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 443894A8AA for ; Thu, 18 Apr 2024 10:11:03 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id EFA3968D448; Thu, 18 Apr 2024 13:11:00 +0300 (EEST) Received: from mail-qt1-f178.google.com (mail-qt1-f178.google.com [209.85.160.178]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id E1D9B68D25A for ; Thu, 18 Apr 2024 13:10:54 +0300 (EEST) Received: by mail-qt1-f178.google.com with SMTP id d75a77b69052e-434b7ab085fso13873531cf.1 for ; Thu, 18 Apr 2024 03:10:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713435053; x=1714039853; darn=ffmpeg.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=qrEbOwVEueg6mBHKopj7f0nnft0+b1MBEbWOdUbA58M=; b=aNDaIp8sXmNKXEG9bh8L2iFLz7hfpwRthmWCbGg2ia4nOkTf1zFDGDkRj96mOSvAQ7 fvI45/EbQ73vAUWWpSdwrvwGC/rP8OQEyrepdi40DAzPwtI64A8GH5HHHZqYiHjoW4CT Hdz9asdHvw+GApQlmksFAs6dHUCTO7tVOuylXmnPlNXcVzeSSE3IPAnrezOrTKofcmwz CtMN38aPBbbcBqWr6M2tu2luDg36YKD0v3/v4T5Sc0krF5oOQiOyjqyos/AyzhI8KJEN dpqwB7ek1x8UsLyqmPRvTStjuk/also98kSroayNBaJzXJpFiNxOgjoHfl/joI7tCBqK 9EZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713435053; x=1714039853; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=qrEbOwVEueg6mBHKopj7f0nnft0+b1MBEbWOdUbA58M=; b=QpIDbYcdw+PkPvdDiuPrpt2DOiQ96vdRaRAsvcgT7x78FXd/4mLQYYU4Dej3B4vV2E mB3gGfRPa0IMDlyCZ/iWDSo/r12WSdd7NKZS5xZ+INX7t0DCZEBs/awoM/eHhoTi5lTA mBys/k5LVpOFhMBR/7vWgmEZZ5fMq+0NO4pk9+XJ5lxk/c41ezLa1z1u1lcs/GYF0HnC 8aMPeiqbB1L5o82AamPQRBdrUpBezCYRf/PfaPzPeM9BzXO4Llr186ZLVTbNWVArdYpW gp8YigMx29skyHn5ELDBi2IQQdeRBUpOmUrujw4eetLVRyiM2N6jok+drrjCBAim8BKJ zU5w== X-Gm-Message-State: AOJu0Yz6tRhEFDNeMXolBuGrAaXJvtSPixL+yjR7Se/pXA3yOfChJweq LM0F6+ln3EBNXIB/a1+J7aHDoLgw6BPz9Wr2vdKiZ4N3rOYTclJDPPT0vTNQjcxECtV+iAqbJGo IEibayNs7NNFGSLKbB15ej/wP5KXpbP6y8Yo= X-Google-Smtp-Source: AGHT+IHVnsERc+9mYHpH2pDNk21gQVihP2F+Qso5THWzixkNn/Dv/D6F3FfKQG7IC4k4TtDyFIuaWC/zxJWkJhk57P4= X-Received: by 2002:ac8:5849:0:b0:437:658e:bf5a with SMTP id h9-20020ac85849000000b00437658ebf5amr3074617qth.32.1713435053194; Thu, 18 Apr 2024 03:10:53 -0700 (PDT) MIME-Version: 1.0 References: <20240417135832.GJ6420@pb2> In-Reply-To: From: Aidan Date: Thu, 18 Apr 2024 03:10:40 -0700 Message-ID: To: FFmpeg development discussions and patches X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: > > On date Wednesday 2024-04-17 19:21:39 -0700, Aidan wrote: > > 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 > I should probably redo my patch at this point. It's a year old. It's kind of a complicated patch because TTML is a huge format. It would be great to have a TTML decoder existing in FFmpeg. I guess if I do submit one, I will be more annoying about pinging. There is nowhere saying bumping every few weeks is ok. I read all documentation related to sending a patch. > > 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. > The only few times I've been completely ignored while trying to contribute to FLOSS software was software that ended up being forked with a better alternative because it was run by shitty people. However I am not saying that FFmpeg is that way. > 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) Yep, you are completely right. I cannot say you aren't right. > 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. I saw that conversation. It just sounds like over-complication for this project. Email can be okay if done right. Not user-friendly but if its documented good then its mostly fine. > > 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. > Funny to see my old patch on that list. Kind regards, Aidan / TheDaChicken _______________________________________________ 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".