Skip to content

Commit 1968eed

Browse files
authored
Update Contributing.md doc (#194)
1 parent bad5938 commit 1968eed

File tree

1 file changed

+9
-25
lines changed

1 file changed

+9
-25
lines changed

CONTRIBUTING.md

+9-25
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,11 @@ See the [public meeting notes](https://docs.google.com/document/d/1CIMGoIOZ-c3-i
88
for a summary description of past meetings. To request edit access, join the
99
meeting or get in touch on [Gitter](https://gitter.im/open-telemetry/opentelemetry-python).
1010

11+
See to the [community membership document](https://github.com/open-telemetry/community/blob/master/community-membership.md)
12+
on how to become a [**Member**](https://github.com/open-telemetry/community/blob/master/community-membership.md#member),
13+
[**Approver**](https://github.com/open-telemetry/community/blob/master/community-membership.md#approver)
14+
and [**Maintainer**](https://github.com/open-telemetry/community/blob/master/community-membership.md#maintainer).
15+
1116
## Development
1217

1318
This project uses [`tox`](https://tox.readthedocs.io) to automate some aspects
@@ -74,15 +79,16 @@ Open a pull request against the main `opentelemetry-python` repo.
7479
### How to Get PRs Merged
7580

7681
A PR is considered to be **ready to merge** when:
77-
* It has received two approvals from Collaborators/Maintainers (at different
78-
companies).
82+
* It has received two approvals from [Approvers](https://github.com/open-telemetry/community/blob/master/community-membership.md#approver)
83+
/ [Maintainers](https://github.com/open-telemetry/community/blob/master/community-membership.md#maintainer)
84+
(at different companies).
7985
* Major feedbacks are resolved.
8086
* It has been open for review for at least one working day. This gives people
8187
reasonable time to review.
8288
* Trivial change (typo, cosmetic, doc, etc.) doesn't have to wait for one day.
8389
* Urgent fix can take exception as long as it has been actively communicated.
8490

85-
Any Collaborator/Maintainer can merge the PR once it is **ready to merge**.
91+
Any Approver / Maintainer can merge the PR once it is **ready to merge**.
8692

8793
## Design Choices
8894

@@ -111,25 +117,3 @@ For a deeper discussion, see: https://github.com/open-telemetry/opentelemetry-sp
111117
as specified with the [napolean
112118
extension](http://www.sphinx-doc.org/en/master/usage/extensions/napoleon.html#google-vs-numpy)
113119
extension in [Sphinx](http://www.sphinx-doc.org/en/master/index.html).
114-
115-
## Become a Collaborator
116-
117-
Collaborators have write access to the repo.
118-
119-
To become a Collaborator:
120-
* Become an active Contributor by working on PRs.
121-
* Actively participate in the community meeting, design discussion, PR review
122-
and issue discussion.
123-
* Contact the Maintainers, express the willingness and commitment.
124-
* Acknowledged and approved by two Maintainers (at different companies).
125-
126-
## Become a Maintainer
127-
128-
Maintainers have admin access to the repo.
129-
130-
To become a Maintainer:
131-
* Become a [member of OpenTelemetry organization](https://github.com/orgs/open-telemetry/people).
132-
* Become a Collaborator.
133-
* Demonstrate the ability and commitment.
134-
* Contact the Maintainers, express the willingness and commitment.
135-
* Acknowledged and approved by all the current Maintainers.

0 commit comments

Comments
 (0)