Board/Minutes/2021-02-S2S/How do we define “core”, in terms of categories (e.g. software) and what is in each category?
How do we define "core", in terms of categories (e.g. software) and what is in each category?
Notes by participants. Might be enriched.
This session took place in parallel with "Discuss Membership prerequisites, steps towards Annual General Meeting (AGM) resolution". A summary was provided to the other group.
- Allan Mustard
- Eugene Alvin Villar (facilitator for this session)
- Jean-Marc Liotier
- Tobias Knerr
The rest of the board members participated in the parallel session.
Also present: Dorothea Kazazi (administrative assistant)
If it supports the mapping process, it is core. That is a new way to define core, functionally rather than technically.
Two complementary definitions:
- Technical core (crucial): rock bottom, without which Openstreetmap disappears. Mostly the database and its API
- Functional core (not crucial): the mapping process
The Openstreetmap Foundation must ensure that there is at least one fully FOSS path to complete the Openstreetmap process.
Open question: What are we willing to host on our servers/website ?
- The Openstreetmap database
- The Openstreetmap API
- OSM website
- A sufficient number of editors: iD
- At least one map rendering: osm-carto
Mostly core by decision
- Editors: iD, Potlatch 3, JOSM (funds offered)
- Database tools: osm2pgsql
- Geocoder: Nominatim
Pillars of the mapping process
- A quality assurance framework (Osmose, Keepright, OSMcha)
- Sufficient querying API (Overpass)
- Sufficient reporting (Taginfo etc.)
- number of users of tool/software
- lack of alternatives
- lack of alternative funding
Various tools for discussion:
- Database tools: Osmosis
- Editors: JOSM, Vespucci, RapiD
- mapping survey tools (e.g, Field Papers, Mapillary, KartaView)
- data inspection (example: Taginfo)
- quality assurance tools (e.g., OverPass Turbo(?), Osmose, Geofabrik Inspector, osmcha)
- rendering tools (e.g., website, tile servers)
- geocoders/reverse geocoders (e.g., Nominatim)
- libraries and APIs for building applications (example: uMap, Leaflet, osm2pgsql, osmium, osmosis, Overpass API)
- end-user applications
- communication platforms
- The Openstreetmap Foundation must ensure that there is at least one fully FOSS path to complete the Openstreetmap process.
- Continue conversation.