aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastien Goasguen <run...@gmail.com>
Subject Re: [DISCUSS] shepherding contributors
Date Tue, 22 Apr 2014 20:04:19 GMT

On Apr 22, 2014, at 3:46 PM, Henry Saputra <henry.saputra@gmail.com> wrote:

> If you look at many of existing ASF projects, including the big ones,
> not many of them have "shepherds".
> 
> When someone has question then sending email to dev@ list is the way
> to go and the community should be able to help.
> 

I agree with Henry, dev@ is the de-facto "tier-one".

Helping a new contributor become a committer (aka mentoring,shepherding) happens through the
review process, email discussions, IRC discussions, jira exchanges.

Actually even non-committers can be "shepherds", because it's not always about code. Remember
Apache Way motto is "community over code".

When you have questions, the community will help. So my views of your question is "if you
have questions, dev@ is here to help", from there anyone can pick it up.


> We could use prefix in subject to help define topics or certain discussions.
> 
> But the decision to have shepherds is up to you guys. If you think you
> need one please do have them =)
> 
> I was just giving my 2-cents.
> 
> - Henry
> 
> On Tue, Apr 22, 2014 at 12:25 PM, Bill Farner <wfarner@apache.org> wrote:
>> I disagree that shepherding is unneeded.  Just having a de-facto tier one
>> support contact is huge to help acquaint a new developer.  Perhaps our
>> definitions of shepherd differs, i'm thinking of it amounting to "when you
>> have questions, [committer name] is here to help you".
>> 
>> -=Bill
>> 
>> 
>> On Tue, Apr 22, 2014 at 12:04 PM, Henry Saputra <henry.saputra@gmail.com>wrote:
>> 
>>> I think for small community like Aurora we do not need shepherding for
>>> contributors.
>>> 
>>> We could do it via JIRA and review boards as Sebastien mentioned. If a
>>> contributor is interested in certain feature then one of the PPMCs
>>> could just engage and help driving through solution.
>>> 
>>> Once contributions come as rapid as in Apache Spark or Hadoop, then I
>>> believe shepherding of new contributors needed.
>>> 
>>> - Henry
>>> 
>>> On Tue, Apr 22, 2014 at 11:58 AM, Sebastien Goasguen <runseb@gmail.com>
>>> wrote:
>>>> 
>>>> 
>>>>> On 22 Apr 2014, at 20:04, Bill Farner <wfarner@apache.org> wrote:
>>>>> 
>>>>> Some things not yet addressed (some have obvious solutions, but still
>>>>> warrant explicit discussion):
>>>>> 
>>>>> - What is expected of a shepherd?
>>>>> 
>>>>> - How does a newcomer learn that we have a shepherd program?
>>>>> 
>>>>> - How is a shepherd assigned
>>>> 
>>>> Doesn't sheperding happens through review board and jira ? And whoever
>>> picks up review or comments on bug is the sheperd ?
>>>> 
>>>> 
>>>>> -=Bill
>>>>> 
>>>>> 
>>>>>> On Mon, Apr 21, 2014 at 5:27 PM, Jake Farrell <jfarrell@apache.org>
>>> wrote:
>>>>>> 
>>>>>> As part of our first IRC meeting one of the topics that came up was
>>>>>> shepherding contributors that have shown interest and how we can
help
>>> and
>>>>>> encourage them into committer roles and grow the community.
>>>>>> 
>>>>>> Opening this discussion thread so we can flush out any ideas not
>>> brought up
>>>>>> during the meeting
>>>>>> 
>>>>>> -Jake
>>>>>> 
>>> 


Mime
View raw message