From: "Jean-Baptiste Kempf" <jb@videolan.org>
To: ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps
Date: Thu, 27 Feb 2025 00:11:39 +0100
Message-ID: <8c1d1b3f-8a76-42c2-9a18-9cc0cef5253d@betaapp.fastmail.com> (raw)
In-Reply-To: <20250226015112.GC4991@pb2>
On Wed, 26 Feb 2025, at 02:51, Michael Niedermayer wrote:
> 1. I agree we need discussions, transparency and maybe IRC or some other
> audio/video form of commuication can be tried. Such discussion should be
> public and open. And they must include admins and main authors.
Great, the mailing list is here for that. It is public and open.
> 2. The CC is overstepping its authority.
Literally, the email just says that the CC is now meeting regularly; what authority can it be overstepping?
People speaking together and meeting is now forbidden?
> 3. About "internal panel", There should not be a "internal panel" dominated
CC was elected by GA. GA is composed of most of the active developers. This is not a random internal panel.
And people active in a project are allowed to talk to each other. How can you deny people the right to talk to each other?
--
Jean-Baptiste Kempf
_______________________________________________
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:[~2025-02-26 23:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 23:04 Marth64
2025-02-26 1:51 ` Michael Niedermayer
2025-02-26 14:22 ` Vittorio Giovara
2025-02-26 22:33 ` Kieran Kunhya via ffmpeg-devel
2025-02-26 23:11 ` Jean-Baptiste Kempf [this message]
2025-02-26 23:51 ` James Almer
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=8c1d1b3f-8a76-42c2-9a18-9cc0cef5253d@betaapp.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