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 4D6704757A for ; Thu, 12 Oct 2023 17:42:08 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id DA98168C8D8; Thu, 12 Oct 2023 20:42:05 +0300 (EEST) Received: from w4.tutanota.de (w4.tutanota.de [81.3.6.165]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 026B368C60B for ; Thu, 12 Oct 2023 20:41:59 +0300 (EEST) Received: from tutadb.w10.tutanota.de (unknown [192.168.1.10]) by w4.tutanota.de (Postfix) with ESMTP id 51576106019B for ; Thu, 12 Oct 2023 17:41:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1697132517; s=s1; d=lynne.ee; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Content-Transfer-Encoding:Cc:Date:Date:In-Reply-To:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:References:Sender; bh=DOV5vTd1yYUGbShxZXKE53FjvbON2Z/4DmwrNL8uGa4=; b=AlEWGsSz8eSVrqo7mEmpvltXVo1C2w52p6gswBBDmq7Py6Jr1WMB5JyfiXnrERj6 GOUpQJAPPfSy9vg90XKmI6ULDQwRnxxfX8BunQ+OIR2mOG1nG1PfylSuUCERPrNxopC xxMg7FqoJWkdp7ZxHk0ThJ1xelOvhtR9R6TsokyG9OjT1C8HvRDHb4tAMNWP3EPJF0d Le1+8U0I/cKxWt7FIZ2XcUVoqy40KZxT5dZB9OyvmO3HDeWS8suGIxG0VtIb6slBxw6 zkdye8jYNVof6DOtjtmNWIS0Usgss9Vm9ckfVuPU8m6kein8etI/HaiN6AKg2wHgbCe +anlpqNrSA== Date: Thu, 12 Oct 2023 19:41:57 +0200 (CEST) From: Lynne To: FFmpeg development discussions and patches Message-ID: In-Reply-To: <20231012173739.GN3543730@pb2> References: <20231011181015.6433-1-michael@niedermayer.cc> <20231011181015.6433-3-michael@niedermayer.cc> <20231012173739.GN3543730@pb2> MIME-Version: 1.0 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Oct 12, 2023, 19:37 by michael@niedermayer.cc: > 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 >> > >> > 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 >> >> > +For other things, it is recommanded to disscuss them beforehand >> ^ ^ >> e >> >> > +on ffmpeg-devel and if the community agrees to fund them, also with >> > +SPI through stefano before starting with anything. >> ^ >> S >> >> > + >> > + >> > +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. >> ^ >> >> > + >> > +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 contractors. >> > +As already mentioned, without knowing the contributor's country >> > + >> > +SPI does have templates, but they depend on the contractors country. If 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 would >> > +take some time >> > + >> > +Also, SPI has two models, MSA (which transfers ownership) and CSA (which >> > +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 >> >> This should explain what the abbreviations stand for. >> > > I believe MSA stands for Master service agreement. I do not know what CSA stands for > > all other things fixed > I think this belongs on the website, not in the source code. _______________________________________________ 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".