| | 1 | = Google Summer of Code 2022 == |
| | 2 | |
| | 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. |
| | 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 | * If you are looking for additional ideas, refer to our past GSOCS: |
| | 11 | * [wiki:GoogleSummerCode2019 Google Summer Of Code 2022] |
| | 12 | * [wiki:GoogleSummerCode2019 Google Summer Of Code 2019] |
| | 13 | * [wiki:GoogleSummerCode2018 Google Summer Of Code 2018] |
| | 14 | * [wiki:GoogleSummerCode Google Summer Of Code 2013] |
| | 15 | |
| | 16 | ** Improving your chances ** |
| | 17 | |
| | 18 | For most projects involving PostGIS you will eventually need the following: |
| | 19 | |
| | 20 | * Know how to install PostgreSQL |
| | 21 | * Know how to install PostGIS in PostgreSQL |
| | 22 | * Know how to compile PostgreSQL code |
| | 23 | * Know how to compile PostGIS code and run tests |
| | 24 | * Some basic knowledge of git -- at least how to do a git clone, git push, git pull and pull requests |
| | 25 | |
| | 26 | While you can learn to do these things and ask questions, we would prefer students to know these before starting on a PostGIS project. |
| | 27 | |
| | 28 | |
| | 29 | **Idea 1: Augment pgAdmin to support importing and exporting shapefiles** |
| | 30 | |
| | 31 | ''Expected outcome'': There should be a menu option in the pgAdmin browser tree whenever you right-click a database, table, or schema that allows you to import or export shapefiles. The tool would use the shp2pgsql and pgsql2shp commandlines that are part of the PostGIS source code in much the same way the backup and restore data browse menu options |
| | 32 | built into pgAdmin utilizes pg_dump / pg_restore. |
| | 33 | |
| | 34 | ''Skills required'': python, html, css, and javascript, ability to compile PostgreSQL code, ability to compile PostGIS code, ability to compile [https://git.postgresql.org/git/pgadmin4.git pgAdmin] |
| | 35 | some familiarity with PostGIS, PostgreSQL, and pgAdmin is preferable |
| | 36 | |
| | 37 | ''Mentors'': Regina Obe |
| | 38 | |
| | 39 | ''Difficulty'': Medium |
| | 40 | |
| | 41 | ``Student Test'': |
| | 42 | |
| | 43 | 1. git clone code from [https://git.postgresql.org/git/postgresql.git PostgreSQL] and compile |
| | 44 | 2. git clone PostGIS code from one of [wiki:CodeMirrors Git repos] and compile |
| | 45 | 3. git clone code from [https://git.postgresql.org/git/pgadmin4.git pgAdmin4] and compile |
| | 46 | 4. Create a working PostgreSQL database with postgis extension installed and |
| | 47 | 5. Setup a public fork of PostGIS repo for your work (can be [https://git.osgeo.org/gitea osgeo], [https://gitlab.com gitlab], [https://github.com github], or any other repo you can make available for public review) |
| | 48 | |
| | 49 | Since the above is all work in pgAdmin, installing PostGIS / postgis commandline tools from a repository is equally acceptable to doing (1,2) |
