End of Japanese community | SUMO community discussions | Forums

Hi marsf, I’m so sorry to read your message. Even though we haven’t seen each other for a while, I still have fond memories of you (we last met at All Hands in Orlando… in 2018).
I completely understand your frustration after the introduction of SumoBot. We Italians, along with the Spanish, were the first to experiment with automatic translation/updates via SumoBot (https://support.mozilla.org/en-US/forums/contributors/717387?last=89505), and I’ve already expressed some concerns. I hope that, after talking with Kiki and the staff, you’ll change your mind about ceasing your localization contributions.

marsf said

• It doesn’t follow our translation guidelines.

Fortunately, for the Italian localization, our guidelines are being respected.

• It approves its direct English MT immediately for All archived KB articles.
• It approves only in 72 hours after its updates, so we lost our work to train new contributors.
• It has been working now without our acceptance, without controls, without communications.

These are also in my opinion the sore points, especially the fact that SumoBot updates or translates (when there’s a new article) immediately, which hinders the training of new contributors because they end up doing “proofreading” since SumoBot immediately takes over…
For me, as a locale leader, it’s not easy to help a new contributor understand how the localization process works, the syntax of the Sumo wiki, if they have to view a “diff” that SumoBot has already automatically proposed (Often retranslating parts of the article that aren’t subject to changes…).

I believe the various locales should be able to decide whether or not to use machine translations, especially if we want to involve new contributors. In the last few months, I’ve trained two new contributors, but since the introduction of machine translation and on-the-fly translation, they’ve lost interest, and I spend my time alone (As always) fixing SumoBot’s intrusiveness.

Hugs,
Michele

Hi marsf, I’m so sorry to read your message. Even though we haven’t seen each other for a while, I still have fond memories of you (we last met at All Hands in Orlando… in 2018).
I completely understand your frustration after the introduction of SumoBot. We Italians, along with the Spanish, were the first to experiment with automatic translation/updates via SumoBot (https://support.mozilla.org/en-US/forums/contributors/717387?last=89505), and I’ve already expressed some concerns. I hope that, after talking with Kiki and the staff, you’ll change your mind about ceasing your localization contributions.

”marsf [[#post-89603|said]]”

• It doesn’t follow our translation guidelines.

Fortunately, for the Italian localization, our guidelines are being respected.

• It approves its direct English MT immediately for All archived KB articles.
• It approves only in 72 hours after its updates, so we lost our work to train new contributors.
• It has been working now without our acceptance, without controls, without communications.

These are also in my opinion the sore points, especially the fact that SumoBot updates or translates (when there’s a new article) immediately, which hinders the training of new contributors because they end up doing “proofreading” since SumoBot immediately takes over…
For me, as a locale leader, it’s not easy to help a new contributor understand how the localization process works, the syntax of the Sumo wiki, if they have to view a “diff” that SumoBot has already automatically proposed (Often retranslating parts of the article that aren’t subject to changes…).

I believe the various locales should be able to decide whether or not to use machine translations, especially if we want to involve new contributors. In the last few months, I’ve trained two new contributors, but since the introduction of machine translation and on-the-fly translation, they’ve lost interest, and I spend my time alone (As always) fixing SumoBot’s intrusiveness.

Hugs,
Michele