From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>
Subject: Re: [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps
Date: Wed, 26 Feb 2025 14:33:14 -0800
Message-ID: <CABGuwE=bTr23PXdWwiKwUD6hJupn5CYKXJcnige6-s_LgNkV2Q@mail.gmail.com> (raw)
In-Reply-To: <CABLWnS8PobZWOJ2P6wpY=g8pH3bauw6Ov9JTYziF2eZXcO4aVw@mail.gmail.com>
> While people who spent a significant time of their life working on FFmpeg
> may be great developers, their skillset might not be matching the one
> needed to handle a community.
>
> Cmon we've been over these points, let's not rehash the same drama over and
> over, and let the volunteers of the CC do their job.
Hi Vittorio,
A quick reminder that questioning the unelected people who run our
infrastructure in a wholly secretive fashion is unacceptable but
questioning the elected CC is perfectly fine. I thought you knew the
rules here by now.
Regards,
Kieran Kunhya
_______________________________________________
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 22:33 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 [this message]
2025-02-26 23:11 ` Jean-Baptiste Kempf
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='CABGuwE=bTr23PXdWwiKwUD6hJupn5CYKXJcnige6-s_LgNkV2Q@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=kieran618@googlemail.com \
/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