Active Topics
-
Facebook chat on Nokia N9 - back to life :) (41)
to MeeGo / Harmattan by shakolan - 4 hrs, 27 mins ago -
Any chance to get back mirror.thecust.net ? (3)
to MeeGo / Harmattan by dredlok706 - 4 hrs, 37 mins ago -
TLS 1.2 for N9 is ready (17)
to MeeGo / Harmattan by shakolan - 6 hrs, 8 mins ago -
Pinephone and Pinephone Pro on Leste vs Mobian (0)
to Maemo 7 / Leste by biketool - 12 hrs, 1 min ago -
need .bin for update nokia 770 tablet (17)
to Nokia 770 by amigo157 - 5 days, 9 hrs ago -
I have found alien dalvik rpm (3)
to SailfishOS by HtheB - 5 days, 18 hrs ago - more...
|
2009-09-22
, 18:05
|
|
Posts: 206 |
Thanked: 72 times |
Joined on Jun 2009
@ Switzerland
|
#52
|
Originally Posted by Architengi
In computing, the majority of revenues come from:
I just don't want all my work to be open and free and to live from services (technical support or customizations), just because there is not the same money from that, so in the end I will have to look for a job.
All the developers that make their source code public will take the job and the bread from the hand of other developers.
For example: If Office is free, the developers of Quick Office, WordPerfect, even the MS Office will have to find another job.
For humanity's progress I love Open Source, like I would love no patents. But in todays world even the human genes (made by nature) are patented.
Now, the question is, the companies that researched and found that gene usage, can they get the money back from all that investment in research? The same with the code, if it is not closed and everybody has access to its source, will be the same interest for the companies to produce that code?
- Services.
- Sale of hardware.
- Some custom features/sofwares developed for companys.
The revenues are sufficient for profitable company and pay everybody. (including developers)
If a company relies solely on a community to develop its Free Software, she controls nothing. The company must hire developers and rely on the community to make more.
In addition, each company that uses free software can modify it to suit his needs: he must therefore developers.
So no, the Free Software does not reduce the number of places of work for developers. It's creates.
 |
|
2009-09-22
, 18:26
|
|
Posts: 4,384 |
Thanked: 5,524 times |
Joined on Jul 2007
@ ˙ǝɹǝɥʍou
|
#53
|
@korbe: some numbers to backup your claim, please?
it'd be a shame if y'all are wasting all this time and effort to discuss false assumptions of mythical proportions
it'd be a shame if y'all are wasting all this time and effort to discuss false assumptions of mythical proportions
| The Following User Says Thank You to ysss For This Useful Post: | ||
|
|
2009-09-22
, 18:32
|
|
Posts: 206 |
Thanked: 72 times |
Joined on Jun 2009
@ Switzerland
|
#54
|
Numbers on what?
 |
