►
From YouTube: Compliance: UX Office Hours (2021-05-07)
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
Hey
everyone,
my
name
is
austin.
I'm
a
senior
product
designer
git
lab
in
the
compliance
group
jumping
into
some
news
for
this
week,
discover
this
really
cool
tool
that
we
talked
about
in
slack.
A
I
thought
I'd
share
with
everybody
else
in
case
you
haven't
already
noticed
this,
but
there's
now
an
option
to
select
a
reviewer
from
ux,
which
is
awesome,
because
this
will
help
you,
if
you're
not
just
looking
for
me,
but
if
you're
looking
for
anyone
to
help
review
ux,
you
can
also
spin
the
wheelbase
off
of
some
parameters
that
you
put
in
and
get
someone
random,
so
that
should
help
you
when
you're
in
your
mrs
looking
for
a
ux
person
to
review
it.
That
isn't
me
next.
A
I
wanted
to
share
that
we're
keeping,
or
at
least
I'm
keeping
up
to
date
with
this
kr
focused
on
improving
the
mr
widgets.
So
as
we
look
to
introduce
status
checks,
we're
going
to
stay
in
line
with
any
design
decisions
that
come
through
this
currently
so
far,
I've
just
been
trying
to
share
the
different
states
that
it's
going
to
appear
in
for
status,
checks
and
we'll
see
how
it
evolves
from
there.
A
Next,
I
also
wanted
to
share
some
more
collaboration,
we're
doing
with
the
pipeline
authoring
group,
so
thinking
about
the
holistic
experience
of
authoring
pipelines
and
how
they
merge
together.
I
was
coming
up
with
a
couple
ideas
of
how
we
could
demonstrate
to
users
that
there
is
an
impact
on
the
pipelines
that
they're
working
in.
So
some
of
these
ideas
include
like
showing
a
dedicated
tab
to
view
the
preview
of
the
compliance
pipeline.
That's
been
inherited
or
perhaps
being
able
to
show
the
visual
of
the
compliance
pipeline
alongside
the
project's
pipeline.
A
I
was
also
thinking
just
putting
in
like
the
header,
a
little
banner
notification,
essentially
telling
you
that
this
project's
inherited
a
compliance
framework
and
a
way
to
access
that
one.
So
you
have
to
keep
in
your
mind
like
where
it
is
or
where
it's
coming
from
and
just
trying
to
create
more
awareness
in
the
system.
A
We
had
a
nice
contribution,
come
in
on
the
collaboration
on
merge
requests
so,
as
we
think
about
introducing
features
specifically
related
to
compliance
that
impact.
The
merge
request,
experience
we're
going
to
use
these
frameworks
that
have
been
established,
or
rather
look
for
ways
that
we
can
properly
engage
like
the
code
review
group
or
source
code
just
so
that
we're
making
sure
that
we're
not
negatively
impacting
a
feature
set
or
degrading
the
mr
experience
any
further.
A
There
were
two
insights
that
we
brought
up
in
a
foundation's
office
hours.
The
first
is
on
a
button
variant.
I
won't
necessarily
open
this
up,
but
just
know
that
we
tend
to
overuse
the
secondary
danger
button
or
even
the
danger
button
itself
in
a
table
when
there
are
a
bunch
of
delete
buttons.
That's
not
something
we
should
really
scream
about
so,
especially
in
cases
where
we
use
a
modal
to
prevent
a
user
from
removing
an
object
or
deleting
in
the
first
place,
we
can
use
the
default
button
in
those
cases.
A
A
So
it's
more
on
a
case-by-case
basis
and
we
just
kind
of
have
to
check
it
as
we
go,
and
this
was
a
really
neat
issue
that
pedro
tagged
me
in
so
four
years
ago
someone
brought
up
the
idea
of
status
checks
and
we
are
doing
something
very
similar
with
status
checks.
So
we're
going
to
continue
diving
into
this
and
stressing
out
some
more
of
the
feedback
that
users
were
looking
for
and
understanding
what
were
they
looking
for
out
of
these
web
hooks?
How
could
we
maybe
incorporate
this
into
the
existing
workflow?