Just because the IPhone seems to be what most people use and the extensive amount of new applications they keep coming out with. They even have applications for beginner's without programming knowledge to write applications. So as far as openness, I think i'd say IPhone.

Wendy Seltzer asks, Which is more open: the Nokia N95 or the iPhone? Regardless of the answer, I'm wondering if there's an objective way to score openness... perhaps a kind of in-the-wild folksonomic list of deal-makers and deal-killers.

Definitely it won't be easy to score objectively between those two, but one can score easily between Linux and, say, Apple OS. Between the two, whichever phone makes installing other software on it seamless will probably be the winner. Whichever one comes with software that you can manipulate and change, that would be the most opensource one.
However, I think that makes neither good for the Opensource points :)

didn't get around to making an index, or a site, or a colorful table out of it (I'm currently using zim for it). If I did the latter, it would certainly be biased, of course, because it doesn't only describe openness.

I think it is a good idea to evaluate the openness. In my opinion the most important factor should be that you can see and change the source code. Then it is totally open.
If this is not possible the dimensions which are mentioned before are quite good. Just rank them with an importance factor and you have your scoring model.

- can you transfer it to someone else?
- can you copy it for yourself?
- can you copy it to give away?
- can you copy it and sell it?
- can you alter it and use it by itself?
- can you alter it and use it with its standard infrastructure?
- can you alter it and distribute the method of alteration?
- can you alter it and distribute the altered work?
- can you alter it and sell the altered work?
- which of these abilities can you pass to other people?
- which of these abilities can you restrict from other people?
- is there a documented ABI?
- is there a documented API?
- is there an available SDK?
- is there a free or very-low-cost SDK?
- does the programming interface expose all the features?
- can you get source code and/or schematics?
- can you redistribute the source or schematics?
- how end-user friendly is the best method of adding functions (new HW, new SW)?

I've started compiling a list of companies this summer, containing some information about them, like what software they are using for their site, what file formats they use, what good/bad things they've done lately (or, if they are the same all the time, throughout their history)…

I didn't get around to making an index, or a site, or a colorful table out of it (I'm currently using zim for it). If I did the latter, it would certainly be biased, of course, because it doesn't only describe openness.

For example, it lists:
About web sites:
- the web server used for the site
- how much Flash the site contains and how much it depends on it
- what other file formats are used
- what the site says about browsers (e.g. "This site is best viewed in …)
About company relationships
- what company designed the site, what company gave them software, hardware etc

Subsidiaries are all listed under the owner, and their name links to the owners name.

Trending Topics

Upcoming Webinar

Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report

August 27, 2015
12:00 PM CDT

DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.