[Gvsig_english] gvSIG project structure

[Benjamin Ducke]

Hi Jose

this would be just a temporary solution for work based on the
"dead" 1.9 codebase. Hopefully, somewhere along the 2.X line
we will be able to merge everything back into one codebase
and there will be no more need for any branching.
It will be much easier to integrate external developers'
contributions into a "live" codebase.

Also, as far as bug fixing and extensions are concerned,
there is no problem and no need for any branches.

Cheers,

Ben

----- "José Antonio Canalejo Alonso" <jacanalejo at yahoo.es> schrieb:

> Hello Ben,
> working together but keep an OADE branch?? I can't understand that.
> What kind of "working together" is that? Without gvSIG is not possible
> to have gvSIG OADE.
> gvSIG needs to have a larger number of external contributors working
> together on the same project but not in different ones. There are now
> several external contributors working on the same project: gvSIG . Why
> should it be different with OADE? This approach seems not to be right
> :(
> Regards
> Jose
> 
> 
> --
> José Antonio Canalejo Alonso
> CSGIS
> Email:jose.canalejo at csgis.de
> Web: http://www.csgis.de
> 
> 
> 
> 
> 
> De: Benjamin Ducke <benjamin.ducke at oxfordarch.co.uk>
> Para: Users and Developers mailing list
> <gvsig_internacional at listserv.gva.es>
> Enviado: sáb,27 marzo, 2010 12:56
> Asunto: [Gvsig_english] gvSIG project structure
> 
> 
> ----- "Luis W. Sevilla" < lsevilla at sigrid.es > schrieb:
> 
> > Hi Ben, Jorge (community),
> > I have null interest in perform or participate in a flame war.
> 
> I think we can all agree on that!
> 
> [SNIP]
> 
> > point, but an abstract could be: Big changes in project
> > management/driving could be done before gvSIG could be considered an
> > open project. It's free software, and collaborative. But not open
> > because there's no openness in project decision taking, not
> > transparency.
> >
> 
> So maybe for the immediate future, as regards gvSIG and gvSIG
> OADE, one approach would be to work very closely together regarding
> bug fixes, but keep an OADE branch for other changes such as GUI
> design decisions, that are not of critical importance but more a
> matter of "taste" or workflow habits.
> 
> I will have to think about some possible options for a while and
> will get back to you with some suggestions in the "gvSIG 1.9.1"
> message thread.
> 
> I think in the long term, this closed decision making will have
> to be reconsidered if gvSIG is to attract a larger number of
> external contributors. Eventually, there should be a way for
> anyone with the right skills to become part of the decision
> making group. But that is an issue that can probably wait for
> discussion until the right time comes.
> 
> Best wishes,
> 
> Ben
> 
> 
> 
> 
> _______________________________________________
> Gvsig_internacional mailing list
> Gvsig_internacional at listserv.gva.es
> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional


------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.