Re: Closed Source Packages in Maemo
 

1 million.

The number of HTC G1 sold in U.S.A by T-Mobile.

Source [In French]

Yet it is equipped with Android, an OS that HTC's competitors can also install on their smartphones.

And this Android, except for some drivers and 4 applications softwares, are FOSS.

These 4 applications softwares proprietary are:
- gMail --> replaceable by a FOSS e-mail client.
- gTalk --> replaceable by a FOSS IM Client.
- Google Map --> require much work, but replaceable by a FOSS Map Software.
- Adroid Market --> replaceable by a package manager (ex: PackageKit) to provide FOSS softwares.

So we can say that the HTC G1 was sold with an OS almost pure FOSS to 1 million copies.

There are exist even "100% FOSS version" of Android.

If HTC can it, Nokia can it.

PS: Some people ask for an example with numbers, it is.

Re: Closed Source Packages in Maemo
 

Like if Android's OpenGL ES library was opensource.

Come on, stop this madness.

Re: Closed Source Packages in Maemo
 

I'm not sure what point you're making with that set of data ... especially right now, when those 4 "Google Experience" apps have caused controversy in the Android camp (Google recently issued a Cease and Desist letter to one of the bigger Android hackers over those 4 apps).

So, it would seem that:
1) Android, even in its most vanilla form, is not 100% FOSS ... it has apps and components that are flat out "not open". Just like Maemo.
2) Nokia is being more open than Google about it ... haven't seen nor heard of a C&D letter to the Mer team, for example.

It would seem to me that you've just undermined your own argument against Nokia's positioning/etc. with Maemo.

Re: Closed Source Packages in Maemo
 

Nokia is working in exactly the opposite direction with the Mer team, trying to help them get access to the closed parts. So no, you will never see a C&D letter issued to the Mer team...

Re: Closed Source Packages in Maemo
 

That said, we are being very careful in Mer. Such as working with vendors on ways for us to use closed blobs and integrating them in images (this may be useful for the Diablo Community SSU project too). We do this because it is a longer lasting solution and gives us better relations with vendors.

But fair is fair - if you included copyrighted material you did not have a license to redistribute, you'll get a C&D. I think Google shot themselves in the foot over this matter though - instead of working out a way this could be useful. I mean, the users already have google apps on their device, why can't they keep them? Nokia went out of their way to work with us to find a solution for these issues and they should be applauded for this attitude.

What we try to do is making a way for the scenario of: if you own a device, you can remix the firmware you have and distribute it to other device owners. - or in Mer's perspective, have HW support blobs and the rest of the system 100% OSS and have things working out of the box.

Re: Closed Source Packages in Maemo
 

I'd rate that suggestion as insightful and this message I'm writing as redundant. :)

Re: Closed Source Packages in Maemo
 

I'm not sure of this. As I understand it, Android is the OS only, not the apps, and the wifi component, etc., is open, AFAIK

Yes, lol on this one, :D

Re: Closed Source Packages in Maemo
 

No, because I mentioned the HTC G1 for this:


Compared to the beginning of this thread, I try to be respectful and I bring good examples (with numbers if possible) to substantiate my statements.

Have I got a real debate in return?

No really, some people ignore me, others have talk at the limit of the insult and others change the meaning of my talk by fixing themselves on what I don't want mean for hide what I want mean....

Is it this? "Maemo.org, the Open Community"?

Re: Closed Source Packages in Maemo
 

Hehe, the whole THC UI called Sense is proprietary

Re: Closed Source Packages in Maemo
 

HTC G1 haven't got this UI.