►
From YouTube: 2022-11-01 Product Analytics 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).
B
A
Product
analytics
group
sync
and
we'll
be
going
with
I'm
gonna
hold
on
get
my
tabs
kind
of
organized
here
and
then
share
the
board.
So
we
can
review
the
billboard.
A
That
is
the
intent,
because
I
don't
want
anyone
else
to
see
how
many
other
tabs
I
have
open
in
my
main
window.
So
the
contents.
Well,
you
know
how
I
am
with
sensitive
information.
So
yes
cool,
so
we've
got
two
open
issues
that
aren't
in
a
workflow,
State
I,
don't
know
if
we
want
to
cover
these
at
all,
but
we've
got
make
an
internal
announcement
about
dog
fooding
plan
Sam.
Is
there
anything
new
here
we
want
to
talk
about.
C
No
overallcock,
mostly
positive
reception
everything
I
got
from
it
was
in
the
public
thread,
so
no
like
special
DMS
from
anyone,
so
really
encouraging
some
good
questions
in
the
discussion
as
well.
So
we
can
take
those
and
put
those
into
an
FAQ
document
or
product
documentation
somewhere
for
the
most
part,
I
think
this
issue
I'll,
probably
leave
it
open
for
another
day
or
so
in
case
people
have
comments
on
the
feedback
issue.
Otherwise,
I'll
close
it
once
that's
done.
D
Awesome
and
like
from
me,
especially
that
went
so
well
so
congrats
Sam,
because
those
kind
of
announcements
company-wide
can
attract
some
like
negative
feedback.
Generally
speaking,
anything
privacy
related
and
as
far
as
I
could
tell
there
was
questions,
but
nobody
actively
saying
this:
isn't:
okay,
so
yeah
handled,
amazingly
well.
Thank
you.
We.
C
That
will
probably
be
the
more
controversial
version
of
the
announcement,
but
this
was
a
good
proxy,
for
hopefully
it
won't
be
too
bad.
A
I
guess
it'll
be
good
to
see
how
many
people
are
running
ad
blockers
or
just
running
the
DNT
or
gpc's.
The
the
Privacy
signals
to
see
if
they'll,
even
notice,
but.
A
A
Yeah
actually
I,
remember
I.
Think
I
had
to
figure
out
how
to
turn
off
GPC
on
on
Chrome
first,
for
whatever
reason,
since
we
had
added
that
but
anyways
cool,
so
yeah
I
think
that's
that's
good
progress,
obviously
there's
more
announcements
to
come.
It's
a
long
journey
in
terms
of
our
Communications
there
and
then
it'll
get
more
exciting,
especially
once
you
get
more
public
about
it
and
generates
an
excitement
externally.
But
you
know
it's
exciting,
nonetheless,
all
right
and
then
the
other
issue.
We
have
retrieve
product
dashboard
of
this
via
rest.
D
A
A
E
Yeah,
that's
me:
I
have
done
nearly
every
screen,
I'm
just
on
the
dashboards
listing
screen,
sort
of
view,
I've
done
the
empty
state
for
that
and
doing
the
other
state,
so
I'm,
hoping
I
should
have
that
out
to
yarn
and
Sam
to
get
some
initial
feedback
on
all
the
terrible,
terrible
things
I've
done
and
how
to
make
it
better
today,
hopefully,
and
if
anyone
has
any
ideas
on
alternative
ways
to
design
stuff,
please
tell
me
when
I
share
it
cool.
A
All
right
we
got
tracking
he's
such
as
the
new
tracker
internal
handbook,
this
one's
currently
blocked
pending
a
production,
Readiness
review,
yeah
I
think
this
is
more
blocked
by
me.
More
than
anything
so
I'll
just
speak
to
it.
So
I'm
going
to
be
working
on
that
today,
once
I
get
the
sandbox
Cloud
environment
provision
for
the
group,
which
I
have
a
later
point
to
talk
about,
but
yeah
I
think
that
covers
that
issue.
Axel
is
not
here,
so
we
can't
speak
to
the
Loading
state
for
customizable
dashboards.
A
So
we'll
continue
on
carrying
on
with
what
I
was
saying
before,
there's
some
conversations
that
need
to
happen
with
both
infrastructure
and
security,
just
to
make
sure
we're
good
to
go
with
the
change
to
basically
instrument.
The
internal
handbook.
A
I
was
hoping
to
do
that
earlier
this
week,
but
the
sandbox
cloud
and
our
domain
names
expiring,
are
going
away,
is
a
little
bit
more
important
to
be
able
to
collect
data
if
we
need
to
be
able
to
send
events
somewhere.
So
I've
been
working
on
that,
but
we'll
update
it
as
soon
as
we
can.
It
seems
like
so
far.
There's
no
major
concerns;
they
are
classifying
the
data
we
are
collecting,
even
with
IP
address
as
yellow
data.
A
So
that's
great
means
that
the
data
we're
collecting
doesn't
require
us
to
have
any
special
treatment
or
restrictions,
or
things
like
that.
So
so
far,
it's
looking
good
and
then
moving
on
to
the
line
chart.
B
Yeah
so
I
just
started
with
this.
This
is
a
good
little
intro
into
what
we're
I
guess
trying
to
accomplish
here
with
the
dashboards
I've,
mostly
today
been
stuck
in
the
surrounding
infrastructure.
To
this
so
I've
updated
the
documentation
on
our
kitlab
UI
for
charts,
because
that
was
a
bit
yeah.
It
was
like
a
high
Quantic
space
for
me
and
just
wanted
to
make
it
simpler
for
the
next
person
also
to
figure
out
like
how
to
use
each
arts
and
what
all
the
options
are.
B
The
Bridge,
Crossing
and
also
I
have
a
general
item
that
we
just
follow
up
on
or
just
get
a
check
in
on
where
we
are
with
the
schema,
since
that
also
impacts
the
change
they're
making
so
yeah.
D
Sorry
I
was
yes,
I.
Think
there's
a
point
in
number
five
to
talk
about
it,
but
basically
like
like
to
get
it
wrapped
up.
But
let's
come
to
it
at
the
agenda.
E
A
That
later
I
think
we
haven't
really
been.
E
Coming
down
nice,
okay,
just
so
the
admin
settings
is
an
initial
front-end
and
back
and
review
set
a
few
rounds.
Hopefully
this
will
be
the
final
round,
I'm
actually
reviewing
it
right
now
and
the
second
item
we
could
actually
close
it
off.
I
feel
like
we
could
just
remove
the
front,
end
aspects
of
that
and
just
close
that
off
Max
to
be
fair
rather
than
transferring
it.
E
We
could
just
copy
the
we
can
just
copy
the
enable
disable
settings
bit
into
the
other
issue,
because
the
only
reason
it
was
split
was
just
because
we
weren't
sure
when
you
were
going
to
be
able
to
get
to
it
because
you
got
to
it
so
quickly
before
front
end
was
even
done.
It
makes
no
sense,
it's
just
a
check
button.
We
can
just
close
it
off.
It's
fine
yeah.
A
Thank
you
all
right.
We
haven't
really
been
tracking
closed
issues,
but
I
know:
we've
done
a
bit
and
there's
some
new
ones
in
here.
I
feel
like
basic.
A
I
feel
like
the
basic
blocks
and
upwards
has
been
new,
but
I'll
just
leave
it
to
the
group
to
if
anything,
they'd
like
to
call
out
as
far
as
completed
items
here.
A
Looks
like
we
got
the
license
check
behind
and
we
also
removed
the
dead
code
from
the
former
attempt
to
do
product
analytics.
So
that's
great.
That
was
a.
E
A
B
Sure
so
I
just
wanted
to
check
in
on.
What's
still
remaining
for
us
to
define
the
version,
one
of
the
user,
dashboard
schema,
I
know,
there's
still
one
remaining
open
question
from
Tim
regarding
how
we're
going
to
Define
stuff,
like
date,
ranges
on
the
dashboard
and
how
that's
also
going
to
then
be
inherited
by
or
override
widget
definitions,
but
in
terms
of
anything
else,
yeah
I
think
Max.
You
also
have
a
point
and
then
also
the
following
agenda
item
for
this
yeah.
D
So
I
think
I'm
working
on
the
Assumption
at
this
point
that
it's
not
going
to
change
a
huge
amount.
I
think
the
discussion
that
you
and
Rob
obviously
had
was
a
really
really
good
step
forward.
So
that
was
good.
D
There
is
a
still
open
conversation
with
Tim
who's
out
today,
so
I
would
like
to
have
agreed
a
version.
One
schema
by
the
end
of
this
week,
if
possible,
just
because
I'm
kind
of
limited
to
how
much
backhand
work
I
can
do
while
that's
still
in
Vlogs
I'm
making
some
assumptions
at
this
point
like
title
and
description
for
a
dashboard
is
probably
unlikely
to
change,
but
the
actual
relationships
between
like
widgets
and
figures
and
stuff,
like
that
I'm
aware
that
that
might
not
be
exact.
D
Yet
so,
let's
see
where
that
conversation
with
Tim
goes,
and
hopefully
we
can
mail
something
down
by
the
end
of
the
week
in
terms
of
adding
a
due
date.
Let's
add
a
due
date
at
the
end
of
the
week
to
the
issue,
because
at
least
then
we
can
say
you
know
this
would
be
good
and
also
you
know
we're
doing
it
in
such
a
way
where
the
schema
can
be
Illustrated
on
anywhere
in
the
future.
So
that's
fine.
D
Thank
you
so
yeah.
The
next
issue
leads
into
the
next
Point
leads
into
that
I've
started
some
back-end
work
to
basically
process
those
yaml
definitions,
convert
them
into
Ruby
objects
and
make
them
available
to
two
endpoints,
one
of
which
would
make
a
list
of
dashboards
for
a
project
available.
I
would
make
more
data
about
this
dashboard
available,
first
of
which
I've
started
an
MRI,
but
there
are
two
or
three
open
questions
on
that
issue.
I
know,
Sam
has
already
fed
back
about
them,
but
yeah.
D
If
there's
any
more
inflammation
that
anyone
any
more
questions
that
people
have
about
that
before
I
get
too
deep
into
it.
That
would
be
good,
I've
added
a
rest
endpoint
in
my
sort
of
first
draft
Mr,
but
you
know
Sam's
race,
a
good
point
that
we
are
graphql
first
and
I.
Don't
really
have
a
strong
opinion,
either
way
so
yeah.
It's
just
something
to
have
a
look
and
do
I
think
when
you
get
a
chance.
A
D
Yeah
I've
been
working
on
the
Assumption
of
developer
because
currently
the
proxy
API
to
cube
is
developer
or
higher.
So
it
just
kind
of
followed
that
this
would
you
know
if
you
can
make
a
request,
a
cube,
then
you
probably
also
need
that
same
permission
to
see
those
outputted
dashboards
yeah.
But
again
that
can
absolutely
change
at
this
point:
we're
all
behind
a
deeper
I'll
preacher
flag
and
nothing
kind
of
works
in
production.
So
there's
no
dealing
with
breaking
or
anything
like
that.
Eileen.
A
Developers
was
I
think
more
from
a
semantics
point
of
view.
What
would
what
would
make
sense
there,
but
that's
that's
a
long
discussion
that
doesn't
have
to
happen
right
now.
So
Sam
you
have
the
next
point.
C
And
not
to
move
on
from
the
other
one,
just
yet
in
general,
I
think
this
is
an
area
we're
going
to
have
to
Circle
back
to
and
put
a
lot
more
Nuance
around
in
the
future,
because
if
we
want
to
go
down
the
route
of
having
embedded
dashboards,
those
will
need
to
be
public,
maybe
or
maybe
have
some
lighter
access
restrictions
or,
if
you're
aggregating,
say
Red
Data
with
your
app's
data.
Maybe
that
is
even
maintainer.
C
Only
so
I
think
this
is
somewhere
where
we
should
make
a
choice
for
now
with
the
expectation
we'll
need
to
revisit
it
to
make
more
nuanced
access
controls
in
the
future.
D
Yeah,
that's
a
very
good
point,
something
we
should
all
bear
remind
as
developers
as
well.
C
Yeah,
so
my
next
Point
I
wanted
to
signal
boost
I
created
an
okr
issue
for
our
group
for
the
coming
quarter.
This
is
going
to
be
the
first
okr
group
has
had
so
I'm
pretty
excited
about.
It
feel
free
to
add
feedback
or,
if
you
think
we
should
be
doing
something
different
completely
open
to
that.
C
C
A
Yeah
I
mean
to
be
fair.
I
wasn't
asked
to
make
okr
as
an
ally
for
this
quarter
and
for
the
for
the
for
analytics,
but
I.
Imagine
yeah
I
would
I
would
prefer
to
keep
it
in
gilab,
because
what
we
ended
up
doing
for
La
anyways
was
like
draft
and
then
get
lab
copy
them
over
to
Ally,
run
them
an
ally
and
then
eventually
feed
them
back
into
Gate
lab.
So
I
was
like
what
is
the
point
of
Ally.
A
Then
excuse
me
yeah,
but
yeah
I
I
will
probably
mirror
that
just
to
keep
things
simple,
but
I
was
just
curious
if
it
was
a
company
mandate
which
I
would
have
been
very
excited
about,
but
to
your
point,
I
mean
for
the
okr
just
to
throw
something
out
there
synchronously.
How
do
we
are
we?
Is
it
ambitious,
too
ambitious
to
think
about
instrumenting.com
in
the
next
quarter?
E
D
C
E
D
Rob,
there's
a
there's
an
okay
Target
as
well.
I
can
never
remember
what
it
is,
but
it
should
be
ambitious
enough
that
you
won't
hit
them
all
all
the
time.
I
can't
remember
what
it's
like
80
or
something
like
I
like
that.
As
an
idea,
we
can
say
you
know,
there's
instrument
gitlab.com
and
you
can
Define
quite
tightly
what
instrument
means
like
we
can
install
Jitsu
in
your
oral
jssdk
in.com,
whether
or
not
we're
providing
valuable
data
at
the
end
of
it
is
another
question.
D
A
And
it's
quite
constrained
already
because
we're
not
we're
only
tracking
direct,
like
contributors
to
the
project
right,
it's
not
anyone
that
hits
it
so
like
we're,
not
expecting
it
to
be
like
millions
of
events
a
day
or
anything
like
that.
But
at
the
same
time
we
can
still
even
apply
finer
grain
controls
to
even
like
say,
like
a
percentage
of
audience
that
even
meets
this
criteria.
To
begin
with,
could
do
that
so
I
I
just
would
like
to
see
I
mean
I'm.
A
Consider
me
challenging
us
to
see
if
we
can
push
a
little
further
beyond
the
handbook,
since
we're
kind
of
knocking
on
that
door
already,
and
we
still
have
one
months
left
in
this
quarter
so
so.
C
I
started
the
okr
out
as
that
and
pulled
back
the
reason
being
that
this
is
going
to
Encompass
the
new
year,
so
I
figured
we'd
have
a
lot
less
availability
due
to
holidays.
We're
also
going
to
need
a
lot
more
notice
period,
probably
at
least
two
weeks
since
we'll
be
doing
this
in
public
and
I
wasn't
sure
if
sequencing
of
that
made
it
realistic
or
not.
If
you
all
tell
me,
you
think,
that's
achievable,
though
I'm
certainly
happy
to
make
it
more
ambitious.
A
So
from
a
technical,
lift
point
of
view
granted
we
did
a
lot
of
instrumentation
and
things
that
have
to
happen
and
what
I
mean
by
instrumentation
is
like
us
monitoring
how
the
cluster
performing
so
that
we
have
other
questions
that
we
need
to
answer
like
that
still
has
to
be
figured
out,
but
in
terms
of
just
hitting
the
goal
being
able
to
collect
data,
from.com
I
think
that's
realistic,
but
yeah.
Well,.
C
Let's,
let's
go
ahead
and
update
this
okr
asynchronously
then
to
to
incorporate
that,
because,
if,
if
we
think
it's
ambitious
but
also
achievable
I'm
all
for
it.
C
A
This
is
just
a
heads
up
that
I
need
everyone
in
the
group
that
wants
access
to
the
cloud
environment.
That
doesn't
mean
you
can't
send
data
to
it,
but
if
you
need,
if
you
feel
like
you'll
need
access
to
the
cluster,
which
we
can
debate
least
amount
of
access
or
whatever
zero
trust
whatever.
But
for
me
to
create
the
group
environment
I
just
want
everyone
to
sign
into
the
sandbox
Cloud
realm.
A
All
you
need
to
do
is
just
hit
the
OCTA
button
authenticate
via
OCTA
and
once
you're
in
you're
good
to
go
that
way.
I
can
have
everyone
added
to
the
group
environment.
I.
Believe
I
can
add
you,
after
the
fact,
but
I
just
wanted
to
send
the
notice
out
now
that
you
know
it'll
be
better
if
you
do
it
sooner
rather
than
later,
for
those
that
don't
remember
the
gitlab
internal
project
on
gcp,
which
is
currently
what's
controlling
the
Prototype
prototype.gatlab.com
DNS
Zone,
if
it
hasn't
already,
it
will
be
deleted
this
week.
A
A
This
I
did
post
some
instructions
on
how
you
can
import
the
data
set
that
was
currently
in
the
the
test
cluster
into
your
local
environment,
so
that
you
have
some
data
to
work
with
as
far
as
dashboards
concerned,
so
I'm
looking
for
feedback
on
how
difficult
that
process
is
because
eventually
that'll
be
turned
into
something
where
we
can
see
the
the
local
environment
so
that
you
can
have
data
to
work
with
whenever
we
are
working
with
dashboards.
A
So
looking
for
feedback
there,
Rod
has
a
read-only
point
if,
unless
you'd
like
to
vocalize
it
otherwise
Sam,
you
have
the
next
point.
C
C
C
And
with
that,
we
are
at
the
end
of
our
agenda.
Any
other
topics
folks
want
to
go
through
before
we
break.