Thanks for the wiki page. We already filled the page with information. It was definitely one of the next steps for us to create and maintain the page.
Concerning your criticism: Well, with some of the issues you might be right (e.g. the binary package), but others are not really fair.
It’s not true that OSMapTuner was first announced after the work is done (BTW: it’s worth to mention that for us the work is by far not done with the release of the App). We worked on OSMapTuner for 3 years now, did a community workshop with the local OSM community in Austria, had a presentation at the SOTM Europe last year (http://sotm-eu.org/talk?50), had presentations at several conferences, e.g. AGIT 2011 (http://www.agit.at) and LBS 2011 (http://lbs2011.org). We submitted an abstract to FOSSGIS conference 2012 http://www.fossgis.de/konferenz/2012/ but did not get accepted. Since three years we are organizing the “OpenStreetMap Spezialforum” in the context of the annual AGIT conference with the goal to improve communication between the GIS and the OSM community.
Maybe you consider the channels above as the wrong channels. We are now trying to improve communication and to post information to the “right” channels. Although we are not OSM newbies (all of us are active OSM contributors), it’s not always easy for us to find the right channel to the community. We are glad about any suggestions.
That’s definitely not fair. Since we are very interested in valuable feedback, we offer several feedback channels (directly via Google Play, OSM forum, email, etc.) and provide answers in acceptable time. Although it’s not always possible to react within hours since OSMapTuner is only one of our numerous projects, we try our best and try to react within days.
Well, that’s a good point: What do you mean in full cooperation with the community? One of the answers is, that each of us feels as part of the community (I hope you agree with this). OSMapTuner is one of the results of our research work which we decided to contribute to the community. Data contributions are another issue (as already mentioned we are also active mappers in our spare time). As in any community, contributions may be liked or disliked. We are happy about the likes and try to improve our work to minimize the dislikes (although this is not an easy job as any community member has good reasons to like or dislike a contribution). So, OSMapTuner is maybe on the edge of two different communities: the scientific community and the OSM community. This may be challenging, but we are confident that such contributions can give new directions to both communities.
In your eyes, what would be a useful result? Don’t you agree, that any result which brings the OpenStreetMap project forward is a useful result? The release of OSMapTuner should pursue this goal (otherwise we would not have released the App). It’s very difficult to know in advance which direction brings the best results. With OSMapTuner we want to open new perspectives in mobile editing. It is designed to best support some of the mobile editing use cases. We don’t want to substitute any editor, but offer additional opportunities. That answers the question why OSMapTuner has only limited functionality. That’s not a bug, it’s a feature! OSMapTuner can be seen as a kind of experiment. With an easy to use interface we want to reduce the hurdle for OSM contributions and open the project to potential new contributors (in a similar way as http://wheelmap.org). As described on the project’s home page OSMapTuner is also perfectly suited to get to know the OSM project (check which data is already there, check tags and tag values, get to know the OSM wiki, aso.). Maybe it is not the best editor for “power mappers”. However, my preferred mapping style is to edit geometries from aerial imagery with JSOM and afterwards I go out and add the details (e.g. addresses) with OSMapTuner. One of the most valuable characteristics of the OSM project is that any mapper is free to establish an own mapping style. So, let’s have a try and look forward to the things happening. OSMapTuner succeeds if it helps to open new possibilities for contribution.
That’s definitely one of the issues we heavily discussed. By now we have decided to release OSMapTuner for free as binary package (except the changes to the mapsforge library which are publically available on our SVN). We are aware that some members of the OSM community refuse to use closed source tools to edit open data. However, on the other hand we think that most of the community members will be perfectly happy with a free tool and are not willing/able to contribute on a source code level. As research company we have to gain some return on investment (our work has to be financed somehow). Our current strategy is to re-use parts of the source code in commercial projects in order to gain some return on investment to ensure the further development of OSMapTuner in the future. However, we are also thinking about other strategies to finance our work. So, maybe in the future we will be able to release the source code of OSMapTuner to the public. In the meanwhile, anybody is free to decide whether the use of free but closed source software is acceptable for him/her to edit open data. For those not accepting closed source applications, there are several other open source editing options such as Vespucci, JOSM, aso. We understand OpenStreetMap as open project which gives us the opportunity to experiment with new ways of contribution/financing. Some of them will succeed and others fail. If closed source applications fail we might have to change our plans
We hope this helps to clarify some of the issues raised in previous comments.
So, keep tuning the map with OSMapTuner.
Karl Rehrl for the OSMapTuner Team