Attention: Mailing List Change

[Brian Proffitt]

All:

One of the long-standing requests in the oVirt community is the merging of the [arch] and [engine-devel] mailing lists. This note is an announcement that on Monday, March 31, this will get done.

What will happen:

1) Subscribers from [arch] and [engine-devel] will be migrated to a new [devel] list.
2) Archives from [arch] (this list) will be left as is, and available for searching on the list.ovirt.org/mailman site.
3) Archived from [engine-devel] will be renamed to [devel]

If you have any comments or concerns, let me know.

Thank you for your patience in this matter,
Brian

[Livnat Peer]

Post by Brian Proffitt
One of the long-standing requests in the oVirt community is the merging of the [arch] and [engine-devel] mailing lists. This note is an announcement that on Monday, March 31, this will get done.
1) Subscribers from [arch] and [engine-devel] will be migrated to a new [devel] list.
2) Archives from [arch] (this list) will be left as is, and available for searching on the list.ovirt.org/mailman site.
3) Archived from [engine-devel] will be renamed to [devel]
If you have any comments or concerns, let me know.
Thank you for your patience in this matter,
Brian

First of all +1 for doing that.

Can we include VDSM as well in a single ovirt-devel list? There is no
reason to track two different lists. which is a concern we've discussed
in the past...

[Eyal Edri]

----- Original Message -----

From: "Livnat Peer" <lpeer at redhat.com>
To: "Brian Proffitt" <bproffit at redhat.com>, "arch" <arch at ovirt.org>
Sent: Thursday, March 27, 2014 10:32:07 AM
Subject: Re: Attention: Mailing List Change

Post by Brian Proffitt
One of the long-standing requests in the oVirt community is the merging of
the [arch] and [engine-devel] mailing lists. This note is an announcement
that on Monday, March 31, this will get done.
1) Subscribers from [arch] and [engine-devel] will be migrated to a new [devel] list.
2) Archives from [arch] (this list) will be left as is, and available for
searching on the list.ovirt.org/mailman site.
3) Archived from [engine-devel] will be renamed to [devel]
If you have any comments or concerns, let me know.
Thank you for your patience in this matter,
Brian

First of all +1 for doing that.
Can we include VDSM as well in a single ovirt-devel list? There is no
reason to track two different lists. which is a concern we've discussed
in the past...

+1

_______________________________________________
Arch mailing list
Arch at ovirt.org
http://lists.ovirt.org/mailman/listinfo/arch

[Dan Kenigsberg]

Post by Livnat Peer

Post by Brian Proffitt
One of the long-standing requests in the oVirt community is the merging of the [arch] and [engine-devel] mailing lists. This note is an announcement that on Monday, March 31, this will get done.
1) Subscribers from [arch] and [engine-devel] will be migrated to a new [devel] list.
2) Archives from [arch] (this list) will be left as is, and available for searching on the list.ovirt.org/mailman site.
3) Archived from [engine-devel] will be renamed to [devel]
If you have any comments or concerns, let me know.
Thank you for your patience in this matter,
Brian

First of all +1 for doing that.
Can we include VDSM as well in a single ovirt-devel list? There is no
reason to track two different lists. which is a concern we've discussed
in the past...

I prefer keeping vdsm-devel intact. It's a different programming
language, with its different set of problems, unrelated profiling
issues, and somewhat different target audience.

[Livnat Peer]

Post by Dan Kenigsberg

Post by Livnat Peer

Post by Brian Proffitt
One of the long-standing requests in the oVirt community is the merging of the [arch] and [engine-devel] mailing lists. This note is an announcement that on Monday, March 31, this will get done.
1) Subscribers from [arch] and [engine-devel] will be migrated to a new [devel] list.
2) Archives from [arch] (this list) will be left as is, and available for searching on the list.ovirt.org/mailman site.
3) Archived from [engine-devel] will be renamed to [devel]
If you have any comments or concerns, let me know.
Thank you for your patience in this matter,
Brian

First of all +1 for doing that.
Can we include VDSM as well in a single ovirt-devel list? There is no
reason to track two different lists. which is a concern we've discussed
in the past...

I prefer keeping vdsm-devel intact. It's a different programming
language, with its different set of problems, unrelated profiling
issues, and somewhat different target audience.

We can use the message subject to differentiate between VDSM specific
correspondence to Engine etc.

Having a unified mailing list would expose VDSM to other people which do
not track VDSM list today and would increase VDSM visibility.

In addition most of the features are cross component and tracking it in
two different lists is not working - at least not for me.

Livnat

[Alon Bar-Lev]

----- Original Message -----

From: "Brian Proffitt" <bproffit at redhat.com>
To: "arch" <arch at ovirt.org>
Sent: Wednesday, March 26, 2014 8:39:51 PM
Subject: Attention: Mailing List Change
One of the long-standing requests in the oVirt community is the merging of
the [arch] and [engine-devel] mailing lists. This note is an announcement
that on Monday, March 31, this will get done.
1) Subscribers from [arch] and [engine-devel] will be migrated to a new [devel] list.
2) Archives from [arch] (this list) will be left as is, and available for
searching on the list.ovirt.org/mailman site.
3) Archived from [engine-devel] will be renamed to [devel]

Can we rename [devel] prefix to [ovirt-devel], it is confusing with other lists.
Same I guess to any ovirt list.

Thanks!

If you have any comments or concerns, let me know.
Thank you for your patience in this matter,
Brian
--
Brian Proffitt - oVirt Community Manager
Open Source and Standards, Red Hat - http://community.redhat.com
Phone: [phone]BKP
_______________________________________________
Arch mailing list
Arch at ovirt.org
http://lists.ovirt.org/mailman/listinfo/arch