I would like to become a member
Closed this issue · 30 comments
@zeke @obensource @RichardLitt Is this still a thing? What should @lxmarinkovic do?
I'm unsure. Haven't been active in a while, and I should probably resign from the board as being inactive in general, unfortunately.
I'm unsure. Haven't been active in a while, and I should probably resign from the board as being inactive in general, unfortunately.
I'll remove you as a maintainer but leave you as a member unless you indicate otherwise.
Sadly, I have to say the same. I haven't been active in this space for a while and it's a disservice to the community for me to pretend otherwise.
I'll remove you as a maintainer but leave you as a member unless.
This actually sounds good to me. Thanks, @Trott.
@obensource @bnb Any chance you can provide guidance here?
@nodejs/i18n What should happen here? Is i18n group still a thing? Is CrowdIn still being used? Or should @lxmarinkovic open pull requests for translations directly against the nodejs.org repo?
Hey there 👋 I'm also interested in contributing to the i18n team in general. From this thread it feels like the i18n team is not receiving currently much help, is this correct?
I also saw that the Crowdin integration is broken, and I'd like to help there if possible 👀 (Also with the Website Working Group).
I'd love to chat, @ovflowd:gnome.org on Matrix :)
@nodejs/tsc If the larger i18n coordination effort is to be revived, it will need a commitment from leadership, I think. Hopefully someone (@RichardLitt @bnb @obensource @zeke) can confirm or correct this summary but my impression is that:
- The larger i18n effort was a CommComm thing. So it doesn't have a home anymore.
- None of the people who used to lead it are involved in it anymore.
- It's basically broken and in stasis.
- It's different/separate from the general website localization efforts in that....here's where I don't actually know. I think the idea was to use Crowdin to make it easier for more people to do translations than our current open-a-pull-request-in-the-nodejs.org-repo method. It may have also had the intention of localization for the API docs but that never came to fruition as far as I know.
I think winding it down and telling people to continue submitting PRs to the website repository is a valid option, and a better option if we're not prepared to put real time and potentially resources (via the foundation, I suppose) into a larger effort. Almost everything that has ever happened with localization happened with individuals submitting PRs to the website repo. I'm not sure that this initiative ever bore much fruit (which is fine--lots of things get tried and don't work out). Again, I could be wrong, and maybe one of the folks who was involved in it can comment and add some context or info I don't have.
I think your summary comment is almost right. The problem here is that all the folks that have access to Crowdin are out of contact and I cannot promote things to integrate. I feel using Crowdin UI makes translations easier and we should have a lot of translated texts, so integrating into it would be great. Maybe we could focus on API docs for now and continue the current style for the website (submitting PRs to the repo). Or at least I'd like to move the texts on Crowdin to somewhere.
Maybe we could focus on API docs for now
How/where do we published localized API docs? Or is making the translations widely available part of the problem that a larger initiative would solve?
How/where do we published localized API docs? Or is making the translations widely available part of the problem that a larger initiative would solve?
There is currently an integration (it's broken for the reason @JohnTitor mentioned) between this repository and Crowdin. The Crowdin via bot create PR keep the translated documents synchronized.
Part of the problem we need to solve is making the contents of this repository available to Node.org.
Part of this discussion can be seen #328 and #315
confirm or correct this summary
@Trott alas, your summary is correct from my point of view. I can only speak for myself but, I haven't been able to make time in the last couple years to commit to Node.js i18n effort.
Note.: My comment stands as I would definitely love to contribute to Internationalisation efforts. I'm also going to contribute to the new node.js website starting with this issue.
I do have open source maintaining experience, and would love to chat on Matrix or any other platform. Sorry for chiming in 😅 🙇
I don't think anybody in the TSC has any availability to restart the i18n and new website projects :(. Managing this kind of initiative is a long-term effort, and we did not do a good job keeping them active.
I'll take look at the CrowdIn instance to see if that's at least something we'd like to keep going. We should identify any text anywhere that suggests a larger and more robust initiative and adjust it to the scale of what we're actually doing.
Hi @Trott , I put a little effort into Crowdin almost half a year ago to see if it is operational before I invest more time in it.
All that I can see now (after more than five months) is that I have "suggested 12 translations into Serbian (Latin)" without any comments or reviews, really no action at all
@mcollina regarding the new website initiative, if we have strong active contributors, is this something we could maybe work on?
I’m on the website redesign slack channel and would love to talk some alternatives and ideas there. Maybe I can be of use here :)
I'm not familiar with the website redesign - minus that it stalled.
There certainly seems to be lots of CrowdIn activity and it would be a shame to lose all that work. https://crowdin.com/project/nodejs/activity-stream
Let's see if we can at least fix the integration so this repository can get updated and at least the translated docs will be available.
@obensource The CrowdIn interface says you're a manager. Can you log in and make me a manager so I can try to get things going/working again?
@obensource It'd be great if you could also add me, my account is https://crowdin.com/profile/huyuumi.
Semi-related: how are https://crowdin.com/profile/nodejs-crowdin 's credentials managed? If it's currently shared only within some i18n WG members, it probably should be placed under the control of TSC (or another team? I'm not sure).
Semi-related: how are https://crowdin.com/profile/nodejs-crowdin 's credentials managed? If it's currently shared only within some i18n WG members, it probably should be placed under the control of TSC (or another team? I'm not sure).
I'm guessing it's not exactly the same as the Node.js Crowdin bot's credentials, but just in case: @nodejs/build Is this something Build WG knows anything about?
Semi-related: how are https://crowdin.com/profile/nodejs-crowdin 's credentials managed? If it's currently shared only within some i18n WG members, it probably should be placed under the control of TSC (or another team? I'm not sure).
I'm guessing it's not exactly the same as the Node.js Crowdin bot's credentials, but just in case: @nodejs/build Is this something Build WG knows anything about?
Not to my knowledge.
For the record, I'm still interested in contributing with i18n, including helping run the team.
I'm primarily curious regarding the node/i18n package as we might want to (still) use that for the translations and the docs for the https://github.com/nodejs/nodejs.dev website.
cc @Trott
Off-topic: Oh hey, @JohnTitor, fellow GNOME Foundation here 👀
Update: I briefly exchanged private messages with @obensource and expect to get the CrowdIn stuff working again soon (as in days, not weeks--famous last words and all that). Nothing more to report at this moment, though.
This repo/group is mostly inactive but there's lots of i18n activity going on at https://crowdin.com/project/nodejs. So if you haven't joined there, consider it!