# Open Collective for Jupyter

**URL:** <https://discourse.jupyter.org/t/open-collective-for-jupyter/3352>\
**Category:** General\
**Created:** [February 17, 2020, 8:01pm UTC](https://discourse.jupyter.org/t/open-collective-for-jupyter/3352 "2020-02-17T20:01:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![saulshanabrook](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/saulshanabrook/32/159_2.png) [@saulshanabrook](https://discourse.jupyter.org/u/saulshanabrook)\
**Post date:** [February 17, 2020, 8:01pm UTC](https://discourse.jupyter.org/t/open-collective-for-jupyter/3352/1 "2020-02-17T20:01:48Z")

</div>

I am curious if we could start an [Open Collective](https://opencollective.com/) for Project Jupyter. It gives a way for people to start funding the projects in a grass roots manner that is a little bit more user friendly than contributing directly to NumFocus. They [recently announced](https://blog.opencollective.com/double-the-love/) an integration with Github Sponsors.

Spyder has had luck with [their Open Collective](https://opencollective.com/spyder), raising enough money to hire some junior devs to work on the project.

We could either use NumFocus as the fiscal sponsor or if that is too much hassle then just the default [“Open Source Collective”](https://opencollective.com/opensource) (which takes a 5% cut).

Even if we don’t know exactly how the money would get spent currently, it wouldn’t hurt to put it out there and see what the reception is like!

---

<div class="post-metadata">

**Author:** ![goanpeca](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/goanpeca/32/1579_2.png) [@goanpeca](https://discourse.jupyter.org/u/goanpeca)\
**Post date:** [February 17, 2020, 8:13pm UTC](https://discourse.jupyter.org/t/open-collective-for-jupyter/3352/2 "2020-02-17T20:13:41Z")

</div>

I definitely back this idea! ( **Spyder** core dev here!)

The Spyder team has always seen **Jupyter** as a huge and very influential partner!

A couple of years ago the team was having a hard time with funding and finding devs that could work on the project. As a desperate last effort we launched [https://opencollective.com/spyder](https://opencollective.com/spyder) to see if there was interest in the project, and with the support from different people the project we could finally hire some junior devs that kept the project alive (as @saulshanabrook pointed out),

We are in much better shape now, but we had many dark times when we were about to loose hope!.

This is a screenshot from my inbox Today.

 ![Screen Shot 2020-02-17 at 15.02.35](https://canada1.discourse-cdn.com/flex031/uploads/jupyter/original/2X/f/f5fe7cd94f9ed9e9ffa5f580224f14561a961ce8.png)

It is not much, but every drop counts, and even thought the Jupyter team might be taking some time to develop a governance model, it really does not hurt at all to start a collective and see how users and people all over the world using and relying on Jupyter for their daily workflows, respond.

It takes time to create momentum and projects like webpack can brag about this level of funding:

> **[webpack - Open Collective](https://opencollective.com/webpack)**
>
> webpack is THE build solution for modern web applications.

Anyway my 2 cents 😉 !

---

<div class="post-metadata">

**Author:** ![choldgraf](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/choldgraf/32/1264_2.png) [@choldgraf](https://discourse.jupyter.org/u/choldgraf)\
**Post date:** [February 17, 2020, 9:15pm UTC](https://discourse.jupyter.org/t/open-collective-for-jupyter/3352/3 "2020-02-17T21:15:28Z")

</div>

I think this is great idea, I opened up a similar issue about this a few months back but didn’t get much traction:

> <https://github.com/jupyter/governance/issues/73>
>
> What do folks think about adding a .github/FUNDING.yml file to the Jupyter GitHub organizations so that a "sponsor" button shows up?
> We...

This is something I’d be happy to brainstorm with others!

---

<div class="post-metadata">

**Author:** ![goanpeca](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/goanpeca/32/1579_2.png) [@goanpeca](https://discourse.jupyter.org/u/goanpeca)\
**Post date:** [February 17, 2020, 9:28pm UTC](https://discourse.jupyter.org/t/open-collective-for-jupyter/3352/4 "2020-02-17T21:28:41Z")

</div>

I think one of the key factors on having a sponsor _button point to NumFocus donate button_ vs. _have it point to open collective_, is that the open collective platform, model, and effort to make every expense transparent makes it a much more appealing option for donors.

As @saulshanabrook pointed out, the fiscal sponsorship could be handled by NumFocus anyway, but the platform (which is what I believe is a big plus) would be open collective.

Also on open collective it is very clear who (person/company) is donating and how much, which also adds to the trust of the platform. OC themselves are very open in general [https://opencollective.com/opencollective/expenses/13843](https://opencollective.com/opencollective/expenses/13843).

---

<div class="post-metadata">

**Author:** ![choldgraf](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/choldgraf/32/1264_2.png) [@choldgraf](https://discourse.jupyter.org/u/choldgraf)\
**Post date:** [February 18, 2020, 3:41am UTC](https://discourse.jupyter.org/t/open-collective-for-jupyter/3352/5 "2020-02-18T03:41:16Z")

</div>

I am happy with either one - I don’t have strong opinions about the particular platform used for taking in donations, I just pointed out the NumFocus page because it already exists. I’m happy to support any efforts to set something like this up one way or another.

---

<div class="post-metadata">

**Author:** ![moscardo](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/moscardo/32/1307_2.png) [@moscardo](https://discourse.jupyter.org/u/moscardo)\
**Post date:** [February 21, 2020, 11:43am UTC](https://discourse.jupyter.org/t/open-collective-for-jupyter/3352/6 "2020-02-21T11:43:53Z")

</div>

We are looking for an improvement of the LDAP plugin to get the GID into jupyterhub. So we want our users to get LDAP UID/GID and we would be willing to pay the full cost of it. How could we speed this up a little bit?  
Thanks.