►
From YouTube: 2021-04-29 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
A
A
B
My
friend
is
moving
to
london
and
he's
trying
to
like
get
rid
of
all
the
stuff.
He
did
give
me
this
like.
Oh
this,
like
midi
controller
keyboard,
so
I
can
just
like.
I
don't
know
how
to
play
the
piano,
but
I
can
I
can
do
it.
You.
C
B
Play
tune
for
us,
is
it
plugged
into
zoom
it's
plugged
into
garageband,
and
I
could
pipe
my
audio
through
and
play
some
like.
You
know:
bossa
nova,
music
for
you,
muzak
waiting.
B
I
play
girl
from
epinema
or
something
like
that.
Pretty
fun.
D
A
Yeah
I
added
it,
but
I
copied
it
from
somebody's
message
in
slack.
So
it's
not
really
my
item.
I
just
wanted
to
make
sure
that
it
was
in
the
record.
I
guess
for
malalita.
E
F
F
Sure
I
think
I
had
shared
notes
with
everyone
on
our
incubation
channel
and
let
me
just
pull
up
the
notes
right
now,
but
just
to
give
you
an
update
again,
you
know
there
was
a
very
positive
feedback
coming
in
from
the
user
interviews
that
the
toc
conducted
and
again
you
know,
as
we
chatted
with
alina
she
said
everything
went
well
there.
F
The
toc
also
would
like
us
to
address
the
comments
that
were
raised
in
the
incubation,
doc
that
are
still
pending,
including
a
couple
of
the
action
items
you
know
again.
There
was
a
request
for
documentation
right
for
the
architecture
of
the
project,
as
well
as
any
other
additional
details
on
a
compatibility,
matrix
of
sorts
for
tracing
metrics
and
logging,
or
some
kind
of
a
maturity
matrix
right,
which
again
would
be
complex
to
do,
I
would
say,
but
we
still
should
do
it
and,
I
think
ted
you
had
some
thinking
around.
F
D
F
Mean
we
can
we
can
do
that
on
the
spec
repo,
if
that
makes
sense
and
then
just
link
to
it
from
there,
because
it's
easier
to
update
you
know
make
updates
to
the
matrix
or
you
know.
However,
we
want
to
present
that
on
the
spec
repo
just
file,
you
know
we
can
modify
it
and
maintain
it
and
then
just
link
keep
a
link.
D
Yeah,
I
just
want
to
make
sure
it's
something
that
that
stays
up
to
date.
I
was
thinking
of
just
putting
something
that
was
very
simple,
like
tracing
metrics
logs,
something
like
that,
because
we
we
we
have
some
of
this
stuff
scattered
about
right
now
and
we're
not
very
good
at
updating
it
like
we.
We
made
one
of
these
in
the
community
repo
and
it's
pretty
out
of
date,
and
we.
F
I
didn't
I
didn't
know
that
I
mean
I
can.
I
can
definitely
take
a
look.
I
mean
because
the
reason
I
say
that
I'm
okay
with
being
the
owner
for
the
matrix,
at
least
at
least
one
of
the
owners,
because
I
do
update
that
into
you-
know,
for
even
our
teams
in
terms
of
what
we
are
you
know,
working
on
and
staying
in
sync
with
it
so
ted
again
happy
to
be
one
of
the
owners.
If
that
makes
sense,.
D
Yeah,
it
would
be
great
to
maybe
update
that
piece
in
the
community
repo,
but
I
was
thinking
you
know
might
as
well
just
move
it
to
the
website.
We
don't
it's,
we
don't.
We
don't
have
like
great
tooling
for
being
able
to
like
sync
and
pull
things
onto
the
website
from
other
places.
So.
D
Sure
yeah,
that
that
would
be
good
as
well,
maybe
move
it
over
to
this
it'd
be
nice
to
maybe
integrate
that
with
the
compliance
matrix.
So
in
the
spec
repo
we've
got
this
compliance
matrix
and
maybe.
F
F
Talk
and
other
than
that,
I
think
elena
said
that
she
would
set
up
a
review
with
rich
richie
as
and
bartek
on
the
observability
sig
to
walk
through
the
incubation
dock
after
we
have
addressed
everything
on
by
may
may
20th,
and
that
will
be
the
last
part
of
you
know
everything
of
the
process
before
it
goes
into
public
comment
period
for
two
weeks.
G
F
G
I
am
doing
a
like
a
virtual
panel
with
bartek
and
other
people
hosted
by
info
queue
and
bartek
had
some
rather
positive
things
to
say
about
open
telemetry
in
that
in
that
virtual
panel,
we're
doing
it
over
like
typing
into
google
doc.
So
I
think
that,
as
far
as
the
public
review
period,
I
don't
think
that
there
that
that's
going
to
be
a
problem,
because
I
think
kind
of
from
a
public
perspective
now
that
we've
kind
of
talked
through
some
of
the
challenges.
G
I
I
think
that
things
are
a
little
bit
more
conciliatory.
Now,
that's
great
cool!
That's
good
news!.
D
I
had
one
one
question
on
that
front:
there's
still
like
that
blob
of
bartek
comment
up
at
the
top
of
the
document
around
that
was
essentially
like
the
protestation.
I
believe
the
idea
was
that
was
going
to
get
moved
somewhere
and
then
we
were
going
to
write
a
rebuttal,
but
I
hadn't
seen
them
touch
it
yet.
So
I
was.
F
F
Yes,
that's
correct,
so
ted.
I
think
that
that
will
get
updated
as
soon
as
we
have
addressed
or
as
part
of
as
we
address
the
comments.
D
F
D
F
So
I
think
that
that
was
all
we
had
and
then
the
two
action
items
alina
suggested
or
recommended
are
that
you
know,
of
course,
the
github
page
we
created
as
an
addendum
to
link
to
the
architecture
component,
specs
testing,
support
and
other
documents
requested
and,
of
course,
the
components,
readiness
matrix
also
being
available
in
terms
of
the
maturity
matrix
that
we
just
discussed.
D
Yeah
it,
it
seemed
like
the
one
thing
we
haven't
heard
back
from
them
on
how
much
of
a
sticking
point
it
is
for
incubation,
but
the
one
like
practical
matter
was
related
to
testing
and
code
coverage
looks
like
that's
actually
pretty
pretty
scatter
shot
right
now
across
the
different
cigs.
D
Since
that
was
like
a
thing
they
highlighted.
They
didn't
mention
whether
that
would
be
a
blocker
for
incubation,
but
it
does
sound
like
something
we
should
send
off
to
the
the
sig
maintainers.
Just
the
requests
to
to
get
a
code
coverage
badge
up
and
running.
F
Yeah,
that's
a
good
great
idea,
ted
and
I
think
that
they
had
requested
that
in
the
in
in
the
incubation
doc
comments
ted.
So
I
think
that
we
do
need
to
at
least
outline
you
know
what
our
test
current
test
strategy
is,
and
you
know
what
do
we
want
to
see
in
the
long
run.
B
D
Yeah,
we
haven't
really
it's
kind
of
been
every
sig
do
their
own
thing
as
far
as
testing
so
far,
so
that
is
actually
an
area
where
maybe
we
need
to
to
get
a
little
more
coordinated
but
yeah
at
minimum,
getting
just
like
some
code
coverage
badges.
That
would
probably
be
helpful.
F
F
F
All
right,
that's
all
that
you
know
I
mean
that
was
the
update
again
from
the
discussion
that
we
had
liz
and
morgan,
ted
and
ben.
Thank
you
for
joining
in
there.
C
I
remember
seeing
there
was
a
comment
asking
for
sort
of
a
more
detailed
overview
of
the
architecture.
Yes,
that
seems
like
a
sizable
chunk
of
work
that
we
don't
really
have
that
anymore.
F
We
have
some
architecture
diagrams
in
the
spec
today
and,
and
we
can
we
but
you're
right-
we'll
have
to
actually
do
some
work
there
right.
G
Like
the
toc
is
not
going
to
go
digging
around
in
the
spec
repo
right
like
we
have
to
expose
this
on
the
public-facing
documentation
website.
That
is
our
obligation.
Yes,
that
the
diagrams
exist.
We
just
need
to
service
them
right,
like
you
know,
what
role
is
a
collector
play
right
like
what's
the
difference
in
their
apm
sdk
right
like
stuff
like
that
is
what
they're
looking
for
yep.
D
I
have
a
talk
for
for
olliefest,
that's
on,
like
basically
the
the
design
justification
for
open,
telemetry
like
this
is.
This
is
like
why
we
split
things
up
the
way
we
did
and
and
the
best
practices
there
so
that
things
do
monday.
I
can
probably
take
what
I
what
I've
got
from
that
slide
deck
when
it's
done
and
maybe
turn
some
of
that
into
yeah,
because.
F
D
F
D
Yeah
yeah
after
I
don't
know
after
you're
done
and
the
ollie
fest
is
a
rule
that
you
know
they
don't
want
the
talk
to
have
been
given
somewhere
else
before,
but
I
think
it's
probably
fine
to
share
the
deck
and
start
turning
it
into
other
stuff.
E
Switch
switching
gears
a
bit,
so
there
was
a
some
sort
of
security
incident
with
code
cov
code
coverage
a
few
weeks
ago.
I
know
that
some
of
the
sigs
have
gone
and
rebuilt
all
of
the
the
assets
that
they.
F
We
had
to
change
all
the
credentials
if
there
were
most
repos
did
not
have
credentials,
but
some
did.
We
did
go
through
and
scrub
everything.
Oh.
G
Workflow
or
whether
they
were
just
you
know,
publishing
the
hashtag
of
the
code.
Okay,
yep.
D
G
It
only
impact
right
like
it
only
impacted
the
bash
uploader.
It
did
not
impact
other
forms
of
uploading.
So
that's
why
the
impact
was
relatively
constrained.
That
being
said,
you
know
full
disclosure.
It
was
not
entirely
free
of
disruption.
Some
when
the
collector
was
re-tagged
and
rebuilt,
it
resulted
in
some
applications
that
imported
code
from
the
collector
breaking,
because
the
ghost
sums
stopped
matching.
E
F
It
was
discussed
morgan
in
the
maintainers
meeting
and
yes,
the
six
did
go
and
update
in
the
maintainers.
F
Yeah,
what
was
requested,
though,
was
again
by
a
lot
of
the
maintainers
was
a
published
process.
For
you
know
when
there
are
p0
issues,
you
know
what's
the
triage
process
or
you
know,
and
the
reporting
process,
because
people
kind
of
scrambled
to
figure
out
you
know
what
needs
to
be
done,
but
you
know
at
least
three
things:
having
a
slack
channel
opened,
having
a
triage
done
and
reported
back
and
documented
some
place
would
be
good.
F
So
would
the
would
the
tc
draft
this
checklist,
or
can
any
of
us
do
it.
I
I
think
we
should
add
it
on
the
create
an
issue
for
this
to
track
it
and
assign
the
tc
team
for
okay
yeah.
I
can
open
up
an.
F
I
E
Like
steve
steve,
flanders,
splunk
had
brought
this
up
with
me,
and
he
mentioned
he
was
gonna
file
an
issue,
so
he
may
already
have
one.
Let
me
just
see
if
I
can
find
it.
E
F
Morgan,
would
you
really
chat
with
steve
and
find.
E
E
E
B
I
just
threw
something
in
there.
I
was
just
looking
at
last
week's
agenda
and
I
think
we
were
going
to
create
a
issue
to
do
a
mission
and
vision
thing
and
we
didn't
so.
I
I
typed
one
up.
I
put
a
screenshot
in
our
die.
I
don't
know
if
anyone
has
issues
with
my
issue,
but
I
just
thought,
if
not
I'll,
just
violet,
let's
find
them
so.
F
B
Really
fantastic,
I
mean
the
only
thing
that's
a
little
controversial
is.
I
did
not
use
the
word
vote
anywhere
like
I
don't
think
we
should
do
a
public
vote
like
I
think,
voting
on
stuff
like
this
is
stupid.
I
think
the
gc
should
make
a
decision
and
if
people
don't
like
it,
they
can
fire
us.
Like
that's
kind
of
how
I
feel
about
this
one.
Does
that
make
sense?
I
mean
I
say
that
unapologetically
it
just
mission
vision,
don't
work
well
with
voting.
Okay,
great
I'll
file,
the
issue.
B
B
C
Yeah
they
closed
the
ticket
linking
to
some.
Is
it
detail
something
apparently,
but
I
have
no
idea
how
that
works.