►
From YouTube: 2022-11-22 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
Shift
C,
hello,
everyone
and
welcome
to
the
November
22nd
edition
of
the
product
analytics
weekly
sync.
Unless
there
are
any
volunteers,
I
can
go
ahead
and
load
up
the
build
board
and
we
can
go
take
a
look
at
that
all
right,
then
I
will
take
it
this
week.
Let
me
share
my
screen
and
let
me
stop
my
window
manager
from
moving
everything
everywhere.
I
apologize-
and
here
we
go
all
right.
So
we've
got
the
Milestone
planning
issue,
which
has
got
a
separate
item
for
which
we
could
take
a
look
at
later
on.
A
We've
also
got
three
other
items
that
are
open
for
this
Milestone,
adding
a
Jitsu
key
to
project
graphql
type.
Is
there
anything
we
need
to
do
here
as
far
as
validating
the
solution
here.
B
I
was
just
confirming
with
Max
on
the
whether
we
should
be
taking
this
approach,
considering
what
we're
planning
on
doing
in
future.
But
he
confirmed
that
this
is
the
right
approach
to
take.
So
I
just
need
to
move
that
into
get
the
implementation
plan
validated
and
then
move
it
into
ready
for
development.
C
Yeah
the
implementation
plan
looks
fine.
Are
you
happy
to
take
it
because
I
signed
here
or
do
you
want
to
assign
it
to
me.
B
A
Okay,
look
cool
all
right,
then
we'll
move
on
and
we've
also
got
the
single
stat
and
table
Cube
query
running
widgets.
Excuse
me.
These
are
blocked
by
the
work
that
John's
already
doing
on
the
line
chart.
So
we
can
just
check
that
over
there
for
blocked
issues.
That's
still
waiting
on
the
production
review,
which
I
have
a
couple
of
responses
from
a
couple
different
interested
parties,
but
generally
looks
like
we're.
A
Okay,
we've
got
some
just
like
kind
of
to-do's
we
want
to
get
to
towards
as
we
get
to
external
users,
but
I.
Think
from
what
I've
read
so
far
that
the
internal
previews
shouldn't
be
blocked
by
this.
So
I'm
just
going
to
answer
those
questions
and
get
that
organized
we've
got
onboarding
the
API
to
retrieve
the
state
of
the
product
analytics
stack
Max.
Is
there
anything
you
want
to
call
out
here.
C
A
D
Some
good
news-
it's
unblocked
by
and
thanks
so
much
to
Rob,
for
helping
me
investigate
all
the
crazy
stuff
there
and
also
creating
Mr
to
fix
the
issues
with
qproxy
and
I.
Finally
got
some
Focus
time
to
sit
down
so
I'll
have
something
later
on
in
original,
I
have
a
channel
item
to
demo
the
work
that
I've
done
there,
but
it's
basically
done
and
hopefully
fingers
crossed
by
the
end
of
the
day.
I
can
create
my
Mr
and
get
it
into
the
initial
review.
A
C
Else
to
add
yeah,
it's
recording
demo,
no,
nothing,
nothing!
To
add!
Sorry!
It's
ready
to
go!
Rob's
done
a
first
pass,
a
review,
so
I'm
gonna,
look
at
that,
probably
this
afternoon
or
tomorrow
morning,
but
yeah.
It's
looking
good
it's
later
in
the
agenda,
but
there's
a
link
to
and
until
the
video
where
I
show
it
working
as
well.
For
those
interested.
A
E
Yeah
so
I
just
committed
a
proposal
for
a
new
section
on
the
documentation.
Now
you
share
a
link,
so
so
you
can
take
a
look
at
that
and
hopefully,
hopefully,
I'm
hoping
for
for
a
quick
turnaround
time
here
on
the
after
the
after
the
technical
writing
approval.
C
Yeah,
so
this
is
a
couple
literally
just
said:
this
is
to
merge
when
the
pipeline
succeeds.
So
this
will
allow
access
to
all
of
the
information
about
dashboards
and
their
widgets
and
visualizations
biographical
API.
So,
assuming
that
the
merge
succeeds,
I'll
move
it
into
verification
before
I
sign
off
today.
A
Very
cool
and
then,
as
mentioned
I'm,
currently
working
oops.
Excuse
me
with
John
Jarvis
on
answering
a
couple
different
questions.
So
we've
got
some
very
fun
long
form
things
going
on
with
the
Readiness
review.
Just
answering
a
bunch
of
different
questions
here,
but
I'm
working
on
answering
those
playing
a
little
ping
pong
here,
but
definitely
interesting
if
you're
curious
about
all
the
inner
workings
for
getting
this
productionized,
but
definitely
getting
a
lot
of
support
from
infrastructure.
A
So
I'm
definitely
appreciative
of
that
I'm
hoping
to
get
that
sorted
this
week,
cool
and
then
our
bookmark
was
moving.
The
cube
API
proxy
feature
to
EE.
So
then,
as
far
as
what's
been
merged
and
we've
got
finally
the
version,
one
of
our
user
dashboard
schema
version.
That's
huge
news
great
to
see
max
anything.
You
want
to
add
to
that.
C
Yeah
so
it's
you
know,
we've
got
a
solid
version
of
something
to
aim
for
I'm,
expecting
it
to
change,
but
we've
agreed
at
least
it's
something
that
we
can
get
started
on
and
make
assumptions
based
on
and
no
so
far
no
one
has
turned
around
and
gone.
Oh,
my
goodness.
We've
completely
done
this
wrong.
So
that's
a
good
sign
as
far
as
I'm
concerned,
bearing
in
mind
we're
not
public,
we
can
make
changes
to
version
one
and
it's
not
really
considered
a
breaking
change
either.
A
A
You
might
have
seen
as
well
there's
the
working
group
for
dashboard.
So
you
know
once
we
get
the
nomenclature
finalizer.
Maybe
some
changes
there
just
so
that
we're
consistent
from
from
the
very
beginning.
A
B
We've
just
got
closed
because
it
got
converted
to
an
epic
but
I
in
general.
The
designs
faded
that
is
done.
B
We've
just
got
an
additional
view
that
we're
discussing
right
now,
which
I
finally
got
into
designed
this
morning
sounds
good
though
so
we
should
be
nearly
all
wrapped
up.
We
I
just
need
I've
got
two
issues
that
I
need
to
do
the
implementation
plans
for
after
this
meeting,
and
then
we
can
put
everything
into
ready
for
development.
Awesome.
A
Very
cool,
then.
Second,
we
have
the
loading
state
for
customizable
dashboards.
Anything
we
want
to
add
here
excellent
yeah.
E
D
Yeah
so
yeah,
this
was
solved
by
the
introduction
of
the
concept
of
visualizations,
which
is
a
bit
of
a
change
from
I
guess
the
language
where
it
was
dashboards
with
separate
widgets.
Now
widgets
are
kind
of
the
thing
that
is
baked
into
a
dashboard,
and
the
visualization
is
the
thing
that
can
be
shared
in
separate,
so
different
names,
but
accomplishing
the
same
thing.
D
This
is
also
well.
This
is
also
done
by
the
fact
that
the
V1
schema
is
a
merchant
done,
and
then
this
also
applies
into
Max's
work.
That
is
in
verification
to
get
all
the
details
via
graphql,
although
that's
not
needed
for
the
internal
preview,
because
currently
the
use
the
reusable
visualizations
is
part
of
the
baked
in
dashboard
configurations
that
we
have.
D
A
And
that
wraps
up
our
Board
review,
then
I
would
have
saved
this
bookmark.
Excuse
me
and
then
stop
that
find
my
tab
again
and
then
we
can
carry
on.
A
The
next
one
we're
already
a
few
days
into
the
Milestone
we've
I've
pinged
everyone
on
the
Milestone
planning
issue
itself.
We
have
a
follow-up
point
after
this
to
talk
about
capacity,
but
Sam
Sam
and
I
had
already
kind
of
determined
the
themes
for
the
Milestone.
The
timing
doesn't
work
out
because
of
the
long
weekend
and
everything,
but
definitely
take
a
look
at
it,
see
if
it
makes
sense
and
see.
If
there's
anything,
we
can
do
to
help
get
that
better
organized
for
everyone.
A
As
always,
if
there's
any
questions,
please
reach
out
to
Sam
Timmer
myself,
so
we
can
help
clarify
or
address
any
feedback
or
concerns
on
the
topic
of
Milestone
planning.
Two
something
I
had
forgotten
previously.
In
my
other
teams
we
had
actually
hit
in
the
dates
we
were
going
to
be
unavailable,
so
I
just
wanted
to
pull
the
room
for
capacity
planning
purposes.
If
anyone
had
any
opinions
on
that,
so
right
now,
I
just
called
up
the
days
that
I
wouldn't
be
available.
A
But
if
anyone's
not
comfortable
with
that,
we
can
always
switch
over
to
more
of
a
I'm
just
not
going
to
be
available
for
a
percentage
of
the
the
milestone.
D
I'll
voice
over
my
points,
I
feel
like
my
default,
is
to
go
to
Black,
hidden
and
not
have
the
days
available,
especially
since
we
usually
also
don't
do
that
on
our
gitlab
statuses,
anymore,
yeah
and
I
know
in
like
a
previous
group,
and
some
people
only
afterwards
voiced
that
it
was
like
a
concern
for
them
that
we
were
like
posting
it
publicly.
D
C
C
No
say
I
I
agree.
My
address
is
public
for
anyone
clever
enough
to
figure
it
out
and
various
who
is
databases,
so
knowing
what
I'm
not
around
is
always
a
concern.
A
Sounds
good,
then,
we'll
swap
everything
over
to
the
percentage
base.
So
then,
based
on
that
as
an
example,
if
you're
out
for
two
days,
given
that
there's
two
or
sorry
20
working
days
and
we
give
a
milestone
more
or
less
each
day,
chalks
up
to
about
five
percent
of
availability.
So
any
any
day
you
take
that
off
just
list
your
total
availability
for
that,
and
then
we
can
use
that
going
forward.
Plan
against
capacity
can.
A
Sorry,
let
me
just
add:
I
was
trying
to
pull
the
shared
calendar
notes
from
the
section
meeting
Dennis
to
to
planning
template.
F
A
And
then,
lastly,
I
just
created
a
shared
calendar
for
everyone
for
the
entire
section.
So
hopefully
we
can
add
all
the
meetings
there.
I
did
add
Milestone
kind
of
Milestone,
Milestones
or
Milestone
key
dates
as
far
as
like
when
when
things
should
be
happening,
given
the
product
development
flow,
but
I've
also
added
like
the
planning
meetings
for
Sam
and
myself
that
everyone
else
is
invited
for
product
analytics
if
anyone's
Keen,
to
join
that.
Hopefully
we
can
get
the
product
intelligence
group
events
out
of
there
as
well
and
then
yeah.
A
If
you've
got
PTO
instead
of
trying
to
send
it
to
everyone,
you
can
always
just
add
it
to
the
shared
calendar
and
everyone
will
be
able
to
see
it,
but
just
another
thing
to
keep
us
a
little
bit
more
organized.
But
if
there's
nothing
else,
that's
pretty
much
the
end
of
the
housekeeping
section.
We
can
move
on
to
the
good
stuff,
which
is
show
and
tell
Tim.
You've
got
the
first
point.
G
Me
cool
I
made
a
little
bit
of
progress
as
it's
such
a
quiet
nice
week
with
Thanksgiving,
so
I'm
happy
to
share
if
I'm
capable
of
finding
that
window.
G
Let
me
see
it's
the
bestest
word
Because.
By
the
way,
I
ran
again
into
the
problem
where
Cube
says
no
it,
so
they
have
locked
me
out
again,
so
my
local
Cube
instance
doesn't
take
any
requests
anymore
when
I'm
locked
in
with
my
normal
browser.
As
soon
as
I
go
Incognito,
it
works
again.
So
there
seems
to
be
something
weird
with
some
sort
of
security
or
a
cookie
tool,
something
or
I'm
doing
too
many
requests.
It
gets
annoyed
by
me,
so
I
need
to
get
basically
become
a
phantom
to
it.
G
Good
I
was
looking
again
at
the
query
designer
that
I
showed
you
already
last
week
and
by
now
we
can
do
actually
a
couple
of
more
things
so
bear
with
me.
This
is
not
rebased
yet
as
I'm
always
afraid
to
rebase
with
some
updates.
So
this
is
not
using
yet
the
visualization
stuff,
but
that
will
be
really
the
next
step
to
update
against
Jan's
latest
updates
and
then
basically
provide
and
create
the
actual
format
that
we
have.
G
I
cleaned
it
up
a
little
bit
so
that
it
looks
nicer
and
we
can
actually
already
use
the
page
views.
We
can
say
Okay
I
want
to
measure
all
the
page
views
I
want
to
go
ahead
and
want
to
get
the
insights
on
page
views
either
Group
by
a
certain
time
frame.
So
you
can
also
say,
for
example,
I
want
to
have
them
grouped
by
by
week.
You
can
then
display
them
on
a
line
chart
really
just
by
on
a
weekly
basis,
for
example,
and
we're
already
providing
the
query
that.
F
G
In
this
version
can
then
take
and
copy
over
I
will
already
convert
it
to
yaml
so
that
we
don't
need
to
convert
that
part.
But
the
reality
is
that,
hopefully,
as
soon
as
we
have
the
functionality
to
edit
dashboards,
we
can
hit
add
to
dashboard
and
simply
take
this
over
basically
to
the
dashboard
that
we
are
currently
on
or
a
specific
dashboard.
Etc.
G
So
the
idea
is
really
simply
that
we
basically
go
step
by
step
through
first
the
measurements
and
then
the
dimensions
so
that
you
can
have
a
very
clear
with
out,
basically
hiding
all
those
funky
field,
names
and
and
in
the
tables
that
we
have
and
what
you
can
do.
So
you
can
say
Okay
I
want
to
have
basically
urls.
G
G
What
also
already
works-
and
this
is
so
nice
that
Cube
provides
us.
That
stuff
is
that
we
can,
for
example,
use
multiple
Dimensions.
So
here
it
is
a
pivot
against
multiple
dimensions
of
chrome
and
the
version
of
the
browser,
and
that
is
also
something
that
we
can.
Then
support
by
adding
multiple
Dimensions
here,
it's
the
predefined
thing
is
basically
adding
already
two
of
them
at
the
same
time.
G
What
else
can
we
do
everything
that
has
n
a
in
Brackets
doesn't
work
yet
because
we
don't
need
the
data
and
that's
what
I'm
currently
targeting
it
is
to
figure
out
what
data
we
need
to
and
how
we
need
to
collect
data
or
transform
data
that
we
can
then
provide
at
a
later
point
also,
the
statistics
that
same
already
started
to
define
the
ideas
that
we
can
build.
Almost
everything
that
we
defined
there
already
through
the
query,
Builder
and
then
simply
do
the
editing
process
and
do
this
manually.
G
In
this
phase
we
can
measure
against
the
viewport,
but
what
we
can
do
also
on
top
of
that
is
already
filtering.
So
if
we
say
okay,
we
want
to
see
the
page
path.
I
can
add
now
another
filter
and
say:
okay
I
want
to
have
the
page
path
should
be
contained.
G
That
is
basically
adding
the
filter.
So
now
we
see
that
all
the
only
the
URLs
are
ending
up
in
the
charts
that
have
slash
handbook,
slash.
D
G
G
G
It
is
yep,
so
we
can
go
back
and
say
we
want
to
have
have
all
the
page
paths
and
we
only
want
to
have
the
ones
that
equal,
basically,
the
internal
handbook,
so
that
we
only
get
the
handbook
stuff
and
not
localhost,
Etc
and
so
on
and
yeah.
And
that
again
provides
us
then
already
with
the
query
that
can
then
could
take
and
copy
over.
G
And
we
support
already
specific
time
ranges
so
that
we
can
only
filter
to
the
time
range
that
we
want
to
see
so
that
we
can
say
Okay
a
specific
month
for
last
90
days,
so
that
we
can
have
different
ones
or
we
get
the
one
that
is
basically
defined
in
the
dashboard
and
yeah.
That's
where
I
am
at
the
moment
with
my
little
hobby
project.
So
any
questions.
H
G
C
The
queries
that
you're
running
against
Cuba
they're
using
the
direct
Cube
API,
are
they
using
our
proxy.
G
They
are
all
using
our
proxy,
but
I
extended
our
proxy
by
the
meter
endpoint
and
the
dry
run
endpoint.
So
the
Mr
already
contains
the
extension
of
the
proxy,
not
only
the
slash
load,
endpoints
but
already
use
the
proxy.
So
this
is
fully
using
both
the
proxy
endpoints,
but
also
already
the
previous
version
of
the
line
chart
that
we
have,
for
example.
G
So
let's
go
back
here
and
say
page
view
very
cool
which
is
classic
no
I
want
to
have
by
day.
Then
we
basically
see
here
all
the
page
views
that
we
have
counted
over
the
specific
days
over
that
time,
branch
and
so
on,
but
yeah.
G
E
A
Couple
of
topics
that
have
to
be
unraveled
there,
but
no
looks
great
thanks
Tim
for
the
demo,
all
right,
Max
you've
got
the
next
one.
C
A
short-ish
of
time,
a
month,
sort
of
basic
anyway,
so
I've
created
the
first
craft,
doing
an
R
to
create
the
product
analytics
stack
for
a
project
via
graphical
mutation,
I've
recorded
a
demo
of
it
there
so
go
and
check
it
out.
Let
me
know
if
you've
got
any
questions.
D
Yeah,
let
me
quickly
share
I'll,
unfortunately,
have
to
share
my
entire
desktop,
so
I'll
zoom
in
as
much
as
possible,
but
this
is
the
boring
part
of
what
I
did.
So.
These
are
the
two
line
charts.
It
may
look
strange
that
there's
two
copies,
that's
explicitly
so
so
that
I
can
test
that
the
reusability
of
it
works.
The
interesting
part
of
what
I
did
and
what
I
quickly
want
to
show,
especially
to
the
engineers
in
this
Hall,
is
the
the
architecture
part
of
it.
D
So
this
should
slot
very
nicely
in
with
what
Tim
just
came
out
in
terms
of
that
output
for
the
visualization
and
also
the
work
that
maxed
it
in
terms
of
getting
that
visualization
from
graphql.
So
what
we
have
here
is
a
completely
reusable
and
I've
completely
forgot
the
word
but
agnostic
framework
in
terms
of
like
what
what's
used
to
to
render
our
dashboards
and
widgets.
D
This
also
means
that
this
is
a
bit
of
a
pre-optimization,
but
it
also
means
that
group
optimize
can
also
slow
down
quite
early
into
into
the
process
of
making
use
of
our
reusable
dashboards,
because
what
we
have
is
something
that
is
completely
configurable.
D
You
can,
based
on
the
configuration
of
the
widget
coming
in
we've,
pulled
the
data
source
based
on
the
type
and
the
current
data
source
that
we
have
right
now
is
Cube
analytics
and
Cube
analytics
is
just
a
simple
Library
function
that
can
we
can
extend
after
time
that
runs
the
cube
query
and
converts
it
to
the
expected
output
for
all
of
our
charts.
So
this
could
be
swapped
out
with
any
other
data
source
that
we
wanted
to
use
in
the
future
or
any
other
API
also.
D
So
it
could
be
another
Cube
instance,
and
then
we
transform
it
to
a
standard
chart.
Output
that
has
the
benefits
that
are
actual
chart.
Components
are
incredibly
simple
and
should
just
focus
mainly
on
like
the
responsiveness
and
The
Styling,
and
those
are
all
still
issues
that
we
like
did
the
ux
that
we
can
like
continue
to
improve
on
and
for
the
next
two
visualizations
that
we
have,
which
is
the
the
like,
the
counter,
the
single
value
and
the
table.
D
They
should
be
able
to
slot
into
this
new
framework
quite
easily
and
just
build
upon
what
I
have
mostly
actually
using
the
code
that
I
wrote
and
if
anything
comes
up
where
it's
not
reusable.
We
can
just
extend
what's
here
but
yeah.
That's
just
a
quick
demo.
A
D
D
Just
writing
a
bunch
of
specs,
currently
so
yeah
pretty
much
all
all
the
word
concerned,
I'm
just
verifying
that
everything
works
as
I
expected
and
throwing
hqs
inside
it,
then,
hopefully,
by
the
end
of
the
day,
we'll
be
in
review.
Nice.
G
A
All
right
we're
getting
more
agenda
topics
added.
This
is
great
great
to
see,
but
we're
also
running
out
of
time
final
topics.
Timmy
have
the
first
point.
G
G
Data
with
and
on
the
site
may
be
another
cluster
which
is
simply
containing
test
data
so
that
we
have
all
the
the
same
base,
for
example,
and
also
can
connect
easily,
hopefully,
at
some
point
review,
apps
I
think
it
doesn't
have
a
high
priority
or,
let's
say
super
high
priority,
but
any
everything
that
we
can
take
into
consideration
there
to
get
us
there
as
soon
as
possible.
I
think
would
be
really
nice
in
taking
us
from
there.
So.
A
Yeah
we
were
talking
about
this
yesterday
because
I
think
there's
a
lot
of
reusable
test
steps
and,
as
especially,
we
start
to
incorporate
the
dashboards
into
things.
Getting
reviewed
it'll
be
a
lot
easier
for
people
to
review
it
if
we
have
something
that
they
can
just
plug
into
and
start
looking
at
data
without
having
them
needing
to
run
Cedars
or
anything
like
that,
so
I'm
definitely
happy
to
set
up
another
cluster
specifically
for
this
purpose.
A
I
guess
one
thing
we
would
need
to
figure
out
is:
if
that's
something
we
want
to
anonymize
or
kind
of
modify
or
transform,
so
that
it's
not
the
same
data
that
we
all
have
access
to,
but
that
can
definitely
be
a
good
test
for
one
just
testing
the
mirroring
of
data
between
clusters,
but
also
there's
basically
I.
Just
given,
like
you
said,
it's
not
the
top.
The
highest
priorities.
I
just
wanted
to
get
the
interest
from
everyone
else
to
see.
A
If
that's
something
worth
looking
at,
because
I
also
have
been
thinking
about,
you
know
publishing
the
data
set
automated
so
that
everyone
has
a
fresh
set
to
work
with
at
any
time
and
then
also
the
dev
kit
could
use
the
cedar
as
well.
So
there's
different
forms
of
this
so
just
trying
to
see
if
it's
worth
jumping
into
right
now,
when
I
hop
back
and
forth
between.
F
A
So
I'll
I'll
put
the
issues
together
and
then
I'll
start
organizing
them.
G
G
That
that
is
basically
poking
currently
into
my
eye
is
that
that
we
have
the
events
tables
simply
called
Jitsu.
So
if
anyone
knows
how
we
can
configure
this
very
easily
so
that
we
can
call
it
track,
debates
or
anything
I
will
also
create
an
issue
for
this,
but
I
would
like
to
think
in
the
sense
of
that
we
remove
all
the
teacher
naming
references
because
yes,
I
can
definitely
see
that
we
rather
or
earlier.
G
Rather
earlier
than
later,
we
are
going
to
hop
on
a
train
that
we
are
building
our
own
tracking
endpoint
system
through
the
product
intelligence
team.
So
this
yeah
just
keep
this
in
mind.
If
you're
naming
anything,
then
rather
not
call
it
Jitsu,
but
rather
call
it
trekking
or
something
like
that.
So.
B
G
A
Very
smart
to
do
this
is
more
advisory,
but
yeah
I
think
the
champ,
the
the
tampermonkey
script,
we're
using
I
think
we'll
still
continue
to
be
useful,
as
as
we
kind
of
experiment
with
getting
new
data,
I
guess
what
I'm
trying
to
say
is
I
want
to
move
it
into
repo
so
that
everyone
has
the
capability
to
add
stuff.
A
So,
for
example,
if
Tim
wants
to
add
additional
events
or
track
page
areas
or
things
like
that
or
anyone
else
in
the
team
that
wants
to
you
do
have
control
to
do
that,
it
should
be
easy
to
migrate.
Since
people
are
pointing
to
the
snippet,
we
can
just
point
to
the
final
location
of
where
it's
in
the
repository.
So
this
is
just
more
of
an
advisory
like
we'll
move
it,
so
everyone
else
has
is
able
to
contribute
to
that.
There.
A
C
F
G
Yes,
I
stumbled
last
week
overview
grid
layout,
so
that
looks
really
like
in
the
way
what
we
want
and.
G
Might
take
a
look
to
switch
over
to
that,
because
this
gives
us
really
already
the
functions
to
serialize
and
deserialize
by
default
and
that
might
be
cut
the
the
time
for
getting
us
to
a
level
where
we
can
edit
grids
in
half
looking
at
it,
but
only
I
looked
at
it
for
10
minutes.
So
far,.
B
I
I,
if
you've
got
capacity
to
do
the
review,
works
I,
don't
own.
This
Milestone
that'd
be
great
I'm
agnostic,
whatever
we
use
as
long
as
it
covers
all
the
immediate
features
we
need
to
build
and
with
a
consideration
for
future
too
and
I'm
sure
I
know
you've
you,
you
know
everything
we
need
to
do
so.
Whatever
you've
come
up
with
in
an
issue,
I'm
happy
to
proceed
with.
G
G
What
we
had
in
the
POC
that
was
using
a
vanilla,
JavaScript
library,
so
anything
that
is
around
reactiveness
and
serializing
and
deserializing.
We
would
have
needed
to
write
on
top
of
this,
and
this
is
basically
already
a
view,
control
that
has
everything
like
that
built
in,
so
we
can
basically
hand
over
the
different
objects
and
should
have
at
the
end,
if
we
configure
everything
right,
basically,
discrete
we
hit
save,
we
get
a
full
Json
pack
and
that
should
already
have
basically
the
output
of
exactly
what
we
are
defining
in
the
schema.
B
Yeah
just
to
raise
that
dinosaur
and
I
have
put
in
a
code
change
suggestion
for
the
dashboard
working
group
that
they're
setting
up
to
start
figuring
out
Noma
culture
for
the
dashboards
and
how
they're
going
to
interact,
and
all
that
kind
of
thing.
B
B
H
Yeah,
thanks
for
joining
us
would
be
good
to
get
us
good
to
get
us
represented
there
for
sure.
G
And
I
will
also
reconnect
next
week
with
Kristen
the
pm4
manage
foundations,
as
it
is
called
by
now,
as
they
are
the
main
drivers,
together
with
ux.
So
I
think
we
are
heavily
aligned
on
this
and
I
think
it
might
be
a
perfect
solution
to
have
a
working
group
to
align
this
through
optimize.
But
I
was
also
talking
to
a
read,
for
example,
on
on
deaf
site
that
we
might
have
even
some
more
use
cases
around
dashboards
and
so
on.
So.
F
F
G
Awesome
thanks
a
lot
for
everyone's
inputs.
It
was
a
great
meeting,
even
if
we
went
over
a
little
bit
but
yeah
take.