https://wiki.osgeo.org/w/api.php?action=feedcontributions&user=Wiki-Surveyor&feedformat=atomOSGeo - User contributions [en]2024-03-29T10:43:32ZUser contributionsMediaWiki 1.35.9https://wiki.osgeo.org/w/index.php?title=User:Surveyor&diff=116760User:Surveyor2018-09-30T03:22:38Z<p>Wiki-Surveyor: /* Landon Blake (AKA - The Sunburned Surveyor) */</p>
<hr />
<div>{{OSGeo Member<br />
|Name=Landon Blake<br />
|JobTitle=Owner<br />
|Company=Redefined Horizons<br />
|Country=USA<br />
|State=California<br />
|City=Stockton<br />
|Coordinate=37.9577016, -121.2907796<br />
|LocalChapter=California Chapter<br />
|Email=sunburned dot surveyor at gmail dot com<br />
|Phone=(209) 571-1765<br />
|SocialMedia=https://twitter.com/mapit4u; http://www.linkedin.com/in/landonblake;<br />
|Website=http://www.redefinedhorizons.com/<br />
|Photo=landon_blake_portrait.jpg<br />
|Info=Landon Blake is a land surveyor and GIS programmer with a focus on OpenJUMP and CAD customization. He serves as the Vice President of the California Land Surveyors Association Central Valley Chapter, is a member of the California Land Surveyors Association GIS Committee, and also serves as a member of the California Geodetic Control Working Group.<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=Yes<br />
|Board=No<br />
|Coder=No<br />
|Translate=No<br />
|PSC=No<br />
|ExBoard=No<br />
|Charter=No<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=No<br />
}}<br />
=== [http://www.redefinedhorizons.com/bio.shtml Landon Blake] (AKA - The Sunburned Surveyor) ===<br />
<br />
[[File:landon_blake_portrait.jpg|100px|thumb|right|Landon Blake]]<br />
<br />
Owner, [http://www.redefinedhorizons.com Redefined Horizons]<br />
<br />
Location: Stockton, California, United States of America<br />
<br />
Landon Blake is a land surveyor and GIS programmer with a focus on OpenJUMP and CAD customization. He serves as the Vice President of the California Land Surveyors Association Central Valley Chapter, is a member of the California Land Surveyors Association GIS Committee, and also serves as a member of the California Geodetic Control Working Group.<br />
<br />
* Web Page: [http://www.redefinedhorizons.com]<br />
* Blog: [http://www.redefinedhorizonsblog.com]<br />
* Twitter: [https://twitter.com/mapit4u]<br />
* LinkedIn: [http://www.linkedin.com/in/landonblake]<br />
<br />
;OSGeo Experience<br />
* Past Volunteer Editor of the OSGeo Journal<br />
* Board Representative for the OSGeo California Chapter<br />
<br />
;Contact:<br />
: Email: sunburned dot surveyor at gmail dot com<br />
: Phone (cell): (209) 298-7521<br />
: Phone (home): (209) 464-2612<br />
: Skype: <br />
<br />
;Profile last updated: 08 13 2014<br />
<br />
[[GIS Data Models]]<br />
<br />
[[Category:OSGeo Advocate]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Java_2018_Code_Sprint&diff=116759Java 2018 Code Sprint2018-09-30T03:21:42Z<p>Wiki-Surveyor: /* Participants */</p>
<hr />
<div>The Java tribe has a real challenge for 2018 - updating our open source projects for the Java roadmap.<br />
<br />
== Location ==<br />
<br />
Sprint scheduled for Q4 2018, proposed date:<br />
<br />
* October 22-26th <br />
<br />
We are looking at setting up a distributed sprint with locations in:<br />
<br />
* North America - Victoria, Boundless Office, billeting options available for those travelling<br />
* Europe - Sevilla, Spain half.confirmed. Italy or UK have been proposed, recommendations welcome!<br />
* Oceania - recommendations welcome<br />
<br />
=== Contacts ===<br />
<br />
Jody Garnett<br />
<br />
== Sponsors ==<br />
<br />
We would like to thank our sponsors!<br />
<br />
=== Gold Sponsors ===<br />
<br />
TBD<br />
<br />
=== Bronze Sponsors ===<br />
<br />
TBD<br />
<br />
=== In-Kind Support ===<br />
<br />
[[File:Boundless_Logo.png|350px|link=http://boundlessgeo.com]] [[File:GeoCat.png|350px|link=https://www.geocat.net]]<br />
<br />
== Participants ==<br />
<br />
Please add your name and the projects you are planning to sprint and note the likehood of your attendance.<br />
<br />
{| style="border: solid grey 1px; width:100%" class="sortable"<br />
|+ Participants<br />
|-<br />
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Notes || Attendance <br />
|-<br />
| 1 || [[User:Delawen|María Arias de Reyna]] || Spain || GeoCat bv || working remotely || working remotely || GeoNetwork || Notes || Partially working on the codesprint <br />
|-<br />
| 2 || [[User:Jive|Jody Garnett]] || Canada || Boundless || local || local || GeoTools || Able to host guests || Confirmed<br />
|-<br />
| 3 || [[User:Tbarsballe|Torben Barsballe]] || Canada || Boundless || local || local || GT/GS || || Confirmed<br />
|-<br />
| 4 || [[User:ksmith|Kevin Smith]] || Canada || Boundless || local || local || GT/GWC/GS || || Confirmed<br />
|-<br />
| 5 || [[User:dvntucker|Devon Tucker]] || Canada || Boundless || local || local || GT/GS || || Confirmed<br />
|-<br />
| 6 || [[User:moovida|Antonello Andrea]] || Italy || HydroloGIS || TBD || TBD || GT/JTS, Hortonmachine || || Confirmed, waiting on Europa location to be revealed :-)<br />
|-<br />
| 7 || [[User:ianturton|Ian Turton]] || UK || Astun || TBD || TBD || GT/GS || || Either Italy or remote <br />
|-<br />
| 8 || [[User:Aaime|Andrea Aime]] || Italy || GeoSolutions || TBD || TBD || GT/GWC/GS/jai-ext/imageio-ext/jaitools || || Either Italy or remote <br />
|-<br />
| 9 || [[User:jhughes|Jim Hughes]] || US || CCRi || TBD || TBD || JTS/GT/GS/GeoMesa || || Confirmed <br />
|-<br />
| 10 || [[User:Surveyor|Landon Blake]] || US || BKF Engineers || Working Remotely || Working Remotely || JTS/Proj4J || || Confirmed <br />
|}<br />
<br />
== Discussion ==<br />
<br />
=== Java has a roadmap? === <br />
<br />
Yes, we had a previous sprint focused on Java 8 compatibility, several features had changed breaking compatibility.<br />
<br />
More importantly the Java roadmap has changed to a six-month release cycle:<br />
<br />
* six month release cycle is already well underway having started with Java 9 and Java 10.<br />
<br />
* Oracle is offering three year LTS releases commercially<br />
<br />
* AdoptOpenJDK is setting up LTS releases of OpenJDK .. backed by IBM, Microsoft and others.<br />
<br />
* RedHat is focusing on LTS (skipping Java 9 and Java 10) and plans to ship OpenJDK based on Java SE 11<br />
<br />
=== Why is updating our open source projects for the Java roadmap a challenge? === <br />
<br />
- Java changed the service provider interface plugin system used by GeoTools, forcing the project to write its own replacement.<br />
<br />
- The java runtime has been broken up into modules, not all of which are activated by default. We need to review what sections of the JRE we require and ensure they are turned on.<br />
<br />
- Java introduced the module system "jigsaw" providing both a class-path and module-path for loading jars.<br />
<br />
- When loaded on the module-path jars are prevented from using the same package. This breaks multi-jar projects like GeoTools library where gt-api defining interfaces, and gt-main providing implementations.<br />
<br />
- Jigsaw also locks down aspects of Java reflection, affecting projects like Spring that make heavy use of reflection to "auto wire" GeoServer together. Spring 5 has been released and upgrading to this release will be a key focus.<br />
<br />
- With these changes projects like GeoServer need to review of hundreds open source dependencies to determine what other libraries are broken, if an update is available or replacement can be found.<br />
<br />
- The java web service framework (responsible for concepts like Servlet and Session) is being removed from Oracle oversight and has been setup as [Jakarta EE Software](https://jakarta.ee).<br />
<br />
=== Recommended reading ===<br />
<br />
* [https://www.azul.com/what-comes-after-jdk-8/ What Comes After JDK 8?]<br />
* [https://medium.com/criciumadev/its-time-migrating-to-java-11-5eb3868354f9 It's time! Migrating to Java 11] - contains working example of updating spring application<br />
* [http://openjdk.java.net/projects/jigsaw/spec/sotms The State of the Module System] / [https://www.oracle.com/corporate/features/understanding-java-9-modules.html Understanding Java 9 modules]<br />
<br />
=== Do you have any experience running sprints? === <br />
<br />
The GeoServer team really benefited from [[Java 2017 Code Sprint|java 2017 code sprint]] and is eager to repeat the success.<br />
<br />
== GeoServer Planning ==<br />
<br />
Initial planning has started:<br />
<br />
* [https://github.com/geoserver/geoserver/wiki/GSIP-171 GSIP 171 Java 18.9 Compatibility] (GeoServer)<br />
<br />
Preflight activities:<br />
<br />
* dependency audit <br />
<br />
Required updates:<br />
<br />
* Spring 5 - Older versions of spring are not compatible with Java 11. Upgrading to from Spring 4 to Spring 5 does involve handling some API changes.<br />
* HazelCast - Like Spring, HazelCast involves a lot of reflection. <br />
<br />
Module refactor:<br />
<br />
* Repackage GeoServer application jars to prevent conflicts at the package level.<br />
* Resulting application can be used on either the CLASSPATH (Java 8) or MODULEPATH (Java 11)<br />
<br />
== GeoTools Planning ==<br />
<br />
Planning and work is already well underway:<br />
<br />
* [https://github.com/geotools/geotools/wiki/Java-9-Compatibility GeoTools Java-9-Compatibility] (GeoTools)<br />
<br />
The first completed phase is to allow GeoTools to be used on the classpath:<br />
<br />
* [https://github.com/geotools/geotools/wiki/Migrate-Units-to-JSR-363 Migrate Units to JSR-363] (GeoTools)<br />
* [https://github.com/geotools/geotools/wiki/FactoryRegistry-Refactoring-for-Java-9-Compatibility FactoryRegistry Refactoring for Java 9 Compatibility] (GeoTools)<br />
<br />
The sprint goal is to refactor the geotools library into modules, allowing the jars to be used on either the classpath (Java 8) or the module path (Java 11).<br />
<br />
* [https://github.com/geotools/geotools/wiki/Restructure-GeoTools-into-Jigsaw-modules Restructure GeoTools into Jigsaw modules] (GeoTools)<br />
<br />
* Core library refactored into modules<br />
<br />
[[File:Gt-modules.png|frameless|GeoTools Java 11 modules ]]<br />
<br />
* plugins used to automatic modules to dependencies on the classpath<br />
<br />
[[File:Module-path.png|800px|module-path bridge to classpath]]<br />
<br />
In the above illustration the gt-svg module is used as an automatic module publishing org.geotools.renderer.style.svg package. It acts as a bridge to the multi-jar project batik still on the classpath, completely masking the fact batik is used used to read and render svg files. The core module gt-renderer publishes select packages for use, while hiding others. It makes use of ServiceLocator to access the IconFactory implemented by gt-svg and never has direct use of the batik implementation.<br />
<br />
For this to work the gt-svg jar has been refactored, moving the icon factory the new package org.geotools.style.svg. This was required as the package org.geotools.renderer.style was already published by gt-renderer.<br />
<br />
We expect:<br />
<br />
* Initial focus is on the core library, refactoring to allow jars to be used on the module path as named modules<br />
* plugins will remain on the classpath, accessed via service locator, any conflicting packages will not be visible to client code<br />
<br />
== JTS Topology Suite Activities ==<br />
<br />
Results of bonn code sprint:<br />
<br />
* [https://github.com/locationtech/jts/pull/274 Add module names for better Java 9/Jigsaw support] (JTS Topology Suite)<br />
<br />
JTS jars can be placed on the module-path used as an automatic module, the jars have been supplied am Automatic-Module-Name using a MANIFEST.MF entry.<br />
<br />
For an example.application using jts-core as a module add '''module-info''':<br />
<br />
module example.application {<br />
requires org.locationtech.jts; // jts-core<br />
}<br />
<br />
== GeoNetwork Planning ==<br />
<br />
[[https://github.com/geonetwork/core-geonetwork/wiki/OSGeo-Java-codesprint-2018 Strategy for GeoNetwork]]<br />
<br />
== How to sponsorship ==<br />
<br />
Contributions will be put towards travel costs for sprint participants who would be otherwise unable to attend. Any surplus at the end of the event will be turned over to OSGeo or used for a future code sprint. We have set-up the sprint to minimize travel and accommodation costs.<br />
<br />
Sponsors will receive the following benefits / honours:<br />
<br />
* Your logo at the top of this page<br />
* Mention in project communication (for example the GeoServer 2.15 release announcement)<br />
* The ability to run on a supported java platform<br />
* Our gratitude :)<br />
<br />
This event provides the following sponsorship levels:<br />
<br />
{| class="wikitable"<br />
|-<br />
| Gold<br />
| style="text-align:right;" | $2500 USD<br />
|-<br />
| Silver<br />
| style="text-align:right;" | $1500 USD<br />
|-<br />
| Bronze<br />
| style="text-align:right;" | $750 USD<br />
|-<br />
| In-Kind || colspan="3" | In-kind support graciously accepted<br />
|}<br />
<br />
This is an official OSGeo event, your contribution counts towards being recognized as an [https://www.osgeo.org/about/how-to-become-a-sponsor/ OSGeo Sponsors].<br />
<br />
For more information on sponsorship, please contact [[Jody Garnett]], [[User:Aaime|Andrea Aime]].<br />
<br />
=== How to Sponsor ===<br />
<br />
# Contact OSGeo [[Treasurer]] for details on using PayPal or to request an invoice:<br />
# The OSGeo [[Treasurer]] will contact both you and the event organizers to acknowledge your sponsorship<br />
#* Please have a logo ready for your organization if you wish to be acknowledged publicly <br />
#* Your event sponsorship, at your request, can contribute towards [http://www.osgeo.org/sponsorship being recognized] as an OSGeo Foundation sponsor<br />
<br />
=== Sponsorship Outreach ===<br />
<br />
We are reaching out to organizations to see if there is interest in sponsorship:<br />
<br />
* Prior sponsors: gaia3d, boundless, ian, geodan, how2map, fossgis, atol, geosolutions, astun<br />
* Local sponsors: astun, vivid solutions, transient software<br />
<br />
If there is a lot of local sponsorship we expect to drag the developers away from the task at hand and meet the local community (at a social evening or similar).<br />
<br />
=== OSGeo Funding Request ===<br />
<br />
The following information is requested by OSGeo Board [[Code_Sprint_Guidelines]], we provided an indication that we would be planning a sprint during the 2018 budget process.<br />
<br />
* [[Java_2018_Code_Sprint_Budget_:_Budget|Java 2018 Code Sprint Budget]]<br />
<br />
It is intended to that OSGeo be recognized as hosting this event, rather than acknowledged as a sponsor.<br />
<br />
[[Category:Code Sprints]]<br />
[[Category:Java Tribe Code Sprint]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Java_2018_Code_Sprint&diff=116758Java 2018 Code Sprint2018-09-30T03:21:13Z<p>Wiki-Surveyor: /* Participants */</p>
<hr />
<div>The Java tribe has a real challenge for 2018 - updating our open source projects for the Java roadmap.<br />
<br />
== Location ==<br />
<br />
Sprint scheduled for Q4 2018, proposed date:<br />
<br />
* October 22-26th <br />
<br />
We are looking at setting up a distributed sprint with locations in:<br />
<br />
* North America - Victoria, Boundless Office, billeting options available for those travelling<br />
* Europe - Sevilla, Spain half.confirmed. Italy or UK have been proposed, recommendations welcome!<br />
* Oceania - recommendations welcome<br />
<br />
=== Contacts ===<br />
<br />
Jody Garnett<br />
<br />
== Sponsors ==<br />
<br />
We would like to thank our sponsors!<br />
<br />
=== Gold Sponsors ===<br />
<br />
TBD<br />
<br />
=== Bronze Sponsors ===<br />
<br />
TBD<br />
<br />
=== In-Kind Support ===<br />
<br />
[[File:Boundless_Logo.png|350px|link=http://boundlessgeo.com]] [[File:GeoCat.png|350px|link=https://www.geocat.net]]<br />
<br />
== Participants ==<br />
<br />
Please add your name and the projects you are planning to sprint and note the likehood of your attendance.<br />
<br />
{| style="border: solid grey 1px; width:100%" class="sortable"<br />
|+ Participants<br />
|-<br />
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Notes || Attendance <br />
|-<br />
| 1 || [[User:Delawen|María Arias de Reyna]] || Spain || GeoCat bv || working remotely || working remotely || GeoNetwork || Notes || Partially working on the codesprint <br />
|-<br />
| 2 || [[User:Jive|Jody Garnett]] || Canada || Boundless || local || local || GeoTools || Able to host guests || Confirmed<br />
|-<br />
| 3 || [[User:Tbarsballe|Torben Barsballe]] || Canada || Boundless || local || local || GT/GS || || Confirmed<br />
|-<br />
| 4 || [[User:ksmith|Kevin Smith]] || Canada || Boundless || local || local || GT/GWC/GS || || Confirmed<br />
|-<br />
| 5 || [[User:dvntucker|Devon Tucker]] || Canada || Boundless || local || local || GT/GS || || Confirmed<br />
|-<br />
| 6 || [[User:moovida|Antonello Andrea]] || Italy || HydroloGIS || TBD || TBD || GT/JTS, Hortonmachine || || Confirmed, waiting on Europa location to be revealed :-)<br />
|-<br />
| 7 || [[User:ianturton|Ian Turton]] || UK || Astun || TBD || TBD || GT/GS || || Either Italy or remote <br />
|-<br />
| 8 || [[User:Aaime|Andrea Aime]] || Italy || GeoSolutions || TBD || TBD || GT/GWC/GS/jai-ext/imageio-ext/jaitools || || Either Italy or remote <br />
|-<br />
| 9 || [[User:jhughes|Jim Hughes]] || US || CCRi || TBD || TBD || JTS/GT/GS/GeoMesa || || Confirmed <br />
|-<br />
| 10 || [[User:Surveyor]] || US || BKF Engineers || Working Remotely || Working Remotely || JTS/Proj4J || || Confirmed <br />
|}<br />
<br />
== Discussion ==<br />
<br />
=== Java has a roadmap? === <br />
<br />
Yes, we had a previous sprint focused on Java 8 compatibility, several features had changed breaking compatibility.<br />
<br />
More importantly the Java roadmap has changed to a six-month release cycle:<br />
<br />
* six month release cycle is already well underway having started with Java 9 and Java 10.<br />
<br />
* Oracle is offering three year LTS releases commercially<br />
<br />
* AdoptOpenJDK is setting up LTS releases of OpenJDK .. backed by IBM, Microsoft and others.<br />
<br />
* RedHat is focusing on LTS (skipping Java 9 and Java 10) and plans to ship OpenJDK based on Java SE 11<br />
<br />
=== Why is updating our open source projects for the Java roadmap a challenge? === <br />
<br />
- Java changed the service provider interface plugin system used by GeoTools, forcing the project to write its own replacement.<br />
<br />
- The java runtime has been broken up into modules, not all of which are activated by default. We need to review what sections of the JRE we require and ensure they are turned on.<br />
<br />
- Java introduced the module system "jigsaw" providing both a class-path and module-path for loading jars.<br />
<br />
- When loaded on the module-path jars are prevented from using the same package. This breaks multi-jar projects like GeoTools library where gt-api defining interfaces, and gt-main providing implementations.<br />
<br />
- Jigsaw also locks down aspects of Java reflection, affecting projects like Spring that make heavy use of reflection to "auto wire" GeoServer together. Spring 5 has been released and upgrading to this release will be a key focus.<br />
<br />
- With these changes projects like GeoServer need to review of hundreds open source dependencies to determine what other libraries are broken, if an update is available or replacement can be found.<br />
<br />
- The java web service framework (responsible for concepts like Servlet and Session) is being removed from Oracle oversight and has been setup as [Jakarta EE Software](https://jakarta.ee).<br />
<br />
=== Recommended reading ===<br />
<br />
* [https://www.azul.com/what-comes-after-jdk-8/ What Comes After JDK 8?]<br />
* [https://medium.com/criciumadev/its-time-migrating-to-java-11-5eb3868354f9 It's time! Migrating to Java 11] - contains working example of updating spring application<br />
* [http://openjdk.java.net/projects/jigsaw/spec/sotms The State of the Module System] / [https://www.oracle.com/corporate/features/understanding-java-9-modules.html Understanding Java 9 modules]<br />
<br />
=== Do you have any experience running sprints? === <br />
<br />
The GeoServer team really benefited from [[Java 2017 Code Sprint|java 2017 code sprint]] and is eager to repeat the success.<br />
<br />
== GeoServer Planning ==<br />
<br />
Initial planning has started:<br />
<br />
* [https://github.com/geoserver/geoserver/wiki/GSIP-171 GSIP 171 Java 18.9 Compatibility] (GeoServer)<br />
<br />
Preflight activities:<br />
<br />
* dependency audit <br />
<br />
Required updates:<br />
<br />
* Spring 5 - Older versions of spring are not compatible with Java 11. Upgrading to from Spring 4 to Spring 5 does involve handling some API changes.<br />
* HazelCast - Like Spring, HazelCast involves a lot of reflection. <br />
<br />
Module refactor:<br />
<br />
* Repackage GeoServer application jars to prevent conflicts at the package level.<br />
* Resulting application can be used on either the CLASSPATH (Java 8) or MODULEPATH (Java 11)<br />
<br />
== GeoTools Planning ==<br />
<br />
Planning and work is already well underway:<br />
<br />
* [https://github.com/geotools/geotools/wiki/Java-9-Compatibility GeoTools Java-9-Compatibility] (GeoTools)<br />
<br />
The first completed phase is to allow GeoTools to be used on the classpath:<br />
<br />
* [https://github.com/geotools/geotools/wiki/Migrate-Units-to-JSR-363 Migrate Units to JSR-363] (GeoTools)<br />
* [https://github.com/geotools/geotools/wiki/FactoryRegistry-Refactoring-for-Java-9-Compatibility FactoryRegistry Refactoring for Java 9 Compatibility] (GeoTools)<br />
<br />
The sprint goal is to refactor the geotools library into modules, allowing the jars to be used on either the classpath (Java 8) or the module path (Java 11).<br />
<br />
* [https://github.com/geotools/geotools/wiki/Restructure-GeoTools-into-Jigsaw-modules Restructure GeoTools into Jigsaw modules] (GeoTools)<br />
<br />
* Core library refactored into modules<br />
<br />
[[File:Gt-modules.png|frameless|GeoTools Java 11 modules ]]<br />
<br />
* plugins used to automatic modules to dependencies on the classpath<br />
<br />
[[File:Module-path.png|800px|module-path bridge to classpath]]<br />
<br />
In the above illustration the gt-svg module is used as an automatic module publishing org.geotools.renderer.style.svg package. It acts as a bridge to the multi-jar project batik still on the classpath, completely masking the fact batik is used used to read and render svg files. The core module gt-renderer publishes select packages for use, while hiding others. It makes use of ServiceLocator to access the IconFactory implemented by gt-svg and never has direct use of the batik implementation.<br />
<br />
For this to work the gt-svg jar has been refactored, moving the icon factory the new package org.geotools.style.svg. This was required as the package org.geotools.renderer.style was already published by gt-renderer.<br />
<br />
We expect:<br />
<br />
* Initial focus is on the core library, refactoring to allow jars to be used on the module path as named modules<br />
* plugins will remain on the classpath, accessed via service locator, any conflicting packages will not be visible to client code<br />
<br />
== JTS Topology Suite Activities ==<br />
<br />
Results of bonn code sprint:<br />
<br />
* [https://github.com/locationtech/jts/pull/274 Add module names for better Java 9/Jigsaw support] (JTS Topology Suite)<br />
<br />
JTS jars can be placed on the module-path used as an automatic module, the jars have been supplied am Automatic-Module-Name using a MANIFEST.MF entry.<br />
<br />
For an example.application using jts-core as a module add '''module-info''':<br />
<br />
module example.application {<br />
requires org.locationtech.jts; // jts-core<br />
}<br />
<br />
== GeoNetwork Planning ==<br />
<br />
[[https://github.com/geonetwork/core-geonetwork/wiki/OSGeo-Java-codesprint-2018 Strategy for GeoNetwork]]<br />
<br />
== How to sponsorship ==<br />
<br />
Contributions will be put towards travel costs for sprint participants who would be otherwise unable to attend. Any surplus at the end of the event will be turned over to OSGeo or used for a future code sprint. We have set-up the sprint to minimize travel and accommodation costs.<br />
<br />
Sponsors will receive the following benefits / honours:<br />
<br />
* Your logo at the top of this page<br />
* Mention in project communication (for example the GeoServer 2.15 release announcement)<br />
* The ability to run on a supported java platform<br />
* Our gratitude :)<br />
<br />
This event provides the following sponsorship levels:<br />
<br />
{| class="wikitable"<br />
|-<br />
| Gold<br />
| style="text-align:right;" | $2500 USD<br />
|-<br />
| Silver<br />
| style="text-align:right;" | $1500 USD<br />
|-<br />
| Bronze<br />
| style="text-align:right;" | $750 USD<br />
|-<br />
| In-Kind || colspan="3" | In-kind support graciously accepted<br />
|}<br />
<br />
This is an official OSGeo event, your contribution counts towards being recognized as an [https://www.osgeo.org/about/how-to-become-a-sponsor/ OSGeo Sponsors].<br />
<br />
For more information on sponsorship, please contact [[Jody Garnett]], [[User:Aaime|Andrea Aime]].<br />
<br />
=== How to Sponsor ===<br />
<br />
# Contact OSGeo [[Treasurer]] for details on using PayPal or to request an invoice:<br />
# The OSGeo [[Treasurer]] will contact both you and the event organizers to acknowledge your sponsorship<br />
#* Please have a logo ready for your organization if you wish to be acknowledged publicly <br />
#* Your event sponsorship, at your request, can contribute towards [http://www.osgeo.org/sponsorship being recognized] as an OSGeo Foundation sponsor<br />
<br />
=== Sponsorship Outreach ===<br />
<br />
We are reaching out to organizations to see if there is interest in sponsorship:<br />
<br />
* Prior sponsors: gaia3d, boundless, ian, geodan, how2map, fossgis, atol, geosolutions, astun<br />
* Local sponsors: astun, vivid solutions, transient software<br />
<br />
If there is a lot of local sponsorship we expect to drag the developers away from the task at hand and meet the local community (at a social evening or similar).<br />
<br />
=== OSGeo Funding Request ===<br />
<br />
The following information is requested by OSGeo Board [[Code_Sprint_Guidelines]], we provided an indication that we would be planning a sprint during the 2018 budget process.<br />
<br />
* [[Java_2018_Code_Sprint_Budget_:_Budget|Java 2018 Code Sprint Budget]]<br />
<br />
It is intended to that OSGeo be recognized as hosting this event, rather than acknowledged as a sponsor.<br />
<br />
[[Category:Code Sprints]]<br />
[[Category:Java Tribe Code Sprint]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Java_2018_Code_Sprint&diff=116757Java 2018 Code Sprint2018-09-30T03:20:04Z<p>Wiki-Surveyor: /* Participants */</p>
<hr />
<div>The Java tribe has a real challenge for 2018 - updating our open source projects for the Java roadmap.<br />
<br />
== Location ==<br />
<br />
Sprint scheduled for Q4 2018, proposed date:<br />
<br />
* October 22-26th <br />
<br />
We are looking at setting up a distributed sprint with locations in:<br />
<br />
* North America - Victoria, Boundless Office, billeting options available for those travelling<br />
* Europe - Sevilla, Spain half.confirmed. Italy or UK have been proposed, recommendations welcome!<br />
* Oceania - recommendations welcome<br />
<br />
=== Contacts ===<br />
<br />
Jody Garnett<br />
<br />
== Sponsors ==<br />
<br />
We would like to thank our sponsors!<br />
<br />
=== Gold Sponsors ===<br />
<br />
TBD<br />
<br />
=== Bronze Sponsors ===<br />
<br />
TBD<br />
<br />
=== In-Kind Support ===<br />
<br />
[[File:Boundless_Logo.png|350px|link=http://boundlessgeo.com]] [[File:GeoCat.png|350px|link=https://www.geocat.net]]<br />
<br />
== Participants ==<br />
<br />
Please add your name and the projects you are planning to sprint and note the likehood of your attendance.<br />
<br />
{| style="border: solid grey 1px; width:100%" class="sortable"<br />
|+ Participants<br />
|-<br />
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Notes || Attendance <br />
|-<br />
| 1 || [[User:Delawen|María Arias de Reyna]] || Spain || GeoCat bv || working remotely || working remotely || GeoNetwork || Notes || Partially working on the codesprint <br />
|-<br />
| 2 || [[User:Jive|Jody Garnett]] || Canada || Boundless || local || local || GeoTools || Able to host guests || Confirmed<br />
|-<br />
| 3 || [[User:Tbarsballe|Torben Barsballe]] || Canada || Boundless || local || local || GT/GS || || Confirmed<br />
|-<br />
| 4 || [[User:ksmith|Kevin Smith]] || Canada || Boundless || local || local || GT/GWC/GS || || Confirmed<br />
|-<br />
| 5 || [[User:dvntucker|Devon Tucker]] || Canada || Boundless || local || local || GT/GS || || Confirmed<br />
|-<br />
| 6 || [[User:moovida|Antonello Andrea]] || Italy || HydroloGIS || TBD || TBD || GT/JTS, Hortonmachine || || Confirmed, waiting on Europa location to be revealed :-)<br />
|-<br />
| 7 || [[User:ianturton|Ian Turton]] || UK || Astun || TBD || TBD || GT/GS || || Either Italy or remote <br />
|-<br />
| 8 || [[User:Aaime|Andrea Aime]] || Italy || GeoSolutions || TBD || TBD || GT/GWC/GS/jai-ext/imageio-ext/jaitools || || Either Italy or remote <br />
|-<br />
| 9 || [[User:jhughes|Jim Hughes]] || US || CCRi || TBD || TBD || JTS/GT/GS/GeoMesa || || Confirmed <br />
|-<br />
| 10 || [[User:Landon Blake]] || US || BKF Engineers || Working Remotely || Working Remotely || JTS/Proj4J || || Confirmed <br />
|}<br />
<br />
== Discussion ==<br />
<br />
=== Java has a roadmap? === <br />
<br />
Yes, we had a previous sprint focused on Java 8 compatibility, several features had changed breaking compatibility.<br />
<br />
More importantly the Java roadmap has changed to a six-month release cycle:<br />
<br />
* six month release cycle is already well underway having started with Java 9 and Java 10.<br />
<br />
* Oracle is offering three year LTS releases commercially<br />
<br />
* AdoptOpenJDK is setting up LTS releases of OpenJDK .. backed by IBM, Microsoft and others.<br />
<br />
* RedHat is focusing on LTS (skipping Java 9 and Java 10) and plans to ship OpenJDK based on Java SE 11<br />
<br />
=== Why is updating our open source projects for the Java roadmap a challenge? === <br />
<br />
- Java changed the service provider interface plugin system used by GeoTools, forcing the project to write its own replacement.<br />
<br />
- The java runtime has been broken up into modules, not all of which are activated by default. We need to review what sections of the JRE we require and ensure they are turned on.<br />
<br />
- Java introduced the module system "jigsaw" providing both a class-path and module-path for loading jars.<br />
<br />
- When loaded on the module-path jars are prevented from using the same package. This breaks multi-jar projects like GeoTools library where gt-api defining interfaces, and gt-main providing implementations.<br />
<br />
- Jigsaw also locks down aspects of Java reflection, affecting projects like Spring that make heavy use of reflection to "auto wire" GeoServer together. Spring 5 has been released and upgrading to this release will be a key focus.<br />
<br />
- With these changes projects like GeoServer need to review of hundreds open source dependencies to determine what other libraries are broken, if an update is available or replacement can be found.<br />
<br />
- The java web service framework (responsible for concepts like Servlet and Session) is being removed from Oracle oversight and has been setup as [Jakarta EE Software](https://jakarta.ee).<br />
<br />
=== Recommended reading ===<br />
<br />
* [https://www.azul.com/what-comes-after-jdk-8/ What Comes After JDK 8?]<br />
* [https://medium.com/criciumadev/its-time-migrating-to-java-11-5eb3868354f9 It's time! Migrating to Java 11] - contains working example of updating spring application<br />
* [http://openjdk.java.net/projects/jigsaw/spec/sotms The State of the Module System] / [https://www.oracle.com/corporate/features/understanding-java-9-modules.html Understanding Java 9 modules]<br />
<br />
=== Do you have any experience running sprints? === <br />
<br />
The GeoServer team really benefited from [[Java 2017 Code Sprint|java 2017 code sprint]] and is eager to repeat the success.<br />
<br />
== GeoServer Planning ==<br />
<br />
Initial planning has started:<br />
<br />
* [https://github.com/geoserver/geoserver/wiki/GSIP-171 GSIP 171 Java 18.9 Compatibility] (GeoServer)<br />
<br />
Preflight activities:<br />
<br />
* dependency audit <br />
<br />
Required updates:<br />
<br />
* Spring 5 - Older versions of spring are not compatible with Java 11. Upgrading to from Spring 4 to Spring 5 does involve handling some API changes.<br />
* HazelCast - Like Spring, HazelCast involves a lot of reflection. <br />
<br />
Module refactor:<br />
<br />
* Repackage GeoServer application jars to prevent conflicts at the package level.<br />
* Resulting application can be used on either the CLASSPATH (Java 8) or MODULEPATH (Java 11)<br />
<br />
== GeoTools Planning ==<br />
<br />
Planning and work is already well underway:<br />
<br />
* [https://github.com/geotools/geotools/wiki/Java-9-Compatibility GeoTools Java-9-Compatibility] (GeoTools)<br />
<br />
The first completed phase is to allow GeoTools to be used on the classpath:<br />
<br />
* [https://github.com/geotools/geotools/wiki/Migrate-Units-to-JSR-363 Migrate Units to JSR-363] (GeoTools)<br />
* [https://github.com/geotools/geotools/wiki/FactoryRegistry-Refactoring-for-Java-9-Compatibility FactoryRegistry Refactoring for Java 9 Compatibility] (GeoTools)<br />
<br />
The sprint goal is to refactor the geotools library into modules, allowing the jars to be used on either the classpath (Java 8) or the module path (Java 11).<br />
<br />
* [https://github.com/geotools/geotools/wiki/Restructure-GeoTools-into-Jigsaw-modules Restructure GeoTools into Jigsaw modules] (GeoTools)<br />
<br />
* Core library refactored into modules<br />
<br />
[[File:Gt-modules.png|frameless|GeoTools Java 11 modules ]]<br />
<br />
* plugins used to automatic modules to dependencies on the classpath<br />
<br />
[[File:Module-path.png|800px|module-path bridge to classpath]]<br />
<br />
In the above illustration the gt-svg module is used as an automatic module publishing org.geotools.renderer.style.svg package. It acts as a bridge to the multi-jar project batik still on the classpath, completely masking the fact batik is used used to read and render svg files. The core module gt-renderer publishes select packages for use, while hiding others. It makes use of ServiceLocator to access the IconFactory implemented by gt-svg and never has direct use of the batik implementation.<br />
<br />
For this to work the gt-svg jar has been refactored, moving the icon factory the new package org.geotools.style.svg. This was required as the package org.geotools.renderer.style was already published by gt-renderer.<br />
<br />
We expect:<br />
<br />
* Initial focus is on the core library, refactoring to allow jars to be used on the module path as named modules<br />
* plugins will remain on the classpath, accessed via service locator, any conflicting packages will not be visible to client code<br />
<br />
== JTS Topology Suite Activities ==<br />
<br />
Results of bonn code sprint:<br />
<br />
* [https://github.com/locationtech/jts/pull/274 Add module names for better Java 9/Jigsaw support] (JTS Topology Suite)<br />
<br />
JTS jars can be placed on the module-path used as an automatic module, the jars have been supplied am Automatic-Module-Name using a MANIFEST.MF entry.<br />
<br />
For an example.application using jts-core as a module add '''module-info''':<br />
<br />
module example.application {<br />
requires org.locationtech.jts; // jts-core<br />
}<br />
<br />
== GeoNetwork Planning ==<br />
<br />
[[https://github.com/geonetwork/core-geonetwork/wiki/OSGeo-Java-codesprint-2018 Strategy for GeoNetwork]]<br />
<br />
== How to sponsorship ==<br />
<br />
Contributions will be put towards travel costs for sprint participants who would be otherwise unable to attend. Any surplus at the end of the event will be turned over to OSGeo or used for a future code sprint. We have set-up the sprint to minimize travel and accommodation costs.<br />
<br />
Sponsors will receive the following benefits / honours:<br />
<br />
* Your logo at the top of this page<br />
* Mention in project communication (for example the GeoServer 2.15 release announcement)<br />
* The ability to run on a supported java platform<br />
* Our gratitude :)<br />
<br />
This event provides the following sponsorship levels:<br />
<br />
{| class="wikitable"<br />
|-<br />
| Gold<br />
| style="text-align:right;" | $2500 USD<br />
|-<br />
| Silver<br />
| style="text-align:right;" | $1500 USD<br />
|-<br />
| Bronze<br />
| style="text-align:right;" | $750 USD<br />
|-<br />
| In-Kind || colspan="3" | In-kind support graciously accepted<br />
|}<br />
<br />
This is an official OSGeo event, your contribution counts towards being recognized as an [https://www.osgeo.org/about/how-to-become-a-sponsor/ OSGeo Sponsors].<br />
<br />
For more information on sponsorship, please contact [[Jody Garnett]], [[User:Aaime|Andrea Aime]].<br />
<br />
=== How to Sponsor ===<br />
<br />
# Contact OSGeo [[Treasurer]] for details on using PayPal or to request an invoice:<br />
# The OSGeo [[Treasurer]] will contact both you and the event organizers to acknowledge your sponsorship<br />
#* Please have a logo ready for your organization if you wish to be acknowledged publicly <br />
#* Your event sponsorship, at your request, can contribute towards [http://www.osgeo.org/sponsorship being recognized] as an OSGeo Foundation sponsor<br />
<br />
=== Sponsorship Outreach ===<br />
<br />
We are reaching out to organizations to see if there is interest in sponsorship:<br />
<br />
* Prior sponsors: gaia3d, boundless, ian, geodan, how2map, fossgis, atol, geosolutions, astun<br />
* Local sponsors: astun, vivid solutions, transient software<br />
<br />
If there is a lot of local sponsorship we expect to drag the developers away from the task at hand and meet the local community (at a social evening or similar).<br />
<br />
=== OSGeo Funding Request ===<br />
<br />
The following information is requested by OSGeo Board [[Code_Sprint_Guidelines]], we provided an indication that we would be planning a sprint during the 2018 budget process.<br />
<br />
* [[Java_2018_Code_Sprint_Budget_:_Budget|Java 2018 Code Sprint Budget]]<br />
<br />
It is intended to that OSGeo be recognized as hosting this event, rather than acknowledged as a sponsor.<br />
<br />
[[Category:Code Sprints]]<br />
[[Category:Java Tribe Code Sprint]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Java_2018_Code_Sprint&diff=116756Java 2018 Code Sprint2018-09-30T03:18:44Z<p>Wiki-Surveyor: /* Participants */</p>
<hr />
<div>The Java tribe has a real challenge for 2018 - updating our open source projects for the Java roadmap.<br />
<br />
== Location ==<br />
<br />
Sprint scheduled for Q4 2018, proposed date:<br />
<br />
* October 22-26th <br />
<br />
We are looking at setting up a distributed sprint with locations in:<br />
<br />
* North America - Victoria, Boundless Office, billeting options available for those travelling<br />
* Europe - Sevilla, Spain half.confirmed. Italy or UK have been proposed, recommendations welcome!<br />
* Oceania - recommendations welcome<br />
<br />
=== Contacts ===<br />
<br />
Jody Garnett<br />
<br />
== Sponsors ==<br />
<br />
We would like to thank our sponsors!<br />
<br />
=== Gold Sponsors ===<br />
<br />
TBD<br />
<br />
=== Bronze Sponsors ===<br />
<br />
TBD<br />
<br />
=== In-Kind Support ===<br />
<br />
[[File:Boundless_Logo.png|350px|link=http://boundlessgeo.com]] [[File:GeoCat.png|350px|link=https://www.geocat.net]]<br />
<br />
== Participants ==<br />
<br />
Please add your name and the projects you are planning to sprint and note the likehood of your attendance.<br />
<br />
{| style="border: solid grey 1px; width:100%" class="sortable"<br />
|+ Participants<br />
|-<br />
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Notes || Attendance <br />
|-<br />
| 1 || [[User:Delawen|María Arias de Reyna]] || Spain || GeoCat bv || working remotely || working remotely || GeoNetwork || Notes || Partially working on the codesprint <br />
|-<br />
| 2 || [[User:Jive|Jody Garnett]] || Canada || Boundless || local || local || GeoTools || Able to host guests || Confirmed<br />
|-<br />
| 3 || [[User:Tbarsballe|Torben Barsballe]] || Canada || Boundless || local || local || GT/GS || || Confirmed<br />
|-<br />
| 4 || [[User:ksmith|Kevin Smith]] || Canada || Boundless || local || local || GT/GWC/GS || || Confirmed<br />
|-<br />
| 5 || [[User:dvntucker|Devon Tucker]] || Canada || Boundless || local || local || GT/GS || || Confirmed<br />
|-<br />
| 6 || [[User:moovida|Antonello Andrea]] || Italy || HydroloGIS || TBD || TBD || GT/JTS, Hortonmachine || || Confirmed, waiting on Europa location to be revealed :-)<br />
|-<br />
| 7 || [[User:ianturton|Ian Turton]] || UK || Astun || TBD || TBD || GT/GS || || Either Italy or remote <br />
|-<br />
| 8 || [[User:Aaime|Andrea Aime]] || Italy || GeoSolutions || TBD || TBD || GT/GWC/GS/jai-ext/imageio-ext/jaitools || || Either Italy or remote <br />
|-<br />
| 9 || [[User:jhughes|Jim Hughes]] || US || CCRi || TBD || TBD || JTS/GT/GS/GeoMesa || || Confirmed <br />
|-<br />
| 10 || [[User:Landon Blake]] || US || BKF Engineers || TBD || TBD || JTS/Proj4J || || Confirmed <br />
|}<br />
<br />
== Discussion ==<br />
<br />
=== Java has a roadmap? === <br />
<br />
Yes, we had a previous sprint focused on Java 8 compatibility, several features had changed breaking compatibility.<br />
<br />
More importantly the Java roadmap has changed to a six-month release cycle:<br />
<br />
* six month release cycle is already well underway having started with Java 9 and Java 10.<br />
<br />
* Oracle is offering three year LTS releases commercially<br />
<br />
* AdoptOpenJDK is setting up LTS releases of OpenJDK .. backed by IBM, Microsoft and others.<br />
<br />
* RedHat is focusing on LTS (skipping Java 9 and Java 10) and plans to ship OpenJDK based on Java SE 11<br />
<br />
=== Why is updating our open source projects for the Java roadmap a challenge? === <br />
<br />
- Java changed the service provider interface plugin system used by GeoTools, forcing the project to write its own replacement.<br />
<br />
- The java runtime has been broken up into modules, not all of which are activated by default. We need to review what sections of the JRE we require and ensure they are turned on.<br />
<br />
- Java introduced the module system "jigsaw" providing both a class-path and module-path for loading jars.<br />
<br />
- When loaded on the module-path jars are prevented from using the same package. This breaks multi-jar projects like GeoTools library where gt-api defining interfaces, and gt-main providing implementations.<br />
<br />
- Jigsaw also locks down aspects of Java reflection, affecting projects like Spring that make heavy use of reflection to "auto wire" GeoServer together. Spring 5 has been released and upgrading to this release will be a key focus.<br />
<br />
- With these changes projects like GeoServer need to review of hundreds open source dependencies to determine what other libraries are broken, if an update is available or replacement can be found.<br />
<br />
- The java web service framework (responsible for concepts like Servlet and Session) is being removed from Oracle oversight and has been setup as [Jakarta EE Software](https://jakarta.ee).<br />
<br />
=== Recommended reading ===<br />
<br />
* [https://www.azul.com/what-comes-after-jdk-8/ What Comes After JDK 8?]<br />
* [https://medium.com/criciumadev/its-time-migrating-to-java-11-5eb3868354f9 It's time! Migrating to Java 11] - contains working example of updating spring application<br />
* [http://openjdk.java.net/projects/jigsaw/spec/sotms The State of the Module System] / [https://www.oracle.com/corporate/features/understanding-java-9-modules.html Understanding Java 9 modules]<br />
<br />
=== Do you have any experience running sprints? === <br />
<br />
The GeoServer team really benefited from [[Java 2017 Code Sprint|java 2017 code sprint]] and is eager to repeat the success.<br />
<br />
== GeoServer Planning ==<br />
<br />
Initial planning has started:<br />
<br />
* [https://github.com/geoserver/geoserver/wiki/GSIP-171 GSIP 171 Java 18.9 Compatibility] (GeoServer)<br />
<br />
Preflight activities:<br />
<br />
* dependency audit <br />
<br />
Required updates:<br />
<br />
* Spring 5 - Older versions of spring are not compatible with Java 11. Upgrading to from Spring 4 to Spring 5 does involve handling some API changes.<br />
* HazelCast - Like Spring, HazelCast involves a lot of reflection. <br />
<br />
Module refactor:<br />
<br />
* Repackage GeoServer application jars to prevent conflicts at the package level.<br />
* Resulting application can be used on either the CLASSPATH (Java 8) or MODULEPATH (Java 11)<br />
<br />
== GeoTools Planning ==<br />
<br />
Planning and work is already well underway:<br />
<br />
* [https://github.com/geotools/geotools/wiki/Java-9-Compatibility GeoTools Java-9-Compatibility] (GeoTools)<br />
<br />
The first completed phase is to allow GeoTools to be used on the classpath:<br />
<br />
* [https://github.com/geotools/geotools/wiki/Migrate-Units-to-JSR-363 Migrate Units to JSR-363] (GeoTools)<br />
* [https://github.com/geotools/geotools/wiki/FactoryRegistry-Refactoring-for-Java-9-Compatibility FactoryRegistry Refactoring for Java 9 Compatibility] (GeoTools)<br />
<br />
The sprint goal is to refactor the geotools library into modules, allowing the jars to be used on either the classpath (Java 8) or the module path (Java 11).<br />
<br />
* [https://github.com/geotools/geotools/wiki/Restructure-GeoTools-into-Jigsaw-modules Restructure GeoTools into Jigsaw modules] (GeoTools)<br />
<br />
* Core library refactored into modules<br />
<br />
[[File:Gt-modules.png|frameless|GeoTools Java 11 modules ]]<br />
<br />
* plugins used to automatic modules to dependencies on the classpath<br />
<br />
[[File:Module-path.png|800px|module-path bridge to classpath]]<br />
<br />
In the above illustration the gt-svg module is used as an automatic module publishing org.geotools.renderer.style.svg package. It acts as a bridge to the multi-jar project batik still on the classpath, completely masking the fact batik is used used to read and render svg files. The core module gt-renderer publishes select packages for use, while hiding others. It makes use of ServiceLocator to access the IconFactory implemented by gt-svg and never has direct use of the batik implementation.<br />
<br />
For this to work the gt-svg jar has been refactored, moving the icon factory the new package org.geotools.style.svg. This was required as the package org.geotools.renderer.style was already published by gt-renderer.<br />
<br />
We expect:<br />
<br />
* Initial focus is on the core library, refactoring to allow jars to be used on the module path as named modules<br />
* plugins will remain on the classpath, accessed via service locator, any conflicting packages will not be visible to client code<br />
<br />
== JTS Topology Suite Activities ==<br />
<br />
Results of bonn code sprint:<br />
<br />
* [https://github.com/locationtech/jts/pull/274 Add module names for better Java 9/Jigsaw support] (JTS Topology Suite)<br />
<br />
JTS jars can be placed on the module-path used as an automatic module, the jars have been supplied am Automatic-Module-Name using a MANIFEST.MF entry.<br />
<br />
For an example.application using jts-core as a module add '''module-info''':<br />
<br />
module example.application {<br />
requires org.locationtech.jts; // jts-core<br />
}<br />
<br />
== GeoNetwork Planning ==<br />
<br />
[[https://github.com/geonetwork/core-geonetwork/wiki/OSGeo-Java-codesprint-2018 Strategy for GeoNetwork]]<br />
<br />
== How to sponsorship ==<br />
<br />
Contributions will be put towards travel costs for sprint participants who would be otherwise unable to attend. Any surplus at the end of the event will be turned over to OSGeo or used for a future code sprint. We have set-up the sprint to minimize travel and accommodation costs.<br />
<br />
Sponsors will receive the following benefits / honours:<br />
<br />
* Your logo at the top of this page<br />
* Mention in project communication (for example the GeoServer 2.15 release announcement)<br />
* The ability to run on a supported java platform<br />
* Our gratitude :)<br />
<br />
This event provides the following sponsorship levels:<br />
<br />
{| class="wikitable"<br />
|-<br />
| Gold<br />
| style="text-align:right;" | $2500 USD<br />
|-<br />
| Silver<br />
| style="text-align:right;" | $1500 USD<br />
|-<br />
| Bronze<br />
| style="text-align:right;" | $750 USD<br />
|-<br />
| In-Kind || colspan="3" | In-kind support graciously accepted<br />
|}<br />
<br />
This is an official OSGeo event, your contribution counts towards being recognized as an [https://www.osgeo.org/about/how-to-become-a-sponsor/ OSGeo Sponsors].<br />
<br />
For more information on sponsorship, please contact [[Jody Garnett]], [[User:Aaime|Andrea Aime]].<br />
<br />
=== How to Sponsor ===<br />
<br />
# Contact OSGeo [[Treasurer]] for details on using PayPal or to request an invoice:<br />
# The OSGeo [[Treasurer]] will contact both you and the event organizers to acknowledge your sponsorship<br />
#* Please have a logo ready for your organization if you wish to be acknowledged publicly <br />
#* Your event sponsorship, at your request, can contribute towards [http://www.osgeo.org/sponsorship being recognized] as an OSGeo Foundation sponsor<br />
<br />
=== Sponsorship Outreach ===<br />
<br />
We are reaching out to organizations to see if there is interest in sponsorship:<br />
<br />
* Prior sponsors: gaia3d, boundless, ian, geodan, how2map, fossgis, atol, geosolutions, astun<br />
* Local sponsors: astun, vivid solutions, transient software<br />
<br />
If there is a lot of local sponsorship we expect to drag the developers away from the task at hand and meet the local community (at a social evening or similar).<br />
<br />
=== OSGeo Funding Request ===<br />
<br />
The following information is requested by OSGeo Board [[Code_Sprint_Guidelines]], we provided an indication that we would be planning a sprint during the 2018 budget process.<br />
<br />
* [[Java_2018_Code_Sprint_Budget_:_Budget|Java 2018 Code Sprint Budget]]<br />
<br />
It is intended to that OSGeo be recognized as hosting this event, rather than acknowledged as a sponsor.<br />
<br />
[[Category:Code Sprints]]<br />
[[Category:Java Tribe Code Sprint]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Incubation_Committee&diff=113279Incubation Committee2018-01-19T17:56:55Z<p>Wiki-Surveyor: </p>
<hr />
<div>The project incubation committee is responsible for overseeing the incubation process for new projects entering the foundation. The incubation committee provides resources to assist new projects to reach full membership, and makes recommendations to the board when they feel projects have completed incubation.<br />
<br />
== About the Incubation Committee ==<br />
<br />
The OSGeo Incubation Committee is responsible for:<br />
<br />
# OSGeo website project review<br />
#* Reviewing applications to list projects on the OSGeo website<br />
#* Preparing and recommend criteria and review process for projects to be listed on the OSGeo website<br />
# Community project program<br />
#* Reviewing community project applications and recommending projects to the board to be accepted as community projects<br />
#* Reporting on the status of projects in the community project program to the board periodically (via Chair)<br />
#* Preparing and recommending community project process and criteria to the board.<br />
# OSGeo Incubation<br />
#* Reviewing applications for incubation and making recommendations to the board on projects that should be admitted into incubation.<br />
#* Appointing mentors for incubation projects.<br />
#* Reviewing progress of projects against incubation requirements, and recommending projects for full project status to the board, when deemed appropriate.<br />
#* Reporting on the status of projects in incubation and the incubation process to the board periodically (via Chair).<br />
#* Preparing and recommending incubation process and criteria to the board.<br />
<br />
The OSGeo incubation committee is not responsible for OSGeo Projects, who report directly to the board via their project officer.<br />
<br />
=== Committee Members ===<br />
<br />
'''Volunteers Welcome''' - if you would like to take part we are always looking for new members, sign up to the email list, and introduce yourself to volunteer.<br />
<br />
Current members:<br />
<br />
* Bruce Bannerman<br />
* Bob (CI-StPaul) Basques<br />
* Landon Blake<br />
* Howard Butler<br />
* Arnulf Christl<br />
* Jody Garnett (chair)<br />
* Dimitris Kotzinos<br />
* Tom Kralidis<br />
* Julien-Samuel Lacroix<br />
* Mark Lucas<br />
* Steve Lime<br />
* Daniel Morissette<br />
* Markus Schneider<br />
* Cameron Shorter<br />
* Norman Vine<br />
* Frank Warmerdam<br />
<br />
'''Thanks you''' - we ask that volunteers remain active, joining the discussion and voting on the email list. If you are unable to take part please send us an email. As volunteers we understand that life can get in the way of advocacy – you are welcome to rejoin at any time. We will also retire inactive members as needed. Prior members:<br />
<br />
* Robert Bray<br />
* Chris Holmes<br />
* Judit Mays<br />
* Jeff McKenna<br />
* Markus Neteler<br />
* Paul Spencer<br />
* Jeroen Ticheler<br />
<br />
=== Committee Operation ===<br />
<br />
The incubation committee operates within the OSGeo committee guidelines, operating in a close working relationship with the OSGeo board as reflected in our responsibilities above.<br />
<br />
* Voting members: Voting members are maintained on this page as outlined below. This committee is volunteer based with committee member ship driven by email request to be added or removed. Inactive members (see below) are removed as needed to preserve committee function.<br />
* Project mentors: Have volunteered to represent our organization at a personal level as a guest on the projects email list and meetings. Project mentors are responsible for recommending when a project is ready for graduation based on this first hand experience. For more information see mentor guidelines.<br />
* Committee chair: Committee chair appointed by motion, result forward to the board for approval and recognition as an officer of the foundation. Committee chair is responsible for operation of the committee.<br />
* Communication: This committee operates on the [https://lists.osgeo.org/mailman/listinfo/incubator incubator mailing list]. With the occasional breakout IRC meeting, hangout, or phone call to explore specific issues.<br />
* Decision making: Decision making is performed by email motion. Motions are held open for a two week period. Each motion requires a 50% quorum within the two week period. Voting consists of +1 (approval), +0 (slight agreement), -0 (slight disagreement), -1 (against). The committee chair is responsible for replying to the email thread with voting results and motion resolution.<br />
** Email motions should be clearly worded and have a subject line “Motion:”.<br />
** Motions are held open for a two week period to give everyone a chance to respond, this accounts for volunteers that are only available on weekends.<br />
** At discretion of the chair a motion may be held open longer than two weeks.<br />
** If a motion does not gather a 50% response within a two week period we may need to revisit our active member list – removing members that have not voted within the last year.<br />
** Voting +0 and -0 are a good way to reach quorum for volunteers that have not had a chance to follow the discussion.<br />
** There is no veto in the incubation committee, but we tend to respect -1 votes and withdraw motions that are divisive. It is noted that when reviewing graduation checklists -1 votes tend to track outstanding issues that are then addressed within the voting period.<br />
* Independence: Our mandate is focused on providing to the OSGeo board as outlined above.<br />
<br />
Example email:<br />
<br />
subject: motion: accept blink as a community project<br />
<br />
The following motion has been made by Landon Blake:<br />
<br />
Motion to accept Blink Raster as an community project.<br />
<br />
This motion is held open for two weeks closing January 29th, requiring 50% quorum,<br />
from the following incubation committee members:<br />
<br />
- Bruce Bannerman<br />
- Bob (CI-StPaul) Basques<br />
- Landon Blake +1 initial motion<br />
- Howard Butler<br />
- Arnulf Christl<br />
- Jody Garnett <br />
- Dimitris Kotzinos<br />
- Tom Kralidis<br />
- Julien-Samuel Lacroix<br />
- Mark Lucas<br />
- Steve Lime<br />
- Daniel Morissette<br />
- Markus Schneider<br />
- Cameron Shorter<br />
- Norman Vine<br />
- Frank Warmerdam<br />
<br />
A subsequent email will be sent when the motion is completed, either by the elapsed time period, or by unanimous consent before the closing period.<br />
<br />
== Documents ==<br />
<br />
* Official incubator public web page is at: http://osgeo.org/incubator/index.html (with members list).<br />
* [[Incubation FAQ]]<br />
* [[Official_IncCom_Documents]]<br />
* Incubation process docs: http://osgeo.org/incubator/process/index.html (original [[Official_IncCom_Documents|wiki draft documents]])<br />
* [[Incubation Badges]]<br />
<br />
Draft or Example Documents<br />
* Draft [[Commiter Responsibilities Guidelines]]<br />
* OSGeo Distribution and Committer [[http://www.osgeo.org/content/foundation/legal/licenses.html licenses] which can be used as is, or as an example for projects starting off with participatory open source.<br />
** Geotools Copyright Assignment ([http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.pdf pdf], [http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.odt odt]) - previous example<br />
** [[Project Copyright Assignment]] - previous example<br />
* [[Contributor Agreement]] and FAQ <br />
* [[Incubation Phases]] proposal<br />
<br />
Document Refresh 2014<br />
* [[Project Graduation Checklist]]<br />
<br />
Projects:<br />
* [[OSGeo Labs]] - for OSGeo related projects that haven't reached incubation status<br />
* List of [[Project Steering Committees]]<br />
<br />
Reference:<br />
* [[Project Infrastructure Migration]]<br />
* [http://producingoss.com/html-chunk/index.html Producing OSS] - by Karl Fogel - an excellent primer on running an FOSS project.<br />
<br />
Reports:<br />
* [[Incubation Committee Report 2012]]<br />
* [[Incubation Committee Report 2011]]<br />
<br />
Trac:<br />
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&order=priority Open Incubator Trac Issues]<br />
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&keywords=%7Eapplication&order=priority Pending Incubation Applications]<br />
<br />
Discussion:<br />
* [[5-star-rating]] - discussion about more fine incubation procedure<br />
Reference:<br />
<br />
== Meetings and Reports ==<br />
Meetings are scheduled via [http://lists.osgeo.org/mailman/listinfo/incubator Mailing List] and take place via [[Getting_Started#Jump_on_IRC | IRC]] at the times specified in the [[Foundation Calendar]].<br />
* [[IncCom Meeting1|First Meeting]] - March 13th 2006<br />
* [[IncCom Meeting2|Second Meeting]] - March 20th 2006<br />
* [[IncCom Meeting3|Third Meeting]] - March 27th 2006<br />
* [[IncCom Meeting4|Fourth Meeting]] - April 10th 2006<br />
* [[IncCom Meeting5|Fifth Meeting]] - April 24th 2006<br />
* [[IncCom Meeting6|Sixth Meeting]] - June 19th 2006<br />
* [[IncCom Meeting7|Seventh Meeting]] - August 7th 2006<br />
* [[IncCom Meeting8|Eighth Meeting]] - October 30th 2006<br />
* [[IncCom Meeting9|Nineth Meeting]] - February 12th 2007<br />
* [[IncCom Meeting10|Tenth Meeting]] - June 11th 2007<br />
* [[IncCom Meeting11|Eleventh Meeting]] - October 29th 2007 <br />
* [[IncCom Meeting12|Twelfth Meeting]] - September 8th 2008 <br />
* [[IncCom Meeting13|Thirteenth Meeting]] - October 29th 2009<br />
* [[IncCom Meeting14|Fourteenth Meeting]] - March 1th 2010<br />
* [[IncCom Meeting15]] - Nov 21 2011<br />
* [[IncCom Meeting16]] - Jan 17 2012<br />
* [[IncCom Meeting17]] - March 19 2012<br />
* [[IncCom Meeting18]] - May 21 2012<br />
* [[IncCom Meeting19]] - July 23 2012<br />
* [[IncCom Meeting20]] - Sep 24 2012<br />
* [[IncCom Meeting21]] - Feb 18 2013<br />
* [[IncCom Report22]] - 2013 Q2<br />
* [[IncCom Report23]] - 2013 Q3<br />
* [[IncCom Report24]] - 2014 Q1<br />
* [[Fall 2014 Committee Report for OSGeo Journal]]<br />
<br />
== Incubator ==<br />
<br />
The OSGeo incubation process takes place in three stages:<br />
<br />
# Initial Application<br />
# Incubation<br />
## Project Status: project details, and a few resourcing questions for the system admin committee (see [[Project Status Template]]).<br />
## Provenance Review: quick check to ensure the project is open source and has permission to distribute its source code.<br />
## Final Checklist: review the project procedures and gather requested information for OSGeo participation<br />
# Graduation<br />
<br />
The following projects are currently in OSGeo incubation. The links provided are used to track the progress of incubation projects and are used by the developer team (and OSGeo mentor). In many cases the links will take you to a project specific wiki or website in order to be closer to their target community.<br />
<br />
When projects have completed the incubation checklist their mentor will recommend them to the Incubation committee for graduation.<br />
<br />
== Projects Currently In Incubation ==<br />
=== IstSOS ===<br />
<br />
'''IstSOS''': http://wiki.osgeo.org/wiki/IstSOS<br />
# [[IstSOS Provenance Review]]<br />
# [[IstSOS Incubation Status]] <br />
# ''Mentor'': [[User: Jeff_McKenna|Jeff McKenna]]<br />
<br />
=== MetaCRS ===<br />
<br />
'''MetaCRS''': http://trac.osgeo.org/metacrs/<br />
# [[MetaCRS Incubation Status]]<br />
# no provenance review provided<br />
# no check list provided<br />
# ''Mentor'': [[User: Dmorissette|Daniel Morissette]]<br />
<br />
=== Opticks ===<br />
<br />
'''Opticks''': http://opticks.org<br />
# [[Opticks Incubation Status]]<br />
# no provenance review provided<br />
# [[Opticks Incubation Checklist]]<br />
# ''Mentor'': [[User: Mark_Lucas|Mark Lucas]]<br />
<br />
=== Oskari ===<br />
<br />
'''Oskari''': http://oskari.org/<br />
# [[Oskari Incubation Application]]<br />
# [[Oskari Incubation Status]]<br />
# ''Mentor'': [[Arnulf Christl]]<br />
<br />
=== OSGeoLive ===<br />
<br />
'''OSGeoLive''': http://live.osgeo.org<br />
# [[https://trac.osgeo.org/osgeo/ticket/2002 OSGeoLive Incubation Application]]<br />
# [[Live_GIS_Incubation_Graduation_Checklist]]<br />
# ''Mentor'': [[Jody Garnett]]<br />
<br />
=== PyWPS ===<br />
<br />
'''PyWPS''': http://pywps.org<br />
# PyWPS Application<br />
# Incubation Status<br />
# [https://github.com/geopython/pywps/wiki/ProjectGraduationChecklist PyWPS Graduation Checklist]<br />
# ''Mentor'': [[User:Tomkralidis|Tom Kralidis]]<br />
<br />
=== TEAM Engine ===<br />
<br />
'''TEAM Engine''': http://teamengine.sourceforge.net<br />
# status template not filled out<br />
# no provenance review provided<br />
# no check list provided<br />
# ''Mentor'': [[User: Jdeolive|Justin Deoliveira]]<br />
<br />
=== ZOO-Project ===<br />
<br />
'''ZOO-Project''': http://www.zoo-project.org<br />
# [[ZOO-Project_Incubation_Status]]<br />
# [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance Review]<br />
# [[ZOO-Project Incubation Checklist]]<br />
# ''Mentor'': [[User: Kotzino|Dimitris Kotzinos]]<br />
<br />
== Graduated == <br />
<br />
The following status and provenance documents are for historical purposes, and are no longer actively maintained. <br />
<br />
* Community Mapbuilder: [[Community Mapbuilder Incubation Progress]] | [[Community Mapbuilder Provenance Review]] (Entered 2006-02-04, Graduated 2006-07-14, Mentor: Steve Lime)<br />
* deegree: [[deegree Incubation Status]] | [[deegree Provenance Review]] (Entered: 2008-06-09, Graduated 2010-02-04, Mentor: Jody Garnett)<br />
* FDO: [[FDO Incubation Status]] | [[FDO Provenance Review]] (Entered 2007-03-06, Graduated 2008-02-08, Mentor: Daniel Morissette)<br />
* GEOS: [[GEOS Incubation Status]] | [[GEOS Provenance Review]] (Entered 2007-11-02, Graduated 2012-04-28, Mentor: Frank Warmerdam)<br />
* GDAL/OGR: [[GDAL Incubation Progress]] | [[GDAL Provenance Review]] (Entered 2006-02-04, Graduated 2008-02-08, Mentor: Paul Spencer)<br />
* Geomajas: [[GeoMajas Incubation Status]] | [[GeoMajas Provenance Review]] (Entered 2010-03-04, Graduated 2010-11-22, Mentor: Paul Spencer)<br />
* GeoNetwork: [[GeoNetwork Incubation Status]] | [[GeoNetwork Provenance Review]] (Entered 2006-11-10, Graduated 2008-06-21, Mentor: Jody Garnett)<br />
* GeoNode: [[GeoNode Incubation Status]] [[GeoNode Provenance Review]] [[GeoNode Incubation Checklist]] (Entered 2015-08-13, Graduated 2016-11-09, Mentor: David Bitner)<br />
* GeoMOOSE: [[GeoMoose Incubation Status]] | [[GeoMoose Provenance Review]] | [[GeoMoose Incubation Checklist]] (Entered 2011-12-08, Graduated 2013-04-19, Mentor: Jody Garnett)<br />
* GeoTools: [[GeoTools Incubation Progress]] | [[GeoTools Provenance Review]] (Entered 2006-02-27, Graduated 2008-07-18, Mentor: Cameron Shorter)<br />
* GeoServer: [http://old.geoserver.org/OSGEO%20incubation%20questionnaire.html Incubation Questionnaire] | [http://old.geoserver.org/GeoServer%20Incubation%20Status.html Incubation Status] | [https://github.com/geoserver/geoserver/wiki/GeoServer-Provenance-Review Provenance Review] | [https://github.com/geoserver/geoserver/wiki/GeoServer-Incubation-Checklist Incubation Checklist] | [[Geoserver Mentor Notes]] (Entered 2009-11-05, Graduated 2013-03-15, Mentor: Landon Blake)<br />
* gvSIG: [[gvSIG Incubation Status]] | [[gvSIG Provenance Review]] | [[gvSIG Incubation Checklist]] (Entered 2007-09-07, Graduated 2015-11-26, Mentor: Dimitris Kotzinos)<br />
* GRASS: [[GRASS Incubation Progress]] | [[GRASS Provenance Review]] (Entered 2006-02-27, Graduated 2008-02-08, Mentor: Norman Vine and Arnulf Christl)<br />
* Mapbender: [[Mapbender Incubation Progress]] | [[Mapbender Provenance Review]] (Entered 2006-02-04, Graduated 2006-07-15, Mentor: Paul Spencer)<br />
* MapFish: [[MapFish Incubation Status]] | [[MapFish Provenance Review]] (Entered 2009-11-09, Graduated 2011-09-01, Mentor: Gary Sherman)<br />
* MapGuide Open: [[MapGuide Incubation Status]] | [[MapGuide Provenance Review]] (Entered 2006-02-04, Graduated 2007-03-02, Mentor: Daniel Morissette)<br />
* MapServer: [[MapServer incubation status]] | [[MapServer Provenance Review]] (Entered 2006-02-04, Graduated 2008-12-16, Mentor: Chris Holmes)<br />
* Marble: [[Marble Incubation Status]] | [[Marble Code Provenance Review]] | [[Marble Graduation Checklist]] (Entered 2012-10-12, Graduated 2013-10-17, Mentor: Arnulf Christl)<br />
* OpenLayers: [[OpenLayers Incubation Status]] | [[OpenLayers Provenance Review]] (Entered 2006-11-10, Graduated 2007-11-16, Mentor: Howard Butler)<br />
* Orfeo ToolBox (OTB): [[OTB Project Incubation Status]] | [[OTB Code Provenance Review]] (Entered 2009-10-26, Graduated 2017-07-20, Mentor: Landon Blake)<br />
* PostGIS: [[PostGIS Incubation Status]] | [[PostGIS Provenance Review]] (Entered 2009-08-06, Graduated 2012-06-07, Mentor: Arnulf Christl)<br />
* pycsw: [https://github.com/geopython/pycsw/wiki/Project-Status Incubation Status] | [https://github.com/geopython/pycsw/wiki/Project-Graduation-Checklist Graduation Checklist] | [https://github.com/geopython/pycsw/wiki/pycsw-Provenance-Review Provenance Review] (Entered 2013-03-30, Graduated 2015-03-05, Mentor: Jeff McKenna)<br />
* OSSIM: [[OSSIM incubation status]] | [http://trac.osgeo.org/ossim/wiki/ossimprovenance OSSIM Provenance Review] (Entered 2006-02-27, Graduated 2009-06-02, Mentor: Richard Gould)<br />
* QGIS: [[QGIS Incubation Status]] | [[QGIS Provenance Review]] (Entered 2007-03-02, Graduated 2008-03-14, Mentor: Bob Bray)<br />
<br />
The initial projects to go through the incubation process helped define what is required. The above pages tracked the progress (and capture the experience) of these projects.<br />
<br />
== Withdrawn == <br />
<br />
The following projects did not complete incubation:<br />
<br />
* '''[http://www.rasdaman.org rasdaman]''': : [[ rasdaman Incubation Status ]] | [http://rasdaman.org/wiki/OSGeoCodeProvenance Code Provenance] | [http://www.rasdaman.org/wiki/OSGeoIncubationChecklist Incubation Checklist] (Mentor [[User: Bruce.bannerman|Bruce Bannerman]] )<br />
<br />
==OSGeo Community Projects==<br />
The Incubation Committee also assists [https://wiki.osgeo.org/wiki/OSGeo_Community_Projects OSGeo Community Projects]. <br />
<br />
[[Category:Incubation]]<br />
[[Category:Committees]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Community_Projects&diff=113278OSGeo Community Projects2018-01-19T17:53:48Z<p>Wiki-Surveyor: </p>
<hr />
<div>== About OSGeo Community Projects==<br />
OSGeo Community Projects are software projects that:<br />
<br />
* Have an open source license.<br />
* Welcome new contributors.<br />
* Are in the process of building their developer and user communities.<br />
* Are in the process of working on project governance, documentation, and marketing.<br />
<br />
OSGeo Community Projects may not yet have an active developer and user community. They may be benevolent dictatorships or feature experimental and unstable technology.<br />
<br />
==How OSGeo Community Projects Are Related To OSGeo Incubation==<br />
There are two ways for an open source software project to join OSGeo. The first way is through the regular incubation process. This is best for projects that already have an established community of developers and users. (This community should be diverse. This means that developers should come from more than one organization or group.)<br />
<br />
If a project doesn't yet have an active and diverse community, it can join OSGeo as an OSGeo Community Project. OSGeo Community Projects get help from the incubation committee with things like choosing an open source license, setting up project governance, promoting the project, and building the project community).<br />
<br />
The same volunteers that help software projects through the OSGeo Incubation Process also help OSGeo Community Projects.<br />
<br />
== Purpose ==<br />
<br />
The purpose of OSGeo Community Projects is to provide a home at OSGeo for projects that don't qualify for our normal incubation process. This allows them to get help from the volunteers on the OSGeo Incubation Committee and to become familiar with the guidelines and operation of OSGeo as an organization. Most OSGeo Community Projects are working to qualify for the normal incubation process, but this isn't a requirement.<br />
<br />
The normal OSGeo incubation process requires that software projects meet a high standard for things like project governance. Working through the normal incubation process can involve a lot of work. in contrast, we want the process to become and OSGeo Community Project to be as painless as possible. That allows projects to build community strength before they enter incubation.<br />
<br />
==Qualifying As An OSGeo Community Project==<br />
<br />
We would like to make joining OSGeo as an OSGeo Community Project as simple and painless as possible. If you would like your software project to become an OSGeo Community Project, please send a description of your project to the [http://lists.osgeo.org/mailman/listinfo/incubator OSGeo Incubation Committee Mailing List], or [mailto:sunburned.surveyor@gmail.com e-mail Landon Blake.]<br />
<br />
Your software project needs to meet the following criteria to be a OSGeo Community Project:<br />
<br />
# The technology in your software project should be geospatial (or directly support geospatial applications).<br />
# Your project should be open source and welcomes new contributions. If you don't have a license selected, we can help with that.<br />
<br />
==Getting Started==<br />
Once your software project has been accepted as an OSGeo Community Project, the Incubation Committee will assign you personal mentor. This mentor will help your project withcommunity building and other tasks. First steps for an OSGeo Community Project include:<br />
<br />
# Creation a home page for the project. The OSGeo wiki is recommended for this page. <br />
# Selection of an open source license (if the project hasn't already done this).<br />
# Announcement and discussion of the project on the [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss] OSGeo Discussion mailing list.<br />
# Set-up of project infrastructure (mailing list, source code repository, doc repository).<br />
# Creation of plans for software development, marketing and documentation.<br />
<br />
== Member Projects ==<br />
<br />
The following projects are listed with the community projects [[Category:OSGeo Labs|program]]:<br />
<br />
* [[Geoinformatica]]<br />
* [[GeoWebCache]]<br />
* [[pgRouting]]<br />
* [[Postal Address Geo-Coder]]<br />
* [[MapProxy]]<br />
* [[Virtual Terrain Project]]<br />
* [[Proj4php]]<br />
<br />
==Member Project History==<br />
The following projects have now graduated from incubation:<br />
* [[pycsw]]<br />
<br />
There is an archive of the old OSGeo Technology Projects page at [[OSGeo Labs Page Archive]].<br />
<br />
== Volunteers Needed ==<br />
Please let us know on the [https://lists.osgeo.org/mailman/listinfo/incubator Incubation Committee Mailing List] if you would like to help with OSGeo Community Projects. Here is the type of help we need:<br />
* Project marketing.<br />
* Development of user and programmer communities.<br />
* Establishment of programs and policies for project documentation, copyright assignment, and licensing.<br />
* Establishment of programs and policies for software development. This includes version tracking, bug tracking, and feature request tracking, creation of a development road map, and organization of code sprints/events.<br />
* Establishment of project governance programs and policies.<br />
* Collaboration on technical standards, data formats, and code sharing with other open source geospatial software projects.<br />
* Utilization of software development infrastructure like mailing lists, bug trackers, version control software/hosting, and web hosting.<br />
<br />
== OSGeo Community Projects Checklist ==<br />
This will be coming soon!<br />
<br />
== OSGeo Community Project Stages==<br />
OSGeo Comminity Projects are assigned a "stage" that helps interested developers and users understand their maturity. Here are the different stages, in a profession from least mature to most mature:<br />
<br />
* '''Research Project''': This project is in the conceptual stage. There may be some source code written, but it is incomplete or very experiemental. The project may lack deliverables, community support, project infrastructure, project governance, community activity, or marketing and outreach.<br />
<br />
* '''New Project''': This project is moving beyond the conceptual stage with some concrete code. However the code is still experimental and isn't stable. Projects at this status level could still experience a lot of change in their code base. This project should start to have some project infrastructure and some basic documentation.<br />
<br />
* '''Stable Project''': This project has functional source code, although it may not be "mature and feature rich". For example, the code may only be usable as a programming library or a command line tool instead of featuring a GUI. The project has started to support users and programmers with communication tools, trackers, and documentation. The project has started to think about project governance and marketing, perhaps creating plans in these areas that are not fully implemented.<br />
<br />
* '''Established Project''': This project has a usable and user friendly deliverable, like an executable program or a stable and well-deocumented programming library. The project is supporting users and programmers with communication tools, trackers, and documentation. It has started the initial phases of incubation. This includes addressing issues of copyright, licensing, and project governance. The project also has a marketing and community growth plan and has started to implement the plan.<br />
<br />
==Available Branding==<br />
Once they are approved by the Incubation Committee, OSGeo Community Projects can use the following logo:<br />
https://wiki.osgeo.org/wiki/File:OSGeo_community.png</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Community_Projects&diff=113277OSGeo Community Projects2018-01-19T17:51:44Z<p>Wiki-Surveyor: </p>
<hr />
<div>== About OSGeo Community Projects==<br />
OSGeo Community Projects are software projects that:<br />
<br />
* Have an open source license.<br />
* Welcome new contributors.<br />
* Are in the process of building their developer and user communities.<br />
* Are in the process of working on project governance, documentation, and marketing.<br />
<br />
OSGeo Community Projects may not yet have an active developer and user community. They may be benevolent dictatorships or feature experimental and unstable technology.<br />
<br />
==How OSGeo Community Projects Are Related To OSGeo Incubation==<br />
There are two ways for an open source software project to join OSGeo. The first way is through the regular incubation process. This is best for projects that already have an established community of developers and users. (This community should be diverse. This means that developers should come from more than one organization or group.)<br />
<br />
If a project doesn't yet have an active and diverse community, it can join OSGeo as an OSGeo Community Project. OSGeo Community Projects get help from the incubation committee with things like choosing an open source license, setting up project governance, promoting the project, and building the project community).<br />
<br />
The same volunteers that help software projects through the OSGeo Incubation Process also help OSGeo Community Projects.<br />
<br />
== Purpose ==<br />
<br />
The purpose of OSGeo Community Projects is to provide a home at OSGeo for projects that don't qualify for our normal incubation process. This allows them to get help from the volunteers on the OSGeo Incubation Committee and to become familiar with the guidelines and operation of OSGeo as an organization. Most OSGeo Community Projects are working to qualify for the normal incubation process, but this isn't a requirement.<br />
<br />
The normal OSGeo incubation process requires that software projects meet a high standard for things like project governance. Working through the normal incubation process can involve a lot of work. in contrast, we want the process to become and OSGeo Community Project to be as painless as possible. That allows projects to build community strength before they enter incubation.<br />
<br />
==Qualifying As An OSGeo Community Project==<br />
<br />
We would like to make joining OSGeo as an OSGeo Community Project as simple and painless as possible. If you would like your software project to become an OSGeo Community Project, please send a description of your project to the [http://lists.osgeo.org/mailman/listinfo/incubator OSGeo Incubation Committee Mailing List], or [mailto:sunburned.surveyor@gmail.com e-mail Landon Blake.]<br />
<br />
Your software project needs to meet the following criteria to be a OSGeo Community Project:<br />
<br />
# The technology in your software project should be geospatial (or directly support geospatial applications).<br />
# Your project should be open source and welcomes new contributions. If you don't have a license selected, we can help with that.<br />
<br />
==Getting Started==<br />
Once your software project has been accepted as an OSGeo Community Project, the Incubation Committee will assign you personal mentor. This mentor will help your project withcommunity building and other tasks. First steps for an OSGeo Community Project include:<br />
<br />
# Creation a home page for the project. The OSGeo wiki is recommended for this page. <br />
# Selection of an open source license (if the project hasn't already done this).<br />
# Announcement and discussion of the project on the [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss] OSGeo Discussion mailing list.<br />
# Set-up of project infrastructure (mailing list, source code repository, doc repository).<br />
# Creation of plans for software development, marketing and documentation.<br />
<br />
== Member Projects ==<br />
<br />
The following projects are listed with the community projects [[Category:OSGeo Labs|program]]:<br />
<br />
* [[Geoinformatica]]<br />
* [[GeoWebCache]]<br />
* [[pgRouting]]<br />
* [[Postal Address Geo-Coder]]<br />
* [[MapProxy]]<br />
* [[Virtual Terrain Project]]<br />
* [[Proj4php]]<br />
<br />
==Member Project History==<br />
The following projects have now graduated from incubation:<br />
* [[pycsw]]<br />
<br />
There is an archive of the old OSGeo Technology Projects page at [[OSGeo Labs Page Archive]].<br />
<br />
== Volunteers Needed ==<br />
Please let us know on the Incubation Committee Mailing List if you would like to help with OSGeo Community Projects. Here is the type of help we need:<br />
* Project marketing.<br />
* Development of user and programmer communities.<br />
* Establishment of programs and policies for project documentation, copyright assignment, and licensing.<br />
* Establishment of programs and policies for software development. This includes version tracking, bug tracking, and feature request tracking, creation of a development road map, and organization of code sprints/events.<br />
* Establishment of project governance programs and policies.<br />
* Collaboration on technical standards, data formats, and code sharing with other open source geospatial software projects.<br />
* Utilization of software development infrastructure like mailing lists, bug trackers, version control software/hosting, and web hosting.<br />
<br />
== OSGeo Community Projects Checklist ==<br />
This will be coming soon!<br />
<br />
== OSGeo Community Project Stages==<br />
OSGeo Comminity Projects are assigned a "stage" that helps interested developers and users understand their maturity. Here are the different stages, in a profession from least mature to most mature:<br />
<br />
* '''Research Project''': This project is in the conceptual stage. There may be some source code written, but it is incomplete or very experiemental. The project may lack deliverables, community support, project infrastructure, project governance, community activity, or marketing and outreach.<br />
<br />
* '''New Project''': This project is moving beyond the conceptual stage with some concrete code. However the code is still experimental and isn't stable. Projects at this status level could still experience a lot of change in their code base. This project should start to have some project infrastructure and some basic documentation.<br />
<br />
* '''Stable Project''': This project has functional source code, although it may not be "mature and feature rich". For example, the code may only be usable as a programming library or a command line tool instead of featuring a GUI. The project has started to support users and programmers with communication tools, trackers, and documentation. The project has started to think about project governance and marketing, perhaps creating plans in these areas that are not fully implemented.<br />
<br />
* '''Established Project''': This project has a usable and user friendly deliverable, like an executable program or a stable and well-deocumented programming library. The project is supporting users and programmers with communication tools, trackers, and documentation. It has started the initial phases of incubation. This includes addressing issues of copyright, licensing, and project governance. The project also has a marketing and community growth plan and has started to implement the plan.</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Community_Projects&diff=113276OSGeo Community Projects2018-01-19T17:48:30Z<p>Wiki-Surveyor: </p>
<hr />
<div>== About OSGeo Community Projects==<br />
OSGeo Community Projects are software projects that:<br />
<br />
* Have an open source license.<br />
* Welcome new contributors.<br />
* Are in the process of building their developer and user communities.<br />
* Are in the process of working on project governance, documentation, and marketing.<br />
<br />
OSGeo Community Projects may not yet have an active developer and user community. They may be benevolent dictatorships or feature experimental and unstable technology.<br />
<br />
==How OSGeo Community Projects Are Related To OSGeo Incubation==<br />
There are two ways for an open source software project to join OSGeo. The first way is through the regular incubation process. This is best for projects that already have an established community of developers and users. (This community should be diverse. This means that developers should come from more than one organization or group.)<br />
<br />
If a project doesn't yet have an active and diverse community, it can join OSGeo as an OSGeo Community Project. OSGeo Community Projects get help from the incubation committee with things like choosing an open source license, setting up project governance, promoting the project, and building the project community).<br />
<br />
The same volunteers that help software projects through the OSGeo Incubation Process also help OSGeo Community Projects.<br />
<br />
== Purpose ==<br />
<br />
The purpose of OSGeo Community Projects is to provide a home at OSGeo for projects that don't qualify for our normal incubation process. This allows them to get help from the volunteers on the OSGeo Incubation Committee and to become familiar with the guidelines and operation of OSGeo as an organization. Most OSGeo Community Projects are working to qualify for the normal incubation process, but this isn't a requirement.<br />
<br />
The normal OSGeo incubation process requires that software projects meet a high standard for things like project governance. Working through the normal incubation process can involve a lot of work. in contrast, we want the process to become and OSGeo Community Project to be as painless as possible. That allows projects to build community strength before they enter incubation.<br />
<br />
==Qualifying As An OSGeo Community Project==<br />
<br />
We would like to make joining OSGeo as an OSGeo Community Project as simple and painless as possible. If you would like your software project to become an OSGeo Community Project, please send a description of your project to the [http://lists.osgeo.org/mailman/listinfo/incubator OSGeo Incubation Committee Mailing List], or [mailto:sunburned.surveyor@gmail.com e-mail Landon Blake.]<br />
<br />
Your software project needs to meet the following criteria to be a OSGeo Community Project:<br />
<br />
# The technology in your software project should be geospatial (or directly support geospatial applications).<br />
# Your project should be open source and welcomes new contributions. If you don't have a license selected, we can help with that.<br />
<br />
==Getting Started==<br />
Once your software project has been accepted as an OSGeo Community Project, the Incubation Committee will assign you personal mentor. This mentor will help your project withcommunity building and other tasks. First steps for an OSGeo Community Project include:<br />
<br />
# Creation a home page for the project. The OSGeo wiki is recommended for this page. <br />
# Selection of an open source license (if the project hasn't already done this).<br />
# Announcement and discussion of the project on the [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss] OSGeo Discussion mailing list.<br />
# Set-up of project infrastructure (mailing list, source code repository, doc repository).<br />
# Creation of plans for software development, marketing and documentation.<br />
<br />
== Member Projects ==<br />
<br />
The following projects are listed with the community projects [[Category:OSGeo Labs|program]]:<br />
<br />
* [[Geoinformatica]]<br />
* [[GeoWebCache]]<br />
* [[pgRouting]]<br />
* [[Postal Address Geo-Coder]]<br />
* [[MapProxy]]<br />
* [[Virtual Terrain Project]]<br />
* [[Proj4php]]<br />
<br />
==Member Project History==<br />
The following projects have now graduated from incubation:<br />
* [[pycsw]]<br />
<br />
There is an archive of the old OSGeo Technology Projects page at [[OSGeo Labs Page Archive]].<br />
<br />
=== Comparison with Incubation ===<br />
<br />
As shown below there is some overlap requirements for an OSGeo projects (as defined by the [http://www.osgeo.org/incubator/process/project_graduation_checklist.html incubation process] graduation checklist).<br />
<br />
{| class="wikitable"<br />
! scope="col" width="310" style="text-align: center; font-weight: bold;" | Responsibility<br />
! scope="col" width="155" style="text-align: center; font-weight: bold;" | OSGeo Community<br />
! scope="col" width="155" style="text-align: center; font-weight: bold;" | OSGeo Project<br />
|-<br />
| Open Source<br /><br />
- check headers<br /><br />
- See LICENSE.md<br />
| X<br />
| X<br />
|-<br />
| Participatory<br /><br />
- See CONTRIBUTING.md<br />
| X<br />
| X<br />
|-<br />
| Open Community<br /><br />
- communication channel<br /><br />
- decision making process<br />
| <br />
| X<br />
|-<br />
| Active Healthy Community<br /><br />
- user and developer collaboration<br /><br />
- long term viability<br />
| <br />
| X<br />
|-<br />
| Development Process<br /><br />
- version control<br /><br />
- issue tracker<br /><br />
- leadership open to new members<br /><br />
- transparent decision making<br />
| <br />
| X<br />
|-<br />
| Documentation<br /><br />
- user documentation<br /><br />
- developer documentation<br />
| <br />
| X<br />
|-<br />
| Release Procedure<br /><br />
- release process<br /><br />
- documented testing process<br /><br />
| <br />
| X<br />
|-<br />
| style="font-weight: bold;" | Foundation Resources<br />
| style="font-weight: bold;" | Technology<br />
| style="font-weight: bold;" | Project<br />
|-<br />
| Representation<br /><br />
| incubation chair<br /><br />
| project officer<br />
|-<br />
| infrastructure and facilities<br />
| X<br />
| X<br />
|-<br />
| promotion & marketing<br />
| X<br />
| X<br />
|-<br />
| budget and fundraising<br />
| X<br />
| X<br />
|}<br />
<br />
Available branding:<br />
<br />
{| class="wikitable"<br />
! scope="col" width="310" style="text-align: center; font-weight: bold;" | Community<br />
! scope="col" width="310" style="text-align: center; font-weight: bold;" | Project<br />
|-<br />
| [[File:OSGeo community.png|frameless|OSGeo Community Project]]<br />
| [[File:OSGeo project.png|frameless|OSGeo Project]]<br />
|}<br />
<br />
== Volunteers Needed ==<br />
<br />
Assisting new projects is the responsibility of the incubation committee. If you are passionate about open source, helping development teams and making OSGeo great - we would love to hear from you!<br />
<br />
As a volunteer you can help new projects with:<br />
<br />
* Project marketing.<br />
* Development of user and programmer communities.<br />
* Establishment of programs and policies for project documentation, copyright assignment, and licensing.<br />
* Establishment of programs and policies for software development. This includes version tracking, bug tracking, and feature request tracking, creation of a development road map, and organization of code sprints/events.<br />
* Establishment of project governance programs and policies.<br />
* Collaboration on technical standards, data formats, and code sharing with other open source geospatial software projects.<br />
* Utilization of software development infrastructure like mailing lists, bug trackers, version control software/hosting, and web hosting.<br />
* Mentor projects entering the OSGeo incubation program<br />
<br />
== How good is my project ==<br />
<br />
While this can serve as a useful exercise for projects seeking to improve their game (and may be useful to incubation mentors) please note that it is only an exercise. You may also consider looking at [https://www.openhub.net/orgs/OSGeo Open HUB metrics] as used by OSGeo Live (and are impartially calculated based on commit history).<br />
<br />
In the past OSGeo Labs used an informal “project status” system to assist programmers and users evaluate projects under development.<br />
<br />
# Source Code Completeness<br />
# Source Code Stability<br />
# Community Support (Mailing Lists, Documentation, Tutorials)<br />
# Project Deliverables (Programming Libraries and/or Executables)<br />
# Project Infrastructure (Source Code Versioning, Bug Trackers, Feature Trackers, Web Site, Mailing Lists, Discussion Forums)<br />
# Project Governance (Decision Making Processes, Licensing, Copyright Assignment, Release Schedule, Coding Standards)<br />
# Community Activity<br />
# Marketing and Outreach<br />
<br />
Here is what that ended up looking like:<br />
<br />
* '''RnD Project''': This project is in the conceptual stage. There may be some source code written, but it is incomplete or very experiemental. The project may lack deliverables, community support, project infrastructure, project governance, community activity, or marketing and outreach.<br />
<br />
* '''New Project''': This project is moving beyond the conceptual stage with some concrete code. However the code is still experimental and isn't stable. Projects at this status level could still experience a lot of change in their code base. This project should start to have some project infrastructure and some basic documentation.<br />
<br />
* '''Stable Project''': This project has functional source code, although it may not be "mature and feature rich". For example, the code may only be usable as a programming library or a command line tool instead of featuring a GUI. The project has started to support users and programmers with communication tools, trackers, and documentation. The project has started to think about project governance and marketing, perhaps creating plans in these areas that are not fully implemented.<br />
<br />
* '''Established Project''': This project has a usable and user friendly deliverable, like an executable program or a stable and well-deocumented programming library. The project is supporting users and programmers with communication tools, trackers, and documentation. It has started the initial phases of incubation. This includes addressing issues of copyright, licensing, and project governance. The project also has a marketing and community growth plan and has started to implement the plan.</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Community_Projects&diff=113275OSGeo Community Projects2018-01-19T17:42:13Z<p>Wiki-Surveyor: </p>
<hr />
<div>== About OSGeo Community Projects==<br />
OSGeo Community Projects are software projects that:<br />
<br />
* Have an open source license.<br />
* Welcome new contributors.<br />
* Are in the process of building their developer and user communities.<br />
* Are in the process of working on project governance, documentation, and marketing.<br />
<br />
OSGeo Community Projects may not yet have an active developer and user community. They may be benevolent dictatorships or feature experimental and unstable technology.<br />
<br />
==How OSGeo Community Projects Are Related To OSGeo Incubation==<br />
There are two ways for an open source software project to join OSGeo. The first way is through the regular incubation process. This is best for projects that already have an established community of developers and users. (This community should be diverse. This means that developers should come from more than one organization or group.)<br />
<br />
If a project doesn't yet have an active and diverse community, it can join OSGeo as an OSGeo Community Project. OSGeo Community Projects get help from the incubation committee with things like choosing an open source license, setting up project governance, promoting the project, and building the project community).<br />
<br />
The same volunteers that help software projects through the OSGeo Incubation Process also help OSGeo Community Projects.<br />
<br />
== Purpose ==<br />
<br />
The purpose of OSGeo Community Projects is to provide a home at OSGeo for projects that don't qualify for our normal incubation process. This allows them to get help from the volunteers on the OSGeo Incubation Committee and to become familiar with the guidelines and operation of OSGeo as an organization. Most OSGeo Community Projects are working to qualify for the normal incubation process, but this isn't a requirement.<br />
<br />
The normal OSGeo incubation process requires that software projects meet a high standard for things like project governance. Working through the normal incubation process can involve a lot of work. in contrast, we want the process to become and OSGeo Community Project to be as painless as possible. That allows projects to build community strength before they enter incubation.<br />
<br />
==Qualifying As An OSGeo Community Project==<br />
<br />
We would like to make joining OSGeo as simple and painless as possible. If you wish to join the foundation please send a description of your project to the [http://lists.osgeo.org/mailman/listinfo/incubator OSGeo Incubation Committee Mailing List], or [mailto:sunburned.surveyor@gmail.com e-mail Landon Blake.]<br />
<br />
You will need to put in a little bit of effort (checking your license, source code and repository) before you can be listed. We will be happy to help answer any questions you have, but we do not have volunteers standing by to do this work for you.<br />
<br />
If your project would like to join OSGeo the technology initiative asks:<br />
<br />
# That your project is geospatial (or directly supports geospatial applications);<br />
#* Data & doc projects would of course need an appropriate data or documentation license<br />
# That your project is open source<br />
#* Uses an OSI approved open source license<br />
#* That you know where your source code came from, and that care is taken when accepting external contributions<br />
# Participatory (accepts pull-requests)<br />
<br />
===Getting Started===<br />
<br />
If you need assistance meeting the criteria to be listed please ask for direction and help on the mailing list:<br />
<br />
# Selection of an open source license if the project hasn't already done so.<br />
# Checking your source code headers and history<br />
# Setup appropriate LICENSE, CONTRIBUTING and README files (for github projects)<br />
<br />
Once you have been accepted as an OSGeo Technology Project we would be pleased to help you with the next steps:<br />
<br />
# Creation a home page for the project. The OSGeo wiki is recommended for this page. <br />
# Announce and discuss the project on the [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss] email list.<br />
# Set the project software development up on the OSGeo infrastructure if appropriate (mailing lists, ec...).<br />
<br />
== Member Projects ==<br />
<br />
The following projects are listed with the community projects [[Category:OSGeo Labs|program]]:<br />
<br />
* [[Geoinformatica]]<br />
* [[GeoWebCache]]<br />
* [[pgRouting]]<br />
* [[Postal Address Geo-Coder]]<br />
* [[MapProxy]]<br />
* [[Virtual Terrain Project]]<br />
* [[Proj4php]]<br />
<br />
==Member Project History==<br />
The following projects have now graduated from incubation:<br />
* [[pycsw]]<br />
<br />
There is an archive of the old OSGeo Technology Projects page at [[OSGeo Labs Page Archive]].<br />
<br />
=== Comparison with Incubation ===<br />
<br />
As shown below there is some overlap requirements for an OSGeo projects (as defined by the [http://www.osgeo.org/incubator/process/project_graduation_checklist.html incubation process] graduation checklist).<br />
<br />
{| class="wikitable"<br />
! scope="col" width="310" style="text-align: center; font-weight: bold;" | Responsibility<br />
! scope="col" width="155" style="text-align: center; font-weight: bold;" | OSGeo Community<br />
! scope="col" width="155" style="text-align: center; font-weight: bold;" | OSGeo Project<br />
|-<br />
| Open Source<br /><br />
- check headers<br /><br />
- See LICENSE.md<br />
| X<br />
| X<br />
|-<br />
| Participatory<br /><br />
- See CONTRIBUTING.md<br />
| X<br />
| X<br />
|-<br />
| Open Community<br /><br />
- communication channel<br /><br />
- decision making process<br />
| <br />
| X<br />
|-<br />
| Active Healthy Community<br /><br />
- user and developer collaboration<br /><br />
- long term viability<br />
| <br />
| X<br />
|-<br />
| Development Process<br /><br />
- version control<br /><br />
- issue tracker<br /><br />
- leadership open to new members<br /><br />
- transparent decision making<br />
| <br />
| X<br />
|-<br />
| Documentation<br /><br />
- user documentation<br /><br />
- developer documentation<br />
| <br />
| X<br />
|-<br />
| Release Procedure<br /><br />
- release process<br /><br />
- documented testing process<br /><br />
| <br />
| X<br />
|-<br />
| style="font-weight: bold;" | Foundation Resources<br />
| style="font-weight: bold;" | Technology<br />
| style="font-weight: bold;" | Project<br />
|-<br />
| Representation<br /><br />
| incubation chair<br /><br />
| project officer<br />
|-<br />
| infrastructure and facilities<br />
| X<br />
| X<br />
|-<br />
| promotion & marketing<br />
| X<br />
| X<br />
|-<br />
| budget and fundraising<br />
| X<br />
| X<br />
|}<br />
<br />
Available branding:<br />
<br />
{| class="wikitable"<br />
! scope="col" width="310" style="text-align: center; font-weight: bold;" | Community<br />
! scope="col" width="310" style="text-align: center; font-weight: bold;" | Project<br />
|-<br />
| [[File:OSGeo community.png|frameless|OSGeo Community Project]]<br />
| [[File:OSGeo project.png|frameless|OSGeo Project]]<br />
|}<br />
<br />
== Volunteers Needed ==<br />
<br />
Assisting new projects is the responsibility of the incubation committee. If you are passionate about open source, helping development teams and making OSGeo great - we would love to hear from you!<br />
<br />
As a volunteer you can help new projects with:<br />
<br />
* Project marketing.<br />
* Development of user and programmer communities.<br />
* Establishment of programs and policies for project documentation, copyright assignment, and licensing.<br />
* Establishment of programs and policies for software development. This includes version tracking, bug tracking, and feature request tracking, creation of a development road map, and organization of code sprints/events.<br />
* Establishment of project governance programs and policies.<br />
* Collaboration on technical standards, data formats, and code sharing with other open source geospatial software projects.<br />
* Utilization of software development infrastructure like mailing lists, bug trackers, version control software/hosting, and web hosting.<br />
* Mentor projects entering the OSGeo incubation program<br />
<br />
== How good is my project ==<br />
<br />
While this can serve as a useful exercise for projects seeking to improve their game (and may be useful to incubation mentors) please note that it is only an exercise. You may also consider looking at [https://www.openhub.net/orgs/OSGeo Open HUB metrics] as used by OSGeo Live (and are impartially calculated based on commit history).<br />
<br />
In the past OSGeo Labs used an informal “project status” system to assist programmers and users evaluate projects under development.<br />
<br />
# Source Code Completeness<br />
# Source Code Stability<br />
# Community Support (Mailing Lists, Documentation, Tutorials)<br />
# Project Deliverables (Programming Libraries and/or Executables)<br />
# Project Infrastructure (Source Code Versioning, Bug Trackers, Feature Trackers, Web Site, Mailing Lists, Discussion Forums)<br />
# Project Governance (Decision Making Processes, Licensing, Copyright Assignment, Release Schedule, Coding Standards)<br />
# Community Activity<br />
# Marketing and Outreach<br />
<br />
Here is what that ended up looking like:<br />
<br />
* '''RnD Project''': This project is in the conceptual stage. There may be some source code written, but it is incomplete or very experiemental. The project may lack deliverables, community support, project infrastructure, project governance, community activity, or marketing and outreach.<br />
<br />
* '''New Project''': This project is moving beyond the conceptual stage with some concrete code. However the code is still experimental and isn't stable. Projects at this status level could still experience a lot of change in their code base. This project should start to have some project infrastructure and some basic documentation.<br />
<br />
* '''Stable Project''': This project has functional source code, although it may not be "mature and feature rich". For example, the code may only be usable as a programming library or a command line tool instead of featuring a GUI. The project has started to support users and programmers with communication tools, trackers, and documentation. The project has started to think about project governance and marketing, perhaps creating plans in these areas that are not fully implemented.<br />
<br />
* '''Established Project''': This project has a usable and user friendly deliverable, like an executable program or a stable and well-deocumented programming library. The project is supporting users and programmers with communication tools, trackers, and documentation. It has started the initial phases of incubation. This includes addressing issues of copyright, licensing, and project governance. The project also has a marketing and community growth plan and has started to implement the plan.</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Incubation_Committee&diff=113274Incubation Committee2018-01-19T17:27:04Z<p>Wiki-Surveyor: </p>
<hr />
<div>The project incubation committee is responsible for overseeing the incubation process for new projects entering the foundation. The incubation committee provides resources to assist new projects to reach full membership, and makes recommendations to the board when they feel projects have completed incubation.<br />
<br />
== About the Incubation Committee ==<br />
<br />
The OSGeo Incubation Committee is responsible for:<br />
<br />
# OSGeo website project review<br />
#* Reviewing applications to list projects on the OSGeo website<br />
#* Preparing and recommend criteria and review process for projects to be listed on the OSGeo website<br />
# Community project program<br />
#* Reviewing community project applications and recommending projects to the board to be accepted as community projects<br />
#* Reporting on the status of projects in the community project program to the board periodically (via Chair)<br />
#* Preparing and recommending community project process and criteria to the board.<br />
# OSGeo Incubation<br />
#* Reviewing applications for incubation and making recommendations to the board on projects that should be admitted into incubation.<br />
#* Appointing mentors for incubation projects.<br />
#* Reviewing progress of projects against incubation requirements, and recommending projects for full project status to the board, when deemed appropriate.<br />
#* Reporting on the status of projects in incubation and the incubation process to the board periodically (via Chair).<br />
#* Preparing and recommending incubation process and criteria to the board.<br />
<br />
The OSGeo incubation committee is not responsible for OSGeo Projects, who report directly to the board via their project officer.<br />
<br />
=== Committee Members ===<br />
<br />
'''Volunteers Welcome''' - if you would like to take part we are always looking for new members, sign up to the email list, and introduce yourself to volunteer.<br />
<br />
Current members:<br />
<br />
* Bruce Bannerman<br />
* Bob (CI-StPaul) Basques<br />
* Landon Blake<br />
* Howard Butler<br />
* Arnulf Christl<br />
* Jody Garnett (chair)<br />
* Dimitris Kotzinos<br />
* Tom Kralidis<br />
* Julien-Samuel Lacroix<br />
* Mark Lucas<br />
* Steve Lime<br />
* Daniel Morissette<br />
* Markus Schneider<br />
* Cameron Shorter<br />
* Norman Vine<br />
* Frank Warmerdam<br />
<br />
'''Thanks you''' - we ask that volunteers remain active, joining the discussion and voting on the email list. If you are unable to take part please send us an email. As volunteers we understand that life can get in the way of advocacy – you are welcome to rejoin at any time. We will also retire inactive members as needed. Prior members:<br />
<br />
* Robert Bray<br />
* Chris Holmes<br />
* Judit Mays<br />
* Jeff McKenna<br />
* Markus Neteler<br />
* Paul Spencer<br />
* Jeroen Ticheler<br />
<br />
=== Committee Operation ===<br />
<br />
The incubation committee operates within the OSGeo committee guidelines, operating in a close working relationship with the OSGeo board as reflected in our responsibilities above.<br />
<br />
* Voting members: Voting members are maintained on this page as outlined below. This committee is volunteer based with committee member ship driven by email request to be added or removed. Inactive members (see below) are removed as needed to preserve committee function.<br />
* Project mentors: Have volunteered to represent our organization at a personal level as a guest on the projects email list and meetings. Project mentors are responsible for recommending when a project is ready for graduation based on this first hand experience. For more information see mentor guidelines.<br />
* Committee chair: Committee chair appointed by motion, result forward to the board for approval and recognition as an officer of the foundation. Committee chair is responsible for operation of the committee.<br />
* Communication: This committee operates on the [https://lists.osgeo.org/mailman/listinfo/incubator incubator mailing list]. With the occasional breakout IRC meeting, hangout, or phone call to explore specific issues.<br />
* Decision making: Decision making is performed by email motion. Motions are held open for a two week period. Each motion requires a 50% quorum within the two week period. Voting consists of +1 (approval), +0 (slight agreement), -0 (slight disagreement), -1 (against). The committee chair is responsible for replying to the email thread with voting results and motion resolution.<br />
** Email motions should be clearly worded and have a subject line “Motion:”.<br />
** Motions are held open for a two week period to give everyone a chance to respond, this accounts for volunteers that are only available on weekends.<br />
** At discretion of the chair a motion may be held open longer than two weeks.<br />
** If a motion does not gather a 50% response within a two week period we may need to revisit our active member list – removing members that have not voted within the last year.<br />
** Voting +0 and -0 are a good way to reach quorum for volunteers that have not had a chance to follow the discussion.<br />
** There is no veto in the incubation committee, but we tend to respect -1 votes and withdraw motions that are divisive. It is noted that when reviewing graduation checklists -1 votes tend to track outstanding issues that are then addressed within the voting period.<br />
* Independence: Our mandate is focused on providing to the OSGeo board as outlined above.<br />
<br />
Example email:<br />
<br />
subject: motion: accept blink as a community project<br />
<br />
The following motion has been made by Landon Blake:<br />
<br />
Motion to accept Blink Raster as an community project.<br />
<br />
This motion is held open for two weeks closing January 29th, requiring 50% quorum,<br />
from the following incubation committee members:<br />
<br />
- Bruce Bannerman<br />
- Bob (CI-StPaul) Basques<br />
- Landon Blake +1 initial motion<br />
- Howard Butler<br />
- Arnulf Christl<br />
- Jody Garnett <br />
- Dimitris Kotzinos<br />
- Tom Kralidis<br />
- Julien-Samuel Lacroix<br />
- Mark Lucas<br />
- Steve Lime<br />
- Daniel Morissette<br />
- Markus Schneider<br />
- Cameron Shorter<br />
- Norman Vine<br />
- Frank Warmerdam<br />
<br />
A subsequent email will be sent when the motion is completed, either by the elapsed time period, or by unanimous consent before the closing period.<br />
<br />
== Documents ==<br />
<br />
* Official incubator public web page is at: http://osgeo.org/incubator/index.html (with members list).<br />
* [[Incubation FAQ]]<br />
* [[Official_IncCom_Documents]]<br />
* Incubation process docs: http://osgeo.org/incubator/process/index.html (original [[Official_IncCom_Documents|wiki draft documents]])<br />
* [[Incubation Badges]]<br />
<br />
Draft or Example Documents<br />
* Draft [[Commiter Responsibilities Guidelines]]<br />
* OSGeo Distribution and Committer [[http://www.osgeo.org/content/foundation/legal/licenses.html licenses] which can be used as is, or as an example for projects starting off with participatory open source.<br />
** Geotools Copyright Assignment ([http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.pdf pdf], [http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.odt odt]) - previous example<br />
** [[Project Copyright Assignment]] - previous example<br />
* [[Contributor Agreement]] and FAQ <br />
* [[Incubation Phases]] proposal<br />
<br />
Document Refresh 2014<br />
* [[Project Graduation Checklist]]<br />
<br />
Projects:<br />
* [[OSGeo Labs]] - for OSGeo related projects that haven't reached incubation status<br />
* List of [[Project Steering Committees]]<br />
<br />
Reference:<br />
* [[Project Infrastructure Migration]]<br />
* [http://producingoss.com/html-chunk/index.html Producing OSS] - by Karl Fogel - an excellent primer on running an FOSS project.<br />
<br />
Reports:<br />
* [[Incubation Committee Report 2012]]<br />
* [[Incubation Committee Report 2011]]<br />
<br />
Trac:<br />
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&order=priority Open Incubator Trac Issues]<br />
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&keywords=%7Eapplication&order=priority Pending Incubation Applications]<br />
<br />
Discussion:<br />
* [[5-star-rating]] - discussion about more fine incubation procedure<br />
Reference:<br />
<br />
== Meetings and Reports ==<br />
Meetings are scheduled via [http://lists.osgeo.org/mailman/listinfo/incubator Mailing List] and take place via [[Getting_Started#Jump_on_IRC | IRC]] at the times specified in the [[Foundation Calendar]].<br />
* [[IncCom Meeting1|First Meeting]] - March 13th 2006<br />
* [[IncCom Meeting2|Second Meeting]] - March 20th 2006<br />
* [[IncCom Meeting3|Third Meeting]] - March 27th 2006<br />
* [[IncCom Meeting4|Fourth Meeting]] - April 10th 2006<br />
* [[IncCom Meeting5|Fifth Meeting]] - April 24th 2006<br />
* [[IncCom Meeting6|Sixth Meeting]] - June 19th 2006<br />
* [[IncCom Meeting7|Seventh Meeting]] - August 7th 2006<br />
* [[IncCom Meeting8|Eighth Meeting]] - October 30th 2006<br />
* [[IncCom Meeting9|Nineth Meeting]] - February 12th 2007<br />
* [[IncCom Meeting10|Tenth Meeting]] - June 11th 2007<br />
* [[IncCom Meeting11|Eleventh Meeting]] - October 29th 2007 <br />
* [[IncCom Meeting12|Twelfth Meeting]] - September 8th 2008 <br />
* [[IncCom Meeting13|Thirteenth Meeting]] - October 29th 2009<br />
* [[IncCom Meeting14|Fourteenth Meeting]] - March 1th 2010<br />
* [[IncCom Meeting15]] - Nov 21 2011<br />
* [[IncCom Meeting16]] - Jan 17 2012<br />
* [[IncCom Meeting17]] - March 19 2012<br />
* [[IncCom Meeting18]] - May 21 2012<br />
* [[IncCom Meeting19]] - July 23 2012<br />
* [[IncCom Meeting20]] - Sep 24 2012<br />
* [[IncCom Meeting21]] - Feb 18 2013<br />
* [[IncCom Report22]] - 2013 Q2<br />
* [[IncCom Report23]] - 2013 Q3<br />
* [[IncCom Report24]] - 2014 Q1<br />
* [[Fall 2014 Committee Report for OSGeo Journal]]<br />
<br />
== Incubator ==<br />
<br />
The OSGeo incubation process takes place in three stages:<br />
<br />
# Initial Application<br />
# Incubation<br />
## Project Status: project details, and a few resourcing questions for the system admin committee (see [[Project Status Template]]).<br />
## Provenance Review: quick check to ensure the project is open source and has permission to distribute its source code.<br />
## Final Checklist: review the project procedures and gather requested information for OSGeo participation<br />
# Graduation<br />
<br />
The following projects are currently in OSGeo incubation. The links provided are used to track the progress of incubation projects and are used by the developer team (and OSGeo mentor). In many cases the links will take you to a project specific wiki or website in order to be closer to their target community.<br />
<br />
When projects have completed the incubation checklist their mentor will recommend them to the Incubation committee for graduation.<br />
<br />
== Projects Currently In Incubation ==<br />
=== IstSOS ===<br />
<br />
'''IstSOS''': http://wiki.osgeo.org/wiki/IstSOS<br />
# [[IstSOS Provenance Review]]<br />
# [[IstSOS Incubation Status]] <br />
# ''Mentor'': [[User: Jeff_McKenna|Jeff McKenna]]<br />
<br />
=== MetaCRS ===<br />
<br />
'''MetaCRS''': http://trac.osgeo.org/metacrs/<br />
# [[MetaCRS Incubation Status]]<br />
# no provenance review provided<br />
# no check list provided<br />
# ''Mentor'': [[User: Dmorissette|Daniel Morissette]]<br />
<br />
=== Opticks ===<br />
<br />
'''Opticks''': http://opticks.org<br />
# [[Opticks Incubation Status]]<br />
# no provenance review provided<br />
# [[Opticks Incubation Checklist]]<br />
# ''Mentor'': [[User: Mark_Lucas|Mark Lucas]]<br />
<br />
=== Oskari ===<br />
<br />
'''Oskari''': http://oskari.org/<br />
# [[Oskari Incubation Application]]<br />
# [[Oskari Incubation Status]]<br />
# ''Mentor'': [[Arnulf Christl]]<br />
<br />
=== OSGeoLive ===<br />
<br />
'''OSGeoLive''': http://live.osgeo.org<br />
# [[https://trac.osgeo.org/osgeo/ticket/2002 OSGeoLive Incubation Application]]<br />
# [[Live_GIS_Incubation_Graduation_Checklist]]<br />
# ''Mentor'': [[Jody Garnett]]<br />
<br />
=== PyWPS ===<br />
<br />
'''PyWPS''': http://pywps.org<br />
# PyWPS Application<br />
# Incubation Status<br />
# [https://github.com/geopython/pywps/wiki/ProjectGraduationChecklist PyWPS Graduation Checklist]<br />
# ''Mentor'': [[User:Tomkralidis|Tom Kralidis]]<br />
<br />
=== TEAM Engine ===<br />
<br />
'''TEAM Engine''': http://teamengine.sourceforge.net<br />
# status template not filled out<br />
# no provenance review provided<br />
# no check list provided<br />
# ''Mentor'': [[User: Jdeolive|Justin Deoliveira]]<br />
<br />
=== ZOO-Project ===<br />
<br />
'''ZOO-Project''': http://www.zoo-project.org<br />
# [[ZOO-Project_Incubation_Status]]<br />
# [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance Review]<br />
# [[ZOO-Project Incubation Checklist]]<br />
# ''Mentor'': [[User: Kotzino|Dimitris Kotzinos]]<br />
<br />
== Graduated == <br />
<br />
The following status and provenance documents are for historical purposes, and are no longer actively maintained. <br />
<br />
* Community Mapbuilder: [[Community Mapbuilder Incubation Progress]] | [[Community Mapbuilder Provenance Review]] (Entered 2006-02-04, Graduated 2006-07-14, Mentor: Steve Lime)<br />
* deegree: [[deegree Incubation Status]] | [[deegree Provenance Review]] (Entered: 2008-06-09, Graduated 2010-02-04, Mentor: Jody Garnett)<br />
* FDO: [[FDO Incubation Status]] | [[FDO Provenance Review]] (Entered 2007-03-06, Graduated 2008-02-08, Mentor: Daniel Morissette)<br />
* GEOS: [[GEOS Incubation Status]] | [[GEOS Provenance Review]] (Entered 2007-11-02, Graduated 2012-04-28, Mentor: Frank Warmerdam)<br />
* GDAL/OGR: [[GDAL Incubation Progress]] | [[GDAL Provenance Review]] (Entered 2006-02-04, Graduated 2008-02-08, Mentor: Paul Spencer)<br />
* Geomajas: [[GeoMajas Incubation Status]] | [[GeoMajas Provenance Review]] (Entered 2010-03-04, Graduated 2010-11-22, Mentor: Paul Spencer)<br />
* GeoNetwork: [[GeoNetwork Incubation Status]] | [[GeoNetwork Provenance Review]] (Entered 2006-11-10, Graduated 2008-06-21, Mentor: Jody Garnett)<br />
* GeoNode: [[GeoNode Incubation Status]] [[GeoNode Provenance Review]] [[GeoNode Incubation Checklist]] (Entered 2015-08-13, Graduated 2016-11-09, Mentor: David Bitner)<br />
* GeoMOOSE: [[GeoMoose Incubation Status]] | [[GeoMoose Provenance Review]] | [[GeoMoose Incubation Checklist]] (Entered 2011-12-08, Graduated 2013-04-19, Mentor: Jody Garnett)<br />
* GeoTools: [[GeoTools Incubation Progress]] | [[GeoTools Provenance Review]] (Entered 2006-02-27, Graduated 2008-07-18, Mentor: Cameron Shorter)<br />
* GeoServer: [http://old.geoserver.org/OSGEO%20incubation%20questionnaire.html Incubation Questionnaire] | [http://old.geoserver.org/GeoServer%20Incubation%20Status.html Incubation Status] | [https://github.com/geoserver/geoserver/wiki/GeoServer-Provenance-Review Provenance Review] | [https://github.com/geoserver/geoserver/wiki/GeoServer-Incubation-Checklist Incubation Checklist] | [[Geoserver Mentor Notes]] (Entered 2009-11-05, Graduated 2013-03-15, Mentor: Landon Blake)<br />
* gvSIG: [[gvSIG Incubation Status]] | [[gvSIG Provenance Review]] | [[gvSIG Incubation Checklist]] (Entered 2007-09-07, Graduated 2015-11-26, Mentor: Dimitris Kotzinos)<br />
* GRASS: [[GRASS Incubation Progress]] | [[GRASS Provenance Review]] (Entered 2006-02-27, Graduated 2008-02-08, Mentor: Norman Vine and Arnulf Christl)<br />
* Mapbender: [[Mapbender Incubation Progress]] | [[Mapbender Provenance Review]] (Entered 2006-02-04, Graduated 2006-07-15, Mentor: Paul Spencer)<br />
* MapFish: [[MapFish Incubation Status]] | [[MapFish Provenance Review]] (Entered 2009-11-09, Graduated 2011-09-01, Mentor: Gary Sherman)<br />
* MapGuide Open: [[MapGuide Incubation Status]] | [[MapGuide Provenance Review]] (Entered 2006-02-04, Graduated 2007-03-02, Mentor: Daniel Morissette)<br />
* MapServer: [[MapServer incubation status]] | [[MapServer Provenance Review]] (Entered 2006-02-04, Graduated 2008-12-16, Mentor: Chris Holmes)<br />
* Marble: [[Marble Incubation Status]] | [[Marble Code Provenance Review]] | [[Marble Graduation Checklist]] (Entered 2012-10-12, Graduated 2013-10-17, Mentor: Arnulf Christl)<br />
* OpenLayers: [[OpenLayers Incubation Status]] | [[OpenLayers Provenance Review]] (Entered 2006-11-10, Graduated 2007-11-16, Mentor: Howard Butler)<br />
* Orfeo ToolBox (OTB): [[OTB Project Incubation Status]] | [[OTB Code Provenance Review]] (Entered 2009-10-26, Graduated 2017-07-20, Mentor: Landon Blake)<br />
* PostGIS: [[PostGIS Incubation Status]] | [[PostGIS Provenance Review]] (Entered 2009-08-06, Graduated 2012-06-07, Mentor: Arnulf Christl)<br />
* pycsw: [https://github.com/geopython/pycsw/wiki/Project-Status Incubation Status] | [https://github.com/geopython/pycsw/wiki/Project-Graduation-Checklist Graduation Checklist] | [https://github.com/geopython/pycsw/wiki/pycsw-Provenance-Review Provenance Review] (Entered 2013-03-30, Graduated 2015-03-05, Mentor: Jeff McKenna)<br />
* OSSIM: [[OSSIM incubation status]] | [http://trac.osgeo.org/ossim/wiki/ossimprovenance OSSIM Provenance Review] (Entered 2006-02-27, Graduated 2009-06-02, Mentor: Richard Gould)<br />
* QGIS: [[QGIS Incubation Status]] | [[QGIS Provenance Review]] (Entered 2007-03-02, Graduated 2008-03-14, Mentor: Bob Bray)<br />
<br />
The initial projects to go through the incubation process helped define what is required. The above pages tracked the progress (and capture the experience) of these projects.<br />
<br />
== Withdrawn == <br />
<br />
The following projects did not complete incubation:<br />
<br />
* '''[http://www.rasdaman.org rasdaman]''': : [[ rasdaman Incubation Status ]] | [http://rasdaman.org/wiki/OSGeoCodeProvenance Code Provenance] | [http://www.rasdaman.org/wiki/OSGeoIncubationChecklist Incubation Checklist] (Mentor [[User: Bruce.bannerman|Bruce Bannerman]] )<br />
<br />
<br />
[[Category:Incubation]]<br />
[[Category:Committees]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Incubation_Committee&diff=113273Incubation Committee2018-01-19T17:09:30Z<p>Wiki-Surveyor: </p>
<hr />
<div>The project incubation committee is responsible for overseeing the incubation process for new projects entering the foundation. The incubation committee provides resources to assist new projects to reach full membership, and makes recommendations to the board when they feel projects have completed incubation.<br />
<br />
== About the Incubation Committee ==<br />
<br />
The OSGeo Incubation Committee is responsible for:<br />
<br />
# OSGeo website project review<br />
#* Reviewing applications to list projects on the OSGeo website<br />
#* Preparing and recommend criteria and review process for projects to be listed on the OSGeo website<br />
# Community project program<br />
#* Reviewing community project applications and recommending projects to the board to be accepted as community projects<br />
#* Reporting on the status of projects in the community project program to the board periodically (via Chair)<br />
#* Preparing and recommending community project process and criteria to the board.<br />
# OSGeo Incubation<br />
#* Reviewing applications for incubation and making recommendations to the board on projects that should be admitted into incubation.<br />
#* Appointing mentors for incubation projects.<br />
#* Reviewing progress of projects against incubation requirements, and recommending projects for full project status to the board, when deemed appropriate.<br />
#* Reporting on the status of projects in incubation and the incubation process to the board periodically (via Chair).<br />
#* Preparing and recommending incubation process and criteria to the board.<br />
<br />
The OSGeo incubation committee is not responsible for OSGeo Projects, who report directly to the board via their project officer.<br />
<br />
=== Committee Members ===<br />
<br />
'''Volunteers Welcome''' - if you would like to take part we are always looking for new members, sign up to the email list, and introduce yourself to volunteer.<br />
<br />
Current members:<br />
<br />
* Bruce Bannerman<br />
* Bob (CI-StPaul) Basques<br />
* Landon Blake<br />
* Howard Butler<br />
* Arnulf Christl<br />
* Jody Garnett (chair)<br />
* Dimitris Kotzinos<br />
* Tom Kralidis<br />
* Julien-Samuel Lacroix<br />
* Mark Lucas<br />
* Steve Lime<br />
* Daniel Morissette<br />
* Markus Schneider<br />
* Cameron Shorter<br />
* Norman Vine<br />
* Frank Warmerdam<br />
<br />
'''Thanks you''' - we ask that volunteers remain active, joining the discussion and voting on the email list. If you are unable to take part please send us an email. As volunteers we understand that life can get in the way of advocacy – you are welcome to rejoin at any time. We will also retire inactive members as needed. Prior members:<br />
<br />
* Robert Bray<br />
* Chris Holmes<br />
* Judit Mays<br />
* Jeff McKenna<br />
* Markus Neteler<br />
* Paul Spencer<br />
* Jeroen Ticheler<br />
<br />
=== Committee Operation ===<br />
<br />
The incubation committee operates within the OSGeo committee guidelines, operating in a close working relationship with the OSGeo board as reflected in our responsibilities above.<br />
<br />
* Voting members: Voting members are maintained on this page as outlined below. This committee is volunteer based with committee member ship driven by email request to be added or removed. Inactive members (see below) are removed as needed to preserve committee function.<br />
* Project mentors: Have volunteered to represent our organization at a personal level as a guest on the projects email list and meetings. Project mentors are responsible for recommending when a project is ready for graduation based on this first hand experience. For more information see mentor guidelines.<br />
* Committee chair: Committee chair appointed by motion, result forward to the board for approval and recognition as an officer of the foundation. Committee chair is responsible for operation of the committee.<br />
* Communication: This committee operates on the [https://lists.osgeo.org/mailman/listinfo/incubator incubator mailing list]. With the occasional breakout IRC meeting, hangout, or phone call to explore specific issues.<br />
* Decision making: Decision making is performed by email motion. Motions are held open for a two week period. Each motion requires a 50% quorum within the two week period. Voting consists of +1 (approval), +0 (slight agreement), -0 (slight disagreement), -1 (against). The committee chair is responsible for replying to the email thread with voting results and motion resolution.<br />
** Email motions should be clearly worded and have a subject line “Motion:”.<br />
** Motions are held open for a two week period to give everyone a chance to respond, this accounts for volunteers that are only available on weekends.<br />
** At discretion of the chair a motion may be held open longer than two weeks<br />
** If a motion does not gather a 50% response within a two week period we may need to revisit our active member list – removing members that have not voted within the last year.<br />
** Voting +0 and -0 are a good way to reach quorum for volunteers that have not had a chance to follow the discussion<br />
** There is no veto in the incubation committee, but we tend to respect -1 votes and withdraw motions that are divisive. It is noted that when reviewing graduation checklists -1 votes tend to track outstanding issues that are then addressed within the voting period.<br />
* Independence: Our mandate is focused on providing to the OSGeo board as outlined above.<br />
<br />
Example email:<br />
<br />
subject: motion: accept blink as a community project<br />
<br />
The following motion has been made by Landon Blake:<br />
<br />
Motion to accept Blink Raster as an community project.<br />
<br />
This motion is held open for two weeks closing January 29th, requiring 50% quorum,<br />
from the following incubation committee members:<br />
<br />
- Bruce Bannerman<br />
- Bob (CI-StPaul) Basques<br />
- Landon Blake +1 initial motion<br />
- Howard Butler<br />
- Arnulf Christl<br />
- Jody Garnett <br />
- Dimitris Kotzinos<br />
- Tom Kralidis<br />
- Julien-Samuel Lacroix<br />
- Mark Lucas<br />
- Steve Lime<br />
- Daniel Morissette<br />
- Markus Schneider<br />
- Cameron Shorter<br />
- Norman Vine<br />
- Frank Warmerdam<br />
<br />
A subsequent email will be sent when the motion is completed, either by the elapsed time period, or by unanimous consent before the closing period.<br />
<br />
== Documents ==<br />
<br />
* Official incubator public web page is at: http://osgeo.org/incubator/index.html (with members list).<br />
* [[Incubation FAQ]]<br />
* [[Official_IncCom_Documents]]<br />
* Incubation process docs: http://osgeo.org/incubator/process/index.html (original [[Official_IncCom_Documents|wiki draft documents]])<br />
* [[Incubation Badges]]<br />
<br />
Draft or Example Documents<br />
* Draft [[Commiter Responsibilities Guidelines]]<br />
* OSGeo Distribution and Committer [[http://www.osgeo.org/content/foundation/legal/licenses.html licenses] which can be used as is, or as an example for projects starting off with participatory open source.<br />
** Geotools Copyright Assignment ([http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.pdf pdf], [http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.odt odt]) - previous example<br />
** [[Project Copyright Assignment]] - previous example<br />
* [[Contributor Agreement]] and FAQ <br />
* [[Incubation Phases]] proposal<br />
<br />
Document Refresh 2014<br />
* [[Project Graduation Checklist]]<br />
<br />
Projects:<br />
* [[OSGeo Labs]] - for OSGeo related projects that haven't reached incubation status<br />
* List of [[Project Steering Committees]]<br />
<br />
Reference:<br />
* [[Project Infrastructure Migration]]<br />
* [http://producingoss.com/html-chunk/index.html Producing OSS] - by Karl Fogel - an excellent primer on running an FOSS project.<br />
<br />
Reports:<br />
* [[Incubation Committee Report 2012]]<br />
* [[Incubation Committee Report 2011]]<br />
<br />
Trac:<br />
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&order=priority Open Incubator Trac Issues]<br />
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&keywords=%7Eapplication&order=priority Pending Incubation Applications]<br />
<br />
Discussion:<br />
* [[5-star-rating]] - discussion about more fine incubation procedure<br />
Reference:<br />
<br />
== Meetings and Reports ==<br />
Meetings are scheduled via [http://lists.osgeo.org/mailman/listinfo/incubator Mailing List] and take place via [[Getting_Started#Jump_on_IRC | IRC]] at the times specified in the [[Foundation Calendar]].<br />
* [[IncCom Meeting1|First Meeting]] - March 13th 2006<br />
* [[IncCom Meeting2|Second Meeting]] - March 20th 2006<br />
* [[IncCom Meeting3|Third Meeting]] - March 27th 2006<br />
* [[IncCom Meeting4|Fourth Meeting]] - April 10th 2006<br />
* [[IncCom Meeting5|Fifth Meeting]] - April 24th 2006<br />
* [[IncCom Meeting6|Sixth Meeting]] - June 19th 2006<br />
* [[IncCom Meeting7|Seventh Meeting]] - August 7th 2006<br />
* [[IncCom Meeting8|Eighth Meeting]] - October 30th 2006<br />
* [[IncCom Meeting9|Nineth Meeting]] - February 12th 2007<br />
* [[IncCom Meeting10|Tenth Meeting]] - June 11th 2007<br />
* [[IncCom Meeting11|Eleventh Meeting]] - October 29th 2007 <br />
* [[IncCom Meeting12|Twelfth Meeting]] - September 8th 2008 <br />
* [[IncCom Meeting13|Thirteenth Meeting]] - October 29th 2009<br />
* [[IncCom Meeting14|Fourteenth Meeting]] - March 1th 2010<br />
* [[IncCom Meeting15]] - Nov 21 2011<br />
* [[IncCom Meeting16]] - Jan 17 2012<br />
* [[IncCom Meeting17]] - March 19 2012<br />
* [[IncCom Meeting18]] - May 21 2012<br />
* [[IncCom Meeting19]] - July 23 2012<br />
* [[IncCom Meeting20]] - Sep 24 2012<br />
* [[IncCom Meeting21]] - Feb 18 2013<br />
* [[IncCom Report22]] - 2013 Q2<br />
* [[IncCom Report23]] - 2013 Q3<br />
* [[IncCom Report24]] - 2014 Q1<br />
* [[Fall 2014 Committee Report for OSGeo Journal]]<br />
<br />
== Incubator ==<br />
<br />
The OSGeo incubation process takes place in three stages:<br />
<br />
# Initial Application<br />
# Incubation<br />
## Project Status: project details, and a few resourcing questions for the system admin committee (see [[Project Status Template]]).<br />
## Provenance Review: quick check to ensure the project is open source and has permission to distribute its source code.<br />
## Final Checklist: review the project procedures and gather requested information for OSGeo participation<br />
# Graduation<br />
<br />
The following projects are currently in OSGeo incubation. The links provided are used to track the progress of incubation projects and are used by the developer team (and OSGeo mentor). In many cases the links will take you to a project specific wiki or website in order to be closer to their target community.<br />
<br />
When projects have completed the incubation checklist their mentor will recommend them to the Incubation committee for graduation.<br />
<br />
== Projects Currently In Incubation ==<br />
=== IstSOS ===<br />
<br />
'''IstSOS''': http://wiki.osgeo.org/wiki/IstSOS<br />
# [[IstSOS Provenance Review]]<br />
# [[IstSOS Incubation Status]] <br />
# ''Mentor'': [[User: Jeff_McKenna|Jeff McKenna]]<br />
<br />
=== MetaCRS ===<br />
<br />
'''MetaCRS''': http://trac.osgeo.org/metacrs/<br />
# [[MetaCRS Incubation Status]]<br />
# no provenance review provided<br />
# no check list provided<br />
# ''Mentor'': [[User: Dmorissette|Daniel Morissette]]<br />
<br />
=== Opticks ===<br />
<br />
'''Opticks''': http://opticks.org<br />
# [[Opticks Incubation Status]]<br />
# no provenance review provided<br />
# [[Opticks Incubation Checklist]]<br />
# ''Mentor'': [[User: Mark_Lucas|Mark Lucas]]<br />
<br />
=== Oskari ===<br />
<br />
'''Oskari''': http://oskari.org/<br />
# [[Oskari Incubation Application]]<br />
# [[Oskari Incubation Status]]<br />
# ''Mentor'': [[Arnulf Christl]]<br />
<br />
=== OSGeoLive ===<br />
<br />
'''OSGeoLive''': http://live.osgeo.org<br />
# [[https://trac.osgeo.org/osgeo/ticket/2002 OSGeoLive Incubation Application]]<br />
# [[Live_GIS_Incubation_Graduation_Checklist]]<br />
# ''Mentor'': [[Jody Garnett]]<br />
<br />
=== PyWPS ===<br />
<br />
'''PyWPS''': http://pywps.org<br />
# PyWPS Application<br />
# Incubation Status<br />
# [https://github.com/geopython/pywps/wiki/ProjectGraduationChecklist PyWPS Graduation Checklist]<br />
# ''Mentor'': [[User:Tomkralidis|Tom Kralidis]]<br />
<br />
=== TEAM Engine ===<br />
<br />
'''TEAM Engine''': http://teamengine.sourceforge.net<br />
# status template not filled out<br />
# no provenance review provided<br />
# no check list provided<br />
# ''Mentor'': [[User: Jdeolive|Justin Deoliveira]]<br />
<br />
=== ZOO-Project ===<br />
<br />
'''ZOO-Project''': http://www.zoo-project.org<br />
# [[ZOO-Project_Incubation_Status]]<br />
# [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance Review]<br />
# [[ZOO-Project Incubation Checklist]]<br />
# ''Mentor'': [[User: Kotzino|Dimitris Kotzinos]]<br />
<br />
== Graduated == <br />
<br />
The following status and provenance documents are for historical purposes, and are no longer actively maintained. <br />
<br />
* Community Mapbuilder: [[Community Mapbuilder Incubation Progress]] | [[Community Mapbuilder Provenance Review]] (Entered 2006-02-04, Graduated 2006-07-14, Mentor: Steve Lime)<br />
* deegree: [[deegree Incubation Status]] | [[deegree Provenance Review]] (Entered: 2008-06-09, Graduated 2010-02-04, Mentor: Jody Garnett)<br />
* FDO: [[FDO Incubation Status]] | [[FDO Provenance Review]] (Entered 2007-03-06, Graduated 2008-02-08, Mentor: Daniel Morissette)<br />
* GEOS: [[GEOS Incubation Status]] | [[GEOS Provenance Review]] (Entered 2007-11-02, Graduated 2012-04-28, Mentor: Frank Warmerdam)<br />
* GDAL/OGR: [[GDAL Incubation Progress]] | [[GDAL Provenance Review]] (Entered 2006-02-04, Graduated 2008-02-08, Mentor: Paul Spencer)<br />
* Geomajas: [[GeoMajas Incubation Status]] | [[GeoMajas Provenance Review]] (Entered 2010-03-04, Graduated 2010-11-22, Mentor: Paul Spencer)<br />
* GeoNetwork: [[GeoNetwork Incubation Status]] | [[GeoNetwork Provenance Review]] (Entered 2006-11-10, Graduated 2008-06-21, Mentor: Jody Garnett)<br />
* GeoNode: [[GeoNode Incubation Status]] [[GeoNode Provenance Review]] [[GeoNode Incubation Checklist]] (Entered 2015-08-13, Graduated 2016-11-09, Mentor: David Bitner)<br />
* GeoMOOSE: [[GeoMoose Incubation Status]] | [[GeoMoose Provenance Review]] | [[GeoMoose Incubation Checklist]] (Entered 2011-12-08, Graduated 2013-04-19, Mentor: Jody Garnett)<br />
* GeoTools: [[GeoTools Incubation Progress]] | [[GeoTools Provenance Review]] (Entered 2006-02-27, Graduated 2008-07-18, Mentor: Cameron Shorter)<br />
* GeoServer: [http://old.geoserver.org/OSGEO%20incubation%20questionnaire.html Incubation Questionnaire] | [http://old.geoserver.org/GeoServer%20Incubation%20Status.html Incubation Status] | [https://github.com/geoserver/geoserver/wiki/GeoServer-Provenance-Review Provenance Review] | [https://github.com/geoserver/geoserver/wiki/GeoServer-Incubation-Checklist Incubation Checklist] | [[Geoserver Mentor Notes]] (Entered 2009-11-05, Graduated 2013-03-15, Mentor: Landon Blake)<br />
* gvSIG: [[gvSIG Incubation Status]] | [[gvSIG Provenance Review]] | [[gvSIG Incubation Checklist]] (Entered 2007-09-07, Graduated 2015-11-26, Mentor: Dimitris Kotzinos)<br />
* GRASS: [[GRASS Incubation Progress]] | [[GRASS Provenance Review]] (Entered 2006-02-27, Graduated 2008-02-08, Mentor: Norman Vine and Arnulf Christl)<br />
* Mapbender: [[Mapbender Incubation Progress]] | [[Mapbender Provenance Review]] (Entered 2006-02-04, Graduated 2006-07-15, Mentor: Paul Spencer)<br />
* MapFish: [[MapFish Incubation Status]] | [[MapFish Provenance Review]] (Entered 2009-11-09, Graduated 2011-09-01, Mentor: Gary Sherman)<br />
* MapGuide Open: [[MapGuide Incubation Status]] | [[MapGuide Provenance Review]] (Entered 2006-02-04, Graduated 2007-03-02, Mentor: Daniel Morissette)<br />
* MapServer: [[MapServer incubation status]] | [[MapServer Provenance Review]] (Entered 2006-02-04, Graduated 2008-12-16, Mentor: Chris Holmes)<br />
* Marble: [[Marble Incubation Status]] | [[Marble Code Provenance Review]] | [[Marble Graduation Checklist]] (Entered 2012-10-12, Graduated 2013-10-17, Mentor: Arnulf Christl)<br />
* OpenLayers: [[OpenLayers Incubation Status]] | [[OpenLayers Provenance Review]] (Entered 2006-11-10, Graduated 2007-11-16, Mentor: Howard Butler)<br />
* Orfeo ToolBox (OTB): [[OTB Project Incubation Status]] | [[OTB Code Provenance Review]] (Entered 2009-10-26, Graduated 2017-07-20, Mentor: Landon Blake)<br />
* PostGIS: [[PostGIS Incubation Status]] | [[PostGIS Provenance Review]] (Entered 2009-08-06, Graduated 2012-06-07, Mentor: Arnulf Christl)<br />
* pycsw: [https://github.com/geopython/pycsw/wiki/Project-Status Incubation Status] | [https://github.com/geopython/pycsw/wiki/Project-Graduation-Checklist Graduation Checklist] | [https://github.com/geopython/pycsw/wiki/pycsw-Provenance-Review Provenance Review] (Entered 2013-03-30, Graduated 2015-03-05, Mentor: Jeff McKenna)<br />
* OSSIM: [[OSSIM incubation status]] | [http://trac.osgeo.org/ossim/wiki/ossimprovenance OSSIM Provenance Review] (Entered 2006-02-27, Graduated 2009-06-02, Mentor: Richard Gould)<br />
* QGIS: [[QGIS Incubation Status]] | [[QGIS Provenance Review]] (Entered 2007-03-02, Graduated 2008-03-14, Mentor: Bob Bray)<br />
<br />
The initial projects to go through the incubation process helped define what is required. The above pages tracked the progress (and capture the experience) of these projects.<br />
<br />
== Withdrawn == <br />
<br />
The following projects did not complete incubation:<br />
<br />
* '''[http://www.rasdaman.org rasdaman]''': : [[ rasdaman Incubation Status ]] | [http://rasdaman.org/wiki/OSGeoCodeProvenance Code Provenance] | [http://www.rasdaman.org/wiki/OSGeoIncubationChecklist Incubation Checklist] (Mentor [[User: Bruce.bannerman|Bruce Bannerman]] )<br />
<br />
<br />
[[Category:Incubation]]<br />
[[Category:Committees]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=California_Chapter_Events_Page&diff=103039California Chapter Events Page2016-09-16T17:43:44Z<p>Wiki-Surveyor: </p>
<hr />
<div>We have an [[California/Exhibition Pack|California Chapter Exhibition Pack]], see the page for details if you want to use it.<br />
<br />
== Budget ==<br />
Based on our fund raising efforts we will determine what our [[California/Budget| Budget]] will allow use to do.<br />
The goal for '''2009''' is '''$1500'''..<br />
For 2010 the new focus is on getting several new sponsors for OSGeo in general which would create additional funds for support of chapter activities.<br />
<br />
== Future/Confirmed ==<br />
<br />
* [[OSGeo California Chapter 2016 Annual Meeting]]<br />
* [[Fall 2016 JTS Code Sprint]]<br />
<br />
<br />
== Proposed ==<br />
<br />
<br />
== Past ==<br />
(Reverse Date Order, Most recent 1st)<br />
*[[CLSA 2014 Conference OSGeo Open Source GIS Track]]<br />
*[[OSGeo California Chapter 2013 Annual Meeting]]<br />
*[[OSGeo California Chapter 2015 Annual Meeting]]<br />
* SCALE (February 22-24, 2013)<br />
* AGU 2013 (December 2013)<br />
* AAG (April 13, 2013)<br />
* Strata (February 26-28, 2013)<br />
* CLSA Conference (March 23-27, 2013)<br />
* URISA CAL-GIS (April 15-17, 2013)<br />
* OSGeo Annual Meeting (October 12, 2013)<br />
* [[OSGeo California Chapter Spring 2013 Hackathon]] (January 19, 2013)<br />
* California Geographic Society (Spring 2013)<br />
* [[California Chapter 2012 Annual Meeting]] Saturday, October 16, 2012<br />
* [[California Chapter 2011 Annual Meeting]] October 22, 2011 - Davis, CA<br />
* [[Where 2.0 2011]] April 19-21, 2011, Santa Clara Hyatt<br />
* California Invasive Plant Society annual meeting Jul11 - LiveDVD<br />
* FLUXNET and Remote Sensing Open-Workshop June11 - provided LiveDVD to interested participants<br />
* San Francisco GeoMeetup - 2011 monthly/recurrent<br />
* [[AAG 2011]] April 12-16 Seattle<br />
* [[CGS 2011]] April 29-May 1st, Bishop, CA<br />
* Missed -[[ACM SIGSPATIAL 2010]] - Nov 2-5, San Jose ([http://acmgis2010.cs.ucsb.edu Conference Website])<br />
* Missed -[[AGU 2010]] Dec, SF - It's always in California<br />
* Missed -[[GTC WEST 2010]] Cal chapter involvement proposed. May 11-12, Sacramento<br />
* [[CGS 2010]] May 1, Fullerton<br />
* [[AAG 2010]] April 2010, Washington, D.C.<br />
* [[Where_20_2010 | Where 2.0]]<br />
* [[SCALE 2010]] Feb 19-21, Los Angeles<br />
* [[AGU 2009]] December 14-18 - SF - It's always in California<br />
* [[GIS Day 2009]] November - Worldwide Local events (Berkeley, Davis, ?)<br />
* [[NACIS 2009]] October 7- 10 - Sacramento : We gave a 50 minute team demo on 4 OSGeo applications.<br />
<br />
* [[OSCON 2009]] July 20-24, San Jose, CA - State of OSGeo "Lightening Talk" was a hit!<br />
* [[Where 2.0 2009]] May 20-21 - San Jose, CA- Paul Ramsey will join us.<br />
* [[USGS Open House 2009]] May 16-17 - Menlo Park, we we're invited at [[CalGIS]]<br />
* [[CGS 2009]] May 2 - Santa Ynez - Always in California, small cheap, outreach to grade schools and non-profits.<br />
* [[CalGIS 2009]] April 7-9 Sacramento - Booth was too expensive($800 for booth), Berkeley GIF Lab talked about QGIS<br />
* [[AAG 2009]] (Mar) - Las Vegas <br />
* [[California/InauguralMeeting|Inaugural Meeting]] (Feb) of California Chapter<br />
<br />
* [[AGU 2008]] - Open Source Session at American Geophysical Union; San Francisco, CA<br />
* GIS Day 2008 - UC Berkeley GIF Lab, US EPA Region IX<br />
* [[OSBootCamp OSBootCamp 2008]] - Open Source day at UC Berkeley<br />
* [[CGS 2008]] - Booth at the Calfornia Geographical Society meeting in Chico.<br />
* [[4H Workshop]] - [[User:bwoodall|Bill]] will be running a workshop at UC Davis for 4H high schoolers on GPS/GIS<br />
<br />
== Missed Opportunities (May Recur)==<br />
* [[OSCON 2010]] - Cal chapter involvement proposed. July?, Portland<br />
* UCSB Vendor Fair, May 2011, Santa Barbara<br />
* [[OpenSourceWorld 2009]] August, SF<br />
* [[APCG 2009]] Sept 30 - Oct 3 - San Diego<br />
* [[ACM GIS 2009]] November 4-6 - Seattle (pass it to [[cugos]], speaking opportunities)<br />
<br />
== OSGeo Chapter Annual Meetings ==<br />
Meetings will be held annually at minimum and as needed in between.<br />
*[[California Chapter 2012 Annual Meeting]]<br />
*[[California Chapter 2011 Annual Meeting]]<br />
*[http://wiki.osgeo.org/wiki/California/Meeting_Minutes California 2009 Annual Meeting]<br />
<br />
== Navigation ==<br />
[http://wiki.osgeo.org/wiki/California California Chapter Wiki Home Page]<br />
<br />
[[Category: Local Chapters]]<br />
[[Category: California]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Fall_2016_JTS_Code_Sprint&diff=103038Fall 2016 JTS Code Sprint2016-09-16T17:42:32Z<p>Wiki-Surveyor: Created page with "==Description== A simple code sprint to update JTS, a key 2D geospatial geometry library for open source GIS programs written in Java. ==Date== Saturday, September 24, 2016..."</p>
<hr />
<div>==Description==<br />
A simple code sprint to update JTS, a key 2D geospatial geometry library for open source GIS programs written in Java.<br />
<br />
==Date==<br />
Saturday, September 24, 2016<br />
<br />
==Location==<br />
We will be doing this code sprint remotely. Landon is willing to host local programmers in Stockton the afternoon of the sprint. <br />
<br />
==Source Code Repository==<br />
https://subversion.assembla.com/svn/surveyos-main-code-repo/trunk/main/jts refactored<br />
<br />
==Proposed Tasks==<br />
* Update JUnit tests for the geometry package to JUnit 5.<br />
* Set-up automated test quite for unit tests in the geometry package.<br />
* Refactor LineSegment class to group utility/calculation methods that work with external objects to a separate LineSegmentUtilities class.<br />
* Improve Javadoc comments for classes/interfaces in the geometry package.<br />
* Implement generics and for/each loops in the geometry package.<br />
* Design new experimental Geometry interface using Java 8/Java 9 features.<br />
* Implement CoordinateArray for a set of points with unique identifiers.<br />
<br />
<br />
==Completed Tasks==<br />
To be determined.</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_California_Chapter_2016_Annual_Meeting&diff=103037OSGeo California Chapter 2016 Annual Meeting2016-09-16T17:26:17Z<p>Wiki-Surveyor: Created page with "== Introduction == Every year the California OSGeo Chapter is required to have an annual meeting. Our 2016 Annual Meeting is scheduled for Saturday, November 15. == Schedul..."</p>
<hr />
<div>== Introduction ==<br />
Every year the California OSGeo Chapter is required to have an annual meeting. Our 2016 Annual Meeting is scheduled for Saturday, November 15. <br />
<br />
== Schedule ==<br />
To be determined.<br />
<br />
'''UnConference Ideas:'''<br />
What is an UnConference? Participants organize themselves into groups interested in a particular topic to have discussions and informal learning sessions. For example, a group might decide to explore data sources, and another group might discuss drone systems. We'll explain more and organize on the day of the event.<br />
<br />
== Directions & Parking ==<br />
To be determined.<br />
<br />
=== Exact Location ===<br />
To be determined.<br />
<br />
=== Parking ===<br />
To be determined.<br />
<br />
=== Map for Directions ===<br />
To be determined.<br />
<br />
=== Transit ===<br />
<br />
==== In Town ====<br />
To be determined.<br />
<br />
==== Out of Town ====<br />
To be determined.<br />
<br />
<br />
== Sponsors ==<br />
To be determined.<br />
<br />
== History ==<br />
Links to previous meetings:<br />
* [[OSGeo_California_Chapter_2015_Annual_Meeting]]<br />
* [[OSGeo_California_Chapter_2014_Annual_Meeting]]<br />
* [[OSGeo_California_Chapter_2013_Annual_Meeting]]<br />
* [[California_Chapter_2012_Annual_Meeting]]<br />
* [[California Chapter 2011 Annual Meeting]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=California_Chapter_Events_Page&diff=103036California Chapter Events Page2016-09-16T17:23:00Z<p>Wiki-Surveyor: </p>
<hr />
<div>We have an [[California/Exhibition Pack|California Chapter Exhibition Pack]], see the page for details if you want to use it.<br />
<br />
== Budget ==<br />
Based on our fund raising efforts we will determine what our [[California/Budget| Budget]] will allow use to do.<br />
The goal for '''2009''' is '''$1500'''..<br />
For 2010 the new focus is on getting several new sponsors for OSGeo in general which would create additional funds for support of chapter activities.<br />
<br />
== Future/Confirmed ==<br />
<br />
* [[OSGeo California Chapter 2016 Annual Meeting]]<br />
* [[Fall 2016 JTS Code Sprint]]<br />
<br />
<br />
== Proposed ==<br />
*[[CLSA 2014 Conference OSGeo Open Source GIS Track]]<br />
*[[OSGeo California Chapter 2013 Annual Meeting]]<br />
*[[OSGeo California Chapter 2015 Annual Meeting]]<br />
<br />
== Past ==<br />
(Reverse Date Order, Most recent 1st)<br />
* SCALE (February 22-24, 2013)<br />
* AGU 2013 (December 2013)<br />
* AAG (April 13, 2013)<br />
* Strata (February 26-28, 2013)<br />
* CLSA Conference (March 23-27, 2013)<br />
* URISA CAL-GIS (April 15-17, 2013)<br />
* OSGeo Annual Meeting (October 12, 2013)<br />
* [[OSGeo California Chapter Spring 2013 Hackathon]] (January 19, 2013)<br />
* California Geographic Society (Spring 2013)<br />
<br />
* [[California Chapter 2012 Annual Meeting]] Saturday, October 16, 2012<br />
* [[California Chapter 2011 Annual Meeting]] October 22, 2011 - Davis, CA<br />
* [[Where 2.0 2011]] April 19-21, 2011, Santa Clara Hyatt<br />
* California Invasive Plant Society annual meeting Jul11 - LiveDVD<br />
* FLUXNET and Remote Sensing Open-Workshop June11 - provided LiveDVD to interested participants<br />
* San Francisco GeoMeetup - 2011 monthly/recurrent<br />
* [[AAG 2011]] April 12-16 Seattle<br />
* [[CGS 2011]] April 29-May 1st, Bishop, CA<br />
* Missed -[[ACM SIGSPATIAL 2010]] - Nov 2-5, San Jose ([http://acmgis2010.cs.ucsb.edu Conference Website])<br />
* Missed -[[AGU 2010]] Dec, SF - It's always in California<br />
* Missed -[[GTC WEST 2010]] Cal chapter involvement proposed. May 11-12, Sacramento<br />
* [[CGS 2010]] May 1, Fullerton<br />
* [[AAG 2010]] April 2010, Washington, D.C.<br />
* [[Where_20_2010 | Where 2.0]]<br />
* [[SCALE 2010]] Feb 19-21, Los Angeles<br />
* [[AGU 2009]] December 14-18 - SF - It's always in California<br />
* [[GIS Day 2009]] November - Worldwide Local events (Berkeley, Davis, ?)<br />
* [[NACIS 2009]] October 7- 10 - Sacramento : We gave a 50 minute team demo on 4 OSGeo applications.<br />
<br />
* [[OSCON 2009]] July 20-24, San Jose, CA - State of OSGeo "Lightening Talk" was a hit!<br />
* [[Where 2.0 2009]] May 20-21 - San Jose, CA- Paul Ramsey will join us.<br />
* [[USGS Open House 2009]] May 16-17 - Menlo Park, we we're invited at [[CalGIS]]<br />
* [[CGS 2009]] May 2 - Santa Ynez - Always in California, small cheap, outreach to grade schools and non-profits.<br />
* [[CalGIS 2009]] April 7-9 Sacramento - Booth was too expensive($800 for booth), Berkeley GIF Lab talked about QGIS<br />
* [[AAG 2009]] (Mar) - Las Vegas <br />
* [[California/InauguralMeeting|Inaugural Meeting]] (Feb) of California Chapter<br />
<br />
* [[AGU 2008]] - Open Source Session at American Geophysical Union; San Francisco, CA<br />
* GIS Day 2008 - UC Berkeley GIF Lab, US EPA Region IX<br />
* [[OSBootCamp OSBootCamp 2008]] - Open Source day at UC Berkeley<br />
* [[CGS 2008]] - Booth at the Calfornia Geographical Society meeting in Chico.<br />
* [[4H Workshop]] - [[User:bwoodall|Bill]] will be running a workshop at UC Davis for 4H high schoolers on GPS/GIS<br />
<br />
== Missed Opportunities (May Recur)==<br />
* [[OSCON 2010]] - Cal chapter involvement proposed. July?, Portland<br />
* UCSB Vendor Fair, May 2011, Santa Barbara<br />
* [[OpenSourceWorld 2009]] August, SF<br />
* [[APCG 2009]] Sept 30 - Oct 3 - San Diego<br />
* [[ACM GIS 2009]] November 4-6 - Seattle (pass it to [[cugos]], speaking opportunities)<br />
<br />
== OSGeo Chapter Annual Meetings ==<br />
Meetings will be held annually at minimum and as needed in between.<br />
*[[California Chapter 2012 Annual Meeting]]<br />
*[[California Chapter 2011 Annual Meeting]]<br />
*[http://wiki.osgeo.org/wiki/California/Meeting_Minutes California 2009 Annual Meeting]<br />
<br />
== Navigation ==<br />
[http://wiki.osgeo.org/wiki/California California Chapter Wiki Home Page]<br />
<br />
[[Category: Local Chapters]]<br />
[[Category: California]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Community_Projects&diff=97161OSGeo Community Projects2016-03-06T22:12:47Z<p>Wiki-Surveyor: /* Member Projects */</p>
<hr />
<div>= OSGeo Labs Projects =<br />
<br />
See http://wiki.osgeo.org/wiki/Category:OSGeo_Technology_Projects<br />
<br />
== Purpose ==<br />
OSGeo Technology Project is an umbrella for open source geospatial software projects that would like to become OSGeo projects in the future, but that aren't ready for incubation quite yet. It is appropriate to submit your new or experimental project as an OSGeo Technology Project.<br />
<br />
The volunteers that work as part of OSGeo Technology Projects have the goal of helping OSGeo Technology Project qualify for incubation. To reach this goal,OSGeo Technology Project volunteers help OSGeo Technology Project with the following tasks:<br />
<br />
* Project marketing.<br />
* Development of user and programmer communities.<br />
* Establishment of programs and policies for project documentation, copyright assignment, and licensing.<br />
* Establishment of programs and policies for software development. This includes version tracking, bug tracking, and feature request tracking, creation of a development road map, and organization of code sprints/events.<br />
* Establishment of project governance programs and policies.<br />
* Collaboration on technical standards, data formats, and code sharing with other open source geospatial software projects.<br />
* Utilization of software development infrastructure like mailing lists, bug trackers, version control software/hosting, and web hosting.<br />
<br />
== OSGeo Technology Project Selection Criteria ==<br />
Projects should only submit themselves for inclusion in OSGeo Technology Project if they follow the OSGeo Incubation principles.<br />
# The code is under an OSI approved license (data & doc projects need to specify their choice for a type of license).<br />
# The project is willing to keep code clear of encumbrances<br />
# The project is "geospatial", or directly supports geospatial applications.<br />
# The project hopes to become a graduated OSGeo project,.<br />
<br />
==Becoming a OSGeo Technology Project==<br />
The goal is to keep the submission process for OSGeo Technology Project as simple and painless as possible. (The OSGeo Incubation Process is hard enough.) To submit your software project for inclusion in OSGeo Technology Project, simply send a description of the project to the [http://lists.osgeo.org/mailman/listinfo/incubator OSGeo Incubation Committee Mailing List], or [mailto:sunburned.surveyor@gmail.com e-mail Landon Blake.]<br />
<br />
==OSGeo Technology Project Set-Up Process==<br />
Once a project has been accepted into OSGeo Technology Project, the OSGeo Technology Project volunteers will help the projects take these steps:<br />
# Selection of an open source license if the project hasn't already done so.<br />
# Creation a home page for the project. The OSGeo wiki is recommended for this page. <br />
# Announce and discuss the project on the [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss] email list.<br />
# Set the project software development up on the OSGeo infrastructure if appropriate. (Sourceforge or other software development hosting sites can be used as an alternative.)<br />
<br />
== OSGeo Technology Project Status Conditions ==<br />
<br />
We’ve designed an informal “status” system to assist programmers and users evaluate projects in OSGeo Labs. Each project in labs is assigned one (1) of five (5) status conditions. The following factors are used to determine the status condition of the projects:<br />
<br />
1) Source Code Completeness<br />
2) Source Code Stability<br />
3) Community Support (Mailing Lists, Documentation, Tutorials)<br />
4) Project Deliverables (Programming Libraries and/or Executables)<br />
5) Project Infrastructure (Source Code Versioning, Bug Trackers, Feature Trackers, Web Site, Mailing Lists, Discussion Forums)<br />
6) Project Governance (Decision Making Processes, Licensing, Copyright Assignment, Release Schedule, Coding Standards)<br />
7) Community Activity<br />
8) Marketing and Outreach<br />
<br />
Below are the different status conditions that can be assigned to a project in OSGeo Technology Project.<br />
<br />
* '''Seed''': This project is in the conceptual stage. There may be some source code written, but it is incomplete or very experiemental. The project may lack deliverables, community support, project infrastructure, project governance, community activity, or marketing and outreach.<br />
<br />
* '''Seedling''': This project is moving beyond the conceptual stage with some concrete code. However the code is still experimental and isn't stable. Projects at this status level could still experience a lot of change in their code base. This project should start to have some project infrastructure and some basic documentation.<br />
<br />
* '''Sapling''': This project has functional source code, although it may not be "mature and feature rich". For example, the code may only be usable as a programming library or a command line tool instead of featuring a GUI. The project has started to support users and programmers with communication tools, trackers, and documentation. The project has started to think about project governance and marketing, perhaps creating plans in these areas that are not fully implemented.<br />
<br />
* '''Adult''': This project has a usable and user friendly deliverable, like an executable program or a stable and well-deocumented programming library. The project is supporting users and programmers with communication tools, trackers, and documentation. It has started the initial phases of incubation. This includes addressing issues of copyright, licensing, and project governance. The project also has a marketing and community growth plan and has started to implement the plan.<br />
<br />
== Member Projects ==<br />
* [[OSGeo Technology Project: Geoinformatica]]<br />
* [[OSGeo Technology Project: pgRouting]]<br />
* [[OSGeo Technology Project: PAGC]]<br />
* [[OSGeo Technology Project: MapProxy]]<br />
* [[OSGeo Technology Project: pycsw]]<br />
* [[OSGeo Technology Project: Virtual Terrain Project]]<br />
* [[OSGeo Technology Project: PyWPS]]<br />
* [[OSGeo Technology Project: OSGeo Certification]]<br />
<br />
== Archive ==<br />
<br />
There is an archive of the old OSGeo Technology Projects page at [[OSGeo Labs Page Archive]].</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Labs:_OSGeo_Certification&diff=97159OSGeo Labs: OSGeo Certification2016-03-06T22:12:08Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: OSGeo Certification to OSGeo Technology Project: OSGeo Certification</p>
<hr />
<div>#REDIRECT [[OSGeo Technology Project: OSGeo Certification]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Technology_Project:_OSGeo_Certification&diff=97158OSGeo Technology Project: OSGeo Certification2016-03-06T22:12:08Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: OSGeo Certification to OSGeo Technology Project: OSGeo Certification</p>
<hr />
<div>== Basic Project Data ==<br />
*'''Project Name:''' OSGeo Certification<br />
*'''Project Status Condition:'''<br />
*'''Project Web Site:''' [[OSGeo Certification]]<br />
*'''Project Contact:''' [http://wiki.osgeo.org/wiki/User:Fjbehr Franz-Josef Behr]<br />
*'''Short Project Description:''' This project develops a draft of an OSGeo Certification model to contribute to the professional certification of people working for and with open source geospatial software and data.<br />
<br />
== Project History ==<br />
*'''FOSS4G 2014, Portland:''' First consultations<br />
*'''FOSS4G Europe 2015, Como, 2015-07-14:''' GeoForAll Preconference Meeting<br />
*'''FOSS4G Europe 2015, Como, 2015-07-16:''' OSGeo Certification BOF Meeting. The participants ([[Arnulf Christl]], [[User:jachym|Jáchym Čepický]], [[User:kotzino|Dimitris Kotzinos]], Phillip Davis, [[User:Darsvid|Daria Svidzinska]], [[User:Fjbehr|Franz-Josef Behr]]) agree that the certification model developed by Tanzeel Khan (presented on Tuesday) should be used as starting point for the OSGeo Certification project.<br />
<br />
== Project Infrastructure ==<br />
*'''Project Source Code:''' not applicable.<br />
*'''Project Mailing List:'''<br />
*'''Project Version Control Repository:'''<br />
*'''Project Bug Tracker:''' No bug tracker.<br />
*'''Project Feature Request Tracker:''' No feature request tracker.<br />
<br />
== Project Governance ==<br />
*'''Source Code License:''' <br />
*'''Documentation License:''' Creative Commons Attribution-ShareAlike 3.0 United States<br />
*'''Copyright Assignment Policy:''' <br />
*'''Decision Making Procedure:''' <br />
*'''Coding Standards:''' None<br />
*'''Release Procedure:''' None<br />
<br />
== Project Deliverables ==<br />
*'''Latest Project Release:''' No release yet. Code is still in alpha.<br />
<br />
[[Category: OSGeo Labs]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Labs:_PyWPS&diff=97157OSGeo Labs: PyWPS2016-03-06T22:11:58Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: PyWPS to OSGeo Technology Project: PyWPS</p>
<hr />
<div>#REDIRECT [[OSGeo Technology Project: PyWPS]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=PyWPS&diff=97156PyWPS2016-03-06T22:11:58Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: PyWPS to OSGeo Technology Project: PyWPS</p>
<hr />
<div>== Basic Project Data ==<br />
*'''Project Name:''' PyWPS<br />
*'''Project Status Condition:''' Mature<br />
*'''Project Web Site:''' http://pywps.wald.intevation.org<br />
*'''Project Contact:''' [[User:jachym]] http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev<br />
*'''Short Project Description:''' Implementation of OGC Web Processing Service (OGC WPS) 1.0.0 standard on the server side in Python programming language.<br />
<br />
== Project Infrastructure ==<br />
*'''Project Source Code:''' https://github.com/geopython/PyWPS<br />
*'''Project Mailing List:''' <strike>http://lists.wald.intevation.org/mailman/listinfo/pywps-devel and</strike> http://lists.osgeo.org/cgi-bin/mailman/listinfo/pywps-dev<br />
*'''Project Version Control Repository:''' https://github.com/geopython/PyWPS<br />
*'''Project Bug Tracker:''' https://github.com/geopython/PyWPS<br />
*'''Project Feature Request Tracker:''' https://github.com/geopython/PyWPS<br />
<br />
== Project Governance ==<br />
*'''Source Code License:''' GNU/GPL NOTE: Considering licence change for new version (written from scratch)<br />
*'''Documentation License:''' TBD<br />
*'''Copyright Assignment Policy:''' NONE<br />
*'''Decision Making Procedure:''' Consensus<br />
*'''Coding Standards:''' No specific, follow http://www.python.org/dev/peps/pep-0008/ as much as possible<br />
*'''Release Procedure:''' When consensus reached, new version released.<br />
<br />
== Project Deliverables ==<br />
*'''Latest Project Release:''' 3.2.1 2011-09-06<br />
<br />
[[Category: OSGeo Labs]]<br />
<br />
== PyWPS Incubation ==<br />
<br />
Originally started at https://trac.osgeo.org/osgeo/ticket/337 (2009-02-27) moved here for more collaborative work<br />
<br />
NOTE: meanwhile: PyWPS moved to GitHub, started work on PyWPS-4.<br />
<br />
Later in this text: PyWPS-3 is current (2014-04) stable version. PyWPS-4 is current development version with completely new code base.<br />
<br />
Project name:<br />
:'''PyWPS'''<br />
<br />
Project homepage:<br />
: http://pywps.wald.intevation.org<br />
<br />
Please provide the name and email address of the principal Project Owner.:<br />
: Jachym Cepicky, jachym.cepicky at gmail.com<br />
<br />
Please provide the names and emails of co-project owners (if any).:<br />
: none<br />
<br />
Please provide the names, emails and entity affiliation of all official committers:<br />
: '''PyWPS-3'''<br />
: Jachym Cepicky, jachym.cepicky gmail com, Initial autor, core developer, coordinator of development<br />
: Lorenzo Becchi, lorenzo at ominiverdi com, Initial autor of GUI, ka-Map Developer<br />
: Luca Casagrande, luca.casagrande at gmail com, Initial autor of GUI, ka-Map Developer<br />
: Sebastian Holler, sh at sholler de, core developer<br />
: Panagiotis Skintzos, p at pskintzos net, core developer<br />
: Jorge de Jesus, jorge.de-jesus jrc it, Power user, testing<br />
<br />
: '''PyWPS-4'''<br />
: Alex Morega, alex grep ro, https://github.com/mgax, architecture of PyWPS-4<br />
: Jachym Cepicky, jachym.cepicky gmail com, https://github.com/jachym, architecture of PyWPS-4<br />
: Calin Ciociu, calin.ciociu gmail com, https://github.com/Noctalin, architecture of PyWPS-4<br />
: Luís de Sousa, luis.a.de.sousa gmail com, https://github.com/ldesousa, development of PyWPS-4<br />
<br />
<br />
Please describe your Project.:<br />
:PyWPS (Python Web Processing Service) implements the OGC(r)'s Web Processing Service as a Python API on Apache Server using CGI requests.<br />
<br />
Why is hosting at OSGeo good for your project?:<br />
: We want to share the infrastructure, connect with other projects, provide the support for easy server-side scripting, as well as know-how and code for WPS clients. We want to be closer part of OSGeo Community.<br />
: In fact, we just need some of the parts of OSGeo infrastructure, currently mainly the mailing list<br />
<br />
Type of application does this project represent(client, server, standalone, library, etc.):<br />
: Server and Python API<br />
<br />
Please describe any relationships to other open source projects.:<br />
: PyWPS is written with direct support for GRASS GIS, allowing from GRASS modules to run as server-programs. However, connection to GDAL/OGR, PROJ.4, Python Interfaces and Rpy or any other command line tools is possible.<br />
<br />
Please describe any relationships with commercial companies or products.:<br />
: PyWPS-3 is independent project released under GNU/GPL licence. It's development is (currently) supported mainly by Help Service - Remote Sensing company (Czech) through Prezem http://www.prezem.cz/ project.<br />
: PyWPS-4 uses MIT license, not used yet anywhere<br />
<br />
Which open source license(s) will the source code be released under?:<br />
: PyWPS-3 GNU/GPL<br />
: PyWPS-4 MIT<br />
<br />
Is there already a beta or official release?:<br />
: There is 3.2.x release and currently, 3.2.x branch is on the schedule.<br />
: PyWPS-4 is still in early development phase<br />
<br />
What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)?:<br />
: Commercial, experimental, government, education<br />
<br />
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?:<br />
: PyWPS is a OGC WPS 1.0.0 implemenation. It has not been certified yet. After testing the PyWPS API using the test suite described in Annex A of the OpenGIS Web Processing Service version 1.0.0 (OGC 05-007r6) and Annex A of the OGC Web Services Common Specifications (OGC 06-121r3), it will be requested a OGC certification, now when OGC CITE tests are at hand.<br />
: PyWPS-4 will be supporting new WPS-2.0.0 standard too<br />
<br />
Is the code free of patents, trademarks, and do you control the copyright?:<br />
:Yes.<br />
<br />
How many people actively contribute (code, documentation, other?) to the project at this time?:<br />
: PyWPS-3 - 9<br />
: PyWPS-4 - 4<br />
<br />
How many people have commit access to the source code repository?:<br />
: PyWPS-3: 9 https://github.com/geopython/PyWPS/graphs/contributors<br />
: PYWPS-4: 4 https://github.com/jachym/pywps-4/graphs/contributors<br />
<br />
Approximately how many users are currently using this project?:<br />
:There are 45 Non-digested Members of the mailing list.<br />
<br />
What type of users does your project attract (government, commercial, hobby, academic research, etc. )?:<br />
: Precise Farming calculation in Prezem project http://www.prezem.cz/<br />
: PyWPS has attracted the attention of the INTAMAP research project (www.intamap.org) , as one of the WPS API's responsible for client/server interaction for automatic interpolation mapping and cross validation of results.<br />
: PyWPS is also beeing using with OpenLayers and Ka-maps client (Embrio).<br />
: Plymouth Marine Laboratory are currently developing WPS processes using PyWPS for use in an EU funded project http://interrisk.nersc.no/. PML have recommended PyWPS to other project members with at least one other so far developing a new service.<br />
: University of Perugia ( Italy) is developing a DSS for water management which uses pyWPS in a tool for withdrawals handling.<br />
: International Office for Water is developping two WPS based on PyWPS :<br />
: One is for the French Information System on Water and is calculating various information for a given watercourse (e.g : the land occupation based on Corine Land Cover for the watercourse's catchment).<br />
: One is to help Regional Directorate for Industry, Research and the Environment in their discharge points identification. It will identify all Water Framework Directive waterbodies potentially impacted by a given discharge point.<br />
<br />
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 />
: PyWPS is long time considered as one of affiliate projects. We are members of OSGeo family.<br />
<br />
Does the project include an automated build and test?:<br />
: As for PyWPS-3 Partly. Since the project uses python setup script, it is possible to build it on any system. Standard example processes are included for testing purposes. Further development will fallow to full fill OGC's test suits (see point) 12<br />
: For PyWPS-4: test driven development is introduced. We use Tox and setup the environment for Python-2 and Python-3. For every push, Travis hook is running the automated test suite.<br />
<br />
What language(s) are used in this project? (C/Java/perl/etc):<br />
: PyWPS-3 Python. Partly PHP (outdated). In the future, PHP, JavaScript? and others (clinents examples) should be used. However, Python will be always the main programming language.<br />
: PyWPS-4 is pure Python (2 and 3)<br />
<br />
What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers?:<br />
: English (with some documentation also written in French)<br />
<br />
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 />
: PyWPS-3 cca 300 Kb. no idea :-) See q. no. 16<br />
: PyWPS-4, still early development, currently it's about 400 Kb</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Labs:_Virtual_Terrain_Project&diff=97155OSGeo Labs: Virtual Terrain Project2016-03-06T22:11:48Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: Virtual Terrain Project to OSGeo Technology Project: Virtual Terrain Project</p>
<hr />
<div>#REDIRECT [[OSGeo Technology Project: Virtual Terrain Project]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Virtual_Terrain_Project&diff=97154Virtual Terrain Project2016-03-06T22:11:48Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: Virtual Terrain Project to OSGeo Technology Project: Virtual Terrain Project</p>
<hr />
<div>== Basic Project Data ==<br />
*'''Project Name:''' VTP<br />
*'''Project Status Condition:''' Active<br />
*'''Project Web Site:''' http://vterrain.org/<br />
*'''Project Contact:''' ben@vterrain.org<br />
*'''Short Project Description:''' Realtime 3D visualization of geodata<br />
<br />
== Project Infrastructure ==<br />
*'''Project Source Code:''' http://code.google.com/p/vtp/source/<br />
*'''Project Mailing List:''' http://groups.yahoo.com/group/vtp/<br />
*'''Project Version Control Repository:''' http://code.google.com/p/vtp/source/browse/<br />
*'''Project Bug Tracker:'''<br />
*'''Project Feature Request Tracker:'''<br />
<br />
== Project Governance ==<br />
*'''Source Code License:''' MIT/X License<br />
*'''Documentation License:'''<br />
*'''Copyright Assignment Policy:'''<br />
*'''Decision Making Procedure:'''<br />
*'''Coding Standards:'''<br />
*'''Release Procedure:'''<br />
<br />
== Project Deliverables ==<br />
*'''Latest Project Release:''' 1.49 (2012.02.02)<br />
<br />
[[Category: OSGeo Labs]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Labs:_pycsw&diff=97153OSGeo Labs: pycsw2016-03-06T22:11:29Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: pycsw to OSGeo Technology Project: pycsw</p>
<hr />
<div>#REDIRECT [[OSGeo Technology Project: pycsw]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Pycsw&diff=97152Pycsw2016-03-06T22:11:29Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: pycsw to OSGeo Technology Project: pycsw</p>
<hr />
<div><br />
<big>'''NOTE: pycsw has graduated as an OSGeo project (March 2015).'''</big><br />
<br />
== Basic Project Data ==<br />
*'''Project Name:''' pycsw<br />
*'''Project Status Condition:''' Stable, Adult<br />
*'''Project Web Site:''' [http://pycsw.org http://pycsw.org]<br />
*'''Project Contact:''' [http://wiki.osgeo.org/wiki/Angelos_Tzotsos Angelos Tzotsos]<br />
*'''Short Project Description:''' pycsw is an OGC CSW server implementation written in Python. pycsw fully implements the OpenGIS Catalogue Service Implementation Specification [Catalogue Service for the Web]. Initial development started in 2010 (more formally announced in 2011). The project is certified OGC Compliant, and is an OGC Reference Implementation. pycsw allows for the publishing and discovery of geospatial metadata. Existing repositories of geospatial metadata can also be exposed via OGC:CSW 2.0.2, providing a standards-based metadata and catalogue component of spatial data infrastructures.<br />
<br />
== Project Infrastructure ==<br />
*'''Project Source Code:''' https://github.com/geopython/pycsw<br />
*'''Project Mailing List:''' https://lists.osgeo.org/mailman/listinfo/pycsw-devel<br />
*'''Project Version Control Repository:''' https://github.com/geopython/pycsw.git<br />
*'''Project Bug Tracker:''' https://github.com/geopython/pycsw/issues<br />
*'''Project Feature Request Tracker:''' https://github.com/geopython/pycsw/issues<br />
<br />
== Project Governance ==<br />
*'''Source Code License:''' http://pycsw.org/docs/license.html<br />
*'''Documentation License:''' http://pycsw.org/docs/license.html<br />
*'''Copyright Assignment Policy:''' Copyright is assigned to committers<br />
*'''Decision Making Procedure:''' Through mailing list voting and IRC meetings (#pycsw at FreeNode)<br />
*'''Coding Standards:''' [http://www.python.org/dev/peps/pep-0008/ PEP 8]<br />
*'''Release Procedure:''' https://github.com/geopython/pycsw/wiki/Release-Packaging<br />
<br />
== Project Deliverables ==<br />
*'''Latest Project Release:''' [http://download.osgeo.org/pycsw/ 1.4.1] - 26 March 2013<br />
<br />
[[Category: OSGeo Labs]]<br />
[[Category:pycsw]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Labs:_MapProxy&diff=97151OSGeo Labs: MapProxy2016-03-06T22:11:22Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: MapProxy to OSGeo Technology Project: MapProxy</p>
<hr />
<div>#REDIRECT [[OSGeo Technology Project: MapProxy]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=MapProxy&diff=97150MapProxy2016-03-06T22:11:21Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: MapProxy to OSGeo Technology Project: MapProxy</p>
<hr />
<div>== Basic Project Data ==<br />
*'''Project Name:''' MapProxy<br />
*'''Project Status Condition:''' Stable<br />
*'''Project Web Site:''' http://mapproxy.org<br />
*'''Project Documentation:''' http://mapproxy.org/documentation.html<br />
*'''Project Contact:''' Oliver Tonnhofer <olt at omniscale.de><br />
*'''Short Project Description:''' MapProxy is a tile cache and WMS proxy.<br />
<br />
== Project Infrastructure ==<br />
*'''Project Source Code:''' https://github.com/mapproxy/mapproxy<br />
*'''Project Mailing List:''' http://lists.osgeo.org/mailman/listinfo/mapproxy<br />
*'''Project Version Control Repository:''' git://github.com/mapproxy/mapproxy.git<br />
*'''Project Developer Documentation:''' http://mapproxy.org/docs/nightly/deployment.html<br />
*'''Project Bug Tracker:''' https://github.com/mapproxy/mapproxy/issues<br />
*'''Project Feature Request Tracker:''' ditto<br />
<br />
== Project Governance ==<br />
*'''Source Code License:''' [http://www.apache.org/licenses/LICENSE-2.0.html Apache License 2.0]<br />
*'''Documentation License:''' ditto<br />
*'''Copyright Assignment Policy:''' All contributions are licensed under the terms of the Apache License 2.0 without explicit assignment (see [http://www.apache.org/licenses/LICENSE-2.0.html license])<br />
*'''Decision Making Procedure:''' [http://en.wikipedia.org/wiki/Benevolent_Dictator_for_Life BDFL], at least for now.<br />
*'''Coding Standards:''' [http://www.python.org/dev/peps/pep-0008/ PEP8]<br />
*'''Release Procedure:''' Major/minor releases. Beta and release candidates as necessary.<br />
<br />
== Project Deliverables ==<br />
*'''Latest Project Release:''' http://pypi.python.org/pypi/MapProxy<br />
<br />
[[Category: OSGeo Labs]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Labs:_PAGC&diff=97149OSGeo Labs: PAGC2016-03-06T22:11:06Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: PAGC to OSGeo Technology Project: PAGC</p>
<hr />
<div>#REDIRECT [[OSGeo Technology Project: PAGC]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Postal_Address_Geo-Coder&diff=97148Postal Address Geo-Coder2016-03-06T22:11:05Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: PAGC to OSGeo Technology Project: PAGC</p>
<hr />
<div>== Basic Project Data ==<br />
*'''Project Name:''' Postal Address Geo-Coder Wiki<br />
*'''Project Status Condition:''' <br />
*'''Project Web Site:''' http://www.pagcgeo.org/<br />
*'''Project Contact:'''<br />
*'''Short Project Description:'''<br />
<br />
== Project Infrastructure ==<br />
*'''Project Source Code:'''<br />
*'''Project Mailing List:'''<br />
*'''Project Version Control Repository:'''<br />
*'''Project Bug Tracker:'''<br />
*'''Project Feature Request Tracker:'''<br />
<br />
== Project Governance ==<br />
*'''Source Code License:''' MIT License<br />
*'''Documentation License:'''<br />
*'''Copyright Assignment Policy:'''<br />
*'''Decision Making Procedure:'''<br />
*'''Coding Standards:'''<br />
*'''Release Procedure:'''<br />
<br />
== Project Deliverables ==<br />
*'''Latest Project Release:'''<br />
<br />
[[Category: OSGeo Labs]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Labs:_pgRouting&diff=97147OSGeo Labs: pgRouting2016-03-06T22:10:57Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: pgRouting to OSGeo Technology Project: pgRouting</p>
<hr />
<div>#REDIRECT [[OSGeo Technology Project: pgRouting]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=PgRouting&diff=97146PgRouting2016-03-06T22:10:56Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: pgRouting to OSGeo Technology Project: pgRouting</p>
<hr />
<div>== Basic Project Data ==<br />
*'''Project Name:''' pgRouting<br />
*'''Project Status Condition:''' Stable<br />
*'''Project Web Site:''' http://pgrouting.org<br />
*'''Project Contact:''' Daniel Kastl <project at pgrouting.org><br />
*'''Short Project Description:''' pgRouting adds routing functionality to PostGIS.<br />
<br />
== Project Infrastructure ==<br />
*'''Project Source Code:''' https://github.com/pgrouting/pgrouting<br />
*'''Project Mailing List:''' http://lists.osgeo.org/mailman/listinfo/pgrouting-users<br />
*'''Project Version Control Repository:''' git://github.com/pgRouting/pgrouting.git<br />
*'''Project Bug Tracker:''' https://github.com/pgrouting/pgrouting/issues<br />
*'''Project Feature Request Tracker:''' https://github.com/pgrouting/pgrouting/issues<br />
<br />
== Project Governance ==<br />
*'''Source Code License:''' [http://www.gnu.org/licenses/gpl-2.0.html GNU General Public License, version 2]<br />
*'''Documentation License:''' [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-Share Alike 3.0]<br />
*'''Copyright Assignment Policy:''' All contributions are licensed under the terms of the GNU General Public License, version 2 without explicit assignment<br />
*'''Decision Making Procedure:''' Project Steering Committee<br />
*'''Coding Standards:''' https://github.com/pgRouting/pgrouting/wiki/2.0-Development-Guidelines-and-Standards<br />
*'''Release Procedure:''' https://github.com/pgRouting/pgrouting/wiki/pgRouting-Release-Process-Checklist<br />
<br />
== Project Deliverables ==<br />
*'''Latest Project Release:''' Version 2.0.0 (September 2013)<br />
<br />
[[Category: OSGeo Labs]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Labs:_Geoinformatica&diff=97145OSGeo Labs: Geoinformatica2016-03-06T22:10:21Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: Geoinformatica to OSGeo Technology Project: Geoinformatica</p>
<hr />
<div>#REDIRECT [[OSGeo Technology Project: Geoinformatica]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Geoinformatica&diff=97144Geoinformatica2016-03-06T22:10:21Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs: Geoinformatica to OSGeo Technology Project: Geoinformatica</p>
<hr />
<div>== Basic Project Data ==<br />
*'''Project Name:''' Geoinformatica (names of the subprojects include libral and Gtk2-Ex-Geo among others)<br />
*'''Project Status Condition:''' Adult, but without a marketing and growth plan; and no strict governance<br />
*'''Project Web Site:''' [http://geoinformatics.aalto.fi/software.shtml geoinformatics.aalto.fi]<br />
*'''Project Contact:''' Ari Jolma (ari.jolma at aalto.fi)<br />
*'''Short Project Description:''' Geoinformatica is made of a part in C, libral, and several Perl packages, which build on GDAL and GTK+ Perl bindings. libral is a simple raster algebra package at heart, but includes a simple visualization library to render GDAL rasters and vectors to a memory canvas (pixbuf), which can be given to GDK (a GTK+ subsystem).<br />
<br />
== Project Infrastructure ==<br />
*'''Project Source Code:''' <br />
*'''Project Mailing List:''' [https://list.hut.fi/mailman/listinfo/geo-perl list.hut.fi/mailman/listinfo/geo-perl] (The future of this list is uncertain)<br />
*'''Project Version Control Repository:''' [https://github.com/ajolma/geoinformatica github.com/ajolma/geoinformatica]<br />
*'''Project Bug Tracker:''' Use the one in GitHub (for CPAN modules rt.cpan.org)<br />
*'''Project Feature Request Tracker:''' Use the one in GitHub<br />
<br />
== Project Governance ==<br />
*'''Source Code License:''' LGPL and Artistic Licence<br />
*'''Documentation License:''' No licence<br />
*'''Copyright Assignment Policy:''' Copyright remains by the author<br />
*'''Decision Making Procedure:''' Not fixed<br />
*'''Coding Standards:''' K&R, perlstyle<br />
*'''Release Procedure:''' Not fixed<br />
<br />
== Project Deliverables ==<br />
*'''Latest Project Release:''' 16 Jun 2012<br />
<br />
[[Category:OSGeo Labs]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Community_Projects&diff=97143OSGeo Community Projects2016-03-06T22:09:56Z<p>Wiki-Surveyor: </p>
<hr />
<div>= OSGeo Labs Projects =<br />
<br />
See http://wiki.osgeo.org/wiki/Category:OSGeo_Technology_Projects<br />
<br />
== Purpose ==<br />
OSGeo Technology Project is an umbrella for open source geospatial software projects that would like to become OSGeo projects in the future, but that aren't ready for incubation quite yet. It is appropriate to submit your new or experimental project as an OSGeo Technology Project.<br />
<br />
The volunteers that work as part of OSGeo Technology Projects have the goal of helping OSGeo Technology Project qualify for incubation. To reach this goal,OSGeo Technology Project volunteers help OSGeo Technology Project with the following tasks:<br />
<br />
* Project marketing.<br />
* Development of user and programmer communities.<br />
* Establishment of programs and policies for project documentation, copyright assignment, and licensing.<br />
* Establishment of programs and policies for software development. This includes version tracking, bug tracking, and feature request tracking, creation of a development road map, and organization of code sprints/events.<br />
* Establishment of project governance programs and policies.<br />
* Collaboration on technical standards, data formats, and code sharing with other open source geospatial software projects.<br />
* Utilization of software development infrastructure like mailing lists, bug trackers, version control software/hosting, and web hosting.<br />
<br />
== OSGeo Technology Project Selection Criteria ==<br />
Projects should only submit themselves for inclusion in OSGeo Technology Project if they follow the OSGeo Incubation principles.<br />
# The code is under an OSI approved license (data & doc projects need to specify their choice for a type of license).<br />
# The project is willing to keep code clear of encumbrances<br />
# The project is "geospatial", or directly supports geospatial applications.<br />
# The project hopes to become a graduated OSGeo project,.<br />
<br />
==Becoming a OSGeo Technology Project==<br />
The goal is to keep the submission process for OSGeo Technology Project as simple and painless as possible. (The OSGeo Incubation Process is hard enough.) To submit your software project for inclusion in OSGeo Technology Project, simply send a description of the project to the [http://lists.osgeo.org/mailman/listinfo/incubator OSGeo Incubation Committee Mailing List], or [mailto:sunburned.surveyor@gmail.com e-mail Landon Blake.]<br />
<br />
==OSGeo Technology Project Set-Up Process==<br />
Once a project has been accepted into OSGeo Technology Project, the OSGeo Technology Project volunteers will help the projects take these steps:<br />
# Selection of an open source license if the project hasn't already done so.<br />
# Creation a home page for the project. The OSGeo wiki is recommended for this page. <br />
# Announce and discuss the project on the [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss] email list.<br />
# Set the project software development up on the OSGeo infrastructure if appropriate. (Sourceforge or other software development hosting sites can be used as an alternative.)<br />
<br />
== OSGeo Technology Project Status Conditions ==<br />
<br />
We’ve designed an informal “status” system to assist programmers and users evaluate projects in OSGeo Labs. Each project in labs is assigned one (1) of five (5) status conditions. The following factors are used to determine the status condition of the projects:<br />
<br />
1) Source Code Completeness<br />
2) Source Code Stability<br />
3) Community Support (Mailing Lists, Documentation, Tutorials)<br />
4) Project Deliverables (Programming Libraries and/or Executables)<br />
5) Project Infrastructure (Source Code Versioning, Bug Trackers, Feature Trackers, Web Site, Mailing Lists, Discussion Forums)<br />
6) Project Governance (Decision Making Processes, Licensing, Copyright Assignment, Release Schedule, Coding Standards)<br />
7) Community Activity<br />
8) Marketing and Outreach<br />
<br />
Below are the different status conditions that can be assigned to a project in OSGeo Technology Project.<br />
<br />
* '''Seed''': This project is in the conceptual stage. There may be some source code written, but it is incomplete or very experiemental. The project may lack deliverables, community support, project infrastructure, project governance, community activity, or marketing and outreach.<br />
<br />
* '''Seedling''': This project is moving beyond the conceptual stage with some concrete code. However the code is still experimental and isn't stable. Projects at this status level could still experience a lot of change in their code base. This project should start to have some project infrastructure and some basic documentation.<br />
<br />
* '''Sapling''': This project has functional source code, although it may not be "mature and feature rich". For example, the code may only be usable as a programming library or a command line tool instead of featuring a GUI. The project has started to support users and programmers with communication tools, trackers, and documentation. The project has started to think about project governance and marketing, perhaps creating plans in these areas that are not fully implemented.<br />
<br />
* '''Adult''': This project has a usable and user friendly deliverable, like an executable program or a stable and well-deocumented programming library. The project is supporting users and programmers with communication tools, trackers, and documentation. It has started the initial phases of incubation. This includes addressing issues of copyright, licensing, and project governance. The project also has a marketing and community growth plan and has started to implement the plan.<br />
<br />
== Member Projects ==<br />
* [[OSGeo Labs: Geoinformatica]]<br />
* [[OSGeo Labs: pgRouting]]<br />
* [[OSGeo Labs: PAGC]]<br />
* [[OSGeo Labs: MapProxy]]<br />
* [[OSGeo Labs: pycsw]]<br />
* [[OSGeo Labs: Virtual Terrain Project]]<br />
* [[OSGeo Labs: PyWPS]]<br />
* [[OSGeo Labs: OSGeo Certification]]<br />
<br />
== Archive ==<br />
<br />
There is an archive of the old OSGeo Technology Projects page at [[OSGeo Labs Page Archive]].</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Talk:OSGeo_Community_Projects&diff=97141Talk:OSGeo Community Projects2016-03-06T22:06:26Z<p>Wiki-Surveyor: Surveyor moved page Talk:OSGeo Labs to Talk:OSGeo Incubation Technology Projects</p>
<hr />
<div>Some Ideas on what to do with OSGeo Labs to better utilize it for recruitment of projects, contributors and community.<br />
<br />
<br />
== Idea 1 ==<br />
This is just one grouping of ideas, please feel free to comment and add alternate ideas.<br />
<br />
'''What is OSGeo Labs?'''<br />
A place to encourage the growth and sustainability of open source geospatial applications.<br />
<br />
(Short Version)<br />
''How this is different from the current: we're thinking of an launchpage to a list of Labs projects, projects fill out a form (like the questionarre below) to get listed, the catalog of these is then searchable/sortable, Labs becomes the minimum bar for any group requesting things like mailing list from [[SAC]] and help set marketing priorities for things like the [[Live DVD]] and it also becomes a way to recruit good project, demonstrate affinity with OSGeo and show OSGeo's role in fostering the future''<br />
<br />
(Full Version)<br />
''<br />
Why would my project want to join?<br />
''<br />
* Encourage your project to adopt sustainable development practices(Adverstise that your project aims to achieve sustainable development practices.)<br />
** To help find additional developers<br />
** To expand the user community<br />
** Create a dialog between the users and developers<br />
** Form some type of Project Steering Committee<br />
*** A place to work on defining the workflow for patches, translations, documentation<br />
** Get help picking the right license for your project<br />
** Get help coming up with a long term road map<br />
* Access to OSGeo infrastructure and marketing (varied by project and availability)<br />
* Figure out if applying to be an OSGeo project is right for your project (Applying for incubation)<br />
* Demonstrate your projects willingness to be part of an open, collaborative community<br />
* Show you affiliation with OSGeo and it's projects<br />
* Increase your visibility among the Open Source Geospatial Community<br />
* Potential Cross project collaboration<br />
<br />
What type of projects should join?<br />
<br />
* Anything related to open geospatial topics (Need not be a software project directly)<br />
* That can be licensed under an OSI approved open source license<br />
* Does not contain any patents subject to license restrictions<br />
* Have a willingness to explore expanding the current community and increase participation.<br />
<br />
Why might OSGeo labs be a better place for my project instead of OSGeo Project Incubation?<br />
* Projects related to Open Data Access (OpenAerialMap), Open Education(Free GIS Book), OSGeo Live DVD|Virtual Machine etc.<br />
* Maybe you don't meet all the requirements to be an OSGeo project, yet<br />
* Not sure how to take your project fully open source/community based yet but still want to encourage patches/participation from the community<br />
* Aren't quite ready to decide the future direction of the project<br />
* Haven't worked out licensing and patents yet<br />
* Project is still in the planning stages with little or no working code<br />
<br />
What does OSGeo offer Lab's projects? (These are all opt in services)<br />
* mailing lists<br />
* source code hosting (depends on resource availability)<br />
* wiki space<br />
* marketing exposure<br />
** Inclusion on the OSGeo Live project<br />
** Awareness at conference booths<br />
** Web Presence at OSGeo a meeting place of open source geospatial<br />
* A path towards project incubation – If you're thinking about applying for incubation take a step towards that goal by joining OSGeo labs.<br />
* Even if your project falls by the wayside from lack of interest, OSGeo can assure an archive of the code in case others will find it useful sometimein the future.<br />
* an OSGeo labs logo you can put on your website and marketing materials<br />
* Participation in Google Summer of Code under OSGeo<br />
<br />
What do I have to do to join?<br />
* List your project on the OSGeo Labs project page<br />
** Include contact information<br />
** Links to current code<br />
** Licensing status<br />
* Occasionally OSGeo will go through and verify compliance with the basic rules of OSGeo Labs and notify your project if you're out of compliance (and then remove if it's not fixable or you won't fix it)<br />
<br />
New Project Questionnaire/Checklist: (This could also just be a reworked version of the Incubation Application)<br />
This serves multiple purposes: Introduces the project to prospective participants and users, helps you asses the state of your project and compare against full Project and Projects in Incubation<br />
<br />
1. Whats the name?<br />
2. What does it do?<br />
1. Programming Languages<br />
2. Desktop, Web, Database, Library, etc?<br />
3. What makes it different from other similar stuff?<br />
4. Do you have a roadmap? URL?<br />
3. Community<br />
1. How many people have commit access<br />
2. How many people other than committers submit patches, documentation, webpages, on a regular basis?<br />
3. If you have mailing list(s), how many unique subscribers, how many email/week?<br />
4. Contact/Governance<br />
1. If you have a website, URL?<br />
2. Who owns the Copyrights? Patents?<br />
3. Do you have a governance model (Steering Committee, etc)?<br />
4. Who is the main contact(s) for the project?<br />
5. Other<br />
1. Are you looking for more ideas to get started?<br />
2. Do you want more coders?<br />
3. Need help with anything in particular pertaining to Governance, Licensing, etc.?<br />
<br />
A note on a gentle way to push projects to join: Or call it a Rewards system:<br />
Google Summer of Code - OSGeo Project, Incubation, Labs will always be ranked higher than non registered applications (ie MapWindow)<br />
OSGeo Live - We're reaching disc capacity so will have to start turning down applications and prioritizing; OSGeo Project, Incubation, Labs take priority over all other applications no matter how good the other stuff is (ie mapnik, kosmo, spatialite, geopublisher <- we should be inviting all of these)<br />
Website should be labs.osgeo.org or osgeo.org/labs with main page possibly having a status update showing recent activity in labs or a way to find stuff in labs.<br />
<br />
This should push projects that really ought to be part of OSGeo in some way to start down the path, without us having to be very harsh, considering how easy it is to join.<br />
<br />
Projects to invite/encourage:<br />
* mapnik<br />
* kosmo<br />
* openjump<br />
* geopublisher<br />
* marble<br />
* osgearth<br />
* Mapwindow<br />
* ILWIS<br />
* SAGA<br />
* Opticks<br />
* liblas (propose merge with GDAL/OGR?)<br />
* Various R Spatial View packages<br />
* GeoJQuery (Maybe it can merge with GeoExt to be GeoJS with multiple downloads for Ext only/Jquery only, Both - you know some will do both)<br />
* GeoKettle<br />
* OpenCPN<br />
* Octave Mapping Toolbox<br />
* MapTiler<br />
* A bunch of things that applied for incubation that clearly are not ready for incubation. (In my mind there needs to be clear community interest and involvement in a project to consider it)<br />
<br />
I'm well aware there are more floating around that people have mentioned recently.<br />
<br />
Benefits to OSGeo:<br />
* Demonstrate our role in the Open Source Geospatial Community<br />
* Have projects acknowledge their affiliation (Plenty of projects come to FOSS4G and have people on our lists but don't necessarily link to us on their pages or tell people about us in local context)<br />
* Give us a way to encourage merging, collaboration, new project initiation.<br />
* Provide a map to applying for Incubation.<br />
* By instilling good community principles it helps to highlight what makes OSGeo stuff different from a random OSS project on the internet.<br />
* More projects in the Labs is a bigger pool of people for FOSS4G, local chapters, etc.<br />
<br />
----</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Community_Projects&diff=97139OSGeo Community Projects2016-03-06T22:06:25Z<p>Wiki-Surveyor: Surveyor moved page OSGeo Labs to OSGeo Incubation Technology Projects</p>
<hr />
<div>= OSGeo Labs Projects =<br />
<br />
See http://wiki.osgeo.org/wiki/Category:OSGeo_Labs<br />
<br />
== Purpose ==<br />
OSGeo Labs is an umbrella for open source geospatial software projects that would like to become OSGeo projects in the future, but that aren't ready for incubation quite yet. It is appropriate to submit your new or experimental project as an OSGeo labs project.<br />
<br />
The volunteers that work as part of OSGeo Labs have the goal of helping OSGeo Labs Projects qualify for incubation. To reach this goal, OSGeo Labs volunteers help OSGeo Labs Projects with the following tasks:<br />
<br />
* Project marketing.<br />
* Development of user and programmer communities.<br />
* Establishment of programs and policies for project documentation, copyright assignment, and licensing.<br />
* Establishment of programs and policies for software development. This includes version tracking, bug tracking, and feature request tracking, creation of a development road map, and organization of code sprints/events.<br />
* Establishment of project governance programs and policies.<br />
* Collaboration on technical standars, data formats, and code sharing with other open source geospatial software projects.<br />
* Utilization of software development infrastructure like mailing lists, bug trackers, version control software/hosting, and web hosting.<br />
<br />
== OSGeo Labs Project Selection Criteria ==<br />
Projects should only submit themselves for inclusion in OSGeo Labs if they follow the OSGeo Incubation principles.<br />
# The code is under an OSI approved license (data & doc projects need to specify their choice for a type of license).<br />
# The project is willing to keep code clear of encumbrances<br />
# The project is "geospatial", or directly supports geospatial applications.<br />
# The project hopes to become a graduated OSGeo project,.<br />
<br />
==Becoming a Labs Project==<br />
The goal is to keep the submission process for OSGeo Labs as simple and painless as possible. (The OSGeo Incubation Process is hard enough.) To submit your software project for inclusion in OSGeo Labs, simply send a description of the project to the [http://lists.osgeo.org/mailman/listinfo/incubator OSGeo Incubation Committee Mailing List], or [mailto:sunburned.surveyor@gmail.com e-mail Landon Blake.]<br />
<br />
==OSGeo Labs Set-Up Process==<br />
Once a project has been accepted into OSGeo Labs, the OSGeo Labs volunteers will help the projects take these steps:<br />
# Selection of an open source license if the project hasn't already done so.<br />
# Creation a home page for the project. The OSGeo wiki is recommended for this page. <br />
# Announce and discuss the project on the [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss] email list.<br />
# Set the project software development up on the OSGeo infrastructure if appropriate. (Sourceforge or other software development hosting sites can be used as an alternative.)<br />
<br />
== Labs Project Status Conditions ==<br />
<br />
We’ve designed an informal “status” system to assist programmers and users evaluate projects in OSGeo Labs. Each project in labs is assigned one (1) of five (5) status conditions. The following factors are used to determine the status condition of the projects:<br />
<br />
1) Source Code Completeness<br />
2) Source Code Stability<br />
3) Community Support (Mailing Lists, Documentation, Tutorials)<br />
4) Project Deliverables (Programming Libraries and/or Executables)<br />
5) Project Infrastructure (Source Code Versioning, Bug Trackers, Feature Trackers, Web Site, Mailing Lists, Discussion Forums)<br />
6) Project Governance (Decision Making Processes, Licensing, Copyright Assignment, Release Schedule, Coding Standards)<br />
7) Community Activity<br />
8) Marketing and Outreach<br />
<br />
Below are the different status conditions that can be assigned to a project in Labs.<br />
<br />
* '''Seed''': This project is in the conceptual stage. There may be some source code written, but it is incomplete or very experiemental. The project may lack deliverables, community support, project infrastructure, project governance, community activity, or marketing and outreach.<br />
<br />
* '''Seedling''': This project is moving beyond the conceptual stage with some concrete code. However the code is still experimental and isn't stable. Projects at this status level could still experience a lot of change in their code base. This project should start to have some project infrastructure and some basic documentation.<br />
<br />
* '''Sapling''': This project has functional source code, although it may not be "mature and feature rich". For example, the code may only be usable as a programming library or a command line tool instead of featuring a GUI. The project has started to support users and programmers with communication tools, trackers, and documentation. The project has started to think about project governance and marketing, perhaps creating plans in these areas that are not fully implemented.<br />
<br />
* '''Adult''': This project has a usable and user friendly deliverable, like an executable program or a stable and well-deocumented programming library. The project is supporting users and programmers with communication tools, trackers, and documentation. It has started the initial phases of incubation. This includes addressing issues of copyright, licensing, and project governance. The project also has a marketing and community growth plan and has started to implement the plan.<br />
<br />
== Member Projects ==<br />
* [[OSGeo Labs: Geoinformatica]]<br />
* [[OSGeo Labs: pgRouting]]<br />
* [[OSGeo Labs: PAGC]]<br />
* [[OSGeo Labs: MapProxy]]<br />
* [[OSGeo Labs: pycsw]]<br />
* [[OSGeo Labs: Virtual Terrain Project]]<br />
* [[OSGeo Labs: PyWPS]]<br />
* [[OSGeo Labs: OSGeo Certification]]<br />
<br />
== Archive ==<br />
<br />
There is an archive of the old OSGeo Labs page at [[OSGeo Labs Page Archive]].</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_Community_Projects&diff=96519OSGeo Community Projects2016-02-11T16:54:59Z<p>Wiki-Surveyor: /* Member Projects */</p>
<hr />
<div>= OSGeo Labs Projects =<br />
<br />
See http://wiki.osgeo.org/wiki/Category:OSGeo_Labs<br />
<br />
== Purpose ==<br />
OSGeo Labs is an umbrella for open source geospatial software projects that would like to become OSGeo projects in the future, but that aren't ready for incubation quite yet. It is appropriate to submit your new or experimental project as an OSGeo labs project.<br />
<br />
The volunteers that work as part of OSGeo Labs have the goal of helping OSGeo Labs Projects qualify for incubation. To reach this goal, OSGeo Labs volunteers help OSGeo Labs Projects with the following tasks:<br />
<br />
* Project marketing.<br />
* Development of user and programmer communities.<br />
* Establishment of programs and policies for project documentation, copyright assignment, and licensing.<br />
* Establishment of programs and policies for software development. This includes version tracking, bug tracking, and feature request tracking, creation of a development road map, and organization of code sprints/events.<br />
* Establishment of project governance programs and policies.<br />
* Collaboration on technical standars, data formats, and code sharing with other open source geospatial software projects.<br />
* Utilization of software development infrastructure like mailing lists, bug trackers, version control software/hosting, and web hosting.<br />
<br />
== OSGeo Labs Project Selection Criteria ==<br />
Projects should only submit themselves for inclusion in OSGeo Labs if they follow the OSGeo Incubation principles.<br />
# The code is under an OSI approved license (data & doc projects need to specify their choice for a type of license).<br />
# The project is willing to keep code clear of encumbrances<br />
# The project is "geospatial", or directly supports geospatial applications.<br />
# The project hopes to become a graduated OSGeo project,.<br />
<br />
==Becoming a Labs Project==<br />
The goal is to keep the submission process for OSGeo Labs as simple and painless as possible. (The OSGeo Incubation Process is hard enough.) To submit your software project for inclusion in OSGeo Labs, simply send a description of the project to the [http://lists.osgeo.org/mailman/listinfo/incubator OSGeo Incubation Committee Mailing List], or [mailto:sunburned.surveyor@gmail.com e-mail Landon Blake.]<br />
<br />
==OSGeo Labs Set-Up Process==<br />
Once a project has been accepted into OSGeo Labs, the OSGeo Labs volunteers will help the projects take these steps:<br />
# Selection of an open source license if the project hasn't already done so.<br />
# Creation a home page for the project. The OSGeo wiki is recommended for this page. <br />
# Announce and discuss the project on the [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss] email list.<br />
# Set the project software development up on the OSGeo infrastructure if appropriate. (Sourceforge or other software development hosting sites can be used as an alternative.)<br />
<br />
== Labs Project Status Conditions ==<br />
<br />
We’ve designed an informal “status” system to assist programmers and users evaluate projects in OSGeo Labs. Each project in labs is assigned one (1) of five (5) status conditions. The following factors are used to determine the status condition of the projects:<br />
<br />
1) Source Code Completeness<br />
2) Source Code Stability<br />
3) Community Support (Mailing Lists, Documentation, Tutorials)<br />
4) Project Deliverables (Programming Libraries and/or Executables)<br />
5) Project Infrastructure (Source Code Versioning, Bug Trackers, Feature Trackers, Web Site, Mailing Lists, Discussion Forums)<br />
6) Project Governance (Decision Making Processes, Licensing, Copyright Assignment, Release Schedule, Coding Standards)<br />
7) Community Activity<br />
8) Marketing and Outreach<br />
<br />
Below are the different status conditions that can be assigned to a project in Labs.<br />
<br />
* '''Seed''': This project is in the conceptual stage. There may be some source code written, but it is incomplete or very experiemental. The project may lack deliverables, community support, project infrastructure, project governance, community activity, or marketing and outreach.<br />
<br />
* '''Seedling''': This project is moving beyond the conceptual stage with some concrete code. However the code is still experimental and isn't stable. Projects at this status level could still experience a lot of change in their code base. This project should start to have some project infrastructure and some basic documentation.<br />
<br />
* '''Sapling''': This project has functional source code, although it may not be "mature and feature rich". For example, the code may only be usable as a programming library or a command line tool instead of featuring a GUI. The project has started to support users and programmers with communication tools, trackers, and documentation. The project has started to think about project governance and marketing, perhaps creating plans in these areas that are not fully implemented.<br />
<br />
* '''Adult''': This project has a usable and user friendly deliverable, like an executable program or a stable and well-deocumented programming library. The project is supporting users and programmers with communication tools, trackers, and documentation. It has started the initial phases of incubation. This includes addressing issues of copyright, licensing, and project governance. The project also has a marketing and community growth plan and has started to implement the plan.<br />
<br />
== Member Projects ==<br />
* [[OSGeo Labs: Geoinformatica]]<br />
* [[OSGeo Labs: pgRouting]]<br />
* [[OSGeo Labs: PAGC]]<br />
* [[OSGeo Labs: MapProxy]]<br />
* [[OSGeo Labs: pycsw]]<br />
* [[OSGeo Labs: Virtual Terrain Project]]<br />
* [[OSGeo Labs: PyWPS]]<br />
* [[OSGeo Labs: OSGeo Certification]]<br />
<br />
== Archive ==<br />
<br />
There is an archive of the old OSGeo Labs page at [[OSGeo Labs Page Archive]].</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OTB_Project_Incubation_Status&diff=88900OTB Project Incubation Status2015-11-28T21:47:23Z<p>Wiki-Surveyor: </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.<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 commiters 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 />
Changes will be made to the website as part of a website redesign before the end of 2014.<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-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OSGeo_California_Chapter_2015_Annual_Meeting&diff=88114OSGeo California Chapter 2015 Annual Meeting2015-11-16T22:24:04Z<p>Wiki-Surveyor: Created page with "== Introduction == Every year the California OSGeo Chapter is required to have an annual meeting. We are still working to determine the date and location of our 2015 Annual Me..."</p>
<hr />
<div>== Introduction ==<br />
Every year the California OSGeo Chapter is required to have an annual meeting. We are still working to determine the date and location of our 2015 Annual Meeting, but it is tentatively scheduled for January 23, 2016 at UC Davis.<br />
<br />
== Speakers ==<br />
* 10:00AM to 10:30AM = <br />
* 10:30AM to 11:00AM = <br />
* 11:00AM to 11:30AM = <br />
* 11:30AM to 12:00PM = <br />
<br />
== Activities ==<br />
* 2:00PM to 4:30 PM: <br />
* 2:30PM to 4:30 PM: <br />
<br />
== Directions & Parking ==</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=California_Chapter_Events_Page&diff=88113California Chapter Events Page2015-11-16T22:16:41Z<p>Wiki-Surveyor: </p>
<hr />
<div>We have an [[California/Exhibition Pack|California Chapter Exhibition Pack]], see the page for details if you want to use it.<br />
<br />
== Budget ==<br />
Based on our fund raising efforts we will determine what our [[California/Budget| Budget]] will allow use to do.<br />
The goal for '''2009''' is '''$1500'''..<br />
For 2010 the new focus is on getting several new sponsors for OSGeo in general which would create additional funds for support of chapter activities.<br />
<br />
== Future/Confirmed ==<br />
<br />
* [[OSGeo California Chapter 2015 Annual Meeting]]<br />
<br />
<br />
== Proposed ==<br />
*[[CLSA 2014 Conference OSGeo Open Source GIS Track]]<br />
*[[OSGeo California Chapter 2013 Annual Meeting]]<br />
<br />
== Past ==<br />
(Reverse Date Order, Most recent 1st)<br />
* SCALE (February 22-24, 2013)<br />
* AGU 2013 (December 2013)<br />
* AAG (April 13, 2013)<br />
* Strata (February 26-28, 2013)<br />
* CLSA Conference (March 23-27, 2013)<br />
* URISA CAL-GIS (April 15-17, 2013)<br />
* OSGeo Annual Meeting (October 12, 2013)<br />
* [[OSGeo California Chapter Spring 2013 Hackathon]] (January 19, 2013)<br />
* California Geographic Society (Spring 2013)<br />
<br />
* [[California Chapter 2012 Annual Meeting]] Saturday, October 16, 2012<br />
* [[California Chapter 2011 Annual Meeting]] October 22, 2011 - Davis, CA<br />
* [[Where 2.0 2011]] April 19-21, 2011, Santa Clara Hyatt<br />
* California Invasive Plant Society annual meeting Jul11 - LiveDVD<br />
* FLUXNET and Remote Sensing Open-Workshop June11 - provided LiveDVD to interested participants<br />
* San Francisco GeoMeetup - 2011 monthly/recurrent<br />
* [[AAG 2011]] April 12-16 Seattle<br />
* [[CGS 2011]] April 29-May 1st, Bishop, CA<br />
* Missed -[[ACM SIGSPATIAL 2010]] - Nov 2-5, San Jose ([http://acmgis2010.cs.ucsb.edu Conference Website])<br />
* Missed -[[AGU 2010]] Dec, SF - It's always in California<br />
* Missed -[[GTC WEST 2010]] Cal chapter involvement proposed. May 11-12, Sacramento<br />
* [[CGS 2010]] May 1, Fullerton<br />
* [[AAG 2010]] April 2010, Washington, D.C.<br />
* [[Where_20_2010 | Where 2.0]]<br />
* [[SCALE 2010]] Feb 19-21, Los Angeles<br />
* [[AGU 2009]] December 14-18 - SF - It's always in California<br />
* [[GIS Day 2009]] November - Worldwide Local events (Berkeley, Davis, ?)<br />
* [[NACIS 2009]] October 7- 10 - Sacramento : We gave a 50 minute team demo on 4 OSGeo applications.<br />
<br />
* [[OSCON 2009]] July 20-24, San Jose, CA - State of OSGeo "Lightening Talk" was a hit!<br />
* [[Where 2.0 2009]] May 20-21 - San Jose, CA- Paul Ramsey will join us.<br />
* [[USGS Open House 2009]] May 16-17 - Menlo Park, we we're invited at [[CalGIS]]<br />
* [[CGS 2009]] May 2 - Santa Ynez - Always in California, small cheap, outreach to grade schools and non-profits.<br />
* [[CalGIS 2009]] April 7-9 Sacramento - Booth was too expensive($800 for booth), Berkeley GIF Lab talked about QGIS<br />
* [[AAG 2009]] (Mar) - Las Vegas <br />
* [[California/InauguralMeeting|Inaugural Meeting]] (Feb) of California Chapter<br />
<br />
* [[AGU 2008]] - Open Source Session at American Geophysical Union; San Francisco, CA<br />
* GIS Day 2008 - UC Berkeley GIF Lab, US EPA Region IX<br />
* [[OSBootCamp OSBootCamp 2008]] - Open Source day at UC Berkeley<br />
* [[CGS 2008]] - Booth at the Calfornia Geographical Society meeting in Chico.<br />
* [[4H Workshop]] - [[User:bwoodall|Bill]] will be running a workshop at UC Davis for 4H high schoolers on GPS/GIS<br />
<br />
== Missed Opportunities (May Recur)==<br />
* [[OSCON 2010]] - Cal chapter involvement proposed. July?, Portland<br />
* UCSB Vendor Fair, May 2011, Santa Barbara<br />
* [[OpenSourceWorld 2009]] August, SF<br />
* [[APCG 2009]] Sept 30 - Oct 3 - San Diego<br />
* [[ACM GIS 2009]] November 4-6 - Seattle (pass it to [[cugos]], speaking opportunities)<br />
<br />
== OSGeo Chapter Annual Meetings ==<br />
Meetings will be held annually at minimum and as needed in between.<br />
*[[California Chapter 2012 Annual Meeting]]<br />
*[[California Chapter 2011 Annual Meeting]]<br />
*[http://wiki.osgeo.org/wiki/California/Meeting_Minutes California 2009 Annual Meeting]<br />
<br />
== Navigation ==<br />
[http://wiki.osgeo.org/wiki/California California Chapter Wiki Home Page]<br />
<br />
[[Category: Local Chapters]]<br />
[[Category: California]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OTB_Project_Incubation_Status&diff=85293OTB Project Incubation Status2015-07-26T04:47:06Z<p>Wiki-Surveyor: /* 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.<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 />
The project doesn't currently have a PSC. There are plans to form one and to have control passed from CNES to the PSC. This should take place by the early summer of 2014.<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 commiters 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 />
Changes will be made to project documentation in Fall 2014.<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 />
Changes will be made to the website as part of a website redesign before the end of 2014.<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-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OTB_Code_Provenance_Review&diff=83165OTB Code Provenance Review2015-04-01T03:30:35Z<p>Wiki-Surveyor: Created page with "= Committers = List committers here. = Outstanding Issues = List current issues with the code review here. = Included Libraries = == Free Libraries == List free libraries here..."</p>
<hr />
<div>= Committers =<br />
List committers here.<br />
<br />
= Outstanding Issues =<br />
List current issues with the code review here.<br />
<br />
= Included Libraries =<br />
<br />
== Free Libraries ==<br />
List free libraries here.<br />
<br />
== Non-Free Libraries ==<br />
List non-free libraries here.<br />
<br />
== Code Review ==<br />
List information on reviewed source code here. Comments should be organized logically based on software architecture.</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OTB_Project_Incubation_Status&diff=83164OTB Project Incubation Status2015-04-01T03:28:31Z<p>Wiki-Surveyor: /* 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.<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 />
The project doesn't currently have a PSC. There are plans to form one and to have control passed from CNES to the PSC. This should take place by the early summer of 2014.<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 commiters 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 />
Changes will be made to project documentation in Fall 2014.<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 />
Changes will be made to the website as part of a website redesign before the end of 2014.<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-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Fall_2014_Committee_Report_for_OSGeo_Journal&diff=80509Fall 2014 Committee Report for OSGeo Journal2014-10-25T00:36:49Z<p>Wiki-Surveyor: </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.</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Fall_2014_Committee_Report_for_OSGeo_Journal&diff=80508Fall 2014 Committee Report for OSGeo Journal2014-10-25T00:36:35Z<p>Wiki-Surveyor: Created page with "**OTB Project** * 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 Spr..."</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.</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Incubation_Committee&diff=80507Incubation Committee2014-10-25T00:34:13Z<p>Wiki-Surveyor: /* Meetings and Reports */</p>
<hr />
<div>The project incubation committee is responsible for overseeing the incubation process for new projects entering the foundation. The incubation committee provides resources to assist new projects to reach full membership, and makes recommendations to the board when they feel projects have completed incubation.<br />
<br />
== Documents ==<br />
<br />
* Official incubator public web page is at: http://osgeo.org/incubator/index.html (with members list).<br />
* [[Incubation FAQ]]<br />
* [[Official_IncCom_Documents]]<br />
* Incubation process docs: http://osgeo.org/incubator/process/index.html (original [[Official_IncCom_Documents|wiki draft documents]])<br />
* [[Incubation Badges]]<br />
<br />
Draft or Example Documents<br />
* Draft [[Commiter Responsibilities Guidelines]]<br />
* OSGeo Distribution and Committer [[http://www.osgeo.org/content/foundation/legal/licenses.html licenses] which can be used as is, or as an example for projects starting off with participatory open source.<br />
** Geotools Copyright Assignment ([http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.pdf pdf], [http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.odt odt]) - previous example<br />
** [[Project Copyright Assignment]] - previous example<br />
* [[Contributor Agreement]] and FAQ <br />
* [[Incubation Phases]] proposal<br />
<br />
Document Refresh 2014<br />
* [[Project Graduation Checklist]]<br />
<br />
Projects:<br />
* [[OSGeo Labs]] - for OSGeo related projects that haven't reached incubation status<br />
* List of [[Project Steering Committees]]<br />
<br />
Reference:<br />
* [[Project Infrastructure Migration]]<br />
* [http://producingoss.com/html-chunk/index.html Producing OSS] - by Karl Fogel - an excellent primer on running an FOSS project.<br />
<br />
Reports:<br />
* [[Incubation Committee Report 2012]]<br />
* [[Incubation Committee Report 2011]]<br />
<br />
Trac:<br />
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&order=priority Open Incubator Trac Issues]<br />
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&keywords=%7Eapplication&order=priority Pending Incubation Applications]<br />
<br />
== Meetings and Reports ==<br />
Meetings are scheduled via [http://lists.osgeo.org/mailman/listinfo/incubator Mailing List] and take place via [[Getting_Started#Jump_on_IRC | IRC]] at the times specified in the [[Foundation Calendar]].<br />
* [[IncCom Meeting1|First Meeting]] - March 13th 2006<br />
* [[IncCom Meeting2|Second Meeting]] - March 20th 2006<br />
* [[IncCom Meeting3|Third Meeting]] - March 27th 2006<br />
* [[IncCom Meeting4|Fourth Meeting]] - April 10th 2006<br />
* [[IncCom Meeting5|Fifth Meeting]] - April 24th 2006<br />
* [[IncCom Meeting6|Sixth Meeting]] - June 19th 2006<br />
* [[IncCom Meeting7|Seventh Meeting]] - August 7th 2006<br />
* [[IncCom Meeting8|Eighth Meeting]] - October 30th 2006<br />
* [[IncCom Meeting9|Nineth Meeting]] - February 12th 2007<br />
* [[IncCom Meeting10|Tenth Meeting]] - June 11th 2007<br />
* [[IncCom Meeting11|Eleventh Meeting]] - October 29th 2007 <br />
* [[IncCom Meeting12|Twelfth Meeting]] - September 8th 2008 <br />
* [[IncCom Meeting13|Thirteenth Meeting]] - October 29th 2009<br />
* [[IncCom Meeting14|Fourteenth Meeting]] - March 1th 2010<br />
* [[IncCom Meeting15]] - Nov 21 2011<br />
* [[IncCom Meeting16]] - Jan 17 2012<br />
* [[IncCom Meeting17]] - March 19 2012<br />
* [[IncCom Meeting18]] - May 21 2012<br />
* [[IncCom Meeting19]] - July 23 2012<br />
* [[IncCom Meeting20]] - Sep 24 2012<br />
* [[IncCom Meeting21]] - Feb 18 2013<br />
* [[IncCom Report22]] - 2013 Q2<br />
* [[IncCom Report23]] - 2013 Q3<br />
* [[IncCom Report24]] - 2014 Q1<br />
* [[Fall 2014 Committee Report for OSGeo Journal]]<br />
<br />
== Progress in the incubator ==<br />
<br />
The OSGeo incubation process takes place in three stages:<br />
<br />
# Initial Application<br />
# Incubation<br />
## Project Status: project details, and a few resourcing questions for the system admin committee (see [[Project Status Template]]).<br />
## Provenance Review: quick check to ensure the project is open source and has permission to distribute its source code.<br />
## Final Checklist: review the project procedures and gather requested information for OSGeo participation<br />
# Graduation<br />
<br />
The following projects are currently in OSGeo incubation:<br />
<br />
* gvSIG: http://www.osgeo.org/gvsig<br />
*# [[gvSIG Incubation Status]]<br />
*# [[gvSIG Provenance Review]]<br />
*# [[gvSIG Incubation Checklist]]<br />
<br />
* MetaCRS: http://trac.osgeo.org/metacrs/<br />
*# [[MetaCRS Incubation Status]]<br />
*# no provenance review provided<br />
*# no check list provided<br />
<br />
* Opticks: http://opticks.org<br />
*# [[Opticks Incubation Status]]<br />
*# no provenance review provided<br />
*# [[Opticks Incubation Checklist]]<br />
<br />
* rasdaman: http://www.rasdaman.org<br />
*# [[ rasdaman Incubation Status ]]<br />
*# http://rasdaman.org/wiki/OSGeoCodeProvenance<br />
*# http://www.rasdaman.org/wiki/OSGeoIncubationChecklist<br />
<br />
* Zoo-Project: http://www.zoo-project.org<br />
*# [[ZOO-Project_Incubation_Status]]<br />
*# [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance Review]<br />
*# [[ZOO-Project Incubation Checklist]]<br />
<br />
* pycsw: http://pycsw.org<br />
*# status template not filled out<br />
*# no provenance review provided<br />
*# no check list provided<br />
<br />
* TEAM Engine: http://teamengine.sourceforge.net<br />
*# status template not filled out<br />
*# no provenance review provided<br />
*# no check list provided<br />
<br />
*OTB<br />
*# [[OTB Incubation Application]]<br />
*#[[OTB Project Incubation Status]]<br />
<br />
<br />
The above pages are used to track the progress of incubation projects and are used by the developer team (and OSGeo mentor). In many cases the links<br />
will take you to a project specific wiki or website in order to be closer to their target community.<br />
<br />
When projects have completed the incubation checklist their mentor will recommend them to the Incubation committee for graduation.<br />
<br />
== Graduated == <br />
<br />
The following status and provenance documents are for historical purposes, and are no longer actively maintained. <br />
<br />
* Community Mapbuilder: [[Community Mapbuilder Incubation Progress]] | [[Community Mapbuilder Provenance Review]]<br />
* deegree: [[deegree Incubation Status]] | [[deegree Provenance Review]]<br />
* FDO: [[FDO Incubation Status]] | [[FDO Provenance Review]]<br />
* GEOS: [[GEOS Incubation Status]] | [[GEOS Provenance Review]]<br />
* GDAL/OGR: [[GDAL Incubation Progress]] | [[GDAL Provenance Review]]<br />
* Geomajas: [[GeoMajas Incubation Status]] | [[GeoMajas Provenance Review]]<br />
* GeoNetwork: [[GeoNetwork Incubation Status]] | [[GeoNetwork Provenance Review]]<br />
* GeoMoose: [[GeoMoose Incubation Status]] | [[GeoMoose Provenance Review]] | [[GeoMoose Incubation Checklist]]<br />
* GeoTools: [[GeoTools Incubation Progress]] | [[GeoTools Provenance Review]]<br />
* GeoServer: [[http://geoserver.org/display/GEOS/OSGEO+incubation+questionnaire Incubation Questionnaire]] | [[http://geoserver.org/display/GEOS/GeoServer+Incubation+Status Incubation Status]] | [[http://geoserver.org/display/GEOS/GeoServer+Provenance+Review Provenance Review]] | [[http://geoserver.org/display/GEOS/GeoServer+Incubation+Checklist Incubation Checklist]] | [[Geoserver Mentor Notes]]<br />
* GRASS: [[GRASS Incubation Progress]] | [[GRASS Provenance Review]]<br />
* Mapbender: [[Mapbender Incubation Progress]] | [[Mapbender Provenance Review]]<br />
* MapFish: [[MapFish Incubation Status]] | [[MapFish Provenance Review]] (Graduated: August 2011)<br />
* MapGuide: [[MapGuide Incubation Status]] | [[MapGuide Provenance Review]]<br />
* MapServer: [[MapServer incubation status]] | [[MapServer Provenance Review]]<br />
* Marble: [[Marble Incubation Status]] | [[Marble Code Provenance Review]] | [[Marble Graduation Checklist]] (Graduated 17 October 2013)<br />
* OpenLayers: [[OpenLayers Incubation Status]] | [[OpenLayers Provenance Review]]<br />
* PostGIS: [[PostGIS Incubation Status]] | [[PostGIS Provenance Review]]<br />
* OSSIM: [[OSSIM incubation status]] | [http://trac.osgeo.org/ossim/wiki/ossimprovenance OSSIM Provenance Review]<br />
* QGIS: [[QGIS Incubation Status]] | [[QGIS Provenance Review]]<br />
<br />
<br />
The initial projects to go through the incubation process helped define what is required. The above pages tracked the progress (and capture the experience) of these projects.<br />
<br />
[[Category:Incubation]]<br />
[[Category:Committees]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=Incubation_Committee&diff=80506Incubation Committee2014-10-25T00:33:46Z<p>Wiki-Surveyor: /* Meetings and Reports */</p>
<hr />
<div>The project incubation committee is responsible for overseeing the incubation process for new projects entering the foundation. The incubation committee provides resources to assist new projects to reach full membership, and makes recommendations to the board when they feel projects have completed incubation.<br />
<br />
== Documents ==<br />
<br />
* Official incubator public web page is at: http://osgeo.org/incubator/index.html (with members list).<br />
* [[Incubation FAQ]]<br />
* [[Official_IncCom_Documents]]<br />
* Incubation process docs: http://osgeo.org/incubator/process/index.html (original [[Official_IncCom_Documents|wiki draft documents]])<br />
* [[Incubation Badges]]<br />
<br />
Draft or Example Documents<br />
* Draft [[Commiter Responsibilities Guidelines]]<br />
* OSGeo Distribution and Committer [[http://www.osgeo.org/content/foundation/legal/licenses.html licenses] which can be used as is, or as an example for projects starting off with participatory open source.<br />
** Geotools Copyright Assignment ([http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.pdf pdf], [http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.odt odt]) - previous example<br />
** [[Project Copyright Assignment]] - previous example<br />
* [[Contributor Agreement]] and FAQ <br />
* [[Incubation Phases]] proposal<br />
<br />
Document Refresh 2014<br />
* [[Project Graduation Checklist]]<br />
<br />
Projects:<br />
* [[OSGeo Labs]] - for OSGeo related projects that haven't reached incubation status<br />
* List of [[Project Steering Committees]]<br />
<br />
Reference:<br />
* [[Project Infrastructure Migration]]<br />
* [http://producingoss.com/html-chunk/index.html Producing OSS] - by Karl Fogel - an excellent primer on running an FOSS project.<br />
<br />
Reports:<br />
* [[Incubation Committee Report 2012]]<br />
* [[Incubation Committee Report 2011]]<br />
<br />
Trac:<br />
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&order=priority Open Incubator Trac Issues]<br />
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&keywords=%7Eapplication&order=priority Pending Incubation Applications]<br />
<br />
== Meetings and Reports ==<br />
Meetings are scheduled via [http://lists.osgeo.org/mailman/listinfo/incubator Mailing List] and take place via [[Getting_Started#Jump_on_IRC | IRC]] at the times specified in the [[Foundation Calendar]].<br />
* [[IncCom Meeting1|First Meeting]] - March 13th 2006<br />
* [[IncCom Meeting2|Second Meeting]] - March 20th 2006<br />
* [[IncCom Meeting3|Third Meeting]] - March 27th 2006<br />
* [[IncCom Meeting4|Fourth Meeting]] - April 10th 2006<br />
* [[IncCom Meeting5|Fifth Meeting]] - April 24th 2006<br />
* [[IncCom Meeting6|Sixth Meeting]] - June 19th 2006<br />
* [[IncCom Meeting7|Seventh Meeting]] - August 7th 2006<br />
* [[IncCom Meeting8|Eighth Meeting]] - October 30th 2006<br />
* [[IncCom Meeting9|Nineth Meeting]] - February 12th 2007<br />
* [[IncCom Meeting10|Tenth Meeting]] - June 11th 2007<br />
* [[IncCom Meeting11|Eleventh Meeting]] - October 29th 2007 <br />
* [[IncCom Meeting12|Twelfth Meeting]] - September 8th 2008 <br />
* [[IncCom Meeting13|Thirteenth Meeting]] - October 29th 2009<br />
* [[IncCom Meeting14|Fourteenth Meeting]] - March 1th 2010<br />
* [[IncCom Meeting15]] - Nov 21 2011<br />
* [[IncCom Meeting16]] - Jan 17 2012<br />
* [[IncCom Meeting17]] - March 19 2012<br />
* [[IncCom Meeting18]] - May 21 2012<br />
* [[IncCom Meeting19]] - July 23 2012<br />
* [[IncCom Meeting20]] - Sep 24 2012<br />
* [[IncCom Meeting21]] - Feb 18 2013<br />
* [[IncCom Report22]] - 2013 Q2<br />
* [[IncCom Report23]] - 2013 Q3<br />
* [[Fall 2014 Committee Report for OSGeo Journal]]<br />
* [[IncCom Report24]] - 2014 Q1<br />
<br />
== Progress in the incubator ==<br />
<br />
The OSGeo incubation process takes place in three stages:<br />
<br />
# Initial Application<br />
# Incubation<br />
## Project Status: project details, and a few resourcing questions for the system admin committee (see [[Project Status Template]]).<br />
## Provenance Review: quick check to ensure the project is open source and has permission to distribute its source code.<br />
## Final Checklist: review the project procedures and gather requested information for OSGeo participation<br />
# Graduation<br />
<br />
The following projects are currently in OSGeo incubation:<br />
<br />
* gvSIG: http://www.osgeo.org/gvsig<br />
*# [[gvSIG Incubation Status]]<br />
*# [[gvSIG Provenance Review]]<br />
*# [[gvSIG Incubation Checklist]]<br />
<br />
* MetaCRS: http://trac.osgeo.org/metacrs/<br />
*# [[MetaCRS Incubation Status]]<br />
*# no provenance review provided<br />
*# no check list provided<br />
<br />
* Opticks: http://opticks.org<br />
*# [[Opticks Incubation Status]]<br />
*# no provenance review provided<br />
*# [[Opticks Incubation Checklist]]<br />
<br />
* rasdaman: http://www.rasdaman.org<br />
*# [[ rasdaman Incubation Status ]]<br />
*# http://rasdaman.org/wiki/OSGeoCodeProvenance<br />
*# http://www.rasdaman.org/wiki/OSGeoIncubationChecklist<br />
<br />
* Zoo-Project: http://www.zoo-project.org<br />
*# [[ZOO-Project_Incubation_Status]]<br />
*# [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance Review]<br />
*# [[ZOO-Project Incubation Checklist]]<br />
<br />
* pycsw: http://pycsw.org<br />
*# status template not filled out<br />
*# no provenance review provided<br />
*# no check list provided<br />
<br />
* TEAM Engine: http://teamengine.sourceforge.net<br />
*# status template not filled out<br />
*# no provenance review provided<br />
*# no check list provided<br />
<br />
*OTB<br />
*# [[OTB Incubation Application]]<br />
*#[[OTB Project Incubation Status]]<br />
<br />
<br />
The above pages are used to track the progress of incubation projects and are used by the developer team (and OSGeo mentor). In many cases the links<br />
will take you to a project specific wiki or website in order to be closer to their target community.<br />
<br />
When projects have completed the incubation checklist their mentor will recommend them to the Incubation committee for graduation.<br />
<br />
== Graduated == <br />
<br />
The following status and provenance documents are for historical purposes, and are no longer actively maintained. <br />
<br />
* Community Mapbuilder: [[Community Mapbuilder Incubation Progress]] | [[Community Mapbuilder Provenance Review]]<br />
* deegree: [[deegree Incubation Status]] | [[deegree Provenance Review]]<br />
* FDO: [[FDO Incubation Status]] | [[FDO Provenance Review]]<br />
* GEOS: [[GEOS Incubation Status]] | [[GEOS Provenance Review]]<br />
* GDAL/OGR: [[GDAL Incubation Progress]] | [[GDAL Provenance Review]]<br />
* Geomajas: [[GeoMajas Incubation Status]] | [[GeoMajas Provenance Review]]<br />
* GeoNetwork: [[GeoNetwork Incubation Status]] | [[GeoNetwork Provenance Review]]<br />
* GeoMoose: [[GeoMoose Incubation Status]] | [[GeoMoose Provenance Review]] | [[GeoMoose Incubation Checklist]]<br />
* GeoTools: [[GeoTools Incubation Progress]] | [[GeoTools Provenance Review]]<br />
* GeoServer: [[http://geoserver.org/display/GEOS/OSGEO+incubation+questionnaire Incubation Questionnaire]] | [[http://geoserver.org/display/GEOS/GeoServer+Incubation+Status Incubation Status]] | [[http://geoserver.org/display/GEOS/GeoServer+Provenance+Review Provenance Review]] | [[http://geoserver.org/display/GEOS/GeoServer+Incubation+Checklist Incubation Checklist]] | [[Geoserver Mentor Notes]]<br />
* GRASS: [[GRASS Incubation Progress]] | [[GRASS Provenance Review]]<br />
* Mapbender: [[Mapbender Incubation Progress]] | [[Mapbender Provenance Review]]<br />
* MapFish: [[MapFish Incubation Status]] | [[MapFish Provenance Review]] (Graduated: August 2011)<br />
* MapGuide: [[MapGuide Incubation Status]] | [[MapGuide Provenance Review]]<br />
* MapServer: [[MapServer incubation status]] | [[MapServer Provenance Review]]<br />
* Marble: [[Marble Incubation Status]] | [[Marble Code Provenance Review]] | [[Marble Graduation Checklist]] (Graduated 17 October 2013)<br />
* OpenLayers: [[OpenLayers Incubation Status]] | [[OpenLayers Provenance Review]]<br />
* PostGIS: [[PostGIS Incubation Status]] | [[PostGIS Provenance Review]]<br />
* OSSIM: [[OSSIM incubation status]] | [http://trac.osgeo.org/ossim/wiki/ossimprovenance OSSIM Provenance Review]<br />
* QGIS: [[QGIS Incubation Status]] | [[QGIS Provenance Review]]<br />
<br />
<br />
The initial projects to go through the incubation process helped define what is required. The above pages tracked the progress (and capture the experience) of these projects.<br />
<br />
[[Category:Incubation]]<br />
[[Category:Committees]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=2014_Fall_Chapter_Activity_Report&diff=805052014 Fall Chapter Activity Report2014-10-25T00:26:58Z<p>Wiki-Surveyor: Created page with "This wiki page has been set-up so we can collect information on chapter activities in the Fall of 2014 for the OSGeo Journal. Please contribute and help Landon get the report put..."</p>
<hr />
<div>This wiki page has been set-up so we can collect information on chapter activities in the Fall of 2014 for the OSGeo Journal. Please contribute and help Landon get the report put together.<br />
<br />
== Chapter Events ==<br />
* 2014 California Chapter Annual Meeting<br />
<br />
== Member Activities ==<br />
<br />
=== Landon Blake ===<br />
* Helped the Journal Team publish Volume 12 of the OSGeo Journal.<br />
* Worked to guide and support the OTB Project through OSGeo Incubation.<br />
<br />
== Navigation ==<br />
<br />
[http://wiki.osgeo.org/wiki/California California Chapter Wiki Home Page]<br />
<br />
<br />
<br />
[[Category: Local Chapters]]<br />
<br />
[[Category: California]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=California&diff=80504California2014-10-25T00:25:41Z<p>Wiki-Surveyor: /* Documentation */</p>
<hr />
<div>== Introduction ==<br />
The California Chapter is a regional chapter of OSGeo on the west coast of the United States. California is home to Silicon Valley, some of the top public research/teaching universities and some very large industries. You can learn more about the [[California Chapter Mission and Objectives]].<br />
<br />
== Events ==<br />
The California Chapter maintains a presence at geospatial conferences and events around the West Coast of the United States. It also organizes its own events, including an annual meeting.<br />
<br />
You can learn more on the [[California Chapter Events Page]].<br />
<br />
== Membership ==<br />
To be a member of the Chapter you simply need to state that by adding yourself to our [[California Chapter Membership Page]]. You should also subscribe to our [http://lists.osgeo.org/mailman/listinfo/california mailing list].<br />
<br />
== Marketing and Outreach ==<br />
You can learn more about the California Chapter [[California Chapter Marketing]] marketing and outreach efforts, which include our Open Geospatial Data Award and our list of Outreach Speakers.<br />
<br />
== Links ==<br />
<br />
Please visit our [[California Chapter Links Page]] for a list of California links related to GIS and open source software.<br />
<br />
== Fund Raising and Accounts ==<br />
See the [[California Chapter Fundraising]] page for more information on fundraising, donations, and the financial accounts for the California Chapter.<br />
<br />
== Mailing List ==<br />
The main arena for discuss events and ideas in California is the email list, please join.<br />
[http://lists.osgeo.org/mailman/listinfo/california Mailing List Info Page] (You subscribe to the mailing list at this page.)<br />
<br />
== Documentation ==<br />
*[[2010 California Chapter Annual Report]]<br />
*[[2012 California Chapter Annual Report]]<br />
*[[2014 Fall Chapter Activity Report]]<br />
<br />
[[Category: Local Chapters]]<br />
[[Category: California]]</div>Wiki-Surveyorhttps://wiki.osgeo.org/w/index.php?title=OTB_Project_Incubation_Status&diff=80199OTB Project Incubation Status2014-09-25T15:10:39Z<p>Wiki-Surveyor: /* Foundation Membership */</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.<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 />
The project doesn't currently have a PSC. There are plans to form one and to have control passed from CNES to the PSC. This should take place by the early summer of 2014.<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 commiters 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 />
Changes will be made to project documentation in Fall 2014.<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 />
Changes will be made to the website as part of a website redesign before the end of 2014.<br />
<br />
==Code Copyright Review==<br />
#'''Has a Code Provenance Review document been prepared for the project?''' <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-Surveyor