shortname: BEP-20
name: Bounties in BigchainDB
type: Meta
status: Raw
editor: Chalid Mannaa <chalid@bigchaindb.com>
This document describes a pragmatic bounty system that enables open source projects to reward coding contributions to software in the BigchainDB ecosystem.
This specification is based on the intents and concepts of the Gitcoin project.
This document is governed by 1/C4 and 2/COSS.
The primary goal of BOUNTY is to facilitate a reward process for open source software contributions into github repositories. Such repositories should represent elements of the ecosystem building for the web3.
BOUNTY is intended to above all be economical and rapid, so that it is useful to small teams with little time to spend on more formal processes.
Software repositories in Github contain issues . Issues represent problems in their specific context which should be resolved.
An issue is called bounty when it has
- a requirement specification,
- a definition of done,
- a funding,
- a resolution proposal,
- an approved revision,
- a merge into the master code branch and
- a successful payment transaction.
The purpose of bounties is to
- resolve issues,
- scale developments in the ecosystem,
- attract contributors for key components,
- support adoption and
- self-maintenance
The process requires following activities that should be performed
- Identify issue and provide requirements specification
- Estimate efforts for the work to be done
- Define the bounty, eg. funds/DoD
- Clarify revisions and issue labeling ("bounty")
- Create and submit bounty on the platform
- Publish to blog, slack, gitter, twitter and linkedin
- Monitor progress and comment where applicable
- Revise pull request and merge
- Reward / pay the bounty hunter
A typical interaction between bounty poster and bounty hunter is described in following sequence diagram.
Gitcoin as a platform supports the lifecycle of the bounty with Github integration and enables monitoring via email. Additional guidance can be found here.
To the extent possible under law, all contributors to this BEP
have waived all copyright and related or neighboring rights to this BEP.