We are really glad you are reading this because we need volunteer developers to help with this project.
If you have not already, come find us on
or contact us via discourse.
We want you to work on things you're excited about. Drop a message and if someone can assist you, will contact you back ASAP.
Here are some important resources:
- Participate in the discourse discussions
- Find a bug? Open an issue.
Any kind of contribution will automatically fall to the following Licences:
-
Code contribution: GNU General Public License v2.0 or later,
- Directly by making an explicit pull request.
- Indirectly by posting code on issues/wiki/gitter/discourse
-
Documentation contribution:
- Creative Commons Attribution-Share Alike 3.0
-
We need a contribution agreement when you are working in a company that develops software.
Contributions developed for an employer or as part of a work project also fall under the above licences. This should be cleared with an authorized supervisor or manager in advance.
Contributions should be developed by the contributor, from the public domain, or from an open source project under a compatible licence. If the code does not come from the contributor, the original source should be clearly marked.
Do not remove existing copyright headers and licence text from contributions. If the copyright holder wants to give up copyright, they must do so in writing before any copyright messages are deleted.
Write a clear log message for your commits. One-line messages are fine for small changes, but bigger changes should have more information.
Fill in the commit message template.
Start reading our code and you'll get the hang of it. We optimize for readability.
This is open source software. Consider the people who will read your code, and make it look nice for them.
- Use editorconfig on your editor to get the coding conventions
Thanks, pgRouting team