►
From YouTube: Compliance: UX Office Hours (2021-06-04)
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
product
designer
gitlab,
looking
into
the
agenda
for
this
short
week.
The
first
thing
I
want
to
touch
on
was:
I
spent
a
good
bit
of
time
in
merge,
requests
and
responsions,
which
you
know
keeping
up
with
the
async
communication
could
be
a
good
bit
of
work,
but
what
got
me
most
excited
was
just
seeing
the
progress
we've
been
making
on
status
checks.
It's
looking
great
super
stoked
that
we're
getting
closer
to
the
finish
line
of
getting
that
feature
and
its
first
release
out.
A
The
next
thing
I
want
to
highlight
is
I'll,
be
presenting
next
week
at
the
ux
showcase
in
case
you're
interested
it'll,
be
on
wednesday.
I've
got
my
slides
here,
I'll
be
talking
about
how
we
don't
want
to
sleep
on
documentation.
So
I
think
one
thing
we've
all
been
seeing
is
just
continual
questions
around
some
of
the
features
we've
released.
Our
documentation
is
so
key
for
helping
users
understand
how
to
configure
their
environments,
how
to
set
up
their
things
for
the
first
time
and
great
documentation
is
tied
directly
to
that
user
experience.
A
So,
let's
make
sure
we
have
great
examples
in
there,
especially
for
ones
that
tie
to
our
persona
cameron,
all
right,
and
so
next
I
spent
just
a
day
focused
on
trying
to
establish
a
mechanism
for
how
we
might
bring
audit
events
into
a
web
hook.
Functionality
I'll
highlight
a
few
things
here,
since
it's
not
a
super
long
agenda,
I
was
considering
how
we
might
use
the
existing
webhook
interface
to
do
this,
it's
possible
that
we
could
bring
it
in
here.
My
biggest
concern
with
just
tucking
on
events,
nice
and
neatly
in
there
is.
A
A
I
would
definitely
work
with
libor
on
ecosystem,
since
he
is
tied
directly
to
web
hooks,
integrations
and
see
how
that
might
all
work
out,
and
then
you
know
I'm
looking
for
different
ways
that
we
might
bring
those
web
hooks
into
the
view
with
audit
events.
I
haven't
explicitly
settled
on
any
one
of
these
in
particular,
yet
dividing
it
up
between
tabs
one
area
that
I
kind
of
liked
was
perhaps
instead
of
buying
like
multiple
web
hooks,
just
a
singular
web
hook
that
we
can
show
its
status.
A
A
A
The
way
that
we
were
coming
together
on
a
decision
of
like
what
we
could
test
next
was
around
making
protective
branches
more
like
a
blunt
hammer,
so
I'll
visualize,
this
probably
sometime
next
week,
but
more
or
less,
only
being
able
to
configure
like
a
default
set
for
protected
branches
at
the
group
level,
not
for
a
specific
protective
branch,
but
for
just
any
protective
branch
you
can
maybe
set
a
bare
minimum
like
you
require
it
to
be
at
least
maintainers
or
something
I'm
not
being
able
to
go
below
whatever
set
the
group
level
and
then,
as
an
mr
approval
rule.
A
And
lastly,
I'm
going
to
be
shopping
around
some
issues
that
I
had
worked
on
in
design
that
don't
directly
tie
to
us.
So
a
great
example
of
this
is
the
project
deletion
experience.
We
did
help
with
this
in
the
past.
It's
not
directly
compliance
related,
so
I'm
gonna
be
looking
around
some
other
teams
and
seeing
if
they
might
be
willing
to
take
this
on
honestly,
this
might
be
a
great
candidate
for
a
hackathon.