<br><br><div class="gmail_quote">2011/6/23 <span dir="ltr"><<a href="mailto:jr.morreale@enoreth.net">jr.morreale@enoreth.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Is this fork going to stay in sync with gvsig's trunk or is it going its own seperate path ? I thought that after last year's talks about differences between your OA edition and the official (but not public) tree the situation would have improved.</blockquote>
<div><br>What are you referring to with the "not public" tree?<br>Benjamin will answer officially, but the CE edition will try to keep the sync with the official trunk. At now the CE trunk contains a gvSIG 1.9 snapshot (the same of the OADE edition), but will be upgraded soon to gvSIG 1.11, which is the latest release.<br>
A critical moment will be the release of gvSIG 2.0, which will be a deep refactoring of the core code structure. When it will happen the development and maintanance forces should be split between the 1.1x series and the new... I cross my fingers!<br>
<br>giovanni<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div class="h5"><br>
<br>
On Thu, 23 Jun 2011 09:21:25 +0100 (BST), Benjamin Ducke wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Paolo (all) --<br>
<br>
----- Original Message -----<br>
<br>
[SNIP]<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I didn't like their development model: AFAICT, there is a commercial<br>
association of all gvsig devs; this has a strong potential for a<br>
monopoly.<br>
</blockquote>
<br>
That's precisely why a number of users and external developers,<br>
including myself, have now forked off the gvSIG Community Edition (CE).<br>
<br>
We are still in the process of building up the web infrastructure,<br>
but the mailing lists are already active and you can read up on<br>
progress in the list archives (the most active one is currently<br>
the "community" list):<br>
<br>
<a href="http://sourceforge.net/projects/gvsigce/" target="_blank">http://sourceforge.net/<u></u>projects/gvsigce/</a><br>
<a href="http://sourceforge.net/mail/?group_id=343517" target="_blank">http://sourceforge.net/mail/?<u></u>group_id=343517</a><br>
<br>
Cheers,<br>
<br>
Ben<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
______________________________<u></u>_________________ Qgis-developer mailing<br>
list <a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/qgis-<u></u>developer</a><br>
</blockquote>
<br>
<br>
------<br>
Files attached to this email may be in ISO 26300 format (OASIS Open<br>
Document Format). If you have difficulty opening them, please visit<br>
<a href="http://iso26300.info" target="_blank">http://iso26300.info</a> for more information.<br>
<br>
______________________________<u></u>_________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/qgis-<u></u>developer</a><br>
</blockquote>
<br></div></div>
______________________________<u></u>_________________<div><div></div><div class="h5"><br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/qgis-<u></u>developer</a><br>
</div></div></blockquote></div><br><div style="visibility: hidden; left: -5000px; position: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-top: 0px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 130%;" id="avg_ls_inline_popup">
</div>