Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Cosmin Stejerean via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>
Cc: "Cosmin Stejerean" <cosmin@cosmin.at>
Subject: Re: [FFmpeg-devel] VDD 2023, FFmpeg meeting notes, (23-11-2023, 4pm, Dublin)
Date: Mon, 25 Sep 2023 13:16:54 +0000
Message-ID: <0101018acc7c51a0-f22bf67b-e105-4d7f-b6ea-9be72fdd3534-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <20230924164537.GJ3543730@pb2>



> On Sep 24, 2023, at 5:45 PM, Michael Niedermayer <michael@niedermayer.cc> wrote:
> 
> On Sun, Sep 24, 2023 at 04:10:00PM +0100, Ronald S. Bultje wrote:
>> 
>> 
>> I believe the GA should have sole control and ownership over the domain and
>> trademark. I suggested to kindly ask Fabrice to transfer ownership and/or
>> legal control permanently to a non-profit controlled by and composed of
>> only our GA. I believe this can be amicably worked out.  If you believe
>> Fabrice should continue to have *some* (although not *sole*) say over
>> FFmpeg and ffmpeg.org, then we could propose for him to be a GA member,
>> too. I think that makes a lot of sense - he historically has a ton more
>> work in FFmpeg than me.
> 
> 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.

These are legitimate concerns that exist in every member driven non-profit. There are common tools though to deal with this. I'm not proposing anything specific for ffmpeg, I don't get a vote here, but I'm just going to list some suggestions:

- a board, elected by the GA with staggered board seats such that 1/N come up for a vote every year
- rules around how or when something can be put to a vote by the GA
- bylaws requiring a supermajority of the vote such as 2/3 or 3/4 for certain decisions that shouldn't be left to simple majority
- new members of the GA needing to be voted in by existing members in addition to requiring certain criteria for eligibility such as number of commits 

Perhaps some of these things have been considered in the past.  The more important point is that these are common concerns with common tools to deal with them. I don't believe concerns about a name takeover should require an ad-hoc governance model when more common and arguably more equitable governance models exist. 

- Cosmin
_______________________________________________
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".

  parent reply	other threads:[~2023-09-25 13:17 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 [this message]
2023-09-26 13:21       ` Ronald S. Bultje
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=0101018acc7c51a0-f22bf67b-e105-4d7f-b6ea-9be72fdd3534-000000@us-west-2.amazonses.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=cosmin@cosmin.at \
    /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