Request for adding repository admin permisson

[corona10]

Hi @flowdas,

Thank you so much for all your contributions to the Korean translation of the Python documentation.

Recently, there has been some discussion about the outdated state of the Korean translation repository. The Python core team and the PSF are exploring ways to ensure the long-term sustainability and maintainability of translation efforts.

Given your current absence, I’d like to kindly request admin access for myself (@corona10) as the Korean core developer and @darjeeling as the Korean PSF director so that we can move the translation work forward for any other unexpected situations. If you’d like to discuss this further, please let me know :)

We also plan to involve non-Korean PSF members or core team members in the near future to help foster collaboration with other language translation teams.

For reference:

• PEP 545 -- (Miscellaneous Updates) Python Documentation Translations steering-council#284
• https://discuss.python.org/t/addressing-outdated-korean-python-docs-proposal-for-maintainership-and-community-driven-updates/88163

[corona10]

cc @willingc @ewdurbin

[ewdurbin]

@corona10 and @darjeeling added as collaborators with Maintain privileges on the repo.

[flowdas]

I apologize for the inactivity.
Coincidentally, I resumed working on the 3.13 branch a few days ago.
I've been sharing my progress on https://www.flowdas.com/posts/2025/04/python-docs-ko-reboot/.
I'm a little embarrassed.

[corona10]

Hi @flowdas,

There's no need to feel embarrassed—this kind of situation has happened in other language communities as well. I’d like to suggest the following actions moving forward:

• Please join the Official Python Documentation Discord channel and discuss the future direction with the Python Korea User Group admins.
  (Let me know the email address you're using so we can coordinate.)

• Consider moving the translation tools to the main branch of the python-docs-ko repository.
  This will make it easier for the community to contribute and collaborate on tooling issues.
  You can also connect with other language teams on Discord if you run into any problems.

• Please clarify the relationship between https://python.flowdas.com/ and https://docs.python.org.
  I’m concerned about the following points:

  • Currently, it appears that https://python.flowdas.com/ (Commentary version) acts as the upstream, while https://docs.python.org/ is treated as downstream. This should not be the case since you are managing the official Korean translation.
  • The identical UI design may lead people to believe your site is an official Python documentation site, which can be misleading.
  • The statement “Korean translation Copyright © 2017–2021, Flowdas & Translator. All rights reserved” is also concerning.
    Translation output for Python documentation is not personal intellectual property.

Thank you for your attention to these matters.

cc @darjeeling @willingc @hugovk

[corona10]

[darjeeling]

Background Discussion

The recent proposal to update PEP 545 highlights the necessity of establishing and enhancing governance structures to ensure the long-term sustainability of Python documentation translations. This is not an issue confined to the Korean translation; it affects all language translations within the Python community. 

Key points from the discussion include:
• Maintaining Translation Quality: Translations should aim to match the quality of the original English documentation. Unreviewed machine translations are discouraged to prevent degradation of documentation standards. 
• Managing Inactive Translations: If a translation coordinator is inactive for over a year and does not respond within two weeks to a check-in issue, they may be marked as inactive. This allows others to take over and continue the translation efforts, ensuring that documentation remains up-to-date. 
• Attracting New Translators: Improving visibility and accessibility for potential contributors is crucial. Proposed measures include adding a “Help Translating” link in the documentation footer and updating the developer guide to include translation contribution guidelines.  

Implementing these governance enhancements will help maintain the quality and relevance of Python documentation across all languages, fostering a more inclusive and collaborative community.

[flowdas]

Hi, @corona10

Consider moving the translation tools to the main branch of the python-docs-ko repository.
This will make it easier for the community to contribute and collaborate on tooling issues.

Changing to the main branch breaks the current Dev Container strategy.
Could you explain the benefits of changing from the 3.13 branch to the master branch?

Please clarify the relationship between https://python.flowdas.com/ and https://docs.python.org.

It's my personal (extended) project.
I modified cpython/Doc to include example code translations and translators's comments.

Currently, it appears that https://python.flowdas.com/ (Commentary version) acts as the upstream, while https://docs.python.org/ is treated as downstream. This should not be the case since you are managing the official Korean translation.

No.
python.flowdas.com acts as the downstream.
Technically, it's a derivative work of cpython/Doc not python-docs-ko.

The identical UI design may lead people to believe your site is an official Python documentation site, which can be misleading.

Sadly, due to my laziness, I didn't change the style.
However, I've re-titled and described it so that it's not confused with the official site.

The statement “Korean translation Copyright © 2017–2021, Flowdas & Translator. All rights reserved” is also concerning.
Translation output for Python documentation is not personal intellectual property.

I'll fix it.

Thank you.

[corona10]

@flowdas

Thank you for the clarification.

Changing to the main branch breaks the current Dev Container strategy.

As far as I can see, the current master branch of this repository — and of flowdas/python-docs-ko — doesn’t include a Dev Container setup. Are you referring to a future plan?

If so, would you be open to discussing it with the community in a public space? The Discord server could be a good starting point. If that sounds good to you, could you share your email address so I can send you an invitation?

[corona10]

And I hope that every translation infra will be managed at the Python public repo rather than the personal repo for healthy and sustainable translation in the future.

[flowdas]

@corona10

As far as I can see, the current master branch of this repository — and of [flowdas/python-docs-ko]
(https://github.com/flowdas/python-docs-ko) — doesn’t include a Dev Container setup. Are you referring to a future plan?

I'm working on moving flowdas/python-docs-ko into python/python-docs-ko and adding Dev Container support.
Some of the work is already in the 3.13 branch of python/python-docs-ko.

Coincidentally, I resumed working on the 3.13 branch a few days ago.
I've been sharing my progress on https://www.flowdas.com/posts/2025/04/python-docs-ko-reboot/.

Please check it out.

[corona10]

@flowdas Would you like to check mailbox that @darjeeling sent to you?

[corona10]

Since we got permission to do this repo, I am now closing the issue.
I hope that the rest of the things can be handled by @flowdas and @darjeeling.

Thank you for the cooperation.