create public nodejs/collaborators repo

[MylesBorins]

It seems to me like there is a need for us to have a place for collaborators to discuss ideas that are not appropriate for the main tracker.

I'd like to suggest that we create a new repo nodejs/collaborators, similar to nodejs/tsc and nodejs/ctc, as a place for these discussions to happen.

This could also be a great place to move conversations that have a good kernel but are inappropriate or derailing in other environments.

Unlike NG or EPS, collaborators would be an explicitly social repo, where we can explore ideas in good faith.

Thoughts @nodejs/collaborators

[addaleax]

Isn’t this basically what nodejs/CTC is supposed to be? If not: How would it be different? :)

[MylesBorins]

@addaleax perhaps you are right. After re-reading the README.md it is dawning on me that perhaps I had the wrong idea about what the CTC repos purpose was.

I'm going to close this with that in mind. If others think this has legs feel free to reopen

[Qard]

I've never really even looked at the CTC repo because the name just gave me the impression it was just for CTC members and not the greater contributor community. Might be nice to rename it to nodejs/collaborators.

[nebrius]

I've never really even looked at the CTC repo because the name just gave me the impression it was just for CTC members and not the greater contributor community. Might be nice to rename it to nodejs/collaborators.

I never really looked at it either, for this same reason. I thought it's purpose would be analogous to nodejs/TSC which is just for TSC business.

[refack]

I support the node/collaborators idea. That way the node/CTC is kept for CTC related coordination.

[refack]

I've never really even looked at the CTC repo because the name just gave me the impression it was just for CTC members and not the greater contributor community. Might be nice to rename it to nodejs/collaborators.

I never really looked at it either, for this same reason. I thought it's purpose would be analogous to nodejs/TSC which is just for TSC business.

You guys have been teaching me that wording makes a difference 👐 (no cynicism!)

[williamkapke]

FYI, this exists:
https://github.com/nodejs/collaboration

[addaleax]

I’m reopening, moving to nodejs/collaborators doesn’t seem like a bad idea. /cc @jasnell who originally created the repo, iirc

FYI, this exists:
https://github.com/nodejs/collaboration

I know we talked about archiving that together with the nodejs/collaboration team, and I agree. It just seems like a stalled project that people only know about because it comes up in the autocompletion for nodejs/collaborators…

[refack]

I’m reopening, moving to nodejs/collaborators doesn’t seem like a bad idea. /cc @jasnell who originally created the repo, iirc

FYI, this exists:
https://github.com/nodejs/collaboration

But rename to nodejs/Collaborators yes? Re branding for new shot of life

[nebrius]

I forgot about nodejs/collaboration! It is also somewhat poorely named, as it's really nodejs/working-group-collaboration.

The idea behind that working group was to serve as a sort of clearing house for working groups, and to create a space for working groups to communicate with one another more easily. At the time, it was difficult for different working groups to talk to each other. IIRC myself and a few others from the now inactive nodejs/hardware WG were having a tough time getting in touch with folks we needed to in trying to get some initiatives going.

All of that said, I'm not sure this is as much of an issue anymore. nodejs/collaboration was created before the Node.js Foundation was created, and I suspect that the structure we've created within the Foundation since then has more or less solved that particular problem. However, if there is still a need for such a group, then nodejs/community-committee is probably a good place to start organizing it.

[refack]

I jumped the gun, but I have a few questions I wanted to put in writing.

[jasnell]

At this point I am definitely -1 on creating another new repository for discussion. We have the existing nodejs/node, nodejs/ctc, nodejs/tsc, nodejs/NG, and nodejs/node-eps repositories. Perhaps the existing nodejs/collaboration repo can be repurposed, but I still see no need.

[addaleax]

Renaming nodejs/CTC to nodejs/collaborators seems perfectly fine to me.