<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi all,<div><br></div><div>First off I am sorry for not announcing the meetings. We had one this morning, notes:</div><div><a href="http://matt.dev.openstreetmap.org/osm-strategic/2013/osm-strategic.2013-02-28-15.03.html">http://matt.dev.openstreetmap.org/osm-strategic/2013/osm-strategic.2013-02-28-15.03.html</a></div><div><br></div><div>Some quick notes from memory now that it's fresh:</div><div><br></div><div>We focused on messaging new mappers. </div><div>Two strategies emerged. </div><div>One would be to just message all new mappers after they make their first edit, using Pascal Neis's new mapper feeds.</div><div>Charlotte is going to write a proposal for the CWG as this is something we would definitely need to run past them. She will post here first.</div><div>Another more involved approach is to empower folks to start sending out messages to new mappers regionally. These messages would be more tailored (language, culture, info specific to region).</div><div>For that we would need to describe a workflow that could be easily adopted.</div><div>I identified five elements we would need:</div><div><div>[08:43] < mvexel> | 1) tools to monitor new mappers in an area CHECK</div><div>[08:44] < mvexel> | 2) new mapper message templates that people can get inspiration from</div><div>[08:44] < mvexel> | 3) a tool to (semi) automatically send these messages</div><div>[08:45] < mvexel> | and most importantly 4) local leaders who initiate the process and oversee it for their region</div><div>[08:46] < mvexel> | and finally 5) a page that documents all this well so it's easy for folks to get started with the process</div></div><div>I will work on collecting the information needed to describe such a workflow.</div><div>In the mean time, feedback is of course much appreciated!</div><div><br></div><div>Next meeting Thursday next, Mar 7. We will stick with the 1500Z time slot unless we come up with something better. (Enter preferred time slot here: <a href="http://doodle.com/bxgspb4qdd4bmht5">http://doodle.com/bxgspb4qdd4bmht5</a>).</div><div><div><div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>-- </div><div>Martijn van Exel</div></div>
</div>
<br></div></div></body></html>