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 — how decisions are mademembers.md — how people participatemoderation.md — how the code of conduct is enforcedorganizations.md — how organizations are managedpermissions.md — the permissions members have+-------------------------------------------------+
| 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:
Teams should be made up of:
How teams communicate internally and externally is left to each team to decide, but:
Organization teams are scoped to an organization and govern the projects under it.
They have the same responsibilities as all teams, and additionally:
Organization teams additionally include:
The unified team is an organization team responsible for @unifiedjs.
The remark team is an organization team responsible for @remarkjs.
The rehype team is an organization team responsible for @rehypejs.
The retext team is an organization team responsible for @retextjs.
The redot team is an organization team responsible for @redotjs.
None.
The mdx team is an organization team responsible for @mdx-js.
The micromark team is an organization team responsible for @micromark.
The syntax tree team is an organization team responsible for @syntax-tree.
The vfile team is an organization team responsible for @vfile.
Collective teams are scoped to the whole collective and govern the organizations under it.
They have the same responsibilities as all teams, and additionally:
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 members.
They:
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 members.
The collective is unified as a whole with the organizations under it and the projects under them.
An organization is a collection of projects around a shared area typically hosted in a GitHub organization.
A project is a single repository on GitHub governed by a team.
An initiative is a (proposed) change.
We follow the Contributor Covenant code of conduct. 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).
This project is inspired by the Rust governance proposal, the Node governance docs, the Node admin project, the Electron governance docs, and Django’s dissolving of core.
This work is licensed under a Creative Commons Attribution 4.0 International License.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4