GeoServer : OSGEO incubation questionnaire
This page last changed on Sep 04, 2009 by aaime.
This wiki page has been setup to allow a community filling of the OSGEO incubation questionnaire. Please participate in answering the questions/correcting the existing answers
GeoServer sources are assigned to a single legal entity, The Open Planning Project, as reported by the source code headers:
The project is controlled by a Project Streering commitee composed by:
Current committers are listed in the Xircles GeoServer developer page
We thank previous committers for all the hard work in GeoServer. They been removed during the OSGEO preparation cleanup so that the actual committer list shows the ones that have been active:
GeoServer is a Java-based web GIS server with a strong focus on implementing Open Geospatial Consortium (OGC) specification while keeping an eye for other popular Web GIS communication protocols such as REST.
For a longer answer see the GeoServer description page on the GeoServer site: http://geoserver.org/display/GEOS/What+is+GeoServer
It raises visibility and makes for a natural match that people out there are expecting to see.
Web GIS server.
GeoServer lives and breaths in an open source environment, so it relates, to various degrees, to many open source projects.
Here is a list of the geospatial ones:
The technical underpinning of GeoServer also use a number of non geospatial libraries, such as Spring, Apache Commons, Xerces, Wicket, Log4J, PicoContainer, FreeMarker, XStream, Batik, H2 database and Jetty, just to name some.
The GeoServer community involves developers that are paid by commercial companies and "dot-org" ones, such as OpenGeo, GeoSolutions, LisaSoft and Refractions research, and by public institutions, such as AUSCOPE.
GeoServer can work without the aid of any commercial software, but it can talk to some, for example it has data stores for Oracle and ArcSDE, as well as readers for closed formats such as MrSID or ECW.
The source code is released under the GPL V2 license, although there are talks to release some of the core classes under a less restrictive licence so that it's possible to develop closed source plugins.
GeoServer has a long stable release history with tens of stable releases over various years.
11. What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)?
The software originated years ago at a no profit called "Visions for New York". The no profit needed to use streets and traffic information and needed a way to deal with it on a level that went beyond just displaying maps.
Over the years various people joined the project and improved the number of services supported, the data formats accessed and generated, and a UI was provided too.
12. Does the project support open standards? Which ones and to what extent? (OGC, w3c, ect.) Has the software been certified to any standard (CITE for example)? If not, is it the intention of the project owners to seek certification at some point?
GeoServer is reference implementation of OGC WFS 1.1, WFS 1.0 and WCS 1.1. It's also certified compliant for WMS 1.1 and WCS 1.0. Every stable release of GeoServer must pass all CITE tests for any implemented standard before being released to the public.
All the file headers report "The Open Planning Project" as the copyright owner. All new committers are required to sign a copyright assignment agreement towards "The Open Planning Project".
We are not aware of patent or trademarks infringements in the code base but some due diligence is in order to double check.
A scan in the svn logs over the project trunk and the active 1.7.x branch over the last few months (approximately since February 2009) reveals 19 active committers:
The list has been obtained using the following commands on July 24 2009:
The SourceForge download counters routinely report downloads in the order of the 10 thousands each month.
17. What type of users does your project attract (government, commercial, hobby, academic research, etc. )?
It seems to attract a wide variety of users, government, commercial, students and research.
18. If you do not intend to host any portion of this project using the OSGeo infrastructure, why should you be considered a member project of the OSGeo Foundation?
We don't intend to join OSGeo because of the infrastructure, but because we share the same principles and we feel like part of the OSGeo community.
That said, moving SVN and eventually the mailing lists over to OSGeo infrastructure is under consideration.
The projects has two build bot that routinely polls the version control and builds GeoServer:
The bot also generates a nightly build of every active branch for users to check out progress:
The source code contains 272 test classes, each executing multiple unit tests, totalling 1124 separate tests (computed using "cat `find . -name "*Test.java"` | grep "void test" | wc -l" on the GeoServer trunk checkout).
Also, before pushing out a release all CITE tests against the core services are run, adding between one and two thousands other tests to the mix.
21. What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers?
22. What is the (estimated) size of a full release of this project? How many users do you expect to download the project when it is released?
A release comprises various packaging and plug-ins to satisfy different needs. At the moment each packaging is around 45MB (each user is expected to download only one of the different packaging, as they are usually native installers which are plaftform dependent) and the plugin size varies between the few kilobytes and some megabytes.
Summing up the various native installers and packaging formats, and the extensions, the disk space used by a single release is around 200MB.
|Document generated by Confluence on May 14, 2014 23:00|