[Grok-dev] Maintenance of Community Documentation

Kent Tenney ktenney at gmail.com
Tue Jun 9 09:05:42 EDT 2009

On Tue, Jun 9, 2009 at 3:02 AM, Sebastian Ware<sebastian at urbantalk.se> wrote:
> I just want to note that not getting an explicit go ahead is a show
> stopper for us. We need to know that we have the endorsement of the
> community in general and Martijn in particular.
> Basically, if you think we are getting it wrong let us know so we
> don't waste everybodys time. And if you think we are getting it right,
> just give us a thumbs up.



> Mvh Sebastian
> 8 jun 2009 kl. 10.31 skrev Sebastian Ware:
>> Hi all,
>> I have had some discussions with Tim Cook and Steve Schmechel and we
>> have agreed that we would like to put some effort into organising the
>> maintenance of the community docs.
>> If we could get peoples blessing on this we would like to do the
>> following:
>> -Create a separate Community Doc email list [grok-doc]
>> The purpose would be to highlight documentation efforts and questions
>> related to documentation. This would be the place to go if one is
>> working on community documentation or has questions related to
>> community docs. This could also be the place where Grok users could
>> learn more about the capabilities of Grok by reading the discussions.
>> Basically we would like to support the emerging Grok culture of
>> learning-by-writing-docs. This would benefit everybody.
>> -Organise a peer review workflow. Tagging content as:
>>  - Peer reviewed for version x.y (doc looks ok)
>>  - Out of date (with regards to current version)
>>  - Needs editing (for reason xyz)
>>  - Needs merging (with content xyz)
>>  Maybe create a simple webtool to keep track of peer reviews (if this
>> isn't easily implemented in Plone).
>> -Organise on-line sprints every three months
>> The purpose is to focus the community during a week to peer review and
>> improve community docs. If the tasks are reasonably well organised,
>> this could be fun and very, very useful.
>> If this sounds reasonable I'll be happy to take a lead on this effort.
>> Mvh Sebastian
>> _______________________________________________
>> Grok-dev mailing list
>> Grok-dev at zope.org
>> http://mail.zope.org/mailman/listinfo/grok-dev
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev

More information about the Grok-dev mailing list