[S1] Scribe Bounty Program
Program Name: Guild Scribe Bounty Program - Season 1
Program Champion: jameswmontgomery.eth, hashed Mae
OP Date: August 3, 2021
Status: Closed: Passed [Draft->Voting->Closed]
Voting Link: LINK
TL;DR
- 3000 BANK/week in bounties to take & edit notes for Dev Guilds.
- 18,000 BANK remunerations.
- Max budget: 39,000 BANK (7 weeks left in season)
Program Justification:
Taking notes during meetings is a vital responsibility to ensure all asynchronous Dev Guild members can continue to stay informed on meetings & discussion points.
Furthermore, the notes from project updates provide a baseline to draw from for editorialized content like a Guild Newsletter or Community Call updates.
Creating the Scribe role codifies the responsibilities of note taking and ensures asynchronous communication stays consistent.
Program Terms
The role would exist for a trial period lasting for Season 1 and require renewal or otherwise be more firmly instantiated.
Responsibilities/Domain
The responsibilities of this role are to:
- Take notes during both Dev Guild weekly meetings
- Edit notes after each meeting to improve readability
Payment
- Recurring Bounty
- Bounties per week: 2 (1 for each meeting)
- Bounties per season: 24 (max)
- Currently mid-season so take remaining weeks and double it.
- Bounty rate: 1500 BANK (90m per meeting, 1000 BANK/hr)
- Payout per week: 3000 Bank
- Payout per season: 36,000 BANK
- One-time Remuneration
- 6 weeks = 18,000 BANK
- 10,500 BANK paid to Icedcool (7 meetings)
- 1,500 BANK paid to MrPackman (1 meeting)
- 1,500 BANK paid to Behold (1 meeting)
- 1,500 BANK to note-taker for 8/4 meeting
- 1,500 BANK to note-taker for 8/9 meeting
- 1,500 BANK to note-taker for 8/11 meeting
- Total maximum payable: 39,000 BANK
- Remuneration (18,000) + 7 weeks of bounties (21,000)
Rotation
- This is not an elected role.
- At the beginning of each Guild meeting, any interested member can volunteer to claim the bounty and take notes for the meeting.
- Any conflicts in choosing the scribe can be handled through soft consensus at the beginning of the meeting.
Questions
Are all responsibilities captured?
How can we codify role sharing and rotation?
How does this role interact with Project meetings?