[Grok-dev] Community Documentation

[Sebastian Ware]

I think you are on to something important. I was advocating early on  
having an editor responsible of keeping an eye on the community docs.  
The problems I was pointing at are quite evident right now. The  
community docs don't get maintained, merged or cleaned up in a way  
that is required for them, as a whole, to stay useful.

Whereas the quality of a lot of the docs that are contributed is  
great. The path right now is the old Zope.org fire-and-forget mish- 
mash-web of gradually outdated user content.

I'd be happy to team up with you on sketching out a simple editorial  
workflow so we could manage the user contributed content better. (I am  
not thinking along the terms of increasing the barrier of entry, just  
managing the content once it has been submitted)

Mvh Sebastian

22 maj 2009 kl. 15.12 skrev Tim Cook:

> I want to volunteer to help review community documentation on the Grok
> site.
>
> I need to get up to speed on some things as far as editing goes but  
> I'm
> happy to do that if the team can use some help.
>
> Cheers,
> Tim
>
>
>
>
> -- 
> Timothy Cook, MSc
> Health Informatics Research & Development Services
> LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
> Skype ID == timothy.cook
> **************************************************************
> *You may get my Public GPG key from  popular keyservers or   *
> *from this link http://timothywayne.cook.googlepages.com/home*
> **************************************************************
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev