Comments on: On Monday Google will announce Android, their mobile phone platform *UPDATE* http://www.intomobile.com/2007/11/03/set-the-date-on-monday-google-will-announce-android-their-mobile-phone-platform.html Cell Phone News, Information, and Analysis Tue, 24 Nov 2009 14:16:36 -0600 http://wordpress.org/?v=abc hourly 1 By: Mike http://www.intomobile.com/2007/11/03/set-the-date-on-monday-google-will-announce-android-their-mobile-phone-platform.html/comment-page-1/#comment-75207 Mike Mon, 05 Nov 2007 09:25:01 +0000 http://www.intomobile.com/2007/11/03/set-the-date-on-monday-google-will-announce-android-their-mobile-phone-platform.html#comment-75207 Yes this is great news. ! Yes this is great news. !

]]> By: pseudofinn http://www.intomobile.com/2007/11/03/set-the-date-on-monday-google-will-announce-android-their-mobile-phone-platform.html/comment-page-1/#comment-74371 pseudofinn Sun, 04 Nov 2007 00:33:43 +0000 http://www.intomobile.com/2007/11/03/set-the-date-on-monday-google-will-announce-android-their-mobile-phone-platform.html#comment-74371 Wow this is very good news. :razz: Wow this is very good news. :razz:

]]> By: Linux Pundit http://www.intomobile.com/2007/11/03/set-the-date-on-monday-google-will-announce-android-their-mobile-phone-platform.html/comment-page-1/#comment-74333 Linux Pundit Sat, 03 Nov 2007 22:16:23 +0000 http://www.intomobile.com/2007/11/03/set-the-date-on-monday-google-will-announce-android-their-mobile-phone-platform.html#comment-74333 Good question, Stefan. Google's choice of the Apache license for the user-space portion of the Android stack would give Google, its partners, and future application writers more flexibility (meaning less reciprocity) when licensing their code. Such code would reside above the Linux kernel and base libraries, which are GPLv2 (modified by the COPYING) and LGPL respectively. That would mean that applications and application enabler m/w could be released to run on Android with either compatible FLOSS or commercial licensing terms, in line with Apache 2.0 terms. The Apache license, like the GPLv2/3, does require unfettered (re)distribution of derived works, ensuring availability of Android code to a community of developers. The FSF characterizes the Apache 2.0 license as "a free software license, compatible with version 3 of the GPL," but "...not compatible with GPL version 2, because it has some requirements that are not in the older version. These include certain patent termination and indemnification provisions." Given that most components of the Android stack (I suppose) would not directly co-mingle with GPLv2 code, the FSF objections are probably not an issue. You can read the Apache 2.0 license at http://www.apache.org/licenses/LICENSE-2.0 Good question, Stefan. Google’s choice of the Apache license for the user-space portion of the Android stack would give Google, its partners, and future application writers more flexibility (meaning less reciprocity) when licensing their code. Such code would reside above the Linux kernel and base libraries, which are GPLv2 (modified by the COPYING) and LGPL respectively. That would mean that applications and application enabler m/w could be released to run on Android with either compatible FLOSS or commercial licensing terms, in line with Apache 2.0 terms.

The Apache license, like the GPLv2/3, does require unfettered (re)distribution of derived works, ensuring availability of Android code to a community of developers.

The FSF characterizes the Apache 2.0 license as “a free software license, compatible with version 3 of the GPL,” but “…not compatible with GPL version 2, because it has some requirements that are not in the older version. These include certain patent termination and indemnification provisions.”

Given that most components of the Android stack (I suppose) would not directly co-mingle with GPLv2 code, the FSF objections are probably not an issue.

You can read the Apache 2.0 license at http://www.apache.org/licenses/LICENSE-2.0

]]> By: Stefan Constantinescu http://www.intomobile.com/2007/11/03/set-the-date-on-monday-google-will-announce-android-their-mobile-phone-platform.html/comment-page-1/#comment-74315 Stefan Constantinescu Sat, 03 Nov 2007 21:34:57 +0000 http://www.intomobile.com/2007/11/03/set-the-date-on-monday-google-will-announce-android-their-mobile-phone-platform.html#comment-74315 You're right about them wanting Wind River for their SDK, but as far as the idea to monetize the SDK ... unsure about that. I'm going to say doubtful. Can you enlighten us as to what this open source lisence means versus others? You’re right about them wanting Wind River for their SDK, but as far as the idea to monetize the SDK … unsure about that. I’m going to say doubtful.

Can you enlighten us as to what this open source lisence means versus others?

]]> By: Linux Pundit http://www.intomobile.com/2007/11/03/set-the-date-on-monday-google-will-announce-android-their-mobile-phone-platform.html/comment-page-1/#comment-74311 Linux Pundit Sat, 03 Nov 2007 21:23:54 +0000 http://www.intomobile.com/2007/11/03/set-the-date-on-monday-google-will-announce-android-their-mobile-phone-platform.html#comment-74311 An important question is why did Google bring Wind River into the deal? The Alameda-based firm is a relative newcomer to Linux, especially to mobile applications. Their only announced mobile design win has been with Palm, for the Foleo and other devices presumably in the pipeline. The most likely answer is for tools - Wind's Workbench presents an attractive and very usable Eclipse CDT integration. While there is a real need for a professional tool set to support a program of this presumed scope, will Google also provide a non-commercial SDK? An important question is why did Google bring Wind River into the deal? The Alameda-based firm is a relative newcomer to Linux, especially to mobile applications. Their only announced mobile design win has been with Palm, for the Foleo and other devices presumably in the pipeline.

The most likely answer is for tools – Wind’s Workbench presents an attractive and very usable Eclipse CDT integration. While there is a real need for a professional tool set to support a program of this presumed scope, will Google also provide a non-commercial SDK?

]]>