search

mdx-js / mdx

Markdown for the component era
https://mdxjs.com
MIT License
17.74k stars 1.14k forks source link

Governance #343

Closed wooorm closed 5 years ago

wooorm commented 5 years ago

Hi collaborators, contributors, and community! 👋

Governance

I’m checking in with y’all because we’re drafting the governance for this organisation (mdx-js) and unified as a whole. We’re doing that in unifiedjs/governance#2, and would appreciate your feedback.

One important thing we’re striving for is less people with write/merge and/or release rights. I think it’s important, especially because of recent event-stream things, to make MDX secure in that sense too.

It’s important to note that organisations under the collective, in this case MDX, remain relatively self-governed, except for a team of independent moderators (@mdx-js/moderators, the moderation collective team) which moderates the community when needed, and a core team (@mdx-js/core, the core collective team, including @johno) that deals with overarching goals and administration.

Feel free to comment below or in unifiedjs/governance#2 if you have feedback, questions, or suggestions!

GitHub structure

Other than the governance draft linked to earlier (which is pretty vague, we need to specify more stuff on the organisation level), I’m proposing we set up GitHub in the following ways (other than the two aforementioned moderation and core teams):

I suggest @mdx-js/contrib to be removed, or at least to have read rights on the whole org instead of write rights on @mdx-js/mdx?

People

I have reviewed the current people in this organisation, and I suggest the following roles for every current member, however, I’m looking for consensus, and everything’s up for review. The below may sound a bit rude, which is not my intention, I want to properly review membership based on current activity, and reduce the attack vector.

Note that y’all can become a merger, releaser, emeritus, etc if you’d like, this is based on recent activity!

Call for team members

We’re actively looking for team members: be it stakeholders (people who are strongly affected by decisions) or area experts (people who’d love to help build and code up @mdx-js). We’re not just looking for MDX members, but for all the orgs under the unified collective.

If you’d like to join:

Thanks for getting to the end of this way top long issue! 🎉 Titus

ticky commented 5 years ago

That sounds reasonable to me, I was only added under an advisory capacity due to work on prior art!

ChristopherBiscardi commented 5 years ago

Sounds good to me.

With respect to /releasers team. We could keep that low participation (I saw a bunch of comments in the core governance doc about least-privilege) if we set up a continuous release from CI with a tag like 0.16.0-ci.219. I do this in gatsby-mdx and it means that if something gets merged I don't need to do a release to ask someone to test merged code, etc. We already use lerna, so it should be as simple as a script that only runs on master with the ci tag.

"publish-ci": "lerna publish -y --canary --preid ci --npm-tag=ci",
wooorm commented 5 years ago

@ChristopherBiscardi and @ticky you both now have the correct rights and memberships set up. (and Chris, John opened GH-344 with your proposal! 🎉)

wooorm commented 5 years ago

Hey folks just wanted to mention that I‘ve restructured the teams and orgs following the above suggestions, except that Tim appreciated to be on the releasers team as well!

I’m closing this for now, but feel free to respond if you think things should be structured differently!