When it comes down to it, the issue of how the text is edited is really an entirely different discussion than how to restructure the help content.<br><br>At the risk of sounding like a broken record, the timeline is much too short for this issue (we have just over 2 weeks) to change the way the help documentation works - I'm sure if you want to sign up to rewrite help text for a module with the new format, and post it as a comment, someone else can put it into the PHP code and roll the patch. <br>
<br>But to be honest, like Jennifer said on the other thread that was started on barriers to contributing, there are many other really useful places you can help that do not require going into the code or rolling patches. She put several examples in her reply that I think are worth going through if you want to help out more!<br>
<br>Ariane<br><br><br><br><br><div class="gmail_quote">On Sat, Nov 14, 2009 at 5:06 AM, adept digital evolution <span dir="ltr"><<a href="mailto:techlists@ade.pt">techlists@ade.pt</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">
<br>
</div>I have to agree. There should be an easier way to participate for<br>
non-developers who, like myself, know nothing of CVS systems or patches<br>
or php, and who do not have time or inclination to learn that end of<br>
things, but who (also like myself) might be quite good at helping to<br>
author and organize good help documentation.<br>
<br>
I've pretty much given up on helping with docs because I click links<br>
from this discussion list to look at an issue, and then have absolutely<br>
no idea what to do. It looks like I'd have to know php, to know how to<br>
check out items from some repository somewhere (where?), how to write<br>
something called a "patch", how to test it, and so on. This is just not<br>
my profession. The whole approach pretty much freezes just regular old<br>
consultants and writers from your process.<br>
<br>
I had done much work on he D7 install guide (the online version) and<br>
therefore offered to also review the install.txt document that gets<br>
included with the downloaded installer , but for some reason this is<br>
much more complicated than just editing a text document. I didn't know<br>
where to get it or what the heck to do with it. I used up my time trying<br>
to figure all that out without ever even finding it.<br>
<br>
I will continue to edit any d.o doc pages that I might have priv's to<br>
edit. But I hope some day editing help text is as easy as editing<br>
anything on d.o<br>
<br>
kazar<br>
<div><div></div><div class="h5"><br>
<br>
--<br>
Pending work: <a href="http://drupal.org/project/issues/documentation/" target="_blank">http://drupal.org/project/issues/documentation/</a><br>
List archives: <a href="http://lists.drupal.org/pipermail/documentation/" target="_blank">http://lists.drupal.org/pipermail/documentation/</a><br>
</div></div></blockquote></div><br>