►
From YouTube: NuPIC Sprint Planning - Apr 11, 2014
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
B
B
B
So
I'm
not
going
to
jump
directly
into
this
to
trying
to
get
these
api
tests
in
place,
for
example,
that's
one
of
the
big
ones
and
then
and
try
and
start
working
on
consolidating
algorithms
that
there's
a
lot
of
work
there
and
I
want
to
take
the
sprint
to
to
kind
of
a
regroup.
So
there
is
still
no
lack
of
work
that
needs
to
be
done
so,
switching
over
to
the
current
sprint,
we've
got
about
the
same
amount
of
open
and
closed
issues,
but
a
good
amount
of
work.
B
I've
done
a
lot
of
issues
got
closed.
This
this
print
I'm
not
going
to
go
through
them
all,
but
a
lot
of
activity,
especially
from
David
it
once
again
mark
and
we've
had
a
new
contributor
named
utensil
song
who's
been
helping
out
so
is
also
much
appreciated
on
our
open
issues.
A
lot
of
these
have
currently
a
lot
of
discussion
going
on
either
on
the
issuer
on
the
mailing
list,
so
I'm
not
going
to
dive
in
deeply
into
any
of
them.
B
B
We're
also
discussing
this
NTA
x,
developer,
build
and
that's
actual
real
bug
that
needs
to
be
fixed.
I've
marked.
That
is
important
if
nobody
picks
that
up
I'm
going
to
try
and
tackle
it,
but
I'm
not
really
sure
what
I'm
doing
there.
So
if
anybody
with
better
knowledge
of
what
this
error
is
wants
to
jump
in,
that
would
be
awesome.
B
I'm
working
on
a
tutorial.
This
is
the
PR
there's
a
ticket
down
somewhere
else.
That's
basically
just
as
improve
dodjem
tutorial
I've
been
putting
in
a
lot
of
work
on
that
the
past
day.
Hope
to
have
something
by
the
end
of
the
sprint
that
I
can
publish
so
I'm
going
to
leave
that
in
the
sprint.
I'm,
not
sure
if
this
is
valid
or
not
I.
Just
asked
a
question:
this
is
something
that
utensil
opened.
B
B
There's
one
assigned
to
Alan
about
the
docker
wiki:
that's
the
doctor
so
probably
needs
some
TLC.
We
removed
our
new,
our
repository
for
since
it's
all
on
her
I,
oh
now,
but
there's
still
an
issue
with
sub
modules
there
that
they
can't
handle
the
sub-module
ish
and
our
build.
So
that's
a
problem
with
with
docker
but
they're.
B
Following
up
with
me
on
that
they're
in
the
process
of
fixing,
it
apparently
see
create
a
ce
mec
test
target
that
runs
python
tests,
I,
don't
I,
don't
know
if
that's
a
valid
ticket
anymore,
yeah
I,
don't
think
this
is
a
that.
This
was
actually
already
been
done
and
has
already
been
discussed
a
lot.
So
I
think
this
is
probably
obsolete
to
get.
B
We
still
have
the
original
test.
Runner.
How
that's
going
to
work
out
in
the
future
again
is
something
that's
a
topic
that's
being
discussed
in
in
the
mailing
list.
Okay,
chetan
you're
still
tagged
on
this
vector
encoder
thing:
vagrant
instructions
are
out
of
date.
There's
a
lot
of
details
on
this.
I'm
still
looking
for
someone
to
help
with
it.
B
B
This
issue
has
an
Associated.
This
collected
a
connected
permanent
sting,
has
an
Associated
pull
request
with
it
somewhere
here
right
underneath
of
it
that
I
created,
but
it
needs
the
unit
test.
It
Pat
the
bill
passes
I,
think
it
works,
but
I'd
really
like
to
try
and
get
it
unit
tested
and
I.
Don't
know
what
I'm
doing
writing
this
unit
test.
I
can't
figure
out
where
to
put
it.
If
I
had
some
extra
time,
I
could
probably
jump
into
it.
B
But
if
anybody
is
familiar
with
Python
unit
testing
and
we'd
like
to
to
jump
in
its
a
probably,
you
have
to
have
a
bit
of
knowledge,
I
think
of
the
with
the
spatial
pooler,
but
there's
already
tests
in
place
there.
So
it
might
be
a
good
opportunity
to
learn
a
little
bit
more
about
how
it
works
and
about
what
our
current
coverage
is
like.
So
looking
for
out
there,
another
thing
about
the
docker
like
like
I
mentioned,
have
already
removed
the
demented
dr.
new
pic
project
because
it's
being
hosted
now
in
dr.
B
I,
oh,
but
there's
there's
still
this
issue.
We
can't
create
a
trusted
build
in
the
index
because
of
the
sub-module
issue,
so
I'm
assigned
to
that
to
follow
up
once
they
tell
me
that
that
issue
is
fixed
use,
the
new
pic
or
build
system.
I
think
this
is
closed.
All
right,
I
think
that
that's
probably
done
yeah
I
think
this
is
just
a
relic.
B
Okay,
those
I
imagine
I
was
a
duplicate
tickets,
so
so
that
is
it
I'm
working
on
the
hot
gym
example,
oh
yeah,
here
we
go
to
implement
new
directory
structure
for
new
pic
I.
Don't
think
this
is
a
huge
pressing
issue
at
the
moment.
I
don't
know
if
anyone
has
any
strong
opinions
about
that,
but
I'm
a
since
we,
since
the
builds
are,
are
working
and
running
right
now,
I'm
going
to
take
this
out
of
the
next
sprint.
I'd
rather
focus
on
something
else.
B
A
B
That's
my
opinion
to
if,
if
we
make
it
a
priority
to
support
PIP,
which
we've
always
wanted
to
do,
I
think
that
would
be
a
great
initiative.
Then
the
directory
structures
would
kind
of
be
a
subtopic
of
that
discussion.
I'm
pretty
sure.
That's
not
one
for
the
next
sprint,
yeah
I,
don't
think
so
either.
B
C
B
A
B
B
Okay,
let
me
just
do
a
quick
check
and
show
you
what's
currently
in
sprint:
20,
which
is
our
upcoming
sprint
I've,
as
I've
come
up
with
some
issues
during
the
past,
spread
that
I
know
I
want
to
do
I've
dumped
them
in
here.
So
a
few
of
these
are
already
here
some
of
the
most
of
documentation,
tasks
that
I
no
need
to
happen.
B
So
that's
what
exists
and
all
of
the
rest
of
these
issues.
We
will
push
to
spread
20
and,
like
I,
said
in
the
past,
although
it's
it
seems
odd
to
have
so
many
unfinished
issues
in
each
sprint,
because
we're
open
source
and
we're
looking
for
volunteers,
I
like
to
have
the
categorization
of
the
moat.
What
I
think
are
the
most
important
things
to
be
done,
even
if
they're
not
designed
that
I
don't
know
if
you're
going
to
get
done
or
not
in
the
current
sprint,
so
the
Sun
was
looking
for
work.
B
They
can
come
pick
something
up
out
of
the
current
sprint.
That's
not
assigned
all
right,
so
this
is
new.
Pic
I've
got
23
open
issues
and
that's
what
our
next
sprint
looks
like.
So
it's
really
there's
not
a
lot
of
focus
on
the
sprint.
It's
kind
of
cleanup
of
tickets
that
were
either
opened
as
a
result
of
work.
B
That's
been
done
recently
things
we
need
to
just
get
a
better
handle
on,
and
I'm
going
to
use,
I'm
going
to
take
the
opportunity
on
the
sprint
to
kind
of
try
and
plan
out
as
the
direction
for
the
upcoming
core
extraction
task,
which
is
trying
to
put
some
api
tests
into
place.
That's
going
to
be
a
bit
of
an
administrative
work
on
my
part.
B
New
pit
core
is
a
lot
less
busy.
Let's
pick
spread
19,
we
do
have
16
issues,
clothes
new,
pic
or
I
don't
think
it
was.
There
was
anything
very
major
going
on
here.
There
was
some
support
for
the
independent
build
stuff
that
david
was
doing,
did
close
all
the
tickets
that
make
sure
the
tests
were
running
and
passing
and
travis.
B
The
current
open
tickets
is
to
configure
a
code
scan
for
Coverity.
I
don't
know
if
that's
going
to
happen
or
not,
but
I
think
it
would
be
great
if
any
parents
just
in
doing
that
as
an
Italian
yeah.
So
it's
how
they
volunteered
to
do
that
he's
a
rock
engineer,
so
he
seems
to
have
some
experience
with
Coverity
and
we've
got
this
issue
of
missing
dependency
checks
that
there's
a
discussion
about
this
between
David
utensil
and
Mark.
B
So
I
think
that's
a
valid
issue
this
other.
This
is
like
a
sister
issue
of
the
connected
permanence
one
in
new
pic
because
the
algorithms
are
in
C
as
well
as
Python.
So
it's
the
exact
same
issue,
the
exact
same
situation.
I've
got
to
fix
in
place,
but
it
needs
unit
tests
and
this
one's
even
worse
off,
because
they're
C++
unit
tests
and
I
I,
don't
know.
I
know
enough
c++
to
switch
and
greater
than
or
equals
to
than
a
greater
than,
and
that
was
the
fix
for
this
bug.
So.
B
So
it
still
needs
someone
to
help
with
this.
You
do
remember:
Gary
compilat,
no
one,
that's
Africa
pile!
That's
crazy!
Run
that
new
pic
or
build
and
test
sand
trap.
Let's
see,
I
think
that's
taken
care
of
I.
Don't
think
we
need
that
one
anymore.
Okay,
so
all
the
rest,
we're
dumping
over
to
sprint,
20
and
I,
don't
think
spread.
B
20
had
anything
in
it
in
the
first
place,
so
yeah
not
a
whole
lot
of
of
stuff
in
Newport
core,
but
a
lot
of
cleanup
work,
bug,
fixes,
build
issues
and
new
pic
that
need
to
be
worked
on
so
are
looking
for
Python
people.
If
anybody's
watching
you
want
to
get
involved,
especially
if
you
got
a
little
sea
background
or
a
little
make
background.
That
would
be
awesome.
B
Okay,
other
than
in
these
issues.
Let's
see
I
wanted
to
look
at.
There
are
a
couple
of
things:
I
wanted
to
throw
out
there.
If
anybody
is
interested
in
working
on
some
of
our
tooling
or
satellite
projects,
or
just
going
to
secure
my
screen
once
again
on
the
let's
see
ya,
then
I
meant
2.org
website
there's.
This
is
something
that
I
was
hoping
Jeff
get
out
both.
B
This
overlapping
texts
same
deal,
I,
think
I
showed
this
to
you
in
the
last
sprint
looks,
looks
ugly
when
it
gets
squished
together.
That's
that's
the
issue,
so
I'm
just
throwing
these
over
into
the
next
sprint
at
the
other,
the
other
one
is
one
of
them,
both
the
other
ones.
I
will
probably
end
up
taking
care
of
and
that
those
are
just
media
page
updates.
So
that's
limited
org,
the
tooling
server.
I
believe
I
do
have
some
issue.
I
wanted
to
get
fixed
Oh
something
came
up,
but
it
actually
wasn't
an
issue.
B
Oh
this
was
it
so
someone
was
asking
about.
Maybe
this
doesn't
really
topic
for
sprint
planning,
but
there's
been
some
discussion
and
I
might
bring
this
up
on
the
mailing
list
about
how
to
deal
with
this
sub
module
dependency.
Every
time
there
is
a
merge
to
do
the
core
master.
Someone
had
the
idea
that
we
should
have
some
tooling
in
place
to
create
a
PR.
B
That
will
update
this,
the
Shah
of
the
sub-module
to
point
to
the
new
one,
and
so
we
can
at
least
run
Travis
Travis
build
over
it
I
think
that's
a
good
idea!
So
I
made
a
ticket
for
it.
I
don't
know
if
that's
exactly
what
we
want
to
do,
but
even
if
we
end
up
not
not
using
it,
I
would
love
to
see
that
you
know
and
someone
merges
to
master
that
everything
works
with
new
pic.
B
So
I'm,
probably
going
to
move
this
to
the
next
sprint
I
haven't
assigned
to
me,
but
I'm
going
to
unassign
it
because
I
don't.
I
don't
care
who
works
on
it,
and
I
really
don't
know
if
I'm
going
to
have
time
to
work
on
it.
But
this
is
a
JavaScript,
tooling
server.
So,
let's
see
this
is
a
bug
that
I
that
I
found
in
the
tooling
server
that
I
see.
B
It's
probably
going
to
be
hard
to
debug,
but
and
there's
this
other
one
which
is
really
hard
to
explain,
but
that's
why
I
haven't
assigned
to
me,
but
it's
about
validators
whenever
it
gets
to
get
hook
so
I'm
going
to
leave
these
in
sprint
20
and
if
I
have
time
to
pick
these
up.
I'll
try
they're,
not
huge
huge
here
to
the
important
issues
they're
just
so
you
know
sort
of
small
painful
things
that
usually
that
I
just
noticed
you
can
assign
this
to
me.
Man,
if
you
want
absolutely
all
of
them,
I,
don't.
B
How
it,
let's
see
I'll,
give
you
this
one,
because
there
is
a
test
in
place
for
this
and
it's
passing,
but
in
production
it
it's
not
so
there's
something
wrong.
There
obviously,
and
you've
you've
put
some
other
tests
in
place.
So
maybe
that's
a
good
candidate
and
you
know,
ask
questions
on
sticking,
aww,
hope,
y'all,
okay,
other
stuff,
nothing
really
important,
I!
Think
going
on
with
our
status
board
yeah
this
year.
This
is
like
a
nice
to
have
would
love
to
have
some
time,
but
other
than
that,
let
me
look
through
my
issues.
B
A
A
B
B
There's
there's
some
open
tickets
on
the
on
the
fluent
repos,
if
anybody's
interested
in
working
on
fluent,
but
that's
about
it
other
than
that
that
that's
the
whole
sprint
planning.
So
just
to
recap,
most
of
the
work
is
going
to
be
a
new
pic,
build
build
issues
clean
up
that
sort
of
stuff
and
then,
during
this
brand
I'm
going
to
be
planning
for
the
next
one.