►
From YouTube: 2022-02-03 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
A
C
How
is
our
recovery,
I
heard
you
you've,
got
you've
got
covered.
Oh.
B
Yeah
it
was,
it
wasn't
bad.
Luckily,
you
know
I've
been
vaccinated,
so
it
was.
It
was
a
mild
case,
and
but
we
got
stuck
staying
out
at
my
step-dad's
farm
in
hawaii,
because
we
had
to
change
our
plane
flights,
which
you
know
there
are
worse
places
to
be
stuck
so.
B
Yeah
yeah
luckily,
but
it
was
very,
it
was
surprising.
You
know
we
had
like
a
family
christmas,
small
christmas
gathering,
maybe
eight
or
nine
people
and
pretty
much
pretty
much.
Everybody
got
it
and
we're
all
vaccinated.
So
you
know
that
omicron
strain
really
is
virulent.
C
B
I
suspect
it's
actually
understated,
because,
because
the
symptoms
are
not
that
bad,
especially
if
you're
vaccinated,
I
suspect
it's
hard.
B
Test
at
least
yeah
yeah,
and
also
when
I
I
got
a
pcr
test
and
yeah.
I
definitely
had
it,
but
it
came
up
negative,
as
did
for
several
people
in
my
crew.
So
and
I've
read
some
stuff
about
that
as
well,
that,
like
the
omicron's,
not
because
it's
it
doesn't
hang
out
in
your
nose,
essentially
as
much
as
the
other
variety.
The
the
pcr
tests
aren't.
E
E
All
my
friends
at
google
they
got
the
google's,
give
them
out
for
free
to
all
employees
and
like
like
something
like
a
thousand
dollars
of
tests
a
month
to
every
employee,
so
yeah
I've
been
bought,
my
own
machine
and
I've
been
sort
of
begging
and
pleading
and
cajoling
my
googler
friends
to
give
me
some
of
the
tests,
because
I
can
put
them
in
mine.
F
B
All
right
do
we
have
any
agenda
for
today.
F
E
Some
of
them
have
come
along,
so
daniel
had
his
two
prs
into
the
community
repo,
I
believe
both
have
now
been
merged.
One
of
them
was
merged
a
few
days
ago,
and
I
checked,
I
think
the
second
was
about
to
be
so
that
was
the
requirements
or
description
for
what
does
it
mean
to
be
a
maintainer?
Here's
an
example
of
how
the
process
should
work
for
a
sig.
E
I
think
that
one
was
merged
and
there
was
a
he
updated,
the
one
of
the
reviewer
one
as
well,
so
that
should
be
done.
I
need
to
check
in
with
bogdan
and
tigran
about
where
they
are
with
the
maintainer
thing,
because
that
I
think
today
was
two
weeks
after
we
last
met,
so
that
should
be
done
today,
so
I
will
circle
back
with
them,
because
I,
as
far
as
I
know,
nothing's,
come
out
of
that
from
them.
C
But
is
that
all
I'm
trying
to
find
here
to
know.
C
It
the
one
on
20th
two
weeks
ago.
H
C
H
The
only
one
that
is
left
so
I'm
hoping
to
you
know
get
that
up
for
review
next
week.
H
A
C
I
see
okay
yeah,
let's
see
there
so
what
privileges
role
should
they
have?
Okay,
antonio,
propose:
okay,
all
right.
C
C
Does
anyone
of
the
meeting
have
stock
from
the
me?
I
found
it
on
the
invitation
really.
So
the
meeting
notes
are
attached
to
the
generation.
C
C
Then,
on
the
20th
there
are
those
two
items
in
there.
H
I
think
again,
let
me
just
pull
up
the
maintainers
jurassic.
Do
you
have
the
link
for
the
maintainers
here
that
daniel
filed
it.
H
You
specifically
I'll
I'll,
have
to
look
up
the
notes,
but
the
idea
was
that
again,
it
was
just
esta
proposing
a
a
brief
process,
for
you
know
how
to
become
an
approver
and
having
concrete
steps
there.
That
was
the
action
item.
I
H
G
G
B
H
I
think
the
question
I
had
from
morgan
and
ben
and
folks
who
were
in
that
discussion
were
was
that
so
once
this
is
posted,
was
the
idea
to
actually
discuss
this
in
the
maintainers
sync,
the
maintainers
meeting
on
monday
yep.
H
E
H
Okay,
did
we
have
other
agenda
topics
because
I
think.
H
I
didn't
get
to
fill
it
up,
but
my
action
item
or
agenda
item
was
to
actually
discuss
what
we
want
to
do
for
kubecon.
I
know
jurassic
had
brought
up.
You
know
kubecon
europe
and
that's
coming
up
in
may
so
hopefully
some
of
us
will
be
able
to
participate
and-
and
I
think
that
it
would
be
a
really
cool
thing-
to
actually
get
our
cool
open,
telemetry
community
together.
I
Okay,
I
will
think
quick
thing
by
the
way.
I
Did
you
see
the
new
capability
of
github
to
add
new
roles?
So
remember
we
had
the
triager
staff
roles
yeah.
Let
me
present
they
have
a
capability
now
to
add
custom
roles
for
for
this,
which
may
be
interesting
because
sometimes
we
had
limitations
on
the
triage
not
being
able
to
add
labels
or
things
like
that,
so
we
may
tune.
We
may
create
our
own
roles
for
for
our
own.
That's.
I
Probably
yes,
we
can.
We
can
downgrade
a
bit
approver
from
from
having
all
the
all
the
things
anyway,
I'm
not.
E
E
Now
that
we're
that,
I
believe
we
get
guaranteed,
this
is
the
main
trainer
maintainer
track
sessions
and
and
other
sort
of
guaranteed
placement
that
we
didn't
necessarily
get
before,
and
so
I
at
least
elite.
I
don't
know
if
someone's
reached
out
to
you
no
one's
reached
out
to
me,
but
I.
C
Yes,
so
they
typically
send
out
an
email.
I
think
they
should
have
sent
one
already,
but
I
can
I
can
check
that
out.
I
can
check
that,
but
they
typically
send
an
email
asking
for
if
you
want
to
participate
in
the
project
pavilion
for
the
event
or
if
we
want
a
project
booth
at
the
you
know
in
real
life
or
if
you
want
both
and
the
same
for
for
the
maintainers
track.
C
So
if
you
want
to
have
anything
there,
maintenance
track
is
it
was
typically
two
two
sessions
so
two
times
30
and
they've
changed
that
because
we
have,
we
are
so
many
projects
now
and
now
it
is,
I
think
one
yo.
Do
you
remember
how
was
it
last
time
for
cubeco
for
kubecon
one
for
30
minutes
or
145
minutes?
Do
you
remember.
C
G
C
Yeah,
so
those
are
the
three
options,
typically
so
virtual
booth
and
or
maintainers
track.
H
H
One
of
the
things
we
should
do
is
you
know,
given
that
ted
actually
put
out
the
nice
o'reilly
book
as
well
as
some
of
the
other
publications
that
have
been
happening
around
open
telemetry.
We
should
definitely
use
the
opportunity
to
distribute
or
circulate,
and-
and
we
should
have
you
know-
physical
copies
as
well
as
pdfs,
maybe
that
we
can
give
out.
B
Yeah,
oh,
it's
a
report,
so
it
doesn't
get
in,
doesn't
get
an
animal,
but
here
I
can
give
people
a
direct
link
to
the
pdf.
J
A
B
It's
the
book
does
not
it's
not
a
book,
it
doesn't
doesn't
cost
money,
though,
by
giving
you
all
direct
links,
then
you
you
will
not
be
spammed
by
lightstep
marketing.
So
I
suppose
that's
awesome.
H
No,
I
I
cannot
believe
that
lightstep
marketing
doesn't
have
all
hotel
emails
anyway,
you
have
already.
B
To
have
have
one
of
those
I
assume
enough
of
us
will
be
there.
I.
H
Ted,
I
mean
one
of
the
things.
At
least
this
we
did
very
regularly
at
oscon,
as
for
other
open
source
projects.
Is
that
whenever
we
have
like
a
book,
you
know,
and
even
a
short,
you
know
brief,
like
the
one
that
you
did.
Yeah
just
have
the
o'reilly
boots.
Typically,
you
know
actually
host
sessions
which
you
can
be
available
for,
and
you
know
have
have
like
a
presentation.
Brief
presentation,
also
a
bunch
of
copies
of
the
book
too,
so
having
a
booth,
has
advantages
for
sure.
Yeah.
B
I'll
just
I'll
I'll
double
check
with
with
white
step
marketing,
because
we
ordered
a
bunch
of
copies
of
it,
and
I
assume
we
will
have
a
physical
presence
there.
But
let
me
confirm
with
people
that
that's
happening,
but
if
so
yeah
we
can
definitely
definitely
bring
physical
copies.
I
don't
think
o'reilly
is
going
to
provide
physical
copies
for
us
for
free,
sadly,
but
now.
B
E
So
it
sounds
like
we
want
to
do
a
booth
to
tell
cncf
as
a
as
this
type
of
product
project.
We
want
a
booth
and
that
we
also
want
to
take
advantage
of
whatever
maintainer
track
sessions
are
available,
sounds
like
it
might
only
be
one
these
days,
but
that's
fine.
E
So
how
do
we
previous
funny
previous
kubecons
they've?
Always
at
least
I've
always
gotten
emails
from?
I
think.
H
E
C
Yeah,
just
to
make
sure
just
being
the
person
that
I
that
I
have
in
mind
and
asking
what
is
the
timeline?
What
were
the
plans,
because
I.
C
One
over
the
past
couple
of
weeks,
so
I.
E
C
So
if
we
go
back
to
the
tree
slack,
I
think
it
is
the
same
day
that
I
posted
a
message
on
slack.
H
C
E
E
E
E
F
E
C
That
might
come
out
later.
C
So
the
deadline
to
review
yeah,
so
the
deadline
to
review
the
talks
was
january
31st
for
for
the
reviewers.
So
I
think
it's
gonna
take
a
few
more
days,
yeah,
that's
typically,
two
or
three
weeks
after
that,
then
the
the
the
chairs
of
the
track.
They
would
then
review
the
reviews
and
select
the
final
or
make
a
close
to
a
final
selection
and
then
the
event
chairs
would
then
pick
up
the
final
ones.
H
All
right,
what
else
is
coming
up
so
morgan
is?
Are
there
any
plans?
I
think
we
had
drafted
a
blog
post
for
the
metrics
update
earlier
I
mean
at
least
I
had
worked
on
a
draft.
I
think
it
would
be
good
to
communicate
sometime,
maybe
after
the
next
release,
because
the
collector.
H
E
E
H
E
H
So
I
what
I'll
do
is
I'll
take
an
action
item
on
circling
with
you
and
riley
and
and.
E
D
One
thing
on
the
agenda,
but
it's
sort
of
a
just
abusing
the
brains
of
the
people
on
the
call
in
case
you
all
knew
of
something
I've
had
not
one
but
two
different
customer
calls
recently
when
people
have
asked
about
whether
open
telemetry
wants
to
get
into
the
business
of
defining
like
sort
of
declarative
definitions
of
like
the
monitoring
configuration
for
a
service.
D
Like
you
know
the
sort
of
like
I
mean
not
exactly
this,
but
sort
of
like
a
definition
of
what
a
simple
dashboard,
plus,
alerting
thresholds
and
slo's
might
look
like,
but
not
getting
necessarily
into
the
level
of
like
individual,
like
specific
query
languages
more
like
again
like
a
little
bit
more
declarative
or
something
okay.
Whatever
I'm
not
saying
it's
a
good
idea
or
a
bad
idea,
I
did
say
open.
Telemetry
is
too
much
scope
and
that's
not
a
telemetry
project.
That's
a
monitoring
project.
It
does
seem
like
a
decent
idea.
D
I
actually
like
the
idea
for
what
it's
worth,
but
I
was
curious.
Like
does
something
like
this
already
exist,
I
mean,
obviously
you
can.
You
know
use
terraform
to
define
dashboards
and
stuff
like
that,
but
I
was
just
curious
if
there's
something
else
that
you
all
know
about,
because
I
I
thought
it
was
like
an
interesting
idea
to
the
idea,
of
course,
to
connect
the
other
side
of
this
to
some
kind
of
open
standard
on
the
monitoring
front.
E
D
D
E
E
G
G
H
Or
whatever
I
think
ben,
that's
a
very,
very
much.
You
know
many
customers
ask
for
that
right,
because
there
is
a
standard
guidance
that
you
could
provide,
either
as
a
template
or
as
a
configuration
default
configuration,
and
you
know
at
least
downstream.
We,
for
example,
we
do
provide
on
a
dot.
You
know
specific
configurations
for
say
ecs
or
eks,
or
you
know
other
compute,
but
bogdan,
and
you
know
I-
and
we
have
talked
about
this
on
the
collector
side
in
terms
of
how
do
you
do
better?
H
You
know
configuration
management
right
and
and
maybe
having
the
ability
to
not
only
interoperate
with
other
configurations
that
are,
you
know
then
standardized
to
be
collector,
consumable
or
providing.
You
know
some
kind
of
a
reference
template
guidance.
C
Yeah,
no
so
yeah
I
was
gonna
say
there
is
something
called
mixins
in
the
realm
of
prometheus,
grafana
and
and
so
on,
and
we
we
can
define
or
we,
as
you
know,
the
tool
provider
we
can.
We
can
provide
what
is
the
base
or
what
are
the
the
primitives
that
we
want
to
allow
people
to
build
on
top
of,
and
then
people
can
say.
Oh,
I
want
a
a
collector
and
I
want
a
a
application
instrumented
with
open,
yeah
instrumentation
for
java.
C
H
To
give
feedback
on
mixins
again
we
have
taken
a
look
at
it
in
depth
as
well.
As
I
know,
azure
has,
and
no
and-
and
you
know
we
have
found
that
the
mixins
are
actually
very
difficult
for
customers
to
use
and
also
the
other
feedback.
You
know
that
we
did
get
was
that
they're
not
well
maintained
enough.
You
know
and
are
two
third
parties,
so
it's
very
difficult
to
actually
recommend
those
to
customers.
H
E
Know
that
we
absolutely
like
our
infrastructure
monitoring
part
of
of
observability
cloud.
We
have
this
aim
where,
like
yeah,
if
you
have
a
kafka
thing,
kafka
server
running
and
you
monitor
it,
we
automatically
give
you
an
option
to
create
some
sort
of
smart
alerts
and
not
smart,
like
using
ai
or
ml
to
smart,
like
we've
generated
them
with
these
are
sort
of
alerting
thresholds.
We
think
are
good
for
kafka
and
we
have
to
build
and
maintain
all
these
and
we
we
hate
doing
so.
E
We
like
like
like,
if
we
could
snap
our
fingers
and
if
there
was
like
a
huge
repository
of
like
hey
for
kafka,
we've
talked
to
100
engineers
and
they
recommend
you
know
using
these
thresholds
and
monitoring
these
metrics
and
not
bothering
these
10.
That
would
be
amazing,
like
like
we
as
a
business,
would
love
that.
I
know
our
customers
would
love
it
too,
because
what
we
provided
them
today
is
usually
like
someone
wrote
it
five
years
ago
and
never
touched
it
again.
D
Yeah
I
mean
I
I
sort
of
like
people
talk
about,
you
know
configuration
as
code,
and
I
imagine
this
is
just
an
extension
of
that
drossy.
I
actually
really
appreciate
the
pointer,
I
didn't
frankly
know
about
the
mix
and
stuff
and
I,
regardless
of
whether
or
not
it's
totally
hitting
the
marker,
it's
just
nice
to
see
some
prior
art.
That's
that
okay!
Well
I'll
continue
again.
This
is
sort
of
slight
abuse
of
open,
telemetry
governance
committee,
because
I
don't
think
this
should
be
an
hotel
project,
but
it
is
related.
It's.
I
Very
relevant,
I
wanna,
I
wanna
point
one
one
thing
that
it's
in
our
scope
and
we
should
be
very
careful
how
we
deal
with
this.
Is
we
we're
gonna,
write
instrumentations
and
during
these
instrumentations
we're
going
to
collect
metrics,
for
example,
or
traces
or
things-
and
this
is
very
I
mean
this.
D
D
And
then
somehow,
the
collector
and
other
pieces
of
infrastructure
would
follow
suit
and
obviously
the
metric
needs
names
need
to
flow
through
and
be
consistent
as
well.
But
there's
some
appeal
in
my
mind
of
having
all
that
in
one
repository,
instrumentation
plus
the
configuration
and
how
it's
going
to
be
used.
What
reasonable
thresholds
are
that
sort
of
stuff?
So,
okay,
I
I
promise.
H
Ben
keep
us
posted
because
you
know
we
also
do
something
which
is
I'll
just
share
it
with
you
called
recipes
right
and
and
that's
another
area
that
you
know
we
actually
make
available.
Let
me
just
share
the
link
with
you.
H
That's
that's
also
another
aspect,
I'll
just
bring
it
to
you
on
slack
but
yeah.
We
have
recipes
that
we
share
and
it's
the
same
concept
again.
You
know:
how
do
we
make
available
convenience?
You
know
configurations
if
you
will
for
different
types
of
setups
yeah.
J
H
B
Yeah,
you
could
go
a
step
further
and
just
think
of
them
as
open,
telemetry
playbooks
right
like
a
playbook
project,
where
you
know
here's
just
just
like
an
entire
playbook.
These
are
the
metrics
we
emit.
These
are
the
alerts
we
recommend
setting
off.
If
you
see
these
things
going
off,
these
are
the
things
you
should
check:
try
to
get
experts
from
all
those
projects
to
kind
of
help
maintain
them.
I
definitely
think
it
should
be
a
side
project
and
not
core
open
telemetry
stuff,
but
that
would
be
like
a
really
awesome
community
resource.
Maybe.