Commit fc329c
2025-07-18 12:07:39 ordex: -/-| /dev/null .. DataChannelOffload/How To Contribute.md | |
| @@ 0,0 1,30 @@ | |
| + | # How To Contribute |
| + | |
| + | ## Linux |
| + | |
| + | The DCO implementation on Linux is a kernel module called _ovpn_. |
| + | |
| + | _ovpn_ has been merged in the Linux mainline repository and it's part of the |
| + | offical kernel release since version 6.16. |
| + | |
| + | For this reason all new features and bug-fixes must follow the Linux kernel |
| + | development process and patches must adhere to the Linux kernel CodingStyle. |
| + | |
| + | All patches for _ovpn_ are collected in the `ovpn-net-next` repository and then |
| + | submitted to the Linux networking tree by the _ovpn_ maintainer (Antonio Quartulli |
| + | at the time of writing). |
| + | |
| + | ### Branches |
| + | |
| + | To follow the Linux kernel development process, the `ovpn-net-next` repository |
| + | provides 2 branches, namely `main` and `net`, which respectively track the upstream |
| + | `net-next` and `net` tree. |
| + | |
| + | Developers willing to send new features should based their changes on the `main` branch, |
| + | while for bug fixes they should use `net`. |
| + | |
| + | ### Sending patches |
| + | |
| + | New patches for _ovpn_, being them new features or bug-fixes, should be sent to the |
| + | openvpn-devel mailing list witht the specific subject `[PATCH ovpn-net-next]`, so that |
| + | they can be picked up accordingly. |