Rename of "language groups" from iojs-* to nodejs-*

[srl295]

Related to #2367 (comment) et al. Given convergence, the question comes up about the WG names iojs-* changing to nodejs-*?

For stability and continuity, each group may need to rename itself, or at least come to consensus.

The TSC could provide guidance here.

[thefourtheye]

Cc @nodejs/tsc

[mikeal]

A few notes: fully formed and functional working groups are autonomous, so the most we can do is suggest a name change to those working groups.

However, many of the language communities are inactive and we should be able to transition them to a new name. My suggestion would be:

• Use "nodejs-", we discussed some alternatives like "community-" but I think this is better and has parity with what we did before. The concern i remember noted was that we have "node-gyp" and other "node-" things, but we don't have any nodejs- things so this should be fine.
• Post an issue to every WG repo proposing the change. Note that inactive repos will be migrated by a certain date, while active communities should take this opportunity to consider a name change and decide how to handle it themselves.

[srl295]

@mikeal thanks. I've hopefully adopted the sentiment here.

Can I get any +1s on the proposed wording in https://gist.github.com/srl295/e5b502d5eb015c0b093a ? I put the target date as Sept 23rd (3 weeks).

[yorkie]

BTW, could you guys remove these groups from the Node.js, and create another org like Node.js-i18n? Sometimes I just wanna track something more technical repo from this org Node.js, but I have to ignore those language groups by my eyes.

[srl295]

@yorkie could be, not sure what the pros and cons are. But there are other "non-technical" repos also, could you just track this one (nodejs/node)?

[yorkie]

@srl295 It's fine to manually manage list what I have wanna watched on, just think that's the best one if language repos doesn't exist here for me :)

[srl295]

@mikeal any comments on the gist above? Timing? (maybe +3 weeks from when the notice goes out)?

[srl295]

CC: @nodejs/collaboration

[mikeal]

@srl295 +1