Don't Be Evil Means Don't Be Evil
Mixing Open Source communities and corporate boardrooms is a lot like mixing nitroglycerin — done properly, it produces unmeasurable good, but make a wrong move and the results won't be pretty. Some companies, like Red Hat, are adept at successfully marrying the two, while other companies seem to spend more time than they should diving for the nearest bunker.
We here at the news-desk are fans of the near-omnipresent search giant that is Google, and we don't mind saying so. However, though we don't play much poker, we know a spade when we see one, and we're not afraid to call it when we do. One such spade comes in the form of events that played out over the past few weeks with regard to the company's Open Source darling, Android.
Android has been an amazing success for Google, with a whole cadre of phones boasting it inside, and even the rocketing netbook market getting in on the game. The platform has not been without its faults, however, both with the software itself and perhaps more serious, with the company behind it.
Google's first major Android faux pas to come to light turned up last July, while the $10,000,000 Android Challenge was underway. In a move pulled straight from a sitcom script, Developer Advocate David McLaughlin accidentally alerted the world that the company was holding out on the community, providing up-to-date software development kits to contest participants while leaving Open Source developers in the lurch.
That revelation alone was enough to raise torches and pitchforks on the horizon, but that wasn't all. Google didn't just fail to hand out the goods to everyone in the class — they called in the gLaw team to have a go at it, using Non-Disclosure Agreements to keep the kits under wraps. As anyone who has been involved with the Open Source community for more than a few minutes can attest, legal teams aren't particularly popular. Those carting silencers, like NDAs, may find themselves tarred and feathered.
Silencer is a good term for it, as silence was Google's only response, including when two hundred developers petitioned for answers. The company — or at least, one of its minions — eventually spoke, but by all appearances not before consulting anyone with any knowledge of the Open Source world. The twenty-six word response read:
We appreciate the enthusiasm of our developers and we're excited that you're so passionate about the Android platform. Thanks for taking the time to send this.
To their credit, the company was smart enough to release an updated development kit shortly thereafter, along with plans for the future. The past several weeks, however, would suggest that a lesson was not among the things Google took away from the incident.
Enter Cyanogen — Steve Kondik — the developer behind an optimized Android fork known as CyanogenMod. CyanogenMod is built to offer rock-solid reliability and high performance — it also included several of Google's Android applications, including Google Talk, YouTube, and Gmail, among others. We say "included" because it doesn't any longer, thanks to another appearance from gLaw.
What did the besuited and briefcased bearers of the big stick want with Mr. Kondik? Why, to serve him with a Cease and Desist Order, of course.
If those bearing Non-Disclosure Agreements are likely to be tarred and feathered, anyone caught serving a Cease and Desist Order in the Open Source world should prepare to be bound, coated in honey, and left in the general vicinity of a colony of angry fire ants. Suffice it to say, they will not be popular, and Google's Gucci-clad goons are no exception.
CyanogenMod found itself on the wrong end of Google's heavy hand because, though Android is Open Source, the Google applications in question are not. There are ten thousand arguments to be made over the evils of closed-source applications, but what we can't dispute is that the apps in question were not free for use, and Google had legal grounds for preventing their distribution. Few of us would argue against protecting the proper use of one's software, open or closed — after all, that's the whole point behind software licensing. (For example, enforcing the requirement to distribute source code when the license requires it.) The Software Freedom Law Center keeps itself busy doing just that, and have had impressive success at forcing even the largest companies to play by the rules.
So then, what raises the reminders to "Don't Be Evil"? While we can't dispute that the grounds were there, or the virtue of doing so, the way one goes about protecting one's software is key, especially when the "one" in question is a multi-billion dollar corporation. The evil at hand isn't open vs. closed, nor is it legal distribution — the evil here is delivering messages by tank, and in the process cutting off your nose to spite your face.
When someone is dedicated enough to "your" Open Source software to want make it better, and to do it freely for the benefit of the people you're supposed to be so committed to providing benefits to, use a little discretion. While you're at it, do it before you have to offer half-hearted exhortations on your love for Open Source.
Tap the person on the shoulder and say "Hey, do you know you really shouldn't be distributing those?" Take ten minutes to figure out that leading with lawyers is both overkill and one of the worst sins you can commit in this community. If you're going to claim a commitment to openness, try to learn how it works, and think a little before sending a street gang to beat down people who, if anything, are a bit too enthusiastic about being open.
Above all, get a clue. That's not how this team plays.
Justin Ryan is a Contributing Editor for Linux Journal.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
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.Register Now!
- Google's SwiftShader Released
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Interview with Patrick Volkerding
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- 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