From: Lynne <dev@lynne.ee> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests Date: Wed, 12 Feb 2025 19:49:20 +0100 Message-ID: <f1c9e182-43e9-4a73-b72c-19c4be85031b@lynne.ee> (raw) In-Reply-To: <20250212180659.GP4991@pb2> [-- Attachment #1.1.1.1: Type: text/plain, Size: 1490 bytes --] 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. > This information should help the community make decissions about the use of > web based git development vs the mailing list. Every one of us is already familiar with the benefits of having a platform. This is just slowing down and delaying what we ought to do, which is to switch as soon as possible. Finally, without CI, it doesn't really show the potential. We all know that github will not be the platform we move to, so instead of getting used to a temporary workflow, I'd rather we test a likely final workflow that we could potentially be using. Instead of github, I want to use the current test Forgejo instance. It already has CI working and over 10 developers have registered. Some have doubts about whether it would slow down with more users, or bugs would appear, and it would be good to demonstrate the platform can handle our workflow, and fix any remaining issues. Users can already login to the instance with their github accounts, so there's no barrier to entry. [-- Attachment #1.1.1.2: OpenPGP public key --] [-- Type: application/pgp-keys, Size: 637 bytes --] [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 236 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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 18:49 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-12 18:06 Michael Niedermayer 2025-02-12 18:49 ` Lynne [this message] 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-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-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=f1c9e182-43e9-4a73-b72c-19c4be85031b@lynne.ee \ --to=dev@lynne.ee \ --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