Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Jean-Baptiste Kempf" <jb@videolan.org>
To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] doc/plans: add a file to list approved projects
Date: Mon, 22 Aug 2022 16:42:48 +0200
Message-ID: <b5236a30-96b3-44d6-b272-cf881b3ac426@www.fastmail.com> (raw)
In-Reply-To: <YwN536J3x1gBS1+Y@phare.normalesup.org>

On Mon, 22 Aug 2022, at 14:43, Nicolas George wrote:
>> Therefore, I don't think those plans documents are useful: "show us
>> the code!".
>
> Try this with your plumber: “Show me my shower fixed and I'll pay you if
> I'm satisfied.” It does not work that way, you have to sign a sales

This is a contract, with paid money and clear objectives.

> quote before the plumber gets to work. This is the kind of mechanism I
> want to find for FFmpeg.

FFmpeg is a volunteer open source project, not a contracting or plumbing initiative.
If the SoW is not done, the money is not paid. This does not work for open source communities.

> Are you suggesting that I propose the headers and documentation for
> AVWriter, that we discuss it and hopefully push it before investing more
> time in the implementation?

You provide a full header and documentation, and then get it discussed.
When there is a consensus for approval of the headers, then, you can code the core of it that matches the headers.
That avoids the "I spent time for nothing" issue.


-- 
Jean-Baptiste Kempf -  President
+33 672 704 734
_______________________________________________
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:[~2022-08-22 14:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 21:49 Nicolas George
2022-08-17 21:49 ` [FFmpeg-devel] [PATCH 2/2] doc/plans: add AVWriter Nicolas George
2022-08-18  6:40   ` Paul B Mahol
2022-08-18 17:23   ` Jean-Baptiste Kempf
2022-08-22 14:55     ` Leo Izen
2022-08-22 14:59       ` Nicolas George
2022-08-18  6:49 ` [FFmpeg-devel] [PATCH 1/2] doc/plans: add a file to list approved projects Anton Khirnov
2022-08-18 17:26 ` Jean-Baptiste Kempf
2022-08-19 16:01   ` Nicolas George
2022-08-19 16:08     ` Jean-Baptiste Kempf
2022-08-22 12:43       ` Nicolas George
2022-08-22 14:42         ` Jean-Baptiste Kempf [this message]
2022-08-22 15:01           ` Nicolas George

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=b5236a30-96b3-44d6-b272-cf881b3ac426@www.fastmail.com \
    --to=jb@videolan.org \
    --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