Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
moved communications guidelines from governance, updated and clarified process#26703
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
b5c473a
toa5c92ce
CompareUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
94cab67
to783bb50
Comparestory645 commentedOct 31, 2023 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
@timhoffm made all the changes and keep running into instances where it'd be really convenient to be able to cross ref the list of our communications channels 😅 |
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I‘ve fixed some formatting.
Anybody can merge after CI pass.@story645 do you want to keep the individual commits or can we squash?
story645 commentedNov 1, 2023 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I'd rather keep them separate here b/c they're all doing different things - but I'll rebase your fixes so it's cleaner. (basically I remembered/learned how to reorder commits) |
Fix section title formattingCo-authored-by: Tim Hoffmann <2836374+timhoffm@users.noreply.github.com>
4caf7c2
to0887901
CompareAlso once this gets merged, the comms guide needs to get deleted in governance, but do we add a redirect (and if so where?) |
IMHO a redirect is not necessary. I don’t think the comma guide is something that many people have referenced. Also, redirects are nice for usability but not a strict requirement. |
I send it to people but I think I've always used the repo |
…vernance, updated and clarified process
…vernance, updated and clarified process
…703-on-v3.8.xBackport PR#26703 on branch v3.8.x (moved communications guidelines from governance, updated and clarified process )
…703-on-v3.8.1-docBackport PR#26703 on branch v3.8.1-doc (moved communications guidelines from governance, updated and clarified process )
…linesmoved communications guidelines from governance, updated and clarified process
Uh oh!
There was an error while loading.Please reload this page.
There's been an open issue for a while to move the communications guidelines out of the governance repository because it should function more like code or documentation guidelines. In that issue the move was waiting on a new development repo, but I figure as an incremental step it can be moved into the development guidelines section with the other documents that are more geared towards maintainers because maintainers are the audience it is currently written for. I broke up this change into:
attn: @matplotlib/steering-council