Yesterday, the Fedora Project released Fedora 21, and with it the tech media got on its proverbial horse and started reports and reviews of the latest release. While it’s a good release and we won’t be reviewing it here — I already gave it a shakedown during the alpha and found it to be fantastic and completely worth the wait — there’s one thing that’s missing from Fedora 21 that I find rather disheartening.
Namely, Fedora 21 is missing a release name.
It’s quirky, perhaps, but release names are a favorite item of mine in the FOSS realm. While completely useless in the scope of the software itself, it does actually reflect a degree of creativity within the respective communities. Depending on the how it’s done, the decision process ranges from a spirited event to a tried-and-true yawner.
Until Fedora 21, the Fedora Project used to have a process for release names in which knock-down drag-out brawls would break out, rhetorically speaking, in the debate and community-wide voting for the name. Arguably, Fedora 17 “Beefy Miracle” wobbled the process from the rails, and while the rest of the names were noble — my favorite was Fedora 19 “Schrodinger’s Cat” — the formula was fairly simple: Names had to meet a “is-a” test. For example, “Schnozz is a ____, and so is Keister.” Taking the example of naming Fedora 14 “Laughlin,” the Fedora Project took the name of Fedora 13 “Goddard” and, though the miracle of the “is-a” test, had a list of candidates, of which Laughlin won. So the formula is as follows: “Robert H. Goddard was a professor of physics, and so was Robert Laughlin.” To see this in action, you can look at the Fedora Release Name History.
Reglue and our project before it,The HeliOS Project; has been a long-time user of Mint…and not for any other reason than it fits our needs. As my friend Eric Johnson says:
And the beat goes on…
While we in the States were dealing with family and turkey, the EU was busy working on preparing Google’s head for the platter. The European Parliament yesterday passed by a wide margin a non-binding resolution urging anti-trust regulators to break up the company. For those keeping score, the final vote was 384 yeas and 174 nays.
In comes a castoff ThinkPad T500 from a friend in Seattle and I’m now in the 64-bit club.
It also seems to fit with one of the underlying philosophies of the distro. Mint is famous for being a desktop that anybody can use. Updates on the dash is a concept which a new-to-Linux Windows’ user can understand, maybe even without having to go to the forums for help — and a piece of cake for experienced free software users. In my case, the only problem I had is that I misunderstood the severity numbering scheme, figuring one to be most severe instead of the least, but I easily managed to patch and update my system.
A biennial tradition in the San Francisco Bay Area, MeetBSD 2014 uses a mixed unConference format featuring both scheduled talks and community-driven events such as birds-of-a-feather meetings, lightning talks, and speed geeking sessions. MeetBSD can be traced back to a local workshop for BSD developers and users, hosted annually in Poland since 2004. Since then, MeetBSD’s popularity has spread, and it’s now widely recognized as its own conference with participants from all over the world.
Here’s what I want to know. Is replacing a well known application in Linux with a crippled version acceptable when it’s done in the name of stability? I’ll go ahead and place myself in front of you for scorn and castigation by admitting that I’ve been a member of the Slashdot community since 2002. Everyone has a sig line, right? Mine was thoroughly honed to be as concise a possible: