From: Jacob Lifshay <programmerjake@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org
Date: Tue, 22 Jul 2025 02:15:22 -0700
Message-ID: <CAC2bXD6zZVJQcGX9uxgFWKvVUQ7RGdJAHr-uVYU01pr2xPJGdQ@mail.gmail.com> (raw)
In-Reply-To: <CABPLASQn14pXhEwVX3QQ_9OWukzTA8paoxH_h1a0GWmG2+puXQ@mail.gmail.com>
On Tue, Jul 22, 2025 at 1:44 AM Kacper Michajlow <kasper93@gmail.com> wrote:
> On Tue, 22 Jul 2025 at 05:54, Lynne <dev@lynne.ee> wrote:
> > + Additionally, new users have frequently encountered difficulties with mailing list development.
> > + From finding out the correct SMTP login details, configuring git send-email, new email security
> > + mechanisms interfering with mailing list operations, and finally not having a comfortable workflow
> > + to review patches.
>
> Just a 2 cents from me, I don't think sending email itself is a
> problem,
If you don't need to send patches, email isn't really a problem.
however, imo figuring out how to get git send-email to work is a
significant problem (it took me like 20-30min to set up since I was
also figuring how to securely store the gmail app password in gnome
keyring using a git credential helper), I have contributed to quite a
few FOSS projects over the last 10yr or so and FFmpeg is the only(?)
one that requires using git send-email. the vast majority of them are
using a git forge or you just point them to your git forge of choice
and they'll pull from there.
tbh the only reason I'm contributing now using git send-email is
because I'm being paid to, if I weren't being paid I'm much less
likely to have bothered even when I had the code in a git repo.
Jacob Lifshay
_______________________________________________
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-07-22 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 3:53 Lynne
2025-07-22 8:44 ` Kacper Michajlow
2025-07-22 9:15 ` Jacob Lifshay [this message]
2025-07-22 15:01 ` Leo Izen
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=CAC2bXD6zZVJQcGX9uxgFWKvVUQ7RGdJAHr-uVYU01pr2xPJGdQ@mail.gmail.com \
--to=programmerjake@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