This repository acts as a "roadmap" for the GeoJupyter community.
The reason this repository exists is to enable roadmapping as a living discussion, not a static artifact.
Writing initiatives may require adopting a mindset that doesn't come naturally to you. These tips are intended to help you get in to the right mindset.
Your job as an initiative author is not to advocate for a specific idea. Your job is to instead characterize an opportunity clearly enough that the community can compare it to other opportunities and decide whether (and when) to pursue it.
Try imagining yourself reading your answers to each question out loud to another person, and then imagine them asking follow up questions. If they can't understand what you said in your answer (and the detail isn't in another section) then you have to go back and clarify.
When filling out specific fields, carefully read the field descriptions in the GitHub template. They are written to help you get in to the right mindset!
- https://miro.com/blog/mapping-product-teams-teresa-torres/
- https://learn.producttalk.org/continuous-interviewing
- https://www.mountaingoatsoftware.com/blog/why-the-three-part-user-story-template-works-so-well
The roadmap is managed as GitHub issues.
Labels are used to categorize and prioritize the issues.
This repository includes a "linter" (in the validator/ directory) for those issues
which ensures each issue provides necessary details for us to effectively plan each
initiative.
The GeoJupyter Initiatives Project Board gives us an interface to visualize issues. This is a work in progress.
This is inspired by the 2i2c initiatives repository and the JupyterHub community's roadmapping workshop in early 2026.
- Support structural validation of headers (i.e. not just the header level but what children a header should have)
- Explore how we might use a project board