►
From YouTube: NuPIC Sprint Planning - Dec 20, 2013
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
A
A
A
So
I'm
just
going
to
go
ahead
and
go
go
on
with
this
so
I'm.
Looking
at
my
current
issues,
that's
into
this
we
will
look
at
spread
11,
so
14
closed
for
requests
or
tickets
during
the
Sprint.
So
for
me,
I
added
some
documentation
and
oxygen
had
a
blog
post
from
Donna
that
I
published
we
had
best
failure
fix
from
zubat
I.
I
created
a
Status
page
for
new
pic
which
I'm
going
to
use
here
in
a
minute
another
teeth.
A
Yeah
at
a
fixed
up,
tooling
server
issue.
So
one
of
my
major
things,
this
Brett
was
getting
this
status
page
out,
so
this
shows
the
overall
status.
It
doesn't
sort
of
accumulate.
If
there's
one
failure
in
any
of
this,
it
doesn't
doesn't
display
it
as
an
overall
status
of
green
or
red,
but
it
it
shows
all
the
services
that
we
use
in
new
pic
to
building
and
good
things.
A
So
it
has
spent
a
lot
of
time
to
sprint.
Getting
this
automatically
running
and
documenting
the
pic
API,
which
is
going
to
be
your
public
API,
so
network
region
link
cetera
a
lot
of
missing
stuff
in
here,
there's
a
lot
of
places
where
you'll
see
to
do
document,
but
any
docs
that
were
in
the
code
I
retained
so
ish.
So
there
is
some
useful
stuff
in
here.
It
might
not
be
perfect,
so
updates
are
definitely
welcome.
So,
for
example,
this
instructor
doesn't
have
any
parameters
documented,
so
we
need
docs
for
that.
A
Some
of
the
functions
are
pretty
well
documented,
but
there
are
still
a
lot
of
to
do
items
in
here.
So
this
is
all
low
hanging
fruit.
If
anybody
who's
new
to
the
project
wants
to
come
in
and
improve
our
documentation,
there
is
a
wiki
site
on
our
home,
looking
page
under
table
of
contents,
development
processes
documenting
code,
and
this
is
instructions
on
running
a
building
docks
locally
and
then
some
of
the
standards
for
documenting
python
and
c++
code.
A
So
that's
that
the
status
page
also
has
a
extra
information
about
the
latest
new
big,
build,
whether
it
be
from
a
pull
request
or
on
master
and
that
it
breaks
out
two
boxes,
one
for
just
masters
easier,
Master
build
has
been
good
for
over
for
a
week
and
our
new
pic
PRS
build
history.
These
are
only
builds
from
PRS,
so
we've
been
pretty
clean
on
that
there's
one.
That's
keeps
erroring
from
David
who's,
trying
to
update
the
Travis
file
and
then
stop
working
out.
A
A
So
still
a
lot
of
open
pull
request,
some
small
administrative
things
that
that
I
need
to
do
I'm,
starting
to
create
tickets
for
specifically
documenting
starting
areas
of
code.
These
are
just
website
updates
that
I
haven't
had
time
to
get
to
most
of
this
stuff
is
probably
just
going
to
fall
into
the
next
sprint.
A
So
and
I
don't
know
what
some
of
them
are
this
contributing
that
md
file?
If
we
have
that
file
existed
in
our
repository,
then,
whenever
someone
opens
an
issue
and
get
have
issues,
it
will
display
the
text
in
the
smile
or
the
display
a
link
to
this
file
and
ask
people
to
read
it
before
they
create
an
issue.
So
that's
a
good
kind
of
roadblock
to
get
people
to
understand
what
our
processes
before
creating
an
issue.
We
get
a
lot
of
questions.
A
Well,
a
few
questions
right
now:
they're,
really
a
better
student
to
go
to
the
mailing
list
that
turn
into
github
issues,
so
that
file
out
I
should
at
least
put
something
in
there
to
defer
people
to
sending
questions
for
the
mailing
list
still
need
a
joke.
Lock,
a
rock
employee.
To
give
me
admin
rights
to
lure
AWS
account
so
that
I
can
get
everything
under
one
place
and
there
we
still
have
some
AWS
assets
that
are
used
entirely
for
a
new
pic
that
are
under
an
internal
rock
AWS
account.
A
So
as
part
of
that,
I
need-
and
you
take
that
out
in
the
open
just
so
potentially
if
we
have
any
collaborators
that
want
to
help
with
that
type
of
infrastructure,
that
I
can
give
them
permission
to
do
so
without
bugging.
Anybody
within
grok
I
am
lagging
behind
on
this
goals
and
specs
for
an
epic
API
defined.
A
documented
I
wanted
to
get
some
of
the
API
dots
initially
up
and
out
there
for
review
before
we
talk
to
more
about
what
the
goals
are
for
them
for
the
official
hippocampi
I
couple
things
from
mark.
A
So
a
lot
of
these
things
are
sitting
here.
Let
me
clear
this,
so
these
are
all
of
the
PRS
that
our
mark
is
ready.
So
these
are
things
that
the
author
is
waiting
for,
review
and
merge
on.
So
these
are
kind
of
the
high
priority
things
that
we
want
to
not
let
sit
there
and
and-
and
fester
like
this-
has
been
around
for
24
days
a
month
a
month
a
month,
two
months,
two
months,
two
months.
A
So
a
lot
of
this
falls
onto
you
know:
suet,
I
and
Scott
and
and
the
towel
your
people
that
work
for
Brock,
so
I
know
I,
can't
blame
the
community
for,
for
these
things,
kind
of
languishing
and
those
guys
are
busy
building
product,
but
I'm
still
trying
to
put
some
pressure
on
people
to
get
these
things
with
you
door
closed.
If
we're
not
going
to
merge
them,
or
at
least
get
them,
make
sure
that
there's
a
least
progress,
those
things,
okay,
so
might
as
well
just
create
a
new
milestone.
A
A
B
A
11
it's
about
issues
with
issues,
so
all
these
sprint
11
tasks
at
this
point
that
are
still
open,
I'm
going
to
be
moving
them
into
sprint,
well
and
I'm,
not
adding
any
more
tickets,
because
there's
more
than
enough
to
consider
to
continue
to
work
on.
So
this
is
the
highest
priority
list
of
things
to
work
on.
A
lot
of
them
are
just
administrative
stuff
for
me.
If
anybody
wants
to
pick
one
of
these
up,
please
assign
them
to
yourself.
A
Growth
in
here
I've
changed.
This
recently
thought
it
was
attribution
standards
now
I've
lost
it
development
process,
yeah
so
which
involves
discussion,
logging
issue
working
and
creating
a
pull
request.
Sort
of
in
that
work,
I'm
trying
to
hear
into
that
and
people
are
doing
a
job
so
far,
so
appreciate
all
the
work
that's
gone
on
and
we
got
a
decent
amount
done
in
the
last
sprint,
and
so
the
holidays
are
coming
up
so
pick
up
anything
that
you
feel
like
pick
it
up.
A
A
B
A
A
Yeah
we've
had
issues
with
travis
and
and
get
help
being
intermittently
up
and
down
recently,
and
so
it's
nice
to
just
know
immediately
what
the
problem
is
and
also
invented.
Our
website
is
had
a
few
build
issues
so
yeah,
that's
it
our
will
close
it
off.
That
was
a
quick
sprint
planning
meeting.
If
you
have
any
questions
about
it,
there's
there's
already
an
email
on
the
mailing
list.