Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: compn <ff@hawaiiantel.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org
Date: Thu, 24 Jul 2025 17:40:28 -1000
Message-ID: <20250724174028.00001285@hawaiiantel.net> (raw)
In-Reply-To: <CAC2bXD6zZVJQcGX9uxgFWKvVUQ7RGdJAHr-uVYU01pr2xPJGdQ@mail.gmail.com>

On Tue, 22 Jul 2025 02:15:22 -0700, Jacob Lifshay wrote:

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

people can always just manually attach patches to emails sent to
ffmpeg-devel list. no need for git send mail.

git-send-email is not a requirement to contribute to ffmpeg. in fact,
i've never used git send email to send patches.

git send-email is not listed as a requirement on our mailing list
information page:
https://ffmpeg.org/contact.html#MailingLists
likewise , the submitting patches developer documentation does not make
git send-email a requirement.
https://ffmpeg.org/developer.html#Introduction

also i'm sure whatever development toolset you use can be scripted to
send a patch via email? are you using github or some other non command
line git to write code? maybe there is an easier workflow for you if
git send-email is not to your liking?


thanks for detailing out how other projects do it though, we are
always looking to improve.

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

  reply	other threads:[~2025-07-25  3:40 UTC|newest]

Thread overview: 41+ 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
2025-07-25  3:40     ` compn [this message]
2025-07-25  3:58       ` Jacob Lifshay
2025-07-25  4:36         ` compn
2025-07-25 11:41         ` Nicolas George
2025-07-25 14:20           ` Kieran Kunhya via ffmpeg-devel
2025-07-23  4:05   ` Lynne
2025-07-22 15:01 ` Leo Izen
2025-07-23  4:01   ` Lynne
2025-07-22 23:04 ` Michael Niedermayer
2025-07-23  4:01   ` Lynne
2025-07-23  9:16     ` Michael Niedermayer
2025-07-23  9:39       ` Kieran Kunhya via ffmpeg-devel
2025-07-23  9:59         ` Michael Niedermayer
2025-07-23 10:02           ` Kieran Kunhya via ffmpeg-devel
2025-07-23 11:48           ` Nicolas George
2025-07-25  4:05           ` compn
2025-07-26 14:57             ` Michael Niedermayer
2025-07-23  9:38     ` Michael Niedermayer
2025-07-23 11:49       ` Nicolas George
2025-07-26 17:03 ` Derek Buitenhuis
2025-07-26 19:29   ` Timo Rothenpieler
2025-07-26 20:01     ` Derek Buitenhuis
2025-07-26 20:14       ` Timo Rothenpieler
2025-07-26 20:24         ` Kacper Michajlow
2025-07-26 20:29           ` Derek Buitenhuis
2025-07-26 20:41           ` Timo Rothenpieler
2025-07-26 20:45             ` Derek Buitenhuis
2025-07-26 21:07             ` Kacper Michajlow
2025-07-26 21:18               ` Timo Rothenpieler
2025-07-26 22:44             ` Michael Niedermayer
2025-07-26 22:57               ` Timo Rothenpieler
2025-07-26 22:48             ` Michael Niedermayer
2025-07-27  9:39           ` Nicolas George
2025-07-26 20:28         ` Derek Buitenhuis
2025-07-26 20:14     ` Kacper Michajlow
2025-07-26 20:23       ` Timo Rothenpieler
2025-07-26 20:29         ` Kacper Michajlow
2025-07-26 20:33           ` Derek Buitenhuis

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=20250724174028.00001285@hawaiiantel.net \
    --to=ff@hawaiiantel.net \
    --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