►
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
Welcome
to
the
application,
Performance
Group,
16.5
planning,
my
name
is
Roger
and
with
me
is
Paul.
My
engineering
manager
counterpart,
one
thing
that
we
should
call
out
right
now
is
Paul
I,
know,
you're
kind
of
helping
us
drive
the
effort
to
rename
the
group
to
Cloud
connector
to
reflect
the
domain
that
we've
been
working
on.
A
I.
Think
we're
probably
going
to
aim
to
get
that
moving
within
this
coming
Milestone
and
hopefully
wrap
up
the
Milestone
following
if
it
takes
longer,
but
not
much
more
than
that
in
terms
of
capacity
we
are
currently
at
about
85
team
capacity
with
PTO
and
our
top
priorities
for
16.5
continue
to
be
supporting
git
lab
on
South
map.
A
Ai
features
on
self-managed,
starting
with
gitlab
chat
for
our
Focus
part
of
this
involves
building
a
proxy
API
for
instantropic
into
the
AI
Gateway,
and
in
the
long
run
we
expect
these
code
paths
to
be
owned
by
the
AI
framework
team
and,
as
such,
we're
going
to
be
collaborating
with
them
on
specific
changes
to
the
Gateway.
A
Part
of
this
effort
also
includes
providing
guidance
on
how
to
instrument
chat
related
to
mandatory.
In
a
way,
that's
consistent
across
both
SAS
and
self-managed,
and
this
is
a
problem
that
we
noticed
needed
some
attention
with
code
suggestions,
because
a
lot
of
these
features
were
built,
SAS,
first
and
so
are
self-managed
Telemetry
just
needed
some
additional
considerations
to
make
sure
they
were
comparable.
A
Some
additional
Focus
items
that
we've
been
working
on
and
carrying
forward
include
improving
the
code
suggestion
metrics
for
self-managed
instances,
so
our
long-term
goal
is
to
display
code
suggestion
business
metrics
in
Tableau,
and
we've
already
been
able
to
instrument
the
number
of
unique
instances
and
unique
users,
beginning
with
16.3
and
there's
ongoing
work
to
make
this
data
visible.
So
we're
going
to
continue
to
support
that
effort.
A
We're
also
exploring
additional
support
for
AI
features,
currently
we're
looking
into
suggested
reviewers
and
trying
to
figure
out
how
we
can
bring
suggested
reviewer
capability
to
our
self-managed
instances
and
also
looking
to
understand
how
explain
this
vulnerability
might
work.
Lastly,
we're
preparing
post
suggestions
for
General
availability
in
support
of
the
other,
broader
efforts
in
the
company
to
GA
and
monetize
code
suggestions
as
an
add-on.
So
one
of
the
things
we're
going
to
do
is
streamline
customer
onboarding
we're
going
to
stop
performing
manual
onboarding
for
customers
on
16
1,
16
2.
A
Without
a
CSM
for
those
customers,
we
recommend
that
they
upward
to
upgrade
to
16.3
to
perform
self-guiding
onboarding.
Lastly,
we're
going
to
work
through
some
ux
design
problems
to
make
sure
that
when
we
do
monetize
code
suggestions
through
an
add-on,
we
have
a
smooth
and
Clear
customer
experience
in
terms
of
how
the
purchasing
happens,
how
the
activation
happens
and
the
types
of
configurations
that
will
need
to
take
place.
A
I
think
that's
kind
of
a
summary
of
what
we're
looking
at
for
the
application.
Performance
Group
soon
to
be
the
cloud
connector
group
called.
Do
you
have
anything
you
want
to
add
in
or
just
throw
in
there?
No
I
think.
That's
all
good
that
question
all
right.
Well,
thank
you
everybody.
This
is
our
kickoff
for
application.
Performance,
Group,
16.5.