<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>As something of an aside, the underlying suitability of the current wiki to our policy drafting needs might need to be considered. TTF?<br><br>Re the issue on the table. For right now, I'm drawn towards manually inserting the newer version of a statement at the top with relevant identifying info (date erc). The prior statement(s) would remain beneath for reference. <br><br>Inelegant? Yes.</div><br><br><div style="font-size:75%;color:#252525">Sent from Samsung Focus</div><br><br><div>-------- Original message --------</div><div>From: Judith Hellerstein <judith@jhellerstein.com> </div><div>Date: 2/2/18 5:12 AM (GMT-05:00) </div><div>To: Maureen Hilyard <maureen.hilyard@gmail.com> </div><div>Cc: ALAC <alac@atlarge-lists.icann.org>, Alan Greenberg <alan.greenberg@mcgill.ca> </div><div>Subject: Re: [ALAC] Suggested revision of At-Large Policy Development template </div><div><br></div>Hi all,<div><br></div><div>I agree with Maureen </div><div>Best </div><div>Judith <br><br><div id="AppleMailSignature">Sent from my iPhone<div><a href="mailto:Judith@jhellerstein.com">Judith@jhellerstein.com</a></div><div>Skype ID:Judithhellerstein </div></div><div><br>On Feb 2, 2018, at 10:09 AM, Maureen Hilyard <<a href="mailto:maureen.hilyard@gmail.com">maureen.hilyard@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">If we are working towards an appropriate statement that reflects all related views then, does it matter? The page can be as long as we like as long as we get to the end product. <div><br></div><div>You asked for our opinions but you are still stating your own as THE view. (and I'm not being grumpy about it, Im just stating my piece. :))</div><div><br></div><div>And as you say it happens infrequently, but when it does, why are we sticking to a dumb rule.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 1, 2018 at 5:07 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>
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?<span class=""><br><br>
At 01/02/2018 09:54 PM, Maureen Hilyard wrote:<br>
</span><blockquote type="cite" class="m_-1171271091432090239cite"><span class="">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" target="_blank">alan.greenberg@mcgill.ca</a>
> wrote:<br>
</span><dl>
<dd><span class="">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>
</span></dd><dd>Alan<br><br>
</dd><dd><span class="">At 01/02/2018 04:33 PM, Maureen Hilyard wrote:<br>
</span><blockquote type="cite" class="m_-1171271091432090239cite">
<dd><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>
</span></dd><dd><span class="">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:
</span><dl>
<dd>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 class=""><font color="#888888"><br>
</font></span></dd><dd><font color="#888888">Holly</font></dd><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_-1171271091432090239cite">
<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>
</dd><dd>Some statements go through several transitions.<br><br>
</dd><dd>M <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:
<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>
</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>
</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>
</dd><dd>Alan<br>
</dd><dd>______________________________<wbr>_________________
</dd><dd>ALAC mailing list
</dd><dd><a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">
ALAC@atlarge-lists.icann.org</a>
</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>
</dd><dd>At-Large Online:
<a href="http://www.atlarge.icann.org/" target="_blank">http://www.atlarge.icann.org</a>
</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>
</dd></dl></dd></blockquote></dd></dl></dd></blockquote></dd></dl></blockquote>
<span class=""><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></span><br>
</div>
</blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>ALAC mailing list</span><br><span><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a></span><br><span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a></span><br><span></span><br><span>At-Large Online: <a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a></span><br><span>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></span></div></blockquote></div></body></html>