►
From YouTube: Compliance: UX Office Hours (2021-10-22)
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,
I'm
going
to
try
and
keep
today's
friday
agenda,
pretty
short,
I'm
really
hungry
and
want
to
go
find
something
to
eat.
So
first
thing
I
want
to
touch
on
this
is
something
I've
been
mulling
over
all
week.
There
have
been
some
updates
to
project
deletion
since
the
last
time
we
as
a
group
touched
it,
and
I
really
want
to
go
in
and
help
refine.
A
This
experience
a
little
bit
more
and
there
are
two
areas
that
I'd
like
to
see
some
improvements
done
in
the
future.
One
is,
namely
around
how
we
differentiate
the
experience
around
a
delayed
deletion
versus
a
immediate,
like
permanent
deletion.
I
think
the
delay
deletion
should
come
with
just
more
of
a
hesitancy
or
warning
associated
with
it,
and
the
permanent
deletion
should
be
like
the
final
stop
so
using
some
color
and
iconography
to
distinguish
that
additionally,
there's-
I
didn't
realize
this
until
this
week,
but
there's
been
a
third
way
to
finally
delete
a
project.
A
So
this
is
in
the
premium
license,
but,
let's
say
you've
gone
in,
you've
got
delay.
Deletion
on
you've
deleted
a
project
cool.
We
don't
tell
you
this
in
the
delete
area,
but
it
says
that
hey,
you
know
this
project
can
be
deleted
on
a
specific
date.
But
what
if
you
just
want
to
delete
it
right
now,
you
just
can't
wait.
You
just
have
to
get
rid
of
it.
Well,
you
technically
can.
A
A
There's
no
going
back,
give
you
some
data
on
it
and
the
one
area
I
also
kind
of
want
to
help
differentiate
is
whether
or
not
the
project
is
a
fork,
that's
kind
of
important,
which
is
why
I'm
starting
to
label
this
as
the
leading
source
project
and
deleting
forked
project,
I
think,
potentially
even
adding
that
text
before
could
really
help
clarify
what
is
about
to
happen
as
well
as
what
type
of
project
it
is.
So
we'll
continue
working
on
that
with
tech,
writing
and
then
look
forward
to
some
implementation
in
the
future.
A
A
I
won't
be
adding
a
severity
if
it's
something
that's
for
a
new
feature
that
doesn't
count
so
much
rather
for
things
that
already
exist
or
if
it's
like
a
refinement.
A
That
would
be
something
we
might
want
to
add
a
severity
for
just
to
indicate
if
it's
something
that's
significantly
hindering
the
experience
or,
if
it's
just
more
of
a
nice
to
have,
but
there's
a
workaround
available.
A
A
Pipelines
are
so
integral
to
the
experience
of
merging
code
in
gitlab
that
compliance
wants
to
have
a
nice
overarching
view
of
that
and
so
ways
that
we
can
think
about
integrating
tightly.
There
will
be
cool
in
the
future.
We
have
identified
a
few
ways
to
at
least
expose
like
compliance
pipelines
in
the
pipeline
pages
themselves,
which
I
don't
think
we
ever
got
around
to
so
maybe
that's
something
we
could
consider
picking
up
for
that
group.
A
Additionally,
we
planned
a
long
time
ago
to
go
back
to
the
credentials
page
and
reorganize
some
things
in
our
settings
to
help
unify
that
experience.
I
think
we
might
be
able
to
start
taking
on
some
effort
there.
A
Additionally,
we've
talked
about
surfacing
some
more
information
inside
of
compliance
framework,
so
as
you're
building
them,
you
can
see
maybe
the
projects
that
are
impacting
some
of
the
downstream
effects
that
they're
creating
just
so
you
can
have
awareness
of
how
that
compliance
framework
is
being
utilized
or
what
benefits
you're
going
to
reap
from
it
and
then
another
area
that
I
was
just
looking
at
this
week
again.
That's
just.
I
keep
forgetting
some
so
much
context.
Switching
the
configuration
tab
or
the
configuration
page
under
security
compliance
there's
a
tab
for
securing
testing.
A
We
have
one
for
compliance
as
well,
but
we're
not
utilizing
it
for
anything
yet.
So
I
had
some
ideas
of
what
to
do,
but
haven't
really
got
around
to
really
fully
looking
into
those
things.
So
I
might
put
that
on
my
agenda
for
next
week,
but
speaking
of
my
jennifer
next
week,
I
did
pause
a
little
bit
on
the
compliance
management
cms
building
because
there
is
a
issue
that
needs
to
be
resolved
in
creating
git
pod
workspaces.
A
So
once
that's
resolved
I'll
get,
the
dry
runs,
going
we'll
be
good
there,
so
I'm
gonna
start
building
the
one
for
category
events
or
it's
friday,
audit
events
and
yeah.
If
you're
interested
on
any
of
these
things.
Let's
let's
chat
about
it.
If
you
want
to
do
one
of
the
dry,
one
dry
runs
more
than
welcome
to,
but
yeah
have
a
good
friday.