Le 22/01/2020 à 17:35, Sundeep Anand a écrit :
That would help in tracking purposes.
It really goes complex in Transtats when we have multiple upstream
projects in just one translation project for example
(similarly multiple upstream project into one srpm/rpm or vice-versa)
I'm afraid you'll never reach this perfect situation.
Here is an example of multiple components for a single Fedora package:
And here an example of one single project with one rhel dedicated
Both use cases will increase over time.
Limiting the ways to configure in Weblate will not be possible, mostly
because of the configuration burden it would mean for me.
For the migration, I do the first component configuration of upstream
team. If they want to configure additional components, or tune settings,
they have administration rights to do it.
Nobody can add a new project without asking me first. I do it for now
only to make sure we translate upstream open source software and not
what an individual decided to translate (multiple example in Zanata for
This may change in the future once I'll be able to force the users to
set a license. I opened these requests that I feel like being a
But anyone with an existing project can change or add a component.