The nice thing about the subscribe commenting system was that the project maintainers could see how many users were interested in the issue; granted, the "follow" button was a major improvement for the focus of the issue. Adding a count of the number of users following any particular issue (perhaps next to the button) could help the maintainers reprioritize their approach to the issue queue, especially in regard to feature ...more »
Despite the awesome "Follow" button that was added to the top of issues, I still see a lot of people posting "subscribe" or "+1" in the issue queues. I think there are two reasons for this: 1) If you aren't logged in, you don't see the Follow button 2) It only appears at the top of the issue, but people are going to be most tempted to "subscribe" when they have read to the bottom of the thread and determined that the ...more »
Our issue guidelines for Drupal core (and other projects) explicitly state that users should submit steps to reproduce. However, many people overlook this.
Improve the form UX. When an issue is filed as a bug report, a field or template for steps to reproduce is automatically displayed.
* We've had the ability to add issue summaries to Drupal.org issues for 7-8 months now
* However, issue summaries are still used only sporadically
* The workflow to paste in the template for issue summaries is tedious
* Add a handy button to BU editor (which is already installed and configured) that will insert a summary template with the standard headers
The Component property of an issue is a single value currently. Often times, however, an issue spans over multiple components/topics, in which you have to figure out the primary component and usually assign the other ones as issue tags. Especially for Drupal core, an issue might be related to Node module, but is also changing plethora of CSS, JS, and markup. And oh, that very same issue might even try to "fix" an oddity ...more »
Just goin' out on a limb here, but...
Would it be helpful to see a related block of current issues related to a certain docs API page?
Does this initiative already exist?
The burgeoning issue queues are a big drag on the velocity of the core development. Significantly increased community participation is the most important part of the solution. One of the biggest obstacles to participation is on-boarding the prospective contributor. Even after a rousing presentation on why its so important, and the pretty darn good “how to get started as a contributor” pages on d.o, nothing works so ...more »