►
From YouTube: Community Standup: 10/29/19
Description
NRELabs Community Standup, Oct 29, 2019
Attendees:
Lisa Caywood
Derick Winkworth
Stephen Kiely
A
I
just
had
one
quick
thing
for
the
agenda.
Matt
pointed
out
to
me
after
our
call
last
week
that
should
we
should
also
have
ratified
the
code
of
conduct,
given
it
that
nobody
has
had
any
comments
on
the
code
of
conduct.
I
would
assume
that
that
means
that
everybody's
fine
with
it.
So
we
should
just
ratify
that.
So
any
any
last
comments
before
we
actually
take
a
vote
on
the
code
of
conduct.
B
A
A
So
that's
been
a
long
time
coming,
but
that
is
done
and
I
think
we're
about
a
week
and
a
half
or
so
away
from
having
a
new
new,
improved,
front-end
and
user
experience,
and
so
we'll
give
a
little
bit
of
thought
to
kind
of
making
a
little
bit
noise
about
that
do
from
a
from
an
outbound
perspective.
But
yes,
though,
things
are
moving
along.
B
C
The
Steve
Steven
actually
now
that
you're
on
the
phone.
This
is
this
is
I'm
glad
you
dialed
in.
We
need
to
find
a
way
to
include.
C
Or
or
or
I
should
say,
we
should
update
the
Docs
for
people
who
are
like
I
run.
Linux
and
I
have
an
Intel
CPU,
and
that
means
that
VirtualBox
is
and
supports
vt,
and
it
and
running
a
lesson
like
I
have
a
pretty
beefy
box
and
it
stills
really
slow
way
too
slow
and
so
running.
Linux
with
an
Intel
CPU
makes
vagrant
makes
VirtualBox
now
viable
for
me.
So
we
need
there.
C
Now
in
in
I,
wrote
a
boon
to
and
and
I
believe,
there's
also
packages
in
CentOS
to
install
the
support
needed
for
KVM,
because
you
there's
actually
a
command.
You
can
run
vagrant
plug-in,
install
lipfird,
vagrant
or
whatever,
but
unfortunately
that's
broken.
Right
now
is
broken
on
every
linux
platform
and
there
and
it's
I
don't
know
how
or
when
that's
gonna
get
it
resolved.
But
if
you
go
to
the
github
repository
for
it,
it's
like
you're,
not
in
a
good.
It's
it's!
It's
broken!
C
That's
the
bottom
line
there,
but
somebody
has
made
packages
native
to
like,
like
the
unsolvable
via
more
apt,
so
that
you
don't
that
that
just
installs
it
anyway,
so
that
you
don't
have
to
worry
about
that.
That
problem
that
they're
dealing
with
and
that
allows
us
that
allow
someone
like
me
to
run
self-medicate
on
my
box
in
and
you
know,
with
reasonable
performance.
So
we
should
update
the
docs
on
how
to
how
to
install
that
support
and
then
also
update
our
vagrant
script.
D
Correct
so
there's
a
there's,
a
a
new
box
that
Olivier
pointed
me
towards
the
generic
into
1804,
which
I'm
testing
now
Olivier
responded
on
the
as
a
Liberty,
a
grant
provider
issue
or
I
guess
he
has
it
working
in
his
own
repository
and
all
he
had
to
do
was
change
the
provider
inside
the
antidote
conveyed
from
VirtualBox
to
live
Bert,
and
that
was
all
he
needed
to
get
it
working.
Yes,.
C
C
B
C
D
D
D
Having
some
so
I,
I
too,
am
having
that
she's
trying
to
get
hyper-v
to
work
so
I
rolled
back
to
vagrant
I
installed
the
newer
version
of
vagrants
in
VirtualBox.
Now
I
can't
even
get
VirtualBox
to
work
with
the
latest
version
of
vagrant.
So
I
don't
know
if
it's
my
VirtualBox
is
too
old
or
vagrant
to
new,
so
yeah
I
understand
the
issues.
C
C
C
A
C
That
are
they're
meaningless,
but
then,
when
you
do
I
so
I
was
looking
and
there's
so
there's
a
package
that
somebody
is
maintaining,
that
has
this
vagrant
livered
plug-in
and
it's
and
it's
up-to-date
and
you
can
just
do
it.
A
PD,
install
and
I
think
the
same
thing.
C
D
C
C
C
C
All
right:
well,
then,
hyper-v
is
not
gonna
work.
C
D
Yep
I
noticed
that
on
their
backlog
they
gonna
assign
a
date
to
it.
But
yes,
yeah.
C
C
Okay,
well,
if
there's
nothing
else,
then
Lisa
you're,
good
I'm.