----- Original Message -----
From: "Alon Bar-Lev" <alonbl(a)redhat.com>
To: "Itamar Heim" <iheim(a)redhat.com>
Cc: devel(a)ovirt.org
Sent: Wednesday, April 9, 2014 3:22:41 PM
Subject: Re: [ovirt-devel] [Devel] Attention: Mailing List Change
> >
> > ----- Original Message -----
> >> From: "Brian Proffitt" <bproffit(a)redhat.com>
> >> To: "Itamar Heim" <iheim(a)redhat.com>
> >> Cc: "David Caro" <dcaroest(a)redhat.com>, devel(a)ovirt.org,
"Alon Bar-Lev"
> >> <alonbl(a)redhat.com>
> >> Sent: Wednesday, April 9, 2014 3:14:46 PM
> >> Subject: Re: [Devel] Attention: Mailing List Change
> >>
> >> Well, shoot, I can change that now.
> >>
> >> The prefix [devel] will now be [ovirt-devel].
> >
> > Can you please do this for all? for example users.
>
> I think only devel and users are interesting. the rest are are either
> already with engine prefix (engine-patches), or very low traffic
> (announce, etc.).
especially announce... :)
As I got no response, so I will try to explain using two arguments...
1. People that subscribe to announce usually have no filters as it is low traffic, so it
is ovirt prefix should be added to differentiate from other activity.
2. Consistency... important for engineering and for professional appearance. Exceptions
should have good reason. There is no good reason why not all ovirt mailing list share the
same prefix, easier to search, comfortable as eye catcher etc.
Not sure what your argument not to have plain consistent prefix for all.
I would like to emphasis the obvious move that is long overdue to host all lists at
ovirt.org[1], the share of experience of people is important, I still do not understand
why we do not use our human resources and experience to understand how to improve. This
applies to mailing list, our site organization, our bug management, our release
engineering, which still do not line up with best practises.
Regards,
Alon
[1]
http://lists.ovirt.org/pipermail/infra/2012-December/001688.html