defining three groups: people using/exploring MapReader, people contributing to documentation, people contributing to code, people contributing to worked examples (see Split contribution guide into different types of contributors #146)

think about how these roles are separate, but also have some shared space (and we want to encourage the shared space, but also respect that there are different skills required)

use roadmap doc created by @kallewesterling to review feedback vs our goals

distinct problem of maps. this is something different, based on different principles from vector data capture.

June: invite people to figure out what's missing