Sure, but these are English words. I don't think anybody argues that it should be an issue to _everyone_, perhaps you. But you seem to suggest that it shouldn't be an issue to _anyone_ because it isn't an issue to many people. I don't think that works either. Ex: if someone proposed a fix to the Chinese translation strings in an app, would we say this is merely China-centric? I'd also suggest framing this as "some people's personal issues" is dismissive, but maybe the choice of words wasn't meant that way. (again, I think we'd never say, who cares about the Chinese translation? that's just their personal issue.)
I read between the lines that you view this is as just some US English speaker pet issue, so people like me must just not be global-minded. I think the backgrounds of people you're interacting with here might surprise you! Constructively: what do you mean by specialists and 'blindly renaming'? like, we shouldn't just pick a rename but go with some well-accepted alternative name? That would be great to add as input here. If a rename isn't a solution -- and yes, nobody thinks this single-handedly fixes social problems -- what would be a better one? The compatibility concern is very much important. But I think you'll see the proposal is not to break compatibility. Your review and input on that technical dimension is valuable. On Tue, Aug 4, 2020 at 10:11 AM Alexander Shorin <kxe...@apache.org> wrote: > > Hi Sean! > > Your point is good and I accept it, but I thought it worth to remind yet > again that ASF isn't limited by the US and the world is not limited by > English language and as the result shouldn't be limited by some people's > personal issue - there are specialists around who can help with these. > > P.S. Sorry if my response was a bit quite disrespectful, but the intention > was to remind that blindly renaming all the things around is not a solution - > let's think world wide or at least about compatibility issues which somehow > should be handled? And what will be motivation for people to handle them? > --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
