Anyone is welcome and encouraged to add new features to app.shapeshift.com. If your project has developer resources available to build the integration, follow this guide to develop the integration yourself. Alternatively, there is a growing community of developers who are familiar with ShapeShift’s codebases and eager to integrate your feature if a compelling bounty is offered.
Whether you decide to develop the integration yourself or offer a bounty, ShapeShift DAO’s Product and Engineering workstreams will provide guidance and support. Feel free to reach out to the either workstream in Discord at any time for questions; make sure to select the corresponding role in the #role-selector channel to get access.
To post a bounty, create a forum post in the Engineering category using the following template:
Title: BOUNTY: [Bounty Amount] for [Feature Name] by [Expiration Date]
Tags: bounty, open
Provide a high level overview about the feature being integrated.
What feature is being bountied?
Why should this feature be integrated with ShapeShift?
Who is the team/project behind the feature?
What specifically needs to be delivered for this bounty to be considered complete?
Feature Spec and UI/UX (optional):
- A comprehensive spec with all feature requirements, acceptance criteria, and UI/UX mockups are approved by ShapeShift DAO’s Product Workstream Leader
How much are you offering for this bounty? Will the bounty be paid out in milestones, or upon full completion?
Does this bounty have a deadline? If so, when is it? For aggressive deadlines (ie. less than 6 months away), consider decaying the bounty amount in one or two stages rather than ending it abruptly.
At the bottom of your bounty, paste this section with instructions on how bounty hunters can apply.
How to apply
To apply for this bounty, please add a comment to this thread with details on the backgrounds of each individual who would work on the bounty, how soon you could start, and a target delivery date.
Note for bounties which required code to be shipped to production by a certain date:
If a bounties definition of done requires that code be shipped to production, we recommend these four workstreams each provide an interim milestone date (and specific deliverable) that bounty hunters must hit in order to ensure an on-time release.
This will allow workstreams to correctly plan to support a bounty effort and also provide an upfront conversation about the amount of time required. Bounty hunters can rest assured that if they hit the interim milestone, the workstream will do everything in its power to support the targeted release date and will be able to plan and fit the needed capacity into their schedules.
The purpose of these interim milestones is to avoid last minute requests to workstreams and facilitate better planning as bounties are formulated and target release dates are set.