►
From YouTube: 2022-04-20 Workspace weekly
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).
B
A
I
am
afraid
will
be.
There
will
be
not
many
engineers
joining
today,
I'm
looking
at
the
ptos,
so
just
okay.
One
thing
I
will
brought
up
if
engineer
sounds
like
and
the
second
thing
that
as
we
are,
as
we
close
the
phase
one
so
the
so
the
phase
one
is
ready
and
the
code
is
ready
to
move
to.
Other
phases
will
be
a
hosting
imi.
A
So
it
was
a
ask
from
christopher,
so
development
director.
A
I
will
touch
base
of
the
team
around
the
time
zones
and
dates
and
how
to
how
to
do
it
in
a
most
effective
way,
but
just
an
fyi,
especially
to
mike.
If
someone
will
be,
you
know,
asking
questions
about
the
future
of
the
future
of
the.
I
know
certain
design
choices
just
just.
I
just
want
to
warn
you
that
we'll
be
doing
this
thing,
so
those
questions
can
can
appear.
A
Also,
I
can
send
you
the
I
think
there
was
it
was
recorded
and
definitely
there
was
an
agenda
that
we
have
already
have
ami
on
more
product
level.
So
those
could
also
be
really
helpful
to
you
to
see
how
you
were
approaching
those
those
questions.
Oh,
it
was
like
two
months
ago
or
something.
A
I
think
it
will,
I
think
the
question
that
asked
was
more
about
like
engineer
oriented
ami
and
what
so
I
will
I
will
check
with
with
the
team
I
will
check
also
with
with
aurit,
but
when
she,
when
she
come
back
to
make
sure
that
we
are
doing
it
in
the
most
productive
way.
So
everyone
can
ask
questions.
B
Since
you
have
all
of
ux
represented
here,
do
you
have
any
questions
for
us?
Do
you
have
any
and
vice
versa
mike?
Do
you
have
any
questions.
A
I
already
was
talking
to
mike
last
week
so
right
now.
I
know
that
we're
in
this
very
rich
position,
when
I'm
sure
mike
is
I
would
be
happy
to
jump
into
the
work,
but
on
the
back
end,
there's
still
a
lot
of
lot
of
effort
to
to
be
done
to
be
able
to
go
into
the
situation
where
you
can
start
thinking
about
more
changes
like
bigger
changes,
there's
still
a
lot
of
backend
forth.
To
do
so,
I
know
that's.
A
This
is
not
a
like
the
best
situation,
but,
on
the
other
hand,
we'll
have
we
have
time
to
to
really
do
a
good
research
on
on
the
changes
that
are
coming.
Like
my
biggest
ask
is:
maybe
it's
I
think
I've
said
it
for
it.
That's.
A
I
know,
there's
a
lot
of
terminology
going
around
like
like
workspace
namespace
and
how
we
are
going
to
call
the
like
this
main
group
that
will
this
will
be
our
mind
unit
of
of
understanding,
because
I
believe
that
we
should
start
thinking
of
the
terminology,
because
we
should
use
it
in
the
code
once
we
get
there.
A
The
same
use
the
same
language
as
the
as
the
language
that
will
be
customer
facing,
as
this
greatly
help
with
communication
between
engineers
and
product
team
and
support
team
and
the
the
most
the
heart.
The
hardest
thing
is:
when
everyone
calls
the
same
thing
differently,
then
that's
yeah
and
that's
terrible.
So
if
we
can
actually
start
with
like
good
naming,
that
would
be
like
helpful.
B
That's
great
start,
honestly,
so
yeah
I
mean
so
from
an
engineering
perspective.
What
what
are
you
guys
referring
to?
Are
you
using
namespace
as
the
actual
term
or
workspace,
or
something
different.
A
Actually,
like
naismas,
is
that,
namely
used
in
the
code,
that's
that
hosts
groups,
projects
and
users-
and
this
is
like,
like
the
container
that
somehow
is
connected
to
groups,
that
is
a
group
actually
like
some
subset
of
namespaces
are
groups.
Some
substitute
namespaces
are
users
like
that,
and
it's
used
when
we
create
users
projects
in
a
personal
profile
on
the
personal
profile
and
right
now
we
have
also
namespaces
that
are
wrapper
around
projects.
A
That's
actually
what
we
are
working
on
right
now,
actually
there
something
that
I
think
was
described
as
workspace,
but
it
was
not
a
like
name
that
would
be
used
as
it
may
be,
confusing.
We
in
the
code
is
called
like
root
group
or
root
ancestor,
so
something
that's
that's
on
the
very
top
of
the
character,
yeah
yeah.
So
this
is
the
name.
That's
it's
using
the
code.
The
root
group
root
ancestor,
that's
dependent
on
the
other
place
so
yeah.
This
is
the.
A
This
is
how
we
call
it
right
now,
but
I
know
that
workspace
was,
I
think,
was
fought
as
like
the
bigger
night,
like
the
name
for
the
spec
root
group.
So
they
think
it's
on
the
very
top,
but
I
don't
know
it
was
decided
that
we'll
stay
calling
it
that.
C
Let
me
ask
a
tangential
question
in
the
ama
and
in
the
last
thing
last
interaction
I
saw
that
nick
post
did
before
he
left.
There
was
a
discussion
about
whether
projects
and
groups
will
still
exist,
and
the
answer
that
I
think
was
given
was
yes.
They
will.
C
But
my
question
is:
is
that
in
the
near
term,
or
is
that
a
long-term
answer?
So
I
think
in
this
in
the
short
term,
it
makes
sense
that
they
obviously
have
to,
because
we
can't
switch
this
new
thing
until
we
get
this
new
thing.
But
in
your
opinion,
was
that,
given
as
a
short-term
answer
or
was
that
given
as
a
long-term
answer,
it
was
hard
to
get
that
context
without
being
there.
A
I
think
the
whole
idea
was
to
make
everything
more
flexible,
so
so
making
so,
and
so
I
I
cannot,
I
would
refer.
I
would
like
delegate
this
question
to
orient
like
how
the
product
like
is
seeing
it
as
a
future.
I
know
that
for
the
short
term,
we
definitely
cannot
cannot
deviate
far
away
from
what
we
have
now,
as
this
would
be
very
confusing
for
users
also,
because,
like
projects
are
very
strongly
connected
to
repositories-
and
we
cannot
go
away
from
that.
A
So
this
is
a
great
question
for
our
rates
about,
like.
A
C
And
if
I'm
being
completely
transparent,
I
I
would
like
to
ask
you
know
I
I
I
kind
of
was
asking
just
to
see
where
the
alignment
was
on
that
from
from
your
perspective,
yeah,
I
agree.
It's
definitely
an
order
question
because
she's
the
one
that
gave
the
answer.
So
I'm
sorry
for
putting
you
in
the
position.
No,
I
think.
A
A
I
think
that
that,
with
the
changes
we
are
currently
doing,
we
will
have
option
to
even
think
about
it
to
even
think
if
we
want
to.
If
you
want
to.
A
Go
away
from
groups
and
projects
and
organize
it
in
some
other
way,
and
but
but
I
I
I
cannot
answer
you,
I
cannot
say
it
more
than
that
tonight
then
I
don't
know.
C
Gotcha
yeah
and
the
reason
why
I
think
that's
important
for
damian.
Yes,
if
that
was
the
long-term
thing,
you
know
what
we're
then
talking
about
the
new
name
being
the
third
thing,
in
addition
to
groups
and
projects,
or
is
it
a
replacement
of
groups
and
projects?
And
so
I
think
that
you
know
that's
a
key
factor
in
what
it
is
for
sure.
C
A
Okay,
if
there's,
if
there's
something
we
have
for
today,
I
will
give
your
time
back
and
thanks
for
joining
and
we'll
see
each
other
next
week.
Thanks
all.