►
From YouTube: NuPIC Sprint Planning - July 9, 2014
Description
Where we plan Sprint 26. http://status.numenta.org/issues.html#milestone=Sprint+26
A
A
B
A
Closed
issues,
that's
basically,
where
I
got
this,
so
there's
still
ongoing
work
on
the
pip
install
the
branch
that
they've
created,
I
I've
managed
to
get
it
installing
into
a
local
location
and
that
works
and
waiting
for
others
to
try
that
and
then,
as
soon
as
we
can
confirm
that
works
for
other
people,
I
think
we're
just
going
to
merge
that
and
take
any
of
the
other
issues
that
came
up
on
that
PR
and
turn
them
into
new
tickets
for
continued
work.
So
we
can
finally
get
that
key
are
merged.
A
Fergal
and
utensil.
Special
utensil
has
been
working
on
putting
in
place
a
c++
unit
test
framework,
which
is
I,
think
he's
decided
to
use
the
catch
framework,
which
is
c++
automated
tests
and
the
headers,
or
something
like
that.
It
stands
for
something
about
headers,
but
it's
better
than
you
tried.
Google
test
at
first.
A
A
A
A
Or
was
it
her?
You
know,
I,
don't
know
where
was
it
was
in
here
somewhere
see,
make
DNT
a
coven
abled
and
in
the
sea
make
a
file
he
had
to
add
something
for
covered
enabled,
but
yeah
I
was
dash
dash
coverage
for
it,
which
yeah
and
that's
too
obvious
for
the
word,
but
it
was.
He
commented
on
this
on
how
easy
it
was
to
do
this
very
simple,
sorry,
yeah.
C
C
A
I
imagine
I'm,
probably
archiving
the
binary
that
was
made
with
this,
so
the
binary
archive
in
using
in
the
regression
tests
we've
probably
slow
down,
but
that's
some
major
issue,
but
something
we
should
wonder
if
I
could
fix
later
so
anyway,
these
we
actually
have
coverage
reports.
Now
on
you
pick
or
forty
three
percent
coverage.
So
that's
cool
I
was
one
of
the
major
things
I
wanted
to
get
done,
which
is
nice
back
to
this
okay.
A
A
Hey
I
talked
about
the
core
coverage.
I
did
a
lot
of
work
on
the
tooling
server
in
preparation
for
some
major
work
that
will
come
later.
That
should
simplify
how
a
lot
of
our
pipeline
integration
works
out.
All
those
calls
out
to
the
shell
and
specs
get
to
be
installed
and
certain
repos
to
be
checked
out,
and
that's
all
very
messy.
So
I
did
a
lot
of
new
tooling
clean
up
I
updated
the
demented
adored
media
page,
which
was
pretty
pretty
messy.
A
So
I
think
I
have
that
organized
a
little
bit
better
now
and
it's
only
got
sort
of
professional
media,
not
necessarily
tutorials,
just
things
from
other
organizations
where
jeff
gives
a
presentation
or
jeff
has
interviewed,
and
things
like
that.
If
links
on
top
too,
if
you
want
videos
about
specific
details,
go
to
these
places,
I
also
did
a
little
work
on
some
of
our
satellite
repos.
A
Like
fluence,
we
added
a
travis,
build
and
unit
test
cook
and
then
one
of
our
interns
barrage
added
a
bunch
of
gear
tests,
which
was
nice
and
I,
updated,
pi
stuff
to
auto,
deploy
a
pipe
I.
Whenever
released
tag
was
pushed,
we
edited
a
new
repository.
That's
we'll
talk
about
in
our
next
open
office
hour
called
new
pic
geospatial.
We
may
change
the
name
of
that
and
just
got
that
up
and
running
with
a
Travis
build,
and
you
know
test
framework,
but
no
real
unit
tests
and
then
quite
a
few
bug
fixes.
A
A
We
really
want
to
get
this
fib,
installable
merged
I.
Think
we
can
do
that
soon
and
it's
it's
become
pretty
obvious
from
the
questions.
I've
been
getting
an
IRC
or
over
email
that
we
need
documentation
for
seal
a
model,
a
model
factory,
there's
a
lot
of
really
common
tasks
like
create
model
or
save
or
load
from
checkpoint
that
just
aren't
documented
anywhere
easily
found,
and
those
should
be
documented
in
our
API,
automated
API
dogs.
So
we've
got
some
tickets
for
that
and
someone
on
IRC
are.
It
is
third
with
nada,
so.
C
A
Utensil
will
be
continuing
to
work
on
unit
test
kind
of
moving
from
the
old
framework
to
the
catch
framework
and
he's
putting
together
a
wiki
with
instructions
on
how
to
create
those
types
of
tests.
It's
a
bit
of
a
behavior
driven
test
framework
if
you're
familiar
with
that,
there's
nothing
to
be
afraid
of
it's
pretty
easy
to
write
tests
that
way,
it's
just
a
different
way
of
defining
what
the
tests
are
testing.
A
So
we've
had
some
discussions
about
this
new
pic
insularis
integration,
so
we
might
get
some
more
traction
from
austin
to
to
work
on
that.
This
coming
spread,
which
would
be
good
and
I,
have
a
task
to
work
a
bit
on
the
on
the
wall
board
because
I
find
myself
using
certain
components
of
it
a
lot,
but
not
not
never
using
the
main
page
anymore,
because
it's
just
too
cluttered
over
it.
It's
not
useful
anymore,
so
I
wanted
to
just
clean
it
up
a
bit
and
then
start
working
on
regression
tests.
A
A
A
Maybe
so,
but
the
the
bad
thing
about
moving
to
another
CI
is
and
we're
already
totally
integrated
with
github
folks
and
travis's
hooks
and
stuff.
So
all
that
stuff
would
have
to
be
reworked
and
they're,
not
all
exactly
the
same.
Like
circle.
Ci
has
a
little
bit
different
web
interface
and
Travis
does
so
so
I
might
give
up
on
this
am
I
not.
A
Okay
to
oh
yeah,
implement
pure
temporal
memory,
which
is
currently
called
the
TP
plus
the
white
paper
description,
something
that
jayden
is
going
to
be
working
on.
So
we'll
definitely
move
that
over
the
new
pic
or
continuing
work
on
C++
unit
tests.
They
are
already
generating
a
clean,
install
reports
and
utensils
branch.
So
he's
well
on
his
way.
A
There
utensils,
also
looking
into
another
CI
option
for
dotnet,
builds
called
app
conveyor
that
we
may
be
able
to
kind
of
tag
on
to
our
current
build
process
or
pipeline
so
that
we
can
get
a
windows
build
at
some
point
in
the
future.
That's
not
necessarily
a
step
in
our
pipeline.
The
kind
of
an
additional
thing
may
be
attached
to
a
Windows
built
branch
or
something
like
that.
B
A
A
A
All
right,
simple,
yeah,
nuka
core
builds
on
Suarez
aside
to
austin
this
region
of
notation
factory
david
will
start
work
on
as
soon
as
we
get
a
tip
thing
merged
another.
This
is
the
same
with
in
the
same
boat
changes
the
region,
implementation
factory.
I
have
some
tasks
to
work
on
the
tooling
server,
nothing,
nothing
serious
and
then
for
the
this
nab,
which
is
nimitta
anomaly,
benchmarks,
I,
don't
know
what
the
status
of
this
ticket
is
ian
created.
I,
don't
actually
know
what
it
means,
the
man
we
need
to
builds
and
to
prepare
them.
A
That's
going
to
be
a
little
bit
hard
to
do
in
an
automated
fashion,
so
I'll,
try
and
catch
up
with
Guillen
on
this
and
see
if
it's
something
he
really
thinks
is
important
to
do
or
not,
because
it's
probably
gonna
take
a
bit
of
work
and
then
there's
these
kind
of
dangling
linux,
64
and
darling,
64
issues
aust
and
that's.
If
those
aren't
priorities,
I
think
we
should
just
pull
it
off
to
the
backlog.
If
you
I'd
rather
see
you
work
on
the
Salar
stuff.
C
A
A
Ok,
not
a
lot
of
issues
got
left,
we're
doing
pretty
good
cleaning
up
our
issues.
We
used
to
have
a
lot
more
issues
and
our
open
PRS
are
much
much
much
less
open.
Be
ours
I'm,
not
sure
why
they're
open,
oh
I,
just
move
those
over,
so
there's
only
seven
open
PRS
that
aren't
in
the
backlog.
If
this
one
is
brand
new,
this
one's
been
around
for
a
while
and
I'm
still
waiting
on
on
mark
to
work
on
it.
A
A
A
A
C
C
A
A
So
I
am
just
slowly
moving
these
and
this
one
I'm
going
to
pull
off
onto
the
backlog
for
now
e
/,
so
that
should
be,
should
now
have
we're
25,
empty
and
all
of
our
steps
of
beans
for
twenty-six
thirty-eight,
open
issues
and
spread
26,
so
I
might
run
through
here
offline
and
print.
Some
of
these
down
that
I
know
we
aren't
going
to
get
to
or
letter
fold
or
need
to
be
updated
and
paying
people
on
what
should
be
done
on
them.
But
I
don't
want
to
do
that
while
we're
all
sitting
here.
C
A
Okay,
what
else
do
we
have
here?
So
I
think
that's
good
said:
23
new
pic
issues,
a
look
at
the
assignments
most
most
of
the
stuff
assigned
to
me
is
to
look
tooling
things,
five
out
of
signed
issues.
So,
if
anybody's
watching
once
some
work
got
several
these
couple
of
newbie
tasks,
one
says
another.
This
has
helped
wanted
I
think
as
soon
as
we
merged
hit
install
what
we
could
get
rid
of
that
it
knows.
Yeah.
A
B
A
Okay,
so
I
think
I
am
halfway
tracking
them
they're,
not
a
part
of
this
board
hear
a
thing
if
I
remember
correctly,
all
got
a
fluent
from
the
server
got
to
your
spatial.
I
could
easily
adds
three
grocery
go
to
hear,
but
I
wanted
to
talk
to
Chayton
and
make
sure
that
that's
where
he
wanted
to
track
the
issues,
but
it
makes
sense
if
anybody
in
the
open
source
community
is
going
to
be
working
on
them.
They
should
probably
be
tracked
where
they
can
be
saved.
Yeah.
B
A
Then
account
you
probably
live
here,
I
think
that's
probably
the
right
thing
to
do
yeah.
So
what
I
want
to
put
that
on
my
list?
Things
do
doesn't
really
fit
anywhere.
So
I'm
just
going
to
take
a
note.
So
it's
easy
to
get
those
incorporated
into
this
issue.
Tracker
thing
here.
So
actually
one
of
the
one
of
the
issues
that
I
have
is
to.
A
Think
it's
on
this
one
establish
a
process
for
adding
to
refuse
and
repose
into
the
new
pic
fold,
which
includes
kind
of
a
central
list
of
all
the
repositories
that
are,
we
should
be
tracking
so
once
I
get
this
in
place,
it'll
be
easy,
just
to
add
it
to
that
list
and
make
sure
that
the
tooling
server
is
monitoring
it.
The
status
board
is
monitoring.
It.