Create a GOVERNANCE document for our community #78
Conversation
The document specifies the roles within our community, including their responsibilities and how they are appointed. The document does not list current holders of each role (except the BDFL and Founders), which will be managed through GitHub teams and displayed on our website instead. Draws on similar documents from SimPEG, Jupyter, Numpy, and SciPy.
|
As BDFL, I nominate @santisoler @aguspesce @MGomezN @LL-Geo to form the initial Steering Council. Please add your approval to this PR if you agree to serve on the Council. Once formed, the Council will then appoint people to the Community Manager and Package Maintainer roles during our regular meetings. |
|
Comments and suggestions to this document are more than welcome from anyone in our community! If there are no objections by Thursday 2022-11-17 (in time for our weekly meeting), I will take that as agreement from the community to merge this PR. |
This will be handled through GitHub and our website instead.
|
Update: I've been experimenting with fetching the user information from GitHub teams using their REST API. It's a bit complicated since there is a rate limit to how often I can make requests. It seems like the only way to get team members and their names is to make 1 request per member. But there is a limit of 60 requests per hour so it's very easy to run out. So maybe that's not the best idea. Instead, we could list people in Markdown files like we do with the Authors already. |
I approve my nomination as member of the Steering Council 👨🏼⚖️ |
There was a problem hiding this comment.
Really like this! Thanks for taking the time to write this @leouieda. I left just one minor question below.
The document is a simple logbook to track social media and website posts. It should be improved later with some automatization <!-- Thank you for contributing a pull request to Fatiando! 💖 👆🏽 ABOVE: Describe the changes proposed and WHY you made them. 👇🏽 BELOW: Link to any relevant issue or pull request. Please ensure you have taken a look at the CONTRIBUTING.md file in this repository (if available) and the general guidelines at https://github.com/fatiando/community/blob/main/CONTRIBUTING.md --> **Relevant issues/PRs:** Fixes #107 / For account access, see ACCOUNTS.md, and #98 / For community manager responsibilities, see GOVERNANCE.md and #78 <!-- Example: "Fixes #1234" / "See also #345" / "Relevant to #111" Use keywords (e.g., Fixes, Closes) to create the links and automatically close issues when this PR is merged. See https://github.com/blog/1506-closing-issues-via-pull-requests -->
The document specifies the roles within our community, including their responsibilities and how they are appointed. The document does not list current holders of each role (except the BDFL and Founders), which will be managed through GitHub teams and displayed on our website instead. These rules were discussed and agreed upon during our 2022-11-09 community call https://github.com/fatiando/community/blob/main/development-calls/2022.md#2022-11-09. To start things off, I (Leonardo Uieda) will be appointed as BDFL. Draws on similar documents from SimPEG, Jupyter, Numpy, and SciPy.
Relevant issues/PRs:
Fixes #76