From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests
Date: Wed, 12 Feb 2025 22:51:26 +0100
Message-ID: <8887ba88-7657-4432-a8c4-6d9d0eb33f8c@rothenpieler.org> (raw)
In-Reply-To: <DM8P223MB03659F8C99A85BD43A967411BAFC2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
On 12.02.2025 22:37, Soft Works wrote:
>
>
>> -----Original Message-----
>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Timo
>> Rothenpieler
>> Sent: Mittwoch, 12. Februar 2025 22:33
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests
>>
>> 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.
>
> Hi Timo,
>
> Does that mean that you cannot create forks and create PRs from that forked repo like on GitHub?
>
Not sure what you mean, you need "admin approval" to be allowed to
create repos, including forks.
Just to avoid abuse. Obviously you can then PR from that fork once you
got one.
Or you can submit PRs without a fork as stated above.
_______________________________________________
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-12 21:51 UTC|newest]
Thread overview: 24+ 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 [this message]
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-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-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=8887ba88-7657-4432-a8c4-6d9d0eb33f8c@rothenpieler.org \
--to=timo@rothenpieler.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