►
From YouTube: Turn Contributors into Maintainers with TAG Contributor Strategy - Josh Berkus & Catherine Paganini
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Turn Contributors into Maintainers with TAG Contributor Strategy - Josh Berkus, Red Hat & Catherine Paganini, Bouyant
TAG Contributor Strategy focuses on writing guides and templates to help CNCF maintainers build successful projects and communities. In this session, we will walk you through how to use a contributor ladder along with governance documentation to provide a structure for turning contributors into maintainers. This is done through a gradual process where contributors gain increased responsibility within a project jointly with governance documentation that defines the decision making process, values, and principles. The primary topics for this session will include: Promoting and recognizing contributors using a ladder framework The role of governance in contributor promotion and value communication Evolving these concepts as projects move from sandbox to incubating to graduated The audience will walk away with tools, templates, and best practices for building successful CNCF projects and communities.
A
A
We
have
done
presentations
before
and
how
to
attract
new
contributors
to
your
project,
which
is
also
an
important
thing,
but
that's
not
something
that
we're
going
to
be
covering
today.
Instead
we'll
be
covering
how
to
get
them
to
do
more
as
reviewers
or
doc,
writers
or
maintainers,
or
even
project
leaders.
B
B
Sorry,
oh
sorry,
yeah,
so
tack
control.
What
is
the
tech
contributor
strategy?
So
it's
a
group
from
the
cncf
with
the
goal
to
help
projects
like
yourself
be
successful
and
we
do
that
by
creating
guides,
docs
and
tools
that
you
can
use
and
apply
for
your
project.
And
why
would
we
do
that?
I
mean
there
are
so
many
other
projects
who
have
been
through
what
your
experience
is
today
right
like
facing
your
challenges
or
whatever
you're
trying
to
achieve
so.
B
A
Yeah
and
in
terms
of
sort
of
tangible
products
that
we
have
for
you
so
which
we're
going
to
be
discussing
today
is
the
tag
actually
produces
primarily
two
things.
One
is
templates
that
you
can
copy
for
your
project
and
use
for
project
paperwork
and
guidance,
documentation,
advisories
guides
to
you
know.
How
do
I
get
new
contributors
guides
to?
How
do
I
set
up
governance
and
that
sort
of
thing
advice
basically
for
running
your
project?
The
what
happened
there.
A
Oh
okay,
again,
okay
right,
the
project
templates
can
actually
be
found
in
cncf
such
project
template
we
created
as
a
separate
repository
in
case.
You
want
to
just
clone
it
or
merge
it
directly
into
your
project,
community
repository
in
order
to
use
some
of
these
templates
for
paperwork
that
the
cncf
requires
and
that
even
if
the
scenes
have
didn't
require
it
would
be
a
good
idea
for
you
to
have
them
the.
A
B
Yeah
and
so
you'll
find
the
contributor
growth
strategy
framework
there,
and
I'm
gonna
be
talking
mostly
about
that.
That's
a
very
high
level
overview
of
things
that
you
have
to
keep
in
mind
when
to
grow
your
contributor
base
and
a
lot
of
these
things
sound
very
common
sense,
but
it's
really
important
to
spell
them
out,
because
it's
often
kind
of
easy
to
forget,
so
everything
I'm
going
to
cover
there.
You
can
find
there.
So,
of
course
it
all
starts
with
contributors
right.
So
where
do
they
come
from?
B
And
how
do
you
keep
them?
So
initial
motivation
varies
as
much
as
people
themselves.
Of
course,
some
need
a
feature,
someone
to
learn
something
some
just
want
to
be
part
of
an
open
source
project,
and
so
there's
it's
difficult
for
you
to
control
that
trigger.
But
what
you
can
control
is
really
to
keep
them
motivated
once
they
are
once
they
started
contributing,
and
you
can
do
that
by
trying
to
create
an
really
awesome
and
welcoming
experience.
B
So
it's
really
important
to
be
really
cl
likes,
be
really
clear
about
the
level
of
effort
that
it
that
that
is
required
right.
What
are
contributors
getting
into?
How
much
time
will
it
take?
If
you
don't
spell
that
out,
they're
gonna
have
probably
false
expectations.
That's
going
to
lead
to
frustration
or
they
may
not.
Even
they
may
hesitate
to
contribute
in
the
first
place.
So
it's
really
important
to
to
to
be
very
clear
about
that.
B
Also,
when
you
in
your
docs
and
your
issues,
it's
very
important
to
be
very
descriptive,
the
more
descriptive
actually
the
better,
but
that
takes
time
right.
So
it's
very
easy,
especially
if
you're
very
busy,
it's
very
easy
to
kind
of
say
like
oh,
we
have
so
many
other
things
that
we
have
to
focus
on.
So
I
cannot
focus
on
this
right
now
but
like
if
you
don't
tell
contributors
exactly
what
they
need,
how
can
they?
B
How
can
they
know
what
you,
what
you,
what
you,
what
you,
what
you're
looking
for
right
so
you're
gonna
get
prs
that
are
not
reflecting
what
you
what
you
were
looking
for.
It's
gonna
lead
to
a
lot
of
back
and
forth.
It's
gonna
lead
to
frustration
and
yeah.
So
definitely
not
a
good
contributor
experience
and
not
good
for
you.
So
although
it
may
feel
like
it's
a
lot
of
time,
it
will
save
you
time
down
the
line.
The
other
things
are.
B
The
different
paths
that
you
can
take
and
josh
will
talk
about
the
contributor
ladder
in
a
little
bit,
but
just
on
a
high
level,
it's
basically
the
same
thing
as
a
career
right
like
when
you
are
starting
your
career
or
even
at
your
company,
now
you're
asking
contributors
to
dedicate
their
time.
So
they
need
to
know
what
they're
like.
Where
are
you
going?
Is?
Are
your
goals
aligning
with
their
goals
right
and
yeah,
so
they
they
want
to
make
sure
that
that
there's
a
it's
a
good
fit
for
them
as
well.
B
You
know,
I
think,
if
contributing
is
a
pain,
motivation
will
go
really
really
fast
and
doing
it
right
should
really
be
the
easiest
path,
so
contributing
should
be
easy
and
intuitive,
or
at
least
as
easy
and
as
intuitive
as
possible.
It
cannot
be
always
super
easy
right,
but
make
a
real
effort
to
make
it
really
smooth
and
then
the
documentation
that
goes
to
the
into
the
previous
point
as
well.
B
Right,
like
clear
communication,
clearly
communicate
what
they
should
do,
what
they
should
expect
when
they're
submitting
a
pr
that
will
smoothen
the
whole
process
as
well,
and
then
it's
important
to
minimize
the
steps
right
like
be
really
clear
about
the
development
requirements.
Point
that
point
them
to
the
right
tooling.
They
shouldn't
be
looking
around
right.
It
should
all
be
in
one
place
and
leverage
tools
to
minimize
to
reduce
the
steps
as
much
as
possible.
There
are
a
lot
of
tools
that
allow
you
to
automate
things
if
it
can
be
automated.
B
Your
contributor
shouldn't
be
doing
this,
but
we're
often
focused
so
focused
on
the
technology
that
we
forgot
about
the
human
element
and
that
overlooking
that
can
actually
really
discourage
people
and
we're
gonna
talk
about
the
contributor
letter
again,
because
it's
a
really
important
thing,
but
there
are
a
lot
of
small
things
that
are
really
important
and
make
like
a
and
have
like
a
huge
impact.
First
of
all,
and
that's
what
I'm
saying
it's
like,
it
sounds
really
common
sense
but
like,
and
you
know
like
when
you're
really
busy.
B
You
may
forget
right,
like
thank
every
single
person
contributor,
publicly,
especially
the
new
ones,
but
everyone
deliberately
create
a
welcoming
community
reach
out
start
a
conversation.
What
are
you?
How
are
you
using
our
project?
What
are
you,
what
are
you
working
on,
like
whatever
it
is,
try
to
make
that
one-on-one
connection,
especially
that's
especially
important
for
smaller
projects
once
you
scale,
it
will
become
a
little
bit
more
difficult,
but
there
are
tools
that
can
help
you,
so
there
are
like
community
crms.
I
don't
know
if
any.
B
I
know
that
a
lot
of
people
are
not
very
familiar
with
them,
but
they
are
really
helpful
because
they
help
you
keep
track
of
your
contributors.
You
can
even
automate
things
like
some
tools.
Allow
you
to
automate.
Thank
you
tweets
or
thank
you
messages
through
github.
They
can
aggregate
a
lot
of
data.
B
Mentoring,
of
course,
is
huge,
so
that's
very
that's
very
motivating
and
swag.
It
sounds
silly
right
but
like
becoming
part
of
the
project
becoming
part
of
the
tribe,
really
people
start
feeling
like
identifying
with
the
project
so
kind
of
being
away
being
able
to
kind
of
show
that
project
that
makes
them
proud
is
that
does
make
a
difference,
and
here
I
wanted
just
to
showcase,
like
the
recognition
one
of
the
recognition
programs
that
we
have
at
linker
d.
B
So
each
month
we,
the
community
nominates
a
hero
and
maintainers,
are
going
to
select
based
on
merit
and
we
have
three
different
categories:
code
content.
So
if
someone
wrote
a
really
good,
blog
or
or
spoke
at
a
conference
and
help
right
like
helping
on
slack,
we
value
a
lot,
because
that
takes
a
lot
of
time.
B
B
But
there
is
so
much
more
to
a
thriving
community
than
code
right
and,
of
course
you
need
awesome
features.
But
who
is?
Who
cares
about
the
features?
If
no
one
is
able
or
no
one
uses
your
project,
because
no
one
is
talking
about
it
right
or
if
it's
impossible
to
implement,
because
the
docs
are
incomplete
or
because
it's
difficult
to
get
help
because
the
maintainers
are
so
busy.
They
cannot
really.
They
cannot
really
be
there
and
explain
it
to
people.
B
But,
interestingly,
maintainers
themselves
are
kind
of
perpetuating
a
little
bit
that
burden
because
of
their
own
bias
towards
code,
and
so
because
open
source
projects
are
focused
on
technologists,
who
are
good
at
code
at
coding.
That's
what
they
value
most
right
and
then,
but,
as
I
said
before,
there's
so
much
more
to
it.
Right
like
like
than
a
bunch
of
developers,
you
have
you
need
so
many
different
skills.
You
need
people
who
have
the
skills
you
don't
have,
or
that
can
do
things
that
you
don't
have
time
to
do
so.
B
Basically,
you
need
a
bunch
of
people
with
a
bunch
of
different
skills
and
so
to
motivate
these
people
to
help
you
to
be
part
of
the
community.
You
have
to
be
really
inclusive
right.
You,
you
have
to
see
how
you
can
recognize
them
for
their
non
contributions
as
well.
So
that's
a
little
call
to
action
kind
of
like
thinking
about
that
reflecting
and
then
seeing
like
okay,
who
are
the
people
that
make
this
community
like
besides
the
code
like
who
make
this
community
much
better
and
then
thinking
about
how
to
recognize
them
as
well.
A
Now
all
projects
have
a
contributor
ladder,
whether
or
not
it's
documented
but
documented
contributor
ladders
make
it
explicit
what
contributors
need
to
do
to
reach
the
next
level
and
by
making
it
explicit.
It
really
helps
motivate
contributors
to
put
in
just
a
little
bit
more
effort.
Consider
the
difference
between
you
need
to
review
more
prs
before
we
make
you
a
reviewer,
and
you
need
to
review
five
more
pr's
before
we
make
you
a
reviewer.
A
The
you
know
and
there'll
be
a
whole
set
of
sort
of
other
responsibilities
that
go
with
it,
but
by
letting
people
know
and
giving
them
measurable
requirements
to
reach
the
next
stage
of
responsibility
in
the
next
stage.
The
next
sort
of
title
in
the
organization
that
also
lets
them
know
that
they're
going
to
be
quote
unquote,
rewarded
with
greater
authority
and
responsibility.
A
A
It's
going
to
be
a
real
tendency
to
promote
the
people
who
show
up
at
meetings
the
most
often
because
those
are
the
people
who
are
top
of
mind,
even
though
you
might
have
somebody
who
works
in
a
time
zone
on
the
other
side
of
the
world,
who's
been
doing
really
great
work
on
documentation
and
really
actually
ought
to
get
that
promotion
and
by
making
sure
that
you
don't
miss
people.
You
have
an
opportunity
to
promote
more
people,
and
for
that
reason
you
really
want
to
have
a
contributor
ladder.
A
A
So
now
we've
talked
about
all
the
things
to
do,
encouraging
I'm
going
to
talk
a
little
bit
about
sort
of
maintaining
state,
particularly
so
the
role
of
governance
and
say:
okay.
Well,
this
is
about
promoting
contributors.
Why
are
we
talking
about
governance?
Well,
I'll.
Give
you
that
in
one
word,
which
is
membership,
if
we
have
that?
Yes,
which
is
people
care
about
belonging
to
something
they
want
to
be
equal
participants
in
your
project
and
formal
written
governance,
is
one
of
the
ways
that
we
prove
to
them
that
they
are
equal
participants.
A
This
sounds
like
a
lot
of
stuff.
Keep
in
mind
that
this
grows.
The
idea
is
for
this
to
grow
with
your
project
right.
You
don't
need
to
have
all
of
this
when
the
project
is
very
small
and
it's
new
and
it's
at
the
sandbox
level,
and
you
don't
even
want
to
have
a
whole
ton
of
paperwork
at
that
level,
because
then
that
paperwork
can
be
daunting
to
people.
A
Your
contr
contribution
guide
gets
longer
with
stuff
about
testing
and
all
kinds
of
other
things
and
then,
eventually
by
the
time,
you're
a
graduated
project,
etc.
You
should
have
sort
of
all
of
the
documentation
and
all
of
the
practices,
even
things
like
individual
role,
handbooks
for
different
jobs
in
the
community,
for
people
to
step
into
so
to
sort
of
wrap
it
up.
B
Yeah
and
please
visit
the
website
and
check
out
all
the
resources,
and
if
there
is
something
that
you
need
and
you
don't
find
it
join
us
and
we
can
help
you
create
it
like
so
really
like
we
can
help.
You
connect
you
to
people
who
who
can
help
you
who
can
answer
all
the
questions
you
can
put
it
all
in
a
doc
and
it's
not
going
to
be
only
for
you
we're
going
to
contribute
to
it,
so
anyone
can
benefit.
B
So
that's
why
I
think
this
is
really
great,
like
that's
actually
how
I
worked
on
the
framework
with
some
other
people.
It's
like
just
talking
to
all
these
people.
I
would
not
have
been
able
to
do
that.
Just
like
saying
I
want
to
do
this
for
linker
d,
but
if
I'm
doing
it
for
the
tag.
So
if
you
have
an
idea,
we're
always
looking
for
new
projects
to
work
on.
C
C
A
B
I
I
you
can
my
my
feeling
would
be
it's
just
the
same
thing
I
mean
like.
Sometimes
you
feel
you
feel
that
someone
is
more
committed,
but
it's
basically
the
same
thing
as
in
the
job
market.
You
know
you
hire
someone,
you
invest
in
them
and
they
may
leave
too.
So
I
I
think,
like
it's
really
just
like
you
can.
Sometimes
you
can
tell,
and
you
have
a
feeling
if
someone
is
really
committed
and
then
you
have
to
make
a
bet,
but
it
can
go
wrong.
A
But
the
other
thing
is,
I'm
saying
is:
this
is
why
we
actually
spent
you
know
15
minutes
talking
about
about
keeping
your
contributors
motivated
to
contribute
more
right,
because
people
don't
just
leave
randomly.
They
leave
for
a
reason
and
honestly,
if
your
project
is
a
fun
place
to
be,
and
they
feel
rewarded
and
encouraged
and
respected
for
contributing
they're
more
likely
to
stick
around,
so
you
can't
determine
for
the
individual.
But
you
can
try
to
create
an
environment
where
they
are
less
likely
to
leave
and
more
likely
to
stick
around
and
do
more.
A
A
D
I
was
actually
wondering
you
keep
saying
the
word
project
as
in
singular
and
I'm
actually
part
of
a
company
where
we
have
an
organization
where
we
have
multiple
projects
we
have
actually
over
100
of
them
and
that's
100
different
maintainers
we're
working
with
and
many
many
contributors.
How
would
you
work
with
a
community
that
large
to
ensure
that
their
contributor
journey
at
an
individual
level
is
still
on
the
right
path
when
you've
got
hundreds
of
projects
to
look
after.
A
You
can
say:
well,
I
think
that
you're,
the
community
crm
person
here
the
so
wait.
So
the
first
question
is:
let
me
repeat
the
question
right
because
we
got
to
do
that
which
is
the
question
is
if
you
are
in
charge
of
an
organization,
and
you
have
dozens
or
hundreds
of
projects,
how
do
you
keep
track
and
work
with
the
contributors
of
all
of
these
projects
to
keep
them
moving
along
in
their
contributor
growth
path?.
B
I
think
it's
just
like
those
maintainers
have
to
see
themselves
like,
of
course,
you
want
it
as
an
overall,
but
I
think,
like
it's
per
project,
you
have
to
do
the
same.
Things
create
the
community
that
people
really
want
to
be
part
of
and
yeah.
Maybe
those
crm
tools
can
community
crm
tools
can
help
you
automate
some
of
the
stuff.
You
know
that
that
yeah,
so
you
don't
have
that
much
of
a
burden,
but
I
would
say
it's
the
same
thing
for
the
maintainers
themselves.
A
A
The
I
would
say
in
a
lot
of
cases
when
you
think
about
recognition,
programs
and
mentoring
and
motivation
and
stuff.
You
want
to
think
at
the
level
at
which
people
identify
as
part
of
a
community.
So
even
if
things
are
separate
projects,
you
actually
look
at
them
as
a
contributor.
If,
if
they
think
of
themselves
as
part
of
the
same
community,
you
want
to
look
at
them
as
a
single
contributor
base,
so
sometimes
you
create
groups
like
in.
In
my
case,
I
would
say
an
example.
A
The
ones
I
go
in
there
is
for
the
ml
data
pipeline
stuff.
You
know
across
strimzy
and
kafka
and
tensorflow
etc.
Is
that
group
tends
to
regard
itself
as
kind
of
a
continuous
community?
And
so
you
look
at
how
do
I
promote
people,
regardless
of
which
actual
project
they're
contributing
to
and
and
then
talk
to
those
maintainers?
As
a
group
also.
A
Okay,
oh
yeah,
the
okay,
so
the
question
was:
how
does
one
join
the
tag
and
find
the
meetings
so
for
finding
the
meetings?
The
cncf
has
a
cncf
community
calendar
that
has
google
and,
I
think
apple
calendar
as
well,
that
you
can
sign
up
for
and
then
you
can
see
all
of
the
meetings
which
is
really
the
best
way
to
do
it,
because
sometimes
we
change
our
meeting
times.
A
We
have
separate
meetings
of
the
tag
in
general
maintainer
circle,
which
is
another
thing
that
we
do
and
in
fact
we're
doing
later
today,
and
the
governance
and
contributor
growth
working
groups
because,
like
the
contributor
growth
working
group
right
now,
is
1pm
pacific
on
thursdays,
but
that
has
changed
and
will
probably
change
again
so
subscribe
to
the
calendar
for
other
stuff.
We
have
tag
contributor
strategy
channel
on
the
cncf
slack.