►
From YouTube: Community Standup: 2/18/2020
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
A
A
B
B
B
A
B
Than
doubled,
yeah,
that's
crazy.
It's
crazy
and
my
theory,
I
think
is,
is
is
working
out.
If
you
look
at
the
the
breakdown,
the
the
the
lead,
one
was
ansible
and
I.
Don't
think
that
was
a
surprise,
but
then
the
this,
the
second
one
was
a
the
Linux
basics
and
then
get
and
then
bash
and
then
yeah
Mille
right.
A
B
A
B
A
B
It's
it
does
seem
to
be
sort
of.
Let
lily
and
ansible,
of
course,
is
not.
Is
not
a
fundamentals
lesson
so
I
don't
know,
maybe
that's
just
how
it
worked
out.
Maybe
maybe
people
are
just
migrating
to
those.
My
green
to
those
lessons,
I
mean
if
you
look
at
the
catalog
it
literally
four.
You
know
refresh
the
page,
it's
populated
by
it
by
a
you,
know
an
unordered
data
type
in
the
backend.
So
there's
there's
no
ordering.
You
know
that's
possible.
Basically,
if
you
refresh
it,
you
get,
you
get
different
results
every
time.
B
A
B
Wonder
if
that's
something
we
could
see
in
Google,
Analytics
I
still
don't
know
when
it
comes
down
when
it
comes
down
to
like
drilling
in
like
that
kind
of
detail,
I'm
not
even
sure
if
it
shows
it
and
they've
enough
did
I'm,
not
a
power
user
for
Google,
Analytics,
I,
know
basic
stuff.
Like
page
views
and
stuff
like
that,
yeah.
A
B
B
Part
of
the
package,
I
think
I
mean
I'm
sure
there
are
some
aspects
that
are
paid
but,
like
I
said,
I'd
I
would
expect
that
there
are
a
lot
of
things
that
I
just
haven't
gotten
into
myself.
That
are
part
of
the
package,
so
I
haven't
even
when
it
comes
time
to
getting
to
it's.
Just
you
know,
features
that
are
so
advanced
that
you
have
to
pay
for
it:
I'm,
not
even
I'm,
not
even
close
to
being
able
to
consume
those
things.
Okay,.
A
B
A
B
A
B
C
B
A
B
B
Okay,
so
a
recap
of
the
launch,
so
I
I
mean
we
were
kind
of
just
talking
about
this
all
to
show
the
visuals
just
for
impact
instead
of
the
last
seven
days.
Let's
do
previous
week
there
we
go
so
this
is
when
we
launched
right
about
here
is
when
we
started
sending
everything
out
things.
I
remember
my
first
tweet
I
sent
like
here
and
I'm
like
hey
a
lot
of
people
found
the
instable
lesson
and
little
did
I
know
that
it
would
literally
triple
in
terms
of
good
current
lesson.
Usage
now
keep
in
mind.
B
This
isn't
the
only
thing
going
on
like
there
were
19
people
using
the
ansible
lesson
at
this
point
or
at
Lille
closer
to
22.
But
there
were
a
lot
of
other
lessons
in
use
to
a
lot
of
which
had
to
lessons
than
you.
So
you
know
wasn't
just
the
ansible
show
that
would
just
there
was
actually
a
lot
going
on.
B
So
if
there's
one
lesson
of
one
lesson
and
there's
and
there's
one
other
instance
of
another
lesson
being
used,
this
the
sit
on
top
of
each
other.
So
just
keep
that
in
mind,
but
yeah
the
the
usage
was
good
and
you
can
see
I
added
a
counter
here.
The
the
official
number
for
the
week
was
thirteen
hundred
and
seventeen
lessons
launched.
And
if
you
look
at
this,
you
can
see
the
breakdown
here.
We
have
this
data
in
a
spreadsheet.
That's
that's,
I!
Think
public!
B
The
you
know
first
lesson
is
ansible,
obviously
pretty
pretty
big
piece
of
content
with
531
for
the
week,
but
the
other
ones
had
a
pretty
good
showing
too
and
as
we
kind
of
discussed,
the
the
fundamentals,
one,
the
fundamentals,
lessons
definitely
showed
up
and
I
think
this
is
important,
because
now
the
new
web
UI
randomizes,
the
catalog,
so
these
are
people-
are
actually
seeing
these
lessons
out
as
opposed
to
just
sort
of
clicking
on
the
first
thing
they
see
so
that
I
think
that's
cool
the
the
this
is
obviously
I'd
want
to
have
more
than
just
one
week
worth
of
data,
especially
a
launch
week,
which
has
its
own
biases
built
in,
but
in
general
I'm
feeling
good
about
the
the
fact
that
I'm
sort
of
personally
focusing
in
terms
of
curriculum
development
well
am
I'm
feeling
good
about
that
in
general,
but
also
the
specific
curriculum
elements
that
I
personally
am
committing
to
keeping
you
know.
B
B
Yeah
yeah.
In
fact,
we
were
kind
of
talking
about
that
on
the
last
meeting
that
we
had
with
them.
I
think
probably
the
next
step
is
I,
can't
remember
what
I
have
notes
on
this
I.
Just
don't
have
them
in
front
of
me,
but
yeah
there's
definitely
interest
in
fact,
I
think
for
Shawn.
The
big
thing
is
like
look.
Did
the
initial
ansible
lesson
was
a
was
a
good
step
in
the
right
direction
in
terms
of
just
getting
interest
within
within
RedHat
for
an
Ori
labs.
B
The
real,
the
real
amo
that
he's
gonna
want
is
is
to
sort
of
continue
down
that
path
and
build
in
as
much
ansible
content
as
possible,
including
some
of
their
higher
level
management
stuff.
So
that's,
there's
I
I
won't
have
to
I.
Won't
have
to
convince
him
of
that
for
sure
it's
just
a
matter
of
getting
it
done
and
when
so
I'm
sure
we'll
find
time
for
that
over
the
next
month
or
two.
B
A
B
Okay,
yeah
well,
we'll
put
it
somewhere.
Let
me
figure
out
where
I
was
I.
Have
so
many
things
open?
Oh
my
god.
Okay,
so
here
is
where
it
gets
posted
one
thing,
I
discovered
so
I
have
there's,
there's
automation
running
in
the
backend,
the
same
thing
that
posts,
those
stats
to
slack,
also
post
them
here
and
I
I.
B
Could
this
is
by
the
way
this
is
easily
fixable
I
just
haven't
gotten
around
to
it,
but
in
this
spreadsheet
we're
missing
most
of
November
in
all
of
December,
in
fact,
from
from
early
November
through,
in
fact
all
of
January
as
well.
In
this
spreadsheet,
the
data
still
exists
in
the
this
is
not
the
primary
way
of
storing
the
statistics
so.
A
B
I
could
easily
go
back
and
get
you
know,
go
go
to
the
source
and
and
get
them,
but
I
just
haven't
yet.
But
anyway,
the
point
I'm
trying
to
make
is
the
reason
that
is
that
we
don't
have.
Those
stats
is
because
apparently
Google
sheets
is
limited
to
column,
a
e
like
it
won't.
Let
you
create
more
columns.
B
Okay,
maybe
I
hold
on
I'm,
second-guessing
myself
now,
cuz
I
can
just
do
it
manually,
I,
don't
know
I,
don't
know,
I
don't
know
anyway.
I
will
figure
that
out,
but
regardless
we
have
a
second.
A
second
sheet
I
took
I
took
the
data
that
we
had
already
and
I
put
it
on
I
put
it
on
its
own
sheet,
and
now
the
automation
is
resumed.
As
you
can
see,
everything
got
posted
correctly.
We
had
also
by
the
way
the
week
before
this
with
a
measly
360,
which
apparently
included
22
instances
of
the
ansible
lesson.
B
Pre-Launch
cuz
I,
think
I
I
think
I
turned
on
the
telemetry
for
this
before
before
their
launch,
which
makes
sense,
but
anyway,
yes,
1388,
so
we'll
track
this
going
forward.
I
think
this
especially
this
this.
This
new
data
set
that
you
know
that's
post,
launch
and
like
sort
of
randomized
we're
gonna
be
able
to
actually
see
from
a
you
know
from
a
weekly
perspective,
what
has
grown
in
popularity
and
what
has
decreased
in
popularity.
I.
Think
that
sort
of
macro
view
might
be
helpful
anyway.
B
B
A
Well
so
question
here:
are
we
thinking
primarily
it's
about.
B
B
Well,
what
I
don't
want
to
do
is
I,
don't
want
it
to
turn
into
like
a
hey,
I
had
an
issue
this
one
time
and
blah
blah
blah.
You
know
what
I
mean
like
that's
kind
of
not
what
I'm
going
after,
because
that's
that's
more
just
like
troubleshooting
in
the
moment,
and
we
we
have
plans
for
helping
out
with
with
things
like
that,
like
little
little
help
boxes
in
the
UI,
that
you
can
click
and
you
know,
send
your
debug
in
from
information
to
the
to
the
team
and
whatnot
we're
still
gonna.
B
Do
that
for
the
survey
I'm
I
would
say
the
probably
are
some
UX
related
things
that
we
could
ask.
We've
got
to
be
careful
about
opening
up
the
can
of
worms
there,
mostly,
though
I
think
I'm
I'm
interested
in
it.
You
know
what,
if
you,
if
you've
been
involved,
if
you,
if
you
looked,
if
you
looked
at
the
curriculum,
what
do
you
think
about
it?
What
do
you
think
is
missing,
you
know
if
you
and
then
maybe
maybe
get
into
a
little
bit
about
contributing
like
if
you
haven't
contributed.
Why
not
like
what?
B
What
kind
of
things
have
you
written?
You
know
get
get
a
finger
on
the
pulse
of
why
folks
haven't
contributed
to
the
curriculum
things
like
that,
so
it's
very
creative,
very
curriculum
focused,
but
not
exclusively,
and
not
just
on
users
either
it's
more
of
like
a
it's
more
of
like
a
general
curriculum
survey.
A
B
That
doesn't
really
tell
me
much
I
what
drives
my
involvement
in
the
project
is
mmm-hmm
I
mean
even
outside
of
just
like
the
open
source
elements.
It's
it's
actually
to
help.
The
industry
learn,
automation,
I
mean,
and
so
like
I
like
that,
that
has
to
be
I
have
to
get
more
information
on
that
I
have
to
get
more
information
on.
Are
we
actually
meeting
that
goal
or
are
either?
Are
we
even
aiming
towards
that
goal?
So
that's
kind
of
what
the
the
survey
started
off
as
yeah.
A
B
B
B
Cool
yeah
I
will
so
it
sounds
like
you
want
to
take
an
initial
stab
at
that
yeah.
A
B
Good
to
me
cool
the
the
the
the
only
thing
on
the
on
the
agenda
as
far
as
the
remaining
and
items
on
the
agenda
or
the
next
steps
for
the
curriculum
and
the
antidote
platform,
the
curriculum
is
very
straight
forward.
In
fact,
I
will
just
we'll
just
call
this
I'll,
you
know,
I,
haven't
I,
haven't
done
the
the
kickoff
posts
in
the
forum
I'll.
B
Do
that
today
will
consider
this
will
consider
this,
the
the
official
kickoff
for
the
curriculum
release,
because
I
know
that
that's
more
tangible
I
may
wait
on
the
antidote
the
next
antidote
released.
Just
because
I
want
to
figure
out
where
things
are
at
mm-hmm
they're
a
little
bit,
so
we
I
might
wait
there.
I
do
have
a
note
too.
I
do
have
something
to
mention
on
the
antidote
thing,
because
we
actually
did
it.
We
did
it
like
a
second
patch
release
over
the
weekend
very
minor
thing,
but
to
circle
back
onto
the
curriculum
first.
B
The
reason
that's
solid
is
because
we
have
curriculum
releases
planned
out
kind
of
ad
infinitum
like
through
it
through
the
summer
practically.
So
we
kind
of
know
where
that's
at
at
a
minimum
we'll
be
publishing
is
the
next
stage
in
the
get
lesson,
because
that's
that's
where
we
started
with
the
labs
and
watch
a
video
series,
and
so
we're
just
gonna
keep
keep
going
down
that
path,
so
that'll
be
version
1.0
or
1.1.1.
B
I
guess
I
think
yeah.
What
are
we
on
one,
not
one
two?
Oh
yeah
yeah,
so
one
down
1.1,
so
no
minor
release
just
because
it's
just
an
update
to
the
to
the
to
the
get
lesson.
There's
also
been
some
fixes
of.
In
fact,
speaking
of
Olivier
Olivier
submitted
a
PRF
to
make
a
minor
fix
to
the
existing
get
content.
B
B
The
ansible
lesson
has
an
issue
I'll
ping
Sean
today
and
ask
if
he's
had
any
progress
on
that
he
said
he
wanted
to
ask
some
internal
ansible
engineers
if
they
have
any
ideas
at
first
I
thought
this
might
have
been
a
VQ
FX
issue,
but
he's
since
it
only
seems
to
be
happening
with
this
one
module
and
in
the
VQ
effects
in
this
lesson
is:
is
operating
normally,
otherwise,
so
I
guess
being
like
the
the
NRI
lab.
The
antidote
platform
is
actually
you
know
configuring
it
properly.
B
B
He
might
be
able
to
adjust,
but
I
haven't
heard
from
him
on
that
so
I'll
ping,
him
on
that
and
see
what's
going
on
the
other
issue
that
was
brought
up
and
I
haven't,
had
a
chance
to
try
to
or
I
haven't,
been
able
to
reproduce
this
yet.
But
another
user
reported
that
there
was
an
issue
with
the
stack
storm
lesson.
B
B
Fortunately,
doesn't
look,
it's
like
it's
the
whole
lesson.
It's
just
two
of
the
stages
seem
to
you
know
failing
to
initialize
and
it
obviously
is
intermittent
because
I
haven't
been
able
to
reproduce
it.
So
we'll
give
this
a
shot.
If
we
can
reproduce
it,
we
might
just
have
to
say
you
know
like
it
doesn't
can't
reproduce
it.
So
if
you
can't
reproduce
it,
it's
really
hard
to
fix
anyway.
B
There's
those
issues
like
that,
what
I'll
do
is
I'll
create
the
I'll,
create
the
kickoff
post
as,
as
is
the
standard
you
know,
sort
of
release
process
I'll
create
that
today
and
basically
say
look
we're
aiming
we're
aiming
to
do
this
release.
You
know
effectively
by
the
end
of
the
week
and
we'll
and
we'll
publish
it.
You
know
basically,
over
the
weekend.
B
B
No
worries
that's
effectively.
Oh
that's
right.
I
wanted
one
more
thing:
antidote.
Next
steps
like
I
mentioned
the
the
platform
features
that
are
next
from
the
features
that
are
next
room,
like
sort
of
an
antidote
platform
perspective
are
actually
a
little
bit
more
long-term.
So
there's
not
a
huge
need
to
kick
that
off
like
right
now,
I
think
what
I'll
do
is
I'll
I'll
I'll
spend
more
time
doing
some
proper
triage
for
what
will
be
0.6
dot
zero
for
that
I
do
want
to
mention.
B
You
might
notice
that
in
the
middle
of
the
relaunch
week,
we
had
some
variation
here
in
the
lesson
startup
time
now.
These
were
there
were
still
plenty
of
plenty
of
lessons
that
spun
up
quickly,
but,
as
you
can
see,
some
of
the
lessons
took
upwards
of
150
and
in
some
very
extreme
cases,
over
200
seconds
to
start,
which,
admittedly,
is
still
pretty
quick.
B
If
you're
talking,
if
you're,
comparing
it
to
some
other
sort
of
environment
learning
environments,
200
seconds
is
not
like
that
big
of
a
deal
but
from
an
from
an
ad
you
look
at
it.
If
you
look
at
an
average
like
what
we
are
accustomed
to,
especially
one
of
the
reasons
why
we
moved
to
bare
metal
is
because
we
can
provision
any
lesson
in
in
under
in
under
hunt
100
seconds
and
in
most
cases
under
a
minute
which
is
which
is
nice
but
the.
B
But
the
you
know
that
portion
of
the
week
we
saw
some
variation
and
some
really
crazy
variations
and
I
think
I
figured
out
why
it
turns
out
that
the
well
I,
basically,
one
of
the
ways
that
we've
deployed
curriculum
content
into
the
environment
is
through
git.
So
the
lesson
content
is
in
the
NRI
labs,
curriculum,
github
repository,
and
so
what
we
did
was
we
we
effectively
downloaded
this
repo
every
time
we
wanted
to
start
a
lesson,
it's
actually
worse
than
that,
because
there
were,
we
didn't
use
any
sort
of
shared
directories
on
the
cluster.
B
So
what
we
ended
up
doing
was
cloning.
It
once
for
every
single
lesson,
end
point
in
a
lesson
and
then
doing
all
of
that
for
for
each
instance
of
that
lesson,
that
was
spawned
so
you're.
Basically,
cloning,
a
git
repository,
maybe
you
know
total
of
five
to
seven
to
ten
times
for
every
lesson
that's
launched,
and
that
takes
a
few
seconds
and,
of
course,
it's
dependent
on
internet
connectivity,
and
you
know
github
and
all
of
that
stuff.
The
reason
we
did
this
by
the
way
is
cuz.
B
It
ended
up
being
a
lot
easier
than
managing
sort
of
shared
directories
on
the
cluster.
It
was
just
one
of
those
things
early
on
in
the
project
where
I
was
like.
Look
it's
obviously
not
a
great.
You
know
thing
to
do
from
a
performance
perspective,
but
we've
got
other
problems
right
now.
So,
let's
just
do
that!
Look
well,
we've
actually
grown
a
lot
since
then,
and
now
this
is
a
pretty
big
bottleneck
and
I.
Think
what
happened
in
this
variation
was
github
released.
B
A
new
command
line
tool
called
gh
around
this
time,
like
right
as
soon
as
we
started,
seeing
this
variation
and
I'm
pretty
sure
they
started
to
do
some
rate
limiting,
which
meant
that
the
the
time
that
it
took
to
download
those
read
the
the
curriculum
for
each
end,
point
was
slowed
and,
as
a
result,
lesson
startup
time
was
slow,
so
I
said:
look
I
wanted
to
move
away
from
this
module
for
a
long
time.
Just
we
have
the
curriculum
already
cloned
on
each
server
in
the
cluster.
B
All
we've
got
to
do
is
just
look
at
it
and
copy
those
files
in
directly
from
the
filesystem,
so
I
made
the
necessary
code
changes
to
syringe
spent
the
weekend
testing
them.
They
worked
great
and
I
just
deployed
it
as
a
patch
version
on
Sunday
and
we
are
off
and
running,
and
so
hopefully,
no
more
variations
like
that.