Blame
| fc329c | ordex | 2025-07-18 12:07:39 | 1 | # How To Contribute |
| 2 | ||||
| 3 | ## Linux |
|||
| 4 | ||||
| 5 | The DCO implementation on Linux is a kernel module called _ovpn_. |
|||
| 6 | ||||
| 7 | _ovpn_ has been merged in the Linux mainline repository and it's part of the |
|||
| 8 | offical kernel release since version 6.16. |
|||
| 9 | ||||
| 10 | For this reason all new features and bug-fixes must follow the Linux kernel |
|||
| 11 | development process and patches must adhere to the Linux kernel CodingStyle. |
|||
| 12 | ||||
| 13 | All patches for _ovpn_ are collected in the `ovpn-net-next` repository and then |
|||
| 14 | submitted to the Linux networking tree by the _ovpn_ maintainer (Antonio Quartulli |
|||
| 15 | at the time of writing). |
|||
| 16 | ||||
| 17 | ### Branches |
|||
| 18 | ||||
| 19 | To follow the Linux kernel development process, the `ovpn-net-next` repository |
|||
| 20 | provides 2 branches, namely `main` and `net`, which respectively track the upstream |
|||
| 21 | `net-next` and `net` tree. |
|||
| 22 | ||||
| 23 | Developers willing to send new features should based their changes on the `main` branch, |
|||
| 24 | while for bug fixes they should use `net`. |
|||
| 25 | ||||
| 26 | ### Sending patches |
|||
| 27 | ||||
| 28 | New patches for _ovpn_, being them new features or bug-fixes, should be sent to the |
|||
| 29 | openvpn-devel mailing list witht the specific subject `[PATCH ovpn-net-next]`, so that |
|||
| 30 | they can be picked up accordingly. |
