Page MenuHomePhabricator
Create Task
Maniphest T433169

translatewiki.net: translation support for https://github.com/wikimedia/CopyPatrol may be dropped due to inactivity
Open, Needs TriagePublic
Actions

Description

translatewiki.net provides translation services for this project. As part of our annual activity audit (T383652), we semi-automatically check whether supported projects are still actively developed.

Our supported projects requirements include:

🛠 Active maintenance: To maximize the impact of our translators' efforts, we require regular availability of translations to users (at least annually, but more frequently is preferred) and integration into your version control system at least once a quarter.

Our audit found that https://github.com/wikimedia/CopyPatrol has not had an upstream (non-translation) commit in over 12 months. Based on this, we are considering dropping translation support.

If this project is still active, please let us know — we'd love to continue supporting it! A brief update on the project's status and plans would be appreciated.

Please reply at: https://translatewiki.net/wiki/Translating_talk:Activity_Audit_2026

A reply in this task is also fine.

If we don't hear back within a reasonable time, we will proceed with removing this project from translatewiki.net.

Related Objects

Event Timeline

siebrand created this task.Sat, Jul 25, 1:27 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSat, Jul 25, 1:27 PM
siebrand added a project: translatewiki.net.Sat, Jul 25, 1:49 PM
siebrand moved this task from Backlog to Projects to remove on the translatewiki.net board.Sat, Jul 25, 1:56 PM
JJMC89 added a project: Moderator-Tools-Team.Mon, Jul 27, 5:02 PM
JJMC89 moved this task from Backlog to Front end on the CopyPatrol board.
JJMC89 updated the task description. (Show Details)Thu, Jul 30, 4:44 PM
JJMC89 subscribed.EditedThu, Jul 30, 4:53 PM

While the project is not in active development, it is actively used (e.g., https://copypatrol.wmcloud.org/en/leaderboard).

Commits, including translations, to that repo are automatically deployed daily.

MusikAnimal subscribed.Fri, Jul 31, 6:21 PM

The frontend is actually deployed via release tags, so indeed we were missing a year's worth of translation updates :( I just cut a new release now, so everything is up-to-date.

CopyPatrol has a new home under Moderator-Tools-Team. We will discuss this. I'm thinking we should auto-deploy translation updates. The app could probably use some dependency version bumps as well, but rest assured, as JJMC89 says, the tool is actively being used and there's benefit to keeping our TWN integration.

siebrand added a comment.Fri, Jul 31, 9:46 PM

there's benefit to keeping our TWN integration.

We would like you to guarantee and ideally allow for verification of regular deployment of translations. From what I understand you're planning regular deployments now. Displaying some kind of identifier on the deployed version could achieve that. When dealing with lots of different pieces of softeware, a year goes by quickly. Translator effort is usually real human effort that other real people benefit from. We shouldn't let it gather dust for a long time in a git repo; it should be incorporated in software as quickly as possible, and in online software that's usually easy if it's defined as an important aspect of the software development process.

Thanks for considering this.

MusikAnimal mentioned this in T434139: CopyPatrol: Show date of last deployment in the footer.Wed, Aug 5, 7:14 PM
MusikAnimal mentioned this in T434140: Set up CopyPatrol frontend with rootless Docker deployments.Wed, Aug 5, 7:19 PM
MusikAnimal added a comment.Wed, Aug 5, 7:22 PM

We would like you to guarantee and ideally allow for verification of regular deployment of translations. From what I understand you're planning regular deployments now. Displaying some kind of identifier on the deployed version could achieve that. When dealing with lots of different pieces of softeware, a year goes by quickly. Translator effort is usually real human effort that other real people benefit from. We shouldn't let it gather dust for a long time in a git repo; it should be incorporated in software as quickly as possible, and in online software that's usually easy if it's defined as an important aspect of the software development process.

Thanks for considering this.

You got it! I will add a message to the site footer indicating the date of last deployment. We do similarly in other tools we maintain. I've filed T434139 for that.

The auto-deployments haven't been set up yet but I would like to do that. I'm thinking we can adopt the same rootless Docker deployment system that Moderator-Tools-Team uses for their other tools, and that will have it deploy on every commit. Takes time and some skills I haven't mastered yet, so for now I've filed T434140 for triaging, and in the meantime we'll be more diligent about manually deploying from time to time.

Not sure if this is enough to consider this task resolved or not?

siebrand added a comment.Sat, Aug 8, 8:44 PM

Not sure if this is enough to consider this task resolved or not?

Great work. Thanks.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits