Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Romain Beauxis <romain.beauxis@gmail.com>
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 10:56:56 -0600
Message-ID: <CABWZ6OQhvUODk6UCZkLP9djHTuX_Yt2dxSs9+6X-gOVsBzPX2Q@mail.gmail.com> (raw)
In-Reply-To: <CABWZ6OQib2K2doPYWA=dOtNc9v7Y+vkn6zM+BJ0phqQEvRFi2Q@mail.gmail.com>

Le mer. 12 févr. 2025 à 16:12, Romain Beauxis
<romain.beauxis@gmail.com> a écrit :
>
>
>
>
> Le mer. 12 févr. 2025 à 15:32, Timo Rothenpieler <timo@rothenpieler.org> a écrit :
> >
> > On 12.02.2025 22:22, Stephen Hutchinson wrote:
> > > On 2/12/25 2:23 PM, Lynne wrote:
> > >>
> > >>
> > >> On 12/02/2025 19:53, Romain Beauxis wrote:
> > >>> Le mer. 12 févr. 2025 à 12:49, Lynne <dev@lynne.ee> a écrit :
> > >>>>
> > >>>> Users can already login to the instance with their github accounts, so
> > >>>> there's no barrier to entry.
> > >>>
> > >>> Would you mind sharing the url? A quick search didn't reveal anything.
> > >>
> > >> Sure
> > >> https://code.ffmpeg.org/
> > >>
> > >
> > > Are all accounts restricted to owning a maximum of 0 repositories by
> > > default, or is it set to 0 only for those that sign up through one of
> > > the external logins?
> >
> > It's set to 0 by default, to avoid spammers uploading junk, or just
> > people (ab)using it for non-ffmpeg things.
> >
> > You can open issues and comment on existing PRs.
> > And also create PRs using the AGit workflow:
> > https://forgejo.org/docs/latest/user/agit-support/
> >
> > The repo limit can manually be lifted per user. I preferred that
> > approach vs. the Videolan approach of completely locking down the
> > instance, and requiring admin approval for every single new user, which
> > imo is more detrimental to new contributors than a ML.
>
> I totally understand the concern.
>
> The procedure for creating PRs using AGit is a bit arcane but I'll give it a try.
>
> It would be nice to have this document big and bold when users register, I was quite lost after registration seeing I couldn't fork.
>
> I'm gonna try to think about how to split patches from the ML perspective to a PR perspective.
>
> Is there any opinion on this? Typically the series I have has a section for flac and one for opus, do y'all think one general PR for the base work then one PR for flac and one PR for opus or one single PR with the patch series like in the ML?

I went ahead and submitted one of two recent patch series:
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/6

The process was pretty easy once you've figured out the base setup
(SSH key, rebase against the actual repo `master` branch, command line
arguments).

Hopefully this will help get the patchset reviewed!
-- Romain
_______________________________________________
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 16:57 UTC|newest]

Thread overview: 45+ 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-12 22:12           ` Romain Beauxis
2025-02-12 23:22             ` Soft Works
2025-02-13 16:56             ` Romain Beauxis [this message]
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-13 12:10             ` Tomas Härdin
2025-02-13 12:38               ` martin schitter
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=CABWZ6OQhvUODk6UCZkLP9djHTuX_Yt2dxSs9+6X-gOVsBzPX2Q@mail.gmail.com \
    --to=romain.beauxis@gmail.com \
    --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