►
From YouTube: NuPIC Sprint Planning - November 8, 2013
Description
NuPIC Sprint Planning - November 8, 2013
C
D
A
A
A
Alright,
so
we
are
in
we're
closing
out
sprint.
Eight
right
now,
I've
already
started
a
sprint
nine.
So
let's
take
a
look
at
the
issues
and
github
done
pretty
well,
seven
closed
issues
and
still
for
open
one
of
them
is
the
C
make
issues.
David
said
he
has
no
time
to
work
on.
It
is
working
on
a
school
project,
but
he
said
next
week.
He
would
try
to
get
back
onto
it,
so
we're
going
to
move
that
one
into
the
next
sprint
because
he
should
be
able
to
work
on
it
soon.
A
Tsumetai
is
currently
actively
working
on
moving
new
SP
implementation.
Moving
to
the
new
SP
implementation
and
he's
found
some
some
issues
that
he
wants
to
make
sure
we
have
test
coverage
for
re
is
just
today
opened
a
pull
request
for
armed
b7
support,
so
we
made
a
ticket
for
that
and
this
is
actually
fixed.
So
let
me
move.
We
move
these
into
the
next
sprint
and
this
guy
I'm
going
to
close
exhaustion
and
let's
go
to
the
milestones
and
close
the
sprint,
and
I
go
spread
night,
okay.
A
So
a
quick
review
of
these.
This
first
task
is
one
for
me.
The
tooling
server
is
doing
something
weird
with
statuses
that
I
noticed
today.
I
will
look
into
that.
I'm
not
sure
about
about
this
one.
If
we
should
do
it
immediately
or
not,
but
we
have
this
prediction
or
framework
/
prediction:
folder,
that's
an
old
old
code,
that's
not
being
used,
there's
an
associated
gira
with
this,
where
this
originally
came
from
and
we'd
like
to
get
rid
of
this
entirely.
A
However,
there
are
currently
tests
that
rely
on
this,
this
old
framework
being
there,
so
it
tests
the
core
algorithms
through
this
old
framework,
we'd
like
to
get
rid
of
this
currently
Vitali
is
assigned
I'm,
really
not
sure.
If
he's
going
to
be
able
to
work
on
this,
the
Sprint
or
not,
but
I'm
I'm
thinking
about
just
keeping
it
there
and
asking
him
about
it,
and
maybe
he'll
have
some
time,
but
that
would
be
nice.
It's
just
kind
of
a
code
cleanup
task,
the
ok
update,
dev,
workflow
and
process
docs.
That's
that's
my
job.
A
Basically,
we're
using
new
github
issues
and
I
have
not
updated
the
wikis
to
reflect
that,
and
I
probably
want
to
kind
of
better
establish
our
in
any
any
processes
that
that
touched.
The
issue
tracker
anywhere
that
I've
written
up
any
process
stuff
about
jira.
I
need
to
replace
how
we're
using
github
issues
and
I
also
kind
of
need
to
establish
a
standard
for
how
we're
using
github
issues
with
who
boards.
So
new
people
can
come
in
and
understand
how
we're
doing
it,
even
though
I'm
still
sort
of
figuring
it
out
myself.
A
So
these
are
the
ones
that
we
just
moved
over.
Scott
is
not
going
to
be
able
to
work
on
anything.
This
sprint
is
fully
engaged
on
Brock
issues.
However,
this
is
a
pretty
low
hanging
item
that
somebody
brought
up
at
the
hackathon.
I
think
it
was
it
was
you
Matt
yeah,
so
there's
just
a
couple
of
lines
here
in
the
clean
bill
that
we
probably
don't
need
anymore.
It
actually
is
kind
of
detrimental
if
they're
there,
because
it
removes
stuff
that
we
don't
want
to
remove
so
hey
Matt.
How
about
you
take
this.
C
F
A
C
A
Oh
and
thank
you
Jeff
for
volunteering
to
help
establish
a
community
managed
VM.
Please
keep
me
updated
on
any
progress.
You
can
just
email
the
list
if
you
want,
if
you
have
anything
you
want
to
talk
directly
to
me
or
you
want
some
guidance
on
feel
free
to
email
me
come
and
let's,
let's
I
think
these
are
all
valid
to
be
in
the
current
sprint.
Let's
take
a
look
at
the
backlog
of
items
and
see
if
there's
anything
important,
all
your
most.
F
F
A
A
A
F
D
F
B
A
F
A
A
E
A
D
A
F
A
B
A
A
But
it's
sort
of
like
some
tasks.
So
if
you
have
like
an
overarching
issue-
and
you
got
several
pr's
the
knots
and
they
all
link
back
up
to
that
one-
it's
sort
of
okay
I'm
not
going
to
lose
any
sleep
about
it
at
this
point,
but
ok,
this
was
you're
going
to
sort
by
newest
resolution
on
unsigned
or
than
zero
checks.
A
A
A
A
And
when
use
parameters
just
got
a
PR.
This
looks
somewhat.
This
is
the
same
PR
he's
referring
to
superior
and
I'm
going
to
leave
that
out
for
now
feast
a
few
starts
working
on
these
I'll
pull
them
in.
How
did
these
are
marks
just
brainstorming
things
that
need
to
be
done?
Well,
these
are
PRS
substitute,
Graham,
opulent
variable.
E
A
E
A
E
A
A
A
E
A
A
Not
crazy
about
how
I
have
to
deal
with
labels
with
who
bored,
so
I'm
not
sure
if
we're
gonna
continue,
there's
still
kind
of
in
a
trial
period
here,
but
there
we
go
at
least
so
I,
don't
Austin!
You
don't
have
anything
I,
don't
know
how
busy
you're
going
to
be
this
coming
sprint,
but
feel
free
to
go
through
and
grab
any
issues.
A
So
basically,
if
you
have
cycles-
and
you
see
something
interesting-
you
want
to
work
on,
grab
it
anybody's
watching
and
just
try
and
try
and
label
it
if
you
can
so
that
it's
if
you're
working
on
it
put
it
in
to
going
to
show
you,
for
example,
put
it
into
a
current
milestone,
which
you
can
do
here,
where
it's
written
on
and
assign
it
to
yourself.
If
you
can't
assign
it
to
yourself.
Email
me
mad
at
newman
store
gal,
make
sure
that
you're
on
the
appropriate
team
list
for
new
menta.
A
A
Maybe
we
did
kind
of
rally
the
troops
and
attack
a
certain
thing,
so
everybody
can
sort
of
work
in
the
same
area,
but
I'm
not
wasn't
quite
afraid
to
do
that
for
this
coming
sprint
after
the
the
hackathon,
so
hopefully
after
the
screen
will
have
a
little
bit
more
time
to
work
on
new
pic
and
not
just
hackathon
and
brought
them
and
trying
to
sort
of
restore
some
order
to
our
to
our
plan
as
we
go
ahead
and
our
road
mount
them
all
that
stuff.
That
could.