From e2c03da940507a30a61d573418e236ff9ddbc125 Mon Sep 17 00:00:00 2001 From: "Daniel P. Berrange" Date: Thu, 21 Jan 2010 16:48:11 +0100 Subject: [PATCH] Add docs about new mailing list * docs/contact.html.in: Document new users mailing list --- docs/contact.html.in | 45 ++++++++++++++++++++++++++++++++++++-------- 1 file changed, 37 insertions(+), 8 deletions(-) diff --git a/docs/contact.html.in b/docs/contact.html.in index 5d055b123e..09f8e35d82 100644 --- a/docs/contact.html.in +++ b/docs/contact.html.in @@ -3,16 +3,45 @@

Contacting the development team

-

Mailing list

+

Mailing lists

- There is a mailing-list libvir-list@redhat.com for libvirt, - with an on-line archive. - Please subscribe to this list before posting by visiting the - associated Web - page and follow the instructions. Patches with explanations and provided as - attachments are really appreciated and will be discussed on the mailing list. - If possible generate the patches by using git diff in a GIT + There are two mailing-lists: +

+ +
+
libvir-list@redhat.com
+
This list a place for discussions about the development of libvirt. Topics for discussion include +
    +
  • New features for libvirt
    • +
  • Bug fixing of libvirt
    • +
  • New hypervisor drivers
    • +
  • Development of language bindings for libvirt API
    • +
  • Testing and documentation of libvirt
    • +
+
+ +
libvirt-users@redhat.com
+
This list a place for discussions involving libvirt users. Topics for discussion include +
    +
  • Usage of libvirt / virsh
    • +
  • Administration of libvirtd
    • +
  • Deployment of libvirt with hypervisors
    • +
  • Development of applications on top of / using the libvirt API(s)
    • +
  • Any other topics along these lines
    • +
+
+
+ +

+ Both mailing lists require that you subscribe before posting to the list, + otherwise your posting will be delayed for manual approval by mailman. + You can subscribe at the linked webpages above. +

+

+ Patches with explanations and provided as attachments are really appreciated and should + be directed to the development mailing list will be discussed on the mailing list. + If possible generate the patches by using git format-patch in a GIT clone.