WeblateOrg / WeblateOrg/weblate

Differentiate and Filter Translations by User Group (e.g., Community vs. LSP)

Open
#15,718 3 comments 0 reactions 0 assignees View on GitHub
Waiting for: Demand
Dominant language
Python
Stars
6.1k
Forks
1.4k
Avg merge
9h 53m
Merged PRs (30d)
395

Description

### Describe the problem

We work with two distinct translator groups: a professional Language Service Provider (LSP) and volunteer community translators. Currently, Weblate does not provide a way to differentiate contributions from these groups. This makes it difficult to apply separate Quality Assurance (QA) workflows or accurately track contributions from each source.

### Solution brainstorm

We propose a feature based on User Groups.
- When a user from a specific group (e.g., the 'LSP' group) saves a translation, store the user's group as metadata associated with that specific string version.
- Enhance the search and filtering capabilities to allow users to filter strings based on the translator's group (e.g., "Show all strings last edited by the 'Community' group").

### Describe alternatives you have considered

_No response_

### Screenshots

_No response_

### Additional context

Key Benefits
This would enable several improvements to our workflow:
- We could quickly filter and batch-approve all work from the trusted LSP group.
- We could easily isolate community translations to send them for professional review.
- We could track and report on community contributions to acknowledge their valuable work.

This would make our review process much more efficient and give us better insight into our localization efforts.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.