Difference between revisions of "MapProxy Incubation Application"
(Update to 2020 state) |
|||
| Line 14: | Line 14: | ||
* Oliver Tonnhofer, olt<ät>omniscale.de, Omniscale GmbH & Co. KG | * Oliver Tonnhofer, olt<ät>omniscale.de, Omniscale GmbH & Co. KG | ||
| − | + | ||
| − | + | Right know we are building a PCS and adding more official committers. | |
=== Please describe your Project. === | === Please describe your Project. === | ||
| Line 25: | Line 25: | ||
=== Why is hosting at OSGeo good for your project? === | === Why is hosting at OSGeo good for your project? === | ||
| − | + | MapProxy fits in well in the OSGeo software stack. It can be used in combination with other software like MapServer, GeoServer, OpenLayers, QGIS, etc and this has been demonstrated on OSGeo Live. | |
| − | + | MapProxy was developed and maintained by Omniscale as a single-vendor open source project. Omniscale is now stepping down from any further development. MapProxy is used all around the world and there is interest from companies and individuals to continue to work on MapProxy. Right know we are building a PSC with users and developers. We think it is a good idea to hand the project to the OSGeo as an umbrella for this new developer community that is building right now. | |
=== Type of application does this project represent(client, server, standalone, library, etc.): === | === Type of application does this project represent(client, server, standalone, library, etc.): === | ||
| Line 39: | Line 39: | ||
=== Please describe any relationships with commercial companies or products. === | === Please describe any relationships with commercial companies or products. === | ||
| − | Development was started by Omniscale | + | Development was started by Omniscale. There are no commercial versions of MapProxy available (no dual-licensing, etc.). |
=== Which open source license(s) will the source code be released under? === | === Which open source license(s) will the source code be released under? === | ||
| − | The source code is | + | The source code is released under the Apache License 2.0. |
=== Is there already a beta or official release? === | === Is there already a beta or official release? === | ||
| − | The first official release was made in March 2010 | + | The first official release was made in March 2010. There was at least one major releases per year in the past. We hope to increase this pace in the future. |
=== What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)? === | === What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)? === | ||
| Line 63: | Line 63: | ||
MapProxy is not a registered trademark. | MapProxy is not a registered trademark. | ||
| − | All rights are held by Omniscale, with the exception of a few modules that are included in MapProxy. These modules are under a BSD-ish licenses, included in separate files. Copyright is documented in COPYING.txt, see https:// | + | All rights are held by Omniscale, with the exception of a few modules that are included in MapProxy. These modules are under a BSD-ish licenses, included in separate files. Copyright is documented in COPYING.txt, see https://github.com/mapproxy/mapproxy/blob/master/COPYING.txt |
=== How many people actively contribute (code, documentation, other?) to the project at this time? === | === How many people actively contribute (code, documentation, other?) to the project at this time? === | ||
| − | Most code | + | Most code was contributed by Omniscale, with only a few smaller patches from other people. |
| − | + | Omniscale received monetary contributions from various companies and institutions in the last years to implement new features for MapProxy. | |
| + | Omniscale is stepping down from the development and other developers are already started to work on new features. | ||
| − | But the codebase of MapProxy is also not very large, with | + | But the codebase of MapProxy is also not very large, with around 20k lines of code and around 20k lines of tests. |
=== How many people have commit access to the source code repository? === | === How many people have commit access to the source code repository? === | ||
| − | We use a distributed version control system, so anybody can fork the project and provide code. | + | We use a distributed version control system, so anybody can fork the project and provide code. We will increase the number of people with push-rights to GitHub in the PSC forming process. |
=== How many users do you expect to download the project when it is released? === | === How many users do you expect to download the project when it is released? === | ||
=== Approximately how many users are currently using this project? === | === Approximately how many users are currently using this project? === | ||
| − | We have an active mailing list with | + | We have an active mailing list with 320 subscribers (as of April 2020) and around 2000 downloads/month according to https://pypistats.org/packages/mapproxy. |
| − | We know from conferences, mailing lists and business contacts, that MapProxy is used by a lot of open source GIS companies. Especially in Germany, were we are active in the local chapter (FOSSGIS e.V.). | + | We know from conferences, mailing lists and business contacts, that MapProxy is used by a lot of open source GIS companies all around the world. Especially in Germany, were we are active in the local chapter (FOSSGIS e.V.). |
=== What type of users does your project attract (government, commercial, hobby, academic research, etc. )? === | === What type of users does your project attract (government, commercial, hobby, academic research, etc. )? === | ||
| Line 89: | Line 90: | ||
=== 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? === | === 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? === | ||
| − | Our mailing list is already hosted by OSGeo as a OSGeo Lab project. We | + | Our mailing list is already hosted by OSGeo as a OSGeo Lab project. We are using Git and the code is hosted on GitHub. |
| + | |||
| + | The PSC might plan to move the mapproxy.org domain and hosting (static web page only) to the OSGeo infrastructure in the future. | ||
=== Does the project include an automated build and test? === | === Does the project include an automated build and test? === | ||
| − | We have an extensive test suite with over 1000 unit and system tests. We have a continuous integration server that runs all these tests automatically with different Python versions. ( | + | We have an extensive test suite with over 1000 unit and system tests. We have a continuous integration server that runs all these tests automatically with different Python versions. (https://travis-ci.org/github/mapproxy/mapproxy) |
Documentation is build nightly and there are packages with the latest source code available. | Documentation is build nightly and there are packages with the latest source code available. | ||
Latest revision as of 00:30, 16 April 2020
MapProxy Incubation Application
Mailing list discussion: http://lists.osgeo.org/pipermail/incubator/2012-January/001747.html
Ticket: http://trac.osgeo.org/osgeo/ticket/851
Questionnaire
Please provide the name and email address of the principal Project Owner.
Oliver Tonnhofer, olt<ät>omniscale.de, Omniscale GmbH & Co. KG
Please provide the names, emails and entity affiliation of all official committers
- Oliver Tonnhofer, olt<ät>omniscale.de, Omniscale GmbH & Co. KG
Right know we are building a PCS and adding more official committers.
Please describe your Project.
MapProxy is an open source proxy for geospatial data. It caches, accelerates and transforms data from existing map services and serves any desktop or web GIS client.
MapProxy is a tile cache solution, but also offers many new and innovative features like full support for WMS clients and a powerful authorization API.
Why is hosting at OSGeo good for your project?
MapProxy fits in well in the OSGeo software stack. It can be used in combination with other software like MapServer, GeoServer, OpenLayers, QGIS, etc and this has been demonstrated on OSGeo Live.
MapProxy was developed and maintained by Omniscale as a single-vendor open source project. Omniscale is now stepping down from any further development. MapProxy is used all around the world and there is interest from companies and individuals to continue to work on MapProxy. Right know we are building a PSC with users and developers. We think it is a good idea to hand the project to the OSGeo as an umbrella for this new developer community that is building right now.
Type of application does this project represent(client, server, standalone, library, etc.):
Server/proxy application.
Please describe any relationships to other open source projects.
MapProxy is written in Python and uses multiple open source libraries, from Python Image Library to GDAL, Proj4 and GEOS.
Please describe any relationships with commercial companies or products.
Development was started by Omniscale. There are no commercial versions of MapProxy available (no dual-licensing, etc.).
Which open source license(s) will the source code be released under?
The source code is released under the Apache License 2.0.
Is there already a beta or official release?
The first official release was made in March 2010. There was at least one major releases per year in the past. We hope to increase this pace in the future.
What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)?
The project started as a commercial product by Omniscale and was open sourced in March 2010.
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?
It implements various open standards like WMS, WMTS, KML, and TMS.
Is the code free of patents, trademarks, and do you control the copyright?
The code does not contain anything where we have patents on and we are not aware of any other existing patents. The Apache License also contains a patent clause.
MapProxy is not a registered trademark.
All rights are held by Omniscale, with the exception of a few modules that are included in MapProxy. These modules are under a BSD-ish licenses, included in separate files. Copyright is documented in COPYING.txt, see https://github.com/mapproxy/mapproxy/blob/master/COPYING.txt
How many people actively contribute (code, documentation, other?) to the project at this time?
Most code was contributed by Omniscale, with only a few smaller patches from other people. Omniscale received monetary contributions from various companies and institutions in the last years to implement new features for MapProxy. Omniscale is stepping down from the development and other developers are already started to work on new features.
But the codebase of MapProxy is also not very large, with around 20k lines of code and around 20k lines of tests.
How many people have commit access to the source code repository?
We use a distributed version control system, so anybody can fork the project and provide code. We will increase the number of people with push-rights to GitHub in the PSC forming process.
How many users do you expect to download the project when it is released?
Approximately how many users are currently using this project?
We have an active mailing list with 320 subscribers (as of April 2020) and around 2000 downloads/month according to https://pypistats.org/packages/mapproxy.
We know from conferences, mailing lists and business contacts, that MapProxy is used by a lot of open source GIS companies all around the world. Especially in Germany, were we are active in the local chapter (FOSSGIS e.V.).
What type of users does your project attract (government, commercial, hobby, academic research, etc. )?
Mostly government, but also commercial and academic users.
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?
Our mailing list is already hosted by OSGeo as a OSGeo Lab project. We are using Git and the code is hosted on GitHub.
The PSC might plan to move the mapproxy.org domain and hosting (static web page only) to the OSGeo infrastructure in the future.
Does the project include an automated build and test?
We have an extensive test suite with over 1000 unit and system tests. We have a continuous integration server that runs all these tests automatically with different Python versions. (https://travis-ci.org/github/mapproxy/mapproxy)
Documentation is build nightly and there are packages with the latest source code available.
What language(s) are used in this project? (C/Java/perl/etc)
Python and it makes use of libraries written in C (Proj4, GDAL, ...)
What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers?
All source code, comments and documentation is written in English.
What is the (estimated) size of a full release of this project?
Should fit on a floppy.