►
From YouTube: 2022-10-05 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).
A
Foreign
welcome
to
the
October
4th
our
very
first
product
analytics
group.
Sync
I
have
a
wall
of
text,
but
there's
definitely
been
some
contributions
from
the
rest
of
the
team,
so
I'm
having
to
go
through
those.
There
are
a
couple
read-only
items
made
throughout
your
Ledger.
A
A
A
But
point
being
is
that
we're,
as
I've
been
saying
this
week
very
close
to
basically
connecting.com
to
the
the
what
we
would
call
the
internal
production
cluster
for
the
analytics
stack
and
so
there's
just
a
couple
of
items
we
have
here
on
the
agenda
that
I
can
share
my
screen
until
we
can
walk
through
it
together
and
then
have
others
speak
to
their
points
that
they've
added
to
it.
So
one
minor
thing
we
have
to
do
is
just
change
how
we
connect
the
gitlab
application
to
Jitsu.
A
The
dev
kit
uses
a
single
image
for
both
the
configurator
UI,
as
well
as
the
edge
server
that
supplies
like
the
library
and
receives
the
actual
event
requests.
So
the
Mr
needs
to
be
updated
and
we'll
probably
rename
the
variable
as
well
and
tangent
or
semi-related
the
work
that
Rob
will
be
doing
with
application.
Settings
that
refers
to
these
same
setting
via
the
UI
will
likely
have
to
be
updated.
There
feel
free
to
interrupting
if
there's
any
questions
or
feedback
as
well.
A
The
next
thing
that's
coming
up
would
be
making
sure
that
we
create
the
infrastructure
production
change
issue
so
that
they
can
want
to
understand
what
we're
doing
what
they're,
integrating
and
then
actually
detail
the
commands
that
they
have
to
run
on
the
rails
console
to
connect.com,
so
that
we
can
actually
set
this
up
for
the
internal
handbook.
A
But
as
we
do
that
I'm,
this
is
the
one
thing
I'm
kind
of
wanting
to
get
everyone's
feedback
on
is
probably
it
might
be
wise
for
us
to
start
doing
in
some
internal
Communications
as
far
as
like
the
rollout
for
the
internal
handbook.
So
that's
not
catching
anyone
off
guard.
A
It's
not
a
major
concern
from
a
legal
standpoint,
since
it's
part
of
our
General
I.
Think
agreement
like
in
terms
of
employment,
as
far
as
like
HR
and
legal
concern,
but
I
think
it'd
be
good.
To
like
have
some
internal
communication.
Science
is
something
we're
going
to
start
doing.
A
Sam
I
think
you
added
the
document
here.
I
was
curious.
Your
thoughts
on
everyone
else's
in
terms
of
like,
should
we
announce
this
before
we
kind
of
initiate
the
or
create
the
infrastructure
issue.
B
So
we
should
definitely
make
some
sort
of
internal
communication
before
this
goes
live
for
sure,
I'm
thinking
we
need
at
least
one
calendar
week
before
we
push
the
button
to
start
collecting
data
in
the
internal
handbook,
just
to
give
everyone
the
chance
to
opine
and
and
have
a
discussion
if
needed.
B
If
we
have
a
clear
line
of
sight
between
this
is
when
we're
going
to
start
making
these
infrastructure
changes
to
this
is
what's
going
to
happen
next
and
it'll
go
live
I'm,
certainly,
okay,
if
we
want
to
make
the
announcement
now
to
go
alongside
with
some
of
these
infrastructure
changes,
so
the
infra
team
has
the
contacts
as
well
as
everyone
else
right.
A
And
so
that's
kind
of
what
I'm
thinking
of
as
well
as
like
it'd,
be
good
to
point
them
to
somewhere
where
they
can
see.
The
context
see
why
we're
doing
this
and
then
have
an
issue
to
collect
feedback,
and
they
can
do
that
so
I
mean
it
wouldn't
take
long
for
me
to
draft
the
actual
production
change
issue
itself.
A
It's
just
more
of
you
know
providing
somewhere
for
them
to
understand
what
we're
doing
so,
whatever,
whether
that's
the
draft
document
or
whatever
the
document
will
be
in
its
final
form,
as
well
as
like
an
issue
for
them
to
like
collect
feedback
there.
So
it's
not
just
in
the
production
issue
itself.
A
Okay,
awesome
then
I
guess
would
you
need
just
kind
of
our
our
review
of
the
draft
document
before
we.
B
Yeah,
so
the
placeholders
that
we
would
need
to
reconfirm
before
publishing
it
is
what
is
the
data
we're
going
to
be
collecting
just
to
make
sure
that
it's
correct
still
and
then
timeline
details
for
the?
When
is
this
going
to
happen,
because
that's
the
really
big
to
do,
and
that's
the
only
one
that
I'm
aware
of
that,
we
haven't,
haven't
nailed
down
yet.
A
Yeah
I
guess
it's
a
chicken
and
egg
problem
of
like
when
we
know
the
dog
food
and
it's
like
well,
when
you
know
I
guess
we
can
show
this
without
that
part
answered
to
infrastructure
at
least
so
they
have.
They
have
the
context
and
they
have
a
place
to
get
feedback
and
then
once
they
kind
of
can
confirm
with
us
that
they're
good
with
it,
then
we
can
establish
that
timeline
for
when
they
can
actually
run
the
commands
to
connect
the
GitHub
instance
to
our
stack.
Would
that
make
sense
then.
B
Okay-
and
this
also
doesn't
have
to
be
a
I-
don't
think
this
needs
to
be
so
specific
of
it's
going
to
be
Tuesday
at
3
48
p.m.
If
we
want
to
put
something
around
right
now,
we're
working
on
getting
the
infrastructure
changes
pushed
to
production,
we
plan
to
let
that
settle.
Do
whatever
and
our
estimate
is
it's
going
to
be
live
a
week
after
that
or
something
to
that
effect.
I
think
that
would
be
all
right
as
well.
A
Yeah
I
mean
barring
any
major.
You
know
kind
of
requests
from
infrastructure
to
like
make
sure
that
they're
comfortable,
integrating
with
stack
I,
would
like
to
Target
the
end
of
October
at
the
latest.
So
I
think
that's
that's
yeah,
so
maybe
we
can
start
with
that
and
then
we
can.
We
can
fine
tune
it
if
we
have
more
insight
into
when
we
can
actually
or
if
we
can
bring
that
in
at
all.
B
Okay,
yeah:
let's
go
ahead
and
we
can
asynchronously
get
that
document
updated
to
kind
of
describe
what
the
plan
is
then
and
hopefully
get
it
posted
alongside
those
infrastructure
changes
in
the
the
near
future.
B
A
On
this
async
and
then
let's
yeah,
because
I
like
to
have
that
right,
basically
cool
now,
assuming
that
all
goes
well
and
we
have
the
approval
from
infrastructure,
we're
able
to
connect
to
all
that.
A
Then
we
have
the
internal
handbook
merge
request
that
Rob
is
already
set
up
to
actually
start
using
the
JS
SDK
to
send
events
to
so
once
the
once.com
is
connected
and
we
can
generate
a
Jitsu
key,
then
we
can
plug
that
in
and
start
collecting
data
for
internal
handbook,
and
that
gives
us
real
data
to
work
with
to
build
onto
the
dashboard
foundation
and
and
which
that
we've
been
working
on
already
so
I.
A
C
C
A
Thanks
for
the
clarification
there,
so
yeah
we'll
definitely
make
sure
so
that
you
can
pick
up
the
host
and
key
there
from
the
environment
variables
cool.
D
Yeah
sure
thank
you
Dennis.
So,
regarding
the
the
work
we
have
been
doing,
the
Rob
and
I
with
the
dashboard.
We
created
a
feature
for
that,
and
this
is
basically
like
a
placeholder
issue
that
I
created
for
the
rollout,
so
I
just
I
just
wanted
to
bring
that
up.
So
we
can.
We
can
start
using
that
issue
to
to
track
whenever
we
want
to.
D
We
want
to
start
going
going,
live
with
the
with
the
handbook
project
and
and
besides
that,
something
that
I
didn't
wrote
down
was
an
update
regarding
the
the
the
the
the
progress
of
that
of
this
work
is
that
we
have
a.
We
have
a
green
pipeline
now,
after
after
publishing
and
refining
between
Robin
height.
So
we
are
really.
We
are
ready
for
for
reviews,
so
I.
In
fact,
I
believe
the
pipeline
is
just
finish:
nice,
yes,
yeah.
C
Just
so
I'm
happy
to
approve
from
a
front-end
point
of
view
and
then
you'll
need
to
get
two
back-end
reviews.
Anna
we'll
have
to
find
we'll
have
to
get
a
front-end
maintainer,
but
from
I'm
happy
to
approve
as
the
front
end
counterpart
initially
wait.
A
C
C
Been
pulled
out,
there's
a
separate
issue
that
Axel
set
up,
which
would
need
to
be
handled
I
mean
obviously
the
dashboard
Foundation
dashboard
stuff
doesn't
need
to
be
done
for
us
to
start
getting
data
from
the
internal
handbook.
C
This
is
just
stuff
we
need
to
get
done
to
get
customer
facing.
If
that
makes
sense
for
that
sort
of
to
begin
getting
data
would
be
super
useful
for
all
of
us.
I
think
and
test
stress
testing
the
infrastructure
Etc.
A
Yeah,
exactly
and
I,
don't
think
the
the
navigation
is
critical,
yet
until
they
start
getting
it
as
part
of
like
the
public
customer
preview,
which
will
likely
not
happen
until
you
have
the
cab
meetings
which
we
can
get
to
in
a
moment.
Very
cool
I
just
wanted
to
double
check
that
thanks
for
clarifying
right,
yeah,
the
next
play.
C
Yeah
just
to
say
that
I
had
a
great
chat
with
Brandon
from
optimize.
Luckily
worked
with
him
in
manage
before
and
he's
close
friends
with
Jan.
So
I
had
an
easy
in
to
be
able
to
start
talking
to
the
engineering
manager.
I
got
some
great
feedback
which
I
summarized
in
the
dashboarding
issue,
and
we've
started
implementing
in
Axel's
Mr
by
moving
things
to
EE
and
then
my
Mr
with
the
actual
widget
configuration
system
that
we're
creating
awesome.
C
As
soon
as
I
have
something
worth
seeing,
I'm
gonna
ping
Brandon
on
my
Mr
to
start
getting
his
feedback,
and
then
he
can
put
he's
he's
happy
to
pull
in
anyone
from
his
team
that
he
wants
to
get
eyes
on
as
well.
My
guess
is
initially
because
they're
going
to
be
quite
self-contained,
there's
not
going
to
be
much
in
the
way
of
commentary,
but
there'll
be
stuff
going
on
once
these
things
start
to
make
use.
C
They
are
very,
very
keen
to
get
this
dashboard
config
into
a
yaml
file,
because
that's
the
only
time
it
actually
makes
sense
and
is
usable
for
the
team,
but
they
at
least
doing
this
gives
them
the
ability
to
start
making
those
widgets
and
trying
those
out
before
they
get
to
that
point.
It
just
won't
be
usable
as
a
MVC
for
them
right.
A
That's
exciting,
I
think
some
good
first
steps
there
as
far
as
like
collaboration
with
them
yeah
very
cool,
coming
up
as
well.
I
guess,
I
also
missed
onboarding,
which
is
something
we'll
want
to
look
at
as
well,
but
as
far
as
admin
settings.
A
So
again,
if
I
can
eventually
get
this
demo
working
there
you'll
see
that
the
all
the
configurations
being
done
through
the
rails
console
so
part
of
that
is
creating
some
admin
settings
that
we
can
actually
plug
that
in
and
configure
it
from
the
product
itself,
but
that
would
be
coming
after
the
dashboard
foundation
in
terms
of
just
improving
the
usability
of
connecting
those
same
pixels
closer
to
that
customer
public
preview
so
and
so
yeah
like
that
will
be
necessary.
A
That
Rob
has
already
started
some
new
I
work
on.
So
thanks
for
for
doing
that,
anything,
you
want
to
speak
to
that
I
speak
to
at
this
point.
C
The
UI
is
now
ready
to
be
developed,
so
be
great
to
get
that
assigned
I'm
happy.
If
Axel,
you
were
mentioning
to
me
the
other
day
that
you
were
thinking,
you
might
be
running
out
of
stuff
to
do
soon.
So
if
you
want
to,
if
you
feel
comfortable
I'd,
be
more
than
happy
for
you
to
pick
that
up
and
start
developing
that
alongside
the
dashboard
work
you've
been
doing
until
we
can't
do
the
Cube
stuff
until
I've
done
the
widget
stuff.
C
So
that's
I'm,
being
a
Blocker
on
you
at
this
point
and
just
to
note
that
there
is
an
enabled
enabled
product
analytics
checkbox
which
is
being
split
out,
which
we
don't
have
the
settings
for
that.
Yet
that's
now
a
separate
issue.
So
there's
a
there's
going
to
be
two
parts
to
this,
but
the
second,
the
chat
boss
is
going
to
require
back-end
engineering
know-how.
C
So
that's
either
going
to
be
Max
or
myself,
probably
whoever
gets
to
that
first,
but
that's
a
lower
priority
than
just
getting
these
UI
settings.
It.
D
C
Okay
issue
and
if
you
have
any
questions
with
the
I've
written
out
a
rough
information
plan,
but
if
you
have
any
questions,
just
let
me
know
I
will
yes.
A
I
can't
type
talk
again
on
me
and
myself.
At
the
same
time,
I
just
wanted
to
add
more
detail
to
the
onboarding
section,
so
Rob
already
has
created
some
great
flow
diagrams
in
terms
of
how
this
stack
service
is
currently
working.
A
A
We
would
also
need
to
be
able
to
actually
trigger
the
the
connection
to
like
basically
get
that
Jitsu
key
whenever
we
want
to
enable
it
for
the
Jitsu
service
and
so
I
think
that's
another
part
of
the
onboard.
The
flow
which
robs
into
already
have
been
working
with
with
figma
I
I
would
assume,
naturally,
you'd
move
on
to
that
at
some
point.
Once
you're
once
you're
done
with
the
dashboarding
aspect,
does
it.
C
Yeah
exactly
the
I've
linked
to
these
flow
diagrams,
underneath
I've
been
enjoying
them
far
more
than
mermaid.
Just
from
a
visual
perspective.
They
are
a
lot
more
distinct
and
super
super
easy
to
do.
Just
copy
paste
copy
paste
are
brilliant,
whereas
mermaid
can
get
a
bit
fiddly
at
times
yep.
C
My
next
aim,
taking
that
flow
diagram
that
with
the
rough
idea
of
how
it
would
all
work,
I'm
going
to
start
trying
to
map
out
mock
up
some
rough
UI
so
expect
to
hear
from
me
Sam
quite
extensively
because
I'm
not
a
designer,
so
I'm
gonna
do
my
best,
and
it's
also
why
I
don't
really
have
time
to
take
on
the
admin
settings
and
stuff
because,
as
you
said,
as
soon
as
I
get
through
this
we're.
Just
that's
one.
C
That's
my
second
Focus
because
then
once
I've
mocked
those
up
and
got
those
into
some
issues,
then
me
and
axel
and
Jan
are
going
to
be
busy
for
a
little
while,
because
there's
going
to
be
quite
a
few
things
to
create.
A
Pressure
yeah
sounds
good,
sounds
exciting,
so
yeah
definitely
a
lot
of
things
to
kind
of
help
polish
and
get
us
to
that
public
figure,
but
yeah
as
we
of
course
Focus
for
the
short
term
in
terms
of
just
collecting
data
on
a
journal
handbook
and
getting
those
dashboard
we're
just
going
yeah,
that's
a
little
bit
further
out
for
sure
trying
to
look
forward
to
cool
so
I'm
still
waiting.
A
Also
Zoom
is
really
messing
with
my
mouse
Focus,
so
I
apologize
for
all
the
flipping
Windows
I
had
a
couple
questions
that
have
kind
of
come
up
as
I
was
testing
this
ferment
and
I
promised
it
did
work
at
one
point,
but
the
content
security
policy,
so
the
internal
handbook
looks
like
it
both
uses,
unpackaged
and
then
now
JS
delivered
the
content,
delivery
network,
I
guess
rob
you
have
a
point
to
this,
but
I
had
some
instructions,
so
development
kit,
Purge
requests.
A
Yes,
so
my
previous
instructions
on
the
dev
kit
involved
changing
the
git
by
the
ammo
file,
which
is
not
recommended
because
that
gets
automatically
recreated
every
time
you
run
reconfigure.
So
I
do
have
a
merge
request
here
to
actually
make
that
option.
Configurable
I
just
need
to
see
that
through
that
said,
that
is
what's
going
to
allow
us
to
at
least
Define
the
content,
security
policy
or
disable
it.
So
it
can
work
with
how
we're
using
the
JS
SDK,
where
I
tested
for
the
on
the
on
the
various
cdns.
A
But
we
will
need
to
also
update
that.com,
because
that
does
have
a
very
strict
content
security
policy
to
make
sure
that
when
we
do
enable
this
on
the
gitlab
project
within
gitlab
org,
the
last
thing
I
want
to
do
is
have
a
bunch
of
battle
requests,
because
the
content
security
policy
isn't
allowing
us
to
download
the
JS
SDK,
so
good
call
out
there.
Max
is
for
the
GDK.
I
will
put
that
right
now.
C
I
don't
or
see
the
CSP
being
a
particular
issue,
though,
for
an
externally
loaded,
Javascript
file,
a
problem
and
if
anything,
your
MR2
disable
CSP
I
doubt
that
will
get
acceptance
from
the
gtk
developers.
They
will
rather
see
us
do
what
they
did
with
snow
plow,
where,
when
snowplow
was
enabled
it
gets
appended
to
CSP
we
shouldn't
I,
don't
I,
don't
see,
we
don't
have
any
other
issues
with
other
external
scripts
and
fingers
crossed
we'll
be
okay
with
it.
The
one.
C
The
one
point
that
makes
me
question
is
if
we
start
link
connecting
to
a
local
copy
of
the
SDK
for
development,
rather
than
pointing
to
a
published
version
public
connecting
to
your
local
instance.
Instead,
that's
where
things
might
get
a
bit
iffy.
A
Yeah
I
well
I
mean
so
they
have
this
long-standing
issue
to
like
move
to
anything
that
is
configurable
in
the
gitlab
gamble
to
something
that
you
can
flip
on
and
off.
So
I
feel
like
this
is
in
line
with
that
I
I,
but
I
understand
that
like
if
it
was
brand
new
setting
in
terms
of
just
completely
disabling
it.
That
would
make
sense
but
yeah
I.
Just
wonder
if
that
gets
trickier.
A
If
we
have
to
like
keep
modifying
how
we
extend
the
CSP
locally,
if
we
do
want
to
reference
it
locally,
but
yeah
I
guess
we
can
especially.
C
A
A
Might
be
useful
in
some
cases
to
turn
it
off,
but
the
fault
is
still
enabled
which
is
in
the
merge
request.
So
you
know
maybe
we
can.
We
can
take
that
discussion
in
the
merge
list.
We're
we're
actually
running
low
on
time,
and
so
there
were.
A
A
E
Yeah
I'm
going
to
shout
this
out
this
afternoon,
I'm
pretty
sure,
based
on
the
documentation
that
all
it
does
is
restrict
access
to
the
configuration.
Endpoint
I'd
be
very,
very
surprised
if
it
changes
the
port
number
at
that
point.
But
it's
it's
on
my
list
to
check
today.
So
I'll.
Let
you
know
before
I
finish:
got
it
yeah.
A
Cool
you
can
follow
up
on
that
next
time
cool.
There
was
this
kind
of
topic
with
priority
alignment,
but
I
think
I've
met
with
most
everyone
at
this
point
and
it
seems
like
we've
got
plenty
of
work
to
kind
of
chase
after
at
least
until
the
next
time
we
meet.
So
that
was
kind
of
the
my
question
for
this
one
was
going
to
be:
does
everyone
have
kind
of
a
clear,
clear
view
of
what
they're
going
to
be
working
on
the
short
term?
It's
a
safety
dot.
A
C
Sure
it's
not
really
a
show
and
tell
but
I'm
I'm
happy
to
I'm
happy
to
show
anyway,
so
just
pointing
out
that
I
have,
as
mentioned
already
I've,
been
creating
these
in
figma.
These
this
one
is
feel
free
to
use
them
with
with
other
people
outside
or
in
the
case
of
the
cab.
If
it's
useful,
Sam
you're
more
than
welcome
to
use
them
when
trying
to
explain
the
process,
especially
if
they're
a
bit
more
technical.
C
So
this
is,
for
instance,
to
zoomy
two
zoomy.
This
one,
for
instance,
is
the
quick
one
I
wrote
recently,
which
Max
hasn't
seen
on
probably
argue
against.
At
some
point,
I've
done
something.
E
C
Well,
that's
all
right,
then,
that
just
generally
explains
how
the
stack
system
works,
which
then
ties
into
this
one,
which
is
what
the
flow
diagram
the
onboarding
flow
is
supposed
to
do,
which
is
actually
mentioned
as
an
analytics
stack
setup
service.
So
it's
just
because
we're
dealing
with
very
abstract.
Sometimes
things
is
quite
useful
to
have
that
visual
aid
to
help
break
down
how
it
always
meant
to
flow
together,
at
least
for
me.
C
So
if
you
don't
have
a
figma
account,
I
highly
recommend
creative
one
and
having
a
play,
you
just
use
a
fake
Jam
file
and
they
pre-
come
pre-configured
with
a
bunch
of
flowchart
elements.
You
just
drag
and
drop
and
have
a
fun
play
time.
A
Yeah,
the
cluster
I've
done
something
wrong.
This
is
what
happens
when
I
play
with
it
before
to
demo.
So
I
will
record
a
video
and
I
will
send
it
out
and
post
it
on
this
live
Channel
when
I
am
able
to
get
it
sorted.
So
I
was
trying
to
mess
around
with
TLS
certificates
and
I'm,
not
paying
the
price
cool.
Let's
see
here
so
as
far
as
what's
left
on
the
agendas
yeah.
B
B
B
B
B
B
E
Sounds
good
yeah
I
just
wanted
to
make
sure
it
wasn't
you
alone,
so
that
would
have
been
a
bad
thing,
but
it's
always
good
to
have
other
folks
in
the
room
too
yeah
for
sure.
A
Sam,
do
you
know
exactly
when,
in
that
two
and
a
half
hour
window,
that
we
are
I,
don't
know
what
this
is
going
to
be
up?
Just
so
I
can
make
sure
I'm
available.
B
Oh,
it's
40,
40
minutes
in
so
I.
Think
that'll
put
us
right
around
11,
40,
Eastern
Time.
A
A
But
no
that
should
be
fine
cool
I've
done
a
last-ditch
effort
to
restart
some
of
these
deployments.
They
are
not
responding.
So
I
will
record
that
another
time,
thanks
for
dealing
with
that
and
we're
at
the
end
and
we're
almost
at
time
and
we're
at
the
final
point
anyways
any
questions,
any
feedback,
any
thoughts.
Anyone
else,
any
sorry
is
there
anything
else.
Anyone
would
like
to
share.
C
I
had
one
thing
I'd
like
to
I'd
like
to
find
out
from
that
cap
is
how
what
sort
of
events
do
they
track
and
what?
How
do
they
consume?
That
data
like
when
they
is
it
gesture
going
to
Google,
anatics
and
looking
at
the
charts,
or
are
they
actually
doing
anything
more
detailed
and
linking
in
with
other
behavioral
analytics
or
business
analytics
type
scenarios,
because
that'd
be
useful
from
a
from
our
point
of
view
to
make
sure
that
we're
rendering
the
right
kind
of
data
for
them
in
the
right
ways.
D
B
Yeah
I'll
be
sure
to
bring
that
up
with
them.
Then,
thanks
for
the
question.
A
Anything
else
all
right,
then,
thanks
for
everyone
for
sharing
added
to
the
agenda,
it's
good
to
see
everyone
and
here's
to
many
more
product
analytics
groups.
Thanks
have
a
good
rest
of
your
days
and
weeks
and
enjoy
family
and
friends
day
and
see
you
all.
Next
time
see
you
folks,
bye.