►
From YouTube: Compliance: UX Office Hours (2021-11-05)
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
product
designer
here
at
gitlab,
working
in
the
compliance
group
so
to
for
this
week.
In
my
realm
I
have
a
good
bit
of
things
that
I
wanted
to
cover,
so
I'm
going
to
do
it
as
swiftly
as
possible.
So
first
thing
I
want
to
share.
Is
I
found
out
that
the
full
project
path
being
super
long
is
very
rare,
so
a
big
shout
out
to.
A
I
think
it
was
paul
who
helped
out
with
us,
but
we
were
trying
to
figure
out
essentially
if
we
should
use
a
multi-line
like
text
area
or
a
single
line
input
when
deleting
a
project,
and
the
concern
was
that
we
would
be
having
projects
with
really
long
name
spaces
attached
to
their
project
name,
which
might
expand
past
our
normal,
like
threshold
for
character
limits
in
terms
of
being
visible
in
the
same
space.
Short
answer
is:
that's
rare,
at
least
in
the
data
set
that
he
pulled
back,
didn't
even
see
any
instances
of
it.
A
Next,
I
wanted
to
talk
about
the
fact
that
I
continue
to
see
features
being
requested
in
the
group
level,
so
they
can
be
better
administrated
at
the
project
level.
This
specific
customer
request
came
around
topics
which
are
available
for
projects,
so
they
wanted
to
essentially
be
able
to
use
this
to
create
metadata
for
their
own,
like
dashboards
and
stuff.
A
So
they
want
to
be
able
to
put
these
topics
on
projects,
but
they're
annoying
they'd
have
to
manage
them
in
individual
projects
and
want
to
be
able
to
do
it,
the
group,
so
what
that
means
is
we
need
workspaces.
I
really
want
to
work
with
nick
post
on
the
settings
portion
of
that.
A
I
also
wanted
to
highlight
next
that
I'm
seeing
if
we
can
get
keys
and
tokens
in
as
a
focus
for
a
redesign
effort,
so
jeremy
is
looking
for
five
areas
of
the
product
in
which
they
would
consider
doing
a
redesign
of
the
ui,
so
some
other
designers
are
adding
in
some
of
their
ideas.
I
would
love
to
see
it
specifically
for
keys
and
tokens.
A
A
A
Another
thing
that
I
found
really
interesting
is
that
we
might
be
deprecating
the
segmented
control
we
don't
what's
interesting
about
this.
Is
we
don't
actually
use
this
true,
segmented
control,
components
on
the
audit
events
page?
We
kind
of
mimic
it
with
a
button
group.
What
they
change
about
is
jerry's
saying
we
should
get
rid
of
it
in
place
of
that
using
a
button
group.
A
So,
even
though
we
did
recently
restyle
the
segmented
control
since
it's
a
radio
button
group
underneath
the
hood,
I'm
thinking
we're
going
to
probably
end
up
landing
somewhere
with
buttons
themselves
instead
and
defining
a
pattern
so
we'll
go
back,
refine
that
and
then
we'll
go
back
and
update
audit
events.
We
need
to.
A
A
I
do
see
sometimes
happen
like
ruby
or
in
other
areas,
and
different
file
types
aren't
so
I
hamel
are
also
creating
alerts,
so
those
will
have
to
be
converted
as
well,
but
really
what
this
epic
is
trying
to
do
is
look
at
some
of
the
alerts
that
can
run
into
each
other
ones.
That
could
be
displayed
at
the
same
time
or
have
weird
overlapping
issues
or
they're
presented
in
a
regular
format
and
I'm
just
trying
to
run
through
each
one.
But
is
this
really
necessary?
A
The
refactoring
effort
turn
this
into
a
proper
global
alert
that
actually
goes
across
the
entire
page,
like
our
pajamas
guidelines
says,
but
as
like
an
alternative,
we
could
just
stop
presenting
a
global
alert
and
make
it
a
focused
one.
So
we
could
tuck
an
alert
section
into
the
drop
down
when
you're
going
to
clone
so
actually
tying
in
like
when
does
it
matter
to
you?
A
It
matters
when
you
have
an
ssh
key
when
you're
trying
to
clone
something
if
you're
trying
to
pull
or
push
that
would
definitely
be
a
situation,
so
it's
possible
that
that
could
be
maybe
displayed
better
like
maybe
we
even
make
that
another
to
do
potentially
some
type
of
action
item
in
there.
I
have
that
mapped
out
for
a
couple.
A
Other
ideas,
like
I
maybe
highlighted
this
last
week,
but
maybe
it
could
be
like
that
for
personal
access
tokens
or
the
other
stuff
as
well,
that
might
expire
those
things
that
are
globally
affecting
your
experience
in
gitlab.
Maybe
we
can
tie
them
more
closely
to
their
respective
areas
so
that
it's
not
just
like
seven
alerts,
stacking
on
each
other,
potentially
at
the
same
time-
and
I
also
want
to
say-
I
took
another
stab
at
getting
danger
bot
to
incorporate
ux
into
the
roulette,
I'm
getting
a
lot
closer.
A
I
simple,
I
simplified
the
scope,
so
I
want
to
keep
this
iteration
smaller
so
that
it's
still
viable
and
useful,
but
it
reduces
the
impact
and
it
doesn't
have
to
be
as
robust.
It
can
still
function
as
a
very
useful
contribution.
This
way.
A
So
I
had
it
working,
but
then
I
came
to
learn
that
there
was
a
lot
more
to
other
steps
involved,
so
I'm
still
working
on
getting
these
other
danger
files
updated
and
then
once
we
get
this
one
merged,
then
then
we'll
be
then
we'll
be
cooking,
so
that
would
be
really
cool
to
see.
So
essentially,
when
you
see
a
merge
request,
come
through
with
ux
and
community
contribution,
you
see
those
two
tags
on
there.
You'll
then
see
in
the
review
roulette
the
actual
tag.
A
So
you
kind
of
see
it's
happening
now
or
it's
picking
up
a
different
designer
to
review
it.
This
will
be
fixed
once
we
fix
some
of
the
metadata
and
yeah
that
will
help
kind
of
get
more
ux
eyes
on
community
contributions,
potentially
creating
a
nice
call
to
action
for
our
contributors.
A
I
don't
know
what
the
best
way
to
break
this
down
is
so
I've
asked
him
to
kind
of
give
it
a
little
check.
I
reviewed
some
of
the
other
implementations
so
like
load
performance
did
this.
We
talked
about
that
a
little
bit
last
week,
but
I
guess
the
way
I
was
imagining
is
like.
Maybe
each
issue
is
one
converts:
the
loading
state
one
does
air
state
one?
Does
this
the
passing
state
one?
Does
the
sub
states
the
drop-down
options?
A
I
don't
know
I'm
not
the
front
engineer,
so
I
definitely
don't
know
what
the
best
way
to
break
it
up.
That's
kind
of
how
it's
magic
in
my
head.
I
don't
imagine
this
bottom
piece
is
going
to
be
built
yet
because
we
don't
have
the
ability
to
show
failed
status
checks
yet,
and
we
don't
have
the
ability
to
show
a
non-blocking
version
of
that,
so
we
won't
get
there,
but
when
I
initially
can't
believe
these
designs,
I
don't
know
what
point
we're
going
to
be
at
when
we're
ready
to
migrate.
A
The
component
and
next
eventually,
users
will
probably
have
the
ability
to
turn
off
audit
events,
and
this
is
going
to
be
for
a
lot
of
the
different
set
different
features
that
you
see
in
visibility.
Settings
under
like
the
project,
general
visibility
and
what
I
was
thinking
as
a
dependency
to
do
this
is.
We
would
definitely
want
to
capture
an
audit
event.
This
is
a
very
meta
example.
A
So
that's
just
going
to
be
coming
down
the
pipe,
maybe
as
we're
trying
to
provide
more
flexibility
into
the
user's
long
term.
Tory's
been
doing
some
really
awesome.
Videos
on
posting
them
unfiltered
about
navigation.
The
changes
that
we're
making
to
it
the
ways
that
we're
going
to
try
and
make
it
more
flexible
for
users
and
hopefully
make
some
good
progress
with
the
foundations
group,
all
right.
That
was
a
lot.
If
you
made
to
the
end,
let
me
know
and
I'll
send
you
a
coffee
chat.