Re: [Xen-API] [XenARM] [Xen-devel] [Proposal] Additional mailing lists for specific purposes

[Tim Deegan <tim@xxxxxxx>]

At 08:42 +0100 on 23 Apr (1366706522), Ian Campbell wrote:
> On Mon, 2013-04-22 at 17:42 +0100, Lars Kurth wrote:
> > On new lists, we will need lists for
> >       * xenproject-marketing@xxxxxxxxxxxxxxxxxxxx ... maybe
> >         xenproject-publicity@xxxxxxxxxxxxxxxxxxxx hits it better than
> >         marketing (seems to work for debian)
> 
> For things which are xenproject wide and not related to a specific
> subproject I think omitting the prefix is the way to go, so marketing@,
> publicity@ etc, the xenproject bit is in the domain and repeating it
> makes everything sound clumsy.

+1.  So, xen-devel@xxxxxxxxxxxxxxxxxxxx, xapi-devel@, &c for project
lists, but publicity@, announce@ without prefixes.

> >       * I need something for votes and discussions that cut accross
> >         sub-project and teams. Maybe
> >         xenproject-proposals@xxxxxxxxxxxxxxxxxxxx or
> >         xenproject-decisionmaking@xxxxxxxxxxxxxxxxxxxx? Just putting
> >         these into the room: none of these sound right to me. Maybe
> >         xenproject-leadership@xxxxxxxxxxxxxxxxxxxx is better?

What would this new list be used for?  The sort of thing that's currently
cross-posted to the various developer lists?  Unless that list is
automatically maintained as the union of all the dev list members, it
seems like it will just make the process less transparent (since people
who join xen-devel@ won't know to join governance@ too and so will be
left out).

> vote@, committers@ and/or maintainers@ ?

I don't think there's much use for separate committer/maintainer lists:
anything the committers or maintainers want to discuss in public can
just happen on the developer lists.  There won't be very much of it.

Tim.

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api