Hey folks,
today I've realized (again) we need more contributors to review
current docs and update them. I've thinking about creating a kind of
"Documentation Contributor" role, composed by people who could help
editors reviewing and updating content.
These contributors would be able to view documents in draft
(non-public) state and edit them, but not to publish them. I don't
think this enters in conflict with the planned KB/core docs split nor
the documentation editors' responsabilities, and would certainly help
us with reviews. I've often had problems finding free editors to
review my own work (I'm also an editor).
Thoughts? Is this a stupid, a reasonable, a good idea? Any input is
appreciated. :)
Thank you very much for your time!
-- israel
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.
http://p.sf.net/sfu/bobj-july_______________________________________________
Plone-docs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-docsIsrael Saeta Pérez
Re: Documentation Contributor role
