This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
Content-Type: text/plain; charset=UTF-8
On Wed 09 Apr 2014 10:36:29 PM CEST, Alon Bar-Lev wrote:
----- Original Message -----
> From: "Alon Bar-Lev" <alonbl(a)redhat.com
"Itamar Heim" <iheim(a)redhat.com
> 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"
>>>> Cc: "David
Caro" <dcaroest(a)redhat.com>, devel(a)ovirt.org, "Alon Bar-=
>>>> 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
>> (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 l=
traffic, so it is ovirt prefix should be added to differentiate from o=
2. Consistency... important for engineering and for professional
ance. Exceptions should have good reason. There is no good reason why not=
all ovirt mailing list share the same prefix, easier to search, comforta=
ble 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, the share of experience of people is important=
, I still do not understand why we do not use our human resources and exp=
erience to understand how to improve. This applies to mailing list, our s=
ite organization, our bug management, our release engineering, which stil=
l do not line up with best practises.
> Devel mailing list
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
RHT Global #: 82-62605
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----END PGP SIGNATURE-----