[development] How to post bug reports and patches

Steven Surowiec steven at digitalpulp.com
Fri Oct 31 16:42:28 UTC 2008

Just to propose an alternative idea to the Digg-like voting system, how 
about restricting commiters to only working on specific issues? So 
instead of being a free-for-all where people just go in and pick and 
choose the issues that they find the most interesting, important, or 
fun, to work on (as this is largely personal opinion), have it setup so 
they can only work on issues assigned to them by some one with greater 
permissions then them. I know, from experience, that this is how many 
commercial software shops operate when it comes to bug reports and 
feature requests and it can be quite efficient. The only remaining issue 
is to make sure the proper issues are assigned, and assigned to the 
proper person.

I personally feel a lot of the problems being discussed tend to stem 
from a free-for-all setup where people can work on whatever issues they 
like. Perhaps treating Drupal as a regular commercial product would be 
more beneficial (although I do like the voting idea, I haven't seen that 
idea proposed for something like this before).

As a disclaimer, while I've been using Drupal for over a year, I'm still 
new to the list and have not been very active in the community yet, so 
there is a good chance I don't know what I'm talking about in regards to 
how bugs are currently handled. But from an outsiders perspective this 
is how it appears.

Tomas Fulopp wrote:
> I think this is a very good idea - potentially accelerating testing 
> and committing the most desperately needed patches.
> On Fri, Oct 31, 2008 at 4:42 PM, Darren Oh 
> <darrenoh at sidepotsinternational.com 
> <mailto:darrenoh at sidepotsinternational.com>> wrote:
>     Could we add a Digg-like button to issues that would promote them
>     to a popular issues page?
>     On Oct 31, 2008, at 10:46 AM, Earnie Boyd wrote:
>         The only solution to the issue is for every
>         development at drupal.org <mailto:development at drupal.org> user to
>         keep a watchful eye to
>         http://drupal.org/project/issues?projects=3060&states=8&priorities=&categories=&users=
>         <http://drupal.org/project/issues?projects=3060&states=8&priorities=&categories=&users=> to
>         review the patches submitted.  Testing and watching for coding
>         standards then setting the status to RTBC so that the
>         committers can then have a look.
>         I created myself a service that will notify me of the changes
>         via an aggregated feed and notification by email of the
>         changes.  The feed is scheduled for once every ten minutes so
>         that I keep up to date.  Sure I might miss one or two that
>         someone else has set to the status something else but then
>         that one is already reviewed.
>         If your interested, feel free to use the service with the
>         understanding that the service is still in alpha/beta stage
>         but the data is coming in like mad.  There are between 5 to 50
>         requested reviews in a day.  I can't get to them all.  The
>         service is hosted at http://r-feed.com and is accepting
>         registrations for you convenience.

More information about the development mailing list