Skip to content

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

Closed
matplotlib/matplotlib
#26703

Description

@tacaswell

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.

Activity

  1. story645 commented on Apr 20, 2022

    @story645
    Member

    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?

  2. tacaswell commented on Apr 20, 2022

    @tacaswell
    MemberAuthor

    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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions