►
Description
CNCF SIG Contributor Strategy Contributor Growth WG 2021-03-02
A
A
B
A
B
B
B
B
A
A
Yeah
so
I
I
did
put
a
pull
request
because
there
were
like
some
links
missing
and
some
spacing,
and
then
there
was
like
a
sentence
that
shouldn't
have
made
it
in.
That
was
like
the
copy
and
paste
kind
of
stuff
that
not
only
that
one
that
we
fixed
but
another
one.
It
was
not
so
so
that's
still
in
right
now.
Do
you
want
me
to
share
screen
or
like
if
you
or
just
what
did
you
mean
with
going
through
it.
A
A
Carlessia
mentioned
something
about
tilt
and
I
put
something
in
there,
but
it's
like
it
needs
a
proper
description
because
it's
like
sometimes
because
I'm
not
that
technical
like.
If
I
look
at
the
website,
it
doesn't
really
tell
me
what
the
value
is
in
here
and
I'm
sure
there
are
like,
maybe
some
other
things
and
they're
like
that,
could
go
in
here.
So
there
are
parts
where
I
would
love.
Someone
to
you
know
have
a
look
and
see
specifically
with
the
technical
parts.
To
be
honest,
it
was
in
the
pr
process.
A
It
was
really
like.
Okay,
I'm
just
typing
what
people
are
telling
me,
because
I
don't
really
understand
the
process.
So
it's
just
like
for
me,
but
I
think,
like
scott
looked
over
it,
so
I
think
that's
probably
fine,
but
with
the
tools.
Maybe
there
is
like
something
that
we
want
to
add
here.
It's
like.
I
don't
know.
D
So
when
I
read
the
tools
section,
it's
intended
to
be
examples
of
how
you
can
help
people
with
tools,
not
recommendations
for
tools,
I
would
say,
or
a
thorough
explanation
of
the
value
prop.
So
I
think
what
you
had
was
fine
I'll,
definitely
recheck.
It,
though
I
think
only
one
of
them.
I
commented
on
because
it
was
a
little
confusing
docker
yeah
I
mean,
but
I
wouldn't
worry
about
trying
to
capture
like
selling
tilt
or
why,
like?
It
only
makes
sense
if
it
makes
sense
for
your
project
and
they're.
D
A
A
D
A
Okay,
that
was
like
mostly
the
thing
and
it's
like.
If,
if,
if
you
feel
look,
I
mean
it's
not
yes,
as
you
said,
it's
nothing
like
super
prescriptive.
It's
like
very
high
level,
so
I
I
I
don't
know
if
anything
is
missing
or,
and
the
other
one
the
so
the
next
section
is
actually
should
be
become
a
pr
very
soon.
Hopefully,
tomorrow.
D
D
B
A
Yeah,
well,
there
are
a
lot
of
things.
So
why
don't
like
we
like?
We
have
the
problem.
Is
it
is
kind
of
a
beast
right,
so
they're
like
well,
this
is
the
biggest
section
and
it
becomes
smaller
each
one
yeah,
probably
as
well,
because
it
was
the
interviews
and
people
were
getting
tired,
but
also
like
these
are
kind
of
the
main
sections
too.
So
I
don't
know
if
yeah.
A
If
so,
I
don't
know
what
what
we're
gonna
do
with
this
anyways
like
one
like
once,
it
is
all
there
and
we
got
feedback
or
didn't
get
feedback.
It's
now
in
the
draft
folder.
What
what
are
like?
What
are?
I
mean,
of
course,
at
some
point.
We
want
it
to
be
on
a
website
where
everyone
can
access
it,
but
like
the
website,
isn't
live
yet
right.
So
that's
also
like
a
long
process,
and
I
don't
know
why
it
looks
so.
Nice.
B
D
B
A
B
D
B
B
B
B
B
A
Just
because
it
has
several
sections,
should
we
kind
of
do
them
one
by
one
like
this
one,
like
I
just
want
to
have
those
questions
like
still
answered
right,
but
like
once,
we
feel
this
is
like
ready
for
that.
Should
we
just
put
the
sections,
I'm
just
thinking
about
user
friendliness,
because
it's
like,
if
it's
like
five
at
once,
it
may
be
overwhelming,
or
do
we
wanna
have
it
like
ready
and
then
put
it
all
in
there?
I'm.
D
D
D
D
A
E
E
I
kind
of
can't
remember,
because
we've
been
going
back
and
forth
about
it
was
kind
of
having
like
a
well
I've
now
named
it
the
expansion
pack,
but
it's
like
an
expansion
of
the
maintainer
section
because,
based
on
some
of
the
bigger
projects,
there
are
more
categories
under
maintainer
so
hold
on.
Let
me
drop
the
link,
I
know
just
not
careless
comment,
so
I
haven't
deleted.
E
So
basically
I
made
a
duplicate
version
of
the
original
one
that
we
had
and
I
need
to
clean
up
the
maintainer
expansion
pack,
but
essentially
that
would
be
like
a
sorry.
My
cougar
clock
is
off
and
anything
else,
but
basically
we
were
gonna.
Have
this
expansion
pack
be
more
more
specific
to
like
the
different
maintainer
roles
that
we
talked
about?
So
I
think,
as
of
right
now,
what
would
fall
under
that
would
be
like
the
community
maintainer
project
manager,
which
stephen
augustus
gave
us.
E
D
B
E
B
D
B
Yeah,
the
because
I
mean
like
the
maintainer
well
once
we
have
this,
I'm
going
to
make
some
changes
to
the
maintain
to
the
maintain
our
council
governance
template
to
take
some
things
out
and
simply
direct
people
to
contribute
a
ladder
template
so
the
because
better
than
having
sort
of
duplicate
stuff.
For
one
thing,
I'm
already
dealing
with
some
projects
that
have
two
different
definitions
of
a
maintainer
in
two
different
documents.
D
E
E
E
B
B
E
B
E
C
D
E
B
A
Not
like
extended
ladder
contributor
ladder
because
it's
an
extension
right
like
once
you
grow,
you
extend
it.
What
was
it
extended,
bladder
or
yeah?
I
think
the
one
would
be
like
the
basic
right
like
that's
what
you
need.
The
core.
Any
project
needs
those
and
then
the
extended
leather
is
like
once
you
grow.
You
start
needing.
You
start
to
need
additional
necessarily
all
at
once,
but.
A
Yeah
and
I
have
a
question
regarding
the
community
manager
because
we
were
kind
of
brainstorming
about
creating
that
role
as
well
for
linker
d,
but
not
so
much
for
the
social
media
part,
but
more
like
helping
like
really
foster
an
engaging
community
being
like
help
answering
questions.
I
feel
like
that
really
is
part
of
it
right
like
someone
who
helping
people
identify
people
who
have
a
story
to
tell
and
then
encourage
them
to
tell
that
story
right
like.
B
The
these
all
need
to
be
filled
out,
so
we
could
really
use
your
help
with
that,
because
if
you
look
at
the
earlier
roles
in
sort
of
the
core
set
like
like,
you
know
the
basic
maintainer
role,
for
example,
we
have
this
criteria
and
responsibilities
and
privileges
with
each
one,
and
we
really
need
to
have
that
with
all
of
these
roles.
We
just
have
not
filled
that
out
yet.
B
E
Yeah,
okay,
so
kind
of
going
back
to
what
we
were
saying
with
the
like
umbrella
category
being
maintainer,
then
do
we
so
right
now
under
maintainer?
There
is
the
criteria,
responsibilities
and
additional
privileges
sections.
Do
you
want
to
just
take
it
out
under
the
like
under
the
maintainer
section
and
then
create
you
know
a
set
for
each
subset
or
or
do
we
want
one
that
is
like
a
general
maintainer
list
that
would
apply
to
the
community
manager,
the
project
manager,
release
manager
and
like
so
on,
and
so
on.
E
D
They
may
have
been
contributing,
but
in
a
different
way
like,
for
example,
they
may
be
showing
up
to
meetings
and
helping
to
design
and
lay
out,
like
your
plans
for
doing
a
whole
bunch
of
things
and
being
extremely
engaged.
They
may
have
never
actually
worked
on
a
pr
with
you,
though,
I'd
be
concerned
that
the
criteria
would
make
people
who
are
coming
from
a
different
method
of
engaging
with
the
project.
Yeah
feel
like
they
can't
be
this
unless
they've
been
doing
prs,
because
a
lot
of
these
things
don't
happen
in
prs.
E
Yeah,
so
I
think
that
was
kind
of
like
what
I'm
getting
at.
We
can
either
structure
it
where
we
put
the
initial
set
of
criteria,
responsibilities
and
privileges
at
the
beginning
for
all
maintainers
and
just
make
it
like
really
really
generic
and
then
like
do
like
the
you
know,
additional
points
under
each
category
of
like
the
different
kinds
of
maintainers,
or
we
scrape
the
generic
criteria,
responsibility,
privileges
and
then
just
do
each
section.
With
those
points.
D
Do
generic,
but
I
think,
instead
of
thinking
about
specific
activities,
yeah
looking
for
a
general
level
of
responsibility
towards
the
project
and
people
have
demonstrated
it
already,
so
they
are
coming
to
meetings.
They
are
engaging
with
new
users
and
helping
them.
They
are
aware
of
and
helping
to
make
decisions
for
the
project,
like
I'm,
maybe
not
saying
these
great
because
I
probably
want
to
like
think
about
it
before
I
write
them
down,
but
it
has
nothing
to
do
potentially
with
conference
speaking
obligations
or
pull
requests
or
anything
like
that.
D
D
Right
yeah
so
for
general
criteria,
but,
like
I
think
those
like
what
we
have
right
now
is
perfect
for
code
maintainer,
right
yeah
and
we
can
just
start
over
and
make
just
more
general
things
like
do
they
have
the
right
attitude?
Are
they
demonstrating
that
they
will
be
a
responsible
maintainer
already,
you
know,
yeah,
not
they're
doing
certain
actions.
The
actions
are
going
to
be
different
for
each
one
of
these
roles,
but
in
general,
there's
a
there's,
a
different
attitude
of
someone
who's
trustworthy.
D
A
A
Then
it
gets
like
if
you
go
specific,
it
has
it's
completely
different,
because
these
are
and
that's
why
I
think
sometimes
the
word
letter
is
a
little
misleading,
because
it's
not
one.
It's
like
you
have
like
these
parallel
tracks.
Right,
if
you're
community
manager,
I
mean
yes,
you
need
to
understand
the
technology
to
help
and
so
on,
but
it's
like
it's
I
mean
yeah.
You
don't
have
to
have
gone
that
path.
You
you
maybe
you're
super
you.
A
You
enjoy
helping
people
and
you
know
engaging
with
the
community
and
you
know
it's
a
different
track
with
docs
manager.
I
think
it's
even
more
clear
because
it
can
be
a
technical
writer
who
has
never
submitted
a
pr.
So
it's
like
you
want
someone
who
has
like
really
good
skills
at
writing
and
explaining
technologies.
That's
their
strongest.
You
know
characteristic,
not
necessarily
like
triaging
and
things
like
that.
Yeah.
D
So,
for
example,
on
porter
we
have
a
docs
manager
and
she
she
didn't
get
the
role
by
submitting
a
ton
of
prs
the
docs.
It
was
all
through
giving
us
on
advice
on
how
to
do
our
docs
and
then
maybe
she
shut
off
all
the
meanings
and
then
was
able
to
give
us
feedback
on
like
where
we're
missing,
how
we
should
organize
it
all
sorts
of
stuff
that
none
of
it
gets
captured
and
get
up.
D
D
D
D
E
Our
approver
is
on
the
the
other
one
yeah,
the
other
one
because,
like
I
guess
like
regardless
of
how
or
that
seems
like
something,
that's
more
of
a
generic
role
than
like,
or
that
like
yeah,
like
most
projects,
will
have
regardless
so
that
one's
sitting
there.
Do
you
think?
Okay,
that's
where
I'll
edit
it
then
I
just
want
to.
D
D
D
You
know
that
kind
of
stuff,
like
there's
importer,
for
example,
people
like
to
be
able
to
assign
issues
to
themselves
and
pick
them
up,
and
you
know
we
have
like
a
lot
of
stuff
in
the
backlog
and
we
don't
want
to
be
like
ask
and
maybe
we'll,
let
you
so
as
soon
as
someone's
done
their
first
pr.
They
become
a
an
org
member
just
so
that
they
can
assign
an
issue
to
themselves
and
claim
it.
F
A
So
I
think
I'm
gonna
drop,
but
I
think
I
would
like
to
help
with
the
community
manager
thing
just
because
I
was
like
thinking
it
through
and
if
you
need
more,
you
know
areas,
but
you
are
working
now.
So
this
is
so
it's
not
you
you're,
not
working.
This
is
not
merged
yet
so
like.
Where
is
like
the
best
way
to
kind
of
add
ideas,
or
should
I
just
you
know
you.
D
A
A
D
E
E
D
I
guess
I
think
in
because
we
almost
for
the
most
part
work
in
github.
I
think
all
the
cncf
does
github
it's
easy
to
conflate
the
github
organization.
Member
with
this.
Maybe
if
we
called
it
project
member,
it
would
not
be
like
there
wouldn't
be
like
we
wouldn't
have
to
like
have
a
caveat.
We're
like
this
doesn't
actually
mean
github
organization
member.
D
E
D
E
D
I'm
saying
it's:
that's
like
a
technical
mechanism
for
doing
voting
yeah,
but
this
role
right
here
that
we're
describing
has
nothing
to
do
with
github.
It
has
to
do
with
just
categorizing
your
relationship
to
the
project,
and
so
we're
saying
like
when
we
say
the
word
organization.
What
does
that
refer
to
when
you're
talking
about
a
cncf
project?
E
D
D
D
E
E
D
E
D
D
D
D
D
D
D
B
B
E
D
D
F
D
D
D
D
D
Thing
right:
it's
yeah
it's!
This
is
a
very
and
that's
why
I
was
kind
of
like
picking
on
it.
A
bit
is
it's
very
specific
to
kubernetes
right,
so
in
kubernetes,
no
one
has
commit
access
to
be
clear.
Everything
goes
through
prow,
which
is
like
this
github
automation
that
they
have
yeah,
and
you
leave
a
comment.
D
If
you're
a
reviewer
and
you
say,
slash
lgtm
and
if
you're
approver,
then
you
can,
you
can
do
slash
lgtm,
but
you
can
also
do
slash
approve
so
like
an
approver
can
just
you
know,
merge
the
thing
all
by
themselves,
pretty
much
yeah
and
then,
if
you're,
a
reviewer
you're
able
to
do
the
work
of
the
code
review
and
then
maybe
make
it
a
little
easier
for
the
approver
to
just
go.
Yes,
this
looks
good
in
general
and
trust
that
the
review
was
done
well.
Okay,
like
every
project,
has
different
rules
about
that.
E
B
D
There's
people
who,
who
don't
have
as
much
trust
so
like
they
can
help
review
and
they
they
can
be
like.
Oh,
this
style
is
wrong
or
whatever,
like
help
fix
the
code
and
get
it
up
to
speed,
but
that
second
person
could
be
a
maintainer
could
be
the
approver
has
to
make
a
decision
on.
Like
is
the
whole
thing
actually
implemented.
The
way
we
wanted
it
to
be.
Is
it
ready?
Are
there
gaps?
You
know?
Is
this
safe
to
bring
in.
E
D
D
E
D
E
D
E
D
A
E
D
E
E
D
E
D
E
D
I
think
we
want
to
be
careful
about
how
we
frame
it,
because
I
don't
want
it
to
be
like
well
the
default
best
first
class.
Whatever
one
is
the
code
one.
I
just
more
meant
that
the
description
right
now
for
maintainer
includes
a
lot
of
technical,
like
code
contributions,
because
the
contributor
reviewer,
if
you're,
trying
to
become
a
compute,
a
community
manager,
for
example,
you're
not
going
to
do
those
right
and
there
should
still
be
a
way
to
do
it.
D
D
That
was
that
attitude
stuff
yeah,
that's
your
responsibility,
yeah
and
then,
because
we
did
that
maintainer
doesn't
mean
just
code,
maintainer
yeah,
someone
with
decision
making
capabilities
on
the
project,
and
then
there
are
different
types
of
maintainers
and
code.
Maintainer
is
quite
available
to
these
other
ones.
E
E
And
then,
when
we
were
on
our
call
last
thursday,
josh
mentioned,
like
the
other,
the
the
newer
or
the
additional
ladder
being
more
like
a
breakout
of
the
maintainer
section,
and
so
now
I'm
wondering
like
the
way
you're
phrasing,
the
code
main
camera
roll.
You
know
if
we're
trying
to
not
necessarily
give
any
weight
to
any
one
kind
of
maintainer
than
another
should
be
throw
the
ones
that
are
in
them
spa
in
the
expansion
pack
back
in.
D
Oh
no!
Oh
okay!
I
don't
I
don't
think
so,
and
I'm
I
want
to
make
sure
that
my
suggestion
makes
sense.
Okay,
I
think
it's
trying
to
address
what
you're
talking
about
here,
where
it
says
maintainer
right,
we're,
gonna
change
it
so
that
none
of
the
criteria
or
tasks
are
about
code,
committing
code
reviewing
code,
all
that
stuff
that
we
think
of.
E
D
A
D
E
D
I
think
it's
big
enough
and
the
idea
is
that
maintainer
is
the
the
top
ladder
right
yeah,
so
you've
made
it
to
the
top
of
the
ladder.
It's
just
a
question
of
like.
Are
you
on
the
left
side
of
the
ladder
to
the
middle
side?
Yeah?
Maybe
okay,
you
know
like
who
are
you
standing
next
to
on
the
ladder
and
they're
all
different
people?
E
D
D
D
Oh,
I
see
your
question
like
what
we
call
it
yeah,
it's
still
a
template
yeah.
I
would
just
maybe
call
it
if
I
I
got
to
just
pick
and
I
wrote
down
whatever
I
felt
like
I'd,
probably
call
it
contributor
ladder,
maintainer
types,
template
and
I
know
it's
wordy,
but
yeah
yeah.
I
like
that
and
then
it'd
be
clear.
It's
kind
of
like
a
sub
document
just
so
it's
not
ginormous
and
it's
easy
to
see
that
they're
all
equal
at
that
point.
E
D
E
D
E
E
Think
it's
six,
but
I
don't
think
you
have
to
be
elected
per
se,
I'm
thinking
of
like
one
specific.
Can
you
say
it
we're
recorded,
so
I
don't
know
yeah,
which
one
it
is
well.
I
can't
remember
specifically
and
also
like
I
can't
say,
but
more
so
that
like
they're,
like
just
that,
like
the
role
that
someone
took
up,
wasn't
necessarily
dictated
by
like
a
voting
system.
E
D
D
D
You
may
be
a
maintainer
just
for
a
single
repository
yeah,
because,
like
porter
does
that
we
have
like
lots
of
repos,
and
some
people
are
just
a
maintainer
for
one
of
those
repos
but
they're
a
maintainer
they're
not
called
they're,
not
less
than
other
people.
It's
just
the
scope
of
their
decision.
Making
capabilities
is
restricted
to
that
repository.
E
D
D
D
E
Okay,
so
maybe
it's
more
of
like
thinking
it
from
thinking
about
it,
not
from
the
not
so
much
the
angle
of
like
how
much
they're
overseeing
but
more
so
like
kind
of
like
the
discipline.
That's
probably
not
the
best
word,
but
just
kind
of
like
the
kind
of
stuff
that
they
would
do
right
like
because
it's
like
the
nature
of
like
being
a
community
manager
like
the
nature
of
the
work
that
you
do,
will
be
very
different
from
a
docs
manager.
And
that's
why
we're
like
we're
splitting
yeah.
E
E
E
D
D
D
E
E
D
Yeah
does
that
make
sense,
and
then
so
I
got
rid
of
what
I
want
to
get
rid
of
I'm
going
to
delete
it
real,
quick
and
then
don't
cry.
I
do
this.
Does
that
make
sense
yeah,
but
I
don't
want
to
lose
the
changes
you've
made,
but
I'm
just
saying
like
that,
should
any
changes
we've
made
to
that
should
just
go
in
the
other
document
and
we
can
get
rid
of
this
section.