[drupal-docs] establishing a process/workflow for creating, submitting, editing documentation

[Anisa]

At the current status of everything, using the project module instead of 
the book module's moderation queue offers several advantages, including 
transparency.  It can also be degraded if and when the book module improves.

Anisa.

Dries Buytaert wrote:

>  
>
>>Sounds like project issues it is.
>>
>>    
>>
>
>Great.
>
>
>  
>
>>Questions:
>>
>>Rather than letting non-book maintainers create new pages, would it be
>>better to have them submit new pages and edits via the project module?
>>Would this be easier than dealing with moderation?
>>
>>    
>>
>
>One limitation of the book module is that it is difficult to provide  
>feedback to the original submitter, and that the original submitter  
>can't improve his submission until the last revision is approved.   
>That aside, I think using the book module could work as long there  
>are people to review, approve and fix up contributions.   It is  
>important that these reviewers know the handbook inside out and that  
>they get the big picture.
>
>In short, whether it works or not depends on the willingness of the  
>documentation team to fix up contributions and their insight in the  
>structure of the Drupal handbook.  My gut feeling tells me that in  
>the end, the book module is not up to the job, but neither is the  
>project module.  Fortunately, we have some people (including myself)  
>that are willing to work on the book module ...
>
>I vote for using the book module.
>
>--
>Dries Buytaert  ::  http://www.buytaert.net/
>
>
>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://drupal3.drupal.org/pipermail/documentation/attachments/20050523/aec41654/attachment.htm