►
From YouTube: 2021-05-06 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
A
Oh
yeah,
I
see
I
see
that
oh
yep,
I
know
what
that
is,
that
is
a
accidental
middle
mouse
button
of
my
slack
for
some
reason
got
it.
E
I'm
just
kidding
I'm
running
freebsd
on
a
mac,
so
it's
fine,
true
technically
true
halloween.
She
is
the
only
one
with
agenda
items.
I
think.
D
F
C
E
E
D
Agenda
item
just
fyi
all
of
us,
including
me
who
have
action
items
please
make
sure
they're
done
and
in
the
dock
before
may
20th
and
do
a
once-over
just
to
make
sure
no
new
questions
have
popped
up
that
you
might
be
able
to
answer.
F
C
F
That
makes
sense
okay,
so
it's
there's
no
change
in
scope
or
chart
or
anything
just
nope.
A
F
H
Yeah
yeah
totally
totally
sorry
about
running
a
couple
of
minutes
behind.
So
I
just
wanted
to
you
know
kind
of
give
a
heads
up
on.
There
was
an
compliance
program
announced
by
prometheus,
based
on
the
compatibility
tests
that
they
have
been
building.
H
You
know
I
have
been
jana
and
I've
been
working
with
them
on
the
remote
right
tests
and
having
a
specification
that
you
know
we
can
actually
guarantee
interoperability
on
for
hotel,
so
based
on
you
know
that
work
that
they
released
those
test
suites
on
they
announced
this
compliance
program.
H
Tom
wilkie,
who
is
the
you
know,
who
is
kind
of
driving
this
effort
at
grifana
labs,
will
be
providing
more
details
on
what
the
formality
of
this
program
is.
But
right
now
it's
only
from
my
understanding.
It's
only
the
tests,
but
there
may
be
some
more
formality.
You
know
that
needs
to
be
filled
out
in
terms
of
being
rated
compatible
right.
So
that
applies
to
anybody
who
seeks
compatibility
status
and
I
guess
it
may
be.
It
may
be
modeled.
H
F
F
E
Yeah
I
mean
it's
pretty
self-explanatory,
I'm
just
bothering
people
about
it.
My
feeling
is
that
people
are
probably
gonna
put
it
off
until
I
say
it's
due
like
next
week
and
it's
not
so
that's
probably
what
people
are
gonna
do,
but
it
would
be
kind
of
helpful.
E
Even
if
it's
I
would
encourage
people,
even
if
it's
just
like
some
ideas
that
you
wanna
get
down
or
some
concepts.
That's
fine,
it's
just
it's
kind
of
like
a
you
know,
copying
and,
and
changing
things
is
encouraged.
I
think
just
we
just
want
to
get.
H
A
And
I
think
one
thing
I
did
want
to
bring
the
folks
attention
is
that
last
week
there
were
some
questions
about
what
a
hotel
distro
means
and
there's
some
vigorous
discussion
in
the
open,
telemetry
general
channel
on
cncf
select.
It
just
highlights
that
you
know
at
some
point
we
need
to
talk
about.
Like
you
know
what
is
a
distro
right
like
kind
of
formalizing,
this
notion
of
of
kind
of
no
it's
not
going
to
diverge
from
the
spec
right
like
these
are
convenience
wrappers
yep.
H
So
liz
again,
that's
a
very
good
question.
I
mean
ted
and
I
have
discussed
that
before
and
and
what
you
know
would
be
great
to
see-
and
we
discussed
this
that
maybe
the
tc
should
get
a
proposal
and
then
they
can
review
it
or
you
know
the
other
way
around.
Tell
us,
you
know
tell
me
what
works
for
you
guys
and
then
I
can
definitely
add.
You
know
some
of
the
assumptions
that
we
made
on
the
aws
distro
as
a
baseline
and
then
we
can
modify.
You
know
that
doc.
D
A
In
the
main
hotel
channel,
it
was
a
thread
I
I
posted
a
hey
by
the
way,
like
honeycomb
launched
a
distro.
You
know
this
week
and
then
a
bunch
of
people
had
questions
about
what
that
meant
and
like
yeah
yeah.
H
C
D
Yeah
we
should
define
what
certification
means
for
open,
telemetry
collectors
in
particular.
Is
it
compliance
with
certain
apis?
Is
it
that
they're
open
source?
Is
it
that
they're
constructed
only
out
of
certain
certified
plug-ins
there's
like
a
couple
different
directions
there,
and
as
part
of
that,
we
should
also
build
or
identify
some
tooling
for
end
users
to
construct
their
own
distros
to
to
make.
It
seem
like,
like
a
little
bit
less
weird
of
a
thing
to
do.
D
Basically,
I
think
people
have
the
idea
that
the
collector
is
like
a
thing,
and
so
they
get
weirded
out
by
distros,
because
they
they
don't
they're,
not
totally
tuned
into
the
fact
that
the
class
collector
is
really
just
a
collection
of
plugins.
H
H
Sarah,
this
goes
back
to
the
point
that
I
think
the
technical
committee.
Again
it
depends
on
who's
interested
there
I
mean,
I
know
liz
liz
would
be
probably
very
interested,
but
perhaps
you
know
also
creating
a
group
within
the
tc
with
folks
who
are
interested
in
it
like
I'm
interested
in
it,
but
you
know
I
I
can
either
make
a
proposal
or
or,
however
that
works
again.
It
is
a
mission
of
it's
part
of
the
mission.
At
least
I
consider
of
the
tc
to.
H
H
H
H
If
nobody
else
has
any
topics,
I
just
wanted
to
bring
up
one
more
topic.
I
can
add
it
also
to
the
agenda.
Is
that
again,
one
of
the
things
that
we
have
done
in
terms
of
maintainer?
Again,
you
know
in
diversifying
the
workload
of
our
core
maintainers
is
that
on
the
collector
you
know
one
of
the
things
we
have
adopted,
and
this
is
working
with
bogdan
and
tigran.
I've
been,
you
know
there
are
a
slew
of
vendor
components
in
contrib
that
each
vendor
is
interested
in.
H
You
know
having
code
owners
and
maintainers
for
and
in
agreement
with
bogdan
and
tigran,
we
have
kind
of
adopted
an
informal
process
right
now
of
two
reviews
being
done
by
non-maintainers
from
the
vendor.
So
in
aws
case
again
to
you
know,
anthony
and
anurag,
for
example,
doing
code
reviews
and
then
once
they've
completed
code
reviews,
then
a
code
approver
you
know
on
on
the
listed
code.
Owners
list
would
do
an
approve
approval.
H
Then
I
I
have
triage
rights,
so
I'd
tag
it
for
ready
to
be
merged
because
I
triaged
the
you
know,
started
triaging,
the
collective
backlogs
and
then
gradually.
You
know
once
it's
tagged
with
ready
to
merge,
then
bogdan
would
just
nudge
it
because
it's
just
you
know
very
hard
for
him
to
have
the
bandwidth
to
be
able
to
do.
You
know
so
much
and
that's
kind
of
led
to
this
backlog.
So
that's
the
process
we
are
trying
out,
but
really
would
love
to
see.
H
But
that
said
again:
that's
it's
not
a
solved
problem,
yet
we
will
have
a
whole
slew
of
you
know
new
contributors
joining
in
in
the
summer
with
our
interns
from
every
company.
So
there
will
be
a
whole
flood
at
that
point.
A
A
Think
the
last
thing
is
like,
as
you
can
tell,
we
are
starting
to
finally
underflow
rather
than
overflow,
our
meetings,
which
is
good
so
once
we're
incubated,
I
think
we
should
maybe
drop
governance
to
once
every
two
weeks
like
it
feels
like
we're
finally
reaching
that
state
of
maturity
where
things
are
no
longer
as
on
fire,
you
just
drink,
so
many
things.