OSGeo - User contributions [en]

Subversion

2022-06-29T03:46:33Z

Warmerdam:

= Intro =

OSGeo maintains a set of subversion services, running at '''http://svn.osgeo.org/''' (the [[TracsvnVM|tracsvn VM]] at OSU OSL).

Subversion access is authenticated based on [http://www.osgeo.org/osgeo_userid OSGeo Userids] and each project has a committer list also maintained in LDAP. Excellent general information on subversion is available from the [http://svnbook.red-bean.com/nightly/en/index.html Subversion Book].

= Current Repositories =

* Full list: http://svn.osgeo.org/
* http://svn.osgeo.org/fdo - FDO (also a bunch of old repositories exist for FDO)
* http://svn.osgeo.org/gdal - GDAL (now at https://github.com/osgeo/gdal)
* http://svn.osgeo.org/geotools - GeoTools ( now at https://github.com/geotools/geotools )
* http://svn.osgeo.org/grass - GRASS GIS
* http://svn.osgeo.org/mapbender - Mapbender
* http://svn.osgeo.org/mapguide - MapGuide
* http://svn.osgeo.org/moss4g - MOSS4g
* http://svn.osgeo.org/osgeo - OSGeo
* http://svn.osgeo.org/ossim - OSSIM
* http://svn.osgeo.org/geos - GEOS
* http://svn.osgeo.org/mapserver - MapServer (now at https://github.com/mapserver/mapserver )
* http://svn.osgeo.org/qgis - QGIS (now at https://github.com/qgis/QGIS )
* http://svn.osgeo.org/fusion - Fusion
* http://svn.osgeo.org/osgeo4w - OSGeo4W
* http://svn.osgeo.org/postgis - PostGIS
* http://svn.osgeo.org/metacrs - MetaCRS
* http://svn.osgeo.org/geoinformatica/ - Geoinformatica

= Administration =

Frank Warmerdam (warmerdam), Howard Butler (hobu), and Chris Schmidt (crschmidt) are the primary contacts for Subversion administration issues. Requests can be submitted via the [http://trac.osgeo.org/osgeo/newticket SAC Trac].

== Add/Remove Committer ==

Any member of a subversion committer group can add and remove members to the commiter group at an url of the following form, with the project name substituted for gdal. [http://www.osgeo.org/osgeo_userid OSGeo Userids] has details on finding or creating OSGeo userids.

https://www.osgeo.org/cgi-bin/auth/ldap_group.py?group=gdal

== Creating a repository ==

Create the repository on the main server using the create_svn_repo.sh script on tracsvn.osgeo.org
$ cd /osgeo/tools
$ sudo ./create_svn_repo.sh project_name

Create the authorization group for the svn repository by using the tool

/osgeo/tools/create_ldap_group.py group_name admin_username

This will prompt you for the manager password.

Then restart apache gracefully:

$ sudo /etc/init.d/apache2 reload

Notify hobu/mloskot about adding a mirror of the newly created repository to http://svnmirror.osgeo.org

== Loading a repository from a dumpfile ==

By root on main server:
$ sudo svnadmin load /var/www/svn/repos/<repo_name> < /path/to/dumpfile
$ sudo chown -R www-data:www-data /var/www/svn/repos/<repo_name>

== Dumping a repository ==

By root on main server:
$ sudo svnadmin dump /var/www/svn/repos/<repo_name> > dumpfile

== Recovering / unlocking repository ==
* subversion may lock if user ctl-c during checkout or checkout is interupted with an apache restart
* Need policy on who to contact and who can run 'svnadmin recover' as
priviledged access is needed (may need to stop/start apache to drop
requests to repository before recover)

Subversion was upgraded to version 1.4.3 (30 Jan. 2007) to reduce the repository locking problem if ctl-c used to end a checkout.

If the repository locks the following command should be used to recover the repository:

$ sudo svnadmin --wait recover /var/www/svn/repos/<repo_name>
$ sudo chown -R www-data:www-data /var/www/svn/repos/<repo_name>

In most cases this will work in the odd case that you are waiting a very long time for the command to run then apache may have to be restarted to drop anything accessing the repository and preventing the repository from being recovered

$ sudo /sbin/service httpd restart
$ sudo svnadmin --wait recover /var/www/svn/repos/<repo_name>
$ sudo chown -R www-data:www-data /var/www/svn/repos/<repo_name>

= Authz Rules =

By default we use one LDAP "group" for an entire subversion repository. Everyone in that group has commit priveledges on the whole repository. However, some project desire to have subgroups. For instance a core commiter group with update on the trunk source tree, and a broader contributor group that has commit access in a subarea, such as /sandbox. We accomplish this using an "authz" file to hold the rules for the respository, and multiple LDAP groups.

A project wishing this will need to prepare an authz template file looking something like:

<pre>
[groups]
committers = @@gdal@@
sandbox = @@gdal_sandbox@@

[/]
* = r
@committers = rw

[/sandbox]
* = r
@committers = rw
@sandbox = rw
</pre>

This file should be submitted to SAC via a Trac ticket for placement on the server, and for creation of any corresponding LDAP groups. Thereafter any successful update via https://www.osgeo.org/cgi-bin/auth/ldap_group.py?group=project will result in the authz being generated from the corresponding authz.tmpl.

== Administration Notes ==

The authz.tmpl files need to be named exactly authz.tmpl and place in the corresponding project repository directory, /var/www/svn/repos/gdal for instance. Make sure the file is owned by www-date.www-data.

The corresponding /etc/httpd/conf.d/subversion/project.conf file should look something like the following. Note the removal of <LimitExcept> stuff, and reference to any specific ldap group as well as the AuthzSVNAccessFile.

<pre>
<Location /gdal>
DAV svn
SVNPath /var/www/svn/repos/gdal
AuthzSVNAccessFile /var/www/svn/repos/gdal/authz
Include conf.d/ldap_auth_url.inc
Satisfy Any
Require valid-user
</Location>
</pre>

The LDAP groups should be created as ''groupOfNames'' nodes below the ou=svn element using PHPLDAPAdmin. Make sure the membership is pre-initialized with an administrator for the project so they can do future updates themselves. Try to keep the names of the groups clearly related to the base project. eg. gdal, gdal_sandbox, gdal_documentors.

== Notes ==

The script /var/www/svn/site-local/ldap_update_authz.py script is run by an os.system() call out of ldap_group.py on any successful group update. It will scan for /var/www/svn/repos/*/authz.tmpl.

There are lots of things that can go wrong in the script which has poor error checking, and it might only manifest as some or all of the authz file no longer getting regenerated. So when an authz.tmpl file is put in place, or updated do a test update and verify that all authz files are being updated (check timestamps).

Anyone (on osgeo1) can run ldap_update_authz.py, but if authz files are created by someone that apache.apache can't delete, problems may ensue. If this occurs, the following as root may help.

cd /var/www/svn
chown www-data.www-data */*/authz*

= SVN Mirror =

OSGeo uses "svnsync" to mirror SVN repositories to ensure we have a live SVN backup with full history. Currently a mirror is maintained at Frank's system (iweb.gdal.org) but it is also possible for others to setup their own mirrors. To mirror all repositories you can do the following steps:

% mkdir osgeo-svn-mirror
% cd osgeo-svn-mirror
% wget http://svn.osgeo.org/osgeo-svn-mirror.sh
% chmod a+x osgeo-svn-mirror.sh
% ./osgeo-svn-mirror.sh

The above will run for a long time creating and mirroring repos in osgeo-svn-mirror/repos. To keep them up to date setup a cronjob to run the osgeo-svn-mirror.sh script regularly.

Currently the mirrored svn at iweb can be examined, but not updated using urls of the form:

svn://iweb.gdal.org/home/warmerda/osgeo-svn-mirror/repos/<project>

So for instance, gdal could be extracted like:

svn checkout svn://localhost/home/warmerda/osgeo-svn-mirror/repos/gdal/trunk/gdal gdal-local

'''TODO: add details on how to setup apache so these repositories will just work.'''

'''TODO: make sure that svnmirror.osgeo.org points to a live svn mirror, possibly at iweb.'''

Note: SVN mirrors do *not* capture special per-repository configurations like authz files.

See also: [http://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt svnsync.txt] - useful general info on svnsync.

[[Category:Infrastructure]]
[[Category:Services]]

User:Warmerda

2021-01-29T21:42:38Z

Warmerdam:

{{OSGeo Member
|Name=Frank Warmerdam
|Company=Planet
|Country=Canada
|State=Ontario
|City=Eganville
|Coordinate=45.4630735,-77.27171
|LocalChapter=California Chapter
|Email=warmerdam@pobox.com
|Phone=+1 (650) 701-7823
|Website=
|Photo=warmerda.jpg
|Info=Frank Warmerdam is a C++, Java and Python geospatial software developer, primarily known for founding the [http://www.gdal.org GDAL/OGR] multi format geospatial data access and translation project. He is also active on the PROJ.4, libtiff, and libgeotiff projects, was a founding director of OSGeo, and is a [[SAC:Primary_Administrators|Primary Administrator]] on the OSGeo [[SAC|System Administration Committee]].
}}
{{OSGeo Experience
|User=Yes
|Committee=Yes
|Board=No
|Coder=No
|Translate=No
|PSC=Yes
|ExBoard=Yes
|Charter=Yes
|Chair=No
|SolKatz=Yes
|Committer=No
}}
=== Frank Warmerdam ===

[[File:warmerda.jpg|thumb|right|100px|Frank Warmerdam]]

Employment: Google

Location: Mountain View, California, USA

Frank Warmerdam is a C++, Java and Python geospatial software developer, primarily known for founding the [http://www.gdal.org GDAL/OGR] multi format geospatial data access and translation project. He is also active on the PROJ.4, libtiff, and libgeotiff projects, was a founding director of OSGeo, and is a [[SAC:Primary_Administrators|Primary Administrator]] on the OSGeo [[SAC|System Administration Committee]].

;OSGeo Experience [[File:OSGeo_exboard.png|link=OSGeo_Advocate#OSGeo_Board_Members]][[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]] [[File:OSGeo_committee.png|link=OSGeo_Advocate#Developers_and_Committee_Members]] [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]] [[File:SolKatz.png|link=OSGeo_Advocate#Sol_Katz_Award]]

;Contact
: Email: warmerdam@pobox.com
: Web: http://pobox.com/~warmerdam/
: Phone: +1 (650) 701-7823

;Spoken Language(s): English

;Profile last updated: 17 August 2012

[[Category:Former_OSGeo_Director]]
[[Category:Sol Katz Awardee]]
[[Category:OSGeo Advocate]]

Daytona Beach Code Sprint 2017

2017-02-04T21:20:33Z

Warmerdam:

=== Gold Sponsors ===
[[File:GC-Group_logo.png|320px|Link=http://www.geocue.com]]

=== Silver Sponsors ===

=== Bronze Sponsors ===
[[File:CoordinateSolutions_TRANS.png|320px|link=http://www.coordinatesolutions.com/]]

[[file:Azavea_med-300x143.png|320px|link=http://www.azavea.com]]

[[File:mobileGeographicslogo.png|320px|link=http://www.mobilegeographics.com]]

[[File:RBT_Blue_and_White.png|320px|link=http://http://radiantblue.com/]]

=== Venue Sponsor ===

[[File:Erau_logo_images.jpeg|320px|link=https://erau.edu/]]

=== Other/in-kind sponsors ===

{| border=0 cellspacing=15 cellpadding=10
|
[[File:OSGeo_logo.png|260px|OSGeo|link=http://www.osgeo.org/]]
 
http://www.osgeo.org/
|}

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:

* [[Paris Code Sprint 2016|Paris]] (2016)
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)
* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009)

== Other Events from January to March 2017 ==

* FOSSGIS Hacking event January 20-22
* FOSS4G Asia January 26-29
* '''OSGeo's 11th birthday Feb 4'''
* FOSDEM Feb 4-5
* FOSS4G-IT (Genoa) Feb 8-11
* Daytona 500 NASCAR race Feb 26
* OGC Technical meeting March 7-11

== Dates and Times ==

Dates:
* Sprint: Tuesday-Friday, Feb 7 to 10, 2017 (4 days)
* Welcome event: International Speed Way WingHouse Monday afternoon - Welcome to Daytona!

== Location ==

=== Coding Venue ===
* Embry Riddle Aeronautical University, College of Arts & Science (COAS) building: https://www.openstreetmap.org/way/361201184#map=16/29.1912/-81.0494
* Located 5 minutes from Daytona International Airport (DAB)
* Three Conference Rooms within COAS
* Bring your laptop, excellent wifi and printing available
* We'll eat on campus, to ease transportation burden

=== Accommodations ===
Several hotels are within walking distance of the venue. Here are a few options:
{|border=1
|-
| '''Hotel Name''' || '''Price Range (USD)''' || '''TripAdvisor Rank''' || '''Distance''' || '''Notes'''
|-
| [http://www.marriott.com/hotels/travel/dabri-residence-inn-daytona-beach-speedway-airport/?pid=corptbta&scid=b661a3c4-9c47-48c8-9e13-75b66089dd79 Marriott Residence Inn] || 115$+ || [https://www.tripadvisor.ca/Hotel_Review-g34172-d596573-Reviews-Residence_Inn_Daytona_Beach_Speedway_Airport-Daytona_Beach_Florida.html #28 of 103] || 1.1 mile || Right next to University Campus
|-
| [https://www.choicehotels.com/florida/daytona-beach/quality-inn-hotels/fl931 Quality Inn Daytona Speedway] || 80-90$ || [https://www.tripadvisor.ca/Hotel_Review-g34172-d240235-Reviews-Quality_Inn_Daytona_Speedway-Daytona_Beach_Florida.html #3 of 103] || 2.4 miles ||
|}

=== Airport options ===
Airports to look at DAB - Daytona Beach International - Connects thru Atlanta on Delta, Charolette NC on American Airlines, and JFK from Jet Blue this might help with connections ideas: http://www.flydaytonafirst.com/schedule.stml

DAB is super easy in/out 5 minutes away from Embry-Riddle Aeronautical University, actually the college is situated off the runway for the flight school. Here are the other airports that might be cheaper on the surface, but between having to commute another hour plus the extra time dealing with the airports...DAB is probably $200 more to fly in/out of, but you save hours of transportation time and costs. Of course if you are hitting Disney World while you are here or something, then fly out of Orlando or Sanford. Or Kennedy Space Center which is an hour South, you could fly out of Melbourne FL or again Orlando. MCO is the main Orlando airport and probably has the "cheapest flights" because of the volume, but security takes a good bit of time, and typically you need to check in 90 minutes early, and traffic in Orlando can build quickly.

SFB is about 50 minutes South West and typically has good deals on Allegiant Airlines (no-frills) http://www.orlandosanfordairport.com/

MCO is about 90 minutes West in Orlando FL

JAX is about 90 minutes North in Jacksonville FL

== Schedule ==

=== Mon Feb 6, 2017 Welcoming Event ===
Gathering at the Wing House, International Speedway location-
6:00 - 9:00 PM

=== Tue Feb 7, 2017 - First Sprint Day / Evening ===
9:00 Breakfast on Campus
12:00 Lunch on Campus

3:00 - 5:00 GIS Night Introduction for ERAU students, demonstrate current projects, introduce open source, OSGEO, to Embry-Riddle Students, discuss weeks goals. 10 Round tables with monitors set up around the room, bring a pictures, and show how your code is used for students and show them code. ERAU has Unmanned Aerial Systems course (perfect for Open Drone Map), Mechanical Engineering - LIDAR/PDAL, Software Engineering - developers, Aviation/Weather Community - Satellite Imagery, remote Sensing, gdal/ogr/proj4; Aerospace Engineering - satellite imagery, deployment, imaging; Engineering Physics - all the above.

5:00 - 7:00 GIS Night for ERAU Faculty, Researchers, Administrators, Volusia County GIS Professionals - Introduction of OSGEO Sprinters and Projects being worked on this week, introduce OSGEO. Short 10 minute presentations, with the goal of sparking an interest for faculty/researchers into the GIS Community (let steve@qpublic.net know if your interested in presenting). ERAU recently added a GIS Minor and has a renowned Computational Weather Program, extensive robotics teams, Google Self Driving Car Project, about 5000 technical students interested in Aviation/Aerospace.

8:00 - 10:00 Ale House for a few pints and collaboration

=== Wed Feb 8, 2017 - Second Sprint Day / Evening ===
9:00 Breakfast on Campus
12:00 Lunch on Campus
7:00 - 10:00 Ocean Deck for dinner and collaborative thinking and planning

=== Thu Feb 9, 2017 - Third Sprint Day / Evening ===
9:00 Breakfast on Campus
12:00 Lunch on Campus
3:00 - 10:00 Daytona Internal Speedway for VIP Tour, Dinner, Collaboration/Socializing

=== Fri Feb 10, 2017 - Fourth Sprint Day ===
9:00 Breakfast on Campus
12:00 Lunch on Campus
7:00 - 10:00 Crabby Joe's, Port Orange Pier, for dinner and collaborative thinking and planning (transportation provided)

== Project Plans ==
(i.e what do you wish/want/plan to work on during the sprint ?)

* Mapserver
* PDAL
* Open Drone Map
* GDAL/OGR, PROJ4

== Social ideas ==

If you need to take a break, some ideas close to the sprint place:
Daytona Beach!!! (5 miles away, water temp around 76F)
http://www.volusia.org/services/public-protection/beach-safety/beachcams-and-daily-safety-report.stml

Daytona International Speedway (2 miles away, tours, driving experience)
https://www.daytonainternationalspeedway.com/

Barnes Noble

== Participants ==

We are planning for attendance of ~50. Please add your name and the projects
you are planning to sprint and note the likeliness of your attendance.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Attendance / Notes
|-
|1 || [[User:remanuele|Rob Emanuele]] || US || Azavea || first day || last day || PDAL, GDAL || Highly Likely
|-
|2 || [[User:dmorissette|Daniel Morissette]] || CA || Mapgears || first day || last day || MapServer, GDAL/OGR || Booked
|-
|3 || [[User:msmitherdc|Michael Smith]] || US || US Army Corp || first day || last day || MapServer, PDAL || Booked
|-
|4 || [[User:Schpidi|Stephan Meißl]] || AT || EOX || first day || last day || MapServer || Tentative
|-
|5 || [[User:smathermather|Stephen Mather]] || US || Cleveland Metroparks || first day || last day || OpenDroneMap || Highly Likely
|-
|6 || [[User:hobu|Howard Butler]] || US || Hobu Inc || Monday|| Friday morning || PDAL, MapServer, Proj.4, GDAL || Booked
|-
|7 || [[User:tomkralidis|Tom Kralidis]] || CA || self || first day|| Friday afternoon || pycsw, OWSLib, GeoHealthCheck, pygeometa, other geopython, MapServer || Booked
|-
|8 || [[User:pomadchin|Grigory Pomadchin]] || RU || Azavea || first day || last day || PDAL || Highly Likely
|-
|9 || [[User:sdlime|Steve Lime]] || US || self || first day || last day || MapServer || Booked
|-
|10 || [[User:dbenjamin|Dakota Benjamin]] || US || Cleveland Metroparks || first day || last day || OpenDroneMap || Highly Likely
|-
|11 ||Steve Lehr || US || ERAU || first day || last day || Mapserver, PDAL || Booked
|-
|12 ||[[User:warmerda|Frank Warmerdam]] || hmm || Planet Labs || first day || last day || GDAL, PROJ.4 || Booked
|-
|13 ||[[User:connormanning|Connor Manning]] || US || Hobu Inc || first day || last day || PDAL, Entwine, Greyhound || Booked
|-
|14 ||[[User:chambbj|Brad Chambers]] || US || RadiantBlue || Monday || Friday morning || PDAL || Booked
|-
|15 || Jim Hughes || US || CCRi || Monday afternoon || Friday morning || GeoMesa || Booked
|-
|16 || Tom Kunicki || US || CCRi || Monday afternoon || Friday morning || GeoMesa || Booked
|-
|-|#|| your name || country code || org || date || date || project name || Confirmed, tentative, etc
|}

== Communication ==

* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net
* Twitter: #TOSprint ( https://twitter.com/search?q=tosprint )

== Photos ==
Embry Riddle Flight Line -> https://www.google.com/search?q=embry+riddle+flight+line&source=lnms&tbm=isch&sa=X&ved=0ahUKEwj3vY-Ng9bRAhXCOBQKHRvYCJ0Q_AUICCgB&biw=1408&bih=692

Daytona Beach -> https://www.google.com/search?q=daytona+speedway+photos&biw=1408&bih=692&source=lnms&tbm=isch&sa=X&ved=0ahUKEwi89bPAg9bRAhWDuhQKHRYLC6MQ_AUIBigB#tbm=isch&q=daytona+beach+photos

Daytona Speedway Photos -> https://www.google.com/search?q=daytona+speedway+photos&biw=1408&bih=692&source=lnms&tbm=isch&sa=X&ved=0ahUKEwi89bPAg9bRAhWDuhQKHRYLC6MQ_AUIBigB

Did we mention the Atlantic Ocean is 76F in January!

== Costs ==

Participants should plan for the following costs:

* Travel to Daytona Beach
* Accommodation for four nights

All other costs - food, outings and entertainment - should/will be covered by the sponsors

== Financial ==

'''Detailed budget'''
* [[Daytona_Beach_Code_Sprint_2017_:_Budget|Budget]]

== Individual preparation ==

* Bring your own laptop
* Install GIT and compiler tools, and come with a working development environment
* If your laptop need it, video export adapter to DVI and/or VGA
* Optional: something to take pictures (camera, smartphone, small tablet...)

== Sponsors ==

We have three sponsorship levels:

* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

We encourage sponsors to support nutriment and entertainment for the
sprinters as they work hard and play hard for four or five productive days.
Contributions will be put towards lunch, snacks, and dinner costs for the
sprinters, and potentially bringing in sprinters who might otherwise be unable
to attend. Any surplus at the end of the event will be turned over to OSGeo or
used for a future code sprint.

Sponsors will receive the following:

* Your logo at the top of this page
* Mention in all of our public communication
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...)
* And as extra, for Silver and Gold: Kakemono in the event room (if you provide it)

To sponsor, please contact steve@qpublic.net directly.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]

Daytona Beach Code Sprint 2017

2017-01-19T00:45:14Z

Warmerdam: /* Participants */

=== Gold Sponsors ===
[[File:GC-Group_logo.png|320px|Link=http://www.geocue.com]]

=== Silver Sponsors ===

=== Bronze Sponsors ===
[[File:CoordinateSolutions_TRANS.png|320px|link=http://www.coordinatesolutions.com/]]
=== Venue Sponsor ===

=== Other/in-kind sponsors ===

{| border=0 cellspacing=15 cellpadding=10
|
[[File:OSGeo_logo.png|260px|OSGeo|link=http://www.osgeo.org/]]
 
http://www.osgeo.org/
|}

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:

* [[Paris Code Sprint 2016|Paris]] (2016)
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)
* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009)

== Other Events from January to March 2017 ==

* FOSSGIS Hacking event January 20-22
* FOSS4G Asia January 26-29
* '''OSGeo's 11th birthday Feb 4'''
* FOSDEM Feb 4-5
* FOSS4G-IT (Genoa) Feb 8-11
* Daytona 500 NASCAR race Feb 26
* OGC Technical meeting March 7-11

== Dates and Times ==

Dates:
* Sprint: Tuesday-Friday, Feb 7 to 10, 2017 (4 days)
* Welcome event: TBD

== Location ==

=== Coding Venue ===
* Embry Riddle Aeronautical University, College of Arts & Science building: https://www.openstreetmap.org/way/361201184#map=16/29.1912/-81.0494
* Located 5 minutes from Daytona International Airport (DAB)

=== Accommodations ===
Several hotels are within walking distance of the venue. Here are a few options:
{|border=1
|-
| '''Hotel Name''' || '''Price Range (USD)''' || '''TripAdvisor Rank''' || '''Distance''' || '''Notes'''
|-
| [http://www.marriott.com/hotels/travel/dabri-residence-inn-daytona-beach-speedway-airport/?pid=corptbta&scid=b661a3c4-9c47-48c8-9e13-75b66089dd79 Marriott Residence Inn] || 115$+ || [https://www.tripadvisor.ca/Hotel_Review-g34172-d596573-Reviews-Residence_Inn_Daytona_Beach_Speedway_Airport-Daytona_Beach_Florida.html #28 of 103] || 1.1 mile || Right next to University Campus
|-
| [https://www.choicehotels.com/florida/daytona-beach/quality-inn-hotels/fl931 Quality Inn Daytona Speedway] || 80-90$ || [https://www.tripadvisor.ca/Hotel_Review-g34172-d240235-Reviews-Quality_Inn_Daytona_Speedway-Daytona_Beach_Florida.html #3 of 103] || 2.4 miles ||
|}

=== Airport options ===
Airports to look at DAB - Daytona Beach International - Connects thru Atlanta on Delta, Charolette NC on American Airlines, and JFK from Jet Blue this might help with connections ideas: http://www.flydaytonafirst.com/schedule.stml

DAB is super easy in/out 5 minutes away from Embry-Riddle Aeronautical University, actually the college is situated off the runway for the flight school. Here are the other airports that might be cheaper on the surface, but between having to commute another hour plus the extra time dealing with the airports...DAB is probably $200 more to fly in/out of, but you save hours of transportation time and costs. Of course if you are hitting Disney World while you are here or something, then fly out of Orlando or Sanford. Or Kennedy Space Center which is an hour South, you could fly out of Melbourne FL or again Orlando. MCO is the main Orlando airport and probably has the "cheapest flights" because of the volume, but security takes a good bit of time, and typically you need to check in 90 minutes early, and traffic in Orlando can build quickly.

SFB is about 50 minutes South West and typically has good deals on Allegiant Airlines (no-frills) http://www.orlandosanfordairport.com/

MCO is about 90 minutes West in Orlando FL

JAX is about 90 minutes North in Jacksonville FL

== Schedule ==

=== Mon Feb 6, 2017 Welcoming Event ===

=== Tue Feb 7, 2017 - First Sprint Day / Evening ===

=== Wed Feb 8, 2017 - Second Sprint Day / Evening ===

=== Thu Feb 9, 2017 - Third Sprint Day / Evening ===

=== Fri Feb 10, 2017 - Fourth Sprint Day ===

== Project Plans ==
(i.e what do you wish/want/plan to work on during the sprint ?)

*
== Social ideas ==

If you need to take a break, some ideas close to the sprint place:

== Participants ==

We are planning for attendance of ~50. Please add your name and the projects
you are planning to sprint and note the likeliness of your attendance.

{| style="border: solid grey 1px; width:100%" class="sortable"
|+ Participants
|-
| # || Participant || Country || Organization || Arrival || Departure || Project Work on || Attendance / Notes
|-
|1 || [[User:remanuele|Rob Emanuele]] || US || Azavea || first day || last day || PDAL, GDAL || Highly Likely
|-
|2 || [[User:dmorissette|Daniel Morissette]] || CA || Mapgears || first day || last day || MapServer, GDAL/OGR || Booked
|-
|3 || [[User:msmitherdc|Michael Smith]] || US || US Army Corp || first day || last day || MapServer, PDAL || Highly Likely
|-
|4 || [[User:Schpidi|Stephan Meißl]] || AT || EOX || first day || last day || MapServer || Tentative
|-
|5 || [[User:smathermather|Stephen Mather]] || US || Cleveland Metroparks || first day || last day || OpenDroneMap || Highly Likely
|-
|6 || [[User:hobu|Howard Butler]] || US || Hobu Inc || Monday|| Friday morning || PDAL, MapServer, Proj.4, GDAL || Booked
|-
|7 || [[User:tomkralidis|Tom Kralidis]] || CA || self || first day|| Friday afternoon || pycsw, OWSLib, GeoHealthCheck, pygeometa, other geopython, MapServer || Booked
|-
|8 || [[User:pomadchin|Grigory Pomadchin]] || RU || Azavea || first day || last day || PDAL || Highly Likely
|-
|9 || [[User:sdlime|Steve Lime]] || US || self || first day || last day || MapServer || Booked
|-
|10 || [[User:dbenjamin|Dakota Benjamin]] || US || Cleveland Metroparks || first day || last day || OpenDroneMap || Highly Likely
|-
|11 ||Steve Lehr || US || ERAU || first day || last day || Mapserver, PDAL || Booked
|-
|12 ||[[User:jive|Jody Garnett]] || Canada || Boundless || first day || last day || GeoTools || Perhaps
|-
|13 ||[[User:warmerda|Frank Warmerdam]] || hmm || Planet Labs || first day || last day || GDAL, PROJ.4 || Highly Likely
|-
|-|#|| your name || country code || org || date || date || project name || Confirmed, tentative, etc
|}

== Communication ==

* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net
* Twitter: #TOSprint ( https://twitter.com/search?q=tosprint )

== Photos ==

== Costs ==

Participants should plan for the following costs:

* Travel to Daytona Beach
* Accommodation for four nights (including breakfast)

All other costs - food, outings and entertainment - should/will be covered by the sponsors

== Financial ==

'''Detailed budget'''
* [[Daytona_Beach_Code_Sprint_2017_:_Budget|Budget]]

== Individual preparation ==

* Bring your own laptop
* Install GIT and compiler tools, and come with a working development environment
* If your laptop need it, video export adapter to DVI and/or VGA
* Optional: something to take pictures (camera, smartphone, small tablet...)

== Sponsors ==

We have three sponsorship levels:

* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

We encourage sponsors to support nutriment and entertainment for the
sprinters as they work hard and play hard for four or five productive days.
Contributions will be put towards lunch, snacks, and dinner costs for the
sprinters, and potentially bringing in sprinters who might otherwise be unable
to attend. Any surplus at the end of the event will be turned over to OSGeo or
used for a future code sprint.

Sponsors will receive the following:

* Your logo at the top of this page
* Mention in all of our public communication
* Our undying gratitude, which comes in handy when you least expect it (Remember that feature you wanted...)
* And as extra, for Silver and Gold: Kakemono in the event room (if you provide it)

To sponsor, please contact steve@qpublic.net directly.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]

User talk:Afreeman foss4g

2016-02-09T04:35:07Z

Warmerdam: Welcome!

'''Welcome to ''OSGeo Wiki''!'''
We hope you will contribute much and well.
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].
Again, welcome and have fun! [[User:Warmerda|Warmerda]] ([[User talk:Warmerda|talk]]) 20:35, 8 February 2016 (PST)

User:Afreeman foss4g

2016-02-09T04:35:07Z

Warmerdam: Creating user page for new user.

Web mapping services manager at MassGIS, MassIT, Commonwealth of MA

User talk:Andrewc

2016-02-05T16:44:38Z

Warmerdam: Welcome!

User:Andrewc

2016-02-05T16:44:38Z

Warmerdam: Creating user page for new user.

Provide research computing support to staff and students at a university in the South West of England ... relevant interests include UNIX/GNU Linux, GIS, Python scripting and data management etc.

Trac

2015-05-29T01:05:30Z

Warmerdam: /* Procedures */ add Making trac read-only section.

= Summary =

Trac 0.11.7 is running at http://trac.osgeo.org/ (the tracsvn VM at OSU OSL).

* [http://trac.edgewall.org/wiki/TracGuide Trac Guide]
* All data and configurations live under /var/www/trac
* virtual server configurations are under /etc/httpd/conf.d/trac
* [http://trac.osgeo.org/ Existing Instances]
* Actual python is installed in /usr/lib/python2.3/site-packages/trac
* Frank Warmerdam and Howard Butler have configuration experience, and can help maintain instances.
* available plugins:
** [http://trac-hacks.org/wiki/TocMacro TOC] - multi page tables of contents.
** MediaWikiMacro - provides media wiki like format support (link? details?
** [http://trac-hacks.org/wiki/DoxygenPlugin TracDoxygen] - mix doxygen docs into trac interface (needs extra admin support)
** SecureTickets - The authz policy mechanism provides fine-grained permissions for tickets.

= Procedures =

== Local Customizations ==

The file /usr/lib/python2.3/site-packages/trac/notification.py was substantially modified to support looking up email addresses in LDAP, and will need to be re-adjusted if we upgrade to a new version of Trac.

* http://trac.osgeo.org/osgeo/ticket/39

== Creating a trac instance ==

$ sudo createdb -U postgres trac_<proj_name>
$ sudo trac-admin /var/www/trac/<proj_name> initenv

* Make sure to set the db connection to postgres://postgres@/trac_<proj_name>
* Use /var/www/svn/repos/<proj_name> for the svn path

$ sudo trac-admin /var/www/trac/<proj_name> permission add <osgeo_userid> TRAC_ADMIN
$ sudo chown -R www-data:www-data /var/www/trac/<proj_name>

* Update /var/www/trac//<proj_name>/conf/trac.ini to enable email notification.
* Add virtual host file /etc/apache2/conf.d/trac/<proj_name>.conf enabling LDAP based authentication.
* Logo can be referenced in /var/www/trac/<proj_name>/conf/trac.ini and placed in /var/www/trac/<proj_name>/htdocs
* modify webadmin.* setting in trac.ini to enabled for web based administration.
* Add to /var/www/trac/index.html
* Regenerate the robots.txt file with the command:

$ sudo /var/www/trac/mkrobots.sh

Recommended Trac permissions:
anonymous BROWSER_VIEW
anonymous CHANGESET_VIEW
anonymous FILE_VIEW
anonymous LOG_VIEW
anonymous MILESTONE_VIEW
anonymous REPORT_SQL_VIEW
anonymous REPORT_VIEW
anonymous ROADMAP_VIEW
anonymous SEARCH_VIEW
anonymous TICKET_VIEW
anonymous TIMELINE_VIEW
anonymous WIKI_VIEW
authenticated TICKET_CHGPROP
authenticated TICKET_CREATE
authenticated TICKET_MODIFY
authenticated WIKI_CREATE
authenticated WIKI_MODIFY
developers DOXYGEN_VIEW
developers MILESTONE_ADMIN
developers REPORT_ADMIN
developers REPORT_CREATE
developers WIKI_ADMIN
warmerdam developers
warmerdam TRAC_ADMIN
...

SQL Compatability Issue with Postgres

You will have to modify the SQL statement of the ''All Ticket by Milestone'' report. This can be done by accessing the trac report page and click the ''Edit report'' button (You need to be an admin of the trac instance). Check the sql statement of another trac instance and replace the one of the new instance.

== Plugins ==

Installed plugins (do in every trac instance, [http://trac.edgewall.org/wiki/TracPlugins installation guide]):

* http://trac-hacks.org/wiki/TocMacro

== Custom fields ==

See http://trac.edgewall.org/wiki/TracTicketsCustomFields

for example, in trac.ini:

[ticket-custom]
platform = select
platform.label = Platform
platform.options = Unspecified|MSWindows 2K|MSWindows XP|MSWindows Vista|MSWindows CygWin|MacOSX|Linux|Other Unix|All
platform.value = Unspecified

cpu = select
cpu.label = CPU
cpu.options = Unspecified|x86-32|x86-64|OSX/PPC|OSX/Intel|Other|All
cpu.value = Unspecified

== Secure Tickets ==

See http://trac-hacks.org/wiki/SecureTicketsPlugin (Note that the installed plugin has been modified for OSGeo)

The initial behavior of the plugin was to set all tickets private, then let the user
defines what are the public components. It has been modified this to fit osgeo needs.
Since everything is public by default, we'll set manually the private
components and everything else will be public.

'''Using the plugin'''

1- Enable the plugin in trac.ini:

[components]
securetickets.* = enabled

2- Modify the permission_policies in trac.ini:

permission_policies = SecureTicketsPolicy, DefaultPermissionPolicy, ...

3- Define private components in trac.ini:

[securetickets]
private_components = Vulnerabilities, Component2, ...

To allow a user or a group to view the private tickets, you'll have to add him
the permission SECURE_TICKET_VIEW

== Making Trac Read-Only ==

It appears the usual way of making Trac read-only is to remove all permissions on the "authenticated" group in the Admin/Permissions dialog. This will remove the authenticated group and then only those with special admin priviledges can edit the wiki, create tickets, etc.

== Timeline with filename indication ==

[timeline]
changeset_long_messages = false
changeset_show_files = 1
changeset_files_count = 3
default_daysback = 30
ticket_show_details = false

(see for example [http://trac.osgeo.org/grass/timeline here])

== Hotcopy a trac instance ==

$ sudo trac-admin /var/www/html/trac/<proj_name> hotcopy /path/to/copy/trac/to

= Trac Spam =

We have had problems with trac spam when ticket create and ticket modify permissions were set to anonymous (the default). To get around this most (all?) instances have been changed to require authenticated users to do these actions.

But some projects strongly desire to support anonymous ticket creation and modification and at some point this might be viable using image captcha technology to keep out the spammers. A Trac plugin for this is apparently under development, and described at:

http://trac.edgewall.org/browser/sandbox/spam-filter-captcha

= Trac notification forward to project mailing list =

To fwd notifications from trac to e.g. a project developers mailing list, you need to
* set in trac the mailing list address as default (trac Admin section)
* add the trac@osgeo.org address (or trac_osgeo@.., or ...) in Mailman to
** "Privacy options"
*** "Subscription rules"
*** "[Sender filters]"
**** "Non-member filters"
***** "List of non-member addresses whose postings should be automatically accepted."

* As the mail may be addressed to "undisclosed recipients" instead of directly to the list, the messages may be held for moderator approval. To avoid this add "undisclosed recipients" to the list of acceptable aliases at
** "Privacy options"
*** "[Recipient filters]"
**** ''acceptable_aliases''

[[Category:Infrastructure]]

Trac

2015-05-27T17:44:49Z

Warmerdam: remove upgrade plan as it is complete and then some.

= Summary =

Trac 0.11.7 is running at http://trac.osgeo.org/ (the tracsvn VM at OSU OSL).

* [http://trac.edgewall.org/wiki/TracGuide Trac Guide]
* All data and configurations live under /var/www/trac
* virtual server configurations are under /etc/httpd/conf.d/trac
* [http://trac.osgeo.org/ Existing Instances]
* Actual python is installed in /usr/lib/python2.3/site-packages/trac
* Frank Warmerdam and Howard Butler have configuration experience, and can help maintain instances.
* available plugins:
** [http://trac-hacks.org/wiki/TocMacro TOC] - multi page tables of contents.
** MediaWikiMacro - provides media wiki like format support (link? details?
** [http://trac-hacks.org/wiki/DoxygenPlugin TracDoxygen] - mix doxygen docs into trac interface (needs extra admin support)
** SecureTickets - The authz policy mechanism provides fine-grained permissions for tickets.

= Procedures =

== Local Customizations ==

The file /usr/lib/python2.3/site-packages/trac/notification.py was substantially modified to support looking up email addresses in LDAP, and will need to be re-adjusted if we upgrade to a new version of Trac.

* http://trac.osgeo.org/osgeo/ticket/39

== Creating a trac instance ==

$ sudo createdb -U postgres trac_<proj_name>
$ sudo trac-admin /var/www/trac/<proj_name> initenv

* Make sure to set the db connection to postgres://postgres@/trac_<proj_name>
* Use /var/www/svn/repos/<proj_name> for the svn path

$ sudo trac-admin /var/www/trac/<proj_name> permission add <osgeo_userid> TRAC_ADMIN
$ sudo chown -R www-data:www-data /var/www/trac/<proj_name>

* Update /var/www/trac//<proj_name>/conf/trac.ini to enable email notification.
* Add virtual host file /etc/apache2/conf.d/trac/<proj_name>.conf enabling LDAP based authentication.
* Logo can be referenced in /var/www/trac/<proj_name>/conf/trac.ini and placed in /var/www/trac/<proj_name>/htdocs
* modify webadmin.* setting in trac.ini to enabled for web based administration.
* Add to /var/www/trac/index.html
* Regenerate the robots.txt file with the command:

$ sudo /var/www/trac/mkrobots.sh

Recommended Trac permissions:
anonymous BROWSER_VIEW
anonymous CHANGESET_VIEW
anonymous FILE_VIEW
anonymous LOG_VIEW
anonymous MILESTONE_VIEW
anonymous REPORT_SQL_VIEW
anonymous REPORT_VIEW
anonymous ROADMAP_VIEW
anonymous SEARCH_VIEW
anonymous TICKET_VIEW
anonymous TIMELINE_VIEW
anonymous WIKI_VIEW
authenticated TICKET_CHGPROP
authenticated TICKET_CREATE
authenticated TICKET_MODIFY
authenticated WIKI_CREATE
authenticated WIKI_MODIFY
developers DOXYGEN_VIEW
developers MILESTONE_ADMIN
developers REPORT_ADMIN
developers REPORT_CREATE
developers WIKI_ADMIN
warmerdam developers
warmerdam TRAC_ADMIN
...

SQL Compatability Issue with Postgres

You will have to modify the SQL statement of the ''All Ticket by Milestone'' report. This can be done by accessing the trac report page and click the ''Edit report'' button (You need to be an admin of the trac instance). Check the sql statement of another trac instance and replace the one of the new instance.

== Plugins ==

Installed plugins (do in every trac instance, [http://trac.edgewall.org/wiki/TracPlugins installation guide]):

* http://trac-hacks.org/wiki/TocMacro

== Custom fields ==

See http://trac.edgewall.org/wiki/TracTicketsCustomFields

for example, in trac.ini:

[ticket-custom]
platform = select
platform.label = Platform
platform.options = Unspecified|MSWindows 2K|MSWindows XP|MSWindows Vista|MSWindows CygWin|MacOSX|Linux|Other Unix|All
platform.value = Unspecified

cpu = select
cpu.label = CPU
cpu.options = Unspecified|x86-32|x86-64|OSX/PPC|OSX/Intel|Other|All
cpu.value = Unspecified

== Secure Tickets ==

See http://trac-hacks.org/wiki/SecureTicketsPlugin (Note that the installed plugin has been modified for OSGeo)

The initial behavior of the plugin was to set all tickets private, then let the user
defines what are the public components. It has been modified this to fit osgeo needs.
Since everything is public by default, we'll set manually the private
components and everything else will be public.

'''Using the plugin'''

1- Enable the plugin in trac.ini:

[components]
securetickets.* = enabled

2- Modify the permission_policies in trac.ini:

permission_policies = SecureTicketsPolicy, DefaultPermissionPolicy, ...

3- Define private components in trac.ini:

[securetickets]
private_components = Vulnerabilities, Component2, ...

To allow a user or a group to view the private tickets, you'll have to add him
the permission SECURE_TICKET_VIEW

== Timeline with filename indication ==

[timeline]
changeset_long_messages = false
changeset_show_files = 1
changeset_files_count = 3
default_daysback = 30
ticket_show_details = false

(see for example [http://trac.osgeo.org/grass/timeline here])

== Hotcopy a trac instance ==

$ sudo trac-admin /var/www/html/trac/<proj_name> hotcopy /path/to/copy/trac/to

= Trac Spam =

We have had problems with trac spam when ticket create and ticket modify permissions were set to anonymous (the default). To get around this most (all?) instances have been changed to require authenticated users to do these actions.

But some projects strongly desire to support anonymous ticket creation and modification and at some point this might be viable using image captcha technology to keep out the spammers. A Trac plugin for this is apparently under development, and described at:

http://trac.edgewall.org/browser/sandbox/spam-filter-captcha

= Trac notification forward to project mailing list =

To fwd notifications from trac to e.g. a project developers mailing list, you need to
* set in trac the mailing list address as default (trac Admin section)
* add the trac@osgeo.org address (or trac_osgeo@.., or ...) in Mailman to
** "Privacy options"
*** "Subscription rules"
*** "[Sender filters]"
**** "Non-member filters"
***** "List of non-member addresses whose postings should be automatically accepted."

* As the mail may be addressed to "undisclosed recipients" instead of directly to the list, the messages may be held for moderator approval. To avoid this add "undisclosed recipients" to the list of acceptable aliases at
** "Privacy options"
*** "[Recipient filters]"
**** ''acceptable_aliases''

[[Category:Infrastructure]]

Conference Committee

2015-05-15T16:39:22Z

Warmerdam: moved myself to past members.

The Conference Committee is the official committee of OSGeo responsible for operating the annual [[FOSS4G]] conferences.

= Noteworthy Documents =

* [http://www.osgeo.org/conference OSGeo Conference Committee main page] (includes RFP, proposals, and archived files from past conferences)
* http://lists.osgeo.org/mailman/listinfo/conference_dev - Conference Committee email list
* [[Motion to form Conference Committee]]
* [[Conference website management]]

= Goals =

* facilitate the hosting application/decision process
* assist the conference local organizing committees in planning
* make sure OSGeo foundation principles exist in all conferences
* possibly support other affiliated conferences

== Other Responsibilities ==

* [[Sol Katz Award]]

= Current Members =

* Eli Adam
* Thierry Badard
* Peter Batty
* David Bitner
* Jachym Cepicky
* Vasile Craciunescu
* David Fawcett
* Steven Feldman
* Gavin Fleming
* Darrell Fuhrman
* Dave McIlhagga
* Helena Mitasova
* Claude Philipona
* Venkatesh Raghavan
* Paul Ramsey
* Cameron Shorter
* Jeroen Ticheler

= Past Members =

* Lorenzo Becchi
* Allan Doyle
* Olivier Ertz
* Alain Grignon
* Luc Maurer
* Daniel Rappo
* Dave Patton
* Rafael Medeiros Sperb
* [[Jeff McKenna]]
* Arnulf Christl
* [[Markus Neteler]]
* Steve Lime
* Frank Warmerdam

= Meetings =

* Meetings occur in IRC in the #foss4g channel (on irc.freenode.net)
* See the [[Conference_Committee_Meetings | Conference Committee Meetings]] page for information about the committee's meetings.

= 2016 Pages =

* [http://www.osgeo.org/conference/rfp/ 2016 RFP schedule]

= 2015 Pages =

* [[FOSS4G 2015 Bid Process]]

= 2014 Pages =

* [[FOSS4G 2014 Bid Process]]
* [[FOSS4G 2014]]
* [[FOSS4G Europe 2014]]
* [[FOSS4G Handbook]] (provides guidance to future FOSS4G and FOSS4G related events, based upon the collective wisdom gained during prior events)

= 2013 Pages =

* Main page: [[FOSS4G_2013]]
* [http://svn.osgeo.org/osgeo/foss4g/2013/documents/FOSS4G_2013_UK_Proposal-Final_version.pdf 2013 Proposal]
* Reflections on the event by the LOC (includes lessons learnt and supersedes the old Lessons Learned page): [[FOSS4G2013_Reflections_by_the_LOC]]

= 2012 Pages =
Main page: [[FOSS4G 2012]]
* RFP ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-2012-request-for-proposal.odt OpenOffice], [http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-2012-request-for-proposal.pdf pdf])
* budget template ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-budget-template.ods OpenOffice])
* Important dates:
** Letters of Intent (Stage 1) due: 2011-06-30 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=06&day=30&hour=23&min=0&sec=0 23:00 UTC])
** Stage 1 question period: 2011-06-30 to 2011-07-07
** Stage 1 decision: 2011-07-07
** Proposals (Stage 2) due: 2011-08-01 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=08&day=01&hour=23&min=0&sec=0 23:00 UTC])
** Stage 2 question period: 2011-08-01 to 2011-08-05
** Final decision: 2011-08-05

= 2011 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Letters of Intent]
* [[FOSS4G_2011_Bid_Process | 2011 Bid Process]]
* [[FOSS4G Reboot 2011 | Initial thoughts on 2011 required changes]]

= 2010 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Proposals]
* [[Conference_Committee_2010_Bid_Questions | Bid Questions]]
* [[Conference_Committee_2010_Voting_Process | Voting Process]]

= 2009 Pages =

* [[FOSS4G 2009 Governance]]
* All [http://wiki.osgeo.org/wiki/Category:FOSS4G2009 FOSS4G 2009] pages.

= 2008 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Proposals]
* [http://lists.osgeo.org/pipermail/conference_dev/2007-July/000355.html Voting Process]
* [[FOSS4G 2008 Governance]]
* [[FOSS4GLOC matters]]
* [http://spreadsheets.google.com/pub?key=p6mc38S7PA8lHWRQuIgExDA Workshop and lab evaluations]

= 2007 Pages =

* [http://wiki.osgeo.org/index.php/Category:FOSS4G2007 Pages in category "FOSS4G2007"]
* [[FOSS4G2007]] - wiki page
* http://www.foss4g2007.org/ - Conference Site
* [http://www.osgeo.org/conference/rfp Proposals and RFP]
* [[OSGeo_Conference_RFP_2007#RFP_Response_Requirements | requirements Wiki page]]
* [[OSGeo_Conference_Naming_Results | Naming results]]
* [http://www.foss4g2007.org/bid_site/ Victoria 2007 Proposal]
* [[FOSS4G 2007 Governance]]
* [[FOSS4G2007 Lessons Learned]]

= 2006 Pages =

* [http://wiki.osgeo.org/index.php/Category:FOSS4G2006 Pages in category "FOSS4G2006"]
* http://www.foss4g2006.org/ - Conference Site
* [[FOSS4G2006]] information

= Event Policy Pages =

* [[Official_OSGeo_Event_Policy | OSGeo Event policy]] (in review)
* [[OSGeo_Conference_Policy | Board notes]] regarding event policy

[[Category:FOSS4G]]
[[Category:Committees]]
[[Category:Conference Committee]]

LIDAR Format Letter

2015-04-18T01:38:42Z

Warmerdam: /* Signed */

=Open Letter of the Need for Open Standards in LiDAR=
April 2015.

We, the undersigned, are concerned that the current interoperability between LiDAR applications, through use of the open "LAS" format, is being threatened by ESRI's introduction and promotion of an alternative "Optimized LAS" '''''proprietary format.''''' This is of grave concern given that fragmentation of the LAS format will reduce interoperability between applications and organisations, and introduce vendor lock-in.

We request that:
# The OGC initiate the formalisation of an open standard for storing LiDAR data, and that OGC sponsors help prioritise the development of this open LiDAR standard.
# ESRI support the OGC in their [http://www.opengeospatial.org/ogc/vision mission] "to advance the development and use of international standards and supporting services that promote geospatial interoperability." In particular, ESRI join the OGC in consolidating an Open Standard for use of LiDAR data. This might include proposing ESRI's "Optimized LAS" as an Open Standard to remove any technical or legal hurdles in use of "Optimized LAS" as an Open Standard. A simple test to determine if "Optimized LAS" can be used as an Open Standard would be if "Optimized LAS" can legally be implemented by Open Source software such as libLAS or LASzip.
# Users and sponsors of LiDAR data, publicly state their preference for the use of an open LiDAR format over proprietary when selecting software and services.
# The custodians of the open LAS format [http://www.asprs.org/LD-Division/LAS-Working-Group.html LAS Working Group (LWG)], who are part of [http://www.asprs.org/ American Society for Photogrammetry and Remote Sensing (ASPRS)], request the term "LAS" not to be included in the name of a proprietary format, as it makes such a proprietary format appear to be an approved derivative of LAS.

=Signed=
Name, Affiliation(s), Optional comment on interest in Open LiDAR format

# Suchith Anand, Geo for All, committed to Open Principles in Geo Education and Policy.
# Martin Isenburg, founder of [http://rapidlasso.com rapidlasso GmbH] and creator of [http://rapidlasso.com/LASzip LASzip], [http://rapidlasso.com/LAStools LAStools], and [http://rapidlasso.com/PulseWaves PulseWaves].
# Cameron Shorter, GeoSpatial Director at [http://lisasoft.com LISAsoft]. Core contributor and coordinator of [http://live.osgeo.org OSGeo-Live]. Contributor to numerous OGC testbeds, technical lead on a range of previous Australian and New Zealand Open Government initiatives.
# Stefan Keller, founder and director of [http://www.hsr.ch/geometalab Geometa Lab]; Professor in GIS, databases, open (government) data and interoperability; maintainer of GeoConverter; contributor to open source software (GDAL/OGR, QGIS).
# Patrick Hogan, NASA World Wind Project Manager, committed to the US National Spatial Data Infrastructure principles, one being "to make geographic data more accessible to the public" [http://www.fgdc.gov/nsdi/nsdi.html NSDI]. Open standards are essential for this.
# Lene Fischer, Associate Professor, Department of Geosciences and Natural Resource Management, University of Copenhagen. User of Open and free Data from The Danish Geodata Agency - Using LAZ and LAS http://download.kortforsyningen.dk/content/dhmpunktsky.
# [http://www.ege-como.polimi.it/index.php?content=maria_brovelli Maria Antonia Brovelli], Full Professor, Department of Civil and Environmental Engineering, Politecnico di Milano. Geo For All, committed to Open Principles in Geo Education and Policy. Committed to Open Principles in Research.
# Ron Fortunato, President of [http://www.trilliumlearning.com/AmericaBridge/ Trillium Learning] LLC. Committed to open data standards that are necessary for education and all levels of communication.
# [http://www.geodatawiz.com/armin-schmidt Armin Schmidt], Chief Developer at [http://www.GeodataWIZ.com GeodataWIZ Ltd] and Chairman of [http://www.archprospection.org ISAP], committed to better science through Open Data.
# [http://www.linkedin.com/in/gconti Giuseppe Conti], CTO Trilogis Srl, Italy. Committed to open data standards that maximize opportunity for innovative solutions, unencumbered by artificial obstacles to data exchange.
# [http://pt.linkedin.com/pub/jorge-rocha/1b/560/499 Jorge Gustavo Rocha], Professor, Computer Science Department, University of Minho, Portugal, committed to better science through [http://www.gistam.org/EventChairs.aspx?y=2016 Open Data].
# [http://people.eecs.ku.edu/~miller/ Jim Miller], University of Kansas, Professor, Computer Science. Open standards for data exchange are essential for education and research.
# [http://www.linkedin.com/pub/brandt-melick/22/869/261 Brandt Melick], Information Technology Department Director, Springfield Oregon USA. The need to promote open solutions is paramount.
# Alex Paza Makini, National University Solomon Islands, Natural Resources and Applied Science. Committed to open data standards for education and research, and everything beyond.
# Jorg M. Hacker, Professor, Director/Chief Scientist of [http://www.airborneresearchaustralia.com Airborne Research Australia], Flinders University, Adelaide, Australia. Open formats have always been a great benefit to airborne LiDAR.
# Didier Richard, Head of IS Training Dept. in Education and Research Directorate of [http://www.ign.fr Institut National de l'Information Géographique et Forestière], France. OGC user, Contributor to OSGeO projects like GDAL.
# [http://www.linkedin.com/pub/adryane-gorayeb/74/517/96a Adryane Gorayeb], [http://www.ufc.br/ Federal University of Ceará Brazil], Geography Department. Open standards for data exchange are essential for education and research.
# [http://www.linkedin.com/in/yuryryabov Yury Ryabov], PhD, Senior researcher at [http://www.istc.ru/istc/db/inst.nsf/wsu/i0001823 Russian Scientific-Research Centre for Ecological Safety], [http://www.interacademies.net/Academies/ByRegion/CentralEasternEurope/13383.aspx Russian Academy of Sciences], Saint Petersburg, Russia. Open data formats are essential for successful and reproducible scientific research.
# [http://www.linkedin.com/pub/teresa-lamelas-gracia/40/4a7/20b María Teresa Lamelas], [http://cud.unizar.es/ Centro Universitario de la Defensa Zaragoza], [http://geoforest.unizar.es/es/index.php GeoForest-IUCA]. Committed to open data standards for education and research.
# [http://www.linkedin.com/in/davidherries David Herries], [http://www.interpine.co.nz/SitePages/Home.aspx Using LiDAR for forest yield modelling at Interpine Innovation]. Establishing open data standards provide scope for exponential growth in innovation. This is key to a rapidly developing technology like LiDAR.
# [[User:Ivansanchez|Iván Sánchez Ortega]], [http://www.mazemap.no Mazemap]. OSGeo Charter member and Open Data nerd.
# [[User:AnitaGraser|Anita Graser]], GIS specialist with AIT Austrian Institute of Technology, OSGeo Charter member and QGIS team member. Committed to open data standards for education and research.
# [[User:vehrka|Pedro-Juan Ferrer]], [http://www.geomaticblog.net Geomaticblog]. OSGeo Charter member and member of the Open Knowledge Foundation.
# [http://www.linkedin.com/pub/karl-donert/3/160/571 Professor Karl Donert], President European Association of Geographers (http://www.eurogeo.nl/ EUROGEO)
# Drew Fenton, Boulder Creek, CA [http://www.savetheredwoods.org/redwoods/coast-redwoods/ Countdown to the Last Coast Redwood]. Please protect Open Standards for geospatial data!
# [[User:Bolosig|Wladimir Szczerban]], [http://www.geoinquiets.cat Geoinquiets] Geogeek & OSGeo Spanish Local Chapter Member, Spain
# [http://vmx.cx Volker Mische], OSGeo Charter member and creator of GeoCouch
# [http://www.linkedin.com/in/clquintanilla Carlos López Quintanilla], [http://www.psig.es PSIG] [http://www.geoinquiets.cat Geoinquiets] GIS consultant, Spain
# [[User:woodbri|Stephen Woodbridge]], [http://imaptools.com iMaptools], OSGeo Charter member.
# [[User:odoepner|Oliver Doepner]], [http://oliver.doepner.net doepner.net], Software Engineer (Java,Linux), Open Standards and Open Source advocate
# [[User:Lucadelu|Luca Delucchi]], [http://gis.cri.fmach.it Fondazione Edmund Mach], OSGeo Charter member, FOSS4G and Open Data developer, advocate, contributor and user.
# Antoine Cottin, CTO of [http://www.carbomap.com Carbomap Ltd.] and creator of [http://github.com/carbomap/Fleurdelas Fleurdelas], Edinburgh, United Kingdom.
# [http://strk.keybit.net Sandro Santilli], [http://strk.keybit.net/services.html NetLab], Free Software Hacker. There are already too many users slave to their tools, let's stop that!
# [http://www.itopen.it Alessandro Pasotti], [http://www.itopen.it ItOpen], GIS Free Software Developer.
# [http://www.roccatello.com Eduard Roccatello], [http://www.3dgis.it 3DGIS], 3DGIS CTO and co-Founder
# [[User:moovida|Andrea Antonello]], [http://www.hydrologis.com HydroloGIS], OSGeo Charter member, Open Source GIS developer, HydroloGIS co-founder.
# [http://www.associazionegfoss.it Stefano Campus], President of [http://www.associazionegfoss.it GFOSS.it] Association (Associazione Italiana per l'Informazione Geografica Libera), Italian Local Chapter of OSGeo Foundation.
# [http://wiki.osgeo.org/wiki/User:Madi Margherita Di Leo], OSGeo Charter Member
# [http://wiki.osgeo.org/wiki/User:Sacosta Sergio Acosta y Lara], OSGeo Charter Member
# [http://wiki.osgeo.org/wiki/User:Maximdubinin Maxim Dubinin], CEO at NextGIS, OSGeo Charter Member. Another 'standard' proprietary format? No, thank you.
# [[User:Steko|Stefano Costa]], Soprintendenza Archeologia della Liguria, Ministero dei Beni e delle Attività Culturali e del Turismo, Italy
# [http://www.geog.illinois.edu/people/jgrn Jonathan Greenberg], Assistant Professor, [http://publish.illinois.edu/jgrn/ GEARS Laboratory], Department of Geography and Geographic Information Science, University of Illinois at Urbana-Champaign.
# Bob Basques, Saint Paul, Mn., Technical Director for SharedGeo.
# [http://wiki.osgeo.org/wiki/User:Maning Maning Sambale], OSGeo Charter Member
# [http://wiki.osgeo.org/wiki/User:Pcav Paolo Cavallini], QGIS PSC
# [http://wiki.osgeo.org/wiki/User:Dr Phillip Davis], Member OSGeo Geo For All education advisory board, Director @ GeoAcademy
# [http://wiki.osgeo.org/wiki/User:Nbozon Nicolas Bozon], [http://zoo-project.org ZOO-Project PSC], OSGeo Charter Member
# [http://www.linkedin.com/in/ruslanrainis Ruslan Rainis], Professor, Director, [http://www.research.usm.my/default.asp?tag=36 Centre for Research Initiatives in Liberal Arts & Social Sciences](CRI-LASS). Open GeoInformation for a Sustainable Tomorrow and the Bottom Billions.
# [[User:Silli|Silvia Franceschi]], [http://www.hydrologis.com HydroloGIS], OSGeo Charter member, Environmental Engineer Open Source GIS power user, HydroloGIS co-founder.
# Oscar Martinez Rubi [http://esciencecenter.nl Netherlands eScience Center] eScience engineer.
# Werner Macho, QGIS team member. Committed to open data standards for education and research.
# Giuseppe Patti, Geologist and Freelance Geospatial Advisor, GFOSS supporter.
# [http://wiki.osgeo.org/wiki/User:Drappo Daniel Rappo], Professor, University of Applied Sciences and Arts Western Switzerland, School of Business and Engineering Vaud.
# [[User:nachouve|Juan Ignacio Varela]], Freelance Geospatial Advisor and OSGeo Local Chapter Member.
# [[User:dmorissette|Daniel Morissette]], President at [http://mapgears.com Mapgears], OSGeo Charter member.
# Raul Nanclares, RS&GIS Specialist
# [http://www.ing.unitn.it/dica/hp/index_eng.php?user=rigon Riccardo Rigon], Professor at University of Trento (Italy)
# [[User:Siki| Zoltan Siki]] Budapest University of Technology and Economics (Hungary), OSGeo Charter member.
# [http://lefsky.org Michael Lefsky], Professor of Remote Sensing Science, Colorado State University and Director, Center for Ecological Applications of Lidar.
# Lucas Villa Real, Research software engineer at IBM Research - Brazil.
# [http://terraremote.com Loren Dawe], GIS Manager at Terra Remote Sensing Inc. Lidar Supplier and Open Standards Advocate
# Frank Warmerdam, Software Developer, OSGeo Charter member

=Background=
==About LiDAR==

[http://en.wikipedia.org/wiki/Lidar LiDAR] (Light Detection And Ranging) is a form of high precision range measurement, much like a radar system, that uses laser light instead of electromagnetic waves. The standard LiDAR product is a 3D point cloud that can be conceptualized as a series of point measurements representing distance between the sensor to a returned emission.

For over a decade (since 2003), there has been a common format for storing LiDAR data, the [http://www.asprs.org/Committee-General/LASer-LAS-File-Format-Exchange-Activities.html “LAS” format], and open source libraries have been developed to read, write and process these LAS files: [http://live.osgeo.org/en/overview/liblas_overview.html libLAS] and [http://github.com/LASlib/LASlib LASlib]. These libraries have been incorporated within many LiDAR applications, allowing read/write access to a common exchange format, and resulting in full interoperability between the applications. There is also an open source compression algorithm for the LAS format called [http://laszip.org LASzip] that many LiDAR data portals use to compress LAS into smaller LAZ files for faster download. Many LiDAR software packages have added [http://laszip.org/#software-with-native-laz-support native support] for these compressed LAZ files.

==LAS Limitations==

Quoting [http://boundlessgeo.com/2014/01/lidar-format-wars/ Paul Ramsey]:

: LAS format is not without its drawbacks:

:* While it is a binary format and does not waste any space unnecessarily, neither does it apply any compression to the data it stores. That’s not good for archival use.
:* Also, LAS stores points in scan order, so accessing any particular chunk of points involves reading the whole file. That’s not good for random access.
: Clearly there is a little more work to be done. Can LAS be improved? In fact, it already has been:
:* An open source compression library, LASzip can apply 20''':'''1 lossless compression to LAS files, making them great for archival purposes.
:* Other LAS users have experimented with re-ordering points in a LAS or LASzip file to allow random access to internal chunks of the LIDAR point cloud.
: Basically, making LAS smaller and faster is not rocket science, and if the work were incorporated into libLAS then the whole LIDAR community could leverage it together, and the user community would only have one file type to interchange.

=="Optimized LAS" A ''' ''Proprietary'' ESRI Format'''==
ESRI has announced the release of an [http://www.lidarnews.com/content/view/10214 "Optimized LAS"] format which is claimed to provide faster access and smaller file sizes (similar to the open [http://laszip.org LASzip] format). This announcement created a outburst of vocal protest in the LiDAR community [[http://rapidlasso.com/2013/12/30/new-compressed-las-format-by-esri/ 1] [http://boundlessgeo.com/2014/01/lidar-format-wars/ 2] [http://www.spatiallyadjusted.com/2014/01/15/las-laz-lazzip-zlas-and-you/ 3] [http://www.northrivergeographic.com/archives/lidar-software 4] [http://boundlessgeo.com/2014/01/lidar-format-wars-2/ 5] [http://boundlessgeo.com/2014/02/lidar-format-wars-3/ 6]].

The "Optimized LAS" format is neither published, nor available under any open license, which provides both technical as well as legal barriers for other applications reading and/or writing to this proprietary format. This creates a vendor lock-in scenario which is contrary to the principles of the Open Geospatial Consortium, the OSGeo Foundation, and many government IT procurement policies.

One year after releasing the "Optimized LAS" format, ESRI released a free Windows DLL that is claimed to convert between LAS and "Optimized LAS". Note there is a distinct difference between "free" and "open". Unless the Windows DLL is released under an "open" license, libLAS and related products will be legally prevented from incorporating ESRI's reader/writer code into their codebase, or from fixing any underlying bugs or performance limitations which may exist in ESRI's product.

==OGC's Efforts For An ''' ''Open'' LiDAR Standard'''==

The [http://www.opengeospatial.org/ Open Geospatial Consortium (OGC)] has indicated their interest in developing a standard LiDAR format.

Carl Reed (formerly on OGC staff) provided the following information on OGC's previous efforts to work toward enabling Open Standards in LiDAR:

: "Over the last 8 or so years, the OGC approached ASPRS at least twice regarding LAS and worked with ASPRS to bring LAS into the OGC for consideration as both a Best Practice and an OGC standard. OGC member Rick Pearsall worked diligently on this. Rick worked for NGA, was active in the OGC, and was also the Standards Committee chair at ASPRS. Rick and Carl tried and failed. These attempts go back to [http://www.asprs.org/a/society/divisions/ppd/ppd_meetings/2007springppdreport.pdf at least 2007]. More recently, Carl Reed had an email dialogue with Lewis Graham to bring LAS into OGC as an OGC Best Practice. Carl thought progress was being made, but then for some reason all communication stopped."

[http://www.opengeospatial.org/ogc/organization/staff/ssimmons Scott Simmons] (Executive Director, Standards Program) has explained the OGC's continuing interest in pursuing point cloud encoding standards, including a member-initiated mechanism to extend LAS data with OGC-standard XML content.
: The OGC invites interested members who wish to work on this effort to please contact Scott Simmons (Executive Director, Standards Program E-mail : ssimmons@opengeospatial.org) to register their interest and discuss details. OGC will also be holding an ad hoc session at the OGC's next [http://www.opengeospatial.org/event/1506tc Technical Committee meeting in Boulder, CO, USA in early June] to bring together all interested parties from all sectors (government, industry, academia) for this and plan next steps.

==History: LAS and ESRI's "Optimized LAS"==

Martin Isenburg, one of the leading experts in LIDAR formats, and creator of [http://rapidlasso.com/LASzip LASzip], [http://rapidlasso.com/LAStools LAStools] and [http://rapidlasso.com/PulseWaves PulseWaves], explains the history of LAS and "Optimized LAS":

: '''Summary:'''

:* The LAS format has been used successfully for over a decade.
:* Within last couple of years, ESRI has added native LAS support into ESRI products.
:* ESRI discussed embracing the open [http://laszip.org LAZ] format and simultaneously developed a proprietary "Optimized LAS" format.
:* The open geospatial community offered, on numerous occasions, to work with ESRI to avoid format fragmentation.
:* ESRI's proprietary "Optimized LAS" format is very similar in design and performance to the open [http://laszip.org LASzip] format.

: '''1998: Original LAS format definition'''

: The original development of the LAS format started in 1998 according to [http://groups.google.com/forum/#!topic/lasroom/zKqchDj1JL4/discussion Lewis Graham]. The effort was at first led by pioneers of the LiDAR industry until the format was donated to the [http://www.asprs.org/Committee-General/LASer-LAS-File-Format-Exchange-Activities.html ASPRS]. Since then ASPRS's [http://www.asprs.org/LD-Division/LAS-Working-Group.html LAS Working Group (LWG)] has been maintaining the LAS format, guiding it from the initial LAS 1.0 version until today's LAS 1.4 version. This effort successfully created an open data exchange format for discrete LiDAR points that is currently supported by practically every LiDAR-related software program.

: '''2011: ESRI joins LAS Working Group'''

: ESRI did not join the LWG of the ASPRS until rather late, the 24th of August in 2011. At that time ESRI was not a significant "player" in the LiDAR market given they did not have much support for LiDAR in any of their products. That was to change soon as they were planning to add LAS as a native data type in ArcGIS 10.1.

: Shortly before that, in June 2011, Martin Isenburg received a personal message from the ESRI development team: "I have a question about LAS compression. I’m evaluating some potential enhancements and support for [LAS and] LAZ is one of them. Compression time and amount is impressive." When inquiring two months later about the status of [http://laszip.org LAZ] integration Martin was told: "We’re in beta and working to finish the current release. I very much doubt LAZ will make it in because it’s too big a change at this time. So, we’ll be considering, for the following release, [for] what we want to do regarding compression and spatial indexing."

: '''June 2012: ArcGIS 10.1 includes [proprietary] LAS Dataset file'''

: In June 2012 ESRI released ArcGIS 10.1 and introduced the proprietary "LAS Dataset file (*.lasd)" that groups collections of files into one logical unit. This format of this useful LAS container file was not shared with others despite several private and eventually [http://groups.google.com/d/topic/lastools/jwHpi0efUgA/discussion public] requests.

: '''2012/2013: Collaboration Discussions'''

: There were encouraging follow-ups from the ESRI team about adopting the open LAZ format in January 2012: "I would be interested in having a more in depth meeting with you to better understand the great work you are doing with LAS and how we can possibly better partner on this." and again in December 2012: "If you have time, I'd like to set some time aside Tuesday afternoon to meet with <an important person> at the ESRI booth. Does 2pm sound okay?" The meeting went well and it looked as if ESRI was going to embrace the LAZ format because shortly after the meeting Martin got word that: "I hear from <an important person> that it was a success and that he had a good meeting with you. I wanted to see if we can have a telephone discussion on Wednesday or Thursday this week related to the potential of incorporating LAZ into ArcGIS."

: Then the first signs of hesitation showed. First there were legal issues raised in February 2013: "Currently the legal aspects are being reviewed. They were having some issues separating the LPGL aspects from LASzip from the remainder of LAStools etc." and then in April 2013 concerns about the code were made: "We have started to look into the integration of LAZ, but came across some issues. We don’t want to copy files from the other package, mix and match or hack around. We were hoping for an API to stream points out of a LAZ file as well as write LAZ files. There should be a simple code sample for that?" and - following up on that - in June 2013 Martin was told "I see value in LASzip becoming a de-facto standard that provides compression to the LAS format. If this is to happen then it needs to be bundled together with appropriate reference implementations, examples and documentation as a standard and so ensure that issues as defined earlier in email do not occur."

: '''June 2013: ESRI asked to sponsor clean LASzip DLL'''

: At that time [http://laszip.org LASzip] was an open source project without sponsorship. The original funding from [http://www.erdc.usace.army.mil/Locations/ColdRegionsResearchandEngineeringLaboratory.aspx USACE] that had turned [http://laszip.org LASzip] from an academic prototype into an industry strength compression engine had long run out. So Martin asked ESRI to become a sponsor to create the clean [http://laszip.org LASzip] API that ESRI was after. The answer was: "ESRI often helps in the financing of Open Source projects and I could foresee ESRI possibly helping in LASzip. [...] If you are interested in promoting LASzip as such a standard and doing the required work then I would recommend you put together a proposal and I can look to get ESRI as a sponsor."

: Immediately Martin proposed to ESRI: "I hereby propose to write an easy to use open source DLL wrapper for LASzip that will make it easier to integrate LASzip in a standardized manner into other software products such as ArcGIS, LP 360, or Terrasolid. This will come with example code on how to use the DLL for reading and writing LAZ files and include a few compressed example files. I hereby ask ESRI to provide funding for this effort without imposing any limitations on the produced DLL API."

: '''July 2013: ArcGIS 10.2 includes [proprietary] LAS indexing '''

: With the release of ArcGIS 10.2 in July 2013, ESRI introduced spatial indexing to speed up area-of-interest queries. The new proprietary *.lasx files with seemingly identical functionality to the open *.lax files that had been [http://groups.google.com/d/topic/lastools/j0qA8NBMHJs/discussion announced] in May 2011 and were [http://rapidlasso.com/2012/12/03/lasindex-spatial-indexing-of-lidar-data/ presented] at ELMF in November 2012.

: '''July 2013: Open LASzip API released'''

: After more requests for an easier interface to [http://laszip.org LASzip] (in particular for [http://forsys.cfr.washington.edu/fusion/fusionlatest.html USDA's FUSION]), Martin [http://groups.google.com/d/topic/lastools/oplsDhhnhDQ/discussion released] a clean, well-documented, and easy-to-use LASzip DLL (without ESRI funding). Martin expected that developers at ESRI would now use it to add read and write support for [http://laszip.org LAZ] to their next release of ArcGIS.

: '''December 2013 : ESRI discovered to be secretly developing proprietary LAS format'''

: In December of 2013, several LAStools users contacted Martin with suspicions that ESRI may be creating a proprietary LAS compression. Martin [http://rapidlasso.com/2013/12/30/new-compressed-las-format-by-esri/ broke the news] as soon as it became evident that ESRI had used the time it needed to resolve "legal issues" and "code problems" to put together their own proprietary compressed format with near-identical performance and functionality to [http://laszip.org LASzip]. A few days later ESRI released an [http://www.lidarnews.com/content/view/10214/ official FAQ] to confirming this was the case.

: From day one, Martin has worked with stakeholders, including ESRI, to avoid format fragmentation. Martin's core argument for resolving this to everybody's benefit was that - coincidentally - a natural break was happening in the LAS format with the introduction of the new LAS 1.4 point types. Martin outlined a detailed plan for how a joint development of [http://laszip.org LASzip] for LAS 1.4 between rapidlasso and ESRI could exploit this natural break in the LAS format to accomplish two things at once:
:# Add the unspecified technical additions that ESRI had hinted at desiring, and
:# Extend the [http://laszip.org LASzip] compression scheme to handle the new point types introduced with the LAS 1.4 specification. As there was no pressing need at the time to handle LAS 1.4 Martin had delayed the extension of [http://laszip.org LASzip] to the new LAS 1.4 point types to make sure a cooperation with ESRI would remain a viable option.

: '''1 April 2014: Positive reception to "Optimized LAS" / LASzip collaboration April Fools announcement'''

: In an attempt to convince ESRI management of the community desire for an open standard, Martin released an April Fools' Day [http://rapidlasso.com/2014/04/01/esri-and-rapidlasso-develop-joint-lidar-compressor/ prank press release] pretending that ESRI had already agreed to the envisioned collaboration to develop a joint LiDAR compressor. Community [http://rapidlasso.com/2014/04/01/esri-and-rapidlasso-develop-joint-lidar-compressor/ jubilant reactions (see comments)] left no doubt about the sentiment on this issue within the LiDAR community.

: '''October 2014: Announcement of [open] LAS Compatibility mode'''

: [http://www.csc.noaa.gov/digitalcoast/ Digital Coast, NOAA Coastal Services Center] became a Gold Sponsor of [http://laszip.org LASzip] for the development of the [http://rapidlasso.com/2014/10/06/rapidlasso-announces-laszip-compatibility-mode-for-las-1-4/ LAS 1.4 compatibility mode] that was [http://groups.google.com/d/topic/lastools/nUFMkKSz53g/discussion beta-released] in November 2014. This allowed support for the new point types in [http://laszip.org LASzip] without closing the door on a potential cooperation with ESRI for a joint LAS 1.4 compressor.

: '''November 2014: ESRI announces proprietary extension to LAS 1.4'''

: In November 2014 [http://blog.lidarnews.com/esri-las-optimizer-updated ESRI announced] that they had added their [http://blog.lidarnews.com/esri-las-optimizer-updated own extension] for the new LAS 1.4 point types to "Optimized LAS", dismissing the opportunity to develop a joint compressor and avoid format fragmentation by exploiting this "natural break" in the LAS format as Martin had suggested.

: Since then, ESRI has been [http://rapidlasso.com/2014/11/06/keeping-esri-honest/ promoting] "Optimized LAS". By including the term "LAS" in "Optimized LAS" and "zLAS", the distinction between the open LAS format and proprietary format is blurred. This is likely to mislead novice and future users, thereby endangering many years of standardization work. To date, [April 2014], the [http://www.asprs.org/a/society/committees/standards/LAS_1_4_r13.pdf custodians of the LAS format], the LAS Working Group (LWG) of the ASPRS has [http://rapidlasso.com/2015/02/22/lidar-las-asprs-esri-and-the-laz-clone/ yet to make an official statement] regarding use of the "LAS" name in promoting a proprietary LiDAR format.

=Value of Standards=

The importance of Open Standards is described in most government IT policies. For instance, the United Kingdom policy states:
: … Government assets should be interoperable and open for re-use in order to maximise return on investment, avoid technological or supplier lock-in, reduce operational risk in ICT projects and provide responsive services for citizens and business. This should also lower barriers to entry for more diverse sources of IT services, including citizens and SMEs. <ref>All about Open Source – An Introduction to Open Source Software for Government IT, Version 2.0, United Kingdom Cabinet Office https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/78959/All_About_Open_Source_v2_0.pdf</ref>

The value of Open Standards has been described in numerous national studies on the effects of standards on economic growth.

: ... the national studies demonstrate that standards have a positive influence on economic growth due to the resulting improved diffusion of knowledge. The contribution of standards to the growth rate in each country is equivalent to 0.9% in Germany, 0.8% in 0.3% in the UK and 0.2% in Canada. <ref>Prof. Dr. Knut Blind, Prof. Dr. Andre Jungmittag, Dr. Axel Mangelsdorf [http://www.din.de/sixcms_upload/media/2896/DIN_GNN_2011_engl_akt_neu.pdf "The Economic Benefits of Standardization"], ''DINN, 2000''. Retrieved March 2015.</ref>

=Further Reading=

# Paul Ramsey provides background to LAS vs Optimised LAS, http://boundlessgeo.com/2014/01/lidar-format-wars/
# Running commentary by Martin Isenburg, author of LASlib, http://rapidlasso.com/2015/02/22/lidar-las-asprs-esri-and-the-laz-clone/
# Earlier comment from Martin Isenburg, http://rapidlasso.com/2014/11/06/keeping-esri-honest/
# First call-to-action by Martin Isenburg, http://rapidlasso.com/2013/12/30/new-compressed-las-format-by-esri/
# ESRI Announces "Optimised LAS", http://blog.lidarnews.com/esri-announces-las-compression/
# ESRI description of "Optimised LAS", http://www.lidarnews.com/content/view/10214
# Discussion background on this topic at Geo for All list , http://lists.osgeo.org/pipermail/ica-osgeo-labs/2015-March/001225.html

=References=

<references />

Contacts

2015-01-08T15:13:56Z

Warmerdam: /* Software Projects */

OSGeo Projects are freestanding entities, handled by their own Project Steering Committees. Each project has been asked to provide a representative to help coordinate OSGeo involvement. These volunteers are listed by project below:

== General ==
* General Foundation Info - info@osgeo.org - [mailto:info@osgeo.org] (emails are currently forwarded to 3 people: FrankW, JeffM, Jachym)
* [[President]] - [[Jeff McKenna]] - jmckenna at osgeo.org
* [[Treasurer]] - [[Michael Smith]] - michael.smith.erdc at gmail.com
* [[Secretary]] - [[Jáchym Čepický]] - jachym.cepicky at gmail.com
* [[Board of Directors]]

== Software Projects ==
'''Web Mapping'''
* [http://www.deegree.org deegree]: [http://wiki.deegree.org/deegreeWiki/StructuresAndProcedures PSC] - Contact: [[User:JensFitzke | Jens Fitzke]]
* [http://geomajas.org Geomajas]: [http://www.geomajas.org/geomajas/project-steering-committee PSC] - Chair: Pieter De Graef (pieter.degraef at geosparc.com)
* [http://www.geomoose.org/ GeoMoose]: [http://www.geomoose.org/rfc/rfc-1.html PSC] - Chair: - Brian Fischer (bfischer at houstoneng.com)
* [http://geoserver.org GeoServer]: [http://docs.geoserver.org/latest/en/developer/policies/psc.html PSC] - Project Officer: Andrea Aime (andrea dot aime at geo-solutions.it) (checked 2014-10-09)
* [http://www.mapbender.org Mapbender]: [http://www.mapbender.org/index.php/Category:PSC PSC] - Chair: Christian Wygoda
* [http://www.mapfish.org MapFish]: [http://trac.mapfish.org/trac/mapfish/wiki/Community/PSC PSC] - Chair: [[User:Elem | Eric Lemoine]]
* [http://mapguide.osgeo.org/ MapGuide Open Source]: [http://mapguide.osgeo.org/psc.html PSC] - Chair: Robert Bray (robert.bray at autodesk.com)
* [http://mapserver.org/ MapServer]: [http://mapserver.org/development/rfc/ms-rfc-23.html PSC] - Chair: Stephen Lime (sdlime at comcast.net)
* [http://openlayers.org/ OpenLayers]: [http://trac.openlayers.org/wiki/SteeringCommittee PSC] - Chair: [[User:Tschaub | Tim Schaub]]

'''Desktop Applications'''
* [http://grass.osgeo.org/ GRASS GIS]: [http://trac.osgeo.org/grass/wiki/PSC PSC] - Chair: [[Markus Neteler]]
* [http://www.gvsig.org/ gvSIG]: - [[GvSIG Technical Project Committee|PSC]] - Chair: [[Manuel Madrid]] (checked 2014-10-14)
* [http://marble.kde.org/ Marble]: [http://edu.kde.org/marble/authors.php Authors] - Liaison Officer: [[Torsten Rahn]]
* [http://www.ossim.org/ OSSIM]: [http://trac.osgeo.org/ossim/wiki/ossimgovernance PSC] - Chair: Garrett Potts
* [http://www.qgis.org/ Quantum GIS]: [http://wiki.qgis.org/qgiswiki/Project_Organigram PSC] (outdated, see [http://spatialgalaxy.net/2013/08/25/welcome-to-new-qgis-psc-members/ this blog post] by Gary Sherman for the current PSC members - Chair: Gary Sherman (sherman at mrcc.com)

'''Geospatial Libraries'''
* [http://fdo.osgeo.org/ FDO]: [http://fdo.osgeo.org/ Home Page] (link to PSC broken) - Chair: Greg Boone (greg.boone at autodesk.com)
* [http://www.gdal.org/ GDAL/OGR]: [http://trac.osgeo.org/gdal/wiki/GovernanceAndCommunity PSC] - Chair: Even Rouault (even.rouault at spatialys.com)
* [http://www.geotools.org/ GeoTools]: [http://docs.codehaus.org/display/GEOT/4+Project+Management+Committee PSC] - Project Officer Jody Garnett (jody.garnett at gmail.com) (checked 2014-10-09)
* [http://geos.osgeo.org/ GEOS]: [http://trac.osgeo.org/geos/wiki/PSC PSC] - Chair: [[User:Strk | Sandro Santilli]] (strk at keybit.net)
* [http://metacrs.osgeo.org/ MetaCRS]: [http://metacrs.osgeo.org PSC] - Chair: Frank Warmerdam (warmerdam@pobox.com)
* [http://postgis.net/ PostGIS]: [http://postgis.net/docs/postgis_introduction.html#psc PSC] - Chair: [[User:Pwramsey3 | Paul Ramsey]]
* [http://pgrouting.org/ pgRouting]: [http://pgrouting.org/development.html PSC] - Chair: [[User:Woodbri | Stephen Woodbridge]]

'''Metadata Catalog'''
* [http://geonetwork-opensource.org GeoNetwork opensource]: [http://trac.osgeo.org/geonetwork/wiki/PSC PSC] - Chair: [[User:Ticheler | Jeroen Ticheler]] (Jeroen.Ticheler at geocat.net) (checked 2014-10-09)

'''Spatio-Temporal Analytics'''
* [http://www.rasdaman.org rasdaman opensource]: [http://rasdaman.org/wiki/Governance PSC] - Chair: [[User:Pebau | Peter Baumann]] (baumann at rasdaman.com) (checked 2014-10-09)

== Committees ==
* [[Conference Committee]] -
* [[Education and Curriculum Committee]] - Charlie Schweik - cschweik at pubpol.umass.edu (checked 2014-10-09)
* [[Finance Committee]] - [[User:Dmorissette|Daniel Morissette]] - dmorissette at mapgears.com (checked 2014-10-09)
* [[Incubation Committee]] - Jody Garnett - jody.garnett at gmail.com (checked 2014-10-09)
* [[Marketing Committee]] - Cameron Shorter - cameron.shorter at gmail.com (checked 2014-10-09)
* [[Public Geospatial Data Committee]] - [[User:Bitner|David Bitner]] - bitner at dbspatial dot com (checked 2014-10-09)
* [[SAC|System Administration Committee]] - Alex Mandel - tech_dev at wildintellect.com (checked 2014-10-09)
* [[Website Committee]] - Christopher Schmidt - crschmidt at crschmidt.net
* OSGeo [[Journal]]

== Packaging ==
* [http://live.osgeo.org OSGeo-Live] - Cameron Shorter - cameron.shorter at gmail.com

== Local Chapters ==

Contacts list for the [[:Category:Local_Chapters|local chapters]]:
* [[Africa Local Chapter]] - [[User:Gfleming|Gavin Fleming]]
* [[Aust-NZ]] - Australia and New Zealand Chapter- Bruce Bannerman - bruce.bannerman.osgeo at gmail.com
* [[Brazil]] - Helton Uchoa - engenheiro.uchoa at gmail.com
* [[California]] - Landon Blake - sunburned.surveyor at gmail dot com
* [[Cascadia|CUGOS Cascadia Chapter US]] - [[User:Racicot|Aaron Racicot]] - aaronr at cugos.org (checked 2014-10-09)
* [[China]] - Chen Rongguo - chenrg at lreis.ac.cn
* [[D-A-CH]] (German language) - [[User:Mlechner|Marco Lechner]] (checked 2014-09-30)
* [[Finland]] - [[User:AJolma|Ari Jolma]] - ajolma at osgeo.org (checked 2014-10-09)
* [[Francophone]] - board at osgeo.asso dot fr / president at osgeo.asso.fr (Etienne Delay) (checked 2014-09-30)
* [[Greek]] - [[User:kotzino|Dimitris Kotzinos]] - kotzino at csd dot uoc dot gr (checked 2014-09-30)
* [[India]] - P.S. Roy - psroy13 at gmail.com
* [[Italy]] - [[User:epifanio|Massimo Di Stefano]] - IT -- epiesasha at me dot com
* [[Japan]] - Mr. Mori Toru - moritoru at orkney.co.jp (checked 2014-09-30)
* [[Korea | Korean Chapter]] - [[User:Endofcap|Sanghee Shin]] - shshin at gaia3d.com or endofcap at gmail.com (checked 2014-09-30)
* [[KSA Chapter]] - Awase Khirni Syed - awasekhirni at gmail.com
* [[Nederlands | Dutch language Chapter]] - [[User:Just|Just van den Broecke]] (secretary) [[User:Geejee|Gert-Jan van der Weijden]] (president). info at osgeo dot nl (checked 2014-10-08)
* [[Ottawa Chapter]] - Fabien Ancelin - fabien.ancelin at gmail.com
* [[PDX-OSGEO]] - Oregon, US Chapter -- [[User:EliL|Eli L Adam]] - contact on user page (checked 2014-09-30)
* [[Philippines]] - [[User:maning|Maning Sambale]] - emmanuel dot sambale at gmail dot com (checked 2014-10-09)
* [[Poland]] - Tomasz Kubik - tomasz kubik at pwr wroc pl (checked 2014-09-30)
* [[Portugal]] - Jorge Gustavo Rocha - [[Jorge_Gustavo_Rocha]], Giovanni Manghi - [[Giovanni_Manghi]]
* [[Romanian]] - [[User:Vasile|Vasile Crăciunescu]] - vasile at geo-spatial dot org
* [[Quebec]] - [[User:Dmorissette|Daniel Morissette]] - dmorissette at mapgears dot com (checked 2014-10-09)
* [[Spanish]] - [[Pedro-Juan Ferrer]] - vehrka at gmail.com (checked 2014-10-09)
* [[Taiwan]] - Sander Borghuis - s.borghuis at geo.uu.nl '''(mail not delivered)'''
* [[Twin_Cities]] - Twin Cities, MN -- [[User:Bitner|David Bitner]] - bitner at dbspatial dot com
* [[Yukon Chapter]] - [[User:hammj|Jeff Hamm]] - jeff at geoprism dot ca
* [http://www.osgeo.org/uk UK] - [[User:JoCook|Jo Cook]]

== Infrastructure ==

* [[SAC:Primary Administrators]]

== Local Representatives ==

* list of local leaders by region: [[OSGeo Advocate]]

[[Category:Board]]
[[Category:Education]]
[[Category:Incubation]]
[[Category:Infrastructure]]
[[Category:PSC]]

Contacts

2015-01-08T15:12:55Z

Warmerdam: /* Committees */ Frank never actually stepped into conference chair role.

OSGeo Projects are freestanding entities, handled by their own Project Steering Committees. Each project has been asked to provide a representative to help coordinate OSGeo involvement. These volunteers are listed by project below:

== General ==
* General Foundation Info - info@osgeo.org - [mailto:info@osgeo.org] (emails are currently forwarded to 3 people: FrankW, JeffM, Jachym)
* [[President]] - [[Jeff McKenna]] - jmckenna at osgeo.org
* [[Treasurer]] - [[Michael Smith]] - michael.smith.erdc at gmail.com
* [[Secretary]] - [[Jáchym Čepický]] - jachym.cepicky at gmail.com
* [[Board of Directors]]

== Software Projects ==
'''Web Mapping'''
* [http://www.deegree.org deegree]: [http://wiki.deegree.org/deegreeWiki/StructuresAndProcedures PSC] - Contact: [[User:JensFitzke | Jens Fitzke]]
* [http://geomajas.org Geomajas]: [http://www.geomajas.org/geomajas/project-steering-committee PSC] - Chair: Pieter De Graef (pieter.degraef at geosparc.com)
* [http://www.geomoose.org/ GeoMoose]: [http://www.geomoose.org/rfc/rfc-1.html PSC] - Chair: - Brian Fischer (bfischer at houstoneng.com)
* [http://geoserver.org GeoServer]: [http://docs.geoserver.org/latest/en/developer/policies/psc.html PSC] - Project Officer: Andrea Aime (andrea dot aime at geo-solutions.it) (checked 2014-10-09)
* [http://www.mapbender.org Mapbender]: [http://www.mapbender.org/index.php/Category:PSC PSC] - Chair: Christian Wygoda
* [http://www.mapfish.org MapFish]: [http://trac.mapfish.org/trac/mapfish/wiki/Community/PSC PSC] - Chair: [[User:Elem | Eric Lemoine]]
* [http://mapguide.osgeo.org/ MapGuide Open Source]: [http://mapguide.osgeo.org/psc.html PSC] - Chair: Robert Bray (robert.bray at autodesk.com)
* [http://mapserver.org/ MapServer]: [http://mapserver.org/development/rfc/ms-rfc-23.html PSC] - Chair: Stephen Lime (sdlime at comcast.net)
* [http://openlayers.org/ OpenLayers]: [http://trac.openlayers.org/wiki/SteeringCommittee PSC] - Chair: [[User:Tschaub | Tim Schaub]]

'''Desktop Applications'''
* [http://grass.osgeo.org/ GRASS GIS]: [http://trac.osgeo.org/grass/wiki/PSC PSC] - Chair: [[Markus Neteler]]
* [http://www.gvsig.org/ gvSIG]: - [[GvSIG Technical Project Committee|PSC]] - Chair: [[Manuel Madrid]] (checked 2014-10-14)
* [http://marble.kde.org/ Marble]: [http://edu.kde.org/marble/authors.php Authors] - Liaison Officer: [[Torsten Rahn]]
* [http://www.ossim.org/ OSSIM]: [http://trac.osgeo.org/ossim/wiki/ossimgovernance PSC] - Chair: Garrett Potts
* [http://www.qgis.org/ Quantum GIS]: [http://wiki.qgis.org/qgiswiki/Project_Organigram PSC] (outdated, see [http://spatialgalaxy.net/2013/08/25/welcome-to-new-qgis-psc-members/ this blog post] by Gary Sherman for the current PSC members - Chair: Gary Sherman (sherman at mrcc.com)

'''Geospatial Libraries'''
* [http://fdo.osgeo.org/ FDO]: [http://fdo.osgeo.org/ Home Page] (link to PSC broken) - Chair: Greg Boone (greg.boone at autodesk.com)
* [http://www.gdal.org/ GDAL/OGR]: [http://trac.osgeo.org/gdal/wiki/GovernanceAndCommunity PSC] - Chair: Even Rouault (even.rouault@spatialys.com)
* [http://www.geotools.org/ GeoTools]: [http://docs.codehaus.org/display/GEOT/4+Project+Management+Committee PSC] - Project Officer Jody Garnett (jody.garnett at gmail.com) (checked 2014-10-09)
* [http://geos.osgeo.org/ GEOS]: [http://trac.osgeo.org/geos/wiki/PSC PSC] - Chair: [[User:Strk | Sandro Santilli]] (strk at keybit.net)
* [http://metacrs.osgeo.org/ MetaCRS]: [http://metacrs.osgeo.org PSC] - Chair: Frank Warmerdam (warmerdam@pobox.com)
* [http://postgis.net/ PostGIS]: [http://postgis.net/docs/postgis_introduction.html#psc PSC] - Chair: [[User:Pwramsey3 | Paul Ramsey]]
* [http://pgrouting.org/ pgRouting]: [http://pgrouting.org/development.html PSC] - Chair: [[User:Woodbri | Stephen Woodbridge]]

'''Metadata Catalog'''
* [http://geonetwork-opensource.org GeoNetwork opensource]: [http://trac.osgeo.org/geonetwork/wiki/PSC PSC] - Chair: [[User:Ticheler | Jeroen Ticheler]] (Jeroen.Ticheler at geocat.net) (checked 2014-10-09)

'''Spatio-Temporal Analytics'''
* [http://www.rasdaman.org rasdaman opensource]: [http://rasdaman.org/wiki/Governance PSC] - Chair: [[User:Pebau | Peter Baumann]] (baumann at rasdaman.com) (checked 2014-10-09)

== Committees ==
* [[Conference Committee]] -
* [[Education and Curriculum Committee]] - Charlie Schweik - cschweik at pubpol.umass.edu (checked 2014-10-09)
* [[Finance Committee]] - [[User:Dmorissette|Daniel Morissette]] - dmorissette at mapgears.com (checked 2014-10-09)
* [[Incubation Committee]] - Jody Garnett - jody.garnett at gmail.com (checked 2014-10-09)
* [[Marketing Committee]] - Cameron Shorter - cameron.shorter at gmail.com (checked 2014-10-09)
* [[Public Geospatial Data Committee]] - [[User:Bitner|David Bitner]] - bitner at dbspatial dot com (checked 2014-10-09)
* [[SAC|System Administration Committee]] - Alex Mandel - tech_dev at wildintellect.com (checked 2014-10-09)
* [[Website Committee]] - Christopher Schmidt - crschmidt at crschmidt.net
* OSGeo [[Journal]]

== Packaging ==
* [http://live.osgeo.org OSGeo-Live] - Cameron Shorter - cameron.shorter at gmail.com

== Local Chapters ==

Contacts list for the [[:Category:Local_Chapters|local chapters]]:
* [[Africa Local Chapter]] - [[User:Gfleming|Gavin Fleming]]
* [[Aust-NZ]] - Australia and New Zealand Chapter- Bruce Bannerman - bruce.bannerman.osgeo at gmail.com
* [[Brazil]] - Helton Uchoa - engenheiro.uchoa at gmail.com
* [[California]] - Landon Blake - sunburned.surveyor at gmail dot com
* [[Cascadia|CUGOS Cascadia Chapter US]] - [[User:Racicot|Aaron Racicot]] - aaronr at cugos.org (checked 2014-10-09)
* [[China]] - Chen Rongguo - chenrg at lreis.ac.cn
* [[D-A-CH]] (German language) - [[User:Mlechner|Marco Lechner]] (checked 2014-09-30)
* [[Finland]] - [[User:AJolma|Ari Jolma]] - ajolma at osgeo.org (checked 2014-10-09)
* [[Francophone]] - board at osgeo.asso dot fr / president at osgeo.asso.fr (Etienne Delay) (checked 2014-09-30)
* [[Greek]] - [[User:kotzino|Dimitris Kotzinos]] - kotzino at csd dot uoc dot gr (checked 2014-09-30)
* [[India]] - P.S. Roy - psroy13 at gmail.com
* [[Italy]] - [[User:epifanio|Massimo Di Stefano]] - IT -- epiesasha at me dot com
* [[Japan]] - Mr. Mori Toru - moritoru at orkney.co.jp (checked 2014-09-30)
* [[Korea | Korean Chapter]] - [[User:Endofcap|Sanghee Shin]] - shshin at gaia3d.com or endofcap at gmail.com (checked 2014-09-30)
* [[KSA Chapter]] - Awase Khirni Syed - awasekhirni at gmail.com
* [[Nederlands | Dutch language Chapter]] - [[User:Just|Just van den Broecke]] (secretary) [[User:Geejee|Gert-Jan van der Weijden]] (president). info at osgeo dot nl (checked 2014-10-08)
* [[Ottawa Chapter]] - Fabien Ancelin - fabien.ancelin at gmail.com
* [[PDX-OSGEO]] - Oregon, US Chapter -- [[User:EliL|Eli L Adam]] - contact on user page (checked 2014-09-30)
* [[Philippines]] - [[User:maning|Maning Sambale]] - emmanuel dot sambale at gmail dot com (checked 2014-10-09)
* [[Poland]] - Tomasz Kubik - tomasz kubik at pwr wroc pl (checked 2014-09-30)
* [[Portugal]] - Jorge Gustavo Rocha - [[Jorge_Gustavo_Rocha]], Giovanni Manghi - [[Giovanni_Manghi]]
* [[Romanian]] - [[User:Vasile|Vasile Crăciunescu]] - vasile at geo-spatial dot org
* [[Quebec]] - [[User:Dmorissette|Daniel Morissette]] - dmorissette at mapgears dot com (checked 2014-10-09)
* [[Spanish]] - [[Pedro-Juan Ferrer]] - vehrka at gmail.com (checked 2014-10-09)
* [[Taiwan]] - Sander Borghuis - s.borghuis at geo.uu.nl '''(mail not delivered)'''
* [[Twin_Cities]] - Twin Cities, MN -- [[User:Bitner|David Bitner]] - bitner at dbspatial dot com
* [[Yukon Chapter]] - [[User:hammj|Jeff Hamm]] - jeff at geoprism dot ca
* [http://www.osgeo.org/uk UK] - [[User:JoCook|Jo Cook]]

== Infrastructure ==

* [[SAC:Primary Administrators]]

== Local Representatives ==

* list of local leaders by region: [[OSGeo Advocate]]

[[Category:Board]]
[[Category:Education]]
[[Category:Incubation]]
[[Category:Infrastructure]]
[[Category:PSC]]

Contacts

2015-01-08T15:12:15Z

Warmerdam: /* Software Projects */ Even now GDAL Chair

OSGeo Projects are freestanding entities, handled by their own Project Steering Committees. Each project has been asked to provide a representative to help coordinate OSGeo involvement. These volunteers are listed by project below:

== General ==
* General Foundation Info - info@osgeo.org - [mailto:info@osgeo.org] (emails are currently forwarded to 3 people: FrankW, JeffM, Jachym)
* [[President]] - [[Jeff McKenna]] - jmckenna at osgeo.org
* [[Treasurer]] - [[Michael Smith]] - michael.smith.erdc at gmail.com
* [[Secretary]] - [[Jáchym Čepický]] - jachym.cepicky at gmail.com
* [[Board of Directors]]

== Software Projects ==
'''Web Mapping'''
* [http://www.deegree.org deegree]: [http://wiki.deegree.org/deegreeWiki/StructuresAndProcedures PSC] - Contact: [[User:JensFitzke | Jens Fitzke]]
* [http://geomajas.org Geomajas]: [http://www.geomajas.org/geomajas/project-steering-committee PSC] - Chair: Pieter De Graef (pieter.degraef at geosparc.com)
* [http://www.geomoose.org/ GeoMoose]: [http://www.geomoose.org/rfc/rfc-1.html PSC] - Chair: - Brian Fischer (bfischer at houstoneng.com)
* [http://geoserver.org GeoServer]: [http://docs.geoserver.org/latest/en/developer/policies/psc.html PSC] - Project Officer: Andrea Aime (andrea dot aime at geo-solutions.it) (checked 2014-10-09)
* [http://www.mapbender.org Mapbender]: [http://www.mapbender.org/index.php/Category:PSC PSC] - Chair: Christian Wygoda
* [http://www.mapfish.org MapFish]: [http://trac.mapfish.org/trac/mapfish/wiki/Community/PSC PSC] - Chair: [[User:Elem | Eric Lemoine]]
* [http://mapguide.osgeo.org/ MapGuide Open Source]: [http://mapguide.osgeo.org/psc.html PSC] - Chair: Robert Bray (robert.bray at autodesk.com)
* [http://mapserver.org/ MapServer]: [http://mapserver.org/development/rfc/ms-rfc-23.html PSC] - Chair: Stephen Lime (sdlime at comcast.net)
* [http://openlayers.org/ OpenLayers]: [http://trac.openlayers.org/wiki/SteeringCommittee PSC] - Chair: [[User:Tschaub | Tim Schaub]]

'''Desktop Applications'''
* [http://grass.osgeo.org/ GRASS GIS]: [http://trac.osgeo.org/grass/wiki/PSC PSC] - Chair: [[Markus Neteler]]
* [http://www.gvsig.org/ gvSIG]: - [[GvSIG Technical Project Committee|PSC]] - Chair: [[Manuel Madrid]] (checked 2014-10-14)
* [http://marble.kde.org/ Marble]: [http://edu.kde.org/marble/authors.php Authors] - Liaison Officer: [[Torsten Rahn]]
* [http://www.ossim.org/ OSSIM]: [http://trac.osgeo.org/ossim/wiki/ossimgovernance PSC] - Chair: Garrett Potts
* [http://www.qgis.org/ Quantum GIS]: [http://wiki.qgis.org/qgiswiki/Project_Organigram PSC] (outdated, see [http://spatialgalaxy.net/2013/08/25/welcome-to-new-qgis-psc-members/ this blog post] by Gary Sherman for the current PSC members - Chair: Gary Sherman (sherman at mrcc.com)

'''Geospatial Libraries'''
* [http://fdo.osgeo.org/ FDO]: [http://fdo.osgeo.org/ Home Page] (link to PSC broken) - Chair: Greg Boone (greg.boone at autodesk.com)
* [http://www.gdal.org/ GDAL/OGR]: [http://trac.osgeo.org/gdal/wiki/GovernanceAndCommunity PSC] - Chair: Even Rouault (even.rouault@spatialys.com)
* [http://www.geotools.org/ GeoTools]: [http://docs.codehaus.org/display/GEOT/4+Project+Management+Committee PSC] - Project Officer Jody Garnett (jody.garnett at gmail.com) (checked 2014-10-09)
* [http://geos.osgeo.org/ GEOS]: [http://trac.osgeo.org/geos/wiki/PSC PSC] - Chair: [[User:Strk | Sandro Santilli]] (strk at keybit.net)
* [http://metacrs.osgeo.org/ MetaCRS]: [http://metacrs.osgeo.org PSC] - Chair: Frank Warmerdam (warmerdam@pobox.com)
* [http://postgis.net/ PostGIS]: [http://postgis.net/docs/postgis_introduction.html#psc PSC] - Chair: [[User:Pwramsey3 | Paul Ramsey]]
* [http://pgrouting.org/ pgRouting]: [http://pgrouting.org/development.html PSC] - Chair: [[User:Woodbri | Stephen Woodbridge]]

'''Metadata Catalog'''
* [http://geonetwork-opensource.org GeoNetwork opensource]: [http://trac.osgeo.org/geonetwork/wiki/PSC PSC] - Chair: [[User:Ticheler | Jeroen Ticheler]] (Jeroen.Ticheler at geocat.net) (checked 2014-10-09)

'''Spatio-Temporal Analytics'''
* [http://www.rasdaman.org rasdaman opensource]: [http://rasdaman.org/wiki/Governance PSC] - Chair: [[User:Pebau | Peter Baumann]] (baumann at rasdaman.com) (checked 2014-10-09)

== Committees ==
* [[Conference Committee]] - Frank Warmerdam - warmerdam at pobox.com
* [[Education and Curriculum Committee]] - Charlie Schweik - cschweik at pubpol.umass.edu (checked 2014-10-09)
* [[Finance Committee]] - [[User:Dmorissette|Daniel Morissette]] - dmorissette at mapgears.com (checked 2014-10-09)
* [[Incubation Committee]] - Jody Garnett - jody.garnett at gmail.com (checked 2014-10-09)
* [[Marketing Committee]] - Cameron Shorter - cameron.shorter at gmail.com (checked 2014-10-09)
* [[Public Geospatial Data Committee]] - [[User:Bitner|David Bitner]] - bitner at dbspatial dot com (checked 2014-10-09)
* [[SAC|System Administration Committee]] - Alex Mandel - tech_dev at wildintellect.com (checked 2014-10-09)
* [[Website Committee]] - Christopher Schmidt - crschmidt at crschmidt.net
* OSGeo [[Journal]]

== Packaging ==
* [http://live.osgeo.org OSGeo-Live] - Cameron Shorter - cameron.shorter at gmail.com

== Local Chapters ==

Contacts list for the [[:Category:Local_Chapters|local chapters]]:
* [[Africa Local Chapter]] - [[User:Gfleming|Gavin Fleming]]
* [[Aust-NZ]] - Australia and New Zealand Chapter- Bruce Bannerman - bruce.bannerman.osgeo at gmail.com
* [[Brazil]] - Helton Uchoa - engenheiro.uchoa at gmail.com
* [[California]] - Landon Blake - sunburned.surveyor at gmail dot com
* [[Cascadia|CUGOS Cascadia Chapter US]] - [[User:Racicot|Aaron Racicot]] - aaronr at cugos.org (checked 2014-10-09)
* [[China]] - Chen Rongguo - chenrg at lreis.ac.cn
* [[D-A-CH]] (German language) - [[User:Mlechner|Marco Lechner]] (checked 2014-09-30)
* [[Finland]] - [[User:AJolma|Ari Jolma]] - ajolma at osgeo.org (checked 2014-10-09)
* [[Francophone]] - board at osgeo.asso dot fr / president at osgeo.asso.fr (Etienne Delay) (checked 2014-09-30)
* [[Greek]] - [[User:kotzino|Dimitris Kotzinos]] - kotzino at csd dot uoc dot gr (checked 2014-09-30)
* [[India]] - P.S. Roy - psroy13 at gmail.com
* [[Italy]] - [[User:epifanio|Massimo Di Stefano]] - IT -- epiesasha at me dot com
* [[Japan]] - Mr. Mori Toru - moritoru at orkney.co.jp (checked 2014-09-30)
* [[Korea | Korean Chapter]] - [[User:Endofcap|Sanghee Shin]] - shshin at gaia3d.com or endofcap at gmail.com (checked 2014-09-30)
* [[KSA Chapter]] - Awase Khirni Syed - awasekhirni at gmail.com
* [[Nederlands | Dutch language Chapter]] - [[User:Just|Just van den Broecke]] (secretary) [[User:Geejee|Gert-Jan van der Weijden]] (president). info at osgeo dot nl (checked 2014-10-08)
* [[Ottawa Chapter]] - Fabien Ancelin - fabien.ancelin at gmail.com
* [[PDX-OSGEO]] - Oregon, US Chapter -- [[User:EliL|Eli L Adam]] - contact on user page (checked 2014-09-30)
* [[Philippines]] - [[User:maning|Maning Sambale]] - emmanuel dot sambale at gmail dot com (checked 2014-10-09)
* [[Poland]] - Tomasz Kubik - tomasz kubik at pwr wroc pl (checked 2014-09-30)
* [[Portugal]] - Jorge Gustavo Rocha - [[Jorge_Gustavo_Rocha]], Giovanni Manghi - [[Giovanni_Manghi]]
* [[Romanian]] - [[User:Vasile|Vasile Crăciunescu]] - vasile at geo-spatial dot org
* [[Quebec]] - [[User:Dmorissette|Daniel Morissette]] - dmorissette at mapgears dot com (checked 2014-10-09)
* [[Spanish]] - [[Pedro-Juan Ferrer]] - vehrka at gmail.com (checked 2014-10-09)
* [[Taiwan]] - Sander Borghuis - s.borghuis at geo.uu.nl '''(mail not delivered)'''
* [[Twin_Cities]] - Twin Cities, MN -- [[User:Bitner|David Bitner]] - bitner at dbspatial dot com
* [[Yukon Chapter]] - [[User:hammj|Jeff Hamm]] - jeff at geoprism dot ca
* [http://www.osgeo.org/uk UK] - [[User:JoCook|Jo Cook]]

== Infrastructure ==

* [[SAC:Primary Administrators]]

== Local Representatives ==

* list of local leaders by region: [[OSGeo Advocate]]

[[Category:Board]]
[[Category:Education]]
[[Category:Incubation]]
[[Category:Infrastructure]]
[[Category:PSC]]

WebExtraVM

2014-09-17T05:36:22Z

Warmerdam: /* *.foss4g.org */

The Web Extra VM is a Debian virtual machine administered by [[SAC]], hosted on OSGeo3 at OSU OSL and used for hosting web sites and services that are directly the responsibility of SAC and that don't fit on the other more special purpose VMs (ie. TracSVN, or Drupal). OSGeo member/project services that SAC isn't willing to take direct responsibility for likely belong on either the [[ProjectsVM]] or the [[AdhocVM]].

The VM is reachable by ssh at webextra.osgeo.osuosl.org. Anyone in the https://www.osgeo.org/cgi-bin/auth/ldap_shell.py?group=sac (SAC) list has ssh access, and anyone in this group can add new people via the link.

== Existing Services on Web Extra VM ==

=== mum03.mapserver.org ===

* /osgeo/foss4g/mum2003-web
* Admined by FrankW
* static html historial site
* Backup available in /osgeo/backup/longterm/mum03 on BackupVM.

=== planet.osgeo.org ===

* /osgeo/venus (venus2?)
* Admined: [[Paolo Corti]], [[User:Jsanz|Jorge Gaspar Sanz Salinas]], [[User:Mloskot|Mateusz Loskot]], [[User:crschmidt|Christopher Schmidt]]
* See also: [[PlanetOSGeo]]
* All admins can be contacted by e-mail on planet (at) osgeo (dot) org

=== live.osgeo.org ===

* /osgeo/osgeolive
* Static html site from SVN (https://svn.osgeo.org/osgeo/livedvd/website)
* Alex (wildintellect)

=== gallery.osgeo.org ===

Status: offline due to massive spamming

TODO: implement moderated queue or other antispam measure

* /var/www/gallery/
* content is in sqlite DB
* Spam removal howto: to be implemented

=== 2011ws.foss4g.org ===

* /osgeo/foss4g/uploads
* Admined by FrankW, jmckenna
* used for FOSS4G 2011 workshop files (through SFTP)

=== *.foss4g.org ===
Includes main www and 2003, 2006, 2007, 2008, 2009, 2010, 2012, 2013
/osgeo/foss4g/*
* 2011 is on webvm - as it's using Drupal
* Most are static dumps from CMSs that were used,
* 2008 uses the OCS instance (conference.osgeo.org) hosted on webextra
/osgeo/ocs2
* Most being moved from osgeo1 29sep11 by tmitchell
* 2010 also moved from projects vm.
* 2013 site lives in svn and is checked out here manually
* Backups should be put /mirror/longterm on backup.osgeo.org as a comperessed tar file per the instructions there.

=== vmap0.tiles.osgeo.org ===

* Serves as http://vmap0.tiles.osgeo.org/wms/vmap0?SERVICE=WMS&VERSION=1.1.0&REQUEST=GetCapabilities
* Lives in /var/www/tiles/vmap0 and /mapdata (2.3G)
* Originally setup by Chris Schmidt.
* Currently produces the bulk of load on the webextra VM.
* Presumably this is widely used as a default layer in OpenLayers.
* For the purpose of sharing the load, a copy of this service has been set up on "sphere.telascience.org" and a round-robin DNS provides balancing (Martin Spott).

[[Category:Infrastructure]]

ZOO-Project Incubation Checklist

2014-09-14T00:26:41Z

Warmerdam: /* Processes */ preliminary

= Incubation Checklist =

== Open ==

The project has demonstrated that it has an open, active and healthy user and developer community:
# Open: projects are expected to function in an open and public manner and include:
#* Open source license(s),
#** The ZOO-Project is primarily under the BSD [http://www.zoo-project.org/trac/browser/trunk/zoo-project/LICENSE LICENSE] and the [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance Review] has confirmed there are no known problems.
#* Open communication channels,
#** The [http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss zoo-discuss] list is public and active. IRC and other [http://zoo-project.org/site/ZooWebSite/ZooProject/Contact Contact] points also available.
#* Open decision making process,
#** (Gerald is looking into making zoo-psc list public). PSC meeting agenda and results available (for instance [http://zoo-project.org/trac/wiki/PSC/meetings/PSCMeet19?version=8 PSC Meeting 19]).
# Active and healthy community:
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. 
#** Suggested Text?
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. 
#** contributions come from GeoLabs SARL, Fundazione Edmund Mach, 3LIZ SARL, Cartogenic SARL and further more.

== Copyright and License ==

We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:
# All project source code is available under an Open Source license.
#* Yes, as seen in [http://www.zoo-project.org/trac/browser/trunk/zoo-project/LICENSE LICENSE].
# Project documentation is available under an open license, such as Creative Commons.
#* (to confirm)
# The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included, as per a [http://www.osgeo.org/incubator/process/codereview.html Provenance Review].
#* [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance review] completed, no issues.
# The project maintains a list of all copyright holders identified in the Provenance Review Document.
#* (how to respond?)
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.
#* The [http://zoo-project.org/docs/community/developer.html code contribution guidelines] have been documented and agreed to by all developers.

== Processes ==

# The project has code under configuration management. Eg, subversion, git.
#* Yes (Could we get a public url to source control?)
# The project uses an issue tracker and keeps the status of the issue tracker up to date.
#* Yes, at http://zoo-project.org/trac
# The project has documented its management processes. This is typically done within a Developers Guide or Project Management Plan.
#* Yes, at http://zoo-project.org/docs/community/developer.html
# The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. This typically means a Project Management Committee has been established with a process for adding new members. A robust Project Management Committee will typically draw upon developers, users and key stakeholders from multiple organisations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.
#* Yes, there is a functioning PSC (add link to PSC guidelines).
# The project uses public communication channels for decision making to maintain transparency. E.g. archived email list(s), archived IRC channel(s), public issue tracker.
#* Yes, IRC, zoo-discuss, and Trac.

== Documentation ==

# The project has user documentation:
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.
# The project has developer documentation:
#* Including checkout and build instructions.
#* Including commented code, ideally published for developer use. Examples: javadocs for Java applications, or Sphinx documentation for Python applications.
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.

==Release Procedure==

In order to maintain a consistent level of quality, the project should follow defined release and testing processes.

# The project follows a defined release process:
#* Which includes execution of the testing process before releasing a stable release.
# The project follows a documented testing process. Ideally, this includes both automated and manual testing Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests.
# Release and testing processes provide sufficient detail for an experienced programmer to follow.

= OSGeo Committees and Community =

The OSGeo Foundation is made up of a number of committees, projects and local chapters. This section gathers up information these groups have requested from OSGeo projects. These expectations are not mandatory requirements before graduation, but a project should be prepared to address them in order to be considered a good OSGeo citizen.

== Board ==

The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:

# A project provide a Project Officer as a contract point:
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]
#* This person is established when the incubation committee recommends the project for graduation
#* Your community can change the project officer as needed (just add an agenda item to the next board meeting so they can recognise the change of officer).

== Marketing ==

Access to OSGeo's [[Marketing_Committee]] and associated [[Marketing_Pipeline]] is one of the key benefits of joining the OSGeo foundation. The Marketing Committee requests:

# Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's [http://wiki.osgeo.org/wiki/Marketing_Artefacts Marketing Artefacts]. This lists the documentation requirements for [http://live.osgeo.org OSGeo-Live]. Marketing Artefacts include:
#* Application Overview
#* Application Quick Start
#* Logo
#* Graphical Image
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. In most cases, this will at least include [http://live.osgeo.org OSGeo-Live], but may also include [http://wiki.debian.org/DebianGis DebianGIS], [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS], and/or [http://trac.osgeo.org/osgeo4w/ osgeo4w] [http://www.maptools.org/ms4w/ ms4w], etc.)

== Projects ==

Projects do not exist in isolation; and are expected to communicate and collaborate on key issues.

As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.

== SAC ==

The [[SAC|System Administration Committee]] is available to help infrastructure and facilities. Information for this committee is collected as part of the [[Project Status Template]]. The following should be set up:
* A http://projectname.osgeo.org domain name.

A project may optionally request SAC help to make use of:
* OSGeo issue tracker
* OSGeo mailing list
* OSGeo svn
* http://downloads.osgeo.org

[[Category: Incubation]]

ZOO-Project Incubation Checklist

2014-09-14T00:20:26Z

Warmerdam: /* Copyright and License */ preliminary writeup

= Incubation Checklist =

== Open ==

The project has demonstrated that it has an open, active and healthy user and developer community:
# Open: projects are expected to function in an open and public manner and include:
#* Open source license(s),
#** The ZOO-Project is primarily under the BSD [http://www.zoo-project.org/trac/browser/trunk/zoo-project/LICENSE LICENSE] and the [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance Review] has confirmed there are no known problems.
#* Open communication channels,
#** The [http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss zoo-discuss] list is public and active. IRC and other [http://zoo-project.org/site/ZooWebSite/ZooProject/Contact Contact] points also available.
#* Open decision making process,
#** (Gerald is looking into making zoo-psc list public). PSC meeting agenda and results available (for instance [http://zoo-project.org/trac/wiki/PSC/meetings/PSCMeet19?version=8 PSC Meeting 19]).
# Active and healthy community:
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. 
#** Suggested Text?
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. 
#** contributions come from GeoLabs SARL, Fundazione Edmund Mach, 3LIZ SARL, Cartogenic SARL and further more.

== Copyright and License ==

We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:
# All project source code is available under an Open Source license.
#* Yes, as seen in [http://www.zoo-project.org/trac/browser/trunk/zoo-project/LICENSE LICENSE].
# Project documentation is available under an open license, such as Creative Commons.
#* (to confirm)
# The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included, as per a [http://www.osgeo.org/incubator/process/codereview.html Provenance Review].
#* [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance review] completed, no issues.
# The project maintains a list of all copyright holders identified in the Provenance Review Document.
#* (how to respond?)
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.
#* The [http://zoo-project.org/docs/community/developer.html code contribution guidelines] have been documented and agreed to by all developers.

== Processes ==

# The project has code under configuration management. Eg, subversion, git.
# The project uses an issue tracker and keeps the status of the issue tracker up to date.
# The project has documented its management processes. This is typically done within a Developers Guide or Project Management Plan.
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. This typically means a Project Management Committee has been established with a process for adding new members. A robust Project Management Committee will typically draw upon developers, users and key stakeholders from multiple organisations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.
#* The project uses public communication channels for decision making to maintain transparency. E.g. archived email list(s), archived IRC channel(s), public issue tracker.

== Documentation ==

# The project has user documentation:
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.
# The project has developer documentation:
#* Including checkout and build instructions.
#* Including commented code, ideally published for developer use. Examples: javadocs for Java applications, or Sphinx documentation for Python applications.
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.

==Release Procedure==

In order to maintain a consistent level of quality, the project should follow defined release and testing processes.

# The project follows a defined release process:
#* Which includes execution of the testing process before releasing a stable release.
# The project follows a documented testing process. Ideally, this includes both automated and manual testing Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests.
# Release and testing processes provide sufficient detail for an experienced programmer to follow.

= OSGeo Committees and Community =

The OSGeo Foundation is made up of a number of committees, projects and local chapters. This section gathers up information these groups have requested from OSGeo projects. These expectations are not mandatory requirements before graduation, but a project should be prepared to address them in order to be considered a good OSGeo citizen.

== Board ==

The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:

# A project provide a Project Officer as a contract point:
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]
#* This person is established when the incubation committee recommends the project for graduation
#* Your community can change the project officer as needed (just add an agenda item to the next board meeting so they can recognise the change of officer).

== Marketing ==

Access to OSGeo's [[Marketing_Committee]] and associated [[Marketing_Pipeline]] is one of the key benefits of joining the OSGeo foundation. The Marketing Committee requests:

# Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's [http://wiki.osgeo.org/wiki/Marketing_Artefacts Marketing Artefacts]. This lists the documentation requirements for [http://live.osgeo.org OSGeo-Live]. Marketing Artefacts include:
#* Application Overview
#* Application Quick Start
#* Logo
#* Graphical Image
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. In most cases, this will at least include [http://live.osgeo.org OSGeo-Live], but may also include [http://wiki.debian.org/DebianGis DebianGIS], [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS], and/or [http://trac.osgeo.org/osgeo4w/ osgeo4w] [http://www.maptools.org/ms4w/ ms4w], etc.)

== Projects ==

Projects do not exist in isolation; and are expected to communicate and collaborate on key issues.

As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.

== SAC ==

The [[SAC|System Administration Committee]] is available to help infrastructure and facilities. Information for this committee is collected as part of the [[Project Status Template]]. The following should be set up:
* A http://projectname.osgeo.org domain name.

A project may optionally request SAC help to make use of:
* OSGeo issue tracker
* OSGeo mailing list
* OSGeo svn
* http://downloads.osgeo.org

[[Category: Incubation]]

ZOO-Project Incubation Checklist

2014-09-14T00:16:44Z

Warmerdam: /* Open */ flesh out a few points.

= Incubation Checklist =

== Open ==

The project has demonstrated that it has an open, active and healthy user and developer community:
# Open: projects are expected to function in an open and public manner and include:
#* Open source license(s),
#** The ZOO-Project is primarily under the BSD [http://www.zoo-project.org/trac/browser/trunk/zoo-project/LICENSE LICENSE] and the [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance Review] has confirmed there are no known problems.
#* Open communication channels,
#** The [http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss zoo-discuss] list is public and active. IRC and other [http://zoo-project.org/site/ZooWebSite/ZooProject/Contact Contact] points also available.
#* Open decision making process,
#** (Gerald is looking into making zoo-psc list public). PSC meeting agenda and results available (for instance [http://zoo-project.org/trac/wiki/PSC/meetings/PSCMeet19?version=8 PSC Meeting 19]).
# Active and healthy community:
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. 
#** Suggested Text?
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. 
#** contributions come from GeoLabs SARL, Fundazione Edmund Mach, 3LIZ SARL, Cartogenic SARL and further more.

== Copyright and License ==

We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:
# All project source code is available under an Open Source license.
# Project documentation is available under an open license, such as Creative Commons.
# The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included, as per a [http://www.osgeo.org/incubator/process/codereview.html Provenance Review].
# The project maintains a list of all copyright holders identified in the Provenance Review Document.
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.

== Processes ==

# The project has code under configuration management. Eg, subversion, git.
# The project uses an issue tracker and keeps the status of the issue tracker up to date.
# The project has documented its management processes. This is typically done within a Developers Guide or Project Management Plan.
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. This typically means a Project Management Committee has been established with a process for adding new members. A robust Project Management Committee will typically draw upon developers, users and key stakeholders from multiple organisations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.
#* The project uses public communication channels for decision making to maintain transparency. E.g. archived email list(s), archived IRC channel(s), public issue tracker.

== Documentation ==

# The project has user documentation:
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.
# The project has developer documentation:
#* Including checkout and build instructions.
#* Including commented code, ideally published for developer use. Examples: javadocs for Java applications, or Sphinx documentation for Python applications.
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.

==Release Procedure==

In order to maintain a consistent level of quality, the project should follow defined release and testing processes.

# The project follows a defined release process:
#* Which includes execution of the testing process before releasing a stable release.
# The project follows a documented testing process. Ideally, this includes both automated and manual testing Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests.
# Release and testing processes provide sufficient detail for an experienced programmer to follow.

= OSGeo Committees and Community =

The OSGeo Foundation is made up of a number of committees, projects and local chapters. This section gathers up information these groups have requested from OSGeo projects. These expectations are not mandatory requirements before graduation, but a project should be prepared to address them in order to be considered a good OSGeo citizen.

== Board ==

The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:

# A project provide a Project Officer as a contract point:
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]
#* This person is established when the incubation committee recommends the project for graduation
#* Your community can change the project officer as needed (just add an agenda item to the next board meeting so they can recognise the change of officer).

== Marketing ==

Access to OSGeo's [[Marketing_Committee]] and associated [[Marketing_Pipeline]] is one of the key benefits of joining the OSGeo foundation. The Marketing Committee requests:

# Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's [http://wiki.osgeo.org/wiki/Marketing_Artefacts Marketing Artefacts]. This lists the documentation requirements for [http://live.osgeo.org OSGeo-Live]. Marketing Artefacts include:
#* Application Overview
#* Application Quick Start
#* Logo
#* Graphical Image
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. In most cases, this will at least include [http://live.osgeo.org OSGeo-Live], but may also include [http://wiki.debian.org/DebianGis DebianGIS], [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS], and/or [http://trac.osgeo.org/osgeo4w/ osgeo4w] [http://www.maptools.org/ms4w/ ms4w], etc.)

== Projects ==

Projects do not exist in isolation; and are expected to communicate and collaborate on key issues.

As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.

== SAC ==

The [[SAC|System Administration Committee]] is available to help infrastructure and facilities. Information for this committee is collected as part of the [[Project Status Template]]. The following should be set up:
* A http://projectname.osgeo.org domain name.

A project may optionally request SAC help to make use of:
* OSGeo issue tracker
* OSGeo mailing list
* OSGeo svn
* http://downloads.osgeo.org

[[Category: Incubation]]

ZOO-Project Incubation Checklist

2014-09-14T00:06:31Z

Warmerdam: Preliminary

= Incubation Checklist =

== Open ==

The project has demonstrated that it has an open, active and healthy user and developer community:
# Open: projects are expected to function in an open and public manner and include:
#* Open source license(s),
#** The ZOO-Project is primarily under the BSD [http://www.zoo-project.org/trac/browser/trunk/zoo-project/LICENSE LICENSE] and the [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance Review] has confirmed there are no known problems.
#* Open communication channels,
#* Open decision making process,
# Active and healthy community:
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. Eg. collaboration on project activities such as testing, release and feature development.
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. Eg. The project is resilient enough to sustain loss of a developer or supporting organisation, often referred to as having a high [http://en.wikipedia.org/wiki/Bus_factor bus factor]. Decisions are made openly instead of behind closed doors, which empowers all developers to take ownership of the project and facilitates spreading of knowledge between current and future team members.

== Copyright and License ==

We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:
# All project source code is available under an Open Source license.
# Project documentation is available under an open license, such as Creative Commons.
# The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included, as per a [http://www.osgeo.org/incubator/process/codereview.html Provenance Review].
# The project maintains a list of all copyright holders identified in the Provenance Review Document.
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.

== Processes ==

# The project has code under configuration management. Eg, subversion, git.
# The project uses an issue tracker and keeps the status of the issue tracker up to date.
# The project has documented its management processes. This is typically done within a Developers Guide or Project Management Plan.
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. This typically means a Project Management Committee has been established with a process for adding new members. A robust Project Management Committee will typically draw upon developers, users and key stakeholders from multiple organisations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.
#* The project uses public communication channels for decision making to maintain transparency. E.g. archived email list(s), archived IRC channel(s), public issue tracker.

== Documentation ==

# The project has user documentation:
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.
# The project has developer documentation:
#* Including checkout and build instructions.
#* Including commented code, ideally published for developer use. Examples: javadocs for Java applications, or Sphinx documentation for Python applications.
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.

==Release Procedure==

In order to maintain a consistent level of quality, the project should follow defined release and testing processes.

# The project follows a defined release process:
#* Which includes execution of the testing process before releasing a stable release.
# The project follows a documented testing process. Ideally, this includes both automated and manual testing Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests.
# Release and testing processes provide sufficient detail for an experienced programmer to follow.

= OSGeo Committees and Community =

The OSGeo Foundation is made up of a number of committees, projects and local chapters. This section gathers up information these groups have requested from OSGeo projects. These expectations are not mandatory requirements before graduation, but a project should be prepared to address them in order to be considered a good OSGeo citizen.

== Board ==

The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:

# A project provide a Project Officer as a contract point:
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]
#* This person is established when the incubation committee recommends the project for graduation
#* Your community can change the project officer as needed (just add an agenda item to the next board meeting so they can recognise the change of officer).

== Marketing ==

Access to OSGeo's [[Marketing_Committee]] and associated [[Marketing_Pipeline]] is one of the key benefits of joining the OSGeo foundation. The Marketing Committee requests:

# Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's [http://wiki.osgeo.org/wiki/Marketing_Artefacts Marketing Artefacts]. This lists the documentation requirements for [http://live.osgeo.org OSGeo-Live]. Marketing Artefacts include:
#* Application Overview
#* Application Quick Start
#* Logo
#* Graphical Image
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. In most cases, this will at least include [http://live.osgeo.org OSGeo-Live], but may also include [http://wiki.debian.org/DebianGis DebianGIS], [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS], and/or [http://trac.osgeo.org/osgeo4w/ osgeo4w] [http://www.maptools.org/ms4w/ ms4w], etc.)

== Projects ==

Projects do not exist in isolation; and are expected to communicate and collaborate on key issues.

As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.

== SAC ==

The [[SAC|System Administration Committee]] is available to help infrastructure and facilities. Information for this committee is collected as part of the [[Project Status Template]]. The following should be set up:
* A http://projectname.osgeo.org domain name.

A project may optionally request SAC help to make use of:
* OSGeo issue tracker
* OSGeo mailing list
* OSGeo svn
* http://downloads.osgeo.org

[[Category: Incubation]]

Incubation Committee

2014-09-13T23:58:51Z

Warmerdam:

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.

== Documents ==

* Official incubator public web page is at: http://osgeo.org/incubator/index.html (with members list).
* [[Incubation FAQ]]
* [[Official_IncCom_Documents]]
* Incubation process docs: http://osgeo.org/incubator/process/index.html (original [[Official_IncCom_Documents|wiki draft documents]])
* [[Incubation Badges]]

Draft or Example Documents
* Draft [[Commiter Responsibilities Guidelines]]
* 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.
** Geotools Copyright Assignment ([http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.pdf pdf], [http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.odt odt]) - previous example
** [[Project Copyright Assignment]] - previous example
* [[Contributor Agreement]] and FAQ
* [[Incubation Phases]] proposal

Document Refresh 2014
* [[Project Graduation Checklist]]

Projects:
* [[OSGeo Labs]] - for OSGeo related projects that haven't reached incubation status
* List of [[Project Steering Committees]]

Reference:
* [[Project Infrastructure Migration]]
* [http://producingoss.com/html-chunk/index.html Producing OSS] - by Karl Fogel - an excellent primer on running an FOSS project.

Reports:
* [[Incubation Committee Report 2012]]
* [[Incubation Committee Report 2011]]

Trac:
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&order=priority Open Incubator Trac Issues]
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&keywords=%7Eapplication&order=priority Pending Incubation Applications]

== Meetings and Reports ==
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]].
* [[IncCom Meeting1|First Meeting]] - March 13th 2006
* [[IncCom Meeting2|Second Meeting]] - March 20th 2006
* [[IncCom Meeting3|Third Meeting]] - March 27th 2006
* [[IncCom Meeting4|Fourth Meeting]] - April 10th 2006
* [[IncCom Meeting5|Fifth Meeting]] - April 24th 2006
* [[IncCom Meeting6|Sixth Meeting]] - June 19th 2006
* [[IncCom Meeting7|Seventh Meeting]] - August 7th 2006
* [[IncCom Meeting8|Eighth Meeting]] - October 30th 2006
* [[IncCom Meeting9|Nineth Meeting]] - February 12th 2007
* [[IncCom Meeting10|Tenth Meeting]] - June 11th 2007
* [[IncCom Meeting11|Eleventh Meeting]] - October 29th 2007
* [[IncCom Meeting12|Twelfth Meeting]] - September 8th 2008
* [[IncCom Meeting13|Thirteenth Meeting]] - October 29th 2009
* [[IncCom Meeting14|Fourteenth Meeting]] - March 1th 2010
* [[IncCom Meeting15]] - Nov 21 2011
* [[IncCom Meeting16]] - Jan 17 2012
* [[IncCom Meeting17]] - March 19 2012
* [[IncCom Meeting18]] - May 21 2012
* [[IncCom Meeting19]] - July 23 2012
* [[IncCom Meeting20]] - Sep 24 2012
* [[IncCom Meeting21]] - Feb 18 2013
* [[IncCom Report22]] - 2013 Q2
* [[IncCom Report23]] - 2013 Q3
* [[IncCom Report24]] - 2014 Q1

== Progress in the incubator ==

The OSGeo incubation process takes place in three stages:

# Initial Application
# Incubation
## Project Status: project details, and a few resourcing questions for the system admin committee (see [[Project Status Template]]).
## Provenance Review: quick check to ensure the project is open source and has permission to distribute its source code.
## Final Checklist: review the project procedures and gather requested information for OSGeo participation
# Graduation

The following projects are currently in OSGeo incubation:

* gvSIG: http://www.osgeo.org/gvsig
*# [[gvSIG Incubation Status]]
*# [[gvSIG Provenance Review]]
*# [[gvSIG Incubation Checklist]]

* MetaCRS: http://trac.osgeo.org/metacrs/
*# [[MetaCRS Incubation Status]]
*# no provenance review provided
*# no check list provided

* Opticks: http://opticks.org
*# [[Opticks Incubation Status]]
*# no provenance review provided
*# [[Opticks Incubation Checklist]]

* rasdaman: http://www.rasdaman.org
*# [[ rasdaman Incubation Status ]]
*# http://rasdaman.org/wiki/OSGeoCodeProvenance
*# http://www.rasdaman.org/wiki/OSGeoIncubationChecklist

* Zoo-Project: http://www.zoo-project.org
*# [[ZOO-Project_Incubation_Status]]
*# [http://zoo-project.org/trac/wiki/Provenance%20Review Provenance Review]
*# [[ZOO-Project Incubation Checklist]]

* pycsw: http://pycsw.org
*# status template not filled out
*# no provenance review provided
*# no check list provided

* TEAM Engine: http://teamengine.sourceforge.net
*# status template not filled out
*# no provenance review provided
*# no check list provided

*OTB
*# [[OTB Incubation Application]]
*#[[OTB Project Incubation Status]]

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
will take you to a project specific wiki or website in order to be closer to their target community.

When projects have completed the incubation checklist their mentor will recommend them to the Incubation committee for graduation.

== Graduated ==

The following status and provenance documents are for historical purposes, and are no longer actively maintained.

* Community Mapbuilder: [[Community Mapbuilder Incubation Progress]] | [[Community Mapbuilder Provenance Review]]
* deegree: [[deegree Incubation Status]] | [[deegree Provenance Review]]
* FDO: [[FDO Incubation Status]] | [[FDO Provenance Review]]
* GEOS: [[GEOS Incubation Status]] | [[GEOS Provenance Review]]
* GDAL/OGR: [[GDAL Incubation Progress]] | [[GDAL Provenance Review]]
* Geomajas: [[GeoMajas Incubation Status]] | [[GeoMajas Provenance Review]]
* GeoNetwork: [[GeoNetwork Incubation Status]] | [[GeoNetwork Provenance Review]]
* GeoMoose: [[GeoMoose Incubation Status]] | [[GeoMoose Provenance Review]] | [[GeoMoose Incubation Checklist]]
* GeoTools: [[GeoTools Incubation Progress]] | [[GeoTools Provenance Review]]
* 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]]
* GRASS: [[GRASS Incubation Progress]] | [[GRASS Provenance Review]]
* Mapbender: [[Mapbender Incubation Progress]] | [[Mapbender Provenance Review]]
* MapFish: [[MapFish Incubation Status]] | [[MapFish Provenance Review]] (Graduated: August 2011)
* MapGuide: [[MapGuide Incubation Status]] | [[MapGuide Provenance Review]]
* MapServer: [[MapServer incubation status]] | [[MapServer Provenance Review]]
* Marble: [[Marble Incubation Status]] | [[Marble Code Provenance Review]] | [[Marble Graduation Checklist]] (Graduated 17 October 2013)
* OpenLayers: [[OpenLayers Incubation Status]] | [[OpenLayers Provenance Review]]
* PostGIS: [[PostGIS Incubation Status]] | [[PostGIS Provenance Review]]
* OSSIM: [[OSSIM incubation status]] | [http://trac.osgeo.org/ossim/wiki/ossimprovenance OSSIM Provenance Review]
* QGIS: [[QGIS Incubation Status]] | [[QGIS Provenance Review]]

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.

[[Category:Incubation]]
[[Category:Committees]]

OSGeo Budget 2014

2014-03-06T20:32:49Z

Warmerdam: /* Expenses */ fix addition

''****DRAFT in progress****''

== Income ==
{|border=1
| '''Source'''
| '''Qty'''
| '''Unit $'''
| '''2014 Amount'''
| '''Notes'''
|-
| '''''Foundation Sponsorships'''''
|-
| Sustaining Sponsorships (50K)
|align=right|0
|align=right|50,000
|align=right|0
|
|-
| Principal Sponsorships (20K)
|align=right|0
|align=right|20,000
|align=right|0
|
|-
| Supporting Sponsorships (10K)
|align=right|1
|align=right|10,000
|align=right|10,000
| Not paid yet
|-
| Associate Sponsorships (3K)
|align=right|9
|align=right|3,000
|align=right|27,000
| lost 2 in 2012, gained 2 in 2013
|-
| '''''FOSS4G Conferences'''''
|-
| FOSS4G Nottingham
|
|
|align=right|50,000
|
|-
| FOSS4G NA (50% of profits)
|
|
|align=right|9,000
| local committee estimates 500 attendees and 18k profit
|-
| '''''GSoC'''''
|-
| GSoC (mentorships)
|align=right|20
|align=right|500
|align=right|10,000
|
|-
| GSoC mentor summit reimbursement
|
|
|align=right|2,000
|
|-
| '''Total'''
|
|
|align=right|'''108,000'''
|
|}

== Expenses ==

{|border=1
| '''Source'''
| '''Qty'''
| '''Unit $'''
| '''2014 Amount'''
| '''Notes'''
|-
| '''''Administration'''''
|-
| Bank fees (base pkg, wire fees, paypal feels, etc.)
|align=right|12
|align=right|75
|align=right|900
|
|-
| Quickbooks (yearly fee, renews in Oct)
|
|
|align=right|301.54
|
|-
| EarthClassMail (monthly pkg + charges)
|align=right|12
|align=right|40
|align=right|480
|
|-
| Office supplies
|
|
|align=right|100
|
|-
| Accounting/tax filing support
|
|
|align=right|5,000
|
|-
| 501c3 support
|
|
|align=right|2,000
|
|-
| Other professional services (as needed)
|
|
|align=right|5,000
|
|-
| Directors and Officers insurance
|
|
|align=right|1,500
|
|-
|
|
|
|align=right|'''10,281.54'''
|-
| '''''SAC'''''
|-
| Peer1 Servers (ending June 2014?)
|align=right|6
|align=right|559
|align=right|3,354
| TODO:Retire osgeo1 in 2014?
|-
| OSUOSL hosting
|
|
|align=right|3,500
|
|-
| More hardware at OSUOSL
|
|
|align=right|5,000
|
|-
| Domain registrations
|
|
|align=right|200
|
|-
| SSL Cert ($1499 in 2011, every 5 years)
|
|
|align=right|0
|
|-
|
|
|
|align=right|'''12054.00'''
|-
| '''''Outreach committee'''''
|-
| General events support (starter kits, LiveDVD/USB matching funds)
|
|
|align=right|10,000
|
|-
|
|
|
|align=right|'''10,000.00'''
|-
| '''''Travel expenses'''''
|-
| GSoC Mentor Summit expenses reimbursement
|
|
|align=right|2,500
|
|-
| ICA/OSGeo Labs Student Travel
|
|
|align=right|5,000
|(detailed procedures to be decided)
|-
| Yearly Board F2F
|
|
|align=right|0
|
|-
| Strategic travel (case by case)
|
|
|align=right|7,500
| For example, to send an OSGeo Advocate (such as a board member) to negotiate on behalf of OSGeo at the founding of the LocationTech foundation. (This typically doesn't extend to sponsorship of OSGeo speakers at conferences).
|-
|
|
|
|align=right|'''15,000.00'''
|-
| '''''Events'''''
|-
| Code Sprint Support
|
|
|align=right|15,000
| (approximately $10K already committed to Vienna sprint)
|-
| FOSS4G Seed Money
|
|
|
| FOSS4G seed money (inc regional events). Requires ~ $50K capital per global event of 800 attendees. Less for smaller. Seed money should be returned with a modest profit.
|-
| Other Sponsorship Opportunities
|
|
|align=right|5,000
| a small amount for other events
|-
|
|
|
|align=right|'''20,000.00'''
|-
| '''Total'''
|
|
|align=right|'''67,335.54'''
|
|-
| .
|-
| '''Surplus/Loss'''
|
|
|align=right|'''40,664.46'''
|
|}

== Notes ==

* All amounts are in US dollars.

[[Category:Budget]]
[[Category:Finance]]

OSGeo Budget 2014

2014-03-06T20:30:11Z

Warmerdam: /* Expenses */ add 5k for edu travel.

''****DRAFT in progress****''

== Income ==
{|border=1
| '''Source'''
| '''Qty'''
| '''Unit $'''
| '''2014 Amount'''
| '''Notes'''
|-
| '''''Foundation Sponsorships'''''
|-
| Sustaining Sponsorships (50K)
|align=right|0
|align=right|50,000
|align=right|0
|
|-
| Principal Sponsorships (20K)
|align=right|0
|align=right|20,000
|align=right|0
|
|-
| Supporting Sponsorships (10K)
|align=right|1
|align=right|10,000
|align=right|10,000
| Not paid yet
|-
| Associate Sponsorships (3K)
|align=right|9
|align=right|3,000
|align=right|27,000
| lost 2 in 2012, gained 2 in 2013
|-
| '''''FOSS4G Conferences'''''
|-
| FOSS4G Nottingham
|
|
|align=right|50,000
|
|-
| FOSS4G NA (50% of profits)
|
|
|align=right|9,000
| local committee estimates 500 attendees and 18k profit
|-
| '''''GSoC'''''
|-
| GSoC (mentorships)
|align=right|20
|align=right|500
|align=right|10,000
|
|-
| GSoC mentor summit reimbursement
|
|
|align=right|2,000
|
|-
| '''Total'''
|
|
|align=right|'''108,000'''
|
|}

== Expenses ==

{|border=1
| '''Source'''
| '''Qty'''
| '''Unit $'''
| '''2014 Amount'''
| '''Notes'''
|-
| '''''Administration'''''
|-
| Bank fees (base pkg, wire fees, paypal feels, etc.)
|align=right|12
|align=right|75
|align=right|900
|
|-
| Quickbooks (yearly fee, renews in Oct)
|
|
|align=right|301.54
|
|-
| EarthClassMail (monthly pkg + charges)
|align=right|12
|align=right|40
|align=right|480
|
|-
| Office supplies
|
|
|align=right|100
|
|-
| Accounting/tax filing support
|
|
|align=right|5,000
|
|-
| 501c3 support
|
|
|align=right|2,000
|
|-
| Other professional services (as needed)
|
|
|align=right|5,000
|
|-
| Directors and Officers insurance
|
|
|align=right|1,500
|
|-
|
|
|
|align=right|'''10,281.54'''
|-
| '''''SAC'''''
|-
| Peer1 Servers (ending June 2014?)
|align=right|6
|align=right|559
|align=right|3,354
| TODO:Retire osgeo1 in 2014?
|-
| OSUOSL hosting
|
|
|align=right|3,500
|
|-
| More hardware at OSUOSL
|
|
|align=right|5,000
|
|-
| Domain registrations
|
|
|align=right|200
|
|-
| SSL Cert ($1499 in 2011, every 5 years)
|
|
|align=right|0
|
|-
|
|
|
|align=right|'''7,554.00'''
|-
| '''''Outreach committee'''''
|-
| General events support (starter kits, LiveDVD/USB matching funds)
|
|
|align=right|10,000
|
|-
|
|
|
|align=right|'''10,000.00'''
|-
| '''''Travel expenses'''''
|-
| GSoC Mentor Summit expenses reimbursement
|
|
|align=right|2,500
|
|-
| ICA/OSGeo Labs Student Travel
|
|
|align=right|5,000
|(detailed procedures to be decided)
|-
| Yearly Board F2F
|
|
|align=right|0
|
|-
| Strategic travel (case by case)
|
|
|align=right|7,500
| For example, to send an OSGeo Advocate (such as a board member) to negotiate on behalf of OSGeo at the founding of the LocationTech foundation. (This typically doesn't extend to sponsorship of OSGeo speakers at conferences).
|-
|
|
|
|align=right|'''15,000.00'''
|-
| '''''Events'''''
|-
| Code Sprint Support
|
|
|align=right|15,000
| (approximately $10K already committed to Vienna sprint)
|-
| FOSS4G Seed Money
|
|
|
| FOSS4G seed money (inc regional events). Requires ~ $50K capital per global event of 800 attendees. Less for smaller. Seed money should be returned with a modest profit.
|-
| Other Sponsorship Opportunities
|
|
|align=right|5,000
| a small amount for other events
|-
|
|
|
|align=right|'''20,000.00'''
|-
| '''Total'''
|
|
|align=right|'''62,835.54'''
|
|-
| .
|-
| '''Surplus/Loss'''
|
|
|align=right|'''45,164.46'''
|
|}

== Notes ==

* All amounts are in US dollars.

[[Category:Budget]]
[[Category:Finance]]

OSGeo Budget 2014

2014-03-06T19:48:23Z

Warmerdam: /* Expenses */

''****DRAFT in progress****''

== Income ==
{|border=1
| '''Source'''
| '''Qty'''
| '''Unit $'''
| '''2014 Amount'''
| '''Notes'''
|-
| '''''Foundation Sponsorships'''''
|-
| Sustaining Sponsorships (50K)
|align=right|0
|align=right|50,000
|align=right|0
|
|-
| Principal Sponsorships (20K)
|align=right|0
|align=right|20,000
|align=right|0
|
|-
| Supporting Sponsorships (10K)
|align=right|1
|align=right|10,000
|align=right|10,000
| Not paid yet
|-
| Associate Sponsorships (3K)
|align=right|9
|align=right|3,000
|align=right|27,000
| lost 2 in 2012, gained 2 in 2013
|-
| '''''FOSS4G Conferences'''''
|-
| FOSS4G Nottingham
|
|
|align=right|50,000
|
|-
| FOSS4G NA (50% of profits)
|
|
|align=right|9,000
| local committee estimates 500 attendees and 18k profit
|-
| '''''GSoC'''''
|-
| GSoC (mentorships)
|align=right|20
|align=right|500
|align=right|10,000
|
|-
| GSoC mentor summit reimbursement
|
|
|align=right|2,000
|
|-
| '''Total'''
|
|
|align=right|'''108,000'''
|
|}

== Expenses ==

{|border=1
| '''Source'''
| '''Qty'''
| '''Unit $'''
| '''2014 Amount'''
| '''Notes'''
|-
| '''''Administration'''''
|-
| Bank fees (base pkg, wire fees, paypal feels, etc.)
|align=right|12
|align=right|75
|align=right|900
|
|-
| Quickbooks (yearly fee, renews in Oct)
|
|
|align=right|301.54
|
|-
| EarthClassMail (monthly pkg + charges)
|align=right|12
|align=right|40
|align=right|480
|
|-
| Office supplies
|
|
|align=right|100
|
|-
| Accounting/tax filing support
|
|
|align=right|5,000
|
|-
| 501c3 support
|
|
|align=right|2,000
|
|-
| Other professional services (as needed)
|
|
|align=right|5,000
|
|-
| Directors and Officers insurance
|
|
|align=right|1,500
|
|-
|
|
|
|align=right|'''10,281.54'''
|-
| '''''SAC'''''
|-
| Peer1 Servers (ending June 2014?)
|align=right|6
|align=right|559
|align=right|3,354
| TODO:Retire osgeo1 in 2014?
|-
| OSUOSL hosting
|
|
|align=right|3,500
|
|-
| More hardware at OSUOSL
|
|
|align=right|5,000
|
|-
| Domain registrations
|
|
|align=right|200
|
|-
| SSL Cert ($1499 in 2011, every 5 years)
|
|
|align=right|0
|
|-
|
|
|
|align=right|'''7,554.00'''
|-
| '''''Outreach committee'''''
|-
| General events support (starter kits, LiveDVD/USB matching funds)
|
|
|align=right|10,000
|
|-
|
|
|
|align=right|'''10,000.00'''
|-
| '''''Travel expenses'''''
|-
| GSoC Mentor Summit expenses reimbursement
|
|
|align=right|2,500
|
|-
| Yearly Board F2F
|
|
|align=right|0
|
|-
| Strategic travel (case by case)
|
|
|align=right|7,500
| For example, to send an OSGeo Advocate (such as a board member) to negotiate on behalf of OSGeo at the founding of the LocationTech foundation. (This typically doesn't extend to sponsorship of OSGeo speakers at conferences).
|-
|
|
|
|align=right|'''10,000.00'''
|-
| '''''Events'''''
|-
| Code Sprint Support
|
|
|align=right|15,000
| (approximately $10K already committed to Vienna sprint)
|-
| FOSS4G Seed Money
|
|
|
| FOSS4G seed money (inc regional events). Requires ~ $50K capital per global event of 800 attendees. Less for smaller. Seed money should be returned with a modest profit.
|-
| Other Sponsorship Opportunities
|
|
|align=right|5,000
| a small amount for other events
|-
|
|
|
|align=right|'''20,000.00'''
|-
| '''Total'''
|
|
|align=right|'''57,835.54'''
|
|-
| .
|-
| '''Surplus/Loss'''
|
|
|align=right|'''50,164.46'''
|
|}

== Notes ==

* All amounts are in US dollars.

[[Category:Budget]]
[[Category:Finance]]

OSGeo Budget 2014

2014-03-06T19:47:34Z

Warmerdam: /* Expenses */

''****DRAFT in progress****''

== Income ==
{|border=1
| '''Source'''
| '''Qty'''
| '''Unit $'''
| '''2014 Amount'''
| '''Notes'''
|-
| '''''Foundation Sponsorships'''''
|-
| Sustaining Sponsorships (50K)
|align=right|0
|align=right|50,000
|align=right|0
|
|-
| Principal Sponsorships (20K)
|align=right|0
|align=right|20,000
|align=right|0
|
|-
| Supporting Sponsorships (10K)
|align=right|1
|align=right|10,000
|align=right|10,000
| Not paid yet
|-
| Associate Sponsorships (3K)
|align=right|9
|align=right|3,000
|align=right|27,000
| lost 2 in 2012, gained 2 in 2013
|-
| '''''FOSS4G Conferences'''''
|-
| FOSS4G Nottingham
|
|
|align=right|50,000
|
|-
| FOSS4G NA (50% of profits)
|
|
|align=right|9,000
| local committee estimates 500 attendees and 18k profit
|-
| '''''GSoC'''''
|-
| GSoC (mentorships)
|align=right|20
|align=right|500
|align=right|10,000
|
|-
| GSoC mentor summit reimbursement
|
|
|align=right|2,000
|
|-
| '''Total'''
|
|
|align=right|'''108,000'''
|
|}

== Expenses ==

{|border=1
| '''Source'''
| '''Qty'''
| '''Unit $'''
| '''2014 Amount'''
| '''Notes'''
|-
| '''''Administration'''''
|-
| Bank fees (base pkg, wire fees, paypal feels, etc.)
|align=right|12
|align=right|75
|align=right|900
|
|-
| Quickbooks (yearly fee, renews in Oct)
|
|
|align=right|301.54
|
|-
| EarthClassMail (monthly pkg + charges)
|align=right|12
|align=right|40
|align=right|480
|
|-
| Office supplies
|
|
|align=right|100
|
|-
| Accounting/tax filing support
|
|
|align=right|5,000
|
|-
| 501c3 support
|
|
|align=right|2,000
|
|-
| Other professional services (as needed)
|
|
|align=right|5,000
|
|-
| Directors and Officers insurance
|
|
|align=right|1,500
|
|-
|
|
|
|align=right|'''10,281.54'''
|-
| '''''SAC'''''
|-
| Peer1 Servers (ending June 2014?)
|align=right|6
|align=right|559
|align=right|3,354
| TODO:Retire osgeo1 in 2014?
|-
| OSUOSL hosting
|
|
|align=right|3,500
|
|-
| More hardware at OSUOSL
|
|
|align=right|5,000
|
|-
| Domain registrations
|
|
|align=right|200
|
|-
| SSL Cert ($1499 in 2011, every 5 years)
|
|
|align=right|0
|
|-
|
|
|
|align=right|'''7,554.00'''
|-
| '''''Outreach committee'''''
|-
| General events support (starter kits, LiveDVD/USB matching funds)
|
|
|align=right|10,000
|
|-
| '''''Travel expenses'''''
|-
| GSoC Mentor Summit expenses reimbursement
|
|
|align=right|2,500
|
|-
| Yearly Board F2F
|
|
|align=right|0
|
|-
| Strategic travel (case by case)
|
|
|align=right|7,500
| For example, to send an OSGeo Advocate (such as a board member) to negotiate on behalf of OSGeo at the founding of the LocationTech foundation. (This typically doesn't extend to sponsorship of OSGeo speakers at conferences).
|-
|
|
|
|align=right|'''10,000.00'''
|-
| '''''Events'''''
|-
| Code Sprint Support
|
|
|align=right|15,000
| (approximately $10K already committed to Vienna sprint)
|-
| FOSS4G Seed Money
|
|
|
| FOSS4G seed money (inc regional events). Requires ~ $50K capital per global event of 800 attendees. Less for smaller. Seed money should be returned with a modest profit.
|-
| Other Sponsorship Opportunities
|
|
|align=right|5,000
| a small amount for other events
|-
|
|
|
|align=right|'''20,000.00'''
|-
| '''Total'''
|
|
|align=right|'''47,835.54'''
|
|-
| .
|-
| '''Surplus/Loss'''
|
|
|align=right|'''60,164.46'''
|
|}

== Notes ==

* All amounts are in US dollars.

[[Category:Budget]]
[[Category:Finance]]

OSGeo Budget 2014

2014-03-06T19:47:10Z

Warmerdam: Update various numbers.

''****DRAFT in progress****''

== Income ==
{|border=1
| '''Source'''
| '''Qty'''
| '''Unit $'''
| '''2014 Amount'''
| '''Notes'''
|-
| '''''Foundation Sponsorships'''''
|-
| Sustaining Sponsorships (50K)
|align=right|0
|align=right|50,000
|align=right|0
|
|-
| Principal Sponsorships (20K)
|align=right|0
|align=right|20,000
|align=right|0
|
|-
| Supporting Sponsorships (10K)
|align=right|1
|align=right|10,000
|align=right|10,000
| Not paid yet
|-
| Associate Sponsorships (3K)
|align=right|9
|align=right|3,000
|align=right|27,000
| lost 2 in 2012, gained 2 in 2013
|-
| '''''FOSS4G Conferences'''''
|-
| FOSS4G Nottingham
|
|
|align=right|50,000
|
|-
| FOSS4G NA (50% of profits)
|
|
|align=right|9,000
| local committee estimates 500 attendees and 18k profit
|-
| '''''GSoC'''''
|-
| GSoC (mentorships)
|align=right|20
|align=right|500
|align=right|10,000
|
|-
| GSoC mentor summit reimbursement
|
|
|align=right|2,000
|
|-
| '''Total'''
|
|
|align=right|'''108,000'''
|
|}

== Expenses ==

{|border=1
| '''Source'''
| '''Qty'''
| '''Unit $'''
| '''2014 Amount'''
| '''Notes'''
|-
| '''''Administration'''''
|-
| Bank fees (base pkg, wire fees, paypal feels, etc.)
|align=right|12
|align=right|75
|align=right|900
|
|-
| Quickbooks (yearly fee, renews in Oct)
|
|
|align=right|301.54
|
|-
| EarthClassMail (monthly pkg + charges)
|align=right|12
|align=right|40
|align=right|480
|
|-
| Office supplies
|
|
|align=right|100
|
|-
| Accounting/tax filing support
|
|
|align=right|5,000
|
|-
| 501c3 support
|
|
|align=right|2,000
|
|-
| Other professional services (as needed)
|
|
|align=right|5,000
|
|-
| Directors and Officers insurance
|
|
|align=right|1,500
|
|-
|
|
|
|align=right|'''10,281.54'''
|-
| '''''SAC'''''
|-
| Peer1 Servers (ending June 2014?)
|align=right|6
|align=right|559
|align=right|3,354
| TODO:Retire osgeo1 in 2014?
|-
| OSUOSL hosting
|
|
|align=right|3,500
|
|-
| More hardware at OSUOSL
|
|
|align=right|5,000
|
|-
| Domain registrations
|
|
|align=right|200
|
|-
| SSL Cert ($1499 in 2011, every 5 years)
|
|
|align=right|0
|
|-
|
|
|
|align=right|'''7,554.00'''|-
| '''''Outreach committee'''''
|-
| General events support (starter kits, LiveDVD/USB matching funds)
|
|
|align=right|10,000
|
|-
| '''''Travel expenses'''''
|-
| GSoC Mentor Summit expenses reimbursement
|
|
|align=right|2,500
|
|-
| Yearly Board F2F
|
|
|align=right|0
|
|-
| Strategic travel (case by case)
|
|
|align=right|7,500
| For example, to send an OSGeo Advocate (such as a board member) to negotiate on behalf of OSGeo at the founding of the LocationTech foundation. (This typically doesn't extend to sponsorship of OSGeo speakers at conferences).
|-
|
|
|
|align=right|'''10,000.00'''
|-
| '''''Events'''''
|-
| Code Sprint Support
|
|
|align=right|15,000
| (approximately $10K already committed to Vienna sprint)
|-
| FOSS4G Seed Money
|
|
|
| FOSS4G seed money (inc regional events). Requires ~ $50K capital per global event of 800 attendees. Less for smaller. Seed money should be returned with a modest profit.
|-
| Other Sponsorship Opportunities
|
|
|align=right|5,000
| a small amount for other events
|-
|
|
|
|align=right|'''20,000.00'''
|-
| '''Total'''
|
|
|align=right|'''47,835.54'''
|
|-
| .
|-
| '''Surplus/Loss'''
|
|
|align=right|'''60,164.46'''
|
|}

== Notes ==

* All amounts are in US dollars.

[[Category:Budget]]
[[Category:Finance]]

OSGeo Budget 2014

2014-03-06T19:38:05Z

Warmerdam: /* Expenses */ first pass updating for 2014.

''****DRAFT in progress****''

== Income ==
{|border=1
| '''Source'''
| '''Qty'''
| '''Unit $'''
| '''2014 Amount'''
| '''Notes'''
|-
| '''''Foundation Sponsorships'''''
|-
| Sustaining Sponsorships (50K)
|align=right|0
|align=right|50,000
|align=right|0
|
|-
| Principal Sponsorships (20K)
|align=right|0
|align=right|20,000
|align=right|0
|
|-
| Supporting Sponsorships (10K)
|align=right|1
|align=right|10,000
|align=right|10,000
| Not paid yet
|-
| Associate Sponsorships (3K)
|align=right|9
|align=right|3,000
|align=right|27,000
| lost 2 in 2012, gained 2 in 2013
|-
| '''''FOSS4G Conferences'''''
|-
| FOSS4G Nottingham
|
|
|align=right|50,000
|
|-
| FOSS4G NA (50% of profits)
|
|
|align=right|9,000
| local committee estimates 500 attendees and 18k profit
|-
| '''''GSoC'''''
|-
| GSoC (mentorships)
|align=right|20
|align=right|500
|align=right|10,000
|
|-
| GSoC mentor summit reimbursement
|
|
|align=right|2,000
|
|-
| '''Total'''
|
|
|align=right|'''108,000'''
|
|}

== Expenses ==

{|border=1
| '''Source'''
| '''Qty'''
| '''Unit $'''
| '''2014 Amount'''
| '''Notes'''
|-
| '''''Administration'''''
|-
| Bank fees (base pkg, wire fees, paypal feels, etc.)
|align=right|12
|align=right|75
|align=right|900
|
|-
| Quickbooks (yearly fee, renews in Oct)
|
|
|align=right|301.54
|
|-
| EarthClassMail (monthly pkg + charges)
|align=right|12
|align=right|40
|align=right|480
|
|-
| Office supplies
|
|
|align=right|100
|
|-
| Accounting/tax filing support
|
|
|align=right|5,000
|
|-
| 501c3 support
|
|
|align=right|2,000
|
|-
| Other professional services (as needed)
|
|
|align=right|5,000
|
|-
| '''''Insurance'''''
|-
| Directors and Officers insurance
|
|
|align=right|1,500
|
|-
| General Liability
|
|
|align=right|0
|
|-
| Special Event insurance
|
|
|align=right|0
|
|-
| '''''SAC'''''
|-
| Peer1 Servers (ending June 2014?)
|align=right|6
|align=right|559
|align=right|3,354
| TODO:Retire osgeo1 in 2014?
|-
| OSUOSL hosting
|
|
|align=right|3,500
|
|-
| More hardware at OSUOSL
|
|
|align=right|5,000
|
|-
| Domain registrations
|
|
|align=right|200
|
|-
| SSL Cert ($1499 in 2011, every 5 years)
|
|
|align=right|0
|
|-
| '''''Outreach committee'''''
|-
| General events support (starter kits, LiveDVD/USB matching funds)
|
|
|align=right|10,000
|
|-
| '''''Travel expenses'''''
|-
| GSoC Mentor Summit expenses reimbursement
|
|
|align=right|2,500
|
|-
| Yearly Board F2F
|
|
|align=right|0
|
|-
| Strategic travel (case by case)
|
|
|align=right|7,500
| For example, to send an OSGeo Advocate (such as a board member) to negotiate on behalf of OSGeo at the founding of the LocationTech foundation. (This typically doesn't extend to sponsorship of OSGeo speakers at conferences).
|-
| '''''Events'''''
|-
| Code Sprint Support
|
|
|align=right|15,000
| (approximately $10K already committed to Vienna sprint)
|-
| FOSS4G Seed Money
|
|
|
| FOSS4G seed money (inc regional events). Requires ~ $50K capital per global event of 800 attendees. Less for smaller. Seed money should be returned with a modest profit.
|-
| Other Sponsorship Opportunities
|
|
|align=right|5,000
| a small amount for other events
|-
| '''Total'''
|
|
|align=right|'''?'''
|
|-
| .
|-
| '''Surplus/Loss'''
|
|
|align=right|'''?'''
|
|}

== Notes ==

* All amounts are in US dollars.

[[Category:Budget]]
[[Category:Finance]]

SAC:Mailing Lists

2014-01-30T19:36:54Z

Warmerdam: /* Renaming Lists */

Mailing lists are administered with Mailman on the virtual host lists.osgeo.org. Physically this is the "Mail" VM running on osgeo4. Frank Warmerdam (warmerdam) and Alan Boudreault (aboudreault) do most of the mailman work.

= Notes for List Administrators =

== Requesting a new list ==

If your project or activity would like to have a mailing list at lists.osgeo.org please take the following steps:

* First, confirm that there isn't already an appropriate list for this activity, and consider whether OSGeo is the right home for the proposed list.
* File a ticket at http://trac.osgeo.org/osgeo (use your OSGeo Userid to login) and make sure the component is set to "SAC". This is the request to the System Administration Committee to create the list.
* Please include the exact name you would like for the list (ie. foo-announce), and the email address of the person who should be the list admin. Also provide the justification for the list, and indicate if it was explicitly requested by an OSGeo Project PSC or project representative.
* Include any special instructions (such pointers to info if the list is actually being migrated from elsewhere).
* Hopefully, someone in SAC will act on the ticket and create the list. When complete the ticket will be updated and closed, and the proposed admin will receive an email with the admin password for the list.
* Review the list settings, in particular ensuring that the short description gets set (ie. review following points)

Generally it is up to the mailman administrator to judge whether a list is justified for creation. The justification doesn't need to be strong, but the list should be OSGeo related, reasonably likely to generate some use, or be requested on behalf of a project.

== All lists ==

* Please set "A terse phrase identifying this list." to something brief and meaningful as this is what is shown on the main lists directory. It is on the ''General'' tab.
* Set "Who can view subscription list?" on the ''Privacy'' tab to "List Admin Only", otherwise anyone can subscribe and then harvest the mailing list.
* Set ''generic_nonmember_action'' on the ''Privacy->Sender filters'' tab to reject as most lists are not actively administered so we prefer to reject rather than holding posts from unsubscribed folks.
* Ensure the "Prefix for subject line of list postings." on the ''General'' tab is set to something meaningful. If the list name is generic (such as "announce") it may be helpful to prefix it with OSGeo-, eg. "[OSGeo-Announce]"
* Be sure to choose a name that does not already have an existing alias, such as: sales, support, www, security. If you need to use one of these names someone will have to edit the /etc/aliases file for you manually.

== Other options ==

* For announce lists (ie. moderated lists) turn on "Emergency moderation of all list traffic" on. It is on the ''General'' tab.

= Outstanding Issues =

# Administrator/moderator permissions. Currently this is a hodgepodge. Some administrators have set the passwords but then others can't help administrate the list. The default admin password is not very secure. It has been suggested that we use some sort of LDAP/http authentication to verify that folks trying to do list admin are in some sort of mail administration group.
# List setting policies. Do we want to mandate more policies than the ones listed above as "Notes for List Administrators"?
# Search. Do we want to do anything special to enable searching the archive? Jason has setup an OSGeo.org grouping on nabble (<strike>http://www.nabble.com/OSGeo.org-f18127.html</strike>, http://osgeo-org.1803224.n2.nabble.com/) that makes searching all osgeo related mailing lists effective. We might want to expand on that.

= System Tasks =

== New Lists ==

* Create a new list through the [http://lists.osgeo.org/mailman/create web admin login].

== Renaming Lists ==

* create new list
$sudo /usr/lib/mailman/bin/newlist listname admins@email lists_passwd
* move original lists archive to newlists archive location
$ sudo cp /var/lib/mailman/archives/private/oldlist.mbox/oldlist.mbox \
/var/lib/mailman/archives/private/newlist.mbox/newlist.mbox
* create archive
$ sudo /usr/lib/mailman/bin/arch --wipe newlist
* export subscribers from old list regular and digest members
$ sudo /usr/lib/mailman/bin/list_members -r oldlistname > listname-regular.txt
$ sudo /usr/lib/mailman/bin/list_members -d oldlistname > listname-digest.txt
* import subscribers into new list
$ sudo /usr/lib/mailman/bin/add_members --regular-members=listname-regular.txt --welcome-msg=y newlistname
$ sudo /usr/lib/mailman/bin/add_members --digest-members=listname-digest.txt --welcome-msg=y newlistname
* remove old list
$ sudo /usr/lib/mailman/bin/rmlist oldlistname
* check that proper permissions are set (takes 10+ minutes!)
$ sudo /usr/lib/mailman/bin/check_perms -f
* edit postfix aliases - /etc/aliases
oldlist: newlist@lists.osgeo.org
oldlist-request: newlist-request@lists.osgeo.org
oldlist-admin: newlist-admin@lists.osgeo.org
oldlist-owner: newlist-owner@lists.osgeo.org
* update postfix with new aliases
$ sudo /usr/bin/newaliases
$ sudo /usr/sbin/service postfix reload

== copy / clone user addresses across lists ==
* add '''-r''' to remove the old address
$ sudo clone_member old@address.com new@address.com

== Migrate ==

When migrating from another system to osgeo, get the .mbox files, and the whole /var/lib/mailman/lists/<listname> directory, and follow roughly the following steps as root (or sudo each step):

# newlist -q grass-announce warmerdam@pobox.com junk
# cd /var/lib/mailman/lists/grass-announce
# cp ~warmerdam/grass-announce/* .
# withlist -l -r fix_url grass-announce
# /usr/lib/mailman/bin/arch grass-announce ~warmerdam/grass-announce.mbox
# chown -R list.list /var/lib/mailman/lists/grass-announce
# chown -R list.list /var/lib/mailman/archives/private/grass-announce*
# /usr/lib/mailman/bin/genaliases
# /usr/sbin/service postfix restart
# /usr/lib/mailman/bin/mailmanctl restart

If the list name on the new system is different than on the old system, it may be prudent to fix this up on the mail page of the web admin interface after the ''withlist'' command has been used, and before the archives are imported. (''FrankW'')

== References ==
* Here is [http://www.chris-lamb.co.uk/2007/10/02/renaming-a-mailman-list/ another approach to renaming], though our web admin interface won't actually allow you to do the final rename step

== Remove Mails from Archive ==
Sometimes users send mails with contentious content to the list and ask for it to be removed. As a courtesy this should be done asap. In general it is better to not remove the mail altogether but just remove the content. Instructions:
* http://wiki.list.org/pages/viewpage.action?pageId=4030681
Archives live in:
/var/lib/mailman/archives/
To recreate archives use:
/usr/lib/mailman/bin/arch [listname]

== List Statistics ==

From time to time it is nice to get a sense of the number of lists, users, etc. The following may be helpful:

all subscribers of all osgeo lists hosted on osgeo.org:

sudo list_lists -b | xargs -n 1 sudo list_members | wc -l

unique list of email addresses across all lists:

sudo list_lists -b | xargs -n 1 sudo list_members | sort | uniq | wc -l

Note: since 2009 there is [[User:Neteler|Markus Neteler]]'s cronjob running for gathering these statistics and sending them to "info AT osgeo org". For a time series, [[VisibilityStats#Mailing_list_subscribers|see statistics]]

= Nabble =

There are a variety of web forum oriented interfaces for mailing lists that can be connected to existing mailing lists. One of the most widely used is Nabble and OSGeo makes an effort to provide some administrative support for it.

The Nabble liasons for OSGeo are [[Jorge Sanz]] with [[Mateusz Loskot]] as a backup.

Technical details to follow.

[[Category:Infrastructure]]

SAC:Mailing Lists

2014-01-30T19:26:21Z

Warmerdam: /* Renaming Lists */

Mailing lists are administered with Mailman on the virtual host lists.osgeo.org. Physically this is the "Mail" VM running on osgeo4. Frank Warmerdam (warmerdam) and Alan Boudreault (aboudreault) do most of the mailman work.

= Notes for List Administrators =

== Requesting a new list ==

If your project or activity would like to have a mailing list at lists.osgeo.org please take the following steps:

* First, confirm that there isn't already an appropriate list for this activity, and consider whether OSGeo is the right home for the proposed list.
* File a ticket at http://trac.osgeo.org/osgeo (use your OSGeo Userid to login) and make sure the component is set to "SAC". This is the request to the System Administration Committee to create the list.
* Please include the exact name you would like for the list (ie. foo-announce), and the email address of the person who should be the list admin. Also provide the justification for the list, and indicate if it was explicitly requested by an OSGeo Project PSC or project representative.
* Include any special instructions (such pointers to info if the list is actually being migrated from elsewhere).
* Hopefully, someone in SAC will act on the ticket and create the list. When complete the ticket will be updated and closed, and the proposed admin will receive an email with the admin password for the list.
* Review the list settings, in particular ensuring that the short description gets set (ie. review following points)

Generally it is up to the mailman administrator to judge whether a list is justified for creation. The justification doesn't need to be strong, but the list should be OSGeo related, reasonably likely to generate some use, or be requested on behalf of a project.

== All lists ==

* Please set "A terse phrase identifying this list." to something brief and meaningful as this is what is shown on the main lists directory. It is on the ''General'' tab.
* Set "Who can view subscription list?" on the ''Privacy'' tab to "List Admin Only", otherwise anyone can subscribe and then harvest the mailing list.
* Set ''generic_nonmember_action'' on the ''Privacy->Sender filters'' tab to reject as most lists are not actively administered so we prefer to reject rather than holding posts from unsubscribed folks.
* Ensure the "Prefix for subject line of list postings." on the ''General'' tab is set to something meaningful. If the list name is generic (such as "announce") it may be helpful to prefix it with OSGeo-, eg. "[OSGeo-Announce]"
* Be sure to choose a name that does not already have an existing alias, such as: sales, support, www, security. If you need to use one of these names someone will have to edit the /etc/aliases file for you manually.

== Other options ==

* For announce lists (ie. moderated lists) turn on "Emergency moderation of all list traffic" on. It is on the ''General'' tab.

= Outstanding Issues =

# Administrator/moderator permissions. Currently this is a hodgepodge. Some administrators have set the passwords but then others can't help administrate the list. The default admin password is not very secure. It has been suggested that we use some sort of LDAP/http authentication to verify that folks trying to do list admin are in some sort of mail administration group.
# List setting policies. Do we want to mandate more policies than the ones listed above as "Notes for List Administrators"?
# Search. Do we want to do anything special to enable searching the archive? Jason has setup an OSGeo.org grouping on nabble (<strike>http://www.nabble.com/OSGeo.org-f18127.html</strike>, http://osgeo-org.1803224.n2.nabble.com/) that makes searching all osgeo related mailing lists effective. We might want to expand on that.

= System Tasks =

== New Lists ==

* Create a new list through the [http://lists.osgeo.org/mailman/create web admin login].

== Renaming Lists ==

* create new list
$sudo /usr/lib/mailman/bin/newlist listname admins@email lists_passwd
* move original lists archive to newlists archive location
$ sudo cp /var/lib/mailman/archives/private/oldlist.mbox/oldlist.mbox \
/var/lib/mailman/archives/private/newlist.mbox/newlist.mbox
* create archive
$ sudo /usr/lib/mailman/bin/arch --wipe newlist
* export subscribers from old list regular and digest members
$ sudo /usr/lib/mailman/bin/list_members -r oldlistname > listname-regular.txt
$ sudo /usr/lib/mailman/bin/list_members -d oldlistname > listname-digest.txt
* import subscribers into new list
$ sudo /usr/lib/mailman/bin/add_members --regular-members=listname-regular.txt --welcome-msg=y newlistname
$ sudo /usr/lib/mailman/bin/add_members --digest-members=listname-digest.txt --welcome-msg=y newlistname
* remove old list
$ sudo /usr/lib/mailman/bin/rmlist oldlistname
* check that proper permissions are set
$ sudo /usr/lib/mailman/bin/check_perms -f
* edit postfix aliases - /etc/aliases
oldlist: newlist@lists.osgeo.org
oldlist-request: newlist-request@lists.osgeo.org
oldlist-admin: newlist-admin@lists.osgeo.org
oldlist-owner: newlist-owner@lists.osgeo.org
* update postfix with new aliases
$ sudo /usr/bin/newaliases
$ sudo /usr/sbin/service postfix reload

== copy / clone user addresses across lists ==
* add '''-r''' to remove the old address
$ sudo clone_member old@address.com new@address.com

== Migrate ==

When migrating from another system to osgeo, get the .mbox files, and the whole /var/lib/mailman/lists/<listname> directory, and follow roughly the following steps as root (or sudo each step):

# newlist -q grass-announce warmerdam@pobox.com junk
# cd /var/lib/mailman/lists/grass-announce
# cp ~warmerdam/grass-announce/* .
# withlist -l -r fix_url grass-announce
# /usr/lib/mailman/bin/arch grass-announce ~warmerdam/grass-announce.mbox
# chown -R list.list /var/lib/mailman/lists/grass-announce
# chown -R list.list /var/lib/mailman/archives/private/grass-announce*
# /usr/lib/mailman/bin/genaliases
# /usr/sbin/service postfix restart
# /usr/lib/mailman/bin/mailmanctl restart

If the list name on the new system is different than on the old system, it may be prudent to fix this up on the mail page of the web admin interface after the ''withlist'' command has been used, and before the archives are imported. (''FrankW'')

== References ==
* Here is [http://www.chris-lamb.co.uk/2007/10/02/renaming-a-mailman-list/ another approach to renaming], though our web admin interface won't actually allow you to do the final rename step

== Remove Mails from Archive ==
Sometimes users send mails with contentious content to the list and ask for it to be removed. As a courtesy this should be done asap. In general it is better to not remove the mail altogether but just remove the content. Instructions:
* http://wiki.list.org/pages/viewpage.action?pageId=4030681
Archives live in:
/var/lib/mailman/archives/
To recreate archives use:
/usr/lib/mailman/bin/arch [listname]

== List Statistics ==

From time to time it is nice to get a sense of the number of lists, users, etc. The following may be helpful:

all subscribers of all osgeo lists hosted on osgeo.org:

sudo list_lists -b | xargs -n 1 sudo list_members | wc -l

unique list of email addresses across all lists:

sudo list_lists -b | xargs -n 1 sudo list_members | sort | uniq | wc -l

Note: since 2009 there is [[User:Neteler|Markus Neteler]]'s cronjob running for gathering these statistics and sending them to "info AT osgeo org". For a time series, [[VisibilityStats#Mailing_list_subscribers|see statistics]]

= Nabble =

There are a variety of web forum oriented interfaces for mailing lists that can be connected to existing mailing lists. One of the most widely used is Nabble and OSGeo makes an effort to provide some administrative support for it.

The Nabble liasons for OSGeo are [[Jorge Sanz]] with [[Mateusz Loskot]] as a backup.

Technical details to follow.

[[Category:Infrastructure]]

SAC:Mailing Lists

2014-01-30T19:25:53Z

Warmerdam: /* Renaming Lists */

Mailing lists are administered with Mailman on the virtual host lists.osgeo.org. Physically this is the "Mail" VM running on osgeo4. Frank Warmerdam (warmerdam) and Alan Boudreault (aboudreault) do most of the mailman work.

= Notes for List Administrators =

== Requesting a new list ==

If your project or activity would like to have a mailing list at lists.osgeo.org please take the following steps:

* First, confirm that there isn't already an appropriate list for this activity, and consider whether OSGeo is the right home for the proposed list.
* File a ticket at http://trac.osgeo.org/osgeo (use your OSGeo Userid to login) and make sure the component is set to "SAC". This is the request to the System Administration Committee to create the list.
* Please include the exact name you would like for the list (ie. foo-announce), and the email address of the person who should be the list admin. Also provide the justification for the list, and indicate if it was explicitly requested by an OSGeo Project PSC or project representative.
* Include any special instructions (such pointers to info if the list is actually being migrated from elsewhere).
* Hopefully, someone in SAC will act on the ticket and create the list. When complete the ticket will be updated and closed, and the proposed admin will receive an email with the admin password for the list.
* Review the list settings, in particular ensuring that the short description gets set (ie. review following points)

Generally it is up to the mailman administrator to judge whether a list is justified for creation. The justification doesn't need to be strong, but the list should be OSGeo related, reasonably likely to generate some use, or be requested on behalf of a project.

== All lists ==

* Please set "A terse phrase identifying this list." to something brief and meaningful as this is what is shown on the main lists directory. It is on the ''General'' tab.
* Set "Who can view subscription list?" on the ''Privacy'' tab to "List Admin Only", otherwise anyone can subscribe and then harvest the mailing list.
* Set ''generic_nonmember_action'' on the ''Privacy->Sender filters'' tab to reject as most lists are not actively administered so we prefer to reject rather than holding posts from unsubscribed folks.
* Ensure the "Prefix for subject line of list postings." on the ''General'' tab is set to something meaningful. If the list name is generic (such as "announce") it may be helpful to prefix it with OSGeo-, eg. "[OSGeo-Announce]"
* Be sure to choose a name that does not already have an existing alias, such as: sales, support, www, security. If you need to use one of these names someone will have to edit the /etc/aliases file for you manually.

== Other options ==

* For announce lists (ie. moderated lists) turn on "Emergency moderation of all list traffic" on. It is on the ''General'' tab.

= Outstanding Issues =

# Administrator/moderator permissions. Currently this is a hodgepodge. Some administrators have set the passwords but then others can't help administrate the list. The default admin password is not very secure. It has been suggested that we use some sort of LDAP/http authentication to verify that folks trying to do list admin are in some sort of mail administration group.
# List setting policies. Do we want to mandate more policies than the ones listed above as "Notes for List Administrators"?
# Search. Do we want to do anything special to enable searching the archive? Jason has setup an OSGeo.org grouping on nabble (<strike>http://www.nabble.com/OSGeo.org-f18127.html</strike>, http://osgeo-org.1803224.n2.nabble.com/) that makes searching all osgeo related mailing lists effective. We might want to expand on that.

= System Tasks =

== New Lists ==

* Create a new list through the [http://lists.osgeo.org/mailman/create web admin login].

== Renaming Lists ==

* create new list
$sudo /usr/lib/mailman/bin/newlist listname admins@email lists_passwd
* move original lists archive to newlists archive location
$ sudo cp /var/lib/mailman/archives/private/oldlist.mbox/oldlist.mbox \
/var/lib/mailman/archives/private/newlist.mbox/newlist.mbox
* create archive
$ sudo /usr/lib/mailman/bin/arch --wipe newlist
* export subscribers from old list regular and digest members
$ sudo /usr/lib/mailman/bin/list_members -r oldlistname > listname-regular.txt
$ sudo /usr/lib/mailman/bin/list_members -d oldlistname > listname-digest.txt
* import subscribers into new list
$ sudo /usr/lib/mailman/bin/add_members --regular-members=listname-regular.txt --welcome-msg=y newlistname
$ sudo /usr/lib/mailman/bin/add_members --digest-members=listname-digest.txt --welcome-msg=y newlistname
* remove old list
$ sudo /usr/lib/mailman/bin/rmlist oldlistname
* update aliases and check that proper permissions are set
$ sudo /usr/lib/mailman/bin/check_perms -f
* edit postfix aliases - /etc/aliases
oldlist: newlist@lists.osgeo.org
oldlist-request: newlist-request@lists.osgeo.org
oldlist-admin: newlist-admin@lists.osgeo.org
oldlist-owner: newlist-owner@lists.osgeo.org
* update postfix with new aliases
$ sudo /usr/bin/newaliases
$ sudo /usr/sbin/service postfix reload

== copy / clone user addresses across lists ==
* add '''-r''' to remove the old address
$ sudo clone_member old@address.com new@address.com

== Migrate ==

When migrating from another system to osgeo, get the .mbox files, and the whole /var/lib/mailman/lists/<listname> directory, and follow roughly the following steps as root (or sudo each step):

# newlist -q grass-announce warmerdam@pobox.com junk
# cd /var/lib/mailman/lists/grass-announce
# cp ~warmerdam/grass-announce/* .
# withlist -l -r fix_url grass-announce
# /usr/lib/mailman/bin/arch grass-announce ~warmerdam/grass-announce.mbox
# chown -R list.list /var/lib/mailman/lists/grass-announce
# chown -R list.list /var/lib/mailman/archives/private/grass-announce*
# /usr/lib/mailman/bin/genaliases
# /usr/sbin/service postfix restart
# /usr/lib/mailman/bin/mailmanctl restart

If the list name on the new system is different than on the old system, it may be prudent to fix this up on the mail page of the web admin interface after the ''withlist'' command has been used, and before the archives are imported. (''FrankW'')

== References ==
* Here is [http://www.chris-lamb.co.uk/2007/10/02/renaming-a-mailman-list/ another approach to renaming], though our web admin interface won't actually allow you to do the final rename step

== Remove Mails from Archive ==
Sometimes users send mails with contentious content to the list and ask for it to be removed. As a courtesy this should be done asap. In general it is better to not remove the mail altogether but just remove the content. Instructions:
* http://wiki.list.org/pages/viewpage.action?pageId=4030681
Archives live in:
/var/lib/mailman/archives/
To recreate archives use:
/usr/lib/mailman/bin/arch [listname]

== List Statistics ==

From time to time it is nice to get a sense of the number of lists, users, etc. The following may be helpful:

all subscribers of all osgeo lists hosted on osgeo.org:

sudo list_lists -b | xargs -n 1 sudo list_members | wc -l

unique list of email addresses across all lists:

sudo list_lists -b | xargs -n 1 sudo list_members | sort | uniq | wc -l

Note: since 2009 there is [[User:Neteler|Markus Neteler]]'s cronjob running for gathering these statistics and sending them to "info AT osgeo org". For a time series, [[VisibilityStats#Mailing_list_subscribers|see statistics]]

= Nabble =

There are a variety of web forum oriented interfaces for mailing lists that can be connected to existing mailing lists. One of the most widely used is Nabble and OSGeo makes an effort to provide some administrative support for it.

The Nabble liasons for OSGeo are [[Jorge Sanz]] with [[Mateusz Loskot]] as a backup.

Technical details to follow.

[[Category:Infrastructure]]

SAC:Mailing Lists

2014-01-30T19:14:07Z

Warmerdam: /* Renaming Lists */

Mailing lists are administered with Mailman on the virtual host lists.osgeo.org. Physically this is the "Mail" VM running on osgeo4. Frank Warmerdam (warmerdam) and Alan Boudreault (aboudreault) do most of the mailman work.

= Notes for List Administrators =

== Requesting a new list ==

If your project or activity would like to have a mailing list at lists.osgeo.org please take the following steps:

* First, confirm that there isn't already an appropriate list for this activity, and consider whether OSGeo is the right home for the proposed list.
* File a ticket at http://trac.osgeo.org/osgeo (use your OSGeo Userid to login) and make sure the component is set to "SAC". This is the request to the System Administration Committee to create the list.
* Please include the exact name you would like for the list (ie. foo-announce), and the email address of the person who should be the list admin. Also provide the justification for the list, and indicate if it was explicitly requested by an OSGeo Project PSC or project representative.
* Include any special instructions (such pointers to info if the list is actually being migrated from elsewhere).
* Hopefully, someone in SAC will act on the ticket and create the list. When complete the ticket will be updated and closed, and the proposed admin will receive an email with the admin password for the list.
* Review the list settings, in particular ensuring that the short description gets set (ie. review following points)

Generally it is up to the mailman administrator to judge whether a list is justified for creation. The justification doesn't need to be strong, but the list should be OSGeo related, reasonably likely to generate some use, or be requested on behalf of a project.

== All lists ==

* Please set "A terse phrase identifying this list." to something brief and meaningful as this is what is shown on the main lists directory. It is on the ''General'' tab.
* Set "Who can view subscription list?" on the ''Privacy'' tab to "List Admin Only", otherwise anyone can subscribe and then harvest the mailing list.
* Set ''generic_nonmember_action'' on the ''Privacy->Sender filters'' tab to reject as most lists are not actively administered so we prefer to reject rather than holding posts from unsubscribed folks.
* Ensure the "Prefix for subject line of list postings." on the ''General'' tab is set to something meaningful. If the list name is generic (such as "announce") it may be helpful to prefix it with OSGeo-, eg. "[OSGeo-Announce]"
* Be sure to choose a name that does not already have an existing alias, such as: sales, support, www, security. If you need to use one of these names someone will have to edit the /etc/aliases file for you manually.

== Other options ==

* For announce lists (ie. moderated lists) turn on "Emergency moderation of all list traffic" on. It is on the ''General'' tab.

= Outstanding Issues =

# Administrator/moderator permissions. Currently this is a hodgepodge. Some administrators have set the passwords but then others can't help administrate the list. The default admin password is not very secure. It has been suggested that we use some sort of LDAP/http authentication to verify that folks trying to do list admin are in some sort of mail administration group.
# List setting policies. Do we want to mandate more policies than the ones listed above as "Notes for List Administrators"?
# Search. Do we want to do anything special to enable searching the archive? Jason has setup an OSGeo.org grouping on nabble (<strike>http://www.nabble.com/OSGeo.org-f18127.html</strike>, http://osgeo-org.1803224.n2.nabble.com/) that makes searching all osgeo related mailing lists effective. We might want to expand on that.

= System Tasks =

== New Lists ==

* Create a new list through the [http://lists.osgeo.org/mailman/create web admin login].

== Renaming Lists ==

* create new list
$sudo /usr/lib/mailman/bin/newlist listname admins@email lists_passwd
* move original lists archive to newlists archive location
$ sudo cp /var/lib/mailman/archives/private/oldlist.mbox/oldlist.mbox \
/var/lib/mailman/archives/private/newlist.mbox/newlist.mbox
* create archive
$ sudo /usr/lib/mailman/bin/arch --wipe newlist
* export subscribers from old list regular and digest members
$ sudo /usr/lib/mailman/bin/list_members -r oldlistname > listname-regular.txt
$ sudo /usr/lib/mailman/bin/list_members -d oldlistname > listname-digest.txt
* import subscribers into new list
$ sudo /usr/lib/mailman/bin/add_members --regular-members=listname-regular.txt --welcome-msg=y newlistname
$ sudo /usr/lib/mailman/bin/add_members --digest-members=listname-digest.txt --welcome-msg=y newlistname
* remove old list
$ sudo /usr/lib/mailman/bin/rmlist oldlistname
* update aliases and check that proper permissions are set
$ sudo /usr/lib/mailman/bin/genaliases
$ sudo /usr/lib/mailman/bin/check_perms -f
* edit postfix aliases - /etc/aliases
oldlist: newlist@lists.osgeo.org
oldlist-request: newlist-request@lists.osgeo.org
oldlist-admin: newlist-admin@lists.osgeo.org
oldlist-owner: newlist-owner@lists.osgeo.org
* update postfix with new aliases
$ sudo /usr/bin/newaliases
$ sudo /usr/sbin/service postfix reload

== copy / clone user addresses across lists ==
* add '''-r''' to remove the old address
$ sudo clone_member old@address.com new@address.com

== Migrate ==

When migrating from another system to osgeo, get the .mbox files, and the whole /var/lib/mailman/lists/<listname> directory, and follow roughly the following steps as root (or sudo each step):

# newlist -q grass-announce warmerdam@pobox.com junk
# cd /var/lib/mailman/lists/grass-announce
# cp ~warmerdam/grass-announce/* .
# withlist -l -r fix_url grass-announce
# /usr/lib/mailman/bin/arch grass-announce ~warmerdam/grass-announce.mbox
# chown -R list.list /var/lib/mailman/lists/grass-announce
# chown -R list.list /var/lib/mailman/archives/private/grass-announce*
# /usr/lib/mailman/bin/genaliases
# /usr/sbin/service postfix restart
# /usr/lib/mailman/bin/mailmanctl restart

If the list name on the new system is different than on the old system, it may be prudent to fix this up on the mail page of the web admin interface after the ''withlist'' command has been used, and before the archives are imported. (''FrankW'')

== References ==
* Here is [http://www.chris-lamb.co.uk/2007/10/02/renaming-a-mailman-list/ another approach to renaming], though our web admin interface won't actually allow you to do the final rename step

== Remove Mails from Archive ==
Sometimes users send mails with contentious content to the list and ask for it to be removed. As a courtesy this should be done asap. In general it is better to not remove the mail altogether but just remove the content. Instructions:
* http://wiki.list.org/pages/viewpage.action?pageId=4030681
Archives live in:
/var/lib/mailman/archives/
To recreate archives use:
/usr/lib/mailman/bin/arch [listname]

== List Statistics ==

From time to time it is nice to get a sense of the number of lists, users, etc. The following may be helpful:

all subscribers of all osgeo lists hosted on osgeo.org:

sudo list_lists -b | xargs -n 1 sudo list_members | wc -l

unique list of email addresses across all lists:

sudo list_lists -b | xargs -n 1 sudo list_members | sort | uniq | wc -l

Note: since 2009 there is [[User:Neteler|Markus Neteler]]'s cronjob running for gathering these statistics and sending them to "info AT osgeo org". For a time series, [[VisibilityStats#Mailing_list_subscribers|see statistics]]

= Nabble =

There are a variety of web forum oriented interfaces for mailing lists that can be connected to existing mailing lists. One of the most widely used is Nabble and OSGeo makes an effort to provide some administrative support for it.

The Nabble liasons for OSGeo are [[Jorge Sanz]] with [[Mateusz Loskot]] as a backup.

Technical details to follow.

[[Category:Infrastructure]]

WebExtraVM

2013-12-08T23:30:55Z

Warmerdam: /* *.foss4g.org */

The Web Extra VM is a Debian virtual machine administered by [[SAC]], hosted on OSGeo3 at OSU OSL and used for hosting web sites and services that are directly the responsibility of SAC and that don't fit on the other more special purpose VMs (ie. TracSVN, or Drupal). OSGeo member/project services that SAC isn't willing to take direct responsibility for likely belong on either the [[ProjectsVM]] or the [[AdhocVM]].

The VM is reachable by ssh at webextra.osgeo.osuosl.org. Anyone in the https://www.osgeo.org/cgi-bin/auth/ldap_shell.py?group=sac (SAC) list has ssh access, and anyone in this group can add new people via the link.

== Existing Services on Web Extra VM ==

=== mum03.mapserver.org ===

* /osgeo/foss4g/mum2003-web
* Admined by FrankW
* static html historial site
* Backup available in /osgeo/backup/longterm/mum03 on BackupVM.

=== planet.osgeo.org ===

* /osgeo/venus (venus2?)
* Admined: [[Paolo Corti]], [[User:Jsanz|Jorge Gaspar Sanz Salinas]], [[User:Mloskot|Mateusz Loskot]], [[User:crschmidt|Christopher Schmidt]]
* See also: [[PlanetOSGeo]]
* All admins can be contacted by e-mail on planet (at) osgeo (dot) org

=== live.osgeo.org ===

* /osgeo/osgeolive
* Static html site from SVN (https://svn.osgeo.org/osgeo/livedvd/website)
* Alex (wildintellect)

=== gallery.osgeo.org ===

Status: offline due to massive spamming

TODO: implement moderated queue or other antispam measure

* /var/www/gallery/
* content is in sqlite DB
* Spam removal howto: to be implemented

=== 2011ws.foss4g.org ===

* /osgeo/foss4g/uploads
* Admined by FrankW, jmckenna
* used for FOSS4G 2011 workshop files (through SFTP)

=== *.foss4g.org ===
Includes main www and 2003, 2006, 2007, 2008, 2009, 2010, 2012, 2013
/osgeo/foss4g/*
* 2011 is on webvm - as it's using Drupal
* Most are static dumps from CMSs that were used,
* 2008 uses the OCS instance (conference.osgeo.org) hosted on webextra
/osgeo/ocs2
* Most being moved from osgeo1 29sep11 by tmitchell
* 2010 also moved from projects vm.
* 2013 site lives in svn and is checked out here manually

=== vmap0.tiles.osgeo.org ===

* Serves as http://vmap0.tiles.osgeo.org/wms/vmap0?SERVICE=WMS&VERSION=1.1.0&REQUEST=GetCapabilities
* Lives in /var/www/tiles/vmap0 and /mapdata (2.3G)
* Originally setup by Chris Schmidt.
* Currently produces the bulk of load on the webextra VM.
* Presumably this is widely used as a default layer in OpenLayers.
* For the purpose of sharing the load, a copy of this service has been set up on "sphere.telascience.org" and a round-robin DNS provides balancing (Martin Spott).

[[Category:Infrastructure]]

SAC:Mailing Lists

2013-12-03T01:33:59Z

Warmerdam: /* Migrate */ fix some mailman migration details for new OSU OSL version.

Mailing lists are administered with Mailman on the virtual host lists.osgeo.org. Physically this is the "Mail" VM running on osgeo4. Frank Warmerdam (warmerdam) and Alan Boudreault (aboudreault) do most of the mailman work.

= Notes for List Administrators =

== Requesting a new list ==

If your project or activity would like to have a mailing list at lists.osgeo.org please take the following steps:

* First, confirm that there isn't already an appropriate list for this activity, and consider whether OSGeo is the right home for the proposed list.
* File a ticket at http://trac.osgeo.org/osgeo (use your OSGeo Userid to login) and make sure the component is set to "SAC". This is the request to the System Administration Committee to create the list.
* Please include the exact name you would like for the list (ie. foo-announce), and the email address of the person who should be the list admin. Also provide the justification for the list, and indicate if it was explicitly requested by an OSGeo Project PSC or project representative.
* Include any special instructions (such pointers to info if the list is actually being migrated from elsewhere).
* Hopefully, someone in SAC will act on the ticket and create the list. When complete the ticket will be updated and closed, and the proposed admin will receive an email with the admin password for the list.
* Review the list settings, in particular ensuring that the short description gets set (ie. review following points)

Generally it is up to the mailman administrator to judge whether a list is justified for creation. The justification doesn't need to be strong, but the list should be OSGeo related, reasonably likely to generate some use, or be requested on behalf of a project.

== All lists ==

* Please set "A terse phrase identifying this list." to something brief and meaningful as this is what is shown on the main lists directory. It is on the ''General'' tab.
* Set "Who can view subscription list?" on the ''Privacy'' tab to "List Admin Only", otherwise anyone can subscribe and then harvest the mailing list.
* Set ''generic_nonmember_action'' on the ''Privacy->Sender filters'' tab to reject as most lists are not actively administered so we prefer to reject rather than holding posts from unsubscribed folks.
* Ensure the "Prefix for subject line of list postings." on the ''General'' tab is set to something meaningful. If the list name is generic (such as "announce") it may be helpful to prefix it with OSGeo-, eg. "[OSGeo-Announce]"
* Be sure to choose a name that does not already have an existing alias, such as: sales, support, www, security. If you need to use one of these names someone will have to edit the /etc/aliases file for you manually.

== Other options ==

* For announce lists (ie. moderated lists) turn on "Emergency moderation of all list traffic" on. It is on the ''General'' tab.

= Outstanding Issues =

# Administrator/moderator permissions. Currently this is a hodgepodge. Some administrators have set the passwords but then others can't help administrate the list. The default admin password is not very secure. It has been suggested that we use some sort of LDAP/http authentication to verify that folks trying to do list admin are in some sort of mail administration group.
# List setting policies. Do we want to mandate more policies than the ones listed above as "Notes for List Administrators"?
# Search. Do we want to do anything special to enable searching the archive? Jason has setup an OSGeo.org grouping on nabble (<strike>http://www.nabble.com/OSGeo.org-f18127.html</strike>, http://osgeo-org.1803224.n2.nabble.com/) that makes searching all osgeo related mailing lists effective. We might want to expand on that.

= System Tasks =

== New Lists ==

* Create a new list through the [http://lists.osgeo.org/mailman/create web admin login].

== Renaming Lists ==

* create new list
$sudo /usr/lib/mailman/bin/newlist listname admins@email lists_passwd
* move original lists archive to newlists archive location
$ sudo cp /var/lib/mailman/archives/private/oldlist.mbox/oldlist.mbox \
/var/lib/mailman/archives/private/newlist.mbox/
* create archive
$ sudo /usr/lib/mailman/bin/arch --wipe newlist
* export subscribers from old list regular and digest members
$ sudo /usr/lib/mailman/bin/list_members -r oldlistname > listname-regular.txt
$ sudo /usr/lib/mailman/bin/list_members -d oldlistname > listname-digest.txt
* import subscribers into new list
$ sudo /usr/lib/mailman/bin/add_members --regular-members=listname-regular.txt --welcome-msg=y newlistname
$ sudo /usr/lib/mailman/bin/add_members --digest-members=listname-digest.txt --welcome-msg=y newlistname
* remove old list
$ sudo /usr/lib/mailman/bin/rmlist oldlistname
* update aliases and check that proper permissions are set
$ sudo /usr/lib/mailman/bin/genaliases
$ sudo /usr/lib/mailman/bin/check_perms -f
* edit postfix aliases - /etc/aliases
oldlist: newlist@lists.osgeo.org
oldlist-request: newlist-request@lists.osgeo.org
oldlist-admin: newlist-admin@lists.osgeo.org
oldlist-owner: newlist-owner@lists.osgeo.org
* update postfix with new aliases
$ sudo /usr/bin/newaliases
$ sudo /usr/sbin/service postfix reload

== copy / clone user addresses across lists ==
* add '''-r''' to remove the old address
$ sudo clone_member old@address.com new@address.com

== Migrate ==

When migrating from another system to osgeo, get the .mbox files, and the whole /var/lib/mailman/lists/<listname> directory, and follow roughly the following steps as root (or sudo each step):

# newlist -q grass-announce warmerdam@pobox.com junk
# cd /var/lib/mailman/lists/grass-announce
# cp ~warmerdam/grass-announce/* .
# withlist -l -r fix_url grass-announce
# /usr/lib/mailman/bin/arch grass-announce ~warmerdam/grass-announce.mbox
# chown -R list.list /var/lib/mailman/lists/grass-announce
# chown -R list.list /var/lib/mailman/archives/private/grass-announce*
# /usr/lib/mailman/bin/genaliases
# /usr/sbin/service postfix restart
# /usr/lib/mailman/bin/mailmanctl restart

If the list name on the new system is different than on the old system, it may be prudent to fix this up on the mail page of the web admin interface after the ''withlist'' command has been used, and before the archives are imported. (''FrankW'')

== References ==
* Here is [http://www.chris-lamb.co.uk/2007/10/02/renaming-a-mailman-list/ another approach to renaming], though our web admin interface won't actually allow you to do the final rename step

== Remove Mails from Archive ==
Sometimes users send mails with contentious content to the list and ask for it to be removed. As a courtesy this should be done asap. In general it is better to not remove the mail altogether but just remove the content. Instructions:
* http://wiki.list.org/pages/viewpage.action?pageId=4030681
Archives live in:
/var/lib/mailman/archives/
To recreate archives use:
/usr/lib/mailman/bin/arch [listname]

== List Statistics ==

From time to time it is nice to get a sense of the number of lists, users, etc. The following may be helpful:

all subscribers of all osgeo lists hosted on osgeo.org:

sudo list_lists -b | xargs -n 1 sudo list_members | wc -l

unique list of email addresses across all lists:

sudo list_lists -b | xargs -n 1 sudo list_members | sort | uniq | wc -l

Note: since 2009 there is [[User:Neteler|Markus Neteler]]'s cronjob running for gathering these statistics and sending them to "info AT osgeo org". For a time series, [[VisibilityStats#Mailing_list_subscribers|see statistics]]

= Nabble =

There are a variety of web forum oriented interfaces for mailing lists that can be connected to existing mailing lists. One of the most widely used is Nabble and OSGeo makes an effort to provide some administrative support for it.

The Nabble liasons for OSGeo are [[Jorge Sanz]] with [[Mateusz Loskot]] as a backup.

Technical details to follow.

[[Category:Infrastructure]]

Board of Directors

2013-10-17T18:23:50Z

Warmerdam: /* Meetings */ remove the extra wiki link leading back to here.

== OSGeo Foundation Board of Directors ==

The board is elected by the [http://www.osgeo.org/charter_members Charter members] as outlined in the [[Board Election Procedure]].

Period: August 2012 - July/August 2014
* [[Anne Ghisla]] - Berlin, Germany (Central European Time UTC +2h)
* [[Jeff McKenna]] - Halifax, Nova Scotia, Canada (Atlantic Time UTC - 3h)
* [[Daniel Morissette]] - Chicoutimi, Quebec, Canada (US Eastern Time UTC - 4h)
* [[Cameron Shorter]] - Sydney, Australia (Australian Eastern Time UTC + 10h)
* [[Frank Warmerdam]] - Mountain View, California, USA (US Pacific Time UTC - 7h)

Period: September 2013 - August 2015
* [[Jáchym Čepický]] - Jičín, Czech republic (Central European Time UTC +2h)
* [[Jorge Sanz]] - Valencia, Spain (Central European Time UTC +2h)
* [[Bart van den Eijnden]], The Netherlands (Central European Time UTC +2h)
* [[Gerald Fenoy | Gérald Fenoy]], France (Central European Time UTC +2h)

More detailed information is available in the [[Board Member Profiles]].

==Meeting timeslots==
* A. [http://www.timeanddate.com/worldclock/meetingdetails.html?hour=20&min=0&sec=0&p1=224&p2=75&p3=179&p4=286&p5=215&p6=240 20.00 UTC]
* B. [http://www.timeanddate.com/worldclock/meetingdetails.html?hour=12&min=0&sec=0&p1=224&p2=75&p3=179&p4=286&p5=215&p6=240 12:00 UTC]
* C. [http://www.timeanddate.com/worldclock/meetingdetails.html?hour=3&min=0&sec=0&p1=224&p2=75&p3=179&p4=286&p5=215&p6=240 03:00 UTC]

[http://www.timeanddate.com/worldclock/meetingtime.html?p1=224&p2=75&p3=179&p4=286&p5=215&p6=240&iv=0 Meeting Planner]

== Meetings ==
; Next meeting:
* [[Board Meeting 2013-10-17]] 20.00 UTC

; Previous meetings:
* [[Board Meeting 2013-09-20]] 7.00 UTC
* [[Informal OSGeo OGC Meeting 2013-09-18]]
* [[Board Meeting 2013-08-15]] 3.00 UTC
* [[Board Meeting 2013-07-11]] 12.00 UTC
* [[Board Meeting 2013-06-13]] 20.00 UTC
* [[Board Meeting 2013-05-09]] 20.00 UTC
* [[Board Meeting 2013-04-11]] 20.00 UTC
* [[Board Meeting 2013-02-26]] 18.00 UTC
* [[Board Meeting 2013-01-17]] 20.00 UTC

== Meeting Archive ==
[[:Category:Board_Meetings_2012|2012]] - [[:Category:Board_Meetings_2011|2011]] - [[:Category:Board_Meetings_2010|2010]] - [[:Category:Board_Meetings_2009|2009]] - [[Board Meetings 2008|2008]] - [[Board Meetings 2007|2007]] - [[Board Meetings 2006|2006]] - [http://www.osgeo.org/content/foundation/meetings/board/board_meetings.html Earlier].

== Documents ==
* [[Executive Positions]] and [[Director Responsibilities]]
* [[Board Election Procedure]]
* Election 2012: [[Board Election 2012 Results]]
* Election 2011: [[Board Election 2011 Results]]
* Election 2010: [[Board Election 2010 Results]]
* Election 2009: [[Board Election 2009]], see 2009 section of [[Proposed Board Election Procedure]]
* Election 2008: [[Board Election 2008]], see 2008 section of [[Proposed Board Election Procedure]]
* <strike>[[Executive Director]] (rough ideas), [[Executive Director Job Description]]</strike> (no such position at time)
* Election 2007: [[Board Election 2007]], see 2007 section of [[Proposed Board Election Procedure]]
* [[Foundation Sponsorship]] (adopted), [[Project Sponsorship]] (adopted), [[Local Chapter Sponsorship]] (idea)
* [[Conflict Of Interest Policy]]

== Mailing list ==

The http://lists.osgeo.org/mailman/listinfo/board mailing list is used for most public board discussions. There is also a private board mailing list used only for matters that are considered needful to be kept private.

== Previous OSGeo Foundation Boards of Directors ==

* [[Board Election 2012 Results|Board of Directors 2012]] (Aug. 2012 - Aug. 2013)
* [[Board Election 2011 Results|Board of Directors 2011]] (Aug. 2011 - Aug. 2012)
* [[Board Election 2010 Results|Board of Directors 2010]] (Aug. 2010 - Aug. 2011)
* [[Board Election 2009 Results|Board of Directors 2009]] (Sept. 2009 - Aug. 2010)
* [[Board Election 2008 Results|Board of Directors 2008]] (July 2008 - Sept. 2009)
* [[Board Election 2007 Results|Board of Directors 2007]] (Aug. 2007 - July 2008)
* [[Interim Board of Directors 2006]] (Feb. 2006 - July 2007)

An interim Board of Directors with 5 members was elected on February 4th, 2006, by the initial members of the [http://www.osgeo.org Open Source Geospatial Foundation]. On March 18th, 2006, the board has been completed to now total nine members:

== Potential FAQ ==

'''Q''': What do board members do? 
'''A''': http://wiki.osgeo.org/wiki/Director_Responsibilities

'''Q''': That doc doesn't say anything about meetings. How often to board members meet? 
'''A''': The [http://www.osgeo.org/content/foundation/incorporation/bylaws.html foundation bylaws] say the board meets after the after the annual members meeting and then at regular meetings on a schedule fixed by directors. In practice, the board schedules monthly meetings in addition to the annual face-to-face meeting after the AGM at the FOSS4G conference.

'''Q''': How are board decisions made? 
'''A''': The [http://www.osgeo.org/content/foundation/incorporation/bylaws.html bylaws] (section 4.5) describe that a majority of members must be present for an event to be considered a meeting. At a meeting, each member present is given one vote. Strictly speaking (according to the bylaws) an affirmative vote by the majority of members present at a meeting constitutes a decision by the board. In practice, we don't consider a motion passed if there are any negative votes ('''TODO''': document the +1, +0, -0, -1 voting procedure if needed).

'''Q''': Is an IRC gathering a meeting? 
'''A''': The [http://www.osgeo.org/content/foundation/incorporation/bylaws.html bylaws] (section 4.4) say that an electronic medium may be used and an event will constitute a meeting if members can hear one another at the same time. In practice, we often have IRC meetings and then have a vote by voice if there are items that need voting on ('''TODO''': document the convention on email voting if this is an alternative to voice voting).

[[Category: Board]]
[[Category:Committees]]

Board Meeting 2013-09-20

2013-10-17T15:29:37Z

Warmerdam:

This meeting is '''scheduled for the 20th of September 2013''' at [http://www.timeanddate.com/worldclock/fixedtime.html?year=2013&month=9&day=20&hour=6&min=0&sec=0 7am Nottingham Time, 6.00 UTC].

Daniel proposing to hold this meeting face to face in the Cavendish Hall Cafeteria at the Nottingham FOSS4G. (To be confirmed)

Note: Meeting ended up taking place face to face on 2013-09-19 at 6:00pm Nottingham time.

== Agenda ==

'''Mandatory agenda items'''

* roll call
* appoint meeting chair, meeting scribe/secretary
* Review and approve past minutes: [[Board Meeting 2013-08-15]] (reported to next meeting)
* Short introductions for new board members
* Appoint director positions:
** Term durations/limits
** President
** Treasurer
** Secretary
* Appoint Key Liaison Roles:
** Discuss PDX conference team requests/needs + Appoint Board Rep on FOSS4G 2014 Portland LOC
** OSGeo Rep at LocationTech
** OSGeo Rep for OGC MOU (do we currently have one?)
* Annual General Meeting (AGM)
** Anything we need to discuss?
* Finance update
** 501c4 and cleaning up IRS filing, finances, etc.
** Sponsors invoicing for 2013

'''Discussion points if we have time:'''

* Discuss FOSS4G LOC vs OSGeo involvement
** Need to setup processes for managing foss4g
*** Template Contract with PCO
*** Non-profit aspects (taxes vs PCO, extending nonprofit status to LOC, etc.)
*** See email from PDX committee
* Discuss OSGeo vision, mission, objectives, policies updates
** Setup one or more working groups?
** SAC issues
* Discuss OSGeo involvement with partner organizations:
** OGC, LocationTech, OSGeo Sponsors, (others?)
** Need champions for each one?
* ''add your items here''
* Decide on who to report this meeting summary to the Discuss list
* Schedule next meeting

== Minutes ==

* Attending: Jorge Sanz, Daniel Morissette, Jeff McKenna, Bart van den Eijnden, Frank Warmerdam, Anne Ghisla, Jáchym Čepický, Gérald Fenoy

* Presiding: Jeff McKenna

* Scribing: Frank Warmerdam

* Meeting comes to order at 6:00pm, 2013-09-19.

* Review of past minutes deferred to the next meeting.

* MOTION: Daniel Morissette is re-appointed Treasurer. Moved by Frank Warmerdam, carried.

* MOTION: Jáchym Čepický is appointed Secretary. Moved by Jorge Sanz, carried.

* The topic of term limits is discussed but no firm conclusion was arrived at.

* MOTION: Jeff McKenna is re-appointed President. Moved by Daniel Morissette, carried.

* TASK: Jeff is to seek a volunteer to act as board liason to FOSS4G 2014.

* MOTION: The meeting is adjourned. Moved by Jeff McKenna, carried.

[[Category:Board]]
[[Category:Board Meetings 2013]]

OSGeo.org Web Site - 2016 Barn Raising

2013-10-15T21:13:58Z

Warmerdam: /* Background */

'''October 2013 -''' WebCom began investigating migration options for the main Drupal website.

=Prequisites=
* Identify essential functionality within current site

=Requirements=
* Automated migration of content from current site
* Duplicate essential functionality
* Solid multilingual support
* ...

=Software Evaluations=
* [[Drupal 8 Evaluation]]
* Alternatives (e.g. Django)

[[Category: WebCom]]
[[Category:Committees]]

= Background =
* [[Drupal Upgrade Plan]] - Wolf's fall 2007 plan to upgrade Drupal to 5.3.

OSGeo.org Web Site - 2016 Barn Raising

2013-10-15T21:10:58Z

Warmerdam:

'''October 2013 -''' WebCom began investigating migration options for the main Drupal website.

=Prequisites=
* Identify essential functionality within current site

=Requirements=
* Automated migration of content from current site
* Duplicate essential functionality
* Solid multilingual support
* ...

=Software Evaluations=
* [[Drupal 8 Evaluation]]
* Alternatives (e.g. Django)

[[Category: WebCom]]
[[Category:Committees]]

= Background =
* [[2007 Drupal Upgrade Plan]] - Wolf's fall 2007 plan to upgrade Drupal to 5.3.

Website Committee

2013-10-15T21:10:34Z

Warmerdam: add 2013 drupal upgrade in a new location.

This is the main wiki page for the OSGeo Website Committee. Started as per the [[Web Site Committee Motion]] approved by the board at the [[First Board Meeting]].

== Official Site: Comments and access management ==
The official home of the [http://osgeo.org/webcommittee/index.html OSGeo Web Site Committee], includes the member list. If you have questions, want to learn more or feel like you can contribute ('''translations'''!) to the OSGeo main web site please subscribe to the [http://lists.osgeo.org/mailman/listinfo/webcom WebCom mailing list].

'''Update: Oct-Nov 2013 -''' WebCom are currently discussing migration options for the main OSGeo website. Join us on the [http://lists.osgeo.org/mailman/listinfo/webcom WebCom mailing list] and visit the [[Drupal Update 2013]] wiki page.

== Meeting Agendas and Minutes ==

Most recent first...

* May 08, 2008 [[WebCom Meeting 20080508]]
* May 30, 2007 [[WebCom Meeting 20070530]]
* May 09, 2007 [[WebCom Meeting 20070509]]
* May 02, 2007 [[WebCom Meeting 20070502]]
* March 21, 2007 [[WebCom Meeting 20070321]]
* March 07, 2007 [[WebCom Meeting 20070307]]
* February 07, 2007 [[WebCom Meeting 20070207]]
* January 31, 2007 [[WebCom Meeting 20070131]]
* October 25, 2006 [[WebCom Meeting 20061025]]
* October 11, 2006 [[WebCom Meeting 20061011]]
* September 20, 2006 [[WebCom Meeting 20060920]]
* August 30, 2006 [[WebCom Meeting 20060830]]
* August 23, 2006 [[WebCom Meeting 20060823]]
* August 2, 2006 [[WebCom Meeting 20060802]]
* July 19, 2006 [[WebCom Meeting 20060719]]
* July 5, 2006 [[WebCom Meeting 20060705]]
* May 17, 2006 [[WebCom Meeting 20060517]]
* April 5, 2006 [[WebCom Meeting 20060405]]
* March 29, 2006 [[WebCom Meeting 20060329]]
* March 22, 2006 [[WebCom Meeting 20060322]]
* March 15, 2006 [[WebCom Meeting 20060315]]
* March 9, 2006 [[WebCom Meeting 20060309]]

== Other Pages ==
* [[WebCom Scope]] - Collaborative area discussion committee's focus
* [[WebCom OSGeo Site Focus]] - Collaborative area for designing site features, layout, etc. Based on the user focus being determined by VisCom at [[VisComTargets]]
* [[News Queue]] - Notes on the role of News Editor, and how the news items are maintained.
* [[Spotlights]] - About producing developer/project/etc spotlights for website.
* [[Drupal Portal]] - Notes on trasitioning www.osgeo.org to a Drupal based CMS.
* [[Web Migration Map]] - broader discussion of transitioning stuff off CN.
* [[Infrastructure Transition Plan]] - high level transition plan approved by board.
* [[Service Provider Directory]] - proposal for managing a service provider directory
* [http://lists.osgeo.org/mailman/listinfo/webcom WebCom Mailing list]
* [[Spam]] fighting

== Tasks ==

* [[Drupal Update 2013]] - Effort to upgrade to Drupal 8
* WebCom general TODO and specific tasks are tracked at [[WebComTODO]].
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=WebSite&order=priority Open WebCom Issues]
* [http://trac.osgeo.org/osgeo/newticket Submit Trac Ticket] - Remember to set Component to WebSite!

[[Category: WebCom]]
[[Category:Committees]]

Board Meeting 2013-09-20

2013-09-24T02:51:41Z

Warmerdam: /* Minutes */

This meeting is '''scheduled for the 20th of September 2013''' at [http://www.timeanddate.com/worldclock/fixedtime.html?year=2013&month=9&day=20&hour=6&min=0&sec=0 7am Nottingham Time, 6.00 UTC].

Daniel proposing to hold this meeting face to face in the Cavendish Hall Cafeteria at the Nottingham FOSS4G. (To be confirmed)

== Agenda ==

'''Mandatory agenda items'''

* roll call
* appoint meeting chair, meeting scribe/secretary
* Review and approve past minutes: [[Board Meeting 2013-08-15]] (reported to next meeting)
* Short introductions for new board members
* Appoint director positions:
** Term durations/limits
** President
** Treasurer
** Secretary
* Appoint Key Liaison Roles:
** Discuss PDX conference team requests/needs + Appoint Board Rep on FOSS4G 2014 Portland LOC
** OSGeo Rep at LocationTech
** OSGeo Rep for OGC MOU (do we currently have one?)
* Annual General Meeting (AGM)
** Anything we need to discuss?
* Finance update
** 501c4 and cleaning up IRS filing, finances, etc.
** Sponsors invoicing for 2013

'''Discussion points if we have time:'''

* Discuss FOSS4G LOC vs OSGeo involvement
** Need to setup processes for managing foss4g
*** Template Contract with PCO
*** Non-profit aspects (taxes vs PCO, extending nonprofit status to LOC, etc.)
*** See email from PDX committee
* Discuss OSGeo vision, mission, objectives, policies updates
** Setup one or more working groups?
** SAC issues
* Discuss OSGeo involvement with partner organizations:
** OGC, LocationTech, OSGeo Sponsors, (others?)
** Need champions for each one?
* ''add your items here''
* Decide on who to report this meeting summary to the Discuss list
* Schedule next meeting

== Minutes ==

* Attending: Jorge Sanz, Daniel Morissette, Jeff McKenna, Bart van den Eijnden, Frank Warmerdam, Anne Ghisla, Jáchym Čepický, Gérald Fenoy

* Presiding: Jeff McKenna

* Scribing: Frank Warmerdam

* Meeting comes to order at 6:00pm, 2013-09-19.

* Review of past minutes deferred to the next meeting.

* MOTION: Daniel Morissette is re-appointed Treasurer. Moved by Frank Warmerdam, carried.

* MOTION: Jáchym Čepický is appointed Secretary. Moved by Jorge Sanz, carried.

* The topic of term limits is discussed but no firm conclusion was arrived at.

* MOTION: Jeff McKenna is re-appointed President. Moved by Daniel Morissette, carried.

* TASK: Jeff is to seek a volunteer to act as board liason to FOSS4G 2014.

* MOTION: The meeting is adjourned. Mopved by Jeff McKenna, carried.

[[Category:Board]]
[[Category:Board Meetings 2013]]

501c4Announcement

2013-09-12T23:38:43Z

Warmerdam:

OSGeo is pleased to announce that the U.S. Internal Revenue Service (IRS) [http://svn.osgeo.org/osgeo/board/irs_docs/OSGeo-Determination_Letters_c3andc4-20130909.pdf has accepted our application](pdf) for non-profit status under section 501(c)(4) of the tax code. Our 501(c)(4) status declares that we are a [http://www.irs.gov/Charities-&-Non-Profits/Other-Non-Profits/Social-Welfare-Organizations Social Welfare Organization]. This determination affirms OSGeo role in serving the public through our mission focused around Open Source Geospatial software.

This determination helps ensure that the organization will not have pay US federal taxes on money accumulated toward the fullfilment of our mission. Unfortunately, unlike a 501(c)(3) (Charitable) status, this does not allow financial contributors to OSGeo to treat the contributions as a charitable contribution which can have a tax benefit for US tax payers. There should still be no problem with commercial organizations treating contributions to OSGeo as a business expense.

OSGeo owes a special debt to past Executive Director Tyler Mitchell, and current Treasurer Daniel Morissette who have carried this process to a successful conclusion after several years of work.

501c4Announcement

2013-09-12T23:36:31Z

Warmerdam: Created page with "OSGeo is pleased to announce that the U.S. Internal Revenue Service (IRS) [http://svn.osgeo.org/osgeo/board/irs_docs/OSGeo-Determination_Letters_c3andc4-20130909.pdf has accepted..."

OSGeo is pleased to announce that the U.S. Internal Revenue Service (IRS) [http://svn.osgeo.org/osgeo/board/irs_docs/OSGeo-Determination_Letters_c3andc4-20130909.pdf has accepted our application](pdf) for non-profit status under section 501(c)(4) of the tax code. Our 501(c)(4) status declares that we are a [http://www.irs.gov/Charities-&-Non-Profits/Other-Non-Profits/Social-Welfare-Organizations Social Welfare Organization]. This determination affirms OSGeo role in serving the public through our mission focused around Open Source Geospatial software.

This determination helps ensure that the organization will not have pay US federal taxes on money accumulated toward the fullfilment of our mission. Unfortunately, unlike a 501(c)(3) (Charitable) status, this does not allow financial contributors to OSGeo to treat the contributions as a charitable contribution which can have a tax benefit for US tax payers. There should still be no problem with commercial organizations treating contributions to OSGeo as a business expense.

OSGeo owes a special debt to Tyler Mitchell, and Daniel Morissette who have carried this process to a successful conclusion after several years of work.

SAC:Mailing Lists

2013-09-11T23:21:01Z

Warmerdam: /* System Tasks */ move item into separate topic that seems to be unrelated to renaming lists.

Mailing lists are administered with Mailman on the virtual host lists.osgeo.org. Physically this is the "Mail" VM running on osgeo4. Frank Warmerdam (warmerdam) and Alan Boudreault (aboudreault) do most of the mailman work.

= Notes for List Administrators =

== Requesting a new list ==

If your project or activity would like to have a mailing list at lists.osgeo.org please take the following steps:

* First, confirm that there isn't already an appropriate list for this activity, and consider whether OSGeo is the right home for the proposed list.
* File a ticket at http://trac.osgeo.org/osgeo (use your OSGeo Userid to login) and make sure the component is set to "SAC". This is the request to the System Administration Committee to create the list.
* Please include the exact name you would like for the list (ie. foo-announce), and the email address of the person who should be the list admin. Also provide the justification for the list, and indicate if it was explicitly requested by an OSGeo Project PSC or project representative.
* Include any special instructions (such pointers to info if the list is actually being migrated from elsewhere).
* Hopefully, someone in SAC will act on the ticket and create the list. When complete the ticket will be updated and closed, and the proposed admin will receive an email with the admin password for the list.
* Review the list settings, in particular ensuring that the short description gets set (ie. review following points)

Generally it is up to the mailman administrator to judge whether a list is justified for creation. The justification doesn't need to be strong, but the list should be OSGeo related, reasonably likely to generate some use, or be requested on behalf of a project.

== All lists ==

* Please set "A terse phrase identifying this list." to something brief and meaningful as this is what is shown on the main lists directory. It is on the ''General'' tab.
* Set "Who can view subscription list?" on the ''Privacy'' tab to "List Admin Only", otherwise anyone can subscribe and then harvest the mailing list.
* Set ''generic_nonmember_action'' on the ''Privacy->Sender filters'' tab to reject as most lists are not actively administered so we prefer to reject rather than holding posts from unsubscribed folks.
* Ensure the "Prefix for subject line of list postings." on the ''General'' tab is set to something meaningful. If the list name is generic (such as "announce") it may be helpful to prefix it with OSGeo-, eg. "[OSGeo-Announce]"
* Be sure to choose a name that does not already have an existing alias, such as: sales, support, www, security. If you need to use one of these names someone will have to edit the /etc/aliases file for you manually.

== Other options ==

* For announce lists (ie. moderated lists) turn on "Emergency moderation of all list traffic" on. It is on the ''General'' tab.

= Outstanding Issues =

# Administrator/moderator permissions. Currently this is a hodgepodge. Some administrators have set the passwords but then others can't help administrate the list. The default admin password is not very secure. It has been suggested that we use some sort of LDAP/http authentication to verify that folks trying to do list admin are in some sort of mail administration group.
# List setting policies. Do we want to mandate more policies than the ones listed above as "Notes for List Administrators"?
# Search. Do we want to do anything special to enable searching the archive? Jason has setup an OSGeo.org grouping on nabble (<strike>http://www.nabble.com/OSGeo.org-f18127.html</strike>, http://osgeo-org.1803224.n2.nabble.com/) that makes searching all osgeo related mailing lists effective. We might want to expand on that.

= System Tasks =

== New Lists ==

* Create a new list through the [http://lists.osgeo.org/mailman/create web admin login].

== Renaming Lists ==

* create new list
$sudo /usr/lib/mailman/bin/newlist listname admins@email lists_passwd
* move original lists archive to newlists archive location
$ sudo cp /var/lib/mailman/archives/private/oldlist.mbox/oldlist.mbox \
/var/lib/mailman/archives/private/newlist.mbox/
* create archive
$ sudo /usr/lib/mailman/bin/arch --wipe newlist
* export subscribers from old list regular and digest members
$ sudo /usr/lib/mailman/bin/list_members -r oldlistname > listname-regular.txt
$ sudo /usr/lib/mailman/bin/list_members -d oldlistname > listname-digest.txt
* import subscribers into new list
$ sudo /usr/lib/mailman/bin/add_members --regular-members=listname-regular.txt --welcome-msg=y newlistname
$ sudo /usr/lib/mailman/bin/add_members --digest-members=listname-digest.txt --welcome-msg=y newlistname
* remove old list
$ sudo /usr/lib/mailman/bin/rmlist oldlistname
* update aliases and check that proper permissions are set
$ sudo /usr/lib/mailman/bin/genaliases
$ sudo /usr/lib/mailman/bin/check_perms -f
* edit postfix aliases - /etc/aliases
oldlist: newlist@lists.osgeo.org
oldlist-request: newlist-request@lists.osgeo.org
oldlist-admin: newlist-admin@lists.osgeo.org
oldlist-owner: newlist-owner@lists.osgeo.org
* update postfix with new aliases
$ sudo /usr/bin/newaliases
$ sudo /usr/sbin/service postfix reload

== copy / clone user addresses across lists ==
* add '''-r''' to remove the old address
$ sudo clone_member old@address.com new@address.com

== Migrate ==

When migrating from another system to osgeo, get the .mbox files, and the whole /var/lib/mailman/lists/<listname> directory, and follow roughly the following steps as root (or sudo each step):

# newlist -q grass-announce warmerdam@pobox.com junk
# cd /var/lib/mailman/lists/grass-announce
# cp ~warmerdam/grass-announce/* .
# withlist -l -r fix_url grass-announce
# /usr/lib/mailman/bin/arch grass-announce ~warmerdam/grass-announce.mbox
# chown -R mailman.mailman /var/lib/mailman/lists/grass-announce
# chown -R mailman.mailman /var/lib/mailman/archives/private/grass-announce*
# genaliases
# /usr/sbin/service postfix restart
# mailmanctl restart

If the list name on the new system is different than on the old system, it may be prudent to fix this up on the mail page of the web admin interface after the ''withlist'' command has been used, and before the archives are imported. (''FrankW'')

== References ==
* Here is [http://www.chris-lamb.co.uk/2007/10/02/renaming-a-mailman-list/ another approach to renaming], though our web admin interface won't actually allow you to do the final rename step

== Remove Mails from Archive ==
Sometimes users send mails with contentious content to the list and ask for it to be removed. As a courtesy this should be done asap. In general it is better to not remove the mail altogether but just remove the content. Instructions:
* http://wiki.list.org/pages/viewpage.action?pageId=4030681
Archives live in:
/var/lib/mailman/archives/
To recreate archives use:
/usr/lib/mailman/bin/arch [listname]

== List Statistics ==

From time to time it is nice to get a sense of the number of lists, users, etc. The following may be helpful:

all subscribers of all osgeo lists hosted on osgeo.org:

sudo list_lists -b | xargs -n 1 sudo list_members | wc -l

unique list of email addresses across all lists:

sudo list_lists -b | xargs -n 1 sudo list_members | sort | uniq | wc -l

Note: since 2009 there is [[User:Neteler|Markus Neteler]]'s cronjob running for gathering these statistics and sending them to "info AT osgeo org". For a time series, [[VisibilityStats#Mailing_list_subscribers|see statistics]]

= Nabble =

There are a variety of web forum oriented interfaces for mailing lists that can be connected to existing mailing lists. One of the most widely used is Nabble and OSGeo makes an effort to provide some administrative support for it.

The Nabble liasons for OSGeo are [[Jorge Sanz]] with [[Mateusz Loskot]] as a backup.

Technical details to follow.

[[Category:Infrastructure]]

SAC:Mailing Lists

2013-09-11T23:19:10Z

Warmerdam: /sbin/service is now /usr/sbin/service

Mailing lists are administered with Mailman on the virtual host lists.osgeo.org. Physically this is the "Mail" VM running on osgeo4. Frank Warmerdam (warmerdam) and Alan Boudreault (aboudreault) do most of the mailman work.

= Notes for List Administrators =

== Requesting a new list ==

If your project or activity would like to have a mailing list at lists.osgeo.org please take the following steps:

* First, confirm that there isn't already an appropriate list for this activity, and consider whether OSGeo is the right home for the proposed list.
* File a ticket at http://trac.osgeo.org/osgeo (use your OSGeo Userid to login) and make sure the component is set to "SAC". This is the request to the System Administration Committee to create the list.
* Please include the exact name you would like for the list (ie. foo-announce), and the email address of the person who should be the list admin. Also provide the justification for the list, and indicate if it was explicitly requested by an OSGeo Project PSC or project representative.
* Include any special instructions (such pointers to info if the list is actually being migrated from elsewhere).
* Hopefully, someone in SAC will act on the ticket and create the list. When complete the ticket will be updated and closed, and the proposed admin will receive an email with the admin password for the list.
* Review the list settings, in particular ensuring that the short description gets set (ie. review following points)

Generally it is up to the mailman administrator to judge whether a list is justified for creation. The justification doesn't need to be strong, but the list should be OSGeo related, reasonably likely to generate some use, or be requested on behalf of a project.

== All lists ==

* Please set "A terse phrase identifying this list." to something brief and meaningful as this is what is shown on the main lists directory. It is on the ''General'' tab.
* Set "Who can view subscription list?" on the ''Privacy'' tab to "List Admin Only", otherwise anyone can subscribe and then harvest the mailing list.
* Set ''generic_nonmember_action'' on the ''Privacy->Sender filters'' tab to reject as most lists are not actively administered so we prefer to reject rather than holding posts from unsubscribed folks.
* Ensure the "Prefix for subject line of list postings." on the ''General'' tab is set to something meaningful. If the list name is generic (such as "announce") it may be helpful to prefix it with OSGeo-, eg. "[OSGeo-Announce]"
* Be sure to choose a name that does not already have an existing alias, such as: sales, support, www, security. If you need to use one of these names someone will have to edit the /etc/aliases file for you manually.

== Other options ==

* For announce lists (ie. moderated lists) turn on "Emergency moderation of all list traffic" on. It is on the ''General'' tab.

= Outstanding Issues =

# Administrator/moderator permissions. Currently this is a hodgepodge. Some administrators have set the passwords but then others can't help administrate the list. The default admin password is not very secure. It has been suggested that we use some sort of LDAP/http authentication to verify that folks trying to do list admin are in some sort of mail administration group.
# List setting policies. Do we want to mandate more policies than the ones listed above as "Notes for List Administrators"?
# Search. Do we want to do anything special to enable searching the archive? Jason has setup an OSGeo.org grouping on nabble (<strike>http://www.nabble.com/OSGeo.org-f18127.html</strike>, http://osgeo-org.1803224.n2.nabble.com/) that makes searching all osgeo related mailing lists effective. We might want to expand on that.

= System Tasks =

== New Lists ==

* Create a new list through the [http://lists.osgeo.org/mailman/create web admin login].

== Renaming Lists ==

* create new list
$sudo /usr/lib/mailman/bin/newlist listname admins@email lists_passwd
* move original lists archive to newlists archive location
$ sudo cp /var/lib/mailman/archives/private/oldlist.mbox/oldlist.mbox \
/var/lib/mailman/archives/private/newlist.mbox/
* create archive
$ sudo /usr/lib/mailman/bin/arch --wipe newlist
* export subscribers from old list regular and digest members
$ sudo /usr/lib/mailman/bin/list_members -r oldlistname > listname-regular.txt
$ sudo /usr/lib/mailman/bin/list_members -d oldlistname > listname-digest.txt
* import subscribers into new list
$ sudo /usr/lib/mailman/bin/add_members --regular-members=listname-regular.txt --welcome-msg=y newlistname
$ sudo /usr/lib/mailman/bin/add_members --digest-members=listname-digest.txt --welcome-msg=y newlistname
* remove old list
$ sudo /usr/lib/mailman/bin/rmlist oldlistname
* update aliases and check that proper permissions are set
$ sudo /usr/lib/mailman/bin/genaliases
$ sudo /usr/lib/mailman/bin/check_perms -f
* edit postfix aliases - /etc/aliases
oldlist: newlist@lists.osgeo.org
oldlist-request: newlist-request@lists.osgeo.org
oldlist-admin: newlist-admin@lists.osgeo.org
oldlist-owner: newlist-owner@lists.osgeo.org
* update postfix with new aliases
$ sudo /usr/bin/newaliases
$ sudo /usr/sbin/service postfix reload
* copy / clone user addresses across lists:
** add '''-r''' to remove the old address
$ sudo clone_member old@address.com new@address.com

== Migrate ==

When migrating from another system to osgeo, get the .mbox files, and the whole /var/lib/mailman/lists/<listname> directory, and follow roughly the following steps as root (or sudo each step):

# newlist -q grass-announce warmerdam@pobox.com junk
# cd /var/lib/mailman/lists/grass-announce
# cp ~warmerdam/grass-announce/* .
# withlist -l -r fix_url grass-announce
# /usr/lib/mailman/bin/arch grass-announce ~warmerdam/grass-announce.mbox
# chown -R mailman.mailman /var/lib/mailman/lists/grass-announce
# chown -R mailman.mailman /var/lib/mailman/archives/private/grass-announce*
# genaliases
# /usr/sbin/service postfix restart
# mailmanctl restart

If the list name on the new system is different than on the old system, it may be prudent to fix this up on the mail page of the web admin interface after the ''withlist'' command has been used, and before the archives are imported. (''FrankW'')

== References ==
* Here is [http://www.chris-lamb.co.uk/2007/10/02/renaming-a-mailman-list/ another approach to renaming], though our web admin interface won't actually allow you to do the final rename step

== Remove Mails from Archive ==
Sometimes users send mails with contentious content to the list and ask for it to be removed. As a courtesy this should be done asap. In general it is better to not remove the mail altogether but just remove the content. Instructions:
* http://wiki.list.org/pages/viewpage.action?pageId=4030681
Archives live in:
/var/lib/mailman/archives/
To recreate archives use:
/usr/lib/mailman/bin/arch [listname]

== List Statistics ==

From time to time it is nice to get a sense of the number of lists, users, etc. The following may be helpful:

all subscribers of all osgeo lists hosted on osgeo.org:

sudo list_lists -b | xargs -n 1 sudo list_members | wc -l

unique list of email addresses across all lists:

sudo list_lists -b | xargs -n 1 sudo list_members | sort | uniq | wc -l

Note: since 2009 there is [[User:Neteler|Markus Neteler]]'s cronjob running for gathering these statistics and sending them to "info AT osgeo org". For a time series, [[VisibilityStats#Mailing_list_subscribers|see statistics]]

= Nabble =

There are a variety of web forum oriented interfaces for mailing lists that can be connected to existing mailing lists. One of the most widely used is Nabble and OSGeo makes an effort to provide some administrative support for it.

The Nabble liasons for OSGeo are [[Jorge Sanz]] with [[Mateusz Loskot]] as a backup.

Technical details to follow.

[[Category:Infrastructure]]

FOSS4G 2013 Code Sprint

2013-09-10T18:02:53Z

Warmerdam: /* GDAL/OGR */

== Code Sprint - what's that? ==

A code sprint is about getting a group together to work on Open Source software, sitting around a table and sharing ideas. It's not just about writing code, as you know a project has many needs including documentation, testing, and providing feedback. What a better way to give feedback and give back to the project that you love than to spend a day with the project's developers. There are roles needed to be filled, no matter what your expertise.

With such a short timeframe (one day) you should probably use this page to set a specific goal for your project. But don't worry, if all you get done is actually sitting at the same table with the project's developers and talking about the next release, that is also great :)

== Where & When ==

[http://www.openstreetmap.org/?lat=52.938804&lon=-1.203427&zoom=18&layers=M East Midlands Conference Centre, Nottingham, UK].

The day after the main conference (Sunday 22nd September) has been set aside for the Code Sprint. There is also a plan to provide facilities throughout the event in the main venue.

We also have a hackathon running on 17th & 18th September which is also free to attend. See the [http://2013.foss4g.org/geohack/ geohack pages] for details.

== What to Bring ==

== How to get there ==

TBD

== Sponsor ==

== Questions/Comments/Ideas ==

*ask on the foss4g2013 mailing list ([http://lists.osgeo.org/mailman/listinfo/foss4g2013 subscribe])

== Additional Interested People ==

The following people are potentially interested in participating in sprinting activities though have not yet established a Workgroup.

*name:project

= Workgroups =

To participate, copy a project skeleton and start a section below for your project.

== Project-name ==

'''Attending:'''

*user
*user

'''Goals:'''

*your goals

 

== OpenLayers 3 ==

Please note: the OpenLayers 3 sprint is taking place on Wednesday 18th in room: Humanities A3

'''Attending:'''

* Tim Schaub
* Bart van den Eijnden
* Julien-Samuel Lacroix
* Jachym Cepicky

'''Goals:'''

* The OpenLayers 3 sprint will begin with a presentation and background

 

== GeoTools ==

'''Attending:'''

*[[User:Ianturton|Ian Turton]]
*user

'''Goals:'''

* Dependency audit / cleanup
** Look at replacing JDOM with DOM as it is only used internally
** Replace vecmath to avoid Java 3D dependency
** Consider replacing Apache Commons Collections with Guava (if Gabriel still is interested)
** Replace or inline JSR-275 unit classes

== GeoServer ==

'''Attending:'''

*[[User:fgdrf|Frank Gasdorf]]
*[[User:ianturton|Ian Turton]]

'''Goals:'''

* TBD

'''Tracker:'''
https://jira.codehaus.org/browse/GEOS

'''Repository:'''
TBD
 

'''Goals:'''
TBD

'''Possibles:'''
* separate i18n as standalone *_nl* jars to keep translations separated from core code base
* add new developer docs how to synch translations to/from [https://www.transifex.com/projects/p/geoserver_23x/ Transifex]

== uDIG ==

The uDIG (user-fiedly Desktop Internet GIS) is moving from Refractions to LocationTech.org (an Eclipse Industry Working Group for location aware software). The initial IP review of the uDig codebase is complete and we are in position for our initial code contribution.

'''Attending:'''

*[[User:fgdrf|Frank Gasdorf]]
*[[User:moovida|Andrea Antonello]]
*[[User:silli|Silvia Franceschi]]

'''Goals:'''

* Initial Code contribution
** Refactor from net.refractions.udig to org.locationtech.udig
** Update headers
** Update about.html files
* Clean up after IP review
** Migrate to GeoTools 9.0-M1 (a new milestone with several IP issues resolved)
** Temporarily disable features from the product (for example that depend on antlr 2.7.7)
* Make it look pretty
** Update target platform to Eclipse Kepler for a new look and feel
** Update branding for splash screen and about dialog

'''Tracker:'''
https://locationtech.org/bugs/

'''Repository:'''
TBD
 

== MapServer ==

'''Attending:'''

*[[User:Dmorissette|Daniel Morissette]]
*[[Jeff McKenna]] : documentation
*[[User:szekerest|Tamas Szekeres]]
*[[User:yjacolin|Yves Jacolin]] : documentation/translation

'''Goals:'''

*TBD

== GDAL/OGR ==

'''Attending:'''

*[[User:rouault|Even Rouault]]
*[[User:szekerest|Tamas Szekeres]]
*[[User:yjacolin|Yves Jacolin]] : documentation translation
*[[User:warmerda|Frank Warmerdam]]

'''Goals:'''

*TBD

 

[[Category:FOSS4G2013]] [[Category:FOSS4G]] [[Category:Code_Sprints]]

Open Geospatial Consortium

2013-05-30T17:40:41Z

Warmerdam: /* Joint OSGeo and OGC Activities */ add membership link.

''Open Geospatial Consortium, Inc. (OGC) and OSGeo are distinctive organizations with individual goals and visions. This page describes the OGC, an organization dedicated to developing [[Standards]] for the geospatial realm.

== Joint OSGeo and OGC Activities ==
OGC and OSGeo support each other at conferences and other public events. This collaboration has taken publicly visible forms in several activities and documents:
* In December 2008 OSGeo and the OGC have signed a '''[[OSGeo signs Memorandum of Understanding with OGC | Memorandum of Understanding]]''' to coordinate in advancing open geospatial standards (OGC's mission) and Open Source geospatial software and data (OSGeo's mission) under which some [[OGC membership]]s are available.
* OGC organized the [http://www.opengeospatial.org/pressroom/pressreleases/1046 Climate Challenge Integration Plugfest] at [[FOSS4G 2009]] in Sydney focusing on Climate Change
* In May 2011 OSGeo and OGC published a White Paper on the use of the term Open in [[Open Source and Open Standards]].
* The [http://inspire.jrc.ec.europa.eu/events/conferences/inspire_2011/?page=workshop Geospatial SDI Workshop] at the INSPIRE conference 2011 in Edinburgh

[[Image:Ogc logo.png|thumb|144px|right|OGC Logo]]

== About OGC ==
'' From http://www.opengeospatial.org/ogc:''

The Open Geospatial Consortium, Inc (OGC) is an international industry consortium of 346 companies, government agencies and universities participating in a consensus process to develop publicly available interface specifications. [http://www.opengeospatial.org/standards/ OpenGIS® Specifications] support [http://www.opengeospatial.org/resource/faq/openness/#10 interoperable] solutions that "geo-enable" the Web, wireless and location-based services, and mainstream IT. The specifications empower technology developers to make complex spatial information and services accessible and useful with all kinds of applications.

== Vision ==
''From: http://www.opengeospatial.org/ogc/vision''

Realization of the full societal, economic and scientific benefits of integrating electronic location resources into commercial and institutional processes worldwide.

== Mission ==
To serve as a global forum for the collaboration of developers and users of spatial data products and services, and to advance the development of international standards for geospatial interoperability.
Strategic Goals:

: Goal 1 - Provide free and openly available standards to the market, tangible value to Members, and measurable benefits to users.
: Goal 2 - Lead worldwide in the creation and establishment of standards that allow geospatial content and services to be seamlessly integrated into business and civic processes, the spatial web and enterprise computing.
: Goal 3 - Facilitate the adoption of open, spatially enabled reference architectures in enterprise environments worldwide.
: Goal 4 - Advance standards in support of the formation of new and innovative markets and applications for geospatial technologies.
: Goal 5 - Accelerate market assimilation of interoperability research through collaborative consortium processes.

== History ==
The early history of the OGC is closely related to the Open Source software [[GRASS]]. Read more on the OGC website at: http://www.opengeospatial.org/ogc/history.

[[Image:From GRASS to OGC.png|500px|From GRASS to OGC time line]]

== Sites ==
The OGC operates several web sites, portals and Wikis, each with specific access regulations:
* The main web site http://www.opengeospatial.org/ gives access to all public standards.
* Internal documents can be accessed by members through the portal http://portal.opengeospatial.org/ after authentication.
* On the inside the OGC is structured into Standard Working Groups (SWG) and Domain Working Groups (DWG). Members of the OGC can opt into SWG to contribute to the work. Due to patent regulations the work in the SWG is limited to members of the group. Before a standard becomes official it is openly published for a period of comments.
* OGC Network http://www.ogcnetwork.net/ is an outward facing portal where information from Technical Committee Meetings is published for non-members. As a service to OSGeo we will provide more information on the [[OGC News]] page.
* [http://cite.opengeospatial.org/ Compliance & Interoperability Testing & Evaluation Initiative]
* All [http://cite.opengeospatial.org/reference OGC reference implementations] are based on Open Source Software,
** [[GeoNetwork]] opensource (Graduated OSGeo Project)
** [[deegree]] (Graduated OSGeo Project)
** [http://www.geoserver.org GeoServer] (currently in OSGeo Incubator)

[[Category: OGC]]
[[Category: Standards]]
[[Category:MoU]]

Google Summer of Code 2013 Ideas

2013-03-28T21:59:22Z

Warmerdam: /* The ideas pages */ add gdal

[[Image:Gsoc-2013-logo-color.jpg|350px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]

-----
* Back to the main OSGeo [[Google Summer of Code 2013]] wiki page.

* See also ideas from [[Google Summer of Code 2010 Ideas|2010]], [[Google Summer of Code 2011 Ideas|2011]], and [[Google Summer of Code 2012 Ideas|2012]].
-----

== OSGeo Google Summer of Code 2013 ==

The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.

These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders; show us what you've got.

* '''If you need more information on how to apply you can contact all the mentoring organisations via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])

* There is a [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers Google SoC flyer] to look at and post in appropriate places and [http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/ an OSGeo flavoured one as well] (TODO: update to 2013).

* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.

== Important dates ==

* [http://www.google-melange.com/gsoc/events/google/gsoc2013 '''The official timeline''']

* April 8: Google announces accepted organizations.
: If OSGeo is accepted as an organization for Google Summer of Code, '''start talking to us earlier rather than later.'''
* April 22: '''Student applications open.
: The earlier you start the more probable it is that you will be accepted!'''
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''
* May 3: '''Student application deadline.'''
* May 27: Accepted student proposals are announced and Community Bonding Period begins
* June 17: '''Coding begins!'''
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')
* July 29: Mid-term evaluation begins
* September 16-23: '''Pencils down!'''
* September 23-27: Final evaluations
* September 27: Students begin submitting required code samples to Google
* October 1: Final results announced

== The ideas pages ==
'''''[Check back often, it's a work in progress]'''''

Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:

* [http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2013 '''GRASS GIS''' SoC Ideas]: GRASS GIS is an open source GIS focusing mainly on analysis. It is written as a collection of stand-alone C programs and has a new GUI written in wxPython. If you know Python, or want to implement algorithms in C take a look!

* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2013 '''Quantum GIS''' SoC Ideas] Quantum GIS (QGIS) is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.

* [http://trac.osgeo.org/ossim/wiki/GSoC_2013_Ideas '''OSSIM''' SoC Ideas]: - OSSIM is a powerful suite of geospatial libraries and applications used to process imagery, maps, terrain, and vector data. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.

* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code '''uDig''' SoC Ideas]: User-friendly Desktop GIS is a Java application written with the Eclipse RCP framework. The project has a community svn area to host student plug-ins, tutorials cover how to package up a custom application to show off your work.

* [[GvSIG_GSoC_2013_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.org/web/projects/gvsig-desktop/description2/view?set_language=en Desktop], [http://www.gvsig.org/web/projects/gvsig-mobile/description-2/view?set_language=en PDAs], and [http://gvsigmini.org mobile phones]. The gvSIG project looks for students with Java skills that want to develop new ideas on any of these products.

* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: Opticks is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.

* [http://trac.osgeo.org/geos/wiki/GSoC '''GEOS''' Ideas]: GEOS (Geometry Engine - Open Source) is a C++ port of the JTS Topology Suite (JTS). It includes the OpenGIS Simple Features for SQL spatial predicate functions and spatial operators, as well as specific JTS enhanced topology functions.

* [http://live.osgeo.org/en/overview/geoserver_overview.html '''Geoserver'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desk top GIS programs. This means that you can store your spatial data in almost any format you prefer but that your users do not need to know anything about GIS data. At the simplest level all they need is a web browser to see your maps exactly as you want. GeoServer is the reference implementation of the Open Geospatial Consortium (OGC) Web Feature Service (WFS) and Web Coverage Service (WCS) standards, as well as a high performance certified compliant Web Map Service (WMS).
:* ''Geoserver will accept one idea, according to the developers' availability. Please contact them to get more information.''

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: GDAL is a C++ library for reading and writing geospatial data raster and vector formats.

We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/zoo-project_overview.html ZOO-Project], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE]...

Guest project:

* [https://code.google.com/p/istsos/wiki/GSoC_ideas '''istSOS''' Ideas]: [http://code.google.com/p/istsos/ istSOS] (Istituto Scienze della Terra Sensor Observation Service) is an implementation of the Sensor Observation Service (SOS) standard from the Open Geospatial Consortium (OGC). The development of istSOS was started in 2009 in order to provide a simple implementation of the SOS standard for the management, provision and integration of hydro-meteorological data collected in Canton Ticino (Switzerland). istSOS is entirely written in Python.

Guest students (accepted under OSGeo umbrella):

* [https://github.com/mapnik/mapnik/wiki/GSOC-Ideas '''Mapnik''' Ideas] [http://mapnik.org/ Mapnik] is a Free Toolkit for developing mapping applications. It’s written in C++ and there are Python bindings to facilitate fast-paced agile development. It can comfortably be used for both desktop and web development, which was something I wanted from the beginning.
:* ''Mapnik students will be required to apply under OSGeo or OpenStreetMap umbrella, according to the main topic of their project.''

== Which project do I choose? ==

Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.
: View the documents and download the ISO from http://live.osgeo.org

== How to get in contact via mailing lists ==

Since OSGeo is an umbrella organisation for multiple projects, each project has their own discussion and development mailing lists.

'''Main OSGeo mailing lists of interest to students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc)
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)

Also see the [[Mailing Lists]] page for project specific lists, as well as the longer list at http://lists.osgeo.org.

== How to get in contact via IRC ==

Primary channel:

* irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client], [http://webchat.freenode.net alternative])

GSoC @ OSGeo inter-project discussions:

* irc://irc.freenode.net/#osgeo-soc

Project irc channels:

* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#gvsig
* irc://irc.freenode.net/#mapbuilder
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapnik
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#opticks
* irc://irc.freenode.net/#ossimplanet
* irc://irc.freenode.net/#pgrouting-project
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig

== Application questions we'll ask you ==
'''''[Provisional]'''''

* All questions must be answered, ''no exceptions''. Treat this as something between a formal job application and a scholarship application, because that's exactly what it is.

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of
the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan ('''detailed timeline''': how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member
project and more generally the OSGeo Foundation as a whole:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you
could write a program in, hardware, networking experience, etc.)

Please provide details of previous GIS experience:

Please provide details of any previous involvement with
GIS programming and other software programming:

Please tell us why you are interested in GIS and open
source software:

Please tell us why you are interested in working for OSGeo
and the software project you have selected:

Please tell us why you are interested in your specific
coding project:

Would your application contribute to your ongoing studies/
degree? If so, how?

Please explain how you intend to continue being an active
member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent
to a full-time paid summer internship or summer job?

Do you have any known time conflicts during the official coding
period? (June 17 to Sept. 27)

== What to expect during the summer ==

* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you: [http://google-opensource.blogspot.com/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code] -- READ THIS eBOOK

=== Be prepared to be in constant communication with your mentors and project ===

You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to integrate you into the developer community, so you should get involved with them from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you in case of problems, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== Weekly reports ===

Yes, every week we expect to see a report posted to the soc@osgeo mailing list that at least answers the following questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)

If you want, feel free to write *more*. But three sentences is the bare minimum. *IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME*, if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you in IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's cool. We have all studied at some point, just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

Last year this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

=== Wiki page and blogs ===

In addition to weekly reports we require you to maintain a wiki or blog page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this.

We hope to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

[Back to [[Google Summer of Code 2013]] @ OSGeo]
[[Category: Google Summer of Code]]

ProjectsVM

2013-03-22T21:10:53Z

Warmerdam:

The Projects VM is a Debian virtual machine minimally administered by [[SAC]], hosted on [[Infrastructure Transition Plan 2010#New_Hardware|osgeo4]] at OSU OSL and used for hosting project web sites and some related services.

The VM is reachable by ssh at projects.osgeo.osuosl.org. Anyone in the https://www.osgeo.org/cgi-bin/auth/ldap_shell.py has ssh access, and anyone in this group can add new people via the link. Sudo access can be provided by existing sudoer's by adding folks to the sudoers group in /etc/group, though it is normal practice to try and only extend sudo access to one user per project.

This VM hosts several '''project critical resources''' (projects web sites primarily). It is a shared environment and it is important that folks making changes on the system be aware of the impact they might have on other hosted services. Apache changes should be made carefully and needfully.

Place to reach SAC members in case of troubles or quick questions:

*irc://irc.freenode.org#osgeo
*irc://irc.freenode.org#telascience
*If you don't have an IRC client, you can use the [http://irc.telascience.org/cgi-bin/telascience-irc.cgi IRC Web browser interface] or [http://webchat.freenode.net/ Freenode's Webchat] (if you are behind a restrictive firewall)

;Existing services hosted on the Projects VM:

{| border="1" class="wikitable"
|-
! site
! path
! contact
! [[SAC:Backups|backup]]
! comments
|-
| <s>2010.foss4g.org</s>
| <s>/osgeo/foss4g/2010</s>
| admined by frank/lorenzo?</s>
| ?
| moved to webextra
|-
| demo.geotools.org
| /osgeo/geotools
| admined by jdeolive/jgarnett
| ?
|
|-
| geos.org
| /osgeo/geos
| admined by pramsey
| ?
|
|-
| geotools.org
| /osgeo/geotools
| admined by jdeolive/jgarnett
| ?
|
|-
| grass.osgeo.org
| /osgeo/grass
| admined by neteler/martinl/hamish
| random site copies to http://gis.cri.fmach.it
| own mediawiki
|-
|rowspan="2"| mapserver.org
| /osgeo/mapserver.org
| admined by hobu/jmckenna
| ?
|
|-
| /osgeo/mapserver
| admined by dmorissette, used for [http://trac.osgeo.org/mapserver/wiki/MapServerReleasePackagingHowTo release packaging]
| ?
|
|-
| openlayers.osgeo.org
| /osgeo/openlayers
| admined by crschmidt
| ?
|
|-
| projects.mapbender.osgeo.org
| /osgeo/mapbender
| admined by astrid_emde/christoph/uli have a look at [[Mapbender at ProjectsVM]]
| ?
|
|-
| spatialreference.org
| /osgeo/sr-org
| warmerdam ([http://trac.osgeo.org/metacrs/wiki/SpatialReferenceOrg Trac])
| Not yet
|
|-
| tilecache.org
| /osgeo/tilecache
| admined by crschmidt
| ?
|
|-
| www.gdal.org
| /osgeo/gdal
| admined by FrankW
| ?
|
|-
| www.remotesensing.org
| /osgeo/remotesensing.org
| admined by FrankW
| ?
|
|-
| www.pycsw.org
| /osgeo/pycsw
| admined by kalxas, tomkralidis
| ?
|
|-
|}

=== Backup strategy ===

There is none :( Amazing. See also column above.

[[Category:Infrastructure]]
[[Category:MapServer]]

Spatialreference.org

2013-03-22T21:05:54Z

Warmerdam:

'''Current info at http://trac.osgeo.org/metacrs/wiki/SpatialReferenceOrg - The following is deprecated and likely out of date.'''

----

Currently runs under gunicorn wsgi server proxied through apache.
* Proxy /etc/apache/site-available/sr.org.conf
* Service can be controlled via /etc/init.d/gunicorn
* Configuration file /etc/gunicorn.d/sr.gunicorn (
** Port 8092
** workers=4 (Can be modified, gunicorn recommends 2-4x # of cores (which is 4), but I lowered it to see if it plays better with the existing services.)
* Gunicorn is installed via backports

''The notes below are for the previous method which is still installed but currently disabled:''
SR.org lives on its own apache server to prevent it going down and taking out the rest of the projects VM. To fix it:

* cat /var/run/srorgapache.pid for a PID File, and check that that pid is an apache2 file running with the srorg config (using grep).
* Kill this process.
* Run /etc/init.d/srorgapache start

This weird process is a side effect of how the srorgapache init.d script is written; because it is the same process name (apache2), the apache init script will kill the main projects VM if you just run restart.

The server runs on port 8090; it takes about one minute to become available after the server is started. You can access it directly at http://spatialreference.org:8090, and http://spatialreference.org is proxied through the main apache.

WebExtraVM

2013-03-21T21:13:23Z

Warmerdam: /* vmap0.tiles.osgeo.org */

The Web Extra VM is a Debian virtual machine administered by [[SAC]], hosted on OSGeo3 at OSU OSL and used for hosting web sites and services that are directly the responsibility of SAC and that don't fit on the other more special purpose VMs (ie. TracSVN, or Drupal). OSGeo member/project services that SAC isn't willing to take direct responsibility for likely belong on either the [[ProjectsVM]] or the [[AdhocVM]].

The VM is reachable by ssh at webextra.osgeo.osuosl.org. Anyone in the https://www.osgeo.org/cgi-bin/auth/ldap_shell.py?group=sac (SAC) list has ssh access, and anyone in this group can add new people via the link.

== Existing Services on Web Extra VM ==

=== mum03.mapserver.org ===

* /osgeo/foss4g/mum2003-web
* Admined by FrankW
* static html historial site
* Backup available in /osgeo/backup/longterm/mum03 on BackupVM.

=== planet.osgeo.org ===

* /osgeo/venus (venus2?)
* Admined: [[Paolo Corti]], [[User:Jsanz|Jorge Gaspar Sanz Salinas]], [[User:Mloskot|Mateusz Loskot]], [[User:crschmidt|Christopher Schmidt]]
* See also: [[PlanetOSGeo]]
* All admins can be contacted by e-mail on planet (at) osgeo (dot) org

=== live.osgeo.org ===

* /osgeo/osgeolive
* Static html site from SVN (https://svn.osgeo.org/osgeo/livedvd/website)
* Alex (wildintellect)

=== gallery.osgeo.org ===

Status: offline due to massive spamming

TODO: implement moderated queue or other antispam measure

* /var/www/gallery/
* content is in sqlite DB
* Spam removal howto: to be implemented

=== 2011ws.foss4g.org ===

* /osgeo/foss4g/uploads
* Admined by FrankW, jmckenna
* used for FOSS4G 2011 workshop files (through SFTP)

=== *.foss4g.org ===
Includes main www and 2003, 2006, 2007, 2008, 2009, 2010, 2012
/osgeo/foss4g/*
* 2011 is on webvm - as it's using Drupal
* Most are static dumps from CMSs that were used,
* 2008 uses the OCS instance (conference.osgeo.org) hosted on webextra
/osgeo/ocs2
* Most being moved from osgeo1 29sep11 by tmitchell
* 2010 also moved from projects vm.

=== vmap0.tiles.osgeo.org ===

* Serves as http://vmap0.tiles.osgeo.org/wms/vmap0?SERVICE=WMS&VERSION=1.1.0&REQUEST=GetCapabilities
* Lives in /var/www/tiles/vmap0 and /mapdata (2.3G)
* Originally setup by Chris Schmidt.
* Currently produces the bulk of load on the webextra VM.
* Presumably this is widely used as a default layer in OpenLayers.
* As of March 2013, it appears this has been mostly or completely migrated to servers at telescience.

[[Category:Infrastructure]]

Boston Code Sprint 2013

2013-03-20T23:36:53Z

Warmerdam: /* Participants */

'''Gold Sponsors'''
{| class="wikitable"
|-
| [http://www.enterprisedb.com EnterpriseDb]
| [[File:EDB_logo_rgb_300.jpg‎|300px]]
|-
|}

'''Silver Sponsors'''
{| class="wikitable"
|-
| [http://www.geosynergy.com.au GeoSynergy]
| [[File:GeoSynergy.png|200px]]
|       
| [http://www.airborneinteractive.com Airborne Interactive]
| [[File:AirborneInteractive.png|200px]]
|-
|}

'''Bronze Sponsors'''
{| class="wikitable"
|-
| [http://www.hobu.biz Hobu]
| [[File:Logo-Hobu.png‎|150px]]
|      
| [http://www.azavea.com Azavea]
| [[File:Logo-azavea.png|150px‎]]
|      
| [http://www.1ocean.com OneOcean]
| [[File:Bos_code_sprint_oneocean.png|150px]]
|     
| [http://www.appgeo.com/ AppGeo]
| [[File:Appgeo_bos2013.jpg‎|150px]]
|-
|}

'''Host Sponsor'''
{| class="wikitable"
|-
| [http://www.paragoncorporation.com Paragon Corporation]
| [[File:Version8.png|175px]]
|-
|}

== SPECIAL BULLETIN ==
If you have not found accommodation under $200 or would like to have a roomie, please contact Leo at lr at pcorp.us now. You will still find great values on Hotwire or Price Line. Deluxe accommodation starts around $120. Luxury starts around $170. Act fast!

If you have special dietary requirements, please contact Leo at lr at pcorp.us. Otherwise be expected to consume land animals, sea creatures, and vegetation.

== Purpose ==
Get together project members to make decisions and tackle larger geospatial problems (as done last year at the [[IslandWood Code Sprint 2012]] and previous years: [[Montreal Code Sprint 2011|Montreal]] (2011), [[New York Code Sprint 2010|New York City]] (2010), and [[Toronto Code Sprint 2009|Toronto]] (2009)). This code sprint is targeting members of the "C Tribe" (eg, MapServer, GRASS, GDAL, Proj, PostGIS, MapGuide, OpenLayers). Other tribes are welcome to join the sprint, of course, but we hope that "C Tribe" members will give this event special consideration.

We have started a [[Boston Sprint 2013 Agenda]] page for preliminary planning of tasks.

== Dates and Times ==
Dates: Monday - Thursday 3/25-3/28

Time: Mon-Wed (9AM - 5PM), Thu (9AM - Noon)

== Venue ==
[http://www.devonshireboston.com/skyclub.html Devonshire Sky Club Conference Room] (42.358187,-71.057593)

Walking distance from all subway lines, rail and bus. From airport, take subway (Blue line) to State Street.

== Agenda ==
'''Monday (March 25th)'''
* 9:00am to 9:30am - Welcomes
* 9:30am to 11:30am - Sprinting
* 11:30am to 1:30pm - Lunch, Informal Presentations
* 1:30pm - 2:30pm - Google Hangout
* 2:30pm to 4:00pm - Sprinting
* 4:00pm to 6:00pm - Cocktail

'''Tuesday (March 26th)'''
* 9:00am to 11:30am - Sprinting
* 11:30am to 1:30pm - Lunch, Informal Presentations
* 1:30pm - 2:30pm - Google Hangout
* 2:30pm to 4:00pm - Sprinting
* 4:00pm to 6:00pm - Cocktail

'''Wednesday (March 27th)'''
* 9:00am to 11:30am - Sprinting
* 11:30am to 1:30pm - Lunch, Informal Presentations
* 1:30pm - 2:30pm - Google Hangout
* 2:30pm to 4:00pm - Sprinting
* 4:00pm to 6:00pm - Cocktail

'''Thursday (March 28th)'''
* 9:00am to 11:30am - Sprinting
* 11:30am to Noon - Farewells

== Hotel ==
We've decided not to get a block of rooms because it seems it is pricier than having people pick the hotel they like best. There are over a dozen hotels name-brand and boutique within walking, all rated above three stars. Should you have specific questions, feel free to email us directly: lr at pcorp.us. We’ll help you find the perfect accommodation.

Our recommendation is to book your own room via Hotwire or Priceline.

For Hotwire, any hotel in the Financial District will be within walking distance.
For Price Line, any hotel within a half mile of 1 DEVONSHIRE PL BOSTON MA 02109 will be within walking distance.

== Costs ==
Participants should plan for the following costs:

* Travel to Boston
* Accommodation for three nights
* Breakfast and dinner

== Project Plans ==
* [[Boston Sprint 2013 Agenda]]
* [https://github.com/mapserver/mapserver/wiki/Boston-Codesprint-Agenda MapServer sprint plan]

== Sponsor Demos ==
During the lunch hour, our sponsors will have the opportunity to talk briefly and informally about their products/services and how they use open source.

* Monday - Azavea: GeoTrellis
* Tuesday - TBA
* Wednesday - TBA

== Communication ==
* Please join the mailing list: http://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net

== Participants ==
We are planning for attendance of 20-30. Please add your name and the projects you are hoping to sprint and note the likeliness of your attendance.

Indicate if you have already finalized accommodation and travel arrangements.

# Regina Obe - Paragon Corporation - Hostess
# Leo Hsu - Paragon Corporation - Hostess' consort
# Stephen Mather - PostGIS/Raster/PDAL - Attendance assured. Local
# [[User:Woodbri|Steve Woodbridge]] - iMaptools.com - MapServer; pgRouting; postGIS - Attendance assured. Local
# [[User:pwramsey3|Paul Ramsey]] - PostGIS - Arriving Mar 24 @ 18:11 on AC364
# Thomas Bonfort - Terriscope - MapServer - Arriving Mar 24 @ 19:25 on LH424
# Jonas Lund Nielsen - Danish Geodata Agency - MapServer - Arriving Mar 24 @ 19:15 on AC8666
# Howard Butler - Hobu, Inc. - Arriving Mar 24 @ 4:30 on UA1235
# [[User:dmorissette|Daniel Morissette]] - Mapgears - MapServer; GDAL/OGR - Flight/Hotel booked
# [[Jeff McKenna]] - Gateway Geomatics - MapServer - Flight booked
# Olivier Courtin - Oslandia - PostGIS, TinyOWS - Flight booked
# Hugo Mercier - Oslandia - PostGIS - Flight booked
# Stephan Meissl - EOX - MapServer - Flight booked
# Bborie Park - PostGIS Raster - Flight booked
# Steve Lime - MapServer - Flight booked
# Alan Boudreault - Mapgears - MapServer, MapCache; GDAL/OGR - Flight/Hotel booked
# [[User:Djay|Gérald Fenoy]] - GeoLabs SARL - ZOO-Project - Flight booked
# Jim Klassen - SharedGeo - Flight booked
# Michael Smith - US Army Corps - MapServer; PDAL; GDAL/OGR - Attendance assured
# [[User:Dzwarg|David Zwarg]] - Azavea - PostGIS Raster; GDAL/OGR - Very likely
# Norman Barker - Cloudant - Very likely
# [[User:kshepard|Kenny Shepard]] - Azavea - PostGIS - Very likely
# Rob Emanuele - Azavea - PostGIS Raster - Very likely
# Pierre Racine - University Laval - PostGIS Raster - Very likely
# Tom Kralidis - MapServer, pycsw, owslib - Likely
# Michael P. Gerlek (or designee) - OneOcean - PDAL & Friends - Likely
# [[User:Jwalgran|Justin Walgran]] - Azavea - OpenLayers; PostGIS - Likely
# Norman Vine - Likely
# Sarah Ward - qPublic - MapServer documentation - Flight/Hotel booked
# [[User:Mloskot|Mateusz Loskot]] - PostGIS/PDAL - Unlikely
# <strike>[[User:kirk|Kirk McKelvey]] - LizardTech - PDAL/GDAL - </strike> (will sorely miss this - until next year then)

== Individual Preparation ==

* Bring your own computer
* Install subversion and the compiler tools, and come with a working development environment if possible

== FAQ ==

* Is the Boston Code Sprint just a coding event?
** Yes, a coding, testing and documentation event. It is a working session for people who are already participants in open source projects.
* Will it be possible to present new projects during this event?
** No, this is not a presentation-oriented event. People will get together in small groups and work on areas of mutual interest within their projects.
* Will there be presentation time to show case innovative uses of technology?
** Yes, Sponsors and sprinters actively working on projects will have their moment of glory

== Extracurricular Activities ==

Here are some events happening around town that could be of interest:

=== Sporting Events ===
* Hockey - Mon Mar 25 Maple Leafs vs. Bruins
* Hockey - Wed Mar 27 Canadiens vs. Bruins
* Hoops - Tue Mar 26 Knicks vs. Celtics

=== Crashing Parties ===
* Mon Mar 25 7-10 PM [http://ignitelocationtechboston1.eventbrite.com/ Ignite LocationTech Boston] (follow link to register)
* [http://www.meetup.com/avidgeo/ AvidGeo] might be having a meetup around that time too.

== Sponsors ==
We have three sponsorship levels:

* Gold: $2000+, Silver: $1500, Bronze: $750

We encourage sponsors ($750+) to support nutriment and entertainment for the sprinters as they work hard and play hard for four productive days. Contributions will go towards space rental, lunch, and libations (in this order).

Sponsors will receive the following honors:

* Your logo or portrait at the top of this page
* 30-min slot to talk about how you are using FOSS GIS
* Get to stare at us during the sprint and voice your in put in person
* Our undying gratitude, which comes in handy when you least expect it. (Remember that feature you wanted...)

To sponsor, please contact Leo Hsu and Regina Obe (lr at pcorp dot us) directly regarding sponsorship and level of sponsorship you'd like to provide

=== 2013 Sponsors ===
==== Gold ====
EnterpriseDb
==== Silver ====
Mobile Geographics, Airborne Interactive, GeoSynergy
==== Bronze ====
OneOcean, Azavea, Hobu, AppGeo