►
From YouTube: GitLab 16.5 Kickoff - Enablement:Tenant Scale
Description
16.5 milestone kickoff for the Tenant Scale group. 16.5 planning issue: https://gitlab.com/gitlab-org/tenant-scale-group/group-tasks/-/issues/111
A
Three
Engineers
are
out
on
PTO
for
varying
length
of
time,
but
in
essence,
we
have
four
back-end
Engineers
that
we
can
count
on
in
terms
of
capacity
in
this
Milestone,
and
our
front-end
engineer
is
also
taking
two
weeks
of
PTO,
so
we
are
a
bit
at
reduced
capacity.
I
think
we
will
get
some
help
from
the
Geo
team
for
front-end
work,
so
there's
actually
quite
a
few
things
we
are
going
to
start
working
on
and
I
would
like
to
show
you.
Our
goals
are,
as
usual,
the
organization
and
sales
has
the
highest
priorities.
A
We
do
have
an
okr
relating
to
fixing
cross
joins
between
users
and
namespaces,
which
is
a
result
of
cells.
Iteration,
two
and
there's
one
issue
in
this
Milestone
to
at
least
make
some
progress
on
this,
and
the
staff
managed
decomposition
is
also
still
something
we're
working
on
with
a
few
issues
per
Milestone.
Until
we
get
it
to
better
and
then
we
will
focus
entirely
on
sales.
A
As
of
yesterday,
we
are
dealing
with
another
feature,
change
log,
so
these
plans
might
be
slightly
disrupted,
so
take
it
with
a
grain
of
salt
as
I
present.
What
we're
planning
to
do
in
terms
of
organization
work.
One
of
the
issues
we're
looking
into
is
roles
in
particular
how
to
assign
organization
owners
to
the
organization
so
that
it
fits
into
our
data
model
relating
to
roles.
So
that's
one
of
the
back
end
issues
we're
going
to
take
up.
A
As
for
front-end
work,
there
will
be
the
organization
settings
page
where
at
least
the
upper
section
we're
going
to
start
building
now
the
more
advanced
sections
we
will
add
in
later.
So
once
it
is
in
place,
users
can
added
the
organization
name,
add
a
description
and
the
Avatar
section
will
be
very
basic
in
the
beginning
and
we'll
add
the
ability
to
change
our
returns
later.
A
Another
thing
we're
going
to
take
on
is
the
organization
list
view
in
your
work,
which
will
look
something
like
this
very
basic.
It's
just
going
to
list
all
the
organizations
that
a
particular
user
has
created
and
we're
also
thinking
about
adding
a
way
how
to
also
list
organizations
that
the
user
is
frequenting
very
often,
but
it's
not
necessarily
a
member
or
a
creator
of
talking
about
organization
Creation.
A
It
will
lean
on
the
designs
of
the
forms
we
already
have
for
groups
and
projects,
so
it
will
look
very
similar
in
the
way
it
feels
where
the
user
is
just
going
through
the
flow
to
add
the
organization
name,
description
and
an
avatar,
also
adding
existing
top
level
groups.
Though,
to
make
this
particular
section
function,
we
will
have
to
work
through
a
couple
of
other
issues,
but
once
that
is
in
place,
the
work
section
can
be
populated,
and
then
we
are
a
couple
of
steps
closer
to
having
a
functioning
prototype
for
cells.
A
We
will
not
take
on
too
many
issues,
as
we
still
have
a
couple
of
issues
that
will
fall
out.
We
have
the
feature
change
log
to
build,
which
we
work
on
issues
to
improve
upon
in
relation
to
that
and
there's
a
few
issues
we
will
have
to
take
up
for
the
giddly
migration.
A
So
the
most
important
item
that
we
can
and
we'll
work
on
now
is
to
get
started
on
sales,
iteration
3,
which
is
focusing
on
creating
a
project
on
a
different
cell,
and
this
issue
will
unblock
a
whole
bunch
of
other
issues
that
are
similar
to
the
ones
we've
already
worked
through
in
relation
to
groups.
So
we
will
also
go
through
processes
like
identifying
cross
transactions,
cross
joints
and
converting
foreign
keys
before
we
can
deliver
the
demo
in
which
we
will
create
a
project
on
a
different
sub.
A
So
this
issue
is
unblocking
all
of
that
work.
That's
why
we're
going
to
focus
on
that
in
16.5
and
in
terms
of
bugs
we
have
decided
on
an
S2
bug,
that's
been
in
the
backlog
for
a
while.
There
will
be
Fallout
from
the
previous
Milestone,
so
we're
not
gonna.
Take
on
more
than
necessary
and
what's
listed
under
maintenance
is
mostly
the
work
related
to
Italy
and
then
an
issue
also
relating
to
the
self-managed
decomposition.