I’d like to get a new version of the French language pack (plugin key l10nfr) into the Marketplace. I’m not its current maintainer, so I’m asking you to decide whether the entry can move to the fork I now maintain.
Where the entry stands
The latest public version is 10.0.0, released 2023-06-02 from jycr/sonar-l10n-fr. l10nfr.properties marks it compatible with SQCB [24.12,LATEST] and SQS [10.8,LATEST].
Of the 8,438 messages Community Build 26.10 ships, 10.0.0 translates at most 3,448 (41%). It also still uses positional arguments ({0}) where the web app now passes named ICU arguments, so placeholders show up as-is on screen (jycr/sonar-l10n-fr #41, #42, #44).
The last commit on main is from 2023-06-23. The SonarCloud project linked from its README (jycr_sonar-l10n-fr) no longer exists.
What I tried first
2026-09-15: issue jycr/sonar-l10n-fr#47, with a diagnosis and an offer to contribute.
2026-09-15: PR jycr/sonar-l10n-fr #48, CI green, linked from #47.
In #47 I set a deadline of 2026-10-15 and said I’d release from a fork after that. Neither the issue nor the PR got a reply.
To be fair to jycr: he’s active on GitHub elsewhere, so the repository is dormant but its owner isn’t unreachable. I’m pointing him to this thread from #47. If he replies, I’ll go with what he prefers, including leaving the entry where it is.
The fork
Sonar-l10n-FR/sonar-l10n-fr, with the full history. The plugin key (l10nfr), Maven coordinates (org.sonarqube.l10n.fr:sonar-l10n-fr-plugin) and license (LGPL-3.0) are unchanged.
It’s hosted in a GitHub organization created for the pack, Sonar-l10n-FR, rather than in a personal account. The entry has lived in three places already (SonarCommunity, ZoeThivet, jycr), and each move changed every URL. With an organization, the next handover only means adding a maintainer, and jycr is welcome to join it.
Release 26.10.0, with release notes, jar and SHA-256. It’s published by a tag-triggered workflow that runs the test harness first.
On Community Build 26.10.0.133078, 8,297 of the 8,438 catalogue messages have French. The other 141 read the same in both languages (product names, acronyms) or aren’t UI text.
Sonar-Version floor: 9.14.0.375. The plugin only implements org.sonar.api.Plugin.
I’ve only verified it on Community Build, so the release has no sqs range.
What I’m asking
Update-center PR: SonarSource/sonar-update-center-properties#960. It adds 26.10.0 with sqcb=[26.10,LATEST], ends 10.0.0’s sqcb at [24.12,26.9.*] so the public ranges don’t overlap, and points homepageUrl at the fork. It passes the mojo’s validateOnly check.
The entry has changed hands before: it moved from ZoeThivet/sonar-l10n-fr to jycr/sonar-l10n-fr in update-center PR #371 (2023). That move was a repository transfer, though, and this one would be a fork, which is why I’m asking here rather than just sending the PR.
If you’d rather give the maintainer more time, or handle this some other way, I’m happy to go along with that.
I am the current maintainer of the FR pack. I took over from @Zoe_Thivet several years ago, who transferred ownership of the repository to me. Like Zoé back then, I am now working in a completely different activities, and I am no longer able to dedicate the time required to maintain this repository.
It is now time for me to “pass the torch”. Transferring it to an independent GitHub organization—one not tied to any individual’s personal account—is the action to ensure the long-term viability of this pack.
Thank you, jycr, and thank you for keeping the pack alive all these years.
The organization is ready: Sonar-l10n-FR. To move the original repository there with its history, issues and releases, the simplest path I see is:
You transfer jycr/sonar-l10n-fr to my account, Greenystuff (Settings → Danger Zone → Transfer ownership). I accept it and move it into the organization.
Beforehand I move the current fork out of the way so the name is free, then bring its commits, tags and the 26.10.0 release into the transferred repository. The final URL stays Sonar-l10n-FR/sonar-l10n-fr, so the update-center PR doesn’t need to change, and GitHub keeps redirecting the old 10.0.0 download links.
If you’d rather transfer it straight into the organization, I can invite you instead, and you’re welcome to stay a member. Just tell me which you prefer.
Je fais des belles réponses avec mon agent mais si vous voulez faire une conv ou autre pour faire connaissances, n’hésitez pas ! J’aime aussi beaucoup parler avec des confrères techniques et passionnés ! Voilà pour un peu de message humain quand même
Hey there @Greenystuff and @jycr, if you want me to open a private message thread between you two here in the Community Forum, let me know. Normally we restrict private messages to users with a higher maturity level to avoid spammers, but if you prefer to communicate over here rather than over Linkedin, I can do it.
Hey @Greenystuff, it’s not a problem that you discuss via this public thread. It’s just that since I saw you going over to private messages on LinkedIn, I wanted to offer if you wanted to instead have private messages over here. But since you’re already in touch, I’ll let you continue over LinkedIn, no problem. And thanks for taking over the language pack plugin!
Thanks andres, for the offer and for the kind words, and to you jycr for the handover. We sorted it out over LinkedIn, and the transfer is done.
The original repository is now Sonar-l10n-FR/sonar-l10n-fr, with its full history since 2012, its issues and its releases, and old jycr/sonar-l10n-fr links redirect there. The 26.10 work is on main, release 26.10.0 is published from the original repository with the same jar, and the SonarCloud analysis runs from it with a green quality gate. The temporary fork is gone.
For the Marketplace, the update-center PR is ready as it is: both download URLs resolve, 26.10.0 from the new location and 10.0.0 through GitHub’s redirect. Whenever someone on the Marketplace side has a moment to review it, that would be great.
Voilà pour un peu de message humain quand même 