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 B71E647896 for ; Fri, 27 Oct 2023 01:28:48 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id A156368CB33; Fri, 27 Oct 2023 04:28:45 +0300 (EEST) Received: from mail-qv1-f47.google.com (mail-qv1-f47.google.com [209.85.219.47]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id B556968C95C for ; Fri, 27 Oct 2023 04:28:38 +0300 (EEST) Received: by mail-qv1-f47.google.com with SMTP id 6a1803df08f44-65b0e623189so10483156d6.1 for ; Thu, 26 Oct 2023 18:28:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ob-encoder-com.20230601.gappssmtp.com; s=20230601; t=1698370117; x=1698974917; darn=ffmpeg.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=KCr0HSuFiGl1Lre5ubqFZkwYjkq1gDpXQIhyBNW8EPw=; b=ZlR/kf+HwZO4HW2dy7r5pD5+ZJkLXIwykgN0fc4mPLviIkG/jh59tUsKMIeurPttFH f3pHJDI/BFgJO1Fc7peaYRIDMo4wq1GDKNTePZ6yN8aJP+xMbYDUmLxrPPuez65xQyQX QFXpxOyz0I0amSqX32x96hPeZU5T+yHraFGOjVlfgoZMLhUkjLoutADo9pvYsEoPREsV 8R39vbbmpjvJE2nh8ULuyqVr/P0oUVQqypsvjn/b5yFiowMZ0LGIar8aVoae5sqRlKrV G/N4XC6vYNIe0cPpj5RMhYJeB9p78oy1KI+MQzkG/AeNJUDq++yaCaVL2uNX1H4P4O8F u7yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698370117; x=1698974917; h=cc: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=KCr0HSuFiGl1Lre5ubqFZkwYjkq1gDpXQIhyBNW8EPw=; b=XSbaGngvMzg6lQx/F4opbKOH1jxowXHXdXYwHH8EjNZnHnRYDKxbZB0rP7zg+Yv5vp MHMW/88nNFCvoS+MC/CIIWf+qlZ1CmQ4zt9jYNMZOVIi5Gqvq4j9jBVhtXLZAKg4yo1F 9+Vp9f1KgN3UIVad/iGsIrXOwW46wOM9IKvRpChBtsFS3RIJmxbvOBf0nqBM2cJl/UqJ CVPHVoUnCSGtLIkv5suTw26RhiWDKDlZ8OVzrTQnZURpChqiEnbC7fR2Xail0NmPwJoM v5ptmNdIHhznMd5SQ38xwcce+ae6QF0z9j69inzZQ4XOaODslVgnDfq62iADSa2yOL3w yqQg== X-Gm-Message-State: AOJu0Yzphf/Oi4gm1IKnJ88mzQT9Sat6UR7K894TgOIj6ZSA1Fbll+A7 zNms5nTXAhGYDSXZkTPyoCEnKQtYaiZdipVLdtD1cSUsvUmkX2drKkmryw== X-Google-Smtp-Source: AGHT+IEaCX1+EqBGUKBPbbFx1khTgi2S9NrzgOKxsN8ZX/m4H6JWW9PmYXyZVUKQx4sbreyPZClpjZnHZVljSpT4UAA= X-Received: by 2002:a05:6214:f06:b0:66d:236f:2b89 with SMTP id gw6-20020a0562140f0600b0066d236f2b89mr1621390qvb.47.1698370116155; Thu, 26 Oct 2023 18:28:36 -0700 (PDT) MIME-Version: 1.0 References: <20231026154523.GI3543730@pb2> <9dc06c51-3aa0-3b71-b0a6-12a5e4cfe662@mail.de> In-Reply-To: <9dc06c51-3aa0-3b71-b0a6-12a5e4cfe662@mail.de> From: Kieran Kunhya Date: Thu, 26 Oct 2023 18:28:25 -0700 Message-ID: To: FFmpeg development discussions and patches X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [FFmpeg-devel] [RFC] financial sustainability Plan A (SPI) 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 Cc: Thilo Borgmann 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: Hi, On Thu, 26 Oct 2023 at 12:41, Thilo Borgmann via ffmpeg-devel < ffmpeg-devel@ffmpeg.org> wrote: > Of course. FFmpeg has a donations account. So the money is already there > and > already used for the reimbursement requests. Whatever we spent it for > needs to > be decided by the community. Spending more money instead of just watch it > growing is a good thing. That this will lead to more "disaster" is an > assumption > without basis. Even if this does happen and fails, its still better than > not > having even tried. > Reimbursement requests for clearly defined things like travel costs with receipts, or hardware that the project owns is in no way comparable to consulting work, contracts, statements of work etc. And the current swscale proposal is far from this too. > Also, you just advertised FFmpeg and asked for more financial support in > your > talk at Demuxed [1] - so I figure your prefered way of doing that would be > to > channel money into some company without the community being involved? > Actually if you watched the presentation, I said big companies need to support maintenance (not the same as bounties) of FFmpeg by hiring employees to work full time as they do with Linux Kernel maintainers. Or failing that they can donate to the community - but as you know well the numbers we have are not enough to hire full time maintainers. Agreement via mailing list for money is a recipe for disaster. What we need are clear statements of work that are voted on by TC. We can't even agree on patch reviews, throwing money into the mix is throwing gasoline into the fire. And since you also advertised explicitly for FFlabs - what is your relation > to > FFlabs? I own 25% of that company and I am not aware of any relationship. > You > just did advertise FFlabs because... FFlabs exists? FFlabs is a company > co-owned > by some FFmpeg developers, it's not FFmpeg nor can it represent it or act > on its > behalf. > I linked to the consulting page and also to FFlabs which as far as I know is the only company offering an SLA on FFmpeg. If others existed I would have included them. > As soon as we pay developers via SPI it can become a good zero-trust > environment > for donators to offer tasks & money to FFmpeg and handle the money flow > via SPI. > The donators can be sure that their issues are handled properly in the > project > (on the ML) and do not flow away into some other sink and the developers > can be > sure to get their money from SPI because the offer is public and backed by > the > FFmpeg SPI account. Sounds like a quite trustworthy and most importantyl > transparent way to handle things and build up trust in potential donators > that > the money they spent actually end up with FFmpeg. > Do you really think the way SPI funding is managed currently matches your description? Stefano approves by saying "Approved on my side, pending Michael's approval." This is not at all a community driven process where one person can veto everything. > I don't think developers should be paid via SPI for this reason. > > I think supporting FFmpeg developers via SPI fits perfectly into what we > have > SPI for in the first place - an independant entity that handles the > community > funds with absolute objectivity and no intrinsic interest whatsoever. In > contrast to any company, including (my own-ish) FFlabs. > If there is disagreement (which will be inevitable) SPI will not step in. Money is only going to make our current ML drama situation worse. Regards, Kieran Kunhya _______________________________________________ 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".