<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yiv9156747621"><div id="yui_3_16_0_ym19_1_1475155829729_130813"><div style="color:#000;background-color:#fff;font-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;" id="yui_3_16_0_ym19_1_1475155829729_130812"><div id="yiv9156747621yui_3_16_0_ym19_1_1475155829729_86351"><span id="yui_3_16_0_ym19_1_1475155829729_130849">Great thread. Two points with two hats</span></div><div id="yiv9156747621yui_3_16_0_ym19_1_1475155829729_86351"><span><br clear="none"></span></div><div id="yiv9156747621yui_3_16_0_ym19_1_1475155829729_86351"><span id="yiv9156747621yui_3_16_0_ym19_1_1475155829729_87029">With my Mapbox hat on, there is definite interest to contribute developer time to more core software projects. It's just a matter of having a clear plan and avenues to contribute without shouldering all the burden of organizing everything.</span></div><div id="yiv9156747621yui_3_16_0_ym19_1_1475155829729_86351"><span><br clear="none"></span></div><div id="yiv9156747621yui_3_16_0_ym19_1_1475155829729_86351"><span id="yiv9156747621yui_3_16_0_ym19_1_1475155829729_87237">With my Board hat on, I don't see any conflict with a mixture of resources -- paid and volunteer -- dedicated to core software. If structured right, having some paid project or maintainer can encourage more volunteer contributions (iD is a good example of this). Not saying this is necessarily the strategy, but glad that "spending some money" is an option on the table.</span></div><div id="yiv9156747621yui_3_16_0_ym19_1_1475155829729_86351"><br clear="none"></div><div class="yiv9156747621signature" id="yiv9156747621yui_3_16_0_ym19_1_1475155829729_86298">* Mikel Maron * +14152835207 @mikel s:mikelmaron</div> <div class="yiv9156747621qtdSeparateBR" id="yui_3_16_0_ym19_1_1475155829729_130817"><br clear="none"><br clear="none"></div></div></div></div><div class=".yiv9156747621yahoo_quoted"> <div style="font-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div class="qtdSeparateBR"><br><br></div><div class="yiv9156747621yqt6069743096" id="yiv9156747621yqtfd20455"><div dir="ltr"><font size="2" face="Arial"> On Thursday, September 29, 2016 10:29 AM, Simon Poole <simon@poole.ch> wrote:<br clear="none"></font></div> <blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;margin-top:5px;padding-left:5px;"> <br clear="none"><br clear="none"> <div class="yiv9156747621y_msg_container"><br clear="none"><br clear="none">Am 29.09.2016 um 16:08 schrieb Ilya Zverev:<br clear="none">> This looks similar to what I proposed earlier for reorganization of EWG:<br clear="none">Actually not.<br clear="none"><br clear="none">I'm proposing nothing more complicated and involved than writing a<br clear="none">minimal spec (which in the worst case I will do) adding some money and<br clear="none">asking Andy or someone else to implement it.<br clear="none"><br clear="none">While I wouldn't simply want to dismiss doing all you list below just<br clear="none">like that, it isn't as if it hasn't been tried before, and while there<br clear="none">are lots and lots of people working on their own projects (including<br clear="none">myself) the situation wrt osm.org hasn't really changed over the years<br clear="none">with the results as Andy has pointed out.<br clear="none"><br clear="none">Simon<br clear="none"><br clear="none">PS: just in case it goes forgotten, the over large project is Matts work<br clear="none">of moving the API proper in to CGI-MAP which should bring lots of long<br clear="none">term benefits.<div class="yiv9156747621yqt3173174980" id="yiv9156747621yqtfd83600"><br clear="none"> <br clear="none">><br clear="none">> The Engineering Working Group will do little programming, but a lot of planning and community relations. Its tasks are outlined on the current EWG wiki page: assistance with developer events, helping new developers with current tasks and directing them to people who know stuff (e.g. to core software developers). And financial assistance: grants for hosting hackathons, and potentially grants for developing software. The scope of this group is finding new developers and promoting the OSM development. It partially includes development strategy, since this group should know where the project is heading and which tools are needed.<br clear="none">><br clear="none">> Working on the EWG would be hard, but I hope rewarding. If you want to help, discussing the development strategy and forming proposals weekly, drop me a note. We'll have the first EWG meeting late October if we have enough members.<br clear="none">><br clear="none">> IZ<br clear="none">><br clear="none">>> 29 сент. 2016 г., в 16:49, Benoit Fournier <<a rel="nofollow" shape="rect" ymailto="mailto:ben.fournier@gmail.com" target="_blank" href="mailto:ben.fournier@gmail.com">ben.fournier@gmail.com</a>> написал(а):<br clear="none">>><br clear="none">>> Let me add that this was an item during the Sunday session "Local<br clear="none">>> chapters congress", an open discussion at State of the Map a few days<br clear="none">>> ago.<br clear="none">>> Thank you Simon for putting some of the more actionable ideas here for<br clear="none">>> more discussion.<br clear="none">>><br clear="none">>> My take on this:<br clear="none">>> A lot of different people from different communities did show interest<br clear="none">>> for better tools with regards to communication and community building,<br clear="none">>> local and global.<br clear="none">>> The general idea was to facilitate welcoming, gathering, interacting.<br clear="none">>><br clear="none">>> I agree that group messaging & news dropdown are good suggestions and<br clear="none">>> good steps.<br clear="none">>><br clear="none">>> Benoît<br clear="none">>><br clear="none">>> _______________________________________________<br clear="none">>> osmf-talk mailing list<br clear="none">>> <a rel="nofollow" shape="rect" ymailto="mailto:osmf-talk@openstreetmap.org" target="_blank" href="mailto:osmf-talk@openstreetmap.org">osmf-talk@openstreetmap.org</a><br clear="none">>> <a rel="nofollow" shape="rect" target="_blank" href="https://lists.openstreetmap.org/listinfo/osmf-talk">https://lists.openstreetmap.org/listinfo/osmf-talk</a><br clear="none">><br clear="none">> _______________________________________________<br clear="none">> osmf-talk mailing list<br clear="none">> <a rel="nofollow" shape="rect" ymailto="mailto:osmf-talk@openstreetmap.org" target="_blank" href="mailto:osmf-talk@openstreetmap.org">osmf-talk@openstreetmap.org</a><br clear="none">> <a rel="nofollow" shape="rect" target="_blank" href="https://lists.openstreetmap.org/listinfo/osmf-talk">https://lists.openstreetmap.org/listinfo/osmf-talk</a><br clear="none"><br clear="none"></div><br clear="none"><div class="yiv9156747621yqt3173174980" id="yiv9156747621yqtfd16614">_______________________________________________<br clear="none">osmf-talk mailing list<br clear="none"><a rel="nofollow" shape="rect" ymailto="mailto:osmf-talk@openstreetmap.org" target="_blank" href="mailto:osmf-talk@openstreetmap.org">osmf-talk@openstreetmap.org</a><br clear="none"><a rel="nofollow" shape="rect" target="_blank" href="https://lists.openstreetmap.org/listinfo/osmf-talk">https://lists.openstreetmap.org/listinfo/osmf-talk</a><br clear="none"></div><br clear="none"><br clear="none"></div> </blockquote> </div></div><div class="yiv9156747621yqt6069743096" id="yiv9156747621yqtfd14099"> </div></div><div class="yiv9156747621yqt6069743096" id="yiv9156747621yqtfd02602"> </div></div></div></body></html>