Bounties
What are Bounties?
Bounties are an opportunity to get a little bit [1] of money while helping out the development of BoofCV and the community as a whole. Anyone can participate [2] and if the submission is accepted as completed your work will be added to BoofCV and you will get the bounty! Each bounty is broken up into two amounts, base and bonus. The base is the amount you will receive no matter what if you submission is accepted. The bonus is a variable amount that is decided based on the submission's overall quality and how well it meets all the requirements.
It's advised that you publicly announce on BoofCV's message board that you're working on a bounty and provide a link to your project page. This is a collaboration not a competition in the end! Feel free to place comments in the bounty's Google Doc description for clarifications.
|
 |
[1] The bounties are paid out of pocket and are not intended to compete with what you would get for a commercial contract in the US. Think of it as a nice bonus for a hobby of yours. They are also significantly more than most open source bounties as is.
[2] Read the rules below. There are rare exceptions.
Bounties: Infrastructure
| Task | Max Award | Base |
|---|---|---|
| Generate Webpage Javadoc with Gradle | $75 | $75 |
| Example/Demonstration Application Enhancements | $150 | $100 |
| Website for Generating Fiducials and Calibration targets | $200 | $100 |
| Improved 3D Viewer | $200 | $50 |
| DeepBoof: Load Caffe Models | $350 | $200 |
| Assisted Calibration in ROS | $150 | $100 |
Awards are specified in USD. Max award is the base amount plus the maximum bonus.
Bounties: Algorithms
| Task | Max Award | Base |
|---|---|---|
| AruCo markers in BoofCV | $320 | $120 |
| Improve Supervised Watershed | $150 | $100 |
| Improved Image Stitching | $275 | $150 |
| DeepBoof: 40% Speed Improvement to Convolution Code | $150 | $150 |
| Unroll Convolution for Interlaced Images | $150 | $75 |
| Convolution Runtime Regression Tests | $50 | $50 |
| GMM Background Model | $175 | $75 |
Awards are specified in USD. Max award is the base amount plus the maximum bonus.
Code Requirements
Code submitted to a bounty needs to meet applicable requirements below for quality control purposes. Failure to meet a requirement will be pointed out in the code review. Minor issues are likely to be allowed but will affect your bonus.
- All submitted code must have good unit test coverage
- Unit tests should take at most 50ms to complete each
- Current unit tests take on average 10ms each
- You should shoot for 2ms or less
- When applicable, provide a usage example with example data
- All code and comments must be in English
- No merge conflict with latest SNAPSHOT
- All unit tests must pass
- Regression Tests for Speed and Stability
- Only required when specifically mentioned in detailed description
- They will be placed into ValidationBoof
- Use existing internal functionality
- Don't reinvent the wheel unless there is a good reason
- Ask if you don't know if that capability exists already!
- Adding new external libraries is discouraged and will need to be justified
- We like to keep BoofCV as small as possible
- Getting external developers to fix bugs or accept patches is often a tedious procedure and slows down development
- Code should minimize the creation of new memory and should recycle memory as much as possible
- Ask for examples if you aren't sure how to do this
Rules
Effective as of December 30, 2016
Definitions
- Awardee, refers to the person receiving the bounty
- Award, refers to the amount of money award for completing a bounty.
- Internal Bounty, A bounty which involve submitting and donating new code for integration into BoofCV
- External Bounty, A bounty which does not involve adding code to BoofCV
- Maintainers, see list of people here.
Submission
Submission for Internal Bounties Internal bounties involve adding new code to BoofCV and related projects.
- To qualify for a bounty you must submit a pull request on GitHub against the latest SNAPSHOT of BoofCV with your code
- The pull request must specify which bounty it is for and who will receive the award
- Donating code without declaring intent for a bounty voids your claim for any bounties as a result of that code donation
- All of the code included with the pull request must be owned by you
- Before it can be accepted the copyright/ownership of the code must be transferred over to the BoofCV project
- Transferring of ownership over to BoofCV project involves the following:
- The code will be released publicly under an Apache 2.0 license
- Ownership will be transferred over to Peter Abeles, see Donating to BoofCV for why
- The code is considered accepted once it has been merged into the master repository on GitHub
- Final acceptance of a submission is at the sole discretion of BoofCV's maintainer
Submission for External Bounties External submissions are for modifications external to the main code base.
- Please see the Google Doc description for how to complete the task as each one is different
- Examples:
- Fixing code in another project and getting the patch accepted
- Creating and hosting a website while making the code publicly available
- Creating your own project and releasing it as an independent open source project hosted publicly
Awarding
This section describes how the bounty will be awarded.
- After the code has been accepted the submitter qualifies to receive the award
- See submission above for what it means for a submision to be 'accepted'
- The amount of the award is specified on the wiki's Bounties page
- If the award amount on the page changes then the largest award after the earliest of the following events will be used:
- Announcement of intent to pursue the bounty by awardee on BoofCV message board
- Submission of the pull request with qualifying code
- Mistakes happen and type-os may or may not be honored. Please let us know if you see anything that looks suspicious!
- The final award amount will be the base award plus the bonus
- The amount of bonus will vary between $0 and the maximum specified on the bounties webpage
- If the award amount on the page changes then the largest award after the earliest of the following events will be used:
- Bounties will be awarded to an individual when it is legal to do so within the US and their home country
- Void where prohibited
- The awardee is responsible for all taxes and fees associated with the receipt of the award
- All bounties are specified in US dollars
- No bounty will be awarded more than once
- If multiple qualified submissions are received then the time stamp of the e-mail/pull request that announces completion will be used
- Only one individual can receive a bounty
- If multiple individuals contributed it is up to them to decide who will receive the payment and distribute it to the group
- If no agreement can be reached then the person who created the first repository will receive the award
- A bounty will be award using PayPal
- The awardee has 45 days from the date of pull request acceptance to fix any issues with receipt of award
- Falsifying time stamps or other attempts to mislead will result in the forfeiture of all bounties
- If a bounty cannot be sent to an individual the individual may select from the charities listed below for a donation to be made in their name or they may forfeit the award.
