From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTP id 46D504A871
	for <ffmpegdev@gitmailbox.com>; Thu, 18 Apr 2024 08:20:02 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 4534B68D3FA;
	Thu, 18 Apr 2024 11:20:00 +0300 (EEST)
Received: from mail-ej1-f53.google.com (mail-ej1-f53.google.com
 [209.85.218.53])
 by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 4AF7268D306
 for <ffmpeg-devel@ffmpeg.org>; Thu, 18 Apr 2024 11:19:54 +0300 (EEST)
Received: by mail-ej1-f53.google.com with SMTP id
 a640c23a62f3a-a4715991c32so54968466b.1
 for <ffmpeg-devel@ffmpeg.org>; Thu, 18 Apr 2024 01:19:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20230601; t=1713428393; x=1714033193; darn=ffmpeg.org;
 h=user-agent:in-reply-to:content-disposition:mime-version:references
 :mail-followup-to:message-id:subject:to:from:date:from:to:cc:subject
 :date:message-id:reply-to;
 bh=qp2ySOxhkW2CHg4qSqRWFWUFpTO+w3REm0hLdY7oyKQ=;
 b=EZbVkyXX6CH10HZogQWoY9wywCSnui9Pf91ebFHFTUZjEUMYeBSzSPJhsmHQ7xybPm
 gKZXjkITgXAFJ+Y3+lOcyzNk0L8DpLwMdIgrAvr5Atc2gu/fNGSiztFimv+Zv1BghH7h
 mvSKoChYQ7NRNotfU5qsue8vLWhgXw98Q0mtBqVemU6Jpx8ogQI2lc2T1BsyiiliY4dh
 6qHIzToFlpxo3q6jwp/e+RTTawOruRUNqxFjc9Cq3Ua0rs9IVHstzn1oUGNJiFEh0VpP
 R2E/eiOfoslPvObV/N4ZKdLu/R0u3ri/w9TXaJQ7OeRUcYGuP+1x234+thdf67ndTc2c
 tZpA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20230601; t=1713428393; x=1714033193;
 h=user-agent:in-reply-to:content-disposition:mime-version:references
 :mail-followup-to:message-id:subject:to:from:date:x-gm-message-state
 :from:to:cc:subject:date:message-id:reply-to;
 bh=qp2ySOxhkW2CHg4qSqRWFWUFpTO+w3REm0hLdY7oyKQ=;
 b=HYMhLBk7mvmtmAaStZnLBsOzDZgAiP/ehiWje2h1I6iTa1J9Fhs8LpLjQtoOFNDMj6
 II7fUKj3S2RE0OovmVm/zyyGBcKaUePKvpwkUWe/KDDz3q8I6rm1qDDCFUUZZ+Vhh67r
 PlV9rkFvhlrlvC7fvHqIaTEEewChaDWw/gGlMnvm1ifMwwLdGkbEDYa8+I95CDHZU7DV
 m65CUIF8U+2lls0w0cgmjg4xx9qNyWB1ZscLdzkYvI7ZhUOQkMn6Niv6S8XIlmnqow+W
 /FmoEgsCWi0fIor+HQKzPHY+HoWpJ4XRhVU/OxgY7PfbjjK0RIFkZxFyX1q5m2iyqCw3
 Ov4g==
X-Gm-Message-State: AOJu0Yyvi+sqMCIHMXzQ9j8Sv/RhtefDVac5IRMQ2o/PnuV4RYOCKqdz
 EJm1cz8B125GTyH8rRaN45eRBJxh7y7MLv1PVrPeHNZhD7W33LOjy1INyg==
X-Google-Smtp-Source: AGHT+IGoP9kC1ItFNsol/CVGX4O3UahpiEjkcCrKwvt1t2P2zD4GEAs3Go8bVPlbG+SqM1DyTQF4eg==
X-Received: by 2002:a17:906:dcb:b0:a55:73c3:f817 with SMTP id
 p11-20020a1709060dcb00b00a5573c3f817mr537862eji.12.1713428392403; 
 Thu, 18 Apr 2024 01:19:52 -0700 (PDT)
Received: from mariano (host-87-17-49-61.retail.telecomitalia.it.
 [87.17.49.61]) by smtp.gmail.com with ESMTPSA id
 e6-20020a170906504600b00a4e26377bf1sm565668ejk.175.2024.04.18.01.19.51
 for <ffmpeg-devel@ffmpeg.org>
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Thu, 18 Apr 2024 01:19:51 -0700 (PDT)
Received: by mariano (Postfix, from userid 1000)
 id 9917ABFCE8; Thu, 18 Apr 2024 10:19:50 +0200 (CEST)
Date: Thu, 18 Apr 2024 10:19:50 +0200
From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Message-ID: <ZiDXpvhl3UiEFc31@mariano>
Mail-Followup-To: FFmpeg development discussions and patches
 <ffmpeg-devel@ffmpeg.org>
References: <20240417135832.GJ6420@pb2>
 <CADHDR+3p5pjjKZza-rh9SgOKuzs2Qp0tRMPab9sMWYr10eiEQA@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CADHDR+3p5pjjKZza-rh9SgOKuzs2Qp0tRMPab9sMWYr10eiEQA@mail.gmail.com>
User-Agent: Mutt/2.1.4 (2021-12-11)
Subject: Re: [FFmpeg-devel] [RFC] 5 year plan & Inovation
X-BeenThere: ffmpeg-devel@ffmpeg.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/ZiDXpvhl3UiEFc31@mariano/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>

On date Wednesday 2024-04-17 19:21:39 -0700, Aidan wrote:
> The best option is to figure stuff out.
[...]
> I use FFmpeg to download HLS streams from the internet or convert files
> like probably most people do. FFmpeg is the ultimate way of doing this
> because there is no better option.
> 
> But there are issues:
[...]

> I submitted a patch for a TTML decoder because I thought it would be great.
> It was completely ignored.

Please ping the patch or send a new one.

> If my patch was seriously bad, then fine. But seriously *no one cared*.

I think contribution management is a serious issue here.

What happens when you send a patch is that if you're lucky someone
will be interested and put some effort to review and eventually get it
pushed, which depending on several factors might require several
interactions.

Sometimes contributors are side-tracked or frustrated and the review
process is interrupted. Sometimes the reviewer won't reply, and the
review also might be stuck (in this case you might want to ping the
patch).

Sometimes there is no qualified or interested developer around, or
maybe those ones are busy with other things (and it's easy to miss
a patch, especially if you don't check emails since a few days and you
got hundreds of backlog emails).

In general, this is done on a best effort basis (read as: most
developers are volunteers and they might have job/families/stuff to
tend to), there is no guarantee that a patch might be reviewed in a
timely fashion.

This is not a problem specific with FFmpeg, but in general with most
FLOSS projects.

Probably we should find ways to fund such activites, so that a
developer can spend more time on reviewing work, but this comes with
other risks/issues (since managing money is also complex of potential
tensions in a mostly volunteering-based project).

It's also very difficult to track the sent patches, and that's why
having a Pull-Request process a-la github has been proposed several
times; we cannot switch to github for several reasons (licensing and
affilitation issues with platform owner) and handling your own gitlab
is costly and we lack volunteers at the moment.

We are using patchwork to mitigate the tracking issue:
https://patchwork.ffmpeg.org/project/ffmpeg/list/

but that's not really providing an effective workflow.

Personally I find the status tracking confusing, e.g.:
https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=&submitter=&state=&q=TTML&archive=both&delegate=

I cannot easily figure out what was integrated and what not.
_______________________________________________
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".