On 30 January 2017 at 19:03, Brett Cannon firstname.lastname@example.org wrote:
On Mon, 30 Jan 2017 at 07:16 Berker Peksağ email@example.com wrote:
+1 for b) or any idea that would indicate that the Python developers don't maintain translations of the official documentation. I don't have a strong opinion on naming the GitHub organization (maybe python-docs-translations?) but that can be discussed later. Another advantage of this approach is that you can have separate issue trackers for each language (e.g. python-docs-fr) so people can easily report documentation issues in their native languages.
Does hosting on Read the Docs makes any of this easier/harder?
RTD models translations as separate projects, so it should make it easier: http://docs.readthedocs.io/en/latest/localization.html#project-with-multiple...
Most importantly, because they're separate projects, each translation will get to set its own project home page and source control repo reference.
It will still be up to translation authors to make some of the manual changes that Terry mentions to point people to the right issue trackers, but it shouldn't be any worse than what we see with occasionally redirecting people to the Python Packaging Authority issue trackers for various purposes.