Skip to content

Commit bdd647d

Browse files
authored
docs: repoint readers to shared .github files (fastify#5268)
1 parent 62f564d commit bdd647d

File tree

3 files changed

+6
-438
lines changed

3 files changed

+6
-438
lines changed

CODE_OF_CONDUCT.md

Lines changed: 2 additions & 176 deletions
Original file line numberDiff line numberDiff line change
@@ -1,178 +1,4 @@
11
# Code of Conduct
22

3-
Fastify, as member project of the OpenJS Foundation, use [Contributor Covenant
4-
v2.0](https://contributor-covenant.org/version/2/0/code_of_conduct) as their
5-
code of conduct. The full text is included
6-
[below](#contributor-covenant-code-of-conduct) in English, and translations are
7-
available from the Contributor Covenant organisation:
8-
9-
- [contributor-covenant.org/translations](https://www.contributor-covenant.org/translations)
10-
- [github.com/ContributorCovenant](https://github.com/ContributorCovenant/contributor_covenant/tree/release/content/version/2/0)
11-
12-
Refer to the sections on reporting and escalation in this document for the
13-
specific emails that can be used to report and escalate issues.
14-
15-
## Reporting
16-
17-
### Project Spaces
18-
19-
For reporting issues in spaces related to Fastify please use the email
20-
`[email protected]` or `[email protected]`. Fastify handles CoC issues
21-
related to the spaces that it maintains. Projects maintainers commit to:
22-
23-
- maintain the confidentiality with regard to the reporter of an incident
24-
- to participate in the path for escalation as outlined in the section on
25-
Escalation when required.
26-
27-
### Foundation Spaces
28-
29-
For reporting issues in spaces managed by the OpenJS Foundation, for example,
30-
repositories within the OpenJS organization, use the email
31-
`[email protected]`. The Cross Project Council (CPC) is responsible for
32-
managing these reports and commits to:
33-
34-
- maintain the confidentiality with regard to the reporter of an incident
35-
- to participate in the path for escalation as outlined in the section on
36-
Escalation when required.
37-
38-
## Escalation
39-
40-
The OpenJS Foundation maintains a Code of Conduct Panel (CoCP). This is a
41-
foundation-wide team established to manage escalation when a reporter believes
42-
that a report to a member project or the CPC has not been properly handled. In
43-
order to escalate to the CoCP send an email to
44-
45-
46-
For more information, refer to the full [Code of Conduct governance
47-
document](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md).
48-
49-
---
50-
51-
## Contributor Covenant Code of Conduct v2.0
52-
53-
### Our Pledge
54-
55-
We as members, contributors, and leaders pledge to make participation in our
56-
community a harassment-free experience for everyone, regardless of age, body
57-
size, visible or invisible disability, ethnicity, sex characteristics, gender
58-
identity and expression, level of experience, education, socio-economic status,
59-
nationality, personal appearance, race, religion, or sexual identity and
60-
orientation.
61-
62-
We pledge to act and interact in ways that contribute to an open, welcoming,
63-
diverse, inclusive, and healthy community.
64-
65-
### Our Standards
66-
67-
Examples of behavior that contributes to a positive environment for our
68-
community include:
69-
70-
* Demonstrating empathy and kindness toward other people
71-
* Being respectful of differing opinions, viewpoints, and experiences
72-
* Giving and gracefully accepting constructive feedback
73-
* Accepting responsibility and apologizing to those affected by our mistakes,
74-
and learning from the experience
75-
* Focusing on what is best not just for us as individuals, but for the overall
76-
community
77-
78-
Examples of unacceptable behavior include:
79-
80-
* The use of sexualized language or imagery, and sexual attention or advances of
81-
any kind
82-
* Trolling, insulting or derogatory comments, and personal or political attacks
83-
* Public or private harassment
84-
* Publishing others' private information, such as a physical or email address,
85-
without their explicit permission
86-
* Other conduct which could reasonably be considered inappropriate in a
87-
professional setting
88-
89-
### Enforcement Responsibilities
90-
91-
Community leaders are responsible for clarifying and enforcing our standards of
92-
acceptable behavior and will take appropriate and fair corrective action in
93-
response to any behavior that they deem inappropriate, threatening, offensive,
94-
or harmful.
95-
96-
Community leaders have the right and responsibility to remove, edit, or reject
97-
comments, commits, code, wiki edits, issues, and other contributions that are
98-
not aligned to this Code of Conduct, and will communicate reasons for moderation
99-
decisions when appropriate.
100-
101-
### Scope
102-
103-
This Code of Conduct applies within all community spaces, and also applies when
104-
an individual is officially representing the community in public spaces.
105-
Examples of representing our community include using an official e-mail address,
106-
posting via an official social media account, or acting as an appointed
107-
representative at an online or offline event.
108-
109-
### Enforcement
110-
111-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
112-
reported to the community leaders responsible for enforcement at the email
113-
addresses listed above in the [Reporting](#reporting) and
114-
[Escalation](#escalation) sections. All complaints will be reviewed and
115-
investigated promptly and fairly.
116-
117-
All community leaders are obligated to respect the privacy and security of the
118-
reporter of any incident.
119-
120-
### Enforcement Guidelines
121-
122-
Community leaders will follow these Community Impact Guidelines in determining
123-
the consequences for any action they deem in violation of this Code of Conduct:
124-
125-
#### 1. Correction
126-
127-
**Community Impact**: Use of inappropriate language or other behavior deemed
128-
unprofessional or unwelcome in the community.
129-
130-
**Consequence**: A private, written warning from community leaders, providing
131-
clarity around the nature of the violation and an explanation of why the
132-
behavior was inappropriate. A public apology may be requested.
133-
134-
#### 2. Warning
135-
136-
**Community Impact**: A violation through a single incident or series of
137-
actions.
138-
139-
**Consequence**: A warning with consequences for continued behavior. No
140-
interaction with the people involved, including unsolicited interaction with
141-
those enforcing the Code of Conduct, for a specified period of time. This
142-
includes avoiding interactions in community spaces as well as external channels
143-
like social media. Violating these terms may lead to a temporary or permanent
144-
ban.
145-
146-
#### 3. Temporary Ban
147-
148-
**Community Impact**: A serious violation of community standards, including
149-
sustained inappropriate behavior.
150-
151-
**Consequence**: A temporary ban from any sort of interaction or public
152-
communication with the community for a specified period of time. No public or
153-
private interaction with the people involved, including unsolicited interaction
154-
with those enforcing the Code of Conduct, is allowed during this period.
155-
Violating these terms may lead to a permanent ban.
156-
157-
#### 4. Permanent Ban
158-
159-
**Community Impact**: Demonstrating a pattern of violation of community
160-
standards, including sustained inappropriate behavior, harassment of an
161-
individual, or aggression toward or disparagement of classes of individuals.
162-
163-
**Consequence**: A permanent ban from any sort of public interaction within the
164-
project community.
165-
166-
### Attribution
167-
168-
This Code of Conduct is adapted from the [Contributor
169-
Covenant](https://www.contributor-covenant.org), version 2.0, available at
170-
[contributor-covenant.org/version/2/0/code_of_conduct](https://www.contributor-covenant.org/version/2/0/code_of_conduct).
171-
172-
Community Impact Guidelines were inspired by [Mozilla's code of conduct
173-
enforcement ladder](https://github.com/mozilla/diversity).
174-
175-
For answers to common questions about this code of conduct, see the FAQ at
176-
[contributor-covenant.org/faq](https://www.contributor-covenant.org/faq).
177-
Translations are available at
178-
[contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).
3+
Please see Fastify's [organization-wide code of conduct
4+
](https://github.com/fastify/.github/blob/main/CODE_OF_CONDUCT.md).

GOVERNANCE.md

Lines changed: 2 additions & 105 deletions
Original file line numberDiff line numberDiff line change
@@ -1,107 +1,4 @@
11
# Fastify Project Governance
22

3-
<!-- TOC -->
4-
5-
* [Lead Maintainers](#lead-maintainers)
6-
* [Collaborators](#collaborators)
7-
* [Collaborator activities](#collaborator-activities)
8-
* [Great Contributors](#great-contributors)
9-
* [Collaborator nominations](#collaborator-maintainers-nominations)
10-
* [Lead Maintainers nominations](#lead-maintainers-nominations)
11-
* [Consensus seeking process](#consensus-seeking-process)
12-
13-
<!-- /TOC -->
14-
15-
## Lead Maintainers
16-
17-
Fastify Lead Maintainers are the organization owners.
18-
They are the only members of the `@fastify/leads` team. The Lead
19-
Maintainers are the curator of the Fastify project and their key responsibility
20-
is to issue releases of Fastify and its dependencies.
21-
They manage the [Open Collective](./EXPENSE_POLICY.md) funds and are responsible
22-
for approving expenses and invoices.
23-
24-
## Collaborators
25-
26-
Fastify Collaborators maintain the projects of the Fastify organization.
27-
28-
They are split into the following teams:
29-
30-
| Team | Responsibility | Repository |
31-
|---|---|---|
32-
| `@fastify/leads` | Fastify Lead Maintainers | GitHub organization owners |
33-
| `@fastify/core` | Fastify Core development | `fastify`, `fast-json-stringify`, `light-my-request`, `fastify-plugin`, `middie` |
34-
| `@fastify/plugins` | Build, maintain and release Fastify plugins | All plugins repositories |
35-
| `@fastify/benchmarks` | Build and maintain our benchmarks suite | `benchmarks` |
36-
| `@fastify/docs-chinese` | Translate the Fastify documentation in Chinese | `docs-chinese` |
37-
38-
Every member of the org is also part of `@fastify/fastify`.
39-
40-
Collaborators have:
41-
42-
* Commit access to the projects repository of the team they belong
43-
* Grant to release new versions of the project
44-
45-
Both Collaborators and non-Collaborators may propose changes to the source code
46-
of the projects of the organization. The mechanism to propose such a change is a
47-
GitHub pull request. Collaborators review and merge (_land_) pull requests
48-
following the [CONTRIBUTING](CONTRIBUTING.md#rules) guidelines.
49-
50-
### Collaborator activities
51-
52-
* Helping users and novice contributors
53-
* Contributing code and documentation changes that improve the project
54-
* Reviewing and commenting on issues and pull requests
55-
* Participation in working groups
56-
* Merging pull requests
57-
* Release plugins
58-
59-
The Lead Maintainers can remove inactive Collaborators or provide them with
60-
_Past Collaborators_ status. Past Collaborators may request that the Lead
61-
Maintainers restore them to active status.
62-
63-
64-
## Great Contributors
65-
66-
Great contributors on a specific area in the Fastify ecosystem will be invited
67-
to join this group by Lead Maintainers. This group has the same permissions of a
68-
contributor.
69-
70-
## Collaborator nominations
71-
72-
Individuals making significant and valuable contributions to the project may be
73-
a candidate to join the Fastify organization.
74-
75-
A Collaborator needs to open a private team discussion on GitHub and list the
76-
candidates they want to sponsor with a link to the user's contributions. For
77-
example:
78-
79-
* Activities in the Fastify organization
80-
`[USERNAME](https://github.com/search?q=author:USERNAME+org:fastify)`
81-
82-
Otherwise, a Contributor may self-apply if they believe they meet the above
83-
criteria by reaching out to a Lead Maintainer privately with the links to their
84-
valuable contributions. The Lead Maintainers will reply to the Contributor and
85-
will decide if candidate it to be made a collaborator.
86-
87-
The consensus to grant a new candidate Collaborator status is reached when:
88-
89-
- at least one of the Lead Maintainers approve
90-
- at least two of the Team Members approve
91-
92-
After these conditions are satisfied, the [onboarding
93-
process](CONTRIBUTING.md#onboarding-collaborators) may start.
94-
95-
96-
## Lead Maintainers nominations
97-
98-
A Team Member may be promoted to a Lead Maintainers only through nomination by a
99-
Lead maintainer and with agreement from the rest of Lead Maintainers.
100-
101-
102-
## Consensus seeking process
103-
104-
The Fastify organization follows a [Consensus Seeking][] decision-making model.
105-
106-
[Consensus Seeking]:
107-
https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
3+
Please see Fastify's [organization-wide governance
4+
](https://github.com/fastify/.github/blob/main/GOVERNANCE.md) document.

0 commit comments

Comments
 (0)