Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update GOVERNANCE.md for PyMCon_2022 planning repo #6088

Merged
merged 4 commits into from
Sep 6, 2022
Merged

Conversation

canyon289
Copy link
Member

@OriolAbril let me know if I got this right. If so we can have the other steering committee members review it.

Additionally I can remove all single member additions to the pymcon_2022 repo and instead grant view and commit permissions to all named groups in the pymc-devs organization. This way anyone in those groups can participate in the pymc web series discussion. What do you think of all that?

@canyon289 canyon289 requested a review from OriolAbril August 31, 2022 22:52
GOVERNANCE.md Outdated
@@ -653,6 +653,9 @@ Team:
In addition, Council members are given administrative rights to all repositories within
the [pymc-devs](https://github.com/pymc-devs) organization.

##### Communication Focused Repositroes
Some repositories on Github may be used primarily for internal knowledge store and communication, rather than as codebases that are packaged and deployd. In this case permissions, such as write permissions, will be granted in a manner more like other communication platforms such as slack.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would change the rather than as codebases... to something like rather than content that is curated and published/released _by the project_.

Then also the next sentence:

The permissions of such repositories will be set in order to allow the same participation and access levels we use on private project communication channels like Slack. Therefore, similarly to slack, these repositories will be private and write permissions will be given to all recurrent contributors (that is, anyone with access to slack).

@canyon289
Copy link
Member Author

No changes to rendered docs. Merging

@canyon289 canyon289 merged commit 1ad177a into main Sep 6, 2022
@OriolAbril OriolAbril deleted the update_governance branch September 6, 2022 12:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants