►
From YouTube: Compliance: UX Office Hours (2021-08-13)
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
Everyone,
my
name,
is
austin,
I'm
a
senior
product
designer
here
at
git
lab
this
week
in
our
design
role
for
compliance
focused
on
a
few
things.
I
wanted
to
share
some
cool
validation.
We
heard
from
a
customer
earlier
this
week.
I
think
one
thing
we
want
to
focus
on
as
we
continue
to
grow.
The
status
checks
feature
is
how
we
can
give
more
autonomy
to
the
responses
that
they
can
give
an
example
that
was
referred
to
was
the
ability
to
use
external
like
pipeline
validation.
A
So
in
this
case,
if
the
response
is
200,
it's
accepted.
If
it's
406
is
rejected
and
then
anything
else
sent
in
those
codes
would
be
accepted
and
logged.
A
What
our
users
might
want
to
do
is
configure
how
they
actually
respond
with
a
message
so
that
they
can
do
more
than
just
pass
or
fail.
So
something
this
might
look
like
is
being
able
to
interpret
a
message
message.
Maybe
it's
in
json,
maybe
it's
another
format,
but
just
something
so
that
they
can
give
some
feedback
to
users
when
something
fails.
So
as
they
build
out
these
automated
checks
that
are
happening
in
their
merge
requests,
they
can
decide
whether
or
not
they
can
provide
that
feedback.
A
The
success
message
might
not
be
so
important,
but
I
think
for
failures.
Knowing
how
to
resolve
this,
especially
if
it's
going
to
be
something
that's
blocking
is
going
to
be
critical
to
the
user's
experience
to
resolving
it,
which
we
already
knew,
but
it
was
just
very
cool
to
see
some
of
that
in
flight
already
otherwise.
This
week
I
was
doing
a
lot
of
setup.
A
Since
we
have
some
engineering
downtime,
I
guess
you
could
call
it
just
with
less
people
currently
working
right
now.
I
took
some
time
to
set
up
for
some
okr
work,
as
well
as
thinking
ahead
to
some
ux
research
that
I
want
to
get
done
or
specifically
around
the
category
maturity
scorecard.
So
one
way
I
was
starting
to
do
that
was
working
on
the
main
heart
of
the
issue
for
compliance
management.
A
I'm
also
going
to
need
to
do
one
for
audit
reports
and
for
audit
events
as
well.
So
you
can
read
more
about
the
research
request.
The
recruiting
effort
for
the
dovetail
research-
this
will
probably
be
the
single
source
of
truth
and
everything
else
will
be
ancillary
and
help
come
out
and
we'll
see
what
the
outcome
is
later.
But
the
goal
is
to
better
evaluate
this
that
we
know,
for
example,
this
is
going
to
be
truly
deemed
viable
in
q4,
given
what
we've
built
already.
A
So,
alongside
the
okr
work,
I've
got
a
pretty
great
issue
put
together.
I
think,
for
daniel
to
take
on
I've
got
to
get
pod
snapshot
set
up
which
should
work.
Okay,
he's
got
a
scenario
he's
going
to
run
through
and
I'm
interested
to
see
what
hero6
he
comes
back
with
in
terms
of
his
evaluation,
with
like
a
ux
scorecard.
A
Sweet
and
then
well,
I
have
time
this
week
I
jumped
and
helped
with
a
few
ui
text
related
things.
Some
of
these
smaller
front
end
changes
I
like
to
just
tackle
when
I
can,
I
think,
they're
kind
of
fun
to
learn
more
about
the
code
base
and
how
to
do
a
little
bit
more
engineering
work.
Just
like
you
better
understand
that
workflow
but
yeah,
so
I
helped
fix
some
of
that,
and
I've
also
got
another,
mr
that
I
opened
today
this
one.
A
I
know
the
tests
are
failing,
but
it
it
adds
a
description
essentially
to
our
approval
settings
for
each
level
as
opposed
to
what
we
do
now,
which
is
add,
links
to
all
the
different
ones,
so
that'd
be
cool
once
it
gets
through,
but
might
need
some
help.
Resolving
the
tests
like
that
have
a
good
weekend.