The guidelines are helpful high level guidance but the actual challenge is in implementation. Building a proper data operation, whether in OSM or not, is not just about talking to people and provide feedback. It definitely is that, but needs to be in a system. But working across all aspects of data operations systematically.
It would really benefit the broader community to understand what those systems look like from groups that have built them. HOT could learn and the authors of the guidelines could learn, if they want to listen. Mikel On Thursday, March 28, 2019, 2:04 PM, Rory McCann <[email protected]> wrote: On 28.03.19 02:57, Vao Matua wrote: > I have observed some characteristics about the OSM mapping through HOT > tasks being done by mapathons, primarily ones done by corporate sponsors. > It appears that often these efforts are not well led, or at least not > led by individuals that have a good level of OSM experience and skills. > The results are that very common mistakes and errors are created. > ... > Perhaps HOT should establish a test or a vetting process for potential > mapathon leaders? Isn't this why we created the Organized Editing Guidelines in the first place? One solution is for mapathon hosts to talk about it before hand, and for people will more experience to provide feedback? We spent a year on the organized editing policy. Why fart around ignoring the solution we have chosen. Let's move on. Mapathons can be of good quality and good for the community by following the policy. The rules are there. Follow them. Map. Organize. Have fun. Rory _______________________________________________ HOT mailing list [email protected] https://lists.openstreetmap.org/listinfo/hot
_______________________________________________ HOT mailing list [email protected] https://lists.openstreetmap.org/listinfo/hot
