►
From YouTube: CNCF SIG Contributor Strategy 2020-12-03
Description
CNCF SIG Contributor Strategy 2020-12-03
A
B
B
C
E
E
C
E
C
C
So
let's
it's
two
minutes
and
I
have
a
feeling
this
is
like
this-
is
the
crowd
we're
gonna
get
cause.
I
know
carolyn's
on
vacation,
I
think
april's
not
feeling
well,
oh
nope,
that's
how
you
feel
is
going
hey
dawn,
hello.
So,
let's
just
kick
things
off
hold
up.
Let
me
lazy
link
the
agenda,
which
is
really
nothing
right
now.
So
please
put
agenda
topics
on
here.
We.
C
E
E
A
D
E
C
Welcome
everyone
now
that
we
have
a
good
mass
of
folks
here,
let's
see
karen's
in
the
house
dawn's
in
the
house-
oh
you're,
good!
I
don't
know
if
I
I,
this
is
my
first
meeting
in
a
while.
I
don't
know
if
you've
been
here
before
if
you'd
like
to
introduce
yourself
in
a
second
when
we
get
kicked
things
started.
That
would
be
awesome,
but
I
did
include
the
agenda
in
chat
if
you
just
joined
and
don't
have
that,
let
me
link
again.
C
And
just
put
your
pop
your
name
on
that
doc.
If
you
have
anything
that
you
would
like
to
talk
about
today,
feel
free
to
include
otherwise,
this
will
most
likely
be
a
shorter
meeting
than
are
usual,
but
anyway,
let's
go
so.
Who
put
maintainer
circle?
Was
that
the
yeah
I
was
gonna
say
was
that
steven,
the
anonymous
unicorn
all.
D
C
Everybody
for
some
reason
in
the
doc
is
anonymous.
Now
I
was
like
all
right.
We've
got
a
lot
of
animals
here
today,
all
right
so
before
we
get
started,
though,
don't
forget
be
kind.
We
do
have
a
small
crew.
It's
only
six
of
us
today
so
feel
free
to
interject.
That's
fine
and,
like
I
said,
if
you
have
any
other
topics
to
share,
feel
free
to
put
them
on
the
agenda.
C
C
C
We
have
a
speaker
lined
up,
I
kind
of
want
to
take
the
recording
off
honestly,
because
I
kind
of
want
to
be
a
little
surprise
and
delight.
I
don't
know
I'll
tell
you
all
in
dms
later
how
about
that,
because
one
of
the
maintainers,
some
one
of
the
maintainers
was
gonna,
give
a
personal
story
and
it's
gonna
be
a
little
fireside
chat
and
it
will
be
very
lovely
and
then
we're
also
going
to
have
a-
and
I
can
tell
you
this.
This
is
fine.
C
It's
either
going
to
be
a
researcher
from
the
university
of
san,
diego
or
jen,
who
gave
the
burnout
talk
at
kubecon
just
recently,
I
don't
know
if
y'all
saw
jen's
talk,
but
either
jen
or
a
woman
named
heather.
I
believe
from
university
of
san
diego
and
she
does
false
research
for
burnout,
as
well
as
other
kinds
of
occupational
things
like
occupational
mental
health
situations.
C
So
she
actually
has
a
lot
of
data.
She's
done
a
lot
of
data
with
wikipedia,
so
that's
we're
pretty
much
set
up
to
run
on
december
the
summer
17th.
I
just
need
to
get
one
of
those
two
folks
to
confirm,
and
then
the
other
one
that
confirms
later
is
actually
going
to
get
set
up
for
a
future
meetup.
So
good
news
as
soon
as
one
of
them
confirms
I'm
going
to
get
the
registration
information
out
to
the
maintainers
list,
so
we're
talking
about
the
maintainers
at
private
cncf
lists.
C
C
There
are
still
like
antitrust
laws
that
we
have
to
abide
by,
for
instance,
so
like
having
private
meetings
and
having
private
slack
channels
and
stuff
like
that
is
you
know
not
necessarily
the
greatest
thing.
However,
if
we
still
do
a
public
agenda
and
things
like
that,
then
we
can
still
have
a
semi-closed
group,
for
you
know
personal
dialogue
and
things
like
that,
because
that's
really
what
the
intention
is
here
is
like
the
more
personal
connections
that
we
can
make
as
maintainers.
C
C
E
C
E
B
B
B
C
I
mean
my
thing:
is
I
just
don't
necessarily
want
just
like
end
users
showing
up
to
hang
out
with
with
maintainers
or
and
like
you
know
what
I
mean
like
that
kind
of
thing,
because
it
really
is
about
the
bonds
of
these
people
and
also
them
telling
like
more
personal
leadership
type
stories
so
yeah
anyway,
all
right.
Let's.
C
Okay,
cool
all
right:
let's
go,
let's
roll,
so
I'm
I'm!
I'm
like
looking
at
my
I'm
steady
looking
at
my
email
right
now,
because
I'm
expecting
to
confirm
back
from
one
of
these
two
folks,
so
yeah
we're
definitely
gonna
have
this
out.
I
would
love
for
you
all
to
look
and
approve
of
the
copy
before
that
goes
out
so
I'll
either
copy
and
paste
that
into
an
issue
or
in
the
slack.
So
if
y'all
could
take
a
peek,
give
me
an
lg
tm
that
would
be
lovely
and
that's
pretty
much
it
for
maintainer
circle.
C
E
Yeah,
so
the
shush
slack
so
the
so
one
question
about
maintaining
recycle
is
like,
should
we
be
doing
recruiting
as
well
starting
to
see
some
more
of
the
sessions
with
presenters
and
cadence-wise
yeah?
I
think
you
mentioned
monthly
on
the
pr,
but
do
we
want
to
do
the
monthly
or
are
we
playing
on
doing
the
alternating
week
thing
I'm
fine
with
either
personally
so.
C
C
So
that's
why
I
was
just
thinking
of
the
monthly
unless,
unless,
like
you
know,
we
decide
that,
like
it's
a
very
popular
thing
and
we
need,
like
you
know
like
the
the
circle
grows
or
whatever,
then
we
can
change
it,
but
so
I'm
just
thinking
monthly
to
start.
However,
it
would
be
every
other
week
for
us,
with
the
exception
of
oh
it's
an
odd
week,
so
we
still
have
our
meta
meeting.
C
E
C
A
C
C
A
I'll
just
talk
to
it
really
quickly,
so,
as
you
can
see,
we
broke
it
down
into
well.
We
broke
it
down
into
like
kind
of
the
progression
of
how
you
would
move
operates
like
community
member
to
contributor
to
approver
maintainer
and
under
maintainer.
We
talked
about
this
last
week
about
nesting
some
of
the
more
specific
roles.
A
So
I
think
I
was
trying
to
make
this
in
a
way
where,
like
I
just
added
as
many
examples
as
possible
or
descriptions
and
ideas
like
someone
would
come
in
and
like
pare
it
down
to
whatever
fits
their
role.
So
if
anyone
has
more
examples
or
descriptions,
please
drop
them
in.
This
is
for
my
limited
knowledge
and
then
the
last
part
is
around
like
inactivity
and
like
people
stepping
down
or
removing
them
from
an
existing
role.
A
A
C
A
C
I
know
I
think
it's
I
think
it's
good.
I
think
the
only
thing
I'm
gonna
I
can
add
to
it
in
a
draft
state
is
just
like
what
you're
pretty
much
links
to
examples
at
the
bottom.
We
only
have
to
like
embed
them
in
yet
just
pretty
much
like
a
resource
list
or
or
a
link
to
the
resource
guide,
the
resource
list
that
we
have
or
something
like
that,
but
all
right,
y'all
karen
needs
a
review
so.
E
E
A
C
C
F
Yeah
hi
everyone,
my
name
is
jurgen,
I'm
a
maintainer
of
the
cncf
sandbox
project
called
captain.
I
was
the
head
here.
It's
a
captain
and
yeah
I'm
really
interested
in
like
how
we
as
a
project,
should
grow
and
our
community
and
how
I
can
like
get
help
from
the
whole
cncf
ecosystem
and
taking
a
look
at
this
document.
I
was
not.
F
Is
this
document
it's
the
purpose
of
the
document
for
other
projects
to
to
take
it
and
like
have
it
as
a
contributor's
guide
to
the
letter,
so
it
will
be
like
a
resource
for
us
already.
Awesome,
that's
cool!
I
thought.
Maybe
it's
only
for
like
the
the
big
incubating
projects,
but
it's
okay.
So
I'm
in
the
right
meeting,
yeah.
F
E
C
It
no
yeah
we're
here
for
any
of
those
kinds
of
questions
that
you
have.
So
if
you,
if
you
want,
save
those
for
one
second,
let
us
get
through
this
meta
planning
stuff,
and
then
we
can
chat
your
ear
off
all
day
about,
like
any
questions
that
you
have
about
your
project
specifically
and
then
also
how
you
can
get
more
involved
with
us
and
like
and
stuff
like
that,
cool
cool
awesome,
all
right.
So
last
any
other
questions
for
karen.
As
far
as
contributor
ladder
is
concerned,.
E
C
Like
I
think,
it's
a
are
all
the
to
do's
that
were
listed
on
the
dock
as
like
initial
to
do's
done.
Just
like
what
you're
like
what
you
just
pretty
much
asked
like
where
the
to-do's
and
then
once
we
give
it
a
final
review,
and
this
is
in
my
opinion,
like
we
can
change
any
of
this
and
then
it
and
then
we
can
do
the
move
and
do
the
final
review
once
that.
Once
everything
like
is
good
in
the
pr.
G
When
I
was
gonna
say
right,
I
actually
see
those
as
two
different
processes
for
the
advisory
docs.
We
really
need
to
get
someone
from
the
toc
to
approve
them
to
sign
off
on
them
the
because
in
a
lot
of
cases,
the
advisory
docs
are
going
to
be
saying.
Like
hey,
you
have
this
requirement
as
an
incubating
project.
This
is
what
that
means,
and
so
it
needs
to
be
endorsed
by
somebody
from
the
toc
as
as
part
of
the
the
making
it
ga
process
do.
C
B
C
Let's
do
that
for
the
templates,
then
so,
but
I
mean,
as
far
as
the
governance
stuff,
that
you're
giving
his
advice
is
this:
are
you
applying
that
same
kind
of
principle
that
we
were
just
talking
about
with
karen,
where
it's
like
are
the
to
do's
done
that
you
initially
set
forth
and
then
has
they
give
given
a
final
review,
or
do
you
do
anything
else
in
between
that?
For
for
the
graduation
step?
Well,.
G
G
G
G
But
no,
but
I
mean
I
don't
I
don't
you
know,
I
know
how
busy
he
is.
I
think,
if
we
hand
him
something-
and
we
say
this
is
done-
he's
probably
not
going
to
say
and
unless
we
say
something
in
there,
there's
like
whoa.
No,
no,
you
guys
are
way
off
base
there.
Okay,
like,
if
he's
going
to
have
an
objection
to
it,
it's
going
to
be
a
major
objection.
C
E
C
E
C
All
right:
well
at
least
we
have
some
kind
of
framework
I
mean
and
then
and
then
of
course
stephen
can
do
his
like
elaborate,
you
know
get
ups,
you
know
once
we
once
we've
launched
and
graduated
at
least
one
you
can
do
some
get
outs
for
our
graduation
process,
all
right,
so
I'm
taking
it.
You
have
the
next
two
for
the
coupon
stuff
or
is
it
did
somebody
else
about
that.
E
G
C
G
E
G
E
G
G
Right
we
had
the
zoom
thing
and
I
said,
look
just
send
a
message
out
to
everybody
we're
going
to
have
I
first
I
asked
him
to
cut
straight
to
q,
a
I
said:
there's
going
to
be
a
mostly
q
a
session
anyway,
please
just
cut
straight
to
q.
A
now
and
he's
like
wait.
I'm
fixing
the
video
I'm
like.
No,
no,
no,
don't
fix
the
video
cut
straight
yeah
he's
like
wait.
I'm
fixing
the
video.
B
G
B
Literally
had
to
pull
in
his
manager
and
they
couldn't
figure
out
how
to
just
let
us
share
one
of
our
screens,
because
we
all
have
the
presentations
and
the
the
presentation
and
the
stuff
open
we're
like
we'll.
Just
do
it
again,
we'll
do
it
live
whatever.
Just
just
put
us
put
us
alive
and-
and
I'm
I'm
I
don't
know,
I
was
getting
a
little
irritated
and
I'm
like.
Can
you
just
make
us
live,
and
I
just
kept
saying
it
over
and
over
again
and
yeah.
It
was
also.
B
G
And
not
only
that,
like
when
I
dialed
in
when
I
dialed
in,
I
was
like,
I
think,
there's
a
problem.
I
think
there's
a
problem
with
my
it
was,
I
don't
remember,
a
sound
or
video,
but
like
I
was
seeing
a
problem
when
I
dialed
in,
and
so
I
reported
this
to
the
tech
and
he
didn't
respond
at
all
the
love
it.
So
it
was
please.
G
C
C
C
B
C
Just
being
dated,
I
think
we
should
just
do
a
meta
session
of
what
kind
of
services
people
can
get
from
us
just
kind
of
like
what
like,
like.
You
know,
jurgen's
here
like
he's
like
am
I
in
the
right?
It's
like
you
are
absolutely
in
the
right
meeting.
We
are
here
to
help,
so
it's
just
some
kind
of
meta
session
of
like
hey,
here's
who
we
are
blah
blah
blah,
but
I
really
want
an
all-day
contributor
summit
linux
foundation
if
you're
listening.
C
F
C
F
F
F
F
It
install
it,
but
we
are
having
a
little
bit
of
hard
time
to
also
convince
people
that
it's
an
open
source
project
and
they
can
join
and
we
do
have
contributing
guidelines.
We
do
have
the
captain
core,
which
is
our
project,
and
it
might
have
a
little
bit
of
a
hard
learning
curve
because
it's
yeah,
it
has
been
the
the
core
development
team
has
been
originated
from
one
company.
So
it's
a
lot
of
knowledge
that
is
in
their
heads.
F
But
what
we
built
is
the
captain
sandbox,
which
is
a
more
lightweight
approach
to
also
join
the
project
and
just
build
integrations
to
the
project.
So
we
are
trying
a
lot
of
things
or
we
think
that
we
are
trying,
but
we
are
not
seeing
yet
that
that
we
really
that
people
are
picking
it
up.
So
we
also
joined
the
cncf.
B
F
Was
really
great,
we
had
a
great
job,
also
presenting
today
in
our
community
meetings,
so
we're
also
doing
community
meetings
trying
to
to
be
open
and
include
the
community
also
show
what's
currently
going
on
in
the
project
but
yeah.
I
thought,
since
I
found
this
sick,
I
thought
I
I
have
to
join
and
I
have
to
find
out
what
you're
discussing
here
and
maybe
how
you
could
help
projects
like
ours.
C
F
No,
I
I
think
it's
that
we're
trying
to
already
solving
a
a
problem
in
pitching
what
the
idea
of
the
of
our
project
is.
Maybe
they
think
too
much
it's
a
product
and
they
just
like
they
ask
us
to
provide
or
to.
Of
course,
we
we
are
here
also
fix
bucks,
and
we
are
happy
for
every
conversation
that
we're
having.
But
since
it's
originating.
F
B
G
F
F
G
The
way
that
you
get
long-term
contributors
is
by
having
a
bunch
of
short-term
contributors,
it's
not
targeting
a
different
group
of
people.
If
you
follow
me
that
is,
somebody
comes
intending
to
fix
one
thing
or
to
do
one
thing
right
and
then
they
decide
they
like
it
there
and
they
stay
the
either
because
they
had
a
good
experience
or
because
they
start
using
kept
in
more
in
their
environment
and
therefore
more
things
come
up.
G
And
more,
what
I
was
thinking
about
with
the
good
first
issue
in
the
advertising
is
more
that
you're
trying
to
keep
up
a
stream
saying
hey.
This
is
an
open
source
project.
We
are
actively
looking
for
contributions
of
all
kinds.
Like
I
said
it's
not
necessarily
you
get
somebody
contributing
to
that
specific
issue.
It's
that
you
create
a
view
of
people
that
this
is
their
project
and
not
a
project
being
maintained
by
somebody
else
for
their
benefit.
G
F
So
we
we
try
to
also
open
up
the
discussion,
so
we
do
a
lot
of
the
discussions
directly
on
the
issues
on
github,
but
we
are
more
or
less
trying
to
work
on
from
one
weekly
developer
meeting
to
the
other.
So
you
could
call
it
a
weekly
sprint
and
I'm
not
sure-
and
that's
just
an
like
very
open
question
here.
B
F
G
C
G
Well,
but
meetings
do
reach
a
certain
group
of
developers.
It's
just
there's
another
group
of
developers.
They
don't
reach
it's
the
same
thing
with
the
one
week.
Sprint
thing
right:
the
only
sprint
thing
is
great
for
somebody
coming
in
and
saying
hey.
I
have
some
free
time
this
week
in
order
to
work
on
contributing
to
captain
or
whatever.
What
can
I
do
this
week
right?
So
it's
good
from
for
that
group
of
people
for
the
group
of
people
who
are
like
hey,
I
use
captain.
I
have
this
one
thing.
That's
really
annoying
me.
G
It's
part
of
my
job,
but
not
the
main
part
of
my
job.
Those
people
are
going
to
be
in
a
much
longer
timeline
and
as
long
as
there's,
nothing
blocking
them
from
eventually
getting
that
thing
in
it's
not
really
a
problem.
There's
this
other
one-week
sprint
thing
going
on.
So
I
guess
the
question
is:
if
somebody's
operating
on
a
longer
timeline,
if
somebody's
operating
on
a
timeline
where
they
can't
really
participate
in
the
one-week
sprints,
is
there
still
a
route
for
them
to
contribute.
F
F
To
an
issue
like
we
wait
sometimes
like
two
weeks,
but
we
don't
see
any
contribution
and
we
don't
know
if
they
also
joined
our
slack
or
what
is
the
twitter
handle.
So
then
we
sometimes
just
reassign
it.
If
someone
else
is
stepping
in
and
wants
to,
take
it,
but
yeah
in
issues
that
are
like
are
that
are
would
be
blocking,
if
not,
if
not
done
in
a
timely
manner
that
we
should
label
with.
B
G
And
realistically
those
sorts
of
issues
are
going
to
be
up
to
the
core
maintainers,
whoever
they
are
right,
because
in
order
to
respond
to
short
deadlines,
working
on
captain
has
to
be
part
of
your
job
assignment
the
now.
Hopefully,
eventually,
those
core
developers
will
work
for
a
bunch
of
different
companies,
but
it'll
take
a
while
to
get
there
the
yeah,
and
so
for
that
reason
it
would
be
a
good
idea
to
tag
those
right.
It'd
be
a
good
idea.
G
F
And
what
would
be
your
advice
on
like
weekly
developer
meetings?
They
should
be
so
you
usually
we
discuss
and
present
also
contributions
to
the
project,
not
something
if
you
fix
a
typo,
it's.
If
you
really
want
to
present
you
can,
but
we
call
it
noteworthy
issues
in
prs
where
we
that
maybe
needs
discussion
or
was
really
a
major
contribution.
So
we
show
it
to
the
to
the
whole
group.
So
we
had
one
earlier
today
and
we
used
this
time
to
show
our
computer
contributions
and
also
talk
about
the
next
week.
F
So
maybe
we
should
remove
this
part
where
we
actually
assign
issues
for
the
next
week,
because
it's
publicly
available
on
github,
everyone
can
just
take
whatever
he
wants
to
contribute
to
and
assign
it
to
himself
and
then
present
next
time.
So
we
should
maybe
just
use
it
for
discussion
and
what
needs
discussion
and
not
so
much
on
task
distribution.
C
C
If
you
will,
where
we're
like
trying
to
like
plan
stuff
for
you
all
and
get
advice
done
on
tuesdays,
there
is
a
contributor
growth
subgroup
and
then
a
governance
subgroup,
and
if
you
have
other
questions
and
like
want
to
get
into
like
nitty
gritty,
detail,
questions
or
like
stuff
like
that,
feel
free
to
come
and
they
are
10
30
in
the
morning,
so
actually
might
even
be
a
better
time
for
you,
I'm
not
sure
just
depends
yeah.
No
thanks
for
coming
and
being
interested
and
like
growing
your
project.
G
C
That
is
so
key,
like
the
more
liberal.
Your
policies
are
with
contribution,
the
easier
it
is
for
people
to
get
responses
and
quickly
merged
the
more
users
like
the
more
users
are
going
to
see
that
and
go
wow.
I
can
actually
like
submit
this
patch
wow.
It
won't
like
sit
in
the
ether
so
yeah
that
that's
the
like
that,
I
think
the
key,
like
the
key
hook
to
users
to
getting
more
people
interested
and,
like
the
more
more
of
the
we
really
care
about
this
vibe.
B
Didn't
say
much:
I
miss
you
yeah,
I'm
good!
I
was,
I
admit,
to
multitasking
a
little
bit
because
I
have
a
million
things
to
do
and
vmware
gave
us
like
a
ton
of
extra
holiday
days,
and
so
I
I'm
off
on
monday
and
then
after
the
11th,
I'm
just
off
the
rest
of
the
year.
But
what
that
means
is
that
I
have
a
million
things
that
I
need
to
wrap
up
before.
I
can
just
take
off
and
check
out
out
on
the
11
after
the
11th.
So
so
now,
I'm
just
panicked
of
all
the
stuff.
G
A
B
C
B
G
G
C
B
F
C
We're
not
that
that
big,
yet,
but
maybe
soon,
but
anyway,
I
wanted
to
say
we
also
have
a
github
repo,
if
you
haven't
checked
that
out
yet,
and
that
has
like
what
we're
doing
what
we're
trying
to
do
so,
like
you
can
see
and
tell
all
of
your
maintainers
friends
said,
kept
captain
that
hey
we're
here
for
you.
This
is
what
they
do
and
then
also
join
the
maintainers
circle
as
well.
C
C
So
I
mean
I
guess
it's
like
bring
your
own
brandy
at
that
point,
but
you
bring
your
own
putt-putt
too.
I
guess
so,
but
anyway
yeah
just
just
some
kind
of
thing
for
you
as
maintainers
to
get
to
know
other
maintainers
who
are
in
the
same
shoes
you
are
or
might
be
in
the
same
shoes
you
are
or
in
some
kind
of
other
growth
path.
So
if
you
need
anything
from
us
at
all,
like
I
said
reach
out.
C
It's
also
a
zoom,
meaning
it's
also
a
zoom
meeting
and
it
will
not
be
recorded.
So
that's
it's
definitely
one
of
those.
You
should
be
there
for
it
type
of
things
just
because
it's
not
going
to
be
recorded
because
one
we're
going
to
go
into
breakout
rooms,
but
two
because
in
case
you
say
something
personal
or
fee.
You
know
feel
like
you're,
comfortable
enough
to
say
something
personal
that
you
can
do
that.