[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

On Mon, Apr 22, 2013 at 05:42:26PM +0100, Lars Kurth wrote:
>    Hi,
>    seems nobody has any views. How about I make a more concrete proposal. I
>    also noticed that we have no real global list for voting and proposals
>    (and to discuss issues like this). I have to include all lists, which
>    creates spam. As already indicated on the blog, at some point we should
>    move to @lists.xenproject.org, which will cause some impact on
>    mailfilters, etc. (similar to when we moved from @lists.xensource.com to
>    @lists.xen.org about a year ago). So that may be a good opportunity to
>    deal with some inconsistencies that have grown over time.
>    It also raises questions about naming conventions for new lists. Should
>    lists be
>    - [1]xen-...@xxxxxxxxxxxxxxxxxxxx, or should they be
>    - [2]xenproject-...@xxxxxxxxxxxxxxxxxxxx
>    And then of course, should any convention be forward looking or should we
>    rename lists to be consistent and (as we are already changing
>    @lists.xenproject.org, changing the actual list name may not be any
>    worse).
>    On new lists, we will need lists for
>      * [3]xenproject-marketing@xxxxxxxxxxxxxxxxxxxx ... maybe
>        [4]xenproject-publicity@xxxxxxxxxxxxxxxxxxxx hits it better than
>        marketing (seems to work for debian)
>      * I need something for votes and discussions that cut accross
>        sub-project and teams. Maybe
>        [5]xenproject-proposals@xxxxxxxxxxxxxxxxxxxx or
>        [6]xenproject-decisionmaking@xxxxxxxxxxxxxxxxxxxx? Just putting these
>        into the room: none of these sound right to me. Maybe
>        [7]xenproject-leadership@xxxxxxxxxxxxxxxxxxxx is better?
>      * We will have a list for the advisory board, which wants to be totally
>        open and transparent. So this would be
>        [8]xenproject-advisoryboard@xxxxxxxxxxxxxxxxxxxx and I will post
>        minutes, etc. of the last meeting when we created the list.
>      * xenproject-private, if we actually need it would work too. However the
>        advisory board recommended in the meeting last week not to have any
>        private lists at all. So maybe we don't need this.
>    Also, for example XAPI does not have a separate dev or user list. That is
>    also one to consider at some point.

I thought that's what xen-api@xxxxxxxxxxxxx was supposed to be :) 

-- Pasi
>    Anyway, I am just putting these into the room for discussion.
>    Lars
>    On 19/04/2013 04:52, Chip Childers wrote:
>  On Sun, Apr 14, 2013 at 06:52:09PM +0100, Lars Kurth wrote:
>  1) A list for coordinating blog posts, other communication,
>  attending of event, etc. - not sure about the name, so am looking
>  for suggestions. I am not sure whether we should have public
>  archives: comparable lists of other projects don't.
>  From an outsider / lurker perspective, [9]xen-marketing@xxxxxxxxxxxxx is a
>  good fit.
>  2) A semi-private invite mailing list for ALL project leads,
>  committers and maintainers of ALL projects hosted on xen.org
>  Similarly to above: [10]xen-private@xxxxxxxxxxxxx
>  Both of these list names are used in other projects I'm working with /
>  observe.
> References
>    Visible links
>    1. mailto:xen-...@xxxxxxxxxxxxxxxxxxxx
>    2. mailto:xenproject-...@xxxxxxxxxxxxxxxxxxxx
>    3. mailto:xenproject-marketing@xxxxxxxxxxxxxxxxxxxx
>    4. mailto:xenproject-publicity@xxxxxxxxxxxxxxxxxxxx
>    5. mailto:xenproject-proposals@xxxxxxxxxxxxxxxxxxxx
>    6. mailto:xenproject-decisionmaking@xxxxxxxxxxxxxxxxxxxx
>    7. mailto:xenproject-leadership@xxxxxxxxxxxxxxxxxxxx
>    8. mailto:xenproject-advisoryboard@xxxxxxxxxxxxxxxxxxxx
>    9. mailto:xen-marketing@xxxxxxxxxxxxx
>   10. mailto:xen-private@xxxxxxxxxxxxx

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.