<div dir="ltr">There was a time when despite putting out numerous calls to At-Large/ALAC for responses for public comment, there was nil response. so that the fact we are getting comments at all is a refreshing change. </div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 12, 2018 at 3:47 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>
We may well need a better process to handle issues where there are
differeing opinions. To be honest, at times we have not had sufficient
differeing opinions for that to matter, so if we do have such a situation
now, I find it rather refreshing.<br><br>
But to be clear, the change documented here is just to better track
revised drafts as they come up, not necessarily due to differing opinions
(although there was a bit of that here).<br><br>
ALan<div><div class="h5"><br><br>
At 12/05/2018 09:33 PM, Holly Raiche wrote:<br><br>
</div></div><blockquote type="cite" class="m_-8215002545533194739cite"><div><div class="h5">Folks<br><br>
I would hope this becomes an item for the revised policy
committee. We do need a better way to handle statements when there
are numerous comments - particularly when there is disagreement amongst
them<br><br>
Holly<br>
On 11 May 2018, at 4:37 am, Alan Greenberg
<<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>
> wrote:<br><br>
<blockquote type="cite" class="m_-8215002545533194739cite">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>
<blockquote type="cite" class="m_-8215002545533194739cite">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>
<blockquote type="cite" class="m_-8215002545533194739cite">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:
<dl>
<dd>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...
</dd><dd>Alan
</dd><dd>At 01/02/2018 04:33 PM, Maureen Hilyard
wrote:<blockquote type="cite" class="m_-8215002545533194739cite">
<dd>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>
</dd><dd>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:
<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<font color="#888888">
</font></dd><dd><font color="#888888">Holly</font></dd>
<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_-8215002545533194739cite">
<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
</dd><dd>Some statements go through several transitions.
</dd><dd>M
</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 s no longer there (unless you go to the trouble of
finding the correct earlier version).
</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.
</dd><dd>That way we have a full history of the draft evolution.
</dd><dd>Does anyone see a reason not to do this?
</dd><dd>Alan
</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>
</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>
</dd></dl></dd></blockquote></dd></dl></dd></blockquote></dd></dl></blockquote></blockquote>
______________________________<wbr>_________________ <br>
ALAC mailing list <br>
<a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">
ALAC@atlarge-lists.icann.org</a> <br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">
https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br>
At-Large Online:
<a href="http://www.atlarge.icann.org/" target="_blank">http://www.atlarge.icann.org</a>
<br>
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>
</blockquote></div></div></blockquote>______________________________<wbr>_________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">
ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">
https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br><br>
At-Large Online:
<a href="http://www.atlarge.icann.org/" target="_blank">
http://www.atlarge.icann.org</a><br>
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></div>
Content-Type: text/plain; charset="us-ascii"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: inline<br>
X-Microsoft-Exchange-<wbr>Diagnostics:<br>
<u></u> <u></u>
1;YTOPR01MB0396;27:<wbr>QYr8Y9Ox0YnsrsnLZjDWsvZ24tyPxM<wbr>o1skhm2PbqDCXszxoCKcOJxg8nvSym<wbr>6NFkHpKSeHPYKi1afUXKrDFOtIgsNF<wbr>sh/KhqaKE6pChO+<wbr>bsVU0JLM0Tx47NkPtRrtCIM<br>
X-Microsoft-Antispam-Message-<wbr>Info:<br>
<u></u> <u></u>
zKcJgtPuDrOZXbyI1AFtP2eCObowbr<wbr>Vu4NYpwW6xPWkfmI0UMO839TB68R6E<wbr>FCurwV+A+<wbr>kvpZdOkYMpo3zTI3D7DsnpN9MDu6c6<wbr>uTD+<wbr>rt0ElpX2RXrSbKVlxsM4vWrsk3BDMa<wbr>2/4NSb64qRKptB+8Sy4+<wbr>uox7BdwG4ABFK4Is4+<wbr>cwlT6iUOH7j2SOnBKApC58thT7ONnu<wbr>NunL3YFIafjk3S68enquutjJGf0uCV<wbr>cjYW7XTxk3hQn9k6zVinNmy5ro1Hd+<wbr>ktcHglaz1jwbdYAGy2jhj4J86keZs6<wbr>FqzkCsMpKDgFjz9jjUs8lGxbH4YMLu<wbr>RhUmqucPB7oLDPrdla0AIvNniOGQj+<wbr>tmmLuNAXusp9J7tKaeJMwvPNKH9pJI<wbr>RJjse8OBvCdQfCAs6jpfa/UB+<wbr>a18Yg7PNnBfOvnf0+ctwKk6/<wbr>tfLPZEHqK3plKQxwpAkdlSv35KQq+<wbr>QL9rS01SeX8pzoNn6qCdrq3B/<wbr>Bu5apX+7Up/7Q8FmQiEuHMjay2B1<span class=""><br>
<br>
______________________________<wbr>_________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">
https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br><br>
At-Large Online:
<a href="http://www.atlarge.icann.org/" target="_blank">
http://www.atlarge.icann.org</a><br>
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>
)</span>
<br>______________________________<wbr>_________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" rel="noreferrer" target="_blank">https://atlarge-lists.icann.<wbr>org/mailman/listinfo/alac</a><br>
<br>
At-Large Online: <a href="http://www.atlarge.icann.org" rel="noreferrer" target="_blank">http://www.atlarge.icann.org</a><br>
ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" rel="noreferrer" target="_blank">https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Advisory+Committee+(ALAC)</a><br></blockquote></div><br></div>