►
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
C
You
sheesh
again
welcome
to
the
strategic
marketing
group.
Conversation.
I
will
be
your
moderator
today
and
if
you
have
I
hope
you
have
seen
the
presentation
and
potentially
the
YouTube
video.
If
you
have
any
questions,
please
type
them
in
the
group.
Conversation
agenda
documents
and
I
will
be
there
to
verbalize
and
get
the
appropriate
person
to
answer
that,
for
you.
D
Yeah,
so
maybe
y'all
can
ask
the
first
question:
I
see
that
there's
slide
number
seven
is
about
the
competitive
intelligence,
and
it
says
new
site
replaces
crayon
memorable
URL
about
gala,
become
slash,
compete,
I,
thought
that
we
already
had
compare
comparisons
on
our
website,
so
I'm
kind
of
puzzled.
Why?
This
is
not
on
those
pages,
so.
C
We
do
have
comparisons,
there
are
two
aspects
to
it:
the
DevOps
tools,
comparison
pages
is
on
our
website
and
externally
facing,
and
this
is
on
our
handbook.
Mainly.
The
content
here
is
for
internal
audiences,
such
as
sales
and
marketing
in
others.
So
crayon
was
meant,
for
you
know
our
competitive
intelligence
work
that
can
be
public,
and
this
essentially
replaces
that,
so
the
content
would
be
essentially
locked
and
only
for
a
flatte
personnel.
D
C
It's
one
of
those
things
where
you
know
we
decided
tomorrow
from
crayon,
because
it
was
very
difficult
to
use
and
I
think
at
the
last
group
conversation
or
some
other
meeting,
we
discussed
about
putting
it
up
on
a
web
page
and
making
it
accessible
through
the
website,
rather
than
amount
to
the
hand
book
rather
than
to
a
proprietary
software
and
that's
the
direction
we've
gone.
Yeah.
D
C
This
is
not
a
comparison.
It's
more
around
a
comparative
strategy
around
different
vendors.
You
know
how
we
compete
and
how
we,
you
know,
do
better
in
terms
of
differentiating
ourselves.
A
lot
of
this
information
is
also
present
in
the
DevOps
tools.
Landscape
pages.
This
kind
of
takes
it
to
probably
a
slightly
different
level
of
detail
that
may
be
more
easy
to
consume
for
sales.
A
Another
good
example
might
be,
you
know,
think
about
confidential
data,
that
you
know
either
the
vendor
or
the
customer
that
we're
working.
They
don't
want
to
make
public
and
then,
thirdly,
is
it's
also
in
a
format
that
sales
sometimes
finds
it
easy
to
consume
to
take
to
their
prospects
and
customers.
So
we
have
the
occasional
need
to
provide
to
create
a
deck,
for
example,
and
so
we'll
create
it.
A
D
Yes,
so
again,
I
totally
support
the
move
from
crayon
to
public
web
pages.
I,
don't
understand
why
we
have
about
Kayla
TOCOM,
slash,
compete
and
about
get
Lacombe
slash,
def
of
tools
as
separate
entities.
She
said
lots
of
information
on
compete
is
also
present
on
DevOps
tools
and
I.
Think
it's
super
hard
for
us
to
keep
all
the
information
up
to
date.
I
see
continually
see
stuff,
that's
out
of
date
and
the
way
to
keep
stuff
up
to
date
is
to
have
a
single
source
of
truth.
D
Have
a
single
page
that
you
maintain
otherwise
you're
maintaining
two
pages,
which
is
a
lot
more
work.
It's
not
even
twice
as
much
work.
Sometimes
it's
multiple
times
as
much
work,
because
it's
unclear
what
you're,
updating
and
I
don't
think.
There's
a
restriction
where
we
say:
oh
DevOps
tools
cannot
contain
detailed
information.
We
can
that's
our
it's
our
site.
We
can
be
as
detailed
as
we
want.
No
one's
gonna
complain
if
we
add
too
much,
if
we
add
detail
to
their
and
if
they
do,
you
can
send
them
to
me.
D
A
A
D
D
A
E
D
C
E
Just
think
it's
really.
This
is
Hayden
by
the
way,
I
understand
what
you're
saying
I
just
think.
It's
very
difficult
to
have
one
page
that
serves
both
audiences.
You
know
prospective
customers
existing
customers
and
employees.
How
do
you?
How
do
you
manage
that?
Because
you
know,
as
a
prospective
customer
going
to
be
interested
in
our
sales
strategy
around
a
competing
tool.
D
I
fully
agree,
Hayden
I
think
combining
the
two
things
will
be
a
problem
and
there
will
be
some
people
that
say
yeah.
Well
all
this
information
isn't
relevant
to
me,
however,
I
think
our
biggest
problem
as
a
company
right
now
isn't
that
we
have
information
on
on
a
site
that
isn't
relevant
to
some
people.
I
think
our
biggest
problem
is
that
the
information
we
have
is
not
getting
a
lot
of
love.
I.
Think
our
product
marketing
team
is
focused
very
much
on
the
compete
site
and
on
presentations,
and
this
is
languishing
if.
D
D
We
should
have
something
like
this
on
every
page
and
it
should
probably
be
dynamically
generated,
but
it
feels
like
this
page
has
is
not
getting
the
kind
of
the
love
that
it
it
requires,
and
that's
the
thing
I'm
trying
to
fix
and
I'd
rather
have
an
ugly
page
with
a
lot
of
out-of-date
content
and
then
something
that
was
last
updated
five
months
ago,
because
I
think
our
comparison
would
get
lap.
Github
changed
over
the
last
five
months.
I
think
we
added
five
releases
and
I
think
they
changed
some
things
right
now,
that's
not
being
reflected.
D
F
Correct
me
for
I'm,
not
sure
where
you
were
looking
at,
but
that
page
was
updated
less
than
five
months
ago.
The
graphic
that
we
added
a
page
was
updated
about
a
month
ago.
The
the
other
thing
is
I
believe
if
you
look
in
the
deck
there's
a
slide
that
talks
about
correct
me.
If
I'm
wrong,
is
she
sure?
Maybe
it
was
in
an
issue,
but
it
talks
about
the
comparison
page
and
what
that
mock-ups,
looking
like,
maybe
everybody's
slide,
11.
F
So
there's
comparison
pages,
we
have
a
whole
initiative,
that's
outlined
there
and
11
I
mean
we
could
link
to
two
that
issues
that
you
could
see
the
designs
that
are
being
and
you
can
see
actually
a
mock-up
of
the
design
there
that
will
be
applied
to
all
the
comparison
pages
as
we
get
it
done.
So
that's
happening
as
you
speak
as
we
speak,
and
there's
actually
I've
seen
it
a
that.
This
is
not
a
working
design
comp.
F
That's
taking
that
idea
of
comparison
with
those
graphs
to
the
next
level,
so
I
think
there's
a
there's,
a
general
agreement
with
you
and
probably
we're
not
moving
fast
enough,
but
I.
Don't
think,
there's
a
difference
in
opinion
about
what
needs
to
happen
and
there's
actions
happen
towards
that.
That.
D
Makes
it
on
a
sense
thanks
for
that
Todd
you're
right?
It
has
been
updated
more
recently
than
five
months
ago,
looking
at
the
framework
and
apparently
there's
somewhere
else,
you
need
to
actually
update
the
information.
I
didn't
see
like
recent
github
developments
like
code
spaces,
and
things
like
that.
That
I
think
are
great
github
features
that
I
think
we
should
highlight
on
our
competitive
phase.
I
know
we
talked
about
them
internally,
so
I
think
we
can
talk
about
them
externally.
D
The
design
is
like
11,
looks
super
cool
and
then
maybe,
instead
of
combining
the
two
pages,
which
seems
to
be
an
idea
that
only
only
I
am
for,
and
only
for
reasons
of
updating
which
we
can
also
achieve
through
other
means,
maybe
cross
link.
Maybe
that
would
be
a
great
next
step
where
we
make
sure
that
on
our
DevOps
tool,
page,
we
say
hey
if
you
were
to
get
live.
We
also
have
this
page
with
a
bunch
of
presentations
and
on
our
compete
page.
D
We
also
say
hey
if
you're
interested
here's
our
comp
black
comparison,
page.
F
You
know
the
other
point
I
make
is
the
reason
we
have.
That
is
when
you
talk
about
when
you're
talking
to
sales
about
how
we
achieve
success
over
our
competitors.
It's
a
different
conversation.
Even
if
some
of
this
information
is
the
same,
so
I
agree.
We
should
have
a
single
source
of
truth
and
linked
to
that
Canon
of
information,
but
how
you
train
sales
and
what
to
focus
on
is
a
different
topic
in
a
different
audience,
and
so
that's
what
we're
trying
to
achieve
on
that
page.
So,
just
to
back
up
with
Hayden
Sun.
D
C
C
G
Know
thanks
perhaps
I'll
jump
on
that?
Yes,
so
we
have
two
sets
of
personas
a
set
of
user
personas,
which
we
are
used
in
both
in
product
marketing
and
marketing
at
large.
As
far
as
and
I,
don't
really
know,
if
top
my
head,
I,
think,
there's
probably
10
or
12
of
them
that
we
use
to
define
require
that
the
product
team
uses
defined
requirements.
We
use
it
when
we
think
about
messaging
and
campaigns
and
and
building
outbound
content.
G
So
they're
they're
actively
part
of
what
we
do
and
it's
one
that
we're
continuing
to
iterate
and
invest
on,
as
we
think
about
building
messaging
around
specific
solutions
and
go
to
mark
emotions
that
people
are
why
they're
choosing
to
adopt
gitlab.
It's
a
great
question:
I
think
when
we
say
prospects
and
customers
I
think
we're
really
generalizing
to
the
larger
audience.
But
when
we
try
to
build
a
messaging,
we're
thinking
much
more
specific.
H
B
That
is
the
way
that
we're
working
it
is.
We've
been
working
with
cross-organizational
team,
a
lot
of
folks
on
this
call
we're
with
the
docs
folks,
the
customer
service,
folks
marketing,
of
course,
they're
our
marketing
folks
in
looking
at
how
we
present
that
in
a
single
way,
so
there's
a
single
source
of
truth
for
technical
content.
That's
we're
still
figuring
out
the
best
way
to
do
that.
This
is
that
effort
as
well.
So
so
please
check
out
the
epic
and
add
yourself
on
to
it.
E
B
Epileptic
couple
issues
and
we're
moving
forward
with
that
and
everybody
who's
involved
in
creating
content,
that's
technical
content
or
consuming
it
could
advantage
from
this.
So
we
want
to
get
understand
the
the
necessary
inputs
and
and
information
metadata,
that's
necessary.
So
all
the
different
teams
can
take
advantage
of.
I
Yeah
so
context
is
I'm
in
the
channel
on
this
channel
solution
architect
and
we
have
as
we're
bringing
on
a
lot
of
partners
who
are
super
enthusiastic
about
gitlab
and
really
want
to
build
a
DevOps
practice
with
Gil
lab
as
a
foundation.
They
want
to
learn
about
get
lab
in
an
actionable
way.
How
do
I
get
my
developers
to
know
best
practices,
or
how
do
we
solve
this
situation?
I
That's
common
in
our
customer
base,
and
so
the
challenge
has
been
really
trying
to
find
consistent
material
to
enable
them
and
empower
them
to
get
started
with
gitlab.
So
there's
been
a
few
instances
where
we've
sent
them
technical
marketing,
videos
or
they've
come
across
a
technical
marketing
page
and
they
understand
the
concept
that
technical
marketing
is
expressing,
but
it's
not
actionable
for
them.
They're
still,
you
know
they
get
an
overview
of
what
the
feature
does,
but
then
they
still
have
to
go.
Read
the
documentation
to
implement
it
and
sometimes
that's
challenging.
I
I
Our
challenge
is
getting
you
know,
trying
to
put
out,
or
at
least
provide
partners
with
self-service
material
where
they
can
feel
informed
and
being
placed
on
a
road
to
become
service
providers
and
thought
leaders
and
solution
providers
to
their
customers
around
Gila
and
that's
kind
of
dovetails
in
with
the
learning
collab
initiative,
which
were
just
became
aware
of
yesterday
and
we're
super
enthusiastic
about
and
we're
happy
to
support.
But
that's
something
that's
really
pulling
on
our
needs
that
we're
seeing
from
the
broader
community
of
organizations
that
want
to
support,
get
lab.
Officially.
C
B
However,
I
think
when
it
comes
to
learn
an
important
value
here
is
that
there
are
other
organizations
like
the
tam
organization,
has
an
effort
that
is
identified,
top
questions
that
they
were
are
going
to
do
tutorial
or
more
deeper
information.
Videos
for-
and
that
was
a
separate
effort
that
we're
trying
to
coordinate
with
so
so
that
everyone
who's
creating
that
type
of
information.
B
Valued
information
can
can
put
it
in
a
single
place,
so
we
can
all
find
it
and
take
advantage
of
it
hook
it
onto
the
docs
page,
acceptor,
etcetera,
so
so
yeah,
that's
that's
love
to
have.
You
join
us.
Give
us
your
input
on
making
sure
that
we
do
that.
The
way
that
the
benefits
number
one
most
thanks.
C
J
So
I've
really
enjoyed
the
technical
marketing
content
that
has
been
put
out
of
late
and
just
curious.
How
do
you
I
guess,
retire
or
diminish?
How
that
shows
up
as
the
product
evolves
to
highlight
the
latest
iteration
of
technical
marketing
content
that
would
follow
up
say
on
the
security
dashboard
as
it
might
look
drastically
different
from
13.0
to
13.5?
Are
those
videos
retired
or
they
you
stored
somewhere
else,
I've
seen
quite
a
few
pieces
that
are
maybe
three
years
old
are
still
getting
lots
and
lots
of
views.
So
it
curious
how
you
handle
that.
B
Yeah
so
yeah,
that's
a
challenge.
I'll
admit
that
we
do
have.
We
do
replace
older
videos
with
newer
ones
when
we
can
I
think
there
it
would
be
nice
if
there
was
a
way
in
YouTube
to
link
forward.
You
know
to
newer
versions
of
videos
or
to
have
versioning
of
videos,
but
but
we
expect
to
learn
to
help
with
this
too,
because
we'll
be
able
to
meta
tag.
The
information
about
dates
and
versions
which
we
are
doing
would
also
help
the
process
of
going
through
the
content
and
pulling
out
all
their
stuff.
B
With
respect
to
updating
you
know,
as
you
guys
all
know,
we
move
very
fast,
that
UI
does
the
product
does
and
I
think
I
think
one
of
the
pieces.
You
might
be
talking
about
that
when
we
do
a
video
that
shows
an
overall
value
that
the
product
provides,
sometimes
that
that
doesn't
get
updated
as
fast
as
because
we
have
you
know
the
bandwidth
to
do,
but
if
it
still
shows
the
value
but
to
you
eyes
a
little
bit
out
of
date,
they're
still
showing
the
value.
B
B
But
we
do
pull
older
videos
down,
there's
if
you'll
notice
and
learn
there's
an
archive
area
where
there's
some
water
content
and
and
so
we'll
continue
to
do
that
and
please,
if
you
identify
things
that
that
you
think
that
you
say
hey
this
is
this
is
looking
pretty
out
of
date
and
this
is
a
concern
and
that
we've
missed
it
and
please,
let
me
know,
send
mil
or
hit
our
channel
so
that
we
can
get
on
and
take
a
look
at.
It.
C
K
C
C
B
B
So,
for
example,
I
know
working
with
Tina
that
some
of
the
partner
marketing
foot
items
needs
to
be
presented
in
a
different
way
or
with
extra
information,
but
the
core
content
that
you
might
be
pointing
to
the
video
showing
how
to
do
something,
for
example,
is
usually
the
same
so
so
learn
will
help
with
that
having
a
centralized
set
of
assets
and
then
working
with
the
partner
team
could
actually
absolutely
be
looking
at
this
and
saying.
Okay,
what
do
we
share
out
to
partners
from
this?
B
B
What's
the
content
that
that
we're
going
to
have
available
in
the
inventory
as
we
build
that
now's
the
time
to
join
in
and
tell
us
okay,
this
is
the
kind
of
tag
or
metadata
information
that
would
be
helpful
for
you
to
pull
out
the
information
you
need
and
present
it
in
the
right
way,
things
like
version,
information
or
stage
and
category
and
all
that
type
of
thing.
Thank
you.