Proposal: Move Code-of-Conduct into separate repository #224
Comments
|
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 |
jasnell
added a commit
to jasnell/TSC
that referenced
this issue
Mar 31, 2017
This was referenced Mar 31, 2017
|
Core PR: nodejs/node#12147 |
jasnell
added a commit
that referenced
this issue
Apr 17, 2017
* meta: move the code of conduct into the TSC repository Refs: #224 * doc: update links to the Code of Conduct
jasnell
added a commit
to jasnell/node
that referenced
this issue
Apr 17, 2017
jasnell
added a commit
to nodejs/node
that referenced
this issue
Apr 17, 2017
PR-URL: #12147 Ref: nodejs/TSC#224 Ref: nodejs/TSC#232 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
|
This has been done. |
evanlucas
pushed a commit
to nodejs/node
that referenced
this issue
Apr 25, 2017
PR-URL: #12147 Ref: nodejs/TSC#224 Ref: nodejs/TSC#232 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
evanlucas
pushed a commit
to nodejs/node
that referenced
this issue
May 1, 2017
PR-URL: #12147 Ref: nodejs/TSC#224 Ref: nodejs/TSC#232 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
evanlucas
pushed a commit
to nodejs/node
that referenced
this issue
May 2, 2017
PR-URL: #12147 Ref: nodejs/TSC#224 Ref: nodejs/TSC#232 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
gibfahn
pushed a commit
to nodejs/node
that referenced
this issue
May 15, 2017
PR-URL: #12147 Ref: nodejs/TSC#224 Ref: nodejs/TSC#232 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
MylesBorins
pushed a commit
to nodejs/node
that referenced
this issue
May 18, 2017
PR-URL: #12147 Ref: nodejs/TSC#224 Ref: nodejs/TSC#232 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
mhdawson
added a commit
to mhdawson/benchmarking
that referenced
this issue
May 29, 2017
Update to use shared code of conduct. See nodejs/TSC#224 for background discussion. The benchmarking WG CoC was an exact copy anyway.
mhdawson
added a commit
to nodejs/benchmarking
that referenced
this issue
Jun 1, 2017
Update to use shared code of conduct. See nodejs/TSC#224 for background discussion. The benchmarking WG CoC was an exact copy anyway. PR-URL: #112 Reviewed-By: Gareth Ellis <gareth.ellis@uk.ibm.com>
andrew749
pushed a commit
to michielbaird/node
that referenced
this issue
Jul 19, 2017
PR-URL: nodejs/node#12147 Ref: nodejs/TSC#224 Ref: nodejs/TSC#232 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
rluvaton
pushed a commit
to nodejs/performance
that referenced
this issue
Apr 8, 2024
Update to use shared code of conduct. See nodejs/TSC#224 for background discussion. The benchmarking WG CoC was an exact copy anyway. PR-URL: nodejs/benchmarking#112 Reviewed-By: Gareth Ellis <gareth.ellis@uk.ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: