From maciej.olko at gmail.com  Fri Apr  5 20:11:07 2019
From: maciej.olko at gmail.com (Maciek Olko)
Date: Sat, 6 Apr 2019 02:11:07 +0200
Subject: [Doc-SIG] Polish translation
Message-ID: <CALYYG81wcZ4SOZ1mHu_C2iSmemQf5ATjgFdKYPfMYaZuHDk5tg@mail.gmail.com>

Hello,
I'd like to request a designation to coordinator role for Polish
translation of Python documentation and a creation of GitHub repository for
it.

I am currently a Python developer at YouGov. I am coordinator of Django
documentation translation into Polish.

I am native Polish speaker, my English skills are about C2 CEFR [1].

In couple of days I'd like come up with a plan to efficiently encourage
people to join the translation project.

Regards,
Maciej Olko

[1]
https://en.wikipedia.org/wiki/Common_European_Framework_of_Reference_for_Languages
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20190406/08a6b622/attachment.html>

From julien at palard.fr  Sat Apr  6 13:02:59 2019
From: julien at palard.fr (Julien Palard)
Date: Sat, 06 Apr 2019 17:02:59 +0000
Subject: [Doc-SIG] Polish translation
In-Reply-To: <CALYYG81wcZ4SOZ1mHu_C2iSmemQf5ATjgFdKYPfMYaZuHDk5tg@mail.gmail.com>
References: <CALYYG81wcZ4SOZ1mHu_C2iSmemQf5ATjgFdKYPfMYaZuHDk5tg@mail.gmail.com>
Message-ID: <jVMfGau_U7NWNHcHx-RYGHPcaNqLym2JBYJaJDZhD6v_ZPCciBtrW50NRny6ZjKgARinxNpxpGocrcYb1TLegcZB0l5TT3wukUfPXZ_O0YE=@palard.fr>

Hi Maciek!

Nice to hear from Poland! You can already start translating using the transifex project: https://www.transifex.com/python-doc/python-newest/ that's where most of the translation looks to happen (except French which only happen on Github, we find it easier to review pull requests and comment on them than transifex).

You're the de-facto coordinator for this language, (there's no established process) so welcome on board :)

Feel free to start encouraging people to join (more efficient than trying to translate alone), I'll create you a repository on github.com/python/python-docs-pl as soon as it make sense ("enough" strings are translated), a few percent later we'll add you to the build so you can preview the doc on docs.python.org, and finally we'll follow the rules of PEP 545 about going public, being you'll need to have translated:

- 100% of bugs.html with proper links to the language repository issue tracker.
- 100% of tutorial.
- 100% of library/functions (builtins).

Bests,
--
Julien Palard
https://mdk.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20190406/cd1d08c0/attachment.html>

From maciej.olko at gmail.com  Sat Apr  6 19:30:16 2019
From: maciej.olko at gmail.com (Maciek Olko)
Date: Sun, 7 Apr 2019 01:30:16 +0200
Subject: [Doc-SIG] Polish translation
In-Reply-To: <jVMfGau_U7NWNHcHx-RYGHPcaNqLym2JBYJaJDZhD6v_ZPCciBtrW50NRny6ZjKgARinxNpxpGocrcYb1TLegcZB0l5TT3wukUfPXZ_O0YE=@palard.fr>
References: <CALYYG81wcZ4SOZ1mHu_C2iSmemQf5ATjgFdKYPfMYaZuHDk5tg@mail.gmail.com>
 <jVMfGau_U7NWNHcHx-RYGHPcaNqLym2JBYJaJDZhD6v_ZPCciBtrW50NRny6ZjKgARinxNpxpGocrcYb1TLegcZB0l5TT3wukUfPXZ_O0YE=@palard.fr>
Message-ID: <CALYYG83ii_WijyH08dQnoSfH2uhcCLXJTgwW4EjsZ350vBh0BA@mail.gmail.com>

Thank you for warm welcome!

