Skip to content

meta: move WORKING_GROUPS.md to CTC repo - #11555

Closed
jasnell wants to merge 1 commit into
nodejs:masterfrom
jasnell:move-working-groups
Closed

meta: move WORKING_GROUPS.md to CTC repo#11555
jasnell wants to merge 1 commit into
nodejs:masterfrom
jasnell:move-working-groups

Conversation

@jasnell

Copy link
Copy Markdown
Member

Move the working groups doc the CTC repo, where it more likely belongs...

Ref: nodejs/CTC#73

Checklist
  • documentation is changed or added
Affected core subsystem(s)

meta

@nodejs-github-botnodejs-github-bot added the meta Issues and PRs related to the general management of the project. label Feb 25, 2017
@Trott

Copy link
Copy Markdown
Member

Do we have a criteria for what belongs there and what belongs here? I would imagine the main criterion would be "Where will someone who is looking for X expect to find it?"

With CTC meeting notes and agendas, the answer might be the CTC repo.

But for a list of working groups? I'd look in the main repo. A lot of new contributors aren't even aware the CTC exists, much less the CTC repo. It would be a shame to move this information to a lower-visibility area like that. Also, having it there suggests that these are CTC working groups instead of Node.js working groups.

@jasnell

Copy link
Copy Markdown
MemberAuthor

Nope, no such criteria exists in any documented manner.

Having it there suggests that these are CTC working groups ...

The first sentence of the working groups page also suggests that these are CTC working groups:

Specifically:

Node.js Core Working Groups are autonomous projects created by the Core Technical Committee (CTC).

For me, this falls under the same category of information as the list of dependent/adjacent projects in the TSC repo.

These are formed by petitioning the CTC, they are chartered by the CTC and the information makes sense to me to keep there.

That said, if it's at all controversial I'm not going to insist on it by any means, mainly just doing a bit of housekeeping.

@gibfahn

Copy link
Copy Markdown
Member

I think if this document was linked to from the README.md and CONTRIBUTING.md then it wouldn't matter where it was. I'm not sure I've ever noticed it, even in the top level of nodejs/node.

@jasnell

Copy link
Copy Markdown
MemberAuthor

@Trott ... so I'm clear, are you against moving this?

@Trott

Copy link
Copy Markdown
Member

@jasnell I'm not against it if we have a link in the nodejs/node README or somewhere else sensible/findable.

@jasnell
jasnellforce-pushed the move-working-groups branch from 2cd132b to 96b1ec9CompareMarch 6, 2017 22:29
@jasnell

Copy link
Copy Markdown
MemberAuthor

Link to the new location added to the readme

jasnell added a commit that referenced this pull request Mar 7, 2017
PR-URL: #11555
Ref: nodejs/CTC#73
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
@jasnell

Copy link
Copy Markdown
MemberAuthor

Landed in 06942d8

@jasnelljasnell closed this Mar 7, 2017
evanlucas pushed a commit that referenced this pull request Mar 8, 2017
PR-URL: #11555
Ref: nodejs/CTC#73
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
@evanlucasevanlucas mentioned this pull request Mar 8, 2017
MylesBorins pushed a commit that referenced this pull request Apr 17, 2017
PR-URL: #11555
Ref: nodejs/CTC#73
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
MylesBorins pushed a commit that referenced this pull request Apr 19, 2017
PR-URL: #11555
Ref: nodejs/CTC#73
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
@MylesBorinsMylesBorins mentioned this pull request Apr 19, 2017
andrew749 pushed a commit to michielbaird/node that referenced this pull request Jul 19, 2017
PR-URL: nodejs/node#11555
Ref: nodejs/CTC#73
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

metaIssues and PRs related to the general management of the project.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@jasnell@Trott@gibfahn@bnoordhuis@MylesBorins@nodejs-github-bot