►
From YouTube: Community Standup: 1/21/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
Main
changes
to
the
site
and
talked
about
what
we
might
want
to
call
out
as
our
key
points
in
a
launch
blog,
we
need
to
decide
where
we
want
to
have
that
Lodge
blog
hosted,
certainly
at
a
minimum.
We
can
have
it
on
our
own
site.
We
talked
about
reaching
out
to
pack
up
odors
and
seeing
if
they
would
take
it
all
so.
A
A
All
right,
I
did
reach
out
to
excuse
me
Juniper
PR,
about
their
willingness
to
support
us
with
you
know
the
project
with
a
supporting
press
release.
They
didn't
feel
that
the
changes
to
the
site,
although
useful
for
users
would
would
constitute
a
noteworthy
or
press-worthy
bit
of
news
so
that,
while
they
will
support
you
know
from
a
social
standpoint,
you
know
amplify
may
be
anything
that
we
choose
to
do
they.
They
didn't
recommend
a
supporting
press
release
from
a
Juniper
standpoint.
A
B
Well,
do
the
the
typical
updates
on
the
few
things
on
the
agenda
item.
Let
me
figure
out
how
to
show
my
screen.
Oh
that's
forgot
what
workspace
ahead!
That's
it
there.
We
go
okay,
so
yep,
so
back
to
the
relaunch
plan,
we're
again
moving
moving
pretty
well
actually
again,
since
the
Fotolia
work
is
done,
it's
it's
kind
of
all.
Just
you
know
it's
it's
just
a
matter
of
getting
through
the
items
I
spent
yesterday.
Looking
at
this
item,
which
I'll
talk
about
here
shortly,
so
this
is,
this-
is
done.
B
I'll
talk
about
the
conclusion
to
this.
The
old.
You
know
the
benchmarking,
the
old
guacamole
approach
versus
the
new
X
term
Jas,
the
performance
is
better,
but
we
may
not
be
able
to
like
see
specifically
why
or
how.
In
our
example,
we
might
just
need
to
rely
on
other
people's
studies,
which
were
which
are
a
close
approximation,
so
I'll
get
to
that
in
a
second.
B
B
So
we
can
continue
to
unify
our
web
properties,
but
that's
definitely
not
something
we
have
to
do
before
the
launch.
It's
it's
kind
of
fine,
as
is
we'll
do
that
for,
like
maybe
the
the
phase
four
on
the
sunday
of
the
forum.
I
did
not
have
this
in
the
update,
but
I
mentioned
on
last
stand-up.
We
were
migrating
the
site
to
the
new
domain,
and
that
is
done.
So
if
you
go
to
discuss
I
actually,
if
you
go
to
community
I'd
network,
reliability
of
engineering
you'll
actually
get
redirected
to
this.
A
B
Yeah
and
it
was
a
paint,
a
pretty
painless
event.
It
turns
out
the
DNS
for
the
record,
for
this
actually
already
existed.
I
just
needed
to
tell
III
had
had
the
forethought
when
I
was
setting
up
the
new
domain
tariffs,
terraform
resources
that
I
set
up
this
subdomain
in
advance.
So
all
I
had
to
do
is
tell
discourse
about
it.
There's
a
there's
a
place
in
the
admin
panel.
You
can
just
save
changed
my
domain
and
so
I
did
and
then
I
added
redirects.
Those
are
the
two
things.
B
I
need
to
do
so,
there's
redirects
a
place
if
you
go
to
the
old
site,
you'll
still
still
go
here,
but
yeah.
The
new
one
is
discussed,
energy
lab,
Co,
much
shorter
and
hopefully
that
will
be
felt
for
a
while,
because
community
is
a
long
word
in
and
of
itself
never
mind
appending
it
to
you
know
or
girl
liability
that
engineering
anyway,
shortening
domains
is
dope.
B
B
Domains
is
dopey,
I
am
yes,
so
yeah
mostly
these
are
I,
mean
I,
don't
want
to
downplay
the
the
work
that's
left
to
do
it
be
it
all
definitely
still
needs
done
for
the
most
part.
Updating
that
you
know
updating
this,
the
site
making
making
sure
all
the
copy
is
good.
A
few
links
that
are
old
and
things
like
that
finishing
you
know.
The
new
Docs
page
is
of
course
important,
but
these
are
all
again.
These
are
all
sort
of
known
things.
I,
don't
have
any
worry
about
getting
these
done
in
the
next
few
weeks.
B
The
thing
that
I
want
to
get
done
earlier
than
that
which
leads
me
into
the
the
the
development
milestones
is
the
release
for
the
antidote
platform,
which
I
can't
believe
I
didn't
link
to
in
this.
This
is
rough
I
wish
I
had
linked
to
them,
but
the
curriculum
release,
which
is
the
big
thing
and
the
the
platform
release,
which
is
not
there.
It's
here
platform
release
is
probably
going
to
be
easy
because,
like
I
said
in
last
call
last
week's
call
and
I
still
need
to
clean
this
up.
B
The
way
that
I
want
so
I
would
expect
that
I'll
be
able
to
merge
these
two
PRS
to
fix
all
of
the
sort
of
issues
that
we've
discovered
since
deployment
I'll,
probably
be
able
to
merge
those
like
woods
in
the
next
few
days
because,
like
I
said,
I
haven't
really
touched
them
in
a
while,
and
it
seems
like
everything's
working
the
way
that
I
want
so
merging
goes
into
master
and
then
redeploying.
You
know
the
master
code
and
making
sure
that
that
works
is
good.
B
One
thing
we're
waiting
for
Bo,
Toby
and
I'll,
send
an
email
today
to
double
check
the
status
of
this,
because
it
should
be,
it
should
be
done
very
soon.
I'm
hoping
is
the
fix
for
the
bug
on
the
hamburger
menu
on
mobile.
It's
really
the
only
thing
that
we
absolutely
need
to
fix
from
a
platform
perspective
before
we
ship
it.
So
I'd
like
to
get
that
done
within
the
next
few
days.
B
Then,
of
course
the
curriculum
as
I
mentioned
is
the
other
is
the
other
one.
This
is
going
to
take
more
work,
but
we're
making
great
progress
actually
the
three
new
lessons
that
we
want
to
have
for
this
release,
since
it's
one
dot
one
dot.
Oh,
we
want
to
have
new
content
and
those
to
be
lessons
are
the
revamped
get
lessons
so
I'm
actively
I
literally
started
pushing
comments
to
this.
You
know
early
last
week
and
I've
been
I've,
been
writing
a
lot
of
content.
There.
B
That's
gonna
have
at
least
three
stages
worth
of
content
and
the
Fae
the
reason
I
hesitated
was
I'm,
trying
to
I'm
trying
to
figure
out
if
the
existing
platform
HTTP
presentation
is
sufficient
enough
to
throw
a
gitlab
endpoint
in
there.
That
shows
the
web
UI
problem.
The
problem
with
that
is
get
lab,
takes
a
long
time
to
start
up,
and
so
I'm
gonna
I'm
trying
to
invest
some
time
into
figuring
out
how
to
shorten
that.
B
If
we
could,
like
you,
know,
start
it
and
then
save
it,
save
a
copy
of
the
database
somewhere
locally
and
then
put
that
into
a
docker
container.
I,
don't
know,
but
if
worse
comes
to
worse
I'll,
just
kind
of
cut
it
off
at
that
at
that
stage
and
not
include
this
not
include
gitlab
and
we'll
add
that
stage
in
a
future
release.
That's
that's
also
very
easy
to
do
so.
Get
lessons
one.
The
other
thing
is
the
ansible
for
networking
lesson,
which
is
actually
a
something
that
we're
working
on
with
in
conjunction
with
Red
Hat.
B
That's
in
that's
it's
it's!
It's!
It's
not
working
on
the
site
in
its
current
state.
It
doesn't
do
much
because
my
goal
for
this
week
was
to
just
get
an
image
where
it
where
it's,
where
it's
running
or
it's
actually,
you
know
functioning
and
running
and
ansible
playbook,
but
that
ansible
playbook
doesn't
really
do
much
all
it
does.
Is
it
sets
them?
It
configures
the
the
login
banner
on
a
Juno's
device
which
it
does
successfully
and
I
actually
really
liked.
The
the
font
here
by
the
way
I'll
make
I'll
make
that
comment.
B
The
the
font
and
the
color
of
the
terminal,
instead
of
having
it
be
that
old,
the
the
font
that
was
like
really
you
know,
kind
of
big.
Actually,
with
the
black
background,
this
looks
a
lot
more
natural
anyway.
This
lesson
works.
You
know
it
obviously
needs
a
lot
more
content
than
the
mist,
and
you
know
it
needs
to
be
more
than
just
running
a
few
commands,
but
the
the
technical
bits
are
there.
So
that's
the
second
lesson.
The
third
lesson
is
revamping
the
rest.
B
Api's
lesson
so
I
mean
I,
haven't
really
done
much
there
yet
because
that's
been
sort
of
the
last
thing
I
wanted
to
do,
but
that'll
get
done
this
week
and
I
don't
see
it
in
the
you
know,
see
it
and
oh,
this
is
the
platform
release.
I'm
sorry
I
went
to
the
wrong
release
there
we
go
finish
resting,
yes,
listen
so
yeah,
that's
there
and
then
fixing
all
of
the
other
issues.
These
are.
These
are
easier
to
fix.
Starting.
You
know
these
two
issues
are
actually
kind
of
joined
in
the
hip.
B
Olivier
pointed
out
a
few
weeks
ago
that
it
would
be
nice
to
just
only
start.
You
know
1vq
effects
node,
because
you
don't
need
like
three
you're,
just
exploring
the
rest
api
on
of
the
VG
effects,
so
there's
no
need
to
start
three
of
them,
which
is
correct,
so
I'll
downgrade
that
in
the
in
the
rest,
deep,
you
guys
lesson
and
then
a
bunch
of
other
fixes,
like
fixing
the
fixing
the
load
function
in
the
emma
lesson,
because
it's
throwing
a
warning
right
now
things
like
that
things
that
are
pretty
easy
to
fix.
B
They
just
need
to
get
done
so
this
is.
This
is
gonna,
be
pretty
much.
My
focus
I
view
this
as
the
the
the
sort
of
the
long
tentpole.
It's
the
thing,
that's
kind
of
still
standing
out
as
the
thing
that's
going
to
take
the
most
work,
so
I'm
gonna
be
focusing
almost
entirely
on
this
until
until
it
gets
done.
B
Cool,
so
that's
the
relaunch.
Those
are
the
release
update
the
CFP
for
Au
NES
is
open
until
February
3rd
I
am
going
to
do,
I
mean
III.
Think
we
should
submit
something
for
this.
I
will
send
a
note
out
on
Twitter,
as
well
as
the
forum
and
say
hey.
Does
anybody
want
to
submit
an
entry?
Let's
talk
to
this
in
in
fin.
You
know,
I.
Think
it's
I,
don't
know
what
date
the
conference
is.
That.
B
So
so
the
sort
of
CFP
is
open
to
February
3rd
I
will
I
will
send
a
note
out
now.
I
will
submit
to
this.
If
nobody
else
does,
but
I
would
like
somebody
else
to
submit
to
it
and
I
will-
and
you
know
we'll
do
our
best
to
support
to
support
that
effort,
obviously
including
possibly
even
going
out
going
out
there.
I
know.
Juniper
has
some
presence
there,
so
it
probably
won't
be
that
hard
for
at
least
one
of
us
to
get
out
there
to
support
whoever
is
talking,
but
of
course
minimally.
B
Last
thing,
Lisa
and
I
have
been
talking
about
ways
to
you,
know,
sort
of
really
articulate
the
the
benefits
of
some
of
the
changes
that
we've
made
to
the
to
the
website.
One
of
those
is
moving
away
from
guacamole.
Guacamole
has
been
a
problem
for
a
number
of
reasons,
and
one
of
those
reasons
is
performance,
especially
on
mobile.
If
you
go,
if
you,
if
you
get
on
a
really
poor
connection,
guacamole
kinda
shows
its
ugly
side
where
it
tends
to.
B
It
tends
to
not
perform
very
well,
and
it's
really
hard
to
really
hard
to
describe
with
what
I
mean
there,
unless
you
actually
use
it
on
like
a
mobile
connection
or
app
or
internet
connection,
it
just
gets
a
little,
it
gets
really
sluggish
and
it
becomes
unnatural.
It
doesn't
feel
like
you're
typing
into
a
you
know,
a
natural
terminal.
It
feels
like
you're
typing
into
a
web
site
on
a
poor
internet
connection,
which
is
not
the
experience
we
want.
We
want
it,
we
want
it
to
be.
B
We
want
it
to
be
a
good
experience,
so
the
the
blog
post
I
have
up
here
is
linked
in
the
notes
and
it's
titled
age
to
the
people
versus
WebSockets
and
performance
comparison.
So
I
actually
did
some
work.
I
tried
to
figure
out
a
ways:
I
could
get
some
performance
figures
from
guacamole,
as
well
as
our
new
X
term.
B
Jay
s
based
a
application
for
antidote
web
I
got
some
I
mean
I
was
able
to
do
some
things
and
I
in
the
work
that
I
put
in
is
probably
gonna,
be
much
more
useful
when,
when
I
finally
get
around
to
writing
a
framework
for
testing
our
lessons,
which
is
something
I've
wanted
to
do
literally
since
we
launched
in
our
labs.
So
it's
not
wasted
effort,
but
I
decided
not
to
go
down
the
rabbit
hole
from
a
performance
perspective,
because
I
feel
that
the
the
the
numbers
shown
in
this
blog
post
are
actually
pretty
accurate.
B
The
reason
for
that
is
because
I
think
the
main
reason
we're
gonna
be
getting
better
performance
out
of
out
of
the
new
solution
is
because
we're
using
WebSockets
extra
Japs
is
definitely
a
more
modern
approach.
There's
definitely
architectural
differences
between
the
two
that
make
xterm
j/s
and
when
I
say
to
go,
but
the
real
big
reason
why
I
mean
the
first
very
first
reason
why
it's
gonna
be
a
better
performing
solution
is
because
we're
not
using
stay.
B
You
know
we're
not
using
full
HTTP
requests
for
every
keystroke
I
mean
that's
gonna,
be
that
we
would
have
seen
a
massive
performance
improvement,
even
if
we
have
stayed
with
guacamole
and
what
with
WebSockets,
because
that's
possible
on
guacamole.
The
reason
we
didn't
know
that
I
mean
the
main
reason
I
didn't
even
look
at.
That
is
because
the
docs
for
doing
that
are
not
great,
and
there
are
other
architectural
reasons
why
we
didn't
want
to
stick
with
guacamole.
So
it's
a
good
reason
we're
moving,
but
the
I
think
the
main
performance
boost
actually
is
gonna.
B
Come
from
the
fact
that
we're
changing
from
this,
you
know
old
request
per
keystroke
architecture,
which
is
really
heavy-handed
frankly
to
using
WebSockets,
which
means
it's
a
persistent
well
for
those
you
know
know
what
WebSockets
is
the
persistent
connection,
so
you're
saying
it's
a
one
commit
you
know
one
connection
for
the
entire
terminal
and
when
you
said
a
keystroke,
it
just
sends
the
small
amount
of
data
needed
to
send
that
keystroke,
not
a
full
HD
request
and
it
screwed
it
scroll
past.
All
of
the
code.
You
don't.
B
This
is
just
showing
you
how
to
how
to
replicate
the
the
test
that
they
did.
But
if
you
run,
if
you,
if
you
look
at
this
blog
post,
you
can
see
some
of
the
some
of
these
statistics,
so
requests
duration
might
be
kind
of
useful
I
mean
I
mean.
Obviously,
if
you,
if
you're
running,
you
know
something
like
socket
IO,
which
is
what
we're
running,
which
is
which
is
good
cuz.
That
makes
this
test
even
more
relevant
to
us.
That
might
be
useful
one
of
the
things
that
I
thought
was
very
useful.
B
Was
this
data
transfer
statistics
so,
if
you're
using
an
HTTP
request
it
needs,
it
needs
a
lot
more
data
than
a
simple
WebSocket
request.
So
if
you,
if
you
connect
a
WebSocket
and
you
send
a
keystroke,
the
data
you're
sending
is
like
a
seventh
or
an
eighth
of
the
size
and
again
on
a
mobile
connection
that
actually
matters
not
only
just
from
a
data
use
perspective,
but
that
transmitting
that
amount
of
data
takes
time
and
he's
gotta
transmit
eight
times
the
data
per
keystroke
you're
gonna
feel
that
it's
just
gonna
be
something
you
feel.
B
The
other
thing
is:
requests
per
second,
not
crazy,
worried
about
this,
because
we're
not
really
you
know
unless
you
can
type
like
an
absolute
champ.
You're,
not
gonna,
be
hidden
hidden,
many
things
here
again,
all
things
being
equal,
you're
you're
not
going
to
be
pushing
the
boundaries
of
either
or
HTTP
or
WebSockets.
B
The
the
main
thing
will
be
the
latency
induced
by
the
data
transfer,
the
the
amount
of
data
you're
sending
as
well
as
you
know,
a
few
other
things
so,
but
it's
clear,
though,
because
you
can
paralyze
WebSocket
connections
that
it's
that
it's
just
generally
faster
anyway,
I'll
leave
it
at
that.
This
is
I,
think
a
good,
a
good
benchmark
for,
for,
for
us
to
just
sort
of
refer
to
generally
and
say:
look
we're
changing
to
this
new
architecture.
This
company
that
runs
this
project
I,
don't
even
know
anything
about
this
product
feathers.
B
They
they
put
some
effort
into
benchmarking,
the
two
and
and
it
looks
like
they're
using
the
same
technology.
We
are
on
the
back
end,
so
I'm
pretty
comfortable,
saying
you
know
it's
gonna,
be
it's
gonna,
be
you
know
X
X
after
I.
Don't
know
it's
eight
times
faster.
You
know,
I
would
say
at
least
at
least
five.
You
know
five
times
faster
would
be
good
where.
A
B
A
B
It's
it's
good,
it's
pretty
obvious,
like
you
can
you
can
just
tell
you,
can
tell
the
difference.
I,
don't
know
if
you've
ever
done
like
VR,
but
if
you,
if
you
get
into
like
a
virtual
reality,
headset
and
like
the
computer's
not
up
to
stuff
or
something
like
that,
and
so
the
refresh
rate
is,
is
not
great
like
like
it
drops
a
few
frames
like
anybody
that
doesn't
understand,
VR
hasn't
used,
VR
would
say:
oh
my
god,
that's
not
a
huge
deal.
So
what?
If
you
drop
a
few
friends?
So
no.
B
It
actually
literally
makes
you
sick
and,
and
and
and
this
is
not
that
severe,
but
it's
the
same
kind
of
thing:
it's
a
if
I'm
describing
the
performance
difference
in
words.
It's
like
whew,
you
know,
I
mean
it's
really
hard
to
get.
Somebody
excited
about
websocket
efficiency,
but
when
you're
on
the
keyboard
and
you're
relying
on
this
to
feel
like
a
natural
experience,
it
matters
a
lot.
So
it's
it's
really
hard
to
describe
with
numbers
and
words.
It's
one
of
those
things
where
you
just
gotta
you.
You
have
to
have
seen
how
bad
it
got.