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?
Apart from the whole organization, governance, and openness, I haven’t followed in much detail the code changes since moving to comaps, but this page has some initial changes since forking and I recall they removed the sponsored, kayak affiliate links from the fork.
And CoMaps is run by the volunteers who did majority of development on OrganicMaps anyway. Only after the fork did I start seeing actual meaningful commits in OM repo from owners themselves. For atleast a year before the fork all the big changes were made by developers who forked OM.
Apart from the whole organization, governance, and openness, I haven’t followed in much detail the code changes since moving to comaps, but this page has some initial changes since forking and I recall they removed the sponsored, kayak affiliate links from the fork.
And CoMaps is run by the volunteers who did majority of development on OrganicMaps anyway. Only after the fork did I start seeing actual meaningful commits in OM repo from owners themselves. For atleast a year before the fork all the big changes were made by developers who forked OM.