►
From YouTube: 2022-10-03 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
All
right
there
we
go
welcome
everyone
to
the
October
3rd
edition
of
the
analytics
section.
Meeting
I've
got
a
laundry
list
of
agenda
topics,
but
if
anyone
would
like
to
add
to
it,
please
feel
free
to
do
so
happy
to
talk
about
anything,
that's
happening
and
within
the
analytics
section,
but
I'll
start
things
off
with
a
bunch
of
recent
announcements.
Some
of
them,
since
we
haven't
had
a
meeting
in
about
two
weeks
you
may
have
seen,
but
with
worth
reiterating
in
case
you
did
miss
it.
A
B
Yeah
so
I'll
just
say
again:
I'm
super
excited
to
be
here:
I
think
we
really
have
a
great
set
of
opportunities
ahead.
Us
ahead
of
us,
with
the
analytics
section
between
both
of
our
groups.
I
think
we
have
a
huge
chance
to
make
a
difference
for
our
external
customers,
as
well
as
internal
customers
and
I'm
excited
to
go
on
that
Journey
with
you
all
together.
A
Definitely
exciting
stuff
continuing
the
exciting
news
you
may
have
seen
recently
that
Jan
will
be
joining
us
from
compliance
starting
on
October
18th
Rob
is
very
excited
about
that
visibly
Tim
as
excited
as
well.
Smiles,
I
think
Smiles,
it's
very
good
and
that
completes
sorry.
That's
a
good
question
joined
us
from
compliance.
I
already
wrote
this
once
and
I
forgot
already
joining
product
analytics
as
a
front-end
engineer
there.
So
that
means
we
are
and
I'll
jump
a
little
bit.
A
We
are
still
looking
for
a
front
end
engineer
for
product
intelligence.
I
didn't
announce
that
during
the
I
did
announce
that
during
the
group
sync
but
I'm,
just
announcing
it
out
of
the
wider
audience
here
speaking
is
very
difficult.
I
apologize
just
in
the
case
anyone
has
referrals
for
front-end
Engineers
for
for
the
product
intelligence
group.
A
That
is
the
final
one
that
we
have
for
the
section
for
this
year,
though,
hopefully
we
can
add
even
more
on
top
of
that,
so
yeah
Jan
will
join
us
on
the
18th
there
and
then
just
as
another
reminder.
A
Since
we've
been
counting
down
the
time
next,
Monday
Sebastian
will
be
joining
us
as
engineering
manager
for
product
intelligence.
So
a
lot
of
new
faces
a
lot
of
official
a
lot.
A
lot
of
good
people
coming
on
board,
so
I'm
very
excited
about
that
and
to
round
out
good
news.
A
Just
as
another
reminder,
we
do
have
another
friends
and
family
day
for
October
7th,
so
don't
forget
to
put
that
into
PTO
by
roots
and
enjoyed
a
long
weekend,
yeah
along
as
far
as
group
updates,
starting
off
with
product
analytics,
we're
getting
very,
very
close
to
being
able
to
instrument
or
add
instrumentation
to
the
internal
handbook.
I
gave
a
demo
to
this
to
Tim.
Perhaps
I'll.
A
Do
it
to
this
group
if
if
people
are
interested
enough
and
it
I
have
not
prepared
for
it,
so
if
you
want
to
see
what
it
looks
like
for
me
to
demo
very
often
offhand,
then
I
would
be
gladly
willing
to
entertain
that
or
I
can
record
a
demo
as
well.
Amanda
that'd
probably
be
working
better
when
I'm,
not
at
the
talent
of
my
day
here,
but
it's
up
to
you,
but
at
any
rate
I've
tested
and
complete
end-to-end
integration
of
getting
the
analytics
stack
set
up.
A
Obviously,
in
our
production
cluster,
getting
that
integrated
with
gitlab
as
a
product
with
my
GDK,
which
would
be
easily
replicated
through
with
our
production.com
instance,
they
could
watch
the
recording.
That's
true,
but
basically,
the
point
being
is
that
I
was
able
to
go
and
set
everything
up
from
start
to
finish,
including
instead
of
getting
the
code,
the
Jitsu
code
that
we
get
from
integrating
with
the
service
and
then
being
able
to
track.
A
Events
on
that,
and
so
I
have
that
working
on
my
own
local
environment,
but
just
to
be
able
to
compose
the
steps
required
for
infrastructure
to
do
on.com
and
make
sure
that
what
we
would
expect
to
see
is
what
we
would.
What
we
get
one
thing
I
did
catch
is
that
we
will
need
to
update
our
constant
security
policy
since
we
refer
to
an
external
script
for
the
JavaScript
SDK.
So
that
was
something
that
I
wanted
to
catch.
A
I'm
glad
that
I
caught
now
so
that
when
we
get
it
set
up
for.com,
we
don't
start
trying
to
track
things,
and
then
we
get
a
bunch
of
I.
Don't
remember
the
error
code
403s
or
something
like
that
when
we're
trying
to
to
load
the
JS
SDK
but
yeah.
That's
just
good
news
to
say
that
there's
a
couple
of
minor
steps
we
need
to
get
to
getting
like
the
final
steps
for
the
internal
handbook.
A
They
include
making
sure
that
we
are
able
to
hit
the
Jitsu
endpoint
correctly,
there's
a
minor
two.
We
have
to
make
there
with
our
authentication
file
there.
Of
course
we
need
the
production,
change,
tickets
or
issue
as
well
and
then
also
Sam's
is
more
of
a
question
to
you,
or
maybe
we
can
take
it
to
the
group
sync
as
well,
but
we've
obviously
got
kind
of
like
a
communication
schedule.
We
want
to
do
to
make
sure
that
people
both
internal
and
external,
to
gitlabber,
aware
of
that
we're
going
to
start.
A
You
know
collecting
data.
Maybe
this
is
not
appropriate
for
the
internal
handbook
right
now,
but
maybe
more
for
actually
instrumenting.com,
but
I
just
wanted
to
kind
of
check
in
with
you
there
and
then,
of
course,
we've
Rob
has
already
prepared
a
merge
request
for
the
internal
handbook
to
be
able
to
start
tracking
events
there.
So
once
we
have
everything
set
up
on
the.com
instance,
we
can
just
add
the
key
at
the
endpoint
and
we're
good
to
go
there.
C
Yeah
so,
as
you
mentioned,
the
the
content
security
policy,
would
it
can
I
haven't
looked
at
the
internal
handbook,
how
this
is
set
up,
but
would
we
have
also?
There
are
the
possibility
to
do
a
local
version
of
the
JS
SDK,
like
npm
node
modules
and
not
going
I,
think
we
are
in
the
Mr.
We
are
going
to
unpackage
so
that
we
are
staying
true
first
person
database
and
don't
have
the
content
security
policy
problems.
D
The
answer
that
is
I
know
really
it's
a
Hugo
server,
so
it
generates
static.
Html
with
a
compiled
JS
I
can
have
a
look
I,
don't
I
think
the
answer
is
no.
They
have
no
node
module
system
set
up,
but
I
can
take
another
look
at
it.
C
Yeah
that
would
be
cool
because
now
playing
the
tennis
Advocate,
not
that
I
would
bring
this
up.
But
then
there
are
people
like
yeah
you're,
doing
the
first
person
but
you're
sending
data
of
the
user
to
unpackage
because
they
are
downloading
the
GS
package.
There.
A
C
C
Ip,
it's
not
that
I
would
bring
up
this
argument,
but
I
know
that
people
could
bring
up
this
argument
in
the
classic
data
protection
app
for
discussion
view.
So.
C
Would
also
take
a
look
that
we
get
it
on
the
clouds
here,
yeah,
which
is
currently
all
the
villain,
but
that's
another
topic,
but
they
haven't
had
to
be
supposed
to
for
first
party.
C
D
The
using
package
is
purely
just
for
convenience
because
it
automatically
gets
from
npm.
You
know
gets
to
point
there
if
we
want
to
deploy
it
elsewhere.
If
we
can't
use
an
npm
module
I'm
fine
with
that
I
just
don't
know
how.
C
C
Let's
go
roll
with
a
local
version
if
it's
too
hard,
but
then
yeah.
B
A
They'll
see
it,
but
it's
good
to
just
be
upfront
about
it
and
try
to
calm
as
many
doubts
as
possible
at
any
rate,
I
don't
think
it's
going
to
be
the
biggest
deal
for
the
internal
handbook,
but
definitely
we'll
want
to
have
that
FAQ
ready
or
at
least
that
topic
of
trust
for
when
we
roll
out
to.com
and
specifically
to
to
instrumentation
there
Amanda
you
had
a
comment
as
well
about
communication.
F
Yeah
yeah
I
think
it
would
be
a
light
blog
explaining
what
you're
working
on
the
fact
that
you're
working
on
it
internally
to
understand.
You
know
how
we
could
do
this
in
a
privacy-minded
way,
maybe
a
light
explanation
of
the
technical
components
you
know
so
that
people
understand
that
we're
not
sharing
data
with
a
third
party
that
sort
of
thing
as
early
as
you
can
post
something
like
that,
even
if
you're
not
working
on
gitlab.com
but
set
the
stage.
F
That's
you
know
if
you
kind
of
Envision
a
a
series
of
blog
posts,
this
would
be
number
one
set
the
stage
then,
when
you're
thinking
about
going
how
we
can
apply
to
github.com
before
you
start
work
another
one,
then
we'll
start.
You
know
what
I
mean
until
your
final
and
I
think
that
that
would
be
a
nice
thing
to
refer
to
in
the
FAQ
as
well
as
any.
If
we
have
to
do
any
Communications
in
the
future.
F
A
C
A
Definitely
with
the
internal
handbook,
since
it's
covering
it's
instantly
going
to
affect
GitHub
team
members,
we
want
to
just
go
make
sure
that
we
have
a
slack
announcement
and
an
issue
to
collect
feedback
for
internal
stakeholders
for
now
and
then
I
think
after
that
would
make
sense
to
kind
of
do
like
that.
That
part
one
of
saying
hey.
A
This
is
what
we're
trying
to
do
and
here's
what
we've
done
with
the
internal
beginnings
of
like
what
we're
trying
to
do
with
the
internal
handbook
and
then,
where
we
plan
to
go
with
that,
so
that
people
are
aware
that
we're
we're
continuing
to
pursue
this
and
and
apply
it
externally
as
well.
So
I
think
that's
a
good
idea.
A
B
How
do
I
apply
to
my
own
use
cases
is
a
separate
topic
from
how
do
we
dog
food,
it
I
think
putting
content
together
about
this
is
what
product
analytics
is
how
we
envision
you
as
a
customer
will
use
it
yourself
is
relatively
straightforward:
a
lot
of
the
open
questions
we
got
when
we
started
with
the
initial
blog
draft
related
to
how
does
dog
fooding
it
at
gitlab
with
gitlab.com?
B
B
How
I
would
see
this
going
is
we
could
do
a
blog
post
about
we're
doing
this
internally
on
the
internal
handbook?
This
is
our
broad
sort
of
product
vision
for
how
we
envision
you
using
it
in
the
future.
B
Get
some
Community
involvement
I'm
going
to
be
talking
about
this
at
the
customer,
Advisory
Board
here
in
a
couple
weeks
and
then
as
a
follow-on
Blog
in
the
future.
Once
we
figure
out
all
those
legal
answers,
then
we
start
talking
about
our
dog
food
and
plans
once
we
have
a
little
bit
more
firm
idea
on
how
we're
going
to
do
that
correctly.
F
Sam
I
wonder
if
you
could
even
use
that
blog
post
as
an
invitation
for
people
to
give
feedback
on
hey.
Do
you
wanna?
Do
you
want
to
be
part
of
our
pilot,
or
do
you
want
to
talk
to
us
about
how
you
might
implement
this
in
your
kind
of
like
customer
interviews?
I
know
you've
done
a
lot
of
those
already,
but
could
be
another
angle
where
we're
inviting
the
community
to
build
with
us,
or
you
know,
collaborate
with
us
yeah.
B
Yeah,
no,
it's
a
good
point.
Certainly
once
we
get
further
along
I
want
us
to
do
something
around
either
an
alpha
or
a
closed
beta,
and
that
does
seem
like
a
really
good
way
to
get
those
folks
involved.
B
A
I
apologize,
I'm,
taking
notes,
Sam.
Why
don't
you
jump
to
your
point
and
I'll
finish
up
the
product
intelligence,
okay,
you're,
doing
that
all
right,
all
right,
I'm
gonna
go
ahead
and
jump
to
product
intelligence,
then
I
do
have
a
couple.
Well,
I!
Guess,
one
of
the
things
sorry,
a
couple
things
for
product
intelligence
I
was
looking
for.
A
Was
that
I
needed
a
volunteers
for
the
triage
schedule,
so
we've
already
we're
in
unknown
territory
for
the
for
the
week
of
October
3rd
and
onwards,
we
don't
have
any
triage
scheduled
volunteers
yet
so
this
is
just
an
open
call
out
too
all
group
members
there
there's
an
MR
there
to
extend
that
calendar.
A
So
please
add
yourself
to
at
least
one
of
those
thoughts
and
I
would
greatly
appreciate
that
I
also
had
something
similar
for
the
service
ping
manual
Generation
for
those
that
aren't
aware
of
the
service
ping
that
we
generate
is
done
manually
with
production
rails,
console
access.
So
this
is
something
that
we
only
have
a
few
people
that
are
able
to
do
in
the
group
and
I
I.
A
Wasn't
aware
of
that
actually,
and
what
I
also
wasn't
aware
of
is
that
we
have
a
plan
to
automate
that
within
the
data
warehouse-
and
so
that's
that's
great-
to
hear
any
manual
processes
that
we
have
to
do,
especially
when
they
take
24
plus
hours
to
do,
there's,
definitely
not
an
efficient
use
of
our
our
our
time.
So
I'm
glad
to
hear
that's
being
addressed.
A
That
said,
after
getting
all
the
contacts
from
all
the
product
intelligence
team
members,
I'm
gonna
say,
let's
just
hold
off
on
granting
any
more
production
access
to
any
of
the
team
members,
especially
since
not
all
of
it
not
everyone's
familiar
with
the
process
itself.
So
all
that
to
say
is
I
think
the
data
team
is
expecting
by
the
end
of
the
month
to
be
able
to
have
this
automated
process
complete.
And
so,
if
that's
the
case,
then
I
think
we're
good.
A
Then
we
can
remove
all
that
access
if
we
no
longer
require
production
and
access
for
anything
other
than
service
ping
generation,
and
then
that
will
actually
make
things
easier
in
terms
of
yeah
any
any
interactions
with
infrastructure.
As
far
as
granting
access
and
things
like
that,
yeah
that's
pretty
much
it
Amanda.
You
have
a
point
here
which
I
can
type.
F
Yeah,
like
the
vocalize,
no,
it's
okay,
just
a
gentle
FYI
that
automation
has
been
complete
since
May
and
the
target
date
of
it
going
live
has
continually
rolled
three
months
in
a
row,
so
there
is
definitely
a
possibility
that
it
doesn't
hit
at
the
end
of
October.
F
A
For
sure
yeah
I
remember
that
comment:
I
was
just
thinking
in
terms
of
okay.
A
If
I
open
up
two
or
three
more
access
requests
and
say,
go
to
go
to
infrastructure
and
say:
hey
can
we
grab
more
and
they
have
the
the
and
then
we
look
at
Israel's
comments
where
it's
like
the
top
priority
for
the
smallest,
no,
no
I'm
sure
it
was
also
the
top
priority
for
the
previous
Milestones
too,
but
yeah
I
mean
if
anything,
it
would
be
just
a
stronger
case
for
us
to
then
extend
the
access
to
the
rest
of
our
group
members
until
they
are
able
to
have
more
confidence
in
terms
of
when
they
can
actually
complete
the
automation,
so
I
guess
yeah.
A
A
No,
it's
worth
noting
it's
worth
noting,
but
yeah,
no
we'll
we'll
see
what
happens
this
month
and
then
we'll
go
from
there
cool
Sam.
You
have
the
next
point.
Unless
anyone
had
any
questions,
sorry
I
didn't
pause,
cool
Sam.
B
Thanks
so
I
just
wanted
to
signal
boost
I
am
working
on
hiring
a
new
product
manager
for
the
the
product
intelligence
group
as
Amanda
transitions
to
her
new
group.
If
any
of
you
all
have
folks
in
your
network,
you
think
would
be
a
good
fit.
Please
share
their
information
with
me,
as
well
as
the
role
with
them,
so
that
we
can,
you
know,
get
someone
in
that.
That's
really
going
to
do
a
great
job
and
I'll
also
point
out.
We
do
have
a
referral
incentive.
B
So
if
you
do
find
someone
that
we
end
up
hiring,
there's
some
some
bonus
in
it
for
you
personally
as
well.
So
so
why
don't
the
signal
boost
that
then.
A
I
respect
you,
yes,
and
to
piggyback
off
of
that,
as
I
had
mentioned
before,
we
are
hiring
still
for
both
groups,
product
analytics
and
product
intelligence.
So
we
are
still
looking
for
two
back-end
Engineers
for
product
analytics,
one
back
in
engineer
for
product
intelligence
and,
of
course,
as
I
mentioned
earlier.
Just
this
morning,
meeting
one
front-end
engineer
for
product
intelligence
and,
like
Sam
had
mentioned,
we
do
have
that
referral
incentive
and,
as
we
had
discussed
actually
in
the
product
intelligence,
sync,
please
consult
the
compensation
calculator.
A
We
do
have
a
page
where
we
can
indicate
which
countries
we
are
able
to
hire
for
from
and
which
that
we
aren't
due
to
a
variety
of
legal
reasons,
and
things
like
that.
So
please,
you
know,
as
you
submit
referrals,
just
double
check
that
just
so
we're
being
efficient
with
our
candidates
times
Tim.
You
have
some
comments
here.
Would
you
like
to
vocalize?
A
C
So
if
you
have
referrals,
as
already
said,
they
are
more
than
welcome,
and
but
please
also
let
us
as
hiring
managers
know
additionally.
So
because
then
we
are
always
looking
that
we
get
them
checked
out
ASAP,
because
sometimes
there's
in
Greenhouse,
you
can't
filter
by
referrals
or
anything
they
get
lost
so
easily.
C
The
other
thing
is
I
have
also
around
800
applicants
in
another
part
in
two
other
pipelines
for
front-end
engineers
and
plan
at
the
moment,
so
I'm
trying
to
get
also
through
them,
with
the
hiring
managers
there
and
try
to
see
if
we
have
some
super
candidates.
That
would
be
perfect,
fits
also
for
either
product
intelligence
or
product
analytics
to
some
extent.
And
then
we
will
also
guide
them
over
here.
So
no.
E
Well,
yeah,
just
for
all
of
those
roles,
including
the
PM
ones
as
well,
if
we
can
get
links
to
the
full
job
adverts.
So
we
know
that
the
people
we're
referring
are
exactly
what
we're.
Looking
for.
Just
because
I've
made
referrals
in
the
past
that
were
rejected
for
not
you
know,
matching
a
particular
criteria,
but
what
otherwise,
potentially
strong
candidates
for
other
teams.
A
A
I
do
want
to
tweak
the
backend
engineering
one
for
product
analytics
a
little
bit,
but
they
should
be
mostly
up
to
date.
That
said,
if
anyone
would
like
to
help
out
with
you
know,
application
review
and
things
like
that
we
can
potentially
get
that
going.
I
could
definitely
use
some
help.
There,
there's
I
guess
as
a
kind
of
call
out
to
what
I'm
going
to
be
focusing
on
for
the
next
two
weeks
is
primarily
getting
the
stack
set
up
and
answering
any
questions.
A
Infrastructure
has
just
so
we
can
get
into
the
internal
handbook
collecting
data,
so
they
can
actually
start
building
the
dashboards
around
it.
So
hiring
is
still
a
top
priority
of
mine,
but
you
know
if
anyone
wants
to
help
out
with
that,
I
can
definitely
use
it.
A
C
C
Needed,
let
me
know
happy
to
carry
it
through
and
push
wherever
needed.
A
I
think
we're
in
a
we're
in
a
good
spot,
so
we're
very
close
and
I'll
keep
pushing
for
mine
as
well.
So
thanks
for
the
support
everyone,
if
anyone
has
any
questions
or
feedback,
let
us
know
otherwise.
Yeah
enjoy
the
rest
of
your
Mondays
and
have
a
good
week
and
we'll
see
everyone
next
time.