[distribution-discuss] Project Setup policy? Vote needed

[Shawn Walker]

On Fri, Apr 18, 2008 at 12:34 PM, Eric Boutilier <Eric.Boutilier at sun.com> wrote:
> On Fri, 18 Apr 2008, John Plocher wrote:
>
> > Shawn Walker wrote:
> >
> > > Do we want to defer creation of a mailing list for new projects until
> > > we feel its needed?
> > >
> >
> >
> > Mailing lists are easy and cheap to create, and almost impossible to
> > rename or delete.  In addition, more mailing lists results in community
> > fragmentation.
> >
> > This argues for only creating them after there is a demonstrated and
> > persistent need.
> >
> > I take Shawn's suggestion to be that all projects should start by using
> > the distribution-discuss alias, and only after [some metric[1]] should
> > a splinter list be created.
> >
> > +1
> >
> >
>
>  For *-discuss lists (as opposed to *-dev lists), I strongly agree.
>  We've found that leaders of a new projects are instincively tempted to
>  create a separate *-discuss lists early on; unfortunately that almost
>  always results in less effective communication not better. As the new
>  project progresses, its audience will say when (if /ever/) they want
>  discussions to be separated away from the parent (sponsoring CG)
>  list.

Since distribution projects inherently have a development aspect,
should we then automatically create a
distribution-project-dev at opensolaris.org mailing list?

Or, should we have a distribution-dev at opensolaris.org mailing list
where bug reports, automated commit notifications, etc. can all go?

Cheers,
-- 
Shawn Walker

"To err is human -- and to blame it on a computer is even more so." -
Robert Orben