Le keskiviikkona 20. marraskuuta 2024, 20.44.35 EET Michael Niedermayer a écrit : > > > 1. lacks expertiese in some areas > > > > vague attacks on the TC should not be tolerated - either list and provide > > examples or don't disparage elected members of the community > > every TC member knows every part of the project, every specification > every architecture, every decoder, every encoder, every filter, every > demuxer every muxer, every protocol, ...
Of course, they don't know. People on the TC are trusted to take good *informed* decisions. That's why it is accepted for the TC to take time to take decisions. If somebody does not want to spend the time to understand whatever issue is legitimately raised to the TC, then they should not put forward their candidacy. > > > 2. for a growing project there is a point where the TC cannot handle the > > > cases > > > > > > anymore at a acceptable quality > > > > you're not it, chief > > The TC can handle 1 case per month, if the project doubles in size it can > handle 2 cases a month. > If it doubles again, the TC can handle 4 cases a month. > Eventually the TC can handle a billion cases a second, no problem here > > As the project grows, the number or maintainers grows with it. The capacity > of the TC does not grow with it. We can worry about that whence FFmpeg has several thousands of active developers. At that point, I expect that the project would have to be subdivided anyhow. Fedora and Debian are waaaay larger than FFmpeg and their technical committees are running just fine. -- Rémi Denis-Courmont http://www.remlab.net/ _______________________________________________ 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".
