►
From YouTube: Compliance: UX Office Hours (2021-11-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
Everyone,
my
name
is
austin,
I'm
a
senior
practice
designer
here
in
git
lab
I'm
working
in
the
compliance
group
and
I'm
going
through
my
async
ux
office
hours.
So
this
week
I
was
kind
of
all
over
the
place
I
was
in
figma
and
issues.
I
was
in
merge
requests
and
felt
felt
really
productive.
So
this
felt
like
a
great
week.
I
want
to
share
a
few
things
that
were
top
of
mind
for
me
and
some
things
I
was
working
through.
A
So
one
thing
that
I
was
just
working
on
was
refining
several
different
ideas
for
how
we
might
start
exposing
the
ability
to
stream
audit
events
in
our
ui.
The
first
thing
that
kind
of
came
to
mind
was
being
able
to
just
use
a
banner
notification
as
a
way
to
bring
awareness
to
users
that
you
can
start
streaming.
These
events
directly
on
the
audit
events
page
itself,
maybe
instead,
maybe
we
end
up
putting
that
into
the
configuration
section,
perhaps
not
sure,
maybe
maybe
not.
A
I
was
also
considering
like
what
it
might
look
like
if
we
did
like
a
split
view,
so
we
have
a
tab
that
shows
the
logs
and
then
we
have
a
tab
that
shows
this
page
for
streaming,
which
then
you
can
set
up
and
then
they'd
start
appearing
in
that
section,
and
I
was
also
thinking
about
if
we
kept
it
all
in
one
page,
add
buttons
to
it.
I
think
maybe
a
potential
downside
of
this.
A
A
We
don't
currently
right
now
as
far
as
I'm
aware,
but
that
might
be
something
we
could
consider
as
a
potential
entry
point,
maybe
even
like
replicating
that
similar
form
but
putting
it
in
specifically
the
configuration
section
for
securing
appliance.
Perhaps
that
can
help
localize
our
settings
a
little
bit
better,
make
it
easier
to
discover,
but
it
still
feels
a
little
disconnected
because
the
logging
portion
will
be
separate
for
the
future.
I
don't
know
we'll
see.
A
Next,
I
went
back
and
revisited
the
credentials
area
a
bit,
so
one
thing
that
I
think
is
worth
considering
is
we
have
a
epic
to
bring
bulk
actions
into
the
page,
and
so
this
would
help
with
expediting
things
like
revoking
all
the
expired
tokens
or
evoking
the
ones
with
no
expiration
or
evoking
ones
that
are
expiring.
Soon.
A
A
So
more
of
this
was
kind
of
refining
for
my
own
benefit
and
some
of
these
things
and
definitely
want
to
keep
in
mind
that
we've
made
a
change
to
pajamas,
and
it
was
on
my
to-do
list
for
this
week
to
get
around
to,
but
I
didn't
get
much
more
than
starting
an
epic
we've
defined
the
date
and
time
guidelines
for
how
we
want
to
use
absolute
and
like
relative
time.
A
So
this
might
be
useful
if
you
want
to
check
this
out,
but
we
give
you
like
a
decision
tree
on
which
to
use
and
why
so,
I
think
for
audit
events
and
we'll
probably
default
to
using
the
absolute
time.
So
we
can
make
sure
things
are
converted
correctly,
but
we
may
still
want
to
give
the
option
to
if
it's
presented
in
iso
or
if
it's
presented
in
this
format
like
more
readable
version.
A
A
But
another
thing
I'm
trying
to
consider
is
like
how
do
these
how's,
like
the
credentials
area
as
an
example,
work
with
workspace
or
access,
something
that
I
know
access
is
working
on?
Is
project
access
tokens
like
how
those
are
currently
tied
into
creating
the
bots
that
people
are
using
right
now
so
as
they're
creating
a
form
to
create
bots
like
how
does
that
integrate
into
our
credentials?
Inventory,
that's
something
we
got
to
be
thinking
about
and
then,
as
workspace
is
spinning
up.
A
And
I
spent
like
basically
a
whole
day
like
opening
and
creating
issues
and
like
setting
everything
up
for
the
different
category
maturity
scorecards,
that
we
have
on
the
docket.
So
I've
got
a
main
issue
for
compliance
management,
audit
events
and
audit
reports.
We've
got
a
research
request
open
to
request
for
help
from
ux
research.
We've
got
a
recruiting
effort
to
ask
for
recruitment
effort
for
each
one
compliance
management,
it's
going
to
be
internal
audit
reports.
Also,
the
internal
audit
events
will
be
the
only
one
that
ends
up
going
external.
A
A
Complete
and
then
complete
to
viable,
no,
it's
going
from
viable
to
complete
I've
like
gotten
so
mixed
up
with
all
these
different
things.
So
to
go
to
complete
you
get
tests
with
external
participants,
so
you
don't
have
to
necessarily
know
about
all
these,
but
just
know
that
we
have
a
lot
of
issues
in
flight
to
try
and
get
that
research
accomplished
in
the
next
couple
quarters.
A
Next.
I
also
want
to
just
give
myself
a
little
pound
of
the
black
back.
The
danger
bot
will
spin
for
ux
reviewers.
There
is
a
tag
for
community
contribution
ux.
I
think
the
merge
requests
that
I
merged
it
on
has
this.
As
an
example,
I'd
add
the
label
rain
the
danger
review
job
yeah,
so
you
kind
of
get
like
an
example
of
what
that
looks
like
here.
A
The
great
thing
is
it
works.
I
it
will
pull
in
someone
random.
The
downside
is
in
community
contributions.
You
need
a
gitlab
team
member
to
actually
kick
off
the
danger
review
job.
So
it's
not
perfect,
but
we
can
extend
the
logic
from
here
and
I
learned
a
lot
about
all
the
different
danger
files
that
have
to
be
updated
to
make
that
happen.
So
that
was
a
really
good
learning
experience
this
next
one
I
thought
was
gonna,
be
a
big
deal
and
it
turned
out
not
to
be
a
big
deal.
A
So
as
we're
thinking
about
being
able
to
turn
off
different
settings
or
really
turning
off
disabling
specific
features.
You
can
currently
disable
security
and
compliance
which
may
make
you
wonder,
like
oh,
what
happens
to
audit
events?
Well,
you
will
no
longer
be
able
to
access
it
in
ui,
but
it's
not
currently
disabling
the
feature
itself.
So
no
security
risk
there.
A
It's
still
logging
all
the
different
data
attributes,
and
this
is
probably
something
we
want
to
keep
in
mind
if
we
end
up
giving
the
ability
to
disable
audit
events
specifying
that's
not
actually
going
to
disable
the
logging
of
those
events,
it's
just
going
to
hide
them
in
the
user
interface.
A
That
might
be
a
better
way
to
explain
that
feature
to
users
once
we
get
around
to
it
and
I'm
also
still
working
on.
Are
you
I'm
still
working
on
reviewing
our
community
contribution
wow,
it's
friday
at
five,
really
feeling
it
yeah?
If
you
want
to
know
like
where
I'm
struggling,
there's
a
video
on
loom,
you
can
follow
the
links
and
get
to
it
but
yeah.
What
was
weird
is
like.
A
Sometimes
the
setting
would
affect
the
project
or
the
group
that
was
underneath
it
and
it
seemed
like
it
would
only
update
it
if
the
initial
value
had
not
ever
been
deliberately
changed
by
a
user,
which
seems
really
weird.
I
don't
know
why
it
would
be
caching
that
value.
That's
the
only
reason
I
could
distill
down
to
why
it
was
happening,
but
essentially
I
was
seeing
an
inconsistency
in
the
user
experience
recently.
A
I
was
expecting
it
to
show
up,
and
so
I'm
trying
to
kind
of
suss
out
why
that's
happening
before
we
move
forward
with
the
merging,
but
we
did
think
about
maybe
putting
spine
feature
fog
until
we
cleaned
it
up
a
little
bit
more
if
the
user,
or
rather
the
contributor,
still
sees
it
as
valuable
right
now
and,
lastly,
working
with
sam
a
better
way
to
communicate
our
long-term
vision.
A
So
this
came
out
of
like
our
one-on-one
discussion
on
monday,
something
that
I
felt
like
was
a
big
big,
big
topic,
especially
with
the
way
we
communicated
what
compliance
was
doing.
A
These
might
be
official
ones
like
the
ones
they
listed
in
the
merge
request
itself
with
sam,
or
these
could
be
internal
ones
that
they
themselves
as
an
organization
want
to
enforce
so
it
you
know,
we
haven't
quite
gotten
there
yet
we're
just
we're
still
laying
the
foundation.
So
as
we
improve
those
different
configuration
options
as
we
make
git
lab
more
powerful
to
administrate.
A
That
sets
us
up
nicely
for
being
able
to
say
hey.
You
know
if
you're
going
to
be
working
on
a
project,
that's
I
don't
know
responsible
for
socks.
Then
you
need
to
make
sure
that
merge,
request.
Approvers
cannot
approve
their
own
merge
requests
and
that
needs
to
be
on
every
project
in
your
entire
instance,
not
just
one
project,
and
we
can
help
better
administrate
things
like
that.
Now
that
we're
getting
more
more
granular,
with
the
way
that
we
can
administrate
from
a
higher
level,
so
yeah,
that's
that's
it!
A
For
the
week
it's
been
been
a
good
one
and
I'm
looking
forward
to
the
weekend
catch
y'all
next
week.