1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
|
.. include:: header.rst
.. contents:: Table of contents
:depth: 2
:backlinks: none
contributing to libtorrent
==========================
There are several ways to contribute to libtorrent at various levels. Any help is
much appreciated. If you're interested in something libtorrent related that's not
enumerated on this page, please contact arvid@libtorrent.org or the `mailing list`_.
.. _`mailing list`: https://lists.sourceforge.net/lists/listinfo/libtorrent-discuss
1. Testing
This is not just limited to finding bugs and ways to reproduce crashes, but also
sub-optimal behavior is certain scenarios and finding ways to reproduce those. Please
report any issue to the bug tracker at `github`_.
New features that need testing are streaming (``set_piece_deadline()``), the different
choking algorithms (like the rate-based choker).
Additional fuzzers are also always welcome. Find a libtorrent interface
that's not already covered by a fuzzer (see the ``fuzzers`` directory in the
root) and add a new fuzzer to it. Alternatively, improve an existing fuzzer by
producing inputs that gets coverage deeper in to libtorrent.
.. _`github`: https://github.com/arvidn/libtorrent/issues
2. Documentation
Finding typos or outdated sections in the documentation. Contributing documentation
based on your own experience and experimentation with the library or with BitTorrent
in general. Non-reference documentation is very much welcome as well, higher level
descriptions on how to configure libtorrent for various situations for instance.
The reference documentation for libtorrent is generated from the header files.
Each heading in the online documentation has a short-cut link to file a new issue
against the documentation.
For updates, please submit a `pull request`_. All documentation is in
restructured text (rst_). All documentation is spell checked with hunspell
which can be invoked via ``make spell-check`` in the docs directory. If
words are missing, please add them to ``docs/hunspell/libtorrent.dic``
3. Code
Contributing code for new features or bug-fixes is highly welcome. If you're interested
in adding a feature but not sure where to start, please contact the `mailing list`_ or
``#libtorrent`` @ ``irc.freenode.net``. For proposed fixes or updates, please
submit a `pull request`_.
New features might be better support for integrating with other services, new choking
algorithms, seeding policies, ports to new platforms etc.
For an overview of the internals of libtorrent, see the hacking_ page.
For outstanding things to do, see the `todo list`_.
.. _hacking: hacking.html
.. _`pull request`: https://github.com/arvidn/libtorrent
.. _`todo list`: todo.html
.. _rst: https://docutils.sourceforge.io/rst.html
|
