►
From YouTube: Compliance: UX Office Hours (2021-04-23)
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
gitlab
records
video
again
because
the
audio
didn't
record
the
first
time.
So
maybe
that
means
I'll
be
a
little
more
brief.
The
second
time
all
right.
So
I
was
out
last
thursday
I
was
sick,
my
family
friends
day
so
cram
in
two
weeks
into
one
basically
a
week
and
a
half.
So
first
thing
I
want
to
touch
on
was.
A
We
discussed
how
to
address
the
shield
icon.
That
appears
in
git
lab
long
story.
Short
decision
is
to
keep
the
shield
associated
with
the
navigation
item,
security
and
compliance.
We
are
exploring
some
other
options
to
replace
it
for
areas
where
we
see
it
appear
now
like
it
shows
up
next
to
internal
projects.
We
have
some
ideas
running
a
thread
for
how
we
can
better
make
that
more
of
a
distinct
icon.
A
I
also
want
to
take
a
chance
to
really
emphasize
how
important
cross-stage
collaboration
is
for
our
group.
There
definitely
has
been
some
rework
that
we've
been
going
through
to
try
and
better
refine
some
of
the
proposed
work
that
impacts
other
areas,
especially
as
we
continue
to
grow.
We
need
to
be
cognizant
of
how
we
are
impacting
other
stages
and
groups,
so
I'm
thinking
through
some
of
the
bigger
things
that
we're
hearing
from
customers
like
just
needing
more
administrative
power
to
take
advantage
of
all
the
different
features
in
gitlab
and
just
considering.
A
I
also
wanted
to
show
how
that
might
play
out.
We
are.
I
was
looking
at
the
broader
experience
with
pedro
and
mike
around
configuring,
protective
branches
and
approval
rules,
and
you
got
your
code
owners
and
we're
bringing
in
status
checks,
and
these
are
really
great
bits
of
information
to
help
keep
safeguards
in
place.
Keep
production
safe
from
error
prone
things
reaching
it,
and
that
experience
can
be
kind
of
confusing
for
users
that
are
trying
to
set
up
all
these
different
configurations.
A
A
A
So
really
we
had
some
research
around
two-person
approvals.
Didn't
really
test
super.
Well,
it
just
added
more
confusion
into
the
product,
so
we're
gonna
be
cognizant
of
that
and
be
leery
of
where
we
might
implement
it
an
area
we
might
still
consider
it
would
be
for
deleting
a
project
we
have
introduced,
delayed
deletion.
We
really
need
to
dig
in
more.
Why
is
it
necessary
or
how
can
we
better
predict
what
a
accidental
project
deletion
might
happen?
A
A
I
have
a
change
that
I'm
trying
to
propose
in
pajamas.
I
talked
a
little
bit
last
week
about
how
we're
using
the
icon-
that's
outlined
in
blue
as
opposed
to
all
those
other
variations,
but
I
also
want
to
introduce
some
other
patterns
that
I've
seen
kind
of
just
adopted
as
an
implied
usage
for
the
info
icon
versus
a
question
icon,
so
think
about
it
like
this,
if
you're
trying
to
expose
details
within
the
ui
that
aren't
just
directly
there
consider
using
info
icon
on
a
pop
over.
A
So
this
is
like
helpful
information
that
you
might
need
to
use
to
complete
a
task
or
dig
for
deeper
information,
but
if
you
really
are
trying
to
direct
users
to
docs
or
somewhere
else
in
get
lab,
consider
using
the
help
icon
as
it
stands
in
for
these
hyperlinks
that
we're
creating,
which
direct
you
directly
to
documentation
or
something
else
in
a
new
in
a
in
the
same
tab
or
a
new
tab.
I
should
say
so
we'll
see
if
that
goes
through
it's
still
kind
of
working
through
the
refinement.
A
I
also
want
to
say
big
congrats
on
this
huge
release.
It
was
awesome
to
see
pipeline
complying.
It's
really
headlining
it.
I'm
super
stoked
to
see
the
all
the
amazing
work
that
we've
done.
I
have
some
quick
wins
that
I
can
see
us
following
up
with,
like
I
can
already
see.
Some
of
our
docs
has
been
a
bit
of
a
challenge
already
for
communicating
how
to
set
things
up.
So
look
out
for
a
couple,
mrs
for
me
next
week
to
try
and
make
that
seem
a
little
more
seamless
with
that.