►
From YouTube: 2021-11-04 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).
D
E
B
Yeah,
interestingly
ben,
can
you
add
my
gmail
also
it's
just.
B
C
Yeah
with
this
change
I'll
be
more
focused
on
open,
telemetry
as
a
whole,
so
yeah,
it's
good
indeed,.
E
C
H
C
C
H
J
Google
was
just
anya.
J
I
was
because
I
I
got
the
lazy
part
after
one
year
at
google
yeah.
H
J
H
Who
was
jeff
with
five
f's?
We
had
a
sales
person,
I
worked
with,
whose
name
was
robin
and
she
had
her
primary
email
address
was
not
batman
at
google.com,
which
I
thought
was
probably
the
most
clever.
I.
H
And
then
there
was
a
guy
in
kirkland
to
team
lead
who
had
cool
man,
cool
man
and
one
of
his
friends
joined
his
team
and
got
coolman2
at
google.com.
Was
his
primary
email
address.
H
C
Quickly,
yeah,
I
guess
I
should
I
mean
I
I
realize
that
I
know
most
of
you
and
most
of
you
know
me
already,
but
sure
you
know
so
officially
I'm
hi
I'm
should
I
see
I'm.
I
work
here
at
rafana
since
october,
just
as
we,
as
I
just
mentioned,
I'm
a
maintainer
on
the
eager
project
since
2018
or
or
perhaps
even
earlier.
My
involvement
is
a
little
bit
earlier
than
that.
C
I
was
part
of
the
team
at
red
hat
that
helped
become
part
of
the
cmcf
back
then,
and
I
was
quite
active
on
the
open
tracing
community
and
now
open
telemetry
as
well.
Now
I'm
focusing
more
on
the
collector
side
of
things
and
that's
what
my
focus
should
be
here
at
grafana.
C
I'm
really
excited
to
be
here.
I'm
really
glad
to
be.
You
know
with
so
many
good
folks.
People
who
I
admire
and
yeah,
and
I
think
you
know
for
people
have
been
asking
me
why
why?
Why
would
I
want?
You
know
this
trouble
to
my
head
and
I
guess
one
thing
that
I
want
to
do
in
this.
The
next
couple
of
years.
C
Being
part
of
this
group
here
is
to
have
more
visibility
in
terms
of
you
know,
bringing
or
making
sure
that
every
project
every
tech
lead
in
this
all
the
separate
sub-projects
know
about
especially
diversity
programs
that
we
have
available
as
part
of
the
cncf
or,
as
part
of
you
know,
a
bigger
community
and
perhaps
even
get
your
own
companies
to
you
know
collaborate
on
on
those
diversity
activities
as
well.
C
A
second
goal-
and
I
think
you
know
very
close
to
the
first
one-
is
ensuring
that
you
know
everything
that
we
decide
on
at
a
governance
level
at
a
at
this
level.
Here
is
compatible
with
open
source
ideals.
I
know
it's
it's
it's
it's
been
like
that
already,
but
you
know
it's.
C
It
never
hurts
to
just
keep
an
eye
and,
taking
a
you,
know
the
open
source
side
of
things
into
into
the
game,
not
only
thinking
about
products,
and
you
know
how
to
how
do
we
sell
these,
but
you
know
thinking
really
on
a
broader
ecosystem,
not
only
from
an
open
source
perspective,
but
also
open
source
ecosystem,
so
you
know
dealing
with
other
communities
around
telemetry
as
well
yeah.
So
that's
me
and
that
and
really
again
again,
I'm
really
looking
forward
to.
C
It
it
doesn't
matter
whatever
you
prefer.
C
But
jp
is
fine.
I'm
also
used
to
getting
my
name
mispronounced
and
in
brazil
it's
a
unisex
name,
I
would
say
so.
People
even
you
know,
get
my
gender
right
wrong
so
that
you
know,
and
I'm
fine
with
that,
that's
whatever
you
prefer,
I'm
fine
with
that
great.
A
E
Is
there
anything
else
people
want
to
add
here
I
put
something
on
the
list
that
was
kind
of
like
at
the
the
last
previous
gc
iteration
meeting.
We
had
just
kind
of
a
prioritization
exercise
and
I
wanted
to
do
a
similar
thing
for
this
one,
maybe
not
taking
as
much
time
since,
aside
from
jp
it's
the
same
people,
but
but
I
I
don't
think
that
we've
done
a
great
job
at
holding
ourselves,
as
you
see
accountable
to
timelines
on
things
that
we
agree
are
important.
E
So
I
kind
of
wanted
to
kick
things
off
on
the
right
foot
if
possible,
and
try
to
establish
a
little
tiny
bit
of
discipline
about
that
for
ourselves
anyway,
and
as
so
I'd
like
to
have
that
conversation,
we
could
have
it
right
now,
but
I'd
also
happy
to
schedule
like
we
could
extend
next
weeks
to
one
hour
or
something
like
that
just
to
like
if
people
want
more
time
to
think
about
it.
E
But
that's
the
only
thing
I
had
on
my
list
right
now
is
just
to
try
and
look
through
the
priorities
and
actually
decide
like
what
are
we
committing
to
and
who's
going
to
own
it?
That
sort
of
thing.
K
Did
have
a
question
for
jp
since,
since
you
are
a
grafana
rep
and
I
feel
like
grafana
is
a
company
that
isn't
like
hugely
represented
in
open
telemetry,
I
I
could
be
wrong.
That's
just
been
my
vague
impression,
maybe
because
we've
been
more
focused
on
like
tracing
traditionally,
but
I
I
was
curious.
If
you
had
any
idea
of
like
how
grafana
as
an
organization,
sees
open,
telemetry
and
is
like
positioning
itself.
B
I
I
would
like
to
add
the
ted
and
just
clarify
that
rafana
has
been
involved
because
we
have
been
working.
You
know
since
january,
on
open
telemetry,
prometheus
interoperability
on
metrics
and.
F
K
Yes
right,
I
totally
get
all
of
those
things
and
I
know
they've
graffana's
been
involved
in
the
prometheus
stuff
in
particular,
but
I
was
I
was
curious,
just
not
that
you
are
a
graffana
mouthpiece,
but
since
you
are
someone
who
who
works
there
and
is
on
and.
K
They're
a
major
player
in
this
space.
I
think
it's
important
to
just
understand
your
thoughts.
There
yeah.
C
Sure
absolutely
yeah
so
as
mentioned,
I
was
indeed
hired
to
work
on
open,
telemetry
exclusively
and
my
job
here.
So
I'm
still
trying
to
understand
what
is
my
position
here.
It's
just
been
one
month
and
from
what
I've
I've
understood.
My
job
is
twofold.
C
So
first
is
making
sure
that
whatever
we
grafana
are
doing
has
open
telemetry
mind,
so
you
know
making
sure
that
otlp
is
a
protocol
that
we
ingest
in
metric
systems
in
tracing
systems
and
logging
systems,
on
the
other
hand,
is
making
sure
that
whatever
or
not
making
sure
but
being
attuned
to
what
the
community
is
doing,
where
the
community
is
heading
and
and
bringing
the
voice
of
rafana
to
that
as
well.
C
So
if,
if
there
is
something
that
we
think
is
right
in
terms
of
vlogging-
and
there
is
a
contradiction
going
on
in
the
community
or
something
that
would
you
know
be
against
that,
then
I
should
bring
those
concerns
and
and
discuss
with
the
community,
of
course,
not
not
trying
to
force
anything.
Obviously,
I
think
you
you
all
know
me,
so
it's
not
what
I
would
try
to
do,
but
mostly
to
bring
this
knowledge
or
just
to
be
this
bridge
between
grafana
and
the
community.
C
Now
I'm
not
the
only
one
here,
working
at
open,
telemetry
right
now,
so
there's
already
someone
working
with
open
telemetry
as
well
exclusively
and
we
are
getting
more
people
to
work
there.
So
it's
true
that
rafana
has
not
been
a
huge
voice
in
the
community.
Quite
the
opposite!
Right
I
mean
it's
it's.
C
It
has
kind
of
stayed
out
of
the
game
for
some
time
in
terms
of
open
telemetry,
with
the
exception
of
perhaps
tempo
and
otp,
so
temple
implements
where
I
ingest
or
tlp
since
its
inception,
and
even
before
joining
I've
seen
some
people
from
grafana
contributing
to
the
collector,
so
some
processors
and
the
collector
is
emitted
into
grafana
agent,
for
instance
as
well.
So
there
there
has
been
some
contribution,
but
my
my
take
is
you
know
from
now
on,
you're
gonna
see
more
of
us
here
awesome
in
the
community.
J
It
will
be
interesting
as
a
separate
thing
and
maybe
probably
during
the
collector's
signature,
to
discuss
the
relationship
between
grafana
agent
and
collector,
but
that's,
let's
not
polarize
this
discussion
about
that.
Yes,.
B
J
J
During,
let's
see
segmenting
to
discuss
this
problem
yeah,
I
think
that
was
what
I
tried
to
say.
B
K
A
K
E
What
means
we
made
last
week?
Well,
yeah,
so
jurassic
you
can
open
the
link
and
zoom.
If
you
want
just
to
see
what
we
did.
The
idea
with
that
exercise
we
spent
an
hour
gosh
was
that
just
last
week's
been
kind
of
a
lot
of
busy
week
going
through
the
gc
everyone
kind
of
put
down
possible.
You
know
problems
to
solve
priorities,
and
then
we
did
a
kind
of
a
quick
vote.
E
We
didn't
have
total
participation
in
the
meeting,
so
you
know
it's
kind
of
approximate,
but
thankfully
there
was
some
banding
that
came
out
of
that.
That
was
somewhat
clear.
I
think
our
point
of
view
is
that
the
number
of
maintainers
is
a
huge
bottleneck
for
a
lot
of
different
things
and
this
kind
of
the
clear
first
priority.
A
lot
of
the
other
things
that
seem
like
priorities
are
arguably
symptoms
of
not
having
enough
maintainers.
E
So
we
don't
have
people
in
the
end
user
community
complaining
about
number
of
maintainers,
but
we
do
have
people
complaining
that
we
don't
have
road
maps
or
that
contributions
take
too
long
to
go
through
or
whatever,
which
is.
You
know
has
a
lot
to
do
with
maintainer
head
count.
E
Basically,
so
so
that's
thing
number
one,
then
the
other
two
priorities
that
kind
of
bubbled
up
to
the
top
in
our
discussion
and
just
from
the
ranking
were
just
you
know
not
road
maps
at
the
level
of
like
individual,
prs
and
stuff
like
that,
but
like
high
level
road
maps
for
that
are
at
the
granularity
that
end
user
companies
would
really
care
about.
E
We
don't
really
have
them
in
a
credible
way
for
many
parts
of
the
project,
and
so
that
seemed
like
a
biggie
and
then
sometimes
we
do
things
well,
but
we
don't
let
anyone
know,
because
I
think
the
team
that
the
people
working
on
hotel
are
so
technical
that
we
tend
to
sort
of
you
know,
skip
the
messaging
part
of
the
work
that
we're
doing
or
it's
like,
left
to
a
blog
post,
instead
of
like
really
updating
the
docs
or
making
things
clear,
etc.
E
E
So
I
think
in
the
interest
of
not
like
getting
a
third
of
the
way
through
a
discussion
and
then
running
out
of
time,
I
would
kind
of
suggest
that
we
allocate
like
an
hour
sometime
soon
to
talk
about
okay
like
well.
What
do
we
want
to
do
about
it
at
the
dc
level,
including
assigning
ownership
and
stuff
like
that?
For
those
three
topics,
I
think
if
we
try
to
bite
off
much
more
than
that,
we're
going
to
be
spread
too
thin
based
on
just
historical
averages
of
performance.
E
J
Is
a
outstanding
topic
as
well
to
discuss
with
the
tc.
I
remember,
and
we
said
that
we
want
to
have
that
discussion
after
the
new
yeah.
That's
right
coming,
please
so
another
one-hour
discussion
that
we
said
we're
gonna
have
with
the
pc.
E
E
Yeah,
I
put
the
lincoln
thing
but
yeah
I
mean
all
three,
these
two
for
sure-
and
maybe
you
could
argue
this
as
well-
are
like
super
relevant
to
the
tc.
It
would
be
difficult
to
talk
about
the
roadmap
accountability
stuff
without
also
having
the
tc
involved.
I
think
so
we
we
could
try
to
do
that
as
one
big
happy
family.
E
It's
a
lot
of
people,
but
I
don't
know
what
you
all
think
if,
if
you'd
prefer
that
we
talked
about
this
as
a
dc
separately
or
or
combine
that
with
the
tc
discussion,
I'm
flexible
about
that,
but.
K
I,
I
might
add,
there's
one:
maybe
it's
on
the
more
in
the
gc
plate
as
far
as
public
messaging
is
just
to
to
try
to
get
the
comms
group
staffed
up
with
people
who
can
who
are
willing
to
to
write,
docs
and
and
other
website
related
stuff.
I
think,
but
we
identified
that
as
like.
Like
another
blockage,
it's
like
it's
basically
patrice
over
there
right
now.
So
that's
just
a
bit
of
a
bottleneck.
That's
probably
not
directly
the
tc's
job.
A
E
E
All
right
so
do
we
think
that
we
can,
I
don't
remem.
Do
you
think
an
hour
with
the
gcntc
is
enough
to
tackle
this
and
the
other
outstanding
item
that
we
have
to
discuss
with
them?.
F
B
Schedule
yeah
great
agreed,
and
then
I
mean
I
think
that
the
again
there
is
a
road
map
document
that
josh
zuret
has
been
coordinating
across
the
tc
and
and
also
communicating
with
all
the
maintainers
on.
It
still
requires
some
more
feedback,
but
that's
definitely
a
good
document
to
base
that
discussion
on.
E
H
E
The
tc,
or
something
like
that,
like
this,
is
kind
of
part
of
your
job
or
something
like
it's,
not
that
we
would
have
a
you
know
some
kind
of
integration
that
will
remove
you
from
the
the
metadata
file.
E
If
you
don't
like
meet
your
timelines,
but
I
think
the
g,
I
think
there
should
be
some
accountability
for
like
hitting
like
you
know,
we
should
obviously
have
consensus
on
what
the
roadmap
timelines
would
be,
but
I
I
don't
think
we
have
enough
back
pressure
on
scope
as
a
project,
so
I
more
want
to
have
the
discussion
about
like
everyone
agreeing
that
we
need
to
be
accountable,
we
being
potentially
at
gc
as
well.
I
don't
know
less
about
what
the
actual
runoff
should
be.
E
I
mean
that
that
conversation,
I
think,
should
be
made
after
deciding
what
the
accountability
mechanism
is,
that,
if
that
makes
sense
to
people
yeah.
K
E
E
All
right
so
to
be
clear,
I
believe
the
thing
that
we
wanted
to
talk
about
previously
with
the
gc
and
the
tc
together
had
it
was
back
to
from
gosh.
I
guess
october
21st
and
dan
brought
up
from
the
kubecon
contributor
strategy
sessions,
and
we
wanted
to
talk
about
contribution,
ladders
and
stuff
like
that.
Is
that
the
discussion
that
we
previously
wanted
to
have
with
the
gc
and
the
tc,
you
know
basically
try
to
make
some
progress
on
the
maintainer.
The
maintainer
number
of
maintainers,
and
that
sort
of
thing
is
that
correct.
E
Cool,
so
that's
one
and
then
the
other
would
be
a
discussion
of
I
mean.
The
reason
I
ask
is
because
I
feel
like
that's
basically
this.
If
I
mean
essentially
right,
it's
like
we're
talking
about
the
ladders
and
so
on.
That's
a
means
to
addressing
that
issue
yeah.
E
Well,
I
guess
I
wouldn't
schedule
a
separate
gcntc
session
to
also
to
to
separately
talk
about
this.
I
think
it's
it's
they're
very
similar
right
and
then
this
roadmap
thing
does
seem
like
potentially
a
separate
topic.
I
don't
know
how
you
all
feel
about
it.
I
wouldn't
mind
like
starting
by
scheduling
one
hour
trying
to
make
as
much
progress.
We
can
on
this
thing
and
then,
if
we
have
time
left
over,
we
can
start.
You
know
talking
about
this
rather
than
just
immediately
scheduling
part.
E
Well,
I
will
say
part
of
the
reason
I
think
we
have
trouble
hitting
timelines,
that
we
have
a
habit
of
whenever
there's
something
interesting
that
comes
up
in
hotel.
We're,
like
oh,
let's,
create
a
one-hour
meeting
next
week,
and
so
I'm
trying
to
like
compress
more
into
these
things
if
possible,
but
maybe
we
can
say
we're
definitely
going
to
talk
about
the
maintainer
count
issue
and
if
we
have
time
we'll
talk
a
bit
about
the
diagnosing
the
roadmap
stuff
and
if
we
have
to
schedule
additional
time
so
be
it.
E
Does
that
work
for
people
cool
all
right,
okay,
I'm
I'm
done
and
then
ted
on
the
on
on
this.
I
I
think
this
is
an
important
topic,
but
not
a
tc
topic.
I
think
this
is
like.
F
F
F
G
Is
that
a
country,
canada,
it's
not
yeah,
it's.
H
H
But
in
commonwealth
countries
it's
a
day
off,
but
also
more
than
one
week's
notice
is
probably
good.
J
J
E
H
E
I'll
I'll
try
and
propose
that
and
then
we'll
just
hope
that
enough,
the
tc
shows
up
that
it's
a
quorum
or
something.
I
B
K
E
Link
in
there
with
some
possibilities
and
and
we'll
we'll
find
a
time
I
I've-
I
don't
want
to
you-
know
we're
probably
not
not
going
to
be
able
to
get
100,
but
we
should
at
least
be
somewhat
thoughtful
about
it
and
get
enough
of
the
gc
there
and
stuff.
C
I'm
in
berlin,
so
it's
it
will
be,
I
think,
8
p.m.
For
me,
which
is
not
the
best
time
ever,
but
it's
also
not.
I
mean
I'm.
C
E
C
If
it's,
if
it's
you
know,
if
it's
well
enough
in
advance,
then
I
can
schedule
my
day
so
that
I.
E
J
99
pacific
should
work
very
well
because
berlin
is
now
eight
hours,
but
will
be
nine
hours
normally
and
nine
hours.
Nine
plus
nine
is
eighteen.
So
it's
six
six
o'clock
which
is
pretty
decent
trade-off.
I
think
yeah.
C
Right
yeah,
so
that's
why
I'm
okay
in
in
you
know
I
have
the
flexibility
of
making
my
day
the
way
that
I
that
I
liked
so
it's
okay
for
me.
Okay,
all
right
for
other
folks
in
europe!
It
wouldn't
be
that
easy,
so
for
other
gcm
members
that
are
here
in
in
in
europe
would
not
be
that
that
good.
But
for
me
it's
okay.
E
All
right,
I
have
a
customer
call,
I
have
to
go,
but
I
will
I'll
send
out
the
scheduling
thing.
Thanks.
Everyone,
okay,.
D
Yeah,
do
you
have
me
needs
to
talk.