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 ADA3B47A36 for ; Sun, 28 Jan 2024 03:26:00 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 75ABE68D149; Sun, 28 Jan 2024 05:25:57 +0200 (EET) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id F26FA68C2FE for ; Sun, 28 Jan 2024 05:25:50 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id 4AA381C0007 for ; Sun, 28 Jan 2024 03:25:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1706412350; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=hqFmU/IqVn8Py3LtBbo+zkHdCFkB4NkzqD1W8gWK5CE=; b=MTfEnPAipEiCfabMSICq2lL+xoeBJbkzvSEnt+J+7c5W89G1JrJ/EqQQiT20PWiLuDMdZs xmSvu4SS8pzrPtIsU2Nq/cGWJ3ntJ81dDerVsU8WmCqEE1zkNTA8rI9nZscYe1O9VjCfKA oYR4i57hL6668CDFuCJIsVKrBB1bIVHZm4YhO9ZzxL+mqRd+A5wUy3prHKQEA7qtPA9aH6 Msy4NdrQO0ppPv3UsVxXpnZW3ofbCOjQJk0ORM9hopafK1DcqwhiffKzKv90zTf5Cq0sE+ kDkwJkA0sV4Tnli0i7mv0GZ1yrQ10xD9HnMlMZFkDVXPxq2LlUe4ko8nZHq4Ww== Date: Sun, 28 Jan 2024 04:25:49 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240128032549.GN6420@pb2> MIME-Version: 1.0 X-GND-Sasl: michael@niedermayer.cc Subject: [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 Content-Type: multipart/mixed; boundary="===============8355753430481522503==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============8355753430481522503== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="WMO2RBxtllpoaZld" Content-Disposition: inline --WMO2RBxtllpoaZld Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all We are offered to apply for a sponsorship of FFmpeg by the Sovereign Tech F= und (STF). Please read the following to get a better understanding what STF is about: (In short it is about maintenance and sustainability, not features) https://www.sovereigntechfund.de/programs/applications As some probably already know, Thilo has worked with STF to work out many details of this. SPI will handle the financials for FFmpeg. Everyone willing to benefit from this sponsorship must not be a US sanction= ed entity or in a US sanctioned country. And must sign a contractor agreement and simplified SoW with SPI. "A SOW purpose is to protect the contracted from doing a work and not getting paid, and to protect the contractor from paying for a work which wasn't wanted" At this point, what we need is a list of Projects so we can submit an appli= cation to STF at or before 12th Feb. (at the 14th they have a meeting and will review our= submission) What STF told us, they need ATM is: - A scope of work for the project to defined before hand for the upcoming r= eview and eventually a contract. It doesn=E2=80=99t have to be tied to spec= ific people. - The contract STF will sign with SPI will be a service agreement based on = that SOW and milestones. Payment of invoices will be contingent and after d= elivery (aka performance) of agreed upon milestones. 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) 3. it must have a developer willing to do the work and a monetary amount as well as a expected time frame. Of course these don't need to be added at the same time you can add an idea and someone else can add herself as person doing the work. But for consideration it needs to contain all parts 4. The developer doing the work must be qualified. An easy way to ensure this, is that (s)he has at least 100 authored commits in FFmpeg. According to STF, April 1st is a possible start date for the work and STF w= ould also like to know if the work will be finished in 2024 or 2025 for their budget. the SoW can be for example: "do X by date Y to receive Z", but according to SPI it can also be "only tasks X are eligible, invoices should be sent by date Y, and payment will not exceed the budget Z" "Ideally, it should also mention the parameters for how much each thing done is worth =E2=80=94 eg. If you're p= aying for hours or for tasks, and how much =E2=80=94 as the SOW is supposed to give = the contracted person means to know how much they'll be paid for what they do." "SOW should also note that if no valid tasks are performed, no payment will be made." Next step. For each Project suggestion from the wiki page we will send a mail to the ML with a copy and paste of the project suggestion. Once an apparent consensus is reached. This is the communities opportunity to object or approve the suggestion. Anyone can call for a formal vote of the GA here too if they do not want to object/approve in public. But i hope we can avoid that overhead. All suggested project ideas will then be submitted to STF We have never done STF before so there likely will be some surprises and we may need to adjust in case we hit any issues. and I also didn't expect to be involved in this but i don't want to stand around and have the opportunity for FFmpeg lost There can be no late objections here to any project suggestions. Objections must be before a project suggestion is submitted to STF, objections after that cannot be considered! Also once the person doing the work reaches the agreed milestone. She will submit an invoice with stefano and my help to SPI/STF. (in the unlikely case of a dispute on reaching a milestone it would be decided by the technical committee if the milestone has been reached from FFmpegs point of view) Thanks --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB It is what and why we do it that matters, not just one of them. --WMO2RBxtllpoaZld Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZbXJOQAKCRBhHseHBAsP qy4XAJ4yoRIY0Vm0zZU3E+ec2HPapir25ACeKcMs/noFnjvpRmj+Ondn0mkTm30= =T5Kg -----END PGP SIGNATURE----- --WMO2RBxtllpoaZld-- --===============8355753430481522503== 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". --===============8355753430481522503==--