<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dave Chakrabarti wrote:
<blockquote
cite="mid:38B63D02-0966-4D3B-9901-2F8458266EFE@digitalraindrop.com"
type="cite">
<div><span class="Apple-style-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; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span
class="Apple-style-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; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;">Thought:
If there's a typo on a page, would someone use the same system? While I
love the idea of creating a prominent "report this page for updates"
link / button, I think we'll end up with pages reported without a clear
idea of whether it's a one-line typo / grammar error or a
multi-paragraph rewrite. <br>
</span></span></div>
</blockquote>
Yeah... that wouldn't be good.<br>
<blockquote
cite="mid:38B63D02-0966-4D3B-9901-2F8458266EFE@digitalraindrop.com"
type="cite">
<div><br class="khtml-block-placeholder">
</div>
<div><span class="Apple-style-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; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span
class="Apple-style-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; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;">I'm
a doc newbie, of course, so take this with a grain of salt :)</span></span></div>
</blockquote>
So? In fact, we should weight newbies' thoughts more than vets'. The
newer you are, the more your mindset is like that of a casual visitor
looking through the handbook.<br>
<blockquote
cite="mid:38B63D02-0966-4D3B-9901-2F8458266EFE@digitalraindrop.com"
type="cite">
<div><span class="Apple-style-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; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span
class="Apple-style-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; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;">
Maybe adding a comment field with "Submit suggestions for updates"
would encourage readers to add a specific update instruction?</span></span></div>
</blockquote>
That would be perfect. Along with the comments box, should the user
also be able to choose the priority? To help them decide which one is
right, I guess we could have a few examples there, like critical is
broken code, minor is typo, and normal is something in between.<br>
<br>
Possible format:<br>
<br>
Issue title: "Page Title updates requested."<br>
Submitted by: whoever submitted it -- Should the user have to be logged
in?<br>
Project: Documentation<br>
Component: whatever component<br>
Category: task<br>
Priority: whichever the user chooses<br>
Initial status: patch (code needs review)<br>
<br>
Description: "User whatever requested that the Handbook page 'Page
Title' in Component be updated.<br>
<br>
Comments: whatever the user put in"<br>
<br>
What do you guys think?<br>
<blockquote
cite="mid:38B63D02-0966-4D3B-9901-2F8458266EFE@digitalraindrop.com"
type="cite">
<div><br class="khtml-block-placeholder">
</div>
<div><span class="Apple-style-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; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span
class="Apple-style-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; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;">Hope
this helps,</span></span></div>
<div><br class="khtml-block-placeholder">
</div>
<div><span class="Apple-style-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; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><span
class="Apple-style-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; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;">
Dave.<br class="Apple-interchange-newline">
<div><br class="khtml-block-placeholder">
</div>
<div>------------------------</div>
<div>Dave Chakrabarti</div>
<div>Director of Programs</div>
<div>Grassroots.org</div>
<br class="Apple-interchange-newline">
</span></span> </div>
<br>
<div>
<div>On Aug 8, 2007, at 10:01 AM, Ben Feldman wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"> Greg Knaddison - GVS wrote:<br>
<blockquote
cite="mid:3861c6770708080714v53923bc4vb6cb778f3d9512c6@mail.gmail.com"
type="cite">
<blockquote type="cite">
<pre wrap="">Also, I think if a common user could flag a handbook as "needs updated",
it would come in use. Before I was a maintainer, I viewed handfuls of
handbook pages that needed updated, but I didn't know who to notify. It
would be useful to have a link for "needs updated", or something
similar, so that maintainers could be notified. All flagged handbook
pages would be compiled into a page, sorted by number of flags.
</pre>
</blockquote>
<pre wrap="">This sounds great to me as well. We have the "suggest documentation
improvements" link in the bottom of the left sidebar along with a
couple other things. I'd prefer seeing that in the content area just
under each handbook page and above any comments. That's the place
where people will be thinking about it and might act on it. The
bottom of the left sidebar is a place where, even after viewing
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 class="moz-signature" cols="72">--
Ben Feldman
Director, Go FLOSS!
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:ben@go-floss.org">ben@go-floss.org</a></pre>
<div style="margin: 0px;">--</div>
<div style="margin: 0px;">Pending work: <a moz-do-not-send="true"
href="http://drupal.org/project/issues/documentation/">http://drupal.org/project/issues/documentation/</a></div>
<div style="margin: 0px;">List archives: <a moz-do-not-send="true"
href="http://lists.drupal.org/pipermail/documentation/">http://lists.drupal.org/pipermail/documentation/</a></div>
</blockquote>
</div>
<br>
<pre wrap="">
<hr size="4" width="90%">
--
Pending work: <a class="moz-txt-link-freetext" href="http://drupal.org/project/issues/documentation/">http://drupal.org/project/issues/documentation/</a>
List archives: <a class="moz-txt-link-freetext" href="http://lists.drupal.org/pipermail/documentation/">http://lists.drupal.org/pipermail/documentation/</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Ben Feldman
Director, Go FLOSS!
<a class="moz-txt-link-abbreviated" href="mailto:ben@go-floss.org">ben@go-floss.org</a></pre>
</body>
</html>