Active Topics
-
Maemo repository (8)
to Community by Maemish - 14 hrs, 48 mins ago -
Porting apps to Leste (44)
to Maemo 7 / Leste by norayr - 19 hrs, 21 mins ago -
List of well performing apps on Leste (35)
to Maemo 7 / Leste by smatkovi - 3 days, 16 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 4 days, 14 hrs ago -
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 4 days, 14 hrs ago -
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 4 days, 20 hrs ago - more...
| The Following User Says Thank You to Stskeeps For This Useful Post: | ||
 |
|
2009-02-02
, 15:12
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#12
|
__________________
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
| The Following 5 Users Say Thank You to Stskeeps For This Useful Post: | ||
|
|
2009-02-02
, 17:37
|
|
Posts: 1,101 |
Thanked: 1,185 times |
Joined on Aug 2008
@ Spain
|
#13
|
About the closed source items, this is a field where I think that less is more.
 |
|
2009-02-02
, 17:42
|
|
Posts: 2,535 |
Thanked: 6,681 times |
Joined on Mar 2008
@ UK
|
#14
|
Originally Posted by maacruz
I think the N8x0 users who don't get Fremantle might disagree when they don't have:
About the closed source items, this is a field where I think that less is more.
- Flash
- Operator wizard
- Handwriting recognition & word completion
- Battery charging
- ...
__________________
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
| The Following 2 Users Say Thank You to Jaffa For This Useful Post: | ||
 |
|
2009-02-02
, 17:50
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#15
|
EDIT: Don't reply to this post until you've read the replies below, thanks! 
Why are we being asked to justify every closed-source component? I would think it would be a more simple case than that; can we have the closed source bits for Mer? Yes? Thanks!
It seems weird that Nokia is saying, "Yes, you can have closed source bits, but you have to work for it; you have to justify each one -- why do you need that one? And why do you need that one? Are you really, really sure you need that one? Show me how much you want it. Oh, come on, you can live without that one."
It seems obvious to me that the Mer team isn't asking for closed source bits because they're lazy; you guys are pouring a lot of sweat into this project. Anyone looking at the project can see that you're doing your best to find open source components wherever possible. So it seems kind of insulting to ask you to justify your need for each component. If there were good, easy-to-find open source replacements for these bits, wouldn't Nokia use them instead of developing closed-source versions?
I say you build Mer using as few closed bits as possible, but without losing any functionality found in Diablo. After you've built the thing, tell Nokia what you've got in there, and they can argue with you over the stuff you've got.
If anything, I'd like to see Nokia ask the Mer team, "Have you tried project x instead of our closed-source component y?" I'm pretty sure Nokia's developers looked at the open source offerings before they started in-house development, and the developers probably know all of the alternatives out there. They'd be your best bet to suggest an alternative.
Is Nokia worried that you could build a viable competitor to Maemo 5? They're afraid that they're handing you the weapons that will destroy them?
Naaahh... that's silly...
Or ... IS IT???
Last edited by qole; 2009-02-02 at 20:38.
Originally Posted by Stskeeps
Ok, I guess I wasn't very clear; I'll try again...
...we would like to ask the members of this forum a question, since we will be bringing Fremantle components to the N8x0(W), 770 devices. There are quite interesting discussions with Nokia going on about being able to provide community firmware images through maemo.org to Nokia tablet users, which could include closed source applications, drivers, etc. (see http://wiki.maemo.org/Task:Community...e_distribution). Associated with that we have to provide a list of what packages/applications, bits and pieces of Diablo we would like to distribute as part of these images, for legal discussion.
We would then like to ask you users, what you would expect as part of these future firmware images, and to write why these ought to be part of the community firmware images - why are they important for you to have on your tablet.
Please restrict yourself to the closed source components as part of your answers. If you know of a proper open source replacement for a closed source component, you are welcome to write these as well so we can consider these for inclusion in the standard images. If they are OK to just to be downloadable through the Application Manager, note this as well.
Why are we being asked to justify every closed-source component? I would think it would be a more simple case than that; can we have the closed source bits for Mer? Yes? Thanks!
It seems weird that Nokia is saying, "Yes, you can have closed source bits, but you have to work for it; you have to justify each one -- why do you need that one? And why do you need that one? Are you really, really sure you need that one? Show me how much you want it. Oh, come on, you can live without that one."
It seems obvious to me that the Mer team isn't asking for closed source bits because they're lazy; you guys are pouring a lot of sweat into this project. Anyone looking at the project can see that you're doing your best to find open source components wherever possible. So it seems kind of insulting to ask you to justify your need for each component. If there were good, easy-to-find open source replacements for these bits, wouldn't Nokia use them instead of developing closed-source versions?
I say you build Mer using as few closed bits as possible, but without losing any functionality found in Diablo. After you've built the thing, tell Nokia what you've got in there, and they can argue with you over the stuff you've got.
If anything, I'd like to see Nokia ask the Mer team, "Have you tried project x instead of our closed-source component y?" I'm pretty sure Nokia's developers looked at the open source offerings before they started in-house development, and the developers probably know all of the alternatives out there. They'd be your best bet to suggest an alternative.
Is Nokia worried that you could build a viable competitor to Maemo 5? They're afraid that they're handing you the weapons that will destroy them?
Naaahh... that's silly...
Or ... IS IT???
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
Last edited by qole; 2009-02-02 at 20:38.
| The Following User Says Thank You to qole For This Useful Post: | ||
|
|
2009-02-02
, 18:02
|
|
Posts: 2,535 |
Thanked: 6,681 times |
Joined on Mar 2008
@ UK
|
#16
|
Originally Posted by qole
Ignoring the rest of your post for the moment (which seems to have gone slightly off the reality wagon), Nokia sell devices. Mer uses lots of Maemo open source components.
Is Nokia worried that you could build a viable competitor to Maemo 5? They're afraid that they're handing you the weapons that will destroy them?
Naaahh... that's silly...
Or ... IS IT???
Why would Mer reusing Nokia-shipped closed-source binaries for N8x0 releases "destroy them", or be a viable competitor to Maemo 5?
__________________
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
Andrew Flegg -- mailto:andrew@bleb.org | http://www.bleb.org
 |
|
2009-02-02
, 18:09
|
|
Posts: 4,930 |
Thanked: 2,272 times |
Joined on Oct 2007
|
#17
|
Originally Posted by Jaffa
Of those, Flash is the only one that needs additional closed components. There are ways to handle the Operator Wizard's role (possibly even ones that aren't broken by default, and can have their database updated when a problem is found with it), and several open-source handwriting input methods, and IIRC xvkbd can do completion, so the code's out there. And unless I'm mistaken, Mer already includes (i.e., steals from existing Maemo install) bme.
I think the N8x0 users who don't get Fremantle might disagree when they don't have:
- Flash
- Operator wizard
- Handwriting recognition & word completion
- Battery charging
- ...
You didn't mention it, but I'd put Skype with Flash; those are the two things I can see that have substantial impact on end-users and don't have plausible replacement paths.
As interim components until we get some of those worked out, I'm not averse to other things, but I don't see them as very important.
| The Following User Says Thank You to Benson For This Useful Post: | ||
 |
