From 652409a096c49c83c652d75759245b9783bd39f6 Mon Sep 17 00:00:00 2001 From: James Vorderbruggen Date: Tue, 5 Jan 2021 19:46:25 -0500 Subject: [PATCH 01/12] First stab at membership rights and obligations --- README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/README.md b/README.md index 9202e6a..59e5cbf 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,17 @@ # Mass Mesh Governance This is where we can make membership changes and approve various policies/projects. + +## Core Team Privileges +- Can propose new policies +- Can initiate meetings on behalf of Mass Mesh +- May be promoted to admin on the wiki + +## Core Team Obligations +- Should approve/reject policy proposals in a timely fashion +- Participate in governance meetings when applicable/possible +- May be asked to help manage access to the wiki +- May be asked to help with maintenance of the network + +## Joining the Core Team +- Membership in the core team is by invite, and invites are vetted by consensus From 725b338a2bad1408f45686d600ba18fe4137c256 Mon Sep 17 00:00:00 2001 From: James Vorderbruggen Date: Tue, 5 Jan 2021 21:06:02 -0500 Subject: [PATCH 02/12] Expand privileges section --- README.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 59e5cbf..dfa9fd9 100644 --- a/README.md +++ b/README.md @@ -3,9 +3,16 @@ This is where we can make membership changes and approve various policies/projects. ## Core Team Privileges -- Can propose new policies -- Can initiate meetings on behalf of Mass Mesh -- May be promoted to admin on the wiki +Everyone on the core team has certain privileges that other participants in Mass Mesh and the neighborhood networks do not. +- Initiate meetings on behalf of Mass Mesh +- Make pull requests in this repository. All pull requests will be subject to review by the entire core team. This implies the ability to: + - Invite new core team members + - Draft new Mass Mesh policies + - Draft changes to the Network Commons License +- Core team members are also eligible to administer Mass Mesh's online assets, including: + - The wiki + - Massmesh.org email addresses and mailing lists + - Social media channels ## Core Team Obligations - Should approve/reject policy proposals in a timely fashion From aeb4c3ef45dbd12d3eb1505967920f23a14eabf0 Mon Sep 17 00:00:00 2001 From: James Vorderbruggen Date: Tue, 5 Jan 2021 21:11:35 -0500 Subject: [PATCH 03/12] Add para explaining repository's goals --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index dfa9fd9..e1d3fab 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # Mass Mesh Governance -This is where we can make membership changes and approve various policies/projects. +Mass Mesh is a grassroots project focused on building community wireless networks in Massachusetts. To facilitate the growth of our project, set expectations about the way we operate, and keep us accountable to ourselves, we maintain our governance policies publicly in this Git repository. Here, you can find the rights and responsibilities of our [core team](members.md), as well as information about how to get involved. ## Core Team Privileges Everyone on the core team has certain privileges that other participants in Mass Mesh and the neighborhood networks do not. From 076cd9970ce64939f95e02a6159ba3ce9c701118 Mon Sep 17 00:00:00 2001 From: James Vorderbruggen Date: Thu, 7 Jan 2021 19:09:40 -0500 Subject: [PATCH 04/12] Expand responsibilities. --- README.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index e1d3fab..0836375 100644 --- a/README.md +++ b/README.md @@ -15,10 +15,12 @@ Everyone on the core team has certain privileges that other participants in Mass - Social media channels ## Core Team Obligations -- Should approve/reject policy proposals in a timely fashion -- Participate in governance meetings when applicable/possible -- May be asked to help manage access to the wiki -- May be asked to help with maintenance of the network +All core team members are expected to participate actively in the maintenance of Mass Mesh -- the organization and the network. Although not everyone will contribute in the same way, or with the same frequency, please keep the following in mind before accepting a core team membership. +- Participate in governance meetings on a regular (at least quarterly) basis. +- Participate in other meetups on a regular (at least monthly) basis. +- Approve/reject pull requests in this repository in a timely fashion +- May be asked to help manage access to the wiki and other online assets +- May be asked to help with maintenance of the community network(s) ## Joining the Core Team - Membership in the core team is by invite, and invites are vetted by consensus From 022e711627414302132c1400e50e8f75c708a257 Mon Sep 17 00:00:00 2001 From: James Vorderbruggen Date: Thu, 7 Jan 2021 21:27:04 -0500 Subject: [PATCH 05/12] Credit to Anusha for the front-matter --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 0836375..1888578 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,8 @@ # Mass Mesh Governance -Mass Mesh is a grassroots project focused on building community wireless networks in Massachusetts. To facilitate the growth of our project, set expectations about the way we operate, and keep us accountable to ourselves, we maintain our governance policies publicly in this Git repository. Here, you can find the rights and responsibilities of our [core team](members.md), as well as information about how to get involved. +Mass Mesh is a volunteer-led organization focused on building community mesh networks in Boston and the surrounding area. Using off-the-shelf hardware and open-source software, Mass Mesh builds home-grown Internet infrastructure. Its aim is to give communities the tools they need to communicate securely online on their own terms. + +To facilitate the growth of our project, set expectations about the way we operate, and keep us accountable to ourselves, we maintain our governance policies publicly in this Git repository. Here, you can find the rights and responsibilities of our [core team](members.md), as well as information about how to get involved. ## Core Team Privileges Everyone on the core team has certain privileges that other participants in Mass Mesh and the neighborhood networks do not. From f8c5bf6fd08a6aec63bb60fc593815221d8f40ff Mon Sep 17 00:00:00 2001 From: James Vorderbruggen Date: Thu, 7 Jan 2021 21:31:22 -0500 Subject: [PATCH 06/12] Break admin things into their own list --- README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 1888578..4e9427e 100644 --- a/README.md +++ b/README.md @@ -5,16 +5,17 @@ Mass Mesh is a volunteer-led organization focused on building community mesh net To facilitate the growth of our project, set expectations about the way we operate, and keep us accountable to ourselves, we maintain our governance policies publicly in this Git repository. Here, you can find the rights and responsibilities of our [core team](members.md), as well as information about how to get involved. ## Core Team Privileges -Everyone on the core team has certain privileges that other participants in Mass Mesh and the neighborhood networks do not. +Everyone on the core team has certain privileges that other participants in Mass Mesh and the neighborhood networks do not. Core team members may: - Initiate meetings on behalf of Mass Mesh - Make pull requests in this repository. All pull requests will be subject to review by the entire core team. This implies the ability to: - Invite new core team members - Draft new Mass Mesh policies - Draft changes to the Network Commons License -- Core team members are also eligible to administer Mass Mesh's online assets, including: - - The wiki - - Massmesh.org email addresses and mailing lists - - Social media channels + +Core team members are also eligible to administer Mass Mesh's online assets, including: +- The wiki +- Massmesh.org email addresses and mailing lists +- Social media channels ## Core Team Obligations All core team members are expected to participate actively in the maintenance of Mass Mesh -- the organization and the network. Although not everyone will contribute in the same way, or with the same frequency, please keep the following in mind before accepting a core team membership. From 8dfb1b083faeab5f6d598cdfb8efc5b8a478e608 Mon Sep 17 00:00:00 2001 From: James Vorderbruggen Date: Thu, 7 Jan 2021 21:38:25 -0500 Subject: [PATCH 07/12] Add info about leaving --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index 4e9427e..5ad4a06 100644 --- a/README.md +++ b/README.md @@ -27,3 +27,10 @@ All core team members are expected to participate actively in the maintenance of ## Joining the Core Team - Membership in the core team is by invite, and invites are vetted by consensus + +## Leaving the Core Team +Core team members may leave at any time -- participation is completely voluntary. Leaving the core team doesn't have to mean leaving Mass Mesh, either. In order to sustain the health of the group and avoid disruptions, though, we do ask that anyone leaving the core team do the following: +- Give some notice so that others can try to make adjustments to our processes, etc. +- Notify any external parties to whom you are the point of contact of where to get in touch with the group (if applicable) +- Hand off any assets that you are managing +- Return any shared equipment (if applicable) From 809017d9ef091f62b56fd05a27362487ca2eebe9 Mon Sep 17 00:00:00 2001 From: James Vorderbruggen Date: Thu, 7 Jan 2021 21:39:41 -0500 Subject: [PATCH 08/12] team --- members.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/members.md b/members.md index 50dd211..d95a073 100644 --- a/members.md +++ b/members.md @@ -1,6 +1,6 @@ -# Core Members +# Core Team Members -Core members may make pull requests to this repository. All pull requests must be approved unanimously by the core members in this list before they are merged into the `main` branch. When a pull request is merged into the `main` branch, that becomes the official policy of Mass Mesh. +Core team members may make pull requests to this repository. All pull requests must be approved unanimously by the core team members in this list before they are merged into the `main` branch. When a pull request is merged into the `main` branch, that becomes the official policy of Mass Mesh. --- From d6e63deff3afecdce0b0827d271147e4f4ac1c39 Mon Sep 17 00:00:00 2001 From: James Vorderbruggen Date: Thu, 7 Jan 2021 21:45:14 -0500 Subject: [PATCH 09/12] First stab at disputes --- README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 5ad4a06..2e12bee 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ Mass Mesh is a volunteer-led organization focused on building community mesh networks in Boston and the surrounding area. Using off-the-shelf hardware and open-source software, Mass Mesh builds home-grown Internet infrastructure. Its aim is to give communities the tools they need to communicate securely online on their own terms. -To facilitate the growth of our project, set expectations about the way we operate, and keep us accountable to ourselves, we maintain our governance policies publicly in this Git repository. Here, you can find the rights and responsibilities of our [core team](members.md), as well as information about how to get involved. +To facilitate the growth of our project, set expectations about the way we operate, and keep us accountable to ourselves, we maintain our governance policies publicly in this Github repository. Here, you can find the rights and responsibilities of our [core team](members.md), as well as information about how to get involved. ## Core Team Privileges Everyone on the core team has certain privileges that other participants in Mass Mesh and the neighborhood networks do not. Core team members may: @@ -34,3 +34,9 @@ Core team members may leave at any time -- participation is completely voluntary - Notify any external parties to whom you are the point of contact of where to get in touch with the group (if applicable) - Hand off any assets that you are managing - Return any shared equipment (if applicable) + +## Disputes +If you believe that anyone on the core team is not living up to their responsibilities, has abused their privileges, or is in violation of our community norms at any time, you may either contact another core team [member](members.md) directly, or submit an issue on this Github repository. Depending on the severity of any wrong-doing, the following sanctions may be employed: +- Meeting to address the issue, and warning against further violations (1st violation/non-serious violations) +- Suspension from the core team for up to 1 month (2nd violation/serious first-time violations) +- Removal from the core team (3rd violation/very serious violations including theft, abuse, or misuse of shared funds) From 1ae8712d53affc52edb7972b184d377bb5251b4b Mon Sep 17 00:00:00 2001 From: James Vorderbruggen Date: Tue, 12 Jan 2021 18:02:28 -0500 Subject: [PATCH 10/12] Add expense approval as privilege --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 2e12bee..d98230a 100644 --- a/README.md +++ b/README.md @@ -7,6 +7,7 @@ To facilitate the growth of our project, set expectations about the way we opera ## Core Team Privileges Everyone on the core team has certain privileges that other participants in Mass Mesh and the neighborhood networks do not. Core team members may: - Initiate meetings on behalf of Mass Mesh +- Approve expenses on our [Open Collective](https://opencollective.com/mass-mesh) - Make pull requests in this repository. All pull requests will be subject to review by the entire core team. This implies the ability to: - Invite new core team members - Draft new Mass Mesh policies From 7b8cf97389896f5d6a0720f93fc1a339354db41c Mon Sep 17 00:00:00 2001 From: James Vorderbruggen Date: Tue, 12 Jan 2021 18:08:09 -0500 Subject: [PATCH 11/12] Add more info about joining core team --- README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index d98230a..c4c2287 100644 --- a/README.md +++ b/README.md @@ -27,7 +27,13 @@ All core team members are expected to participate actively in the maintenance of - May be asked to help with maintenance of the community network(s) ## Joining the Core Team -- Membership in the core team is by invite, and invites are vetted by consensus +Membership in the core team is by invite, and invites are vetted by consensus. If you are interested in joining the core team, please talk to one of the [existing members](members.md) in our [Matrix chat](https://riot.im/app/#/group/+massmesh:matrix.org). We'll be most likely to invite you in if you: + +- Have an active interest in growing our network in your neighborhood +- Have contributed regularly to the project in the past +- Have an active interest in expanding our capacity in some very involved way (i.e. growing our legal capacity, overhauling our online presence, maintaining social media channels on our behalf.) + +Generally, if the things you're doing or hope to do involve putting substantial amounts of your time or reputation into the project, you should ask about becoming a core team member. We're trying to build an organization that is volunteer-led, and an inclusive, healthy core team is an important part of that. ## Leaving the Core Team Core team members may leave at any time -- participation is completely voluntary. Leaving the core team doesn't have to mean leaving Mass Mesh, either. In order to sustain the health of the group and avoid disruptions, though, we do ask that anyone leaving the core team do the following: From 59839be0e3de3ac03eacc47722d512aa0b4e9ddb Mon Sep 17 00:00:00 2001 From: James Vorderbruggen Date: Tue, 12 Jan 2021 18:09:04 -0500 Subject: [PATCH 12/12] clarification --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c4c2287..44b223a 100644 --- a/README.md +++ b/README.md @@ -27,11 +27,11 @@ All core team members are expected to participate actively in the maintenance of - May be asked to help with maintenance of the community network(s) ## Joining the Core Team -Membership in the core team is by invite, and invites are vetted by consensus. If you are interested in joining the core team, please talk to one of the [existing members](members.md) in our [Matrix chat](https://riot.im/app/#/group/+massmesh:matrix.org). We'll be most likely to invite you in if you: +Membership in the core team is by invite, and invites are vetted by consensus. If you are interested in joining the core team, please talk to one of the [existing members](members.md) in our [Matrix chat](https://riot.im/app/#/group/+massmesh:matrix.org). We'll be most likely to invite you into the team if you: - Have an active interest in growing our network in your neighborhood - Have contributed regularly to the project in the past -- Have an active interest in expanding our capacity in some very involved way (i.e. growing our legal capacity, overhauling our online presence, maintaining social media channels on our behalf.) +- Have an active interest in expanding our capacity in some very involved way (i.e. growing our legal capacity, overhauling our online presence, maintaining social media channels on our behalf, etc.) Generally, if the things you're doing or hope to do involve putting substantial amounts of your time or reputation into the project, you should ask about becoming a core team member. We're trying to build an organization that is volunteer-led, and an inclusive, healthy core team is an important part of that.