[ALAC] Suggested revision of At-Large Policy Development template

[Alan Greenberg]

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...

Alan

At 01/02/2018 04:33 PM, Maureen Hilyard wrote:
>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.
>
>
>
>On Thu, Feb 1, 2018 at 11:28 AM, Holly Raiche 
><<mailto:h.raiche at internode.on.net>h.raiche at internode.on.net> wrote:
>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
>
>Holly
>
>On 2 Feb 2018, at 6:40 am, Maureen Hilyard 
><<mailto:maureen.hilyard at gmail.com>maureen.hilyard at gmail.com> wrote:
>
>>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
>>
>>Some statements go through several transitions.
>>
>>M
>>
>>On Thu, Feb 1, 2018 at 8:42 AM, Alan Greenberg 
>><<mailto:alan.greenberg at mcgill.ca>alan.greenberg at mcgill.ca> wrote:
>>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).
>>
>>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.
>>
>>That way we have a full history of the draft evolution.
>>
>>Does anyone see a reason not to do this?
>>
>>Alan
>>
>>_______________________________________________
>>ALAC mailing list
>><mailto:ALAC at atlarge-lists.icann.org>ALAC at atlarge-lists.icann.org
>>https://atlarge-lists.icann.org/mailman/listinfo/alac
>>
>>At-Large Online: <http://www.atlarge.icann.org/>http://www.atlarge.icann.org
>>ALAC Working Wiki: 
>><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
>>
>>
>>_______________________________________________
>>ALAC mailing list
>><mailto:ALAC at atlarge-lists.icann.org>ALAC at atlarge-lists.icann.org
>>https://atlarge-lists.icann.org/mailman/listinfo/alac
>>
>>At-Large Online: <http://www.atlarge.icann.org>http://www.atlarge.icann.org
>>ALAC Working Wiki: 
>><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20180201/c9d28567/attachment.html>