<br><br><div><span class="gmail_quote">On 8/8/07, <b class="gmail_sendername">Ben Feldman</b> <<a href="mailto:ben@go-floss.org">ben@go-floss.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"><br>
<br>
What do you guys think?</div></blockquote><div><br>I think all the documentation should be a wiki. Click here to edit. Give admins the ability to lock pages, were necessary.<br><br>The current status of having 50 comments on a page for something as critical how to upgrade your module to the next API version, is completely unacceptable. We are forcing companies and admins to spend collectively millions of dollars on upgrading their sites between versions with inconsistent and unclear documentation.
<br><br>Kieran<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div bgcolor="#ffffff" text="#000000"><blockquote type="cite"><div>
<span class="e" id="q_114465c10b95e26e_7"><div><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
Hope
this helps,</span></span></div>
<div><br>
</div>
<div><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
Dave.<br>
<div><br>
</div>
<div>------------------------</div>
<div>Dave Chakrabarti</div>
<div>Director of Programs</div>
<div><a href="http://Grassroots.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Grassroots.org</a></div>
<br>
</span></span> </div>
<br>
<div>
<div>On Aug 8, 2007, at 10:01 AM, Ben Feldman wrote:</div>
<br>
<blockquote type="cite"> Greg Knaddison - GVS wrote:<br>
<blockquote type="cite">
<blockquote type="cite">
<pre>Also, I think if a common user could flag a handbook as "needs updated",<br>it would come in use. Before I was a maintainer, I viewed handfuls of<br>handbook pages that needed updated, but I didn't know who to notify. It
<br>would be useful to have a link for "needs updated", or something<br>similar, so that maintainers could be notified. All flagged handbook<br>pages would be compiled into a page, sorted by number of flags.<br>
</pre>
</blockquote>
<pre>This sounds great to me as well. We have the "suggest documentation<br>improvements" link in the bottom of the left sidebar along with a<br>couple other things. I'd prefer seeing that in the content area just
<br>under each handbook page and above any comments. That's the place<br>where people will be thinking about it and might act on it. The<br>bottom of the left sidebar is a place where, even after viewing<br>hundreds of handbook pages, I didn't know it existed
</pre>
</blockquote>
I think this is an absolutely great idea! And while something similar
exists, I think the fact that it sends you to the issues page would
either be too confusing, or seems like too much work--like you'd have
to point out what needs to be updated and what it should be updated to,
if you know what I mean.<br>
<br>
How about this? There is a simple "Add page to update queue" link (with
better wording) at the location you noted, Greg, that when click
automatically adds an issue to our Issues page with simply a link to
the handbook page and a little text saying "such and such a user
submitted this handbook page for updates."<br>
<br>
I, too, would be more willing to act upon old information if this kind
of a system existed.<br>
<pre cols="72">-- <br>Ben Feldman<br>Director, Go FLOSS!<br><a href="mailto:ben@go-floss.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">ben@go-floss.org</a></pre>
<div style="margin: 0px;">--</div>
<div style="margin: 0px;">Pending work: <a href="http://drupal.org/project/issues/documentation/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/project/issues/documentation/
</a></div>
<div style="margin: 0px;">List archives: <a href="http://lists.drupal.org/pipermail/documentation/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.drupal.org/pipermail/documentation/
</a></div>
</blockquote>
</div>
<br>
</span></div><pre><hr size="4" width="90%"><span class="q"><br>--<br>Pending work: <a href="http://drupal.org/project/issues/documentation/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://drupal.org/project/issues/documentation/
</a><br>List archives: <a href="http://lists.drupal.org/pipermail/documentation/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.drupal.org/pipermail/documentation/</a></span></pre>
</blockquote><span class="q">
<br>
<pre cols="72">-- <br>Ben Feldman<br>Director, Go FLOSS!<br><a href="mailto:ben@go-floss.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">ben@go-floss.org</a></pre>
</span></div>
<br>--<br>Pending work: <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://drupal.org/project/issues/documentation/" target="_blank">http://drupal.org/project/issues/documentation/</a><br>List archives:
<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://lists.drupal.org/pipermail/documentation/" target="_blank">http://lists.drupal.org/pipermail/documentation/</a><br></blockquote></div><br><br clear="all">
<br>-- <br>To strive, to seek, to find, and not to yield.<br>