http://groups.drupal.org/documentation-team News about ongoing work and ways to get involved with the Drupal.org Documentation Team en http://groups.drupal.org/node/16988 <p>Our current style guide for the handbooks has not been reviewed in quite a while.</p> <p>siliconmeadow and LeeHunter are the leads for this project.</p> <p>We have determined that there really is no need for a separate writer's guide and style guide. One place that says "this is how we do stuff here" would probably be more useful. So we need to look at consolidating the current pages:<br /> <a href="http://drupal.org/documentation-writers-guide" title="http://drupal.org/documentation-writers-guide">http://drupal.org/documentation-writers-guide</a><br /> <a href="http://drupal.org/about/authoring" title="http://drupal.org/about/authoring">http://drupal.org/about/authoring</a></p> <p>Would also be nice if we can work on adding some sample templates for project help files (like INSTALL.txt and README.txt)</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Project - open Documentation Team Fri, 21 Nov 2008 23:55:03 +0000 add1sun 16988 at http://groups.drupal.org http://groups.drupal.org/node/16987 <p>We need to make sure that we have a clear, complete <a href="http://drupal.org/getting-started/6" rel="nofollow">Getting Started guide for Drupal 6</a>, along the same lines as the <a href="http://drupal.org/getting-started/5" rel="nofollow">Drupal 5 guide</a>. We are currently discussing <a href="http://drupal.org/node/337079" rel="nofollow">how to approach this</a>. Originally we were just going to duplicate the D5 guide. We should have an approach and start implementation by Monday, November 24.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Project - open Documentation Team Fri, 21 Nov 2008 23:51:02 +0000 add1sun 16987 at http://groups.drupal.org http://groups.drupal.org/node/16977 <p>Once again, big thanks to Hans for pulling together a summary for us. The original IRC log is here: <a href="http://pastebin.com/f13c30b7a" title="http://pastebin.com/f13c30b7a">http://pastebin.com/f13c30b7a</a></p> <h2>Announcements</h2> <ul> <li>Leisa from MBD has a new post up re: docs redesign ideas: <a href="http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/" title="http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section/">http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-docume...</a></li> <li>The next iteration (#9) of the redesign just went up <a href="http://drupal.markboultondesign.com/iteration9/" title="http://drupal.markboultondesign.com/iteration9/">http://drupal.markboultondesign.com/iteration9/</a></li> <li>The FP post re: open editing is up</li> <li>We are testing out using an online colab tool called Diigo to see if this helps us hammer on issues directly in the handbook pages. Read more about that here: <a href="http://drupal.org/node/332021" title="http://drupal.org/node/332021">http://drupal.org/node/332021</a></li> </ul> <h2>Agenda</h2> <h3>New page holding pen: http://lists.drupal.org/pipermail/documentation/2008-November/006351.html</h3> <p>Basically we've got +1s on this so I'd like to implement it. There is an <a href="http://drupal.org/node/337134" rel="nofollow">issue for drupal.org customizations</a> since this will take a patch code to implement.</p> <h3>New projects on radar:</h3> <p><strong>Getting started guide for D6 needs basic content completed</strong><br /> We need to get the content filled out and we can start by copying stuff from the D5 guide and then updating to D6. Shai_ stepped up to commit time to this. The question was raised on why we are creation a "duplicate" version rather than trying to generalize like we are with themeing. Basically the idea that it is simply faster to do that right now, while the need is rather urgent, and there is a correlation between the D5 HTML and PDF. (Note by Addi, while I proposed and argued this, I'm not totally convinced that duplication is a good idea. I'd like to talk out a plan a little more this weekend, if possible.)</p> <p><strong>Reorganizing the theme guides</strong><br /> Main issue: <a href="http://groups.drupal.org/node/16594" title="http://groups.drupal.org/node/16594">http://groups.drupal.org/node/16594</a></p> <p>HansBKK has taken the lead on a theme guide team to get the theme guides somewhat sane and will be the main point of contact for questions. Theme team to post recommendations via issues to the main queue for feedback before making major changes. They will give a status report every couple of weeks. Addi will do the top-level book wrangling first and then the team can take over.</p> <p>HansBKK has written up a "Heads-up: we're rearranging again" <a href="http://drupal.org/node/337208" rel="nofollow">announcement draft</a> to the issue queue for feedback, Addi will promote to front page.</p> <p>The team will try using Diigo, a "social bookmarking" tool:</p> <ul> <li>browser extension or bookmarklet + website, drupal-docs team has its own group</li> <li>allows for tagging and sticky notes to be posted directly to the pages under discussion. no copy/paste back and forth</li> <li>"meta" discussion re page classification and navigation hierarchy can take place there without cluttering up the main doc team's channels</li> <li> <p>All docs team members invited to join:</p> <ul> <li>sign up with Diigo first: <a href="http://www.diigo.com" title="http://www.diigo.com">http://www.diigo.com</a></li> <li>then come to the drupal-docs group here: <a href="http://groups.diigo.com/groups/drupal_docs" title="http://groups.diigo.com/groups/drupal_docs">http://groups.diigo.com/groups/drupal_docs</a> and request</li> <li>then go to the head of the D6 theming guide and try it out, add sticky notes to pages, highlight text then add a sticky to the highlight.</li> </ul> </li> <li> <p>Diigo guidelines:</p> <ul> <li>only post d.o. links to the drupal-docs group, and for now limited to theming stuff</li> <li>use Diigo's discussion facilities just for "meta" issues re page classification and navigation hierarchy</li> <li>substantive content discussion to take place in main docs-team channels on d.o.</li> </ul> </li> </ul> <p>Current members on Diigo:<br /> Heather - (nearlythere)<br /> Addi (add1sun)<br /> Richard (siliconmeadow)<br /> Hans (hansbkk)<br /> Lee (leehunter)<br /> Wolf (wolfflow)<br /> Shai (shaigluskin)<br /> dvessel</p> <p><strong>Reviewing/expanding the handbook style guide and creation of some basic templates</strong><br /> siliconmeadow and LeeHunter stepped up to help guide this one.</p> <p>We determined that there really is no need for a separate writer's guide and style guide. One place that says "this is how we do stuff here" would probably be more useful. So we need to look at consolidating the current pages:<br /> <a href="http://drupal.org/documentation-writers-guide" title="http://drupal.org/documentation-writers-guide">http://drupal.org/documentation-writers-guide</a><br /> <a href="http://drupal.org/about/authoring" title="http://drupal.org/about/authoring">http://drupal.org/about/authoring</a></p> <p>Would also be nice if we can work on adding some sample templates for project help files (like INSTALL.txt and README.txt)</p> <p><strong>Additional topic that came up was using groups.drupal.org and deprecating the mail list</strong><br /> The discussion on this was brief and positive enough to post for more talk. There is a <a href="http://groups.drupal.org/node/16958" rel="nofollow">g.d.o post</a> and a <a href="http://lists.drupal.org/pipermail/documentation/2008-November/006373.html" rel="nofollow">mailing list post</a>.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> http://groups.drupal.org/node/16977#comments Minutes Documentation Team Fri, 21 Nov 2008 15:20:35 +0000 add1sun 16977 at http://groups.drupal.org http://groups.drupal.org/node/16958 <p>So this is an issue that has been kicking around in my head for a while. It was <a href="http://lists.drupal.org/pipermail/documentation/2008-March/thread.html#5900" rel="nofollow">raised</a> briefly earlier this year on the list and it was decided to stick with the mailing list. I raised it again today during our IRC meeting to get a general pulse. So, I'm going to lay it all out and see what the larger team thinks.</p> <p>I am proposing that we deprecate the documentation mailing list and use groups.drupal.org for our discussions instead. In order to not have conversations happening in two places we need to have one definitive "discussion" venue. Due to this, the current docs group is "read-only." To make it read-only we have to limit who can actually become a member of the group. Limiting membership like this severely hampers our use of all the tools that g.d.o could offer us.</p> <p>If we allowed membership and free posting on the g.d.o group, we would:<br /> - Still have email notifications of all discussions.<br /> - Be able to use wiki posts to collaborate on one living document rather than having to attach separate iterations to an issue in the queue.<br /> - Read threads all on one page rather than have to page through the mailman archive.<br /> - Organize and categorize discussions to make it easier to find areas of interest.<br /> - Replying to old threads that you didn't actually receive in email is clear and straightforward - just leave a new comment. (How to respond to archived mail threads is not an apparent thing.)</p> <p>The only advantage that the mailing list provides that the group does not, is the ability to reply to a thread directly from your email. I feel that losing this feature is worth the advantages we would gain by shifting to g.d.o. I feel that this is true for actually collaborating as a team and to make it easier for new users to join in.</p> <p>I am posting this to the mailing list as well as posting on g.d.o with comments turned <em>on</em>. This is one conversation that I'd like to see discussed wherever folks feel most comfortable.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> http://groups.drupal.org/node/16958#comments Documentation Team Thu, 20 Nov 2008 23:05:03 +0000 add1sun 16958 at http://groups.drupal.org http://groups.drupal.org/node/16719 <p>We've set the time for the next IRC meeting. The meeting will be for 1 hour in the #drupal-docs FreeNode channel on Thursday, November 20, 2008 at 1 p.m. EST (18:00 GMT, 10 a.m. PST).</p> <p>Agenda:</p> <ul> <li>Announcements</li> <li><a href="http://groups.drupal.org/node/15779" rel="nofollow">Limiting page creation?</a> (please continue this discussion on list and use the meeting to hash out remaining bits/action items)</li> <li>Next projects on radar: <ul> <li>Getting started guide for D6 needs basic content completed</li> <li><a href="http://groups.drupal.org/node/16594" rel="nofollow">Reorganizing the theme guides</a></li> <li>Reviewing/expanding the handbook style guide and creation of some basic templates</li> </ul> </li> </ul> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Meeting Documentation Team Thu, 13 Nov 2008 22:24:06 +0000 add1sun 16719 at http://groups.drupal.org http://groups.drupal.org/node/16610 <p>The last meeting we covered a lot of ground and bounced around a bunch of ideas. We didn't have much time to dive into new projects, so let's set another one up soon. the meeting will be for 1 hour in the #drupal-docs FreeNode channel.</p> <p>Here is the scheduling Doodle: <a href="http://doodle.com/u2xw6996qgkfd9yt" title="http://doodle.com/u2xw6996qgkfd9yt">http://doodle.com/u2xw6996qgkfd9yt</a> (Please respond to the Doodle with your preference by Thursday, November 13.)</p> <p>Agenda:</p> <ul> <li>Announcements</li> <li><a href="http://groups.drupal.org/node/15779" rel="nofollow">Limiting page creation?</a> (let's please continue this discussion on list and use the meeting to hash out remaining bits/action items)</li> <li>Next projects on radar: <ul> <li>Getting started guide for D6 needs basic content completed</li> <li><a href="http://groups.drupal.org/node/16594" rel="nofollow">Reorganizing the theme guides</a></li> <li>Reviewing/expanding the handbook style guide and creation of some basic templates.</li> </ul> </li> </ul> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Announcement Documentation Team Sun, 09 Nov 2008 23:59:04 +0000 add1sun 16610 at http://groups.drupal.org http://groups.drupal.org/node/16594 <p><a href="http://drupal.org/user/149289" rel="nofollow">HansBKK</a> is currently lead on the workgroup to help create a single, well-organized Theming Guide, and will be the main point of contact for questions. Any interested <a href="http://drupal.org/node/109372" rel="nofollow">documentation team members</a> are invited to join in this effort. Others that would like to contribute should first <a href="http://drupal.org/node/23367" rel="nofollow">request to join the docs team</a>; see the "Pitch In!" section below.</p> <h3>History</h3> <p>The original post in the documentation team's <a href="http://groups.drupal.org/node/14492/projects" rel="nofollow">issue queue</a> discussing this project was <a href="http://drupal.org/node/254947" rel="nofollow">Reorganize Theme handbooks</a> and the currently active one is <a href="http://drupal.org/node/337091" rel="nofollow">Theming doc workgroup forming</a>.</p> <p>See the <a href="http://drupal.org/node/337857" rel="nofollow">announcement for this project</a> posted to drupal.org's front page.</p> <h3>Current project stage</h3> <p>Addi has merged the main D5 and D6 theming guides into one. There are still four other major locations for theming information in the drupal.org handbooks that are candidates for merging once we have a decent structure:</p> <ul> <li><a href="http://drupal.org/node/196218" rel="nofollow">Beyond the Basics: Theme HowTos</a></li> <li><a href="http://drupal.org/node/45471" rel="nofollow">BtB: Theming snippets</a></li> <li><a href="http://drupal.org/node/196218" rel="nofollow">BtB: Contributed themes</a></li> <li><a href="http://drupal.org/node/323990" rel="nofollow">BtB: Comparisons of contrib themes</a></li> </ul> <p>plus of course many valuable contributions scattered around in other parts of the Handbooks.</p> <p>Note that some sets of theming-related pages will not be moved:</p> <ul> <li>all the automatically generated pages within the automated API documentation system, e.g. <a href="http://api.drupal.org/api/file/themes/garland/template.php" rel="nofollow"> core template.php</a></li> <li>the stream of discussions flowing through the <a href="http://drupal.org/forum/3" rel="nofollow">forums</a></li> <li>those pages pertaining to specific contrib modules, e.g. <a href="http://drupal.org/node/42597" rel="nofollow">Theming Views</a></li> <li><a href="http://drupal.org/node/136502" rel="nofollow">and BtB: Theming videos and slides</a></li> </ul> <p>In fact, module-specific pages currently in the above locations will be moved out to the relevant module's doc pages.</p> <h3>Team tools</h3> <p>To help them classify and re-organize the relevant pages, the team will be using <a href="http://www.diigo.com/index" rel="nofollow">Diigo</a>, a "social bookmarking" tool, where they have created a group called drupal-docs. Diigo's capabilities include:</p> <ul> <li>a group can share bookmarks, and create a standard set of keywords for tagging pages</li> <li>comments threads automatically show up while members are browsing, right on the handbook page being discussed</li> <li>"sticky notes" can contain discussion about a particular section of the page, as can specific highlighted text</li> <li>no copy/pasting links and text back and forth</li> <li>less chatter cluttering up the main doc team's discussion channels</li> <li>works via browser extension (or bookmarklet) + diigo.com web interface</li> </ul> <h3>Pitch in!</h3> <p>Successfully completing this project will be a lot of work, so <strong>all</strong> qualified Drupallers are invited to join in and help; any level of participation is welcome. As this is a sub-group of the documentation group, you must first be a member of the docs team; <a href="http://drupal.org/node/23367" rel="nofollow">here's how to join</a>. You should also have a "reasonable" amount of theming experience, although relative newcomers can contribute valuable feedback from a newbie's POV, and will certainly learn a lot by participating in the project.</p> <p>Once accepted to the main team, first sign up with <a href="http://www.diigo.com/index" rel="nofollow">Diigo</a>, then come to <a href="http://groups.diigo.com/groups/drupal_docs" rel="nofollow">drupal-docs there</a> and request to join the group.</p> <p>Play around and become familiar with the toolset, by creating some private bookmarks; try commenting via sticky notes and highlighting text, as these are immediately visible on the page for any team members coming by. Then go to the head of the <a href="http://drupal.org/theme-guide" rel="nofollow">theming guide</a> and try posting some sticky notes to pages there and sharing them to the group. Also check out the group's Diigo forum.</p> <p>It is important for the rest of the docs team to not be excluded from important discussions, so the workgroup will post its recommendations for feedback, via issues posted to the main documentation queue, before making major structural changes, and give a status report every couple of weeks.</p> <p>We are also putting some guidelines in place for using Diigo specifically. These guidelines will be regularly revised as needed, so theming workgroup members using this tool should return here to review them once in a while.</p> <p>Note we are also investigating other tools, in particular <a href="http://drupal.org/node/337121" rel="nofollow">real-time collaborative editors</a>.</p> <h3>Diigo guidelines</h3> <ul> <li>drupal.org is primary</li> <ul> <li>Diigo's discussion facilities should primarily be used for "meta" issues like page classification and navigation hierarchy</li> <li>substantive discussions about page content or other issues should take place in the main docs-team channels on d.o., where you're also likely to get better answers</li> </ul> <li>target pages - bookmarks and page annotations shared to the group should be</li> <ul> <li>to/on <strong>drupal.org</strong> pages only, and </li> <li>for now, limited to <strong>theming-related</strong> pages only</li> <li>feel free to link to any other relevant pages within your comments, or create your own group for talking about other topics on Diigo</li> </ul> <li>what kind of "Diigo spoor" to use</li> <ul> <li>don't use page-level comments, they are only visible with the sidebar open</li> <li>only use page-level bookmarks for tagging (see standard tags below)</li> <li>post sticky notes to the top of the page for page-level comments</li> <li>start a new sticky note if you're starting a different topic = "topic thread" for the page</li> <li>or if one gets too long (summarize first)</li> <li>use highlights and comment within them when discussing specific text on the page</li> <li>don't highlight whole blocks, just enough to show what you're referring to, e.g. subtitles</li> <li>if you're motivated, clean up your no-longer-relevant comments, unless you think others will need to reference them</li> </ul> </ul> <h3>Diigo tags defined for drupal-docs group</h3> <h4>version applicability tags</h4> <p>Use these to tag theming-related pages, ideally via a sticky with any comments. If the node as a whole is mixed (D5!6) then maybe flag which bits are which with text highlighting. D6 topics that apply to D5+Zen should be explicitly labelled as such. Substitute D4 or D7 if needed.</p> <table> <tr> <td>D5&amp;6 </td> <td> applies to both, doesn't need splitting</td> </tr> <tr> <td>D5!6 </td> <td> some applies to D5 some to D6, needs splitting out</td> </tr> <tr> <td>D6. </td> <td> D6 only</td> </tr> <tr> <td>D5. </td> <td> D5 only</td> </tr> <tr> <td>D6? </td> <td> tagger thinks D6 but wants confirmation</td> </tr> <tr> <td>D5? </td> <td> tagger thinks D5 but wants confirmation</td> </tr> <tr> <td>D? </td> <td> tagger looked at it but doesn't know, asking for help</td> </tr> </table> <p>Feedback on this topic can be posted <a href="/node/338428" rel="nofollow">here</a></p> <h3>Current members on Diigo</h3> <ul> <li>Heather - (nearlythere)</li> <li>Addi (add1sun)</li> <li>Richard (siliconmeadow)</li> <li>Hans (hansbkk)</li> <li>Lee (leehunter)</li> <li>Wolf (wolfflow)</li> <li>Shai (shaigluskin)</li> <li>dvessel</li> <li>Alexander (alexanderpas)</li> <li>Emma Jane (emmajane)</li> <li>Trevor (trevortwining)</li> </ul> <p>Reference: <a href="http://drupal.org/node/332021" rel="nofollow">past discussion on Diigo</a></p> <h3>The Big Picture</h3> <p>As part of the current <a href="http://groups.drupal.org/drupalorg-redesign-plan-drupal-association#-0-3" rel="nofollow">overall drupal.org redesign project</a>, there are more general <a href="http://www.disambiguity.com/drupalorg-redesign-a-strategy-for-the-documentation-section" rel="nofollow">discussions going on</a> about a full re-structuring of Drupal's documentation.</p> <p>The documentation team's reorganizing the theming content should help build our capacity to contribute to the larger project as well.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Project - open Documentation Team Sat, 08 Nov 2008 13:11:30 +0000 add1sun 16594 at http://groups.drupal.org http://groups.drupal.org/node/16581 <p>HUGE thanks to HansBKK for doing the summary this time round. Here is the full log: <a href="http://pastebin.com/f31e56f30" title="http://pastebin.com/f31e56f30">http://pastebin.com/f31e56f30</a> This is the summary for today's IRC meeting, with a few edits by me:</p> <p>Meeting agenda: <a href="http://groups.drupal.org/node/16343" title="http://groups.drupal.org/node/16343">http://groups.drupal.org/node/16343</a></p> <p><strong>Announcement</strong>: ical feed on the group's upcoming events block</p> <h2>Assessing open editing</h2> <p>Addy's thoughts: <a href="http://lists.drupal.org/pipermail/documentation/2008-November/006351.htm" title="http://lists.drupal.org/pipermail/documentation/2008-November/006351.htm">http://lists.drupal.org/pipermail/documentation/2008-November/006351.htm</a>...</p> <p>Consensus it's all good, non-docs team people making useful edits, it's quick to review, just check the diff. Decision: Leave it open, revisit if issues later on, no fixed review date.</p> <p><strong>Ideas/thoughts/suggestions</strong><br /> Most people don't know they can edit, suggestion to encourage them, along the lines of "This is a community contributed page. Please feel free to improve it with your edits."</p> <p>Some issues re test posts, spam but not a lot. Creation of a sandbox for noobs to test post to, could link from the "Please do NOT post test pages. Drupal.org is a production site and you will not be able to delete content once you post it." text.</p> <p>Also steer people to the issues queue to ask for help re creating pages.</p> <p>Addy's idea on a "speed bump" on creating pages, parking them in a separate book to then be placed (by doc team members?): <a href="http://lists.drupal.org/pipermail/documentation/2008-November/006351.htm" title="http://lists.drupal.org/pipermail/documentation/2008-November/006351.htm">http://lists.drupal.org/pipermail/documentation/2008-November/006351.htm</a>...</p> <p>Idea to let the author suggest a place then let it be confirmed or moved rather than a separate book? Needs infrastructure. Don't want to create bottleneck or extra management overhead, leave for redesign.</p> <p>Idea to display badges based on docteam membership, site maintainer role, help prioritize edits needing review.</p> <p>Redesign ideas - would be great if only a small subset of people made "structural" changes.</p> <p>a rating system on posts that flowed through to user ratings</p> <p>Thank you messages and invitation to join the docs team - automated?</p> <p>Tracking who's making a lot of edits recently.</p> <p>Way to flag edits not yet reviewed - workflow system.</p> <p><strong>Things to work on</strong><br /> Recent edits page at <a href="http://drupal.org/handbook/updates" title="http://drupal.org/handbook/updates">http://drupal.org/handbook/updates</a> needs a pager rather than just bumping the fixed number up, pending Views implementation.</p> <p>Need to get one non-conflicting patch made and then Addy will poke the infra dudes.</p> <h2>Redesign</h2> <p>Redesign effort, current doc-specific thread: <a href="http://groups.drupal.org/node/15965" title="http://groups.drupal.org/node/15965">http://groups.drupal.org/node/15965</a></p> <p>Current design iteration: <a href="http://groups.drupal.org/node/16548" title="http://groups.drupal.org/node/16548">http://groups.drupal.org/node/16548</a></p> <h2>Other projects</h2> <p>Work needed on getting some content into the D6 getting started guide, and getting the handbook style guide reviewed, refreshed and prominent, actually use it once we have something we like. Addy wants to work on templates,like README.txt files for module devs and various handook content like snippets.</p> <p>We need to continue discussion and plan another meeting to line up projects.</p> <p><strong>Summarizer's current hobby horse:</strong><br /> Decision needed on the version "forking" issue, e.g. reorg the theme guides:<br /> <a href="http://drupal.org/node/254947" title="http://drupal.org/node/254947">http://drupal.org/node/254947</a><br /> <a href="http://groups.drupal.org/node/15965#comment-56550" title="http://groups.drupal.org/node/15965#comment-56550">http://groups.drupal.org/node/15965#comment-56550</a><br /> <a href="http://drupal.org/node/105356#comment-1094732" title="http://drupal.org/node/105356#comment-1094732">http://drupal.org/node/105356#comment-1094732</a></p> <p>Briefing doc on groups page, then vote?</p> <p>Or if decision is yes, merge topics then next process is deciding specifically how to start the process.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Minutes Documentation Team Fri, 07 Nov 2008 20:41:58 +0000 add1sun 16581 at http://groups.drupal.org http://groups.drupal.org/node/16174 <p>Let's get together and whip up some Doc Love. We'll meet for 3 hours at the DC Public Library to work on Drupal and then, if folks are interested, we can go out for food and drinks after. We have a medium meeting room (A-9) reserved from 2 p.m. to 5 p.m. on Sat. November 8. (<strong>For directions to the room, see below in the Where? section.</strong>)</p> <p>Everyone can feel free to work on whatever they like, for as long as they like. If you only want to stop by for half an hour or the whole time, it's up to you. I will be around to give guidance, give people doc rights if they need them and generally be around to answer questions for the whole time. I'll also bring some drinks and munchies but if you have anything in particular you want to gnosh on, feel free to bring it.</p> <p>Oh and if anyone feels like designing up come cool Drupal Doc Love graphics, I'd be a very happy camper. ;-)</p> <h2>What will we do?</h2> <p>We will run the gamut and have tasks for everyone from total newbie to expert hacker. Here is an idea of the kinds of things to do:<br /> - Copy-editing: good old-fashioned cleanup<br /> - Basic read-through reviews: great for newbies to learn and help at the same time<br /> - Adding screenshots: find places where images would help and get them added to the page<br /> - Rolling comments: adding information form comments back into the parent page<br /> - Code review: check for standards compliance and security on code samples<br /> - Testing: for both code and tutorials/howtos - do they actually work?<br /> - Version upgrades: admin UI pages as well as code<br /> - Issue queue maintenance: see if issues are still valid, review drafts, mark duplicates, etc.<br /> - Review and help code work on docs-related contrib modules (e.g. book access, term message, revision moderation modules)</p> <h2>Where?</h2> <p>We are meeting at the <a href="http://www.dclibrary.org/dcpl/cwp/view.asp?a=1266&amp;q=565330" rel="nofollow">Martin Luther King, Jr. Memorial Library</a>. This is the central DC public library, right in the middle of downtown, near both the Gallery Place and Metro Center metro stops. There is also free parking.</p> <p>901 G Street, NW<br /> Washington, DC 20001<br /> <a href="http://maps.google.com/maps?q=901+G+Street,+NW+Washington,+DC+20001&amp;ie=UTF8&amp;oe=utf-8&amp;client=firefox-a&amp;z=16&amp;g=901+G+Street,+NW+Washington,+DC+20001&amp;iwloc=r2%3E" rel="nofollow">Map</a></p> <p><strong>We will be in meeting room A-9. This is one floor down from the main entrance.</strong><br /> If you enter through the garage: go up the stairs to Level A and walk through two sets of double doors. A-9 will be in front of you to the right.<br /> If you enter from the main entrance: there is an elevator just inside the security to the right (under the Green MLK portrait). Take the elevator down to A. When you get off you are in a weird lobby area that opens onto A-2. Walk all the way through A-2 and out the other door. A-9 will be on your right.</p> <div class="og_rss_groups"><a href="/philadelphia-area">Philadelphia Area</a></div> http://groups.drupal.org/node/16174#comments Sprint Documentation Team Maryland Washington, DC Drupalers Northern VA Users Group Philadelphia Area Thu, 06 Nov 2008 17:16:29 +0000 add1sun 16174 at http://groups.drupal.org http://groups.drupal.org/node/16343 <p>Our next IRC meeting will be on Friday, November 7 at Noon EST (17:00 GMT, 9 a.m. PST). We will meet in the #drupal-docs channel on the FreeNode network for one hour.</p> <p>Agenda:<br /> - Announcements<br /> - Discuss the open editing experience. Is it working, should we continue? Thoughts, improvements? (Update: there is a thread, <a href="http://lists.drupal.org/pipermail/documentation/2008-November/006351.html" rel="nofollow">Open editing/limiting creation?</a> I started on the list related to this)<br /> - Catch up on the D.o Redesign and how it is effecting docs (<a href="http://groups.drupal.org/node/16548" rel="nofollow">Iteration 7</a> is up and we have a <a href="http://groups.drupal.org/node/15965" rel="nofollow">good thread on docs</a> going)<br /> - Discuss next projects (Getting Started guide, <a href="http://drupal.org/node/254947" rel="nofollow">reorg the theme guides</a>)</p> <p>Feel free to add to the agenda and discuss open editing prior to the meeting on the docs mail list. </p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Meeting Documentation Team Thu, 30 Oct 2008 14:22:08 +0000 add1sun 16343 at http://groups.drupal.org http://groups.drupal.org/node/16175 <p>Well, we have had open editing for a week now and so far so good as I<br /> have been watching. We should meet to talk about how our trial is<br /> going and whether we want to continue to keep it open or close back<br /> up. We can also talk about the state of the redesign. If you have<br /> other agenda items, feel free to add.</p> <p>Here is the doodle to schedule the meeting: <a href="http://www.doodle.com/667xykvs65hhyh5z" title="http://www.doodle.com/667xykvs65hhyh5z">http://www.doodle.com/667xykvs65hhyh5z</a></p> <p>Please add your preference to the Doodle by Thursday, October 30. We will meet for one hour in the #drupal-docs IRC channel, as usual.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> http://groups.drupal.org/node/16175#comments Documentation Team Fri, 24 Oct 2008 18:51:22 +0000 add1sun 16175 at http://groups.drupal.org http://groups.drupal.org/node/15965 <p>The redesign has been doing lots of great stuff, rethinking how we approach Drupal.org. We should take this opportunity to really think about how we present documentation on the site. There has been a lot of talk and there are lots of little nits of annoyance in addition to the larger complaint of organization with regard to the handbooks. I wanted to try to gather up at least some of the larger things for us to consider and continue the discussion so that we can focus on specific changes while we have the services of MBD available to us. MBD has put up a new <a href="http://drupal.markboultondesign.com/iteration4/index.html" rel="nofollow">prototype iteration</a> that is now beginning to address the documentation section. This is the perfect time for us to organize our thoughts and give feedback to craft a better solution.</p> <p>There is an older discussion that was started earlier this year about a <a href="http://groups.drupal.org/node/10223" rel="nofollow">Drupal Knowledge Base</a>, which was a doc-specific spin off of ideas from an original <a hrf="http://groups.drupal.org/node/10003" rel="nofollow">high level redesign post</a>. Incorporating some of the thoughts from that, as well as other discussions on the mailing list and in the issue queues, here is a (I'm sure incomplete) summary of "big" things I think we should address during this redesign. I encourage everyone to not just talk about this, but to actually make some <a href="http://www.disambiguity.com/drupalorg-come-wireframe-with-me/" rel="nofollow">quick wireframes</a> to help everyone see it.</p> <ul> <li> <p>Overall architecture of the handbooks:<br /> Everyone has different ways they expect to find the information they need. The documentation comprises of several different "books." What content belongs in which book is one issue, but also pulling back a bit and looking at what we are using as top-level books to compartmentalize our content needs to be looked at. Do we have too many separate books? Not enough? Should we be grouping things together differently? In particular a book like "<a href="http://drupal.org/handbook/customization" rel="nofollow">Beyond the basics</a>" is really more of just a catchall bin and rather vague.</p> </li> <li> <p>Versions<br /> Much of Drupal's documentation is written to the version of Drupal software (and we currently mark the version(s) with a vocabulary). Many pages apply to more than one version, some pages apply to all or no versions. It would be great to be able to look at the Drupal 5 version of the handbook and cut out the clutter and noise of other versions. It is a <em>lot</em> harder than it sounds. Much of this is a technical problem to solve but what would an ideal, or even achievable ;-), design for this look like? What would we even shoot for &gt;? Something like the API version tabs? What do we do about pages that need no version at all? This is a really hard problem but if we can find a solution that even moves us in that direction, it could be a huge boost to make it easier for people to find the info they need.</p> </li> <li> <p>Taxonomy/Tagging<br /> We currently have two vocabularies for handbook pages: Drupal version and a new page status. These act as "flags" but do not really help us organize our content, nor make any easier to find what you need. How can we think about using taxonomy to improve this? People want to find info in different ways at different times. Tagging our content to give people more "meta" info could help people track down and group the information they need. Again, how does this look? How would this most help us?</p> </li> <li> <p>Videos<br /> We currently have a video section of the handbooks (under Beyond the basics) but as video becomes more and more popular, I think we need to look at how to really effectively address these informational videos. Where should they be? How best to organize them? How do we make them easy to find and view while also linking them up with the appropriate written parts of the handbook? There is a <a href="http://groups.drupal.org/node/9643" rel="nofollow">thread on video ideas</a> that can be looked where some of these things are discussed. We should also note that the Dojo will be <a href="http://groups.drupal.org/node/15832" rel="nofollow">reviving their external site</a> as a simple way to host videos. I think we should work with and think about this as a prototype for what we can do within the Drupal.org handbooks for videos.</p> </li> </ul> <div class="og_rss_groups"><a href="/drupalorg-redesign-plan-drupal-association">Drupal.org redesign plan for the Drupal Association</a></div> http://groups.drupal.org/node/15965#comments Documentation Team Drupal.org redesign plan for the Drupal Association Fri, 17 Oct 2008 14:24:25 +0000 add1sun 15965 at http://groups.drupal.org http://groups.drupal.org/node/15796 <p>Here is a brief summary of the IRC meeting held Friday, October 10. The IRC log can be read here: <a href="http://pastebin.com/f575075de" title="http://pastebin.com/f575075de">http://pastebin.com/f575075de</a>. I had to leave the meeting early due to an unplanned meeting that came up, for which I apologize, and thanks to everyone that kept the meeting running. :-)</p> <p>Announcements:<br /> - Our group page has tabs for things like projects and issues now<br /> - We now have a page status vocab on book pages pursuant to this issue: <a href="http://drupal.org/node/304826" title="http://drupal.org/node/304826">http://drupal.org/node/304826</a>. The issue is still open because we need to document these changes so feel free to dive in and help with that so we can close that up.<br /> - I've been asked to to a Docs presentation at DrupalCon so we tossed out a few topics: general state of documentation, the team, a report on what happened when we opened up the editing and the impact of the d.o redesign on docs.<br /> - The Redesign prototypes are up, <a href="http://groups.drupal.org/node/15512" title="http://groups.drupal.org/node/15512">http://groups.drupal.org/node/15512</a>, so please take a look and give feedback. Nothing on the docs section just yet.</p> <p><strong>AGENDA</strong><br /> Getting Involved:<br /> The <a href="http://drupal.org/getting-involved" rel="nofollow">new book</a> is now live but we still have some <a>work to do</a>. Let's clean up at least the landing pages that need to be fleshed out so we can close the issues and consider <a href="http://groups.drupal.org/node/15415" rel="nofollow">the project</a> "done." The continued betterment of the book will fall under regular handbook work like the others.</p> <p>Open edit rights:<br /> We have an issue in the webmasters queue to open the rights up: <a href="http://drupal.org/node/310912" title="http://drupal.org/node/310912">http://drupal.org/node/310912</a>. We just need to do a few tasks before flipping the switch. The first was to set a date. We decided that we will shoot for <strong>October 15</strong> to open the rights, which means the one month trial period will end <strong>November 15</strong>. At that point we will asses how things are going and whether we want to extend the period of close editing back up again.</p> <p>In preparation for the switch we also need to:<br /> 1. Figure out which pages to restrict. A discussion was started on the <a href="http://lists.drupal.org/pipermail/documentation/2008-September/006299.html" rel="nofollow">mail list</a>, then during the meeting a <a href="http://groups.drupal.org/node/15779" rel="nofollow">page on the group site</a> was created, which was then moved to <a href="http://drupal.org/node/319685" rel="nofollow">a handbook page</a> so that everyone on the team can edit it and we point users to that pages for a list of the ones that are <em>not</em> editable by regular auth users.<br /> 2. Go through and change the input format to "Documentation" on pages we want to "lock"<br /> 3. Write an announcement to post to the front page on d.o</p> <p>We agreed that we should gather up the list of pages (for #1) by Monday, Oct. 13 so that we have 2 days to lock. If anyone would like to start writing a draft for the front page announcement, feel free to write a draft and attach it to the <a href="http://drupal.org/node/310912" rel="nofollow">main webmaster issue</a>.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Minutes Documentation Team Sat, 11 Oct 2008 14:47:46 +0000 add1sun 15796 at http://groups.drupal.org http://groups.drupal.org/node/15779 <p>We have decided to open up editing rights for all users for a one month trial period. (See the <a href="http://lists.drupal.org/pipermail/documentation/2008-September/006248.html" rel="nofollow">mail list discussion summary</a>.) We opened up permissions on October 15 and have decided to let them remain open. We will announce the continuation on our November 15 deadline. We have created a <a href="http://drupal.org/node/319685" rel="nofollow">list of "locked" pages</a> and two related issues have been completed: requiring the log message and adding a diff link to the <a href="http://drupal.org/handbook/updates" rel="nofollow">Recent updates</a> page.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Project - closed Documentation Team Fri, 10 Oct 2008 16:39:04 +0000 JBrauer 15779 at http://groups.drupal.org http://groups.drupal.org/node/15515 <p>The next Documentation IRC meeting will be on October 10th, 2008 in the #drupal-docs IRC channel (on the freenode network) beginning at 16:00 GMT and lasting for one hour. The agenda will be:</p> <ol> <li>Wrap up discussion on the Getting Involved handbook. We will touch on important remaining items, if there are any. Feel free to keep working on it in the meantime: <a href="http://groups.drupal.org/node/15415" title="http://groups.drupal.org/node/15415">http://groups.drupal.org/node/15415</a> ;-)</li> <li>Talk about opening the editing rights up. Two helper issues we wanted are now done and so we need to just get our ducks in a row before we flip the switch. We can talk about what ducks need ordering, what the change entails for the team and set a firm date.</li> </ol> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Meeting Documentation Team Thu, 02 Oct 2008 16:36:29 +0000 add1sun 15515 at http://groups.drupal.org http://groups.drupal.org/node/15420 <p>This is a list of important issues in the Documentation issue queue and non-core queues.</p> <ul> <li><a href="http://drupal.org/project/issues?projects=18753&amp;text=Getting%20Involved:&amp;states=1,16,8,13,14,15,2,4" rel="nofollow">All Getting Involved handbook issues</a></li> <li><a href="http://drupal.org/node/317657" rel="nofollow">Standardized CSS for handbook pages</a> (Webmasters)</li> <li><a href="http://drupal.org/node/307650" rel="nofollow">Delay edit/create perms for new users</a> (Webmasters)</li> <li><a href="http://drupal.org/node/282399" rel="nofollow">Statistics on Book contributors and Our editors pages are way out!</a> (Drupal.org customizations)</li> <li><a href="http://drupal.org/node/337134" rel="nofollow">Put new pages by regular users in a "holding book"</a> (Drupal.org customizations)</li> </ul> <p>These two issues/patches need to be made into one patch that does not conflict:<br /> - <a href="http://drupal.org/node/322828" rel="nofollow">Provide feed of recently updated handbook pages</a> (Drupal.org customizations)<br /> - <a href="http://drupal.org/node/325780" rel="nofollow">Add a pager to the Handbook Update page </a>(Drupal.org customizations)</p> <p><strong>Module issue queues</strong><br /> These are modules that the Doc team is interested in testing for use on Drupal.org. The modules need to be solid and secure before being presented for D.o review, so fixing bugs and conducting overall code, security and performance reviews are useful to move them forward.</p> <ul> <li><a href="http://drupal.org/project/issues/term_message" rel="nofollow">Term Message</a> (This is needed to move <a href="http://drupal.org/node/313439" rel="nofollow">Add highlight message on book pages based on taxonomy</a> forward.)</li> <li><a href="http://drupal.org/project/issues/book_access" rel="nofollow">Book access</a> (To give docs team more control over create, edit, delete rights per book.)</li> </ul> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Documentation Team Mon, 29 Sep 2008 23:04:35 +0000 add1sun 15420 at http://groups.drupal.org http://groups.drupal.org/node/15418 <p>Now that the Getting Involved book is started up, I wanted to set up a time for the next IRC meeting. Our IRC meetings are held in the #drupal-docs channel on the Freenode netwrok and last one hour. Let' s shoot for something next week with the top agenda items being:</p> <ol> <li>Wrap up discussion on Getting Involved. I hope we get a fair bit of cleanup done during this week but we should touch on important remaining items, if there are any.</li> <li>Talk about opening the editing rights up. Two helper issues we wanted are now done and so we need to just get our ducks in a row before we flip the switch. We can talk about what ducks need ordering, what the change entails for the team and set a firm date.</li> </ol> <p>Here is ye old doodle to pick a time: <a href="http://www.doodle.ch/2rgcqb6tmmik2yck" title="http://www.doodle.ch/2rgcqb6tmmik2yck">http://www.doodle.ch/2rgcqb6tmmik2yck</a> Please voice your preference by Thursday, October 4.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> http://groups.drupal.org/node/15418#comments Announcement Documentation Team Mon, 29 Sep 2008 23:00:27 +0000 add1sun 15418 at http://groups.drupal.org http://groups.drupal.org/node/15415 <p>The Getting Involved handbook project has been in the works since March 2008. For background on this project, read the <a href="http://drupal.org/node/313366" rel="nofollow">Drupal.org front page post</a>.</p> <p>The current status is that we have done the initial creation of the book and added it to the Documentation landing page (as of September 28, 2008). It can be found at <a href="http://drupal.org/getting-involved" title="http://drupal.org/getting-involved">http://drupal.org/getting-involved</a>. Now that the book is created we need to finish it up. Currently the landing page has a list of high-priority issues to finish. You can also see the remaining issues in this <a href="http://drupal.org/project/issues?projects=18753&amp;text=Getting%20Involved:&amp;states=1,16,8,13,14,15,2,4" rel="nofollow">issue queue search</a>.</p> <p>Beyond finishing the specific issues (which mostly involves finishing a few incomplete pages), we also need folks to read through the book and identify places that don't feel like they are in a good order or where the information doesn't make sense. We also need to think of things that are missing and should be added to help people get involved in many ways. If you find problems or have questions, feel free to create a new issue in the <a href="http://drupal.org/project/issues/documentation" rel="nofollow">Documentation issue queue</a> and/or just jump in and start editing.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Project - open Documentation Team Mon, 29 Sep 2008 22:51:16 +0000 add1sun 15415 at http://groups.drupal.org http://groups.drupal.org/node/15366 <p>These patches affect Drupal's documentation, or affect Drupal's documentation team. Looking for reviews and help from people with this itch to scratch. Feel free to add your own!</p> <ul> <li><a href="http://drupal.org/node/299050" rel="nofollow">Revamped Help System</a></li> <li><a href="http://drupal.org/node/308352" rel="nofollow">Allow revision log messages to be required</a></li> <li><a href="http://drupal.org/node/100680" rel="nofollow">A modern solution for the FAPI reference and similar array based systems.</a></li> <li><a href="http://drupal.org/node/314870" rel="nofollow">Add a hook.module to core</a></li> </ul> <p>See also: <a href="http://drupal.org/project/issues?projects=3060&amp;versions=156281&amp;components=book.module,documentation,user%20interface%20text" rel="nofollow">All documentation-related patches</a></p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Patch Spotlight Improvements to core Documentation Team Sat, 27 Sep 2008 00:29:16 +0000 webchick 15366 at http://groups.drupal.org http://groups.drupal.org/node/15133 <p>During the sprint window whoever happens to have a few free moments can stop by #drupal-docs IRC channel (on the Freenode network) and help out with preparing the <a href="http://drupal.org/node/293455" rel="nofollow">Getting Involved handbook</a> for launch. There will be someone around during the entire time to answer questions, give direction and help newbies out on work to be done, so if you have a spare 15 minutes, roll on by and be part of the process. Newbies are encouraged!</p> <p>(Note, there are two sprints planned, one on Tues. Sept. 23 and another on Thurs. Sept 25.)</p> <p><strong>Specific tasks we need to do during this sprint:</strong><br /> - Review the getting an account page: <a href="http://drupal.org/node/240235" title="http://drupal.org/node/240235">http://drupal.org/node/240235</a> and see if it has everything we need, then report back either "looks good" or "we could improve..." to the issue.<br /> - Look over issues at <a href="http://drupal.org/project/issues?projects=18753&amp;text=Contrib%20Redesign:" title="http://drupal.org/project/issues?projects=18753&amp;text=Contrib%20Redesign:">http://drupal.org/project/issues?projects=18753&amp;text=Contrib%20Redesign:</a> that are marked "patch (code needs review)" and see if there is more to add. Leave comments on the issue if you have other pages to add, thoughts on what should be there or if you think it is OK.<br /> - Should we include this section at all? <a href="http://drupal.org/node/240264" title="http://drupal.org/node/240264">http://drupal.org/node/240264</a>, please post thoughts/ideas to the issue.<br /> - Anyone interested in working on the CVS sections please ping add1sun in IRC - they are kind of gnarly and need work.<br /> - Start the d.o front page post to tell everyone about the new book and warn them that the handbook will be shifting around this weekend.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Sprint Documentation Team Sun, 21 Sep 2008 21:51:33 +0000 add1sun 15133 at http://groups.drupal.org http://groups.drupal.org/node/15132 <p>During the sprint window whoever happens to have a few free moments can stop by #drupal-docs IRC channel (on the Freenode network) and help out with preparing the <a href="http://drupal.org/node/293455" rel="nofollow">Getting Involved handbook</a> for launch. There will be someone around during the entire time to answer questions, give direction and help newbies out on work to be done, so if you have a spare 15 minutes, roll on by and be part of the process. Newbies are encouraged!</p> <p>(Note, there are two sprints planned, one on Tues. Sept. 23 and another on Thurs. Sept 25.)</p> <p>What'll we be doing?<br /> - Working on completing the "<a href="http://drupal.org/project/issues?projects=18753&amp;text=Contrib%20Redesign:" rel="nofollow">section issues</a>" to find all of the existing pages that need to be moved into the new book. This mostly involves checking out the handbook looking for certain kinds of pages and then reporting back where (or if) you found them.<br /> - If we find multiple pages on the same topic, work on merging them into one page.<br /> - Identifying what is missing and creating new pages, even if they are only stub pages for the time being.<br /> - Write up a draft and help edit the front page announcement about the book.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Sprint Documentation Team Sun, 21 Sep 2008 21:36:57 +0000 add1sun 15132 at http://groups.drupal.org http://groups.drupal.org/node/14932 <p>The new <a href="http://drupal.org/node/293455" rel="nofollow">Getting involved handbook</a> needs some focused attention to get it going. I'd like to create the book and announce it to the larger community by Sept. 28. During the last IRC meeting we thought that maybe a few short virtual sprints focused just on this task might help since many folks aren't quite sure what needs to be done, or just have a hard time setting time aside for it.</p> <p>I've set up a (large) Doodle at <a href="http://www.doodle.ch/participation.html?pollId=weeh8anybfx9fe54" title="http://www.doodle.ch/participation.html?pollId=weeh8anybfx9fe54">http://www.doodle.ch/participation.html?pollId=weeh8anybfx9fe54</a> for folks to indicate times next week that would be good. We'll schedule it out to overlap with as many people's schedules as we can. I'll post the sprint schedule on this list and on g.d.o on September 20. Keep in mind that the sprint times will be broad (2+ hours each) but that each person can show up for whatever time they happen to have available in the window; be it 15 minutes or 2 hours.</p> <p>CROSS-POSTED FROM DOCS MAIL LIST.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Documentation Team Tue, 16 Sep 2008 13:50:14 +0000 add1sun 14932 at http://groups.drupal.org http://groups.drupal.org/node/14903 <p>This is a copy of the summary email for the <a href="http://groups.drupal.org/node/14570" rel="nofollow">Sept 14 IRC meeting</a>, sent out to the Documentation mail list at <a href="http://lists.drupal.org/pipermail/documentation/2008-September/006273.html" title="http://lists.drupal.org/pipermail/documentation/2008-September/006273.html">http://lists.drupal.org/pipermail/documentation/2008-September/006273.ht...</a></p> <p>Here is the IRC log from the meeting: <a href="http://pastebin.com/f183bcc8d" title="http://pastebin.com/f183bcc8d">http://pastebin.com/f183bcc8d</a></p> <p>We had several announcements at the beginning of the meeting and then we hit the two agenda items. As usual if I missed anything in here or others have feedback/thoughts, feel free to add to this summary. Thanks to all who attended.</p> <h2>ANNOUNCEMENTS</h2> </p> <p>New read-only group page: <a href="http://groups.drupal.org/documentation-team" title="http://groups.drupal.org/documentation-team">http://groups.drupal.org/documentation-team</a><br /> KDI proposal for doc sprints: <a href="http://groups.drupal.org/node/14669" title="http://groups.drupal.org/node/14669">http://groups.drupal.org/node/14669</a><br /> The d.o redesign underway: <a href="http://groups.drupal.org/drupal-org-redesign-analysis" title="http://groups.drupal.org/drupal-org-redesign-analysis">http://groups.drupal.org/drupal-org-redesign-analysis</a><br /> - Ways to help out with the redesign: <a href="http://groups.drupal.org/node/14643" title="http://groups.drupal.org/node/14643">http://groups.drupal.org/node/14643</a><br /> - D.o Wireframe game: <a href="http://www.disambiguity.com/drupalorg-come-wireframe-with-me/" title="http://www.disambiguity.com/drupalorg-come-wireframe-with-me/">http://www.disambiguity.com/drupalorg-come-wireframe-with-me/</a><br /> Webchick wants feedback on the D7 help text system. She'll be posting to the list soon with more details, but one issue to jump in on is at <a href="http://drupal.org/node/299050" title="http://drupal.org/node/299050">http://drupal.org/node/299050</a></p> <h2>AGENDA</h2> <h3>Getting involved handbook</h3> <p>The Getting involved book needs to get pushed over the finish line. We need to flech out the issues for it. Many people are unsure of exactly what to do, so we decided that having a few short virtual sprints specifically focused on the Getting involved book would help. We will be scheduling those later this week. The goal is to officially create the new book and announce it to the community by Sept 28.</p> <p>A discussion that arose from this was how difficult it is to keep track of all of the projects and dates for doc team work. We agreed that getting a more streamlined and public way of our ongoing work and meetings would be desired. We will create a small "working group" of folks interested in sorting that out and implementing. emmajane has started a thread for that.</p> <h3>Opening editing rights to auth. users</h3> <p>The majority decision on this point is to open the editing rights to all auth users for a one month test period. There are a few things we would like in place prior to doing that, namely getting Moshe's path linking to diffs from the Latest updates page and requiring the revision log to be filled out when editing. We also looked at an issue on the idea of having a delay period for new users <a href="http://drupal.org/node/307650" title="http://drupal.org/node/307650">http://drupal.org/node/307650</a>, though this will take a while to implement and so won't happen before the initial trial. Anyone interested in this feature should chime in on the thread so we can nail down a direction and work on the code to make it happen on d.o. The biggest thing that needs to happen now is getting the infra team on board to implement the change.</p> <h2>NEXT STEPS</h2> <p>Getting involved (GI):<br /> - Get GI issues filled out: <a href="http://drupal.org/project/issues?projects=18753&amp;text=Contrib%20Redesign:" title="http://drupal.org/project/issues?projects=18753&amp;text=Contrib%20Redesign:">http://drupal.org/project/issues?projects=18753&amp;text=Contrib%20Redesign:</a><br /> - Set new docs vocab: <a href="http://drupal.org/node/304826" title="http://drupal.org/node/304826">http://drupal.org/node/304826</a><br /> - Do some GI sprints: I'll send a followup email out re: sprint scheduling<br /> - Post to d.o front page re: handbook reorg: We can write this up once we get closer</p> <p>Opening edit rights:<br /> - Check with infra about the next steps to implement: I'll do that this week<br /> - Get recent updates patch going: <a href="http://drupal.org/node/304667" title="http://drupal.org/node/304667">http://drupal.org/node/304667</a> (need to check with Moshe on this)<br /> - Get required revision log patch done: <a href="http://drupal.org/node/308675" title="http://drupal.org/node/308675">http://drupal.org/node/308675</a><br /> - Write up an announcement for d.o front page</p> <p>New tasks:<br /> mechfish created an issue for a Recent updates RSS feed: <a href="http://drupal.org/node/308354" title="http://drupal.org/node/308354">http://drupal.org/node/308354</a><br /> emmajane has started a thread about schedule/calendar issues: <a href="http://lists.drupal.org/pipermail/documentation/2008-September/006267.html" title="http://lists.drupal.org/pipermail/documentation/2008-September/006267.html">http://lists.drupal.org/pipermail/documentation/2008-September/006267.ht...</a></p> <ul> <li>Addi (add1sun)</li> </ul> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Minutes Documentation Team Mon, 15 Sep 2008 19:55:38 +0000 add1sun 14903 at http://groups.drupal.org http://groups.drupal.org/node/14730 <p>There is a discussion currently happening on the docs mailing list about potentially opening up editing rights for all authenticated users. The discussion has been happening for about two weeks now and there is a <a href="http://lists.drupal.org/pipermail/documentation/2008-September/006248.html" rel="nofollow">summary post</a> that distills the conversation and outlines next steps. Please feel free to join the conversation on the mail list or come to the <a href="http://groups.drupal.org/node/14570" rel="nofollow">next IRC meeting</a>.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Documentation Team Wed, 10 Sep 2008 14:30:41 +0000 add1sun 14730 at http://groups.drupal.org http://groups.drupal.org/node/14669 <p><strong>Edit, October 2 -- This proposal has been passed along to the Knight Foundation for consideration -- <a href="http://drupal.org/node/316402" title="http://drupal.org/node/316402">http://drupal.org/node/316402</a>. End Edit</strong></p> <p>This proposal is to request funding to improve Drupal's documentation by conducting documentation-specific sprints. There are two major components to this project:<br /> 1) Tackle big Documentation team issues: Gather key people to work on specific documentation issues that will further the goals of the Documentation team, the handbooks on Drupal.org and documentation that ships with the Drupal code.<br /> 2) Grow the Documentation team: Conduct community sprints at Drupal group gatherings to grow the Documentation team and teach people how to contribute to documentation, including how to conduct their own sprints. Think of it as viral documentation love in addition to actually getting work done.</p> <p>In conducting the documentation sprints at both DrupalCon Boston and DrupalCon Szeged, I've learned a few things that I think are very important. Firstly, having people int he same location working on the same goal can create incredible results in terms of work accomplished. Beyond that, the feeling of comradery and unification lingers long after the physical event. I've also found that many people who have attended the sprints have been interested in helping but were hesitant to jump in by themselves. Having a group of people there to personally walk them through the steps and answer questions real time lowers the barrier enough that not only do people finally engage but they also gain enough confidence to continue the work on their own once the sprint is over. Also, through leading these sprints I am beginning to get a much better sense of what is involved to create a successful sprint. Success being measured by the amount of work accomplished, as well as the number of new seeds planted for future growth.</p> <p>Besides, the normal day-to-day monumental task of maintaining Drupal documentation, there are specific issues which can put the entire team into a holding pattern indefinitely. Some of these have to do with infrastructure and technical issues. Some simply have to do with having a larger goal defined and a sense of authority to enact it. Often, there is simply a lack of time and focus available for key people to sit down, figure things out and push them out the door. One very specific arena where this will be very important in the near future is the direction and implementation of the Drupal.org redesign as it applies to the Drupal.org handbooks. The handbooks are a major component of Drupal.org and making them easy to use for all levels of users is a high priority for the redesign.</p> <p>In addition to the Drupal.org handbooks, we would also like to shore up and improve the documentation that ships with the Drupal code base so that users who do not have access to the handbooks online will still have a reasonable guide to get them up and running with Drupal. Finding the best way to implement a real change in this direction will require serious discussion with key people in various areas of the Drupal community.</p> <p>The specific road map to address the two major goals of this proposal is as follows:</p> <h2>Invitation Sprints</h2> <p>Invitation sprints are very focused sprints of up to 8 people that are specifically invited for the task at hand. Each sprint would be two days long and the location would be determined by cities closest to the largest number of attendees and availability of space in a venue (e.g. a hotel meeting room or maybe donated space, if possible). There are two invitation sprints that would be the focus of this proposal:</p> <h3>Planning, road map, specs</h3> <p>This sprint would be the first one and would include key community members that have an interest in and experience with documentation. The focus would be to determine a prioritization of goals and a road map for how to achieve them, including specifications for code help, as needed. This would address both the Drupal.org handbooks and documentation included in Drupal's code base as well.</p> <h3>Code</h3> <p>Once needs are identified and we have specifications for what we want, we would have a code sprint where coders with the background and interest to help documentation can gather and actually produce the needed code. Doing this at a sprint allows focused time and immediate testing and feedback. The code produced could be for both core and contrib, depending on the needs identified and the best way to achieve them.</p> <h2>Community Sprints</h2> <p>Community sprints would involve organizing community documentation sprints during local DrupalCamps around the world. Since the camps will already be doing the organizational work and gathering large groups of attendees, there would be no overhead to running the sprints other than logistics to get there. These are designed to be very similar to the DrupalCon doc sprints by getting people to join the docs team and being focused on general documentation tasks. These would also teach people how to run their own local sprints at regular meetups and train people who would like to be regional sprint organizers.</p> <p>I would attend the camp and arrange with the camp leaders to have a doc sprint track running for the entire camp (if feasible), which I would be responsible for running. My personal time would be donated and the funding requested would cover the logistical needs of travel, room and board. These would be spread out around the world and are dependent on locations that conduct DrupalCamps in the next year, so there are no specific locations determined yet. That said, I would like to conduct the following by region:</p> <p>3 North American sprints<br /> 2 European sprints<br /> 1 Asia/Pacific sprint</p> <p>In addition to physically going to large events I also want to organize a way for me to appear virtually at smaller events (local meetups, small camps) so that I can be a resource online for the organizers on the ground. This would not require funding in this proposal, but is added for completeness.</p> <ul> <li>As a note about sprints at <em>DrupalCons</em>, I will still be doing that as well but I am not asking for funding for those in this proposal because I will not be focused solely on doc sprinting at Cons.</li> </ul> <h3>Sprint Documentation</h3> <p>A solid set of documentation (written and video) would be created to guide others in their own sprints; be they two people just meeting up to work on docs, to local meetups that want to have a sprint night, to running larger regional sprints at camps and conferences. The initial set of documentation and material would encompass not just information related to organizing sprints but also more generic info about the Documentation team, including policies and road maps, how to get involved, written and video instructions for tasks, etc. Everything written and created would be available in the Drupal.org handbook including materials like videos and PDFs.</p> <p>One week (40 hours) of solid time would be invested in creating the documentation and materials early on, which would then be systematically refined in response to implementation at the sprints themselves. Another 40 hours spread over the following year would be spent on this refinement and creating additional materials.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> http://groups.drupal.org/node/14669#comments proposals Knight Drupal Initiative Documentation Team Mon, 08 Sep 2008 19:13:13 +0000 add1sun 14669 at http://groups.drupal.org http://groups.drupal.org/node/14570 <p>Pursuant to the <a href="http://www.doodle.ch/7dx3823d582rxgsk" rel="nofollow">latest scheduling Doodle</a> we will be having a team IRC meeting on the FreeNode network #drupal-docs channel on Sept. 14 at 17:00 GMT (1pm EDT, 10am PDT). the meeting will go for one hour.</p> <p>The current agenda items:<br /> * The Getting involved handbook: <a href="http://groups.drupal.org/node/14517" title="http://groups.drupal.org/node/14517">http://groups.drupal.org/node/14517</a><br /> * Opening editing rights to all auth users: <a href="http://lists.drupal.org/pipermail/documentation/2008-August/006191.html" title="http://lists.drupal.org/pipermail/documentation/2008-August/006191.html">http://lists.drupal.org/pipermail/documentation/2008-August/006191.html</a></p> <p><a href="http://groups.drupal.org/node/14903" rel="nofollow">Summary and logs posted here</a></p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Meeting Documentation Team Thu, 04 Sep 2008 16:04:45 +0000 add1sun 14570 at http://groups.drupal.org http://groups.drupal.org/node/14517 <p>We have announced a new handbook that will be added to the main Drupal Documentation landing page: Getting involved. Read more about it and how you can help at <a href="http://drupal.org/node/293455" title="http://drupal.org/node/293455">http://drupal.org/node/293455</a>.</p> <div class="og_rss_groups"><a href="/documentation-team">Documentation Team</a></div> Documentation Team Wed, 03 Sep 2008 11:10:18 +0000 add1sun 14517 at http://groups.drupal.org