<div class="gmail_quote">On Wed, Aug 4, 2010 at 4:05 PM, Richard Weait <span dir="ltr"><<a href="mailto:richard@weait.com">richard@weait.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Wed, Aug 4, 2010 at 9:00 AM, 80n <<a href="mailto:80n80n@gmail.com">80n80n@gmail.com</a>> wrote:<br>
> If there is anything under development it would be good if we could see it.<br>
> It is unlikely to be a trivial piece of code and I'd be very surprised if it<br>
> can be developed by September 1st if it hasn't already been started.<br>
<br>
</div>You've referred to your arbitrary September first deadline several<br>
times. When did you first suggest September first had some<br>
significance? It was weeks ago.<br>
<br>
The LWG, OSMF Board, and implementation plan have no September first<br>
deadline of which I am aware.<br></blockquote><div><br>Richard<br>Without a deadline the re-licensing process will drag on interminably. And due to the Phase I changes which have already been implemented it would eventually succeed through a process of attrition. That is not a fair way of achieving a license change and will be challenged by the community.<br>
<br>I'm sorry if you haven't been informed about it but September 1st represents a reasonable timeframe, based on the currently published implementation plan [1], to establish a consensus from the community about the license change. Failure to achieve an unarguable majority by then, using any reasonable measure, will kill the license change process.<br>
<br>There have been calls for some kind of community vote and this has led to questions about what kind of data loss impact there would be. So the tools referred to in this thread are necessary to measure the impact of a vote. Without the tools and without the vote the license change process would just keep lumbering on and continue to damage the project. Even Steve realises this now [2].<br>
<br>There is very little that can stand in the way of the overwhelming success of OSM. It's a superbly constructed approach with no single point of failure. One of the worst things that could happen is for the license change process to continue to undermine and damage it for another two or three years. It needs to be brought to a conclusion rapidly.<br>
<br>80n<br><br>[1] <a href="http://wiki.openstreetmap.org/wiki/Open_Data_License/Implementation_Plan#Current">http://wiki.openstreetmap.org/wiki/Open_Data_License/Implementation_Plan#Current</a><br>[2] <a href="http://opengeodata.org/the-false-dichotomy-osm-as-open-or-closed">http://opengeodata.org/the-false-dichotomy-osm-as-open-or-closed</a> (the opaqueness of the ODbL and the proposed Contributor Terms will be excellent ammunition for the threats that Steve sees).<br>
<br><br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
I don't recognize anything significant about your arbitrary deadline<br>
but it seems to be important to you. I'm pretty sure that the<br>
implementation plan currently calls for more time than the calendar<br>
provides between now and September first. Avoid the rush. Consider<br>
your arbitrary marker to be passed. Now what? You declare failure?<br>
<div><div></div><div class="h5"><br>
_______________________________________________<br>
legal-talk mailing list<br>
<a href="mailto:legal-talk@openstreetmap.org">legal-talk@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/legal-talk" target="_blank">http://lists.openstreetmap.org/listinfo/legal-talk</a><br>
</div></div></blockquote></div><br>