3 Have you used tinc? Do you like it? Is there something missing? There are
4 various ways you can help to make tinc even better:
7 Don't hesitate to [[send|contact]] in a bug report.
8 If we don't know about a bug, we cannot fix it.
9 It is also fine to report a bug that has already been reported,
10 that way we can determine how many people are affected by it.
12 * **Improve and/or translate the documentation.**
13 Is there anything missing in the documentation?
14 Do you think some parts are hard to understand and could be written better?
15 Feel free to send improvements for the documentation.
16 The documentation comes in several forms:
17 * Manpages, these are reference manuals for the binaries and configuration files.
18 * The [[manual|docs]], which contains also contains introductions and explainations about how tinc works and how you can set it up.
19 * The [[examples]] on the wiki, which describe how to set up tinc in various scenatios.
21 * **Test development versions of tinc.**
22 Tinc is continuously being improved.
23 There are two branches of development; the stable branch (version 1.0.x), and the 1.1 branch.
24 The code for these versions can be found in the [[repository]].
26 * **Port and maintain tinc on your favorite OS/device.**
27 There are many software and hardware [[platforms]] that tinc will run on.
28 However, the main developers cannot test tinc on all of them.
29 We can use people who test new versions of tinc on their favorite operating system, distribution or hardware device,
30 and report or fix any problems they encounter.
31 Furthermore, if your OS distribution does not come with a native package for tinc,
32 you are welcome to create and maintain such a package.
33 In particular, we are looking for maintainers for:
38 * **Help writing code.**
39 If you know C and would like to help improve tinc, [[let us know|contact]].
40 There will always be something to work on.
41 You can send patches in any way you like, either directly via [[email|contact]],
42 or you can clone the [[Git repository|repository]] and send us a pull request.
43 Please keep your code in the same style as existing code, which is mostly following
44 the [Linux kernel coding style](https://www.kernel.org/doc/Documentation/CodingStyle) (indent using real TAB characters).
47 Monetary contributions are also welcome.
48 Use the Paypal link in the sidebar to donate.
49 Your contribution will be used to cover the costs of the domain names,
50 backup infrastructure, and possibly to buy hardware to port tinc to.