Conversation
This PR adds a new "Roles" section to the Contributing Guide to clarify Mesa's community structure and progression path. It outlines the different ways community members can contribute and grow within the project: - Describes the Contributor, Collaborator, Maintainer and Special roles - Emphasizes that Mesa welcomes contributions from everyone - Explains GitHub permissions and labels for each role - Encourages reaching out to discuss taking on more responsibility - Reinforces that we're all volunteers working together This documentation aims to make Mesa's governance more transparent and welcoming to new contributors while providing clear paths for increased involvement.
| ## Roles in Mesa | ||
| Mesa has several roles to help structure our collaboration and recognize great work. They also form a progression path for community members to that want to take on increasing responsibility in the project. Since we're all volunteers, everyone contributes what they can when they can - there are no minimum time commitments. Also, the best ideas and contributions can come from anyone, these roles are just a way to coordinate our efforts. | ||
|
|
||
| Feel free to reach out to us anytime to discuss your interests and ambitions in the project. We're always happy to chat about how you can grow your involvement in Mesa! |
There was a problem hiding this comment.
I would add a link to the matrix chat in this section
| Maintainers are selected based on their technical expertise, project understanding, and community leadership. Maintainers receive full repository permissions and the "Member" label. | ||
|
|
||
| ### Special Roles | ||
| In some cases, special roles may be created for specific purposes, such as leading particular initiatives or components within Mesa. These roles are created as needed based on project requirements and may come with specific permissions and labels. |
There was a problem hiding this comment.
Reading this I immediately think of Mesa Frames, is that the idea? Regardless, I would add an example here just to give folks an idea.
There was a problem hiding this comment.
Yeah it is indeed. I prefer to keep it a bit open and generic so we don’t have to keep updating it.
|
This is great @ewout! I think having a documented clear path will be very helpful |
|
@tpike3 agree! |
|
|
||
| The license of this project is located in [LICENSE]. By submitting a contribution to this project, you are agreeing that your contribution will be released under the terms of this license. | ||
|
|
||
| ## Maintainers |
There was a problem hiding this comment.
A few thoughts --
-
I think people should be primarily managed at the repo level -- most people should not be across the organization -- most people don't need access to every repo. It is a liability. (This is not captured here, but it is something we should discuss further.)
-
Manage people in group -- I think we should be managing people within groups of permissions instead of individual, so it is very clear who belongs to which group.
There was a problem hiding this comment.
^^ These are just general comments, not specific to this line.
There was a problem hiding this comment.
Do you think we need to document this here / in this document? I don't want to make it too long or formal.
There was a problem hiding this comment.
No -- I think we just need to clean this ups -- and then make sure the labels match these labels in some way to make it very clear what group someone is falling in.
| ### Special Roles | ||
| In some cases, special roles may be created for specific purposes, such as leading particular initiatives or components within Mesa. These roles are created as needed based on project requirements and may come with specific permissions and labels. | ||
|
|
||
| All roles are expected to: |
There was a problem hiding this comment.
This is applied to all roles, yes? It reads like a subsection of special roles.
There was a problem hiding this comment.
In the others it's implied I think
There was a problem hiding this comment.
Maybe we move this up to the top so it is clear?
tpike3
left a comment
tpike3
left a comment
There was a problem hiding this comment.
I think at this point is best to get this merged
|
Let’s merge it as is, and follow-up PRs can be made. |
This PR adds a new "Roles" section to the Contributing Guide to clarify Mesa's community structure and progression path. It outlines the different ways community members can contribute and grow within the project: - Describes the Contributor, Collaborator, Maintainer and Special roles - Emphasizes that Mesa welcomes contributions from everyone - Explains GitHub permissions and labels for each role - Encourages reaching out to discuss taking on more responsibility - Reinforces that we're all volunteers working together This documentation aims to make Mesa's governance more transparent and welcoming to new contributors while providing clear paths for increased involvement.
3 participants
This PR adds a new "Roles" section to the Contributing Guide to clarify Mesa's community structure and progression path. It outlines the different ways community members can contribute and grow within the project:
This documentation aims to make Mesa's governance more transparent and welcoming to new contributors while providing clear paths for increased involvement.
@projectmesa/maintainers this is a first draft based on our internal discussions. Let me know what you think of it, happy to make adjustments.