►
From YouTube: 2021-12-02 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
D
E
Did
something
happen
that
would
have
caused
the
js
sig
link
to
be
regenerated
within
the
last
week?.
E
Because
we
had
it,
we
had
a
new
meeting
id
this
week
from
last.
D
It
does
whatever
zoom
usually
does
as
an
integration.
I
don't
know
if
I
don't
know
zoom
well
enough
to
know
if
it
auto
regens.
We
should
probably
assume
that
it
does
to
be
honest,
which
is
why
I've
been
telling
people
like
just
joined
from
the
calendar
like
we
basically
just
can't
rely
on
stack
links
anymore
at
a
minimum
they're
going
to
change
once
a
year,
because
those
links
expire
after
365
days.
C
Who
actually
declined
this
meeting
liz
and
alolita
bogdan's?
Not
here
and
we
have
quorum?
Theoretically,
maybe
we
should
just
get
going.
I
guess
or
something.
C
She
declined
formally
to
climb
the
meeting.
I
just
put
something
on
my
agenda
totally
selfishly,
but
I
made
an
issue
for
the
like
sig
health
tracking
thing.
I
mean
we
can
talk
about
the
actual
proposal
if
you
all
want,
but
the
main
issue
is
like
I've
got
like
nearly
zero
feedback
about
it
a
little
bit,
but
the
maintainers
are
the
ones
who
I
was
sort
of
hoping
to
hear
from.
C
I
can
like
go
and
just
mention
every
maintainer
and
say
hey,
please,
like
speak
now
or
forever
hold
your
piece
or
something
like
that.
But
or
we
can
just
say,
look
we're
doing
this
launch
and
iterate
whatever
it's
not
like
a
bunch
of
it's
not
very
hard
to
do.
It's
a
question
of
whether
it's
the
right
thing.
E
Yeah,
I
think
I
would
rather
I
didn't
even
know
this
was
here.
I
think
I
probably
clicked
on
the
notification
and
then
missed
it.
I
bet
a
lot
of
the
maintainers.
Don't
know
it's
here,
so
I
think
we
should
just
bring
it
up
in
the
maintainers
meeting
exactly
yeah,
but
sounds
good.
I'm
happy
to
do
that.
Just
mention
that
it
yeah
here's
the
issue.
Please
go!
Look
at
it.
A
E
I
spent
some
time
with
bogdan
talking
about
the
one
maintainer
to
approvers
thing
and
trying
to
come
up
with
some
requirements
for
like
an
automation
to
do
that,
like
a
github
bot
and
alolita
mentioned
that
she
would
have
engineering
resources
that
could
build
it
once
we
came
up
with
the
requirements,
but
we
never
really
moved
beyond
the
the
early
phase
of
that
I
was
hoping
to
to
do
it
after
the
holiday,
but
he's
obviously
not
here
today.
I
can
reach
out
to
him
separately.
C
E
E
Does
anybody
know
whether
constance
ended
up
doing
the
project.
C
Priorities
blog
post
or
I
just
sent
her
a
dm-
I
mean
she
didn't
do
it,
but
I
think
she
just
forgot
said
this
last
time,
but
last
time
she
seemed
like
she's
going
to
do
it
like
day
of
so
I
think
she
probably
has
forgot,
but
if
she
doesn't
do
it
this
week,
I.
E
E
A
On
the
open
tracing
front,
just
to
give
people
an
update,
so
we've
added
a
matrix
to
the
spec
compliance
matrix,
we've
added
open
tracing
concepts.
There's
just.
I
think,
two
remaining
open
issues
that
need
to
get
resolved
around.
What
open
tracing
support
actually
means
like
the
one
big
one
is
around
baggage,
because
we
can't
it's
the
only
feature.
We
can't
just
directly
support
out
of
the
box.
The
way
everything
else
works
so
once
hopefully
that'll
get
resolved
next
week.
A
C
A
Yeah
yeah,
my
hope,
is
end
of
end
of
year.
We'll
certainly
have
like
all
of
the
spec
stuff
sorted
out
like
in
the
next
week
or
two,
and
you
know
something
on
the
web
page
there's
still
as
far
as
like,
actually
implementing
it
in
places
that
it's
not
implemented.
That'll
come
in
january,
but
yeah
I
have.
I
have
I've,
told
amy
or
whoever
from
the
cncf
about
this
schedule,
so
they
should
be
aware
of
it.
E
A
E
A
B
Yeah
so
eager
is
also
recommending
using
you
know:
that's
one
one
supported
way
of
migrating
from
from
the
eager
clients
to
open
language
sdks
through
the
shin
and
there
was
there
is
a
blog
post
on
eager's
website
telling
people
how
to
do
that
with
java
libraries
so
how
to
migrate.
One
existing
application
using
open,
telemetry,
open
tracing
plus
jager
to
open,
trace
influence,
open
telemetry.
F
G
B
A
few
people
in
the
jager
community-
they
they
did
mention
they
are
using
remote
sampling
and
that's
one
thing
that
is
preventing
them
from
from
using
some
clients.
I
think
the
java
one
implements
remote
sampling
already.
So
that's
that's
good,
but
it's
pretty
much.
The
only
one
right
so
remote
sampling
is
part
of
this
pack.
I
think
it's
something
that
we
brought
from
the
edgar
community
into
open,
telemetry,
so
buy
this
pack.
All
the
sdks
have
to
provide
remote
sampling
capabilities,
but
only
the
java
one
is
implementing
that.
G
So
you
are
not.
You
are
talking
about
yager's
remote
sampling
protocol,
so
so
we
we
have
the
sampler
interface,
so
anyone
can
implement
that.
But
one
implementation
of
this
interface
is
the
jager
remote,
the
sampling.
Again,
it's
a
younger
specific
thing.
We
agree
to
implement,
don't
get
me
wrong,
but
call
it
jager
remote,
because
we
also
talking
about
having
our
own
remote
sampling
configuration,
which
probably
would
be
a
different
protocol
but
yeah.
Let's,
let's
make
sure
we
support
the
yaga
remote.
B
E
E
But
there's
I
remember
that
being
a
part
of
like
the
environment
variables
back
almost
or
something
like
that,.
G
Yeah
we
have
the
jugger
transformation,
but
we
don't
have
that
requirement
anyway.
I
think
we
should
daniel.
Maybe
somebody
should
take
this
as
an
action
item
in
order
for
us.
G
F
G
A
G
B
Jurassic,
can
you
take
an
action
item
to
provide
us
documentation
about
this
sure
yeah?
So
I
just
checked
the
blog
post,
which
you
know
should
have
been
in
my
my
head,
but
basically
the
only
part
that
is
specified
as
part
of
the
open
telemetry.
B
G
Okay,
picking
egos
like,
if
you
need
to
help
with
the
specification,
I
think
it
will
be
good
to
come
also
from
your
respects,
the
specting
so
that
at
least
we
we
have
somebody
from
the
yaga
community
coming
and
asking
for
this.
So
we
play
nice
yeah.
True.
G
Yes,
I
think
we
can
actually
it's
a
good
point.
I
we
may
extract
that
as
a
as
an
extension,
maybe
jurassic
we
can,
we
can
define,
we
can
talk
about
that
in
country,
maybe
maybe
a
separate
issue
and
extract
that
as
an
extension
standalone.
G
So
I
don't
know
daniel
how
much
you
know
about
the
the
collector,
but
extension
is
because
it's
not
connected
to
the
pipelines
to
the
data
pipelines.
It's
different.
We
will
make
it
an
extension,
so
the
collector
can
enable
that
with
any
other
format
you
want
like,
even
if
you
skip
in
you
can
still
use
that.
I
don't
care
that
would
be
better
yeah.
We
will
do
it
we'll
do
it,
but
thanks
for
pointing
it's,
it
was
a
yeah.
B
So
to
be
clear
that
one
should
follow
jager's
protocol.
G
Will
be
will
be
a
younger,
remote
sampling
extension
we're
going
to
put
jagger
in
the
name
just
for
people
to
know
that
it
comes
it
respects
the
yaga
protocol
just
in
case,
if
we
come
up
with
a
different
one,
we
have
the
freedom
to
call
that
remote
sampling
and
not
not
not
have
to
to,
and
also
give
credits
to
the
younger
people
that
they
designed
this.
So
I
think
we're
gonna
call
it
everywhere,
jager
remote
sampling
for
the
moment,
and
but
we
need
to
explain
that
it
can
be
used
with
anything
else.
B
Yeah,
it's
gonna,
it's
gonna,
look
weird
having
like
the
jager,
remote
sampling
of
accession
and
not
have
jager
as
part
of
the
pipeline.
I
mean
it.
It
will
look
weird
too
yeah,
but
it's
maintaining
that
but
yeah
I
mean
if
we
make
it
clear
in
the
documentation
that
it's
not
jager
specific,
then
sure
yep.
A
Our
the
the
main
difference
I
see
is
like
we
want
to
have
more
general
purpose.
Remote
configuration-
and
you
know
sampling
would
probably
be
like
a
subset
of
information
that
comes
along
that
that
remote
configuration
pipeline.
So
that's
probably
why
open
telemetry
won't
just
like
pull
hog
take
on
the
the
jaeger
remote
sampling
protocol,
because
it's
just
like
a
subset
of
the
remote
sampling.
We
want
to
do.
G
C
H
G
Probably
everyone
should
we
cancel
the
last
two
weeks
of
the
year
this
meeting.
Definitely
between
christmas
and
new
year,
I
would
suggest
to
cancel
but
the
thursday
before
christmas.
Should
we
cancel
that
as
one
as
well.
I
think
it's
23rd
or
24th
no
one's
going
to
go
to
that
23rd
yeah.
So
so,
let's,
let's
cancel
the
23rd
and
30
just
for
for
everyone
to
not
have
pressure
on
this
meeting
or
anything
enjoy.
G
I
E
In
support,
if
if
people
want
to
do
it,
I
know
that
some
people,
like
liz
in
particular,
is
pretty
concerned
about
in-person
events.
Large
events,
so
I
don't
know
if
we
do
it
around
a
conference
or
if
we
do
something
smaller,
I
would
suggest.
G
Something
smaller
where
people
feel
more
comfortable
to
come
clear
vaccination
rules
and
stuff
whatever
we
want
doesn't
matter,
but
I'm
just
saying
it
would
be
good
to
maybe
have
gctc
members
and
couple
of
other
main
contributors
coming
to
one
day.
Event
finished
with
some
beers
drinks
and
stuff
and
as
open
source
does
not
as
corporation
does.
A
We
could
do
just
the
lowest
barrier
is
just
starting
some
local
meetups
right.
That's
like
pretty
easy
to.
I
G
But
I
don't
want
to
open
for
everyone
for
the
at
least
at
least
for
having
initially,
with
all
these
people
feeling
comfortable
to
come,
then
then
next
sessions
can
be
open
with
everyone
and
people
who
feel
comfortable
to
come
with
more
people
can
come,
but
I
would
like
at
least
one
session
to
meet
with
with
everyone
in
gctc
next
year,
maybe
probably
around
march.
I
think
it's
good
march
april
to
not
be
winter.
A
C
I
mean
it
seems
like
I'm
totally
in
favor
of
what
you're
suggesting.
Maybe
my
personal
point
of
view
is
that
it's
kind
of
unlikely
that
we'll
get
literally
everyone
from
gcntc
to
do
anything
that
involves
travel
unless
it's
connected
to
an
event.
So
we
can
just
have
a
tradition
that
every
one
of
the
cmcf
conferences
that
we
make
a
point
of
like
scheduling
some,
you
know
social
plus,
not
quite
a
social
thing,
for
the
hotel
gcntc.
I
think
that
would
be
a
great
idea.
I
mean
I
have
no
idea.
I
C
G
Yeah,
I
don't
know
I
will
try
at
least
to
to
ping
you
guys
in
the
area.
I
know.
H
Yeah
also,
a
bunch
of
us
went
to
different
other
places.
H
H
A
I
I
went
to
the
last
cncf,
you
know
in
la
and
it
was
it
was
slightly
weird,
but
it
was
fine,
so
I'll
probably
go
to
this
next
one
yeah.
I
went
to
la
also.
A
Yeah
yeah,
I
mean
yeah,
I
plan
on
being
there.
So
may
is
not
like
that
far
away
so,
but
if
yeah,
if
people
are
always
looking
for
excuses
to
come
down
to
sf,
so
people
want
to
have
just
like
a
little
local
thing
in
sf.
Before
then
sure
you
could
probably
work
that
anyway,.
I
G
Don't
do
that,
I
was
in
portland
last
weekend.