►
From YouTube: 2022-03-10 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
I
guess
liz
is
out,
but
I
just
yeah.
A
A
D
I
just
have
a
question
that
doesn't
necessarily
require
a
quorum.
I
guess
I
put
a
collector
maintainer
follow-up
in
the
agenda.
Do
we
know
we
went
through
the
the
process
of
of
creating
a
process
to
promote
maintainers?
Do
we
know
if
the
collector
sig
ever
actually
promoted?
One.
C
B
A
They
were,
after
alex,
was
nominated
in
the
video.
B
A
Yeah,
I
mean
one
of
the
things
again.
The
we've
been
doing
on
the
collector
contrib
is
to
add
a
build
out,
a
like
a
bot
for
being
able
to
code
a
sign
and
to
the
code
owners
and
to
once
they've
approved.
Then
self
auto
merge.
So
that's
something
that
we're
just
adding
tooling
for,
but
you
know
it's
not
related
necessarily
to
maintainership.
A
I
think
I
think
the
other,
the
other
folks
have
added
you
know.
Other
sigs
have
added
like
the
gosig
has
more
approvers.
The
reddit
also
may
have
gotten
a
new
maintainer,
but
again
it
depends
on
the
specific
sake.
The
other
interesting
area
that
I
just
wanted
to
call
out
in
that
context
is
that
java,
where
we
used
to
have
you
know
a
lot
of
maintainers
or
abundance
of
folks
participating,
has
kind
of
dropped
down
to
two
consistent
maintainers,
and
that's
really
something.
A
You
know
that
we
should
pay
attention
to,
because
java
has
been
a
very
large
community
for
us
and
it's
interesting
to
see
the
you
know
that
the
number
of
maintainers
has
dropped.
You
know
significantly.
D
Yeah,
we
saw
the
same
thing
in
javascript.
I
think
I
mentioned
it
when
we,
yes,
who
finished
the
tracing
work.
A
lot
of
the
a
lot
of
the
regular
contributors
were
really
only
interested
in
tracing
and
then
I
think,
metrics
work
aside
from
people
not
being
as
interested
in
it
it's
much
more
like
technically
and
mathematically
involved
and
and
I
think,
more
intimidating
for
your
average
person.
That's
not
like
a
regular
maintainer
or
super
familiar
with
the
spec.
I
think
metrics
is
more
intimidating
to
get
ramped
up
with.
A
A
D
Okay,
well,
I
guess
the
the
maintainer
track
talk
was
accepted
officially,
and
I
am
planning
on
joining
the
that
discussion
about
the
open
source
summit
tomorrow.
Yeah.
D
A
Yeah
I
mean
again,
if
I'm
presenting
a
talk,
then
I'll.
Definitely
I
can
help,
and
I
I
will
you
know
I've
also.
My
understanding
is
that
some
of
our
contributor
teams
like
new
relic
and
others,
are
actually
going
to
be
there.
A
So
we
should
actually
work
together
to
figure
out
a
larger
set
of
folks,
who
can
you
know
maybe
be
present
or
organize
them
off
and
just
be,
you
know,
hold
a
buff,
at
least
as
part
of
the
community
discussions,
okay,
so
happy
to
lead
that
I've
already
spoken
with
char.
Who
was
interested
in
that
and
I
also
spoke
with
ted.
So
again,
I
think
we
can
still
do
something.
It
could
be
just
a
buff,
but
you
know.
B
Yeah,
I
think
I
think
the
crux
of
it
in
my
mind,
I
mean
personally,
I'm
probably
just
basically
not
going
to
do
it,
but
I
think
it
will
be
fine
if
we
don't
have
to
do
a
full,
rfc
and
blah
blah
blah.
I
just
yes.
A
A
Agree,
I
agree,
I
mean
I
think
we
should
just
do
an
informal,
buff
and,
and
you
know,
have
any
contributors
or
anyone
interested
in
hotel.
Just
gather
up
for
a
you
know,
cup
an
hour,
a
couple
of
hours
and
just
meet
up,
and
you
know
talk
about
areas
that
folks
are
interested
in
seeing
the
project.
You
know
work
on
or
are
feeling
some
pain
points
on
again.
You
know
discussing
different
case
studies
if
folks
are
available,
but
it
should
be
informal.
A
Yes,
exactly,
it's,
like
you
know
something
a
meetup
that
happens
at
conferences,
typically,
where
you
know
folks
are
gathering
up
for
the
conference
and
also
work
on
hotel
or
are
interested
in
it
using
it.
A
C
D
A
Yeah,
exactly
I
mean,
are
you
on
the
east
coast
daniel?
What
are
you
are
you
on
the
east
east
east
coast?
I.
D
A
All
right
did
we
bring
up
any
other.
I
just
all.
The
only
other
item
that
I
want
wanted
to
just
bring
up
was
that
we
are
starting
to
do
a
regular
triage
for
the
metrics
ga
and
that's
on
fridays,
from
8
30
to
9.-
and
this
is
you
know,
really
the
burn
down
for
completing
any.
You
know,
items
that
are
in
flight,
the
only
three
or
four
items
left
for
the
sdks.
Do
we
java's
in
good
shape,
I
think
daniel
javascript?
What's
your
feel
there.
D
We
tend
to
err
on
the
side
of
waiting
for
the
specification
to
actually
stabilize
before
implementing,
because,
specifically
on
metrics,
we
got
burned
really
hard
on
the
first
metrics
implementation,
where
we
did,
we
had
a
full
implementation
and
then
the
met
the
spec
changed
so
drastically
that
we
it
required
a
full
rewrite.
So
the
people
that
put
the
work
into
the
first
implementation
are
hesitant
to,
I
think,
do
anything
until
the
specification
is
pretty
stable,
agreed.
A
And-
and
I
think
that
java
has
already
done
an
implementation
but
they're
just
you
know
they
were
waiting
for
one.
The
views
part
to
get
you
know
ratified
in
this
spec
and
I
think
there's
only
one
issue
open
on
the
spec
at
this
point,
which.
D
Yeah
we're
pretty
close.
The
only
thing
that
that
we're
really
waiting
for
in
javascript
is
resolution
on
the
the
issue
that
josh
has
been
working
on
for
the
last
couple
of
weeks,
around
temporality
per
instrument,
and
we
we
have
not
implemented
that,
but
we
expect
to
when
it
murdered.
You
know
we're
we're
fairly
close.
A
A
No
totally
so
I
mean
again,
this
aligns
well
with
the
thinking
we
had
about
announcing
the
ga
at
kubecon.
So
that's
why
I
think
it
would
be
good
to
be
able
to
do
that
if
we
can
land
every
all
our
sdks
in
at
least
three
sdks.
D
I
mean,
I
don't
think
the
javascript
sdk
is
going
to
be
like
I
don't
know
if
we'll
have
1.0
by
kubecon,
but
it'll
certainly
be
usable
and
up
to
date
with
the
latest
spec.