Re: [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org

[Timo Rothenpieler <timo@rothenpieler.org>]

On 7/27/2025 12:44 AM, Michael Niedermayer wrote:
> Hi Timo
> 
> On Sat, Jul 26, 2025 at 10:41:57PM +0200, Timo Rothenpieler wrote:
>> On 7/26/2025 10:24 PM, Kacper Michajlow wrote:
>>> On Sat, 26 Jul 2025 at 22:14, Timo Rothenpieler <timo@rothenpieler.org> wrote:
>>>>
>>>> On 7/26/2025 10:01 PM, Derek Buitenhuis wrote:
>>>>> On 7/26/2025 8:29 PM, Timo Rothenpieler wrote:
> [...]
>>> Also, I don't think the current ML workflow is very sophisticated on
>>> ffmpeg-devel, so there are likely not many tools to migrate to the new
>>> one.
>>
>> You'd be surprised about the sophisticated tooling a lot of people have
>> built around patch wrangling via a mailing-list.
>>
>> A lot of people will need to learn an entire new workflow, and I can
>> absolutely understand that being forced to do so from one day to the next is
>> very disruptive and off putting.
> 
> yes, we need decissions that everyone is on board with, even if they
> did not vote for the winning choice.
> 
> I think the gitlab vs forgejo decission was such a decission, it had
> a very clear outcome.
> 
> This testing period can show that forgejo works better and that it leads
> to more contributors and fewer unreviewed patches.
> Or it can fail to do so.
> 
> I think having the result of that testing, could convince most people
> which is the right choice
> 
> 
> [...]
>>
>>> It's just my personal opinion and it doesn't reflect anyone else in
>>> the community.
>>
>> I'm completely with you that we desperately need to move forward.
>> But there just are a lot of people who've been with the project for a long
>> time who are not comfortable with it or outright reject it.
>> Do we really want to just leave them behind, and not even give them a chance
>> to learn new tools?
> 
> yes, exactly, i think we should make sure everyone moves together
> 
> and just speaking about myself how do i replace git send email ?
> do we have a drop in replacement for that ?

Pretty much just with a push to a branch in your personal fork of 
FFmpeg/FFmpeg on code.ffmpeg.org

When you push to a new branch, git itself will echo you a link to create 
a new Pull Request from it right then.
You can of course also ignore that link and manually create it via the 
Web UI, or use the tea CLI tool to create it.

_______________________________________________
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".