Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: martin schitter <ms+git@mur.at>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests
Date: Thu, 13 Feb 2025 05:05:15 +0100
Message-ID: <e3926d8e-484c-4d1e-9dc7-be43e8ce9055@mur.at> (raw)
In-Reply-To: <6a5a1ba9-08c3-40fe-9313-55f82889afa2@rothenpieler.org>



On 2/12/25 23:05, Timo Rothenpieler wrote:
> PRs are not restricted. Creating repos is.
> And there is no way to NOT restrict it, unless you want to pay several 
> hundred Euros a month in hosting fees extra, and constantly be on the 
> lookout for hosting illegal/harmful things.

Hosting tons of forks can be done very efficiently if you storage 
solution provides adequate *deduplication* support. That's only one of 
the typical issues that you'll have to face, if you try to imitate the 
big ones by using utterly inadequate means. Tools which only look 
similar on their outer surface.

Fighting notification spam, which plagued codeberg (=forgejo) users the 
last days in a very unpleasant way, are a similar problem. Ignoring the 
importance of these less obvious maintenance requirements looks to me 
like setting up an email server resp. gateway without any mature spam 
protection facilities these days.

But I also wouldn't be happy if GitHub would be simply chosen at the end 
because of all this challenging troubles and dangers.

Anyway -- CI workflow, automatic PR checks and satisfying comment and 
documentation support are IMHO much more important aspects than just 
hosting a git repo on the web.

martin
_______________________________________________
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".

  parent reply	other threads:[~2025-02-13  4:05 UTC|newest]

Thread overview: 32+ 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 [this message]
2025-02-13  8:49                   ` Leo Izen
2025-02-13  9:27                     ` Tanay Manerikar
2025-02-13  9:49                     ` Gyan Doshi
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
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=e3926d8e-484c-4d1e-9dc7-be43e8ce9055@mur.at \
    --to=ms+git@mur.at \
    --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