I've already started translating. I was thinking that GitHub repo and
translation process described there would direct people to Transifex and
help to spread the word as being googlable.

Regards,
Maciej Olko

sob., 6 kwi 2019 o 19:03 Julien Palard <julien at palard.fr> napisa?(a):

> Hi Maciek!
>
> Nice to hear from Poland! You can already start translating using the
> transifex project: https://www.transifex.com/python-doc/python-newest/
> that's where most of the translation looks to happen (except French which
> only happen on Github, we find it easier to review pull requests and
> comment on them than transifex).
>
> You're the de-facto coordinator for this language, (there's no established
> process) so welcome on board :)
>
> Feel free to start encouraging people to join (more efficient than trying
> to translate alone), I'll create you a repository on
> github.com/python/python-docs-pl as soon as it make sense ("enough"
> strings are translated), a few percent later we'll add you to the build so
> you can preview the doc on docs.python.org, and finally we'll follow the
> rules of PEP 545 about going public, being you'll need to have translated:
>
>    - 100% of bugs.html with proper links to the language repository issue
>    tracker.
>    - 100% of tutorial.
>    - 100% of library/functions (builtins).
>
> Bests,
> --
> Julien Palard
> https://mdk.fr
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20190407/053ecd84/attachment.html>

From marco at rougeth.com  Sun Apr  7 09:28:41 2019
From: marco at rougeth.com (Marco Rougeth)
Date: Sun, 7 Apr 2019 13:28:41 +0000
Subject: [Doc-SIG] Updates on Transifex
Message-ID: <CAHKrs2P+hxziOFCs8E+1tp2hu5EsMnrQhcN6uZbB1TqTF1fUgg@mail.gmail.com>

Hey folks,

I'd like to know how Transifex is updated with new strings or changes from
the docs. I?m asking this because I noticed that the path of source of the
strings are different on .po files on Portuguese translation, e.g.

Portuguese *about.po* file:
#: ../../about.rst:15

French *about.po* file::
#: ../Doc/about.rst:15

I don?t know if this path is used or how it affects the translation but I
believe it should be the same, right?

I'm assuming that the *python-doc *project on Transifex is something
official or managed/maintained by the community.

Thanks,
Marco.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20190407/3dea8dad/attachment.html>

From songofacandy at gmail.com  Sun Apr  7 22:10:30 2019
From: songofacandy at gmail.com (Inada Naoki)
Date: Mon, 8 Apr 2019 11:10:30 +0900
Subject: [Doc-SIG] Updates on Transifex
In-Reply-To: <CAHKrs2P+hxziOFCs8E+1tp2hu5EsMnrQhcN6uZbB1TqTF1fUgg@mail.gmail.com>
References: <CAHKrs2P+hxziOFCs8E+1tp2hu5EsMnrQhcN6uZbB1TqTF1fUgg@mail.gmail.com>
Message-ID: <CAEfz+Ty+vN=-8UyMwgNTUg-C+zuEvn1w6vSy2nPe=2-hx1vWoA@mail.gmail.com>

On Sun, Apr 7, 2019 at 10:29 PM Marco Rougeth <marco at rougeth.com> wrote:
>
> I don?t know if this path is used or how it affects the translation but I believe it should be the same, right?
>

Yes, it's just a comment.  It helps translator want to know how the
message is used (context).
It doesn't affect to translate process.

I am not sure, but the comment is just copied from pot file.
Pot build process was changed at some point.

"../../about.rst" is current comment in about.pot file.

Maybe, French version `about.po` is not updated after the pot build
process change.

-- 
Inada Naoki  <songofacandy at gmail.com>

