We’ve been having a number of conversations about how to document how to grow into leadership roles within the OpenData Community.
As you can see, we have crafted two paths:
- Technical Leadership - become a Regen Ranger
- DAO Leadershp - become an ODC Jedi
In each case the ingredients include:
- useful activities
- an OATH
- a vote
And in return you get - a Soul Bound Token
- we see these marks as similar to professional qualifications, hopefully with much less arbitrary gatekeeping
When this is adopted, we add it and other accepted proposals as an addendum to the governance doc
I suggest these changes the people pipeline.
Regen Ranger use this algorithm for calculating levels.
every 1 months, we run a report on all ODC contributors:
(comms Twitter 5 msg per month discord 20 msg per month discourse 10 msg per month) +
(github reviews 10 per month PRs 5 per month commits 5 per month) +
(hackathon submissions 1 entries per quarter mentoring 1 entries per quarter).
Ranger level 1 hit target values in comms and GitHub sections,
Ranger level 2 values in all 3 sections.
I think these activities lead to Regenerative projects which will keep the ODC OSS going.
Regen Ranger badge is held for 6 months.
The ODC Jedi act as the administrative staff until we have a governance committee or board of directors. Every 6 months, the ODC Jedi can vote on new members.
One possibility for naming of the 4 levels is that we could stick to the Star Wars theme:
Thanks for the clear description
I am not in favor of level 1 level 2, I would prefer naming.
I agree with the benefits of each level.
I think Jedi levels should require a vote.
As you suggest each month we can run a council meeting to review the potential person that reaches the requirements of a new level according to the algorithm.
Regen roles are granted after a quick review and Jedis roles are voted upon. The process for voting could be 5 days in a forum post to inform and 5 days to vote (similar to gitcoin)
As the Jedi role could be reached quickly I suggest that we add a minimum number of months to maintain the requirements 2-2.5-3 months. this would reduce the amount of time to wait to grant the Jedi role to someone compared to the every 6 months vote.
Sarob you suggested an algorithm with minimum requirements in each channel. I would suggest a point mechanism.
Where we can grant a number of points for each type of action, using Govern or similar tools will help.
- Twitter retweet 10pt
- Twitter comment 15 pt
- discord message 1pt
- discord emoji 0.5p
- discord emoji on a written post 0.5/ emoji
- response to a message 1pt
- Mentioned in a discord message 1pt
- GitHub review/comment 10 pt
- GitHub PR 10pt
- Hackathon submission winner of the bounty gets 100 points then proportional to the received value
I came up with these numbers and I’m sure they can be improved and thought more deeply about. The threshold for the number of points could be determined by backtesting.
@Poupou Love all of this. I will take a pass at writing this up shortly and let me know if I captured your recommendations.