Mapping our pipeline before looking for leaks

[Myrle Krantz <my...@apache.org>]

Hey all,

Niclas has made several points (open source as employment vs. volunteers,
the incubator) which relate to understanding our pipeline.

Our volunteer pipeline is little more complex than
contributor->committer->PMC

And it's likely that parts of that pipeline are in better shape than others.

To take one of many potential concrete examples: it's very likely true that
there are different obstacles to participation in open source for women as
part of their paid work for big tech companies (bias towards front-end work
perhaps), than there are for women who are doing open source as an
after-work hobby ("second shift" perhaps).

I'd like to see us map out our pipeline as a first step, before we start
hypothesizing what the problems might be, what questions we might want to
ask to narrow down our problems more precisely, and which areas we want to
focus on.

Waddaya think?

Best,
Myrle

Re: Mapping our pipeline before looking for leaks

[Myrle Krantz <my...@apache.org>]

Hey Gris,

Actually it's probably easiest if I just show you what I mean.  There's no
need to hold up any other tasks for this.  Let me try to find a good visual
representation for putting my ideas "on paper" and I'll send it around for
feedback.

Best,
Myrle


On Fri, Jul 19, 2019 at 6:59 PM Griselda Cuevas <gr...@apache.org> wrote:

> Hi Myrle,
>
> I'm not quite sure what mapping the pipeline means. In my opinion the
> subject of diversity is too broad and can have as many dimensions as we can
> possibly think.
>
> This is an important reason why I wanted to define values, a mission
> statement and goals for our committee. They would give us a framework to
> work with and decide what we work on and when.
>
> I'd say that personally I wouldn't like to complicate how we measure
> diversity in the community, the more dimensions we introduce the messier
> things can be.
>
> In my opinion, motivations for folks can vary, and they can be studied as
> part of the experience research. However the experiences people have in the
> communities aren't affected by this motivations necessarily. e.g. I'm a
> paid employee who is tasked to contribute to open source, my motivations
> change how long I'm willing to stand abrasions but doesn't change the fact
> that me or another non-native EN speaker will have the same trouble keeping
> up with lengthy threads.
>
> Right now I am not saying yes or no to this suggestion, I don't think I
> fully get it and the first impression it gives me is an extra complication
> to how we measure our current status.
>
> G
>
>
> On Fri, 19 Jul 2019 at 08:45, Myrle Krantz <my...@apache.org> wrote:
>
> > Hey all,
> >
> > Niclas has made several points (open source as employment vs. volunteers,
> > the incubator) which relate to understanding our pipeline.
> >
> > Our volunteer pipeline is little more complex than
> > contributor->committer->PMC
> >
> > And it's likely that parts of that pipeline are in better shape than
> > others.
> >
> > To take one of many potential concrete examples: it's very likely true
> that
> > there are different obstacles to participation in open source for women
> as
> > part of their paid work for big tech companies (bias towards front-end
> work
> > perhaps), than there are for women who are doing open source as an
> > after-work hobby ("second shift" perhaps).
> >
> > I'd like to see us map out our pipeline as a first step, before we start
> > hypothesizing what the problems might be, what questions we might want to
> > ask to narrow down our problems more precisely, and which areas we want
> to
> > focus on.
> >
> > Waddaya think?
> >
> > Best,
> > Myrle
> >
>

Re: Mapping our pipeline before looking for leaks

[Griselda Cuevas <gr...@apache.org>]

Hi Myrle,

I'm not quite sure what mapping the pipeline means. In my opinion the
subject of diversity is too broad and can have as many dimensions as we can
possibly think.

This is an important reason why I wanted to define values, a mission
statement and goals for our committee. They would give us a framework to
work with and decide what we work on and when.

I'd say that personally I wouldn't like to complicate how we measure
diversity in the community, the more dimensions we introduce the messier
things can be.

In my opinion, motivations for folks can vary, and they can be studied as
part of the experience research. However the experiences people have in the
communities aren't affected by this motivations necessarily. e.g. I'm a
paid employee who is tasked to contribute to open source, my motivations
change how long I'm willing to stand abrasions but doesn't change the fact
that me or another non-native EN speaker will have the same trouble keeping
up with lengthy threads.

Right now I am not saying yes or no to this suggestion, I don't think I
fully get it and the first impression it gives me is an extra complication
to how we measure our current status.

G


On Fri, 19 Jul 2019 at 08:45, Myrle Krantz <my...@apache.org> wrote:

> Hey all,
>
> Niclas has made several points (open source as employment vs. volunteers,
> the incubator) which relate to understanding our pipeline.
>
> Our volunteer pipeline is little more complex than
> contributor->committer->PMC
>
> And it's likely that parts of that pipeline are in better shape than
> others.
>
> To take one of many potential concrete examples: it's very likely true that
> there are different obstacles to participation in open source for women as
> part of their paid work for big tech companies (bias towards front-end work
> perhaps), than there are for women who are doing open source as an
> after-work hobby ("second shift" perhaps).
>
> I'd like to see us map out our pipeline as a first step, before we start
> hypothesizing what the problems might be, what questions we might want to
> ask to narrow down our problems more precisely, and which areas we want to
> focus on.
>
> Waddaya think?
>
> Best,
> Myrle
>