Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andrew Sayers <ffmpeg-devel@pileofstuff.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [OSS-Fuzz] Have you considered enabling memory sanitizer?
Date: Tue, 16 Jul 2024 14:18:40 +0100
Message-ID: <ZpZzMD51Ra8zrnPB@andrews-2024-laptop.sayers> (raw)
In-Reply-To: <20240716122504.GL4991@pb2>

On Tue, Jul 16, 2024 at 02:25:04PM +0200, Michael Niedermayer wrote:
> On Mon, Jul 15, 2024 at 02:36:15PM +0200, Vittorio Giovara wrote:
> > Disagree - this is not the right way to attract new contributors.
> 
> no ?
> did you do a study ?
> 
> try this:
> A. "please we need more maintainers" (we tried this i think)
> B. gently push someone away
>     (now people are angry, they want their rights, their access, they want to
>      contribute ...)
>     ;)

A little off-topic, but I suspect this points to a deeper problem:

When a new person comes along and says "can I contribute my way?", replying
"no, here's the correct way to do it" leaves them with two options:
accept things are done that way for reasons they don't understand,
or go find another project that does things the way they already understand.

If you want more maintainers - that is, people with a deep understanding of the
project - you need to engage new contributors in a discussion about why things
are done that way.  Then over the course of years, they'll learn enough to
become maintainers.

I realise this can be daunting, but think about it this way: if you're right
about the best solution to some problem, arguing your case is a great way to
weed out illogical people who shouldn't become maintainers.  And if you're
wrong, you can hand over a part of the project to a new maintainer, safe in the
knowledge they understand that particular issue better than you.
_______________________________________________
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:[~2024-07-16 13:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 19:07 Kacper Michajlow
2024-06-26 22:45 ` Michael Niedermayer
2024-06-27  0:50   ` Kacper Michajlow
2024-07-13 21:12     ` Kacper Michajlow
2024-07-14 19:55       ` Michael Niedermayer
2024-07-15 11:32         ` Kacper Michajlow
2024-07-16 12:14           ` Michael Niedermayer
2024-07-17  0:16             ` Kacper Michajlow
2024-07-17  9:54             ` Anton Khirnov
2024-07-17 12:22               ` Nicolas George
2024-07-17 12:26                 ` Vittorio Giovara
2024-07-17 12:39                   ` Nicolas George
2024-07-17 13:15                     ` Vittorio Giovara
2024-07-15 12:36         ` Vittorio Giovara
2024-07-16 12:25           ` Michael Niedermayer
2024-07-16 13:18             ` Andrew Sayers [this message]
2024-07-16 18:52             ` Vittorio Giovara
2024-07-15 13:01         ` epirat07

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=ZpZzMD51Ra8zrnPB@andrews-2024-laptop.sayers \
    --to=ffmpeg-devel@pileofstuff.org \
    --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