From marco at rougeth.com  Mon Apr  8 06:09:48 2019
From: marco at rougeth.com (Marco Rougeth)
Date: Mon, 8 Apr 2019 11:09:48 +0100
Subject: [Doc-SIG] Updates on Transifex
In-Reply-To: <CAEfz+Ty+vN=-8UyMwgNTUg-C+zuEvn1w6vSy2nPe=2-hx1vWoA@mail.gmail.com>
References: <CAHKrs2P+hxziOFCs8E+1tp2hu5EsMnrQhcN6uZbB1TqTF1fUgg@mail.gmail.com>
 <CAEfz+Ty+vN=-8UyMwgNTUg-C+zuEvn1w6vSy2nPe=2-hx1vWoA@mail.gmail.com>
Message-ID: <CAHKrs2NFmDGNJKQY18TFc4Eqt9F-PjpBdRe1+BnOCP5oOmqTwg@mail.gmail.com>

Thanks for clarifying Inad.

Em seg, 8 de abr de 2019 ?s 03:10, Inada Naoki <songofacandy at gmail.com>
escreveu:

> On Sun, Apr 7, 2019 at 10:29 PM Marco Rougeth <marco at rougeth.com> wrote:
> >
> > I don?t know if this path is used or how it affects the translation but
> I believe it should be the same, right?
> >
>
> Yes, it's just a comment.  It helps translator want to know how the
> message is used (context).
> It doesn't affect to translate process.
>
> I am not sure, but the comment is just copied from pot file.
> Pot build process was changed at some point.
>
> "../../about.rst" is current comment in about.pot file.
>
> Maybe, French version `about.po` is not updated after the pot build
> process change.
>
> --
> Inada Naoki  <songofacandy at gmail.com>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20190408/5f1a3caa/attachment.html>

From julien at palard.fr  Tue Apr  9 03:44:27 2019
From: julien at palard.fr (Julien Palard)
Date: Tue, 09 Apr 2019 07:44:27 +0000
Subject: [Doc-SIG] Updates on Transifex
In-Reply-To: <CAEfz+Ty+vN=-8UyMwgNTUg-C+zuEvn1w6vSy2nPe=2-hx1vWoA@mail.gmail.com>
References: <CAHKrs2P+hxziOFCs8E+1tp2hu5EsMnrQhcN6uZbB1TqTF1fUgg@mail.gmail.com>
 <CAEfz+Ty+vN=-8UyMwgNTUg-C+zuEvn1w6vSy2nPe=2-hx1vWoA@mail.gmail.com>
Message-ID: <uJuR6a5TCZXcJxJA_zaUJj__0yrvvYu6RfUs9poq8RnzHbqQyXMxxBaiW2bXeShPTlRunqtVNpT9ZvhtqUtan8JA82pKZH-lH2DHb5BXThY=@palard.fr>

While we're at it, does the project requires only one language to upload the pot files and it updates for everyone (what I think is true)?

But if so, why do we have different pot comments in different translations?

(In fact the franch translation does not use transifex, we still sync manually (translations only not pot) from time to time just in case, but nobody translate there).

--?
Julien Palard
https://mdk.fr


From marco at rougeth.com  Wed Apr 10 11:13:22 2019
From: marco at rougeth.com (Marco Rougeth)
Date: Wed, 10 Apr 2019 16:13:22 +0100
Subject: [Doc-SIG] Updates on Transifex
In-Reply-To: <uJuR6a5TCZXcJxJA_zaUJj__0yrvvYu6RfUs9poq8RnzHbqQyXMxxBaiW2bXeShPTlRunqtVNpT9ZvhtqUtan8JA82pKZH-lH2DHb5BXThY=@palard.fr>
References: <CAHKrs2P+hxziOFCs8E+1tp2hu5EsMnrQhcN6uZbB1TqTF1fUgg@mail.gmail.com>
 <CAEfz+Ty+vN=-8UyMwgNTUg-C+zuEvn1w6vSy2nPe=2-hx1vWoA@mail.gmail.com>
 <uJuR6a5TCZXcJxJA_zaUJj__0yrvvYu6RfUs9poq8RnzHbqQyXMxxBaiW2bXeShPTlRunqtVNpT9ZvhtqUtan8JA82pKZH-lH2DHb5BXThY=@palard.fr>
