maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Community (https://talk.maemo.org/forumdisplay.php?f=16)
-   -   [Council] State of Maemo, Q32010.2 (https://talk.maemo.org/showthread.php?t=66275)

lma 2010-12-11 12:49

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

Originally Posted by jstokes (Post 894617)
True. But it's not hard to make it use Nokia's libcal.

Though there may be licensing issues when using cal.h ("Copyright (C) 2004-2008 Nokia. All rights reserved.") outside Fremantle/N900.

Quote:

Code:

Nokia-N800-43-7:~# ls -l /usr/lib/libcal*

I stand corrected (silly me, I was looking for a libcal package, but it's actually in libdsme0).

kureyon 2010-12-12 04:40

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

Originally Posted by qgil (Post 892423)
There is also the argument that Nokia prefers to encourage contributions around the frameworks currently in development rather than encourage contributions (by opening the source code) around the frameworks that the Nokia software strategy is not interested in pushing anymore.

AKA the same old story.

Drop support for an "old" device and push people to buy a new one = more money for Nokia.

Quote:

Originally Posted by sivang (Post 891635)
the "escalation" policy in brief is as follows: ...

What does this say about Nokia's policy/organisation/motivation? You have to kick their behind multiple times to get things looked at? Or is it a perseverance test - if you're stubborn enough to complete all the steps then maybe they'll reward you by looking at your request?

Quote:

Originally Posted by geneven (Post 893319)
It's a good point, but to me it's almost funny that these apps that are in general not that good are so well protected. It's like keeping dog biscuits in a safety deposit box.

It's probably because the code for these apps are atrocious, which is why they are not that good, and hence they want to keep the crappy code secret ;)

kureyon 2010-12-12 04:44

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

Originally Posted by javispedro (Post 893612)
I find it funny that you mention RedHat, considering they do practically the same Nokia does. (They have large closed source software comercial offerings

Interesting, any examples, links?

Quote:

but it is usually presented as a opensource friendly company because they use and, more importantly, contribute to open source projects. Like Nokia).
As lma says, Red Hat is notorious for for buying closed source software with the express intention of turning them into open source (and hence benefiting their competitors).

tso 2010-12-12 06:00

Re: [Council] State of Maemo, Q32010.2
 
Iirc, one nokia engineer claimed the dmse is still closed because they are embarrassed about its quality...

lardman 2010-12-12 19:20

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

Originally Posted by tso (Post 895026)
Iirc, one nokia engineer claimed the dmse is still closed because they are embarrassed about its quality...

Yeah I'd heard that about a few packages.

danramos 2010-12-13 04:18

Re: [Council] State of Maemo, Q32010.2
 
So... status of Maemo: EMBARASSING?

javispedro 2010-12-13 15:46

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

Originally Posted by kureyon (Post 895011)
Interesting, any examples, links?

Check your copy of the "Linux Applications" disk.

Quote:

Originally Posted by kureyon (Post 895011)
As lma says, Red Hat is notorious for for buying closed source software with the express intention of turning them into open source (and hence benefiting their competitors).

And I understand that, as lma mentioned exactly the piece of software I had in mind, which has been opensourced.

lma 2010-12-14 07:59

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

Originally Posted by qgil (Post 893429)
When it comes to product development the guys deciding on the Nokia investments and the plans to convert them into benefits conclude that having a Nokia proprietary layer is better for business than not having it. Looking at the market and at the business results of companies shipping devices with 100% free software I can't deny that they have a point.

I assume this refers to Openmoko? While there are many reasons that project failed commercially (mostly boiling down to "not deep enough pockets"), none of them are that the software was too open. Are those guys saying that it would have been more successful with a proprietary layer, or that a completely open MeeGo product is doomed to failure? With no disrespect meant, isn't it the job of the open source advocate to correct these misconceptions?

tso 2010-12-14 08:47

Re: [Council] State of Maemo, Q32010.2
 
Openmoko bombed because it was only 2g in a world going 3g. Had they dropped the mobile radio fully i suspect it could have gone differently...

qgil 2010-12-14 13:49

Re: [Council] State of Maemo, Q32010.2
 
There was OpenMoko and there were/are others device makers putting all the stress in software freedom - with no remarkable impact in the mobile market whatsoever. But what is more important: do you have a more convincing business model for a company like Nokia? Taking into account that there are competitors out there that would clearly benefit from a 100% free & reusable UX experience in Nokia products.

Quote:

Originally Posted by lma (Post 896452)
With no disrespect meant, isn't it the job of the open source advocate to correct these misconceptions?

You just pushed a misconception yourself, assuming that Nokia business planners have such misconceptions about OpenMoko. :)

The job of an open source advocate inside a company is to help the company's objectives by pushing open source software and open development when/where it matters.

The Nokia N900 is still the most open handset you can buy from a major vendor, and the MeeGo platform is shaping up as the most open mobile platform any mobile vendor can use. Things could be still better from the point of view of software freedom... However, I honestly believe that the many open source advocates inside Nokia are achieving something useful for the free software community - and the company hiring them.


All times are GMT. The time now is 21:26.

vBulletin® Version 3.8.8