Mailing-List: contact dev-help@metamodel.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@metamodel.incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of henry.saputra@gmail.com
 designates 74.125.82.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPaJBx48Ro9v4JLZxPnSTq=3tDtwDDeuTrSd_w_rwiLNsTzSNA@mail.gmail.com>
References: 
 <CAPaJBx5i7SfkVDnfAmh_4=D-RU9Zr=XpAmYBbAXZ4F-55gWHHw@mail.gmail.com>
	<CA+U3tt_BOQGfXt-B8HZJa3F3TQa6y=ezbJBhsN4-N-tmPaXU_g@mail.gmail.com>
	<CAPaJBx5tkg10pr+T11rGcEq9NW93+n0AAB5d_qodONCVRQ4j4Q@mail.gmail.com>
	<CA+U3tt-9a6AvoHYDZJz3KonCTf=zvYWd5AXkLMm40-tKXiR3Xw@mail.gmail.com>
	<CALuGr6bZnF2k0H07X4G9t0tdFe2KmTwSYXwn30PyA6J2S7kNKg@mail.gmail.com>
	<CA+U3tt_0nf-h9NzL3rHkGe_W-Kofj=YieE2wQneUxen74uJ9tA@mail.gmail.com>
	<CALuGr6aLDTaQC3qZP7+p=mgAkUVYD7sKzV525Psv5uKW=WNB=g@mail.gmail.com>
	<CAPaJBx48Ro9v4JLZxPnSTq=3tDtwDDeuTrSd_w_rwiLNsTzSNA@mail.gmail.com>
Date: Mon, 28 Apr 2014 10:51:14 -0700
Message-ID: 
 <CALuGr6beJHATi6x9P8LYYy21ZP8-eGCSq1CZTKi_sgNF9izp9w@mail.gmail.com>
Subject: Re: Attracting contributions
From: Henry Saputra <henry.saputra@gmail.com>
To: "dev@metamodel.incubator.apache.org" <dev@metamodel.incubator.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks for the link Noah.

I just could not find particular note about Twitter handle account.
Some other ASF projects I have checked have Twitter handle manage by a
particular PMC with share account/password.

- Henry

On Mon, Apr 28, 2014 at 10:45 AM, Noah Slater <nslater@apache.org> wrote:
> For reference:
>
> http://www.apache.org/foundation/marks/pmcs.html
>
> (Follow links as necessary if you need a refresher on any of this stuff.)
>
> Summary is: if the PPMC is happy (I assume we are) and we control it
> (i.e. the password can be shared) then I see no issue at all. And I am
> not aware of any specific restrictions.
>
> On 28 April 2014 19:36, Henry Saputra <henry.saputra@gmail.com> wrote:
>> I do not think there is a special rule to be followed. You can just
>> create one for MetaModel =3D)
>>
>> - Henry
>>
>> On Mon, Apr 28, 2014 at 10:10 AM, Kasper S=C3=B8rensen
>> <i.am.kasper.sorensen@gmail.com> wrote:
>>> Regarding twitter profile ... I can create one ... Any conventions or
>>> Apache rules or anything like that, which needs to be applied/conformed=
 to?
>>>
>>> Kasper
>>>
>>>
>>> 2014-04-06 19:46 GMT+02:00 Henry Saputra <henry.saputra@gmail.com>:
>>>
>>>> Thanks Kasper!
>>>>
>>>> On Sun, Apr 6, 2014 at 2:40 AM, Kasper S=C3=B8rensen
>>>> <i.am.kasper.sorensen@gmail.com> wrote:
>>>> > We should get that set up then.
>>>> >
>>>> > In the mean time I also started labeling some of the issues in JIRA =
with
>>>> a
>>>> > 'starter' label:
>>>> >
>>>> https://issues.apache.org/jira/browse/METAMODEL-17?jql=3Dproject%20%3D=
%20METAMODEL%20AND%20labels%20%3D%20starter
>>>> >
>>>> > I suppose we should advertise that tag somewhere on the website for
>>>> people
>>>> > who would like to start contributing.
>>>> >
>>>> >
>>>> > 2014-04-03 13:22 GMT+02:00 Noah Slater <nslater@apache.org>:
>>>> >
>>>> >> Infra can set us up with a MetaModel blog under blogs.apache.org.
>>>> >>
>>>> >> On 3 April 2014 12:45, Kasper S=C3=B8rensen <i.am.kasper.sorensen@g=
mail.com>
>>>> >> wrote:
>>>> >> > Hi Noah,
>>>> >> >
>>>> >> > Thank you for mentioning this worry and for all the good ideas to
>>>> create
>>>> >> > more traction.
>>>> >> >
>>>> >> > It's an overwhelming lot of work, so I don't think we can ask any=
one
>>>> in
>>>> >> > particular to do all this, but that we all need to be more proact=
ive
>>>> in
>>>> >> > promoting the project. One part that I think I can help with is m=
aybe
>>>> >> > blogging about how we use MetaModel in the case of DataCleaner (
>>>> >> > www.datacleaner.org). You mention that we should have a project b=
log.
>>>> >> How
>>>> >> > is that done? I have a personal blog that I could post it on, but
>>>> what is
>>>> >> > the usual approach when making a project blog?
>>>> >> >
>>>> >> > Kasper
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> > 2014-04-02 14:22 GMT+02:00 Noah Slater <nslater@apache.org>:
>>>> >> >
>>>> >> >> Hi folks,
>>>> >> >>
>>>> >> >> We've not elected anybody to the committership since we started
>>>> >> >> incubation, as far as I can tell. Learning how to do this is a r=
eally
>>>> >> >> important part of incubation, so why don't we kick start the eff=
ort
>>>> >> >> now? :)
>>>> >> >>
>>>> >> >> There are multiple parts to this:
>>>> >> >>
>>>> >> >> 1. Making the project attractive to potential contributors
>>>> >> >> 2. Making it easy to start contributing
>>>> >> >> 3. Recognising merit in people who do contribute
>>>> >> >> 4. The formality of electing those people to the committership
>>>> >> >>
>>>> >> >> Now, we've been working on (1) since we started incubating. It's=
 the
