get-involved.txt 2.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100
  1. // -*- mode:doc; -*-
  2. Getting involved
  3. ================
  4. Like any open source project, Buildroot has different ways to share
  5. information in its community and outside.
  6. One piece of it is the document you are currently reading ;-).
  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
  12. http://lists.busybox.net/pipermail/buildroot[] for discussion and
  13. development.
  14. [[mailing-list-subscribe]]
  15. Subscribing to the mailing list
  16. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  17. You can subscribe by visiting
  18. http://lists.busybox.net/mailman/listinfo/buildroot[].
  19. Only subscribers to the Buildroot mailing list are allowed to post to
  20. this list.
  21. The list is also available through _Gmane_ http://gmane.org[], at
  22. +gmane.comp.lib.uclibc.buildroot+
  23. http://dir.gmane.org/gmane.comp.lib.uclibc.buildroot[].
  24. Searching the List Archives
  25. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  26. Please search the mailing list archives before asking questions on the
  27. mailing list, since there is a good chance someone else has asked the
  28. same question before. Checking the archives is a great way to avoid
  29. annoying everyone on the list with frequently asked questions...
  30. IRC
  31. ---
  32. The Buildroot IRC is irc://freenode.net/#buildroot[].
  33. The channel +#buildroot+ is hosted on Freenode
  34. http://webchat.freenode.net[].
  35. When asking for help on IRC, share relevant logs or pieces of code
  36. using a code sharing website.
  37. [[patchwork]]
  38. Patchwork
  39. ---------
  40. The Buildroot patch management interface is at
  41. http://patchwork.buildroot.org[].
  42. All patches and comments sent through the mailing list are
  43. automatically indexed in http://patchwork.buildroot.org[patchwork].
  44. [[bugtracker]]
  45. Bugtracker
  46. ----------
  47. The Buildroot bugtracker is at https://bugs.busybox.net[].
  48. To open a bug, see xref:reporting-bugs[].
  49. Buildroot wikipage
  50. ------------------
  51. After the Buildroot developer day on February 3, 2012,
  52. a page dedicated to Buildroot has been created on
  53. http://elinux.org[elinux.org].
  54. This page is reachable at http://elinux.org/Buildroot[].
  55. Currently, this page is mainly used as a _todo-list_.
  56. [[events]]
  57. Events
  58. ------
  59. Buildroot Developer Days aside ELC-E 2012 (November 3-4, 2012 - Barcelona)
  60. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  61. * Event page: http://elinux.org/Buildroot:DeveloperDaysELCE2012[]
  62. Buildroot presentation at LSM 2012 (July 12-14, 2012 - Geneva)
  63. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  64. * Announcement: http://lists.busybox.net/pipermail/buildroot/2012-May/053845.html[]
  65. Buildroot Developer Days aside FOSDEM 2012 (February 3, 2012 - Brussels)
  66. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  67. * Announcement & agenda thread: http://lists.busybox.net/pipermail/buildroot/2012-January/049340.html[]
  68. * Report: http://lists.busybox.net/pipermail/buildroot/2012-February/050371.html[]