On Wed, Oct 26, 2022 at 11:59 AM 'Alina Strohaya' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote:
> I'm kind of surprised that you said this about maintenance, because if > it's in OSS, and gets outdated, or people notice something they want to > improve, they can file a PR and add to it. The community can review and > assist. On an article on this kind of site, I'm the sole author. If I don't > maintain or update it, no one will, it's just me. > True in the general case, but translations might be special in that a relatively small group (contributors and reviewers) becomes even smaller (contributors and reviewers fluent in a specific language). Additionally, neither many contributors nor the majority of users will be able to even identify content problems, and if they're identified, getting them addressed other than just deletion is a new challenge. When KK merged anonymously contributed translations without review, there was some embarrassing nonsense <https://github.com/jenkinsci/jenkins/blob/ea724ab13dd3b55d41902fd723f788de080fd4d3/core/src/main/resources/lib/hudson/buildCaption_oc.properties> included in Jenkins for several years. In general, we've not had great experiences in the past with bigger translation projects specifically. https://plugins.jenkins.io/localization-zh-cn/ , for which there's an entire JEP, has had two contributions and no releases in the last two years. Two other contributors wanted to go this route in core PRs #4306 and #4775 (first step: delete all translations that already exist…), and there was very little followup when we suggested they start contributing regular translations first. The Chinese localized version of jenkins.io is badly outdated: https://www.jenkins.io/zh/changelog-stable/ is probably the most easily understandable example. In the case of a localized tutorial, it is unclear what would need to be done when the source text is substantially updated. In core, we generally delete affected translations, resulting in a fallback to the updated English text for a few more strings on the UI, and IIRC there've been some interesting discrepancies when we didn't do that. Deleting an entire tutorial doesn't seem practical. I absolutely do not want to discourage you from contributing translations! As a project we need to consider how this plays out long-term, including after you've moved on or lost interest. If you have suggestions how we would navigate that, it'd make your proposal much stronger. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKwDRqcOZe-79961LG_ah7_DJhQnNNQcg3zuCgEi6jVeg%40mail.gmail.com.
