►
From YouTube: 2022-09-22 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
Hello
I
think
this
is
my
fourth
or
fifth
to
last
QC
meeting.
B
C
C
B
I
think
we
have
Quorum
now
right
were
there
specific
topics?
Maybe
we
can
just
add
some
topics.
Books
of
things
to
discuss,
Ben
did
jurassi
or
worked
and
gave
you
an
update
on
on
any
of
the
election
process
or
procedures
or
anything
do
they
did.
They
need
and
I
mean
I,
think
Daniel
and
I
and
always
had
kind
of
updated
them.
We.
C
C
B
Good
yeah
yeah
no
worries.
We
were
just
wondering
if,
if
they
had
given
you
an
update.
B
So,
actually,
let
me
add
to
the
agenda.
I
had
one
topic:
I
just
wanted
to
discuss
people,
and
this
was
about
the
the
dev
stats
on
the
project,
because
I
think
that
there's
some
consolidation
and
cleanup
that
has
happened
on
the
project
stats
and
that
might
be
coming
from
cncf
itself
as
well
as
the
just
wondering.
If
you
know
we
had
recently
because
I
know
we
have
discussed
this
in
the
past.
B
We
had
recently,
you
know
from
the
TC
looked
at
what
the
current
status
of
maintainers
is
on
different
parts,
because
I
I
do
know
of
some
maintainers
who
have
stopped
contributing-
and
you
know
like
anurag,
for
example,
who
was
a
very
prolific
contributor.
You
know
from
in
in
the
last
three
years
has
is
not
contributing
anymore
right.
So
there's
a
significant
contributors,
who
have
very
you
know
not
been
contributing
to
the
projects.
I
wondered
if
there
is
a
need
for
us
to
actively
actually
go
and
also
get
other.
C
I
know
I
hear
you're,
saying
I
mean
it
seems
like,
like
the
GC
in
my
mind,
should
be
responsible,
slash
accountable
for
accurately
representing
the
sort
of
maintainer
Health,
yes
across
the
various
cigs
and
so
on
so
forth,
and
so
yeah,
it's
like
I
mean
otherwise
just
an
example.
But
if
there's
someone
who's
just
completely
they've
just
ceased
working
on
openflammatory,
that's
their
right
to
do
that,
but
they
probably
shouldn't
be
listed
as
a
maintainer
I.
B
Don't
think
the
project
has
been
pretty
good
at
doing,
because
you
know
they
are
I
am
seeing
different
teams.
You
know
actually
move
folks
to
Emeritus
and
after
three
months
of
inactivity,
which
is
which
is
fine,
but
it's
also
that
it
changes.
The
balance
of
you
know
just
contribution
as
well.
As
you
know,
maintainership
responsibilities
right.
So
it's
it's
just
that's
something
we
should
be
aware
of
as
a.
C
Yeah
and
so
I
guess,
the
second
piece
is
then
so
having
established
like
an
accurate
measure
of
sick
health
and
maintainer
populations,
and
so
on,
is
the
GC
responsible
for
like
ensuring
that
the
things
are
healthy
from
a
maintainer
standpoint,
which
I
think
is
a
totally
fine
proposal
of
what
it's
worth,
but
that's
the
second
thing
right
so
that
I
think
in
this
case
we
take
the
form
of
you
know
for
Life
a
better
word
recruiting
or
you
know
getting
people
excited
about
getting
themselves
into
that
role,
though
I
think
in
the
past,
we've
had
issues
where
it's
like
there
are
people
who
might
even
want
to
do
it
in
some
cases
and
think
in
The
Collector,
but
like
there
were
issues
around
having
the
necessary
merit,
badges
and
so
on
and
so
forth,
right
so
exactly,
but
that
that
seems
okay
to
me
as
a
concept
and
certainly
I,
think
for
the
long-term
Health.
C
The
project
is
kind
of
critical,
especially
for
the
parts
that
are
getting
more
into
well.
No
pun
intended,
like
maintenance
mode
I,
think
we're
going
to
find
it's
much
harder
to
get
maintainers
to
stay
engaged.
Fine.
Now,
if
we
agree
that
we're
going
to
take
that
on
I,
don't
see
it
working
very
well,
unless
we
have
like
specific
GC
members
assigned
to
specific
six
and
being
like
this
is
your
job
to
fix
this
one.
B
Yeah,
yeah
and
I
think
that
that's
a
good
suggestion,
because
why
not
right
I
mean
even
if,
like
you
know
as
as
something
that
I
mean
I've
I
personally
care
about
it,
so
you
know
it's
something
that
I
do
join
into
the
Sig
meetings
or
the
and
and
work
with
specific
sigs
more
actively.
B
So
again,
you
know,
even
if
each
of
us
takes
you
know
two
three,
six
that
we
follow
up
with
I
know:
Morgan
does
also
so
you
know
again.
Daniel
does
too
so.
Some
of
us
are
pretty
active.
Only
different.
You
know
with
this
different
Sig
communities
and
can
certainly
take
responsibility,
for
you
know,
making
sure
that
we
are
working
with
those.
You
know
teams
to
make
sure
that
they're
they
have
a
you,
know,
good
balance
and,
and
we
also
re-amplify
their
needs.
B
If
they're
looking
for
maintainers
and
specific
Focus
areas
or
specific
activities,
I
mean
that's,
it's
very
important
because
I
mean,
as
you
can
see,
we
have
new
initiatives
such
as
profiling,
spinning
up
very
exciting
for
the
project,
but
on
the
and
on
the
same
hand,
you
know,
even
when
SQL
commenter
was
added
to
the
project
or
historically
or
you
know,
flow
mail
was
contributed
by
you
know,
Splunk
again,
all
great
components,
but
also
very
single
threaded,
sometimes
because
you
know
the
maintainers
who
were
originally
part
of
the
project
you
know
did
help,
but
also
you
know
not
able
to
kind
of
diversify
the
maintainership
across
different.
B
You
know,
folks,
above
and
beyond
the
original
contributors
right.
So
so
that's
that's
very
important
because
then
you
know
it,
it
is
it
just
in.
Is
it
a?
Is
a
hotel
just
an
umbrella
for
different?
You
know
companies
providing
you
know
that
that
component
and
hence
you
know
putting
it
under
the
banner
of
Open,
Source
and
kind
of
doing
something
there,
but
or
it
being
a
more
General
approach
which
actually
serves
end
users.
B
B
So
I
mean
these
are
trade-offs
right
and
when
you're
looking
at
different
areas
of
technology
that
are
like,
you
know,
coming
under
a
project
as
large
as
hotels.
So
you
know
I
mean
how
do
we
better
better
manage
it
than
just
letting
it
be
right
in
its
own
organic
way?.
B
A
C
Think
the
issue
is
that
we're
not
actually
tracking
a
normal
maturity
curve.
It's
like
on
a
per
Sig
basis.
We
actually
are
we're.
You
know
we're
front
loading,
a
lot
of
the
fun
work
because
it
feels
very
Green
Field
and
then,
as
soon
as
we
get
to
the
bit,
we're
we're
actually
like
fixing
the
end
user
problems.
It
gets
very,
very
high,
friction
and
and
which
is
normal
and.
A
Many
of
the
contributors
that
are
employed
by
vendors
might
have
an
interesting
fixing
this
right,
like
also
people
who
are
end
users
themselves
and
are
empowered
to
work
on
this
right.
Like
I,
think
there
are
some
incentives
that
do
come
into
play
to
try
to
resolve
this,
but
I
agree
that
it's
also
an
acceptably
High.
C
Yeah
no
yeah,
I
I,
just
I,
think
my
issue
is
just
that:
there's
always
so
much
more
oxygen.
It's
like
bleeding
edge,
Greenfield
things
and
well
forget
it.
I,
I,
I'm,
sorry,
I,
I,
I'm,
not
trying
to
suggest
that
we
should
necessarily
cease
development
on
you
know
whatever.
We
want
to
say
whether
it's
the
profiling
stuff
for
evpf
or
whatever.
It's
not
that
I
think
they're
bad
ideas
in
as
much
as
it's
a
zero
sum
with
the
kind
of
core
promise
hotel
which
it's
not
actually.
D
A
Energy
from
outside
of
the
project
right
like
it
may
add
some
demands
to
the
current
core
signal
types,
but
you
know
I
think
that
this
is
a
mechanism
that
we're,
hopefully
we
can
get
the
interest
converted
into
interesting.
Also.
B
D
That's
one
way
to
get
people
involved,
but
at
the
same
time
that
you
challenges
that
Ben
pointed
up
are
going
to
crop
out
when,
when
we
switch
from
specification
to
implementation
exactly
because
then
it
becomes
a
little
more
zero-sum.
Potentially
because
people
like
Daniel
and
various
other
maintainers
who
are
working
on
traces
and
metrics,
now
need
to
split
their
time
with
this.
And
that's
when
I
think
the
real
pain
will
start
that
Ben's,
pointing
out.
B
Right,
right
and
and
if
we
are
not,
you
know
like
ahead
of
the
curve
in
getting
more
maintainers
or
mean
getting
more
contributors
in
those
areas,
then
it
adds
even
more
stress
to
the
existing
maintainers
and
and
that
you
know,
doesn't
necessarily
play
out
healthily
on
the
project
right.
So
it's
really
that
balance
and
and
I
mean,
as
you
see
we
need.
We
should
be
very
aware
of
that.
B
You
know,
even
if
we
are
taking
just
in
pulse
every
quarter
or
have
some
mechanisms
that
we
you
know
want
to
adopt
as
just
general
ways
of
you
know,
kind
of
understanding,
hey
you
know
this
is
these-
are
some
of
the.
C
No
I
mean
I,
I,
guess
I'm,
let
me
be
less
grumpy
about
it.
I
genuinely
am
happy
about
a
lot
of
the
I
mean
I,
also
thought
it
was
awesome
that
the
GC
and
TC
I
think
made
the
correct
decision
about
a
very
appealing,
Greenfield
thing
in
that
analytical
query
language
thing,
which
I
think
is
a
great
idea
by
the
way
it
just
I,
don't
think
it
belongs
in
hotel.
C
That's
all
so
I
think
like
we're
like
saying
no
to
like
the
correct
things
or
whatever
and
there's
nothing
wrong
with
The
Continuous
profiling,
thing
I.
Think
what's
frustrating
is
that
we're
not
doing
a
good
job
before
Elita
I
think
we're
doing
an
okay
job
with
like
the
slightly
easier
task
of
marketing
people
as
as
Meredith
or
whatever
I
mean
that's.
It's.
B
C
Universally
but
we're
doing
okay
at
that.
We're
not
doing
good
job
at
like
backfilling
and
we're
doing
no
job
actually
at
assessing
our
the
kind
of
progress
bar
I
guess
on
a
maturity
curve.
For
many.
C
C
We're
like
we
have
some
assessments
of
where
we've
gotten
in
certain
areas,
but
we're
still
like
really
far
from
the
thing
that
people
actually
adopt
hotel
for
most
frequently
and-
and
we
don't
have
a
clear,
even
qualitative
measure
of
that
that
we
look
at
as
if
you
see
like
ever
and
maybe
that's
the
thing
that
would
make
me
feel
better
about
the
the
Greenfield
initiatives
if
we
could
at
least
be
looking
at
some
sort
of
public
dashboard
on
our
website
of
like
this
is
how
far
we've
gotten
on
tracing,
metrics
and
I.
C
Guess
logs
right,
we
haven't.
We
haven't
implemented
that
yeah.
B
I
mean
we
can
certainly
pull
you
know
some
qualitative,
metrics
and
and
even
Define,
that
you
know
as
what
is
acceptable
to
us.
As
you
know,
they
could
be
even
three
three
areas
that
we
are.
You
know
kind
of
reporting
on,
but
still
you
know
being
very
cognizant
of
the
fact
that
projects
you
know
and
and
and
folks
participating
and
focus
areas
on
projects
change,
especially
on
large
projects
such
as
hotel.
But
on
the
other
hand,
you
know
also
to
be
very
aware.
You
know,
given
that
I
represent
a
big
end.
B
User
is
also
that
you
know
there
are
pain,
points
that
the
project
hasn't
addressed
from
an
end
user
adoption
perspective
and
those
are
areas
that
are
not
necessarily
actively
prioritized
on
hotel.
Yet
right.
So
what's
the?
What
is
the
intersection
there
Beyond?
You
know
us
actually
speaking
to
some
end
users,
which
we
are
starting
to
do.
What
are
some
of
those
areas
that
can
really
really.
You
know
make
sure
that
hotel
is
the
first.
You
know
collection,
choice
for
everyone
right
and
that's
that's.
A
Yeah
I
think
this
is
an
issue
that
honestly
every
open
source
project
struggles
with
right
like
how
do
you,
how
do
you
fund
ongoing
maintainership
right,
like
and
with
projects
like,
for
instance,
Apache
Kafka
right,
like
it's
pretty
clear
that
you
know
for
better
for
worse,
the
fact
that
confluent
has
paying
customers
means
that
they
can
afford
to
have
people
work
on
the
open
source,
maintainership
right
like
for
a
multi-stakeholder
project.
That
has
you
know
not
that
is
not
dominated
by
any
one
company
for
writing
commercial
support.
A
Right,
like
you
know,
I
I
think
that
the
incentives
will
work
out
in
the
long
term,
but
I
agree
that
we're
going
through
a
difficult
path.
B
Exist
if
they
don't
interact
with
the
projects
and
provide,
you
know
that
that
support
right,
because
again
it's
a
support
team.
It's
like
a
you
know
in
in
a
practical,
World,
you'd
say
Hey,
you
know
is
this
something
that
you
know
we
can
leverage
as
an
Outreach
team
or
an
Outreach
strategy
of
some
sort
right
so
I
mean
how
do
we
leverage
that
and
that's
a
larger
question?
But
the
point
again
goes
back
to
that.
B
This
is
one
of
the
roles
of
of
you
know
just
project
governance
right
where
you
are
kind
of
very
conscious
about
okay.
How
do
we
make
sure
that
this
is
something
that
always
stays
in
our
green
area
of
growth
and
and
how
do
we
ensured
that
the
project
is
you
know
successful
long
term.
B
So
I
mean
again:
I
I
think
that
one
of
the
things-
maybe
that
will
help
I
just
wanted
to
kind
of
raise
it-
is
that
I've
I've
had
discussions
with
many
other
end
users
who
are
interested
in
participating
and
also,
obviously
you
know,
other
vendors
who
are
kind
of
starting
to
get
more
involved
in
hotel
or
using
or
building
Integrations
into
Hotel
and
and
we're
looking
at.
B
You
know
how
could
we
maybe
formalize
some
way
of
thinking
about
project
health,
and
then
you
know
leveraging
that
to
pull
in
folks
to
participate
in
different
parts
right.
So
would
it
be
worth
us
actually
kind
of
doing
a
one-pager
on
this
and
seeing
hey,
you
know
what
what
are
some
of
the
areas
that
we
would
like
to
book
book
around.
B
Because
it
will
it
will,
you
know,
I
mean
this
is
something
that's
just
staring
Us
in
the
face.
The
stuff
is
changing
right
as
logging,
as
we
make
continue
to
make
more
progress
on
logging,
I'm,
hoping
that
profiling
will
pick
up,
and
this
is
also
speaking
to
Yuri's.
You
know
suggestion
of
having
more
areas
of
telemetry
data
being
incorporated
into.
D
B
B
D
Be
challenging
to
bench
Point
earlier,
but
we
can't
do
anything
unless
we
at
least
address
these
all
right.
Sorry,
unless
we
at
least
identify.
B
At
least
yeah
exactly
because,
unless
you
even
understand
them,
how
to
see
even
go
forward
from
there,
so
I
think
I
can
I
can
put
together
a
one
pager
that
I
can
actually
share
because
I've
been
thinking
about
it
and
you
know
kind
of
looking
at
it
and
then
welcome
everyone
to
kind
of
add
to
it.
B
As
we
figure
out
you
know
what
are
the
metrics
we'd
like
to
collectively
look
at
and
and,
as
you
know,
Liz
said,
Liz
is
rolling
off
the
GC
again,
but
you
know
she's
very
active
and
very
prolific
about
you
know
in
this
area
and
and
then
I'm
also
happy
to
help
so
something
that
we
all
care
about.
B
C
I
was
just
taking
notes,
but
not
really
so
yeah
I,
just
I'm
sorry
I,
missed
the
meeting.
Last
week.
I
was
hoping
to
talk
about
that.
C
The
analytical
query
language
so
to
speak,
or
whatever
it
was
called
that
got
sort
of
decided
against
on
the
TC,
as
I
mentioned
on
the
GitHub
issue,
I'm
totally
aligned
about
this
not
being
part
of
a
hotel.
That
said
I
actually
do
think
it's
a
good
idea
like
I
mean
I.
Just
don't
think
it
should
be
part
of
Hotel
and.
B
B
So
you
know
if
we
are
saying
that,
for
example,
a
query
you
know
language
is
not
a
priority
for
us.
There
still
is
a
need
for
it,
and-
and
does
that
also
mean
like
for
metrics?
Do
we
actually
support
prompt
ql
fully?
You
know
it's
like
because
that
need
exists
right.
So
what's.
A
Right,
at
least
in
the
case
of
the
prom
ql
thing
that
is
being
standardized
under
open
metrics
right,
like
people
talk
about
open,
metrics
compatibility,
it's
encompassing
query
language
compatibility
right,
so
I
anticipate
that
there
are
very
well
maybe
kind
of
satellite
products
that
spin
up
as
entirely
separate
projects,
whether
under
cncf
umbrella
or
not,
but
kind
of
you
know.
We
have
decided
that
our
Line
in
the
Sand
is
kind
of.
You
know
we
care
about
the
generation
and
standardization
of
the
Telemetry
output.
C
I
mean
I
was
going
to
say,
I
think
there's
a
couple
of
subtleties
to
it,
and
so
let
me
try
to
be
I'll,
try
to
be
concise
and
not
like
pick
favorite,
Sun
approaches
so
and
again,
not
thinking
about
what's
popular
right
now
or
whatever,
which
kind
of
came
up
at
the
end
of
that
threat.
C
So
thinking
about
this
conceptually,
the
thing
that
worries
me
and
I
didn't
want
to
muddy
the
waters
in
that
GitHub
issue
with
this
is
that
the
Telemetry
Gathering
that
we're
doing
right
now
in
otel
is
actually
like
in
terms
of
where
I
think
the
stuff
will
end
up
going
is
pretty
primitive
in
that
the
the
instrumentation
is
hardly
Dynamic.
C
The
closest
we
get
is
that
there's
some
tail
sampling
sometimes
and
then
the
collector
can
do
some
stuff,
but
the
way
this
might
work
in
the
future
is
that
the
you
know
the
observability
needs
will
be
defined.
Hopefully,
declaratively
configures
code,
probably
using
some
kind
of
query
language,
whether
it's
standardized
or
not,
and
then
I
think
in
order
to
address
what
I
perceive
to
be
fairly
Grievous
like
Roi
issues
with
Telemetry.
C
Today
that
does
like
push
it
pushes
Telemetry
decision
making
like
further
and
further
left
in
the
pipeline,
certainly
before
things
would
egress
to
the
internet
and
maybe
even
before
the
U.S
The
Collector,
and
so
there
is
oddly,
like
there's
a
theoretical
need
actually
to
like
understand.
The
analytical
needs
of
the
Telemetry
very
early
in
the
Telemetry
process,
and
then
there
are
other
things
like
you
know:
there
are
commercial
vendors
like
workout
and
the
other
one
should
help
me.
Oh
yeah,
right
light
run.
C
How
could
I
forget
I
should
be
suing
them
for
IP,
but
but
but
those
vendors,
dynamically
instrument,
the
code
also
based
on
analytical
needs
and
I
think
is
actually
really
cool
and
I
would
love
it
if
otel
supported
Dynamic
instrumentation
based
on
queries,
but
but
the
queries
end
up
becoming
like
somewhat
like
tightly
coupled
to
the
Gathering
of
telemetry
or
the
processing
and
aggregation
and
sampling
of
the
Telemetry
yeah.
C
So
I
just
wanted
to
say
like
I,
think
for
for
now
it
seemed
like
a
crazy
expansion
of
scope
for
otel,
where
we're
already
struggling
with
very
broad
scope,
but
I
did
kind
of
want
to
mention
that
there's
a
little
part
of
me,
that's
sort
of
like
oh
gosh,
like
you
know,
if
you
really
think
big
picture
about
where
the
stuff
is
going,
the
query
is
probably
do
inform
the
Telemetry
Gathering
and
it's
not
I,
don't
think
it's
a
good
idea
to
expand
our
telescope
right
now
or
even
next
year
or
whatever,
but
I
also
think
that
there's
a
real
need
for
like
declarative
configurus
code
for
monitoring,
if
not
observability,
and
if
we
do
it
right.
A
A
What's
in
a
in
a
what
what
you
might
call
it
in
a
Helm
chart
right
like
and
also
we've
seen
similar
issues
with
honeycomb's
refinery
right
where
honeycomb
is
a
finer,
is
something
that's
open
source
we're
thinking
of
voting
it
Upstream,
but
it
of
course,
has
its
own
Tomo
file
specification
right.
So
it's
yeah!
There
is
interesting
work
to
do
there,
but
I.
Don't
think
that
standardizing
it
is
a
this
year
thing.
B
Right,
right,
absolutely
and
and
but
I
think
that
again
I
think
we
are
very
fortunate
as
a
project
to
actually
have
a
Federation
of
subject
matter:
experts
in
observability,
where
you
know
we
we
should
at
least
think
about
it
right.
That
is
how
does
this?
How
does
collection
influence
you
know
querying
and
analytics
and
vice
versa
right.
A
B
A
B
We're
at
time,
but
Liz
dropped
and.