Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.This is a portion of the ongoing reorganization of the Drupal.org handbook.
This is one page -- a landing page intended for users who have just discovered a problem, don't know anything about the Drupal community or how problems should be reported, and have therefore been scanning through the handbook's table of contents looking for a phrase that's something like "Report a Problem". :) This page should explain about the issue queue and direct users to the section of the handbook about the queue. You may also want to refer users to the "Get a drupal.org account" section, and/or other Drupal resources.
Comments
Comment #1
esmerel commentedAnd because I think there's a crossover between this and 'talking to the community', I will go ahead and take this one also.
Comment #2
esmerel commentedI'm somewhat torn on making this it's own thing. Reporting a problem *is* communication with the community. The issue queues are just one of the many areas we communicate. However, it's one of the highest profile ones and the thing people are most likely to get vocal about.
That said:
http://drupal.org/Troubleshooting-FAQ could probably be included here.
We should include some basic guidelines and suggestions on reporting problems (what to include in a report, etc.) The forum guidelines at http://drupal.org/forum-posting are also completely appropriate for the issue queues.
Get a d.o. account if you don't have one already: http://drupal.org/user/register
Issues queues may generally 'belong' to the community, but really? You're asking a small group of people (mostly the maintainer) for help with a problem. Issue queues are not a place to get snippy if you aren't getting the answer you want (not that this EVER happens.)
http://drupal.org/project/issues is the overview page for all issues for the project. Specific modules have their own issue queues, which can be reached by using a more specific URL: http://www.drupal.org/project/issues/ - for example, http://www.drupal.org/project/issues/Drupal for Drupal core.
Comment #3
add1sun commentedWellI thikn we are hoping someone sees "Report a problem" because they want to complain and then we show them that there is no "they". ;-) This should be linked to directly from the Support page.
Re: some specifics:
"Troubleshooting-FAQ"
+1
"Get a d.o. account if you don't have one already."
We will have a whole new handbook page on this one: http://drupal.org/node/240235
The rest of this looks good to me too. It occurs to me that another thing we may want to add are things like problems with d.o itself (webmasters, infra), and point to the "d.o" issue queues.
Comment #4
nielsbom commentedChanged the component to reflect the new component categorization. See http://drupal.org/node/301443
-nielsbom
Comment #5
add1sun commentedOK, so lessee. One page that basically walks through this outline:
You found a problem! Oh noes!!!! ;-) Here is how our community deals with problems:
First, check out the http://drupal.org/Troubleshooting-FAQ
Then look to see if others have had the same issue. (See the Issue queue section for specifics on using/searching the queue: http://drupal.org/node/240213)
Some important things:
Get a d.o. account if you don't have one already: http://drupal.org/node/240235
How to report bugs effectively: http://drupal.org/node/19279
Also a note about the d.o website itself that many people don't think of as having issue queues:
Documentation: http://drupal.org/node/240242, queue: http://drupal.org/project/issues/documentation
Webmaster queue: http://drupal.org/project/issues/webmasters
Infrastructure queue: http://drupal.org/project/issues/infrastructure
Comment #6
add1sun commentedThis page has been created and needs to be written out. http://drupal.org/node/314185
Comment #7
add1sun commentedchanging title for ongoing work
Comment #8
mike booth commentedI fleshed out the Report a Problem page, working more or less from the outline.
Things we may want to address:
* The order of the links and/or their relative emphasis. If the goal is to steer people toward the issue queues, we might want to remove the specific IRC and support-forums links and just have a generic "talk with the Drupal community" link. If the goal is to steer people to the forums first, perhaps we should move them up on the page. And so on.
* I didn't include a link to the website infrastructure queue because I despair of explaining the difference between a "webmaster issue" and a "drupal.org infrastructure issue" to a newbie in ten words or less. This may be because I don't really understand the difference myself. ;) The latest entries in the webmaster queue suggest that most other people don't understand the difference either; e.g. http://drupal.org/node/303702
Comment #9
add1sun commentedLooks good to me. Thanks! I'm happy with how it is so feel free to close this ticket unless others want to continue working on it.
I think that the order on the info is good. I think we do want to push them to the issue queue, but I think having a list of support options at the bottom doesn't hurt.
I agree re: infrastructure. It is better to not confuse people. Good call.
Comment #10
mike booth commentedComment #11
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.