[development] Drupal Answers: A Stackoverflow/StackExchange site proposal

Sam Tresler sam at treslerdesigns.com
Tue Feb 1 16:05:12 UTC 2011

There is a point, perhaps a line in the sand, where "Eat your own Dog Food" becomes 'isolationism'.

I'm for a Stack Overflow solution.  It involves monumentally less resources from us.  It puts us solidly in touch with another community on the interwebs.  It works.

I prefer forums for forum-like discussions.  Support discussions on forums are annoying.

I prefer issue queues for development, as they are good for managing ongoing development and archiving past development.

I prefer a Stack Overflow for support because they are a meritocracy based, self-sorting, self documenting system.

These are three different things, and I think we gain more than just a solution to our own problems by going th Stack Overflow route.

Sam Tresler

On Mon, 31 Jan 2011, Josh Koenig wrote:

>> However, if a project is formed on d.o to create an "EntityUnderrun"
>> install profile, I'll be one of the first to revoke my commit on
>> StackExchange.
>> Justin
> Not to undercut my own argument for why a StackExchange site would be nice,
> but this already exists:
> http://drupal.org/project/arrayshift
> And, as far as it goes, this isn't very difficult to do:
> http://engineeredweb.com/blog/09/11/building-stack-overflow-clone-drupal-part-1
> However, the value to me is that nobody has to write any code for us to use
> StackOverflow, people are already using it, it reaches an audience outside
> the normal *.drupal.org sphere, and it will keep getting better as the
> general StackExchange platform gets better.
> If it really takes off and people decide to build a viable clone on
> something.drupal.org, we can easily migrate the Q&A data. They make it all
> available as dumps or via API and user contributions are Creative Commons
> licensed:
> http://blog.stackoverflow.com/2009/06/attribution-required/
> -j

More information about the development mailing list