►
From YouTube: Product Analytics 15.7 frontend group kickoff
Description
In this call we discuss the frontend work we have planned for 15.7
A
Oh
yeah,
so
a
basically
what
Gianna
already
said
here
on
the
on
the
notes.
Basically,
the
main
objective
is
to
deploy
internal
preview
with
internal
Outlook
handle
to
collect
data,
and
this
is
what
we
have
been
chasing
as
the
main
objective
things
thing
we
have
started
as
a
group
and
also
the
onboarding
workflow.
A
That's
something
that
I'm
pretty
interesting
with,
and
the
other
thing
is
implementing
the
schema
to
show
our
first
widget
on
the
on
the
dashboard
so
and
in
the
priority
set
features
a
we
have
the
cube,
rendering
with
the
first
one
that
you
can
work
on
and
I
mean.
That's
that's
pretty
pretty
much
done
if
I,
because
we
have,
we
have
a
immersion
Mark
already
so
I
know.
If
the
end
you
want
to
yeah.
B
A
C
C
It
would
be
okay
to
begin
working
on
them
yeah
after
the
initial
review
is
completed,
I
would
say
once
it
goes
into
maintainer.
That's
when
you
can
start
beginning,
but
you
I
wouldn't
put
anything
out
there.
You
know
for
review
until
yarn's
work
is
in
because
we
are
adding
a
new
package
to
the
JS
to
yeah
up
there
to
yarn
yeah.
A
C
A
So
ready
for
development,
we
have
the,
and
this
is
a
vacuum
issue,
so
I
should
have
filtered
this
right.
Now
we
are
working
on
what
we
just
mentioned
about
this
line.
Chart
we
and
after
we
get
this
first
round
of
previews,
we
can
unblock
the
rest,
another
back-end
task,
but
this
is
pretty
much
related
to
to
our
responsibilities.
C
A
A
Yes
and
in
review
the
the
team,
it
seems
the
only
front-end
related
one
is
the
a
follow-up
to
other
the
link
to
the
product,
analytic
documentation,
I
added
this
section
regarding
the
regarding
the
how
to
enable
the
settings
and
I
put
a
screenshot
here
so
yeah
this
has
been
reviewed.
Let's
hopefully,
hopefully
we
get
a
quick
turnaround
time
here
and
we
already-
we
already
went
through
this
on
the
Retro,
but
we
close
a
pretty
good
deal
of
of
enabling
features
for
for
this
Milestone.
B
B
B
That's
blocking
for
the
rest
and
the
response
from
Sam
was
that
the
expectation
is
that
we
prioritize
the
planning,
and
so
we
can
start
with
the
development
ASAP-
and
you
know
by
extension,
hopefully
get
it
done
during
this
master,
which
I
think
is
Fair,
considering
our
capacity
and
the
amount
of
work.
So,
let's
give
it
a
shot,
see
see
what
we
can
do
and
then
rob
you
have
a
responsor
there.
C
Are
we?
My
question
is:
are
we
happy
just
for
me
to
write
the
implementation
plans
for
the
view
app
and
the
loading
without
the
state
machine?
That's
been
discussed
if
the
mutation
that
you
say
your
brain's
not
working
on
if
Matt
the
mutation
Max
is
working
on,
is
coded
and
deployed
and
we
get
the
Jitsu
key
added
to
the
projects
graphql
endpoint.
B
C
I'm
happy
with
that
approach.
I
can
write
those
implementation
posts
this
afternoon,
so
we
can
actually
start
assigning
these
two
tasks
and
get
work
going.
I
can
always
do
the
back
end
aspects
as
well,
so
the
Jitsu
key
stuff
and
we're
definitely
going
to
need
that
state
machine.
Before
we
start
doing
the
next
phase
of
customer
facing
where
we
start
wanting
more
details
and
stacked
information
and
stuff.
Definitely.
A
C
Yeah
I
have
pinged
you
both
from
the
issue.
Sam's
responded,
preferring
option
three,
but
I
have
finally
got
those
designs
done
to
get
the
user
to
come
back
to
the
tracking
setup
guide.
Afterwards
after
they've,
you
know
completed
and
implemented
their
tracking
details
and
actually
got
some
dashboards
showing
up.
So
this
is
where
contentious
point
that
Sam
said
needed
to
be
done
for
this
MVC.
However,
we
can't
actually
do
it
the
whole
linking
back
until
we've
completed
the
tracking
view.
C
So
it's
an
end
of
the
end
of
the
MVC
piece
of
work
to
be
have
completed.
Sam's
feel
free
to
take
a
look
async
and
respond
in
that
your
preferences,
Sam
as
I
said,
has
Preferred
option.
Three
is
a
separate
page
rather
than
a
modal,
which
I
kind
of
agree
with.
But
if
there's
any
other
suggestions
you
guys
have
or
want
me
to
scope
out
and
have
a
play
with,
let
me
know.
B
After
the
next
one,
I
just
wanted
to
quickly
discuss,
because
that's
usually
part
of
our
kickoff
is
just
eyeing
who
wants
to
take
on
some
of
these
open
issues,
since
no
one
is
assigned
just
yet
it
doesn't
have
to
be.
You
know
concrete,
but
Axel.
It
seems
like
you're
you're
interested
in
taking
at
least
one
on.
A
Yeah
yeah
totally
I'm
interested
in
this
the
thing
of
that
one,
not
because
it
is
easier.
It's
just
that
it.
It
deals
with
a
few
Concepts
that
I
work
on
on
the
on
the
PLC,
that's
basically
with
discount
and
and
how
do
they
work
and
and
yeah
so
I
might?
If,
if
you
guys
agree,
I
might
take
over
cheap
over
this,
so
so
I
could
I
could
push
it.
Forward
I
believe
that
that
was
the
the
let's
say.
The
objective
of
yeah.
B
Why
I
just
decided
I'll
provisionally
assign
myself
then
as
a
dri
for
the
table?
But
if
you
finish,
if
you
find
yourself
finishing
quickly
or
whatever
we
can
always
and
you're,
also
interested
in
doing
the
table,
we
can
also
just
swap
I
think
it
just
helps
for
the
rest
of
the
group.
If
all
the
issues
have
a
assigned
dri.
So
that's
yeah,
there's
someone
to
to
to
to
Ping.
Instead
of
pinging
the
entire
group
on
like
open
issues.
C
B
C
A
Yeah
yeah,
so
I
have
a
I,
have
an
X
Point
I
put
this
here
because,
basically
to
talk
about
the
onboarding
flow
NBC
like
what's
the
and-
and
this
is
maybe
maybe
a
question
for
raw
like
what's-
is
if
there's
something
we
can,
we
can
start
working
on
right
now
and
I
know.
That's
that's
a
pretty
general
question,
but
I
run
through
it
and
I
saw
mostly
like
ongoing
discussions
instead
of
of
a
decision,
so
so
yeah
I
just
wanted
to
ask
you
what
what
do
you
think.
C
B
A
A
C
A
A
C
A
Yes,
yes,
and
so
just
mentioning
it
so
because
they
don't
appear
on
our
regular
board,
because
they
don't
have
a
milestone
and
we
might
be
overlooking
something
drugs
I
I
was
I
was
that's
what
I
mentioned
it,
because
when
I
was
When,
I
Was
preparing
for
this
Milestone
I
I
was
like.
Where
are
those
issues
that
I
created?
Where
I
I
remember
this
issue
like
this,
and
then
it
was
because
they
they
don't
have
a
milestone
so
yeah
just
to
keep
an
eye
on
them.
C
So
there's
two
points
here:
one
would
be
to
check
to
see
whether
issues
should
be
in
the
epics
they're
in
yes,
the
second
would
be
a
lot
of
you.
We
in
compliance,
we
had
the
concept
of
next
UPS,
which
are
issues
which
are
what
we're
going
to
be
working
on
next,
and
you
can
infer
that
every
issue
in
front
of
analytics
is
something
we're
going
to
be
working
on
next,
because
we
we
have
nothing
so
we're
we're
sort
of
doing
everything
at
once.
C
So
you
can
even
so
any
issue
about
a
milestone,
isn't
necessarily
a
bad
thing,
but
you
could
take
it
on
as
an
idea
of
has
it
been
assigned
to
to
the
right
epic.
What
epic
are
we
working
on
next?
Maybe
I
should
start
contributing
and
working
towards
an
issue
that
I
can
contribute
to
in
an
epic
that
we're
going
to
be
doing
next,
so
we
know
we're
doing
internal
preview.
Has
every
internal
preview
issued
being
handled
then?
Move
on
to
the
customer
facing
obesity
is
a
second.
A
C
A
C
C
And
yourself
yeah,
which
you
can
import
into
your
Chrome
instance
that
will
give
you
direct
links
to
be
able
to
copy
the
headings
for
those
different
sections
if
you'd
like
it,
just
provides
context
to
the
user
to
the
person
seeing
your
review,
what
you
mean
when
you're
putting
these
comments
in,
are
they
actual
blockers
or
not
so
something
to
look
at
on
my
next
Point
and
something
I've
already
raised?
I,
don't
know
what
ux
looks
like
this
Milestone.
C
A
B
A
great
well
yeah,
I'm
I'm,
pretty
much
100,
but
that's
just
to
say
that's
the
pings
and
the
split
range
should
should
stop.
There's
no
active
feature
that
I'm
working
on
I've
finished
off
all
my
future
work.
The
last
thing
that
I'm
helping
out
is
just
general
questions
that
people
have
and
the
odd
review
every
now
and
then.
B
Good
news
is
that
a
new
senior
front-end
engineer
will
be
coming
on
board
I
think
next
week
for
them
and
I'll
be
the
onboarding
buddy.
So
that
will
take
a
bit
of
my
time,
but
once
that's
done
then,
hopefully
I
can
yeah
leave
them
to
enjoy
their
new
space
and
new
team
and
I
mean
they're
a
new
stages
like
new
everything,
but
I
think
it's
going
to
be
good.