Moving docs translations into separate repository

[greyli]

The documentation of FastAPI is brilliant, but IMO mix all the translations in one repository is not a good idea.

It's very user-friendly to have so many translations support. However, when the community grows there will be more people who want to help translate the docs into their language, which means dozens of PRs per language will be created. Besides, when there is one minor change in the English version of the documentation, there will be ten or more PRs for the update of translations. I would recommend moving the translations into a separate repository.

Currently, the PR list (and commit history) is a bit occupied by translations (120/190), it may inconvenience people who want to contribute to the code (similarly, the issue tracker is occupied by questions #2228).

[old-syniex]

@tiangolo what are your thoughts about the suggestion?

[tiangolo]

Yep, but moving it somewhere else would mean even more work for me in another place, so I can't do that. And I do want people to notice and help with translations.

Also, I consider docs and translations very important, and I think people contributing them deserve to be "contributors to FastAPI" and have their commits there.

So, for now, I'll pass on this suggestion, but thanks for the interest! ☕

[github-actions[bot]]

Assuming the original need was handled, this will be automatically closed now. But feel free to add more comments or create new issues or PRs.

[dolfinus]

Currently most of PRs (379+ of 676 at the moment of creating this message) are documentation translations. This is really hard to navigate in PRs and find ones related to framework features or bugs:

What do you think about solutions below:

1. Move documentation and/or translations to separated repository. Yes, this may cause the source code and documentation to diverge, but maybe there are ways to keep these changes in sync.
2. Add more maintainers to handle translations PRs specifically, to merge such PRs as soon as possible. Only one maintainer for such a large and important project is really a bus factor.
3. Use third-party services for documentation translations, e.g. https://poeditor.com/kb/open-source-localization. Personally, I've never used such services, but this can probably solve issues like Management of multilingual translations #10872