►
From YouTube: NuPIC Sprint Planning - Sep 5, 2014
Description
Planning sprint 30.
A
I
think
these
are
all
over
all
open,
vrs,
there's,
there's
one
in
the
backlog
that
I'm
waiting
for
a
mark
to
look
at,
but
other
than
that
none
of
these
are
too
old,
except
for
this
anomaly,
modular
pr
which
mark
says,
is
ready
once
again
for
review.
I
signed
that
to
scott,
I
believe,
to
take
a
look
at
it's,
not
a
huge
pr,
but
there's
some
there's.
There
are
changes.
It
doesn't
touch
a
whole
lot
of
files.
A
A
So
you
know
our
his
historically.
I
think
we're
still
doing
pretty
well
on
keeping
or
closing
prs
pretty
quickly.
So
there's
you
know
six
open,
but
that's
not
awful.
I
don't
think
so
all
right.
Let's
look
at
issues
in
sprint
29.
This
is
this.
Is
the
sprint
we're
closing
out
I'm
not
going
to
talk
about
the
priorities
right
now.
A
A
You've
closed
all
your
issues
for
the
current
sprint,
so
that's
good
david's,
not
online,
but
I
did
want
to
go
over
he's
got
a
couple
issues
one
is
is
renaming
some
files,
which
I'm
pretty
certain
he's
not
going
to
have
time
to
do
so,
I'm
going
to
pull
that
off
to
the
backlog,
the
other
one,
which
is
the
implementation
factory,
move
regional
factory,
move.
I've
still
got
that
marked
as
a
higher
priority.
So
I
would
like
to
keep
this
one
in
and
move
it
to
sprint
30..
A
I
don't
remember
this
guy's
name,
sorry,
but
he
was
working
on
some
documentation
tasks,
so
I
think
he
doesn't.
I
don't
think
there
are
pr's
open
for
these.
Are
there
no,
but
one
was
to
write
a
little
doc
string,
checker
like
a
utility
for
development
to
make
sure
that
python
source
files
have
docked
strings
and
then
just
adding
more
documentation
to
cla
model.
A
This
is
jay
has
an
issue
for
documentation
updates.
This
is
a
pr
that
I
think
is
ready
to
merge,
but
no
other
open
issues,
so
subutai
added
your
ticket
to
move
the
private
research
code
into
the
newpic.research
repo.
So
that's
already
in
sprint,
30.!
Okay,
thank
you.
These
other
tickets
are
just
sitting
in
the
backlog.
So
if
you
need
something
to
do,
you
can
grab
one
of
those.
I
think
that
you
reported
these
two
okay
to
utensil.
A
So
he's
still
assigned
a
couple
of
things
and
he
has
been
working
on
getting
a
windows
build
working,
so
they're
still
actually
continuing
to
work
on
that
build
support
for
windows,
which
is
nice
so
we'll
see
how
that
goes.
They've
got
some
stuff
working,
but
there's
still
more
progress
to
make
scott
purdy.
Let's
look
at
just
spread
29,
so
you
still
are
assigned
several
tickets
and
let's
run
through
them
real,
quick
and
make
sure
that
those
are
still
things
you
plan
on
working
on
the
coming
sprint.
A
A
Forgot
about
that,
okay,
so
I'll,
just
probably
pop
these
over
into
sprint
30.,
I
won't
make
you
watch
me,
do
that
right
now,
one
by
one
brad
probably
isn't
here,
but
he
has
taken
on
a
few
issues
here
and
there,
which
is
nice.
He
asked
me
to
give
him
a
couple
things
for
him
to
work
on
in
his
in
his
free
time.
A
So
I've
got
him
a
a
couple
of
small
issues
assigned.
He
can
grab
those
if
he
has
time
I'll,
probably
move
this
this
one
over.
It's
just
one,
one
for
the
wall
board
that
annoys
me
that
he
could
probably
help
with
jeff
thanks
for
attending,
but
you
you.
Let
me
know
that
you're,
probably
not
gonna,
have
much
time
to
work
over
the
next
sprint.
So
I'll
I'll,
probably
just
move
this
one
to
the
backline
yeah.
A
A
A
A
Okay,
that
makes
sense
if
you
identify
specific
refactorings,
that
should
be
done.
Would
you
create
tickets
for
them?
Yes,
thank
you.
Okay,
I'm
gonna
pull
this
out
on
the
backlog
again,
then,
for
now
and
as
you
identify
new
tickets,
just
go
ahead
and
create
them
and
and
then
assign
them
to
yourself
and
put
them
in
the
right
sprint.
A
A
My
issues,
I've
got
a
bunch
of
stuff,
and
these
are
all
backlogs:
let's
filter
some
web
content,
there's
there's
a
couple
of
old
bugs,
like
this
problem,
running
python
unit
test
that
I'm
just
I'm
just
stuck
on.
I
think
this
is
a
32-bit
problem,
but
I'm
not
certain
I'm
I
I'll
probably
this
is
I've
been
skipping
this
along
from
sprint
to
sprint
and
not
making
much
progress
on
it,
but
no,
no
one
is
really
complaining
at
the
moment.
A
I've
got
some
this
a
wiki
bug
or
what
wikia
enhancement
to
make
I'm
still
planning
on
making
this
tertiary
osx
build
process.
Although
I'm
blocked
on
that,
because
travis
has
put
me
on
a
waitlist,
apparently
the
osx
build
feature
has
become
popular
enough,
that
it's
not
immediately
accessible
to
people
who
request
it
this.
This
issue
for
newpic
tools
is
really
annoying
and
I'm
going
to
fix
it
as
soon
as
I
can
it's.
A
Basically,
if,
if
repository
doesn't
have
a
travis
build,
it
immediately
gets
marked
by
nupic
tools
as
needing
a
merge
and
invalidated
for
no
reason,
if
I
manually
revalidate
it
it's
fine,
so
there's
a
it's
a
bug.
I
also
have
a
tool.
That's
got
a
problem
that
I
logged,
but
it's
not
super
important
but
and
yeah.
The
report
final
report
on
this
season
of
new
pick
2014
and
then
we've
got
this
big.
A
A
A
Okay,
okay,
so
assuming
that
everything
else
that
for
everyone's
issues
that
are
currently
in
sprint,
29
will
be
moved
to
sprint.
30.,
we'll
we'll
still
have
a
nice
chunk
of
work
in
sprint.
30.,
there's
already
a
few
issues
here
in
sprint,
30,
some
of
which
I
might
I
might
pull
out
when
I
clean
up
a
little
bit,
but.
A
A
B
A
Answered,
okay,
all
right
so
so
I
sent
an
email
this
morning
with
kind
of
a
proposal
for
a
process
change
for
sprint
planning
to
make
it
more
or
less
like
sprint,
planning
and
and
more
of
just
a
prioritized
backlog
of
tickets
that
anybody
can
grab
and
and
and
take
a
ticket.
So
I'm
hopeful.
Hopefully
it
will
simplify
our
backlog
of
tickets
and
make
it
easier
to
identify
what
or
what's
important
to
work
on
and
what's
not
so
we
might
change
our
process
a
bit.
A
I'm
still
waiting
on
feedback
from
the
community.
Most
people
have
said
sure
that
sounds
great
or
they
don't
care,
which
is
fine,
but
the
the
upshot
is.
We
would
still
have
bi-weekly
meetings.
They
wouldn't
necessarily
be
called
sprint
planning
meetings.
We
might
call
them
a
progress
review
or
something
like
that
where
we
at
least
can
see
the
state
of
development,
of
what
we've
got
done
and
and
the
chunks
of
work
that
we're
planning
another
repercussion
would
be
that
we
the
what
we're
calling
sprints,
which
are
milestones
and
github.
A
We
wouldn't
use
a
sprints.
They
wouldn't
be
timed
box
time
boxes
or
issues
to
fall
into
it.
Would
actually
be
you
know,
categories,
for
example,
all
the
pip
install
stuff
we're
trying
to
do.
That
would
be
a
milestone.
So
any
issue
that
contributes
to
that
goal
defined
by
the
milestone
would
be
tagged
with
that,
so
it
might
make
things
a
little
bit
clearer
using
the
milestone
category
for
something
more
like
a
milestone
and
less
like
a
sprint.
A
So
if
you
want
more
details
on
that
check
the
new
pickpackers
mailing
list,
I
am
looking
for
feedback.
I'm
not
changing
the
process
immediately,
but
I've
I've
been
thinking
along
those
directions
for
a
while
to
provide
priorities
for
tickets
and
then
have
a
simple
view
where
people
can
see
a
stack
rank
of
tickets
and
pick
the
most
important
ones
off
the
top
that
they
have.
The
skill
set
and
motivation
to
work
on.
B
A
A
B
Yeah
and
I
think
that
these
meetings
can
become
a
little
more
strategic
in
nature
also,
rather
than
looking
at
individual
issues,
you
can
be
looking
at
the
level
of
milestones
and
what
we're
really
trying
to
accomplish,
rather
than
you
know,
take
it
by
ticket
yeah.
I
think
sometimes
the
forest
gets
lost
for
the
trees.
A
A
The
office
hour,
no,
we
don't
have
a
topic.
I
don't
even
remember
when
it
is
honestly
it's
monday.
Yes,
it
is
monday,
that's
a
good
point.
We
should
have
a
topic
for
the
office
hour.
I
guess
do
you
do
any
of
you
have
a
topic
for
the
office
hour.
Besides,
maybe
ongoing
algorithmic
work,
we
can
talk
about
new
research,
potentially.
B
A
Yeah,
well,
maybe
we'll
maybe
I'll
just
send
an
email
to
the
list
and
ask
what
people
think
that's
generally
what
I
do
well,
maybe
the
latest
thing
is
the
geospatial
encoder,
and
how
do
you
work
with
that?
Possibly
I
don't
know
yeah.
There
is
a
lot
of
interest
in
that,
so
we
we
put
out
the
video,
but
maybe
but
it's
a
really
interesting
encoder.
I
think,
and
we
could
talk.
We
could
have
jayden
talk
about
that
and
take
questions
about
how
it
works
and
potential
applications.
That's
not
a
bad
idea.