►
From YouTube: Compliance: UX Office Hours (2021-02-25)
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
Everybody,
my
name
is
austin,
I'm
a
product
designer
at
gitlab
jumping
into
this
week's
agenda
right
in
front
of
us,
a
pretty
cool
ui
change
recently
came
to
git
lab
the
reply
field,
so
this
used
to
be
like
a
button
inside
like
an
input.
There's
an
interesting
discussion.
Jeremy
opened
up.
I'm
talking
a
little
bit
more
about
why
this
came
about,
but
you
know
fun,
ux
change
to
the
way
that
we
carry
on
our
discussion
threads
within
gitlab.
A
Next
thing
I
want
to
talk
about.
I
I
got
hooked
on
this
like
random
idea
that
I
had
a
while
back
and
I
had
five
minutes
between
a
meeting.
So
I
kicked
off
this,
mr
to
add,
in
a
functionality
that
has
been
like
driving
me
insane,
I've
added
so
many
collapsible
sections
in
my
markdown
editors,
I'm
hoping
we
can
get
some
more
support
behind
this
and
help
it
move
forward.
I
think
it'd
be
super
useful.
I
know
it's
not
like
vanilla
markdown,
it's
not
the
purest
thing,
but
I
find
it
super
useful.
A
Initially,
I'm
proposing
like
using
a
modal
workflow,
just
talking
annabelle
literally
like
an
hour
ago,
and
she
made
me
very
aware
of
some
like
key
attributes
that
might
make
this
a
little
more
challenging
like
clicking
outside
the
modal,
dismisses
it
or
that
the
primary
action
closes
it.
So
those
things
could
definitely
hamper
the
workflow
a
bit,
so
that
might
be
going
back
to
the
drawing
board,
but
definitely
that
pattern
will
help
us
establish
what
we'll
do
elsewhere
in
the
application.
Once
we
figure
out
the
kinks
there.
A
A
Next,
I
submitted
another
merge
request.
I
guess
merged
requested
a
theme
for
this
week
based
off
of
an
idea
that
tom
had
it's
one
that
I
wanted
to
get
around
to
for
a
while
now,
but
it's
not
obvious
this
little
section
of
checkboxes
down
here
that
they're
not
directly
associated
here
at
least
they're
more
like
approval
settings
as
opposed
to
approval
rules.
A
Funny
enough
that
we
call
them
merge,
request
approval
project
settings
in
the
docs,
so
I've
got
a
change
in
here
to
do
that,
just
as
a
header
really
nothing
crazy
and
updates
the
docs
to
reflect
that.
But
I
think
that
should
help
us
in
our
discussion
about
breaking
down
group
level,
merge
request
approvals
that
way
we
can
help
split
the
work
a
little
bit
better.
A
We
identified
two
there's
going
to
be
one
focused
on
improving
the
messaging
around
ssh
keys,
with
a
stretch
goal
of
replacing
the
component
with
our
calendar
date
picker
and
the
other
one
will
be
clarifying
the
call
to
action
of
personal
access
tokens.
So
this
would
be
great
for
better
clarifying
to
the
user.
Hey,
you
know,
you
have
tokens,
expired,
here's
your
primary
action
to
get
it,
and
also
rearranging
some
of
the
columns
so
that
they
better
align
with
the
content
that
they're
more
relevant
to.
A
I
do
some
stuff
outside
of
compliance,
so
that's
not
necessarily
in
scope,
but
if
you
drop
it
into
the
next
iteration,
because
I'm
gonna
go
out
on
some
vacation
time,
you
can
see
what
I
more
or
less
have
scope
for
myself
for
when
I
come
back
seems
like
a
lot,
but
some
of
these
are
like
super
related,
so
like
gpg,
keys
and
tokens
and
ssh
is
all
kind
of
like
one
altogether
so
trying
to
keep
my
context
switching
to
a
minimum.