#8291 Fedora messaging - Translation platform topics review
Opened a month ago by jibecfed. Modified 24 days ago

Our future translation platform will send to fedora messaging.

The Weblate dev, Michal Čihař, did this: https://github.com/WeblateOrg/fedora_messaging/

He says: "Also it would be great if somebody would review the payload and topics if those make
sense, because I have no clue how those things are going to be used."

As I never used the Fedora messaging and as I'm not a dev, I don't feel like I can assume this task. Who can give it a look?


I think the question is: what do you want to use these notifications for?
Answering this question should help you figure out if the messages have the content you need.

I don't think infra has anything scheduled at this time around weblate, so I don't think we have an opinion at what the content of the notifications should be.

One thing you may want to discuss with upstream is adding message schema to their plugin: https://fedora-messaging.readthedocs.io/en/stable/messages.html#schema

(If it is already there, sorry for missing it :()

Thank you for your answer, my question was purely on technical aspect, such as the schema or naming rules. I think it's OK to close this if no other advice or issue identified.

On request of @bex here is a ping for @mattdm and @bcotton

In short: the weblate dev did the work to push the changes you can see here: https://translate.stg.fedoraproject.org/changes/ in our messaging infrastructure. The purpose of this is to be able to track Localization team activity using the tools we use the measure our community activity. The biggest volume is related to the number of translations, which also is the most interesting data.

In addition for infra team, the weblate dev says:

I don't think I can push directly to your infra, I probably need some
SSL cert and configuration to do that. The documentation [1] covers
consuming the events, but doesn't speak about what is needed for
publishing to your infra.

[1]: https://fedora-messaging.readthedocs.io/en/stable/fedora-broker.html

That is correct, we'll have to provide them with an SSL cert so they can published on the bus.

@jibecfed Can the folks at weblate provide the following in their repo's README:

  • Several example messages
  • A guide to the values that will appear in the action field and a list if it is reasonable to be exhaustive.

Can you:

  • Verify the following have specific meaning in weblate and are well understood:
    • url
    • project
    • component
  • Verify both of these represent FAS IDs?
    • author
    • user

I think this will allow us to understand the review request.

thanks Bex.

I confirm url, project and component are standard items from Weblate. I explicitly asked to have these.

With current configuration, user will always be a user existing in FAS. I'll check with Weblate folks if we it's indeed the FAS ID and not something else.
Author may be unknown if we accept non logged user to suggest an improvement.

It is possible in Weblate to allow other connection methods than FAS. I'm unsure we'll enable these someday, but if we decide to do so, user value may vary.

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

a month ago

example were added, please give your feedback: https://github.com/WeblateOrg/fedora_messaging/

In the example the dev added, three are technical, three are functional, but I assume there will be many more.

Here is my opinion on how we may use it.

  • Repository merge event, new source string event and Resource update event are technical indicator, useful for debugging in our early adoption and every once in a while afterwards.
    • May be useful to track upstream issues with po files: when we suddenly have a lot of translation to do for an already translated project, it means something went wrong, it's what happening now with REHL, French team went from 1000 words to 60 000 words to translate, but I can't investigate...
  • Project removal event: functional indicator, useful for public stats (I assume project creation is also in the list of events)
  • New contributor event: functional indicator, useful for welcoming newcomers and to monitor community health
  • New translation event: functional indicator, useful to monitor community health and provides badges to contributors

Login to comment on this ticket.

Metadata