On Wed, Feb 26, 2025 at 2:51 AM Michael Niedermayer <mich...@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-requ...@ffmpeg.org with subject "unsubscribe".
