Changes between Version 10 and Version 11 of HowToContribute

Timestamp:

Oct 5, 2018, 12:18:25 PM (6 years ago)

Author:

Even Rouault

Comment:

Update to reflect github workflow

HowToContribute

@@ -1 +1 @@
 == Developers ==
-
-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 development version in "master" branch of the official git repository at https://github.com/OSGeo/gdal).
 
-Contributions may be proposed following the usual [https://help.github.com/articles/github-flow/ GitHub workflow] and submitted as pull requests.
+Contributions are preferably proposed following the usual [https://help.github.com/articles/github-flow/ GitHub workflow] and submitted as pull requests against the latest development version in "master" branch of the official git repository 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.
@@ -19 +17 @@
 Contribute to the wiki, improving documentation, providing examples, etc.
 
-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. 
+File quality bug reports using GitHub issues at https://github.com/OSGeo/gdal/issues/new 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. 
+
+Note: the old ticket database in https://trac.osgeo.org/gdal/report/1 is no longer open for new tickets. New tickets should got to GitHub issues
 
 
-