Bugathon

Jump to: navigation, search

The Moodle bugathon started on November 12th 2007 and ended on February 12th 2008 (3 months later).

Congratulations to all our prize winners and a big thank you to everyone who took part in the bugathon - see the Bugathon prize winners announcement for the results.


There are prizes in four categories (see below). The cash prizes are from Moodle.com and the iPods are from Bryan Williams of Remote-Learner.net. (If you want to contribute towards the prizes for future events, please use the donation page).

The judges decision is final. Developers currently employed by Moodle.com are not eligible for prizes but will be competing anyway. :-) We reserve the right to disallow someone if it becomes obvious they are cheating the system (eg by filing fake reports, setting up fake accounts, reassigning bugs from other people after they are done etc).

Note in all this I'm referring to bugs specifically (ie problems that need fixing) and not wider issues like feature requests! (We'll get onto those again once we clean up some of these bugs).

Some general documentation about the tracker.


Most bugs resolved

The first person to attach a stable patch to a bug in the tracker, or submit a correctly-labelled-and-merged fix to CVS is deemed to be the resolver of a bug. Resolved bugs must be verified by an independent QA tester to be counted.

Points are assigned like this: 5 points for every bug + 1 point for every VOTE on that bug (so everybody vote for your favourite bugs!)

Developers should keep track of the bugs they fix here in the wiki (official developers can generate this from the tracker itself, but others will have to maintain it manually).


Prizes:

  • #1 Developer: AU$1000 (approx $US940) + Apple iPod Touch
  • #2 Developer: AU$500
  • #3 Developer: AU$250
  • Next 5 Developers: Choice of any item from the Moodle Shop
  • Any other developer who fixes more bugs than the best-performing Moodle HQ programmer can get something from the Moodle Shop too. :-)


Candidates (add yourself here!)

Most fixes verified

To join the testing group in the tracker, email Michael Blake at support@moodle.com so he can add you.

This allows you to assign yourself as a QA person for any bug. After testing that a "Resolved" bug actually is fixed or works as the developer reported, you should change the status to Closed and make a comment on the bug to say what you saw.

Keep track of the bugs you've verified in the Bugathon wiki page (this is easy to generate from the tracker).

Prizes:

  • First prize: AU$250 + Apple iPod Nano
  • Second prize: AU$100
  • Third prize: Choice of any item from the Moodle Shop


Candidates (add yourself here!)


Most duplicates identified

If you find a bug that is the same as another bug (read them very carefully to make sure because sometimes this is deceptive) then create a new link between the two bugs marking the later one as a DUPLICATE. If you can, close the later bug too.

You'll need to keep a list of your duplicate bugs in the wiki to collect the prize (there is not a way to generate this info from the tracker, unfortunately).

Prizes

  • First prize: AU$250 + Apple iPod Nano
  • Second prize: AU$100
  • Third prize: Choice of any item from the Moodle Shop


Candidates (add yourself here!)


Most new bugs filed

New bugs are always welcome. Some people in our community are very good at finding them too, so this category is for them. Obviously bugs should be real fixable problems, and should not be duplicates of others already filed. All new bugs should contain full steps to reproduce the problem.

Keep track of the bugs you've filed in the Bugathon wiki (this is easy to generate from the tracker).

Prizes:

  • First prize: AU$250 + Apple iPod Nano
  • Second prize: AU$100
  • Third prize: Choice of any item from the Moodle Shop


Candidates (add yourself here!)