►
From YouTube: Community Standup: 1/28/20
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
He
also
said
FYI,
my
students
are
delivering
their
projects
results
tomorrow,
and
that
means
I'll
have
some
feedback
for
antidote
flash
entry
labs
in
the
close
future.
They
didn't
produce
much
due
to
all
the
technicalities
and
setting
at
the
environment,
etc.
But
still
that
may
result
in
a
few
commits
sooner
or
later,
I'll
try
to
keep
you
posted.
B
B
A
A
Alright,
you
see
this
yep,
so
it's
done
the
basically
for
the
for
those
that
are
watching.
Basically,
the
thing
we've
been
working
on
with
Red
Hat
for
a
while
is
getting
some
ansible
content
in
the
curriculum.
The
previous
attempt
was
was
a
little
more
complicated
because
it
was
requiring
that
we
sort
of
have
an
image
with
sort
of
ansible
Tower
baked
in
as
well
as
you
know,
having
having
self-medicate
working
on
their
laptop,
and
we
just
decided
to
take
a
different
tack
in
the
last
really
week.
A
To
be
honest,
it's
see,
it
seems
like,
like
my
mind,
is
still
telling
me
that
it
should
be
longer
than
that,
but
really
hasn't
it,
like
literally
from
Monday
to
Monday.
That's
that's
when
this
happened.
So
as
a
results,
we
just
you,
know
well
I.
Basically
what
I
did
was
I.
You
know
we
haven't
launched
on
any
labs
done
IO.
A
Yet
so
I
just
made
that
our
our
test
bed
I
made
that
our
version
of
self
medicate
our
way
to
preview
content
that
we're
working
on
which
obviously
we
can't
do
that
after
the
relaunch,
but
since
we
kind
of
launched
yet
I
decided
to
just
to
move
the
needle
on
this
lesson,
it
was
worth
it
so
yeah.
As
a
result,
we
were
able
to
get
an
answer.
Lesson
done.
That's
nice!
It's
actually
really
nice!
We,
if
you
look
at,
let
me
see
if
I
can
load
it
up
somewhat
somewhat
quickly.
A
A
You
see
it's
four
stages:
they
focus
on
some
some
basic
stuff
within
with
an
answerable.
The
first
step
is
to
enable
Netcom
from
the
Juniper
device
you
can
actually,
you
know
reach
out
to
it.
That's
by
the
way.
This
is
this.
Is
this
this
content
wasn't
necessarily
created
from
scratch.
It
was
actually
copied
from
the
existing
ansible
workshops
curriculum,
so
it's
very
similar
to
what
they've
been
using
in
their
actual
X
formal
training,
which
is
also
very
cool,
so
the
first
step
they
usually
do.
A
Is
they
make
sure
that
the
network
devices
that
they're
about
to
work
with
are
prepped
and
that's
why
that's
the
first
step,
but
then
they
go
into
some
detail
on
some
specifics
on
what
you
might
want
to
know
about
ansible
sort
of
facts
and
basics
of
playbooks,
and
then
we
end
with
making
network
configuration
changes
on
both
Juno's
and
cumulus.
So
we
have
the
cv
x.
Image
we've
had
the
cv
x,
image
in
place
for
a
while,
just
hasn't
been
in
a
lesson.
A
The
existing
ansible
content,
as
I
mentioned
in
their
workshop,
is
already
multi-vendor
with
juniper
and
cisco,
but
unfortunately,
cisco
hasn't
contributed
an
image
to
any
labs
yet,
and
so
since
cumulus
has
I
decided
just
to
sub
that
out
and
the
ansible
folks
were
kind
enough
to
effectively
replace
that
content
and
then
create
create
some
cumulus
steps.
Just
yeah
it
works
really.
Well,
it's
actually
really
cool
it.
Configures,
oh
yeah
between
them.
So
it's
a
multi
vendor
Network,
automation,
lesson!
A
It's
it's
pretty
dope,
nice,
so
yeah
and
in
the
it
looks
great
there's
a
I
made
a
diagram
for
this
lesson.
So
it's
it's.
Just
one
of
I
have
a
feeling.
This
is
gonna,
be
one
of
our
one
of
our
sort
of
you
know
crown
jewel
lessons
because
it's
got.
It's
got
a
lot
of
nice
kinds.
It's
it's
a
there's,
a
good
variety
of
content.
It's
not
just
one
thing
or
one
vendor,
there's
just
a
lot
you
can
play
with
in
here
and
yeah.
Like
I
said
it's
it's
merged,
so
it's
ready
to
go.
A
Not
yet
I
figured
what
more
than
likely
what
we'll
do
is
we'll
in
the
in
the
next
few
weeks
as
we
go
through
some
of
the
other
things
that
we
need
to
do
for
the
relaunch,
because
he's
writing
a
blog
and
there's
a
few
other
things
we
wanted
to
from
that
perspective.
Well,
we'll
just
keep
sending
back
and
forth
ideas
on
on
the
next
steps
that
we
can,
that
we
can
do
my
goal.
A
Is
that
basically,
the
curriculum
plans
that
I'm
putting
together
will
have
us
on
the
track
for
realistically
doing
one
stage
every
two
weeks
and
I
really
do
think
that's
doable.
We
just
got
to
stay
on
it,
so
the
the
release
act,
the
release
immediately
after
the
relaunch
may
or
may
not
include
another
stage
on
this
lesson.
It
kind
of
just
depends
on
how
it
goes,
but
we'll
you
know
we'll
see
with
Sean
what
what
you
know
what
next
steps
he
wants
to
take,
especially
after
it's
gone
live,
and
he
just
said
it
to
some
folks.
A
There
will
be
space
for
it.
I
I'm
pretty
firmly
committed
to
me
meeting
that
curriculum
released
every
two
weeks.
That's
the
more
I
talk
about
that.
The
more
I
like
that
more
like
that
idea,
and
we
don't
have
to
we-
don't
to
boil
the
ocean
to
make
that
happen.
I
think
we've
gotten
into
the
habit
of
trying
to
release
a
bunch
of
content
at
once
and
make
it
very
impressive
and
I'm
kind
of
over
that
model
because
it
ends
up.
It
ends
up
being
more
of
a
water
flow
model
instead
of
a
devil.
A
And
the
in
and
and
I
think
I
got
in
my
head
a
little
bit
saying
you
know
one
one
stage
is
nothing
you
need.
You
need
like
full
lessons.
Well,
not
really
I
think
it's
useful
to
release.
You
know
one
stage
at
a
time
as
long
as
it's
done
frequently
enough
that
it
doesn't.
You
know
it
doesn't
force
people
to
wait
too
long.
A
There's
plenty
of
ideas:
I
mean
if
you
go
to
the
curriculum.
If
you
go
to
the
curriculum
right
now,
you
can
see
like
a
tremendously
large
number
of
issues
opened.
Most
of
them
are
new
lesson
ideas
and
each
one
of
them
and
a
lot
of
those
ideas
are
again
full
lesson
ideas.
So
there's
usually
multiple
stages
involved
with
those
things
so
yeah
that
obviously
teeb
that's
TBD.
That's
that's
opposed
to
relaunch
activities
and
he's
got
plenty
to
do
before
you
need
to
get
to
that
point.
But
it's
something
I'm
something
I'm
thinking
about
yeah.
B
A
A
Are
and
if
you
look
at
the
screen,
the
the
Kanban
board
for
the
curriculum
is
up
there
and
you
can
see
it.
It's
pretty
heavy
on
the
right,
which
is
awesome,
because
that
means
we're
almost
done
and
the
only
two
and
and
so
like
all
the
ansible
lesson
is
done.
There
were
also
a
bunch
of
there
are
a
bunch
of
issues
with
the
current
curriculum
and
things
being
broken
and
whatnot.
Just
from
various
things
like
software
upgrades
and
whatnot
and.
B
A
Fixed
all
those
those
are
all
fixed,
so
the
old
literally,
the
only
two
things
we
have
left
to
do
are
the
two
new
lessons
the
get
lesson
and
the
revamp
of
the
rest.
Api's
lesson:
the
get
lesson
is
almost
done.
I
was
originally
going
to
take
on
one
more
stage,
but
I'm
gonna
save
that
for
later,
because
again,
I'm
gonna
try
to
do
many,
many
more
releases
it
for
the
curriculum
over
the
over
over
the
next.
You
know,
basically,
you
know
setting
the
stage
to
make
many
more
frequent
curriculum
releases.
A
So
that's
not
a
big
deal.
The
the
stage
I
had
in
mind
relies
on
a
classical
feature.
That's
not
quite
finished
yet
so
I'm
gonna,
I'm,
gonna,
I'm
gonna
delay
that
and
release
the
three
or
four
I
can
remember.
I.
Think
four
stages
that
I've
built
in
this
lesson,
thus
far,
which
is
still
very
substantial
way
more
than
what
we
currently
have,
which
is
like
a
single
stage
with
two
commands.
A
So
this
is
effectively
a
new
lesson
and
then
the
same
thing
will
need
to
be
true
for
the
rest,
ap
guys
lesson
and
I
had
you
know
like
like
I
said
this
is
the
the
reason
this
is
almost
the
reason
this
curriculum
Kanban
board
is
almost
done
is
because
this
is
continuing
to
receive
my
soul
focus
until
it's
all
done
so
I'm
hoping
that
probably
tomorrow,
to
be
honest,
my
goal
is
to
buy
by
tomorrow.
A
Both
of
these
columns
will
be
empty
and
will
be
ready
to
cut
a
new
release
of
the
curriculum
and
then
turning
my
attention,
then,
to
the
antidote
release.
Also
in
a
very
similar
situation,
just
need
to
tie
some
things
up.
This
sum
this
tax
task
here
isn't
really
even
a
platform.
This
is
actually
just
I,
like
I,
said:
I
used
to
put
antidote
a
table
stacks
in
here.
This
is
just
a
task
that
I
need
to
take
on
to
do
the
actual
release.
A
It's
not
an
actual
task
for
the
platform
itself
and
then
there's
two
other
things
that
are
that
are
fairly
minor.
I
I
noticed
some
strange
behavior
on
Chrome,
with
respect
to
cross-origin
requests
and
I
haven't
been
able
to
replicate
it.
So
I
may
have
to
drop
this
and
it's
not
a
huge
deal,
it's
hard
to
explain,
but
it's
it's
it's
not
a
blocker.
If
it
comes
down
to
it,
we
need
to
make
a
release.
This
can
wait,
and
the
same
thing
I
think,
is
true.
A
With
this
comment,
our
contractor
Nils
made
a
comment
on
on
one
of
the
PRS
that
I
made
and
he
said
that
it
wasn't
a
super
major
issue,
but
it
might
be
something
that
I
want
to
slightly
modify
and
I
was
a
little
bit
confused
on
what
he
was
saying
so
I
emailed
him
and
asked
for
clarification.
So
the
reason
I'm
saying
all
of
this
you
know
babbling
a
little
bit
is-
is
that
were
imminent
on
and
on
a
release
of
the
platform
as
well.
A
Both
the
curriculum
and
Lee
and
the
platform
are
both
very
nearly
ready
for
further
releases
and
I
am
absolutely
going
to
try
to
get
everything
done
well
before
the
end
of
this
week.
Hopefully
well
helpfully
well
before
the
end
of
this
week,
but
at
the
I
guess
in
the
worst
case
scenario
by
the
end
of
the
week,
because
I
want
to
be
able
to
allocate.
You
know
basically
the
entirety
of
next
week
for
testing
cool.
A
Yeah
yeah,
that
would
be
great
they'd,
be
great.
We
still
I
mean
I
think
it's
still
fair
that
we
should.
We
should
have
a
lesson
that
more
more
specifically
looks
into
doing
automation
generally
with
cumulus,
specifically
because
that
doesn't
exist
yet
yeah.
B
A
Well,
yeah
yeah,
probably
probably
mentioned
briefly
but
I'll
bring
it
up
in
following
meetings.
Let
me
assure
my
screen
once
more
and
I'll
tell
you
what
I
mean
the
thing
that
I
think
might
need
to
get
brought
up
more
than
once
you
may
have
to
have
other
people
on.
The
call
for
this
is
the
the
code
of
conduct
is
still
not
merged.
We
merged
the
the
the
governance
talk
long
time
ago,
but
we
never
merged
the
the
code
of
conduct
doc.
Oh
no,.
A
Okay,
well
then
I
was
confused,
so
I
will
merge
this
and
I
the
reason
I
the
that
I
got
my
the
reason
that
my
attention
was
drawn
to
this
was
because
in
our
in
the
docs
this
is
a
linked
or
in
the
site.
This
is
links
to
the
pull
request
instead
of
actual
file,
it
would
be
useful
and
the
reason
for
that
is
because
it's
not
merged
other,
so
I'll
I'll
merge
this
and
then
I'll
update
all
the
references
to
be
the
actual
file.
Just
like
the
government
stock
is
okay.
B
A
B
A
B
A
And
then
the
last
thing
I
wanted
to
bring
up
and
I
won't
go
into
detail
on
this
because
again,
I
think
this
is
first
off
the
thing
that
the
design
change
that
proposing
is
not
going
to
happen
for
this
release,
so
it's
not
relevant
for
the
relaunch.
This
is
at
least
a
month
or
two
out,
but
the
the
way
that
we
present
HTTP
content.
This
kind
of
does
link
into
my
get
lesson.
I
was
gonna,
show
an
end
point
that
has
get
labs,
so
people
can
understand
how
to
open,
pull
requests
and
things
like
that.
A
The
main
problem
with
with
showing
web
content
today
well
originally
it
was
that
the
abstraction
for
doing
so.
It
was
really
bad.
The
way
that
you
defined
a
piece
of
content
in
your
lesson
that
showed
a
web
UI
of
some
kind
was
really
awful.
Fortunately,
we
fixed
that
in
ODOT,
for
so
the
way
that
you
do,
that
is
through
the
new
presentations
thing,
which
is,
which
is
nice.
It's
a
nice
way
of
thinking
about
how
to
define
the
way
that
you
want
to
show
your
content.
A
For
why
this
is
important
is
it
will
finally
give
people
a
reason
and
an
ability
to
show
content
from
a
web
perspective
without
placing-
and
this
is
the
current
hurdle-
without
placing
a
huge
emphasis
on
image
writers.
The
which
is
a
which
you
know
creating
images
in
in
energy
labs
is
still
one
of
the
biggest
hurdles
that
we're
trying
to
solve
and
I
think.
A
This
will
help
alleviate
some
of
that
pressure,
because
right
now
the
way
that
you
the
way
that
the
way
that
you
are
the
only
way
that
you're
able
to
show
web
content
is,
if
you
configure
your
image,
to
sort
of
jump
through
hurdles
to
show
that
content-
and
it's
not
it's
not
scalable.
So
we
want
to
make
it
a
lot
easier
for
people
to
do
that.
This
is
I
think
this
is
the
path
to
do
that.