From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests
Date: Thu, 13 Feb 2025 07:24:24 +0000
Message-ID: <DM8P223MB03658CB6BCE379C4BA60C5E5BAFF2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <e823f705-e466-4dfb-8ff6-405fcd895cfd@lynne.ee>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Lynne
> Sent: Donnerstag, 13. Februar 2025 07:15
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests
>
> On 13/02/2025 03:59, Soft Works wrote:
> >
> Finally, with federation, there's are no restriction. If users have an
> account on another Forgejo instance, such as codeberg, they can clone
> and submit PRs to FFmpeg without having to register, and without needing
> to use agit.
Two more thoughts:
I'm a bit surprised to hear that Spammers would be such a big problem. On GitHub, I'm subscribed to dozens of repos and surely more than a thousand conversations, but over the past 10 years I have received less than 5 spam messages in total. That makes we wonder how GH is doing it, because notifications are sent out instantly and I would have seen those in the inbox even when they would have been cleaned up later.
What's their recipe?
And regarding Codeberg: When spam is such a big concern that we must require user to apply even for creating a fork (unlike almost any other open-source software project in the world) - why then even bother with self-hosting? If we think it causes too much trouble, why do it in the first place? There are other organizations for which hosting Git repos is their daily and primary business. Maybe it's better to have it professionally hosted and call it a day...
Why not Codeberg actually?
Best
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-02-13 7:24 UTC|newest]
Thread overview: 34+ 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 4:05 ` martin schitter
2025-02-13 8:49 ` Leo Izen
2025-02-13 9:27 ` Tanay Manerikar
2025-02-13 9:49 ` Gyan Doshi
2025-02-13 10:30 ` Soft Works
2025-02-12 22:12 ` Romain Beauxis
2025-02-12 23:22 ` Soft Works
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 [this message]
2025-02-13 11:04 ` Tobias Rapp
2025-02-12 20:38 ` Michael Niedermayer
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=DM8P223MB03658CB6BCE379C4BA60C5E5BAFF2@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