►
From YouTube: Compliance: UX Office Hours (2021-11-19)
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.
This
is
a
shorter
week,
just
with
get
loud,
contribute
being
on
tuesday
and
wednesday.
So
just
got
a
few
agenda
items
that
I
thought
would
be
useful
to
share
with
others.
I'm
still
working
pretty
heavily
on
our
community
contribution
to
add
a
merge
method
across
all
the
different
layers
of
git
lab.
A
First
of
all,
I
apologize
because
I
think
I
sent
several
recordings
out
expressing
confusion
only
to
have
realized
this
week
that
I
was
on
an
old
get
pod
instance,
which
is
why
I
should
explain
why
nothing
seemed
to
be
changing
for
the
better.
But
I
checked
out
a
new
branch,
fresh
instance
on
gitpod.
It
seems
to
be
behaving
more
expectantly
it
just.
A
I
think
there
are
some
components
of
the
cascading
settings,
implementation
that
can
lead
to
some
unexpected
consequences,
but
not
necessarily
ones
that
are
detrimental
to
the
product.
It's
just
maybe
not
going
to
do
as
much
as
you
would
hope.
A
But
with
that
said,
I'm
working
on
writing
some
documentation
pages.
There
haven't
been
any
doc
changes
to
the
merge
request.
Change
so
I'm
working
with
evan
on
that
and
yeah,
hopefully
we'll
get
that
I'll
get
a
little
bit
closer.
I
think
there
needs
to
be
a
database
review
as
well.
A
The
next
thing
I
want
to
say
is:
we
got
a
design
issue
open
for
redesigning
the
personal
credentials
inventory,
so
this
this
ties
more
to
what
jeremy
is
going
to
be
taking
on
as
a
personal
kr.
So
one
of
the
redesign
he's
doing
five
redesign
sessions,
and
I
acknowledge
some
areas
I'd
like
to
see
addressed
and
why
this
would
be
beneficial.
A
A
Nick
post
and
I
had
a
good
sync
meeting
earlier
this
week-
some
topics
of
conversation
where,
with
features
that
we
have
in
the
admin
area
as
we're
considering
their
future
destination,
we've
always
talked
about
bringing
them
into
sas.
So
taking
something
out
of
the
admin
area.
Where
does
it
go
from
there,
perhaps
into
a
namespace
or
the
workspace
container
itself
will
be
the
ultimate
destination?
A
What
we
really
need
to
probably
aim
for
is
identifying
that
hey
we're
not
going
to
necessarily
do
any
lifting
and
shifting
right
now
we're
going
to
focus
on
other
problems,
and
then
we
will
put
an
effort
to
help
relocate
features
that
we
are
directly
responsible
for,
like
the
credential
inventory
in
the
admin
area
or
like
audit
events
and
making
sure
that
they
work
more
seamlessly
in
this
next
generation
type
of
field
for
git
lab
and
then,
alongside
that,
I
feel,
like
I've,
gained
a
good
level
of
empathy
for
some
of
the
struggles
that
come
with
settings
inheritance.
A
So
I'm
going
to
record
a
few
sessions
just
to
help
provide
context
of
what
makes
gitlab
difficult
to
manage
in
terms
of
its
settings
and
how
to
configure
things
and
where
they're
located
to
hopefully
help
illustrate
a
problem
that
ideally
workspace,
can
help
solve,
or
perhaps
even
the
ecosystem
stage
with
foundations
taking
on
responsibility
for
navigation
and
settings
probably
be
some
collaboration
across
those
stages.
But
I
want
to
help
try
and
put
us
in
the
right
direction
there
just
kind
of
hearing
what
nick's
thinking
and
what's
coming
out
of
the
pipe
so
yeah.
A
If
you
may
see
on
this
video
sorry,
my
fans
are
loud,
got
gdk
and
a
video
recorder
going.
So,
of
course,
it's
getting
angry,
maybe
two
fun
things
that
I
failed
to
do
well
this
week,
I
tremendously
failed
to
like
create
a
patch.
A
I
don't
know
how
you
guys
create
patches
like
a
git
patch,
completely
destroyed
the
get
pod
that
I
was
in
took
me
a
while
to
recover
that
and
then
on
the
flip
side,
I
was
trying
to
do
like
a
demo
of
how
I
get
mini,
cube
running
and
configured.
So
I
could
run
terminal
in
my
web
ide
in
gitlab
and
also
completely
destroyed
my
gdk.
So
there
are
two
fun
failures
for
the
week.
Happy
friday,
everybody.