From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id AA42149725 for ; Thu, 18 Apr 2024 20:15:35 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 6F68368CF49; Thu, 18 Apr 2024 23:15:33 +0300 (EEST) Received: from relay7-d.mail.gandi.net (relay7-d.mail.gandi.net [217.70.183.200]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id BC4D7680068 for ; Thu, 18 Apr 2024 23:15:26 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id E2E7520004 for ; Thu, 18 Apr 2024 20:15:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1713471326; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=UYKbYILcgdOXTX25nxD46Wwjt7D3LkU6D4DQMKcK8Us=; b=Tr0O0vi8J9MaotgO29LpSRvYiKlUF04G5Pe4YCtNdCrw16RzXwZb1haPWujzxTJzUUrohA 81P8YiYUuZFLL51R1KB0AlwfbA2iR9kOMI7k0y5bXr+cpzUrVXYe5ORtdSTjRMG8iqCmyf hjLSp7kc5c0a7bpBYY3K3tFgid2qZKe3LjgOYo2IGNnTB+mAnUMZkMBPLmvioPwmspO02V +isCLo6Ynwe/mcUupOd90nGhOKOIdW7tDooWEoH6VokbZCsvKeTHAp0crhGMGcTYv8VwV1 L+KMhCQKYQ6heu5alKrmA61FheHHkrxMx431Dtu6gUPcymp9e5YbKHBeKNDnSQ== Date: Thu, 18 Apr 2024 22:15:25 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240418201525.GR6420@pb2> References: <20240417135832.GJ6420@pb2> MIME-Version: 1.0 In-Reply-To: X-Spam-Flag: yes X-Spam-Level: *********** X-GND-Spam-Score: 165 X-GND-Status: SPAM X-GND-Sasl: michael@niedermayer.cc 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: multipart/mixed; boundary="===============5906224536771936858==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============5906224536771936858== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="29qiwH/IWihEz+CP" Content-Disposition: inline --29qiwH/IWihEz+CP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 18, 2024 at 10:19:50AM +0200, Stefano Sabatini wrote: > 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. > >=20 > > But there are issues: > [...] >=20 > > I submitted a patch for a TTML decoder because I thought it would be gr= eat. > > It was completely ignored. >=20 > Please ping the patch or send a new one. >=20 > > If my patch was seriously bad, then fine. But seriously *no one cared*. >=20 > I think contribution management is a serious issue here. >=20 > 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. >=20 > 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). >=20 > 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). >=20 > 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. >=20 > This is not a problem specific with FFmpeg, but in general with most > FLOSS projects. >=20 > 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). >=20 > 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. >=20 > We are using patchwork to mitigate the tracking issue: > https://patchwork.ffmpeg.org/project/ffmpeg/list/ >=20 > but that's not really providing an effective workflow. >=20 > Personally I find the status tracking confusing, e.g.: > https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=3D&submitter=3D&= state=3D&q=3DTTML&archive=3Dboth&delegate=3D >=20 > I cannot easily figure out what was integrated and what not. Would it help if i add a "patch" type to trac.ffmpeg.org ? If patches are missed on patchwork or its confusing, then patch authors could open such a ticket type=3Dpatch that points to the patc= hwork patch as tickets have all the metadata from keywords over priority to component and do also allow voting. It may help keeping track of patches and also allow the community to express their preferance with voting. thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB When the tyrant has disposed of foreign enemies by conquest or treaty, and there is nothing more to fear from them, then he is always stirring up some war or other, in order that the people may require a leader. -- Plato --29qiwH/IWihEz+CP Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZiF/VgAKCRBhHseHBAsP q63IAJ9Qef0xKPr7ts6gCNA8w51Y1E7HLACfUprPKBVOoEc94lo6IFk+mS/I+48= =N0WW -----END PGP SIGNATURE----- --29qiwH/IWihEz+CP-- --===============5906224536771936858== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============5906224536771936858==--