Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Vittorio Giovara <vittorio.giovara@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Query from Reuters on XZ, open source, and Microsoft
Date: Wed, 10 Apr 2024 23:59:04 -0400
Message-ID: <CABLWnS-pxVtmac+SHVT7u1RzqANrAY8D4_bKenQHhG3MPNHorg@mail.gmail.com> (raw)
In-Reply-To: <20240411011927.GV6420@pb2>

On Wed, Apr 10, 2024 at 9:19 PM Michael Niedermayer <michael@niedermayer.cc>
wrote:

> Hi
>
> On Tue, Apr 09, 2024 at 03:57:02PM -0500, Romain Beauxis wrote:
> > [Apologies for continuing the conversation, Rémi]
> >
> > Le mar. 9 avr. 2024 à 14:05, Tomas Härdin <git@haerdin.se> a écrit :
> >
> > > mån 2024-04-08 klockan 13:13 -0500 skrev Romain Beauxis:
> [...]
> >
> > > Also as someone who had to maintain a Gitlab instance at uni for a
> > > couple of years, I agree with Rémi's points
> > >
> >
> > My initial contribution was motivated by the argument presented in the
> > original talk that bringing new blood is critical to the survival of the
> > project.
> >
> > If so, then I do believe that there must be a compromise to be made
> between
> > being easier to join for new developers and changing the existing
> workflow.
> > I'm also aware that changing the existing workflow has been discussed
> > before.
> >
> > I don't think that media is not cool anymore, as argued in the talk. I
> see
> > a _lot_ of interested developers in my other projects and all over the
> open
> > source landscape. That's why I believe that it's also important to
> consider
> > other reasons than the talk's argument.
>
> To bring some of the new blood into the project the project needs to
> first understand why they dont. And asking thouse who manage with
> difficulty
> to join could be a biased oppinion.
>

In my experience this boils down to three points
1. there is a legit barrier of entry in a large codebase such as ffmpeg,
but over time newcomers can learn about it
2. the review process can be though and it's easy to miss a ping and
patches get lost, very defeating for a new developer
3. there is net negative help from trolls who spread toxic poison, which is
confusing and uninteresting for the new blood

2 out of 3 can be solved technically, while the last one needs a cultural
shift - overall I think we're doing a good job at slowly changing pace and
having a bit of a better structure to solve situations when they arise, but
there is still a lot of work to do
-- 
Vittorio
_______________________________________________
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-04-11  3:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 15:51 Satter, Raphael (Reuters) via ffmpeg-devel
2024-04-03 16:38 ` Kieran Kunhya via ffmpeg-devel
2024-04-03 16:42   ` [FFmpeg-devel] [EXT] " Satter, Raphael (Reuters) via ffmpeg-devel
2024-04-03 19:26   ` Satter, Raphael (Reuters) via ffmpeg-devel
2024-04-03 19:43     ` Kieran Kunhya via ffmpeg-devel
2024-04-08 11:02     ` Tomas Härdin
2024-04-08 14:40       ` Nicolas George
2024-04-08 17:56         ` Paul B Mahol
2024-04-09 19:08         ` Tomas Härdin
2024-04-17 19:05         ` [FFmpeg-devel] Mailinglist conduct (was: [EXT] Re: Query from Reuters on XZ, open source, and Microsoft) Ronald S. Bultje
2024-04-08 18:13   ` [FFmpeg-devel] Query from Reuters on XZ, open source, and Microsoft Romain Beauxis
2024-04-08 21:29     ` Vittorio Giovara
2024-04-09  3:09     ` Rémi Denis-Courmont
2024-04-09  8:36       ` Nicolas George
2024-04-10  9:27         ` Stefano Sabatini
2024-04-10 13:15           ` Gyan Doshi
2024-04-09 19:05     ` Tomas Härdin
2024-04-09 20:57       ` Romain Beauxis
2024-04-09 23:46         ` Paul B Mahol
2024-04-10  1:43           ` Romain Beauxis
2024-04-10 12:40           ` Ronald S. Bultje
2024-04-10 11:38         ` Tomas Härdin
2024-04-11  1:19         ` Michael Niedermayer
2024-04-11  3:59           ` Vittorio Giovara [this message]
2024-04-11  7:27             ` Paul B Mahol
2024-04-17 19:24             ` 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=CABLWnS-pxVtmac+SHVT7u1RzqANrAY8D4_bKenQHhG3MPNHorg@mail.gmail.com \
    --to=vittorio.giovara@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