Google Irks Android Developers with Cyanogen Move
Google has created uproar among Android developers by calling out a so-called "modder" for creating a firmware modification known as CyanogenMod that bundles some of Google's proprietary applications. At issue is Google’s commitment to openness and developer perception of how well the company is managing that commitment.
Google has created uproar among Android developers by calling out a so-called "modder" for creating a firmware modification known as CyanogenMod that bundles some of Google's proprietary applications.
According to reports, Google has slapped a cease-and-desist order against the developer. "Google has reportedly filed a cease-and-desist order against one of the Android platform’s most prolific developers," said a GigaOm report. "The developer, Steve Kondik, who’s known as Cyanogen, offers a free, after-market firmware product that bundles closed-source Google apps such as Gmail, Market, Talk and YouTube. CyanogenMod, as the app is dubbed, claims 30,000 users, many of whom appear to be hardcore Android fans."
In a blog post regarding the situation, Steve Schultze, associate director of the Center for Information Technology Policy at Princeton University, said:
"Android represents a careful balance on the part of Google, in which the company seeks to foster open platforms but maintain control over its proprietary (but free) services. Google has stated as much, in response to the current debate. Android is an exciting alternative to the largely closed-source model that has dominated the mobile market to date. Google closely integrated their Apps with the operating system in a way that makes for a tremendously useful platform, but in doing so hampered the ability of third-party developers to fully contribute to the system. Perhaps the problem is simply that they did not choose the right location to draw the line between open vs. closed source—or free-to-distribute vs. not."
In response to the uproar from developers, Dan Morrill, a Google engineer working in the developer relations team for Android, said, "Recently there's been some discussion about an exchange we had with the developer of one of those builds, and I've noticed some confusion around what is and isn't part of Android's open source code. I want to take a few moments to clear up some of those misconceptions, and explain how Google's apps for Android fit in."
Added Morrill:
"With a high-quality open platform in hand, we then returned to our goal of making our services available on users' phones. That's why we developed Android apps for many of our services like YouTube, Gmail, Google Voice, and so on. These apps are Google's way of benefiting from Android in the same way that any other developer can, but the apps are not part of the Android platform itself. We make some of these apps available to users of any Android-powered device via Android Market, and others are pre-installed on some phones through business deals. Either way, these apps aren't open source, and that's why they aren't included in the Android source code repository. Unauthorized distribution of this software harms us just like it would any other business, even if it's done with the best of intentions."
However, Google's response has done little to quell developer reaction.
In a message on a mailing list for New York Android Software Developers, a developer identified as Chris Stratton said, "To me, this really highlights a question that has been worrying me ever since getting involved in Android: Is Android open source for end users, or only for OEM phone manufacturers who hold the bootloader keys and can negotiate the licenses for the proprietary parts needed to give it full function?"
Added Stratton:
"This is very worrisome, because it's the exact opposite of the Stallman-esque 'right to repair' behind Android's GPL Linux kernel. It may well ultimately prove possible to create some kind of tool for in-phone combination of a customized platform built from open sources with the proprietary binaries already on the phone, but the effective message that 'only OEMs should expect to retain full functionality when changing the platform' seems to suggest that it is only the theoretical Android, and not the practical one, which is actually open source."
Another poster to the New York Android Software Developers list, identified as "Hong," said: "I'm very disappointed at how Google handled CyanogenMod. There are many users [who] got an Android phone just because of CM ROM who would otherwise go for some other phones. Google has effectively told the ROM community that it's illegal to distribute Google apps in Android ROM. But an Android ROM w/o Gmail/Google account settings is basically unusable."
Moreover, said Hong, "I'm putting some Android work on hold and resuming back to my old iPhone dev self, and will also resume my [Palm] Pre webOS projects."
Speaking of the iPhone, Palm and the webOS, in a Phandroid post titled "Eff Google, Screw Android: The Backlash Begins," Jean Baptiste Queru, a Google engineer working on Android is cited for tweeting his disdain for Google's handling of the situation. The Phandroid post reads:
"This is bad. Really bad. So bad that one of the lead Android developers themselves are insinuating this is worth walking away from the platform. Jean-Baptiste Queru has just tweeted, 'To my Apple, Microsoft and Palm buddies: are you hiring to work on mobile stuff?'”
In addition, a commenter identified as "Bob" responding to Schultze's blog post said:
"Finally the world is waking up to Google and its 'open-source' strategy. The company is a serial abuser of the entire notion of 'open'—cynically wielding it as a weapon in business.
"The company has never *joined* an open-source project. It just starts them—ensuring that by the strength of the number or coders it has, it keeps control over the projects. It does this even when there are well-established projects already, screwing over other communities in the process—Mozilla vs. Chrome, Android or ChromeOS vs. MobLin or LiMo.
"Bottom line—Google uses the 'open' concept cynically. It makes things open when it suits its interests (and always retains control) and it locks down otherwise.
"And the simpering community rolls over and takes it because it's the darling 'do no evil' Google."
Google 'Conflicted'
Meanwhile, Brian Gupta, a New York Android developer and engineer at Brandorr Group, told eWEEK, "I am certain that Google is conflicted about the whole thing. On one hand, the folks working on Android truly appreciate the uptake by the hacker and modding community, and are working to figure out how to accommodate their needs. On the other hand, technically the Cyanogen mods did include proprietary binary code from a number of sources, including Google and HTC, and were being redistributed without a distribution license."
Added Gupta:
"My guess is that Google has known for some time what was going on, but probably thought 'best not to upset the apple cart' while Android was in its infancy, with only one or two devices from a single manufacturer available on a single carrier. Now that we are on the verge of Android devices being shipped from at least five hardware vendors with over half a dozen carriers, Google probably felt that they needed to get a handle on this. I sense they feared things getting out of control with modders doing willy-nilly ports of innovations from one vendor/carrier to another—e.g., Motoblur on HTC devices and HTC Sense on Motorola devices. I think Google's legal team had a strong part in what took place, and forced action."
Gupta also said he believes that Google needed to engage the community before sending out the cease-and-desist order. "They hadn't made their position clear and depending on your point of view seemed to tacitly be condoning what was going on," he said. "Going forward, I really do think they need to work out a policy that allows people to rebundle the apps that come with a device and release blessed custom firmware for that same device."
"All in all," Gupta said, "it seems that this is a serious setback, but not large enough of one to stop the momentum that Android has built to this point."
Gupta is optimistic:
"At this point, I really don't want to see what is truly the most promising open mobile platform crash and burn, just as it is about to take off. That said, now that Google has rebooted the community, I think that people are retooling and refocusing on actually making the open-source promise of Android a reality. JBQ, a Google developer, kicked off an informal project to make the open-source build of Android actually useful out of the box."
Meanwhile, in a Sept 27 post responding to Google's cease-and-desist move, the CyanogenMod site said:
"The issue that’s raised is the redistribution of Google’s proprietary applications like Maps, GTalk, Market, and YouTube. These are not part of the open source project and are only part of 'Google Experience' devices. They are Google’s intellectual property and I intend to respect that. I will no longer be distributing these applications as part of CyanogenMod. But it’s OK. None of the go-fast stuff that I do involves any of this stuff anyway. We need these applications though, because we all rely so heavily on their functionality. I’d love for Google to hand over the keys to the kingdom and let us all have it for free, but that’s not going to happen. And who can blame them?"
In addition, "There are lots of things we can do as end users and modders, though, without violating anyone’s rights," the Cyanogen blog said. "Most importantly, we are entitled to back up our software. Since I don’t work with any of these closed source applications directly, what I intend to do is simply ship the next version of CyanogenMod as a 'bare bones' ROM. You’ll be able to make calls, MMS, take photos, etc. In order to get our beloved Google sync and applications back, you’ll need to make a backup first. I’m working on an application that will do this for you."
source
Google has created uproar among Android developers by calling out a so-called "modder" for creating a firmware modification known as CyanogenMod that bundles some of Google's proprietary applications.
According to reports, Google has slapped a cease-and-desist order against the developer. "Google has reportedly filed a cease-and-desist order against one of the Android platform’s most prolific developers," said a GigaOm report. "The developer, Steve Kondik, who’s known as Cyanogen, offers a free, after-market firmware product that bundles closed-source Google apps such as Gmail, Market, Talk and YouTube. CyanogenMod, as the app is dubbed, claims 30,000 users, many of whom appear to be hardcore Android fans."
In a blog post regarding the situation, Steve Schultze, associate director of the Center for Information Technology Policy at Princeton University, said:
"Android represents a careful balance on the part of Google, in which the company seeks to foster open platforms but maintain control over its proprietary (but free) services. Google has stated as much, in response to the current debate. Android is an exciting alternative to the largely closed-source model that has dominated the mobile market to date. Google closely integrated their Apps with the operating system in a way that makes for a tremendously useful platform, but in doing so hampered the ability of third-party developers to fully contribute to the system. Perhaps the problem is simply that they did not choose the right location to draw the line between open vs. closed source—or free-to-distribute vs. not."
In response to the uproar from developers, Dan Morrill, a Google engineer working in the developer relations team for Android, said, "Recently there's been some discussion about an exchange we had with the developer of one of those builds, and I've noticed some confusion around what is and isn't part of Android's open source code. I want to take a few moments to clear up some of those misconceptions, and explain how Google's apps for Android fit in."
Added Morrill:
"With a high-quality open platform in hand, we then returned to our goal of making our services available on users' phones. That's why we developed Android apps for many of our services like YouTube, Gmail, Google Voice, and so on. These apps are Google's way of benefiting from Android in the same way that any other developer can, but the apps are not part of the Android platform itself. We make some of these apps available to users of any Android-powered device via Android Market, and others are pre-installed on some phones through business deals. Either way, these apps aren't open source, and that's why they aren't included in the Android source code repository. Unauthorized distribution of this software harms us just like it would any other business, even if it's done with the best of intentions."
However, Google's response has done little to quell developer reaction.
In a message on a mailing list for New York Android Software Developers, a developer identified as Chris Stratton said, "To me, this really highlights a question that has been worrying me ever since getting involved in Android: Is Android open source for end users, or only for OEM phone manufacturers who hold the bootloader keys and can negotiate the licenses for the proprietary parts needed to give it full function?"
Added Stratton:
"This is very worrisome, because it's the exact opposite of the Stallman-esque 'right to repair' behind Android's GPL Linux kernel. It may well ultimately prove possible to create some kind of tool for in-phone combination of a customized platform built from open sources with the proprietary binaries already on the phone, but the effective message that 'only OEMs should expect to retain full functionality when changing the platform' seems to suggest that it is only the theoretical Android, and not the practical one, which is actually open source."
Another poster to the New York Android Software Developers list, identified as "Hong," said: "I'm very disappointed at how Google handled CyanogenMod. There are many users [who] got an Android phone just because of CM ROM who would otherwise go for some other phones. Google has effectively told the ROM community that it's illegal to distribute Google apps in Android ROM. But an Android ROM w/o Gmail/Google account settings is basically unusable."
Moreover, said Hong, "I'm putting some Android work on hold and resuming back to my old iPhone dev self, and will also resume my [Palm] Pre webOS projects."
Speaking of the iPhone, Palm and the webOS, in a Phandroid post titled "Eff Google, Screw Android: The Backlash Begins," Jean Baptiste Queru, a Google engineer working on Android is cited for tweeting his disdain for Google's handling of the situation. The Phandroid post reads:
"This is bad. Really bad. So bad that one of the lead Android developers themselves are insinuating this is worth walking away from the platform. Jean-Baptiste Queru has just tweeted, 'To my Apple, Microsoft and Palm buddies: are you hiring to work on mobile stuff?'”
In addition, a commenter identified as "Bob" responding to Schultze's blog post said:
"Finally the world is waking up to Google and its 'open-source' strategy. The company is a serial abuser of the entire notion of 'open'—cynically wielding it as a weapon in business.
"The company has never *joined* an open-source project. It just starts them—ensuring that by the strength of the number or coders it has, it keeps control over the projects. It does this even when there are well-established projects already, screwing over other communities in the process—Mozilla vs. Chrome, Android or ChromeOS vs. MobLin or LiMo.
"Bottom line—Google uses the 'open' concept cynically. It makes things open when it suits its interests (and always retains control) and it locks down otherwise.
"And the simpering community rolls over and takes it because it's the darling 'do no evil' Google."
Google 'Conflicted'
Meanwhile, Brian Gupta, a New York Android developer and engineer at Brandorr Group, told eWEEK, "I am certain that Google is conflicted about the whole thing. On one hand, the folks working on Android truly appreciate the uptake by the hacker and modding community, and are working to figure out how to accommodate their needs. On the other hand, technically the Cyanogen mods did include proprietary binary code from a number of sources, including Google and HTC, and were being redistributed without a distribution license."
Added Gupta:
"My guess is that Google has known for some time what was going on, but probably thought 'best not to upset the apple cart' while Android was in its infancy, with only one or two devices from a single manufacturer available on a single carrier. Now that we are on the verge of Android devices being shipped from at least five hardware vendors with over half a dozen carriers, Google probably felt that they needed to get a handle on this. I sense they feared things getting out of control with modders doing willy-nilly ports of innovations from one vendor/carrier to another—e.g., Motoblur on HTC devices and HTC Sense on Motorola devices. I think Google's legal team had a strong part in what took place, and forced action."
Gupta also said he believes that Google needed to engage the community before sending out the cease-and-desist order. "They hadn't made their position clear and depending on your point of view seemed to tacitly be condoning what was going on," he said. "Going forward, I really do think they need to work out a policy that allows people to rebundle the apps that come with a device and release blessed custom firmware for that same device."
"All in all," Gupta said, "it seems that this is a serious setback, but not large enough of one to stop the momentum that Android has built to this point."
Gupta is optimistic:
"At this point, I really don't want to see what is truly the most promising open mobile platform crash and burn, just as it is about to take off. That said, now that Google has rebooted the community, I think that people are retooling and refocusing on actually making the open-source promise of Android a reality. JBQ, a Google developer, kicked off an informal project to make the open-source build of Android actually useful out of the box."
Meanwhile, in a Sept 27 post responding to Google's cease-and-desist move, the CyanogenMod site said:
"The issue that’s raised is the redistribution of Google’s proprietary applications like Maps, GTalk, Market, and YouTube. These are not part of the open source project and are only part of 'Google Experience' devices. They are Google’s intellectual property and I intend to respect that. I will no longer be distributing these applications as part of CyanogenMod. But it’s OK. None of the go-fast stuff that I do involves any of this stuff anyway. We need these applications though, because we all rely so heavily on their functionality. I’d love for Google to hand over the keys to the kingdom and let us all have it for free, but that’s not going to happen. And who can blame them?"
In addition, "There are lots of things we can do as end users and modders, though, without violating anyone’s rights," the Cyanogen blog said. "Most importantly, we are entitled to back up our software. Since I don’t work with any of these closed source applications directly, what I intend to do is simply ship the next version of CyanogenMod as a 'bare bones' ROM. You’ll be able to make calls, MMS, take photos, etc. In order to get our beloved Google sync and applications back, you’ll need to make a backup first. I’m working on an application that will do this for you."
source
Posts
No comments: