►
From YouTube: CNCF SIG Contributor Strategy 2021-03-25
Description
CNCF SIG Contributor Strategy 2021-03-25
A
A
I
don't
know,
I
just
have
so
many
zoom
meetings
and
I'm
just
so
so
tired
of
them.
This
week
it's
been
better.
The
last
two
weeks
have
been
better
because
of
the
the
time
zone.
Confusion.
So
you
all
went
to
daylight
savings.
We
have
not.
So
all
my
meetings
are
an
hour
earlier
so
like,
instead
of
being
done
at
7
30,
I'm
done
at
6
30.,
it's
pretty
cool.
A
C
A
A
D
C
C
B
B
B
C
C
C
B
C
C
B
B
A
D
D
C
D
Keep
trying
to
stage
this
somehow
and
then
rolling
it
out
without
impacting
anything,
but
we
also
want
a
whole
bunch
of
review
to
happen,
but
the
review
is
not
happening
so
like
it's
going
to
stay
stuck
for
a
very
long
time
and
like
so
when
I
first
did
it.
We
kind
of
talked
about
we're
just
going
to
merge
these
two
pr's
at
the
same
time
and
have
a
website.
D
We
don't
switch
over
the
domain,
but
the
website's
live.
But
that
means
that
for
a
period
of
time
like
between,
if
you
don't
merge
them
at
the
same
time
or
you
don't
flip
the
domain
or
whatever,
like
basically
in
a
day
or
something
you're
gonna
end
up
with
weird
links
that
go,
don't
go
to
the
right
place
because
they
assume
it's
gonna
be
hosted
at
the
url
it's
hosted
at
so
it
makes
sense
but
like
in
the
meantime,
it's
like.
D
D
C
D
So
I've
linked
both
pr's
okay,
because
there's
always
lag
between
when
I
asked
people
for
reviews
and
when
I've
rebased
it
last
on
on
the
main
branch
like
we
shouldn't
actually
merge
these
immediately
because
it
probably
needs
more
rebating,
because
more
stuff
is
moved
around.
You
know
what
I
mean
and
I
had
to
move
files
to
get
this
to
work.
So
if
we
get
approvals,
then
I'll
do
another
rebase
and
like
update
everything.
But
it's
getting
to
be
a
lot
of
work
to
rebase
it
over
and
over
and
over
again
and
then
well.
C
C
C
D
C
D
E
C
D
C
D
D
C
C
C
F
C
C
C
C
A
C
B
D
We're
just
putting
together
the
cube
contact.
I
guess
that's
the
that's
the
biggest
thing,
we're
gonna
record
early
next
week
to
be
honest,
like
I
lost
people
on
my
team,
and
I
have
way
too
many
things
on
my
plate
right
now,
so
I
haven't
been
able
to
do
much
around
contributor
growth
other
than
the
talk.
C
D
C
B
D
I
don't
have
time
to
do
thorough
reviews
and
and
like
edit
and
contribute
to
these
these
docs
that
we're
writing
right
now.
So
if
other
people
have
time
to
do
that,
okay,
yeah
that'd
be
really
helpful,
because
I
know
I
feel,
like
my
participation,
is
holding
up
the
contributor
ladder.
For
example,
I.
C
From
my
perspective,
you
actually
did
give
us
some
feedback
on
the
contributor
ladder,
I'm
actually
waiting
for
karen's
full
feedback,
because
this
has
been
her
baby
as
much
as
mine.
So
that's
the
other
thing,
but
but
my
goal
is
for
us
to
approve
the
contributor
ladder
by
next
week's
contributor
growth
meeting,
so
I'm
gonna
gonna
ping
her
about
it
again,
because
the
thing
is
it's
not
like
it's
not
a
document
doesn't
have
a
lot
of
her
input
already
it's
just.
C
I
really
need
her
to
do
a
final
check
on
it,
because
I
made
a
lot
of
changes
in
the
last
round
the
so
I'd
like
to
finalize
that
next
week,
because
it's
you
know
a
it's
something:
a
bunch
of
organizations
have
been
asking
for
b.
I've
already
put
it
into
play
with
an
existing
project
because
they
couldn't
wait
and
and
also
several,
our
governance
templates,
have
references
to
the
contributor
ladder.
C
C
C
I
just
put
that
in
as
a
note
in
the
main
document
saying
hey,
you
might
have
these
maintainer
specializations
depending
on
your
project
and
there's
a
list
of
them,
but
the
actual
requirements
for
them
are
going
to
be
very
specific
to
your
project
because,
like
I
started
out
with
say,
documentation
maintainer,
because
I
have
a
good
example
that
from
kubernetes
and
I'm
like
okay,
let
me
take
the
kubernetes
requirements
for
documentation,
maintainer
and
try
to
make
them
generic.
And
when
I
eliminated
everything
that
was
particular
specific
to
kubernetes.
D
C
B
D
I
think
the
the
reason
why
we
originally
wanted
to
try
to
include
content
like
this
somewhere
is
output
from
our
group
is
because
people
are
familiar
with
I'm
a
maintainer,
I
sling
code,
but
these
other
types
of
activities
and
roles
aren't
getting
adequate
representation
or
are
being
downplayed
compared
to
code,
and
so
it
was
an
aspiration
to
somehow
try
to
help
address
that
I
guess.
But
if
it's
not
working,
I
don't
want
this
to
hold
up
the
whole
ladder.
D
C
D
C
Because
one
of
our
big
to-do's
is
that
we
actually
ought
to
have
a
more
narrative
advisory
document
to
go
with
each
one
of
of
our
templates
like
all
of
them,
and
so
that
could
go
in
there
right,
as
we
could
say,
hey
here's
some
examples:
here's
the
kubernetes
documentation,
maintainer,
here's
the
program
manager
for
linker
d.
There's
you
know
all
of
these
other
roles
that
people
have.
But
these
are
you
know
we're
only
going
to
link
because
they're
not
templatable,.
B
B
So
yeah,
I
think,
like
especially
like
the
porter,
kubernetes,
etc.
I
think
that
would
be
really
good,
so
we
also
have
the
contributor
framework
that
katherine
and
for
catherine
and
folks
have
been
working
on.
That
also
is
kind
of
review-less,
and
that's
also
again
me
as
well,
so
I'm
going
to
put
some
eyeballs
on
that,
based
on
what
I'm
seeing
and
what
we
know
now
that
we
have
contributor
ladder
as
well
as
a
draft
of
the
recruiting
playbook.
B
It
sounds
like
we're
going
in
this
direction,
where
we
want
this
contributor
framework
to
be
this
umbrella
and
then
have
all
of
these
other
contributor
related
docs,
not
necessarily
governance,
but
those
two
docs
specifically
included
inside
of
those
in
inside
of
that
framework
model.
Do
I
have
that
correct?
D
B
Should
we
have
a
dedicated
meeting
for
this?
A
lot
of
people
said
no,
no
more
meetings,
let's
try
to
incorporate
it
in
our
meetings,
and
then
we
try
to
do
this,
like
every
other
meeting
thing
which
doesn't
work
for
google
calendars,
so
it's
kind
of
like
problem
statement.
How
can
we
get
them
a
dedicated
invite
without
having
a
ton
of
overhead,
so
what
we
came
to
is
what
we
have
in
the,
but
we
have
in
the
thread.
C
B
We
have
managing
grief
and
law
set
right
now,
but
it's
not
set
set,
but
we
need
to
confirm.
We
have
a
psychologist
that
works
with
maintainers,
not
just
like
maintain
but
folks
in
tech,
but
she
has
experience.
She
talked
to
kubecon
once
so.
She's
gonna
talk
about
that,
and
then
we
have
a
maintainer
that
I
won't
name
that
is
going
to
come
and
probably
do
a
fireside
chat
about
her
experience
with
managing
open
source
for
in
a
time
where
something
not
great
happened
to
her
child.
B
So
I
think
that'll
be
that'll,
be
pretty
nice.
She
feels
like
she
has
a
lot
of
like
lessons
learned
from
that
experience,
and
so
that's
that
so
you
could
host
that
one
josh.
It
sounds
kind
of
like
uber
depressing,
but
I
think
it
might
be
uber
worth
it,
because
it's
not
a
conversation
that
we
talk
a
lot
about,
but
it's
stuff
that
we
obviously
deal
with,
especially
in
this
pandemic.
B
D
B
C
C
C
F
B
I
I
feel
like
once
we
get
a
good
amount
of
cncf
folks,
I
mean
there's
60,
plus
projects
right.
A
thousand
maintainers
most
of
the
maintainers
still
have
no
idea
that
this
exists
yeah.
So
that's
the
only
thing
I
mean,
and
the
other
thing
is
like
most
of
the
maintainers
are
sharing
really
personal
stories
during
the
fireside
chat
part,
and
I
guess
they
would
have
to
be
okay
with
outside
folks
that
don't
abide
by
our
code
of
conduct
coming
in
and
potentially
tweeting
their
stories.
C
D
D
D
C
A
B
If
you
want
to
call
me
pum,
that's
kind
of
what
I
always
envisioned
this
as
just
like
an
open
door
for
cncf
maintainers,
all
thousands
if
they
want
to
come
in
and
they
can
come
in,
but
you
know
I
I
do
see
like
I
feel
like
it's
been
exclusive
due
to
the
fact
of
our
reach
is
only
so
far
so
that's
definitely
been-
and
I
bet
I
was
talking
to
karen
about
that
extensively
too,
when
she
was
when
she
was.
You
know.
C
B
F
B
I'm
gonna
quickly
draft
some
of
the
charter,
graduation
review
stuff
that
we
talked
about
today
that
import
that
incorporates
the
t
like
the
toc
liaison
stuff
like
having
one
lgtm
there
and
then
also
update
the
toc
with
the
new
structure
to
match
the
website
and
then
josh.
I
think
you
said
something
about
helping
out
with
some
kind
of
github
setup.
If
I
recall
there
is
an
open
pull
or
actually
I'm
sorry,
there
is
an
open
issue
for
you
to
do
the
pull
request
workflow
anyway,.
B
C
B
C
C
And
then,
and
then
do
this
meeting
only
on
the
alternate
two
weeks,
so
basically
we
only
be
having
this
meeting
every
four
weeks.
That
depends
on
our
ability
to
do
cue,
clearing,
asynchronously
and
if
that
really
doesn't
work
out,
then
I'll
be
proposing
adding
a
a
half
hour
cue
clearing
meeting
at
a
different
time.
B
C
D
C
I
feel
like
I
don't
want
to.
I
want
to
do
it
earlier
than
thursday,
just
because
you
know
for
like
dawn.
This
is
thursday
night,
and
I
you
know,
and
if
you
know,
somebody's
european
and
they're
taking
friday
off
then
they're,
basically
getting
a
ping
on
something
they're
not
going
to
look
until
next
week.
So
maybe
like
two.
C
C
C
F
D
F
C
My
particular
favorite
one
was
where
I
did
a
rebase
that
somehow
backed
out
every
commit
in
the
project
from
the
last
six
months.
That's
beautiful
and
it
would
be
like
you
know.
That
would
be
a
lovely
thing
to
do.
If
I
know
how
I
did
it
right,
because
there
are
times
when
you
actually
want
to
do
that,
and
you
end
up
spending
an
entire
weekend
doing
that
and
I'm
like,
if
I
had
any
idea
how
I
did
this.
C
C
Vm,
if
it's
any
consolation,
I
have
done
that
despite
the
fact
that
I
have
also
been
paid
400
an
hour
to
fix
somebody
else's,
get
repo
it
doesn't,
I
mean
get,
is
a
tool
with
notably
absent
guardrails.
It's
like
star
wars
in
the
bottomless
pits,
it
doesn't
take.
A
single
character
out
of
place
can
get
you
to
a
place
where
you
can't
figure
out
how
you
got
there,
how
to
get
back.