<div dir="ltr">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.. <div><br></div><div>But you are only currently given 2 options, first and final.. </div><div><br></div><div>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. </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 1, 2018 at 12:23 PM, Alan Greenberg <span dir="ltr"><<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
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...<br><br>
Alan<span class=""><br><br>
At 01/02/2018 04:33 PM, Maureen Hilyard wrote:<br>
</span><blockquote type="cite" class="m_3948708457364076926cite"><span class="">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>
<br><br>
On Thu, Feb 1, 2018 at 11:28 AM, Holly Raiche
<<a href="mailto:h.raiche@internode.on.net" target="_blank">
h.raiche@internode.on.net</a>> wrote:<br>
</span><dl>
<dd>Makes sense to me. When I died to post a ‘first draft’ of
the privacy stuff, I couldn’t, and so put stuff in the ‘comment’
space. While that whole wiki reflects pretty much what the
discussion was, it doesn’t follow the concept of first and final
draft<span class=""><font color="#888888"><br><br>
</font></span></dd><dd><font color="#888888">Holly</font></dd><br><br>
<dd>On 2 Feb 2018, at 6:40 am, Maureen Hilyard
<<a href="mailto:maureen.hilyard@gmail.com" target="_blank">
maureen.hilyard@gmail.com</a>> wrote:<br><br>
<blockquote type="cite" class="m_3948708457364076926cite">
<dd>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<br><br>
</dd><dd>Some statements go through several transitions.<br><br>
</dd><dd>M <br><br>
</dd><dd>On Thu, Feb 1, 2018 at 8:42 AM, Alan Greenberg
<<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>
> wrote:<br>
<dl>
<dd>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 is no longer there (unless you go to the trouble of
finding the correct earlier version).<br><br>
</dd><dd>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.<br><br>
</dd><dd>That way we have a full history of the draft evolution.<br><br>
</dd><dd>Does anyone see a reason not to do this?<br><br>
</dd><dd>Alan<br><br>
</dd><dd>______________________________<wbr>_________________<br>
</dd><dd>ALAC mailing list<br>
</dd><dd><a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">
ALAC@atlarge-lists.icann.org</a><br>
</dd><dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">
https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br><br>
</dd><dd>At-Large Online:
<a href="http://www.atlarge.icann.org/" target="_blank">http://www.atlarge.icann.org</a>
<br>
</dd><dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank">
https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</a>
<br><br>
</dd></dl></dd></blockquote></dd></dl><br>
<dd>______________________________<wbr>_________________<br>
</dd><dd>ALAC mailing list<br>
</dd><dd><a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">
ALAC@atlarge-lists.icann.org</a><br>
</dd><dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">
https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br><br>
</dd><dd>At-Large Online:
<a href="http://www.atlarge.icann.org" target="_blank">http://www.atlarge.icann.org</a>
<br>
</dd><dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank">
https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</a>
</dd></blockquote><br>
</div>
</blockquote></div><br></div>