Difference between revisions of "GvSIG Incubation Status"

From OSGeo
Jump to navigation Jump to search
m (added myself as project contact)
Line 9: Line 9:
 
: [[User:Ticheler|Jeroen Ticheler]] has been assigned as incubation mentor.
 
: [[User:Ticheler|Jeroen Ticheler]] has been assigned as incubation mentor.
 
: [[Jorge Sanz]] has been assigned by the gvSIG project as formal contact with the project.
 
: [[Jorge Sanz]] has been assigned by the gvSIG project as formal contact with the project.
 +
 +
There's a [https://forge.osor.eu/pm/task.php?group_id=89&group_project_id=317 task repository] for the icubation process at the OSOR.eu forge.
  
 
== Infrastructure Transition ==
 
== Infrastructure Transition ==

Revision as of 05:23, 14 December 2009

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 Tracs, SVN repositories and so on. gvSIG Technical Committe considers at this moment that gvSIG infrastructure should be managed with project servers set up on 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 English official webpage
There is an info sheet at OSGeo web page
Is the OSGeo bug tracker being used for the project?
No, gvSIG at this time is using an internal instance of Trac, but is giving credentials for anyone who asks for them.
Instead of 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 ve 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 has its own server at http://subversion.gvsig.org anonymously accesible
There is also a viewvc interface to navigate the repository at http://subversion.gvsig.org/viewvc
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/

Community Functioning

Is there a functioning user support mechanisms (ie. mailing list)?
gvSIG has a mailing lists page that refers mainly to three public lists: two Spanish spoken for users and developers and another International mailing list where English is preferred. There is also an Italian mailing list that is being managed by our Italian community.
Are source and binary downloads for the package available?
In the 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 Project 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.
Not yet, the gvSIG portal is being restructured and the organizational aspects will be published as part of this refactoring. There is also a «how to participate» page on the gvSIG portal.
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 and 4th gvSIG Conference.
Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
Not yet, as we are going to build a new website, we will try to expose OSGeo collaboration as much as possible.

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
Have issues raised in the provenance review been adequately addressed?
indicate outstanding issues.
Are Commiter Responsibilities Guidelines covering legal issues in place?
yes/no - point to the guidelines and indicate if it is adopted by PSC, and accepted by all commiters.