►
From YouTube: 2023-02-21 Product Analytics Group Sync
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
Hello,
everyone
and
welcome
to
the
product
analytics
weekly
for
February.
The
21st
I
forgot
how
numbers
work
there
for
a
while
I'll
start
us
off
by
walking
through
the
bull
board
if
you're
open
issues
the
first
one
deploy
product
Analytics
to
GitHub
lab
Dennis.
Anything
you'd
like
to
note
about
this.
B
Yeah,
we
still
need
to
promote
this,
but
I
think
what
we're
going
to
end
up
doing
is
just
pivoting
this
over
to
the
public
handbook.
I
think
that's
just
going
to
be
a
lot
more
value
in
terms
of
what
we're
looking
for
for
additional
data,
so
we'll
be
updating
this
issue
likely
Tomorrow,
Sam
and
I
have
a
session
to
kind
of
organize
and
and
fill
in
gaps
for
issues
and
epics
for
the
rest
of
the
customer.
A
We
can
skip
over
the
15
chain
one.
Then
we
have
ADD
product
analyst
application
setting
for
collector
hosts
in
solution,
validation
for
backend
I
see
this
is
an
assigned
I,
don't
know.
If
anyone
has
any
comments,
also
move
on,
then
we
have
put
a
add
dashboard
button
on
product
analytics
page
and
this
one
is
a
friendly
issue
in
problem.
Validation.
I
just
wanted
to
ask
a
question
whether
or
not
the
expectation
is
for
this
to
be
delivered
in
this
Milestone
or
only
be
planned
out.
A
So
we
have
this
issue,
put
an
add
dashboard
button
on
the
analytics
listing
page.
This
is
presumably
for
the
new
shared
listing
page.
The
current
status
of
this
or
the
workflow
is
problem
validation,
so
it
still
needs
to
I
think,
go
through
potentially
ux
and
then
also
implementation
planning.
So
I
just
wanted
to
check
if
the
expectation
is
to
have
this
delivered
this
Milestone
or
only
planned
out.
B
B
B
C
Into
planning
great,
but
this
one
for.
C
D
Saving
the
custom
dashboard
Spike
already
has
this
implemented,
so
this
basically
creates
like
an
empty
dashboard
object
and
basically
the
first
time
it's
saved.
It's
then
redirected
to
exactly
viewing
the
dashboard,
so
the
save
dashboards
to
the
custom
Ripple
will
include
this,
because
otherwise
you
will
be
as
a
step.
Wife
I
believe
I
can
link
you
to
the
list
of
the
spikes,
so
this
is
already
implemented.
It
just
needs
to
be
cut
in
with
the
saving,
because,
of
course,
for
adding
a
new
dashboard.
We
first
need
the
savings.
A
A
B
D
Shouldn't
have
any
sort
of
specifics
on
that
level.
Only
later,
when
you
are
adding
panels,
then
you
can
add
whatever
you
want,
because
optimize
will
definitely
have
some
things,
but
we
are
already
looking
into
plan
because
we
have
a
couple
of
burn
down,
charts
that
we
could
add,
but
they
are
not
coming
from
optimized.
So
there
shouldn't
be
any
sort
of
you
create
a
dashboard,
and
then
you
can
only
add
that
type
of
stuff.
We
should
be
able
to
filter
down
what
you
are
adding
to
the
editor.
That's
what
I
believe
is
currently
the
time.
A
Before
so,
I
can
actually
move
this,
then
into
review
yeah
all
right.
Let
me
quickly
do
that.
B
Case
yeah,
this
one
needs
to
be
closed
just
to
capture
it's
the
same
as
last
week.
Just
need
to
capture
the
decision
that
we
will
introduce
the
slash
visualization
designer
endpoint
and
then
should
we
need
to
change
it.
For
you
know,
subsequent
variations
of
that
Designer
then
we'll
we'll
route
it
from
there.
So
there's
a
draft
sitting
in
my
this
covers
the
naming
so
far,
but
there's
the
whole
overall
strategy
for
it,
which
I'll
publish
the
draft,
and
then
we
can
close
that
issue
out.
A
Cool
then
there
is
a
an
assigned
backing
issue
that
I'm
very
excited
for
is
to
add
the
first
State
Management
to
the
back
end
for
product
Analytics
then
make
sure
you
have
document
existing,
which
is
your
integration
points.
E
Yeah,
so
this
was
just
writing
down
some
information
about
how
gitlab
currently
interacts
with
Jitsu
and
where,
in
the
code
base
that
happened,
so
I
posted
some
documentation
and
a
diagram
explaining
how
that
actually
works.
E
A
A
Yeah
I'll
fix
that
quickly.
After
the
call,
then
we
have
percent
of
culture
actions
configuration
dashboards
in
shared
dashboards,
listing
Well.
These
titles
will
be
coming
along
I
yeah.
This
is
saying:
planning
breakdown,
I,
don't
know
if
we
have
anything
else
to
say
about
this
Rob
I,
don't
know.
If
you
have
any
comments
for
this
one.
F
Not
right
now
I
need
to
get
back
to
it,
it's
sort
of
tied
into
what
I'm
doing,
with
the
shared
listing
moving
that
all
over.
So
it's!
This
is
next
on
the
pipeline.
After
that,
I
need
to
get
back
to
see
if
I
can
move
this
into
ready
for
development
or
blocked
or
whatever
whether
I
can
move
on
I'll.
Do
that
shout
after
this
call.
A
B
B
A
Will
rather
just
edit
the
flag
there?
Also,
then
we
have
a
blocked
issue:
remove
product
analytics,
specific
dashboard
listing
I
think
this
is
just
pending
the
work
to
move
the
dashboard
listing
over
to
the
generic
shared
listing
page
right.
A
Well
before
we
discussed
that
one
and
then
Sam,
you
have
created
a
blog
post
about
product
analytics
the
internal
preview.
Anything
to
comment.
C
Yeah
so
I
wrote
a
draft
of
a
blog
post.
It's
in
the
issue,
if
you'd
like
to
take
a
look
and
I'm
working
with
tech
right
or
product
marketing
to
get
that
finalized
and
we'll
get
that
posted,
so
comments,
feedback
questions
welcome
on
it.
As
always,
if
you
have
any.
A
Cool
and
then
we
have
the
next
to
our
mind
for
a
Handler
dashboard,
if
not
available
with
a
404
404
page,
it
was
again
just
a
nice
like
quality
of
life
Improvement
for
users
in
case
the
dashboards
that
they're
linking
to
select
the
URL
exchange
or
something,
and
there
should
be
a
small
change
and
yeah
which
I
haven't
started
with
and
then
I
also
have
attic,
add
Cube
cube.js
to
the
renovate
bot,
and
this
is
to
automate
the
updated
process
of
it
that
it
creates
a
Mr
and
then
like
assigns
it
to
one
of
the
frontal
engineers
in
this
group
for
review,
I'll,
probably
ping
AP
for
some
advice
on
like
how
to
actually
implement
this.
A
Then
we
have
another
issue
here
that
I
think
Rob
is
actually
pretty
much
working
on,
because
this
is
to
use
the
analytics
namespace
for
all
of
our
translation,
strings,
I.
Think
Rob.
The
work
that
you're
currently
doing
in
the
front
ends
should
actually
solve
this.
A
Oh
and
then
Alvin
has
also
this
one
to
add
a
feature
spec
for
the
dashboard
visualization
designer
So.
Currently
we
have
a
feature
spec
for
the
dashboards
listing
page,
but
we
do
not
have
one
for
the
visualization
designer,
so
I've
wrote
an
implementation
plan
here
and
assign
itself,
and
that
basically,
just
does
goes
through,
like
the
basic
steps
of
clicking
on
a
measurement
clicking
on
a
dimension
and
then
just
checking
that
the
expected,
like
that
the
data
table
contains
like
the
expected
data
that
we're
returning
from
a
mock,
Black,
Cube
response.
A
B
Yeah
we've
also
been
filing
and
making
improvements
to
it
already
and
there's
no
open
issues
linked
to
them
anymore.
So.
A
They
just
disappeared,
then
we
have
connected
Devin
staging
gitlab
environments
to
respective
clusters,
Dennis
yeah.
B
So
this
was
previously
kind
of
a
test
git
lab
instance
for
us
to
connect
to
isolated
cluster
environment,
but
I've
changed
this
just
to
basically
be
because
I
have
the
dev
cluster
up
now
and
I'm
going
to
verify
the
changes
one
more
time
for
the
instrument.
Excuse
me
infrastructure
documentation
for
staging
one
more
time
and
then
I
think
it
just
makes
sense
for
us
to
connect
dev.getlab
and
Stage
lab
to
those
environments,
and
then
we
can
do
our
testing
there.
B
Should
we
need
more
environments
from
that
point,
you
can
just
follow
the
instructions
and
set
up
your
own
cluster
on
gcp.
If
you
need
that,
but
dev
kit
should
be
more
than
sufficient,
so
this
issue
will
just
basically
give
us
one-to-one
parody
with
all
of
our
different
environments.
B
So
kind
of,
depending
on
the
the
above
issue,
I
want
to
kind
of
verify
all
the
baddest
changes
on
dev
promote
it
through
the
normal
ways
before
putting
it
into
production.
Since
that's
where
most
of
our
sensitive
or
important
redis
data
is
so
I
just
wanted
to
make
sure
everything's
good
there
before
you
know,
we
don't
have
less
worry
of
red,
is
failing
over
in
production,
so
yeah.
A
Well,
the
next
one
is
to
improve
the
panel,
rendering
responsiveness
and
consistency
specifically
how
visualizations
like
fit
in
them.
I'll,
probably
end
up
picking
this
up.
It's
currently
unassigned
then
rob
you
have
the
next
one
to
replace
product
analytics
dashboard
lists
with
the
new
shared
listing.
F
Yeah
chunky
boy-
this
is
over
4000
lines
being
broken
down
into
five
separate
MLS
back
end
is
waiting
for
the
pipelines
to
succeed.
Thank
you
very
much
Max
for
reviewing
that.
This
morning,
the
first
front-end
demos
with
you
young
and
substitute
the
subsequent
Mrs
I,
am
currently
working
on
and
juggling
all
the
rebasing
ETC.
That
needs
to
happen
to
get
this
all
through,
but
it's
going
it's
making
progress,
It's
happening.
Finally,.
E
In
fact,
documenting
the
ability
to
explore
raw
click
out
data
by
the
key
proxy,
and
so
that's
in
review.
Lorena
has
made.
B
E
Very
useful
comments
on
that
and
I
think
Rob
has
also
raised
some
questions
which
I
haven't
responded
to
yet
so
we
should
get
that
merge
during
this
recovered
thing.
A
Also
just
moved
it
into
review.
The
first
item
here
is
mine
to
update
the
learner
setup
that
I
took
over
from
Axel
I
think
this
is
just
pinning
a
review
from
Rob
but
I'm,
assuming
that
it's
pretty
low
priority
against
all
the
other
works
that
you're
doing
so.
No
rush.
A
And
then
we
already
discussed
the
dashboard
button
to
the
analytics
listing
page
and
then
verification
yeah
with
this
Spike
to
investigate
final
analysis
needs
I,
don't
know
if
you've
anything.
If
you
would
like
to
add
there
packs.
B
Well,
I'm
same
thing
with
the
different
clusters
we'll
promote
them
that
way,
because
oh
I
keep
breaking
Productions,
sometimes
with
these
these
promotions
so
verify
it
properly.
A
And
then
some
of
you
were
doing
some
great
work
to
improve,
like
the
dashboards
that
here,
like
the
list
three
chains
fluid
container
after
visiting
a
dashboard
of
the
panel
designer.
D
B
B
F
Feel
like
we
have
to
mark
the
issues
completed,
issues
of
workflow,
complete
like
when
they
put
production
I
feel
like
that's
a
thing.
Sam
might
tell
me
otherwise.
B
D
C
Yeah,
thank
you
James,
so
that
is
applied
after
features
avoided
production
verification
is
needed,
and
the
issue
has
been
closed.
So
we
might
need
to
update
this
board
to
have
that
column
since
that
change
has
been
merged.
A
All
right,
then,
that's
good
to
know.
I
agree
with
some
of
that
would
be
nice
if
we
could
just
automate
that.
C
Expanded,
but
how
about
we
dig
into
this
top
async
topic
asynchronously,
because
I
think
there's
probably
going
to
be
some
discussion,
we'll
need
to
tab
here
and
we'll
probably
run
out
of
time
during
this
call.
A
A
Also
thanks.
Tim
for
raising
the
question.
Slash
bug
about
the
unintended
or
erroneous
date
range
limit
that
was
added.
I
created
the
issue.
To
remove
that,
then
we
have
onboarding
API.
Oh,
this
was
just
the
issue
that
was
close
to
that
are
promoted
to
an
epic
and
the
Milestone
planning.
We
don't
need
to
discuss
and
the
internal
preview
dashboards
issues
I
also
don't
think
we
need
to
discuss
both
in
that
case,
I'll
stop
sharing.
B
Cool,
so
we
did
some
introductions
yesterday
at
the
session
announcement.
But
of
course
some
some
of
us
could
make
it
as
a
holiday
or
other
reasons,
but
we
have
a
couple
new
faces
since
yesterday:
James
and
Kevin,
starting
with
James,
if
you
wanted
to,
if
you
don't
have
to.
But
if
you'd
like
to
we'd
love
to
hear
a
little
bit
about
you
if
you'd
like
to
introduce
yourself
but
no
pressure.
G
Yeah
sure,
hey
folks,
I'm
James,
heimbach
I'm,
coming
to
you
from
pipeline
execution.
Most
recently
I've
been
at
gitlab
about
three
and
a
half
years
spent
the
whole
time
in
verify
started
with
the
testing
team,
which
has
turned
into
the
pipeline
and
States
team,
and
about
a
year
and
a
half
ago,
moved
over
to
pipeline
execution
based
near
Denver
Colorado.
So
Mountain
Time,
Zone,
The,
Forgotten
time
zone,
I,
joke
I'm,
usually
up
pretty
early.
G
We
have
a
nine-year-old
who
we
I
have
already
dropped
off
at
school
this
morning,
so
that
I
can
make
this
meeting.
But
that's
about
normal
time
for
us
so
working
hours
and
all
that
other.
What
not
are
in
my
readme
and
I'll
be
getting
copy
chat
booked
with
everybody
over
the
next
couple
of
weeks
as
time
zone
and
schedules
to
allow.
B
H
Sure
hi
everyone
I'm
Kevin
I'm
a
product
designer
here
at
gitlab
for
about
three
years
ish.
Almost
four
years,
it's
crazy
I
spend
most
of
my
time
in
growth
and
yeah
now
I'm
moving
here,
I
live
in
Amsterdam,
but
I'm
a
Dutch
I'm
French
I'm
here
about
five
years
ago,
something
like
that
but
yeah
working
hours.
Obviously
it
depends,
but
the
only
thing
that
is
constant
is
that
I'm
much
more
proactive
in
the
morning
and
fresh
so
I,
usually
do.
H
The
bulk
of
my
work
in
the
morning
and
afternoon
is
essentially
meetings
as
much
as
possible,
so
yeah
I
also
try
to
book
coffee
chat.
With
most
of
you.
B
Thanks
Kevin
I
also
realize
we're
asking
you
for
an
intro,
but
we're
not
introducing
ourselves,
but
in
the
interest
of
time
I
guess
we'll
have
to
do
that
in
another
meeting
or
a
in
coffee
chat.
So
thanks
thanks,
James
and
Kevin
for
your
introductions,
yeah.
The
next
point.
A
Yeah
on
that
topic,
maybe
it's
time
for
another
social
call,
since
the
team.
B
A
Going
so
rapidly,
we
can
have
like
another
round
of
social
calls
or
maybe
APAC
friendly
one
Speaking
of
APAC
friendly.
Since
we
have
a
Apec
team
member,
the
topic
again
comes
up
about.
Should
we
consider
having
an
APAC
friendly
time
slot
or
going
fully
asynchronous?
Then
if
you
have
a
response.
B
Yeah
we've
done
previous
iterations
of
this
in
the
past.
We
could
definitely
alternate
time
zones,
I.
Think,
there's
value
in
having
synchronous
discussions
just
looking
back
at
our
recent
agendas,
so
I
would
say
something
doing
something
like
emea
Americas
for
one
session
and
then
the
other
week.
Perhaps
like
I.
Don't
know
if
this
is
the
question.
I
have
is
Apac
Americas
or
APAC
emea,
previous
iterations
of
this,
on
different
teams,
and
so
I.
B
Don't
want
to
bring
that
over
here,
but
just
some
valuable
feedback
is
that
sometimes
people
don't
find
it
as
valuable
when
the
engineering
and
product
managers
aren't
present,
and
it
just
feels
more
of
a
stand-up
which
we
already
do
asynchronously.
B
So
if
that's
the
case,
then
you
know
that
that's
not
valuable,
so
Curious
to
hear
what
other
people's
thoughts
are
or
we
can
open
an
initiative
discussed
and
figure
out.
What's
the
right
balance
for
that.
C
I
think
it's
a
good
idea
in
general.
I
will
point
out
that
the
product
intelligence
group
also
has
alternating
times
for
time
zones.
So
when
we're
scheduling
this
I
just
ask
that
we
be
mindful
of
when
their
call
is
and
not
double
book
it
on
the
same
time,
in
case
folks,
want
to
attend
both
attend
both
calls.
H
B
As
far
as
action
items,
I'll
open,
initially
just
to
figure
out
who
who
would
find
it
would
be
useful.
We
obviously
have
a
lot
of
people
in
all
regions
now,
so
not
everyone's
going
to
be
attend
attending
that,
then
that's
fine,
but
I'll
start
an
issue
for
that.
B
I
also
have
the
next
Point
the
infrastructure
onboarding
instructions.
This
is
primarily
for
Max
and
Rob,
but
for
anyone
else
interested
in
how
we
can
deploy
the
an
analytics
stack
into
a
cluster
environment,
those
instructions
will
be
going
out
later
today,
I'm
just
verifying
it
one
last
time,
just
to
make
sure
I
covered
at
least
most
of
the
bases,
so
yeah
that
should
be
I'll,
send
that
out
to
the
channel,
but
just
a
heads
up.
D
Yeah,
just
a
quick
update
from
your
silent
contributor
design
updates,
have
been
merged
and
are
in
production.
By
now
so,
and
CSS
now
doesn't
is
now
filling
the
whole
screen.
It
looks
much
nicer,
I,
even
posted
a
screenshot
already
with
the
new
navigation
even
better,
and
the
visualization
designer
match
request
was
merged
today
in
the
morning
this
will
add
basically
the
capability
to
filter
by
sessions
to
measure
sessions
and
all
the
session
parameters,
like
average
duration
of
sessions
and
so
on,
and
also
all
the
unique
users
stuff.
D
So
we
can
definitely
now
Measure
A,
Thousand,
Miles
and
vowels,
and
all
that
other
stuff
through
the
visualization
designer
I,
cut
it
out
yesterday
the
loading
dashboard
Mr,
which
is
basically
now
loading
from
the
other
pointer
repo.
So
what
optimizes
implemented
so
that
you
can
set
basically
another
repo
where
all
the
dashboards
are
going
to
be
stored.
You
can
also
use
the
same
if
you,
if
you're
really
adventurous.
D
This
is
basically
showing.
If
you
don't
have
anything,
set
up
an
info
message,
then
it
guides
you
to
the
settings.
You
can
set
it
up
and
then
it
basically
goes
ahead
and
loads
from
our
predefined
directories
under
dot,
gitlab
dashboards
and
the
same
goes
for
the
visualization.
D
A
Very
exciting
anything
else,
anyone
would
like
to
share
or
any
final
topics,
questions
concerns.