Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: first draft governance proposal #1953

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
143 changes: 143 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,143 @@
# Code of Conduct

Standard is an [contributor covenant](https://www.contributor-covenant.org/) abiding organization.
Specifically, we have adopted [Code of Conduct v2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).

## Reporting Issues
To report issues please use the [Standard Discord Channel](https://discord.gg/ZegqCBr) and direct message a staff member.
The full text of the code of conduct is included below.

--
## Contributor Covenant Code of Conduct v2.1

### Our Pledge

We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, caste, color, religion, or sexual
identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.

### Our Standards

Examples of behavior that contributes to a positive environment for our
community include:

* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
* Focusing on what is best not just for us as individuals, but for the overall
community

Examples of unacceptable behavior include:

* The use of sexualized language or imagery, and sexual attention or advances of
any kind
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email address,
without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting

### Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.

Community leaders have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions that are
not aligned to this Code of Conduct, and will communicate reasons for moderation
decisions when appropriate.

### Scope

This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official email address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.

### Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement as outlined above
in [Reporting](#reporting). All complaints will be reviewed and investigated
promptly and fairly.

All community leaders are obligated to respect the privacy and security of the
reporter of any incident.

### Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:

#### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.

#### 2. Warning

**Community Impact**: A violation through a single incident or series of
actions.

**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or permanent
ban.

#### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.

#### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within the
community.

### Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.1, available at
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].

Community Impact Guidelines were inspired by
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].

For answers to common questions about this code of conduct, see the FAQ at
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
[https://www.contributor-covenant.org/translations][translations].

[homepage]: https://www.contributor-covenant.org
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
[Mozilla CoC]: https://github.com/mozilla/diversity
[FAQ]: https://www.contributor-covenant.org/faq
[translations]: https://www.contributor-covenant.org/translations

97 changes: 97 additions & 0 deletions GOVERNANCE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,97 @@
# Standard Project Governance

<!-- TOC -->

* [Organizers](#organizers)
* [Collaborators](#collaborators)
* [Collaborator activities](#collaborator-activities)
* [Rule Adoption Committee](#rule-adoption-committee)
* [Consensus seeking process](#consensus-seeking-process)

<!-- /TOC -->

## Organizers

Standard organizers are the organization owners and lead maintainers.
They are the only members of the `@standard/leads` team. The organizers
are the curators of the standard project and their key responsibility
is to issue releases of standard packages and its dependencies.

## Collaborators

Standard collaborators maintain the projects of the standard organization.

They are split into the following teams:

| Team | Responsibility | Repository |
|---|---|---|
| `@standard/leads` | Standard lead maintainers | GitHub organization owners |
| `@standard/core` | Standard Core development | `standard`, `standard-engine`, `eslint-config-standard`, `eslint-config-standard-with-typescript` |
| `@standard/config` | Build, maintain and release standard configs | `eslint-config-standard`, `eslint-config-standard-with-typescript` |

Every member of the org is also part of `@standard/standard`.

Collaborators have:

* Commit access to the projects repository of the team they belong
* Grant to request/suggest a new release following the [semver](https://semver.org/) model.

Both collaborators and non-collaborators may propose changes to the source code
of the projects of the organization. The mechanism to propose such a change is a
GitHub pull request. Collaborators review and merge (_land_) pull requests
following the [CONTRIBUTING](CONTRIBUTING.md#rules) guidelines.

### Collaborator activities

* Helping users and novice contributors
* Contributing code and documentation changes that improve the project
* Reviewing and commenting on issues and pull requests
* Participation in working groups
* Merging pull requests
* Release configs

## Collaborator nominations

Individuals making significant and valuable contributions to the project may be
a candidate to join the Standard organization.

A collaborator needs to open a private team discussion on GitHub and list the
candidates they want to sponsor with a link to the user's contributions. For
example:

* Activities in the standard organization
`[USERNAME](https://github.com/search?q=author:USERNAME+org:standard)`

Otherwise, a contributor may self-apply if they believe they meet the above
criteria by reaching out to a lead maintainer privately with the links to their
valuable contributions. The lead maintainers will reply to the Contributor and
will decide if candidate it to be made a collaborator.

The consensus to grant a new candidate collaborator status is reached when:

- at least one of the organizers approve
- at least two of the team members approve

After these conditions are satisfied, the [onboarding
process](CONTRIBUTING.md#onboarding-collaborators) may start.

## Rule Adoption Committee
A subset of collaborators and organizers form the rule adoption committee.
The rule adoption committee has final authority over the rules adopted by standard.
The rule adoption committee is to meet once quarterly to discuss adoption of proposed rules to Standard.
These rules adjustments may be proposed by any member of the community at large and are to be added the
rule adoption committee agenda for discussion during each committee meeting.
Given that the rule adoption committee also consists of members of the standard organization,
other issues may also be discussed as needed.

## Organizer nominations

A team member may be promoted to an organizer only through nomination by a
organizer and with consensus from the rest of organizers.

## Consensus seeking process

The standard organization follows a [Consensus Seeking][] decision-making model.

[Consensus Seeking]:
https://en.wikipedia.org/wiki/Consensus-seeking_decision-making