►
From YouTube: Enablement Group Conversation (Public Live Stream)
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
Hi
everyone-
this
is
Joshua
Lambert,
a
group
manager
of
product
for
enablement,
and
this
is
the
enablement
section
group
conversation.
We
are
live
streaming
to
YouTube
publicly,
just
as
a
heads
up
and
these
slides
are
available
in
the
document.
So
please
review
those,
and
thanks
stand
for
the
first
question.
A
slide
for
maturity.
Chart
shows
an
improvement
going
to
q3
and
then
no
other
improvements
going
forward.
I
think
one
the
primary
causes
for
so
I
think
Bob
Ian's
already
commented
thanks.
A
Bobbing
is
that
we
just
got
the
enablement
section
to
appear
on
the
maturity
page
that
wasn't
happening
before
or
a
non
DevOps
stage.
I'm
sorry
I
should
have
you
read
these
going
for
it?
How
do
you
voice
your
question
next
time?
Thanks
my
first
time
hosting
a
GC,
so
I'll
do
that
going
forward,
but
but
yeah
so
we're
working
towards
getting
us
up.
A
B
Great
thanks
for
asking
the
question
so
I
think
this
is
I
think
as
Josh
already
said,
probably
just
a
mistake,
as
we
haven't
defined
a
time
yet
to
when
it
goes
from
complete
to
love
ago.
So
I'll
follow
up
why
this
is
calculated
in
this
way.
But
I
don't
think
this
is
100%
representative,
so
I
apologize
for
that
it.
C
A
Thanks
Jan
thanks
the
question
and
yeah
I.
Think
again,
we
just
got
this
appearing
in
the
page,
with
the
kind
of
the
full
four
quarter
look
here
just
recently,
and
so
we're
trying
to
also
make
sure
we
add
maturity,
States
for
all
of
our
categories
going
forward,
and
so
it's
a
bit
of
a
work
in
progress
here,
as
we
sort
of
start
to
start
to
plan
these
out
and
have
that
present
on
this
page.
A
A
A
D
A
Yeah,
so
thanks
apologize
for
those
those
links,
we'll
get
them
fixed
here
right
now.
Thank
you
play
that
out.
So
the
Search
Group
is
a
new
group,
we're
working
to
form
and
the
intent
for
this
group
is
to
be
responsible
for
the
elasticsearch,
primarily
within
gitlab,
and
so
this
will
be
the
elasticsearch
cluster
that
get
lab
well
utilized
to
provide
global
search
across
all
of
github.com,
and
so
we
also
really
responsible
for
the
global
search
functions
that
then
utilize,
elastic
search
and
so
we're
making
this
a
dedicated
team
right
now.
A
Kai
and
the
great
team
are
doing
a
great
job
and
driving
this
forward,
but
there's
really
some
specialized
skills
and
elasticsearch
around
planning
and
ensuring
that
the
queries
just
set
up
properly,
so
you
can
scale
in
shard,
elasticsearch
and
so
we're
making
this
a
separate
team
to
help.
I
really
drive
that
forward
and
also
make
sure
that
for
our
customers,
who
are
larger,
we
can
also
scale
up
for
them
as
well
like
we
have
to
for,
did
LUN
calm,
and
so
that's
the
goal
there.
A
A
Alright,
so
a
couple
other
quick
notes,
while
I
hopefully
get
some
more
questions
here
on
slide
6
for
telemetry,
you
can
see
some
of
the
existing
literature
that
we
already
had
today
for
a
bit
a
moment
section.
These
are
available.
We
made
an
enablement
topic,
you
know
in
periscope,
and
so
as
as
we
add,
more
charts
here,
you'll
be
can
use
those
to
find
all
things
enable
MIT.
But
right
now
we
have
a
chart
of
active
instances
broken
down
by
the
deployment
type
and
then
also
we
have
percent
of
installations
behind
the
latest
release.
A
A
This
would
be
a
little
bit
interesting
for
things
like
distribution,
for
example,
or
on
how
you
consider
an
active
user,
so
we're
thinking
through
that
and
we're
working
to
find
those
in
that
issue
there.
So
if
you
have
thoughts
or
opinions
or
want
to
follow
along,
please
subscribe
there
I'll
check
back
for
some
questions.
C
I'll,
just
stop
typing
in
Alaska
Thanks
on
slide
7.
The
priorities
when
the
priorities
listed
for
enablement
is
on,
number
four
is
get
logged
can
be
enterprise,
compliance
and
integration
needs.
I'm
kind
of
interested
in
the
integration
needs
part
of
that
like
what's
the
what's
the
thinking
there
are,
we
are
we
talking
about.
C
E
Hey
Dan
thanks
for
the
question
so
that
there
are
a
couple
of
things
there
and
I
think
those
are.
Those
are
both
great
points,
so
the
the
primary
focus
coming
in
is
going
to
be
working
on
some
of
the
integrations
that
we
currently
have
that
our
enterprise
customers
are
most
interested
in.
So
the
number
one
priority
for
me
today
is
JIRA
integration.
E
For
some
enterprise
customers
they
are
completely
locked
into
JIRA
like
there
is
a
0%
chance
that
we
are
going
to
be
able
to
move
them
over
to
something
like
gitlab
for
the
things
they're
using
JIRA
for
for
five
to
ten
years.
Maybe,
and
so
what
we
need
to
do
is
enable
them
to
use
the
gait
lab
product
by
having
a
JIRA
integration
that
is
robust
enough
and
gives
them
a
great
experience
that
they
are
there.
Their
users
are
comfortable.
E
C
That
does
that's
great
detail.
Thanks
Patrick
I'm
excited
to
hear
you
guys
are
getting
rolling,
I'm
kind
of
riffing
off
the
answer.
I
added
another
sub
question:
you
mentioned
the
integrations
for
Jenkins.
Are
we
considering,
or
maybe
it's
too
early,
but
migration
tools,
as
well
as
just
the
actual
direct
integrations
yeah.
E
F
Is
that
just
so
hard
to
use
JIRA
now
that
he's
moved
over
from
github
the
as
I'm
here
today,
I
have
a
bunch
of
people
that
ask
me
the
exact
same
question:
is
there
a
road
map
by
to
actually
improve
on
our
JIRA
integration,
to
be
able
to
come
to
on
par
with
what
it
can
do,
or
at
least
in
their
viewpoint?
So
that's
good
to
hear
that
we're
targeting
those
specifically
so.
E
That's
awesome:
I
have
a
huge
epic
that
I'm
collecting,
JIRA
and
stuff
into
of
try
to
decant
I've
started
to
categorize
it
and
get
secrete
some
themes
for
the
work
that
we're
addressing.
So
yes,
there
is
definitely
some
some
work
that
I'll
link
that
here
want
some
time
talking
and
there's
definitely
a
ton
of
work
that
we've
got
on
our
backlog
for
that
and
the
places
that
they
can
go.
E
Read
about
that,
and
please
please,
please,
if
you
have
customers
that
you're
talking
to
or
potentials
that
you're
talking
to
you
who
are
interested,
please
put
them
in
touch
with
me.
I
would
love
to
talk
to
them
to
hear
their
story
and
understand
their
use
case.
Our
researcher
would
love
to
talk
to
them
to
understand
their
use
case,
so
any
of
those
people,
please
put
them
in
contact
thanks,
Jason.
F
A
So
thanks
the
question
that
metric
comes
out
of
the
usage
pink
and
we
see
I
think
a
file.
That's
even
the
database
like
where
it's
coming
from
and
so
I
think
someone
has
edited
that
that
field
on
their
on
their
home
shirt
and
they
have
to
find
their
own
installation
type
effectively
and
so
you'll
see
you
see
like
I,
think
another
kind
of
interesting
one
is
well
popping
up
in
there,
but
yeah
someone's
define
their
own
installation
type.
Essentially,
it's
why
that's
coming
from
I
believe.
G
Yeah,
so
we
have
any
idea
on
how
many
customers
are
actually
using
our
charts
to
install
clap
on
on
communities,
and
then
you
know
what's
up
what
a
forward
plan
to
improve
maturity
here
is
because
I
know
that
there
are
some
questions
in
slack
regarding
a
customer
is
looking
to
use
this
way
of
installation
instead.
I
think
we
need
to
make
it
mature
test
it
and
burn
it
in.
So,
if
you
have
any
insights
around
going
to
go
for
plan
here,
yeah.
A
So
thanks
the
question,
and
this
is:
you
can
also
see
what
I
show
you
my
screen.
Hopefully
you
could
see
my
browser.
If
not
let
me
know,
but
you
can
see
here's
what
Jason
was
referring
to.
But
actually,
if
you
look
at
this
this
chart,
you
can
actually
isolate
just
the
helmet
art-
and
so
you
can
see
here
is
the
home
chart
data,
and
so
it's
red
up
around
a
thousand
installations
active
installations
that
are
still
recording
in
that
said.
A
Currently,
our
usage
ping
data
is
is
broken,
we're
working
to
fix
it
and
that's
why
you
don't
see
any
data
since
July,
but
you
can
actually
kind
of
follow
along
with
the
helm
chart
installations
here,
so
we
had
a
good
amount
of
growth
there
and
we're
having
some
challenges
with
the
data
feed
from
the
usage
ping
right
now.
But
hopefully
you
help
answer
your
question
there,
a
little
bit
mech
in
the
first
portion,
I'll
stop
sharing,
and
the
second
aspect
is
yes,
we're
absolutely
working
to
improve
this.
A
So
that
was
that
was
fantastic
and
that
will
I
think
continue
as
you
work
to
try
and
move
more
blows
into
Cuban
that
using
so
that
dogfooding
trend
is,
is
moving
forward,
which
is
fantastic,
and
so
we'll
learn
a
lot
there.
As
far
as
other
customers
go,
we
definitely
are
getting
continued
feedback
from
them.
This
is
an
area
of
focus.
I.
A
G
F
A
A
Well,
a
quick
topic
on
the
already
for
questions.
If
we
can
get
some
is
the
the
Geo
team
and
dog
hoodie,
so
we're
going
to
try
a
new
model
here,
going
forward
with
the
Geo
team,
where
the
Geo
team
will
effectively
be
working
to
set
up
geo
for
calm
and
partnership
with
the
infant
team,
and
so
this
is
a
kind
of
new
model
where
the
engineering
team
will
be
spending
some
time
doing
this.
But
we're
excited
to
get
geo
set
up
and
to
get
that
dog
fooding
going.
B
B
B
You
know
things
that
are
good
about
it.
You
know
the
dog
fooding
aspect,
the
disaster,
recovery
aspect.
This
is
something
that
we
want
to
prioritize,
and
so
we
will
keep
you
posted,
but
you
know
this
is
something
where,
rather
than
just
sort
of
servicing
kept
calm
as
an
internal
customer,
we
are
also
providing
some
some
help
more
directly
and
I'm
quite
excited
for
that.
A
Thanks
about
in
check
back
on
the
questions
here,
don't
see
any
more,
so
one
less
comment
here,
while
they
try
and
leave
some
more
questions
and
then
we'll
wrap
up,
if
not
I
just
want
to
also
highlight
we
spoken
about
distribution
and
search.
An
ecosystem
in
geo.
I
also
wanted
to
highlight
the
great
work
that
the
memory
team
has
been
doing
on
site.
F
Sorry
about
the
background
noise
for
a
second,
there
I
wanted
to
point
out
a
couple
things
that
we
actually
learned
from
helm
summit
having
been
here.
What
we
found
out
is
the
talking
points
that
I
really
covered,
which
is
some
of
the
architectural
decisions
that
we've
made
in
the
design
of
the
charts
it's
componentization
and
its
ability
to
be
independently
controlled
for
each
component.
Well,
specifically
for
our
use
case,
which
allows
us
to
actually
begin
the
migrations
piece
by
piece
and
component
by
component
for
the
actual
migration
of
our
SATs
to
our
charts.
F
This
is
actually
something
that
other
large
providers
are
doing
as
well.
They're,
not
necessarily
doing
it
in
such
a
large
chart
as
we
are,
but
I
had
comments
from
IBM
and
Jay
frog
and
Microsoft,
as
well
as
the
Red
Hat
developers
that
what
we're
doing
is
actually
the
kind
of
things
that
they
realized
at
large
scale.
They
have
to
do
so
inadvertently.
We
were
following
along
and
actually
demonstrating
thought
leadership
throughout
the
community
in
helm.
That
dry
pattern
is
what
you
should
be
doing.
A
Thanks
Jason
and
we're
excited
a
learn
more
about
Hell,
mystery,
I'm
sure
going
forward
from
the
home
from
summit
as
well,
but
thanks
everyone
I,
don't
see
more
questions,
so
we'll
wrap
up
a
little
bit
early
appreciate
the
questions
at
the
time
and
you
can
find
us
on
those
slack
channels
referenced
in
the
deck
earlier.
If
you
want
to
learn
more
thanks
for
weekend,
thanks.