►
From YouTube: Dev:Manage/Plan/Ecosystem UX Design Review - 2021-03-23
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
Pass
this
one
off:
oh
maybe
I
think
daniel
joined
as
you
were,
on
that
one
austin.
Oh
yeah,
yeah
now
he's
got
a
point
there
talking
about
settings
inheritance.
B
Thank
you
just
so
to
follow
up
how
I
was
kind
of
agreeing
with
you
like
I'm,
specifically
intentionally
moving
like
with
diligence
and
care
before
just
saying.
Oh,
I
have
an
iterative
solution
because
so
many
of
us
been
doing
this
working
on
this,
I'm
hoping
we
can
come
to
like
a
more
cohesive
like
direction
or
statement
or
project
agenda,
or
maybe
just
we
can
work
easily
and
design
an
epic
and
say
we've
come
to
this
proposal
where
we're
going
to
start
doing
it
this
way
or
think
about
it.
C
D
C
C
I
thought
it
was
kind
of
hard
to
just
tie
everything
together
with
an
epic,
so
I
was
starting
with
the
merch
request.
That
was
like
a
sentence
long
because
that's
pretty
easy
to
shut
down.
If
it's
not
good,
so
I
think
your
idea
is
great
and
I
think
if
you
just
drop
some
of
that
feedback
in
the
merge
requests,
we
can
continue.
This
conversation.
A
C
C
I
think
the
tl
dr
for
him
was
like
don't
try
and
create
feature
parody
across
the
different
levels
of
gitlab,
where
his
was
his
opinion,
but
then
that
makes
it
difficult
when
we
have
to
solve
immediate
customer
problems,
so
just
trying
to
figure
out
those
complexities.
B
I
think
maybe
this
the
work
we're
doing
in
access
might
address
the
statement
of
not
try
and
do
feature
parity,
because
I
think
the
way
that
we're
thinking
about
it
is
having
it
tied
to
this
top
level.
Namespace
object
or
top
level
group
object
that
we've
been
trying
to
work
on,
and
so
the
idea
is
that,
if
the
behavior
attaches
to
that
object,
then
the
logic
would
flow
down
from
that
so
you're
not
necessarily
trying
to
bring
parity
between
different
environments.
You
know
the
self-managed
or
the
dot-com,
or
anything
like
that.
B
C
Sure-
and
I
think
that's
maybe
why
it's
mostly
a
pain
point
for
me-
is
like
we
have
customers
and
end
users
that
are
asking
for.
I
want
to
be
able
to
configure
protected
branches
at
the
group
level
and
have
those
inherited
by
my
projects,
which
is
supposed
to
be
kind
of
resolved
by
the
working
group,
to
simplify
that
whole
model.
D
B
It's
either
yes,
no
or
true
false
within
the
environment
versus
define
a
protected
branch
within
particular
projects
or
groups
and
associated
to
whatever
you
know,
pass
fail
scenario
or
things
like
that.
Maybe
I'm
not
thinking
about
it
correctly.
C
Yeah,
no,
I
think
they
could
be
substitutable,
so
I'll
use
autodevops
to
take
it
away
from
both
of
our
own
workspaces
should
autodevops
be
something
that
is
automatically
inherited
and
enforced.
It
is
an
on
off
thing,
there's
no,
like
specific
configuration,
should
it
be
inherited
by
all
projects
by
all
groups
and
enforceable
by
default.
C
C
So
I
think
the
answer
I
was
first
trying
to
understand
is:
what
is
our
pattern
that
we
default
to
once?
I
know
that
pattern
then
I
could
be
like
yeah
cool.
I
can
see
how
daniel's
toggle
helps
solve
a
problem
that
is
exposed
by
the
pattern
and
it
might
be
for
more
unique
settings
rather
than
all
of
them,
but
I
think
the
first
thing
to
do
is
define
the
pattern,
so
we
at
least
have
a
north
star.
B
E
B
Various
patterns
like
what
I
was
mentioning
earlier
or
last
week
about
right,
the
the
vocabulary
or
the
way
that
things
are
written,
that
I
think
that
can
also
help
define
a
lot
of
the
behavior
of
the
feature
by
saying,
if
you
write
it
a
certain
way,
it
has
one
interpretation:
if
you
write
it,
some
other
way,
it's
totally
interpreted
in
a
different
way
does
not
necessarily
apply
to
what
you're
describing,
but
it
kind
of
ties
to
what
you're
saying
about
patterns.
B
C
No,
there
hasn't
been
a
dedicated
research
effort.
I
would
say
the
only
thing
that
I
can
tie
back
to
it
is
for
more
compliance,
focused
customers,
the
ones
that
ask
for
more
compliance
related
features,
they're
the
ones
that
speak
up
most
vocally
about
specific
compliance,
settings
or
related
settings.
C
C
A
E
D
E
Oh
does
mike
own
this
meeting.
I
bet
he
does
because
I
can't
share
my
entire
screen
I'll
copy
this
over.
So
I'm
just
kind
of
exploring
road
maps
right
now
and
I'll
try
to
keep
this
short.
Because
I
see
we
have
other
things
on
the
agenda,
but
basically
our
road
maps
aren't
very
performant
right
now
and
I
think
that's
you
know
due
to
a
few
different
problems,
but
one
of
them
is
just
the
sheer
number
of
things
that
get
loaded
into
a
roadmap.
So,
for
example,
worst
case
scenario
or
best
case
scenario.
E
I
guess
how
you
look
at
it
at
gitlab.
You
know
we
have
a
lot
of
epics
and
when
you
enter
a
roadmap,
it's
basically
loading
in
every
single
epic.
Until
you
start
filtering
there
narrowing
it
down,
so
we
start
really
broad
instead
of
narrow
and
then
you
can
basically
scroll
over
infinity
to
like
any
point
in
time.
So
I
could
scroll
back
you
know,
years
and
years
and
years
here
and
as
I'm
scrolling,
it's
loading
in
more
epics.
E
As
I
scroll
down,
let's
say:
if
I
hadn't
filtered
it,
would
it
would
load
in
more
epics
as
well.
So
one
step
forward
towards
making
the
red
map
more
performance
and
then
also
really
allowing
users
to
kind
of
focus
on
in
on
the
data
or
the
epics
they
care
about.
One
thing
we're
thinking
is,
we
could
add
basically
a
way
to
pick
dates.
E
So
that's
something
I'm
exploring
right
now
and
something
I
encountered
here
is
that
it
gets
a
little
strange
because
our
columns
are
pretty
set
based
on
week
based
on
the
kind
of
segment
you've
chosen.
So
if
I
choose
like
weeks
here,
each
column
will
be
a
week
they're,
not
dynamic.
E
They
just
kind
of
load
more
in
as
you
scroll.
So
I
think
that
would
be
something
interesting
to
look
at
and
some
of
the
issues
that
was
causing
me,
for
example,
was
when
I
was
looking
at
how
we
could
perhaps
like
add
a
date
picker
in
here
there'd,
basically
be
these
big
empty
states
on
the
roadmap.
So
I
looked
at
different
dates.
E
We
could
possibly
allow
a
user
to
pick
and
for
mvc
I
was
thinking
we
just
give
them
kind
of
sensible
defaults
instead
of
allowing
them
to
pick
whatever
date
they
want,
because
that
could
cause
some
like
validation
issues.
So
just
picking
a
few
seems
like
a
good
default
and
I
just
explored
a
few
different
ones
here
and
what
that
could
mean
by
like.
So
let's
say
I,
my
time
frame
is
a
month.
What
would
that
look
like
if
I
tried
to
segment
it
by
those
different
those
different
like
views?
E
We
give
users
up
here
right
and
it
got
kind
of
weird.
So
I
explored
this.
So
let's
say
I
want
to
see
a
month
segmented
by
quarter.
I
have
this
big
empty
state
here,
because
I'm
looking
at
quarter,
columns
and
they're
set
they're,
not
dynamic.
E
If
I
want
to
see
let's
say
a
month,
segmented
by
month,
you're
just
going
to
see
like
one
column
and
then
a
bunch
of
just
emptiness,
whatever
the
emptiness
looks
like
if
you
want
to
see
let's
say
three
years
of
data
segmented
by
week,
you're
going
to
get
this
big
road
map
that
you
have
to
scroll,
and
maybe
you
only
have
like
five
epics
on
there.
You're
you're
scrolling
a
large
amount.
E
So
I
thought
about
like
what
it
would
look
like
if
the
roadmap
columns
were
more
dynamic
based
on
like
the
views
you
picked
or
maybe
we
could,
you
know
default
it
to
what
we
think
makes
sense.
It
looks
something
more
like
this,
so
if
I
want
to
see
this
quarter
segmented
by
quarter,
you
just
see
like
a
quarter
right
a
a
year
segmented.
E
I
was
thinking
for
nbc
if
you
wanted
to
just
give
users
a
few
different,
like
I
said,
sensible
defaults
of,
like
you
know,
quarter
year
within
three
years,
something
like
that.
What
we
could
potentially
do
is
basically
just
take
away
any
of
those
states
that
were
had
like
an
empty
state
within
them.
E
And
let's
say
if
I
picked
a
quarter,
because
there
was
those
strange
empty
states
I
showed
for
viewing
by
month
or
week
or
quarter
there.
We
just
allow
them
to
see
by
week
within
they're
in
the
when
they're
within
the
quarter
view,
and
so
basically
they
have
like
six
view
options
here.
E
So
it
gets
a
little
kind
of
finicky
right
so,
like
only
when
I'm
within
three
years
can
I
see
all
the
different
view,
options
and
talking
with
the
pms
as
well
like
they
want
more
than
three
years
so
again,
this
is
just
kind
of
like
me
ideating,
but
they're
like
oh.
I
want
10
years
of
data.
E
That
would
be
useful
for
me
to
see
within
the
roadmap.
I
don't
want
just
three
years
so
I
mean
maybe
the
follow-up
could
either
be.
They
have
their
own
date
paper
here,
like
I
said,
maybe
we
have
more
brush
and
zooming
dynamic
roadmap.
E
I've
seen
that
in
other
products,
like
roadmap
or
roadmap,
has
something
like
this
that
I
kind
of
like,
where
kind
of
like
I
was
saying
where
the
viewport
is
kind
of
set
you're,
not
scrolling
you're,
just
kind
of
zooming
in
in
and
out
most
roadmaps.
I
see
have
like
a
couple
years
of
data.
I
think
it's
like
four
and
you
can
scroll
and
like
kind
of
how
we
have
like
segment
it
in
different
ways.
E
So
I
don't
know
I'm.
Let's
just
I
just
want
to
show
y'all
what
I'm
playing
with
here,
I
think.
Actually,
the
other
larger
problem
to
solve
is
allowing
users
to
kind
of
like
filter
in
from
the
start,
so
they're
not
starting
broad
they're,
not
coming
into
this
huge
roadmap
of
like
every
epic
ever
maybe
we
have
them
kind
of
like
create,
like
add
in
a
roadmap
creation
flow
where
they're,
maybe
picking
a
few
filters
to
start
off
and
focus
their
view
and
then
maybe
they're
also
kind
of
picking
those
dates
there.
E
But
I'm
thinking
this
is
like
where
I
want
to
go.
Sorry
someone's
talking
and.
E
A
Because
I
was
thinking
really
loudly
about
something
when
you
said
filtering,
I
wonder
if
that
would
make
sense
that
the
timeline
width
is
as
wide
as
the
longest
epic.
E
I
guess
the
only
problem
there
is
some
epics
I
mean.
Maybe
this
is
the
other
problem
to
solve
some
epics
don't
have
a
start
or
due
date.
So
we're
not
opinionated
there
right.
So
then
it's
like
what
does
that
mean?
I
guess
maybe
it'd
be
as
long
as
the
second
or
the
first
epic,
with
the
start
and
due
date.
D
F
E
Yeah,
I
didn't.
I
also
have
the
well
it's
in
the
issues,
but
I
could
explicitly
put
that
there
too.
F
Yeah,
I
think
it
looks
great
I'm
just
kind
of
there's
a
lot
to
take
in
so
I'm
just
kind
of
processing
and
evaluating
so
I'd
love
to
just
comment.
Async
thanks
for
sharing
alexis.
I
always
love
looking
at
your
discovery,
because
you
always
put
in
so
much
just
amazing
visuals
as
part
of
your
your
kind
of
ideation.
I
can
really
see
your
thought
process
and
I
love
that
road.
A
Yeah
you're
exceptional
to
visually
articulating
your
divergent
thinking.
Your
divergence
is
strong
with
this
one
yeah.
C
So
I
just
quickly
pull
a
lot
together
to
try
and
frame
a
problem
and
like
an
idea
for
a
proposal,
and
I
have
it
in
problem
validation.
But
I
was
curious
what
you
all
would
consider
doing
to
go
validate
this
as
a
true
problem
to
solve
or
a
way
to
create,
like
a
direction
for
a
good
solution.
My
initial
thinking
was
just
pull
in
some
of
the
tams
and
have
them
like
talk
about
this
with
a
few
of
the
customers
that
have
ssc
2
audio
requirements.
C
F
F
Who
does
this
see
if
there's
any
sort
of
pattern
to
be
established,
or
if
it's
maybe
is
it
an
industry
thing
is
like
I
worked
at
an
insurance
company
years
ago
as
a
designer,
and
they
had
to
have
everything
because
they
were
audited
frequently,
and
so
maybe
it
depends
on
the
industry
and
also
any
tools
that
they
use
currently
are
methods
that
they
use
currently
to
try
to
solve
this
problem.
In
addition
to
the
screenshots
like
what
do
they
do
with
them,
once
they've
got
them,
did
they
put
them
somewhere?
B
B
This
is
the
perfect
opportunity
to
have
like
an
audit
log
like
okay,
everything
changes
whenever
you
make
a
change
in
the
system,
but
nothing
changes
on
the
front
end.
And
then
you
go
to
the
audit
log
and
you
hit
export
setting
changes
and
it
says
all
the
specific
changes
that
existed
over
time
and
any
changes
to
them.
C
Yeah,
I
think
the
thing
that
can
be
sometimes
hard
to
discern
from
even
a
list
is
what
did
things
look
like
in
april
of
2021,
when
it's
december
of
2021.
you'd
have
to
do
some
reverse
engineering
to
figure
out
what
all
has
changed
since
then.
So
I
think
the
visual
snapshot
in
time
in
some
ways
is
helpful.
C
From
what
I
understand,
it's,
like
auditors,
checking
what
the
configurations
were
like
through
time.
So
specific
points.
Did
you
have
your
mr
approval
rule
set
up
in
this
way,
but
for.
E
That
I'd
be
interested
in
what
daniel
was
saying
then,
because
yeah,
I'm
not
sure
I
would
think
a
list
would
be
helpful
there
too,
if,
like
all
the
configurations,
what
were
you
saying
daniel
sorry,
I.
B
Was
gonna
say
that
perhaps
the
audit
log
would
actually
do
the
screenshots,
for
you
not
actual
screenshots,
but
just
actual
statuses
of
this
is
today's
date.
These
are
the
changes
that
exist
just
like
an
mr
right.
You
have
the
before
and
after
and
so,
and
you
have
an
archival
history
where
you
could
do
a
search
and
a
query
to
say.
B
I
want
to
know
what
the
status
of
the
settings
were
at
you
know
two
years
ago
on
this
date
and
it's
again,
it's
just
all
tied
to
an
audit
log
behavior
which
would
prevent
them
from
having
the
visual
aspect,
because
looking
at
the
visuals
is
totally
irrelevant
for
looking
at,
like
a
folder
full
of
screenshots
you're.
Looking
at
the
title
to
say:
okay,
what
what's
the
title?
How
do
we
organize
a
title
or
the
folder
architecture?
B
F
C
Sure
this
is
totally
back
to
holly's.
Point
like
this
is
just
trying
to
validate
a
problem
to
solve,
so
I
think
there
is
more
time
to
talk
with
customers
and
better
understand.
How
are
they
currently
solving
this
problem
today?
I
think
all
we've
heard
so
far
is
they're,
taking
screenshots
of
their
gitlab
environments,
storing
them
somewhere
and
then
come
audit
time,
handing
those
screenshots
off
to
the
auditor,
so
the
auditor
can
verify
they
have
their
configuration
set
up
in
a
specific
way.
At
a
specific
point
in
time,.