3 You can help in numerous ways. This document should give you an overview of what
4 is possible and how you can get involved. It will **not** give you all information
5 you need to successfully contribute to avoid content duplication between this
6 document and our [wiki](https://wiki.ipfire.org/). Instead, it should guide you
7 to the right places to look for further information.
11 All information is available in the [development section](https://wiki.ipfire.org/devel)
12 of our wiki. The following is a very short overview of the most important topics.
16 We use the mailing list `<development@lists.ipfire.org>` for our communication. For the
17 list archive and registration, see [here](http://lists.ipfire.org/mailman/listinfo/development).
21 We use our own infrastructure for code hosting, accessible at `git.ipfire.org`. The
22 GitHub repositories are **only** mirrors of `git.ipfire.org`, available as a courtesy
23 to the internet community.
25 ### How to build the distribution?
27 In order to contribute, you certainly need to build the distribution at some point.
28 See [here](https://wiki.ipfire.org/devel/ipfire-2-x/build-howto) for a long guide
33 We have a bug tracker located [here](https://wiki.ipfire.org/devel/bugzilla). Further
34 information can be found in our [wiki](https://wiki.ipfire.org/devel/bugzilla). We do
35 **not** use GitHub for tracking bugs.
37 ### Contribute changes to the source code
39 Unfortunately, we do not accept GitHub pull requests. Instead, we are working with patches
40 which are sent to our mailing list `<development@lists.ipfire.org>`. This process might
41 be a bit tricky in the beginning. That's why you can find more information how to do
42 this [here](https://wiki.ipfire.org/devel/submit-patches).