<html><body bgcolor="#FFFFFF"><div>As a module maintainer, the fragmentation of support channels is of primary concern to me. To be a responsible maintainer, I think that I allready need to pay attention to:</div><div><br></div><div>My issue queues</div><div>Forums</div><div>Support mailing list</div><div>Appropriate <a href="http://groups.drupal.org">groups.drupal.org</a> groups</div><div><br></div><div>Then success of any of these tools is only going to be based on who and how many people participate. IMHO adding channels will only degrade support, not enhance it. I'd like to see people who have problems with my own code driven towards my issue queue and not away from it. </div><div><br></div><div>Dave<br><br>Sent from my iPad</div><div><br>On Jan 31, 2011, at 10:59 AM, Justin Ellison <<a href="mailto:justin@techadvise.com">justin@techadvise.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>I was going to keep quiet on this one, but Scott's mail spurred me to back him up. I'm pretty sure I'm the one that started the Area51 link being passed around twitter. I think the StackExchange site is an excellent idea, but I knew that the conversation would quickly become "we could do it ourselves with modules X, Y, and Z".<div>
<br></div><div>Drupal is a swiss army knife. However, if I have to chop down a tree and have my swiss army knife sitting right next to my chainsaw (that was built specifically to chop down trees), which one will I pick up? Just because I *can* use my knife doesn't mean I *should*.</div>
<div><br></div><div>With my background in the sysadmin world, we're often preaching using the best tool for the job, and I think that mantra is being overlooked here.<br><br></div><div>I understand the that the idea of having a .NET site run any part of something endorsed by d.o is a bit unsettling, but you can't deny how cheap it would be. It costs little to no time, no custom module needs built, and it will cost zero in terms of infrastructure.</div>
<div><br></div><div>All the hard work is already done wrt the StackExchange setup, all it needs now are committals from the community to use it. Why not at least help push it forward just to see how it's received by the community? If nothing else, use the StackExchange site as a pilot/prototype, assess its strengths and shortcomings, then develop a homegrown solution to succeed it?</div>
<div><br></div><div>The bottom line here is that it will take very little effort to get the StackExchange site up and running, and I don't think anyone here would argue that what we have right now is better than what the StackExchange site would provide.</div>
<div><br></div><div>I should clarify that I'm not dead set on the idea either, and I'm not saying I'm right. These are just questions and ideas of mine that no one else has brought up. If you think I'm completely off base, please tell me why.</div>
<div><br></div><div>Justin</div><div><br></div><div><br><div class="gmail_quote">On Mon, Jan 31, 2011 at 12:04 PM, Scott Reynen <span dir="ltr"><<a href="mailto:scott@makedatamakesense.com"><a href="mailto:scott@makedatamakesense.com">scott@makedatamakesense.com</a></a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">... </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
And that sounds a lot like what the Drupal community has been working hard to improve the last few years, so this might be a good opportunity to push that even further.<br><font color="#888888">
<br>
-- <br>
Scott Reynen<br>
<a href="http://MakeDataMakeSense.com"><a href="http://MakeDataMakeSense.com">MakeDataMakeSense.com</a></a><br>
</font></blockquote></div><br></div>
</div></blockquote></body></html>