►
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
I
am
the
manager
of
technical
marketing
team
here
at
gate,
lab
technical
marketing
team
as
part
of
strategic
marketing,
and
this
is
the
strategic
marketing
group
conversation
for
April
2020,
so
welcome
everyone
before
we
get
started
as
people
are
putting
in
their
questions.
I
just
wanted
to
do
a
shout
out
and
say:
happy
Earth,
Day
to
everybody
happens
to
be
that
today
go
plant
a
tree
or
recycle
something
or
clean
up
a
park
or
just
take
a
walk,
but
stay
six
feet
apart
from
everyone.
A
B
A
C
Are
we
gonna
move
to
kind
of
that
way
of
presenting
maybe
on
our
github
versus
give
up
page,
and
the
other
question
is
kind
of
how
broad
do
we
make
these
comparisons?
Because,
for
example,
if
we
compare
with
Basecamp
we
have
like,
we
have
merge
requests,
they
don't
have
it
I
think
it's
a
good
point
like
we're
much
broader
application,
but
then
specifically
saying
they
don't
have
merge,
request
feature
a
B
and
C
like
yeah.
They
skim
doesn't
have
hold
the.
D
E
F
So,
yes,
we
are
going
to
use.
You
know
a
background
that,
like
you
see
behind
me,
but
you
know:
you're
gonna
have
you're
gonna,
be
comparing
at
the
use
case
level,
so
source
code
management,
CI,
CD,
dev,
sir
coughs,
that
you
know
that
sort
of
level
of
demarcation.
So
the
very
first
graphic
you
see
would
be
every
use
case.
G
F
That's
the
first
main
thing:
I'm
Rob
right
out.
The
second
thing:
there's
some
background
noise.
If
you
don't
mind
muting,
please
thank
you.
Like
thanks,
Ashish,
the
second
thing
is
you're
right.
The
very
first
panel
is
going
to
be
at
the
use
case
level.
So
for
a
base
camp
you
will
find
you
know,
use
cases
where
they
don't
participate,
so
it'll
be
very
apparent.
The
idea
is
to
make
it
apparent
for
some
of
these
point
tool,
vendors,
that
they
don't
participate
in
the
entire
breadth
of
what
DevOps
tools
are
supposed
to
do.
F
So
the
very
first
panel
would
have
at
that
level
so
that
we
can
wait
digging.
Users
can
very
quickly
distinguish
the
fact
that
they
have
very
narrow,
offering
versus
our
broad
offering
and
then,
when
you
click
on
an
individual
tab,
obviously
there
will
be
a
you
know,
lower
level
comparison
as
it
pertains
to
that
particular
use
case.
F
F
F
F
The
reason
why
we
went
to
the
model
that
you
see
behind
me
or
my
background
is
that
today,
at
the
rest
of
the
comparison
site
follows
that
model.
So
we
didn't
want
to
inject
a
new
framework.
You
know
when
we
put
the
graphic
out,
so
that's
why
we
wanted
it
to
be
consistent
as
of
now,
but
eventually
it's
going
to
be
moving
over
to
our
use
case
based
model
where.
H
H
So
this
is
slide
number
four,
very
briefly.
What
a
use
case
is
or
attempt
to
define.
You
know
what
exactly
is
a
customer
problem
that
is
well-defined,
that
a
customer
service
solved.
So
we
often
talk
about
the
value
that
given
lab,
brings
to
our
customers,
and
we
talk
with
the
features
on
how
they
can
help
solve
those.
But
the
use
case
actually,
very
briefly,
is
like
the:
what
of
the?
What
is
the
exact
problem?
How
is
the
best
articulated
by
a
customer
in
their
language?
How
does
the
industry
define
it?
H
You
know
focus
right
on
that
use
case.
The
use
cases
could
be
I
wanna
solve
for
managing
my
code
and
intellectual
property.
I
wanna
like
break
my
bells
better
I
want
to
incorporate
security
into
it,
so
slide
four
and
five
giving
good
overview
of
that,
and
then
we
provide
a
link
right
now.
That
goes
to
the
handbook
page
that
describes
the
use
case
in
much
more
detail
and
all
the
use
cases
that
are
underneath
this.
Hopefully
that
answers
the
question.
C
A
H
A
You
want
to
come
up
that
that
that
we,
you
know
we're
watching
for
that
all
the
time.
So,
for
example,
on
slide
five,
it
mentions
new
use
case
remote
software
development
wasn't
on
our
radar
as
a
as
a
a
customer
movement
that
we
were
getting
a
lot
of
traction
on
I've
been
talking
to
to
folks
at
first,
but
with
code
nineteen
that
became
a
much
bigger
thing
to
focus
on,
so
that
moved
up
in
priority
became
something
about
focusing
so
slide.
A
Five
does
talk
about
here's
kind
of
the
prioritization
that
we've
done
around
the
the
keys
cases
that
we're
hearing
from
sales
and
customers
and
folks
we're
talking
to
that.
We
should
make
sure
that
we
have
good
assets
for
slide.
Six
is
is
illustrating
this
is
the
Bill
of
Materials
that
we're
creating
for
there's
about
thirty
five
assets
for
each
use
case
from
from
resource
pages,
with
information
about
about
the
market
requirements
which
are
key
piece
of
this
all
the
way
to
demos
and
competitive
information
created
in
that
space.
A
So
when
a
customer
comes
to
or
talks
to
a
sales
person
or
marketing
person
about
a
particular
use
case,
they
have
a
challenge
with
then
you
know
you
get
obstinate
infrastructure
or
or
I
need
help
securing
and
versioning
my
development
assets
right.
Then
we
will
have
a
set
of
content
ready
to
go,
that's
all
linked
together
and
that
that's
that's,
that's
ready
to
go
for
that,
and
so
that's
that's.
What
slide
six
is
illustrating
slide.
C
A
So
I
keep
east
of
the
use
case.
Is
the
the
next
level
break
down
into
okay
proof?
So
if
there's
this
particular
problem
that
a
customer
houses
are
trying
to
solve
what
are
what
we
call
the
market
requirements,
not
a
necessary,
you
can
call
the
market
capabilities
we're
trying
to
not
overlap
with
some
terms
that
are
already
out
there
that
are
necessary,
regardless
of
what
gitlab
has
right.
This
is
what
competitors
will
come
with
the
you
know.
C
E
That's
all
next,
thanks
team
put
the
information
together.
The
the
question
is:
what
specific
content
are
we
seeing
kind
of
getting
the
most
views
from
prospects?
And
let
me
give
a
little
bit
of
background
myself
in
andrew.galea
st
are
working
to
do
some
open
activities,
obviously,
and
we
want
to
kind
of
mirror
what
we
see
prospects
asking
us
for
from
information,
so
we
can
kind
of
give
back
so
I
didn't
know
if
any
of
the
content
is
like
hey.
E
H
I
will
answer
that
I
should
have
the
answer
based
on
the
metrics.
We
have
on
our
content:
I
don't
have
it
on
the
top
of
my
head.
We
get
back
to
you
with
the
definitive
top
three
to
five
pieces
of
content
that
I've
highest
views,
but
in
general
we
know
that
giving
demos
or
documentation
pages
blogs
and
thought
leadership
papers
have
very
high
views.
The
comparison
page
is
also
coming
pretty
close.
I
think
we
have
the
numbers
of
that.
Recently.
We
looked
at
about
4,000
views
per
month.
F
H
A
You
know,
content
team
has
some
really
great
stuff
and
topic
pages,
and
so
the
idea
is
to
look
across
all
of
those
and
get
those
in
the
place
where
we
can
see
the
path
not
just
path
factory,
where
we're
serving
them
a
set
of
things,
but
also
as
they're
hitting
our
website.
What?
What
is
the
path
that
they're
following?
What
are
they
looking
at
so
that
by
the
time
they
get
to
in
str
o
or
to
you
that
you
have
a
sense
of
like
okay?
A
How
far
did
they
go
down
a
learning
path
that
we
provided
for
them?
How
much
of
this
particular
content
did
we
did
we
look
at
so
early
in
that?
But
that's
that's
what
we'd
like
to
get
to
is
that
when
you
get
a
lead,
it
has
more
rich
information
about
what
they've,
what
they've
touched
and
gone
after.
E
Doesn't
seem
like
a
trend
in
like
get
up
starting
to
go
like
this.
We're
gonna
mirror
our
outreach
on
get
ops
or
you
know,
could
be
deaf
cyclist
or
whatever
it
is.
So
it
helps.
We
see
that
uptick
in
you
know,
customers
or
prospects
pulling
information
from
us
or
viewing
content
will
just
merit
from
an
outbound
standpoint
as
well.
So
that's
the
aspect.
Thank
you.
Dan
absolutely.
A
Yeah
we
and-
and
we
have
that's
a
great
example-
we
have
seen
that
right
and
right
now
it's
where
we're
hearing
it
from
from.
Like
you,
you
know
your
team
when
you
share
it
with
us
and
when
we
talk
to
folks
and
so
like
as
an
example
we
pulled
get
up
because
we
were
seeing
that
happening
with
get
ups.
We
pulled
get
ops
forward
as
a
use
case
that
we
are
prioritizing,
so
we
started
it
earlier
in
the
mid
quarter
because
it
was
dude.
A
It
was
set
for
a
second
quarter
start,
and
so
that's
that's
an
example
of
a
reaction
to
that.
The
idea
of
getting
more
metrics
that
are
like
less
about
you
know,
hey
we're
hearing
this
from
from
several
places,
but
more
about
hey.
We.
We
know
this
because
we're
seeing
the
data
not
as
where
we
want
to
thank.
E
G
Next
one,
and
just
one
say
thank
you
for
your
team
Ashish.
We
always
love
the
work
that
your
team
does.
So
thank
you
there,
but
one
of
the
things
I
was
saying
in
sales.
We've
always
been
taught
to
focus
on
capabilities
and
benefits
that
a
better
customer
gets
rather
than
a
feature,
because
a
feature
can
always
be
built
by
someone
else
can
compete
again.
So
I
know
your
team's
aware
of
those
kind
of
things
I
just
saw
it
fits
more
with
the
use
case.
Studies
sounds
like
John's
got
an
answer
on
that
side
of
things.
I
John
I'll,
just
chime
in
and
verbalize
the
answer
to
and
share
quick
do
quick,
green
share
as
we're
building
the
use
cases
out
we're
thinking
outside
in
from
the
way
the
market
is
viewing
and
thinking
about
it,
and
so
that
that
leads
us
then
to
the
ability
than
to
decompose
into
say,
for
this
example
would
be
from
for
automating,
build
and
test
for
the
CI
space
of
how
do
we
break
it
down
into
this?
The
requirements
which
will
help
to
drive
comparisons
but
it'll
also
help
drive,
ROI
and
value.
I
So
it's
exactly
what
you're
asking
for
I
think
is
a
way
to
uplevel
the
messaging
and
talk
about
it
like
this,
and
so
we
think
that
the
and
we
believe
that,
as
we
build
these
use
cases,
the
the
market
requirements
will
be
a
derivative
and
we
can
derive
from
it.
Both
you
know,
Dan's
team
is
building
demos.
I
Let
me
show
you
the
I'll,
go
back
to
one
page
and
show
you
the
the
output
or
how
we
think
the
output
of
that
flows,
sorry
about
the
scrolling,
but
the
the
market
requirements
would
flow
to
both
comparisons,
which
Mahesh
is
driving
input
into
ROI
models
and
then
also
blogs
and
demos
and
other
content
specific
related
to
that.
So
all
of
this
to
help
you
help
foster
those
conversations.
D
Oh
I
think
I
have
the
next
question:
kudos
Dan
I
love
the
video.
It
was
super
helpful
in
preparing
for
this
discussion.
Yeah
I
asked
about
where
the
dries
for
the
use
cases
are
and
I
think
William
responded
with
where
they,
where
they
specifically
are
in
the
handbook.
I
would
appreciate
it
if
those
would
be
updated,
especially
on
the
use
case
pages
themselves,
as
like
they're,
largely
aligned
to
how
the
product
organization
is
structured,
none
and
they
shouldn't
be
100%
aligned,
but,
as
PMS
are
reviewing
those
use
case.
I
I
got
it
for
action.
I'll
do
that
and
the
other
thing
I
when
you
read
those
pages,
the
intent
of
the
way
we
laid
those
pages
out,
the
top
half
of
it
up
to
the
market
requirements
is
really
intended
to
be
the
kind
of
the
view
of
the
market
and
then
the
bottom
half
of
it
is
more
how
we
answer
our
different
chairs,
our
messaging
and
things
how
we
positioned.
So
that's
the
intents
of
the
way
we
tried
to
structure
it
as
well
as
we
as
we
iterate
on
building
these
yeah.
I
D
Totally
agreed
and
I
think
that
I've
already
heard
some
pianos
have
have
concern
about
that
view
of
the
market
being
duplicative
of
our
direction
pages,
but
they
shouldn't
be
one
should
be
about
where
we're
headed
and
I
think
another
can
be
a
more
immediate
description
about
what
customers
are
experiencing
today,
so
I
think
there's
good
separation
there,
but
just
knowing
who
the
person
the
content
owner
is
would
be
helpful.
Thanks.
Thank
you.
G
This
I'm
back
sorry
to
do
this,
but
you
know
I
always
have
to
leave
a
little
hockey
in
here
somehow
some
way
for
those
those
completely
deprived
people
in
hockey
today,
but
one
of
the
things
I've
been
watching,
then
HL
has
done.
Some
there's
been
a
lot
of
unique
ways
that
people
reached
out
and
done
things
differently.
Then
HL
actually
does
something
really
cool
that
they
put
the
players
on.
They
do
chats
between
the
players
and
like
fans,
can
ask
questions
and
things
like
that.
I
was
just
thinking
about
that.
G
H
John
thanks
well
that
suggestion
I
think
there's
broader
in
force
across
marketing
on
that.
But
this
is
an
example
and
you'd
be
aware
of
this:
maybe
not
everybody,
but
we
had
planned
an
in-person
customer
advisory
board
that
was
going
to
last
one
and
a
half
days.
We
converted
that
into
a
half-day
worship,
customer
advisory
board
meeting
yesterday,
wonder
if
cam,
lock
or
monitor
on
the
cob
camp.
Do
you
want
to
give
it
a
color
to
that
unit?
I
am.
J
And
I
can
the
discussions
that
were
able
to
have
virtual
were
a
great
opportunity
but
I
understand
exactly
where
John's
looking
for
this,
it
would
be
great
if
John
can
I
interpret
what
I
was
hearing
you're
good
with
that
I
think
what
John
is
saying
is
hey
if
we
advertise
a
session,
we're
like
customers
of
that
are
not
necessarily
cab.
Members
could
come
and
ask
those
questions
publicly.
Is
that
what
you're
saying
we
live
stream?
That
is
that
kind?
What
you're
hinting
at
yeah.
G
Something
like
that,
you
know,
get
lab
TV
with
our
product
team
and
you
know
in
CI
CD
today,
and
people
can
come
in
and
see
what
we're
working
on
hey.
Here's
the
features
coming
this
month-
and
you
know,
talk
about
those
kind
of
things
we're
coming
in
the
next
month
that
we're
working
on
hey,
we'd
love
to
have
your
feedback
sort
of
like
a
live
representation
of
what
we
do
on
our
upcoming
releases
page,
but
doing
a
TV
type
format.
J
J
G
Had
four
players
from
Boston
on
yesterday
and
they
know
they
talk
about
growing
up
in
Boston
and,
and
you
know
so,
sort
of
like
a
behind
the
scenes
get
to
know
them
a
little
bit
more
personal
kind
of
thing
what
life
is
like
at
home
for
them?
Well,
we
have
a
lot
of
people
that
work
in
that
way
and
interesting
for
people
connect
what
to
get
that
team.
K
First
of
all,
I
just
want
to
start
off
by
saying
thanks
to
the
strategic
marketing
team,
I
really
love
the
content.
You
have
put
out
and
use
it
every
day
in
conversations.
Thank
you.
So
much
I
did
want
to
ask
if
and
where
and
how.
We
see
a
better
together
story
with
our
partners
that
we
have
in
market
today
and
how
that
fits
into
the
use
case
strategy
and,
if
there's
anything,
that
the
Alliance
team
can
do
to
help.
A
You
she
had
that
yeah.
So
there
are
some
answers
there,
I,
don't
know
Tina's
actually
on
the
call
all
right
now,
she's
at
a
partner
thing,
I
think
but
yeah
I'll.
I
Jump
on
it,
because
Tina
and
I
have
we've
been
working
on
this
a
lot
and,
and
so
the
lack
that
this
is
really
really
valid.
It's
one
of
the
reasons,
and
we
look
at
get
ups
as
we
go
forward,
because
this
is
a
use
case
where
we
really
do
have
a
key
partner,
we're
together,
where
we
are
better
together
with
the
partner
and
that's
what
this,
what
we're
trying
to
focus
on,
and
so
as
we
develop
the
use
case,
the
the
market
requirements
are
outlined.
I
What
does
the
market
look
for
in
this
kind
of
a
solution
and
then,
as
we
look
at
where
we
are,
and
how
do
partners
help
to
fill
in
is
where
we
see
these
opportunities
to
start
to
highlight
that
story
and
to
build
that
story
out,
and
so
each
one
of
the
use
cases
is
we
build
out
the
use
cases
we
have.
We
have
a
couple
of
points
we
were
looking
specifically
at.
Where
do
we
have
that
partner?
Where
does
a
partner
fit
into
it
and
I?
I
Think
we'll
see
this
in
you
know
it's
some
level
there's
some
parts
of
perhaps
in
the
deficit,
cops
ones
where
there's
some
partner,
you
know
elements
of
it.
There's
also
you
get
ops
I
think
is
the
most
is
one
that,
where
it's
going
to
be
most
significant
and
it's
one
that
you
know
Williams
on
point
working
on
as
we
go
forward
so.
A
K
When
I
think
about
use
cases
and
reviews
from
the
content,
that's
why
he
presented
so
many
partners
come
to
mind.
I
think
there's
a
less
amount
of
possibilities
and,
of
course,
we
need
to
be
Khadijah
Khan
on
how
we
kind
of
positioned
ourselves
with
their
partners
and
that
better
together
story,
but
I'm.
I
I
A
All
right,
unless
there
are
any
other
questions,
that
anyone
has
that
they
want
to
speak
out,
there
are
no
more
in
the
doc.
We
are
about
three
minutes
to
the
end
of
the
meeting.
I
won't
call
it.
Thank
you
very
much
everyone
for
your
time
and
attention
and
for
your
input
and
your
comments
always
appreciated
have
a
great
day.