Create and align the Jupyter community on a vision that drives the project forward

[choldgraf]

Next actions

• Identify a person/organization that can assist the JEC in leading community conversations around technical and product vision.
• Conduct these discussions
• JEC synthesizes a few big ideas and proposes them
• Feedback and iteration
• JEC votes on a finalized proposal.

Context

It is critical for a project to have big ideas and goals that drive its action. These are ambitious and impactful things that rally people's excitement, help align efforts across the community, and can potentially be used to grow resources needed to get things done (either from in-kind labor, or from fundraising).

Jupyter doesn't currently have a singular definition of these big ideas. It has several subprojects, each of which has their own product vision, roadmap, etc, but not a coherent story that brings them all together. This both makes it hard to coordinate and align the actions across all subprojects, and also makes it hard for external stakeholders to learn what Jupyter wants to accomplish, and how they can help. We believe that helping Jupyter define a vision for itself is key.

We think that the @jupyter-governance/executive-council is the right group to do this, because it has the most visibility and representation across the Jupyter ecosystem (for example, because it has connections both to the Union of Councils, and to the Jupyter Foundation). However we want to ensure that this happens in conversation with the other key stakeholders in the Jupyter ecosystem (particularly the UoC and the Foundation members).

What would be needed to do this?

Doing this effectively would require a combination of:

• Gathering information and input from the Jupyter Community and the Jupyter Foundation Members
• Synthesizing this information into a concrete direction (e.g., 3-5 strategic pillars to drive the project forward)
• Getting feedback to improve this proposal and get buy-in / alignment across the community

What would we need

We'd like to identify a person or group that can help structure and facilitate these conversations, so that we can have them effectively as a community. The @jupyter-governance/executive-council can help with some of this, but wants to participate at a content level primarily (not just facilitation).