►
From YouTube: Community Standup: 11/19/19
Description
Community Standup: Nov. 19, 2019
C
C
Making
breakfast
I
also
I,
don't
know
if
you
guys
had
issues
finding
the
link
to
the
stand-up
I.
We
we
still
need
to
figure,
can
I
have
like
an
internal
meeting,
invite
for
the
stand-up
when
we
originally
started
it,
and
it
still
has
the
old
juniper
networks
late,
so
I
had
to
go
to
the
forums
to
find
it,
but
the
forms
I.
C
B
A
C
A
C
A
C
A
D
A
You
so
that
you
know
you
get
a
custom
built
kernel,
that's
Verdi!
Oh
only
right,
we
eliminate
all
those
unnecessary
drivers,
so
it's
nice
and
tiny.
Then
we
then
it
installs.
Wherever
packages
makes
whatever
you
know,
user
additions,
it
has
to
make
group
additions
stuff,
like
that,
you
know
it
should
and
then
installs,
like
I,
said
any
pip
apt
packages
and
then
finally,
it's
you
know
some
shell
scripts
or
whatever
or
static
files
that
you
want
to
copy
over
and
potentially
execute
or
config
files,
static,
config
files,
and
it
should
be.
A
A
That's
what
mp3
is
about
so
I
don't
know.
If
anyone
here
has
the
experience
building,
custom
kernels,
but
there's
a
good
starting
point.
There's
a
project
called
firecracker
out
there
and
they're
their
whole
thing
is
what
they
call
micro
VMs,
which
is
so
it's
so
basically,
instead
of
what
they
do
is
they
launch.
Firecracker
is
like
a
cloud
cloudy
type
platform
right
and
it's
container
base,
but
what's
interesting
is
that
your
applications
do
not
reside
in
the
actual
containers.
What
happens?
A
Is
it
launches
a
container
then,
within
that
container
it
launches
a
virtual
machine,
but
that
virtual
machine
is
very,
very
tiny.
It's
and
they
call
it
a
micro
VM
and
the
way
they
accomplish
that
is
they
they
have.
They
very
meticulously
went
through
the
kernel
config
file
like
fur,
for
you
know
whatever
you
call
that
standard
the
standard
kernel
and
eliminated
like
90%
of
that
kernel
file,
and
it
was
like
I
said
before
it.
A
There
was
there's
all
kinds
of
stuff
in
there
like
PCMCIA
drivers
and
audio
drivers
for
10,000
audio
pieces
of
hardware
and
graphics
tablets
and
there's
all
together
when
they
they
went
from
a
three
gig
minimum
Debian
bill
to
150
mank
Debian,
build
by
just
eliminating
unnecessary
scuzzy
drivers
and
Ray
drivers,
and
just
just
all
could,
of
course,
graphics.
Drivers
like
all
kinds
of
things.
So
anyway,.
A
That's
so
where
I'm
thinking
we're
gonna
use
that
as
the
baseline,
there
are
some
things
we
have
to
add
back
in
to
that
custom
kernel
config,
they
disable
a
lot
of
networking
stuff,
and
this
is
a
Network
automation,
learning
platform.
So
I
kind
of
don't
want
to
do
that,
but
it
shouldn't
be
more
than
175
200
Meg,
with
a
base,
build
and
and
and
what's
interesting,
is
that
with
all
of
this
stuff
eliminated
this
kind
of
blows
my
mind.
A
A
Let's
say
you
know,
target
slash
whatever,
and
then
you
can't
route
to
that
directory
chr,
ot
and
that
basically
tricks
the
system
into
thinking
that
that
or
that
you
or
whatever
you're
running
with
the
true
command
it
tricks
it
into
thinking
that
that
directory
is
root.
And
then
you
can
run
this
thing
called
Det
bootstrap.
A
Of
that
true-
and
it
turns
it'll-it'll-
make
all
the
directories
and
basically
create,
as
if
that's
the
route
of
a
debian
build
and
then
and
then
you
can
turn
that
into
a
bootable
image.
So
that's
that's
effectively.
What
will
have
to
do
with
mp3
and
as
soon
as
the
sensible
tower
image
is
done,
I
have
to
focus
on
mp3
and
we
have
to
automate
this.
The
whole
process,
like
I,
said
so
that
it's
it's
a
lot
simpler
and
people
can
build
curriculum,
easier.
A
D
Idea
is
maybe
that
also
it
deals
with
distributing
the
images
so
that
they're
available
for
cooling
later
and
so
on.
So
it's
a
kind
of
a
standard
way
to
have
a
workflow
of
building
and
distributing
and
pouring
so
I'm,
not
sure
if
there
are
any
drawbacks
performance
wise,
but
at
least
in
terms
of
normalization
of
the
workflow
and
being
able
to
reuse,
maybe
other
images
and
and
customize
more
I
would
tend
to
rely
on
an
existing
project.
But
maybe
that's
not
the
best
way,
because
maybe
that's
not
the
purpose.
D
C
I
would
recommend
is
that
we
very
similar
to
what
we're
doing
with
all
the
other
many
projects.
What
whatever
they
three
needs
is
you
know
its
own
design
dog.
It
talks
about
all
the
options
in
the
open
list,
them
side
by
side,
provide
pros
and
cons,
and
all
of
that,
so
we
have
it
all
in
one
place
and
we
can
make
a
logical
decision
on
which
one
we
want
to
go
with
like
in
my
head,
the
last
time
I
looked
at
Qbert,
which
is
probably
months
ago.
C
It
seemed
like
it
wasn't
actually
dealing
with
much
of
the
images
stuff
and
much
more
on
just
like
the
runtime
options
of
like
starting
and
pausing
and
stopping
VMs,
which
wouldn't
really
need,
because
we
don't
care
about
stopping
VMs.
We
just
kill
the
kubernetes
pod,
that's
fine,
but
maybe
hit.
Maybe
it's
changed
and
I,
and
and
it's
all
speculation
honestly
until
it's
written
down
like
we
got
to
have
it
written
down
in
one
place
that
way
everybody
can
comment
on
it.
C
E
C
A
I'm
gonna
go
ahead
and
say,
though,
that
we
will
do
micro,
VMs,
that's
gonna,
be
the
outcome
just
because
it's
they
boot
faster,
they
consume
way
less
resources
and
we
get
way
more
way
more
out
of
the
resources
that
were
paying
for
in
the
cloud
very
tiny
images
and
that's
what
we're
gonna
do.
We
just
have
to
have
a
way
building
and
by
the
way
that
build
process
needs
to
be
automated
and
it
needs
to
be
repeatable
so
that,
whether
it's
nightly
or
weekly
we're
automatically
building
the
images
over
and
over
again
mm-hmm.
C
Yeah
we
are
that,
that's
that
that
part's
actually
I
think
the
most
exciting
part
about
this,
because
everything
outside
of
what
Derek's
talking
about
is
already
automated
so
like.
If
you,
if
you
look
at
the
images
that
are
that
are
currently
being
used,
they
have
make
files
and
they
have
to
support
that
make
docker
thing.
This
is
all
in
the
docs
so
that
that
part's,
automated
that
runs.
So
all
that's
needed
is
for
the
sort
of
intra
image,
automation,
stuff
to
get
done
and
hooked
up
to
that
make
docker
step.
C
And
if
you
do
that,
then,
like
literally
everything
is
automated
and
that
and
that's
exciting
in
the
same
way
that
it
I
mean
we.
We
do
have
that
actually
today,
but
it's
all
with
docker
images
with
no
VM
layer
at
all,
which
has
the
trade-offs
that
I'm
sure
Derek
Derek
talked
about
at
the
beginning.
You
know
we
have
to
basically
grant
them
privilege
mode,
which
is
that
which.
A
C
So
yeah
I've
took
notes
on
that.
I
basically
said
yeah
we're.
You
know
we're
gonna,
follow
the
lead
with
a
fire
cracker
project,
which
is
to
create
a
common
micro
VM
base
which
is
very
stripped
down
and
then
automate
the
installation
of
packages
on
top
of
that
and
well.
The
first
step
is
to
create
a
draft
sort
of
design
doc
that
talks
about
the
options
and
allows
people
to
see
at
least
what
you
know
tangibly.
What
we're
gonna
be
doing
and
see
what
the
options
are.
A
Okay,
so
that's
mp3
in
a
nutshell
and
I'll
I'll
tell
you
what
Olivier!
If
you
have
time,
why
don't
you
document
if
there
is
a
queue
for
image
process
or
recommended
one
for
a
cute
bird
I?
Don't
I
didn't
see
any
guidance
from
them
either
and
how
to
build
the
images
I
know
that
there
is
recommendations
to
do
a
micro.
Vm
kind
of
thing
was
gonna
run
Qbert,
but
if
you
find
that
please
there's
an
mp3
placeholder
now
inside
of
the
one
of
them
they
and
that
oh,
my
gosh,
and
that
repository
yeah.
C
A
There
I'm
gonna,
regardless
of
that
process
or
Nautilus
whatever
process
player
fire
cracker,
recommends
I'm,
probably
gonna
go
through
figuring
out
how
to
build.
Do
it
by
hand
anyway,
so
I
know
we
have
to
do
to
do
it
right
and
and
and
then
we'll
see.
If
those
tools
will
will
match
what
we
need
to
do.
I.
A
F
C
A
A
C
A
B
A
C
You
don't
to
read
it
no
I
more.
We
don't
even
have
really
have
to
discuss
it.
I
think
it
I
think
everything's
contained
there
if
everybody
wants
to
sort
of
like
digest
that
over
the
next
week.
That's
fine
too.
The
big
thing
for
me
is
like
to
be
honest.
I
use
self-medicate
as
as
extremely
important
to
the
health
of
the
project.
At
the
moment,
I
just
want
to
reiterate
that,
because
our
biggest
one
of
our
biggest
problems
is
that
we
we
have
there's
a
lot
to
do
and
we
just
need
bodies.
You.
C
There's
just
pissed
struggles,
so
I
would
say
like
if
we
can,
if
we
can
rally
around
that,
if,
if
we
can
have,
you
know
sort
of
somebody
step
up
and
say
like
look,
here's
the
plan
for
how
we
want
self-medicate
to
work
right
now,
here's
what
it'll
support
here's,
how
it'll
work,
here's,
what
kind
of
projects
it'll
use
and
here's!
Why
and
then
we
all
rally
around
that
I
think
that'll
that'll
be
very
meaningful,
but
that
doesn't
have
to
get
solved
today.
C
I,
don't
think
I
think
this
is
one
of
those
things
where
it's
actually
worth
taking
a
little
slow
and
thinking
thinking
meaningfully
about
what
needs
to
be
done.
So
we
can
circle
back
next
week.
I
think
and
that's
that's
totally
fine,
but
I
wanted
to
like
I
said
I
when
I
when
I
was
on
the
road
like
three
weeks
for
the
last
three
weeks.
C
C
You
know
coordinated
towards
towards
a
common
purpose,
and
that
purpose
is
stability
of
self
Medicaid,
because
I
just
want
to
highlight
not
not
yeah,
like
I
said
at
the
beginning
of
that
post
I,
don't
think
it's
actually
all
that
bad
I,
don't
think
it'll
take
a
lot
of
work
to
do
that.
I.
Think
the
thing
I
wanted
to
highlight
was
that
self
medicate
for
us
and
and
I
have
other
plans
to
make
this
less
true.
C
A
The
first
time
was
just
them
setting
up
a
server.
They
just
hadn't
really
done
that
in
forever
and
they
sort
of
walk
him
through
setting
up
in
Abood
to
server
the
second
time,
though,
and
we
had
the
script
that
we
were
using
to
start,
it
was
gone
so
said:
okay,
it's
vagrant,
so
your
Intel
and
your
on
Linux
and.
A
We
just
ran
into
issues
like
in
that
and
I.
We
cannot
use
vagrant
I'm
I'm
in
telling
Linux
it
just
it's
like
if
there's
three
nodes
in
a
lesson,
if
there's
two
nodes
in
a
lesson,
it
becomes
unusable,
slow,
like
it's
just
slow
and
I,
have
a
beefy
box
so
and
then
getting
lipfird
installed.
Lippert
is
no
longer
by
default,
supported
with
vagrant
and
there's
a
vagrant
lippert
vagrant
plugin.
A
Unfortunately,
it
doesn't
always
install
super-easy
there's.
Sometimes
if
you
have
other
Ruby
packages,
installed
leak
and
interfere
with
the
build
process,
and
if
you
have
a
vanilla,
18:04
like
a
boon
to
box,
it
installs
no
way
it'll
install
with
no
issues.
I
didn't
I
had
a
1904
box
and
I
had
Ruby
already
installed
for
all
the
projects
and
it
would
not
build
I
could
not
get
it
to
build
and
well
actually
that's
not
true.
I
got
it
to
work,
but
then
I
destroyed
my
box
in
the
process
and
I
had
to
rebuild
it.
A
So
I
went
and
I
decided,
I'm,
just
gonna
go
LTS
away
from
1904
and
then
with
before
I
put
anything
else
in
the
Box
it
installed.
Just
like
the
directions
say
it
will,
but
unfortunately
the
abouttwo
box
that
we
built
for
packet
butchers.
They
also
could
not
get
it
to
build
or
install.
So
we
really
need
to
nail
that
down.
A
lot
of
people
are
gonna,
be
using
Intel
based
boxes
with
Linux
and
in
so
far,
both
partners
that
we're
talking
to
are
using
Linux
with
Intel
CPUs.
So
he
we
have
to.
A
C
Think
I
think
I
mean
this
is
the
struggle
right
like
we
like.
None
of
the
reasons
we
moved
to
vagrant
lists
so
that
we
could
support
more.
You
know
the
the
mini
cube
command
by
itself.
I,
don't
think
supported
all
operating
systems
very
well.
I
think
it
worked
really
well
on
Linux,
but
then
other
other
other
operating
systems
that
didn't
what
so.
D
C
D
C
So
like,
if
you,
if
you
look
at
the
ingress
definition
for
antidote,
whether
the
problem
was
or
syringe
rather,
the
problem
was
that
you
know
the
in
the
default
when
you
sweat
the
this,
the
Ingenix
ingress
controller,
the
default,
the
default
back
end
is
antidote
web.
So
that
will
work
no
matter
what?
Because
that's,
even
if
there's
a
problem,
that's
where
it
gets
routed.
So
that's
why
you
can
always
get
to
the
web
front-end.
C
But
unless
you
use
that
antidote
local
host
name,
then
you
would
not
be
able
to
see
any
lessons,
because
you
couldn't
reach
syringe
because
syringe
uses
a
different
path
and
a
different
ingress
definition.
So
this
so
the
what
I
discovered
after
some
experimentation
was
that
you
can
actually
just
remove
the
host
there.
The
host
you
know,
whatever
definition
declaration
in
the
ingress,
for
you
know
the
routing
so
that
you
only
have
the
path
which
is
slash,
syringe,
which.
C
D
C
D
D
D
D
A
C
Will
be
no
need
for
it,
because
all
we
all
we
will
need
to
do
at
that
point.
If
there's
a
proper
database
back
ending
all
of
this,
you
can
just
load
whatever
content
you
want
into
the
database
and
it'll
show
that
so
there
won't
be
a
need
for
a
mock
it'll.
Just
the
API
will
show
whatever's
in
the
database.
Okay,.
D
In
any
case,
that
was
also
some
change.
That
could
be
useful
if
you
look
at
the
chart,
it's
issue
54
on
South
Medicaid,
where
I
advocated
the
splits
of
the
visioning
scripts
into
one
part
about
kubernetes
and
one
part
about
antidote
which
would
help
making
sure
we
can
still
use
mini,
cube
or
kind
or
another
alternative
of
visioning
a
hypervisor
so
that
we
are
not
bound
to
the
backbones
so
you've.
D
D
A
D
B
D
The
thing
is
not
only
to
test
I
mean
my
my
difficulty
here
is
that
it
was
going
a
bit
backwards
compared
to
the
move
to
vagrants,
so
I
want
I,
didn't
want
to
be
rude
to
stiffen,
for
instance,
that
had
worked
on
vagrant,
which
was
about
merging
everything
in
a
single
script.
So
speaking
again
was
some
kind
of
way
going
backwards.
So
it's
not
just
about
the
technical
feasibility.
It's
just
like
what
is
the
consensus
or
what
is
there
any
guidance
going.
A
A
D
A
D
A
A
D
A
I'm,
okay,
with
leaving
descriptive
Steven
made
as
the
default
standard
way
a
lot
of
open
source
projects,
have
a
tools
or
user
scripts
directory
where
people
contribute
other
ways
of
doing
things
with
the
prod
inside
the
project
or
helpful
tools
for
their
different
environments.
In
fact,
I
think
that
would
probably
Matt
what
do
you
think
about
that?
I
think
that's
a
good
idea.
We
can
make
like
a
tools
directory
and
and
inside
that
tools
directory.
C
C
Make
sure
that
that
has
all
of
the
things
thought
through
right
make
sure
we
put
all
of
the
different
options
for
running
kubernetes
on
the
board
kind:
mini
cube
micro
kate's,
whatever
the
options
are
like
just
put
them
all
up
there
and
pick
one
and
then
have
one
option
as
the
like
blessed
stable
version
that
we
that,
if
somebody
doesn't
have
an
opinion,
because
that's
gonna
be
everybody
that
first
arrives
right
when
they
first
show
up
they're
gonna,
be
like
you
know
what
I
don't
really
care.
I,
don't
know
enough
about
this
project.
C
A
What
I'm
saying
is
this?
That's
not.
We
don't
have
to
socialize
everything,
we
don't
the
bog
everything
down
in
bureaucracy,
let's
go
with
what
we
have,
because
it's
almost
working
Liberty
we
haven't.
We
have
an
answer
for
the
Liberty
problem,
so
go
and
it's
a
one
as
fragran
up
and
it's
running
great
and
that's
what
we
want.
The
initial
experience
to
be.
Someone
doesn't
want
to
do
something
else
and
then,
with
these
other
things
that
we
put
into
this
user
scripts
directory,
we
can
play
with
those
over
time.
A
We
can
experiment
with
them
and
if
we
want
to
change,
we
can
do
that.
But
right
now,
I
don't
want
to
change
again.
Let's
just
go
because
we
because
we
need
to
get
packet,
pushers
and
Red
Hat
on
board.
So
let's
just
focus
on
getting
what
we
have
to
work
and
document
it,
and
then
we
can
put
these
other
things
into
a
into
user
user
tools
or
userscript
directory
yeah.
B
C
D
C
A
B
B
C
C
A
I,
what
I
think
will
happen
is
this
I
think
VirtualBox
will
be
the
default
because,
as
of
because
this
was
16
September,
that
they
announced
data
for
6.1,
so
that's
that's.
Gonna
come
out
soon,
like
probably
before
the
end
of
the
year,
if
not
first
quarter
next
year,
the
beta
runs
are
1/4
on
average
for
VirtualBox,
so
like
three
three
or
four
months,
so
I
I
think
that
VirtualBox
6.1
is
going
to
come
out.
D
D
B
C
D
C
A
B
B
It
doesn't
look
as
generic
like
you
may
have
to
change
directory
paths
between
Windows
and
Linux,
but
if
we
can
get
kind
to
work
that
maybe
a
second
option,
we
support
virtual
box
or
we
support
kind
or,
and
we
support
kind.
I'm.
Okay,
with
my
time,
has
been
limited
the
past
few
weeks,
I'm
in
transition
on
jobs,
but
I
should
have
more
time
after
hours
to
experiment
with
these
things
to
dedicate
to
self-medicate
yep.
Ok,.
A
So
we're
talking
about
all
the
options
and
we're
running
out
of
time.
So
what?
Let's
we'll
do
that
know
what?
Maybe
we
should
do
an
MP
on
this
or
or
a
proposal
document,
but
let's
stabilize
them
what
we
have
right.
We
can
assume
that
VirtualBox
would
be
the
default
and
then
anything
outside
of
the
default,
which
is
what
we
should
focus
on
and
stabilize
anything
outside
of
that
including
kind.
It
needs
to
be
a
user
tools
or
user
script
directory
and
say:
hey.
Look
these
other
tools
out
here.
A
If
you
want
to
experiment
with
other
things,
it's
not
officially
supported,
you
can
get
a
hold
of
the
person
that
made
them
and
and
then,
if
they
get
to
them
the
point
where
they're
there
they
work
reasonably.
Well,
then
maybe
we
can
back
the
mountain
to
the
parent
directory,
but
let's
focus
on
getting
vagrant
and
VirtualBox
working
as
a
default
first,
because
it
needs
to
be
stable
guys.
A
We
haven't
had
new
content
since
I
did
the
bash
script,
and
that
was
three
months
ago
and
and
in
my
experience,
I
told
people
just
just
github,
just
do
the
git
clone
and
type
in
vagrant
up
better
or
just
type
in
what
it
was,
the
bass
grip
and
it
doesn't
work
like
it
just
didn't
work.
There
was.
There
was
issues,
so
we
we
have
to.
We
have
to
make
that
go
away
and,
and
the
way
to
do
that
is
to
standardize
so
VirtualBox
and
embankment.
A
If
anyone,
the
other
thing
is
every
Friday
I
mean
I'm.
Only
Matt
and
I
are
only
two
people
and
we
were
like
we
have
so
much.
We
have
families
and
and
another
job.
Besides
this,
and
even
though
we
get
to
work
on
this,
like
70
percent
of
time,
we
have
30
percent
of
other
stuff.
We
have
to
do
including
travel
and
personal
lives,
and
we
are
extremely
constrained-
and
we
really
and
so
I've
committed
to
doing
this
to
get
the
curriculum
back
going.
A
It
would
be
great
if
I
could
get
someone
else
to
commit
to
that.
It's
just
to
do
in
one
stage
a
week
or
one
stage
every
other
week,
I
just
a
stage
on
anything.
It
could
be
anything
yeah,
Mille,
JSON
Python.
It
doesn't
even
have
to
be
about
networking
or
or
or
kampf,
or
anything
like
that.
It
can
just
be
simple
topics
or
or
if
you
know
a
lot
about
something
like
FRR
or
batfish,
or
something
like
that.
A
That's
fine
do
a
lesson
on
that,
but
we
just
one
stage
a
week:
I
can
do
one
stage
week.
Every
Friday
I've
cleared
I
made
sure
that
was
possible
and
it
would
and
we're
really
looking
for
someone
else
to
do
that
and
Matt's
not
gonna,
be
the
person
because
Matt's
list
is
much
longer
than
mine
and
and
he
has
a
newborn
still
it's
one
year
old
Kitt's.
Oh
he's
still,
you
know
it
gets
poopy
everyday
when
he
wakes
up
so
and
then.
C
A
There
can
be
if
we
have
someone
to
commit
to
a
stage
that'd
be
great,
and
the
thing
about
doing
this
simple
stages
is
that
you
don't
have
to
make
an
image.
You
can
reuse
one
of
the
existing
images,
a
Linux
image,
let's
say,
and
and
so
you
don't
have
to
worry
about
that-
and
you
can
just
work
on
the
content
and
the
lessons
only
got
to
be.
The
lesson
should
be
consumable
in
ten
minutes
or
less
that's
the
goal.
It
used
to
be
five
minutes
or
less,
but
I.
A
Don't
it's
ten
minutes
or
less
is
fine,
and
if
you
look
again
again,
it
can
be
about
the
simplest
of
topics.
You
know
it
could
be
at
a
stage
the
bash
lesson
at
a
stage
to
the
yamo
lesson.
Right
now
we
have
yeah
mole,
dictionaries
and
I.
Think
yema
lists,
or
maybe
you
have
a
list
of
not
dictionaries,
I
don't
know,
but
you
could
usually
add
another
demo
lesson
or
two
anyways
I'm
hearing
you're
selling
it.
A
If
one
of
you
want
to
volunteer
to
do
stage
once
a
week
or
once
every
other
week,
please
respond
in
the
community
forums
and
we
can
we
can
coordinate.
We
can
have
a
separate
curriculum
meeting
like
every
other
week
or
something
to
figure
out
where
people
are
at
and
and
look
at
each
other's
work
and
and
and
stuff
like
that.
If
you
want
whatever
you
want
to
do,
but
we
we
have
to
get
more
curriculum.
We
have
to
get
more
stuff
into
the
curriculum.
A
B
D
C
B
D
A
C
Yes,
that
I
was
that
was
the
one
I
was
trying
to
remember
so
one
of
the
things
I
highlighted
and
I
actually
talked
about
this
in
my
forum
post
a
little
bit
the
antidote
Docs
and
the
NRI
labs
curriculum
Docs
are
together
right
now,
and
we've
already
talked
at
length
about
one
of
the
barriers
for
people
creating
new
content,
which
is
self
medicate,
so
I'm
not
gonna,
break
I'm,
not
gonna.
Talk
about
that
anymore.
C
I
think,
probably
a
good
second
choice
for
a
barrier
like
the
the
barrier
after
that
biggest
barrier
is
probably
that
the
docs
aren't
easy
to
follow,
which
is
tough
for
me
to
say.
Cuz
I've
spent
a
lot
of
time
on
them,
but
but
I
can't
deny
that
they're,
they're,
they're,
they're,
exhaustive,
but
they're
just
hard
to
follow
and
I've
actually
heard
that
from
people
not
just
me.
I've
heard
that
from
Red
Hat,
actually
the
Red
Hat
guys
were
saying,
like
you
know,
I,
don't
even
know
where
to
get
started
in
these
dogs.
C
So
you
can't
like
read
it
top
to
bottom,
because
you
can't
that's
true,
you
can't.
It
actually
starts
with
like
antidote
platform
Docs,
which
chronologically
that
doesn't
make
a
whole
lot
of
sense.
What
I
would
like
to
suggest
is
that
we
split
off
the
the
docs
that
focus
on
the
energy
lapse,
curriculum
and
the
process
for
contributing
there,
as
well
as
getting
started
with
self-medicate,
because
self-medicate
is
basically
a
curriculum
resource
just
because
it
uses
it.
Does
it's
not
meant
to
be
used
for
anything
antidote,
testing
wise,
it's
always
using
stable
releases
of
that.
C
So
my
suggestion
would
be
that
we
that
we
split
off
anything
to
do
with
NRI
labs
specific
into
its
own
curriculum
and
that
it
be
rewritten
to
you
know,
be
effectively
chronological
start
at
the
top
and
then
go
from
step
to
step
to
step
in
order
to
get
through
the
curriculum
development
experience.
I'll
also
say
before
it
sounds
like
I'm.
Just
inventing
things
to
work
on
I
would
I
would
be
happy
to
take
this
on,
because
I
wrote
most
of
the
docs
anyway.
C
It
doesn't
really
make
a
whole
lot
of
sense
to
shove
that
onto
somebody
else.
My
main,
my
main
question
is:
does
that
make
sense
to
everybody?
Does
that
sound
like
a
good
idea?
I
would
also
say
that
I
would
probably
take
the
opportunity
to
move
to
something
like
get
book
instead
of
read
the
docs
cuz
get
books,
look
just
looks
a
lot
better
and
I.
Think
a
lot
of
projects
are
starting
to
use
that
so
plus.
C
C
Yeah
this
is
a
nice
dude
like
if
you
look
at
like
the
the
thing
I've
been
doing
a
lot
of
prototyping
for
mp1
and
we're
gonna
be
using
nasa's
'm
as
a
pubsub
messaging
system
for
for
antidote
and
nats
documentation
uses
it
there's
actually
a
lot
of
products
that
start
to
use.
It
I
think
it
looks
a
lot
better,
a
lot
easier
to
follow
them.
A
C
A
C
Now
right
it
doesn't
read
like
it
doesn't
read
like
a
story,
because
it
really
can't
it
I
mean
the
antidote
Doc's
are
will
also
be
part
of
this
cuz.
The
antidote
Doc's
is
probably
the
best
place
for
learning
like
what
kind
of
things
you
can
put
in
a
lesson.
Those
that's
just
like
antidote
features,
so
that
makes
sense
to
keep
there.
So
there
will
be
references
between
them,
of
course,
but
I
think
when
it
comes
time
to
like
pointing
when
it
when
it.
E
C
C
C
C
Are
also
kind
of
related
to
each
other
part
of
mp1
which,
by
the
way,
I
am
officially
committing
to
finishing
the
draft
by
the
end
of
this
week,
and
the
reason
for
that
is
because
I
have
to
and
the
reason
for
that
is
because
I'm
talking
about
it
at
a
meetup
here
in
Portland
on
Thursday
and
so
expect
that
expect
in
the
next
stand-up.
That
I'll,
basically
be
saying
hey
comments:
welcome
ready
for
review
all
that
kind
of
stuff.
C
Hopefully,
I'll
already
have
good
feedback
from
a
bunch
of
go
developers
here
in
town
and
and
also
I'll,
be
sending
it
to
a
bunch
of
other
folks
that
I
know
on
the
internet,
so
that'll
be
cool.
Circling
back
to
how
this
impacts,
the
the
initial
developer,
experience
part
of
what
I
want
to
tackle
an
MP
one
which
is
in
the
design
doc,
is
we're
gonna,
be
creating
brand
new
models
for
everything,
because
we're
gonna
be
using
an
external
database,
and
so
you
need
to
create.
You
know.
C
Sort
of
schema
well
they're
ghosts,
trucks,
but
it's
kind
of
the
same
idea
right.
You
have
to
create
models
for
populating
that
data
and
when
you
have
that
it
becomes
a
lot
easier,
especially
if
you
structure
right,
which
is
again
part
of
the
goal
of
what
I'm
gonna
do
it'll,
be
actually
a
lot
easier
to
to
create
not
just
import
lesson
content
but
create
lesson
content
right
now,
they're,
only
literally
the
only
way
that
people
can
do,
that
is
by
copying
an
existing
lesson,
which
is
horrible
and
I
feel
guilty
about
it.
C
Every
single
day,
I
part
of
mp1,
is,
is
going
to
include
way
way
way
way
way
better
command-line,
tooling.
That
says:
look
we
know
what
kind
of
thing
going
to
lessen,
because
we
have
the
database
models
built
into
syringe,
and
all
we
got
to
do
is
is
add:
sub
commands,
sir
sy,
our
CTL.
This
is
like
s
what
our
CTL
lesson
create,
and
it
goes
through
those
models.
It
walks
you
through
all
those
fields
and
what
they
do,
and
it
says
how
many
nodes
do
you
want
to
miss
lesson?
Three
cool?
C
How
do
you
want
them
to
be
connected
this
one,
this
one,
this
one
cool?
What
do
you
want?
The
name
of
the
lesson
to
be:
what
do
you
know
matically
generate
the
lesson
ID
it'll
it'll,
you
know,
do
all
that
stuff
for
you
and
I.
Think
honestly,
that'll
probably
get
folks
90%
of
the
way
there
and
they
really
would
only
need
to
run
self
medicate
to
just
double-check
that
it's
working
and
what
does
it
go?
Struct.
C
C
C
Would
we
we
wouldn't
be
so
reliant
on
the
on
the
self-medicate
experience
if
our
if
the
antidote
tooling
was
better
and
if
the
antidote
tooling
was
better
than
we
could
also
build
a
better
you
know,
maybe
we
could
actually
build
an
energy
labs
lesson
that
talks
about
building
a
building,
a
lesson
you
know
cuz,
it's
not
like
I
said:
there's
nothing
really
to
show
right
now,
the
the
way
you
create
a
new
lesson.
Is
you
copy
an
existing
lesson?
I'm,
you
know
we.
C
We
can't
read
a
lesson
that
runs
the
CP
command
so,
like
all
of
this,
all
of
these
things
are
related
and
I.
Think
what
I
the
thing
I
want
to
underscore
is
that,
like
I've,
you
Anna,
no
one
dunno,
especially
the
the
changes
to
syringe
as
effectively
being
able
to
unlock
a
lot
of
these
other
things,
and
that's
why
I'm
gonna
be
laser
focused
on
it
in
the
near
future.
C
I'll
also
say
you
know,
I
I,
now
that
the
design
is
solidifying,
it's
not
actually
gonna
take
nearly
as
long
as
I
thought.
It
would
because
again
we're
not
trying
to
boil
the
ocean
we're
not
trying
to
do
everything
in
fact,
part
of
what
the
changes
to
syringe
will
be
are
setting
us
up
for
better
extensibility
later
so
anyway.
Oh
also,
the
name
syringe
is
going
away,
sorry
to
drop
that
bomb.
C
A
C
So
so,
just
just
to
level
set
basically
what
we,
what
we've
been
doing
over
the
past
few
weeks,
a
few
months,
actually
is
thinking
about
the
the
backend
platform.
For
all
this,
we
call
it
antidote
and
that's
kind
of
what
I
want
to
refer
to
everything
as
going
forward
right
now.
The
design
is
is
still
very
much
in
the
proof-of-concept
stage.
We
built
it
to
be
very,
very
simple
at
the
beginning,
so
we
could
like
work
out
the
rest
of
the
project
which
I.
D
C
C
How
can
we
best
redesign
antidote
to
work
properly
in
that
environment,
and
so
that's
what
we're
doing
now
so
I,
if
you,
if
you
want
to
get
more
involved
on
the
on
that
portion
of
the
project
which
is
currently
called
syringe,
but
will
just
be
calling
it
antidote
going
forward,
I
I
would
love
that
I
would
absolutely
love
that
the
best
way
I
think
the
best
way.
I.
Think
for
you
to
do.
C
That
is
take
a
peek
at
the
design
when
I,
you
know,
basically,
I'll
send
a
notification
out
on
the
forums
and
I'll
probably
talk
about
it
tomorrow.
In
next
week's
stand
up
and
say:
yep
the
design
draft
is
finished
and
it's
ready
for
review
so
just
go
through
that
and
ask
questions
and
and
raise
concerns
and
do
whatever
you
need
to
do.
Cool
yeah,
because
this
is
this-
is
this-
is
kind
of
probably
going
to
be
the
last
time
such
a
dramatic
change
is
made
to
that
layer.
A
D
A
A
D
C
Because
the
women
but
yeah
well,
the
original
intent
was
to
have
it
consistently
at
the
same
time,
so
we
could
have
like
a
live
show
right
and
that
we
can
have
like
people
that
are
like
you
know,
asking
questions
live,
and
that
was
the
idea
we're
just
not
getting
the
live.
Engagement.
We're
getting
a
lot
of
engagement,
though,
on
the
recordings.
Like
that's
the
thing,
there's
a
mismatch
there
yeah.
A
People
are
watching
the
recordings,
so
people
want
to
watch
the
content.
The
problem
is
that
they're
not
watching
it
at
Monday
at
noon
and
the
more
I
think
that
more
I
say
that
out
loud
the
more
it's
kind
of
insane
that
we
picked
the
time
that
we
did
so
we
we
need,
like
Wednesday
and
they'll,
tell
you
the
best
time
the
tweets
are
like.
If
you
want
to
get
your
tweet
out
into
the
universe,
is
Wednesday
and
Thursday.
A
Yeah
I
get
that
but
I
for
those
of
you
who
can
see
Olivia's
video.
He
made
a
point
without
words
see
he
showed
somebody
dozing
off,
because
somebody
people
might
fall
asleep
at
one
o'clock,
but
also
that
that's
true,
but
you
know
we
also
want
to
do
it
at
a
time
when
people,
because
we
have
people
in
the
UK
and
in
France
who
want
to
watch.
You
want
to
watch
the
stream.
So
we
doing
it
first
thing
in
the
morning
doesn't
make
sense.
A
I,
don't
think,
because
anyways
we're
gonna
move
it
to
Wednesday
or
Thursday
afternoon.
Does
anyone
have
any
objections
or
any
thoughts
on
whether
it
should
be
Wednesday
or
Thursday
and
by
the
way
we're
not
opposed
to
pre
recording
it,
but
it'll
still
come
out
on
the
same
time?
In
the
same
day,
it'll
just
be
recording
you.
D
D
C
C
Agree
as
it
as
I
can
I
will
say
that,
like
this,
like
for
my
talk,
this
Thursday
I'm
gonna
I'm
gonna
rerecord
that
so,
if
it
makes
sense
for
me
to
rerecord,
then
I'll
do
that
I.
You
know,
there's
not
much.
We
can
do
about
like
what
you
kind
of
the
second
part
of
what
you
said
which
is
like.
If
the
conference
doesn't.
D
A
A
A
One
Eastern
I've
got
it
yeah,
one
Eastern,
so
Thursday
1:00
Eastern
is
when
we're
gonna
move.
It
I'll
make
the
announcement
on
Twitter
and
in
the
community
forums
and
then
we'll
we'll
go
from
there
Matt
and
I
by
the
way.
I'm
gonna
I'm
gonna
discuss
this
without
talking
to
Matt
first,
but
we
do
have
sight.
We
I
have
some
thoughts
and
more
shows
that
Matt
and
I
can
do.
We
that
Network
automation,
certification,
show
went
pretty
well
people
liked
it.
The
feedback
I
got
and
we
have
all
the
right.
I
have
other
ideas.
A
Anyways
first
for
shows
like
that,
where
we
kind
of
explore
a
topic
and
we
pull
resource
from
the
internet
and
we
talk
about
it
and
and
just
have
commentary
so
I
think
well,
you'll
see
a
couple,
some
more
of
that,
but
probably
probably
in
the
next
two
months
in
particular,
because
it's
hard
to
book
people
during
December
in
January
so
be
ready.
Matt,
including
a
show
called,
hopefully
a
regular
show,
will
do
maybe
once
a
month
called
things.
I
wish.
I
knew
about
automation
and
networking
and.
F
A
Is
the
only
meeting
that
that
you're
on,
unless
we
do
set
up
a
separate
meeting
to
talk
about
curriculum
stuff
which
which
I'm
we
so
desperately
need
to
start
developing
and
getting
a
like
a
community
going
around
content
development
that
we
might
end
up
with
a
second
meeting?
But
right
now?
This
is
the
only
meeting
the.