Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

meta: move WORKING_GROUPS.md to CTC repo #11555

Closed
wants to merge 1 commit into from

Conversation

jasnell
Copy link
Member

@jasnell jasnell commented Feb 25, 2017

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-bot nodejs-github-bot added the meta Issues and PRs related to the general management of the project. label Feb 25, 2017
@Trott
Copy link
Member

Trott commented Feb 26, 2017

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
Member Author

jasnell commented Feb 26, 2017

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
Member

gibfahn commented Feb 26, 2017

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
Member Author

jasnell commented Feb 27, 2017

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

@Trott
Copy link
Member

Trott commented Feb 27, 2017

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

@jasnell
Copy link
Member Author

jasnell commented Mar 6, 2017

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 <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
@jasnell
Copy link
Member Author

jasnell commented Mar 7, 2017

Landed in 06942d8

@jasnell jasnell 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 <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
@evanlucas evanlucas 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 <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
MylesBorins pushed a commit that referenced this pull request Apr 19, 2017
PR-URL: #11555
Ref: nodejs/CTC#73
Reviewed-By: Gibson Fahnestock <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
@MylesBorins MylesBorins 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 <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues 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