From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id E225940054 for ; Wed, 15 Oct 2025 14:53:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ffmpeg.org; i=@ffmpeg.org; q=dns/txt; s=mail; t=1760540023; h=date : to : message-id : references : mime-version : in-reply-to : reply-to : subject : list-id : list-archive : list-archive : list-help : list-owner : list-post : list-subscribe : list-unsubscribe : from : cc : content-type : content-transfer-encoding : from; bh=qwqX3xSOABqYwf3eYs9tjldb68GPSk9soqmG33xYhTU=; b=AI18sB7mvBBUgfxobXijeIpx+XspO+cODLOHA5QcmlKpEmUNZBslQVeDzYfX/izqHGhed 4e471iNxXrJ948OuFudvqqNPF446K8U0Zr6vnDYdnclckLrB7zRcCV161nAL5Mkai+OogzJ bVd1ytaPxgYVGtlXKH0djzF0jMcLFoxoPFOppHsF2ewezjp2027668mtPbalP0FOB0tpZaD btigyEj2f7Zj5Y4aUQ+ujAeYH2ZXPF14X+cn0Qk1FBBc7aVU5/K3KtOdiAU6VJ3xpX8jm1m iTiOBMHlB6COioJraqNdqB04qy7//yIMwFB0gl6vGNcf+F2QbTEqc3R9OZUA== Received: from [172.19.0.4] (unknown [172.19.0.4]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 5ED9868F3A5; Wed, 15 Oct 2025 17:53:43 +0300 (EEST) ARC-Seal: i=1; cv=none; a=rsa-sha256; d=ffmpeg.org; s=arc; t=1760540020; b=MUPNzqSO9jLrhsxbHS1TEaQZuW4DG0bBS4Ar0j3qB5c74lwSoMyFimlI7TXPmMw6Gwch5 1VIJnbxgle5EQFc8arstbKzwUbDpjscOlgCCcurQlr73tA+5RLLW2j6B/ay/lypa//Lalu+ wBj+d5bbFufia/ew/QhhIUhpAQ8aGSXXhHI3QC078uVEosQESp4D6NVNp3dhpErlh3xI5Gt QHM2xbv+Pgk4WC+A7FK95EdFpUrTP87K4Q/M30daox/fS3FJNkwXwmj2Na1AhW3hIfOv23/ S9PVnRpzam5BRGebSkl2CJRXCyFdAbPuewDdOMh3wfv790rB/HOOwK3P111w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=ffmpeg.org; s=arc; t=1760540020; h=from : sender : reply-to : subject : date : message-id : to : cc : mime-version : content-type : content-transfer-encoding : content-id : content-description : resent-date : resent-from : resent-sender : resent-to : resent-cc : resent-message-id : in-reply-to : references : list-id : list-help : list-unsubscribe : list-subscribe : list-post : list-owner : list-archive; bh=T/Z4cxEezUzE5wUqtrhNbiebuLQjK8oEArfSa8UiVds=; b=K96P2yJcS21pu/yFkP9+WasdWJdRYY16sd8R1oCon5uQ+JlerhLUR3LzaV9g9vMlVLvvH yQdTk/9fLO/cw0aU1zk4BuPSnoiFO6S9od37Du54KLfu4jtv6kdDeWTmx6w3jiJW8cP/gUR Y2ClcOIYz8rzx3e9a620GnfaV1T0NJuFI2nDfUGK1XbazEKJGjKBCSBwgFTKRWKhgUz2S+a ipnMPu++kot7AKwEPypEaGlc6MHGP9w66YBpDmWAtSe/bAdcyURvGRiuqPPDV0FKHUIzDUl 5y78mNXBG8qp7DDhIes6kN4MltKdn3Tvaz4mBqLoM9Q2yTIC2djhxAUXBYwA== ARC-Authentication-Results: i=1; ffmpeg.org; dkim=fail; arc=none; dmarc=none Authentication-Results: ffmpeg.org; dkim=fail; arc=none (Message is not ARC signed); dmarc=none Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id E6DC868F28B for ; Wed, 15 Oct 2025 17:53:28 +0300 (EEST) X-ENS-nef-client: 129.199.129.80 ( name = phare.normalesup.org ) Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80]) by nef.ens.fr (8.14.4/1.01.28121999) with ESMTP id 59FErSAj004650 for ; Wed, 15 Oct 2025 16:53:28 +0200 Received: by phare.normalesup.org (Postfix, from userid 1001) id 327512EFE6; Wed, 15 Oct 2025 16:53:28 +0200 (CEST) Date: Wed, 15 Oct 2025 16:53:28 +0200 To: FFmpeg development discussions and patches Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Wed, 15 Oct 2025 16:53:28 +0200 (CEST) Message-ID-Hash: O2KQMYFDUZ7RPFSPJH6NZJ3A4RWNK4KU X-Message-ID-Hash: O2KQMYFDUZ7RPFSPJH6NZJ3A4RWNK4KU X-MailFrom: SRS0=cQ4G=4Y=phare.normalesup.org=george@ffmpeg.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-ffmpeg-devel.ffmpeg.org-0; header-match-ffmpeg-devel.ffmpeg.org-1; header-match-ffmpeg-devel.ffmpeg.org-2; header-match-ffmpeg-devel.ffmpeg.org-3; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list Reply-To: FFmpeg development discussions and patches Subject: [FFmpeg-devel] Re: [RFC] Funded Task Ideas List-Id: FFmpeg development discussions and patches Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: Nicolas George via ffmpeg-devel Cc: Nicolas George Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Archived-At: List-Archive: List-Post: Michael Niedermayer via ffmpeg-devel (HE12025-10-14): > As we are now looking for sponsors, we also should look for tasks to fund. > PS: once we have enough yearly income we can look at hiring / funding > people fulltime. I will step into it: This is severely misguided. FFmpeg is a Libre Software project: its goal is to make beautiful and/or useful software. FFmpeg's goal is NOT to gain market shares. FFmpeg's goal is NOT to turn a profit. FFmpeg's goal is ABSOLUTELY NOT to get a livelihood for its authors. The problem with people getting paid to work on FFmpeg is that it is a misaligned incentive. It creates the incentive to push the code as is instead of polishing it, instead of accepting suggestions to make it better. It creates the incentive to work alone rather than seek the insights of our peers. I am sure some developers are able to resist the incentive and not let the fact that they are paid for it reduce the quality of their code in favor of speed at all. But I am also sure they are not a majority. So, sponsorships? Sponsorship in the form of hosting, absolutely! Sponsorship in the form of hardware, server hardware that can benefit the whole project as a FATE instance or remote development computer, absolutely. Sponsorship in the form of hardware personal for one developer in particular: that is already more problematic. Sponsorship in the form of funding people to code: this is where it becomes difficult. I think we can fund tasks that have a very precise scope: straightforward tasks that require no creativity from the coder and where the completion status is objective and unambiguous. But beyond that, we should not try to fund: anything that requires design choices, anything involving new API, etc., we should favor people who do it because they want to do it. We cannot prevent people from obtaining funding on their own, of course, and neither should we. But at least we will not be in a situation of conflict of interest: if the task is harder than they thought, if we demand they do it better, it is between them and their sponsor, and we are not in an awkward position. Also, I think we should demand people to disclose when they have specific funding like that, on pain of getting their Git write access suspended if they neglected to do it and it gets known. We should know when somebody's loyalty is to themselves and their sponsor rather than to the project. Regards, -- Nicolas George _______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org