[documentation] training system

[ruben d canlas jr]

Sorry I just read this now. What's the status on this? Is there now a team
working on the training system?

thanks
benc



>
> Here are my thoughts about why I would say this:
>
> 1) In order to develop a structured training system, the base
> documentation needs to be very solid.  If not for the entire doc
> system, at least for the particular area that is going to be
> initially developed (i.e. Newbie/Install/Initial Configuration).
>
> 2) I maybe mistaken in this statement, but I have yet to find a
> Roadmap or structured plan for the documentation system itself.
> While I realize there is a documentation project page (which tracks
> bugs, feature requests, etc.), I think that a structured plan would
> be very beneficial.
>
> Upon developing this structured attack plan, I would suggest that a
> serious effort be made to compartmentalize each of the specific
> milestones (doc sections) and assign them based on a volunteer basis.
> Once the milestones are assigned, get them completed in a very
> defined manner rather than having so many people doing different
> things at different times.
>
> An example would be the following based on the current doc structure.:
>
> 1.0 - Open Discussion on [Drupal.org README first] (Limit to 3 day
> discussion)
> -1.1 - Define Changes [Drupal.org README first] (assistant of section
> compiles changes)
> -1.2 - Commit Changes [Drupal.org README first] (moderator of section
> changes compiles changes)
> -1.3 - Close Changes [Drupal.org README first] (reopen at a set
> interval in the future - create a sandbox for future changes to be
> committed at next opening session.)
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/documentation/attachments/20060223/eea7d068/attachment.htm