►
From YouTube: CNCF SIG Contributor Strategy 2020-09-10
Description
CNCF SIG Contributor Strategy 2020-09-10
B
C
D
E
D
D
B
I
J
D
All
right
so
today
we
are
collectively
crossing
at
least
four
streams,
so
I'm
gonna
give
everybody
some
context,
because
everybody's
kind
of
here
on
maybe
sort
of
different
sort
of
different
offshoots
of
the
same
topic
of
maintainer
events,
amanda
and
others
are
here
because
of
the
maintainer
track,
specifically
at
kubecon
mainta
amanda,
and
I'm
going
to
give
amanda
the
floor
in
a
second.
But
amanda
came
and
said
that
in
a
in
a
feedback
session
to
cncf
that
it's
a
lot
for
maintainers
to
do
now
virtually
to
get
them
prepped.
D
D
So
there's
a
lot
of
different
kind
of
ideas
and
then
there's
also
the
maintainer
circle,
which
is
in
this
group,
which
the
intentions
are
obviously
learning
and
training
and
camaraderie
of
maintainers
on
some
kind
of
like
quarterly
cadence
and
then
now.
There's
also,
this
idea
of
what,
if
we
just
throw
a
cncf
contributor
summit
and
a
lot
of
contributor
project
or
a
lot
of
cncf
projects,
are
asking
me
for
this
because
they
don't
they
see.
D
D
So
why
don't?
We
start
with
the
mate,
since
we
have
a
lot
of
cncf
people
on
the
line
and
abandoned?
Let's
talk
with,
let's
talk
about
the
maintainer
track,
specifically
now
that
you
know
kind
of
all
of
that
stuff
amanda.
Do
you
want
to
take
the
floor
and
talk
talk
a
little
bit
about
the
very
specific,
your
very
specific
use
case
that
you
brought
to
cncf
that
day.
G
Sure
so
I'm
I've
seen
where
we
went
from
a
in-person
event
and
where
the
maintainers
I
have
maintainers
that
run
across
several
projects
and
where
they
just
needed
to
show
up
to
a
booth.
You
know
the
logos
were
all
printed.
They
just
showed
up
and
answered
questions
like
we.
You
know
it
was
a
q,
a
bar
at
one
time
it
was
an
answer,
there's
lots
of
names,
but
they
would
show
up
and
then
answer
everybody's
questions.
G
And
then,
when
we
went
to
virtual
it
was
here's
a
login
to
create
your
own
virtual
booth,
and
you
need
to
you
know
basically
either
find
somebody
to
upload
all
this
content
for
you
or
as
a
maintainer.
You
need
to
go
through
and
create
a
virtual
booth,
and
so
what
we
found
was
that
you
know
the
skills
and
the
expertise
that
are
needed
to
put
up
a
virtual
booth
is
a
different
skill
set
than
maintainers,
and
so
that's
one
of
the
items
that
that
we
ran
into.
G
We
also
ran
into
the
office
hours
where
you
know
kind
of
trolls
came
through
and
started
playing
video
games
and
they
weren't
locked
down,
and
you
know
then
other
zoom
zoom
links
had
to
be
sent
out.
So
we
ran
into
that
as
well.
So
that
was
our
experience
with
both
the
virtual
booth
and
then
the
zoom
office
hours,
and
then
in
the
slack
we
ran
into
that
it
was
just
you
know,
every
anybody's
game
in
this
in
the
slack
and
we'd.
G
The
maintainers
that
I'm
representing
here
would
appreciate.
More
of
you
know
either
like
a
q,
a
type
time
where
people
could
show
up-
and
you
know
all
be.
You
know,
conversing
about
a
certain
things
or
more
moderation
to
make
sure
that
everything
you
know
was
getting
answered
from
the
projects
or
maybe
splitting
some
things
out
a
little
bit,
but
just
more
help
for
them.
So
they
didn't
feel
so
on
point
and
needing
to
have
all
this
expertise
in
order
to
come
to
virtual
kubecon.
D
C
I
agree
it's
a
lot
to
me
like
just
you
put
on
and
even
like
show
up
for
a
virtual
event
and
doing
them
every
day.
Now,
basically,
essentially,
you
know
like
for
an
hour
at
a
time
here
and
there
it
is
a
high
bar
to
clear
and
when
it
is
such
not
chaos,
but
just
like
everything's
slower
now,
right,
like
everything
is
just
requires
more
work.
It
seems
like
so
adding
more
burden
to
an
already
burdened
person
is
just
gonna
crack
them
right.
So
that's
my
concern,
so
I'm
here
to
help
with
that.
C
D
B
Yeah,
I
think
most
of
you
have
heard
my
take
on
this
in
bits
and
pieces,
but
I'm
you
know
our
our
model
of
let's
combine
everything
because
everybody's
going
to
be
in
person
in
this
one
city
at
this
one
time
and
that's
how
we've
built
all
of
our
infrastructure
around
events,
and
I
I
really
think
that
needs
to
change
in
the
virtual
environment.
Stuffing
everything
together
makes
it
harder,
not
not
easier,
and
so
I
think,
the
more
bits
we
can
pull
out.
K
C
I
I
D
Yeah,
I
think,
from
a
content
creation
perspective.
I
think
that's
where
we're
like
kind
of
I
mean
we
were
already.
I
mean
honestly
before
the
we
even
hit
virtual.
I
think
our
maintainers
were
burned
out
of
kubecon.
I
mean
that's
just
like
the
honest
truth,
because
most
of
our
maintainers
are
doing
main
stage
tracks
with
their
employers,
probably
a
workshop,
probably
some
kind
of
contributor
summit,
an
intro
and
a
deep
dive.
So
most
maintainers
have
like
five
sessions
at
kubecon,
which
is
pretty
much
like
three
weeks
of
their
life.
Doing
content
planning.
D
And
that's
just
not
yet
I
totally
agree
with
that.
So
that's
why
I'm
like
I'm
wondering
and
then
and
that's
what
I'm
saying
like
with
the
addition
of
like
a
maintainer
circle,
where
we
have
regular
cadence
meetings
and
then
possibly
with
the
addition
of
a
contributor
summit
like
I
feel
like
there's
other
avenues
where
we
could
probably
take
this
so
that
it's
not
all
cube
con.
D
I
do
want
to
give
some
some
folks
some
some
other
context
too,
and
this
is
what
tim
pepper
was
talking
about
in
slack,
and
this
is
something
we
have
you
know
obviously
taken
much
care
to
analyze,
but
essentially
like
at
one
point
in
time.
Openstack
had
split
their
conference
from
developers
to
users,
but
again
this
is
in
person.
D
G
G
Reach
out,
you
know,
and
so
I
think,
there's
some
people
on
the
phone
who
are
like
okay,
we
need
to
know
like
what
what
stuck
and
what
didn't
right,
but
we
can't
go,
ask
cncf
for
a
big
update,
it's
all
individuals,
so
then,
now
we're
asking
them
to
track
an
email.
So
I
think
it'd
be
a
good
idea
to
get
all
of
the
things
down
that
we
that
we're
asking
them
and
seeing
if
we
can
streamline
some
things
to
make
it
easier.
G
G
This
is
insane,
but
like
a
hundred
thousand
dollars
and
make
xyz
project
booth,
like
you
know,
have
fireworks
coming
out
of
it
and
what
I
liked
about
you
know
the
in
person
was
that
it
was
just
like
a
logo
you
put
it
up
top
and
that
you
know
everybody
was
seeing
all
the
projects
were
seen.
You
know
as
equal.
Yes,
there
are
some
that
are
graduated
versus
incubating
and
there
was
a
difference
there,
but
it
was
more
of
equal.
G
G
So
maybe
streamlining
some
things
and
then
paris
to
your
point
about
breaking
some
things
out.
I
do
worry
that
getting
people
to
spend
like
if
it
was
small
chunks
of
time
on
certain
days
or
something
like
that.
I
think
that
would
be
okay,
but
I
think
asking
people
to
take
two
weeks
off
of
two
weeks
off
of
work
to
go
to
virtual
events
that
are
the
maintainers
that
might
get
tricky
inside
a
company.
D
C
G
They
had
virtu,
they,
they
had
virtual
booths
that
you
had
to
like
upload
content
to
you
had
the
staff
for
like
10
hours
a
day.
That
might
be
an
exaggeration.
I
don't
think
it
was
10
hours,
but
maybe
it
was
you
know
you
had
to
do
things
you
had.
You
know
people
uploaded
like
killer
videos,
and
you
know
people
did
kind
of
go
all
out
in
some
areas.
A
From
maintainers
it
was
different
software,
it
wasn't
slack
it.
It
worked
differently
than
slack
like
they
had
to
refresh
the
page.
Every
three
seconds
to
check
people
came
there.
There
was
definite
overhead
to
using
it
compared
to
other
things.
Yeah,
I
don't
know
it
wasn't
it
wasn't
easy.
It
definitely
required
a
lot
from
people
to
use
the
feedback.
I
got
was
overwhelmingly
negative,
but
I
won't
speak
for
them.
I
Do
you,
as
a
group,
feel
that
hosting
a
virtual
booth
from
a
maintainer
standpoint
in
this
setting
is
actually
the
right
approach?
That
could
be
something
very
easily
that
we
take
off
the
table
and
have
more
heavy
emphasis
on
the
project
office
hours
where
they
jump
on,
maybe
not
zoom,
because
we
did
have
issues
with
zoom
but
some
other
platform
that
allows
attendees
to
get
on
and
ask
questions
in
that
hour.
Those
seem
to
be
highly
successful
from
what
we
were
tracking
on
our
end
and
just
eliminate
the
booth
in
general.
I
At
this
point-
and
you
know
in
that-
that
channel
of
the
project
office
hours
we
can
send
out-
and
when
I
say
we,
you
know
the
linux
foundation,
events
team
can
send
out
a
message
to
everyone
who's
on
the
call
that
includes
you,
know
the
project,
slack
channel
or
github
or
whatever
other
ways
for
them
to
continue
to
engage
with
the
maintainers
after
that
hour
has
concluded
where
to
get.
You
know,
content
all
that
information
as
long
as
we're
provided
it,
we
can
send
it
out
and
we
can
create
that
checklist.
I
C
L
D
C
D
H
I
H
I
H
I
just
think
the
the
introduction
to
a
project
can
be
kind
of
shortened
as
much
as
possible.
Essentially
you
want
to
give
an
introduction
to
a
project
and
then
we
have
a
deep
dive
anyway
and
then,
if
you
want
to
dive
even
deeper
and
talk
to
the
maintainers,
we
have
the
office
hours.
So
it's
kind
of
like
a
stepping
stone.
D
G
J
E
C
L
D
Well,
I
mean
that's
not
off
the
table,
I
mean
the
the
off
the
table
is
at
cube
con.
I
think
everybody
on
this
call
said
no
maintainer
circle
at
cubicon,
so
no
maintainer
circle
at
cubecon.
I
wanted
to
mention
that
because
I
feel
like
a
lot
of
this
time,
like
a
lot
of
this
content,
can
come
out
at
maintainer
circle
as
well,
and
then
the
second
thing
that
was
discussed
and
has
been
discussed
by
other
maintainers
is
contributor
summits
and
that
they
want
they
want
contributor
summits.
D
There
is
no
timing,
I
I
hear
there's
you
can
even
see.
I
can
even
send
you
some
some
tweets
from
some
angry
maintainers
last
year
who
who
want
more
content
during
kubecon,
there's,
just
not
an
any
really
maintainer
content
outside
of
like
intros
and
stuff,
like
that,
meaning
there's
no
opportunities
for
them
to
grow
as
individuals
and
they
feel
like
kubernetes
gets
all
that
love
because
we
give
that
to
them
because
we
have
a
sig.
D
That
does
it
so
you
know
at
home
and
karen
and
that
crew
like
they
have
somebody
dedicated
so
and
you
know,
like
amanda,
I'm
just
giving
some
examples,
but
anyway
like
how
would
that?
What
would
that
look
like?
Would
we
serve
that
at
cubecon
when
we
serve
it,
not
at
cubecon,
like
all
that
stuff
is
in
the
air
like?
This
is
just
ideas
of
people
who
are
starving
for
this
type
of
content
and
like
want
that
camaraderie
piece
at
kubecon.
D
L
For
what
it's
worth,
I'm
actually
talking
with
both
kubevert
and
cryo
about
doing
their
own
contributor,
advanced
user
summit
things,
but
for
both
of
those
projects,
they've
specifically
requested
that
we're
going
to
be
doing
it
at
least
a
week
away
from
kubecon.
If,
if
not
a
month
away,
it's
like
they
specifically
don't
want
to
overlap,
because
they
don't
think
people
are
going
to
be
able
to
pay
attention.
K
So
for
home
we
are
thinking
of
doing
you
know
like
a
half
day
like
all
hell
day
event,
so
we
haven't
decided
on
the
timing
of
it,
but
like
we're
trying
to
figure
out
like
if
it
makes
sense
to
do
something
soon,
as
like
a
follow-up
to
kubecon,
as
in
to
like
kind
of
bring
in
all
the
people
that
were
introduced
to
home
from
kubecon
europe
or
do
something
similar
to
the
other
projects.
That
would
be
like.
K
L
L
D
A
All
that
stuff,
you
just
said
for
the
extra
things
that
aren't
specific
to
a
project.
If
you
okay,
so
I
have
a
question
you
just
said
before
people
you
were
saying
angry
tweets
about
maintainers
who
want
content
directed
for
them
during
kubecon.
Did
I
entertain
you
right
like
if
that
content
was
available
during
kubecon?
A
That's
what
I
would
go
to
like.
I
don't
really
want
to
go
to
the
things
about
the
projects
anymore
because
I'm
usually
oh
like
I
know
that
stuff,
but
I
would
go
to
every
single
one
of
the
things
you
just
said,
and
I
bet
a
lot
of
them.
Maintainers
would
want
to
as
well,
but
if
they
were
competing
with
me
doing
my
contributor
summit,
that
would
be
incredibly
frustrating
to
miss
those.
A
L
D
The
other,
then
this
was
the
other
idea
that
we
brought
up
to
the
kubecon
chairs,
which
was,
let's
just
completely
redo
the
maintainer
track.
Let's
just
uphold
like
let's
just
upheaval
it
and
serve
contributor
related
contributor
summit,
related
content
on
the
maintainer
track
and
also
have
some
like
some.
You
know,
sig
updates
and
things
like
that.
So
that
was
the
other
idea
and
I
think
that
was
also
shot
down.
But
me
I'm
hearing
that
all
the
time
like
carolyn's
use
case
that
she
just
mentioned.
That's
all
I
hear
y'all.
D
C
G
Do
we
have
ambassadors
for
other
projects?
Are
there
other
people
that
we
can
tap
or
lift
them
up
in
the
community
to
help
here?
Is
there
like
another
program
where
we're
not
you
know
where
we
can
uplift
people
get
more
visibility
from
people,
but
also,
like
you
know,
get
more
content
not
from
the
same
people,
but
on
that
on
this
topic,.
D
D
We
would
be
able
to
run
like
eight
different
content
sessions
or
something
like
that,
whereas
like
to
get
those
like
what
I
meant
like
the
stuff
that
I
mentioned,
like
inclusive
language,
inclusive
meetings,
all
that
stuff
like
that,
would
take
us
like
a
year
just
to
just
to
do
one
like
a
maintainer
circle.
So
this
is
just
rapid
fire
content
that
I
was
thinking
about.
That
could
be
served
from
a
maintainer
perspective,
but
you
know
a
lot
a
lot
of
thoughts.
I
G
D
All
right,
let's
go
into
regular
sig
updates,
cncf
folks,
if
y'all
don't
want
to
listen
to
this
boring,
stand-up
kind
of
thing
feel
free
to
jump.
Otherwise
you
can
also
hang
out,
but
let's
get
into
what's
going
on
in
some
of
our
working
groups.
If
that's
cool,
why
don't
we
start
off
with
the
anonymous
dingo?
Who
is
josh
burkus
in
the
in
the
the
doc?
L
L
I
need
to
actually
circle
back
with
liz
rice
and
find
out
what
the
toc
is
expecting
from
us
on
that,
because
we
already
gave
them
feedback
about
our
position
on
steering
committees,
namely
that
they're
good
for
some
projects,
but
we
don't
recommend
them
being
a
requirement
the,
and
so
I
don't
know
what
else
the
toc
is
looking
for
in
that.
So.
E
I
can
step
in
for
some
of
that.
It
looks
like
we're
going
to
be
scheduling
that
meeting
for
the
end
of
september,
because
not
everybody
can
make
it
to
the
15th
and
I
think
it's
just
being
able
to
come
and
have
a
conversation
about
here's
our
position.
Here's
why
we
have
it.
Here's
some
other
things
that
maybe
we
should
consider.
L
Review
thing
annual
report
thing
that
sort
of
thing
to
see
what
was
already
there
in
terms
of
badge
material.
The
only
other
sort
of
useful
thing
I
got
out
of
it
was
just
that
osi
conference
is
going
on
right
now
and
somebody
actually
did
a
thing
on
badges,
which
was
interesting,
so
you
know
plan
to
incorporate
that
you
know
where
they
actually
said
that
you
really
need
to
limit
the
number
of
badges
or
they
lose
their
value.
L
D
And
context
for
new
folks
is
cncf.
Graduation
requirements
say
different,
like
open
governance
and
stuff
like
that,
and
certain
projects
might
need
steering
committees
and
so
now
cnc
the
toc
is
getting
into
thinking
about
like
what?
What
does
that
look
like
for
the
requirement
should
we
require
like
if
you,
if
you
don't
have
xyz,
then
you
have
to
have
a
steering
committee
and
then
dims,
like
the
white
knight
that
he
is
came
in
and
said
well
what
about
this
badging
idea
and
like
here?
D
It
is
in
openstack
and
like
just
the
badging
idea,
is
just
letting
the
end
user
know
what
kind
of
governance
that
you
have,
which
is
a
neat
idea,
and
then
it's
not
necessarily
prescribed
it's
more
like
on
the
end
user.
To
look
and
see
and
good
news
is,
I
invited
bogdan
who
was
at
the
who
did
the
talk
to
our
crew
to
come
and
talk
about
badging,
so
we
have
logged
in.
Hopefully
next,
not
this
not.
D
Also
on
the
badging
note,
it
was
in
it's
in,
like
the
latest
change
log
with
nadia.
She
talks
about
taxonomies
and
the
need
for
categorization
of
governance
and
and
community
groups,
and
things
like
that.
It's
just
literally
all
on
the
same
topic.
So
I
feel
like,
if
any,
if
it
gave
us
anything,
it
gives
us
validation
that
we're
all
on
the
right
page,
so
cheers
all
right,
contributor,
gro!
Well,
actually
any
questions
about
governance
or
anybody
want
to
probe
governance.
D
B
D
A
Sure
I've
actually
been
drowning
and
haven't
been
able
to
make
the
last
couple
meetings
like
I
was
on
vacation
last
week.
So
is
anyone
here
last
week
actually
can
help
out
updating?
What's
going
on
I'm
celebrating
burnout
month
to
be
honest,
like
full
transparency
burn
out
five
months,
so
my
burnout
month
is
going
well.
My
project
just
got
accepted
into
the
cncf,
so
I'm
like
a
real
cncf
person.
Now,
instead
of.
E
D
D
Yeah,
no,
we
were
it
was.
It
was
quiet
amy
and
I
had
gotten
on
the
line
and
different
at
different
intervals,
and
I
was
like
I
was
like
all
right,
good
good.
I
got.
I
got
another
couple
minutes
back
all
right,
I'm
gonna,
I'm
actually
gonna
share
my
screen,
so
we
can
look
at
don's
pr
great
hold
on
a
moment
in
context
for
folks
online
hold
on.
Let
me,
oh
god,
which
screen
am
I
sharing?
Oh
no.
D
All
right.
I
want
to
get
fired
yet
y'all,
so
context
dawn.
I
I'd
asked
dawn
to
help
me
with
this
because
I
know
dawn's
an
expert
in
this
area.
A
lot
of
the
projects
take
things
very
literally
right.
So
as
far
as
graduation
requirements
are
concerned,
the
one
requirement
is
like
you
know,
must
demonstrate
project
health
and
you
know
good
standing,
blah
blah
blah.
B
Yeah
absolutely
so,
as
we
know,
all
projects
are
a
little
bit
different,
they're
at
different
stages
in
the
the
life
cycle
of
the
cncf.
They
have
different
needs.
They
have
different
wants.
So
what
we
tried
to
do
was
give
people
some
ideas
for
how
they
could
measure
the
health
of
their
project
without
being
super
prescriptive
about
this
is
this
is
exactly
what
you
have
to
do
and
how
you
have
to
do
it
it's
more
about.
B
You
know,
responsiveness
is
important,
you
should
you
know
reply
to
things
in
a
timely
manner,
and
here
are
some
links
to
some
areas
in
dev
stats,
where
you
can
look
at
that,
and
you
can
measure
it,
and
so
so
that's
kind
of
the
the
measurements
section
and
if
you
want
to
just
scroll
down
there's
some
different
areas:
contributor
activity,
same
thing,
contributor
risk
which
is
kind
of
bus
factor
slash.
You
know
somebody
wins
lottery
whatever
they're,
no
longer
working
project,
velocity
release,
activity,
inclusivity,
and
so
these
are
all
just
kind
of
the
big.
B
Some
of
the
big
buckets
that
I
like
to
think
about
when
it
comes
to
project
health,
and
then
we
included
just
a
few
best
practices.
So
you
know
picking
picking
a
reasonable
window
to
measure
it
in
whether
you
measure
the
whole
project
at
once
or
a
repository
group.
The
way
kubernetes
does
there
are
lots
of
different
different
options.
So
what
we're
trying
to
do
is
provide
people
with
lots
of
different
options
that
they
can
use
to
do
the
right
thing
for
their
project
and
as
with
all
of
our
resource
docs.
B
A
B
D
All
right
and
don't
forget,
we
also
have
the
resources
file
in
there.
So
if
you
have
any
other
like
link
linkable
resources
that
are
good
for
projects
or
for
even
for
us
for
research
with
governance
topics,
any
kind
of
maintainer
topic-
that's
also
in
the
repo
for
for
us,
don't
forget
and
that's
pretty
much
it.
Anybody
have
anything
else.
D
All
right,
I'm
calling
it
if
no
one
has
anything
else
all
right,
so
we
got
a
lot
of
action.
Cncs
going
to
come
back
to
us
with
summaries
and
feedback.
Don't
forget
to
oh,
I
know
josh
you're,
talking
don't
forget.
Tuesday
is
working
group
for
governance
as
well
as
contributor
growth.
So
that's
where
we'll
like
try
to
do
some
of
this
work.
Josh
go
ahead.