Skip to content

Move the communication guidelines to the (future) development guide repo #24

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

Closed
tacaswell opened this issue Apr 20, 2022 · 2 comments · Fixed by matplotlib/matplotlib#26703

Comments

@tacaswell
Copy link
Member

waiting on matplotlib/matplotlib#22866

It is simpler if all of the content in this repo is content that requires sign off from a majority of the steering council to change.

We want to be more agile/have less ceremony on the communication guidelines.

@story645
Copy link
Member

story645 commented Apr 20, 2022

We want to be more agile/have less ceremony on the communication guidelines

what do you mean by this? just that changes to the comms docs shouldn't need steering council sign off?

@tacaswell
Copy link
Member Author

Correct, the governance has a process for changing it self which has high level of ceremony and sign off (because changing the governance should be a rare-ish thing) vs the communication guidelines which I would put on the same footing as the PR review guidance or development guide which we want to be able to be able to update as we need.

Rather than having to on a case-by-case basis having to decide if the PR to this repo needs the higher level of scrutiny, I want to remove anything that does not need it that level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants