GNOME To Start Using Codenames
prisoninmate writes: A discussion between GNOME developers and users during the annual GUADEC conference lead to potential code names for the desktop environment, starting with the upcoming September release, GNOME 3.18, which might be dubbed Gothenburg. They decided to codename the September releases after the city where the GUADEC conference took place, as explained above, and the March releases after the city where the GNOME.Asia Summit will take place.
So we won't know it's Gnome until the release?
Very, very, sneaky!
I suggest the first code name be "Zurich"; my second choice is "Gringott"... don't tell anyone, we wouldn't want them knowing we were talking about Gnome!
So glad they sorted out all the other issues and devoted time to what really matters.
Only the State obtains its revenue by coercion. - Murray Rothbard
Switching to codenames seems unnecessary. Version 3 was completely unrecognizable as Gnome already.
There are two screenshots that will show you everything you need to know about GNOME 3 and the disaster that it has been.
The first screenshot shows Gedit, a simple graphical text editor for the GNOME environment. This is what it looked like prior to the GNOME 3.
The second screenshot also shows Gedit, but as part of GNOME 3.
Yes, that's right. GNOME 3 somehow managed to completely fuck up the UI of something as basic as a simple graphical text editor. It took a program that was usable, and turned it into a monstrosity. It took a desktop environment that was usable, and turned it into a monstrosity.
It could have been worse. Fedora 19 was the "Schrödinger's Cat" release, and it broke number of software installation tools . Many old scripts in bash, ruby, or perl would read "/etc/issue.net" or "/etc/fedora-release", and now had to parse the Unicode content with a single quote and two text words embedded in the text. For many old, simply written shell scripts, in particular, it broke them _very_ badly.
For many of us, Fedora 19 was known as the "Bobby Tables" release. ( https://xkcd.com/327/ )
When I first got into computers, the startup sequence was hard-coded into the kernel, as was the command shell. The idea of plug-replaceable shells and filesystems came later, along with customizable startup sequences and other buffet-style services.
I'm beginning to feel like we've stopped moving forward and have started moving backwards.
It had to be said.. Yes, I know, Fedora patches and urxvt (I even maintain a branch with text shadow and transparency), terminator, etc. But come on and include something at least on par with MacOS's terminal. I do love the quake-like terminal plugin for gnome shell and it does transparency without a hitch. Out of box matters and people do want something equivalent to MacOS or hell even Cygwin's mintty. The rest of Gnome / Gnome Shell are doing pretty well except I think Tweak Tool should be a default as well. Otherwise I appreciate the project all together and use it daily once I configure it heavily. The project needs to listen a bit more to its users it definitely could easily make many more people happier with it that way.
Quite true.
Unfortunately a lot of projects pick overly clever code names and get themselves all tangled up with existing popular search terms, to the detriment of both.
...and easy to understand. Obviously they have no place in GNOME.
Sabbotaged, Cantshutdown, Removefunctionality, Singlepanefile, Cinnamonh8tr, Activiteslongword, Formoverfunction, Lostourway.
https://www.youtube.com/c/BrendaEM
After Gnome 3, it's completely understandable that the developers would want to switch to code names. Using their real names probably made it too easy for disgruntled users to track them down.
But then the software that broke was obviously broken, so this was a good test to catch them and fix them.
I feel the need to reply "me too" here, just so that perhaps some people not reading score 0 comments (since, by default, they're not shown) will see your post.
Damn Slashdot and its war on Anonymous Cowards.
Because a code name makes everything better.
I just read the discussion over su reimplementation in systemd, Funny how people insist that old [UNIX] code is not broken and any evidence of contrary are met with denial.
I hope they can pronounce it. It's s.t. like [yotebur], at least that's what I recall from when I was there ten or twelve years ago. If English speaking people pronounce it the way it's spelled, the Vikings may start raiding our coasts.
Ok, just found it in the Wikipedia article, and it's [jtbrj]: that's a front rounded vowel in the first syllable, and a sort of [i] ('ee') on the end. I guess my pronunciation was/is pretty bad. But not as bad as it would be if I tried to use the spelling (and my English pronunciation) as a guide.