From: Kacper Michajlow <kasper93@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Forgejo entry threshold
Date: Tue, 5 Aug 2025 16:17:03 +0200
Message-ID: <CABPLASTGOnw8KDer+3bNcqyvN_JRNbzup1aYWGcMiAr2gQyf0g@mail.gmail.com> (raw)
In-Reply-To: <aJIC1f--W4TF09sc@phare.normalesup.org>
On Tue, 5 Aug 2025 at 15:10, Nicolas George <george@nsup.org> wrote:
>
> Leon Grutters (HE12025-08-04):
> > 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.
>
> No, it is not harder at all, but it has the reputation to be, which has
> the same result.
>
> Nowadays, any idiot wannabe coder already has a github account and knows
> how to fumble on a similar webapp without having ever heard of
> etiquette, coding style or good practices. At least, when learning
> involves reading a doc instead of clicking randomly on buttons, they
> would have an occasion to.
Those "idiot wannabe coders," as you call them, are simply not
interested in low-level C/ASM media processing libraries. They use
Playskool Plastic Tool Kit to develop web applications in javascript.
Seriously, I think elitism and gatekeeping are not the right approach.
Judging someone's contribution quality based on whether they use gmail
or other "non-approved" tools is unfair. It saddens me that this kind
of attitude comes from a senior member of the community with so much
experience in the project.
The whole point is to attract new contributors and make the workflow
easier for everyone to improve productivity. If you care about
quality, go review the patches.
- Kacper
_______________________________________________
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".
next prev parent reply other threads:[~2025-08-05 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250804143901.82ED768C3C2@ffbox0-bg.ffmpeg.org>
2025-08-04 14:45 ` Nicolas George
2025-08-04 14:47 ` Hendrik Leppkes
2025-08-04 14:49 ` Nicolas George
2025-08-04 15:06 ` Leon Grutters
2025-08-05 13:10 ` Nicolas George
2025-08-05 14:17 ` Kacper Michajlow [this message]
2025-08-05 13:07 ` Nicolas George
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=CABPLASTGOnw8KDer+3bNcqyvN_JRNbzup1aYWGcMiAr2gQyf0g@mail.gmail.com \
--to=kasper93@gmail.com \
--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