Some are asking: why does privacy-focused Organic Maps use GitHub? The largest open-source contributor network, familiar PR & issue workflow, Actions CI, broad integrations, zero infra to maintain, and easy onboarding/discoverability. This lets us focus on improving the app instead of running and maintaining servers. Development time is the most precious resource nowadays, and most of our users don't care where the code is hosted, but care about the app functionality and usability…
Do you care?
Isn’t all of their concern kind of demonstrated to be unfounded? CoMaps forked the exact codebase being discussed and moved to Codeberg already, and they’re doing great now. Whatever it is that the Organic Maps team thinks is indispensable on GitHub is clearly not actually an insurmountable challenge to ditch.
Isn’t all of their concern kind of demonstrated to be unfounded? CoMaps forked the exact codebase being discussed and moved to Codeberg already, and they’re doing great now. Whatever it is that the Organic Maps team thinks is indispensable on GitHub is clearly not actually an insurmountable challenge to ditch.