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 B5EFD48DDA for ; Sun, 28 Jan 2024 20:33:38 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id A808068D181; Sun, 28 Jan 2024 22:33:37 +0200 (EET) Received: from relay1-d.mail.gandi.net (relay1-d.mail.gandi.net [217.70.183.193]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 87C0868D14A for ; Sun, 28 Jan 2024 22:33:30 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id CF96F240004; Sun, 28 Jan 2024 20:33:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1706474010; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=NS3FWW0maUoUCCztrJfmKy4ErVqE/FbPQVxImUJ8cwE=; b=LLTjjThDwrXyDM5LJhzAZUvBDrk+dntoFffX2KcU7NmCCnQ2teYMc9jsf8YvJ6j0LhV4EX XlTRe0wTwWZj4rn1sAI/NflJAufuKd7BZiTdHuW8rJPwYJirxQK9fO4Te64HWKpPHMuV1m 5OMK7SwcxA/3NeCLZ3Oz+WEVlWIJ5fHPeE4D7UHw0eTiL45PbAIs29ZlF/biggAo8++NRP R67SgXimfbDthPwWeKUv97xVou5GUP7tneltSGqG6nEnSwuzbpF911LSfbE7Akp6gONtO9 vqMmbxFxURoKtbFV84tP0X7jSDnqsY66CmEkh+f6NqtFRDXtB2HoyCWvQoI15A== Date: Sun, 28 Jan 2024 21:33:29 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240128203329.GQ6420@pb2> References: <20240128032549.GN6420@pb2> <1976392.nZu15OXtJW@basile.remlab.net> MIME-Version: 1.0 In-Reply-To: <1976392.nZu15OXtJW@basile.remlab.net> X-GND-Sasl: michael@niedermayer.cc 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: multipart/mixed; boundary="===============0579211319004739770==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============0579211319004739770== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="EPOcP+nFr63CSOLy" Content-Disposition: inline --EPOcP+nFr63CSOLy Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Remi, Jonatas (for the sanctioned list question) On Sun, Jan 28, 2024 at 09:17:03PM +0200, R=E9mi Denis-Courmont wrote: > Le sunnuntaina 28. tammikuuta 2024, 5.25.49 EET Michael Niedermayer a =E9= crit : > > Please read the following to get a better understanding what STF is abo= ut: > > (In short it is about maintenance and sustainability, not features) > > https://www.sovereigntechfund.de/programs/applications > >=20 > > As some probably already know, Thilo has worked with STF to work out > > many details of this. SPI will handle the financials for FFmpeg. >=20 > As anybody who's been following FFmpeg-devel knows, people have pointed o= ut=20 > SPI seems like a poor choice of vehicle for that sort of commission. I wo= n't=20 > repeat the arguments that were already made in the second half of last ye= ar. I have seen people associated with commercial entities (FFlabs and Videolab= s) being against SPI. Given that FFlabs tried to obtain money from STF there is significant confl= ict of interrest here. At least thats how it looks to me. Of course thats no reason to dismiss any arguments, its just some backgroun= d not everyone might be aware of >=20 > But I will add a few comments... >=20 > > Everyone willing to benefit from this sponsorship must not be a US sanc= tioned > > entity or in a US sanctioned country.=20 >=20 > In other words, the choice of a US vehicle is excluding people who are, o= r=20 > fear that they may be affected by US sanctions. Some active developers ar= e=20 > associated with, for example, the Chinese Academy of Science, Huawei=20 > Technologies or other Chinese IT R&D entites. This is discriminatory, and= thus=20 > something that an open-source project should actively seek to *avoid*. There are a few things here. First we dont sponsor huawei or another company, and iam also sure STF woul= d not approve that. Paying some employee of huawei or member of the Chinese Academy of Science IIUC would only be a problem if that person is personally on the sanctions = list. which you can check here: https://sanctionssearch.ofac.treas.gov/ But maybe Jonatas can confirm? Also i iam not sure germany/STF is ok with funding people on the OFAC list (they technically maybe should not care but i still would not assert that as a given) [...] > > > At this point, what we need is a list of Projects so we can submit an > > application to STF at or before 12th Feb. (at the 14th they have a meet= ing > > and will review our submission) What STF told us, they need ATM is: >=20 > The "selection criteria" seem rather restrictive. It seems that critical = tasks=20 > such as long-term maintainance (Anton) and security fixes (you) are in sc= ope.=20 > Though I can only agree with Kieran that SoW is ill-suited for tasks of t= he=20 > sort. If SPI insists on SoW, which is somewhat understandable from their = legal=20 > and moral standpoint, then that is another reason why SPI should not, or= =20 > maybe, cannot, be the vehicle. >=20 > By stretching the criteria a little, maybe reasonably expected external o= r=20 > normative updates are also in scope, like say implementing optimisations = for=20 > new ISA extensions or new codec profiles. But implementing entirely new= =20 > features seems unambiguously excluded, especially if competing with exist= ing=20 > open-source projects. Prototypes are also *explicitly* excluded. So for t= he=20 > sake of the argument, reimplementing X264, dav1d or GNU/radio functionali= ty in=20 > FFmpeg seems like it would not qualify. >=20 > I am not a lawyer, but there may be nontrivial legal implications for SPI= and=20 > the contractees here. Note that I do not mean to argue against the=20 > restrictions here. They make perfect sense considering that this funding = would=20 > ultimately come from the German tax payers. >=20 > (...) >=20 > > My suggestion is that we create a Trac WIKI page similar to the ideas > > page for GSoC. > > On that page everyone can add a project idea. > > The requirement is that > > 1. it must fit in the goals and mission and all of STF > > 2. it must be about FFmpeg (IIUC non coding tasks are ok) >=20 > IIUC, they are *not* OK, unless they are a dependency of a coding task: >=20 > | Development is our primary focus, although security audits, conference > | attendance, and other community-based events can be included in the > | application should they be necessary. The thing is, we can ask STF relatively easily if theres a specific task we want funded, to check what they think about it. features are not the primary focus of STF but the way i understood is that it would not be impossible for them to sponsor a feature if it fits their mission So STF seems quite reasonable. If you have a specific project idea that you would want funded, i or thilo can directly ask tara. I just dont want to ask hypothetical things. As that could annoy STF. thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Modern terrorism, a quick summary: Need oil, start war with country that has oil, kill hundread thousand in war. Let country fall into chaos, be surprised about raise of fundamantalists. Drop more bombs, kill more people, be surprised about them taking revenge and drop even more bombs and strip your own citizens of their rights and freedoms. to be continued --EPOcP+nFr63CSOLy Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZba6EgAKCRBhHseHBAsP qyU+AJ40jFKl9hqh8yfau1rnKfQhwHs5JwCeMHmePMz9nehlLfdo4XRE/hzokvc= =Lc85 -----END PGP SIGNATURE----- --EPOcP+nFr63CSOLy-- --===============0579211319004739770== 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". --===============0579211319004739770==--