I guess this is a good place to start: <meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://area51.stackexchange.com/faq">http://area51.stackexchange.com/faq</a><br><br><div class="gmail_quote">
On Mon, Jan 31, 2011 at 8:00 PM, Victor Kane <span dir="ltr"><<a href="mailto:victorkane@gmail.com">victorkane@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div class="im">On Mon, Jan 31, 2011 at 6:57 PM, Josh Koenig <span dir="ltr"><<a href="mailto:josh@getpantheon.com" target="_blank">josh@getpantheon.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Stew,</div><div><br></div><div>Thanks for starting this thread. This is important stuff:</div><div><div><br></div><div><a href="http://area51.stackexchange.com/proposals/2978/drupal-answers" target="_blank">http://area51.stackexchange.com/proposals/2978/drupal-answers</a></div>
<div><br></div></div>I want to put my support behind this proposal and explain my thinking in doing so.<div><br></div><div>The Drupal community is already growing faster than Drupal's infrastructure can easily support. With the release of D7 and all the other associated projects getting off the ground, <a href="http://drupal.org" target="_blank">drupal.org</a> is increasingly often a bottleneck or blocker. We have wonderful hosts from OSUOSL, but the human resources needed to develop, maintain and manage our own infrastructure (which is a 24x7x365 job) are limited.</div>
<div><br></div><div>We have to pick our battles. I much would rather see energy, effort, attention and money poured into continuing to improve our git and module infrastructure — which is much more deeply intrinsic to the health and future of the project — and accept that even though we *can* build our own StackOverflow (@eaton proved this already) that doesn't necessarily mean it's the best use of limited resources, or the best thing for the project.</div>
<div><br></div><div>Drupal can theoretically/technically solve a lot of its own problems, but I think we often suffer from a "not built here" prejudice as a result. In the realm of getting good quality answers to Drupal questions out to the most people possible, I can't see how a StackExchange site would do anything but help. I would love to see the community embrace something really cool and useful from the wider Internet as a way to promote the project.</div>
<div><br></div></blockquote><div><br></div></div><div>You make a convincing argument Josh; my own gut feeling has been, reading this thread, "how can we delegate something so important to the Drupal Community as its own documentation to another party who may or may not exist in the near/medium/long term".</div>
<div><br></div><div>Can someone inform somewhat on who these guys are? And why there and not someplace else?</div><div><br></div><font color="#888888"><div>Victor</div></font><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div></div><div>Finally, I should say that I *do not* think a StackExchange answers site replaces anything. It's not an issue queue, and it's not a replacement for the dialogue that exist in the forums. I would say it's a new resource, something that can help the 10s of 1000s of people who will be trying to wrap their mind around Drupal in the coming year. </div>
<div><br></div><div>Cheers</div><div>-josh</div>
</blockquote></div></div><br>
</blockquote></div><br>