►
From YouTube: CNCF SIG Contributor Strategy 2020-04-13
Description
CNCF SIG Contributor Strategy 2020-04-13
Contributor Growth Working Group
A
A
B
B
C
B
B
Yeah,
let's
do
it
all
right
and
then
all
right,
so
everybody's
got
the
agenda.
All
right,
I
went
ahead
and
did
a
launch
contributor
growth
sub-project
issue,
and
there
is
a
lot
on
there
and
the
method
behind
the
madness
here
and
let
me
share
my
screen
as
well
from
tab
where
you
at
here
do
our
share.
B
So
obviously
we
need
things
like
a
readme
who's,
owning
much
dream,
just
some
very
basic
conceptual
foundational
things
right
now
that
we
need
to
figure
out
so
that
we
can
really
get
moving
so
before
I
start
I
do
folks
want
to
do
intros,
not
sure
if
everybody
knows
each
other,
let's
just
do
intros
just
just
to
be
just
to
be
safe.
Hippie,
you
go
first
I'm
looking
at
you
know
your
and
give
it
a
little
brief.
Give
a
brief
intro
about
yourself
and
why
you're
here,
and
why
you're
interested
in
doing
this
work.
C
For
a
while
and
I'm
really
fascinated
by
our
community's
ability
to
scale
in
to
be
inclusive
and
I,
think
that
what
we
do
here
to
be
really
useful
in
other
organizations
and
so
I,
particularly
the
key
factor,
is
to
be
growing
new
people
into
leadership,
and
so
the
strategy
that
we
have
for
helping
everybody
start
from.
What
is
this,
and
what
into
being
here,
please
come
join.
That's
why
I'm
here
awesome.
B
E
A
A
People
who've
been
doing
this
stuff,
and
so
so
I'm
here
to
learn
and
then
also
I
think
in
a
sense
the
bubble
up
the
stuff
from
all
of
my
teams
up
to
kind
of
see
like
what
all
the
different
concerns
are
out
there
yeah
and
how
many
of
you
how
many
of
your
projects
are
in
CNCs.
Just
out
of
curiosity,
oh
there's,
home
brigade,
virtual
cubelet,
SMI
just
joined
and
then
there's
like
other
projects
from
like
sister
teams,
Cato
as
well
so
ya
know
just
curious
yeah.
F
G
Didn't
have
so
much
stuff
to
say
here,
but
as
Amy
mentioned,
we
both
work
at
C
and
see
if
specifically,
my
cell
phone
used
to
be
there
Kim
Benitez
contributor
for
a
while
and
used
to
work
with
the
community
to
contribute
to
experience
for
a
while.
But
besides
that
also
helped
CN
CF
is
our
contributor
initiatives,
manager,
initiatives
and
all
the
related
stuff
whoo.
B
And
you
are
awesome
thanks
so
much
for
helping
us.
This
is
gonna,
be
awesome.
We
do
have
for
folks
that
were
not
on
the
last
contributor
strategy
meeting
or
and
other
folks
discussed,
like
what
repo
we
own,
why
we
own
them,
etc.
We
kind
of
came
to
this
conclusion
that
the
CNC
F
contributor
strategy,
repo,
which
is
like
our
Sigma
doe
repo,
will
have
things
about
our
processes.
Maybe
our
guidance
things
along
those
lines,
and
then
we
also
have
the
CNC
F
contribute
repo
as
well
folks
that
thought
that
contributors
might
see
that
more.
B
We've
also
been
working
hard
on
github
management
and
admin
related
stuff,
a
or
Steven
Jared,
so
many
others
Josh
to
get
us
all
hooked
up
with
some
kind
of
workflow
and
process
and
review
process
and
things
along
those
lines
for
stuff
that
we're
putting
inside
of
our
repos.
And
the
one
thing
we
do
want
to
make
sure
of
is
that
we
are
not
like
blatantly
putting
our
employers
stuff
in
as
guidance
like
meaning
as
the
word,
if
it's
in
as
like
as
a
resource.
B
That's
one
thing,
but
if
it's
in
his
guidance
and
we're
like
saying
XYZ
company
says
that
you
should
do
it
this
way,
we
should
just
make
sure
that
our
guidance
is
a
little
bit
more.
What
sort
of
looking
for
not
you
know
non
bias
or
you
know
not.
You
know
geared
towards
a
company
but
geared
towards
us
as
a
group,
so.
E
B
So
just
I'm
going
to
shoot
I'm
going
to
ask
some
questions
really
quick
to
the
crew.
So
if,
for
folks
that
have
read
this
issue,
is
there
anything
any
one
of
these
bullets
that
calls
out
to
you
and
just
I?
Remember
we
had
to
keep
focused
that's
another
priority
here,
because
our
crew
is
gonna
one
expand
quickly,
but
to
also
expand
in
scope.
So
we
just
want
to
make
sure
that
we're
actually
gonna
do
something
right.
E
B
C
Kind
of
a
meta
thing
is
automation
around
this
and
taking
the
automation
and
and
including
the
infrastructure
all
the
way
down
to.
Hopefully,
a
base
level
on
kubernetes
I
know
that
within
the
within
the
Cates
community,
we
were
all
really
heavily
on
the
cakes
and
for
working,
an
amazing
group
of
people,
but
all
of
that
infrared,
Lee
googly,
and
so
we
tend
to
by
modeling
a
Google
away
kind
of
let
the
world
know
that
that's,
maybe
the
only
way,
I
think
it
would
really
cool.
C
If
we
at
the
CN
CF
level,
we're
able
to
provide
things
like
crown,
CN
CF
that
I
own
and
integrations
for
all
of
the
CN
CF
hosted
projects,
including
the
way
that
we
automate
our
community
aspects,
but
maybe
put
a
little
of
effort
of
trying
to
I
mean
I.
Don't
know
this
is
just
thought,
that's
what
I'd
love
to
be
to
help
with
is
the
automation
currently
at
this
quarter.
C
One
of
my
goals
is
to
bring
up
proud,
CN
CF
that
I,
oh
because
the
CN
CF
Cates
informants
is
where
vendors
submit
their
test
results,
and
we
want
to
automate
that
and
say.
Yes,
you
did
pass
all
of
these
tests,
but
it's
not
appropriate
for
that
to
go
under
Kate's,
proud
on
Kate's.
That
I
am
so
it's
a
good
opportunity
to
start
doing
that
new
thing,
maybe
on
multiple
multi
vendors,
or
at
least
a
non
non
googley
vendor
done.
B
B
Okay,
I'm,
sorry
yeah,
so
let's
talk
offline
about
about
spinning
that
into
either
its
own
working
group
or
something
where
the
scope
is
a
little
bit
wider.
I
think
for
this
one
I
think
we
should
really
start
foundationally
I
feel
like
prowl
is
like
a
couple
steps
ahead
of
what
we
should
try
to
accomplish
at
first
here.
I,
don't
know
what
anybody
else's
thoughts
are,
but
I
definitely
think
it's
it's
relevant
important
and
should
probably
be
its
own
working
group.
What
are
some
other
donkeys
I.
E
We
may
decide
that
we
want
something
a
little
different
or
whatever
I
have
one
question:
if
you
don't
mind,
one
thing
that
I've
struggled
with
with
my
projects
is
like
where
I
manage
projects,
and
things
like
that
and
I
was
curious
Paris
if
you
had
an
idea
of
where
that
fits
in
in
various
SIG's
or
just
where
to
get
help
with
that.
Is
this
the
right
thing
for
that
kind
of
thing
like,
for
example,
help
with
using
github
project
boards
versus
other
stuff?
That's
out
there
I.
B
Definitely
think
that
could
be
a
part
of
this
project
management.
The
only
problem
that
I
think
with
the
only
thing
that
I
worry
about
it
is
we
we've
flipped,
we've
learned,
fluttered
I
mean
New.
York
can
also
tell
you
a
little
bit
about
this
I
feel
like
we
have
gotten
stuck
in
kubernetes
land
with
project
management,
because
no
one
wants
to
have
a
say.
You
have
to
use
one
tool
and
such
as
being
this
like
great
bike,
shed
about
how
to
do
project
management.
B
G
And
I
can
just
adhere
so
at
the
final,
and
we
would
just
decide
it,
and
within
the
cabinet
is
fold
it.
Everybody
can
do
their
project
management
as
they
prefer.
So
every
every
granular
groups
every
seek
and
every
some
context
owner
they
they
do
as
they
prefer
like.
As
we
do
with
the
see
contributor
experience.
E
E
There's
no
good
way
to
automatically
have
it
added
to
your
project
board
and
those
were
some
shaking
it
like
if
there's
box
or
automations
we're
making
that
can
do
pluggable
individual
things
like
that
that
just
work
with
random
default
tools,
it
doesn't
have
to
be
like
everyone
must
do
this,
but,
like
we've,
got
a
building
block
in
our
prow
toolkit
like
that
would
be
cool
but
I
know
that's
not
really
related.
We're
trying
to
talk
about.
So
that's
good,
I
think.
G
That
it
could
be
easier
now
from
the
automation
standpoint,
comparing
it
to
debt,
where
we
were
all
like
two
or
three
years
ago
because
of
the
github
actions
like
two
or
three
years
ago,
given
github
actions
didn't
exist
and
as
far
as
I
remember,
we
end
up.
Even
the
project
boards
didn't
exist
so
these
days
we
can,
we
can
automate
it
probably
more
efficiently.
G
I,
don't
want
to
say
easier,
but
somehow
easier
with
the
github
etchings
lists
will
we
have
all
their
all
the
available
tools,
all
the
possible
available
tools
directly
from
github,
and
we
don't
need
to
develop
something
now
old,
so
prom
is
good,
but
pro
is
good
and
the
scale
of
the
community's
project,
probably
is
the
currency.
Mcf,
sighs
I
mean
the
CNC
of
github
size.
We
don't
need
something
it's
from
the
powerful
annex
from
the
complicated
as
proudest
things
that
it
can
be
rather.
E
B
H
G
Cool
and
I
was
at
you
is
the
PM
stuff
that
we
had,
that
we
haven't
haven't,
haven't
had
enough
manpower,
so
it
just
was
like
enough
time
concealing.
So
if
you
can
allocate-
and
if
you
have
all
the
necessary
experience
with
dead,
it's
really
awesome
because
humans
and
terrible
will.
He
was
one
of
the
biggest
issues
again
in
the
past.
So
it's
it's
easier
to
define
and
develop
the
guidelines
and
to
find
a
program,
but
sometimes
it's
more
complicated
just
to
maintain
it.
You
know
the
same
way,
so
it
could
be
yeah.
G
I'd
like
to
like
to
remind
us
that
I'm
working
on
on
the
contributor
repo
resigning
restructure
and
after,
like
I'd
like
to
share
like
Darren
you
version
of
it
for
blue
tomorrow
tomorrow
on
Wednesday,
it's
basically
the
same
content,
but
a
bit
differently,
structured
easily,
more
easily
readable
after
that
I'd
like
us
to
also
to
review
it
and
provide
more
details
on
what
we're
missing
here.
So
the
current
company
is
available
here
then,
under
repo.
You
can
take
a
look
there
right
now.
G
B
G
D
B
C
B
So
they
can
ask
us
about
their
specific
contributor
growth
related
problem
issue
opportunity,
whatever
you
know
whatever
they
want
to
talk
about
so
I
want
to
know
from
this
crew
one.
Is
that
a
good
idea
to
should
we
create
a
separate
time?
The
reason
why
I
have
been
putting
on
you
know
putting
it
on
to
the
contributor
strategy
meetings
is
because
of
meeting
fatigue,
but
if
we
need
some
kind
of
separate
ima
like
I'm,
send
me
open
to
hearing
hearing
thoughts
on
that.
E
Heard
Karen
hit
right
off
of
how
much
we
need
that
meeting
for
ourselves,
because
we
did
pay
right
is
like
a
time
that
works
for
us
at
the
moment.
I
have
a
feeling
that
the
majority
of
our
time
that
we
need
together
is
going
to
be
in
our
sub
projects,
and
so
this
would
be
a
great
use
for
the
larger
sig
to
be
able
to
connect
with
the
community,
because,
like
that's
vitally
important
for
us
actually
helping
people
as
opposed
to
just
doing
ivory,
tower
work
all
right
so
I'm
all
for
it.
B
Okay
and
the
other
deal
is
we're
creating
a
maintainer
circle
as
well,
which
obviously
will
produce
its
own
meetings
and
things
like
that.
So
my
method,
all
my
methodology
to
the
madness
here
is
like
okay,
let's
at
least
get
people
heard
immediately,
hey
chase,
there's
like
any
project
out
there.
That's
like
really,
you
know
needing
something
immediately
and
then
they
can
tap
into
like
maintainer
circle
and
we
can
tap
into
maintain
our
circle
as
far
as
delivering
the
educational
content
that
we
need.
F
B
You're
misreading
this
maintainer
circle
will
be
much
more
in
depth
and
we're
talking
about
a
thousand
maintainer
x'.
They
they
want
to
do
mini
circles.
They
want
to
talk
about
burnout,
they
want
camaraderie,
so
I
think
the
maintainer
circle
will
be
focused
and
that's
where
we
can
also
deliver
webinars
and
our
presentations
and
things
like
that.
E
Circle,
it's
important
to
have
it
a
little
bit
separate
from
the
wider
community.
Its
maintainer
is
often
everything
you
do
is
transparent
to
the
point
where
it's
really
difficult
to
have
ranked
conversations
where
you
can
be
vulnerable
and
get
feedback
from
other
people
who
don't
need
something
from
you,
but
can
be
there
to
support
you
and
so
I
think
it's
important
to
carve
out
that
space
for
them
and
instead
of
trying
to
make
it
something
where
it's
open.
E
To
like
a
wider
group
of
people
where,
like
the
random
public,
for
example,
the
helm
users
may
show
up
to
where
the
hell
maintainer
they're,
trying
to
get
support
from
other
maintained,
errs
because
it'll
be
very
difficult
to
talk
about
things
that
are
important
to
them
when
the
people
who
need
their
help
and
are
asking
for
things
from
them,
are
gonna
be
listening
in.
If
that
makes
sense,
so
it
kind
of
does
need
to
be
a
really
separate
space.
In
my
opinion,.
B
B
All
right,
yeah
and
then
same
with
you
hippie
if
you've
got
like
any
automation,
talks
or
like
anything
or
even
how
about
this,
even
other
people
that
you've
seen
give
talks.
That's
also,
you
know
cool
too,
especially
if
we
could
probably
come
in
and
do
it
here.
They
don't
necessarily
need
to
be
a
part
of
our
crew.
A
lot
of
people
would
probably
think
that's
cool,
so
we
can
also
solicit
folks
all
right
and
then
we've
got.
B
B
Why,
here
from
that
Klein,
so
I'll
just
sacrifice
myself
and
put
myself
there,
but
if
anybody
else
wants
to
work
on
that
that
sort
of
falls
in
line
with
you
know
some
of
the
other
stuff
we're
doing
with
pull
like
ladder
and
templates
and
things
like
that.
But
it's
not
very
direct.
You
know.
The
goal
here
is
to
get
contributors
and
maintainer
to
be
more
direct
about
what
they
need.
B
Alright
and
then
this
sort
of
falls
in
this
one
right
here
on
the
net
this
next
one
here
role,
Hamlet
role,
handbook
templates,
building
roles
outside
of
the
usual
contributor
ladder-
this
is
kind
of,
like
maybe
I,
would
say,
p12
I
would
actually
say
it's
p1,
meaning
like.
Let's
do
the
contributor
ladder
work
for
work
first,
because
that's
sort
of
the
really
key
roles
there,
which
are
like
maintainer,
approvers
things
like
that.
Does
anybody
else
is
this
called
anybody
once
works.
E
B
So
in
kubernetes,
we've
got
I,
think
six
teams
now
in
each
one
of
those
teams,
is
different
than
the
contributor
ladder
ones.
The
release
team,
so
obviously
Karen
did
the
communications
manager
role
and
that
hat
that
produced
a
role
of
this
is
a
way
to
get
people
to
think
about
succession
and
also
all
morning
and
so
it'll
be
also
the
contributor
summit
events.
B
B
B
B
Sorry,
bag
Kate
that
takes
care
of
everything
we
have
in
the
queue
thus
far
I
listed.
What's
done,
but
what
is
done
for
this
issue?
But
does
anybody
else
have
anything
now
that
we've
talked
about
this
for
like
20
minutes?
Is
there
anything?
That's
blaring
lien
like
I
cannot
believe
it's
not
on
this
list
related
to
remember,
related
a
contributor
grows.
We've
got
a
governance,
a
project
going,
we've
got
some
other
thing
and
like
will
maybe
even
have
this
automation.
Some
project
work
you'd
be
going
anything
that
really
relates
to
that
I
have.
E
One
thing
that
I
know
is
gonna
come
up,
especially
for
people
in
the
kubernetes
group,
which
is
when
they're
looking
for
help
as
our
sig
Ram
Club
is
if
we
could
just
have
something
somewhere.
This
is
written
down
that
says
come
here
for
come
to
us
for
these
things
and
go
to
kubernetes
contributor
experience
for
these
things.
Cuz
always
we're
just
gonna
ask
you
Paris,
you
know
what
I
mean,
or
just
it's
just
gonna
unclear.
E
B
B
Alright,
so
in
this
issue
will
close
and
will
be
officially
launched
once
we
have
something
a
little
bit
more
descriptive
in
the
readme
we
already
have.
Actually
we
already
know
what
I'm
at
at
this
we
do
know
who
is
owning
what
now
what's?
The
first
thing
is
that
we
accomplish
and
send
a
note
to
the
TOC
in
the
maintainer
group
about
our
AMA,
which
is
a
little
bit
meta
note
about
us.
B
So
let's
talk
a
little
bit
about
this.
What's
is
the
first
thing
we
accomplished
look
like
and
the
definition
of
done,
four
things
this
does
not
and
should
necessarily
not
be
answered
now,
unless
you
know
folks
immediately
have
some
things
to
come
to
their
head,
but
once
we
disperse
and
start
digging
into
and
start
digging
into
some
of
this
stuff,
I
think
we're
gonna
see
what
done
looks
like,
maybe
in
like
the
next
week
to
two
weeks,
and
anybody
have
any
initial
thoughts
on
this.
E
E
B
B
B
E
B
B
B
B
B
B
Alright,
so
here's
the
two
links
in
the
issue
so
y'all
can
take
a
look
at
those.
My
my
idea
here
is:
we
can
collect
like
I,
said
to
let
let's
collect
a
bunch
of
stuff
that
already
exists
and
then
analyze
it.
It
does
anybody
know
other
other
good
resources
off
the
top
of
their
head
or
that
they
can
include
here.
E
B
Yeah,
that's
the
exact
thing
we
should
do
include
anything
that
you
think
looked
really
good.
Anything
that
was
impressive,
carrying
you
to
like,
if
you've
seen
stuff
when
you're
out
and
about
that's
really
impressive
na
VIU's
has
stuff.
That's
probably
not
cloud
native
I.
Think
the
40
pride
when
I
did
when
I
did
some
digging
I
think
the
40
projects
that
she
analyzed
but
I,
don't
think
so.
So
as
I'm
saying
it
might
not
necessarily
some
of
the
stuff
might
not
be
relevant
for
us.
Some
of
it
might
so.
E
E
B
It
doesn't
matter
I'm
open
with
whatever
you
want
to
use
totally
cool,
okay,
let
me
Google
box
and
yeah.
We
can
start
or
not,
and
then
I
think
what
are
what
are
definition
of
done
would
probably
look
like
here
is
maybe
a
nice.
You
know
template
repo
kind
of
like
this
I
mean
obviously
larger
than
this,
but
you
know
contributor
debt,
you
know
templates
and
then
in
here
have
some
folder.
B
E
F
B
B
B
C
B
D
F
Think
about
these
as
like,
they
will
just
record
like
no
matter
like
what
is
like.
You
know.
As
soon
as
you
come
in,
like
it
will
record,
which
is
nice
because
then
you
never
have
to
be
able
to
turn
on
the
recording,
but
then
it's
challenging
on
the
other
end,
if,
like
someone,
shares
their
screen
and
shares
chat
or
whatever,
then
you
got
to
go
back
in
and
edit
it
out.
Yeah.
B
E
H
B
Gotten
some
of
those
requests
me
and
we
still
do
the
hey.
Oh
my
gosh
I
for
not
that
I
shared
my
important
work,
information
and
like
at,
like
you,
know
three
minutes
and
33
seconds,
and
what
do
I
do?
Oh,
my
god,
all
right,
y'all,
it's
been
swell
I'll,
definitely
see
you
on
the
23rd
and
I'm
sure
we're
all
gonna
be
chatting
and
slack.
Oh
also.
Let's
try
really
really
really
hard
to
work
on
the
mailing
list:
okay,
I'm!
So
bad
at
it,
but
I
want
you.
B
B
Just
tojust
I
guess
talk
about
our
next
steps
on
there,
if,
especially,
if
they're,
not
in
issues
late,
because
we
I
think
we're
just
well
II-
and
it's
me
personally,
I've
built
this
culture
around
slack
and
like
talking
in
black
and
like
making
decisions
and
slack
and
like
I'm,
constantly
going
nope
I
need
to
take
this
elsewhere.
Like
so
yep
keep
me
honest,
that's
number
one
say
Paris.
This
needs
to
go
in
an
issue
or
the
mailing
list.
Sneeze
like
I'm,
not
gonna,
take
any
like
issue
with
that.
B
I'm
gonna
be
like
you're
right
and
same
with
anybody
on
the
call
like.
If
you
see
any
of
us
like
it's
talking
in
slack,
which
is
awesome
like
we
want
to
communicate
real-time
in
slack.
But
if
there's
like
something
that
like
we're,
making
a
decision
about
or
like
the
guidance
thereof,
let's
talk
about
that
I
are
doing
mailing.
E
B
Yeah
would
tell
me
about
this
checklist
cuz.
That's
honestly,
that's
a
good
part
about
like
contributor
strategy.
I,
think
that
we
should
give
to
to
SIG's
that
me
not
stakes,
two
projects
which
is
like.
How
are
you
communicating
your
decisions
and
like
what
are
you
talking
about
on
the
mailing
list?.