►
From YouTube: Workspace meeting 2021-12-22
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
C
Not
too
much
of
data.
Well,
I
guess
the
update
is
it's
still
in
review
and
I
guess
it
is
going
to
still
now
for
the
holidays,
because
the
someone
who
is
reviewing
it
is
on
holidays,
I'm
not
sure
if
I'll
be
moving
it
to
someone
else.
I
do
have
to
do
some
changes
based
on
his
suggestions.
There.
C
Because
we're
kind
of
getting
some
big
batches
we're
so
basically
for
the
this
is
the
migration
for
gitlab
work
only
group
and
because
we're
using
the
batched
migration.
The
best
migration
is
basically
just
scanning
the
entire
table
in
six
sized
batches
and
what
what
happens
is
that?
Because
for
pretty
much
the
entire
table,
there
is
nothing
to
do
the
batches
grow
very,
very
big.
C
That's
probably
not
going
to
happen
on
production,
but
it
still
needs
to
be
way
lower
than
that,
like
I
don't
know
like
around
the
second,
maybe
is
something
acceptable,
so
the
suggestion
is
that
you
to
try
and
see
if
we
can
add
a
different
strategy
to
scan
this
table,
these
the
name
spaces
were
do
something
different
there.
C
So
yeah!
That's
what
this
is
not
going
to
happen,
though,
for
the
entire
table
migration,
because
we
will
just
like
there
is
no
go.
There's
not
going
to
be
these
bigger
gaps,
because
you'll
have
to
update
basically
for
every
batch
you'll
have
to
update
pretty
much
the
same
number
of
records
and
create
records.
So
it
will
do
a
lot
more
work,
so
it
like,
within
these
two
minutes
or
three
minutes
or
how
much
the
delay
we're
setting
it'll
actually
do
the
actual
work.
C
So
it'll
I've
been
running
it
like
locally
for
the
entire
namespaces
table
and
for
me
it
was
around
two
thousand
ladies
basically
batches
two
up
to
three
thousand
or
something
along
those
lines,
but
yeah
for
a
single
namespace.
Obviously
it
just
has
nothing
to
do
it.
It
gets
like
a
range
of
two
million
and
there
is
no
project
to
be
migrated
in
that
range.
So
it.
C
So
there
is
no
easy
way
to
do
it
in
bench:
migrations.
The
easy
way
is
it:
it
is
to
do
in
the
old
style
background
migrations,
but
we
don't
have
as
much
control
over
those
right.
So
there
is
like
you
just
queue,
a
bunch
of
psychic
jobs,
and
then
you
kind
of
have
to
grab
them
in
the
logs
or
see.
What's
happened,
did
they
finish
and
and
so
on
and
so
forth.
So
in
order
to
use
the
best
migrations
strategy
or
what?
What
not
that
we
kind
of
need
to
do.
C
Why
don't
we
either
need
to
like
refactor
the
batch
migrations
for
you
to
take
a
scope
in
one
way
or
another,
or
there
is
a
notion
of
batching
strategy
and
we
need
to
develop
that
part
where
we're
like
it's
a
class.
That
kind
of
has
how
big
the
batches
should
be,
where
what
are
what
is
actually
the
minimum
and
the
maximum
ids.
C
So
yeah
I'll
start
looking
into
that
today,
but
yeah
it
seemed
like
recently.
I've
got
a
lot
of
reviews
to
do
so.
I've
not
been
able
to
get
to
that,
but
yeah.
I
I've
been
looking
into
that.
Like
prior
to
to
joining
the
call,
so
yeah
we'll
see
how
that
goes
and
yeah,
either
being
back
simon
after
holidays
or
or
try
to
pass
it
to
someone
else
but
yeah,
that's
the
status.
C
C
So
basically,
this
is
a
sort
of
a
question
for
the
self-managed,
but
in
that
scenario
the
feature
flat
being
on
will
land
before
we
actually
run
the
the
migration
and
then
we
should
be
okay,
because
if
if
during
the
migration
a
project
is
being
created,
we
will
get
the
corresponding
project
namespace.
For
for
that,
so
yeah.
B
Okay
seems
reasonable
if
there's
any,
I
know
who's
from
database
team
is
working
for
the
holidays,
but
if
it's
a
big
I
don't
know
if
you're
working
you're,
probably
off
next
week
as.
B
Will
look
for
data
based
in
someone
is
available
during
this
time,
so
maybe
we
can
like
actually
push
it
forward
during
the
holidays.
I'm
also
here
at
least
two
days
next
week,
so
I
can
try
to
do
that.
C
Yeah
I
can,
I
can
bring
you
or
ping
someone
on
the
database
once
I've
got
something
solved
out
from
from
for
the
batching
just
basically
yeah
okay
sounds
good.
C
Yeah,
I
think
gallery
has
topic.
D
Yeah
I
did
have,
I
guess,
just
a
question
to
start
out.
Does
the
workspace
group
currently
take
place
in
quad
planning.
B
We
like,
because
we
are
like,
as
I
said
to
you
before
as
we
are
trying,
these
changes
should
be
invisible.
They
like
they
should
not.
They
should
not
make
any
changes
visible
to
a
user
right
now.
So,
for
example,
this
enabling
feature
flag
that
alexandria
mentioned
this
should
not
be
visible
to
a
user
user
should
not
be
aware
that
we
are
doing
something
in
in
the.
C
If
everything
should
just
be
the
same,
it
should
not
change
for
the
user
in
any
way,
and
there
will
be
just
some
changes
in
phase
two
where
I
think
we'll
deal
with
we'll
be
dealing
with
some
of
the
permissions
and
memberships
and
that's
where
some
of
these
changes
may
like
we
will
we
should.
We
should
strive
to
do
it
as
transparent
to
the
easier
as
possible,
like
not
bring
any
changes,
but
I
don't
think
that
will
be
possible
for
the
entirety
of
of
the
of
the
change.
C
I
think
yeah,
I
don't
know
about
that
like
there
is
one
thing
I
think
that
is
going
to
be
touched
for
sure
is
where
there
was
a
thing
where,
like
the
user,
that
is
member
of
a
project
gets
to
read
access
in
the
parent
groups,
but
not
if
a
user
is
a
member
in
a
subgroup,
they
don't
get
the
same,
read
permissions
in
the
parent
group.
C
So
so
it's
like
this
kind
of
a
weird
behavior
which
I
think
is
going
to
it
just
has
to
change
just
because
now
the
memberships
will
be
in
the
project
name,
space,
which
is
basically
a
grouping
and
namespace.
So
I
don't
know
how
big
that
of
a
change
that
is
for
the
customers,
but
it
kind
of
touches
on
the
security
and
the
ux
and
all
that
behavior
stuff.
B
C
That's
great:
that's
why
you
can
introduce
you
can
introduce
the
the
breaking
change
for
some
of
the
customers
that
do
not
have
this
behavior
right
they're,
not
assuming
that
that's
how
how
it
is
working
right
now.
So
then,
like
all
of
a
sudden,
they
will
see
some
users
that
do.
D
C
Permissions
in
the
like
read
permissions
in
parent
groups,
then
that's
not
I
I
mean
at
least
we
should
be
forthcoming
and
prevent
like
letting
them
know
that
this
is
going
to
be
the
change
it's
going
to
make
it
like
behave
the
same
and
all
that
stuff,
but
it
is
a
change
that
is
going
to
be
introduced.
I
think.
D
Yeah
and-
and
I
understand
yeah
there's
like
some
changes
right
now
that
are
mainly
supposed
to
be
not
visible
to
the
end
user.
I
guess
where
I
was
kind
of
just
wondering
about
was
if
it
would
be
beneficial
at
this
time
to
consider
like
availability
and
testing
kind
of
in
that,
basically,
with
like
cloud
planning
with
what
other
groups
are
doing
at
this
time.
D
Is
they
that
their
counterpart
sdt
will
put
this
section
in
with
issues
in
the
description
that
are
ready
for
development
to
think
about
testing
at
all
the
different
levels,
so
not
necessarily
just
on
testing
and
trying
to,
like
think
of
questions,
collaborate
and
trying
to
identify
gaps
to
where
test
coverage
might
be
needed.
So
I
was
just
curious
if
we
think
that
could
be
beneficial
at
this
time
or
if
it
would
be
better
more
maybe
for
later
faces.
C
Yeah,
I
don't
see
a
reason
why
not
to
have
that
collaboration?
I
think
we
are
doing
a
good
part
of
the
testing
anyway,
at
the
at
least
as
back-end
development
and
all
that
stuff,
not
as
much
definitely
not
as
much
for
end-to-end
testing.
I
don't
think
we
touch
too
much
on
the
outside
as
as
engineers,
but
yeah
definitely
should
be
raising
the
question
of
quality
and
how
we
can
insure
one
or
or
or
other
aspects
of
that.
A
A
B
No,
no,
I
I
love
families
valerie's
input
on
any
issue
when
she
sees
like
he
needs
a
little
bit
of
more
testing
from
that
I'm.
I'm
would
be
very
happy
to
see
that.
D
Cool
yeah,
I
know,
and
one
way
that
quad
planning
kind
of
helps
bring
visibilities
for
the
scts
too.
So
we
have
an
automatic
report,
that's
generated
based
on
labels
that
are
affixed
to
the
issues,
so
I
believe
either
engineering
manager,
product
manager
assigns
those
labels
onto
the
issues
that
are
like
being
worked
on
for
that
milestone,
and
that
way
the
report
can
pick
it
up
and
I
can
see
which
ones
I
can
come
into
and
start
putting
that
feedback
on
but
yeah,
but
that
that
is
something
like.
D
D
A
Also,
you're
also
willing
invited
to
go
in
and
follow
the
epics
and
the
issues
and
the
and
the
mr's
being
created
and
jump
in
proactively.
On
that.
A
If,
if
we'll
get
all
the
labels
in
there
right
now
or
not,
but
but
please
feel
free
to
to
follow
along
and
join
the
if
you're,
not
already
in
the
in
the
the
group
in
slack
and
all
that
stuff
to
be
as
proactive
as
we
need
to
be
so.
C
Yeah
like
for
this
specific
project,
it's
fairly
easy
to
follow.
I
would
say,
because
everything
has
been
within
this
epic,
that
I've
linked
in
the
in
the
doc
so
like.
I
think
we
can
really
easily
apply
all
of
the
labels
if
you
need
that
for
your
process,
just
because,
like
everything
is
basically
encapsulated
within
one
of
these
epics
or
sub-epics,
and
for
the
migration
that
we
were
talking,
it's
all
it's
all
in
phase
one
epic
and
then
the
next
one
is
broken
down
to
phase
two
and
phase
three,
so
yeah.
C
We
try
and
keep
it
organized
in
in
that
way,
so
probably
an
easy
way
is
to
go
and
just
apply
the
labels
to
whatever
I
don't
know.
If
you
want,
I,
like
I'm,
not
acquainted
with
the
process
that
you
like
the
testing
team
is
following.
Do
you
need
the
labels
only
for
this
specific
release.
C
Okay,
to
apply
the
labels
for
the
entire
epic
suit
that
will
be
like
maybe
six
or
seven
or
12
releases
long.
I
don't
know
how
how
long
that
will
be.
So
maybe
you
don't
want
that
many
issues
to
be
tracked
right,
so
yeah
you
can.
You
can
feel
free
to
to
apply
the
labels
to
just
the
one
that
has
the
respective
milestone.
C
I
like
again,
I'm
not
I'm
not
sure
what
the
process
is
there,
but
we
can
definitely
help
if
you
have
any
questions
or
give
you
like
the
all
the
facilities
to
to
enable
yourself
to
to
do
the
job.
D
Yeah
yeah,
that's
a
great
question
and
from
what
I
was
seeing,
because
I'm
I'm
learning
about
it
as
I
go
as
well
from
what
I've
been
seeing
in
the
handbook
looks
like
if
it
has
the
workflow
ready
for
development
and
the
the
group
workspace
label
attached
to
it
and
an
upcoming
release
milestone,
then
it
should
be
picked
up
by
that
automatic
report.
D
So
I
think
it's
just
those
labels
from
what
I
can
see
here,
but
otherwise,
but
like
even
before
that's
implemented
yeah.
I
I
can
definitely
jump
in
and
start
contributing
before
him
too.
A
I
I
think
I
would
also
look
at
the
end
development
issues
as
well.
It's
not
everything
gets
marked
with
a
ready
for
development
so
because
we
just
we're
pretty
proactive
as
well
and
just
pick
up
and
move
forward
with
stuff.
So.
B
Yeah
and
in
the
same
time
like
we
work
right
now
like
what
alexander
was
telling
us
about
before
is
phase
one,
but
still
some
some
issues
from
phase
two
were
picked
up
because
we
could
work
on
them
in
parallel.
B
So,
even
though
the
phase
one
is
still
very
much
in
progress,
some
of
the
phase
two
issues
were
already
started
to
work
on,
because
we
have
a.
We
have
a
plan
for
phase
one,
so
we
know
how
it's
supposed
to
work.
So
some
some
some
members
of
the
team
started
to
work
on
the
face.
These
two
issues
already.
D
Gotcha,
okay,
great
yeah,
it
makes
sense
yeah
just
kind
of
wanted
to
to
call
that
as
a
discussion
to
see
if
that
might
be
something
helpful
to
start
on.
So
thank
you.
B
Okay,
if
there's
this
is
the
end
of
our
agenda.
I
would
just
like
to
wish
you
all
great
holidays,
some
time
off,
good
food,
if
you're
celebrating
my
way
and
just
happy
happy
happy
holidays
for
for
all
of
you
and
because
I
know
that
some
of
us
won't
be
here
next
week.
I
think
it
would
be
good
to
cancel
meeting
next
time
because
I
don't
believe
there'll
be
much
change
in
this
week
with
all
of
the
time
off
going
on.
So
I
will
see
each
other
in
january.