►
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
So
basically,
we've
got
a
few
things
going
on.
We
we
have
a.
We
have
a
really
good
platform
right
now,
you
know,
NRI
labs
itself
is
is
not
meant
to
be
an
end-all
be-all
to
everything.
In
fact,
that's
sort
of
certainly
not
the
goal
for
for
the
antidote
platform.
You
know
we
did
with
the
antidote
platform.
Was
we
built
it
to
be
as
agnostic
to
the
curriculum
as
possible?
You
know
loading
things
like
lessons
and
eventually
things
like
quizzes
as
well.
A
As
you
know,
new
the
new
feature
that
we've
got
coming
out
in
the
next
release
called
collections,
there's
a
bunch
of
other
other
resources
that
we've
been
playing
with
but
effectively.
You
know
the
the
software
the
platform
itself
is
in
is
ambiguous
to
all
of
that,
and
so
what
we
wanted
to
do
was
we
wanted
to
build
a
platform
that
is,
you
know
that
you
can
use
for
for
learning,
pretty
much
anything.
There's
some
exceptions
to
that.
There's
some
some
trade-offs
that
we
made
some
optimizations
that
we
made,
but
generally
that's
the
case.
A
Certainly,
there's
no
opinionate,
there's
no
opinion
baekeland
the
platform
on
what
kind
of
you
know
what
kind
of
you
know
what
specific
kind
of
curriculum
you
can
teach
there's
really
if
there
are
any
limitations,
it's
just
a
limitation
of
what
the
platform
offers.
So
we've
done
that
and
then,
of
course,
entering
labs
is
a
specific
curriculum
that
we've
also
built
to
feed
into
that
platform
to
teach
Network
automation
specifically,
and
we
have
a
whole
bunch
of
other
guidelines
around
that
things.
Like
you
know,
you
can't
make
it
all
about
sales
pitches.
A
You
know
if
you
have
something
to
show,
that's
cool,
you
can
show
it
but
make
it
about
value
to
the
user.
You
know
make
it
about
something
that
the
users
can
you
know
something
that
they
can
get
out
of
it.
You
know
on
day
one
without
having
to
sort
of
buy
into
some
sort
of
a
grand
vision,
for
you
know
what
automation
means
to
to
those
of
us
that
have
a
lot
more
experience.
A
A
A
One
of
those
things
is,
you
know
the
the
platform
behind
the
scenes.
You
know
specifically
syringe,
which
is
the
back-end
Orchestrator
for
super
brain
it
out
as
well
some
of
the
front-end
stuff.
You
know
we
really
built
that
originally
as
I
want
to
say
proof-of-concept,
but
you
know
our
goal
wasn't
to.
You
know,
sit
behind
the
scenes
and
build
this
thing
and
have
it
be
perfect,
and
only
after
it's
perfect,
you
know,
release
it
to
the
world.
A
Rather
we
we
wanted
to
get
it
out
as
early
as
possible,
and
so
there's
some
trade-offs
that
we
made
it's
I,
don't
have
a
white
board,
but
to
get
into
some
of
the
specifics,
you
know.
There's
no
database
behind
any
of
this.
There's
no
way
to
track
state
for
who's
got
one
lesson
other
than
storing
it
in
memory
which
you
know
has
trait
has
the
trade-offs.
Is
that
fast
is
as
simple
absolutely
and
that's
exactly
why
we
did
it
that
way.
A
But
you
know
that
also
has
its
trade-off.
That
means
that
means
you
have
sort
of
essentially
a
single
point
of
failure.
So
what
we're
gonna
we're
gonna
start
addressing
that
we
don't
have
necessarily
any
sort
of
design
specifics
around
this,
but
I
can
tell
you
what
we
won't
do
we,
what
we,
what
we
won't
do
is
make
this
into
some
sort
of
a
you
know.
You
got
a
you,
got
a
learn,
how
web
development
works,
or
you
know,
database
operations
work
in
order
to
contribute
a
lesson.
That's
not
going
to
happen.
A
You
know
we're
gonna,
have
the
same
curriculum
as
code
model
and
we're
simply
just
going
to
build
tooling.
That
allows
you
to
feed
that
curriculum
store,
didn't
get
as
code
into
the
platform
and
that's
it
so
we're
gonna
be
built.
We're
gonna,
we're
gonna
build
some
resiliency
into
the
platform.
Where
do
things
like
you
know?
Having
a
you
know,
multiple
active
copies
of
syringe
running,
because
once
you
have
everything
stored
in
an
external
database,
you
can
start
doing
stuff
like
that.
A
A
There's
a
few
other
things
in
1.0
that
we're
thinking
about
I
want
to
talk
about
gamification.
So
gamification
is
an
interesting
word
because,
typically
in
our
circles
it
tends
to
be
kind
of
gross
I'm.
Being
honest,
it's
not
exactly
the
the
best
way
to
talk
to
technical
people
about
what
you're
building,
in
my
opinion,
I
think
gamification
is
actually
kind
of
cool
just
as
long
as
it's
done
appropriately.
It
can't
be
all
about
the
gamification.
A
You
can't
just
say
like
here:
we're
gonna
go,
do
some
gamification
and
then
say
like
you
know,
build
something
that
is
just
way
over
the
top
and
not
serious.
So
for
us,
it's
a
lot
less
about
just
making
a
game
out
of
this
and
much
more
about
you
know
you
guys
you're
spending
a
lot
of
time,
learning
these
concepts,
whether
it's
a
nunnery
labs
or
not,
and
I-
think
that
that
should
be
recorded
somewhere.
I.
Think
that
should
be
recorded
not
only
for
yourself,
but
also
for
you
know,
potential
future
employers.
A
I
went
through
a
similar
program
when
I
was
when
I
was
in
college,
actually
the
ipv6
age
program
from
Hurricane
electric.
They
offered
this
amazing
kind
of
like
a
certification,
although
it's
not
a
certification
in
the
sense
of
like
a
Cisco
surgeon
apart,
but
it's
it's,
you
know
they
certify
you
it's
free,
but
you
have
to
sit.
You
have
to
provide.
You
know
technical
expertise.
You
have
to
you
know
be
able
to.
You
have
to
be
able
to
do
certain
things
in
production.
They
have
ways
of
validating
that.
A
A
You
know
again,
I,
don't
know
if
we
have
specifics
to
show
but
something
we're
thinking
about.
By
the
way,
we
will
be
exposing
a
lot
of
a
lot
of
our
thoughts
in
in
writing.
You
know,
as
the
day's
progress
that
way,
you
guys
can
actually
provide
comments
and
feedback,
but
just
not
yet
not
today,
there's
a
few
other
things.
A
Nri
labs
doesn't
support
mobile
right
now
and
we
we
know
that
that
sucks,
we
don't
like
that
either
and
honestly
I
the
more
I
think
about
it.
The
less
I
feel
like
there's
a
really
good
reason
for
it
other
than
the
fact
that
the
CSS
and
the
HTML,
and
all
that
isn't
it's
just
not
optimised
as
it
should
be,
so
we're
gonna
be
fixing
that,
especially
if
it's
as
easy
a
problem
as
I
think
it
is
to
solve
we're
gonna
be
making
sure
that
that
gets
fixed,
there's
a
few
other
things.
A
A
You
know
what,
if
we,
what
have
we
learned?
What
have
we
learned
in
the
past
year?
We
learned
a
few
things.
First,
off
I
mean
the
idea
is
clearly
is
clearly
powerful
one.
You
know,
we've
got
this
idea
of
fairly
democratized
learning,
which
is
cool
and
it's
all
stored
and
get
and
fall.
You
know
version
controlled
and
you
can
contribute
to
it.
Just
like
you
contribute
to
any
software
project.
A
That's
that's
pretty
cool,
but
you
know
you
you
there
there's
one
thing
that
I
that
I,
that
I
think
we
could
have
done
a
little
better
job
at
is,
is
improving
the
contributor
experience.
I,
think
it's
a
I,
think
it's
a
cool
experience,
but
for
most
people
it's
probably
not
the
easiest.
Let
me
let
me
let
me
let
me
explain
why
so
we've
got
we've
got
this.
You
know
git
repo
called
NRI
labs
curriculum
and
it's
it's.
You
know
houses
all
of
the
files
that
are
necessary
that
are
necessary
to
teach.
A
A
So,
in
order
to
contribute
to
that,
you
need
to
know
a
few
things
you
need
to
know
how
it
works.
You
need
to
know
how,
to
you
know,
make
a
commit
push.
You
know
push
files
push
commits
rather,
and
you
need
to
know
how
to
do
certain
things,
and
not
only
that.
That's
that's
just
one
aspect.
You
obviously
also
have
to
know
how
the
whole
antidote
platform
works,
because
it's
it's
it's
all
custom
software.
This
isn't
something
that
you
can
like
go.
Google
for,
and
you
know,
take
off
the
shelf.
A
You
you
have
to
sort
of
you
know,
learn
the
platform
that
we
built
and
and
contribute
to
that
in
our
sort
of
in
our
terms
which
isn't
easy.
It's
it's
all,
it's
all
totally
new
and
we
and
we-
and
we
know
that
the
thing
is
you
know
we
came
out.
You
know
last
year
with
this,
you
know,
create
labs
in
an
in
a
curriculum,
is
code
way
so
that
you
know
people
that
want
to
learn.
Automation
can
do
so
as
easily
as
possible
because
all
they
have
to
do
is
go
to
a
web
browser
right.
A
So
what
we're
planning
is
to
come
full
circle
with
that
it's
it's
no
longer
acceptable
for
me.
Personally,
it's
no
longer
acceptable
for
us
to
say
you
know
we
want
to
make
things
as
easy
as
possible
for
the
learner,
but
then
do
nothing
for
the
contributor
or
the
teacher
in
terms
of
improving
the
experience.
A
So
so
that's
that's.
That's
that's
something
we
want
to
that's
something
we
want
to
fix
anything
anything
that
we
can
do
to.
You
know
improve
the
the
way
that
the
way
that
people
contribute
to
the
to
the
curriculum,
whether
that's
better
tooling,
whether
that's
a
better
contribution
model,
meaning
you
know
we
want
the
file
store
to
get,
because
that's
there's
value
in
that,
but
maybe
maybe
abstracting
it
away.
So
you
don't
have
to
know
everything
there
is
to
know
about
get
in
order
to
contribute
things
like
that.
A
We're
also
playing
with
a
few
ideas
like
contributing
in
the
browser
kind
of
like
you.
You
can
learn
in
the
browser.
What,
if
you
could
contribute
all
in
the
browser
without
having
to
know
anything
or
install
anything?
It's
the
same.
It's
the
same
value
proposition
for
learning
applied
to
the
you
know:
the
curriculum,
authors
and
the
teachers.
So
that's
that's
something
we're
playing
with
of
the
ideas
that
I
have
I
probably
have
the
least
specifics
around
that,
but
I
can
tell
you
I'm,
probably
most
excited
about
it
of
the
ideas
that
we
have.
A
Because
here's
the
thing
I
know
that
there
is
so
much
good
automation,
content
out
there
really
really
good
content
and
it's
not
gonna
help
us
and
I
mean
us,
as
in
the
industry.
I
don't
mean
us,
as
as
in
juniper
at
all,
I
mean
us
as
in
the
industry
as
if
we,
if
we
just
hope
if
we
have
a
barrier
to
being
able
to
contribute
that
knowledge,
that
fundamental
knowledge,
it's
just
not
gonna
work.
What
I
want
to
do
is
you
know
my
mission
in
all
of
this.
A
You
know
when
we
went
out
and
set
up
set
out
to
build
this.
The
mission
is
and
and
has
always
been
to
highlight,
bright
spots
in
the
industry.
The
platform
itself
is,
you
know
it's
a
loudspeaker.
It's
a
loudspeaker
for
people
to
tell
the
message
of
what
they've
built
the
successes
that
they've
had
and
get
those
you
know
get
spread
the
love
as
it
were,
and
so,
if
our
loudspeaker
is
difficult
to
speak
into,
that's
that's
a
problem.
A
It
doesn't
matter
how
loud
the
loudspeaker
is
people
if
people
don't
feel
like
they
can
walk
up
to
it
and
tell
their
story.
That's
it's
not
gonna
matter,
so
we
know
that
and
we're
gonna
fix
it
and
I'm
pretty
excited
about
that.
Actually
is
the
more
I
think
about
this?
The
more
I
realize
this
is.
This
was
always
the
endgame
you
know
being
able
to
contribute
as
easily
as
you
can
learn
is
just
poetic,
so
I'm
real
excited
about
that.
A
A
So
that's
those
are
some
of
the
loose
loose
thoughts
that
I
have
around
this.
You
know
we're
gonna,
be
doing
a
lot
in
the
near
future
to
take
action
on
this.
Just
like
everything
else.
This
isn't
gonna
be
something
that
you
know
one
dot,
oh,
isn't
gonna,
be
something
that
we
sort
of
sit
behind
the
scenes
and
and
plan
ourselves
and-
and
you
know,
build
ourselves
like
that's,
not
gonna,
that's
not
gonna
work
for
us.
A
In
fact,
we
were
kind
of
self-conscious
about
doing
that
before
we
ever
launched,
because
you
know
we
wanted
to
make
sure
that
this
is
something
that
was
truly
useful
to
the
community.
But
what
so?
That's
like
that's
exactly
the
reason
we
launched.
You
know
as
early
as
possible,
making
the
trade-offs
we
did
because
we
wanted
to
get
it
into
the
community's
hands.
A
So,
similarly,
for
one
not
oh,
when
we
talk
about
solving
a
lot
of
the
problems
that
we've
seen
over
the
past
year,
such
as
the
contributor
model,
the
fact
that
syringe
is
effectively
a
single
source
or
a
single
point
of
failure
when
we're
looking
at
solving
these
problems,
what
we're
gonna
be
doing
is
we're
gonna
we're
gonna,
be
first
off
publishing.
All
of
the
1.0,
like
you
know,
design
documentation.
The
plan
for
like
when
certain
features
are
planning
to
be
implemented.
We're
gonna
continue
to
do
this.
A
You
know
specific
release
planning
so
whenever
we
know
of
and
whenever
we
have
an
upcoming
release
like
right
now,
the
next
release
is
0.40
and
if
you
go
to
github
on
the
NRA
learning
organization,
you'll
be
able
to
see
the
full
plan
where
we
have
issues
triage
of
things
that
we
want
to
implement
and
things
like
that.
But
if
you
want
to
see
the
broader
plan,
we're
gonna
have
a
doc
that
you
can
always
go
to
to
say:
oh
cool,
so
here's
the
road
to
one
auto.
A
You
know
due
to
be
released
in
October
of
2019.
Where
are
we
on
that
road?
Where
are
we
on
the
path
to
one,
not
Oh
in
that
time
frame?
So
you
know
we're
gonna,
be
publishing.
All
of
that.
We're
gonna
make
sure
that
you
guys,
you
know
you
all
have
a
chance
to
contribute
to
the
roadmap
that
you
have
a
way
to
share
the
opinions
of
where
you
you
know,
of
where
you
think
the
project
should
go
and
the
usefulness
that
it
should
have.
A
We've
already
got
a
lot
of
people
providing
feedback
and
we're
incorporating
those
that
feedback
into
the
plan.
For
instance,
the
there
was
a
guy
that
popped
up
on
the
street
on
the
chat
just
a
few
days
ago,
actually
with
all
kinds
of
really
cool
ideas,
and-
and
you
know
we
wouldn't
have
thought
about
it-
you
know
we're
only
you
know.
Derek
and
I
are
only
two
guys.
You
know
we're
not
gonna.
Think
of
everything
there
is
certainly
so
we
actively
want
this.
A
You
know
we
want
people
to
provide
their
to
provide
their
feedback
and
to
provide
ideas,
because
without
you
guys,
you
know
we're
not
gonna
have
as
effective
of
a
project
as
as
we
as
we
can
and
Derek's
and
I.
You
know
the
goal
for
Derek
and
I.
It
has
always
been
to
build
something
useful
for
the
community,
so
it
doesn't
serve.
Anybody,
including
us
to
just
you
know,
go
build
this
behind
the
scenes.
We're
gonna
make
sure
everybody
has.
It
has
a
way
to
provide
input.
A
So
yeah
I
think
that's
I,
think
that's
it.
You
know,
like
I,
said
I
nothing
tangible
to
show
right
now
we
do
have
some
planning
documentation
that
we're
starting
to
build
out,
but-
and
you
know
when,
when
we
finished
when
we
finished
an
early
draft,
we'll
we'll
publish
it,
probably
as
a
Google
Doc,
maybe
whatever's
easiest
for
everybody
to
consume
without
you
know
signing
up
for
anything,
that's
what
we'll
do
and
yeah.
If
you
have
any.
A
If
you
have
any
questions
before
we
talk
about
any
of
that
stuff,
certainly
if
you
have
any
ideas
for,
like
you
know
a
big
feature
that
is
sort
of
like
one
dot.
Oh,
you
know
spiritually
aligned
with
a
wunderkind
of
thing,
something
that
you
might
have
thought
you
know
thought
about
before,
but
held
off
on
because
he
thought
it
was.
You
know,
maybe
too
big
or
too
too
early.
Let
us
know
you
know
if
there's
something
we
can
add
to
the
Wonder
roadmap.
A
Now
is
absolutely
the
time
because
we've
still
got
whatever
you
know,
six
months
or
four
five
months
whatever
it
is.
You
know
at
least
happy
know
around
half
a
year
until
until
the
timeframe
for
when
we
want
this
stuff
to
finish
up,
you
know
1.0
until
that
time
frame
comes
so
so
now
is
absolutely
the
time.
If
you
have
any
ideas,
please
share.
A
So
I
think
that's
it
thanks
for
bearing
with
me
this
morning.
This
is
a
pretty
informal,
but
hopefully
it
was
a
value.
Hopefully
you
could
hear
me
I'm
only
on
my
phone
right
now,
so
it's
not
as
if
I
can,
you
know,
see
the
stream
quality
from
from
here.
I'm
just
talking
into
this
as
loudly
as
possible,
so
I
can
make
sure
that
it
works
next
week.
A
Hopefully,
we've
yet
we'll
be
back
in
our
in
our
traditional
office,
setting
where
we
got
proper
microphones
and
not
noisy
naked
people
fountains
behind
us,
but
until
then
you
know
keep
it
real
and
let
us
know
let
you
know
keep
you
know,
let
us
know
for
how
we're
doing
and
how
we
can
how
we
can
do
better,
because
this
is
something
that
we're
very
passionate
about
about
building
something
that's
truly
useful
to
the
community.
So
it's
nothing
without
your
input,
.,
and
I
mean
that
alright
thanks
everybody.