Chandra wrote:I think there's always the choice. For those who believe in Community OS, there's nothing that can forbid them to work as a team, a motivation to stride for the best they could ever create.
It seems to me like the goal you'd like us to go for is to create an OS where the whole community participates. That's a terrible goal to begin with; the actual goal should be an OS with certain properties (which everyone will disagree on). You mention "the best they could ever create"---"best" by itself means nothing without a metric; what happens if we disagree (e.g., X would like performance, Y would like security, Z would like portability---these are very broad design principles but discussions would take place for even the tiniest decision)? I'll tell you what would happen: People would either fight all the time until they eventually left the project, or they would come to a compromise yielding in an OS that is neither performant, nor secure, nor portable (i.e., not "best" by any definition).
Note that in order to make a point, I have already made two wrong assumptions:
- That everyone is knowledgeable. (What, do we test people or something?)
- That everyone will actually dedicate the necessary amount of time. (I, for one, have a bad record at this.)
Chandra wrote:And for those who have their own goals in life, something different then the rest of the world has, there isn't anything aswell that can stop them from continuing on then work. But there always has been a debate, particularly on the subject of Community OS, so it seems as if there isn't much possibility for a team work over here.
Actually, a place where people have no real world experience would probably go for this and fail, as it has happened countless times before. These are not just guesses we are making even though you refuse to accept the idea. The world isn't a fairly tale---it's unfortunate, but it just doesn't work that way.
Chandra wrote:I believe that a well planned project can still attract huge interests.
You do, but who are you? What experience do you have? Over the many years that people have worked on huge amounts of projects, they have learned something. Do you think your fairy tale belief is better than everyone's experience and that we shouldn't learn from past mistakes?
Chandra wrote:And to the part that "The more people on a project, the longer it take", image what would world be like if everyone was to do his job, himself. I was wondering how would it feel like if I were ever obliged to do my kidney operation myself.
That's the thing---if you want a well-planned project, someone needs to design it. A committee-driven design (rather, a community-driven design) is surely to fail. The alternative is for you, Chandra, to design the OS; however, I, Love4Boobies, have no interest in working in an OS of your design---I'm here because I have my own ideas of what a perfect OS should look like. So, the solution is fairly obvious: You need to design something good, make it happen, then attract developers. That way you will end up with people who are working towards the same goal, since they implicitly agreed to it when they volunteered. Linux might be a community project but it is directed by one man, for the most part.
The kidney thing is a terrible analogy because:
- The doctor and the patient always have the same goal (well, hopefully).
- The doctor might consult with his/her peers, but will make decisions on his/her own.
- There are very few decisions to be made, if any.
Here's a better analogy: Gather everyone on your street and ask them to decorate your house.
You're right that an efficiency criteria would have to be defined, though.