Localization

[ghost]

just like the old iojs website was, shouldn't this website be (eventually) localized? forgive me if I missed something really obvious here, just thought I'd bring it up

[fhemberger]

That was the plan, yes. We wanted to wait until the English version was complete, which is the case now.

[bnb]

+1. We need to start rolling out information about localization and how to handle it. @mikeal You were the key player in setting up the io.js localization - do you have any input on how we should start from here?

[mikeal]

We need documentation on where to start localizing, how to build, etc. We can pull inspiration from the io.js site.

[mikeal]

Oh, and those docs should land in the README.

[ghost]

Opened a PR for adding localization instructions/config: #242

[fhemberger]

#242 is merged. Can we close this now or do you want to keep this issue for further discussion/planning?

[ghost]

Ideally, every translation WG should open an issue now, right? How about we ping them?

[bnb]

@sup A collaborator can ping all their teams in the org. @fhemberger You have my +1. Do we need more +1s for this? If not, feel free to do it - I can do it if you'd like, too.

[fhemberger]

I wrote a little script to add all localization team members from "nodejs/iojs-*" to the new team "nodejs/localization". It's way easier to mention everybody now.

[fhemberger]

@mikeal I also wrote a little script to rename the iojs-* teams to nodejs-*. I can't run it myself, as I'm not organization administrator: https://gist.github.com/fhemberger/bea66aedbdba7a441ea4
Maybe this helps.

[sotayamashita]

@fhemberger Its issue is too old so I think it should be closed.