►
From YouTube: 2021-09-30 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
C
F
Hey
yep
yeah,
I'm
happy
to
see
this.
I
still
feel
like
my
the
point
I
made
in
that
issue
stands,
which
is
I'm
a
little
concerned
that
tc
members
may
just
be
spread
thin
with
like
a
bunch
of
other
commitments
and-
and
if
that's
the
case
then
you
know
like
no
amount
of
process
will
will
help
them
keep
up
with
the
workload
yeah.
But
I
think.
B
Yes,
I
I
agree,
I
mean
again,
I
think
that,
with
the
with
the
scope
that
exists
and
or
maybe
needs
to
exist
with
the
tc,
I
think
they
have
spread
way
too
thin.
So
they
either
we
get
more
folks
to
participate
in
different
subgroups.
B
A
Yeah,
I
was
I,
I
agree
that
some
of
the
challenges
of
just
people
being
spread
thin
will
probably
not
disappear
and,
like
I
it's
interesting,
I
noticed
like
tigran
was
the
person
who
did
all
the
work
to
post
this
and
call
it
everything,
and
he
I
happen
to
know-
is
very
spread
thin
left
between
a.
A
Even
just
within
open
telemetry,
frankly
with
being
the
the
primary
maintainer
on
the
collector,
as
well
as
on
the
tc,
so
that
that
probably
won't
vanish,
but
still
it's
good
for
them
to
apply
more
structure
here,
because
I
I
I
will
say
like
anarag's
original
message,
really
resonated
with
me.
There's
the
past
there's
been
a
lot
of
opacity
with
the
tc's
responsibilities,
their
timeliness
and
other
functions.
B
F
Making
it
super
clear
what
everyone
like
what
the
expectations
are,
helps
us
then
be
able
to
like
talk
about
yeah,
whether
you
know
the
the
group
needs
more
people
power
to
meet
those
expectations,
or
you
know,
should
we
I
mean
the
other
thing
to
to
look
at
is
like.
Is
it
possible
to
free
for
the
tc
members
who
have
a
lot
of
other
hotel
commitments?
A
A
Leaders
instrumental
in
this
actually
in
that
in
and
thank
you
for
the
salary
to
like
banging
the
drum
about
the
collector
in
particular,
which
I
think
only
had
just
tigran
and
bogdan
as
maintainers.
For
a
long
time.
A
Which
led
us
with
a
really
low
bus
factor
for
critical
part
of
open
telemetry,
so
there
we'll
be
adding
more
maintainers
there,
which
hopefully
will
reduce
the
load
on
tigran
and
bogdan,
so
they
can
focus
more
on
the
tc
yeah
yeah.
G
B
You
know,
but
the
the
bus
factor
on
the
maintainership
still
exists
until
we
can
continue
to
relieve
it.
I
mean
our
prs:
are
you
know
that
is
prs
in
the
community
are
just
backed
up
for
weeks
now
so
yeah.
B
Stats
for
that,
even
in
the
dc
and
ted-
and
I
have
discussed
this
morgan,
you
and
I
have
discussed
this-
is
that
just
having
that
visibility,
that
what
is
the
current
you
know
we
can
automate
all
this
where
we
can
get.
You
know
like
how
long
are
the
pr
sitting?
How
long
are
you
know
the
reviews
taking
all
this
information
can
be
available
to
the
tc
to
assess
right
and
plan
accordingly.
B
And-
and
this
also
goes
back
to
you-
know
again-
building
trust
and
continuing
to
build
trust
with
our
larger
community.
Our
users,
are,
you
know,
developers
who
are
who
are
investing
in
contributing
to
the
project
and
continuing
to
maintain
that
momentum
right,
because
the
hotel
is
very
lucky
today
to
have
both.
You
know,
stakeholders
from
the
vendors
as
well
as
from
end
users
and
big
users
to
you,
know
give
feedback
participate
in
and
contribute.
A
All
right,
the
next
topic
is
the
ebpf
recommendation,
so
we
had
spun
up
a
temporary
sig
on
at
the
behest
of
the
technical
committee
in
response
to
the
donation
from
splunk
about
their
flomel
ebpf
collector
I've
been
involved
to
an
extent
I've
joined,
maybe
half
their
calls,
it's
mostly
being
led
by
yana
from
aws
jonathan
from
splunk
and
a
gentleman
from
datadog
mike
michael.
I
think
yeah.
A
From
from
datadog
and
there's
a
few
others
as
well,
but
those
three
are
the
the
core
contributors
from
talking
to
jonathan.
They
expect
their
doc
to
be
in
today
looks
like
they're
gonna
recommend
that
it's
accepted,
but
I
think
we'll
wait
for
the
final
doc.
I
talked
with
sergey
sergey
said
the
tc
because
they
commissioned
a
group
just
plans
to
just
accept
whatever
the
group
says.
A
Was
on
the
call
like
two
weeks
ago
three
weeks
ago,
it
seemed
then
and
I've
chatted
with
jonathan,
since
because
he
was,
he
was
asking
for
some
guidance
but
like
it
seems
like.
A
Basically,
they
want
to
accept
it
with
the
initial
use
case
of
it
being
very
focused
on
just
capturing
more
network
telemetry
for
the
collector
and
then
over
time,
extending
it
to
become
more
generic
to
be
used
for
other
ebpf
use
cases,
but
initially
it'll
be
pretty
focused
on
network
telemetry
and
they
wanted
to
fit
with
all
the
existing
hotel
semantic
conventions
over
time.
They
may
have
requests
for
more,
but
they
didn't
want
to
rock
the
boat
on
that
right
now
and
and
create
more
specs
and
things.
B
Awesome
yeah,
I
mean
the
semantic
conventions
on
that.
Don't
are
you
know
a
big
part
of
all
the
work
that
is
happening
both
on
the
on
all
parts
of
the
project
and
and
especially
the
collector
and
the
goal
live.
You
know
maintainers
have
been
driving
that
for
which
is
which
is
really
great.
We
have,
you
know,
done
a
lot
of
work
in
that,
but
with
instrumentation
also
picking
up
steam,
there
is
an
specific
interest.
B
You
know
from
microsoft,
maintainers
as
well
as
us
and
others
to
kind
of
really
identify.
You
know
clear
semantic
conventions
for
different
categories
of
instrumentation
and
in
in
and
continue
to.
You
know
improve
the
spec,
so
that's
work
in
progress,
I'm
I'm
guessing
that
the
ebpf
you
know,
network
telemetry
conventions
will
also
intersect
with
that.
A
And
I
didn't
answer
the
notes,
but
I
also
joined
the
rum
sig
call
yesterday.
A
That's
kicked
off
I'll,
probably
be
involved
in
that
a
bit
early
on.
I
wasn't
planning
on
it
because
I
don't
actually
like
I
work
on
splunk,
open,
telemetry
confusions,
of
course,
but
like
I'm,
not
that
involved
in
our
rum
stuff,
but
there
aren't
a
lot
of
existing
hotel
community
members
there
with
a
lot
of
new
people,
and
I
got
feedback
from
several
after
they
left
saying.
We
could
use
some
guidance
for
the
next
few
weeks,
so
I'll
be
there
for
the
next
few
weeks,
at
least.
B
Want
to
you
know
also,
we
have
a
whole
team
which
is
actually
working
on
ram,
so
I'd
like.
A
B
A
Did
not,
and
one
of
my
action
items
was
to
ask
you
if
you'd
be
willing
to
come
daniel
for
you
or
someone
else
from
the
jsc
to
come
next
week.
C
Yeah
I
can
come
next
week.
The
person
that
I
would
ordinarily
send
is
bart
from
lightstep
and
he's
on
vacation
for
two
weeks,
so
I
can
come
for
at
least
this
next
week.
Perfect
and.
A
E
That's
a
kind
of
dumb
question
about
the
rom
group.
You
know.
Sorry
if
this
is
annoying,
I'm
just
better
to
do
is.
E
That's
good
yeah,
that's
synthetics,
that's
synthetic!
No!
It
just
like
so
far.
We've
we've
been
talking
about
telemetry
and
not
about
observability.
That's
and
rum
is
an
application
of
the
data.
I'm
sorry.
This
is
super
pedantic,
but
it's
kind
of
important
because
we're
not
god,
help
us.
I
don't
think
we're
building
a
wrong
product
with
an
open,
telemetry
we're
talking
about
capturing
data
from
clients.
Yes,
can
we
call
it
that?
I'm
sorry?
This
sounds
pedantic.
I
just
don't
want
to
confuse
people
because
I
know
with
open
tracing.
E
E
E
And
I
just
don't
want
people
to
get.
I
mean
the
fact
that
it's
within
open
telemetry,
I
think,
will
be
somewhat
helpful.
But
it's
just
yeah.
The
data
collection
from
clients
is
a
subtle
thing
for
lots
of
good
reasons,
and
I'm
glad
that
there's
I'm
very
happy
to
see
a
focused
group
on
that.
For
lots
of
you
know
there
are
lots
of
reasons
for
that,
but
yeah,
just
if
it's
not
too
late
to
issue
that
it's.
E
C
B
B
Interesting,
okay,
I
think
that's
only
one
of
the
parts,
though
I
mean
the
collection
and
standardization
and
intersection
with
the
you
know
the
data
signals
that
are
existing
in
the
project.
There's
been,
you
know,
discussion
about
events,
you
know
and
what
are
events
so
again.
I
think
it
will
get
more
detailed
than
just
conventions,
but
yeah.
E
E
They
they
already
have
some
kind
of
side
channel
to
get
data
from
the
mobile
app
into
their
telemetry
pipeline
and
they
need
to.
They
need
to
shunt
this
through
that,
because
you
really
want
to
minimize.
D
E
H
E
Can
help
factor
out
that
problem?
That's
huge,
huge,
huge,
huge
and
it's
totally
about
telemetry,
but
it's
way
more
than
a
conventional.
I
don't
think
that
should
be
a
v1
thing
necessarily,
but
I'm
just
saying
like
I.
I
don't
think
the
scope
should
be
limited
to
semantic
conventions.
I
just
don't
think
we
should,
but
the
analysis
of
the
data
yeah.
D
F
Yep
yeah
and
pray
your
earlier
point,
then
perhaps
we
should
call
it
molasses.
Since
that's
what
you
make
rum
out
of.
F
Yeah
I
I
actually
do
have
like
a
real
point
relative
to
not
rum,
but
this
came
up
in
is
coming
up
in
the
instrumentation
semantic
working
groups,
especially
getting
into
messaging
we're
starting
to
use
links.
F
This
is
more
of
like
a
tc
thing,
but
I
might
just
mention
it
that
one
thing
I
think
that's
kind
of
critical
there
is
is
some
amount
of
like
expectation
about
what
a
reasonable
storage
implementation
would
be
for
the
kind
of
data
we're
producing,
and
you
know
I
can
see
that
it
might
be
fairly
trivial
for
rum
but
like
if
we're
going
to
like
start
using
links
to
create
like
a
big
graph
of
traces
connected
to
each
other
right
like
how
we
propose
to
do
that
should
match
up
with
some
thought
about
how
we
expect
people
to
to
store
that
data,
at
least
like
in
terms
of
like
the
parameters
like
how
big
do
you
expect
that
graph
to
be
able
to
get
before
it's
unreasonable
and
stuff
like
that?
F
A
E
Good
yeah,
I
mean
I
appreciate
all
the
comments
from
folks
here
and
then
also.
There
are
a
few
faults
from
just
I
put
that
note
in
the
main,
open
country
slack
that
it
made
some
comments
but
they're
all
like
very
local.
I
mean
I'll
go
through
them
this
afternoon.
I
was
waiting
to
see
if
anything
else
came
in.
That
was
more
of
like
a
record
scratching
thing,
but
there
wasn't
anything.
I
did
want
to
mention
that
you
know
sergey
and
I've
assumed
others
like
put
some
work
into
the
values
doc.
E
I
really
like
significantly
paired
it
back
for
this.
No
one
seemed
to
strenuously
object
to
that
because
I
think
there's
an
effort
to
just
make
it
shorter.
Basically,
but
that's
the
I
mean
I
was
sort
of
expecting
someone
to
say:
oh
well,
we
missed
this
important
point
or
whatever,
but
I'm
planning
on
just
like
resolving
the
comments
that
are
there
today
and
then
putting
out
a
final
kind
of
apb
like
hey
anyone.
E
If
you
want
to
make
a
comment,
this
is
your
chance,
but
I
was
hoping
to
merge
it
like
early
next
week,
assuming
there
are
no
further
kind
of
concerns
about
it
and
then
I'll
follow
up
with
another
pr
to
actually
link
to
it
and
make
sure
it's
visible
and
stuff
like
that.
If
you
want,
I
can
put
that
in
the
single
pr,
but
I
kind
of
like
the
idea
of
just
getting
the
doc
in
there
and
then
having
a
separate
one
to
handle
all
the
references,
but
so
that's
kind
of
the
status.
E
A
B
Yep,
I
agree
so
ben
once
this
is
published
next
week,
then
we
should
definitely
link
it
from
our
site,
but
probably
make
it
also
visible.
As
a
pinned,
you
know
if
we
can
pin
it
in
different
on
our
github
org.
That
is
there
a
way
of
doing
that.
Do
we
have
the
ability
to
do
that.
E
E
B
A
B
E
E
The
review
got
it
okay
and
then
and
then
for
the
open,
telemetry
github
organization.
If
I
mean,
if
I
guess,
one
thing
we
could
do
would
be
for
the
org,
not
for
the
repos
we
have,
I
I
don't
know
it
might
be
a
little
too
prominent,
but
there's
the
one
liner
I
mean
I'm
just
I
can
share
my
screen,
but
there's.
E
There's
this
I
mean
there's
this
text
right
here,
like
I
don't
know,
if
you're
allowed
to
probably
not
allowed
to
put
links
into
that,
so
we
can't
put
it
there.
A
C
C
B
E
Yeah,
okay
yeah,
I
can
see
if
I
can,
I
don't
want
to.
I
guess
I
don't
get
to
have.
I
only
have
this
kind
of
crap
since
no
one
reads
these
things.
Well,
I'll.
Do
this
on
my
own
time,
but
I'll
I'll
figure
out
if
there's
a
way
to
get
like
it
would
be
awesome
if
it
was
a.
You
know
like
that
actual
hyperlink,
where
I
could
have
just.
E
G
F
C
But
not,
as
you
know,
maybe
not
a
mailing
list,
but
you
know
there's
a
reason.
Mailing
lists
exist.
I
suppose
it
is.
H
A
E
A
Then
our
announcement.
D
H
D
H
D
E
We're
losing
two
people,
no
matter
what
what's
the
so
I'm
just
helping.
What's
the
deadline,
liz.
E
E
F
B
I
was
bogdan's
not
here
today,
but
wachten
was
saying
he
would
he'd
like
to
focus.
A
G
B
A
Had
also
said
that
so
we
it
made
there's
a
possibility,
it
ends
up
being
me
from
splunk.
We
may
get
other
people
to
run.
I
don't
know
we'll
have
to
figure
it
out.
B
And
also,
I
think,
punya
had
said
he
will
file
an
application
good.
A
B
You
know
it's
it's
difficult
to
be
focused
on.
B
Okay,
there's
any
other
guidance
in
terms
of
anything
else
that
we
need
to
do
for
the
election.
Do
should
messaging
should
be
nope.
D
We
may
need
help,
we
don't
have
the
list
of
eligible
voters,
yet
we
need
to
work
on
that.
That's
the
main
thing.