►
From YouTube: Community Standup: 3/3/2020
Description
These community standups are open to all interested in participating in the NRE Labs project. Information on the schedule for these standups as well as how to join can be found here:
https://discuss.nrelabs.io/t/about-nre-labs-weekly-standups/84
B
B
Not
in
them
and
not
in
my
household
but
hopefully
the
the
the
state
that
I
live
in
Oregon
had
their
first
case
first
official
case,
her
fee
first
confirmed
case
I'm
sure
there's
many
more
that
are
spreading.
The
first
confirmed
case
I,
don't
know
week
ago,
and
it
was
in
a
neighborhood.
That's
like
five
minutes
from
me.
So
we'll
see
see
what
happens.
We've
got
they've
got
it.
We've
got
like
a
few
weeks
of
food
and
water,
just
in
case
of
any
like
courts
in
ourselves.
B
Is
yeah
yeah
yeah,
it's
one
of
those
things
where
it's
like
you
know,
I'm
I'm
gonna
do
everything
I
can
but
I'm,
not
I'm,
not
gonna,
stress
out
about
it.
I'm
not
gonna
make
it
like.
You
don't
mean
it
is
what
it
is
you
just
do
you
do
the
you
do
the
stuff
that
you
have
control
over
and
then
you
try
to
you.
Try
to
live
with.
Whatever
happens.
A
A
B
B
A
B
C
A
B
Okay,
so
let's
see
you
let's
go
to
the
agenda,
fix
and
post
stats
spreadsheet.
Let
me
do
that.
First,
that's
easy!
B
Oop,
okay,
sir,
this
is
the
nra
labs,
weekly
stats.
We
put
the
spreadsheet
together
a
long
time
ago
for
packet,
pushers,
originally,
but
we've
been
sort
of
adding
people
to
it
over
time.
It's
basically
an
export
of
the
day
that
were
already
collecting
an
influx
DB
for
lesson
usage.
So
it's
a
way
of
gaining
access
to
that
data.
Without
having
to
worry
about.
B
You
know,
influx
TB
queries,
I've
still,
I'd
still
like
to
get
to
a
point
where
we
can
public
publicly
allow
people
to
read
our
raw
influx
TB
data,
which
would
make
this
kind
of
not
necessary,
but
then
they
would
also
make
you
have
to
know
how
to
do
that.
So
this
is
fine.
For
now
the
the
data
we
started.
Collecting
this
data,
or
at
least
exporting
into
the
spreadsheet
back
in
April
of
2019,
probably
have
even
more
data
in
influx
TB
that
we
could
add
to
as
well.
B
But
this
is
fine
for
now
and
you
can
see
I
remedied
the
last
the
last
week
last
week
we
showed
this
I
was.
There
was
an
issue
where
I
only
got
up
to
November
and
then
there
was
a
huge
gap
because
apparently
the
IAM,
the
the
apparently
the
Google
sheets,
don't
add.
They
doesn't
add.
Ematic
automatically
add
columns
when
you
try
to
add
data
via
their
API,
which
is
kind
of
weird
I.
Don't
really
know
why
that's
the
case
but
whatever
so.
B
Basically,
the
the
data
was
still
in
our
in
our
database
in
our
TS
DB,
but
it
wasn't
being
exported
to
this
spreadsheet
because
it
didn't
have
room,
apparently
literally
so
I
fixed
that
and
then
I
went
back
and
I
added
I
went
back
and
I
reek.
We
read
those
weeks
and
added
them
to
this
spreadsheet,
so
we
have
all
the
way
through
from
April,
and
you
can
see
November.
B
This
is
about
where
it
stopped
so
I
added
everything
after
this
myself
just
last
night
up
through
up
through
to
three,
which
is
where
I
found
the
problem
in
it
and
fixed
it.
So
it
was
automatically
being
at
it
again.
So
I
took
all
on
that
data
and
I
combined
it
together
and
now
we
have
the
full
data
set
from
April
to
today,
so
that
exists,
I,
threw
together
a
few
graphs.
Just
for
funsies,
as
you
can
imagine.
B
The
basically
from
here
until
about
here
is
on
the
old
site,
which
had
the
old
lesson
catalogue
which
had
more
or
less
a
static
order.
I
don't
know
if
it
was
alphabetical
or
what,
but
the
introduction
TEM
will
file
Essen
one
pretty
much
every
day,
but
now
it's
a
crapshoot.
Now
it's
totally
randomized
you
can
see.
Ansible
is
pretty
dominant,
which
is
expected,
but
then
you
can
see
a
little
little
races
I'd
like
to
drill
into
this.
B
Once
we
have
a
few
more
weeks
of
data
to
gather,
but
you
can
see
that
there
is
no
real,
clear,
necessarily
second
or
third
or
fourth
place,
not
all
the
time
there.
There
are
sort
of
swaps
which
is
kind
of
which
is
kind
of
fun
and
then
and
then
totals
we
have
totals
for
for
for
that
period
of
time.
So
all
that's
fixed.
B
The
one
thing
that's
not
fixed
is
actually
sharing
this
and
I
wanted
to
ask
if
this
was
the
way
that
we
wanted
to
make
this
data
available,
because
if
so,
then
we
might
want
to
consider
moving
to
moving
this
spreadsheet
elsewhere,
such
as
into
an
energy
labs,
Google
Drive
right
now,
it's
in
a
Juniper,
Google
Drive,
it's
just
where
we
created
it.
So
as
a
result,
we
can't
share
this
with
with
everybody.
What
we
would
have
to
do
is
if
somebody
wanted
to
view
it,
we
can
add
it.
B
B
It
would
be
nice
if
we
could
post
it
publicly
and
have
it
just
publicly
readable,
so
I
don't
think
that's
possible
if
we
keep
it
within
the
Google
Drive
that
it's
at,
so
the
question
then
becomes
are
we
are
we
still
sold
on
creating
a
Google
Drive
from
the
NRI
Labs
account
and
then
moving
this
into
that?
Or
did
we
want
to
take
the
opportunity
to
figure
out
even
a
better
way
to
share
this?
Is
this?
Is
this
a
is
this
a
good
way
to
share
this
data.
C
C
B
A
B
B
I'll
fix
that
later
we
do
have
Griffin
on
dashboards
for
everything
and
actually
early
on
very
early
on
in
in
NRE
labs.
What
we
did
was
we
had
a
stats
page
baked
into
antidote
web
with
with
I
you
can
you
can
actually
embed
these
these
graphs
as
iframes
into
your
page,
and
we
did
that
and
the
problem
with
that
was
that
you
know
any
pretty
much
anytime.
We
changed
the
layout
or
anything
like
that.
B
Well,
now
that,
now
that
we
now
that
we
have
a
you-
know
a
sort
of
a
main
site
that
doesn't
follow
that
cadence
we
can,
we
can
update
kind
of
whatever
we
want,
that
kind
of
reopens
the
possibility
for
just
using
her
phone
and
directly
again
and-
and
we
can
make
I
mean
I
I,
don't
know
how
familiar
you
are
with
with
Griffin
ELISA,
but
you
can
make
all
kinds
of
different
this
we're
not
limited
just
to
what
I've
created
here.
Girl
fauna
is
a
full-on
visualization
tool.
B
So
if
there's
a
visualization,
we
think
is
necessary
for
the
site.
We
could
just
create
it
even
in
a
separate
dashboard
like
we
can
keep
this
dashboard
as
useful
to
like
me
or
other
people
that
are
running
the
site,
but
we
can
create
a
new
dashboard.
That's
explicitly
used
for
sharing
data
on
the
website.
D
A
B
B
C
C
C
B
Okay,
so
curriculum
the
energy
left
curriculum
version
101
that
one
went
out
yesterday.
That
is
pretty
pretty
minor
release,
though
it's
just
a
new
section
on
its
new
stage
on
the
get
lesson.
So
that's
a
for
the
schedule
that
that
this
is
sort
of
like
we
had
a.
We
had
a
three
week
gap
in
between
the
relaunch
and
this
next
version,
because
I
wanted
to
start
on
the
top
of
the
top
of
the
month
and
then
do
one
in
the
middle
of
the
month.
B
So
this
is
sort
of
getting
officially
getting
us
onto
that
two-week
cadence
so
that
that's
pretty
cool
and
I'm
I'm
I'm
eager
to
get
in
to
just
keep
going
on
this
cadence
doing
doing
releases
every
two
weeks,
even
even
though
they're
very
minor
I
think
that's
good.
Okay.
So
that's
out,
oh
the
labs
in
latte
video,
I
recorded
and
edited
yesterday.
That's
also
going
out
probably
I,
can't
remember
if
I
said
820
or
8:30,
but
it's
gonna.
It's
literally
gonna
get
published.
Probably
while
we're
on
this
call.
B
B
B
So
antidote
D
is
this
server
for
running
this.
You
can,
you
can
run
it
just
using
that
command
and
then
you
pass
that
a
config
file
I've
moved
away
from
environment
variables,
because
I
was
tired
of
sort
of
environment
variable
creep,
so
I
put
everything
in
the
ml
file
and
it's
a
lot
nicer
now.
The
other
thing
is
the
the
the
the
way
that
the
way
that
answer
note
handles
data
now,
the
way
that
it
handles
its
own
state
is
greatly
simplified,
but
also
centralized.
B
So
there's
only
one.
There's
now
one
place
to
go
inside
of
antidote
to
know
what
you
know,
what
states
are
certain
things
are
at
seams.
That
seems
like
it's
fairly,
straightforward
and
expected,
but
the
way
it
grew
sort
of
organically
it
actually
meant
that
that
the
API
server
had
some
of
the
state
and
the
scheduler
had
other
pieces
of
the
state,
and
some
state
was
elsewhere
as
just
really
bad.
B
B
So
if
you
look
at,
for
instance,
the
config
that
I
mentioned
it's
a
text
file
now,
instead
of
an
environment
variable,
you
can
see
that
there
is
a
field
called
enabled
services,
and
so
we
can
actually
disable
the
scheduler
so
that
what
that
means
is
only
the
API
is
running
and
the
scheduler
for
actually
working
with
kubernetes
is
not
running
at
all
and
that's
okay,
because
that's
literally
how
it
was
built
previously,
this
was
not
possible
now
you're,
asking
probably.
Why
would
I
want
to
do
this?
B
Well,
imagine
you're
working
on
the
web
UI
and
you
would
like
to,
and
you
would
like
to
make
some
changes
well
previously.
The
way
that
we
made,
that
possible
is
through
something
called
syringe,
D
mock,
because
that
provided
a
fake
API
for
you
to
do
that
on
top
of
and
that's
necessary,
because
you
don't
want
to
have
a
full-blown
kubernetes
cluster.
If
you
just
want
to
make
some
web
changes
right,
you
just
need,
if
usually
to
fake,
fake
API
with
some
data.
That's
all
you
need.
My
problem
was
yes,
go
ahead:
Olivia
yeah,.
A
B
Yep,
it's
no
probably
not
ever
I.
That
was
one
of
the
things
in
mp1
that
I
said:
I
was
gonna
explore,
but
I've
kind
of
decided
not
to
do
that,
just
because
it
doesn't
seem
necessary,
there's
stuff
in
terms
of
the
the
way
that
they're
the
the
way
that
they're
modularized
so
in
terms
of
reasoning
about
them
that
that
definitely
has
been
accomplished,
but
I
I
see
no
evidence
to
suggest
that
we
absolutely
need
to
break
them
out
into
separate
processes
today.
B
Now
the
good
news
is
all
of
the
work
that
I'm
that
I'm
doing
now
makes
that
still
very
possible
and
definitely
easier
than
it
would
have
been
before.
So
it's
something
we
can
still
consider
doing,
but
for
now
I
think
it's
I
think
it's
good
to
keep
everything
in
one
one
application.
It
keeps
things
a
lot
simpler,
okay,
but
what
you
can
do
is
you
can
just
in
the
in
the
in
the
startup
of
syringe
D.
B
B
Basically,
it
was
a
way
for
me
to
bake
in
a
buncha
gamal
files
into
syringe
for
the
purposes
of
showing
a
you
know,
sample
dataset,
that's
not
great,
because
that
means
that
if
you
wanted
to
change
that
data
you'd
have
to
recompile,
syringe
and
you'd
have
to
know
how
it
works
in
this
model
in
the
antidote
core.
Instead,
what
you
can
do
is
you
can
start
the
is.
You
can
start
syringe,
D
with
just
the
API
service
running
and
then
using
the
tool,
an
T
CTL,
which
is
a
tool
that's
explicitly
used
for
basic?
B
It's
like
an
admin
tool.
It's
not
meant
for
you
for
regular
users.
It's
just
a
companion
tool
for
antidote
that
allows
you
to
manipulate
and
view
state,
and
one
of
the
commands
is
live
lessons.
So
you
can
say,
look
I
want
to
see
the
list
of
live
lessons
that
are
present
within
the
server
and
you
can
see
there
are
none,
because
there
are
no
lessons
started,
but
we
can
also
create
our
own
live
lessons
State
now.
This
is
not
obviously
very.
This
isn't
something
that
you'd
want
to
do
in.
B
B
A
B
So
that
I'm,
what
I'm
trying
to
do
is
I'm
trying
to
give
that
treatment
to
everything.
So
it's
so
that
it
so
that
it's
not
so
that
it
so
that
nothing
is
is
baked
in.
It's
all,
basically
just
exposed
via
this
tool
and
yeah
I
live
lessons
that
the
the
canonical
one,
because
that's
what
gets
you
the
ability
to
make
to
sort
of
test
things,
but
I'm
sure
there
are
others
so
yeah
I'm
gonna,
try
to
I'm
gonna.
Try
to
abate
I've
been
trying
to
make
that
in
across
the
board.
B
I've
been
I
mean
the
the
way
that
this
massive,
this
change
has
turned
into
effectively
a
top-to-bottom
rewrite,
but
the
way
I
started
was
wanting
to
rethink
the
way
that
antidote
handled,
State
and
not
being
able
to
do
this
was
or
yeah.
One
of
the
byproducts
are.
The
way
that
we
were
handling
state
before
was
meant
that
we
couldn't
really
do
stuff
like
this,
but
now
we
can
so
yeah.
E
B
Is
my
this
is
basically
my
current
plan
for
replacing
what
we
currently
have
in
syringe
D
mock
and
it
seems
like
it
works
pretty
well,
because
you
can
query
it
via
the
API
and
it
shows
up
and
it
it
doesn't
change
cuz.
The
scheduler
is
not
running
so
this
state
won't
change,
there's
nothing
acting
on
it
right.
So
there's
no!
There's
no
process,
that's
running
within
the
code
that
that
you
know,
updates
these
this
status
or
runs
health
checks
or
calls
kubernetes.
B
Did
it
just
stays
this
way,
because
because
the
API
doesn't
make
those
changes,
it's
the
scheduler
is
not
running.
This
data
is
just
gonna
stay,
the
way
that
it
is
but
again,
if
you're,
just
making
web
UI
changes
and
tests.
That's
that's
actually,
okay,
so
anyway,
more
on
that
later,
I
just
wanted
to
give
you
a
preview
that
that's
some
now
that
the
curriculum
release
is
done
for
today.
B
A
B
A
It
so
I
just
wanted
to
give
you
a
quick
update
on
my
students,
work
so
I,
don't
think
I
attended
the
meeting
since
the
previous
projects.
We
are
delivered.
Actually
they
didn't
deliver
much.
But
if
you
remember,
I
had
two
students
working
on
integration
of
antidote
with
learning
management
systems
through
LTI,
oh
yeah,
so
they
had
to
to
to
tweak,
send
him
out
to
try
and
add
an
API
for.
A
B
Another
part
of
MP,
one
that
I
did
do
was
was
integrating
with
Nats,
even
though
we're
not
separate
processes,
there's
still
a
lot
of
value
in
having
a
you
know,
formalized
pub/sub
system.
So
if
you
can
imagine
those
three
services
that
I
showed
you
in
the
config
which
which
was
stats,
API
and
scheduler,
there
could
be
a
fourth
one
called
you
know,
LTI
export
or
something
like
that,
and
its
job
basically
is
just
to
watch
Nats
for
messages
and
export
those
messages
as
LTI
packets.
You
know
effectively
so.
B
A
B
It
should
it
should
be
the
same.
I
mean
the
the
only
difference
would
be
how
that
code
is
executed,
how
that
code
is
actually
triggered,
but
the
way
that
it
calls
out
to
another
API
will
almost
certainly
not
be
impacted.
I
would
expect
it's
just
a
matter
of
how
it's
called,
but
yeah
I
mean.
Definitely
let
me
know
when
you
got
more
on
that,
because
I
think
in
the
new
architecture,
some
of
that
might
even
be
a
little
easier
in.
A
Any
case
I'm
still
interested
in
testing
antidote
in
the
real
news
case
in
our
University
and
I
can
imagine
that
at
some
point
in
time
we
would
need
to
identify
users
to
kind
of
save
their
work
or
retrieve
some
lab
results
that
could
be
sent
to
the
office
or
something
like
that.
So
we
need
some
kind
of
integration
in
any
case,
but
only
post,
one,
the
two
or
close
to
one
or
two
and
I-
can
figure
if
I'm
able
to
dedicate
much
effort,
and
so
there
was
another
project.
D
A
A
B
B
A
What
we're
investigating
is
a
bit
of
the
larger
project
closer.
It
keeps
cold
eclipse
a
che,
so
it
keeps
a
chair
is
a
basically
a
way
to
provide
eclipse
for
developer
teams,
/
communities,
so
cool,
hey
guys,
just
web
edit,
all
the
web
ID.
So
what
I'm
trying
to
understand
is
I
did
value
of
a
clip
to
show
you
how
they
manage
things
like
workspaces,
where
the
rapper
will
save
her
files
or
to-do
lists
or
stuff
like
that,
which
would
give
a
hint
on
how
maybe
we
could
integrate.
B
Yeah
yeah
I,
don't
know
anything
about
the
Shay
project,
so
I
did
I
would
mostly
be
interested
in
seeing
how
how
they
do
what
they
do
and
and
if
they're,
if
it's
even
compatible
with
the
way
we're
doing
stuff,
because
it
sounds
like
it
sounds
like
there's
a
there's,
a
certain
matter,
a
certain
manner
of
persistence
involved
there
and,
as
you
know,
energy
labs
is
not
very
persistent.
My
design
right.
We
don't
want
to
necessarily
keep
everything
around
so
so
we'll
see
yeah
happy
to
happy
to
hear
about
that.
I
would
love
to
hear
more.
A
A
B
B
A
B
That
that's
understood,
that's
understood.
I
I
should
do
that.
That's
totally
fine
I'm
I'm
happy
to
update
it
accordingly
and
it's
been
on
my
list.
I
just
haven't
had
time
to
get
to
it.
So
that's
fine,
keeping
keeping
it
up
to
date
with
the
with
the
latest
platform
and
and
whatnot
is,
is
totally
fine.
That's
that's
it's
not
a
huge
deal.
The
problem
is,
the
the
problem
is
is
is
when
self
medicate
becomes
literally
the
only
way
people
have
to
preview
their
content.
B
If
it's
their
only
option,
then
that's
a
problem,
so
the
the
model
that
I
really
would
like
to
get
to
is
hey
self-medicates
out
there,
and
you
could
use
it
for
this.
If
you
feel
like
that's
what
you
want,
you
want
a
local
preview.
You
want
this,
you
know
you
want
the
the
unique
advantages
of
having
this
stuff
running
locally.
B
Fine
self
medicate
will
stay
around
for
that
purpose,
but
in
terms
of
we
get
we
just
get
so
many
people
that
are
just
look
I
just
want
to
add
my
script,
to
the
curriculum,
how
it
was
the
easiest
way
to
do
that.
You
know
what
I
mean
and
the
answer
cannot
be:
go,
download
self,
medicate
and
struggle
through
all
those
hypervisor
issues
and
tough
luck,
because
that's
your
only
option,
we
don't
have
anything
else
for
you,
like
that's
painful,
and
it's
actually
been
pretty
bad
for
people
that
are
that
are
contributing
to
the
curriculum.
B
I
mean
we.
We
had
a
number
of
people
contributing
to
the
curriculum
early
on
that
were
savvy
enough
to
deal
with
it,
and
so
we
we
thought
ok,
cool.
This
is
this
is
working,
but
the
problem
is
I.
Think
like
90%
of
the
people
that
really
want
to
contribute
to
the
curriculum.
Aren't.
Actually
you
know
necessarily
automation,
experts,
they're,
not
they're,
not
vagrant
experts,
they
don't.
E
B
E
B
Know
I
mean
like
he,
you
know
he's
not
in
it
he's
not
inexperienced
with
this
stuff,
if
he's
having
issues
with
vagrant
and
and
libvirt,
and
all
that
stuff
and-
and
you
know
what
I
mean,
and
he
knows
you
know
how
all
that
works,
but
he's
still
having
issues
and
struggling
through
it.
That's
that's
a
problem.
That's
a
problem
that
needs
to
get
fixed
so
anyway,
I'm
not
I,
have
no
plans
to
deprecate
self-medicate
at
all.
A
Work
in
all
cases
like
all
hyper
visuals
or
how
old
OS
is,
but
at
least
one
where
we
have
the
ingress
working.
We
have
more
or
less
most
of
the
images
working
and
then
we
can
have
an
official
branches
or
alternative
scripting
start
startup
scripts,
but
at
least
I
mean
I'm
really
presumed
about
the
new
web
SSH
to
invest
changes
needed
and
stuff.
So
it's
probably
better
if
you,
if
you
do
the
work
and
then
we
can
try
and
support
lipfird
like
that,
yeah.
B
Yeah
I
think
I
think
the
I
think
the
the
name
of
the
game
here
will
be
stability,
getting
self
medicate
to
a
place
where
we
really
don't
change
it.
That
much
because
there's
not
a
need
to
not
a
need
to
I
think
it's
totally
fine
to
not
try
to
support
all
the
things.
Let's
just
pick,
let's
pick
it.
Let's
pick
an
approach
that
works
for
most
folks.
Keep
it
simple
and
say:
look
this
is
this
is
out
there.
B
If
you
want
to
use
it,
you
got
to
use
XYZ
kind
of
stuff,
I
think
I,
think
not
forcing
everybody
to
use
it
for
curriculum
development
will
help
with
that
too.
Because
then,
then
it's
it's
not
a
thing
where
it's
like
you,
you,
you
know,
you're,
not
we're,
not
in
a
situation
where
we
have
to
point
everybody
to
the
to
the
one
tool
and
then
therefore
we
have
to
make
that
tool
work
for
everybody.
If
we're
not
pointing
everybody
to
the
tool
to
begin
with,
then
we
don't
really
have
to
make
it
work
for
everybody.
B
We
kind
of
just
have
to
make
it
work,
for
you
know,
at
least
you
know.
Generally,
people
that
are
that
are
running
sensible
stuff,
and
then
we
can
just
say:
look
you
know
this
is
this
is
out
there?
If
you
want
this
as
an
option,
you
got
to
use
the
hypervisor.
We
support
that
kind
of
thing.
Yeah
and
I
think
that'll
be
better
for
everybody,
not
just
not
just
the
people
that
use
it
because
then
again
it'll
be
stable
and
we
won't
have
to
worry
about
it
being
broken.
B
So
anyway,
I
all
of
that
said,
I
I
still
I
still
will
update
it
to
the
latest
platform
and
updating
it
so
that
you
know
guacamole
is
not
running
inside
of
it,
and
anything
I
do
have
that
actually
in
a
PR,
so
I
just
I
need
to
finish
that
PR
and
merge
it,
and
that
way
everybody
can
use
it.
So
I
will
still
do
that.
I'm
committed
to
that.
Okay.