►
From YouTube: NuPIC Development Progress Review
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
Hello
new
pic
pic:
this
is
a
new
pic
development
progress
review.
It
is
November
14
2014,
so
what
we're
going
to
start
off
with
look
at
our
roadmap?
The
first
thing
to
note
is
that
we've
changed
the
name
of
our
milestone
from
Allah
to
0.1
and
beta
to
0.2,
which
makes
more
sense
so
we're
starting
right
off
with
the
semantic
versioning.
Hopefully
we
can
get
to
a
1
point
0
at
some
point.
A
A
Another
cool
thing
to
note,
as
you
can
see,
we're
making
progress
we're
at
33
of
72
tickets
resolved.
Two
weeks
ago,
at
our
last
meeting,
we
were
at
nine
of
67,
so
we
went
from
thirteen
percent
complete
to
forty
six
percent
complete.
If
we
keep
up
that
velocity,
we
will
reach
our
goal
of
closing
out
this
milestone
by
the
end
of
the
year.
So
here's
hoping
we
can
keep
it
up.
Speaking
of
progress,
there's
just
a
quick
review
of
all
of
the
tickets
step
or
closed
on
this
milestone.
A
A
A
There's
some
big
chunks
of
work
to
get
done
on
this,
especially
packaging
new
pic
for
linux
and
OS
x,
which
should
be
part
of
the
release
process,
still
got
the
temporal
memory,
c++
implement
an
ongoing
and
then
another
big
one
is
that
new
pic
should
build
with.
Assuming
that
nucca
core
is
a
standard
external
library
and
it
looks
like
Austin.
You
just
sent
a
couple
PRS
regarding
think
this
one
to
the
core
is
install
oil
as
a
standalone
library,
so
making
progress.
That's
great!
That's
a
big
chunk
of
the
work.
A
We
also
have
the
serialization
upgrade
to
platform-independent
model.
I.
Don't
think
we've
made
any
progress
on
that,
but
hopefully
we
can
hopefully
Scott
you'll
have
time
to
do
that
before
the
ear
and
then
a
lot
of
the
build
improvements
that
we
had
in
our
last
meeting
have
been
categorized
better
into
this
ticket,
improve
the
build
framework
for
a
new
pic
or
C++
development,
and
there's
a
bunch
of
subcategories
here
or
sub
tasks
that
are
not
assigned
so
I
sent
an
email
to
new
peak
hackers.
Today,
yesterday,
I,
don't
remember
I
asking
for
help.
A
If
anybody
wants
to
get
involved,
if
you've
got
experience,
building
and
compiling
C++,
we
could
probably
use
your
expertise.
Auto
build
build
room.
It's
that
we
had
in
our
last
meeting
have
been
cat
eyes
better
than
to
anybody
else,
hear
that
or
nubuck
or
C++
development
and
there's
a
bunch
of
subcategories
here
or
subtests.
You
guys
hear
that
I
really
long
Oh,
no
there's
a
noise
main
list
melt
Snoopy
hackers
today,
yesterday,
I,
don't
remember.
Can
you
guys
hear
me
at
all.
A
Okay,
wow
I
can't
hear
you
guys,
I,
don't
really
know.
What's
going
on
you're
laughing
I
can
tell
that
continue,
or
should
we
start
over
I'm
just
going
to
continue
at
it
as
soon?
Let's
just
pretend
that
didn't
happen,
all
right,
I
and
at
the
bottom
of
each
of
these
zones,
there's
these
standalone
issues
that
don't
really
fit
into
a
group.
A
A
A
Yeah
I
forgot
it's
better
now,
cuz
I
had
one
of
me
now:
yeah
absolutely
want
to
get
I
really.
Where
was
I,
I
guess
so.
I
was
at.
I
was
talking
about
us
alone
issues
at
the
bottom
and
and
super
issues
of
major
initiatives
sort
of
at
the
top.
But
everything
in
this
milestone
we
want
to
try
and
get
done,
that's
in
or
in
order
to
release
0.1.
A
So
chime
in
you
guys.
If
something
weird
happens
again
so
I
can
stop,
then
me
and
I'll
just
continue
on.
So
what
I
was
about
to
talk
about
is
right.
The
user
experience
versus
the
developer
experience.
This
is
I,
think
a
discussion
we
were
having
on
this
ticket
where
we
were
drafting
out
sort
of
what
we
think
the
build
should
look
like,
and
there
was
some
there's
quite
a
bit
of
discussion
here,
but
the
gist
of
it
is
we.
A
We
want
to
make
the
build
easier
for
developers,
especially
for
C++
developers
that
are
going
to
be
working
on
new
decor
that
also
for
Python
developers
work
on
new
pic.
So
we
want
this
integration
between
new
pic
and
new
decor
to
be
cleaner
and
easier
and
more
flexible,
so
Austin
has
been
working
on
that
which
is
great,
but
I
also
want
to
point
out
that
we
still
have
an
initiative.
Let
me
scroll
down
here
to
our
0.2
mile
stone.
We
still
have
an
initiative
to
get
PIP
install
new
pic
working
this.
A
In
my
opinion,
this
is
the
end
all
user
installation
experience
here.
So
when
we
get
to
this
point,
it
is
complete
any
user
of
new
pic
who
will
not
be
working
with
the
new
pic
source
code.
You
just
wants
to
use.
It
should
be
able
to
just
pip
install
new
pic,
and
that
will
be
that
and
not
have
to
worry
about
anything
else.
Then
they
can
import
new
pickin
and
in
there
python,
scripts
etc,
and
everything
will
be
set
up.
A
That's
how
we
want
users
to
use
new
pic
and
what
and
when
you
pip,
install
a
python
module.
It
should
get
the
latest
stable
release,
so
we
have
to
have
a
release
peer
of
0.1
before
we
can
get
to
pip
install
new
pic,
because
getting
the
release
in
place
means
we're
going
to
be
publishing
binaries
and
then
we
can
work
on
getting
pip
install
new
pic
to
put
the
binaries
the
proper
binaries
in
the
proper
places
in
the
users
environments.
A
A
Ok,
all
right,
ok!
So
let's
do
a
quick
review
of
the
open,
PRS
and
then
we'll
most
likely
finish
up
pretty
quickly.
So
the
oldest
are
on
the
top.
Here
anomaly
strict
is
mark.
It
is
in
currently
airing
on
the
build
and
it's
in
his
the
windows.
Build
implementation
is
a
PR.
A
That's
really
not
mirja
ball,
there's
but
they're,
aware
of
that,
the
guys
that
are
working
on
this
or
just
trying
to
get
new
big
building
windows
once
I
get
to
a
certain
amount
of
progress
done,
we'll
talk
about
how
we
can
get
the
version
of
that
merged
in
another
few
from
mark.
These
three
are
all
marks
PRS
and
they
are
either
failing
or
airing
and
the
balls
into
work
for
those
and
again
the
anomaly
parameter
is
exposed,
I
think,
is
pending
one
last
review
from
mark
all
right.
A
Scott
just
did
a
review
I
just
want
mark
to
take
a
look
at
it.
Real
quick
address
the
one
or
two
common
see
left,
and
then
that
should
be
mirja
bellezza
Lee.
So
that
would
be
good
this.
This
utensils
review
here
is
a
corollary
to
the
windows.
Build
he's
simplified
that
PR.
So
there's
a
bit
of
discussion
going
on
there.
A
There
is
an
amp
er
that
I'm
not
too
concerned
about,
and
then
some
more
recent
PRS
that
Jake
is
actively
working
on
that.
This
is
for
limited
org,
that's
nothing
important
and
then
Austin's
recent
PRS
working
towards
getting
a
new
pic
or
built
as
a
standard
library.
So
there
is
not
a
whole
lot
of
action
for
us
to
take
right
now
on
these,
that's
not
already
being
taken
so
we're
in
a
pretty
good
place
for
PRS.
We've
got
some
old
ones,
but
there
are
most
mostly
old
ones,
are
in
mark's
court.
A
Everything
else
to
go
over,
I
think
that's
so
that's
all
that
I
wanted
to
to
go
over
think
we're
pretty
much
on
the
same
page.
I'm
really
happy
with
the
progress
it
that
we've
been
making
over
the
past
month,
or
so
since
the
hackathon,
so
just
want
to
give
everybody
a
quick
kudos
for
that.
So,
thanks
for
all
of
your
hard
work,
do
you
guys
in
the
office
want
to
press
anything
in
particular.
A
Sounds
like
a
no
alright.
That's
it
quick
meeting
good
progress.
Let's
keep
it
up
if
anybody
is
looking
for
work
good,
please
go
to
the
roadmap
and
and
pick
something
in
0.1.
That's
we're
really
pushing
all
of
the
issues
in
this
0.1
miles
down
here
that
that's
what
we're
trying
to
get
to.
Of
course
you
can
work
on
other
issues,
but
we're
not
going
to
put
nearly
as
much
emphasis
on
those
as
the
ones
that
are
listed
here
in
an
hour
roadmap.