|
2009-09-22
, 19:00
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#55
|
So, if Maemo from top to bottom was actually fully open source, what would you actually do with it?
This thought is actually fairly reasonable, let me just list items that were OSS'ed that pretty much have tumbleweed surrounding it instead of interested developers contributing and developing and using it - some of them that people actually almost begged to get OSS'ed: WiFi driver (stlc45xx), DSME, alarm framework - and opened frameworks like hildon input method and other examples..
How about instead of going about demanding that everything should be 100% libre that we go and set up an organisation and distribution with what we actually do have OSS, that is capable of giving proper contributions back and actually valuing and using open sourced components when they do come instead of having the source gathering dust somewhere?
EDIT: oh, wait - we -are- working on that.
Last edited by Stskeeps; 2009-09-22 at 19:02.
This thought is actually fairly reasonable, let me just list items that were OSS'ed that pretty much have tumbleweed surrounding it instead of interested developers contributing and developing and using it - some of them that people actually almost begged to get OSS'ed: WiFi driver (stlc45xx), DSME, alarm framework - and opened frameworks like hildon input method and other examples..
How about instead of going about demanding that everything should be 100% libre that we go and set up an organisation and distribution with what we actually do have OSS, that is capable of giving proper contributions back and actually valuing and using open sourced components when they do come instead of having the source gathering dust somewhere?
EDIT: oh, wait - we -are- working on that.
__________________
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.
Last edited by Stskeeps; 2009-09-22 at 19:02.
|
|
2009-09-22
, 19:12
|
|
Posts: 206 |
Thanked: 72 times |
Joined on Jun 2009
@ Switzerland
|
#56
|
Originally Posted by Stskeeps
If Maemo is 100% Free, I can have 100% confidence in him.
So, if Maemo from top to bottom was actually fully open source, what would you actually do with it?
This thought is actually fairly reasonable, let me just list items that were OSS'ed that pretty much have tumbleweed surrounding it instead of interested developers contributing and developing and using it - some of them that people actually almost begged to get OSS'ed: WiFi driver (stlc45xx), DSME, alarm framework - and opened frameworks like hildon input method and other examples..
How about instead of going about demanding that everything should be 100% libre that we go and set up an organisation and distribution with what we actually do have OSS, that is capable of giving proper contributions back and actually valuing and using open sourced components when they do come instead of having the source gathering dust somewhere?
EDIT: oh, wait - we -are- working on that.
And yes, FOSS is not only technical advantages.
But from a technical standpoint, there are advantages to having a 100% FOOS:
- I can work to resolve any bug. Whether a bug that I found or a bug found by a user.
- If I have an idea of new functionality, hop I can develop it, test it. And if it is quality and what I write is good, I can distribute this improvement to the official team.
|
|
2009-09-22
, 19:25
|
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#57
|
But from a technical standpoint, there are advantages to having a 100% FOOS:
- I can work to resolve any bug. Whether a bug that I found or a bug found by a user.
- If I have an idea of new functionality, hop I can develop it, test it. And if it is quality and what I write is good, I can distribute this improvement to the official team.
| The Following 3 Users Say Thank You to lardman For This Useful Post: | ||
|
|
2009-09-22
, 19:49
|
|
Posts: 1,513 |
Thanked: 2,248 times |
Joined on Mar 2006
@ US
|
#58
|
Originally Posted by lardman
My understanding (correct if I am wrong) is that plenty of bugs have been identified and reported in Diablo and will not be fixed by Nokia and cannot be fixed by the community because of the parts in Diablo that are closed. I understand (even if Korbe doesn't like it) why Nokia doesn't completely open source Fremantle. But here is a question for us to ponder:
Which closed source components require this attention from you? I.e. bugs you've spotted and are looking to fix?
How do we know that the bugs and "fixed in Fremantle" situation that occurred with Diablo and the n8x0 NITs won't be repeated with Fremantle and the N900?
|
|
2009-09-22
, 20:03
|
|
Posts: 1,213 |
Thanked: 356 times |
Joined on Jan 2008
@ California and Virginia
|
#59
|
Umm, is there a more open source phone out there?
No?
OpenMoko?
Ok.... what is the argument again? Oh, that Nokia is not Good Enough because it is not 100% FOSS. I mean, most of the OS is open source. And why can you not "trust" it if it is not open source? Is it going to eat you or something? Don't tell me that you are going to read and comprehend every single line of code in Maemo if it was FOSS. Would it be nice, yes it would. Would it be practical, probably not. Nokia has done a lot for open source.
No?
OpenMoko?
Ok.... what is the argument again? Oh, that Nokia is not Good Enough because it is not 100% FOSS. I mean, most of the OS is open source. And why can you not "trust" it if it is not open source? Is it going to eat you or something? Don't tell me that you are going to read and comprehend every single line of code in Maemo if it was FOSS. Would it be nice, yes it would. Would it be practical, probably not. Nokia has done a lot for open source.
__________________
----------------------------------------------------
www.ezschool.com - The best online educational experience.
----------------------------------------------------
www.ezschool.com - The best online educational experience.
|
|
2009-09-22
, 20:10
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#60
|
Originally Posted by SD69
My personal hope - that we'll have a strong enough community development going on that we either
How do we know that the bugs and "fixed in Fremantle" situation that occurred with Diablo and the n8x0 NITs won't be repeated with Fremantle and the N900?
1) never get in the situation or
2) have developers crossing the 'divide' along who's willing to dedicate some time with some fixes and being allowed to publish results with
3) infrastructure and procedures in community to make community variants / SSU's to deliver these fixes or
4) a community which can make a precise request for X source to be opened, along with list of people who can actually do something about the source if it was opened and what they would do..
__________________
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.
 |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 19:05.
Mediated == popular
Last edited by korbé; 2009-09-22 at 17:40.