From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [ANNOUNCE] Repeat vote: GA voters list updates
Date: Tue, 14 Nov 2023 19:44:18 +0100
Message-ID: <ZVPAAvgQPM4Hbnin@phare.normalesup.org> (raw)
In-Reply-To: <2797265.T4TqJhQMIy@basile.remlab.net>
[-- Attachment #1.1: Type: text/plain, Size: 2011 bytes --]
Rémi Denis-Courmont (12023-11-14):
> The French (XIXth century) Empire used notoriously public ballots, and the
> results were skewed to say the least. There is a good reason why ballots are
> supposed to be confidential.
>
> And I don't think FFmpeg is immune to the same sort of issues. Consider the
> case of developers with any kind of corporate affiliation or financial
> dependency. What's to prevent their boss from telling them how to vote if the
> ballots are public?
Nothing prevents their boss from telling them how to vote, even if the
ballots are secret.
The kind of secrecy a remote voting software can give us is “urn-style”
secrecy: once the ballot is in the box, now way of knowing whose ballot
it is.
But to prevent bosses from interfering, we would need
“voting-booth-style” secrecy: secrecy as the ballot is being cast and no
way for the person who cast it to prove what they voted for.
Vote-from-home systems cannot provide voting-booth-style secrecy:
somebody can hover behind your back while you cast your ballot, or even
demand you surrender your secret token.
Urn-style secrecy, the only kind we can have, only protects from casual
interference, like a kind in a conservative family not daring vote
liberal, or an elected official voting against the interests of their
biggest campaign donors. This is obviously not a problem for a libre
software projects where contributors are all over the world and barely
know each others.
Now that the question has been raised and I had a chance to reflect on
it, I think votes should probably be public. For votes about technical
questions, it seems to me quite obvious. For votes about people, like
the one now, it is more doubtful because it can lead to more personal
polarization, but I am rather in favor too.
Also, I will say it here instead of sending a separate mail:
I find the strategy of legal intimidation about the GDPR disgusting.
Regards,
--
Nicolas George
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-11-14 18:44 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 7:22 Thilo Borgmann via ffmpeg-devel
2023-11-11 7:58 ` Anton Khirnov
2023-11-11 9:31 ` Zhao Zhili
2023-11-11 9:39 ` Lynne
2023-11-11 9:42 ` Jean-Baptiste Kempf
2023-11-14 9:28 ` Tomas Härdin
2023-11-14 12:49 ` Thilo Borgmann via ffmpeg-devel
2023-11-14 15:56 ` Tomas Härdin
2023-11-14 16:17 ` Vittorio Giovara
2023-11-14 16:46 ` Rémi Denis-Courmont
2023-11-14 18:44 ` Nicolas George [this message]
2023-11-14 19:15 ` Rémi Denis-Courmont
2023-11-14 20:12 ` Nicolas George
2023-11-14 19:19 ` Ronald S. Bultje
2023-11-14 19:28 ` Nicolas George
2023-11-14 19:32 ` Ronald S. Bultje
2023-11-14 20:10 ` epirat07
2023-11-14 19:34 ` Vittorio Giovara
2023-11-14 21:02 ` Tomas Härdin
2023-11-11 9:54 ` Jean-Baptiste Kempf
2023-11-11 15:35 ` Michael Niedermayer
2023-11-11 16:58 ` Nicolas George
2023-11-11 18:29 ` Jean-Baptiste Kempf
2023-11-11 18:38 ` Michael Niedermayer
2023-11-11 10:28 ` Rémi Denis-Courmont
2023-11-11 11:15 ` Nicolas George
2023-11-11 11:49 ` Rémi Denis-Courmont
2023-11-11 12:08 ` James Almer
2023-11-11 18:43 ` Vittorio Giovara
2023-11-12 13:59 ` Thilo Borgmann via ffmpeg-devel
2023-11-12 14:03 ` James Almer
2023-11-12 14:08 ` [FFmpeg-devel] Poll: " Anton Khirnov
2023-11-12 16:23 ` Nicolas George
2023-11-12 17:31 ` [FFmpeg-devel] [ANNOUNCE] " Michael Niedermayer
2023-11-12 17:43 ` J. Dekker
2023-11-12 18:02 ` Michael Niedermayer
2023-11-12 18:34 ` Anton Khirnov
2023-11-12 21:38 ` Michael Niedermayer
2023-11-12 14:10 ` Paul B Mahol
2023-11-20 15:44 ` Thilo Borgmann via ffmpeg-devel
2023-11-20 16:06 ` Derek Buitenhuis
2023-11-20 16:08 ` J. Dekker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZVPAAvgQPM4Hbnin@phare.normalesup.org \
--to=george@nsup.org \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git