Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

doc: move WORKING_GROUPS.md into CTC repository #73

Closed
wants to merge 1 commit into from

Conversation

jasnell
Copy link
Member

@jasnell jasnell commented Feb 25, 2017

Move the WORKING_GROUPS.md from the core repo into the CTC repo where it most likely belongs.

@gibfahn
Copy link
Member

gibfahn commented Feb 25, 2017

Are there any links to the old location anywhere? The only reference to WORKING_GROUPS.md I can find is in nodejs/TSC BasePolicies/Charter.md, which doesn't actually have a link (although maybe it should).

gibfahn

This comment was marked as off-topic.

@jasnell
Copy link
Member Author

jasnell commented Feb 25, 2017

No links that I've been able to find.

@Trott
Copy link
Member

Trott commented Feb 26, 2017

What's the motivation for this? Who does this change help? I can be probably persuaded that this is a good move, but it's not immediately obvious that it is.

If I were trying to find a list of Node.js working groups, I'd look in the main repo. A lot of new contributors don't even know this repo exists. A lot of long-time contributors don't know the difference between CTC and TSC and won't know which of those two repos to look in, even in the unlikely event that they know it's in a governance repo and not the main repo.

To me, this hides the information rather than puts it where people are likely to find it.

@jasnell
Copy link
Member Author

jasnell commented Feb 26, 2017

Just tidying up. If it's at all controversial then no worries leaving it where it is.

@sam-github
Copy link

I think its tidier to move it, the current location is an odd fit, but @Trott has a point about findability. Maybe the main nodejs/node README should have a back-link to the CTC, and some text saying "node is only one of the projects under the node foundation umbrella, see ... nodejs/CTC/ for information on the overall project structure" (not those exact words, but that sentiment).

Its hard to get to all the nodejs/ projects, or understand them, and moving some core infrastructure description into CTC/ could help with that, and allow the nodejs/node repo to be more focussed on node.

@jasnell
Copy link
Member Author

jasnell commented Feb 27, 2017

Better navigation is definitely a good thing.

@mhdawson
Copy link
Member

I think I'd vote for the move provide we have a link back from the existing location as suggested by @sam-github

jasnell added a commit that referenced this pull request Mar 6, 2017
@jasnell jasnell closed this Mar 6, 2017
jasnell added a commit to jasnell/node that referenced this pull request Mar 6, 2017
jasnell added a commit to nodejs/node 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]>
evanlucas pushed a commit to nodejs/node 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]>
MylesBorins pushed a commit to nodejs/node 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 to nodejs/node 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]>
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 subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants