[drupal-docs] Planning for the Drupal 4.7 Documentation Sprint

[Charlie Lowe]

With the Drupal feature freeze underway, it won't be long now before we 
need to begin a documentation sprint for Drupal 4.7 to update the 
existing admin/help documentation that Kieran previously worked so hard on.

The purpose of this email is to discuss the best process for achieving 
this. As I see it, there are two approaches:

1) The Drupal docs team reviews all of the admin/help docs in the 
following sections:

http://drupal.org/handbook/modules
http://drupal.org/handbook/config/contribmodules

Problem with this:

* difficult to coordinate
* many contrib modules are not updated until after the release candidate 
right before Drupal 4.7 will be official released (if not afterwards). 
Depending on how module API's have been changed for this release (is 
this a factor?), they may not work until then.

I would imagine we would need to shoot for reviews and updates of the 
core modules right before and right after Drupal 4.7 RC.

2) A better way to do this would be to implement an ongoing process, one 
that would require the participation of developers. *If* we could get 
developers working on modules to submit Documentation issues when they 
have made changes to a module which requires a documentaiton update, we 
could take care of these on a case-by-base basis, with a big push to 
finish up any during the RC release in time for the stable version. 
Also, this would allow us to track needed changes to contrib module 
documentation and provide patches for subsequent updates.

****


Any thoughts?

Charlie Lowe