OTB Graduation Checklist - Revision history

Wiki-Grizonnetm: /* Copyright and License */

2017-06-19T10:06:33Z

Wiki-Grizonnetm: /* Copyright and License */

2017-06-19T10:02:59Z

Wiki-Grizonnetm: /* Marketing */

2017-05-29T08:45:41Z

Marketing

Wiki-Grizonnetm: /* Marketing */

2017-05-29T08:43:47Z

Marketing

Wiki-Grizonnetm: /* Release Procedure */

2017-05-29T08:29:12Z

Release Procedure

Wiki-Grizonnetm: /* Processes */

2017-05-29T08:26:23Z

Processes

Wiki-Grizonnetm: /* Copyright and License */

2017-05-29T08:25:50Z

Wiki-Grizonnetm at 08:23, 29 May 2017

2017-05-29T08:23:45Z

Darkblueb at 07:48, 26 May 2017

2017-05-26T07:48:07Z

Darkblueb: /* Release Procedure */

2017-05-26T07:46:37Z

Release Procedure

@@ Line 26: / Line 26: @@
 #* https://git.orfeo-toolbox.org/otb.git/blob/HEAD:/LICENSE
 # Project documentation is available under an open license, such as Creative Commons.
-#* Website and Cookbook are licensed under a Creative Commons Attribution-ShareAlike 4.0 International license (CC-BY-SA)
+#* Website and Cookbook are licensed under a Creative Commons Attribution-ShareAlike 4.0 International license (CC-BY-SA) (see related RFC for the Cookbook adopted in June 2017: https://wiki.orfeo-toolbox.org/index.php/Request_for_Changes-94:_CookBook_licensed_under_cc-by-sa)
 # 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].
 #* https://wiki.osgeo.org/wiki/OTB_Code_Provenance_Review

@@ Line 26: / Line 26: @@
 #* https://git.orfeo-toolbox.org/otb.git/blob/HEAD:/LICENSE
 # Project documentation is available under an open license, such as Creative Commons.
-#* Website is creative commons, could not quite tell what the user guide uses.
+#* Website and Cookbook are licensed under a Creative Commons Attribution-ShareAlike 4.0 International license (CC-BY-SA)
 # 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].
 #* https://wiki.osgeo.org/wiki/OTB_Code_Provenance_Review

@@ Line 89: / Line 89: @@
 # 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
+#* Application Overview https://live.osgeo.org/en/overview/otb_overview.html
-#* Application Quick Start
+#* Application Quick Start https://live.osgeo.org/en/quickstart/otb_quickstart.html
-#* Logo
+#* Logo https://live.osgeo.org/_images/logo-otb7.png
-#* Graphical Image
+#* Graphical Image https://git.orfeo-toolbox.org/otb-documents.git/tree/HEAD:/Artwork
 # Ideally, stable version(s) of executable applications are bundled with appropriate distributions.<br/><i>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.)</i>
 #* OTB is included is [https://live.osgeo.org/en/overview/otb_overview.html OSGeo-Live] , [https://packages.debian.org/fr/sid/otb-bin DebianGIS] and UbuntuGIS. An old version is also available in osgeo4w, it was not updated for a while due to packaging and dependencies issues.

@@ Line 94: / Line 94: @@
 #* Graphical Image
 # Ideally, stable version(s) of executable applications are bundled with appropriate distributions.<br/><i>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.)</i>
 == Projects ==

@@ Line 69: / Line 69: @@
 #* See OTB Cdash (nightly builds, unit tests and code coverage submissions): https://dash.orfeo-toolbox.org/
 # Release and testing processes provide sufficient detail for an experienced programmer to follow.
+#* See "help for release actions" page on th wiki which provides some guidelines to follow: https://wiki.orfeo-toolbox.org/index.php/Help_for_release_actions
 = OSGeo Committees and Community =

@@ Line 37: / Line 37: @@
 # The project has code under configuration management. <br/><i>Eg, subversion, git.</i>
-#* Git https://git.orfeo-toolbox.org - There is a mirror on Gitub: https://github.com/orfeotoolbox/OTB
+#* Git https://git.orfeo-toolbox.org - There is also a mirror on GitHub: https://github.com/orfeotoolbox/OTB
 # The project uses an issue tracker and keeps the status of the issue tracker up to date.
 #* https://bugs.orfeo-toolbox.org/my_view_page.php

@@ Line 32: / Line 32: @@
 #*  Following Apache copyright notice recommendations. The list of all copyright holders identified is maintain in the NOTICE file in the source tree: [https://git.orfeo-toolbox.org/otb.git/blob/HEAD:/NOTICE]
 # All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.
