►
From YouTube: Dev:Manage/Plan/Ecosystem UX Design Review 2022-02-07
Description
Weekly design review for Manage, Plan, and Ecosystem
B
So
yeah
so
right
now,
just
a
little
bit
of
background.
The
workspace
workspaces
initiative
is
still
a
couple
years
off,
but
I
think
a
lot
of
people
have
been
asking
to
sort
of
see
a
rough
visualization
of
potentially
how
some
of
these
concepts
within
workspace
will
work,
and
so
I
just
wanted
to
sort
of
lay
out
one
of
these
concepts,
which
is
switching
between
different
workspaces.
B
So,
as
I
say,
this
is
a
one
or
two
years
out,
but
I
just
want
to
dive
into
a
quick
prototype,
and
what
I'm
interested
with
this
in
particular,
is
how
I
may
be
able
to
potentially
improve
the
way
that
I
communicate
these
concepts
to
other
people,
since
it
seems
that
some
of
the
the
ways
that
I'm
communicating
this
stuff
currently
isn't
necessarily
sticking.
So
if
you
don't
understand
anything,
that's
a
good
thing.
Bring
it
up,
tell
me
and
I'll
try
and
fix
it.
A
B
What
what
I
I
mean,
it's
just
an
abstract
thing:
basically,
the
difference
between
workspaces
and
name
spaces.
All
these
just
there,
a
lot
of
it,
I
think,
is
to
do
with
terminology
information
architecture,
how
things
fit
within
one
and
within
each
other.
So
I
don't
want
to
go
into
too
much
more
depth
because
of
that
potentially
made
bias
like
the
the
way
that
you
interpret
this
stuff.
So
maybe
maybe
we
can
discuss
that
after
I
just
sort
of
give
you
a
quick
pitch.
B
B
B
I
have
been
invited
as
a
contractor
from
otherco
and
I've
been
invited
to
get
lab
to
see
currently
what's
going
on
within
gitlab's
workspace,
gitlab's
workspace,
currently
basically
equivalates
to
what
is
equivalent
to
what
gitlab
org
is
today.
So
the
sort
of
all-encompassing
sum
of
contents
that
gitlab
is
working
with
and
that
spans
across
the
entire
devops
life
cycle
and
well
as
as
this
contractor,
I
can
switch
between
different
workspaces.
B
B
So
I'm
dif
by
switching
between
these
workspaces,
I'm
switching
between
different
scopes
of
organizations
that
I
belong
to,
and
I
can
also
potentially
just
aggregate
all
those
things
together.
I
don't
know
whether
this
would
be
performant
enough,
but
there's
the
potential
to
basically
say
here
is
all
the
content
that
I
have
access
to.
Let
me
look
through
that,
so
I'm
going
to
pause
there
and
see
if
anyone's
got
any
questions,
comments,
concerns.
D
D
I
also
wonder
up
in
the
top
left
where
the
menu
actually
drops
down,
if
that
can
actually
also
the
way
that
that's
visually
set
up,
which
is
you
know,
public
namespace
is
that
could
be
a
educational
opportunity
as
well.
So
it
sort
of
lends
itself
to
saying
that,
like
almost
like
a
breadcrumb
right
and
you're
using
that
first
part
as
a
variable
to
change
that
breadcrumb,
I
wonder
if
that
was
intentional,
and
if
not,
could
we
make
that
intentional.
B
Yeah,
so
I
think
some
of
the
challenges
that
that
gitlab
have
is
has
is
from
that
having
nested
namespaces
within
each
other,
so
I
think
making
the
breadcrumb
potentially
a
little
bit
more
prominent
within
our
within
our
ui
is
probably
a
good
idea,
and
I've
been
looking
at
some
competitors
and
azure
devops.
Actually
does
this
quite
nicely
as
we
can
see
sort
of
right
here.
B
That's
a
workspace!
That's
a
project!
These
are
like
the
features
as
well.
So
I
actually
quite
like
that
quite
a
bit
because
it
sort
of
conveys
where
you
are
a
lot
more
a
lot
more
easily.
We
have
a
bread
get
crumb
currently,
but
I
think
we
could
probably
beef
up
that
functionality
and
and
make
it
slightly
more
prominent
as
a
navigation
tool.
D
It's
almost
like
you
could
sorry
daniel.
I
interrupt
you
again.
It's
almost
like
you
could
make
the
bread
crumbs
instead
of
clicking
on
it,
to
go
to
where
that
parent
is
in
the
breadcrumb.
You
could
almost
make
it
a
drop
down
so
that
you
could
sort
of
create
variables
in
this
steps.
I
I
know
it
would
get
maybe
difficult,
especially
if
you're
very
nested
in
in
the
breadcrumb,
but
at
the
top
level
it
could
almost
make
sense
as
well.
A
I
do
also
think
that
the
the
top
placement
where
you
have
it
really
helps
with
the
current
navigation,
because
we
have
that
your
groups
or
your
projects,
the
top
in
that
area
anyways,
which
is
kind
of
bulky
and
cumbersome
and
not
really
well
executed.
I
think
this
kind
of
can
help
that,
by
reducing
some
of
that
clutter
or
confusion,
but
probably
obviously
have
to
validate
it.
B
Yeah
yeah
and
there's
some
more
more
work.
That
needs
to
be
done
with
this
like
on
how
it
would
actually
function
with
the
namespaces
that
live
within
this
particular
workspace,
but
yeah.
That's
basically
where
I
am
today
a
little
bit
of
the
thinking,
any
other
sort
of
feedback
on
potentially
the
pitch
and
how
that
could
be
refined.
D
I
you
called
out
sort
of
a
time
span.
I
think,
is
super
important
as
given
the
context
that
I
have
with
this.
I
think
that
there
are
some
people
that
don't
understand
the
how
long
of
a
timeline
of
change
this
is
and
where
that
what
is
the
work
that
you're
doing
now
fall
in
that
plan.
I
know
you're
kind
of
getting
pulled
in
a
couple
of
directions.
D
Obviously,
people
who
are
asking
for
like
phase
one
phase.
Two
work
are
like
those
who
expect
to
be
more
affected
by
these
changes
more
in
a
timely
manner
versus
that
sort
of
long-term
vision
thing.
So
I
love
the
reiteration
of
the
time.
I
I
think
it
there
there's
a.
There
are
members
of
the
audience
of
workspaces
that
when
you
mentioned
about
two
years,
that
would
blow
their
mind.
They
had
no
idea
that
that
was
like
we're
actually
talking
about
long
long
term
changes
here.
D
B
B
B
One
is
refining
the
settings
and
how
we
cascade
settings
down
from
workspace
to
nested
namespaces
and
then
the
final
one.
Is
this.
This
workspace
type
thing
which
is,
which
is
a
lot
further
out,
so
the
the
number
one
priority
for
me
and
and
the
rest
of
the
workspace
team
at
the
moment
is
merging
together
projects
and
groups.
So
that
is
a
little
bit
lower
level
with
regards
to
this,
but
it's
yeah,
it's
sort
of
occupying
my
head's
base
at
the
moment.
B
Correct
yeah,
so
the
first
so
we're
the
the
the
engineering
team
is
sort
of
chopping.
This
up
to
into
a
number
of
phases
right
now.
Most
of
the
changes
are
happening
on
the
back
end
and
you
won't
be
able
to
notice
anything
that's
happening
and
then
they'll
get
to
a
point
where
we
start
to
try
and
merge
together
the
functionality
of
projects
and
groups,
and
what
we'll
try
and
do
is
try
and
keep
it
consistent
as
possible.
B
But
there
is
inconsistency
between
projects
and
groups
that
we
need
to
figure
out,
so
that
will
have
to
be
done
on
a
feature
by
feature
basis
and
that's
something
that
I
can
support
with.
But
each
team
will
also
need
to
sort
of
contribute
to
that,
because
it's
basically
looking
at
the
entire
product
of
git
lab.
A
B
D
E
D
A
I
think
also
one
thing
to
add:
not
so
much
solicit
information
or
feedback
from
the
ux
team,
but
using
these
little
blurbs
or
walk
throughs
or
office
hours
or
whatever
you
want
to
do
with
it
to
the
product
group
or
the
product
channel
to
the
wider
organization.
You
might
get
more
varied
feedback,
probably
more
targeted
in
terms
of
like.
Oh,
my
god.
What
is
this
going
to
do
to
my
customer?
Xyz
and
you'll
probably
get
some
really
good
feedback
that
way.
D
I
do
just
a
quick
one.
You
will
see
yet
another
new
face
in
these
meetings.
Sasha
eggenberger
is
here.
Finally,
today
is
his
first
day.
I
thought
we
would
do
just
a
little
round,
robin
just
so
come
off
mute
and
whoever
wants
to
sort
of
introduce
themselves
and
tell
them
what
you
do
here
and
how
long
you've
been
here
and
any
other
icebreaker
questions
that
you'd
like
feel
free.
F
Sure
dude,
I
can
so
yeah
my
name's
sasha
I
joined
today
this
morning
so
like
already
created
my
first
merch
request
and
yeah,
I'm
I'm
fully
into
the
onboarding
issue,
walking
through
I'm
34,
I'm
based
in
zurich,
switzerland
and
yeah
I'm
about
to
becoming
a
dad
in
april.
So
I'm
really
looking
forward
for
that
as
well
and,
of
course,
the
start
at
gitlab
I
was
so
excited
and
now,
finally,
the
day
is
here
and
yeah,
I'm
also
I'm
a
designer
for
quite
a
long
time.
F
You
know,
like
the
the
obvious
things
to
do
in
switzerland,
where
we
have
like
the
mountains
and
I'm
a
big
runner.
So
I
do
like
three
to
four
runs
a
week.
I
already
did
one
today
and
yeah,
and
otherwise
I'm
also
involved
in
the
drupal
open
source
project.
So
whenever
I
have
time,
I
contribute
to
drupal
both
design
and
code,
I'm
also
a
core
maintainer
of
drupal
and
I'm
the
the
maintainer
of
the
design
system
and
the
creator
of
the
new
admin
theme
which
might
be
out
with
drupal
10..
A
G
G
Yeah
we
have
good
pizzas,
I
just
eat
pizza
every
day,
no,
not
really,
but
yeah
and
hot
dogs.
Clara
says.
What
do
I
like
to
do?
I
swam
for
like
20
years
competitively.
So
like
that's
one
thing
I
just
started
doing
again.
So
that's
you
know
just
super
fun.
Otherwise.
What
else
do
I
like
to
do?
Make
my
own
perfume?
I
feel
like
I'm
way
less
active
than
you
sasha,
but
you
know
I'm
getting
there.
What
about?
Who
else
is
here?
Nick.
B
Hi
yeah
nick
post,
based
in
bristol
and
the
uk,
with
regards
to
like
london,
that's
like
a
couple
hours
by
train
or
car,
the
south
west-
I
I
was
actually
just
in
switzerland
for
the
last
few
weeks
in
green,
which
is
the
french
side,
but
I
was
doing
some
snowboarding.
There
was
one
of
my
my
favorite
hobbies.
I
also
enjoy
reading
I've
been
in
gitlab
for
a
couple
of
years.
B
E
E
E
D
E
A
A
If
my
computer
would
stop
loading
where
the
you
would
have
more
of
this
a
little
developer
bubble.
We
currently
have
that
visual
doesn't
really
say
anything.
It's
not
a
hover,
but
now
the
idea
is
that
we
would
have
it
manifest
different
versions.
So
I
have
like
direct
membership
or
inherited
membership
or
shared
membership,
which
is
the
third
option
and
I
differentiate
it
by
having
little
icons.
A
D
B
Yeah
I
I
like
I
like.
I
think
this
is
super
useful
and
it's
also
really
useful
for
some
of
the
stuff.
That's
happening
with
name
spaces
and
and
nested
things
as
well.
So
definitely
definitely
welcome
and
it'll
be
useful
to
update
pajamas
docs
with
with
potentially
some
of
the
use
cases.
Maybe,
but
I
yeah
I
like
the
icons
I
especially
like
the
inherited
icon.
B
That's
I
think
that
that
one's
really
clear
that
it's
sort
of
a
nested
one,
I
think
the
share
one
to
me
jumps
out
is
more
of
like
an
action
like
the
the
share
thing.
So
I
think
I
would
prefer,
like
potentially
the
metaphor
of
a
of
a
chain
linking
together
to
projects
or
groups
or
something
like
that.
But
that's
my
that's
just
my
perspective.
Maybe.
A
Yeah,
I
I
wasn't
confident
with
the
share
icon
because
it
like
from
experience.
It
looks
like
an
action
share,
but
that's
you
know
when
you
look
through
our
component
library,
that's
the
share
icon,
so
I
just
use
it
as
a
reference.
I
don't
know
if
that's
an
opportunity
for
us
to
offer
feedback
on
the
icon
itself
in
terms
of
the
greater
use
across
the
environment,
but
I
do
also.
B
We
have
subsets
within
within
our
icons
like
we
have
status
icons.
We
have
trend,
icons
and
things
as
well,
so
potentially
there's
an
opportunity
here,
since
it's
it's
happened
so
often
across
get
lab
to
convey
inheritance
or
parents
or
children
or
linking
in
some
way
as
well.
Maybe
there's
like
a
ia
icon,
set
that
we
could
that
we
could
create
or
contribute
to.
A
Yeah,
so
currently
there
is
no
tooltip,
so
we
do
have
cases
of
a
badge,
but
it
doesn't
appear
everywhere,
and
it
doesn't
also
give
you
any
information.
It
just
says
developer
whatever
your
role
is
so
there
is
a
problem
where
sometimes
people
don't
know
where
their
permission
came
from
or
what
their
access
level
is
at
that
environment.
So
having
that
visual,
since
we
already
have
it
in
some
cases,
just
expand
on
that
feature
and
say
it's
actually,
all
these
other
groups
or
projects
you
have
access
to.
G
So
it's
it's
telling
you
where
you
like
how
you
access
this
versus
like
what
it
is
like.
I
think
what
I'm
getting
at
is.
Are
you
ever
going
to
tell
the
user
what
it
means
like
how
they
can
contribute?
I
think
that
that
might
be
what
I
would
expect
like
when
I
hover
over
it.
It's
like
what
does
developer
mean?
Does
that
mean
I
can
post
in
this
or
that
I
could
view
issues
or
you
know
stuff
like
that
or
like?
Maybe
it
could
be
a
pop-over
yeah.
A
G
A
Would
a
link
like
if
you
clicked
on
the
bubble,
with
a
link
to
the
docs
help
so
it'll
jump
to
developer
documentation
and
say
this
is
what
developer
does
or
maintainer
or
whatnot,
because
I
don't
want
to
take
them
out
of
the
flow
of
the
work
that
they're
doing
or
perhaps
it'd
be
like.
Like
I'm
curious,
if
there's
a
way
to
not
impact
their
flow
as
much
as
having
to
go
external
from
the
screen
so
like
having
an
overpopulated
tool
tip
with
the
docks
might
be
problematic.
A
G
It
could
be,
I'm
thinking,
maybe
like
maybe
you
could
test
out
like
docs
or
like
a
pop
over
or
a
tool
tip
with,
like
really
short,
it'd,
probably
be
like
a
pop
over
something
like
that,
but
maybe
test
it
out.
I
guess
and
see
what
people
expect,
but
I
agree:
yeah,
like
you,
wouldn't
necessarily
want
to
be
taken
somewhere
else,
just
to
understand
what
that
information
is,
but
it
kind
of
sounds
like
this
should
be
a
global
pattern
as
well.
Do
we
we
might
not
have
that
like
learning
more
about
this
developer
badge
right.
B
Yes,
this
is
a
problem
sort
of
similar
a
little
bit
to
some
of
the
stuff
that
we
had
in
in
value
stream,
analytics
where
people
didn't
really
know
what
the
metrics
were.
So
we
used
a
pop
over
and
gave
like
a
brief
snippet
of
what
it
meant
and
then
also
linked
to
the
docs
as
well.
So
I'll
share
an
example
of
that
in
the
agenda,
then.
B
B
A
A
So
evan
created
this
really
nice
mural.
I
received
a
mermaid
doc.
That
kind
of
shows
this,
where
you
have
the
the
hierarchy
or
the
way
that
membership
is
assigned
or
inherited
or
how
you
get
access
to
it,
and
so
this
is
what
they
were
going
to
include
in
the
documentation.
So
that's
kind
of
helpful.
I
thought
it's
not
as
colorful
as
the
one
that
I
had
started
with
earlier
this
one,
which
is
the
early
version,
but
but
yeah.
This
is
what
they're
going
to
be
using
for
the
documentation.