[FFmpeg-devel] Regarding Git Tooling
Michael Niedermayer
michael at niedermayer.cc
Tue Jan 21 03:26:24 EET 2025
Hi
On Mon, Jan 20, 2025 at 02:39:29PM -0600, Marth64 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)
>
> 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?
I dont know why the options are exclusive. One can add a Forgejo on ffmpeg.org
but leave the Mailing List/Patch Workflow in place for cases where the
maintainer or patch author prefers a ML workflow.
I mean just add an option and see what happens
Who uses it ?
do people submit patches to it ?
do people enjoy working with it ?
do people hate working with it ?
IIUC one can add 1 line to .git/config and then a git fetch will
fetch all pull requests and one can simply merge any without any need of any
browser.
I also dont think we even need a vote to just setup a Forgejo on ffmpeg.org
when it replaces nothing but just adds an option
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
It is dangerous to be right in matters on which the established authorities
are wrong. -- Voltaire
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20250121/3016c23b/attachment.sig>
More information about the ffmpeg-devel
mailing list