OTB Project Incubation Status - Revision history

Wiki-Grizonnetm: /* Community Functioning */

2017-04-07T14:08:33Z

Community Functioning

Wiki-Grizonnetm: /* Community Functioning */

2017-04-07T14:04:41Z

Community Functioning

Wiki-Grizonnetm: /* Community Functioning */

2017-04-07T14:02:38Z

Community Functioning

Wiki-Grizonnetm: /* Community Functioning */

2017-04-07T14:02:12Z

Community Functioning

Wiki-Grizonnetm: /* Community Functioning */

2017-04-07T14:00:38Z

Community Functioning

Wiki-Grizonnetm: /* Code Copyright Review */

2017-03-15T09:19:17Z

Code Copyright Review

Wiki-Grizonnetm at 12:48, 12 February 2016

2016-02-12T12:48:40Z

Wiki-Grizonnetm at 12:39, 12 February 2016

2016-02-12T12:39:36Z

Wiki-Surveyor at 21:47, 28 November 2015

2015-11-28T21:47:23Z

Wiki-Surveyor: /* Community Functioning */

2015-07-26T04:47:06Z

Community Functioning

@@ Line 33: / Line 33: @@
 In early 2015, OTB set up an official Project Steering committee (PSC) to provide high level guidance and coordination.  It provides a central point of contact for the project and arbitrates disputes. It is also a stable base of institutional knowledge to the project and tries its best to involve more developers and guarantees that OTB remains open and company neutral. The OTB PSC was inspired by existing structure which exists in other geospatial software projects like GRASS GIS, GDAL or QGIS.
