[libvirt] [PATCH] Add docs about new mailing list
* docs/contact.html.in: Document new users mailing list --- docs/contact.html.in | 43 ++++++++++++++++++++++++++++++++++++------- 1 files changed, 36 insertions(+), 7 deletions(-) diff --git a/docs/contact.html.in b/docs/contact.html.in index 5d055b1..3a0d439 100644 --- a/docs/contact.html.in +++ b/docs/contact.html.in @@ -3,15 +3,44 @@ <body> <h1>Contacting the development team</h1> - <h2>Mailing list</h2> + <h2>Mailing lists</h2> <p> - There is a mailing-list <a href="mailto:libvir-list@redhat.com">libvir-list@redhat.com</a> for libvirt, - with an <a href="https://www.redhat.com/archives/libvir-list/">on-line archive</a>. - Please subscribe to this list before posting by visiting the - <a href="https://www.redhat.com/mailman/listinfo/libvir-list">associated Web</a> - page and follow the instructions. Patches with explanations and provided as - attachments are really appreciated and will be discussed on the mailing list. + There are two mailing-lists: + </p> + + <dl> + <dt><a href="https://www.redhat.com/archives/libvir-list/">libvir-list@redhat.com</a></dt> + <dd>This list a place for discussions about the <strong>development</strong> of libvirt. Topics for discussion include + <ul> + <li>New features for libvirt</li> + <li>Bug fixing of libvirt</li> + <li>New hypervisor drivers</li> + <li>Development of language bindings for libvirt API</li> + <li>Testing and documentation of libvirt</li> + </ul> + </dd> + + <dt><a href="">libvirt-users@redhat.com</a></dt> + <dd>This list a place for discussions involving libvirt <strong>users</strong>. Topics for discussion include + <ul> + <li>Usage of libvirt / virsh</li> + <li>Administration of libvirtd</li> + <li>Deployment of libvirt with hypervisors</li> + <li>Development of applications on top of / using the libvirt API(s)</li> + <li>Any other topics along these lines</li> + </ul> + </dd> + </dl> + + <p> + Both mailing lists require that you <strong>subscribe before posting to the list</strong>, + otherwise your posting will be blocked by mailman. You can subscribe at the linked webpages + above. + </p> + <p> + 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 <code>git diff</code> in a GIT clone. </p> -- 1.6.2.5
Daniel P. Berrange wrote:
* docs/contact.html.in: Document new users mailing list ... Sounds good.
+ <p> + Both mailing lists require that you <strong>subscribe before posting to the list</strong>,
Since both lists are using listhelper, http://savannah.gnu.org/maintenance/ListHelperAntiSpam it is now possible to remove the subscribe-before-posting requirement. If we remove it, that makes it easier for people to send their first post. Now, that may not always be such a good thing ;-) but at least it won't result in spam.
+ otherwise your posting will be blocked by mailman. You can subscribe at the linked webpages + above.
Perhaps say "delayed for manual approval" rather than blocked?
+ </p> + <p> + 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 <code>git diff</code> in a GIT clone. </p>
Minor wording fix, and say we prefer "git format-patch", rather than "git diff" output, since the former can provide (we hope) a commit log and useful attribution, if/when we apply the patch, while "git diff" does not. Patches with explanations and provided as attachments are really appreciated. They should be sent to the development mailing list, and will be discussed there. If possible, generate the patches by using <code>git format-patch</code> in a GIT clone.
On Fri, Jan 15, 2010 at 11:31:34AM +0100, Jim Meyering wrote:
Daniel P. Berrange wrote:
* docs/contact.html.in: Document new users mailing list ... Sounds good.
+ <p> + Both mailing lists require that you <strong>subscribe before posting to the list</strong>,
Since both lists are using listhelper,
http://savannah.gnu.org/maintenance/ListHelperAntiSpam
it is now possible to remove the subscribe-before-posting requirement. If we remove it, that makes it easier for people to send their first post. Now, that may not always be such a good thing ;-) but at least it won't result in spam.
I would keep the lists subscriber oriented, amybe that could be removed for the -user one, but I think the status quo is fine.
+ otherwise your posting will be blocked by mailman. You can subscribe at the linked webpages + above.
Perhaps say "delayed for manual approval" rather than blocked?
okay
+ <p> + 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 <code>git diff</code> in a GIT clone. </p>
Minor wording fix, and say we prefer "git format-patch", rather than "git diff" output, since the former can provide (we hope) a commit log and useful attribution, if/when we apply the patch, while "git diff" does not.
Patches with explanations and provided as attachments are really appreciated. They should be sent to the development mailing list, and will be discussed there. If possible, generate the patches by using <code>git format-patch</code> in a GIT clone.
Okay I have made the 2 small changes and pushed the patch, Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel@veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/
participants (3)
-
Daniel P. Berrange -
Daniel Veillard -
Jim Meyering