Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Regarding Git Tooling
Date: Mon, 20 Jan 2025 16:44:22 -0600
Message-ID: <CA+28BfBfs3q4j01eG9j_oXLi3REQsZ83ZE4+32tiNAmHCQROMA@mail.gmail.com> (raw)
In-Reply-To: <Z47NUo-7yrLe0Fvf@phare.normalesup.org>

Hi Nicolas,

This is fine and your preferences are understandable. Everyone has
their tools of choice.

That said, I did try Forgejo on a local instance today without
JavaScript and it was not a usable experience for a contributor.
I could do some limited functions but not raise a PR, for example.
Besides this issue, the experience was pleasant and fast.

Suppose there is an option with simple, reasonably, documented APIs
that can be used to bridge the gaps for our CLI-first developers.
Would you be open to experimenting?
Or as an output from this thread, can we declare what CLI-based user
workflows are needed
for folks to keep their velocity and start there? I imagine a creative
a solution can be found.

Forgejo seems to have this: https://forgejo.org/docs/latest/user/api-usage/
I know from past experience managing a GitLab instance, it has APIs too.
_______________________________________________
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-01-20 22:45 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 [this message]
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

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=CA+28BfBfs3q4j01eG9j_oXLi3REQsZ83ZE4+32tiNAmHCQROMA@mail.gmail.com \
    --to=marth64@proxyid.net \
    --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