Community Proposals

See the proposal process guidelines for more details.

1. Discussion
   Create an issue to track discussion and status around the proposal. In this issue, scope out whatever information is needed to drive conversation and sharpen ideas about the proposal.
   
   • Use our GitHub Issue Template to submit your proposal.
   • Scope out whatever information is needed to drive conversation and sharpen ideas about the proposal.
   • Create an issue for your proposal idea here →
2. Draft Your Proposal
   When the idea is concrete enough, draft language for the proposal in a proposal Google Doc.
   
   • Create your proposal by copying the Google Doc Proposal Template.
   • Include clear goals, expected outcomes, and an estimated budget.
   • Keep it concise and easy to understand.
3. Submitting Your Proposal
   • In the proposal Google Doc, mark its status as “Reviewing”.
   • In the proposal GitHub issue, post a comment mentioning the @jupyter-foundation-admins team asking them to move the issue status to “Reviewing”.
4. Follow-Up
   • You may be contacted with additional questions about your submission.
   • In addition to asking questions on the discussion issue you created above, feel free to ask questions on the Jupyter Zulip Chat.

Any active Jupyter community member or contributor can submit a funding proposal. We especially encourage collaborative submissions from multiple community members.

Proposals are due September 28, 2025, Anywhere on Earth. See the timeline below for more details.

The jupyter-foundation/funding-proposals repository has one issue for each proposal. This Funding Proposal progress board contains the current status of all funding proposals.

Use the comments of each proposal’s issue for discussion around the proposal itself. Eventually, proposal authors will create Google Docs to write content. Use the comments in the Google Doc to discuss language within the proposal. See the funding proposal guidelines for more information.

To increase the likelihood of your proposal being accepted:

• Focus on outcomes and community value rather than implementation details.
  Align your proposal to the Jupyter Foundation priorities:
  • Grow contributor capacity
  • Improve the reliability, security, and consistency of Jupyter’s software
• Keep your budget reasonable; smaller budget proposals tend to have a higher acceptance rate. That said, don’t hesitate to be ambitious! We want to see creative and impactful ideas.
• Demonstrate strong community support for your proposal through endorsements, references, or visible discussion.

This CFP is an experiment aimed at learning how to deliver community-based proposals, so please bear with us and provide feedback! In this first round of funding proposals, our goal is to release enough funding that we can improve this process, learn what delivers value to the Jupyter community, and have some impact that supports our funding priorities.

Here are milestones we are targeting in this CFP process.

• We aim to solicit at least 2-4 proposals in this CFP round.
• We aim to award at least $225K. We hope to exceed this, but consider this the minimum target to help us learn and deliver value.
• As this is the inaugural CFP from the Jupyter Foundation Governing Board, we aim to learn by exercising this funding process to provide some concrete and positive impact for the Jupyter community via the funded proposals. 

We look forward to seeing your ideas and working together to make the Jupyter ecosystem even stronger!