You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/site/pages/en/about/get-involved/contribute.md
+16-10Lines changed: 16 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,20 +28,26 @@ The Node.js project is currently managed across a number of separate GitHub repo
28
28
29
29
## Code contributions
30
30
31
-
If you'd like to fix bugs or add a new feature to Node.js, please make sure you consult the [Node.js Contribution Guidelines](https://github.com/nodejs/node/blob/main/CONTRIBUTING.md/#pull-requests). The review process by existing collaborators for all contributions to the project is explained there as well.
31
+
If you'd like to fix bugs or add a new feature to Node.js, please make sure you consult the [Node.js Contribution Guidelines](https://github.com/nodejs/node/blob/main/doc/contributing/pull-requests.md). The review process by existing collaborators for all contributions to the project is explained there as well.
32
32
33
33
If you are wondering how to start, you can check [Node Todo](https://www.nodetodo.org/) which may guide you towards your first contribution.
34
34
35
35
## Becoming a collaborator
36
36
37
-
By becoming a collaborator, contributors can have even more impact on the project. They can help other contributors by reviewing their contributions, triage issues and take an even bigger part in shaping the project's future. Individuals identified by the TSC as making significant and valuable contributions across any Node.js repository may be made Collaborators and given commit access to the project. Activities taken into consideration include (but are not limited to) the quality of:
37
+
By becoming a collaborator, contributors can have even more impact on the project. They can help other contributors by reviewing their contributions, triaging issues and taking an even bigger part in shaping the project's future.
38
38
39
-
- code commits and pull requests
40
-
- documentation commits and pull requests
41
-
- comments on issues and pull requests
42
-
- contributions to the Node.js website
43
-
- assistance provided to end users and novice contributors
44
-
- participation in working groups
45
-
- other participation in the wider Node.js community
39
+
Existing collaborators may identify and nominate individuals who make significant and valuable contributions across any Node.js repository to be a new collaborator and give them commit access to the project. Activities taken into consideration include (but are not limited to) the quality of:
46
40
47
-
If individuals making valuable contributions do not believe they have been considered for commit access, they may [log an issue](https://github.com/nodejs/TSC/issues) or [contact a TSC member](https://github.com/nodejs/node#tsc-technical-steering-committee) directly.
41
+
- Commits in the [nodejs/node][] repository.
42
+
- Pull requests and issues opened in the [nodejs/node][] repository.
43
+
- Comments on pull requests and issues in the [nodejs/node][] repository
44
+
- Reviews on pull requests in the [nodejs/node][] repository
45
+
- Help provided to end-users and novice contributors
46
+
- Pull requests and issues opened throughout the Node.js organization
47
+
- Comments on pull requests and issues throughout the Node.js organization
48
+
- Participation in other projects, teams, and working groups of the Node.js organization
49
+
- Other participation in the wider Node.js community
50
+
51
+
Collaborators might overlook someone with valuable contributions. In that case, the contributor may open an issue or contact a collaborator to request a nomination.
0 commit comments