Component lists rewamp

[nijel]

Describe the problem

Presently, component lists are a site-wide grouping of components across projects, configurable in the Django admin only.

The original intention was to be able to see progress of translations across projects.

A typical use case is openSUSE, which uses these to track translation progress of individual distro releases: https://l10n.opensuse.org/component-list/opensuse-leap-15_6/

Describe the solution you would like

We need to better define expectations and then adjust implementation.

• What do we expect from component lists? Especially on shared sites, where there is no need for centralized component lists.
• Who should be able to create and edit component lists? This is bound to the previous question.
• Should it affect permissions? It currently does and complicates the code.

Describe alternatives you have considered

No response

Screenshots

No response

Additional context

• [ ] https://github.com/WeblateOrg/weblate/issues/1370
• [ ] https://github.com/WeblateOrg/weblate/issues/7181
• [ ] https://github.com/WeblateOrg/weblate/issues/11549
• [ ] https://github.com/WeblateOrg/weblate/issues/5792

[tomkolp]

Should it affect permissions? It currently does and complicates the code. Please elaborate on how this relates to permissions?

Our entire translation system is based on component lists. We use component lists to assign permissions to very large sets of components.

Translators who do not have access to the entire project have their own component list. This list contains only the components they have access to. Without component lists, how can I assign, for example, 1000 components to a translator? I currently use component lists for this.

If it is necessary to abandon assigning translation permissions using component lists, it should be possible to assign permissions using categories.

[nijel]

That's why this issue is here to collect use cases and design the feature based on that. Currently, the feature is a bit hidden, so it has very little users. Once we make it more visible, it might be too late to make more significant changes to it without breaking existing workflows.

[tomkolp]

I will only add that for a few/several months there is a problem with long loading, after clicking "Add a new list of components" in the Django interface, the same for previewing already created componet lists. In the normal weblate interface, componet lists work without a problem.

[nijel]

@tomkolp a96a13d41add9155ccfa89bf11268c14118ad761 should fix that, but opening a separate issue for that would be a better approach :wink:

[michael-smt]

If it is necessary to abandon assigning translation permissions using component lists, it should be possible to assign permissions using categories.

It would be great to get support assigning permissions using categories. I have opened #12851 for this.