/software-bounty-program

Fermat road map & bounty program.

alt text

Software Bounty Program

We are running a bounty program to complete the projected functionality as soon as possible. Currently bounties are not paid in cash, but in Fermat tokens. This is one of the ways we use to distribute ownership of the project with whoever adds value to it.

Sign-up - License Agreement - (READ FIRST)

Anyone who adds value to the Project in any form needs to sign up a Contribution License Agreement as the first step to become part of the project. To do that, please follow the steps described here

Now, after signing up, you can follow the Bounty program procedure below.

Software Release Life Cycle

A software release life cycle is the sum of the stages of development and maturity for a piece of computer software: ranging from its initial development to its eventual release, and including updated versions of the released version to help improve software or fix bugs still present in the software.

We adhere to the following definitions:

Procedure

  1. Grab a Team and apply for one of the projects listed whose status reads as Not Assigned (if you are already a member of the bitDubai network 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.)
  2. Create an Issue in this REPO tagging the @bounty-program-team asking to assign to your team the project you are interested in.
  3. Someone on this team will evaluate your skills and may or may not assign 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.
  4. 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.

Rules

  1. If you miss the target month for any reason you can still be awarded half of the bounty if you reach the targe phase the following month.
  2. A team has to maintain the code implemented during the first 3 months in production.
  3. The team will be awarded a 10% extra of the bounty received for each of these 3 months.
  4. 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 that helped.
  5. Team leaders can make agreements for tokens 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 their commitment to the project for certain dates.
  6. Reaching production phase means passing all controls, checks and approvals that might be in place by the time the code is implemented. Those approval procedures might or might not be in place at present time.
  7. 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.
  8. If the @bounty-program-team sees a lack of commitment of a team with the project assigned or a the progress is too slow, it might cancel the assigment and return the project to the pool of Not Assigned bounties.
  9. If you achieve it within the target you will get 100% of the bounty (of course), if you make it during the next 30 days after the deadline you'll get 50%, from day 31 to 60 you'll get 0, from day 61 to 90 you will have to pay 50% in tokens and from day 91 to 120 you will pay 100% of the tokens.
  10. A short agreement will be added to the agreements folder in this repo with the conditions agreed by the team and the @bounty-program-team.
  11. The same agreement document will be updated once the bounty is won with a distribution table where all beneficiaries will be listed together with the percentage that they will receive.
    1. At a DEMO-DAY the team showcases the functionality that has developed and a jury decides if the bounty should be awarded or not.
  13. The payment of the bounty will be done when the project is released to general public (production). The amount of Tokens to receive will be calculated at the Tokens price at the date the project is relesed to the public.
  14. The bounty awarded expires after 30 days of the DEMO day if the project has not been released.
  15. A Team cannot participate on other bounty of this program until the current one they are working at is released (production).
  16. Team members cannot leave the team for other teams before the project reaches the phase specified on this bounty program. The only way to leave is leaving the Fermat project.
  17. GUI and A project types have one free review. The following reviews without approval will cost the team 25% of the bounty each.

2016 Bounties

Below you can see a table with all current bounties available and their status.

