►
From YouTube: GitLab 13.1 Kickoff 13.1 - 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
Hi
I'm
Patrick
Dooley
on
the
senior
product
manager
for
get
labs
ecosystem
group,
and
this
is
our
thirteen
point.
One
kickoff
we're
gonna
talk
a
little
bit
about
the
work
that
we'll
be
doing
over
the
next
month,
including
some
documentation
updates
some
new
components
that
we're
adding
to
pajamas
and
some
work
that
we're
doing
on
mass
integrations.
So
first,
we've
been
working
with
ServiceNow
over
the
last
few
months,
developing
an
integration
between
our
product
and
their
DevOps
plugin.
A
So
the
integration
is
specifically
for
change
management,
which
is
when
you
want
to
set
up
a
process
or
workflow
that
allows
changes
to
be
approved
or
requires
changes
to
be
approved
before
they
can
be
get
deployed
to
production.
This
integration
is
primarily
done
on
the
ServiceNow
side
on
the
get
lab
side.
A
We're
really
excited
to
have
this
integration
added.
It's
been
a
big
request
for
quite
a
while,
and
so
it's
been
great
working
with
them
to
get
this
up
on
the
mass
integration
front,
we've
got
a
couple
of
changes
that
we'll
be
doing,
and
so
specifically,
this
is
a
back-end
change.
We're
adding
a
new
field
on
the
database
side
for
projects
that'll.
Our
project
integrations
sorry
that
allow
them
to
inherit
from
an
ID,
and
you
can
pass
it
an
instance
ID.
So
it
inherits
that
integration
from
the
instance
level.
A
If
it
is
set
to
nil,
then
it
will
not
inherit
from
anything
and
so
it'll
use
its
own
settings.
This
is
a
back-end
change
specifically,
so
this
doesn't
affect
anything
on
the
front-end,
except
there
will
be
some
front-end
code
that
has
to
get
reworked
to
make
sure
that
it's
respecting
these
settings.
A
Additionally,
we've
got
a
page
that
we're
adding
or
a
view
that
we're
adding
that'll
show
that
the
project
overrides.
So
it's
easier
to
show
you
than
talk
about
it.
So
this
is
our
figma
mock-up.
If
you're
interested
you
can
find
this
on
that
issue.
So
this
is
on
the
admin
side.
So
in
the
admin
area,
we're
soon
to
add
an
integrations
set
integrations
page,
so
you
can
see
all
of
the
instance
level
integrations.
A
So
if
we
scroll
down
here
to
JIRA
who's,
our
constant
companion
for
demos
JIRA,
so
this
is
again,
the
admin
side
integrations
JIRA.
This
allows
you
to
set
those
specific
fields
and
save
them,
and
the
table
in
question
is
here,
and
we
don't
have
any
data
to
show
in
this
particular
mock-up.
But
this
allows
you
to
see
the
projects
that
are
using
custom
settings
so
projects
that
are
specifically
overriding
the
things
that
are
being
added
at
the
instance
level
and
again
to
back
up
a
few
fields.
A
So
that
means
that
projects
that
have
inherit
from
ID
set
to
nil.
So
that's
what
we're
working
on
for
mass
integrations.
We
do
also
have
a
new
small
setting.
That'll
set
it
so
that
newly
created
projects
have
that
set
to
the
instance
level
ID
by
default.
So
moving
on,
we've
got
two
new
components
that
we're
working
on
for
pyjamas,
specifically
a
file
uploader
and
progress,
bars,
I
think
every
time
I
talk
about
John's
work,
I,
always
talk
about
how
I'm
excited
about
a
specific
component.
Progress
bars
are
really
valuable.
A
They're
used
all
over
the
place,
I'm
really
excited
to
see
how
we
approach
that.
So
that's
awesome.
So
please
start
using
those
in
your
builds.
Once
we
get
those
in
file
uploader
and
progress
bars
should
be
available
soon
and
then
we've
got
some
work
on
the
GDK.
So
broadly,
we've
got
an
epoch
that
we
just
opened.
There
are
a
couple
of
specific
issues
that
we've
got
scheduled
for
13:1,
but
broadly
right
now.
A
What
we're
working
on
is
improving
the
GDK
documentation
specifically
to
make
it
easier
for
new
contributors
for
those
who've
been
using
the
GDK
for
a
few
years,
it's
all
pretty
straightforward,
but
for
those
who
are
brand
new
to
it,
it
can
be
kind
of
difficult
to
dive
into
so
this
is
specifically
improving
documentation
around
how
you
set
it
up
the
first
time.
How
do
you
maintain
it?
How
do
you
use
it?
We
have
a
bunch
of
updates
that
need
to
happen
to
the
pre
racks
right,
so
we've
got
like
a
Google
Chrome
prereq.
A
That's
a
little
out
of
date
has
some
old
info.
How
we
manage
Ruby,
how
we
manage
node.
All
of
these
things
need
some
updates
around
what
their
their
documentation
tells
you
to
do,
and
then,
specifically,
this
is
a
really.
This
is
a
really
weak
issue,
but
it's
kind
of
an
open
question.
What
does
it
look
like
to
have
a
one
line
or
one-click
install
of
the
GDK,
so
ash
who's?