| 3 | | **Augment PostGIS 3.2 with GIST support added to PG14** |
| | 3 | ** Introduction ** |
| | 4 | |
| | 5 | So you are interested in becoming a Google Summer of Code student. What should you do to improve your chances of being selected? We recommend reading |
| | 6 | |
| | 7 | * [https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students OSGeo's GSoC Recommendations for Students] |
| | 8 | * We currently have one project in mind listed below, with a mentor ready to help - refer to Idea 1 below. We are open to other ideas, but Idea 1 takes precedence since we already have a mentor for that. |
| | 9 | * Join the [https://lists.osgeo.org/mailman/listinfo/postgis-devel PostGIS Developers list] and describe your proposed project (or willingness to work on Idea 1 listed below). We will let you know if we think the project is worthwhile and doable within the allotted time you have. |
| | 10 | |
| | 11 | ** Improving your chances ** |
| | 12 | |
| | 13 | For most projects involving PostGIS you will eventually need the following: |
| | 14 | |
| | 15 | * Know how to install PostgreSQL |
| | 16 | * Know how to install PostGIS in PostgreSQL |
| | 17 | * Know how to compile PostgreSQL code |
| | 18 | * Know how to compile PostGIS code and run tests |
| | 19 | * Some basic knowledge of git -- at least how to do a git clone, git push, git pull and pull requests |
| | 20 | |
| | 21 | While you can learn to do these things and ask questions, we would prefer students to know these before starting on a PostGIS project. |
| | 22 | |
| | 23 | |
| | 24 | **Idea 1: Augment PostGIS 3.2 with GIST support added to PG14** |
