Sumber : 
http://androidandme.com/2009/09/news/google-responds-to-cyanogenmod-controversy/


Google responds to CyanogenMod controversy
By Taylor Wimberly on Sep 25


Android developer Dan Morrill has made a post on the official Android  
blog in response to the recent Cyanogen controversy.

     Lately we’ve been busy bees in Mountain View, as you can see from  
the recent release of Android 1.6 to the open-source tree, not to  
mention some devices we’re working on with partners that we think  
you’ll really like. Of course, the community isn’t sitting around  
either, and we’ve been seeing some really cool and impressive things,  
such as the custom Android builds that are popular with many  
enthusiasts. 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.

     Everyone knows that mobile is a big deal, but for a long time it  
was hard to be a mobile app developer. Competing interests and the  
slow pace of platform innovation made it hard to create innovative  
apps. For our part, Google offers a lot of services — such as Google  
Search, Google Maps, and so on — and we found delivering those  
services to users’ phones to be a very frustrating experience. But we  
also found that we weren’t alone, so we formed the Open Handset  
Alliance, a group of like-minded partners, and created Android to be  
the platform that we all wished we had. To encourage broad adoption,  
we arranged for Android to be open-source. Google also created and  
operates Android Market as a service for developers to distribute  
their apps to Android users. In other words, we created Android  
because the industry needed an injection of openness. Today, we’re  
thrilled to see all the enthusiasm that developers, users, and others  
in the mobile industry have shown toward Android.

     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.

     I hope that clears up some of the confusion around Google’s apps  
for Android. We always love seeing novel uses of Android, including  
custom Android builds from developers who see a need. I look forward  
to seeing what comes next!

Steve Kondik (Cyanogen) issued his own response on his Twitter account.

     Sorry everyone, CyanogenMod in it’s current state is done. I am  
violating Google’s license by redistributing their applications. The  
only thing we can do is develop an open-source replacement for the  
most important parts. I do plan to release a “bare bones” version of  
CM as 4.2, and the source code will remain available. Unfortunately, I  
feel this is a chilling effect for the entire Android community, since  
what we are doing is now considered illegal.

We even had an inside source who wishes to remain anonymous that  
weighed in on the issue:

     The C&D that Google sent to cyanogen was spawned by Google’s  
legal team, and lacks the support of the Android developers (who think  
it’s in VERY poor taste), likely spawned by the fact that he included  
a copy of the new 1.6 marketplace which had not been released anywhere  
else. He’s had at least 1 phone call with Google, and is working to  
open a dialog with them about the issue. They’re so far well with in  
their legal rights to do what they did, and he’s trying to open a  
dialog to allow him to continue. At this point, he thinks they’re  
acting in good faith, and is trying to keep this as quiet as possible  
to avoid any negative PR, so long as they’re acting in good faith.



--~--~---------~--~----~------------~-------~--~----~
Google Groups "Indonesian Android Community [id-android]" group.

To post to this group, send email to id-android@googlegroups.com

To request to subscribe to this group, please visit the following page:
 http://groups.google.com/group/id-android/subscribe?hl=en-GB

To send a message to the owner, visit the following page:
 http://groups.google.com/group/id-android/post?sendowner=1&hl=en-GB    or   
    agus.hamonan...@gmail.com


For more options, visit this group at
http://groups.google.com/group/id-android?hl=en?hl=en-GB

To unsubscribe from this group, send email to
id-android+unsubscr...@googlegroups.com

Indonesian Android Community on Facebook

http://www.facebook.com/group.php?gid=112207700729
-~----------~----~----~----~------~----~------~--~---

Kirim email ke