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-requ...@ffmpeg.org with subject "unsubscribe".
