►
From YouTube: 2021-05-27 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
I
I
guess
it's
you
and
me.
B
C
Look,
let
me
just
before
everyone
thinks
I'm
like
just
taking
advantage.
My
house
is
being
jackhammered
right
now
and
it's
vibrating
to
the
extent
that
like
objects
are
falling
off
our
shelves
and
like
smashing
on
the
ground,
so
I'm
like
I
mean
I
can
put
headphones
on,
but
you
wouldn't
be
able
to
hear
me.
It's
like
the
whole
house
is
just
like.
C
B
C
C
E
F
E
Week
with
some
folks
from
google-
and
I
think
google
of
all
the
companies
is
still
being
the
most
negative-
is
probably
the
wrong
word,
but
the
most
like
you
should
not
come
back
to
the
office.
Yet
awesome.
E
Person
in
a
20-person
meeting
room
still
wearing
his
mask
and
the
table
and
all
of
the
chairs
were
covered
covered
in
disposable
plastic
that
I
assume
he
was
supposed
to
throw
away
after
the
meeting
was
over.
It's
like
oh
wow,
I'm
good
at
home.
E
Actually
kind
of
slightly
weird
about
it,
like
employees,
couldn't
go
back
and
pick
up
their
stuff
at
all
to
the
point
where,
like
I've
been
gone
for
six
months
from
google,
and
I
still
they
still
have
my
mouse
and
a
bunch
of
things
that
belong
to
me.
Yeah.
E
No
one
else
there,
it
was
kind
of
weird,
so
some
of
the
firms
are
doing
that
google's
not
even
doing
that
or
if
they,
if
they
are
it's
very
recent,
because
even
even
when
I
left
in
january,
I
asked
them
like
I'm
leaving
the
company.
Can
I
please
get
my
personal
items
back?
Also
I'm
leaving
seattle.
Can
I
like?
Can
I
come
get
them
and
they're,
like
no
policy
says
no,
it's
like
really.
D
B
A
All
right
incubation
update.
A
Okay,
so
I
just
wanted
to
give
everybody
an
update.
I've
been
you
know,
following
up
with
alina
and
she's,
been,
you
know
going
through
the
dd
doc
with
cornelia,
as
many
of
you
have
seen,
but
she's
also
requested
a
meeting
in
the
week
of
june
7th
with
with
richie
from
the
observability
tag
group,
and
I
think
bartek
is
also
back
from
vacation
in
that
week.
A
So
again,
it's
a
discussion
that
I
think
it's
the
last
discussion
that
needs
to
be
happening
for
the
incubation,
a
process
to
be
completed,
and
so
I
I
will
send
out
a
doodle
poll.
I
was
going
to
do
that
last
night
to
me
and
a
friends
to
get
everybody's
availability
for
those
who
are
interested
and
and
then
I'll,
set
up
a
time
with
them.
A
So
just
wanted
to
give
everybody
an
update
and
also
heads
up
on.
Please
give
me
your
availability
so
that
you
can
get
something
scheduled.
A
And
liz,
thank
you
for
sharing
the.
I
think
the
github
link
for
open
elementary
adoption
was
pretty
cool,
so.
C
E
Well,
the
funny
thing
is,
I'm
guessing
a
lot
of
you,
viewers
of
the
blog,
probably
assume
they're
like
oh,
they
work
for
microsoft
now,
so
this
is
probably
like
some
azure
product.
I
I
hadn't
seen
like
photos
a
light
step
in
a
while,
so
I
kind
of
assumed
it
was
like.
Oh
microsoft,
tracing
solution
looks
really
nice
and
then,
and
then
liz
pointed
it
out
on
chat.
I
was
like
oh
so
yeah.
B
E
E
A
lot
of,
like
the
metrics
part,
doesn't
really
work,
and
I
was
like
yeah
okay,
true,
like
you're,
not
wrong,
and
I
was
happy
that
a
lot
of
the
most
conversation
was
extremely
positive
with
various
people
saying
like
hey,
my
company
adopted
this
and
it's
really
good,
and
I
like
that
I
was
just.
I
felt
really
proud.
A
B
C
Yeah,
I'm
just
pasting
this
thing
in
just
for
context.
This
person
who's
that
fico
emailed
just
sort
of
a
random
hodgepodge
of
people,
morgan
you're
on
that
thread
and
t
grin,
was
on
it
too
anyway.
It's
maybe
it's
not
worth
discussing
here
exactly,
but
I'm
bringing
it
up
mainly
because
what
they're
doing
is
sort
of
interesting.
It's
like
I.
I
don't
have
the
materials
in
front
of
me,
but
it's
like
a
very
elaborate
schema
for
semantic
conventions.
C
It's
not
at
all
about
like
api
changes
whatsoever,
but
it's
this
like
kind
of
they
want
to
open
source
like
a
whole
bunch
of
work,
they've
done
to
kind
of
classify
various
types
of
logging
statements
and
things
like
that.
But
it's
quite
elaborate
like
it's.
It's
a
big
schema.
So
is
this.
C
E
C
Thing
I
was
interested
in
is
like
I
mean
I
guess
we
could
sort
of
forward
this
to
the
technical
committee
like
any
other
donation.
That's
probably
the
right
thing
like,
but
the
tc,
I
guess,
is
responsible
for
deciding
on
the
semantic
conventions
too.
The
thing
that's
confusing
about
it,
though,
is
that
I
don't,
unlike
adding
instrumentation
for
kafka
or
something
like
that,
like
if
consonant
wanted
to
do
that,
it's
like
great,
like
okay
cool.
This
is
they've
done
a
lot
of
work.
C
It's
probably
high
quality,
I
mean
at
least
the
stuff
I've
looked
at
and
I
had
a
call
with
them.
It
seemed
fine,
but
I
don't
really
know
like
what
what
we
want
to
do
with
a
donation
of
semantic
conventions,
because
we
don't
want
to
have
like
multiple
different
semantic
conventions
that
are
one
are.
C
A
I
think
I
think
ben
just
to
add
I
mean
so.
The
I've
been
following
up
on
the
semantic
conventions
working
on
it
for
with
the
for
the
collectors
specifically,
you
know,
based
on,
what's
been
proposed
for
the
go
library
you
know
for
by
tyler
and
anthony
and,
and
I
think
that
it
would
be
worth
accepting
a
you
know,
their
donation
in
terms
of
just
as
a
reference,
but
you
know
again.
A
Ultimately
it
won't
be
the
same
right,
because
what
I
mean
our
maintainers
are
already
defining
those
for
the
different
languages
and
and
what's
used
for
you
know
for
us.
C
C
Well,
they
have
a
bunch
of
they
have
a
whole
repo.
That's
private
right
now
and
they're
offering
to
you
know,
provide
read
access
to
it
or
something
which
is
fine,
but
anyway,
I
I
think
I'll,
respond
on
the
thread
and
be
like
you
know.
Unless
it's
something
that's
proprietary,
can
you
just
make
the
repo
public,
so
we
can
at
least
see.
F
C
And
and
then
suggest
that
they
start
an
issue
on
the
tc,
with
the
tc
and
and
then
maybe
set
some
expectations.
That,
like
accepting
a
donation
of
a
semantic
convention,
is
not
going
to
be
as
easy
as
accepting
like
instrumentation.
Because
we.
E
Cool
that
mirrors
exactly
my
thoughts,
amazing.
Also,
if
I'm
on
the
thread,
it's
probably
my
old
google.com
email
address,
because
I
at
least
I
it's
not
in
my
inboxes.
E
C
C
Yeah,
anyway,
it's
security
group.
That's
doing
this!
It's
like
it's
all
through
that
angle,
which
is
actually,
I
think,
really
a
good
thing
for
open
telemetry
to
have
more
more
end
users
coming
at
this
from
that
angle,
but
yeah.
A
A
And-
and
I
mean
we
can
always-
you
know-
give
a
shout
out
to
them
if
there
are
areas
that
we
use
from
their
conventions.
So
that's
totally
cool.
B
Yep
so
last
week,
I
believe
open
slo
was
launched
by
the
folks
at
noble9
and
it
is
an
effort
that
is
similar.
That
has
overlap
with
us
in
terms
of
people
wanting
to
use
the
output
of
their
telemetry
to
derive
service
level
objectives.
But
I
think
that
it
is
something
that
may
fit
better
with
the
cd
foundation
and
steered
them
that
way.
F
A
Okay,
I
I
think
I
had
another
item
I
just
wanted
to.
You
know
update
everyone
on
the
follow
up
with
grafana
labs
on
the
adpl
and
the
low
key
components
in
the
collector
and
morgan.
I
think
you
had
expressed
an
interest
in
meeting
up
with
them.
I
did
reach
out
to
tom
wilkie,
so
I'll
be
chatting
with
him
next
week.
If
you're
interested,
I'm
happy
to
you
know.
E
F
E
He's
traveling
today
and
yeah
he'll
be
in
your
because
he's
I
think,
he's
heading
back
home
to
romania
for
for
like
a
few
weeks,
so
yeah
yeah
just
pull
me
in
then,
because
the
time
zone
probably
will
be
tough
with
him
yeah.
I
know.
A
But
I
mean
tom's
in
in
london.
So
again
I
think
maybe.
G
Disagreement:
it's
not
a
it's
not
like
a
personal
fight
or
anything
like
that.
Okay,
we
have
in
the
we
are
seeing
this
in
the
javascript
seg
right
now,
it's
the
first
time
we
really
run
into
this,
but
I
don't
know
if
we're
the
first
overall
to
run
into
this.
I
don't
know
if
other
sigs
have
had
this
problem.
E
G
G
So
I
was
wondering:
is
there
an
official
process
for
this?
We
sort
of
tagged
the
technical
committee
on
on
the
issue.
He.
B
G
E
G
Okay
and
then.
B
G
B
B
G
G
Yeah,
so
the
core
issue
is
with
the
context
api
and
whether
or
not
we
should
have
a
default
argument
for
the
for
the
context,
if
you're
binding
to
a
sp
to
an
event
emitter
in
javascript.
G
G
So
we
have
gotten
some
feedback
from
some
of
the
approvers
on
the
issue,
but
I
think
for
the
most
part
they're
staying
away
because
the
maintainers
disagreed
and
they
don't
want
to
be
stuck
in
the
middle
of
it.
Yeah.
E
G
But
the
reason
I
was
asking
about
an
official
process
is
because
the
reason
we
couldn't
come
up
with
with
the
framing
document
was
because
whenever
I
wrote
something
he
would
say
well,
this
sounds
too
much
like
you're
framing
it
in
a
way
that
makes
your
side
look
good
and
then,
when
he
wrote
it,
I
thought
the
same
thing
and
I
an
official
process
would
be
something
more
along.
G
The
lines
of
each
side
comes
up
with
a
document
separately
and
presents
it
to
the
tc
right
that
that
would
be
a
way
that
a
potential
proposal
for
a
process,
but
I
I
I
didn't
know
if
there
was
one
already
if
there
was,
I
would
do
that
or
if
there
isn't.
Maybe
there
should
be
one
in
the
because
this
is
unlikely
to
be
the
last
time
this
ever
happens.
E
Yeah,
I
think
you're
going
to
be
the
first
like
I.
I
helped
out
a
bit
with
java,
but
that
was
more.
It
was
less
of
a
pure
technical
issue
and
it
was
just
basically
some
maintainers
saying
we're
ready
for
1.0
and
other
maintainers
saying
no.
No,
no!
No.
We
need
to
like
clear
out
these
these
other
remaining
issues,
and
so
and
the
disagreement
was
mostly
between
people
who
worked
at
splunk.
So
I
just
sort
of
mediated
a
bit
and
said,
like
okay,
come
up
with
the
actual
ones
you
need
to
chip.
This.
C
C
C
I
don't
actually
like
the
idea
of
having
both
sides,
write
up
a
document
and
present
it
to
tc
and
have
the
tc
decide
like
the
javascript
expert.
This
is
a
javascript
issue.
I
mean
I
understand
what
I
understand
the
words
you
said,
and
I
know
what
they
mean,
but
I'm
certainly
not
qualified
to
have
an
opinion.
Nor
am
I
on
the
tc,
but
even
if
I
was,
I
still
don't
think
that
I
should
be
the
one
making
that
decision.
C
I
would
rather,
that
we
sort
of
like
have
the
process
be
more
clearly
defined
for
who
gets
to
make
a
decision
when
there's
not
consensus
like.
I
don't
think
that
we
should
require
a
consensus
among
the
maintainers
and
I
think
it
should
just
be.
I
mean
I
don't
honestly
really
have
a
super
strong
feeling
about
what
that
process
should
be
if
it's
voting
among
maintainers
and
make
sure
we
have
an
odd
number
or
if
it's
that
there's
one
sort
of
super
maintainer.
C
Who
is
the
one
who
decides
when
there's
not
consensus
or
what
but
I'd,
rather
that
there
was
just
some
kind
of
clarity
around
who
has
the
decision
making
authority?
Ultimately-
and
it
should
be
someone
in
the
maintainer
group-
because
we
do
these
things
where
you
like-
escalate
to
some
group
of
superiors
or
whatever,
that
seems
appropriate
for
certain
types
of
issues
like
more
like
community
behavior
type
of
stuff.
But
if
it's
a
purely
technical
issue,
you
know
the
maintainers
in
the
javascript
should
be
the
experts
like.
B
C
Exactly
and
that's
exactly
what
I'm
thinking
so
it's
like
so
we've,
you
know
the
tc
has
decided.
These
are
the
people
who
make
decisions
about
javascript.
This
is
a
javascript
issue,
so
let's
just
help
them
like
have
a
it's
not
like
a
you
know,
one
person's
word
versus
another,
and
it's
just
like
yeah.
The
sign
on
the
wall
says
that
it's
majority
vote
of
maintainers
when
there's
a
conflict
and
or
whatever
I
mean
I
and
then
it
doesn't
become
like
a
power
play
or
something
it's
just
like
these
are
the
rules.
C
A
Especially
on
a
language
specific
issue,
I
mean,
if
it
was
something
generic
like
cross
repo,
you
know
impact
on
on
a
technical
decision
then
make
sense
to
go
to
the
pc.
F
G
B
I
anything
it
also
behooves
us
to
explain
that,
like
in
the
case
that
that
there
is
a
decision
that
is
majority
vote
right
like
we
owe
it
to
each
other
to
come
in
and
disagree
right
that
that
is
kind
of
hard.
I
think
that's
where
the
gc
has
has
the
role
to
save
right
like
these
are
community
standards
right
like
we
are
trying
to
move
constructively
as
a
project,
not
everyone's
going
to
agree
with
everything.
C
That
seems
to
be
the
question,
so
is
it
possible
at
least
agree
on
what
the
decision
is
and
that
there
are
these
two
options
that
we're
deciding
between,
and
I
mean
it
seems
like
there
does
need
to
be
some
kind
of
multiple
choice
test
that,
like
maybe
like
the
process,
could
be
when
there's
a
real
conflict
like
this.
C
The
maintainers
have
to
agree
on
what
the
decision
is,
whether
they
agree
on
the
framing
or
not,
but
at
least
like
what
are
the
you
know,
end
choices
that
we
have
here
and
then
I
mean
I
would.
I
would
propose
that
that
we
have
a
a
just.
You
know
majority
rules
kind
of
maintainers
vote
to
make
a
decision
about
something
like
this,
but
you
just
need
to
have
the
choices
be
articulated
and
I
wasn't
sure
if
by
saying
the
framing
couldn't
be
agreed
upon,
can
at
least
the
choices
be
agreed
upon.
G
C
C
B
B
C
Majority
vote
come
in
and
disagree
so
if
the
tc,
if
there's
if
there's
a
split,
then
the
tc
gets
one
vote
to
resolve
the
the
decision.
Okay,
I
like
that
okay
cool
I'm
happy
to
write
that,
like
you
know
soon
like
today,
or
something
as
a
pr
against
whatever
md
file
should
be
in
the
community.
Repo
of
that
proposal.
G
C
Just
to
keep
things
simple,
I
think
I'll
propose,
rather
than
getting
condorcet
and
all
this
crap,
just
like
the
maintainers
have
to
vote
on
the
create
a
github
issue
documenting
the
choices.
Maintainers
all
have
to
record
a
vote
as
a
comment
on
that
issue
or
whatever
and
then
that'll
be
yeah.
Sound,
good,
okay,
yeah.
B
And
I
think
that
resolves
the
issue
of
how
is
this
document
right?
That's
that's
why
I
wanted
something
written
up.
It
wasn't
that
you
know.
Oh,
you
know
the
keys
needed
to
make
a
decision.
It's
a
like.
We
should
be
documenting
what
we
do
for
the
sake
of
you
know.
If
there
is
a
future
need
to
refer
back
to
it,.
C
Yeah,
which
md
duck
should
the
speed.
We
think
this
is
it's
kind
of
tech,
community
tech
committee
charter,
but
this
is
where
are
the
cigs
documented
from
a
process
standpoint
as
community
membership
or
something
yeah.
B
We
talk
about
the
role
that
maintainers
play,
so
I
think
it's
community
membership
yeah.
A
Yeah
man-
I
I
assigned
you
to
do
an
action
night
about
that
on
the
talk
right,
all
right,
then,
and
again,
if
you're
are
we
done
with
this
discussion?.
A
Yes,
okay,
so
just
wanted
to
bring
up
an
interesting
discussion
that
is
ongoing
right
now,
and
I've
been
part
of
is
the
real
user
monitoring.
You
know
support
in
open,
telemetry
and
really
looking
at.
If
that
can
be,
you
know
if.
B
A
It's
it's
actually
an
event
type
liz
because
introducing
you
know
a
data
model
edition
as
well
as
discussion
around.
You
know.
How
can
really,
how
does
how
does
real
user
monitoring
actually
get
handled
in
in
the
open,
telemetry
collection
pipeline
right?
That
is
yeah.
B
Exactly
I
think,
I
think
that
ladder
bit
feels
like
it
is
a
kind
of
data
governance
type
issue
which
is
is
particularly
interesting.
I'm
not
yet
sure
that
I,
I
think
that
we'd,
we
would
have
a
lot
more
opposition
kind
of,
or
at
least
like
scope
creep
concerns
over
real
user
monitoring,
like
as
a
as
an
additional
signal
right,
but
I
think
that
saying
you
know
it
is
a
kind
of
tracing
or
is
a
kind
of
login
right
that
fits
in
with
existing
data
data
types.
We
just
need
to
think
about
how
it's
ingested
yeah.
A
I
mean
I
mean
yes
and
no,
because
I
think
that
and
then
I've
been
you
know,
there
are
several
stakeholders
who
have
been
actually
working
on
specific
implementations,
specifically
even
splunk
has
been,
and
I've
been,
you
know,
looking
at
and
aws
has
been
also,
obviously
so
one
of
the
things
that
we've
gone
back
and
forth
with
tigran
on
you
know
if
he
could
actually
use
the
existing
logging
model
in
the
way
that
it
is
existing
today
it
cannot.
A
I
don't
think
it
actually
satisfies
many
of
the
use
cases
that
rum
has
so
we
again
it's
a
discussion
right
and-
and
it
really
is
evaluating.
Ultimately
we
may
say:
okay,
we
can.
This
is
how
we
can
handle
it
with
the
existing
signals,
but
that's
the
discussion
that
we
need
to
have
and
there's
no
forum
necessarily
for
it,
because
the
log
you
know
sig
is
actually
much
larger
than
just
focusing
on
this
area
and
it
might
be
wise
to
spin
up
a
work
group
like
we
have
done
with
prometheus.
A
A
A
They're
taking
place,
I
think,
off
band
on
slack
as
well
as
on
it
came
up
in
the
collector
discussions.
It
came
up
in
the
spec
sig.
It
came
up
in
the
log's
sake.
Obviously
this.
B
B
Is
precedent
with
regard
to
the
land
and
so
realistic
to
think
about
it
that
way,
yeah.
A
Yeah
exactly
that's
why
liz
I
was
thinking
of
you
know
a
work
group
that
is,
you
know
just
focusing
on
that
and
then
giving
recommendation,
or
you
know
back
to
the
larger
spec
rig
and
the
maintenance.