This repository was archived by the owner on Nov 21, 2018. It is now read-only.
Remove/flag stale i18n articles #246
Description
Current State
As far as I can tell (I just performed a quick audit based on a lazy search of a few phrases), the following folders in the content directory have not yet been forked from English:
- @iojs/iojs-cs
- @iojs/iojs-da (pending PR Adds Danish translation of website #153 )
- @iojs/iojs-hi
- @iojs/iojs-hu
- @iojs/iojs-ka
- @iojs/iojs-mk
- @iojs/iojs-nl
- @iojs/iojs-pl
- @iojs/iojs-sv
Previously mentioned
- @iojs/iojs-ru (approved in PR Update site pages for ru lang #248)
- @iojs/iojs-no (since merged)
My apologies if any were incorrectly tagged! Also, the list above is in no way an indication of any translation work that may still be in progress on those groups behind the scenes :)
I propose we do one of two things:
- Delete folders AND articles that only contain English copies, letting the i18n groups add them back in (via PR) when the work is ready
- Somehow flag placeholder articles/directories as such behind the scenes
Why?
- With the upcoming work to promote languages which are available (in addition to English) on the io.js website, I don't want a bunch of duplicate pages getting picked up by Google.
- Likewise, I don't want somebody who speaks Esperanto to see the translation links, click one, then be disappointed/confused that the page is still in English.
- Once we are aware of the actual documents that are translated we can properly cross-link them on a site-wide and per-article level.
- As we keep adding new articles, guides, update posts (say for TC/WG meetings), etc. the list of articles will keep growing. It seems silly to keep adding/maintaining duplicates of every upcoming page across all of the languages. I'd rather translation work be opt-in by each group.
Thoughts?
Activity
snostorm commentedon Feb 27, 2015
Side note: I remember we also talked about organizing the content directories to possibly live in the individual group repos and utilizing git subtrees to bring them in once ready for a PR in the main repo.
Second thought: Instead of deleting the folder, deleting all of the
.mdfiles inside should be enough for auto-detection magic on my end.Starefossen commentedon Feb 27, 2015
@iojs/iojs-no is awaiting a decision regarding #136. If git subtrees are a no go we'll create a PR to this repo.
Olegas commentedon Feb 27, 2015
nodejs/nodejs-ru#73 WIP
snostorm commentedon Feb 27, 2015
@Starefossen @Olegas thanks for pointing out the blockers/progress.
This post is mostly just aimed at getting agreement for removing not yet translated Markdown files from the individual language directories in the master branch here UNTIL they are ready. When they are translated, they return.
AntouanK commentedon Feb 27, 2015
👍 from me to keep out untranslated pages until they are done.
AdriVanHoudt commentedon Feb 27, 2015
You could also add a 'catch page' to see how many people click on a particular language and so you can let the wg know their translation is needed
snostorm commentedon Feb 27, 2015
@AdriVanHoudt ya, tracking stats for each would be helpful, good suggestion.
As of today ... we don't have any non-English language destined links, partially because of this issue (although I'm just reporting it now since it is on my radar.)
bnb commentedon Feb 27, 2015
Opt-in translation sounds like the best strategy to me.
I just looked at the members for each of the teams, and noticed @iojs/iojs-sv literally has 0 members. This is really not ideal. There are also @iojs/iojs-cs and @iojs/iojs-mk, which just have 1 contributor. I think we need to have some sort of minimum number of contributors in place, as I feel it's ridiculous to think one person is going to be able to maintain the entire translation.
I suggest the minimum number be 3-5 contributors before a repository is created or commit access is given. This will ensure enough of a fallback to where the brunt of the translation will be distributed over multiple people, allowing for some faults.
This suggestion isn't reflective of the members of cs and mk, or anybody else that wants to take on a whole translation themselves - it's simply a reflection on the condition of being a person. It's unreasonable to expect one person to do everything at the level of commitment the translations need. People have lives, commitments, distractions, etc. It's not fair to the potential readers of a one-manned localization of the site to be in a position where they're reading a stale localization. That will reflect really poorly on io.js for those potential readers.
I'm pretty sure just about every person who is helping with io.js in any way can attest to the disappointment and frustration that goes with un-updated, unmaintained content. That shouldn't be something we permit on the io.js website.
For #246, removes untranslated i18n article copies
snostorm commentedon Feb 27, 2015
FYI there's now a PR #247 which covers this change if approved
Olegas commentedon Feb 27, 2015
#248 for ru update
kosamari commentedon Mar 1, 2015
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)
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
gustavohenke commentedon Mar 1, 2015
@kosamari, at @iojs/iojs-pt, we translated the website (see #150 and #176), we have open issues for translating the roadmap slides (nodejs/nodejs-pt#28 and nodejs/nodejs-pt#29), and we have a gitter chat at https://gitter.im/iojs/iojs-pt.
kosamari commentedon Mar 1, 2015
@gustavohenke thanks! updated.
Olegas commentedon Mar 1, 2015
@kosamari Please fix, line 30 is iojs-ru, line 31 is iojs-ro
kosamari commentedon Mar 1, 2015
@Olegas fixed
snostorm commentedon Mar 1, 2015
Thanks @kosamari! I don't have time to read through that all now but it looks like a great resource you've put together
stringparser commentedon Mar 2, 2015
@kosamari iojs-es, is missing gitter
edit: https://gitter.im/iojs/iojs-es :)
therebelrobot commentedon Mar 2, 2015
On the agenda for Mar 2nd Website WG meeting #240
For #246, removes non-translated cs,da,hi,hu,ka,mk,nl,pl,sv articles …
For #246, removes public articles
Merge pull request #247 from iojs/246_removes_empty_i18n_articles
snostorm commentedon Mar 4, 2015
The PR has been closed on this. Might keep the ticket open for a bit so we don't lose track of @kosamari's progress on tracking groups.
snostorm commentedon Mar 13, 2015
Moving @kosamari article to a new issue, closing this one. Thanks everyone!