[FFmpeg-devel] [POLL] [VOTE] code.ffmpeg.org

[Lynne]

On 22/07/2025 21:26, Timo Rothenpieler wrote:
> On 22/07/2025 08:15, Hendrik Leppkes wrote:
>> On Mon, Jul 21, 2025 at 3:03 AM Timo Rothenpieler 
>> <timo at rothenpieler.org> wrote:
>>>>>
>>>>> * announce code.ffmpeg.org publically so people can start submitting
>>>>>     and reviewing on it as an alternative to the ML
>>>
>>> Just be aware that merging is not possible, since the sync script will
>>> just force push anything merged away.
>>>
>>
>> That seems like a big oversight to me, and makes me wonder why noone
>> else has asked about it. If we actually start using such a platform,
>> shouldn't the full workflow be represented on it for a fair
>> assessment?
>> Can we work towards enabling merging?
> 
> Forgejo would have to be the main repo to enable merging pull requests.
> We would then first need to shut down our current main repo on 
> git.videolan.org and turn it into a mirror, or make it redirect to Forgejo.
> 
> Then we can just click merge on MRs, and I can enable branch protections 
> again to disallow force pushes.
> 
> My understanding of this was it just being an extended test-drive, not a 
> full on switch yet.

I think it should be no issue to make the current repo redirect to the 
Forgejo instance. Then we can push from both Forgejo and have devs still 
use the old push URL (with a different signature, but we've already had 
to update it once recently).
Force pushing would still be enabled for the "test-drive", though we all
know it'll be what we end up using.