Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: epirat07@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, 17 Apr 2024 21:24:26 +0200
Message-ID: <C59718AD-8636-4E24-B0A9-43716545439C@gmail.com> (raw)
In-Reply-To: <CABLWnS-pxVtmac+SHVT7u1RzqANrAY8D4_bKenQHhG3MPNHorg@mail.gmail.com>



On 11 Apr 2024, at 5:59, Vittorio Giovara wrote:

> On Wed, Apr 10, 2024 at 9:19 PM Michael Niedermayer <michael@niedermayer.cc>
> wrote:
>
>> […]
>>
>> 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

This has honestly been one of the most discouraging things when contributing
here.

The ML workflow just contributes to make this even worse for me, as it makes
it really hard to keep track of things. (Of course everyone is different
and I get why some people like the ML-patches workflow, but having experienced
both at VLC, I can say for myself I vastly prefer Gitlab-like solutions)

> 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

Another factor is IMO the general tone here on the ML, let’s just say it is not
the most welcoming environment. It doesn’t help that sometimes technical discussion
and „politics“ are mixed together so you have no way to escape it when you don’t feel
like being dragged down by the state of this community some days…

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

      parent reply	other threads:[~2024-04-17 19:24 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
2024-04-11  7:27             ` Paul B Mahol
2024-04-17 19:24             ` epirat07 [this message]

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=C59718AD-8636-4E24-B0A9-43716545439C@gmail.com \
    --to=epirat07@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