incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <>
Subject Re: No dev-, user- lists for small podlings (was: Re: [PROPOSAL] Kitty to Enter the Incubator)
Date Thu, 09 Sep 2010 19:24:54 GMT
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.


On Thu, Sep 9, 2010 at 04:42, Robert Matthews
<> wrote:
> I'm with James on this one.  Many good points have been made on this,
> but we do have bigger things to worry about.
> On Wed, 2010-09-08 at 08:06 -0400, James Carman wrote:
>> On Wed, Sep 8, 2010 at 7:39 AM, dan haywood
>> <> wrote:
>> >
>> > For the moment at least the dev community is more active (or at least more
>> > vocal), so their mailing list should be the main focal point.  As I said in
>> > the other email, when we have more user traffic than dev traffic, then
>> > we can vote to split them out.
>> >
>> Why are we even having this discussion?  When did mailing lists become
>> such a heavyweight operation that we have to discuss at length whether
>> they should even exist?  Just create the user/dev/commits/issues lists
>> and be done with it.  If nobody uses the user list, so be it.  I think
>> it's just more confusing to start moving traffic from one list to
>> another.  Keep things consistent.
>> > And another benefit of putting user traffic on the dev list is that
>> > it'll give the devs exposure to any probs that regular users are having with
>> > actually using the framework (ie so we can mature its documentation etc)
>> >
>> The developers should be "listening" to the user list so that they can
>> answer questions.  They can't just hide in the dev list and not listen
>> to the community.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message