►
From YouTube: 2022-05-26 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
B
B
Yeah,
I
don't
think
anything
has
has
missed
the
the
power
of
interest
rates.
E
B
C
A
Yeah,
I'm
just
going
to
say
we
use
the
community
bug
tracker
to
track
a
number
of
issues
relevant
to
the
agency
like
we,
we
can
move
files
and
like
documentation
out
of
the
community
repo.
We
cannot
kill
the
community
yeah.
F
But
the
question
is
like
documents
like
mission
or
charters:
should
they
really
be
authored
in
the
documentation
repo
in
the
first
place?
Oh
sorry,
in
the
in
the
website,
repo
that
she's
called.
B
It's
a
fair
question.
Like
I
see
I
just
saw
ben's
comment
there
about
liking,
to
be
able
to
find
these
like
how
we
could
find
these
things
in
the
file
tree
in
github.
I
must
say
that
I
also
find
that
appealing
there's
got
to
be
a
way
to
double
publish
these,
though.
D
I
I
have
to
say
I'm
like
an
aesthetic
level,
it
kind
of
bugs
me
for
the
what's,
essentially
the
marketing
website
to
be
the
source
of
truth
for
anything
approximating
like
mission
vision,
code
of
contact
like
those
sorts
of
fundamental
things,
although
I
will
also
admit
that
it's
it's
a
totally
aesthetic
thing,
it's
not
like
it's
not
like
we're
ever
going
to
not
have
a
website
or
something.
So
it's
like
it's
not
like.
It's
actually
a
problem
it
just
it
just
kind
of
feels
smells
wrong
or
something.
D
So
it's
a
pretty
dumb
argument
like
I
can't
well,
I
think
the
copying
of
files
seems
like
a
guaranteed
like
future
skew
issue.
So
I
can
see
why
there's
a
desire
not
to
do
that.
A
A
We
can
pro
we
can
pull
in,
I
believe
the
otl
or
the
hotel
specs
into
the.
E
A
C
C
There
are
yeah
there's
some
problems
with
that,
because
it's
pulled
in
via
sub
module
and
the
way
that
our
static
site
generator
renders
markdown,
particularly
with
regards
to
links
and
relative
links,
in
particular
github
run,
like
has
them
in
a
different
path.
So
you
can
only
have
links
that
work
in
github
or
on
the
website.
You
cannot
have
a
link
that
works
on
both
without
using
like
a
full
global
url
yeah.
C
C
It
mattered
for
like
the
javascript
documentation
because
we
were
using
a
sub
module,
so
we
would
modify
the
documentation
in
the
javascript
repo
and
keep
it
update
and
everything.
And
that
was
great.
But
then,
when
the
sub
module
was
updated
on
the
website,
it
would
fail
their
markdown
linting
and
cause
the
build
to
fail
and
stuff
like
that.
C
C
F
B
D
F
I
don't
know
if
the
sub
modules
actually
is
the
better,
because
sub
module
requires
manual.
Update
of
the
commit
in
the
in
the
docs
is
that
the
workflow
that
they
have
to
manually
update
for
the
spec
changes.
F
Yeah
yeah
the
build
can
definitely
pull
it
and
then
just
have
the
build
kicked
off
on
a
like
a
web
hook
from
from
those
ripples
instead
of
sub
module.
Okay,
oh
I'll
reply
to
this.
B
Okay,
you're
gonna
reply:
you're
ready,
perfect.
Okay,
I
will
close
my
reply.
Then
all
right
next
was
a
lolita
who's,
not
here
updated
ted
on
customer
discussion.
Postponement
due
to
customer
concern
about
safe
space
to
share
we'll
discuss
further
gc
to
figure
out
resolution.
C
E
C
C
B
Yeah
all
right
I'll
tag
her
in
a
comment
here.
Actually
I
don't
know
her
new
email
address,
so
I
don't
know
how
to
tag
her.
I
think.
B
B
B
Next
topic
was
aleda
metrics
announcement
cubicon,
you
congrats.
What
is
ga
we'll
pick
up
the
maintainer
meeting,
but
it
should
be
pretty
soon.
Let's
celebrate
with
a
blog
post,
we
have
a
blog
post.
B
C
Yeah,
so
I
just
put
like
a
a
a
list
of
topics
here,
essentially
having
just
finished
kubecon.
There
are
definitely
some
things
that
I
think
could
be
improved
like
at
the
booth
we
didn't
have.
A
demo
of
any
kind
we
didn't
really
have
like
even
a
powerpoint
would
have
been
a
huge
improvement.
We
just
showed
the
website
and
waited
for
people
to
ask
questions.
F
C
Planning
could
definitely
improve
that.
Yes,
so
that's
what
I
had
for
the
booth.
I
was
not
at
the
community
event,
but
I
just
listed
it
as
a
topic
in
case
someone
has
feedback
for
there
by
attendance.
I
meant
it
was
impossible
to
know
who,
from
the
community,
particularly
maintainers,
were
going
to
be
there
until
we
showed
up,
which
made
it
really
hard
to
plan
a
lot
of
the
things
that
I'm
talking
about
here.
So
a
more
in.
C
B
That
rarely
was
an
issue,
but
but
since
then,
certainly
with
la
and
now
valencia
has
been
a
challenge
where
a
lot
of
people
are
deciding
last
minute.
They
want
to
come.
C
C
Go
you
may
have
responsibilities,
yeah
yeah
again
with
speaker
slots.
It
wasn't
particularly
organized
with
the
not
just
like
the
maintainer
track
talk
but
like
there
were
a
handful
of
open,
telemetry
talks
and
I
think
it
would
have
been
nice
to
coordinate.
You
know
we're
doing
a
beginner.
B
Interestingly
enough,
like
the
non
like
the
maintainer
track,
talk
we'd
organized
like
like
here
and
discussed
it
before
the
the
non-maintainer
talks,
the
regular
regular
cube
contacts.
I
don't
know
what
they're
called
they
were
mostly
done
by
people
who
aren't
really
involved
in
the
community
at
all
is
my
sense.
C
C
C
Been
a
community
member
in
the
past,
so
yeah
I
I'm
not
sure,
and
yet
I
kind
of
agree
it
would
have
been
nice
to
have
some.
You
know
organization
there,
but
having
external
people
stop
talking
about
open
telemetry
is
is
a
good
thing.
You
know
it's.
C
B
B
Maybe
the
gentleman
from
from
honeycomb
had
mentioned
that
he'd
talked
to
some
of
the
other
projects
with
their
project
booths
and
said,
like
hey,
did
you
have
to
tell
the
cncf
to
go
put
in
the
batches
and
the
the
stickers
and
they're
all
like
no
like
they?
They
just
showed
up
yeah
yeah
yeah
yeah,
that
was
it
yeah.
B
Yes,
it
was
you
okay,
and-
and
so
I
it's
it's
not
even
clear
like
how
how
we're
supposed
to
get
those
considering
other
projects
they've
just
materialized
for
them,
so
michael's
following
up
or
had
taken
the
action
follow-up
with
the
cmcf,
because
it
was
curious
like
open
tracing
which
ben
correct
me
if
I'm
wrong,
but
I
think
it's
officially
shut
down
now.
D
It's
officially,
what's
the
word
put
out
to
pasture
yeah,
but.
B
They
had
like
brand
new
stickers
for
it
and
and
the
little
little
badges
that
you
put
on
top
of
your
main
conference
badge,
and
so
I'm
guessing
some
wires
got
crossed
michael's
going
to
chase
it
down.
B
B
B
They
prioritized
dating
projects-
I
guess
but
yes,.
B
And
so
that
one's
on
me
like
I
waited
a
few
days
to
respond
to
the
email
because
I
was
slammed
and
I
didn't
think
it
was
time-sensitive
to
be
honest
because
they're,
like
oh,
you
got
three
weeks
to
reply
and
then
I
fill
in
the
form
it's
like.
Oh,
you
can
only
choose
a
pm
booth,
because
the
first
10
people
got
that
got
the
amp
and
booths.
C
B
Exactly
I
I
was
concerned
like
to
be
perfectly
honest.
I
was
even
concerned
the
community
meeting
which
I've
been
like
sending
out
links
to
on
slack,
but
no
one
had
been
like
directly
replying
to
them.
I
was
like
oh
no,
it's
just
going
to
be.
B
And
then
it
was
a
full
house
like
like
five
minutes
before
it
started.
People
were
grabbing
chairs
from
other
rooms
to
join
and
so
like,
like
we
have
a
project,
that's
very,
very
popular
but
you're.
Right
like
like
before
the
conference,
you
could
have
told
me
it
was
gonna,
go
the
other
way
and
I
would
have
believed
you.
B
B
C
But
we
could
say
yes
right,
wait,
we
could
say
this
would
rather
have
more
people
yeah,
you
know
or
or
you
know
not
to
not
to
just,
I
guess-
lie
about
it.
We
could
say
last
time
the
room
was
full
yeah.
This
time
we
have
a
registration
form.
Registered
attendees
will
be
prioritized.
If
there
are
space
we.
C
So
those
are,
those
were
the
items
that
I
had
like.
I
said
it
wasn't
necessarily
I
wasn't
at
the
community
event,
so
I
don't
have
anything.
B
C
B
Can
give
an
update
on
that
one
and
I'll
give
it
again
next
week
when
we
have
more
attendance,
so
it
was
mobbed,
even
though
it
was
before
kubecon
technically
kicked
off.
We
had
very
good
attendance
amongst,
like
users
of
open
telemetry,
so
we
did
a
like.
B
I
ran
it
kind
of
ad
hoc,
but
we
we
had
several
sessions,
one
of
which
was
like
feedback
on
the
project
which,
where
we
actually
took
over
an
adjacent
room
and
had
anyone
who
contributes
or
maintains
parts
of
open
telemetry,
go
to
that
room
and
talk
about
the
contributor,
maintainer
experience
and
then
the
other
room
which
was
run
by
henrik
from
from
dynatrace
daniel.
B
You
probably
know,
was
the
the
user
experience,
and
so
I
don't
have
the
data
from
from
that
one,
because
I
was
running
the
contributor
experience
session
for
about
an
hour.
But
we
got.
We
got
a
lot
of
good
feedback
on
on
things
that
can
be
improved,
go
figures,
things
that
we've
talked
about
before,
like
more
maintainers,
less
burden
on
maintainers,
particularly
around
contrib
repos
things
like
that.
But
we
can
go
over
the
full
list
and
then
we
talked
about
the
project
roadmap.
I
had
written
up
like
on
the
flight.
B
I
can't
sleep
on
planes
and
the
flight
had
no
internet
at
all
because
it
was
a
replacement
plane.
So
I
was
bored
and
just
wrote
up
like
here's,
a
list
of
like
15,
brainstorming
ideas
of
like
major
things.
The
project
can
focus
on,
and
so
then
we
spent
about
an
hour
having
the
attendees
add
more
discuss
the
ones
that
were
already
there
and
then
we
just
took
like
just
a
straw
vote
of
people's
interests,
about
which
of
these
items
were
more
appealing
to
them
as
a
community
which
did,
they
think,
were
the
most
interesting.
B
Just
putting
in
the
zoom
chat,
probably
the
most
interesting
or
surprising
thing
was
that
profiling,
as
a
signal,
was
the
number
two
most
requested
thing
amongst
the
users
and
maintainers
after
logging,
as
a
signal
which
is,
of
course
already
happening.
B
But
you
can
see
the
the
list
here,
so
I'd
added
them
as
people
were
speaking.
So
this
is
the
full
list
and
then
at
the
for
the
vote
at
the
bottom,
we
just
I'd
put
on
that
list
and
had
people
edit
the
dock
and
add
an
x
to
the
things
they're
interested
in.
B
C
I
will
try
I'll
contact
henrik
to
see
if
he
has
any
sort
of
formal
feedback
from
the
user
experience.
You.
B
Should
have
a
bunch,
there
was
nicholas
harteau,
the
the
the
new
mark
carter
at
aws
who's
running
their
open
source,
observability
team
he's
the
gm
for
it
who,
by
the
way,
I
used
to
work
with
him
at
google
back
in
the
day,
but
but
he
he
attended
and
he
actually
had
a
ton
of
like
really
powerful
feedback
for
the
user
experience.
B
B
It
was
today,
but
not
many
people
came
so
I
assume
it's
in
two
weeks
today
was
a
holiday
in
austria
too.
I.
D
B
Yeah
yeah
so
anyway,
lots
of
good
stuff
there
with
the
roadmap
discussion
as
well
as
the
just
general
feedback
from
the
community.
We
can
go
over
that
in
the
end
user
working
group.
I
think
primarily
in
the
next
few
weeks.
C
Okay,
in
terms
of
these,
like
kubecon
retro
items,
I
know
we're
going
to
run
out
of
time
pretty
soon
for
the
upcoming
october
kubecon.
I
think
we
should
we
don't
necessarily
need
to
assign
right
now,
but
we
should
assign
somebody
to
be
responsible
for
the
booth
experience
exactly.
B
E
B
It
ended
up
like
I
think
it
was
excellent
like
to
me
that
was
the
highlight
of
kubecon
was
like
the
engagement
at
the
community
event,
and
the
number
of
people
who
showed
up,
who
are
actually
interested
in
giving
us
feedback
and
like
and
having
like
those
conversations
and
users
was
really
really
great
but
still
like,
like
it
was
kind
of
like
hastily
organized
on
my
part.
C
Yeah,
I
I
just
don't
know
how
we
can
make
like
a
more
official.
I
think
guaranteeing
the
attendance
in
advance
would
help
us
with
so
many
things.
I
almost
wonder
if
we
should
try
to
have
like
an
official
maintainers
meeting,
an
in-person
maintenance.
I.
B
Think
we
should
yeah
in
the
october
one
I
had
originally
kind
of
assumed
that
the
community
event
would
be
that,
because
I
wasn't
expecting
massive
attendance.
Yes,.
B
C
C
Yeah,
so
that
might
be
one
way
to
go
about
it
and
without
making
offense
to
our
european
colleagues,
I
think
it's
easier
to
do
that
in
the
us.
It'll
be
easier
to
get
more
of
the
maintainers
to
commit
to
that.
Well,
there's.
B
Yeah
so
yeah
overall,
I
think
the
conference
was
great
to
me.
The
the
community
meeting
was
the
was
the
highlight
it
was
wonderful
to
see
like
open,
telemetry
highlighted
like
in
so
many
talks
and
and
just
having
so
many
people
and
companies
and
others
interested
in
it.
Yeah.
B
It
would
always
be
kind
of
a
small
thing
compared
to
like
kubernetes
itself,
and
now
it's
like
open
telemetry
has
so
much
attention
to
it.
It's
very
exciting
to.
B
In
his
little
book.
B
Yeah,
but
no
it
was.
It
was
a
great
showing
for
the
project.
My
only
other
two
follow-ups,
so
cisco
had
launched
some
observability
product
at
kubecon.
It's
like
a
distributed
tracing
backhand,
pretty
basic
one
that
literally
uses
a
telescope
like
it's.
Basically,
the
hotel
logo,
flipped
90
degree
like
just
mirrored
so
ted,
was
talking
to
them
in
the
cncf
to
get
that
to
change.
C
B
It's
it's
rather
amusing,
just
because
it
says
telescope
powered
by
open
telemetry.
It
has
an
open,
telemetry
logo
beneath
the
telescope.
One
is
basically
the
same.
Ted
already
talked
to
them
sounds
like
they're,
going
to
fix
it,
but
just
to
keep
an
eye
on
it.
Yeah.
C
B
Yeah
yeah,
maybe
but
but
the
logo
was
the
the
one
that
at
least
I
was
focused
on
the
other
thing
was
I
was
going
to
ask
the
cncf
like
all
the
booths,
not
just
ours,
but
the
whole
collection
of
project
booths
were
kind
of
shoved
off
into
a
corner.
I
feel
like
a
kubecon.
B
The
project
boosts
like
not
specifically
arcs
but
like
even
kubernetes
is
project
booth
and
others
should
probably
have
more
of
a
presence,
rather
than
being
relegated
to
the
side
and
like
I
I
get
that
the
conference
makes
money
from
sponsors
and
it
wouldn't
exist.
Otherwise,
and
this
is
a
fundraising
event
for
the
cncf,
but
at
the
same
time,.
B
D
Amplified
by
I
mean,
I
think,
a
common
theme
in
this
comment
as
well
as
the
comment
about
like
you
know,
swag
and
stuff
like
that,
is
that
open
telemetry
may
be,
if
not
one
of
the
only
I
guess
kubernetes
might
be
in
this
category
too,
but
it's
probably
the
only
like
really
successful
cmc
project
that
isn't
basically
open
core
for
a
single
vendor
right.
So
I
think
for
other
projects.
There
is
some
vendor
that
you
would
go
to
to
like.
You
know
who
have
some
fancy
booth
or
whatever
and
the
more
prominent.
E
D
But
open
telemetry
is
kind
of
like
that's
like
the
place.
You'd
go
to
type
of
open
telemetry
period
right.
So
yes,
I
think
that's
an
issue.
B
C
B
Traveling
around
to
other
booths
to
talk
to
people.
I
was
at
the
splunk
booth
briefly
and
someone
had
recognized
open
telemetry
and
they
said.
Oh,
do
you
use
our
database
with
open
telemetry
like
do
you
use
it
like?
Are
you
a
customer
of
our
database,
I'm
just
like
what
anyways
all
righty.
B
C
We'll
go
ahead.
Yeah
I
was
going
to
say:
I
think
we
covered
the
the
retro
topics,
at
least
from
a
high
level
pretty
well,
and
we
can.
We
can
have
more
specific
conversations
about
this
stuff
later
and
and
assign
roles,
yep
cool.