Is anyone from the Organic Maps and OSM contributor communities familiar with the people forking this, and can vouch for their intentions and the necessity of forking?
How do we get confidence in that?
The thing being forked could also respond to these clear assertion, which could be a check against confusing forks that are bad-faith, ill-conceived, not necessarily aligned, etc.
(Of course, when I hear of a fork, I instantly assume that there was probably a good reason, and there usually is, but always assuming that is a mistake, which exposes us another way to bad actor risk.)
Here's the CoMaps governance repo for deciding on decisionmaking: https://codeberg.org/comaps/Governance/ and the leadership here https://codeberg.org/org/comaps/members vs top contributors to OM since the Maps.me fork: https://github.com/organicmaps/organicmaps/graphs/contributo...
We've got some FAQs up about legitimacy and plans but the website was literally coming together over the weekend, so there's more work to be done for sure. https://www.comaps.app/support/ -- one thing we're also trying to do is focus on the future rather than rehash issues that haven't seen resolution in chat channels in over a month and don't seem to be getting resolved any time soon. The community and users deserve an actively-developed app, and the CoMaps founders don't want to continue contributing to a for-profit app, so in absence of a timely satisfactory resolution all our energy is going into the fork!
Thanks for those helpful comments about this particular fork. It's a good example for a question about best practices for our field.