►
From YouTube: 2021-01-07 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
B
E
Yeah
I
have
to
stay
a
little
longer
because
my
mom
is
like
mom's
70
and
she's
being
stubborn
about
taking
care
of
herself,
so
I
have
to
be
the
helicopter
parent.
I
see
good
good
yeah.
Sometimes
you
need
to
have
that
push
it's
funny
because,
like
I
now
seems
like
I'm
lecturing
her,
she
gives
me
these
facial
expressions.
I'm
like
oh,
that's
where
I
got
it
from.
E
She's
adamant
that
she
can
take
care
of
herself
and
that
like,
but
it's
like,
so
she
has
she
just
suddenly
developed,
really
bad
arthritis
where
she
like
can't
really
move
her
shoulders
and
she's.
Like
oh
I'm
talking
to
the
doctor,
and
I'm
like.
Let
me
get
on
the
call
of
the
doctor
and
the
doctor
is
like.
Oh,
you
didn't
say
that
I'm
like
that's
what
I
thought
mom
I'm
gonna
drag
you
to
all
the
pt
and
test
right
now
and
she's
like
thank
you.
E
C
Yeah,
I
think
spoons
co-worker
at
lightstep
was
saying
his
five-year-old,
I
believe,
has
picked
up
the
phrase
for
the
record.
G
I'm
also
moving
up
to
vancouver
tomorrow,
awesome
congrats.
G
F
C
The
link
yeah
just
filling
out
this
sheet.
We
don't
have
much
of
an
agenda
coming
back
from
break.
B
C
This
is
just
trivial
administrative,
I
think
morgan,
you
at
least
temporarily
perhaps
still
have
access
to
the
google
calendar.
G
G
So
so
anyone
who
I
gave
access
to
already
can
edit
and
make
whatever
changes
they
want,
because
I
created
the
calendar
originally
at
google,
which
in
hindsight
was
a
huge
mistake.
Only
people
of
google.com
email
addresses
can
add
additional
administrators.
C
Yeah,
okay,
well,
the
the
one
thing
I
was
noticing
is
maintainers
currently
aren't
on
that
list,
and
we
bumped
into
like
a
couple
of
times
where
they
wanted
to.
We
noticed
it
around
chris.
G
I
B
You
can
probably
see
the
the
emails
on
the
vacation
calendar.
C
C
G
The
vacation
calendar
does
not
have
this
issue,
because
I
created
that
one
for
gmail
account
so
that
one's
anyone
who
has
admin
rights,
which
is
all
the
people
can
add
events,
can
also
add
more
admins
to
it.
Is
it
difficult
to
migrate.
G
G
Well,
I
mean
yeah,
I
think
it
was.
I
also
I
think
our
calendar
was
literally
just
the
old
open
sentence
calendar
or
something
which
so
like
it
dates
back
to
like
late
2016
early
2017.,
when
I
think
actually,
they
probably
didn't,
have
those
restrictions
in
the
first
place.
G
I
G
I
I
Okay,
but
meanwhile,
if
you
need
urgent
access,
just
share
this
link
with
people,
there
is
instruction.
A
Ted,
did
you
also
want
to
give
a
quick
update
on
the
versioning
discussions
yeah.
C
C
What
are
we
actually
offering
people
and
to
also
try
to
to
break
that
up
from
this
monolithic,
open,
telemetry,
ga
concept,
which
wasn't
really
matching
reality
to
something
that
would
allow
us
to
start
releasing
stable,
1.0
versions
of
tracing
and
all
the
languages
that
have
it
so
that
work
is,
is
pretty
much
done,
and
I
expect
some
languages
to
start
announcing
their
1.00
potentially
later
in
january,
like
but.net
being
the
first
first
there.
C
So
my
plan
is
to
to
to
work
with
these
groups
to
to
just
get
the
announcements
lined
up
and
try
to
figure
out
where,
where
we're
at
maybe
through
the
maintainers
meeting,
I
realize
we
don't
totally
have
an
automated
way
or
even
a
manual
way
to
to
track
all
of
these
releases
and
what
goes
in
them.
We
had
an
aborted
attempt
to
do
that
on
the
website,
so
just.
C
If
the
data
changes,
it
seems
like
there's
a
variety
of
ways:
data
could
change
that
could
break
some
kind
of
dashboard
or
backward
back
in
somewhere,
and
that
was
like
a
sufficiently
broad
set
of
things
that
didn't
seem
to
to
boil
down
to
something
that
was
easily
put
into
like
some
high
level
guidelines.
C
So
we
punted
on
that
bit
for
now,
because
it's
not
actually
clear
to
us
what
we
want
to
offer
there.
But
that
is
something
people
identified
as
very
important
and
I
agree
with
them.
We
do
have
to
figure
out
how
to
keep
the
the
data
stable.
C
So
if
people
have
good
ideas
on
that
front-
or
you
know
have
a
background
in
trying
to
do
that,
work
help
would
be
appreciated.
C
Sorting
that
particular
issue
out
it
seems
like
plenty
of
organizations
have
done
it,
but
because
they
control
both
the
front
end
and
the
back
end,
because
they're
doing
it
all
in
house
there's
often
a
lot
of
ad
hoc
stuff
that
goes
on
there.
That's
harder
to
do
when
you
don't
know
what
the
back
end
actually
is.
C
A
Yeah,
I
think
this
will
be
very
helpful
because
some
of
the
language
maintainers
have
already
started
driving
towards
stability
and
that's
exciting.
D
C
It's
going
to
be
a
big,
it's
going
to
be
a
big
shift.
I
think
when
we
start
telling
people
things
are
1.0
and
stable.
I
do
worry,
there's
so
much
interest
in
metrics
that
the
next
couple
of
months
will
be
a
little
bumpy
on
that
front,
which
is
the
other
primary
thing
is
just.
C
I
want
to
help
turn
my
attention
from
tracing
to
metrics
now
to
see
about
just
getting
that
over
the
finish
line,
not
designing
the
metric
stuff,
but
helping
to
find
consensus
and
making
sure
we
can
clean
that
up
and
land
it
soon,
because
that's
that's
the
current
spec
issue.
Du
jour
is
getting
getting
metrics
fully
baked,
which
is
even
more
complicated
issue
than
getting
tracing
fully
baked,
because
there's
so
much
prior
right.
There.
C
B
H
A
You
know
get
many
of
the
requirements
that
are
still
open,
hammered
out.
C
Yeah
just
doing
a
straw
poll
of
maintainers,
it
does
feel
like
people,
you
know
their
workload
is
lightening
up
a
bit
on
the
tracing
side,
as
all
of
that
gets
buttoned
down.
C
But
there
is
some
concern
that
most
of
the
maintainers
don't
have
a
background
in
metrics,
because
the
reason
they're
currently
maintainers
they
had
a
background
in
tracing
or
they
had
an
interest
in
that
and
so
there
I
have
had
some
maintainers
voice
concerned
that
they
would
love
to
see
more
metrics
experts
around
not
even
necessarily
debating
this
spec
with
josh,
but
at
least
around
like
implementing
all
this
stuff
in
the
different
languages.
They're
feeling.
A
Nervous,
definitely
ted
and,
and
what
what
you
know
I've
been
doing
and
jana
has
been.
You
know,
jan
and
I've
been
working
together
on
that,
and
some
of
you
are
aware
of
that
is
that
we've
been
pulling
in
the
prometheus
team
and
the
open
metrics
teams
to
actually
come
in
and
join
up
and
participate,
and
they
are,
you
know,
that's
one
of
the
reasons
why
I
have
asked
for
a
weekly
work
group,
and
this
is
again
pulling
in
that
heft
into
you
know
for
metrics
into
the
project.
C
Great
yeah
so
for
people
looking
to
resource
open,
telemetry
this
quarter
and
next
quarter.
I
do
think
if
there
are
more
people
who
understand
metrics
enough
to
implement
this
stuff
well,
but
are
not
so
iconoclastic
that
they
can.
They
can
work
with
the
metrics
implementation.
That's
maybe
different
from
their
particular
one.
I
think
that's.
C
K
I
think
I
think
we
should
not
forget
the
motivation
of
the
metrics
and
I
do
understand
a
lot
of
the
incentives
from
prometheus
folks
and
and
open
metrics
folks,
but
one
of
the
our
intention
goal
was
to
to
make
things
backwards,
compatible
with
open
senses
and
and
things
that
we
agreed
on
so
yeah,
even
though
I
do
agree
that
it's
nice
to
to
talk
with
everyone
and
have
everyone
on
board.
A
Yeah
and
I
think
bogdan
to
your
point-
I
agree-
you
know
it
really
is
interoperability,
because
for
customers,
interoperability
matters
a
lot
and
and
that's
something
that
we
need
to
absolutely
guarantee
from
the
project.
K
Not
necessarily
true,
but
I
mean
the
re.
The
reason
why
I'm
not
I'm
saying
not
necessarily
true
is
again
repeating
what
our
initial
goal
was
was
to
to
to
merge
the
two
projects
open,
sensors
compound
tracing,
and
I
think
we
we
need
to
to
be
more
precise,
on
keeping
backwards
compatible
with
open
sensors.
There
yeah
that
that's.
I
C
Nervous
about
the
open
census
compatibility
just
because
I
feel,
like
I've,
seen
less
work
going
on
on
that
part
of
it.
Maybe
there's
like
google
stuff
happening
that
I
haven't
been
looking
at,
so
I've
been
like
the
open
tracing
stuff.
We
we
verified
that
that
stuff
generally
works,
I'm
a
little
nervous.
Maybe
we're
gonna
find
something
with
open
census
where
it
doesn't.
K
A
A
Sure
again,
I
had
three
specific
areas
that
just
wanted
to
you
know
call
out.
I
have
the
document
that
I
added
for
our
project
stats
usage.
I
have
added
an
initial
document,
would
love
to
get.
You
know
everybody's
review
and
feedback
and
also,
of
course,
editions
did.
I
share
the
link
it's
on
the
first
issue.
Let
me
just
put
that
up
five
six
four
create
guidelines.
H
Okay,
that
one
quick
question-
I
I
don't
want
to
have
the
full
discussion
here,
but
just
in
terms
of
the
scope
I
mean
I,
I
believe
that
that
doc
is
mainly
about
the
dubsteps
issue.
Specifically,
there's
also
this
question
of
like
how
are
we
going
to
constrain.
A
I
think
ben
I
expanded
it
to
a
larger
scope
in
terms
of
the
dock
itself.
I
you
know
looked
at
it
as
project
data
rather
than
just
dev
stats,
and
that
includes
you
know
brand
and
trademark
guidelines,
as
well
as
other
areas
that
you
know
I
I
was
looking
at,
but
please,
you
know,
feel
free
to
expand
the
scope.
H
A
Yes,
exactly
and
I
did
expand
the
scope
to
be
more
raw
marketing,
so
please
feel
free
to
you
know.
Edit
add
I
know
sega
and
some
of
the
others
have
already
had
a
chance
to
look
at
it.
But
please
take
a
look
and
add,
I
think.
H
A
Think
when
that
we
do
need
to
look
at
the
overall
picture,
because
you
know
dev
stats
is
just
one
of
the
examples
right
and-
and
it
happens
to
be
the
concrete
example
that
we
picked
up.
But
it's
it's,
I
think,
good-
to
have
general
guidelines.
Okay,.
K
K
J
A
Let's
fix
it,
yeah,
let's
fix
it,
I
mean
again,
don't
do
it
bogdan
nothing.
Specific
about
splunk
needs
to
be
yeah.
A
K
No
because
because
if
we
start,
if
we
start
saying
that
negative
things,
there
are
other
negative
things
that
happen,
and
people
will
like
to
point
that
as
well
and
whatever.
Let's
not
start,
let's
not
start
that.
So
my
point
is:
let's:
let's,
let's
make
the
document
saying
positive
things,
and
here
is
how
you
should
do
it.
Not
here
is
how
you
should
do
it.
Yeah.
H
Yeah,
I
was
going
to
say
something
similar.
I
think
that
the
principles
can
be
framed
positively,
but
one
thing
I
found
very
effective
is
kind
of
like
if
you
as
prior
I'd
reference
this
the
shrunken
whites
elements
of
style,
where
you
have
a
few
good
examples
and
bad
examples.
Just
two
or
three
of
a
couple
of
principles
I
think,
would
go
a
long
way
and
probably
be
better
than
trying
to
formally
describe
the
rule
purposes.
So
so
I
I
absolutely.
H
K
Yeah,
I'm
not
saying,
as
I
said,
my
point
was
that's
the
only
example
in
that
document
and
I
think
is
not
fair,
because
there
are
other
examples
that
can
be
put
there.
G
J
A
As
next
steps
again,
you
know
I
I'll
definitely
take
the
feedback.
You
know
that
of
some
of
the
areas
we
discussed
and
add
that,
but
again
you
guys
should
also
feel
free
to
you
know
edit
modify,
add
more
examples
and
and
take
a
crack
yeah.
A
Sure
all
right,
so
I
just
had
two
other
actually
a
few
other
points
that
just
wanted
to
bring
up
one
was
that
again
a
request
for
two
work
groups:
one
is
a
sig,
a
lambda
sig
and
for
I
think
we
had
a
conversation
with
ted
and
with
alex
from
knightstep
and
again
you
know
we
are
starting
to
work
on
lambda
specific
functionality.
We
built
out
a
python
implementation,
also
in
november
december,
which
we'd
like
to
add
to
the
project.
A
So
you
know
again
I'm
in
the
process
of
moving
that
code
over
to
open,
telemetry
and
also
would
like
to
you
know,
get
more
folks
involved
just
in
the
lambda
discussions,
not
lambda
specific,
but
really
you
know
actually
driving
and
more
function,
less
platform,
support
architecture
and,
in
you
know,
support
in
open
telemetry
in
general,
so
ted
again
looking
forward
to
working
with
you
and
alex
and
others
closely
yeah.
So.
A
Right
right,
I
just
wanted
to
bring
that
up.
It's
more
just
sergey,
just
to
set
up
a
time
which
works
for
folks
and
just
have
a
weekly
calendar,
invite
for
a
new
seg,
yeah
and
and
the
same
thing
again.
It
was
a
request.
We
discussed
this
in
the
spec
meeting
and
really
to
formalize
the
request
that
we've
had
for
prometheus.
You
know
deep
dive
that
we
need
to
work
on
and
really
pulling
in
using
this
as
a
mechanism
to
drive
and
pull
in
more
metrics.
You
know
contributors
and
experts.
C
A
Yes,
exactly
so
again,
it's
it's
just
an
anchor
to
start
off
the
you
know,
deeper
conversations,
josh
and
bogdan.
Both
have
been
very
involved
and
looking
forward
to
really
picking
up
steam
on
that
in
the
metrics
area,
quick
quickly,
and
then
there
are
two
other
areas
that
you
know.
At
least
I've
been
working
on
to
make
sure
that
this
was
based
on
some
of
the
board
discussions.
A
We'd
had
earlier,
you
know
in
november
and
december
on
the
migration
that
cncf
has
requested
for
all
the
cicd
workflows
to
be
migrated
from
circle
ci
to
github
actions
and
towards
that
again
you
know
my
team
has
been
filing
prs.
I've
been
reviewing
and
you
know,
we've
been
kind
of
doing
them
to
make
sure
that
you
know
all
the
repos
have
solid,
updated
recent.
A
You
know
lee
tested
workflows
for
ci
as
well
as
cd
and
again,
thanks
to
all
the
maintainers
who've
been
reviewing
that,
so
we
are
almost
there
and
I
think,
there's
only
one
more
one,
more
repo
that
is
left,
which
is
the
collector
contrib,
but
other
than
that.
The
prs
are
all
in
progress.
The
maintainers
you
know
are
in
the
process
of
reviewing,
so
we
should
be
able
to
complete
that
migration,
pretty.
B
Soon,
one
thing
this
may
be
only
affecting
js
and
it's
the
reason
that
our
contrib
pr
isn't
merged.
Yet
we've
seen
a
significant
slowdown
in
the
tests
after
moving
from
circle
to
github
like
very,
very
drastic
and
the
tests
have
become
flaky,
they've
started
timing
out,
especially
ones
that
depend
on
like
external
services.
B
Like
you
know,
if
we're
testing
the
the
grpc
instrumentation
package,
for
instance,
it
makes
actual
grpc
requests
as
part
of
the
test
and
when
we
run
a
lot
of
tests
in
parallel,
we
see
them
time
out
fairly
often,
and
it's
become
pretty
frustrating
so
our
contrib
package,
because
it's
almost
all
instrumentation
packages-
I
just
I
foresee
that
becoming
flaky
to
the
point
of
being
almost
useless.
I.
A
Think
I
think
daniel
one
of
the
issues
that
I
saw
and
I
you
know
we
tested
this-
is
the
the
you
have
to
actually
implement
a
more
sophisticated
caching
mechanism
that
github
provides
for
you
know
some
of
the
workflows
as
they
exist.
A
So
let's
take
a
look
at
that
and
see
if
we
can,
because
we
noticed
that
slowdown
also,
especially
when
we
were
testing
on
the
collector,
you
know
repo,
given
it
has
so
many
components
that
you
know
get
get
built
and
then
tests
are
run
for
so
you
really
see
an
huge
slowdown
on.
You
know
the
execu
the
completion
time.
So,
let's
maybe
let's
discuss
that.
I
Okay,
yeah
and
if
you
need
to
meet
with
github
people,
we
already
met
them
with
them
once
and
they
were
very
open
to
help
troubleshoot.
Whatever
issues
we
have
cool.
A
A
And
and
again
you
know
the
idea
really
was:
let's
pull
this.
You
know
complete
this
initial
migration
and
then
optimize
in
the
areas
that
we
need
to,
and
and
just
to
that
also
there
is
another
area
that
you
know
we've
been
looking
at
and
I
have
been
driving,
which
is
the
adding
security
scans
with
codeql,
which
is
available
for
github
reapers
to
the
collector,
as
well
as
the
language
sdks,
which
really
improves
again.
A
I
had
opened
up
a
notep
for
it
and
you
know
really
improving
the
quality
and
building
trust
which
really
helps
our
security
reviews
for
downstream
the
downstream
distribution
as
well.
As
you
know,
customer
requests
in
general.
I
Okay,
I
have
next
item
very
small
one.
I
wonder
what
how
we're
doing
on
getting
out
of
sandbox,
because
this
year
maintains
track,
is
limited
to
incubation
plus.
So
is
there
any
updates.
E
I
have
a
doc
I
need
to
send
out.
I
need
to
reach
it
from
steve.
Has
it
and
he
hasn't
sent
it
to
me,
he's
on
vacation?
It's
been
hard
to
reach
him,
but
once
I
have
access
to
a
doc
I'll,
send
it
out
yeah.
H
And
I
also
just
had
a
meta
thing
that
there
are
a
bunch
of
ais
from
our
last
meeting
december.
That
I
mean
many
of
which
are
on
my
list
by
the
way
that
haven't
been
done.
We
should
just
do
them.
H
I
don't
need
to
say
any
more
than
that,
but
there's
some
stuff
around
like
the
mission,
vision,
type
stuff
and
then
some
other
things
about
contributors,
but
I
think
that'll
actually
really
help
with
the
marketing
guidelines
to
be
able
to
point
at
the
the
idea
of
a
public
mission
that
we
have
to
support
in
our
messaging
whatever.
So
anyway,
just
remind
me,
we
should
all
like
just
everyone,
just
look
at
the
notes
and
put
the
stuff
on
your
list.