Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Leandro Santiago <leandrosansilva@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests
Date: Wed, 19 Feb 2025 23:02:56 +0100
Message-ID: <e03cfdec-f1ea-4309-b6a6-e832e1f398d0@gmail.com> (raw)
In-Reply-To: <20250212203842.GR4991@pb2>

Hi devs, I'm been following the discussion but not taking part on it.

I've just created a WIP PR on the forgejo instance which I'd like to get review, in case the instance is ready for the experiment.

Please let me know if you prefer that I send the changes via the mailing list instead, in case the experiment has not yet started.

(Please also let me know if I should start a new thread for it, as I still feel a bit confused by it).

Here is the link for the PR: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/10

Cheers,

Leandro

On 2/12/25 21:38, Michael Niedermayer wrote:
> On Wed, Feb 12, 2025 at 07:49:20PM +0100, Lynne wrote:
>> On 12/02/2025 19:06, Michael Niedermayer wrote:
>>> Hi all
>>>
>>> I propose, that we enable github pull requests
>>>
>>> github is the most widely used development platform and has the lowest barrier
>>> of entry.
>>>
>>> after ~1-3 Month, we then evaluate how many new developers this attracted,
>>> how many new contributions it attracted.
>>> What the ratios of reviewed vs ignored vs applied vs rejected patches are compared to the ML
>> Those are rather arbitrary statistics.
> Some people claimed these statistics would improve. I do think we should
> compare some statistics (obviously not limited to these)
>
>
> [...]
>
>> Users can already login to the instance with their github accounts, so
>> there's no barrier to entry.
> Thats cool, then forgejo is probably better for this experiment (if we do it)
>
> thx
>
>
> [...]
>
>
> _______________________________________________
> 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".
_______________________________________________
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-19 22:03 UTC|newest]

Thread overview: 55+ 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-13 21:44                       ` Stephen Hutchinson
2025-02-14  2:13                         ` Timo Rothenpieler
2025-02-14  5:19                           ` Tanay Manerikar
2025-02-14  5:40                         ` Steven Liu
2025-02-12 22:12           ` Romain Beauxis
2025-02-12 23:22             ` Soft Works
2025-02-13 16:56             ` Romain Beauxis
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-16 17:58               ` Rémi Denis-Courmont
2025-02-16 19:20                 ` Soft Works
2025-02-17 13:46                   ` Rémi Denis-Courmont
2025-02-13 12:10             ` Tomas Härdin
2025-02-13 12:38               ` martin schitter
2025-02-16 17:55             ` Rémi Denis-Courmont
2025-02-16 18:59               ` Soft Works
2025-02-12 20:38   ` Michael Niedermayer
2025-02-19 22:02     ` Leandro Santiago [this message]

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=e03cfdec-f1ea-4309-b6a6-e832e1f398d0@gmail.com \
    --to=leandrosansilva@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