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 8A7734629D for ; Fri, 13 Oct 2023 18:33:42 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 4B95A68C94A; Fri, 13 Oct 2023 21:33:34 +0300 (EEST) Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [217.70.183.194]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 53C3168C901 for ; Fri, 13 Oct 2023 21:33:28 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id 6C09140005 for ; Fri, 13 Oct 2023 18:33:27 +0000 (UTC) Date: Fri, 13 Oct 2023 20:33:26 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20231013183326.GP3543730@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="===============3692507240793119955==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============3692507240793119955== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Jy7fHMWyH2pKEqn7" Content-Disposition: inline --Jy7fHMWyH2pKEqn7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 13, 2023 at 12:53:34AM +0200, Stefano Sabatini wrote: > On date Wednesday 2023-10-11 20:10:15 +0200, Michael Niedermayer wrote: > > 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 @@ >=20 > Add a short introduction about SPI here. >=20 > SPI (Software in the Public Interest) is a non-profit corporation > registered in the state of New York founded to act as a fiscal sponsor > for organizations that develop open source software and hardware. For > details check here: > https://www.spi-inc.org/ >=20 > FFmpeg is an SPI associated project and donations can be collected and > handled by SPI on behalf of FFmpeg. For details about the association > check here: > https://www.spi-inc.org/projects/ffmpeg/ >=20 >=20 > > +How to request refunds from SPI: > > +-------------------------------- > > +Send a mail to ffmpeg-devel with [REFUND-REQUEST] in the subject >=20 > Expanding on this: >=20 > Send a mail to ffmpeg-devel with the [REFUND-REQUEST] tag and a short > description of the refund topic in the subject. >=20 > In the mail, you also need to provide the amount to be refunded, with > a short description of how the money was spent. >=20 > There is no need and is not recommeded to send receipts when sending > the refund request on the ffmpeg-devel mailing-list, but they are > usually needed later when the request is approved and the refund > request is sent to SPI: > https://www.spi-inc.org/treasurer/reimbursement-form/ >=20 > > + > > + > > +What can be payed by SPI: > > +------------------------- >=20 > > +FFmpeg money collected at SPI can be used for any purpose which is OK = by >=20 > OK =3D> fine/compliant/in line with >=20 > > +501(c)3 nonprofit rules, and within our mission (Free & OSS software). > > + > > +In practice we frequently payed for Travel and Hardware. >=20 > > +For other things, it is recommanded to disscuss them beforehand >=20 > recommended .. to discuss >=20 > > +on ffmpeg-devel and if the community agrees to fund them, also with > > +SPI through stefano before starting with anything. >=20 > My take on this: >=20 > For other refund expenses or sponsorships, it is recommended to > discuss them beforehand on ffmpeg-devel. If there is a community > agreement on their approval, the current FFmpeg liaison will followup > to get an approval on the SPI side. >=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 >=20 > > +additional paperwork, but it is not prohibitied. >=20 > prohibited >=20 > > + >=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. >=20 > This part is a useful resume of the past internal discussions, but at > the same time we never really went down to this road, so I'm not sure > moving this to the repo would be helpful from the operational point of > view. It's probably useful to clarify the current status quo with the > other developers though. >=20 > About the placement of the text, given that this is an internal memo > intended for developers probably it's better to keep it in the ffmpeg > repo rather than on the web one (as it was proposed in another reply). ill post a V2 with your suggested changes it doesnt really matter where it is, important is that it is somewhere thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Democracy is the form of government in which you can choose your dictator --Jy7fHMWyH2pKEqn7 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZSmNdgAKCRBhHseHBAsP q4fXAJ9bI2EW2QvGKDtxbqEP90U/Q9Qf/QCcDpj57T88YStkDIjagTd/I5If6kE= =KOMd -----END PGP SIGNATURE----- --Jy7fHMWyH2pKEqn7-- --===============3692507240793119955== 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". --===============3692507240793119955==--