►
From YouTube: 2021-02-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).
B
A
D
C
No,
I
mean
I've
got
my
truck.
I
brought
it
up,
but
it's
it's
not
a
well
documented
process.
You
have
to
do
a
federal
import
and
a
provincial
import.
It's
a
whole
thing.
Oh.
C
E
B
In
1999
I
lived
in
australia
and
one
of
my
friends.
There
was
canadian
and
he
lived
in
like
way
north
in
canada
and
he
had
a
diesel
truck
for
whatever
I
think
and
they
and
he
basically
for
the
winter.
He
had
to
leave
it
idling
overnight,
like
every
night,
because
if
you
turn
it
off,
you
basically
couldn't
restart
it.
So
it's
too
cold
to
go.
C
C
D
E
B
C
I
was
in
the
call
it's
going
to
be
just
they're,
going
to
finish
the
presentation
not
next
week
but
the
following
week,
because
they
only
meet
every
other
week,
but
it
seemed
positive.
So
I'd
expect
to
get
sign
off
about
a
week
and
a
half
from
now.
A
Cool
and
then
I
heard
back
from
the
the
observability
sig
and
I
think
there
were
no
issues
there,
either.
C
D
D
You
should
be
happy
yeah
honeycomb
announced
a
20
million
dollar
series
b
and
lightstop
announced
a.
How
shall
I
character?
Is
this
a
metrics
launch
and
also
a
kind
of
cross
cross
systems
kind
of
correlations,
launch
more
extensive
than
what
lifestyle
already
did
with
correlations
very
cool
yeah?
Don't.
B
Hey
genuinely,
if,
if
anyone
sees
stuff
I've,
I've
like
told
our
marketing
and
devrel
people
to
be
careful
about
the
marketing
guidelines
that
you
know
we
like
in
this
sort
of
setting
set
up.
If
you
see
anything,
that's
hotel,
wise.
That
seems
a
foul
from
that.
Please,
let's
do
what
we're
saying
we're
going
to
do
and
let
you
know,
let
me
know
or
let
gc
know
and
we'll
try
to
correct
it.
B
I
think
we're
all
good
in
terms
of
talking
about
hotel,
but
I
was
trying
to
be
careful
about
that
with
the
messaging
that
we
used
around
hotel,
specifically,
so
an
open
invitation
for
feedback-
I
guess,
is
what
I'm
saying
since
it's
kind
of
like
a
little
bit
of
a
test
run
for
I
don't
know
launches
that
refer
to
hotel
in
some
way.
It's
not
the
headline
by
any
means,
but
certainly
in
like
our
press
materials.
A
Okay,
so
I
think
I
had
the
next
item
just
wanted
to
give
a
very
quick
update
on
you
know
the
progress
that
the
prometheus
metrics
were
group
is
making.
We
have
actually
gotten
organized
with
a
slack
channel
that
we
have
set
up
on
the
cncf
slack
for
the
prometheus
discussions
and
again
any
of
you
who
is
interested
in
not
on
the
channel
yet
happy
to
add
you
guys
in
if
you
want
to
track
white
flow.
What's
going
on.
F
A
A
Yeah
and
and
maybe
ted
what
I
can
do
is
also
add
to
the
community.
You
know
repo
a
list
of
the
channels
that
are
available.
You
know
that
I
have
at
least
found
for
a
hotel
on
the
slack
cncf
sac
workspace,
so
at
least
folks
can
find
it
then.
F
A
It's
just
that
you
know
there's
several
of
the
engineers
are,
you
know
available
on
on
that
slack
workspace
because
of
other
groups,
also
so
good
to
tap
into
that.
A
Yes,
so
again
we
are
again
sega
created
the
repo
for
the
group
that
you
know
we
requested,
and
so
I'm
just
in
the
process
of
adding
the
backlog
in
there
and
I'm
working
with
punya
from
and
josh
from,
google
to
actually
also
add
their
items.
So
we'll
we'll
make
sure
we
drive.
You
know
this
and
make
progress.
A
Okay
and-
and
then
I
think
you
were
next.
E
A
E
A
I
mean
one
of
the
things
again
I
just
wanted
to
add
is
that
it
might
be
good
to
just
do
a
brief
blog
post
ted.
Maybe
you
know
we
can
do
a
short
post
on
our
project
blog
to
just
give
an
update,
because
I
think
there's
some
confusion
around
1.0.
What
that
means.
You
know
from
tracing
spec
stabilization
and
the
sdks
that
are
getting
ready
with
rc's.
A
F
I
have
a
blog
post
drafted,
actually
that
I
can
share
around
the
1.0
announcement
and
yeah.
That's
specifically
the
part
where
I
want
feedback,
because
we
want
to
simultaneously
announce
that
the
specification
is
turning
1.0
yeah
and
that
you
know
we
have
release
candidates
in
a
number
of
languages,
but
we
at
the
same
time,
have
to
also
like
clarify
that
it's
just
tracing
yeah
and
these
other
things
are
coming
because
it's
sort
of
like
we're
announcing,
but
we're
also
saying
hey.
We
have.
F
I
would
say
we
also
want
to
talk
about
the
observa.
The
support
guarantees
we're
going
to
be
offering
with
this
yeah.
That
whole
thing
turns
out
to
be
like
that
makes
it
for
like
a
very
long
post.
A
Maybe
maybe
we
can
do
two
ted
because
it's
better
to
be
concise
on
you
know
what
is
available
as
stable,
with
the
1.0
tracing
specification,
stability
and
and
just
the
rc's,
because
that's
more
release
focused
and
then,
of
course,
the
larger
discussion
of
you
know
what
that
entails
from
an
inversioning
standpoint
and
stability
guarantees
standpoint,
because
again,
there's
lots
of
detail
there
right.
So
I
I
mean
what
is
what
I'm
seeing
is
that
you
know,
since
most
of
the
providers
are
getting
a
bit
anxious
about.
A
You
know
what
what
the
condition
is
right
and-
and
we
have
said
that,
if
we
wanted
to
you
know,
get
to
1.0
for
tracing
specifically
the
sdks
at
least
at
least
three
sdks,
you
know
should
be
moving
in
that
direction
in
and-
and
I
think
that
we
had
discussed
at
some
point-
that
it
would
be
february
by
which
at
least
three
sdks
would
be
ready
with
the
tracing
stability
yeah.
We.
F
We're
looking
at
I
think
february
15th
is
like
the
announcement
date
yeah
and
so
yeah
getting
getting
our
ducks
in
the
row
there,
but
yeah
it's
a
good
point.
That
is
one
piece
of
feedback
I
would
like
is
like
I'll
try
to
post
it
by
end
of
week
for
review
on
the
comms
channel,
but
yeah,
whether
it
should
be
one
blog,
post
or
chopped
up
into
multiple
and
like
what
should
be
above
the
fold,
because
I
do
think
yeah.
It's
it's
an
important
announcement,
but
it's
also
one.
F
We
you
have
to
stick
the
landing
on
yeah,
because
the
main
thing
I'm
worried
about
is
you
know:
well
we're
not
going
to
be
able
to
stop
people
from
doing
this,
but
we're
already
getting
metrics
users
right.
Yes,
metrics
is
not
stable,
so
just
making
sure
that
that's
to
my
mind,
that's
like
the
two
clearest
things
are
tracing
a
stable
metrics
is
not
stable.
A
That's
correct
and,
and
I
mean
that's
what
I
have
been
communicating-
you
know,
because
again
our
target
is
that
as
we
get
to
2.0,
that
will
be
where
you
know
metrics
will
stabilize
so
really
reorienting.
The
idea
of
you
know
big
bang,
ga.
B
A
But
actually,
you
know
driving
towards
stability
component
by
component.
There
was
also
a
discussion
in
the
collector
said
earlier
this
week,
where
you
know
again.
The
discussion
has
been
that
I'd
like
to
see
stability
component
by
component
in
the
collector,
which
is
an
assortment
of
multiple
parts,
so
bogdan
has
suggested
a
review
of
the
components
you
know
and
and
tagging
them
as
stable,
ready
for
tracing
versus
other
types
of
data.
F
Nice
so
yeah,
I
could
see
there
being
like
three
blog
posts
in
a
row
here:
one
announcing
stable
tracing,
what
all
that
means
a
follow-up
on
like
the
the
metrics
roadmap
like
how
we're,
since
we
we
are
coming
up
with
like
a
tighter
plan
and
then
yeah
another
one
for
the
collector
roadmap.
A
Yeah
because
there's
no
reason
for
the
collector
to
be,
you
know
doing
a
big
bang.
Also
it's
just
you
know.
There
are
several
components
which
have
which
handle
all
three
data
streams
and
at
the
same
time,
then
there
are
other
components
that
only
are
very
specific
to
traces
or
metrics.
So
if
we
can
actually
gradually
move
towards
stability,
that
would
be
ideal.
F
Yeah
and
I
actually
changed
the
language
of
this
somewhat
in
the
spec
and
just
fyi,
the
the
terminology
I'd
like
to
see
us
start
using
is
open,
telemetry
clients.
F
In
the
past
we
had,
we
tended
to
just
say,
open,
telemetry
and
kind
of
like
imply
the
clients
or
the
sdk
or
like
whatever
we
happen
to
be
talking
about,
and
the
only
official
term
we
had
was
language
implementation,
but
people
outside
of
our
community
don't
totally
know
what
that
means
either
and
like
it's
the
client
portion.
So
that
seems
like
clients
would.
C
F
Yeah,
and
so
like
I
would
say,
like
the
main
thing
when
writing
going
forward
is
just
be
wary
of
when
you're
just
saying
open,
telemetry
but
you're
actually
referring
to
one
one
part
of
it.
We
tend
to
not
do
that
so
much
for
the
collector,
but
we've
done
that
with
like
other
components
and
and
that's
I've
had
feedback
now
that
that's
that's
been
a
little
confusing.
A
Definitely
yeah
I
mean
I've
used
library
and
implementations
for
the
api
sdks,
but
happy
to
you
know,
standardize.
F
A
F
F
Help
you
I've
been
trying
to
get
the
last
water
squeezed
out
of
this
stone.
There's
like
two
final
issues
that
have
to
get
closed
for
that
spec
to
go
1.0,
but
now
that
I'm
back
from
vacation
on
vacation,
I
should
say
now:
I'm
working
from
my
home
office
again
yeah
I'll
get
that
out
the
door.
So
you
should
see
draft
tomorrow,
cool
cool
ben.
B
B
I
think
I'm
not
sure
this
is
actually
a
problem
to
if
this
is
actually
a
problem,
if
I
just
perceive
it
might
be
a
problem
but
like
kevin
you're
saying
like
we
need
to
change
the
way
we're
talking
about
the
clients,
I
agree
completely
and
I
believe
that
we
might
just
have
enough
overlapped.
B
I
just
think
we
have
a
communication
issue
with
nothing
like
drastic,
but
I
wonder
if
maybe
there's
some
like
need
to
actually
address
that,
because
I
just
don't
trust
that,
like
saying
something
that
I
think
is
actually
totally
important
and
worthwhile
here
is
enough
to
get
the
project
to
understand
it.
C
B
More
general
thing
like
that,
I
mean
the
sort
of
I
mean
I
I'll
lead.
This
should
get
credit
for
this
she's
one
who's
suggesting
it
to
me
but
like,
but
just
something
like
I
don't
know
it's
kind
of
like
we
have
a
few
dots
we've
written
lately
that
have
a
bit
of
an
sla
around
certain
things
like
within
two
weeks,
we'll
respond
to
donation
requests
like
it's
more
like
you
know.
We
have
some
process,
I
guess
for
saying
listen!
B
This
is
something
that
everyone
needs
to
understand,
which
means
we're
going
to
write
something
about
it
on
the
hotel,
blog
and
we're
going
to
make
sure
it
comes
up
at
every
maintainer's
meeting
and
we're
going
to
like
check
them
off
and
say
yes
that
happened
or
whatever
I
mean,
that's
just
an
idea,
but
but
the
the
I
think
you
understand
the
spirit
of
what
I'm
saying
just
like.
What's
the
process
for
communicating
stuff
across
the
project
that
everyone
needs
to
at
least
like
see,
does
that
make
sense.
F
Yep
yeah,
we
tend
to
use
the
maintainers
meeting
to
try
to
do
that
kind
of
stuff.
A
I
mean
the
thing
is
that
ted
is
you
know,
referring
to
we've
seen
this
issue
before
right?
That
is,
even
with
the
current
pace
of
the
you
know,
rc's
towards
stability.
Different
different
maintainers
have
their
own
short
list
for
the
language
implementations,
and
you
know
it's
again.
A
There
is
an
kind
of
an
expectation
that
things
will
slide
right,
even
if
there
is
a
commitment
to
deliver
say
on
february
15th,
but
you
know
so
I
mean
again
kind
of
closing
that
gap
between
what
is
committed
to,
and
at
least
making
sure
that
that's
something
that
we
do
regularly.
You
know
within
that
week.
F
F
There
will
be
like
other
priorities,
I'm
sure
maintainers
want
to
work
on,
but
yeah
making
sure
the
metrics
stuff
is
done
in
a
coordinated
fashion
and
that
actually
it's
also,
we
have
to
improve
our
process
there
as
well
around
just
so
the
governance
committee
knows
we've
been
talking
about
this
with
the
maintainers
around
having
a
more
explicit
process
of
like
when
are
we
prototyping
versus
when
we've
decided?
We
we
like
this
and
we're
going
with
it
and
we're
committing
it
into
the
spec,
and
then
everyone
is
expected
to
go
implement
it.
F
E
F
So
it's
kind
of
led
yeah
maintainers
to
be
in
sort
of
a
nebulous
place
relative
to
the
spec,
where,
like
maintainers,
are
sort
of
running
against,
like
head
of
main
on
the
spec
necessarily,
instead
of
like
a
version
of
the
spec,
is
cut
and
then
you
go
implement
all
the
stuff
you're,
not
busy.
Prototyping,
and
part
of
that
is
because
we
don't
really
suspect
very
often
so
like
that.
F
That
process
really
has
to
get
tightened
up
where
some
people
are
prototyping
things
we
have
like
regular
releases
of
the
spec
and
and
people
are
like
clear
maintainers.
Have
it
clear
in
their
head
about
like
what's
what
stuff,
they're
prototyping
versus
what
stuff
that's
like,
they
feel
confident
they
can
just
go
implement
and
it's
not
gonna
thrash
out
from
under
them
or
they're
gonna
break
their
users,
which
is
the
other
thing.
We
have
to
really
start
caring
about
yeah.
A
And
also
just
using
a
simple
tagging
mechanism
for
communication:
that
is,
if
it
is,
you
know
too
heavy
weight
to
even
communicate
across
groups.
Even
tagging
can
help
on
reapers
saying
that
this
is
work
in
progress.
This
is
experimental
versus
this
is
stable
to
be
able
to
indicate
you
know
to
the
larger
contributor
pool,
what's
the
status,
and
how
can
we
actually
help?
A
It
is
again,
you
know
causing
a
lot
of
thrash.
I
can
see
on
the
language
contrib
repos,
especially
yeah,
where
you
know
there
are.
There
is
some
blockage
and
it's
very
difficult.
You
know
for
stability
and
trust
to
be
established
if,
if
we
don't
unblock
these
cross,
you
know
these
are
cross-functional
areas.
These
are
not
even
specific
to
one.
F
We
have
all
the
tools
we
need
to
do
this.
I
think
it's
it's
a
matter
of
leveraging
the
otep
process
a
bit
more
and
doing
more
prototyping
on
metrics
when
it's
in
the
otep
phase.
So
even
though
it'll
be
experimental
when
it
goes
into
the
spec
one
thing
I'm
trying
to
disseminate
is
like
experimental
does
not
mean
we
can
just
thrash
on
it
or
break
it
left
and
right.
Even
experimental
things
like
metrics
people
are,
are
gonna,
start
relying
on
and
so
we're
not
giving
long-term
support
guarantees
yet.
F
But
that
also
doesn't
mean
we
can
just
like
thrash
on
that
without
without
creating
trouble
for
our
users
and
ourselves.
So
so
just
having
a
clear
process
of
like
what's
getting
prototyped
who's,
prototyping
that
those
maintainers
being
aware
that
they're
prototyping
it
so
they're
making
sure
the
work's
you
know
being
expressed
their
users
more
clearly
and
then
the
other
maintainers
being
able
to
get
more
like
faster
releases
of
the
spec,
with
more
confidence
that,
like
okay,
I
don't
have
to
follow
ahead
of
the
specification.
F
There's
going
to
be
a
thing
that
comes
out,
I
can
look
at
the
change
log
there.
I
can
go
implement
those
features
and
then
rev
and
and
feel
confident
that
that's
that
process
is
going
to
be
saying-
and
I
don't
have
to
like
lose
my
mind
following
all
the
meetings
or
or
thrashing
my
users,
so
I
I'm
seeing
that
all
get
get
put
together.
The
the
metrics
track
is
really
getting
well
organized.
At
this
point,
I
think.
A
Yeah,
but
I
mean
it's
not
only
metrics
right,
there's
also
an
underlying
issue
of
of
just
release,
cadence,
even
on
on
components
that
are
stable
or
are
contributed.
A
I
mean
there
is
some
serious
blockage
on
you
know:
different
languages
not
having
enough
maintainers
to
be
able
to
you
know,
do
regular
releases
for
contrib,
reapers
and
and
at
the
same
time
you
know
not
not
diversifying
the
ci
process
and
the
cd
process
to
be
able
to
build.
You
know
individual
contrib,
contributed
components
and
and
make
those
artifacts
available.
F
Yeah,
I
mean
again
shout
out
if
anyone
has
a
php
maintainer
that
they're
hiding
somewhere,
please,
the
php
working
group
bob
would
really
love
a
second
maintainer.
There.
A
B
F
B
F
It's
great
jobs
that
aren't
jobs
yeah
like
is
it
like,
like
you
know,
we
need
like.
Are
you
interested
in
like
contributing?
Do
you
have
these
skills,
like
we
really
like
identifying
like,
because
to
a
certain
degree
like
it's?
Okay,
it's
not
jobs,
you
don't
get
paid,
but
it
is
a
community
where
people
do
get
paid
in
the
sense
that
they
get
allocated
by
an
employer
to
to
work
on
it.
F
So
that
and
then
it's
also
an
open
community
where
people
might
just
wander
in
and
want
to
help,
but
we
don't
have
that
listed
anywhere
right
now,
so
that
that
might
help
that
issue,
because
yeah
we're
doing
a
pretty
good
job
of
identifying
the
places
where
we
need
more
help.
But
it's
like
you
know
if
this
group
of
people
like
had
more
developers
that
they
could
just
bring
to
bear
on
those
problems,
I'm
sure
it
would
have
just
happened
already,
and
so
that's,
I
think,
part
of
the
issue.
A
I
think
that
it's
both
because
you
know
I
mean
we
have
like
four
developers
assigned
to
net
very
specifically
right
from
aws
and-
and
we
have
I
have
asked
you
know
our
current
maintainers
to
you-
know
work
with
with
them
to
give
them
tasks
that
they
can
work
through
and
you
know,
become
approvers
gain
the
rights
you
know
for
being
able
to
maintain
and
run
releases.
You
know
things
that
the
core
maintainers
don't
have
bandwidth
for,
and
it's
still
not
been
easy
to
get
that
going.
So
it's
it's
just.
A
F
Right
yeah,
so
that
was
also
another
idea
of
ahead
on
this
front
is
helping
the
maintainers
with
something
like
regular
review
cycles.
Again,
this
is,
like
you
know,
we're
building
a
real.
F
Here
and
one
thing
that
is
difficult
there
is,
you
know
it's
kind
of
like
on
the
maintainers,
not
just
to
like
notice
when
people
are
contributing
and
like
give
people
further
access
and
like,
but
if
we
don't
actually
have
like
a
process
or
timeline
or
or
a
way.
I.
F
Yeah
but
the
the
tc
is
kind
of
a
technical
group
right
like
they're,
not
no
offense
to
the
tc,
but
like
stuff,
that's
more
like
that
kind
of
project
management.
I
don't
that
hasn't.
I
think
traditionally
been
what
the
tc
focuses
a
lot
of
their
effort
on.
I.
A
Mean
it's
both
right.
It's
features
as
well
as
making
sure
that
the
technical
processes
are
working
right,
so
we
can
again.
I
know
we're
at
time
so
let's
kind
of
discuss.
A
F
Member,
it
could
be
anybody
one
thing
before
we
go
specific
to
net
since
you
brought
it
up.
If
you
have
people
interested
in
working
on
that
the.net,
auto
instrumentation
sig
is
actually
really
really
desperate
for
additional
hands
on
deck
there.
So
if
you
do
have
four
devs,
that's
a
separate
working
group
but
they're
there's
no
one
full
time
allocated
to
that
group
and
so
they're
they're
struggling
to
to
keep
pace
with
anything
they're
struggling
even
to
effectively
take
all
the
data
dog
stuff
and
port
it
over.
F
And
it's
just
due
to
a
lack
of
of
capacity
on
that
team.
F
F
B
F
The
way,
if
you
guys
don't
mind
if
aws
doesn't
mind
starting
to
attend
that
meeting
too
and
like
looking
at
that
backlog,
that
would
be
actually
super
super
helpful
for
the
net
project.