The GeoNode Roadmap Process is designed to complement the more technical gnips and strives to make it easier for the various organizations invested in GeoNode to collaborate on features of common interest.
It is based on the roadmap items developed at the GeoNode Summit held in May 2011.
Overall, the process for adding items to the collective roadmap is as follows:
- Organizational partner has an intent to add a feature to the roadmap.
- Organizational partner communicates with the organizational partners list about the change to gauge interest and determine who else is committed to making it happen.
- Organizational partner creates a feature specification on the wiki to further flesh out the idea.
- Organizational partner finds a committer on the developer list to shepherd the roadmap item through the GeoNode Improvement Proposals (GNIPS).
Each roadmap item will go through four stages:
- Descriptive Stage (under discussion/”Active”)
- Technical Stage
- Development Stage
After communicating on the organizational partners list the roadmap items enters the Descriptive Stage and must have a wiki page that lays out the description, user stories, and other interested parties. Optionally, the roadmap item will also include an idea of the difficulty and goals as well as any wireframes, technical diagrams, or prior art.
A roadmap item enters the Technical Stage once a committer has been found to shepherd the roadmap item through the GNIPS process, then the wiki page must contain a clear sense of the technical assumptions, requirements or dependencies, and suggested implementation. Some roadmap items may need to be divided into multiple independent GNIP proposals.
Once it passes through the Improvement Proposals process, a roadmap item enters the Development Stage on its way to Release.