On 3/1/22 23:13, Harlan Lieberman-Berg wrote:
Hello everyone,
I propose the following ballot option for the current GR:
Rationale
========
While I agree that there are some votes which, due to their nature,
may be so controversial that the potential for a person's votes to be
publicly revealed may cause them to change their vote (or opt out of
the election), even among divisive GRs, few rise to that level of
controversy: the RMS GR and the systemd GR being two recent examples
which have provoked ire.
There is something which fundamentally distinguishes the kind of
voting that Debian does from that of a private institution or group,
where minutes and votes are typically kept out of public view: Debian
serves a larger community than the members of the institution. In
that sense, we are more similar to a public body than a private
membership.
Our Social Contract makes this distinction clear: when it says that we
will not hide problems, it immediately emphasizes that the bug
database will be open for public view at all times. Taking the step
to make a particular vote secret should require us to stop and
carefully weigh the costs to the larger community.
I hope this option better strikes the balance between the aspirations
of public visibility and the occasional, pragmatic need for secrecy.
Ballot Option
==========
The changes are available at:
https://salsa.debian.org/hlieberman/webwml/-/commit/82729d07aba7dd7ac641f7e4a87178f34b23efca
A diff follows (the word diff is very confusing, so I've omitted it):
diff --git a/english/devel/constitution.wml
b/english/devel/constitution.wml
index 41cb9dfbd80..7924992d3a7 100644
--- a/english/devel/constitution.wml
+++ b/english/devel/constitution.wml
@@ -226,12 +226,15 @@ earlier can overrule everyone listed
later.</cite></p>
<li>
<p>
- Votes are taken by the Project Secretary. Votes, tallies, and >> - results are not revealed during the voting period; after the >> - vote the Project Secretary lists all the votes cast. The voting
- period is 2 weeks, but may be varied by up to 1 week by the
- Project Leader.
+ Votes, tallies, and results are not revealed during the voting
period.
+ After the vote, the Project Secretary lists all the votes
cast, unless
+ either one of the following is true:
</p>
+ <ol>
+ <li><p>The vote is for a leadership election as defined in
§5.2.</p></li>
+ <li><p>At least 4K Developers have sponsored any single ballot
option
+ which says the votes will be kept secret.</p></li>
The changes are available at: https://salsa.debian.org/hlieberman/webwml/-/commit/82729d07aba7dd7ac641f7e4a87178f34b23efca
A diff follows (the word diff is very confusing, so I've omitted it):
diff --git a/english/devel/constitution.wml b/english/devel/constitution.wml index 41cb9dfbd80..7924992d3a7 100644
- --- a/english/devel/constitution.wml
+++ b/english/devel/constitution.wml
@@ -226,12 +226,15 @@ earlier can overrule everyone listed later.</cite></p>
<li>
<p>
- - Votes are taken by the Project Secretary. Votes, tallies, and
- - results are not revealed during the voting period; after the
- - vote the Project Secretary lists all the votes cast. The voting
- - period is 2 weeks, but may be varied by up to 1 week by the
- - Project Leader.
+ Votes, tallies, and results are not revealed during the voting period.
+ After the vote, the Project Secretary lists all the votes cast, unless
+ either one of the following is true:
</p>
+ <ol>
+ <li><p>The vote is for a leadership election as defined in §5.2.</p></li>
+ <li><p>At least 4K Developers have sponsored any single ballot option + which says the votes will be kept secret.</p></li>
+ </ol>
</li>
<li>
Does this not force people that would like to keep their vote secret to publish that fact in order for it to happen (which might well hint
strongly at how they are likely to vote)?
In reaction to that flaw I suspect you'd then end up with a bunch of public-spirited folk suggesting that option for every vote, in order to
cater to a presumed need for privacy by others.
How about people being able to request a secret ballot in private, by
asking the secretary, who would keep a tally of requests and announce
whether the vote was to be secret before voting started?
BTW I had been persuaded that the published-only-internally option was
not really good enough by subsequent discussion, which is why I've not proposed such an amendment, but perhaps the combination of published-only-internally with option-to-go-secret would actually be
worth having as a ballot option.
On 3/1/22 23:13, Harlan Lieberman-Berg wrote:
Hello everyone,
I propose the following ballot option for the current GR:
Rationale
========
While I agree that there are some votes which, due to their nature,
may be so controversial that the potential for a person's votes to be publicly revealed may cause them to change their vote (or opt out of
the election), even among divisive GRs, few rise to that level of controversy: the RMS GR and the systemd GR being two recent examples
which have provoked ire.
There is something which fundamentally distinguishes the kind of
voting that Debian does from that of a private institution or group,
where minutes and votes are typically kept out of public view: Debian serves a larger community than the members of the institution. In
that sense, we are more similar to a public body than a private
membership.
Our Social Contract makes this distinction clear: when it says that we
will not hide problems, it immediately emphasizes that the bug
database will be open for public view at all times. Taking the step
to make a particular vote secret should require us to stop and
carefully weigh the costs to the larger community.
I hope this option better strikes the balance between the aspirations
of public visibility and the occasional, pragmatic need for secrecy.
Ballot Option
==========
The changes are available at: https://salsa.debian.org/hlieberman/webwml/-/commit/82729d07aba7dd7ac641f7e4a87178f34b23efca
A diff follows (the word diff is very confusing, so I've omitted it):
diff --git a/english/devel/constitution.wml b/english/devel/constitution.wml
index 41cb9dfbd80..7924992d3a7 100644
--- a/english/devel/constitution.wml
+++ b/english/devel/constitution.wml
@@ -226,12 +226,15 @@ earlier can overrule everyone listed later.</cite></p>
<li>
<p>
- Votes are taken by the Project Secretary. Votes, tallies, and - results are not revealed during the voting period; after the - vote the Project Secretary lists all the votes cast. The voting
- period is 2 weeks, but may be varied by up to 1 week by the - Project Leader.
+ Votes, tallies, and results are not revealed during the voting
period.
+ After the vote, the Project Secretary lists all the votes cast,
unless
+ either one of the following is true:
</p>
+ <ol>
+ <li><p>The vote is for a leadership election as defined in §5.2.</p></li>
+ <li><p>At least 4K Developers have sponsored any single ballot
option
+ which says the votes will be kept secret.</p></li>
+ </ol>
</li>
<li>
Resending with not-clearsigned signature this time.
Hello everyone,
I propose the following ballot option for the current GR:
Rationale
========
While I agree that there are some votes which, due to their nature,
may be so controversial that the potential for a person's votes to be publicly revealed may cause them to change their vote (or opt out of
the election), even among divisive GRs, few rise to that level of controversy: the RMS GR and the systemd GR being two recent examples
which have provoked ire.
There is something which fundamentally distinguishes the kind of
voting that Debian does from that of a private institution or group,
where minutes and votes are typically kept out of public view: Debian
serves a larger community than the members of the institution. In
that sense, we are more similar to a public body than a private
membership.
Our Social Contract makes this distinction clear: when it says that we
will not hide problems, it immediately emphasizes that the bug
database will be open for public view at all times. Taking the step
to make a particular vote secret should require us to stop and
carefully weigh the costs to the larger community.
I hope this option better strikes the balance between the aspirations
of public visibility and the occasional, pragmatic need for secrecy.
I have argued against this notion that private votes in some way
contradicts our principles of transparency, but that got no replies whatsoever.
https://lists.debian.org/msgid-search/Yg+tfywh09xmPZFM@debian.org
I think that is a reasonable concern, but I'm not sure how exactly we
are losing transparency here. Let's see; if we were to decide that all
votes are public, then:
- the discussion of the GR itself, the formulation of ballot options,
and the debate about them, is still public and transparent; or at
least as public and transparent as they currently are.
- the final ballot and the call for votes are still public.
- the positions of all the people who participated in the public
discussions is still public.
- the only change is that after the vote, you cannot see how exactly
each individual voted. I understand the argument that Debian decisions
are of public interest. But how exactly being able to know how each of
us voted helps with that? Are we harvesting peoples votes to be able
to throw stuff in their faces stuff like "You say that now, but back
in the day when we voted on XXX you favored YYY? You are part of the
problem!".
I get that knowing what people you like/respect/admire/collaborate
think about an issue can be useful to form your own opinion, but
that's only really useful if done before the vote, not after. And for
that you would need to ask them explicitly anyway.
votes being public brings a few extra bits of transparency
Regarding the 'public as an option' ballot: it's not hard to imagine a(nother)
controversial GR where people voting X>Y would be more likely to make it public, while those voting Y>X would be strongly inclined to keep it private --
therefore creating material for assumptions, which can certainly lead to intimidation.
+ <li><p>At least 4K Developers have sponsored any single ballot option
+ which says the votes will be kept secret.</p></li>
Hi,
On Wed, Mar 02, 2022 at 07:46:16PM -0300, Antonio Terceiro wrote:
[...]
I have argued against this notion that private votes in some way contradicts our principles of transparency, but that got no replies whatsoever.
https://lists.debian.org/msgid-search/Yg+tfywh09xmPZFM@debian.org
I think that is a reasonable concern, but I'm not sure how exactly we
are losing transparency here. Let's see; if we were to decide that all votes are public, then:
s/public/private?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hello everyone,
I propose the following ballot option for the current GR:
Rationale
========
While I agree that there are some votes which, due to their nature,
may be so controversial that the potential for a person's votes to be publicly revealed may cause them to change their vote (or opt out of
the election), even among divisive GRs, few rise to that level of controversy: the RMS GR and the systemd GR being two recent examples
which have provoked ire.
There is something which fundamentally distinguishes the kind of
voting that Debian does from that of a private institution or group,
where minutes and votes are typically kept out of public view: Debian
serves a larger community than the members of the institution. In
that sense, we are more similar to a public body than a private
membership.
Our Social Contract makes this distinction clear: when it says that we
will not hide problems, it immediately emphasizes that the bug
database will be open for public view at all times. Taking the step
to make a particular vote secret should require us to stop and
carefully weigh the costs to the larger community.
I hope this option better strikes the balance between the aspirations
of public visibility and the occasional, pragmatic need for secrecy.
Ballot Option
==========
The changes are available at: https://salsa.debian.org/hlieberman/webwml/-/commit/82729d07aba7dd7ac641f7e4a87178f34b23efca
A diff follows (the word diff is very confusing, so I've omitted it):
diff --git a/english/devel/constitution.wml b/english/devel/constitution.wml index 41cb9dfbd80..7924992d3a7 100644
- --- a/english/devel/constitution.wml
+++ b/english/devel/constitution.wml
@@ -226,12 +226,15 @@ earlier can overrule everyone listed later.</cite></p>
<li>
<p>
- - Votes are taken by the Project Secretary. Votes, tallies, and
- - results are not revealed during the voting period; after the
- - vote the Project Secretary lists all the votes cast. The voting
- - period is 2 weeks, but may be varied by up to 1 week by the
- - Project Leader.
+ Votes, tallies, and results are not revealed during the voting period.
+ After the vote, the Project Secretary lists all the votes cast, unless
+ either one of the following is true:
</p>
+ <ol>
+ <li><p>The vote is for a leadership election as defined in §5.2.</p></li>
+ <li><p>At least 4K Developers have sponsored any single ballot option + which says the votes will be kept secret.</p></li>
+ </ol>
</li>
<li>
- --
Harlan Lieberman-Berg
~hlieberman
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEELyAgabIlUqb16FUfGikbTg3OS1cFAmIe7pJfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDJG MjAyMDY5QjIyNTUyQTZGNUU4NTUxRjFBMjkxQjRFMERDRTRCNTcACgkQGikbTg3O S1d5zQ/9F9rMHgeOnEyXWkZ1gIAabwjzY5IedPkoEGECaGz9uiYA446J/Q+jH5V6 blDNcTmy3VL8YxrPJ1NKhwYpF7SCL0QxUnCXiFtp5UFYzCiDWqWGHM4UbqPMZxox 8Z3/oDu7W5N8aa9GHSsL0f6aHtxBHxIS/CnA+wtOIGuGEpHQRxGhqQ0P17pbPkDn bOMbPC9x2Sve2bwzZ4hlvCySRGVorwKNWsvjZ7LWCc5k6a1ZLBYFQK065J6l17NN 6+rEBZ8yJ6UHnQ9wH1Y7loM8B4Z35qgf6MwXyeqMYHSRSrmfAc2uIp/EL4FStig2 4wWiNEyN6QuWkR75Tr3ZSNC+2NF3ptRmM+gc2nBWhz6Zx+yVm5JmvRHkGQfsTrRD 0NtVTflHIOHGsFHYj16IHmC1Xvu/9OHvf4bQumahIG88Rz58Zgsi965FaDTRn5di FtAxKoxsqzvKAe0OJkUHOnSVnv3w95UNg0uco5tgbUmDYISlFYNTHav0gL1EQBR2 GeNYNlJP6zlFEu6uxZuXlfv3BLNvQ4Yc2miE9Rv14bKEd1QizPVUGpX5YR8a89Ph QF2tSdy62MFqRrV9VKmheEnNb2uNsttFJci6ZBjci32zP6mMMFEgUuvgfl2CaMbG MUBi7dtjYkoL3IQuj+OsF5VKZLq2ERJhIDf8mogzetUWNT8aQVo=
=5e/l
-----END PGP SIGNATURE-----
I think, 4K puts the bar very high (that would require 20 people).
However, to generate further discussion, I do agree with Judit [1] that
4K seems like a high bar.
In practice, the way that I would like to see this work is that a
ballot option is proposed with no content other than turning the
ballot to a secret option. Then people can, regardless of their
position on the issue, second that ballot option to avoid splitting
the vote.
(...)
If it is your intention that making the ballot secret extends the discussion time (as adding a ballot option would), then also: Amend
A.1.4. to read, "The addition of a ballot option, the change via an amendment of a ballot option, or a successful call for a secret ballot changes the end of the discussion period..."
I think that's a more elegant solution. Adapted into https://salsa.debian.org/hlieberman/webwml/-/commit/7c4d89528a50345b0bd0e67d9d36499413d9d6c1.
I hereby amend this proposal, unless any of the seconding Developers
(CCed) objects. The diff follows:
commit 7c4d89528a50345b0bd0e67d9d36499413d9d6c1
Author: Harlan Lieberman-Berg <hlieberman@setec.io>
Date: Sat Mar 5 16:01:26 2022 -0500
Change language as suggested by rlaager
diff --git a/english/devel/constitution.wml b/english/devel/constitution.wml index 7924992d3a7..4830c972df9 100644
--- a/english/devel/constitution.wml
+++ b/english/devel/constitution.wml
@@ -225,16 +225,10 @@ earlier can overrule everyone listed later.</cite></p>
</li>
<li>
- <p>
- Votes, tallies, and results are not revealed during the voting period.
- After the vote, the Project Secretary lists all the votes cast, unless
- either one of the following is true:
- </p>
- <ol>
- <li><p>The vote is for a leadership election as defined in §5.2.</p></li>
- <li><p>At least 4K Developers have sponsored any single ballot
option
- which says the votes will be kept secret.</p></li>
- </ol>
+ <p>Votes, tallies, and results are not revealed during the voting period.
+ If, during the discussion period, at least 4K Developers call for a secret
+ ballot, then the votes are kept secret. Otherwise, after the vote, the
+ Project Secretary lists all the votes cast.</p>
</li>
<li>
@@ -854,12 +848,12 @@ plebiscites, where stated above.</p>
proposed disagree with that change within 24 hours. If any of them do
disagree, the ballot option is left unchanged.</li>
- <li>The addition of a ballot option or the change via an amendment of a
- ballot option changes the end of the discussion period to be one week
- from when that action was done, unless that would make the total
- discussion period shorter than the minimum discussion period or longer
- than the maximum discussion period. In the latter case, the length of
- the discussion period is instead set to the maximum discussion
+ <li>The addition of a ballot option, the change via an amendment of a ballot
+ option, or a successful call for a secret ballot changes the end of the
+ discussion period to be one week from when that action was done,
unless that
+ would make the total discussion period shorter than the minimum
discussion
+ period or longer than the maximum discussion period. In the latter
case, the
+ length of the discussion period is instead set to the maximum discussion
period.</li>
<li>The proposer of a ballot option may make minor changes to that
Sincerely,
I hereby amend this proposal, unless any of the seconding Developers
(CCed) objects. The diff follows:
commit 7c4d89528a50345b0bd0e67d9d36499413d9d6c1
Author: Harlan Lieberman-Berg <hlieberman@setec.io>
Date: Sat Mar 5 16:01:26 2022 -0500
Change language as suggested by rlaager
diff --git a/english/devel/constitution.wml b/english/devel/constitution.wml >index 7924992d3a7..4830c972df9 100644
--- a/english/devel/constitution.wml
+++ b/english/devel/constitution.wml
@@ -225,16 +225,10 @@ earlier can overrule everyone listed later.</cite></p>
</li>
<li>
- <p>
- Votes, tallies, and results are not revealed during the voting >period.
- After the vote, the Project Secretary lists all the votes cast, >unless
- either one of the following is true:
- </p>
- <ol>
- <li><p>The vote is for a leadership election as defined in >§5.2.</p></li>
- <li><p>At least 4K Developers have sponsored any single ballot
option
- which says the votes will be kept secret.</p></li>
- </ol>
+ <p>Votes, tallies, and results are not revealed during the voting >period.
+ If, during the discussion period, at least 4K Developers call for a >secret
+ ballot, then the votes are kept secret. Otherwise, after the vote, the
+ Project Secretary lists all the votes cast.</p>
</li>
<li>
@@ -854,12 +848,12 @@ plebiscites, where stated above.</p>
proposed disagree with that change within 24 hours. If any of them do
disagree, the ballot option is left unchanged.</li>
- <li>The addition of a ballot option or the change via an amendment of a
- ballot option changes the end of the discussion period to be one week
- from when that action was done, unless that would make the total
- discussion period shorter than the minimum discussion period or longer
- than the maximum discussion period. In the latter case, the length of
- the discussion period is instead set to the maximum discussion
+ <li>The addition of a ballot option, the change via an amendment of a >ballot
+ option, or a successful call for a secret ballot changes the end of the
+ discussion period to be one week from when that action was done,
unless that
+ would make the total discussion period shorter than the minimum
discussion
+ period or longer than the maximum discussion period. In the latter
case, the
+ length of the discussion period is instead set to the maximum discussion
period.</li>
<li>The proposer of a ballot option may make minor changes to that
I still hope that this option receives enough seconds to go on the
ballot as an intermediary position between the current options of
"always secret" and "never secret except for DPL elections".
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 48:23:52 |
Calls: | 6,710 |
Calls today: | 3 |
Files: | 12,243 |
Messages: | 5,354,640 |
Posted today: | 1 |