Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>,
	Kieran Kunhya <kieran618@googlemail.com>
Subject: [FFmpeg-devel] Re: [RFC] Sponsors & Funding
Date: Sun, 28 Sep 2025 12:31:25 +0100
Message-ID: <CABGuwEm1Rr1U2eKSh-zOOfPSX9b-gPp6JBn-94tigCW0=DaYvw@mail.gmail.com> (raw)
In-Reply-To: <20250928105455.GD29660@pb2>

>
>  - The FFmpeg community will be the decission maker about these funds.
>  - The FFmpeg community will, at any time be able to change the process of
> how these decission are made by public consensus.
>  - In absence of privacy concerns, decissions will be made by public
> consensus amongth the commuity, or if that fails,
>    public vote of the GA members requireing a 2/3 majority to release
> funds for some use.
>  - For cases with privacy concerns, decissions will be made by consensus
> or (2/3 maj) vote amongth the General Assembly.
>

Missing the important part about Michael Niedermayer being allowed to
arbitrarily decide votes are invalid because the GA is rigged or some other
deranged conspiracy.

Here is a quote to that end (Warning: insane verbal diarrhoea):

"Let me provide several independant arguments here.

in the GA system
someone spending 2 days to submit 20 patches and not caring about FFmpeg has
1 vote
someone spending the last 20 years working every day on FFmpeg and
authroing over 20000 commits has 1 vote

A. this is not fair
B1. It is exploitable, the 2nd man could just submit 200 commits each under
     100 pseudonyms to receive 100 votes
B2. It is exploitable, anyone can just hire 20 developers on fiver and
     have them sign NDAs and for less than maybe 20k $ get 20 votes, these
are
     fully KYC-able, they can even travel to a meeting, they are real people
     payed to do some work in FFmpeg, not distingishable from others who
     currently work on ffmpeg for money. In fact the current developers
     already WILL TODAY vote the way their employer wants them to

now if you compare this to the system proportional to commits, it is much
more robust. You can still hire someone to do 20000 commits but thats MUCH
more
expensive. They get vote power but they have to pay in contributions to
FFmpeg.

Really if voting power is not proportional to effort by the developer then
all
kinds of problems arise. (as shown above)
"

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

      reply	other threads:[~2025-09-28 11:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09  8:19 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-09-09  9:02 ` [FFmpeg-devel] " Kieran Kunhya via ffmpeg-devel
2025-09-09 12:02   ` [FFmpeg-devel] SDR debate again Was: " Michael Niedermayer via ffmpeg-devel
2025-09-09 12:11     ` [FFmpeg-devel] " Kieran Kunhya via ffmpeg-devel
2025-09-09 11:49 ` [FFmpeg-devel] " Rémi Denis-Courmont via ffmpeg-devel
2025-09-09 12:10   ` Michael Niedermayer via ffmpeg-devel
2025-09-09 16:29     ` Rémi Denis-Courmont via ffmpeg-devel
2025-09-10 15:48       ` Michael Niedermayer via ffmpeg-devel
2025-09-10 16:21         ` Kieran Kunhya via ffmpeg-devel
2025-09-10 20:52           ` Michael Niedermayer via ffmpeg-devel
2025-09-11  8:11             ` Gyan Doshi via ffmpeg-devel
2025-09-11 22:26               ` Michael Niedermayer via ffmpeg-devel
2025-09-12  0:13                 ` Kieran Kunhya via ffmpeg-devel
2025-09-12  6:41                 ` Gyan Doshi via ffmpeg-devel
2025-09-12 16:06                   ` Michael Niedermayer via ffmpeg-devel
2025-09-28 10:54 ` Michael Niedermayer via ffmpeg-devel
2025-09-28 11:31   ` Kieran Kunhya via ffmpeg-devel [this message]

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='CABGuwEm1Rr1U2eKSh-zOOfPSX9b-gPp6JBn-94tigCW0=DaYvw@mail.gmail.com' \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=kieran618@googlemail.com \
    --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 http://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/ http://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