Re: Project structure in weblate?

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 
> https://translate.fedoraproject.org/projects/abrt/
> (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: 
https://translate.fedoraproject.org/projects/authselect/

And here an example of one single project with one rhel dedicated 
branch: https://translate.fedoraproject.org/projects/pykickstart/


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).

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 
requirement: https://github.com/WeblateOrg/weblate/issues/3369 and 
https://github.com/WeblateOrg/weblate/issues/3370


But anyone with an existing project can change or add a component.


Jean-Baptiste
_______________________________________________
trans mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[email protected]