You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 20, 2022. It is now read-only.
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:
Thank you @yasinaydin! Happy to hear your positive feedback! 🙌
Currently we're in the consensus seeking phase of this proposal, and if the feedback is good from all the l10n groups by the 15th–then we'll be good to go to start setting up our i18n repo and your Crowdin project. Excited to be in touch about it, and feel free to reach out to me or anyone in the i18n working group if you have any questions!
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: