Skip to content
This repository has been archived by the owner on Jan 11, 2022. It is now read-only.

Archiving nodejs-pt (node's i18n process has changed) #83

Open
obensource opened this issue Jan 10, 2022 · 2 comments
Open

Archiving nodejs-pt (node's i18n process has changed) #83

obensource opened this issue Jan 10, 2022 · 2 comments

Comments

@obensource
Copy link
Member

Dear nodejs-pt team,

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

The i18n Working Group is currently in the process of archiving node's l10n repositories since we've moved all translation efforts to the Crowdin platform over the past few years. We're planning on archiving all l10n repositories that follow the previous method that was established during the io.js fork on 01-14-22. I believe this repository meets that criteria, but if there is a reason to continue to maintain nodejs/nodejs-pt other than localizing Node.js into Portuguese (and you'd like to keep this repository open), please respond here on this issue so we can discuss it and understand how to best help you in your efforts.

In the meantime, 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)

@gustavohenke
Copy link
Contributor

Hello @obensource! I think we're done over here, there has been zero activity for the last couple of years.
Thanks for looking after the official procedures!

@obensource
Copy link
Member Author

Hey @gustavohenke 👋

Thanks a million for letting me know, I really appreciate it – and thank you for all your great work! 🙏

Cheers! 🍻
–Ben

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants