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 3093F46227 for ; Wed, 11 Oct 2023 18:10:48 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 4666068C9B4; Wed, 11 Oct 2023 21:10:27 +0300 (EEST) 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 B9BA468C7F0 for ; Wed, 11 Oct 2023 21:10:19 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id F044F240008 for ; Wed, 11 Oct 2023 18:10:18 +0000 (UTC) From: Michael Niedermayer To: FFmpeg development discussions and patches Date: Wed, 11 Oct 2023 20:10:15 +0200 Message-Id: <20231011181015.6433-3-michael@niedermayer.cc> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20231011181015.6433-1-michael@niedermayer.cc> References: <20231011181015.6433-1-michael@niedermayer.cc> X-GND-Sasl: michael@niedermayer.cc Subject: [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 MIME-Version: 1.0 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: 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. +For other things, it is recommanded to disscuss them beforehand +on ffmpeg-devel and if the community agrees to fund them, also with +SPI through stefano before starting with anything. + + +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. -- 2.17.1 _______________________________________________ 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".