From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: [FFmpeg-devel] [PATCH 3/3] doc: add spi.txt Date: Wed, 11 Oct 2023 20:10:15 +0200 Message-ID: <20231011181015.6433-3-michael@niedermayer.cc> (raw) In-Reply-To: <20231011181015.6433-1-michael@niedermayer.cc> 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".
next prev parent reply other threads:[~2023-10-11 18:10 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-11 18:10 [FFmpeg-devel] [PATCH 1/3] avformat/tmv: Check video chunk size Michael Niedermayer 2023-10-11 18:10 ` [FFmpeg-devel] [PATCH 2/3] avformat/jacosubdec: clarify code Michael Niedermayer 2024-03-26 0:17 ` Michael Niedermayer 2023-10-11 18:10 ` Michael Niedermayer [this message] 2023-10-12 2:53 ` [FFmpeg-devel] [PATCH 3/3] doc: add spi.txt Steven Liu 2023-10-12 8:03 ` Andreas Rheinhardt 2023-10-12 17:37 ` Michael Niedermayer 2023-10-12 17:41 ` Lynne 2023-10-12 22:53 ` Stefano Sabatini 2023-10-13 18:33 ` Michael Niedermayer 2023-10-15 22:54 ` [FFmpeg-devel] [PATCH 1/3] avformat/tmv: Check video chunk size Michael Niedermayer
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20231011181015.6433-3-michael@niedermayer.cc \ --to=michael@niedermayer.cc \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git