Difference between revisions of "Bounties"

From BoofCV
Jump to navigationJump to search
m
m
 
(74 intermediate revisions by the same user not shown)
Line 1: Line 1:
Bounties are an opportunity to get a little bit of money while helping out the development of BoofCV and the community as a whole.  Anyone [1] can submit code they own and donate it to the project for one of the tasks below.  If the code is accepted 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 complete the task and the code is accepted.  The bonus is a variable amount that is decided based on the quality of the code and how much time was required to integrate it in.
New bounties are being worked on. There have been a lot of changes since the bounties were first written and it needs to be updated. An announcement will be made when this page is updated again.  2026-Jun-01


THIS HASN'T STARTED YET


== Bounties: Infrastructure ==


{| class="wikitable sortable" style="width:600px;"
= Code Requirements =
!style="width: 70%; "| Task
!style="width: 15%; text-align:center;"| Base
!style="width: 15%; text-align:center;"| Max Bonus
|-
| Generate Webpage Javadoc with Gradle
| $50
| $20
|-
| Improvements to Example/Demonstration Application
| $100
| $50
|-
| Website for Generating Fiducials and Calibration targets
| $100
| $100
|-
| Improve 3D Point Cloud Viewer
| $50
| $50
|}


== Bounties: Algorithms ==
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.


{| class="wikitable sortable" style="width:600px;"
* All submitted code must have good unit test coverage
!style="width: 70%; "| Task
!style="width: 15%; text-align:center;"| Base
!style="width: 15%; text-align:center;"| Max Bonus
|-
| AruCo markers in BoofCV Leveraging Existing
| $100
| $100
|-
| Improve Supervised Watershed
| $50
| $50
|-
| Improved Image Stitching
| $100
| $100
|-
| GMM Based Background Model
| $50
| $50
|-
| People Detector
| $100
| $200
|-
| Face Detector
| $100
| $200
|}
 
== Code Requirements ==
 
To qualify for the award you must meet all the minimum requirements specified in the project description and when applicable the following is also required.  Code might be accepted even if it doesn't meet all of the "requirements".  If that does happen then the bonus amount is likely to be reduced or removed completely.
 
