<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Hi Shai, Nat, et. al.,</div><div><br></div><div>Thanks for the warm welcome and the pointers to where to go next. I've followed your links and created a new issue to request to join the docs team:</div><div><br></div><div><div><a href="http://drupal.org/node/265234">http://drupal.org/node/265234</a></div><div><br></div><div>I'll certainly monitor this listserve, though I suspect I'll be quiet-ish while I find my feet. Since working with Drupal is now my day job and I'm still learning about it, I'll probably spend a fair bit of time on the Drupal.org handbook pages in the coming weeks.</div><div><br></div><div>Sounds like since I'm in Sydney and much of the Drupal community is in America or Europe, I might not be able to discuss much in real time over IRC or the like. But that's all right, I'll just post here and make what I hope will be helpful edits for a while as I get to know you all.</div><div><br></div><div>Thanks again for the warm welcome. I'm looking forward to getting to know all of you, as well,</div><div>Cheers,</div><div><div>--</div><div>-Meitar Moscovitz</div><div>Drupal: <a href="http://drupal.org/user/265715">http://drupal.org/user/265715</a></div><div>Personal: <a href="http://maymay.net/">http://maymay.net/</a></div><div>Professional: <a href="http://MeitarMoscovitz.com/">http://MeitarMoscovitz.com/</a></div><div><br></div></div><div><br></div></div></div><div>On May 30, 2008, at 11:18 PM, Shai Gluskin wrote:</div><div apple-content-edited="true"><br class="Apple-interchange-newline"> </div><div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Meitar,<br><br>Great piece on setting up a multisite local development server!<br><br>Meitar, here is the part that may have confused you: Any registered user of Drupal.org has permissions to create a new handbook page. That's how you could post the multisite local development piece that you wrote to the handbook. If you create the page, you can also edit it.<br> <br>In order to edit a handbook page that you did <i>not</i> create, you need to be on the docs team. I highly recommend that you join the docs team. Nat Catch gave you the URL and I'll give it to you again: <a href="http://drupal.org/project/issues/documentation/">http://drupal.org/project/issues/documentation/</a> Create a new issue and put in the title, "Request to Join Docs Team." It could take from a couple minutes to a couple days to go through. List your user number and mention that you've written a doc already.<br> <br>It seems like you got hung up a bit on your lack of permission to assign an issue in the issue queue to anyone other than yourself. That feature isn't really used by the documentation team, anyway. Just post away in the Doc issue queue if you have issues to bring up.<br> <br>Regarding the issue you raised at: <a href="http://drupal.org/node/263767">http://drupal.org/node/263767</a> (Configuring Apache and PHP for Drupal in a Shared Environment" Best Practices), which no one responded to: tt was a proposal, actually a draft, to write another book page. Let me translate the lack of response: "Meitar, go for it, no objections here." However, I totally understand that it is hard to read that in the silence. I'm pleased that you wrote to this list and didn't give up. I'll go leave a note on that issue now. Your experience teaches a lesson about how it can be confusing about how to be involved in Drupal.<br> <br>I second Nat's suggestion that you join the discussion at: <a href="http://drupal.org/node/263767">http://drupal.org/node/263767</a>, which in some ways is trying to address isues that you bring up.<br><br>How can you help? You already have. More. Keep thinking of handbook pages that you think need writing and write some of them yourself. Poke around the handbook and edit other's work (afteryou get doc team privileges). Monitor this listserve. There are some IRC meeting being convened by Addi Berry to discuss major upgrades to the handbook for the upcoming upgrade to Drupal.org; I believe she always announces those meetings on this list serve. Monitor the documentation issue queue.<br> <br>Thanks for writing and I look forward to working with you and getting to know you better,<br><br>Shai<br><a href="http://content2zero.com">content2zero</a><br><br><br>On Fri, May 30, 2008 at 6:41 AM, Nathaniel Catchpole <<a href="mailto:catch56@googlemail.com">catch56@googlemail.com</a>> wrote:<br> ><br>> Meitar,<br>><br>> You can edit that page directly if you're a member of the documentation team. To do that, you just need to follow the process outlined here: <a href="http://drupal.org/node/23367">http://drupal.org/node/23367</a> - the short version is go to <a href="http://drupal.org/project/issues/documentation/">http://drupal.org/project/issues/documentation/</a> and add a request.<br> ><br>> You also seem to be our exact target for a proposed new block to make it easier to find information about contributing to documentation - your input would be very helpful on this issue: <a href="http://drupal.org/node/263767">http://drupal.org/node/263767</a><br> ><br>> Nat<br>><br>><br>><br>><br>> On 5/30/08, Mr. Meitar Moscovitz <<a href="mailto:meitarm@gmail.com">meitarm@gmail.com</a>> wrote:<br>>><br>>> Hi all,<br>>><br>>> I'm new here, and I'm a developer new to Drupal as well. I've just<br> >> recently begun working with Drupal full time in a professional<br>>> context, and in the process have found the existing Drupal docs to be<br>>> of invaluable importance in my learning. Naturally, I found some areas<br> >> where they could be better, more clear, or are simply lacking. I<br>>> thought I'd raise my hand to volunteer to help out whatever<br>>> documentation efforts the Drupal community has and, especially as a<br> >> new Drupal user and developer, try to flesh out whatever I can so its<br>>> more accessible to people without prior Drupal experience or knowledge.<br>>><br>>> I've already added a few a page of my own to the documentation, not<br> >> very Drupal-specific but helpful (I think), which you can see at <a href="http://drupal.org/user/265715/track">http://drupal.org/user/265715/track</a><br>>><br>>> A while ago I also put in this documentation issue: <a href="http://drupal.org/node/238799">http://drupal.org/node/238799</a><br> >><br>>> I let it sit for a while since I hadn't had the time to get back to it—<br>>> it's always a challenge to balance "getting work done" and "giving<br>>> back to the community" as I'm sure you al know. In any event, I'd love<br> >> to start getting more involved, but don't know precisely how to go<br>>> about doing that. I figured what better place to ask than here, on the<br>>> doc list?<br>>><br>>> Who do I poke about that documentation issue? Where can I go to see<br> >> other issues that I can help out with (if not the documentation<br>>> issues, which apparently I need special privileges that I lack to<br>>> affect). So basically…yeah, where might I be needed, or helpful?<br> >><br>>> By way of delayed introduction, I'm a technical author and a web<br>>> developer/sysadmin by trade. I'm specifically a front-end specialist,<br>>> with a focus on semantic web technologies, and if that's not enough,<br> >> I'm dating a writer. :)<br>>><br>>> Cheers,<br>>> -Meitar Moscovitz<br>>><br>>> Drupal: <a href="http://drupal.org/user/265715">http://drupal.org/user/265715</a><br>>> Personal: <a href="http://maymay.net/">http://maymay.net/</a><br> >> Professional: <a href="http://MeitarMoscovitz.com/">http://MeitarMoscovitz.com/</a><br>>><br>>><br>>> --<br>>> Pending work: <a href="http://drupal.org/project/issues/documentation/">http://drupal.org/project/issues/documentation/</a><br> >> List archives: <a href="http://lists.drupal.org/pipermail/documentation/">http://lists.drupal.org/pipermail/documentation/</a><br>><br>><br>> --<br>> Pending work: <a href="http://drupal.org/project/issues/documentation/">http://drupal.org/project/issues/documentation/</a><br> > List archives: </blockquote></div><br></body></html>