>>>> >> >> rest we need to pay attention to now. But briefly, here are some
>>>> >> >> ideas:
>>>> >> >>
>>>> >> >> - Have a nice website that clearly explains what the project doe=
s
>>>> >> >> - Have friendly, active mailing lists where people's questions a=
re
>>>> >> answered
>>>> >> >> - Put out regular releases and share the news of this around the=
 web
>>>> >> >> - Start a project blog, or something similar, and communicate pr=
oject
>>>> >> news
>>>> >> >> - Set up a Twitter account, etc, and talk about the project a lo=
t in
>>>> >> >> other places
>>>> >> >>
>>>> >> >> This is, essentially, marketing activity. Which I know a lot of =
folks
>>>> >> >> have an allergic reaction to. But it's essential to getting the =
word
>>>> >> >> out. Which is your first step if you want to convert people into
>>>> >> >> contributors. :)
>>>> >> >>
>>>> >> >> Okay, for step (2), there are lots things to do:
>>>> >> >>
>>>> >> >> - Add a "starter" tag to your JIRA tickets, which means "this is
>>>> ideal
>>>> >> >> for people who are just starting out with the code base". Docume=
nt
>>>> >> >> this tag on the project homepage, and make it abundantly clear t=
hat
>>>> >> >> contribution is welcome!
>>>> >> >> - Add "easy", "medium", and "hard" tags. These serve a similar
>>>> function.
>>>> >> >> - Get the GitHub integration set up and functioning as a first c=
lass
>>>> >> >> contribution method. Document this on the website. Make the top =
level
>>>> >> >> files in our repository "GitHub friendly" (i.e. they display nic=
ely
>>>> on
>>>> >> >> GitHub)
>>>> >> >> - Add documentation. Lots of it. Start with a CONTRIBUTING.md fi=
le at
>>>> >> >> the root of the repository, and make it very very easy to get st=
arted
>>>> >> >> - Consider having weekly or monthly Google Hangouts, or webcasts=
, or
>>>> >> >> write blog posts about specific modules or parts of the code
>>>> >> >> - Keep a keen eye out for anyone on the lists who looks like the=
y
>>>> >> >> *might* be interested in contributing and gently prod them in th=
e
>>>> >> >> right direction. Be friendly, encouraging, and thankful
>>>> >> >>
>>>> >> >> Step (3) is starting to get more process oriented, but basically=
:
>>>> >> >>
>>>> >> >> - Look at people opening tickets, creating pull requests, answer=
ing
>>>> >> >> questions on the mailing lists, submitting patches, etc. Set up =
some
>>>> >> >> sort of weekly or monthly reminder for yourself or the whole PMC=
 to
>>>> do
>>>> >> >> this
>>>> >> >> - Remind yourself that code is not the only way to contribute. W=
e're
>>>> >> >> interested in attracting any sort of help. Be that with code,
>>>> >> >> documentation, project organisation, community management, marke=
ting,
>>>> >> >> QA, tests, ticket triage, user support, etc
>>>> >> >> - As soon as you spot a likely candidate, bring it up on the
>>>> private@list
>>>> >> >>
>>>> >> >> Step (4) is easy, and I can guide you though that when the time
>>>> comes.
>>>> >> >>
>>>> >> >> Thanks,
>>>> >> >>
>>>> >> >> --
>>>> >> >> Noah Slater
>>>> >> >> https://twitter.com/nslater
>>>> >> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Noah Slater
>>>> >> https://twitter.com/nslater
>>>> >>
>>>>
>
>
>
> --
> Noah Slater
> https://twitter.com/nslater