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

[srl295]

3-week timeline OK'ed by TSC in meeting #3126 , so I will start sending these out.

[srl295]

Proposed mapping

• iojs-ar → nodejs-ar Arabic
  • notify
• iojs-bg → nodejs-bg Bulgarian
  • notify
• iojs-bn → nodejs-bn Bengali
  • notify
• iojs-cn → nodejs-zh-CN Chinese (China)
  • notify
• iojs-cs → nodejs-cs Czech
  • notify
• iojs-da → nodejs-da Danish
  • notify
• iojs-de → nodejs-de German
  • notify
• iojs-el → nodejs-el Greek
  • notify
• iojs-es → nodejs-es Spanish
  • notify
• iojs-fa → nodejs-fa Persian
  • notify
• iojs-fi → nodejs-fi Finnish
  • notify
• iojs-fr → nodejs-fr French
  • notify
• iojs-he → nodejs-he Hebrew
  • notify
• iojs-hi → nodejs-hi Hindi
  • notify
• iojs-hu → nodejs-hu Hungarian
  • notify
• iojs-id → nodejs-id Indonesian
  • notify
• iojs-it → nodejs-it Italian
  • notify
• iojs-ja → nodejs-ja Japanese
  • notify
• iojs-ka → nodejs-ka Georgian
  • notify
• iojs-ko → nodejs-ko Korean
  • notify
• iojs-mk → nodejs-mk Macedonian
  • notify
• iojs-ms → nodejs-ms Malay
  • notify
• iojs-nl → nodejs-nl Dutch
  • notify
• iojs-no → nodejs-no Norwegian
  • notify
• iojs-pl → nodejs-pl Polish
  • notify
• iojs-ro → nodejs-ro Romanian
  • notify
• iojs-ru → nodejs-ru Russian
  • notify
• iojs-sv → nodejs-sv Swedish
  • notify
• iojs-sw → nodejs-sw Swahili
  • notify
• iojs-ta → nodejs-ta Tamil
  • notify
• iojs-tr → nodejs-tr Turkish
  • notify
• iojs-tw → nodejs-zh-TW Chinese (Taiwan)
  • notify
• iojs-uk → nodejs-uk Ukrainian
  • notify
• iojs-vi → nodejs-vi Vietnamese
  • notify

[srl295]

Note that iojs-{cn/tw} map here to nodejs-zh-{CN/TW} - their webpages explicitly state "io.js in China" and "Node.js Taiwan".

[srl295]

• Need to update WORKING_GROUPS.md
• Need to update other website/links

[yoannmoinet]

Should we keep/delete our twitter/medium?

cc @nodejs/iojs-fr

[srl295]

FYI: note discussions in the cn and tw groups.

[srl295]

@yoannmoinet asked

should we keep twitter/medium?

probably a question for @nodejs/evangelism ?

[outsideris]

@srl295 We changed iojs-ko to nodejs-ko. Thanks.

[srl295]

OK… time is up. @nodejs/tsc @mikeal I actually don't have permissions (anymore?) to do this change. Please do this: ( Keys: NR=no response, +1= plus one'ed )

• iojs-ar → nodejs-ar Arabic - NR
• iojs-bg → nodejs-bg Bulgarian - +1
• iojs-bn → nodejs-bn Bengali - NR
• iojs-cs → nodejs-cs Czech - NR
• iojs-da → nodejs-da Danish - NR
• iojs-el → nodejs-el Greek - +1
• iojs-es → nodejs-es Spanish - +1
• iojs-he → nodejs-he Hebrew +1
• iojs-hi → nodejs-hi Hindi +1
• iojs-hu → nodejs-hu Hungarian +1
• iojs-it → nodejs-it Italian +1
• iojs-ms → nodejs-ms Malay - NR
• iojs-ru → nodejs-ru Russian +1
• iojs-sv → nodejs-sv Swedish NR
• iojs-sw → nodejs-sw Swahili NR
• iojs-ta → nodejs-ta Tamil - NR-ish

[mikeal]

All moved :)

[srl295]

Thanks! I have some PR to open to fix the web and group links then I'll
close this. Thanks for your help on this.

[srl295]

• @mikeal can you also rename these teams to nodejs- ? Some are already done.

[mikeal]

i thought i got them all, which did i miss?

[srl295]

@mikeal see the link "teams" - it's a query.

[mikeal]

these weren't ones that i moved, these are all active and have renamed their own repos, i wonder if they are lacking team maintainers who can rename the group?

[srl295]

@mikeal I think that may be the case. Can we assume if they renamed (or had renamed) their repo that the team can follow? Again they are all renames to nodejs-* except for nodejs-zh-CN and nodejs-zh-TW

[mikeal]

probably, but i would also like them to assign a maintainer if they don't have one

[srl295]

@mikeal I closed all issues. There are 19 of these with wrong team names. Should I reopen these 19 issues and say- please assign a maintainer, rename team, and close this, and if you need help contact ???

[mikeal]

just comment in the closed issue that if they want a team maintainer they should ping me. i'll go ahead and move them now.

[mikeal]

all moved.

[srl295]

@mikeal thanks! I think i'm close to closing this issue. May need to check on website issues.

[cjihrig]

@srl295 can this be closed now?

[srl295]

yes, all done