►
From YouTube: 2023-02-16 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).
B
C
C
C
C
C
A
B
Cool
well,
the
first
thing
is
the
end
user
working
group
is,
would
like
to
become
e-cig
they've
Reese
posted
a
issuing
community
that
hasn't
gotten
any
action,
so
wanted
to
bring
it
up
to
governance
and
see
if
there
were
thoughts
or
if
people.
Why.
B
D
D
B
There's
you
know,
while
it's
not
you
know,
they're,
not
maintaining
a
library
the
stuff
they
do
is
very
important
to
the
project
and
we
should,
as
a
project,
probably
recognize
that
by
elevating
the
working
group
to
asig.
So
not
my
you
know
not
my
call
I
I
support
it,
but
I
just
wanted
to
bring
that
people's
attention
to
go
and
post
about.
D
I
mean
my
take
would
be
to
actually
look
at
some
of
the
models
or
kubernetes,
because
kubernetes
has
you
know,
also
specific
contributor,
six
and-
and
you
know,
related
activities
which
are
actually
done
by
the
groups.
A
lot
and
and
they're
done.
You
know
consistently
long
term,
so
yeah.
C
D
Think,
maybe
that's
worthy
of
you
know,
looking
at
as
a
comparative,
you
know
area
and
seeing
if
that's
something
we
can
also
leverage
as
a
model.
D
B
A
I
was
interested
on
that
if
we
needed
to
kind
of
revisit
how
we
Define
maintainer
and
approver,
since
those
rules,
I
are
at
least
when
they
were
defined
were
thought
of.
As
repository
like
tailored,
maybe
the
language
towards
repository
maintainership
and
Repository
approvers.
A
D
Agreed
agreed
and-
and
maybe
Trask
to
that
point,
do
you
want
to
maybe
do
an
issue
or
something
to
because
I
think
that
that's
also
related
to
you
know
a
larger
discussion
that
you
know
we
are
planning
to
have
with
the
leadership
meeting
on.
D
A
Yeah
I
could
start
with
on
just
posting
back
on
Reese's
issue
and
sort
of
asking
her
and
the
that
seek
that
working
group.
What
they,
how
they
would
see,
expanding
the
language,
the
existing
language,
language
of
maintainers
approvers,
to
fit
their
needs.
D
Good
suggestion,
yeah
trust
that
makes
sense,
I,
think
the
other
aspect
I
wanted
to
also
bring
up
and
Austin.
This
goes
back
to
you
know
the
understanding,
the
success
you
know,
metrics
of
of
what
end
user,
what
groups
or
end
user
sigs
mean
to
us
as
a
project.
Is
that
the
cncf
has
you
know
these
end
user
meetings
that
are,
you
know,
held
regularly
and
I've
been
trying
to
find
out
more
about
them?
D
You
know
to
understand
better
understand
what
are
the
you
know
what
what
are
the
focus
areas
and
purpose
of
these
so-called
end
user
meetings,
also
at
a
larger
level,
because
observability
is
very
important
aspect
of
you
know
many
end
users,
you
know
discussing
and
and
meeting
under
the
auspices
of
cncf,
and
and
could
we
actually
have
more
of
a
larger.
D
You
know
areas
of
Leverage
instead
of
the
project
itself,
having
to
go
and
do
a
lot
of
this
work
itself
right
because
again,
while
it's
good,
it's
also,
you
know:
are
we
actually
being
able
to
access
the
the
diversity
of
end
users
that
we
would.
B
D
B
Yeah
I
know
I
mean
I,
think
that's
that's
totally
valid.
I
I,
don't
wanna.
B
B
You
know
in
terms
of
like
adhesiveness
right,
like
there's
the
project,
you
know
it's
very,
even
as
large
as
open
Telemetry
is
like
the
actual
core
I
would
say,
of
open,
till
3
is
fairly
small
or
at
least
tighten
it,
and
then,
when
you
start
like
going
out
into
sort
of
the
tag
sphere
and
you
go
out
even
further
into
end
user,
various
end
user
groups
and
other
things
you
know
there,
you
are
getting
these
the
solution.
B
Are
you
getting
further
and
further
away
from
where
those
accession
discussions
can
have
impact
and
where
people
are
likely
to
be
so
I
think
there's
again,
this
can
be
part
of
a
larger
discussion
about
you
know,
roles,
responsibilities
and
whatnot.
B
I,
don't
want
us
to
just
Farm
out
I,
don't
I,
don't
think
it's
good
for
us
to
just
kind
of
farm
out
the
there
being
an
end
user,
Landing
Landing
Pad,
almost
in
in
sort
of
that
close
project
sphere
right,
because
now,
especially
that
end
user
working
group
is
starting
to
kind
of
publish
reports.
And
if
you
look
on
the
blog,
they've
got
I.
Think
two
or
three
up
now
and
getting
that.
B
So
you
know
having
a
place
is
just
like
when
someone
goes
to
open
telemetry.io
and
they
see
like
oh
Andrew's,
a
working
group
right
like
that's
a
place
that
is
easy
for
them
to
get
plugged
into
versus
going
back
out
into
the
broader
cncf
sphere.
You
know
you're,
adding
more
meetings,
you're,
adding
more
hops
between
people.
D
And
people
that
can
take
action,
I,
totally
agree
and-
and
the
point
is
that
I
think
that
it's
valuable,
very
valuable
for
the
project.
You
know
as
large
as
ours
to
be
having
these
discussions
close
to
the
project
itself
right,
but
I
think
it's
also
that
can
we
use
other
avenues
within
the
cncf
to
be
able
to
expand.
You
know
the
the
reach
to
you
know
it's
it's.
It
goes
both
ways
right.
C
B
Into
the
go
out
to
the
cncf
and
go
to
those
end
user
sessions
or
whatever
and
be
like
hey,
let's
make
sure
that
we
get
the
you
know.
Let's
make
sure
that
we
get
these
things
on,
like
the
official
cncf
calendars
and
through
the
plugged
into
the
official
cncf
community
group
stuff
and
into
the
tag
meetings
and
just
you
know,
using
it
as
a
central,
a
centralizing
place
for.
B
D
And,
and,
and
the
other
point
that
I'd
like
to
call
out
there,
is
that
you
know
again
just
to
understand
the
usefulness
of
the
even
the
information
that
you
know.
Some
users
are
sharing
in
our
end
user
groups
right
because
who
is
that
benefiting?
Is
it
other
end?
Users
is
just
another
way
of
vendors
collecting
more,
you
know,
understanding
and
on
their
potential
customers,
I
mean
again.
C
B
B
B
I
don't
know
some
of
this
is
just
like.
What
do
we
want
to
be
right?
Do
we
want
to
does,
is
the
is
the
goal
of
hotel
to
be
the
box
of
Lego
that
other
people
go
out
and
build
stuff
with,
or
are
we
you
know
do
we
do?
We
believe
that
we
need
a
product,
you
know
like
Hotel
itself
should
be
a
product,
and
it
should
have
a
good
experience
like
product
like
experience
for
installation
and
configuration.
C
D
The
more
that
can
be
organized
the
easier
it
is
for
people
to
adopt.
You
know
the
technology
that
is
being
built
on
the
project,
but
it
also
is
that,
can
we
make
it
more?
You
know
of
a
virtuous
cycle
where
you
know
and
gourmet
dinner
on
Java.
You
know
on
the
Java
agent
or
whether
that's
a
PHP
or
whether
that's
you
know,
Ruby
can
get
that
same
information.
Then
you
know
which
is
useful
to
improving
the
experience.
D
It's
not
just
to
understand
what
a
user
is
doing
with
open
Telemetry,
but
it's
also
to
see
you
know
and
understand
how
we
can
improve
our.
You
know:
user
experience
for
the
different
components
and.
A
Do
we
think
that
we're
not
getting
that
input
back
in
the
individual
like
language
Reapers,
because
I
mean
my
experience
in
the
Chavez
instrumentation
repo
we've
got.
We
got
a
lot
of
issues
from
end
users.
A
You
know
more
than
we
can
generally
keep
up
with,
so
don't
feel
like
the
feedback.
Loop
is
necessarily
missing
there,
but
I
don't
know
if
it's
different
in
other
areas.
D
No
I
would
just
say
trust
that
you
know
having
kind
of
been
involved
in
the
different
language.
You
know
communities
on
our
end
on
our
project.
It
is
varied.
Java
is
probably
the
you
know.
Has
the
richest
amount
of
you
know?
Feedback
coming
in
in
terms
of
you
know,
users
actually
actively
providing
feedback
as
well
as
anyone
using
you
know
or
having
experience
in
the
instrumentation
we're
coming
and
providing
feedback
there,
but
I
don't
think
that's
the
same
for
all
the
other
language.
Libraries
too,
we'd
like
to
see
that.
D
So
you
know
if
we
could
actually
connect
some
of
the
mission
of
the
end
User
Group,
to
provide
some
of
that
or
collect
some
of
that
technical
feedback.
Then
that's
valuable
to
the
to
the
project.
If
we
are
just
collecting,
you
know,
end
user
experiences,
I,
don't
I,
think
it's
valuable
has
limited
that
you
know
value
to
the
project.
It
has
more
value
to
vendors,
it
doesn't
have.
It
has
very
little
value
back
to
the
maintainers
and
the
contributors
of
different
components.
I.
A
Remember
one
of
Ben's
top
items
concerns
had
been
yeah,
the
user
friendliness
of
the
the
onboarding
experience.
A
B
Think
the
the
one
thing
I
would
say
just
from
or
where
I'm
sitting
is,
that
I
would
agree
that,
yes,
it's
it's,
certainly
not
equal
the
level
of
feedback
and
the
sort
of
the
people
that
are
giving
that
feedback
are
is
very
different
based
on
Sig
and
I.
Also
think
I
mean
it's
also
important
to
remember
that
there
are
the
end
user.
Open
Telemetry
is
actually
it's
a
pretty
broad,
yes
cross
sector,
you
know
cross-section
and
yeah.
B
A
good
example
is
I
was
at
the
end
user
meeting
today
and
you
know
a
lot
of
the
questions
were
from
someone.
That's
building
like
this
very
large.
You
know
internal
complementary
deployment,
and
so
the
questions
are
very
much
around,
like
Electro
scaling,
collector
right
sizing
buffering,
you
know,
and
it's
like
specific
collector
issues,
but
also
then
it's
like
okay.
B
Well,
how
do
we
manage
all
this
right
and
how
do
we
get
into
you
know
now
you're
starting
to
do
cross-cutting
stuff
around
op-amp
and
talking
about
both
collector
Fleet
Management,
but
also
SDK
management
and
yeah.
A
Do
you
know
if
it's
possible
in
the
the
end
user
or
meetings
to
know
ahead
of
time,
what
topic
topics
there
are
the.
B
B
Way
they
run
them
is
that
it's
people
come
in
and
then
like
at
the
beginning.
It's
like
a
lean
coffee
style
things
with
the
beginning
of
it.
People
will
write
questions
into
a
if
you
ever
use
like
a
retro
board,
where
you
know
people
write
the
cards
and
they're
blurred
out.
It's
that
kind
of
thing.
So
I
think
some
of
this
could
be
like
I
would
say
from
talking
to
Rhys
and
sort
of
my
involvement
with
the
end
user
stuff,
since
they
started
last
year
is
they're.
Very
you
know.
B
Certainly
would
love
you
know
would
be
willing
to
change
things
right,
like
they're
they're,
pretty
much
just
going
off
of
what
they
what
they
have
seen
from
other
groups.
What
they
think
is
right
and
what
seems
to
be
useful.
You
know
to
the
the
collection
of
people
around
them,
so
if
this
is
something
that,
like
the
government,
that
governance.
C
B
B
Then
there's
a
way
for
like
like
hey
maintainers,
you
can
go
over
here
and
ask
for
feedback
and
they
have
a
way
to
give
feedback.
It's
building
those
conduits
between
parts
of
the
project.
A
So
is,
would
it
be
fair
to
say,
as
far
as
the
end
user
working
group
becoming
a
Sig
that
there's
interest
in
that
being
clear
on
that
that
it's
not
just
a
landing
pad,
as
you
were
saying,
and
that
part
of
that
sigs
Charter
is
connecting
yeah.
B
I
think
I
mean
I,
think
that's
a
good
idea
and
I
I
think
it's
totally
fair
to
say,
like
hey
yeah,
this
is
cool.
Let's
you
know,
let's,
let's
define
exactly
you
know
the
expanded
scope
of
this
and
again
hashing
it
out
in
that
issue.
I
think
would
be
the
best
way
to
do
it,
but
that
strikes
me
as
a
and
that's
also
something
we
can
talk
about
more
in
person
too
like
or
we
can
talk
about
the
leadership
meeting
like
it
doesn't.
D
Have
to
be
decided
absolutely
I
mean
it's
a
discussion
right
and
again.
Austin
I
completely
agree
with
you
that
the
end
user
group
is
very
open
about.
You
know
again
being
able
to
tune
what
works
you
know
for
the
project
so.
B
D
I
I
think
it's
just
a
task.
You
know
to
your
point
just
working
through
with
the
group
also
and
kind
of
tuning
it
so
that
it
does
actually,
you
know
effectively
help
provide
input
back
into
the
different.
You
know,
language
groups,
as
well
as
the
collector
itself
and
other
areas
do.
C
B
B
D
We
deliberately
wanted
to
keep
the
discussions
on
slack
so
that
folks
would
benefit
from
you
know
the
the
desired
questions
that
you
know
different
folks
ask
and,
at
the
same
time,
also
not
kind
of
fragment
the
you
know
the
discussions
too
much
by
having
individual,
but
rather
you
know,
use
the
end
user
meeting
to
have
those
discussions
yeah,
but
in
terms
of
getting
feedback,
for
example
back
to
the
maintainers,
and
you
know
being
able
to
actually
be
an
effective
Channel.
D
There
I
think
we
can
totally
work
on
that
further
because
there
was
definitely
initial
intent.
You
know,
if
you
look
at
the
issue
that
we
had
filed
again.
D
B
Yeah
well,
I
also
wanted
to
update
real
quick
on
observability
today
Europe
in
our
final
three
minutes.
The
cfp
is
closed.
We
have
122
122
proposals
are
submitted,
which
is
pretty
good,
pretty
good
response
rate
yeah.
B
And
the
program
committee
is
reviewing
them
now,
I
believe
the
review
period
ends
next
Tuesday
and
then
selections
and
all
that
should
happen
and
the
schedule
be
announced
early
in
March.
B
D
Good,
so
what's
the
next
step
there
as
soon
as
it
to
just
kind
of
have
the
program
review,
yeah.
D
B
B
So
I
have
a
public
update.
You
know,
I
have
an
update
by
you
know
we'll
have
updates
before
then,
but
once
the
scoring
is
done,
I
think
that's
when
we
would
start
to
seriously
talk
about
like
panels
and
getting
a
maintainers
panel
and
so
on
and
so
forth.