From: "Ronald S. Bultje" <rsbultje@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] VDD 2023, FFmpeg meeting notes, (23-11-2023, 4pm, Dublin) Date: Tue, 26 Sep 2023 15:21:49 +0200 Message-ID: <CAEEMt2=DixSXH5p4xBE7grFHaO8zGwVP-FczLXfFku_fCbWv3Q@mail.gmail.com> (raw) In-Reply-To: <20230924164537.GJ3543730@pb2> Hi Michael, On Sun, Sep 24, 2023 at 6:45 PM Michael Niedermayer <michael@niedermayer.cc> wrote: > I disagree > * Who is and is not a member of the GA is in flux, there can be disputes > even on GA membership. > * You cannot have something owned by a group like that. There needs to be > an individual like a treassurer who has the actual key. > So you again trust one person, this is not different from what it is > now. > > Also democracies can make really bad decissions. Which iam sure you have > never seen occur ;) > > And last but not least, this is attackable even unintentionally > you just need for a single moment a majority in the GA that is > bad. This is not hard to reach, a group can easily pose as enough > active developers to achieve 51% and if the domain then really is > legally controlled by the GA. yeah goodby domain > this is not a scenario possible with fabrice having theretical veto > power. > So Yes, i strongly favor fabrice keeping this veto power. > Yes, these are good points / concerns, and I share most of this. (I think it's important to state this explicitly.) So, the question is: do you think we can find a middle ground here where you and I (and other GA members, obviously) might agree on what legal entity could be the holder of this "certificate of ownership"? And do you think it would make sense that in practice, one person elected by (for example) the TC or GA actually practically "has" that key, in the role of executing the "will of the assembly" (similar to treasurer, indeed)? I think we're essentially trying to define a democratic governance model here. Or do you explicitly think that Fabrice owning it is the only good way forward? (More like a benevolent king model.) And sure i can probably word above mail more convincingly if i go > over it 3 times and send it tomorrow but i belive you understand > my point even with it just roughly worded > <signal> Thumbs-up-emoji.</signal> Ronald _______________________________________________ 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-09-26 13:22 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-24 8:37 Kyle Swanson 2023-09-24 9:21 ` Matthias Dressel 2023-09-24 10:09 ` Michael Niedermayer 2023-09-24 10:13 ` Jean-Baptiste Kempf 2023-09-24 22:14 ` Derek Buitenhuis 2023-09-24 15:31 ` Ronald S. Bultje 2023-09-24 17:12 ` Nicolas George 2023-09-27 18:03 ` Michael Niedermayer 2023-10-04 14:51 ` Anton Khirnov 2023-09-24 12:36 ` Marton Balint 2023-09-24 13:46 ` Michael Niedermayer 2023-09-24 15:10 ` Ronald S. Bultje 2023-09-24 16:45 ` Michael Niedermayer [not found] ` <119D9DAB-2F0B-427B-A7D1-063C0AF7C3BD@cosmin.at> 2023-09-25 13:16 ` Cosmin Stejerean via ffmpeg-devel 2023-09-26 13:21 ` Ronald S. Bultje [this message] 2023-09-27 10:00 ` Michael Niedermayer 2023-09-27 13:29 ` Vittorio Giovara 2023-10-03 18:50 ` Nicolas George 2023-10-03 19:13 ` Vittorio Giovara 2023-10-03 19:29 ` Kieran Kunhya via ffmpeg-devel 2023-10-04 14:23 ` Michael Niedermayer 2023-10-04 15:06 ` Anton Khirnov 2023-10-05 12:55 ` Nicolas George 2023-10-05 17:32 ` Vittorio Giovara 2023-10-05 18:33 ` Michael Niedermayer 2023-10-05 19:45 ` Rémi Denis-Courmont 2023-10-05 19:54 ` Nicolas George 2023-10-05 19:00 ` Nicolas George 2023-10-04 15:11 ` Rémi Denis-Courmont 2023-10-03 19:29 ` Rémi Denis-Courmont 2023-10-03 19:36 ` Leo Izen 2023-09-26 19:26 ` Anton Khirnov 2023-09-26 18:44 ` Anton Khirnov 2023-09-27 13:15 ` Tomas Härdin 2023-10-02 9:55 ` Nicolas George 2023-10-03 18:41 ` Nicolas George
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='CAEEMt2=DixSXH5p4xBE7grFHaO8zGwVP-FczLXfFku_fCbWv3Q@mail.gmail.com' \ --to=rsbultje@gmail.com \ --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