[meta] Issues for improving support options on d.o.

Also, if anyone wants to work on this, let me know and I'll get you access to a shared d.o sandbox for this work! :)

Oh, we should hope to be so lucky! :D

But true enough. Instead, we'll have people leave a comment at #1414828: Implement the Answers module for providing better support on Drupal.org if they'd like to lay down some code.

Be aware, there is a support sprint being organized for DrupalCon. I'm sure some of these things can be worked on there. Those interested can contact realityloop and hedgemage.

I took a look at the work that's been done so far. I just wanted to say that since we're at the beginning of building something great, we should also take care of not allowing it to be haunted/taunted by the defects of the past. To that end, I think we should seriously think about implementing something like #19386: Automatically search for duplicate issues/questions before submitting new issue/question before we take it live. We need to make sure we don't get a multitude of dupes putting support people off each time they need to type "This has been asked before" answers.

PS: ...for those that don't want to go through the entire issue there, there's the Similar Entries contrib module and here's a screenie of how bugzilla does it.

Edit: That screenshot is kinda big to have it inline. I don't want to bloat the issue ;)

I don't like blocking this improvement on duplicate checking (there are 11 years of duplicate posts, another few months of them isn't worth holding up something the community desperately wants to see), but I agree that it would certainly be a killer feature.

Another killer feature that would be worth playing around with (again, not a blocker) is something like http://drupal.org/project/node_convert (if that actually works; I'm going by name only :)) to convert nodes to/from issues and support requests. Ideally, we could boot things out of the issue queue to this system if we find they're asking for help instead of talking about bugs/features, and similarly if we find bug reports being submitted in the support section we could turn them into issues.

I don't like blocking this improvement on duplicate checking (there are 11 years of duplicate posts, another few months of them isn't worth holding up something the community desperately wants to see)...

...fair enough. But, instead of splitting it to an entirely different issue I adjusted the related one and noted that it is a nice-to-have not a blocker for this one: #19386-16: Automatically search for duplicate issues/questions before submitting new issue/question

Also went ahead and filed a new issue for Angie's idea: #1477438: Provide means to convert issues/comments to/from support questions.

I can confirm Node Convert works in D6. I've used it many times and it's great. :)

For people that were interested in this, this may be of some interest: https://twitter.com/cweagans/status/350076910086266881

@Michelle - Any experience with the D7 Version of the code?

No activity for 5 years.
All issues linked in the summary closed.
I believe we can close this now. You've got two weeks to reopen if you disagree.

No disagreement but I wanted to apologize to mgifford for not answering him. That question came at a time when I had fallen away from Drupal for a while so I probably missed it when I came back 4 months later. And I don't remember if I ever used it in D7. The site I used it on folded and I don't think I ever upgraded it.

For what it is worth, I've used the Drupal 7 version of Node Convert in several projects. In my experience, it works as advertised. However, it looks like it needs a new maintainer,