Adding projects to Damned Lies
This guide aims to answer common questions of project maintainers that would like to have their project translated by GNOME translation teams using the dedicated translation platform Damned Lies.
Requirements and recommendations
Procedural requirements
The following are required in order be allowed to have the projects translated in use Damned Lies:
Not use another translation platform. This bypasses the workflow and coordination of the translation teams, potentially causing conflicts that result in translations/credits loss. If your project use another translation platform, please phase it out in order to start using Damned Lies.
Not receive translation update from another source. This includes from pull requests or merge requests. Contributors must be encouraged to contribute in the respective language's translation team in Damned Lies.
Not edit PO files exclusively to translation teams. Unless there is a breakage, fixing manually PO files also bypasses translation team workflow and coordination and, therefore is not allowed. For improving translations, notify translations by any public way e.g. gnome-i18n mailing list, filing an issue mentioning translations so they get notified, etc.
Technical requirements
Requirements only for source code repo in GNOME GitLab:
Non-personal namespace: if your project is in a repository in your personal namespace in GNOME GitLab (e.g. johndoe/your-project), request it to be move to another namespace available in Damned Lies. Example of namespaces are: GNOME for core apps, World for extra apps and Circle apps (Consider applying for GNOME Circle!).
.doap file: Make sure .doap file is properly set describing your project, see Git/FAQ for an example.
Add @translations with Developer role: in order for Damned Lies be able to push translations, @translations user must be a member of your repository with the Developer role
If branch protected, allow pushes from Developer: Master/main branches are protected by default, allowing pushes only by Maintainer role. So it is important to allow Developer role to push commits, allowing @translations user to bring translations to the repository. See Protected branches.