►
From YouTube: CNCF SIG Contributor Strategy 2020-11-05
Description
CNCF SIG Contributor Strategy 2020-11-05
B
C
B
D
E
No,
I
rearranged
my
whole
schedule
so
that
I
could
stay
up
all
night
and
watch
the
results
come
in
because
they're
not
in
a
time
zone,
that's
friendly
to
me
but
pain
after
brexit.
Like
you
look
at
the
polls
and
I
went
to
bed
and
I
was
like:
oh
you
know
it's
going
to
get
remained.
That's
what
all
the
polls
say.
E
D
B
So
so
we
had
mentioned,
we
had
mentioned
this.
Why
don't
we
just
do
it
or
should
we
do
the
should
we
do
the
hey,
we're
meeting
we're
meeting
stuff
yeah?
Let's
do
that
really
quick,
hello,
hello!
Everyone
today
is
november
5th.
This
is
the
bi-weekly
meeting
for
cncf
sig
contributor
strategy.
This
is
a
meeting
that
will
be
recorded
and
available
on
the
internet
later.
So
please
be
mindful
of
what
you
say
and
do
please
be
sure
to
adhere
to
the
cncf
code
of
conduct
and
in
general,
just
be
awesome.
People.
B
F
F
F
So
those
are
the
things
that
I'm
like
really
gung-ho
about
right
now,
but
if
there's
been
further
developments
with
maintainer
circle
without
me
like,
let's
talk
about
it
and
collaborate
and
see
how
we've
how
we've
grown
and
and
whatnot
I
mean-
I
don't
necessarily
think
it
needs
to
be
some
one.
Size
fits
all
thing,
but
please
go
ahead.
G
B
F
Yeah
I
was
like
I
was
envisioning
break
rooms
and
small
discussions
kind
of
like
what
we
do
here
now
with
individual
groups,
but
a
lot
of
different
maintainers
from
different
groups,
which
then
the
conversation
would
get
a
little
wild.
So
I
was
mean
I
was
envisioning
breakout
rooms
and
discussions,
and
things
like
that
from
way
back
in
the
day
way
in
the
beginning
of
this
year,
but
yeah,
I
know
I
do.
I
have
some
awesome.
B
So
yeah,
so
what
we?
Actually,
I
think,
maybe
it's
a
few
meetings
back.
What
we
had
landed
on
was
we
kept
coming
back
to
like
burnout
and
just
talking
about
like
maintainer
sustainability,
so
we
were
thinking.
Maybe
we
do
that
as
the
first
topic,
the
contributor,
no,
the
inclusive
naming
initiative
is
planned
to
have
its
first
community
meeting
at
cubecon.
So
it's
going
to
be
that
thursday
morning,
depending
on
your
time
zone.
B
F
F
Yeah,
I've
just
I've
just
been
using
github
issues.
So
that's
for
all
the
issues,
that's
where
they
all
are
now
I
mean
I
can
definitely
organize
that
in
a
better
way
or
we
could
put
an
issue
template
together
all
ears.
I
mean
this
is
you're.
Looking
at
the
the
bottom
of
the
foundation
of
the
of
the
thing,
any
anything
can
be
changed
at
this
point,
so
you
as
as
it
stands
at
10
38
a.m.
F
D
F
B
D
You,
although,
if
we
want
to
do
maintainer
circle,
stuff
bi-weekly,
then
do
we
want
to
basically
have
this
on
the
calendar
every
week
and
every
other
week
it's
going
to
be
maintainer
circle
and
then
the
succeeding
week.
It's
going
to
be
half
an
hour
of
actual
sig
stuff
yeah.
That's
how
we
want
to
do
things.
C
B
F
D
Prep
for
our
mini
micro
paperwork
workshop,
the
we've
done
dawn
carolyn
and
I
have
done
the
recording
now.
There's
two
other
things:
one
is
to
potentially
get
more
materials
for
projects
prepared
to
you
know
whatever
we
can
get
put
together
in
the
next
two
weeks
and
then
the
other
thing
is,
of
course,
to
get
project
leaders
to
show
up
at
it.
D
I
already
plugged
the
session
in
the
toc
meeting
on
tuesday,
but
that
meeting
was
extremely
lightly
attended.
So
I'm
I
don't
know
that
necessarily
anybody
that'll
have
actually
gotten
the
word
out.
You
know
beyond
that.
I
think
we
can
all
sort
of
individually
socialize
it
we're
gonna
ask
amy
to
send
something
out
to
the
projects
yeah.
F
D
I
D
D
D
And
so
I'm
writing
generic
template
documents
for
each
of
those
forms
for
the
templates
directory.
It's
extremely
difficult
to
write
completely
generic
governance
documents
because
you
pretty
quickly
get
into
a
decision
tree
of.
If
you
do
this,
and
if
you
do
that,
so
I'm
going
to
get
that
those
done.
Probably
tomorrow,
I
and
then
I'll
ask
people
to
review
them.
I'd
like
to
have
them
available
for
the
micro
paperwork
session.
D
D
I've
been
cutting
and
pasting
that
to
fit
in
with
the
cncf
requirements
and
the
structures
we
have
for
the
rest
of
our
documentation
and
I'm
going
to
try
to
get
that
finished
for
the
paperwork
session,
so
that
even
for
types
of
paperwork
where
we
don't
have
a
full
advisory
document
or
a
template.
We
at
least
have
a
paragraph
saying:
hey
you're,
probably
going
to
want
this.
F
So
some
of
the
governance
documents
that
are
in
the
resources
guide
are
actually
really
beautiful,
and
I
was
wondering
if
we
could
adopt
some
of
those.
So
some
of
the
there's
like
a
there's
like
re
there's
like
governance
checklists,
some
of
them
are
really
beautiful,
like
I
can
bring
up
them
now
like
like
sustain
a
like,
sustain
oss.
F
They
have
a
governance,
checklist
and
they're,
really
like
thoughtful
and
like
they
would
be
great
for
like
a
workshop,
I
don't
know
if
y'all
thought
about
that
kind
of
style
and
like
there's
one
one
of
them.
That's
linked
as
well
is
like
a
work
there's
like
a
governance
workshop
and
it's
the
curriculum
of
the
governance
workshop
that
looks
like
it
could
be
sort
of
a
plug-and-play
to
like
what
we've
already
done
and
stuff
hold
on.
Let
me
I'm
gonna
get
some
of
the
links
out.
D
The
and
that's
actually
led
to
something
else
I
put
further
down
on
the
agenda,
but
so
we
are
focusing
on
a
checklist.
It's
the
cncf
requirements,
checklist
for
for
different
levels
of
maturation
and
then
what
we
focus
on
in
detail
is
going
to
depend
on
who
shows
up
the
we
have.
What
was
it
with
12
minutes
of
video
and
the
12
minutes
of
video
sort
of
focuses
on
that
checklist
and
the
general
requirements
and
then
the
rest
of
it's
going
to
be
q.
D
D
B
D
D
F
D
D
F
So
I
was
like
we
should
just
like
you
could
almost
not
adopt
it,
but
pretty
much
adopt
up
a
plug-and-play
with
some
of
the
stuff
that,
like
all
the
work,
that's
on
like
some
of
the
stuff,
that's
already
been
going
on.
You
know
what
I
mean
to
like,
make
it
hours
if
you
will,
but
from
a
general
a
general
sense.
F
D
B
D
Specific
stuff
I
have
so
far,
I
can
work
into
the
templates
most
of
the
cncf
stuff
does.
Is
it
limits
some
of
the
decisions
you
need
to
make
right
like
you,
don't
need
to
come
up
with
a
whole
structure
for
managing
your
ip,
because
the
cncf
does
that
right?
You
just
need
to
designate
who's
allowed
to
tell
the
cncf
what
what
to
do
the
and
you
don't
have
to
decide
which
coc
to
have
you
know
those
are
two
things
you.
F
B
B
Words
I
there
are
words
I
I
didn't
know
what
I
was
doing.
This
is
a
short
version
of
it
and
there's
there
yeah,
there's
quite
a
bit
of
digging
that
you
have
to
do
to
kind
of
like
put
the
pieces
together
in
the
right
way.
There
are.
There
is
a
template
now
right,
there's
a
template
for
proposals,
an
expectation
of
doing
a
pr,
but
it's
still
hard.
I
would.
D
D
D
The
I
do
have
to
say
one
of
the
dismay
things
was.
I
said:
okay
well,
first,
what
I'm
gonna
do
for
copying
texas,
I'm
just
gonna,
look
through
the
governance
documents
that
we
have
for
all
of
our
established
projects
and-
and
you
know,
pull
out
common
elements
and
the
thing
is
even
when
the
workflows
are
more
or
less
the
same.
The
wording
is
completely
different.
H
B
H
H
F
E
F
D
J
J
F
Yeah
yeah
yeah
and
those
are
on
the
resources,
the
resources
guide
that
we
have
in
the
in
the
github
repo
too.
So
if
we
want
to
just
like
review
that
too
josh,
you
could
pretty
much
use
anything
that's
on
there
yeah,
if,
like
we,
if
you,
if
you
have
to
fill
in
gaps,
meaning
like
and
and
say,
like
you
know,
more
templates
coming
tbd
kind
of.
H
D
D
D
F
J
F
J
F
C
F
F
J
B
J
F
D
Well
wait.
No,
that's
not
right,
and
so
now
we
have
a
much
bigger
to-do
item
of
hey.
We
need
to
actually
have
somewhere
a
canonical
source
of
what
the
complete
requirements
are
for
projects
at
each
level
and
and
then
that
source
should
become
the
source
of
data
for
all
other
places
where
this
is
listed.
D
D
F
Yep
and
then,
but
any
anything
else
as
far
as
like
resources
or
like
any
any
folks
to
like
help
us
out
because,
like
the
thing
is
the
thing
about
the
cncf
site
right,
is
it's
not
totally
open
source
or
is
it
now
because
it's
like
it's
like
a
wordpress
thing,
a
wordpress
theme
or
something
like
I
don't
know.
I
don't
remember,
but
yeah
there
was
like
some
yeah
no.
D
D
J
G
F
J
B
J
F
J
B
F
I
H
B
B
J
J
B
F
B
Yeah
we
did
so
like
for
the
naming
stuff.
We
did
a
panel
to
talk
to
start
talking
about
the
inclusive
naming
initiative
and
everyone
on
the
panel
was
basically
I
was
like
I'm
an
engineer.
I
don't
want
to
do
things
twice
like.
Can
we
just
lay
down
a
framework
that
works
for
everyone
and
try
to
adopt
it
everywhere
and
they're
like
yeah?
We
don't
want
to
do
these
twice.
That's
why
we
form
this
thing.
D
B
B
That
is,
that
is
the
point
that
I
feel
like
everyone
is
at
agreeing
to
so
with
kubernetes,
specifically
and
probably
a
lot
of
other
places.
It's
basically
people
you
have
like
you,
have
a
set
of
people
who
are
interested
in
making
changes
or,
and
maybe
new
contributors
come
by
and
they're
like.
Yes,
let's
make
this
change.
I
saw
this
issue
was
open
and
I
started
searching
room
place.
Replacing
everything
and
you're
like
oh
hold
on
hold
on.
Don't
do
that
yet
because
you
just
changed
an
api
and
we
have
an
api
deprecation
policy.
B
Yada
yada
yada
right.
So
yes,
that
one
too
so
trying
to
figure
out
like
the
people
who
were
ready
to
run
but
giving
them
a
framework
to
run
with.
So
we
landed
the
docs
for
basically
like
recommendation
or
workflow
and
a
template
and
a
language
evaluation
framework
to
give
people
kind
of
like
a
starting
path.
B
And
then
I
think
aaron
landed
the
first
thing
using
that
workflow,
or
rather
we
have
to
review
it,
but
it's
it's
master
to
control
plane
right
then
we're
going
to
wear
on
top
of
that.
One
like
qbadm,
has
some
work
and
flight
as
well
already
and
they've
started
making
changes
on
the
website.
So
you
know
it's
going.
It's
going
all
right.
I
think
the
what's
cool
about
the
language
evaluation
framework.
B
We
don't
want
these,
and
then
you
know
the
next
piece
is
like:
okay,
we'll
lay
down
the
recommendations
for
them,
execute
on
that
hand
it
off
to
the
the
code
owners
or
the
content
owners,
and
the
next
piece
for
us
is
that
you
know
finding
people
who
are
interested
in
doing
the
work
now
that
some
of
it
is
better
defined
and
then
also
starting
to
think
about
those
second
and
third
order
concerns
that
you
know
that
are
maybe
a
little
bit
more
ambiguous
right.
So.
D
D
B
D
D
D
D
F
A
B
B
D
D
B
Yeah
yeah
great,
I
love
that
I
mean
what
I
loved
most
about.
That
conversation
is
we're
like
hey.
You
know,
okay,
well,
when,
when
you're
all
set
with
that
stuff,
just
like
post
it
up
on
the
mailing
list
and
we'll
you
know
and
we'll
we'll
do
the
tweets
and
the
blogaid
thing
or
the
you
know
the
face,
crams
and
yeah,
and
then
they
came
back
and
you
know
sent
something
to
the
mailing
list
talking
about
contributor
growth
and
we're
like
we
have
that
like
we
have
that
come
come
on
down.
D
B
D
The
so
yeah
the
I
mean,
actually
I
I
generally
kind
of
like
the
week
after
switch
back
to
standard
time,
because
I
have
all
these
early
morning
meetings,
and
so
that's
like
one
week
where
it's
a
little
bit
easier
for
me
to
get
up
for
those
early
morning.
Meetings
assuming
those
meetings
are
set
in
u.s
time,
if
they're
set
on
european
time.
It
doesn't
help
me
so.