Bughunt competition

By chx on 8 Dec 2005 at 14:26 UTC

With the release of 4.7.0 beta1, I will be co-sponsoring a bug hunt competition to be concluded with the release of 4.7.0. The prize will be a combination of 150USD from the Google Summer of Code and an additonal 200USD donated by me.

I will count the opened, non-duplicate issues marked as "CVS" or "4.7..." in the Drupal project issue's tracker between now and 4.7.0 are released. First place will be 200USD, second will be 100USD, and third will be 50USD. In reality, anyone using Drupal will be the winner as the more bugs found and fixed before 4.7.0 means a stronger build for every user.

People listed in MAINTAINERS.txt are not eligible (that includes me). The reason for this that I'd like to get more new contributors.

Please include PHP version in all your bug reports, for more see http://drupal.org/node/317.

In any debate, I decide.

Here are the Seven Tips of Dries to Find More Bugs:

Use CVS HEAD; as we fix things, we might introduce new bugs. Spot them before other people can.
Take advantage of the slightly disruptive changes in the recent MySQL and PHP versions: like, use MySQL 5 in strict mode with PHP 5.1.
Use Drupal 4.7 beta1 or CVS HEAD on a production site with thousands of users; they'll do all the work for you. Not advised. ;)
Differentiate your test setup: use the multi-site setup with database prefixing, use PostgreSQL, or focus on the less popular modules.
Help upgrade contributed themes and modules. As soon you start touching code, you'll be able to find code/API bugs that are not triggered by any of the core modules.
Migrate an existing Drupal 4.6 site and see if everything continues to work. Having a real-life database to start from tends to be better than having to start with an empty database.
Take advantage of Drupal's error logging: periodically check your logs for 404s, errors, etc.

Comments

Great initiative!

robertDouglass commented 9 December 2005 at 08:10

Thanks Károly, this is right in the spirit of the Summer of Code project, and a fine use of the funds that we received from Google.

Just to remind; bugs are problems in Drupal -- things that don't work right, are broken, or have unexpected side-effects. These differ from feature requests, which are things that one would like to see in Drupal to make it better. I bring this up because the two often get confused.

- Robert Douglass

-----
My sites: HornRoller.com, RobsHouse.net

I post your competition in

Lupin3rd commented 9 December 2005 at 09:52

I post your competition in drupal.it. I hope that italian people help in the bug's research...

---
Visita drupal.it, la comunità italiana di Drupal.

I'll do my part, but...

Renirtor commented 9 December 2005 at 17:24

I hope there will be very few, not critical, bugs! :P

--
Thank you, http://drupal.org !
E per la traduzione un grosso grazie al team di http://www.drupalitalia.org

weighted?

bertboerland commented 9 December 2005 at 14:47

first of all, kudo's to people who can mix the spirit of OSS and bringing in money while still holding true to the OSS principles. Maybe you want to add "weighted" bugs.

Critical bugs (moderated by the community and maybe you) will gain 3 points, lesser critical 2 and 1. I dont think this will lead to more higher ranking bugs, it wont do drupal or the bugreporter any good.

--
groets
bertb

--
groets
bert boerland

no

chx commented 9 December 2005 at 15:06

Too complicated. Needs project module changes.
--
Read my developer blog on Drupal4hu. | The news is Now Public

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

Different weights

Cvbge commented 9 December 2005 at 20:22

It could be weighted, but IMO:
3 points for commited patch
1 point for not-duplicate bug report
or similar :)

OTOH... I'm sure, that as allways with money, there will be problems with people who feel the winners were not choosed fairly...

--
Polska strona o Drupalu: http://drupal.cvbge.org

no problems

chx commented 9 December 2005 at 21:23

In any debate, I decide.

Noone is forcing you to play by this rule, you can apply for the usual fee for bugreports :P
--
Read my developer blog on Drupal4hu. | The news is Now Public

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

Cvbge's only eligible for

Wesley Tanaka commented 10 December 2005 at 10:35

Cvbge's only eligible for the usual fee anyway. =)

Seven tips to increase your chances

Dries commented 10 December 2005 at 08:48

Use CVS HEAD; as we fix things, we might introduce new bugs. Spot them before other people can.
Take advantage of the slightly disruptive changes in the recent MySQL and PHP versions: like, use MySQL 5 in strict mode with PHP 5.1.
Use Drupal 4.7 beta1 or CVS HEAD on a production site with thousands of users; they'll do all the work for you. Not advised. ;)
Differentiate your test setup: use the multi-site setup with database prefixing, use PostgreSQL, or focus on the less popular modules.
Help upgrade contributed themes and modules. As soon you start touching code, you'll be able to find code/API bugs that are not triggered by any of the core modules.
Migrate an existing Drupal 4.6 site and see if everything continues to work. Having a real-life database to start from tends to be better than having to start with an empty database.
Take advantage of Drupal's error logging: periodically check your logs for 404s, errors, etc.

I love this comment

chx commented 10 December 2005 at 16:33

Dries, thanks for the tips. I am copying it to the original post.
--
Read my developer blog on Drupal4hu. | The news is Now Public

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

Results so far

chx commented 8 January 2006 at 10:35

Total number of issues since beta1:

print db_result(db_query("SELECT COUNT(n.nid) c FROM {node} n INNER JOIN {users} u ON n.uid = u.uid INNER JOIN {project_issues} p ON p.nid = n.nid WHERE n.created > 1133996400 AND p.pid = 3060 ORDER BY c"));

Number of issue nodes created against Drupal project -- duplicates are not yet deleted and noone is excluded:

$result = db_query_range("SELECT name,  COUNT(n.nid) c FROM {node} n INNER JOIN {users} u ON n.uid = u.uid INNER JOIN {project_issues} p ON p.nid = n.nid WHERE n.created > 1133996400 AND p.pid = 3060 GROUP BY n.uid ORDER BY c DESC, n.uid DESC", 0, 10);
while ($row = db_fetch_object($result)) {
  $items[] = $row->name.' '.$row->c;
}
print theme('item_list', $items);

note that this a PHP comment, so results will change from time to time. So far, it seems that wtanaka won (75 nodes!), Ber is the second with 14 and the third place is not yet determined, as markus_petrux, m3avrck, drumm all have 12 nodes. In case there is a draw

I'd like to get more new contributors.

so people with higher UIDs win.

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

The code

chx commented 8 January 2006 at 10:41

The code that generated the post is:

$result = db_query_range("SELECT name,  COUNT(n.nid) c FROM {node} n INNER JOIN {users} u ON n.uid = u.uid INNER JOIN {project_issues} p ON p.nid = n.nid WHERE n.created > 1133996400 AND p.pid = 3060 GROUP BY n.uid ORDER BY c DESC, n.uid DESC", 0, 10);
while ($row = db_fetch_object($result)) {
  $items[] = $row->name.' '.$row->c;
}
print theme('item_list', $items);

--
Read my developer blog on Drupal4hu. | The news is Now Public

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

This is a great idea. But

Dave Cohen commented 8 January 2006 at 10:53

This is a great idea. But how about a prize for the most approved patches?

Patching is easy

chx commented 8 January 2006 at 15:02

Once I know what's the bug, a fix rarely lasts an hour. Mostly it's a lot less. It's a localized problem. Most patches are just a handful of lines. Catching bugs IMO are much more important.
--
Read my developer blog on Drupal4hu. | The news is Now Public

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

Does this take into account

m3avrck commented 14 January 2006 at 07:42

Does this take into account bugs that are created and the marked as duplicates? And what about issues that are created as bugs but turn out not to be bugs?

Just wondering how the system works since I'm not sure the query is *that* smart :-)