I’d like to contribute to the localization of GeoServer, specifically the Hungarian one, but as I logged into the OSGeo Weblate I realized that all GeoServer module translations are locked due to a repository conflict. (As far as I can tell it has been in this state for a few months now.)
Does anybody know anything more about this? Where would be the proper place to report this to the Weblate admins?
I know the weblate is not exactly an “end user” matter, but I feel it’s also not strictly a developer topic, so sorry if I’m posting in the wrong category.
I am the administrator of the weblate project and indeed I have to make a big check of the configuration to match the recent changes in the GeoServer repository. I will try to find some time this week to unlock the whole thing.
If you or the core team are currently overloaded with adjusting the upstream sync configurations or resolving the recent repository structural mismatches between GeoServer and Weblate, I would be glad to lend an extra pair of hands to help debug and automate this workflow.
I specialize in DevOps pipelines, custom Python automation scripting, and Git workflow architectures. I can help you look into the Webhook configurations, automated branch syncing, or look over the repository hooks to ensure that future upstream updates won’t cause hard locking issues for the localization modules.
You can check out some of my automation scripts, deployment infrastructure layouts, and general code quality directly in my portfolio repository on GitHub: Bohdan Betskov Portfolio on GitHub.
Feel free to drop me a direct message (DM) here on Discourse if you want to offload some of these configuration chores and get the Hungarian and other translation modules unlocked for the contributors sooner!