RFEBounty

From GridWiki
Revision as of 19:46, 12 January 2009 by Dant (talk | contribs) (New page: == Grid Engine H2Y09 RFE Bounty == One of the greatest things about Grid Engine is the community. We have a vibrant community with lively mailing lists and an active wiki. What we don't...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Grid Engine H2Y09 RFE Bounty

One of the greatest things about Grid Engine is the community. We have a vibrant community with lively mailing lists and an active wiki. What we don't have, though, is a significant amount of community contributions to the project, with the expect of some notable contributions like the array task dependencies. There are probably multiple reasons for that, one of which is the fact that we, the engineering team, don't make it clear with issues we are planning to tackle. We're going to fix that, and we're going to throw in some added incentive to boot.

Here's the deal. Below is a list of RFEs that the engineering team will not address in the next six months. They have been hand selected from the full list of open RFEs as issues that are 1) useful, 2) interesting, and 3) appropriately scoped for community contribution. The first four community members who resolve one or more of these RFEs will receive a laptop. Yes, I just said a laptop. Everyone else who resolves one of the listed RFEs will receive an iPod. And that's one laptop/iPod per RFE, with a max of one total award per person, i.e. the award for a team contribution will will only be a single item, and you can't earn more than one award.

Let's be a little more specific. Resolving an RFE means taking it through the full development cycle. You'll start by writing a spec for your proposed changes. Once your spec is approved by the engineering team, you will write and test your code. Included in the testing is writing and contributing a test suite test. Once your code and test are written and working, you'll have to have both reviewed by a member of the engineering team. After the review, you'll make whatever changes your reviewer requested and then have the reviewer sign off on those changes. After testing again, just to be sure, you can then send in your changes to be committed. The commit time is how we will determine who the first four contributors are.

You can find more information about the laptops and iPods at the bottom of this page, along with the legal details about the contest. What follows is a list of the RFEs, sorted by issue number, with links to the issues in Issuezilla. The dev mailing list is your friend. If you have questions about a particular RFE or the source code in general, that's where you should start. Good luck, God speed, and may the Schwarz be with you.