View Single Post
Posts: 1,513 | Thanked: 2,248 times | Joined on Mar 2006 @ US
#10
Two things here - the discussion is not about open sourcing Nokia closed source items. The discussion is about being able to create community images (based on our recipe!) containing these proprietary bits and distribute these from maemo.org, and what they should contain.

We cannot expect everything handed to us with source and everything, but Nokia is doing something unprecedented in mobile devices, which they should be applauded for - they're inviting the community to actively remix the OS running on their hardware and are working with the community to provide legal framework and ability to distribute the remixes from maemo.org when they are produced.
Thanks, not opening up (that is a bit imprecise language), but allowing to use some components in Mer and allowing Mer to be freely licensed...


The discussion only dealt with licenses that prohibit commercial usage of the software - there are GPLv2 licensed materials in Ubuntu - and my own personal scripts are BSD-licensed. The point about GPLv3 was that the mere existence of GPLv3 licensed materials in the base system makes sure Mer will be used in open devices (Tivoization protection), living up to the motto of open device open platform (which Nokia tablets are) in contrast to let's say, T-Mobile G1, which is closed device open platform.
Naturally, Mer inherits licensing status from Ubuntu. Just to get clarity. There will be a version of Mer with closed bits from Nokia that will be licensed to NIT MAC addresses and distributed from maemo.org, and an open source version of Mer available for other devices?

I don't mean to take the topic to something you don't want to discuss and if you instead want to focus on the nuts and bots. Thanks again for all your work.