resources.txt 2.8 KB

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