<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>This was never an elegant solution but I assumed that enough of us agreed it was better than the status quo. Therefore, its perhaps a case of us ALAC members needing to remember to implement it when we have meaningfully divergent views rather than having multiple staff members trained in the ancient art of wiki-fu.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><br>==<br>Bart</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:alan.greenberg@mcgill.ca">Alan Greenberg</a><br><b>Sent: </b>Thursday, May 10, 2018 2:44 PM<br><b>To: </b><a href="mailto:alac@atlarge-lists.icann.org">ALAC</a><br><b>Cc: </b><a href="mailto:alac@atlarge-lists.icann.org">ALAC</a><br><b>Subject: </b>Re: [ALAC] Suggested revision of At-Large Policy Development template</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We have again had a problem with the original comment being changed without clear notice and causing confusion.<br><br>I have investigated whether Maureen suggestion is possible (have additional DRAFT boxes be added as needed) and found that this is not practical for a number of reasons (a) it would have to be done by staff since non-staff do not have the privileges to alter these macros; b) few staff have the skills; c) having specific staff do it on a tight time-frame is not practical). In light of that, I have instructed that staff modify the pages to give clear instructions for what can be done without extensive training or staff time to address the issue.<br><br>Alan<br><br><br>At 01/02/2018 11:07 PM, Alan Greenberg wrote:<br><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>This happens relatively infrequently. Why create a new process that requires staff intervention when simply stacking the version in the box now called DRAFT(s) will do. And it allows for more than two version is required?<br><br>At 01/02/2018 09:54 PM, Maureen Hilyard wrote:<br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>But as Holly said, sometimes you just need another space to reorganise your thoughts before it becomes the final draft... although sometimes it ends up as the final draft.. <br><br>But you are only currently given 2 options, first and final.. <br><br>There should be two boxes to start off with, and the penholder can ask for another one if required as a transition section before the final statement . But it should be highlighted in another colour what changes have been made. <br><br>On Thu, Feb 1, 2018 at 12:23 PM, Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a> > wrote: <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>When I was drafting more statements, I also would often post my "first draft" in the comment area and move it up if it had general acceptance. But there will always be cases where there are multiple draft versions posted and I was trying to find a really easy path for doing that without losing history along the way. Having staff create new boxes along the ways seems likea much more challenging way to address the problem...<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Alan<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>At 01/02/2018 04:33 PM, Maureen Hilyard wrote:<o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'>I think there is room for having personal comments remaining at the bottom of the wiki page, but drafts of the statement should be able to be inserted as they develop. It might mean teaching penholders how to create these boxes for new drafts or asking the new policy support staff person to create one for them.<br><br><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>On Thu, Feb 1, 2018 at 11:28 AM, Holly Raiche <<a href="mailto:h.raiche@internode.on.net"> h.raiche@internode.on.net</a>> wrote: <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Makes sense to me. When I died to post a âfirirst draftâ of f the privacy stuff, I couldnât, and so put stuff in tn the âcomment⠬⢠space. While that whole wiki reflects pretty much what the discussion was, it doesnât follow the concept of firfirst and final draft<span style='color:#888888'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='color:#888888'>Holly</span> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>On 2 Feb 2018, at 6:40 am, Maureen Hilyard <<a href="mailto:maureen.hilyard@gmail.com"> maureen.hilyard@gmail.com</a>> wrote:<br><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-left:.5in'>Sounds good to me because when you don't see the developments as new contributions are incorporated into the statements, it may seem as if its only just been ONE or only a few contributors <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Some statements go through several transitions. <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>M <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>On Thu, Feb 1, 2018 at 8:42 AM, Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a> > wrote: <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>It has been pointed out to me that the template we use has a space for "First Draft" and then "Final Draft". This works for issues that do not generate a lot of dialogue and revision of the statement. For such statements, there is no specific place to post the revised version(s). Simply changing the first draft does not really work, because then we are left with Wiki comments on that draft that refer back to something that s no longer there (unless you go to the trouble of finding the correct earlier version).<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>I suggest that we change the title from "FIRST DRAFT SUBMITTED" to "DRAFT STATEMENTS" and add instructions saying that if multiple draft versions are posted, old versions should remain, with the newer version posted at the top of the box, prefixed with the date posted and author, and separated from earlier versions by a horizontal line.<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>That way we have a full history of the draft evolution.<o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Does anyone see a reason not to do this? <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>Alan <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>_______________________________________________ <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>ALAC mailing list <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>At-Large Online: <a href="http://www.atlarge.icann.org/">http://www.atlarge.icann.org</a> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a> <o:p></o:p></p></blockquote><p class=MsoNormal style='margin-left:.5in'>_______________________________________________ <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>ALAC mailing list <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'>At-Large Online: <a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a> <o:p></o:p></p></blockquote></blockquote></blockquote><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:1.5in;margin-bottom:5.0pt;margin-left:2.0in'>ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a> <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>