|
2009-02-02
, 18:10
|
|
Posts: 643 |
Thanked: 628 times |
Joined on Mar 2007
@ Seattle (or thereabouts)
|
#18
|
@qole: It's easiest to understand the situation if you don't think of Nokia as one entity. I have little doubt that if the people working on Maemo were calling the shots we could get anything we wanted, but the issue is that *they* have to justify releasing closed source bits to *their* legal department. Then their legal department has to vet all of the request to make sure Nokia actually *does* own the IP rights to those pieces of software and that it doesn't have some other legal ramifications.
Now, *technically* we could just go ahead and cobble together a release using any Nokia closed source software we wanted to, but there are a couple good reasons why we won't. One of the big reasons is that it completely compromises our goals of working providing on a truly open source alternative distribution. This might also prevent people from being interested in contributing. I know *I* wouldn't contribute to something in such a questionable legal state. I can only imagine some others feel the same.
EDIT: I should emphasize as Stskeeps said further down, that they never asked us for justification. We asked you.
We want to go with open source wherever it makes sense, so we want to find out specifically what functionality people care about the most.
-John
Last edited by Johnx; 2009-02-02 at 18:16.
Now, *technically* we could just go ahead and cobble together a release using any Nokia closed source software we wanted to, but there are a couple good reasons why we won't. One of the big reasons is that it completely compromises our goals of working providing on a truly open source alternative distribution. This might also prevent people from being interested in contributing. I know *I* wouldn't contribute to something in such a questionable legal state. I can only imagine some others feel the same.
EDIT: I should emphasize as Stskeeps said further down, that they never asked us for justification. We asked you.
We want to go with open source wherever it makes sense, so we want to find out specifically what functionality people care about the most.-John
Last edited by Johnx; 2009-02-02 at 18:16.
| The Following 2 Users Say Thank You to Johnx For This Useful Post: | ||
|
|
2009-02-02
, 18:10
|
|
Posts: 4,930 |
Thanked: 2,272 times |
Joined on Oct 2007
|
#19
|
Originally Posted by Jaffa
I do believe you've been Qoled.
Ignoring the rest of your post for the moment (which seems to have gone slightly off the reality wagon), Nokia sell devices. Mer uses lots of Maemo open source components.
Why would Mer reusing Nokia-shipped closed-source binaries for N8x0 releases "destroy them", or be a viable competitor to Maemo 5?
|
|
2009-02-02
, 18:11
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#20
|
Originally Posted by qole
OK, I really have to defuse this one, sorry
Why are we being asked to justify every closed-source component? I would think it would be a more simple case than that; can we have the closed source bits for Mer? Yes? Thanks!
This is -me- asking, what we need to put our focus into looking at trying to make work in Mer. All Nokia has asked for, is a list[1]. No justifications, just what we think would be useful and what we would want to distribute, and to isolate early on as possible to see what would be possible to distribute, both of Nokia applications and 3rd party code. They are doing us a huge favour through this opening, - allowing Mer on tablets to accelerate to Fremantle-level functionality so when Fremantle (and RX-51) comes out, N8x0(W) (and maybe even 770) will have quite similar functionality.
Why we're asking for reasoning, is to make it possible to prioritize our time in determining where it's even worth spending time on trying to integrating the closed source bits.
I say you build Mer using as few closed bits as possible, but without losing any functionality found in Diablo. After you've built the thing, tell Nokia what you've got in there, and they can argue with you over the stuff you've got.
Anyone looking at the project can see that you're doing your best to find open source components wherever possible. So it seems kind of insulting to ask you to justify your need for each component. If there were good, easy-to-find open source replacements for these bits, wouldn't Nokia use them instead of developing closed-source versions?
Is Nokia worried that you could build a viable competitor to Maemo 5? They're afraid that they're handing you the weapons that will destroy them?
[1] http://lists.maemo.org/pipermail/mae...ry/002946.html
__________________
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.
| The Following 5 Users Say Thank You to Stskeeps For This Useful Post: | ||
 |
| Tags |
| mer, mer release firmware |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
All times are GMT. The time now is 07:29.
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.