►
From YouTube: Growth 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).
A
A
Can
we
do
it
exactly
when
the
call
starts
not
one
minute
before,
because
it's
just
it's
very
bad,
watching
like
a
minute
of
nothing,
you
should
have
to
go
to
your
content
works
there
SpaceX
because
they
got
a
great
content.
I
think
we
need
to
try
a
bit
harder
and
just
start
them
exactly
at
8
o'clock
and
also
give
a
bit
of
a
countdown.
So
the
person
make
sure
the
person
who
will
speak.
Is
there
then
give
them
a
countdown?
A
A
C
D
D
We
were
reading
on
a
privacy
policy
decision
to
be
made
by
implementing
pendo
we're
gonna
start
tracking
user
level
information
in
a
new
way
and
so
took
a
bit
of
time
to
arrive
at
a
at
a
decision
on
how
we
were
going
to
interpret
that
policy
and
implement
it.
That
decision
was
made
about
a
week
ago,
and
so
we're
now
in
across
of
rolling
that
out.
That
involves
updating
our
sign-in
process
to
have
a
checkbox
for
opt
in.
It
involves
a
cookie
bar
being
presented
to
people
in
gdpr
regions.
D
I've
involves
an
email
update
out
to
customers
and
involves
a
blog
post
that
we're
going
to
use
pendo.
There's
a
bunch
of
teams
involved
in
rolling
this
thing
out.
Tim,
hey
has
an
epic
and
a
bunch
of
issues
tracking
that,
as
well
as
a
single
project
and
so
I'll.
Let
Tim
weigh
in
with
any
details.
I
might
have
missed
yeah.
C
C
F
Just
saw
them
there
that
you
noted
the
fastboot
in
Vancouver.
No,
we
spent
a
fair
amount
of
money
on
it
got
a
lot
of
people
together.
I
saw
some
really
positive
things
in
regards
to
the
fact
of
we
define
a
lot
of
process
of
how
we're
gonna
work
together,
because
this
is
a
new
team
and
other
aspects,
but
I
wanted
to
see.
If,
if
we
you
know
the
feedback
is,
is
this
has
really
helped
us
accelerate
and
did
we
learn
anything
novel
from
the
experience
I.
D
I,
don't
have
any
doubt
it
helped
us
accelerate
the
average
tenure
on
the
team
at
the
time
we
had
that
was
probably
about
a
month.
So
it's
a
lot
of
new
people
all
trying
to
figure
out
how
to
work
together
all
trying
to
figure
out
how
to
work
as
a
growth
team,
which
is
has
some
unique
elements
from
a
typical
development
team,
so
enabled
us
to
get
everyone
on
the
same
page
about
the
KPIs.
We
were
all
driving
stitute.
So
what
are
our
North
Stars?
D
How
are
we
going
to
work
just
get
to
know
each
other
and
we
spent
three
and
a
half
days
out
of
the
five
actually
building
stuff
so
the
first
day
and
a
half
was
getting
aligned
and
making
sure
we're
all
on
the
same
page
about
our
goals
and
then
three
and
a
half
days
of
smaller
teams
breaking
out
and
building
stuff.
There's
a
fastboot
update
that
Bartek
made
to
the
to
the
hanbĂ´
with
links
to
a
bunch
of
the
stuff
that
got
done.
We
shipped
a
few
things
there.
G
Yeah
I
just
said
that
go
what
Scott
said:
I
thought
it
was
really
useful
to
get
us
all
together.
There
get
to
know
each
other,
a
line
around
the
experiences
that
we're
having
today
and
the
opportunities
that
we
have
to
improve
those
and
get
everyone
marching
in
the
same
direction
and
really
excited
and
energized
about.
You
know
the
opportunities
we
have
in
front
of
us,
so
I
mean
for
me
personally
being
about
a
month
in
at
the
time
it
was.
It
was
really
useful
and
we've
we've
hit
the
ground
running
since
then.
G
A
Is
this
Auto
DevOps?
Is
this
our
distribution
team,
it's
kind
of
between
the
things,
but
someone
should
highlight
them
and
right
now
it's
my
co-founder
doing
that
I
think
this
is
probably
should
be
caught
in
the
future
by
kind
of
a
UX
review,
they're
doing
great
job
of
reviewing
jobs
to
be
done
or
by
a
product
manager
speedrun.
That
kind
of
shows
how
to
get
from
nothing
to
something
you
know
up
by
the
growth
teams,
but
it's
a
it's
an
inhabitant,
a
kind
of
acquisition,
so
I
wonder
what
whether
we
aligned
on
that
is
this.
D
D
A
Yeah,
so
probably
not
the
experienced
teams,
though,
and
Chrissy's
already
doing
this
in
the
UX
experience
baseline
team
and
I'm
also
expecting
p.m.
speedruns
in
the
future.
So
I'll
stop
bringing
this
up
to
the
acquisition
team.
The
next
question
as
well:
do
we
think
it's
okay
to
send
user
events
from
get
lab
ee?
A
I
think
right
now
we're
kind
of
gearing
up
to
do
that
at
pendo
and
we're
kind
of
snowflake
sending
events
of
individual
users
at
a
certain
point
in
time
back
to
ourselves
and
back
to
a
third-party
registry
or
back
to
a
third-party
service.
In
the
case
of
endo
I
think
people
will
be
furious
when
they
hear
this
but
I'm
hearing
other
opinions
and
just
want
to
ask
ask
the
questions
we're
going
to
do
a
blog
post
about
it.
Ask
people
but
I
wonder
what
people
are
thinking.
A
E
C
C
So
it's
not
going
to
be
an
opt
out
for
this
right
out
of
the
gate.
It's
gonna
be
opt
in,
so
they're
gonna
actually
have
to
verify
that's
happening
now.
The
users
who
are
rolling
up
under
those
instances
of
EE
well
they're,
probably
employed
by
that
person,
so
I
think
it's
up
to
the
employer
to
kind
of
manage
that
message.
Internally.
That's.
A
Great,
that's
this.
Those
are
two
great
things
making
it
I
think
at
some
point,
we're
going
to
make
it
uptown,
but
starting
opt-in
is
good,
especially
if
we
set
the
expectation
look.
This
is
going
to
be
opt-out
in
the
future,
but
we're
starting
like
this
and
I
love
the
idea
of
giving
value
back
so
I
think
those
are
two
great
things
both
of
those
things.
I
did
not
see
in
the
blog
post.
A
I
think
it's
we're
being
a
bit
super
extra
nice
by
saying
that
we
do
this
on
a
saw
service,
I.
Think
a
lot
of
saucers
just
do
this!
I
never
have
a
blog
post
about
it.
So
I
think
people
will
be
upset
about
the
saw
service
as
well,
but
I
think
that
will,
if
you
dig
into
the
data
I
think
every
very
many
saw
service
are
doing
this
I.
Don't
think
it's
that
uncommon.
A
If
we
make
it
opt-in
for
self-managed,
then
I
think
that
takes
away
a
lot
of
the
immediate
pressure
yeah
and
if
we
give
data
back
to
be
great
so
but
I
didn't
see
those
in
the
tool
in
the
blog
posts,
I
expected
the
blog
post.
You
have
a
more
negative
response,
so
let's
close
that
loop
and
have
that
in
there
it's.
D
A
E
A
Now,
when
we
sent
out
the
pink,
we
do
all
the
queries
they
all
timeout
and
then
it
doesn't
get
sent
out.
Are
we
what's
what's
our
progress
and
this
has
been
around
for
a
while?
So
can
we
are
we
gonna
kind
of
do
the
query,
store
them
in
the
database
and
then
send
out
the
usage
ping
itself
only
sense
out
of
the
data
or
something
like
that
in
the
middle
of
this
one
I
sure.
C
Am
I
sure
AM,
so
there's
a
handful
of
issues.
I
guess
I
could
link
one
of
them
in
here,
but
it's
count
use
unique
users
for
more
accurate
s,
Mau
reporting,
but
it's
all
about
usage
ping,
for
instance.
So
we
are
working
on
it
said.
Let
me
let
me
get
those
links
in
here.
So
that
way
you
can
have
some
visibility
until
what's
happening,
but.
A
A
C
A
A
Why
not
like
what
why
we've
this
seems
such
an
the
usage
being,
has
been
broken
for
the
calm
now
for
half
a
year.
That's
not
your
your
problem,
but
it
seems
such
an
obvious
thing
to
do.
What's
standing
in
the
way
of
normally
when
something
obvious
isn't
happening,
I'm
missing
something
maybe
I'm
missing.
C
H
To
provide
a
little
bit
of
engineering
background
than
that,
we
were
doing
a
lot
of
experimentation
with
snowplow
and
seeing
a
snowplow
an
event
like
having
an
event-driven
sort
of
data
would
be
better
than
using
usage
pain.
So,
throughout
the
history
of
telemetry,
we've
had
a
couple
of
PN's
rolling
it
out
and
I.
H
Think
the
there
was
a
general
consensus
that
we
wanted
to
investigate
snowplow
as
being
an
alternative
and
maybe
something
that
we
ultimately
move
towards.
Instead
of
using
the
usage
pain
before
both
recording
of
self
managed
and
allowing
self
managed
admins
to
be
able
to
review
their
own
performance.
So
that's
I
think
why
it's
not
been
prioritized
yet
because
we
were
talking
about
other
things
around
it.
If
that's
helpful,
yeah.
A
That's
super
helpful,
I,
intuitively
I
would
say
people
are
much
more
likely
to
allow
aggregate
data
to
get
sent
back
than
individual
data.
That's
way
more
sensitive,
so
I
think
fixing
what
we
already
have
and
making
sure
it
actually
works
should
should
not
be
should
have
been
a
priority
instead
of
just
trying
to
go
for
that.
A
great,
a
more
intrusive
thing,
but
I
think
we're
realizing
that
as
well,
so
that
we're
making
that
adjustment.
I
D
Being
considered
in
a
couple
of
contexts,
one
is:
should
we
have
an
always-on
license
ping
where
customers
have
to
phone
home
for
license
related
stuff?
It's
unclear
whether
we
would
include
usage
ping
in
there.
Secondly,
might
we
bundle
this
with
the
way
that
we
provide
support
like
hey
in
order
to
provide
great
support?
D
We
need
data
about,
what's
going
on
in
your
instance,
I
think,
if,
if
positioned
this
way,
along
with
providing
great
support,
it
might
have
might
be
more
palatable
to
most
customers,
I
think
in
all,
in
all
cases,
we'll
need
the
ability
to
turn
it
off
work
for
specific
customer
types
like
government,
so
I,
don't
imagine
us
getting
to
a
point
where
we
can't
turn
it
off
at
all.
But
if
we
surround
it
with
enough
a
value
like
better
support,
a
better
licensing
experience
I
have
to
imagine.
D
A
And
what
use
instead
of
calling
an
always-on
license
being
I've
heard
the
term
cloud
license
provisioning
things
like
that?
Maybe
we
that's
not
a
super
catchy
name
and
anything
that
cloud
is
kind
of
diffused,
so
you
might
want
to
think
about
it,
a
more
catchy
name
to
that
to
make
sure
everyone
is
using
that
yeah.
J
Following
up
on
Pindo,
because
the
comment
was
made
that
it's
rolling
out
for
calm,
only
or
initially
I
guess
two
points
there
like
timeline
and
follow-on
for
self-managed
and
I
guess
my
other
question
would
be.
Why
are
we
doing
calm
before
self-managed
I
would
say?
Self-Managed
is
like
arguably
from
a
p.m.
perspective.
D
C
Just
Java,
so
we
can,
we
can
add
it
to
it.
It's
just
the
opt-in
issues
that
that
come
around
it,
so
we
can
absolutely
move
forward
with
it.
We
were
going
to
test
it
on
calm,
first,
get
it
all
set
up
and
configure
get
people
trained,
and
then
we're
going
to
try
to
roll
it
out
to
EE
afterward
I
can
look
at
condensing
it
and
and
launching
them
on
both.
At
the
same
time,
that's.
A
A
H
There's
also
a
couple
of
licensing
challenges
around
that
I
believe
have
come
up
in
several
of
the
issues
around
pendo.
It
can
potentially
leak
proprietary
information
from
your
self-managed
installation,
and
so
the
likelihood
of
people
opting
internet
is
fairly
small.
So
we
want
to
sort
of
investigate
how
people
feel
about
it
when
we
roll
this
out
on
comm
and
then
what
the
sort
of
result
might
be
if
we
try
to
introduce
it
to
self-manage.
So
there's
a
lot
of
license
and
legal
concerns
there.
B
If
I
might
just
add
a
comment
here,
the
value
of
right,
aeration,
I'm,
not
sure
if
this
has
been
considered,
but
in
terms
of
open
source
projects
using
some
sauce.
The
synthesis
of
of
ie
I
think
this
will
be.
This
might
be
of
concern.
So
it
might
be
a
good
idea,
in
any
case,
to
learn
from
what
happens
with
rollout
of
a
Kesari
of
calm
and
seeing
simulations
that
we
or,
if
there's
anything,
that
we
need
to
adjust
for
for
self-hosted.