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

Shai Gluskin shai at content2zero.com
Mon Jan 31 03:19:14 UTC 2011

I had dreamed of having more time to give to the Drupal effort, which sadly
has not emerged. I had schemed on strongly advocating for the establishment
of a "support team" just like we have a "documentation team". In my opinion
support and documentation are very different.

I fully acknowledge that suggesting an idea when I don't have the time to
lead or even help make it happen is lame... But in the context of this
discussion, I can't help myself from at least putting it out there.

The ideas in this thread are awesome. It would be nice to have a focussed
support team that could make them happen.


On Sun, Jan 30, 2011 at 8:31 PM, Dipen <dipench at gmail.com> wrote:

> Also, I will be very much willing to help get that system in place if there
> is interest from infrastructure/webmasters group. To oversimplify things
> using flag module and good permission system ( letting the question author
> and some select group of people ) to set that flag should help us realize
> that goal.
> I really feel we should have that system on forums. The good part of that
> system is we can crowdsource many how to's if we have that structure and
> community filter in place.
> ----------------------------------
> Dipen Chaudhary
> Founder, QED42 : We build beautiful and scalable web strategies (
> www.qed42.com )
> Blog: dipenchaudhary.com
> Twitter: http://twitter.com/dipench
> On Mon, Jan 31, 2011 at 6:58 AM, Dipen <dipench at gmail.com> wrote:
>> I feel the most important feature of a support system from a seeker's
>> point of view is to quickly filter out the signal from the noise, when I
>> search google for support on any topic I am really looking for 2 things:
>> 1> To find a forum topic (blog posts are godsend) which is close to what I
>> am looking for.
>> 2> When I see that the post or the question has been answered, which is
>> usually the most difficult part as when I am not sure if the post has
>> already been answered comprehensively by community I am weary of reading the
>> whole thing but irrespective I have to. If you look at new age support
>> systems like stackoverflow, zendesk you can quickly make out if the query is
>> resolved and in most cases you got to read only one response ( like in case
>> of stackoverflow )
>> I would like to see the 2nd part on drupal.org a way to mark a question
>> SOLVED/RESOLVED as I think that will make lives of thousand of support
>> seekers easier by filtering out the noise from signal. Some more work into
>> that system we will also be able to reduce number of duplicate questions.
>> I created an issue about this around 2 years back but never got a response
>> :) - http://drupal.org/node/399592
>> What do you think?
>> Cheers
>> ----------------------------------
>> Dipen Chaudhary
>> Founder, QED42 : We build beautiful and scalable web strategies (
>> www.qed42.com )
>> Blog: dipenchaudhary.com
>> Twitter: http://twitter.com/dipench
>> On Mon, Jan 31, 2011 at 5:24 AM, nan wich <nan_wich at bellsouth.net> wrote:
>>>  It also appears to do badging (such as User Badges will hopefully get
>>> to). Is that in ArrayShift?
>>> The interesting thing is that I never could navigate to a question. Is
>>> that a function of age or must one be a member before one may ask or see
>>> questions?
>>> And thanks for letting me know about VUD so now I know which direction to
>>> move Plus 1 for merging.
>>> *Nancy*
>>> Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L.
>>> King, Jr.
>>>  ------------------------------
>>>  *From:* Carl Wiedemann
>>> Recently the Vote Up/Down module http://drupal.org/project/vote_up_downwas implemented on
>>> groups.drupal.org in an effort to provide some sense of each post's
>>> value to the community. Integrating Vote Up/Down with drupal.org's
>>> existing forum could be a next step.
>>> Stack Overflow's architecture translated to Drupal bespeaks a content
>>> type, comments, free-tagging taxomony, vote up/down, Views and a few other
>>> things (notifications/subscriptions, statistics, flags, etc). Some effort in
>>> has already been put toward emulating it:
>>> http://drupal.org/project/arrayshift
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20110130/9da5368a/attachment.html 

More information about the development mailing list