overhaul governance #7

story645 · 2019-12-10T23:21:04Z

Based on this weeks dev call, temporarily putting the following docs here:

Social Media/Communications Guidelines
Contributor Roadmap
Named Roles (which maybe should be part of the people?
Sorry, didn't realize I could push directly to this repo. 🙁

communications_guidelines.md

contributor_roadmap.md

trallard

I added a few comments to the docs.
Some other things that came to mind while going over these are:

How is the onboarding of these folks happening? - i.e. do you have a manual or a call or the such
How can also folks step down from their responsibilities shall their circumstances change?

contributor_roadmap.md

trallard · 2020-01-06T12:52:18Z

contributor_roadmap.md

+- potential repercussion of a [Code of Conduct](https://www.python.org/psf/conduct/) violation
+
+
+# Community / communications


I like the fact that there is an emphasis on the folks observing the Code of Conduct and that breaches to this would lead to revoking their privileges. A quick search did not point me to clear guidelines on how to report this or enforce the CoC (maybe my search-fu failed) .

So maybe it would also be useful to appoint a code of conduct person or subteam

On our to-do list is to adopt the Python CoC to an MPL specific one and then include enforcement details and reporting - which will be to NumFocus so that there's an external record of the report.

named_project_roles.md

story645 · 2020-01-08T17:58:26Z

Thanks for all the feedback!

How is the onboarding of these folks happening? - i.e. do you have a manual or a call or the such

We have a post on discourse and the plan is to ultimately move these documents into the docs. Would love to do community calls but don't have anyone with the bandwidth to run them at the moment.

How can also folks step down from their responsibilities shall their circumstances change?

We're working on sorting that out, so TBD

astraw · 2020-01-08T18:30:58Z

I just want to say as a long-ago MPL contributor that, while I have surely lost all right to commit, I am very pleased that MPL is so vibrant today. And -- what a sign of strength to see this thread! It makes me really happy and I'm sure John Hunter would be proud and justifiably so. We use MPL every day in my lab. Thanks for all you are doing and please feel free to remove me from all relevant permissions, as I unfortunately cannot foresee becoming an active MPL developer again.

tacaswell · 2020-03-05T23:00:36Z

I have hi-jacked this PR to also include broader overhaul of the governance (as the Deputy Lead Developer roles sync up well with the onboarding path.

I can move those commits to a different branch if people prefer.

story645 · 2020-03-05T23:39:40Z

contributor_roadmap.md

+- get triage privileges: granted on 1st merged pull request
+    - (We need to write the script for this, run as a service on heroku’s free tier?  can we do this with actions?)
+
+**Get commit privileges:**


Who gets to decide what is significant or sustained? What's the criteria here?

Would sustain mean x number of PRs over x months? Would there also be a mechanism to remove this if folks go MIA or need a break?

attn @samdbrice, it's a thing on our todo list to clarify.

story645 · 2020-03-05T23:40:53Z

contributor_roadmap.md

+- repeated or severe violations of [merge guidelines](https://matplotlib.org/devdocs/devel/coding_guide.html)
+- potential repercussion of a [Code of Conduct](https://www.python.org/psf/conduct/) violation
+
+# Release Powers


really release managment, & you need a how they get it/how they lose it section

story645 · 2020-03-05T23:47:14Z

contributor_roadmap.md

+
+**tweet as twitter account:**
+- be a lead on at least one of the other community projects
+


add the release manager to this list or just set something up on matplotbot to auto tweet when a release gets tagged?

story645 · 2020-03-05T23:49:11Z

contributor_roadmap.md

+- potential repercussion of a [Code of Conduct](https://www.python.org/psf/conduct/) violation
+-  at discretion of [communications lead](named_project_roles.md)
+
+# Github


this whole block is a missing a how you get/how you lose

story645 · 2020-03-05T23:49:39Z

governance.md

@@ -30,7 +30,7 @@ Development Team (MDT)" in the project license.  Anyone can be a
 Contributor. Contributors can be affiliated with any legal entity or
 none. Contributors participate in the project by submitting, reviewing
 and discussing GitHub Pull Requests and Issues and participating in
-open and public Project discussions on GitHub, Google+, Hackpad,
+open and public Project discussions on GitHub, discourse, Hackpad,


i think you mean hackmd - we don't use a hackpad

story645 · 2020-03-05T23:56:33Z

governance.md

 to code, code review, infrastructure work, mailing list and chat participation,
-community help/building, education and outreach, design work, etc. We are
+community help/building, education and outreach, design work, etc.  We are


community building, user and developer support,

story645 · 2020-03-05T23:57:26Z

governance.md

+inactive for a period of 2 months, they will be approached by the LD to see if
+they plan on returning to active participation.  If not they will be asked to
+step down, if the Council Member indicates they intend to be active again but
+have not done so after 1 month the Council my vote to remove them.


story645 · 2020-03-05T23:58:15Z

governance.md

+listed on the project website, acknowledging the period during which they were
+active in the Council.
+
+The Council reserves the right to eject current Members, other than the LD, if


so uh, how do they stage a coup 😉?

like as much as I was joking, I think it would be good to have an actual structural way to address BDFL/steering committee/etc problems. Not 'cause I think anybody is a problem, but b/c these are the sorts of things you'd rather write explicitly when you don't need them and never use than not write & have to figure out when you need them. I don't love forking as a solution 'cause I think a end goal of governance is also to mitigate potential fallout especially where the community is concerned.

The governance already suggests forking if the community disagrees with the direction the project is going, however on a bit more consideration, I added that the NF board can evict the PL as they are on the hook that our conduct is inline with their non-profit status.

I'm on board w/ NumFocus as final arbiter, but I'm still a bit unclear as to why in this governance structure the Steering council can evict each other but not the project lead given that it falls under the whole "steering the direction of the project" thing.

governance.md

story645 · 2020-03-06T00:01:22Z

governance.md

-Changes to the governance documents are submitted via a GitHub pull
-request to The Project's governance documents GitHub repository at
+Changes to the governance documents are submitted via a GitHub pull request to
+The Project's governance documents GitHub repository at


is this gonna change if this all moves to the main docs?

no, I think it should stay in it's own repository, even if we publish build artifacts as part of the main docs.

contributor_roadmap.md

governance.md

story645 · 2020-03-23T20:03:39Z

governance.md

+
+**Developer Relations**
+
+In addition to communication to end-users we need to maintain


This is still end users too given discourse management falls under this

story645 · 2020-03-23T20:05:17Z

governance.md

+- Maintaining a "matplotlib update" slide deck
+- the [Ann] mailing list
+
+This communication is primarily broadcast out and intended to engage


and developers of 3rd party libraries. Also I just don't like the language of end users, user/developer split.

I am not a fan either, but was having trouble finding other words for it.

Co-Authored-By: Tim Hoffmann <[email protected]>

- BDFL is an inside joke that has gotten outside of the in-group where it was funny. I feel dumb using it to describe my self, but the look on my in-laws face when I used the term was the final straw. - Deputy Lead Developers aka "named roles" is a way to recognize that people are leading development along different axes of process. This is motivated by several aspects: 1. empower people to make decisions 2. provide a title people can put on their resume's

No fundamental changes, just wording and a bit of re-arrangement.

- adjust BDFL -> LD - add emphasis to financial / fund raising aspect of council - assert the LD counts in the council size

- introduce 2yr terms. We want people to be able to gracefully roll out of responsibility. - introduce A/B staggered classes. To make sure we maintain some continuity

Given that our Steering Council is smaller than Jupyters, do not imply Institutional Partners can install Council Members.

Given that we have a smaller council, expect all to participate. If someone has gone inactive, then they should be removed first.

jklymak · 2020-07-13T21:10:20Z

governance.md

+
+
+### API consistency Leader
+


I'd consider merging this and reference documentation.

I did this, but a private conversation with @timhoffm changed my mind back to it being two roles.

The API lead needs to have a broad view of the library and good design taste, the reference doc lead needs to be an expert at rst and documenting what the library actually does (independent if it is a good idea or not ;) )

story645 · 2020-07-27T06:23:38Z

Closing in favor of #10 & #11, which I think supersede this?

story645 added the enhancement label Dec 10, 2019

timhoffm reviewed Dec 15, 2019

View reviewed changes

trallard reviewed Jan 6, 2020

View reviewed changes

story645 commented Mar 6, 2020

View reviewed changes

trallard reviewed Mar 12, 2020

View reviewed changes

contributor_roadmap.md Show resolved Hide resolved

tacaswell reviewed Mar 16, 2020

View reviewed changes

governance.md Show resolved Hide resolved

story645 commented Mar 23, 2020

View reviewed changes

tacaswell mentioned this pull request May 11, 2020

Communication guide #9

Merged

story645 and others added 19 commits July 13, 2020 12:45

onboarding oriented governance docs

dfbfb4c

typo

a881edf

Co-Authored-By: Tim Hoffmann <[email protected]>

adding https

e905b13

Co-Authored-By: Tim Hoffmann <[email protected]>

DOC: google+ is dead

6eec206

GOV: re-write BDFL -> LD section

22dab36

No fundamental changes, just wording and a bit of re-arrangement.

GOV: tweak Steering Council a bit

47e92f3

- adjust BDFL -> LD - add emphasis to financial / fund raising aspect of council - assert the LD counts in the council size

GOV: substantially re-write the council member section

f444ad2

- introduce 2yr terms. We want people to be able to gracefully roll out of responsibility. - introduce A/B staggered classes. To make sure we maintain some continuity

GOV: update wording in CoI section

d03518a

GOV: slight wording change to Council communications

f516380

GOV: clear out rest of BDFL -> LD

6cc3f3c

GOV: tweak wording for institutional partners

a1cb7b5

Given that our Steering Council is smaller than Jupyters, do not imply Institutional Partners can install Council Members.

GOV: tweak rules to change governance

9f1de2a

Given that we have a smaller council, expect all to participate. If someone has gone inactive, then they should be removed first.

GOV: add sketch of DLD titles

d574592

STY: strip trailing whitespace

3eccd6e

GOV: Do not need owners of org outside of SC

22b47fa

GOV: make the get a commit bit wording consistent

a591e2a

GOV: move github admin and separate from dev / release sections

c8c7d2d

GOV: add domain project leads

3c89228

tacaswell added 4 commits July 13, 2020 12:45

GOV: adjust contributor roadmap to match current state

9d2cecb

GOV: change "Lead Developer" -> "Project Leader"

6f220a2

GOV: start to flesh out the deputy roles based on call

0b3db52

Add additional line to secretary role

3417e50

tacaswell force-pushed the guidelines branch from 0f8840f to 3417e50 Compare July 13, 2020 16:48

tacaswell changed the title ~~onboarding oriented governance docs~~ overhaul governance Jul 13, 2020

jklymak reviewed Jul 13, 2020

View reviewed changes

This was referenced Jul 27, 2020

Governance #10

Merged

Onboarding #11

Open

story645 closed this Jul 27, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

overhaul governance #7

overhaul governance #7

story645 commented Dec 10, 2019 •

edited

Loading

trallard left a comment

trallard Jan 6, 2020

story645 Jan 8, 2020

story645 commented Jan 8, 2020 •

edited

Loading

astraw commented Jan 8, 2020

tacaswell commented Mar 5, 2020

story645 Mar 5, 2020

trallard Mar 12, 2020

story645 Jul 8, 2020

story645 Mar 5, 2020

story645 Mar 5, 2020

story645 Mar 5, 2020

story645 Mar 5, 2020

story645 Mar 5, 2020

story645 Mar 5, 2020

story645 Mar 5, 2020

tacaswell Jul 13, 2020

story645 Jul 13, 2020

tacaswell Jul 27, 2020

story645 Jul 27, 2020 •

edited

Loading

story645 Mar 6, 2020

tacaswell Jul 13, 2020

story645 Mar 23, 2020

story645 Mar 23, 2020

tacaswell Mar 23, 2020

story645 Mar 23, 2020

jklymak Jul 13, 2020

tacaswell Jul 27, 2020

story645 commented Jul 27, 2020

		- potential repercussion of a [Code of Conduct](https://www.python.org/psf/conduct/) violation


		# Community / communications


		tweet as twitter account:
		- be a lead on at least one of the other community projects


		Developer Relations

		In addition to communication to end-users we need to maintain

overhaul governance #7

overhaul governance #7

Conversation

story645 commented Dec 10, 2019 • edited Loading

trallard left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

story645 commented Jan 8, 2020 • edited Loading

astraw commented Jan 8, 2020

tacaswell commented Mar 5, 2020

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

story645 Jul 27, 2020 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

story645 commented Jul 27, 2020

story645 commented Dec 10, 2019 •

edited

Loading

story645 commented Jan 8, 2020 •

edited

Loading

story645 Jul 27, 2020 •

edited

Loading