From: Niklas Haas <ffmpeg@haasn.xyz> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Is the GA democratic ? Date: Tue, 21 Jan 2025 19:49:01 +0100 Message-ID: <20250121194901.GB634940@haasn.xyz> (raw) In-Reply-To: <20250121174149.GL4991@pb2> On Tue, 21 Jan 2025 18:41:49 +0100 Michael Niedermayer <michael@niedermayer.cc> wrote: > Hi > > As people likely know i belive it is not but i got a 2nd opinion: > > > I asked chat gpt this: > [...] The validity and relevance of AI tools notwithstanding, I suggest to take a look at this ChatGPT session: https://chatgpt.com/share/678febb2-a3ac-8003-953c-0b06d78020ba While it tries very hard to maintain a neutral tone throughout, highlighting the strengths of both a democratic and centralized power model in FOSS projects, it does succinctly summarize the current problems in the FFmpeg community and offers a clear solution to our current community woes. I want to highlight some quotes: > In summary, while FFmpeg officially adopts a democratic governance model > with decision-making through consensus and voting, there are indications > that, in practice, the project may still exhibit characteristics of a > BDFL model. This suggests that FFmpeg's governance may align with the > scenario where a democratically elected committee's decisions are > occasionally overridden by a single leader, reflecting a hybrid model with > centralized influences. > > [...] > > Risks of Status Quo: > If contributors perceive that the democratic process is a façade or their > input is consistently disregarded, community morale and trust will erode. > The project may face difficulty scaling or sustaining long-term growth if > contributors disengage, potentially stagnating as competing projects (or > forks) attract disillusioned members. > > [...] > > My Recommendation > > FFmpeg should move toward a more democratic governance model for its > long-term sustainability and growth. The project has grown too large and > essential for authoritarian leadership to remain practical or desirable. > > [...] > > Removing all disgruntled community members and consolidating sole control > under an authoritarian leader may appear to streamline governance in the > short term, but it is rarely a sustainable or beneficial strategy in the > long term. Of course, only a fool would take anything an AI chatbot says at face value. Just some food for thought. > > > > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > No human being will ever know the Truth, for even if they happen to say it > by chance, they would not even known they had done so. -- Xenophanes > _______________________________________________ > 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". _______________________________________________ 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-01-21 18:49 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-01-21 17:41 Michael Niedermayer 2025-01-21 17:53 ` James Almer 2025-01-21 21:10 ` Michael Niedermayer 2025-01-21 23:05 ` James Almer 2025-01-22 16:59 ` Michael Niedermayer 2025-01-22 20:00 ` Nicolas George 2025-01-22 20:53 ` Soft Works 2025-01-21 18:13 ` Kieran Kunhya via ffmpeg-devel 2025-01-21 18:57 ` James Almer 2025-01-21 20:24 ` Kieran Kunhya via ffmpeg-devel 2025-01-21 18:49 ` Niklas Haas [this message] 2025-01-21 19:04 ` Soft Works 2025-01-21 20:34 ` Michael Niedermayer
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=20250121194901.GB634940@haasn.xyz \ --to=ffmpeg@haasn.xyz \ --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