<div dir="ltr">Hi all. For us -users, the Community- the solution adopted by the gvSIG Association (merging all geoprocesses managers in one) is a very good one, and probably the best. We only have to get used to it and soon it will be assimilated in the way we deal with the software.<div style>
Cheers,</div><div style>Sergio</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/6/4 Fernando González <span dir="ltr"><<a href="mailto:fergonco@gmail.com" target="_blank">fergonco@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Álvaro, I only want to counterargument two or your arguments:<br>
<br>
- the bus factor[1] of SEXTANTE is not as high as you think. Indeed,<br>
Ben Ducke is working hard on it and he was not involved at the<br>
beginning of the project, and this is meaningful. Additionally to the<br>
number of developers, the complexity of the software has to be taken<br>
into account and SEXTANTE is indeed quite simple. Finally, the work<br>
required in SEXTANTE now is mainly maintenance and improving the<br>
connections with grass (actually Ben's work).<br>
<br>
- Arguing that the code is hosted in gvSIG CE repository sounds weird.<br>
In the end the code is hosted at sourceforge and we haven't denied yet<br>
anyone of write access that I know.<br>
<br>
Cheers.<br>
<br>
<br>
<br>
[1] <a href="http://en.wikipedia.org/wiki/Bus_factor" target="_blank">http://en.wikipedia.org/wiki/Bus_factor</a><br>
<div class="HOEnZb"><div class="h5"><br>
On Tue, Jun 4, 2013 at 12:46 PM, Alvaro Anguix <<a href="mailto:aanguix@gvsig.com">aanguix@gvsig.com</a>> wrote:<br>
> Hello Wolfgang,<br>
><br>
> Allow me to dedicate some lines to answer you to explain the current<br>
> situation and the planned one at the gvSIG Association in reference to<br>
> the geoprocessing manager in gvSIG.<br>
><br>
> The geoprocessing tools are a very important part of a GIS. Until the<br>
> 1.x version gvSIG included two geoprocessing managers, one of them was<br>
> belonging to gvSIG and the other one was the Sextante library, together<br>
> with other geoproceses available for the user from several menus/buttons.<br>
><br>
> On one hand, in order to improve the usability that we started in gvSIG<br>
> 2.0, we dealt with the option to have an unified geoprocessing manager,<br>
> where the user can find any geoprocess available in gvSIG. And our first<br>
> objective, from the point of view of the product, we had to include all<br>
> the geoprocessing tools of the gvSIG 1.x versions for the users. For<br>
> that, in gvSIG 2.0 you can find the geoprocessing tools from the "old"<br>
> gvSIG geoprocessing manager (clip, buffer, union...), the raster<br>
> geoprocesses of gvSIG, and the geoprocessing tools from the Sextante<br>
> library.<br>
><br>
> On the other hand, we had to solve the technical issues attending to a<br>
> main element for us, not only technical, and it's the issue that I think<br>
> it can explain the current situation better and where we want to go to.<br>
> The dependency of a library maintained almost in an individual mode is<br>
> always a risk, in its evolution we can see that the person who maintains<br>
> it currently is doing it voluntarily -not in its java version- and he<br>
> specified that he abandoned it. Also the maintenance of its java version<br>
> is transferred to a fork of gvSIG that has a dynamics very different to<br>
> our ones in reference to the software development, and that doesn't take<br>
> care of past requests as basic (in my opinion) as they change its name<br>
> and don't use the "gvSIG" word. Apart from the path followed by Sextante<br>
> as a project/s, some decisions were taken previously -by one or the<br>
> other part- that were making difficult the collaboration. For us some<br>
> important decision like the change of the license or the integration on<br>
> ArcGIS led us to take decisions for not spending in Sextante and that<br>
> any geoprocess that we develop on gvSIG was always licensed GPL.<br>
><br>
> At this way, the collaboration between gvSIG and Sextante has been more<br>
> complicated to carry out and the interpretations about how to develop an<br>
> open source project have taken different ways. All of them lawful and<br>
> respectable, of course. But this general outlook was analysed by us<br>
> attending mainly to the project that we want to build, more over the<br>
> product.<br>
><br>
> We return to the main factor to solve. With the objective to build a<br>
> professional software development model, it was non-viable to have a<br>
> dependency with the aforementioned conditions. Our goal is to solve this<br>
> dependency and to be independent to progress the gvSIG geoprocessing<br>
> manager attending to our needs as a project and, in conclusion, the<br>
> needs of our community. Our first step, returning to the beginning, is<br>
> that the users had the geoprocessing tools in gvSIG 2.0 from the beginning.<br>
><br>
> Best,<br>
> Alvaro<br>
><br>
> El 03/06/13 17:13, Wolfgang Qual escribió:<br>
>> Dear all,<br>
>><br>
>> does anybody know whether sextante will be included in gvSIG 2.0?<br>
>> I am a bit worried since I read that sextante seems to concentrate on qgis<br>
>> now [1].<br>
>> Any comments are appreciated!<br>
>><br>
>> Best,<br>
>> Wolfgang<br>
>><br>
>> [1] <a href="http://www.sextantegis.com/java.html" target="_blank">http://www.sextantegis.com/java.html</a><br>
>><br>
>><br>
>><br>
>> --<br>
>> View this message in context: <a href="http://osgeo-org.1560.x6.nabble.com/gvSIG-2-0-and-sextante-tp5057501.html" target="_blank">http://osgeo-org.1560.x6.nabble.com/gvSIG-2-0-and-sextante-tp5057501.html</a><br>
>> Sent from the gvSIG users mailing list archive at Nabble.com.<br>
>> _______________________________________________<br>
>> Gvsig_internacional mailing list<br>
>> <a href="mailto:Gvsig_internacional@listserv.gva.es">Gvsig_internacional@listserv.gva.es</a><br>
>><br>
>> To see the archives, edit your preferences or unsubscribe from this mailing list, please access this url:<br>
>><br>
>> <a href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional" target="_blank">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</a><br>
>><br>
><br>
> _______________________________________________<br>
> Gvsig_internacional mailing list<br>
> <a href="mailto:Gvsig_internacional@listserv.gva.es">Gvsig_internacional@listserv.gva.es</a><br>
><br>
> To see the archives, edit your preferences or unsubscribe from this mailing list, please access this url:<br>
><br>
> <a href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional" target="_blank">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</a><br>
_______________________________________________<br>
Gvsig_internacional mailing list<br>
<a href="mailto:Gvsig_internacional@listserv.gva.es">Gvsig_internacional@listserv.gva.es</a><br>
<br>
To see the archives, edit your preferences or unsubscribe from this mailing list, please access this url:<br>
<br>
<a href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional" target="_blank">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</a><br>
</div></div></blockquote></div><br></div>