Live data from Hacker News

End of Japanese community

support.mozilla.org

151–160 of 820 posts

Re: End of Japanese community

#151
post #101
post #72

Earlier quoted context omitted.

I can imagine what you mean, but since I am not in Japan, it would be interesting why you feel that way.

long and slow consensus building that weighs existing stakeholder's opinions heavily vs doing "the right thing" from the outset. So you move slowly and end up having very annoying conversations and compromises instead of just pushing something through. And the formal process is just a formality anyways, so then anyone not in the informal chatter just gets to experience the capriciousness anyways The sort of consensus…

Move fast and break stuff didn't work out much better though.

Re: End of Japanese community

#152

Earlier quoted context omitted.

But he lists the problems? Pretty unambiguously.

The problems are nowhere near actionable. A lot more information is needed. E.g. literally the first bullet: "It doesn't follow our translation guidelines". OK -- where are those guidelines? Is there a way to get it to follow them, like another commenter says works? Does the person need help following the process for that? Or is there a bug? Etc. These are the things a call can clarify. It's the necessary first step,…

Turning off the machine translation and reverting all the changes it made seems pretty actionable to me. They can turn it back on when issues are addressed.

Re: End of Japanese community

#153

Earlier quoted context omitted.

> It sounds like Mozilla just turned on the machine without consulting the human translators to see if the machine actually worked in a useful manner. Yes. And someone should make a real apology. But learning what the machine did wrong is part of fixing a machine.

Yes, that's why you engage with the people doing the work first and run it on a staging environment to see what would be overwritten. You test until it's working well enough to enhance the effort done by the translators.

And the fact that they didn't strongly suggests that they knew.

Re: End of Japanese community

#154

Earlier quoted context omitted.

But he lists the problems? Pretty unambiguously.

The problems are nowhere near actionable. A lot more information is needed. E.g. literally the first bullet: "It doesn't follow our translation guidelines". OK -- where are those guidelines? Is there a way to get it to follow them, like another commenter says works? Does the person need help following the process for that? Or is there a bug? Etc. These are the things a call can clarify. It's the necessary first step,…

They are actionable by entirely canceling the machine translation operations in that community,

Re: End of Japanese community

#155

Earlier quoted context omitted.

My guess would be the anger comes from implication that is a possible solution at all. This type of “hop on a call” request is not usually actually designed to “truly understand what you're struggling with.” (words from the post) Instead it is usually a PR tactic. The goal of the call requester is to get your acquiescence. Most people are less likely to be confrontational and stand up for themselves when presented wi…

Are we reading too much into one sentence? HN comments dese days

No, we aren't.

It was this exact part of the conversation that touched me negatively too. marsf expresses some very valid criticism that, instead of being publicly addressed, is being handled by "let's discuss it privately". This always means that they don't want to discuss, they just want to shut you down.

Re: End of Japanese community

#156
post #101

Earlier quoted context omitted.

long and slow consensus building that weighs existing stakeholder's opinions heavily vs doing "the right thing" from the outset. So you move slowly and end up having very annoying conversations and compromises instead of just pushing something through. And the formal process is just a formality anyways, so then anyone not in the informal chatter just gets to experience the capriciousness anyways The sort of consensus…

Move fast and break stuff didn't work out much better though.

Yeah sure, I feel like back channeling stuff is generally just the respectful thing to do, so I'm not on the side of the debate I'm expanding upon in most cases.

Just that lacking context one really can't make that many blanket statements.

Re: End of Japanese community

#157
post #133

Earlier quoted context omitted.

I’m not sure those who speak like that are equipped to understand how offensive their words and tone can be. It suggests a decision can be reversed with a quick call, which questions one’s choices or conviction. As if to suggest the choice was made without considerable thought and care. It’s such an unserious tone to a moment that’s very serious to the other.

I think it's because it's almost never accompanied by "we may have fucked up, please help us understand how to fix it now and in the future". It's almost always (like this time) "I'm sorry you feel that way, please spend more of your free time ", and sometimes (like this time) "[we're doing it anyway but maybe we'll make some changes]". It feels insulting because it is insulting. The decision has been made, they just…

Changing the medium to a private conversation also means not committing to any decision publicly for as long as possible. It feels like damage control and protecting your own image (the person posting with respect to their company) as opposed to addressing the real issue promptly and transparently.

Re: End of Japanese community

#158
post #133

Earlier quoted context omitted.

I’m not sure those who speak like that are equipped to understand how offensive their words and tone can be. It suggests a decision can be reversed with a quick call, which questions one’s choices or conviction. As if to suggest the choice was made without considerable thought and care. It’s such an unserious tone to a moment that’s very serious to the other.

I think it's because it's almost never accompanied by "we may have fucked up, please help us understand how to fix it now and in the future". It's almost always (like this time) "I'm sorry you feel that way, please spend more of your free time ", and sometimes (like this time) "[we're doing it anyway but maybe we'll make some changes]". It feels insulting because it is insulting. The decision has been made, they just…

Another reason in context of public forums is that it's dismissive of any concerns or questions raised: If a call would be sufficient, that implies they think that nobody else cares.

Re: End of Japanese community

#159

Earlier quoted context omitted.

The problems are nowhere near actionable. A lot more information is needed. E.g. literally the first bullet: "It doesn't follow our translation guidelines". OK -- where are those guidelines? Is there a way to get it to follow them, like another commenter says works? Does the person need help following the process for that? Or is there a bug? Etc. These are the things a call can clarify. It's the necessary first step,…

> where are those guidelines? It's entirely possible that such information is well-known to everyone involved in the translation community. I would consider it outright insulting if someone who ostensibly "wants to help" doesn't know basic information like that - if the people making decisions about SumoBot are NOT aware of basic information like "where to find the local translation guidelines" then they are presumab…

Yep agree with this. Nothing is more infuriating than someone Kramering into a space trying “to help” without spending any time or effort trying to understand that space.

They should have understood the guidelines before turning on their machine translation in a given locality.

Re: End of Japanese community

#160
post #133

Earlier quoted context omitted.

I think it's because it's almost never accompanied by "we may have fucked up, please help us understand how to fix it now and in the future". It's almost always (like this time) "I'm sorry you feel that way, please spend more of your free time ", and sometimes (like this time) "[we're doing it anyway but maybe we'll make some changes]". It feels insulting because it is insulting. The decision has been made, they just…

At some point, "quick calls" are used for discussions that they don't want a trace of. So, even in the best "sorry we screwed up" scenario, the quick call covers their butt and let them leeway to backtrack as needed. That's also part of why we viscerally react to opaque meetings IMHO.

oh yes, completely agreed: https://news.ycombinator.com/item?id=45831721
Post reply on HN