Skip to content

Commit e5741d0

Browse files
Document how grants and fees work with LF (#179)
Co-authored-by: Chris Holdgraf <choldgraf@gmail.com> Co-authored-by: Jason Grout <jasongrout@users.noreply.github.com>
1 parent 3b83b4d commit e5741d0

2 files changed

Lines changed: 59 additions & 0 deletions

File tree

docs/finances.md

Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
# Finances and grants
2+
3+
Project Jupyter's finances run through [The Linux Foundation](https://www.linuxfoundation.org/) (LF) and [LF Charities](https://lf-charities.org/).
4+
This page explains how grants and other funds flow through the LF structures that hold Jupyter's money. It documents where the money can land, how much overhead is taken out, and who controls how it is spent.
5+
6+
## How money is held
7+
8+
Two LF entities can receive and hold Jupyter funds:
9+
10+
- **[The Jupyter Foundation](https://jupyterfoundation.org/)** is a directed fund of [The Linux Foundation 501(c)(6)](https://projects.propublica.org/nonprofits/organizations/460503801). This is the main pool of Jupyter money and is governed by the Jupyter Foundation's governing board.
11+
- **[LF Charities Inc](https://lf-charities.org/)** hosts Project Jupyter as an open-source project and is a [501(c)(3) nonprofit](https://projects.propublica.org/nonprofits/organizations/841730246). Project Jupyter is governed by the Jupyter Executive Council, a community-elected group that also sits on the Jupyter Foundation governing board.[^509a3]
12+
13+
[^509a3]: LF Charities is a 509(a)(3) "supporting organization" for the LF 501(c)(6). That legal relationship is what lets Project Jupyter receive funds in LF Charities and later move them into the Jupyter Foundation to save on G&A overhead.
14+
15+
:::{warning} Open question: grants raised by someone other than the EC
16+
The Executive Council controls the 501(c)(3), so it directs how those funds are spent.
17+
We have not settled what happens when someone else, such as a subproject or individual leader, raises a grant and expects to direct those funds themselves.
18+
We need a clear policy for who decides how that money is spent.
19+
:::
20+
21+
## G&A fees (aka indirect fees)
22+
23+
The LF charges a general and administrative (G&A) fee on income to cover the administration cost. The rate is **9%** on the first 1 million USD of income in a year and **6%** on income over that. The fee is assessed when the income lands in its _final destination fund_, not when it first arrives.
24+
25+
:::{note} Example
26+
Money is received into LF Charities and then _transferred to the Jupyter Foundation_. It is charged the G&A fee when it lands in the Jupyter Foundation (its final destination). If the Jupyter Foundation has already received `$1 million USD` in income in the year, the funds moved in from LF Charities are charged the lower **6%** overhead rate.
27+
:::
28+
29+
:::{note} High-cost grants may incur a higher G&A fee
30+
Some grants require an exceptional amount of reporting or compliance work.
31+
For example, grants or contracts from the US federal government.
32+
For these, LF may charge an additional G&A fee to cover the extra administration costs.
33+
:::
34+
35+
## Restricted funds and how transfers are tracked
36+
37+
There is a tradeoff between moving money into the Jupyter Foundation for the lower overhead and keeping it separately controlled in LF Charities.
38+
39+
When LF Charities transfers money into the Jupyter Foundation, it goes in without conditions.
40+
This is deliberate: attaching conditions would make the money "restricted funding" under IRS rules and trigger extra reporting requirements. The cost of avoiding that is that the money becomes part of the Jupyter Foundation's single pot rather than a separately tracked bucket.
41+
42+
The Jupyter Foundation's governing board then allocates that money. It can steer funds toward the priorities the Executive Council has laid out, so the EC's intent can still be honored in practice. What it cannot do is make an explicit written commitment tied to the transfer, since that would be the kind of condition that creates restricted funding.
43+
44+
If keeping funds under the Executive Council's governance matters more than the lower overhead, the money can instead stay in LF Charities. However, until the yearly income there for Jupyter passes 1 million USD (regardless of any funds that are in the 501(c)(6)), the overhead rate will be the higher 9% rate.
45+
46+
## Grants on behalf of a subproject
47+
48+
A grant "for Jupyter" can be received two ways:
49+
50+
- Into one of the LF entities above, so the money sits inside Jupyter's own structures.
51+
- By an outside organization (for example, a university) that does the work and administers the grant directly.
52+
53+
:::{warning} Open question: approval for grant work on Jupyter technology
54+
We need a process for approving grant work that involves Jupyter technology.
55+
A grant commits people to a particular vision and execution plan, and we want to be sure the project is aligned with both before anyone signs on.
56+
Otherwise others can get legally committed to work that Jupyter isn't ready to accept.
57+
:::
58+

docs/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,7 @@ EC members allocate time during our weekly scheduled meetings to review new issu
3030
:titlesonly:
3131
operations
3232
accounts
33+
finances
3334
meeting_notes/index
3435
office_hours/index
3536
reports/communitybuilding/readme

0 commit comments

Comments
 (0)