Friday, 21 December 2012

bugs in programming

I have decided to try something different next year and also take a leaf out of the software industry. I am going to pay for bugs in the programming textbook that we use. I am going to use the bug Bounty guidelines that Firefox have put in place
This will be my own bug bounty, but instead of money, I will be offering the rare chocolate fish as payment.
I have been working on twitter to find a supplier of chocolate fish, and the best I have so far is 40 for $25.

General Bounty Guidelines

Head Geek will pay a bounty for certain bugs, as detailed below. All bugs must follow the following general criteria to be eligible:
  • Bug must be original and previously unreported.
  • Submitter must not be the author of the buggy code nor otherwise involved in its contribution to the DTG project (such as by providing check-in reviews).
  • Students of the DTG course and its subsidiaries are ineligible.
Head Geek reserves the right to not give a bounty payment if we believe the actions of the reporter have endangered the security of the DTG.

If two or more people report the bug together the reward will be divided among them.

Payment will be a chocolate fish.


Please file a bug describing the bug. We encourage you to attach a "proof of concept" testcase or link to the bug that demonstrates the code fail. While not required, such a testcase will help us judge submissions more quickly and accurately.

No comments: