►
From YouTube: Compliance: UX Office Hours (2021-09-17)
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's
austin,
I'm
a
senior
product
designer
here
at
gitlab
this
week,
will
be
going
through
the
agenda
of
well.
Basically,
I
guess
like
the
last
two
weeks,
because
I
forgot
to
do
last
friday,
so
here
we
are
to
start
us
off,
I'm
going
to
just
talk
a
little
bit
about
the
default
branch
protections
and
the
work
that
we're
doing
there.
So
essentially
that
works
been
split
into.
A
Two
different
areas
and
stuff
that
we
know
about
and
the
unknowns
so
the
stuff
that
we
feel
good
about,
that
worker
can
be
planned,
broken
down
or
something
forward
on
it.
Thinking
through
how
we
might
do
more
of
the
enforcement
around
that
protection
is
something
I
can
highlight
real
quickly
in
figma.
A
This
is
kind
of
where
I'm
getting
stuck
more
or
less,
and
it's
mostly
because
we
have
this.
This
feature
we
introduced
in
premium
so
being
able
to
set
a
default
branch
protection
is
actually
a
free
feature,
but
we
created
this
ability
to
prevent
owners
from
being
able
to
modify
this
setting
at
the
group
level.
A
This
type
of
enforcement
is
different
than
the
cascading
settings,
and
so
it
can
make
things
a
bit
confusing.
So
just
walk
through
a
simple
illustration
of
this.
If
you're
in
the
admin
area,
once
we've
gone
through
those
known
issues
and
we've
made
some
progress
on
relocating
the
setting
into
the
default
branch
area
of
repositories,
you'll
be
able
to
specify
your
protection
level,
and
then
this
is
that
setting
I'm
talking
about.
A
So
this
is
what
is
currently
in
premium,
allowing
owners
to
manage
the
default
branch
protection
per
group-
it's
kind
of
confusing,
but
what
it's
going
to
do
is
it's
going
to
impact
all
your
new
and
existing
groups?
It's
going
to
essentially
show
or
hide
the
setting
beneath
it.
So
if
it's
not
checked
like
it
is
here
kind
of
show,
this
would
impact
either
administrators
or
an
owner's
view.
So
in
this
example,
I'm
in
gitlab
org
I'm
an
admin,
so
I
can
still
see
all
these
settings
today.
A
A
So
if
we
use
this
to
allow
users
to
enforce
protections-
meaning
not
just
like
hide
the
setting
but
be
able
to
prevent
users
from
making
changes
to
it
so
also
making
it
read-only
and
a
level
beneath
it
and
where
we're
really
trying
to
prevent
the
change,
ultimately
is
what
makes
it
to
the
project
level.
So,
as
you
go
through
the
different
layers
of
git
lab,
you
set
your
protected
branch
default
here
in
the
admin
area.
A
Your
group
then
inherits
that
once
it's
created
and
then
a
subgroup
inherits
that
value
from
its
parent
group
once
it's
created
and
then,
when
you
create
a
project
and
a
repository
is
created,
it's
initialized.
You
then
get
this
protected
branch,
and
so
that's
that's
really
where
we're
trying
to
figure
out.
A
It
all
just
looks
disabled
regardless,
if
you're
an
admin
or
an
owner,
you
notice.
I
know
why,
but
the
answer
would
be:
you'd
have
to
uncheck
two
places
for
it
to
turn
off,
and
that's
just
not
good,
so
I
think
order
of
operations
is
going
to
be
important
here
all
right.
Next,
we've
had
a
lot
of
really
great
additions,
come
through
just
to
help
refine
our
ui
text
I'll
emphasize
again
that
a
big
part
of
improving
our
sus
scores
and
coming
from
learnability.
A
I
am
a
big
proponent
of
thinking
that
introducing
small
changes
that
improve
our
ui
text
would
go
a
long
way.
A
lot
of
things
I
personally
struggle
with
in
trying
to
learn
gitlab
as
a
team
member
is
sometimes
the
descriptions
or
the
help
text
is
unclear,
and
that
already
creates
a
barrier
to
learning
which
makes
me
go
to
docs
and
have
to
read
further.
A
A
So
thanks
for
dan
for
doing
that
cool,
so
next
hen's
been
doing
a
great
job
just
breaking
down
the
compliance
report.
I
know
max
has
been
doing
that
too
we're
going
to
continue
to
ship
more
from
this
epic
around
building
out
the
compliance
report.
I've
been
hyped
about
this
for
months
now.
A
I
think
it
was
like
back
in
january
when
I
was
talking
with
matt
about
our
learnings
from
some
research
sessions,
knowing
that
this
is
going
to
make
a
substantial
impact
on
the
way
that
our
persona
cameron
interacts
with
the
compliance
information
that
we
present
right
now
we're
just
such
a
minimal
state
that
almost
makes
the
feature
useless
in
some
ways.
That's
we
heard
from
a
lot
of
users
in
terms
of
feedback,
so
this
takes
a
huge
leap
forward.
A
There
is
a
scenario
that
involves
looking
for
separation
of
duty
violations
in
gitlab
and
the
easier
that
is
the
better,
we'll
probably
do
that
maturity
rate
daniel
bosco
and
this
oak
as
an
okr
for
this
quarter,
is
working
with
me
on
doing
a
ux
scorecard.
So
you
can
read
and
watch
about
his
experience
through
looking
out
that
issue.
Overall,
he
gave
it
a
b
minus.
I
have
watched
his
unedited
video
and
I
watched
his
edited
video.
It's
great
there's
some
more
details
around
the
experience.
As
you
go
through
the
user
journey.
A
Something
surprised
me.
Some
things
did
not
so
much.
Surprise
me.
I
think
he
did
a
great
job
coming
in
checking
out
using
what
he
knew
about
the
product
we,
I
could
inform
him
about
compliance,
and
I
think
we
have
some
great
steps
that
we'll
be
able
to
take
forward
after
14
4..
A
I'm
also
going
to
be
looking
into
more
sus
focused
opportunities
for
compliance
right
now.
If
you
kind
of
look
at
our
issue
list
that
has
compliance
and
such
time
together,
aren't
that
many,
I
anticipate
a
good
number
of
them
are
going
to
come
from
both
the
audit
events
feature
coming
from
compliance
frameworks
and.
A
I
was
going
to
say
maybe
a
configuration
of
compliance
settings
in
particular,
but
for
now,
let's
just
say,
audit
events
and
compliance
report,
probably
like
the
two
biggest
things
that
we're
going
to
continue
refining
in
the
future.
A
And
trying
to
get
a
quick
update,
there's
some
great
work
going
into
14
4
around
the
merge
request
report
widget,
it
looks
like
a
good
bit
is
going
to
get
done
in
terms
of
creating
that
initial
component,
but
there'll
be
more
levels
that
need
to
be
built
out.
A
So
I
think
once
we
get
through
some
when
I
say
we
once
the
broader
gitlab
team
gets
through
a
number
of
these
issues,
then
we'll
be
ready
to
start
looking
at
when
we
can
schedule
updating
status
checks
to
use
that
component
and
last
but
not
least,
we
hired
a
new
manager
which
is
super
exciting.
Welcome,
blair
to
the
team
he's
watching.
My
video
now
consider
setting
up
some
coffee
with
him
it'd
be
really
great,
just
to
chat
it
up
and
get
to
know
each
other,
a
little
bit
he's
still
on
boarding.
A
So
it's
a
good
time
with
that
I'll
see
you
again
soon.