►
From YouTube: GitLab 12.8 Kickoff - Enablement:Ecosystem
Description
Ecosystem PM (Patrick Deuley) walks through the items scheduled for 12.8 GitLab release, shipping Feb. 22nd, 2020.
Planning Board: https://gitlab.com/groups/gitlab-org/-/boards/1167634?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=group%3A%3Aecosystem
A
Hi
I'm
Patrick,
Dooley
I'm,
the
senior
product
manager
for
get
labs,
ecosystem
group
and
I'm
here
today
for
the
12.8
kickoff
we're
going
to
talk
about
the
work
that
we'll
be
doing
over
the
next
month.
So
first
up
we're
gonna
be
looking
at
the
design
of
our
JIRA
comments.
So
if
you
have
the
JIRA
and
get
lab
integration
set
up,
when
you
have
activity
that
happens
inside
of
get
lab,
it
leaves
a
comment
inside
of
JIRA.
A
Here's
a
screen
shot
of
one
of
these
see
our
Turo
here
has
worked
on
a
commit
that
commits
then
created
that
comment
inside
of
JIRA.
That
adds
that,
under
the
activity
section,
we've
had
a
few
requests.
We
have
for
open
issues
today,
and
here
are
some
verbatim
from
those
issues.
It
looks
a
bit
cluttered.
They
want
to
include
the
branch
name
here.
We
want
to
include
the
repo
and
name
and
target
branch.
This
one
wants
to
be
able
to
create
a
template
that
the
users
can
change
it
for
their
needs.
A
All
of
these
things
are
a
lot
of
configuration,
and
one
of
the
design
principles
we
have
for
get
lab
is
for
it
to
be
as
easy
to
use
out
of
the
box
without
lots
of
configuration.
So
we
want
to
see
if
we
can
create
a
more
elegant
solution
that
solves
more
users
needs
without
having
to
have
a
customized
template
or
a
bunch
of
bells
and
whistles
that
you
have
to
set
up
in
twelve
six
and
twelve
seven
get
lab
comm
implemented
a
limit
on
the
number
of
web
hooks
per
project.
So
on
get
lab
comm.
A
That
limit
is
set
to
a
hundred
per
project,
but
for
self
managed
users
we
don't
have
any
documentation
around
how
they
can
implement,
how
admins
can
implement
those
limits
themselves,
so
we're
gonna
document
the
steps
required
to
set
that
up
and
then
admins
can
set
that
up.
So
it's
at
a
limit
that
is
appropriate
for
their
organization
in
the
pursuit
of
our
work
on
this
epic
mass
integration
at
a
group,
an
instance
level
we're
going
to
rename
project
service
to
be
more
generic.
A
So
today,
what
we
call
integrations
in
the
UI
our
project
services
in
our
code
base-
that's
not
really
appropriate
if
services
or
integrations
are
going
to
be
available
at
and
instance
levels,
so
we
need
to
rename
it.
We
think
we're
gonna,
probably
just
call
it
integrations,
but
that's
the
work
that
we'll
be
doing
here
to
make
it
make
more
sense,
as
we
go
down
the
road
on
that.
A
Additionally,
for
that
that
same
work
to
do
mass
integrations,
we
need
to
take
the
service
templates
section
in
the
admin
area
and
migrate
it
over
to
a
integration
settings
again.
Service
templates
are
going
to
be
the
baseline
for
what
our
integrations
at
an
instance,
level
are
going
to
be,
and
so
this
is
part
of
that
migration
we'll
do
the
design
work
to
make
that
make
sense
and
make
it
easy
for
users
to
transition
and
then,
finally,
we're
also
doing
some
design
work
around
allowing
and
disallowing
inheritance
for
integrations.
A
So
the
way
to
think
about
this
is
if
an
integration
is
set
up
at
the
instance
level
and
the
projects
below
it
are
inheriting
those
values.
We
need
to
do
a
few
things.
We
need
to
show
the
users
that
that
inheritance
is
happening.
So
if
you
create
a
new
project
and
it's
already
integrated
with
asana,
why
is
it
integrated?
Where
is
that
data
coming
from
it's
not
a
bug?
It's
not
something
that
happened
on
accident.
It's
a
thing,
that's
intentionally
being
done
by
the
admin.
A
So
we
need
to
notify
the
users
of
that
and
make
sure
that
they're
able
to
see
that
in
a
sensible
way.
We
also
want
to
think
about
how
we
allow
them
to
or
disallow
them
admins
can
allow
or
disallow
that
inheritance
from
happening,
and
then
what
that
looks
like
in
the
UI.
So,
if
you're
not
allowed
to
inherit
a
thing
like
what
does
that
look
like
or
if
you're
not
allowed
to
override
a
thing?
A
A
So
that's
it
for
12-8.
We're
really
excited
about
the
work
that
we're
doing
on
larger
and
larger
scale.
Integrations
I
think
it's
gonna
be
really
powerful
for
customers
with
really
large
installations
right
now,
I
hear
stories
all
the
time
about
customers
who
are
having
to
manage
thousands
of
integration,
and
it's
really
painful
to
do
those
on
one-off
basis.
So
that's
why
it's
our
top
priority
right
now
to
work
on
that
and
I
think
it's
a
really
exciting
work
to
be
doing
thanks
a
lot
for
watching.