►
From YouTube: Compliance: UX Office Hours (2021-03-12)
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
everybody,
my
name
is
austin.
I'm
a
product
designer
here
get
lab.
I'm
going
to
jump
into
the
agenda
for
this
week.
Do
my
best
to
keep
it
under
three
minutes.
If
I
can,
I
mentioned
that
there
was
a
pattern
going
into
pajamas
about
using
ellipsis
at
the
end
of
a
text
button
when
there
is
a
subsequent
action
needed
so
give
that
a
read
check
it
over.
A
He
and
asked
us
a
really
good
question
about
hey
what
if
we
replace
the
new
page
with
the
modal
workflow
when
creating
an
editing
compliance
frameworks.
I
brought
this
forth
to
the
foundations.
Office
hours
had
a
really
great
discussion
there,
I'll
give
you
the
tldr
they
su.
The
foundation
team
supports
the
idea
of
using
a
modal.
In
this
instance.
A
However,
there
are
still
some
strong
opinions
on
other
gitlab
team
members
thoughts
around
if
we
should
be
using
modals
for
this
type
of
workflow,
I'm
going
to
try
and
explore
some
other
options
before
we
settle
on
a
direction,
but,
generally
speaking,
I
love
the
idea.
I
think
I'm
going
to
continue
hashing
it
out
and
see
what
other
options
we
have
available
to
us
to
try
and
keep
the
user
engaged
in
the
workflow.
A
A
Next
marcel
brought
this
great
question
of
like:
where
should
compliance
framework?
The
setting
itself
live
totally
recognize
that
there
could
be
a
better
place
for
this.
I'm
going
to
look
into
setting
up
some
tree
testing
in
the
future
to
go
validate
a
better
placement
for
this
figure
out
how
we
can
keep
it
discoverable
without
necessarily
taking
the
most
valuable
real
estate
in
the
settings
area
of
the
application.
A
We
also
did
a
video
on
unfiltered
discussing
cascading
settings.
Daniel
is
working
on
an
effort
in
access.
It
brought
back
this
idea
from
a
long
time
ago
about
configuring,
protected
branches
and
groups
and
ideas.
I
had
around
like
a
toggle
for
allowing
or
disabling
changes.
So
now
I
really
need
to
go
back
and
sync
with
them
and
make
sure
we're
all.
On
the
same
page,
there.
A
Had
a
really
great
discussion
today
actually
about
this
idea
to
bring
in
the
compliance
like
pipeline
configuration
file
that
we
are
releasing
into
this
policy
builder,
so
there's
a
lot
more
to
be
explored
here,
but
generally
it
would
be
really
cool
if,
instead
of
having
to
do
it
in
your
compliance
framework,
you
could
build
these
policies
for
your
groups.
That
could
incorporate
this
logic
that
might
make
the
users
experience
a
little
bit
more
seamless
right
now.
There
are
a
lot
of
steps
to
get
things
set
up
and
configured
and
tying
together.
A
A
We're
still
hashing
out,
you
know,
details
around
mr
approval
settings
and
rules,
but
one
thing
that
I've
been
trying
to
get
through
is
a
small
change,
just
to
essentially
add
approval
settings
to
clarify
these
little
details
here.
Thank
you,
tan
and
ian
for
helping
me
with
some
of
the
front
end
cleanup
that
I
wanted
to
touch
on
as
well
on
this.
Mr,
I
completed
a
course
this
morning
for
accessibility
for
web
design.
It's
really
great,
I
highly,
would
recommend
if
you
wanted
to
check
this
out.
A
This
led
me
to
a
couple
ideas.
One
thing
that
I
think
would
be
super
helpful
would
be
adding
to
our
mr
template.
This
also
came
from
as
well,
since
he
was
doing
this
for
setting
up
and
testing.
A
I
think
it'd
be
super
helpful
to
identify
what
accessibility
conformances
we
test.
I
have
been
terrible
about
doing
this
in
the
past,
and
this
would
help
remind
me-
and
I'm
sure,
other
people
to
do
this
as
well
get
any
thoughts.
Please
drop
them
in
there
and
lastly,
I
was
working
on
a
merge
request
to
further
extract
our
jobs
to
be
done
statements.
We
did
a
good
bit
of
effort
in
the
fall
to
actually
launch
our
first
job
statements,
which
were
good,
but
not
at
a
high
enough
level.
They
were
a
little
bit
too
descriptive.
A
They
were
more
like
user
stories
more
like
tasks,
so
I
just
reworded
some
of
the
language
here.
I'll
share
this
out
in
slack
as
well,
but
the
overall
thinking
is
these
jobs
are
going
to
be
helpful
for
us
in
completing
category
maturity,
scorecards,
which
might
be
like
an
okr
in
the
next
quarter.
So
having
this
good
foundation
of
job
terminology
will
set
the
wheels
in
motion
for
what's
to
come
in
future
okrs.
Okay,
I
didn't
think
I
kept
it
under
five
minutes,
but
I
did
my
best
so
have
a
good
week.