►
From YouTube: 2022-08-22 Analytics Section Meeting
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
Yeah
I'm
happy
to
kick
out
sorry,
it's
all
right,
hello!
All
welcome
to
the
analytics
section
meeting
20
to
22nd
of
August.
That's
the
date!
Yes,
I've
been
signing
my
name
on
things
this
morning
and
I
still
don't
remember
the
day.
I
might
as
well
kick
off
since
I'm.
First
on
I'm,
Rob
just
joined
from
the
compliance
team
in
manage
howdy
I'm,
a
front-end
engineer,
I've
joined
the
product
analytics
team
to
try
and
help
get
it
off
the
ground.
A
I've
started
looking
at
Cube
JS
and
understanding
how
security
context
I've
put
an
initial
brain
dump
in
an
issue
which
I've
linked
to
already.
So
if
anyone
wants
to
contribute
or
tell
me,
I'm
an
idiot
deal
free,
I'm,
still
very
much
trying
to
get
my
head
around
this
whole
problem
space.
So
the
more
I
learn
the
the
better.
It
will
be.
B
Welcome
Rob,
but
have
you
on
board,
looks
like
we
got
Max
next.
C
The
same
really
yeah,
you
need
to
the
analytics
team
from
compliance
I'm,
a
back-end
engineer.
My
focus
so
far
has
been
trying
to
figure
stuff
out,
basically
so
I'm
looking
at
specifically
how
we're
going
to
connect
gitlab
projects
to
Jitsu
and
closing
that
whole
Loop
into
Cube,
which
I
wasn't
helping
me
with
the
last
couple
of
days.
C
Yeah
spending
a
lot
of
time,
just
sort
of
reading,
stuff
and
thinking
about
it,
and
then
writing
some
of
it
down
before
I
actually
get
into
the
meat
of
it
all
so
I've
linked
to
an
issue
I've
been
working
on
so
far,
so
you
can
follow
that
along
async
and
I'm
going
to
try,
hopefully
at
least
once
a
day
to
contribute
what
I've
been
fiddling
with
basically
back
to
the
dev
kit,
so
others
can
pick
that
up
as
well
feel
free
to
set
up
coffee
chats.
D
Welcome
Rob
and
Max
to
another
exception:
yeah.
Another
announcement
is
that
I'm
gonna
transfer
it
from
probably
the
intelligence
to
engineering
productivity
and
then
back
to
IC
and
I
will
officially
start
on
Tuesday
on
Thursday
of
August
and
I'll
still
be
around
for
any
sport
that
anyone
who
might
need
and
yeah.
Thank
you
for
the
great
support
so
far,
especially
with
the
transfer
and
that's
it.
Then,
if
you
have
maybe
some
more
details.
B
Yeah
I
will
definitely
miss
you,
but
as
far
as
transition
details
go
I
kind
of
move
points
around,
but
I
will
be
out
of
office
from
the
31st
of
August
until
the
6th
of
September,
and
because
of
this
it
will
be
best
if
Elena
remains
kind
of
dri
for
any
questions
for
the
group's
ongoing
work
until
I
return.
B
That
said
this
week,
I'm
going
to
be
meeting
with
Lena
and
Amanda
to
get
a
get
up
to
speed
on
all
the
work,
that's
happening
in
product
intelligence
and
then
I'll
be
planning
to
schedule
some
coffee
chats
for
this
week
and
next
just
to
get
to
know
the
group
a
little
bit
better.
B
As
far
as
official
business
one-on-ones
will
start
when
I'm
back
on
the
seventh
and
then
you
know,
bear
in
mind-
and
this
has
been
communicated
already,
but
there's
a
new
engineering
manager
coming
on
board,
starting
on
October,
10th
and
so
I'll
just
be
interested
in.
For
you
know
briefly
a
month
or
so,
but
hopefully
we'll
you
know,
have
some
fun
working
on
product
intelligence
together
and
then
we've
got
some
words
from
a
couple
of
different
team
members
here.
If
they
would
like
to
vocalize.
A
Yeah,
just
congratulations:
ancient
productivity
is
a
really
interesting
group,
so
I'm
sure
you're
super
excited.
E
I
can
vocalize
my
Elena
thanks
for
all
your
contributions
over
the
years
on
product
intelligence,
I
think
one
notable
metric
that
can
sort
of
map
your
contributions
is
when
but
I
think
you
started
on
the
team.
The
percentage
of
customer
sharing
service
ping
was
something
like
30,
and
now
it's
well
over
two-thirds,
it's
like
68
69,
and
we
were
doing
things
like
manually,
generating
SAS
service
ping.
F
Yes,
something
that
I
definitely
can
add
on
on
top
of
that
is
like
yeah
thanks
a
lot
for
all
the
work
that
you've
done
in
product
intelligence,
but
especially
in
your
acting
em
role,
where
I
work
with
you-
and
this
was
really
great-
you
have
given
me
really
great
support
in
in
taking
care
of
the
team
and
during
this
transition,
and
so
I'm
really
glad
that
engineering
productivity
gets
a
fantastic
new
team
member
I'm,
pretty
sure
you
will
be
doing
great
work
also
over
there,
that
we
will
also
benefit
from
so
looking
forward
to
that
and
yeah
thanks
for
the
ongoing
support
and
I
can
definitely
let
you
know.
F
B
So
now
that
we've
got
two
new
team
members,
Robin
Max
on
board,
just
to
kind
of
give
a
brief
update
on
where
we're
at.
If
we
think
about
kind
of,
maybe
it
helps
to
show
perhaps
a
data
diagram
I
know
Tim,
you
have
a
new
one,
but
it
doesn't
include
all
the
fancy
different
features.
B
We
want
to
build
in
right
now,
but
if
we
think
about,
if
we're
looking
at
the
collector
in
the
git
lab
as
a
product
itself,
we've
got
Jeremy
and
axel
working
focused
on
the
dashboard
and,
and
you
know
getting
integrating
that
work
with
from
a
live
data
source
from
the
POC
as
well
as
the
you
know
how
we
want
to
have
it
driven
by
a
schema
and
version
controlling
that
and
so
on,
and
we've
got
Rob
and
Max
working
on
the
collector
and
it
seemed
in
terms
of
how
we,
you
know,
are
planning
to
manage
Jitsu,
integrate
with
Cube
and
make
sure
that
we're
you
know,
make
sure
making
sure
that
we're
acquiring
what
we're
supposed
to
be
querying,
especially
as
we
have
an
initial
pilot
stack
where
everyone
will
be
it'll,
be
multiple
people
on
that,
and
so
security
and
making
sure
people
can
only
see
their
own
data
will
be
very
important
there.
B
And
so
the
plan
is
to
eventually
meet
the
middle
and
I'll
include
that
diagram,
which
definitely
needs
to
be
updated.
Until
there's.
F
B
Version
that
we
can
use,
but
the
whole
point
is
that
we're
working
from
both
ends
in
terms
of
making
sure
that
all
the
services
are
working
together
and
integrated
properly,
as
well
as
the
features
that
the
users
will
be
interacting
with
and
then
hopefully
can
meet
in
the
middle
to
integrate
the
two
together
and
so
there's
a
number
of
issues
that
you
can.
If
you,
you
know
query
what
we're
looking
at.
That's
that'll
include
more
details
there,
just
not
to
include
too
many
links
to
issues
and
such
on
that
note.
B
B
Some
things
will
be
moving
around
so
I
apologize
in
advance,
but
and
also
in
terms
of
what
I'm
currently
focused
on
in
terms
of
our
pilot
analytics
stack
continue
to
getting
that
set
up,
getting
continue
to
refine
like
security
policies
and
making
sure
that
once
exposed
is
exposed,
and
if
it
is,
you
know,
it's
got.
B
Tls
certificates
and
things
like
that
also
working
on
instrumenting
it
and
making
sure
that
you
know
we're
able
to
monitor
the
performance
of
it,
not
only
so
that
doesn't
follow
over,
but
it'll
be
important
in
terms
of
how
we
actually
determine
like
how
much
things
cost
and
how
we'll
actually
factor
that
into
our
pricing
model.
B
So,
in
the
meantime,
Rob's
already
started
creating
issues
in
terms
of
how
we
can
get
the
Jitsu
Library
added
in
How,
we'll
get
permission
for
the
internal
handbooks.
It's
something
that'll
down
behind
Sam
will
be
on
top
of
in
Terms
of
getting
clearance
legal
as
we
move
towards
getting
more
real
production
data
along
those
lines.
I've
also
been
looking
into
how
we
can
have
some
simulated
traffic,
not
only
for
us
to
kind
of
help.
B
You
know
say
if
we
need
certain
flows
to
show
up
when
we're
actually
monitoring
these
we're
collecting
data
for
certain
applications,
but,
more
importantly,
for
having
a
data
set
that
is
relevant
and
usable
in
our
development
kits,
so
that
you
know
something.
That's
nice
with
click
house
is,
you
can
literally
just
say,
import
and
link
to
a
SQL
file
in
object,
storage
or
AWS,
and
so
the
the
goal
is
to
at
least
have
an
example.
B
Data
set
that
people
can
use
once
these
features
are
better
integrated
to
be
able
to
actually
query,
like
you
know,
simulated
traffic
on
the
GDK
and
eventually
maybe
use
the
simulator
itself,
but
yeah.
That's
what
I've
been
currently
focused
on.
That's
a
little
bit
of
an
update
on
what
the
group
has
been
focused
on
Tammy.
You've
got
a
couple
extra
points
here.
F
Yes,
thanks
a
lot
Dennis
for
the
update,
something
that
I
started
on.
C
C
F
No
meetings
so
I
have
a
bit
of
time
to
do
stuff
is
simply
get
the
repo
started
for
our
SDK,
so
that
we
can
encapsulate
mainly
chitsu
or
if
at
some
point,
we
want
to
write
completely
on
our
own
or
want
to
do
something
differently.
F
I
think
this
is
best
to
completely
encapsulate
this
part,
and
also
it
gives
us
the
possibility
to
extend
this
to
all
the
other
ideas
that
we
had
during
the
POC
phase
of
extending
the
SDK
there
and
also
bringing
in
the
knowledge
and
to
know
how
how
we
are
encapsulating
already
stuffing
tracking
what
are
things
that
we
were,
for
example
missing
in
snowplow
and
so
on,
and
so
on.
F
So
I'm,
currently
working
on
the
first
init,
which
is
simply
importing
Jitsu
and
it's
piping
it
through
to
the
init
call
and
that's
it
for
now
and
then
I'm
going
to
connect
with
the
product
intelligence
team
with
the
next
couple
of
days
to
really
see
that
we
can
bring
in
their
know-how
and
their
experience
of
how
to
build
in
the
tracking
Parts
how
we
are
going
to
do
now
session
handling.
F
If
this
is
something
we
already
basically
need
to
provide
some
some
identifiers
during
the
SDK
and
then
maybe
in
the
data
transformation,
add
another
session
record
Etc.
So
I
think
this
is
the
big
Next
Step,
so
that
we
can
literally
have
our
own
SDK
added
to
whatever
asset
we
have
internally
or
externally
to
then
basically
track
through
our
SDK
to
our
analytics
component.
F
We
finally
need
some
naming
that
we
need
to
get
around
in
the
next
couple
of
days
for
this
box
with
Jitsu
and
clickhouse
and
Cube
and
yeah,
and
then
the
big
Next
Step
will
be
the
proxy
and
tunneling
of.
B
F
Yeah
I
I
think
so
too.
It's
it
really
should
give
us
also
a
good
opportunity
to
build.
On
top
of
that,
I
was
looking
into
a
couple
of
different
sdks
so
that
we
have
basically
a
vanilla,
JavaScript
SDK,
and
then
we
can
also
get
this
extended
to
next
view,
react
and
whatever
and
basically
encapsulate
even
more
automatic
tracking
for
those,
so
that
people
can
use
it
and
yeah
shouldn't
be
too
hard
to
get
started
and
then
endless
possibilities.
B
So
it'll
be
good
to
see
it
all
working
together
as
far
as
hiring
updates,
I'm
still
working
on
tweaking
the
final
back-end
engineering
role
for
this
I'm
we're
looking
for
someone
with
a
little
bit
more
Ops
experience,
while
I've
been
enjoying
my
time
in
kubernetes
land
and
all
of
the
from
this
tied
to
that
looking
for
someone
that
can
handle
that
more
on
a
day-to-day
basis.
B
So
some
some
more
Hands-On
experiences
there.
Thankfully
there's
a
referral,
that's
coming
I
think
we'll
have
to
double
check
that,
but
there's
a
referral.
That's
come
in
that
that
should
fit
that
description.
So
we'll
see
how
that
looks.
As
for
the
remaining
front-end
engineering
position,
we're
looking
to
make
an
offer
there.
B
So
as
soon
as
we
have
more
news,
we'll
be
I'll,
be
I'll,
be
sharing
that
but
I'm
pretty
excited
about
that
as
well
and
then
just
as
a
final
note,
I'll
be
as
I
mentioned
before
out
of
office
for
about
a
week
starting
the
middle
of
next
week.
So
yes,
there's
a
lot
of
information.
I'll
stop
again!
If
there
was
any
questions
or
feedback
there.
E
Thanks
Dennis
hell,
if
I
haven't,
met
you
yet
good
to
meet.
You
I
think
some
of
you
I've
met,
feel
free
and
schedule.
A
coffee
chat,
I'd
love
to
get
to
meet
you
in
person.
But
if
you
haven't
seen
his
note,
Kenny
is
leaving
gitlab
and
the
the
crying
face
emoji
only
like
begins
to
capture
my
emotions
regarding
his
departure.
E
So
David
sent
a
note
out
recently,
but
I'll
be
taking
over
the
analytics
section
on
the
PM
side
in
his
absence.
I
put
my
readme
in
here.
If
you
want
to
learn
a
little
bit
more
about
me,
but
my
primary
focus
right
now
is
just
supporting
Sam
Sam's,
not
going
anywhere
he's
still
he's
still
acting
PM
for
the
foreseeable
future,
and
my
focus
right
now
will
be
helping
him,
but
also
spending
a
lot
of
time
on
hiring
so
I
I
had
about
four
interviews.
E
Four
screens
last
week
and
I
put
a
mini
update
here
before
candidates
in
team
interviews
for
product
analytics
and
two
for
product
intelligence.
So
I'm
pretty
pretty
happy
with
the
pipeline.
It
looks
really
strong,
so
hopefully
we'll
we'll
find
some
great.
A
great
couple
of
new
team
members
here
in
the
next
in
the
next
few
weeks.
C
F
C
B
B
Well,
it's
good
good
to
see
everyone
have
a
good
rest
of
your
Mondays.
That's
14
minutes
back
and
have
a
good
rest
of
your
weeks.
Take.