►
From YouTube: CNCF Contributor Strategy Governance WG 2020-11-11
Description
CNCF Contributor Strategy Governance WG 2020-11-11
A
A
Not
too
bad,
that's
bet
back
to
work,
so
everything
is
fine.
How
about
you.
B
Okay,
the
the
nice
thing
about.
B
B
C
D
Yeah
it's
funny.
I've
started
having
this
weird,
like
online
conference
stress
because,
like
the
day
or
two
before
the
conference,
I
feel
like
I
should
be
preparing
more,
but
I
don't
need
to
because
I
did
the
presentation
weeks
ago,
and
so
I've
got
this
like
weird
feeling
that
I've
forgotten
to
do
something.
B
B
B
B
B
I
did
this
thing
a
while
ago,
where
I
was
going
to
move
from
one
password
to
bit
warden
and
then
in
the
middle
of
it
one
password
started
offering
free
password
keeping
to
the
kubernetes
project,
so
I
decided
not
to
move,
but
now
I've
got
like
half
wait.
B
A
It's
currently
recorded
so,
okay,
I
mean
amy,
should
take
care
of
it.
Okay,.
B
Anyway,
welcome
to
the
governance
working
group
meeting
for
november
10th,
the
it
as
usual
under
the
cncf
code
of
conduct.
But
all
of
you
know
that
I
did
actually
invite
a
couple
of
projects
who
had
had
governance
questions
to
come
by
this
meeting.
But
we
will
see
if
they
do.
B
D
B
The
goal
was,
I
took
two
of
the
most
common
types
of
governance.
Right,
one
is
like
straight
up:
maintainer
council,
one
and
the
other
one
is
simple,
is
steering
committee
elections
and
I
tried
to
come
up
with
the
simplest
most
generic
version
of
each
one
of
those
as
a
as
a
starting
point
for
projects.
B
The
third
one
that
I
wanted
to
do,
which
is
another
common
type,
is
your
sort
of
composite
or
subproject
amalgamation,
where
you
have
multiple
sub-projects
and
then
there's
a
leadership
council,
that's
composed
of
the
leaders
of
the
subprojects,
but
I
haven't
honestly
been
able
to
find
a
good
example
of
that
to
start
from,
and
my
goal
for
these
was
to
not
come
up
with
a
wholly
synthetic
example
that
wasn't
even
similar
to
anything
anybody
had
adopted,
because
I'm
not
sure
it
would
be
useful
right
because,
like
I
know,
the
maintainer
council
one
is
useful
and
I
know
the
elections
one's
useful
because
they
are
both
derived
from
charters.
D
B
Oh
okay,
yeah!
I
could
do
that
and
see
if
she
yeah.
If
she
actually
knows
those.
I
was
also
going
through.
Obviously,
a
bunch
of
the
cncf
ones
and
a
couple
of
the
cnc
projects
basically
do
have
that
sort
of
general
form,
but
they
have
it
in
such
a
complicated
because,
like
I
started
off
basing
something
on
the
prometheus
starter,
and
I
realized
that
the
prometheus
thing
was
so
complicated,
in
particular
to
the
prometheus
project
that
it
wasn't
going
to
genericize.
Well,.
B
The
and
I
don't
know
we'll
see
I've
been
the
network
tools.
Working
group
for
for
cncf
has
been
talking
about
actually
becoming
a
project
as
well
as
a
working
group,
and
if
they
do
that,
then
they
will
have
that
form
of
governance
governance.
So
maybe
I'll
have
the
chance
to
write
one.
But
in
the
meantime
I
don't
expect
to
get
one
ready
for
kubecon.
B
B
And
I'm
hoping
to
get
that
finished
before
next
week,
and
this
is
basically
just
this
paperwork
with
a
paragraph
of
description.
You
know
with
the
idea
that
at
some
point
we
will
have
examples
or
templates
for
most
of
those
things.
D
B
B
D
B
I
I
have
the
advantage
that
pretty
much
everybody
that
I
work
with
is
going
to
be
involved
with
kubecon.
So
I
expect
most
of
my
regular
meetings
next
week
to
be
cancelled
by
other
people.
B
The
very
true
so
it's
already
the
case
that
that
I'm
not
hearing
from
anybody
at
the
cncf
except
right
now
how
you
are.
B
The
so.
B
B
Well,
we'll
get
that
when
we
have
a
web
page,
I
guess
because
carolyn's
been
working
on
the
contributor
webpage
and
I
think
one
of
the
things
that
we
can
do
once
we
have,
that
is
put
up
the
schedule
of
meetings
for
this
so
that
people
know
oh.
B
Up:
hey
charles
you
did
you
come
here
with
questions?
Are
you
showing
up
to
help.
E
B
Yeah
not
a
whole
lot
well,
one
of
the
things
I
actually
wanted
to
mention
here
is
just
so
people
know
the
so
after
that
whole
long
discussion
with
the
toc
about
steering
committees
and
alternate
ways
to
approach
the
multi-organizational
requirement
for
projects
for
graduation
etc,
we
do
not
have
a
clear
mandate
for
anything.
They
want
us
to
prepare.
E
B
There
was
a
suggestion
that
somebody
tried
to
draft
requirements
that
target
more
the
actual
critical
elements
you
know,
survivability
and
ensuring
that
contributions
are
welcome
regardless
of
source
the,
but
the
toc
never
took
a
vote
or
even
a
lazy
consensus
to
say
that
was
the
direction
they
wanted
to
go
in
so
so
that
remains
unchanged,
probably
to
be
an
item
of
discussion
again
at
some
point
in
the
future
and
in
the
meantime
we
will
continue
to
work
with
projects
on
becoming
multi-organizational
for
graduation.
E
Cool,
what
was
the
website
you're
just
mentioning,
because
that's
something
that
I
can
is
there
are
there
is
an
open
source.
B
Yeah,
so
yes,
yes,
there
is
so
hold
on.
Let
me
get.
B
B
B
The
yeah
I
kind
of
I
mean
I
do
admit
that,
and
this
is
really
more
for
the
general
meeting,
that
having
one
website
called
contribute.cncf.io
and
the
second
one
called
contributors.cncf.io
be
problematic.
A
B
Because
people
would
never
remember
to
distinguish
the
two
of
them.
The.
A
A
A
I'm
happy
to
help
with
this
I'm
happy
to
help
with
this
from
the
cnc
side.
If
something
will.
B
A
B
Yes,
the
answer
would
be
since
carolyn's
leading
this
effort
to
go
ahead
and
coordinate
with
her
in
that
and
then
maybe
give
us
the
ability
to
push
things
to
the
contribute
site.
I
guess
the
question
is:
if
we
change
the
path
of
stuff,
that's
on
the
contribute
site.
What
are
we
going
to
break.
B
B
A
Yep,
exactly
what
we
can
do,
we
can.
We
can
move
this
branch
from
c
contributor
strategy,
ripple,
move
it
to
to
the
contribute,
repo
and
point
both
domains
to
to
the
netlife
to
the
netlify.
Our
website.
That's
that's!
It.
B
B
B
I
don't
think
it's
that
much
of
a
problem,
but
we
don't
want
to
do
it.
You
know,
without
discussing
it
and
without
potentially
at
least
posting
a
warning
on
cncf
slack
in
the
toc
thing.
B
Yeah,
so
that's
the
thing,
and
the
idea
here
is
that
that
will
become
our
publication
target
for
a
lot
of
our
advisories
and
guides
and
everything
else.
Everything.
That's
not
a
template,
that'll
go
into
that
website
and
then
you
know
so
we'll
have
some
kind
of
process
whereby
stuff
gets
approved
to
go
on
to
the
website.
B
Ideally,
you
know
once
we
get
that
set
up,
I'm
gonna
solicit
the
toc
to
authorize
a
liaison,
probably
matt.
I
guess,
if
he's
still
on
the
toc
I've
lost
track,
but
at
toc
liaison
to
approve
our
decisions
there
rather
than
having
everything
come
up
for
a
full
toc
vote,
because
if
we
have
to
have
a
full
toc
vote
every
time
we
want
to
publish
an
update
to
a
document.
It's
going
to
be
real,
slow.
B
B
B
E
Through
them-
and
these
aren't,
these
aren't
like
live
anywhere
right.
I
have
a
markup
renderer
that
I
can
use
just
curious
if
it's
live
somewhere
that
I
can
read.
B
No,
the
pr
hasn't
been
word
merged,
yet
okay,
cool
vm
and
you
actually
kind
of
need
to
look
at
the
raw
because
they're
designed
to
be
templates
for
markdown
documents
and
there
is
no
markdown
template
language,
so
the
so
there's
a
bunch
of
stuff
in
there.
That's
actually
invisible.
If
you
look
at
it
as
rendered
markdown.
B
Yeah
and
just
more
I'm,
you
know
looking
at
hey
what
is
this
actually
going
to
be
useful
to
people
like?
I
think
it
is
based
on
dealing
with
some
of
the
red
hat
projects,
but
more
eyes
is
good.
Okay,.
B
Cool,
how
did
the
linker
d
anchor
launch
go.
E
Good
we've
got
a
few
folks
interested
already
and
we're
finding
ways
to
get
them
kind
of
talking
to
each
other
as
well.
So
yeah
catherine
will
definitely
be
chatting
about
that
this
afternoon.
Yeah.
We
got
some
interest
straight
away
and
we
also
reached
out
to
folks
who
we
knew
were
already
basically
like.
E
B
Yeah,
particularly
without
in-person
events,.
B
The
because,
like
we,
have
a
couple
of
projects
that
have
deferred
launching
new
ambassador
programs,
simply
because
without
having
in-person
events,
there's
not
that
much
for
the
investors
to
do.
E
That's
interesting,
yeah
we're
focusing
on,
like
your
people,
become
ambassadors
or
anchors
based
off
of
content
that
they're
generating
you
know,
and
it's
kind
of
the
way
we've
approached
it
is
we.
We
know
that
you're
integrating
linker
d
with
xyz,
let's
write
a
blog
post
about
that
and
share
it
with
folks
or,
let's,
let's
put
together
a
tutorial,
you
know
the
difference
between
a
blog
post
is.
E
This
is
what
we
did
and
why
we
did
it
and
the
tutorials
like
step
by
step
by
step,
because
just
from
my
position
of
working
with
the
community,
I
see
people
asking
similar
questions
but
they'll
happen
like
three
and
four
weeks
apart
and
I'm
like
oh,
I
know
somebody
just
asked
that
they
might
know,
and
then
we
have
the
free
version
of
slack.
So
I
I
can't
go
back
very
far
to
find
the
answers
that
I'm
looking
for
so
but
yeah,
it's
we're
iterating
over
it.
E
It's
pretty
exciting
and
yeah
catherine's
been
doing
a
lot
of
the
thinking
most
of
the
thinking
around
it.
So
I'm
excited
to
for
her
to
share
with
you
what
she's
come
up
with.
D
Yeah,
I
think
that's
a
really
good
approach.
I
think
it's,
I
think
it's
probably
healthy
for
us
now
to
take
sort
of
a
step
back
and
think
of
not
always
think
of
ambassadors.
It's
just
the
people
who
fly
around
to
all
the
conferences
and
give
all
the
talks.
I
mean,
there's
other
other
ways
to
be
an
ambassador
that
don't
involve
spending
all
of
your
time
on
a
plane.
A
A
These
days,
so,
however,
drop
warehouse
ways
how
you
can
contribute
to
to
the
open
source
world,
even
not
flying
to
different
conferences
and
speaking
there
like
write
a
blog
post
or
publish
even
you
know,
publish
some
books
run
or
speak
at
the
podcast
like
be
engaged
in
the
community,
be
be
active
with
your
local
community
in
the
online
or
you
know,
on
online
or
offline
way
like
even
drug.
There
are
some
ways:
how
can
you,
how
can
you
work
with
the
local
community
so
definitely
ability
to
speak
at
the
global
events?
E
Here,
yeah,
that's
that's
where
we
didn't
even
consider
like.
B
E
On-Site
events
as
part
of
our
strategy,
we're
focusing
on
doing
as
much
as
we
can
virtually
and
we've
also
we're
working
internally
to
have
like
one
member
of
the
team,
generate
one
piece
of
content
once
a
month
right.
So
that
gives
us,
if
only
if
only
our
team
is
doing
it.
That
means
for
the
next
two
years
we
will
generate
one
piece
of
content
per
month,
which
is
way
lower
than
we
want
it
to
be,
but
that's
just
internally.
E
So,
if
we're
getting
folks
externally
we're
hoping
to
have
two
to
three
pieces
of
content
per
month,
and
that's
the
thing
well
this
this
actually,
this
question
might
be
better
in
one
of
the
other
groups.
But
the
thing
that
I
personally
am
seeing
is,
I
feel,
like
people
are
getting
fatigue
from
virtual
conferences,
so
my
focus
is
to
generate
content
that
they
can
consume
on
their
time.
Whether
that
again
is
it's
either
an
article,
a
blog
post
or
a
video.
E
E
And
I
think
it's
a
function
of
this
is
a
forcing
function.
Actually,
so
we
need
to
start
thinking
differently
and
how
do
we
get
people
give
them
interesting
things,
not
just
things.
I
don't
want
to
throw
a
bunch
of
content
out
there
that
people
aren't
interested
in
so
yeah.
These
are
like
questions
that
are
open-ended
for
us
and
that
we're
we
continue
to
try
and
answer
ourselves.
E
There
was
no
question,
it's
open-ended.
Questions
like
I
started
to
go
down
the
path
of,
if
you
all
have
thoughts
about
alternative
content,
but
then
I
realized,
I
think,
that's
a
better
just
like
open-ended
discussion
like
sit
down
and
start
throwing
things
at
the
wall
and
see
what
sticks
yeah,
but
that's
kind
of
what
we're
doing
internally,
but
there
are
other.
E
B
Yeah
and
I'll
tell
you
one
thing
so:
there's
there's
different
ways
to
do
that
for
some
projects
you
just
say:
hey:
if
you're
already,
if
you're
sort
of
an
acknowledged
anchor,
then
you
automatically
have
the
ability
to
vote
assuming
wait.
Let
me
look
at
liberty,
governance.
I
don't
think
you
have
voting
right
now.
D
E
B
Yeah,
so
so
until
you
actually
have
yeah,
you
have
basically
your
counsel
yeah,
because
I
was
looking
at
you.
If
you
maintain
your
counsel,
I
should
have
based
my
maintainer
counsel
on
yours,
because
you
have
a
ridiculously
simple
one:
the,
but
you
have
a
basic
maintainer
council
structure,
so
there
isn't
currently
any
voting.
B
So
if
you're
not
moving
to
like
an
electoral
structure
anytime
in
the
near
future,
which
there
may
be
no
good
reason
for
you
to
do
so,
my
suggestion
would
be
that
eventually,
you
actually
have
make
anchors
a
project
in
and
of
their
own
and
give
and
basically
then
create
anchor
maintainers
and
it's
a
way
to
get
people
involved
with
governance
out
of
the
anchor
program,
even
in
advance
of
them
being
code
contributors.
C
The
hey
bill-
hey
how's,.
B
The
you
came
in
a
good
time
because
we
just
finished
with
our
earlier
topics,
and
you
had
some
governance
related
questions
earlier.
C
Yeah,
I
guess
thanks
so
yeah.
I
guess
we're
starting
a
new
like
working
group
like
the
cnf
conformance
and
we
presented
to
the
tse
last
week,
and
they
said
it
might
go
under
like
sig
app
delivery,
sig
networking,
but
our
question
kind
of
is,
is
if
we
want
to
get
this
like
kind
of
before
that
happens.
C
We
want
to
get
it
kind
of
like
off
the
ground
and
running
at
kubecon
and
we're
trying
to
like
get
people
kind
of
like
in
charge
of
that,
because
right
now,
it's
kind
of
like
so
I
work
with
this
at
the
cncf
and
it's
kind
of
being
like
organized
by
us,
but
we'd
like
to
have
it
be
kind
of
like
driven
by
the
community
going
forwards
and
we'd
like
to
kind
of
have
some
like
elections,
and
I
was
wondering
if
there's
any
kind
of
like
like
advice
or
like
standard
structure
like
template.
B
Group
there
isn't,
because
the
way
that
governance
works
for
the
sigs
is
that
each
sig
has
a
certain
small
set
of
of
chairs
or
leads,
and
those
people
are
generally
selected
by
some
kind
of
rough
consensus
and
then
they're
approved
by
the
toc.
C
B
C
B
And
so
nobody
ever
felt
that
they
needed
a
more
complicated
mechanism,
for
you
know
a
more
representative
mechanism
for
selecting
leadership
as
far
as
I
know,
and
that
would
cover
which
one's
sig
networking
sig
run
time.
Sig
storage,
at
least
all
work
that
way,
along
with
our
sig.
B
So
but
as
amy
pointed
out,
the
working
group
thing
is
less
defined
and
I
guess
one
of
the
questions
is
well.
The
cncf
doesn't
require
you
to
have
any
particular
mechanism
for
selecting
leadership
and
it
requires
that
the
toc
ratify
your
leadership
changes.
They
also
don't
prohibit
you
of
having
a
more
sophisticated
mechanism.
B
So
the
question
is:
is
there
a
reason
for
you
to
have
some
kind
of
a
representative.
C
Mechanism
so
like
it,
so
is
there
a
reason
why
they
have
where
we
should
have
like
a
structure
or
like.
B
Right,
in
other
words,
we'll
having
a
more
formal
structure
for
representation,
either
engage
more
potential
participants
or
be
a
way
of
avoiding
sort
of
interminable
disputes
around
things.
These
are
the
two
reasons
why
you
adopt
a
more
sophisticated
governance
structure
is
to
do
one
of
those
two
things.
C
Yeah,
ours
is
kind
of
like
the
latter,
where,
in
the
telco
space,
there's
kind
of
like
a
lot
of
inventor
vendors
who
have
like
very
entrenched
interests,
and
we
don't
want
them
to
kind
of
like
control.
The
conversation
we
want
to
be
driven
by
like
multiple
different
parties,
especially
ones
like
the
service
providers
and
stuff,
and
so
we
don't
want
to
be
kind
of
yeah.
I
guess
kind
of
like
controlled
by
a
few
people
that
already
kind
of
control
the
ecosystem.
C
B
Like
you
know,
vendor
seats
and
service
provider
seats
and
say
even
an
end-user
seat,
with
the
complexity
always
that
it's
hard
to
define
those
things.
B
C
B
Another
suggestion
would
be
if
you're
going
to
go
through
a
complicated
election
process.
You
might
want
to
get
dispensation
from
the
toc
to
not
have
the
requirement
that
they
approve
those,
because
it
feels
kind
of
pointless
to
have
an
election.
If,
then,
the
toc
can
go
well
nah
or
simply
delay
approval,
because
they're
busy
with
other
things,
which
is
the
more
likely
problem.
C
C
B
It's
obviously
an
area
where
my
employer
has
some
definite
interest,
so
I
can
get
work
time
to
spend
on
it,
the
yeah
and
even
even,
if
I'm,
telling
how
y'all
I'm
gonna
set
things
up
so
that
you
don't
have
control
over
this,
but
that's
fine,
the
and
but
you
want
to
already
announce
a
governance
structure
at
kubecon
yeah.
That's
kind
of
ambitious,
given
that
kubecon
is
next
week
and
the
toc
would
have
to
approve
at
least
the
governance
structure.
B
Yeah,
and
the
advantage
of
that
honestly,
is
that
we
can
write
a
draft
governance
and
then
run
it
past
your
early
participants,
so
that
they
actually
can
supply
feedback
and
have
a
stake
in
the
governance
structure
that
you
end
up
with.
C
B
The
so.
C
B
So
there's
no
good
way
to
even
kind
of
get
their
blessing
on
the
idea
that
that
cnf
conformance
is
going
to
have
its
own
governance.
B
D
D
B
No
you're
absolutely
right
any
further
right
in
that.
You
need
to
look
at
what
the
outputs
of
this
governance
structure
are
going
to
be
like.
What
do
you
need
leadership
to
actually
do,
because
that
will
determine
the
structure
that
the
leadership
needs
to
take.
B
I
mean
to
give
certificate
like
if,
if
leadership's
role
is
exclusively
going
to
be
approving
conformance
rules
and
tests
right,
then
that
would
argue
for
some
sort
of
a
centralized
committee
structure,
regardless
of
how
they're
selected,
whereas
if
it's
more
that
you're
going
to
have
different
aspects
of
conformance
worked
on
in
different
sub-projects
than
that
might
argue
in
favor
of
more
composite
structure.
You
know
one
in
which
you
have
sort
of
these
sub
projects
and
then
there's
some
sort
of
counsel
from
the
subprojects
and
leadership
is
mainly
technical
in
nature.
C
B
C
B
C
So
we
I've
talked
with
like
quite
a
few
people
like
across
a
number
of
different
organizations,
so
and
quite
a
few
have
expressed
interest
in
like
being
involved
so
far.
C
B
C
B
And
for
right
now,
they're
just
you
know,
because
the
important
thing
is
to
find
out
far
more
important.
The
important
thing
is
to
find
out
who's
going
to
actually
put
people
onto
this.
C
B
D
Yeah-
and
I
think
sometimes,
but
now
focusing
on
things
like,
like
the
outputs,
and
you
know
how
you're
going
to
communicate
with
each
other
and
decision
making
processes
and
some
of
the
stuff
that
that
goes
around
the
kind
of
the
leadership
selection.
That's
a
part
of
governance,
I
think,
would
probably
be
a
better
use
of
the
time
right
now.
C
Okay,
so
get
kind
of
get
it
off
the
ground
and
running
like
with
us
running
it
and
then
once
we
kind
of
have
sorted
out
who's
actually
contributing
and
like
working
on
it
then
kind
of
like
then
that's
when
we
actually
launched,
like
the
the
formal
governance
process
like
right
now.
I
guess
for
the
time
being
saying
like
we're
kind
of
like
a
benevolent
dictator.
B
B
C
So
I
I
know
I
just
jumped
in
at
the
last
minute
here,
so
I
do
appreciate
you
taking
the
time
to
chat
with
me
today.
B
You
were
you,
were
one
of
the
people
invited
to
come
by
this
meeting
for
questions
about
governance.
So
and
if
you
look
at
the
agenda,
we
kind
of
had
the
section
of
the
meeting
unfilled.
So
thank
you
for
remembering
to
come
by.
B
Yep,
the
and.
B
Now
that's
about
it,
I
mean
when
you
actually
at
some
point
when
we
have
more
stuff
up
we're
working
on
creating
a
new
website.
I
might
ping
you
and
say:
hey.
We
now
have
a
bunch
of
government
governance
resources
online.
Tell
me
if
these
would
have
helped
you.