8 It is possible to communicate with other community members using mail and IRC.
9 All project related communication should be done on public channels that are
10 archived and easily browsable. Specific problems and tasks may be resolved
11 using direct means of communication.
16 The project offers the following mailing lists
18 . https://lists.infradead.org/mailman/listinfo/lede-dev[lede-dev@lists.infradead.org] -
19 This list is used for submitting patches and general development related work
20 . https://lists.infradead.org/mailman/listinfo/lede-adm[lede-adm@lists.infradead.org] -
21 This list is used for project organisational purposes. Anyone can
22 subscribe and read this list, only committers may write to this list.
24 In addition there are two read only announcement lists:
26 . http://lists.infradead.org/mailman/listinfo/lede-bugs[lede-bugs@lists.infradead.org] -
27 This list receives bug tracking notifications from Flyspray
28 . http://lists.infradead.org/mailman/listinfo/lede-commits[lede-commits@lists.infradead.org] -
29 This list tracks the commits to our core Git repositories
34 The project provides 2 IRC channels on freenode
36 . #lede-dev - a public channel for everyone to join and participate
37 . #lede-adm - a moderated channel that anyone can join but only people with +v flag can write on
42 In case of services going down, being moved or being unreachable for any other
43 reason, please go to twitter and see what the status is. The project will do
44 its best to post updates link:https://twitter.com/lede_project[here]
49 Please direct general inquiries to
50 link:mailto:lede-contact@lede-project.org[lede-contact@lede-project.org] in order
51 to confidentially get in touch with the link:about.html#people[project developers].
53 Note that this contact is primarily intented to find a suitable mode of
54 cooperation and to inquire about project matters without having to disclose
55 your corporate identity upfront. There will be no special treatment beyond the
56 "first contact". Please see the project link:rules.html[rules] for further
59 Actual development should happen in public and corporations are strongly
60 encouraged to send their contributions through the public mailing lists or in
61 the form of Github pull requests.
65 We attempt to have regular IRC meetings to discuss and decide project matters.
69 The next meeting date is yet to be decided.
71 For the agenda of the upcoming meeting refer to the
72 http://piratepad.net/ep/pad/view/ro.UdKV08dIlKx/latest[agenda pad].
76 All meeting logs can be viewed under http://meetings.lede-project.org/lede-adm/[here]