►
From YouTube: Compliance: UX Office Hours (2021-08-20)
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
the
senior
product
designer
here
at
git
lab
working
for
the
compliance
group.
So
this
week
I
wanted
just
to
highlight.
I
spent
a
good
bit
of
time
working
on
my
360
feedback.
Most
of
it
was
four
people
in
our
group,
so
hopefully,
as
I
tie
it
together,
you'll
find
that
feedback
useful.
A
Let
me
know
in
the
future
if
it
helped
you
or
not,
I'd
love
to
know
if
you
enjoyed
or
found
my
feedback
constructive,
but
outside
that
I
was
doing
a
number
of
things
to
kind
of
stay
occupied
and
try
and
accomplish
some
smaller
tasks.
Since
I
was
taking
a
lot
of
my
mental
capacity
this
week,
one
of
the
things
that
I'm
still
building
out
are
the
scenarios
for
the
category
maturity
scorecard.
A
My
concern
with
these
controls
is:
it
might
take
way
too
long
to
actually
run
the
actual
research
itself,
and
I
don't
know
if
that's
going
to
be
acceptable
or
not.
So
I'm
going
to
work
with
sam
on
kind
of
synthesizing
this
down
to
my
ex
research
counterpart
ana,
to
just
make
sure
that
we
have
a
good
scenario
here.
I'm
going
to
also
do
this
for
audit
events
and
audit
reports
just
so
that
we're
getting
ready
for
those
evaluations
coming
up.
A
This
is
also
a
fun
thing
that
I
was
looking
into
this
week,
so
we
actually
have
a
feature
that
had
a
feature
flag
turned
off.
So
if
you
go
into
security
and
compliance
and
in
a
project,
not
in
a
group
and
you
open
up
that
in
a
new
tab,
you'll
see
that
there's
a
configuration
page.
So
there's
one
for
security
testing
and
one
for
compliance.
This
description
doesn't
change,
but
the
only
thing
it's
showing
here
is
license
compliance.
So
one
thing
that
I'm
considering
is
how
we
might
actually
make
that
page
more
useful.
A
But
specifically,
there
are
a
few
that
we
could
highlight
for
a
specific
project
itself,
so
we
could
highlight
the
usage
of
compliance
frameworks.
We
could
highlight
the
usage
of
external
statuses,
whether
inherited
membership
is
enforced
or
not.
What
the
current
ssh
key
restriction
is,
if
they've
done
any
separation
of
duty
configurations
now,
mostly
this
will
just
be
pointers,
so
it
would
point
you
back
to
where
other
settings
exist
in
git
lab,
but
this
would
be
a
neat
way
of
kind
of
showing
hey.
A
Are
you
taking
advantage
of
all
the
different
compliance
features
that
we
offer
you
in
gitlab,
even
if
they
don't
necessarily
belong
to
our
group
like
license?
Compliance
doesn't
necessarily
belong
to
us,
but
it
is
kind
of
a
part
of
the
compliance
management
journey.
If
you
want
to
think
about
it
that
way,.
A
I
also
wanted
to
highlight
something:
that's
been
coming
up
in
some
discussions
so
as
we
consider
the
experience
of
interacting
with
gitlab,
we
have
a
large
number
of
features
in
the
sidebar,
both
at
the
group
and
the
project
level.
Both
are
this
way
and
we're
trying
to
holistically
think
about
how
we
can
create
a
more
focused
space
for
the
user
so
that
we're
not
creating
more
cognitive
load.
A
One
area
that
has
been
called
out
recently
is
requirements.
It's
a
lower
feature
in
terms
of
active
users,
it's
a
useful
feature,
but
it
might
be
better
located
somewhere
else.
So,
as
we
come
across
some
of
these
revisions
or
these
ideas
to
better
improve
our
navigation
and
the
product,
if
it
somewhat
relates
to
us,
I
might
encourage
us
to
think
about
taking
that
on
just
to
help
keep
that
at
the
top
of
focus
as
we
try
and
refine
the
product
to
make
the
sus
a
little
bit
better.
A
Definitely
what
we've
been
hearing
is
hey.
You
have
a
lot
of
features,
but
you're
telling
me
all
at
the
same
time
and
it
just
kind
of
clutters
the
space
so
we'll
see
where
we
go
with
that
outside
of
the
compliance
group,
I've
been
working
on
a
few
things
around
pajamas
to
better
improve
our
documentation
for
the
gitlab
flavored
markdown.
So
in
my
case,
I'm
working
on
this
audio
one,
it's
kind
of
cool
for
each
browser.
A
Whenever
you
attach
a
file,
it
has
a
custom
player
that
displays
and
the
one
thing
I'm
going
to
recommend
for
sure
in
terms
of
the
implementation
is
that
it
expand
100
to
its
container
in
the
div
right
now.
It's
just
about
like
this
size,
it's
kind
of
tiny
which
would
suck
if
you
had
a
large
file
and
you
wanted
to
scrub
it.
So
that
would
be
cool
usability
improvement.
We're
also
trying
to
like
figure
out
what
we're
going
to
build
for
figma.
A
What's
going
to
actually
be
owned
by
git
lab,
I
don't
think
we're
going
to
end
up
owning
the
styling
of
this.
For
now
I
thought
maybe
we'd
go
down
with
creating
our
own,
like
gitlab
flavored
audio
file
player,
but
I
just
don't
think
it's
high
enough
priority
right
now.
So
mostly
it's
around
documentation-
and
I
want
to
give
a
special
shout
out
to
both
max-
and
I
mean
y'all-
are
great.
I
really
enjoyed
working
with
you,
I'm
actually
doing
great
on
mr
approval
settings
just
watched
your
video.
I
love
to
see
how
that's
coming
through.
A
I
I
have
played
with
those
settings
like
endlessly
and
thought
about
them
deeply.
So
it's
really
cool
to
kind
of
see
that
come
to
fruition
and
thank
you
so
much
for
pairing
with
me.
It
was
been
really
fun.
This
week
we
got
to
work
on
some
tests
together.
I
learned
more
about
how
to
run
tests
locally
and
how
to
better
write
smaller
tests.
So
that's
going
to
help
improve
the
pipelines
that
end
up
running
in
the
future,
hopefully
not
costing
the
company
so
much
pipeline
minutes,
but
that's
it
for
this
week.