www-community mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <bay...@apache.org>
Subject Re: Low level community
Date Mon, 30 Jun 2014 05:03:59 GMT
+1 to the decoupling part. The bigger the bump to join in, the less people
will join.

Other important items imo:

* What is the value of your project? Is it valuable? Who is it valuable to?
What is the larger community it is related to and what are the trends in
that community? Are you also trending the same way? Basically put on a
devil advocate hat, and try to convince yourself that your project is worth
using.
* Once you've identified where that larger community is, tweet to them (or
other communication method). A quiet but constant monologue, a heartbeat. I
think communities get the heartbeat at the gut level, a project whose
heartbeat can't be heard is assumed to be dead. You need to establish that
beat.
* Communicate todo items too. If your community is full of hard core
hackers, send out the gnarly problems while you fix the build. If, more
typically, your project hides the painful and makes life easier for users,
then typically you would send out the simpler issues while you deal with
the gnarly.

I wonder if the Attic needs a page on "Staying out of the Attic" :)

Hen



On Sun, Jun 29, 2014 at 4:58 AM, Santiago Gala <santiago.gala@gmail.com>
wrote:

>
>
>
> On Sat, Jun 28, 2014 at 11:09 AM, Lewis John Mcgibbney <
> lewis.mcgibbney@gmail.com> wrote:
>
>> Hi  Folks,
>> community@ is the orrect place for this question.
>> What do we* do when we have low level activity, low level community,
>> generally speaking low level anything on a project?
>>
>
> Other ideas worth exploring (I'm not sure what kind of project you talk
> about):
> * ensure that parts of the project worth separate use are packaged
> separately, so that people can feel compelled to use, and improve/maintain,
> them. Again, you need to publisize them
> * See if your project have "reinvented wheels", i.e. parts that can be
> easily replaced with off the shelf components and that are adding no value
> (say a template engine with no special value, present because of historical
> reasons). If this is the case, maintenance can be simplified by
> substituting them with well-maintained components
>
> Regards
> Santiago
>
>
>
>> I am NOT talking about the attic.
>> I am committed to ensuring the project is NOT going to the attic.
>> Lewis
>>
>> * in the collective sense. Your, I, Us, Etc.
>>
>> --
>> *Lewis*
>>
>
>

Mime
View raw message