Just wanted to review some things discussed as it’s been nearly a month since we initiated this discussion and there hasn’t been any momentum in the last few weeks:
- Many community members report the experience on CoMaps is as good or better than Organic Maps. I don’t think I’ve seen anyone complain about a usability downgrade.
- CoMaps seems to have demonstrated pretty well that it is truly community-driven. (See: reply #30, project governance docs, financial transparancy)
- CoMaps is waiting on Accrescent for inclusion in their app store. In the meantime, security-conscious Android users can install it via Obtanium among other options. (Interestingly, Organic Maps doesn’t promote Accrescent as an option on their website.)
As far as I can tell, there are largely only positives of switching from Organic Maps to CoMaps. I think we mainly have 2 items to follow-up on:
- It seems like it’s a matter of when (not if) CoMaps will be recommended in place of Organic Maps. Should we wait for the project to reach a certain age? As discussed, we probably shouldn’t need to wait for the project to be 1+ years old before recommending it, but if not a year, how old should it be? Alternatively, we can pick a concrete step such as waiting til the formation of a legal entity is complete. (Perhaps @CoMaps or @IXVG47QZ have some insight as to when that may happen?)
- It’s been over a month since the last update regarding progress with Accrescent. It seems like their financial situation has improved since then so I wonder if now is a good time for CoMaps to reach back out? Anyone who’s on Codeberg can ask about it under issue #52.