Openness data for Fremantle PR1.1 and Diablo 4.1.2
 

I've just published a blog post 'Mapping openness of Maemo5.0 PR 1.1 and Maemo 4.1.2' where I give the openness report I've been taking about for a while now. Please read the blog post through before diving into the actual openness report as it can be a bit confusing otherwise.

http://mer-project.blogspot.com/2010...-pr11-and.html

Feel free to comment in this thread or on my blog.

Re: Openness data for Fremantle PR1.1 and Diablo 4.1.2
 

It might also be useful to compare L1+L2 vs L3-L7, ie how much can be rebuilt for using on a beagleboard, Mer etc. However there are a few complications when counting closed dependencies:

• some like libjpeg6b & libspeex1 can (presumably) be replaced by their upstream open counterparts with just some performance loss.
• some are softer than others (eg modest can be built without exchange/nokia messaging support).
• some are just "content", not code (eg osso-rss-feed-reader-list or hildon-welcome-default-logo).

Re: Openness data for Fremantle PR1.1 and Diablo 4.1.2
 

You're right on speex and libjpeg (we do this in Mer) - the idea is not really to have the numbers but to provide us a view of where things are connected at the hip and how to work around them is then an exersise left to us.