►
From YouTube: Community Standup: 10/15/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
B
B
B
A
A
B
C
D
A
B
C
E
A
Okay,
so
Matt
I
think
you
wanted
to
go
over
the
road
map
a
little
bit
in
more
detail
since
we're
we're
sort
of
celebrating
our
first
anniversary
and
looking
forward
to
the
next
year.
C
Sure
desktop,
and
can
you
see
this?
Yes,
all
right,
this
really
shouldn't
be
new,
because
I've
we've
talked
about
this
probably
ad
nauseam,
but
now
that
we
have
a
place
to
point
to
for
the
one
dollar
roadmap
I
figured
I'd
show
you
guys
just
overview
what's
involved
here.
One
thing
I
do
want
to
call
out,
because
there
has
been
a
lot
of
ideas
on
augmentations
for
for
the
platform.
This
is
the
antidote
one
dot.
Oh
sort
of
roadmap
is
not
meant
to
be
like
the
final
state
of
antidote.
C
It's
just
so
it
is
it's
a
1.0.
That's
it
there
will
be
a
to
die.
No,
there
will
be
a
one
point,
five.
So
the
reason
the
to
be
honest,
the
primary
reason
for
this
is
just
is
to
address
what
I
view
as
like
gaping
holes
in
the
platform.
So
with
respect
to
Olivier,
I
saw
your
note
on
integration
with
that,
whatever
it's
called
the
the
one
protocol
for
learning
management
systems,
yeah,
so
I
thought
about
maybe
putting
that
into
MP
one,
but
I
actually
thought
like
one
of
the
things.
C
So
the
cool
thing
about
the
cool
thing
about
a
lot
of
the
work
that's
here
is
it
is
meant
to
be
very
temporal
like
this
is
not
meant
to
stretch
on
and
and
solve
all
the
problems.
So
I
want
to
be
very
careful
about
scope
creep
because
that's
you
know,
it's
not
meant
it's
not
meant
to
address
all
the
problems
and
implement
all
the
features
there
will
be.
There
will
be
space,
in
fact,
the
it's
specifically
mp1.
The
whole
point
of
mp1
is
to
create
space
for
all
those
other
features.
C
Objective
verification
is
another.
One.
I
actually
wanted
to
do
that
a
long
time
ago
and
it
kind
of
exists
in
the
current
version
of
syringe.
But
it's
the
use
case
for
verifying
optional
objectives
is
very
event-driven
in
nature,
so
it
kind
of
makes
sense
that
we
do
the
mp1
project
first
and
then
come
back
and
circle
back
and
do
that
later.
C
So
for
that,
for
that
kind
of
stuff,
I've
been
sort
of
passively
opening,
you
know
note
PRS,
like
blueprints
for
the
for
the
for
the
scratch
scratch
directory
editor
idea
that
toad
and
I've
had
so.
These
are
all
these
are
all
things
that
that
I
I
want
to
address
after
mp1,
and
those
are
just
examples,
so
the
reason
I
bring
that
up
is
this.
Isn't
this
isn't
meant
to
be
exhaustive?
C
This
isn't
meant
to
be
like
okay,
if
we
ever
want
to
get
anything
done
with
syringe
or
antidote
web
or
whatever
like
we
got
to
get
it
in
these
projects.
That's
not
the
case.
This
is
just
this
is
just
what
I
what
I
have
viewed
you
know
basically
over
the
last
year
and
then,
of
course,
with
feedback
from
from
everybody
else.
What
I,
what
I?
C
Viewed
as
the
the
big
gaping
holes,
the
things
that
that
that
I
still
feel
make
antidote,
and
by
and
by
extension,
NRI
labs
still
in
its
proof
of
Fay's,
addressing
these
moves
us
out
of
that
phase
and
into
a
more
mature
phase
of
actual
maintainable
software.
So
that's
it
that'll
again
again,
that's
just
the
first
step,
though
that's
that's
one,
zero
that
gets
us
on
a
stable
footing.
Once
we
get
all
of
these
things
done,
we
can
say:
okay,
cool.
We
have
a.
We
have
a
good,
stable
platform.
C
C
Some
of
these
some
of
these
things
will
not
be
a
surprise
I'll.
You
know,
and
a
lot
of
these
aren't
even
decided
yet,
as
you
can
see
the
proposed
design
and
implementation
plan
for
each
of
the
four
requests.
That
means
that
those
are
still
being
worked
on.
I
will
tell
you
the
one
that
will
be
finished.
First
is
likely
to
be
MP.
One,
although
Derrick
is
working
hard
on
mp3,
so
we'll
see
we'll
see
who
will
see
who
wins.
C
Mp
two
is
actually,
to
be
honest,
that's
probably
the
easiest
to
complete,
just
because
most
of
that
work
is
being
done
by
our
the
contractor
that
we've
engaged
for
the
UX
revamp,
so
I
can
easily
sort
of
sum
up.
The
the
scope
of
what's
being
done
there
and
I
actually
should
be
I
should
have
done
that
a
long
time
ago.
Just
to
give
folks
a
heads
up
that
we're
doing
that,
I,
don't
know
that
everybody
know.
C
I
know
that
I
think
everybody
on
the
call
knows
this
just
because
we've
talked
about
it
a
lot,
but
only
everybody
like
on
the
forums,
for
instance,
knows
that
we're
working
with
a
contractor
for
that.
So
maybe
I
should
actually
complete
mp2
first
and
then
or
the
the
draft
for
that
first
and
just
say:
here's
what's
happening,
they
here's
what
the
contractors
doing.
Here's
the
contractor
not
doing
so
that
you
know
folks
can
understand
what
they
can
continue
to
work
on,
while
that
works
going
on
I.
Just
thought
of
that
just
now.
C
C
How
can
we
make
the
antidote
images
a
easier
easier
to
create
and
integrate
with
and
and
augment
while
at
the
same
time,
adding
a
nice
consistent
security
layer
using
virtualization
without
making
it
really
bloated,
which
Derek's
made
a
lot
of
headway
on
actually
he's
doing
a
lot
of
really
good
work?
There
mp4
I
I
had
I
still
have
this
year,
but,
like
I,
said,
I've
had
thoughts
lately
that
that
that
have
me
convinced
that
perhaps
this
is
not
really
a
mini
project,
because
again
it's
not
necessarily
like
a
1.0
thing.
C
It's
something
that
we
can
easily
do
in
a
separate
sort
of
just
standalone
PR,
because
it
is
all
mostly
you
know,
mostly
something
that
requires
mp1
to
be
finished
and
I
generally
don't
want
to
have
with
these
mini
projects
for
100
I
generally,
don't
want
to
have
like
a
ton
of
interdependence
on
each
other.
I
don't
want
like
I.
Don't
want
it
to
be.
You
know,
sort
of
implied
that
one
relies
on
the
other
or
even
expressly
stated
that
way.
C
C
You
know
we
wanted
to
solve
a
lot
of
the
problems
that
self-medicates
had
thus
far,
in
particular,
just
the
fact
that
you
kind
of
have
to
know
kubernetes
in
order
to
troubleshoot
it,
but
also
it
doesn't
really
help
you
build
content.
It
kind
of
understand,
of
it
kind
of
like
forces
you
to
figure
out
a
way
to
build
your
content
using
some
other
way,
usually
by
copying
and
pasting
somebody
else's
content
and
then
modifying
it,
which
is
totally
fine.
C
It's
you
know
whatever
whatever
gets
as
long
as
whatever
gets
submitted
is
doesn't
have
any
of
that
copypasta
in
it.
That's
fine,
but
that's
not
ideal,
that's
not
very
easy
to
do
so.
We
were
hoping
to
for
a
long
time.
Actually
I
was
hoping
to
build
a
wizard
into
syringe.
First,
that
allowed
you
like
basically
say
like
hey
I'd,
like
to
create
a
new
lesson,
and
then
it
go.
C
It
walks
you
through
a
bunch
of
questions
I'm
like
what
kind
of
things
you
want
to
put
in
the
title
and
the
stages
and
all
that
thinking
about
it
more.
We
may
still
do
that
in
syringe,
but
we
might
also
build
basically
a
separate
web
application,
so
not
an
it
a
web,
but
something
kind
of
like
that
that
is,
that
is
expressly
built
for
the
purpose
of
creating
lessons
in
a
visual
way.
So
drag-and-drop
topologies,
you
know,
drop
down.
You
know
quizzes
for
creating
lessons
and
all
kinds
of
stuff
like
that.
C
So
we'll
see
that
that's
probably
the
least
well
formed
of
all
these
mini
projects,
but
we'll
see
how
that
goes
and
then
finally,
the
top-level
execution
plan.
This
is
absolutely
not
final.
I
just
want
to
say
that
I
have,
in
fact,
as
soon
as
mp1
is
done
and
I'm
ready
to
start
that
work
I'll
be
coming
back
and
totally
changing
this
and
identifying
specific
mini
project
milestones
to
put
here
as
well
as
other.
These
are
sort
of
other
things
that
I
think
represented
one
dotto
release,
but
they
don't
really
warrant
a
mini
project.
C
They're
just
changes
so
those
those
are
gonna
be
mixed
in
with
each
other
and
placed
here
and
then
once
once
that,
once
those
drafts
are
more
or
less
finished,
I'm
gonna
go
back
to
the
release,
planning
and
the
antidote
platform,
and
this
process
will
be
followed
for
version
0.5
to
zero.
So
first
step
is
to
get
all
this
stuff
more
or
less
finalized,
which,
like
I,
said
I,
think
the
drafts
will
be.
C
You
know
marked
as
reviewable
one
at
one
or
more
of
the
drafts
will
be
marked
as
reviewable,
hopefully
in
the
next
few
weeks,
and
once
that's
once
those
are
all
reviewed
and
everybody
sort
of
you
know
on
the
same
page
with
what's
with
the
work
that's
going
to
take
place
there,
I'm
gonna
make
sure
these
get
at
least
then
at
least
0.5
and
0.6
get
updated.
That
way.
C
We
have
a
good
sort
of
short-term
roadmap
and
then
I'll
start
executing
per
the
release
plan
on
0
to
5
and
and
then
it
will
just
continue,
will
continue
to
march
towards
and
I
don't
know,
I,
don't
know
how
many
releases
it'll
take
right
now,
like
I
said.
That's
part
of
what
I
need
to
finish,
but
eventually
it'll
end
and
one
in
one
danau.
C
So
this
is
a
this
is
live
this
this
roadmap
is
live.
It's
again.
It's
not
final.
It's
still
is,
should
be
considered
a
living
document,
you'll
notice
that
each
MP
mini
project
also
has
a
discussion
forum.
So
if
you
want
to
talk
about
any
mini
project,
I
created
categories
for
that
in
the
forums
and
there's
obviously
there's
a
brief
summary
of
what
we
want
to
do
in
each
one.
Any
questions
about
this
I.
C
C
Wait,
that's
weird
I
need
to
clean
this
up.
Here
we
go
so
in
each
mini
project.
We
should
have
individual
milestones
and
those
milestones
should
be
composed
of
one
or
more
github
issues,
so,
as
an
example
did
I
cut,
those
I
can't
remember:
I
really
need
to
I
really
need
to
clean
this.
The
bottom
part
of
this
up
I've
been
focusing
mostly
on
the
top
part.
Let
me
see
if
I
can
find.
C
Obviously
we
can
find
the
sirens
the
issues,
because
there
is
a
few
one
day
yeah
here
we
go
so
here's
a
specific
task,
and
this
is
the
idea
I'll
have
to
go,
make
sure
this
is
the
case,
but
the
idea
is
that
this
would
have
been
linked
from
the
actual
np-1
dock,
and
this
is
a
this
is
a
specific.
This
is
a
specific
piece
of
work,
so
so,
at
the
end,
by
the
time,
MP
will
the
MP
1
dock
as
an
example,
and
we
should
do
this
for
all
of
the
MP
docks.
C
Actually,
each
each
mini
project
dock
will
have
a
design
like
here's.
How
the
final
state
will
work
once
that
p1
is
finished
and
then
it'll
have
a
work
breakdown
in
terms
of
milestones
and
each
of
those
milestones
linked
to
an
issue
like
what
I
just
said
and
those
issues
should
represent.
You
know
a
PR
Abul
worth
of
work
and
and
they'll
be
they'll,
be
contained
here.
So
the
milestones
will
be
something
will
you
know
I
in
in
serve
the
syringe
mini
project,
I
break
it
down
like
this.
You
know
mini
project.
C
You
know,
milestone
1.1,
move
state
to
external
database,
so
there's
a
there's.
This
is
actually
probably
a
pretty
big
task,
but
will
will
document
what
what's
required
there
and
then
somebody
can
come
across
and
then
and
then
that'll
be
contained
in
an
issue,
and
that
issue
will
be
linked
right
here
and
then
somebody
can
say:
okay
well,
I
I
know
a
lot
about
how
to
use
like
the
sequel,
ORM
and
go
and
I
comfortable
writing
migration
scripts.
C
So
I'm
gonna
take
on
this
particular
part
of
the
project,
and
somebody
else
can
and
a
lot
of
these
can
be
done
in
parallel
and
all
that's
part
of
what
I'll
I'll
build.
The
dock
is
understanding
what
could
be
done
in
parallel
and
what
camp,
and
so
somebody
else
can
then
be.
You
know.
Maybe
I
can
work
on
this
in
parallel
to
that,
as.
B
C
That's
fine
I
mean
if
that
ends
up
being
the
case
that
so
that's
okay
with
me,
but
what
I
want
to
do
is
I
want
to
break
down
the
work
so
that
in
the
worst
case
scenario,
if
I
do
end
up
doing
all
the
work
people
just
know
what's
going
on,
but
in
the
in
the
I.
In
the
ideal
case
scenario,
people
understand
where
they
can
contribute.
If
they're
in
there
will
be
small
tasks,
I
it
would
to
be
clear.
There
will
be.
There
will
be
things.
B
Syringe
and
key
one
because
it's
probably
more
complex
in
the
base
that
we
need
to
move
the
other
many
projects.
So
I
would
say
you
have
to
focus
on
that,
whereas
all
our
many
projects
could
be
more
depending
on
your
engine
and
then
people
come
come
can
work
in
parallel,
but
for
the
p1
I
don't
know,
maybe
someone
will
come
out
of
the
woods
and
say:
okay,
I
know
go
and
let's.
A
So
when,
when
certainly
can
you
know
which
route
happenstance,
but
if
there
are,
you
know
specific
skills,
for
example,
that
we
don't
currently
have
in
our
beauty
but
are
needed
for
a
particular
type
of
work.
We
can
go
recruiting
for
them
right
and
you
have
a
a
an
event
coming
up
in
a
couple
weeks
where
that
would
be
an
ideal
thing
to
do
so
it
might
be
worth
spending
a
little
bit
of
time
to
think
about.
A
B
F
B
Karos
or
proposals
so
I
don't
know
who's
in
charge
of
taking
the
time
to
log
you
that
or
not
intent,
but
I
feel
that
some
of
the
issues
I've
had
others
may
have.
So
you
can
be
a
showstopper
and
they
could
be
too
shy
to
ask
a
report
in
the
forums
as
well.
So
I,
don't
know
if
you
have
some
time
to
to
have
a
look.
I
lost
offend
you,
you
responded
today
or
yesterday.
Thank
you
last
night,
if
you
can
hold
it.
G
G
So
all
I'll
test
that
change
out
in
my
Windows
environment
I
want
to
see
if
I
can
flag
when
I
know
I
can
fly
when
host
a
host.
Updater
is
not
installed
until
the
users
to
make
the
host
set
is
manually,
but
I
want
to
see
if
there's
a
way
to
flag.
If
the
host
file
failed,
host,
updater
failed
to
tell
the
users
to
manually
make
the
changes
for
you
send
them
a
link
on.
C
G
B
And
also
one
of
the
things
I
experienced
in
the
last
test:
I
did
Sunday
night.
I
guess
was
a
crlf
conversion
issue.
The
notion
noticed
so
it's
the
classical
problem
when
you
use
git
on
Windows
with
some
defaults
that
will
use
standard
in
line
endings
and
when
you're
in
variant
it
causes
some
trouble.
So
I'm
not
sure
how
to
solve
that.
But
I
expect
many
people
to
experience
that
so
I
don't
know
how
to
best
address
that
probably
absorptions
but
again
maybe
I'm.
B
G
B
G
G
E
B
A
G
B
C
Yeah
I
think
Derek
Derek's
a
lot
closer
to
this
than
I
am,
but
he
I
was
I.
I
thought
he
was
gonna.
Take
a
look
at
this
last
week:
I
got
it
I
gotta.
Ask
him
he's
I!
Think
he's
still
traveling
I'll
ask
him
what
he
what
he
looked
at
if
anything
last
week,
but
if
it
works,
ok,
serial
tickle!
Excuse
me:
I
didn't
get
my
coffee
by
the
way.
I
need
to
go.
Do
that?
That's
not
obvious
anyway.
Yeah
I'll
take
a
look
at
it
as
well.
C
E
B
Besides
this
Matt,
you
proposed
a
few
days
ago,
will
you
post
it
on
the
forum
about
new
ways
to
harm
antidote
weapons
and
syringe
without
kubernetes?
Am
I
right,
yep
and
so
I
think
my
students
we
are
looking
for
that.
So
probably
they
did
test
it,
but
I
haven't
had
any
feedback,
so
it
saves
us
they
need
to
use
a
docker
push
too
hard
applying
to
self-medicate.
C
So,
to
be
clear,
this
is
not
for
any
if
you're,
if
you're,
just
working
on,
it's
meant
for
people
that
are
working
on
an
Ida
wet.
That's
like
the
that's.
The
main
use
case
run.
If
you
want
to
do
web
development
on
that
on
antidote
web
today
or
I,
guess
you
know
whatever
two
weeks
ago
previously
it
was
kind
of
impossible.
What
you
would
have
to
do
really
was
like
deploy.
You
have
to
deploy
self-medicate
really
cuz.
You
had
to
have
syringe.
C
Cuz
syringe
has
the
API
that
powers
most
of
the
things
that
take
place
in
the
web
front
end
and
then
syringe
in
turn
means
a
working
kubernetes
cluster
because
it
automatically
connects
when
it
starts,
and
if
it
fails
it
shuts
down,
so
that
basically
meant
you
needed
self-medicate
and
so
like
the
way
that
you've
made
changes
to
the
web
front-end.
Is
you
effectively?
C
You
know
change
the
manifest
that
the
manifest
for
antidote
web
inside
of
kubernetes
and
pointed
it
to
like
your
own
docker
repo
and
then,
when
you
made
changes
to
the
to
the
and
I'm
assuming
this
is
what
you
were
talking
about.
Yeah
then
you
would
have
to
then
you
would
have
to
push
you
know,
rebuild
rebuild
you
make
changes
rebuild
using
that
that
you
know
your
own
repo
push
to
that
and
then
restart
the
internet
web
pod,
so
that
you
would
see
your
changes.
C
C
What
I
did
was
more
or
less
a
stopgap
measure,
because
once
we
have
mp1
in
place
we'll
be
able
to
up
we'll
be
able
to
put
in
we'll
be
able
to
put
in
a
data
model
that
is
just
sort
of
static
for
syringe
and
then
we'll
just
simply
not
start
any
schedulers.
But
in
the
meantime,
what
I
did
was
I
created
a
third
service
I
call
it
syringe,
D
mock,
it
does
a
really
simple
thing:
it
just
starts
the
syringe
API
and
it
doesn't
try
to
do
anything
else.
C
It's
basically
just
like
syringe
D,
which
which
is
the
normal,
syringe
sort
of
scheduler
binary
process,
except
that
it
doesn't
do
most
of
the
things
that
most
of
the
things
in
that
process
does.
The
only
thing
it
does
is
it
starts
the
API
and
that's
it
and
it
offers
very
static
data.
It's
like
literally
compiled
into
the
binary
for
now
again.
This
is
gonna,
be
a
lot
easier
once
mp1
is
done,
but
for
now
basically
that's
what
you
got.
You
got
syringe
D
mock
now.
C
The
cool
thing
is
you
shouldn't
have
to
touch
that,
because
what
I
did
in
antidote
web
was
I,
also
developed
a
docker
compose
file
that
uses
that
and
then
just
simply
runs
it
alongside
a
an
antidote
web
container.
That's
built
so
the
cool
doctor
compose
allows
you
to
both
use
pre
pre
pre,
built
images
as
well
as
supporting
building
a
new
image
as
part
of
the
docker
composed
sort
of
up
state.
So
so
that's
like
then
I.
You
know
that's
that
basically
offers
a
really
nice
way
to
preview
antidote.
C
Web
changes
so
start
syringe,
D
mock
and
then
it'll
build
the
antidote
web
container.
You
know
local
on
the
file
system
and
then
start
it
and
that's
it
that's
pretty
much
all
you
need,
because
it's
again
there's
no
need
for
kubernetes.
There's
no
need,
for
you
know,
there's
no
need
for
a
VM
or
anything
like
that.
It's
just
running
in
containers.
C
So
that
said,
if
you,
if
there's
actually
not
this,
wasn't
you
guys,
but
there
was
there,
were
some
folks
that
were
confused
about
I
think
somebody
from
some
Red
Hat.
It
was
confused
that
this
was
like
for
building
lessons.
This
is
so
this
has
nothing
to
do
with.
That
was
there's
nothing
to
do
with,
like
self-medicate
self-medicates
still
the
way
to
go
for
building
lessons,
because
you
really
need
a.
You
really
need
like
a
working
version
of
all
of
this.
If
you
want
to
build
lessons,
so
this
is
just
hard.
C
So
yeah,
please
please
play
with
that.
I
mean
it.
You
see,
it
seems
like
it
works
for
me:
I
verified
with
somebody
else
that
has
yet
to
join
these
stand-ups,
but
she
she
also
is
looking
to
do
some
some
minor
web
improvements
and
seems
to
work
for
her,
but
obviously
it
was
something
I
threw
together
within
a
few
days,
so
I'm
sure
it
could
be
improved.
C
Like
I
said,
though
I
once
syringe,
mp1,
it's
done
being
able
to
being
able
to
have
like
a
fake
or
just
being
able
to
upload
any
of
being
able
to
have
any
version
of
the
platform
running
that
you
want.
That
way.
You
can,
you
know,
develop
on
it
very
easily.
That'll
be
I,
think
that
would
be
a
lot
easier.
That's
part
of
what
I
want
to
do
it
at
people,
so
you
don't
have
a
statically
compiled
lesson.
Definitions
into
the
binary
I
would
not
recommend
doing
that
long
term.
A
All
right
anything
else
we
need
to
cover
today.
D
C
They're
wearing
orange
vests,
though
so
I
assume
this
okay,
there
is
no
authentication.
This
is
an.
This
is
a
this
is
a
free
and
open
society.
There's
no
authentication
for
these
people,
they're
just
coming
up
with
drilled
holes
because
they're
wearing
vests,
nobody
asks
questions
actually
that
I
just
saw
a
video.
This
is
actually
really
funny.
C
Sorry,
this
is
a
tangent,
but
there
was
this
video
where
these
these
people
have
this
had
this
this
this
theory
that
they
that,
if
they
that,
if
they
they
could
walk
into
any
any
place
that
would
normally
you
know
that
you
normally
I'd
be
like
pay
to
get
in
like
a
movie
theater
or
a
museum,
or
something
like
that.
As
long
as
you
were
carrying
a
ladder,
no
one.