►
From YouTube: Compliance: UX Office Hours (2021-06-10)
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
rig
mary,
I'm
a
senior
product
designer
here
at
gitlab,
so
for
this
week
most
of
my
time
was
spent
resolving
discussions
and
just
thinking
through
some
ideation
on
some
different
features
that
we've
been
focused
on
for
the
past
milestone.
So
I
won't
dive
into
too
much
detail
about
that
until
we
get
to
some
more
important
decision
making
or
at
least
come
out
with
a
meaningful
decision.
But
here's
some
other
highlights
from
the
week
I
presented
at
the
ux
showcase.
I
did
it
on
topic
around
not
sleeping
on
documentation.
A
It
does
seem
like
a
very
meaningful
feature,
especially
for
customers
and
users
that
are
trying
to
take
data
from
git
lab
and
meld
it
with
a
collection
of
other
data,
either
for
automation
purposes
or
for
reporting
a
unique
requirement
that
I
heard
there
was
they
were
taking
screenshots
of
the
audit
events
page
and
initially
I
just
thought:
oh,
that's
because
they
can't
take
the
data
easily
outside
of
gitlab,
but
it
turns
out
it's
like
an
auditor
requirement.
A
A
We're
also
exploring
some
ideas
to
bring
in
other
icons
for
security
and
compliance.
So
jeremy
was
just
sharing
a
couple
ideas
here
and
there
are
lots
of
others
that
we
might
explore,
but
we're
trying
to
just
not
always
use
the
lock
or
shield
icon.
They
can
be
representative
of
a
lot
of
things
and
we
don't
necessarily
want
to
degrade
what
their
initial
meaning
of
definition
is
in
the
ui.
A
Today
I
spent
a
lot
of
time
learning
how
to
use
apis.
I've
never
really
interacted
with
apis
before
so
I
was
learning
how
to
use
postman.
First
thing
I
did
was
learn
how
to
like
get
to
our
audit
events
and
pull
back
those
results,
which
was
good
good
thing
to
learn,
but
we
hear
that
customers
are
using
the
api
to
manage
their
settings.
So
let's
say
I
need
to
go
up
to
all
the
protected
branches.
That's
what
I
was
trying
to
do
myself
today,
couldn't
quite
figure
it
out.
A
In
this
epic
trying
to
share
why
using
compliance
pipelines
has
been
a
challenge,
it's
it's
long.
I
haven't
even
digested
all
of
it
myself
and
come
back
to
be
on
monday,
but
it
might
be
worth
a
read
just
to
better
understand
how
users
are
trying
to
implement
it
and
what
they're
looking
for
out
of
it
that'll
help
define
our
roadmap
in
the
future.