►
From YouTube: GitLab 13.2 - Manage Joint Kickoff
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
Well,
hello
and
welcome
to
the
manage
stage:
joint
kickoff,
recording,
you're
gonna,
see
access
import
and
optimize
plans
for
13
12.,
so
without
further
delay
melissa.
Why
don't
you
tell
us
what
access
is
working
on.
B
B
Specifically,
the
linear
queries
work
that
we've
been
working
on,
continuing
that
and
hopefully
enabling
it
for
all
of
gitlab.com
and
again
that's
to
reduce
complexity
of
the
way
namespaces
are
looked
up
where,
instead
of
being
recursive,
queries,
we're
re-architecting
them
to
be
linear,
queries,
so
less
expensive,
less
complicated,
so
that
work
is
continuing
along
with
a
couple
of
other
work
streams,
but
we
are
working
on
one
feature
which
is
for
new
saml
setups
when
samwell
is
set
up
for
gitlab.com
groups
by
default,
enabling
and
also
presenting
a
warning
that
disabling
sample
enforcement
could
be
a
security
risk.
B
So
moving
forward,
we're
going
to
enable
it,
like,
I
said,
enforce
it
whenever
it's
enabled
and
keep
an
eye
on
metrics
to
see
if
people
switch
it
back
or
if
now
we
see
more
people
enforcing
it,
because
we
believe
that's
the
intended
behavior.
If
you're
going
through
the
whole
process
to
set
up
saml
and
that's
it
for
access.
B
A
Obvious
is
it
for
for
users
to
see
that
it
is
now
enabled
by
default
and
also
how
to
disable
it.
B
So
let
me
show
my
screen
again
in
this
issue.
You
can
see.
This
is
what
it
looks
like
and
I'll
show
you
in
one
of
my
test
groups
in
case
you
want
to
see,
but
it's
within
settings
sample
sso,
there's
different
toggles.
B
This
is
to
enable
it
basically
to
allow
you
to
sign
in
through
saml,
and
this
is
so
that
you
can
only
sign
in
through
saml,
so
it's
two
different
check
boxes,
but
it's
fairly
set
it
and
forget
it.
So
I
don't
think
people
are
going
back
here
every
day
and
by
default.
This
is
off
today
and
I
don't
believe
it's
very
clear
right
now.
What
the
difference
is
between
enabling
and
enforcing
it,
which
is
what
we're
trying
to
do.
Also
just
clean
up
the
language.
A
Well,
you're,
getting
something
in
addition
to
just
perfection
right.
B
A
So
I
can
go
next
and
I
will
share
my
screen
to
elaborate
follow
along.
A
A
We
worked
on
some
of
the
bugs
performance
and
technical
depth
issues
in
the
previous
milestone,
instead
of
continuing
on
the
feature,
because
that
was
something
that
was
important
and
we
also
had
a
spike
that
we
had
to
do
in
order
to
unblock
these
last
three,
the
performance
of
so
the
the
framework
that
we've
set
up
was
not
as
performant
as
we
wanted
to
be,
and
we
didn't
want
to
leave
the
tech
field
behind.
A
So
we
kind
of
took
time
to
go
back,
find
a
better
way
better
path
forward
and
hopefully,
we'll
be
able
in
1312
to
make
some
progress
against
these
last
couple
of
pieces
that
are
required
for
epics
to
be
able
to
be
migrated.
A
A
So
we
wanted
to
allow
people
to
use
object,
storage
or
external
storage
and
just
kind
of
point
the
import
in
that
direction
and
then
can
allow
the
back-end
processes
to
pull
the
file
across
to
be
imported
from
an
import
storage.
This
is
something
that
you
know.
Typically,
when
there's
an
issue
with
a
larger
file.
You
know
support
and
for
the
people
get
involved,
and
it's
a
drain
on
resources
to
to
do
that.
So
this
will
help
with
the
bandwidth
of
the
group.
A
That's
a
good
point:
it's
been
a
while,
since
I've
sort
of
shared
the
larger
picture
there.
So
really
the
larger
picture
is
this.
You
know
parent
epic,
to
the
epic
migration,
which
is
a
group
migration.
So
what
we're
doing
is
we're
migrating
the
entire
group
epics
being
kind
of
the
most
complex
thing
that
we
had
to
migrate
within
the
group,
but
in
addition
to
that,
we,
you
know
we
need
to
migrate
milestones,
iterations
labels,
boards,
badges
all
kinds
of
things.
A
So,
if
you
look
at
this
list
here,
these
are
all
the
things
that
we
need
to
move.
Some
of
these
have
been
closed,
like
the
milestones
and
the
labels
and
the
badges
are
already
being
migrated.
A
We're
currently
doing
kind
of
still
working
on
the
epic,
epic,
but
past
that
we
have
a
few
things
to
wrap
up,
one
of
them
being
boards,
because
it's
also
one
of
those
complex
kind
of
multi-level
objects
that
we
will
use
the
new
new
software
solutions,
new
engineering
solution
to
migrate
and
to
kind
of
wrap
it
all
up.
We
will
provide
an
api
for
our
customers
to
be
able
to
automate
this
process
once
that's
completed.
A
We
will
have
achieved
the
parity
with
the
currently
existing,
like
old,
a
group
export
import,
which
means
that
we
will
be
able
to
sunset.
The
group
export
import,
as
the
group
migration
will
now
have
everything
that
the
old
feature
did.
So
that's
the
next
steps
will
be
really
just
wrapping
that
up
and
being
able
to
finalize
the
completion
of
the
group
migration
once
that's
completed.
A
There
is
a
there's,
an
even
bigger
strategy
here,
so
once
we
have
the
parity
with
the
group
export
import,
we
will
move
on
to
adding
users
to
groups
which
is
something
that
we
never
had.
So
it's
not
part
of
the
parity
with
the
old.
It's
actually
new
and
exciting
migrating
users
from
one
instance
to
another
that
belong
to
a
group
is.
It
was
something
that
we
didn't
do
before.
What
we
did
was.
We
would
require
you
to
have
all
the
same
users
in
the
destination,
and
then
we
would
kind
of
match
between
the
users.
A
So
we
would
match
the
owners
of
an
epic
if
the
user
had
the
same
user
with
the
same
email
in
the
source
and
destination
would
become
the
owner
of
an
epic
beam
migrator,
for
example,
but
we
wouldn't
really
migrate
the
users
here
we're
going
to
look
to
actually
move
the
users
across
the
new
instance
and
then
proceed
with
projects.
That's
going
to
be.
The
final
big
chunk
is
just
getting
the
projects
also
to
migrate.
A
B
Clean
up
all
my
stuff,
but
I
think
user's
migration
is
awesome,
because
now
you
can
start
directly
attributing
seats
to
import,
which
is
going
to
be
a
huge
thing
for
them.
A
Yeah,
it
could
be.
Definitely
it
would
be.
A
performance
indicator
for
us
is
to
sort
of
count
how
many
people
we
have
imported,
not
just
how
many
imports
we've
kicked
off,
but
you
know
we
could
kick
off
one
import
that
has
10
000
seats
versus
10
imported
at
10
seats
each
and
it's
not
the
same
thing
so
be
able
to
measure
how
many
users
we're
importing
could
be
a
new
performance
indicator
for
our
group.
A
Cool
so
since
there's
no
more
questions,
thank
you
for
listening
and
I
will
now
let
larissa
tell
us
about
what
optimizes
planning
in
1312.
C
Thank
you
harris,
so
I'm
going
to
go
over
what
we're
working
on
for
our
two
main
categories
that
we're
focused
on
these
days,
which
are
devops
adoption
and
value
stream
analytics
for
devops
adoption.
We
got
the
adoption
table
into
the
group
in
1311,
which
is
really
exciting,
but
prior
to
that
it
was
a
just
an
instance
level
feature.
So
now
you
can
go
to
any
group
and
add
the
subgroups
in
that
group
and
see
which
features
have
been
adopted.
C
This
is
really
exciting.
Value
stream
analytics
is
starting
to
really
take
shape
and
get
a
lot
of
enhancements,
and
it's
looking
quite
different
to
how
it
did
a
few
months
ago
we
have
finished
the
back
end
work
to
be
able
to
sort
the
issues
that
you
see
within
a
stage.
C
And
then
we've
been
working
on
so
the
project
level
value
stream
analytics,
looks
like
this.
It's
quite
different
to
how
the
group
ui
is
looking
and
we've
been
doing
some
work
to
align
project
the
project
ui
with
the
group
ui.
The
next
things
we'll
be
doing
for
this
are
changing
to
the
horizontal
navigation.
So
this
vertical
navigation
here
will
go
away
and
we'll
put
we'll
be
adding
this
horizontal
navigation
at
the
project
level
and
we
recently
added
an
overview
view
that
just
gives
you
some
charts.
C
Instead
of
listing
out
issues
and
mrs
and
we're
going
to
be
adding
that
overview
into
the
project
level
as
well
and
then
the
next
thing
is
we've
been:
we've
had
quite
a
few
requests
for
being
able
to
see
how
many
issues
or
mrs
we
use
to
calculate
the
stage
time,
pagination
and
and
expanding
the
number
of
issues
that
you'll
see
in
this
view
will
help
with
that.
But
it's
still
not
all
that
intuitive.
C
And
then,
finally,
we
will
start
work.
This
will
probably
take
a
number
of
milestones,
but
we
will
start
work
on
a
work
in
progress
view
today.
When
you
look
at
a
stage,
it
is
only
listing
out
the
issues
that
have
reached
the
end
event,
not
any
issues
that
are
still
in
progress
in
that
stage
and
so
we're
going
to
add
a
work
in
progress
view,
which
is
a
view
that
you
would
look
at
if
you
want
to
take
action,
so
items
that
are
still
pending
in
this
stage.
C
A
Yeah,
so
for
the
devops
adoption
view,
how
did
you
pick
which
features
to
show
it
feels
like
you
know
you
were
trying
to
kind
of
represent
the
different
stages
or
so
will
there
be
just
like
representative
features
for
each
one
of
the
areas
or
will
you
just
have
all
the
features
there?
At
some
point,
we.
C
Won't
do
all
the
features,
because
there
are
so
many
of
them.
The
way
that
we
did.
This
was
a
combination
of
things
we
went
around
to
each
product
manager
and
asked
for
their
input
on
what
they
thought
were.
The
key
features
for
their
stage
that
showed
devops
maturity
and
were
indicators
of
how
successful
a
customer
might
be
in
that
stage,
and
we
also
got
feedback
from
customers
on
what
they'd
like
to
see
in
the
table,
and
then
I
put
together
a
spreadsheet
and
based
on
the
number
of
requests
for
each
feature.
A
A
Oh
cool,
so
my
other
comment
was
about.
I'm
really
excited
about
this.
To
see
any
kind
of
you
know,
sort
pagination,
rich
interactions.
A
So
when
you
mention
the
sword
and
the
imagination
of
value
stream
analytics,
I'm
really
excited
about
that
and
I'm
wondering
if
it's
being
done
in
a
way
that
kind
of
ends
up
being
a
part
of
a
component
in
kind
of
the
ui
toolkit
and
therefore
be
able
to
be
reused
easily
or
maybe
become
something
that
just
comes
for
free
next
time.
Somebody
builds
a
table.
C
That's
a
great
question
that
I
don't
know
the
answer
to
I'd,
have
to
look
in
the
issue
and
see
how
they're
going
about
implementing
it.
A
Okay,
cool
yeah,
that's
something
that
I
always
kind
of
look
for
and
look
into,
and
when
we
build
things
I'm
like
well,
you
know.
Maybe
other
people
want
to
be
able
to
use
this
yeah.
C
A
Well,
let's
stay
in
touch
all
of
us
to
just
make
sure
that
we
don't
like
you
know,
duplicate
and
triplicate.
Yeah.
C
A
B
C
Yeah,
that's
a
huge
focus
for
where
we
want
to
take
value
stream
analytics
because
it
is
like
you
say,
one
thing
to
look
retrospectively
and
and
see
that
you've
made
adjustments
over
time
to
remove
bottlenecks
and
look
at
historic
data,
but
then
to
actually
take
real-time
action
is
a
huge
value.
I
think.
A
Cool,
thank
you
all
yeah.
Thank
you.
If
there's
no
additional
questions,
I
think
this
may
be
it
for
the
manage
stage
for
1312.,
thanks
for
thanks
for
participating
thanks
to
everybody,
who's
watching
this
take
care.