[Incubator] gvSIG incubation status

[Jorge Gaspar Sanz Salinas]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

First, sorry for the delay to answer Arnulf call, we've been very busy
these last weeks preparing a developers workshop on gvSIG 2.0 new
features that ended last Friday.

gvSIG started OSGeo incubation at September 2007. On that two years
we've been opening more and more our development community from just
publishing the sources on every release to the current situation, where
the code repositories are available[1] and every binary build we produce
is being published through our community portal[2][3] (and HTTP/FTP i.e.
[4]) including all the bugs, tasks and notes resolved for any of them.

The incubation page[12] is updated, including some notes about the
technical committee[5].

We're moving all our contents from the official page[6] hosted on the
CIT servers to the community portal[2], after that process all the
procedures and protocols of how gvSIG is managed will be published. Not
only of how gvSIG is managed from the technical point of view but also
for testing, translating, documenting and so on.

In fact gvSIG project has developed an specific Plone product[7] for
that purpose (also a i18n product[8] manage the translation the gvSIG
interface to any language has been developed).

Related with the incubation, the bug database[9] (using Trac) at this
time is not accessible to anonymous full search but we provide access
for anyone is asking for it. The reason is that we want to offer the bug
database through our portal, independently if its hosted on a Trac
instance or maybe a GForge one (gvSIG team is studying to move the
collaborative infrastructure to OSOR.eu[10]).

In short, the front-end for the bug database is being developed and at
this time is only accessible for listing tickets of an specific build
(you can click on "Bugs corregidos en esta version" on [3] and a list of
bugs will be reported, we are going to translate all this front-pages
but not the bug database).

About the code review. On gvSIG 2.0 we're moving to maven building tool,
with it we have more control over the dependencies any library or
extension has (i.e. [11]) and we've also configured some rules to detect
when a source code doesn't have the correct header.

This is just the first step to start detecting problems in our code base
(with more than 800K lines) that we plan start after publishing the 2.0
release.

I realize that more feedback between OSGeo and gvSIG is needed, we (me
or any other gvSIG team member) will always answer to any question that
arises.

Cheers

[1] http://subversion.gvsig.org/viewvc
[2] http://gvsig.org
[3] https://gvsig.org/web/projects/gvsig-desktop/devel/gvsig
[4]
http://downloads.gvsig.org/pub/gvSIG-desktop/devel/gvSIG-1_9/gvSIG-1_9_0/
[5] http://wiki.osgeo.org/wiki/GvSIG_Technical_Project_Committee
[6] http://www.gvsig.gva.es
[7] https://forge.osor.eu/projects/gvsig-bpd/
[8] https://forge.osor.eu/projects/gvsig-i18n/
[9] https://gvsig.org/trac/bugtracking
[10] http://www.osor.eu/
[11]
http://downloads.gvsig.org/pub/gvSIG-desktop/docs/reference/org.gvsig.fmap.dal.db/2.0.0/dependencies.html
[12] http://wiki.osgeo.org/wiki/GvSIG_Incubation_Status

- --
Jorge Gaspar Sanz Salinas
Ingeniero en Geodesia y Cartografía
http://www.prodevelop.es
tfno: +34 963 510 612


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEcBAEBAgAGBQJKUbjbAAoJEAOYD75lvHdB2wsH/0UDaZbPK3go49oLR2OySJYy
87NJMXsP5mANeuKxM0ftO0C7SCZ7YzJCulrSTR1kKcsqTtTeYyEIbiy13GFAcZhb
X61Adn5Y6r/SDZWuw3GxoTx4wQTXfY1sPFnBTpZ4d3unWlaaxA/P6YC+cpp0AG/+
/Ct6MreOgDt9Xyej3BGRDt5Mhx3WqRpVWw2ciy++tYrWT4v5DhiFBUNN0skyOxwd
l4r/ya1iRmvnixspoxg7BzPF14ZxsjoJtmncQMnHoGz2Dr4Rv0db3sy6FLASnSAc
WU8R02/gDudB92WrjKxXaYy0eV/aSDUZkqQfnCOlXQVyqhSAT2hymoe1EIQBENQ=
=G8IV
-----END PGP SIGNATURE-----