►
From YouTube: 2022-03-09 Workspace 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
Yeah
I'll
I'll
need
to
leave
in
about
15
minutes.
B
I
I
need
to
take
care
of
some
personal
stuff
sure
you
can
give
it
a
bit
of
time
if
anyone
else
wants
to
join
just
just
leave
as
a
fyi.
A
A
B
I
I
knew
the
behavior,
but
I
did
not
expect
that
we'll
have
that
many
things
like
lined
up
like
I
didn't
know
about
the
ci
builds
migration
right
because
I'm
not
reviewing
every
single.
Mr,
so
absolutely.
B
I
was
not
aware
of
that,
but
I
was
aware
of
the
fact
that
we
do
this
batching
sequentially.
A
B
And
that
that's
a
limitation
yeah,
I
don't
know
that
we
can
do
much
about
that.
B
Maybe
we
can
think
about
some
improvements
like
splitting
into
very
important
migrations
and
migrations
that
can
take
long
long
times,
even
though
all
of
these
batched
migrations
are
are
geared
towards
long
migrations
because
they
need
to
scan
the
whole
table.
So
this
is
why
they
are
very
like
slow
and
down
in
batches
but
yeah.
I
like,
I,
don't
think
there
is
a
super
easy
way
out
of
out
of
this.
B
So
yeah
about
the
notification,
I
I'm
I
was
just
wondering
if
we
can
just
add
a
note
to
the
engineering
weekly
or
something
and
let
know
people
that
we
have
this
in
place
and
eventually
we'll
just
have
it
backfilled.
So
people
can
maybe
we
will
let
them
know
once
again
because,
like
I
don't
know,
what's
the
best
way
to
let
the
entire
engineering
team
know
about
the
progress
on
this
project
and
and
yeah
like
them
being
aware
that
we
now
have
project
name
spaces.
A
But
in
the
same
time
like
we
haven't
migrated
members,
yet
we
haven't
migrated
routes,
it's
like
and
the
problems
of
vibrating
won't
start
in
30
days.
B
Obviously
it
will
be
easier
if
we
already
have
a
couple
examples:
the
browsing,
the
members
but
other
than
that,
I
don't
think
that's
a
a
big
blocker
and
that's
where
I
kind
of
mentioned
that
in
in
the
point
three:
okay,
yes,
where
we're
like,
I
don't
think
we
should
like
block
everyone
from
just
start
doing
stuff
unless
there
is
something
that
I'm
I'm
really
missing
here,
which
which
totally
may
be
the
case,
but
otherwise
like
yeah.
Let's,
let's
move
forward.
Let's
do
it
and
the
sooner
the
better.
Obviously.
A
Okay,
okay,
I
will
work
with
aurit
on
phase
two
clean
up,
but
she
suggested
a
similar
thing,
so
we
move
everything
other
than
membership
consolidation
about
consolidation
to
phase
three
and
then
from
facebook.
We
will
take
it
further.
A
My
only
question
is
about
importing
and
exporting,
because
I
know
that
import
expert
group
has
this
idea
that
if
you
change
something
that
influences
import,
export
you're
responsible
for
import
export
as
well
of
these
like
new
features-
and
I
wonder
if
this
is
the
other
thing
that
we
should
think
about,
because
if
we
migrate
routes
and
especially
memberships
and
like
project
name
spaces,
then
we
should
also
like
take
take
a
look
at
import
export
process.
B
Yeah,
I
I
think
like
I
did
not.
I
did
not
test
it
and
we
should
test
it
obviously
with
like.
I
think
we
can
test
it
now.
Try
and
export
a
project
that
does
have
a
project
namespace
and
then
try
to
import
it
back
and
see
what
happens.
I
think
it
should
work
as
is,
and
it
will
work,
as
is
what
it
will
do.
B
Is
it
will
not
export
the
project
namespace
and
when
we
import
it
will
basically
create
a
new
project
namespace
right,
okay,
so
it
should
work
for
the
meantime
as
like
when
we
start
moving
away
from
from
using
projects
we'll
need
to
to
fix
this.
So
this
will
be
some
something
like
to
follow
up
as
basically
as
soon
as
possible,
right.
A
B
B
That
is
kind
of
very
important
after
phase
two,
this
kind
of
approach
that
was
that
was
what
I
was
thinking
of-
how
we
can
move
this
stuff
out
of
phase
two
into
phase
three
without
like
yeah
having
to
keep
face
to
open
indefinitely,
because
there
will
be
a
lot
of
these
small
things
that
need
to
be
done
and
so
on
and
so
forth.
But
that's
not
a
reason.
I
guess
to
not
close
the
phase.
Two.
Basically.
B
A
But
we
are
working
on
the
routing
we're
working
membership,
so
I
think
this-
this
won't
be
a
big
thing
that.
B
A
Can
like
save
it
for
manage
because,
like
he
will
be
helping
us
now
and
working
with
you
around
you
on
this,
and
I
don't
know
if
he
has
any
experience
with
important
sport,
but
I
wouldn't
be
surprised
if
he,
if
he
has
something
so
like,
I
think
he
he
will
finally
have,
and
you
know
we
have
contacts
in
manage.
You
know,
although,
like
import
team,
is
pretty
it's
very
small
right
now,
but
yeah
well,
I
think
we
can
lift
us
to
manage.
I
will
I
will.
I
just
do
for
myself.
B
Yeah,
the
important
thing
right
now
is
just
to
test
it
out
like
export,
a
project
that
does
have
a
project
namespace
and
then
try
to
import
it
and
and
see
what
happens
if
it
works.
Then
it's
not
a
huge
problem
like
it's
something
that
we
need
to
address,
but
it's
not
a
blocker
to
kind
of
keep
it
in
phase
two
and
not
let
people
start
working
on
stuff
and
things
like,
because
if
we
get
then
we
need
to
fix
it
as
soon
as
possible,
but
I
think
I
think
it
should
work.
A
Yeah,
but
at
the
same
time,
yeah
at
the
same
time
when
we
will
be
working
on
membership,
consolidation
will
also
need
to
like
update
membership
creation
to
like
at
the
same
thing
as
we
were
like
right
now,
when
you're
creating
projects
you're
also
creating
project
namespace.
So
from
when
we
migrate
all
the
projects,
we
can
make
sure
that
what
once
we
creating
members,
we
are
also
creating
like
they're,
also
as
like
attached
to
the
project
namespace.
B
A
Okay:
okay,
okay,
okay,
you
were
talking
about
point
two.
B
Yeah
on
the
point
two
with
like,
because
this
takes
such
a
long
time,
I
would
assume
that
it
may
take
a
long
time
on
on
on
premises
as
well
and
we
don't
have
like
any
visibility
on
either
the
migration
finished
or
not.
B
So
how
do
we
kind
of
automate
the
firing
of
next
backfilling
migration,
so
backfilling
of
the
members
or
routes
is
dependent
on
this
one
finish
so
now
we
need
a
way
to
kind
of
know
if
we
can
fire
those
migrations
or
not-
and
I
I've
posted
this
question
in
slack
and
try
to
get
some
opinions
there.
I
I
I
can
see
two
approaches,
one
to
just
like
hardly
block
the
the
migrations,
but
I
think
that
can
break
the
the
upgrade
process.
B
I'm
not
100
sure
and
the
other
one
is
like
not
to
hard
block
it,
but
done
there
is
no
easy
way
to
let
to
let
admins
or
whoever
is
managing
yourself
manage
the
instance
know
that
backfilling
failed
or
it's
still
in
progress
where
there
were
some
migrations
that
kind
of
ran,
but
they
still
need
to
run
in
background,
but
I'm
not
running
because
something
happened
there.
So
yeah
I
don't.
I
don't
know
how,
like.
B
Something
that
I
don't
think
we
caught
up
before
so
it
kind
of
popped
up
recently
when
I
started
thinking
about
how
do
I
follow
up
with
the
backfilling
of
routes
but
yeah?
That's
that's
something
that
I'm
looking
into
next.
A
B
B
A
Okay,
I
understand
that
we
need
to
solve
this
before
we
push
forward
with
the
backfilling
for
numbers
and
routes.
B
B
B
A
Okay,
okay,
do
we
have
more
points
to
talk
about?
I
think
we're
done
and
you
have
one
minute
so
I
think
we're
just
in
time.