> -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of Rémi > Denis-Courmont > Sent: Sonntag, 16. Februar 2025 18:56 > To: FFmpeg development discussions and patches <ffmpeg- > de...@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests > > Le torstaina 13. helmikuuta 2025, 1.07.25 UTC+2 Soft Works a écrit : > > > -----Original Message----- > > > From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of > Timo > > > Rothenpieler > > > Sent: Mittwoch, 12. Februar 2025 22:33 > > > To: ffmpeg-devel@ffmpeg.org > > > Subject: Re: [FFmpeg-devel] [RFC] Experiment: enable github pull requests > > > > > > On 12.02.2025 22:22, Stephen Hutchinson wrote: > > > > Are all accounts restricted to owning a maximum of 0 repositories by > > > > default, or is it set to 0 only for those that sign up through one of > > > > the external logins? > > > > > > It's set to 0 by default, to avoid spammers uploading junk, or just > > > people (ab)using it for non-ffmpeg things. > > > > > > You can open issues and comment on existing PRs. > > > And also create PRs using the AGit workflow: > > > https://forgejo.org/docs/latest/user/agit-support/ > > > > For those who are too lazy to look it up: > > > > The "Agit workflow" requires you to use non-standard Git "push-options" > > (either -o or --push-options): > > > > git push origin HEAD:refs/for/master -o topic="topic-branch" \ > > -o title="Title of the PR" \ > > -o description="# The PR Description > > This can be **any** markdown content.\n > > - [x] Ok" > > > > This means essentially that our attempt to move away from the e-mail-based > > submission procedure to something easy and user-friendly, would end up in > > replacing the current rarely-known mechanism with another even more rare > > and obscure procedure which would (again) force everybody to use the Git > > command line because it's (again) not supported by any tooling except Git > > CLI. > > > > I'm afraid, but from my point of view, this doesn't match the objective. > > Do you really expect to develop FFmpeg without using a CLI? In the first > place, > FFmpeg is a set of library and CLI tools.
Hi Rémi, call me lazy, but I want to be able to click the push button in my Git tools rather than crafting a command like above each time. FFmpeg has been the only project where I wasn't able to do so and I think it would be great when the new way would allow to work in the same way as with 95%(*) of all other software projects in the world instead of replacing one special sauce with another even more special sauce. (* I don't have real figures, but the argument doesn't change whether it's 85 or 99%) > As far as the Git CLI is concerned, I believe that the main objection is the > reliance on git-send-email, and the implied need for an outbound SMTP server > - > not the need to use the Git GLI as such. The only improvement is that no SMTP setup is needed, but otherwise it just replaces one unhandy and uncommon Git command with another unhandy, uncommon and now even non-standard Git command. We really should be able to do better than that. The intention was to tear down fences for attracting new contributors, but from my point of view, this (plus the requirement to ask for admission) is building up an even higher fence. Best, sw _______________________________________________ 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".
