|
| 1 | +# How Matplotlib will acknowledge financial support |
| 2 | + |
| 3 | +There will be two different ways to acknowledge financial and in-kind support: |
| 4 | +one to recognize significant active support, and another one to recognize |
| 5 | +support received in the past and smaller amounts of support. |
| 6 | + |
| 7 | +Entities who fall under "significant active supporter" we'll call Sponsor. The |
| 8 | +minimum level of support given to Matplotlib to be considered a Sponsor are: |
| 9 | + |
| 10 | +- \$30,000/yr for unrestricted financial contributions (e.g., donations) |
| 11 | + |
| 12 | +- \$60,000/yr for financial contributions for a particular purpose |
| 13 | + (e.g., grants) |
| 14 | + |
| 15 | +- \$100,000/yr for in-kind contributions (e.g., time for employees to |
| 16 | + contribute) |
| 17 | + |
| 18 | +We define support being active as: |
| 19 | + |
| 20 | +- for a one-off donation: it was received within the previous 12 |
| 21 | + months, |
| 22 | + |
| 23 | +- for recurring or financial or in-kind contributions: they should be |
| 24 | + ongoing. |
| 25 | + |
| 26 | +After support moves from "active" to "inactive" status, the acknowledgement |
| 27 | +will be left in its place for at least another 6 months. If appropriate, the |
| 28 | +funding team can discuss opportunities for renewal with the sponsor. After |
| 29 | +those 6 months, acknowledgement may be moved to the historical overview. The |
| 30 | +exact timing of this move is at the discretion of the funding team, because |
| 31 | +there may be reasons to keep it in the more prominent place for longer. |
| 32 | + |
| 33 | +The rationale for the above funding levels is that unrestricted financial |
| 34 | +contributions are typically the most valuable for the project, and the hardest |
| 35 | +to obtain. The opposite is true for in-kind contributions. The dollar value of |
| 36 | +the levels also reflect that Matplotlib's needs have grown to the point where |
| 37 | +we need multiple paid developers in order to effectively support our user base |
| 38 | +and continue to move the project forward. Financial support at or above these |
| 39 | +levels is needed to be able to make a significant difference. |
| 40 | + |
| 41 | +Sponsors will get acknowledged through: |
| 42 | + |
| 43 | +- a small logo displayed on the front page of the Matplotlib website |
| 44 | + |
| 45 | +- prominent logo placement on <https://matplotlib.org/about/> |
| 46 | + |
| 47 | +- logos displayed in talks about Matplotlib by maintainers |
| 48 | + |
| 49 | +- announcements of the sponsorship on the Matplotlib mailing list and the |
| 50 | + matplotlib Twitter account |
| 51 | + |
| 52 | +In addition to Sponsors, we already have the concept of Institutional Partner |
| 53 | +(defined in Matplotlib's [governance |
| 54 | +document](https://github.com/matplotlib/governance/goverance.md)), for entities |
| 55 | +who employ a Matplotlib maintainer and let them work on Matplotlib as part of |
| 56 | +their official duties. Institutional Partners get the same benefits as |
| 57 | +Sponsors, in addition to what is specified in the Matplotlib governance |
| 58 | +document. |
| 59 | + |
| 60 | +Finally, a page on the website (<https://matplotlib.org/goverance/funding/>, |
| 61 | +linked from the About page) will acknowledge all current and previous sponsors, |
| 62 | +partners, and any other entities and individuals who provided \$5,000 or more |
| 63 | +of financial or in-kind support. This page will include relevant details of |
| 64 | +support (dates, amounts, names, and purpose); no logos will be used on this |
| 65 | +page. The rationale for the \$5,000 minimum level is to keep the amount of work |
| 66 | +maintaining the page reasonable; the level is the equivalent of, e.g., one GSoC |
| 67 | +or a person-week's worth of engineering time in a Western country, which seems |
| 68 | +like a reasonable lower limit. |
0 commit comments