Changes between Version 9 and Version 10 of HowToContribute

Timestamp:

Mar 24, 2018, 11:46:54 AM (6 years ago)

Author:

Mateusz Łoskot

Comment:

Update after migration to GitHub

HowToContribute

@@ -3 +3 @@
 Using the Ticket system is the best way to submit code contributions. If you are looking for examples, follow ticket numbers to see how GeoJSON (#1968) or GPX (#1515) drivers have been incorporated.
 
-New functions should be developed against latest developement version ("trunk" lying at http://svn.osgeo.org/gdal/trunk/gdal).
+New functions should be developed against latest development version in "master" branch of the official git repository at https://github.com/OSGeo/gdal).
 
-Create a new Ticket of ''type: enhancement'' and now we refer to this ticket when submitting driver code, driver test cases, changes to the building configuration required for the new driver, etc. So, we can track all necessary updates and changes in one place, using a single Ticket. After a new driver is incorporated and well tested, we can annotate and close the ticket.
+Contributions may be proposed following the usual [https://help.github.com/articles/github-flow/ GitHub workflow] and submitted as pull requests.
 
-Contributions may also be proposed as pull requests against the git mirror hosted at https://github.com/OSGeo/gdal
+Please, submit new pull request with a new driver code, driver test cases, changes to the building configuration required for the new driver, etc. So, we can track all necessary updates and changes in one place. After a new driver is incorporated and well tested, we can annotate and close the pull request.
 
 Code contribution shall be done under the MIT/X license in order to be incorporated into GDAL/OGR baseline. Refer to the Legal paragraph of [http://trac.osgeo.org/gdal/wiki/rfc3_commiters RFC3] for more details.
@@ -19 +19 @@
 Contribute to the wiki, improving documentation, providing examples, etc.
 
-File quality bug reports in Trac when you observe errors.  The greatest value comes from boiling down the problem to the minimum manifestation with small data files such that a developer/maintainer can very easily reproduce the error. 
+File quality bug reports using GitHub issues when you observe errors.  The greatest value comes from boiling down the problem to the minimum manifestation with small data files such that a developer/maintainer can very easily reproduce the error.