Skip to content
This repository was archived by the owner on Mar 22, 2023. It is now read-only.
This repository was archived by the owner on Mar 22, 2023. It is now read-only.

Archiving nodejs-ko (node's i18n process has changed) #1198

@obensource

Description

@obensource

Dear nodejs-ko 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-ko other than localizing Node.js into Korean (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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions