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 74D524907C for ; Wed, 31 Jan 2024 23:15:16 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id F07E868CF98; Thu, 1 Feb 2024 01:15:12 +0200 (EET) Received: from mail-ej1-f46.google.com (mail-ej1-f46.google.com [209.85.218.46]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id AB05768C44F for ; Thu, 1 Feb 2024 01:15:06 +0200 (EET) Received: by mail-ej1-f46.google.com with SMTP id a640c23a62f3a-a30e445602cso322469266b.0 for ; Wed, 31 Jan 2024 15:15:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706742905; x=1707347705; darn=ffmpeg.org; h=user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=T1fqeII3gi3ZcbVBerJypgDnvycL/WYmmQx2GgAtFKo=; b=Ct42louG2fA0auA5L+/G2nzv4lcMRn1lUWd/VoCV8z22rzMopFTvCelnZYnvMNjdEB zqSNuZw1UsmdzhafKdsj+0G49DrEEbd4S6ZfreDmD7RNMIvZswm8VgcXwbMWgxCY9bof 1P2ueT7WV5EW9okPEkKM3Rt3zBG9U7LofSEdIt+OnUpiB+mKG+LziWHEDP+r5uu6WZe7 tQlDlrG/7CzqTJVYfRJL/SZPiU2P5vFn9GqaFRdcqePk8cd6sfCjDvyC8B187T2dTaXl NUdilVAwi0EQm37KZZxP57wE1JBo8DpOXpPx1OgV+z1+0Ws42r1j2fsFP5OUeBYs6iGF Wl0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706742905; x=1707347705; h=user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=T1fqeII3gi3ZcbVBerJypgDnvycL/WYmmQx2GgAtFKo=; b=D+1b7lSSVKZz9kbCOzwmKh7w0axg3DKWTdZ/Xkr4OldpjnINuZhJkahpH+94nq/KRT 2b/g48JqtMqyZFFdsNW5f5T4l/HVLHad033Zj4ot53fV5221p/tq21VU4LOzTYvJiFm/ A68NPUNNCNnrTfUwDhfYNuomu2kITP1vabNEbqUWMLm/L75l4NH0SxLxYeVbiZab1A1s mU1iQlus/pMG1Oosw0iARrW1TJAA0AmEPY8qH7Afu6zAzllBkpBhYSrl0tfrMBqByvm9 DOl5LgW+twFP9+xN9d1b9MZbMkcLBFTsM+NmD5Lnse4NAmBzWIQl/N2foBZAR0+x57D6 LGUw== X-Gm-Message-State: AOJu0Yx4z4xxziMRoVyDJrpuZOZ6XUNxzKMFXsW7V2rGiZb0Xzv53rFj 4PIL59fZEUu72PDk7jcYcAk+4l/sOEeNZx1pndaKImjIBP79dIXfQp+mwRdT X-Google-Smtp-Source: AGHT+IEo8uPkswPiobfHgkfSH7y5DAIq7jvSkTXBeXasi+ZBGFwb1lqzXDboZge0iGDKTr7A0o/trA== X-Received: by 2002:a17:906:8413:b0:a36:5924:77e0 with SMTP id n19-20020a170906841300b00a36592477e0mr2793765ejx.10.1706742904979; Wed, 31 Jan 2024 15:15:04 -0800 (PST) Received: from mariano (dynamic-adsl-84-220-189-10.clienti.tiscali.it. [84.220.189.10]) by smtp.gmail.com with ESMTPSA id vo6-20020a170907a80600b00a36915d811dsm662466ejc.184.2024.01.31.15.15.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 31 Jan 2024 15:15:04 -0800 (PST) Received: by mariano (Postfix, from userid 1000) id A0E47BFB9D; Thu, 1 Feb 2024 00:15:03 +0100 (CET) Date: Thu, 1 Feb 2024 00:15:03 +0100 From: Stefano Sabatini To: FFmpeg development discussions and patches Message-ID: Mail-Followup-To: FFmpeg development discussions and patches , "Jonatas L. Nogueira" References: <20240128032549.GN6420@pb2> <170670599775.8914.331021234730065376@lain.khirnov.net> <25474700.8Xr1rsAvgU@basile.remlab.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <25474700.8Xr1rsAvgU@basile.remlab.net> User-Agent: Mutt/2.1.4 (2021-12-11) Subject: Re: [FFmpeg-devel] Sovereign Tech Fund 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: "Jonatas L. Nogueira" Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On date Wednesday 2024-01-31 18:10:57 +0200, R=E9mi Denis-Courmont wrote: > Hi, [...] > Sarcasm aside, I take that to mean that SPI has been involved with those = > discussions for months in a private and closed process. Michael asserted = that = > an open inclusive process is better than the usual closed approach whence= the = > funding goes through a company. > > It looks to me that those SPI discussions were just as opaque and closed,= and = > all the talk of openess is just pretense. It does not help that Michael, = and = > now you too, misrepresent any challenge to SPI proposed *process* as an = > attempt to reject the idea of STF sponsorship, under the convenient prete= xt = > that there is not enough time. > = > This is further aggravated by the context that Michael brought forward th= e = > idea of funding developers through SPI 3 months ago (in actual Earth unit= s). = > From your statement, I have to infer that Thilo, Michael and SPI already = knew = > of the STF plan and concealed that key piece of contextual information ba= ck = > then. > Jos=E9 already provided and excellent summary from his side. On my side I can say I was involved in the discussion, and that this was mostly about the feasibility and the groundwork of approaching STF and later SPI. So in my opinion there was no need to involve the community at that early stage, especially given that until the past week there was still no evidence that STF was providing a grant (and BTW, still this needs to be substantiated with a SOW and then it will have to be reviewed and approved on the STF side). Also SPI was involved at a later stage, after the investigation about using the donors fund for active development (which also involves the handling of SOW from SPI to the individual contributor). The main result of that investigation was discussed in the open and can be found here: https://ffmpeg.org/pipermail/ffmpeg-devel/2023-October/315702.html If I undestand it correctly, it was never committed because there was a disagreement about where to put it (ffmpeg or ffmpeg-web) and about the general intent, then at some point the discussion died off before a conclusion was really reached. Note that the focus in that case was to make good use of the donations fund (keeping it in the account is not a good use for it). > In hindsight, it feels hypocritical to me that they were arguing for the = SPI = > path, and against the corporate path, on the basis of openess already the= n, to = > be honest. > > I can only agree with Anton that this looks like an attempt to strongarm = the = > community. This is ostensibly being to ignore all the objections that wer= e = > already brought in October and are being brought again now, with the = > complicity of SPI. I can't say that this looks well on SPI, but that's ju= st my = > personal opinion. SPI was involved at a later stage to act as fiscal sponsor for STF. Just to reiterate, SPI involvement was requested, and was not actively seeked by SPI itself. I cannot read any attempt to strongarm the community, nor I see why this should challenge the corporate path (which has a different focus and has its own merits). > With all that said, I don't think anybody will attempt to prevent this fr= om = > happening (if they even can?). But that will take place without the conse= nt of = > the GA, without any legitimacy on the claims of openess and inclusiveness= , and = > obviously without any form of preclearance from the technical appropriate= ness = > of the resulting code contributions. It's unfortunate there is a tight deadline - one option would be to try to delay the deadline and ask General Assembly for a vote before the application is sent - we might probably want both things to avoid the feeling that this is done against the "community" and create a tense environment, but any of this might probably result in voiding the opportunity. Also, it should be assumed that this proposal was done in good faith, in view of the sustainability discussions done in the past months. _______________________________________________ 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".