qemu: Move capability checks for IOMMU features
[libvirt/ericb.git] / docs / contact.html.in
blob7c2b71501a3a6c0fe362492f8eea3568bef35590
1 <?xml version="1.0" encoding="UTF-8"?>
2 <!DOCTYPE html>
3 <html xmlns="http://www.w3.org/1999/xhtml">
4 <body>
5 <h1>Contacting the project contributors</h1>
7 <ul id="toc"></ul>
9 <h2><a id="security">Security Issues</a></h2>
11 <p>
12 If you think that an issue with libvirt may have security
13 implications, <strong>please do not</strong> publicly
14 report it in the bug tracker, mailing lists, or irc. Libvirt
15 has <a href="securityprocess.html">a dedicated process for handling (potential) security issues</a>
16 that should be used instead. So if your issue has security
17 implications, ignore the rest of this page and follow the
18 <a href="securityprocess.html">security process</a> instead.
19 </p>
21 <h2><a id="email">Mailing lists</a></h2>
23 <p>
24 There are three mailing-lists:
25 </p>
27 <dl class="mail">
28 <dt><a href="https://www.redhat.com/mailman/listinfo/libvir-list">libvir-list@redhat.com</a> (for development)</dt>
29 <dd>
30 Archives at <a href="https://www.redhat.com/archives/libvir-list">https://www.redhat.com/archives/libvir-list</a>
31 </dd>
32 <dd>
33 This is a high volume mailing list. It is a place for discussions
34 about the <strong>development</strong> of libvirt.
35 </dd>
36 <dd>
37 Topics for discussion include:
38 <ul>
39 <li>New features for libvirt</li>
40 <li>Bug fixing of libvirt</li>
41 <li>New hypervisor drivers</li>
42 <li>Development of language bindings for libvirt API</li>
43 <li>Testing and documentation of libvirt</li>
44 </ul>
45 </dd>
47 <dt><a href="https://www.redhat.com/mailman/listinfo/libvirt-users">libvirt-users@redhat.com</a> (for users)</dt>
48 <dd>
49 Archives at <a href="https://www.redhat.com/archives/libvirt-users">https://www.redhat.com/archives/libvirt-users</a>
50 </dd>
51 <dd>
52 This is a moderate volume mailing list. It is a place for discussions
53 involving libvirt <strong>users</strong>.
54 </dd>
55 <dd>
56 Topics for discussion include:
57 <ul>
58 <li>Usage of libvirt / virsh</li>
59 <li>Administration of libvirt</li>
60 <li>Deployment of libvirt with hypervisors</li>
61 <li>Development of applications on top of / using the libvirt API(s)</li>
62 <li>Any other topics along these lines</li>
63 </ul>
64 </dd>
66 <dt><a href="https://www.redhat.com/mailman/listinfo/libvirt-announce">libvirt-announce@redhat.com</a> (for release notices)</dt>
67 <dd>
68 Archives at <a href="https://www.redhat.com/archives/libvirt-announce">https://www.redhat.com/archives/libvirt-announce</a>
69 </dd>
70 <dd>
71 This is a low volume mailing list, with restricted posting, for
72 announcements of new libvirt releases.
73 </dd>
74 <dd>
75 Subscribe to just this if you want to be notified of new releases,
76 without subscribing to either of the other mailing lists.
77 </dd>
79 </dl>
81 <p>
82 It is recommended but not required that you subscribe before posting
83 to the user and development lists. Posts from non-subscribers will be
84 subject to manual moderation delays. You can subscribe at the linked
85 web pages above.
86 </p>
87 <p>
88 Patches with explanations and provided as attachments are really
89 appreciated, and should be directed to the development mailing list
90 for review and discussion.
91 Wherever possible, please generate the patches by using
92 <code>git format-patch</code> in a git repository clone. Further
93 useful information regarding developing libvirt and/or contributing is
94 available on our <a href="hacking.html">Contributor Guidelines</a>
95 page.
96 </p>
98 <h2><a id="irc">IRC discussion</a></h2>
101 Some of the libvirt developers may be found on IRC on the <a href="http://oftc.net">OFTC IRC</a>
102 network. Use the settings:
103 </p>
104 <ul>
105 <li>server: irc.oftc.net</li>
106 <li>port: 6667 (the usual IRC port)</li>
107 <li>channel: #virt</li>
108 </ul>
110 NB There is no guarantee that someone will be watching or able to reply
111 promptly, so use the mailing-list if you don't get an answer on the IRC
112 channel.
113 </p>
115 </body>
116 </html>