►
From YouTube: GitLab 13.2 Kickoff - Create:Ecosystem
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
First
I
wanted
to
touch
on
mass
integration,
so
we've
been
working
on
this
for
months
now.
It's
been
a
huge
lift,
a
massive
shout
out
and
thank
you
to
everyone.
Who's
participated,
both
our
team
and
people
throughout
get
lab,
and
people
in
the
community
have
contributed
to
this.
It's
been
awesome,
so
we've
got
a
massive
amount
of
work,
we're
hitting
our
first
milestone,
which
is
instance,
level
integration.
A
So
that's
shipping
in
13.1
and
before
we
move
on
to
group
level,
integration,
we're
gonna
start
off
a
new
MVC
which
will
pivot
to
briefly
and
then
we'll
come
back
to
to
group
level
integration.
So
let's
talk
about
that
so
much
like
mass
integration.
This
is
driven
by
JIRA,
so
expanding
to
your
integration
to
allow
the
viewing
of
issues
is
all
about
the
developer
we
hear
commonly
from
customers
at
large
enterprises.
They
want
to
see
a
two-way
data
sink.
A
What
they
say
is
that
their
developers
don't
want
to
leave
gitlab
where
they're
spending
their
time
the
most.
This
is
a
common
concept
in
development.
We'll
talk
about
flow,
so
if
you're
in
flow
you're,
writing
code
you're
doing
work,
you
don't
want
to
leave
and
go
to
a
completely
different
type
of
system
because
it
can
break
flow.
So
by
keeping
people
in
get
lab,
we
can
increase
productivity
and
make
their
day
better.
So
to
that
end,
we're
gonna
add
as
an
MVC.
So
this
is
a
minimal,
viable
change.
A
We're
gonna
add
a
list
of
issues
in
our
current.
Your
integration
you'll
see
on
the
sidebar
a
link
to
that
JIRA
server
instance.
Well,
we'll
add
a
new
issue
list
to
that,
where
we'll
load
a
list
of
issues
from
a
given
project.
Now
this
will
be
configurable,
so
you
can
turn
it
on
or
off
we're
gonna
be
using
those
credentials
which
may
be
admin
credentials
after
all,
so
we
can
turn
it
off
if
it's
security
concern,
but
we'll
add
this
list
of
issues
so
developers
can
quickly
navigate
to
the
right
issue.
A
Next
steps
so
we'd
like
for
people
to
be
able
to
federate
the
account,
because
once
you've
federated
your
account,
we
can
do
things
like
add
comments,
change
status
once
we
have
that
we
can
add
a
detail
view,
so
you
can
see
the
whole
thread
see
more
detail,
more
meta
information
about
that
issue
and
then,
possibly,
even
maybe
add
a
board
view
so
trying
to
give
you
all
of
the
tools
that
you
need
to
do
your
job
without
having
to
leave
gitlab
inside
of
tira.
So
that's
super
excited.
I'm
super
excited
about
that.
A
It's
super,
exciting
work,
I.
Think
it's
really
interesting.
I
think
a
lot
of
developers
will
find
this
to
be
a
huge
quality
of
life
improvement.
So
it's
gonna
be
an
awesome
little
experiment
to
play
with,
on
the
front
end
UX
foundation,
side,
here's
some
work,
we're
doing
in
the
pajamas
design
system,
two
things
that
I'd
really
like
to
call
out
one
we've
got
to
create,
build
and
style
items
happening,
that'll
be
coming
to
pajamas,
so
accordions
and
lists
are
both
in
process
and
we'll
be
working
on
those
getting
those
in
there
soon.
A
A
This
tells
us
how
we
should
be
prioritizing
what
things
we
should
be,
focusing
our
time
and
attention
on,
and
similarly
we're
also
going
to
be
running
a
GDK
survey
which
we'll
come
back
and
talk
to
you
in
a
second,
so
we're
continuing
work
on
GDK
checkout.
So
this
is,
as
a
quick
recap
will
allow
you
to
check
out
a
specific
branch.
This
is
hugely
important
for
product
managers,
designers,
anyone
who
is
not
actively
using
the
GDK
and
writing
code
for
get
lab
on
a
daily
basis.
A
We
want
to
make
a
really
easy
one-step
command
for
them
to
check
out
a
branch
and
view
it
specifically.
This
depends
on
GDK,
pristine
or
it
may
depend
on
GDK
pristine,
and
so
that's
also
in
process
and
the
idea
being
that
you
can
run
a
single
command
and
have
what
you
need
without
having
to
worry
about
updating
and
setting
everything
up
and
making
sure
everything's
in
a
usable,
State
we're
running
a
GDK
survey
where
we're
going
to
try
to
understand
more
about
our
users
and
then
we'll
post.