►
From YouTube: Community Stream #14 - Update on v0.4.0 plan
Description
Broadcasted live on Twitch -- Watch live at https://www.twitch.tv/nrelabs
A
B
A
A
baby
dude,
you
know
I
think
around
two
or
two-and-a-half
three.
They
become
a
toddler,
something
like
that
yeah.
You
know
at
this
point:
they'll
still
gladly
eat
broken
glass
or
stick
their
fingers
in
electrical
sockets.
They
do
all
kinds
of
thing.
You
have
to
watch
him.
Dude
babies
have
no,
they
have
no
boundaries.
B
My
sister
went
my
older
sister
when
she
was
when
she
had
her
daughter
about
about
this
age
and
I.
Obviously,
I
didn't
have
any
kids
and
she
was
she
was
playing.
She
was
like
yeah,
so
it
turns
out.
Parenting
is
just
trying
to
keep
your
kids
from
accidentally
killing
themselves
like
every
day
all
day
and
I'm
like
okay.
I
can
see
that
yeah.
A
A
Yeah
we
had
that
that
was
that
was
Missy.
When
we
had
Eleanor
it
was
organic
foods
and
cloth,
diapers
and
organic.
You
know,
diaper
rash
cream
had
to
be,
or
had
to
be
organic
and
made
from
bee
wax
and
all
kinds
of
stuff,
and
it
was
it
was
gross
dude.
Let
me
tell
you
something:
it
was
gross
and
then,
when
we
had
her
second
baby
she's
like
yeah,
Kraft,
Mac
and
Cheese
and
disposable
diapers,
that's
what's
happening.
Yeah.
A
B
A
Yeah
yeah
talking
about
baby
diapers,
a
technical
scream
Wow.
Well,
there
is
a
couple
really
significant
changes,
including
one
that
I'm
very
excited
about.
I
know:
we've
talked
about
some
of
this
in
the
past,
but
they're
eminent
now
and
it's
theirs
and
it's
going
to
have
an
impact
on
and
how
how
the
project,
how
well,
how
the
how
the
project
carries
on
in
a
week
on
a
week
to
week
basis
and
we're
gonna
we're
gonna
talk
about
some
of
that
today.
A
A
B
You
sure
so
in
terms
of
imminent
changes,
I
assume
you're,
referring
to
a
lot
of
the
the
pipeline
changes
that
we've
been
talking
about
right.
Yes,
so
that's
one
of
them,
there's
a
bunch
of
things
actually,
I
think
what
might
be
useful
is
just
talk
really
quickly
about
the
next
release,
because
I
don't
know
what
I
don't
know
what
it
is
about
the
last
few
months,
but
you
know
we,
you
know
one
of
the
things
that
we
want
to
do.
Let
me
let
me
take
even
one
further
step
back
one
of.
B
You
know
everything
I
say
right
now
is
we'll
talk
about
like,
like
you
know
that
what
the
past
few
months
have
looked
like.
Obviously
you
know
when
it
comes
to
like
releasing
new
versions
the
platform
it's
something
that
was
is
pretty
centralized
to
the
to
the
two
of
us,
but
our
intention
is
overwhelmingly
that
more
people
get
involved.
B
Somebody
else
can
be
in
charge
of
it
and
a
lot
of
open
source
projects
work
that
way
where
you
have
a
specific
set
of
you
know
scripts
or
workflows
that
are
designed
to
automate
the
release
of
a
certain
project,
and
you
know
a
lot
of
folks
on
the
project,
especially
if
they're
like
corporately
back
they'll
rotate
engineers
through
that
process,
so
that
everybody
can
get
involved
with
it.
It's
a
lot
better
than
having,
because
I've
worked
in
both
environments.
I've
worked
in
that
environment.
A
B
B
B
And
what
that
means
is
we
haven't
had
a
new
content
on
the
main
NRA
website.
Since
then,
it
also
means
we
haven't
published
a
version
of
the
platform.
Now,
of
course,
if
you've
been
working
on
lessons,
you
have
had
access
to
the
latest
version
of
all
of
that
stuff,
but
it's
not
into
a
release,
which
means
again
it's
not
in
it's,
not
in
the
main
NRA
lab
site,
because
we,
you
know
the
NRA
website.
We
only
use
version
releases
for
stability
reasons.
B
B
Cuz
we're
going
to
be
talking
about
the
the.
What
we
view
is
the
things
that
need
to
be
done
by
0.40.
What's
the
next
release
and
yeah,
so
we
want
to.
We
want
to
break
things
apart
a
little
bit
and
make
it
so
that
we
don't
feel
like.
We
have
to
boil
the
ocean
to
get
a
release
out
because
well,
that's
not
technically
true.
It
can
feel
like
that's
true,
especially
for
major
releases
like
the
0.4
dot
zero.
You
know
we've
been
kind
of
on
0
to
3x
for
a
while.
B
So
that's
part
of
the
problem,
I
think
so
anyway,
all
about
to
say
we
you
know.
Unfortunately,
we
haven't
done
a
release
in
a
while.
We
have
pushed
a
lot
of
changes
to
the
latest
version.
So
if
you,
if
you've
been
paying
attention
to
like
you
know
if
you've
been
building
lessons
with
self-medicate
or
something
like
that,
you've
still
been
getting
updates.
It's
just
that.
B
There's
a
lot
of
there's
actually
a
lot
of
lessons
that
we
haven't
published
yet
because
we
haven't
created
a
new
release
and
even
and
and
there's
actually
a
task
that,
even
if
we
did
create
a
release,
some
lessons
wouldn't
make
it
in
so
there's
just
there's,
there's
a
there's
a
lot
of
I.
Think,
though,
that
moral
of
the
story
here
is
there's
a
lot
of
there's
a
lot
of
work
in
progress.
That's
just
been
stalled
out
for
a
long
time,
and
so
we
want
to
solve
that.
B
B
Let
me
share
my
screen.
If
I
could
find
it
there,
it
is
all
right.
Can
you
see
that
yep
so
I've
covered
this
on
previous
streams,
but
I'll
just
reiterate
it
every
time
we
want
to
plan
a
release,
we
we
create
a
project
at
the
org
level.
So
if
you
go
to
network
reliability,
engineering,
x'
github
organization
here
and
you
click
projects,
you'll
see
at
least
always
you'll-
see
at
least
one
usually
two,
because
what
I
do
is
I
is
I,
create
this
project
plan
for
0.40,
for
instance,
and
as
I
work
on
that
I.
B
So
the
moral
of
the
story
is
this
project
is
existed
for
a
while,
because
we've
been
wanting
to
do
0.40
for
a
while,
but
there's
a
lot
of
really
big
tasks
in
this
in
this
prod.
In
this
release
that
we
want
to
get
done,
but
some
of
them
some
of
them,
we
we
want
to
actually
move
because
they're
just
too
big
and
probably
don't
need
to
be
done
that
urgently.
B
A
B
They
don't
need
to
be
done
in
this
release,
there's
a
bunch
of
other
things,
but
let's
say
well,
it's
actually
what
might
be
useful
and
it
and
toad
stop
me.
Stop
me
if
you
have
questions
or
if
I
need
to
slow
down
or
do
something,
but
what
I
would
actually
really
like
to
do
is
just
go
through
all
of
these
issues
and
and
either
pod
them
to
the
next
release
or
explain
what
needs
done
and
that
way
people
can
understand
the
work
that
he's
done
and
maybe
and
maybe
help.
B
A
B
B
If
you
read
that
the
long
and
short
of
it
is
to
make
that
optional,
so
that,
if
you
so
so,
you
can
opt
in
to
making
that
not
happen.
So
if
you
really
really
don't,
if
you
really
really
want
to
take
that
on
yourself,
you
certainly
can
we'll
still
use
this
in
production.
So
we
will
use
this
option,
but
Olivier
wants
it.
So
we're
and
it's
it's
easy
to
do
you
just
add
a
config
flag
to
say:
hey,
don't
create
a
network
policy
and-
and
we
want
so
that
that's
easy
to
do.
B
We
can
keep
this
for
this
release.
Yep
interface
down
trigger,
not
firing
st
lesson.
This
is
this
is
a
bug
I
identified
because
I
was
going
through
when
I
was
when
I
was
going
through
and
identifying
or
changing
all
of
the
lessons.
In
the
current
curriculum
to
the
new
endpoint
format,
I
noticed
that
the
st2
lesson
was
broken.
There's
a
specific
thing,
that's
broken,
that's
described
in
the
issue.
B
I
do
want
to
figure
that
out
before
before
the
next
release,
because
in
production
it's
fine,
it's
it's
clearly
something
that
has
happened
between
then
and
now
so
I
want
identify
that
yeah
all
right.
The
third
one
is
a
little
more
complicated
moving
to
packets.
So
if
you've
paid
attention,
I
think
we
talked
about
this
briefly.
We
you
know,
we
have
a
number
of
things
that
we
want
to
do,
and
one
of
them
is
is
moving
to
a
bare-metal
as
a
service
provider.
I
feel
this
is.
B
Resources.
Unfortunately,
there's
other
images
that
don't
that
aren't
that
that
easy
that
require
a
little
bit
more
and
nested
virtualization
kills
them.
So
we
want
to
be
able
to
move
to
a
bare-metal
as
a
service
provider
and
and
I'll
tell
you
the
two
lessons
that
use
that
they're
really
unusable
until
we
do
this,
which
means
that
until
we
do
this,
we
can't
publish
them
there
in
PTR,
but
they
just
don't.
You
can
load
them.
If
you
want
they,
they
take.
B
Unfortunately,
there
there's
actually
a
number
of
things
that
we
need
to
do
even
before
that
and
so
Wow
I.
Absolutely
don't
I
wouldn't
do
this
if
it
wasn't
the
case,
because
I
do
think
this
is
very
important.
I,
don't
see
this
getting
done
before
0.40
and
it's
really
to
be
honest.
It's
not
even
it's
not
even
really
a
release.
Specific
thing,
that's
I
think
that's
the
main
thing
because
this
can
happen
outside
of
a
release:
cadence,
you'll
notice.
This
is
in
the
antidote,
ops,
repo.
This
is
about
how
we're
running
into
those.
B
So
this
doesn't
really
affect
I,
think
the
release
process
for
the
project
or
for
the
platform
specifically
or
even
the
curriculum.
Once
we
do
have
packet
as
a
back-end,
we'll
move
those
two
lessons
from
PTR
to
prod.
So
that
will
happen,
but
I,
you
know,
I,
don't
think
we
need
to
I.
Don't
think
we
need
to
keep
this
in
the
in
this
project
plan.
Okay,
I
will
I,
won't
remove
it.
What
I'll
do
is
I'll,
just
move
it
to
0.40.
B
If
I
can
it
lets
me
scroll
down
so
I'll
remove
from
that
and
then
I'll
put
it
on
0
to
4.1.
That
way
at
least
I
have
a
reminder.
That's
another
thing
I
like
to
do
which
I
probably
shouldn't
do
but
I
use
that
as
a
way
of
making
sure
I
don't
lose
really
important
issues.
Yeah,
okay,
various
labs,
cleanup
tasks.
This
is
this
is
a
bunch
of
antidote
web
fixes.
B
B
So
what
I'm
gonna
actually
do
is
remove
this,
because
the
only
thing
that
I
wouldn't
want
to
move
out
of
this
project
is
the
is
the
copy
and
paste
broken
part.
So
that's
fine,
I'm
gonna
remove
this
and
the
other
ones.
The
other
ones
are
not
urgent.
The
copy
and
paste
has
its
own
issue
so
we'll
keep
that
in
there
once
we
get
to
it
alright.
B
Right
yeah
so
I
the
original
issue.
He
opened
this
this.
Actually,
this
issue
is
going
through
a
few
different
changes.
I
I,
don't
think
the
original
reason
he
opened
it
is
is:
is
there
any
more
I
think
we
answered
that
properly?
His
initial
concern
was
that
we
didn't
support
connection
between
non
devices-
yeah,
that's
technically,
not
true,
but
in
in
the
previous
version
of
syringe,
which
is
recent,
which
has
since
been
more
than
fixed
because
it's
been
revamped
entirely.
The
actual
cause
was,
if
you
don't
have
any
devices
in
your
in
your
lesson
definition.
B
Then,
then
it
wouldn't
support
any
connections
at
all
which,
which
was
not
ideal,
but
anyway
the
whole
devices
concept
has
been
blown
away.
So
none
of
that
matters
anymore
at
the
end
of
the
the
one
thing
that
he's
not
still
not
clear
on
is
the
the
the
scene
I
plugin
still
assigned
IP
addresses
to
to
each
of
these
networks,
and
he
was
calling
out
the
fact
that
they
get
the
same
IP
address.
B
Mom
I
I
want
to
know
I
want
to
make
sure
that
he
could
still
pass
traffic
on
any
address
that
he
wants,
because
that's
what
my
experience
has
been
once
that's
confirmed:
I'm
I'm
gonna
just
modify
the
cni
config
to
not
provision
an
IP
address,
because
these
are
these.
These
segments
are
just
layer,
two
segments
or
just
Linux
bridges.
The
fact
that
an
IP
address
is
assigned
doesn't
actually
matter,
because
you
can.
You
could
change
that
yeah.
A
B
I'm,
just
waiting
for
more
info
on
that
I.
Don't
think
much
work
needs
done
if
any
so
I'm
happy
to
keep
that
in
here
and
just
get
some
clarity
from
him
Brian.
If
you
watch
just
please,
let
me
know
what
you
think,
because
I
don't
think
that
that's
gonna
require
a
lot
of
work.
If
anything
I
did
skip
over
this,
this
isn't
actually
an
issue.
It's
just
a
little
card,
I
created
I
might
end
up,
creating
an
issue
out
it
or
I
might
punch
it
to
the
next
release.
B
It
looks
like
I
can't
move
it
until
I,
convert
it
to
an
issue,
I
guess
anyway.
I
will
I'll
do
that
later.
Basically,
right
now,
the
V,
the
V
key,
affects
disc
images,
because
we
still
only
have
a
few
images
and
the
projects
are
it's
okay
that
we're
doing
this
thus
far,
but
what
I
want
to
do
is
I
want
to
set
us
up
for
long-term
success,
which
is
storing
all
of
our
images
locally
or
not.
Look
couldn't
not
storing
our
images
locally.
B
That's
what
we're
doing
right
now,
so
I
have
a
vq
FX
image
on
my
laptop
and
so
in
the
in
the
very
rare
event.
I
think
we
haven't
done
this
in
like
half
a
year,
but
in
a
very
rare
event
that
we
need
to
update
one
of
the
vqf
x
images
I
run
the
docker,
build
on
my
laptop
and
then
push
it
very,
very,
not
ideal,
obviously
so
long
term.
What
I
want
to
do
is
I
want
to
add
those
disk
images
to
our
own
GCE
bucket.
B
It's
kind
of
like
an
s3
bucket
from
Amazon
and
then
the
docker
build
would
just
download
those
images
from
that
location
and
that
way
anybody
can
run
the
build
yeah
and
one
of
the
things
that
I'm
going
to
talk
about
soon
is
actually
running
the
image
creation.
The
image
build
process
in
our
release,
workflow.
So
that's
another
improvement
that
I
want
to
make
so,
but
that
can
happen
anything
this
honestly.
This
is
probably
something
that
I
want
to
just
add.
To
said
that,
let
me
just
do
that
right
now.
B
Actually,
before
I
forget
delete
note:
yes,
yes,
yes
and
then
I
will
add
it
here,
I'll
I'll
get
to
this
eventually.
This
is
like
the
big
issue.
I
want
to
talk
about.
This
is
kind
of
a
junk
drawer.
At
the
moment,
ok
moving
quickly
move
of
Jupiter,
page
2
docks.
This
is
pretty
straightforward
right
now
we
have
a
dedicated
sort
of
static
page.
If
you
go
to
what
was
it
I
think
it's
Jupiter
Lam
guides
dot
HTML?
No,
that's
not!
It.
B
B
There
is
actually
a
page
in
the
docs
that
explains
this
from
like
a
lesson
builders
perspective,
but
there
is
not
a
page
from
the
lesson
learners
perspective
like
if
you're
using
a
lesson,
what
are
jupiter
notebooks
and
how
can
you
use
them
and,
like
literally,
how
do
you
navigate
through
them
right
now
that
documentation
is
not
in
our
Doc's
but
rather
built
into
antidote
web,
which
was
useful
initially,
but
it's
not
now.
It
doesn't
make
sense
to
have
that
in
the
in
in
the
actual
web
UI
so
well.
B
This
is
just
simply
really
a
copy
or
cut
and
paste
exercise
from
the
latter
to
the
former
okay,
so
that
I
that's
fine.
We
can
do
that
in
0.4.
As
your
again
doesn't
take
a
lot
of
work.
Oh
I
see
it
looks
like
I
skipped
this
separate
lesson,
catalog
in
a
separate
page.
You
know
this
is
interesting.
I,
don't
know
how
I
feel
about
this
I'm
curious.
What
your
thoughts
are,
basically
the
the
gist
of
that,
and
actually
let
me
go
to
PTR,
because
that's
what's
gonna
show
what
I
want
to
do.
B
If
you
go
to
lesson,
catalog
you'll
see
that
it
links
to
advisor,
slash
index,
dot,
HTML,
and
that
currently
has
the
layout
that
you're
familiar
with,
which
is
that
the
advisors
up
top
and
then
the
catalogs
below
it
what
I'm
and
then,
if
you
click
on,
if
you
click
on
the
advisor
it
just
goes
to
the
same
thing,
because
they're
both
on
the
same
page
yeah,
so
I
have
them
with
separate
menu
items,
but
they
just
go
to
the
same
location.
What
I'm
suggesting
is
that
we
break
them
out
into
separate
pages.
B
Okay,
because
there's
a
lot
of
things
that
I
want
to
do
with
the
catalog
itself.
Instead
of
having
these
like
three
columns,
I
want
to
do
something
a
little
more
dynamic
based
on
not
just
static
categories,
but
also
things
like
tags
and
maybe
search
queries
like
that.
My
gut
is
telling
me
that
that's
something
we
should
push
to
a
later
release,
because
that's
probably
gonna
be
a
decent
amount
of
work
and
I.
Don't
know
that
it's
that
urgent
from
anybody's
perspective
sure.
B
B
Okay,
now
we're
at
this
Jupiter
page,
so
we've
talked
about
that
alternative
images
POC.
What's
oh
we're
already
doing
this
I.
Don't
even
need
to
have
this
right
now,
because
we're
actually
doing
this
actively,
so
we
can
actually
close
this
I
think
it's
not
done
well.
Actually,
what
do
you
think
you're
working
on
the
cumulus
image
right,
yeah.
A
Yeah
talk
about
that
a
little
bit
sure
it's
it's
just
cumulus
in
a
VM.
Actually
we
talked
about
this
because
Brian
Brian
Linkletter
really
wanted
FRR
and
I
started
working
on
that
and
I
got
FFR
working
in
a
container.
The
problem
with
that
is
you
have
there
are
namespaced
sis
proc
properties
that
that
have
to
be
modified.
That
would
require
the
F
revoir
container
to
have
escalated
privileges
on
the
host,
and
we
can't
we
can't
launch
that
in
production,
so
it
makes
more
sense.
A
To
put
you
know
something
like
human,
actually,
any
network
device,
if
you
will
to
run
them
as
a
VM
inside
of
inside
of
a
container
and
and
that's
what
that's,
what
I
effect
of
Lee
did
with
cumulus,
which
you
know
it's.
You
know
and
then
there's
interfaces
that
are
that
you
map
to
bridges
inside
of
your
container
and
those
bridges
or
bridges
or
what
bridges
or
what
connects
you
to
to
the
other
containers
inside
of
the
lesson.
Topology,
so
that's
I
mean
that's
effectively.
I
mean
that's
effectively.
What
it
is.
It
works
fine.
A
B
Of
the
things
I'll
talk
about
after
we
go
through
this
release,
planning,
sir
science
is
weird
any
we're
gonna
be
one
of
the
things
that's
been
keeping
me
from
doing.
Release
work
actually
is
publishing
design
Docs
in
a
draft
form
from
the
little
mini
products
that
we
want
to
do.
We
have
about
six
mini
projects
that
each
represent
a
fairly
fairly
significant
amount
of
work,
and
one
of
those
things
is
is
changing.
The
way
we
represent
images,
so
using
docker
has
its
advantages
because,
of
course,
you
know
the
whole
docker
build
and
docker
file.
B
A
B
B
A
you
know
no
work,
it's
gonna
be
more
fundamental
than
that
like
this
is.
This
is
a
new
way
that
we're
gonna
do
endpoints,
because
there
are
pros
and
cons
to
each
each
each
each
approach,
and
what
we
want
to
do
is
is
preserve
the
current
experience
of
building
docker
images
while
providing
vml
a
level
isolation.
There's
there's
a
bunch
of
projects
out
there
actually
at
one
of
our
colleagues
Dimitri.
Just
let
me
know
about
one
of
them
and
it
looks
really
promising.
B
It
has
to
do
with
firecracker
from
AWS,
but
there's
tooling
built
on
top
of
it
because
fire
what
firecracker
does
is
they
use
like
little
mini
VMs
for
first
service
stuff
but
and
then
we've
I
think
the
company
we've
created
some
tooling.
On
top
of
that,
to
provide
the
dock
asked
experience,
I,
don't
remember
what
it's
called
notes.
B
It's
ignite,
it
was
called
I
haven't,
looked
at
it,
yeah
I
haven't
looked
at
it
like
in
detail
at
all
I
just
looked
at
the
link
that
Demetri
sent
me,
but
it
looks
extremely
promising
and
and
and
it
spiritually
Fino
sort
of
aligned
with
what
I
wanted,
which
was
you
know,
VM
level
isolation
without
sacrificing
the
current
user
experience.
That's
that's
the
end
goal,
so
anything
we
do
I
think
should
do
that
which
would
make
it
awesome
for
anything
we
want
to
do.
A
B
All
right
so
I
added
these
improving.
These
are
PRS
as
you
from
the
icon,
so
it
looks
like
I
built
something
but
I'm
not
gonna.
Go
to
detail
here,
because
they're
not
ready,
clearly
and
they're,
not
that
urgent,
so
I'm,
just
gonna
I'm,
gonna
punt
them
to
the
next
project.
It's
less
important
to
do
those
I
think
right
now
than
it
is
to
just
simply
keep
things
moving
along.
You
do
you
agree,
yeah,
yeah,
those!
That's
that's
easy!
Copy-Paste
is
broken.
That's
something
that
we've
identified
in
the
web.
B
You
are
it's
not
entirely
true
like
you
could
still
do
it,
but
you
have
to
use
the
you
have
to
use.
Right-Click
I
think
paint
copy
works
actually,
but
it's
paste
that's
broken
and
you
can
still
paste
if
you
right-click
in
the
terminal,
but
the
button
that
we
put
up
there
that
says
paste
is
not
working
for
some
reason.
So,
while
there's
a
workaround,
it's
still
something
that
we
want
to
fix
it.
So
we'll
leave
that
in
there
all
right
should
all.
It
should
also
be
pretty
easy
to
fix.
B
B
The
the
effects
hole
issues
these
are
actually
tightly
coupled
with
the
move
to
packet,
so
I'm
gonna
move
this
as
well
yeah,
because
we
know
that
it's
gonna
work
properly
unless
it's
running
on
packet,
so
we'll
punt
that
building
a
self-service
automation
system
on
top
of
media
is.
This
is
an
exciting
lesson
that
I
want
to
build,
but
I'm
gonna
punt
it
it
actually,
the
the
the
reason
I
wanted
to
build
this
for
this
release
is
because
it
uses
a
web.
B
You
a
little
the
the
endpoints
change
included,
a
new
functionality
called
presentations
and
one
of
the
presentation
types
is
HTTP,
which
does
a
little
iframe,
and
this
lesson
actually
uses
that
and
it's
there.
Actually.
This
lesson
is
the
reason
why
I
started
thinking
about
building
that
functionality
at
all,
and
so
because
that
functionality
now
exists
in
the
proper
way.
I
wanted
to
put
in
a
lesson
that
highlights
that.
B
But
there's
no
way
I'm
gonna
be
able
to
get
to
it
this
week.
So
while
it's
kind
of
silly
that
there's
not
like
a
flagship
lesson
to
highlight
that
new
functionality,
which
does
exist
and
works,
it's
just
not
gonna,
be
feasible
for
me
to
get
to
get
to
it.
You
know
if
I
think,
if
I
do,
if
we
do
get
through
all
these
tasks,
I'll
consider
doing
it
if
there's
time
left
but
for
I
think
the
right
calls
to
punt
it.
B
Okay,
I,
don't
like
that,
because
I
like
to
have
a
lesson
that
highlights
a
new
functionality
instead
of
just
saying:
hey,
this
functionality
exists.
Good
luck,
finding
out
how
it
works,
are
good
luck,
seeing
it
in
action
because
you
can't
but
I
think
it's
still
the
right
call
user,
editing
improvement.
This
is
definitely
punchable,
because
it's
just
a
it's
a
feature
enhancement,
that's
you
know
improving
and
basically
improving
the
way
that
people
edit
stuff
inside
of
the
inside
of
the
terminal,
so
I
have
no
problem.
Punting.
B
Gonna,
add
it
to
0.4
dot,
1
I'll,
open
it
as
a
new
tab
and
then
what
I'll
do
is
I'll
add
it
to.
You
can
see
that
we've
punted
this
a
few
times,
I'll
add
it
to
the
the
mini
project
for
antidote
web.
We
actually
have
another
mini
project
which
is
for
revamping
antidote
web
and
the
reason
we're
doing.
That
is
because
we're
actually
engaging
a
vendor
to
help
us
with
some
of
that
heavy
lifting,
and
so
while
we
won't
have
them,
do
everything
in
our
wish
list.
B
Oh
yeah,
like
spell
checks,
I'm
punching
this
because
we're
not
adding
a
lot
more
content
for
this
release.
This
is
basically
I.
I
spend
one
of
the
things
that
we
in
and
now
Derek
now
that
you're
doing
routes
for
the
curriculum,
I
imagine
this
is
true
for
you
as
well.
A
lot
of
the
reviewing
time
for
curriculum
PRS
is
spent
doing
basic,
like
spell
checks
and
grammar
checks,
and
there
are.
B
B
Okay,
I'm
gonna
skip
over
this,
because
this
is
the
last
thing.
I
want
to
talk
about
interactive
wizard
for
building
a
new
lesson
in
a
new
collection,
absolutely
printable,
that's
nice,
but
definitely
not
something
we
need
to
do
by
the
end
of
the
week
using
certificate
based
authentication
instead
of
a
static
password,
definitely
plentiful,
because
that's
gonna,
that's
actually
gonna
require
a
decent
amount
of
work,
so
definitely
plentiful,
confusing
lesson,
directory,
parameter!
B
Yeah
yeah
yeah
because
there
yeah
exactly
there's
an
environment.
It
used
to
be
that
there
was
an
environment
very
called
lesson
directory
and
I
think
even
in
the
last
release,
I
changed
it
to
be
curriculum
directory,
so
yeah
I'm,
just
gonna
close
that
that's
definitely
done
view
source
on
github,
so
I
want
a
button
on
the
web
front-end
that
basically
allows
you
to
go
to
the
source.
Just
like
you
have
like
on
a
doc
site.
You
can
say
like
edit
on
github.
For
anything.
B
That's
stored
in
github
definitely
should
do
this
and
it
probably
will
be
that
hard,
but
I
would
say
definitely
punt
able
as
well,
because
it's
not
super
critical.
What
do
you
think
yeah?
That's
fine!
All
right,
nearing
the
end,
Center
around
curriculum,
again
I!
Don't
like
you
having
this
in
here!
This
is.
This
is
exactly
finished.
It's
done!
B
B
Is
basically
zooming
out
because
now
now
we're
not
just
now,
it's
not
just
lessons
that
are
the
that
are
the
it's
not
just
lessons
that
are
the
resource.
Now
it's
it's
collections
and,
and
there
will
be
others
so
lesson-
authors
in
metadata,
ooh,
I'm,
gonna,
punt
this,
but
I
actually
want
to
also
open
it
in
a
new
tab,
so
that
I
can
remember
to
add
it
to
the
syringe
mini
project.
Okay,
because
I
think
and
well
actually,
to
be
honest,
I
think
it
might
already
be
in
there
so
anyway,
I'll
follow
up
with
that.
B
Definitely
plentiful,
though
this
is
one
of
the
things
that
I
want
to
talk.
One
of
the
things
I
wanted
to
do
for
a
while
is,
is
figure
out
how
to
attribute
contributions
beyond
just
who
initially
creates
the
lesson.
So,
like
imagine,
and
we're
actually
seeing
this
today,
we
had
somebody
create
a
new
stage
actually
too
too
recently
in
the
past
few
weeks.
Actually,
while
I
was
out
two
people
adding
stages
to
an
existing
lesson
and
those
contributions
were
awesome,
but
unfortunately
the
people
who
initially
contributed
those
lessons.
B
B
So
if
you
want
to
look
at
the
authors
for
a
particular
lesson,
you
can
click
it
go
to
their
github
pages
and
all
that
kind
of
stuff,
as
opposed
to
as
opposed
to
just
statically
like
saying
so-and-so
created
this
lesson
in
the
in
the
lesson
guide,
which
is
so
not
immutable,
but
it
doesn't
change.
Often
I
want
this
to
be
a
little
bit
more
dynamic
and
I
want
it
to
be
more
inclusive
of
people
who
don't
necessarily
create
lessons
from
scratch.
B
So
definitely
want
to
do
this,
but
I
would
say
not
urgent.
Definitely
doesn't
need
to
be
done
by
0.4
that
one
and
probably
couldn't
be
done
because
it
will
require
a
decent
amount
of
work,
so
I
will
punt
it
to
the
next
release,
but
I'll
say:
let's
keep
it
in
that
cadence,
okay.
So
what
that
means-
and
this
is
good
I'm,
proud
of
us,
because
that
means
we
now
have
six
big
two
dues
for
this
release.
B
Six
things
standing
in
the
way
of
us
actually
doing
the
release
and,
as
you
can
see,
I
do
have
also
a
few
things
in
progress.
So
I
won't
include
those
in
what
I'm
talking
about,
because
the
kind
of
self-explanatory,
one
of
which
actually
isn't
even
related
to
the
release,
so
I
might
even
punt
this.
But
oh
no.
B
Three
actually
require
a
lot
of
work,
so
I'll
leave
those
as
an
exercise
for
the
listener.
So
I've
talked
about
all
of
these
issues
on
the
left,
the
the
to
do,
meaning
the
things
that
haven't
had
work
started
on
them.
There's
six
and
all
of
them
seem
to
be
pretty
straightforward
to
do
so.
I'm
I'm
encouraged
even
more
because
of
that
there's
one
that
the
the
st2
troubleshooting
and
the
copy-and-paste
troubleshooting
might
take
a
decent
amount
of
time,
but
but
the
other
ones
definitely
won't,
and
even
those
won't
take
a
tremendous
amount
of
time.
B
I
would
expect
the
one
thing
that
will
take
a
lot
of
time.
Is
this
last
one
improve
build
and
release
process?
So
let
me
actually
open
this
in
a
new
tab.
That
way
you
can
see
what's
going
on
here,
as
you
can
see,
I
created
this
a
long
time
ago.
This
was
created
in
January
and
there
are
a
bunch
of
like
sort
of
subtasks
on
this
and
I've
accomplished
three
of
them,
so
you
might
notice
you
know
basically
building
and
publishing
binaries
for
syringe
in
addition
to
the
docker
image.
B
B
If
you
go
to
the
syringe
project
now
and
you
go
to
releases,
and
you
can
see
that
we
pre
compiled
binaries
for
most
major
platforms
and
you
can
just
simply
download
them,
you
can
still
compile
from
source
if
you'd,
like,
obviously
that
that's
an
option
for
you,
but
if
you
just
want
to
use
the
binaries
that
we've
built,
you
certainly
can
do
that
as
well.
Each
of
these,
each
of
these
archives
contains
two
binaries
one
for
syringe,
D
and
the
other
one
for
s
wires
anyway.
B
That's
an
example
of
something
that
we
have,
but
there's
a
lot
of
other
things
that
we
want
to
do.
That
I
think
are
important
in
general.
Some
of
these,
some
of
these
things
are
much
more
important
than
others
and
I
think
and
I,
and
what
I
would
like
to
do
is
is
actually
organize.
Even
these
subtasks,
because
I
think
improving
the
build
and
release
process
is
probably
going
to
be
a
long-term
ongoing
thing,
but
these
specific
tasks
are
much
more
immediate,
so
I
won't
go
into
detail
here.
B
B
We
only
build
the
platform,
and
so
again,
if
you
go
to
the
curriculum,
that's
kind
of
problematic,
because
what
that
means
is
all
of
these
images
in
the
curriculum
sort
of
stay
static,
and
if
you,
if
you
use
them
in
the,
if
you
use
them
in
a
lesson,
there's
no
way
to
sort
of
there's,
there's
no
release
for
each
of
these
images,
and
so
you're
still
gonna
be
on
the
hook.
For
you
know
managing
changes,
so
we
ran
into
this.
B
B
Think
that's,
that's
gonna
be
a
lot
of
work
because
that
means
we
have
to
build
every
single
image
for
every
single
release
and,
of
course,
that's
gonna
take
time
but
I
think
in
terms
of
preserving
or
eliminating
that
fragility
and
pretty
freakin
important,
so
I'll
leave
it
at
that.
There's
I
could
talk
for
horizonte'
to
these
subtasks,
but
I'll
leave
it
at
this.
B
Those
are
the
two
I
think
the
most
important,
subtasks
and
I
would
all
do
as
soon
as
we're
done
with
the
stream
is
I
will
organize
these
subtasks
into
sections
so
that
it's
clear
the
things
that
I
think
are
important
for
for
doing
before
the
next
release
and
then
the
other
things
I
think
are
important
to
sort
of
after
you're
out
for
the
you
know,
this
isn't
necessarily
part
of
you
know.
This
is
the
build
and
release
process
itself.
So
we
don't.
Actually
we
don't.
B
A
Yeah
I'm
in
particularly
excited
about
the
separation,
the
curriculum
from
the
platform
in
terms
of
release,
I
mean
we
that
that'll
allow
us
to.
You
know
get
to
a
point
where
we
have
at
least
some
new
content
on
a
weekly
basis,
even
which
would
be
which
would
be
fantastic,
yeah
and
and
I.
Think
people
are
waiting
on
that,
so
it
that
would
be
that'd
be
super
great
yeah.
The
only
the.
B
Only
thing
that
I
think
the
the
the
only
it's
not
a
drawback,
but
it's
something
that
we
definitely
have
to
start
that
we
have
to
think
about
that.
We
wouldn't
have
had
to
think
about
in
the
current
model,
which
is
compatibility
with
the
current
published
version
of
the
platform.
So,
basically,
you
know
the
platform
is
gonna
is
going
to
be
published,
it's
going
to
be
released
through
its
own
cadence,
and
what
that
means
is
you
know
the
the
the
release
cadence
for
the
curriculum
is
gonna
have
to
be
organized
such
that
you
know
you.
B
You
are
staying
on
top
of
new
features
that
are
in
the
platform,
and
you
know
you
only
use
you'll
only
use
features
in
a
lesson
that
are
that
are
in
a
published
release
of
the
platform,
because,
right
now,
what
we
do
is
is
because
everything's
version
the
same
way
and
released
at
the
same
time.
You
know
we
we
have
this.
We
have.
B
B
In
this
new
model,
though
I
think
what
we'll
end
up
doing
is
probably
being
like
one
release
behind
so
like
as
a
as
a
as
a
lesson
is
looking
at
new
features.
If,
like
you're,
building
a
new
lesson
that
uses
a
new
feature
in
the
platform,
that
lesson
won't
be
able
to
go
into
production
until
that
feature
has
made
it
into
a
release
of
the
platform
that
make
sense.
Yeah.
A
B
That's
another
thing:
we've
gone
back
and
forth
on
many
times
because
if
we
set
it
to
latest
that
means
people
have
to
be
on
top
of
on
top
of
the
platform
like
the
changes
in
the
platform,
but
then,
if
we
don't
set
it
to
that
than
some
people
and
we've
run
into
this
too
or
some
people
are
like
hey,
you
know:
I
want
to
use
this
feature
and
I
was
like
well,
okay,
you
got
to
set
its
latest
then
so
we've
actually
changed.
It
I
think
four
times
in
self
medicate.
A
B
A
A
B
A
B
So
what
one
of
the
things
that
I've
been
trying
to
do
lately
is
is
there
are
some
things
that
are
fairly
urgent,
that
I
got
to
do
myself
just
because
I'm
familiar
with
it,
but
in
whenever
possible,
if,
if,
if
it's
possible
for
me
to
take
a
step
back
and
just
document
what
needs
done
that
way,
other
people
get
up
to
speed
and
and
can
help
I'm
trying
to
do
that
whenever
possible,
literally
at
every
every
piece
of
work.
I
do
I.
B
Ask
myself
that
question
and
I've
known
for
a
long
time
that
some
really
big
things
need
done
like
syringe,
probably
needs
to
be
reelected,
not
totally
rewritten,
but
a
lot
of
the
components.
The
logic
within
it
needs
to
be
broken
out
and
there's
a
whole,
that's
a
whole
rabbit
hole
and
then
and
then,
of
course,
there's
an
Ida
web.
So
I'm,
not
a
web
developer.
B
That
kind
of
thing
which
we
already
talked
about,
that's
its
own
rabbit
hole.
So
we
basically
have
identified
about
six
rabbit
holes
and
I
call
them
mini
projects
because
they're
they're
smaller
than
then
the
the
project
itself,
because
they
usually
focus
on
one
component
but
they're
they're,
pretty
big
undertakings
and
each
undertaking
has
its
own
sub
task
hierarchy.
B
So
one
of
the
reasons
why
I
haven't
been
focusing
on
like
code
is
because
I've
been
building
documentation
around
that.
The
idea
is
that
you
know
I
create
a
draft,
it
won't
be
I'm,
not
gonna.
Finalize
and
I'm
gonna
put
something
up
there,
that's
in
draft
format
and
let
everybody
comment
on
it
and
we
can.
B
As
a
community,
we
can
figure
out
what
needs
done,
but
I'm
creating
the
first
version
of
each
of
those
documents,
and
each
document
will
focus
on
a
specific
mini
project
that
mini
project
will
have
its
own
sort
of
project
management
like
loosely
coupled
or
loosely
structured
around
that
that
way
people
like
if
like,
for
instance,
if
you
have
web
front-end
skills
and
that's
pretty
much
all
you
want
to
work
on
then
you'll
have
a
home
for
that.
Like
you'll
you'll
have
a
sort
of
mini
project
that
you
can
focus
on.
That's
a
concerted
effort.
B
It's
like
a
sprint,
so
to
speak.
So
that's
something
that
I'm
also
going
to
be
doing
and
and
one
of
the
things
that's
been
keeping
me
from.
Actually
writing
code
is
putting
in
the
long
term
work
of
documenting
what
needs
done
instead
of
just
doing
it
and-
and
that
takes
time
so
I'm
doing
my
best
to
get
that
finished.
I
think
doing
this
list
down
so
that
we
can
get
0.40
done
in
the
next
week.
B
Will
help
so
my
two
highest
priorities
are
probably
working
this
plan
down
to
completion
so
that
we
can
release
the
route
four
to
zero
and
then
sort
of
simultaneously
finishing
at
least
one
of
the
draft
documents
for
the
mini
project.
I
won't
be
building
all
these
drafts
at
once
and
then
releasing
all
six.
What
I'll
do
is
I'll
finish
one
and
I'm
one
again
when
I
say
finish,
I
mean
finishing
a
draft,
so
it
won't
be
done.
B
A
A
Did
you
just
leave
the
call
I
did
not?
Oh
you
just
left.
You
stopped
sharing
all
right
here.
We
go.
Okay,
all
right!
Well,
we're
actually
six
minutes
to
the
hour,
so
I
think
I
think
we
can
wrap
this
up.
That
was
good,
I'm,
very
happy,
you're
back
I.
Think
a
lot
of
people
are
happier
back
and
they
are
so
I'm.
You
know
I'm
ready
to
you,
know:
I
I
love
this
project
I
like
working
on
this
project,
so
I'm
rated
to
be
back
doing
just
this
project
all
the
time.
B
A
It'll
be
good,
all
right,
well,
I
think
we're
I
think
we're
gonna
wrap
it
up.
Then
I'm
I'm
cloud,
towed
Cielo,
UDT
Oh
ad
on
Twitter.
Give
me
a
follow
if
you're,
if
you
feel
like
it,
follow
the
main
project.
Nre
labs
at
NRI
labs
on
twitter
matt
is
at
m
IE
r
di
n
me
erdan.
Give
him
a
follow
as
well,
of
course,
join
our
community
at
community
network,
reliability,
data
engineering
and
join
our
discord,
a
link
for
which
is
provided
in
the
documentation
for
the
project.