Hacker News Reader

Comment by dngray | Hacker News Reader

without naming names I see a lot of SJW in that issue without very many commits/participation in the open source community.

Also the maintainers gave their reply as it is their prerogative to do so.

> Michael Natterer @mitch · 5 hours ago Maintainer

> Sorry, the name will not change, closing. Michael Natterer @mitch closed 5 hours ago

So JordiGH, you needn't re-open the issue https://gitlab.gnome.org/GNOME/gimp/issues/3618 and post to HN with the hopes of generating outrage against the GIMP project for not doing what you want.

View on HN

I have to agree. Please, everyone, if you're going to engage with this, look at https://gitlab.gnome.org/GNOME/gimp/issues/3617 and the discussion (and lack thereof) there.

As someone who likes to think that I do have as many "commits/participation" as many others, I would appreciate it if people would focus on the core argument:

It is hard to get people to use this software, who would otherwise benefit, because of their perception of the name, and it's easier to change the name once than change those perceptions every single time.

If you have problems with THAT, I'd love to discuss them, but please leave "SJWism" and whatever out of it - that's not really what's at issue here.

> As someone who likes to think that I do have as many "commits/participation" as many others, I would appreciate it if people would focus on the core argument

The reason this is important is because in recent times essentially nobodies like to pop out of the woodwork with "ideas" like this. They then like to "shame" people who don't agree with them. There's nothing wrong with expecting people to build up a reputation before suggesting divisive and controversial ideas.

If you do a google search for GIMP you literally get no references to the slur.

Almost all of the things I post to HN get buried and are never seen. Have a look through my submissions:

https://news.ycombinator.com/submitted?id=jordigh

The fact that this one was seen indicates that there is an issue here.

I didn't create the issue. I am only drawing attention to it. If the issue weren't a problem, it wouldn't even be possible to draw attention to it.

> Almost all of the things I post to HN get buried and are never seen. Have a look through my submissions: https://news.ycombinator.com/submitted?id=jordigh

> The fact that this one was seen indicates that there is an issue here.

That would have been because it was showing up under /newest. There was probably a small amount of upvotes coming from the link back from the gitlab issue.

> I didn't create the issue. I am only drawing attention to it. If the issue weren't a problem, it wouldn't even be possible to draw attention to it.

No, you opened the duplicate issue after the first one was closed (not locked) by the maintainer.

I didn't link to my duplicate issue and you're really fixated on that particular line of attack. I linked to the original issue, both here and on Lobsters. The duplicate issue was quickly locked and forgotten.

I meant "I didn't create the issue" in the sense that it's not my fault that people want to change Gimp's name, not "issue" as in "id number in Gitlab". You can thwart this particular barbarian at the gate and feel content that if you attack me the question of Gimp's name is settled, until the next barbarian comes along, but there's a lot of barbarians and you'll probably be fighting this war for many years to come as long as you and other Gimp developers decide to dig in their heels and die on this hill.

So now that the original issue has been deleted, not even locked, you agree it's reasonable to open it again? Where else can this discussion continue?

Reply on news.ycombinator.com