From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Regarding Git Tooling
Date: Tue, 21 Jan 2025 13:37:27 -0300
Message-ID: <60abe31a-d33a-409d-a0ef-ebbbffea4111@gmail.com> (raw)
In-Reply-To: <20250121130445.GD9168@haasn.xyz>
[-- Attachment #1.1.1: Type: text/plain, Size: 2058 bytes --]
On 1/21/2025 9:04 AM, Niklas Haas wrote:
> On Mon, 20 Jan 2025 14:39:29 -0600 Marth64 <marth64@proxyid.net> wrote:
>> Hello, in the context of a GA member,
>>
>> I think there is general interest in modernizing technical tooling
>> specifically regarding ML/patch workflow vs. integrated git solution.
>> Both have their merits. I think what we have today is optimized for
>> some but cumbersome for many. Like shopping for a drill, it is good to
>> step back from time to time and ensure we have the right tools.
>>
>> I think the problem statement of productivity being impacted from
>> outgrowing the current tooling is different from who is hosting it.
>>
>> These are some options I noticed interest in (in no particular order):
>> - Forgejo
>> - GitLab
>> - Mailing List/Patch Workflow (current solution)
>
> Since our last discussion at VDD, I have come to prefer Forgejo over GitLab
> and would be in favor of hosting an instance on ffmpeg.org.
>
> What are the current barriers to doing this. Michael, since you said that you
> are in favor iff the community agrees with it, should we start a GA vote on
> the matter?
>
> Can Timo set it up and maintain it for us? If not, I can also volunteer myself
> to do it.
>
>>
>> If we evaluate this as choosing a software appliance and put aside
>> "who is the host" I think we can have a good discussion. There could
>> be value in coming to consensus on one step, then moving on to the
>> next.
>>
>> The goal is not to spin around on which tool is better but I am wondering,
>> - What other options would the community consider and any relevant pros/cons?
>
> One pro about ForgeJo is that unlike most of its competitors, it is a community
> run project with a democratic governance model, a high degree of transparency
> on infrastructure and process, and a commitment to fully open source software
> (GPLv3+).
So, it works. The only thing we're missing is people to stop being
aggressive to each other. And for that, the CC should act and be swift.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 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".
prev parent reply other threads:[~2025-01-21 16:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 20:39 Marth64
2025-01-20 21:09 ` Nicolas George
2025-01-20 21:12 ` Marth64
2025-01-20 22:25 ` Nicolas George
2025-01-20 22:44 ` Marth64
2025-01-20 23:28 ` Marth64
2025-01-22 12:39 ` Nicolas George
2025-01-27 20:39 ` Jan Ekström
2025-01-27 20:55 ` Timo Rothenpieler
2025-01-20 22:44 ` compn
2025-01-20 22:14 ` Leo Izen
2025-01-21 1:26 ` Michael Niedermayer
2025-01-21 1:56 ` Soft Works
2025-01-21 2:38 ` Michael Niedermayer
2025-01-21 3:22 ` Soft Works
2025-01-21 3:56 ` Kieran Kunhya via ffmpeg-devel
2025-01-21 4:03 ` Soft Works
2025-01-21 4:07 ` Marth64
2025-01-21 7:17 ` Nicolas George
2025-01-21 1:57 ` compn
2025-01-21 2:41 ` Michael Niedermayer
2025-01-21 2:56 ` James Almer
2025-01-21 3:34 ` Soft Works
2025-01-21 11:51 ` Niklas Haas
2025-01-21 17:55 ` Frank Plowman
2025-01-21 18:20 ` Niklas Haas
2025-01-21 12:04 ` Niklas Haas
2025-01-21 15:39 ` Lynne
2025-01-21 15:54 ` Michael Niedermayer
2025-01-21 16:14 ` Soft Works
2025-01-22 0:38 ` Soft Works
2025-01-22 1:08 ` Marth64
2025-01-22 2:00 ` Soft Works
2025-01-22 6:41 ` martin schitter
2025-01-25 7:54 ` Soft Works
2025-01-25 19:17 ` martin schitter
2025-01-25 22:20 ` Marth64
2025-01-21 16:22 ` James Almer
2025-01-21 17:48 ` Michael Niedermayer
2025-01-21 17:57 ` James Almer
2025-01-21 18:14 ` Niklas Haas
2025-01-25 6:57 ` Rémi Denis-Courmont
2025-01-21 16:37 ` James Almer [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=60abe31a-d33a-409d-a0ef-ebbbffea4111@gmail.com \
--to=jamrial@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