ShapeShift

Open Source Bounty Work - First Funding

Fund the Engineering workstream with 200K FOX, to be used for bounty rewards and other needs, as determined by the workstream.

Abstract

Centralized ShapeShift engineers are hard at work on the first new repo to go open source. Our intent is that this repo will be under active development from both centralized foxes and DAO community developers. We are targeting to make this repo open source in the next few weeks. Very shortly thereafter we hope to post bounties for specific pieces of work that we believe are well suited for coders new into ShapeShift. The workstream leader will work with centralized ShapeShift engineers to determine the specific bounties.

Motivation

We (centralized ShapeShift engineers) believe this would be a great way to get open source community involvement as early as possible. This is important to keep excitement around the project and build momentum. It is also a great way to get needed functionality added as quickly as possible.

Specification

Passing this proposal would trigger 200K FOX to be sent to the Engineering workstream. The workstream leader will have the authority to spend 100K on bounties to community devs. The workstream leader is being entrusted to the following:

• Work with centralized engineering to determine what functionality in the repo is appropriate for community dev work.
• Determine how much FOX should be allocated to each bounty
• Post bounties in a public forum. The DAO Discord could work. As could posting on gitcoin.
• Track progress of bounty projects. Ensure devs who picked up the work have access to centralized dev foxes so they have the support they need to get the job done.
• Evaluate completeness of work when person/team reports it is complete.
• Pay out bounties

The workstream leader will be accountable to the community for success of this proposal. They will supply a report every two weeks to the community showing status of each bounty project. The report will include for each bounty project:

• Bounty Name
• Bounty Summary
• Person or Group working bounty
• Amount of bounty attached
• Status of work

It is acceptable that current centralized foxes pick up bounty work, but they must do the bounty work after their salary-job hours.

Benefits

• Gets community dev involvement at the earliest possible opportunity
• Huge learning from experimenting with our bounty process.
• Features and functionality supplied to users of our products sooner.

Drawbacks

• Management overhead of the bounty program

Vote

Vote For: A vote for this proposal would immediately send 200K FOX to the engineering workstream. These funds would be used at the discretion of the engineering workstream leader to divvy out to bounty projects at their discretion. They are expected to work with the centralized engineering team in doing so.

Vote Against: A vote against this proposal would cause no action to be taken.