The main code repository is under the EdgeVPNio organization in GitHub, where you can also find code releases and packages

Docker containers can be found in the EdgeVPNio organization in DockerHub

How to Contribute

We welcome community involvement and participation in all aspects of the project. There are several meaningful ways for external participants to contribute. Below we discuss the ways that we can benefit from your contributions and effective ways of going about this.

Troubleshooting Bugs

Please refer to the troubleshooting page for helpful hints and information on how to troubleshoot and submit bug reports.

Enhancements and Feature Suggestions

While using our software you may envision new and interesting ways that it can be used. As a research group we are always excited to hear these ideas - please get in touch with us, let us know, and join the user’s group and developer’s Slack channel. We have finite resources and cannot guarantee that any requested feature will be implemented, but others in the community could be interested.

How you use

Tell us about how you use our software, particularly so if you think you are using it way we haven’t explicitly documented. Additionally, if have a development dependency – or you integrate our software with your own, we would love to hear from you.

Updating the Wiki Documentation

We try to make keep our documentation in the Wiki current, accurate and succinct. If you encounter inaccuracies or ambiguities, please make an update and send us the pull request.

Contributing Code

There is always more code to write than we can get to as quickly as we like. If you have an interest in Python, C++, SDN, and system level network development you may want to participate in developing some of new features of the software.

We generally attempt to adhere the Google Style Guides for C++ and Python

We have one master version of the software. This software product is tested and subjected to a high degree of code review. In order for code to make it into the master version, it must be submitted for code review. Once a project member other than the author has reviewed the code, the code is accepted into our testing branch. Once the code has passed a rigorous suite of tests, it is moved into the master branch. Periodically, packaged releases and containers are made from the master branch.

Porting and Packaging for new Platforms

We are also very interested in having ported to as many platforms as possible. If you don’t see a platform you use being supported, and would like to work on porting one, please get in touch with us, let us know, and join the user’s group and developer’s Slack channel.