Mailing-List: contact dev-help@concerted.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@concerted.incubator.apache.org
MIME-Version: 1.0
Sender: shaposhnik@gmail.com
In-Reply-To: <D25FB538.31B23%cnauroth@hortonworks.com>
References: 
 <CAOeZVifUNoAcASZW5c4kDc9YPqwcVG5sVt5ET0cFtqmYf5D9Xw@mail.gmail.com>
	<26D7AC21-BA32-411E-BE5D-151FA2CEB409@apache.org>
	<D25FB538.31B23%cnauroth@hortonworks.com>
Date: Wed, 4 Nov 2015 21:01:30 -0800
Message-ID: 
 <CA+ULb+u=b9Q4rKk04ZwkXor=aPBMoff_AwLKQXcXQDw4w-jH9g@mail.gmail.com>
Subject: Re: Community Building
From: Roman Shaposhnik <roman@shaposhnik.org>
To: dev@concerted.incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I know I've been sounding like a broken record lately with regard to
the Apache Maturity model,
but here it goes again:
https://community.apache.org/apache-way/apache-project-maturity-model.html

Seriously. This is a great check list of things you can focus on to improve=
 and
develop your community.

Thanks,
Roman.

On Wed, Nov 4, 2015 at 1:28 PM, Chris Nauroth <cnauroth@hortonworks.com> wr=
ote:
> This is a great list from Julian.  To that list, I would just add that
> it's helpful to maintain a queue of newbie work, so that new contributors
> have something small but tangible to do.  Different projects choose
> different methods of managing this in JIRA.  You could link to a JIRA
> filter for all issues at Trivial priority.  You could use a "newbie" labe=
l
> applied to individual JIRAs that are newbie friendly.
>
> The important point is to keep these issues defined to a small scope, lik=
e
> fixing a tiny bug or typos in documentation.  In some ways, it's more
> about helping new contributors practice building, testing and contributin=
g.
>
> --Chris Nauroth
>
>
>
>
> On 10/20/15, 12:06 PM, "Julian Hyde" <jhyde@apache.org> wrote:
>
>>Here are some ideas:
>>* Conduct business in the open, on the dev list and in JIRAs
>>* Be welcoming to new contributors
>>* Release early and often
>>* Make code super-easy to install
>>* Speak at conferences and meetups in every geography where you have
>>contributors
>>* Create a twitter account for the project and use it to propagate news
>>and have conversations with other twitter users
>>* Encourage contributions of all sizes and types - not just code
>>* Add =C2=B3how to get started=C2=B2, =C2=B3how you can help=C2=B2 pages =
to the web site
>>* Consider other channels (e.g. hangouts, IRC) if your community wants
>>them. But be careful to keep business (e.g. making decisions) on the list
>>
>>If these ideas are familiar it=C2=B9s no accident - the Apache Way is a p=
roven
>>method to build community.
>>
>>Julian
>>
>>
>>> On Oct 20, 2015, at 12:49 AM, Atri Sharma <atri@apache.org> wrote:
>>>
>>> Hi,
>>>
>>> I would like to understand steps and ideas around community building.
>>>
>>> Currently we have a PPMC of wide spectrum of developers and core engine
>>> development is currently handled by myself, Nupur and Amrish.
>>>
>>> Gaurav is working on the website and Gaurav and Ayrton are discussing
>>>the
>>> potential of a REST API for Concerted.
>>>
>>> We have added two new contributors since we went into ASF Incubation:
>>> Gaurav and Anand.
>>>
>>> I would like to understand how we can start telling people about our
>>> project, inviting more contributors and getting the game going. I am
>>>hoping
>>> that our mentors will guide us in this direction as well.
>>>
>>> Regards,
>>>
>>> Atri
>>>
>>> --
>>> Regards,
>>>
>>> Atri
>>> Apache Concerted
>>
>>
>