| Type | Project | Target Month / Phase | Bounty Amount [USD] | To be paid in | Status | Assigned Team | Started / Finished | Amount Awarded / Payed [USD] | |:---:|:---:|:---:|---:|:---:|:---:|:---:|:---:|:--:|---:|---:| |All|Crypto Currency Platform|Jan / Alpha | 5,000 | Fermat Tokens | Assigned Beta Beta Testing| Coin Diggers | Sep 2015 / Jan 2016 | 5,000 | |All|Chat Platform| Jan / Alpha | 5,000 | Fermat Tokens | Assigned Implementing Delayed|Gabriel, José & Miguel | Dec 2015 | | |All|Crypto Broker Platform|Jan / Alpha | 15,000 | Fermat Tokens | Assigned Implementing Delayed| Nelson & Cía | Oct 2015 | | |All|Digital Assets Platform| Jan / Alpha | 10,000 | Fermat Tokens | Assigned Alpha Delayed| Thunder | Aug 2015 / Jan 2016 | 10,000 | |All|Fermat ORG P2P| Jan / Alpha | 15,000 | Fermat Tokens | Assigned Implementing Delayed| Miguel Luis | Dec 2015 | | |All|[Fermat ORG Editable](bounties/Fermat.org V3.md)| Jan / Release | 10,000 | Fermat Tokens | Assigned Implementing Delayed| Ricardo Emmanuel | Dec 2015 | | |All|Recover Fermat Repo History|Jan | 1,000 | Fermat Tokens | Assigned Finished Approved| Manuel | Jan 2016 / Jan 2016 | 1,000 | |All|Digital Assets Platform v2|March / Alpha | 10,000 | Fermat Tokens | Assigned Alpha Alpha Testing| Thunder |Feb 2016 / Mar 2016|10,000| |All|[Reduce 50% Compilation Time] (https://github.com/FERMAT-ORG/software-bounty-program/blob/master/bounties/Reduce_compilation_time.md)|February / Release| 2,000 | Fermat Tokens | Assigned Finished Approved|Manuel, Victor & Nerio|February 2016|2,000| |All|Android Components Tool Box| March 15th | 10,000 | Fermat Tokens | Assigned Alpha Alpha Testing| Matias | Feb 2016 / Mar 2016 | 10,000 | |All|Cloud Server Monitor| March 15th | 2,500 | Fermat Tokens | Assigned Alpha Alpha Testing | Roberto | Feb 2016 / Mar 2016 | 2,500 | |All|Fermat P2P Network v1| Mar 2016 | 20,000 | Fermat Tokens | Assigned Implementing Under Construction| Roberto & Leon | Apr 2016 | | |All|Loss Protected Wallet| Mar 2016 | 10,000 | Fermat Tokens | Assigned Implementing Under Construction | Natalia | Mar 2016 | | |All|Fermat Token Platform| | 25,000 | Fermat Tokens | Not Assigned | | | | |All|Digital Asset Store| | 25,000 | Fermat Tokens | Not Assigned | | | | |All|Fermat Blockchain Identities| | 25,000 | Fermat Tokens | Not Assigned | | | | |All|Fermat P2P Network v2..n| | 130,000 | Fermat Tokens | Not Assigned | | | | |All|Fermat Blockchain| | 100,000 | Fermat Tokens | Not Assigned | | | | |All|Fermat Tokens Wallet| | 50,000 | Fermat Tokens | Not Assigned | | | | |All|Fermats Tokens Exchange | | 100,000 | Fermat Tokens | Not Assigned | | | | |All|Discount Wallet| | 25,000 | Fermat Tokens | Not Assigned | | | | |All|Device Private Network| | 100,000 | Fermat Tokens | Not Assigned | | | | |All|Crypto Distribution Network| | 75,000 | Fermat Tokens | Not Assigned | | | | |All|Digital Assets Combined| | 25,000 | Fermat Tokens | Not Assigned | | | | |All|Marketing Platform| | 25,000 | Fermat Tokens | Not Assigned | | | | |All|Niche Wallets APPs| | 25,000 | Fermat Tokens | Not Assigned | | | | |All|Wallet Production Distribution| | 30,000 | Fermat Tokens | Not Assigned | | | | |All|Branded Wallets APPs|| 50,000 | Fermat Tokens | Not Assigned | | | | |All|Multi-Sig Vault| | 50,000 | Fermat Tokens | Not Assigned | | | | |All|Digital Assets Secondary Market| | 75,000 | Fermat Tokens | Not Assigned | | | | |All|Fermat Companies | | 50,000 | Fermat Tokens | Not Assigned | | | | |All|Distributed Reputation System | | 50,000 | Fermat Tokens | Not Assigned | | | | |All|Integrated Feedback | | 50,000 | Fermat Tokens | Not Assigned | | | | |All|Customer Support | | 75,000 | Fermat Tokens | Not Assigned | | | | |All|Fermat APPs Licensing | | 50,000 | Fermat Tokens | Not Assigned | | | | |All|Fermat Multi OS | | 100,000 | Fermat Tokens | Not Assigned | | | | |All|Fermat for iOS | | 100,000 | Fermat Tokens | Not Assigned | | | |

Please Note: Target month and bounty offer may change while their status is Not Assigned

Reference

Type : Means the type of project. The possible projects are: GUI Design (GUI), Analisys (A), Implementation (CODE), All of the previous one (All).

Target Month : Is the month where this functionality should reach production. It is considered to hit the target if it reaches 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 Fermat tokens or 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 the bounty program rules, the amount awarded may vary from the Bounty Amount. Here we show how much it was finally awarded.