►
From YouTube: Compliance: UX Office Hours (2021-07-30)
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
practice
center
git
lab
the
compliance
team
this
week
I
was
only
here
for
a
few
days,
but
that
doesn't
mean
we
don't
have
a
packed
agenda.
So
the
first
thing
I
wanted
to
share
was
we
wrapped
up
the
design
effort
around
the
status
checks.
So
if
you
check
out
this
epic,
it
shows
you
all
the
different
issues
that
we
had
opened
to
show
how
these
will
progress
specifically
for
status
checks.
We
have
the
different
variations
in
the
different
states.
A
So
I
don't
think
that
means
the
compliance
group
specifically
will
be
implementing
the
update
to
status
checks,
but
we'll
keep
an
eye
on
it.
The
next
thing
is,
we
have
a
q3
okr
in
which
we'll
be
conducting
or
I'll
be
conducting
a
ux
scorecard
alongside
a
buddy.
So
I
have
opened
that
up
essentially,
what's
going
to
happen
is
we'll
assign
sam
and
I
will
pick
a
job
and
then
another
designer
is
going
to
try
and
perform
that
job.
A
It's
going
to
be
daniel
fosko
and
the
goal
here
is
to
look
for
learning
opportunities
and
to
create
some
actionable
insights
from
it
to
continue
to
improve,
like
our
onboarding
experience
in
gitlab,
we'll
see
how
that
goes,
and
I'm
interested
to
see
if
we
get
some
useful
feedback
or
if
we
struggle
next.
I
just
wanted
to
share
that.
There
was
an
update
to
the
handbook
which
brought
in
some
inspiration
from
the
auto
devops
design
sprint
it
kind
of
talks
around
how
to
run
it.
A
Who
should
be
involved
the
time
frame
that
kind
of
stuff
we
haven't
done.
One
in
our
group
ourselves
we'll
consider
that
if
it
makes
sense
for
us
in
the
future,
but
it's
just
a
way
to
help,
try
and
create
a
repeatable
pattern
for
other
teams
to
replicate
if
they
decide
that.
A
That's
the
right
tool
for
them
to
solve
a
bigger
problem,
also
spurring
off
of
a
conversation
I
had
with
rob
and
ian
last
week
around
the
settings
placement
of
messages,
one
area
that
I
would
really
love
to
try
and
clarify
is
like:
where
do
we
display
feedback
to
the
user
right
now
in
settings?
I
most
commonly
see
it
displayed
as
a
flash
message,
as
it
appears
at
the
top,
whether
that's
a
success
or
a
success
or
sorry
a
failure
or
a
success
message
displayed
as
an
info
alert.
A
I
think
what
would
make
more
sense
to
me
is
getting
in-page
alerts
when
there's
errors
and
getting
toast
notifications,
when
the
save
of
the
section
was
successful.
Ideally
an
async
refresh
state,
not
refreshing
the
entire
page.
It
kind
of
is
a
disjointed
experience,
so
I'm
going
to
see
where
that
will
go,
maybe
it'll
be
documented.
A
Maybe
it
won't
I'll
keep
you
posted,
I'm
not
going
to
open
this
one
since
it's
a
private
issue,
but
just
as
we
consider
our
safe
framework
on
what
we
should
be
discussing,
I
think
the
one
thing
that
we
call
is
like
we
don't
want
to
share
the
system
usability
scale
externally.
That's
just
gonna
be
something
we're
gonna
keep
internally.
A
Most
of
the
stuff,
though
listed
in
there,
something
that
we
can
usually
be
transparent
about,
but
our
set
score
is
just
something
we're
gonna
keep
a
little
bit
closer
and
then,
additionally,
today
I
learned
that
you
can
set
default
branch
protections.
I
honestly
didn't
know
this
was
a
setting,
but
it
is
so
it
kind
of
makes
the
initial
proposal
of
this
null
and
void,
because
you
already
can
create
a
sensible
default
at
your
group
level.
A
It's
just
overrideable
right
now
and
then
additionally,
what's
a
bit
of
annoying
thing,
is
it
doesn't
have
all
the
different
variations
that
you
could
create
with
the
drop
down
options
and
the
toggles,
so
it
leaves
you
a
little
empty-handed
if
you
wanted
to
configure
someone
for
to
be
allowed
to
push
or
setting
none,
no
one
as
the
default.
You
can't
really
do
those
things
so
trying
to
figure
out
if
we
want
to
basically
extend
the
drop
down
option
using
the
cascading
setting.
A
That
probably
is
the
smallest
change
here
or,
conversely,
we
could
maybe
replace
the
drop
down
option
altogether
and
put
the
form
in
there.
That
way,
we
would
have
to
manage
all
the
different
variations
and
come
up
with
text
for
basically
the
same
thing
so
we'll
see
that
goes,
but
today
learned,
I
had
no
idea
that
was
there
good
thing.
We
didn't
implement
it
just
yet,
because
it
would
have
been
a
conflicting
feature
for
sure
so
great
call
out
there,
carlos
for
highlighting
that
for
our
team
and
that's
it
catch
you
next
week.