►
From YouTube: 2022-03-16 Workspace project 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
A
I
want
to
congratulate
on
the
first
successful
migration
for
members
table
and
alexandria.
Yes,
this
is,
I
know
this
is
half
of
the
migration,
but
this
was
a
big
one,
so
making
this
right
and
I
think
it
was
without
any
issues
and
we
cut
that
we
can
change
the
patch
number
the
right
moment.
So
I
think
it's
overall
success
so
congrats
everyone
involved.
I
know
it
was
a
team
effort
and
from
brett
and
from
charlie,
so
amazing
work.
A
Okay,
so
my
next
question
is
for
alexandria
about
that.
Do
we
know
the
status
of
the
migration
that
is
going
on
right
now
is
blocking
the
our
big
project
namespaces
one.
B
Yeah,
I
don't
know
the
exact
status.
The
latest
that
I
have
access
to
is
since
march
14th,
and
I
think
that's
before
the
there
is
an
incident
with
the
yeah.
We
need
to
we
needed
to
do
something
on
that
migration
now
and
I'm
not
sure
if
it
was
downsized
to
run
slower
or
not.
I
think
it
was
not
that
I'm
not
exactly
sure.
So,
even
if,
if
it
was
kept
as
it
was,
then
we
are
expecting
it
to
run
around
28
days.
B
Maybe
more
previous,
then
after
that
we'll
have
our
backfilling
migration.
I
think
that's
that
our
hours
is
next
in
line,
but
I'm
not
sure
about
that
either.
But
I
can
I
can
check.
We
do
expect
our
migration
to
run
around
six
days,
give
or
take,
but
yeah
well,
we'll
need
to
wait
for
the
for
the
30
days
period
ready
to
get
there.
So
that
should
not
be
a
blocker,
though
I
thought
initially
that
that
might
block
us
onto
merging
the
further
migrations.
B
But
I
think
we
can
do
some
tricks
within
the
migration
to
check
that
the
original
one,
the
one
on
the
back
filling,
has
finished
and
if
not
just
skip
it
yeah.
In
fact,
it
will
not
get
like
if
the
migration
is
running.
It
will
not
even
get
to
these
follow-up
backfilling
migrations
because
we
do
one
migration
at
the
time.
So
it's
done
sequentially,
but
if,
for
instance,
the
back
filling
did
finish
but
did
not
finish
with
success,
then
it
will
still
not
not
run
the
migration.
B
It
will
just
check
the
status
and
and
skip
it.
So
yeah
we'll
probably
need
to
raise
them
some
sort
of
a
vlogging
or
some
sort
of
a
notification
until
that
admins
know
or
whoever
is
there,
that
there
is
something
going
on,
and
this
migration
is
not
running
to
not
block
something
something
else.
But
I
I
think
there
are
some
ways
to
not
have
us
blocked
and
have
this
stuff
meshed
and
move
on
with
the
coding.
B
With
the
caveat
that
we
need
to
keep
in
mind,
we
need
to
treat
the
code
so
that
it
checks
for
the
fact
that
there
might
not
be
data.
Yet
in
the
database
right
just
just
do
your
coding,
but
make
sure
that
you
check
that
there's
still,
there
might
be
a
situation
where
the
project
name
space
is
not
there
yet
and
then
the
I.
B
I
think
the
plan
is
in
15
yeah
in
1500
to
have
a
gatekeeping
migration,
where
it
will
check
that
the
ones
that
are
required
did
actually
finish
and
then
after
15,
oh,
like
in
15
1
or
whenever
we
can
start
removing
the
code.
That
does
the
checks,
because
now
we're
kind
of
sure
that
we
have
the
data
in
place.
So
that's
that's
kind
of
the
steps
that
we
will
need
to
take.
B
I'm
not
exactly
sure
that
it'll
be
150
depends
on
how
we
actually
get
how
far
we
get
with
the
migration
on
on
our.com.
Actually,
so
because
of
this
see
like
big
ci
migration,
it
may
not
make
it
to
the
250
now
like.
Ideally
that
will
be
a
great
place
where
we
would
put
these
gatekeeping
migrations,
because
that's
sort
of
a
breaking
change.
B
It's
not
exactly,
but
it's
a
great
place
to
have
people
look
out
for
breaking
changes
and
have
more
visibility,
and
let
them
know
that
these
are
some
of
the
things
that
you
have
to
make
sure
are
finished
before
you
can
move
on
further
on.
So.
A
I
think
it's
also
for
some
migrations.
It's
like
you
need
to
migrate
everything
between
before
moving
to
the
major
version,
so
I
think
also.
B
Yeah
but
there's
documentation
only
as
well,
so
so
because,
like
it's,
I
my
understanding
is
usually
it's
better
to
do
it
on
major
releases,
because
people
usually
pay
attention
on
major
releases.
More
than
on
my
minor
releases
right
when
you
do
a
major
release,
you
kind
of
expect
some
of
the
breaking
changes
to
happen.
So
that's
why
it
will
be
an
ideal
place
to
do
this,
but
we'll
see
if
that
will
happen,.
A
Okay-
and
I
understand
that
you're
right
right
now-
working
on
routes,
migration,
so
like
the
similar
way
that
we
are,
we
were
dealing
with
members,
so
first
for
groups
and
and
then
for
and
then
once
we
get
the
let's
call
it
main
migration
done.
We
can
move
on
with
routes
as
well
right.
B
Yeah
yeah
the
the
namespaces
one
was
ran
already
as
far
as
I
know
so,
yeah
the
next
one
is
to
be
run
for
the
for
the
project
main
spaces.
So
that's
the
one
I'm
working
on
the
one
for
the
project,
namespaces,
actually
so
yeah.
A
Okay,
so
one
announcement
from
me
we've
already
a
we
clean
up
the
face
to
epic.
We
moved
everything
but
membership
issues,
rouse
issues
and
one
issue
about
imports
to
the
other
epic.
So
we
can
like
focus
like
scope
space
to
into
those
free
subjects,
and
the
other
things
that
we
are
we
need
to
work
on
will
be
in,
like
other
phases
will
be
like
clearer
what
we
should
focus
on
and
make
and
we'll
just
make,
I
think,
easier
for
everyone
to
understand.
What's
what's
going
on
now,.
C
Yeah
yeah
last
last
point
just
a
quick
announcement.
I
I
am
leaving
git
lab
my
last
day
is
going
to
be
on
the
8th
of
april
so
blair.
My
manager
is
here
as
well
to
sort
of
help
with
the
the
transition
and
find
some
new
people
as
well,
but
yeah.
It
was
nice
to
sure
work
with
work
with
you
all
and
yeah.
There's
still
a
still
a
few
more
weeks
before
I
leave
so
I'm
sure
it'll
be
time
to
transition
and
then
say
goodbyes.
A
D
The
yes
absolutely
yep,
we
are
going
to
I'm
working
with
my
leadership
already
we're
going
to
work
very
quickly
on
trying
to
fill
this
role.
We
know
that
workspace
is
so
critical
and
and
touches
so
much
of
the
product
that
we're
really
hoping
to
have
as
little
sort
of
gap
as
possible,
so
yeah
I'm
already
working
on
it
very
quickly.
Thank
you.
D
Thanks
to
nick
for
her
being
such
a
strong
support
in
ux
and
and
supporting
you
guys
and
I'm
not
gonna,
I'm
not
gonna.
Leave
you
guys
hanging
at
all.