►
From YouTube: The Maintainer's Toolkit: Must-know CNCF Resources for Project O... Catherine Paganini & Dawn Foster
Description
Don’t miss out! Join us at our upcoming hybrid event: KubeCon + CloudNativeCon North America 2022 from October 24-28 in Detroit (and online!). 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.
The Maintainer's Toolkit: Must-know CNCF Resources for Project Owners - Catherine Paganini, Bouyant & Dawn Foster, VMware
Whether you are trying to build an active, welcoming community, manage contributors' expectations, or motivate members to take on more responsibility, managing an open source project can feel overwhelming. During this talk, TAG Contributor Strategy leads will discuss CNCF resources available to project owners to help achieve exactly that. You'll learn what resources are available, where to find them, and how to get involved to develop new resources for your project and others. Developed for maintainers by maintainers, these resources help projects implement battle-tested best practices from fellow project owners. They include templates for a contributing guide, contributor ladder, governance frameworks, security disclosures, and more. Plus general guidance to grow your contributor base. There is no need to reinvent the wheel. Whatever challenge you are facing today, someone surely solved it before. Join this community to exchange ideas, learn from one another, and build a thriving ecosystem of successful open source projects.
A
B
Yeah
sure
so
I've
been
in
the
technology
industry
for
over
20
years,
working
mostly
on
open
source
software
from
companies
like
intel
puppet
and
now
at
vmware.
I
am
director
of
open
source
community
strategy
within
the
open
source
program
office.
I'm
on
the
steering
committee
for
the
linux
foundation's
to-do
group.
I'm
a
governing
board
member
and
maintainer
for
the
linux
foundation's
chaos
project.
A
So
as
mentioned
we're
going
to
talk
today
about
cncf
resources
for
project
owners,
but
before
we
do
that,
let's
talk
about
why
we
do
a
toolkit
while
we
need
the
toolkit
at
all
right
because
maybe
you're
thinking,
if
we
have
great
code
that
solves
a
real
pain
point
and
have
dogs
isn't
that
enough,
but
it
turns
out,
of
course
that
is
the
basis.
That's
the
foundation,
but
there
is
a
lot
more
to
it
right
and
if
you
will
join
tomorrow's
keynote,
you'll
hear
that
project
is
very
much
like
a
lemon
tree.
A
A
So
here
you
see
a
lot
of
things
right.
You
see,
governance,
user
recruitment,
marketing
events,
it's
kind
of
overwhelming,
and
the
cncf
does
help
with
some
of
this
right.
You
get
marketing
support
pr
and
infrastructure
tooling,
but
what
about
the
rest?
Yeah
you're,
a
developer
you're,
not
necessarily
good
at
recruiting
contributors
or
motivating
them.
So
how
can
you
possibly
do
all
these
things
and
the
good
news
is
you
don't
really
have
to
figure
it
out
all
by
your
own,
because
we're
open
source
right?
A
We
are
a
commute,
it's
all
about
community
and
it's
not
only
within
your
project.
It
should
be
across
projects
and
the
cncf
is
our
common
home
right
and
it
really
provides
this
great
platform
for
us
to
connect
and
learn
from
each
other
exchange
ideas
and
really
create
this
thriving
ecosystem
of
successful
projects.
A
And
that
is
really
what
the
tag
contributor
strategy
is
about.
So
we're
a
group
of
people
from
a
variety
of
cncf
projects
that
are
committed
to
helping
projects
succeed
by
maintainers
for
maintainers.
We
define
strategies
to
build
scale
and
retain
contributor
communities.
So
if
you're
a
project
maintainer,
we
definitely
should
connect.
You
can
either
join
the
effort
or
just
use
the
resources,
and
so
let's
have
here
a
quote
from
one
of
the
people
of
your
peers,
who
has
been
using
it.
A
So
dipty
from
the
vitesse
team
said
that
the
tag
was
very,
very
useful
when
they
set
out
to
restructure
their
government's
governance
system
and
so
yeah.
Let's
have
a
quick
look
at
what
the
tac
contributor
strategy
offers.
Overall
like
there
are
three
main
buckets
once
you
have
the
maintainer
circle.
These
are
regular
events
where
maintainers
meet
to
discuss
how
they
run
their
projects
to
exchange
ideas.
These
are
super
valuable
ways
to
connect
and
learn
from
one
another
and
and
you
should
definitely
attend,
then
they're
like
information
and
training
resources.
A
So
first
thing
you
should
know
is
there
is
a
website
here.
You'll
see
two
options:
right,
one
for
maintainers
and
one
for
contributors
and
on
the
maintainer
side
you
will
see
all
the
available
resources
that
we'll
discuss
today
and
again.
These
are
developed
by
maintainers
for
maintainers
under
community.
You
will
see
three
different
resources.
One
is
the
community
crm,
runbook
project,
health
and
contributor
growth
framework.
A
So
in
this
run
book,
what
you
will
learn
is
what
these
crms
are
and
how
they
can
help.
You
and
you'll
learn
how
to
best
organize
your
projects,
for
instance,
how
to
how
to
break
it
down.
Maybe
in
sub
projects
or
tagging.
Your
members,
you
may
have
a
member,
a
community
member
who
likes
to
code
in
a
particular
language
or
has
a
very
particular
use
case
or
would
like
to
or
was
interested
in
speaking
about
your
project
right
and
so
by
tagging
them.
Maybe,
let's
say
a
year
from
now.
A
You
need
someone
with
that
skill
set.
You
can
easily
find
them,
because,
obviously
we
cannot
remember
all
these
conversations,
probably
whatever
you
had
whatever
conversation
you
had
like
two
months
ago,
is
probably
very
difficult
to
kind
of
remember
afterwards,
so
like
keeping
that
information
and
and
and
organizing
that
is
very
helpful
and
then,
of
course,
like
keeping
all
the
interact
history
of
all
interactions
right,
like
you're,
probably
interacting
with
a
lot
of
your
community
members
on
slack
that
is
all
suddenly
lost.
A
You
can
keep
a
record
of
that
search
for
that,
which
is
also
very
useful
when
you
wanna
go
back
or
kind
of
search
for
a
certain
conversation
or
a
certain
topic,
and
then
you
can
automate
a
lot
of
tasks.
For
instance,
a
tweeting
like
sending
a
tweet
thinking
a
contributor
each
time
a
pr
is
merged
or
set
reminders
for
things
that
you
have
to
do
regularly.
A
Then
there's
a
project
health
measurement
doc
which,
where
you
will
learn
how
a
healthy
project
looks
like
how
to
measure
project
health
and,
most
importantly,
how
to
make
sense
of
all
the
deaf
stats
that
you
get.
We
hear
a
lot
of
people
have
like
find
it
very
confusing,
so
there
you
learn
all
like
you
kind
of
know
how
to
navigate
those
stats
and
then
you'll,
learn
about
things,
how
responsiveness
impacts,
impacts,
project
health,
how
to
interpret
contributor
activity
and
even
a
contributory
risk.
A
So
if
that's
something
that
you're
interested
really
check
that
out,
there
are
lots
of
great
information
in
here
and
the
last
one
is
the
contributor
growth
framework.
This
is
a
document.
While
you
learn,
you
get
a
lot
of
tips
from
project
maintainers
on
how
to
motivate
and
keep
your
contributors
motivated,
how
to
incentivize
them
to
do
more
and
how
to
encourage
non-code
contributions.
A
B
Okay,
so
we
also
have
a
governance
section
on
the
contribute
contribute
site.
So
governance
is
all
about
alignment
and
getting
all
of
the
various
people
within
your
community
collaborating
together,
and
it's
one
of
those
things
that
you
may
think
you
don't
need
until
something
has
already
gone
wrong.
Expectations
aren't
aligned
you're,
seeing
unhealthy
dynamics
within
the
community.
B
B
Our
biggest
piece
of
advice
is
that
your
process
for
selecting
leaders
should
be
appropriate
for
the
size
and
type
of
your
project.
For
example,
small
projects
do
not
need
elections
to
select
leaders
from
three
maintainers
now.
The
good
news
is
that
tag
contributor
strategy.
We
are
here
to
help
you
put
all
of
the
pieces
together
to
make
leadership,
selection
and
other
governance
documentation
easier
with
governance
templates
that
any
project,
cncf
or
otherwise
can
use.
B
You
can
clone
the
repo
linked
on
the
slide
and
just
copy
the
templates
that
you
need
over
to
your
project
right
now.
We
still
have
the
comments
they're
embedded
in
the
markdown
file,
with
details
about
what
pieces
you
need
to
update,
but
we're
in
the
process
of
actually
moving
those
out
into
separate,
more
detailed
how-to
guides
to
make
them
easier
to
use.
B
B
Now
we
also
have
several
contributing
templates,
including
a
contributing.md
template.
We
also
have
a
reviewing.md
template
that
contains
a
reviewing
guide
that
your
project
can
use
to
provide
information
about
the
reviewing
process
for
your
project.
There's
also
a
contributor
ladder
template
that's
designed
to
be
used
with
any
of
the
various
governance
templates
to
help
your
contributors
understand
the
path
to
moving
into
roles
with
increasing
levels
of
responsibility,
including
various
leadership
positions.
B
We
also
have
maintainer
circles
which,
after
a
brief
hiatus,
are
resuming,
and
it
should
be
happening
about
once
a
month
or
so.
There
was
one
earlier
today
here
at
cubecon
that
was
focused
on
skills
required
for
doing
code,
reviews
and
other
types
of
reviews,
with
a
discussion
about
the
care
that
you
need
to
put
into
being
a
reviewer
and
we're
working
on
plans
for
the
next.
B
If
you
need
a
resource
that
doesn't
yet
exist,
there's
a
good
chance
that
someone
else
probably
needs
it
too.
So
we
encourage
you
to
join
us
and
help
us
build
new
resources,
we're
open
source
folks
right.
We
love
to
create
things
that
other
people
can
also
get
value
from.
So
why
not
share
what
you
come
up
with
with
with
the
rest
of
the
group?
B
Anyone
can
drop
into
our
meetings
the
tag
contributor
strategy
meetings
if
you'd
like
to
join
us
and
build
something
together
or
just
let
us
know
what
you
need.
You
can
also
drop
in
at
any
time
for
advice
about
any
aspect
of
contributor
strategy
for
your
cncf
projects,
because
we
are
here
to
help
you
and
here's
where
you
can
find
us
to
get
help
for
your
project
or
to
volunteer
to
help
us
build
new
resources,
we're
pretty
active
on
slack.
So
that's
a
good
way
to
reach
all
of
us.
B
So
tech
contributor
strategy
is
more
than
just
a
place
to
develop
resources.
We're
really
creating
a
cross-project
community
of
maintainers
who
can
connect,
exchange
ideas
and
support
each
other.
Managing
an
open
source
project
can
be
really
challenging,
but
a
supportive
community
can
provide
resources,
advice
or
maybe
just
listen
when
you're
struggling
with
something
and
when
you
use
our
resources.
Please
let
your
peers
and
other
people
know
how
useful
they
are
join
our
community.
B
You
can
meet
our
team,
you
can
get
involved
and
we
would
love
it
if
you
would
tell
people
about
us
so
feel
free
to
share
this
link
with
whoever
social
media
team
members,
people
who
might
be
interested
now.
What
we've
done
is
we've
left
a
load
of
time
at
the
end,
so
that
we
can
have
discussion
and
q
a
so.
If
you
want
to
ask
questions
about
any
of
the
stuff
that
we've
talked
about
or
have
a
discussion
about
any
of
this,
we
have
plenty
of
time
for
that.
So
thank
you.
B
B
A
Well,
the
question
was
regarding
examples
for
the
sierra
crms,
so
I
well
basically
the
run
book
is
so
I
don't.
I
don't
have
like
a
particular
project
in
mind.
I
know
that
several
are
using
it,
but
I
don't
yeah,
but
the
crm,
basically,
what
it's
doing.
We
kind
of
got
feedback
from
different
different
people
who
are
using
it
and
to
give
advice
on
how
they're,
using
it
so
yeah.
B
A
It
oh
okay,
so
generally
like
if
people,
if
users
get
like
impatient
and
start
like
asking
in
questions
and
then
you
get
like
plus
one
plus
language
learn.
So
I
don't
know,
I'm
just
gonna
say
my
opinion
and
then
we
can
say
so
I
think
in
general.
It
helps
like
I
mean
they're
all
humans
right.
So
sometimes
it
helps
to
explain
that
I
don't
know
if
you're
doing
it
full-time
or
not
full-time
or
something
it's
like
hey.
A
I'm
doing
it
also
on
my
spare
time
we're
all
like
kind
of
doing
it
on
on
the
side
and
kind
of
explain
a
little
bit
that
things
take
a
little
bit
more
time.
Expectation
management
in
general
is
kind
of
so
is
it
like
when
you're,
when
they're
asking
for
features
or
for
help
or
in
general
for
features
yeah.
I
think
I
would
just
explain
a
little
bit
like
hey
this.
Is
we
have
all
these
things
in
the
road?
A
B
Yeah
absolutely-
and
you
know
the
other
thing
could
help
if
you
have
like
a
road
map
or
a
project
board
or
something
where
people
can
see
all
of
the
other
things
that
you're
working
on
that
can
also
help,
because
you
can
see
that
you
know
we've
got
this.
We've
got
this
public
road
map
or
this
project
board
or
whatever
it
is,
and
these
are
the
things
we're
working
on
now.
B
This
is
where
we've
added
your
feature
and
it's
going
to
be
another
two
releases
because
of
all
of
these
other
things,
and
that
can
sometimes
help
people
put
things
in
context
too.
Any
other
suggestions
from
the
audience,
because
this
is
a
this-
is
a
discussion.
Yes,
here,
I'm
gonna,
I'm
gonna
mic
run.
D
One
thing
we've
done
is
offered
them
the
contributors
guide
in
terms
of
here's,
how
you
could
contribute
a
patch,
here's
kind
of
maybe
have
a
mentor.
That's
on
the
team
that
could
help
them
and
say,
if
you're
interested
and
really
want
it,
then
this
is
kind
of
because,
basically
you
can't
do
it
all
and
if
you're
really
busy,
sometimes
it's
like,
we
will
gladly
help
you
maintain
it
or
at
least
implement
it.
So
that's
another
way
of
kind
of
suggesting
to
them.
B
B
C
A
Not
necessarily
contact
information,
so
it
does
pull
information
from
twitter
slack.
So
it's
not
like
that.
You
get
their
emails
or
anything.
So
it's
not
like
a
sales
crm
right,
but
you
want
to
have
a
full
view
of
what
people
have
done.
You
know
like:
what's
what
what
what
they
have
said
and
on
on
on
in
your
slack
integration?
So
you
have.
It
starts
creating
profiles
based
on
how
people
have
interacted
with
your
project.
E
F
I
missed
the
beginning
of
this
session,
so
I
just
arrived
like
this,
but
it
comes
to
me
a
question.
I
was
earlier
at
the
maintainer
circle
and
here
there's
like
7000
people
attending
the
conference,
and
I
was
like
seeing
dozens
of
people,
and
here
I
don't
see
many
people.
So
is
there
like
a
major
need
to
welcome
more
contributors,
and
if
yes,
are
there
areas
where
we
could
help
like
technical
training
regarding
the
go
programming,
language
or
other
things,
or
what
is
the
major?
F
B
I
think
yes
to
all
of
that.
Frankly,
I
mean
it's
getting
getting.
Contributors
for
your
project
is
hard
right
and
we
have
a
lot
of
people
here
at
kubecon,
but
you
know
there's
only.
There
are
only
so
many
maintainers,
and
only
so
many
so
many
projects,
and
only
so
many
people
who
can
who
can
contribute-
and
I
think
you
know
anything
that
we
can
do
to
reduce
some
of
those
barriers
to
contributions
so
from
attacking.
B
B
But
it's
something
I
think
we
need
to
to
focus
on
and
spend
more
time
doing,
and
particularly
you
know,
people
from
maybe
other
backgrounds
who
wouldn't
necessarily
be
contributing.
How
do
we?
How
do
we
find
more
of
these
people
and
how
do
we
get
them
involved
in
our
projects
and
how
do
we?
How
do
we
help
them,
even
though
it
might
take
some
time
and
might
take
a
little
bit
of
help?
How
do
we
get
them
into
those
maintainer
positions?
B
And
so
I
would
I
would
take
a
close
look
at
all
of
your
project
docs
and
your
contributing,
docs
and
you'll
think
about
what
you're
doing
to
make
it
easier
for
new
contributors
and
then
also
think
about
other
programs.
You
could
put
in
place
so
kubernetes
contributor
experience
sake
has
some
fantastic
ones.
They
have.
You
know.
Kubernetes
does
a
lot
of
shadowing,
so
the
release
team
has
shadows.
So
you
know
the
all
of
the
various
components
within
the
release
team.
B
Everybody
has
a
shadow
who
will
eventually,
hopefully,
if
they
they
do
well,
then
move
up
into
that
leadership
position.
We
did
the
same
thing
for
for
other
parts
of
kubernetes,
and
so
you
know
think
about
whether
you
can
put
in
place
some
some
shadowing
programs
for
various
elements
of
your
community
and
where
can
you
get
people
engaged?
You
know
honestly
kubernetes
a
lot
of
people
get
involved
in
sig
release
because
it's
you
know
they
can.
B
B
E
E
Before
that,
but
that's
that's
trying
to
grow
the
community,
but
sometimes
we
also
need
to
think
about
how
we
grow
ourselves.
We
often
come
into
a
leadership
position
because
we're
good
at
coding
or
the
that
traditional
side
of
things,
but
you
need
to
to
avoid
burnout
yourself.
You
need
to
spread
the
workload
and
pull
other
people
in
who
can
do
different
things
and
also
learn
to
learn
new
skills
about
leadership.
E
Part
of
that
might
be,
instead
of
writing
code
writing
a
business
case
to
encourage
businesses
to
incentivize
their
employees
to
care
about
these
things,
and
that's
not
natural
for
most
of
us.
So
we
have
to
stretch
to
learn
how
to
make
those
types
of
arguments
and
then
one
other
last
thing:
I'd
give
a
plug
for
cncf.
E
They
do
have
marketing,
for
this
isn't
kubecon.
This
is
kubecon
cloud,
nativecon,
there's
a
whole
bunch
of
projects,
and
there
is
an
effort
to
get
the
word
out
more
about
other
projects
and
what
they're
doing
and
where
they
need
help
as
well.
So
as
maintainers
leverage
that
the
cncf
is
a
foundation
that
exists
for
you,.
B
Yeah,
that's
a
really
good
point,
because
there
are
loads
of
other
cncf
resources
that
you
can
tap
into
there's.
Actually
a
social
media
channel
on
the
cncf
slack,
and
you
know
if
it's
project
related
and
it's
neutral
and
it's
not
coming
from
a
company
account
they're
generally
happy
to
retweet
lots
of
things.
B
So
if
you
need
contributors
for
your
project,
your
cncf
project-
and
you
know-
maybe
there's
a
specific
area
that
you're
looking
for
you-
can
you
can
get
the
cncf
social
media
to
retweet
things
and,
and
you
can
tap
into
the
you-
know,
cncf
marketing.
Depending
on
what
level
your
project
is
on,
there's
different
support.
A
B
A
Yeah,
just
like
I
mean
like
just
reach
out
to
them
and
they're
again,
they're
super
supportive
and
said
like
hey:
can
we
do
a
blog
post
and
then
they
they
got
us
lots
of
opportunities
as
well
yeah
to
just
get
a
little
bit
more
awareness,
so
they
are
very
helpful.
You
just
have
to
reach
out.
They
just
may
not
know
that
you
need
them
right
now.
So
I
think
the
marketing
in
pr
the
two
areas
where
you
can
do
a
lot
with
them
and
they
can
do
a
lot.
They
can
help
a
lot.
H
I
could
have
asked
why
you
were
still
here.
I
think,
there's
a
bit
of
a
conflict
between
like
the
the
many
things
that
maintainers
already
have
on
their
plate
and
setting
up
additional
processes
and
the
governance
structure,
where
you
have
regular
meetings
in
the
board,
and
so
I
don't
know
how
to
overcome
this,
but
it
feels
like
extra
work
in
addition
to
the
work
you
already
have,
and
that's
already
too
much
so
I
don't
really
know
how
to
motivate
a
maintainer
community
to
say.
H
G
I
work
with
a
lot
of
the
smaller
projects
in
cncf,
and
the
answer
to
this
is
look
for
ways
to
do
this
with
minimal
effort.
I
would
say
things
like
you
should
have
a
weekly
community
meeting,
and
that
doesn't
mean
that
you
should
have
a
separate
meeting
that
is
specifically
a
community
meeting.
It
means
when
you
do
your
weekly
development,
sync
meeting
or
bi-weekly
development.
G
Sync
meeting
make
that
open
and
recorded,
because
actually
it
turns
out
your
biggest
problem
with
regular
community
meetings
is
that
you
don't
have
a
lot
of
people
other
than
your
maintainers
show
up,
and
this
way
at
least
you're
getting
some
work
done.
If
nobody
else
shows
up
and
if
somebody
does
show
up
they're
gonna
immediately
get
drawn
into
whatever
it
is.
B
Yeah
and
the
other
thing
you
can
do
is
kind
of
rotate
some
of
the
responsibilities
around
that
can
help
too,
where
it's
not
one
person,
one
particular
maintainer
getting
stuck
with
doing
everything,
but
you
can
kind
of
shift
things
around,
so
the
different
people
are
responsible
for
at
different
times.
That's
worked
pretty
well
with
the
kubernetes
community
meeting
in
particular,
where
different
people
lead
it
every
every
month.