►
From YouTube: 2022-11-08 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
Hello,
everyone
welcome
to
the
November
8th
edition
of
the
product
analytics
sync.
We
have
a
full
agenda
and
a
full
list
of
attendees.
So
let's
go
ahead
and
get
started.
Would
anyone
like
to
volunteer
to
review
the
billboard.
A
B
A
Alrighty,
let's
start
with
design
our
resident
designers
there
anything
to
report
here.
C
All
of
the
screens
are
more
or
less
done.
We've
we've
removed,
but
we've
separated
out
stuff
we're
going
to
do
now.
As
for
the
minimum,
viable
products
and
stuff
that
we're
gonna,
we
think
about
doing
in
future,
I
need
to
fill
out
those
that
flesh
out
the
issues
that
we've
broken
out
a
bit
more
and
we
have
a
week
a
bi-weekly
with
Sam
me
and
Jan
tomorrow,
just
to
make
sure
we're
all
aligned
and
doing
the
right
things,
and
hopefully
we
can
start
getting
these
into
planning
breakdown.
C
A
Then
we've
got
retrieve
project
dashboards
geographical,
which
is
a
planning
breakdown.
Is
there
anything
we
can
do
here?
That
should.
D
Be
in
review
okay!
Well
then,
let's
update
that
yeah
Rob
already
reviewed
it.
It's
in
maintainer
review
now
and
once
that's
done
and
merged,
we
can
go
ahead
and
add
more
to
it.
Essentially,
at
the
moment,
it
just
pulls
out
the
name
description
and
the
grid
attributes
of
a
dashboard,
and
once
the
maintainer
is
happy
with
the
general
approach
for
taking,
then
we
can
expand
that
to
the
rest
of
the
dashboard
schema
excellent.
A
Cool
there
you
go
track
usage
with
new
tracker
on
internal
handbook,
which
is
blocked,
which
I
guess
we
could
just
blend
itself
into
my
update
here.
Production
Readiness
review
is
still
in
progress.
I'm
waiting
for
I'm,
going
to
repeat
them
again
today,
iot
to
provision
a
or
purchase
a
domain
name
in
the
provision
on
Google
cloud.
Is
this
necessary
for
the
security
and
compliance
part
where
they
quite
literally
want
to
know
where
everything's
hosted
and
all
that
kind
of
stuff.
A
So
I'm
waiting
on
that.
Unfortunately,
the
timing
didn't
work
out
with
the
whole
security
transition
we
were
making
regarding
OCTA,
so
I'm
gonna
be
pushing
on
that
this
week,
since
it
seems
like
we've
wrapped
that
up
last
week
and
then
we've
got
the
cube
query:
rendering
widget
for
line
chart.
E
Yeah,
so
this
is
still
in
development
as
a
first
step
towards
this,
we
need
to
update
our
I
guess
foundational
architecture
in
order
to
introduce
a
visualization
as
this
new
reusable
concept
that
can
be
shared
by
widgets
across
multiple
dashboards.
I've
created
a
craft
Mr
for
that
and
I've
also
started
working
with
the
dev
kids,
trying
to
trying
to
figure
out
how
to
yeah
link
that
up
to
Cube
and
get
everything
working.
E
B
A
Yeah,
if
anything,
maybe
open
a
slack
thread
specifically
with
the
issue
you're
encountering
on,
and
then
we
can
potentially
swarm
on
an
async
curious
what
the
error
is
or
if
it's
related
to
Tim's
issues.
Yesterday.
A
All
right
we've
got
to
find
version.
One
of
the
user
dashboard
schema
this
one's
overdue.
I
have
an
agenda
point
for
this.
We
can
either
address
it
now
or
we
can
get
into
it
later.
F
Yeah
so
Diane
gave
me
like
yeah
I
have
mentioned
before
that
I
had
some
doubts
regarding
regarding
these.
These
simple
issue
yeah,
and
so
some
of
them
were
pointed
out
by
by
giannon.
Thank
you
so
I'm
working
if
it
is
in
review,
slash
on
dev
as
well
so
I'm
addressing
those
but
yeah,
but
but
it
is
probably
and
the
other
one
that
I
have
there.
F
The
moth,
Cube
API
proxy
feature
flag
to
EE
the
a
super
simple
one
that
went
to
production
and
came
back
so
running
the
pipeline
it's
taking
forever,
but
it
should
be
also
ready.
Today.
A
Got
it
yeah
first
broken
Master,
it's
exciting
all
right:
we've
got
ad
support
for
post
requests
and
our
cube.js
library.
C
Yeah
big
thanks
to
Max
for
asking
the
question
and
making
me
go
back
to
that,
because
I
was
able
to
finally
figure
out
a
way
of
making
post
requests
work
with
Cube,
so
I'm
updating
the
back
end.
C
Implementation
to
use
posting
instead
of
get
and
I
have
a
working,
Cube,
JS
call,
which
makes
use
of
a
custom
HTTP
transport
to
allow
us
to
pass
customer
the
headers
we
need
I
found
those
through
axios,
so
you're
on
an
axel
when
we
start
working
on
the
actual
visualization
stuff
pulling
in
Cube.
Where
that
issues
has
the
exact
details
and
I
can
always
share
with
them
again
when
we
get
to
it.
A
A
Adding
open
API
V2
documentation
so
now
we
can
see
where
we
ended
up
after
that.
Oops
excuse
me.
So
we
closed
adding
the
ability
to
enable
or
disable
product
Evolution
of
the
admin,
a
number
of
screens
in
the
design
phase
or
product
analytics
configuration
details,
view
API
endpoint
to
save
product
analytics
details.
Anything
you
would
like.
A
Right,
we
also
closed
sorry.
Actually,
you
have
two
issues
closed
here.
So
I
don't
know
if
you
wanted
to
cover
any
of
these
regarding
the
admin
settings.
F
Oh
yeah,
those
two
are
related
to
the
same
piece
of
work
and
yeah
everything's.
Fine
I
do
have
some
follow-ups
to
address.
For
example,
one
of
them
is
to
is
to
add
a
link
for
the
documentation
that
Max
and
graciously
did,
but
yeah,
mostly
mostly
small
follow-ups
and
from
from
local,
is,
is
completely
functional.
Now
so.
A
Cool
and
then
lastly,
we
have
we've
closed
out
the
issue
for
making
an
internal
announcement
about
dog
fooding
plants
which
had
gone
out
some
weeks
ago.
Anything
else
you
want
to
add
here,
Sam.
G
No,
it
was
posted
on
slack
and
folks.
Read
it
cool.
A
Yeah
we're
getting
a
little
bit
more
data,
as
well
as
a
side
note
on
our
little
extension
Sam
reached
out
to
the
data
team.
I
think
we've
got
two
additional
people
using
it
currently
and
we're
at
about
200
events,
but
so
far
it
looks
like
we're
getting
a
steady
stream
every
day.
So
that's
it's
nice
to
have
I'll
work
on
making
that
more
readily
available,
but
I
wanted
to
gather
some
feedback
on
that,
so
that
will
wrap
up
our
billboard
review
and
then
we
can
go
off
into
the
next
Point
Sam.
G
Yeah
so
just
wanted
to
highlight
a
couple
changes
and
updates
to
a
few
issues,
as
well
as
the
roadmap
recently
as
we're
making
progress
towards
getting
our
dog
food
released
out
the
question
of
what's
next,
and
what
are
we
going
to
be
doing
afterwards
is
is
a
good
one
to
ask,
and
so
I've
gone
through
and
added
some
extra
detail
to
the
two
issues
that
are
linked
there,
as
well
as
some
others
in
our
product
analytics
HQ,
epic
I,
encourage
you
to
go.
Take
a
look
at
them.
G
Really
what
they're
going
to
be
highlighting,
though
or
the
next
big
areas
of
the
product
we
want
to
work
on,
are
really
finishing
up
the
schema,
driven,
dashboarding
and
widget
organization
in
the
product,
as
well
as
data
export
for
a
look
beyond
what
is,
after
that,
I
would
encourage
you
to
check
out
the
link
to
the
the
roadmap
deck.
G
This
deck
is
very
much
in
progress,
but
if
you're
familiar
with
what
we
had
in
compliance,
my
end
goal
is
to
get
a
similar
sort
of
work
product
out
of
it,
but
the
roadmap
slide
is
up
to
date.
At
this
point
in
terms
of
Stack
rankings,
so
that
should
reflect
what's
coming
in
the
future.
That's
also
collected
on
the
direction
page,
if
you've
seen
a
couple
of
emrs
that
I've
worked
on
the
last
few
days,
so
would
love
to
have
feedback
comments
or
thoughts.
Other
synchronously
or
asynchronously
on
that
and
that'll.
G
If
there's
no
comments
or
questions
Dennis,
you
have
the
next
one.
A
Cool
had
a
couple
of
different
points.
Just
wanted
to
get
the
group's
feedback
on
so
the
first
one
was
the
GPC
or
the
global
privacy
control
signal
that
browsers
are
now
starting
to
send
and
how
our
JavaScript
SDK
responds
to
it.
For
those
that
don't
know
do
not
track
was
the
kind
of
first
iteration
of
that,
and
that's
something.
A
That's
configurable
through
your
browser
settings
GPC
on
most
browsers
at
least
I've
encountered
on
some
installations
of
chrome
and
certain
privacy
focused
browsers,
like
brave,
for
example,
it's
sent
by
default
for
me,
I,
don't
know
if
it's
an
experiment
or
not,
but
on
Chrome.
For
me,
the
GP
GPC
signals
always
sent
so
I've
actually
had
to
use
a
extension
to
turn
that
off
for
the
tracker
to
work.
For
me
for
additional
context,
GPC,
the
intent
is
that
you
enable
that
signal.
A
When
you
don't
want
websites
to
sell
your
data
or
share
it
Beyond
themselves
or
basically
share
it
with
third
parties,
we
have
no
intention
of
doing
either
of
those
with
any
of
what
we're
building.
So
the
reason
I
ask
about
how
we
want
to
respond
to
GPC
is
that
we
are
currently
disabling
the
JS
SDK
as
soon
as
we
see
that
signal,
but
if
it's
sent
by
default-
and
we
have
people,
for
example,
dog
fooding,
this
there's
a
little
bit
of
friction
there
in
terms
of
getting
them
to
disable
that
signal.
A
So
the
question
then
becomes:
do
we
actually
listen
like
are
we?
Are
we
respecting
the
signal
properly
because,
by
definition,
I
don't
think
we
are
like
or
played
a
different
way?
I,
don't
know
that
we
need
to
turn
off
the
SDK
when
GPC
is
on
and
I
think
that
will
also
simplify
just
the
JavaScript
SDK
initializing,
when
we
expect
it
to
because
we
again,
we
have
no
intention
of
selling
data
or
sharing
it
Beyond
ourselves.
A
So
just
wanted
to
get
the
team's
feedback
on
that.
If
we
need
to
update
the
JavaScript
SDK
accordingly,.
C
I'll
vocalize
what
I've
said
in
regards
to
that
from
a
front-end
point
of
view,
the
spec
only
sets
true
or
false
one
or
zero
is
there's
a
conscious
decision
to
not
make
it
extensible.
So
you
can't
can't
say
I
only
want
I.
C
Don't
want
you
to
track
me
for
X,
Y
or
Z
reasons
which,
in
terms
of
GPC,
there
are
a
few
different
reasons
why
people
turn
them
on
might
be
because
they
don't
want
to
be
tracked,
full
stop
or
it
might
be,
because
they
don't
want
their
data
to
be
sold
to
third
parties
like
you
suggested
Dennis
or
or
they
just
don't
want
their
personal
data
collected,
not
just
any
data,
just
identifiable
information
more
than
just
session
data.
You
know
people
use
Pages.
C
So
there
is
a
quote.
We
do
have
a
issue
to
enable
privacy
mode
on
Jitsu
by
default,
which
would
remove
a
lot
of
the
identifiable
information
related
to
people
and
replace
it
with
a
with
Anonymous
ID,
more
or
less
rather
than
an
IP
address
related
data.
C
So
we
could
enable
that,
and
if
we
did
that,
then
I
would
be
happy
with
just
turning
off
GPC
or
having
a
setting
like
we're
thinking
for
cookies.
Just
to
say,
do
you
want
to
enable
GPC
and
have
it
defilter
off
yeah.
A
I
think
for
users
of
the
JS
SDK,
who
might
have
a
potential
to
sell
or
process
data
beyond
the
first
party,
we
should
still
have
that
as
a
configurable
option
for
sure,
so
my
suggestion
would
be
then
to
default
it
to
off
with
obviously
provide
a
control
for
them
to
respect
that
signal
in
the
case
that
they
have
that
capab
or
want
that
capability
to
do
more
with
that
data
with
regards
to
privacy,
mode,
I
think
also
yeah.
We
can
make
that
default
too,
but
I
think
making
it
configurable.
A
The
GPC
signal
and
defaulting
it
to
off
would
be
my
recommendation.
Sam
did
you
want
to
vocalize
your
point
so.
F
G
If
we
want
to
change
direction
on
that,
we're
going
to
have
to
recommunicate
all
of
that,
because
of
that,
my
suggestion
would
be
that
we
keep
forward
with
supporting
GPC
in
our
internal
dog
fooding.
If
we
want
to
make
a
change
to
not
look
at
it,
we
do
that
in
alignment
with
the
customer
facing
release,
because
once
we
go
from
31.0
to
1.0,
that's
our
chance
to
make
any
sort
of
breaking
changes
like
this
that
we
would
want
to
without
having
to
realign
everyone.
The
organization
because.
A
G
G
A
The
announcement
says
that
we
will
support
Global
privacy
control
and
what
I'm
suggesting
is
we
I'm
not
saying
we
don't
support
GPC?
What
I'm
saying
is
that
we
have
to
treat
the
signal
differently,
because
if
we
go
out,
as
is
more
than
likely,
the
JS
SDK
will
not
fire
for
most
users
and
based
on
how
the
GPC
is
defined.
We
are
not
violating
it
by
enabling
the
JS
SDK,
while
the
signal
is
on
for
our
purposes
of
dog
fooding,
so
I'm
in
no
way
suggesting
we'd
stop
support
for
it.
C
To
be
clear,
the
announcement
now
is
actually
more
in
line
with
what
Sam
says.
We
say
it's
making
it
possible
to
opt
out
of
having
data
from
the
internal
handbook
be
collected,
so
we
are
saying
that
it
it.
We
do
respect
GPC
if
we,
which
then
leads
towards
turning
this
into
a
setting,
but
defaulting
it
to
on
for
now,
until
we
can
make
that
breaking
change.
Instead.
Okay,.
A
A
G
Yeah
I
think
that
makes
sense,
and
once
we
get
to
that
1.0,
maybe
we
even
change
it
to
default
off
in
gitlab,
Inc
switches
it
on
for
our
own
purposes
and
lets
customers
do
their
own
choice.
A
C
A
Thank
you.
Rob
I
also
wanted
to
talk
about
course
configurability
on
GDK,
because
that's
right
now
is
not
easy
to
do.
Since
everything
is
now
done
in
a
different
yaml
file
and
the
gitlab
yaml
config
file
will
get
overwritten
every
time.
You
reconfigure
so
I
have
an
MR
to
add
the
option
of
disabling
it.
We
can
add
additional
attributes
to
instead
Define
the
allowed
hosts,
but
I
just
wanted
to
give
people's
thoughts
on
that.
So
we
can
make
action
on
that.
A
C
Otherwise,
I'd
much
prefer
if
we
could
either
set
the
custom
GDK
additional
hosts,
not
GDK
and
add
those
to
our
course
policies
or
alternatively,
snowplow
does
this,
where
a
snowplows
enabled
it
adds
the
snow
plow
host
to
cause
for
The
Collector,
the
snow
Pals
collected
and
hosting
so
I'm
wondering,
if
maybe
we
can
use
the
admin
settings
that
we've
got
now
in
the
U
in
the
product
to
add
that
cause
value.
So
even
when
you
set
it
up
locally,
it
should
automatically
allow
you
free.
A
Yeah,
that
sounds
like
a
good
idea,
as
so
to
be
fair,
I'm
not
or
to
be
clear,
I'm
not
advocating
for
disabling
course,
there's
like
a
general
practice
to
do
it
all.
There's
just
an
open
item
for
GDK
options
to
be
migrated
to
this
new
setting
and
just
disabling.
It
is
a
valid
setting
that
it
has
and
it
may
fit
some
use
cases
for
different
people,
but
yeah
if
we
bring
over
just
the
allowed
host.
A
That's
totally
fine
as
well
I
feel
like
that
potentially
less
effort
than
the
admin
settings
thing
though
I
do
agree
that
that's
better
from
a
user
user
experience
perspective
and
would
probably
also
help
us
out
on
the.com
side
of
things.
Maybe,
but
actually
I,
don't
know
if
that
touches
our
cloudflare
integration.
To
be
honest,.
A
C
A
You
anyone
else
any
thoughts
on
that
one
I'm
gonna
skip
C
just
out
of
time.
I
want
to
get
some
feedback
on
the
test.
Data
set
that
I
had
sent
I
know
Tim
had
been
playing
with
that,
but
I
was
curious
if
the
rest
of
the
team
had
time
to
work
with
that.
A
E
A
It
I
have
a
task
to
automate
the
process
of
exporting
that
and
making
that
available
to
people.
So
I
just
want
to
figure
out
how
to
prioritize
it.
Based
on
how
people
have
been
using
it
to
make
sure
that
the
process
works
before
I
spend
time
working
on
that
so
I'll
I'll
hold
for
that.
B
Good
I
yeah
I
already
see
City
on
the
slack
thread
where
we
discussed
all
the
thingies
and
the
problems.
The
other
topic
was
that,
as
we
are
not
peeling
the
version
of
G2
at
the
moment,
this
means
the
table.
Columns
are
changing.
Would
it
work
if
the
dump
basically
has
the
column
headers
in
the
file?
Then
it
should.
A
I'm
I'm
not
convinced
that
it's
the
Jitsu
versions
that
are
causing
the
columns
things
because
I'm
seeing
new
columns
being
added
to
the
test
cluster
right
now,
it's
something
completely
also
unrelated,
but
we
started
Sam
and
I
started
to
see
data
come
from
gitlab.com
from
both
of
us
and
some
in
very
rare
instances.
So
there
might
be
a
cores
issue
there.
But
when
that
happened,
it
started
sending
a
GL
user
ID
column
over
which
I
just
haven't
investigated
in
so
I'm
wondering
if
something
on
the
I,
don't
think
jsotk.
A
But
the
Jitsu
tracker
is
just
for
some
reason:
adding
new
columns
and
I'd
love
to
understand
why
that's
happening
and
then
how
we
can
then
potentially
restrict
that
up
from
our
end.
But
to
answer
your
question,
the
intent
is
to
create
like
I
export.
Both
the
table
schema
as
well
as
the
data
set.
So
theoretically,
when
you
load
it
so
I'll
need
to
tweak
the
instructions.
But
basically,
if
you
want
to
load
it
into
your
dev
kit,
you'll
just
create
a
delete
the
table.
If
it's.
If.
F
A
Animation
has
already
created
one
and
then
rename
the
scheme.
The
table
schema
import
to
match
that
of
whatever
project
namespace
you're
integrated
with
and
then
it'll
that'll
continue
to
collect
data
that'll
create
additional
columns
if
needed
be,
but
then
the
data
set
will
be
at
least
allowed
to
import
in
so
that
you
can
at
least
run
the
visualizations
against
it.
B
C
In
general,
we've
not
done
any
work
regarding
restricting
what
Jitsu
collects
necessarily
from
the
front
end,
so
it
might
be
collecting
cookies
and
stuff,
and
other
environmental
variables
might
be
what
it
is
and
on
the
other
end,
in
terms
of
cube,
we
have
a
schema,
but
it's
a
schema
from
the
preferred
concept.
We
have
not
narrowed
or
refined
or
defined
what
data
Cube's
meant
to
be
collecting
either
yet
so
when
it,
which
is
fine
for
the
just
proof
of
concept,
internal
handbook
work.
A
And
it'll
be
an
iterative
process
too.
We
also
want
to
learn
lean
on
product
and
Titans
to
get
to
get
gain.
Some
use
utilize,
their
wisdom
on
a
taxonomy
and
things
like
that
and
the
schema
in
general
yeah.
F
A
All
right,
you're
running
out
of
time,
but
I
definitely
wanted
to
get
to
this
point.
A
A
Basically,
the
discussion
and
I
agree
is
we
should
at
least
for
the
MVC.
We
should
pick
one
or
the
other
I
think
it's
valid
to
eventually
support
both
but
I'm,
also
thinking
about
it
from
a
user
perspective
and
a
user
experience
perspective,
and
also
just
what
what
is
simpler
to
to
to
excuse
me
to
ship
right
now
for
our
first
iteration
Beyond
robbed,
and
you
have
a
couple
points
here.
If
you
want
to
vocalize
and
then
we
can
try
to
reach
a
decision
very
quickly,.
E
Yeah
I'll
I'll
quickly,
vocalize
mine,
since
I
guess
Rob's
comment
is
my
comments
in
that
I
think
technically,
supporting
one
or
the
other.
The
cost
is
more
or
less
the
same,
so
I
think
our
decision
should
be
on
what's
the
most
usable
and
then
also
to
say
that
I
totally
agree
that
if
we
support
both
completely
there
is
a
middle
ground
that
we
can
have
where
we
we
say
set
a
of
dashboard.
We
allow
and
set
B
of
widget
configuration.
E
We
allow,
for
example,
dates
are
only
on
a
dashboard,
that's
also
explorable,
but
if
we
allow
dates
and
stuff
like
that
to
override
on
both,
then
it
becomes
complex
both
technically
and
as
a
be
like
just
building
this
interface
and
figuring
out
how
we're
going
to
deliver
to
users.
I
think,
that's
something
that's
I
think
is
best
avoided
for
MVC
yeah.
C
I
mean
I'm
just
playing
Devil's
Advocate
and
we're
pointing
out
that
are
very
common
patterns
to
have
date
range
set
graphs
next
to
each
other.
So
you
can
see
progression
over
time
if
that
makes
sense
and
narrow
Focus,
but
I
agree.
We
should
stick
to
one
I
would
probably
vote
for
the
dashboard
level
customization
options
for
now,
just
because
cascading
granularity
can
get
complicated,
even
if
you
start
doing
value
models
and
stuff
like
that.
B
I
think
so
too,
and
the
dashboard
ones
would
be
more
important.
That
only
thing
that
came
now,
to
my
mind,
is
why
not
rather
do
instead
of
an
override
model
rather
pass
on
value,
so
that
we
basically
have
okay
on
the
top
of
dashboard.
We
Define
something
we
have
a
filter.
Okay,
let's
call
it
select
the
date
range.
This
is
simply
automatically
passed
on
to
all
the
widgets
that
are
in
the
dashboard,
and
the
widget
itself
can
then
decide
where
to
put
it,
what
to
do
with
it
Etc
and
the
same
model.
B
Then,
on
a
widget
level,
where
we
can
say
Okay,
a
widget
can
have
a
specific
prop
that
can
then
be
set.
Basically
in
the
designer,
where
you
can
say,
Okay
I
want
to
have
last
90
days,
because
we
will
definitely
need
some
sort
of
relative
time,
namings
Etc.
That
is
something
very
common,
and
then
we
simply
pass
that
prop
on
in
also
again
into
the
witches
and
in
the
widget.
B
We
decide
where
to
use
this
in
the
query
if
at
all
Etc,
so
so
it's
not
this
complex
model
of
override,
because
then
you
might
also
get
into
the
situation
rename
something
down
there.
The
override
comes
in,
and
it's
not
matching
anymore
and
stuff
like
that.
So
what
do
you
think
about
that?.
A
Was
just
going
to
say,
I
think
that's
a
good
approach,
as
we
approach
like
go
from
dashboard
to
widget
level,
I
think
for
the
purposes
of
this
MVC
dashboard
level,
also
from
a
user
experience
perspective
will
be
simpler
because
I
I
do
believe.
A
There's
value
in
having
both
I'd
consider
that
more
of
a
power
user
thing,
because
I
I
can
I've
seen
users
get
confused
themselves
where
they
Define
date,
Rangers
at
the
widget
level
update
something
at
the
dashboard
level
and
then
I
wonder
why
nothing
else
is
changing
below,
but
I
think
yes
defining
at
the
level
passing
that
information
to
widgets
and
then
what
to
decide
what
they
do
with
it
or
if
they
have
something
to
find
at
their
level,
then
that
just
you
know
it
gets
used
instead.
A
I
think
that
makes
sense
when
we
do
decide
to
support
both
but
yeah
I,
don't
know
if
you
had
any
final
thoughts
before
I
was
going
to
push
for.
E
That's
that's
pretty
much
exactly
what
I
was
thinking.
I
think,
okay
seems
good,
makes
sense
and
it's
I
think
Best
Kept
For
a
follow-up
iteration.
So.
A
Can
we
agree,
then
we
will
go
to
the
dashboard
level
for
now,
as
as
the
first
iteration
and
we'll
expand
into
which
level
V
1.1
or
how
the
in
the
next
iteration
awesome
thumbs
up
thumbs
up
thumbs
up.
Okay,
Sam,
if
you
had
a
point,
I
already
answered,
and
it's
part
of
my
status
update
production
Readiness
is
my
focus
for
today
and
unblocking
that.
However,
I
can
any
other
final
thoughts.
Anyone
had
before
we
sign
off.