Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

Merged

Conversation

story645
Copy link
Member

@story645story645 commentedSep 6, 2023
edited
Loading

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:

  1. move over file and add to index,closesMove the communication guidelines to the (future) development guide repo governance#24
  2. update the guidelines with current info, supercedesUpdate comms guidelines governance#36
  3. guidelines for changing guidelines, inline with the API guidance, supercedescomm lead should review changes to guidlines governance#31
  4. update the release guide to use the communications channels listed in the comms guide
  5. removed the checklist code from the pr-guideline b/c I made it a class in 4.

attn: @matplotlib/steering-council

@story645story645 added governanceneeds approval from @steering-council Documentation: devdocsfiles in doc/devel labelsSep 6, 2023
@story645story645force-pushed thecommunication_guidelines branch 3 times, most recently fromb5c473a toa5c92ceCompareSeptember 24, 2023 07:02
@story645story645force-pushed thecommunication_guidelines branch 2 times, most recently from94cab67 to783bb50CompareOctober 6, 2023 14:02
@story645
Copy link
MemberAuthor

story645 commentedOct 31, 2023
edited
Loading

@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 😅

Copy link
Member

@timhoffmtimhoffm left a 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 reacted with hooray emoji
@story645
Copy link
MemberAuthor

story645 commentedNov 1, 2023
edited
Loading

do you want to keep the individual commits or can we squash?

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)

timhoffm reacted with thumbs up emoji

@story645story645force-pushed thecommunication_guidelines branch from4caf7c2 to0887901CompareNovember 1, 2023 08:07
@story645
Copy link
MemberAuthor

Also once this gets merged, the comms guide needs to get deleted in governance, but do we add a redirect (and if so where?)

@timhoffm
Copy link
Member

Also 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.

@story645
Copy link
MemberAuthor

I don’t think the comma guide is something that many people have referenced

I send it to people but I think I've always used the repo

@timhoffmtimhoffm added this to thev3.8-doc milestoneNov 1, 2023
@timhoffmtimhoffm merged commitca1880b intomatplotlib:mainNov 1, 2023
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull requestNov 1, 2023
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull requestNov 1, 2023
QuLogic added a commit that referenced this pull requestNov 1, 2023
…703-on-v3.8.xBackport PR#26703 on branch v3.8.x (moved communications guidelines from governance, updated and clarified process )
QuLogic added a commit that referenced this pull requestNov 1, 2023
…703-on-v3.8.1-docBackport 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 requestNov 2, 2023
@story645story645 deleted the communication_guidelines branchNovember 2, 2023 00:33
story645 added a commit to story645/governance that referenced this pull requestNov 2, 2023
story645 pushed a commit to story645/matplotlib that referenced this pull requestNov 2, 2023
…linesmoved communications guidelines from governance, updated and clarified process
story645 added a commit to story645/governance that referenced this pull requestNov 2, 2023
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@timhoffmtimhoffmtimhoffm approved these changes

@efiringefiringAwaiting requested review from efiring

@dopplershiftdopplershiftAwaiting requested review from dopplershift

Assignees
No one assigned
Labels
Documentation: devdocsfiles in doc/develgovernanceneeds approval from @steering-council
Projects
None yet
Milestone
v3.8-doc
Development

Successfully merging this pull request may close these issues.

Move the communication guidelines to the (future) development guide repo
2 participants
@story645@timhoffm

[8]ページ先頭

©2009-2025 Movatter.jp