Skip to content
This repository has been archived by the owner on Jun 17, 2020. It is now read-only.

Task Approval

Jump to bottom
Dan Connolly edited this page May 2, 2018 · 5 revisions

This is a proposal, a work in progress; see #616.

In the RChain Board meeting of Apr 6, 2018, there was a Resolution to Adopt Bounties Terms of Service, including an Approval Process for Task Identification and Project Bid. We (propose to) carry out the process as follows:

  1. The RChain Coop or a Member identifies a task to be completed (“Task” or “Tasks”);
  2. If a Member has a suggested task, he/she may submit a Task Identification Form to the Task Approval Committee (the “Committee”);

As detailed in CONTRIBUTING, tasks are represented as github issues. The ISSUE_TEMPLATE incorporates the Task Identification Form.

The Committee consists of members certified by a community trust metric, with @dckc, @Jake-Gillberg, and @kitblake as the seed. As a result, most Bounty Task Guides serve on the committee. The trust metric selects for committee members who provide fair and wise input on budgets and rewards. The results of a vote is a weighted average, with more weight given to input from members with higher trust ratings.

  1. Within five (5) days of receiving the Task Identification Form, the Committee will provide written notice to the submitter of the Task Identification Form (the “Task Submitter”) of the Committee’s approval or rejection of the Task Submitter’s Task Identification Form
  2. If the Task Identification Form is approved, it will be posted to the Membership and open for Project Bid Submissions. If the Task Identification Form is rejected, the Task Submitter may choose to revise the terms of the Task and resubmit at a later time.

The issues with a non-zero budget as a result of at least three committee votes are approved. Bounty Task Guides should provide feedback on new issues in their area within a few days, both in the form of github comments and budget votes.

All proceedings of the bounty program are available to the Membership at all times.

  1. Once a Task is open for Project Bid Submissions, Members may submit a Project Bid Submission form to the Committee for consideration.
  2. Within five (5) days of receiving the Project Bid Submission Form, the Committee will provide written notice to the submitter of the Project Bid Submission Form (the “Project Submitter”) of the Committee’s approval or rejection of the Project Bid Submission Form.
  3. If the Project Bid proposed in the Project Bid Submission Form is approved by the Committee, the Project Submitter may begin work on the Project pursuant to the timeline set forth in the approved Project Bid Submission Form. If the Committee rejects the Project Bid Submission Form, the Task Submitter has ten (10) days from the day the Committee sends its written rejection to revise and resubmit its Project Bid Submission Form to the Committee. There is only one revision allowed per Project Bid Submission.

The ISSUE_TEMPLATE incorporates the Project Bid Submission Form (or it should on acceptance of this proposal). In particular, issues should eventually include a suggested budget.

The issues with non-zero rewards as a result of at least three committee votes represent approved bids.

The Bounty Task Guides and trust-certified members should provide timely feedback on suggested budgets and rewards.

All Committee decisions are final and there is no appeal process.

As noted in CONTRIBUTING, voting for each monthly pay period closes a few days after the end of the month.

Clone this wiki locally