i18n tracking spreadsheet

[snostorm]

Posting this to not lose this list. A good resource we should find an official spot for. Via #246

@kosamari commented 13 days ago

Here is a google doc I just put together (data collected at 2/28 10:00 PM EST).
I just visited each repo and glance at master, PR, and issues. I may very well missed something because of language, and I would not know any separate org/repo (like iojs-ja team does)

• There are many teams that are still "inactive" (meaning no translation has been made. Also, this does not mean they will not get to it in the future.)
• Some are just focused on translating io.js Weekly, some are just doing website, some cover api doc.

So for now, removing articles that only contains English and later receive PR sounds good option to me.

Also, if we plan to internationalize everything (including api doc), once #136 has been resolved, Website WG should send message to all i18n team regarding what is preferred place to put translations.

i.e : Japanese team has started separate github org (https://github.com/iojs-jp) and has been translating doc and roadmap there.
This is result of strong user group history, Node.js UG in Japan already had alot of japanese docs under http://nodejs.jp/ (Because nodejs.org was not designed/accepting contribution for i18n). To those active in Node.js and now io.js user group in Japan, having contents under own domain iojs.jp is natural progression. But now that io.js has i18n effort going, it does rise a question whether it should be under i18n ver. of iojs.org

[mikeal]

But now that io.js has i18n effort going, it does rise a question whether it should be under i18n ver. of iojs.org

Every i18n community is autonomous. They should host wherever they think is most appropriate and we should link/integrate wherever possible. It's worth noting that more than just the io.js website is translated under that domain.

Because the website is templatized hosting externally is a little trickier, maybe it should be mirrored? What can we do to help enable this.

[blakmatrix]

@snostorm @mikeal @kosamari I tried doing a few things about this with nodejs/node#1113 also that's up to date as of my last commit... I was unable to update the aforementioned spreadsheet to add the few changes that are listed on that spreadsheet as inactive.

It's quite hard work to go around and find all these links especially since as @kosamari mentioned there are various languages and that is definitely a barrier... what I found myself doing ended up being quite structured though:

• scrape the readmes raw looking for markdown links, looked for chat, weekly emails, and social accounts like twitter and facebook.
• look at medium and see if they exist, and if they were somewhat active, doing google translate.
• look at twitter to see if some people created accounts for the language but have not yet commented on them in their repos.
• for things that I didn't find much info on I did a quick google search to see i anything existed for them and if they seemed active and not just created once

@mikeal I feel like this is something we should solve as iojs evangelists as I think it falls directly into our domain for getting the word out about the different WGs with the addition of autonomy for each i18n group, as those groups, I presume, are more interested in translations vs. gathering other translators for their cause ... eventually I would hope that there would be some evangelists within the different translation groups to help keep things up to date. It is just at this early stage all the i18n WGs are just getting moving, I think it would be incorrect to think they should pick up the evangelism banner before achieving thier goals.

@julianduque , you help out with iojs-es and are a WG evangelist member, what are your thoughts on this?

[snostorm]

FYI I just reposted @kosamari's full original thread.

But now that io.js has i18n effort going, it does rise a question whether it should be under i18n ver. of iojs.org

Every i18n community is autonomous. They should host wherever they think is most appropriate and we should link/integrate wherever possible. It's worth noting that more than just the io.js website is translated under that domain.

I would say it is the website team's goal to try and meeting publishing needs of as many i18n groups as possible so they don't need to worry about hosting stuff and content stays within the "safety net" of our known SSL. Due to the autonomous nature of i18n WGs we'd never force this of course, but we should all be working together to make sure the tooling in place does try and fill these groups' needs and helps avoid duplicating efforts.

Because the website is templatized hosting externally is a little trickier, maybe it should be mirrored? What can we do to help enable this.

Not necessarily. The published outcome is 100% static assets which are even bundled in source control (for now.) The tricky thing are secondary resources like API docs, download links, etc.