I don't think we can delegate any part of Drupal to something we don't control; I think that's just a non-starter.<br><br>So for me, the issue is what we can learn from StackOverflow and friends - they do great stuff and end up with great content. And yes, I think we should build something on that.<br>
<br>Who is signing up to build it? I think it's an easy sell.<br><br>-Randy<br><br><div class="gmail_quote">On Mon, Jan 31, 2011 at 4:25 PM, Dan Horning <span dir="ltr"><<a href="mailto:dan.horning@planetnoc.com">dan.horning@planetnoc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">i have to ask ... what would we actually gain by doing this - cleanup the various methods for finding info about a given module or theme or bug a little and we far surpass this suggested tool<br>
<br>
it seems that stackoverflow is driven very highly on userpoints to control access - which while a good thing - doesn't really fit the development model we have here. there are existing processes that would have to change to fit the suggested model. I for one am more for peer reviews and leadership staff assigning access than a points system that someone could rack up points and just get access ... what's that really do for the community - seems that would be great if we were just a tech help forum - awarding points for the users that help and giving them more access - but what's that do for drupal and it's community? (i know there is a potential for this to help ...)<br>
<br>
another area of issue to me is - another login ? or would it use SSO?<br>
do the drupal leadership users and dries have admin level control...?<br>
<br>
mostly here i just don't get what adding yet another resource (like has been said before) would do to help the lead devs, module + theme devs and just supporting drupal. if i had say -=- i'd vote against this idea<br>
<br>
--<br>
Dan Horning<br>
<br>
----- Original Message -----<br>
> From: "Victor Kane" <<a href="mailto:victorkane@gmail.com">victorkane@gmail.com</a>><br>
> To: <a href="mailto:development@drupal.org">development@drupal.org</a><br>
> Sent: Monday, January 31, 2011 6:01:55 PM<br>
> Subject: Re: [development] Drupal Answers: A Stackoverflow/StackExchange site proposal<br>
> I guess this is a good place to start:<br>
> <a href="http://area51.stackexchange.com/faq" target="_blank">http://area51.stackexchange.com/faq</a><br>
><br>
><br>
> On Mon, Jan 31, 2011 at 8:00 PM, Victor Kane < <a href="mailto:victorkane@gmail.com">victorkane@gmail.com</a> ><br>
> wrote:<br>
><br>
><br>
><br>
><br>
> On Mon, Jan 31, 2011 at 6:57 PM, Josh Koenig < <a href="mailto:josh@getpantheon.com">josh@getpantheon.com</a> ><br>
> wrote:<br>
><br>
><br>
><br>
> Stew,<br>
><br>
><br>
> Thanks for starting this thread. This is important stuff:<br>
><br>
><br>
><br>
> <a href="http://area51.stackexchange.com/proposals/2978/drupal-answers" target="_blank">http://area51.stackexchange.com/proposals/2978/drupal-answers</a><br>
><br>
> I want to put my support behind this proposal and explain my thinking<br>
> in doing so.<br>
><br>
><br>
> The Drupal community is already growing faster than Drupal's<br>
> infrastructure can easily support. With the release of D7 and all the<br>
> other associated projects getting off the ground, <a href="http://drupal.org" target="_blank">drupal.org</a> is<br>
> increasingly often a bottleneck or blocker. We have wonderful hosts<br>
> from OSUOSL, but the human resources needed to develop, maintain and<br>
> manage our own infrastructure (which is a 24x7x365 job) are limited.<br>
><br>
><br>
> We have to pick our battles. I much would rather see energy, effort,<br>
> attention and money poured into continuing to improve our git and<br>
> module infrastructure — which is much more deeply intrinsic to the<br>
> health and future of the project — and accept that even though we<br>
> *can* build our own StackOverflow (@eaton proved this already) that<br>
> doesn't necessarily mean it's the best use of limited resources, or<br>
> the best thing for the project.<br>
><br>
><br>
> Drupal can theoretically/technically solve a lot of its own problems,<br>
> but I think we often suffer from a "not built here" prejudice as a<br>
> result. In the realm of getting good quality answers to Drupal<br>
> questions out to the most people possible, I can't see how a<br>
> StackExchange site would do anything but help. I would love to see the<br>
> community embrace something really cool and useful from the wider<br>
> Internet as a way to promote the project.<br>
><br>
><br>
><br>
><br>
> You make a convincing argument Josh; my own gut feeling has been,<br>
> reading this thread, "how can we delegate something so important to<br>
> the Drupal Community as its own documentation to another party who may<br>
> or may not exist in the near/medium/long term".<br>
><br>
><br>
> Can someone inform somewhat on who these guys are? And why there and<br>
> not someplace else?<br>
><br>
><br>
> Victor<br>
><br>
><br>
><br>
><br>
><br>
> Finally, I should say that I *do not* think a StackExchange answers<br>
> site replaces anything. It's not an issue queue, and it's not a<br>
> replacement for the dialogue that exist in the forums. I would say<br>
> it's a new resource, something that can help the 10s of 1000s of<br>
> people who will be trying to wrap their mind around Drupal in the<br>
> coming year.<br>
><br>
><br>
> Cheers<br>
> -josh<br>
</blockquote></div><br><br clear="all"><br>-- <br>Randy Fay<br>Drupal Module and Site Development<br><a href="mailto:randy@randyfay.com">randy@randyfay.com</a><br>+1 970.462.7450<br><br>