I proposed some qqq in https://gerrit.wikimedia.org/r/c/operations/software/mailman-templates/+/685533/ - let me know if that's sufficient or needs improvement.

@Legoktm I added a few questions to the description and Nemo_bis has left similar ones in the qqq patch. Logo is not needed.

Change 692330 had a related patch set uploaded (by Nikerabbit; author: Nikerabbit):

[translatewiki@master] WIP: Add Wikimedia Mailman templates

https://gerrit.wikimedia.org/r/692330

I'm a bit behind on this, some other higher priority MM issues have come up, but I'm still trying to make progress on it.

• Why are there empty messages?
  • Nemo pointed this out as well, I'll delete them.
• Some messages contain literal tabs, which will be hard to input for translators
  • Would 4 spaces work better? These are all plain text so indentation is used for formatting. Some lines do have a leading space before URLs which is required to be there.
• Is there difference between $foo and ${foo} variable syntax, or could they be unified?
  • ${foo}bar is $foo plus "bar" while $foobar is $foobar. We can use the ${foo} syntax everywhere.
• Is sr expected to be in Latin or Cyrillic script?
  • I don't know, how can I determine this? https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.cfg#L611 just says "Serbian" and utf-8. It doesn't even look like anyone has translated MM3 into Serbian yet.. https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/messages

In T282022#7137308, @Legoktm wrote:

I'm a bit behind on this, some other higher priority MM issues have come up, but I'm still trying to make progress on it.

No worries, you're doing important stuff.

• Some messages contain literal tabs, which will be hard to input for translators
  • Would 4 spaces work better? These are all plain text so indentation is used for formatting. Some lines do have a leading space before URLs which is required to be there.

Yes.

• Is there difference between $foo and ${foo} variable syntax, or could they be unified?
  • ${foo}bar is $foo plus "bar" while $foobar is $foobar. We can use the ${foo} syntax everywhere.

+1 for consistency

• Is sr expected to be in Latin or Cyrillic script?
  • I don't know, how can I determine this? https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.cfg#L611 just says "Serbian" and utf-8. It doesn't even look like anyone has translated MM3 into Serbian yet.. https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/messages

The comment says the list is derived from Mailman 2. Did it have translations there?

In T282022#7138044, @Nikerabbit wrote:

In T282022#7137308, @Legoktm wrote:

• Is sr expected to be in Latin or Cyrillic script?
  • I don't know, how can I determine this? https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.cfg#L611 just says "Serbian" and utf-8. It doesn't even look like anyone has translated MM3 into Serbian yet.. https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/messages

The comment says the list is derived from Mailman 2. Did it have translations there?

https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/messages/sr/LC_MESSAGES/mailman.po so Cyrillic

Pushed some new commits, I think I've addressed all the feedback so far.

Change 704281 had a related patch set uploaded (by Abijeet Patro; author: Abijeet Patro):

[translatewiki@master] Add Wikimedia Mailman Templates

https://gerrit.wikimedia.org/r/704281

Change 704281 merged by jenkins-bot:

[translatewiki@master] Add Wikimedia Mailman Templates

https://gerrit.wikimedia.org/r/704281

The patch has been deployed, and we can now translate the project here: https://translatewiki.net/wiki/Special:Translate/wikimedia-mailman-templates

Exports will happen today at around 1100 UTC

Change 692330 abandoned by Nikerabbit:

[translatewiki@master] WIP: Add Wikimedia Mailman templates

Reason:

See https://gerrit.wikimedia.org/r/c/translatewiki/ /704281

https://gerrit.wikimedia.org/r/692330

A few things to do:

1. Message documentation has been added. Ensure that they appear properly.
2. Enable translations to message documentation on translatewiki.net
3. No exports yesterday, possibly because there were no translations yet. Check again on 22nd Jul.

Automatic merging is not working: https://gerrit.wikimedia.org/r/c/operations/software/mailman-templates/+/706390

Jenkins bot never voted on it. It should have the right to.

In T282018#7069803, @gerritbot wrote:

Change 685938 merged by jenkins-bot:

[integration/config@master] Zuul: [operations/software/mailman-templates] Add CI of debian-glue

https://gerrit.wikimedia.org/r/685938

The config change adds:

gate-and-submit-l10n:
  - debian-glue

The debian-glue job only runs for changes affecting a file in the ./debian directory, it is otherwise not triggered. Since L10n-bot only touches ./i18n/* (example), the job is never run, the gate-and-submit-l10n pipeline does not run any job and the change is left idling waiting for job success that will never come.

Other repositories have the job mediawiki-i18n-check-docker which run the diff through a large sed that attempts to detect HTML. So I guess we should use that job and drop debian-glue.

Change 706443 had a related patch set uploaded (by Hashar; author: Hashar):

[integration/config@master] zuul: [mailman-templates] use i18n checker

https://gerrit.wikimedia.org/r/706443

Change 706443 merged by jenkins-bot:

[integration/config@master] zuul: [mailman-templates] use i18n checker

https://gerrit.wikimedia.org/r/706443

The job fails due to:

+	"help": "Aide pour la liste de diffusion ${listname}\n\nC’est la commande de courriel 'help' pour la version ${version} du gestionnaire de liste\nGNU Mailman sur ${domain}.  Ce qui suit décrit les commandes que vous pouvez envoyer pour obtenir\nde l’information sur le sujet et contrôler votre abonnement aux listes sur ce site.\nUne commande peut être dans la ligne Sujet ou dans le corps du message.\n\nLes commandes doivent être envoyées à l’adresse ${listname}-request@${domain}.\n\nÀ propos des descriptions - les mots entre \"<>\" signifient des éléments OBLIGATOIRES, et\nles mots entre \"[]\" signalent les éléments FACULTATIFS.  Ne pas inclure les \"<>\" ou\n\"[]\" quand vous utilisez les commandes.\n\nLes commandes suivantes sont valides :\n\n    ${commands}\n\nLes questions et inquiétudes à l’adresse d’une personne doivent être envoyés à :\n\n    ${administrator}",

I guess that is because of <> instead of &lt;&gt;?

In T282022#7229672, @hashar wrote:

In T282018#7069803, @gerritbot wrote:

Change 685938 merged by jenkins-bot:

[integration/config@master] Zuul: [operations/software/mailman-templates] Add CI of debian-glue

https://gerrit.wikimedia.org/r/685938

The config change adds:

gate-and-submit-l10n:
  - debian-glue

The debian-glue job only runs for changes affecting a file in the ./debian directory, it is otherwise not triggered. Since L10n-bot only touches ./i18n/* (example), the job is never run, the gate-and-submit-l10n pipeline does not run any job and the change is left idling waiting for job success that will never come.

Ugh, that's not great for native Debian packages which should run the build process on every commit. I guess I can just add a simple tox wrapper to run the tests.

Other repositories have the job mediawiki-i18n-check-docker which run the diff through a large sed that attempts to detect HTML. So I guess we should use that job and drop debian-glue.

That's not useful here, these aren't HTML, it's all plain text.

l10n-bot-watchers rights are still missing, so we can't even override Jenkins currently. Docs: https://www.mediawiki.org/wiki/Gerrit/L10n-bot