Le 26 juillet 2025 23:14:08 GMT+03:00, Timo Rothenpieler <t...@rothenpieler.org> a écrit : >> You do it once, decisively, with no point where it is both dev paths >> simultaniously. >> VideoLAN managed it, and countless companies and other projects have managed >> it with >> no overlap. Many of which I have experienced first hand. It's one thing to >> slowly >> move projects from an org/community over, but having several extant methods >> of >> contributing and reviewing the same repo's code is pretty much the #1 thing >> that >> is avoided. > >Videolan hat the exact same transitional period, where both the ML and Gitlab >were in use for at least a couple months to half a year.
That is misleading. Different projects were migrated at different times, over a period of several years. But there never was cohabitation of -devel MLs and gitlab repos for code review and patch submission, for any project. As the one person who had both most contributions and most objections to Gitlab, I think I'd know. >vlc-devel is still active to this day, even with the very occasional stray >patch still landing there, just not for patches. Yes, but that's not Derek's point. Also vlc-devel is pretty moribond at this point. The occasional non-code technical discussions take place mostly in the issue tracker or in meetings. >How do you intend to get everybody into one boat to move over all at once? >VLC has a central governing body who is able to make such decisions and force >the issue if need be. >FFmpeg does not, so I don't see who would be able to make such a call, and >specially then also have everyone follow it. FFmpeg has a GA who can vote on this, just like VideoLAN. It's just not formalised in a legal document. _______________________________________________ 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".
