From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests
Date: Mon, 17 Feb 2025 15:46:02 +0200
Message-ID: <E9086E26-0616-4EFB-9590-07FED1E9C3BF@remlab.net> (raw)
In-Reply-To: <DM8P223MB0365D5739DB7EBE7FF1E00C1BAF82@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
Le 16 février 2025 21:20:59 GMT+02:00, Soft Works <softworkz-at-hotmail.com@ffmpeg.org> a écrit :
>
>
>> -----Original Message-----
>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Rémi
>> Denis-Courmont
>> Sent: Sonntag, 16. Februar 2025 18:59
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests
>>
>> Le torstaina 13. helmikuuta 2025, 1.34.18 UTC+2 Timo Rothenpieler a écrit :
>> > Videolan apparently even went away from the current approach on our
>> > instance, cause there was still too much spam. So they're
>> > manual-approval-only now.
>>
>> AFAICT, FreeDesktop did something similar (long before the current
>> controversy
>> with change of host).
>>
>> Any open Gitlab instance will be spammed, especially for a well-known web
>> domain. And from other comments, I guess Forgejo has the same problem.
>> Locking
>> down at some point before publishing is unavoidable, either at user creation
>> or at forking.
>
>Needing to ask somebody for getting admission is too high a hurdle.
I don't like it either but it is unavoidable. Spam isn't going to stop just because you want it to.
_______________________________________________
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-02-17 13:46 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 18:06 Michael Niedermayer
2025-02-12 18:49 ` Lynne
2025-02-12 18:53 ` Romain Beauxis
2025-02-12 19:23 ` Lynne
2025-02-12 21:22 ` Stephen Hutchinson
2025-02-12 21:32 ` Timo Rothenpieler
2025-02-12 21:37 ` Soft Works
2025-02-12 21:51 ` Timo Rothenpieler
2025-02-12 22:01 ` Soft Works
2025-02-12 22:05 ` Timo Rothenpieler
2025-02-12 22:16 ` Soft Works
2025-02-12 23:29 ` Timo Rothenpieler
2025-02-12 23:34 ` Kieran Kunhya via ffmpeg-devel
2025-02-13 0:27 ` Timo Rothenpieler
2025-02-13 12:07 ` Tomas Härdin
2025-02-13 4:05 ` martin schitter
2025-02-13 8:49 ` Leo Izen
2025-02-13 9:27 ` Tanay Manerikar
2025-02-13 12:40 ` Leo Izen
2025-02-13 9:49 ` Gyan Doshi
2025-02-13 10:30 ` Soft Works
2025-02-13 12:37 ` Leo Izen
2025-02-13 13:32 ` Timo Rothenpieler
2025-02-13 21:44 ` Stephen Hutchinson
2025-02-14 2:13 ` Timo Rothenpieler
2025-02-14 5:19 ` Tanay Manerikar
2025-02-14 5:40 ` Steven Liu
2025-02-12 22:12 ` Romain Beauxis
2025-02-12 23:22 ` Soft Works
2025-02-13 16:56 ` Romain Beauxis
2025-02-12 23:07 ` Soft Works
2025-02-12 23:34 ` Timo Rothenpieler
2025-02-13 0:17 ` Soft Works
2025-02-13 0:24 ` Romain Beauxis
2025-02-13 0:40 ` Soft Works
2025-02-13 1:52 ` Timo Rothenpieler
2025-02-13 2:59 ` Soft Works
2025-02-13 6:14 ` Lynne
2025-02-13 6:50 ` martin schitter
2025-02-13 6:54 ` Soft Works
2025-02-13 7:24 ` Soft Works
2025-02-13 13:32 ` Timo Rothenpieler
2025-02-13 11:04 ` Tobias Rapp
2025-02-13 12:07 ` Soft Works
2025-02-13 12:27 ` Soft Works
2025-02-13 13:37 ` Timo Rothenpieler
2025-02-16 17:58 ` Rémi Denis-Courmont
2025-02-16 19:20 ` Soft Works
2025-02-17 13:46 ` Rémi Denis-Courmont [this message]
2025-02-13 12:10 ` Tomas Härdin
2025-02-13 12:38 ` martin schitter
2025-02-16 17:55 ` Rémi Denis-Courmont
2025-02-16 18:59 ` Soft Works
2025-02-12 20:38 ` Michael Niedermayer
2025-02-19 22:02 ` Leandro Santiago
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=E9086E26-0616-4EFB-9590-07FED1E9C3BF@remlab.net \
--to=remi@remlab.net \
--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