Difference between revisions of "Bounties"
From SME Server
Jump to navigationJump to searchm (Some more wikification for the numbered list) |
|||
| Line 29: | Line 29: | ||
To successfully claim your prize you need to follow a few rules: | To successfully claim your prize you need to follow a few rules: | ||
| − | + | # All code submitted for a bounty must be without any known intellectual property limitations. Furthermore, it must be submitted under the same license as the application to which it will be applied (for example, GPL for SME Server). | |
| − | + | # The code must be accepted and committed into the development branch by the module's maintainers before any prize will be awarded. | |
| − | + | # Patches must conform to SME Server coding and template/db standards. The code must work and work elegantly (i.e., no hack jobs). | |
| − | + | # In the case of multiple submissions for a single bounty, the judging panel will select and award the highest quality one. | |
| − | + | # Group submissions must designate a lead person who will submit the claim on behalf of the group. | |
| − | + | # All bounty awards or rejections are at the sole discretion of the judging panel. We may refuse to award a bounty to anyone for any reason at any time (although there will certainly be a valid reason, since it is in everyone's interest for the bounty process to work smoothly). | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Once you have submitted your code and it has been accepted into CVS, just let the developers who handled the patch know that you're claiming the bounty. Prizes will be paid using PayPal. | Once you have submitted your code and it has been accepted into CVS, just let the developers who handled the patch know that you're claiming the bounty. Prizes will be paid using PayPal. | ||
Revision as of 12:28, 5 August 2009
SME Server Bounties
The hunt is on!
If simply contributing to an Open Source project is not enough, you now have an added incentive. The SME Server Project has organized an ongoing Bounty Hunt. Listed below are various tasks we would like to see completed or features which have been requested. If you have suggestions for possible bounties, look at the current list of enhancement requests and Submit yours if it is not already listed.
| Component | Task | Bug No. | Bounty Prize | Sponser(s) |
|---|---|---|---|---|
| e-smith-base+ldap | Integrate LDAP auth in the core distribution | Bug 4590 | xxx | Name or Names go here |
Rules
To successfully claim your prize you need to follow a few rules:
- All code submitted for a bounty must be without any known intellectual property limitations. Furthermore, it must be submitted under the same license as the application to which it will be applied (for example, GPL for SME Server).
- The code must be accepted and committed into the development branch by the module's maintainers before any prize will be awarded.
- Patches must conform to SME Server coding and template/db standards. The code must work and work elegantly (i.e., no hack jobs).
- In the case of multiple submissions for a single bounty, the judging panel will select and award the highest quality one.
- Group submissions must designate a lead person who will submit the claim on behalf of the group.
- All bounty awards or rejections are at the sole discretion of the judging panel. We may refuse to award a bounty to anyone for any reason at any time (although there will certainly be a valid reason, since it is in everyone's interest for the bounty process to work smoothly).
Once you have submitted your code and it has been accepted into CVS, just let the developers who handled the patch know that you're claiming the bounty. Prizes will be paid using PayPal.
