Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] STF SoWs
Date: Tue, 6 Feb 2024 16:26:41 +0100
Message-ID: <20240206152641.GZ6420@pb2> (raw)
In-Reply-To: <CAEEMt2=2ZtEMLneV-rJDo4+_7Zw2i4X7OWhFEfab5-mZHdtbPA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1065 bytes --]

On Tue, Feb 06, 2024 at 10:21:21AM -0500, Ronald S. Bultje wrote:
> Hi,
> 
> On Tue, Feb 6, 2024 at 10:15 AM Michael Niedermayer <michael@niedermayer.cc>
> wrote:
> 
> > On Tue, Feb 06, 2024 at 09:18:20AM -0500, Ronald S. Bultje wrote:
> > > Hi,
> > >
> > > On Mon, Feb 5, 2024 at 9:06 PM Michael Niedermayer <
> > michael@niedermayer.cc>
> > > wrote:
> > >
> > > >       2. Deliverables
> > > > Patches submitted for review to the FFMPEG dev mailing list.
> > > >
> > >
> > > I think the goal is to get patches merged, not submitted.
> >
> > Yes but the individual developer cannot gurantee that.
> >
> 
> In a bad situation, someone could send unmergeable patches and they will
> satisfy the legal requirement above for being paid out. I'm suggesting to
> protect the project against that situation.

yes
how foolproof do we want that wording to be ?

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The worst form of inequality is to try to make unequal things equal.
-- Aristotle

[-- 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".

  reply	other threads:[~2024-02-06 15:26 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 [this message]
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
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=20240206152641.GZ6420@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