Repository navigation
Proposal: Move Code-of-Conduct into separate repository #224
Description
Activity
I don't see any drawbacks of this.
The TSC discussed this last week and opted to move the Code of Conduct into the TSC repo for the time being, and to replace the current document in the main repo with a pointer to the new location. We can make a decision later on as to whether moving it into a completely separate repo is the better long term option
Core PR: nodejs/node#12147
TSC PR: #232This has been done.
- added a commit that references this issue
on May 15, 2017 - added a commit that references this issue
on May 18, 2017 - added 2 commits that reference this issue
on May 29, 2017 - added a commit that references this issue
on Jul 19, 2017 - added a commit that references this issue
on Apr 8, 2024
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