Mailing list scope proposal

[Dave Neary]

Hi,

On 08/27/2012 10:31 PM, Karsten 'quaid' Wade wrote:
> On 08/26/2012 12:07 AM, Livnat Peer wrote:
>> On 24/08/12 19:29, Dave Neary wrote:
>>> So - here's my suggestion for that (and as per my suggestion, let's have
>>> this discussion here, and when we reach a consensus ask for the opinion
>>> of the board):
>>>
>>> users@ - User issues

<snip>

>>> arch@ - rename to developers@ - This will be the key developer mailing
>>> list for oVirt

<snip>

>>> board@ - Issues related to the non-technical governance of the project

<snip>

>>> infra@ - issues related to the management of oVirt infrastructure

<snip>

>>> vdsm-devel, node-devel, engine-devel, *-devel: Low-traffic lists related
>>> to the specific implementation issues of the individual components.

<snip>

>>> How does that sound? Does anyone have other/better suggestions?
>>
>> +1, I think this is a good proposal.
>> I would try to avoid discussing patches on the developers list and try
>> to keep it more high level like design discussions etc.
>
> +1 Yes, that makes sense - keep patch discussions in the project, and
> keep discussions that affect oVirt overall on the developers list.
>
> Also, I'm +1 to renaming this list; I reckon arch@ is confusing, dev@ or
> developers@ is a more common Big Main List name.

It seems this has broad support - can we add it to the agenda for the 
weekly meeting this week to give people one last chance to have a say, 
and (assuming there is no major opposition) make it so?

Thanks,
Dave.

-- 
Dave Neary
Community Action and Impact
Open Source and Standards, Red Hat
Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13