I tried to prepare some information regarding the use of our
Weblate translation platform by projects for translating
their content, which could be published as a page in our
The proposal is available for reading in the staging
instance of the Fedora Documentation site and please comment
in this mail list thread (alternatively, in the L10N matrix
room/irc channel). Those who have access to pagure, please
comment in the below ticket (if possible look to the
source file of the page where are some my comments, too).
I'll try to pursue comments made in all sources and write
them down to the ticket.
This new page contains information we would like to
communicate to (upstream) project owners, regarding our
Weblate translation platform. Basically, the information
should make clear what projects that would like to use
Weblate should expect from our side and what they should be
ready for on their side in order to use Weblate for their
localization. Ideally, it should have some explanatory text,
possibly procedural text and some reflections from
experience in practice (hints).
This is a first shot in collecting such information. The
author of most of the information is Jean-Baptist (thank
you!) in his various posts to trans(a)lists.fedoraproject.org.
I'd like to ask you for comments and reviews. Particularly,
I would be happy if you could help me answer these
- is this the right direction?
- is there a better title of the page (Translation projects
in Weblate), the name of the file (hosting.adoc)?
- what could be added or removed for information?
Thank you very much if you find some time to look into this
and contribute your comments, views, suggestions...
Hello to all,
I am still thinking about the state of the repositories in
the fedora-l10n namespace on the pagure.io. It's not that
there is basically something wrong with them, but IMHO there
is a danger of single-point-of-contact failure. When I
realize the users with a commit access or higher are:
* jibecfed (maintainer of all repositories)
* yaron (commit for kde)
I recall when Jean-Baptiste, for example, once answered to
mattdm that he didn't have time to maintain fedora-l10n/doc
repository (while I think he is, in case of an urgent need,
able to help with weblate's things.) asamalik is propably
not more there, too. Nowadays, more or less all lays on the
shoulders of darknao. And copperi is hopefully able to put
some hands on as well.
In this thread could we somewhat reconsider how to better
organize (us) around these repositories?
Would it be possible to have among the users of the
repositories an account that is linked to the fedora-infra
team, for example with the admin role? (I am deeply sorry
for expecting all of you would have gone from the l10n
matters...) Personally, I'd like to see a moment when we
have "a backup of a backup".
We could also reconsider if to maintain the fedora-
l10n/tickets repository. We could have it as a part of
fedora-l10n/docs, if we use tags for issues...?
Do you have anything to propose, comment or your view in
A little similar situation is with the weblate
administration. By going throught this mail list I learned
that the weblate admins are:
* (and perhaps again) darknao
Does this group needs some update, too?
I have some more things to ask or propose, but let's see if
we are able to come to some conclusions in these two things.
PS.: Merry Christmas and Happy New Year!
I used to translate a lot in the past, and now I want to do the same. How
can I locate my Bulgarian peers to see where help is needed? The mailing
list is dead, and everyone seems inactive.
I am still listed as a sponsor for the locale, is this still a thing, and
what can I do with this?
Also, is there a priority for the properties to be translated? I could
start with something, but a priority list would be great.
Also, many pages need to be updated for the L10n/ I18n and G11n. Can I help
review them and make sure they are up-to-date?
Have a great day,
Bogomil "Bogo" Shopov
I care about #privacy, #ethical design, #freedom, and #cybersecurity.
Fediverse/Mastodon: @bogo(a)hapyyr.com <https://hapyyr.com/@bogo>