{{ message }}
moved communications guidelines from governance, updated and clarified process - #26703
Merged
Merged
Conversation
story645
added
governance
story645
force-pushed
the
communication_guidelines
branch
3 times, most recently
from
September 24, 2023 07:02
b5c473a to
a5c92ce
Compare
timhoffm
reviewed
Oct 5, 2023
story645
force-pushed
the
communication_guidelines
branch
2 times, most recently
from
October 6, 2023 14:02
94cab67 to
783bb50
Compare
Member
Author
timhoffm
reviewed
Nov 1, 2023
Member
Author
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 formatting Co-authored-by: Tim Hoffmann <2836374+timhoffm@users.noreply.github.com>
story645
force-pushed
the
communication_guidelines
branch
from
November 1, 2023 08:07
4caf7c2 to
0887901
Compare
Member
Author
|
Also once this gets merged, the comms guide needs to get deleted in governance, but do we add a redirect (and if so where?) |
Member
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. |
Member
Author
meeseeksmachine
pushed a commit
to meeseeksmachine/matplotlib
that referenced
this pull request
Nov 1, 2023
…vernance, updated and clarified process
meeseeksmachine
pushed a commit
to meeseeksmachine/matplotlib
that referenced
this pull request
Nov 1, 2023
…vernance, updated and clarified process
This was referenced Nov 1, 2023
QuLogic
added a commit
that referenced
this pull request
Nov 1, 2023
…703-on-v3.8.x Backport PR #26703 on branch v3.8.x (moved communications guidelines from governance, updated and clarified process )
QuLogic
added a commit
that referenced
this pull request
Nov 1, 2023
…703-on-v3.8.1-doc Backport PR #26703 on branch v3.8.1-doc (moved communications guidelines from governance, updated and clarified process )
story645
added a commit
to story645/governance
that referenced
this pull request
Nov 2, 2023
story645
added a commit
to story645/governance
that referenced
this pull request
Nov 2, 2023
story645
pushed a commit
to story645/matplotlib
that referenced
this pull request
Nov 2, 2023
…lines moved communications guidelines from governance, updated and clarified process
1 task
story645
added a commit
to story645/governance
that referenced
this pull request
Nov 2, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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