On 01/04/2011 11:39 AM, Justin Clift wrote:
Also added explicit links to the subscription and archive pages for the user and developer mailing lists. --- docs/contact.html.in | 77 +++++++++++++++++++++++++++++++++----------------- 1 files changed, 51 insertions(+), 26 deletions(-)
Several suggestions:
- </ul> + <dt><a href="https://www.redhat.com/mailman/listinfo/libvir-list">libvir-list@redhat.com</a> (for development)</dt>
Mention that this is high-volume.
+ <dt><a href="https://www.redhat.com/mailman/listinfo/libvirt-users">libvirt-users@redhat.com</a> (for users)</dt> + <dd>
moderate volume
- </ul> + <dt><a href="https://www.redhat.com/mailman/listinfo/libvirt-announce">libvirt-announce@redhat.com</a> (for release notices)</dt> + <dd>
low-volume, and restricted posting
<p> - 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. + The user and development mailing lists require you to subscribe before + posting to the list. Otherwise your posting will be delayed for manual + approval. You can subscribe at the linked webpages above.
I'd reword this (I'm not a list admin, so I don't know the specifics of this list setup, but on other mailman-based lists that I do manage, non-subscribers can post after moderation delays and can be whitelisted even without subscription; and new subscribers are still subject to a first-time moderation delay to help cut down on spurious subscriptions for the purpose of spreading spam). If so, then this wording might be more accurate: It is recommended but not required that you subscribe before posting to user and development lists. First-time posts may be subject to manual moderation delays. You can subscribe at the linked webpages above.
<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 format-patch</code> in a GIT - clone. + Patches with explanations and provided as attachments are really + appreciated, and should be directed to the development mailing list + for review and discussion. + Wherever possible, please generate the patches by using + <code>git format-patch</code> in a git repository clone.
Can we also point to our hacking.html page, which has better instructions for posting a patch? -- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org