We welcome contributions to the OGC API workshop, in the form of issues, bug fixes, documentation or suggestions for enhancements. This document sets out our guidelines and best practices for such contributions.
It's based on the Contributing to Open Source Projects Guide.
The OGC API workshop has the following modes of contribution:
- GitHub Commit Access
- GitHub Pull Requests
Contributors to this project are expected to act respectfully toward others in accordance with the OSGeo Code of Conduct.
Before submitting a bug, please do the following:
-
Perform basic troubleshooting steps:
- Make sure you're on the latest version. If you're not on the most recent version, your problem may have been solved already! Upgrading is always the best first step.
- Search the issue tracker to make sure it's not a known issue.
Make sure your report gets the attention it deserves: bug reports with missing information may be ignored or punted back to you, delaying a fix. The below constitutes a bare minimum; more info is almost always better:
- What version of Python are you using? For example, are you using Python 2.7, Python 3.7, PyPy 2.0?
- What operating system are you using? Windows (7, 8, 10, 32-bit, 64-bit), Mac OS X, (10.7.4, 10.9.0), GNU/Linux (which distribution, which version?) Again, more detail is better.
- Which version or versions of the software are you using? Ideally, you've followed the advice above and are on the latest version, but please confirm this.
- How can the we recreate your problem? Imagine that we have never used the OGC API workshop before and have downloaded it for the first time. Exactly what steps do we need to take to reproduce your problem?
Your contribution will be under our license as per GitHub's terms of service.
- Proposals to provide developers with GitHub commit access shall be emailed to the OGC API workshop GitHub issues. Proposals shall be approved by the OGC API workshop team. Committers shall be added by the project admin.
- Removal of commit access shall be handled in the same manner.
- Pull requests may include copyright in the source code header by the contributor if the contribution is significant or the contributor wants to claim copyright on their contribution.
- All contributors shall be listed at https://github.com/opengeospatial/ogcapi-workshop/graphs/contributors
- Unclaimed copyright, by default, is assigned to the main copyright holders as specified in https://github.com/opengeospatial/ogcapi-workshop/blob/main/LICENSE.md
-
Always make a new branch for your work, no matter how small. This makes it easy for others to take just that one set of changes from your repository, in case you have multiple unrelated changes floating around.
- Don't submit unrelated changes in the same branch/pull request! If it is not possible to review your changes quickly and easily, we may reject your request.
-
Base your new branch off of the appropriate branch on the main repository:
- In general the released version of the OGC API workshop is based on the
main(default) branch whereas development work is done under other non-default branches. Unless you are sure that your issue affects a non-default branch, base your branch off themainone.
- In general the released version of the OGC API workshop is based on the
-
Note that depending on how long it takes for the dev team to merge your patch, the copy of
mainyou worked off of may get out of date!- If you find yourself 'bumping' a pull request that's been sidelined for a
while, make sure you rebase or merge to latest
mainto ensure a speedier resolution.
- If you find yourself 'bumping' a pull request that's been sidelined for a
while, make sure you rebase or merge to latest
- documentation is managed in
workshop/content/docs/using , in Markdown format - MkDocs is used to generate the documentation
We welcome suggestions for enhancements, but reserve the right to reject them if they do not follow future plans for the OGC API workshop.