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 07:50:21 +0100
Message-ID: <80c8117d-b254-4d5f-9eab-de5b31c0a670@mur.at> (raw)
In-Reply-To: <e823f705-e466-4dfb-8ff6-405fcd895cfd@lynne.ee>



On 2/13/25 07:14, Lynne 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.

This will not work very well together with more advanced CI based PR 
checks and feedback if the used software platform doesn't provide mature 
support for these kinds of distributed setups. Ignoring this limitation 
you'll quickly face inconsistent repository-states and chaos as 
consequence. Until now none of the well known software options is able 
to play well in federated mode.

Using the other "federated" instances just as old fashioned identity 
providers isn't a very convincing solution to solve any of the real 
challenges of setting up a more efficient and somehow future-proof 
collaborative development workflow.

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

  reply	other threads:[~2025-02-13  6:50 UTC|newest]

Thread overview: 33+ 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 [this message]
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=80c8117d-b254-4d5f-9eab-de5b31c0a670@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