Skip to content

replace OrganicMaps with CoMaps#6451

Merged
westnordost merged 2 commits intomasterfrom
comaps
Sep 29, 2025
Merged

replace OrganicMaps with CoMaps#6451
westnordost merged 2 commits intomasterfrom
comaps

Conversation

@westnordost
Copy link
Member

organic maps is no longer fully open source

organic maps is no longer fully open source
@westnordost westnordost changed the title replace organic maps with comaps replace OrganicMaps with CoMaps Aug 17, 2025
@westnordost
Copy link
Member Author

westnordost commented Aug 17, 2025

Currently only based on this comment. OM owners are somewhat mute on the topic, other than accusing CoMaps contributors of "stealing".

So, it might very well be that they will publish that latest code... but at least the current version currently available on Google Play and F-Droid isn't fully open source anymore. And actually, according to this comment, it may have been like that for years. (In a nutshell: New code for generation of map data which is required for the app to work correctly was not added into public repository).
The guideline for included links is that the software should be free and open source, without ads etc.. Organic Maps still somewhat fulfills this guideline, but the CoMaps fork is, well, fully open source, so that's better to recommend from a FOSS/OSM point of view, even if it may (currently) lag behind in features.

The drama about OM is still unfolding, maybe we should wait with merging this, but then again, the drama has been going on since last year, it seems unlikely that OM team will have a change of heart now.

@matkoniecz
Copy link
Member

matkoniecz commented Aug 20, 2025

In a nutshell: New code for generation of map data which is required for the app to work correctly was not added into public repository

to be 100% clear: this code is not part of the app itself (it technically remains open source as it is not part of the app itself), but without it you cannot generate map files needed for app to work

other than accusing CoMaps contributors of "stealing".

they did it in quite unclear way and refused to elaborate despite requests, but clearly claimed that there is proprietary non-public code

which confirms that project is not fully open-source

Also, they now have quite confusing NOTICE file, and refused to fix it: organicmaps/organicmaps#10987 (comment)

@matkoniecz
Copy link
Member

I would be happy to merge it and take responsibility for it (OK, I would still need to check whether icon works - I do not remember whether I did it already)

@westnordost would you prefer to wait more with this change?

@westnordost
Copy link
Member Author

westnordost commented Sep 2, 2025 via email

@matkoniecz
Copy link
Member

matkoniecz commented Sep 2, 2025

I'm still undecided whether to keep OM alongside CoMaps or not.

it is nearly total duplicate right now and it seems unlikely (for now) that they will diverge much

I would not include both

@mnalis
Copy link
Member

mnalis commented Sep 2, 2025

I'm still undecided whether to keep OM alongside CoMaps or not.

I don't think SC should keep promoting OM. As @matkoniecz said CoMaps is almost the same, and given OM reluctance to clarify whether the map generating code is FOSS or to explain/correct their accusations of "stealing" FOSS code I think OrganicMaps should be just replaced with CoMaps...

@matkoniecz
Copy link
Member

matkoniecz commented Sep 2, 2025

also that, if they claim that CoMaps is breaking license/similar then they really could have answered followup questions

if CoMaps is not doing that and is doing fork (like Organic Maps did to MAPS.ME), then claiming otherwise is really bad

I waited quite a long time and at that point I am going to assume that accusations from the Open Letter are all accurate

# Conflicts:
#	app/src/commonMain/kotlin/de/westnordost/streetcomplete/data/user/achievements/AchievementDefinitionsModule.kt
@westnordost
Copy link
Member Author

westnordost commented Sep 29, 2025

Ref organicmaps/organicmaps#11249

While the maintainer claims it is still open source (well, at least the app, which remains true, as far as I know), he also threatens in the same breath the open source fork that takes code from OM with legal action and explicitly reserves the right to withhold parts of the in-production codebase for basically any amount of time, possibly required to run the software properly.

So, while I wouldn't remove an app from suggestions based on public behavior of the owner, he tries very hard to introduce legal uncertainty into the republishability of its code, which I find unacceptable for an open source project.


(I was considering to leave both as suggestions, but decided to just replace OM with CoMaps.)

@westnordost westnordost merged commit 0cda9ae into master Sep 29, 2025
@FloEdelmann FloEdelmann deleted the comaps branch September 30, 2025 07:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants