►
From YouTube: NuPIC Sprint Planning - Apr 25, 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
Just
you
guys
me
and
Jeff
so
Jeff
fault,
ok,
hello,
new
pic,
welcome
to
sprint
21
planning,
I'm
jumping
into
I
actually
created
a
wiki
page
with
the
plan
for
this
sprint.
I
wanted
to
try
and
try
and
move
ahead
with
our
plan
on
on
extracting
core.
So
just
a
quick,
quick
review
excuse
me
we're
moving
ahead
with
a
plan
to
to
pull
core
out.
A
We
already
have
it
out,
but
the
next
step
in
this
vision
towards
having
lots
of
different
client
libraries
is
stuck
to
which
is
preparing
for
a
new
pic
or
release,
and
to
do
that
we
need
a
well-defined
api.
So
this
is
the
bit
next
big
thing:
I
think
we
should
work
towards
is
defining
our
API
with
tests.
So
that
is
what
I
had
in
mind.
Creating.
A
Even
if
we'll
get
to
the
point
of
writing
tests,
but
if
we
can
just
define
it
on
a
wiki
at
least
define
what
needs
to
be
tested.
So,
let's,
let's
start
there,
I've
got
a
couple
of
supporting
tasks
here.
The
first
one
define
the
public
network
API
on
a
wiki.
I
created
a
wiki
page
for
this,
and
this
ticket
has
a
few
useful
references.
A
A
So
luckily,
he
seems
to
have
the
skills
that
we
need
to
do
this
documentation,
which
is
great
and
so
I
linked
him
to
the
previous
ticket.
We
were
talking
about
as
a
reference,
so
if
we
define
all
of
the
what
the
API
is
here
on
this
wiki
page,
and
he
will
then
know
what
needs
to
be
publicly
documented
in
his
ticket.
A
So
right
now
we
don't
generate
any
any
decent
reporting.
Styles.
The
standard
is
xunit
style,
j
unit
style,
whatever
that's
an
xml
format,
that's
pretty
globally,
parsable
and
reportable.
It
can
be
extended
with
coverage
information.
If
we
can
get
into
using
some
standard
c++
testing
framework
that
can
generate
these
reports,
I
don't
really
care
how
we
get
there.
As
long
as
we
can
generate
these
reports,
we
should
have
a
lot
of
options
on
how
we
published
the
reports
and
what
we
can
do
with
them
on
every
build
is,
if.
C
A
Yes,
no
dependencies
here
I
mean
all
three
of
these
tasks.
That
I
think
are
the
next
things
we
should
work
on
are
pretty
much
independent
utensil
could
start
working
on
documentation
even
today.
I
think
he
would
have
a
decent
understanding
of
what
should
be
documented.
What
happened
to
my
screen
share
that
we
still
see
in
history:
oh,
okay,
okay,
okay,
so
this
is
just
kind
of
the
objective
that
I
think
we
should
shoot
for,
and
this
is
a
what
is
you
know
could
emphasize
that
this
is
a
community
initiative.
A
This
is
what
the
community
wants,
so
we
need
help
with
these
things
and
I
think.
Thank
you.
The
people
who
have
jumped
in
and
started
helping
and
have
been
helping
this
whole
time,
but
we're
not
going
to
accomplish
this
goal
without
community
help
I'm,
especially
looking
at.
If
someone
is
watching
this
and
they
have
C++
unit
testing
experience,
I
would
love
your
help
with
this.
C
A
C
A
Good
point:
another
major
initiative-
that's
going
down,
which
would
be
awesome,
is
a
installing
new
pic
as
a
as
a
pip
package.
So
david
has
been
working
on
this
and
I.
Don't
know
how
well
it's
going
or
not,
but
I've
wanted
this
and
for
a
long
time.
So
that's
going
to
be
awesome.
A
quick
season
of
new
pic
update.
This
is
something
I
need
to
put
a
bit
of
work
into
this
print.
I've
got
hackathon
and
some
season
of
nip
it
work
the
sprint,
so
I
won't
be
working
on
a
lot
of
technical
tasks.
A
We
have
sent
acknowledgments
to
all
of
the
students
who
have
submitted
the
projects
that
we
have
approved,
I've
been
very
slow
and
sending
the
emails
back
for
for
the
students
that
did
not
get
approved,
but
I
don't
want
to
discourage
them.
I
think
a
lot
of
those
projects
are
still
good
and
would
get
community
support
if
they
were
just
a
community
project
doesn't
have
to
be
a
season
of
new
pic
project.
A
So
I'm
going
to
try
and
follow
up
on
that
I'm
working
with
Pradeep
toe
to
a
get
some
news
item
out
on
the
website
and
yeah
I'm
going
to
beat
you
there
we
go
and
the
other
thing
is:
congratulations!
Chaydin,
you
for
being
a
committer!
We
voted
on
you
to
bring
you
in
as
a
committer
you're.
The
next
person
on
in
the
ranks
of
number
of
commits
so
and
another
thing
is
a
jet
and
I
was
hoping,
there's,
there's
still
quite
a
few
tickets
and
fluent.
A
Server
issue,
trackers
I
was
hoping
you
could
start
to
manage
those
you
probably
have
been,
but
I've
been
reviewing
them,
but
I'm
probably
going
to
let
those
fall
into
your
lap.
I
just
don't
have
time
to
manage
those.
Okay,
sure
I
just
wanted
to
say
hi
to
utensil
song.
If
he
is
watching
he's
hasn't
he's
created
several
PR
is,
none
of
them
have
actually
been
merged,
but
it's
good
work
and
we
appreciated
and
he's
got
a
lot
of
good
issues
described
and
a
lot
of
good
discussions.
All
this
arguments
are
very
well
put.
A
A
This
is
not
what
I
want
to
pull
this
out
for
now,
okay,
so
these
are
the
two
tickets
that
already
are
going
to
exist
that
are
in
our
high
kind
of
top-level
initiative
for
the
API
definition,
so
these
are
in
sprint,
21
already
so
I'm
moving
now
back
to
sprint
20,
which
is
a
sprint.
We
are
currently
closing
our
clothes
tickets.
A
A
Utensil.
Has
this
a
PR
open
that
renames
all
of
our
source
files
to
the
upper
camelcase
convention?
We've
had
a
lot
of
discussion
about
this
on
the
mailing
list.
I
am
very
anxious
about
this
PR,
as
I've
noted,
and
so
there's
discussion
on
the
mailing
list
about
the
about
it
and
on
this
ticket
I'm
afraid
it's
going
to
break
backwards.
It
could
risk
that
it
could
break
backwards,
compatibility
from
for
model
serialization,
but
they
that
small
risk
has
very
big
consequences.
A
C
A
I
was
encouraging
the
utensil,
since
he
kind
of
initiated
this
to
come
up
with
another
vote
tally.
My
opinion
is
its
majority
rules,
because
this
is
not
a
strategic
decision,
it's
really
more
of
a
styling
decision
and
unless
there's
no
one
screaming
about
anything
that
it
shouldn't
make,
you
know
a
whole
hell
of
a
lot
of
difference.
So
I
would
just
like
him
to
tally
that
up.
I
can.
I
can
send
another
email.
I
asked
them
to
tally
the
votes
and
and
just
see
what
the
majority
is.
A
Boats,
mortality
about
halfway
through
and
I,
think
people
started
discussing
than
Python
naming
conventions
and
module,
naming
conventions
and
class
naming
conventions,
and
really
the
discussion
was
only
about
file
naming
and
this
plus,
plus
new,
pic
or
so
I
think
we
could
probably
pull
all
those
votes
out.
It's
just
a
lot
of
noise
and
that
thread.
If
it's.
D
A
A
A
That
would
be
fine,
I'm
kind
of
letting
I
was
hoping
that
they
would
be
able
to
make
that
decision
amongst
themselves.
But
if,
if
it's
not
made
over
the
weekend
or
so
I'll
come
in
and
try
and
organize
something,
okay,
help
text
for
see
make
options
is
misleading
I'm
not
familiar
with
this
one
chaydin,
but
if
you're
willing
to
work
on
that
the
sprint
I.
A
A
So
we're
good
at
eight
open
new
pit,
cord
tickets
and
sprint
21
on
two
new
pic.
This
is
the
one
that
always
has
the
most
tickets,
so
I
don't
have
anything
in
sprint
21
for
new
pic.
Yet
we
we
did
get
a
good
amount
of
stuff
done
and
a
new
pic
this
past
a
lot
of
little
stuff,
but
so
the
significant
things,
let's
see
I
did
some
swarming
stuff
I.
Think
I
improved
this
warming
dictionary.
A
p.I
is
a
bit
published.
A
A
new
tutorial
Austin's
been
doing
some
good
work
on
getting
better
docker
support
of
sint,
OS
and
ubuntu.
So
he's
doing
that
with
anticipation
of
helping
people
install
new
pic
at
the
hackathon
next
weekend,
so
he's
trying
to
kind
of
pave
the
way
for
that
because
the
last
hackathon,
that's
always
the
tedious
part,
is
getting
it
built
for
people.
A
A
Most
of
this
is
just
clean
up
stuff
that
was
left
over
after
we
we
got
the
builds
totally
separated,
but
it's
all
good
work,
good
cleanup,
so
things
are
cleaning
up.
We're
getting
rid
of
environment
variables
were
putting
everything
into
see
make
so
a
lot
of
stuff
got
cleaned
up
the
sprint,
which
is
what
the
intent
was.
So
that's
great
back
to
open
issues
so
I'm
going
to
roll
down
here
and
select
the
ones
we
think
are
the
most
important
that
we
want
to
move
into
the
next
milestone:
okay,
yeah
Shaitan.
A
You
open
these
to
the
pilot
ones.
That
seems
to
be
a
very
simple
change.
That
should
be
easy
to
merge
and
test.
So
you
might
as
well
move
that
along
the
function,
a
model
functionality
compatibility
test-
that's
your
you're
actively
working
on
that!
Yes,
so
I,
don't
I,
don't
know
what
the
extending
the
SP
to
support
in
dimensional
topology
is.
Is
that
something
you're
going
to
work
on
soon
yeah
and
work
on
that
soon?
A
Great
right-
and
this
this
I
think
is
the
this-
is
the
one
that
I
think
is
important
before
we
can
merge
that
PR,
a
new
pic
or
that
does
name
changing
so
this.
This
is
the
one
if
you
have
a
priority.
Jaden
I
think
this
is
the
one
I
would
like
you
to
like
to
see
closed
off,
first,
which
one
is
that
we
can't
tell
from
the
update
I'm
sorry
I'll
drill
right
down
into
it.
C
A
A
Okay,
so
check
that
the
OPF
bottle
functional
capability
test.
You
had
a
PR
for
that
too
than
you,
yeah.
Okay,
this
one
I'm
going
to
I,
don't
know
if
I'm
gonna
be
able
to
work
on
this
and
I'm,
not
sure
that
it's
a
bug
so
I'm,
probably
going
to
let
it
fall
through,
but
so
running
a
swarm
didn't
used
to
produce
some
model.
Params
that
was
visible.
It
would
just
it
would
it
would
put
it.
A
You
know,
create
the
description
pie
but
went
once
I
had
it
out
put
the
model
program,
so
you
could
run
it
to
create
a
model
directly.
I
noticed
that
there's
a
discrepancy
in
that
where
there
would
say
it
had
a
non
temporal
model
inference
type,
but
it
would
still
include
TP
enable
is
true
and
TP.
Params
I,
don't
think
that
it's
affecting
the
functionality
I
just
think
that
it's
like
an
artifact
left
over
and
one
override
to
the
other,
most
likely
it
creates
the
TP
params,
but
it's
fits
an
antiporter
model.
A
C
A
C
A
Okay,
I'm
making
a
note
on
that.
Okay,
so
I'll
pull
it
along
just
because
I
don't
want
to
lose
track
of
it.
I
don't
have
enough
time
to
work
on
it,
so
renaming
source
and
swig
files
to
follow
upper
camelcase
convention.
That's
it
that's
another
one
that
I'm
not
going
to
feel
comfortable
merging
until
this
top
one
is
is
done,
but
if
Travis
builds-
and
this
test
is
passing,
I
would
be
fine
with
it.
This
extract
boosting
draft
zubat,
I,
I,
think
I
assign
this
to
you.
A
Just
for
review
and
I
made
a
note.
I
mean
there
was
discussion
on
the
mailing
list
about
this.
It
seems
to
be
quite
an
extensive
algorithmic
change.
Do
you
have
the
time
to
put
in
to
look
at
this
PR
because
it's
quite
a
chunk.
C
The
I
think
the
discussion
on
the
mailing
list
was
about
creating
a
subclass
head
into
the
algorithms
and
put
all
at
all
of
this
stuff
into
the
subclass
I.
Don't
know
if
he
did
that
I
can
certainly
take
a
look
at
that
yeah
you
can
I
can
take
a
quick
look
at
that,
because
if
it's
in
a
subclass
then
there's
no
concern
whatsoever.
C
You
know
it's
kind
of
a
nice
way
for
people
to
experiment
with
something,
but
you
know
putting
all
of
this.
All
of
these
changes
into
the
main
will
in
the
main
thing.
Well
definitely,
what
is
a
very
good
chance,
it'll
cause
backward
compatibility
issues
and
right
now
it's
not
going
to
cause.
We
don't
even
know
if
this
will
help
yeah.
A
C
It
would
be
a
he
didn't,
create
a
base
class
for
boosting
and
subclasses
of
boosting,
but
all
of
that
is
in
the
current
spatial
pooler
class
uh-huh.
The
discussion
was
to
create
a
subclass
of
spatial
pooler.
How
I
see
the
problem
with
this?
Is
that
as
it
is,
if
you
unpick
alann
old
checkpoint,
which
doesn't
have
all
of
this
stuff
inside
the
spatial
pool,
or
it
probably
wouldn't
work
so.
A
We
discussed
the
proposal
on
the
mailing
list,
then
log
an
issue
that
should
define
the
problem.
So
if
you
had
logged
an
issue
that
define
the
problem
we
and
before
you
work
on
your
PR,
we
can
come
in
and
say
no,
that's
not
what
we're
talking
about
so
I'm
trying
to
prevent
the
people
doing
work
that
that
gets
thrown
away.
I,
don't
know
if
this
is
going
to
get
thrown
away
or
not,
but
the
fact
is:
I.
Don't
think
that
we
have.
We
might
not
have
time
to
look
at
this
thoroughly
right
now,
so.
A
C
A
Unless
it'll
break
Hildur
stuff
yeah,
ok,
then
I'm
gonna
leave
it
out.
Okay,
this
bug
vitaly
created
was
the
make
clean
and
disk
clean
breaking
something
I'm
going
to
leave
this
in
this
was
something
that
mark
got
added
as
I.
Don't
know
if
it
how
important
it
is,
but
I
signed
it
to
mark
so.
A
A
A
Some
of
these
I'm
going
to
skip
these
next
2,
I'm
going
to
be
pretty
heavily
loaded
this
sprint.
So
I'm
gonna
leave
these
this.
This
build
failure.
When
so
we're
still
having
this
in
TX
developer,
build
thing.
This
should
go
away
when
we
get
new
pic
tip
installable,
I
believe,
but
it's
currently
still
it
currently
still
exists.
It
whoo,
it's
bothering
right
now.
I
know
some
of
us
are
or
have
our
own
solutions
for
getting
around
this
right,
but
I
think
it's
still
important
issue
to
keep
track
up.
A
A
C
C
C
B
A
A
A
love
it
but
okay,
I
will
yeah
amazing
okay.
If
well,
if
you're
not
complaining
about
it,
you
reported
it
comfortable,
ism.
B
A
A
It
was
the
last
error
that
we
saw
a
type
error
in
nuoc
engine
yeah,
so
I,
don't
know
what
to
do
about
this.
This
guy
might
have
just
been
a
casualty
and-
and
you
can
get
it
working
so
I'll,
try
and
follow
up
with
him.
I
don't
want
to
let
stuff
like
this
slip
off
so
I'll,
see
if
I
can
follow
up
with
him
and
get
any
updates.
A
A
This
xcode
thing
so
Louis
reported
this
and
then
I
never
really
heard
anything
else
about,
but
so
I'm
going
to,
let
it
sit
and
if
he
has
any
problems
again
well,
Rhea,
tak
vagrant
instructions
are
out
of
date.
Yes,
they
are.
This
one
can
probably
be
closed
now.
The
new
pic
does
not
use
head
of
master
of
nougat
core,
and
but
we
sort
of
have
another
solution
here,
where
it
would
could
very
easily
use.
Headed
master
because
Austin's
mechanism
uses
a
committee
Sh,
so
we
could
just
update
it
to
head.
A
Ok
switch
default.
Spatial
puller
CPP.
That's
you
already
have
the
PR
for
that
clean
up
unused
code
in
CL,
a
model
I
think
this
is
such
an
old
PR
two
months
old,
and
there
is
this-
is
an
issue.
Here's,
oh
yeah,
here's
the
pr
so
I
was
I,
went
to
look.
I
took
a
little
bit
of
a
drastic
action
on
this.
A
This
this
PR
has
been
open
for
five
months
and
it
was
we've
gone
back
and
forth
and
back
and
forth
about
it
a
month
ago
and
a
month
in
a
week
ago,
as
at
mark
for
updates
on
it
and
not
getting
anything.
So
at
this
point,
I'm
sort
of
gonna
have
a
policy
to
close
to
due
to
inactivity
if
they're
important
to
go
open
back
up.
That's
my
opinion.
I
just
don't
want
to
have
scale
PRS
sitting
around,
so
that's
with
it.
So
I'm
going
to
close
this
close
this
one.
A
A
B
A
Couldn't
figure
out
how
to
write
it,
so
the
thing
is
the
PR
has
been
open
for
such
a
long
time
and
initially
I
was
just
like
well
I'm,
just
going
to
close
it
nobody's
going
to
read
you
test
about
it
then
I
realized.
We
don't
really
have
any
policy
that
says
you
must
test
all
the
code
you
submit
and
I
would
rather
have
correct
code
than
a
non
correct
code.
So
I'll
take
this
without
the
unit
test.
A
A
And
that's
already
motion:
that's
already
merged
I
took
the
same
pragmatic
approach
to
that
as
well.
I
was
sitting
waiting
for
I,
didn't
I,
didn't
know
how
to
write
a
C++
unit
tests
and-
and
nobody
was
helping
I'm,
not
complaining
of
just
you
know.
No,
no
one
could
help
it
wasn't
interest
in
doing
it,
and
then
the
thing
is:
if
there's
no
interest
in
doing
it,
it's
not
important
so
and
I
know
that
the
code
is
better
with
the
with
the
right
code
in
there,
even
if
it
doesn't
have
a
test
around
it.
A
A
That's
the
same
thing
I
was
just
talking
about
there
and
ok.
So
there's
here's
one
more
thing
to
talk
about
your
scalar.
Add
safety
checks,
so
this
is
another
one.
Who's
been
around
for
a
really
long
time,
Oh
in
the
build,
failed
crap,
so
everybody's
pretty
much
to
prove
this.
It's
just
the
last
build
failed
so
mark
its
back
on
you
buddy.
Sorry
we're
all
okay
with
the
change.
We
just
need
to
get
to
build,
passing
all
right.
So
all
of
these
are
moving
into
spread,
21,
okay,
the
rest
of
them.
A
Let
me
the
rest
of
them.
I'm,
going
to
dump
to
the
backlog.
I
haven't
been
extremely
happy
with
with
my
strategy
of
adding
a
bunch
of
tickets
into
the
current
sprint,
because
then
hoping
someone
will
pick
them
up,
because
usually
people
don't
and
a
bunch
more
tickets
get
added
to
the
current
sprint.
So
we're
going
to
go
with
17
tickets
and
sprint
21,
which
I
think
is
more
than
enough.
A
Wow,
yeah,
okay,
there's
a
couple
in
here
for
Darwin
64
that
I
have
assigned
to
Austin
he's
not
here,
but
I'm,
going
to
pay
him
about
them
and
have
them
evaluate
how
valid
they
are,
whether
they
work
same
thing
for
linux,
64,
I'm
sort
of
by
default,
just
giving
Austin
the
conch
on
these
to
decide
what
to
do
with
them,
but
both
these
are
already
in
I
think
spent
21
at
the
I.
Already
these
two
of
the
important
ones,
the
other
one
was
not
so
for
new
men
2.org.
A
This
is
mainly
me
a
few
things
to
do.
It's
not
really
important
to
go
over
for
new
pic
tools
or
sprint
21.
Nothing
extremely
important
to
do
here,
there's
a
couple
little
bugs
that
need
to
get
fixed,
but
nothing
that's
super
bad
and
then
for
sprint.
21
for
the
butcher
twine
for
the
the
wallboard
Jeff
is
going
to
help
me
with
with
these.
So
that
would
be
great
when
I
move
these
into
sprint.
21
Jeff.
Those
are
the
ones
that
that
I.
A
Like
I
said,
I
did
most
of
the
server
side
stuff
right
now,
just
dumps
a
big
Jason
blob
to
the
screen,
but
that
would
be
nice
for
sprint
planning
to
have
that
available.
Okay,
otherwise
going.
B
Okay,
sorry
sorry
Jeff
I've
talked
over
you.
What
was
that
no
one's
talking
over
you
I
started
looking
at
that
today.
It's
these
two
things:
okay,.
A
A
Okay,
okay
in
retrospective,
very
briefly,
I
think
everything
went
pretty
well
to
sprint,
I!
Think
it's
that's
it.
Anyone
else
have
any
opinions.
There.
C
A
B
So
yeah
that
the
hackathon
brings
up
a
good
point.
Is
they?
You
know
a
lot
of
people
when
they
show
up
the
hackathon
they're
new
to
the
whole
thing
and
there's
so
much
development
going
on
debt?
A
Well,
the
other
I'll
have
that
and
everybody
will
get
a
USB
dongle
with
a
snapshot
as
well,
but
I
don't
know
that's
if
they
want
to
use
it,
they
can
but
yeah.
That's
true
and
we've
already
had
some
issues
with
that,
because
the
developments
going
so
fast
people
will
come
and
say,
something's
not
working,
it's
just
because
they
pulled
and
they
didn't
change
anything
so
yeah,
it's
not
going
to
work.
Yeah.
You
gotta,
go.
B
B
Is
always
a
substantial
amount
of
discussion
on
the
mailing
list
in
in
IRC
with
people
going
like?
Oh
I
can't
build,
you
know
and
yeah
well
troubleshooting
with
them
its
seemingly
good
to
have
some
sort
of
snapshot.
It
says
you
know
this
doesn't
have
the
latest
code,
but
this
is
the
latest
working
build
yeah.
If
you
give
a
USB
dongle
with
the
working
code
that
will.
A
C
A
That
might
be
a
good
idea.
Is
that
it
still
it's
really
hard
to
estimate
when
we'll
get
to
the
point
or
we'll
be
ready
for
that,
then
six
months
I
don't
know
so
maybe
maybe
we
could
do
that.
I
mean
we
could
we
could
start
tagging
right
now.
If
we
know
a
good
shot
for
core,
we
know
get
off
for
new
pic.
We
could
tag
on
the
same
and
now
could
at
least
be
a
line
in
the
sand
for
people.
Don't.
B
Think
it
would
cut
down
on
a
lot
of
the
distractions
from
people
just
having
trouble
building
yeah.
You
could
say
you
know
if
you're
new
to
this
here's
here's
you
know,
use
this
tag
and
then,
if
you're,
once
you
kind
of
familiarize
ourself
things
and
how
everything
works
together,
you
can
then
start
getting
the
nightly,
builds
and
stuff.
That's.
A
A
good
idea
as
having
a
pre-release
version
and
a
wiki
page
on
this
is
how
you
build
from
this
pre-release.
We
can
always
defer
people
to
that
if
they're
having
build
issues,
especially
if
they're
just
users
trying
to
get
something
working
and
again
I,
would
really
help
that'd
be
good.
Okay,
I'm
going
to
take
a
note
on
that,
all
right,
guys,
let's
sign
off
and
get
on
with
their
lives.
Thanks
for
your
time,
I
appreciate
it
and
we
will
see.