►
From YouTube: 2021-09-02 Governance Committee private meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
If
you
all
didn't
see
the
communication
from
the
cncf
staff,
they
got
us
some
really
nice
placement
in
some
publications,
including
devops.com.
A
I
thought
that
the
devops.com
reporter
was
great
ben,
and
I
really
liked
talking
to
him-
and
I
think
you
know
our
points
got
through
really
nicely
and
there's
apparently
more
to
come
too.
In
particular,
there
is
a
request
for
us
to
submit
some
people
to
do
like
a
live
interview
on
like
a
stream
or
something
so,
if
you're
interested
in
that,
you
should
volunteer
because,
like
you
know
as
much
as
ben-
and
I
do
like
talking
to
the
press,
you
know
the
opportunity
is
ours.
B
Yeah
I'm
happy
to
to
do
that.
I
saw
that
email
go
by,
so
I'm
certainly
happy
to
pop
on
that
show.
C
Okay,
cool
should
I
do
that
or.
B
Yeah,
would
you
would
you,
would
you
like
to
just
just
respond
to
that
email
yeah?
I
had
responded.
C
B
Is
he's
probably.
D
The
from
that
text,
drawing
thing
he's
probably
the
most
evocular
person
in
tech
media
if,
if
that's
not
too
much
of
a
gre
word,
but
at
the
end
of
these
things,
whenever
I've
taught
him
it
like
off,
you
know
when
the
camera
camera's
obviously
always
get
this
message
like
you're
such
a
good
boy
ben.
It's
like
that
kind
of
thing.
In
a
way.
That's
it's
nice
like
in
a
not
in
a
patronizing
way,
but
he's
a
nice
guy
should
be
fun.
C
That's
good
to
know,
because
you
know
you
have
you
have
different
sorts
in
the
tech
media.
It's
very.
D
I'm
looking
up
aunt
in
latin
mater,
so
I
have
no
idea
what
that
means.
I
think
the
answer
is
no.
Let's
talk
about
our
agenda.
Okay,.
B
D
I'm
just
sort
of
advertising
to
this
group
like
I've,
received
exactly
zero
comments
about
my
mission
vision,
candidate
too,
which
either
means
it's
perfect
or
that
no
one's
read
it.
I'm
gonna
vote
for
something
closer
to
two.
D
I
think
for
what
it's
worth,
the
other
one
has
received.
D
Revisions
and
as
much
like
has
like
more
polish
in
that
respect,
I
just
I
just
kind
of
want
feedback
about
the
approach
of
like
framing
it.
In
terms
of
like
specific
challenges
that
we're
trying
to
address
versus
the
solutions,
I
mean
there's
that
that's
like
the
main
thing
and
then
also
there.
We
still
need
an
actual
mission
statement.
D
The
other
one
is
really
just
a
vision
and
doesn't
have
the
mission
piece
which
I
think
we
should
have
both
the
mission
I
I
chose
is
basically
the
same
one
we
used
in
2019,
which
I
like,
but
I
just
want
to
make
sure
that
we're
talking
about
that
so
definitely
give
feedback
about
the
mission.
D
If
you
don't
like
it,
even
if
it's
just
like
a
tiny
tweak
and
then
on
the
vision,
I'm
interested
in
the
sort
of
high
level
feedback
about
that
framing-
and
I
don't
I
mean
it's-
not
gonna-
have
my
name
attached.
I
don't
give
a
personally.
A
It's
something
that
hybridizes
like
number
one
and
number
two
right
like
number
one
reads
like
a
more
traditional
mission
statement.
That's
why
I'm
like
I
like
mission,
one
or
mission
vision,
one
but
like
at
the
same
time.
I
understand
that
you
know
there
are
points
that
are
in
that
you
felt
you
needed
to
make
their
now
are
different
from
the
proposal
number
one.
D
So
so
not
be
super
pedantic,
but
I
mean
the
mission
and
the
vision
are
different.
Things
like
the
mission
should
be,
in
my
mind,
should
be
like
a
single
clause
or
maybe
a
single
sentence,
and
then
the
vision
is
usually
like.
What
does
the
world
look
like
after
open
telemetry
type
of
thing?
So
the
first
one
doesn't
have
a
mission
statement
and
we
should
have
one
of
those.
It
should
like.
That's
important.
D
I
think
anyway,
and
I'll
argue
that
point
whether
I
don't
know
if
this
is
the
right
one,
but
we
could
take
the
mission
statement
from
candidate
two
and
discard
the
rest,
for
instance,
and
that
would
be
a
fine
outcome
as
well.
I
just
want
to
make
that
clear,
but
yeah.
We
could
certainly
take
that
for
what
it's
worth
the
the
ideas
are
in
both
are
very
similar.
It's
just
a
different
framing,
and
so
maybe
what
you're
saying
is
you
prefer
the
framing
of
candidate,
one
yeah.
D
Okay,
well,
anyway,
just
leave
comments
in
the
doc
or
whatever
I'm
gonna
try
and
do
a
little
bit
more
rabble
rousing
on
this
and
again,
I'd
like
to
tie
this
off
in
the
next
couple
of
weeks.
Just
to
have
something
that
we
can
officially
say
is
the
thing.
D
And
I
don't
think
it's
I
don't
think
of
it
as
just
like
artifice
or
something
I
mean
we.
We
are
dealing
with
some
problems
that
I
think
relate
to
like
a
lack
of
alignment
around
like
the
vision
and
the
scope
and
the
style
of
what
we're
doing
stuff
like
that.
D
Okay,
I'm
done.
I
said
in
that
slack
thing
that
I
would
talk
about
this
here.
So
we've
had
a
couple
of
points
at
this
stage
and
I'm
not
pointing
fingers.
I
I
don't
even
really
remember
which
vendors
it
was,
but
where
we've
had
someone
from
a
marketing
side
of
an
organization
do
something
that
probably
didn't
work
from
the
marketing
guidelines,
but
they
just
never
knew
about
the
marketing
guideline
and
onboarding,
like
a
major
contribution,
seems
like
an
important
point
to
like
force
that
to
happen.
D
So
I
was
thinking
that
we
could
just
add
an
item
to
the
contribution
kind
of
process
where
it's
like.
We
need
an
explicit
act
from
the
company
making
the
contribution
that
their
marketing
department
has
like
comprehended
our
marketing
guidelines.
As
then,
the
contributions
are
being
done
by
the
technical
people
and
then
there's
just
no
synchronization
happening
until
we
see
the
blog
post
come
out
and
get
you
know
and.
C
Get
agitated
about
it,
yep
absolutely.
I
mean
it's
more
often
reaction
than
than
an
action
today.
D
Is
there
a
better
moment
to
make
that
happen
than
the
contribution
itself.
G
B
Okay,
but
I
do
think
you're
right
ben
that
section
we
have
these
contributing
guidelines
in
community
and
the
section
on
donations
is,
is
actually
like,
pretty
slim,
but
I
think
we
actually
do
have
a
whole
pile
of
things
that
come
with
contributions
like
your
copyright
notice
is
gonna
have
to
get
forked
over
to
open
telemetry
authors
and
please
read
these
marketing
guidelines,
but
I
think
we
actually
could
beef
beat
that
section
out
a
bit.
So
there's
at
least
something
people
can
read
when
they're
thinking
about
donating.
H
C
Maybe
maybe
when
they
sign
up
as
members
I
mean
we
could
we
could
just
do
it
that
one
time.
B
Because
the
key
is
it's
not
actually
like,
like
the
the
individual
contributors
right
who
need
to
get
the
message
right.
That's
the
the
problem.
It's
it's!
These
other
functions
within
a
company
that
aren't
going
to
be
making
prs
anyways
yeah,
and
so
that's
why
we
have
to
kind
of
remind
somebody
there
at
the
right
point
to
say:
hey
pass
this
on
too.
D
D
I
mean
like
big
sort
of
I'm
thinking
like
stanza
level
stuff
like
for
the
flowmill
stuff
did.
Did
we
create
a
new
repo
for
that.
C
D
Yeah
I
mean
that
could
be.
We
could
say
like
I
don't
know,
I
guess
the
question
behind
the
question
is
like
I'd
like
to
have
their.
You
know
that
someone
within
the
hotel
sort
of
structure
needs
to
be
responsible
for
doing
this.
If
it's
not
a
bot,
I
think
it's
probably
the
technical
committee
and
there's
like
a
a
doc
about
donations
right
now.
That's
you
know
pretty
thin.
Is
there
a
better
description
of
what
the
tc
is
responsible
for
doing
than
like
this
dock
right?
Here?
I
don't
think
there
is.
B
D
Is
the
place
to
put
it?
This
is
that's
what
I'm
getting
so
this
is
the
place
I
mean,
I
think
the
ai
here
is
I'm
happy
to
do
it,
but,
like
start
a
pr,
if
cc
the
technical
committee
and
be
like,
I
know
this
pr
is
not
done.
Tell
me
all
the
things
that
need
to
be
in
this
list
and
then
the
tc
can
use
this
as
a
bit
of
a
checklist.
C
We
I
thought
the
last
time
we
discussed
this
in
the
gc.
We
decided
that
we
would
at
least
mention
three
items,
one
that
you
know,
issue
be
filed
in
the
community
repo
when
the
donation
process
is
started
or
requested
by
the
requester.
Then
the
second,
you
know
part
is
a
tc
report.
Evaluation
be
added
to
that
issue.
Once
the
evaluation
is
completed,
and
then
it's
signed
off
by
somebody
from
the
tc
in
terms
of
the
issue
being
closed
and
the
decision
accepted
or
not.
C
But
that
was
the
three
steps
that
we
had
discussed.
D
C
E
I
suspect
we
will
still
run
into
issues
with
this
and
just
simply
because
it
will
not,
but
but
at
least
we
can
point
to
a
single
space
to
be
like
there.
You
go.
That's
why
but
yeah
it's
it's
important
to
do,
and
it's
important
to
set
the
expectations,
especially
if
we're
going
to
start
enforcing
them.
C
D
D
Okay,
I'm
happy
to
stop
talking
about
this.
For
now.
I
I'm
totally
happy
to
to
take
a
stab
at
that
and
I
like
the
idea
of
making
issue
template,
whoever
type
that
in
I'll
do
that.
G
D
A
A
propagation
layer
enhancement
that
we
would
like
to
see
yep
exactly.
B
Yeah,
I
think
just
adding
a
note
to
that
issue,
saying
that
gc
approves
this.
C
C
Yeah
in
the
last
iteration
again,
google
did
update
the
post
and
everything
so
all
good.
I
G
G
Yeah
can
it
sounds
good?
I
don't
think
we
can
tell
exact
number
of
days,
because
there
are
questions
like
this.
You
may
say
that
there
is
a
copyright
issue
and
there
is
like
a
branding
issue
and
then
gc
needs
to
figure
out
how
to
deal
with
branding
issue,
for
instance
like
in
flow
milk
case
after
tcg
diligence.
They
immediately
said
that
they
don't
want
to
keep
the
flow
meal
name
because
it's
registered
trademark
was
splunk
in
okay
in
other
cases.
G
It
may
be
not
be
that
easy,
like
maybe
some
I
mean
we
cannot
just
realize
that
you
see
due
diligence,
will
will
not
have
open
questions
that
require
some
further
investigation
by
jc.
I
A
Yep
yep
we
really
have
to
make
with
the
elections
like.
I
have
promised
that
I
will
own
the
technical
pieces
of
the
election
machinery,
but
someone
needs
to
actually
like
draft
the
statement
saying
you
know
hey
like
we're
opening
the
call
for
elections
right
like
so.
A
I
am
hoping
that
another
governance
committee
member
who
is
not
standing
for
re-election
will
join
me
in
working
on
this.
G
C
I
C
Yeah,
I
think
there
were
a
couple
of
issues
that
were
identified.
One
was,
of
course,
the
communication
outbound
and
I
think
the
communication
was
too
little
too
late
right,
I
mean
it
was
right
around
right
before
the
we
did
a
blog
post
right
before
the
election,
so
we
should
actually
do
multiple
rounds
of
you
know
just
on
twitter
on
linkedin
and
wherever
else
we
can
reach
out
to
folks-
and
I
don't
know
if
there's
any
way
of
posting
on
github,
you
know
across
our
maybe
our
community
repo.
C
It
does
have
the
issue
open
and,
of
course,
the
blog
post.
Maybe
we
can
do
it
in
the
tag
observability
group
also,
you
know-
and
I
can
do
that,
but
again,
you
know,
please
suggest
where
else
we
can
post.
I
Yeah
I
mean
I,
I
think
the
sig
meetings
is
the
obvious
first
place,
so
maybe
a
pinned
issue
on
each
repo
or
something
like
that.
D
I
think
the
pinned
issue
idea
is
a
very
good
one.
Daniel
and
I'd
also
suggest.
My
kind
of
option
of
last
resort
ended
up
being
an
issue
where
I
just
mentioned,
like
some
god
ungodly
number
of
people
which
was
not
100
effective,
but
definitely
increased,
like
the
number
of
people
who
signed
up
from
various
ways,
but
that
was
sort
of
my
option
of
last
resort
last
time.
But
I,
like
the
pinned
issue,
idea
a
lot
more.
I
Yeah,
I
mean,
I
think
we
probably
ideally
given
more
time.
I
would
say
we
have
a
pinned
issue
that
links
to
a
page
on
the
website
that
shows
each
candidate
and
when
is
the
vote,
and
how
do
I
vote
and
things
like
that?
But
I
don't
know
if
we're
thinking
we're
going
to
be
voting
in
what
a
month
or
something
like
that.
I
don't
know
whether
we
have
enough
time
to
set
that
much
up.
I
C
G
Did
we
have
a
call
for
eliminations.
C
B
As
well
as
like,
like
just
recreate,
what's
what's
in
there
for
2020
right,
the
degree
to
which
we
need
that
those
two
pages
and
then
I
can
get
that
information,
then
just
copy
it
over
to
the
website,
and
we
can
put
a
banner
up
on
the
website.
Like
just
change
the
website
banner.
It
would
be
pretty
easy.
G
Another
thing
is:
we
have
this
in
charter:
we
have
a
rule
of
number
of
activities
that
needs
to
be
more
than
20
activity
in
past
year,
so
we
asked
lucas
from
dfstats
to
run
this
script
for
us,
so
maybe
worse
doing
it.
So
people
who
don't
have
enough
activity
will
request
for
exception.
C
Okay,
so
maybe
daniel
you
and
I
and
liz
can
just
start
a
google
doc
and
we
can,
you
know,
work
on
a
checklist
and
then
by
next
week
we
can
just
have
a
brief.
You
know
sink
on
anything,
we're
missing
and
then
we'll
kick
start
I'll.
Have
the
issue
ready
and
we
can
review
it
and
and
then
just
start
posting.
I
This
is
really
an
update
that
the
the
cncf
ezcla
thing
so
for
those
that
don't
know,
there's
two
issues
right
now
with
easy
cla
one
is
a
new
branch
protection
rule
was
automatically
applied
to
every
repository,
which
applies
to
every
single
branch
and
does
not
allow
any
changes
without
a
pull
request.
I
This
is
an
issue
for
release
automations,
because
if
you
can't
modify
a
branch,
then
you
can't
create
a
poor
request
to
begin
with,
unless
you
have
a
fork,
so
initially
I
was
going
to
find
out
who
had
a
contact
at
cncf
that
I
could
talk
to
about
this.
I
I
It
then
does
still
leave
the
second
issue
open
where,
once
a
release
automation
has
created
that
branch
when
they
create
the
pull
request.
The
cla
check
will
fail
on
that
pull
request
back
to
the
main
branch,
so
we
still
need
an
exemption,
and
I
I
gather
that
that
is
still
ongoing
discussion,
but
I
don't
have
access
to
the
issue
that
was
created.
So
I
don't
know
how
active
the
discussion
is
or
anything
like
that.
I
I
But
I
mean
the
next
step
is
we're
waiting
on
the
on
the
ezcla
team
to
find
out
whether
we'll
be
able
to
get
an
exemption
for
the
github
action
spot.
If
not,
then
we'll
have
to
find
some
work
around.
C
I
For
now
at
least,
what
javascript
ended
up
doing
was
using
a
personal
access
token
from
one
of
the
maintainers
mine
actually,
which
is,
is
fine
as
a
temporary
solution.
But
I
don't
see
that
as
a
long-term
solution
at
all.
C
Yeah,
I
I
think
that
it
should
be
a
generic
token
right,
but
again,
github
has
a
we'll
have
to
create
a
user.
That's.
I
I
If
they
exempt
the
github
actions
bot,
then
we
actually
don't
need
to
do
that,
because
you
don't
get
a
specific
user
token
to
do
that.
Their
concern
with
doing
that
is
that
github
actions
can
theoretically
do
anything.
So
if
you
exempt
it
from
the
check,
you
know
that
exempts
any
action
that
runs
where
they
they've
previously
exempted
bots
like
dependable,
which
have
like
a
very
limited
scope
of
what
their
of
what
it
does
and
the
changes
that.
I
But
github
actions,
you
know
anyone
can
commit
a
new
action
that
makes
changes
that
could
theoretically
add
new
copyrightable
content
or
something
like
that.
So
there
they
want
some
way
to
be
able
to
control
that.
C
C
You
know,
first
of
all,
shortlisting
what
needs
to
be
done
in
the
core
we've
been
moving,
you
know
components
to
contrib,
which
are
not
part
of
the
core
that
includes
zipkin
jaeger,
prometheus,
also
moving
to
contrib
for
collector,
but
nonetheless,
you
know
being
really
having
building
out
smarter
builds
instead
of
having
everything
you
know
in
a
kind
of
an
mono
repo
structure
that
the
collectors
had
so
far
so
decentralizing
a
bit,
but
also
having
a
lean
and
mean
core
collector,
artifact
and
and
again
we
are
there.
C
We
have
two
releases.
We
are
doing
weekly
releases
now
for
the
next.
You
know
month,
so
we've
released.
We
did
a
release
this
tuesday
we'll
do
every
tuesday
we're
going
to
do
a
weekly
release
so
that
we're
testing
with
the
core.
That's
a
major
change
and
kind
of
you
know
seeing
if
we're
getting
seeing
any
p0s.
C
If
not,
we
do
plan
to
release,
you
know
core
collector
complete
for
tracing
stable,
5914.
So
and
then
we
are
working
on
a
technical
blog
post
associated
with
that.
So
just
wanted
to
give
an
update
to
the
gc.
C
It
is
a
major
milestone
and
it's
something
that
you
know
will
get
us
to
the
1.0
that
we
have
been
looking
for.
I'm
trying
to
achieve
for
a
while.
C
So
lots
of
work
coming
ahead,
but
the
metrics
will
pick
up
right
after
this.
Just
just
you
know,
there's
a
tremendous
amount
of
work
happening
in
that
area
and
we
are
still
you
know,
kind
of
on
boarding
approvers
who
can
potentially
become
maintainers.
We
still
are
very,
very
much.
You
know
very
thin
on
maintainers
on
the
collector,
given
its
its.
D
Thanks
for
the
update
elite
and
it's
good
to
hear
that's
converging,
I'm
curious
just
on
the
maintainer
point,
probably
like
sort
of
a
dumb
question,
but
are
there
people
who
would
like
to
do
that
who
just
don't
kind
of
quote,
qualify.
C
No,
what
we've
been
doing
actually
is
I've
been
working
with
bogdan
to
you
know
again
make
sure
that
there
there
is
a
path
for
approvers.
You
know
who
have
been
approving
to
graduate
to
become
maintainers,
and
I
actually
have
been
explicitly
getting
them
to
carve
out
issues
that
they
can
work
on,
and
you
know
show
that,
because.
D
C
About
no
it's
the
knowledge
of
the
core
collector,
because
you
know
the
docu,
the
the
collector
architecture
is
not
really
documented
anywhere,
so
just
having
the
depth
in
the
code
base
and
and
understanding
the
you
know,
implementation
of
the
core
collector
yeah.
I
know.
D
I
unders
the
question
behind
the
question
is
just
that.
I
wanted
to
make
sure
that
those
whatever
heuristics
we
had
were
pretty
arbitrary
around
the
number
of
this
or
that
that
are
needed,
and
I
just
want
to
make
sure
it
sounds
like
it's
more
of
a
fundamental
knowledge
thing,
though,
which
is
not
as
easy
to
tweak.
So.
Okay.
C
Yes,
exactly
and-
and
we
have
you
know,
been
cultivating
two
or
three-
you
know
maintain
approvers
actively,
so
hopefully
we
can
get
them
to
the
point.
You
know
where
they're
ready.
D
Yeah,
I
guess
we're
done
with
time.