We are running a bounty program to complete projected functionality as soon as possible. Currently bounties are not paid in cash, but in bitDubai shares. This is one of the ways we use to distribute ownership of the project with whoever adds value to it.
- Grabb a Team and apply for one of the projects listed where its status is Not Assigned (if you are already working at bitDubai you can only participate on the projects you are assigned to, if it happens that that project has a bounty then you are automatically participating on the bounty-program together with the team that is working on that.)
- Create an Issue in this REPO tagging the @bounty-program-team asking to assign the project you are interested in to your team.
- Someone on this team will evaluate your skills and may assign or not the project to your team. In any case a complete explanation of the reasons why they do or don't assign it will be given to you. Everything will happen in the disscussion on the issue created.
- The exact scope of the project is defined once the project is assigned to a team. It is agreed between the team members and the @bounty-program-team.
- If you miss the target month for any reason you can still be awarded half of the bounty if you reach production the following month.
- Your team has to maintain the code implemented during the first 3 months on production.
- You wil be awarded a 10% of the bounty received for each of these 3 months.
- The distribution of the bounty between the team members is free. It is up to the team to decide how to distribute the bounty between them or other people from other teams which helped.
- Team leaders can make agreements for shares of the possible bounty with other team leaders to help them with the project. In fact this is expected to happend with graphic designers, UX designers, copywriters and others, in order to secure there commitment to the project for certain dates.
- Taking the functionality into production means passing all controls, checks and approvals that might be in place by the time the code is implemented. This approval procedures might or might not be in place at present time.
- The conditions of bounties that are not yet Assigned might be changed at anytime by the @bounty-program-team. Once assigned, the conditions will stay fixed.
- If the @bounty-program-team sees a lack of commitment of a team with the project assigned or a too slow progress, it my cancel the assigment and return the project to the pool of Not Assigned bounties.
- Some projects might require a colaterall in shares of the team meambers assigned to the project in order to get the project. If they fail to win the bounty they will have to return the shares in collateral. In this cases a contract will be added to the contracts folder in this repo with the agreement.
Below you can see a table with all current bounties available and their status.
| Project | Target Month | Bounty Amount [USD] | To be paid in | Status | Assiged Team | Starded | Finished | Amount Awarded [USD] | |:---:|:---:|---:|:---:|:---:|:---:|:---:|:--:|---:|---:| |Crypto Currency Platform| Jan | 5,000 | bitDubai Shares | Assigned | Coin Diggers | Aug 2015 | | | |Chat Platform| Jan | 5,000 | bitDubai Shares | Assigned | Gabriel José Miguel | Dec 2015 | | | |Crypto Broker Platform| Jan | 15,000 | bitDubai Shares | Assigned | Nelson & Cía | Oct 2015 | | | |Digital Assets Platform| Jan | 10,000 | bitDubai Shares | Assigned | Thunder | Aug 2015 | | | |Wallet Production Distribution| Jan | 10,000 | bitDubai Shares | Assigned | Thunder | Aug 2015 | | | |Loss Protected Wallet| Jan | 5,000 | bitDubai Shares | Assigned | Coin Diggers | Ene 2015 | | | |Discount Wallet| Jan | 5,000 | bitDubai Shares | Assigned | Coin Diggers | Ene 2015 | | | |P2P Network v2| Jan | 15,000 | bitDubai Shares | Assigned | Disruptors | Dec 2015 | | | |Fermat ORG P2P| Jan | 15,000 | bitDubai Shares | Assigned | Miguel Luis Germán | Dec 2015 | | | |Fermat ORG Editable| Jan | 10,000 | bitDubai Shares | Assigned | Miguel Luis Germán | Dec 2015 | | | |Device Private Network| Feb | 30,000 | bitDubai Shares | Not Assigned | | | | | |Crypto Distribution Network| Feb | 25,000 | bitDubai Shares | Not Assigned | | | | | |Digital Assets Combined| Feb | 15,000 | bitDubai Shares | Not Assigned | | | | | |Marketing Platform| Feb | 20,000 | bitDubai Shares | Not Assigned | | | | | |Niche Wallets APPs| Feb | 15,000 | bitDubai Shares | Not Assigned | | | | | |Branded Wallets APPs| Mar | 25,000 | bitDubai Shares | Not Assigned | | | | | |Multi-Sig Vault| Mar | 30,000 | bitDubai Shares | Not Assigned | | | | | |Digital Assets Secondary Market| | 30,000 | bitDubai Shares | Not Assigned | | | | | |Fermat Blockchain| | 30,000 | bitDubai Shares | Not Assigned | | | | | |Fermat P2P v3 | | 20,000 | bitDubai Shares | Not Assigned | | | | | |Fermat Companies | | 40,000 | bitDubai Shares | Not Assigned | | | | | |Distributed Reputation System | | 20,000 | bitDubai Shares | Not Assigned | | | | | |Integrated Feedback | | 20,000 | bitDubai Shares | Not Assigned | | | | | |Customer Support | | 20,000 | bitDubai Shares | Not Assigned | | | | | |Fermat Multi OS | | 30,000 | bitDubai Shares | Not Assigned | | | | | |Fermat for iOS | | 30,000 | bitDubai Shares | Not Assigned | | | | |
Please Note: Target month and bounty offered may change while their status is Not Assigned
Target Month : Is the month where this functionality should reach production. It is considered to hit the target if it reach production any day of that month.
Bounty Amount : Is the amount to be awarded if the desired functionality reaches production on the Target Month.
To be paid in : Is the way we intend to pay for this bounty. It can be in bitDubai shares, Fermat tokens, bitcoins.
Status : Is the status of the bounty. It can be Assigned if some team is already working on it, or Not Assigned if nobody is working on it yet.
Amount Awarded : As per the bounty program rules, the amount awarded may vary from the Bounty Amount. Here we show how much it was finally awarded.
