As much as I really do agree that it would be great to have some more formal acknowledgment, and that it should certainly be a consideration as maybe another phase of the redesign and development of <a href="http://docs.drupal.org">docs.drupal.org</a>, in the meantime, I think it's a bit of a matter of self promoting. <br>
<br>- List your contributions on your d.o profile<br>- Blog about your achievements<br>- Add it to your bio on your company's website<br><br>And never negate the worth of Drupal karma - I have seen my perceived worth and the amount of respect I get in the community grow significantly through working on docs.<br>
<br>But yes, let's put that on the agenda of things to work out - why not file an issue?<br>A.<br><br><br><br><div class="gmail_quote">On Mon, Feb 1, 2010 at 5:36 PM, Shai Gluskin <span dir="ltr"><<a href="mailto:shai@content2zero.com">shai@content2zero.com</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;">Folks,<div><br></div><div>Re: Josh, given that at your first glance you thought there was a security problem... even though it was from not reading thoroughly, I'm concerned othes will read similarly. So I changed some the intro to the following:</div>
<div><br></div><blockquote style="border: medium none ; margin: 0pt 0pt 0pt 40px; padding: 0px;"><div><span style="font-family: 'Bitstream Vera Sans',Verdana,Helvetica; font-size: 13px; color: rgb(0, 49, 80); line-height: 17px;">An alternative, detailed here, is for the <b>site developer</b> to place PHP code into the "PHP Code" fieldset below the allowed values box on the textfield set-up page in order to populate the list by parsing the text stored in a node.</span></div>
</blockquote><div><br></div><div>I've removed the credit at the bottom.</div><div><br></div><div>But it raises a larger issue... which is how to promote more documentation writing within Drupal.</div><div><br></div><div>
By comparison... let's look at developers in the Drupal ecosystem... For those who want to get at the heart of the beast, who have LOTS of patience and not much interest in getting credit, there is Drupal core. For those who want to be in charge, have less patience and want to be king of something... they can be involved in module development. Some folks do both, but it seems like there is a personality difference in the two types of people. So the question is, "How can we make writing documentation more motivating form more people to want to participate?"</div>
<div><br></div><font color="#888888"><div>Shai</div></font><div><div></div><div class="h5"><div><br></div><div><br></div><div><br></div><div><br><div class="gmail_quote">On Mon, Feb 1, 2010 at 8:12 PM, Ariane Khachatourians <span dir="ltr"><<a href="mailto:arianekhachatourians@gmail.com" target="_blank">arianekhachatourians@gmail.com</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;">Just had a skim.<br>
<br>
I would agree and say it's pretty well a policy not to credit yourself on
the pages (though I would keep the links to the other two pages if they
are useful as references). It does indeed discourage others from
updating the pages, and sort of clutters up the pages if a lot of
people have worked on them.<br>
<br>
If people want to know who's worked on pages, all they need to is look at the revisions tab.<br>
<br>
Otherwise, formatting and such looks pretty good.<br><font color="#888888">
A.</font><div><div></div><div><br><br><br><br><div class="gmail_quote">On Mon, Feb 1, 2010 at 5:10 PM, Joshua Brauer <span dir="ltr"><<a href="mailto:joshua@brauerranch.com" target="_blank">joshua@brauerranch.com</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 style="word-wrap: break-word;">Um... OK so I didn't read this correctly... The PHP issue isn't what it looked like at first glance....<div><br></div><div><div><br><div>
<span style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Optima; font-size: medium; 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;"><div>
Thanks,</div><div>Josh</div><div><br></div><div>--</div><div>Follow me on Twitter: <a href="http://twitter.com/jbrauer" target="_blank">http://twitter.com/jbrauer</a></div></span>
</div>
<br></div><div><div></div><div><div><div>On Feb 1, 2010, at 6:01 PM, Joshua Brauer wrote:</div><br><blockquote type="cite"><div style="word-wrap: break-word;">Any user with the permissions to post PHP code to your site has permissions much greater than 'administer content types'. In fact they can give themselves 'administer content types' permissions should they choose to.<div>
<br></div><div>I thought we had a policy against the credit links but maybe it's just been a discussion. In short, in my opinion, the credit links discourage others from editing pages as appropriate, clutter the page, and become a problem as to "at what point when I've edited the page should I remove those credit links from two years ago".</div>
<div><br><div>
<span style="border-collapse: separate; font-family: Optima; font-size: medium; 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;"><div>
Thanks,</div><div>Josh</div><div><br></div><div>--</div><div>Follow me on Twitter: <a href="http://twitter.com/jbrauer" target="_blank">http://twitter.com/jbrauer</a></div></span>
</div>
<br><div><div>On Feb 1, 2010, at 4:53 PM, Shai Gluskin wrote:</div><br><blockquote type="cite"><font face="arial, sans-serif"><span style="border-collapse: collapse;">A friend of mine (he's newish to Drupal, this is his first handbook page... go Laurance Rosenzweig @rosetwig) and I wrote a new handbook page for the Reference: snippets section called, "</span>Managing a CCK allowed values list without granting 'administer content types' access."</font><div>
<font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">It's at: <a href="http://drupal.org/node/701774" target="_blank">http://drupal.org/node/701774</a></font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Three kinds of feedback would be appreciated:</font></div><div><ol><li><font face="arial, sans-serif">Tell me there is a much easier way (I'm dreading this one... hope that is NULL)</font></li>
<li><font face="arial, sans-serif">Review the handbook page and make improvements (it's directly editable by all d.o. users as are other handbook pages).</font></li><li><font face="arial, sans-serif">Give feedback on the "credits" at the end. Laurance in writing it up listed our names as creators of the tutorial. That's pretty rare on handbook pages, isn't it? I'm wondering if that is a part of d.o. culture that might be worth changing. I understand that handbook pages evolve with their wiki style. But the revisions list preserves that. And module pages often have "originally written by" lines in them even as the new maintainer identifies him/herself. What do you think.</font></li>
</ol><div><font face="arial, sans-serif">Best,</font></div><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Shai</font></div>
</div>
--<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></blockquote>
</div><br></div></div></blockquote></div><br></div></div></div></div><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></blockquote></div><br>
</div></div><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></blockquote></div><br></div>
</div></div><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></blockquote></div><br>