| 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273 | // -*- mode:doc; -*-// vim: set syntax=asciidoc:[[community-resources]]== Community resourcesLike any open source project, Buildroot has different ways to shareinformation in its community and outside.Each of those ways may interest you if you are looking for some help,want to understand Buildroot or contribute to the project.Mailing List::+Buildroot has a mailing list for discussion and development. It is themain method of interaction for Buildroot users and developers.+Only subscribers to the Buildroot mailing list are allowed to post tothis list. You can subscribe via thehttp://lists.buildroot.org/mailman/listinfo/buildroot[mailing list infopage].+Mails that are sent to the mailing list are also available in thehttp://lists.buildroot.org/pipermail/buildroot[mailing list archives] andvia http://gmane.org[Gmane], athttp://dir.gmane.org/gmane.comp.lib.uclibc.buildroot[+gmane.comp.lib.uclibc.buildroot+].Please search the mailing list archives before asking questions, sincethere is a good chance someone else has asked the same question before.IRC::+The Buildroot IRC channel irc://freenode.net/#buildroot[#buildroot] ishosted on http://webchat.freenode.net[Freenode]. It is a useful place toask quick questions or discuss on certain topics.+When asking for help on IRC, share relevant logs or pieces of codeusing a code sharing website, such as http://code.bulix.org.+Note that for certain questions, posting to the mailing list may bebetter as it will reach more people, both developers and users.Bug tracker::+Bugs in Buildroot can be reported via the mailing list or alternativelyvia the https://bugs.buildroot.org/buglist.cgi?product=buildroot[Buildrootbugtracker]. Please refer to xref:reporting-bugs[] before creating a bugreport.Wiki::+http://elinux.org/Buildroot[The Buildroot wiki page] is hosted onthe http://elinux.org[eLinux] wiki. It contains some useful links, anoverview of past and upcoming events, and a TODO list.Patchwork::+Patchwork is a web-based patch tracking system designed to facilitatethe contribution and management of contributions to an open-sourceproject. Patches that have been sent to a mailing list are \'caught' bythe system, and appear on a web page. Any comments posted thatreference the patch are appended to the patch page too. For moreinformation on Patchwork seehttp://jk.ozlabs.org/projects/patchwork/[].+Buildroot's Patchwork website is mainly for use by Buildroot'smaintainer to ensure patches aren't missed. It is also used by Buildrootpatch reviewers (see also xref:apply-patches-patchwork[]).However, since the website exposes patches and their correspondingreview comments in a clean and concise web interface, it can be usefulfor all Buildroot developers.+The Buildroot patch management interface is available athttp://patchwork.buildroot.org[].
 |