-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CZI: proposal information needed #99
Comments
Here are links to two to of the previous Jupyter Related accepted CZI fundings
More/Sloan/Helmsley funding (2015) https://blog.jupyter.org/new-funding-for-jupyter-12009a836867 |
@choldgraf do you happen to have the full proposal for the contributor in residence? From the RTC proposal the figures listed for funding are:
|
Hey all - this issue of previous funding has come up a few times, so I've created this Google Sheet to record the ones that I know of right now. It's stored in the JupyterHub team's "proposals and grants" folder, and is editable by anybody on the internet: https://docs.google.com/spreadsheets/d/1kP1ggTmBji7eGlXYakBfRXKS_I7hjFxKR-gfkh-vO50/edit?usp=sharing Want to update that list if you learn of anything new, and we can use this as a reference for future proposals as well? I also opened up a Community Forum topic to share this: |
Hi all
As many of you might be aware a few folks and I are working on a CZI EOSS proposal to tackle accessibility issues in the Jupyter ecosystem.
In the proposal we have to provide information regarding
Existing support
to the Jupyter ecosystem, esp:Since there are 4 proposals being worked on atm I was wondering if there was a way to have this information and share with the rest of the folks working on proposals.
For reference here is the Discourse item where we are keeping track of the proposals:
https://discourse.jupyter.org/t/coordinating-czi-eoss-applications-across-the-community/8472/13
cc/ @choldgraf @Carreau and @minrk who I know are the respective PI's in the other proposals
The text was updated successfully, but these errors were encountered: