mvc for the handbook expansion#8
Conversation
Update handbook
|
|
||
| ## We're pscyhed you're here | ||
|
|
||
| - We want more contributors rather than less. This document is a way too highlight our norms and processes for you to use |
|
|
||
| There is a difference between being a contributor vs everything else. And that's what we want, you to be a contributor. Sometimes it's easier to understand what being a contributor is if you know what it is not. Being a contributor vs a: | ||
|
|
||
| 1. Contractor: Contractors are mostly told what to do. We think this is odd, since most of the time you're the ones building, using, and experience the change we're making. We want you to split your time as a Govrn contributor submitting actual content (build) and submitting ideas and thoughts (collaboration). |
There was a problem hiding this comment.
fix numbering
experience --> experiencing
| There is a difference between being a contributor vs everything else. And that's what we want, you to be a contributor. Sometimes it's easier to understand what being a contributor is if you know what it is not. Being a contributor vs a: | ||
|
|
||
| 1. Contractor: Contractors are mostly told what to do. We think this is odd, since most of the time you're the ones building, using, and experience the change we're making. We want you to split your time as a Govrn contributor submitting actual content (build) and submitting ideas and thoughts (collaboration). | ||
| 1. Investor: Investors give only time or money to a project once and then go away forevery. Contributors give both time and money but in a way that encourages ongoing contributions. |
There was a problem hiding this comment.
forevery --> forever
Might be worth adding that not all investors aren't contributors/go away forever. It's just that being an investor doesn't automatically mean that you're a contributor.
| 1. Investor: Investors give only time or money to a project once and then go away forevery. Contributors give both time and money but in a way that encourages ongoing contributions. | ||
| 1. Users: Users use the product but aren't allowed to submit or build improvements. Othertimes, users will "lob grenades" by throwing out an idea but never following up on it. Contributors provide ideas, follow up with "why", and follow on with iterations. | ||
|
|
||
| Likewise, we reward contributors with additional influence and responsibilty over our decisions. |
There was a problem hiding this comment.
Love this point and think it deserves expansion. I'm not super in love with the term reward.
Contributors become community members who are invested in the vision and growth of Govrn. Contributions can take many, many different forms, but the common thread is that contributions are a way to decentralize the pathways to leadership and decision-making within the Govrn community (and are a form of governance in and of themselves).
|
|
||
| ## Process on becoming a Contributor | ||
|
|
||
| 1. Make a README |
There was a problem hiding this comment.
Where are they making the readme?
| ## Process on becoming a Contributor | ||
|
|
||
| 1. Make a README | ||
| 2. Find an Issue or Repo to work on |
There was a problem hiding this comment.
Wouldn't this be the first step?
|
|
||
| We like keep it simple. | ||
|
|
||
| ## Process for Contributing |
There was a problem hiding this comment.
I think it's confusing to have two numbered step sequences. This seems to overlap with the above. Can they be consolidated?
|
|
||
| ## Process for Contributing | ||
|
|
||
| 1. Make a proposal |
There was a problem hiding this comment.
Where should this proposal be made? Github only?
|
|
||
| 1. Make a proposal | ||
| 2. Post about it in the `# 🙌-come-contribute` channel in [discord](https://discord.com/channels/837049837886767125/910702904388767744) asking for async feedback. | ||
| 3. If more than 3 people comment or express interest, ask a Govrn Mod to create a channel for you |
There was a problem hiding this comment.
I love steps 2 and 3 because it builds in the communication piece and community feedback.
Here's my thought process on contribution steps inspired by what you wrote:
- Find an issue to work on or suggest a new one. Link to open issues here []
- Create a proposal (does this have to be on github??) for how you want to approach the issue and post it in the come-contribute channel.
- If more than 3 people comment or express interest, ask a Govrn Mod to create a discord channel for ongoing collaboration.
- Record your contributions to the Govrn bot!
There was a problem hiding this comment.
Should we add guidelines on what makes for a good proposal? i.e. structure, if it generates a community discussion + debate
|
|
||
| ## We believe in openness | ||
|
|
||
| Whether it's Govrn or Politics, we believe in open systems that are transparently designed. We don't need to burn the existing world down, just the walls that currently divide us. |
There was a problem hiding this comment.
I think the second sentence doesn't relate to openness + brings up two really big themes (reform v abolition) and division/polarization without fully expanding on either. Can we take the second sentence out and fully expand on the openness piece?
2 participants
Starting to expand the foundation's repo to include more processes on how to contribute.
making a pr for the minimum viable change.