►
From YouTube: Enablement Group Conversation (Public Livestream)
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
Hi
everyone-
this
is
Joshua
Lambert,
a
career
path
manager
here
for
get
lad
and
I
am
the
enablement
group
manager,
and
today
I
will
be
talking
about
our
enablement
growth
conversation.
You
can
find
slides
and
the
link
and
the
Google
Doc,
and
we
have
a
few
questions
rolling
in
which
is
fantastic
Syd.
You
want
to
know
it's
over
your
first
question:
yeah.
C
Thanks
for
the
great
slide
deck
so
for
us,
we
have
both
users
from
capcom
and
we
have
users
selves
installed
and
that's
still
driving
90
percent
of
our
revenue,
the
self-manage
once
I
seen
it.
We
have
a
lot
of
new
people
coming
in
and
and
they
naturally
gravitate
towards
our
calm,
offering-
which
is
logical
but
are
we?
Are
we
focusing
enough
on
making
sure
to
self-manage?
Install
is
a
great
experience
like
that.
B
Yeah
so
I
think
the
answer
is,
we
should
be
focusing
here
more
than
we
are
today
for
the
overall
installation
journey
I
went
to
the
process,
part
of
the
product
walkthrough
in
March,
and
it
was
painful
to
be
honest
and
direct,
and
so
I
have
a
number
of
items
open
to
try
and
track
that.
But
we
should
also,
of
course
be
doing
this,
the
more
comprehensive
basis
with
with
user
interviews.
So
the
growth
team
is
getting
an
effort
underway
now,
which
is
fantastic.
B
Thank
you
so
much
the
growth
team
for
getting
that
ball
rolling
fabien
also
noted
an
issue
for
Jia
we're
in
focusing
on
improving
the
user
experience
and
getting
started.
So
both
those
are
are
really
quite
helpful
and
then
we
also
have
a
process
underway
to
try
and
make
provisioning
of
larger
instance
types
also
easier
with
the
provisioner
and
so
automating
in
asia
deployment,
and
that
should
hopefully
take
away
some
of
some
of
the
pain
around
that
experience.
C
I
think
the
painful
experience
you
had
was
with
setting
up
to
you
and
everything.
Are
we
also
making
sure
that,
like
to
set
up
a
simple
server
that
the
way
most
people
will
start?
That
is
that
is
that's
a
much
better
experience,
I
hope,
but
that
maybe
that
can
use
a
little
bit
of
Polish
as
well.
Yeah.
B
So
which
we
need
to
do
both
those
things,
and
so
we
need
to
do
a
better
job
here,
I
think
and
once
we're
past
there,
Janeiro
we'll
have
some
more
time
freed
up
right.
Now
we
have
a
lot
going
on,
but
it's
not
an
excuse.
It's
just
we
needed,
or
we
need
to
do
another
focus
here
more
conclusively
in
the
near
future,
so
we'll
get
that
underway
and
also
on
my
experience
it
wasn't
actually
geo,
which
was
the
problem
for
for
gitlab.
B
It
was
a
hard
time
find
the
documentation.
The
license
I
never
got
a
license
sent
to
me
in
the
license
generation
process
when
I
went
through
the
process,
which
is
the
only
which
is
so.
That
was
the
challenge,
and
we
also
had
bad
and
not
idea,
recommendations
and
how
to
employed
get
lab.
It
just
didn't
work
in
some
cases,
even
getting
the
age
of
the
plant
running
so
I
know,
Colin
is
working
on
support,
improving
the
AG
documentation
as
well.
B
C
Thanks
for
that
context,
it's
super
helpful.
Also.
The
second
question
we
now
are
using
puma
on
capcom,
yay
and
now
the
next
step
is
to
roll
it
out
as
far
as
I
understood.
But
this
is
pretty
complex,
so
so
I'm
just
saying
what
I
think
I
know
I'm
not
saying
I,
don't
think
it's
completely
correct,
but
on
mancom
we
use
puma
multithreaded
for
self-managed
installations
to
prevent
a
ton
of
back-and-forth
to
prevent
a
ton
of
io.
We
have
a
set
of
patches
on
rugged
that
we
ship
that
are
not
multi
treaded
compatible.
C
So
we
can
ship
that
out
yet
and
I.
Don't
know
what
that
I
think
it'd
get
a
lot
back
home.
We
get
to
live
without
the
patches,
maybe
because
we
use
SSDs
and
we've
got
a
ton
more
if
IO
we
can
do,
but
it
seems
like
the
obvious
thing
would
be
to
make
sure
that
those
patches
are
kind
of
both
in
gitlab
for
everyone,
so
everyone
gets
less.
Less
has
less
need
are
for
IO,
but
that
doesn't
seem
to
be
the
solution,
so
I'm
kind
of
I'm
a
bit
puzzled.
What
what's
happening
and
what?
B
Sure
I
could
answer
I'm,
not
sure
Camille's
on
you
can
get
maybe
a
more
detailed
answer,
but
I'll
go
first
as
I'm
clicking
through
them
attendees
here.
So
basically,
obviously
with
a
challenge
with
multi-threading
and
rugged
is
that
ruby
has
a
gill
and
it
needs
a
lot
of
computation
and
a
ruby
in
and
some
time
slicing
through
three
different
spreads,
because
only
wine
can
actually
Xu
at
a
given
time,
and
so
this
causes
that
precinct
an
increase
in
latency.
B
B
So
what
we
are
doing
is
we
have
built
some
other
detection
in
place
so
that,
if
you
need
to
have
rugged
turned
on
it
will,
if
I
quickly
fell
back
to
a
single
process
and
then
a
lot
times
you
behave
like
unicorn
would
I'm
trying
to
find
out
if
Camille
is
on.
You
can
get
more
answered
here.
If
you
are
I
can't
find
you
somebody
just
speak
up,
but
in
general
that's.
B
C
B
C
That
makes
sense
thanks
to
that,
it's
probably
there's
a
good
reason.
We're
not
doing
it,
but
the
rugged
code
has
probably
some
optimizations
in
it.
Is
it?
Is
it
possible
to
bring
those
to
get
early
or
start?
You
start
just
kind
of
reverse
engineering
or
adding
that
that
efficient
code
efficiency
to
get
lab
or
IO
efficiency
to
get
lab
itself
for
everyone,
I.
B
Believe
the
ghillie
team
is
working
on
this
I
think
there's
a
caching
layer
among
potentially
other
things
that
rugged
does
that
make
it
something
more
efficient,
so
I
believe
there's
a
an
issue.
I
can
probably
find
it
to
essentially
eliminate
luggage
and
which
would
be
great.
So
we
can
stop
worrying
about
this
sort
of
fragmented
configuration
matrix
going
forward
cool
thanks
to
that
yep
yeah
I'll,
try
and
follow
up
with
the
the
get
elite
status.
D
B
Sure
so
the
Emperor
p.m.
were
looking
to
have
two
significant
impacts
on
the
company.
The
first
is
being
a
product
manager,
the
first
product
manager
for
the
infrastructure
group.
So
we
have
two
engineering
groups
in
there
we
have
the
scalability
and
the
release
team,
the
race
groups
and
so
it'd
be
great
to
have
a
bike
manager
to
help
to
evangelize
for
their
needs
across
the
broader
pogrom
is
a
Chinon
pipe
development
groups
and
so
kind
of
what
they're,
seeing
and
I
mean
helping
to
make
sure.
B
We
translate
that
into
the
correct
position
for
other
parts
organization
as
well
as
also
just
generally
helping
to
prioritize
the
work
that
they
are
doing,
and
then
we
also
have.
There
are
some
surface
area
of
calm.
That's
it
isn't
really
covered
by
any
of
the
other
pipe
teacher
groups.
So
when
you're,
obviously
we
want
everyone
to
feel
like
they
own
their
features
on
gitlab
calm,
which
is
great,
but
there
are
things
like
what
should
our
availability
being?
What's
one
of
our
margins?
B
They
don't
lis
think
about
the
cost
impact
of
new
features
on
comm,
something
like,
for
example,
the
WebSocket
discussion
from
last
week
could
have
a
fairly
decent
impact
on
comm
if
we
have
have
more
constant
connections
through
to
calm,
and
so
we
kind
of
think
about
those
things
beforehand
and
have
an
analysis
done
and
so
on.
That's
nothing
hoping
to
help
to
have
do
itself
improve
our
processes,
so
we
can
consider
these
things
before
we
get
too
far
along
yeah.
B
B
Great,
thank
you.
Thank
you
jar,
so
we
had
that
board
that
we've
run
through
and
that
has
labels
attached
for
the
various
savings
that
we
think
we
can
achieve
this
way.
We
can
it's
easy
to
figure
out
kind
of
like
the
importance
and
relative
impact
of
these,
and
you
can
see
more
of
those
there
we'll
go
through
and
also
start
to
work
on
tagging
each
of
these
also
with
the
DevOps
groups,
if
they
pertain
to
them
some
of
these
things.
B
Like
the
note,
automated
rebalancing,
you
know
that
that
might
require
some
Gilly
work
and
so
will
help
to
also
go
through
and
make
sure
those
appear.
So
you
can
kind
of
filter
for
your
groups
as
we
find
more
of
these
opportunities
and
I
just
took
them
one.
This
morning
on,
potentially
maybe
reconfiguring
our
I
know.
It's
sizes,
for
you
know,
took
on
flip
houma
potential
savings
here
as
well,
so
you
can
see
some
there.
There
are
some
big
ones
like
the
container
storage
is
a
big
one.
Some
of
the
cloud
net
aspects
are
large.
B
E
Okay,
I
think
I've
got
the
next
one
Josh,
so
Kai.
Thank
you
for
putting
that
link
in
on
the
strategy
for
search
global
search
for
self
hosted
a
little
bit
of
context
Josh
around
this
question,
so
some
of
my
customers,
as
they
start
to
use
more
and
more
of
the
of
the
collaboration
features
of
get
labs
self-hosted.
E
F
I'll
finish
out
the
week
strong
on
this
one,
so
I
just
linked
one
issue
here,
which
is
about
indexing,
elastic
search
or
indexing
Microsoft
Word
files
in
the
last
search.
So
this
isn't
the
first
time
we've
heard
that
customers
are
using
this.
It's
also
not
necessarily
something
but
I'm
sure
is
the
right
use
case
of
what
we're
building
yet
I
think
it's
something
we
need
to
continue
to
validate
and
understand
from
customers.
F
F
I
linked
an
admin
UI
redesign
that
we
had
been
working
on
late
last
year,
put
it
on
the
back
burner,
but
we'd
like
to
revisit,
which
is
in
terms
of
connecting
to
your
elasticsearch
cluster
and
then
getting
some
insights
and
visibility
into
that
I.
Think
that's
an
area
where
we
can
help,
but
there's
a
lot
of
different
ways
that
people
are
installing
and
using
elasticsearch
and
so
I
think
getting
into
that
side
of
it
is
potentially
a
little
more
complicated
at
this
time.
B
Yeah
just
to
quickly
address
the
first
wave
question
about
making
it
easier
to
able
manage.
So
that's
not
currently
I'm
a
short-term
plan.
Right
now
we
were
mostly
focused
on
improving
the
operational
aspects
of
the
service,
so
we
had
a
pretty
big
impact
on
reducing
the
overall
index
size
last
milestone.
B
F
On
the
answer,
so
yeah
I'll
just
verbalize,
the
answer,
which
is
the
handbook,
is
not
in
scope
for
the
global
search
group.
It
is.
There
is
a
new
group
that
is
the
static
site,
editor
group
that
does
have
the
handbook
in
scope
from
a
technology
standpoint
that
handbook
uses
a
Golia
for
search.
It
does
not
use
at
least
last
I
checked
it
should
someone
should
confirm
it.
I'm
pretty
sure
we
still
use
eclipse
research.
It
does
not
use
the
same
back-end
infrastructure
that
obviously
the
get
live
application
uses.
F
So
we're
not
it's
not
anything
that
the
the
feature
group
that
works
on
global
search
is
looking
at.
That
being
said,
Eric
churners,
the
PM
for
that
I
didn't
see
him
on
the
call,
I
think
Eric
Brickman's
on
the
call,
if
he
has
anything
else
to
add,
if
it's
a
focus
for
them,
but
I
like
to
my
handbook
page
about
searching
it,
and
then
you
can
also
follow
up
what
Eric,
sugar,
slack
or
channel
for
moment
more
details
on
that
one
yeah.
G
I
can
add
just
a
little
bit
of
color,
which
would
say
yes,
it
would
be
in
scope
for
that
team
to
own.
It's
not
necessarily
the
focus
at
this
point
in
time
the
focus
has
been
for
that
team
has
been
to
remove
really
inefficiencies
in
the
handbook
with
respect
to
the
pipeline
time
build
times
and
deployment
tons
which,
if
you've
been
continuing
to
the
handbook,
youth,
hopefully
notice.
G
Those
have
turned
it
down
over
the
past
few
months
and
also
getting
a
MVC
of
a
actual
static
site
editor
in
ticket
lab,
so
that
our
handbook
can
begin
to
dog
food
it
or
the
hammock
users
committee
can
begin
to
decree
that
feature,
and
so
we'll
have
a
little
bit
more
information
on
that
in
our
group
conversation
which
actually
happens
to
be
tomorrow.
If
you
want
to
come
and
see
what
we're
doing
there.
C
Yeah
thanks
for
the
presentation,
it's
it's
really
good
it
it.
It
has
a
lot
of
detail.
There's
a
lot
of
links.
It's
very
clear.
We
also
talked
about
the
things
that
we
can
improve
and
yeah.
It
seems
that
everyone
is
focusing
on
the
right
things
like
obviously
I
can
I
can
determine
that.
But
I
see
nothing.
That's
off
I,
see
just
everyone
focusing
on
stuff
that
and
generates
customer
results
and
help
us
to
say
make
it
one
better.
So
really
well
done
thanks
ed.
H
Mech,
hey
great
slides,
as
I
said,
I
wanted
to
congrats
on
slide
10
getting
staging
geo
up.
It's
been
something
it's
a
long
haul
for
a
while
and
here's.
What
are
the
next
steps
to
make
this
into
the
deployment
you
are
we
gonna
plan
to
do
like
a
smoke
fail
over
every
deployment?
What
does
it,
except
here,
I?
Think
JB
and
I
started
answering
that
question
so
yeah.
I
So
thanks
for
for
those
questions,
I
am
also
very
happy
that
we
are
essentially
done
with
getting
GE
on
staging.
That's
been
a
little
bit
of
a
journey,
so
it's
good
to
see
this
finish.
Regarding
the
weekly
de
Provence
I
I'll,
be
honest:
I'm,
not
100%,
sure
how
this
is
being
done.
Like
now,
I
actually
thought
that
you
know
geo
is
now
part
of
those
deployments
in
terms
of
quality
control.
I
I
completely
agree
with
you
that
I
would
I
would
actually
love
to
have
all
of
these
sort
of
smoke
tests
automated
so
that
they
run
every
single
time.
That's
definitely
a
part
of
our
our
vision
for
for
geo.
What
we've
done
in
the
meantime,
especially
for
fail
overs,
is
the
team
essentially
has
a
sort
of
a
cadence
before
releases
to
do
upgrade,
testing
and
and
failover
testing,
but
I
think
this
is
a
great
opportunity
for
us
to.
I
You
know
automate
these
things
and
then
always
do
this
on
stage
a
first
right,
because
one
of
the
big
advantages
of
running
to
you
on
the
staging
environment
for
us
is
really
the
scale
as
well,
and
it's
also
the
complexity
of
the
deployment.
But
this
really
gives
us
an
opportunity
to
verify
regularly
that
things
are
are
fine
which
improves
our
confidence
in
the
product
tremendously.
I
So
both
are
ten
points
and
make
sure
to
speak
with
Jenny.
With
regards
to
what,
specifically,
we
can
do
to
improve
the
QA
going
forward,
I
think
in
like
on
a
high
level
and
in
general,
one
of
the
things
that
the
Geo
team
I
think
is
taking
on
is
to
ensure
that
do
like
essentially
stays
up
and
running
right
that
this
is
not
a
oh
yeah,
we've
deployed
it
once
and
then
it
just
falls
off
and
breaks
again
right.
I
We
want
this
to
be,
you
know,
available
and
also
build
the
knowledge
and
the
team
so
that
this
is
not
something
that
is
you
know.
Only
one
person
can
actually
do
this,
but
something
where
you
know
we
we
build
the
knowledge
inside
the
team
how
to
how
to
manage
this,
because
that
is
also
quite
valuable.
When
we
help
some
of
our
customers
with
large
deployments,
you
know
fix
some
of
the
issues
that
they
may
encounter.
I
K
B
So
the
goal
here
is
to
show
as
effectively
the
upgrade
behaviors
of
our
customers,
and
so
you
can
see,
for
example,
that
we
have
well
talk
online
I
can't
explain
the
the
solid
straight
line
up
for
12.9
I
think
we
ended
a
can
literally
look
at
what's
happening
with
this
chart.
So
thanks
for
pointing
that
out,
that's
erroneous,
but
the
goal
overall
is
to
show
effectively
how
like
what
are
the
big
cohorts
of
our
upgrade
paths,
and
so
how
far
back
are
people
staying?
And
so
you
can
see
here.
B
The
blue
line
is
effectively
that
your
thong,
your
thinner
version,
that's
at
least
three.
You
know
within
the
past
three
months,
right
so
of
the
current
release,
your
n-,
effectively
n
minus
two,
and
then
you
can
see
the
chilling
six-month
is
n
minus
six
and
you
can
see
what
our
percentages
look
like
so
effectively.
B
B
J
Yes,
so
I
just
had
a
quick
question
on
comparing
a
customer
running
a
private
AWS
instance,
which
is
very
common
and
what
would
be
the
Delta
if
they
move
together,
comm
specifically
so
I
noticed
that
AWS
has
done
this
with
their
own
TCO
calculator
from
moving
from
a
pram
to
AWS.
That's
helped
them
scale
into
the
billions
of
Revenue
and
I'd
love
to
understand.
Do
we
have
a
similar
way
to
measure
hey?
J
B
So
we
should
so
that's
a
great
idea
and
we
should
get
an
issue
open
up
and
went
up
after
this,
and
unless
you
would
like
to
but
effectively
there,
there
will
be
a
cost
savings
right,
because,
right
now
our
customers
have
to
pay
for
all
their
compute.
They
have
to
have
someone
to
maintain
it
and
look
after
it.
We
do
know
that
overall
customers
appreciate
the
fact
that
lab
is
relatively
low
maintenance
from
our
glass
cab.
B
That
person
also
need
someone
to
maintain
and
manage
over
all
like
the
settings
groups
and
things
like
that,
but
but
yeah,
that's
a
great
idea,
be
a
good
story
to
pitch
for
help
them
to
help
ship.
Splashmore,
calm
released,
make
sure
they're
aware
of
the
benefits
good.
They
could
receive
perfect.
Thank
you.
Yeah
thanks
great
question.
G
G
So
if
you
were
looking
for
all
the
install
types
like
normalized
up
to
a
hundred
percent
yeah
of
that
hundred
percent,
how
many
would
be
on
the
bus
I
mean
how
many
would
be
helm
and
just
by
looking
at
slide,
seven,
it
looks
like
a
very,
very,
very
small
percentage
of
those
would
actually
be
a
helm
installation
I
mean
you
can
barely
even
see
the
line
on
that
graph.
So
just
curious
like
what's
the
like?
What's
the
desire?
Do
we
have
an
opinion
on
where
we'd
like
to
see
that
trend?
G
B
Sure
so,
if
you
go
onto
the
chart
in
periscope
you
can
click
and
disable
the
other
lines.
You
can
actually
compare
them
directly.
We
have
right
around
1400
Helen
chart
install,
so
these
just
thing
turned
on.
It
is
growing
a
pretty
a
pretty
solid
clip.
So
a
is
accelerating
but
I'm,
not
sure
I'm
gonna
push
people
towards
proven
at
this
point
in
time.
I
think
it's
maintaining
and
troubleshooting
and
operating
a
companies
instance.
B
If
you
aren't
familiar
Burnett,
is
it's
probably
going
to
be
a
challenge,
and
so
we
have
the
recommendation
or
documentation
to
kind
of
maybe
not
consider
get
lab
your
first
application.
We
try
and
run
increments
if
you
haven't
done
anything
before
it's
a
fairly
complex
service.
So
that's
the
current
recommendation.
We
have
just
because
we
kept
getting
I,
give
a
fairly
support,
load,
I.
Think
as
we
improve
our
documentation,
they
still
a
lot
of
areas
to
improve
on
Docs
and
I.
Think
as
we
again
routes
that
out
as
more
companies,
not
much
blur
Freight.
B
B
L
To
just
throw
a
comment
on
that
as
well,
that
I
think
one
thing
that
that
we
don't
maybe
sell
enough
or
let
customers
be
aware
of
is
the
ability
to
start
on
omnibus
and
then
migrate
to
a
cloud
native
environment
using
it.
You
know
an
external
database
there's
the
ability
to
peel
off
the
services
kind
of
one
at
a
time,
in
certain
circumstances,
we're
still
working
on
supporting
that
and
and
what
that
looks
like
long
term.
L
B
So
over
time,
thank
you.
Everyone
and
also
they're,
just
kind
of
last
tidbit
there
is
that
we're
continuing
our
journey
with
combat
kubernetes,
and
so
as
we
continue
that
we're
learning
some
new
things
and
we're
finding
some
issues
and
we're
fixing
them
so
once
that
wraps
up
and
well
again
have
a
little
more
confidence
to
strongly
recommend
good.
Ladies,
but
yeah
thanks,
everyone
appreciate
the
questions.