►
From YouTube: Compliance: UX Office Hours (2021-06-17)
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
git
lab
for
this
week's
agenda
item
a
couple
things
to
note.
So
first
thing
that
I'm
pretty
excited
about
is,
I
feel,
like
I
reached
a
solid
decision,
some
great
feedback
from
tech
writing
and
another
designer,
so
michael
ian
evan
both
contributed
really
well
helping
me
think
through
this
problem,
and
so
I
think
we
have
a
nice
way
to
move
forward
on
the
terms
and
service.
A
I
would
really
love
to
see
this
updated
based
off
some
of
michael's
feedback
to
use
more
live
preview
with
a
better
content,
editor,
but
area
of
changes,
so
we'll
start
with
being
able
to
require
when
terms
are
updated.
Next,
I
wanted
to
share
that
the
access
team
is
working
on
group
access
tokens.
So
one
way
you
can
think
about
this
is,
if
you
are
in
a
large
organization-
and
you
have
a
lot
of
projects,
but
you
don't
want
to
create
a
lot
of
project
access
tokens.
A
Next,
I
want
to
share
that.
I
did
get
this
merge
request
in
which
I
was
pretty
proud
of.
I
realized
that
it
seems
small,
but
something
that
we
will
be
seeing
soon
is
a
replacement
of
some
of
these
labels
to
use
better
text.
This
is
directly
tied
to
one
of
the
krs.
We
had
to
learn
how
to
better
write
what
I
copy.
This
was
a
quick
one
that
I
saw
that
I
could
tackle
myself
learned
a
lot
about
arya
described
by
in
screen
readers
look
into
the
merge
requests.
A
I
also
want
to
share
this
automated
workflow
for
propagating
settings,
so
the
one
of
our
teams
at
gitlab
is
creating
automated
scripts
to
enforce
or
overwrite
really
protected
branches
in
a
merge
request,
approval
so
they're
asking
essentially
for
like
a
json
file
to
describe
what
they're,
looking
for
and
then
they're
being
able
to
commit
that
demonstrate
the
changes
and
then
have
the
option.
Also
roll
back,
even
though
we
might
implement
this
exactly.
A
I
really
do
think
this
should
be
something
that
we
conquer
in
the
ui,
and
I
know
we've
been
talking
about
scaling
this,
but
this
would
be
kind
of
like
what
that
json
file
would
look
like
if
we
just
represented
it
in
ui
and
tied
the
functionality
together,
we'll
see
if
we
can
get
some
more
background
and
context
on
like
what
these
types
of
scenarios
are.
Brian
may
brought
this
up
from
the
professional
services
group
as
they
look
to
make
these
types
of
automations.
A
A
Another
cool
thing
that
we'll
be
implementing
with
this
in
the
handbook
so
we'll
be
using
the
right
method
for
better
evaluating
whether
or
not
we
should
proceed
in
a
research
session.
So,
instead
of
trying
to
get
like
five
to
eight
right
off
the
bat
you
just
start
with
three.
If
there
are
no
issues,
you
continue
getting
a
few
more.
If
there
are
issues,
then
go
back
redesign
some
stuff
test
again,
so
that
just
kind
of
reinforces
a
good
principle
in
user
research
and
also
join
a
book
club.
A
If
you're
interested
in
joining
there's
some
more
detail
here,
the
first
date
will
be
on
july,
8th
it's
going
to
be
talking
about
better
onboarding.
This
is
particularly
important
for
the
growth
group,
but
I
also
was
interested
in
learning
more
about
it
so
going
along
for
the
journey
with
that
that
ends
our
chat
for
today.
Talk
to
you
soon,.