This repository has been archived by the owner on Jan 20, 2022. It is now read-only.
Node.js Internationalization Proposal #18
Comments
|
Go ahead. We haven't worked on this for a very long time. Thew new initiative can definitely bring new life to this group. |
|
Yep, go ahead with the proposal 👍 |
|
I agree too. The proposal is interesting, I hope, like |
|
@mcollina @piccoloaiutante @parro-it hooray! Thankful for the positive feedback! We truly hope to see momentum grow in your group too. Can't wait to talk more soon. 🙌 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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!
The text was updated successfully, but these errors were encountered: