Ubuntu Empire Strikes Back
The old "Ubuntu doesn't contribute back" argument cropped up again when Dave Neary released a report of the talk he gave at GUADEC on the contributions made to the GNOME desktop environment. He found that Red Hat and Novell contributed the most, and that Ubuntu and Mandriva (primarily a KDE distribution) were among the lowest. A firestorm of debate ensued, and Shuttleworth was accused of name calling and guilt to try to win the argument.
The report spurred reactions from many community members, and their responses usually depended upon which side of the fence they sat. Greg DeKoenigsberg, former Red Hat Community Architect, held no punches in his scathing criticism of Canonical and Ubuntu. He said Canonical was little more than "marketing organization masquerading as an engineering organization" taking "credit for code that Red Hat engineers wrote." Debian developers have been saying that for years about their work, but as a primarily KDE distro they didn't make the Top 20 list at all, so it appears they are staying out of this fight. Other distribution developers have been overheard expressing the same sentiments as well. DeKoenigsberg even touched on another one of Mark Shuttleworth's battle cries that really rally his troops while rubbing most of the Open Source community against the grain. He said, "they have the gall to suggest that Red Hat should change its release schedules to make it even easier for them to ride the gravy train." Most people will remember the many speeches given by Shuttleworth calling for "cadence" or the releasing of products (for example, GNOME) when it would be most advantageous to Ubuntu's release schedule.
Adam Williamson of Red Hat and formerly of Mandriva wondered if Ubuntu's success is any real success at all given that Linux represents less than 5% of total desktop usage amongst computer users, and that number hasn't grown significantly since Ubuntu's inception or rise to popularity. He did say that "if you show up with a couple of graphic designers, anyone who’s passed Media Relations 101, and a bit of cash, you can pretty much win by default, which is what Ubuntu did."
Sam Varghese, known Linux detractor and journalist, reminds us that Canonical didn't make the Top 30 in a report from the Linux Foundation on kernel contributors. On the same subject, "Greg Kroah-Hartman cited statistics that showed Canonical's contribution to 2.6.27-rc6 was 100 patches against Red Hat ... with 11,846 patches. Novell had 7222 patches." Varghese asks what everyone's trying to ask, "How about giving back a little more?"
Carlo Daffara, Open Source researcher, said that "GNOME is only one of the projects and they measure too little." He asserts that "bringing Ubuntu to millions of people is a contribution; every time Canonical manages to bring a press release out it is making a huge contribution." He sums up by saying this isn't a contest. "We should be happy for every, small, large, strange or different contributions that we receive." Chris Jones, Canonical employee, suggested "it would generally be more useful for people to be talking about solutions than arguing about who is the most or least evil."
Fortunately, Canonical let their voices be heard. Jono Bacon, Ubuntu Community Manager, offered a calm response pointing out the work Ubuntu developers do that is not part of official GNOME modules or those hosted and developed elsewhere such as Launchpad. He said, "There are also many projects built on GNOME technology that are not taken into account due to non-inclusion in GNOME modules or being developed outside of GNOME infrastructure." He continues to list several projects for which Ubuntu developers code and do not ship upstream. It seems he inadvertently confirmed the heart of the controversy. Debian formed their "Front Desk" in hopes of encouraging derivatives to share back.
Then Shuttleworth strikes back with his response, but it's not clear if he addressed the issue, or avoided it. Does Canonical's silence mean they don't care about giving back? Are the opponents being unfair in their expectations? Perhaps Jeffrey Stedfast summed it up best with "This is just how Free Software works. Don't like it? Cry me a river."
Susan Linton is a Linux writer and the owner of tuxmachines.org.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide