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

Policy framework things are coming to MeeGo, too, which puts a burden on applications to state what kind of activities they're doing.. Such as media player behaviour or dialer ringtone, determining device behaviour and priorities in certain situations.. It's kinda needed for any kind of sane behaviour.

We'll have a open policy for you to rewrite, AFAIK.

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

I don't understand, how is this related to the text you quoted?
I can understand this points, but 100%free software doesn't mean
100% open-source-community-based-crap or semi-professional software.
Yes, but it is this thin layer that stands in our way. A thin layer
wouldn't be so bad, but there are some terrible bugs.

calendar application:
forgets task alarms
has senseless alarm presets.
mediaplayer widget play button doesn't work always.
camera applications exposure setting does not work with manual iso setting.

So you have this thin layer but some parts
just don't work.

We don't know how long nokia supports maemo5 or
if there will be another update.
Is there hope to get bugs fixed?
And (I don't really dare to ask) feature requests?

Another probem is, nokias applications aren't great they aren't worthfull to protect but they are well integrated. And this advantage
is inaccessible for the community. We can never fully replace these well intergrated applications with our owns.

It is just sad to see what could be possible with the great N900 hardware, the Maemo5 OS and this community.

nicolai

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

It's not the policy framework I dislike about Maemo5. It's the fact that it's mostly undocumented and Nokia never intended applications to play by its rules because the rules were kept secret.

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

Not true.
The main problem is that they don't obey their own rules. Download a while/light theme and see the calendar app. It remains black... (there are other examples as well)

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

what? so maemo has same Qt as meego and still you want to develop on meego, but on maemo? and even on symbian where Qt is old? i'll ask u again and i want straight answer "why u asking developers to develop for symbian and not maemo while it should be portable anyway as u advertasing yourself"

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

Add an example:
locales are also a serious problem (calendar, ISO non-compatibility)
although I am still trying to hack this issue :confused:
it appears that some of the nokia-binaries still refuse to play
with locales in a sane manner. :mad:

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

So the question, then, is... why isn't Nokia writing open-source applications from the start (or writing new, or getting open-sourced apps and using them) on these devices, so as to avoid the whole problem altogether? Why does Nokia feel the need to obligate users to use closed-source software, even the ones written by Nokia themselves, on a platform being sold on the benefits of being "open-source"?

100%? How about at least 95%? 90% even? Why does more or less than around half of the firmware image have to come with so much closed-source? To the results, how badly is Red Hat doing? IBM? Hell.. zLinux is 100% open-source that runs on IBM mainframes when they sell their hardware and it's doing pretty well, last time I checked. Novell isn't doing too shabby with SuSE either. They should broaden their scope and look again and how it CAN be done, instead of looking only at handset manufacturers and how they did things wrong.

Mind you--these are server Linux support licenses but they're giving away their distributions of software for free and open-source, with little to no closed-source. Wouldn't Nokia rather sell these devices with a world-class, enterprise capable level of support and maintain customer loyalty to profit from what is essentially a free software product along with their hardware? Nokia's view seems far too narrow and myopic to think of how they could difference themselves from old-school cell phone hardware manufacturer thinking.

My two cents.

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

I find it funny that you mention RedHat, considering they do practically the same Nokia does. (They have large closed source software comercial offerings, but it is usually presented as a opensource friendly company because they use and, more importantly, contribute to open source projects. Like Nokia).

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

It is terribly funny, isn't it? Especially considering the host OS and most of what they give you is pretty much almost entirely open-source and the closed-source offerings are software packages that they offer and support above and beyond the LAMP or base OS they offer. ...much like buying and running closed-source applications you buy for the tablet... yanno, not tied to the OS so much. Funny that, yes.

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

Actually, I'd say that their proprietary software is so tied to the OS that it makes no sense to use it outside of a RedHat context, and that for obvious reasons I do not feel like hacking on it the same way I do feel like hacking on for ex. the Notes (EDIT: the Nokia Notes) application.

So, other than myself not willing to pursue RedHat like I would Nokia for this, because of what was stated above, I see no difference.