News for hackers. Stuff that matters.
Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by dingo_bat on Friday January 15, 2016 @08:48AM (#10909244)
I think democracy is almost the worst way to take decisions when it comes to scientific/engineering things. In an open source project, a single expert should be able to overrule the mass of users/contributors if his point is technically more correct. This is very difficult to consistently achieve in a democracy.

I would love to see the results/conclusion of this research. We would finally get some data-backed insight into why/why not democracy is good for a software project.

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by js8 on Friday January 15, 2016 @09:11AM (#10909358)
Are you familiar with https://en.wikipedia.org/wiki/Condorcet's_jury_theorem ? It basically says that enough independent people voting can give better results than any single of them, which contradicts your theory.

Your thinking is underlined by assumption there is one correct solution to arrive at. But maybe that's actually rarely the case.

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by afarrell on Friday January 15, 2016 @09:49AM (#10909591)
To quote that article: """ This version of the theorem is correct, given its assumptions, but its assumptions are unrealistic in practice. Some objections that are commonly raised: ...

* The theorem doesn't directly apply to decisions between more than two outcomes. """

Additionally, it does not take into account the cost of making the decision, which, under direct democracy, rises quadratically with the number of people that must debate and agree to the decision.

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by js8 on Friday January 15, 2016 @10:00AM (#10909652)
I don't think they are that unrealistic.

I think you would find, if you have n options, one of them is the correct one, and there is slight bias towards the correct one among the decision-makers, a similar theorem still holds (from the central limit theorem).

Regarding the transaction costs, this is a different issue, but I would say that is an issue in any project regardless how things are decided. Nothing in the theorem itself requires the people to actually communicate, they can just become biased towards the correct solution on their own.

It should be also noted that, in the real world, people can decide not to take the vote if they don't feel qualified to decide, further improving the results of the theorem.

(I actually rediscovered the CJT myself when I was interested in how democracy works.)

I think it would be nice to try this on college students, give them some knowledge test (or perhaps two - one in their area of expertise and the other outside their area), and compare the best individual results with the interpretation of the results through voting. I haven't seen anybody trying that, but I think many people would be surprised how well it works. :-)

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by afarrell on Friday January 15, 2016 @10:11AM (#10909718)
> I think you would find, if you have n options, one of them is the correct one, and there is slight bias towards the correct one among the decision-makers, a similar theorem still holds (from the central limit theorem)

You are making too many simplifying assumptions. One of these is that the decision-making process involves a simple up-or-down vote. That is rarely the case in complex discussions. Instead, as the number of folks who can bring up additional points for debate or an n+1th option grows, the length of time spent debating grows quadratically unless there is some procedure (For example, a presiding officer who can cut off debate) to stop it.

> I would say that is an issue in any project regardless how things are decided.

This is definitely incorrect. Decision procedures have a massive impact on how long things take to decide. I have empirically observed this. Student organizations at my university had a word for it: wanking. It was incredibly common at student group meetings.

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by js8 on Friday January 15, 2016 @10:24AM (#10909788)
> This is definitely incorrect. Decision procedures have a massive impact on how long things take to decide.

What I meant was that the quadratic transaction costs apply to any large scale project anyway, because no one can fully understand it. In other words, I see the longer debate as a sign of project complexity, not choice of decision making process.

I agree that bad procedures can lead to indecision, but it's not different from indecisive leader really.

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by logfromblammo on Friday January 15, 2016 @10:18AM (#10909749)
So the contributors appoint a project leader according to relevant expertise, and that leader has final authority in decision-making. But prior to making any decision, the leader solicits independent input from each contributor.
Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by js8 on Friday January 15, 2016 @10:35AM (#10909858)
I am not sure I understand how do you think this is going to improve the probability of making correct decision.

In fact, I think it would be bad to select this "leader" according to his expertise; he should rather be selected according to his ability to produce good consensus by incorporating those different inputs. However, we already have procedures (such as voting) that do that and that we can understand; why then bother selecting a person to do it in a black-box fashion?

In short, if you can reliably decide who is an expert, you can also reliably decide the issue itself. If nothing else than by following the expert in his opinion.

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by logfromblammo on Friday January 15, 2016 @01:06PM (#10910940)
The leader is not producing consensus. The leader is choosing the best of all suggested solutions--including the leader's own solution--without regard to the popularity of any given solution.

Presumably, if the leader is an expert in the field, that person should be able to recognize a good idea, even when it comes from somewhere else.

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by js8 on Sunday January 17, 2016 @08:56AM (#10919455)
> The leader is not producing consensus

I am sorry, that's what he effectively does. The more other person is an expert, more likely is he to agree with the leader if he made the correct choice. You seem to think that good solutions are somehow unpopular but that's contradictory (unless there is somebody acting in bad faith). The best solution actually has the highest probability of being the popular one (otherwise the probabilities of the experts are incorrect).

> Presumably, if the leader is an expert in the field, that person should be able to recognize a good idea

This is exactly what I said. You say "presumably", but it is an assumption.

The point is, you don't actually need him. Everybody can voice their opinion about the best solution, and then they can have a vote. If you think it through, this procedure encompasses your proposal too, because your proposal is just a special case where they all follow (in the voting phase) the opinion of the person they agreed on. And the restriction that they need to agree on the person doesn't help you any.

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by logfromblammo on Monday January 18, 2016 @10:01AM (#10924720)
Consider the case where everyone can generally agree that the leader is qualified to make good decisions, but they cannot agree that everyone is so qualified.
Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by js8 on Wednesday January 20, 2016 @07:36AM (#10937619)
OK. If the 2nd proposition holds, why do you think the agreement in the 1st proposition is correct? If they do think they are not qualified to decide as a group, why do they think they are qualified to correctly select the leader?

But that aside, as I already explained, this is pretty easy to do with voting. All that's needed is that everybody (including the leader) voices their opinion. The people who feel that they are not qualified to make the decision can just vote for what the leader would vote for.

Maybe what you mean is that there is a person A who thinks that person B should get no vote, because they are not qualified enough (or perhaps that some other person C should get more votes, it's a similar deal). But this is already reflected in the "objective" probability of B making the correct decision. So either A's opinion agrees with the probability (through his own probability to make good judgement), in which case it doesn't matter. Or, it disagrees with the probability, and then following A's opinion can only make the result worse.

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by softmodeling on Friday January 15, 2016 @08:51AM (#10909255)
In principle, one tends to agree with the sentence about experts overruling the mass but in fact we don't accept this behaviour in economy or any other aspect of our lives. So, maybe it's the right to do it but I'd love to have more data (and confidence) on that. Also, it's not only about technical decisions but also regarding who decides what feature should be implemented next
Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by TeMPOraL on Friday January 15, 2016 @11:24AM (#10910235)
> in fact we don't accept this behaviour in economy or any other aspect of our lives

I think it's simply because this approach is more prone to abuse. A good dictator leaves democracy in the dust in terms of efficiency, but converesly a bad dictator can make everything go to shit at moment's notice. In economy/politics, it's a matter of life and death. In open-source software, the risks of dictatorship don't matter - someone can always fork the project off and do it better, but even if not, no one is starving or dying because of it.

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by dudul on Friday January 15, 2016 @09:18AM (#10909404)
What do you mean "we don't accept this behaviour in economy"? I believe we very much let experts handle the economy. Or are you talking about the fact that it is a widely criticize state of affair?
Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by oneJob on Friday January 15, 2016 @09:24AM (#10909449)
The Fed Chief is put there by elected officials. Same for Treasury. Same for most of the regulatory agencies. The economy is very much handled by fiscal, monetary, and regulatory policy, which is handled by individuals that are handled by elected officials.

Seriously, the amount of basic misunderstanding of all things not programming related here on HN is starting to get to me. I can't read these threads without being compelled to correct such obvious errors. If you don't know what you're talking about, at least phrase it in a way so that it comes across as an opinion, or better yet, research before you type. It's ruining the quality of these threads.

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by rc4algorithm on Friday January 15, 2016 @11:13AM (#10910163)
It's not like de Raadt or Torvalds got arbitrarily dropped into their positions. People effectively chose them by investing usership and development effort into their projects.
Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by oneJob on Friday January 15, 2016 @09:18AM (#10909407)
This sort of sh*t scares me. Thinking that software is a purely technical endeavor where an expert can always be "right" and thus ignore non experts.
Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by dingo_bat on Friday January 15, 2016 @12:50PM (#10910832)
Note that I do not think non-experts should be ignored. I think everyone should be able to voice their opinion, expert or non-expert. But there should be a final authority where the buck stops, and their word should be final, no matter how many people wanted something else.

Also, I agree that experts are not always right, but they are right in overwhelmingly more cases. Which is practically "always". The small number of times an expert is outright wrong, is a risk I'm willing to take.

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by oneJob on Friday January 15, 2016 @03:47PM (#10912017)
You realize your first sentence is practically the definition for a democratic republic?

I wasn't taking issue with the proposed decision making mechanism. I was taking issue with the idea that there are purely "technical solutions". In math, the most intangible of disciplines, I was taught that when working solving an open problem, the most important question to answer will always be, "So what?" It's easy to come up with novel but trivial proofs all day long. If you can't explain why the new proof is important, then, so what? Go play with Legos.

If such an intangible discipline requires some justification part of its most foundational task, then surely there must be some broader justification in software development. And I'm being specific when I use the term 'software development'. It's not like we're talking about computer science or applied mathematics.

Software development builds things that are to be used by end users for a purpose. There is plenty of room in software development for non-technical perspectives, and non-technical discussions will never be black-or-white. Often a software development project with be built specifically for a non-expert. In that case, to say that the end-user "should not necessarily be ignored" is such a bad tenor to be set for the discussion.

Last, I'd like to mention the idea of a do-ocracy, which is what many OSS projects have organically turned into. In these cases, the technical expert and the novice alike can do whatever they want, because folks will either choose to work with them or not. But in a do-ocracy it's not likely that someone will be forced to do something they don't agree with or at least sign-on-to.

If you want a "buck stops here" set-up, then go to a company that has a hierarchy or pay people to do what you tell them to do. But otherwise, there is no Utopia where programmers can go write whatever software they want and that others will be required to use without getting to share in the decision making process.

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by afarrell on Friday January 15, 2016 @10:13AM (#10909726)
There are other options between unconstrained direct democracy and monarchy by someone who does not listen to colleagues. For example, a model wherein one person makes the final decision but is socially pressured to earnestly listen to the opinions of other members of the community often works well.
Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by softmodeling on Saturday January 16, 2016 @08:09AM (#10915174)
Exactly. Democracy does not imply that all members of the project (including non-technical users) have to vote every single decision.

We could have elections and let elected experts to act unsupervised for a period of time, use liquid democracy (where you delegate your vote when you're not involved in a certain decision),...

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by TeMPOraL on Friday January 15, 2016 @11:26AM (#10910255)
Well, because it is. What scares me is those constant attempts to turn software projects into social gatherings.
Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by oneJob on Friday January 15, 2016 @12:11PM (#10910588)
Yeah, like GitHub. Can you believe how socialist their intro statement is:

"GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over 12.4 million people use GitHub to build amazing things together."

I mean, it doesn't use the word 'technical' once!

Re:Democracy in Open Source: Yes or No? (+ Our Research Prop... by dingo_bat on Friday January 15, 2016 @12:56PM (#10910875)
While the language Github uses to describe themselves has become increasingly "social", and "sharing" and basically political, their success is backed by solid tech and innovation. All the sharing and social aspect of the website is a byproduct of the innovation and technical superiority (owed in part to git).