►
From YouTube: Community Standup: 10/8/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
A
A
If
that's
too
complicated,
there's
also,
you
know
the
possibility
of
doing
something
like
matrix
or
riot,
but
or
we
can
just
take
whatever
whatever
you
want
to
do.
I
know
for
myself:
I
don't
want
to
miss
messages,
so
what
I've
done
is
I've
just
laptop.
You
see
back
here,
I've
rebuilt
it
running
Linux
and
it's
waving
to
the
laptop,
say
hello
to
the
laptop.
It's
running.
It's
running
this
back-end
server.
A
A
B
A
I'll,
do
that
I
have
posted
an
image,
an
image
creation
blog
post
by
the
way
it
was
it
was
actually
published
on
our
on
our
on
the
web
sites
on
Monday
yesterday,
I
am
putting
that
in
the
chat
as
well.
The
link
is
also
in
the
agenda.
This
is
a
for
anyone.
Who's
ever
thought
about
building
lesson.
You'll,
probably
know
that
it's
an
it's
my
belief
now
that
I've
done
a
few
stages.
A
A
This
current
process
is
going
to
change
because
in
stages
one
and
three
we're
gonna
there's
lots
of
things
that
need
to
be
automated
or
that
can
be
automated,
and
so
there's
gonna,
be
things
changing
in
those
stages
and
that'll
be
documented
in
the
mp3
proposal.
Hopefully
by
the
end
of
this
week,
which
is
something
I'll
be
I'll,
be
working
on.
Is
some
ideas
around
how
we
go
about
automating
those
things.
C
Just
on
the
same
topic,
Morris
I've
had
the
first
meeting
with
my
students
that
are
going
to
work
on
trying
to
think
about
securing
the
yams
and
so
on
so
I
guess
they
will
be
interested
in
the
process
so
and
make
sure
they
have
read
this
blog
post
and
maybe
talk
to
you
about
the
options
that
they
are
going
to
have
you
like.
Maybe
what's
I'm
thinking
about,
Qbert
or
stuff
like
that
that
involves
creating
vm's
inside
containers.
So
maybe
it's
related
and
I
guess
that
would
be
interesting
for
them.
A
A
We
have
a
question
what
if
it
says,
how
does
the
process
change
if
you're,
using
an
already
docker
image
like
CEOs
or
CRPD,
so
I
think
what'll
happen?
Is
our
Mac
can
correct
me
if
I'm
wrong
when
he,
when
he
gets
back
from
making
his
coffee
we're
thinking
that
all
of
our
images,
all
of
them
will
will
actually
be
people
will
be
running
micro?
What's
what
I
think
now
is
being
called
a
micro
VM,
which
is
which
is
a
custom
kernel
built
for
our
platform?
It's
only
compiled
with
the
drivers
needed
to
be.
A
A
So
as
convoluted
as
it
sounds,
it'll
actually
be
a
container
running
a
microvia
I'm
running
a
container
for
Sierra,
PD
or
CEOs
that
that
was
what
our
thinking
was.
If
now
that's
not
necessarily
etched
in
stone,
if
we
can
come
up
with
a
waited
to
really
secure
the
containers
that
that
would
be
great,
you
know
that's
what
Olivier
was
just
speaking
to
the
the
issue
with
that
is
right.
A
A
B
The
primary
reason
for
the
micro
VM
of
there's
a
few
but
the,
but
the
primary
reason
is
so
that
we
can
have
from
a
platform
perspective.
We
can
have
a
consistent
deployment
mechanism,
so
it
doesn't
matter
what's
running
inside
of
the
quote
image,
whatever
image,
whatever
that
means
right,
and
that
we,
that
that
consistent
format,
we
don't
have
to
care
really,
if
we've
granted
it
privileged
access
or
or
net
admin
capabilities.
B
E
B
Versus
if
you're
just
running
in
a
native
container,
so
right
now
what
we're
doing
in
order
to
facilitate
virtual
images
like
from
network
devices,
is
we
actually
have
there's
a
there's
a
flag
within
syringe
that
allows
you
to
configure
a
list
of
image
names
that
get
privileged
permissions
and
syringe?
What
it'll
do
is
it
when
it
detects
little
lessons
being
spun
up
with
those
images,
it'll
grant
those
pods
privileged
access,
and
we
on
the
production
side
of
things
like
as
we
configure
things
for
the
actual
NRI
labs
site?
B
What
we
do
is
we
just
make
sure
that
only
images
that
we
know,
because
we,
you
know,
manage
the
curriculum,
basically
that
we
know
have
a
VM
running
within
them,
so
we
can
do
that.
We
can.
We
can
do
that
safely,
but
that's
not
a
scalable
model
and-
and
obviously
even
all
of
that
doesn't
solve
any
of
the
problems
that
Derrick
brought
up
with
respect
to
how
how
difficult
it
is
to
actually
build
images
which
not
everybody
needs
to
do
not
every
lesson
needs
a
new
image,
but
when
it
does
come
up
it's
it
is.
B
A
So
yeah
again
I'll
be
making
those
I'll
be
making
this
week,
I'll
be
editing
the
mp3
doc
with
some
draft
outline
of
what
we're
thinking
it'll
get
fleshed
out
over
time
as
we
both
try
to
technically
actually
achieve.
What's
in
that
document,
and
as
we
talk
about
you
know,
what
should
the
trend
be
going
forward
in
the
future
as
a
as
a
community
and
hey.
B
A
B
Yeah
so
PR
did
I
open
for
this
62
in
Docs
in
the
docs
Rico
yep.
F
B
So
I
kind
of
did
a
bunch
of
things
with
this
PR,
but
I'll
talk
about
the
reviewer
documentation.
So
previously,
if
you
looked
at
in
fact,
if
you
look
at
the
docs
right
now,
cuz,
obviously
this
hasn't
been
merged.
If
you
look
at
the
docs
right
now,
you'll
see
this
section
that
says
contributing
to
the
NRI
labs
curriculum
and
at
the
bottom
of
that,
there's
like
a
kind
of
a
weird
awkward
paragraph
that
covers
some
of
the
things
that
reviewers
of
the
you
know.
B
People
who
were
reviewing
curriculum
PRS
should
be
on
the
lookout
for
and
it
the
way
it's
written
is
also
very
weird,
it's
kind
of
written
towards
the
contributor,
but
it
mentions
these
are
the
things
that
reviewers
will
be
looking
for.
I
wrote
that
when
it
was
pretty
much
me
and
Derek
just
reviewing
everything
which,
obviously
we
don't
want
to
do,
we
want
everybody
to
have
the
opportunity
to
review
everything,
and
so
providing
a
dedicated
doc
to
guide
folks
on
here
are
the
kind
of
things
that
we
think
are
important
to
look
for
empowers.
B
B
I
covered
I
mean
I
cover
things
like
here
are
some
of
the
things
that
we
that
we
hope
that
we
hope
to
have
automated
as
part
of
like
the
CI
process
for
the
curriculum,
for
instance,
we
run,
we
run
the
SOA,
our
CTL,
validate
tool,
I
hope,
I.
Think
it's
been
a
while
since
I
looked
at
that,
but
that's
the
intention.
B
You
know
you're
mixing
tabs
and
spaces,
which
is
horrible,
but
you
shouldn't
be
leaving
comments
like
that.
What
you
should
be
anything
you
can
automate,
you
should
automate
in
the
CI
process.
Reviews
should
not
include
comments
that
could
be
automated,
and
so
the
idea
is
that
we
automate
as
much
as
we
can
and
in
the
end,
since
this
isn't
just
Python
code.
This
is
like
a
curriculum.
B
All
of
that
stuff
that
you
should
not
then
know
reviewer
should
should
have
to
worry
about
or
comment
on.
So
that's
the
first
step,
there's
a
bunch
of
automated
checks,
a
is
the
changelog
updated
properly
again.
That
shouldn't
be
something
interviewer
has
to
keep
in
mind.
It
just
should
be
automated
and
if
you-
and
if
you
don't
do
the
thing
you're
supposed
to
do
in
the
P
R,
the
P,
the
build
should
fail.
That's
the
intention
anyway,
there's
also
much
of
stuff
that
can't
be
automated.
Obviously,
content
quality
is
up
there
Olivier.
B
We
discussed
this
with
you
last
week.
Basically,
like
you
know,
I
put
things
there
that
make
sense,
but
you
know,
as
somebody
who
has
experience
in
education,
you
I'm
gonna,
have
opinions
here
so
happy
happy.
You
know
augment
this
or
really.
Maybe
we
can
merge
this
this
guide,
because
this
isn't
meant
to
be
finished
by
any
stretch.
It's
not.
These
aren't
like
the
rules.
It's
just.
These
are
the
things
that
have
been
on
that
are,
on
my
mind,
every
time
I
do
a
review.
B
So
if
I
merge
this
and
you
have
some
thoughts,
feel
free
to
open
your
own
PR,
that's
fine,
too,
and
then
of
course,
there's
technical
things.
You
know
folks,
folks
that
know
the
antidote
platform
like
myself
and
Derek
will
have
opinions
here,
but
as
as
others,
you
know
get
up
to
speed
with
the
features
that
are
an
antidote
feel
free
to
add
to
this
as
well.
This
is
mostly
just
you
know,
do.
Are
we
taking
advantage
of
the
platform
in
its
in
its?
You
know
it
in
full.
Like
are
we?
B
Are
we
taking
advantage
of
the
platform,
because
the
reality
is
even
though
the
curriculum
and
the
platform
are
separate?
They
come
from
the
same
birthplace,
so
you
know
the
Energy
labs
curriculum
should
be
a
flagship
example
of
an
antidote
curriculum,
and
so
that's
the
idea.
Not
just
are
we
not
just
do?
Is
it
compatible?
B
Obviously,
like
I
said
sy,
our
CTL
validate
helps
with
that
to
a
large
extent,
but
other
things
that
that
can't
be
automated
like
do
we
do
you
know,
do
all
of
the
images
are
all
the
images
built
correctly
like
do
we
have
the
right
security
options
in
place,
which
is
actually
part
of
what
mp3
is
tackling,
so
there's
sort
of
a
three-fold
thing
that
that
reviewers
should
be
able
to
look
out,
for
you
know,
making
sure
all
the
automated
checks
are
working
and
passing,
of
course,
is
the
quality.
Is
the
con?
B
Is
the
quality
of
the
content
there
and
then,
of
course,
are
we
taking
advantage
from
a
technical
aspect
of
everything
underlying
it?
So
that's
the
that
was
the
original
intent
for
the
for
the
for
my
Docs
for
requests.
There
was
also
a
change
I
also
force
I
can't
remember
why,
but
for
some
reason,
I
decided
to
also
tackle
the
expansion
of
the
platform.
B
Hacking
guide,
the
the
change
I
made
was
just
a
bare
minimum,
basically
because
the
if
you
look
at
the
steps
for
for
the
antidote
web
instructions
like
how
to
spin
up
a
test
version
of
antidote
web,
it
really
sucks
like
it's
just
not
great,
and
the
reason
for
that
is.
There's
no
mock
data
for
syringe,
there's,
no
mock
syringe
data
in
an
antidote
web,
and
that
needs
to
happen
so
I'm
gonna
take
that
on.
But
there's
no
need
to
wait
for
this
PR
to
see
its
emerge.
For
that.
B
B
Is
this
is
also
something
I
was
I
was
teasing
around?
This
is
also
something
I
have
experience
with
in
some
of
my
older
software
teams
as
well.
Any
time
you
want
to
propose
like
a
really
complicated
change,
and
this
is
a
platform
thing,
this
has
nothing
to
do
with
curriculum
by
the
way.
Any
time
you
want
to
commit
any
time
you
want
to
add
something
to
the
platform
that's
pretty
complicated
or
especially,
that
needs
to
be
done
across
both
the
web
front-end,
as
well
as
syringe
or
maybe
other
components.
B
What
I'm,
proposing
and
I've
started
to
do
this
myself
and
providing
some
examples
is
to
create
a
blueprint
I,
don't,
although
the
verbage
I'm
borrowing
from
like
you,
know
effectively
my
experience
with
OpenStack,
because
this
is
how
OpenStack
works
whenever
you
want
to
create
a
new
feature,
you
create
a
blueprint,
I'm
borrowing,
the
verbiage
there,
but
I
by
no
means
mean
the
actual
specific
implementation
of
that.
You
know
as
an
example
we're
not
using
launch
pads.
B
So
that's
a
pretty
good
indicator
by
generally,
what
I
mean
is
just
a
basically
a
markdown
file
in
the
proposals,
repo,
where
you
explain
what
it
is
that
you
have
in
mind
that
way,
everybody
gets
on
the
same
page.
That
way,
there's
a
there's,
a
shared
there's,
a
there's.
There's
no
there's
one
place
to
go
for
everything,
regardless
of
whether
or
not
you
know
the
particular
feature
is
being
worked
on
in
the
web,
UI
or
the
or
syringe
or
whatever.
B
It
is
it's
sort
of
a
central
place
for
explaining
the
feature
you
have
in
mind
again.
This
is
pretty
limited
to
like
really
complicated
things.
If
there's
a
feature
that
just
requires
orchestration
across
all
of
the
different.
You
know
sub
projects
of
the
platform,
that's
kind
of
a
good
indicator
that
a
blueprint
is
needed
if
it's
just
a
simple
bug,
fix
and
syringe,
or
even
if,
like
a
new
config
flag
and
syringe,
there's
no
need
for
a
blueprint,
as
I
say
in
the
doc,
there's
not
really
a
hard
rule
on
when
it's
required.
B
B
But
again
it's
not
meant
to
be
super
formal,
there's
just
there's
a
list
of
things
there
in
the
in
this
section
there
on
my
own
PR
62
for
antidote
repo
for
the
docs,
the
covers,
basically
whether
what
are
the
things
that
we
would
want
to
see
in
a
blueprint
that
helps
make
sure
people
have
everything
they
need
to
move
forward
and
I.
Think
it'll
be
a
good
thing
for
me
as
well,
because
this
is
what
I've
been
working
on.
Lately
is
building
things
like
blueprints
really.
B
B
Sorry,
sorry
for
rambling,
like
I,
said
it's
there's
not
really
a
cohesive,
like
overarching
theme
for
this
PR
again,
it
started
as
the
reviewer
guide
and
then
I
just
kind
of
decided
to
attack
two
things
on
they're,
not
really
they're,
not
super
related,
but
the
good
news
is
that
they
also
don't
rely
on
each
other
either.
So
those
are
the
three
things
in
the
docs
repo
I've
been
doing
a
lot
of
Docs
PRS.
Lately
I've
noticed.
A
A
Yeah,
let's
not
do
that,
so
that's
what
I
haven't
we've
customized
URL,
which
is
something
we
should
have
done
a
while
back.
They
just
just
slip
their
mind.
It's
forever
reason,
I
slip
my
mind.
So
it's
it's
been
changed
and
it's
been
updated
in
the
docs
is
well
Lisa.
You
made
some
minor
changes,
I,
don't
know
if
they're
minor
they
seem
minor,
but
because
it's
only
like
one
line
change,
but
you
changed
you've
reworded
a
line
about.
A
A
E
So
I'm
in
the
process
of
going
through
and
resolving
oliviers
comments
and
otherwise
making
the
governance
talk
a
little
bit
neater
elsewhere.
In
the
news
we
are,
we
are
almost
done
with
a
massive
revision
of
the
terms
abused
right
right
now.
What's
on,
this
fight
was
actually
designed
for
something
entirely
different
and
Jennifer
specific
and
so
I've
been
working
with
legal
to
to
gently
pry
from
their
their
imagined
grasp
the.
B
E
E
But
so
else
where'd
the
news
we
finally
heard
back
from
the
software
freedom
Conservancy.
They
have
redone
their
application
and
so
I'm.
Now
in
the
process
of
filling
out
their
new
application,
at
which
point
we
will
submit
it
again
and
wait
for
them
to
review
it
and
and
give
us
the
words
though
I
imagine
this
will
probably
be
another
couple
of
months
before
we.
We
have
any
kind
of
definitive
answer
from
them,
but
I
just
want
to
give
people
a
heads
up.
That's
what
was
happening
and
then
finally,
I
think.
E
E
To
find
everything
from
the
core
energy
lab
site,
so
you
know
right
now.
If
you
go
to
enter
you
know,
lab
start
with
reliability
that
engineering
you
would
have
no
real
way
of
knowing,
for
example,
that
we
have
a
UT
there's,
there's
not
an
obvious
way
to
get
to
our
community
or
tap
platforms
and
so
forth,
and
so
on.
E
You
know
that
our
legal
team,
they're
they're,
actually
very
lovely
to
work
with.
They
are
not
super
familiar
with
open
source
and
how
that
works
and
their
entire
frame
of
reference
is.
You
know,
controlling
the
intellectual
property
of
a
vendor,
but
they're
there
they're
absolutely
willing
to
learn,
and
so
I
really
can't
knock
them.
B
Yeah
they're,
the
the
resistance
has
thus
far
been
just
from
ignorance.
Isn't
the
right
word,
but
it's
basically
like,
like
just
lack
of
experience
in
this
particular
way
of
doing
things
they
they
haven't
at
least
to
me,
which
is
different
from
some
of
the
lawyers.
I've
worked
with
it
with
other
company
companies
seemed
like
they've
been
trying
to
like
argue
they.
They
want
us
to
have
our
way.
It's
just.
They
don't
know
how
yeah.
E
A
A
C
Just
it
is
one
Liza,
sorry
for
not
responding
to
your
response
about
the
sponsorship
for
travel
of
my
students,
but
thanks
for
considering
my
request,
I'll
try
to
respond
and
another
thing
is
I've
been
just
today.
I've
been
testing
the
new
the
latest
changes
to
self-medicate
and
I
tested
the
patent.
B
Sorry
I
saw
some
of
the
issues
you
open
this
morning.
If,
if
the
self
medicate
repo
is
still
the
place
to
go,
yeah
so
yeah
I
mean,
if
that
what
we've
done
is
we've
moved
to
using
vagrant
as
the
as
the
supported
version.
Basically,
the
supported
way
of
launching
self-medicated
doesn't
mean
it's
the
only
way.
It's
just
it's
just
to
keeps
things
simple
for
us.
It's
it's
really
the
same
thing
as
before,
meaning
that
kubernetes
is
running
in
a
VM.
B
B
C
C
C
B
Yeah,
the
I
I
haven't
seen
any
problems
at
that.
That's
far
so
we'll
we'll
cross
that
bridge
when
we
come
to
it.
Regarding
your
pull
request
for
the
fix
39,
which
is
pull
request,
40
looks
like
you
opened
this
issue
and
you
say
that
machine
name
doesn't
resolve
still
works
on
public
IP.
The
VirtualBox
VM
is
there
any
yet
so
that
I
actually
did
I
actually
ran
into
the
same
thing
in
order
to
use
vagrant.
In
order
for
vagrant
to
be
able
to
change
the
host
must
file
of
the
host
machine.
C
C
The
thing
is,
I
didn't
read
the
docs,
so
maybe
the
with
me
could
be
ready
to
just
give
short
hint
instead
of
pointing
to
the
docs,
because
if
you
read
the
dogs
already
in
the
past,
maybe
you
feel
confident
and
then
you
go
to
the
the
wrong
way
or
something
like
that.
So
maybe
they
were
in
these
closer
I.
Don't.
B
That's
not
a
huge
deal
because
it'll
just
edit
the
host
inside
the
VM,
which
that
doesn't
matter
and
then,
of
course,
if
it's
not
running
in
a
VM
it'll
edit
it,
which
is
what
we
want
so
I'll,
look
into
that,
but
in
general
yeah,
while
the
vagrant
method
is
the
only
one
that
we're
going
to
like
quote
officially
support
just
because
it
keeps
things
consistent,
it
keeps
things
simple
for
us.
You
still
can
run
this.
The
the
self
medicate
file
there
bare
metal.
C
B
Well,
I'll
take
a
look
at
your
at
your
PR.
It
sounds.
It
seems
like
the
the
using
an
IP
yeah
I-I'll,
prove
I'd
comments,
but
I.
Don't
we
can't
just
use
the
IP
for
the
moment,
there's
actually
Reliance's
on
the
hostname
when
it
comes
to
ingress
is
so
I'll.
Let
you
know
it's
it's.
It's
cool
I'll
provide
comments,
and
that
way
you
have
more
details
on
where
things
are
because,
like
I
said,
things
are
moving
a
lot
more
a
lot.
B
You
know
very
quickly
right
now,
so
I'll
just
I'll,
send
you
a
bunch
of
stuff
and
that
way
we're
all.
On
the
same
page.
Okay,.
A
All
right,
we
have
help
me
check,
chat,
I,
know,
Kelvin
is
listening
in.
G
D
A
G
A
B
A
Right,
Matt
and
Lisa:
do
you
have
anything.
A
All
right,
then,
I
will
call
time
of
death
at
10:40
to
I.
Will
I
will,
as
always
and
I
feel,
I
have
strong
feelings
about
putting
this
up
on
edited
I,
just
trimmed
the
front
in
the
back.
I
will
do
that
and
post
this
up
on
to
the
YouTube
channel
and
update
the
agenda
with
the
link
to
the
to
the
recording
and
thanks
everyone
for
attending
thanks.