to: @nodejs/tsc
cc: @nodejs/community-committee, @nodejs/collaborators
The proposal is to move the Node.js Code of Conduct into it's own repository (e.g. https://github.com/nodejs/code-of-conduct).
-
The TSC would retain ownership of the CoC. The nodejs/tsc team would have ownership / commit rights to the new repository. Oversight over the content of the CoC would remain with the TSC. Proposed changes to the TSC would be submitted as Pull Requests that would be subject to review and approval from the TSC, just as they are today.
-
The goal is to make the CoC (a) easier to discover, (b) easier to reuse across all Node.js Foundation projects, and (c) easier to version independently of Core.
-
As is the case today, Working Groups and projects would retain the autonomy to choose their own Code of Conduct. The Node.js CoC would continue to be the default choice for all Working Groups and projects that do not explicitly choose a different CoC.
Ref: nodejs/community-committee#7
to: @nodejs/tsc
cc: @nodejs/community-committee, @nodejs/collaborators
The proposal is to move the Node.js Code of Conduct into it's own repository (e.g.
https://github.com/nodejs/code-of-conduct).The TSC would retain ownership of the CoC. The nodejs/tsc team would have ownership / commit rights to the new repository. Oversight over the content of the CoC would remain with the TSC. Proposed changes to the TSC would be submitted as Pull Requests that would be subject to review and approval from the TSC, just as they are today.
The goal is to make the CoC (a) easier to discover, (b) easier to reuse across all Node.js Foundation projects, and (c) easier to version independently of Core.
As is the case today, Working Groups and projects would retain the autonomy to choose their own Code of Conduct. The Node.js CoC would continue to be the default choice for all Working Groups and projects that do not explicitly choose a different CoC.
Ref: nodejs/community-committee#7