|
|
Subscribe / Log in / New account

Who controls glibc?

Who controls glibc?

Posted May 10, 2018 3:08 UTC (Thu) by bferrell (subscriber, #624)
In reply to: Who controls glibc? by yshuiv7
Parent article: Who controls glibc?

> Wait a second. You are saying you can assume someone is agreeing with you, if they don't respond?
> I think there might be some problem with this assumption.

That's actually the concept behind how abstentions are counted... If you abstain, it's not a disagreement, It's counted as if in favor.

At least in areas I've seen it used, which kind of stinks because people thing it means "I disagree, but refuse to vote"


to post comments

Who controls glibc?

Posted May 10, 2018 9:10 UTC (Thu) by karkhaz (subscriber, #99844) [Link]

Systems that have a compulsory voting system typically have abstention as an explicit option, which allows for the kind of protest you mentioned: it is compulsory to cast a vote, but you may cast a vote for "none of the above".

This is used on a national elections level in Australia, where voting is compulsory. There isn't actually a "none of the above" box but it's perfectly legal to turn up to the polling station and hand in a ruined ballot card, which is the defacto way of abstaining.

It's indeed a bit presumptuous to lump "I don't care" with "I strongly disagree with all options" in the absence of a voting system that doesn't distinguish between those options. However, on a software project mailing list, it's not the case that there are a fixed number of options to vote for---if somebody disagrees with all possible proposals that have already been suggested, they're free to introduce an alternative suggestion. So in that context it does seem reasonable to read an abstention as "I don't care about this issue" or "I agree with whatever the current consensus is".


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds