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 <michael@niedermayer.cc>
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: Wed, 27 Sep 2023 12:00:43 +0200
Message-ID: <20230927100043.GP3543730@pb2> (raw)
In-Reply-To: <CAEEMt2=DixSXH5p4xBE7grFHaO8zGwVP-FczLXfFku_fCbWv3Q@mail.gmail.com>


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

On Tue, Sep 26, 2023 at 03:21:49PM +0200, Ronald S. Bultje wrote:
> 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.)

you say you agree, but then you continue talking in disagreement


> 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.)

What we have currently is not a king making decissions.
What we have currently is the founder having a final (very difficult to use)
veto power to prevent something catastrophic

Also
What we have currently is not some random entity being in control of the
zonefile.
What we have is the zonefile on our server. Where our admins make changes
to it as our developers ask for. We did not had a dispute but if we had one
the TC and GA would decide what happens with the zonefile.

I think polling the developers if they want this power is not asking
the right question, because they have as much power already, as possible.

I think its better to keep fabrice as the one who has this final veto power
We have no dispute but if we imagine we had one.

I trust fabrice to act in the best interrests of the community. That is to
enact the democratic choice.

I do not trust a complex government structure to act in the best interrests
of the community and act within what the majority wants or whats best for the
majority.

Complex governance structures fail in complex ways, legal structures need
people willing to go to court even if not doing so would be better for them
in every form.

We see corruption and abuse of power in almost every government around the
world. I do not think we should move to such a system and expect different.

Also setting up such a legal entity and governance structure around the
domain will cost money and time, there are setup costs, there are yearly
costs. Also the people in the structure will want to be paid, maybe
you find a person doing it for free today but eventually teh set of
candidates who want to manage access to the "domain keys" for free
will be down to increasingly corrupt people. It may even be someone
like a bot net admin if you are unlucky enough.
And if you actually elected such a person as "treassurer" once your
not getting the domain back not with all your legal structurers in place

So again, fabrice is IMO the choice that is safe, simple and proofen

Fabrice has nothing to gain from (ab)using this power. Everyone
else who wants to guard  the final veto power for free probably has
something to gain from it.

Thanks

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I have often repented speaking, but never of holding my tongue.
-- Xenocrates

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 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".

  reply	other threads:[~2023-09-27 10:00 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
2023-09-27 10:00         ` Michael Niedermayer [this message]
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=20230927100043.GP3543730@pb2 \
    --to=michael@niedermayer.cc \
    --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