Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: [POLL] [VOTE] code.ffmpeg.org vs. ML
Date: Thu, 18 Sep 2025 14:00:25 +0200
Message-ID: <20250918120025.GU29660@pb2> (raw)
In-Reply-To: <442e6eb-5688-eb5d-c2ea-2130674cfa83@martin.st>


[-- Attachment #1.1: Type: text/plain, Size: 2952 bytes --]

Hi Martin

On Tue, Sep 16, 2025 at 10:54:19PM +0300, Martin Storsjö via ffmpeg-devel wrote:
> On Tue, 16 Sep 2025, Michael Niedermayer via ffmpeg-devel wrote:
> 
> > On Tue, Sep 16, 2025 at 02:12:20PM +0300, Martin Storsjö via ffmpeg-devel wrote:
> > > On Tue, 16 Sep 2025, Michael Niedermayer wrote:
> > > 
> > > > Hi all
> > > > 
> > > > 2 months ago we voted on testing Forgejo vs Gitlab, we picked and tested
> > > > Forgejo. And as said in that vote, (and surprisingly, i have not forgotten it)
> > > > heres the "after testing" discussion and vote
> > > > 
> > > > do we want to keep Forgejo or switch back to the ML workflow
> > > > (or something else)
> > > > 
> > > > F. keep Forgejo as primary forge for patch/git workflow
> > > > M. switch back to the ML for patch/git workflow
> > > > 
> > > > all GA members can vote, by publically replying here with a
> > > > "F." / "Forgejo" vs "M." / "ML"
> > > 
> > 
> > > Any vote on anything that can be even potentially contentious should be made
> > > with closed voting, not requiring everybody to publicly state their
> > > preference.
> > 
> > You mean a "secret ballot"
> > 
> > First, id like to say thanks, for you commenting here, even if we dont
> > agree. I think such debate is a good thing as long as its friendly
> > and you always have been friendly!
> > 
> > my current oppinion on the subject:
> > 
> > The main goal of a secret ballot is to protect the citizen so she can delegate
> > her power to a "office holder" freely
> 
> No, that is not the point at all.

“democracies die behind closed doors.”


> 
> The point is having one's voice and vote count, without needing to disclose
> it publicly.

The purpose of a government is to govern, to make the right decissions
and to take responsibility, especially when the decissions where wrong.

A secret ballot conflicts with this.

Also if you want an example
The classical Assembly (Ekklesia) in ancient greece voted in public

And in most modern Democracies, parliamentary votes are public

In governments where each area has a minister, decissions can be associated
with the specific minister.

There are situations where fully public ballots are bad. like when
deciding military strategy
Or when the citizens elect their representattives (see nicolas reply)


> On potentially contentious matters, people eligible to vote may
> wish to do so, without having to publicly state their preference attached to
> their name.

Certainly. I understand people prefer to have power without having to
stand with their name behind their decission (and take responsibility
if it was the wrong decission)
But i think thats not in the interrest of FFmpeg or the community.

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Nations do behave wisely once they have exhausted all other alternatives. 
-- Abba Eban

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 163 bytes --]

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  parent reply	other threads:[~2025-09-18 12:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16  8:49 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-09-16  9:00 ` [FFmpeg-devel] " Diederick C. Niehorster via ffmpeg-devel
2025-09-16 11:04 ` Timo Rothenpieler via ffmpeg-devel
2025-09-16 11:12 ` Martin Storsjö via ffmpeg-devel
2025-09-16 18:49   ` Michael Niedermayer via ffmpeg-devel
2025-09-16 19:54     ` Martin Storsjö via ffmpeg-devel
2025-09-17  9:41       ` Nicolas George via ffmpeg-devel
2025-09-18 12:00       ` Michael Niedermayer via ffmpeg-devel [this message]
2025-09-16 11:13 ` Martin Storsjö via ffmpeg-devel
2025-09-16 11:54 ` Marvin Scholz via ffmpeg-devel
2025-09-16 13:59 ` Alexander Strasser via ffmpeg-devel
2025-09-16 20:39   ` Michael Niedermayer via ffmpeg-devel
2025-09-16 21:12 ` Balint Marton via ffmpeg-devel
2025-09-17 14:24   ` Timo Rothenpieler via ffmpeg-devel
2025-09-17 18:32     ` Marton Balint via ffmpeg-devel
2025-09-17 23:41       ` Timo Rothenpieler via ffmpeg-devel
2025-09-18  7:02         ` Nicolas George via ffmpeg-devel
2025-09-18  8:52           ` Jacob Lifshay via ffmpeg-devel
2025-09-18  9:15             ` Nicolas George via ffmpeg-devel
2025-09-18  9:49               ` Jacob Lifshay via ffmpeg-devel
2025-09-18 12:18             ` Niklas Haas via ffmpeg-devel
2025-09-18 17:44         ` Marton Balint via ffmpeg-devel
2025-09-17 14:46   ` Niklas Haas via ffmpeg-devel
2025-09-17  3:57 ` Philip Langdale via ffmpeg-devel
2025-09-17  9:42 ` Nicolas George via ffmpeg-devel
2025-09-17 14:44 ` Niklas Haas via ffmpeg-devel
2025-09-18  9:10   ` Zhao Zhili via ffmpeg-devel
2025-09-17 14:53 ` softworkz . via ffmpeg-devel
2025-09-18  9:20 ` Gyan Doshi via ffmpeg-devel
2025-09-19  7:46 ` Peter Ross via ffmpeg-devel

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=20250918120025.GU29660@pb2 \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    /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