pastk

Yeap latest CoMaps update took ~16 days to review (the longest wait for us so far) and two support tickets (submitted first after ~9 days and got "we have expedited it", 5 days later still in review, so submitted one more ticket).

Before that we had a hotfix update (a very small change) and still it took longer than a week and a support ticket (after which it had been approved in a day)...

Hosting etc. expenses are a minor fraction compared to OM's donations inflow. And its enough to hire devs, the first dev was hired more than two years ago, but they have been hiding this fact to look more poor and attract more donations.

Even long-term active contributors have been denied even totals information about donations and got to know about first hire by chance about a year since the fact.

The code in question was in Apache 2.0 repo and DCO signed agreeing its a public contribution.

Please see my post above for details.

Also me and other CoMaps contributors had been actually banned several months later after they've started their accusations, so the ban is not directly because of the accusations.

At first we've been having discussion and arguing about the matter and related topics in OM chats. But people saw their very shaky arguments and how they refute their own previous words about openness of the maps generator etc.

So then they started just deleting such discussions and eventually banning CoMaps contributors.

And nowadays they censor all mentions of CoMaps in their chats and SMs and often ban users who dared to mention us.

To clarify - this quote pertains to the Organic Maps situation

> Despite being advertised as a community-driven project, key decisions, including financial management, partnerships (with Kayak, for instance), and the inclusion of proprietary components in the code were made by a small group of shareholders, often without input from the broader contributor community.

CoMaps had been started because Organic Maps shareholders were not interested fixing those governance and transparency issues.

Proprietary parts had been mentioned in the context of Organic Maps - their map generator is partially closed source, and even OM F-Droid build includes some proprietary assets.

In CoMaps we are serious about being 100% FOSS and this is one of the reasons we've forked from OM.

Don't worry, we have no proprietary code in all builds of CoMaps, not just F-Droid one :)

> made by... "community"? We don't even know who that is, original developers and people with experience are not involved.

FYI I've been the most active non-shareholder contributor of Organic Maps for 3+ years. Though you won't see me (or other ex-OM contributors who've left to start CoMaps) in OM github contributor stats anymore, because OM had banned us (and nowadays they also ban users in their chats and SM accounts for just mentioning CoMaps). But you can still see our PRs, e.g. I've authored Outdoor map style amongst many other improvements.

You're right though that CoMaps had been founded because of things like governance, transparency, community and FOSS values, while many users are just interested in features (and hence often prefer Maps.ME even, which is like 10x more popular than OM looking at downloads).

There is an outdoor map style which is more contrast to the general/default style, if that helps.

There is a subway overlay. And there is marked hiking routes overlay being in development. There is a also an outdoor-focused map style (some people call it a layer too).