Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gyan Doshi via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Gyan Doshi <ffmpeg@gyani.pro>
Subject: [FFmpeg-devel] Re: [RFC] Sponsors & Funding
Date: Fri, 12 Sep 2025 12:11:56 +0530
Message-ID: <55fab1ff-f297-4631-bc80-ff6acc482e67@gyani.pro> (raw)
In-Reply-To: <20250911222622.GB29660@pb2>



On 2025-09-12 03:56 am, Michael Niedermayer via ffmpeg-devel wrote:
> Hi Gyan
>
> On Thu, Sep 11, 2025 at 01:41:24PM +0530, Gyan Doshi via ffmpeg-devel wrote:
>>
>> On 2025-09-11 02:22 am, Michael Niedermayer via ffmpeg-devel wrote:
>>> For this subject to make any sense, we need to have the entities
>>> (GA, the community, myself, stefano) disagree.
>>>
>>> I have to point out, that stefano and myself just pass the community
>>> decissions to SPI, so we will not disagree with the community.
>>>
>>> But let us for sake of this rabbit hole, assume, we all disagree.
>>>
>>> I say: green
>>> Stefano says: red
>>> The community says: blue with 90% majority
>>> The GA says: black with 90% majority
>>>
>>> So what will SPI do ?
>>> IMHO, SPI will see me and stefano disagree and consequently will check the
>>> public communication channels and see that the community in public and
>>> in a verifyable way has choosen: blue
>> What is the 'community' in this scenario? Who are the members (and who
>> decides), what is the voting mechanism, who is/are the adjudicators?
> Thats another deep rabbit hole ...
>
> Also, its not one scenario.
>
> Some examples:
> Has there been a governance attack?
> If yes, whatever rules we have had, would have failed.
>
> Or where peoples systems compromised to produce these disagreements.
> If so, the vote needs to be redone, after things are cleaned up.
>
> Or has the community split in N groups fundamentally disagreeing?
> In this case really we would need to talk and bring people back together.
>
> Or is the disagreement maybe about a meaningless bikeshed question, in
> which case maybe we can simply do without an awnser.
>
> So maybe the question, What is the 'community' in such a extreem case is often
> not the right question.
> But technically, if this question must be awnsered, SPI has to decide in such
> an extreem case.

Let's put aside the extreme cases for now. What is the concrete 
definition of the community in normal cases?

Regards,
Gyan
_______________________________________________
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-12  6:42 UTC|newest]

Thread overview: 14+ 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 [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=55fab1ff-f297-4631-bc80-ff6acc482e67@gyani.pro \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=ffmpeg@gyani.pro \
    /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