aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Farner <wfar...@apache.org>
Subject Re: [DISCUSS] shepherding contributors
Date Tue, 22 Apr 2014 19:25:51 GMT
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
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message