Re: worflow and coordination for translations of the website (salsa and mailing lists)
First all, it's a shame nobody has answered you before :-/
Some weeks ago we (l10n-br-team) started a discussion about what is the
best approach to use salsa and mailing list. Your email give us a
guidance to make some tests about it.
On 30/09/2019 13:31, Laura Arjona Reina wrote:
Note: Please CC me, I'm not subscribed to debian-l10n-portuguese
There has been some conversation in #debian-www about how to coordinate
the translations of the website, given that we have now salsa in
addition to the mailing list and the traditional ways with the dl10n
robot and scripts (the system using ITT, RFR, etc).
I've been investigating a bit several options but I guess it depends a
lot on how a certain language team *wants* to coordinate.
1.- To get notifications of salsa commits/MR
Option A.- If you want to receive mail notifications when there are
commits in the web repos, please subscribe to the "www.debian.org"
pseudopackage via tracker.debian.org and activate the "vcs" keyword there.
See this mail
https://lists.debian.org/debian-publicity/2018/04/msg00001.html on how
to do it (it's explained for the publicity team but you just change
"press" for "www.debian.org" and it would do the same for the website team).
This will make you receive mails for *each* commit in *any* of the repos
of the web team, but I guess you can filter them to get the ones you
want, using their headers, subjects, etc. (The Portuguese team can agree
in adding some word to the "interesting" commits to help this, e.g.
"[Portuguese]" or "pt_br" or whatever).
Option B.- You can change your (individual) notifications settings via
salsa, by logging into salsa and going to
https://salsa.debian.org/webmaster-team/webwml and then play with the
icon of the bell.
Option C.- You can change your notifications settings via salsa as in
Option B, but for the fork repo you're working on:
Option D.- The people with permissions on
https://salsa.debian.org/l10n-br-team/webwml could login in salsa and
tune the settings of that repo, so it notifies the list on any commit,
push, or event. This can be technically done going to Settings >
Integrations > Emails on push, and adding
email@example.com as recipient.
Note that both options A, B and C produce mails to your personal
account: each translator should do one of those (if they want to receive
the mails). Option D sends to the debian-l10n-portuguese mailing list so
everybody subscribed would receive the mails (also translators working
in other areas of Debian that are not the website...).
Options C and D would have the advantage of receiving notifications only
for the activity in the files your team usually touches, plus one mail
each time somebody syncs your fork with the original webwml repo.
2.- Coordination with the website translation dashboards
(I mean this: https://www.debian.org/devel/website/stats/pt )
To get benefit of the website translation dashboards (updated once a
day), you still need to send mails to the debian-l10n-portuguese mailing
list with a subject showing the status of each file (TAF, ITT, RFR,
LCFC, DONE). The website uses the translation-check headers of each wml
file for 2 things:
* to show in the corresponding (built) HTML file a yellow banner warning
if the translation is outdated
* to send mails to the translators listed in each "maintainer" field of
the translation-check header, about the status of their files
But the statistics/dashboard pages such as
https://www.debian.org/devel/website/stats/pt are built parsing the
debian-l10n-portuguese mailing list, and is not coordinated with the git
repo nor salsa.
For the dashboard, it is not relevant if you attach the file or not when
you send for example an [RFR] mail (only the subject will be taken into
3.- Coordination between your fork and the webwml repo (merge requests etc)
If you decide to work in your team fork
https://salsa.debian.org/l10n-br-team/webwml and when the file or files
are ready, submit a merge request to the webwml repo of the web team
(https://salsa.debian.org/webmaster-team/webwml/ ), please take into
* Please keep the fork in sync to avoid generating unneeded "merge
* A member of your team will need to actually merge those merge
requests, since the rest of the web team don't know Portuguese and
probably cannot check that everything is ok.
* If you would like more people to get commit access to the original
webwml repo, please somebody with already commit access send an email to
debian-www mailing list asking for person(s) X to be added, explaining
that they are members of the team etc. This is needed because the Salsa
"request to join" button sends us only the request but with no context,
and we don't know all the Debian contributors nor if they are ready to
commit directly :-)
* I'm not sure if you'll get a notification when a MR is accepted
(merged into the original webwml repo). I think yes if you have set your
personal notifications in Salsa, but I'm not sure if the "settings >
Integrations > push to email" will work too. We can try, if you decide
to use that option.
I hope this info can help you to design your preferred workflow.
I'm not sure how other teams coordinate. The Spanish team don't use
salsa (only commits and the usual mailing list messages ITT, RFR, etc,
with the corresponding files attached, for p2p review).
I'm CC'ing the debian-i18n mailing list for the case somebody has
different ideas or suggestions.
Don't hesitate to ask anything and we can try to figure out.
Paulo Henrique de Lima Santana (phls)
Curitiba - Brasil
Diretor do Instituto para Conservação de Tecnologias Livres
GNU/Linux user: 228719 GPG ID: 0443C450