Fwd: New Transifex API

--===============6645235703149080758==
Content-Type: multipart/alternative; boundary="000000000000c5af0605c8ed16a1"

--000000000000c5af0605c8ed16a1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi there!

The Brazilian translation community uses Transifex API for quite a few
tasks and, the recently released version of it will break a couple of our
use cases.

For example, we have scripts that generate weekly reports,  where we can
see the progress of the week and the areas in the doc recently changed.
This helps us to keep track of our work and to focus on missing translation
sections.

Another example is a bot we created to send a random string to everybody
that wants to participate. It runs daily and, the best part is that for
simple or small phrases, the user can reply the translated version directly
to the bot without ever going to the Transifex website.

We have done all of that using version 2.5 of the official Transifex API.
The problem is that they've released version 3 of the API, which is not
backwards compatible with the one we are currently using. One of the
breaking changes is that in the new API, listing the resources (or *.po
files) is allowed only for maintainers of the project on Transifex. We=E2=
=80=99ve
confirmed this issue with their support:

Only Project Maintainers can add/remove resources, thus resources can only
> be queried by Project Maintainers and Administrators. So, if you grant
> access to this role, you will have access to that list.
>

With that said, I=E2=80=99d like to know if we can have someone from our co=
mmunity
promoted as a maintainer of the python-doc project on Transifex. This will
allow us to migrate to the new API version without losing our tools.

Cheers,
Marco.

---

Originally sent to [email protected]. Thanks Shengjing Zhu reminding
me about doc-sig mailing list.

--000000000000c5af0605c8ed16a1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi there!<br><br>The Brazilian translation community uses =
Transifex API for quite a few tasks and, the recently released version of i=
t will break a couple of our use cases.<br><br>For example, we have scripts=
 that generate weekly reports, =C2=A0where we can see the progress of the w=
eek and the areas in the doc recently changed. This helps us to keep track =
of our work and to focus on missing translation sections.<br><br>Another ex=
ample is a bot we created to send a random string to everybody that wants t=
o participate. It runs daily and, the best part is that for simple or small=
 phrases, the user can reply the translated version directly to the bot wit=
hout ever going to the Transifex website.<br><br>We have done all of that u=
sing version 2.5 of the official Transifex API. The problem is that they&#3=
9;ve released version 3 of the API, which is not backwards compatible with =
the one we are currently using. One of the breaking changes is that in the =
new API, listing the resources (or *.po files) is allowed only for maintain=
ers of the project on Transifex. We=E2=80=99ve confirmed this issue with th=
eir support:<br><br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Only =
Project Maintainers can add/remove resources, thus resources can only be qu=
eried by Project Maintainers and Administrators. So, if you grant access to=
 this role, you will have access to that list.<br></blockquote><br>With tha=
t said, I=E2=80=99d like to know if we can have someone from our community =
promoted as a maintainer of the python-doc project on Transifex. This will =
allow us to migrate to the new API version without losing our tools.<br><br=
>Cheers,<br>Marco.<br><br>---<br><br>Originally sent to <a href=3D"mailto:t=
[email protected]">[email protected]</a>. Thanks Shengjing Zhu rem=
inding me about doc-sig mailing list.<br></div>

--000000000000c5af0605c8ed16a1--

--===============6645235703149080758==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Doc-SIG maillist  -  [email protected]
https://mail.python.org/mailman/listinfo/doc-sig

--===============6645235703149080758==--