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 643714756F for ; Thu, 12 Oct 2023 17:37:49 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 62AE768C8BE; Thu, 12 Oct 2023 20:37:47 +0300 (EEST) Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id B639E68C6DE for ; Thu, 12 Oct 2023 20:37:41 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id DF7DD60007 for ; Thu, 12 Oct 2023 17:37:40 +0000 (UTC) Date: Thu, 12 Oct 2023 19:37:39 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20231012173739.GN3543730@pb2> References: <20231011181015.6433-1-michael@niedermayer.cc> <20231011181015.6433-3-michael@niedermayer.cc> MIME-Version: 1.0 In-Reply-To: X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] [PATCH 3/3] doc: add spi.txt 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="===============1029935395538999628==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============1029935395538999628== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="UWzACjsgnYjrQHZk" Content-Disposition: inline --UWzACjsgnYjrQHZk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 12, 2023 at 10:03:20AM +0200, Andreas Rheinhardt wrote: > Michael Niedermayer: > > This explains how to request refunds and what can be funded by SPI > > --- > > doc/spi.txt | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 50 insertions(+) > > create mode 100644 doc/spi.txt > >=20 > > diff --git a/doc/spi.txt b/doc/spi.txt > > new file mode 100644 > > index 0000000000..7d85de8f09 > > --- /dev/null > > +++ b/doc/spi.txt > > @@ -0,0 +1,50 @@ > > +How to request refunds from SPI: > > +-------------------------------- > > +Send a mail to ffmpeg-devel with [REFUND-REQUEST] in the subject > > + > > + > > +What can be payed by SPI: > > +------------------------- > > +FFmpeg money collected at SPI can be used for any purpose which is OK = by > > +501(c)3 nonprofit rules, and within our mission (Free & OSS software). > > + > > +In practice we frequently payed for Travel and Hardware. > ^ ^ > t h >=20 > > +For other things, it is recommanded to disscuss them beforehand > ^ ^ > e >=20 > > +on ffmpeg-devel and if the community agrees to fund them, also with > > +SPI through stefano before starting with anything. > ^ > S >=20 > > + > > + > > +Is it possible to fund active development by SPI: > > +(the texts below have been taken from multiple > > + replies FFmpeg has received from SPI, they have been edited > > + so that "I" was replaced by "SPI" in some cases.) > > +------------------------------------------------- > > +Paying for development *does* require substantial > > +additional paperwork, but it is not prohibitied. > ^ >=20 > > + > > +Several SPI projects pay contractors for development > > +efforts. SPI needs a contract in place which describes the work to be > > +done. There are also various things SPI needs to check (e.g. are they= a > > +US person or not, as with GSoC mentor payments; are they really a > > +contractor and not a employee). > > + > > +SPI can't deal with employment at the moment because that involves a > > +lot of work, like health insurance, tax withholding, etc. Contractors > > +are easier because they have to take care of that themselves; Whether > > +someone is a contractor vs employee depends on various factors (that > > +of course are different in every country) and can be disputed (see > > +e.g. the debate about whether Uber drivers are employees); SPI has a > > +questionnaire about their circumstances.) > > + > > +Unfortunately, there's no one-size-fits all when dealing with contract= ors. > > +As already mentioned, without knowing the contributor's country > > + > > +SPI does have templates, but they depend on the contractors country. I= f it's > > +US, Australia, France and a couple others SPI could provide them next = day, > > +otherwise SPI would need to ask their attorney to draft one, which wou= ld > > +take some time > > + > > +Also, SPI has two models, MSA (which transfers ownership) and CSA (whi= ch > > +grants a license instead). SPI usually sends the MSA (it's better for = most > > +purposes), but for development purposes, some projects prefer that the > > +contractor retain ownership rights. > ^ > s >=20 > This should explain what the abbreviations stand for. I believe MSA stands for Master service agreement. I do not know what CSA s= tands for all other things fixed thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Everything should be made as simple as possible, but not simpler. -- Albert Einstein --UWzACjsgnYjrQHZk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZSgu4AAKCRBhHseHBAsP q3u+AJsF4vyCIQhopbnq7kUgzf0zRaG8FQCffzNRMFHvYsNz8sZVmhiSPqFPPbk= =DMan -----END PGP SIGNATURE----- --UWzACjsgnYjrQHZk-- --===============1029935395538999628== 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". --===============1029935395538999628==--