►
From YouTube: Product 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).
C
Over
for
sure
Thanks,
so
we
had
an
OPR
add
another
type
of
Linux
consumption
pricing
so
like
have
different
Linux
runners,
but
the
only
reason
we
have
that
because
it
was
an
MVC
of
where
we
want
to
get
to
OS,
X
and
Windows
runners,
now
there's
kind
of
confusion
like
oh
no
one's
asking
for
this.
No
that's
right.
We
just
want
to
do
a
minimal
step,
but
it
seemed
that
kind
of
we
lost
track
of
what
we
originally
wanted.
Should
we
change
this
to
like?
C
Let's
do
OS,
X
and
Windows
runners
and
maybe
move
it
from
the
fulfillment
team,
which
has
a
lot
of
different
priorities
to
a
CI
team
for
which,
like
this
is
the
reason
we're
losing
a
lot
of
people
to
circle
CI
today,
because
they
offer
this
and
we
don't
like
we're,
not
a
complete
CI
solution
today.
Because
of
this,
what
do
you
have
and
and
like?
Okay,
ours
are
not
set
in
stone.
There's
stuff,
we
change
during
the
quarter.
If
we
we
set
a
wrong
goal.
What
do
you
think
it.
A
Makes
sense
to
me
I,
you
know
you
Anna
puts
a
couple
of
times
and
so
I
I
think
it
makes
sense.
I
jason
is
Jason
lending
out
there.
I
was
planning
to
he.
Just
got
back
from
paternity
leave.
I
was
gonna,
bring
it
up
this
week
and
see
how
he
views
this
relative
to
other
CI
priorities,
but
it
seems
like
making
the
shift
to
OS.
X
and
Windows
makes
sense
to
me.
Okay,
are
there
any
other
comments
or
input
from
folks
that
are
closer
to
the
CI
priority
list?.
D
Hey
I'm
here
Scott.
Can
you
hear
me?
Oh
hey,
Jason
good
morning.
I
am
this
is
something
that
we
consider
doing
for
sure.
We
have
other
priorities,
of
course,
as
well.
We
just
went
through
a
list
of
other
things.
Competitors
were
doing
that
were
important,
that
we
wanted
to
have
parody
yarn
and
those
kind
of
filled
up
the
schedule
as
well.
D
But
but
this
is
pretty
important,
there
was
a
really
interesting
thing
that
can
be
found,
potentially
a
partnership,
or
at
least
some
kind
of
technology
collaboration
with
Mac
stadion
to
see
if
we
could
do
something
in
collaboration.
Therefore,
OSX
partners,
at
least
we've
done
a
ton
of
investment
in
making
the
Windows
runner
actually
capable.
So
that's
actually
a
little
further
along
in
terms
of
technology
side.
So.
D
A
F
A
C
C
We
don't
have
any
of
our
defense
stages
in
the
product
today
and
it's
kind
of
that's
okay
for
a
couple
of
months,
but
I
think
it's
time
for
first
iteration.
Is
there
anything
coming
down
the
down
the
pipe
and
I'm
I'm
thinking
specifically
of
implementing
modsecurity
as
a
web
application
firewall
that
works
with
other
DevOps.
F
B
So
maybe
three
months
ago
we
had
had
the
graph
MVC
scheduled,
but
as
a
result
of
some
increased
customer
pain
in
the
secure
stage
categories,
we
pushed
it
out
to
focus
on
improving
the
maturity
in
the
secure
stage
categories.
But
it
is
on
schedule
like
in
on
my
side
Nicole
in
the
next
three
to
four
releases,
so
we're
starting
to
do
investigation.
But
our
current
category
maturity
target
has
that
MVC
in
in
q3
yeah.
C
So
maybe
this
more
engineering
question
I
can
ask
you
there
do
we
have?
Is
it
only
our
secure
team?
That's
working
on
this?
Don't
we
have
that?
Are
we
gonna
grow
with
the
phen
team,
we're
supposed
to
have
three
different
teams
by
the
end
of
the
year?
I
think
we
reduce
that
a
bit,
but
we're
gonna
have
two
teams
and
we
don't.
We
already
have
at
least
one
person
yeah,
we've.
B
Been
so
I
can
speak
and
I
don't
have
Todd's
on.
He
can
also
a
comment
rate,
but
we
made
the
decision
to
incubate
defend
in
the
growing
number
of
secure
teams
and
we
actually
had
our
third
secured
yam
join
today
or
this
at
least
last
week.
So
we've
been
growing
out
secure
team
and
saying
it
to
the
extent
that
we
are
going
to
be
adding
defend
function.
I
will
have
it
from
within
those
teams,
so
their
coverage
includes
defend
and
then
we
will
split
out
a
defense
team
as
the
team
grows.
It.
C
C
B
So
in
the
current
state,
this
p.m.
is
me,
but
in
the
future
I
do
think
you
know
we
expect
PMS
to
both
expand,
breath
and
focus
on
depth.
At
the
same
time,
I
think
we
can
juggle
the
two
we've
been
juggling
the
two
to
get
us
to
the
point
where
we
are
today
where
we
have
a
number
of
new
categories,
despite
those
having
been
incubated
within
Cir
ops,
so
I
don't
think
that's
a
I'm
not
concerned
about
the
PM
not
being
capable
of
juggling
between
us.
You
know
I.
C
B
B
A
G
Scott,
how
are
you
doing
welcome
from
Boulder?
That's
awesome.
You
see
I'm
currently
dealing
with
a
few
customers
that
have
added
numbers
of
licenses
as
part
of
the
migration
from
other
people,
and
so
their
actual
usage
count.
You
know
goes
up
tremendously
based
on
the
number
of
people
that
they
moved
over.
However,
those
people
are
natural
users,
so
they,
you
know,
there's
a
hesitancy
for
them
to
pay
for
people
that
aren't
actually
using
gitlab
but
they're
there,
because
we
migrated
them
right
as
part
of
that.
G
Our
usage
count
in
our
in
our
system
when
they
go
on
our
UI
shows
that
they
have
like
20,000
people,
but
in
all
reality
they
may
have
5,000
people.
So
you
know
they're
they're
asking
us:
when
will
that
process
be
more
accurate
and
could
we
make
it
more
efficient,
as
you
know
that
one
of
the
things
they
were
a
thing
speaking
to
a
little
bit,
what
it
always
says
which,
if
we
can
automate
it?
Let's
do
that
right.
If
we
can
do
that,
so
they
would
love
to
be
able
to
have
it
model.
G
The
AWS
system,
where
you
add
something
you
get
billed
for
it
so
I
know
every
contract
can't
be
done
that
way,
but
is
there
a
way
that
we
can
make
that
more
efficient
I,
know
everything
and
put
something
there,
and
there
is
an
an
issue.
Further
down
it
sits
around
maximum
users
should
always
reflect
current
counts,
but
oftentimes.
We
have
customers
where
it
doesn't
reflect
that
and
I
have
to
issue
them
a
key
for
way
more
than
the
license.
G
H
I,
don't
Scott,
but
John
just
wanted
to
make
you
aware
of
the
things
that
the
fulfillment
team
are
working
on
and
just
to
call
that
work
out,
which
is
the
self
service
upgrades
forget
lab
comm.
Obviously,
that's
not
the
only
thing
that
the
team
is
working
on.
That's
the
number-one
priority
right
now
for
the
fulfillment
team
and
then
we'll
be
moving
on
to
some
of
the
licensing
stuff.
I'm.
H
Just
gonna
share
my
screen
very
quickly,
so
you
can
see
so
here's
the
priorities
from
the
transactions
perspective
on
fulfillment
stealth
service
upgrades,
forget,
lab
comm,
improving
the
trial,
experience,
improving
the
purchase
experience
and
then
automatically
billing
for
new
users
on
get
lab
comm,
but
you
were
asking
more
on
licenses
right.
So
here's
your
maximum
user
issue
that
you
that
you
referred
to
I
also
wanted
to
call
attention
to
the
fact
that
there's
a
whole
number
of
licensing
issues
currently
open.
H
G
I
Specifically,
the
request
was
around
getting
usage,
license
usage
down
for
companies
who
have
a
bunch
of
integrations
they're,
creating
specific
users
and
then
taking
those
users,
personal
access,
tokens
for
usage
with
integrations
and
which
is
kind
of
unfair,
because
it's
not
an
actual
seat,
that's
being
used,
so
we've
got
a
ticket
that
are
an
issue
that
I
mentioned
there.
What
we're
looking
at,
adding
those
service
users,
that's
currently
being
discussed.
J
A
You
know,
first
of
all,
there
was
an
okay
are
coming
into
the
quarter
that
even
preceded
me
that
require
requested
that
the
peach
p.m.
do
at
least
three
interviews.
So
it
was
a.
It
was
an
intentional
goal
coming
into
the
quarter.
First
of
all.
Secondly,
it's
been
a
point
of
emphasis
for
me
coming
into
the
role
to
push
push
the
team
to
do
more
qualitative
interviewing
in
general.
A
My
suggestion
is
to
frame
it
around
either
problem
interviews
where
you're
trying
to
understand
what
the
problem
is.
The
customer
needs
you
to
solve
and/or
a
solution
interview
where
you
think
you
have
a
solution
that
a
problem
you
want
to
go
out
and
test
it
qualitatively.
So
I
think
the
team
has
been
doing
both
of
those
types
of
interviews
here.
A
Anything
else
we
want
to
dive
into
on
that.
Oh
I
will
pay
off
I,
just
think.
When
PM's
and
designers
and
researchers
stack
up
a
bunch
of
interviews,
you
start
to
develop
much
better
intuition
about
who
the
target
user
is
what
they're
trying
to
do.
What
will
what
will
work
for
them?
That
might
not.
You
might
miss
some
things
if
you
operate
more
on
gut
instinct,
so
I'm
just
we're
trying
to
set
up
a
system
where
this
is
a
regular,
recurring
activity
and
the
quality
of
our
decisions
will
improve
over
time.
A
The
more
these
you
do
you
just
get
you
get
better,
you
can
try
and
get
you
can
see
patterns,
and
it
gets
a
lot
easier
to
sift
through
all
the
inputs
that
come
out
of
p.m.
when
they
have
this
filter
to
work
through.
So
it
takes
a
while,
and
it's
just
it's
about
coming
and
doing
it
every
day,
but
over
time
you
get
real
benefit.
They're.
A
E
Yeah,
so
I
was
just
curious
if
we
have
any
tooling
implemented
in
gillip
comm
to
monitor
how
or
what
features
customers
are
currently
using
in
the
product.
Is
that
snow
now,
I
kind
of
remember
that
being
part
of
the
discussion
at
one
point
is
that
is
that
implemented
there
is
there
a
place
that
we
can
see
some
stats
around
that
stuff
yeah.
A
I'll,
take
a
shot
at
this.
Eric
can
fill
in
any
gaps.
Very
recently
we
implemented
snow
plow
on
Comm,
and
so
now
we
have
a
data
source
that
I
think
is,
is
rich
and
should
enabled
us
to
monitor
customer
usage.
So
that's
in
much
better
shape.
As
of
recently
on
the
on-premise
side.
Through
the
usage
ping,
we
are
working
on
a
improvements
to
the
ping
itself
and
across
both
were
also.
We
also
have
a
project
to
get
more
accurate
smell
that
staged
monthly,
active
user
data.
H
That
was
a
very
accurate
description.
Scott.
The
only
other
thing
I
would
say
is
that
up
until
recently,
we
were
not
tracking
all
clicks
from
snow
plow,
so
we
weren't
getting
kind
of
fullness
of
data
that
we
could
have
been,
but
we've
we've
recently
made
changes
to
to
basically
implement
all
all
click
tracking
with
snowplow.
H
So
the
short
answer
is
yes,
and
no
are
we
monitoring
product
feature?
Use
doesn't
get
overcome.
Answer
is
yes,
we
received
any
actual
insights
from
that
data,
yet
not
really
the
other
way
we
are
getting
some
product
feature
usage
from
get
live.com
is
querying
the
database
directly,
and
so,
if
you
look
at
some
of
the
product,
metrics
decks
around
get
Lancome.
We
do
have
some
feature
data
in
that
deck
as
well,
but
it's
primarily
around
querying
a
database
directly.
H
A
L
Thank
you,
yeah
I
just
wanted
to
ask
this
question.
You
know
similar
to
Brian's
question
earlier.
You
know
we
have
the
usage
ping
on
the
on-prem
versions
of
get
lab,
so
posted,
and
you
know
it's
broken
out
with
various
product
lines
of
what
they're
using
if
they
leave
it
on.
Is
there
a
move
to
put
feature
usage
in
there?
A
H
The
I
think
usage
ping
at
or
as
a
data
framework
is
definitely
being
expanded
for
self
managed
fill.
You
know
the
usage
ping
as
as
exists
as,
like
the
actual
thing,
might
be
replaced
by
a
new
tool
or
technology.
The
point
is,
we
want
a
bunch
more
data
from
self-managed
and
we're
making
a
lot
of
improvements
in
12-2,
making
even
more
improvements
in
12,
3
and
12
for
to
get
some
of
that
data
with
respect
to
scripting
around
valuable
features.
H
I
think
that's
something:
that's
we
probably
deeper
into
to
figure
out
how
we
could
get
that
information
programmatically,
and
so
yes,
the
answer
is
yes,
we
are
we're
doing
a
lot
there
with
respect
to
you
know
is
your
specific
example
on
scripting
I'm,
not
sure
if
we
have
that
written
out
as
as
an
issue,
but
we
should
we
should
take
it
off.
One
yeah.
L
The
reason
for
that
was
yeah
I've
got
a
couple
of
customers
that
you
know
have.
Hundreds
of
thousands
of
CI
builds
running
right
and
their
encore,
or
their
aunt
starter.
So
I'm
just
wondering
like
what
does
their
life
look
like
with
not
being
able
to
use
multi
project
pipeline
graphs
or
the
pipeline
dashboard
like?
How
are
they
getting
around
this
and
I'd
love
to
understand?
You
know
it's
a
real
problem
and
what
that
looks
like
on
their
end
and
how
how
you
can
justify
those
feature,
upgrades
I
think.
A
L
M
I
M
M
H
H
The
other
thing
to
note
as
well
just
just
so
everyone's
aware,
is
when
we
make
a
change
like
this,
especially
if
it's
going
to
be
targeted
at
improving
things
for
our
self-managed
customers.
Obviously,
there's
an
upgrade
cycle
that
happens
after
this,
and
so
the
you
know,
there's
going
to
be
a
period
of
time
where
we're
going
to
have
enhanced
usage
being
at
the
same
time.
As
you
know,
people
on
the
older
ping.