Tom, I Can Name That Distro in Two Notes
Everybody loves the wild and wacky names that end up gracing releases of the various Linux distributions throughout the year, even if some of them — we're not going to name names, that might hurt our karma — have gotten a bit more bizarre of late. Among the more interesting processes for picking release names comes from the Fedora Project, where unlike most other distributions, the new name must share a unique link to its predecessor. Its time then to put your thinking caps on, as the race to make that most creative of links is underway.
The method for choosing the the nom de plume for the behatted distro is deceptively simple: The new name must share a link to the old name, and that link must follow the pattern "X is a Y, and so is Z." An example, from the last Fedora name contest: "Cambridge was a ship of the Union Navy, and Leonidas was too." Cambridge (X) was the preceding release name, from Fedora 10, Leonidas (Z) was the winning submission, and the connection between the two was that both were ships in the Union Navy (Y).
Some interesting appellations have been bandied about so far, including our favorite: Ahasuerus was a King present at the Battle of Thermopylae played by Richard Egan in a film, and Leonidas was too. One kink in the system, and the source of our description of the process as deceptively simple, is that obvious links, like "is a place" or "is a word" are disqualified, with preference being given to obscure commonalities referencing interesting topics. The link must be legitimate, it cannot be the same link that was used to pick any previous release name, and perhaps the greatest obstacle, it must be eligible for trademarking. Submitters are obligated to perform a cursory Google search to determine any obvious collisions, while the Red Hat legal department conducts an in-depth investigation before approving the nominations.
The ultimate decision on the new name is left to the Fedora community, though the Fedora Board pre-screens the list to eliminate obvious, illicit, uncreative, or otherwise undesirable before passing it to Red Hat's legal team to slice and dice with the Patent & Trademark Office. The final list, free of thorns and fresh from the lawyers will be presented to the Fedora community for a vote, after which the formal announcement of the new name will be made. Submissions are open through May 23, with vetting by the Board and legal eagles from May 24 through June 8, and the community vote commencing on June 9. The final day of voting will be June 22, with the final name to be announced on June 27.
Submissions are welcome from any member of the Fedora community, provided the have performed the obligatory search and can justify the "is a" link between the two names. Nominations should be made on the Fedora 12 naming page on the Fedora wiki — those seeking a bit more guidance can find the full rules of the process there as well, and anyone looking for past links may find the history of Fedora release names an interesting read.
Justin Ryan is News Editor for LinuxJournal.com.
Submit a tip: Email IRC
Justin Ryan is a Contributing Editor for Linux Journal.
|Designing Electronics with Linux||May 22, 2013|
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
- Designing Electronics with Linux
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Using Salt Stack and Vagrant for Drupal Development
- Validate an E-Mail Address with PHP, the Right Way
- Build a Skype Server for Your Home Phone System
- A Topic for Discussion - Open Source Feature-Richness?
- Tech Tip: Really Simple HTTP Server with Python
- Why Python?
- Not free anymore
1 hour 59 min ago
5 hours 47 min ago
- Reply to comment | Linux Journal
5 hours 55 min ago
- Understanding the Linux Kernel
8 hours 9 min ago
10 hours 39 min ago
- Kernel Problem
20 hours 42 min ago
- BASH script to log IPs on public web server
1 day 1 hour ago
1 day 4 hours ago
- Reply to comment | Linux Journal
1 day 5 hours ago
- All the articles you talked
1 day 7 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?