Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] [VOTE] Mailing List Voting and Formatting Policies

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] [VOTE] Mailing List Voting and Formatting Policies


Chronological Thread 
  • From: Jonah Aragon <jonah AT triplebit.net>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] [VOTE] Mailing List Voting and Formatting Policies
  • Date: Sat, 4 Nov 2017 18:57:51 -0500

Two things to note about your scenarios. Firstly, these would never be an
issue because changes like these just fall under a simple majority of votes.
The only votes that require a supermajority of sorts are the addition or
modification of TLDs.

The other note being that “YES” != Passing. In your second scenario the “NO”
option is the option that would introduce a new policy or change an existing
one. In this scenario, the default would be “YES” because that would be the
unchanging option. The language doesn’t differentiate between YES and NO, it
just deals with the addition of new policies, modification of existing
policies, and deletion of old policies.

Basically in the second scenario you mentioned, assuming it was a vote that’d
require 66% in the first place, with 60% yes and 40% no, the outcome would be
sticking with software because nothing had enough votes to cause a
modification of existing policies.

I’ll pose this in a way that would require a supermajority of votes. Let’s
say the first was phrased as:

> Will we add .TLD to OpenNIC, yes or no?


This is the straightforward one, with 66% yes votes needed to pass.

The second might be phrased as:

> Should OpenNIC exist without .TLD, yes or no?


Or something silly like that. In this case, 66% of “no” votes would be
required for the TLD to pass, as that’s the outcome that would lead to the
addition of a TLD.

Jonah

> On Nov 4, 2017, at 00:34, Fusl <opennic AT lists.dedilink.eu> wrote:
>
> Changing one of my votes:
>
> 1 NO
>
> reason for this is that this rule can be abused and can't really be
> enforced in a clear way.
>
> Simple example: What I mean is, one expects users to call votes such as
>
>> Do we want to switch software from X to Y?
>
> There's now voting result for yes=40%/no=60% whereas 40% of the community
> wants to switch a specific software and 60% does not want to -> We keep
> using X as software and don't switch.
>
> However, they could also be calling a vote
>
>> Do we want to keep using software X instead of switching to Y?
>
> The result for this voting is yes=60%/no=40% whereas "only" 60% of the
> community wants to keep using the software and 40% does not want to -> We
> no longer want to keep using software X because of how the voting was
> defined.
>
> It's also impossible to enforce to a voting that has more than two possible
> choices (instead of simple yes/no).
>
> So my voting for this is:
>
> 1 NO
> 2 YES
> 3 YES
> 4 YES
> 5 YES
> 6 NO
>
>
> --------
> You are a member of the OpenNIC Discuss list.
> You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org



Archive powered by MHonArc 2.6.19.

Top of Page