openstack team mailing list archive

[David Kang <dkang@xxxxxxx>]

 I agree that subject prefix is a way.
There are pros and cons of either approach.
However, when I asked a few of the people who showed interest in bare-metal discussion,
a new mailing list was preferred by them.
And we thought a separate mailing list makes people easier to participate and to manage the discussion.

 We can discuss this issue again among the people who signed up the new mailing list.

 Thanks,
 David
----------------------
Dr. Dong-In "David" Kang
Computer Scientist
USC/ISI

----- Original Message -----
> David Kang wrote:
> >
> >  Hello all,
> >
> >  An openstack mailing list is created for the discussion of
> >  bare-metal provisioning.
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-baremetal
> >
> >  Please join it if you are interested in participating the
> >  dicussion/collaboration
> > of bare-metal provisioning.
> 
> Hmm, any particular reason why you're not having those discussions on
> the development mailing-list instead ? That sounds a totally
> appropriate
> topic for that list... and the overlap between the two groups sounds
> pretty complete (B totally included in A).
> 
> I would prefer if we didn't multiply the sublists for development
> subtopics and if we didn't force developers to subscribe to multiple
> lists just to keep informed on design discussions. That will avoid the
> subgroup coming up with a design that will be rejected by the larger
> group once it is submitted there.
> 
> Why not use a subject prefix instead ? Like [baremetal] ?
> 
> Regards,
> 
> --
> Thierry Carrez (ttx)
> Release Manager, OpenStack
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp