From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] STF SoWs
Date: Wed, 7 Feb 2024 00:04:49 +0100
Message-ID: <20240206230449.GE6420@pb2> (raw)
In-Reply-To: <CAEEMt2=Ht8Ajdsa=0y540cpEZ7LNibrezQ30L9O-gAA_ArXKgA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2525 bytes --]
On Tue, Feb 06, 2024 at 04:39:51PM -0500, Ronald S. Bultje wrote:
> Hi,
>
> On Tue, Feb 6, 2024 at 4:23 PM Michael Niedermayer <michael@niedermayer.cc>
> wrote:
>
> > What i can and did and do suggest is
> > "Patches submitted for review to the FFMPEG dev mailing list. As well as
> > taking care of all reasonable review comments."
> >
> > If "all reasonable review comments" is not enough then what are other
> > review comments ? Obviously it must be UNreasonable review comments
> >
>
> That's again a strawman. Who decides what is reasonable? Assuming this is
> some community-approved process - e.g. the TC, then how is this different
> from going through TC to get the patch merged?
I think you should sign a SoW that has "Merged in git master" as a
Deliverable for 300 commits you spend half a year of ALL your free time on
This would be best. I will not sign that and it seems you are ok with it.
But lets continue the argument:
Let us first assume there is a blocked set of patches because
otherwise obviously none of this matters.
If you have a contract that says you get payed when code is merged then
you cannot submit an invoice before the code is merged so its up
to you to make that happen. Doing months long debates on the ML bringing
things up to the TC, and there is no gurantee you will succeed or how
long this process would take, it could take months or years. You might
never get payed as the TC might just decide not to agree with you or
might not come to a conclusion.
If you have a contract that says you get payed when you took care of all
reasonable comments then you can submit an invoice once you done that
with documentation what and why is unreasonable.
Now you need to be paid, you can just sit back and wait
In the background FFmpeg and SPI might invoke the TC to verify the
list claimed unreasonable.
If the TC agrees you get paid, and the patches maybe would be applied
If the TC disagrees there would be more work before you are paid
if the TC takes months or comes up with no conclusion. You will need
to be paid
thx
PS: do you have a single person willing to sign this Deliverable you
want ?
If not, how will the STF thing work ?
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
If you fake or manipulate statistics in a paper in physics you will never
get a job again.
If you fake or manipulate statistics in a paper in medicin you will get
a job for life at the pharma industry.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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-06 23:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 2:06 Michael Niedermayer
2024-02-06 14:18 ` Ronald S. Bultje
2024-02-06 15:04 ` Vittorio Giovara
2024-02-06 15:14 ` Michael Niedermayer
2024-02-06 15:21 ` Ronald S. Bultje
2024-02-06 15:26 ` Michael Niedermayer
2024-02-06 15:41 ` Michael Niedermayer
2024-02-06 16:04 ` Niklas Haas
2024-02-06 17:02 ` Ronald S. Bultje
2024-02-06 18:17 ` Michael Niedermayer
2024-02-06 18:48 ` Paul B Mahol
2024-02-07 12:16 ` Nicolas George
2024-02-07 13:11 ` Rémi Denis-Courmont
2024-02-06 20:53 ` Ronald S. Bultje
2024-02-06 21:23 ` Michael Niedermayer
2024-02-06 21:39 ` Ronald S. Bultje
2024-02-06 23:04 ` Michael Niedermayer [this message]
2024-02-07 1:38 ` Ronald S. Bultje
2024-02-07 12:58 ` Michael Niedermayer
2024-02-07 13:08 ` Ronald S. Bultje
2024-02-07 14:44 ` Michael Niedermayer
2024-02-07 17:31 ` Ronald S. Bultje
2024-02-08 4:08 ` Michael Niedermayer
2024-02-07 19:01 ` Leo Izen
2024-02-07 19:53 ` Michael Niedermayer
2024-02-08 12:32 ` Nicolas George
2024-02-08 12:42 ` epirat07
[not found] ` <1C84A3B8-51FD-4E46-8A61-B0A047606152@cosmin.at>
2024-02-07 2:28 ` Cosmin Stejerean via ffmpeg-devel
2024-02-06 18:48 ` Niklas Haas
2024-02-06 15:59 ` Niklas Haas
2024-02-06 14:57 ` Vittorio Giovara
2024-02-06 15:25 ` 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=20240206230449.GE6420@pb2 \
--to=michael@niedermayer.cc \
--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