[tsc-devel] VOTE ANNOUNCEMENT: Voting Rules Change
Quintus |
Sun, 20 Mar 2016 23:16:47 UTC
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
A N N O U N C E M E N T O F V O T E
3rd vote March 20th, 2016
This is a formal vote announcement as per § 5 of the Voting Rules
(VotR), which are available online[1]. A vote that is accepted by the
team results in a final decision on a topic and determines how to
proceed.
Allowed to vote is any team member, which as per § 1 VotR is everybody
who is publically listed as a member of the “Secretchronicles”
organisation on GitHub.
Proponent
°°°°°°°°°
The vote was proposed by datahead <…9@y…> and me,
Quintus <…s@q…>.
Vote Subject
°°°°°°°°°°°°
We make the following proposal to adapt the voting rules so they are
more consistant and more flexible:
- --------------------------------------------------------------------------------
Art. 1
§2(2) is changed to “The vote requires that two thirds of the team
members voting are in favour of adding the new person to the team.”.
§3(1)(Nr.3)(2nd sentence) is changed to “This requires a two thirds
majority of those voting, and the candidate for removal is not allowed
to participate in the vote.”
In §20 the words “of the team members” are replaced with “of all
existing team members”.
Art. 2
A new §5a is introduced after §5 with the following text:
§5a IRC Voting Announcement
(1) For votings held in IRC — as an exception to § 5(2)(Nr.3) — it is
sufficient to announce all available voting options in IRC prior to
taking the votes.
(2) If at least three team members are available in IRC and are not just
idling, it is possible to waive the two-week preparation interval and
vote immediately. The waiver requires all non-idling team members in the
chatroom to agree on it.
(3) Any team member can challenge a voting made under the conditions
of (2) above until two weeks after the declaration of results have
passed by approaching the project lead accordingly. If the voting is
challenged, it is treated the same way as if it failed (§12).
Art. 3
These changes enter into force immediately after the Declaration of
Results of the vote for accepting them.
Any votes running at the moment these changes enter into force are
transferred to the changed version of the rules and do not remain under
the old version.
- --------------------------------------------------------------------------------
For eased readability there is a diff on the voting rules text
attached. Please note however that voting occurs not on the diff, but on
the proposal above. The diff is only for convenience.
This proposal is a rephrased and adapted version of my previous proposal
and merged with datahead’s suggestions. It addresses the following
problems:
* Synchronisation between team membership voting requirements
acquisition and removal voting requirements. Both now require only
2/3 of the people who actually voted (Art. 1)
* Clarification that changes to the voting rules themselves need 2/3 of
ALL team members (Art. 1)
* Changing “cast a vote“ to “participate in the vote” for team removal
vote. This is for clarification.
* Deformalise voting pecularities for voting in IRC (Art. 2)
* Get this into force as soon as possible (Art. 3)
The second-to-last thing is new. When preparing the GD, I noticed
there’s a rather low participation on the scheduling and voting issues,
which makes it pretty impossible to vote on anything in IRC under the
current set of voting rules, as they require every single voting option
to be announced two weeks before the IRC meeting. This is needless
formalism if everybody is in chat and is fine with voting
immediately. Therefore, Art. 2 of the above proposal allows to postpone
the announcement of the actual voting options until the IRC meeting
itself (only requiring the voting topic to be announced two weeks in
advance). This is §5a(1). Even more, §5a(2) allows to completely squash
the two-weeks interval for the vote announcement if everybody in chat is
positively fine with it so we can have a flexible agenda to work
through. If we come up with a new topic to be voted on, we can under the
new rules do that on-the-fly, provided that everybody is fine with that.
The new §5a(3) ensures that people who were not in IRC when voting took
place under the quick procedure can make the vote failed so the same
topic can be voted over again in the more lengthy procedure with the
two-week prepration interval. This is to prevent anybody from feeling
ignored or embarassed.
Or in other words: If we are in IRC, formal hurdles are lowered as far
as possible. They’re only standing in the way there.
Vote Options
°°°°°°°°°°°°
Option 1: Yes (Accept the change)
Option 2: No (Reject the change)
Voting Period
°°°°°°°°°°°°°
The voting period starts on 2015-04-04 00:00 UTC, and it ends on
2015-04-18 00:00 UTC. It also ends if the sufficient 2/3 majority has
been reached.
Note that the General Discussion is scheduled for 2015-04-09. If there
is no final result until that date, the voting will be completed at the
beginning of the General Discussion!
Procedure
°°°°°°°°°
On 2015-04-04 I will post the public Call for Votes (CfV) that
officially opens the voting period. After that you may vote by either
emailing your chosen option to the mailinglist, posting it to the forum
into the topic containing this announcement, or — once the General
Discussion has been opened — taking part in IRC voting (detailed IRC
voting procedure is announced in the General Discussion).
Any vote given before that CfV was posted is ignored. The timespan of
two weeks between this announcement and the CfV is intended to give you
time to decide and prepare, to allow you making last efforts in
convincing others from your opinion, and to decide whether you request a
covert vote (see below).
If no single option receives the most votes (but multiple ones win), a
second vote is held with the same options (there are only two).
This vote is a special vote. As per §20 VotR, changes to the voting
rules document require a 2/3 majority of ALL TEAM MEMBERS. So please:
every team member should vote on this!
Covert vote
°°°°°°°°°°°
Each team member has the right to request a covert vote. A covert vote
means that a technical procedure is employed that prevents everyone from
seeing how anyone else has voted. It is intended to prevent conflicts
within the team or between users and specific team members, and you
should only request this if you really think this is required. More
openness is better for the project.
If the request is made, it must be honoured. I will announce the
technical procedure in that case.
The request must be made before the Call for Votes has been posted, any
further requests for covert votes are ignored.
Quintus
TSC project lead.
[1]: https://github.com/Secretchronicles/documents/raw/master/votingrules/votingrules-2015-08-15.pdf
- --
#!/sbin/quintus
Blog: http://www.guelkerdev.de
GnuPG key: F1D8799FBCC8BC4F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJW7y5lAAoJEPHYeZ+8yLxPOb0H/2n6OPU2FPZgtE3hLmulZEln
lBP3h2UpP0C7EjwKk9hyXjWxb2fYk2350pOhnXFLO+5HQJh4+B3R0eGjmJ9r5lQH
ptxNrMFjM6JooKqSNHiuYYvScrSRdVbwx/yzxfQBEzyC7PQSiZLlCwvPMk7eY3Qd
KCHCwxs84Vd95tWR209zKYejw7hFrnfMIpQ7lNVpGQ2gQhxxm95V9um3z85Txje9
1NknDuyWnt91gi4NwFdDuOYQnbvehq9v2s7qaQ5+oRIadTMAYkcDMXNnS/jR3aKn
Lx+nVKZffKYH3O170o9yIJMJqO3EKKIalvuTUwVzxzGjEzegpvv0GQwCZZKz6UU=
=FfCN
-----END PGP SIGNATURE-----