►
From YouTube: CNCF SIG Contributor Strategy 2020-07-16
Description
CNCF SIG Contributor Strategy 2020-07-16
B
A
B
B
B
A
B
A
C
B
C
A
D
April
did
you
we
want
Twitter
last
night,
no
okay,
yeah,
so
someone
socially
engineered
a
Twitter
like
kasseri
or
somebody,
someone
might
access
like
the
admin
plant
panel
and
they
were
able
to
get
into
the
accounts
of
all
the
major
verified,
Twitter
users
and
accounts
like
Barack,
Obama,
Biden,
Ilana,
Apple
I,
don't
know
like
a
whole
bunch
and
they
coasted
a
cryptocurrency
link
and
told
people
to
like
Dhoni
and
then
that
high
profile
person
would
match
it
and
acted
like
it
was
the
thing
for
charity
and
a
lot
of
people
did
I
was
like
asking
and
then
so.
D
The
people
who
had
the
accounts
we're
trying
to
like
delete
their
tweets
and
make
it
go
away
and
I
think
they
were
game
locked
out
and
the
emails
were
being
switched
to
something
else.
I,
don't
know
and
some
sort
of
test
shutting
down
Twitter.
They
just
locked
all
the
verified
people
out
of
their
account,
so
they
could
retweet
for
they
couldn't
tweet
original
tweets,
and
so
they
were
trying
to
communicate
simply
through
retweets,
which
was
hilarious.
So
the
unverified
had
blast
last
night
yeah.
That's.
F
Can
y'all
hear
me
now:
yeah
yeah
yeah,
we
good
yeah
I,
like
I've
decided
for
my
mental
health.
I
need
just
take
some
time
off
of
Twitter,
because
I
tend
to
wake
up.
Look
at
Twitter
and
thank
God.
The
world
is
terrible
and
so
I
missed
all
the
good
stuff.
Apparently
that's
kind
of
amazing
I'm,
really
sorry,
my
god,
yeah.
F
A
All
right
more
officially
for
the
recording,
hello,
hello.
Everyone
today
is
July
16th.
This
is
a
CNC
F,
sig
contributor
strategy,
meeting
this
meeting
that
is
recorded
and
available
on
the
internet.
So
please
be
mindful
of
what
you
say
and
do
please
be
sure
to
adhere
to
the
CNC
f
code
of
conduct
and
in
general,
just
be
awesome
people.
So
we've
got
a
few
things
on
the
agenda
and
it
looks
like
they're
all
they're,
all
working
group
or
sub
project,
the
updates
so
who
is
handling
the
project
template
update.
D
D
D
So,
instead
of
just
adopting
things
out
of
say,
kubernetes
or
something
like
that
is,
it
would
like
we're.
We've
created
the
contributing
guide,
so
I
finally
ways
to
put
that
we're
working
on
a
contribution
ladder
right
now
as
well
and
I,
know
Carbon
hunts
Josh's
in
here,
but
they're
they're,
working
on
similar
things
that
would
go
in
that
template
repo
as
well.
So
we
would.
D
A
F
There's
specific
things
Carolyn
that,
like
y'all,
want
help
with
cuz
like
I,
know:
parents
never
talking
yesterday
about
I'm,
at
least
for
some
other
stuff
that
I'm
working
on
like
looking
at
some
other.
You
know
examples
for
other
projects
and
kind
of
what
they
might
be
doing
so
as
part
of
that
like
is
it
helpful
if
we
find
other
things
and
use
it
to
create
new
stuff
for
deal
already?
We.
D
Really,
you
know
what
Josh
did,
which
was
great.
Was
he
laid
out
like
a
forward-thinking?
What's
all
the
different
content
that
governance
eventually
needs
to
make
I
want
to
do
the
same
thing
on
Tuesday,
with
contributor
growth
right
now
we're
working
on
the
contributing
guide
and
the
contribution
ladder,
but
we
haven't
made
it
like
a
full
list
of
everything
so
that
people
could
start
to
just
think
about
examples
in
the
community
and
start
collecting
them.
F
A
There's
also
a
I
think
it's
like
a
community
health
check
that
is
on
the
github
repos.
Where
can
check
if
you
have
like,
do
you
have
a
readme?
Do
you
have
a
contributor
guy?
Do
you
have
contributor
guidelines?
You
have
like
security
policy
in
place
and
if
we
make
the
repo
have
all
the
check
boxes
and
people
can
kind
of
grab
and
go
and
be
checked
off
in
multiple
places.
A
This
is
something
kind
of
is
relevant
to
me,
like
as
a
new
Dex
maintainer
to
one
of
the
things
that
I
came
to
mind
was
a
website
right
like
when
you
get
started
like
you,
don't
necessarily
have
a
website,
so
I
pasted
in
the
chat,
the
CAF,
Hugo,
Neto,
Phi
starter
as
well,
and
that's
one
of
their
grab-and-go
templates
that
you
can
use
to
just
bootstrap
a
repo
really
quickly
blue
trapper
website
really
quickly.
Oh.
D
C
One
other
suggestion,
maybe
I'll
PR
into
the
project
template
repo
is
one
thing
we
added
to
some
of
the
build
packs
repos
when
you
file
an
issue
so
you're
able
to
create
settings
with
like
good
of
actions.
So
you
can
have
like
different
templates
for
what
the
what
the
issue
should
look
like
and
monks,
and
we
can
also
have
a
link
to
something
else.
C
So
we
had
a
we
posted
and
like
feel
free
to
reach
out
to
us
on
slack
and
then
had
a
link
to
our
the
build
packs
lock
on
it,
which
I
thought
was
kind
of
a
useful
way
of
making.
People
are
free
to
file
issues,
but
they
can
also
just
chat
to
us
and
slack.
Instead
of
doing
that,
we
can
try
and
help
them
faster.
D
D
A
F
B
D
D
So
I'm,
if
you
want
to
add
things
I'm
like
taking
the
links
that
you're
putting
in
chat
and
putting
them
in
the
agenda,
so
we
don't
lose
them
after
the
end
of
the
meeting.
But
if
I'm,
if
I'm
missing
one,
please
link
them
in
there
and
I'll.
Get
these
made
sure
that
we're
talking
about
them
in
the
working
group.
D
But
the
plan
is
on
Tuesday
we're
gonna
go
through
and
make
a
big
list
of
all
the
content
and
stuff
like
that,
and
then
maybe
break
out
individual
issues
and
get
people
thinking
about
these
asynchronously.
So
we
can
have
multiple
people
working
on
these
and
say
like
iterating
on
the
issue
PR
or
the
template,
PRR
PRR
templates
or
start
a
website.
Things
like
that.
So
we
can
have
lots
of
people
working
so
low
surface
area.
For
these.
D
A
D
Originally,
we
were
talking
about
putting
these
in
contribute,
but
then,
when
I
started,
opening
up
an
issue
and
discussing
this
I
got
feedback
overwhelming
feedback
from
everyone
that
this
was
not
the
right
place
for
it
and
that's
what
inspired,
making
project
template
and
doing
it
separately?
The
concern
was:
is
that
contribute
was
really
for
new
contributors
coming
to
CN,
CF
and
looking
for
a
project
and
where
to
contribute
and
what
are
the
norms
and
how
to
do
it
and
everything?
D
And
then
this
type
of
content
we
were
looking
to
add,
was
really
more
for
maintainer
trying
to
get
set
up
and
either
learn
how
to
do
things
or
the
templates
and
everything
and
having
the
both
in
there.
They
didn't
want
to
have
it
all
mixed
and
matched.
In
addition,
we
wanted
it
to
be
a
template
repo
where
you
could
just
clone
and
go
so
that's
why
we
ended
up
making
the
second
repo
yeah.
A
That
totally
makes
sense,
I
would
not
argue
but
say
that
maintainer
ZAR,
also
contributors,
so
I
think
that
at
least
on
the
CN
CF
level
there
should
be
some
sort
of
to
get
started
as
maintainer,
and
maybe
that
lives
in
our.
Maybe
that
lives
in
our
contributor
strategy
repo
instead
or
does
it
live
and
contribute?
Does
a
live-in
contributor
strategy
who
knows
I
think.
A
So,
like
hey,
we
just
got
you
just
got
added
to
the
scene
ZF
as
a
sandbox
incubating
project
right
like
what
to
do
first
right.
How
do
you,
how
do
you
be
an
effective
maintainer,
as
how
do
you
be
an
effective
maintainer
of
a
CF
project,
as
opposed
to
just
a
maintainer
of
the
project
that
you
were
on
before
yeah
no
I
think.
D
D
D
Okay,
I
think
a
lot
of
this
is
gonna,
be
driven
from
the
contributor
growth
working
yeah,
so
I
think
they
should
just
come
to
the
the
meeting
next
week
on
Tuesday
cool
I
can
send
out
a
I'm
saying
in
the
mailing
list
today
sweet
and
invite
people.
Let
them
know
that
this
is
something
that
we're
going
to
be
starting
to
look
at
more
and
then
we're
gonna
be
making
I'm
kind
of
a
Content
grocery
list
and
kind
of
it
just
as
I
think
more
people
can
can
work
on
it
simultaneously.
A
Maybe
first
we
can
really
talk
about
for
quick
yeah
words.
First,
we
can
quickly
talk
about
the
the
TSE
update.
G
A
A
H
H
G
D
G
Karen
dropped
Dan,
yet
she
probably
had
a
conflict
at
11,
so
Karen
and
I
met
last
week.
What
we
talked
about
was
how
much
pretty
much
timing
sucks
on
this
for
launch,
because
obviously
cubic
on
Europe
is
going
off
in
August
mid-august.
We
don't
have
a
slot
there,
there's
no
slots
there
for
us
to
launch
this,
which
means
that
we,
if
we
were
to
launch
in
August,
we
would
be
competing
with
most
of
the
events
going
on,
and
people
would
not
like
that.
G
So
that
leaves
us
with
September,
which
just
seems
so
far,
at
least
to
me
anyway,
to
try
to
launch
something
and
still
maintain
the
momentum
of
the
newness
of
this
group,
so
I
fret
that
we
need
to
figure
out
something
to
launch
and
something
like
it
outside
of
just
like
a
slot
channel.
The
other
thing
that
we
talked
about
was
how
some
people
still
don't
identify
with
the
word
maintainer.
The
goal
of
the
group
is
to
grow,
maintain,
errs
and
support
them.
G
G
D
Notice
all
a
name
but
I
know
one
thing
that
maybe
resonates
more
with
people
in
the
kubernetes
community
is
the
concept
of
chop
wood
carry
water
and
whether
you're
a
maintainer
or
no
reviewer
I
think
you
do
maybe
associate
more
with
that
concept,
and
we
could
find
something
that
maybe
links
in
with
that.
We
could
find
a
cute
name
that
more
people
associate
with
I.
Don't
have
a
name
that
goes
with
that
yeah.
It
just
kind
of
came
to
me
right
now,
but
I
like
unicorns
too
and
then
stamp
cute,
so
I.
G
Also
a
be
tested,
the
just
the
term
leadership
circle.
A
lot
of
people
also
did
not
think
that
they
were
a
leader
because
they're
not
on
a
steering
committee
or
something
which
is
weird
we're,
not
leaders
either.
Sorry
I
was
kidding.
G
I
A
A
G
A
B
My
experience
about
naming
is
that
when
you
name
something,
no
one
will
like
it
and
it
doesn't
matter
what
name
you
pick.
No
one
will
like
it.
Nobody
liked
the
name
Google
when
they
first
launched
the
iPad
got
all
kinds
of
bad
press.
I.
Think
you
pick
something
that
seems
reasonable.
You
go
with
it,
and
people
would
people
will
get
used
to
it.
B
Honestly
I
would
go
with
maintainer
circle
and
just
be
clear
about
the
definition
that
it's
it's
for,
reviewers
it's
for
approvers,
it's
for
owners,
it's
for,
but
no
matter
what
you
picked.
People
or
leadership
circle
I
mean
I
would
I
would
honestly
I
would
go
with
one
of
those
cuz
I
think
coming
up
with
something
crazy
is
gonna,
be
even
even
worse.
A
G
A
But
what
I
kind
of
don't
dig
about
leadership
is
like
some
people
specifically
don't
want
to
be
in
leadership
right
like
they
can
I
feel
like
they
can
sooner
get
on
board
with
the
idea
of
like
owning
code
and
maintaining
code
right,
our
owning
content
and
maintaining
content,
as
opposed
to
you,
I,
have
to
lead
a
thing.
I
have
to
run
a
meeting.
I
have
to
you
know
like
they're.
You
know.
Additional
responsibility
is
implied
with
with
leadership
at.
C
The
same
time,
I
feel
like
with
the
recent
discussion
on
like
master
slave
mentality.
I
feel
like
ownership
is
also
could
be
a
touchy
word,
not
necessarily
but
like
I
could
see.
You
know
people
getting
like
flared
off
about,
even
though
there's
obviously
no
like
there's
no,
not
necessarily
any
insinuation
there
on
that
and
yeah,
but
this
is
no.
This
is
lonely.
Had
I,
don't
know
something
about
growth
as
well
like.
If
this
is
a
group
for
people
who
are
trying
to
to
contribute
to
and
to
grow
their
products
know
this.
G
F
G
Then,
what
about
the
tamai
timing,
tobacco
or
timing
tobacco
here,
where
it's
like?
How
do
we,
because,
like
the
planning
for
this,
is
gonna,
take
care
of
and
I
like
to
launch
like
from
you
know,
to
launch
kind
of
this
birds
of
a
feather
II,
not
serious,
first
session
and
then
launched
the
second
session,
which
is
technically
the
first,
with
like
the
inclusive
language
kit,
with
the
inclusive
language,
fit
we're
talking,
like
probably
three
to
four
weeks
of
planning,
all
of
those
things
but
again
Knox
when
it's
like
that's?
G
F
Well,
I
I
also
think
like
it's
a
little
different
than
if
coupe
Khan
was
in
person
in
terms
of
it
becoming
this
all
consuming.
Everybody
is
only
focused
on
that,
since
its
virtual
this
year,
like
I,
think
it's
less
of
a
you
know:
you're,
not
traveling
you're,
not
you
know
we're
not
getting
to
hang
out
with
each
other
and
have
fun.
We
have
no
choice
but
to
sit
in
front
of
our
computers
and
look
at
updates
without
their.
H
A
You're
you're
totally
right
and
you
know
the
talking
with
the
chairs
and
Aunty
about
this
stuff.
It's
like
it
feels
like
another
meeting
like
there's
no
physically
going
to
a
place
and
blocking
off
time
and
the
workday
like
you're,
still
going
to
be
doing
other
stuff.
You
know
it's:
it's
yeah,
I
I,
don't
know
I
I'm
fine,
with
waiting
personally.
G
All
right
well
launch
with
maintainer
circle,
wait
for
the
duck
and
we'll
do
September
the
other
thing
that
we
talked
about
that
I.
Actually
don't
want
to
necessarily
take
the
time
on
now,
because
I'm
rather
file
the
issue
first,
but
I
think
that
if
we
redid
maintainer
Scot
CN
CF
at
IO
into
an
actual
site
that
could
be
useful,
like
we
could
link
to
things
like
the
project
templates
and
like
the
events
that
we're
going
to
post
for
maintainer,
x'
and,
like
everything,
goes
right
now.
G
It's
just
the
spreadsheet
of
who
can
vote
for
toc
people,
mm-hmm
I,
think
that
would
give
folks
an
identity
and
not
even
a
surly
identity,
but
just
also
just
give
us
somewhere
to
host
this
stuff.
That's
not
necessarily
a
github
as
well
and
like
maybe
we
could
even
like
feature
maintainer
hers.
They
maintain
your
profiles.
Like
I,
don't
know
there
was
just
an
idea
that
I
had
I'd
rather
file
an
issue,
but
I
wanted
to
get
general
kind
of
like
good
bad
ugly,
feels
on
that
kind
of
an
idea.
I.
A
A
You
know
the
K
Kate's
dot,
io
stuff,
where
we
maintain
you
know
in
maintain
email,
membership
or
group
membership
by
IMO
right,
like
the
maintainer
z',
should
not
have
to
necessarily
be
something
that
amy
has
to
update
right
of
any
anyone
who
has
you
know
anyone
who
can
add
an
entry
to
a
yeah
mol
file
should
be
able
to
go
in
and
and
drop
an
update,
and
then
we
slurp
that
into
whatever
site
ends
up
getting
put
up.
I
like
the
idea
yeah.
F
And
I
also
think,
like
you
know,
as
takes
on
more
projects
like
this
spreadsheet
just
becomes
unwieldy
pretty
quickly,
and
so
you
know
it
would
be
great
to
have
it
be
something
that
you
could
easily
filter
by
like
sandbox
projects
and
graduated
and
all
that
and
then
get
to
like
what
you're
really
looking
for,
because
this
is
a
lot
it's
a
pretty
rainbow.
But
it's
a
lot.
G
Yeah,
so
cool
all
right,
I'll
write
an
issue
and
do
the
whole
caboodle
for
it.
But
I
just
wanted
to
get
like
a
pulse
check
of.
Please
don't
go
down
this
line
or
please
do
so.
I'm
gonna
keep
on
truckin.
So
that's
the
end
of
maintainer
circle.
D
Contributing
good
so
I
will
submit
that.
Finally,
because
we
have
the
project
template
repo
now,
so
that's
all
I
have
to
say
about
that.
We're
gonna
start
working
on
the
latter
next
and
then
we'll
kick
off,
making
a
big
grocery
list
of
content.
We're
gonna
start
working
on
next
in
crowdsourcing.
So
let's
move
on
to
governance.
I
G
F
B
Sure
so
suggest
put
together
the
tracking
issue,
which
had
a
big
laundry
list
of
the
types
of
content
that
we
need
for
governance
and
there's
lots
of
it
that
actually
kind
of
overlaps
with
contributor
growth.
So
I
think
there
are
some
bits
that
some
of
the
people
who
are
working
in
both
of
those
working
groups
are
focused
on.
I
took
leadership,
selection
for
governance,
just
something
that
was
relatively
stand-alone
and
I
put
together
a
draft.
So
if
you
want
to
have
a
look
at
it
edit,
it
leave
some
some
feedback.
That
would
be.
B
G
B
Because
they
were
sort
of
blessed
by
the
CNC
F
in
one
way
or
another
as
graduated
projects,
but
if
we
think
there
are
other
like
really
good
examples
of
any
of
those
any
of
those
areas
or
if
there's
maybe
an
area,
that's
more
commonly
used
in
another
type
of
foundation
that
isn't
really
as
represented
in
CNC
F.
Maybe
we'd
want
to
add
an
area
and
use
some
other
examples.
I
B
B
No,
no
I,
don't
think
so,
because
this
is
more
like
a
bunch
of
options
that
you
could.
You
could
pick
but
you'd
kind
of
want
to
pick
one
and
then
go
with
it.
You
should
definitely
add.
G
D
Just
like
what
we
did
I
think
is
helpful
is
sometimes
your
template
just
needs
to
have
a
bunch
of
comments
that
walks
you
through.
These
are
the
required
things
need
to
have
and
here's
some
of
the
optional
things
you
need
to
have,
and
we
may
link
to
documents
like
this
one
where
we
go.
You
need
to
make
this
decision
here
are
some
things
you
need.
You
can
look
at
and
then
you
should
pace
one
of
these
in
here
and
go.
This
is
what
you're
going
to
use.
D
B
Think
it'd
be
useful
to
have
a
governor
instead
MD
template,
because
there
are
some
common
things
that
everything
should
have
so
like.
What
is
your
decision-making
criteria
that
should
be
in
your
governance
document?
What
how
our
maintainer
selected,
how
is
you
know,
I,
don't
know
leadership
selected
or
something
I
think
we
should
at
least
have
some
categories
and
then
links
out
to
documents
that
will
help
them
make
those
decisions.
G
The
other
governance
stuff-
that's
not
on
the
agenda,
but
just
needs
to
bubble
up
for
everyone
just
in
case,
just
only
keep
everybody
on
the
same
page
is
the
multi
org
stuff
is
e.
The
steering
committee
guidance
that
we
gave
to
the
TOC.
G
I
F
Mean
I
think
it
hey.
We
said
we
made
him
recommendation
to
the
TOC,
but
it's
it's
correct
that
like
they
can
ignore
that
right
anyway,
yeah
yeah
for
sure
so
I
guess
that's.
When
we
talk
about
like
next
steps,
it's
kind
of
like
they're,
still
having
you
know
the
conversation,
so
it's
kind
of
a
I,
don't
know
what
is
our
next
step
other
than
you
know
like
we
said
we
don't
think
this
is
the
way
to
go.
Guess.
F
We
Senate
approach,
I
I,
just
don't
know,
I,
don't
know
why
I
know
I,
know
I
know
personally,
I'm
I
was
gonna
respond
to
the
thread
to
just
get
a
little
more
clarification
from
the
last
question
was
like
Matt
talking
about
continuity,
details
and
I'm,
just
kind
of
curious
as
to
like
what
what
he's
envisioning
there.
When
he's
thinking
of
you,
know
continuity
and
how
a
project
would.
F
How
would
a
project
make
its
own
continuity
plan
when
you're
trying,
when
you're,
looking
at
a
scenario
where
the
current
maintainer
czar
no
longer
maintaining
the
project?
If
that
makes
sense,
and
so
that's
why
I'm
trying
to
get
a
feel
for
like
what
exactly
he's
trying
to
get
to
there
and
I
think
I
think
it
all
comes
back
to
like
you
know,
there's
still
a
lot
of
open
questions
about
what
exactly.
F
They're
trying
to
get
at
because
I
liked
you
know
like
DIMMs,
have
pointed
out,
though
the
tagging
aspect
and
like
is
it
something
that
is.
Is
it?
Is
it
something
as
simple,
as
you
know
saying,
like
these
projects,
have
this
kind
of
a
you
know,
maintainer
ship
and
you
as
an
end
user,
should
know
what
that
means
and
how
that
could
impact
your
implementation
or
your
use
of
this
project,
and
is
that
enough?
Or
is
it
more
that
the
TOC
is
trying
to
get
at
so
I.
G
Wonder
if
we
should
go
ahead
and
jump
start,
some
work
around
the
tagging
stuff
that
DIMMs
laid
out
and
defining
some
of
that
too,
because
that
could
be
good.
That
could
be
a
good
next
goal
for
the
next
TOC
meeting,
which
isn't
this
next
Tuesday,
but
it's
the
following
Tuesday.
So
we
could
present
like
hey,
we've
evolved
kind
of
here's,
some
here's,
some
badging-
that
might
help
with
some
of
that
hold
on
yeah.
F
And
I
also
think
it's
a
good
kind
of
like
there's
that
education
piece
that
we
could
be
doing
for
you
know
CTF
members
and
users,
people
who
are
just
interested
in
the
cloud
native
space
in
general
of
like
well.
It
actually
applies
beyond
cloud
Nate,
it's
kind
of
like
all
open
source
of
like
when
we
say
a
project
is
single
maintainer,
multi-org
maintained
or
whatever,
like
kind
of
what
that
means,
and
you
know
this
considerations
that
you
should
think
through
before
you
adopt
this
particular
project.
F
I
mean
ultimately
it's
open
source
right
so
like
if
somebody
if
I
use
something
and
a
maintainer
just
decides
like
I'm
out
of
here,
like
I,
can
always
still
get
the
code,
but
it's
just
an
understanding
of
like
you
know,
unless
you're
willing
to
do
it
yourself.
At
that
point,
you
know
more
features
are
coming,
so
I
think
we
just
need
to
make
that
you
know
clear
kind
of
educate
folks
on
what
the
expectations
should
be
and
I
think
that's
like
a
good
thing
to
have.
G
Right
and
anybody
else
have
anything
for
governance
that
they're
working
on
looking
at
the
time
we
have
lost
in
one
minute,
just
be
quickly
anything
governance.
There
is
lots
to
do
there
all
right,
and
the
next
thing
is
just
approving
a
PR.
It's
our
only
outstanding
PR,
it's
where
we
can
put
our
resources
and
our
links
and
what
we
find
I
just
pre-populated
it
with
just
a
few,
so
you
can
see
where
I
was
going
with
this
that's
this
is
actually
not
all.
I
have
probably
a
lot
more
links
than
this
to
add.
G
So
if
someone
could
give
me
a
review
on
that,
but
that
does
not
need
to
be
live
on.
This
call.
There's
also
going
to
be
a
charter
revision
go
today
and
that
charter
revision
is
going
to
take
away
everything
that
we've
extract
from
the
roadmap.
Add
in
a
lot
of
the
stuff
that
we've
already
talked
about
today
also
add
in
Steven
as
chair,
and
do
a
couple
of
other
help.
Skiing
bits,
of
course,
we're
gonna.
Do
the
charter
revision
route,
which
is
to
get
it
approved
by
TOC
as
well?