Message-ID: <CAHKrs2OhqE_T9CaqvM10YAW5FRTkOqBjoqwW6obE6nGA06az7w@mail.gmail.com>

I'm going to add one more question to the thread.

Today, we have a flat list with all resources on Transifex, which means
that each .rst file are reflected like <folder>--<resource>
(e.g.c-api--bool or c-api--buffer) on Transifex. It would be helpful to
have the resources into categories like we see on the source tree, mainly
because it'd be easier to see the statistics from a specific section and to
prioritize the ones we need to deploy the translation.

Also, it would be nice if someone has a different use case on Transifex.

Thanks,
Marco.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20190410/1604fc48/attachment.html>

From alessandro.cucci at gmail.com  Sat Apr 20 17:10:41 2019
From: alessandro.cucci at gmail.com (Alessandro Cucci)
Date: Sat, 20 Apr 2019 23:10:41 +0200
Subject: [Doc-SIG] Python Documentation Translation in italian language
Message-ID: <CAOr0AwmW3z0WMQSZCom+g9ySOTDeXx5qxW5r+JwWtP0FQPZATQ@mail.gmail.com>

Hello folks,
I want to start a project for translating the Python Documentation in
Italian.
I'm reading the PEP545, trying to understand how it works.

I founded a Python User Group in my city and I can work with them on the
translations, plus next month I will be speaker at Pycon Italy, so I can
easily sponsor this project during the talk and reclute more people to work
on that.

Is there anybody who can help me to start?
Thanks, have a nice day.

*Alessandro Cucci*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20190420/083a9d29/attachment.html>

From julien at palard.fr  Sun Apr 21 11:38:45 2019
From: julien at palard.fr (Julien Palard)
Date: Sun, 21 Apr 2019 15:38:45 +0000
Subject: [Doc-SIG] Python Documentation Translation in italian language
In-Reply-To: <CAOr0AwmW3z0WMQSZCom+g9ySOTDeXx5qxW5r+JwWtP0FQPZATQ@mail.gmail.com>
References: <CAOr0AwmW3z0WMQSZCom+g9ySOTDeXx5qxW5r+JwWtP0FQPZATQ@mail.gmail.com>
Message-ID: <qx0_e0MtH5qrOwDwR-AbgfYDgve6-cGaT7UUmIk83qINlOx5ggMV4pEOA_8Jva_M8MU5YGw8uUXSVJ42g2GdycuDKIlr6Zip7rBCxyiB6zk=@palard.fr>

Hi Alessandro!

> I want to start a project for translating the Python Documentation in Italian.

\o/

> Is there anybody who can help me to start?

I'm the author of the PEP 545, so I should be able to help.

Looks like there's two main ways of translating the Python documentation: git-centric or external-tool centric.

Most countries are going "external tool centric", and most if not all are using transifex here: https://www.transifex.com/python-doc/public/

