<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:10pt"><div><span>To keep is dynamism and retain contributors, it is essential for OSM to keep a flexible type of organizational mapping. To control some commercial organizations, we should not implement rules that will affect all the community, and make some contributors to slow down their participation because they find too restrictive new rules such as creating a second account or create a wiki page.</span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><br><span></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent;
font-style: normal;"><span>I dont think that we can justify to create a second account. This had the effect over the last few years to slow down some valuable Imports. Adding a hasthtag in the Changeset comment would do the same. Also, we should avoid to place the burden of such controls on the contributors when there are other ways to do it. For example, it could be possible to assure the communication between the HOT Tasking Manager and OSM editors such as ID and JOSM, adding automatically a hashtag on the Changeset comment.</span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><br><span></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style:
normal;"><span>We were successful in the last two years to develop a coordination model with various humanitarian organizations, UN agencies and Aerial imagery providers. For the Haiyan Typhoon and the Ebola Epidemy, the OSM community had such a success and gained a fantastic media coverage. We are also seing more and more humanitarian NGO's doing some field work and bring data into OSM. This in parts of the world that badly need some mapping efforts in the context of more and more disasters to cope with.</span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><br><span></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><span>As said by others before,
how will we cover paid training actions, subsidies to develop various local communities, etc.<br></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; background-color: transparent; font-style: normal;"><span>Let's be careful to not restrict such collaborations by implementing too rapidly rules that will restrict participation to such actions. <br></span></div><div> </div><div><span style="font-style:italic;color:rgb(0, 0, 191);font-weight:bold;">Pierre <br></span><br></div> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 10pt;"> <div style="font-family: HelveticaNeue, Helvetica
Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">De :</span></b> Paul Norman <penorman@mac.com><br> <b><span style="font-weight: bold;">À :</span></b> 'OSM Talk' <talk@openstreetmap.org> <br> <b><span style="font-weight: bold;">Envoyé le :</span></b> Mercredi 14 mai 2014 1h44<br> <b><span style="font-weight: bold;">Objet :</span></b> [OSM-talk] Organizational mapping policy<br> </font> </div> <div class="y_msg_container"><br>We have more and more organizations and businesses mapping in OSM. <br>Multiple organizations have been conducting paid editing in Europe and <br>the US. This generally comes to light *after* complaints are made - with <br>the company usually not identifying who they are, what their goals are, <br>and what they want, beforehand. There have also been difficulties <br>determining what has
been mapped on behalf of an organization. <br><br>We will likely see more of this type of editing in the future, and while <br>not necessarily bad, there are differences between it and normal <br>editing. Recent events in a project similar to OpenStreetMap - Wikipedia <br>- have demonstrated that the participation of organizations in data <br>editing can occasionally lead to misunderstandings or disharmony in the <br>project, particularly where a lack of transparency is involved. <br><br>For this reason the DWG is considering if it is necessary to issue <br>guidelines for organizational editing. Some previous discussion is at <br><a href="http://lists.osm.org/pipermail/osmf-talk/2013-November/002344.html" target="_blank">http://lists.osm.org/pipermail/osmf-talk/2013-November/002344.html </a><br><br>There are some activities we do not want to cover in the guidelines<br><br>- Unorganized editing by employees, e.g. a shop owner adding their shop<br>
or nearby details to the map<br><br>- Editors mapping in response to a contest or similar where the contest<br> organizer does not have the power to require them to edit <br><br>- Individuals who, on their own accord, decide to participate in an <br> organised effort or challenge, like local mapping parties, Mapathons, <br> HOT projects, etc<br><br>Some possible guideline requirements could involve <br><br>- Disclosing those who are directing them (e.g. employers or who they <br> are contracting for) on the users page<br><br>- Creating a wiki page with links to user pages of users mapping under <br> an organization's direction<br> <br>- Requiring those working on broader projects to communicate and get <br> feedback from the community before starting<br><br>- Requiring disclosure of proprietary third-party sources used. <br> Organizations may have data from third parties that they can legally
<br> use when contributing to OSM, but aren't able to directly show others<br> the data<br><br>- Maintaining separate accounts if doing both personal and organizational <br> editing<br><br>The extent of editing activities covered is something else that needs to <br>be discussed.<br><br>Some types of activities that *could* be covered are<br><br>- Teachers requiring their students to edit OSM as part of a course<br><br>- Consultants editing for multiple clients<br><br>- Being required to edit as part of an employment relationship<br><br>SEO spammers would be covered by this policy, but are not the target. <br>They would ignore it, so we'll just end up using the existing tools <br>of reverting and blocking.<br><br>Paul Norman<br>For the Data Working Group<br><br><br><br>_______________________________________________<br>talk mailing list<br><a ymailto="mailto:talk@openstreetmap.org"
href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a><br><a href="https://lists.openstreetmap.org/listinfo/talk" target="_blank">https://lists.openstreetmap.org/listinfo/talk</a><br><br><br></div> </div> </div> </div></body></html>