Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/unifiedjs/collective
How the unified collective is governed
https://github.com/unifiedjs/collective
community docs governance unified
Last synced: 3 months ago
JSON representation
How the unified collective is governed
- Host: GitHub
- URL: https://github.com/unifiedjs/collective
- Owner: unifiedjs
- Created: 2018-11-20T19:38:03.000Z (about 6 years ago)
- Default Branch: main
- Last Pushed: 2024-10-02T15:21:10.000Z (4 months ago)
- Last Synced: 2024-10-30T00:00:02.677Z (3 months ago)
- Topics: community, docs, governance, unified
- Language: JavaScript
- Homepage: https://unifiedjs.com
- Size: 153 KB
- Stars: 58
- Watchers: 14
- Forks: 3
- Open Issues: 1
-
Metadata Files:
- Readme: readme.md
- Code of conduct: code-of-conduct.md
Awesome Lists containing this project
README
# Collective governance
The unified collective is a federated system of organizations, consisting in
turn of projects, governed by the team members steering them.This project is maintained by the unified collective core team and describes how
the collective is governed.This document describes the teams of the collective.
Additional policies describe other aspects of governance in detail:* [`decisions.md`][decisions-policy] — how decisions are made
* [`members.md`][members-policy] — how people participate
* [`moderation.md`][moderation-policy] — how the code of conduct is enforced
* [`organizations.md`][organizations-policy] — how organizations are managed
* [`permissions.md`][permissions-policy] — the permissions members have## Table of contents
* [Teams](#teams)
* [Organization teams](#organization-teams)
* [unified team](#unified-team)
* [remark team](#remark-team)
* [rehype team](#rehype-team)
* [retext team](#retext-team)
* [redot team](#redot-team)
* [mdx team](#mdx-team)
* [micromark team](#micromark-team)
* [syntax tree team](#syntax-tree-team)
* [vfile team](#vfile-team)
* [Collective teams](#collective-teams)
* [Core team](#core-team)
* [Moderation team](#moderation-team)
* [Glossary](#glossary)
* [Code of conduct](#code-of-conduct)
* [Acknowledgements](#acknowledgements)
* [License](#license)## Teams
```ascii
+-------------------------------------------------+
| COLLECTIVE |
| core & moderation |
| |
| |
| ORGANIZATIONS |
| +-------------+ +-------------+ +-------------+ |
| | unified | | remark | | rehype | |
| +-------------+ +-------------+ +-------------+ |
| +-------------+ +-------------+ +-------------+ |
| | retext | | redot | | mdx | |
| +-------------+ +-------------+ +-------------+ |
| +-------------+ +-------------+ +-------------+ |
| | micromark | | vfile | | syntax tree | |
| +-------------+ +-------------+ +-------------+ |
+-------------------------------------------------+
```The collective is governed by teams.
Teams are scoped to one **organization** or the **collective**, respectively
governing the **projects** or **organizations** under them.
The [core][] and [moderation][] teams are special.Teams serve as leadership for their scope.
They:* **Set the direction**:
setting the values that are used when making decisions about tradeoffs,
steering the scope toward specific directions, and leading the discussion
for initiatives
* **Shepherd initiatives**:
making stakeholders (people who are strongly affected by decisions) aware of
initiatives, teasing out design tradeoffs and alternatives, and helping
build consensus
* **Accept or reject issues, pull requests, and RFCs**:
deciding on initiatives, whether small or substantial
* **Nominate team members**:
nominating individuals making significant and valuable contributions across
to be part of the teamTeams should be made up of:
* **Area experts**:
people who have a lot of interest and expertise in the area covered by the
team, but who may be far less engaged with other areas of the collective
* **Stakeholders**:
people who are strongly affected by decisions in the area of the team, but
who may not be experts in the design or implementation of that areaHow teams communicate internally and externally is left to each team to decide,
but:* Discussion should take place as much as possible in public spaces, ideally
on issues, pull requests, or GitHub discussions
* Teams should actively seek out discussion and input from non-members## Organization teams
**Organization teams** are scoped to an organization and govern the projects
under it.They have the same responsibilities as [all teams][all], and additionally:
* **Escalate initiatives affecting the collective to a collective team**
* **Implement accepted collective-level initiatives**
* **Define policy on what form changes should take**:
such as which can be a direct pull request or RFC, which need to be
escalated, and which can be handled by the team itselfOrganization teams additionally include:
* **Team lead**:
person responsible for ensuring initiatives are progressing at a reasonable
rate### unified team
The **unified team** is an *[organization][]* team responsible for
[**@unifiedjs**](https://github.com/unifiedjs).#### Members
##### Releasers
* Remco Haszing
([**@remcohaszing**](https://github.com/remcohaszing))
\* Titus Wormer
([**@wooorm**](https://github.com/wooorm))
\
(**lead**)##### Mergers
* Christian Murphy
([**@ChristianMurphy**](https://github.com/ChristianMurphy))
\* John Otander
([**@johno**](https://github.com/johno))
\* Joun Qin
([**@JounQin**](https://github.com/JounQin))
\* Junyoung Choi
([**@Rokt33r**](https://github.com/Rokt33r))
\* Merlijn Vos
([**@Murderlon**](https://github.com/Murderlon))
\#### Contributors
* Mudit Ameta
([**@zeusdeux**](https://github.com/zeusdeux))
\* Stephan Schneider
([**@zcei**](https://github.com/zcei))
\* Victor Felder
([**@vhf**](https://github.com/vhf))
\### remark team
The **remark team** is an *[organization][]* team responsible for
[**@remarkjs**](https://github.com/remarkjs).#### Members
##### Releasers
* John Otander
([**@johno**](https://github.com/johno))
\* Remco Haszing
([**@remcohaszing**](https://github.com/remcohaszing))
\* Titus Wormer
([**@wooorm**](https://github.com/wooorm))
\
(**lead**)##### Mergers
* Christian Murphy
([**@ChristianMurphy**](https://github.com/ChristianMurphy))
\* Jonathan Haines
([**@BarryThePenguin**](https://github.com/BarryThePenguin))
\* Joun Qin
([**@JounQin**](https://github.com/JounQin))
\* Junyoung Choi
([**@Rokt33r**](https://github.com/Rokt33r))
\* Keith McKnight
([**@kmck**](https://github.com/kmck))
\* Marouane Fazouane
([**@fazouane-marouane**](https://github.com/fazouane-marouane))
\* Merlijn Vos
([**@Murderlon**](https://github.com/Murderlon))
\* Victor Felder
([**@vhf**](https://github.com/vhf))
\* Zeke Sikelianos
([**@zeke**](https://github.com/zeke))
\#### Contributors
* Mudit Ameta
([**@zeusdeux**](https://github.com/zeusdeux))
\* Nikita Sobolev
([**@sobolevn**](https://github.com/sobolevn))
\### rehype team
The **rehype team** is an *[organization][]* team responsible for
[**@rehypejs**](https://github.com/rehypejs).#### Members
##### Releasers
* Keith McKnight
([**@kmck**](https://github.com/kmck))
\* Remco Haszing
([**@remcohaszing**](https://github.com/remcohaszing))
\* Titus Wormer
([**@wooorm**](https://github.com/wooorm))
\
(**lead**)##### Mergers
* Christian Murphy
([**@ChristianMurphy**](https://github.com/ChristianMurphy))
\* John Otander
([**@johno**](https://github.com/johno))
\* Joun Qin
([**@JounQin**](https://github.com/JounQin))
\* Merlijn Vos
([**@Murderlon**](https://github.com/Murderlon))
\#### Contributors
* Victor Felder
([**@vhf**](https://github.com/vhf))
\### retext team
The **retext team** is an *[organization][]* team responsible for
[**@retextjs**](https://github.com/retextjs).#### Members
##### Releasers
* Titus Wormer
([**@wooorm**](https://github.com/wooorm))
\
(**lead**)##### Mergers
* Merlijn Vos
([**@Murderlon**](https://github.com/Murderlon))
\#### Contributors
* Richard Littauer
([**@RichardLitt**](https://github.com/RichardLitt))
\### redot team
The **redot team** is an *[organization][]* team responsible for
[**@redotjs**](https://github.com/redotjs).#### Members
##### Releasers
* Christian Murphy
([**@ChristianMurphy**](https://github.com/ChristianMurphy))
\
(**lead**)* Titus Wormer
([**@wooorm**](https://github.com/wooorm))
\##### Mergers
None.
### mdx team
The **mdx team** is an *[organization][]* team responsible for
[**@mdx-js**](https://github.com/mdx-js).#### Members
##### Releasers
* John Otander
([**@johno**](https://github.com/johno))
\
(**lead**)* Remco Haszing
([**@remcohaszing**](https://github.com/remcohaszing))
\* Tim Neutkens
([**@timneutkens**](https://github.com/timneutkens))
\* Titus Wormer
([**@wooorm**](https://github.com/wooorm))
\##### Mergers
* Christopher Biscardi
([**@ChristopherBiscardi**](https://github.com/ChristopherBiscardi))
\* Joun Qin
([**@JounQin**](https://github.com/JounQin))
\* Laurie Barth
([**@laurieontech**](https://github.com/laurieontech))* Sidhartha Chatterjee
([**@sidharthachatterjee**](https://github.com/sidharthachatterjee))
\#### Contributors
* Adam Morse
([**@mrmrs**](https://github.com/mrmrs))
\* Ahmad Awais
([**@ahmadawais**](https://github.com/ahmadawais))
\* Brent Jackson
([**@jxnblk**](https://github.com/jxnblk))
\* Guillermo Rauch
([**@rauchg**](https://github.com/rauchg))
\* Jessica Stokes
([**@ticky**](https://github.com/ticky))
\* Stephan Schneider
([**@zcei**](https://github.com/zcei))
\### micromark team
The **micromark team** is an *[organization][]* team responsible for
[**@micromark**](https://github.com/micromark).#### Members
##### Releasers
* Titus Wormer
([**@wooorm**](https://github.com/wooorm))
\
(**lead**)##### Mergers
* John Otander
([**@johno**](https://github.com/johno))
\* Joun Qin
([**@JounQin**](https://github.com/JounQin))
\* Marouane Fazouane
([**@fazouane-marouane**](https://github.com/fazouane-marouane))
\* Merlijn Vos
([**@Murderlon**](https://github.com/Murderlon))
\* Remco Haszing
([**@remcohaszing**](https://github.com/remcohaszing))
\#### Contributors
* Mudit Ameta
([**@zeusdeux**](https://github.com/zeusdeux))
\* Stephan Schneider
([**@zcei**](https://github.com/zcei))
\* Victor Felder
([**@vhf**](https://github.com/vhf))
\### syntax tree team
The **syntax tree team** is an *[organization][]* team responsible for
[**@syntax-tree**](https://github.com/syntax-tree).#### Members
##### Releasers
* Keith McKnight
([**@kmck**](https://github.com/kmck))
\* Titus Wormer
([**@wooorm**](https://github.com/wooorm))
\
(**lead**)##### Mergers
* Christian Murphy
([**@ChristianMurphy**](https://github.com/ChristianMurphy))
\* Jonathan Haines
([**@BarryThePenguin**](https://github.com/BarryThePenguin))
\* Joun Qin
([**@JounQin**](https://github.com/JounQin))
\* Merlijn Vos
([**@Murderlon**](https://github.com/Murderlon))
\* Remco Haszing
([**@remcohaszing**](https://github.com/remcohaszing))
\### vfile team
The **vfile team** is an *[organization][]* team responsible for
[**@vfile**](https://github.com/vfile).#### Members
##### Releasers
* Titus Wormer
([**@wooorm**](https://github.com/wooorm))
\
(**lead**)##### Mergers
* Christian Murphy
([**@ChristianMurphy**](https://github.com/ChristianMurphy))
\* Joun Qin
([**@JounQin**](https://github.com/JounQin))
\* Junyoung Choi
([**@Rokt33r**](https://github.com/Rokt33r))
\* Remco Haszing
([**@remcohaszing**](https://github.com/remcohaszing))
\#### Contributors
* Olivia Hugger
([**@komaeda**](https://github.com/komaeda))
\## Collective teams
**Collective teams** are scoped to the whole collective and govern the
organizations under it.They have the same responsibilities as [all teams][all], and additionally:
* **De-escalate initiatives to organization teams**
* **Focus on overarching concerns**:
they are specifically designed to take a *global* view of the collective, to
make sure the pieces are fitting together in a coherent way### Core team
The **core team** is a *[collective][]* team responsible for governing all
other teams.
This team does not have a lead and, to limit conflicts of interest, **should**
not include **[moderation team][moderation]** members.They:
* **Set the direction and vision for the collective across organizations**:
setting the core values that are used when making decisions about tradeoffs,
steering the collective toward specific directions, and leading the
discussion for **major** initiatives
* **Spin up or shut down teams**:
creating teams around new (temporary) areas and dissolving teams when their
area is complete
* **Accept or reject motions**:
deciding on initiatives involving people and destructive actions on projects
* **Follow playbooks**:
following certain steps to enact accepted motions#### Members
* Christian Murphy
([**@ChristianMurphy**](https://github.com/ChristianMurphy))
\* John Otander
([**@johno**](https://github.com/johno))
\* Merlijn Vos
([**@Murderlon**](https://github.com/Murderlon))
\* Titus Wormer
([**@wooorm**](https://github.com/wooorm))
\#### Contributors
* Richard Littauer
([**@RichardLitt**](https://github.com/RichardLitt))
\* Stephan Schneider
([**@zcei**](https://github.com/zcei))
\### Moderation team
The **moderation team** is a *[collective][]* team responsible for enforcing the
code of conduct.
This team does not have a lead and, to limit conflicts of interest, **should**
not include **[core team][core]** members.#### Members
* Olivia Hugger
([**@komaeda**](https://github.com/komaeda))
\* Richard Littauer
([**@RichardLitt**](https://github.com/RichardLitt))
\## Glossary
###### Collective
The collective is unified as a whole with the [organization][dfn-organization]s
under it and the [project][dfn-project]s under them.###### Organization
An organization is a collection of [project][dfn-project]s around a shared area
typically hosted in a GitHub organization.###### Project
A project is a single repository on GitHub governed by a team.
###### Initiative
An initiative is a (proposed) change.
## Code of conduct
We follow the Contributor Covenant [code of conduct][coc].
Please read it, as you agree to abide by it by interacting with the collective
spaces (includes any online or offline place such as email, GitHub, npm, or
Twitter).## Acknowledgements
This project is inspired by the [Rust governance proposal][rust], the [Node
governance docs][node], the [Node admin project][node-admin], the [Electron
governance docs][electron], and [Django’s dissolving of core][django].## License
This work is licensed under a
[Creative Commons Attribution 4.0 International License][license].[all]: #teams
[collective]: #collective-teams
[organization]: #organization-teams
[core]: #core-team
[moderation]: #moderation-team
[dfn-organization]: #organization
[dfn-project]: #project
[decisions-policy]: decisions.md
[members-policy]: members.md
[moderation-policy]: moderation.md
[organizations-policy]: organizations.md
[permissions-policy]: permissions.md
[coc]: code-of-conduct.md
[rust]: https://github.com/rust-lang/rfcs/blob/HEAD/text/1068-rust-governance.md
[node]: https://github.com/nodejs/node/blob/HEAD/GOVERNANCE.md
[node-admin]: https://github.com/nodejs/admin
[electron]: https://github.com/electron/governance
[django]: https://github.com/django/deps/blob/HEAD/accepted/0010-new-governance.rst
[license]: https://creativecommons.org/licenses/by/4.0/