►
From YouTube: Community Standup: 1/7/20
Description
Community Standup: Jan. 7, 2020
A
A
A
B
B
So
this
can
get
done
prior
to
that,
which
is
the
other
thing
I'm
going
to
be
talking
about
today,
but
some
of
the
can't,
so
the
majority
of
what's
on
this
plan
is
just
for
sure
everybody
to
know
sort
of.
What's
up
and
well
what
will
be
waiting
on
to
do
the
actual
relaunch?
Why
haven't
we
got
it
already,
one
of
the
things
that
we
still
need
to
do
before
we
can
actually
kick
things
over.
B
So
mostly
it's
documents
for
is
for
information
purposes
if
you're
curious
about
how
we're
doing
some
of
the
DNS
stuff
I'm
having
to
set
up
some
time
with
you,
because
that's
more
on
the
outside
and
as
always
I
would
love
help
on
that.
So,
just
let
me
know
if
you
have
it
any
interested
in
seeing
how
this
works,
but,
generally
speaking,
this
is
just
a
document
that
is,
you
know,
keeping
my
helping
me
keep
my
sanity.
B
One
of
the
things
that
we
want
to
do
before
the
relaunch
is
have
a
new
release
of
both
the
platform
in
the
curriculum.
The
reason
for
that
is
a
lot
of
the
changes
that
we're
putting
into
the
web
front-end
will
be
landing
in
a
new
version
of
the
platform,
because
we
have
to
you
know
we
have
to
create
a
release
that
include
those
changes
in
order
to
deploy
it
and
since
we're
doing
the
platform
release,
we
might
as
well
also
do
a
curriculum
release.
B
A
lot
of
stuff
that
we
want
to
fix
in
the
current
curriculum.
Probably
add
some
lessons
as
well
coming
to
that
in
a
second.
But
those
are
those
are
that's
why
the
platform
release
in
the
curriculum
release
are
happening.
It's
part
of
this
relaunch
because
we
haven't
done
either
in
a
while,
and
it's
probably
a
good
idea
that
we
do
that
anyway,
the
the
changes
are
great.
B
If
you
haven't
seen,
if
you
haven't
seen
the
the
preview
that
I
threw
up
last
week
or
last
session,
go
ahead
and
look
at
that
recording,
but
it's
gonna
be
really
really
cool.
I
just
had
a
devil
last
Friday
from
our
contractor,
with
the
new
terminal
extra
with
WebEx
h2
and
all
that
stuff
working
and
it
it
it's
really
great.
It's
really
really
really
great,
not
just
the
not
just
the
functionality
of
it
in
the
speed
and
the
performance,
but
also
just
how
easy
and
and
flush
it
is
with
the
rest
of
the
page.
B
B
So
what's
gonna
happen
more
than
likely
more
than
likely
before
we
actually
do
the
platform
release
is
we're
gonna,
be
deploying
the
latest
version
of
everything
to
the
new
site,
but
it'll
be
it'll,
be
rough.
We
want.
We
expect
that
there
will
be
issues
there.
The
objective
that
there
is
to
hash
out
any
issues
that
we
you
know
we
have
encountered
once
once.
The
work
from
this
contractors
been
merged
then
effectively.
What
we'll
be
doing
at
that
point
is
we'll
be
working
through.
B
The
excuse
me
we'll
be
working
through
the
plan
to
actually
you
know
we'll
be
working
through
the
the
release
plan
for
ona
v,
dot,
o
and
1.1,
so
that'll
be
that'll,
be
the
thing
that
we
can
actually
start
doing
now.
Hopefully,
within
the
next
few
weeks,
all
of
that
will
be
finished.
The
Moto
V
work
will
be
done.
The
platform
release
work
that
we
planned
will
be
done.
I'm
also
I,
wanna
I've
just
made
this
decision
last
night,
so
you'll
see
references
doe
at
5:00
that
oh
I'm
actually
not
proposing.
B
We
do
that
I'm
we're
just
gonna.
Do
it
patch
release
to
the
latest,
which
is
o
dot
4.1,
because
we're
not
making
a
lot
of
platform
changes?
This
is
not.
This
is
not
a
significant
release.
It's
just
making
sure
that
everything
is
is
good
with
with
the
latest
changes
to
the
to
the
web
frame.
So
that's
the
main
thing
so
yeah,
basically
it
would.
It
would
be
great
if
it
you
know,
maybe
in
the
next
two
or
three
weeks,
all
of
that
all
three
of
those
efforts
converge
at
the
same
time.
B
So
there's
a
few
things
we
need
to
do
and,
via
you
know,
redirects,
but
that's
very
straightforward.
Cloudflare
does
that
very
easily,
so
we'll
just
you
know,
I'm
ready
to
cut
over
we'll
make
the
cut,
and
it
really
is
that
simple
I
know
there's
a
few
cleanup
things
that
we
want
to
do
after
the
fact.
But
that's
not
too
bad,
so
the
other
thing
I
wanted
to
talk
about
was
was
what
I
alluded
to
the
beginning.
B
If
we're
gonna
be
incorporating
new
platform
releases
and
new
and
a
new
curriculum
release,
what
is
that
going
to
look
like?
Well,
a
platform
release
is
pretty
simple
because
mostly
it's
it's
just
you
know,
Canley
is
there
anything
that
we
can
do
to
to
improve
the
platform
experience
minimally
and
it
may
be
it
to
be
honest,
I'm
waffling
a
little
bit.
It
may
be
an
o
dot
v
dot
o
because
of
all
of
the
changes
in
the
web.
Front-End.
So
we'll
see,
I
haven't
done
the
release
kickoff
for
that
yet,
but
I'll
do
that
today.
B
So
I
don't
know
if
all
these
changes,
this
isn't
business.
An
old
project
I
set
this
up
a
long
time
ago.
So
keep
in
mind
this
will
change.
These
issues
have
been
in
this
release
planet
for
a
long
time,
some
of
them
I
may
punch
for
a
future
release.
Because,
again,
we
want
to
make
sure
we
can
get
the
work
done
in
the
next
two
or
three
weeks,
so
it
won't
be
taking
on
anything
crazy,
ambitious
in
that
period
of
time.
B
But
when
I'm
ready
to
kick
off
that
kick
off
that
release
plan,
I
will
do
so
and
then
obviously
everybody
can
comment
and
let
me
know
what
what
they
think.
The
other
aspect
of
this
is
the
1.1
release
for
the
curriculum.
This
is
more
important
because
we
want
to
make
sure
that
all
of
our
content,
a
you
know,
shows
up
properly
in
the
new
web.
Ui
I,
don't
anticipate
problems
with
that.
You
know.
B
The
way
that
lessons
are
stood
up
is
not
changing
with
all
of
these
web
UI
changes,
but
it's
a
good
idea
to
at
least
you
know,
do
do
some
heavy
testing
for
everything
that
we
do
have.
In
addition,
there's
plenty
of
issues
that
we
know
we
have
and
and
some
of
which,
like
Olivier,
brought
up
the
you
know
the
latest
napalm
problem.
B
Storm
less
so
it
seems
like
that's
always
or
maybe
it's
the
Nate
homeless
and
I
can't
remember.
If
it's
text
or
maple
stacks
Ron
seems
like
that
lesson
always
has
problems,
but
again
we
we
haven't
done
a
curriculum
release
in
a
long
time.
So
a
lot
of
these
issues
have
been
sort
of
outstanding
for
a
long
time.
So
we
need
to
fix
this.
B
I
will
say:
I
have
I
I
do
not
want
to
run
the
curriculum
release.
I
I
feel
pretty
strongly.
This
needs
to
be
somebody
else.
I
I
could
do
it
I'm
happy
to
do
it
if
I,
if
we
need
to,
but
this
is
one
of
those
things
where
I
would
prefer
that
somebody
step
up
and
be
a
release
manager
in
the
in
a
lot
of
open
source
projects.
That's
how
it's
done.
Actually,
there's
a
you
know.
B
B
I
just
want
to
let
everybody
know
that's
kind
of
what
my
what
my
desired
outcome
is
for
this,
but
basically
we
need
somebody
to
you
know
sort
of
Shepherd
through
these
issues
not
necessarily
fix
everything,
but
at
least
stay
on
top
of
this
plan
and
say:
hey
so-and-so.
You
know
Matt
you're
a
side
of
this.
What's
the
status
of
that
things
like
that,
and
that's
pretty
much
it
like
I
said
the
the
the
work
that
we
can
do
now
is
these?
Are
these
two
release?
Are
these
two
plans?
B
You
know
the
new
rule
they're
the
new
release
for
the
platform,
the
new
release
for
the
curriculum,
we're
starting
that
work.
Probably
like,
like
I
said
now.
The
curriculum
is
more
important
because
we've
got
just
issues
to
fix.
So
that's
why
I
have
this
here
again,
this
plan
has
existed
for
a
long
time,
but
I
went
through
and
I
updated
it
last
night
and
the
goal
will
be
I.
B
Think
I
updated
the
release
plan
if
you
go
to
the
for
the
curriculum
anyway,
if
you
go
to
the
kickoff
thing,
there
I
did
the
original
post,
which
was
back
in
September.
That's
how
long
this
has
been
outstanding
and
updated
it
with
a
new
target
release
date,
which
is
January
17th
2020,
which
should
be
doable
I,
don't
see,
I
mean
everything
you
know
things
happen,
but
that
that
should
be
a
doable
milestone.
I
mean
what
we're
doing
here
mostly
in
this
in
this
release,
isn't
50
new
lessons.
B
It's
mostly
just
fixing
existing
lessons
and
then
maybe
like
one
additional
piece
of
content
as
a
stretch
goal
so
yeah.
The
the
plan
for
the
relaunch
kind
of
depends
on
us
pulling
that
off
within
the
next,
probably
two
weeks,
because
that
puts
us
sort
of
like
into
into
the
like
the
last
third
of
January,
and
then
you
know
the
rest
of
the
plan
once
that's
done
well,
you
know
ideally
we'll
be
about
this
point.
We
can
kick
off
a
new
release
workflows.
B
The
only
thing
we'll
have
to
do
at
that
point
is
testing
making
sure
that
everything
works
properly,
and
you
know
that
should
be
that
should
be
doable
within
a
week.
So
that's
that
those
are
the
three
efforts
that
I'm
trying
to
get
to
converge.
At
the
same
time
the
BtoB
work
and
then
the
to
the
platform
release
and
then
the
curriculum
release.
C
So,
for
me,
from
actual
you
know,
sort
of
launch
and
making
noise
standpoint
I
think
we
need
to
come
to
ground
pretty
quickly
on
a
release
date
so
that
we
can
plan
accordingly.
So
a
number
of
the
things
that
we
need
to
do
for
me,
noise
making
perspective
we'll
take
it.
Yes
have
it
at
least
a
couple
weeks
lead
time.
B
Yeah
I
would
I
would
say:
let's
just
let
go
ahead
and
just
aim
for
early
February,
just
to
be
safe,
I
mean
everything
I'm
seeing
like
like
the
Tobey
bateau
Vee
is,
is,
is
trucking
along,
like
that's.
That's
going
so
I
have
no
reason
to
be
worried,
but
I
figured
just
just
to
make
sure
we
have
time
to
do
everything
else.
It's
it's
not
that
I,
don't
trust
them.
It's
just
that
I
haven't
mm-hmm,
I,
haven't
deployed
it
yet
and
I
don't
want
to
be
able
to
deploy
it
right.
C
B
C
D
C
C
D
C
B
We
I
I
I,
think
the
the
the
the
plan
that
we
put
together
with
mp1
is
good
I,
don't
think
I,
don't
think
any
of
that
work
is
unnecessary,
but
I'm,
leaning
towards
postponing
that
work
for
the
time
being,
I
think
we
I
think
we
were
in
a
position
now,
especially
with
the
relaunch,
where
we
needed
to
show
momentum
again
with
the
curriculum
and
I'm
leaning
towards
that
trumping.
Everything
else,
so
not
I'm,
not
saying
mp1,
won't
get
done
ever
I
think
what
I'm?
What
I
am
saying
is
that
it's
is.
B
It
cannot
be
my
singular
focus
anymore
Munoz,
as
things
come
up
where
I'm
able
to
work
on.
You
know
an
aspect
of
it
while
I'm
also
helping
to
make
sure
that
create.
Let
me
give
you
the
position.
I'm
in
right
now
is
I'm.
Thinking
like
look,
the
curriculum
is
the
way
that
people
see
this
project
growing.
B
Those
of
us
on
the
call
appreciate
the
platform
improving
in
the
in
the
experience
they're
improving,
which
is
awesome.
I,
don't
want
to
just
I,
don't
want
to
downplay
that,
but
in
terms
of
growing
the
community
I
can't
see
any
other
area
where,
where
we
could
improve
things,
and
so
until
until
that
has
legs,
it
clearly
doesn't
until
that
has
legs.
I'm
I'm
feeling
like
that
needs
to
be
my
my
my
focus,
not
my
sole
focus,
but
it
needs
to
be
a.
B
It
needs
to
be
an
equal
citizen
with
everything
else
that
I
have
going
on.
So
that's
what
I'm,
probably
gonna,
be
doing
in
the
next
little
bit
now
with
mp1,
specifically
I
originally
had
the
approach
of
okay.
Well,
this
is
a
huge
disruptive
change
and
so
what
we
should
probably
do
and
I
even
made
a
forum
post
about
this,
where
I,
where
I
declared
what
my
opinion
was
so
I'll
have
to
go
back
and
change
this,
but
I'm
pretty
much
in
a
180
on
that
I
was
originally
I
was
originally
saying.
B
B
In
retrospect,
that's
pretty
stupid,
if
I'm
being
honest,
I,
don't
know,
I'm,
not
really
sure
why
I
thought
that
that
would
work.
I,
don't
know
if
I
don't
about
you
about
if
anybody's
contributed
to
an
open-source
project
but
I
absolutely
love
it
when
people,
you
know,
don't
get
around
to
merging
my
work
for
months
after
because
they
have
some
other
thing
going
on.
You
know
that
always
works
out
great
for
the
for
the
morale
of
the
contributor.
Obviously,
that's
not
true
and
I'm,
being
I'm
being
facetious,
so
I
think
I,
think
I.
B
B
This
needs
to
get
merged
right
away,
so
we're
going
if,
for
instance,
if
we're
gonna
be
implementing,
you
know,
new
database
functionality
will
cool.
You
have
to
assume
that
as
soon
as
we
merge
that
4
MP
are
into
master
that
it's
gonna
need
to
go
into
production,
so
we're
not
gonna
have
merged
code.
That
is
somehow
not
usable.
That's
an
approach
that
I
can't
believe.
I
was
willing
to
take
earlier,
but
given
especially
the
the
change
in
focus
and
priority,
it's
certainly
not
going
to
work
so
yeah.
Hopefully
that
makes
sense
to
everybody.
B
Yeah
I'll
just
leave
it
at
that.
That's
I
just
want
to
let
everybody
know
that
it
I
feel
like
that's
something
that
needs
my
attention.
The
curriculum
specifically
and
as
a
result
of
that
focus,
but
also
as
a
result
of
a
change
in
I,
guess
common
sense
for
me:
I
changing
the
way
that
we're
doing
mp1,
it's
not
gonna,
be
a
separate
branch
anymore.
It's
gonna,
be
you
know,
well
we'll
go
as
slow
as
we
need
to
to
keep
it
to
keep
things
working
properly,
but
we
got
to
keep
things
working
properly.
D
B
Toddlers
my
toddler,
we
gave
her
a
play
kitchen
which
we
assembled
over
the
weekend
and
she
is
throwing
the
pots
and
pans
which
are
real,
stainless
steel
but
smaller,
which
is
a
great
parenting
decision.
I
highly
advise
that
you
give
your
children,
stainless
steel
pots
and
pans
for
them
to
throw
around.
A
E
C
C
C
E
E
C
D
So,
as
my
main
usage
is
a
for
teaching
computer
science
precisely
I'm
a
bit
outside
the
main
scope
of
the
curriculum,
still
stuff
like
Python
or
gates
or
whatever
can
be
the
local
levels.
I
have
some
expertise.
I
could
have
some
need,
but
but
I
still
it's
on
my
agenda
for
2020
to
be
able
to
dedicate
time
to
to
ask
them
if
they're
interested
in
like
napalm
or
other
areas
of
the
curriculum.
D
Every
day
it's
been
like,
you
know,
we
are
closer
from
2050
than
from
1990,
so
I'm
feeling
like
everything,
is
accelerating
anyway
and
I
don't
have
much
to
provide
from
my
students.
We've
been
testing
a
bit,
but
they
are
struggling
with
installation
with
the
atomic
issues
we've
stuff
like
that.
So
it's
over
the
same
issues
that
the
bootstrapping
is
with
hot.
So
for
sure.