GvSIG Incubation Checklist - Revision history

Gvsig at 12:32, 1 October 2015

2015-10-01T12:32:24Z

Gvsig at 12:31, 1 October 2015

2015-10-01T12:31:13Z

Wiki-Mmadrid: /* Copyright and License */

2015-08-06T07:04:10Z

Wiki-Mmadrid: /* Processes */

2015-08-04T09:15:02Z

Processes

Wiki-Mmadrid: /* Open */

2015-07-15T15:32:26Z

Open

Wiki-Mmadrid: /* SAC */

2015-07-15T15:19:03Z

SAC

Wiki-Mmadrid: /* Copyright and License */

2015-07-15T15:11:10Z

Wiki-Mmadrid at 15:09, 15 July 2015

2015-07-15T15:09:39Z

Wiki-Mmadrid at 15:03, 15 July 2015

2015-07-15T15:03:36Z

Gvsig at 11:54, 16 June 2015

2015-06-16T11:54:48Z

@@ Line 32: / Line 32: @@
 #* 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: About gvSIG organization and technical decisions: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/wiki/Wiki. 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
+#* Open decision making process, '''yes: About gvSIG organization and technical decisions: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/wiki/Wiki. A post is published after every version of gvSIG with the novelties of the next one.'''
 # 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).'''<br/><i>Eg. collaboration on project activities such as testing, release and feature development.</i>

@@ Line 3: / Line 3: @@
 '''Version''': 2.0
-'''Last Updated''': June 2015.
+'''Last Updated''': October 2015.
 '''Status''': Draft
@@ Line 32: / Line 32: @@
 #* 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
+#* Open decision making process, '''yes: About gvSIG organization and technical decisions: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/wiki/Wiki. 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).'''<br/><i>Eg. collaboration on project activities such as testing, release and feature development.</i>
-#* 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. '''<br/> <i> 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.</i>
+#* 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 and a professional structure. 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. '''<br/> <i> 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.</i>
 == Copyright and License ==
@@ Line 42: / Line 42: @@
 # 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 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 Review 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'''
@@ Line 51: / Line 51: @@
 # 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'''
+#* About gvSIG Technical decisions: '''https://redmine.gvsig.net/redmine/projects/gvsig-desktop/wiki/Wiki'''
 #* 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'''
@@ Line 58: / Line 58: @@
 #* Documentation guide:''' http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-documentar'''
 <br/><i>This is typically done within a Developers Guide or Project Management Plan.</i>
-#* 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'''<br/><i>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.</i>
+#* 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) formed by professional structure of gvSIG Association and active developers of the community. More information about this in: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/wiki/Wiki. A post is published after every version of gvSIG with the novelties of the next one decided in TSC meetings.'''<br/>
-#* 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.'''<br/><i> E.g. archived email list(s), archived IRC channel(s), public issue tracker.  </i>
+#* The project uses public communication channels for decision making to maintain transparency. '''Yes: A post is published in gvSIG blog after every version of gvSIG with the novelties of the next one decided in TSC meetings. The road map for the following versions of the application, with the changes, is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/roadmap.'''<br/><i> E.g. archived email list(s), archived IRC channel(s), public issue tracker.  </i>
 == Documentation ==

@@ Line 42: / Line 42: @@
 # 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...).'''
+# 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'''

@@ Line 51: / Line 51: @@
 # 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'''
-#* How to contribute: '''http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig'''
+#* GvSIG Technical Steering Committee: '''http://wiki.osgeo.org/wiki/GvSIG_Technical_Steering_Committee'''
 #* 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'''

@@ Line 34: / Line 34: @@
 #* 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). 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).'''<br/><i>Eg. collaboration on project activities such as testing, release and feature development.</i>
+#* 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).'''<br/><i>Eg. collaboration on project activities such as testing, release and feature development.</i>
 #* 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. '''<br/> <i> 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.</i>

@@ Line 109: / Line 109: @@
 == SAC ==
-The [[SAC|System Administration Committee]] is available to help infrastructure and facilities. Information for this committee is collected as part of the [[Project Status Template]]. The following should be set up:
+gvSIG has several mailing lists operating by the OSGeo infrastructure: https://lists.osgeo.org/mailman/listinfo
 [[Category: Incubation]]

@@ Line 40: / Line 40: @@
 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. All the source code of the different versions is in https://devel.gvsig.org/svn/gvsig-desktop/'''
+# 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 an open 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. '''
+# 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. '''
 # 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...).'''
 # 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). '''