OSGeo - User contributions [en]

GvSIG Incubation Checklist

2015-08-06T07:04:10Z

Wiki-Mmadrid: /* Copyright and License */

= Document Status =

'''Version''': 2.0

'''Last Updated''': June 2015.

'''Status''': Draft

= Purpose =

The purpose of this checklist is to determine whether an Incubator Project produces quality products, remains true to its stated licence and is sustainable. Satisfying this checklist is a pre-requisite for graduation.

A project should have institutionalized the processes in this list or provide justification why the process is not used.

See also:

* [http://www.osgeo.org/incubator/process/application.html Incubation Application Questionnaire]
* [http://www.osgeo.org/incubator/process/statustemplate.html Project Status Template]

= Terms and Definitions =

; Mentor : A member of the Incubation Committee chosen to assist a Project through the Incubation Process.
; Institutionalized Process : A documented process which which addresses a need and is actively in use. It typically takes months before a process becomes institutionalized. ''A more detailed definition of institutionalization is found in the [http://www.sei.cmu.edu/pub/documents/02.reports/pdf/02tr012.pdf Capability Maturity Model (CMMI)] - "Generic Goal 2: Institutionalize a Managed Process"''
; Open Source License : a license recognized by the [http://opensource.org Open Source Initiative]

= Incubation Checklist =

== Open ==

The project has demonstrated that it has an open, active and healthy user and developer community:
# Open: projects are expected to function in an open and public manner and include:
#* Open source license(s), '''yes: gvSIG is developed under GNU/GPL version 3 license'''
#* Open communication channels, '''yes: there are several users and developers mailing lists in different languages (http://www.gvsig.com/en/community/mailing-lists). There's also a mail address (info@gvsig.com), a phone number (0034-961110070) and a fax number (0034-901021995)'''
#* Open decision making process, '''yes: Public mailing list of the gvSIG Technical Steering Committee (TSC) (http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub). There's a roadmap with the decisions taken by the board of the Technical Steering Committee: https://redmine.gvsig.net/redmine/projects/gvsig-cdt-board/roadmap. A post is published after every version of gvSIG with the novelties of the next one.''' The information on the gvSIG Technical Steering Committee can be found at http://wiki.osgeo.org/wiki/GvSIG_Technical_Steering_Committee
# Active and healthy community: '''yes, there's an active community of users and developers from multiple countries at the world.'''
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. ''' yes. Users and developers use mailing lists for collaboration and supporting. There are four main mailing lists (in Spanish and English, for developers and for users) and there are also local mailing lists (in different languages or for different areas, like Argentina, Brazil, Italy or Russia among others). For mailing list activity visit: http://osgeo-org.1560.x6.nabble.com/gvSIG-project-f4102529.html Users and developers use the tracker for uploading the errors in gvSIG (https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues). There are a lot of testers at the community, and there's group of translators, who translate documentation and interface. There are developers that provide patches, new developments, and scripts (at the scripting repository: http://outreach.gvsig.org/scripts/). There's also a web portal for the gvSIG case-studies provided by the community (http://outreach.gvsig.org/case-studies).''' Eg. collaboration on project activities such as testing, release and feature development.
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. '''yes. There are multiple developers from different organizations. The community is participating actively on the development. The commits by developer at the core, the main project, are shown in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/repository/statistics. There are also different sub-projects for the different extensions with their own commits: https://redmine.gvsig.net/redmine/projects. The activity of the project every day is in: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/activity. The gvSIG project is managed by the gvSIG Association, that is composed of four associate companies and more than 40 collaborating companies, as well as different public entities (governments, technical institutes...) and universities. ''' Eg. The project is resilient enough to sustain loss of a developer or supporting organization, often referred to as having a high [http://en.wikipedia.org/wiki/Bus_factor bus factor]. Decisions are made openly instead of behind closed doors, which empowers all developers to take ownership of the project and facilitates spreading of knowledge between current and future team members.

== Copyright and License ==

We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:
# All project source code is available under an Open Source license. '''Yes, gvSIG is developed under GNU/GPL version 3 license. All the source code of the different versions is in https://devel.gvsig.org/svn/gvsig-desktop/'''
# Project documentation is available under an open license, such as Creative Commons. '''Yes. The documentation is under Creative Commons 3.0 CC BY-SA license (there are workshops, tutorials and manuals). They are available in http://www.gvsig.com/. There's a Youtube channel with a lot of videos about the project too: https://www.youtube.com/user/gvsig. All the presentations of the gvSIG Conferences are available too, and the videos are published when they are recorded. There are articles, books and posters about the project compiled at the gvSIG web portal. http://www.gvsig.com/en/diffusion'''
# The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included, as per a [http://www.osgeo.org/incubator/process/codereview.html Provenance Review]. '''Yes. All the information is vetted before publishing (manuals, source code, cartography...). See the gvSIG Code Provenance Revew at http://docs.gvsig.org/plone/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/provenance-review'''
# The project maintains a list of all copyright holders identified in the Provenance Review Document. '''No, as all the source code is owned by the gvSIG Association. All the developers have signed the CLA (http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status). '''
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status'''

== Processes ==

# The project has code under configuration management. '''Yes: the main svn is in https://devel.gvsig.org/svn/gvsig-desktop''' Eg, subversion, git.
# The project uses an issue tracker and keeps the status of the issue tracker up to date. '''Yes: The main project is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues. gvSIG is composed of different sub-projects or extensions: https://redmine.gvsig.net/redmine/projects with their own trackers.'''
# The project has documented its management processes. '''Yes. There are different documents for the different areas'''
#* GvSIG Technical Steering Committee: '''http://wiki.osgeo.org/wiki/GvSIG_Technical_Steering_Committee'''
#* Suggesting new features: '''https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues/new'''
#* Developing contributions: '''http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig'''
#* Commiters guide: '''http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-commiters-de-gvsig'''
#* Developers guide: '''http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide'''
#* Documentation guide:''' http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-documentar'''
 This is typically done within a Developers Guide or Project Management Plan.
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. '''Yes: there's a Technical Steering Committee (TSC) http://docs.gvsig.org/web/working-groups/organizacion. There's a roadmap with the decisions taken by the board of the Technical Steering Committee: https://redmine.gvsig.net/redmine/projects/gvsig-cdt-board/roadmap''' This typically means a Project Management Committee has been established with a process for adding new members. A robust Project Management Committee will typically draw upon developers, users and key stakeholders from multiple organizations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.
#* The project uses public communication channels for decision making to maintain transparency. '''Yes: Archives of the TSC mailing list http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub. The road map for the following versions of the application, with the changes, is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/roadmap.''' E.g. archived email list(s), archived IRC channel(s), public issue tracker. 

== Documentation ==

# The project has user documentation: '''Yes: User documentation is available in http://www.gvsig.com/en/products/gvsig-desktop/documentation. There are workshops, tutorials, posters, articles, presentations and books in http://www.gvsig.com/en/diffusion. There's a Youtube channel with a huge quantity of videos about the project too: https://www.youtube.com/user/gvsig.'''
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.
# The project has developer documentation: '''Yes: Developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development'''
#* Including checkout and build instructions. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/trabajar-con-el-nucleo-de-gvsig/compile_gvsig'''
#* Including commented code, ideally published for developer use. '''Yes: maven site of main project http://devel.gvsig.org/sites/org.gvsig.desktop/2.0.17/''' Examples: javadocs for Java applications, or Sphinx documentation for Python applications.
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions. '''Yes: It's available at the developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development'''

==Release Procedure==

In order to maintain a consistent level of quality, the project should follow defined release and testing processes.

# The project follows a defined release process: '''yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/release-guide'''
#* Which includes execution of the testing process before releasing a stable release. '''yes, there's a testing procedure available for gvSIG, which is a workshop with the cartography: http://docs.gvsig.org/plone/docusr/doctesting/interesting-links-for-testers/view'''
# The project follows a documented testing process. '''There's also a quick testing process for an initial test: http://downloads.gvsig.org/download/testing/testgvSIG_en.pdf ''' This includes manual testing 
# Release and testing processes provide sufficient detail for an experienced programmer to follow. '''Yes, it's available at the documentation section for developers: http://www.gvsig.com/en/products/gvsig-desktop/development'''.

= OSGeo Committees and Community =

The OSGeo Foundation is made up of a number of committees, projects and local chapters. This section gathers up information these groups have requested from OSGeo projects. These expectations are not mandatory requirements before graduation, but a project should be prepared to address them in order to be considered a good OSGeo citizen.

== Board ==

The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:

# A project provide a Project Officer as a contact point: '''Yes'''
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]
#* This person is established when the incubation committee recommends the project for graduation
#* Your community can change the project officer as needed (just add an agenda item to the next board meeting so they can recognise the change of officer).

== Marketing ==

Access to OSGeo's [[Marketing_Committee]] and associated [[Marketing_Pipeline]] is one of the key benefits of joining the OSGeo foundation. The Marketing Committee requests:

# Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's [http://wiki.osgeo.org/wiki/Marketing_Artefacts Marketing Artefacts]. This lists the documentation requirements for [http://live.osgeo.org OSGeo-Live]. Marketing Artefacts include:
#* Application Overview '''Yes. http://live.osgeo.org/en/overview/gvsig_overview.html'''
#* Application Quick Start '''Yes. http://live.osgeo.org/en/quickstart/gvsig_quickstart.html'''
#* Logo '''Yes. http://live.osgeo.org/_images/logo-gvSIG.png'''
#* Graphical Image '''Yes. http://live.osgeo.org/_images/gvsig_desktop.png'''
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. '''Yes: OSGeo-Live.''' In most cases, this will at least include [http://live.osgeo.org OSGeo-Live], but may also include [http://wiki.debian.org/DebianGis DebianGIS], [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS], and/or [http://trac.osgeo.org/osgeo4w/ osgeo4w] [http://www.maptools.org/ms4w/ ms4w], etc.)

== Projects ==

Projects do not exist in isolation; and are expected to communicate and collaborate on key issues.

As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others. gvSIG uses several libraries, like gdal or NASA World Wind, and they are reviewed and updated before releasing the gvSIG versions.

== SAC ==

gvSIG has several mailing lists operating by the OSGeo infrastructure: https://lists.osgeo.org/mailman/listinfo

[[Category: Incubation]]

Manuel Madrid

2015-08-04T09:28:54Z

Wiki-Mmadrid:

Manuel Madrid has worked at the gvSIG project from its very beginning. He has been Product and Testing Manager for five years. He is currently working at the gvSIG Association as Project Manager.

'''email''': mmadrid [at] gvsig [dot] com

2013-09-19T13:34:31Z

Wiki-Mmadrid:

Incubation Status report for Q3 2013.

= Incubation Committee =

No summary

Activities:
* none

= Recent Graduates =

We are tracking recent graduates for a few months to ensure that the correct OSGeo Project logo is rolled out onto the project website, the community is informed, and the OSGeo board has a chance to make a news announcement and appoint a project officer.

[[File:OSGeo project.png]]

* GeoMoose: no formal press release yet? Press Release Draft: http://wiki.osgeo.org/wiki/Board_Press_Release_GeoMoose_Graduates_Incubation
** project displays osgeo project logo, and has announced graduation: http://www.geomoose.org/#geomoose-has-graduated-osgeo-project-incubation

* GeoServer: presse Release: http://www.osgeo.org/news/geoserver-graduation
** Project Announcement: http://blog.geoserver.org/2013/03/18/geoserver-2-3-0-released-first-official-osgeo-release/

= Incubation =

The following projects are following the OSGeo Incubation process.

Relationship with OSGeo:
* Project are expected to display the ''OSGeo Project in Incubation'' logo on their website.
* OSGeo lists these project on the main OSGeo http://www.osgeo.org website.

Relationship with Incubation Committee:
* Each project has a mentor to help answer any questions (very helpful for sensitive subjects that cannot be discussed on an open mailing list).
* Project are expected to link from the [[Incubation_Committee]] wiki to:
** A ''Provenance Review'' document (to confirm they are open source)
** A ''Incubation Checklist'' document (to meet graduation requirements)
* Incubation Committee mailing list is always questions and discussion

[[File:OSGeo incubation.png]]

==gvSIG==

* mentor: Dimitris Kotzinos (taking over from Jeroen Ticheler)
* contact: Manuel Madrid (taking over from Jorge Sanz)
* [[gvSIG Incubation Status]]
* [[gvSIG Provenance Review]]

Status and provenance review updated in September.

==Marble==

* Mentor: [[Arnulf Christl]]
* [[Marble Code Provenance Review]]
* [[Marble Graduation Checklist]]

Provenance review updated in September.

Website at http://www.osgeo.org/marble has been populated.

==MetaCRS==

* mentor: Daniel Morissette
* provenance review not provided
* checklist not provided

No progress to report this quarter, status last updated in 2009.

==Opticks==

* mentor: Mark Lucas
* provenance review not provided
* [http://wiki.osgeo.org/wiki/Opticks_Incubation_Checklist checlist] is at 70%

No progress reported this quarter

==pycsw==

* mentor: [[Jeff McKenna]]
* Status updated July 2013
* provenance review document not provided
* checklist document not provided

No progress reported this quarter.

(Team will assemble documents in the geopython wiki: https://github.com/geopython/pycsw/wiki/OSGeo-Incubation)

==rasdaman==

* mentor: Bruce Bannerman
** [http://www.rasdaman.org/wiki/OSGeoCodeProvenance Rasdaman Code Provenance Review] (done?)
** [http://www.rasdaman.org/wiki/OSGeoIncubationChecklist Rasdaman Incubation Checklist]. (80%)

Progress:

* The project recently appointed a Benevolent Dictatorship, which is not compatible with OSGeo direction for open development. While we can negotiate on the form, a project steering committee is only one example, we do want to ensure that OSGeo projects are open to all willing participants on equal footing.
* Bruce is going to report back in a couple of months.

==TEAM Engine==

* mentor: Justin Deolivera
* no progress to report
* logo not listed on project website (http://teamengine.sourceforge.net)
* Some contact on email, no status or provenance review.

No progress reported this quarter.

==ZOO-Project==

* mentor: Frank Warmerdam
* ongoing [http://www.zoo-project.org/trac/wiki/Provenance%20Review provenance review].
* ongoing [[ZOO-Project_Incubation_Status|status document]].

OSGeo Participation:

* OSGeo Live (>6.0): http://live.osgeo.org/en/overview/zoo-project_overview.html

No progress reported this quarter.

= Labs =

Thanks to Landon Blake for his excellent leadership in reaching out to OSGeo Incubation Lab projects.

* We have extended an invitation to OSGeo Labs projects to participate in the incubation list, as for many routine questions we can help without a dedicated mentor.
* Landon has the idea of setting up resources for community building / project marketing / project governance

===Geoinformatica===

* Website: http://geoinformatics.aalto.fi/software.shtml
* User Mailing List: no
* User Documentation: unknown
* Number of Users: no estimate

OSGeo Participation:

* OSgeo Wiki: [[OSGeo_Labs:_Geoinformatica]]
* OSGeo Live: http://live.osgeo.org/en/overview/pgrouting_overview.html

===pgRouting===

* Website: http://pgrouting.org
* User Mailing List: yes
* User Documentation: unknown
* Number of users: no estimate

OSGeo Participation:

* OSGeo wiki: [[OSGeo_Labs:_pgRouting]]
* OSGeo Live:

===PAGC===

* Website: http://www.pagcgeo.org
* User Mailing List: no
* User Documentation: unknown
* Number of Users: no estimate

OSGeo Participation:

* OSGeo Wiki: [[OSGeo_Labs:_PAGC] (page empty)]
* OSGeo Live:

===MapProxy===

* Website: http://mapproxy.org/
* User Mailing List: http://lists.sourceforge.net/lists/listinfo/pagc-users
* User Documentation: unknown / OSGeo-Live Quickstart
* Number of Users: no estimate

OSGeo Participation:

* OSGeo Wiki: [[OSGeo_Labs:_MapProxy]]
* OSGeo Live: http://live.osgeo.org/en/overview/mapproxy_overview.html

===The SurveyOS KML Toolkit===
* Website:
* User Mailing List: no
* User Documentation: unknown
* Number of Users: no estimate

OSGeo Participation:

* OSGeo Wiki: http://wiki.osgeo.org/wiki/OSGeo_Labs:_The_SurveyOS_KML_Toolkit
* OSGeo Live:

===SlitherGrid===

* Website:
* User Mailing List: no
* User Documentation: unknown
* Number of Users: no estimate

OSGeo Participation:

* OSgeo Wiki: http://wiki.osgeo.org/wiki/OSGeo_Labs:_SlitherGrid (page empty)
* OSGeo Live:

===Virtual Terrain Project===

* Website: http://vterrain.org/
* User Mailing List: no
* User Documentation: unknown
* Number of Users: no estimate

OSGeo Participation:

* OSgeo Wiki: http://wiki.osgeo.org/wiki/OSGeo_Labs:_Virtual_Terrain_Project
* OSGeo Live:

==PyWPS==

* Website: http://pywps.wald.intevation.org/
* User Mailing List: no
* User Documentation: unknown
* Number of Users: no estimate

OSGeo Participation:

* OSGeo Wiki: http://wiki.osgeo.org/wiki/OSGeo_Labs:_PyWPS
* OSGeo Live:

GvSIG Incubation Status

2013-09-19T13:17:12Z

Wiki-Mmadrid:

== 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?
: [[User: kotzino|Dimitris Kotzinos]] took over from [[User:Ticheler|Jeroen Ticheler]] as mentor in April 2013.
: [[User:Mmadrid|Manuel Madrid]] took over from [[User:Jsanz|Jorge Sanz]] as formal contact with the project in March 2013.

There's a [https://devel.gvsig.org/redmine/issues/1719 task ] for the incubation process at the gvSIG infrastructure.

== 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 https://devel.gvsig.org/redmine and http://www.gvsig.org.

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

; Is the OSGeo bug tracker being used for the project?
: No, there is an https://devel.gvsig.org/redmine/projects/gvsig-desktop project with main [https://devel.gvsig.org/redmine/projects/gvsig-desktop/issues trackers] for bugs, feature requests, binary build announces, etc.

; Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project?
: No, the project has its own [https://gvsig.org/web/community/mailing-lists/directory-en/ mailing list server]. Additionally, gvSIG mailing lists are archived at [http://www.nabble.com/gvSIG-f29441.html nabble] under OSGeo projects (also on [http://news.gmane.org/search.php?match=gvsig gmane] and [http://www.mail-archive.com/find.php?domains=www.mail-archive.com&q=gvsig&sa=Search mail-archive.com]).

; Is the OSGeo SVN being used for the project?
: No, the project is using mainly the [https://devel.gvsig.org/svn/gvsig-desktop 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 at http://downloads.gvsig.org/download/

task for
== Community Functioning ==

; Is there a functioning user support mechanisms (ie. mailing list)?
: gvSIG has a [https://gvsig.org/web/community/mailing-lists/directory-en/ 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 [http://www.gvsig.org/web/projects/gvsig-desktop/official downloads area] of gvSIG website you'll find any binary and source code released from 0.3 version up to current release. The [https://gvsig.org/web/projects/gvsig-desktop/devel/view?set_language=en internal builds] are also published on the community portal. Every build has it's corresponding tag a the [https://devel.gvsig.org/svn/gvsig-desktop/tags/ svn server].task for

; 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.

; Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
: TSC is described at [[gvSIG Technical Steering Committee|this wiki]] and at [http://www.gvsig.org/web/organization/about-us/committees/ gvSIG portal].
: There is also documentation about the [http://www.gvsig.org/web/organization/about-us/regulations/ TSC regulation], [http://www.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2.0.0/anexos/contribuciones-y-parches-al-codigo-de-gvsig/contributions-and-patches-to-the-gvsig-code how to contribute] and what [http://www.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2.0.0/anexos/proyectos-oficiales-en-gvsig/gvsig-official-projects gvSIG official projects] are.
: The TSC has a [https://lists.forge.osor.eu/listinfo/gvsig-desktop-tsc-pub 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?
: Can see the developers in the [http://www.ohloh.net/p/gvsig-desktop-2/contributors gvSIG Desktop ohloh web].

== 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 [http://www.gvsig.org 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?
: Yes, there is in [[GvSIG Provenance Review]]

; Have issues raised in the provenance review been adequately addressed?
: A [https://devel.gvsig.org/redmine/issues/1719 task for incubation] has been created.

; Are [[Commiter Responsibilities Guidelines]] covering legal issues in place?
: We are stablishing a [http://www.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2.0.0/anexos/contribuciones-y-parches-al-codigo-de-gvsig/what-is-the-gvsig-cla 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.

[[Category:Incubation]]
[[Category:gvSIG]]

GvSIG Incubation Status

2013-09-19T13:14:16Z

Wiki-Mmadrid:

== 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?
: [[User: kotzino|Dimitris Kotzinos]] took over from [[User:Ticheler|Jeroen Ticheler]] as mentor in April 2013.
: [[User:Mmadrid|Manuel Madrid]] took over from [[User:Jsanz|Jorge Sanz]] as formal contact with the project in March 2013.

There's a [https://devel.gvsig.org/redmine/issues/1719 task ] for the icubation process at the gvSIG infrastructure.

== 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 https://devel.gvsig.org/redmine and http://www.gvsig.org.

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

; Is the OSGeo bug tracker being used for the project?
: No, there is an https://devel.gvsig.org/redmine/projects/gvsig-desktop project with main [https://devel.gvsig.org/redmine/projects/gvsig-desktop/issues trackers] for bugs, feature requests, binary build announces, etc.

; Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project?
: No, the project has its own [https://gvsig.org/web/community/mailing-lists/directory-en/ mailing list server]. Additionally, gvSIG mailing lists are archived at [http://www.nabble.com/gvSIG-f29441.html nabble] under OSGeo projects (also on [http://news.gmane.org/search.php?match=gvsig gmane] and [http://www.mail-archive.com/find.php?domains=www.mail-archive.com&q=gvsig&sa=Search mail-archive.com]).

; Is the OSGeo SVN being used for the project?
: No, the project is using mainly the [https://devel.gvsig.org/svn/gvsig-desktop 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 at http://downloads.gvsig.org/download/

task for
== Community Functioning ==

; Is there a functioning user support mechanisms (ie. mailing list)?
: gvSIG has a [https://gvsig.org/web/community/mailing-lists/directory-en/ 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 [http://www.gvsig.org/web/projects/gvsig-desktop/official downloads area] of gvSIG website you'll find any binary and source code released from 0.3 version up to current release. The [https://gvsig.org/web/projects/gvsig-desktop/devel/view?set_language=en internal builds] are also published on the community portal. Every build has it's corresponding tag a the [https://devel.gvsig.org/svn/gvsig-desktop/tags/ svn server].task for

; 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.

; Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
: TSC is described at [[gvSIG Technical Steering Committee|this wiki]] and at [http://www.gvsig.org/web/organization/about-us/committees/ gvSIG portal].
: There is also documentation about the [http://www.gvsig.org/web/organization/about-us/regulations/ TSC regulation], [http://www.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2.0.0/anexos/contribuciones-y-parches-al-codigo-de-gvsig/contributions-and-patches-to-the-gvsig-code how to contribute] and what [http://www.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2.0.0/anexos/proyectos-oficiales-en-gvsig/gvsig-official-projects gvSIG official projects] are.
: The TSC has a [https://lists.forge.osor.eu/listinfo/gvsig-desktop-tsc-pub 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?
: Can see the developers in the [http://www.ohloh.net/p/gvsig-desktop-2/contributors gvSIG Desktop ohloh web].

== 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 [http://www.gvsig.org 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?
: Yes, there is in [[GvSIG Provenance Review]]

; Have issues raised in the provenance review been adequately addressed?
: A [https://devel.gvsig.org/redmine/issues/1719 task for incubation] has been created.

; Are [[Commiter Responsibilities Guidelines]] covering legal issues in place?
: We are stablishing a [http://www.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2.0.0/anexos/contribuciones-y-parches-al-codigo-de-gvsig/what-is-the-gvsig-cla 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.

[[Category:Incubation]]
[[Category:gvSIG]]