-The documentation about how the governance works is publicly available on the [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee OTB wiki].
+The documentation about how the governance works in general and hopw decisions are made is publicly available in the [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee OTB PSC status page].
-All the decisions regarding OTB are also public and follow a procedure called RFC (Request for Changes).It is also describes in the [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee OTB wiki].
+All the decisions regarding OTB are also public and follow a procedure called RFC (Request for Changes) which is also describes in the [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee OTB wiki].
 A Request for Changes describes a change in Orfeo ToolBox code, API, infrastructure or processes in general that need to be submitted to the PSC vote. Those elements should be provided in an email to the public OTB developer list, with subject starting by "Request For Changes: ".
 The list of all Request for Changes is maintained and publicly available on the [https://wiki.orfeo-toolbox.org/index.php/Requests_for_Changes OTB wiki].
-The PSC status gives also information about contributor guidelines and also in particular how new commiters or PSC members can be added to the project. Like other decisions, it would be done with a vote of a RFC on the mailing list.
+The PSC status gives also information about contributor guidelines and also in particular how new commiters or PSC members can be added to the project. Like other decisions, it would be done with an RFC on the mailing list, a public discussion, a then a vote.
 The [https://www.orfeo-toolbox.org/community/ OTB website] gives also more information on how to contribute to the project.

@@ Line 36: / Line 36: @@
 All the decisions regarding OTB are also public and follow a procedure called RFC (Request for Changes).It is also describes in the [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee OTB wiki].
 A Request for Changes describes a change in Orfeo ToolBox code, API, infrastructure or processes in general that need to be submitted to the PSC vote. Those elements should be provided in an email to the public OTB developer list, with subject starting by "Request For Changes: ".
 The PSC status gives also information about contributor guidelines and also in particular how new commiters or PSC members can be added to the project. Like other decisions, it would be done with a vote of a RFC on the mailing list.

@@ Line 32: / Line 32: @@
 In early 2015, OTB set up an official Project Steering committee (PSC) to provide high level guidance and coordination.  It provides a central point of contact for the project and arbitrates disputes. It is also a stable base of institutional knowledge to the project and tries its best to involve more developers and guarantees that OTB remains open and company neutral. The OTB PSC was inspired by existing structure which exists in other geospatial software projects like GRASS GIS, GDAL or QGIS.
 The documentation about how the governance works is publicly available on the [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee OTB wiki].
 All the decisions regarding OTB are also public and follow a procedure called RFC (Request for Changes).It is also describes in the [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee OTB wiki].
 A Request for Changes describes a change in Orfeo ToolBox code, API, infrastructure or processes in general that need to be submitted to the PSC vote. Those elements should be provided in an email to the public OTB developer list, with subject starting by "Request For Changes: ".
 The PSC status gives also information about contributor guidelines and also in particular how new commiters or PSC members can be added to the project. Like other decisions, it would be done with a vote of a RFC on the mailing list.
 The [https://www.orfeo-toolbox.org/community/ OTB website] gives also more information on how to contribute to the project.
 OTB was created from its inception as a collaborative, community effort. As many open source projects there are number of ways to participate which do not all require programming capabilities: documentation, bug reports and feature requests are all very valuable.

@@ Line 31: / Line 31: @@
 #'''Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines?'''
-In early 2015, OTB set up an official Project Steering committee (PSC) to provide high level guidance and coordination.  It provides a central point of contact for the project and arbitrates disputes. It is also a stable base of institutional knowledge to the project and tries its best to involve more developers and guarantees that OTB remains open and company neutral. The OTB PSC was inspired by existing structure which exists in other geospatial
+In early 2015, OTB set up an official Project Steering committee (PSC) to provide high level guidance and coordination.  It provides a central point of contact for the project and arbitrates disputes. It is also a stable base of institutional knowledge to the project and tries its best to involve more developers and guarantees that OTB remains open and company neutral. The OTB PSC was inspired by existing structure which exists in other geospatial software projects like GRASS GIS, GDAL or QGIS.
 The documentation about how the governance works is publicly available on the [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee OTB wiki].
+All the decisions regarding OTB are also public and follow a procedure called RFC (Request for Changes).It is also describes in the [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee OTB wiki].
 A Request for Changes describes a change in Orfeo ToolBox code, API, infrastructure or processes in general that need to be submitted to the PSC vote. Those elements should be provided in an email to the public OTB developer list, with subject starting by "Request For Changes: ".
 The PSC status gives also information about contributor guidelines and also in particular how new commiters or PSC members can be added to the project. Like other decisions, it would be done with a vote of a RFC on the mailing list.
 The [https://www.orfeo-toolbox.org/community/ OTB website] gives also more information on how to contribute to the project.
 OTB was created from its inception as a collaborative, community effort. As many open source projects there are number of ways to participate which do not all require programming capabilities: documentation, bug reports and feature requests are all very valuable.

@@ Line 30: / Line 30: @@
 #'''Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines?'''
 #'''How many active developers are there? Are they from multiple organizations? Indicate number and some organizations involved.'''
 The ohloh page of the Orfeo ToolBox provides a comprehensive view of contributors activity:

@@ Line 62: / Line 62: @@
 #'''Have issues raised in the provenance review been adequately addressed? Indicate outstanding issues.'''
-A complete list of all copyrights is maintained in the [https://git.orfeo-toolbox.org/otb.git/tree/refs/heads/develop:/Copyright OTB source tree].
+A complete list of all copyrights is maintained in the [https://git.orfeo-toolbox.org/otb.git/tree/refs/heads/develop:/Copyright OTB source tree] and follows Apache foundation guidelines.
-There is no outstanding issue. OTB is in the process to be integrated in Debian as an official package. Debian packaging procedure have been followed and OTB package is currently in [https://ftp-master.debian.org/new.html NEW queue]. OTB is also package for other distribution (fedora, opensuse, arch...).
+OTB is moreover integrated in Debian as an official package. OTB is also package for other distribution (fedora, opensuse, Arch...).
-The only issue spotted (for a long time) is the lack of license for the third party software 6S (developed by NASA, Maryland University and LOA lab). The software is distribute freely (including the source code) but without explicit license. We've got the agreement from the software authors and we're in the process of formalize this agreement (there is no issue)
+#'''Are Committer Responsibilities Guidelines covering legal issues in place?'''
-In the meantime OTB module which use 6S has been deactivated from the Debian package.
+Since migration to Apache v2 in 2017, contributors to the ORFEO ToolBox project need to complete, sign and email to  [http://mailto:cla@orfeo-toolbox.org 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. CLA and ICLA were directly adapted by Software Grant and Corporate Contributor License Agreement provided by the Apache foundation.

@@ Line 61: / Line 61: @@
 [[OTB Code Provenance Review]]
 #'''Have issues raised in the provenance review been adequately addressed? Indicate outstanding issues.'''
-#'''Are Commiter Responsibilities Guidelines covering legal issues in place?'''

@@ Line 21: / Line 21: @@
 #'''Is there a functioning user support mechanisms (ie. mailing list)?'''
-The project currently provides support through a mailing list, managed using Google Groups.
+The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).
 #'''Are source and binary downloads for the package available?'''
 Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html
@@ Line 35: / Line 35: @@
 http://www.ohloh.net/p/otb/contributors?sort=latest_commit
-There were around 15 commiters over the last year.
+There were around 15 committers over the last year.
 The "Contributors" chapter of the Software Guide gives a complete listing of all contributors and their affiliations from the beginning of the project :
@@ Line 55: / Line 55: @@
 #'''Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks? If not, indicate what is planned.'''
-Changes will be made to the website as part of a website redesign before the end of 2014.
+The [https://www.orfeo-toolbox.org/community/ community page] of otb include OSGeo and otb status regarding the incubation process. The event section promote also conference like FOSS4G and is regularly updated.
 ==Code Copyright Review==

@@ Line 25: / Line 25: @@
 Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html
 #'''Has a Project Steering Committee been formed, and given control of the project?'''
-The project doesn't currently have a PSC. There are plans to form one and to have control passed from CNES to the PSC. This should take place by the early summer of 2014.
+A Project Steering Committee has been formed and it is now used to make decisions for the software project. (See: http://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee and http://wiki.orfeo-toolbox.org/index.php/Summary_of_PSC_Decisions)
 Update: (2015-07-24) A Project Steering Committee has been formed. Management decisions are now made in a standard way. Details on the Project Steering Committee can be found at http://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee.
@@ Line 52: / Line 52: @@
 ==Foundation Membership==
 #'''Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation? If not, indicate when this will occur.'''
-Changes will be made to project documentation in Fall 2014.
+The project documentation has been modified to reflect membership in OSGeo.
 #'''Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks? If not, indicate what is planned.'''
 Changes will be made to the website as part of a website redesign before the end of 2014.