From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [TC] Decision on FF_INTERNAL_FIELDS in libavfilter
Date: Tue, 13 Feb 2024 20:49:47 +0200
Message-ID: <45697A7F-DB26-49AD-825D-AFE305822205@remlab.net> (raw)
In-Reply-To: <ZcuXVhHb/1mbBB0P@phare.normalesup.org>
Hi,
Le 13 février 2024 18:22:46 GMT+02:00, Nicolas George <george@nsup.org> a écrit :
>Martin Storsjo (12024-02-13):
>> The main arguments raised were about API consistency, prevention of
>> accidental inclusions, as well as explicitness in marking a field as
>> public or private.
>
>Too bad the committee neglected to ask for the arguments of the people
>who opposed this. Like having a trial and not listening to the defense.
Speaking as an elected member of another OSS project's TC, I believe that the experienced adult developers on the FFmpeg TC are perfectly capable of reading mailing archives and Trac comments as necessary. In fact, I think it is preferable that they stick to arguments made in public, rather than go out of their way to dig up private information.
Or to follow your metaphor, in a trial, the arguments are made before the jury in public sessions. The deliberations of the jury are kept private to shield members from external pressure.
I don't expect that antagonising the TC members will do you, and any potential future arguments of yours, much good.
_______________________________________________
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-13 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 16:15 FFmpeg Technical Committee
2024-02-13 16:22 ` Nicolas George
2024-02-13 18:49 ` Rémi Denis-Courmont [this message]
2024-02-13 19:14 ` 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=45697A7F-DB26-49AD-825D-AFE305822205@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