►
From YouTube: 2022-01-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
Really
I
went
to
utah
park
city
this
year,
but
it's
quite
crowded
there,
like
super
crowded.
A
Oh,
no,
not
really
I'm
in
redmond,
but
I
got
I
epic
pass
so
yeah.
It's
free
entry
for
the
epic
pass
holder.
D
C
Yeah
for
me,
I
have
to
click
on
the
more
details
in
the
calendar
to
get
the
link.
D
Okay,
I
only
saw
like
kudkash
in
the
other
call,
so
yeah
he's
back
here
and
I'm
also
so,
hopefully
no
one
gets
the
wrong
leak.
Okay,
let
me
share
my
screen.
D
Okay,
yeah,
I
think
we
can
start
if
you're
in
the
cold
place.
Add
your
name
to
the
list,
so
we
did
not
have
meetings
for
the
last
two
weeks,
so
we
are
all
like
meeting
after
three
almost
three
weeks
now.
D
D
We
don't
have
date
for
one
two
to
eight,
so
that's
probably
the
only
thing
I
have
to
share.
So
let's
look
at
any
other
questions.
B
D
On,
let's
put
it
and
discuss
right
now,
so
what
was
this
question
so
automatically
yeah?
I
think
this
is
something
which
we
wanted
to
do,
but
the
original
spec
pr
never
got
merged
yeah.
It
could
abandoned
like
a
few
months
back,
so
we
still
want
to
do
it
at
least
for
the
pr,
because
the
spec
repo
still
has
it
for
prs.
D
We
should
be
able
to
just
because
this
one
had
some
people
objecting,
because
this
was
basically
incentivising
people
to
ignore
issues,
because
over
time
they
get
stale
and
get
closed
automatically.
D
So
the
answer
to
this
question
is
yes,
we
still
need
it.
We
can
just
like
restrict
it
to
the
prs
for
now
and
for
issues,
let's
wait
and
see
if,
like
specification
itself,
yeah
okay,
this
is
a
one
from
spec
itself,
yeah
yeah.
This
is
only
first
pr,
so
maybe
we
can
copy
this
as
and
then
come
back
to
this
problem,
if,
like
spec,
ever
define
something
for
issues.
D
B
Yeah
this
was
an
interesting
one
that
came
up
or
the
holidays.
I
think
this
person
is
from
microsoft
from
the
looks
of
his
github
profile,
but.
C
D
Not
to
my
knowledge,
I
don't
recollect
having
anything
similar
to
this.
This
is
similar
to
durable
tasks,
so
something
specific
to
azure.
D
Yeah,
I
don't
have
any
knowledge
about
this
one,
but
it's
an
interesting
use
case
because
it's
so
you
start
the
span
in
one
machine
and
you
let
it
flow
to
the
other
one.
And
then
you
continue.
The
overall
time
would
be
the
sum
of
the
time
spent
in
like
process
one
and
process
two.
So,
okay,
this
is
very
interesting
yeah.
We
cannot
model
it
currently
see
by
sitting
tricedy,
okay
yeah,
but
that's
just
a
like
really
hacky
way:
sadie
and
planet
and
calling
stop
without
start.
B
Lot
of
the
the
context
of
the
span
you'd
effectively
need
to
serialize
the
span
across
processes,
but
a
little
bit
of
research
on
that
it
seems
that
activity
is
not
serializable,
so
yep.
D
Yeah
but
like
this
walk
around
like
it's
like
just
a
hack
like
it
just
works,
but
that
is
probably
relying
on
some
internal
implementation
details
of
activity
class
because,
like
activity
still
allows
one
to
create
an
activity
using
the
constructor
like
new
activity,
you
don't
need
to
ever
start
it.
You
can
simply
stop
it.
So
this
seems
like
working
just
because,
like
activity
existed
before
respect
so
yeah,
so
I
think
this
is
best
to
open
an
issue
in
the
spec
unlock.
D
D
So
maybe
I
can
like
poke
around
and
see
whether,
like
there
is
someone
from
who
the
durable
task
repo,
who
might
be
interested
in
pursuing
this.
E
D
Let
me
see
if
there
is
anything
more
in
the
agenda
yeah,
I
think
that's
pretty
much
it
yeah,
I
mean
looks
like
we
have
a
lot
of
folks
today,
hello,
everyone.
So
you
can
add
your
name
here
and
by
next
week
we
will
start
normal
activities,
so
there
are
like
plenty
of
prs
open
since,
like
probably
like,
first
week
of
december
onwards,
so
I
was
not
very
active,
so
I'll
be
looking
at
them
as
soon
as
possible,
so
I'll
be
getting
back
to
work
tomorrow.
D
So
you
can
expect
me
to
do
all
the
things
which
we
are
painting
from
two
weeks
back.
Oh
three
weeks
back,
I
think
the
one
top
thing
which
we
really
wanted
to
tackle
was
the
configuration
for
otl
exporter,
so
michael
had
an
idea
and
then
had
a
similar
one.
D
So
I
would
be
looking
at
it
at
my
as
my
one
of
the
toppings
and
then
yeah
we'll
see
if
the
spec
is
close
to
making
the
matrix,
stable
and
based
on
that
we
can
continue
the
1.2
plan,
since
I
don't
have
any
actual
date
from
the
spec.
D
I
I
would
just
say
it's
unknown
at
this
point
so
once
I
know
the
date
like
we'll
recreate
the
milestones,
because
the
milestones
are
all
now
outdated
because
it
still
says
like
this
in
the
first
week
or
something
but
yeah
I'll,
come
back
to
it
by
next
sig
meeting
after
I
learn
more
from
the
specifications.
B
D
B
Yeah,
whenever
you're
ready,
I'm
I'm
pretty
available
so.
D
D
D
Maybe
if
it
helps
we
can
discuss,
we
can
have
a
mini
cube
meeting
with
michael
allen,
myself
and
who
else
might
be
interested,
we'll
post
it
in
the
slack
channel
if
you're
a
meeting
and
then
come
back
and
try
to
actually
solve
it
before
next
week
meeting
it
looks
like
we
have
a
lot
of
peers
open
like
50
to
us,
yeah,
maybe
yeah.
All
these
things
requires
some
attention
yeah,
so
I'll
get
to
it
like
in
the
priority
order.
D
D
If
not,
we
can
meet
again
next
week
and
if
there
are
any
tiers
which
require
like
active
attention,
please
mention
me
or
mention
any
of
the
maintenance
or
even
post
it
in
the
slack
channel,
so
we
can
get
to
it
sooner
than
because
there's
like
a
lot
of
backlogs,
so
we
would
want
to
prioritize
if
there
is
anything
which
he's
not
getting
attention,
please
bring
it
up
to
the
slack
channel
or
by
mentioning
one
of
the
maintainers
all
right.
I
guess
that's
it
happy
new
year.