+1

This sounds like an awesome thing to have. +1

Placeholder -1 while the discussion on the mailing list continues.

not to contradict this effort, however, for the first part:
some level of translation progress is already available in Transtats.
for example:

• for French: https://transtats.fedoraproject.org/languages/view/fr_FR
• for German: https://transtats.fedoraproject.org/languages/view/de_DE

(change the language for more, it has package level details too)

• for f34: https://transtats.fedoraproject.org/releases/view/fedora-34
• for f33: https://transtats.fedoraproject.org/releases/view/fedora-33

transtats.fedoraproject.org just has about 100 packages.. and anyone who has a fedora-id can add more .. certainly this can be tweaked if something else is required.

Furthermore, Transtats Jobs interacts with koji for translation statistics in built packages. this can be extended as per requirements, for example, with a download link for the extracted translations.

Edit: Use cases of Transtats had been covered in a talk and a post.

@suanand, https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/6CGTRYGDQPGS2QPQVGCNUIDDZLRAQQZU/

Transtats covers 100 packages, while the change darknao and I do the following (stats are for f33):

• use dnf to download all srpm for a fedora relaese (21330 packages)

OK, so what's the plan with transtats? Let's say that languages.fedoraproject.org is working nicely in half a year... Do we end up with translate.fp.o, transtats.fp.o, and languages.fp.o ?

In general I like this proposal, but we have too many half-done things in Fedora. I'm missing a comprehensive overview how this new shiny thing is going to tie into existing infrastructure, and what parts of that infrastructure will be obsoleted. Just adding things without trying to clean up and remove existing things leads to a state where releng is trying to support 200 different services.

We could probably try to merge both tools together by writing down the goals each tool want to achieve.

My instinct tells me:

• merge processing of this change request with the one in transtats
• refine the transtats UI

Discussing this probably requires a dedicated workshop, some kind of Fedora Activity Day in a common physical location. I don't see this possible for both personal reasons and pandemic, maybe in august before Flock?

We could probably try to merge both tools together by writing down the goals each tool want to achieve.

That would be a good goal to have, I agree

Discussing this probably requires a dedicated workshop, some kind of Fedora Activity Day

Yes I think that would be great

I saw this was discussed in meeting last week. Good! :)

Fedora Infra is not supposed to have to maintain anything, as target is to be hosted on openshift.
In the two owners: darknao is taking care of the openshift automation and requirements.
We already worked together on https://os.fedoraproject.org/console/project/docstranslation/ for fedora docs l10n automation.

Resources consumption shouldn't be too high as plan to build one single release at a "fast" pace, while old ones will be once a month or less.

Website resources requirement is 2GB per Fedora release at the moment, I would be surprised to be identified as an issue for the Fedora project.
We plan to publish one single Fedora release for now (f34), we'll add more once it works fine.

This Change was approved in today's FESCo meeting.

AGREED: Localization measurement tooling makes sense to have, given that the localization team is developing and maintaining it (+7, 0, -0)

Announced: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/CJKN5LTRBDQE53THF77UNWQ2DVBNFNVZ/