| 18 | | 1) It is considered that most developers interested by GDAL development |
| 19 | | |
| 20 | | |
| 21 | | 2) The https://github.com/OSGeo/gdal mirror has existed since 2012 and has |
| 22 | | |
| 23 | | |
| 24 | | |
| 25 | | |
| 26 | | |
| 27 | | |
| 28 | | |
| 29 | | 3) GitHub has become the de-facto hosting platform for a lot of open-source |
| 30 | | |
| | 18 | 1. It is considered that most developers interested by GDAL development |
| | 19 | are nowadays more used to git than Subversion, and the use of Subversion |
| | 20 | as the main source control management makes contributions less attractive. |
| | 21 | 2. The https://github.com/OSGeo/gdal mirror has existed since 2012 and has |
| | 22 | over time become the prefered way for contributors without direct SVN access |
| | 23 | (or even those with SVN access) to submit their contributions, in particular |
| | 24 | because of the coupling with the continuous integratations services of Travis-CI |
| | 25 | and AppVeyor that enable maintainers to check that the contribution doesn't |
| | 26 | introduce known regressions + the friendly way of commenting a pull request. |
| | 27 | However the manual porting of GitHub pull requests to Trac is a bit painful |
| | 28 | for GDAL maintainers. |
| | 29 | 3. GitHub has become the de-facto hosting platform for a lot of open-source |
| | 30 | projects. |
