From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] GSoC 2025
Date: Fri, 31 Jan 2025 05:01:49 +0000
Message-ID: <DM8P223MB03656FC6EA2E091DED1EF451BAE82@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20250130045328.0000423a@hawaiiantel.net>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> compn
> Sent: Thursday, January 30, 2025 3:53 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] GSoC 2025
>
> On Thu, 30 Jan 2025 13:20:19 -0800, Koushik Dutta wrote:
>
> > Why gitlab and not GitHub? If the intent is on making contribution
> from new
> > developers easier, I think the workflow should be where the
> majority of
> > developers are actively participating.
>
> is there a way to bridge github with a mailinglist or with gitlab?
>
> theres no reason why we cant have multiple ways to contribute to
> ffmpeg.
>
> have pull requests send notifications to this mailing list?
> https://github.com/settings/notifications
>
> -compn
There's a working integration which does not only send notifications, it even sends pull requests as patches to the mailing list and mirrors comments from the ML as PR comments. Also handles version updates, performs checks, test build with FATE and requires a successful build+FATE before sending to the ML:
https://github.com/ffstaging/FFmpeg
Explanation: https://github.com/ffstaging/FFmpeg/wiki
sw
_______________________________________________
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".
next prev parent reply other threads:[~2025-01-31 5:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 2:21 Michael Niedermayer
2025-01-29 15:51 ` Yigithan Yigit
2025-01-29 19:01 ` Michael Niedermayer
2025-01-29 19:31 ` Kieran Kunhya via ffmpeg-devel
2025-01-29 20:01 ` Ronald S. Bultje
2025-01-30 6:36 ` Vittorio Giovara
2025-01-30 10:21 ` Sean McGovern
2025-01-30 18:40 ` Michael Niedermayer
2025-01-30 21:20 ` Koushik Dutta
2025-01-30 14:53 ` compn
2025-01-31 5:01 ` Soft Works [this message]
2025-01-31 0:24 ` Vittorio Giovara
2025-01-31 12:51 ` James Almer
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=DM8P223MB03656FC6EA2E091DED1EF451BAE82@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz-at-hotmail.com@ffmpeg.org \
--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