►
From YouTube: Manage:Import 13.1 planning (2020-05-15)
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
A
A
Well
with
the
team
I'm
blinging,
two
different
boards
that
we're
going
to
be
using
here
so
that
you
know
you
can
just
all
on
your
own
or
go
back
to
at
some
point
to
kind
of
see
all
the
B's
that
I'm,
showing
I
have
not
listed
as
far
as
the
objectives.
I'll
talk
about
the
objectives,
but
in
general
this
time
around
I've
avoided
listing
exact
issues
because
I
feel
like
that
is
not
maintainable
in
a
Word
document
type
format
where
we
have
lists
that
are
dynamic
and
true
and
can
be
filtered.
A
A
The
highlights
of
of
13:1
are
you
know
we
have
to
see
if
there's
leftover
and
it
seems
like
that
issue-
might
spill
we'll
talk
about
like
any
kind
of
spillover,
but
if
there's
any
spillover
for
the
new
project
creation
UX
that
will
be
top
of
our
agenda
top
of
our
priority
and
you
leftover
work
for
the
group.
Export-Import
uux
will
also
be
at
the
top.
After
that.
A
We'll
look
at
you
know,
miscellaneous
bugs
security
and
stability,
things
that
we're
moving
a
lot
of
attention
to
over
the
last
couple
of
milestones,
and
let
me
tell
you
that
actually
has
made
a
visible
progress
in
our
backlog
and
our
responsiveness
to
the
field,
because
we
used
to
have
issues
that
just
linger
for
a
long
time.
There's
still
a
lot
of
them
that
are
for
sure,
P,
threes
and
so
on,
but
still
are
there,
and
some
of
them
are
really
old.
A
But
I
was
able
to
triage
out
some
of
them
and
were
able
to
actually
slash
some
of
them
that
were
actual
problems,
so
we're
making
good
inroads
there
on
internationalization,
we'll
be
looking
at
potentially
automating,
some
of
the
import
stuff
and
that's
an
investment
I
will
make
early
so
that
we
don't
have
to
a
the
cost
of
manually
doing
this
over
time.
So
if
we
like
some
time
right
now,
it'll
it'll
pay
in
the
long
run
to
to
our
velocity.
B
A
Templates
same
thing,
we'll
take
a
look
at
a
list
and
have
you
know,
there's
probably
a
couple
template
issues
that
have
bubbled
up.
That
means
take
care
of,
but
it's
just
nothing
to
talk
about
the
one
big
your
discovery
now
I've
been
able
to
resync
with
Amanda
like
with
UX,
you
know
and
and
Amanda
on
our
goals
and
what
we're
doing
in
UX.
A
So
one
thing
we'll
be
working
on
in
13:1
is
bringing
to
close
our
discovery
of
UX
import
experience
of
the
import
experience
overall
and
how
that
then
plays
out
into
all
of
the
things
we're
going
to
do.
Some
of
the
things
we
talked
about
but
are
not
going
to
work
on,
is
making
progress
and
instead
bigger
solution
for
the
github
group
migration,
but
still
next
up,
but
we
weren't
able
to
tease
out
any
issues
and
indices
for
this
milestone
and
similar
for
metrics.
A
C
A
A
So
the
planning
boards
I've
looked
at
yesterday
and
they're
all
kind
of
ready
for
us
to
look
at
what
I
want
to
do
today
is
just
talk
about
the
roadmap,
so
some
of
this
is
the
objectives,
but
I
also
want
to
show
you
the
roadmap,
which
really
hasn't
changed
since
last
time.
I'll
show
you,
but
just
as
a
reminder
where
I
see
they
will
not
go.
A
We
have
just
talked
about
the
objectives
for
the
milestone,
we're
gonna,
look
at
the
previous
milestone
and
know
they
need
carryovers.
We're
gonna,
look
at
the
issues
in
the
refinement
for
some
last-minute
ready
for
development.
I
think
there
are
two
candidates
there
that
I
would
like
to
take
a
look
at
and
and
then
we'll
just
you
know,
big
things
for
13:1
and
all
we'll
set
them.
Deliverable
and
they'll
be
the
end
of
that
thoughts.
All
good.
A
So
the
roadmap
really
I
have
not
updated.
This
I
have
no
validated
decision
awake
to
the
stands
as
a
draft
at
this
point,
but
just
kind
of
as
a
quick
reminder
of
where
we
are
what
the
year
might
look
like.
I
do
know
that
we
want
to
pay
attention
to
these
two
blocks.
Here,
one
is
the
it's
like
group,
migration,
the
other
one
is
the
cloud
project.
Migration
I
expect
this
to
sort
of.
A
As
we
looked
at
the
import,
UX
I
expect
these
two
experiences
to
merge
together
in
the
user
experience
and
then
be
able
to
do
a
full
migration.
So
this
to
me
kind
of
represents
a
you
know:
six-month
effort
to
get
to
a
user
experience
for
importers,
good
lab
to
get
lab
where
we,
you
know,
move
away
from
the
files
and
get
a
solid,
stable
experience.
That
is
easy
for
people
to
access
a
lot
of
roadblocks
on
this
on
this
road,
but
this
is
just
a
general
kind
of
hate.
This
is
where
we
want
to
go.
A
A
This
is
the
this
here
represents
the
investment
that
I
want
to
make
early
like
in
13:1
and
probably
probably
are
still
into
13
to
as
well.
We're
gonna
talk
about
this
in
a
little
bit
to
sort
of
put
some
investment
into
automating
translations
so
that
we
don't
have
to
kind
of
many.
Many
do
manually
do
things
and
then,
after
that,
everything
is
speculative
will
be
validating.
A
What
can
we
do
with
this
past
that
I
expect
the
the
big
github
importer
project
to
hit
around
the
fall
and
we're
gonna
be
spending
a
lot
of
time
on
that?
So
this
is
kind
of
my
visibility
into
things
and
I
just
wanted
to
share
that
with
you,
so
that,
as
we
talk
about
things
as
we
go
from
Oslo
to
milestone,
you
get
an
idea
of
how
we're
moving
through
some
of
the
larger
goals
we
have
and
you
feedback
on
this.
A
So,
let's
start
with
looking
at
the
current
phallus
tone:
13
oh
I'm,
going
to
refresh
the
board
just
to
make
sure
I
get
the
latest
and
greatest
and
we're
gonna
have
to
figure
out
which
one
of
these
things
is
gonna
get
completed
in
30,
no
and
which
ones
which
ones
are
not
I.
Don't
have
a
great
way
of.
A
Marking
distant
here,
in
order
for
me
to
move
it
to
thirteen
one
so
we'll
have
to
just
figure
out
how
we
want
to
do
that,
but
maybe
if
we
can
just
talk
about
and
see,
if
there's
an
easy
chunk
of
things
like
everything,
interview
seems
to
be
making
it
mean
everything.
That's
not
in
review
is
not.
Then
I
can
probably
more
easily
mass
move
things
over
to
13:1.
D
D
This
these
two
are
the
same
thing:
yeah,
that's
right.
So
this
is
a
security
fix.
There's
nothing
I
need
to
do
there.
Everything
has
been
assigned
to
the
release,
but
when
the
security
release
happens,
that's
when
it's
going
to
be
essentially
emerged,
I'm,
not
too
sure
when's.
The
next
Security
release,
whether
it's
going
to
be
at
the
same
time,
with
certain
point
no
or
not.
A
E
A
Night,
thank
you
so
yeah
this
whole
batch
of
things
with
grouping
board
yeah.
F
A
A
E
A
I'll
look
into
that
so
it'll
be
something
for
me
to
to
worry
about
later
today.
So
I'll
just
change
this
to
thirteen
one
week,
because
because
we
know
it's
there,
but
also
as
far
as
it
impacting
the
velocity,
we
didn't
expect
this
to
be
a
big
it's
in
review,
so
it
may
have
some
shine
right,
but
not
not
a
lot
and
it.
F
A
F
A
A
H
Some
weird
issues
with
testing
the
folks
bugs
importer,
which
is
one
of
the
part,
so
this
will
not
make
it
I
will
probably
split
it
to
two
issues
or
not
third
block.
It
first
have
bitbucket
server,
Pro
Plus
cloud
review,
which
and
after
that,
the
folks
bugs,
because
maybe
I'm
missing
something.
Maybe
there
are
some
issues
with
folks,
but
reporter
I
will
probably
will
need
to
help
some
package.
People
and
I
problem
suggest
political,
probably
split
it
to
the
two
separate
requests
and
it
will
not
make
it
in
this
release.
Okay,.
A
Yeah
I
do
highly
recommend
splitting
the
sort
of
this
point
at
the
point
where,
where
the
cuffs
between
two
milestones,
everything
that
didn't
make
it
I
recommend
splitting
into
more
than
one
issues
if
that's
appropriate.
So
if
you
have
do
three
different
importers
to
visit,
just
putting
in
two
separate
issues
would
be
yeah
for.
H
We
should
have
there
like
to
set
up
a
proper
issues
and
to
have
understanding
when
we
will
finish
this
experiment.
So
from
my
belief
and
I
mentioned
this
in
issues,
this
should
not
go
to
the
release
post
of
13.0,
even
if
a
code
you'll
make
it
since
it
will
be
behind
the
experiments
lag
and
probably
it's
just
okay,
not
a
rush.
This
one
a
bit,
but
in
general
it
will
be
code
ready
to
jail
tomorrow.
Just
need
to
clear,
because
it's
just
in
time
I'm
conducting
the
experiments
thing
so.
C
A
B
A
A
So
let
me
see
yeah
we'll
just
discuss
this
again.
I
think
these
are
still
valuable,
so
I'm
gonna
try
to
remember
which
ones
these
were
so
switching
so
now
that
we've
kind
of
decided
what
to
do
with
these
I'm
literally
finding
this
morning
and
some
things
made
across.
There
are
a
couple
of
issues
that
I
do
want
to
discuss
quickly
and
see
if
we
can
do
something
about
them
and
they're
related
to
the
text
sent
to
sanitising
translated
text.
C
F
F
A
H
A
I
mean
we
can
also
still
come
in
here,
even
after
the
fact
like.
If
there
are
things
that
we
find
later
than
we
need
to
discuss.
We
can
come
back
here
and
if
this
turns
infeasible
or
for
whatever
reason,
I
another
kind
of
warm,
so
we
can
remove
it.
So
we
don't
have
to
feel
like.
We
have
to
know
if
this
is
the
right
thing
right
now,
but
if
it
looks
like
the
right
thing,
we'll
just
proceed
with
blooming
into
awesome:
yeah.
A
A
F
Okay,
so
the
idea
for
this
one
was
to
add
some
helper
arguments
or
something
to
the
translation
function,
call
so
that
we
don't
have
to
exclude
HTML
tags
and
make
it
really
hard
for
dibs
who
need
to
use
that
in
their
strengths.
Some
of
the
example
approaches.
If
you
click
on
this
link,
swear
adding
text
either
side
that
are
ones
that
we
just
handled
so
yeah
like
this
one,
where
it's
got
zone,
link,
start
and
zone
link
end
would
be
replaced
programmatically
by
the
a
tag
and
then
that
tag
doesn't
even
go
through
two
translations.
A
H
I
actually
have
a
small
concern
like
we
have
multiple
approaches
in
this
issue
and
it's
hard
for
me,
for
example,
Testaments
affront
when
to
wait,
because
it's
really
depends
on
which
parts
we
will
take
and
we
will
need
to
be
consistent
between
back-end
and
front-end.
In
this
translation
processing.
H
I'm
not
sure
that
we,
it
will
be
great
before
we
market,
is
ready
for
for
development
to
take
a
decision,
at
least
on
the
backend
approach
and
I
will
be
happy
to
jump
in
and
do
so.
We
will
have
a
proper
understanding
can
estimate
how
complex
will
be
it
on
front-end
I.
Don't
expect
any
major
troubles
but,
for
example,
to
understand
how
many
strings
will
be
affected
and
so
on,
like
we
still
have
not
free
but
feels
like
two
possible
approaches:
they're
good.
A
So
we're
not
sure
about
which
approach,
but
is
there
any
concern?
An
approach
may
also
turn
out
to
be
a
different.
Wait
like
it
could
be
a
different
level
of
difficulty,
depending
which
approach
we
take,
so
the
wait
might
go
up
or
down
with
different
approach.
Is
there
concern
that
one
of
these
approaches
will
turn
out
to
be
infeasible
or
that
it
will
blow
it
up
to
where
it
can't
be
completed
in
the
milestone?
Or
is
this
just
really
the
question
of
which
wait?
A
C
C
A
C
C
That
we
schedule
the
work
and
we
think
we
choose
an
approach
and
it
ends
up
being
a
lot
more
than
we
expected
like
you
mentioned,
and
then
it
slips
over
okay,
especially
because
this
touches
both
front
end
and
back
end.
So
we
don't.
We
have
a
different
way
of
externalizing
links
right
now
in
the
front
end,
it's
almost
like
using
HTML
tags
to
create
the
links,
so
we'd
have
to
figure
out
the
approach
that
we're
going
to
take
for
the
translation,
help
her
and
see
how
that
actually
ends
up.
C
A
Have
the
solution
this
is
this
is
what
this
one
coming
from
I
for
us
to
actually
make
this
investment
into
sanitizing
translations
like
her,
so
that
we
can,
you
know,
get
this
out
of
our
way,
I'd
like
to
make
some
progress
against
it
in
13
1.
I
am,
I
think
that
so,
first
of
all,
both
of
these
will
change.
A
So
my
concern
is
that
these
should
come
in
the
same
milestone,
hopefully
so
that
the
translation
community,
only
just
once
has
to
read
translate
everything.
I
think
it'd
be
a
lot
of
churn
if
we
give
them
new
strings
to
translate
your
13:1
and
then
kind
of
changes,
things
again
in
13
to
just
reword
things,
so
I
would
like
to
avoid
that,
so
I
would
prefer
if
these
two
could
come
together.
A
C
A
H
Just
to
throw
to
sense,
it
seems
about
the
total
number
of
translations
which
will
be
affected.
It's
not
that
big,
it
seems
like
there
is
just
104
translations
in
currently
which
use
HTML
tags
and
just
about
60,
which
are
taxed,
which
are
not
strong
or
B,
which
probably
will
be
accepted
in
translation.
A
H
F
Feel
like
the
approaches
that
are
linked
there
aren't
too
dissimilar
like
two
of
them.
The
only
difference
really
is
that
there's
a
different
method
call
rather
than
using
the
underscore
method
and
then
the
other
one
that
looks
like
it
was
kind
of
proven
not
to
work
so
it
it
feels
like
we're
just
deciding
between
whether
we
override
the
default
translation,
we'll
wait
to
find
a
new
one.
I,
don't
think
we'll
change
this
code,
a
huge
amount.
A
E
I'd
leave
it
in
refinement
because
I
think
I
haven't
read
those
issues
very
well
yet
and
I
think
they
buy
the
discussion
that
the
amount
of
time
that
we're
discussing
there's
low
confidence
on
how
we
can
approach
that.
So,
let's
keep
discussing
in
the
HP
itself
a
synchronously
and
maybe
on
the
next
weekly
we
can.
We
can
come
back
and
see
if
it's.
F
E
F
C
Are
we?
Are
we
comfortable
with
how
it's
currently
defined
I?
Guess
it
sounds
like
Josie
Amalia
you're
going
to
be
working
on
it,
so
if
you're
comfortable
with
think
on
thirteen
one,
we
can
do
that
if
you
think
we
need
another,
you
know
if
we
want
to
meet
next
week
to
actually
determine
this
and
do
some
more
digging,
then
we
can
also
do
that.
H
I
mean
we
could
do
that
in
at
least
several
merge
request,
because,
for
example,
we
definitely
should,
for
example,
I
suggest,
adding
the
limiter
as
early
as
possible
compared
to
altering
calls
er
strings,
because
otherwise
we
will
have
a
very
pain
point.
When
we
fix
all
our
code
base
and
new
strings
have
nurtured
with
merge
request.
Putting
must
have
to
read
I
mean
it
would
be
great
to
have
linters
and
somehow
disabling
existing
issues
early.
F
A
So
I
will
move
this
back
to
refinement
I,
do
ask
you
them
to
go
ahead
and
leave
space
in
13-month
for
these
two
issues,
because
there's
a
good
chance
that
if
we
don't
believe
space,
then
you
make
make
for
sure.
So
you
know
think
about
both
of
these
issues
when
we,
you
know,
imagine
them
being
in
13:1.
When
you
decide
what
other
issues
you
want
to
pull
into
35,
oh
so
great,
so
we'll
just
leave
this
I
mean
that
there's
there's
a
block
here.
A
What
we
need
to
discuss
if
we
find
out
things
by
next
Monday's
meeting,
we
can
discuss
on
Monday
as
well.
Whether
this
is
something
that
you
can
report
back
and
tell
us
that
you
feel
comfortable
now
or
not,
and
it's
not.
If
you
need
more
days,
then
it's
fine
too,
but
we'll
check
back
on
Monday
to
see
for
the
first
time
if
this
house
looking
you
so
this
one
is
still
in
refinement
anyway,
so
both
of
them
are
in
the
right
spot,
we'll
just
leave
them
where
they
are
cool,
and
thank
you
for
doing
this.
A
So
this
is
the
look
of
before
I
refresh.
So
these
were
the
three
things
that
were
in
13,
oh
and
I
thought
we.
If
we
had
move
things
back
into
ready
for
development
in
30,
no,
we
could
have
pulled
from
30
note
in
13
1
and
then
go
back
to
the
refined
section
here
and
then
pull
those
as
well
or
into
13
1.
But
if
I
refresh
all
these
will
go
away
because
we
cleaned
up
13.
A
A
So
that's
where
they
are.
What
we
don't
see
here
are
things
in
progress.
There
were
several
things
that
were
in
progress
there,
you're
gonna
have
to
sort
of,
as
we
think
about
how
much
we
can
take
on
consider
this
of
issues
here,
one
two,
three
four.
So
these
six
issues
with
a
weight
of
twenty
four
that
are
in
various
state
of
progress,
some
might
actually
be
almost
done
and
some
might
not
be
in
that
greater
state
anyway.
So
six
issues
with
the
way
the
twenty-one
are
already
in
progress.
A
Another
thing
to
consider
is
that
we
were
able
to
complete
24
issues,
but
we
also
per
sorry
fourteen
issues.
We
also
predict
that
these
additional
eight
issues
will
be
in
thirteen
home,
which
would
mean
that
we
will
have
22
issues
completed
in
thirteen
Oh
with
a
weight
of
39,
so
24
issues
in
the
weight
of
39
seems
to
be
what
we
predict
right
now.
30
no
will
look
like.
A
However,
I
don't
know
how
to
count
these
things
that
are
in
progress
here,
because
part
of
that
weight
was
carried
by
39
part
by
13
one.
So
that's
kind
of
almost
putting
a
difference.
There
somehow
I
think
we
have
a
great
way
of
figuring
out
like
what
are
the
lost
it
is
and
how
we
take
those
numbers
into
account
when
we
plan
thoughts
right.
E
A
Yes,
I'll
refresh
now
because
we
moved
things
around,
remember
that
it's
probably
best
to
refresh
because
we
moved
out
of
13
Oh
everything
if
we
don't
think
it's
gonna,
be
there
so
right
now,
13
Oh
looks
like
15
completed
and
5
in
progress,
so
that
is
30
issues.
The
weight
of
those
is
26
and
then
eight
more
coming,
which
is
34.
A
C
A
Actually
so
the
previous
three
milestones
we
did
not
have
estimates
on
everything,
so
we
didn't
look
at
weights
cuz.
We
just
started
estimating
about
month
and
a
half
ago
like
every
issue,
some
of
them
prior
to
that
work,
estimated
somewhere,
not
so
I
had
the
velocity
in
issues
so
issue
count
was
nineteen
for
the
last
three
milestones
weirdly
enough,
so
we
were
able
to
complete
nineteen
issues
for
the
previous
three
milestones,
which
is
kind
of
interesting,
because
right
now
we
predict
to
complete
twenty.
So
that's
a
1919-1920.
C
A
What
we
do
have
in
progress
which
is
not
showing
here
is
those
six
items
that
are
in
dead
right
now.
So
this
this
only
shows
to
this
board
only
shows
things
are
ready
for
development.
Everything
that's
in
death,
it's
not
gonna
be
displayed
here.
So
there
are
six
items
are
already
in
there.
So
we
need
to
subtract
those
from
the
of
items.
A
We
think
we
can
complete
how
much
please,
like
just
pure
math,
leaves
13
items
to
be
newly
scheduled
3
items
already
having
been
scheduled
in
because
they
were
highest
priority
previous
milestone,
they
were
assigned
to
previous
milestone
and
they
didn't
even
make
it
in
them.
So
taking
these
3
out
we're
looking
for
10
you.
So
if
we're
just
doing
that-
and
please
didn't
just
jump
in
if
you
feel
like,
we
should
adjust
the
math
for
reasons,
but
just
I'm
going
off
pure
math
I
mean
any
reason
not
to
do
that.
E
E
B
I
would
love
to
be
able
to
plays
out
all
issues
in
a
milestone
as
I've
spoken
about
a
few
times
previously
and
say
we.
If
we
stay
consistent
with
what
we
have
been
over
the
last
year,
I
think
we're
in
a
decent
position
to
do
that.
We
get
those
migrations
now
been
closed
down
and
we
should
be
running
largely
at
full
capacity,
so
hopefully
we'll
be
able
to
achieve.
D
B
C
A
D
How
good
I
would
I
would
just
say
what
one
more
thing
just
kind
of
second,
what
Liam
said
I
would
pretty
much
prefer
having
everything
in
done,
not
in
dev,
not
in
kind
of
like
middle
State,
but
I,
don't
know
to
me.
It
feels
like
we
should
definitely
take
a
little
bit
more
conservative
approach
and
be
happy
with
what
we
achieve
and
if
we
achieve
something
you
know
faster
than
than
we
planned,
and
we
can
always
bring
something
else
in.
But
to
me
it
feels
like
for
the
past
three
milestones.
D
We
I've
never
seen
most
achieving
everything
if
there's
always
a
carryover.
There's
always
something
I
feel
like
if
we
keep
keep
adding
things
in
while
we
have
eight
different
issues
in
there
F,
then
we're
just
going
to
we're
just
going
to
be
in
the
same
position
for
certain
you
know
so,
but
I
I
don't
know
all
the
exact
number
of
how
many
issues
we
should
pull
in
I'm.
Just
saying
that
we
should
be
probably
more
a
little
bit
more
concerned.
It's.
A
A
great
point,
I
think
that
so
I
agreed
that
we
should
go
for
that,
and
we
should
not
feel
like
we're
not
getting
things
done,
that
keeping
that
in
mind.
Just
from
my
perspective,
I,
never
considered
us
having
failed
a
milestone,
because
we
have
carryover
I'm
very
impressed
with
what
we
were
able
to
actually
get
done
with
the
previous
several
milestones,
and
the
fact
that
things
were
carried
over
did
not
kind
of
impact.
A
B
Because
I
was
going
to
suggest
as
that
same
thing,
Harris
we've
we've
been
able
to
achieve
19
or
20
issues.
Maybe
we
do
one
less
per
engineer,
so
maybe
we
scheduled
16
issues
for
this
milestone
to
kind
of
first
Georgio's.
Hopefully
reset
things
gets
into
a
position
where
we
won't
have
to
keep
looking
behind
and
I.
Don't,
obviously
you
can
be
in
a
position
where
you
have
a
couple
of
issues
up
your
sleeve.
If
we
are
asking
for
work
in
the
in
the
last
week
of
the
milestone,
okay,.
A
A
A
B
A
F
A
C
E
A
A
This
is
also
nice
just
having
a
cherry-pick
at
the
end,
that's
where
everybody
picks
something
they
want
to
work
on.
This
was
really
good,
so
the
two
choices
are
lack
of
state
parameter
and
github
and
github
project
importers,
gherkin
bypass
I
gotta,
have
any
context,
but
they
seem
to
be
ready
for
development.
So
you,
you
know
you
guys
have
probably
seen
this
and
the.
B
A
It
doesn't
seem
to
be
the
destination
destination
is
not
completed
there.
So
something
to
look
at
is
what
is
the
estimate
of
that?
It
could
have
been
a
mismatch
elated
so
we'll
see
about
that.
But
let's
just
move
this
one
in
because
that's
20
picked
anywhere.
That
seems
to
be
totally
ready,
including
the
estimate
so
George.
What
can
I
do
for
you?
A
D
God
no
I
just
wanted
to
ask
quickly
like
on
your
roadmap.
You've
been
discussing
the
start
of
the
the
full
solution
of
group
and
project
import,
export
and
I'm
just
wondering
because
the
start
of
that
is
certain
point
one
like
where,
where
is
that
we're
going
to
be
fitted
into
what
we
are
planning
right
now?
So.
D
Not
going
to
be
like
a
product,
UX,
design
or
whatnot
like
because
that's
that's
also
time
and
effort
that
we
will
have
to
put
in
in
terms
of
I,
don't
know
designing
the
solution
and
you
know
figuring,
are
figuring
out
what
we
actually
have
to
do,
because
UX
research
is
one
thing,
but
also
you
know
coming
up
with
the
solution,
also
something
that
takes
time.
Yeah.
A
The
refinements,
I
yeah,
this
refinement
is
something
we
should
take
into
account
like
as
a
general
like
above
the
line,
so
not
even
there's
eight
percent
of
time
that
we
spend
just
refining
future
things.
So
that's
that's
something
we
should
just
take
out
of
our
capacity
altogether.
But
to
answer
a
particular
question
and
I'm
and
and
I
will
try
to
push
this
issue
through
research
and
we're
gonna
be
looking
for
kind
of
larger
things,
but
also
we're
looking
for
NBC's
we're
looking
for
small
things
and
things
that
we
learn.
A
A
A
A
Thank
you
all
yeah,
so
clearly
having
having
to
two
issues
being
refined
in
this
Nene
is
not
conducive
to
it.
Running
short,
so
I
appreciate
everybody's
help
with
that
and
hope
we
can
improve
that
next
time
around.