Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Cosmin Stejerean <cosmin@cosmin.at>
Subject: Re: [FFmpeg-devel] SWS cleanup / SPI Funding Suggestion
Date: Wed, 18 Oct 2023 23:53:45 +0200
Message-ID: <ZTBT6RFtMrjNdzfG@mariano> (raw)
In-Reply-To: <0101018b3e934739-8f4f53ff-b0a5-4f65-aeae-d73c8b5b6f52-000000@us-west-2.amazonses.com>

On date Tuesday 2023-10-17 16:58:41 +0000, ffmpeg-devel Mailing List wrote:
> 
> 
> > On Oct 17, 2023, at 7:36 AM, Michael Niedermayer <michael@niedermayer.cc> wrote:
> > 
> > On Sat, Oct 14, 2023 at 07:53:04PM +0200, Stefano Sabatini wrote:
> >> 
> >> It would be useful at this point to define the process to accept the
> >> proposal and potential candidates. We have a technical committee which
> >> might take the lead on that and probably have the last word on it,
> >> since "approved by the community" is a bit vague and there is the risk
> >> that there will be never an approval "from the community" because of
> >> diverging views, or that we get stuck at the design level.
> > 
> > I think there are several shades of this
> > 
> > The community might simply have a consensus that X should be funded.
> > We achieved this both for traval and hw in all or nearly all cases.
> > And quite plausibly we will achieve this too for other cases
> > 
> > Hypothetically the community might have a consensus some work should
> > be funded but not agree on technical details.
> > Here honestly i think the developer doing the work should be the main
> > decission maker. She is the one doing the work, knowing the code best.
> > And most likely its one of the FFmpeg team doing the work.
> 

> I think this makes sense for cases where there is easily reachable
> consensus. What happens when we can't easily reach consensus? For
> example it doesn't seem like we have consensus on funding
> improvements to swscale (compared to integrating a 3rd party
> library). Does that mean that work cannot get funded through SPI?
> 

> This is where I think using the TC to make a decision where the
> community at large cannot reach consensus might be useful. It
> doesn't need to decide the fine technical points of how the work is
> done, but it can provide a useful mechanism to disagree and commit
> about whether the work should be done at all and provide the broad
> strokes (like improve swscale vs write a brand new library vs
> integrate some third party one).

+1

And we should try to prevent both later complaints ("it was decided
against my will") or block development because a single or a minority
of developers is against it.

OTOH voting/decision making should only be seeked out in case there is
some disagreement which cannot be resolved during the preliminary
discussion on list/chat, or in case there is more than one candidate
for the task.

I cannot comment about what exact party should be called out (TC vs
GA).
_______________________________________________
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-10-18 21:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 19:19 Michael Niedermayer
2023-10-13 20:30 ` Vittorio Giovara
2023-10-13 21:23   ` Lynne
2023-10-13 22:02   ` Michael Niedermayer
2023-10-13 22:34 ` Niklas Haas
2023-10-13 22:42   ` James Almer
2023-10-13 22:54     ` Niklas Haas
2023-10-13 23:00       ` Vittorio Giovara
     [not found]         ` <8A960BE2-8364-4AF8-A9B5-E0551C19F9DF@cosmin.at>
2023-10-13 23:16           ` Cosmin Stejerean via ffmpeg-devel
2023-10-14 14:19             ` Kieran Kunhya
2023-10-14 17:00               ` Michael Niedermayer
2023-10-14 17:24                 ` Niklas Haas
2023-10-15 14:36                   ` Michael Niedermayer
2023-10-14 17:41                 ` Kieran Kunhya
2023-10-14 19:38                 ` Vittorio Giovara
2023-10-14 17:26               ` Anton Khirnov
2023-10-14 15:45             ` Michael Niedermayer
2023-10-14 17:53 ` Stefano Sabatini
2023-10-17 14:36   ` Michael Niedermayer
     [not found]     ` <430D0C5B-53A8-4920-B99A-D8BAD816D715@cosmin.at>
2023-10-17 16:58       ` Cosmin Stejerean via ffmpeg-devel
2023-10-18 21:53         ` Stefano Sabatini [this message]
2023-10-17 18:33   ` James Almer
2023-10-17 18:50 ` Rémi Denis-Courmont
2023-10-17 21:57   ` Michael Niedermayer
2023-10-17 22:10     ` Michael Niedermayer
2023-10-18 16:30     ` Rémi Denis-Courmont
2023-10-18 22:12       ` Stefano Sabatini

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=ZTBT6RFtMrjNdzfG@mariano \
    --to=stefasab@gmail.com \
    --cc=cosmin@cosmin.at \
    --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