-#* List of all contributors is available in the OTB Software Guide []. Moreover to accept your contribution, developers need to sign and email to  cla@orfeo-toolbox.org an “Individual Contributor Licensing Agreement” (ICLA) form and  a “Corporate Contributor Licensing Agreement” (CCLA) form if you are contributing on behalf of your company or another entity which retains copyright for your contribution. The ICLA and CCLA are archived on the OTB server.
+#* List of all contributors is available in the OTB Software Guide. Moreover to accept your contribution, developers need to sign and email to  cla@orfeo-toolbox.org an "Individual Contributor Licensing Agreement" (ICLA) form and  a "Corporate Contributor Licensing Agreement" (CCLA) form if you are contributing on behalf of your company or another entity which retains copyright for your contribution. The ICLA and CCLA are based on ICLA provided by the Apache Software foundation and are archived on the OTB server.
 == Processes ==

@@ Line 17: / Line 17: @@
 #** bugs and feature requests? LINK https://bugs.orfeo-toolbox.org/my_view_page.php
 #** devel communication? LINK https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech1.html#x10-140001.4
-#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. <br/>
+#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. <br/>
 #** Contributions from several organizations shown in the [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee PSC]  page including CNES.fr , [http://www.irstea.fr/accueil IRSTEA] , [http://www.c-s.fr/CS-en-bref_a1.html CS-SI.fr] , [http://www.cesbio.ups-tlse.fr/us/organisation.html cesbio.eu]
@@ Line 30: / Line 30: @@
 #* https://wiki.osgeo.org/wiki/OTB_Code_Provenance_Review
 # The project maintains a list of all copyright holders identified in the Provenance Review Document.
-#*
+#*  Following Apache copyright notice recommendations. The list of all copyright holders identified is maintain in the NOTICE file in the source tree: [https://git.orfeo-toolbox.org/otb.git/blob/HEAD:/NOTICE]
 # All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.
-#*
+#* List of all contributors is available in the OTB Software Guide []. Moreover to accept your contribution, developers need to sign and email to  cla@orfeo-toolbox.org an “Individual Contributor Licensing Agreement” (ICLA) form and  a “Corporate Contributor Licensing Agreement” (CCLA) form if you are contributing on behalf of your company or another entity which retains copyright for your contribution. The ICLA and CCLA are archived on the OTB server.
 == Processes ==
 # The project has code under configuration management. <br/><i>Eg, subversion, git.</i>
-#* Git https://git.orfeo-toolbox.org
+#* Git https://git.orfeo-toolbox.org - There is a mirror on Gitub: https://github.com/orfeotoolbox/OTB
 # The project uses an issue tracker and keeps the status of the issue tracker up to date.
 #* https://bugs.orfeo-toolbox.org/my_view_page.php
 # The project has documented its management processes. <br/><i>This is typically done within a Developers Guide or Project Management Plan.</i>
 #* https://www.orfeo-toolbox.org/community/
-# The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. <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 organisations 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. <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>
-#* https://www.orfeo-toolbox.org/community/
+#* Details on the Project Steering Committee can be found at http://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee and also  https://www.orfeo-toolbox.org/community/
 # The project uses public communication channels for decision making to maintain transparency.<br/><i> E.g. archived email list(s), archived IRC channel(s), public issue tracker.</i>
-#* JIRA system linked via https://wiki.orfeo-toolbox.org/index.php/Git
+#* New features have to been describe in a RFC and discuss and vote publicly on the mailing list. The list of all RFCs is available on the OTB wiki (https://wiki.orfeo-toolbox.org/index.php/Requests_for_Changes). Moreover there is also a public JIRA system available to follow day by day developments linked via https://wiki.orfeo-toolbox.org/index.php/Git
 == Documentation ==
@@ Line 56: / Line 56: @@
 #** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf
 #* Including commented code, ideally published for developer use. <br/><i>Examples: javadocs for Java applications, or Sphinx documentation for Python applications.</i>
-#** https://www.orfeo-toolbox.org/packages/OTBSoftwareGuide.pdf
+#** https://www.orfeo-toolbox.org/packages/OTBSoftwareGuide.pdf and https://www.orfeo-toolbox.org/doxygen/
 #* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.
+#** https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech32.html#x63-43000032 and https://wiki.orfeo-toolbox.org/index.php/Contributors_guidelines
 ==Release Procedure==
@@ Line 64: / Line 64: @@
 # The project follows a defined release process:
- LINK https://www.orfeo-toolbox.org/developers/
+#* The release process is described in the OTB wiki https://wiki.orfeo-toolbox.org/index.php/How_to_Release
 #* Which includes execution of the testing process before releasing a stable release.
 # The project follows a documented testing process. <br/><i>Ideally, this includes both automated and manual testing</i><br/><i>Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests.</i>
 # Release and testing processes provide sufficient detail for an experienced programmer to follow.