►
From YouTube: Community Standup: 7/16/19
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
A
A
A
A
A
A
A
B
B
B
B
B
B
A
A
C
C
So
I
I
took
I,
took
notes
when
Lisa
and
I
did
like
a
really
quick
handoff
like
I'm,
pretty
sure
you
were
invited,
but
I
don't
think
you
were
there
just
to
do
like
a
handoff
between
the
pts
and
I
took
notes
on
what
she
said
we
should
cover
today.
I
can't
for
the
life
of
me
find
it,
but
I
know
she
wanted
us
to
cover
both
legal
updating
people
in
process
of
governments
and
went
on
like
how
those
I
didn't.
C
C
C
C
I
mean
how
early
in
the
morning
it
is
yeah,
maybe
but
I
think
I
think
also
talking
about
it
well
before
the
actual
time
of
the
meeting
is
good
too,
like
sending
reminders
and
whatnot
yeah
yeah.
That
probably
helps
that's
I,
think
that's,
probably
the
biggest
thing
is
just
being
being
the
present
yeah.
B
A
B
Multiple
because
Lisa's
been
asking
for
that
every
single
week
and
I
still
haven't
done
it.
But
I,
don't
know
what
to
talk
about
next
week,
like
I'm
I'm
running
out
of
stuff.
To
imagine
that
we
can
just
talk
about
until
we
get
a
release
and
until
the
work
is
coming
along
until
we
have.
You
know,
community
members
that
community,
if
we
could
just
make
that
a
verb
that'd
be
great
because
it's
just
awesome
working
on,
but
what
we
can't
yeah.
A
C
B
B
B
D
D
D
D
D
C
E
E
C
E
C
C
But
then
juniper
ended
that
pilot
and
we're
pretty
sure
they're,
not
gonna,
go
with
zoom
cuz,
because
what
you
said
it
is
expensive,
especially
if
you
had
a
lot
of
users
and
we
have
a
lot
of
users.
So
we
just
ended
up
buying
our
own
for
this
project
and
we
got
one
user.
It's
a
shared
account
everyone's
using
it
like
the
early
days
of
Netflix.
B
Alright,
so
well,
we
have
so
I
I'm,
actually
curious,
I'm,
gonna,
dance,
Tom,
some
more
questions
before
we
start
time.
Are
you?
So?
What
is
your
interest
in
any
real
ABS
I'm?
B
F
D
D
B
So
we'll
go
ahead
and
kick
it
off.
This
is
more
or
less
an
open
agenda.
We're
mainly
because
we're
about
to
have
a
major
release
here
or
a
release
anyway,
with
new
content
and
new
features
in
the
in
the
platform,
and
we've
talked
about
these
pretty
extensively
in
Prior
community
stands
ups
as
well
as
our
livestream
that
we
do
every
Monday.
So
there's
there's
not
a
lot
to
update
on
that.
Just
that
you
know.
A
lot
of
stuff
we've
been
talking
about
is
about
to
go
live
probably
by
the
end
of
the
week.
Okay,.
D
B
Sure
the
the
biggest
thing
that's
coming
out
of
this
change-
we
talked
a
lot
about
this
yesterday-
is
we're
gonna
separate
the
the
curriculum
release
releases
from
the
platform
releases.
Obviously
there's
a
dependency
there
if
there's
features
that
are
being.
You
know
that
there's
new
features
in
the
platform
that
are
in
master
that
you're
creating
lessons
against
you'll
have
to
develop
those
lessons
against
that.
Against
that
a
you
know
against
master
versus,
if
you're
developing
lessons
for
the
existing
platform
to
be,
you
know
to
be
released.
B
You
know
the
existing
platform,
so
that'll
be
a
talk,
there'll
be
a
switch.
You
can
toggle
at
the
command
line
or
in
the
configuration
file
for
self-medicate,
but
that's
that's
really
important,
because
we'll
have
a
separate
cadence
and
the
separate
push
for
trying
to
get
as
much
content
as
we
can
onto
the
site
that
all
and
we
won't
potentially
every
single
week.
That
would
be
really
great
if
we
can
get
at
least
a
few
few
stages.
B
There's
we
are
I,
don't
know
if
we're
at
a
place
yet
where
we're
going
to
we're
kind
of
going
over
the
you
know
the
first
draft
of
a
number
of
different
sort
of
governance.
Docs
things
look
like
you
know
what
this
structure
the
community
is.
You
know
how
contributions
are
made.
The
code
of
conduct,
all
those
things
we're
gonna,
bring
that
to
the
community
pretty
soon
here
for
review
and
discussion
and
we'll
hopefully
be
able
to
finalize
those
things
out.
You
know,
hopefully
in
the
next
month
or
so
yeah.
C
I
I
worked
on
when
I
came
back
from
a
vacation.
Last
week
I
sat
in
a
few
of
those
meetings.
Lisa
is
currently
pushing
a
there's,
a
there's,
actually
quite
a
few
sort
of
parallel
efforts
going
on
going
on
and
in
order
to
just
basically
create
governance.
Draft
Docs
I
can
tell
you
that
that
work
is
is
nearing
the
end.
C
The
main
function
there
at
least
from
like
a
you
know,
the
Juniper
people
on
the
call
perspective
is
the
existing
Terms
of
Service
were
effectively
copied
from
our
engine
at
community,
which
is
not
at
all
what
we
want
to
do
here,
because
this
is
not
unlike
engine
ed.
This
is
not
a
Juniper
owned
prod.
It's
a
Juniper
like
started,
I,
guess
project,
but
sponsored
yeah
that
so
the
terms
the
terms
definitely
need
to
change,
to
reflect
that
and
and
to
keep
it
as
open
and
an
inclusive
as
possible.
That's
that's
the
effort.
C
That's
going
on
there.
That's
actually
that's
actually
nearing
the
end.
I
was
very
encouraged
by
the
last
meeting.
I'm
are
fortunately
a
which
is.
This
is
not
my
normal
experience,
but
our
corporate
lawyers
are
actually
very
understanding
of
what
we're
trying
to
do
and
they're
they
have
thrown
up
absolutely
no
barriers.
We've
got
some
good
folks
that
are
helping
us
get
that
out
there,
but
the
goal
is
not
to
get
the
governance
talks
like
finished
and
then
dump
it
on
everybody.
C
The
goal
is
just
to
get
a
set
of
draft
Docs
ready
so
that
we
have
something
to
share
and
something
to
iterate
on
I
know
both
the
packet
pushers
folks,
as
well
as
some
of
the
other
vendors
that
are
interested
like
cumulus
they've,
expressed
interest
in
in
having
us
produce
a
starter
dock
or
starter
set
of
docks.
I
guess
that
we
can
then
iterate
on,
and
so
that's
really
what
we're
doing
so
since.
C
Like
finalizing,
that's
obviously
not
what
we
want
to
do.
We
want
the
community
to
really
finish
creating
these
governance
talks.
That
effort
is
actually
nearing
nearing
completion.
We
expect
that
to
be
done,
probably
within
the
next
few
weeks,
and
then
you
know
it,
we
will
put
those
docks
somewhere
and
we
can
continue
to
build
them.
C
The
things
that
we're
not
doing
right
now
is
deciding
like
you
know
what
sponsors
get
you
know
who
who's
able
to
who's
able
to?
You
know
have
what
level
of
access
to
various
committees
and
things
like
that.
It's
that's
kind
of
stuff.
We
want
to
work
on
together,
so
we're
mostly
just
getting
the
boring
boilerplate
legalese
out
of
the
way.
First
and.
C
We'll
get
that
stuff
published,
I
and
and
I
and
as
I
say
that
I
have
exhausted
my
knowledge
of
the
process,
because
I
have
no
experience
with
the
legal
around
open
source
other
than
hey.
Please
lawyer
that
works
for
my
company.
Can
I
please
open
source,
my
software,
so
don't
ask
me
any
questions
because
I
won't
answer
them.
C
The
other
thing,
in
addition
to
the
governance
work
slightly
slightly
back
more
in
a
technical
direction.
One
thing
I
also
that
I
personally
am
working
on
as
hard
as
I
can
really
when
I,
when
I
am
able
to
do
this.
It's
like
my
top
priority
right
now,
I
sort
of
mentioned
in
a
previous
stand-up
or
a
previous
stream
that
there
are
that
there
are
really
like
six
around
six
sort
of
I
call
them
right.
Now
many
projects
they're
they're,
smaller
in
scope
than
the
the
entire
antidote
project,
but
they're
pretty
big.
C
C
Still
at
that
point,
still,
okay,
with
doing
the
bulk
of
the
work
that
needs
done.
You
know
it's
a
complicated
piece
of
software
that
I
hate
it's
very
custom,
so
you
know
if
it
comes
down
to
it,
I'm
happy
to
do
that,
but
I
want
to
give
the
community
the
opportunity
to
get
involved,
because
you
know
I
I
keep
I,
keep
telling
people
that
I
need
help
on
the
platform
and
so
I'm
gonna
I'm
gonna
put
in
the
work
the
mix
that
makes
that
not
only
possible
but
obviously
welcoming.
C
So
what
you
can
expect
from
me,
at
least
in
the
next
two
weeks,
is
at
an
at
minimum
one
of
these
Doc's
to
be
published
again
in
draft
form
or
we're
not
publishing
any
finished
Docs
here,
we're
just
starting
them
and
then
publishing
them
so
that
the
community
can
see
them.
So
the
first
one
will
be
the
syringe
rewrite
and
to
be
clear
if
you're
not
familiar
with
the
effort,
it's
not
actually
like
a
total
rewrite.
It's
mostly
it's
mostly
a
separation.
C
Right
now,
syringe
is
a
single
big-ass
binary
and
what
we
want
to
do
is
we
want
to
separate
it
out
into
little
teeny
micro
services,
which
is
which
there
is
a
bunch
of
advantages
in
doing
that.
Not
only
yeah
there's
a
bunch
of
advantages
in
that
I'll
wait
until
the
the
draft
plan
doc
is,
is
released.
C
I
have
created
by
the
way
I've
created
channels
in
discord
in
our
discourse,
server
for
each
mini
project,
at
least
the
first
two
mp1
for
the
syringe,
rewrite
and
mp2
for
the
antidote
web
revamp,
and
then
there
will
be
others
as
I
as
I
create
them,
but
these
are
the
top
two.
These
are
the
two
sort
of
most
important
ones
and
the
most
pressing
ones,
because
they
they
deal
with
the
two
core
components
of
the
platform.
C
So
I
I
would
expect
that
it
depends
on
how
the
remainder
of
the
ODA
for
auto
release
work
goes,
but
assuming
that
goes
relatively
well,
I
would
expect
that
I
could
have
the
draft
plan
document
for
many
project.
One
finished
by
probably
not
by
the
next
standup
but
I
I
should
have
something
to
share
by
the
next
stand-up
and
in
terms
of
like
showing
the
doc
in
progress
with
the
with
the
actual
ultimate
goal
of
having
it
published
for
the
community
to
iterate
on.
C
You
know
that
week,
sometime
next
week-
sometime-
maybe
maybe
by
the
end
of
next
week,
but
hopefully
earlier
than
that
so
I
know
that
was
a
big
rant,
but
the
TLDR
is,
if
you
have
any
interest
whatsoever
in
contributing
to
the
platform.
This
is
going
to
represent
probably
the
biggest
opportunity
for
you
to
do
that
in
the
entire
projects
life
cycle,
because
there
won't
be
there
won't,
while
I'd
obviously
expect
the
platform
to
continue
to
be
worked
on
in
in
for
a
long
time,
not
not
only
by
me
but
by
everybody.
C
These
particular
effort,
these
efforts
in
particular
these
don't
happen
a
lot.
You
know
you,
don't
you
don't
key?
Rebuilding
your
software
over
a
decade,
you
kind
of
do
that
as
few
times
as
possible.
Then
you
iterate
in
smaller
capacities.
So
if
you
want
to
get
into
that
into
the
weeds
of
it,
this
would
be
the
great
time
to
do.
C
So
yeah,
that's
I,
think
that's
all
I
wanted
to
talk
about
the
two
updates
yeah,
the
two
updates
for
the
design
Docs.
Those
are
imminent.
Those
are
sort
of
next
on
my
priority
list
and
then
just
an
update
on
the
governance.
Anybody
have
any
questions
on
either
one
of
those,
especially
the
governance,
because
I
was
kidding
earlier.
I
probably
could
answer
at
least
some
basic
questions,
unlike
when
we
have
what
done
and
and
of
course,
if
you
have
comments
and
concerns
like
hey,
it'd,
be
great.
C
There's
there
we
don't
use
that
term,
but
there
is
a
there's.
A
I'm
and
I
should
say
I'm
new
to
all
of
this,
like
I
I've
I've
been
the
recipient
of
a
lot
of
this,
but
I've
never
organized
this
Lisa,
as
you
can
imagine,
has
a
non-trivial
amount
of
experience.
Setting
up
these
communities
I
have
participated
in
many
of
them.
So
a
lot
of
these
terms
are
familiar
to
me,
but
you
know
I've
never
been
part
of,
like
you
know,
putting
the
actual
structure
together.
Lisa
has
in
this
dock.
C
C
You
know
committers,
who
are
effectively
sort
of
like
leaders
on
a
particular
sub
project,
so,
like
syringe,
will
have
a
set
of
committers
people
who
review
code
and
and
merge
it,
and
things
like
that
at
the
moment,
I
fill
both
roles,
but
I
absolutely
would
love
to
have
a
team
of
committers
on
on
every
project,
not
just
syringe,
but
every
project
who
are
who
are
sort
of
the
first
line
of
defense.
Of
of
you
know,
shepherding
contributions
and
whatnot
sort
of
how
cloud
tote
is
for
the
curriculum
right
now.
C
So
there's
yes,
oh
there's
technical
community
leaders.
It
looks
like
there's
in
everything's
election
based,
so
you
know,
for
instance,
I
would
probably
serve
as
the
technical
community
leader
for
a
year,
but
then
I
believe
what
she
says
in
this
doc
is
the
TCL,
which
is
a
great
acronym.
Tcl,
will
be
elected
by
simple
majority
or
greatest
plurality
for
a
term
of
one
year
by
private
electronic
vote
of
community
members
with
documented
country
on
the
law,
and
then
that
gets
in
the
like
who
can
vote,
which
is
still
something.
C
That's
it's
it's
new
to
me
having
to
decide
who
can
like
vote
on
stuff
I'm,
not
even
used
to
like
that's
the
thing
like
I'm,
not
even
used
to
people
voting
on
things
for
projects
I'm
in
fault
with
it.
It's
it's
all
a
lot
of
structure,
but
it's
good,
it's
necessary
stuff.
I
would
not
have
known
to
do
then.
So,
in
addition
to
the
technical
community,
of
course,
you
have
also
the
the
steering
committee,
which
is
much
more
on
the
sponsorship
side
of
things.
C
So
you
have
like
the
steering
committee
whoo-hoo-hoo,
instead
of
being
like
more
in
charge
of
like
technical
decisions.
They're
more
like
you
know,
what
kind
of
things
do
we
use
our
money
for?
How
do
we
you
know?
Do
we
do
we?
You
know,
elect
different
members
to
the
committee.
How
do
we
develop
like
operational
plans
and
talk
about
things
like
that?
So
all
kinds
of
stuff,
basically
the
non
technical
side
of
things?
It
sounds
like
the
the
steering
committees
in
charge
up
so
yeah.
E
C
A
C
E
E
E
C
A
few
things
I
can
bring
up,
while
you
think
about
that.
One
thing
that
we've
already
done
and
we
we
need
to
act.
We
need
to
label
more
issues
with
this
function,
but
one
of
the
things
when
I
in
the
last
stand-up
meeting
that
I
attended,
which
was
a
few
weeks
ago,
cousin
PTO
I,
wrote
a
whole
bunch
of
new
documentation
and
one
of
those
docs
covered
a
labeling
function
for
all
of
our
github
repositories.
So
this
was
something
we
actually
used.
C
C
Usually,
when
you
join
a
team
like
that,
they're
like
we'll
just
look
at
the
code
and
and
it'll
become
obvious,
it
was
like
kind
of,
but
not
really
so
what
the
stack
storm
team
did
was
they
actually
created
labels
that
indicate
the
level
of
anticipated
and
I
mean
anticipated
from
that
perspective,
anticipated
complexity
involved
in
a
particular
issue.
So
if
it's
like
a
whole,
it's
like
we
need
to
rewrite
the
API
server.
Then
yeah,
that's
gonna,
be
complexity
high.
If
it's
hey,
there's
a
typo
in
in
this
particular
form,
or
something
like
that.
C
You
know:
that's
gonna,
be
a
complexity
low
because
it
just
doesn't
require
a
lot
of
a
lot
of
intimate
knowledge
of
the
software
in
order
to
write.
But
the
cool
thing
about
that
is,
it's
still
a
contribution.
So
you
still
need
to
know
like
how
to
work
with
git
how
to
work
with
the
specifically
the
git
workflow
of
the
project.
C
It
tells
you
it
still
teaches
you
a
bunch
of
things
and
it
gets
you
contributing.
So
it's
it's
not
pointless
at
all.
It's
it's
very
useful
to
have
those
kind
of
issues
identified
specifically
and
and
then,
as
you
become
more
senior
and
more
experienced
on
the
team,
you
you,
you
tend
this
stay
away
from
those
issues,
because
those
are
a
great
way
of
getting
other
people
involved,
and
so
you,
you
know
you
spend
your
time
focusing
on
the
really
hard
stuff
and
that's
what
I'm
gonna
be
doing.
C
I'll
still
tag
those
with
a
complexity
label
that
way
people
understand
which
issues
are
sort
of
low-hanging
fruit
for
first
contributions
and
that's
across
the
board.
That's
not
just
syringe.
That's
syringe!
That's
antidote
web
I
believe
I
created
them
in
the
curriculum
as
well,
so
Derek
can
make
use
of
them.
If
he
feels
like
a
particular
lesson,
you
know
addition
is
fairly
easy
to
do
relative
to
another
like
more
complicated
lesson.
So
that's
gonna
be
a
across
the
board
experience
you
can
expect.
C
C
C
E
B
Yeah
well
we're
we
have
an
ongoing
conversation
with
a
with
a
number
of
different
vendors.
Cumulus
is
one
of
them.
You
do
have
an
image
that
works,
that
that
we
can,
but
we
you
know
we
have
to
have.
We
have
to
make
sure
everyone's
on
board
with
that
before
we
make
that
for
cumulus
in
particular
before
we
make
that
publicly
available.
B
Also
this
week,
one
of
the
things
I
definitely
need
to
finish
is
creating
an
image
for
free
range
routing,
just
by
itself
like
just
just
FRR
running
on
a
inside
of
the
linux
image,
because
there's
some
interest
around
that,
so
we
will
have
the
fr.
Our
image
can
happen.
You
know
immediately
the
using
any
you
know
using
cumulus
or
using
you
know,
any
any
other
vendor.
You
know
who
that's
paid
for
normally
by
the
customer.
B
But
after
some
discussion
we
decided
that
we
didn't
really
want
to
to
do
that
at
the
container
level,
because
it
requires
us
to
escalate
the
privileges
of
the
container
in
on
the
host,
which
would
give
anyone
accessing
that
container
access
to
resources
on
on
the
platform,
that's
hosting
the
site
and
that's
not
that's,
not
viable,
so
we're
just
gonna.
We
backed
away
from
that.
So
we
will
have
at
least
fr
and
then
the
near-term
and
then
hopefully
in
time
you'll
see
cumulus
appears,
is
an
alternate
vendor.
B
C
And
the
there
was
a
it
was
actually
sort
of
a
dependency
tree
of
work
that
needed
done
to
get
any
of
this
working.
The
end
points
change
actually
was
really
the
first
thing
they
needed
to
get
done,
and
that
took
a
few
weeks
because
the
way
that
the
way
that
the
previous
platform
worked
was
that
you
pretty
much.
If
you
wanted
to
use
it,
it
was
it
was,
it
was
kind
of
a
it
was
crap.
C
It
was
a
crappy
abstraction,
if
I'm
being
honest
like,
if
you
wanted
to
use
a
network
device
you
had
to
like
specified
like
uniquely
there
wasn't
it
was.
It
was
kind
of
messy
how
you
specified
that
you
were
using
a
network
device
versus
maybe
like
a
not
network
device,
and
then,
if
you
were
using
a
network
device,
you
can
only
the
only
network
devices
that
you
could
automatically
configure
with
the
platform
were
devices
supported
by
napalm
because
I,
that
was
the
only
option
that
was
used
in
the
backend
to
configure
devices
automatically
between
stages.
C
So
now
we
support
all
kinds
of
really
cool
different
ways
of
configuring.
End
points
first
off
the
end
point
abstraction
is
less
simpler.
End
points,
our
end
points
our
end
points
doesn't
matter
if
they're
running
network
devices
or
anything
else,
everything
and
then
all
endpoints
can
be
automatically
configured
using
a
number
of
options.
Ney
Palma
is
still
an
option.
C
A
C
Nfr
being
lead
examples
of
iOS
as
another
one,
so
our
goal
is
to
use
now
that
now
that
those
are
even
possible,
whereas
before
they
weren't
now
that
those
are
possible,
we're
hoping
to
do
we're
gonna
do
the
bulk
of
the
legwork
to
actually
put
them
into
the
platform
as
a
proof-of-concept,
and
then
once
the
once,
you
know,
cumulus
as
Derek
said,
approves
that
we
can
do
this,
we'll
publish
it
and
and
maybe
build
a
proof-of-concept
lesson
around
it.
The
intention
is
that
that
causes
a
little
bit
of
a
snowball
effect.
C
C
E
The
phone
with
Karl,
Moberg
and
Omar
Sultan
at
Cisco
talking
about
NSO
and
that
platform,
which
is
highly
multi-vendor
as
a
tool
that
maybe
fits
into
the
scheme
there.
That
might
be
an
interesting
way
to
crack
the
Cisco
nut.
If
that's
a
tough,
if
that's
a
tougher
one,
to
tougher
set
of
conversations
to
have
yeah.
C
E
Because
NSO
is
they're
talking
about
it
being
a
highly
multi
vendor
and
that's
a
really
big
deal
to
them
and
they
support
a
couple
of
hundred
different
I,
don't
know
if
it's
platforms
or
OSS
or
what,
but
since
it
also
fits
into
the
world
of
automation,
plausibly
there's
a
use
case
for
that
in
the
whole
energy
labs.
You
know
the
vibe,
the
purpose
of
the
product
and
again
once
you
want
something
that
Cisco
branded
gets
in
there.
Maybe
that
gets
easier
for
that
ecosystem
to
open
up
and
that's
another
one
of
those
snowball
effect.
E
B
B
F
C
Yeah
I
I
did
see
the
tweets
a
little
bit
ago.
Yeah
I
was
gonna
respond
after
this,
but
I'll
I
think
we
should
what
I'll
do
is
I'll
respond
and
let
him
know
the
best
place
to
ask
those
questions
at
the
moment.
Is
the
I
think
for
his
questions?
The
best
places
is
the
the
community
forums
that
way
everybody
can
kind
of
benefit
from
the
from
the
answers
as
well.
Yeah.
A
C
F
C
F
C
Well,
yeah,
the
the
abstraction
that's
in
place
now
I
think
should
be
a
lot
more
conducive
to
that,
because
there's
actually
I
believe
in
syringe
there's
actually
where
I
declare
the
different
presentation
options.
I
believe
I
did
declare
V
and
C,
but
I
might
have
commented
it
out.
So
there
should
be.
C
There
should
be
at
least
starter
code
there
to
make
it
possible,
and
if
not
it
it
shouldn't,
be
that
that
difficult
to
change,
I
think
the
biggest
the
biggest
concern
that
I
had
at
the
time
was
the
the
the
abstraction
that
was
in
place,
because
the
whole
presentations
concept
wasn't
a
thing.
It
was
kind
of
assumed
that
everything
would
be
SSH,
and
then
there
was
this
like
a
really
crappy
side-loaded
http
iframe
kind
of
experience.
If
you
wanted
to
do
that
and
I
didn't
really
talk
about
it
because
it
was
so
crappy,
but.
F
F
F
C
C
F
F
Mini
cubed,
but
another
variant
using
vagrant
or
using
some
other
virtual
machine.
We
three
new
with
nested
virtualization
stuff,
like
that,
so
I
did
shoot
birds
because
they
were
issues
with
the
whole
time.
I,
don't
remember
exactly
all
the
details,
but
that's
something
I
was
interested
in
in
the
need
to
secure
a
bit.
What
happens
inside
the
containers
like
you,
don't
want
people
to
demining.
C
F
D
F
C
Totally
so
I
actually
I'll
mention
this
is
actually
one
of
the
many
projects.
There's
I
think
it's
like
the
sixth,
so
there
basically
there's
a
lot
of
there's
a
lot
of
things
that
there
that
need
to
be
considered
there
a
lot
of
what
she
touched
on,
not
just
not
just
what
technology
we
want
to
use,
but
also,
how
do
we
improve
the
way
that
images
get
created?
C
C
All
very
consistent
because,
right
now
each
image
is
kind
of
done:
artists,
Hennelly,
like
by
hand,
steel
cut
and
that's
that's,
not
sustainable.
So,
and
that's
on
top
of
the
fact
that
you
know.
There's
there's
also
other
lessons
like,
as
you
mentioned,
and
as
I've
run
into,
for
instance,
there's
there's
somebody
who
wants
to
build
a
lesson
on
docker
you.
C
You
just
can't
do
that
without
some
really
that
shortcuts,
because
we're
running
everything
in
docker
in
you
know
in
coup
grenades,
but
through
docker,
so
yeah
and
and
then-
and
I
want
to
get
into
like
eb
PF,
for
instance-
and
you
just
you-
can't
do
that
kind
of
stuff
unless
you
have
kernel
access.
So
what
I
want
to
do
like
that,
like
the
all
up
goal,
I
think
for
us
in
this
in
this
particular
effort,
is
how
do
we?
How
do
we
build
a
user
experience?
C
C
C
B
C
That's
cool
but
I'm.
To
be
honest,
we're
gonna
be
doing
most
of
that
from
syringe
anyway,
which
syringe
that
syringe
can
orchestrate
that
I
mean
syringe
already.
Does
that
kind
of
thing
right
now
you
know
creating
CR,
DS
and
doing
that
kind
of
stuff
for
networking,
but
that
we,
the
build
process,
is
also
kind
of
interesting.
Dimitri.
A
colleague
of
mine
recently
shared
me
a
link
to
weaves
ignite
project,
which
is
based,
which
is
built.
C
It's
a
it's
a
it's
a
little
bit
of
software
on
top
of
the
AWS
fire
cracker
stuff,
which
they
open
sourced
as
sort
of
how
they
do
server
lists
in
little
mini
VMS,
which
looks
promising,
but
I
have
obviously
I
haven't
made
any
decisions
on
that.
My
goal
right
now,
but
the
only
thing
I'm
doing
right
now
is
I'm
just
taking
all
of
these
links
and
putting
them
into
a
Google
Doc
as
part
of
the
you
know,
design
doc
for
many
projects.
It's
because
this
is
gonna,
be
a
whole
mini
project.
C
I
totally
know
that
that's
gonna
happen.
So
if
you
have
links
that
you
want
to
send
me,
please
do
I'll.
Add
them
to
this
doc
and
then
at
the
other
end
of
it
when
I
finally
get
this
design
when
I
finally
get
this
project,
doc
finished
or
at
least
the
draft
finished,
all
of
those
links
will
be
there
and
we
can.
We
can
start
making
some
technical
decisions.
B
C
C
D
C
Yeah,
it
looks
like
on
over
chicks
is
posting
something
a
link
for
me,
I
guess
yeah,
so
I
look
at
the
chat,
I
just
posted
a
link
to
to
the
docs
where
we
have
a
contribute
page.
There
are
there's
a
list
of
there's
real,
there's,
actually
quite
a
few
areas
of
the
project
that
you
can
contribute
to,
and
it's
all
totally
based
on
preference.
C
For
instance,
if
you,
if
you
have
more
of
like
a
network
operator
background
and
you've,
sort
of
done,
automation
or
you're
learning
automation,
you
want
to
share
what
you've
learned
then
contributing
to
the
energy
labs
curriculum
might
be
the
way
to
go.
In
which
case
you
know
you
look
at
the
you
know
the
the
specific
page
that
says
contributing
to
the
NRI
labs
curriculum
and
then
you
sort
of
follow
that
down.
C
There's
there's
a
ton
of
useful
info
there
if
you,
if,
instead
you
want
to
work
on
the
actual
project
like
how
all
this
stuff
works
on
the
back
end,
there's
still
there's
still
a
number
of
things
that
you
can
work
on
like,
for
instance,
syringes
sort
of
the
back
end
component.
So
if
you,
if
you
want
to
work
on
sort
of
back-end
systems
and
sort
of
systems,
programming,
that
kind
of
thing
that
that's
that's
a
good
way
to
go,
if
you.
D
C
D
C
The
link
I
shared
was,
we
have
like
sort
of
an
all
up
contributing
page
in
the
documentation.
There's
a
there's,
a
bunch
of
children
pages
underneath
that.
But
since
you
said
you
are
you
know
mostly,
you
come
from
a
networking
background,
the
specific
page
that
you
probably
want
to
look
at
is
it
says
contributing
to
the
NRI
labs
curriculum.
That's
that's,
probably
the
one
you
want
to
start.
D
C
So,
let's
see
I
will
I
want
to
before
we
go
on
I,
just
wanna
make
sure
I
have
any
action
items
so
I
over
jaques,
the
you
know
the
many
project
stuff,
obviously
I,
think
that'll
help
you,
maybe
with
a
focus
on
the
last
mini
project
for
the
virtual
image
pipeline
and
whatnot.
I
still
think
that
the
antidote
at
the
end
of
the
web
and
the
syringe
many
projects
are
still
probably
like
the
the
leading
priorities.
But
then
maybe
maybe
that's
Matt.
Maybe
that
project
will
be
like
the
third
one
that
sound
good.
It's.
C
Okay,
cool,
so
I'll,
just
I'll
I'll
follow
up
with
you
a
publishing
that
doc
actually
probably
won't
be
a
ton
of
work.
So
maybe
what
I'll
do
is
I'll
just
put
it
together
and
publish
it,
and
that
way
you
can
add
things
to
it
on
your
own,
without
having
to
go
through
me.
E
My
questions
we're
all
just
you
know,
curiosities
about
the
covenants
and
so
on.
There's
no
action
items
from
me
right
now.
I
know
we're
waiting,
we're
waiting
for
new
lessons
on
the
DNS,
no
bash,
scripting
yep,
then
at
some
point,
we're
gonna
translate
that
into
the
packet
pushers
stack
and
start
working
on
evangelization,
but
we
were
kind
of.
C
C
The
curriculum
are
tightly
coupled
with
each
other,
so
you
can
release
Derek
Derek
will
be
able
to
release
content
a
lot
more
frequently
than
then
waiting
on
the
platform,
because
the
platform
has
its
own
cadence
and
it
wasn't
a
problem
until
now,
but
the
more
we
go
we're
like
man.
We
really
need
to
separate
these
things.
So
that's
the
main
reason
for
that
is
to
get
you
that
content
as
soon
as
possible.
C
E
B
Yeah,
absolutely
man,
you
know
you
were
you
had
put
it
out.
You
said
third
quarter
like
I
guess
it
is
third
quarters
and
it
or
almost
third
quarter,
yeah.
B
Quarter
calendar
year
anyway,
yeah
no
rush,
buddy
no
rush.
Just
well
just
send
me
an
invite.
You
have
my
email,
I'll
I'll,
make
sure
I'm
free,
you
know,
but
I
well,
send
me
an
invite
and
then
we'll
we'll
figure
out
we'll
figure
out
a
day
from
there.
I'll
make
sure
we
do
this.
You
know
as
soon
as
you're
able.