Sorry I just read this now. What's the status on this? Is there now a team working on the training system?<br><br>thanks<br>benc<br><br><br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br>Here are my thoughts about why I would say this:<br><br>1) In order to develop a structured training system, the base<br>documentation needs to be very solid. If not for the entire doc<br>system, at least for the particular area that is going to be
<br>initially developed (i.e. Newbie/Install/Initial Configuration).<br><br>2) I maybe mistaken in this statement, but I have yet to find a<br>Roadmap or structured plan for the documentation system itself.<br>While I realize there is a documentation project page (which tracks
<br>bugs, feature requests, etc.), I think that a structured plan would<br>be very beneficial.<br><br>Upon developing this structured attack plan, I would suggest that a<br>serious effort be made to compartmentalize each of the specific
<br>milestones (doc sections) and assign them based on a volunteer basis.<br>Once the milestones are assigned, get them completed in a very<br>defined manner rather than having so many people doing different<br>things at different times.
<br><br>An example would be the following based on the current doc structure.:<br><br>1.0 - Open Discussion on [<a href="http://Drupal.org">Drupal.org</a> README first] (Limit to 3 day<br>discussion)<br>-1.1 - Define Changes [
<a href="http://Drupal.org">Drupal.org</a> README first] (assistant of section<br>compiles changes)<br>-1.2 - Commit Changes [<a href="http://Drupal.org">Drupal.org</a> README first] (moderator of section<br>changes compiles changes)
<br>-1.3 - Close Changes [<a href="http://Drupal.org">Drupal.org</a> README first] (reopen at a set<br>interval in the future - create a sandbox for future changes to be<br>committed at next opening session.)<br><br><br></blockquote>
</div>