Re: [Council] State of Maemo, Q32010.2
 

To be fair, they did say they learned from the 770 story and for a while it looked like they did: the N800 got Bora, Chinook and Diablo, and potentially Elephanta down the line. Then the iPhone happened, Elephanta was scrapped, we had a 2-year gap between devices/OS releases and when it finally arrived it had lost half of what made Maemo unique.

(Yes, it's my standing position to blame Apple for everything, why do you ask?)

Re: [Council] State of Maemo, Q32010.2
 

I sincerely hope and expect the email client at least to be open.

Hm, do we know if Harmattan is still softfp?

There's a big spanner in the works here: platform security. Open MeeGo won't have access to the TPM chip (unless we can convince Nokia to sign our kernels every time, extremely doubtful IMHO), and even if Nokia gives us .debs that will install most of the apps will need platsec to protect user data etc so won't work.

Re: [Council] State of Maemo, Q32010.2
 

And let's not forget the "WONT FIX" list

https://bugs.maemo.org/buglist.cgi?q...ial%20Platform

Re: [Council] State of Maemo, Q32010.2
 

I would make more requests, but sadly they are all related to nokias closed applications.
(Calendar, Conversations, Mediaplayer (- applet)...
And if I understand you right, Nokia will never open this applications.
This "ideas open various parts ...." gave me the hope there is something new.
So, if it is worthwhile I can file licensing change requests.

Nicolai

Re: [Council] State of Maemo, Q32010.2
 

The way I see it, the best thing right now would be a rewrite of the stock apps, it takes time, but it's the only way go FOSS here :/

Here's a start (in Qt), hopefully, this project won't die, I'll open a gitorious page soon (it's currently a UI only) :|

http://i54.tinypic.com/k54gae.jpg
http://i51.tinypic.com/f2t155.jpg

Re: [Council] State of Maemo, Q32010.2
 

That's all well and good, but the calendar nokia made uses some ridiculous one-off backend, can't sync to anything at all reliably, has a completely useless tasks/notes setup, and has several (already mentioned) bugs rendering it nearly useless to a serious user.

Fine, you say, write a better one. That is a bad response, since the bugs the current calendar suffers are all fixable if they'd just open-source the damn thing. There is literally no possible business advantage nokia can be getting out of keeping it locked down. Instead of nicely integrating caldav into the existing calendar, I'm having to kludge a whole series of packages that try to work alongside this thing and work around its stupid timezone bugs.

I'd even prefer a non-redistributable license as long as I could see the source at all so I don't have to spend hours reverse-engineering bugs just to isolate problems that shouldn't exist.

Re: [Council] State of Maemo, Q32010.2
 

I know there are various discussions on meego-dev about softfp vs. hardfp and switching to hardfp for MeeGo 1.2. One of the reasons is Harmattan and Linaro alignment, I believe (with the big overriding one being performance).

More detail in the TSG meeting log for the proposal; and the ToolchainChangeProposal itself.

Stskeeps is the man in the know, though. EDIT: and he points us at this email which pretty much states Harmattan is hardfp.

Re: [Council] State of Maemo, Q32010.2
 

Hmm. Perhaps we should think of alternative ways to get past this roadblock beside completely opening. Maybe Nokia could give maemo.org a restricted license so a limited number of "trusted" people could access and modify the source under limitations sufficient to "protect" Nokia's interests and then maemo.org could redistribute the modified binaries to the public?

Re: [Council] State of Maemo, Q32010.2
 

A similar thing was suggested for PowerVR drivers etc. Nokia had issues with the financial liability that could be incurred by one or more individuals against whom they'd have no recourse.

Re: [Council] State of Maemo, Q32010.2
 

That can be addressed. Yes, the terms of the 3rd party license have to be honored, but if there is a will, there most likely is a way to do this (not complete open source unfortunately, but a license that permits redistribution of modified binaries).