Let's look at this as a great opportunity. Presumably, all of these
phones will have a working linux kernel and drivers that are available
for them, whither the Android platform is truly open or not, surely
this is a big with for the OSS-phone community.

-Will

On Nov 22, 2007 2:50 PM, Rod Whitby <[EMAIL PROTECTED]> wrote:
> Stefan wrote:
> > Isn't google violating GPLv2 when it does not release the Code now?
> > I could use some GPL'ed code, change it, give it to manufacturer and say
> > i'll release it to public when the product is finish.
> > Thats totally against GPL, cause it prevents other company to use the
> > same code like the official manufacturer do.
> >
> > Or do i miss something?
>
> Yes, you missed the vital step of not accusing GPL violation until you
> determine whether the code in question is actually licensed under the
> GPL.  The Android system is an aggregation of things that are GPL'd (for
> which Google released the source code *ahead* of the announcement), and
> things that are not GPL'd (for which, like it or not, it is totally
> their perogative to choose whether and when they release the source code).
>
> Vincent wrote:
> > That is only required once the *distribute* the software.
>
> They *have* distributed the software.  And they have distributed the
> source code for the pieces of the software which is derived from GPL'd code.
>
> <rant>
> There are enough *real* GPL violaters in this world.
>
> Stop crying wolf over those companies whose business model you may not
> agree with, but who are meticulous about complying with the GPL for the
> GPL'd software they are using.
> </rant>
>
>
> -- Rod
>
> _______________________________________________
> OpenMoko community mailing list
> [email protected]
> http://lists.openmoko.org/mailman/listinfo/community
>

_______________________________________________
OpenMoko community mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/community

Reply via email to