I have been thinking of that too, but I think we want quality patches - not quantity.<br><br><div><span class="gmail_quote">On 10/11/06, <b class="gmail_sendername">Arnab Nandi</b> <<a href="mailto:arnab@arnab.org">arnab@arnab.org
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br><br>You mention the Yellow Team and Green Team; I was wondering if we
<br>could implement a game in <a href="http://Drupal.org">Drupal.org</a> itself -- allow developers to<br>form "teams" (randomly assigned, to ensure fairness) and then get<br>"points" for getting issues resolved. We could have a leaderboard of
<br>sorts(reset bimonthly), promoting some fun-filled competition, which<br>motivates users to get stuff done!<br><br>-Arnab<br><br>On 10/7/06, Augustin (Beginner) <<a href="mailto:drupal.beginner@wechange.org">drupal.beginner@wechange.org
</a>> wrote:<br>><br>> Hello and welcome to the eighth edition of {Short issue queues need care}.<br>><br>> This week:<br>> 1} The Yellow Team rocks!<br>> a) What happened<br>> b) The result<br>
> 2} Featured short issue queues.<br>> 3} Why this report and how to cooperate?<br>><br>> *******************************************<br>> 1} The Yellow Team rocks!<br>> *******************************************
<br>><br>> My last report is already a month old: I apologize for the delay.<br>><br>> a) What happened<br>> ================<br>><br>><br>> Last time, I first pointed to this issue queue:<br>>
<a href="http://drupal.org/project/issues?projects=3060&states=14">http://drupal.org/project/issues?projects=3060&states=14</a><br>> I was saying that the Green Team rocks for finding a way to always keep their
<br>> queue short.<br>><br>> Then I pointed to this one:<br>> <a href="http://drupal.org/project/issues?projects=3060&categories=bug&states=8">http://drupal.org/project/issues?projects=3060&categories=bug&states=8
</a><br>> And I invited the Yellow Team, who is responsible for dealing with it, to do<br>> its best to review those issues so as to make their queue shorter.<br>><br>><br>> I posted the 7th edition of {Short issue queues need care} on the 4th of
<br>> September.<br>><br>><br>> And the Yellow Team responded in a way that astounded me: I did not expect the<br>> Team to mobilize to such an extent. The results were obvious within hours of<br>> the posting of the report.
<br>><br>> Other people were surprised, too. They are not subscribed to this list, so<br>> they didn't read the report... but they wondered why all of a sudden, on the<br>> 5th of September, they received so many feedbacks on so many old issues... :)
<br>> (I guess it was kind of freaky, for some....)<br>><br>> That is why I want to doubly apologize for delaying writing this report,<br>> because I feel I dropped the ball on this one! :(<br>><br>><br>
><br>><br>> The yellow queue above was just over 100 issues long on the 4th of September.<br>> Within 2 or 3 days, it was under 60 issues, and after a week it was under<br>> 50!!!<br>><br>> Today, it is back to over 100, though. But this is in itself an achievement: I
<br>> noticed a handful of developers from the White Team<br>> (the team dealing with issues without any patch attached:<br>> <a href="http://drupal.org/project/issues?projects=3060&categories=bug&states=1">
http://drupal.org/project/issues?projects=3060&categories=bug&states=1</a> )<br>> submitting scores of patches for review. There has been a strong drive to<br>> provide long standing bugs with patches.<br>>
<br>> So, many issues have shifted back and forth between the White, Red, Yellow,<br>> Green Teams, and the Yellow Team managed to hold its ground.<br>><br>> Well done!<br>><br>><br>> b) The result<br>
> ================<br>><br>><br>> The net result?<br>><br>> a) The Green Team is currently a bit overwhelmed and has been all month... ;)<br>> <a href="http://drupal.org/project/issues?projects=3060&states=14">
http://drupal.org/project/issues?projects=3060&states=14</a><br>> (21 issues, a handful - 4 - being old).<br>><br>> b) The total of ALL open issues has dropped 78 issues, from 2140 issues one<br>> month ago to 2062 today (down from 2222 issues mid-august!), which proves
<br>> that by focussing on short lists of issues, we avoid feeling discouraged and<br>> we do achieve something significant.<br>><br>><br>><br>> So, the objective for the Yellow Team is for its queue:<br>
> <a href="http://drupal.org/project/issues?projects=3060&categories=bug&states=8">http://drupal.org/project/issues?projects=3060&categories=bug&states=8</a><br>> to become and remain as short as the Green Team's one:
<br>> <a href="http://drupal.org/project/issues?projects=3060&states=14">http://drupal.org/project/issues?projects=3060&states=14</a><br>> !!<br>><br>><br>> Keep going: select one or two of the 7 queues featured below and show us what
<br>> you can do!<br>><br>><br>> Thanks for reading :)<br>><br>> and more importantly:<br>><br>> Thanks for contributing what you can to the Community.<br>><br>><br>><br>> *******************************************
<br>> 2} Featured short issue queues.<br>> *******************************************<br>><br>> There are 930 subscribers to this mailing list.<br>> Is it possible that 20-50 of those read this report and decide to work
<br>> together to lower the number of issues on each of the 7 queues featured this<br>> week?<br>><br>> Pick one list. See at the very end if you wish to officially 'adopt' one<br>> queue.<br>><br>> The number in parenthesis designs the number of issues 2 weeks old or more
<br>> (i.e. issues most likely forgotten and not being dealt with).<br>><br>><br>> (Queue #1) DRUPAL-4-6 critical issues:<br>> <a href="http://drupal.org/project/issues?projects=3060&versions=12052,11555,11262,10237,9739,9703,7696,7636,7578,5660,7407&priorities=1&states=1,8,13,14,2">
http://drupal.org/project/issues?projects=3060&versions=12052,11555,11262,10237,9739,9703,7696,7636,7578,5660,7407&priorities=1&states=1,8,13,14,2</a><br>> 18/06/2006 : 24 (19) issues.<br>> 25/06/2006 : 8 (5) issues.
<br>> 02/07/2006 : 5 (4) issues.<br>> 07/08/2006 : 5 (5) issues.<br>> 14/08/2006 : 5 (4) issues.<br>> 22/08/2006 : 4 (2) issues.<br>> 04/09/2006: 5 (1) issues.<br>> 07/10/2006: 5 (4) issues only.<br>> Those are really critical issues, already fixed in head and
4.7.<br>> A few junior developers (myself and others) have tried to help out, here, but<br>> we lack the knowledge to solve them, and the seniority to decide to downgrade<br>> those issues ('normal' issue, or 'won't fix').
<br>> A senior developer is needed to decide the fate of those issues. If they are<br>> indeed very critical, then a patch is needed soon: can you at least tell how<br>> they should be fixed.<br>><br>><br>>
<br>> (Queue #2) DRUPAL-4-7 critical issues:<br>> <a href="http://drupal.org/project/issues?projects=3060&versions=12050,11551,11252,10634,10412,10302,10273,10238,10195,9902,9842,9753,9728,10696&priorities=1&states=1,8,13,14,2">
http://drupal.org/project/issues?projects=3060&versions=12050,11551,11252,10634,10412,10302,10273,10238,10195,9902,9842,9753,9728,10696&priorities=1&states=1,8,13,14,2</a><br>> 18/06/2006 : 31 (19) issues.<br>
> 25/06/2006 : 12 (8) issues.<br>> 02/07/2006 : 7 (5) issues.<br>> 07/08/2006 : 19 (13) issues.<br>> 14/08/2006 : 7 (0) issues.<br>> 22/08/2006 : 7 (0) issues.<br>> 04/09/2006: 18 (0) issues.<br>> 07/10/2006: 23 (15) issues only!
<br>> New critical issues keep coming every week, because 4.7 is the most used<br>> version. Most are not really critical, though.<br>> (It should get better for Killes when 5.0 comes out).<br>><br>><br>> (Queue #3) HEAD critical bugs:
<br>> <a href="http://drupal.org/project/issues?projects=3060&versions=6487&categories=bug&priorities=1&states=1,8,13,14,2">http://drupal.org/project/issues?projects=3060&versions=6487&categories=bug&priorities=1&states=1,8,13,14,2
</a><br>> 18/06/2006 : 6 (1) issues.<br>> 25/06/2006 : 13 (1) issues.<br>> 02/07/2006 : 15 (1) issues.<br>> 07/08/2006 : 16 (3) issues.<br>> 14/08/2006 : 22 (5) issues.<br>> 22/08/2006 : 21 (6) issues.<br>
> 04/09/2006: 33 (8) issues.<br>> 07/10/2006: 18 (0) issues only!<br>> There are signs that people are readying HEAD for the first Beta release...<br>><br>> (Queue #4) DRUPAL-4-6 Patch Needs Review bugs:<br>
> <a href="http://drupal.org/project/issues?projects=3060&versions=12052,11555,11262,10237,9739,9703,7696,7636,7578,5660,7407&categories=bug&states=8">http://drupal.org/project/issues?projects=3060&versions=12052,11555,11262,10237,9739,9703,7696,7636,7578,5660,7407&categories=bug&states=8
</a><br>> 18/06/2006 : 26 (25) issues.<br>> 25/06/2006 : 26 (25) issues.<br>> 02/07/2006 : 25 (24) issues.<br>> 07/08/2006 : 24 (23) issues.<br>> 14/08/2006 : 24 (23) issues.<br>> 22/08/2006 : 20 (2) issues.
<br>> 04/09/2006: 11 (0) issues.<br>> 07/10/2006: 8 (8) issues.<br>> They need to be bumped to 'cvs', if the bug still exists in HEAD.<br>> If the bug hasn't been fixed yet, try to reroll the patch for head, or else
<br>> set as "patch needs work".<br>><br>><br>> (Queue #5) DRUPAL-4-7 Patch Needs Review bugs:<br>> <a href="http://drupal.org/project/issues?projects=3060&versions=12050,11551,11252,10634,10412,10302,10273,10238,10195,9902,9842,9753,9728,10696&categories=bug&states=8">
http://drupal.org/project/issues?projects=3060&versions=12050,11551,11252,10634,10412,10302,10273,10238,10195,9902,9842,9753,9728,10696&categories=bug&states=8</a><br>> 18/06/2006 : 17 (5) issues.<br>> 25/06/2006 : 16 (7) issues.
<br>> 02/07/2006 : 21 (8) issues.<br>> 07/08/2006 : 15 (11) issues.<br>> 14/08/2006 : 15 (4) issues.<br>> 22/08/2006 : 12 (5) issues.<br>> 04/09/2006: 9 (3) issues.<br>> 07/10/2006: 11 (2) issues only.
<br>> Make sure to note if the bug has been fixed in HEAD already: it would be silly<br>> to have a fix in 4.7, to see the bug reappear when 5.0 comes out.<br>><br>> (Queue #6) HEAD Patch Needs Review bugs:<br>
> <a href="http://drupal.org/project/issues?projects=3060&versions=6487&categories=bug&states=8">http://drupal.org/project/issues?projects=3060&versions=6487&categories=bug&states=8</a><br>> 18/06/2006 : 72 (67) issues.
<br>> 25/06/2006 : 71 (67) issues.<br>> 02/07/2006 : 77 (66) issues.<br>> 07/08/2006 : 72 (59) issues.<br>> 14/08/2006 : 88 (59) issues.<br>> 22/08/2006 : 81 (57) issues.<br>> 04/09/2006: 82 (64) issues.
<br>> 07/10/2006: 86 (54) issues.<br>> As you see, many issues are old (over 2 weeks old: 64 issues), so we have the<br>> choice between :<br>> re-rolling the patch for current head,<br>> set as code needs work,
<br>> or set as already fixed if appropriate.<br>><br>> (Queue #7) Your own list of Patch Needs Review bugs:<br>> <a href="http://drupal.org/project/issues?projects=3060&categories=bug&states=8&participated=your_drupal_user_name">
http://drupal.org/project/issues?projects=3060&categories=bug&states=8&participated=your_drupal_user_name</a><br>> 1) Follow the search link above,<br>> 2) In the URL, replace "your_drupal_user_name" with your actual user name.
<br>> 3) Reload and bookmark the page.<br>><br>> Those are issues you have already participated in, and you should already know<br>> the context. Help the person preparing the patch to eventually come up with a
<br>> patch that can be RTBC.<br>> Obviously, if there are many results to the query, start from those issues you<br>> are the most familiar with...<br>> If everyone does this, the result will be seen in the queues #4, #5 and #6
<br>> above.<br>><br>><br>><br>><br>> *******************************************<br>> 3} Why this report and how to cooperate?<br>> *******************************************<br>><br>> There are now over 2000 issues in the queue.
<br>> The figure sounds daunting: how can a very few volunteer developers deal with<br>> such a huge amount of bugs?<br>><br>> The point is that we don't need to worry of the whole issue queue, but by<br>> getting somewhat more organized, the most important of those issues can be
<br>> definitively dealt with.<br>><br>> To start with, there shouldn't be anything critical within the Drupal project<br>> issues. Critical bugs must be dealt as a matter of priority. But one can get<br>> easily discouraged when facing 4 four pages of critical issues.
<br>> The first step is therefore to sort out what is really critical from what is<br>> not.<br>> Having a shortlist of what is really critical, two or three developers can<br>> focus on a single issue, helping each other, so that one week later there is
<br>> one really critical issue less. Similarly, 10-12 developers could get rid of<br>> 3-4 critical issues and in a few weeks, the list of critical issues would be<br>> down to almost nothing (only 1-2 issues caused by a large patch recently
<br>> introduced in head, for example).<br>><br>><br>><br>> If you wish to participate in tackling one of the 7 short issue queues<br>> featured here, please reply to the list, quoting only the issue you wish to
<br>> 'adopt', changing also the subject title of your email to reflect the queue<br>> you have chosen.<br>> Hopefully, two or three more developers will reply to you, saying they want to<br>> help you with the issues in that same queue.
<br>><br>><br>><br>> Thank you to all the volunteers for your cooperation.<br>><br>> Blessings,<br>><br>> Augustin.<br>><br>><br>><br>><br>><br>><br>> --<br>> <a href="http://www.wechange.org/">
http://www.wechange.org/</a><br>> Because we and the world need to change.<br>><br>> <a href="http://www.reuniting.info/">http://www.reuniting.info/</a><br>> Intimate Relationships, peace and harmony in the couple.
<br>><br><br><br>--<br><a href="http://www.arnab.org">http://www.arnab.org</a><br></blockquote></div><br>