GIMP open source image editor forked to fix 'problematic' name - Surprisingly, Dale Emhke nowhere to be seen.

  • 🏰 The Fediverse is up. If you know, you know.
  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account

Release the GIMP: Glimpse project founded to avoid branding that some find offensive
By Tim Anderson 28 Aug 2019 at 13:50
191 Reg comments SHARE ▼
GIMP is capable open source software, but is the name a barrier to adoption?

GIMP is capable open source software, but is the name a barrier to adoption?
Interview Glimpse is a fork of the popular open source image editor, GIMP, created primarily to offer the software under an alternative name.
GIMP is a longstanding project, first announced in November 1995. The name was originally an acronym for eneral Image Manipulation Program but this was changed to GNU Image Manipulation Program.
The new fork springs from a discussion on Gitlab, where the source code is hosted. The discussion has been hidden but is available on web archives here. A topic titled "Consider renaming GIMP to a less offensive name," opened by developer Christopher Davis, stated:
I'd like to propose renaming GIMP, due to the baggage behind the name. The most modern and often used version of the word "gimp" is an ableist insult. This is also the colloquial usage of the word. In addition to the pain of the definition, there's also the marketability issue. Acronyms are difficult to remember, and they end up pronounced instead of read as their parts. "GIMP" does not give a hint towards the function of the app, and it's hard to market something that's either used as an insult or a sex reference.
The proposal was supported by another developer, Leonora Tindall, who noted that "I have, on two occasions now, recommended this program to photography and graphic design educators (as an alternative to Photoshop) who told me that they considered it and found it good as software but weren't permitted by their institution to use it in the classroom because of the name."
Others opined that changing the name of long-established software would hurt its recognition and usage. The discussion became bad-tempered and caught the attention of Bobby Moss, whose day job is a technical writer at Oracle.
"I'm a long-standing user of the project," he told The Reg. "I saw the abuse and unpleasant things being said to Chris. It was decidedly not cool and not how we should make decisions in free software. I also thought the arguments he made were well reasoned, not focused so much on the offensiveness of the name but on the marketability of the application."
Moss therefore forked the project into a new one called Glimpse.
"Initially I thought it was just going to be a quirky project on my own private GitHub but people expressed enthusiasm for it. It's evolved now into this new thing where you’ve got multiple people running it, myself, Chris who originally posted the issue, and another woman called Clipsey … it's all kind of ballooned out from there."
The subject of the suitability of the name is not new, and is enshrined in the official FAQ:
"I don't like the name GIMP. Will you change it?"
With all due respect, no. We’ve been using the name GIMP for more than 20 years and it's widely known … on top of that, we feel that in the long run, sterilization of language will do more harm than good. … Finally, if you still have strong feelings about the name "GIMP", you should feel free to promote the use of the long form GNU Image Manipulation Program or maintain your own releases of the software under a different name.
The Glimpse project is therefore entirely within the spirit of open source. "We believe free software should be accessible to everyone, and in this case a re-brand is both a desirable and very straightforward fix that could attract a whole new generation of users and contributors," says the About page.
The team wish to continue using the upstream GIMP project libraries and are asking for donations to GIMP as well as Glimpse.
The developers are planning more than just a name change, including a "front-end UI rewrite" according to an update posted a week ago. The team is looking at screenshots of existing image editing application user interfaces to inform design mockups. There is also a discussion about language choices. Rust with GTK (Gnome Toolkit) bindings, perhaps? C++ and Qt?
Changing the user interface is more challenging than changing the name. We wonder if it is all a little too much to take on?
It is "a long-term plan, maybe a few years down the road," says Moss. "It's something people are looking at in parallel. The main focus at the moment is just tracking the upstream releases, and making changes to them. When we hit GNU image manipulation program version 3, they'll have completed their port to GTK 3, and that's where we are looking to do a hard fork and can start getting more ambitious with user interface changes.
"A lot of the functionality is actually in a set of libraries. Those components would still be used and any changes we made to them would be contributed back.
"Even if our project falls flat on its face, at least we've brought new people and new interest to a code base that's been out for a while and probably needs a bit more love from the community than it currently enjoys." ®
 
Of course, he's from Portland.

He strikes me as the kind of man who wiles away his evenings in a gimp suit, shackled to a ring in the corner of his bedroom, while his wife and her boyfriend try for another baby.
He was the only one working on the project and blamed lack of participation on ... the pandemic

https://glimpse-editor.org/posts/a-project-on-hiatus/ massive cope here

Contrary to what some of our critics would have you believe, our project is not run by “woke warriors offended on behalf of disabled people”. Disabled people were always involved at all levels of the project, and marginalized communities are well represented because of our project’s origins on the fediverse and welcoming internal culture.

Unfortunately, as you might imagine, a global health emergency with an economic recession following in its wake has hit our contributors disproportionately hard. This meant that they were no longer able to commit as much time towards the project as they did previously.

By the second half of 2020, there was just me (Bobby Moss) and a couple of external contributors working on the fork itself. Our other remaining project contributors were occupied with trying to start the UI rewrite called “Glimpse NX” as we had previously planned.

Our problem was not a lack of financial contributions or users, because the project was still growing in those areas. Our main issue was that we could not find contributors willing to step up and help with non-code tasks like moderating communication channels, triaging bugs, fixing packaging problems, working with the GNU Image Manipulation Program contributors, monitoring our social media accounts, running servers, testing/documenting new releases, and answering questions that users reached out to us with. As a result, we struggled to scale the project to match increasing demand.

Evil empire Oracle was concerned he was spending too much time on it lol
With that in mind, I (Bobby Moss) should explain why I left the project in February 2021.


The number of gaps I had to fill by August 2020 effectively turned working on this project into an unpaid part-time job for me in addition to my paid full-time job. Frustratingly, I had so much support work to manage that I rarely had enough time to actually work on the fork itself. This is why I made plenty of progress towards Glimpse Image Editor 0.2.2, but never actually released it.

I had originally expected the situation I was in to be temporary, and last for around six months. Unfortunately, by that stage our project was still struggling to move forward without my constant and direct involvement.

My employer had been keeping a close eye on my participation in the Glimpse project since it began, and had started to raise concerns that if I took on many more responsibilities within the project, it might begin to impact performance on my day job. In addition, there had been some changes in company policy that required me to seek legal approval and formally confirm that there have never been any conflicts of interest.

On their advice I temporarily withdrew my participation in the Glimpse project, with the expectation of returning once I had the proper approvals in place and a solid plan to make the project much more sustainable and maintainable ongoing. Unfortunately by the time I started to plot my return ten weeks later, almost all project activity had ceased, and I had neither the time nor the energy to resurrect it alone in the middle of a pandemic.

However, I was concerned that the Glimpse project was still receiving donations and attracting new users despite this situation, so I reached out to Chris and Luna for permission to publish this blog post, and helped them take the right actions to safeguard Glimpse Image Editor users and supporters.
 
Isn't this like the 2nd or 3rd time someone has tried this? And surprise surprise, every other attempt was made up of people who didn't do any work to begin with. (literal outsiders with no experience or ability what so ever who first tried to get the devs to change it before hand)
 
Isn't this like the 2nd or 3rd time someone has tried this? And surprise surprise, every other attempt was made up of people who didn't do any work to begin with. (literal outsiders with no experience or ability what so ever who first tried to get the devs to change it before hand)
apparently it comes up every few years to the GIMP developers, who every time say no. this time caused more of a fuss but still nothing happened to the original project.
 
Back
Top Bottom