[drupal-docs] comments in handbook

[Charlie Lowe]

I like php.net's solution, too. But of course, they don't already have a 
  separate forum area. Better, I think, to minimize the number of areas 
for dicussion. Why not setup a form area under "Development" for Drupal 
handbook/Drupal docs? "Meta" discussion about the "wording/content of 
manual pages" could either be done there, on this list, or perhaps even 
better, through project issues. In other words, it would make sense to 
me for the documentation development process and support to mirror code 
development. Will be less confusing to drupal.org members that way.

Note: Using the project module would centralize a way for people to post 
notices that docs needed to be updated or propose additions to the book 
for evaluation. We've been using the project module on OSDDP, and I 
believe it works pretty well for this other than some of the code 
development terminology used in tagging the issues (i.e., bug report). 
And eventually, using the project module, would encourage it's 
development into a bette documentation construction project management 
solution, something I believe would be an attractive feature for Drupal 
as part of a corporate or organization's knowledge management solution.

So in this case, I'd turn off the the write access to book comments to 
read only. Then, we slowly work through the existing comments and delete 
them as their suggestions are worked into the documentation.

Boris Mann wrote:
> On Tue, 14 Dec 2004 13:46:12 +0100, Bèr Kessels <berdrupal at tiscali.be> wrote:
>  
> 
>>I think we also need to agree on a general rule for commenting to the
>>handbooks.
>>too often the comments are old, talking about problems that no longer exist,
>>or are even plain support requests.
> 
> 
> I agree with everything that you say here, Ber. I like the comments in
> the PHP.net manual -- different ways of doing things, specific
> questions/answers on how to do X, etc.
> 
> Should we delete comments outright? (sometimes) How do we
> contact/notify the comment poster? (pointing them to forums/project
> issues/etc.) Maybe we should even just turn comments off for book
> pages?
> 
> Aside: I realize comments aren't the right place for this, but how do
> we do "meta" comments, to discuss the wording/content of manual pages?
> 
> Aside #2: it would be great to have comment approval *just* for books.
> This is something else we might want to think about in re-vamping
> default workflow.
> 
> --
> Boris Mann
> http://www.bryght.com