►
From YouTube: GitLab 15.3 Kickoff - Ecosystem:Integrations
Description
Learn more about our group Direction:
https://about.gitlab.com/direction/ecosystem/integrations/
A
A
A
Our
okrs
are
what
would
drive
the
direction
for
us.
We
have
set
okrs
around
improving
our
slack
application.
We
in
in
previous
milestones,
released
a
new
version
of
our
slack
application,
which
enables
granular
bot
permissions
more
fine
grain
permissions
for
the
slack
app
another
okr
for
us
beyond
that.
A
Initial
release
is
to
have
have
an
additional
iteration
for
our
slack
app,
so
that
could
be
really
any
any
feature:
functionality
we
assumed
or
anticipated
that
next
iteration
would
be
around
link
unfurling
that
is
still
in
in
the
cards,
but
for
this
upcoming
iteration
we
have
a
slight
change
and
we'll
talk
through
that.
A
So
we
have
kind
of
three
core
goals.
We
kind
of
highlighted
those
just
in
our
okrs,
but
the
first
one
will
be
enabling,
what's
called
our
slack
app
home
and
we'll
be
upgrading
the
onboarding
workflow
by
adding
new
landing
pages
to
highlight
what
exactly
this
slack
application
does
for
the
customer
as
they're
exploring
the
integration.
A
So,
with
this
initial,
this
initial
goal-
we
should
see
here
in
the
slidecap
home-
feature
an
example
of.
Let
me
jump
to
this
one.
Actually
an
example
of
what
this
could
look
like
within
the
app
home
user
could
be
able
to.
A
You
know,
get
a
sense
of
what
it,
what
it
will
look
like
to
initiate
a
slack
sl
slack
slash
command
with
an
animated
gif.
This
would
be
present
directly
within
the
slack
app
home.
So
once
you
open
up
the
app
you
can
go
to
the
home
section
and
learn
a
little
bit
more
about
what
the
what
this
app
actually
offers.
A
The
second
piece
of
this
is
updating
the
landing
pages
that
are
corresponding
with
with
our
integrations
as
we
were
going
through
our
initial
release.
Through
the
slack
marketplace,
we
were
working
with
slack
and
learned
that
there
are
some
guidelines
that
we
need
to
follow
for
future.
Iterations
around
how
we
design
our
landing
pages-
and
we
also
see
this
as
an
opportunity
to
kind
of
expand
and
improve
upon
the
overall
onboarding
workflow
for
integrations.
So
this
will
probably
be
a
first
attempt
at
at
seeing
how
we
could
scale
this
across.
All
of
our
integrations.
A
So,
as
a
result,
we
are
working
on
rolling
out
this.
This
feature
flag
and
as
a
function
of
that
feature,
flag,
we're
also
adding
some
design
elements
that
will
help
users
to
understand
if
there
are
failures
associated
with
their
web
hooks.
So
if
you
are
a
project
owner
or
maintainer,
and
you
have
a
web
hook
in
your
project,
fail
you'll
be
able
to
receive
a
message
if
it
is
a
500
error,
this
is
going
to
be
a
temporary
or
a
cooldown
period
for
the
web
hooks
to
stabilize,
and
then
it
will
automatically
re-enable.
A
All
right
and
then
goal
number
three
is
surrounding
our
again:
our
security,
reliability
and
availability
limit.
So
we'll
continue
burning
down
those
issues.
We've
made
a
lot
of
progress
in
the
last
milestone,
but
we
still
have
some
some
issues
to
continue
to
address.
A
Yeah
and
one
one
example,
I
guess
that
I
will
point
out
for
that
category
is
we're
going
to
be
working
on
optimizing
a
number
of
our
api
endpoints,
such
as
the
projects
hooks
endpoint.
So,
where
we're
seeing
that
you
know
the
the
performance
is
a
little
bit
slower
than
expected
that
can
affect
our
error
budgets.
So
we're
going
to
work
to
to
address
that.
A
All
right,
if
you
have
any
questions
or
if
you're
interested
in
learning
more
about
what
we're
working
on
about
our
direction,
you
can
visit
our
direction.
Page
I'll,
add
this
in
in
the
links
in
the
video,
and
you
can
also
learn
here
how
to
provide
feedback
or
reach
out.
Alright,
thanks
for
your
time,.