You're free to choose another tool, there's very few rules around this:
- From time to time (automatically the better) sync to github so we can pull from it to build the docs on docs.python.org, github is our "meet point".
- Put the contributions under CC0 (see https://www.python.org/dev/peps/pep-0545/#setup-the-documentation-contribution-agreement)

France (my country) is doing "github centric", meaning we're only accepting pull requests on github, see our repo here: https://github.com/python/python-docs-fr/pulls

I like the github workflow for some reasons:
- We can give feedback on a contributor basis as pull request comments, and merge only when the quality is the one expected.
- Contributing to the docs means learning git, command line, cooperation in github, and so on. It's a door to do PR on other open source projects (like cpython upstream documentation), and sometimes translators in workshops are telling us "I did not translated much today, but I learnt a lot, thank you for this", and I like this.

If you choose the gitub workflow, there's a cookiecutter (https://github.com/JulienPalard/python-docs-cookiecutter) to bootstrap it, if you choose to sync from transifex or another tool don't hesistate to get inspiration from other countries (github.com/python/python-docs-* excepted fr and theme).

Next steps are: create the github repo (named python-docs-it), and gather people around the translation, if it works we'll migrate your repo to github.com/python/, and we'll have to nominate a coordinator for your language (typically you if you feel it).

After some translations done, don't hesistate to ask me to start building the doc on docs.python.org for preview purposes. And when you'll reach enough translations [1] we'll add your language to the menu.

Feel free to continue this thread if you have questions, and or come asking me on IRC, I'm mdk on freenode, there's the #python-doc channel dedicated to this.

[1]: https://www.python.org/dev/peps/pep-0545/#add-translation-to-the-language-switcher
--?
Julien Palard
https://mdk.fr


From alessandro.cucci at gmail.com  Sun Apr 21 13:23:08 2019
From: alessandro.cucci at gmail.com (Alessandro Cucci)
Date: Sun, 21 Apr 2019 19:23:08 +0200
Subject: [Doc-SIG] Python Documentation Translation in italian language
In-Reply-To: <qx0_e0MtH5qrOwDwR-AbgfYDgve6-cGaT7UUmIk83qINlOx5ggMV4pEOA_8Jva_M8MU5YGw8uUXSVJ42g2GdycuDKIlr6Zip7rBCxyiB6zk=@palard.fr>
References: <CAOr0AwmW3z0WMQSZCom+g9ySOTDeXx5qxW5r+JwWtP0FQPZATQ@mail.gmail.com>
 <qx0_e0MtH5qrOwDwR-AbgfYDgve6-cGaT7UUmIk83qINlOx5ggMV4pEOA_8Jva_M8MU5YGw8uUXSVJ42g2GdycuDKIlr6Zip7rBCxyiB6zk=@palard.fr>
Message-ID: <CAOr0AwksrvkX4ox2-D+RMZiY=mfG5M+sQRnDDETfdRKdRdA0LA@mail.gmail.com>

Thanks so much Julien!
> Looks like there's two main ways of translating the Python documentation:
git-centric or external-tool centric.
Since I'm a developer, I'll choose the git-centric way!

> If you choose the gitub workflow, there's a cookiecutter (
https://github.com/JulienPalard/python-docs-cookiecutter) to bootstrap it
Soo easy, thanks!

> create the github repo (named python-docs-it)
Done: https://github.com/alessandrocucci/python-docs-it

> gather people around the translation
This is harder, but I have faith in the community

For now, this is enough to get started. I'll play with poedit cause i've
never used it before and of course I'll keep you updated.


*Alessandro Cucci*


Il giorno dom 21 apr 2019 alle ore 17:38 Julien Palard <julien at palard.fr>
ha scritto:

> Hi Alessandro!
>
> > I want to start a project for translating the Python Documentation in
> Italian.
>
> \o/
>
> > Is there anybody who can help me to start?
>
> I'm the author of the PEP 545, so I should be able to help.
>
> Looks like there's two main ways of translating the Python documentation:
> git-centric or external-tool centric.
>
> Most countries are going "external tool centric", and most if not all are
> using transifex here: https://www.transifex.com/python-doc/public/
>
> You're free to choose another tool, there's very few rules around this:
> - From time to time (automatically the better) sync to github so we can
> pull from it to build the docs on docs.python.org, github is our "meet
> point".
> - Put the contributions under CC0 (see
> https://www.python.org/dev/peps/pep-0545/#setup-the-documentation-contribution-agreement
> )
>
> France (my country) is doing "github centric", meaning we're only
> accepting pull requests on github, see our repo here:
> https://github.com/python/python-docs-fr/pulls
>
> I like the github workflow for some reasons:
> - We can give feedback on a contributor basis as pull request comments,
> and merge only when the quality is the one expected.
> - Contributing to the docs means learning git, command line, cooperation
> in github, and so on. It's a door to do PR on other open source projects
> (like cpython upstream documentation), and sometimes translators in
> workshops are telling us "I did not translated much today, but I learnt a
> lot, thank you for this", and I like this.
>
> If you choose the gitub workflow, there's a cookiecutter (
> https://github.com/JulienPalard/python-docs-cookiecutter) to bootstrap
> it, if you choose to sync from transifex or another tool don't hesistate to
> get inspiration from other countries (github.com/python/python-docs-*
> excepted fr and theme).
>
> Next steps are: create the github repo (named python-docs-it), and gather
> people around the translation, if it works we'll migrate your repo to
> github.com/python/, and we'll have to nominate a coordinator for your
> language (typically you if you feel it).
>
> After some translations done, don't hesistate to ask me to start building
> the doc on docs.python.org for preview purposes. And when you'll reach
> enough translations [1] we'll add your language to the menu.
>
> Feel free to continue this thread if you have questions, and or come
> asking me on IRC, I'm mdk on freenode, there's the #python-doc channel
> dedicated to this.
>
> [1]:
> https://www.python.org/dev/peps/pep-0545/#add-translation-to-the-language-switcher
> --
> Julien Palard
> https://mdk.fr
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20190421/0619c2cc/attachment.html>

From alessandro.cucci at gmail.com  Mon Apr 29 08:01:12 2019
From: alessandro.cucci at gmail.com (Alessandro Cucci)
Date: Mon, 29 Apr 2019 14:01:12 +0200
Subject: [Doc-SIG] Python Documentation Translation in italian language
In-Reply-To: <CAOr0AwksrvkX4ox2-D+RMZiY=mfG5M+sQRnDDETfdRKdRdA0LA@mail.gmail.com>
References: <CAOr0AwmW3z0WMQSZCom+g9ySOTDeXx5qxW5r+JwWtP0FQPZATQ@mail.gmail.com>
 <qx0_e0MtH5qrOwDwR-AbgfYDgve6-cGaT7UUmIk83qINlOx5ggMV4pEOA_8Jva_M8MU5YGw8uUXSVJ42g2GdycuDKIlr6Zip7rBCxyiB6zk=@palard.fr>
 <CAOr0AwksrvkX4ox2-D+RMZiY=mfG5M+sQRnDDETfdRKdRdA0LA@mail.gmail.com>
Message-ID: <CAOr0Awn-BVEoR5ecJVotvCdj31LcPXmxqmn-XLQGN5GQ8_L6pA@mail.gmail.com>

Hi Julien,
contributors has to sign the
https://www.python.org/psf/contrib/contrib-form/ ?
How can I collect them using github? Are there any bots you recommend?
Another question: can I add a file to the repo to list contributors' names?
Thanks

*Alessandro Cucci*


Il giorno dom 21 apr 2019 alle ore 19:23 Alessandro Cucci <
alessandro.cucci at gmail.com> ha scritto:

> Thanks so much Julien!
> > Looks like there's two main ways of translating the Python
> documentation: git-centric or external-tool centric.
> Since I'm a developer, I'll choose the git-centric way!
>
> > If you choose the gitub workflow, there's a cookiecutter (
> https://github.com/JulienPalard/python-docs-cookiecutter) to bootstrap it
> Soo easy, thanks!
>
> > create the github repo (named python-docs-it)
> Done: https://github.com/alessandrocucci/python-docs-it
>
> > gather people around the translation
> This is harder, but I have faith in the community
>
> For now, this is enough to get started. I'll play with poedit cause i've
> never used it before and of course I'll keep you updated.
>
>
> *Alessandro Cucci*
>
>
> Il giorno dom 21 apr 2019 alle ore 17:38 Julien Palard <julien at palard.fr>
> ha scritto:
>
>> Hi Alessandro!
>>
>> > I want to start a project for translating the Python Documentation in
>> Italian.
>>
>> \o/
>>
>> > Is there anybody who can help me to start?
>>
>> I'm the author of the PEP 545, so I should be able to help.
>>
>> Looks like there's two main ways of translating the Python documentation:
>> git-centric or external-tool centric.
>>
>> Most countries are going "external tool centric", and most if not all are
>> using transifex here: https://www.transifex.com/python-doc/public/
>>
>> You're free to choose another tool, there's very few rules around this:
>> - From time to time (automatically the better) sync to github so we can
>> pull from it to build the docs on docs.python.org, github is our "meet
>> point".
>> - Put the contributions under CC0 (see
>> https://www.python.org/dev/peps/pep-0545/#setup-the-documentation-contribution-agreement
>> )
>>
>> France (my country) is doing "github centric", meaning we're only
>> accepting pull requests on github, see our repo here:
>> https://github.com/python/python-docs-fr/pulls
>>
>> I like the github workflow for some reasons:
>> - We can give feedback on a contributor basis as pull request comments,
>> and merge only when the quality is the one expected.
>> - Contributing to the docs means learning git, command line, cooperation
>> in github, and so on. It's a door to do PR on other open source projects
>> (like cpython upstream documentation), and sometimes translators in
>> workshops are telling us "I did not translated much today, but I learnt a
>> lot, thank you for this", and I like this.
>>
>> If you choose the gitub workflow, there's a cookiecutter (
>> https://github.com/JulienPalard/python-docs-cookiecutter) to bootstrap
>> it, if you choose to sync from transifex or another tool don't hesistate to
>> get inspiration from other countries (github.com/python/python-docs-*
>> excepted fr and theme).
>>
>> Next steps are: create the github repo (named python-docs-it), and gather
>> people around the translation, if it works we'll migrate your repo to
>> github.com/python/, and we'll have to nominate a coordinator for your
>> language (typically you if you feel it).
>>
>> After some translations done, don't hesistate to ask me to start building
>> the doc on docs.python.org for preview purposes. And when you'll reach
>> enough translations [1] we'll add your language to the menu.
>>
>> Feel free to continue this thread if you have questions, and or come
>> asking me on IRC, I'm mdk on freenode, there's the #python-doc channel
>> dedicated to this.
>>
>> [1]:
>> https://www.python.org/dev/peps/pep-0545/#add-translation-to-the-language-switcher
>> --
>> Julien Palard
>> https://mdk.fr
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20190429/6a556710/attachment.html>

From julien at palard.fr  Mon Apr 29 08:40:32 2019
From: julien at palard.fr (Julien Palard)
Date: Mon, 29 Apr 2019 12:40:32 +0000
Subject: [Doc-SIG] Python Documentation Translation in italian language
In-Reply-To: <CAOr0Awn-BVEoR5ecJVotvCdj31LcPXmxqmn-XLQGN5GQ8_L6pA@mail.gmail.com>
References: <CAOr0AwmW3z0WMQSZCom+g9ySOTDeXx5qxW5r+JwWtP0FQPZATQ@mail.gmail.com>
 <qx0_e0MtH5qrOwDwR-AbgfYDgve6-cGaT7UUmIk83qINlOx5ggMV4pEOA_8Jva_M8MU5YGw8uUXSVJ42g2GdycuDKIlr6Zip7rBCxyiB6zk=@palard.fr>
 <CAOr0AwksrvkX4ox2-D+RMZiY=mfG5M+sQRnDDETfdRKdRdA0LA@mail.gmail.com>
 <CAOr0Awn-BVEoR5ecJVotvCdj31LcPXmxqmn-XLQGN5GQ8_L6pA@mail.gmail.com>
Message-ID: <2L_yT5EZr8XZNVkhsLT2bs_DCybKUkPuRfaQoYRCDPU78AH_jIPGyzr-3bx6RzgqjINDW2NQLUgKsi1l7XmXPNBYKESw4p2VzU0R0Nn79IQ=@palard.fr>

Hi Alessandro,

> contributors has to sign the https://www.python.org/psf/contrib/contrib-form/ ?

No, it's too complicated to collect them as we're gathering translations from multiple sources.

> How can I collect them using github? Are there any bots you recommend?

You just have to put the Documentation Contribution Agreement [1] clearly visible at the very top of your README file.

> Another question: can I add a file to the repo to list contributors' names?

Yes! Maybe name it TRANSLATORS as we did, for consistency: https://github.com/python/python-docs-fr/blob/3.7/TRANSLATORS

[1]: https://www.python.org/dev/peps/pep-0545/#setup-the-documentation-contribution-agreement

Bests,
--?
Julien Palard
https://mdk.fr


From arj.python at gmail.com  Mon Apr 29 14:31:03 2019
From: arj.python at gmail.com (Abdur-Rahmaan Janhangeer)
Date: Mon, 29 Apr 2019 22:31:03 +0400
Subject: [Doc-SIG] Python Documentation Translation in italian language
In-Reply-To: <2L_yT5EZr8XZNVkhsLT2bs_DCybKUkPuRfaQoYRCDPU78AH_jIPGyzr-3bx6RzgqjINDW2NQLUgKsi1l7XmXPNBYKESw4p2VzU0R0Nn79IQ=@palard.fr>
References: <CAOr0AwmW3z0WMQSZCom+g9ySOTDeXx5qxW5r+JwWtP0FQPZATQ@mail.gmail.com>
 <qx0_e0MtH5qrOwDwR-AbgfYDgve6-cGaT7UUmIk83qINlOx5ggMV4pEOA_8Jva_M8MU5YGw8uUXSVJ42g2GdycuDKIlr6Zip7rBCxyiB6zk=@palard.fr>
 <CAOr0AwksrvkX4ox2-D+RMZiY=mfG5M+sQRnDDETfdRKdRdA0LA@mail.gmail.com>
 <CAOr0Awn-BVEoR5ecJVotvCdj31LcPXmxqmn-XLQGN5GQ8_L6pA@mail.gmail.com>
 <2L_yT5EZr8XZNVkhsLT2bs_DCybKUkPuRfaQoYRCDPU78AH_jIPGyzr-3bx6RzgqjINDW2NQLUgKsi1l7XmXPNBYKESw4p2VzU0R0Nn79IQ=@palard.fr>
Message-ID: <CADrxXXm7tnM7YfMwNgB32w0qK+mjRhaGn1Ht_EAO7PiHESCA0A@mail.gmail.com>

we must pin that info somewhere

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Garanti
sans virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Apr 29, 2019 at 4:40 PM Julien Palard via Doc-SIG <
doc-sig at python.org> wrote:

> Hi Alessandro,
>
> > contributors has to sign the
> https://www.python.org/psf/contrib/contrib-form/ ?
>
> No, it's too complicated to collect them as we're gathering translations
> from multiple sources.
>
> > How can I collect them using github? Are there any bots you recommend?
>
> You just have to put the Documentation Contribution Agreement [1] clearly
> visible at the very top of your README file.
>
> > Another question: can I add a file to the repo to list contributors'
> names?
>
> Yes! Maybe name it TRANSLATORS as we did, for consistency:
> https://github.com/python/python-docs-fr/blob/3.7/TRANSLATORS
>
> [1]:
> https://www.python.org/dev/peps/pep-0545/#setup-the-documentation-contribution-agreement
>
> Bests,
> --
> Julien Palard
> https://mdk.fr
>
> _______________________________________________
> Doc-SIG maillist  -  Doc-SIG at python.org
> https://mail.python.org/mailman/listinfo/doc-sig
>


-- 
Abdur-Rahmaan Janhangeer
http://www.pythonmembers.club | https://github.com/Abdur-rahmaanJ
Mauritius
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/doc-sig/attachments/20190429/c9d3c3b4/attachment.html>