-
Notifications
You must be signed in to change notification settings - Fork 62
Bounty Task Guides
Note: a reboot of the bounty system is in progress in Sep 2018.
To get certified to vote / guide an area:
- make the relevant sociocratic connections
- get mandate / sponsorship
- establish budget criteria, and
- make projections
| Label | Guide(s) | Connections / Sponsors | Norms | Q3 Budget |
|---|---|---|---|---|
| core-dev | @dckc, @JoshyOrndorff | @Medha for core-dev Sep 28 | $150/story point | $15 to $20 K per month |
| developer-education | @JoshyOrndorff | @JoshyOrndorff for dev ed / Marketing Sep 29 | example dApps, ed. materials | $4K/month |
Bounty task guides knowledgeable in a number of areas (represented by issue labels) are here to align contributions with goals of the RChain cooperative; for example:
- Development: @dckc splitting into core-dev, tools-dev? solutions-dev?
- ... see issue labels
Guides should provide feedback on issues in their area within a few days and initiate the process of Task Approval: either support a task by adding budget and reward votes or provide negative feedback as noted in Smart Objectives and Pruning below. A Task Approval Overdue audit shows where effort is lacking.
Guides should also participate actively in Trust Ratings.
Regular meetings provide richer and perhaps more reliable ways to get in touch with guides and peers:
- weekly RChain Active Member Meeting
- @dckc's weekly office hours, aka Story Telling and Test Cases
- Governance WG
- Principles and Values WG
- ... other issues tagged Meeting
We also have #bounties and #member-calendar channels in RChain's discord server, and there are various other RChain communications channels.
Issues not connected to a guide via one of these labels are at risk, so this list should get reviewed at least a couple times per week:
Thanks to @TrenchFloat for offering to help in this area.
Guides also help with SMART objectives: Specific, Measurable, Achievable, Realistic, Timely. We use the needs-SMART-objective label to flag issues at risk in this respect.
Guides should report on what value was produced in their area in exchange for rewards. (See, for example, #678.)
See also Guiding Norms
We use the invalid label as part of closing issues that don't seem to fit in and wontfix for tasks that might be a good idea but there isn't a plausible plan or at least a clear next step. (As usual, github issues can be reopened by collaborators.)
To quickly find relevant issues, use this helpful tool.
Bounty guides originated in #401 and have taken on further significance in discussion of Task Approval in #616. Note also #672 on recruiting more guides for each area label.