File: CONTRIBUTING.md

package info (click to toggle)
postgis 3.6.1%2Bdfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 74,932 kB
  • sloc: ansic: 163,470; sql: 96,119; xml: 54,359; cpp: 12,646; perl: 5,875; sh: 5,415; makefile: 3,507; python: 1,207; yacc: 447; lex: 151; pascal: 58
file content (19 lines) | stat: -rw-r--r-- 1,028 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
PostGIS development planning happens via a [Trac instance](https://trac.osgeo.org/postgis/).

In order for proper scheduling of contributions acceptance/merging it
is recommended to file a ticket there and add your patch or a link
to a patch or to a public git branch where your development is ongoing.

Filing a ticket requires setting up an OSGeo account, which lets you
contribute to every project of the [Open Source Geospatial Foundation](http://www.osgeo.org/).

As we understand you might not want to setup a new account, simply
filing a pull request on one of the [PostGIS code mirrors](https://trac.osgeo.org/postgis/wiki/CodeMirrors) is also welcome,
but it is easier for such contributions to miss our radars unless
it _also_ has a matching Trac ticket.

If you intend to be involved for more than an occasional patch we
recommend you to subscribe to the [development mailing list](https://lists.osgeo.org/mailman/listinfo/postgis-devel).

Note that We also welcome
[git patches via email](https://git-send-email.io)