Hello,<br><br>Just to bring my 1 cent on it, I agree with
Angie(webchick), credit is for "Drupal community", consider also that
users can list what they contributed in their d.o profile ("I
contributed Drupal Documentation"), and there is a textarea which could
be used to fill a list of i.e: "Documentation I worked on".<br>
<br>Blessings!<br><br><div class="gmail_quote">On Sun, May 25, 2008 at 11:33 PM, Angela Byron <<a href="mailto:drupal-docs@webchick.net">drupal-docs@webchick.net</a>> 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="Ih2E3d">Angela Byron wrote:<br>
> Steve Dondley wrote:<br>
>> Great point.<br>
>><br>
>> Which sparks an idea: Why not give document pages ownership like we<br>
>> do projects? Why should documentation get what amounts to 2nd class<br>
>> karma status? Might be a more comprehensive change but it could also<br>
>> be very worthwhile.<br>
<br>
</div>As if I didn't type enough in my previous reply... ;)<br>
<br>
I also don't buy this "2nd class karma status" bit at all. I see<br>
handbook contribution on exactly the same level as core patch contribution.<br>
<br>
From index.php:<br>
<br>
---<br>
<br>
$return = menu_execute_active_handler();<br>
<br>
---<br>
<br>
That's the single line that makes Drupal do anything. Do you know who<br>
wrote that line of code? Probably not. Does it really matter? No. What<br>
matters is that Drupal is a kick-ass piece of software.<br>
<br>
Similarly, our goal as docs team members should be to make the handbook<br>
a kick-ass piece of documentation. It doesn't matter who started a page,<br>
or who spent the most time on it, or who fixed the most typos. Improving<br>
the handbook has direct benefits for /everyone/ involved in the Drupal<br>
ecosphere.<br>
<br>
Btw, it turns out, the person who wrote that line of code is chx<br>
(actually, it was originally written long before, and chx was the last<br>
person to refactor it, but nonetheless...). I couldn't begin to list the<br>
lines of code in Drupal that belong to chx, or that chx has touched. I<br>
don't think even chx could do that. :)<br>
<br>
But yet, somehow everyone knows that chx contributes an enormous amount<br>
of code to Drupal core. And somehow chx comes across as someone<br>
knowledgeable about Drupal. And when chx says something, people listen.<br>
It's because of his *actions*, not because of the *credit* given to<br>
those actions. The credit for core commits is actually /harder/ to<br>
determine than those for handbook pages; there's no nice revisions page<br>
showing you a list; you have to go sifting through cvs annotate and cvs<br>
log to figure out this kind of stuff.<br>
<br>
But by all means, add "Contributed 10-Step Form API tutorial" to your<br>
Drupal resumé (just as I'm sure chx has "Re-wrote the Drupal menu<br>
system" on his, and I have "Wrote the Form API Reference" on mine).<br>
There's nothing wrong with being proud of the work you've done, and<br>
communicating to clients and business partners that you're committed to<br>
improving Drupal's documentation.<br>
<div><div></div><div class="Wj3C7c"><br>
-Angie<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><br clear="all"><br>-- <br>Fernando P. García, <a href="http://www.develcuy.com">http://www.develcuy.com</a><br>Developer - Analista de Sistemas<br>+51 1 9 8991 7871, Mz. P Lt. 30 1et Urb. Pachacamac - VES, Lima - Perú<br>