* All submitted code must have unit tests
* Unit tests should take at most 50ms to complete each
* Unit tests should take at most 50ms to complete each
** Current unit tests take on average 10ms each
** Current unit tests take on average 10ms each, shoot for 2ms or less
** You should shoot for 2ms or less
* When applicable, provide a usage example with example data
* You must provide a usage example with example data
* All code and comments must be in English
* Algorithms must be integrated into existing regression tests in [https://github.com/lessthanoptimal/ValidationBoof ValidationBoof] or have new ones created
* All code must be in pure Java unless specified otherwise
** Regression tests for speed and stability will be required
* No merge conflict with latest SNAPSHOT
* No merge conflict with latest SNAPSHOT
* All unit tests must pass
* Maximize use of existing internal functionality
** Not sure if a capability already exists? Ask!
* Adding new external libraries is discouraged and will need to be justified
* Code should minimize the creation of new memory and use a single thread


Suggestions:
= Rules =
* Use of existing internal functionality is highly encouraged
** 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 is often a tedious procedure and slows down development
* Code shoukd 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 January 3, 2017


Definitions
''Definitions''
* Awardee, refers to the person receiving the bounty
* Awardee, refers to the person receiving the bounty
* Award, refers to the amount of money award for completing a 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 [[BoofCV Developers|here]].
== Submission ==
''Submission for Internal Bounties''  Internal bounties involve adding new code to BoofCV and related projects.


Submission
* To qualify for a bounty you must submit a pull request on [http://github.com GitHub] against the latest [https://github.com/lessthanoptimal/BoofCV/tree/SNAPSHOT SNAPSHOT] of BoofCV with your code
* To qualify for a bounty you must submit a pull request on [http://github.com GitHub] against the latest [https://github.com/lessthanoptimal/BoofCV/tree/SNAPSHOT SNAPSHOT] of BoofCV with your code
* The pull request must specify which bounty it is for and who will receive the award
** 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
* 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
* Code's copyright formust be reassigned
** The code will be released publicly under an Apache 2.0 license
** Copyright will be transferred over to Peter Abeles, see [[Donating to BoofCV]] for why
** Your name/organization will be listed as an author after donating
* The code is considered accepted once it has been merged into the master repository on GitHub
* The code is considered accepted once it has been merged into the master repository on GitHub
* Transferring of ownership over to BoofCV project involves the following:
* Final acceptance of a submission is at the sole discretion of BoofCV's maintainer
** The code will be released publicly under the open source licensed used by BoofCV at the time
*** Which is Apache 2.0 at the time of this writing
** Since BoofCV is not a legal entity the code will be owned by Peter Abeles
** In the future the code may be transferred to another individual or group (e.g. BoofCV becomes a registered non-profit)
** The license can only be changed to an open source license approved by the [https://opensource.org/licenses Open Source Initiative] in the future


Awarding of a Bounty
''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
* 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
* All bounties are specified in US dollars
* No bounty will be awarded more than once
* 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
* Only one individual can receive a bounty
** If multiple individuals contributed it is up to them to decide who will receive the payment
** If multiple individuals contributed it is up to them to decide who will receive the payment and distribute it to the group
* After code has been accepted an individual qualifies to receive the award
** If no agreement can be reached then the person who created the first repository will receive the award
** The award is specified on the wiki Bounties page
* A bounty will be award using [https://www.paypal.com PayPal] and/or [https://www.bountysource.com/ bountysource]
** Only award amounts set by Peter Abeles are valid
* If the bounty is cross posted to bountysource then a portion of the award will be collected from there.
** The final award amount will be the base award plus the bonus
* The awardee has 45 days from the date of pull request acceptance to fix any issues with receipt of award
** The amount of bonus will vary between $0 and the maximum specified on the bounties webpage
* Falsifying time stamps or other attempts to mislead will result in the forfeiture of all bounties
* Bounties will be awarded to an individual when it is legal to do so within the US and their home country
* 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.
* A bounty will be award using [https://www.paypal.com PayPal]
* The awardee has 30 days from the date of acceptance to fix any issues with payment
* If a bounty cannot be sent to an individual due to legality or inability to receive money transfers through PayPal a donation will be made in their name to a charity in the list below for amount of the award
** [https://www.eff.org/ Electronic Frontier Foundation]
** [https://www.eff.org/ Electronic Frontier Foundation]
** [https://wikimediafoundation.org Wikimedia Foundation]
** [https://wikimediafoundation.org Wikimedia Foundation]
** [http://www.redcross.org/donations/ways-to-donate American Red Cross]
** [http://www.redcross.org/donations/ways-to-donate American Red Cross]

Latest revision as of 06:59, 2 June 2026

New bounties are being worked on. There have been a lot of changes since the bounties were first written and it needs to be updated. An announcement will be made when this page is updated again. 2026-Jun-01


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, shoot for 2ms or less
  • When applicable, provide a usage example with example data
  • All code and comments must be in English
  • All code must be in pure Java unless specified otherwise
  • No merge conflict with latest SNAPSHOT
  • All unit tests must pass
  • Maximize use of existing internal functionality
    • Not sure if a capability already exists? Ask!
  • Adding new external libraries is discouraged and will need to be justified
  • Code should minimize the creation of new memory and use a single thread

Rules

Effective as of January 3, 2017

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
  • Code's copyright formust be reassigned
    • The code will be released publicly under an Apache 2.0 license
    • Copyright will be transferred over to Peter Abeles, see Donating to BoofCV for why
    • Your name/organization will be listed as an author after donating
  • 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
  • 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 and/or bountysource
  • If the bounty is cross posted to bountysource then a portion of the award will be collected from there.
  • 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.
Retrieved from "http://boofcv.org/index.php?title=Bounties&oldid=3287"