incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Schaefer <joe_schae...@yahoo.com>
Subject Re: No dev-, user- lists for small podlings (was: Re: [PROPOSAL] Kitty to Enter the Incubator)
Date Thu, 09 Sep 2010 22:33:56 GMT
Knowing Roy he'd probably want to see them
all renamed use@.



----- Original Message ----
> From: Mark Struberg <struberg@yahoo.de>
> To: general@incubator.apache.org
> Sent: Thu, September 9, 2010 6:31:05 PM
> Subject: Re: No dev-, user- lists for small podlings (was: Re: [PROPOSAL] Kitty 
>to Enter the Incubator)
> 
> btw, regarding consistency: some projects have a users@a.o (plural) list, 
>others have user@a.o (singular). I most  certainly take the wrong one whenever I 
>write a mail to some u list  ;)
> 
> LieGrue,
> strub
> 
> --- On Thu, 9/9/10, James Carman <james@carmanconsulting.com>  wrote:
> 
> > From: James Carman <james@carmanconsulting.com>
> >  Subject: Re: No dev-, user- lists for small podlings (was: Re: [PROPOSAL] 
>Kitty  to Enter the Incubator)
> > To: general@incubator.apache.org
> >  Date: Thursday, September 9, 2010, 7:33 PM
> > On Thu, Sep 9, 2010 at 3:24  PM, Greg
> > Stein <gstein@gmail.com>
> > wrote:
> >  > The formation of your community is a BIG DEAL. Not
> > something  to
> > > casually sweep under the rug.
> > >
> > >  Partitioning the community between users and devs
> > makes it very
> >  > difficult to establish a large, viable, sustainable
> >  community.
> > >
> > > If projects arrive at the Incubator with  an
> > already-built user
> > > community, then sure. Create separate  lists. But small
> > communities
> > > should (IMO) stick to a single  dev@ list until you
> > can't handle the
> > > traffic any more. If  you started elsewhere with two
> > lists, but your
> > > list traffic  is still "small", then I would recommend
> > combining them
> > >  when arriving at the Incubator.
> > >
> > > It is obviously a call  for each podling to make, so
> > I'm simply
> > > recommending that  all podlings consider the impact of
> > dividing your
> > > community  when you ask for separate dev/user lists. I
> > believe it is
> > >  rarely appropriate.
> > >
> > 
> > And I'm all about  consistency.  Most (if not all, I
> > haven't checked)
> > ASF projects  have separate user/dev lists.  That's
> > just how we do
> > things.   It's really not that much trouble to have two
> > different lists
> >  and just subscribe to both (if you're a developer). 
> > That way,
> >  development "stuff" (votes, board reports, etc.) doesn't
> > bleed  over
> > onto the user lists.  I've always subscribed to both
> > lists  for every
> > project I'm on.  If users are interested in the
> >  development goings-on,
> > then they can subscribe to the dev list.  Some  folks,
> > like us
> > "mentors", might not be interested in user  issues, because
> > we're
> > really not necessarily capable of  answering the
> > questions.  I don't
> > want that junk in my inbox (or  label/folder).
> > 
> >  ---------------------------------------------------------------------
> > To  unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >  For additional commands, e-mail: general-help@incubator.apache.org
> > 
> > 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To  unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For  additional commands, e-mail: general-help@incubator.apache.org
> 
> 


      

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message