►
From YouTube: Navigating namespace - concept
Description
Daniel discusses the concept of navigating namespaces with Michael and Nick
B
Yeah,
so
I
had
started
this
by
doing
some
work
looking
at
the
settings
in
the
admin
page,
because
we
want
to
try
and
bring
parity
between
the
environments
between
the
dot
com
and
the
self-manage
instance,
and
so
through
that
there's
a
lot
of
settings
that
don't
necessarily
overlap.
Hey
nick,
and
so
I
was
saying,
the
settings
in
the
admin
page
has
a
lot
of
things
that
don't
necessarily
make
sense
or
have
context
within
the
com,
environment
and
so
bringing
those
over
obviously
won't
make
any
sense.
B
So
when
we
do
that,
the
idea
would
just
be
to
get
rid
of
those
things,
and
so
one
of
the
things
that
I
was
concerned
about
was
how
that
would
impact
other
groups.
Other
stages-
and
I
know
through
doing
a
lot
of
this
work-
that
you've
actually
done
a
ton
of
work
in
regards
to
the
settings
and
also
nick,
has
done
quite
a
bit
of
research
and
thinking
about
navigation.
B
B
A
Yeah,
so
this
is
the
consolidation
of
the
top
nav.
This
is
something
that
the
editor
group
has
been
looking
at
for
maybe
the
last
month
in
a
bit,
I'm
kind
of
inspired
about
by
nick's
earlier
work
back
in
his
like
explorations
of
different
navigations.
We
saw
this
one
and
thought
it
was
a
good
opportunity
to
consolidate
kind
of
all
the
high
level
items
and
currently
they
all
live
in.
A
They
live
in
the
projects
groups
and
then
this
mysterious
bag
of
more
so
what
we're
really
trying
to
solve
here
is
reducing
the
guessing
of
where
things
live,
and
so
these
are
high
level
objects,
and
so
the
left
nav
will
still
remain.
As
is
oh
well,
the
left
nav
will
still
remain
per
object
area,
but
what
we're
planning
to
do
is
kind
of
consolidate
the
top
three
drop
downs
that
we
currently
have
into
one
big
drop
down.
B
A
They
don't
exist
on
the
left
nav
at
the
moment.
These
items,
these
items
here
all
currently
live
under
the
more
drop
down.
If
you
go
on
your
top
nav
in
gitlab
they'll
be
there
underneath
there
and
then
they'll
be
like
the
admin
wrench
button.
That
appears,
if
you're,
like
an
admin
person
currently
in
the
top
nav,
so.
C
Just
to
clarify
that,
so
when
you
see
milestones
and
when
you
see
things
like
snippets
and
all
that
sort
of
stuff,
those
those
live
at
the
project
level
and
the
group
level,
but
they
also
have
instance
left.
They
also
live
at
the
instance
level
or
the
workspace
level
generally
and
the
top.
The
top
navbar
basically
switches
between
these
containers,
like
projects
and
groups
and
then
the
the
items
that
don't
necessarily
sit
within
a
particular
container.
Like
a
project
or
a
group.
B
C
So
yeah
security
and
compliance,
they
have
features
at
the
instance
level.
They
have
features
at
the
group
level
and
they
have
features
at
the
project
level
and
the
the
ones
that
you
see
currently
in
the
top
nav,
which
you
can
access
from
the
top
now
today
are
the
instance
level
features.
So
this
is.
This
is
sort
of
like
one
of
the
weird
quirks
of
gitlab's
navigation
as
the
these.
These
different
buckets
and
I
realized
that
I've
just
started
it.
B
B
This
idea
of
these
global
settings
that
I
was
thinking
about
would
attach
the
top
level
these
sorts
of
things
that
don't
necessarily
make
sense
being
specifically
at
a
a
group
or
a
project
or
a
subgroup
that
kind
of
idea
that
it
then
moves
to
this
new
area
of
get
lab,
that
we
haven't
fully
envisioned
or
actualized
yet
so
that's
sort
of
where
again,
like
I
go
back
over
here.
So
thinking
about
these
things,
while
looking
at
the
admin
screen.
B
These
were
the
initial
feature
settings
that
were
in
the
admin
screen,
but
then
I
didn't
really
think
about
this
security
object.
So
I
wanted
to
go
back
and
look
at
that,
but
you're
saying
if
we
want
to
use
this
new
drop
down
idea
kind
of
to
help
with
that-
and
this
would
attach
to
this
top
level.
You're
saying.
B
A
I
would
say
that
this
could
be
a
top
level
thing,
whether
it's
more
important
than
projects
and
groups
or
like,
and
I
think
that's
a
future
discussion
that
we
can
have
but
yeah.
I
think,
where
you're
looking
at,
where
it's
just
like
controlling
global
settings,
for,
like
instance,
and
and
like
for
looking
it's
like
kind
of
scoped
to
a
namespace,
to
use
your
words
there
yeah
that.
B
Makes
sense,
okay
and
yeah,
and
that
was
what
I
was
trying
to
determine
or
find
a
solution
for
is
where
should
that
object
live?
And
this
is
my
like
first
idea
of
like
okay?
Well,
it's
not
gonna
exist
the
subgroup,
but
if
you
go
at
the
top
level,
it
would
just
say
this
new
navigational
item,
but
I
think
this
feels
nicer.
B
I
would
probably
suggest
this
instead
because
that
way:
you're
not
necessarily
changing
the
interface
of
whatever
object,
you're
in
so,
if
you're
in
a
group
or
a
project
that
kind
of
stays,
so
at
least
the
information
architecture
that
you're
familiar
with
stays
normal
and
you're,
not
adding
anything
complexity
to
that,
whereas
I
don't
know
if
you've
done
research
into
how
many
people
are
using
this,
but
I
feel
just
from
the
outset.
I
never
use
it
apart
from
like
going
to
my
group
or
my
project,
so
I'm
thinking
that
makes
perfect
sense
to
edit.
There.
B
Make
the
title
the
landing
page
of
the
menu
item,
so
that
was
something
that
I
was
thinking
about
when
I
did
my
research
for
the
where
I
wanted
to
add
members,
one
of
the
feedback
that
we
had
gotten
was
the
the
people
were
thinking
they
could
click
on
the
top
level
container
or
the
top
level
object.
Let
me
share
my
screen
real.
B
C
One
thing:
that's
useful,
like
a
mental
model,
that's
useful
for
thinking
about
our
how
our
navigation
works
is
container
and
then
container
items,
so
workspace,
group
and
project
could
be
a
container
and
then
workspace
project
and
group.
Each
have
unique
container
items
that
are
interchangeable,
sometimes
the
same
whatever
it
is,
so
just
I'm
just
giving
that
mental
model,
because
I
I
foresee
this
is
this
is
probably
a
useful
thing
for
aiding
the
discussion
and
then
michael.
Let
you.
A
Yeah
that
that's
that's
something
that
I
I
needed
to
say
a
few
times
when
I
was
looking
at
this
is
like
yeah.
Where
does
everything
live
and
I
think
that's
kind
of
like
a
future
problem,
and
I
think
this
is
something
that
I
keep
on
talking
to
my
group
about.
Is
you
know
what
problem
are
we
talking?
Are
we
solving
the
current
problem
or
is,
like
you
know,
grouping
things
like
this
idea
of
name
spaces
could
like
change
the
way
we
do
navigation
in
its
own
way.
B
A
One
there
if
we
use
that
to
be
something
else,
yeah,
that's
probably
something
that
we
can
talk
about
and
maybe
not
today,
but
yeah.
We
can
decide
whether
that's
something
you
want
to
pursue
daniel,
because
there's
a
in
so
far
in
our
like
research.
There's
also
been
like
this
idea
of
like
in
issues.
You
know,
if
I'm
looking
at
issues
for
one
project
that
I
want
to
switch
to
another
project.
A
I
think
there's
more
elegant
ways
to
do
that
and
firebase
does
a
pretty
good
execution
of
this
idea
of
switching
project
spaces,
but
I
think
your
head
is
also
in
this
kind
of
namespace
group
kind
of
like
jumping
these
worlds.
Introducing
this
other
new
world
is
interesting
to
me.
Where
am
I
going
with
this
yeah?
That
top
area
is
like
malleable
right
now,
so
one
execution
is
to
potentially
absorb
project
overview
into
that
top
area.
The
other
alternative
is
like.
A
Maybe
you
could
take
it
to
do
your
name
spacing,
because
we,
I
personally,
don't
think
we
need
three
links
to
get
you
to
the
same
page,
I'm
not
against
I'm
not
against
having
multiple
paths
to
a
single
page,
because
that's
useful,
that's
not
the
nature
of
the
web,
but
like
within
the
same
proximity
of
like
they're
all
next
to
each
other,
and
we
don't
need
that.
So
we
could
repurpose
one
of
those
things
and
yeah.
A
The
top
thing
is
an
interesting
one,
but
I
would
caution
of
taking
that
to
like
launch
into
another
high
level
space,
because
people
are
currently
are
accustomed
to
clicking
that
top
part
to
go
home
or
like
the
home
page
of
their
project,
so
hijacking
that
to
take
them
to
like
a
higher
level
instance
might
be
tricky.
But
we
can
probably
circumvent
that
by
rethinking
the
project
overview
page,
which
is
another
thing.
That's
also
for
grabs
from
changing.
B
B
However,
if
we
think
about
it
from
like
a
person
who
subscribes
to
gitlab,
so
they'll
have
this
project
and
this
would
be
their
top
level
and
that
the
object
or
the
idea
would
be
the
association
with
the
attachments
of
the
admin
screen.
The
overview
or
the
security
dashboard
would
exist
at
that
very
top,
which
would
just
be
here
because
this
is
this
screen
that
we're
looking
at
is
kind
of
like
gitlab's
own
space
right,
despite
the
all
these
things
are
public
or
that
we
have
access
to
them
because
obviously
we're
the
employees
here.
B
B
B
A
A
A
B
A
B
B
So
there's
no
security
concerns,
I'm
not
sure
how
much
of
how
much
of
a
disconnect
there
needs
to
be
in
the
interface.
For
that,
I
think
just
the
way
the
slack
did.
It
is
a
simple
like
toggle
or
click
would
be
sufficient
and
I
think
functionally
gitlab
has
that
at
least
if
you're
looking
at
the
group
viewer,
as
I
saw
earlier,
we
show
all
the
group
objects,
but
it's
just
a
table
of
drop-down
folders
right.
Obviously,
that
can
be
a
little
bit
visually
presented
better
but
functionally.
C
So,
just
to
be
clear,
then,
when
you're
saying
you'd
have
different
profile
views,
those
profile
views
would
be
like
an
admin,
my
own
personal
account
and
those
would
exist
within
the
same
name
name,
space
or
instance,
to
use
that
interchangeably.
Or
would
they
exist
across
multiple
workspaces
or
namespaces?
C
B
So
I
am
a
user
in
an
organization,
but
I
also
am
the
admin,
but
I
don't
want
to
have
admin
access
all
over
the
place
in
case
something
bad
happens,
so
I'm
still
within
the
same
organization
or
group
container,
and
I
simply
toggle
the
admin
switch
account
to
allow
me
to
do
an
admin
job
as
I
need
the
iteration
or
the
idea.
That
slack
has
is
that
it
again
like
I
said
it's
totally
a
different
connected
email
address
or
a
different
organization
that
prepends
to
the
dot
com
or
dot
slack
dot
com
address.
B
B
Well,
that's
what
there's
a
few
ways
to
look
at
that.
So
one
of
them
was
a
security
concern
with
some
organizations
that
had
contractors
or
freelancers
who
are
using
personal
emails
to
work
in
an
organization
and
there
was
a
need
to
switch
to
lock
them
out
and
give
them
a
corporate
email
saying
you
need
to
use
your
company
email
but
you're
going
to
lose
access
to
everything.
You've
done
so
far
or
we're
going
to
absorb
that
as
our
as
our
intellectual
property.
So
we
wanted
to
have
that
separation.
B
B
A
Yeah,
so
I'm
just
gonna
share
my
screen
again
because
that's
what
I
do
so
my
parting
note
is
that,
like
I
think,
you're
working
at
a
higher
level
than
where
my
head
is
at
my
head
is
like
at
like
thinking
I
was
like
this
is
like
not
real,
as
in
like
it's
still
exploration,
but
it's
like
this
idea
of
like
how
do
I
get
switching
projects
and
groups
easily
within
one
instance
of
the
world?
You
are
thinking
like
at
a
higher
level
where.
B
A
Want
to
switch
between
multiple
instances
and
different
worlds,
so
I
think
we
should
continue
sharing
each
other's
like
explorations
and
things
because,
like
what
I've
seen
in
over
the
last
week
is
like
some
stuff
might
influence
the
way,
you're
thinking
and
vice
versa,
so
yeah,
let's
go
ahead
and
just
make
an
action
to
keep
on
sharing
each
other's
work
because
yeah,
I
think,
you're
thinking
more
like
outside,
like
like.
Potentially
this
changes
or
like
you
know,
this
changes
like
how
gmail
does
their
kind
of
like
world
switching
but
yeah.
C
C
C
This
is
where
group
lives
within
that
draw
that
out,
draw
the
information
architecture.
It's
rudimentary.
You
may
not
get
it
perfect,
one
100
of
the
time,
but
draw
out
that
system
of
the
way
that
you
that
you,
that
you
expect
the
user
to
interact
and
that
should
help
and
then
number
two
is
create
some
scenarios
so
create
a
little
storyboard
or
something
saying
I
want
to
switch
between
profiles
because
of
xyz,
or
I
want
to
do
this
and
creating
and
making
those
stories.
C
Those
those
storyboards
tangible
again
will
make
it
much
easier
to
communicate
to
what
this
problem
is
and
we'll
also
sort
of
open
up
the
problem
to
give
people
allow
people
to
provide
feedback
on
how
important
things
are
to
them,
and
this
should
help
you
to
prioritize
namespace
user.
Switching.
All
this
sort
of.
B
Yeah
stuff,
that's
really
good.
I
appreciate
that
feedback,
and
that
was
just
to
go
back
to
what
you
were
saying.
Michael.
Was
that
definitely
I'm
trying
to
bring
as
many
people
into
this
and
explain
what's
going
on,
because
it
will
impact
everyone
and
because
it
is
kind
of
a
higher
level.
I
don't
want
to
basically
go
down
a
path
without
really
getting
much
feedback
from
anyone
else.
So
definitely
I
think
this
would
be
more
of
a
collaborative
effort
going
forward.