-
Notifications
You must be signed in to change notification settings - Fork 62
Bounty Task Guides
Bounty task guides for a number of areas are here to align contributions with goals of the RChain cooperative:
- Development: @dckc
- Education: @TrenchFloat
- Marketing: @pmoorman
- Events: @Ojimadu
- Operations: @TrenchFloat @lapin7
- member-site: @ian-bloom @kitblake @dckc
- greeter: @makys @ian-bloom
- Translation: @ICA3DaR5, @Jake-Gillberg
- Governance: @jimscarver with ...?
Guides should provide feedback on issues in their area within a few days and initiate the process of Task Approval.
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.
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.)
Bounty guides originated in #401 and have taken on further significance in discussion of Task Approval in #616.