►
From YouTube: CNCF Contributor Strategy Governance WG 2021-03-16
Description
CNCF Contributor Strategy Governance WG 2021-03-16
C
C
Well,
the
the
previous
one
actually
ended
15
minutes
early,
so
I
moved
down
a
bagel.
Oh
okay,
good,
the
and-
and
you
know,
got
headbutted
by
my
cat
who
could
smell
fish,
and
I
pointed
out
that
he
doesn't
like
smoked
salmon,
but
it
doesn't
matter.
B
C
C
C
Yeah,
but
mostly
for
me,
it's
been,
you
know
spring
conference
hell
with
everything
for
red
hat
summit
and
kubecon.
Do
it
once
yep
the.
C
So,
okay:
well,
we
only
got
really
a
couple
of
things
yeah
so
see.
If
anybody
joins
us
give
a
couple
of
minutes.
Okay,
the.
C
C
A
A
A
B
C
A
C
Given
that,
given
that
shall
we
get
started
officially,
okay,
so
welcome
to
the
governance
working
group
meeting
for
the
cncf
one
to
the
cncfcoc.
C
This
is
being
recorded
and
all
of
that
jazz
and
we
are
going
to
start
out
by
reviewing
the
draft
ooh.
C
If
I
can
get
my
mouse
back,
we're
going
to
start
out
by
reviewing
the
draft
charter
document
for
recommendations
for
projects
to
add
a
charter
component
to
their
governance,
documentation,
which
was
proposed
by
dawn
last
meeting,
and
now
she
has
a
draft.
So
you
want
to
take
that
away
dawn.
A
Absolutely
so
I
did
get
some
good
feedback
from
dems,
which
I
think
I've
incorporated
most
of
that
the
so
the
direction
I
decided
to
go
with
this
was
looking
looking
around.
So
none
of
the
graduated
projects
have
a
quote
charter
document,
but
what
they
do
have
is
they
have
those
components,
and
so
what
what
I
tried
to
do
was
steer
people
towards
including
certain
things
in
their
documentation.
A
So
with
the
idea
that,
having
you
know
having
some
of
this
like
a
scope
and
a
mission,
helps
avoid
issues
and
misunderstandings.
Later
people
don't
actually
understand
what
you
do
and
there's
also
lots
of
complexity,
overlapping
technologies.
That
sort
of
thing
so
so
this
helps
people
fit
their
project
into
the
overall
ecosystem
and
what
functionality
it
has
and
it
doesn't
have.
What
are
they
trying
to
do
and
not
do
so.
A
While
these
are
principles
similar
things
found
within
either
their
governance
documents
or
the
readme,
so
the
specific
recommendation
was
to
include
a
mission
statement
in
the
readme
file
and
then
include
like
a
statement
of
values
or
principles
within
the
governance
document,
wherever
they
have
their
governance
documentation
and
with
a
point
that
it
should
be
consistent
with
the
mission
and
values
of
the
cncf
charter,
which
we
should
all
read,
and
then
jim's
also
made
a
good
point
that
these
really
are
living
document
which
did
change
over
time
as
progress
evolved.
A
So
what
you
need
when
you're
at
sandbox
is
probably
just
a
statement
or
two,
but
what
you
need
when
you,
you
know
by
the
time
you
graduate
is
probably
something
a
bit
more
detailed
and
then
I
gave
a
few
examples.
For
example,.
A
B
Have
no,
I
think
this
is
the
right
approach.
The
only
group
that
I
would
really
highlight
is
having
like
major
charters
here
are
the
sigs,
because
they
need
those
in
order
to
be
able
to
form.
B
I
don't
think
I
would
use
the
same
words
here
like
I'm,
I'm
struggling
with
being
able
to
call
it
a
project
charter
because,
like
as
we've
seen,
it's
not
called
a
charter
at
all
and
it
doesn't
follow
the
same
kind
of
thing
and
being
able
to
set
the
expectation
that
will
have
the
same
level
of
robustness
as
the
big
charters
like
the
cncf
charter
and
the
sig
charters
is
probably
not
something
that
a
tiny
little
baby
project
is
going
to
be
able
to
like
meet
those
goals.
Yeah
do
we
have.
A
Yeah,
no,
that's
a
good
point,
I
think.
Maybe
I
should
add
something
about
about
sings.
A
So
I
what
I
what
I
said
was
that
the
mission
should
be
in
the
in
the
read
me
because
I
think
that's
important
for
people
to
see
front
end
center
and
that
the
either
some
kind
of
statement
about
values
and
principles
should
be
in
the
in
the
governance.
Documentation.
C
Hold
on
I'm
trying
to
catch
up
with
notes,
yep,
the
and
there's
one
thing
that
you
don't
actually
mention
there
that
I
think
is
actually
critical
for
projects
to
have
scope.
A
C
As
in
which
is
kind
of
a
more
technical,
you
know
a
more
technical
corollary
to
the
mission
as
in,
like
you
know,
this
project
you
know
covers
you
know
the
you
know
container
x,
wasm,
runtime
and
its
dependencies
and
drivers.
A
Yeah,
I
ran
across
a
really
good
example
of
the
scope
document.
Well
maybe
that
was
the
kubernetes
one.
A
I
think
another
one
too
yeah
yeah
this
is
this?
Isn't
the
one
I'm
thinking
of
there
was
another
one
that
was
really
good,
that
I
will
dig
up.
That
was
a
very
much
a
technical
scope.
It
was
this
project.
Does
these
things
and
not
these
things,
and
it
was.
It
was
quite
well
written
I'll,
dig
up
an
example.
B
C
B
D
A
There's
quite
a
bit
of
leeway
on
there
yeah
I
tend
to
think
scope,
it's
probably
more
in
the
governance
documentation.
Would
you
agree
with
that.
C
I'm
I'm
fine
with
that.
I
can
see
it
being
in
either
place
so
yeah
the
I
mean
it's.
It's
kind
of
traded
because,
like
for
some
of
the
stuff,
like
I've,
just
been
working
on
conveyors
governance
document
again
and
for
conveyor,
they
really
need
scope
to
be
part
of
the
governance
documentation
because
that's
where
the
procedure
is
on
accepting
new
sub
projects
are
and
that's
when
you
really
need
to
know
scope
yeah
via,
but
for
other
projects.
C
A
A
Well,
this
is
good,
so
what
I'll
do
is
I'll
I'll
take
all
of
this
and
update
it
and
then
probably
do
we
want
to
review
it
one
more
time
in
this
meeting
or
should
I
just
make
the
changes
and
pr
it?
You
have
a
preference.
C
I'd
like
to
actually
spell
out
the
sort
of
three
different
sections
that
we've
identified
so
mission,
scope
and
values
and
principles
to
to
explain
what
those
are
because
right.
This
is
the
advisory
document
right
yep
and
it's
going
to
accompany
the
changes
that
we
make
to
the
templates,
and
so
explanations
are
in
order.
C
C
C
A
B
A
nice
timing
note
the
next
sig
update
meeting
is
april
6th,
so
that
could
give
you
both
a
deadline,
as
well
as
like
a
time
to
be
able
to
put
this
out
in
public
too
too.
Soon
too,
too.
Short
too
fast.
I
turned
15.
A
E
E
C
Yep
yeah,
but
I
do
not
turn
50
on
april
6th,
so
the
so
so
yeah
I
can
probably
be
at
the
meeting
and
that
actually
would
be
good
just.
B
C
Yeah
yeah
the
yeah,
so
we
have
time
to
to
work
on
this
more
in
the
next
week,
plus.
A
C
A
A
Yeah
and
I'll
be
I'll,
be
out
the
week
of
march
29th
through
my
birthday,
so
I'll
be
out
that
week
before,
because
that's
easter
holiday,
so
we
get
friday
and
monday
off
anyways.
So
taking
advantage
of
that
to
take
a
full
week
off
more
than
a
week.
C
A
A
C
C
C
C
A
C
Bm,
oh
well,
how
long
have
I
had
the
the
initial
bullet
point
version
of
the
definition
of
open
governance
sitting
in
a
hackmd
document,
yeah,
true,
so
the
okay
and
speaking
of
long-term
things.
I
have
finally
gotten
all
comments
incorporated
into
the
subprojects
template
so,
if
possible,
I
would
like
to
go
ahead
and
vote
to
merge
that
it
has
been
reviewed
by
sod
not
by
our
new
tse
liaison.
C
But
I
think,
given
that
it's
a
template,
it's
probably
okay,
to
have
it
reviewed
by
one
of
them
we
should
and-
and
we
also
have
not
synced
up
with.
B
Yeah,
no,
I
did
this.
I
want
to
say
last
week
with
updating
with
like
the
the
new
t.o.c.
C
Yeah
yep,
the
okay,
so.
C
A
C
A
Well-
and
you
should
expect
that
the
subprojects
template
to
end
up
in
the
top
project
very
soon,
because
that's
what
that's
what
joshua
works
on
and
he
and
I
were
talking
about
governance
for
for
tough
update.
A
And
okay-
and
I
was
like
I
know,
I
know
exactly
what
you
should
look
at.
I
was
like
it's
a
draft
yeah.
C
C
C
A
C
So
yeah,
and
I'm
just
saying
the
other
two,
the
other
two
did
not
quite
get
the
same
level
of
scrutiny,
which
probably
means
that
they
could
use
it
at
some
point
down
the
line.
Okay,
the
so
I
mean
the
two
are
in
some
ways:
less
complicated
or
have
more
field
examples
right,
because,
like
steering
committee
elections,
we
have
lots
and
lots
of
examples
of
the
and-
and
you
know,
maintainer
council
is
not
that
complicated
of
a
model
plus.
C
A
C
The
do
we
have
stuff
that
carolyn
is
waiting
for
us
on
the
website.
D
Yeah,
I
don't
know
she,
she
was
actually
waiting
for
my
review
and
I've
completed
it
last
week,
while.
B
B
D
Okay
time
zones:
okay,
I
mean,
like
the
day
daylight
savings
time
zones
yeah.
I
expected
that
this
hour
this
meeting
will
start
in
a
few
in
half
an
hour.
So
keller
was
waiting
for
my
review
on
the
website.
I
completed
it
last
week
and
let's
check
if
anything
else
is
there,
but
as
far
as
she
had
to
address
a
few
minor
issues,
then
that's
it.
D
D
Yeah
yeah
just
just
a
minor
just
a
minor
stuff
here
and
once
it's
done
so
we
are
good
on
the
website.
C
C
Okay,
the,
but
it
doesn't
sound
like
there's
specific
stuff
for
governance
to
do
until
that's
live.
C
But
it
doesn't
sound
like
there's
anything
to
do
until
that's
live
so,
okay,
I
think
that's
it
short
and
sweet
unless
you
actually
want
to
do
the
revisions
to
the
mission
stuff
live.
A
No
I'll
do
that
offline
because
I
actually,
given
that
we
want
to
put
more
details
about
the
mission,
scope
and
principal's
values.
I
kind
of
want
to
reorganize
it
a
little
and
break
break
those
down
into
separate
sections.
A
C
C
Okay,
oh
and
this
is
actually
part
of
contributor
growth
effectively,
but
in
there,
which
is
that
work
continues
on
the
template
contributor
ladder.