This discussion could continue endlessly until both the communities will give evidence of their reasons.<br><br> - Official gvSIG: next months a new collaboration workflow, and new paths for the community involvemtn should come out. I really hope it, and we'll be able to evaluate their reasons when this will happen. We know about the effort the TSC team is doing under the covers. It's hard to make it visible and recognizable... but it will happen when things will be born.<br>
- gvSIG CE: no Association, more freedom to contribute, simpler collaboration mehanisms. gvSIG CE has a lighter organization that maybe can help this process. We'l see if a "lighter" community will be able to sustain the efforts required to mantain an indepenent fork and support the community at the same time.<br>
<br>The reasons are very similar. We'll see who will be the first to be able to respond, and mantain a winning equilibrium, between the many requests ;)<br><br>giovanni<br><br><div class="gmail_quote">2011/6/28 Jorge Gaspar Sanz Salinas <span dir="ltr"><<a href="mailto:jsanz@gvsig.com">jsanz@gvsig.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">El 27/06/11 10:47, Simon Cropper escribió:<br>
> Hi Everyone,<br>
><br>
> I have recently joined the CE Maillist and posted the following<br>
> question. As it pertains to both this list and that list I am also<br>
> posting it here...<br>
><br>
> *** POST ***<br>
><br>
> Why is gvSIG CE here? To me the reason for its creation is unclear.If<br>
> you intend to encourage adoption then the distinction between these<br>
> gvSIG and gvSIG CE needs to be clarified.<br>
><br>
> The OADE version and the original code was finally remerged creating a<br>
> single code base in 2010 and next thing I see is that the code is split<br>
> into two projects again.<br>
><br>
> Personally I find it hard to decide where to place my attention /<br>
> allegiances. I have spent over a year getting data and building my<br>
> website to house my tutorials (most of which will be on gvSIG) and now I<br>
> have two separate projects, GUI and communities. Do I stick with the<br>
> original program/community or the new CE one? The same dilemma I had<br>
> when considering creating tutorials for the OADE versus the original<br>
> program.<br>
><br>
> The same indecision will, no doubt, be in the minds of any new comer<br>
> looking at adopting the software.<br>
><br>
> As a general observation -- the gvSIG community appears to be<br>
> splintering as various groups try and drag the project in different<br>
> directions.<br>
><br>
> This is in contrast to say the QGIS community that over the last year<br>
> appears to be growing in strength and pooling resources.<br>
><br>
<br>
Hi Simon,<br>
<br>
gvSIG is a place where everyone can contribute as you can state by your<br>
own history. Not just patches but also documentation, translations, case<br>
studies, artwork and so on. That's happening everyday, no matter what<br>
others say.<br>
<br>
On the development side where are continuously improving our workflows,<br>
the balance between being agile or quick and being very conscious about<br>
stability, GUI consistency and so on is not easy. Our Technical Steering<br>
Committee (which mailing list is open to everyone) are finishing a<br>
document about code contributions workflows and roles.<br>
<br>
So my first point is about to confirm that the whole gvSIG team is<br>
focused on the community, all the time, since the beginning of the<br>
project. Of course everything can be improved, but stating elsewhere<br>
that gvSIG team doesn't collaborate is a non-sense.<br>
<br>
If a group of users or developers want to follow another path we cannot<br>
do anything against that, apart to try to understand the real reasons of<br>
their fork. I personally did that on the CE list asking openly what the<br>
gvSIG team can do to reorient the CE group to other kind of activity<br>
instead a fork and I didn't get any answer. On the same way that group<br>
didn't discussed here about their intentions or concerns before starting<br>
their initiative. They just decided by themselves that the idea was ok<br>
and now they say they are more open oriented than the gvSIG team. Cool.<br>
<br>
Even the name, in my opinion is perverse. They are the Community Edition<br>
and we are... what?? They insist on the "CIT gvSIG" name that is also<br>
wrong. gvSIG is a project born at CIT, and everyone should be proud of<br>
CIT encouraging gvSIG but gvSIG is a community project, supported by the<br>
gvSIG Association and thousands of users, developers, companies,<br>
universities and public administrations all around the world.<br>
<br>
Best<br>
<br>
--<br>
Jorge Gaspar Sanz Salinas<br>
gvSIG Team at Prodevelop<br>
Technical Collaborations Manager<br>
<a href="http://www.gvsig.org" target="_blank">http://www.gvsig.org</a><br>
<a href="http://www.gvsig.com" target="_blank">http://www.gvsig.com</a><br>
_______________________________________________<br>
Gvsig_internacional mailing list<br>
<a href="mailto:Gvsig_internacional@listserv.gva.es">Gvsig_internacional@listserv.gva.es</a><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>
</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>