►
From YouTube: 2022-03-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
B
C
B
So
again,
let's
wait
for
folks
to
join
in,
but
I
think
ben
chris
andercheck
reached
out
to
you
as
well
as
to
me.
I.
B
C
I
I
got,
I
haven't,
sent
a
note
out
kubecon,
so
I
applied
for
a
maintainer's
track.
Talk
that
anyone
in
the
community
wants
to
pull.
Oh.
C
C
C
Sorry
daniel,
what
did
you
say
any
idea
how
big
the
room
is?
I
will
find
out.
I
don't
know
they
just
they
basically
sent
out
like
like
a
google
form
or
sort
of
thing.
It
wasn't
actually
google
form
but
some
equivalent
and
I
got
lucky
because
it's
first
come
first
serve.
They
had
like
eight
available,
and
so
I
just
snatched
one
up
for
us.
So
I
don't.
D
Know,
oh,
but
that's
the
most
obvious
thing
to
do
would
be
like
some
sort
of
like
maintainer
meet
and
greet
or
whatever
exactly.
C
A
Larger
commit
like
that's
like
we're:
gonna,
have
a
day
of
activity
or
whatever,
and
reminds
me
a
bit
of
previous
discussions
around
having
adjacent
conferences
to
kubecon
and
so
on,
where
I
think
we
may
lack
organizers
who
have
the
required
mental
energy
to
organize
an
event
after
having
several
of
them
get
canceled
at
the
last
minute
yeah.
I
think
we
had,
if
someone's
willing
to
organize
it,
sounds
great
like.
A
A
It's
it
is
a
background,
but
it's
real.
It's
a
real
background.
F
E
E
B
A
So
back
to
the
oss
event,
like
I
think
the
question
is:
is
anybody
up
for
actually
organizing
this
because
that's
not
a
light
lift
I
mean
it's
like.
D
C
A
Very
interesting,
that's
weird
arrived
on
march
1st
yeah.
I
got
mine.
D
A
I
think
you
would
the
easiest
thing
would
be
to
send
a
note
to
amy.
You
know
amy.
A
Anyway,
getting
back
to
the
topic,
I
don't
know
who's
going
to
do
this.
B
But
then
it
depends
on
what
we
want
to
do
right,
because
again
we
can.
We
can
definitely
you
know
across
some
of
us
cover
austin,
but
as
a
as
a
location
as
well,
as
you
know,
as
an
open
source
summit,
so
we
can
figure
out.
You
know
what
we
want
to
do
first,
because
actually
we
have
fair
bit
of
flexibility
from
what
I
understand.
A
B
B
E
B
I
can
find
out
if
our
marketing
teams
can
support.
You
know
setting
up
something
like
a
meet
and
greet,
and-
and
you
know
at
least
having
a
couple
of
hours
for
a
maintainers
meet
and
greet.
I
can
definitely
get
back
to
the
gc
by
next
week.
A
A
You
go
with
your,
you
know,
swag
and
try
to
sell
people
stuff.
So,
and
you
know
this
person
hasn't
even
started
yet,
but
I
mostly
just
worry
about
organizational
bandwidth
and
yeah.
H
A
B
B
A
Do
you
think
there's
any
I
I
I
saying
it
out
loud,
I'm
already
thinking
it's
a
bad
idea,
but
we
could
have
some
kind
of
like
you
know,
hotel
hackathon-ish
thing
just
to
get.
I
I
think
the
goal
would
be
not
to
have
polished
integrations,
but
to
get
as
many
kind
of
spikes
done
as
possible
of
getting
a
hotel
instrumentation
added
to
various
ecosystem
stuff.
Oh.
A
So
because
I
think,
like
I
don't
know,
I'm
just
trying
to
think
of
something
that
could
use
up
a
bunch
of
time
that
would
actually
be
productive.
Like
we've
done
these
things
in
the
past,
we've
tried
to
do
like
introduction
to
hotel
or
that's
actually
open
tracing,
but
like
introduction,
open
tracing
and
people
show
up
they're
writing
in
seven
different
programming
languages,
and
it's
just
like
a
total
loss
like
you
can't
possibly
administer
that.
A
But
if
it
was
more
like
hey
the
goal,
this
thing
is
to
have
like
a
proof
of
concept
of
some
instrumentation.
That's
emitting
something
useful
from
as
many
different
things
as
possible
and
then
we'll
take
all
those
you
know,
put
them
on
github
and
then
and
then
work
through
them
over
the
next
couple
of
weeks
or
months.
A
I
think
that
feels
like
it
might
feel
fun
and
could
be
productive,
but
just
getting
some
quick
like
weights
on
instrumentation,
I'm
just
trying
to
think
of
ways
we
could
take
a
day
and
have
it
feel
productive,
yeah
and.
D
B
Yeah,
that's
a
good
idea,
though,
because
I've
done
a
hackathon
at
all
things
open
before,
which
is
our
the
big
open
source
conference
in
raleigh
and
again
it's
typically,
you
know,
you'll
have
at
least
100
folks.
You
know
in
a
hackathon
show
up.
B
B
H
A
E
D
A
Okay
I'll
send
that
to
chris,
so
I
put
this
on
the
agenda.
A
Actually,
I
wasn't
able
to
join
last
week,
so
I
put
this
on
like
almost
two
weeks
ago,
but
I
this
is
maybe
a
more
serious
topic
and
I
have
a
feeling
it
won't
actually
like
resolve
it
exactly,
but
I
don't
really
think
that
we're
doing
a
very
good
job
of
project
management,
especially
when
it
comes
to
things
that
require
many
sigs,
and
I
think
the
problem
has
to
do
with
the
gc
and
the
tc
being
separate
governing
bodies
and
kind
of
a
lack
of
accountability
for
hitting
timelines.
A
So
I'm
not
pointing
fingers
here.
I
think
that's
sort
of
the
issue
is
that
we
don't
have
someone
to
point
a
finger
at,
but
there's
just
not
a
lot
of
accountability
for
things
that
are
multi-sig
and
to
me
this
just
points
to
some
structural
issue
or
maybe
a
process
issue
within.
A
I
think
it's
probably
slightly
more
tc's
than
dc
just
given
the
division
of
responsibilities.
I
know
that
we
have
some
folks
here
who
are
on
both
and
again
I'm
not.
I
don't
mean
this
an
accusatory
way,
but
I
do
want
to
just
state
for
the
record
that
I
don't
think
that
we're
at
a
functional
place
right
now
with
the
number
of
like
delays,
we've
had
on
various
things
we're
getting
close
on
the
metric
stuff
and
I
think
the
burn
down
stuff
you're
doing
morgan
is
quite
helpful
for
that.
A
So
maybe
we'll
kind
of
eek
through
this
at
least
for
the
metrics
push.
But
it's.
A
A
So
I
mean
that's
the
that's
the
topic.
First
of
all
I
mean
some
people
are
not
in
their
heads.
Some
people,
aren't
I
don't,
does
anyone
it's
fine.
Does
anyone
disagree
like?
Does
anyone
think
the
system
or
the
structures
as
they
stand
are,
are
like
actually
working
well
enough.
D
A
I
I
mean,
I
think,
the
ultimate
thing
I'm
interested
in
and
again
I'm
not
trying
to
throw
stones,
because,
let's
just
be
really
clear,
like
I
haven't
done
anything
in
terms
of
technical
work
on
this
project
in
the
last
like
year,
for
sure
maybe
longer
frankly,
is
that
there's
the
deliverable
that
matters
that
end
users
can
adopt
open
telemetry
for
metrics.
A
That's
the
one
that
I'm
like
particularly
concerned
with,
although
prior
to
this,
it's
the
same
issue
for
tracing,
and
we
delivered
that
probably
like
a
year
behind
schedule
according
to
like
what
we
promised
ourselves
the
beginning
of
the
project.
So
it's
end
user
adoption,
which
is
all
of
the
above
right,
and
I
think
that
you
see
like
process
issues
along
the
way
depending
on,
like
which
aspect
you're
looking
at.
A
But
I
think,
like
didn't
atlassian
recently,
just
kind
of
like
basically
pull
the
plug
like
getting
tired
of
waiting
for
stuff
like
this
on
certain
aspects
of
it.
Yeah
bogdan.
I
think
that's
basically
right
your
comment
in
chat
like
too
many
smart
people
trying
to
design
something,
I
think
you're
absolutely
right,
like
we
have
an
actual
truly
like
vendor
diverse
project,
which
means
that
it's
hard
to
just
like
force
things
through,
like
you,
would
in
an
open
core
project.
It's
not
a
bad
thing.
A
It's
a
good
thing
to
have
so
many
different
participants,
but
it's
it's
like
really
slowing
us
down
that,
like
someone,
whoever
is
accountable,
I
think,
needs
to
have
a
timeline
they're
accountable
to
not
just
a
deliverable.
B
A
Agree
with
that
I
mean
I
don't
know
why
you're
not
just
saying
it,
but
the
I
don't
think
this
is.
I
do
not
think
it
has
to
be
this
way.
I
think
that
we
could
say
that
there's
going
to
be,
someone
has
to
be
sort
of
like
anointed
the
responsibility
of
making
decisions
when
a
decision
is
needed
and
doing
so
on
a
timeline
or
they
lose
that
responsibility.
That's
given
to
someone
else
and
that's
how
I
would
propose
dealing
with
who
cannot
do
decision.
A
I
I'm
willing
to
make
a
decision,
but
then
then
there
will
be
people
coming
and
blocking
things.
So,
for
example,
I'll
give
you
an
example:
github
have
a
feature
to
block
prs.
Okay,
you
you
ask
for
changes,
and
if
you
don't
remove
that
you
block
the
pr
indefinitely,
we
never
had
someone
coming
and
removing
that
because
we
found
that
being
very
offensive
and
people
will
get
super
offended
if
you
come
and
unblock
the
pr
with
your
superpower
and
remove
that
blocking.
I
A
How
do
we
do?
I
don't
think
that
there's
not
a
sign
on
the
wall
so
to
speak.
That
says,
you
know.
Well
again,
I
mean
I
don't
want
to
try
to
design
the
process,
but
there's
not
a
sign
in
the
wall.
That
explains
the
process
for
how
we
hit
deadlines
and
again,
whether
that's
that
the
group
has
delegated
the
responsibility
to
some
individual
or
there's
some
kind
of
thing
where
we
hit
that
kind
of
roadblock
login,
there's
just
a
forced
vote
and
it's
majority
rules
or
whatever
I
mean,
there's
different
ways.
A
We
could
think
about
doing
it,
but
we
don't
have
that
on
the
wall
and
then
no
one's
in
it.
I
think
correctly
in
the
context
single
pr
willing
to
try
and
like
design
this
process,
but
if
we
had
a
process
that
says
like
if
things
get
stuck,
this
is
what
you
do
and
we
actually
relied
on
that
we
could
get
through
these
things
as
possible.
A
H
H
We
just
don't
do
that
and
like
yeah
and
we
don't
have
a
project
management
aspect
of
it
so
that
when
we
have
tc
meetings
where
we
actually
go
through
those
things
and
say
yes,
let's,
let's
make
a
decision
considering
the
arguments
that
have
been
made
in
the
ticket.
H
Yeah
I
mean
I
wish
we
didn't
have
to
do
that
honestly,
yeah
kind
of
I
I
don't
have
the
stats
on
how
often
that
happens
and
how
many
prs
actually
get
blocked
because
of
that.
H
Because
it's
a
small
amount,
then
yeah.
We
could
just
take
that
on.
If
it's
sort
of
like
10
pr's
a
week,
then
I
don't
think
that's
the
right
approach
that,
like
the
dtc,
always
has
the
sort
of
responsibility
to
kind
of
always
break
the
tie.
D
D
And
then,
if
the
pr
author
disagrees
with
one
of
those
decisions,
then
appeal
it
to
the
tc
that
would
reduce
the
the
total
number
going
to
the
whole
tc
to
be
voted
on,
and,
I
think,
unblock
a
fair
number
of
if
it
was.
If
it
was,
you
know,
if
you
yuri,
are
assigned
to
a
pr.
It
would
then
be
your
responsibility
to
either
say
yes
or
no.
This
is
or
is
not
going
to
happen.
A
A
I'm
just
trying
to
avoid
a
situation
where
every
single
disagreement
in
a
pr
becomes
a
tc
escalation,
and
so
the
project
management,
sort
of
arm
of
open
symmetry
could
identify
not
the
decision
to
be
made
but
like
this
is
an
issue
or
a
pr
where
we
have
to
make
a
decision
and-
and
that
creates
the
escalation,
as
the
tc
does
have
the
capacity
to
the
right
to
do
this
now.
But
it's
not
happening
as
you're
is
pointing
out
and
I'm.
A
I
think
that
in
some
ways
like
someone
needs
to
sort
of
enable
them
or
something
yeah,
I
mean
do
that.
B
I
I
think,
then
that's
a
good
suggestion,
and-
and
this
has
come
up
before
also
where
we
have
discussed
you
know
the
possibility.
At
least
you
know,
ted,
and
I
and
morgan
have
discussed
that
in
the
past,
where
you
know
having
it's
it's
typical
on
large
projects
that
you
could
have
of
a
group
of
the
tc
which
is
doing
project
management
right.
B
It
could
be,
or
it
could
be
a
you
know-
gc
under
under
gc
plus
dc,
but
it's
a
work
group
that
has
actually
focused
on
project
management
and
their
responsibility
is
to
keep
the
roadmap.
You
know
transparent,
visible
and
up-to-date,
and
and
also
to
forward
any
considerations
that
they
see
also
to
the
tc,
not
that
the
tc
dc
can
pick
up
anything
themselves
directly
and
but
this
work
group
could
also
forward
it
and
typically
that
does
work
on
large
projects.
B
I
mean
again,
but
that's
that
idea
has
never
taken
root
in
into
being
because
you
know
we
didn't
take
decisions
right,
but
that's
that's
an
idea.
B
When
we're
kind
of
saying
that
andrew
clone
had
drew
three
times
over
when
we
had
him
and
but
on
the
other
hand,
also
take
more
responsibility
for
actively
looking
at
all
the
backlogs
and
being
able
to
communicate
anything,
that's
blocked
clearly
to
the
tc's
attention
to.
C
It
could
work,
I
mean
that
was
sort
of
the
mode
we
were
in
for
tracing
when
we
released
it
like
andrew,
was
doing
the
bulk
of
the
work,
but
there
was
a
a
pretty
regular
sync
between,
like
you
me
and
him
and
others
yeah,
and
that's
that's
what
we're
gonna
do
for
metrics.
The
the
question
I
have
is
just
when
we're
not
pushing
for
a
single
release
like
once
we
ship
metrics,
the
breadth
of
things
happening
in
the
community,
is
vast
enough
that
it
is
difficult
to
track
in
that
kind
of
environment.
C
I
think
when
people
complain
about
us
getting
stuck
it's
less
on,
like
tracking
the
implementation
of
various
things
or
like
one
or
two
spec
issues
that
we
need
to
get
us
across
the
line.
It's
various
discussions
between
spec,
the
collector
various
other
cigs
on
sort
of
tangentially
related
topics.
It
might
be
difficult
to
bring
those
all
together.
I
don't
know.
B
C
So
do
we
want
to
try,
I
mean
there's
two
things:
we've
talked
about,
there's
instituting
sort
of
a
process
it
sounds
like
for
for
how
things
should
be
escalated
to
the
tc
or,
if
they're
not
moving
along
quickly
enough,
maybe
maybe
a
misunderstood
and
then
the
other
is.
Should
we
just
have
some
sort
of
planning
group
that
meets
regularly
to
track
status
of
things
and
push.
A
A
I
think
it's
because
people,
I
think
it's
a
big
deal
to
say
that
I'm
escalating
right
now,
yeah
yeah,
but
it's
like
for
me
to
be
like
I'm
not
in
the
tc,
but
I'm
not
tc
to
go
into
pr
where
people
are
already
pissed
off.
Frankly
and
to
say:
I'm
escalating
this
and
I'm
going
to
make
a
decision.
You're.
A
You
have
a
confident
interest
or
whatever
your
decision
is,
is
going
to
be
unpopular
with
at
least
somebody
right.
So
another
way
to
think
about,
it
would
be
to
say,
there's
a
project
manager,
who's.
Looking
at
the
clock,
basically
and
saying
like
this
thing
is
blocking
a
project
and
then
they
kind
of
say
to
tc.
I
need
you
to.
A
It's
that
that's
the.
I
don't
really
care
like
exactly
how
it's
stopped,
although
I
think
it's,
it
is
actually
somewhat
important
that
if
we
were
going
to
try
this
out,
it
could
be
more
like
advisory,
not
like
in
the
official
bylaws
of
open
telemetry,
but
just
like
that,
we're
going
to
sort
of
like
at
least
for
a
major
initiative
like
the
metrics
thing.
I
don't
know
who
it
is.
That's
morgan,
doesn't
it's
green
since
you're
doing
it?
A
And
just
yeah
the
driver
exactly
just
say
like
this
issue-
is
blocking
this
like
major
deliverable
for
us.
You
all
need
to
figure
this
out
and
if
you
don't
do
it
in
the
next
48
hours,
we're
gonna
have
the
tc
figure
it
out
for
you.
I
think
that's
sort
of
like
the
spirit
of
what
I
I
would
like
to
see,
and
I
think
it
would
resolve
a
lot
of
issues
without
changing
all
the
rules
and
yeah
whatever
tc
membership
or
anything
like
that,
which,
I
don't
think
is
actually
the
issue.
B
H
Even
though
daniel
says
that
the
issues
are
being
assigned
to
tc
members,
but
it's
honestly
that
just
noise
and
there's
so
much
going
on
it's-
I
can't
use
that
yep
yep
right
so.
F
D
B
For
review
every
time
the
pc
meets.
D
What
I
meant
to
say
yuri
was,
if,
when
I
create
a
pr
in
the
specification,
a
tc
member
is
automatically
assigned
to
it,
that
already
happens
yeah.
So
if
there's
disagreement
in
the
pr,
I
should
be
able
to
tag
that
tc
member
and
just
say:
hey.
Can
you
please
resolve
this
one?
You
know
one
way
or
the
other
it
I'm
not
saying
that,
like,
I
think,
you're
you're
thinking
of
like
when
you
say
it's
just
noise.
H
I
yes,
I
just
I
agree.
I
don't
think
that's
a
good
system
that
we
assign
them
because
to
me
it
is
noise
because,
first
of
all,
it's
random,
so
I
I
paid
very
little
attention
to
metrics.
I
just
don't
have
time
and
I
still
get
assigned
randomity
metrics
and
more
than
that,
there's
a
lot
of
activity
going
on
in
repo
where
things
might
just
get
resolved.
So
why
am
I
being
assigned
and
tagged
and
sort
of
like
I'm
getting
all
these
notifications
every
time
right?
H
And
so
I
can't
filter
them
out
because
I'm
always
assigned
to
a
whole
bunch
of
stuff,
whereas
this
like
label,
which
says
well,
we've
reached
a
sort
of
a
impasse
because
there's
no
consensus
and
I've
seen
actually
pr
authors
do
that
they,
they
honestly
said
look
I've
looked
at
their
feedback,
there's
no
agreement.
We
need
this
like
to
be
sold
by
tc
or
something
like
that
right,
and
so,
if
they
apply
the
label
at
that
point,
then
that's
going
to
be
much
more
manageable
for
us.
Yeah.
E
I
I
For
users,
so
I
think
yes,
I
I
like
these
things,
and
I
think
this
will
help
to
to
make
the
the
people
be
self
more
self
like
self-serve
like
they,
they
can
have
things
like
slash,
escalate
to
tc,
slash
whatever
something
I
like
it.
Yep.
A
Okay,
cool
well
that
we
lost
morgan,
but
maybe
we
can,
I
don't
know,
try
to
have
him
do
this
for
metrics
in
an
informal
way,
since
we
don't
actually
need
a
process
change
to
to
do
this.
Just
to
like
know,
issues
that
are
on
the
critical
path.
Does
that
sound
good.
B
I
I
B
I
B
No,
I
I
the
the
reason
I
say
it's
fragile
is
because
I
think
that
you
know
again.
If
you
have
a
leader,
then
you
have
to
have
a
backup
also
right.
So
again,
that's
that's
the
that's
the
key
thing
because
then
folks
are
not.
You
know
single
points
of
failure.