Initial Release: January 8, 2014.
Amendment #1: January 15, 2014.
Amendment #2: January 21, 2019.
(日本語版はこちら)
This policy defines our patch acceptance policy from contributors for SoftEther VPN.
Use GitHub to submit a patch
Sending a patch to us is very welcome and appreciated.
If you would like to send a patch for SoftEther VPN, please use the GitHub pull request function.
The GitHub repository URL is: https://github.com/SoftEtherVPN/SoftEtherVPN/
We are afraid that we cannot accept patches by other methods, in order to keep the consistency of the source-code tree.
Comply to the SoftEther VPN Developers Guideline
New contributions are subject to the following guidelines:
https://github.com/SoftEtherVPN/SoftEtherVPN/wiki/SoftEther-VPN-Developers-Guideline
Who decides the patch to be accepted or not?
The SoftEther VPN Project has the authority to decide whether or not to accept the received patch into the SoftEther VPN source code tree. We do not guarantee that any patch will be accepted by us.
What kind of patch will be rejected?
We would like to accept any patches. However, we have the right to reject any patch by our discretion.
The examples of patches which will be rejected are:
- A patch which contains bugs or other issues.
- A patch which degrades the quality or the functionality of SoftEther VPN.
- A patch which obviously has a copyright violation to any third person.
Please note that if your patch is rejected by us, you can publish it on your own forked project of SoftEther VPN, because SoftEther VPN is an Apache License 2.0 open-source project.
Treatment of copyright
As the consequence, anyone will be permitted to copy, modify or re-use your patch program under the Apache License 2.0 license.
Acknowledgment on AUTHORS.TXT for your credit
After your patch will be commited on the source-code tree, as a token of our gratitude, your GitHub username may be added on the AUTHORS.TXT file and on the header of the related source file. Please kindly append your name by yourself editing the text file.
