| | 1 | This page is a step by step guide for contributing to PostGIS |
| | 2 | |
| | 3 | |
| | 4 | ---- |
| | 5 | Workflow: |
| | 6 | - Fork https://github.com/postgis/postgis |
| | 7 | - clone the forked postgis on your computer |
| | 8 | - compile (everything should be ok) |
| | 9 | - if big new feature |
| | 10 | * discuss on the dev mailing list or on irc.freenode.org #postgis |
| | 11 | - if bug correction |
| | 12 | * create / update tickets |
| | 13 | - if minor changes (no API break) |
| | 14 | * directly work on it |
| | 15 | - in all case : create a branch with a telling name (what you will be working on) |
| | 16 | - to code |
| | 17 | * start from SQL looking for the function definition and the associated C function |
| | 18 | * look for C function in postgis sources, and look if the postgis function calls a libgeom function |
| | 19 | * etc |
| | 20 | - to test |
| | 21 | * if libgeom : CUnit |
| | 22 | * test at the postgres level. |
| | 23 | ---- |
| | 24 | |
