https://wiki.osgeo.org/w/api.php?action=feedcontributions&user=Wiki-Grizonnetm&feedformat=atomOSGeo - User contributions [en]2024-03-28T09:54:28ZUser contributionsMediaWiki 1.35.9https://wiki.osgeo.org/w/index.php?title=Annual_General_Meeting_2018&diff=116230Annual General Meeting 20182018-08-22T10:05:45Z<p>Wiki-Grizonnetm: /* Project Reports (15 mins) */</p>
<hr />
<div>== Venue / Timing ==<br />
<br />
* WHEN: Thursday 30 August from 8am-9am (60min)<br />
* WHERE: Selous main hall, of the Julius Nyerere International Convention Centre<br />
* 60 mins - early in the morning. Please show up on time.<br />
<br />
== Description ==<br />
<br />
The Annual General Meeting for OSGeo is open to everybody. <br />
<br />
The goal is to:<br />
<br />
* give an overall status of the organization+<br />
* financial report+<br />
* informing the members of previous and future activities from committees and local chapters<br />
* discuss important issues and take decisions<br />
<br />
+ These two are formal reports that make it an AGM<br />
<br />
== Format ==<br />
<br />
The AGM itself will be a succession of lightning talks (presentations limited to two minutes) given by you in your role as Local Chapter representative, Chair of a committee, representative of a software project, OSGeo director or administrator or whatever else makes up OSGeo. If you feel like you have to say something please add yourself to the correspondent section.<br />
<br />
== Add you content to the shared Slides ==<br />
<br />
This year we are going to use shared slides to setup the presentation for the meeting.<br />
<br />
Please use the shared slide. Two slides/minutes each for a status update. You can provide an extended status report in your project and add the link to this wiki and to the presentation.<br />
<br />
The shared slide deck is available here (request edit access if required):<br />
* https://docs.google.com/presentation/d/1imiG7x09ry7lGvmS15FCVq2Z7yaICY00fcpXBK27TXY/edit?usp=sharing<br />
<br />
How a report could look like<br />
* https://github.com/geotools/geotools/wiki/GeoTools-Annual-Report-2017<br />
<br />
== Board members attending in person ==<br />
* [[María Arias de Reyna]] (OSGeo President will chair the AGM)<br />
* [[User:Maria|Maria Brovelli]]<br />
* [[User:Jive | Jody Garnett ]]<br />
* [[Michael Smith | Mike Smith - Treasurer]]<br />
* [[Vasile Craciunescu]]<br />
* [[Jeff McKenna]] <br />
* [[User:Astrid Emde| Astrid Emde Secretary]]<br />
<br />
==== OSGeo report (10 mins) ====<br />
<br />
Here is what OSGeo has been up to in the last year:<br />
<br />
* Introduction to OSGeo - more than just the FOSS4G conference :)<br />
* Here is what we have done in the last year<br />
** Here is all the events we have sponsored for the year<br />
** photos and stats from events<br />
** photos and stories from code sprints<br />
* Here are our volunteers and leaders thank you<br />
** Pictures from committees and initiatives<br />
* Website <br />
* Budget - we are financially stable<br />
* Elections are coming up<br />
<br />
Contributing to OSGeo report<br />
* tbd<br />
<br />
==== Project Reports (15 mins) ====<br />
<br />
Please use the shared slide. Two slides each for a status update. You can provide an extended status report of your project by adding the link to the presentation<br />
<br />
* 2 mins: Projects and Incubation, status sent to discss@osgeo.org - Report by [[User:Jive | Jody Garnett ]]<br />
* GeoTools Report - releases, committers, status, challenges. Report by [[User:Jive | Jody Garnett ]]<br />
* Mapbender - releases, committers, status, challenges. Report by [[User:Astrid Emde| Astrid Emde]]<br />
* MapServer - releases, committers, status, challenges. Report by [[Jeff McKenna]]<br />
* ZOO-Project - releases, committers, status, challenges. Report by [[User:Djay| Gérald Fenoy]]<br />
* GRASS GIS - releases, committers, status, challenges. Report by [[User:Lucadelu| Luca Delucchi]]<br />
* Oskari - releases, committers, status, challenges. Report by [[User:Tmiosmauli | Timo Aarnioi]]<br />
* QGIS - releases, committers, status, challenges. Report by [[User:mbernasocchi|Marco Bernasocchi]]<br />
* pycsw - releases, committers, status, challenges. Report by (to be determined)<br />
* OpenLayers - releases, committers, status, challenges. Report by (to be determined)<br />
* GeoNode - releases, committers, status, challenges. Report by [[User:Simod|Simone Dalmasso]]<br />
* ORFEO ToolBox - releases, committers, status, challenges. Report by [[User:Djay| Gérald Fenoy]]<br />
<br />
==== Local Chapter Reports (15 mins) ====<br />
<br />
Please use the shared slide. Two slides each for a status update. You can provide an extended status report of your local chapter by adding the link to the presentation<br />
<br />
you need to sign up to be presented<br />
<br />
* 2 mins: Local chapter report by [[User:Astrid Emde| Astrid Emde]]<br />
* 2 mins: OSGeo Website for Local Chapters - [[User:Astrid Emde| Astrid Emde]]<br />
* 2 mins: OSGeo Ottawa Local Chapter - [[User:jerstlouis| Jerome St-Louis]]<br />
* 2 mins: OSGeo Pacific Islands Chapter - [[User:e_liavaa| Edwin Liava'a]]<br />
* 2 mins: OSGeo Romania Chapter - [[Vasile Craciunescu]]<br />
* 2 mins: OSGeo Italian Chapter - [[User:Lucadelu| Luca Delucchi]]<br />
* 2 mins: OSGeo Australia and New Zealand Chapter - [[User:alexgleith| Alex Leith]],[[User:Adamsteer| Adam Steer]]<br />
* 2 mins: OSGeo Francophone Chapter - (to be determined)<br />
* 2 mins: OSGeo Dutch Chapter - (to be determined)<br />
* 2 mins: OSGeo Korea Chapter - (to be determined)<br />
* 2 mins: Geoinquiet@s Argentina - Report by [[User:Mlibman| Malena Libman]]<br />
* 2 mins: OSGeo Irish Chapter - (to be determined)<br />
<br />
==== Partners (6 mins) ====<br />
<br />
OSGeo partners with organizations world wide, this block provides our partners a chance to address:<br />
<br />
* 2 mins: slot 1<br />
* 2 mins: slot 2<br />
<br />
==== Committee Reports (10 mins) ====<br />
<br />
Committees: We expect a status update from each committee, please attend or nominate a delegate (see committees https://www.osgeo.org/about/committees)<br />
<br />
Please use the shared slide. Two slides each for a status update. You can provide an extended status report in you project and add the link to this wiki and to the presentation.<br />
<br />
* Google Summer of Code, and Google Code-in report (Victoria & Jeff)<br />
* Marketing (Jody, Astrid)<br />
* [[SAC 2018 Annual Report|System Administration]] ([[User:wildintellect|Alex M]], [[User:Jmckenna|Jeff M]])<br />
<br />
[[Category: Annual General Meeting]]<br />
[[Category: FOSS4G2018]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=Annual_General_Meeting_2018&diff=116208Annual General Meeting 20182018-08-21T15:37:35Z<p>Wiki-Grizonnetm: /* Project Reports (15 mins) */</p>
<hr />
<div>== Venue / Timing ==<br />
<br />
* WHEN: Thursday 30 August from 8am-9am (60min)<br />
* WHERE: Selous main hall, of the Julius Nyerere International Convention Centre<br />
* 60 mins - early in the morning. Please show up on time.<br />
<br />
== Description ==<br />
<br />
The Annual General Meeting for OSGeo is open to everybody. <br />
<br />
The goal is to:<br />
<br />
* give an overall status of the organization+<br />
* financial report+<br />
* informing the members of previous and future activities from committees and local chapters<br />
* discuss important issues and take decisions<br />
<br />
+ These two are formal reports that make it an AGM<br />
<br />
== Format ==<br />
<br />
The AGM itself will be a succession of lightning talks (presentations limited to two minutes) given by you in your role as Local Chapter representative, Chair of a committee, representative of a software project, OSGeo director or administrator or whatever else makes up OSGeo. If you feel like you have to say something please add yourself to the correspondent section.<br />
<br />
== Add you content to the shared Slides ==<br />
<br />
This year we are going to use shared slides to setup the presentation for the meeting.<br />
<br />
Please use the shared slide. Two slides/minutes each for a status update. You can provide an extended status report in your project and add the link to this wiki and to the presentation.<br />
<br />
The shared slide deck is available here (request edit access if required):<br />
* https://docs.google.com/presentation/d/1imiG7x09ry7lGvmS15FCVq2Z7yaICY00fcpXBK27TXY/edit?usp=sharing<br />
<br />
How a report could look like<br />
* https://github.com/geotools/geotools/wiki/GeoTools-Annual-Report-2017<br />
<br />
== Board members attending in person ==<br />
* [[María Arias de Reyna]] (OSGeo President will chair the AGM)<br />
* [[User:Maria|Maria Brovelli]]<br />
* [[User:Jive | Jody Garnett ]]<br />
* [[Michael Smith | Mike Smith - Treasurer]]<br />
* [[Vasile Craciunescu]]<br />
* [[Jeff McKenna]] <br />
* [[User:Astrid Emde| Astrid Emde Secretary]]<br />
<br />
==== OSGeo report (10 mins) ====<br />
<br />
Here is what OSGeo has been up to in the last year:<br />
<br />
* Introduction to OSGeo - more than just the FOSS4G conference :)<br />
* Here is what we have done in the last year<br />
** Here is all the events we have sponsored for the year<br />
** photos and stats from events<br />
** photos and stories from code sprints<br />
* Here are our volunteers and leaders thank you<br />
** Pictures from committees and initiatives<br />
* Website <br />
* Budget - we are financially stable<br />
* Elections are coming up<br />
<br />
Contributing to OSGeo report<br />
* tbd<br />
<br />
==== Project Reports (15 mins) ====<br />
<br />
Please use the shared slide. Two slides each for a status update. You can provide an extended status report of your project by adding the link to the presentation<br />
<br />
* 2 mins: Projects and Incubation, status sent to discss@osgeo.org - Report by [[User:Jive | Jody Garnett ]]<br />
* GeoTools Report - releases, committers, status, challenges. Report by [[User:Jive | Jody Garnett ]]<br />
* Mapbender - releases, committers, status, challenges. Report by [[User:Astrid Emde| Astrid Emde]]<br />
* MapServer - releases, committers, status, challenges. Report by [[Jeff McKenna]]<br />
* ZOO-Project - releases, committers, status, challenges. Report by [[User:Djay| Gérald Fenoy]]<br />
* GRASS GIS - releases, committers, status, challenges. Report by [[User:Lucadelu| Luca Delucchi]]<br />
* Oskari - releases, committers, status, challenges. Report by [[User:Tmiosmauli | Timo Aarnioi]]<br />
* QGIS - releases, committers, status, challenges. Report by [[User:mbernasocchi|Marco Bernasocchi]]<br />
* pycsw - releases, committers, status, challenges. Report by (to be determined)<br />
* OpenLayers - releases, committers, status, challenges. Report by (to be determined)<br />
* GeoNode - releases, committers, status, challenges. Report by [[User:Simod|Simone Dalmasso]]<br />
* ORFEO ToolBox - releases, committers, status, challenges. Report by (to be determined)<br />
<br />
==== Local Chapter Reports (15 mins) ====<br />
<br />
Please use the shared slide. Two slides each for a status update. You can provide an extended status report of your local chapter by adding the link to the presentation<br />
<br />
you need to sign up to be presented<br />
<br />
* 2 mins: Local chapter report by [[User:Astrid Emde| Astrid Emde]]<br />
* 2 mins: OSGeo Website for Local Chapters - [[User:Astrid Emde| Astrid Emde]]<br />
* 2 mins: OSGeo Ottawa Local Chapter - [[User:jerstlouis| Jerome St-Louis]]<br />
* 2 mins: OSGeo Pacific Islands Chapter - [[User:e_liavaa| Edwin Liava'a]]<br />
* 2 mins: OSGeo Romania Chapter - [[Vasile Craciunescu]]<br />
* 2 mins: OSGeo Italian Chapter - [[User:Lucadelu| Luca Delucchi]]<br />
* 2 mins: OSGeo Australia and New Zealand Chapter - [[User:alexgleith| Alex Leith]],[[User:Adamsteer| Adam Steer]]<br />
* 2 mins: OSGeo Francophone Chapter - (to be determined)<br />
* 2 mins: OSGeo Dutch Chapter - (to be determined)<br />
* 2 mins: OSGeo Korea Chapter - (to be determined)<br />
* 2 mins: Geoinquiet@s Argentina - Report by [[User:Mlibman| Malena Libman]]<br />
* 2 mins: OSGeo Irish Chapter - (to be determined)<br />
<br />
==== Partners (6 mins) ====<br />
<br />
OSGeo partners with organizations world wide, this block provides our partners a chance to address:<br />
<br />
* 2 mins: slot 1<br />
* 2 mins: slot 2<br />
<br />
==== Committee Reports (10 mins) ====<br />
<br />
Committees: We expect a status update from each committee, please attend or nominate a delegate (see committees https://www.osgeo.org/about/committees)<br />
<br />
Please use the shared slide. Two slides each for a status update. You can provide an extended status report in you project and add the link to this wiki and to the presentation.<br />
<br />
* Google Summer of Code, and Google Code-in report (Victoria & Jeff)<br />
* Marketing (Jody, Astrid)<br />
* [[SAC 2018 Annual Report|System Administration]] ([[User:wildintellect|Alex M]], [[User:Jmckenna|Jeff M]])<br />
<br />
[[Category: Annual General Meeting]]<br />
[[Category: FOSS4G2018]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=User:Grizonnetm&diff=110716User:Grizonnetm2017-11-06T08:06:29Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Manuel Grizonnet<br />
|JobTitle=Image processing engineer<br />
|Company=CNES<br />
|Country=France<br />
|City=Toulouse<br />
|Coordinate=43.562299, 1.480199<br />
|LocalChapter=Francophone OSGeo Chapter<br />
|Email=manuel.grizonnet AT gmail DOT com<br />
|Photo=Manuel_Grizonnet.png<br />
|Languages=French; English;<br />
|Info=Manuel works at CNES (French Space Agency) and is involved in the Open Source library for remote sensing image processing Orfeo ToolBox.<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=Yes<br />
|Translate=Yes<br />
|PSC=Yes<br />
|ExBoard=No<br />
|Charter=Yes<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=Yes<br />
}}<br />
===Manuel Grizonnet===<br />
<br />
[[File:Manuel_Grizonnet.png|thumb|right|100px|Manuel Grizonnet]]<br />
<br />
Location : Toulouse, France<br />
<br />
Manuel works at CNES (French Space Agency) and is a many years (9 years) contributor to the Open Source library for remote sensing image processing [http://www.orfeo-toolbox.org/ Orfeo ToolBox].<br />
<br />
;OSGeo Experience [[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]]:<br />
:* Part of the developers team of the ORFEO ToolBox library<br />
:* Contributor to the OSGeo Live project<br />
:* Occasional contributor to OSSIM and QGIS<br />
;Contact:<br />
: Email: manuel.grizonnet AT gmail DOT com<br />
<br />
;Spoken Language(s): French, English.<br />
<br />
[[Category:OSGeo Advocate]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=User:Grizonnetm&diff=108464User:Grizonnetm2017-08-29T16:35:19Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Manuel Grizonnet<br />
|JobTitle=Image processing engineer<br />
|Company=CNES<br />
|Country=France<br />
|City=Toulouse<br />
|Coordinate=43.562299, 1.480199<br />
|LocalChapter=Francophone OSGeo Chapter<br />
|Email=manuel.grizonnet AT gmail DOT com<br />
|Photo=Manuel_Grizonnet.png<br />
|Languages=French; English;<br />
|Info=Manuel works at CNES (French Space Agency) and is involved in the Open Source library for remote sensing image processing Orfeo ToolBox.<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=Yes<br />
|Translate=Yes<br />
|PSC=Yes<br />
|ExBoard=No<br />
|Charter=No<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=Yes<br />
}}<br />
===Manuel Grizonnet===<br />
<br />
[[File:Manuel_Grizonnet.png|thumb|right|100px|Manuel Grizonnet]]<br />
<br />
Location : Toulouse, France<br />
<br />
Manuel works at CNES (French Space Agency) and is a many years (9 years) contributor to the Open Source library for remote sensing image processing [http://www.orfeo-toolbox.org/ Orfeo ToolBox].<br />
<br />
;OSGeo Experience [[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]]:<br />
:* Part of the developers team of the ORFEO ToolBox library<br />
:* Contributor to the OSGeo Live project<br />
:* Occasional contributor to OSSIM and QGIS<br />
;Contact:<br />
: Email: manuel.grizonnet AT gmail DOT com<br />
<br />
;Spoken Language(s): French, English.<br />
<br />
[[Category:OSGeo Advocate]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=User:Grizonnetm&diff=108463User:Grizonnetm2017-08-29T16:34:26Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Manuel Grizonnet<br />
|Company=CNES<br />
|Country=France<br />
|City=Toulouse<br />
|Coordinate=43.562299, 1.480199<br />
|LocalChapter=Francophone OSGeo Chapter<br />
|Email=manuel.grizonnet AT gmail DOT com<br />
|Photo=Manuel_Grizonnet.png<br />
|Languages=French; English;<br />
|Info=Manuel works at CNES (French Space Agency) and is involved in the Open Source library for remote sensing image processing Orfeo ToolBox.<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=Yes<br />
|Translate=Yes<br />
|PSC=Yes<br />
|ExBoard=No<br />
|Charter=No<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=Yes<br />
}}<br />
===Manuel Grizonnet===<br />
<br />
[[File:Manuel_Grizonnet.png|thumb|right|100px|Manuel Grizonnet]]<br />
<br />
Location : Toulouse, France<br />
<br />
Manuel works at CNES (French Space Agency) and is a many years (9 years) contributor to the Open Source library for remote sensing image processing [http://www.orfeo-toolbox.org/ Orfeo ToolBox].<br />
<br />
;OSGeo Experience [[File:OSGeo_coder.png|link=OSGeo_Advocate#Developers_and_Committee_Members]]:<br />
:* Part of the developers team of the ORFEO ToolBox library<br />
:* Contributor to the OSGeo Live project<br />
:* Occasional contributor to OSSIM and QGIS<br />
;Contact:<br />
: Email: manuel.grizonnet AT gmail DOT com<br />
<br />
;Spoken Language(s): French, English.<br />
<br />
[[Category:OSGeo Advocate]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=Annual_General_Meeting_2017&diff=107948Annual General Meeting 20172017-08-13T07:33:20Z<p>Wiki-Grizonnetm: /* Project Reports (15 mins) */</p>
<hr />
<div>== Venue / Timing ==<br />
<br />
* WHEN: Friday August 18, 12:30 - 2:00 pm (90 min)<br />
* WHERE: Seaport Hotel, Room: City View 1, seats 350 people<br />
<br />
== Description ==<br />
<br />
The Annual General Meeting for OSGeo is open to everybody. <br />
<br />
The goal is to:<br />
<br />
* give an overall status of the organization+<br />
* financial report+<br />
* informing the members of previous and future activities from committees and local chapters<br />
* discuss important issues and take decisions<br />
<br />
+ These two are formal reports that make it an AGM<br />
<br />
== Format ==<br />
<br />
The AGM itself will be a succession of lightning talks (presentations limited to three or four minutes) given by you in your role as Local Chapter representative, Chair of a committee, representative of a software project, OSGeo director or administrator or whatever else makes up OSGeo. If you feel like you have to say something please add yourself to the list. <br />
<br />
Board members attending in person: <br />
* Helena Mitasova<br />
* Maria Brovelli<br />
* [[User:endofcap | Sanghee Shin]]<br />
* [[User:Jive | Jody Garnett ]]<br />
* [[User:Michael_Smith | Mike - Treasurer]]<br />
* Vasile Craciunescu<br />
<br />
== Annual General Meeting / Closing Ceremony ==<br />
<br />
=== General Meeting (90 mins) ===<br />
<br />
Room: City View 1, seats 350 people, 90 min time block.<br />
<br />
Final session before the closing session in the invited speaker room (a large space for all interested in attending.)<br />
<br />
==== OSGeo report (10 mins) ====<br />
<br />
OSGeo Foundation (10 min): single slide deck, already on stage, etc...<br />
<br />
Here is what OSGeo has been up to in the last year:<br />
<br />
* Introduction to OSGeo - more than just the foss4g conference :)<br />
* Here is what we have done in the last year<br />
** Here is all the events we have sponsored for the year<br />
** photos and stats from events<br />
** photos and stories from code sprints<br />
* Here are our volunteers and leaders thank you<br />
** Pictures from committees and initiatives<br />
* Website / Branding - key 2017 initiative<br />
* Budget - we are financially stable<br />
* Elections are coming up<br />
<br />
Contributing to OSGeo report<br />
<br />
* 3 mins: [[User:helena | Helena - Vice - President]], OSGeo - OSGeo status overview (formal requirement)<br />
* 2 mins: [[User:Jachym | Jachym - Secretary]] - Secretary's brief report (formal requirement)<br />
* 1 mins: [[User:Michael_Smith | Mike - Treasurer]] - Treasure's brief report (formal requirement)<br />
* 2 mins: Vasile - 2017 elections<br />
* 2 mins: Release of new Website - [[User:Ortelius | Jeffrey Johnson]]<br />
<br />
Technical this is our AGM, since we say we are still going and have money to do so :)<br />
<br />
==== Project Reports (15 mins) ====<br />
<br />
Project Report (15 min): Single slide deck, two slides each for a status update, collect status report on discuss and summary in AGM<br />
<br />
''Several projects have full talks accepted about the project update - we can ask the same person to provide 2-3 slide summary here''<br />
<br />
* 3 mins: Jody - Projects and Incubation, status sent to discss@osgeo.org<br />
* 2 mins: OSGeo Website for PSC members - [[User:Ortelius | Jeffrey Johnson]]: new user outreach, project content, working with service providers<br />
* GeoTools Report - [[User:Jive | Jody Garnett ]]- releases, committers, status, challenges<br />
* GRASS GIS - [[User:Wenzeslaus | Vaclav Petras ]] - releases, committers, status, challenges<br />
* GeoMoose - [[User:theduckylittle | Dan "Ducky" Little]] - releases, committers, status, challenges<br />
* ORFEO ToolBox - [[User:Grizonnetm | Manuel Grizonnet]] - incubation status, releases, committers, challenges<br />
* Add Project Name - releases, committers, status, challenges<br />
* Add Project Name - releases, committers, status, challenges<br />
* Add Project Name - releases, committers, status, challenges<br />
<br />
==== Local Chapter Reports (30 mins) ====<br />
<br />
Local chapters (30 mins): single deck? this is a challenge, you need to sign up to be presented<br />
<br />
* 3 mins: Local chapter report by [[User:endofcap | Sanghee ]]<br />
* 2 mins: OSGeo Website for Local Chapters - [[User:Ortelius | Jeffrey Johnson]]: new user outreach, open source advocacy<br />
* [[Korea | OSGeo Korean Chapter]] Report by [[User:endofcap | Sanghee ]]<br />
* [[Italy| OSGeo Italian Chapter GFOSS]] Report by [[User:maria | Maria Brovelli ]]<br />
* [http://uk.osgeo.org OSGeo:UK] Report by [[User:Stevenfeldman | Steven Feldman]]<br />
* [http://www.osgeo.jp/ OSGeo Japan Chapter] Report by [[User:Yoichi | Yoichi Kayama]]<br />
* [http://www.osgeo.fi/ OSGeo Finland Chapter] Report by [[User:posiki | Pekka Sarkola]]<br />
* [http://www.fossgis.de OSGeo Austria-Germany-Switzerland Chapter (FOSSGIS)] Report by [[User:Peter_Loewe | Peter Loewe]]<br />
* Add Local Chapter name - events, members, outreach, inspire, coming up<br />
* Add Local Chapter name - events, members, outreach, inspire, coming up<br />
* Add Local Chapter name - events, members, outreach, inspire, coming up<br />
<br />
==== Partners (10 mins) ====<br />
<br />
OSGeo partners with organizations world wide, this block provides our partners a chance to address:<br />
<br />
* 5 mins: slot 1<br />
* 5 mins: slot 2<br />
<br />
==== Committee Reports (15 mins) ====<br />
<br />
Committees (15 mins): single slide deck? we expect a status update from each committee, please attend or nominate a delegate <br />
<br />
* 3 mins: Maria - Introduce how committees work, thank the volunteers, and get out of the way<br />
* 2 mins: UN Committee Report by [[User:Maria | Maria Brovelli]]<br />
* 1 mins: GeoForAll - [[User:Maria | Maria Brovelli]] - talk about new members/partners<br />
* 2 mins: OSGeo Website for Committee Chairs - [[User:Ortelius | Jeffrey Johnson]]: new member outreach, working with partners<br />
* 2 mins: Marketing Committee - [[User:Marc Vloemans]]<br />
* 1 mins: Incubation Report - [[User:Jive | Jody Garnett ]]<br />
* 2 mins: Conference Committee (?) - anounce the next foss4g event<br />
* 2 mins Open GeoScience Committee [[User:Peter_Loewe | Peter Loewe]] <br />
* 1 min: Google Summer of Code / Code-In Report - [[Jeff McKenna]]<br />
* Public Geospatial Data Committee (?)<br />
* System Administration Committee (SAC) (?)<br />
<br />
==== Open Q&A from OSGeo Members (10 mins) ====<br />
<br />
If you cannot attend (or if we do not have time for an open mike), please provide questions ahead of time below (answers will be handled by appropriate project, local chapter or committee report):<br />
<br />
* ''Q: How do you start a local chapter?''<br />
* "Q: Where to get a new OSGeo T-Shirt?"<br />
* ''add your name and question (or discussion topic)''<br />
<br />
=== Closing (90 mins) ===<br />
<br />
Room: Commonwealth, seats 900+, 45 min block<br />
<br />
Closing, status update, awards and wrap up.<br />
<br />
==== Keynote (45 mins) ====<br />
<br />
María Arias de Reyna - closing keynote on open data.<br />
<br />
==== OSGeo Update (10 mins) ====<br />
<br />
Moved to AGM<br />
<br />
==== Awards (20 mins) ====<br />
<br />
Awards (20 mins):<br />
<br />
* 5 mins: Developer Awards (GeoCat representative): (have a slide to cover finding awardee on screen)<br />
* 5 mins: Student Awards - GeoForAll: (have a slide to cover finding awardee on screen)<br />
* 10 mins: Sol Katz Award - longer as short speech or video used<br />
<br />
==== Closing (25 mins) ====<br />
<br />
Foss4g Closing:<br />
<br />
* 10 mins: Thanks you to volunteers, local organizing committee<br />
* 10 mins: FOSS4G 2018 Invitation (video? link?). Hand over to next organizing committee<br />
* 5 mins: Thank you for coming, lights out, go home, see you at code sprint on Saturday<br />
<br />
[[Category: Annual General Meeting]]<br />
[[Category: FOSS4G2017]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2017_Code_Sprint&diff=107536FOSS4G 2017 Code Sprint2017-07-20T13:11:37Z<p>Wiki-Grizonnetm: /* Registered Attendees */</p>
<hr />
<div>== Code Sprint ==<br />
<br />
Venue: Boston, Massachusetts, United States<br />
<br />
This year, once again, we are following the old tradition of hosting a code sprint right after [http://2017.foss4g.org FOSS4G 2017]. <br />
The code sprint will be held Saturday August 19th, 2017 at District Hall (http://www.districthallboston.org/). <br />
<br />
<br />
Participation in the code sprint is free of charge and all folks currently involved or interested in getting involved in OSGeo community projects are welcome.<br />
<br />
This is open to all who wish to participate in one or more projects. There’s always plenty to do – it’s not all about programming. Translation, documentation, feedback, discussions, and testing are also very important for projects! Registration with the conference is not a prerequisite for participation in code sprint.<br />
<br />
<br />
If you plan to attend, please signup in the table below so we have ample time for planning of snacks and drinks!<br />
<br />
.<br />
<br />
One thing we’d like to ask you: with over 200 participants anticipated, the WLAN capacity will naturally be exhausted at some point. Please be sure to avoid huge on-site downloads of data, as this could impact the work of others. Thank you!<br />
<br />
The Codesprint Organizing Team is looking forward to your coming!<br />
<br />
'''In summary:'''<br />
<br />
===When ===<br />
* Saturday August 19th 9AM - 5PM<br />
<br />
<br />
=== Where===<br />
* Venue & Accommodation: Boston District Hall. (For more information: http://www.districthallboston.org/) [[http://www.openstreetmap.org/#map=19/42.35229/-71.04528| OpenStreetMap]]<br />
<br />
'''Power connector:'''<br />
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] . See also http://www.power-plugs-sockets.com/<br />
<br />
== Registered Attendees ==<br />
<br />
The Code Sprint does not cost any money. For us it makes planning easier if we know who is coming. So please leave your Name.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="60"|Accomodation<br />
!width="30"|vegetarian food<br />
|-<br />
| 1 ||[[User:Robe|Regina Obe]] || lr pcorp us|| [[PostGIS]], [[GDAL]], [[pgRouting]], [[GEOS]] || home || No<br />
|-<br />
| 2 ||[[Leo Hsu]] || lr pcorp us || [[PostGIS]], [[pgRouting]] || home || No<br />
|-<br />
| 3 ||[[User:gsteinmon|Guido Stein]] || gstein@appgeo.com || [[FOSS4G]] || home || No<br />
|-<br />
| 4 ||[[User:wenzeslaus|Vaclav Petras]] || wenzeslaus gmail com || [[GRASS GIS]], PDAL || || No<br />
|-<br />
| 5 ||[[User:Annakrat|Anna Petrasova]] || akratoc gmail com || [[GRASS GIS]] || || No<br />
|-<br />
| 6 ||[[User:Helena|Helena Mitasova]] || hmitaso ncsu edu || [[GRASS GIS]] || || No<br />
|-<br />
| 7 ||[[User:Adamsteer|Adam Steer]] || adam.steer anu edu au || PDAL,PyWPS || || No<br />
|-<br />
| 8 ||[[User:hgryoo|Hyung-Gyu Ryoo]] || hgryoo pnu edu || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 9 ||[[User:soojin.kim|Soojin Kim]] || soojin.kim pnu edu || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 10 ||[[User:dbaston|Dan Baston]] || dbaston gmail com || [[PostGIS]], [[GEOS]] || || No<br />
|-<br />
| 11 ||[[User:pwramsey3|Paul Ramsey]] || pramsey cleverelephant ca || [[PostGIS]], [[GEOS]] || || No<br />
|-<br />
| 12 ||[[User:darkblue_b|Brian M Hamlin]] || maplabs -at- light42 || OSGeo Live || || Yes<br />
|-<br />
| 13 ||[[User:ianturton|Ian Turton]] || ian -at- ianturton.com || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 14 ||[[User:jimk|Jim Klassen]] || jklassen -at- sharedgeo.org || [[GeoMoose]], [[MapServer]] || || No<br />
|-<br />
| 15 ||[[User:Chrismarx|Chris Marx]] || chrismarx -at- gmail.com || [[PostGIS]] || || No<br />
|-<br />
| 16 ||[[User:larss|Lars Schylberg]] || lars.schylberg -at- blixtmail.se || [[MapServer]] - documentation/demo || || No<br />
|-<br />
| 17 ||[[User: Bluemates |Kyoung-Sook Kim]] || ks.kim -at- aist.go.jp || [[PostGIS]], PDAL || || No<br />
|-<br />
| 18 ||[[User:msmitherdc|Michael Smith]] || michael.smith.erdc-at-gmail.com || PDAL,MapServer || || No<br />
|-<br />
| 19 ||[[User:grizonnetm|Manuel Grizonnet]] || manuel.grizonnet-at-cnes.fr || OTB, OSGeo-Live, QGIS || || No<br />
|}<br />
<br />
= Workgroups =<br />
<br />
Getting the most of a code sprint takes a lot of prep. Please use this area to decide on a topic, sort out a plan of attack.<br />
<br />
Please keep in mind that the FOSS4G conference is an outreach event. Some of the "new" volunteers are learning about open source for the first time, consider listing some activities (and perhaps having a mentor on hand to facilitate).<br />
<br />
== Website Training ==<br />
<br />
OSGeo website training is available throughout the day, please mark your name down to attend. We ask that a member of each OSGeo committee, local chapter, geoforall lab make plans to attend. Service providers and sponsors are also welcome.<br />
<br />
We will be reviewing both the website publication workflow and the about.yaml structured content used by the project working group.<br />
<br />
'''Attending:''' <br />
Jody Garnett, Jeffrey Johnson<br />
<br />
'''Goals:''' <br />
<br />
Introduce members to the new website, editing workflow, and add to the members map.<br />
<br />
Stop by to create your own personal "osgeo branding" using InkScape.<br />
<br />
Answer any questions projects have on about.yaml use.<br />
<br />
Add to the collection of presentations, videos and tutorial links.<br />
<br />
== PostGIS ==<br />
<br />
Spatial database extender for PostgreSQL<br />
<br />
'''Attending:''' <br />
Regina Obe, Leo Hsu, Dan Baston, Paul Ramsey<br />
<br />
<br />
'''Goals:''' <br />
* Getting ready for PostGIS 2.4.0 release.<br />
* Testing out what we'll be pushing.<br />
* Thoughts on better integration with GDAL and PostGIS. Most notably the sucky support of out of db tables in GDAL.<br />
* Better integration of document translations<br />
<br />
== GRASS GIS ==<br />
<br />
Backend and desktop geospatial analysis tool<br />
<br />
'''Attending:''' Vaclav Petras, Anna Petrasova, Helena Mitasova<br />
<br />
'''Goals:''' Documentation, images for manual pages, and testing for next release. <br />
<br />
== GeoTools ==<br />
<br />
GeoTools is an open source Java library that provides tools for geospatial data.<br />
<br />
'''Attending:''' <br />
<br />
Jody Garnett,<br />
Ian Turton<br />
<br />
'''Goals:''' <br />
<br />
* Java 9 "Service Provider Interface" compatibility<br />
* Service Locator based FactoryRegistery replacement<br />
* Updated factory tutorials to document FactoryRegistry replacement<br />
<br />
'''New to Open Source:''' <br />
<br />
* Help review and improve the geotools function list.<br />
* Come prepaired with [http://docs.geotools.org/latest/userguide/build/index.html geotools build and development environment] and review the [http://docs.geotools.org/latest/userguide/tutorial/function.html function tutorial]. We can help answer any questions if you get stuck.<br />
<br />
== GeoServer ==<br />
<br />
Popular web application for sharing geospatial information, written in Java.<br />
<br />
'''Attending:''' <br />
<br />
Jody Garnett,<br />
Torben Barsballe,<br />
Kevin Smith,<br />
Ian Turton<br />
<br />
'''Goals:''' <br />
<br />
* Coordinate Java 9 upgrade with GeoTools project<br />
<br />
<br />
'''New to Open Source:''' <br />
<br />
* Volunteers assist with any remaining REST API docs ahead of the 2.12 release, come prepaired with a GeoServer installation and your own github id.<br />
* Developers come prepaired with [http://docs.geoserver.org/latest/en/developer/quickstart/index.html build and development environment] we can help answer any questions if you get stuck.<br />
<br />
[[Category:FOSS4G2017]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2017_Code_Sprint&diff=107535FOSS4G 2017 Code Sprint2017-07-20T13:11:07Z<p>Wiki-Grizonnetm: /* Registered Attendees */</p>
<hr />
<div>== Code Sprint ==<br />
<br />
Venue: Boston, Massachusetts, United States<br />
<br />
This year, once again, we are following the old tradition of hosting a code sprint right after [http://2017.foss4g.org FOSS4G 2017]. <br />
The code sprint will be held Saturday August 19th, 2017 at District Hall (http://www.districthallboston.org/). <br />
<br />
<br />
Participation in the code sprint is free of charge and all folks currently involved or interested in getting involved in OSGeo community projects are welcome.<br />
<br />
This is open to all who wish to participate in one or more projects. There’s always plenty to do – it’s not all about programming. Translation, documentation, feedback, discussions, and testing are also very important for projects! Registration with the conference is not a prerequisite for participation in code sprint.<br />
<br />
<br />
If you plan to attend, please signup in the table below so we have ample time for planning of snacks and drinks!<br />
<br />
.<br />
<br />
One thing we’d like to ask you: with over 200 participants anticipated, the WLAN capacity will naturally be exhausted at some point. Please be sure to avoid huge on-site downloads of data, as this could impact the work of others. Thank you!<br />
<br />
The Codesprint Organizing Team is looking forward to your coming!<br />
<br />
'''In summary:'''<br />
<br />
===When ===<br />
* Saturday August 19th 9AM - 5PM<br />
<br />
<br />
=== Where===<br />
* Venue & Accommodation: Boston District Hall. (For more information: http://www.districthallboston.org/) [[http://www.openstreetmap.org/#map=19/42.35229/-71.04528| OpenStreetMap]]<br />
<br />
'''Power connector:'''<br />
* Bring [http://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] . See also http://www.power-plugs-sockets.com/<br />
<br />
== Registered Attendees ==<br />
<br />
The Code Sprint does not cost any money. For us it makes planning easier if we know who is coming. So please leave your Name.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="60"|Accomodation<br />
!width="30"|vegetarian food<br />
|-<br />
| 1 ||[[User:Robe|Regina Obe]] || lr pcorp us|| [[PostGIS]], [[GDAL]], [[pgRouting]], [[GEOS]] || home || No<br />
|-<br />
| 2 ||[[Leo Hsu]] || lr pcorp us || [[PostGIS]], [[pgRouting]] || home || No<br />
|-<br />
| 3 ||[[User:gsteinmon|Guido Stein]] || gstein@appgeo.com || [[FOSS4G]] || home || No<br />
|-<br />
| 4 ||[[User:wenzeslaus|Vaclav Petras]] || wenzeslaus gmail com || [[GRASS GIS]], PDAL || || No<br />
|-<br />
| 5 ||[[User:Annakrat|Anna Petrasova]] || akratoc gmail com || [[GRASS GIS]] || || No<br />
|-<br />
| 6 ||[[User:Helena|Helena Mitasova]] || hmitaso ncsu edu || [[GRASS GIS]] || || No<br />
|-<br />
| 7 ||[[User:Adamsteer|Adam Steer]] || adam.steer anu edu au || PDAL,PyWPS || || No<br />
|-<br />
| 8 ||[[User:hgryoo|Hyung-Gyu Ryoo]] || hgryoo pnu edu || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 9 ||[[User:soojin.kim|Soojin Kim]] || soojin.kim pnu edu || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 10 ||[[User:dbaston|Dan Baston]] || dbaston gmail com || [[PostGIS]], [[GEOS]] || || No<br />
|-<br />
| 11 ||[[User:pwramsey3|Paul Ramsey]] || pramsey cleverelephant ca || [[PostGIS]], [[GEOS]] || || No<br />
|-<br />
| 12 ||[[User:darkblue_b|Brian M Hamlin]] || maplabs -at- light42 || OSGeo Live || || Yes<br />
|-<br />
| 13 ||[[User:ianturton|Ian Turton]] || ian -at- ianturton.com || [[GeoTools]], [[GeoServer]] || || No<br />
|-<br />
| 14 ||[[User:jimk|Jim Klassen]] || jklassen -at- sharedgeo.org || [[GeoMoose]], [[MapServer]] || || No<br />
|-<br />
| 15 ||[[User:Chrismarx|Chris Marx]] || chrismarx -at- gmail.com || [[PostGIS]] || || No<br />
|-<br />
| 16 ||[[User:larss|Lars Schylberg]] || lars.schylberg -at- blixtmail.se || [[MapServer]] - documentation/demo || || No<br />
|-<br />
| 17 ||[[User: Bluemates |Kyoung-Sook Kim]] || ks.kim -at- aist.go.jp || [[PostGIS]], PDAL || || No<br />
|-<br />
| 18 ||[[User:msmitherdc|Michael Smith]] || michael.smith.erdc-at-gmail.com || PDAL,MapServer || || No<br />
|-<br />
| 19 ||[[User:grizonnetm|Manuel Grizonnet]] || manuel.grizonnet-at-cnes.fr || OTB, OSGeo-Live || || No<br />
|}<br />
<br />
= Workgroups =<br />
<br />
Getting the most of a code sprint takes a lot of prep. Please use this area to decide on a topic, sort out a plan of attack.<br />
<br />
Please keep in mind that the FOSS4G conference is an outreach event. Some of the "new" volunteers are learning about open source for the first time, consider listing some activities (and perhaps having a mentor on hand to facilitate).<br />
<br />
== Website Training ==<br />
<br />
OSGeo website training is available throughout the day, please mark your name down to attend. We ask that a member of each OSGeo committee, local chapter, geoforall lab make plans to attend. Service providers and sponsors are also welcome.<br />
<br />
We will be reviewing both the website publication workflow and the about.yaml structured content used by the project working group.<br />
<br />
'''Attending:''' <br />
Jody Garnett, Jeffrey Johnson<br />
<br />
'''Goals:''' <br />
<br />
Introduce members to the new website, editing workflow, and add to the members map.<br />
<br />
Stop by to create your own personal "osgeo branding" using InkScape.<br />
<br />
Answer any questions projects have on about.yaml use.<br />
<br />
Add to the collection of presentations, videos and tutorial links.<br />
<br />
== PostGIS ==<br />
<br />
Spatial database extender for PostgreSQL<br />
<br />
'''Attending:''' <br />
Regina Obe, Leo Hsu, Dan Baston, Paul Ramsey<br />
<br />
<br />
'''Goals:''' <br />
* Getting ready for PostGIS 2.4.0 release.<br />
* Testing out what we'll be pushing.<br />
* Thoughts on better integration with GDAL and PostGIS. Most notably the sucky support of out of db tables in GDAL.<br />
* Better integration of document translations<br />
<br />
== GRASS GIS ==<br />
<br />
Backend and desktop geospatial analysis tool<br />
<br />
'''Attending:''' Vaclav Petras, Anna Petrasova, Helena Mitasova<br />
<br />
'''Goals:''' Documentation, images for manual pages, and testing for next release. <br />
<br />
== GeoTools ==<br />
<br />
GeoTools is an open source Java library that provides tools for geospatial data.<br />
<br />
'''Attending:''' <br />
<br />
Jody Garnett,<br />
Ian Turton<br />
<br />
'''Goals:''' <br />
<br />
* Java 9 "Service Provider Interface" compatibility<br />
* Service Locator based FactoryRegistery replacement<br />
* Updated factory tutorials to document FactoryRegistry replacement<br />
<br />
'''New to Open Source:''' <br />
<br />
* Help review and improve the geotools function list.<br />
* Come prepaired with [http://docs.geotools.org/latest/userguide/build/index.html geotools build and development environment] and review the [http://docs.geotools.org/latest/userguide/tutorial/function.html function tutorial]. We can help answer any questions if you get stuck.<br />
<br />
== GeoServer ==<br />
<br />
Popular web application for sharing geospatial information, written in Java.<br />
<br />
'''Attending:''' <br />
<br />
Jody Garnett,<br />
Torben Barsballe,<br />
Kevin Smith,<br />
Ian Turton<br />
<br />
'''Goals:''' <br />
<br />
* Coordinate Java 9 upgrade with GeoTools project<br />
<br />
<br />
'''New to Open Source:''' <br />
<br />
* Volunteers assist with any remaining REST API docs ahead of the 2.12 release, come prepaired with a GeoServer installation and your own github id.<br />
* Developers come prepaired with [http://docs.geoserver.org/latest/en/developer/quickstart/index.html build and development environment] we can help answer any questions if you get stuck.<br />
<br />
[[Category:FOSS4G2017]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Graduation_Checklist&diff=107218OTB Graduation Checklist2017-06-19T10:06:33Z<p>Wiki-Grizonnetm: /* Copyright and License */</p>
<hr />
<div>= Incubation Checklist =<br />
<br />
== Open ==<br />
<br />
The project has demonstrated that it has an open, active and healthy user and developer community: <br />
# Open: projects are expected to function in an open and public manner and include:<br />
#* Open source license(s),<br />
#** Apache License 2.0<br />
#* Open communication channels,<br />
#** The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#* Open decision making process,<br />
#** 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)<br />
#** 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.<br />
# Active and healthy community:<br />
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. <br/><br />
#** release process? LINK https://wiki.orfeo-toolbox.org/index.php/Release_planning<br />
#** bugs and feature requests? LINK https://bugs.orfeo-toolbox.org/my_view_page.php<br />
#** devel communication? LINK https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech1.html#x10-140001.4<br />
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. <br/><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]<br />
<br />
== Copyright and License ==<br />
<br />
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:<br />
# All project source code is available under an Open Source license.<br />
#* https://git.orfeo-toolbox.org/otb.git/blob/HEAD:/LICENSE<br />
# Project documentation is available under an open license, such as Creative Commons.<br />
#* 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)<br />
# 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].<br />
#* https://wiki.osgeo.org/wiki/OTB_Code_Provenance_Review<br />
# The project maintains a list of all copyright holders identified in the Provenance Review Document.<br />
#* 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]<br />
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.<br />
#* 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.<br />
<br />
== Processes ==<br />
<br />
# The project has code under configuration management. <br/><i>Eg, subversion, git.</i><br />
#* Git https://git.orfeo-toolbox.org - There is also a mirror on GitHub: https://github.com/orfeotoolbox/OTB<br />
# The project uses an issue tracker and keeps the status of the issue tracker up to date.<br />
#* https://bugs.orfeo-toolbox.org/my_view_page.php<br />
# The project has documented its management processes. <br/><i>This is typically done within a Developers Guide or Project Management Plan.</i><br />
#* https://www.orfeo-toolbox.org/community/<br />
# 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><br />
#* 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/<br />
# 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><br />
#* 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<br />
<br />
== Documentation ==<br />
<br />
# The project has user documentation:<br />
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
# The project has developer documentation:<br />
#* Including checkout and build instructions.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
#* Including commented code, ideally published for developer use. <br/><i>Examples: javadocs for Java applications, or Sphinx documentation for Python applications.</i><br />
#** https://www.orfeo-toolbox.org/packages/OTBSoftwareGuide.pdf and https://www.orfeo-toolbox.org/doxygen/<br />
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.<br />
#** https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech32.html#x63-43000032 and https://wiki.orfeo-toolbox.org/index.php/Contributors_guidelines<br />
==Release Procedure==<br />
<br />
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.<br />
<br />
# The project follows a defined release process:<br />
#* The release process is described in the OTB wiki https://wiki.orfeo-toolbox.org/index.php/How_to_Release<br />
#* Which includes execution of the testing process before releasing a stable release. <br />
# 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><br />
#* See OTB Cdash (nightly builds, unit tests and code coverage submissions): https://dash.orfeo-toolbox.org/<br />
# Release and testing processes provide sufficient detail for an experienced programmer to follow.<br />
#* 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<br />
<br />
= OSGeo Committees and Community =<br />
<br />
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.<br />
<br />
== Board ==<br />
<br />
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:<br />
<br />
# A project provide a Project Officer as a contract point:<br />
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]<br />
#* This person is established when the incubation committee recommends the project for graduation<br />
#* 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).<br />
<br />
== Marketing ==<br />
<br />
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:<br />
<br />
# 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:<br />
#* Application Overview https://live.osgeo.org/en/overview/otb_overview.html<br />
#* Application Quick Start https://live.osgeo.org/en/quickstart/otb_quickstart.html<br />
#* Logo https://live.osgeo.org/_images/logo-otb7.png<br />
#* Graphical Image https://git.orfeo-toolbox.org/otb-documents.git/tree/HEAD:/Artwork<br />
# 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><br />
#* 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.<br />
<br />
== Projects ==<br />
<br />
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. <br />
<br />
<i>As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.</i><br />
<br />
== SAC ==<br />
<br />
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:<br />
* A http://projectname.osgeo.org domain name.<br />
<br />
A project may optionally request SAC help to make use of:<br />
* OSGeo issue tracker<br />
* OSGeo mailing list<br />
* OSGeo svn<br />
* http://downloads.osgeo.org<br />
<br />
[[Category: Incubation]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Graduation_Checklist&diff=107217OTB Graduation Checklist2017-06-19T10:02:59Z<p>Wiki-Grizonnetm: /* Copyright and License */</p>
<hr />
<div>= Incubation Checklist =<br />
<br />
== Open ==<br />
<br />
The project has demonstrated that it has an open, active and healthy user and developer community: <br />
# Open: projects are expected to function in an open and public manner and include:<br />
#* Open source license(s),<br />
#** Apache License 2.0<br />
#* Open communication channels,<br />
#** The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#* Open decision making process,<br />
#** 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)<br />
#** 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.<br />
# Active and healthy community:<br />
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. <br/><br />
#** release process? LINK https://wiki.orfeo-toolbox.org/index.php/Release_planning<br />
#** bugs and feature requests? LINK https://bugs.orfeo-toolbox.org/my_view_page.php<br />
#** devel communication? LINK https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech1.html#x10-140001.4<br />
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. <br/><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]<br />
<br />
== Copyright and License ==<br />
<br />
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:<br />
# All project source code is available under an Open Source license.<br />
#* https://git.orfeo-toolbox.org/otb.git/blob/HEAD:/LICENSE<br />
# Project documentation is available under an open license, such as Creative Commons.<br />
#* Website and Cookbook are licensed under a Creative Commons Attribution-ShareAlike 4.0 International license (CC-BY-SA)<br />
# 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].<br />
#* https://wiki.osgeo.org/wiki/OTB_Code_Provenance_Review<br />
# The project maintains a list of all copyright holders identified in the Provenance Review Document.<br />
#* 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]<br />
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.<br />
#* 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.<br />
<br />
== Processes ==<br />
<br />
# The project has code under configuration management. <br/><i>Eg, subversion, git.</i><br />
#* Git https://git.orfeo-toolbox.org - There is also a mirror on GitHub: https://github.com/orfeotoolbox/OTB<br />
# The project uses an issue tracker and keeps the status of the issue tracker up to date.<br />
#* https://bugs.orfeo-toolbox.org/my_view_page.php<br />
# The project has documented its management processes. <br/><i>This is typically done within a Developers Guide or Project Management Plan.</i><br />
#* https://www.orfeo-toolbox.org/community/<br />
# 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><br />
#* 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/<br />
# 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><br />
#* 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<br />
<br />
== Documentation ==<br />
<br />
# The project has user documentation:<br />
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
# The project has developer documentation:<br />
#* Including checkout and build instructions.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
#* Including commented code, ideally published for developer use. <br/><i>Examples: javadocs for Java applications, or Sphinx documentation for Python applications.</i><br />
#** https://www.orfeo-toolbox.org/packages/OTBSoftwareGuide.pdf and https://www.orfeo-toolbox.org/doxygen/<br />
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.<br />
#** https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech32.html#x63-43000032 and https://wiki.orfeo-toolbox.org/index.php/Contributors_guidelines<br />
==Release Procedure==<br />
<br />
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.<br />
<br />
# The project follows a defined release process:<br />
#* The release process is described in the OTB wiki https://wiki.orfeo-toolbox.org/index.php/How_to_Release<br />
#* Which includes execution of the testing process before releasing a stable release. <br />
# 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><br />
#* See OTB Cdash (nightly builds, unit tests and code coverage submissions): https://dash.orfeo-toolbox.org/<br />
# Release and testing processes provide sufficient detail for an experienced programmer to follow.<br />
#* 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<br />
<br />
= OSGeo Committees and Community =<br />
<br />
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.<br />
<br />
== Board ==<br />
<br />
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:<br />
<br />
# A project provide a Project Officer as a contract point:<br />
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]<br />
#* This person is established when the incubation committee recommends the project for graduation<br />
#* 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).<br />
<br />
== Marketing ==<br />
<br />
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:<br />
<br />
# 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:<br />
#* Application Overview https://live.osgeo.org/en/overview/otb_overview.html<br />
#* Application Quick Start https://live.osgeo.org/en/quickstart/otb_quickstart.html<br />
#* Logo https://live.osgeo.org/_images/logo-otb7.png<br />
#* Graphical Image https://git.orfeo-toolbox.org/otb-documents.git/tree/HEAD:/Artwork<br />
# 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><br />
#* 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.<br />
<br />
== Projects ==<br />
<br />
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. <br />
<br />
<i>As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.</i><br />
<br />
== SAC ==<br />
<br />
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:<br />
* A http://projectname.osgeo.org domain name.<br />
<br />
A project may optionally request SAC help to make use of:<br />
* OSGeo issue tracker<br />
* OSGeo mailing list<br />
* OSGeo svn<br />
* http://downloads.osgeo.org<br />
<br />
[[Category: Incubation]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Graduation_Checklist&diff=107000OTB Graduation Checklist2017-05-29T08:45:41Z<p>Wiki-Grizonnetm: /* Marketing */</p>
<hr />
<div>= Incubation Checklist =<br />
<br />
== Open ==<br />
<br />
The project has demonstrated that it has an open, active and healthy user and developer community: <br />
# Open: projects are expected to function in an open and public manner and include:<br />
#* Open source license(s),<br />
#** Apache License 2.0<br />
#* Open communication channels,<br />
#** The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#* Open decision making process,<br />
#** 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)<br />
#** 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.<br />
# Active and healthy community:<br />
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. <br/><br />
#** release process? LINK https://wiki.orfeo-toolbox.org/index.php/Release_planning<br />
#** bugs and feature requests? LINK https://bugs.orfeo-toolbox.org/my_view_page.php<br />
#** devel communication? LINK https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech1.html#x10-140001.4<br />
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. <br/><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]<br />
<br />
== Copyright and License ==<br />
<br />
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:<br />
# All project source code is available under an Open Source license.<br />
#* https://git.orfeo-toolbox.org/otb.git/blob/HEAD:/LICENSE<br />
# Project documentation is available under an open license, such as Creative Commons.<br />
#* Website is creative commons, could not quite tell what the user guide uses.<br />
# 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].<br />
#* https://wiki.osgeo.org/wiki/OTB_Code_Provenance_Review<br />
# The project maintains a list of all copyright holders identified in the Provenance Review Document.<br />
#* 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]<br />
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.<br />
#* 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.<br />
<br />
== Processes ==<br />
<br />
# The project has code under configuration management. <br/><i>Eg, subversion, git.</i><br />
#* Git https://git.orfeo-toolbox.org - There is also a mirror on GitHub: https://github.com/orfeotoolbox/OTB<br />
# The project uses an issue tracker and keeps the status of the issue tracker up to date.<br />
#* https://bugs.orfeo-toolbox.org/my_view_page.php<br />
# The project has documented its management processes. <br/><i>This is typically done within a Developers Guide or Project Management Plan.</i><br />
#* https://www.orfeo-toolbox.org/community/<br />
# 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><br />
#* 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/<br />
# 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><br />
#* 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<br />
<br />
== Documentation ==<br />
<br />
# The project has user documentation:<br />
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
# The project has developer documentation:<br />
#* Including checkout and build instructions.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
#* Including commented code, ideally published for developer use. <br/><i>Examples: javadocs for Java applications, or Sphinx documentation for Python applications.</i><br />
#** https://www.orfeo-toolbox.org/packages/OTBSoftwareGuide.pdf and https://www.orfeo-toolbox.org/doxygen/<br />
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.<br />
#** https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech32.html#x63-43000032 and https://wiki.orfeo-toolbox.org/index.php/Contributors_guidelines<br />
==Release Procedure==<br />
<br />
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.<br />
<br />
# The project follows a defined release process:<br />
#* The release process is described in the OTB wiki https://wiki.orfeo-toolbox.org/index.php/How_to_Release<br />
#* Which includes execution of the testing process before releasing a stable release. <br />
# 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><br />
#* See OTB Cdash (nightly builds, unit tests and code coverage submissions): https://dash.orfeo-toolbox.org/<br />
# Release and testing processes provide sufficient detail for an experienced programmer to follow.<br />
#* 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<br />
<br />
= OSGeo Committees and Community =<br />
<br />
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.<br />
<br />
== Board ==<br />
<br />
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:<br />
<br />
# A project provide a Project Officer as a contract point:<br />
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]<br />
#* This person is established when the incubation committee recommends the project for graduation<br />
#* 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).<br />
<br />
== Marketing ==<br />
<br />
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:<br />
<br />
# 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:<br />
#* Application Overview https://live.osgeo.org/en/overview/otb_overview.html<br />
#* Application Quick Start https://live.osgeo.org/en/quickstart/otb_quickstart.html<br />
#* Logo https://live.osgeo.org/_images/logo-otb7.png<br />
#* Graphical Image https://git.orfeo-toolbox.org/otb-documents.git/tree/HEAD:/Artwork<br />
# 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><br />
#* 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.<br />
<br />
== Projects ==<br />
<br />
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. <br />
<br />
<i>As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.</i><br />
<br />
== SAC ==<br />
<br />
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:<br />
* A http://projectname.osgeo.org domain name.<br />
<br />
A project may optionally request SAC help to make use of:<br />
* OSGeo issue tracker<br />
* OSGeo mailing list<br />
* OSGeo svn<br />
* http://downloads.osgeo.org<br />
<br />
[[Category: Incubation]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Graduation_Checklist&diff=106999OTB Graduation Checklist2017-05-29T08:43:47Z<p>Wiki-Grizonnetm: /* Marketing */</p>
<hr />
<div>= Incubation Checklist =<br />
<br />
== Open ==<br />
<br />
The project has demonstrated that it has an open, active and healthy user and developer community: <br />
# Open: projects are expected to function in an open and public manner and include:<br />
#* Open source license(s),<br />
#** Apache License 2.0<br />
#* Open communication channels,<br />
#** The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#* Open decision making process,<br />
#** 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)<br />
#** 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.<br />
# Active and healthy community:<br />
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. <br/><br />
#** release process? LINK https://wiki.orfeo-toolbox.org/index.php/Release_planning<br />
#** bugs and feature requests? LINK https://bugs.orfeo-toolbox.org/my_view_page.php<br />
#** devel communication? LINK https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech1.html#x10-140001.4<br />
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. <br/><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]<br />
<br />
== Copyright and License ==<br />
<br />
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:<br />
# All project source code is available under an Open Source license.<br />
#* https://git.orfeo-toolbox.org/otb.git/blob/HEAD:/LICENSE<br />
# Project documentation is available under an open license, such as Creative Commons.<br />
#* Website is creative commons, could not quite tell what the user guide uses.<br />
# 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].<br />
#* https://wiki.osgeo.org/wiki/OTB_Code_Provenance_Review<br />
# The project maintains a list of all copyright holders identified in the Provenance Review Document.<br />
#* 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]<br />
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.<br />
#* 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.<br />
<br />
== Processes ==<br />
<br />
# The project has code under configuration management. <br/><i>Eg, subversion, git.</i><br />
#* Git https://git.orfeo-toolbox.org - There is also a mirror on GitHub: https://github.com/orfeotoolbox/OTB<br />
# The project uses an issue tracker and keeps the status of the issue tracker up to date.<br />
#* https://bugs.orfeo-toolbox.org/my_view_page.php<br />
# The project has documented its management processes. <br/><i>This is typically done within a Developers Guide or Project Management Plan.</i><br />
#* https://www.orfeo-toolbox.org/community/<br />
# 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><br />
#* 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/<br />
# 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><br />
#* 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<br />
<br />
== Documentation ==<br />
<br />
# The project has user documentation:<br />
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
# The project has developer documentation:<br />
#* Including checkout and build instructions.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
#* Including commented code, ideally published for developer use. <br/><i>Examples: javadocs for Java applications, or Sphinx documentation for Python applications.</i><br />
#** https://www.orfeo-toolbox.org/packages/OTBSoftwareGuide.pdf and https://www.orfeo-toolbox.org/doxygen/<br />
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.<br />
#** https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech32.html#x63-43000032 and https://wiki.orfeo-toolbox.org/index.php/Contributors_guidelines<br />
==Release Procedure==<br />
<br />
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.<br />
<br />
# The project follows a defined release process:<br />
#* The release process is described in the OTB wiki https://wiki.orfeo-toolbox.org/index.php/How_to_Release<br />
#* Which includes execution of the testing process before releasing a stable release. <br />
# 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><br />
#* See OTB Cdash (nightly builds, unit tests and code coverage submissions): https://dash.orfeo-toolbox.org/<br />
# Release and testing processes provide sufficient detail for an experienced programmer to follow.<br />
#* 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<br />
<br />
= OSGeo Committees and Community =<br />
<br />
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.<br />
<br />
== Board ==<br />
<br />
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:<br />
<br />
# A project provide a Project Officer as a contract point:<br />
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]<br />
#* This person is established when the incubation committee recommends the project for graduation<br />
#* 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).<br />
<br />
== Marketing ==<br />
<br />
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:<br />
<br />
# 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:<br />
#* Application Overview<br />
#* Application Quick Start<br />
#* Logo<br />
#* Graphical Image<br />
# 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><br />
#* 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.<br />
<br />
== Projects ==<br />
<br />
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. <br />
<br />
<i>As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.</i><br />
<br />
== SAC ==<br />
<br />
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:<br />
* A http://projectname.osgeo.org domain name.<br />
<br />
A project may optionally request SAC help to make use of:<br />
* OSGeo issue tracker<br />
* OSGeo mailing list<br />
* OSGeo svn<br />
* http://downloads.osgeo.org<br />
<br />
[[Category: Incubation]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=Contacts&diff=106998Contacts2017-05-29T08:31:30Z<p>Wiki-Grizonnetm: /* Software Projects */</p>
<hr />
<div>OSGeo Projects are freestanding entities, handled by their own Project Steering Committees. Each project has been asked to provide a representative to help coordinate OSGeo involvement. These volunteers are listed by project below:<br />
<br />
== General ==<br />
* General Foundation Info - info@osgeo.org - [mailto:info@osgeo.org] (emails are currently forwarded to 3 people: FrankW, JeffM, Jachym)<br />
* [[Executive Positions|President]] - [[Jeff McKenna]] - (president at osgeo.org)<br />
* [[Treasurer]] - [[Michael Smith]] - (treasurer at osgeo.org)<br />
* [[Secretary]] - [[Jáchym Čepický]] - (secretary at osgeo.org)<br />
* [[Board of Directors]]<br />
<br />
== Software Projects ==<br />
'''Web Mapping'''<br />
* [http://www.deegree.org deegree]: [http://wiki.deegree.org/deegreeWiki/StructuresAndProcedures PSC] - Contact: [[User:JensFitzke | Jens Fitzke]]<br />
* [http://geomajas.org Geomajas]: [http://www.geomajas.org/geomajas/project-steering-committee PSC] - Chair: Pieter De Graef (pieter.degraef at geosparc.com)<br />
* [http://www.geomoose.org/ GeoMoose]: [http://www.geomoose.org/rfc/rfc-1.html PSC] - Chair: - Brian Fischer (bfischer at houstoneng.com)<br />
* [http://geoserver.org GeoServer]: [http://docs.geoserver.org/latest/en/developer/policies/psc.html PSC] - Project Officer: Simone Giannecchini (simone.giannecchini at geo-solutions.it ) (checked 2014-10-09)<br />
* [http://www.mapbender.org Mapbender]: [http://www.mapbender.org/index.php/Category:PSC PSC] - Chair: Axel Schaefer<br />
* [http://www.mapfish.org MapFish]: [http://trac.mapfish.org/trac/mapfish/wiki/Community/PSC PSC] - Chair: [[User:Elem | Eric Lemoine]]<br />
* [http://mapguide.osgeo.org/ MapGuide Open Source]: [http://mapguide.osgeo.org/psc.html PSC] - Chair: Robert Bray (robert.bray at autodesk.com)<br />
* [http://mapserver.org/ MapServer]: [http://mapserver.org/development/rfc/ms-rfc-23.html PSC] - Chair: Stephen Lime (sdlime at comcast.net)<br />
* [http://openlayers.org/ OpenLayers]: [http://trac.openlayers.org/wiki/SteeringCommittee PSC] - Chair: [[User:Tschaub | Tim Schaub]]<br />
<br />
'''Desktop Applications'''<br />
* [http://grass.osgeo.org/ GRASS GIS]: [http://trac.osgeo.org/grass/wiki/PSC PSC] - Chair: [[Markus Neteler]]<br />
* [http://www.gvsig.org/ gvSIG]: - [[GvSIG Technical Project Committee|PSC]] - Chair: [[Manuel Madrid]]<br />
* [http://marble.kde.org/ Marble]: [http://edu.kde.org/marble/authors.php Authors] - Liaison Officer: [[Torsten Rahn]] <br />
* [http://www.ossim.org/ OSSIM]: [http://trac.osgeo.org/ossim/wiki/ossimgovernance PSC] - Chair: Garrett Potts<br />
* [http://www.qgis.org/ QGIS]: [http://www.qgis.org/en/site/getinvolved/governance/psc.html PSC] - Chair: [[User:Timlinux | Tim Sutton]]<br />
<br />
'''Geospatial Libraries'''<br />
* [http://fdo.osgeo.org/ FDO]: [http://fdo.osgeo.org/ Home Page] (link to PSC broken) - Chair: Greg Boone (greg.boone at autodesk.com)<br />
* [http://www.gdal.org/ GDAL/OGR]: [http://trac.osgeo.org/gdal/wiki/GovernanceAndCommunity PSC] - Chair: Even Rouault (even.rouault at spatialys.com)<br />
* [http://www.geotools.org/ GeoTools]: [http://docs.codehaus.org/display/GEOT/4+Project+Management+Committee PSC] - Project Officer Jody Garnett (jody.garnett at gmail.com) (checked 2014-10-09)<br />
* [http://geos.osgeo.org/ GEOS]: [http://trac.osgeo.org/geos/wiki/PSC PSC] - Chair: [[User:Strk | Sandro Santilli]] (strk at kbt.io)<br />
* [http://metacrs.osgeo.org/ MetaCRS]: [http://metacrs.osgeo.org PSC] - Chair: Frank Warmerdam (warmerdam@pobox.com)<br />
* [https://github.com/proj4php/proj4php/ Proj4php] - Chair : Julien Moquet (moquet dot julien at gmail dot com)<br />
* [http://postgis.net/ PostGIS]: [http://postgis.net/docs/postgis_introduction.html#psc PSC] - Chair: [[User:Pwramsey3 | Paul Ramsey]]<br />
* [http://pgrouting.org/ pgRouting]: [http://pgrouting.org/development.html PSC] - Chair: [[User:Woodbri | Stephen Woodbridge]]<br />
* [https://www.orfeo-toolbox.org/ Orfeo Toolbox]: [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee PSC] - OSGeo Contact Officer [[User:Grizonnetm | Manuel Grizonnet ]](CNES manuel.grizonnet AT cnes DOT fr)<br />
<br />
'''Metadata Catalog'''<br />
* [http://geonetwork-opensource.org GeoNetwork opensource]: [http://trac.osgeo.org/geonetwork/wiki/PSC PSC] - Chair: [[User:Ticheler | Jeroen Ticheler]] (Jeroen.Ticheler at geocat.net) (checked 2014-10-09)<br />
* [http://pycsw.org pycsw]: [http://pycsw.org/community/psc.html PSC] - Chair: [[Angelos_Tzotsos]] (tzotsos at gmail.com)<br />
<br />
'''Spatio-Temporal Analytics'''<br />
* [http://www.rasdaman.org rasdaman opensource]: [http://rasdaman.org/wiki/Governance PSC] - Chair: [[User:Pebau | Peter Baumann]] (baumann at rasdaman.com) (checked 2014-10-09)<br />
<br />
== Committees ==<br />
* [[CodeOfConduct Committee]] -<br />
* [[Conference Committee]] - <br />
* [[Education and Curriculum Committee]] - Charlie Schweik - cschweik at pubpol.umass.edu (checked 2014-10-09)<br />
* [[Finance Committee]] - [[User:Dmorissette|Daniel Morissette]] - dmorissette at mapgears.com (checked 2014-10-09)<br />
* [[Incubation Committee]] - Jody Garnett - jody.garnett at gmail.com (checked 2014-10-09)<br />
* [[Marketing Committee]] - Cameron Shorter - cameron.shorter at gmail.com (checked 2014-10-09)<br />
* [[Open Geoscience Committee]] -<br />
* [[Public Geospatial Data Committee]] - [[User:Bitner|David Bitner]] - bitner at dbspatial dot com (checked 2014-10-09)<br />
* [[SAC|System Administration Committee]] - Alex Mandel - tech_dev at wildintellect.com (checked 2014-10-09)<br />
* [[UnitedNations Committee]] -<br />
* [[Website Committee]] - Christopher Schmidt - crschmidt at crschmidt.net<br />
* OSGeo [[Journal]]<br />
<br />
== Packaging ==<br />
* [http://live.osgeo.org OSGeo-Live] - Cameron Shorter - cameron.shorter at gmail.com<br />
* [http://osgeo4w.osgeo.org OSGeo4W] - [[User:Jef | Jürgen Fischer]] - jef at norbit.de<br />
<br />
== Local Chapters ==<br />
<br />
Contacts list for the [[:Category:Local_Chapters|local chapters]]:<br />
* [[Africa Local Chapter]] - [[User:Gfleming|Gavin Fleming]]<br />
* [[Aust-NZ]] - Australia and New Zealand Chapter- Bruce Bannerman - bruce.bannerman.osgeo at gmail.com<br />
* [[Belgium]] - [[User:dirkf|Dirk Frigne]] - founder of the geomajas.org framework - OSGeo Advocate - dirk AT geomajas DOT org<br />
* [[Brazil]] - Helton Uchoa - engenheiro.uchoa at gmail.com<br />
* [[California]] - Landon Blake - sunburned.surveyor at gmail dot com<br />
* [[Cascadia|CUGOS Cascadia Chapter US]] - [[User:Racicot|Aaron Racicot]] - aaronr at cugos.org (checked 2014-10-09)<br />
* [[China]] - Chen Rongguo - chenrg at lreis.ac.cn<br />
* [[D-A-CH]] (German language) - [[User:Mlechner|Marco Lechner]] (checked 2014-09-30)<br />
* [[Finland]] - Kari Salovaara - kari.salovaara at pp1.inet.fi (updated 2015-09-18)<br />
* [[Francophone]] - board at osgeo.asso dot fr / president at osgeo.asso.fr (Etienne Delay) (checked 2014-09-30)<br />
* [[Greek]] - [[User:kotzino|Dimitris Kotzinos]] - kotzino at csd dot uoc dot gr (checked 2014-09-30)<br />
* [[Ireland]] - Daniel McInerney - daniel . o . mcinerney at gmail.com<br />
* [[India]] - P.S. Roy - psroy13 at gmail.com<br />
* [[Italy]] - [[User:epifanio|Massimo Di Stefano]] - IT -- epiesasha at me dot com<br />
* [[Japan]] - Mr. Mori Toru - moritoru at orkney.co.jp (checked 2014-09-30)<br />
* [[Korea | Korean Chapter]] - [[User:Endofcap|Sanghee Shin]] - shshin at gaia3d.com or endofcap at gmail.com (checked 2014-09-30)<br />
* [[KSA Chapter]] - Awase Khirni Syed - awasekhirni at gmail.com<br />
* [[Nederlands | Dutch language Chapter]] - [[User:Just|Just van den Broecke]] (secretary) [[User:Geejee|Gert-Jan van der Weijden]] (president). info at osgeo dot nl (checked 2014-10-08)<br />
* [[Ottawa Chapter]] - Fabien Ancelin - fabien.ancelin at gmail.com <br />
* [[PDX-OSGEO]] - Oregon, US Chapter -- [[User:EliL|Eli L Adam]] - contact on user page (checked 2014-09-30)<br />
* [[Philippines]] - [[User:maning|Maning Sambale]] - emmanuel dot sambale at gmail dot com (checked 2014-10-09)<br />
* [[Poland]] - Tomasz Kubik - tomasz kubik at pwr wroc pl (checked 2014-09-30)<br />
* [[Portugal]] - Jorge Gustavo Rocha - [[Jorge_Gustavo_Rocha]], Giovanni Manghi - [[Giovanni_Manghi]]<br />
* [[Romanian]] - [[User:Vasile|Vasile Crăciunescu]] - vasile at geo-spatial dot org<br />
* [[Quebec]] - [[User:Dmorissette|Daniel Morissette]] - dmorissette at mapgears dot com (checked 2014-10-09)<br />
* [[Spanish]] - [[Pedro-Juan Ferrer]] - vehrka at gmail.com (checked 2014-10-09)<br />
* [[Taiwan]] - Sander Borghuis - s.borghuis at geo.uu.nl '''(mail not delivered)'''<br />
* [[Twin_Cities]] - Twin Cities, MN -- [[User:Bitner|David Bitner]] - bitner at dbspatial dot com<br />
* [[Yukon Chapter]] - [[User:hammj|Jeff Hamm]] - jeff at geoprism dot ca<br />
* [http://www.osgeo.org/uk UK] - [[User:JoCook|Jo Cook]]<br />
<br />
== Infrastructure ==<br />
<br />
* [[SAC:Primary Administrators]]<br />
<br />
== Local Representatives ==<br />
<br />
* list of local leaders by region: [[OSGeo Advocate]]<br />
<br />
[[Category:Board]]<br />
[[Category:Education]]<br />
[[Category:Incubation]]<br />
[[Category:Infrastructure]]<br />
[[Category:PSC]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=Contacts&diff=106997Contacts2017-05-29T08:31:02Z<p>Wiki-Grizonnetm: /* Software Projects */</p>
<hr />
<div>OSGeo Projects are freestanding entities, handled by their own Project Steering Committees. Each project has been asked to provide a representative to help coordinate OSGeo involvement. These volunteers are listed by project below:<br />
<br />
== General ==<br />
* General Foundation Info - info@osgeo.org - [mailto:info@osgeo.org] (emails are currently forwarded to 3 people: FrankW, JeffM, Jachym)<br />
* [[Executive Positions|President]] - [[Jeff McKenna]] - (president at osgeo.org)<br />
* [[Treasurer]] - [[Michael Smith]] - (treasurer at osgeo.org)<br />
* [[Secretary]] - [[Jáchym Čepický]] - (secretary at osgeo.org)<br />
* [[Board of Directors]]<br />
<br />
== Software Projects ==<br />
'''Web Mapping'''<br />
* [http://www.deegree.org deegree]: [http://wiki.deegree.org/deegreeWiki/StructuresAndProcedures PSC] - Contact: [[User:JensFitzke | Jens Fitzke]]<br />
* [http://geomajas.org Geomajas]: [http://www.geomajas.org/geomajas/project-steering-committee PSC] - Chair: Pieter De Graef (pieter.degraef at geosparc.com)<br />
* [http://www.geomoose.org/ GeoMoose]: [http://www.geomoose.org/rfc/rfc-1.html PSC] - Chair: - Brian Fischer (bfischer at houstoneng.com)<br />
* [http://geoserver.org GeoServer]: [http://docs.geoserver.org/latest/en/developer/policies/psc.html PSC] - Project Officer: Simone Giannecchini (simone.giannecchini at geo-solutions.it ) (checked 2014-10-09)<br />
* [http://www.mapbender.org Mapbender]: [http://www.mapbender.org/index.php/Category:PSC PSC] - Chair: Axel Schaefer<br />
* [http://www.mapfish.org MapFish]: [http://trac.mapfish.org/trac/mapfish/wiki/Community/PSC PSC] - Chair: [[User:Elem | Eric Lemoine]]<br />
* [http://mapguide.osgeo.org/ MapGuide Open Source]: [http://mapguide.osgeo.org/psc.html PSC] - Chair: Robert Bray (robert.bray at autodesk.com)<br />
* [http://mapserver.org/ MapServer]: [http://mapserver.org/development/rfc/ms-rfc-23.html PSC] - Chair: Stephen Lime (sdlime at comcast.net)<br />
* [http://openlayers.org/ OpenLayers]: [http://trac.openlayers.org/wiki/SteeringCommittee PSC] - Chair: [[User:Tschaub | Tim Schaub]]<br />
<br />
'''Desktop Applications'''<br />
* [http://grass.osgeo.org/ GRASS GIS]: [http://trac.osgeo.org/grass/wiki/PSC PSC] - Chair: [[Markus Neteler]]<br />
* [http://www.gvsig.org/ gvSIG]: - [[GvSIG Technical Project Committee|PSC]] - Chair: [[Manuel Madrid]]<br />
* [http://marble.kde.org/ Marble]: [http://edu.kde.org/marble/authors.php Authors] - Liaison Officer: [[Torsten Rahn]] <br />
* [http://www.ossim.org/ OSSIM]: [http://trac.osgeo.org/ossim/wiki/ossimgovernance PSC] - Chair: Garrett Potts<br />
* [http://www.qgis.org/ QGIS]: [http://www.qgis.org/en/site/getinvolved/governance/psc.html PSC] - Chair: [[User:Timlinux | Tim Sutton]]<br />
<br />
'''Geospatial Libraries'''<br />
* [http://fdo.osgeo.org/ FDO]: [http://fdo.osgeo.org/ Home Page] (link to PSC broken) - Chair: Greg Boone (greg.boone at autodesk.com)<br />
* [http://www.gdal.org/ GDAL/OGR]: [http://trac.osgeo.org/gdal/wiki/GovernanceAndCommunity PSC] - Chair: Even Rouault (even.rouault at spatialys.com)<br />
* [http://www.geotools.org/ GeoTools]: [http://docs.codehaus.org/display/GEOT/4+Project+Management+Committee PSC] - Project Officer Jody Garnett (jody.garnett at gmail.com) (checked 2014-10-09)<br />
* [http://geos.osgeo.org/ GEOS]: [http://trac.osgeo.org/geos/wiki/PSC PSC] - Chair: [[User:Strk | Sandro Santilli]] (strk at kbt.io)<br />
* [http://metacrs.osgeo.org/ MetaCRS]: [http://metacrs.osgeo.org PSC] - Chair: Frank Warmerdam (warmerdam@pobox.com)<br />
* [https://github.com/proj4php/proj4php/ Proj4php] - Chair : Julien Moquet (moquet dot julien at gmail dot com)<br />
* [http://postgis.net/ PostGIS]: [http://postgis.net/docs/postgis_introduction.html#psc PSC] - Chair: [[User:Pwramsey3 | Paul Ramsey]]<br />
* [http://pgrouting.org/ pgRouting]: [http://pgrouting.org/development.html PSC] - Chair: [[User:Woodbri | Stephen Woodbridge]]<br />
* [https://www.orfeo-toolbox.org/ Orfeo Toolbox]: [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee PSC] - OSGeo Contact Officer [[User:GrizonnetM | Manuel Grizonnet ]](CNES manuel.grizonnet AT cnes DOT fr)<br />
<br />
'''Metadata Catalog'''<br />
* [http://geonetwork-opensource.org GeoNetwork opensource]: [http://trac.osgeo.org/geonetwork/wiki/PSC PSC] - Chair: [[User:Ticheler | Jeroen Ticheler]] (Jeroen.Ticheler at geocat.net) (checked 2014-10-09)<br />
* [http://pycsw.org pycsw]: [http://pycsw.org/community/psc.html PSC] - Chair: [[Angelos_Tzotsos]] (tzotsos at gmail.com)<br />
<br />
'''Spatio-Temporal Analytics'''<br />
* [http://www.rasdaman.org rasdaman opensource]: [http://rasdaman.org/wiki/Governance PSC] - Chair: [[User:Pebau | Peter Baumann]] (baumann at rasdaman.com) (checked 2014-10-09)<br />
<br />
== Committees ==<br />
* [[CodeOfConduct Committee]] -<br />
* [[Conference Committee]] - <br />
* [[Education and Curriculum Committee]] - Charlie Schweik - cschweik at pubpol.umass.edu (checked 2014-10-09)<br />
* [[Finance Committee]] - [[User:Dmorissette|Daniel Morissette]] - dmorissette at mapgears.com (checked 2014-10-09)<br />
* [[Incubation Committee]] - Jody Garnett - jody.garnett at gmail.com (checked 2014-10-09)<br />
* [[Marketing Committee]] - Cameron Shorter - cameron.shorter at gmail.com (checked 2014-10-09)<br />
* [[Open Geoscience Committee]] -<br />
* [[Public Geospatial Data Committee]] - [[User:Bitner|David Bitner]] - bitner at dbspatial dot com (checked 2014-10-09)<br />
* [[SAC|System Administration Committee]] - Alex Mandel - tech_dev at wildintellect.com (checked 2014-10-09)<br />
* [[UnitedNations Committee]] -<br />
* [[Website Committee]] - Christopher Schmidt - crschmidt at crschmidt.net<br />
* OSGeo [[Journal]]<br />
<br />
== Packaging ==<br />
* [http://live.osgeo.org OSGeo-Live] - Cameron Shorter - cameron.shorter at gmail.com<br />
* [http://osgeo4w.osgeo.org OSGeo4W] - [[User:Jef | Jürgen Fischer]] - jef at norbit.de<br />
<br />
== Local Chapters ==<br />
<br />
Contacts list for the [[:Category:Local_Chapters|local chapters]]:<br />
* [[Africa Local Chapter]] - [[User:Gfleming|Gavin Fleming]]<br />
* [[Aust-NZ]] - Australia and New Zealand Chapter- Bruce Bannerman - bruce.bannerman.osgeo at gmail.com<br />
* [[Belgium]] - [[User:dirkf|Dirk Frigne]] - founder of the geomajas.org framework - OSGeo Advocate - dirk AT geomajas DOT org<br />
* [[Brazil]] - Helton Uchoa - engenheiro.uchoa at gmail.com<br />
* [[California]] - Landon Blake - sunburned.surveyor at gmail dot com<br />
* [[Cascadia|CUGOS Cascadia Chapter US]] - [[User:Racicot|Aaron Racicot]] - aaronr at cugos.org (checked 2014-10-09)<br />
* [[China]] - Chen Rongguo - chenrg at lreis.ac.cn<br />
* [[D-A-CH]] (German language) - [[User:Mlechner|Marco Lechner]] (checked 2014-09-30)<br />
* [[Finland]] - Kari Salovaara - kari.salovaara at pp1.inet.fi (updated 2015-09-18)<br />
* [[Francophone]] - board at osgeo.asso dot fr / president at osgeo.asso.fr (Etienne Delay) (checked 2014-09-30)<br />
* [[Greek]] - [[User:kotzino|Dimitris Kotzinos]] - kotzino at csd dot uoc dot gr (checked 2014-09-30)<br />
* [[Ireland]] - Daniel McInerney - daniel . o . mcinerney at gmail.com<br />
* [[India]] - P.S. Roy - psroy13 at gmail.com<br />
* [[Italy]] - [[User:epifanio|Massimo Di Stefano]] - IT -- epiesasha at me dot com<br />
* [[Japan]] - Mr. Mori Toru - moritoru at orkney.co.jp (checked 2014-09-30)<br />
* [[Korea | Korean Chapter]] - [[User:Endofcap|Sanghee Shin]] - shshin at gaia3d.com or endofcap at gmail.com (checked 2014-09-30)<br />
* [[KSA Chapter]] - Awase Khirni Syed - awasekhirni at gmail.com<br />
* [[Nederlands | Dutch language Chapter]] - [[User:Just|Just van den Broecke]] (secretary) [[User:Geejee|Gert-Jan van der Weijden]] (president). info at osgeo dot nl (checked 2014-10-08)<br />
* [[Ottawa Chapter]] - Fabien Ancelin - fabien.ancelin at gmail.com <br />
* [[PDX-OSGEO]] - Oregon, US Chapter -- [[User:EliL|Eli L Adam]] - contact on user page (checked 2014-09-30)<br />
* [[Philippines]] - [[User:maning|Maning Sambale]] - emmanuel dot sambale at gmail dot com (checked 2014-10-09)<br />
* [[Poland]] - Tomasz Kubik - tomasz kubik at pwr wroc pl (checked 2014-09-30)<br />
* [[Portugal]] - Jorge Gustavo Rocha - [[Jorge_Gustavo_Rocha]], Giovanni Manghi - [[Giovanni_Manghi]]<br />
* [[Romanian]] - [[User:Vasile|Vasile Crăciunescu]] - vasile at geo-spatial dot org<br />
* [[Quebec]] - [[User:Dmorissette|Daniel Morissette]] - dmorissette at mapgears dot com (checked 2014-10-09)<br />
* [[Spanish]] - [[Pedro-Juan Ferrer]] - vehrka at gmail.com (checked 2014-10-09)<br />
* [[Taiwan]] - Sander Borghuis - s.borghuis at geo.uu.nl '''(mail not delivered)'''<br />
* [[Twin_Cities]] - Twin Cities, MN -- [[User:Bitner|David Bitner]] - bitner at dbspatial dot com<br />
* [[Yukon Chapter]] - [[User:hammj|Jeff Hamm]] - jeff at geoprism dot ca<br />
* [http://www.osgeo.org/uk UK] - [[User:JoCook|Jo Cook]]<br />
<br />
== Infrastructure ==<br />
<br />
* [[SAC:Primary Administrators]]<br />
<br />
== Local Representatives ==<br />
<br />
* list of local leaders by region: [[OSGeo Advocate]]<br />
<br />
[[Category:Board]]<br />
[[Category:Education]]<br />
[[Category:Incubation]]<br />
[[Category:Infrastructure]]<br />
[[Category:PSC]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Graduation_Checklist&diff=106996OTB Graduation Checklist2017-05-29T08:29:12Z<p>Wiki-Grizonnetm: /* Release Procedure */</p>
<hr />
<div>= Incubation Checklist =<br />
<br />
== Open ==<br />
<br />
The project has demonstrated that it has an open, active and healthy user and developer community: <br />
# Open: projects are expected to function in an open and public manner and include:<br />
#* Open source license(s),<br />
#** Apache License 2.0<br />
#* Open communication channels,<br />
#** The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#* Open decision making process,<br />
#** 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)<br />
#** 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.<br />
# Active and healthy community:<br />
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. <br/><br />
#** release process? LINK https://wiki.orfeo-toolbox.org/index.php/Release_planning<br />
#** bugs and feature requests? LINK https://bugs.orfeo-toolbox.org/my_view_page.php<br />
#** devel communication? LINK https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech1.html#x10-140001.4<br />
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. <br/><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]<br />
<br />
== Copyright and License ==<br />
<br />
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:<br />
# All project source code is available under an Open Source license.<br />
#* https://git.orfeo-toolbox.org/otb.git/blob/HEAD:/LICENSE<br />
# Project documentation is available under an open license, such as Creative Commons.<br />
#* Website is creative commons, could not quite tell what the user guide uses.<br />
# 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].<br />
#* https://wiki.osgeo.org/wiki/OTB_Code_Provenance_Review<br />
# The project maintains a list of all copyright holders identified in the Provenance Review Document.<br />
#* 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]<br />
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.<br />
#* 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.<br />
<br />
== Processes ==<br />
<br />
# The project has code under configuration management. <br/><i>Eg, subversion, git.</i><br />
#* Git https://git.orfeo-toolbox.org - There is also a mirror on GitHub: https://github.com/orfeotoolbox/OTB<br />
# The project uses an issue tracker and keeps the status of the issue tracker up to date.<br />
#* https://bugs.orfeo-toolbox.org/my_view_page.php<br />
# The project has documented its management processes. <br/><i>This is typically done within a Developers Guide or Project Management Plan.</i><br />
#* https://www.orfeo-toolbox.org/community/<br />
# 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><br />
#* 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/<br />
# 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><br />
#* 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<br />
<br />
== Documentation ==<br />
<br />
# The project has user documentation:<br />
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
# The project has developer documentation:<br />
#* Including checkout and build instructions.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
#* Including commented code, ideally published for developer use. <br/><i>Examples: javadocs for Java applications, or Sphinx documentation for Python applications.</i><br />
#** https://www.orfeo-toolbox.org/packages/OTBSoftwareGuide.pdf and https://www.orfeo-toolbox.org/doxygen/<br />
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.<br />
#** https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech32.html#x63-43000032 and https://wiki.orfeo-toolbox.org/index.php/Contributors_guidelines<br />
==Release Procedure==<br />
<br />
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.<br />
<br />
# The project follows a defined release process:<br />
#* The release process is described in the OTB wiki https://wiki.orfeo-toolbox.org/index.php/How_to_Release<br />
#* Which includes execution of the testing process before releasing a stable release. <br />
# 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><br />
#* See OTB Cdash (nightly builds, unit tests and code coverage submissions): https://dash.orfeo-toolbox.org/<br />
# Release and testing processes provide sufficient detail for an experienced programmer to follow.<br />
#* 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<br />
<br />
= OSGeo Committees and Community =<br />
<br />
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.<br />
<br />
== Board ==<br />
<br />
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:<br />
<br />
# A project provide a Project Officer as a contract point:<br />
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]<br />
#* This person is established when the incubation committee recommends the project for graduation<br />
#* 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).<br />
<br />
== Marketing ==<br />
<br />
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:<br />
<br />
# 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:<br />
#* Application Overview<br />
#* Application Quick Start<br />
#* Logo<br />
#* Graphical Image<br />
# 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><br />
<br />
== Projects ==<br />
<br />
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. <br />
<br />
<i>As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.</i><br />
<br />
== SAC ==<br />
<br />
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:<br />
* A http://projectname.osgeo.org domain name.<br />
<br />
A project may optionally request SAC help to make use of:<br />
* OSGeo issue tracker<br />
* OSGeo mailing list<br />
* OSGeo svn<br />
* http://downloads.osgeo.org<br />
<br />
[[Category: Incubation]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Graduation_Checklist&diff=106994OTB Graduation Checklist2017-05-29T08:26:23Z<p>Wiki-Grizonnetm: /* Processes */</p>
<hr />
<div>= Incubation Checklist =<br />
<br />
== Open ==<br />
<br />
The project has demonstrated that it has an open, active and healthy user and developer community: <br />
# Open: projects are expected to function in an open and public manner and include:<br />
#* Open source license(s),<br />
#** Apache License 2.0<br />
#* Open communication channels,<br />
#** The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#* Open decision making process,<br />
#** 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)<br />
#** 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.<br />
# Active and healthy community:<br />
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. <br/><br />
#** release process? LINK https://wiki.orfeo-toolbox.org/index.php/Release_planning<br />
#** bugs and feature requests? LINK https://bugs.orfeo-toolbox.org/my_view_page.php<br />
#** devel communication? LINK https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech1.html#x10-140001.4<br />
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. <br/><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]<br />
<br />
== Copyright and License ==<br />
<br />
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:<br />
# All project source code is available under an Open Source license.<br />
#* https://git.orfeo-toolbox.org/otb.git/blob/HEAD:/LICENSE<br />
# Project documentation is available under an open license, such as Creative Commons.<br />
#* Website is creative commons, could not quite tell what the user guide uses.<br />
# 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].<br />
#* https://wiki.osgeo.org/wiki/OTB_Code_Provenance_Review<br />
# The project maintains a list of all copyright holders identified in the Provenance Review Document.<br />
#* 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]<br />
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.<br />
#* 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.<br />
<br />
== Processes ==<br />
<br />
# The project has code under configuration management. <br/><i>Eg, subversion, git.</i><br />
#* Git https://git.orfeo-toolbox.org - There is also a mirror on GitHub: https://github.com/orfeotoolbox/OTB<br />
# The project uses an issue tracker and keeps the status of the issue tracker up to date.<br />
#* https://bugs.orfeo-toolbox.org/my_view_page.php<br />
# The project has documented its management processes. <br/><i>This is typically done within a Developers Guide or Project Management Plan.</i><br />
#* https://www.orfeo-toolbox.org/community/<br />
# 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><br />
#* 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/<br />
# 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><br />
#* 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<br />
<br />
== Documentation ==<br />
<br />
# The project has user documentation:<br />
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
# The project has developer documentation:<br />
#* Including checkout and build instructions.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
#* Including commented code, ideally published for developer use. <br/><i>Examples: javadocs for Java applications, or Sphinx documentation for Python applications.</i><br />
#** https://www.orfeo-toolbox.org/packages/OTBSoftwareGuide.pdf and https://www.orfeo-toolbox.org/doxygen/<br />
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.<br />
#** https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech32.html#x63-43000032 and https://wiki.orfeo-toolbox.org/index.php/Contributors_guidelines<br />
==Release Procedure==<br />
<br />
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.<br />
<br />
# The project follows a defined release process:<br />
#* The release process is described in the OTB wiki https://wiki.orfeo-toolbox.org/index.php/How_to_Release<br />
#* Which includes execution of the testing process before releasing a stable release. <br />
# 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><br />
#* See OTB Cdash (nightly builds, unit tests and code coverage submissions): https://dash.orfeo-toolbox.org/<br />
# Release and testing processes provide sufficient detail for an experienced programmer to follow.<br />
<br />
<br />
= OSGeo Committees and Community =<br />
<br />
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.<br />
<br />
== Board ==<br />
<br />
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:<br />
<br />
# A project provide a Project Officer as a contract point:<br />
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]<br />
#* This person is established when the incubation committee recommends the project for graduation<br />
#* 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).<br />
<br />
== Marketing ==<br />
<br />
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:<br />
<br />
# 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:<br />
#* Application Overview<br />
#* Application Quick Start<br />
#* Logo<br />
#* Graphical Image<br />
# 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><br />
<br />
== Projects ==<br />
<br />
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. <br />
<br />
<i>As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.</i><br />
<br />
== SAC ==<br />
<br />
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:<br />
* A http://projectname.osgeo.org domain name.<br />
<br />
A project may optionally request SAC help to make use of:<br />
* OSGeo issue tracker<br />
* OSGeo mailing list<br />
* OSGeo svn<br />
* http://downloads.osgeo.org<br />
<br />
[[Category: Incubation]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Graduation_Checklist&diff=106992OTB Graduation Checklist2017-05-29T08:25:50Z<p>Wiki-Grizonnetm: /* Copyright and License */</p>
<hr />
<div>= Incubation Checklist =<br />
<br />
== Open ==<br />
<br />
The project has demonstrated that it has an open, active and healthy user and developer community: <br />
# Open: projects are expected to function in an open and public manner and include:<br />
#* Open source license(s),<br />
#** Apache License 2.0<br />
#* Open communication channels,<br />
#** The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#* Open decision making process,<br />
#** 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)<br />
#** 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.<br />
# Active and healthy community:<br />
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. <br/><br />
#** release process? LINK https://wiki.orfeo-toolbox.org/index.php/Release_planning<br />
#** bugs and feature requests? LINK https://bugs.orfeo-toolbox.org/my_view_page.php<br />
#** devel communication? LINK https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech1.html#x10-140001.4<br />
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. <br/><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]<br />
<br />
== Copyright and License ==<br />
<br />
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:<br />
# All project source code is available under an Open Source license.<br />
#* https://git.orfeo-toolbox.org/otb.git/blob/HEAD:/LICENSE<br />
# Project documentation is available under an open license, such as Creative Commons.<br />
#* Website is creative commons, could not quite tell what the user guide uses.<br />
# 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].<br />
#* https://wiki.osgeo.org/wiki/OTB_Code_Provenance_Review<br />
# The project maintains a list of all copyright holders identified in the Provenance Review Document.<br />
#* 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]<br />
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.<br />
#* 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.<br />
<br />
== Processes ==<br />
<br />
# The project has code under configuration management. <br/><i>Eg, subversion, git.</i><br />
#* Git https://git.orfeo-toolbox.org - There is a mirror on Gitub: https://github.com/orfeotoolbox/OTB<br />
# The project uses an issue tracker and keeps the status of the issue tracker up to date.<br />
#* https://bugs.orfeo-toolbox.org/my_view_page.php<br />
# The project has documented its management processes. <br/><i>This is typically done within a Developers Guide or Project Management Plan.</i><br />
#* https://www.orfeo-toolbox.org/community/<br />
# 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><br />
#* 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/<br />
# 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><br />
#* 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<br />
<br />
== Documentation ==<br />
<br />
# The project has user documentation:<br />
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
# The project has developer documentation:<br />
#* Including checkout and build instructions.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
#* Including commented code, ideally published for developer use. <br/><i>Examples: javadocs for Java applications, or Sphinx documentation for Python applications.</i><br />
#** https://www.orfeo-toolbox.org/packages/OTBSoftwareGuide.pdf and https://www.orfeo-toolbox.org/doxygen/<br />
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.<br />
#** https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech32.html#x63-43000032 and https://wiki.orfeo-toolbox.org/index.php/Contributors_guidelines<br />
==Release Procedure==<br />
<br />
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.<br />
<br />
# The project follows a defined release process:<br />
#* The release process is described in the OTB wiki https://wiki.orfeo-toolbox.org/index.php/How_to_Release<br />
#* Which includes execution of the testing process before releasing a stable release. <br />
# 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><br />
#* See OTB Cdash (nightly builds, unit tests and code coverage submissions): https://dash.orfeo-toolbox.org/<br />
# Release and testing processes provide sufficient detail for an experienced programmer to follow.<br />
<br />
<br />
= OSGeo Committees and Community =<br />
<br />
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.<br />
<br />
== Board ==<br />
<br />
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:<br />
<br />
# A project provide a Project Officer as a contract point:<br />
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]<br />
#* This person is established when the incubation committee recommends the project for graduation<br />
#* 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).<br />
<br />
== Marketing ==<br />
<br />
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:<br />
<br />
# 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:<br />
#* Application Overview<br />
#* Application Quick Start<br />
#* Logo<br />
#* Graphical Image<br />
# 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><br />
<br />
== Projects ==<br />
<br />
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. <br />
<br />
<i>As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.</i><br />
<br />
== SAC ==<br />
<br />
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:<br />
* A http://projectname.osgeo.org domain name.<br />
<br />
A project may optionally request SAC help to make use of:<br />
* OSGeo issue tracker<br />
* OSGeo mailing list<br />
* OSGeo svn<br />
* http://downloads.osgeo.org<br />
<br />
[[Category: Incubation]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Graduation_Checklist&diff=106991OTB Graduation Checklist2017-05-29T08:23:45Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>= Incubation Checklist =<br />
<br />
== Open ==<br />
<br />
The project has demonstrated that it has an open, active and healthy user and developer community: <br />
# Open: projects are expected to function in an open and public manner and include:<br />
#* Open source license(s),<br />
#** Apache License 2.0<br />
#* Open communication channels,<br />
#** The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#* Open decision making process,<br />
#** 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)<br />
#** 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.<br />
# Active and healthy community:<br />
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. <br/><br />
#** release process? LINK https://wiki.orfeo-toolbox.org/index.php/Release_planning<br />
#** bugs and feature requests? LINK https://bugs.orfeo-toolbox.org/my_view_page.php<br />
#** devel communication? LINK https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech1.html#x10-140001.4<br />
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. <br/><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]<br />
<br />
== Copyright and License ==<br />
<br />
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:<br />
# All project source code is available under an Open Source license.<br />
#* https://git.orfeo-toolbox.org/otb.git/blob/HEAD:/LICENSE<br />
# Project documentation is available under an open license, such as Creative Commons.<br />
#* Website is creative commons, could not quite tell what the user guide uses.<br />
# 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].<br />
#* https://wiki.osgeo.org/wiki/OTB_Code_Provenance_Review<br />
# The project maintains a list of all copyright holders identified in the Provenance Review Document.<br />
#* 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]<br />
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.<br />
#* 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.<br />
<br />
== Processes ==<br />
<br />
# The project has code under configuration management. <br/><i>Eg, subversion, git.</i><br />
#* Git https://git.orfeo-toolbox.org - There is a mirror on Gitub: https://github.com/orfeotoolbox/OTB<br />
# The project uses an issue tracker and keeps the status of the issue tracker up to date.<br />
#* https://bugs.orfeo-toolbox.org/my_view_page.php<br />
# The project has documented its management processes. <br/><i>This is typically done within a Developers Guide or Project Management Plan.</i><br />
#* https://www.orfeo-toolbox.org/community/<br />
# 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><br />
#* 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/<br />
# 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><br />
#* 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<br />
<br />
== Documentation ==<br />
<br />
# The project has user documentation:<br />
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
# The project has developer documentation:<br />
#* Including checkout and build instructions.<br />
#** FAQ English https://www.orfeo-toolbox.org/packages/OTB-FAQ.pdf<br />
#* Including commented code, ideally published for developer use. <br/><i>Examples: javadocs for Java applications, or Sphinx documentation for Python applications.</i><br />
#** https://www.orfeo-toolbox.org/packages/OTBSoftwareGuide.pdf and https://www.orfeo-toolbox.org/doxygen/<br />
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.<br />
#** https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech32.html#x63-43000032 and https://wiki.orfeo-toolbox.org/index.php/Contributors_guidelines<br />
==Release Procedure==<br />
<br />
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.<br />
<br />
# The project follows a defined release process:<br />
#* The release process is described in the OTB wiki https://wiki.orfeo-toolbox.org/index.php/How_to_Release<br />
#* Which includes execution of the testing process before releasing a stable release. <br />
# 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><br />
#* See OTB Cdash (nightly builds, unit tests and code coverage submissions): https://dash.orfeo-toolbox.org/<br />
# Release and testing processes provide sufficient detail for an experienced programmer to follow.<br />
<br />
<br />
= OSGeo Committees and Community =<br />
<br />
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.<br />
<br />
== Board ==<br />
<br />
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:<br />
<br />
# A project provide a Project Officer as a contract point:<br />
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]<br />
#* This person is established when the incubation committee recommends the project for graduation<br />
#* 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).<br />
<br />
== Marketing ==<br />
<br />
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:<br />
<br />
# 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:<br />
#* Application Overview<br />
#* Application Quick Start<br />
#* Logo<br />
#* Graphical Image<br />
# 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><br />
<br />
== Projects ==<br />
<br />
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. <br />
<br />
<i>As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.</i><br />
<br />
== SAC ==<br />
<br />
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:<br />
* A http://projectname.osgeo.org domain name.<br />
<br />
A project may optionally request SAC help to make use of:<br />
* OSGeo issue tracker<br />
* OSGeo mailing list<br />
* OSGeo svn<br />
* http://downloads.osgeo.org<br />
<br />
[[Category: Incubation]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Project_Incubation_Status&diff=106079OTB Project Incubation Status2017-04-07T14:08:33Z<p>Wiki-Grizonnetm: /* Community Functioning */</p>
<hr />
<div>==General==<br />
<br />
#'''Has the project been approved for incubation by the OSGeo board?''' <br />
Yes. Announcement was made publicly on December 17, 2013.<br />
#'''Has an Incubation Mentor been assigned to the project?''' <br />
Yes. Landon Blake.<br />
<br />
<br />
==Infrastructure Transition==<br />
<br />
#'''Has the projectname.osgeo.org domain been populated with the projects web presence? If not why, and has the project page got a prominent link to the real home?''' <br />
No. An existing web page exists: http://orfeo-toolbox.org/otb/<br />
#'''Is the OSGeo bug tracker being used for the project? If not, why? Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project? If not, why?''' <br />
No. An existing bug tracker is being used by the project: http://bugs.orfeo-toolbox.org<br />
#'''Is the OSGeo SVN being used for the project? If not, why?''' <br />
No. An existing version control system is being used for the project: http://hg.orfeo-toolbox.org/OTB<br />
#'''Are binary and source downloads available from http://download.osgeo.org ? If not, why?'''<br />
No. Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html<br />
<br />
==Community Functioning==<br />
<br />
#'''Is there a functioning user support mechanisms (ie. mailing list)?''' <br />
The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#'''Are source and binary downloads for the package available?''' <br />
Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html <br />
#'''Has a Project Steering Committee been formed, and given control of the project?''' <br />
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)<br />
<br />
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.<br />
<br />
#'''Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines?''' <br />
<br />
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.<br />
<br />
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].<br />
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].<br />
<br />
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: ". <br />
<br />
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].<br />
<br />
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. <br />
<br />
The [https://www.orfeo-toolbox.org/community/ OTB website] gives also more information on how to contribute to the project.<br />
<br />
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.<br />
<br />
#'''How many active developers are there? Are they from multiple organizations? Indicate number and some organizations involved.'''<br />
The ohloh page of the Orfeo ToolBox provides a comprehensive view of contributors activity:<br />
<br />
http://www.ohloh.net/p/otb/contributors?sort=latest_commit<br />
<br />
There were around 15 committers over the last year.<br />
<br />
The "Contributors" chapter of the Software Guide gives a complete listing of all contributors and their affiliations from the beginning of the project :<br />
<br />
http://orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech35.html#x64-52100035<br />
<br />
Very active users and occasional contributors include:<br />
<br />
*Jordi Inglada from CESBIO/CNES is the creator of OTB and as such wrote a lot of OTB code in the past. He still actively uses and promotes it, with a lot of client codes, testing, bug reports, phd and intern works ...<br />
*Gregoire Mercier from Télécom Bretagne wrote the entire wavelet transform code as well as other codes, and currently has a phd working with OTB,<br />
*Angelos Tzotzos from National Technical University of Athens is actively packaging OTB for OpenSuse. He also contributed code for a pan-sharpening algorithm and integrated some OTB in the Gnorasi project,<br />
*Agustin Lobo, who I believe is with CSIC, is a very active user that benchmarked some of OTB functions and makes insightful comments on improving documentation for instance,<br />
*Julien Radoux (UCL) has contributed some algorithms by the past and is still very active on the users list,<br />
*Emmanuel Christophe, currently with Google, who wrote a great deal of OTB code by the past, under CNES and Crisp affiliations.<br />
<br />
==Foundation Membership==<br />
#'''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.''' <br />
The project documentation has been modified to reflect membership in OSGeo.<br />
<br />
#'''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.'''<br />
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.<br />
<br />
==Code Copyright Review==<br />
#'''Has a Code Provenance Review document been prepared for the project?''' <br />
[[OTB Code Provenance Review]]<br />
#'''Have issues raised in the provenance review been adequately addressed? Indicate outstanding issues.''' <br />
<br />
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.<br />
<br />
OTB is moreover integrated in Debian as an official package. OTB is also package for other distribution (fedora, opensuse, Arch...).<br />
<br />
#'''Are Committer Responsibilities Guidelines covering legal issues in place?'''<br />
<br />
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.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Project_Incubation_Status&diff=106078OTB Project Incubation Status2017-04-07T14:04:41Z<p>Wiki-Grizonnetm: /* Community Functioning */</p>
<hr />
<div>==General==<br />
<br />
#'''Has the project been approved for incubation by the OSGeo board?''' <br />
Yes. Announcement was made publicly on December 17, 2013.<br />
#'''Has an Incubation Mentor been assigned to the project?''' <br />
Yes. Landon Blake.<br />
<br />
<br />
==Infrastructure Transition==<br />
<br />
#'''Has the projectname.osgeo.org domain been populated with the projects web presence? If not why, and has the project page got a prominent link to the real home?''' <br />
No. An existing web page exists: http://orfeo-toolbox.org/otb/<br />
#'''Is the OSGeo bug tracker being used for the project? If not, why? Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project? If not, why?''' <br />
No. An existing bug tracker is being used by the project: http://bugs.orfeo-toolbox.org<br />
#'''Is the OSGeo SVN being used for the project? If not, why?''' <br />
No. An existing version control system is being used for the project: http://hg.orfeo-toolbox.org/OTB<br />
#'''Are binary and source downloads available from http://download.osgeo.org ? If not, why?'''<br />
No. Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html<br />
<br />
==Community Functioning==<br />
<br />
#'''Is there a functioning user support mechanisms (ie. mailing list)?''' <br />
The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#'''Are source and binary downloads for the package available?''' <br />
Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html <br />
#'''Has a Project Steering Committee been formed, and given control of the project?''' <br />
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)<br />
<br />
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.<br />
<br />
#'''Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines?''' <br />
<br />
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.<br />
<br />
The documentation about how the governance works is publicly available on the [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee OTB wiki].<br />
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].<br />
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: ". <br />
<br />
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].<br />
<br />
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. <br />
<br />
The [https://www.orfeo-toolbox.org/community/ OTB website] gives also more information on how to contribute to the project.<br />
<br />
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.<br />
<br />
#'''How many active developers are there? Are they from multiple organizations? Indicate number and some organizations involved.'''<br />
The ohloh page of the Orfeo ToolBox provides a comprehensive view of contributors activity:<br />
<br />
http://www.ohloh.net/p/otb/contributors?sort=latest_commit<br />
<br />
There were around 15 committers over the last year.<br />
<br />
The "Contributors" chapter of the Software Guide gives a complete listing of all contributors and their affiliations from the beginning of the project :<br />
<br />
http://orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech35.html#x64-52100035<br />
<br />
Very active users and occasional contributors include:<br />
<br />
*Jordi Inglada from CESBIO/CNES is the creator of OTB and as such wrote a lot of OTB code in the past. He still actively uses and promotes it, with a lot of client codes, testing, bug reports, phd and intern works ...<br />
*Gregoire Mercier from Télécom Bretagne wrote the entire wavelet transform code as well as other codes, and currently has a phd working with OTB,<br />
*Angelos Tzotzos from National Technical University of Athens is actively packaging OTB for OpenSuse. He also contributed code for a pan-sharpening algorithm and integrated some OTB in the Gnorasi project,<br />
*Agustin Lobo, who I believe is with CSIC, is a very active user that benchmarked some of OTB functions and makes insightful comments on improving documentation for instance,<br />
*Julien Radoux (UCL) has contributed some algorithms by the past and is still very active on the users list,<br />
*Emmanuel Christophe, currently with Google, who wrote a great deal of OTB code by the past, under CNES and Crisp affiliations.<br />
<br />
==Foundation Membership==<br />
#'''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.''' <br />
The project documentation has been modified to reflect membership in OSGeo.<br />
<br />
#'''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.'''<br />
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.<br />
<br />
==Code Copyright Review==<br />
#'''Has a Code Provenance Review document been prepared for the project?''' <br />
[[OTB Code Provenance Review]]<br />
#'''Have issues raised in the provenance review been adequately addressed? Indicate outstanding issues.''' <br />
<br />
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.<br />
<br />
OTB is moreover integrated in Debian as an official package. OTB is also package for other distribution (fedora, opensuse, Arch...).<br />
<br />
#'''Are Committer Responsibilities Guidelines covering legal issues in place?'''<br />
<br />
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.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Project_Incubation_Status&diff=106077OTB Project Incubation Status2017-04-07T14:02:38Z<p>Wiki-Grizonnetm: /* Community Functioning */</p>
<hr />
<div>==General==<br />
<br />
#'''Has the project been approved for incubation by the OSGeo board?''' <br />
Yes. Announcement was made publicly on December 17, 2013.<br />
#'''Has an Incubation Mentor been assigned to the project?''' <br />
Yes. Landon Blake.<br />
<br />
<br />
==Infrastructure Transition==<br />
<br />
#'''Has the projectname.osgeo.org domain been populated with the projects web presence? If not why, and has the project page got a prominent link to the real home?''' <br />
No. An existing web page exists: http://orfeo-toolbox.org/otb/<br />
#'''Is the OSGeo bug tracker being used for the project? If not, why? Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project? If not, why?''' <br />
No. An existing bug tracker is being used by the project: http://bugs.orfeo-toolbox.org<br />
#'''Is the OSGeo SVN being used for the project? If not, why?''' <br />
No. An existing version control system is being used for the project: http://hg.orfeo-toolbox.org/OTB<br />
#'''Are binary and source downloads available from http://download.osgeo.org ? If not, why?'''<br />
No. Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html<br />
<br />
==Community Functioning==<br />
<br />
#'''Is there a functioning user support mechanisms (ie. mailing list)?''' <br />
The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#'''Are source and binary downloads for the package available?''' <br />
Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html <br />
#'''Has a Project Steering Committee been formed, and given control of the project?''' <br />
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)<br />
<br />
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.<br />
<br />
#'''Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines?''' <br />
<br />
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.<br />
<br />
The documentation about how the governance works is publicly available on the [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee OTB wiki].<br />
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].<br />
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: ". <br />
<br />
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. <br />
<br />
The [https://www.orfeo-toolbox.org/community/ OTB website] gives also more information on how to contribute to the project.<br />
<br />
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.<br />
<br />
#'''How many active developers are there? Are they from multiple organizations? Indicate number and some organizations involved.'''<br />
The ohloh page of the Orfeo ToolBox provides a comprehensive view of contributors activity:<br />
<br />
http://www.ohloh.net/p/otb/contributors?sort=latest_commit<br />
<br />
There were around 15 committers over the last year.<br />
<br />
The "Contributors" chapter of the Software Guide gives a complete listing of all contributors and their affiliations from the beginning of the project :<br />
<br />
http://orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech35.html#x64-52100035<br />
<br />
Very active users and occasional contributors include:<br />
<br />
*Jordi Inglada from CESBIO/CNES is the creator of OTB and as such wrote a lot of OTB code in the past. He still actively uses and promotes it, with a lot of client codes, testing, bug reports, phd and intern works ...<br />
*Gregoire Mercier from Télécom Bretagne wrote the entire wavelet transform code as well as other codes, and currently has a phd working with OTB,<br />
*Angelos Tzotzos from National Technical University of Athens is actively packaging OTB for OpenSuse. He also contributed code for a pan-sharpening algorithm and integrated some OTB in the Gnorasi project,<br />
*Agustin Lobo, who I believe is with CSIC, is a very active user that benchmarked some of OTB functions and makes insightful comments on improving documentation for instance,<br />
*Julien Radoux (UCL) has contributed some algorithms by the past and is still very active on the users list,<br />
*Emmanuel Christophe, currently with Google, who wrote a great deal of OTB code by the past, under CNES and Crisp affiliations.<br />
<br />
==Foundation Membership==<br />
#'''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.''' <br />
The project documentation has been modified to reflect membership in OSGeo.<br />
<br />
#'''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.'''<br />
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.<br />
<br />
==Code Copyright Review==<br />
#'''Has a Code Provenance Review document been prepared for the project?''' <br />
[[OTB Code Provenance Review]]<br />
#'''Have issues raised in the provenance review been adequately addressed? Indicate outstanding issues.''' <br />
<br />
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.<br />
<br />
OTB is moreover integrated in Debian as an official package. OTB is also package for other distribution (fedora, opensuse, Arch...).<br />
<br />
#'''Are Committer Responsibilities Guidelines covering legal issues in place?'''<br />
<br />
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.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Project_Incubation_Status&diff=106076OTB Project Incubation Status2017-04-07T14:02:12Z<p>Wiki-Grizonnetm: /* Community Functioning */</p>
<hr />
<div>==General==<br />
<br />
#'''Has the project been approved for incubation by the OSGeo board?''' <br />
Yes. Announcement was made publicly on December 17, 2013.<br />
#'''Has an Incubation Mentor been assigned to the project?''' <br />
Yes. Landon Blake.<br />
<br />
<br />
==Infrastructure Transition==<br />
<br />
#'''Has the projectname.osgeo.org domain been populated with the projects web presence? If not why, and has the project page got a prominent link to the real home?''' <br />
No. An existing web page exists: http://orfeo-toolbox.org/otb/<br />
#'''Is the OSGeo bug tracker being used for the project? If not, why? Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project? If not, why?''' <br />
No. An existing bug tracker is being used by the project: http://bugs.orfeo-toolbox.org<br />
#'''Is the OSGeo SVN being used for the project? If not, why?''' <br />
No. An existing version control system is being used for the project: http://hg.orfeo-toolbox.org/OTB<br />
#'''Are binary and source downloads available from http://download.osgeo.org ? If not, why?'''<br />
No. Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html<br />
<br />
==Community Functioning==<br />
<br />
#'''Is there a functioning user support mechanisms (ie. mailing list)?''' <br />
The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#'''Are source and binary downloads for the package available?''' <br />
Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html <br />
#'''Has a Project Steering Committee been formed, and given control of the project?''' <br />
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)<br />
<br />
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.<br />
<br />
#'''Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines?''' <br />
<br />
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.<br />
The documentation about how the governance works is publicly available on the [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee OTB wiki].<br />
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].<br />
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: ". <br />
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. <br />
The [https://www.orfeo-toolbox.org/community/ OTB website] gives also more information on how to contribute to the project.<br />
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.<br />
<br />
#'''How many active developers are there? Are they from multiple organizations? Indicate number and some organizations involved.'''<br />
The ohloh page of the Orfeo ToolBox provides a comprehensive view of contributors activity:<br />
<br />
http://www.ohloh.net/p/otb/contributors?sort=latest_commit<br />
<br />
There were around 15 committers over the last year.<br />
<br />
The "Contributors" chapter of the Software Guide gives a complete listing of all contributors and their affiliations from the beginning of the project :<br />
<br />
http://orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech35.html#x64-52100035<br />
<br />
Very active users and occasional contributors include:<br />
<br />
*Jordi Inglada from CESBIO/CNES is the creator of OTB and as such wrote a lot of OTB code in the past. He still actively uses and promotes it, with a lot of client codes, testing, bug reports, phd and intern works ...<br />
*Gregoire Mercier from Télécom Bretagne wrote the entire wavelet transform code as well as other codes, and currently has a phd working with OTB,<br />
*Angelos Tzotzos from National Technical University of Athens is actively packaging OTB for OpenSuse. He also contributed code for a pan-sharpening algorithm and integrated some OTB in the Gnorasi project,<br />
*Agustin Lobo, who I believe is with CSIC, is a very active user that benchmarked some of OTB functions and makes insightful comments on improving documentation for instance,<br />
*Julien Radoux (UCL) has contributed some algorithms by the past and is still very active on the users list,<br />
*Emmanuel Christophe, currently with Google, who wrote a great deal of OTB code by the past, under CNES and Crisp affiliations.<br />
<br />
==Foundation Membership==<br />
#'''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.''' <br />
The project documentation has been modified to reflect membership in OSGeo.<br />
<br />
#'''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.'''<br />
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.<br />
<br />
==Code Copyright Review==<br />
#'''Has a Code Provenance Review document been prepared for the project?''' <br />
[[OTB Code Provenance Review]]<br />
#'''Have issues raised in the provenance review been adequately addressed? Indicate outstanding issues.''' <br />
<br />
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.<br />
<br />
OTB is moreover integrated in Debian as an official package. OTB is also package for other distribution (fedora, opensuse, Arch...).<br />
<br />
#'''Are Committer Responsibilities Guidelines covering legal issues in place?'''<br />
<br />
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.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Project_Incubation_Status&diff=106075OTB Project Incubation Status2017-04-07T14:00:38Z<p>Wiki-Grizonnetm: /* Community Functioning */</p>
<hr />
<div>==General==<br />
<br />
#'''Has the project been approved for incubation by the OSGeo board?''' <br />
Yes. Announcement was made publicly on December 17, 2013.<br />
#'''Has an Incubation Mentor been assigned to the project?''' <br />
Yes. Landon Blake.<br />
<br />
<br />
==Infrastructure Transition==<br />
<br />
#'''Has the projectname.osgeo.org domain been populated with the projects web presence? If not why, and has the project page got a prominent link to the real home?''' <br />
No. An existing web page exists: http://orfeo-toolbox.org/otb/<br />
#'''Is the OSGeo bug tracker being used for the project? If not, why? Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project? If not, why?''' <br />
No. An existing bug tracker is being used by the project: http://bugs.orfeo-toolbox.org<br />
#'''Is the OSGeo SVN being used for the project? If not, why?''' <br />
No. An existing version control system is being used for the project: http://hg.orfeo-toolbox.org/OTB<br />
#'''Are binary and source downloads available from http://download.osgeo.org ? If not, why?'''<br />
No. Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html<br />
<br />
==Community Functioning==<br />
<br />
#'''Is there a functioning user support mechanisms (ie. mailing list)?''' <br />
The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#'''Are source and binary downloads for the package available?''' <br />
Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html <br />
#'''Has a Project Steering Committee been formed, and given control of the project?''' <br />
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)<br />
<br />
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.<br />
<br />
#'''Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines?''' <br />
<br />
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<br />
software projects like GRASS GIS, GDAL or QGIS.<br />
<br />
The documentation about how the governance works is publicly available on the [https://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee OTB wiki].<br />
<br />
All the decisions regarding OTB are public and follow a procedure through RFC (Request for Changes). It is also describes in the OTB wiki.<br />
<br />
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: ". <br />
<br />
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. <br />
<br />
The [https://www.orfeo-toolbox.org/community/ OTB website] gives also more information on how to contribute to the project.<br />
<br />
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.<br />
<br />
#'''How many active developers are there? Are they from multiple organizations? Indicate number and some organizations involved.'''<br />
The ohloh page of the Orfeo ToolBox provides a comprehensive view of contributors activity:<br />
<br />
http://www.ohloh.net/p/otb/contributors?sort=latest_commit<br />
<br />
There were around 15 committers over the last year.<br />
<br />
The "Contributors" chapter of the Software Guide gives a complete listing of all contributors and their affiliations from the beginning of the project :<br />
<br />
http://orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech35.html#x64-52100035<br />
<br />
Very active users and occasional contributors include:<br />
<br />
*Jordi Inglada from CESBIO/CNES is the creator of OTB and as such wrote a lot of OTB code in the past. He still actively uses and promotes it, with a lot of client codes, testing, bug reports, phd and intern works ...<br />
*Gregoire Mercier from Télécom Bretagne wrote the entire wavelet transform code as well as other codes, and currently has a phd working with OTB,<br />
*Angelos Tzotzos from National Technical University of Athens is actively packaging OTB for OpenSuse. He also contributed code for a pan-sharpening algorithm and integrated some OTB in the Gnorasi project,<br />
*Agustin Lobo, who I believe is with CSIC, is a very active user that benchmarked some of OTB functions and makes insightful comments on improving documentation for instance,<br />
*Julien Radoux (UCL) has contributed some algorithms by the past and is still very active on the users list,<br />
*Emmanuel Christophe, currently with Google, who wrote a great deal of OTB code by the past, under CNES and Crisp affiliations.<br />
<br />
==Foundation Membership==<br />
#'''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.''' <br />
The project documentation has been modified to reflect membership in OSGeo.<br />
<br />
#'''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.'''<br />
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.<br />
<br />
==Code Copyright Review==<br />
#'''Has a Code Provenance Review document been prepared for the project?''' <br />
[[OTB Code Provenance Review]]<br />
#'''Have issues raised in the provenance review been adequately addressed? Indicate outstanding issues.''' <br />
<br />
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.<br />
<br />
OTB is moreover integrated in Debian as an official package. OTB is also package for other distribution (fedora, opensuse, Arch...).<br />
<br />
#'''Are Committer Responsibilities Guidelines covering legal issues in place?'''<br />
<br />
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.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=InfrastructurePreferencesStatusQuo&diff=105896InfrastructurePreferencesStatusQuo2017-03-27T08:06:35Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>Brief report on the current infrastructure preferences amont the OSGeo projects.<br />
<br />
== Objectives ==<br />
<br />
Attempt to answer the following:<br />
<br />
* What are the projects current preferences of development infrastructure?<br />
* How OSGeo projects utilise OSGeo infrastructure?<br />
* What is the potential of needs and demands not satisfied by OSGeo infrastructure?<br />
<br />
== Status Quo ==<br />
<br />
Date of data collection: 19 March 2017<br />
<br />
=== OSGeo Projects ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! # !! Project !! OSGeo SVN !! OSGeo Trac !! OSGeo Git (GOGS) !! GitHub !! Mailing Lists !! Wiki !! <project>.osgeo.org !! Notes<br />
|-<br />
| 1 || '''degree''' || No || No || No || Yes,Org || SF.net || external || No || <br />
|-<br />
| 2 || '''FDO''' || <span style="background:green">Yes</span> || <span style="background:green">Issues,Wiki</span> || No || || <span style="background:green">OSGeo</span> || <span style="background:green">OSGeo</span> || website ||<br />
|-<br />
| 3 || '''GDAL/OGR''' || <span style="background:green">Yes</span> || <span style="background:green">Issues,Wiki</span> || No || Mirror,PR,CI || <span style="background:green">OSGeo</span> || <span style="background:green">OSGeo</span> || No ||<br />
|-<br />
| 4 || '''geomajas''' || No || No || No || Yes,Org || external || || redirect || External bug tracker (JIRA)<br />
|-<br />
| 5 || '''GeoMOOSE''' || Yes,archive || No || No || Yes,Org || <span style="background:green">OSGeo</span> || GitHub || redirect ||<br />
|-<br />
| 6 || '''GeoNetwork''' || <span style="background:green">Yes</span> || Yes,signpost,inactive || No || Yes,Org || SF.net || GitHub || ||<br />
|-<br />
| 7 || '''GeoNode''' || No || No || No || Yes,Org || <span style="background:green">OSGeo</span> || GitHub || redirect ||<br />
|-<br />
| 8 || '''GEOS''' || <span style="background:green">Yes</span> || <span style="background:green">Yes</span> || Yes (mirror and PHP bindings), PR || Mirror,Org,PR,CI || <span style="background:green">OSGeo</span> || <span style="background:green">OSGeo</span> || redirect ||<br />
|-<br />
| 9 || '''GeoServer''' || No || No || No || Yes,Org || SF.net || GitHub || redirect || Gitter<br />
|-<br />
| 10 || '''GeoTools''' || Yes,inactive || JIRA at OSGeo || No || Yes,Org ||SF.net || GitHub || redirect ||<br />
|-<br />
| 11 || '''GRASS GIS''' || <span style="background:green">Yes</span> || <span style="background:green">Yes</span> || No || Mirror,Org,CI || <span style="background:green">OSGeo</span> || <span style="background:green">OSGeo</span> || website || [https://svn.osgeo.org/grass/grass/trunk/doc/infrastructure.txt detailed GRASS GIS infrastructure description]<br />
|-<br />
| 12 || '''gvSIG''' || No || No || No || Yes,Org || external || external || redirect || External bug tracker (Redmine)<br />
|-<br />
| 13 || '''Mapbender''' || <span style="background:green">Yes</span> || No,inactive(?) || No || Yes,Org || <span style="background:green">OSGeo</span> || || redirect ||<br />
|-<br />
| 14 || '''MapFish''' || No || No || No || Yes,some use || external || external || redirect ||<br />
|-<br />
| 15 || '''MapGuide Open Source''' || <span style="background:green">Yes</span> || <span style="background:green">Yes</span> || || <span style="background:green">OSGeo</span> || <span style="background:green">OSGeo</span> || website ||<br />
|-<br />
| 16 || '''MapServer''' || inactive || inactive || No || Yes,Org || <span style="background:green">OSGeo</span> || GitHub || redirect ||<br />
|-<br />
| 17 || '''Marble''' || No || No || No || Mirror || kde.org || kde.org || redirect ||<br />
|-<br />
| 18 || '''OpenLayers''' || inactive || No || No || Yes,Org || inactive || GitHub || redirect ||<br />
|-<br />
| 19 || '''OSSIM''' || inactive || inactive || No || Yes,Org || SF.net || GitHub || redirect ||<br />
|-<br />
| 20 || '''PostGIS''' || <span style="background:green">Yes</span> || <span style="background:green">Yes: Issues, Wiki</span> || Yes (website and main mirror), PR, CI || Mirror,Org,PR,CI || <span style="background:green">OSGeo</span> || <span style="background:green">OSGeo</span> || redirect ||<br />
|-<br />
| 21 || '''pycsw''' || No || No || No || Yes,Org,PR,CI || <span style="background:green">OSGeo</span>|| GitHub || redirect || Full project infrastructure details at https://github.com/geopython/pycsw/wiki/Technical-Infrastructure<br />
|-<br />
| 22 || '''QGIS''' || inactive || inactive || No || Yes,Org,PR,CI || <span style="background:green">OSGeo</span>|| GitHub,hub.qgis.org || redirect ||<br />
|-<br />
! # !! Project !! OSGeo SVN !! OSGeo Trac !! OSGeo Git || GitHub !! Mailing Lists !! Wiki !! <project>.osgeo.org !! Notes<br />
|-<br />
|}<br />
<br />
=== OSGeo Outreach Projects ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! # !! Project !! OSGeo SVN !! OSGeo Trac !! OSGeo Git (GOGS) !! GitHub !! Mailing Lists !! Wiki !! <project>.osgeo.org !! Notes<br />
|-<br />
| 1 || '''OSGeo-Live''' || No || <span style="background:green">OSGeo</span> || No || Yes || <span style="background:green">OSGeo</span> || <span style="background:green">OSGeo</span>, http://wiki.osgeo.org/wiki/Live_GIS_Disc || <span style="background:green">OSGeo</span> http://live.osgeo.org ||<br />
|-<br />
! # !! Project !! OSGeo SVN !! OSGeo Trac !! OSGeo Git || GitHub !! Mailing Lists !! Wiki !! <project>.osgeo.org !! Notes<br />
|-<br />
|}<br />
<br />
=== OSGeo Community Projects ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! # !! Project !! OSGeo SVN !! OSGeo Trac !! OSGeo Git (GOGS) !! GitHub !! Mailing Lists !! Wiki !! <project>.osgeo.org !! Notes<br />
|-<br />
| 1 || '''pgRouting''' || No || No || No || Yes,Org,PR,CI || <span style="background:green">OSGeo</span> || https://github.com/pgRouting/pgrouting/wiki || website http://pgrouting.org/ || Community project<br />
|-<br />
! # !! Project !! OSGeo SVN !! OSGeo Trac !! OSGeo Git || GitHub !! Mailing Lists !! Wiki !! <project>.osgeo.org !! Notes<br />
|-<br />
|}<br />
<br />
=== OSGeo Incubating Projects ===<br />
<br />
{| class="wikitable"<br />
|-<br />
! # !! Project !! OSGeo SVN !! OSGeo Trac !! OSGeo Git (GOGS) !! GitHub !! Mailing Lists !! Wiki !! <project>.osgeo.org !! Notes<br />
|-<br />
| 1 || '''ORFEO ToolBox''' || No || No || No || Yes (mirror) - git repo: https://git.orfeo-toolbox.org/ || Google groups (https://groups.google.com/forum/#!forum/otb-users) || external (https://wiki.orfeo-toolbox.org) || No || external bug tracker (Mantis), would like to move to osgeo mailing list<br />
|-<br />
! # !! Project !! OSGeo SVN !! OSGeo Trac !! OSGeo Git || GitHub !! Mailing Lists !! Wiki !! <project>.osgeo.org !! Notes<br />
|-<br />
|}<br />
<br />
[[Category:Infrastructure]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Project_Incubation_Status&diff=105649OTB Project Incubation Status2017-03-15T09:19:17Z<p>Wiki-Grizonnetm: /* Code Copyright Review */</p>
<hr />
<div>==General==<br />
<br />
#'''Has the project been approved for incubation by the OSGeo board?''' <br />
Yes. Announcement was made publicly on December 17, 2013.<br />
#'''Has an Incubation Mentor been assigned to the project?''' <br />
Yes. Landon Blake.<br />
<br />
<br />
==Infrastructure Transition==<br />
<br />
#'''Has the projectname.osgeo.org domain been populated with the projects web presence? If not why, and has the project page got a prominent link to the real home?''' <br />
No. An existing web page exists: http://orfeo-toolbox.org/otb/<br />
#'''Is the OSGeo bug tracker being used for the project? If not, why? Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project? If not, why?''' <br />
No. An existing bug tracker is being used by the project: http://bugs.orfeo-toolbox.org<br />
#'''Is the OSGeo SVN being used for the project? If not, why?''' <br />
No. An existing version control system is being used for the project: http://hg.orfeo-toolbox.org/OTB<br />
#'''Are binary and source downloads available from http://download.osgeo.org ? If not, why?'''<br />
No. Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html<br />
<br />
==Community Functioning==<br />
<br />
#'''Is there a functioning user support mechanisms (ie. mailing list)?''' <br />
The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#'''Are source and binary downloads for the package available?''' <br />
Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html <br />
#'''Has a Project Steering Committee been formed, and given control of the project?''' <br />
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)<br />
<br />
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.<br />
<br />
#'''Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines?''' <br />
#'''How many active developers are there? Are they from multiple organizations? Indicate number and some organizations involved.'''<br />
The ohloh page of the Orfeo ToolBox provides a comprehensive view of contributors activity:<br />
<br />
http://www.ohloh.net/p/otb/contributors?sort=latest_commit<br />
<br />
There were around 15 committers over the last year.<br />
<br />
The "Contributors" chapter of the Software Guide gives a complete listing of all contributors and their affiliations from the beginning of the project :<br />
<br />
http://orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech35.html#x64-52100035<br />
<br />
Very active users and occasional contributors include:<br />
<br />
*Jordi Inglada from CESBIO/CNES is the creator of OTB and as such wrote a lot of OTB code in the past. He still actively uses and promotes it, with a lot of client codes, testing, bug reports, phd and intern works ...<br />
*Gregoire Mercier from Télécom Bretagne wrote the entire wavelet transform code as well as other codes, and currently has a phd working with OTB,<br />
*Angelos Tzotzos from National Technical University of Athens is actively packaging OTB for OpenSuse. He also contributed code for a pan-sharpening algorithm and integrated some OTB in the Gnorasi project,<br />
*Agustin Lobo, who I believe is with CSIC, is a very active user that benchmarked some of OTB functions and makes insightful comments on improving documentation for instance,<br />
*Julien Radoux (UCL) has contributed some algorithms by the past and is still very active on the users list,<br />
*Emmanuel Christophe, currently with Google, who wrote a great deal of OTB code by the past, under CNES and Crisp affiliations.<br />
<br />
==Foundation Membership==<br />
#'''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.''' <br />
The project documentation has been modified to reflect membership in OSGeo.<br />
<br />
#'''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.'''<br />
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.<br />
<br />
==Code Copyright Review==<br />
#'''Has a Code Provenance Review document been prepared for the project?''' <br />
[[OTB Code Provenance Review]]<br />
#'''Have issues raised in the provenance review been adequately addressed? Indicate outstanding issues.''' <br />
<br />
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.<br />
<br />
OTB is moreover integrated in Debian as an official package. OTB is also package for other distribution (fedora, opensuse, Arch...).<br />
<br />
#'''Are Committer Responsibilities Guidelines covering legal issues in place?'''<br />
<br />
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.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Code_Provenance_Review&diff=105648OTB Code Provenance Review2017-03-15T09:17:27Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>= Committers =<br />
<br />
List of all OTB committers since 2006:<br />
<br />
* Amit Kulkarni<br />
* Angelos Tzotsos<br />
* Arnaud Jaen<br />
* Aurelien Bricier<br />
* Caroline Ruffel<br />
* Charles Peyrega<br />
* Chia Aik Song<br />
* Christophe Palmann<br />
* Conrad Bielski<br />
* Cyrille Valladeau<br />
* Daphne Deleflie<br />
* Emmanuel Christophe<br />
* Etienne Bougoin<br />
* Gregoire Mercier<br />
* Guillaume Borrut<br />
* Guillaume Pasero<br />
* Jonathan Guinet<br />
* Jordi Inglada<br />
* Julien Malik<br />
* Julien Michel<br />
* Luc Hermitte<br />
* Manuel Grizonnet<br />
* Mathieu Deltorre<br />
* Mickael Savinaud<br />
* Otmane Lahlou<br />
* Patrick Imbo<br />
* Rashad Kanavath<br />
* Romain Garrigues<br />
* Rosa Ruiloba<br />
* Sebastien Dinot<br />
* Sebastien Harasse<br />
* Stephane Albert<br />
* Thomas Feuvrier<br />
* Tishampati Dhar<br />
* Vincent Poulain<br />
* Yin Tiangang<br />
<br />
Actual committers to OTB:<br />
<br />
* sdinot (Sébastien Dinot)<br />
* jmalik (Julien Malik)<br />
* msavinaud (Mickaël Savinaud)<br />
* mgrizonnet (Manuel Grizonnet)<br />
* jmichel (Julien Michel)<br />
* gpasero (Guillaume Pasero)<br />
* abricier (Aurélien Bricier)<br />
* jinglada (Jordi Inglada)<br />
* rkanavath (Rashad Kanavath)<br />
* cpalmann (Christophe Palmann)<br />
* salbert (Stéphane Albert)<br />
* lhermitte (Luc Hermitte)<br />
* poughov (Victor Poughon)<br />
<br />
An updated list of all contributors to the library is also available in the [https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech36.html#x69-48700036 OTB Software Guide] (Chapter 36 - Contributors).<br />
<br />
= Outstanding Issues =<br />
There is no outstanding issue regarding OTB code provenance. OTB integrates in one module a dependency to the 6S library (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) In the meantime OTB module which use 6S has been deactivated from the Debian package. <br />
<br />
= Included Libraries =<br />
<br />
List of third party libraries source code integrated in OTB source tree: <br />
* 6S<br />
* SiftFast<br />
* Boost (type_traits)<br />
* OssimPLugins<br />
<br />
Other OTB dependencies are not included in the source tree.<br />
<br />
== Free Libraries ==<br />
<br />
* 6S<br />
* SiftFast<br />
* Boost type_traits<br />
* OssimPLugins<br />
<br />
== Non-Free Libraries ==<br />
OTB does not include any non-free libraries.<br />
<br />
== Code Review ==<br />
Moreover CNES commissioned [https://www.blackducksoftware.com/ Black Duck] to perform a code review of the library in 2011 which does not highlight issue with <br />
<br />
An extensive code review was done in the frame of the license migration for OTB in 2016/2017(from CeCILL v2 to Apache v2).<br />
<br />
Since March 2017, OTB sources are released under Apache v2 (starting with release 6.0). This modification was conduct by the OTB development team and adopted in the following [https://wiki.orfeo-toolbox.org/index.php/Request_for_Changes-84:_Change_license_to_Apache_v2.0 RFC] which detail the procedure.<br />
<br />
As describe in the RFC, OTB follows Apache foundation guidelines regarding copyright management, headers definition.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Incubation_Application&diff=105647OTB Incubation Application2017-03-15T09:10:32Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>==About OTB==<br />
The project is the Orfeo Toolbox (OTB) available at http://www.orfeo-toolbox.org. This is a project started by CNES (the French Space Agency) in 2006 to provide open source tools to process satellite images and extract information. There are several links with other OSGeo project such as Gdal and ossim, QGIS. The project is currently released under the CeCILL license (compatible with GPL).<br />
<br />
==Answers to the Incubator Application Questionnaire== <br />
<br />
1. Please provide the name and email address of the principal Project Owner. <br />
<br />
Manuel Grizonnet (manuel.grizonnet@…)<br />
<br />
2. Please provide the names and emails of co-project owners (if any). <br />
<br />
You can find the list of current members of [http://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee#PSC_members%20here OTB Project Steering committee].<br />
<br />
3. Please provide the names, emails and entity affiliation of all official committers.<br />
<br />
http://www.ohloh.net/p/otb/contributors?page=1 from CNES, CS (mostly under a contract with CNES), IRSTEA, Telecom Bretagne, Google, National Technical University of Athens...<br />
<br />
4. Please describe your Project.<br />
Provide open source tools to process satellite images and extract information<br />
<br />
5. Why is hosting at OSGeo good for your project? <br />
<br />
It would be good for our project to be associated with OSGeo (public awareness, quality control and cooperation with other OSGeo projects like QGIS or Grass). It would be also really interesting to get an access to the OSGeo infrastructure (website, mailing list...).<br />
<br />
6. Type of application does this project represent(client, server, standalone, library, etc.).<br />
<br />
Library with some applications with Graphical User Interfaces (OTB-Applications and Monteverdi).<br />
<br />
7. Please describe any relationships to other open source projects. <br />
<br />
Intensive use of ITK, Gdal and ossim. OTB applications are also available through Quantum GIS plugins (through the processing plugin)<br />
<br />
8. Please describe any relationships with commercial companies or products. <br />
<br />
9. Which open source license(s) will the source code be released under? <br />
<br />
CeCILL v2 (GPL compatible) since the beginning and Apache v2 starting with version 6.0 (2017).<br />
<br />
10. Is there already a beta or official release? <br />
<br />
Current release is 5.10.1 (March 2017). <br />
<br />
11. What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)? <br />
<br />
Government (CNES the French Space Agency)<br />
<br />
12. Does the project support open standards? Which ones and to what extent? (OGC, w3c, ect.) Has the software been certified to any standard (CITE for example)? If not, is it the intention of the project owners to seek certification at some point? OTB supports open data standard through GDAL and OGR<br />
<br />
13. Is the code free of patents, trademarks, and do you control the copyright? <br />
<br />
The code is free of patents and trademarks.<br />
<br />
14. How many people actively contribute (code, documentation, other?) to the project at this time? <br />
<br />
10/15 people currently contributing.<br />
<br />
15. How many people have commit access to the source code repository? <br />
<br />
Distributed source control is used (subversion and mercurial in the past and git since 2015). Currently 20 people have a push access to the main repository.<br />
<br />
16. Approximately how many users are currently using this project? <br />
<br />
That's hard to tell...We observed a significantly increase of the number of downloads since 2010. The availability of binary packages (on Linux, Windows, Mac) helps a lot to increase the number of OTB users.<br />
<br />
17. What type of users does your project attract (government, commercial, hobby, academic research, etc. )? <br />
<br />
government, academic research, company...<br />
<br />
18. If you do not intend to host any portion of this project using the OSGeo infrastructure, why should you be considered a member project of the OSGeo Foundation? <br />
<br />
We intend if it is possible to host portion of the project using the OSGeo infrastructure and we are convinced that the incubation of OTB will really increase interactions with other projects of the foundation.<br />
<br />
19. Does the project include an automated build and test? <br />
<br />
CMake and Ctest with a nightly submission of more that 2600 tests on more than 10 different platforms (see [https://dash.orfeo-toolbox.org/ dash.orfeo-toolbox.org]).<br />
<br />
20. What language(s) are used in this project? <br />
<br />
C++ with availability of Python bindings...<br />
<br />
21. What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers? <br />
<br />
The dominant language is English (code, comments, mailing lists and documentation). Some tutorials are also available in French.<br />
<br />
22. What is the (estimated) size of a full release of this project? How many users do you expect to download the project when it is released? <br />
<br />
40 MB for the source, 60 MB for the windows binary release. Between 500 to 1500 downloads per Month for the latest release 5.8 on [https://www.orfeo-toolbox.org/packages/ OTB website], but the files are available from other sources as well.<br />
<br />
[[Category:Incubation]]<br />
[[Category:Committees]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Incubation_Application&diff=105646OTB Incubation Application2017-03-15T09:08:56Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>==About OTB==<br />
The project is the Orfeo Toolbox (OTB) available at http://www.orfeo-toolbox.org. This is a project started by CNES (the French Space Agency) in 2006 to provide open source tools to process satellite images and extract information. There are several links with other OSGeo project such as Gdal and ossim, QGIS. The project is currently released under the CeCILL license (compatible with GPL).<br />
<br />
==Answers to the Incubator Application Questionnaire== <br />
<br />
1. Please provide the name and email address of the principal Project Owner. <br />
<br />
Manuel Grizonnet (manuel.grizonnet@…)<br />
<br />
2. Please provide the names and emails of co-project owners (if any). <br />
<br />
You can find the list of current members of OTB Project Steering committee [http://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee#PSC_members here].<br />
<br />
3. Please provide the names, emails and entity affiliation of all official committers.<br />
<br />
http://www.ohloh.net/p/otb/contributors?page=1 from CNES, CS (mostly under a contract with CNES), IRSTEA, Telecom Bretagne, Google, National Technical University of Athens...<br />
<br />
4. Please describe your Project.<br />
Provide open source tools to process satellite images and extract information<br />
<br />
5. Why is hosting at OSGeo good for your project? <br />
<br />
It would be good for our project to be associated with OSGeo (public awareness, quality control and cooperation with other OSGeo projects like QGIS or Grass). It would be also really interesting to get an access to the OSGeo infrastructure (website, mailing list...).<br />
<br />
6. Type of application does this project represent(client, server, standalone, library, etc.).<br />
<br />
Library with some applications with Graphical User Interfaces (OTB-Applications and Monteverdi).<br />
<br />
7. Please describe any relationships to other open source projects. <br />
<br />
Intensive use of ITK, Gdal and ossim. OTB applications are also available through Quantum GIS plugins (through the processing plugin)<br />
<br />
8. Please describe any relationships with commercial companies or products. <br />
<br />
9. Which open source license(s) will the source code be released under? <br />
<br />
CeCILL v2 (GPL compatible) and Apache v2 starting with version 6.0<br />
<br />
10. Is there already a beta or official release? <br />
<br />
Current release is 5.10.1 (March 2017). <br />
<br />
11. What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)? <br />
<br />
Government (CNES the French Space Agency)<br />
<br />
12. Does the project support open standards? Which ones and to what extent? (OGC, w3c, ect.) Has the software been certified to any standard (CITE for example)? If not, is it the intention of the project owners to seek certification at some point? OTB supports open data standard through GDAL and OGR<br />
<br />
13. Is the code free of patents, trademarks, and do you control the copyright? <br />
<br />
The code is free of patents and trademarks.<br />
<br />
14. How many people actively contribute (code, documentation, other?) to the project at this time? <br />
<br />
10/15 people currently contributing.<br />
<br />
15. How many people have commit access to the source code respository? <br />
<br />
Distributed source control is used (subversion and mercurial in the past and git since 2015). Currently 20 people have a push access to the main repository.<br />
<br />
16. Approximately how many users are currently using this project? <br />
<br />
That's hard to tell...We observed a significantly increase of the number of downloads since 2010. The availability of binary packages (on Linux, Windows, Mac) helps a lot to increase the number of OTB users.<br />
<br />
17. What type of users does your project attract (government, commercial, hobby, academic research, etc. )? <br />
<br />
government, academic research, company...<br />
<br />
18. If you do not intend to host any portion of this project using the OSGeo infrastructure, why should you be considered a member project of the OSGeo Foundation? <br />
<br />
We intend if it is possible to host portion of the project using the OSGeo infrastructure and we are convinced that the incubation of OTB will really increase interactions with other projects of the foundation.<br />
<br />
19. Does the project include an automated build and test? <br />
<br />
cmake and ctest with a nightly submission of more that 2600 tests on more than 10 different platforms (see [https://dash.orfeo-toolbox.org/ dash.orfeo-toolbox.org]).<br />
<br />
20. What language(s) are used in this project? <br />
<br />
C++ with availability of Python bindings...<br />
<br />
21. What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers? <br />
<br />
The dominant language is English (code, comments, mailing lists and documentation). Some tutorials are also available in French.<br />
<br />
22. What is the (estimated) size of a full release of this project? How many users do you expect to download the project when it is released? <br />
<br />
40 MB for the source, 60 MB for the windows binary release. Between 500 to 1500 downloads per Month for the latest release 5.8 on [https://www.orfeo-toolbox.org/packages/ OTB website], but the files are available from other sources as well.<br />
<br />
[[Category:Incubation]]<br />
[[Category:Committees]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2016_OSGeo_Booth&diff=100018FOSS4G 2016 OSGeo Booth2016-06-29T06:29:06Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>Placeholder for organizing the OSGeo Booth at [[FOSS4G 2016]] Bonn, similar to previous years: [[FOSS4G2015_OSGeo_Booth]] Seoul, [[FOSS4G2014 OSGeo Booth]] Portland.<br />
<br />
'''Event Contacts:''' ''TBD''<br />
<br />
== Event contact ==<br />
<br />
<br />
<br />
== Floor Plan ==<br />
<br />
As always on FOSS4G OSGeo has a booth<br />
It's booth no 27 (25 is Boundless Spatial Inc., 28 is LocationTech)<br />
<br />
* ''plan to be added''<br />
see http://2016.foss4g.org/files/foss4g/media/videos/FOSS4G-Exhibition-Plan_v3.jpg<br />
<br />
Wall facing the stairs for screen/banner<br />
Corner: flyer-console<br />
<br />
== Booth Structure ==<br />
<br />
* Depending on actual location of sockets<br />
<br />
== Booth Size ==<br />
<br />
2m x 2m<br />
<br />
== Volunteers ==<br />
<br />
* [[Venkatesh Raghavan]]<br />
* [[Dirk Frigne]]<br />
* [[Angelos Tzotsos]]<br />
* [[Brent Wood]]<br />
* [[User:stevenfeldman | Steven Feldman]]<br />
* [[User:ortelius|Jeffrey Johnson]]<br />
* [[Anita Graser]] (25th)<br />
* [[Marc_Vloemans]]<br />
* [[User:Grizonnetm | Manuel Grizonnet]]<br />
* Add your name<br />
<br />
== Schedule ==<br />
WCCB Bonn<br />
<br />
{|class=wikitable border="1"<br />
! Day !! Hours !! <br />
|-<br />
| Tues August 23 || 15:30-18:00 || possible setup.<br />
|-<br />
| Wed August 24 || 08:30-18:00 || Regular hours, sessions running, happy hour etc.<br />
|-<br />
| Thurs August 25 || 08:30-18:00 || Regular hours, sessions running, happy hour etc.<br />
|-<br />
| Fri August 26|| 08:30-17:30 || Regular hours, sessions running, etc.<br />
|-<br />
| || 17:30-18:00 || '''Move out'''<br />
|}<br />
<br />
conference program: http://2016.foss4g.org/<br />
<br />
== Signup Schedule ==<br />
<br />
{|class=wikitable border="1"<br />
! Day !! Hours !! What !! Booth Team (2-3/slot) !! Special activity <br />
|-<br />
| Thue August 23 || 8:30-12:30 || '''Move in / Set up''' || Marc & ||<br />
|-<br />
| Wed August 24 || 10:30-13:00 || Regular hours (Exhibit Hall opens at 10:30) || ||<br />
|-<br />
| || 13:00-15:00 || Regular hours || || <br />
|-<br />
| || 15:00-17:00 || Regular hours || || <br />
|-<br />
| || 17:00-19:00 || Regular hours || Marc & ? || <br />
|-<br />
| || 17.00-18.30 || Happy Hour || ||<br />
|-<br />
| Thurs August 25 || 10:30-13:00 || Regular hours || Anita & ? ||<br />
|-<br />
| || 13:00-15:00 || Regular hours || || <br />
|-<br />
| || 15:00-17:00 || Regular hours || ||<br />
|-<br />
| || 17:00-18:30 || Regular hours || Marc & ? || <br />
|-<br />
| || 17.00-18.30 || Happy Hour || TBD || <br />
|-<br />
| || 17:30-19:00 || closed -> Annual Meeting || TBD ||<br />
|-<br />
| Fri August 26|| 10:30-13:00 || Regular hours || ||<br />
|-<br />
| || 13:00-15:00 || Regular hours || ||<br />
|-<br />
| || 15:00-16:00 || Regular hours || ||<br />
|-<br />
| || 16:00-18:30 || Take down || Marc & ||<br />
|}<br />
<br />
== Equipment ==<br />
<br />
Possible needs:<br />
<br />
* Poster?<br />
* Flyer console (to be bought)<br />
* laptops/monitors?: there is not much pace<br />
* 1 high table? drape? 2 stools/chairs? banner (1 FOSSGIS, 1 to be made), cloth banner ceiling (FOSSGIS)<br />
* screen? wired internet?<br />
(FOSSGIS e.V. has some equipement from past conferences)<br />
<br />
* stickers to be printed <br />
* OSGEo Flyer(s) to be printed<br />
<br />
<br />
* Banners:<br />
http://svn.osgeo.org/osgeo/marketing/exhibitionpack/<br />
I suggest both: OSGeo_popup and OSGeo_popup2<br />
Ask printer/see on printer-site, whether the PDF of SVG format is needed. Silk finish or silk matt finish for readability (light glare during exhibitions is high)<br />
<br />
* Brochure:<br />
OSGeo_Brochure_2010_PRINT_A4_spread.pdf<br />
(this is single A4 back and front)<br />
I suggest minimum paperweight of 100 gram paper, silk or silk matt finished.<br />
Ask printer to fold, preferably not do so yourself (bothersome and never a crips bend)<br />
Usually I count max 100 brochures per exhibition day on average. Now, 300 will do I expect.<br />
<br />
* Table runner<br />
http://svn.osgeo.org/osgeo/marketing/exhibitionpack/<br />
If printer is able to print on cloth, you could order:<br />
OSGeo_tablerunner<br />
Please check with printer if PDF or SVG file format required<br />
<br />
* CD Live disk (latest version?)<br />
http://svn.osgeo.org/osgeo/marketing/disk/<br />
Per FOSS4GNA this was still 2011 version.....Check!<br />
<br />
== Presentations & Activities==<br />
* not much space for presentations, perhaps rent a screen?<br />
<br />
* marketplace/message board (post-its and Header-sticker)<br />
* Happy hours Wed 24 & Thurs 25 17.00-18.30, format fixed #drinks in stock, first-come-first-serve.<br />
<br />
=== Self-Running ===<br />
'''Review in case of updates or additions'''<br />
<br />
* ''place visible links to slides or videos here''<br />
* OSGeo Live overview [http://osgeo.github.io/OSGeoLive-presentation/#/ presentation]<br />
<br />
== Other Considerations ==<br />
<br />
* Good reading: Running [http://fromtheinsidelookingin.blogspot.com/2008/10/conference-booths.html Conference Booths]<br />
* [[Operate OSGeo Booth]]<br />
<br />
[[Category: FOSS4G2016]]<br />
[[Category: FOSS4G]]<br />
[[Category: Marketing]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2016_OSGeo_Booth&diff=100017FOSS4G 2016 OSGeo Booth2016-06-29T06:27:48Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>Placeholder for organizing the OSGeo Booth at [[FOSS4G 2016]] Bonn, similar to previous years: [[FOSS4G2015_OSGeo_Booth]] Seoul, [[FOSS4G2014 OSGeo Booth]] Portland.<br />
<br />
'''Event Contacts:''' ''TBD''<br />
<br />
== Event contact ==<br />
<br />
<br />
<br />
== Floor Plan ==<br />
<br />
As always on FOSS4G OSGeo has a booth<br />
It's booth no 27 (25 is Boundless Spatial Inc., 28 is LocationTech)<br />
<br />
* ''plan to be added''<br />
see http://2016.foss4g.org/files/foss4g/media/videos/FOSS4G-Exhibition-Plan_v3.jpg<br />
<br />
Wall facing the stairs for screen/banner<br />
Corner: flyer-console<br />
<br />
== Booth Structure ==<br />
<br />
* Depending on actual location of sockets<br />
<br />
== Booth Size ==<br />
<br />
2m x 2m<br />
<br />
== Volunteers ==<br />
<br />
* [[Venkatesh Raghavan]]<br />
* [[Dirk Frigne]]<br />
* [[Angelos Tzotsos]]<br />
* [[Brent Wood]]<br />
* [[User:stevenfeldman | Steven Feldman]]<br />
* [[User:ortelius|Jeffrey Johnson]]<br />
* [[Anita Graser]] (25th)<br />
* [[Marc_Vloemans]]<br />
* [[Manuel Grizonnet]]<br />
* Add your name<br />
<br />
== Schedule ==<br />
WCCB Bonn<br />
<br />
{|class=wikitable border="1"<br />
! Day !! Hours !! <br />
|-<br />
| Tues August 23 || 15:30-18:00 || possible setup.<br />
|-<br />
| Wed August 24 || 08:30-18:00 || Regular hours, sessions running, happy hour etc.<br />
|-<br />
| Thurs August 25 || 08:30-18:00 || Regular hours, sessions running, happy hour etc.<br />
|-<br />
| Fri August 26|| 08:30-17:30 || Regular hours, sessions running, etc.<br />
|-<br />
| || 17:30-18:00 || '''Move out'''<br />
|}<br />
<br />
conference program: http://2016.foss4g.org/<br />
<br />
== Signup Schedule ==<br />
<br />
{|class=wikitable border="1"<br />
! Day !! Hours !! What !! Booth Team (2-3/slot) !! Special activity <br />
|-<br />
| Thue August 23 || 8:30-12:30 || '''Move in / Set up''' || Marc & ||<br />
|-<br />
| Wed August 24 || 10:30-13:00 || Regular hours (Exhibit Hall opens at 10:30) || ||<br />
|-<br />
| || 13:00-15:00 || Regular hours || || <br />
|-<br />
| || 15:00-17:00 || Regular hours || || <br />
|-<br />
| || 17:00-19:00 || Regular hours || Marc & ? || <br />
|-<br />
| || 17.00-18.30 || Happy Hour || ||<br />
|-<br />
| Thurs August 25 || 10:30-13:00 || Regular hours || Anita & ? ||<br />
|-<br />
| || 13:00-15:00 || Regular hours || || <br />
|-<br />
| || 15:00-17:00 || Regular hours || ||<br />
|-<br />
| || 17:00-18:30 || Regular hours || Marc & ? || <br />
|-<br />
| || 17.00-18.30 || Happy Hour || TBD || <br />
|-<br />
| || 17:30-19:00 || closed -> Annual Meeting || TBD ||<br />
|-<br />
| Fri August 26|| 10:30-13:00 || Regular hours || ||<br />
|-<br />
| || 13:00-15:00 || Regular hours || ||<br />
|-<br />
| || 15:00-16:00 || Regular hours || ||<br />
|-<br />
| || 16:00-18:30 || Take down || Marc & ||<br />
|}<br />
<br />
== Equipment ==<br />
<br />
Possible needs:<br />
<br />
* Poster?<br />
* Flyer console (to be bought)<br />
* laptops/monitors?: there is not much pace<br />
* 1 high table? drape? 2 stools/chairs? banner (1 FOSSGIS, 1 to be made), cloth banner ceiling (FOSSGIS)<br />
* screen? wired internet?<br />
(FOSSGIS e.V. has some equipement from past conferences)<br />
<br />
* stickers to be printed <br />
* OSGEo Flyer(s) to be printed<br />
<br />
<br />
* Banners:<br />
http://svn.osgeo.org/osgeo/marketing/exhibitionpack/<br />
I suggest both: OSGeo_popup and OSGeo_popup2<br />
Ask printer/see on printer-site, whether the PDF of SVG format is needed. Silk finish or silk matt finish for readability (light glare during exhibitions is high)<br />
<br />
* Brochure:<br />
OSGeo_Brochure_2010_PRINT_A4_spread.pdf<br />
(this is single A4 back and front)<br />
I suggest minimum paperweight of 100 gram paper, silk or silk matt finished.<br />
Ask printer to fold, preferably not do so yourself (bothersome and never a crips bend)<br />
Usually I count max 100 brochures per exhibition day on average. Now, 300 will do I expect.<br />
<br />
* Table runner<br />
http://svn.osgeo.org/osgeo/marketing/exhibitionpack/<br />
If printer is able to print on cloth, you could order:<br />
OSGeo_tablerunner<br />
Please check with printer if PDF or SVG file format required<br />
<br />
* CD Live disk (latest version?)<br />
http://svn.osgeo.org/osgeo/marketing/disk/<br />
Per FOSS4GNA this was still 2011 version.....Check!<br />
<br />
== Presentations & Activities==<br />
* not much space for presentations, perhaps rent a screen?<br />
<br />
* marketplace/message board (post-its and Header-sticker)<br />
* Happy hours Wed 24 & Thurs 25 17.00-18.30, format fixed #drinks in stock, first-come-first-serve.<br />
<br />
=== Self-Running ===<br />
'''Review in case of updates or additions'''<br />
<br />
* ''place visible links to slides or videos here''<br />
* OSGeo Live overview [http://osgeo.github.io/OSGeoLive-presentation/#/ presentation]<br />
<br />
== Other Considerations ==<br />
<br />
* Good reading: Running [http://fromtheinsidelookingin.blogspot.com/2008/10/conference-booths.html Conference Booths]<br />
* [[Operate OSGeo Booth]]<br />
<br />
[[Category: FOSS4G2016]]<br />
[[Category: FOSS4G]]<br />
[[Category: Marketing]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2016_Code_Sprint&diff=97849FOSS4G 2016 Code Sprint2016-04-07T08:39:29Z<p>Wiki-Grizonnetm: /* Workgroups */</p>
<hr />
<div>== CodeSprint ==<br />
<br />
Venue: Bonn, Germany<br />
<br />
This year, once again, we are following the old tradition of hosting a codesprint on the FOSS4G. More precisely, we offer a setting so that individual projects can meet for their codesprint. Since projects benefit from each other as well, the codesprint will naturally be held conjointly at one place.<br />
Unfortunately, circumstances have forced us to divide the codesprint timetable-wise.<br />
<br />
[[Image:Basecamp5.png|200px|thumb|right]]<br />
[[Image:Basecamp6.png|200px|thumb|right]]<br />
[[Image:Basecamp7.png|200px|thumb|right]]<br />
[[Image:Basecamp1.png|200px|thumb|right]]<br />
<br />
'''The first part''' is scheduled to take place directly before the conference, the second immediately after. The first two and a half days start on Sunday, August 21, 2016 at around noon and are scheduled to end on Tuesday, August 23, 2016 (open end). The '''second part''' starts in the morning of Saturday, August 27, 2016 and ends on Sunday at 12 pm.<br />
<br />
[[Image:Basecamp2.png|200px|thumb|right]]<br />
[[Image:Basecamp3.png|200px|thumb|right]]<br />
<br />
We are happy to have found a really '''awesome location''' for you. Codesprint and accommodations are combined in one hall. Check out http://www.basecamp-bonn.com/ for details about the venue.<br />
Working zones will be created for you in the breakfast area and hallways. There’s the option of finding relatively inexpensive sleeping accommodations in train sleeping cars, camping buses, classic cars and more. Additionally, an outdoor area is available for you to enjoy Bonn’s summer weather in August, while working. Healthy and not-so-healthy catering of drinks and snacks will be provided by us. Participation in codesprint is free of charge. However, overnight stays will have to be reserved and paid for by you.<br />
<br />
[[Image:Basecamp4.png|200px|thumb|right]]<br />
<br />
Another hint: the BaseCamp is within '''walking distance from the conference venue''' (WCCB) and has good access to public transportation – the Icebreaker takes place here, too.<br />
You see, it’s worthwhile booking here!<br />
<br />
As the accommodations are available to all FOSS4G participants, we will make an effort to make advance booking possible for you a few days ahead, to ensure you have the opportunity to sleep on-site and wrap up the evenings jointly. For that, it’s necessary for you to sign up (https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint) and leave your email address so that we can contact you immediately accomodation booking is available. We need your sign-up for the planning of snacks and drinks, too!<br />
<br />
This is open to all who wish to participate in one or more projects. There’s always plenty to do – it’s not all about programming. Translation, documentation, feedback, discussions, testing – all this is also important for project so everyone is cordially invited to attend the codesprints! Registration with the conference is not a prerequisite for participation in codesprint.<br />
<br />
One thing we’d like to ask you: with an approx. 120 participants anticipated, the WLAN capacity will naturally be exhausted at some point. Please be sure to avoid huge on-site downloads of data, as this could impact the work of others. Thank you!<br />
<br />
The Codesprint Organizing Team is looking forward to your coming!<br />
<br />
'''In summary:'''<br />
<br />
'''When:''' <br />
* Part I: Sun 2016-08-21 12:00 noon - Tue 2016-08-23 (open end)<br />
* Part II: Sat 2016-08-27 - Sun 2016-08-28 12:00 noon<br />
<br />
'''Where:'''<br />
* Venue & Accommodation: BaseCamp. (For more informations: http://www.basecamp-bonn.com/) [[http://www.openstreetmap.org/way/44335958#map=18/50.70763/7.12316| OpenStreetMap]]<br />
* Nearby Hotel: Bonnox (http://www.bonnox.de/en/)<br />
<br />
'''Questions/Comments/Ideas'''<br />
<br />
* If you have questions/comments/ideas please let us know. Send an email to codesprint@foss4g2016.org. You are welcome!<br />
<br />
== Sponsors ==<br />
Thanks to our great sponsors!<br />
<br />
[[File:FOSSGIS_OSGeo_DACH.png]] <br />
<br />
<br />
== Registered Attendees ==<br />
<br />
The Code Sprint does not cost any money. For us it makes planning easier if we know who is coming. So please leave your Name and mark the days you will come.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="30"|sun<br />
!width="30"|mon<br />
!width="30"|tue<br />
!width="30"|sat<br />
!width="30"|sun<br />
!width="60"|Accomodation<br />
!width="30"|vegetarian food<br />
|-<br />
| 1 ||[[User:Astrid Emde|Astrid Emde]] || astrid_emde@osgeo.org || [[Mapbender]] & Organization || x || x || x || x || x || other || x<br />
|-<br />
| 2 ||[[User:rcoup|Rob Coup]] || robert@coup.net.nz || [[GDAL]], [[GeoServer]] || ? || x || x || x || ? || Basecamp? ||<br />
|-<br />
| 3 ||[[User:alfonx|Stefan Tzeggai]] || tzeggai@wikisquare.de || || - || - || x || x || - || Basecamp? ||<br />
|-<br />
| 4 ||[[User:Neteler|Markus Neteler]] || neteler@osgeo.org || [[GRASS GIS]] || x || x || x || x || x || other || x<br />
|-<br />
| 5 ||[[User:pcav|Paolo Cavallini]] || cavallini@faunalia.it || [[QGIS]] || x || x || x || x || x || Basecamp? || <br />
|-<br />
| 6 ||[[User:Pirmin_Kalberer|Pirmin Kalberer]] || pka [ät] sourcepole.ch || [[QGIS]], [[GDAL]] || x || x || x || - || - || Basecamp || <br />
|-<br />
| 7 ||[[User:neumann|Andreas Neumann]] || andreas [ät] qgis.org || [[QGIS]] || x || x || x || x || - || Basecamp ||<br />
|-<br />
| 8 ||[[User:timlinux|Tim Sutton]] || tim [ät] qgis.org || [[QGIS]] || x || x || x || x || - || Basecamp || yes<br />
|-<br />
| 9 ||[[User:Lucadelu|Luca Delucchi]] || lucadeluge @ gmail.com || [[GRASS GIS]] || x || x || x || x || x || Basecamp || <br />
|-<br />
| 10 ||[[User:Schpidi|Stephan Meißl]]||stephan [ät] meissl.name||MapServer, EOxServer||?||?||x||-||-||Basecamp||<br />
|-<br />
| 11 ||[[User:lastools|Martin Isenburg]] || martin near rapidlasso.com || LASzip for LAS 1.4 || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 12 || [[User:jgrocha|Jorge Gustavo Rocha]] || jgr@di.uminho.pt || GeoExt 3 || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 13 || [[User:alexbruy|Alex Bruy]] || alexander.bruy at gmail.com || [[QGIS]] || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 14 || [[User:volaya|Victor Olaya]] || volayaf at gmail.com || [[QGIS]] || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 15 || [[bartvde2|Bart van den Eijnden]] || bartvde at osgis.nl || [[OpenLayers]] || x || x || x || x || x || Basecamp? ||<br />
|-<br />
| 16 || [[User:anitagraser|Anita Graser]] || anitagraser [ät] gmx.at || [[QGIS]] || x || x || x || ? || ? || Basecamp ||<br />
|-<br />
| 17 ||[[User:Dmorissette|Daniel Morissette]]||dmorissette at mapgears.com||MapServer, GDAL/OGR||?||?||x||x||?||Basecamp||<br />
|-<br />
| 18 ||[[User:Stranger | Andreas Schmitz]] || hwbllmnn@mailbox.org || Mapbender || || || || || || other ||<br />
|-<br />
| 19 ||[[User:Uli | Uli Rothstein]] || || Mapbender || || || || || || other ||<br />
|-<br />
| 20 ||[[User:Tbonfort|Thomas Bonfort]]||thomas.bonfort@gmail.com||MapServer||?||?||x||x||?||Basecamp||<br />
|-<br />
| 21 || CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 22 || CCC VOC Team|| || video || || || || || || Basecamp ||<br />
|-<br />
| 23 || CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 24 || CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 25 ||CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 26 ||[[User:Martinl|Martin Landa]] || || [[GRASS GIS]], [[GDAL]], [[QGIS]], [[PyWPS]], GIS.lab || x || x || x || x || x|| Basecamp? ||<br />
|-<br />
| 27 ||[[User:jachym|Jáchym Čepický]] || jachym.cepicky at gmail || [[PyWPS]], GIS.lab || x || x || x || x || x|| Basecamp ||<br />
|-<br />
| 28 ||[[User:Jonaseberle|Jonas Eberle]] || jonas.eberle at gmx.de || [[PyWPS]] || x || x || x || x || x || Basecamp/other? ||<br />
|-<br />
| 29 ||[[User:dassau|Otto Dassau]] ||otto at qgis.org || [[QGIS]] || x || x || x || - || - || other || yes<br />
|-<br />
| 30 ||[[User:rouault|Even Rouault]]||even.rouault @ spatialys.com||GDAL, MapServer, QGIS||?||?||x||x||?||Basecamp||<br />
|-<br />
| 31 ||[[User:grizonnetm|Manuel Grizonnet]]||manuel.grizonnet @ cnes.fr||OTB, OSGeo-Live, QGIS||x||x||x||-||-||Basecamp||<br />
|-<br />
|}<br />
<br />
= Workgroups =<br />
<br />
== Mapbender ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:Astrid Emde|Astrid Emde]]<br />
* [[User:Stranger | Andreas Schmitz]]<br />
* [[User:Uli | Uli Rothstein]]<br />
<br />
'''Goals:''' <br />
<br />
* documentation<br />
<br />
== GRASS GIS ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:Neteler|Markus Neteler]]<br />
* [[User:Lucadelu|Luca Delucchi]]<br />
* [[User:Martinl|Martin Landa]]<br />
<br />
'''Goals:''' <br />
<br />
* planning towards GRASS GIS 8<br />
<br />
== QGIS ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:pcav|Paolo Cavallini]]<br />
* [[User:Pirmin_Kalberer|Pirmin Kalberer]]<br />
* [[User:neumann|Andreas Neumann]]<br />
* [[User:volaya|Victor Olaya]]<br />
* [[User:alexbruy|Alex Bruy]]<br />
* [[User:anitagraser|Anita Graser]]<br />
* [[User:dassau|Otto Dassau]]<br />
<br />
'''Goals:''' <br />
<br />
* working on QGIS 3.0<br />
* porting plugins to Python 3<br />
* Working on QWC II<br />
* Working on QGIS Processing framework<br />
<br />
== PyWPS ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:jachym|Jachym Cepicky]]<br />
* [[User:Jonaseberle|Jonas Eberle]]<br />
<br />
'''Goals:''' <br />
<br />
* What is needed for PyWPS-4<br />
* Discuss new steps<br />
* WPS 2.0.0 start<br />
<br />
== GIS.lab ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:martinl|Martin Landa]]<br />
* [[User:jachym|Jachym Cepicky]]<br />
<br />
'''Goals:''' <br />
<br />
* GIS.lab 1.0<br />
* GIS.lab QGIS Plugin<br />
* new generation of GIS.lab Web Client<br />
* WPS Processing<br />
<br />
== OSGeo-Live ==<br />
<br />
<br />
'''Attending:''' <br />
<br />
*[[User: Astrid Emde]] <br />
* [[User:grizonnetm|Manuel Grizonnet]]<br />
<br />
'''Goals:''' <br />
<br />
* next version<br />
* documentation<br />
* translation<br />
<br />
== GeoMoose ==<br />
<br />
'''Attending:'''<br />
<br />
* [[User:theduckylittle|Dan "Ducky" Little]]<br />
<br />
''Goals:'''<br />
<br />
* 3.0 release! <br />
<br />
== ORFEO ToolBox ==<br />
<br />
'''Attending:'''<br />
<br />
* [[User:grizonnetm|Manuel Grizonnet]]<br />
<br />
''Goals:'''<br />
<br />
* Documentation<br />
* QGIS/OTB compatibility<br />
* Bugs<br />
<br />
== Project-name ==<br />
<br />
To participate, copy this project skeleton and start a section below for your project.<br />
<br />
'''Attending:''' <br />
<br />
*user <br />
*user<br />
<br />
'''Goals:''' <br />
<br />
*your goals<br />
<br />
[[Category:FOSS4G2016]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2016_Code_Sprint&diff=97824FOSS4G 2016 Code Sprint2016-04-05T17:32:01Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>== CodeSprint ==<br />
<br />
Venue: Bonn, Germany<br />
<br />
This year, once again, we are following the old tradition of hosting a codesprint on the FOSS4G. More precisely, we offer a setting so that individual projects can meet for their codesprint. Since projects benefit from each other as well, the codesprint will naturally be held conjointly at one place.<br />
Unfortunately, circumstances have forced us to divide the codesprint timetable-wise.<br />
<br />
[[Image:Basecamp5.png|200px|thumb|right]]<br />
[[Image:Basecamp6.png|200px|thumb|right]]<br />
[[Image:Basecamp7.png|200px|thumb|right]]<br />
[[Image:Basecamp1.png|200px|thumb|right]]<br />
<br />
'''The first part''' is scheduled to take place directly before the conference, the second immediately after. The first two and a half days start on Sunday, August 21, 2016 at around noon and are scheduled to end on Tuesday, August 23, 2016 (open end). The '''second part''' starts in the morning of Saturday, August 27, 2016 and ends on Sunday at 12 pm.<br />
<br />
[[Image:Basecamp2.png|200px|thumb|right]]<br />
[[Image:Basecamp3.png|200px|thumb|right]]<br />
<br />
We are happy to have found a really '''awesome location''' for you. Codesprint and accommodations are combined in one hall. Check out http://www.basecamp-bonn.com/ for details about the venue.<br />
Working zones will be created for you in the breakfast area and hallways. There’s the option of finding relatively inexpensive sleeping accommodations in train sleeping cars, camping buses, classic cars and more. Additionally, an outdoor area is available for you to enjoy Bonn’s summer weather in August, while working. Healthy and not-so-healthy catering of drinks and snacks will be provided by us. Participation in codesprint is free of charge. However, overnight stays will have to be reserved and paid for by you.<br />
<br />
[[Image:Basecamp4.png|200px|thumb|right]]<br />
<br />
Another hint: the BaseCamp is within '''walking distance from the conference venue''' (WCCB) and has good access to public transportation – the Icebreaker takes place here, too.<br />
You see, it’s worthwhile booking here!<br />
<br />
As the accommodations are available to all FOSS4G participants, we will make an effort to make advance booking possible for you a few days ahead, to ensure you have the opportunity to sleep on-site and wrap up the evenings jointly. For that, it’s necessary for you to sign up (https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint) and leave your email address so that we can contact you immediately accomodation booking is available. We need your sign-up for the planning of snacks and drinks, too!<br />
<br />
This is open to all who wish to participate in one or more projects. There’s always plenty to do – it’s not all about programming. Translation, documentation, feedback, discussions, testing – all this is also important for project so everyone is cordially invited to attend the codesprints! Registration with the conference is not a prerequisite for participation in codesprint.<br />
<br />
One thing we’d like to ask you: with an approx. 120 participants anticipated, the WLAN capacity will naturally be exhausted at some point. Please be sure to avoid huge on-site downloads of data, as this could impact the work of others. Thank you!<br />
<br />
The Codesprint Organizing Team is looking forward to your coming!<br />
<br />
'''In summary:'''<br />
<br />
'''When:''' <br />
* Part I: Sun 2016-08-21 12:00 noon - Tue 2016-08-23 (open end)<br />
* Part II: Sat 2016-08-27 - Sun 2016-08-28 12:00 noon<br />
<br />
'''Where:'''<br />
* Venue & Accommodation: BaseCamp. (For more informations: http://www.basecamp-bonn.com/) [[http://www.openstreetmap.org/way/44335958#map=18/50.70763/7.12316| OpenStreetMap]]<br />
* Nearby Hotel: Bonnox (http://www.bonnox.de/en/)<br />
<br />
'''Questions/Comments/Ideas'''<br />
<br />
* If you have questions/comments/ideas please let us know. Send an email to codesprint@foss4g2016.org. You are welcome!<br />
<br />
== Sponsors ==<br />
Thanks to our great sponsors!<br />
<br />
[[File:FOSSGIS_OSGeo_DACH.png]] <br />
<br />
<br />
== Registered Attendees ==<br />
<br />
The Code Sprint does not cost any money. For us it makes planning easier if we know who is coming. So please leave your Name and mark the days you will come.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="30"|sun<br />
!width="30"|mon<br />
!width="30"|tue<br />
!width="30"|sat<br />
!width="30"|sun<br />
!width="60"|Accomodation<br />
!width="30"|vegetarian food<br />
|-<br />
| 1 ||[[User:Astrid Emde|Astrid Emde]] || astrid_emde@osgeo.org || [[Mapbender]] & Organization || x || x || x || x || x || other || x<br />
|-<br />
| 2 ||[[User:rcoup|Rob Coup]] || robert@coup.net.nz || [[GDAL]], [[GeoServer]] || ? || x || x || x || ? || Basecamp? ||<br />
|-<br />
| 3 ||[[User:alfonx|Stefan Tzeggai]] || tzeggai@wikisquare.de || || - || - || x || x || - || Basecamp? ||<br />
|-<br />
| 4 ||[[User:Neteler|Markus Neteler]] || neteler@osgeo.org || [[GRASS GIS]] || x || x || x || x || x || other || x<br />
|-<br />
| 5 ||[[User:pcav|Paolo Cavallini]] || cavallini@faunalia.it || [[QGIS]] || x || x || x || x || x || Basecamp? || <br />
|-<br />
| 6 ||[[User:Pirmin_Kalberer|Pirmin Kalberer]] || pka [ät] sourcepole.ch || [[QGIS]], [[GDAL]] || x || x || x || - || - || Basecamp || <br />
|-<br />
| 7 ||[[User:neumann|Andreas Neumann]] || andreas [ät] qgis.org || [[QGIS]] || x || x || x || x || - || Basecamp ||<br />
|-<br />
| 8 ||[[User:timlinux|Tim Sutton]] || tim [ät] qgis.org || [[QGIS]] || x || x || x || x || - || Basecamp || yes<br />
|-<br />
| 9 ||[[User:Lucadelu|Luca Delucchi]] || lucadeluge @ gmail.com || [[GRASS GIS]] || x || x || x || x || x || Basecamp || <br />
|-<br />
| 10 ||[[User:Schpidi|Stephan Meißl]]||stephan [ät] meissl.name||MapServer, EOxServer||?||?||x||-||-||Basecamp||<br />
|-<br />
| 11 ||[[User:lastools|Martin Isenburg]] || martin near rapidlasso.com || LASzip for LAS 1.4 || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 12 || [[User:jgrocha|Jorge Gustavo Rocha]] || jgr@di.uminho.pt || GeoExt 3 || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 13 || [[User:alexbruy|Alex Bruy]] || alexander.bruy at gmail.com || [[QGIS]] || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 14 || [[User:volaya|Victor Olaya]] || volayaf at gmail.com || [[QGIS]] || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 15 || [[bartvde2|Bart van den Eijnden]] || bartvde at osgis.nl || [[OpenLayers]] || x || x || x || x || x || Basecamp? ||<br />
|-<br />
| 16 || [[User:anitagraser|Anita Graser]] || anitagraser [ät] gmx.at || [[QGIS]] || x || x || x || ? || ? || Basecamp ||<br />
|-<br />
| 17 ||[[User:Dmorissette|Daniel Morissette]]||dmorissette at mapgears.com||MapServer, GDAL/OGR||?||?||x||x||?||Basecamp||<br />
|-<br />
| 18 ||[[User:Stranger | Andreas Schmitz]] || hwbllmnn@mailbox.org || Mapbender || || || || || || other ||<br />
|-<br />
| 19 ||[[User:Uli | Uli Rothstein]] || || Mapbender || || || || || || other ||<br />
|-<br />
| 20 ||[[User:Tbonfort|Thomas Bonfort]]||thomas.bonfort@gmail.com||MapServer||?||?||x||x||?||Basecamp||<br />
|-<br />
| 21 || CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 22 || CCC VOC Team|| || video || || || || || || Basecamp ||<br />
|-<br />
| 23 || CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 24 || CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 25 ||CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 26 ||[[User:Martinl|Martin Landa]] || || [[GRASS GIS]], [[GDAL]], [[QGIS]], [[PyWPS]], GIS.lab || x || x || x || x || x|| Basecamp? ||<br />
|-<br />
| 27 ||[[User:jachym|Jáchym Čepický]] || jachym.cepicky at gmail || [[PyWPS]], GIS.lab || x || x || x || x || x|| Basecamp ||<br />
|-<br />
| 28 ||[[User:Jonaseberle|Jonas Eberle]] || jonas.eberle at gmx.de || [[PyWPS]] || x || x || x || x || x || Basecamp/other? ||<br />
|-<br />
| 29 ||[[User:dassau|Otto Dassau]] ||otto at qgis.org || [[QGIS]] || x || x || x || - || - || other || yes<br />
|-<br />
| 30 ||[[User:rouault|Even Rouault]]||even.rouault @ spatialys.com||GDAL, MapServer, QGIS||?||?||x||x||?||Basecamp||<br />
|-<br />
| 31 ||[[User:grizonnetm|Manuel Grizonnet]]||manuel.grizonnet @ cnes.fr||OTB, OSGeo-Live, QGIS||x||x||x||-||-||Basecamp||<br />
|-<br />
|}<br />
<br />
= Workgroups =<br />
<br />
== Mapbender ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:Astrid Emde|Astrid Emde]]<br />
* [[User:Stranger | Andreas Schmitz]]<br />
* [[User:Uli | Uli Rothstein]]<br />
<br />
'''Goals:''' <br />
<br />
* documentation<br />
<br />
== GRASS GIS ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:Neteler|Markus Neteler]]<br />
* [[User:Lucadelu|Luca Delucchi]]<br />
* [[User:Martinl|Martin Landa]]<br />
<br />
'''Goals:''' <br />
<br />
* planning towards GRASS GIS 8<br />
<br />
== QGIS ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:pcav|Paolo Cavallini]]<br />
* [[User:Pirmin_Kalberer|Pirmin Kalberer]]<br />
* [[User:neumann|Andreas Neumann]]<br />
* [[User:volaya|Victor Olaya]]<br />
* [[User:alexbruy|Alex Bruy]]<br />
* [[User:anitagraser|Anita Graser]]<br />
* [[User:dassau|Otto Dassau]]<br />
<br />
'''Goals:''' <br />
<br />
* working on QGIS 3.0<br />
* porting plugins to Python 3<br />
* Working on QWC II<br />
* Working on QGIS Processing framework<br />
<br />
== PyWPS ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:jachym|Jachym Cepicky]]<br />
* [[User:Jonaseberle|Jonas Eberle]]<br />
<br />
'''Goals:''' <br />
<br />
* What is needed for PyWPS-4<br />
* Discuss new steps<br />
* WPS 2.0.0 start<br />
<br />
== GIS.lab ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:martinl|Martin Landa]]<br />
* [[User:jachym|Jachym Cepicky]]<br />
<br />
'''Goals:''' <br />
<br />
* GIS.lab 1.0<br />
* GIS.lab QGIS Plugin<br />
* new generation of GIS.lab Web Client<br />
* WPS Processing<br />
<br />
== OSGeo-Live ==<br />
<br />
<br />
'''Attending:''' <br />
<br />
*[[User: Astrid Emde]] <br />
* [[User:grizonnetm|Manuel Grizonnet]]<br />
<br />
'''Goals:''' <br />
<br />
* next version<br />
* documentation<br />
* translation<br />
<br />
== Project-name ==<br />
<br />
To participate, copy this project skeleton and start a section below for your project.<br />
<br />
'''Attending:''' <br />
<br />
*user <br />
*user<br />
<br />
'''Goals:''' <br />
<br />
*your goals<br />
<br />
[[Category:FOSS4G2016]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2016_Code_Sprint&diff=97804FOSS4G 2016 Code Sprint2016-04-04T12:54:38Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>== CodeSprint ==<br />
<br />
Venue: Bonn, Germany<br />
<br />
This year, once again, we are following the old tradition of hosting a codesprint on the FOSS4G. More precisely, we offer a setting so that individual projects can meet for their codesprint. Since projects benefit from each other as well, the codesprint will naturally be held conjointly at one place.<br />
Unfortunately, circumstances have forced us to divide the codesprint timetable-wise.<br />
<br />
[[Image:Basecamp5.png|200px|thumb|right]]<br />
[[Image:Basecamp6.png|200px|thumb|right]]<br />
[[Image:Basecamp7.png|200px|thumb|right]]<br />
[[Image:Basecamp1.png|200px|thumb|right]]<br />
<br />
'''The first part''' is scheduled to take place directly before the conference, the second immediately after. The first two and a half days start on Sunday, August 21, 2016 at around noon and are scheduled to end on Tuesday, August 23, 2016 (open end). The '''second part''' starts in the morning of Saturday, August 27, 2016 and ends on Sunday at 12 pm.<br />
<br />
[[Image:Basecamp2.png|200px|thumb|right]]<br />
[[Image:Basecamp3.png|200px|thumb|right]]<br />
<br />
We are happy to have found a really '''awesome location''' for you. Codesprint and accommodations are combined in one hall. Check out http://www.basecamp-bonn.com/ for details about the venue.<br />
Working zones will be created for you in the breakfast area and hallways. There’s the option of finding relatively inexpensive sleeping accommodations in train sleeping cars, camping buses, classic cars and more. Additionally, an outdoor area is available for you to enjoy Bonn’s summer weather in August, while working. Healthy and not-so-healthy catering of drinks and snacks will be provided by us. Participation in codesprint is free of charge. However, overnight stays will have to be reserved and paid for by you.<br />
<br />
[[Image:Basecamp4.png|200px|thumb|right]]<br />
<br />
Another hint: the BaseCamp is within '''walking distance from the conference venue''' (WCCB) and has good access to public transportation – the Icebreaker takes place here, too.<br />
You see, it’s worthwhile booking here!<br />
<br />
As the accommodations are available to all FOSS4G participants, we will make an effort to make advance booking possible for you a few days ahead, to ensure you have the opportunity to sleep on-site and wrap up the evenings jointly. For that, it’s necessary for you to sign up (https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint) and leave your email address so that we can contact you immediately accomodation booking is available. We need your sign-up for the planning of snacks and drinks, too!<br />
<br />
This is open to all who wish to participate in one or more projects. There’s always plenty to do – it’s not all about programming. Translation, documentation, feedback, discussions, testing – all this is also important for project so everyone is cordially invited to attend the codesprints! Registration with the conference is not a prerequisite for participation in codesprint.<br />
<br />
One thing we’d like to ask you: with an approx. 120 participants anticipated, the WLAN capacity will naturally be exhausted at some point. Please be sure to avoid huge on-site downloads of data, as this could impact the work of others. Thank you!<br />
<br />
The Codesprint Organizing Team is looking forward to your coming!<br />
<br />
'''In summary:'''<br />
<br />
'''When:''' <br />
* Part I: Sun 2016-08-21 12:00 noon - Tue 2016-08-23 (open end)<br />
* Part II: Sat 2016-08-27 - Sun 2016-08-28 12:00 noon<br />
<br />
'''Where:'''<br />
* Venue & Accommodation: BaseCamp. (For more informations: http://www.basecamp-bonn.com/) [[http://www.openstreetmap.org/way/44335958#map=18/50.70763/7.12316| OpenStreetMap]]<br />
* Nearby Hotel: Bonnox (http://www.bonnox.de/en/)<br />
<br />
'''Questions/Comments/Ideas'''<br />
<br />
* If you have questions/comments/ideas please let us know. Send an email to codesprint@foss4g2016.org. You are welcome!<br />
<br />
== Registered Attendees ==<br />
<br />
The Code Sprint does not cost any money. For us it makes planning easier if we know who is coming. So please leave your Name and mark the days you will come.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="30"|sun<br />
!width="30"|mon<br />
!width="30"|tue<br />
!width="30"|sat<br />
!width="30"|sun<br />
!width="60"|Accomodation<br />
!width="30"|vegetarian food<br />
|-<br />
| 1 ||[[User:Astrid Emde|Astrid Emde]] || astrid_emde@osgeo.org || [[Mapbender]] & Organization || x || x || x || x || x || other || x<br />
|-<br />
| 2 ||[[User:rcoup|Rob Coup]] || robert@coup.net.nz || [[GDAL]], [[GeoServer]] || ? || x || x || x || ? || Basecamp? ||<br />
|-<br />
| 3 ||[[User:alfonx|Stefan Tzeggai]] || tzeggai@wikisquare.de || || - || - || x || x || - || Basecamp? ||<br />
|-<br />
| 4 ||[[User:Neteler|Markus Neteler]] || neteler@osgeo.org || [[GRASS GIS]] || x || x || x || x || x || other || x<br />
|-<br />
| 5 ||[[User:pcav|Paolo Cavallini]] || cavallini@faunalia.it || [[QGIS]] || x || x || x || x || x || Basecamp? || <br />
|-<br />
| 6 ||[[User:Pirmin_Kalberer|Pirmin Kalberer]] || pka [ät] sourcepole.ch || [[QGIS]], [[GDAL]] || x || x || x || - || - || Basecamp || <br />
|-<br />
| 7 ||[[User:neumann|Andreas Neumann]] || andreas [ät] qgis.org || [[QGIS]] || x || x || x || x || - || Basecamp ||<br />
|-<br />
| 8 ||[[User:timlinux|Tim Sutton]] || tim [ät] qgis.org || [[QGIS]] || x || x || x || x || - || Basecamp || yes<br />
|-<br />
| 9 ||[[User:Lucadelu|Luca Delucchi]] || lucadeluge @ gmail.com || [[GRASS GIS]] || x || x || x || x || x || Basecamp || <br />
|-<br />
| 10 ||[[User:Schpidi|Stephan Meißl]]||stephan [ät] meissl.name||MapServer, EOxServer||?||?||x||-||-||Basecamp||<br />
|-<br />
| 11 ||[[User:lastools|Martin Isenburg]] || martin near rapidlasso.com || LASzip for LAS 1.4 || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 12 || [[User:jgrocha|Jorge Gustavo Rocha]] || jgr@di.uminho.pt || GeoExt 3 || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 13 || [[User:alexbruy|Alex Bruy]] || alexander.bruy at gmail.com || [[QGIS]] || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 14 || [[User:volaya|Victor Olaya]] || volayaf at gmail.com || [[QGIS]] || x || x || x || x || x || Basecamp ||<br />
|-<br />
| 15 || [[bartvde2|Bart van den Eijnden]] || bartvde at osgis.nl || [[OpenLayers]] || x || x || x || x || x || Basecamp? ||<br />
|-<br />
| 16 || [[User:anitagraser|Anita Graser]] || anitagraser [ät] gmx.at || [[QGIS]] || x || x || x || ? || ? || Basecamp ||<br />
|-<br />
| 17 ||[[User:Dmorissette|Daniel Morissette]]||dmorissette at mapgears.com||MapServer, GDAL/OGR||?||?||x||x||?||Basecamp||<br />
|-<br />
| 20 ||[[User:Tbonfort|Thomas Bonfort]]||thomas.bonfort@gmail.com||MapServer||?||?||x||x||?||Basecamp||<br />
|-<br />
| 21 || CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 22 || CCC VOC Team|| || video || || || || || || Basecamp ||<br />
|-<br />
| 23 || CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 24 || CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 25 ||CCC VOC Team || || video || || || || || || Basecamp ||<br />
|-<br />
| 26 ||[[User:Martinl|Martin Landa]] || || [[GRASS GIS]], [[GDAL]], [[QGIS]], [[PyWPS]], GIS.lab || x || x || x || x || x|| Basecamp? ||<br />
|-<br />
| 27 ||[[User:jachym|Jáchym Čepický]] || jachym.cepicky at gmail || [[PyWPS]], GIS.lab || x || x || x || x || x|| Basecamp ||<br />
|-<br />
| 28 ||[[User:Jonaseberle|Jonas Eberle]] || jonas.eberle at gmx.de || [[PyWPS]] || x || x || x || x || x || Basecamp/other? ||<br />
|-<br />
| 29 ||[[User:dassau|Otto Dassau]] ||otto at qgis.org || [[QGIS]] || x || x || x || - || - || other || yes<br />
|-<br />
| 30 ||[[User:Stranger | Andreas Schmitz]] || hwbllmnn@mailbox.org || Mapbender || || || || || || other ||<br />
|-<br />
| 31 ||[[User:Uli | Uli Rothstein]] || || Mapbender || || || || || || other ||<br />
|-<br />
| 32 ||[[User:rouault|Even Rouault]]||even.rouault @ spatialys.com||GDAL, MapServer, QGIS||?||?||x||x||?||Basecamp||<br />
|-<br />
| 33 ||[[User:grizonnetm|Manuel Grizonnet]]||manuel.grizonnet @ cnes.fr||OTB, OSGeo-Live, QGIS||x||x||x||-||-||Basecamp||<br />
|-<br />
|}<br />
<br />
= Workgroups =<br />
<br />
== Mapbender ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:Astrid Emde|Astrid Emde]]<br />
* [[User:Stranger | Andreas Schmitz]]<br />
* [[User:Uli | Uli Rothstein]]<br />
<br />
'''Goals:''' <br />
<br />
* documentation<br />
<br />
== GRASS GIS ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:Neteler|Markus Neteler]]<br />
* [[User:Lucadelu|Luca Delucchi]]<br />
* [[User:Martinl|Martin Landa]]<br />
<br />
'''Goals:''' <br />
<br />
* planning towards GRASS GIS 8<br />
<br />
== QGIS ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:pcav|Paolo Cavallini]]<br />
* [[User:Pirmin_Kalberer|Pirmin Kalberer]]<br />
* [[User:neumann|Andreas Neumann]]<br />
* [[User:volaya|Victor Olaya]]<br />
* [[User:alexbruy|Alex Bruy]]<br />
* [[User:anitagraser|Anita Graser]]<br />
* [[User:dassau|Otto Dassau]]<br />
<br />
'''Goals:''' <br />
<br />
* working on QGIS 3.0<br />
* porting plugins to Python 3<br />
* Working on QWC II<br />
* Working on QGIS Processing framework<br />
<br />
== PyWPS ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:jachym|Jachym Cepicky]]<br />
* [[User:Jonaseberle|Jonas Eberle]]<br />
<br />
'''Goals:''' <br />
<br />
* What is needed for PyWPS-4<br />
* Discuss new steps<br />
* WPS 2.0.0 start<br />
<br />
== GIS.lab ==<br />
<br />
'''Attending:''' <br />
<br />
* [[User:martinl|Martin Landa]]<br />
* [[User:jachym|Jachym Cepicky]]<br />
<br />
'''Goals:''' <br />
<br />
* GIS.lab 1.0<br />
* GIS.lab QGIS Plugin<br />
* new generation of GIS.lab Web Client<br />
* WPS Processing<br />
<br />
== Project-name ==<br />
<br />
To participate, copy this project skeleton and start a section below for your project.<br />
<br />
'''Attending:''' <br />
<br />
*user <br />
*user<br />
<br />
'''Goals:''' <br />
<br />
*your goals<br />
<br />
[[Category:FOSS4G2016]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Code_Provenance_Review&diff=96542OTB Code Provenance Review2016-02-12T12:56:46Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>= Committers =<br />
<br />
List of all OTB committers since 2006:<br />
<br />
* Amit Kulkarni<br />
* Angelos Tzotsos<br />
* Arnaud Jaen<br />
* Aurelien Bricier<br />
* Caroline Ruffel<br />
* Charles Peyrega<br />
* Chia Aik Song<br />
* Christophe Palmann<br />
* Conrad Bielski<br />
* Cyrille Valladeau<br />
* Daphne Deleflie<br />
* Emmanuel Christophe<br />
* Etienne Bougoin<br />
* Gregoire Mercier<br />
* Guillaume Borrut<br />
* Guillaume Pasero<br />
* Jonathan Guinet<br />
* Jordi Inglada<br />
* Julien Malik<br />
* Julien Michel<br />
* Luc Hermitte<br />
* Manuel Grizonnet<br />
* Mathieu Deltorre<br />
* Mickael Savinaud<br />
* Otmane Lahlou<br />
* Patrick Imbo<br />
* Rashad Kanavath<br />
* Romain Garrigues<br />
* Rosa Ruiloba<br />
* Sebastien Dinot<br />
* Sebastien Harasse<br />
* Stephane Albert<br />
* Thomas Feuvrier<br />
* Tishampati Dhar<br />
* Vincent Poulain<br />
* Yin Tiangang<br />
<br />
Actual committers to OTB:<br />
<br />
* sdinot (Sébastien Dinot)<br />
* jmalik (Julien Malik)<br />
* msavinaud (Mickaël Savinaud)<br />
* mgrizonnet (Manuel Grizonnet)<br />
* jmichel (Julien Michel)<br />
* gpasero (Guillaume Pasero)<br />
* abricier (Aurélien Bricier)<br />
* jinglada (Jordi Inglada)<br />
* rkanavath (Rashad Kanavath)<br />
* cpalmann (Christophe Palmann)<br />
* salbert (Stéphane Albert)<br />
* lhermitte (Luc Hermitte)<br />
* poughov (Victor Poughon)<br />
<br />
An updated list of all contributors to the library is also available in the [https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech36.html#x69-48700036 OTB Software Guide] (Chapter 36 - Contributors).<br />
<br />
= Outstanding Issues =<br />
There is no outstanding issue regarding OTB code provenance. OTB integrates in one module a dependency to the 6S library (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) In the meantime OTB module which use 6S has been deactivated from the Debian package. <br />
<br />
= Included Libraries =<br />
<br />
List of third party libraries source code integrated in OTB source tree: <br />
* 6S<br />
* SiftFast<br />
* Boost (type_traits)<br />
* OssimPLugins<br />
<br />
Other OTB dependencies are not included in the source tree.<br />
<br />
== Free Libraries ==<br />
<br />
* 6S<br />
* SiftFast<br />
* Boost type_traits<br />
* OssimPLugins<br />
<br />
== Non-Free Libraries ==<br />
OTB does not include any non-free libraries.<br />
<br />
== Code Review ==<br />
An extensive code review is in progress in the frame of the licence modification for OTB (from CeCILL to Apache). I can provide the link to Landon to follow the progress (work in progress). <br />
<br />
Moreover CNES commissioned [https://www.blackducksoftware.com/ Black Duck] to perform a code review of the library in 2011. The report points only 6S which is publicly available but without license (its authors gave a special permission to Orfeo Toolbox team ton include it). I don't think that I can make the report public.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Code_Provenance_Review&diff=96541OTB Code Provenance Review2016-02-12T12:53:07Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>= Committers =<br />
<br />
List of all OTB committers since 2006:<br />
<br />
* Amit Kulkarni<br />
* Angelos Tzotsos<br />
* Arnaud Jaen<br />
* Aurelien Bricier<br />
* Caroline Ruffel<br />
* Charles Peyrega<br />
* Chia Aik Song<br />
* Christophe Palmann<br />
* Conrad Bielski<br />
* Cyrille Valladeau<br />
* Daphne Deleflie<br />
* Emmanuel Christophe<br />
* Etienne Bougoin<br />
* Gregoire Mercier<br />
* Guillaume Borrut<br />
* Guillaume Pasero<br />
* Jonathan Guinet<br />
* Jordi Inglada<br />
* Julien Malik<br />
* Julien Michel<br />
* Luc Hermitte<br />
* Manuel Grizonnet<br />
* Mathieu Deltorre<br />
* Mickael Savinaud<br />
* Otmane Lahlou<br />
* Patrick Imbo<br />
* Rashad Kanavath<br />
* Romain Garrigues<br />
* Rosa Ruiloba<br />
* Sebastien Dinot<br />
* Sebastien Harasse<br />
* Stephane Albert<br />
* Thomas Feuvrier<br />
* Tishampati Dhar<br />
* Vincent Poulain<br />
* Yin Tiangang<br />
<br />
Actual committers to OTB:<br />
<br />
* sdinot (Sébastien Dinot)<br />
* jmalik (Julien Malik)<br />
* msavinaud (Mickaël Savinaud)<br />
* mgrizonnet (Manuel Grizonnet)<br />
* jmichel (Julien Michel)<br />
* gpasero (Guillaume Pasero)<br />
* abricier (Aurélien Bricier)<br />
* jinglada (Jordi Inglada)<br />
* rkanavath (Rashad Kanavath)<br />
* cpalmann (Christophe Palmann)<br />
* salbert (Stéphane Albert)<br />
* lhermitte (Luc Hermitte)<br />
* poughov (Victor Poughon)<br />
<br />
An updated list of all contributors to the library is also available in the [https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech36.html#x69-48700036 OTB Software Guide] (Chapter 36 - Contributors).<br />
<br />
= Outstanding Issues =<br />
There is no outstanding issue regarding OTB code provenance. OTB integrates in one module a dependency to the 6S library (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) In the meantime OTB module which use 6S has been deactivated from the Debian package. <br />
<br />
= Included Libraries =<br />
<br />
List of third party libraries source code integrated in OTB source tree: <br />
* 6S<br />
* SiftFast<br />
* Boost (type_traits)<br />
* OssimPLugins<br />
<br />
Other OTB dependencies are not included in the source tree.<br />
<br />
== Free Libraries ==<br />
<br />
* 6S<br />
* SiftFast<br />
* Boost type_traits<br />
* OssimPLugins<br />
<br />
== Non-Free Libraries ==<br />
OTB does not include any non-free libraries.<br />
<br />
== Code Review ==<br />
An extensive code review is in progress in the frame of the licence modification for OTB (from CeCILL to Apache). I can provide the link to Landon to follow the progress (work in progress).<br />
<br />
Moreover CNES commissioned [https://www.blackducksoftware.com/ Black Duck] to perform a code review of the library in 2011. The report points only 6S which is publicly available but without license (its authors gave a special permission to Orfeo Toolbox team ton include it). I don't think that I can make the report public.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Project_Incubation_Status&diff=96540OTB Project Incubation Status2016-02-12T12:48:40Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>==General==<br />
<br />
#'''Has the project been approved for incubation by the OSGeo board?''' <br />
Yes. Announcement was made publicly on December 17, 2013.<br />
#'''Has an Incubation Mentor been assigned to the project?''' <br />
Yes. Landon Blake.<br />
<br />
<br />
==Infrastructure Transition==<br />
<br />
#'''Has the projectname.osgeo.org domain been populated with the projects web presence? If not why, and has the project page got a prominent link to the real home?''' <br />
No. An existing web page exists: http://orfeo-toolbox.org/otb/<br />
#'''Is the OSGeo bug tracker being used for the project? If not, why? Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project? If not, why?''' <br />
No. An existing bug tracker is being used by the project: http://bugs.orfeo-toolbox.org<br />
#'''Is the OSGeo SVN being used for the project? If not, why?''' <br />
No. An existing version control system is being used for the project: http://hg.orfeo-toolbox.org/OTB<br />
#'''Are binary and source downloads available from http://download.osgeo.org ? If not, why?'''<br />
No. Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html<br />
<br />
==Community Functioning==<br />
<br />
#'''Is there a functioning user support mechanisms (ie. mailing list)?''' <br />
The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#'''Are source and binary downloads for the package available?''' <br />
Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html <br />
#'''Has a Project Steering Committee been formed, and given control of the project?''' <br />
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)<br />
<br />
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.<br />
<br />
#'''Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines?''' <br />
#'''How many active developers are there? Are they from multiple organizations? Indicate number and some organizations involved.'''<br />
The ohloh page of the Orfeo ToolBox provides a comprehensive view of contributors activity:<br />
<br />
http://www.ohloh.net/p/otb/contributors?sort=latest_commit<br />
<br />
There were around 15 committers over the last year.<br />
<br />
The "Contributors" chapter of the Software Guide gives a complete listing of all contributors and their affiliations from the beginning of the project :<br />
<br />
http://orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech35.html#x64-52100035<br />
<br />
Very active users and occasional contributors include:<br />
<br />
*Jordi Inglada from CESBIO/CNES is the creator of OTB and as such wrote a lot of OTB code in the past. He still actively uses and promotes it, with a lot of client codes, testing, bug reports, phd and intern works ...<br />
*Gregoire Mercier from Télécom Bretagne wrote the entire wavelet transform code as well as other codes, and currently has a phd working with OTB,<br />
*Angelos Tzotzos from National Technical University of Athens is actively packaging OTB for OpenSuse. He also contributed code for a pan-sharpening algorithm and integrated some OTB in the Gnorasi project,<br />
*Agustin Lobo, who I believe is with CSIC, is a very active user that benchmarked some of OTB functions and makes insightful comments on improving documentation for instance,<br />
*Julien Radoux (UCL) has contributed some algorithms by the past and is still very active on the users list,<br />
*Emmanuel Christophe, currently with Google, who wrote a great deal of OTB code by the past, under CNES and Crisp affiliations.<br />
<br />
==Foundation Membership==<br />
#'''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.''' <br />
The project documentation has been modified to reflect membership in OSGeo.<br />
<br />
#'''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.'''<br />
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.<br />
<br />
==Code Copyright Review==<br />
#'''Has a Code Provenance Review document been prepared for the project?''' <br />
[[OTB Code Provenance Review]]<br />
#'''Have issues raised in the provenance review been adequately addressed? Indicate outstanding issues.''' <br />
<br />
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].<br />
<br />
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...).<br />
<br />
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)<br />
<br />
In the meantime OTB module which use 6S has been deactivated from the Debian package.<br />
<br />
#'''Are Committer Responsibilities Guidelines covering legal issues in place?'''<br />
Planned in 2016.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Project_Incubation_Status&diff=96539OTB Project Incubation Status2016-02-12T12:39:36Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>==General==<br />
<br />
#'''Has the project been approved for incubation by the OSGeo board?''' <br />
Yes. Announcement was made publicly on December 17, 2013.<br />
#'''Has an Incubation Mentor been assigned to the project?''' <br />
Yes. Landon Blake.<br />
<br />
<br />
==Infrastructure Transition==<br />
<br />
#'''Has the projectname.osgeo.org domain been populated with the projects web presence? If not why, and has the project page got a prominent link to the real home?''' <br />
No. An existing web page exists: http://orfeo-toolbox.org/otb/<br />
#'''Is the OSGeo bug tracker being used for the project? If not, why? Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project? If not, why?''' <br />
No. An existing bug tracker is being used by the project: http://bugs.orfeo-toolbox.org<br />
#'''Is the OSGeo SVN being used for the project? If not, why?''' <br />
No. An existing version control system is being used for the project: http://hg.orfeo-toolbox.org/OTB<br />
#'''Are binary and source downloads available from http://download.osgeo.org ? If not, why?'''<br />
No. Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html<br />
<br />
==Community Functioning==<br />
<br />
#'''Is there a functioning user support mechanisms (ie. mailing list)?''' <br />
The project currently provides support through a mailing list, managed using Google Groups (otb-users and otb-developers).<br />
#'''Are source and binary downloads for the package available?''' <br />
Downloads are available from the existing web site: http://orfeo-toolbox.org/otb/download.html <br />
#'''Has a Project Steering Committee been formed, and given control of the project?''' <br />
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)<br />
<br />
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.<br />
<br />
#'''Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines?''' <br />
#'''How many active developers are there? Are they from multiple organizations? Indicate number and some organizations involved.'''<br />
The ohloh page of the Orfeo ToolBox provides a comprehensive view of contributors activity:<br />
<br />
http://www.ohloh.net/p/otb/contributors?sort=latest_commit<br />
<br />
There were around 15 committers over the last year.<br />
<br />
The "Contributors" chapter of the Software Guide gives a complete listing of all contributors and their affiliations from the beginning of the project :<br />
<br />
http://orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech35.html#x64-52100035<br />
<br />
Very active users and occasional contributors include:<br />
<br />
*Jordi Inglada from CESBIO/CNES is the creator of OTB and as such wrote a lot of OTB code in the past. He still actively uses and promotes it, with a lot of client codes, testing, bug reports, phd and intern works ...<br />
*Gregoire Mercier from Télécom Bretagne wrote the entire wavelet transform code as well as other codes, and currently has a phd working with OTB,<br />
*Angelos Tzotzos from National Technical University of Athens is actively packaging OTB for OpenSuse. He also contributed code for a pan-sharpening algorithm and integrated some OTB in the Gnorasi project,<br />
*Agustin Lobo, who I believe is with CSIC, is a very active user that benchmarked some of OTB functions and makes insightful comments on improving documentation for instance,<br />
*Julien Radoux (UCL) has contributed some algorithms by the past and is still very active on the users list,<br />
*Emmanuel Christophe, currently with Google, who wrote a great deal of OTB code by the past, under CNES and Crisp affiliations.<br />
<br />
==Foundation Membership==<br />
#'''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.''' <br />
The project documentation has been modified to reflect membership in OSGeo.<br />
<br />
#'''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.'''<br />
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.<br />
<br />
==Code Copyright Review==<br />
#'''Has a Code Provenance Review document been prepared for the project?''' <br />
[[OTB Code Provenance Review]]<br />
#'''Have issues raised in the provenance review been adequately addressed? Indicate outstanding issues.''' <br />
#'''Are Commiter Responsibilities Guidelines covering legal issues in place?'''</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Incubation_Application&diff=96538OTB Incubation Application2016-02-12T12:35:49Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>==About OTB==<br />
The project is the Orfeo Toolbox (OTB) available at http://www.orfeo-toolbox.org. This is a project started by CNES (the French Space Agency) in 2006 to provide open source tools to process satellite images and extract information. There are several links with other OSGeo project such as Gdal and ossim, QGIS. The project is currently released under the CeCILL license (compatible with GPL).<br />
<br />
==Answers to the Incubator Application Questionnaire== <br />
<br />
1. Please provide the name and email address of the principal Project Owner. <br />
<br />
Julien Michel (julien.michel@…)<br />
<br />
2. Please provide the names and emails of co-project owners (if any). <br />
<br />
You can find the list of current members of OTB Project Steering committee [http://wiki.orfeo-toolbox.org/index.php/Project_Steering_Committee#PSC_members here].<br />
<br />
3. Please provide the names, emails and entity affiliation of all official committers.<br />
<br />
http://www.ohloh.net/p/otb/contributors?page=1 from CNES, CS (mostly under a contract with CNES), Telecom Bretagne, Google, National Technical University of Athens...<br />
<br />
4. Please describe your Project.<br />
Provide open source tools to process satellite images and extract information<br />
<br />
5. Why is hosting at OSGeo good for your project? <br />
<br />
It would be good for our project to be associated with OSGeo (public awareness, quality control and cooperation with other OSGeo projects like QGIS or Grass). It would be also really interesting to get an access to the OSGeo infrastructure (website, mailing list...)<br />
<br />
6. Type of application does this project represent(client, server, standalone, library, etc.).<br />
<br />
Library with some applications with Graphical User Interfaces (OTB-Applications and Monteverdi).<br />
<br />
7. Please describe any relationships to other open source projects. <br />
<br />
Intensive use of ITK, Gdal and ossim. OTB applications are also available through Quantum GIS plugins (through the Sextante plugin)<br />
<br />
8. Please describe any relationships with commercial companies or products. <br />
<br />
9. Which open source license(s) will the source code be released under? <br />
<br />
CeCILL (GPL compatible)<br />
<br />
10. Is there already a beta or official release? <br />
<br />
Current release is 3.18.1 for OTB and 1.16.0 for Monteverdi and 0.4 for Monteverdi2. Next release planned end of 2013.<br />
<br />
11. What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)? <br />
<br />
Government (CNES the French Space Agency)<br />
<br />
12. Does the project support open standards? Which ones and to what extent? (OGC, w3c, ect.) Has the software been certified to any standard (CITE for example)? If not, is it the intention of the project owners to seek certification at some point? OTB supports open data standard through GDAL and OGR<br />
<br />
13. Is the code free of patents, trademarks, and do you control the copyright? <br />
<br />
The code is free of patents and trademarks and the copyright is controlled by CNES.<br />
<br />
14. How many people actively contribute (code, documentation, other?) to the project at this time? <br />
<br />
10/15 people currently contributing.<br />
<br />
15. How many people have commit access to the source code respository? <br />
<br />
Distributed source control is used (mercurial) so some people are participating through other members of the team. Currently 20 people have a push access to the main repository (including 6 from CS under contract with CNES).<br />
<br />
16. Approximately how many users are currently using this project? <br />
<br />
That's hard to . For now, there is still not so many people who get a access to Very High Resolution remote sensing image (even if OTB can process other type of data). We observed a significantly increase of the number of downloads since 2010. The availability of binary packages (on Linux, Windows, Mac) helps a lot to increase the number of OTB users.<br />
<br />
17. What type of users does your project attract (government, commercial, hobby, academic research, etc. )? <br />
<br />
government, academic research, company<br />
<br />
18. If you do not intend to host any portion of this project using the OSGeo infrastructure, why should you be considered a member project of the OSGeo Foundation? <br />
<br />
We intend if it is possible to host portion of the project using the OSGeo infrastructure and we are convinced that the incubation of OTB will really increase interactions with other projects of the foundation<br />
<br />
19. Does the project include an automated build and test? <br />
<br />
cmake and ctest with a nightly submission of more that 2600 tests on more than 10 different platforms (see dash.orfeo-toolbox.org/).<br />
<br />
20. What language(s) are used in this project? <br />
<br />
(C/Java/perl/etc) C++ with availability of python binding...<br />
<br />
21. What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers? <br />
<br />
The dominant language is english (code, comments, mailing lists and documentation)<br />
<br />
22. What is the (estimated) size of a full release of this project? How many users do you expect to download the project when it is released? <br />
<br />
28 MB for the source, 14 MB for the windows binary release. Around 3000 downloads for the latest release on sourceforge ( http://sourceforge.net/projects/orfeo-toolbox/files/), but the files are available from other sources as well. What is the (estimated) size of a full release of this project? How many users do you expect to download the project when it is released?<br />
<br />
[[Category:Incubation]]<br />
[[Category:Committees]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Code_Provenance_Review&diff=89256OTB Code Provenance Review2015-12-03T08:57:26Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>= Committers =<br />
<br />
List of all OTB committers since 2006:<br />
<br />
* Amit Kulkarni<br />
* Angelos Tzotsos<br />
* Arnaud Jaen<br />
* Aurelien Bricier<br />
* Caroline Ruffel<br />
* Charles Peyrega<br />
* Chia Aik Song<br />
* Christophe Palmann<br />
* Conrad Bielski<br />
* Cyrille Valladeau<br />
* Daphne Deleflie<br />
* Emmanuel Christophe<br />
* Etienne Bougoin<br />
* Gregoire Mercier<br />
* Guillaume Borrut<br />
* Guillaume Pasero<br />
* Jonathan Guinet<br />
* Jordi Inglada<br />
* Julien Malik<br />
* Julien Michel<br />
* Luc Hermitte<br />
* Manuel Grizonnet<br />
* Mathieu Deltorre<br />
* Mickael Savinaud<br />
* Otmane Lahlou<br />
* Patrick Imbo<br />
* Rashad Kanavath<br />
* Romain Garrigues<br />
* Rosa Ruiloba<br />
* Sebastien Dinot<br />
* Sebastien Harasse<br />
* Stephane Albert<br />
* Thomas Feuvrier<br />
* Tishampati Dhar<br />
* Vincent Poulain<br />
* Yin Tiangang<br />
<br />
Actual committers to OTB:<br />
<br />
* sdinot (Sébastien Dinot)<br />
* jmalik (Julien Malik)<br />
* msavinaud (Mickaël Savinaud)<br />
* mgrizonnet (Manuel Grizonnet)<br />
* jmichel (Julien Michel)<br />
* gpasero (Guillaume Pasero)<br />
* abricier (Aurélien Bricier)<br />
* jinglada (Jordi Inglada)<br />
* rkanavath (Rashad Kanavath)<br />
* cpalmann (Christophe Palmann)<br />
* salbert (Stéphane Albert)<br />
* lhermitte (Luc Hermitte)<br />
* poughov (Victor Poughon)<br />
<br />
An updated list of all contributors to the library is also available in the [https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech36.html#x69-48700036 OTB Software Guide] (Chapter 36 - Contributors).<br />
<br />
= Outstanding Issues =<br />
<br />
= Included Libraries =<br />
<br />
List of third party libraries source code integrated in OTB source tree: <br />
* 6S<br />
* SiftFast<br />
* Boost (type_traits)<br />
* OssimPLugins<br />
<br />
Other OTB dependencies are not included in the source tree.<br />
<br />
== Free Libraries ==<br />
<br />
* 6S<br />
* SiftFast<br />
* Boost type_traits<br />
* OssimPLugins<br />
<br />
== Non-Free Libraries ==<br />
OTB does not include any non-free libraries.<br />
<br />
== Code Review ==<br />
An extensive code review is in progress in the frame of the licence modification for OTB (from CeCILL to Apache). I can provide the link to Landon to follow the progress (work in progress).<br />
<br />
Moreover CNES commissioned [https://www.blackducksoftware.com/ Black Duck] to perform a code review of the library in 2011. The report points only 6S which is publicly available but without license (its authors gave a special permission to Orfeo Toolbox team ton include it). I don't think that I can make the report public.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Code_Provenance_Review&diff=89255OTB Code Provenance Review2015-12-03T08:23:05Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>= Committers =<br />
<br />
List of all OTB committers since 2006:<br />
* <br />
* Amit Kulkarni<br />
* Angelos Tzotsos<br />
* Arnaud Jaen<br />
* Aurelien Bricier<br />
* Caroline Ruffel<br />
* Charles Peyrega<br />
* Chia Aik Song<br />
* Christophe Palmann<br />
* Conrad Bielski<br />
* Cyrille Valladeau<br />
* Daphne Deleflie<br />
* Emmanuel Christophe<br />
* Etienne Bougoin<br />
* Gregoire Mercier<br />
* Guillaume Borrut<br />
* Guillaume Pasero<br />
* Jonathan Guinet<br />
* Jordi Inglada<br />
* Julien Malik<br />
* Julien Michel<br />
* Luc Hermitte<br />
* Manuel Grizonnet<br />
* Mathieu Deltorre<br />
* Mickael Savinaud<br />
* Otmane Lahlou<br />
* Patrick Imbo<br />
* Rashad Kanavath<br />
* Romain Garrigues<br />
* Rosa Ruiloba<br />
* Sebastien Dinot<br />
* Sebastien Harasse<br />
* Stephane Albert<br />
* Thomas Feuvrier<br />
* Tishampati Dhar<br />
* Vincent Poulain<br />
* Yin Tiangang<br />
<br />
Actual committers to OTB:<br />
<br />
* sdinot (Sébastien Dinot)<br />
* jmalik (Julien Malik)<br />
* msavinaud (Mickaël Savinaud)<br />
* mgrizonnet (Manuel Grizonnet)<br />
* jmichel (Julien Michel)<br />
* gpasero (Guillaume Pasero)<br />
* abricier (Aurélien Bricier)<br />
* jinglada (Jordi Inglada)<br />
* rkanavath (Rashad Kanavath)<br />
* cpalmann (Christophe Palmann)<br />
* salbert (Stéphane Albert)<br />
* lhermitte (Luc Hermitte)<br />
* poughov (Victor Poughon)<br />
<br />
<br />
An updated list of all contributors to the library is also available in the [https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech36.html#x69-48700036 OTB Software Guide] (Chapter 36 - Contributors).<br />
<br />
= Outstanding Issues =<br />
<br />
= Included Libraries =<br />
<br />
List of third party libraries source code integrated in OTB source tree: <br />
* 6S<br />
* SiftFast<br />
* Boost (type_traits)<br />
* OssimPLugins<br />
<br />
Other OTB dependencies are not included in the source tree.<br />
<br />
== Free Libraries ==<br />
<br />
* 6S<br />
* SiftFast<br />
* Boost type_traits<br />
* OssimPLugins<br />
<br />
== Non-Free Libraries ==<br />
OTB does not include any non-free libraries.<br />
<br />
== Code Review ==<br />
An extensive code review is in progress in the frame of the licence modification for OTB (from CeCILL to Apache). I can provide the link to Landon to follow the progress (work in progress).<br />
<br />
Moreover CNES commissioned [https://www.blackducksoftware.com/ Black Duck] to perform a code review of the library in 2011. The report points only 6S which is publicly available but without license (its authors gave a special permission to Orfeo Toolbox team ton include it). I don't think that I can make the report public.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Code_Provenance_Review&diff=89224OTB Code Provenance Review2015-12-02T18:00:18Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>= Committers =<br />
<br />
TODO: add git committers list here<br />
<br />
An updated list of all contributors to the library is available in the official [https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech36.html#x69-48700036 OTB Software Guide] (Chapter 36 - Contributors).<br />
<br />
= Outstanding Issues =<br />
<br />
= Included Libraries =<br />
<br />
List of third party libraries source code integrated in OTB source tree: <br />
* 6S<br />
* SiftFast<br />
* Boost (type_traits)<br />
* OssimPLugins<br />
<br />
Other OTB dependencies are not included in the source tree.<br />
<br />
== Free Libraries ==<br />
<br />
* 6S<br />
* SiftFast<br />
* Boost type_traits<br />
* OssimPLugins<br />
<br />
== Non-Free Libraries ==<br />
OTB does not include any non-free libraries.<br />
<br />
== Code Review ==<br />
An extensive code review is in progress in the frame of the licence modification for OTB (from CeCILL to Apache). I can provide the link to Landon to follow the progress (work in progress).<br />
<br />
Moreover CNES commissioned [https://www.blackducksoftware.com/ Black Duck] to perform a code review of the library in 2011. The report points only 6S which is publicly available but without license (its authors gave a special permission to Orfeo Toolbox team ton include it). I don't think that I can make the report public.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Code_Provenance_Review&diff=89223OTB Code Provenance Review2015-12-02T17:59:36Z<p>Wiki-Grizonnetm: /* Code Review */</p>
<hr />
<div>= Committers =<br />
<br />
TODO: add committers list here<br />
<br />
An updated list of all contributors to the library is available in the official [https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech36.html#x69-48700036 OTB Software Guide] (Chapter 36 - Contributors).<br />
<br />
= Outstanding Issues =<br />
<br />
= Included Libraries =<br />
<br />
List of third party libraries source code integrated in OTB source tree: <br />
* 6S<br />
* SiftFast<br />
* Boost (type_traits)<br />
* OssimPLugins<br />
<br />
Other OTB dependencies are not included in the source tree.<br />
<br />
== Free Libraries ==<br />
<br />
* 6S<br />
* SiftFast<br />
* Boost type_traits<br />
* OssimPLugins<br />
<br />
== Non-Free Libraries ==<br />
OTB does not include any non-free libraries.<br />
<br />
== Code Review ==<br />
An extensive code review is in progress in the frame of the licence modification for OTB (from CeCILL to Apache). I can provide the link to Landon to follow the progress (work in progress).<br />
<br />
Moreover CNES commissioned [https://www.blackducksoftware.com/ Black Duck] to perform a code review of the library in 2011. The report points only 6S which is publicly available but without license (its authors gave a special permission to Orfeo Toolbox team ton include it). I don't think that I can make the report public.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Code_Provenance_Review&diff=89216OTB Code Provenance Review2015-12-02T17:31:37Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>= Committers =<br />
<br />
TODO: add committers list here<br />
<br />
An updated list of all contributors to the library is available in the official [https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech36.html#x69-48700036 OTB Software Guide] (Chapter 36 - Contributors).<br />
<br />
= Outstanding Issues =<br />
<br />
= Included Libraries =<br />
<br />
List of third party libraries source code integrated in OTB source tree: <br />
* 6S<br />
* SiftFast<br />
* Boost (type_traits)<br />
* OssimPLugins<br />
<br />
Other OTB dependencies are not included in the source tree.<br />
<br />
== Free Libraries ==<br />
<br />
* 6S<br />
* SiftFast<br />
* Boost type_traits<br />
* OssimPLugins<br />
<br />
== Non-Free Libraries ==<br />
OTB does not include any non-free libraries.<br />
<br />
== Code Review ==<br />
An extensive code review is in progress in the frame of the licence modification for OTB (from CeCILL to Apache). I can provide the link to Landon to follow the progress (work in progress).<br />
<br />
Moreover CNES commissioned [https://www.blackducksoftware.com/ Black Duck] to perform a code review of the library in 2011. The report points only 6S which is publicly available but without license (its authors gave a special permission to Orfeo Toolbox team ton include it). I don't think that I can make this public.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=OTB_Code_Provenance_Review&diff=89215OTB Code Provenance Review2015-12-02T17:30:28Z<p>Wiki-Grizonnetm: </p>
<hr />
<div>= Committers =<br />
<br />
TODO: add committers list here<br />
<br />
An updated list of all contributors to the library is available in the official [https://www.orfeo-toolbox.org/SoftwareGuide/SoftwareGuidech36.html#x69-48700036 OTB Software Guide] (Chapter 36 - Contributors).<br />
<br />
= Outstanding Issues =<br />
<br />
= Included Libraries =<br />
<br />
List of third party libraries source code integrated in OTB source tree: <br />
* 6S<br />
* SiftFast<br />
* Boost type_traits<br />
* OssimPLugins<br />
<br />
Other OTB dependencies are not included in the source tree.<br />
<br />
== Free Libraries ==<br />
<br />
* 6S<br />
* SiftFast<br />
* Boost type_traits<br />
* OssimPLugins<br />
<br />
== Non-Free Libraries ==<br />
OTB does not include any non-free libraries.<br />
<br />
== Code Review ==<br />
An extensive code review is in progress in the frame of the licence modification for OTB (from CeCILL to Apache). I can provide the link to Landon to follow the progress (work in progress).<br />
<br />
Moreover CNES commissioned [https://www.blackducksoftware.com/ Black Duck] to perform a code review of the library in 2011. I don't think that I can make this public. The report points only 6S which is publicly available but without license (its authors gave a special permission to Orfeo Toolbox team ton include it).</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=POSS_2015&diff=87118POSS 20152015-10-12T06:53:58Z<p>Wiki-Grizonnetm: /* Qui */</p>
<hr />
<div>Page d'organisation ddu stand OSGeo au Paris Open source Summit 2015<br />
<br />
* http://opensourcesummit.paris/<br />
<br />
<pre><br />
Paris Open Source Summit, 1er événement européen Libre et Open Source, est le fruit de la fusion de Solutions Linux et de l’Open World Forum, deux événements emblématiques du Libre et de l’Open Source.<br />
<br />
Son ambition est d'exposer les innovations technologiques, la réalité et le dynamisme économique des solutions et acteurs de cette filière numérique, ainsi que leurs impacts sociétaux.<br />
</pre><br />
<br />
== Qui ==<br />
<br />
* Etienne Delay (point de contact)<br />
* Jean-Marie Arsac<br />
* Yves Jacolin<br />
* Manuel Grizonnet<br />
<br />
== Hébergement ==<br />
<br />
* Qui ? Jean-Marie<br />
<br />
À définir : réserver appart Hôtel<br />
<br />
== Déplacement ==<br />
<br />
* Jean-Marie<br />
* Yves<br />
* Etienne<br />
<br />
== Stand ==<br />
<br />
* Qui gère ? Etienne<br />
<br />
== Budget ==<br />
<br />
* Qui ? Jean-Marie<br />
<br />
=== Dépences ===<br />
<br />
* hébergement :<br />
* déplacement : 400 €<br />
* repas : 3 personnes * 2 jours * 20 €<br />
* goodies : <br />
<br />
=== Recettes ===<br />
<br />
Faire une demande à l'OSGeo-fr rapidement !<br />
<br />
== Annonces ==<br />
<br />
* Yves<br />
<br />
=== Présence OSGeo-fr au POSS 2015 ===<br />
<br />
* Site Web OSGeo-fr<br />
* Liste Francophone<br />
<br />
<br />
==== English version ====<br />
<br />
* Liste Discuss<br />
<br />
[[Category: Local chapter francophone]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=Fall_2014_Committee_Report_for_OSGeo_Journal&diff=80590Fall 2014 Committee Report for OSGeo Journal2014-11-04T13:14:39Z<p>Wiki-Grizonnetm: /* OTB Project */</p>
<hr />
<div>==OTB Project==<br />
* Project has moved through the first four (4) phases of the incubation process and is preparing for the code provenance review. Graduation is expected in the Spring of 2015.<br />
<br />
** Web site redesign: We are currently revamping the web site to get an up-to-date look and feel, and have a better integration between site and other web components. As soon as we have a draft new version to show, we will provide you with a link. We've already integrated the OSGEO logo on the website and indicate that OTB is in incubation.<br />
<br />
** Code provenance review: there is a related discussion presently on the debian GIS mailing list related to the integration of OTB and also discussion about integrated third parties in OTB.<br />
<br />
<br />
[[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/022918.html | http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/022918.html]]<br />
[[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023010.html | http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023010.html]]<br />
[[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023011.html | http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023011.html]]<br />
[[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023012.html | http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023012.html]]<br />
[[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023675.html | http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023675.html]]<br />
[[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023773.html | http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023773.html]]<br />
<br />
Don't think that there will have major issue with code provenance with OTB but I think that discussion with Debian guys will help to clarify how copyrights ans third parties and managed in the OTB project.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=Fall_2014_Committee_Report_for_OSGeo_Journal&diff=80589Fall 2014 Committee Report for OSGeo Journal2014-11-04T13:12:38Z<p>Wiki-Grizonnetm: /* OTB Project */</p>
<hr />
<div>==OTB Project==<br />
* Project has moved through the first four (4) phases of the incubation process and is preparing for the code provenance review. Graduation is expected in the Spring of 2015.<br />
<br />
** Web site redesign: We are currently revamping the web site to get an up-to-date look and feel, and have a better integration between site and other web components. As soon as we have a draft new version to show, we will provide you with a link. We've already integrated the OSGEO logo on the website and indicate that OTB is in incubation.<br />
<br />
** Code provenance review: there is a related discussion presently on the debian GIS mailing list related to the integration of OTB and also discussion about integrated third parties in OTB.<br />
<br />
<br />
[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/022918.html]<br />
[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023010.html]<br />
[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023011.html]<br />
[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023012.html]<br />
[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023675.html]<br />
[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023773.html]<br />
<br />
Don't think that there will have major issue with code provenance with OTB but I think that discussion with Debian guys will help to clarify how copyrights ans third parties and managed in the OTB project.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=Fall_2014_Committee_Report_for_OSGeo_Journal&diff=80588Fall 2014 Committee Report for OSGeo Journal2014-11-04T13:11:55Z<p>Wiki-Grizonnetm: /* OTB Project */</p>
<hr />
<div>==OTB Project==<br />
* Project has moved through the first four (4) phases of the incubation process and is preparing for the code provenance review. Graduation is expected in the Spring of 2015.<br />
<br />
** Web site redesign: We are currently revamping the web site to get an up-to-date look and feel, and have a better integration between site and other web components. As soon as we have a draft new version to show, we will provide you with a link. We've already integrated the OSGEO logo on the website and indicate that OTB is in incubation.<br />
<br />
** Code provenance review: there is a related discussion presently on the debian GIS mailing list related to the integration of OTB and also discussion about integrated third parties in OTB.<br />
<br />
<br />
h[ttp://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/022918.html<br />
]<br />
[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023010.html]<br />
<br />
[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023011.html]<br />
<br />
[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023012.html]<br />
<br />
[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023675.html]<br />
<br />
[http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-October/023773.html<br />
]<br />
<br />
Don't think that there will have major issue with code provenance with OTB but I think that discussion with Debian guys will help to clarify how copyrights ans third parties and managed in the OTB project.</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=Edu_current_initiatives&diff=78511Edu current initiatives2014-07-18T10:15:14Z<p>Wiki-Grizonnetm: /* Current members of the ICA-OSGeo Network */</p>
<hr />
<div>== 2013-2014 OSGeo Education and Curriculum Current Initiatives ==<br />
<br />
'''The official website is online at ''http://www.geoforall.org''''' - locations: [http://www.geoforall.org/locations/ ICA-OSGeo Map]<br />
<br />
=== 1) Continue to build up our educational material federated content databases ===<br />
<br />
* [http://www.osgeo.org/educational_content OSGeo edu's educational content metadatabase] -- a place for metadata and links to external material we are posting on our own websites<br />
* [http://elogeo.nottingham.ac.uk/xmlui/ University of Nottingham's educational content database] (ELOGeo) -- a place for us to store education content (the source code) to share<br />
* [[Webinar Series ]]<br />
<br />
===2) Continue to expand the ICA-OSGeo Network ===<br />
<br />
This effort is led by Suchith Anand at the University of Nottingham, UK.<br />
<br />
In September 2011, the Open Source Geospatial Foundation (OSGeo) and the International Cartographic Association (ICA) signed a Memorandum of Understanding with the aim of developing on a global basis collaboration opportunities for academia, industry and government organizations in open source GIS software and data. The MoU aims to provide expertise and support for the establishment of Open Source Geospatial Laboratories and Research Centres across the world for supporting development of open-source geospatial software technologies, training and expertise. It also aims to provide support for building-up and supporting development of open source GIS teaching and training materials, joint organization of open source GIS events, workshops through the ICA network for wider participation globally etc. Details at [[MOU_ICA]].<br />
<br />
== Current members of the ICA-OSGeo Network ==<br />
<br />
<!--<br />
[http://gis.ncsu.edu/osgeorel/index.php#labsmap Updated Leaflet Map of the ICA-OSGeo Network Nodes by Vasek and Anna]<br />
[http://lucadelu.org/ica-osgeo-lab/ Leaflet Map of the ICA-OSGeo Network Nodes by Luca Delucchi, June 2013],<br />
and the related <br />
[http://lucadelu.org/ica-osgeo-lab/ica-osgeo-lab.tar.gz application] <br />
[http://conlibre.org/osgeolabs/ Visit the ICA-OSGeo Network website]<br />
[https://mapsengine.google.com/map/embed?mid=z4Nmc5_-QPhA.kBqA02Uh9xoc Google Map of the ICA-OSGeo Network Nodes],<br />
[https://maps.google.de/maps/ms?msid=217919488281947849251.0004da7def3b647f010c4&msa=0&ll=-27.332735,-43.330078&spn=18.234488,25.158691 The first Google Map of the ICA-OSGeo Network Nodes](thanks to Franz-Josef) <br />
--><br />
<br />
Feel free to join the mailing list http://lists.osgeo.org/cgi-bin/mailman/listinfo/ica-osgeo-labs to follow the discussions among the participants of this initiative.<br />
<br />
The current members of the ICA-OSGeo Network are (please add '''WGS84 decimal coordinates longitude,latitude''', if you don't add the coordinate following this simple rules your institution will not show on the [http://www.geoforall.org/locations/ ICA-OSGeo Map]) : <br />
<br />
{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;" <br />
!<br />
! Laboratory name and institution<br />
! City<br />
! Country<br />
! Continent<br />
! Coordinates (longitude, latitude)<br />
! Application recieved / Announced<br />
! Notes (projects, collaborations, etc)<br />
! Contact names<br />
! Contact emails<br />
|-<br />
| 1.<br />
| [http://www.nottingham.ac.uk/ngi/research/geospatial-science/geospatial-science.aspx University of Nottingham]<br />
| Nottingham<br />
| UK<br />
| Europe<br />
| -1.250296, 52.831497<br />
|<br />
|<br />
| Jeremy Morley<br />
| Jeremy dot Morley at nottingham.ac.uk<br />
|-<br />
| 2.<br />
| [http://www.sigte.udg.edu/ University of Girona]<br />
| Girona<br />
| Spain<br />
| Europe<br />
| 2.837305, 41.967426<br />
| 2012-09-10<br />
|<br />
| Lluís Vicens <br />
| lluis at sigte.udg.edu<br />
|-<br />
| 3.<br />
| [http://www.osgl.soton.ac.uk/ University of Southampton]<br />
| Southampton<br />
| UK<br />
| Europe<br />
| -1.396873, 50.936974<br />
| 2013-04-30<br />
| <br />
| Jason Sadler<br />
| osgl at geodata.soton.ac.uk<br />
|-<br />
| 4.<br />
| [http://geo.fsv.cvut.cz/gwiki/osgeorel Czech Technical University in Prague]<br />
| Prague<br />
| Czech Republic<br />
| Europe<br />
| 14.390363, 50.10183<br />
| 2012-11-23<br />
| Geospatial analysis, modeling and visualization, remote sensing, [http://grass.osgeo.org GRASS GIS] and [http://www.qgis.org QGIS] development<br />
| Martin Landa<br />
| martin.landa at fsv.cvut.cz<br />
|-<br />
| 5.<br />
| [http://research.ncl.ac.uk/osgeolab/ Newcastle University]<br />
| Newcastle<br />
| UK<br />
| Europe<br />
| -1.611536, 54.980656<br />
| 2013-01-17<br />
|<br />
| Philip James<br />
| philip.james at ncl.ac.uk (please use subject: OSGeoLab)<br />
|-<br />
| 6.<br />
| [http://geomatica.como.polimi.it/ Politecnico di Milano - Polo Territoriale di Como]<br />
| Como<br />
| Italy<br />
| Europe<br />
| 9.095939, 45.803516<br />
| 2013-02-25<br />
|<br />
| Maria Brovelli<br />
| geowb at geomatica.como.polimi.it<br />
|-<br />
| 7.<br />
| [http://www2.warwick.ac.uk/fac/sci/lifesci/research/facilities/geolab/ University of Warwick]<br />
| Warwick<br />
| UK<br />
| Europe<br />
| -1.56273, 52.380531<br />
| 2013-03-23<br />
|<br />
| Nataliya Tkachenko<br />
| geolab at warwick.ac.uk<br />
|-<br />
| 8.<br />
| [http://www.gridw.pl UNEP/GRID-Warsaw Centre]<br />
| Warsaw<br />
| Poland<br />
| Europe<br />
| 21.039473, 52.198849<br />
| 2013-03-18<br />
|<br />
| Ela Woloszynska-Wisniewska<br />
| ela at gridw.pl<br />
|-<br />
| 9.<br />
| [http://www.supsi.ch/ist_en/settori-attivita/geomatica.html University of Applied Sciences and Arts of Southern Switzerland] (SUPSI)<br />
| Lugano<br />
| Switzerland<br />
| Europe<br />
| 8.961098, 46.028362<br />
| 2013-09-03<br />
| Institute of Earth Sciences<br />
| Massimiliano Cannata <br />
| geomatica at supsi.ch<br />
|-<br />
| 10.<br />
| [http://karlinapp.ethz.ch/osgl/ ETH Zurich]<br />
| Zurich<br />
| Switzerland<br />
| Europe<br />
| 8.5481, 47.3764<br />
| 2013-09-20<br />
| [http://www.ikg.ethz.ch/about/index_EN Institute of Cartography and Geoinformation, ETH Zurich]<br />
| Ionu? Iosifescu<br />
| iosifescu at ethz.ch<br />
|-<br />
| 11.<br />
| University of Molise<br />
| Molise<br />
| Italy<br />
| Europe<br />
| 14.493651, 41.630815<br />
|<br />
| in process of being established<br />
| Rosella Nocera<br />
|<br />
|-<br />
| 12.<br />
| [http://www.igik.edu.pl/en Institute of Geodesy and Cartography] (IGiK)<br />
| Warsaw<br />
| Poland<br />
| Europe<br />
| 52.178478, 21.013407<br />
|<br />
| in process of being established<br />
| Agata Ciołkosz-Styk<br />
|<br />
|-<br />
| 13.<br />
| [http://opengis.unibuc.ro/ Faculty of Geography, University of Bucharest]<br />
| Bucharest<br />
| Romania<br />
| Europe<br />
| 26.103889, 44.432500<br />
|<br />
| new website under development<br />
| Andreea Marin<br />
| andreea dot marin09 at yahoo dot com<br />
|-<br />
| 14.<br />
| [http://www.geo.info.hu/english/index.php Faculty of Geoinformatics,University of West Hungary]<br />
| Székesfehérvár<br />
| Hungary<br />
| Europe<br />
| 18.418833, 47.188778<br />
|<br />
| in process of being established<br />
| Andrea Podör <br />
|<br />
|-<br />
| 15.<br />
| [http://www.hft-stuttgart.de/Studienbereiche/Vermessung/Master-Photogrammetry-Geoinformatics/Labs/ICA-OSGeo-Labor/index.html/en Stuttgart University of Applied Sciences]<br />
| Stuttgart<br />
| Germany<br />
| Europe<br />
| 9.17370, 48.77996<br />
| 2013-10-14<br />
| <br />
| Franz-Josef Behr<br />
| franz-josef.behr at hft-stuttgart.de<br />
|-<br />
| 16.<br />
| [http://www.geomatica.ufpr.br/index.html Federal University of Paraná]<br />
| Paraná<br />
| Brazil<br />
| South America<br />
| -49.26141, -25.427074<br />
| 2012-05-23<br />
|<br />
| Silvana Camboim<br />
|<br />
|-<br />
| 17.<br />
| [http://www.unesp.br/ São Paulo State University] (UNESP)<br />
| São Paulo<br />
| Brazil<br />
| South America<br />
| -46.654129, -23.576574<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| 18.<br />
| National Amazonian University of Madre de Dios (UNAMAD)<br />
| Puerto Maldonado<br />
| Peru<br />
| South America<br />
| -73.245789, -3.745845<br />
| 2013-02-01<br />
| in process of being established<br />
| Andrea Birgit Chavez <br />
|<br />
|-<br />
| 19.<br />
| [http://ltaat.fcien.edu.uy Universidad de la República]<br />
| Montevideo<br />
| Uruguay<br />
| South America<br />
| -56.176441, -34.902405<br />
| 2013-03-01<br />
| new website under development<br />
| Virginia Fernandez<br />
| vfernandez at presidencia.gub.uy<br />
|-<br />
| 20.<br />
| University of Campinas<br />
| Campinas<br />
| Brazil<br />
| South America<br />
| -47.063239, -22.907105<br />
|<br />
| in process of being established<br />
|<br />
|<br />
|-<br />
| 21.<br />
| Federal University of Alagoas<br />
| Maceió<br />
| Brazil<br />
| South America<br />
| -35.735098, -9.666251<br />
|<br />
| http://www.nmarisco.simplesite.com.br/<br />
|<br />
|<br />
|-<br />
| 22.<br />
| [http://geospatial.ncsu.edu/osgeorel/ North Carolina State University OSGeoREL]<br />
| Raleigh, NC<br />
| USA<br />
| North America<br />
| -78.6764, 35.7818<br />
| 2012-10-18<br />
|Geospatial analysis, modeling and visualization, [http://grass.osgeo.org GRASS GIS] development<br />
| Helena Mitasova<br />
| hmitaso at ncsu.edu<br />
|-<br />
| 23.<br />
| [http://www.umass.edu/opensource University of Massachusetts Amherst]<br />
| Amherst<br />
| USA<br />
| North America<br />
| -72.524696, 42.393578<br />
| 2012-10-18<br />
| <br />
| Charlie Schweik<br />
| cschweik at pubpol dot umass dot edu<br />
|-<br />
| 24.<br />
| [https://sites.google.com/site/foss4gku/ University of Kansas]<br />
| Lawrence, KS<br />
| USA<br />
| North America<br />
| -95.251311, 38.958578<br />
| 2013-08-23<br />
| <br />
| Xingong Li<br />
| lixi at ku.edu<br />
|-<br />
| 25.<br />
| [https://geospatial.ucdavis.edu/resources/open-source University of California, Davis]<br />
| Davis<br />
| USA<br />
| North America<br />
| -121.766945, 38.548801<br />
| 2013-02-04<br />
| [http://live.osgeo.org OSGeo-Live]<br />
| Alex Mandel<br />
| aimandel at ucdavis.edu<br />
|-<br />
| 26.<br />
| [http://www.cozcyt.gob.mx/labsol/ Laboratorio de Software Libre]<br />
| Zacatecas<br />
| Mexico<br />
| North America<br />
| -102.5791, 22.7608<br />
| 2013-04-05<br />
| in process of being established<br />
| Manual Haro<br />
| manuel.haro at zacatecas.gob.mx<br />
|-<br />
| 27.<br />
| Kent State University<br />
| Kent, Ohio<br />
| USA<br />
| North America<br />
| -81.357886,41.153667<br />
| 2013-08-30<br />
|<br />
| Xinyue Ye<br />
| xye5 at kent.edu<br />
|-<br />
| 28.<br />
| [https://gis.uncc.edu/osgl Center for Applied GIScience, University of North Carolina, Charlotte ]<br />
| Charlotte, NC<br />
| USA<br />
| North America<br />
| -80.730000, 35.306944<br />
| 2013-09-05<br />
| <br />
| Wenwu Tang<br />
| WenwuTang at uncc.edu<br />
|-<br />
| 29.<br />
| [http://www.nottingham.edu.my/Geography University of Nottingham, Malaysia campus]<br />
| Semenyih<br />
| Malaysia<br />
| Asia<br />
| 101.721298, 3.172932<br />
| 2012-01-09<br />
| [http://www.nottingham.edu.my/Geography/Research/GeospatialScience/OSGEO-lab.aspx OSGEO research lab]<br />
| Tuong Thuy Vu<br />
| Tuongthuy.Vu at nottingham.edu.my<br />
|-<br />
| 30.<br />
| [http://www.utm.my/ Universiti Teknologi Malaysia] (UTM)<br />
| Johor Bahru<br />
| Malaysia<br />
| Asia<br />
| 101.874222, 2.943748<br />
|<br />
| in process of being established<br />
|<br />
|<br />
|-<br />
| 31.<br />
| National College of Public Administration and Governance(NCPAG), University of the Philippines<br />
| Manila<br />
| Philippines<br />
| Asia<br />
| 121.059875, 14.656005<br />
|<br />
| in process of being established<br />
| Noriel Christopher Tiglao<br />
|<br />
|-<br />
| 32.<br />
| Environmental Science for Social Change (ESSC)<br />
| Quezon City<br />
| Philippines<br />
| Asia<br />
| 121.062241, 14.64372<br />
|<br />
| in process of being established<br />
| Maning Sambale <br />
|<br />
|-<br />
| 33.<br />
| [http://lsi.iiit.ac.in/labinfo/ Lab for Spatial Informatics], IIIT Hyderabad<br />
| Hyderabad<br />
| India<br />
| Asia<br />
| 78.3503, 17.4454<br />
| 2011-08-22<br />
| <br />
| Dr K S Rajan<br />
|<br />
|-<br />
| 34.<br />
| [http://grel.ist.edu.pk/ Geospatial Research and Education Lab](GREL), Institute of Space Technology (IST)<br />
| Islamabad<br />
| Pakistan <br />
| Asia<br />
| 73.175045, 33.520060<br />
|<br />
| <br />
|Rizwan Bulbul<br />
|bulbul(dot)rizwan(at)gmail(dot)com <br />
|-<br />
| 35.<br />
| [http://www.up.ac.za/cgis University of Pretoria]<br />
| Pretoria<br />
| South Africa<br />
| Africa<br />
| 28.22847, -25.75429<br />
| 2012-05-15<br />
|<br />
| Serena Coetzee<br />
| serena dot coetzee at up dot ac dot za<br />
|-<br />
| 36.<br />
| [http://www.rcmrd.org/ Regional Centre for Mapping of Resources for Development] (RCMRD)<br />
| Nairobi <br />
| Kenya<br />
| Africa<br />
| 36.858574, -1.249038<br />
|<br />
| in process of being established<br />
| Hussein Farah<br />
| farah at rcmrd.org<br />
|-<br />
| 37.<br />
| University of Ghana<br />
| Accra<br />
| Ghana<br />
| Africa<br />
| -0.191617, 5.650366<br />
|<br />
| in process of being established<br />
| Foster Mensah<br />
| <br />
|-<br />
| 38.<br />
| The University of Melbourne<br />
| Melbourne<br />
| Australia<br />
| Australia<br />
| 144.962006, -37.797932<br />
| 2013-07-22<br />
|<br />
| Chris Pettit<br />
|<br />
|-<br />
| 39.<br />
| [http://cbi.tamucc.edu/Geospatial-Computing/ Texas A&M University - Corpus Christi]<br />
| Corpus Christi<br />
| USA<br />
| North America<br />
| -97.328799, 27.714506<br />
| 2013-09-09<br />
| in process of being established/website under construction<br />
| Rick Smith<br />
| Richard.Smith at tamucc.edu<br />
|- <br />
| 40.<br />
| [http://www.geomaticsindia-cept.org/ CEPT University]<br />
| Ahmedabad<br />
| India<br />
| Asia<br />
| 72.566004,23.039568<br />
| 2012-07-18<br />
| in process of being established<br />
| Prof. Anjana Vyas & Ms. Darshana Rawal<br />
| anjanavyas at cept.ac.in rawalnet at cept.ac.in<br />
|- <br />
| 41.<br />
| National University of San Juan<br />
| San Juan<br />
| Argentina<br />
| South America<br />
| -68.521408, -31.527273<br />
| 2012-06-15<br />
| in process of being established<br />
| Agustin Arroqui<br />
| aarroqui at unsj.edu.ar<br />
|- <br />
| 42.<br />
| [http://geodacenter.asu.edu GeoDa Center for Geospatial Analysis and Computation, Arizona State University]<br />
| Tempe, AZ<br />
| USA<br />
| North America<br />
| -111.940005, 33.425510<br />
| 2013-09-27<br />
| Spatial econometrics, geocomputation, spatial optimization - [https://geodacenter.asu.edu/software/downloads GeoDa], [http://pysal.org PySAL], [https://geodacenter.asu.edu/software/downloads/geodaspace GeoDaSpace]<br />
| [http://en.wikipedia.org/wiki/Luc_Anselin Luc Anselin]<br />
| geodacenter at asu.edu<br />
|- <br />
| 43.<br />
| National Technical University of Athens<br />
| Athens<br />
| Greece<br />
| Europe<br />
| 23.729310, 37.983716<br />
| 2013-09-26<br />
| in process of being established<br />
|<br />
|<br />
|- <br />
| 44.<br />
| IGN- France<br />
| Paris<br />
| France<br />
| Europe<br />
| 2.352222, 48.856614<br />
| 2013-09-26<br />
| in process of being established<br />
| Benedicte Bucher<br />
|<br />
|- <br />
| 45.<br />
| Universitat Oberta de Catalunya<br />
| Barcelona<br />
| Spain<br />
| Europe<br />
| 2.173403, 41.385064<br />
| 2013-09-27<br />
| in process of being established<br />
| Dr. Antoni Pérez Navarro<br />
| aperezn at uoc.edu<br />
|-<br />
| 46.<br />
| [http://www.isric.org ISRIC - World Soil Information foundation]<br />
| Wageningen<br />
| The Netherlands<br />
| Europe<br />
| 5.665662,51.9875<br />
|2013-10-02<br />
|website in construction<br />
| Jorge de Jesus<br />
| jorge.mendesdejesus at wur.nl<br />
|-<br />
| 47.<br />
| Universidade da Coruña <br />
| A Coruña (España)<br />
| Spain<br />
| Europe<br />
| -8.411540, 43.362344<br />
| 2013-10-15<br />
| in process of being established<br />
| Alberto Varela García<br />
|<br />
|-<br />
| 48.<br />
| Universiti Sains Malaysia<br />
| Penang <br />
| Malaysia<br />
| Asia<br />
| 100.484623, 5.263234<br />
|2013-10-16<br />
|in process of being established<br />
| Ruslan Rainis<br />
|<br />
|-<br />
| 49.<br />
| Kathmandu University<br />
| Dhulikhel <br />
| Nepal<br />
| Asia<br />
| 85.550000, 27.616667<br />
|2012-12-24<br />
|https://sites.google.com/a/ku.edu.np/opensourcegeospatial/<br />
| Shashish Maharjan<br />
|<br />
|-<br />
| 50<br />
| [http://gis.cri.fmach.it/ GIS and Remote Sensing Unit, Fondazione Edmund Mach ]<br />
| San Michele all'Adige (Trento)<br />
| Italy <br />
| Europe<br />
| 11.133042,46.187865<br />
|2013-10-16<br />
|Geospatial analysis, modeling and remote sensing, [http://grass.osgeo.org GRASS GIS] and [http://pymodis.fem-environment.eu/ pyMODIS] development<br />
| Luca Delucchi <br />
| luca.delucchi at fmach.it<br />
|-<br />
| 51.<br />
| [http://gis.research.southwales.ac.uk/ University of South Wales ]<br />
| Cardiff <br />
| United Kingdom<br />
| Europe<br />
| -3.179090,51.481581<br />
|2013-10-31<br />
|<br />
| Dr Mark Ware<br />
| mark.ware at southwales.ac.uk<br />
|-<br />
| 52.<br />
| [http://gisgeek.pdx.edu/wordpress/open-source-gis/ Portland State University]<br />
| Portland, Oregon <br />
| USA<br />
| North America<br />
| -122.676207,45.523452<br />
| 2013-10-22<br />
| Warming up<br />
| David Percy <br />
| percy at pdx.edu<br />
|-<br />
| 53.<br />
| [http://www.icpac.net/ IGAD Climate Prediction and Applications Center]<br />
| Nairobi<br />
| Kenya<br />
| Africa<br />
| 36.821946,-1.292066<br />
| 2013-10-29<br />
| In process of being established<br />
| Muyambi Fortunate <br />
| fbenda at icpac.net<br />
|-<br />
|-<br />
| 54.<br />
| [http://www.labocart.ufc.br/ Federal University of Ceará ]<br />
| Ceará<br />
| Brazil<br />
| South America<br />
| -38.543395,-3.718394<br />
| 2013-10-29<br />
| In process of being established<br />
| Prof. Dr. Adryane Gorayeb <br />
| adryanegorayeb at yahoo dot com dot br<br />
|-<br />
| 55.<br />
| [http://geospecial.wordpress.com/ University of Gloucestershire ]<br />
| Gloucester and Cheltenham<br />
| United Kingdom<br />
| Europe<br />
| -2.223409, 51.872215<br />
| 2013-11-06<br />
| In process of being established<br />
| Dr Robert Berry<br />
| rberry at glos.ac.uk<br />
|-<br />
| 56.<br />
| [http://mrt.ac.lk/foa/ University of Moratuwa ]<br />
| Moratuwa<br />
| Sri Lanka<br />
| Asia<br />
| 79.9008, 6.7964<br />
| 2013-11-11<br />
| [http://www.mrt.ac.lk/tcp/osgeosl.html OSGeoSL ]<br />
| Aruna Wickramasinghe<br />
| toaruna at gmail.com<br />
|-<br />
| 57.<br />
| [http://www.fudan.edu.cn/ Fudan University]<br />
| Shanghai<br />
| China<br />
| Asia<br />
| 121.452, 31.198<br />
| 2013-11-14<br />
| [http://lab.osstat.org/ Open Source STATistics]<br />
| Zhijie Zhang<br />
| epistat at gmail.com<br />
|-<br />
| 58.<br />
| Haskell Indian Nations University<br />
| Lawrence, Kansas<br />
| USA<br />
| North America<br />
| -95.230691, 38.938859<br />
| 2013-11-22<br />
| [https://sites.google.com/site/dtmcdermott/home/haskell-cartography-class/ Haskell Indian Nations University]<br />
| Dave McDermott<br />
| dmcdermott at haskell.edu<br />
|-<br />
| 59.<br />
| [http://www.geof.unizg.hr/mod/book/view.php?id=1165&chapterid=110&lang=en University of Zagreb, Faculty of Geodesy]<br />
| Zagreb<br />
| Croatia<br />
| Europe<br />
| 15.963888, 45.808500<br />
| 2013-11-25<br />
| <br />
| Dražen Tutic<br />
| dtutic at geof.hr<br />
|-<br />
| 60.<br />
| [http://www.geo.gob.bo/ GeoBolivia-Vice-presidency of the State ]<br />
| La Paz<br />
| Bolivia<br />
| South America<br />
| -68.1547, -16.4949<br />
| 2013-11-24<br />
| In process of being established <br />
| Raul Fernando Molina Rodriguez<br />
| rafemoro at gmail.com rmolina@geo.gob.bo<br />
|-<br />
| 61.<br />
| [http://www2.unb.ca/~estef/geo4all.html Geodesy and Geomatics Engineering], University of New Brunswick<br />
| Fredericton, NB <br />
| Canada<br />
| North America<br />
| -66.641474, 45.950252<br />
| 2013-12-10<br />
| Active<br />
| Emmanuel Stefanakis<br />
| emmanuel.stefanakis at gmail.com <br />
|-<br />
| 62.<br />
| [http://geo.sab.ac.lk/ Faculty of Geomatics, Sabaragamuwa University of Sri Lanka]<br />
| Belihuloya, Sabaragamuwa <br />
| Sri Lanka<br />
| Asia<br />
| 80.78995, 6.7102<br />
| 2013-12-12<br />
| In process of being established<br />
| Thilantha Dammalage<br />
| thilantha9 at gmail.com <br />
|-<br />
| 63.<br />
| [http://www.sliit.lk/index.php/sliit/departments/department-of-information-technology Dpt of IT, Faculty of Computing, Sri Lanka Institute of Information Technology]<br />
| Malabe<br />
| Sri Lanka<br />
| Asia<br />
| 79.973166667, 6.914866667<br />
| 2013-12-13<br />
| [http://osgeolab.sliit.lk/ OSGeoSLIIT]<br />
| Nimalika Fernando<br />
| nimalikaf at gmail.com <br />
|-<br />
| 64.<br />
| [http://www.unige.ch/environnement University of Geneva - Institute for Environmental Sciences]<br />
| Geneva<br />
| Switzerland<br />
| Europe<br />
| 6.1487, 46.2253<br />
| 2013-12-19<br />
| In process of being established<br />
| Gregory Giuliani<br />
| gregory.giuliani at unige.ch<br />
|-<br />
| 65.<br />
| [http://www.ifs.hsr.ch/Geometa-Lab.12520.0.html?&L=4 Geometa Lab at HSR - University of Applied Sciences Rapperswil]<br />
| Rapperswil<br />
| Switzerland<br />
| Europe<br />
| 8.81690, 47.22341 <br />
| 2014-01-26<br />
| (published 2014-02-05)<br />
| Prof. Stefan Keller<br />
| sfkeller at hsr.ch (and/or at gmail.ch)<br />
|-<br />
| 66.<br />
| National University of "Kyiv-Mohyla Academy", Ecology Faculty<br />
| Kyiv <br />
| Ukraine<br />
| Europe<br />
| 50.456936, 30.515647 <br />
| 2014-02-16<br />
| In proess of being established<br />
| Tetyana Kuchma<br />
| tanyakuchma at yahoo.com <br />
|-<br />
| 67.<br />
| Centre for Research and Technology Hellas - Hellenic Institute of Transport<br />
| Thessaloniki<br />
| Greece<br />
| Europe<br />
| 40.567811, 22.996707<br />
| 2014-02-17<br />
| In process of being established<br />
| Dr. Evangelos Mitsakis<br />
| emit at certh.gr <br />
|-<br />
| 68.<br />
| Centre for Spatial Information Science(CSIS), University of Tokyo<br />
| Kashiwa-shi, Chiba<br />
| Japan<br />
| Asia<br />
| 139.938952, 35.902681<br />
| 2014-02-18<br />
| In process of being established<br />
| Taichi FURUHASHI<br />
| taichi at csis.u-tokyo.ac.jp <br />
|-<br />
| 69.<br />
|[http://foss4geo.org FOSS4Geo Academy @ Del Mar College National Open Geospatial Technology Consortium]<br />
| Corpus Christi, Republic of Texas<br />
| USA<br />
| North America<br />
| -97.407096, 27.764053<br />
| 2014-02-18<br />
| Active<br />
| Dr. Phillip Davis<br />
| pdavis at delmar.edu<br />
|-<br />
| 70.<br />
| Osaka City University(OCU)<br />
| Sumiyoshi-ku, Osaka<br />
| Japan<br />
| Asia<br />
| 135.507556, 34.593067<br />
| 2014-02-23<br />
| In process of being established<br />
| Venkatesh RAGHAVAN<br />
| venka.osgeo at gmail.com<br />
|-<br />
| 71.<br />
| [http://www.dicca.unige.it/geomatica/ Università di Genova - Laboratorio di Geomatica]<br />
| Genova<br />
| Italy<br />
| Europe<br />
| 8.962795, 44.400133<br />
| 2014-03-21<br />
|[http://www.gter.it Gter Innovation in Geomatics, Gnss and Gis (spin-off company)]<br />
| Tiziano Cosso - Bianca Federici - Roberto Marzocchi - Domenico Sguerso <br />
| bianca.federici at unige.it<br />
|-<br />
| 72.<br />
| [http://www.eiic.ulpgc.es/ Universidad de Las Palmas de Gran Canaria - Escuela de Ingenierías Industriales y Civiles - Grado en Ingenieria Geomática y Topografía]<br />
| Las Palmas de Gran Canaria<br />
| Spain<br />
| Europe<br />
| -15.456207, 28.069303<br />
| 2014-03-23<br />
| <br />
|Fernando Toscano Benítez<br />
| sub_dgn at eiic.ulpgc.es<br />
|-<br />
| 73.<br />
| [http://carsilab.org] Center for Advanced Research on Spatial Information, Hunter College - CUNY<br />
| New York<br />
| US<br />
| North America<br />
| <br />
| 2014-04-04<br />
|<br />
| Carson Farmer<br />
| carson.farmer at hunter.cuny.edu<br />
|-<br />
| 74.<br />
| [http://www.digital-earth.edu.gr/index.php/en/] Hellenic digital earth Centre of Excellence, Aristotle University of Thessaloniki - AUTH<br />
| Thessaloniki<br />
| Greece<br />
| Europe<br />
| 40.627516, 22.961498<br />
| 2014-04-05<br />
|<br />
| Nikos Lambrinos<br />
| labrinos at eled.auth.gr<br />
|-<br />
| 75.<br />
| [http://www.zgis.at/ Interfaculty Department of Geoinformatics - Z_GIS, University of Salzburg]<br />
| Salzburg<br />
| Austria<br />
| Europe<br />
| 47.823711, 13.039586<br />
| 2014-04-14<br />
| [http://www.unigis.net The UNIGIS International Association is the distance education initiative offering masters and diploma programmes in Geographical Information Science and Systems]<br />
| Hermann Klug<br />
| hermann.klug at sbg.ac.at<br />
|-<br />
| 76.<br />
|[http://gisciencegroup.ucalgary.ca The GI Science Group @ the Department of Geomatics Engineering, University of Calgary]<br />
| Calgary<br />
| Canada<br />
| North America<br />
| -114.132457, 51.079735<br />
| 2014-04-22<br />
| in the process of being established<br />
| Andrew Hunter<br />
| ahunter at ucalgary.ca<br />
|-<br />
| 77.<br />
| Ben Gurion University of the Negev (BGU)<br />
| Sede Boqer and Beer Sheva<br />
| Israel<br />
| Europe<br />
| 34.78346, 30.85332<br />
| 2014-04-22<br />
| TBA<br />
| Yaakov GARB<br />
| ygarb at bgu.ac.il<br />
|-<br />
| 78.<br />
| [http://www.grf.bg.ac.rs/fakultet/ka/e?kid=5 University of Belgrade, Faculty of Civil Engineering, Department of geodesy and geoinformatics]<br />
| Belgrade<br />
| Serbia<br />
| Europe<br />
| 20.476321, 44.805499<br />
| 2014-05-03<br />
| Laboratory website is under construction<br />
| Milan Kilibarda<br />
| kili at grf.bg.ac.rs<br />
|-<br />
| 79.<br />
| Open Geospatial Laboratory of Northeast Institute of Geography and Agroecology, CAS<br />
| Changchun, Jilin<br />
| China<br />
| Asia<br />
| 125.400779, 43.99896<br />
| 2014-05-26<br />
| http://lab.osgeo.cn/en<br />
| [[User:BuKun|Bu Kun]]<br />
| See Profile page<br />
|-<br />
| 80.<br />
| [http://www.baycollege.edu/gis Bay College ] <br />
| Escanaba, Michigan<br />
| USA<br />
| North America<br />
| -87.163050, 45.773875<br />
| 2014-06-07<br />
| GIS degree in process of being established. <br />
| Karl Linderoth<br />
| linderok at baycollege.edu<br />
|-<br />
| 81.<br />
| [http://www.univ.kiev.ua/ Taras Shevchenko National University of Kyiv, Faculty of Geography, Department of Physical Geography and Geoecology] <br />
| Kyiv<br />
| Ukraine<br />
| Europe<br />
| 30.4752782, 50.3825971<br />
| 2014-07-11<br />
| Geospatial analysis and modeling for landscape-ecological studies, and spatial planning; QGIS, SAGA GIS, and PostGIS; QGIS Ukraine User Group; new website is under development <br />
| [[User:Darsvid|Daria Svidzinska]]<br />
| d.svidzinska at gmail.com<br />
|-<br />
| 82.<br />
| University of Colorado Denver, Department of Geography and Environmental Sciences<br />
| Denver, CO<br />
| USA<br />
| North America<br />
| <br />
| 2014-07-17<br />
| in the process of being established<br />
| Rafael Moreno<br />
| Rafael.Moreno at ucdenver.edu<br />
|-<br />
| 83.<br />
| French Space Agency CNES<br />
| Toulouse<br />
| France<br />
| Europe<br />
| 1.481608, 43.561984<br />
| 2014-07-17<br />
| in the process of being established<br />
| [[User:Grizonnetm| Manuel Grizonnet]]<br />
| manuel.grizonnet at cnes.fr<br />
|}<br />
<br />
== Interested in adding your own node into the ICA-OSGeo Labs network? ==<br />
<br />
<br />
As the lab network is expanding fast, we have also setup nodal contacts for each regions:<br />
<br />
# Anne Ghisla - Asia & Australia <br />
# Helena Mitasova - North America<br />
# Charlie Schweik - South America<br />
# Suchith Anand - Europe & Africa<br />
<br />
Email Suchith.Anand at nottingham.ac.uk and cc Helena Mitasova [hmitaso at ncsu.edu], Charlie Schweik [cschweik at pubpol.umass.edu], Anne Ghisla [a.ghisla at gmail.com] to start the conversation and they will be happy to discuss details and guide you through the process.<br />
<br />
<br />
The '''key requirements''' for establishing a local OSGL are:<br />
<br />
(A) Both parties should work for the vision of the [[MOU_ICA|ICA-OSGeo MoU]] to develop collaboration opportunities for academia, industry and government organizations in open source GIS software and data in the future.<br />
<br />
(B) Someone at your institution or organization should have a strong Geospatial knowledge and vision to lead this activity and build a team of people, locally.<br />
<br />
(C) There should be a website established for your Open Source Geospatial Laboratory listing current research, people, and training information. This web presence will allow the other nodes in the network and others to understand and promote your local efforts around research and teaching of open source geospatial technologies and approaches.<br />
<br />
From our end, we will promote the initiative widely through both OSGeo and ICA channels to help build up collaboration opportunities for the future. We will also do a joint press release to announce the initiative and start building collaborations. A primary collaborative initiative continues to be the creation and maintenance of shared open access educational resources (for example [http://elogeo.nottingham.ac.uk/ the ELOGeo platform]). We will also add the info of all labs in the Open Geospatial Lab network node site within OSGeo website so that all participating labs urls are added and linked.<br />
<br />
We especially welcome applications from universities, educational institutes, government organisations in developing countries to help develop capacity building in geospatial education by establishing Open Source Geo Labs.<br />
<br />
== Meetings ==<br />
; Next meeting:<br />
* ...<br />
<br />
; Past Meetings:<br />
* [[ICA OSGeo Lab Network 2013-09-05]] 18.00 UTC<br />
* [[ICA OSGeo Lab Network 2013-07-29]] 14.00 UTC<br />
* [[ICA OSGeo Lab Network 2013-05-02]] 14.00 UTC<br />
* [[ICA OSGeo Lab Network 2013-06-06]] 14.00 UTC<br />
<br />
== ISC OSGeo Lab Network Research and Teaching Areas ==<br />
<br />
[[ICA_OSGeo_Lab_Research_areas]]<br />
<br><br />
[[ICA_OSGeo_Lab_Teaching_areas]]<br />
<br />
[[Category: Education]]<br />
[[Category: ICA OSGeo Lab Network]]</div>Wiki-Grizonnetmhttps://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2014_Ideas&diff=76643Google Summer of Code 2014 Ideas2014-02-14T15:55:29Z<p>Wiki-Grizonnetm: /* OSGeo Foundation member projects */</p>
<hr />
<div>[[Image:GoogleSummer_2014logo.jpg|300px|link=http://code.google.com/soc/]] <font size="+3"> @ </font> [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]<br />
<br />
-----<br />
* Back to the main OSGeo [[Google Summer of Code 2014]] wiki page.<br />
<br />
* See also ideas from [[2007_SoC_Merged_Ideas|2007]], [[2008_SoC_Merged_Ideas|2008]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[Google Summer of Code 2010 Ideas|2010]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2012 Ideas|2012]], and [[Google Summer of Code 2013 Ideas|2013]].<br />
-----<br />
<br />
<br />
== OSGeo Google Summer of Code 2014 ==<br />
<br />
The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.<br />
<br />
These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders; show us what you've got.<br />
<br />
* '''Students: If you need more information on how to apply you can contact all the mentoring organisations via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])<br />
<br />
* There is a [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers Google SoC flyer] to look at and post in appropriate places and [http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2013.pdf an OSGeo flavoured one as well].<br />
<br />
* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.<br />
<br />
* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code 2014]] wiki page.<br />
<br />
== Important dates ==<br />
<br />
* [http://www.google-melange.com/gsoc/events/google/gsoc2014 '''The official timeline''']<br />
<br />
<!-- {{done}} --><br />
* February 24: Google announces accepted organizations.<br />
: If OSGeo is accepted as an organization for Google Summer of Code, '''start talking to us earlier rather than later.'''<br />
<!-- : Please start talking to the dev communities you are interested in ''now''. --><br />
* March 10: Student applications open.<br />
: The earlier you start the more probable it is that you will be accepted!<br />
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''<br />
* March 21: Student application deadline.<br />
* April 21: '''Accepted student proposals are announced and Community Bonding Period begins.'''<br />
* May 19: '''Coding begins!'''<br />
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')<br />
* June 23: Mid-term evaluation begins<br />
* August 11-18: '''Pencils down!'''<br />
* August 18-22: Final evaluations<br />
* August 22: Students begin submitting required code samples to Google<br />
* August 25: Final results announced<br />
<br />
== The ideas pages ==<br />
'''''[Check back often, it's a work in progress]'''''<br />
<br />
<br />
Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:<br />
<br />
=== OSGeo Foundation member projects ===<br />
<br />
* ''More coming soon: Get started talking to your favorite project's development team today!''<br />
<br />
<br />
[[Image:logo-grass.png|60px|right]]<br />
* [https://trac.osgeo.org/grass/wiki/GSoC/2014 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!<br />
<br />
<br />
[[Image:logo-qgis.png|60px|right]]<br />
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2014 '''QGIS''' SoC Ideas]: [http://www.qgis.org QGIS] is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.<br />
<br />
[[Image:logo-gdal.png|60px|right]]<br />
<br />
<br />
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.<br />
<br />
<!--<br />
* [http://trac.osgeo.org/osgeo4w/wiki/Reports '''OSGeo4W''']: - OSGeo4W is a binary distribution of a broad set of open source geospatial software for Win32 environments (Windows 7, XP, etc).<br />
[[Image:Logo-osgeo4w-mini.png|60px|right]]<br />
:* ''Idea'': We need to extend support to x64 based platforms to handle larger datasets and circumvent memory restrictions. This is a distribution and packaging project which will involve most/all of OSGeo member projects. (''ed. note: keep in mind that to fulfill GSoC requirements each project must have a majority coding component, so lots of scripting, testing, and Makefiles!'')--><br />
<br />
[[Image:logo-gvSIG.png|60px|right]]<br />
* [[GvSIG_GSoC_2014_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.org/web/projects/gvsig-desktop/description2/view?set_language=en Desktop], [http://www.gvsig.org/web/projects/gvsig-mobile/description-2/view?set_language=en PDAs], and [http://gvsigmini.org mobile phones]. The gvSIG project looks for students with Java skills that want to develop new ideas on any of these products.<br />
<br />
<br />
[[Image:logo-opticks.png|right]]<br />
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.<br />
<br />
<br />
[[Image:Osgeolive_60px.png|right]]<br />
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2014 '''OSGeo-Live''' Ideas]: [http://live.osgeo.org OSGeo-Live] packages over 50 of the best geospatial open source projects, preconfigured with data, quickstarts and project overviews. We have packaging and automated build projects. ([[#Which_project_do_I_choose.3F|See below]])<br />
<br />
<br />
[[Image:logo-postgis.png|60px|right]] <br />
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.<br />
<br />
<br />
[[Image:logo-ossim.png|65px|right]]<br />
* [https://trac.osgeo.org/ossim/wiki/GSoC_2014 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.<br />
<br />
<br />
* [http://wiki.orfeo-toolbox.org/index.php/GSOC_2014 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org OTB] ORFEO ToolBox (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.<br />
<br />
<!--<br />
[[Image:logo-geos.png|60px|right]]<br />
* [http://trac.osgeo.org/geos/wiki/GSoC '''GEOS''' Ideas]: GEOS (Geometry Engine - Open Source) is a C++ port of the JTS Topology Suite (JTS). It includes the OpenGIS Simple Features for SQL spatial predicate functions and spatial operators, as well as specific JTS enhanced topology functions.<br />
--> <!--<br />
[[Image:logo-geoserver-crop.png|50px|right]]<br />
* [http://live.osgeo.org/en/overview/geoserver_overview.html '''Geoserver'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desk top GIS programs. This means that you can store your spatial data in almost any format you prefer but that your users do not need to know anything about GIS data. At the simplest level all they need is a web browser to see your maps exactly as you want. GeoServer is the reference implementation of the Open Geospatial Consortium (OGC) Web Feature Service (WFS) and Web Coverage Service (WCS) standards, as well as a high performance certified compliant Web Map Service (WMS).<br />
:* ''Geoserver will accept one idea, according to the developers' availability. Please contact them to get more information.''<br />
--> <!--<br />
[[Image:ZOO-Project-mini.png|right]]<br />
* [http://www.zoo-project.org/trac/wiki/ZOO_SoC_Ideas '''ZOO-Project''' Ideas]: [http://www.zoo-project.org ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. We are seeking a developper to handle migration from SpiderMonky to Google v8 JavaScript runtime environment, upgrade the ZOO-API, build a demo package and develop new services dedicated to raster gesture.<br />
--><br />
<br />
<br />
<!--<br />
We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE], [http://mapserver.org/ MapServer], ...<br />
--><br />
<br />
=== Guest projects ===<br />
<br />
Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact Hamish, Anne and Dustan.<br />
<br />
[[Image:Logo-osm6.png|60px|right]]<br />
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2014/Project_Ideas '''OpenStreetMap''' Ideas]: [http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.<br />
:* ''This year OpenStreetMap students will again be hosted under OSGeo's GSoC umbrella. Talk to OSM, but apply with us. Begin your proposal description with "OSM: " so we know which way to direct it.''<br />
<br />
[[Image:Pgrouting-logo.png|60px|right]]<br />
<br />
<br />
* [https://github.com/pgrouting/pgrouting/wiki/GSOC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.<br />
<br />
<br />
[[Image:Pywps-logo.png|60px|right]]<br />
<br />
* [https://github.com/jachym/pywps-4/wiki/GSOC-2014-ideas '''PyWPS''' Ideas]: [http://pywps.wald.intevation.org PyWPS] is server implementation of OGC WPS standard on server side using Python programming language. Currently, [http://github.com/jachym/pywps-4/ new version of PyWPS] is being done, were we would like to implement several new attractive features. <br />
<br />
<br />
* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2014/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] [[Image:Logo-istSOS.png|100px|right]] (Istituto Scienze della Terra Sensor Observation Service) is an implementation of the Sensor Observation Service (SOS) standard from the Open Geospatial Consortium (OGC). The development of istSOS was started in 2009 in order to provide a simple implementation of the SOS standard for the management, provision and integration of hydro-meteorological data collected in Canton Ticino (Switzerland). istSOS is entirely written in Python.<br />
<br />
<br />
[[Image:logo-uDig.png|60px|right]]<br />
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2014 '''JGrasstools''' and '''uDig''' SoC Ideas]: User-friendly Desktop GIS ([http://udig.github.io/ uDig]) is a Java application written with the Eclipse RCP framework. The project has a community svn area to host student plug-ins, tutorials cover how to package up a custom application to show off your work.<br />
<br />
<br />
* [http://lsi.iiit.ac.in/redmine/projects/lsiviewer/wiki/GSoC_2014 '''LSIViewer''' Ideas]: [http://lsi.iiit.ac.in/redmine/projects/lsiviewer/wiki/Main/ LSIViewer] Libre Spatial Information Viewer (LSIViewer) is a web based geospatial data viewer which allows you to view your data, style it, export to SVG/PNG/JPEG formats and can be for used in reports and presentation. It uses Wt, a C++ web toolkit which comes with its own http server and has good support for embedded platforms. The initial version had support for only shapefiles but around 13 vector formats, OSM layer, 3D view has been experimental on the lab's internal repository.<br />
<br />
* '''FIXME''': move to a member project's idea page:<br />
: ''[http://sites.google.com/site/foss4gku/projects/gsoc-feature-based-map-algebra '''Feature-based Map Algebra''' SoC Ideas] Map algebra (or cartographic modeling) operations provide powerful tools for analyzing and manipulating geographic data in the raster data model both in commercial and open source GIS software. This project extends these operations to the vector data model and makes them available in PostGIS and QGIS. It will be implemented primarily using the Python programming language.''<br />
<br />
<!--<br />
[[Image:Logo-mapnik.png|100px|right]]<br />
* [https://github.com/mapnik/mapnik/wiki/GSOC-Ideas '''Mapnik''' Ideas]: [http://mapnik.org/ Mapnik] is a Free Toolkit for developing mapping applications. It\u2019s written in C++ and there are Python bindings to facilitate fast-paced agile development. It can comfortably be used for both desktop and web development, which was something I wanted from the beginning.<br />
--><br />
<br />
[[Image:Logo-cartaro.png|60px|right]]<br />
<br />
* [https://groups.drupal.org/node/407408 '''Cartaro''' Ideas]: [http://cartaro.org Cartaro] provides geospatial functionality and web services within the Drupal Content Management System (CMS). It is builds upon robust Open Source components: the PostGIS database, GeoServer and GeoWebCache web services, OpenLayers maps in the browser, all managed from within the powerful Drupal CMS.<br />
<br />
== Which project do I choose? ==<br />
<br />
Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.<br />
: View the documents and download the ISO from http://live.osgeo.org<br />
[[File:Osgeolive wordle.png|400px|center]]<br />
<br />
== How to get in contact via mailing lists ==<br />
<br />
Since OSGeo is an umbrella organisation for multiple projects, each project has their own discussion and development mailing lists.<br />
<br />
'''Main OSGeo mailing lists of interest to students:'''<br />
: Please start here, when contacting us for the first time with questions about Google Summer of Code.<br />
<br />
:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc)<br />
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)<br />
<br />
Also see the [[Mailing Lists]] page for project specific lists, as well as the longer list at http://lists.osgeo.org.<br />
<br />
<br />
== How to get in contact via IRC ==<br />
<br />
Primary channel:<br />
<br />
* irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client], [http://webchat.freenode.net alternative])<br />
<br />
GSoC @ OSGeo inter-project discussions:<br />
<br />
* irc://irc.freenode.net/#osgeo-soc<br />
<br />
Project irc channels:<br />
<br />
* irc://irc.freenode.net/#gdal<br />
* irc://irc.freenode.net/#geoserver<br />
* irc://irc.freenode.net/#geotools<br />
* irc://irc.freenode.net/#grass<br />
* irc://irc.freenode.net/#gvsig<br />
* irc://irc.freenode.net/#mapguide<br />
* irc://irc.freenode.net/#mapnik<br />
* irc://irc.freenode.net/#mapserver<br />
* irc://irc.freenode.net/#openlayers<br />
* irc://irc.freenode.net/#opticks<br />
* irc://irc.freenode.net/#osgeolive<br />
* irc://irc.freenode.net/#ossimplanet<br />
* irc://irc.freenode.net/#pgrouting-project<br />
* irc://irc.freenode.net/#postgis<br />
* irc://irc.freenode.net/#qgis<br />
* irc://irc.freenode.net/#udig<br />
* irc://irc.oftc.net/#osm-dev<br />
<br />
== Application questions we'll ask you ==<br />
'''''[Provisional]'''''<br />
<br />
* All questions must be answered, ''no exceptions''. Treat this as something between a formal job application and a scholarship application, because that's exactly what it is.<br />
<br />
Name:<br />
<br />
Country:<br />
<br />
School and degree:<br />
<br />
Email:<br />
<br />
Phone:<br />
<br />
OSGeo project(s):<br />
<br />
Title:<br />
(please include the name of the member project as part of<br />
the title, for example: "Gee Whiz Foobar 2001 for QGIS")<br />
<br />
Describe your idea<br />
1. Introduction<br />
2. Background<br />
3. The idea<br />
4. Project plan ('''detailed timeline''': how do you plan to spend your summer?)<br />
5. Future ideas / How can your idea be expanded? <br />
<br />
Explain how your SoC task would benefit the OSGeo member<br />
project and more generally the OSGeo Foundation as a whole:<br />
<br />
Please provide details of general computing experience:<br />
(operating systems you use on a day-to-day basis, languages you<br />
could write a program in, hardware, networking experience, etc.)<br />
<br />
Please provide details of previous GIS experience:<br />
<br />
Please provide details of any previous involvement with<br />
GIS programming and other software programming:<br />
<br />
Please tell us why you are interested in GIS and open<br />
source software:<br />
<br />
Please tell us why you are interested in working for OSGeo<br />
and the software project you have selected:<br />
<br />
Please tell us why you are interested in your specific<br />
coding project:<br />
<br />
Would your application contribute to your ongoing studies/<br />
degree? If so, how?<br />
<br />
Please explain how you intend to continue being an active<br />
member of your project and/or OSGeo AFTER the summer is over:<br />
<br />
Do you understand this is a serious commitment, equivalent<br />
to a full-time paid summer internship or summer job?<br />
<br />
Do you have any known time conflicts during the official coding<br />
period? (May 19 to August 18)<br />
<br />
== What to expect during the summer ==<br />
<br />
* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you:<br />
: [http://google-opensource.blogspot.com/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code] -- READ THIS eBOOK<br />
<br />
<br />
=== Be prepared to be in constant communication with your mentors and project ===<br />
<br />
You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.<br />
<br />
University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.<br />
<br />
=== Weekly reports ===<br />
<br />
Yes, every week we expect to see a report posted to the soc@osgeo mailing list that at least answers the following questions:<br />
<br />
# What did you get done this week?<br />
# What do you plan on doing next week?<br />
# Are you blocked on anything?<br />
<br />
These questions BTW are the same as are used in real-work, when developing with the <br />
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)<br />
<br />
If you want, feel free to write *more*. But three sentences is the bare minimum. *IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME*, if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you in IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's cool. We have all studied at some point, just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)<br />
<br />
Last year this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.<br />
<br />
<br />
=== Wiki page and blogs ===<br />
<br />
In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.<br />
<br />
Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this.<br />
<br />
We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.<br />
<br />
Final reports from those blogs and wiki pages will be collected into a OSGeoofcode posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')<br />
<br />
<br />
[Back to [[Google Summer of Code 2014]] @ OSGeo]<br />
[[Category: Google Summer of Code]]</div>Wiki-Grizonnetm