►
From YouTube: 2022-09-12 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
Welcome
to
my
new
office
aka,
the
car
I'm
not
driving,
but
my
oldest
is
today
at
the
for
the
first
time
at
his
football
training.
So
I
brought
him
here
to
doing
the
meeting
in
between
and
then
pick
him
up
afterwards
again
so
fully
remote
yeah
doing
it
classic
old
school
good.
But
this
means
that
I
need
to
work
with
a
small
screen.
Again,
let's
see
how
good
I
am
at
this,
so
that
I
can
see
you
also
at
the
same
time.
A
This
is
yeah,
so
I
have
an
announcement.
I
made
it
already
through
the
snack
Channel.
Today
we
got
this
last
week.
A
I
was
in
the
US,
so
I
was
traveling
a
lot,
so
this
took
a
little
bit
longer
to
get
everyone
pinged
and
merged,
but
I'm
very
happy
to
announce
that
we
have
added
a
new
product
category
to
the
product
intelligence
team,
which
means
that
we
have
aided
as
a
responsibility
the
application
instrumentation
thanks
a
lot
SIM
for
helping
me
to
name
this
whole
thing
and
going
through
the
second
iteration.
A
What
does
this
mean
apart
from
adding
a
category?
This
means
quite
a
shift
for
the
product
intelligence
team
on
the
long
term,
because
this
will
basically
mean
that,
as
we
have
in
the
analytics
section
now,
one
team,
which
is
product
intelligence
and
one
team,
which
is
the
analytics
team,
maybe
you'll,
find
also
another
T
name
at
some
point
for
this
to
make
it
less
confusing.
But
the
target
is
that
the
project
intelligence
team
will
take
over
all
the
instrumentation
parts.
A
So
everything
that
you
have
really
really
good
at
and
have
tons
of
know-how
about
in
the
sense
of
tracking
stuff
and
using
tracking
so
far
with
snowplow
understanding
how
our
applications
work
etc
and
will
be
in
the
future
irresponsibly.
So
this
means
that
the
tile
is
basically
that
product
intelligence
will
be
building
inside
the
product.
The
part
that
is
rating
all
the
tracking
this
means
the
tracking
SDK.
A
This
will
especially
I
think
this
was
the
first
discussion
that
we
started
already
in
a
slack
channel
was
around
event
taxonomy
and
then
also
reuser,
performance,
etc,
etc,
and
the
analytics
team
will
then
basically
focus
on
running
the
collector
and
running
then
also
all
the
the
visualization
and
data
display
Stuff
Etc,
and
that
Target
is
pretty
clear.
A
You
have
the
the
biggest
knowledge
and
know-how
at
all
link,
gitlab,
all
the
product
intelligence
team
members,
so
I
wanted
to
leverage
that
directly
and
be
part
of
the
whole
product
building
part
it's
a
in
reality
and
hopefully
over
time.
We
will
then
also
transform
that
you
added
two
responsibilities
get
smaller
and
smaller,
because
we
build
more
and
more
of
that
stuff
into
the
product
and
can
leverage
it
through
that
yeah
Sam.
Do
you
want
to
add
something
before
we
as
the
representative
of
product
before
we
go
over
questions.
B
No
I
I
think
you
did
a
really
good
job
covering
it.
There
Tim
I
will
say
one
of
the
things
that
makes
me
really
excited
about
this
change
is
that
we're
making
this
category
an
explicit
responsibility
for
the
group
that
it
sits
in
I
think
it's
going
to
be
very
easy
for
people
to
see
product,
instrumentation
or
product
analytics
and
just
assume
a
lot
of
the
magic
happens,
but
breaking
things
down
to
these
Standalone
pieces,
like
instrumentation,
is
really
going
to
help
folks
see
all
the
different
pieces
of
how
things
happen.
B
What
makes
up
the
final
Solutions
and
so
I'm
really
excited
to
see
this
being
broken
out
and
going
to
the
group.
A
C
D
Well,
if
it's
relevant
to
the
responsibilities,
we
can
go
ahead
and
jump
to
that
I
think
just
following
the
same
theme
so
feel
free
to
to
voice
your
point.
There
now.
C
So,
okay,
so
again,
it's
very
exciting
news
and
thank
you
very
much
for
like
pushing
out
to
us
and
involving
us
and
building
new
product.
This
is
three
great
thing.
I
just
wanted
to
ask
for
some
more
of
clarification
or
trying
to
to
expand
on
what
was
just
said
because
I'm
referring
to
the
long-term
goals
that
are
that
are
mentioned
by
by
Denise,
especially
the
taxonomy
or
optimization,
that
this
is
more
of
the
part
of
the
collection
pipeline
rather
than
the
tracking
itself.
C
So
we
rather
kept
the
tracking
and
or
and
the
sdks
as
a
very
thin
layer,
always
oftentimes
to
move
these
parts
to
the
collection
pipeline,
which
doesn't
mean
that
we
don't
really
want
to
work
on
that,
but
rather
just
trying
to
get
better
understanding.
C
What
was
the
expected-
or
maybe
you
could
just
like-
probably
iterate
over
that-
and
collaborate
and
well
jump
whatever
you
see
that,
but
but
what
to
do
voice
out
is
right.
Now.
A
Yeah
I
think
that
that
the
main
part
is
that
we
want
to
move
as
much
as
possible
already
onto
the
application
layer
so
that
we
have
I
think
it's.
It's
really
important
that
in
the
future
we
have
very
clear
data
that
is
coming
from
the
collecting
power,
slash
the
the
whole
tracking
SDK.
So
that's.
Why
I
believe
it's
really
important
that
we
have
a
clear
understanding
what
data
will
end
in
there?
We
will
still
at
some
point,
give
customers
the
whole
possibility.
A
We
add
whatever
you
want
and
on
top
Etc
but
I
think
it's
not
the
first
step
and
it
would
complicate
a
lot
of
things
there.
So
that's
why
I
think
it's
it's
really
important
that
we
figure
out
and
from
objective
the
whole
event
taxonomy
that
they
are
providing
if
we
should
get
this
into
the
SDK
and
how
we
can
build
it
in
there
Etc
and
around
your
other
comment
that
we
that
currently
the
product
intelligence
group
doesn't
have
a
front-end
engineer
yeah.
A
This
is
something
we
definitely
can
change
and
we
have
a
couple
of
more
hires
that
we
can
hire
at
the
product
intelligence
group.
This
will
be
also
a
moving
progress.
I
wanted
to
have
this
shared
and
merged
as
soon
as
possible.
So
it's
clear
for
everyone.
Yes,
both
of
our
teams
here
in
analytics,
are
working
on
the
product
and
get
you
all
involved
as
soon
as
possible.
If
this
means
already
like
trading
code-
and
we
received
River
figures
out
in
the
next
Milestone-
or
is
this
rather
of
like?
A
Okay,
let's
discuss
let's
review
what
we
have
currently
mapped
this
to
the
new.
Would
we
be
able
to
do
this
with
the
current
SDK
so
going
really
into
details
around
the
whole
tracking
SDK
implementation
right
now,
which
is
not
an
implementation?
A
And
that's
where
you
do
all
the
conversions,
so
I
think
that's
that's
something.
We
want
to
strike
less
exactly
with
the
know-how
that
you,
and
that
is
from
the
team,
have
that
we
are
not
building
in
tons
of
yeah
data
conversion
and
merging
Etc
I'm.
Pretty
sure
we
will
not
do
it
perfectly
from
the
start,
but
I
think
having
that
know-how
at
hand
that
this
is
super
vital.
Yeah.
D
And
with
there's
been
taxonomy
and
Seed
animalization,
we
definitely
want
to
just
leverage
you
as
a
subject
matter.
Experts
having
gone
through
that
already,
but
as
I
learned
from
you
know
your
your
work
in
product
intelligence
with
and
speaking
to
the
group
at
large
the
work
there
and
like
how
some
of
those
existing
Transformations,
because
some
of
the
event
names
were
like
misspelled
or
things
like
that.
D
D
As
much
knowledge
that
you
have
as
possible
that
product
intelligence
group
has,
but
obviously
this
is
the
first
step
with
instrumentation
in
terms
of
defining
ownership
there,
this
will
continue
to
iterate
on
that
to
figure
out,
you
know
where
it
is
event:
taxonomy
who's
going
to
own
event,
taxonomy
who's
going
to
own
pseudonymization,
but
until
then
we
obviously
want
to
balance
it
against
product
intelligence.
Existing
priorities,
there's
obviously
a
bunch
of
work
that
you're
already
in
Flight
with
you
know
migrating
the
versions
two
different
cluster,
and
things
like
that.
D
So
we
want
to
balance
that
so
that
we're
not
saying
hey,
we
want
to
use
your
knowledge,
but
then
also
can
you
do
all
this,
even
on
top
of
your
other
existing
priorities,
so
we'll
have
to
balance
it
for
sure.
Hopefully
that
also
gives
a
little
more
context
in
terms
of
how
do
we
plan
to
collaborate
on
that.
C
Applicable
for
for
classification
and
for
the
full
information.
D
Cool
any
other
questions
before
we
move
to
my
wall
of
text,
all
right
cool,
then
I
just
wanted
to
give
a
quick
update
just
to
get
one.
We
kind
of
reorient
ourselves
and
then
kind
of
give
us
give
also
an
update
on
a
variety
of
different
things:
the
moving
Parts
within
product
analytics,
so
the
main
goal,
of
course,
Still
Remains
on
iteration
one
in
terms
of
delivering
an
internal
preview
of
what
we're
we're
working
on
on.
The
main
goal,
though,
is
to
be
able
to
get
data
from
production
applications.
D
So
our
two
candidates
are
too
likely
cannabis,
not
I,
don't
think
that's
the
right
word
where
we
will
be
implementing
instrumentation
will
be
the
internal
handbook
and
then
a
very
specifically
scoped
project,
the
gitlab
project
within
gitlab
org
on
gitlab.com,
and
so
as
far
as
updates
there.
The
cluster
is
operational.
I
do
have
to
relocate
that,
and
so
we
that
will
be
good
to
go
this
week.
I
believe
we
should
be
able
to
get.
D
We
have
the
approvals
for
the
internal
handbook
as
well
start
instrumenting
on
that
Sam
to
your
point,
further
below
we
had
a
legal
review.
We
had
a
review
at
the
legal
team
last
week
and
so
I
will
follow
up
with
written
notes
on
that.
But
basically
we
have
the
go
ahead
to
implement
tracking
for
direct
users
of
the
gitlab
project
within
git.org,
but
we
will
have
to
work
on
a
cookie
consent
model,
because
that
does
not
yet
exist
on
the
product
side
of
the
application.
D
We
do
have
an
existing
implementation
using
one
trust
and
the
marketing
side
of
things,
but
I
think
we
can
do
something
a
little
bit
quicker
in
terms
of
just
like
some
simple
Banner,
opt-in
or
something
like
that.
Until
we
can,
you
know,
figure
out
the
full
details
of
creating
a
new
category
within
one
trust
and
things
like
that.
So
basically
we're
good
to
kind
of
build
the
technical
proof
of
concept.
We
can
then
touch
base
again
with
vehicle
make
sure
that
they.
D
What
we
discuss
is
what
they're
seeing
and
then
we
should
be
good
to
go
to
then
start
collecting
data
on
gitlab.com,
at
least
in
a
very
focused
manner,
on.
D
B
Well,
it's
encouraging.
They
approved
everything
verbally
at
least,
though
the
major
showstoppers
it
doesn't
sound
like
yeah.
D
The
main
discussion
points
that,
like
Justin
and
I,
helped
provide
clarification
on,
were
they
just
won?
They
I
think
it's
a
common
question
where
they
didn't
understand
like
what
product
analytics
is
doing
and
it's
different
from
product
intelligence,
and
you
know
our
analytics
stack
there
versus
snowplow
and
also
they
just
wanted
to
understand
why
we
wanted
to
use
cookies
or
collect
personally
identifiable
information,
because
of
course
we
want
to
be
able
to
be
as
close
to
the
functionality
that
our
users
would
be
using.
D
So
I
think,
once
we
clarify
things
they
were,
they
were
pretty
much
on
board.
There
were
no
major
objections
with
regards
to
why
we
were
collecting
that,
though,
of
course
pseudonymization
is
something
we
want
to
work
on
and
Implement
and
offer
as
a
feature
as
well.
D
So
you
know
at
least
we
have
full
approval
to
go
as
far
as
we
need
to,
despite
us,
maybe
not
using
that
fully
within
our
own
implementation
of
it
or
our
own
dog
food,
about
it,
cool
yeah,
so
yeah
I'll
follow
up
with
that
in
written
form.
Later
today,
I
also
had
asked
if
there
were
any
blockers,
we
had
already
talked
to
the
point,
and
so
longer
term
I
just
included
some
links
and
also
just
want
to
clarify
things
like
event.
D
Taxonomy
pseudonymization
are
all
very
important,
but
I
don't
believe
they
are
required
for
iteration
one
or
even
two
things.
These
are
topics
that
we
want
to
investigate
over
time,
but
you
know
there.
We
want
to
definitely
trying
to
get
closer
to
just
being
able
to
build
dashboards,
live
and
get
that
in
front
of
users.
So
yeah
I
just
want
to
clarify
that,
but
also
include
links
that,
like
mentioned
before,
we
want
to
leverage
the
experience
of
product
intelligence
team
members.
D
A
Yeah
I
will
I
read
out.
This
is
also
mainly
a
FYI,
but
the
manage
optimized
team
is
highly
interested,
also
in
our
crypto
dashboard
solution
and
what
we
started
working
on.
A
So
they
want
to
have,
and
they
will
need
quite
soon
or
they
need
some
custom
dashboard
Solutions
or
in
the
sense
of
that
users
will
be
able
to
build
dashboards
based
on
value
stream,
analytics
data
Etc
depending
on
the
data
source.
We
still
need
to
see.
Maybe
they
also
are
interested
in
using
Cube.
B
A
It's
not
tomorrow,
it's
someone
else,
I
think
it's
even
maybe
next
week,
then
it's
easier
and
we
can
still
move
it.
I
will
find
it
and
send
you
the
invite.
B
A
They
have,
they
have
a
little
bit
work
where
they
did
configuration
in
the
camera
file
for
the
overview
on
the
dot
in
statistics,
but
that's
it
they.
They
have
everything
hard-coded,
nothing
where
people
basically
can
edit
and
set
up
their
own
stuff.
A
But
that's
what
I
want
to
create
release
that
we
have
one
system
I
clearly
can
see
this,
that
we
might
even
have
some
more
teams
in
the
future
also
work
either
on
the
dashboarding
functionality
or
provide
them
to
you
components
or
basically,
components
that
will
be
sitting
in
the
dashboard
and
that's
something.
I
think
that
is
is
super
important
that
the
Align
this
as
early
as
possible.
A
And
or
they
are
also
looking
into
getting
the
database
replicated,
maybe
in
clickhouse,
which
would
already
allow
us
then
for
a
service
ping
at
a
later
version
have
also
a
lot
of
data
that
we
need
for
service
ping.
Stuff,
then,
basically,
based
on
accounts,
Etc
have
that
in
clickhouse
and
rather
query
that
then
the
normal
postgres
database.
A
So
this
is
definitely
a
longer
a
little
bit
Below
on
the
roadmap
for
them,
because
this
will
be
a
huge
lift,
but
it
seems
more
and
more
that
this
is
something
highly
needed,
that
they
can
actually
create
analytics
and
not
work
a
couple
of
Milestones
on
the
on
the
query
so
that
they
perform
actually
on
a
larger
scale.
So
I
think
this
is
one
more
becoming
a
topic
and
then
Cube
definitely
is
also
a
topic.
C
There
are
probably
different
solutions
because
it
was
cube.js,
but
in
the
on
the
like
goals
or
ideas,
they're
the
same
there's
a
different
types
of
configuration,
but
storing
and
my
plating
dashboards
via
code
or
linking
cross-link
in
the
issues.
All
of
this
work
has
been
done
and
the
code
probably
still
in
the
code
base,
so
there
may
be
opportunity
to
reuse
and
repurpose
it
for
the
product
analytics
goals
which
might
save
us.
The
effort,
especially
on
the
initial
iterations.
D
C
D
Exactly
to
the
discussion,
but
I
believe
this
is
where
your
comments
about
monitors.
Apms
work
is
so
we
can
all
fall
up
there.
A
B
Was
today
the
everyone
wear
your
get
lab
shirt
day.
It
looks.
E
B
For
for
the,
the
seven
of
us
are
matching.
E
A
B
Whoever
they
picked
I
liked
the
likes
the
manufacturer
for
sure.