►
From YouTube: Community Standup: 9/17/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
B
Topic
in
its
place,
because
I
meant
to
say
this
yesterday,
but
forget
the
the
original
target
date
for
the
10.1
release
for
the
curriculum.
Is
this
Friday
and
there's
really
there's
only
a
few
things
we
need
to
do
there?
I
can
I
can
quickly
cover
what
I
see
in
the
project
plan.
Now
that
I'm
back
home
the
one
battle
one
release
mm-hmm
or
they
don't
want
yeah.
B
Yeah
yeah
I,
just
I,
want
to
get
in
the
habit
of
of
like
I,
maybe
I
know.
Maybe
we
need
like
a
calendar
or
something
like
that
because,
like
the
current,
currently
the
only
place
the
date
is
published
is
in
is
in
this
is
in
the
forum.
So
unless
you
see
that
date
and
then
mark
it
accordingly,
yourself,
like
it's
gonna
kind
of
go
unnoticed.
So
maybe
we
need
to
create
a
calendar
that
people
can
subscribe
to
I
believe.
C
A
That
reminds
me
we
should
have
a
I,
don't
know
if
it's
on
the
website
or
in
the
forums,
but
you
did
a
really
great
job,
Matt
of
creating
and
then
posting
internal
to
Juniper,
slack,
a
giant
list
of
blog
posts
and
other
like
different
sound
clouds
and
other
things
that
we've
done
for
any
labs
and
we
I
don't
know
if
that
should
be
on
the
website
or
on
the
forum.
But
we
should
definitely
have
a
place
for
people
go
and
look
at
those
things.
Yeah.
C
B
B
C
C
Bring
the
make
the
get
github
more
easily
accessible
to
make
all
of
our
various
other
sites,
all
much
more
accessible
from
the
main
homepage,
essentially
so,
rather
than
knowing
that
you
need
to
go
here
for
this
and
here
for
that
in
here.
For
the
other
thing,
you
can
go
to
one
place
and
find
everything.
So
that's
that's
what
we've
got
underway,
Irish
I
saw
you
came
off
mute
moment
early.
Do
you
want
to
introduce
yourself.
C
Well,
when
you
want
to,
let
us
know
all
right,
Derek,
yes,.
A
D
A
A
I
think
so,
if
it's,
although
I
shouldn't,
otherwise
you
know
it,
it
should
be,
maybe
like
a
proposal
or
a
project
if
it's
like.
So
though
I'm
working
on
something
very
large
right,
the.
A
B
A
We
should
have
another
mechanism
for
that,
or
we
should
I
think
we
should
I
think
we
should
move
that
to
projects
or
the
wiki
or
the
proposals
repo,
like
all
those
seem
better
than
just
having,
because
look
how
many
places
are
we
gonna
have
planning
related
things
now.
B
B
So
that
that,
basically
that's
like
the
detailed
and
that's
not
really
just
like
a
designer
is
just
a
buncha
links,
then
I
think
are
useful
to
whoever
wants
to
implement
this
particular
initiative.
It's
not
a
plan,
it's
a
it's
a
specific
task
that
needs
done,
that
you
can
open
a
PR
against,
which
is
which
is
really
what
an
issue
is
like.
That's
literally
the
purpose
of
an
issue,
so
the
plan
itself
will
be
elsewhere.
It
will
be
referred.
B
I
think
we
should
I
think
we
should
continue,
continue,
make
better
use
of
labels
and
then,
if
we
could
build
whatever
github
bot,
we
use
I'm
sure
has
this
capability.
We
would
then
select
a
set
of
labels
that
would
that
would
perform
that
at
aging
out
and
if
it's
like,
if
it's
not
a
if
an
if
it's
not
explicitly
assigned
one,
obviously
or
if
it's
assigned
one,
that
is
like
help
need
it
or
bug
or
anything
like
that,
then
yeah,
I'm,
fine
with
60
days.
A
B
A
A
That
speaking
of
that,
but
aside
from
that
I
am
trying
to
clear
out,
there
was
a
there
were
a
whole
bunch
of
issues
that
I
closed
with
obtuse
messages,
but
they
they
weren't.
Really,
there
were
issues
that
we're
no
longer
relevant,
or
you
know
literally
one
of
the
one
was
an
issue
for
an
idea.
Man
had
back
in
December,
that's
long
since
you
know
we've
we're
not
going
to
do
that
now,
better
things
have
happened
or
whatever
and
I'd
like
to
do
the
same.
A
I
did
that
for
the
self-medicate
project
and
I'd
like
to
do
that.
This,
the
the
same
thing
for
took
curriculum,
because
a
curriculum
has
54
open
issues
and
they
date
all
the
way
back
to
August
5th.
B
A
A
We
should
we
should
clear
these
out:
I,
don't
I,
don't
I,
don't,
but
I
could
do
that
at
this
exact
moment,
but
we
should
we
should
clear
these
out.
So
this
is
what
I
propose
and
I'll
put
the
same
thing
in
the
notes
and
I'll
actually
put
a
forum
post
explaining
that
what
we're
doing
here,
I'm
not
gonna,
do
that
right
now,
because
some
of
these
are
for
lessons
and
then
smooth.
Some
of
these
are
for.
B
C
B
A
Man
I
got
to
fix
that
yeah
sip
phone
lesson
is
broken,
but
and
then
some
of
these
are
like
you
know
you,
you
can't
there
was
Mac
issues
where
the
script
wasn't
working,
but
those
are
fixed
like
I.
Just
wanted.
I
just
want
to
close
these
out.
A
Be
rather
gonna
do
them
or
we're
not
rain,
and
we
have
so
I
should
probably
close
these
out
or
maybe
not
actually
put
less
than
ideal
at
most.
These
are
lessons
I
lesson
ideas.
We
should
problem
I.
Think
we
shouldn't
have
the
lesson.
Ideas
in
here
that
cuz
they're
spread
out.
There's
like
ideas
for
the
there's,
several
with
ideas
for
the
Python
less
and
then
they're
spread
out.
A
Well,
rather
than
have,
if
there's
multiple,
if
there's
multiple
ideas
for
the
Python
lesson
that
are
not
the
same:
okay
mm-hmm,
it
I
think
it
would
be
easier
to
I,
have
a
wiki
or
someplace
else
where
we
could
have
notes
about
those
lessons
and
ideas
about
what
we
want
to
do
with
those
lessons
collected
into
one
spot,
because
it's,
if
you
all
essay
that
you're
the
person
who
made
one
of
these
lessons
and
this
list
gets
up
to
be
300,
open
issues
and
you're,
and
you
just
want
to
find
all
the
things
all
any
feedback,
any
bugs
any
ideas
for
the
lessons.
A
D
If
we're
I,
like
the
issues,
I'm
not
opposed
as
a
community
member
I'm
not
opposed
to
having
them
as
github
issues,
the
first
place,
I
would
look
as
a
community
member
is
we're
driving
people
to
the
community
NRI
site.
That
would
be
another
good
place
for
them
and
maybe
even
have
under
that
community
site
a
place
for
curriculum
proposals.
I.
B
So
here
here's
where
I'm
thinking,
here's
what
I'm
thinking
this
I
mean
to
me.
The
curriculum
is
a
piece
of
software
right.
It
just
is
if,
in
that
respect,
it's
really
not
any
different
from
from
the
other
from
the
other
projects.
The
intention
and
the
way
that
that
software's
manifested
obviously
is
very
different,
but
it's
a
project.
It's
a
software
project
as
part
of
the
overall
and
re
labs
initiative
so
like
for
me
like.
B
If
I'm,
if
I'm
somebody
that's
coming
in
cold
with
and
I,
you
know,
I
don't
know
about
the
community,
say
I,
don't
know
anything
I
do
all
I
know
is
there's
this
open
source
project
out
there
and
here's
where
the
stuff
is
published.
My
instincts
are
gonna.
Tell
me
well
if
I
want
to
find
out
what's
wrong
with
stuff
and
what
you
know,
what
what
are
the
current
things
that
people
are
providing
feedback
on
as
well
as
feature
requests
which
that's
what
new
lesson
ideas
are
their
feature?
B
B
We
should
have
in
one
place,
I'm
just
saying
that
one
place
should
be
github
issues
because
it's
the
most
intuitive
but
like,
for
instance,
one
of
the
things
that
we
did
recently
with
the
you
know
publishing
the
publishing
the
release
activities
is,
you
know
we
have
now
a
mechanism
for
people
to
provide
ideas
for
what
should
be
in
a
release,
and
if
there
are,
if
there
are
things
that
somebody
identifies
as
part
of
that
process
like
toad,
for
instance,
the
last
the
in
the
in
the
release,
the
the
early
yeah,
the
release,
kickoff
I
did
two
weeks
ago
or
whatever
it
was.
B
You
commented
on
some
of
the
cumulus
stuff
that
needed
to
get
done
now.
There
were
issues
for
that
already,
but
imagine
if
somebody
comes
in
and
says
like
I
really
think
we
should.
We
should
think
about
doing
X
and
it's
like
a
totally
new
idea.
The
the
action
there
would
be
cool.
Can
you
or
I
will,
on
your
behalf,
create
a
github
issue
and
then
label
it
accordingly?
That
way,
everything's
again,
you
know
sort
of,
as
you
say
in
one
place,
because
that
is
useful,
but
I
just
I.
B
C
B
So
my
original
intent
for
that
was
basically
there's
something
wrong.
I
need
to
like
I
need
to
tell
you
about
it,
but
we
totally
could
argument
that
to
be
not
just
providing
feedback
on
what
I
see,
but
also
providing
feedback,
and
why
I
don't
see
like
right
there
in
the
site.
I
wish
you
covered
X,
and
then
you
know
we
would
I.
Don't
know,
put
that
publish
that
to
something
like
Q
that
we
could.
B
C
B
I'm
definitely
cool
with
that
I
in
terms
of
like
like
making
it
so
the
people
who
don't
even
know
anything
about
you
know
what
how
things
are
built
they're
just
going
to
the
site,
and
they
they
see.
Something
is
missing
so
I'm,
right,
yeah,
I,
think
that
makes
sense
I'll
what
we're
where's
that
issue.
It's
got
to
be
an
Internet
web.
Let
me
see
if
I
can
augment
it
with
that
cuz,
that's
kind
of
like
feedback,
it's
just
more
user
feedback
box
issue.
B
76,
oh,
and
we
we
already
added
to
this
because
this
we
were
also
trying
to
figure
out
a
hum.
We
already
have
this
so
here
check
this
out
and
I
believe
this
came
from
you.
Lisa
I
opened
the
issue,
but
I'm
pretty
sure
that
this
wording,
the
the
intention
behind
this
just
sounds
like
you
once
they've
completed
a
lesson
pop
up
a
quiz
or
send
an
email
to
follow
up
to
provide
feedback
for
energy
labs
and
ask
how
it
has
helped
them
in
the
meantime,
ask
for
other
lesson.
Ideas
also
check
this
box.
B
Alright
should
also
provide
a
feedback
button
on
the
lesson,
so
they
can
provide
this
anytime,
not
just
at
the
end.
So
yeah
I
mean
that
that
is
that
kind
of
I
mean
that
kind
of
encapsulates.
What
we're
talking
about
right,
not
just
feedback
like
a
lesson
that
they're
looking
at,
but
also
just
kind
of
open-ended.
What
do
you
think
about
stuff?
Let
us
know
well.
C
B
A
All
right,
okay,.
A
B
A
B
So
the
self-medicate
script
would
still
exist,
I'm,
not
suggesting
that
we
replace
that
with
something
else.
Well,
what
does
the
phrase?
What
are
you
removing
so
the
way
that
the
way
that
we
did
the
the
current
beggar
at
setup,
which
is
courtesy
of
mr.
Steven?
B
We
did
that
was
the
there
there
actually
to
self
medicate
scripts
in
the
repo
right
now,
there's
the
primary
one
that
hasn't
changed
and
then
there's
the
self
medicate
vagrant
SH,
which
is
what's
called
by
the
vagrant
file.
So
the
thing
I'm
suggesting
is
that
we
just
deprecated
the
old
one.
B
The
new
one
is
basically
identical
with
some
button
might
with
some
basic
modifications
to
effectively
run
without
a
vm
without
a
man
qvm,
because
once
you're
in
vagrant,
you
don't
need
a
vm
you're
in
a
vm,
so
you
just
run
bare
metal
and
then,
of
course,
if
you'd,
if
you
don't,
if
you're
running
linux,
natively
like
I,
am
it's,
you
don't
need
the
beggar.
Finally,
there
you
just
run
self-medicate
vagrant,
not
SH,
and
it
runs
bare
metal.
B
So
the
intention
was
to
have
the
vagrant
set
up
both
the
self-medicate
vagrant
on
Sh
script,
with
the
vagrant
file
and
have
those
basically
be
the
the
parallel
you
know.
Have
those
be
there
in
parallel
without
interfering
with
the
current
set
up
that
way,
people
can
just
continue
to
use
the
old
the
you
know
the
old
way
of
doing
things
which
spins
up
the
you
know,
whatever
core
OS
VM,
but
frankly
the
vagrant
stuff
has
worked
pretty
much
from
day
one.
B
So
I
I
think
it's
time
to
start
really
talking
about
just
killing
off
the
old
and
going
with
the
new,
as
as
the
as
the
main
solution.
So
for
most
people
it'll
be
you
know,
vagrant
up
and
then
they'll
interact
with
self-medicate
within
that
VM,
which
they
don't
even
need
to
do
that
first
off
because
it
starts,
it
starts
self-medicate
automatically
on
first
boot,
I.
D
B
B
Okay
yeah,
so
we
don't
squash
that
currently,
if
I
ran
all
I
did
was
I
just
ran,
self-medicate
vagrant
Donna
saves
space
start
and
it
just
generates.
All
of
the
you
know
the
self-medicate
stuff
or
the
the
mini
cube
mini
cube
output,
which
includes
a
warning
that
says
the
nun
driver,
provides
limited
isolation
and
may
reduce
system
security
and
reliability
for
more
information,
see,
and
then
it
points
to
a
github
issue.
B
D
D
C
D
D
D
B
D
B
Just
just
to
reiterate
the
the
work
that's
done
and
for
the
vagrant
file
and
all
of
the
surrounding
scripts
to
make
it
work
in
vagrant,
like
that
was
that
was
stellar
work.
If
you
haven't
looked
at
what
Stephen
did
like
just
check
it
out,
it
worked
with
the
exception
of,
with
the
exception
of
the
one
host
file,
editing
automatically
thing
that
was
actually
ended.
Up
being
my
fault,
cuz
I
didn't
install
the
plug-in
so
aside
from
the
fact
that
I
didn't
do
that,
like
it
worked
like
perfectly
the
first
time.
D
B
C
B
Has
to
actually
compile
to
to
sping
stocks,
but
other
than
that
yeah
I.
Don't
have
any
particulars
if
you
feel
like
it's
ready
to
go
just
you
know,
mark
it
ready
for
review
and
we'll
pick
Iike
it.
We
don't
have
any
specific
like
you
must
have
these
sections
and
they
must
be.
You
know
just
pretty
standard,
pretty
standard,
restructure
text
and
then
you
know
all
of
the
a
we
like
you
know,
having
linked
just
the
docs
practices
are
good
like
good.
You
know
internal
references
where
appropriate.
You
know
yet.
C
B
D
B
C
D
A
Okay,
are
there
any
other
items
open
for
discussion?
Anything
anyone
want
to
bring
up.
B
So
this
is
the
the
current
project
plan.
There
are
a
few
things
that
that
are
actually
done
like,
for
instance,
verify
packet,
pushers
collection,
I
went
back
and
I
saw
that
Derek
added
that
and
it
commits
a
while
back.
So
this
is
done.
We
just
wanted
to
make
sure
packet
pushers
had
the
lesson
that
the
bash
lesson
was
part
of
the
packet
pushers
collection.
B
So
that's
actually
in
PTR
I,
don't
know
it's
useful
guys
to
just
to
send
that
link
to
packet
pushers,
just
wait
until
until
the
until
the
real
link
is
live,
but
you
know
how
many
opinions
on
it
drew
didn't
make
it
into
this
meeting.
Did
he
no
okay,
all
right?
Well,
anyway,
it's
a
PTR.
If
we
think
it'll
move,
if
you
think
it'll
help
you
know,
obviously
we
can
send
them
that
collection
and
say
like
look
your
lessons
here
and
it'll
be
live
soon.
B
I,
don't
know
what
I
meant
here
test
other
misc
fixes
I
got
to
stop
doing
that
without
context.
I
I
believe
what
I
mean
here
is
just
that
all
of
the
fixes
that
have
gone
in
since
one
dunno
dunno,
which
there
have
been
a
few
so
like
really
minor
stuff
or
maybe
maybe
I-
was
referring.
These
fixes,
like
these
top
fixes,
which
are
stack,
storm
lesson
and
then
the
issues
with
the
troubleshooting
lesson.
Yeah.
A
I
I
need
to
probably
put
that
in
PTR
for
now
the
lesson
21
because
there's
multiple
breaks
now
like
it
doesn't
net
box,
doesn't
load.
There's
there's
issues.
Oh
you
mean
like
remove
it
yeah
until
cuz,
it's
it's,
it's
pretty
hosed
up
and
it's
just
broken,
so
we
might
as
well
remove
it
for
now.
B
No
because
that
would
just
like,
like
that,
would
just
remove
it.
People
might
have
links
to
it
that
get
broken
I.
Wouldn't
it
be
better
I
mean
how
do
you
know
how
hard
it's
gonna
be
to
fix
it?
Is
it
gonna
be
like
weeks
of
work?
I,
don't
know
I
I.
A
Don't
know
we
can
leave
it
for
now.
If
it
will
bring,
I'll
have
a
look
at
it
and
I'll
bring
I'll
mention
it
if
it.
If
it
looks
like
it's,
gonna,
be
a
pain.
Okay,.
B
Cuz
we
can
I
mean,
like
the
the
target
date
that
I
established
was
fairly
arbitrary.
It
doesn't
really
make
a
lot
of
sense.
I.
Think
to
just
like
try,
you
know
like
like
I
would
prefer
that
the
lesson
not
get
decommissioned
it's
at
all
possible
and
if
it
means
moving
the
arbitrary
date
that
I
selected
by
throwing
a
dart
on
a
dartboard,
that's
totally
fine
by
me,
but
yeah.
Just
let
me
know
I
if
it
yeah.
B
If
it
is
like
a
tremendous
amount
of
work,
or
maybe,
like
the
you
know,
the
piece
of
software
that
you
put
in
there
there
the
contributor
like
deleted
the
project
and
there's
no,
you
know
that
guidance
catastrophic
is
happening.
Then
yeah.
We
didn't
talk
about
that,
but
we've
got
we've
got
flexibility
from
a
time
perspective,
so
I
don't
want
to
feel
like
we
got
to
rush
anything
style
checks
enforcement,
see
I
Stephen.
Did
you
say
it
was?
You
said
you
wanted
to
take
this
one.
Somebody
say
yeah.
D
D
B
If
there's
a
way
we
can
limit
the
scope,
I'm
sure
there
is,
we
could
limit
the
scope
of
what's
checked
to
all
of
the
added
lines
so
like
if
you're.
If
that
way,
people
don't
have
to
like
fix
the
entire
curriculum.
You
know
the
first
person,
like
the
poor,
poor
soul,
who
happens
to
have
their
PR
like
right
after
we
submit
this
stuff.
He'll
have
will
have
a
task
of
fixing
everybody's
crap.
D
B
B
That's
I
learned
long
ago,
I
think
was
at
eBay
that
one
of
my
went
on
mentors
there
was
was
was
talking
to
me
about
how
basically
that
problem
and
how
you
just
need
everything
in
the
repo
don't
rely
on
like
don't
rely
on,
like
you
know,
getting
getting
detailed
configurations
into
the
pipe,
keep
the
pipeline
really
stupid
and
just
do
everything
within
scripts
and
then
just
execute
those
scripts
so
like.
If
you
want
to
run
tests,
you
better
have
a
makefile
or
something
like
that.
B
That
just
does
make
test,
and
it
does
all
of
the
testing
like
so
that
you
only
have
to
integrate
the
pipeline
at
that
one
point:
don't
you
know
don't
run
a
bunch
of
like
really
specific
bash
commands
within
Travis,
because
then
it's
gonna
have
its
own
peculiarities.
Do
everything
do
everything
in
the
repo
okay,
great.
D
D
B
Let
us
know-
and
it's
kind
of
the
same
thing
with
the
troubleshooting
lesson,
if
you
feel
like
this,
can't
get
done
within
a
reasonable
amount
of
time.
It's
totally
fine,
there's
really
not
a
reason
to
like
rush
that.
So
you
know,
fork
comes
up
just
give
us
a
heads
up
and
we'll
plan
accordingly,
this
can
always
get
fun.
Yeah.
B
B
I
think
I
think
that
makes
sense
yeah,
because
there's
really
patch
releases,
especially,
we
should
consider
just
fixes,
like
fixing
things
that
are
broken
and
that's
basically
it.
Maybe
some
very
minor
changes
like
this
one,
adding
the
pack
of
pushers
collection
to
the
bash
lesson
so
I
think
that
makes
sense
perfect.
B
So
yeah,
basically,
these
two
fixes
Derek
is
taking
taking
taking
this
one
I'll
take
I'll
continue
to
troubleshoot
the
stack
storm
lesson,
I
think
we're
close
to
a
solution,
but
we
didn't
quite
get
there.
I
gotta
figure
out.
Maybe
if
we
got
a
I'm
sure
it
has
something
to
do
with
the
requirement
of
txt
stuff
that
Derek
looked
at,
but
maybe
we
just
need
to
rash
it
down
even
even
further,
even
further
than
we
did
and
then
once
that's
done,
I
mean
test.
B
B
This
was
meant
to
just
be
a
trial
run
of
the
release
process
so
that
we
can
get
it
quick
you'll
get
in
the
habit
of
releasing
the
curriculum
separately
and
quickly
so
I'm,
not
kind
of
pressure
on
on
you
know
doing
this
perfectly
or
trying
to
put
as
much
you
know
as
we
can
inside
this
change.
It's
really
just
meant
to
be
like
a
trial
run
of
the
new
process.
B
You
know
in
every
open
source
project
that
I've
participated
in
there's
been
like
a
rotating
kind
of
like
an
kind
of
like
a
while
on
calls,
not
the
right
word
and
it
it
folks
emotions
that
I'm
not
fond
of,
but
like
kind
of
a
rotating
rotating
schedule
of
folks
like
when
a
new
release
was
coming
up
like
a
may,
a
minor
patch
or
minor
version
released,
like
2.2,
for
instance,
of
stack
storm
I,
was
in
charge
of
that
and
and
then
any
patch
release
under
that.
And
that
way.
B
Basically,
everybody
understands
like
when,
when
you
know
who's
on
the
hook
for
organizing
stuff,
that
person
is
very
rarely
on
the
hook
for
actually
doing
the
work
they're.
Just
more.
You
know,
project
manager,
kind
of
lead.
So
if
you're
interested
in
doing
that,
I
would
just
say
you
know:
pay
close
attention
to
the
docs
on
the
release
process
and
then
what
I'm
doing
here,
because
I
would
love
to
hand
this
off.
That
would
be
awesome.
Okay,.
B
Yes,
that's
also
something
we
need
to
figure
out,
because
the
governance
Doc's
are
talking
about
like
different
roles
of
the
project
and
maintainer
x'
and
whatnot,
and
we're
gonna
need
new
github
teams
to
basically
match
that.
So
that's
one
of
the
reasons
that's
still
work-in-progress
is
because
the
governance
Doc's
are
still
work-in-progress,
but
once
that's
solidified,
we'll
we'll
have
that
all
hammered
out.
Okay,.
D
B
Alright,
that's
it
for
me.
I'm
just
wanted
to
cover
cover
that,
because
the
target
dates
Friday,
so
I,
don't
will
probably
will
probably
not
release
on
Friday
will
probably
mark
Friday
as
the
we're
done
with
with
the
work.
Now
we
begin
the
test
phase,
so
the
actual
release
will
probably
be
a
week
after
that.