[FFmpeg-devel] Forgejo entry threshold

[FFmpeg-devel] Forgejo entry threshold

[Nicolas George]

Dummy_test_user (HE12025-08-04):
> PR #20112 opened by Dummy_test_user
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20112
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20112.patch
> 
> I did that pull request to see what is preventing me from submitting crappy code.
> Apparently nothing.

Hi.

That was me. Thank you for ensuring it went to the mailing-list.

But…

I could register an account and create a pull request without ever
reading the coding-style rules in doc/developer.texi, and the pull
requests has red patcheck:

mismatching doxy params
+ * @param erbut  useless
+ * @param ernut  does nothing

That is not good.

If nothing better comes to mind to exclude crappy code, could we at
least condition creating an account to answering a 10 questions quiz
about our coding conventions?

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".

Re: [FFmpeg-devel] Forgejo entry threshold

[Hendrik Leppkes]

On Mon, Aug 4, 2025 at 4:45 PM Nicolas George <george@nsup.org> wrote:
>
> Dummy_test_user (HE12025-08-04):
> > PR #20112 opened by Dummy_test_user
> > URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20112
> > Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20112.patch
> >
> > I did that pull request to see what is preventing me from submitting crappy code.
> > Apparently nothing.
>
> Hi.
>
> That was me. Thank you for ensuring it went to the mailing-list.
>
> But…
>
> I could register an account and create a pull request without ever
> reading the coding-style rules in doc/developer.texi,
>

Whats the barrier of entry to sending a patch to the ML right now?
Does it quiz you on the guidelines?

- Hendrik
_______________________________________________
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".

Re: [FFmpeg-devel] Forgejo entry threshold

[Nicolas George]

Hendrik Leppkes (HE12025-08-04):
> Whats the barrier of entry to sending a patch to the ML right now?

Being able to, which is strongly correlated to knowing good practices.

> Does it quiz you on the guidelines?

Do you have better to propose?

-- 
  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".

Re: [FFmpeg-devel] Forgejo entry threshold

[Leon Grutters]

On 8/4/25 4:45 PM, Nicolas George wrote:
> Dummy_test_user (HE12025-08-04):
>> PR #20112 opened by Dummy_test_user
>> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20112
>> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20112.patch
>>
>> I did that pull request to see what is preventing me from submitting crappy code.
>> Apparently nothing.
> Hi.
>
> That was me. Thank you for ensuring it went to the mailing-list.
>
> But…
>
> I could register an account and create a pull request without ever
> reading the coding-style rules in doc/developer.texi, and the pull
> requests has red patcheck:
>
> mismatching doxy params
> + * @param erbut  useless
> + * @param ernut  does nothing
>
> That is not good.
>
> If nothing better comes to mind to exclude crappy code, could we at
> least condition creating an account to answering a 10 questions quiz
> about our coding conventions?
>
> Regards,
>
Is it that much harder to submit a patch on the ML? All you do is sign 
up for the ML, run one git command and then attach it to an email and 
click send.

_______________________________________________
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".