* [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps
@ 2025-02-25 23:04 Marth64
2025-02-26 1:51 ` Michael Niedermayer
0 siblings, 1 reply; 2+ messages in thread
From: Marth64 @ 2025-02-25 23:04 UTC (permalink / raw)
To: FFmpeg development discussions and patches
Dear FFmpeg Community,
We’d like to share an update on the work of the Community Committee
(CC). Starting this week, we will hold a weekly internal panel to
discuss community matters and ensure more structured issue resolution.
One of our key goals is to address some of the lingering discussions
from 2024 while laying a strong foundation for the future. We
recognize that progress will be gradual, but we are committed to
working as a team and presenting unified messaging to improve
communication and transparency. We expect to deliver communications
soon on some issues.
We look forward to continuing to serve the FFmpeg community and
fostering a collaborative and productive environment. Thank you for
your ongoing support and engagement.
On behalf of the CC,
Best regards,
Marth64
_______________________________________________
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".
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps
2025-02-25 23:04 [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps Marth64
@ 2025-02-26 1:51 ` Michael Niedermayer
0 siblings, 0 replies; 2+ messages in thread
From: Michael Niedermayer @ 2025-02-26 1:51 UTC (permalink / raw)
To: FFmpeg development discussions and patches
[-- Attachment #1.1: Type: text/plain, Size: 2060 bytes --]
Hi Marth64
On Tue, Feb 25, 2025 at 05:04:00PM -0600, Marth64 wrote:
> Dear FFmpeg Community,
>
> We’d like to share an update on the work of the Community Committee
> (CC). Starting this week, we will hold a weekly internal panel to
> discuss community matters and ensure more structured issue resolution.
>
> One of our key goals is to address some of the lingering discussions
> from 2024 while laying a strong foundation for the future. We
> recognize that progress will be gradual, but we are committed to
> working as a team and presenting unified messaging to improve
> communication and transparency. We expect to deliver communications
> soon on some issues.
>
> We look forward to continuing to serve the FFmpeg community and
> fostering a collaborative and productive environment. Thank you for
> your ongoing support and engagement.
>
> On behalf of the CC,
There are 3+ parts here
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.
2. The CC is overstepping its authority.
3. There is a huge growing backlog of increasing development issues
id like to work on without having to fight and argue over governance
Id like to backport security fixes, make new releases.
About "internal panel", There should not be a "internal panel" dominated
by videolan developers discussing FFmpeg. If there is such a panel, it
should be the main authors, the people who did spend a significant time
of their life working on FFmpeg. (and you should be included as you seem
good at this, and i should be in it because iam one of the main authors
amongth other things)
Thank you
PS: this is just my initial thought/reply and i may have a better idea
after sleeping over this
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Those who are best at talking, realize last or never when they are wrong.
[-- 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".
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-02-26 1:51 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-02-25 23:04 [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps Marth64
2025-02-26 1:51 ` Michael Niedermayer
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