From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 25ACF4BF0D for ; Wed, 22 Jan 2025 12:39:21 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id D512368B90C; Wed, 22 Jan 2025 14:39:17 +0200 (EET) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id A828368A84C for ; Wed, 22 Jan 2025 14:39:11 +0200 (EET) X-ENS-nef-client: 129.199.129.80 ( name = phare.normalesup.org ) Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80]) by nef.ens.fr (8.14.4/1.01.28121999) with ESMTP id 50MCdAu4015684 for ; Wed, 22 Jan 2025 13:39:10 +0100 Received: by phare.normalesup.org (Postfix, from userid 1001) id 68EB92EFE0; Wed, 22 Jan 2025 13:39:10 +0100 (CET) Date: Wed, 22 Jan 2025 13:39:10 +0100 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Wed, 22 Jan 2025 13:39:10 +0100 (CET) Subject: Re: [FFmpeg-devel] Regarding Git Tooling X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Marth64 (12025-01-20): > 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. As long as the ability to use the solution with command-line tools is part of the scope statement of the project, I am absolutely fine testing any kind of solution. Frankly, it is already refreshing that the preference of people who want to work in command-line is taken into consideration at all and not just ignored or treated with scorn, as was so often the case in similar discussions. Regards, -- Nicolas George _______________________________________________ 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".