►
From YouTube: Compliance: UX Office Hours (2021-12-03)
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
compliance
group
got
full
agenda
for
the
past,
basically
a
week,
a
half,
so
I
wanted
to
jump
right
in
so
around
that
I
just
want
to
share
something.
I
was
pretty
proud
of
doing.
I
shared
a
presentation
in
our
ux
showcase
on
wednesday.
Technical
is
asynchronous,
so
it's
been
on
unfiltered
for
a
little
bit
now,
but
I
talk
about
what
I
like
doing
and
trying
to
be
an
active
steward
of
our
gitlab
community.
A
So
if
you
want
to
check
this
out,
go
for
it,
it's
not
that
long
of
a
video
it's
about
maybe
12
minutes
or
so
you
learn
a
little
bit
more
about
the
way
that
I
work
with
our
wider
community
and
kind
of
see
how
like
a
designer,
contributes
in
like
the
open
source
area.
A
Next,
I
also
want
to
share
that.
I
spent
a
good
bit
of
time
diving
into
a
number
of
issues
that
we
have
around
project
deletion.
I
I
feel
like
I
finally
have
caught
up.
I
got
my
head
wrapped
around
it.
I
had
some
design
suggestions.
What
specifically,
how
some
issues
should
be
blocked?
I
don't
know
why
I
listed
the
same
issue
twice
supposed
to
be
a
different
one.
A
That's
my
battle
different
agenda
afterwards,
but
yeah,
I
think
essentially,
the
the
biggest
thing
we
want
to
do
is
prevent
users
from
getting
stuck
in
a
situation
where
they
have
to
know
the
project
url
in
order
to
delete
a
project
permanently.
So
it's
in
that
pending
deletion
state.
A
We
definitely
want
to
make
sure
that
it's
accessible
we're
going
to
do
that
by
exposing
the
deleted
or
the
deleted
projects
tab
to
owners
in
gitlab,
specifically
ones
that
are
on
a
premium
or
higher
license,
and
then
also
we're
going
to
make
it
easier
and
more
seamless
for
users
to
reuse
project
url
slugs
that
have
recently
been
deleted.
A
Next
thing,
I
want
to
just
give
a
couple:
shout
outs
here:
yawn
like
thank
you
so
much
like.
You
really
went
extra
mile
for
making
sure
that
we
had
our
retry
functionality
in
the
status
checks
widget.
A
This
is
really
meaningful,
because
a
piece
of
feedback
that
we
keep
hearing
in
our
ses
results
is
components
of
the
merge
request.
Page
require
you
to
refresh
the
entire
page
in
order
to
see
something
appear,
and
so
in
an
instance
where
maybe
a
connection
gets
blocked
or
reports
blocked
or
something
or
whatever.
Whatever
reason
the
status
check
component
itself
just
fails
to
load,
not
even
like
get
a
signal
back
or
rather
approve
it
just
fails
to
load,
we
give
users
a
way
to
hit
retry
and
then
pretty
quickly.
A
That
gives
you
the
ability
to
see
right
there
without
having
to
scroll
the
page
again
and
find
where
you're
at,
if
it's
actually
able
to
get
to
that
connection,
point
so
kudos.
There
also
just
want
to
say
you're,
just
like
absolutely
killing
the
game.
This
week
I
did
a
merger
quest
review
for
your
ssh
key
expiration
date,
and
I
mean
there
were
so
many
things
that
I
expected
to
not
have
been
covered
and
you
just
knocked
them
all
out,
like
every
edge
case.
I
could
think
of.
A
You
had
addressed
minus
like
one
thing,
and
I
was
just
really
impressed
by
the
way
that
you
you
handled
all
those
threads
and
had
everything
running
so
well.
I
was
able
to
quickly
get
up
and
running
in
my
local,
which
is
always
a
big
plus
also
max
you've
been
super
super
helpful
with
me.
A
Lately
investigating
a
few
issues
like
one
that
you
helped
out
with
was
a
potential
bug
that
was
reported
by
a
user
around
a
setting
not
being
inherited
but
really
came
down
to
more
of
the
way
we
were
explaining,
ui
and
then
another
thing
you
helped
me
out
with
is
just
coming
up
with
like
a
quick
mvc
that
we
could
do
to
try
and
help
auto
populate
some
of
that
data,
which
would
be
really
really
meaningful
to
me
so
yeah.
A
I
want
to
thank
you
three
you're
just
doing
a
great
job
and
I'm
super
glad
to
have
rob
back
as
well.
He's
also
been
doing
great.
Specifically,
I
tagged
him
on
a
few
things
and
he
was
helping
me
like
figure
out
like
another
buddy.
We
have
saw
potentially
compliance
frameworks
where
it's
appearing
for
projects
and
namespaces,
but
nonetheless
glad
to
have
all
of
you
on
team
you're
just
been
really
good
engineers
to
work
with.
A
Also,
I
wanted
to
highlight
that
I've
just
been
doing
a
lot
of
behind
the
scenes,
work
to
try
and
get
the
cms
evaluations
moving
forward.
I
still
have
all
my
pieces
kind
of
in
place,
just
kind
of
working
with
ux
research
to
get
things
scheduled.
I
think
the
git
pod
problem
has
been
resolved.
Unfortunately,
things
have
to
like
re,
populate
everything
and
get
pod.
I
think
to
set
up
my
experiment
again,
but
that's
fine.
I
can
do
that.
A
I
documented
how
I
did
it
last
time,
so
just
need
to
take
the
time
to
do
it.
Next,
I
want
to
share.
We
aren't
going
to
necessarily
have
to
do
some
of
the
work
for
our
users
view
in
the
admin
area.
I
think
access
might
pick
up
a
few
things
here,
specifically
with
how
like
the
table
interactions
are
working.
We
had
a
few
outstanding
things
to
update,
but
I
think
access
is
gonna,
help
us
out
there.
Let's
keep
an
eye
out
for
that,
and
actually
did.
I
just
see
a
new
feature.
A
A
Cool
sorry
got
distracted.
I
also
want
to
share
that
nick
posted
a
really
great
presentation
on
works,
workspaces
and
namespaces,
specifically
how
they
align
our
information
architecture
and,
like
I've,
also
opened
an
issue
to
try
and
start
highlighting
what
I
expect
to
be
impacted.
A
So
specifically,
these
are
maybe
things
we
already
have
in
flight
are
waiting
to
be
scheduled.
That
might
no
longer
be
necessary
if
once
name
spaces
are
created
within
a
workspace,
and
then
we
have
some
things
that
we
haven't
self-managed
right
now
that
we're
trying
to
figure
out
where
they
would
go,
or
maybe
they
exist
in
self-managed
and
sas
today,
but
we're
also
trying
to
figure
out
how
we
consolidate
into
a
single
name
space.
So
we
have
some
things
to
do
there,
but
I'm
going
to
try
and
start
documenting
it.
A
A
I
want
for
basically
what
is
essentially
a
bot
using
a
person's
disguise
as
a
personal
access
token
to
never
expire
or
have
a
really
long,
one
they're
going
to
be
creating
a
specific
experience
for
bots,
specifically,
and
so
those
service
accounts
will
have
their
own
experience
and
they'll
have
a
way
to
specify
how
long
the
duration
can
be,
including,
like
a
non-expiring
one.
So
it
won't
necessarily
be
needed
anymore
for
personal
access
tokens
to
be
non-expiring,
since
you
could
only
kind
of
specify
whether
or
not
the
personalized
token
should
be
able
to
expire
mouthful.