<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Sorry for the delay. Had one more quick chat with Angie and I agree with John, that this isn't really "documentation." So, we'll leave Community Initiatives as a top-level book and link to it where appropriate. It is already has an alias (<a href="http://drupal.org/community-initiatives">http://drupal.org/community-initiatives</a>) and is linked from Getting Involved landing page. I have reopened an issue and attached a new patch to remove the patch spotlight and add the CI link to the block (<a href="http://drupal.org/node/341070#comment-1230034">http://drupal.org/node/341070#comment-1230034</a>). Feel free to sprinkle liberally where it makes sense.<br><br>I'll start setting up the Documentation projects section this weekend and we can remove the tabs from the OG (which no one ever sees or uses anyway).<br><br>Thanks to all the ideas and discussion.<br>- Addi<div><br></div><div><br><div><div>On Jan 21, 2009, at 10:00 PM, John Noceda wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Creating a top-level book does not mean that it has to become a handbook. So<br>my suggestion is, even if we're utilizing the book content type, we do not<br>call this a handbook and not list it on <a href="http://drupal.org/handbooks">http://drupal.org/handbooks</a>. We<br>instead make a link on the "Contributor Links" block called "Community<br>Initiatives" right after the "Advanced Search" and before the "Queue". Then<br>it becomes a project management tool related to the issues queue and not<br>related to documentation. The documentation blocks: "Quick Links" and<br>"Handbook License" shouldn't be visible on this top-level book. We then<br>announce the new functionality on the front page. The documentation<br>admins/managers (or whatever name we decide on this on another on-going<br>discussion) will then make it a task to explain the "Community Inititiative"<br>feature in the "Getting Involved" handbook.<br><br>IMHO, this put things in proper places. Listing it under the "Contributor<br>Links" block makes it more visible to the correct target audience as well as<br>it gives the impression of a better connection with the issues queue. My<br>point is that it's a project management tool and not documentation.<br><br><br>John<br><br><br>-----Original Message-----<br>From: <a href="mailto:documentation-bounces@drupal.org">documentation-bounces@drupal.org</a><br>[<a href="mailto:documentation-bounces@drupal.org">mailto:documentation-bounces@drupal.org</a>] On Behalf Of Gábor Hojtsy<br>Sent: 21. januar 2009 17:39<br>To: A list for documentation writers<br>Subject: Re: [documentation] New handbook section proposal: "Community<br>Initiatives"<br><br>On Wed, Jan 21, 2009 at 5:28 PM, Addison Berry <<a href="mailto:drupal@rocktreesky.com">drupal@rocktreesky.com</a>><br>wrote:<br><blockquote type="cite"><blockquote type="cite">It almost sounds like this should be a view rather than just books <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">hierarchy, since it could include time-frame-limited things, etc.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Maybe it is a "dashboard" of embedded views of 2 or 3 different kinds <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">things? It just seems like something requiring more relational <br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">connections rather than hierarchical burying.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Yeah, I agree that figuring views into this would be nice and I still <br></blockquote><blockquote type="cite">think that we need to take a real look at an "ideal" long-term <br></blockquote><blockquote type="cite">solution. We also need to find a short-term solution that does *not* <br></blockquote><blockquote type="cite">involve views though. We do not have Views enabled on d.o and it will <br></blockquote><blockquote type="cite">not be until after the upgrade/redesign stuff, but Angie is in need of <br></blockquote><blockquote type="cite">some sort of overarching way to organize things *now* and this seemed <br></blockquote><blockquote type="cite">the handiest way to go. I did also raise the fact that we now have <br></blockquote><blockquote type="cite">tags and wouldn't using the taxo lists for tags be one way to go, but <br></blockquote><blockquote type="cite">Angie didn't like it because she wants to highlight only the <br></blockquote><blockquote type="cite">"important" stuff.<br></blockquote><br>We got to same / similar conclusions with the redesign / upgrade project<br>planning. We can tag stuff, but in huge projects, such as these, we need a<br>hierarchic, prioritized plan for what should happen.<br>Therefore I've extended the drupal.org project filter, so if you use<br>[#112233] (with the issue number), you'll get the status and the assigned<br>user to the output already. From here, we can use this to build nested lists<br>with annotations, images, etc for bigger project plans. This is all due to<br>our project module lacking things like milestones, relative priority,<br>project plans, etc, and they will not be implemented anytime soon (not that<br>they should be). Flat views listing is not cutting it, since you cannot<br>order stuff by relative priority (eg. an issue might be an important thing<br>for implementing the map on the redesigned homepage, but the map on the<br>redesigned homepage is not the highest priority overall). Tags don't provide<br>a way for people to understand the process of implementing a big change in<br>Drupal or on drupal.org, the order of them, cross-dependencies, etc.<br><br>What we do because of the lack of higher project planning tools, milestones,<br>etc. is a bit hackish, but looks like we prefer to use drupal.org then to<br>use a third party, where these would be available, since here we can utilize<br>our userbase, issue status data, etc, which we already have.<br><br>Gábor<br>--<br>Pending work: <a href="http://drupal.org/project/issues/documentation/">http://drupal.org/project/issues/documentation/</a><br>List archives: <a href="http://lists.drupal.org/pipermail/documentation/">http://lists.drupal.org/pipermail/documentation/</a><br><br>--<br>Pending work: <a href="http://drupal.org/project/issues/documentation/">http://drupal.org/project/issues/documentation/</a><br>List archives: <a href="http://lists.drupal.org/pipermail/documentation/">http://lists.drupal.org/pipermail/documentation/</a><br></div></blockquote></div><br></div></body></html>