https://medium.com/node-js-javascript/io-js-week-of-february-6th-2015-e185388549a4

Starting now, unless @yoshuawuyts is already doing it.

Dear nodejs-nl team,

Thank you for being part of the Node.js community. 🙏

This repository doesn't seem to have been very active recently, and so it is scheduled to be archived on 01-14-22.

Meanwhile, we'd love to have you come over and be a part of the i18n WG at: https://github.com/nodejs/i18n#contributing

Please feel free to reach out to us there, or to me directly if you'd like to understand how to get involved with node's current localization efforts.

All the best,
–Ben (Node.js i18n Lead)

should be easy enough.

https://medium.com/node-js-javascript/io-js-week-of-february-13th-2015-7846b94074a2

Any takers? I can probably get around to it on Sunday.

I saw that io.js_cn translated the changelog which doesn't seem like a bad idea. But for their, and our own sanity, they translated only from 1.0.0 up.

https://github.com/iojs/iojs-cn/blob/master/CHANGELOG.md

original: https://github.com/iojs/io.js/blob/v1.x/CHANGELOG.md

Dear members of the io.js Dutch WG iojs-nl

It is proposed to rename this repo to:

nodejs/nodejs-nl

As part of the io.js and node.js convergence, node.js releases are now based on the codebase and user base of the converged node.js and io.js communities. A number of the resources and repositories have already been renamed.
In the absence of objections or other discussion, this rename will occur on or after Oct 28, 2015

However, active language working groups should take ownership of this issue and discuss/dispose of it according to their own processes.

For more information or to discuss the overall issue, please see and comment on nodejs/node#2525

This statement was authorized by the Node.js TSC

Cc: @nodejs/iojs-nl

We are going through all of the node.js repositories to rename the primary branch to main. Please see nodejs/node#33864 for more context.

I don't think there should be any issues for the contributors to this repo. I'd like to do the remain this Friday May 22nd unless there are any concerns.

Please let me know in this issue before May 22nd if there are any concerns, otherwise I'll go ahead and do the change.

Hi,

I just wanted to start a discussion on how we will do things. This includes where to write the translations, what to translate, ...
Just so we can have a standard unified way of working.

Personal thoughts:

• I think posting to medium is good, other io.js members also use it and it just a good blogging tool in general
• I think every post that written by io.js or it's core members and shared via their twitter should be considered to be translated
• For collaboration we could use gists or maybe a markdown file per post in this repo for easy collab

Let me know what you think @timdp @yoshuawuyts

EDIT

Decided

• Every blog post has it's own translation file
• Every blog post is translated in Markdown style
• Every translated blog post is posted to Medium
• Prefix all blog posts files with a date
• Tag each issue/PR with either post i18n or general i18n if it is about translating a post/changelog/...

To be decided

• What date to prefix with (posted/translated)
• 1 branch per post
• Add reference to original post/article/changelog to each translated document
• Who posts to medium and at what time

Hi there!

On behalf of the Node.js Community Committee, I’d like to thank you for your group’s contributions to this awesome project! 👏👏👏

I’m reaching out as a member of our new Internationalization Working Group, and we’d like to get in touch with you about our proposal around Internationalization for Node.js!

Our proposed changes would modify the structure of the working model that your group, and all Node.js Localization groups currently observe. The primary difference being that we’d like to introduce a new translation platform to streamline the translation process and setup automated integration of localization into the Node.js project.

If you haven’t seen it already, we’d greatly appreciate if you could please take a moment to review our new proposal and comment in this issue to let us know if you have any thoughts, questions, or objections to it.

We’d love to hear from you by February 14th, during our consensus seeking period for this proposal. If we’re not able to hear from you in that time, we’ll consider that your opinion of the effort is positive, and press on with it.

Moving ahead, the i18n Working Group is so thrilled to stay in touch with you and make the translation of Node.js’ content into your language a success!

We’re excited to be in touch again soon, and thank you for working with us!

https://github.com/iojs/website/tree/master/content/nl is beckoning seductively. Any takers?

Anyone up for translating? If there are no takers I'll give it a go. https://medium.com/@iojs/io-js-and-a-node-js-foundation-4e14699fb7be

Welcome, new localizations team :)

To get this team up and running you have a few initial tasks to accomplish:

• Create a README.md for this repository, it should include:
  • A "call to action" pointing to the Issue tracker for new translators to find tasks.
  • A list of the team members.
  • Instructions on how to log an issue to be added to this team.
• Set the repository description. This should not be in English, it should be in the language for this community :)
• Social Media
  • Create a twitter account for this language. Share the password privately with the team.
  • Create accounts on other social media popular in this language. Share the passwords private with the rest of the team.
  • Make sure you use these accounts not just to promote newly translated material but also to attract people in your community to help with translation tasks.
• Optional: If you plan to do a Google hangout w/ your localization team have @mikeal add you to the Google+ account so that it can post to the iojs YouTube channel. Once you are added there is documentation on how to setup a hangout-on-air.
• Finally, create a new Issue to translate and publish the latest io.js post. Once translated you should post it wherever you think it will get the most visibility to the community speaking you language, you don't have to post it to Medium unless you think that it is best.

nodejs/roadmap#18