From: Romain Beauxis <romain.beauxis@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Recommendations to facilitation patch reviews on forgejo/ML?
Date: Fri, 1 Aug 2025 18:19:39 -0500
Message-ID: <CABWZ6OTDkE9k-QNBoymy0LnFoMjvx0d_=4n4BFcr8w7twDqUDw@mail.gmail.com> (raw)
In-Reply-To: <FAD9432E-76B4-487B-87A8-04B250D8AF54@remlab.net>
Le jeu. 31 juil. 2025 à 06:12, Rémi Denis-Courmont <remi@remlab.net> a écrit :
>
>
>
> Le 30 juillet 2025 00:42:41 GMT+03:00, Romain Beauxis <romain.beauxis@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
_______________________________________________
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".
prev parent reply other threads:[~2025-08-01 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 21:42 Romain Beauxis
2025-07-29 21:52 ` Nicolas George
2025-08-01 23:17 ` Romain Beauxis
2025-08-02 9:59 ` Nicolas George
2025-07-31 11:12 ` Rémi Denis-Courmont
2025-08-01 23:19 ` Romain Beauxis [this message]
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='CABWZ6OTDkE9k-QNBoymy0LnFoMjvx0d_=4n4BFcr8w7twDqUDw@mail.gmail.com' \
--to=romain.beauxis@gmail.com \
--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