incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <gst...@gmail.com>
Subject Re: Podling user@ lists (was: [PROPOSAL] SkyWalking - proposal for Apache Incubation)
Date Thu, 30 Nov 2017 12:54:33 GMT
On Thu, Nov 30, 2017 at 3:51 AM, sebb <sebbaz@gmail.com> wrote:

> On 29 November 2017 at 13:44, John D. Ament <johndament@apache.org> wrote:
> > On Wed, Nov 29, 2017 at 5:59 AM sebb <sebbaz@gmail.com> wrote:
> >
> >> Top posting
> >>
> >> The proposal includes a user@ mailing list.
> >> This is generally not recommended for podlings as their focus needs to
> >> be on building the developer community.
> >>
> >
> > Podlings are more than welcomed to include user@ lists.
>

They might be "welcome" to have such a list. But as sebb quotes my
explanation from years back: it is a Bad Idea.

Community growth is almost directly proportional to activity. You cannot
attract people to "crickets" mailing lists. And dividing/partitioning your
(potential) community is the fastest way to crickets.

The Incubator is about teaching people how to build a functional Apache
community. Keeping users/devs on the same list is one of the easiest and
most straight-forward lessons to teach.

-g


>
> That is not my recollection.
>
> See for example:
>
> http://mail-archives.apache.org/mod_mbox/incubator-general/201009.mbox/%
> 3CAANLkTim7NzJ%2BBLY8AtkR5ZmDUXHR%2BNZxr44VSqGJ_O3D%40mail.gmail.com%3E
>
> > There's nothing stopping them from building developers and users at the
> same time.
>
> That's extra work.
>
> If there is already an external users list, let that continue until
> the project is ready to graduate, then migrate users across.
>
> But it seems wrong to create a new user list initially.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message