GvSIG Incubation Status

General
You can see the GvSIG incubator application request for more details from the project


 * Has the project been approved for incubation by the OSGeo board?
 * Approved at board meeting on September 7th 2007.


 * Has an Incubation Mentor been assigned to the project?
 * Jeroen Ticheler has been assigned as incubation mentor.
 * Jorge Sanz has been assigned by the gvSIG project as formal contact with the project.

There's a task repository for the icubation process at the OSOR.eu forge.

Infrastructure Transition
Note, for each of the following it isn't necessary to move to foundation infrastructure, but if you aren't a reason should be provided.

gvSIG has a huge infrastructure with several trackers, SVN repositories and so on. gvSIG Technical Steering Committe considers at this moment that gvSIG infrastructure should be managed with project servers set up at OSOR.eu project, the Polythecnic University of Valencia (Instituto Tecnológico de Informática) and in the Valencian Government.


 * Has the projectname.osgeo.org domain been populated with the projects web presence?
 * Yes, http://gvsig.osgeo.org redirects to gvSIG official webpage
 * There is an info sheet at OSGeo web page


 * Is the OSGeo bug tracker being used for the project?
 * No, there is an OSOR.eu gvSIG desktop project with main public trackers for bugs, feature requests, binary build announces, etc.
 * Besides publishing directly the bug database, for every new build of gvSIG, there is a list of bugs resolved, tasks and features. Any of them can be viewed through the portal navigating from https://gvsig.org/web/projects/gvsig-desktop/devel/
 * gvSIG team is working to present a complete interface on the bug database through its portal, but it's a work in progress.


 * Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project?
 * No, the project has its own mailing list server. Additionally, gvSIG mailing lists are archived at nabble under OSGeo projects (also on gmane and mail-archive.com).


 * Is the OSGeo SVN being used for the project?
 * No, the project is using mainly the OSOR.eu gvSIG Desktop SCM.


 * Are binary and source downloads available from http://download.osgeo.org ?
 * Yes, the gvSIG download server is linked through the OSGeo front page
 * The gvSIG download server is accessible through http, ftp and rsync at http://downloads.gvsig.org/
 * Nowadays we are migrating all gvSIG downloads to http://gvsig-desktop.forge.osor.eu/downloads/

Community Functioning

 * Is there a functioning user support mechanisms (ie. mailing list)?
 * gvSIG has a mailing lists page that refers to several public lists for users, announcements and developers (in English and Spanish) but also for build announcements and for the Italian an Brazilian communities. All those lists are also archived at Nabble under the OSGeo project forum and in Gmane and mail-archive.com.


 * Are source and binary downloads for the package available?
 * At downloads area of gvSIG website you'll find any binary and source code released from 0.3 version up to current release. The internal builds are also published on the community portal. Every build has it's corresponding tag a the svn server.


 * Has a Project Steering Committee been formed, and given control of the project?
 * Yes, during spring of 2008 a gvSIG Technical Steering Committee has been formed. It's a group of relevant people from the project and there's an executive sub group who is responsible of the final decisions. Briefly, the Technical Comittee is based on workgroups, working on enhancement or change proposals that the executive committee has to approve. There's also a coordinator for the committee, Jorge Sanz, who is also in charge of the incubation of gvSIG in OSGeo.


 * Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
 * TSC is described at this wiki and at gvSIG portal.
 * There is also documentation about the TSC regulation, how to contribute and what gvSIG official projects are.
 * The TSC has a public mailing list where the group discuss. The agendas and minutes of all meetings and proposals are also available and reported on this list and publicly available.


 * How many active developers are there? Are they from multiple organizations?
 * At this moment, and according to gvSIG Desktop and gvSIG mobile ohloh stats, there are more or less 35 people committing code to the svn server. Besides that, there are also 30 or 40 people working on documentation, testing and project management.
 * They are all from several companies, universities and public administrations.

Foundation Membership

 * Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
 * Yes, the current main web site reflects the OSGeo incubation, it has been reported on the mailing lists and several reports and OSGeo appears as Collaborator organization for the 3rd gvSIG Conference, 4th gvSIG Conference, 5th gvSIG Conference and 6th gvSIG Conference.


 * Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
 * No, we are placing the OSGeo logo and doing as much promotion as we can of OSGeo at gvSIG events and gvSIG team is also participating at OSGeo planet but we are not willing to re-style our website with OSGeo guidelines (in the gvSIG portal has just the Plone default skin).

Code Copyright Review

 * Has a Code Provenance Review document been prepared for the project?
 * No at this moment, there is a GvSIG Provenance Review empty at this time. This process is stalled until gvSIG Desktop 2 is released due to the lack of resources.


 * Have issues raised in the provenance review been adequately addressed?
 * A tracker for incubation tasks has been created.


 * Are Commiter Responsibilities Guidelines covering legal issues in place?
 * We are stablishing a CLA protocol. At this time most of the code is owned directly by the project and we will request to sign the CLA to past and new code contributors.