►
From YouTube: 2022-03-18 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
C
B
Just
this
week
for
me,
I'm
visiting
the
the
most
of
the
team
is
in
austria,
so
I'm
visiting
them
this
week
so
we're
in
this
week,
but.
A
Yeah
we're
still
a
lot
in
home
office,
but
yeah
offices
are
open
again.
So.
D
Yeah,
so
for
microsoft,
we
started
in
march.
Like
the
first
day
of
march.
We
started
to
have
many
folks
back
to
the
office
and
by
end
of
march,
all
the
employees
have
to
make
a
written
decision
whether
they
want
to
go
back
to
the
office
and
spend
more
than
50
percent
of
the
time
or
if
they
prefer
to
spend
more
time
remotely,
they
have
to
get
approval
from
their
manager.
B
I
think
it's
going
to
be
the
same
here
except
I'm
officially
a
remote
employee
if
even
before
the
pandemic,
I
was
officially
remote.
So
I
don't
have
the
same
decision
to
make.
I
am
just
at
home,
but
oh
yeah
yeah,
I
think
most
of
ours
are
going
to
be
hybrid,
which
is
like
three
days
a
week
two
days
whatever
you
feel
like.
D
Okay,
it
seems
we
have,
we
have
the
column.
So
let
me
share
my
screen
and
start.
D
First,
let's
look
at
the
new
issues
that
are
coming.
D
D
C
D
Straightforward
yeah:
this
is
semantic
conventions.
We're
going
to
ignore
exemplar
clarification,
this
one
we
we
need
that
before
we
can
move
the
exemplar
part
in
the
sdk
spec
to
stable,
but
at
least
for
now
it's
not
blocking
the
the
initial
like
the
mixed
status
of
moving
all
the
parts
except,
for
example,
so
our
market
that's
allowed
for
pa
and
after
we
keep
the
initial
stable
version
of
the
spike.
Except
for
the
example.
We
can
change
this
back
to
required,
4g
and
work
on
getting
the
entire
spike
too
stable.
That
makes
sense,
yes,
sure.
D
D
The
only
open
comment.
Type
thing
is:
there's
a
nice
warning
suggestion
and
also,
like
I
think,
jack
opened
that
and
he's
flying
with
go
ahead
and
merge
the
pr
it's
a
it's
nice
to
have
like
warning
change,
which
gives
more
clarity,
but
not
that
not
necessarily
change
any
actual
spec
me.
D
D
Actually,
it's
error,
so
he
suggested
some
like
minor
warning
hinge,
but
later
he
suggested
it's
not
blocking
the
prs.
It's
a
nice
to
have
thing.
So
I
wonder
just
do
you
think
we
should
merge
the
pr
as
is,
or
you
want
to
take
some
time
to
fix
this.
D
C
D
And
if
you
can
take
a
quick
look
and-
and
if
you
think
this
is
something
blocking,
I
want
you
to
call
it
by
default.
I
I'm
going
to
put
a
note
here
saying
we
agreed
to
to
leave
this
as
a
nice
to
have
boarding
change
which
is
not
blocking,
and
I
can
create
an
issue
to
follow
up
on
that
and
another
thing
gosh.
We
need
your
help,
so
I
noticed
there's
a
broken
link:
okay
and
and
it's
not
changing
any
meaning,
it's
just
a
minor
like
typo
fix.
D
D
This
one
is
a
like
no-brainer,
so
basically
saying
like
we
we've
addressed
all
the
blocking
issues.
We
should
just
move
forward
and
and
then
make
a
focus
on
example,
and
then
the
entire
spike
would
be
stable
and
that
would
set
a
lifetime
stone
for
us
to
focus
on
the
next
big
things.
Like
the
hint
api
we've
been
talking
about
the
boundary
instrument,
the
like
the
base
tool
exponential,
like
histogram
those
things.
D
F
D
B
D
Keep
this
meeting
or
after
that
we're
done,
I
suggest
maybe
we
keep
it
and
and
depending
on
the
actual
status,
we
can
decide
whether
we
need.
E
F
G
D
G
D
D
Yes,
I
I'll
put
a
link-
I
I
guess
this
is
not
directly
tied
to
the
release
schedule,
but
if
people
want
to
take
a
look,
it'll
be
helpful
to
give
your
opinion,
I
I
think
the
interesting
thing
is:
what's
the
default
export
interval
for
console
it's
a
very
subjective
thing.
We
know
that
exporting
one
minute
probably
wouldn't
make
sense,
because
console
is
intended
to
be
more
interactive,
but
I
I've
seen
like
there's
some
question
about
whether
it
should
be
one
second,
five,
ten
fifteen.
E
What
was
that
crosstalk?
I'm
sorry.
What
was
that
sorry?
I
am
in
a
coffee
shop.
I
was
just
saying
that
we
are
not
even
catching
all
the
errors,
all
the
possible
errors,
patrice
who
has
been
working
on
the
website.
He
has
been
found.
He
hasn't
found.
Well,
he
gets
found.
I
don't
remember
exactly
how
many
errors,
but
like
a
few
of
them,
yeah.