►
From YouTube: CNCF SIG Contributor Strategy 2021-03-30
Description
CNCF SIG Contributor Strategy 2021-03-30
B
B
A
C
B
C
But
you
still
can't
see
the
videos
until
you
close
the
meeting
and
then
you
have
to
wait
for
them
to
do
their
thing,
but
that
would
have
worked
a
lot
better
for
us
than
the
cloud
recording.
I
think.
Maybe
you
know
it
basically
made
local
work
the
same
way
as
cloud
did,
but
there
was
no
way
for
us
to
like
see
the
video
and
know
how
well
it
went
until
you
killed
the
meeting.
C
B
C
B
Or
at
least
or
if
anything
needs
to
be
fixed,
it's
just
a
matter
of
trimming
a
few
seconds
yeah
so
which
I
can
do
in
post.
But
but
it's
it's
starting.
It's
giving
you
the
picture
of
what
doing
a
presentation
is
like
these
days
because,
like
you
know,
we
spent
three
hours
recording
and
out
of
that,
only
45
minutes
was
spent.
Actually
recording
and
it'll
probably
be
four
hours
by
the
time.
I'm
done
editing
it
so
it'll
be
four
hours
to
record
a
session,
most
of
which
is
spent
doing
av
yeah.
C
C
C
B
B
C
C
C
D
B
B
C
A
B
Yeah
because
it's
a
template
yeah,
so
that's
one
of
the
things
that's
going
to
change
that
actually
mentioned
here,
which
is
the
contributor
ladder
file.
That's
in
the
main
repo
is
going
to
disappear.
If
we
merge
the
one
into
templates,
or
rather
there
should
be
a
file
in
the
main
repo,
but
the
file
in
the
main
repo
should
explain
the
concept
of
the
contributor
ladder,
rather
than
being
an
example
of
one
yeah,
the
so.
B
Sorry
go
for
it,
oh
okay,
so
this
is
the.
This
is
the
new
version,
the
template,
but
I've
made
actually
some
substantial
changes
since
it
went
on
to
hackmd
and
we've
all
been
a
little
asynchronous
here.
So
I
wanted
to
make
sure
really
during
this
meeting,
I
wanted
to
be
sure
that,
regardless
of
whatever
knits
we
have
here
that
we
agree
with
the
direction
that
I've
taken
it
in
does
it
happen.
B
C
B
C
B
B
Ladder
the
where
I've
made
some
substantial
changes.
So
one
of
the
last
thing
we
talked
about
in
a
meeting
that
I
was
in
was
having
the
separate
sort
of
maintainer
expansion
pack
file
and
we
started
working
on
that
and
karen
put
up
a
hackmd
file
for
that,
and
then
we
totally
bogged
down
because
there's
a
little
bit
of
stuff
there.
B
C
Okay,
semi-related
note:
we've
added
a
branch
to
the
templates,
repository
called
drafts
and
that's
going
to
be
kind
of
like
a
staging
place
where
we
can
merge
in
things
like
this
before
we're
totally
ready
to
to
put
it
in
front
of
the
toc
and
be
like
this
is
the
template
for
x,
y
or
z,
so
as
you're
looking
for
content
in
that
repo?
Just
be
aware
that
there's
two
branches
there's
main
and
that's
you
know
the
finalized
version
of
any
template
and
then
there's
drafts
where
you'll
find
things
like
this.
The
contributor
ladder.
B
C
B
Not
quite
ready
to
merge
so
one
of
the
things
also
about
that
is
I
added
in
the
additional
maintainer
roles,
and
I
thought:
okay
well,
we're
not
gonna,
be
able
to
provide
a
template,
for
these
at
least
provide
an
example
for
them,
and
so
I
have,
if
you
notice
an
empty
example
link
for
each
of
them
yeah.
So
that
would
be
something
we
should
at
least
take
a
stab
at
annoyingly.
I
have
a
good
example
for
subproject
maintainer,
but
it's
for
a
project
that
also
hasn't
merged
its
contributor
ladder.
Yet.
B
B
E
E
I
guess
so
my
concern.
There
is
more
that
if
it's
not
immediate
on
like
unless
they
click
through
the
comments,
then
they
might
not
think
about
it
at
all,
as
in
like
we
wouldn't
be
encouraging
them
to
think
about
the
different
roles,
so
I
guess
my
only
thing
would
be
like,
so
we
want
to
make
it
more
apparent.
E
B
E
B
C
I
want
to
make
sure
that
I
mean
we
put
a
ton
of
work
into
identifying
different
ways
to
be
a
maintainer
and
have
non-cone
contributions.
I
want
to
make
sure
that
we
don't
we
don't
lose
that
it's
going
to
go
into
the
website,
then
so
nothing
will
be
hidden
behind
to-do's
or
markdown
comments
at
that
point,
it'll
it'll
be
visible
for
everyone
on
the.
C
E
E
C
E
E
C
C
A
A
A
C
C
A
On
my
end,
I
kind
of
yeah
I
mean
like
once
that
is
kind
of
all
submitted
and
then
it's
kind
of
the
question.
How
do
we
get
people
to
review
and
then
because
I
think,
that's
kind
of
the
issue
right?
There
are
a
lot
of
people
with
a
lot
of
things
and
a
lot
of
things
to
review
so
yeah
yeah,
but
we'll
see
when
it's
once
it's
there
right.
A
I
know
carol
and
you
see
see
these,
but
because
I
know
that
there
is
a
process
once
they're
all
there
before
it
gets
like
shown
to
someone
from
the
talk,
there's
like
a
whole
process.
So
but
I
guess
we'll
see
it
once
they're
live
and
I
know
it's
a
lot
to
ask
people
to
review
everything,
because
I'm
not
the
only
one
asking
for
things
to
reveal.
There's
karen's,
josh,
there's,
paris,
everyone
is
asking
review.
C
D
D
A
A
Okay!
So
I
have
to
remember
now
too,
it's
been
a
while
yeah.
Basically
here
we're
kind
of
trying
to
see
like
how
do
you
successfully
kind
of
manage
people
through
the
flow
and
make
sure
they're
not
demotivated
through
the
process?
And
so
here.
Basically,
you
talk
about
like
how
the
process
is
how
the
the
flow
is,
and
I
think
we
got
rid
of
the
things
here,
but
it's
like
also
like
kind
of
make
notes
on
your
crm
tool
so
that
you
can.
A
You
know,
like
you,
remember
things
and
valuable
information
associated
with
one
person,
and
I
hear
when
someone
submitted
like
right.
That's
like
a
really
good
point
or
you
have
to
make
sure
that
the
person
doesn't
get
engaged
so
try
to
suggest
something,
because
that
could
be
like
a
a
moment
where
you
lose
the
person
again.
So
it's
kind
of
like
okay,
when
someone
submits
something
try
to
see
if
they're
interested
in
doing
more
one
of
things
that
came
really
crystallized.
A
Was
the
expectations
part
like
how
that
you
have
to
be
like
super
transparent
regarding
a
response
time,
what
you
need
right,
like
the
better,
the
more
time
you
put
into
explaining
exactly
what
you
need,
which
may
sometimes
feel
like
you,
don't
have
the
time
to
do
it,
but
if
you
do
it,
people
will
create
much
better
prs
right
because
they
know
exactly.
They
cannot
read
your
mind
of
course.
A
Then
it's
a
little
bit
about
tools
like
what
is
that
that
that
you
have
to
like
really
give
people
what
they
need,
and
so
you
have
like
docs
pr
checks
templates
lots
of
different
things.
You
could
do
videos
bots
yeah,
but,
like
also,
you
have
to
be
sure
you're
able
to
maintain
that
so
be
be
conscious
of
what
you
like
what
you
can
maintain
and
but
give
them
as
well
like
enough
tools.
So
people
know
exactly
what
to
do.
Then.
The
automation
part
automate
as
much
as
possible.
D
So
then,
when
I
say
well,
that's
what
automation
can
help
you
out
with
and
like
it
opens
up
a
much
more
positive
outlook
like
and
especially
when
I
demo
things
like
the
that,
like
the
kubernetes
bots
does
with
like
displaying
documentation
and
stuff
like
that.
So
I
wonder
if,
like
we
should
put
just
a
note
at
the
top
that
a
lot
of
this
a
lot
of
this,
we
really
believe,
should
be
automated.
D
A
A
D
D
A
A
You
know
like
so
it's
like,
oh,
if
you
want
to
recruit
people
like
mention
it
and
then
link
like
so
I
think
if,
if
we
have
stuff
already,
we
should
link
to
that
and
not,
but
so
this
is
basically
kind
of
like
more
of
an
overview
and
ideally
it
would
link
to
which
is
more
high
level
and
then
link
to
all
the
things
that
are
more
detailed
and
then,
if
you
wanna,
you
know,
go
more
into
details.
Yeah
read
that.
C
C
D
D
Like,
for
instance,
a
man
like,
I
don't
see
not
necessarily
like
where
you
should
put
this,
I
think
it's
a
good
start.
I
just
I
worry
that
we
have
a
lot
of
duplicate
content
that
we're
gonna,
that
we're
gonna
be
calling
people
to
and
that
we're
also
giving
guidance
in
areas
where
is
more,
adding
more
humans
when
we
don't
necessarily
want
to
add
more
humans
in
a
lot
of
these
situations,.
C
C
C
B
C
B
C
D
I
guess
all
text
which
I
know,
and
I
know
it's
still
in
a
pr
state
just
from
like
a
I'm
trying
to
put
myself
into
a
already
busy
maintainers
mind
of
how
do
I
make
this
better
and
then
it's
just
text
with
not
much
like
links
to
act
like
forkable
things
and
stuff
like
that,
and
not
enough
emphasis
on
automation
and
like
automated
things
that
people
have
created
that
help
this,
like.
I
know,
porter
has
and
stuff
like
that.
A
Well,
I
think
this
section
is
not
really
saying
how
you
should
do
this
right.
It's
more
like
these
are
the
things
that
you
need
to
do
right.
You
have.
You
should
be
clear
about
response
time.
You
should
have
all
the
information
like
clear
information
about
how
the
flow
and
what
the
action
items
are.
D
A
Well,
I
think
a
way
of
seeing
this
as
well
is
like
this
is,
of
course,
very
high
level
right,
and
we
have
some
assets
already
where
we
can
link
through,
but
like
once
we're
done
with
that
and
the
letter
and
so
on,
like
that
would
be
like
okay
like
if
this
is
kind
of
the
things
that
you
need
like.
That
would
be
like
a
good
way
to
identify
the
next.
A
You
don't
want
to
be
too
detailed
in
this
thing,
but,
like
you
want
to
link
to
things
when
people
want
to
have
more
information
about
about
these
specific
areas
for
sure,
so
maybe
it's
a
good
idea
like
it's
a
good
source
of,
as
you
said,
like
the
coding
documentation
quality.
Like
that's
a
if
you
say
like.
Oh
that's,
super
important
point
that
could
be
like
the
next.
You
know
project.
C
I
think
one
thing
paris
pointed
out
that
really
resonated
with
me
is
that
we
need
to
be
careful
that
our
job
here
isn't
to
output
more
yeah
text,
totally
to
give
things
that
a
maintainer
can
look
at
in
a
very
short
amount
of
time.
When
you
do
one
actionable
thing,
because
this
is
like
my
bread
and
butter.
C
C
D
Yeah,
I
think
this
is
this
stock
is
like
the
bible
for
anybody
that
does
community
management
for
yes,
this
is
this
is
the
like.
This
is
the
bible
for
community
man.
This
is
the
bible
for
our
group,
like
it's
like
the
metal.
It's
like
the
meta
bible
for
our
group.
Right
now,
open
source
doesn't
have
community
right.
B
But
what
what
you're
describing
is
actually
a
classic
one
of
the
classic
problems
in
writing,
documentation
which
is
there's
three
basic
types
of
documentation:
there's
narrative
documentation,
there's
reference
documentation
and
there's
solutions.
Documentation
right,
narrative,
documentation,
says
explain
this
whole
concept
to
me.
What
we
have
here
is
narrative
documentation
right.
B
If
you
need
to
understand
the
big
picture,
you
need
the
narrative
documentation
and
then
reference
documentation
is
I
want
x
right?
I
want
to
understand
the
sub
projects.
You
know
explain
the
the
sub
project's
governance
structure
right,
that's
reference
documentation.
I
want
to
understand
one
thing
that
I've
already
defined
and
then
their
solutions,
documentation
which
is
like
that
only
turned
90
degrees
which
says
hey.
I
have
this
problem.
B
Yeah,
and
even
if
you
have
the
staff
to
produce
all
three
keeping
them
in
sync
is
very,
very
difficult
the
so
you
know
for
for
what
it's
worth
I
mean.
So
if
we
approach
this
and
we
say
hey
look,
this
is
narrative
documentation
and
we
want
to
work
on
ways
to
enable
it
to
make
it
useful
as
other
kinds
of
documentation.
We
kind
of
already
have
the
reference
documentation
in
terms
of
the
templates.
We
just
need
to
cross-link
the
two
yeah
right
so
then,
and
the
solutions
documentation
is
really
what's
missing.
D
B
The
and
that
we're
gonna
have
to
create
from
scratch.
Additionally,
after
we
merge
this,
but
but
I
mean
this
is
to
solve
the
problem
which
I
have
run
into
on
multiple
cncf
projects
of
hey,
here's,
a
cncf
project,
it's
sponsored
by
a
company.
This
is
that
company's
first
significant
public
open
source
project.
They
don't
know
how
to
do
open
source
at
all,
and
I
found
that
often
they
are
actually
willing
to
assign
somebody
to
read
through
an
entire
guide.
If
the
guide
exists.
D
Yeah
I
mean
I
would
read
I
I
mean,
I
think,
that
this
guy's
amazing
for
that
role.
That
is
yeah
perfect.
I
wonder
if
we
should
even
put
like
a
little
thing
at
the
top
catherine
that
says
like
even
like,
maybe
an
intended
audience
or
like
who
should
read
this
or
I
mean
obviously
I
wanna.
Obviously
I
want
everybody
to
read
it,
but
it's
kind
of
a
just
like
a
like
a
little
flag.
I
guess
right
for
for
people
who
are
reading,
oh
cool,
you
already
have
one.
B
B
B
D
I
love
the
motivating
users
to
contribute
section.
That
was
the
first
pr
that
I
saw
that
I
liked
like
that.
Like
honestly,
and
I
love
that
you
led
with
that
one,
I
love
where
I
love
that
yeah,
like
I
love
that
we
led
with
that,
because
I
feel
like
that's
the
number
one
question
I
always
get
from
other
maintainers
is:
how
do
I
get
my
users
to
contribute?
A
B
C
I
have
a
suggestion
right
now,
part
of
what
makes
us
feel
daunting
to
imagine
someone
reading.
It
is
because
it
is
one
document,
but
that's
not
how
it's
going
to
be
presented
on
the
website
and
the
website.
These
are
individual
pages
and
I
think
a
good
way
to
tie
together
our
solution
focused
and
reference
documentation.
C
Right
now
we
just
have
reference
and
it's
the
templates
is
maybe
to
have
a
call
to
action
or
like
what
the
heck
am
I
supposed
to
do
with
this
information
that
you
just
dumped
on
me,
either
at
the
beginning
or
the
end
of
the
page,
so
that
you
can
immediately
jump
from
this
to
how
do
I
make
it
go?
How
do
I
make
it
go
fast?
You
know,
I
think,
because
we're
I
feel
like
we've,
given
a
lot
of
unactionable
feedback
to
catherine.
C
B
C
Yeah
yeah,
so,
oh
sorry,
sorry
I
was
gonna
say
we
can
get
a
lot
of
this
merged
in
and
then
have
separate
tasks
and
follow-ons
because,
like
I
said
we're
talking
about
follow-ons
right
here,
let's,
let's
do
that
with
this
too,
where
any
one
of
us
can
go.
I
know
what
one
of
the
next
steps
is
for
a
successful
pr
workforce
or,
to
be
honest,
the
entire
thing
about
automation
could
be.
C
You
know
more
links
and
and
like
here's,
a
quick
win,
here's
a
quick
one
and
just
list
five
quick
wins
at
the
end
of
these
sections
and
all
of
us
can
help
make
that
happen
without
having
to
hold
up.
I
really
don't
want
to
hold
up
catherine's
work
here,
because
it
is
a
great
bible
and
I
want
people
to
read
it
as
soon
as
possible.
A
D
Here
I
have,
I
actually
have
like
a
high
level
kind
of
question
for
the
crew
and
this
because
this
goes
back
to
like
this
whole
idea
of
like
or
not
idea.
These
like
open
questions
that
I
have
with
seeing
not
just
the
cncf
community
at
large
is
do
all
cncf
projects
have
to
be
contributor
communities.
B
B
But
in
some
cases
the
contributor
lad
is
only
going
to
have
two
rungs
on
like
for
a
smaller
community.
That's
that's
the
answer.
It's
not
that
you
don't
have
one!
It's
that
you
have
a
much
shorter
one
because,
for
example,
every
every
project
is
going
to
have
maintainers
and
if
you
don't
have
defined
criteria
for
how
you
become
a
maintainer,
then
it's
hard
to
demonstrate
that
your
project
is
open
to
new
maintainers.
C
C
D
No,
but
what
if
they
say,
why
can't
I
just
do
this
in
my
governance
md,
because
I
can't
the
reason
why
I'm
asking
these
very
specific
questions.
Maintainers
will
take
our
advice
and
just
fork
it
right.
So
so
I
guess
I'm
saying
here
is
like:
do
they
really
need
a
separate
document
as
long
as
it's
spelled
out
somewhere.
B
C
Agreed
a
lot
of
people
who
want
to
do
more
than
just
we
have
maintainer
press
these
buttons.
You
are
a
maintainer
and
it's
two
lines
are
going
to
want
to
say
a
lot
more
than
really
fits
or
belongs
in
the
governing
dock,
at
which
point
it
makes
sense
to
have
the
separate
template,
which
is
why
we
went
that
way.
D
B
B
B
A
Well
so,
as
I
said,
scott
has
them
out
there,
so
I
think
he
can
add
me
to
it
or
something,
and
I
can
add
a
little
bit
to
it,
but
I
think
we
wanted
to
have
like
next
well,
we
had
like
two,
the
next
steps,
takeaways
and
five
quick
wins,
which
we
have
to
decide.
What
we
I
like,
I
kind
of
like
the
kick
quick
wins
as
well.
I
thought
it
was
kind
of
like
it
sounds
cool.
A
A
C
D
D
D
D
A
Yeah,
so
when
I
knew
about
it
sorry,
this
is
what
I
did
here
right,
because
I
knew
you
were
working
on
the
recruit
recruitment,
recruiting
playbook.
So
that's
what
I
why
I
created
here,
because
I
thought
like
that
fits
in
really
well.
So
it's
like
hey
and
here
are
a
few
examples,
and
it's
like
okay,
here's
the
full
thing
right
so
totally
agree.
A
If
we
have
this,
I
just
didn't
know
like
don't
know
where
that
would
be,
but
I
totally
agree
we
don't
want
to
be
like
the
the
like
if
this
can
be
like
really
high
level.
It's
like
okay,
here
are
the
things
you
have
to
think
about,
and
then
it's
like
boom
boom
boom
here
are
the
details
like
if
you
just
want
to
have
an
overview,
just
have
a
read,
but
if
you
want
to
dive
deeper
here
are
the
the
links,
and
so
you
can
really
kind
of
learn
more.
A
So
I
think
that
that's
basically
the
the
kind
of
idea
that
I
had
if
there
is
any
duplicate
content
here
or
something
it's
because
I
wasn't
aware
right.
I
did
this
with
your
playbook.
I
did
it
with
a
letter,
so
I
didn't
go
into
the
letter
in
more
detail.
That's
what
the
actual
file
is
right,
so
so
at
some
point,
maybe
what
we
can
do
as
we
create
new
assets
that
go
deeper,
we
can
decrease.
You
know
like
we
have
like
three
paragraphs
talking
about
the
topic.
A
C
C
C
A
Yeah,
well,
I
think
it's
a
matter
like
as
the
content
grows,
is
kind
of
keeping
in
mind
what
we
have
and
then
adjust
it
right
and
then
yeah
or
should
it
link
what
should
what
can
be
reduced,
but
it's
a
good
problem
to
have
like
once
you
that
means
that
you're
creating
more
and
more
assets
right
now
we're
just
getting
started.
I
guess
okay,
so
for
now
I
just
or
scott
we'll
submit
the
missing
prs
and
then
we
add
those
quick
wins
or
next
steps
or
takeaways
or
whatever.
A
C
Have
them
right
now
and
you
just
need
to
copy
and
paste
them
in,
like
sure,
obviously
we
can
do
it
now.
Otherwise,
I
think
that
those
are
great
things
for
everyone
in
this
call,
and
you
know
in
the
wider
community
to
add
as
they
identify
them.
I
don't
want
to
hold
it
up,
because
we
haven't
figured
out
what
the
right
key
takeaways
are,
though,
for
each
section,
yeah
and.
A
I
think
that
can
be
added
as
we
go
too
and
paris.
Just
to
your
point.
I
think
the
reason
why
we
wanted
to
like
we
yeah
so
that's
when
I
when
I,
when
scott
read
through
it.
The
truth
is
because
that
was
all
based
on
interviews
right
and
this
was
whoops
come
on
go
back
back
here
and
this
kind
of
goes
very
much
into
the
github
detail.
So
what
we
were
thinking
is
it
would
be
good
to
have
an
additional
page
that
goes
more
into
because
it's
too
specific
to
github.
A
A
Okay,
cool
but
yeah.
That
was
that
was
basically
the
reason
why
we
decided
to
just
skip
it
for
version
two
or
an
additional
page,
because
it
was
like
high
level,
high
level
eye
level
and
then
suddenly
you're
talking
about
one,
which
was
a
little
odd
because,
like
why
are
you
diving,
deep
into
github
and
then?
But
that
was
just
because
the
interviews
go
that
way
and
I
wanted
to
capture
everything.
D
That's
why
I
think,
like
a
good
highly,
I
think
that
automate
as
much
as
you
can
might
even
want
to
go
all
the
way
up
to.
I
would
personally
take
it
all
the
way
up
to
the
top
and
like
because
that's
a
good
high
level
of
why
you
should
automate
and
the
fact
that
it
like
just
adding
more
things
and
adding
more
process
to
a
maintainer,
doesn't
mean
that
things
are
going
to
necessarily
get
better.
It
means
things
are
going
to
increase
in
volume,
which
is
burnout.
D
A
And
yeah,
maybe
I'm
gonna
read
through
it,
and
maybe
just
when
we're
talking
about
all
these
things,
to
keep
in
mind
just
always
kind
of
say
like
something
don't
worry,
these
things
can
also
be
automated.
It's
just
like
in
theory,
you
have
to
be
transparent,
but
you
can
also
do
you
can
also
leverage
technology
to
make
it.
You
know
yeah
easier
on
you
100.
A
C
Of
maintainership,
when
we
have
the
website,
I
think
it's
going
to
give
us
an
opportunity
to
make
this
information
feel
much
less
like
a
wall
of
text,
because
we
can
take
so
many
of
these
things
and
bring
them
out
into
their
own
separate
pages
too.
So
we
can
link
to
it,
and
this
really
can
be
high
level,
with
lots
of
links
to
other
pages
that
go
into
the
nitty
gritty
details.
C
A
Yeah,
but
I'm
excited
that
you
like
the
idea
to
have
this
like
as
a
starting
point
and
then
kind
of
have
all
the
things,
because
I
think
that's
like
I
I
mean
that's
how
like
some
people
will
start
with
that,
and
some
people
will
right
go
right
into
the
the
specifics,
depending
where
you're
in,
but
if
you're,
really
starting
at
the
very
beginning,
and
you
need
to
know
you
know
like
as
josh
had
that
meta
overview
right
like
then
you
go
here
and
then
yeah
okay.
So
it's.