►
From YouTube: NuPIC Sprint Planning - Mar 14, 2014
Description
Planning the next two weeks of work for the NuPIC open source project.
A
A
A
A
A
So
there's,
let's
move
on
to
this
str
error,
ignore
I
think
so.
This
is
ready
for
review
something
mark
put
in
it's
a
very
simple
change,
but
it's
a
c
change.
So
I
signed
this
to
scott.
Hopefully
he
has
a
few
minutes
to
to
do
a
review.
The
build
is
passing
on
it,
so
it
looks
good,
so
I'm
going
to
bump
that
whoops
not
pull
request.
A
A
So
I
don't
know
if
we're
gonna
be
able
to
attack
this
immediately,
but
we
might
have
to
establish
some
type
of
c,
plus
plus
only
testing
structure
before
we
can
get
those
running,
but
I
I
really
want
to
get
those
our
c
plus
plus
tests
running
in
nuke
core
build
on
travis.
So
that's
that's
important.
A
A
This
is
the
ticket
associated
with
the
full
request.
I
know
this
is
confusing,
but
I
can't
figure
out
any
other
way
to
do
it
and
we
we
eventually
want
to
make
sure
that
travis
publishes
builds
to
s3,
but
I'm
not.
I.
There
is
some
discussion
about
this
between
david
and
myself
and
exactly
what
we
want
published,
but
I
think
I'm
going
to
wait
on
that
until
the
build
is
actually
building
to
work
on
it,
because
I'm
sure
a
few
things
might
still
need
to
settle
down
a
bit.
A
A
A
A
I
think
austin
brought
this
up
the
vague
instructions.
Instructions
are
out
of
date,
so
I
think
this
is
important.
There's
still
people
trying
to
use
that
vagrant
build
so
I've
attached.
This
help
wanted
tag
to
it,
hoping
somebody
could
come
along.
Austin's
got
very
detailed
ticket
here,
describing
what's
not
working
and
what
needs
to
be
changed.
So
thanks
for
that,
maybe
we
can
get
a
volunteer
to
do
that
if
anyone's
watching
and
wants
to
get
a.
This
is
really
kind
of
a
newbie
task
as
well,
so
feel
free.
Oh,
that
didn't
work
newbie
apply.
A
So
that's
the
only
issue
that
I've
already
got
in
18
the
next
sprint.
Okay,
so
we
tell
you,
you
are
currently
working
on
this
updating
swarming
parameters
and
there
is
an
associated
ticket
immediately
beside
it.
I
think
there's
a
build
failure,
but
you
just
need
a
little
time
to
look
into
it
right.
Yeah,.
B
A
So
we
will
get
that
in
there.
This
is
the
pr
that
I
started
to
on
new
pic
to
update
the
dupic
core
shaw
for
the
sub
module
just
to
kick
that
off.
So
david
could
work
on
that
on
that
fork.
I've
got
some
open
questions
on
on
one
of
the
tickets
for
david
about
where
he's
actually
doing
his
work,
I'm
trying
I
want
to
try
and
keep
all
the
work
out
in
the
open.
A
A
A
There
we
go
pull
that
in
kevin
is
currently
working
on
this
example,
a
spatial
pulling
example,
and
there
is
a
ticket
associated
with
this
here.
It
is
simple,
tutorial
app.
I
changed
this.
It
used
to
say
simple
tutorial,
but
since
kevin
is
building
an
app,
not
necessarily
a
tutorial,
I
I
added
the
word
app
in
there.
We
may
want
to
write
up
a
wiki
page
that
goes
along
with
it,
or
at
least
a
detailed
readme,
which
would
probably
be
even
better.
So
that
is
continuing
work.
B
A
B
A
Of
that,
okay,
I'm
probably
going
to
de-prioritize
it,
at
least
for
now,
and
maybe
we
can
attach
it
to
that
summer
of
new
pic
project,
so
there's
still
a
p.
I
think
this
is
a
ticket
with
an
associated
pr
from
mark,
and
this
pr
is,
I
think,
it's
ready
for
review
or
there's
a
build
failure.
I
can't
remember
yeah
so
there's
a
build
failure.
Last
status
as
I
was
asking
mark
for
an
update
on
it.
A
B
Yeah,
that's
still,
we
should
still
discuss
that
piece
of
it,
the
reconstruction,
the
code
that
I
had
originally
so
it
was
okay
to
remove
it's
actually
not
being
used
anywhere
and
it's
not
tested
anywhere,
and
it's
probably
broken.
So
I
I
think
it's
okay
to
remove
the
unused
reconstruction
code.
That's
a
separate
thing
from
discussing
whether
we
want
to
put
reconstruction
in
the
pic,
but
I
hope
you
can
use
the
existing
code
to
do
it.
It's
just.
A
B
No
no,
but
the
removal
of
I,
I
guess
what
I'm
saying
the
removal
of
reconstruction
is
a
cleanup
task,
because
there's
just
a
few
code
snippets,
not
the
full
thing,
that's
left
in
there.
It's
not
used
in
any
way
and
hasn't
been
used
in
two
years,
so
that
piece
of
it,
I
think
is,
is
it's
reconstruction
related?
But
it's
a
cleanup.
B
A
Okay,
so
if
there's,
if
there's
some
disambiguation
that
needs
to
go
on
within
this,
maybe
we
can
chat
about
that
outside
the
meeting.
Okay,
in
the
meantime,
I'll
pull
it
in
these
next
two.
This
is
a
bug
that
I
think
that
ian
brought
up
with.
Actually
he
brought
up
a
pull
request
that
fixed
it
and
we
created
a
bug.
A
So
that's
ongoing
work
use
the
new
core
build
system.
That's
something
david
is
working
on.
That's
the
pr
or
that's
the
the
work
that
I'm
trying
to
get
visibility
on
and
as
well
implement
new
directory
structure,
documentation
of
the
directory
structure,
and
this
was
the
pr
about
the
cla
model
that
we
were
just
talking
about.
So
I
think
all
this
stuff
is
decent
to
pull
into
the
next
screen
and
at
least
attempt
to
tackle
okay,
closing
out
17,
so
here's
our
sprint
18..
A
So
I
think
that
looks
good
to
me.
We
have
a
bunch
of
little
projects
that
I
just
want
to
run
through,
because
I
know
people
like
jeff
full
have
been
helping
me
out
a
lot
with
some
of
the
tooling
stuff
and
the
website.
So
if
anybody
else
wants
to
get
involved
in
satellite
projects
of
new
pick,
that
would
be
fine
with
me.
A
A
I
don't
know
if
this
is
the
best
way
to
do
this,
but
I've
got
all
of
these
different
projects
have
their
own
milestones
and
everything.
So
it's
kind
of
a
pain
for
me,
but
so,
but
now
we're
in
newpick
tools.
So
this
is
our
tooling
server
and
we've
got
this
problem
where
statuses
are
when
there
is
a
failure,
it
seems
like
this
only
happens
during
revalidation
of
shaw's
of
other
shaws
after
pr
is
merged,
and
it
gives
you
this
like
recursive
status.
A
I
I
don't
know
how
this
is
happening,
but
I
have
some
notes
in
here
about
what
I
think
might
be
happening.
So
that's
it's
an
annoying
issue.
It's
not
breaking
anything
but
I'd
like
to
see
it
fixed.
So
I'm
going
to
throw
it
into
the
sprint.
Maybe
jeff
will
have
time
to
do
it
that'd
be
great.
If
not,
I
might
have
find
time
to
do
it.
A
So
that's
the
only
thing
for
the
tooling
server
that
I
currently
have
our
wall
board.
There's
one
thing
I'd
like
to
see
that
I
haven't
put
much
thought
into
getting
and
it's
on
the
dev
tab.
It
would
be
really
cool
across
all
the
projects
that
the
tooling
server
is
monitoring
over
here
to
see
what
what
jobs
in
travis
are
currently
running.
A
A
It's
another
thing
that
anybody
you
feel
feel
free
to
grab.
If
you
got
wanna,
do
some
javascript
stuff,
that's
all
javascript!
Okay,
yeah!
That's
for
an
18
room!
Then
cerebral.
We
haven't
done
much
on
at
all,
but
someone
did
report
a
bug
that
they
couldn't
run
hot
gem
through
cerebro.
So
I
think
that's
a
valid
bug
and
I
know
at
least
a
few
people
have
got
it
running
and
are
have
actually
used
it.
A
So,
if
anybody's
interested
in
getting
into
that
code,
ian
has
expressed
interest,
but
I
don't
think
he
has
found
time
to
get
into
it.
So
it's
enough
just
another
low
hanging
fruit.
If
anybody
wants
to
get
involved
there,
it
is
okay,
so
I'm
glad
you're
here
austin.
I
wanted
to
talk
about
some
of
these
new
clinic
64
issues,
so
some
of
them
seem
simple,
like
the
remove
pill
from
the
repo,
but
but
I'm
not
quite
sure,
and
and
this
one,
the
python
three
one
looks
pretty
easy.
A
C
A
A
B
B
A
Let's
do
that
this
is
holding
it
up,
yeah,
okay,
so
I
just
added
that
to
this
sprint,
so
it
doesn't
fall
out
of
scope,
and
that
is
the
complete
ticket
review
and
so
in
retrospective.
For
this
sprint,
I
I
have
been
rather
busy
doing
non-code
stuff,
there's
been
a
lot
of
event.
Things
coming
up
and
the
season
of
new
pick
was
a
lot
of
work,
so
I
haven't
been
as
gage
in
as
engaged,
I
think
and
and
kind
of
pushing
people
and
asking
to
do
things,
etc.
A
So
I'm
going
to
try
and
improve
that
on
my
next
sprint
and
one
thing
I
noticed,
I
don't
think
I
need
to
share
my
screen
anymore.
One
thing
I
noticed
is
that
I
need
to
scrub
the
tickets
before
the
sprint
planning
meeting
at
least
a
day
in
advance,
because
it
always
ends
up
sending
a
bunch
of
messages
to
people
and
they
especially
mark
or
david
somebody,
oversees
they're,
not
gonna,
have
time
to
respond
before
the
sprint
planning
meeting.
So
that's
just
an
action
item
for
me
in
retrospective.
A
B
A
Yeah,
it
might
be
good
to,
I
think,
david's,
still
kind
of
new
to
git
and
github
and
git
and
github,
or
both
both
have
sort
of
separate
learning
curves
as
well,
so
it'd
be
nice
to
find
a
decent
tutorial
just
on
from
an
outsider's
perspective
on
getting
introduced
to
git
and
github,
because
I
I
noticed
some
things
that
david
does
that
are
sort
of
non-standard
and
I'd
like
to
give
them
some
resources
to
come
up
yeah.
You
know
just
kind.
B
Of
our
cheat
sheet
of
the
common
things,
you
should
do
like
just
how
you
fork-
and
this
is
how
you
set
up
your
upstream
and
your
origin,
and
you
know
this
is
how
you
push
to
a
pull
request
is
how
you
push
from
change
again
to
a
pull
request.
You
know
just
a
few
common
steps
because
kind
of
understanding,
git
is
a
big
thing
and
even
the
existing
tutorials
may
not.