[FFmpeg-devel] Recommendations to facilitation patch reviews on forgejo/ML?

[Romain Beauxis]

Le jeu. 31 juil. 2025 à 06:12, Rémi Denis-Courmont <remi at remlab.net> a écrit :
>
>
>
> Le 30 juillet 2025 00:42:41 GMT+03:00, Romain Beauxis <romain.beauxis at gmail.com> a écrit :
> >Hi all,
> >
> >Are there any recommendations on how to best get attention to some
> >patches/changes?
> >
> >With the introduction of the new forgejo workflow (which I personally
> >welcome!), I am wondering how casual contributors like myself should
> >approach the task of finding reviewers.
>
> I don't think the situation is any better or worse in that respect. There *is* a transitional problem that some maintainers haven't set up (or refuse to set up) their forge account.
>
> And then it's vacation season in Europe.
>
> I would hope that maintainers sort outstanding requests by last change rather than initial submission, so then just refreshing or commenting your request should bring it back near the top of the list (I suppose Forgejo supports that? At least Gitlab does).
>
> With my CC hat on, ultimately, if you have really exhausted all options, you can appeal to the... TC.
>
> But there was never a way to guarantee that patches got merged, even if they addressed all comments, if you're not a maintainer, and the forge won't change that per se.
>
> The forge gives us an opportunity to define rules to merge code by default, *if* the GA wants to go in that direction. A timer bot similar to what VLC.git has could help here.

Thanks for the response.

You're right, it is vacation time for a lot of people and having down
time is healthy.

I was mostly pushing it because there's a release coming up and it's
discouraging to see the patch series being potentially released in an
incomplete state because of one hold out that seems so close to the
finish line.

-- Romain