This kind of testing and feedback is important for Organic Maps. Good on the author for taking the time to evaluate, investigate, and file an issue on GitHub. It takes so much time, but is invaluable.
Still, as someone who has contributed tens of thousands of edits to OpenStreetMap, uploaded hundreds of GPS traces, donates to Organic Maps, and compiles the Organic Maps Android application from git master a few times a week, I constantly find myself wondering when it will finally be good enough that I won't second guess it.
If you are this deeply involved with Organic Maps, you might never trust it fully. You know too much!
This is true of any software developer. Something that looks great from the outside can be really nasty under the hood. It's easy to bias your view of your work based on the tiny flaws you see in it, but the average user wouldn't see those faults.
Still, as someone who has contributed tens of thousands of edits to OpenStreetMap, uploaded hundreds of GPS traces, donates to Organic Maps, and compiles the Organic Maps Android application from git master a few times a week, I constantly find myself wondering when it will finally be good enough that I won't second guess it.