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 BA70049B35 for ; Sun, 3 Mar 2024 16:36:54 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id E39ED68D39A; Sun, 3 Mar 2024 18:36:51 +0200 (EET) Received: from mail-lj1-f177.google.com (mail-lj1-f177.google.com [209.85.208.177]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 28FEC68CFFE for ; Sun, 3 Mar 2024 18:36:46 +0200 (EET) Received: by mail-lj1-f177.google.com with SMTP id 38308e7fff4ca-2d275e63590so50977871fa.2 for ; Sun, 03 Mar 2024 08:36:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709483804; x=1710088604; darn=ffmpeg.org; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date:from:to:cc:subject :date:message-id:reply-to; bh=Vyy/TSImm5EDgEp3MI5g1yUU3fdJPCWJ++vmVdwFIxY=; b=UV8otf1WBu8vgihxqOC5HFAky+uZ1xbAdEXjbMmrMqOt/hcKNQxBIwF6ugOMhHgG6g deiSbydWyxln3qMJ+FBi2vSkwzTnzaWlmzVH6D6bzcI+atf6W0a8Mb82MiFIjjUwPt3J n8TpTyNFT/fRsXZPlBCgjhWnB88FqkwG9+/0dIp7lWGs38vufYUuyqZNpgE+vSHPVu50 fyUxSYYeUl0TdLAGvjq9BOrGEDYFIQQfBv5UsMSNmlrIyZNkcYO7KVf2D3xxhnZqjpfj T+TEap7SHIK/EOJLs4LsNEedblK1hpEQSRd+lO9cwmAOp9Jq62jzPIwbnVnlb7hP2jo5 CUlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709483804; x=1710088604; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Vyy/TSImm5EDgEp3MI5g1yUU3fdJPCWJ++vmVdwFIxY=; b=FZi1GdQth4RR+6fWzxtmH+TOWVbEOeiF6NzkSNRqDhe6GEagIynJVSGqs2jPasJCwU WYpauHbdkBpv/u4zRpe5qFMVt393jXACnUurfQQVR3OehUQOiO5A7fR1SX+4B5pu5CBw uPbHCZGZNuUDslz4N1DwKkQcEEfUoeb/HPl2PttJsswt2pwDLeERKTK9VAf5PZf2AEYK BE2YxRuSFxcO1tcLvbxvG4N0mS5w+xrMAEQybIUd2QyHFHNU3X2gntfh1PDfU3lVRNHk b1eEKT+iXMRtDPQCRbSP93EH+3mZRR8wJRg52jiHupIE4o1BtzoCJtQkeW+xKliCLVkx M4sw== X-Gm-Message-State: AOJu0YxjXyGjJ0Z5DpqxuZlaajIqfZdvTLuAkFH6wDyLc/VzMsgdgq0E OL96DnjKH32MjkRWoZ9n3StjNmEFB/Q7wlSXZIUKCzXP4r+6cqKnZFaXSA+c X-Google-Smtp-Source: AGHT+IGEwNpyZ3cdV8HMDQl6ACnaSwjj99YGnsPPfxpXnxJIgBPFEOgI60QdMblGORyRvvKq0jxI1Q== X-Received: by 2002:ac2:4c49:0:b0:513:3f2e:aaa8 with SMTP id o9-20020ac24c49000000b005133f2eaaa8mr2585461lfk.36.1709483803917; Sun, 03 Mar 2024 08:36:43 -0800 (PST) Received: from mariano ([188.210.239.74]) by smtp.gmail.com with ESMTPSA id lm7-20020a170906980700b00a449fdfe27bsm2493773ejb.170.2024.03.03.08.36.43 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 03 Mar 2024 08:36:43 -0800 (PST) Received: by mariano (Postfix, from userid 1000) id E96B6BFCDC; Sun, 3 Mar 2024 17:36:41 +0100 (CET) Date: Sun, 3 Mar 2024 17:36:41 +0100 From: Stefano Sabatini To: FFmpeg development discussions and patches Message-ID: Mail-Followup-To: FFmpeg development discussions and patches References: <20240227190126.1725-1-michael@niedermayer.cc> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20240227190126.1725-1-michael@niedermayer.cc> User-Agent: Mutt/2.1.4 (2021-12-11) Subject: Re: [FFmpeg-devel] [PATCH] web: 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: On date Tuesday 2024-02-27 20:01:26 +0100, Michael Niedermayer wrote: > This explains how to request refunds and what can be funded by SPI > > Co-Author: Stefano Sabatini > --- > Makefile | 2 +- > src/spi | 98 ++++++++++++++++++++++++++++++++++++++++++++++ > src/spi_js | 0 > src/spi_title | 1 + > src/template_head2 | 1 + > 5 files changed, 101 insertions(+), 1 deletion(-) > create mode 100644 src/spi > create mode 100644 src/spi_js > create mode 100644 src/spi_title > > diff --git a/Makefile b/Makefile > index 0686e44..dd681e4 100644 > --- a/Makefile > +++ b/Makefile > @@ -1,7 +1,7 @@ > # ffmpeg.org HTML generation from source files > > SRCS = about bugreports consulting contact donations documentation download \ > - olddownload index legal shame security archive > + olddownload index legal shame security spi archive > > HTML_TARGETS = $(addsuffix .html,$(addprefix htdocs/,$(SRCS))) > > diff --git a/src/spi b/src/spi > new file mode 100644 > index 0000000..8fffc7f > --- /dev/null > +++ b/src/spi > @@ -0,0 +1,98 @@ > +

> +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: > +www.spi-inc.org > +

> + > +

> +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: > +www.spi-inc.org/projects/ffmpeg/ > +

> + > +
> + > +

How to request refunds from SPI:

> +

> +Send a mail to ffmpeg-devel with the [REFUND-REQUEST] tag and a short > +description of the refund topic in the subject. > +

> + > +

> +In the mail, you also need to provide the amount to be refunded, with > +a short description of how the money was spent. > +

> + > +

> +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: > +www.spi-inc.org/treasurer/reimbursement-form > +

> + > +
> +

What can be payed by SPI:

> +

> +FFmpeg money collected at SPI can be used for any purpose which is in line with > +501(c)3 nonprofit rules, and within our mission (Free & OSS software). Free & Open Source software? > +

> + > +

> +In practice we frequently payed for travel and hardware. > +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. > +

> + > + > +
> +

Funding 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 prohibited. > +

> +

> +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 about the potential > +contractors(e.g. are they a US person or not, as with GSoC mentor payments; contractors_( > +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 one-size-fits-all ? > +contractors, especially without knowing the contributor's country. > +

> +

> +SPI does have some contract templates which depends on the contractors > +country. In case of US, Australia, France and a couple others > +countries, SPI can easily provide them, otherwise SPI would need to > +ask their attorney to draft one, which would take some time add missing "." > +

> +

> +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 retains ownership rights. Probably it's good to expand MSA (Master Service Agreements) and CSA (Continued Service Agreements) in their first occurrence. > +

> + > +

> + > diff --git a/src/spi_js b/src/spi_js > new file mode 100644 > index 0000000..e69de29 > diff --git a/src/spi_title b/src/spi_title > new file mode 100644 > index 0000000..389532a > --- /dev/null > +++ b/src/spi_title > @@ -0,0 +1 @@ > +SPI > diff --git a/src/template_head2 b/src/template_head2 > index 7ba634b..79d2f51 100644 > --- a/src/template_head2 > +++ b/src/template_head2 > @@ -37,6 +37,7 @@ >
  • Contribute
    • >
  • FATE
    • >
  • Code Coverage
    • > +
  • Funding through SPI
    • Still looks good to me with the minor adjustments, thanks. _______________________________________________ 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".