# MapComplete futures ## Organizational structure options * Pieter's project * OSMbe project * For profit organization * Non-profit organization (coop, vzw) * ...? Who are the stakeholders? ## How to get funding ### Current funding * Groen (groenzoeker) > core * Brussels Mobility (Cyclofix) > core * Provincie Antwerpen (Groendoener) > theme + caching - localized * Provincie Oost-Vlaanderen (cycle paths) > core + theme - possibly localized * NatuurPunt > core + theme (mapviewer) * Toerisme Vlaanderen > theme (data collection) * maybe: OSM UK address verifier > core (data collection with external dataset) ### Funding methods * ad hoc commercial projects * great for startup * forgets about upkeep * maintainance contracts * in scope with NatuurPunt & Toerisme Vlaanderen * OSM projects * from OSMbe * from OSMF ### Funding models * new theme development versus branded themes * "branded theme" implies localized theme, and selling the same functionality again and again * risk/benefit of locking themes to an area * makes sense for highly specific themes (say, objects managed by a certain organization, or layout highly customized in their style) * makes less sense for general themes (focus on a topic) * makes more sense if the client buys not just a theme, but also promotion of the tool or data work * benefit: reduce free-riding by non-funders * risk: less "oh look how awesomely open we are" benefit > hard bargain to sell something that costs close to nothing. (Especially risky if a theme is not really promoted by the original client) ## What are the core tasks? * maintainance * feature growth * refactoring / improvement under the hood * more advanced features * more attractive as a mapviewer for dummies (priority or not?) * marketing * community management Some of these get funded, some are done by volunteers.