diff --git a/README.md b/README.md index c2c0dff6936..2402d2413ef 100644 --- a/README.md +++ b/README.md @@ -40,10 +40,11 @@ for more details. GeoServer uses [JIRA](https://osgeo-org.atlassian.net/projects/GEOS), hosted by [Atlassian](https://www.atlassian.com/), for issue tracking. -## Mailing Lists + +## Community support -The [mailing list page](https://geoserver.org/comm/) on the GeoServer web site provides -access to the various mailing list, as well as some indication of the [code of conduct](https://geoserver.org/comm/userlist-guidelines.html) when posting to the lists +The [Community support page](https://geoserver.org/comm/) on the GeoServer web site provides +access to the various channels of communication, as well as some indication of the [code of conduct](https://geoserver.org/comm/userlist-guidelines.html) when posting to the groups. ## Contributing diff --git a/SECURITY.md b/SECURITY.md index 1f313821623..71d4dc7781b 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -20,7 +20,7 @@ You can volunteer on the developer list to make additional releases, or engage w If you encounter a security vulnerability in GeoServer please take care to report in a responsible fashion: -1. Keep exploit details out of public mailing lists and issue tracker. +1. Keep exploit details out of public forums, mailing lists, and issue tracker. 2. There are two options to report a security vulnerability: @@ -33,7 +33,7 @@ If you encounter a security vulnerability in GeoServer please take care to repor * To report via GitHub: - Navigate to [security](https://github.com/geoserver/geoserver/security) page, use link for *Private vulnerability reporting*. + Navigate to [security](https://github.com/geoserver/geoserver/security) page, use link for [Private vulnerability reporting](https://github.com/geoserver/geoserver/security/advisories/new). For more information see [GitHub documentation](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability#privately-reporting-a-security-vulnerability). diff --git a/doc/en/api/1.0.0/coverages.yaml b/doc/en/api/1.0.0/coverages.yaml index c669726d79b..c0e25ddb805 100644 --- a/doc/en/api/1.0.0/coverages.yaml +++ b/doc/en/api/1.0.0/coverages.yaml @@ -6,8 +6,8 @@ info: description: A coverage is a raster data set which originates from a coverage store. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/coveragestores.yaml b/doc/en/api/1.0.0/coveragestores.yaml index 454b5c60798..28500609cb9 100644 --- a/doc/en/api/1.0.0/coveragestores.yaml +++ b/doc/en/api/1.0.0/coveragestores.yaml @@ -6,8 +6,8 @@ info: description: A coverage store describes how access a raster data source. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/datastores.yaml b/doc/en/api/1.0.0/datastores.yaml index 95cbd4001fd..934838d7fb4 100644 --- a/doc/en/api/1.0.0/datastores.yaml +++ b/doc/en/api/1.0.0/datastores.yaml @@ -6,8 +6,8 @@ info: description: A data store contains vector format spatial data. It can be a file (such as a shapefile), a database (such as PostGIS), or a server (such as a remote Web Feature Service). contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/featuretypes.yaml b/doc/en/api/1.0.0/featuretypes.yaml index c5e72526324..b10a9db10cb 100644 --- a/doc/en/api/1.0.0/featuretypes.yaml +++ b/doc/en/api/1.0.0/featuretypes.yaml @@ -6,8 +6,8 @@ info: description: A feature type is a vector based spatial resource or data set that originates from a data store. In some cases, such as with a shapefile, a feature type has a one-to-one relationship with its data store. In other cases, such as PostGIS, the relationship of feature type to data store is many-to-one, feature types corresponding to a table in the database. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest schemes: diff --git a/doc/en/api/1.0.0/fonts.yaml b/doc/en/api/1.0.0/fonts.yaml index a01836020b9..608cbbbcd63 100644 --- a/doc/en/api/1.0.0/fonts.yaml +++ b/doc/en/api/1.0.0/fonts.yaml @@ -6,8 +6,8 @@ info: description: A font is a set of characters that can be used in a style for displaying labels. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/gwcblobstores.yaml b/doc/en/api/1.0.0/gwcblobstores.yaml index 518a0e03edd..198e6cc2f93 100644 --- a/doc/en/api/1.0.0/gwcblobstores.yaml +++ b/doc/en/api/1.0.0/gwcblobstores.yaml @@ -6,8 +6,8 @@ info: description: BlobStores configure the persistence of tile data. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 schemes: - http diff --git a/doc/en/api/1.0.0/gwcbounds.yaml b/doc/en/api/1.0.0/gwcbounds.yaml index 6c6ff2dc709..d5aaa59d689 100644 --- a/doc/en/api/1.0.0/gwcbounds.yaml +++ b/doc/en/api/1.0.0/gwcbounds.yaml @@ -6,8 +6,8 @@ info: description: A RESTful interface through which get the bounds of a given layer based on srs. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 schemes: - http diff --git a/doc/en/api/1.0.0/gwcdiskquota.yaml b/doc/en/api/1.0.0/gwcdiskquota.yaml index 37e028fe498..286181aed52 100644 --- a/doc/en/api/1.0.0/gwcdiskquota.yaml +++ b/doc/en/api/1.0.0/gwcdiskquota.yaml @@ -6,8 +6,8 @@ info: description: The REST API for Disk Quota management provides a RESTful interface through which clients can configure the disk usage limits and expiration policies for a GeoWebCache instance through simple HTTP calls. Since disk usage increases geometrically by zoom level, one single seeding task could fill up an entire storage device. Because of this, GeoWebCache employs a disk quota system where one can specify the maximum amount of disk space to use for a particular layer, as well as logic on how to proceed when that quota is reached. There are two different policies for managing the disk quotas - Least Frequently Used (LFU) and Least Recently Used (LRU). contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 schemes: - http diff --git a/doc/en/api/1.0.0/gwcfilterupdate.yaml b/doc/en/api/1.0.0/gwcfilterupdate.yaml index c531ffbed4e..02c1844b923 100644 --- a/doc/en/api/1.0.0/gwcfilterupdate.yaml +++ b/doc/en/api/1.0.0/gwcfilterupdate.yaml @@ -6,8 +6,8 @@ info: description: The REST API for Updating GWC filter contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 schemes: - http diff --git a/doc/en/api/1.0.0/gwcglobal.yaml b/doc/en/api/1.0.0/gwcglobal.yaml index 37440b65a1d..9e9ec82a0b5 100644 --- a/doc/en/api/1.0.0/gwcglobal.yaml +++ b/doc/en/api/1.0.0/gwcglobal.yaml @@ -6,8 +6,8 @@ info: description: Global configuration for the GeoWebCache server contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 schemes: - http diff --git a/doc/en/api/1.0.0/gwcgridsets.yaml b/doc/en/api/1.0.0/gwcgridsets.yaml index f86337e13aa..41733710c1c 100644 --- a/doc/en/api/1.0.0/gwcgridsets.yaml +++ b/doc/en/api/1.0.0/gwcgridsets.yaml @@ -6,8 +6,8 @@ info: description: A Grid Set is a set of tile grids associated with a coordinate reference system. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 schemes: - http diff --git a/doc/en/api/1.0.0/gwcindex.yaml b/doc/en/api/1.0.0/gwcindex.yaml index 9a334ccb373..dea9164e3d8 100644 --- a/doc/en/api/1.0.0/gwcindex.yaml +++ b/doc/en/api/1.0.0/gwcindex.yaml @@ -6,8 +6,8 @@ info: description: The front facing html ui for GeoWebCache. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 schemes: - http diff --git a/doc/en/api/1.0.0/gwclayers.yaml b/doc/en/api/1.0.0/gwclayers.yaml index c6165ce7243..2d7e6154db9 100644 --- a/doc/en/api/1.0.0/gwclayers.yaml +++ b/doc/en/api/1.0.0/gwclayers.yaml @@ -6,8 +6,8 @@ info: description: A layer is a published resource (feature type or coverage). contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 schemes: - http diff --git a/doc/en/api/1.0.0/gwcmasstruncate.yaml b/doc/en/api/1.0.0/gwcmasstruncate.yaml index 5fc3dd92f7b..7c24ddb9a79 100644 --- a/doc/en/api/1.0.0/gwcmasstruncate.yaml +++ b/doc/en/api/1.0.0/gwcmasstruncate.yaml @@ -6,8 +6,8 @@ info: description: The REST API for mass truncation provides a mechanism for completely clearing caches more conveniently than with the seeding system contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 schemes: - http diff --git a/doc/en/api/1.0.0/gwcmemorycachestatistics.yaml b/doc/en/api/1.0.0/gwcmemorycachestatistics.yaml index cf6712bcca6..44446fe62b7 100644 --- a/doc/en/api/1.0.0/gwcmemorycachestatistics.yaml +++ b/doc/en/api/1.0.0/gwcmemorycachestatistics.yaml @@ -6,8 +6,8 @@ info: description: A response contains memory cache statistics contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 schemes: - http diff --git a/doc/en/api/1.0.0/gwcreload.yaml b/doc/en/api/1.0.0/gwcreload.yaml index 91ee14e7ce2..6a918c77494 100644 --- a/doc/en/api/1.0.0/gwcreload.yaml +++ b/doc/en/api/1.0.0/gwcreload.yaml @@ -6,8 +6,8 @@ info: description: Reloading a GeoWebCache instance after changing configurations. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 schemes: - http diff --git a/doc/en/api/1.0.0/gwcseed.yaml b/doc/en/api/1.0.0/gwcseed.yaml index 5bba4eb5101..0cc376363db 100644 --- a/doc/en/api/1.0.0/gwcseed.yaml +++ b/doc/en/api/1.0.0/gwcseed.yaml @@ -6,8 +6,8 @@ info: description: A layer is a published resource (feature type or coverage). contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 schemes: - http diff --git a/doc/en/api/1.0.0/importer.yaml b/doc/en/api/1.0.0/importer.yaml index 8542948dc62..d786694dfc8 100644 --- a/doc/en/api/1.0.0/importer.yaml +++ b/doc/en/api/1.0.0/importer.yaml @@ -6,8 +6,8 @@ info: description: The Importer extension gives a GeoServer administrator an alternate, more-streamlined method for uploading and configuring new layers. The main endpoint manages individual import jobs. The importer extension is an optional install and may not be available on all deployments of GeoServer contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest paths: diff --git a/doc/en/api/1.0.0/importerData.yaml b/doc/en/api/1.0.0/importerData.yaml index f78dd34ad2d..2d206cd3d68 100644 --- a/doc/en/api/1.0.0/importerData.yaml +++ b/doc/en/api/1.0.0/importerData.yaml @@ -6,8 +6,8 @@ info: description: The Importer extension gives a GeoServer administrator an alternate, more-streamlined method for uploading and configuring new layers. The data endpoint controls uploading layer data to specific import jobs. The importer extension is an optional install and may not be available on all deployments of GeoServer contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/importerTasks.yaml b/doc/en/api/1.0.0/importerTasks.yaml index 275834749ba..468533196f9 100644 --- a/doc/en/api/1.0.0/importerTasks.yaml +++ b/doc/en/api/1.0.0/importerTasks.yaml @@ -6,8 +6,8 @@ info: description: The Importer extension gives a GeoServer administrator an alternate, more-streamlined method for uploading and configuring new layers. The tasks endpoint controls individual tasks within an import job. The importer extension is an optional install and may not be available on all deployments of GeoServer contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/importerTransforms.yaml b/doc/en/api/1.0.0/importerTransforms.yaml index 66034f6e3ec..bd2c4a423e0 100644 --- a/doc/en/api/1.0.0/importerTransforms.yaml +++ b/doc/en/api/1.0.0/importerTransforms.yaml @@ -6,8 +6,8 @@ info: description: The Importer extension gives a GeoServer administrator an alternate, more-streamlined method for uploading and configuring new layers. The transforms endpoint manages data transforms applied to individual import jobs. The importer extension is an optional install and may not be available on all deployments of GeoServer contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/layergroups.yaml b/doc/en/api/1.0.0/layergroups.yaml index 7802c8ccbce..81434659c1d 100644 --- a/doc/en/api/1.0.0/layergroups.yaml +++ b/doc/en/api/1.0.0/layergroups.yaml @@ -6,8 +6,8 @@ info: description: A layer group is a group of layers that can be referenced as a single layer as part of a WMS request. A layer group can also be used as a container for layers. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/layers.yaml b/doc/en/api/1.0.0/layers.yaml index 891af50a31c..adcae52b9d8 100644 --- a/doc/en/api/1.0.0/layers.yaml +++ b/doc/en/api/1.0.0/layers.yaml @@ -6,8 +6,8 @@ info: description: A layer is a published resource (feature type or coverage). contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/logging.yaml b/doc/en/api/1.0.0/logging.yaml index 6fbe3ea3160..3f64bc736e1 100644 --- a/doc/en/api/1.0.0/logging.yaml +++ b/doc/en/api/1.0.0/logging.yaml @@ -6,8 +6,8 @@ info: description: The Logging area shows logging options for the server contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/manifests.yaml b/doc/en/api/1.0.0/manifests.yaml index 89828fb3c0e..8a25904416c 100644 --- a/doc/en/api/1.0.0/manifests.yaml +++ b/doc/en/api/1.0.0/manifests.yaml @@ -6,8 +6,8 @@ info: description: GeoServer provides a REST service to expose a listing of all loaded JARs and resources on the running instance. This is useful for bug reports and to keep track of extensions deployed into the application. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest schemes: diff --git a/doc/en/api/1.0.0/metadata.yaml b/doc/en/api/1.0.0/metadata.yaml index 26ccdca464d..b69b5c5666f 100644 --- a/doc/en/api/1.0.0/metadata.yaml +++ b/doc/en/api/1.0.0/metadata.yaml @@ -6,8 +6,8 @@ info: description: Customized Metadata Bulk Operations. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/monitoring.yaml b/doc/en/api/1.0.0/monitoring.yaml index 70b045f6c75..40eb3215823 100644 --- a/doc/en/api/1.0.0/monitoring.yaml +++ b/doc/en/api/1.0.0/monitoring.yaml @@ -6,8 +6,8 @@ info: description: Request provides details about OWS and REST requests that GeoServer has handled contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/namespaces.yaml b/doc/en/api/1.0.0/namespaces.yaml index e338fad1cf1..9c349872d14 100644 --- a/doc/en/api/1.0.0/namespaces.yaml +++ b/doc/en/api/1.0.0/namespaces.yaml @@ -6,8 +6,8 @@ info: description: A namespace is a uniquely identifiable grouping of feature types. It is identified by a prefix and a URI. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/opensearch-eo.yaml b/doc/en/api/1.0.0/opensearch-eo.yaml index 1de3ef7c478..f194e8a4eca 100644 --- a/doc/en/api/1.0.0/opensearch-eo.yaml +++ b/doc/en/api/1.0.0/opensearch-eo.yaml @@ -6,8 +6,8 @@ info: description: Allows to manipulate the OpenSearch for EO index contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest/oseo/ diff --git a/doc/en/api/1.0.0/owsservices.yaml b/doc/en/api/1.0.0/owsservices.yaml index d6a70a2256e..c193bfaa836 100644 --- a/doc/en/api/1.0.0/owsservices.yaml +++ b/doc/en/api/1.0.0/owsservices.yaml @@ -6,8 +6,8 @@ info: description: An OWS service refers to any of the OGC services that GeoServer supports, such as WFS, WMS, and WCS. These endpoints controls the settings of these services. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/params-extractor.yaml b/doc/en/api/1.0.0/params-extractor.yaml index 43cb5a0685e..fbd3debcefc 100644 --- a/doc/en/api/1.0.0/params-extractor.yaml +++ b/doc/en/api/1.0.0/params-extractor.yaml @@ -6,8 +6,8 @@ info: description: A parameter extractor rule allows specific request parameters as URL path fragments instead of using the query string. A echo parameter makes sure that certain URL paratemers are added to the capabilities documents backlinks. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/proxy-base-ext.yaml b/doc/en/api/1.0.0/proxy-base-ext.yaml index 89c661ae79b..60362e99511 100644 --- a/doc/en/api/1.0.0/proxy-base-ext.yaml +++ b/doc/en/api/1.0.0/proxy-base-ext.yaml @@ -9,8 +9,8 @@ info: port in the request URL. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/rat.yaml b/doc/en/api/1.0.0/rat.yaml index e19c29ebd49..93b8fae8565 100644 --- a/doc/en/api/1.0.0/rat.yaml +++ b/doc/en/api/1.0.0/rat.yaml @@ -7,8 +7,8 @@ info: that contains a Raster Attribute table in any bad, to create styles out of it. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/reload.yaml b/doc/en/api/1.0.0/reload.yaml index 34e5a383dc3..5f97659518a 100644 --- a/doc/en/api/1.0.0/reload.yaml +++ b/doc/en/api/1.0.0/reload.yaml @@ -6,8 +6,8 @@ info: description: Reset/Reload clears internal caches and reloads configuation from disk contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/resource.yaml b/doc/en/api/1.0.0/resource.yaml index fd521a13262..3b221a5d9e2 100644 --- a/doc/en/api/1.0.0/resource.yaml +++ b/doc/en/api/1.0.0/resource.yaml @@ -6,8 +6,8 @@ info: description: A resource is any item in the data directory that does not represent configuration. Typical resources include styles and icons. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/roles.yaml b/doc/en/api/1.0.0/roles.yaml index bdbae956ace..701da21a932 100644 --- a/doc/en/api/1.0.0/roles.yaml +++ b/doc/en/api/1.0.0/roles.yaml @@ -6,8 +6,8 @@ info: description: Organisation of security roles contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest/security diff --git a/doc/en/api/1.0.0/security.yaml b/doc/en/api/1.0.0/security.yaml index 84594788a71..371dfb1c8a8 100644 --- a/doc/en/api/1.0.0/security.yaml +++ b/doc/en/api/1.0.0/security.yaml @@ -6,8 +6,8 @@ info: description: The Security area shows access rules and other configuration for the security subsystem contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/settings.yaml b/doc/en/api/1.0.0/settings.yaml index 0a5f2a2f38a..c8a52d9c8f3 100644 --- a/doc/en/api/1.0.0/settings.yaml +++ b/doc/en/api/1.0.0/settings.yaml @@ -6,8 +6,8 @@ info: description: The Settings area shows global configuration for the server contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/structuredcoverages.yaml b/doc/en/api/1.0.0/structuredcoverages.yaml index 9d37d1d25c5..5ee388b2aab 100644 --- a/doc/en/api/1.0.0/structuredcoverages.yaml +++ b/doc/en/api/1.0.0/structuredcoverages.yaml @@ -6,8 +6,8 @@ info: description: A structured coverage store allows description of its "granules" and management of them. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/styles.yaml b/doc/en/api/1.0.0/styles.yaml index 61383e8702a..c43e7f67bef 100644 --- a/doc/en/api/1.0.0/styles.yaml +++ b/doc/en/api/1.0.0/styles.yaml @@ -6,8 +6,8 @@ info: description: A style describes how a resource is symbolized or rendered by the Web Map Service. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/system-status.yaml b/doc/en/api/1.0.0/system-status.yaml index 45aba0f6217..1ba4331b613 100644 --- a/doc/en/api/1.0.0/system-status.yaml +++ b/doc/en/api/1.0.0/system-status.yaml @@ -6,8 +6,8 @@ info: description: Request provides details about OWS and REST requests that GeoServer has handled contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/templates.yaml b/doc/en/api/1.0.0/templates.yaml index 3fc27408c06..932925f7086 100644 --- a/doc/en/api/1.0.0/templates.yaml +++ b/doc/en/api/1.0.0/templates.yaml @@ -6,8 +6,8 @@ info: description: Manage templates used to configure output (for example GetFeatureInfo reponse). Templates can be registered for the entire server or workspace. You can also configure a template for use with a store, featureType or coverage. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/transforms.yaml b/doc/en/api/1.0.0/transforms.yaml index a5a683fe562..3460c0bf066 100644 --- a/doc/en/api/1.0.0/transforms.yaml +++ b/doc/en/api/1.0.0/transforms.yaml @@ -6,8 +6,8 @@ info: description: A transform contains a style sheet that can be used to generate a new textual output format of user choosing for WFS contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/urlchecks.yaml b/doc/en/api/1.0.0/urlchecks.yaml index 81c45ae5761..dc42dcbcc41 100644 --- a/doc/en/api/1.0.0/urlchecks.yaml +++ b/doc/en/api/1.0.0/urlchecks.yaml @@ -6,8 +6,8 @@ info: description: An URL External Access Check is the check performed on user provided URLs that GeoServer will use to access remote resources. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/usergroup.yaml b/doc/en/api/1.0.0/usergroup.yaml index ac49ecd533b..71acb153eb3 100644 --- a/doc/en/api/1.0.0/usergroup.yaml +++ b/doc/en/api/1.0.0/usergroup.yaml @@ -6,8 +6,8 @@ info: description: Organisation of security users and groups contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest/security diff --git a/doc/en/api/1.0.0/wmslayers.yaml b/doc/en/api/1.0.0/wmslayers.yaml index 79e3a9fec61..b508b52d30d 100644 --- a/doc/en/api/1.0.0/wmslayers.yaml +++ b/doc/en/api/1.0.0/wmslayers.yaml @@ -6,8 +6,8 @@ info: description: A WMS store is a store whose source is another WMS. Also known as "Cascading WMS" or "External WMS". A WMS store layer is a layer from this store. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/wmsstores.yaml b/doc/en/api/1.0.0/wmsstores.yaml index 91fac4d4382..a2a6be0b8ec 100644 --- a/doc/en/api/1.0.0/wmsstores.yaml +++ b/doc/en/api/1.0.0/wmsstores.yaml @@ -6,8 +6,8 @@ info: description: A WMS store is a store whose source is another WMS. Also known as "Cascading WMS" or "Exernal WMS". contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/wmtslayers.yaml b/doc/en/api/1.0.0/wmtslayers.yaml index ba62f372929..c7f0a3c4180 100644 --- a/doc/en/api/1.0.0/wmtslayers.yaml +++ b/doc/en/api/1.0.0/wmtslayers.yaml @@ -6,8 +6,8 @@ info: description: A WMTS store is a store whose source is a remote WMTS service. Also known as "Cascading WMTS". A WMTS store layer is a layer from this store. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/wmtsstores.yaml b/doc/en/api/1.0.0/wmtsstores.yaml index a9e2c5e0c04..ff618d25d6b 100644 --- a/doc/en/api/1.0.0/wmtsstores.yaml +++ b/doc/en/api/1.0.0/wmtsstores.yaml @@ -6,8 +6,8 @@ info: description: A WMTS store is a store whose source is a remote WMTS. Also known as "Cascading WMTS". contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/workspaces.yaml b/doc/en/api/1.0.0/workspaces.yaml index d89b61388b6..9eff070fb16 100644 --- a/doc/en/api/1.0.0/workspaces.yaml +++ b/doc/en/api/1.0.0/workspaces.yaml @@ -6,8 +6,8 @@ info: description: A workspace is a grouping of data stores. Similar to a namespace, it is used to group data that is related in some way. contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/api/1.0.0/wpsdownload.yaml b/doc/en/api/1.0.0/wpsdownload.yaml index a1040bcc787..9f96c965505 100644 --- a/doc/en/api/1.0.0/wpsdownload.yaml +++ b/doc/en/api/1.0.0/wpsdownload.yaml @@ -6,8 +6,8 @@ info: description: The WPS download module allows to perform large data, map and animation downloads sing asynchronous requests contact: name: GeoServer - email: 'geoserver-users@sourceforge.net' - url: 'http://geoserver.org/comm/' + email: 'geoserver-users@osgeo.org' + url: 'https://geoserver.org/comm/' host: localhost:8080 basePath: /geoserver/rest diff --git a/doc/en/developer/source/introduction.rst b/doc/en/developer/source/introduction.rst index 300ed89d315..b30c1696d85 100644 --- a/doc/en/developer/source/introduction.rst +++ b/doc/en/developer/source/introduction.rst @@ -6,32 +6,26 @@ Introduction Welcome to GeoServer development. The project makes use of a number of resources: * https://github.com/geoserver/geoserver.github.io/wiki Wiki used for Proposals -* https://github.com/geoserver/geoserver Github source code +* https://github.com/geoserver/geoserver GitHub source code * https://osgeo-org.atlassian.net/projects/GEOS Jira issue tracker * `GeoServer User Manual `_ * `GeoServer Developer Manual `_ Communication channels: -* http://blog.geoserver.org/ -* `geoserver-devel `_ email list -* `geoserver-users `_ email list -* https://gitter.im/geoserver/geoserver +* Announcements are made on https://blog.geoserver.org/ +* `geoserver-users `_ Discourse group +* `geoserver-devel `_ email list +* Developer colaboration on https://gitter.im/geoserver/geoserver We have a number of build servers employed to assist with day to day activities: * https://build.geoserver.org/view/geoserver/ (main build server) -* http://office.geo-solutions.it/jenkins/ (windows build server) - -Notification email lists: - -* https://groups.google.com/forum/#!forum/geoserver-commits -* https://groups.google.com/forum/#!forum/geoserver-extra-builds Question and answer: -* http://gis.stackexchange.com/questions/tagged/geoserver -* http://stackoverflow.com/questions/tagged/geoserver +* https://gis.stackexchange.com/questions/tagged/geoserver +* https://stackoverflow.com/questions/tagged/geoserver License ------- diff --git a/doc/en/developer/source/policies/committing.rst b/doc/en/developer/source/policies/committing.rst index dc905845aac..a6127e56e93 100644 --- a/doc/en/developer/source/policies/committing.rst +++ b/doc/en/developer/source/policies/committing.rst @@ -50,7 +50,7 @@ The process of getting community commit access is as follows: #. **Notify the developer list** - After a developer has signed up on Github they must notify the developer + After a developer has signed up on GitHub they must notify the developer list. A project despot will then add them to the group of GeoServer committers and grant write access to the canonical repository. diff --git a/doc/en/developer/source/policies/community-modules.rst b/doc/en/developer/source/policies/community-modules.rst index d10befe429d..5a244f18f04 100644 --- a/doc/en/developer/source/policies/community-modules.rst +++ b/doc/en/developer/source/policies/community-modules.rst @@ -411,10 +411,10 @@ The following outlines the steps to demote a module to community status: #. **Call for a maintainer** - Before demoting the module first try to find a new maintainer for it. Send - an email to both the developer and user list advertising the module is in - danger of getting pushed back to community status. Wait a few days to see - if anyone steps up to take on maintainership. + Before demoting the module first try to find a new maintainer for it. Both notify + GeoServer Devel mailing list and GeoServer User forum that module is in + danger of reverting to community status. Wait a few days to see + if anyone steps up to take on maintainership or provide funding. #. **Move the module and update the build** @@ -439,9 +439,9 @@ appreciated. The more time you can give to the project in lieu of your departure the better. Send an email to the developers list as soon as you know you will - be dropping off + be dropping off. #. **Find a new maintainer** While often not possible, any attempt to find a new maintainer for the - module is greatly appreciated. + module is greatly appreciated - maybe someone who has contributed to the module before. diff --git a/doc/en/developer/source/policies/gsip.rst b/doc/en/developer/source/policies/gsip.rst index a861aa34240..217b0e43a98 100644 --- a/doc/en/developer/source/policies/gsip.rst +++ b/doc/en/developer/source/policies/gsip.rst @@ -82,10 +82,11 @@ Q. Who can comment on a GSIP? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ A: Anyone and everyone can comment on a GSIP including regular users, and it is -encouraged. Comments an take place on the email lists, or as comments on the -wiki page for the GSIP itself. Feedback from the user community is definitely -desired so that the developers do not just making decisions in a vacuum. If you -speak up your voice will be heard. +encouraged. Comments can take place on GeoServer Devel mailing list, the GeoServer +User forum, or as comments on the wiki page for the GSIP itself. + +Feedback from the user community is definitely desired so that the developers do +not just making decisions in a vacuum. If you speak up your voice will be heard. Q. Who can vote on a GSIP? ^^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/doc/en/developer/source/policies/psc.rst b/doc/en/developer/source/policies/psc.rst index acaa506282c..46806aadc0d 100644 --- a/doc/en/developer/source/policies/psc.rst +++ b/doc/en/developer/source/policies/psc.rst @@ -106,7 +106,7 @@ A GSIP proposal is NOT needed for: * an improvement that can go in a community module; or * a bug fix that doesn't rework anything substantially -For minor decisions where feedback might be desired, consult the development list, or raise it in a video meeting (anyone not attending can follow up on the meeting minutes email). The GeoServer Project recognizes that it is run those doing the work, and wish to avoid high overhead for 'getting things done'. +For minor decisions where feedback might be desired, consult the developer mailing list, or raise it in a video meeting (anyone not attending can follow up on the meeting minutes email). The GeoServer Project recognizes that it is run those doing the work, and wish to avoid high overhead for 'getting things done'. For these *snap decisions* that are not official GSIP proposals, everyone 'available' (those in the video meeting or who respond to an email within 4 days) are given the power to vote and decide an issue. The same voting procedure (+1,+0,-0,-1) is used, but any decision that receives a -1 from any party present (even a new user), should go to a GSIP. @@ -125,9 +125,9 @@ Day to day project management. Duties include: **Mailing List Participation** -PSC members are expected to be active on both user and developer email lists, subject to open-source mailing list etiquette of course. +PSC members are expected to be active on both the GeoServer User forum and the GeoServer Devel mailing list, subject to open-source mailing list etiquette of course. -*It is a requirement that all PSC members maintain good public visibility with respect to activity and management of the project. This cannot happen without a good frequency of email on the mailing lists.* +*It is a requirement that all PSC members maintain good public visibility with respect to activity and management of the project. This cannot happen without a good frequency of communication.* .. note:: diff --git a/doc/en/developer/source/policies/service_providers.rst b/doc/en/developer/source/policies/service_providers.rst index 8e8df0e5b5c..583ebdd97eb 100644 --- a/doc/en/developer/source/policies/service_providers.rst +++ b/doc/en/developer/source/policies/service_providers.rst @@ -23,9 +23,9 @@ To recognizing experienced providers and core contributors consistently we have Core contributors: take responsibility for the project, meeting all three core responsibilities: -* ``core`` demonstrating an ongoing responsibility: security email list, releases, supported extension -* ``committer`` active development: geoserver-devel, review of pull-requests, assigned jira tickets, development activities such bug-stomps and sprint participation -* ``support`` sustained community support: geoserver-user, review of jira, gis.stackexchange.com, something! +* ``core`` demonstrating an ongoing responsibility: geoserver-security, releases, supported extension +* ``committer`` active development: geoserver-devel, review of pull-requests, assigned Jira tickets, development activities such bug-stomps and sprint participation +* ``support`` sustained community support: GeoServer User forum, review of Jira issues, gis.stackexchange.com, something! Experienced providers: work on GeoServer when hired by customers but are not always active, demonstrating experience with a selection of the following checklist labels: diff --git a/doc/en/developer/source/release/guide/index.rst b/doc/en/developer/source/release/guide/index.rst index 2f559792019..ac3a70858cf 100644 --- a/doc/en/developer/source/release/guide/index.rst +++ b/doc/en/developer/source/release/guide/index.rst @@ -16,7 +16,7 @@ corresponding GeoTools and GeoWebCache releases. Therefore, before you start you coordinate a release with these projects, either performing the release yourself or asking a volunteer to perform the release. -* `GeoTools Release Guide `_ +* `GeoTools Release Guide `_ * `GeoWebCache Release repo README.md `_ Notify developer list @@ -29,9 +29,9 @@ Prerequisites The following are necessary to perform a GeoServer release: -#. Commit access to the GeoServer `Git repository `_ -#. Build access to `Jenkins `_ -#. Edit access to the GeoServer `Blog `_ +#. Commit access to the GeoServer `Git repository `_ +#. Build access to `Jenkins `_ +#. Edit access to the GeoServer `Blog `_ #. Administration rights to GeoServer `JIRA `__ #. Release/file management privileges in `SourceForge `_ @@ -135,7 +135,7 @@ When creating the first release candidate of a series, there are some extra step * Add the new version to the documentation index (``doc/en/index.html``) just after line 105, e.g.:: - 2.12.x + 2.12.x User Manual Developer Manual @@ -230,9 +230,9 @@ Run the `geoserver-release-publish + https://build.geoserver.org/geoserver/release/ -to the SourceForge FRS server. Navigate to `SourceForge `__ and verify that the artifacts have been uploaded properly. If this is the latest stable release, set the necessary flags (you will need to be a SourceForge admin user) on the ``.exe``, ``.dmg`` and ``.bin`` artifacts so that they show up as the appropriate default for users downloading on the Windows, OSX, and Linux platforms. This does not apply to maintenance or support releases. +to the SourceForge FRS server. Navigate to `SourceForge `__ and verify that the artifacts have been uploaded properly. If this is the latest stable release, set the necessary flags (you will need to be a SourceForge admin user) on the ``.exe``, ``.dmg`` and ``.bin`` artifacts so that they show up as the appropriate default for users downloading on the Windows, OSX, and Linux platforms. This does not apply to maintenance or support releases. Release notes ------------- @@ -298,7 +298,7 @@ Publish JIRA markdown release notes to GitHub tag: Create the download page ------------------------ -The `GeoServer website `_ is managed as a `GitHub Pages repository `_. Follow the `instructions `_ in the repository to create a release announcement. +The `GeoServer website `_ is managed as a `GitHub Pages repository `_. Follow the `instructions `_ in the repository to create a release announcement. The announcement page header fields include the information required to generate a download page for the release. @@ -310,7 +310,7 @@ Mailing lists .. note:: This announcement should be made for all releases, including release candidates. -Send an email to both the developers list and users list announcing the +Send both an email to the Developers list and post an announcement on the Discourse Users group announcing the release. The message should be relatively short. You can base it on the blog post. The following is an example:: @@ -320,7 +320,7 @@ The following is an example:: The release is available for download from: - http://geoserver.org/release/2.5.1/ + https://geoserver.org/release/2.5.1/ GeoServer 2.5.1 is the next stable release of GeoServer and is recommended for production deployment. diff --git a/doc/en/docguide/source/contributing.rst b/doc/en/docguide/source/contributing.rst index cbc437cdbfe..7e166ce132f 100644 --- a/doc/en/docguide/source/contributing.rst +++ b/doc/en/docguide/source/contributing.rst @@ -18,14 +18,14 @@ least make a note of the issue so that someone might fix it for you. File an issue ------------- -If you don't want to write the documentation, and/or would like to suggest a page that isn't included, you can request it. Use JIRA to file an issue. Please include the name of the page, content, and the place where this new information should be included. As with all issues, it is not guaranteed that someone will fulfill your request. +If you don't want to write the documentation, and/or would like to suggest a page that isn't included, you can request it. Use Jira to file an issue. Please include the name of the page, content, and the place where this new information should be included. As with all issues, it is not guaranteed that someone will fulfill your request. .. _file_an_issue_with_patch: File an issue and include a documentation patch ----------------------------------------------- -GeoServer uses `JIRA `_ for issue tracking. New documentation is treated like part of the code, so those who want to submit content (patches etc) can use a pull request or file an issue with JIRA and attach the content to the issue. If the content is deemed satisfactory, a contributor with commit rights will add the content to the documentation. +GeoServer uses `Jira `_ for issue tracking. New documentation is treated like part of the code, so those who want to submit content (patches etc.) can use a pull request or file an issue with Jira and attach the content to the issue. If the content is deemed satisfactory, a contributor with commit rights will add the content to the documentation. For more information see `CONTRIBUTING.md `_ in GitHub. @@ -38,7 +38,7 @@ Get commit rights The documentation is now under version control, just like the source code. Also, like the source code, one must be granted "commit rights" before being able to make changes. This helps keep the quality of the documentation as high as possible. -To gain documentation commit rights, the process is similar to gaining commit rights for code. One should submit some documentation (see the section on how to :ref:`file_an_issue_with_patch` below). If one demonstrates quality work, then a `contributor `_ can nominate this person for commit rights. +To gain documentation commit rights, the process is similar to gaining commit rights for code. One should submit some documentation (see the section on how to :ref:`file_an_issue_with_patch` above). If one demonstrates quality work, then a `contributor `_ can nominate this person for commit rights. To request commit rights, please send an email to the `GeoServer developers list `_. Please note that this access may only be to the documentation, and not the source code. diff --git a/doc/en/user/source/extensions/inspire/index.rst b/doc/en/user/source/extensions/inspire/index.rst index 2048f650fb5..7f5364edf9b 100644 --- a/doc/en/user/source/extensions/inspire/index.rst +++ b/doc/en/user/source/extensions/inspire/index.rst @@ -7,7 +7,7 @@ The INSPIRE extension allows GeoServer to be compliant with the View Service and In practice this means adding some extra elements into an extended capabilities section of the WMS, WFS and WCS capabilities documents. For WMS, WFS and WCS this includes a **Metadata URL** element with a link to the metadata associated with the service, and **SupportedLanguages** and **ResponseLanguage** elements which report the response language (GeoServer can only support one response language). For WFS and WCS there are also one or more **SpatialDataSetIdentifier** elements for each spatial data resource served by the service. -.. note:: The current INSPIRE extension fulfills "Scenario 1" of the View Service extended metadata requirements. "Scenario 2" is not currently supported in GeoServer, but is certainly possible to implement. If you are interested in implementing or funding this, please raise the issue on the :ref:`GeoServer mailing list `. +.. note:: The current INSPIRE extension fulfills "Scenario 1" of the View Service extended metadata requirements. "Scenario 2" is not currently supported in GeoServer, but is certainly possible to implement. If you are interested in implementing or funding this, please raise the issue on the :ref:`GeoServer developer mailing list `. For more information on the INSPIRE directive, please see the European Commission's `INSPIRE website `_. diff --git a/doc/en/user/source/filter/function_reference.rst b/doc/en/user/source/filter/function_reference.rst index cd7c3e93155..fa7be114112 100644 --- a/doc/en/user/source/filter/function_reference.rst +++ b/doc/en/user/source/filter/function_reference.rst @@ -10,7 +10,7 @@ browsing to http://localhost:8080/geoserver/wfs?request=GetCapabilities and searching for ``ogc:Function_Names`` (WFS 1.0.0), ``ogc:FunctionNames`` (WFS 1.1.0), or ``fes:Functions`` (WFS 2.0.0) in the returned XML. If a function is described in the Capabilities document but is not in this reference, then it might mean that the function cannot be used for filtering, -or that it is new and has not been documented. Ask for details on the user mailing list. +or that it is new and has not been documented. Ask for details on the Discourse user group. Unless otherwise specified, none of the filter functions in this reference are understood natively by the data stores, and thus expressions using them will be evaluated in-memory. diff --git a/doc/en/user/source/introduction/gettinginvolved.rst b/doc/en/user/source/introduction/gettinginvolved.rst index b537f4ef2ba..7240d9f2e9c 100644 --- a/doc/en/user/source/introduction/gettinginvolved.rst +++ b/doc/en/user/source/introduction/gettinginvolved.rst @@ -7,76 +7,121 @@ GeoServer exists because of the efforts of people like you. There are many ways that you can help out with the GeoServer project. GeoServer fully embraces an open source development model that does not see a split between user and developer, producer and consumer, but instead sees everyone as a valuable contributor. +GeoServer opperates with full transparency with public `policies and procedures `__. We look forward to working with you. + Development ----------- Helping to develop GeoServer is the obvious way to help out. Developers usually start with bug fixes and other small patches, and then move into larger contributions as they learn the system. Our developers are more than happy to help out as you learn and get acquainted. We try our hardest to keep our code clean and well documented. -You can find the project on `GitHub `_. As part of the GitHub model, anyone can submit patches as pull requests, which will be evaluated by the team. To learn more about contributing to the GeoServer codebase, we highly recommend joining the GeoServer developers mailing list. See details below. +You can find the project on `github.com/geoserver `_. Anyone can submit pull requests, following our `contributing policy `__, which will be evaluated by the team. + +To learn more about contributing to the GeoServer codebase, we recommend reading the `Developers Guide `__ and joining GeoServer Developers (see below). + +.. note:: + + For `commit access `__ new developers can request to work on a community module immediately, or make contributions over time to earn a nomination for full committ access. + Documentation ------------- Another crucial way to help out is with documentation. Whether it's adding tutorials or just correcting mistakes, every contribution serves to make the project more healthy. And the best part is that you do not need to be a developer in order to contribute. -Our official documentation is contained as part of our `official code repository `_. As part of the GitHub model, anyone can submit patches as pull requests, which will be evaluated by the team. +Our official documentation is contained as part of our `official code repository `_. Anyone can submit pull requests, which will be evaluated by the team. -To learn more about contributing to the GeoServer codebase, we highly recommend joining the GeoServer developers mailing list (see details below). For typos and other small changes, please see our :docguide:`Documentation Guide ` for how to make quick fixes. +.. seealso:: + + To learn more about contributing to the GeoServer documentation, we recommend reading the `Documentatiom Guide `__ and joining GeoServer Developers (see below). -Mailing lists -------------- +.. note:: + + For typos and other small changes you can use the :guilabel:`Edit Page` link on any page. Please see :docguide:`Quick Fix ` example. -GeoServer maintains two email lists: +GeoServer User +-------------- -* `GeoServer Users `_ -* `GeoServer Developers `_ +The GeoServer User Forum is hosted on Discourse. See the `usage instructions `__ for how to sign in (or how to set up a mailing list experience). + +The GeoServer User forum is for those who have questions relating to the use of GeoServer. If you see a question asked on that you know the answer to, please respond! -The Users list is mainly for those who have questions relating to the use of GeoServer, and the Developers list is for more code-specific and roadmap-based discussions. If you see a question asked on these lists that you know the answer to, please respond! +This is an open communication channels are publicly available and are a great resource for those who are new to GeoServer, who need a question answered, or who are interested in contributing code. -These lists are publicly available and are a great resource for those who are new to GeoServer, who need a question answered, or who are interested in contributing code. +.. note:: + + The forum includes the complete `geoserver-users `__ Source Forge as a searchable archive going back to 2004. -IRC ---- +GeoServer Developer +------------------- -Users can join the IRC channel, `#geoserver `_, on the `Freenode `_ network, in order to collaborate in real time. GeoServer developers occasionally will be in this channel as well. +The `GeoServer Developers `_ mailing list is hosted SourceForge. -Bug tracking ------------- +The GeoServer Developers list is for for those working directly on the project, with code-specific and roadmap-based discussions. -If you have a problem when working with GeoServer, then please let us know through the mailing lists. GeoServer uses `JIRA `_ , a bug tracking website, to manage issue reports. In order to submit an issue, you'll need to `create an account first `_. +.. seealso:: + + The `Community Development `__ page provides additional communication options for developers. -Everyone is encouraged to submit patches and, if possible, fix issues as well. We welcome patches through JIRA, or pull requests to GitHub. +Reporitng a Bug +--------------- + +If you enounter a problem when working with GeoServer, then please let us know through forum or mailing list above. -Responsible Disclosure +GeoServer uses the `Jira `_ Issue Tracker, to manage issue reports. In order to submit an issue, you'll need to `create an account first `_. -.. warning:: +Everyone is encouraged to submit pull-requests and, if possible, fix issues as well. - If you encounter a security vulnerability in GeoServer please take care to report the issue in a responsible fashion: +.. note:: + + As a popular program GeoServer often excheeds the number of accounts available to open source projects. So if you cannot get in please let us know and we will review unused accounts. - * Keep exploit details out of issue report (send to developer/PSC privately – just like you would do for sensitive sample data) - * Mark the issue as a vulnerability. - * Be prepared to work with Project Steering Committee (PSC) members on a solution +.. warning:: Coordinated Vulnerability Disclosure - Keep in mind PSC members are volunteers and an extensive fix may require fundraising / resources + If you encounter a security vulnerability in GeoServer please keep in mind our `Coordinated Vunerability Disclosue `__ policy: -If you are not in position to communicate in public please consider commercial support, contacting a PSC member, or reaching us via the Open Source Geospatial Foundation at info@osgeo.org. + * Keep exploit details out of public forums, mailing list and issue tracker. + + Send details to `geoserver-security@lists.osgeo.org `__. This is a moderated list: send directly to the address; your email will be moderated; and eventually shared with volunteers. + + Or directly use GitHub `private vunerablity reporting `_. + + * There is no expected response time. Be prepared to work with Be prepared to work with geoserver-security email list volunteers on a solution. + * Keep in mind participants are volunteering their time, an extensive fix may require fundraising/resources. + +If you are not in position to communicate in public, please consider `commercial support `__, contacting a Project Steering Committee member, or reaching us via the Open Source Geospatial Foundation at `info@osgeo.org `__. Translation ----------- -We would like GeoServer available in as many languages as possible. The two areas of GeoServer to translate are the text that appears in the :ref:`web_admin` and this documentation. If you are interested in helping with this task, please let us know via the mailing lists. +We would like GeoServer available in as many languages as possible. The two areas of GeoServer to translate are the text that appears in the :ref:`web_admin` and this documentation. + +If you are interested in helping with this task, please read the `translation `__ seciton of the developers manual, and let us know via communication channels above. Suggest improvements -------------------- -If you have suggestions as to how we can make GeoServer better, we would love to hear them. You can contact us through the mailing lists or submit a feature request through JIRA. +If you have suggestions as to how we can make GeoServer better, we would love to hear them. You can contact us through the mailing lists or submit a feature request through Jira. Spread the word --------------- A further way to help out the GeoServer project is to spread the word. Word-of-mouth information sharing is more powerful than any marketing, and the more people who use our software, the better it will become. +We also gladly accept `blog posts `__ from community members for the GeoServer website. If you have a fun example of using GeoServer to share please volunteer to write a blog post. + Fund improvements ----------------- A final way to help out is to push for GeoServer to be used in your own organization. A number of :website:`commercial organizations ` offer support for GeoServer, and any improvements made due to that funding will benefit the entire GeoServer community. + +* Core Contributors: Have both expertese in GeoServer development and have made a committment to the projects long term sustainability. These + +* Experienced Providers: Have a clear track record of successfully contirbuting changes back into the project as a long term improvements. + +Sponsorship and Donations +------------------------- + +GeoServer accepts sponsorship and donations through the Open Source Geospatial Foundation to take on activities beyond the reach of any single developer or organisation. + +For more information see `GeoServer Sponsorship `_. +