get-involved.txt 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134
  1. // -*- mode:doc; -*-
  2. // vim: set syntax=asciidoc:
  3. Getting involved
  4. ================
  5. Like any open source project, Buildroot has different ways to share
  6. information in its community and outside.
  7. One piece of it is the document you are currently reading ;-).
  8. Each of those ways may interest you if you are looking for some help,
  9. want to understand Buildroot or contribute to the project.
  10. Mailing List
  11. ------------
  12. Buildroot has a mailing list
  13. http://lists.busybox.net/pipermail/buildroot[] for discussion and
  14. development.
  15. [[mailing-list-subscribe]]
  16. Subscribing to the mailing list
  17. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  18. You can subscribe by visiting
  19. http://lists.busybox.net/mailman/listinfo/buildroot[].
  20. Only subscribers to the Buildroot mailing list are allowed to post to
  21. this list.
  22. The list is also available through _Gmane_ http://gmane.org[], at
  23. +gmane.comp.lib.uclibc.buildroot+
  24. http://dir.gmane.org/gmane.comp.lib.uclibc.buildroot[].
  25. Searching the List Archives
  26. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  27. Please search the mailing list archives before asking questions on the
  28. mailing list, since there is a good chance someone else has asked the
  29. same question before. Checking the archives is a great way to avoid
  30. annoying everyone on the list with frequently asked questions...
  31. IRC
  32. ---
  33. The Buildroot IRC is irc://freenode.net/#buildroot[].
  34. The channel +#buildroot+ is hosted on Freenode
  35. http://webchat.freenode.net[].
  36. When asking for help on IRC, share relevant logs or pieces of code
  37. using a code sharing website.
  38. [[patchwork]]
  39. Patchwork
  40. ---------
  41. Patchwork is a web-based patch tracking system designed to facilitate
  42. the contribution and management of contributions to an open-source
  43. project. Patches that have been sent to a mailing list are \'caught' by
  44. the system, and appear on a web page. Any comments posted that
  45. reference the patch are appended to the patch page too. For more
  46. information on Patchwork see
  47. http://jk.ozlabs.org/projects/patchwork[].
  48. Buildroot's Patchwork website is mainly for use by Buildroot's
  49. maintainer to ensure patches aren't missed. The website however,
  50. exposes patches and their corresponding review comments in a clean
  51. and concise web interface.
  52. The Buildroot patch management interface is available at
  53. http://patchwork.buildroot.org[].
  54. [[apply-patches-patchwork]]
  55. Applying Patches from Patchwork
  56. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  57. The main use of Buildroot's Patchwork website for a developer is for
  58. pulling in patches into their local git repository for testing
  59. purposes.
  60. When browsing patches in the patchwork management interface, an +mbox+
  61. link is provided at the top of the page. Copy this link address and
  62. run the following commands:
  63. ---------------------
  64. $ git checkout -b <test-branch-name>
  65. $ wget -O - <mbox-url> | git am
  66. ---------------------
  67. Another option for applying patches is to create a bundle. A bundle is
  68. a set of patches that you can group together using the patchwork
  69. interface. Once the bundle is created and the bundle is made public,
  70. you can copy the +mbox+ link for the bundle and apply the bundle
  71. using the above commands.
  72. [[bugtracker]]
  73. Bugtracker
  74. ----------
  75. The Buildroot bugtracker is at https://bugs.busybox.net[].
  76. To open a bug, see xref:reporting-bugs[].
  77. Buildroot wikipage
  78. ------------------
  79. After the Buildroot developer day on February 3, 2012,
  80. a page dedicated to Buildroot has been created on
  81. http://elinux.org[elinux.org].
  82. This page is reachable at http://elinux.org/Buildroot[].
  83. Currently, this page is mainly used as a _todo-list_.
  84. [[events]]
  85. Events
  86. ------
  87. Buildroot Developer Days aside ELC-E 2012 (November 3-4, 2012 - Barcelona)
  88. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  89. * Event page: http://elinux.org/Buildroot:DeveloperDaysELCE2012[]
  90. Buildroot presentation at LSM 2012 (July 12-14, 2012 - Geneva)
  91. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  92. * Announcement: http://lists.busybox.net/pipermail/buildroot/2012-May/053845.html[]
  93. Buildroot Developer Days aside FOSDEM 2012 (February 3, 2012 - Brussels)
  94. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  95. * Announcement & agenda thread: http://lists.busybox.net/pipermail/buildroot/2012-January/049340.html[]
  96. * Report: http://lists.busybox.net/pipermail/buildroot/2012-February/050371.html[]