►
From YouTube: Compliance: UX Office Hours (2021-08-06)
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
here
at
gitlab
working
in
the
compliance
group.
I
just
wanted
to
share
a
few
cool
things
from
this
week
that
I
was
working
on.
I
mean
I
was
mostly
digging
into
trying
to
figure
out
how
specific
things
were
working
in
gitlab
today,
reading
a
lot
of
documentation
and
features.
A
A
I
won't
cover
all
that
I
did
want
to
do
a
special
highlight
of
this
neat
little
app
that
one
of
our
design
managers
built
out
over
the
last
couple
weeks
on
the
side
it's
available
here
in
git
lab
it's
not
officially
sponsored
by
gitlab
by
any
means
it's
more
of
just
like
a
side
project
if
you'd
like
to
try
it
out,
but
it's
it's
pretty
neat
so
I'll
give
you
a
demo
of
how
it
works.
For
me,
I
can
open
up
this
little
widget
bar
on
my
desktop
and
it's
get
lab
icon.
A
It
shows
you.
My
recent
commits
the
issues
that
I've
been
looking
at
recently.
My
projects
that
I
work
in
and
my
comments
that
I've
left
recently
and
a
number
of
bookmarks,
so
this
saved
me
saves
me
a
few
things
like
normally.
I
have
a
folder
with
bookmarks
that
I
always
jump
into
for
specific
things
and
that's
great.
I
don't
have
to
keep
track
of
those
bookmarks
there
anymore.
A
I
also
am
constantly
jumping
to
my
activity,
feed
to
try
and
figure
out
like
where
I
left
the
comment
recently,
because
that's
usually
my
like
logical
way
of
thinking
what
I
was
doing
last
so,
if
someone's
asking
me
a
question,
that's
usually
my
fastest
way
to
find
it,
but
this
gives
me
one
less
bookmark
to
keep
in
my
browser
and
then
I
also
love
this
recently
viewed
piece.
A
I
encourage
you
to
check
it
out
if
you're
interested
I've
got
an
upcoming,
ux
showcase.
I
volunteered
to
do
one
on
august
18th.
So
if
you're
interested
I'll
make
sure
that
that
gets
sent
to
you,
it's
going
to
be
on
it's
never
too
late
to
pivot
and
the
subject
we're
going
to
I'm
going
to
be,
covering,
as
an
example,
will
be
how
we
implemented
status
checks.
I
think
we
did
a
phenomenal
job
pivoting
when
we
needed
to
specifically,
we
had
already
started
building
out
functionality.
A
We
were
integrating
with
the
way
that
you
could
currently
add
approval
rules,
and
then
we
learned
a
good
bit
from
the
code
review
group
about
that
teacher's
intent
and
we
pivoted
away
like
front
end
was
pretty
upfront
of
saying:
hey.
This
we'd
rather
pay
the
debt
down
now,
and
I
want
to
highlight
how
good
that
was
and
talk
about
the
outcomes
that
we
got
to,
because
I
think
what
we're
seeing
now
is
a
better
feature.
That's
integrated
into
a
more
consistent
part
of
the
application.
A
So,
with
the
merge
request
report
component
being
built
out,
it's
going
to
be
even
better
then,
and
we
have
a
nice
road
map
where
we
think
we're
going
to
go
with
it
and
we're
already
hearing
great
feedback
on
the
features.
So
it's
just
a
win
all
around
it's
something
worth
showcasing
and
yeah.
Lastly,
I
talked
a
lot
about
this
at
the
beginning
of
the
video,
but
this
is
why
I
spent
a
lot
of
time.
Digging
into
this
week
was
really
thinking
through
all
the
different
edge
cases
around
default
branch
protections
man.
A
A
It
was
built
and
sometime
at
the
end
of
version
12,
beginning
of
13,
that's
before
I
even
joined
git
lab.
So
you
know
we
find
things
and
I
think
it's
going
to
give
us
some
points
to
pivot
in
this
ideation
phase,
which
is
fine,
we're
just
gonna
figure
out
how
we
can
make
it
all
work
together
and
have
a
more
seamless,
ux
experience.
We
know
the
problems
that
we
need
to
solve.
It's
just
a
matter
of
making
sure
it
actually
will
work
nicely
with
our
ui
and
I'll
stop.
There.