* [FFmpeg-devel] [PATCH] web: Add spi.txt
@ 2024-02-27 19:01 Michael Niedermayer
2024-03-03 16:36 ` Stefano Sabatini
0 siblings, 1 reply; 5+ messages in thread
From: Michael Niedermayer @ 2024-02-27 19:01 UTC (permalink / raw)
To: FFmpeg development discussions and patches
This explains how to request refunds and what can be funded by SPI
Co-Author: Stefano Sabatini <stefasab@gmail.com>
---
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 @@
+<p>
+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:
+<a href="https://www.spi-inc.org/">www.spi-inc.org</a>
+</p>
+
+<p>
+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:
+<a href="https://www.spi-inc.org/projects/ffmpeg/">www.spi-inc.org/projects/ffmpeg/</a>
+</p>
+
+<br>
+
+<h4>How to request refunds from SPI:</h4>
+<p>
+Send a mail to ffmpeg-devel with the [REFUND-REQUEST] tag and a short
+description of the refund topic in the subject.
+</p>
+
+<p>
+In the mail, you also need to provide the amount to be refunded, with
+a short description of how the money was spent.
+</p>
+
+<p>
+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:
+<a href="https://www.spi-inc.org/treasurer/reimbursement-form/">www.spi-inc.org/treasurer/reimbursement-form</a>
+</p>
+
+<br>
+<h4>What can be payed by SPI:</h4>
+<p>
+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).
+</p>
+
+<p>
+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.
+</p>
+
+
+<br>
+<h4>Funding active development by SPI:</h4>
+<p>
+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.)
+</p>
+<p>
+Paying for development *does* require substantial
+additional paperwork, but it is not prohibited.
+</p>
+<p>
+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;
+are they really a contractor and not a employee).
+</p>
+<p>
+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.
+</p>
+<p>
+Unfortunately, there's no one-size-fits all when dealing with
+contractors, especially without knowing the contributor's country.
+</p>
+<p>
+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
+</p>
+<p>
+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.
+</p>
+
+<br><br>
+
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 @@
<li><a href="developer.html#Contributing">Contribute</a></li>
<li><a href="http://fate.ffmpeg.org">FATE</a></li>
<li><a href="http://coverage.ffmpeg.org">Code Coverage</a></li>
+ <li><a href="spi.html">Funding through SPI</a></li>
</ul>
</li>
<li><a href="#">More</a>
--
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".
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [FFmpeg-devel] [PATCH] web: Add spi.txt
2024-02-27 19:01 [FFmpeg-devel] [PATCH] web: Add spi.txt Michael Niedermayer
@ 2024-03-03 16:36 ` Stefano Sabatini
2024-03-03 21:08 ` Michael Niedermayer
0 siblings, 1 reply; 5+ messages in thread
From: Stefano Sabatini @ 2024-03-03 16:36 UTC (permalink / raw)
To: FFmpeg development discussions and patches
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 <stefasab@gmail.com>
> ---
> 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 @@
> +<p>
> +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:
> +<a href="https://www.spi-inc.org/">www.spi-inc.org</a>
> +</p>
> +
> +<p>
> +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:
> +<a href="https://www.spi-inc.org/projects/ffmpeg/">www.spi-inc.org/projects/ffmpeg/</a>
> +</p>
> +
> +<br>
> +
> +<h4>How to request refunds from SPI:</h4>
> +<p>
> +Send a mail to ffmpeg-devel with the [REFUND-REQUEST] tag and a short
> +description of the refund topic in the subject.
> +</p>
> +
> +<p>
> +In the mail, you also need to provide the amount to be refunded, with
> +a short description of how the money was spent.
> +</p>
> +
> +<p>
> +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:
> +<a href="https://www.spi-inc.org/treasurer/reimbursement-form/">www.spi-inc.org/treasurer/reimbursement-form</a>
> +</p>
> +
> +<br>
> +<h4>What can be payed by SPI:</h4>
> +<p>
> +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?
> +</p>
> +
> +<p>
> +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.
> +</p>
> +
> +
> +<br>
> +<h4>Funding active development by SPI:</h4>
> +<p>
> +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.)
> +</p>
> +<p>
> +Paying for development *does* require substantial
> +additional paperwork, but it is not prohibited.
> +</p>
> +<p>
> +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).
> +</p>
> +<p>
> +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.
> +</p>
> +<p>
> +Unfortunately, there's no one-size-fits all when dealing with
one-size-fits-all ?
> +contractors, especially without knowing the contributor's country.
> +</p>
> +<p>
> +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 "."
> +</p>
> +<p>
> +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.
> +</p>
> +
> +<br><br>
> +
> 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 @@
> <li><a href="developer.html#Contributing">Contribute</a></li>
> <li><a href="http://fate.ffmpeg.org">FATE</a></li>
> <li><a href="http://coverage.ffmpeg.org">Code Coverage</a></li>
> + <li><a href="spi.html">Funding through SPI</a></li>
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".
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [FFmpeg-devel] [PATCH] web: Add spi.txt
2024-03-03 16:36 ` Stefano Sabatini
@ 2024-03-03 21:08 ` Michael Niedermayer
2024-03-03 21:29 ` Lynne
0 siblings, 1 reply; 5+ messages in thread
From: Michael Niedermayer @ 2024-03-03 21:08 UTC (permalink / raw)
To: FFmpeg development discussions and patches
[-- Attachment #1.1: Type: text/plain, Size: 6674 bytes --]
On Sun, Mar 03, 2024 at 05:36:41PM +0100, Stefano Sabatini wrote:
> 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 <stefasab@gmail.com>
> > ---
> > 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 @@
> > +<p>
> > +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:
> > +<a href="https://www.spi-inc.org/">www.spi-inc.org</a>
> > +</p>
> > +
> > +<p>
> > +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:
> > +<a href="https://www.spi-inc.org/projects/ffmpeg/">www.spi-inc.org/projects/ffmpeg/</a>
> > +</p>
> > +
> > +<br>
> > +
> > +<h4>How to request refunds from SPI:</h4>
> > +<p>
> > +Send a mail to ffmpeg-devel with the [REFUND-REQUEST] tag and a short
> > +description of the refund topic in the subject.
> > +</p>
> > +
> > +<p>
> > +In the mail, you also need to provide the amount to be refunded, with
> > +a short description of how the money was spent.
> > +</p>
> > +
> > +<p>
> > +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:
> > +<a href="https://www.spi-inc.org/treasurer/reimbursement-form/">www.spi-inc.org/treasurer/reimbursement-form</a>
> > +</p>
> > +
> > +<br>
> > +<h4>What can be payed by SPI:</h4>
> > +<p>
>
> > +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?
>
> > +</p>
> > +
> > +<p>
> > +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.
> > +</p>
> > +
> > +
> > +<br>
> > +<h4>Funding active development by SPI:</h4>
> > +<p>
> > +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.)
> > +</p>
> > +<p>
> > +Paying for development *does* require substantial
> > +additional paperwork, but it is not prohibited.
> > +</p>
> > +<p>
> > +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).
> > +</p>
> > +<p>
> > +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.
> > +</p>
> > +<p>
> > +Unfortunately, there's no one-size-fits all when dealing with
>
> one-size-fits-all ?
>
> > +contractors, especially without knowing the contributor's country.
> > +</p>
>
> > +<p>
> > +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 "."
>
> > +</p>
> > +<p>
> > +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.
>
> > +</p>
> > +
> > +<br><br>
> > +
> > 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 @@
> > <li><a href="developer.html#Contributing">Contribute</a></li>
> > <li><a href="http://fate.ffmpeg.org">FATE</a></li>
> > <li><a href="http://coverage.ffmpeg.org">Code Coverage</a></li>
> > + <li><a href="spi.html">Funding through SPI</a></li>
>
> Still looks good to me with the minor adjustments, thanks.
will apply
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The misfortune of the wise is better than the prosperity of the fool.
-- Epicurus
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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".
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [FFmpeg-devel] [PATCH] web: Add spi.txt
2024-03-03 21:08 ` Michael Niedermayer
@ 2024-03-03 21:29 ` Lynne
2024-03-03 21:34 ` Michael Niedermayer
0 siblings, 1 reply; 5+ messages in thread
From: Lynne @ 2024-03-03 21:29 UTC (permalink / raw)
To: FFmpeg development discussions and patches
Mar 3, 2024, 22:08 by michael@niedermayer.cc:
> On Sun, Mar 03, 2024 at 05:36:41PM +0100, Stefano Sabatini wrote:
>
>> 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 <stefasab@gmail.com>
>> > ---
>> > 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 @@
>> > +<p>
>> > +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:
>> > +<a href="https://www.spi-inc.org/">www.spi-inc.org</a>
>> > +</p>
>> > +
>> > +<p>
>> > +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:
>> > +<a href="https://www.spi-inc.org/projects/ffmpeg/">www.spi-inc.org/projects/ffmpeg/</a>
>> > +</p>
>> > +
>> > +<br>
>> > +
>> > +<h4>How to request refunds from SPI:</h4>
>> > +<p>
>> > +Send a mail to ffmpeg-devel with the [REFUND-REQUEST] tag and a short
>> > +description of the refund topic in the subject.
>> > +</p>
>> > +
>> > +<p>
>> > +In the mail, you also need to provide the amount to be refunded, with
>> > +a short description of how the money was spent.
>> > +</p>
>> > +
>> > +<p>
>> > +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:
>> > +<a href="https://www.spi-inc.org/treasurer/reimbursement-form/">www.spi-inc.org/treasurer/reimbursement-form</a>
>> > +</p>
>> > +
>> > +<br>
>> > +<h4>What can be payed by SPI:</h4>
>> > +<p>
>>
>> > +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?
>>
>> > +</p>
>> > +
>> > +<p>
>> > +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.
>> > +</p>
>> > +
>> > +
>> > +<br>
>> > +<h4>Funding active development by SPI:</h4>
>> > +<p>
>> > +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.)
>> > +</p>
>> > +<p>
>> > +Paying for development *does* require substantial
>> > +additional paperwork, but it is not prohibited.
>> > +</p>
>> > +<p>
>> > +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).
>> > +</p>
>> > +<p>
>> > +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.
>> > +</p>
>> > +<p>
>> > +Unfortunately, there's no one-size-fits all when dealing with
>>
>> one-size-fits-all ?
>>
>> > +contractors, especially without knowing the contributor's country.
>> > +</p>
>>
>> > +<p>
>> > +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 "."
>>
>> > +</p>
>> > +<p>
>> > +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.
>>
>> > +</p>
>> > +
>> > +<br><br>
>> > +
>> > 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 @@
>> > <li><a href="developer.html#Contributing">Contribute</a></li>
>> > <li><a href="http://fate.ffmpeg.org">FATE</a></li>
>> > <li><a href="http://coverage.ffmpeg.org">Code Coverage</a></li>
>> > + <li><a href="spi.html">Funding through SPI</a></li>
>>
>> Still looks good to me with the minor adjustments, thanks.
>>
>
> will apply
>
I think stuff like this should go to the website, not the git repo.
_______________________________________________
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".
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [FFmpeg-devel] [PATCH] web: Add spi.txt
2024-03-03 21:29 ` Lynne
@ 2024-03-03 21:34 ` Michael Niedermayer
0 siblings, 0 replies; 5+ messages in thread
From: Michael Niedermayer @ 2024-03-03 21:34 UTC (permalink / raw)
To: FFmpeg development discussions and patches
[-- Attachment #1.1: Type: text/plain, Size: 7518 bytes --]
On Sun, Mar 03, 2024 at 10:29:59PM +0100, Lynne wrote:
> Mar 3, 2024, 22:08 by michael@niedermayer.cc:
>
> > On Sun, Mar 03, 2024 at 05:36:41PM +0100, Stefano Sabatini wrote:
> >
> >> 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 <stefasab@gmail.com>
> >> > ---
> >> > 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 @@
> >> > +<p>
> >> > +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:
> >> > +<a href="https://www.spi-inc.org/">www.spi-inc.org</a>
> >> > +</p>
> >> > +
> >> > +<p>
> >> > +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:
> >> > +<a href="https://www.spi-inc.org/projects/ffmpeg/">www.spi-inc.org/projects/ffmpeg/</a>
> >> > +</p>
> >> > +
> >> > +<br>
> >> > +
> >> > +<h4>How to request refunds from SPI:</h4>
> >> > +<p>
> >> > +Send a mail to ffmpeg-devel with the [REFUND-REQUEST] tag and a short
> >> > +description of the refund topic in the subject.
> >> > +</p>
> >> > +
> >> > +<p>
> >> > +In the mail, you also need to provide the amount to be refunded, with
> >> > +a short description of how the money was spent.
> >> > +</p>
> >> > +
> >> > +<p>
> >> > +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:
> >> > +<a href="https://www.spi-inc.org/treasurer/reimbursement-form/">www.spi-inc.org/treasurer/reimbursement-form</a>
> >> > +</p>
> >> > +
> >> > +<br>
> >> > +<h4>What can be payed by SPI:</h4>
> >> > +<p>
> >>
> >> > +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?
> >>
> >> > +</p>
> >> > +
> >> > +<p>
> >> > +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.
> >> > +</p>
> >> > +
> >> > +
> >> > +<br>
> >> > +<h4>Funding active development by SPI:</h4>
> >> > +<p>
> >> > +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.)
> >> > +</p>
> >> > +<p>
> >> > +Paying for development *does* require substantial
> >> > +additional paperwork, but it is not prohibited.
> >> > +</p>
> >> > +<p>
> >> > +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).
> >> > +</p>
> >> > +<p>
> >> > +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.
> >> > +</p>
> >> > +<p>
> >> > +Unfortunately, there's no one-size-fits all when dealing with
> >>
> >> one-size-fits-all ?
> >>
> >> > +contractors, especially without knowing the contributor's country.
> >> > +</p>
> >>
> >> > +<p>
> >> > +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 "."
> >>
> >> > +</p>
> >> > +<p>
> >> > +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.
> >>
> >> > +</p>
> >> > +
> >> > +<br><br>
> >> > +
> >> > 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 @@
> >> > <li><a href="developer.html#Contributing">Contribute</a></li>
> >> > <li><a href="http://fate.ffmpeg.org">FATE</a></li>
> >> > <li><a href="http://coverage.ffmpeg.org">Code Coverage</a></li>
> >> > + <li><a href="spi.html">Funding through SPI</a></li>
> >>
> >> Still looks good to me with the minor adjustments, thanks.
> >>
> >
> > will apply
> >
>
> I think stuff like this should go to the website, not the git repo.
its there now:
https://www.ffmpeg.org/spi.html
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The bravest are surely those who have the clearest vision
of what is before them, glory and danger alike, and yet
notwithstanding go out to meet it. -- Thucydides
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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".
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2024-03-03 21:34 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-02-27 19:01 [FFmpeg-devel] [PATCH] web: Add spi.txt Michael Niedermayer
2024-03-03 16:36 ` Stefano Sabatini
2024-03-03 21:08 ` Michael Niedermayer
2024-03-03 21:29 ` Lynne
2024-03-03 21:34 ` Michael Niedermayer
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