From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02
Date: Thu, 01 Feb 2024 22:10:59 +0200
Message-ID: <2785693.8HhBItc6dF@basile.remlab.net> (raw)
In-Reply-To: <CABLWnS8R7azZ5paPZcHF_0jWD2OSwZJrF+--EQSfvQmMWrCMNw@mail.gmail.com>
Le torstaina 1. helmikuuta 2024, 19.45.52 EET Vittorio Giovara a écrit :
> The same of course should apply to any other future funding, it must be
> either the community (via GA) or a third party setting up the sponsorship.
Neither the community or the GA can forbid people from seeking funding for
themselves. I suppose that, in theory, developers could be required to sign an
agreement to that effect before they are allowed to submit code for inclusion,
but that seems neither practical, nor desirable to me.
That is probably not what you meant, but that is what this reads like.
Frankly, if Thilo secures the funding, it's between him and the German
authorities what they want to spend it on, as long as it remains within the
boundaries of applicable laws. If he can come with a project to fund Michael
to maintain FFmpeg for a while, FFmpeg will be no worse off.
Nobody should claim to represent FFmpeg without any kind of preexisting
delegation to do so. If that was done, then that is very morally wrong. But
realistically, we cannot enforce that. Some people did it in the past and will
continue to do it in the future. It is effectively up the other parties to
perform due diligence and not get fooled - if they even care. STF probably
does not care; NAB most certainly does not care.
Moreover pretenses of this process being open need to be dropped. It's not
open if any and all objections are summarily rejected to put it politely. A
short deadline is not an excuse, even if it was unavoidable. (And I remain
unconvinced that public discussion could not start earlier than they did.)
Ultimately, whatever comes out of this does not get any special exemption from
code review standards and TC oversight, but that should be a given. Therefore
this funding should much preferably be used toward as uncontroversial tasks as
possible: Maintainance is a good example. SDR is a counter-example.
With that long side note, while I agree with most of what you said otherwise,
I don't think that there is any merit to excluding Michael from this process,
doubly so if there are too few viable proposals.
--
雷米‧德尼-库尔蒙
http://www.remlab.net/
_______________________________________________
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".
next prev parent reply other threads:[~2024-02-01 20:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 4:29 Michael Niedermayer
2024-02-01 17:45 ` Vittorio Giovara
[not found] ` <686A824A-CF8F-4D38-ADFA-C84362DE866F@cosmin.at>
2024-02-01 17:49 ` Cosmin Stejerean via ffmpeg-devel
2024-02-01 19:13 ` Michael Niedermayer
2024-02-01 19:42 ` Jonatas L. Nogueira via ffmpeg-devel
2024-02-01 21:04 ` Michael Niedermayer
2024-02-01 20:10 ` Rémi Denis-Courmont [this message]
2024-02-06 15:14 ` Vittorio Giovara
2024-02-03 3:37 ` Michael Niedermayer
2024-02-03 12:13 ` Stefano Sabatini
2024-02-04 0:42 ` Michael Niedermayer
2024-02-04 10:11 ` Paul B Mahol
2024-02-11 12:38 ` Michael Niedermayer
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=2785693.8HhBItc6dF@basile.remlab.net \
--to=remi@remlab.net \
--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