1// -*- mode:doc; -*- 2// vim: set syntax=asciidoc: 3 4[[community-resources]] 5== Community resources 6 7Like any open source project, Buildroot has different ways to share 8information in its community and outside. 9 10Each of those ways may interest you if you are looking for some help, 11want to understand Buildroot or contribute to the project. 12 13Mailing List:: 14+ 15Buildroot has a mailing list for discussion and development. It is the 16main method of interaction for Buildroot users and developers. 17+ 18Only subscribers to the Buildroot mailing list are allowed to post to 19this list. You can subscribe via the 20http://lists.buildroot.org/mailman/listinfo/buildroot[mailing list info 21page]. 22+ 23Mails that are sent to the mailing list are also available in the 24mailing list archives, available through 25http://lists.buildroot.org/pipermail/buildroot[Mailman] or at 26https://lore.kernel.org/buildroot/[lore.kernel.org]. 27 28IRC:: 29+ 30The Buildroot IRC channel irc://irc.oftc.net/#buildroot[#buildroot] is 31hosted on https://www.oftc.net/WebChat/[OFTC]. It is a useful place to 32ask quick questions or discuss on certain topics. 33+ 34When asking for help on IRC, share relevant logs or pieces of code 35using a code sharing website, such as https://paste.ack.tf/. 36+ 37Note that for certain questions, posting to the mailing list may be 38better as it will reach more people, both developers and users. 39 40Bug tracker:: 41+ 42Bugs in Buildroot can be reported via the mailing list or alternatively 43via the https://bugs.buildroot.org/buglist.cgi?product=buildroot[Buildroot 44bugtracker]. Please refer to xref:reporting-bugs[] before creating a bug 45report. 46 47Wiki:: 48+ 49http://elinux.org/Buildroot[The Buildroot wiki page] is hosted on 50the http://elinux.org[eLinux] wiki. It contains some useful links, an 51overview of past and upcoming events, and a TODO list. 52 53Patchwork:: 54+ 55Patchwork is a web-based patch tracking system designed to facilitate 56the contribution and management of contributions to an open-source 57project. Patches that have been sent to a mailing list are \'caught' by 58the system, and appear on a web page. Any comments posted that 59reference the patch are appended to the patch page too. For more 60information on Patchwork see 61http://jk.ozlabs.org/projects/patchwork/[]. 62+ 63Buildroot's Patchwork website is mainly for use by Buildroot's 64maintainer to ensure patches aren't missed. It is also used by Buildroot 65patch reviewers (see also xref:apply-patches-patchwork[]). 66However, since the website exposes patches and their corresponding 67review comments in a clean and concise web interface, it can be useful 68for all Buildroot developers. 69+ 70The Buildroot patch management interface is available at 71http://patchwork.buildroot.org[]. 72