►
From YouTube: 2021-03-05 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
A
How
are
you
great
great
we're
having
a
cold
day
here,
but
staying
here
all
day
long,
so
not
entirely
bad?
Yes,
what
about
you?
You
are
based
in
seattle,
correct,
yeah
right,
and
so
how
are
things
going
there
for
you.
B
Yeah
so
here
like
we
have
been
having
sunny
days
since
early
this
week
and
also
like
I,
I
think
people
started
to
take
vaccine
like
a
month
ago
just
for
old
people
like
older
than
65,
but
now
they're
trying
to
cover
more
so
looking
at
the
trajectory
I
I
guess
probably
like
by
end
of
april.
B
A
I
have
been
working
remotely
for
basically
my
whole
life,
but
of
course,
if
you
are
used
to
going
to
the
office,
probably
stop
really
feeling
this
energy
yeah
anyway,
as
as
you
are,
you
may
have
read,
ted-
is
not
making
it
to
this
meeting
today,
so
yeah.
We
will
have
to
do
it
without
him.
I
guess
we
are
here,
hey
harold.
We
are
also
waiting
for
our
lolita.
A
A
A
But
you
know,
actually
something
interesting
is
that
after
we
released
1.04
tracing
now
the
release
after
ga
or
allow
for
ga
labels
do
not
apply
anymore
yeah.
We
need
to
do
something
about
that.
Yes,
I
was
talking
to
bogdan
like
a
few
weeks
ago
about
the
fact
that,
of
course,
in
this
release
his
metrics
very
metrics
oriented,
but
I
think
we
should
try
to
decide
what
things
we
really
want
to
see.
Tracing
or
resource
wise.
A
B
Yeah,
so
I
I
can
share
my
desktop
to
show:
let's
go
so
I
I
was
chatting
with
ted
last
week,
and-
and
this
is
where
we
are
today,
so
on
the
top
level,
we
have
the
projects
and
each
one
has
a
like
very
specific
purpose,
and
we
use
that
also
as
the
milestone
for
the
issues.
So,
if
you
go
to
the
spec
issues,
you
can
see
their
metrics
api
feature.
Freeze,
and
I
start
to
put
something
here
you
can
see
like
we
try
to
stage
things
so.
B
First,
we
want
to
reach
experimental
release
by
end
of
may
and
then
we
want
to
have
feature
freeze
by
end
of
september
and
then
we
have
stable
release
by
end
of
november
and
and
we
try
to
put
things
here-
not
stable,
just
to
make
sure
we
didn't
forget
about
those
things
and
based
on
the
actual
execution
we
might
figure
out.
Oh,
this
is
something
we
can
always
do
later,
but
we
need
that
before
stable
or
after
stable.
In
this
way,
we
will
put
things
in
different
milestones.
B
B
But
with
that
like,
if
you
look
at
the
experimental
release,
already
see
a
list
of
items
and
I
started
to
like
assign
those
items
to
myself
and
I
went
through
them
every
week
to
make
sure
like,
like
what
we
discussed
in
the
metric
sig
meeting
will
cover
the
topics
here,
or
at
least
I
I
got
it
very
clear,
like
if
people
decided
this
is
out
of
scope,
I'll
I'll,
go
ahead
and
close
the
issue
and
put
the
explanation
link
back
to
the
meeting
notes
for
the
projects
part.
B
This
is
something
that
github
is
not
very
good
at.
So
even
if
you
have
all
the
issues
properly
tagged
and
you
have
different
status,
but
here
projects
you
need
to
stitch
them
together
and
that's
not
automated.
So
that
was
thinking
we
could
automate
that,
but
I
suspect
we
could
find
some
resource
to
cover
that.
So
what
currently
I
have
is
that
I
got
1pm
from
microsoft,
who
went
here
to
do
some
of
the
work
that,
like
previously
covered
by
andrew
so
I'll
I'll,
try
like
he.
B
He
committed
that
he'll
spend
two
days
per
week,
just
to
help
us
to
manage
things
like
like
exit
on
our
current
like
schedule
and
items.
So
that's
that
could
accelerate
since,
but
he
he's
new
he's
he's
pretty
good
at
microsoft
like
internal
project
management,
and
I
have
high
confidence
but
open
temperature
is
pretty
new.
So
I
I'll
I'll
work
with
him
closely
to
ramp
him
up.
But
I
guess
probably
we'll
need
to
give
him
like
one
or
two
weeks
make
sense.
B
B
Yep
yeah,
and
I'm
also
thinking
like
probably
he
he
can
offload
ted
on
some
of
like
facilitating
the
meeting
or
like
you
and
no
colors,
sometimes
like
similar
like
this,
when
tight
is
away
like
by
default.
You
take
over
that.
I,
like
I
try
to.
I
try
to
make
sure
people
have
reasonable
load
instead
of
assuming,
like
you
own
everything
totally
so
like
like,
he
probably
can
start
by
managing
the
projects
and
try
to
like
make
sure
the
items
are
properly
tracked
and
then
once
we
have
a
good
shape.
B
I
expect
that
to
be
in
a
week
and
a
less
than
two
weeks
of
course,
and
once
we
have
that,
like
in
respect
meeting,
we
reserve
the
like
the
20
minutes
or
seven
minutes
whatever,
like
just
to
report
back
the
overall
status.
I
I
think
he
probably
can
take
that
time
to
just
update
people
and
also
give
people
a
heads
up,
which
part
are
we
making
good
progress?
Which
part?
B
A
Start
date
for
him
literally,
he
could
start
next
monday,
okay,
nice,
perfect,
so
let's
do
it.
Let's
do
it
very
nice.
Thank
you
for
setting
this
up
all
right.
So
I
guess
we
have
to
wait
for
a
little
bit
more
of
setup
before
we
can
actually
triage
the
issues.
I
think
we
can
now
go
and
set
the
labels,
but
that's
like
something
very
simple,
but
I
guess
I
guess
I
am
very
curious.
When
it
comes
to
the
actual
metrics
issues
triaging,
you
know.
I
think
you
guys.
B
The
plan,
so
I'm
I'm
doing
things
that
are
always
like
if
I
see
something
that
has
been
covered
in
the
meeting
and
there's
a
clear
note,
what
like
whether
it's
in
school
or
not
I'll,
just
go
ahead,
without
bothering
to
too
many
people,
something
not
not
clear,
I'll,
try
to
be
aggressive
and
just
pull
that
under
the
first
milestone
and
then
I'll
in
this
way.
It's
not
like,
I'm,
not
dropping
it
somewhere
and
forget
about
it
and
bring
that
back
to
the
meeting.
B
B
All
right
that
works
that
works
very
well
and
one
one
struggle.
I
I
think
we
have
like
the
product
is
growing
bigger.
I
think
no
one
can
cover
the
entire
scope.
So
this
is
why
I
saw
my
pr.
I
try
to
break
the
spec
down
into
smaller
pieces,
but
obviously
like.
I
know
that,
trying
to
clarify
the
ownership
and
define
the
rule
probably
take
take
a
long
conversation.
So
I'm
trying
to
do
that
in
parallel
by
trying
to
add
people
just
to
split
the
work,
especially
like
cementing
convention.
B
I
I
think
we
got
to
break
that
down
instead
of
saying
oh,
like
these
are
only
like
eight
people
and
they're
not
specific
to
any
domain,
but
they
will
randomly
pick
to
facilitate
one
thing,
but
it
seems
bogdan,
wanted
us
to
be
conservative
and
having
those
clearly
defined
to
actually
stand
up
too
hard
to
reward.
My
permission.
A
A
B
I'm
I'm
thinking,
probably
we
can
start
with
a
separate
file
like
a
google
doc,
although
I
hate
that,
like
a
google
doc
just
to
track
the
the
file
like
who
should
take
care
of
that,
then
for
triage
at
least.
We
know
we're
not
missing
anything.
A
Yeah,
well,
you
know
let's
wait
for
monday.
I
would
suggest
just
like
the
next,
the
next
business
day,
if
we
can
come
to
an
agreement,
what
he
expects
and
everything,
let's
just
do
that,
if
not
let's
go
with
this
alternative
yeah.
That
would
be
my
suggestion,
but
anyway
yeah
that's
going
to
help
a
lot,
and
I
can.
I
can
totally
tell
you
that
I
I
haven't
been
able
to
catch
up
with
the
semantic
convention
stuff.
It's
like
too
much
stuff.
You
know,
yeah
going.
I
have
no
idea
about
some
of
the
stuff.
B
Exactly
specific
yeah
I
mean,
if
there's
some
effort
and
people
notice
like
they
want
to
start
cover
some
aws
thing.
Well,
I
have
no
idea,
I
probably
can
use
my
common
sense
to
help
them,
but
in
the
end,
if
there
is
a
problem,
it
will
damage
the
overall
open,
telemetry
reputation.
So
I
want
at
least
to
make
sure
when
we
start
that
work
stream,
we
got
reasonable
coverage
similar
like
when
you
start
a
language
sig.
You
want
to
make
sure
they're
like
sufficient
like
stuff.
A
B
A
A
A
Right
so
in
that
way,
yeah
we
have.
We
can
probably
I
mean,
as
I
said
after
1.0,
we
really
need
to
know
and
some
clean
up
their
labels
included.
So
yeah,
that's
something
that
needs
to
be
done,
but
anyway
we
can
coordinate
with
this
new
contributor
that
you're
bringing
so
we
can.
We
know,
put
the
final
details
there.
A
Yeah
now
actually
have
one
more
question.
Well,
sorry
about
that
yeah
yeah.
I
saw
that
you
were
showing
also
the
the
the
projects.
You
know
like
the
milestones
and
all
that
and
there's
one
by
the
end
of
march,
which
is
for
the
metrics
data
model
yeah.
But
it's
I
don't
know.
Maybe
it's
just
me,
but
it
kind
of
feels
weird
that
we
will
probably
most
likely
will
be
including
a
few
tracing
issues
there
and
they
will
be
part
of
the
metrics
data
models.
B
Know
if
it's
fine,
you
know,
I
I
I
think
the
current
approach
is
we.
We
don't
use
the
milestone
as
a
as
a
collection
of
everything.
We
could
have
two
milestones
that
are
having
the
same
timeline.
That's
what
I
I
yeah
we're
going
so
so
let
me
show
you
one
example
here,
like
the
matrix
roadmap,
actually
people
people
like
the
approach
where
we
mentioned
something
like
this.
We
have
we
have
the
same
dates
repeated
here,
but
there
are
two
different
goals:
one
is
covering
the
metrics
api.
B
Another
is
the
premises
so
people
working
on
this
work
stream.
They
know
their
separate
timeline
if
they
need
to
slip
that
like
if
the
api
decided
to
sleep
for
a
month,
we
can
change
that
without
having
to
touch
the
other
plan
and
when
it
comes
to
the
actual,
like
the
physical
release
of
the
spec,
I
I
think
we
just
use
the
the
the
banner
in
in
the
very
top
of
the
stack.
So
if
we
decided
okay,
the
data
model
can
be
stable.
Then
we
just
flip
them
to
stable
and
create
a
new
release
tag.
A
Okay,
yeah
that
make
total
sense,
that's
good
to
know.
In
that
case,
I
guess
I
will
be
working
and
decide
about
trying
to
gather
what's
the
list
of
things
that
tracing
wise
or
baggage
wise,
we
want
to
have
like
really
want
to
have
soon,
as
I
mentioned
before,
shiftkin
or
trigger
specific
stuff
yeah.
So
we
can
have
we
can.
I
can
create
an
additional
parallel
milestone.
A
All
right
I
will
be.
I
was
start
thinking
about
that.
We
have
a
few
meetings
next
week,
so
I
can.
We
can
probably
discuss
in
details
with
that
yeah
I
don't
know.
I
think
we
have
to
be
a
little
bit
more
aggressive
with
what
we
just
do.
Well,
yes
or
no,
I
think
that
we
we
should
be
aggressive
by
limiting
what
we
want
for
for
tracing,
not
to
say,
let's
add
these
15
issues,
but
just
add
five
important
ones
anyway
yeah.
B
Yeah-
and
I
I
guess
like
once,
we
figured
out
what
we
want
to
do,
we
might
get
some
feedback
say
no,
no,
no,
like
like
go
with
a
different
direction,
but
as
long
as
we
start
to
categorize
issues
and
put
them
into
different
buckets
like
changing
the
way,
how
we
organize
things
should
be
much
easier.
The
the
key
part
is
how
to
identify
the
proper
scope
and
tag
those
items.
A
Yes,
that's
correct,
yeah,
that's
a
good
one!
By
the
way.
How
are
you
feeling
confidence
wise
about
the
the
milestone
by
the
end
of
the
month?
I
know
you
guys
have
been
working
a
lot,
but
how
is
it
looking?
What
are
you?
What
is
your
your
your
feeling
about.
B
B
Yes
right,
okay,
yeah,
so
I
I
believe
the
timeline
is
something
we
could
achieve,
but
but
we
need
to
do
a
good
job
there.
It's
not
something
like
very
like
we
have
a
hundred
percent
confidence,
but
it
is
achievable
and-
and
we
probably
need
to
get
more
support
and
being
able
to
make
decision
quicker.
I'm
I
I'm
trying
hard,
and
sometimes
I
figure
if
I
go
harder.
A
Yeah
sure
sure
all
right
yeah,
it's
it's
good
to
know,
yeah.
I
think
that
one
of
the
problems
that
we
need
to
actually
address
some
way
or
another
eventually
is
people
over
subscribing
like
we
that
we
are
sometimes
too
optimistic
about
the
amount
of
time
that
we
can
work
on
different
stuff
at
the
same
time,
and
sometimes
it's
just
unrealistic,
and
that
affects
the
the
outcome.
You
know
like
how
fast
we're
producing
stuff
when
we're
blocked
so
anyway,
to
think
about
in
the
near
future.
C
Yeah,
I
was,
I
was
actually
going
to
say,
I'm
I'm
relatively
new
to
the
project,
but
that's
actually
one
of
the
areas
that
I
I
feel
like
it's
difficult
to
to
really.
You
know
to
really
get
something
that
I
can
that
I
can
feel
like
okay.
Yes,
I
can
start
to
work
on
this
because
there
there
is
a
little
bit
of
like.
C
Obviously
there
are
team
members
who
have
been
here
for
a
while,
and
so
they
kind
of
know
the
general
direction
and
I've
been
trying
to
absorb
a
lot
of
the
things
specifically
I'm
interested
in
metrics
and,
like
you
said,
it's
like
it's
a
bit
mild
so,
like
you
like
we'll
have
these
conversations,
but
we'll
have
you
know
and
not
to
say
that
they
don't
need
to
happen.
C
But
it's
like
you,
have
this
long
conversation
and
then
there's
no
end
to
it
and
then
there's
no
there's
no
resolution
and
there's
no
action
item
to
to
take
out
of
it
now
a
lot
of
times.
There
are
action
items
for
certain
people,
but
again
it's
like
it's
the
same
people,
and
so
I
see.
C
That
leads
to
the
over
tax
thing.
It's
like
okay,
I
would
like
to
contribute.
How
can
I
contribute?
Let
me
know-
because
I
would
love
to
you
know-
do
something
that
that
that's
useful.
This
is
something
that
we're
looking
to
hopefully
implement,
and
you
know
making
this
work
is
potentially
something
that
we
can
that
I
could
commit
to.
I
just
need
to
know.
C
Or
yes,
so
so
for
us,
I
mean
I'm
interested
in
the
data
model
to
the
extent
that
you
know,
obviously
can't
you
can't
build
anything
else
without
knowing
what
the
data
model
is
going
to
be.
But
if,
if
that's
an
area,
I
wouldn't
say
that
I
would
I've
had
to
deal
with
a
lot
of
data,
translation
and
stuff,
but
I
wouldn't
say
that
I'm
an
expert.
So
if
that's
a
specific
area
that
could
use
pushing
I'd
be
more
than
happy
to
try
to
help
there.
B
B
C
B
So
so
previously,
like
folks,
were
focusing
on
tracing,
so
metrics
are
a
little
bit
messy,
but
we're
trying
to
catch
up,
and
recently
there
has
been
a
lot
of
progress.
So
probably
you
will
see
this
is
much
better.
So
this
is
the
the
data
model,
ga
plan-
and
we
already
have
the
items
here-
and
this
is
the
clear
scope
so
folks
in
that
say
already
already
confirmed
that
they
are
good
they're,
not
going
to
add
anything
new
here.
This
is
the
clear
scope.
We
just
moved
all
the
items
to
down
we're
done.
B
C
B
And
if
you
need
to
get
in
touch
with
someone
who
can
guide
you
on
which
item
you
can
start
to
contribute
reach
out
to
josh
here
you
can
see.
C
B
A
Yeah
looking
forward
to
have
this
this
contributor
for
microsoft,
that
will
help
us,
I'm
very
excited
about
that.
B
Okay,
cool!
Thank
you,
colors!
Okay,
perfect!
Thank
you!
So
much
guys
talk
to
you
next
week.
Ciao
see
you
next
week.
Thank
you.