►
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
Hello,
everybody,
my
name
is
Roger
and
I
am
here
with
the
application,
Performance
Group
16.3
planning.
Overall,
in
this
coming
month,
we
expect
our
team
to
be
at
approximately
85
capacity.
Over
the
last
couple
months,
the
team
has
been
working
hard
to
enable
code
suggestions
for
self-managed
and
dedicated
customers
in
16.3.
We
will
continue
to
iterate
on
our
existing
work.
Our
goal
is
so
that
there
is
no
need
for
self-management
to
perform
any
configuration
on
gitlab
SAS.
A
As
part
of
this
effort,
we're
going
to
be
routing
code
suggestions
for
self-managed
users
through
their
self-managed
rails
monolith
ensuring
that
the
self-managed
instance
is
in
the
flow
of
information
and
flow
of
control.
This
work
primarily
impacts
the
authentication
flow
for
self-managed
instances
and
is
separate
for
monetization
of
code
suggestions
for
self-manage.
We've
conducted
several
technical
Explorations
on
how
to
approach
this
problem
in
16.2,
and
our
implementation
is
here
in
this
option.
A
One
sequence:
diagram:
we've
made
actually
pretty
good
progress
towards
a
lot
of
these
items,
but
some
of
these
largest
items
around
authentication
are
still
to
come
and
we
expect
to
wrap
them
in
16.3.
We
have
two
stretch
goals.
One
is
to
improve
code
suggestions
and
metrics
for
self-banish
instances.
Currently
we
don't
have
any
way
of
measuring
users
directly,
because
right
now,
users
on
SAS,
sorry,
we
don't
really
measuring
self-managed
users
directly.
Users
on
SAS
are
currently
being
generally
compared
to
instances
on
self-manage
separating
out.
A
Self-Managed
data
will
help
reduce
confusion
overall
and
also
set
up
foundations
for
us
to
perform
more
self-managed
specific
analysis
and,
in
the
long
run,
support
our
efforts
to
shift
towards
an
organization-based
model,
especially
for
insights
and
Analytics
goal
here,
is
to
support
the
cross
group
effort
for
code
suggestions
to
be
GA
ready
with
16.3's
release.
We
should
validate
whether
self-managed
can
meet
those
timelines
and
do
our
best
to
support.
Given
the
delay
timeline
for
customer
upgrades,
you
know
each
time
you
release
a
self-managed
version,
because
most
customers
are
usually
one
to
three
months
behind.