From: Vittorio Giovara <vittorio.giovara@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps Date: Wed, 26 Feb 2025 15:22:01 +0100 Message-ID: <CABLWnS8PobZWOJ2P6wpY=g8pH3bauw6Ov9JTYziF2eZXcO4aVw@mail.gmail.com> (raw) In-Reply-To: <20250226015112.GC4991@pb2> On Wed, Feb 26, 2025 at 2:51 AM Michael Niedermayer <michael@niedermayer.cc> wrote: > 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. > Thank you for your work trying to steward the community Marth. > > > > 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. > No, they shouldn't, otherwise the CC will be influenced by the project leader *again* and prevented from doing anything actionable *again*. > 2. The CC is overstepping its authority. > No, respectfully, you are. > 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. > Then stop talking about governance, let the current system in place do its job :) > About "internal panel", There should not be a "internal panel" dominated > by videolan developers discussing FFmpeg. It never was or has been, but I agree it should be independent, including from current FFmpeg leadership. > 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) > 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. -- Vittorio _______________________________________________ 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".
prev parent reply other threads:[~2025-02-26 14:22 UTC|newest] Thread overview: 3+ 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 [this message]
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='CABLWnS8PobZWOJ2P6wpY=g8pH3bauw6Ov9JTYziF2eZXcO4aVw@mail.gmail.com' \ --to=vittorio.giovara@gmail.com \ --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