►
From YouTube: wasmCloud Community Meeting - 8 March 2023
Description
Welcome to the wasmCloud community! Tune in live where we discuss the latest developments in the wasmCloud ecosystem, WebAssembly standards, and break out sweet demos.
Agendas for wasmCloud community meetings can be found at: https://wasmcloud.com/community
A
Never
mind
yep,
we
are
we're,
recording
it
for
the
for
the
regulars,
hello,
everybody
Welcome
to
the
wasm
cloud,
Wednesday
Community
stream
for
March
8th.
We
have
a
pretty
fun
agenda
for
you
today,
so
let
me
go
ahead
and
share
it
and
then
we'll
go
ahead
and
get
started.
So
taking
a
look
at
the
I
had
the
wrong
one,
taking
a
look
at
what
we
have
on
Deck
today.
A
Our
first
thing
is
actually
going
to
be
a
demo
and
a
little
bit
of
a
code,
slash
right
architecture,
overview
from
Taylor
I'm,
going
to
be
going
through
some
of
the
wasmcloud
application,
deployment
manager
or
wadham
the
rust
implementation,
processing
events
and
commands.
A
Then
we're
going
to
go
into
again
some
of
the
work
that
Taylor's
been
putting
together
around
some
GitHub
projects
in
the
open
source
organization
just
want
to
make
sure
that
we
are
keeping
all
those
tasks
organized
and
it's
it's
open
for
everybody
to
go
and
look
at
see
what
we're
working
on
and
what's
on
the
roadmap
and
then
gonna,
throw
it
over
to
Roman.
Talking
about
the
implementation
he's
been
working
on
for
a
wasm
cloud
host,
so
I
won't
blabber
any
longer
about
the
agenda.
I'd
rather
just
get
into
it.
B
Sweet,
let's
see
if
I've
Got,
The
Power,
oh
yeah,
now
Brooks
just
gave
me
the
power
okay.
Let
me
go
ahead
and
show
you
I'm
actually
going
to
share
I'm
going
to
share
my
whole
screen.
I'm,
sorry
for
the
quick,
Infinity
stuff,
I
am
on
just
laptop
today,
so
let's
go
and
share
and
we
have
the
wonderful
thing
of
Woodham.
So
what
I'm
going
to
go
ahead
and
demo?
What
we
put
together
is
Kevin
when
I
when
I
first
put
this
RFC
suggested.
B
We
try
out
an
architecture
here
where
it
looks
like
this
I'm
going
to
eventually
put
together
a
whole
diagram
of
how
this
is
all
working.
Once
we've
finished
up
some
of
the
other
pieces.
But
what
happens
is
we're
thinking?
How
can
we
spin
up
multiple
anything
that
can
work
from
one
to
any
number
of
with
damn
processes?
B
So
what
we
decided
to
do
was
a
streaming
architecture
and
we
put
that
all
together
where
it
comes,
and
it
says:
okay,
I
have
a
bunch
of
events
coming
in
being
read
into
a
Nat
stream,
and
then
we
have
processes
that
read
them
up
one
at
a
time,
depending
on
the
lattice
that
they're
coming
from
and
then
same
thing
with
commands,
it
emits
commands
and
those
those
commands
are
handled
one
at
a
time,
so
I'm
actually
going
to
go
ahead
and
show
how
this
all
works.
B
It's
pretty
awesome
so
right
now,
I
have
a
Watson,
Cloud
host
running
and
I'm.
Sorry
I'm,
going
to
close
those
videos,
I
have
a
awesome,
Cloud
host
running
and
I'm
going
to
go
ahead
and
create
two
different
instances
of
what
I
am
running.
So
this
one
is
just
going
to
be
running
with
a
host
idea.
First,
so
we
know
where
it's
coming
from,
and
this
is
just
a
proof
of
concept:
it's
not
doing
any
actual
work
right
now,
oops.
B
This
is
what
happens
when
you
get
a
live
change
on
your
branch.
Let
me
I'll
just
get
stash
I'm
I
is
smart.
I
is
smart!
Developer.
B
A
I
think
I
think
this
one
might
have
actually
been.
My
bad
I
tried
to
be.
B
A
little
yeah.
B
You
just
change
this
right
and
you're
like
I'll
blame
you
Brooks
anyway.
So
now,
I'm
gonna
push
change
to
that.
Okay,
so
that's
gonna
go
ahead
and
start
there,
and
so
it's
giving
a
first
and
then
I'm
gonna
go
ahead
and
start
this
one
with
the
idea
of
second
and
I'm
tracing
like
everything
that's
going
on.
So
we
see
exactly
which
topic
everything's
coming
on
and
I'll
go
ahead
and
I'm
just
going
to
start
an
actor
here.
Oh
it's
not
file,
I'm
gonna
go
ahead
and
start
the
echoactor
foreign.
B
And
we've
submitted
that,
and
so,
if
we
come
over
here,
we'll
see
in
the
logs
a
couple
things
happen.
So
first
off
we
got
probably
over
here.
First,
we
got
like
a
start,
a
start
actor
event
that
happened.
So
we
can
see
it
said,
handle
received
event
after
started
and
then
it
actually
handles
the
work
itself.
B
We
see
a
like
a
start:
actor
command,
that's
coming
from
first
and
then
over
here
we
see
that
there
were
some
other
commands
that
were
sent
through
and
it
sent
out
another
command.
So
the
work's
true,
but
to
make
it
look
really
cool
I'm,
going
to
go
ahead
and
add
some
space
here,
so
we
can
see
where
the
the
change
happened:
yay
for
terminal
demos
and
I'm
going
to
start
10
actors,
so
we're
going
to
see
like
basically
nine
more
active
started.
B
Events,
that's
going
to
pass
across
this
and
you'll
see
that
we
didn't
there's,
definitely
not
nine
events
here.
It
got
split
in
between
these.
These
two
things
right
here,
but
you'll
also
start
to
see
that
once
once
it
started
working
we'll
find
one.
Sometimes
it
takes
a
second
to
find
one,
but
essentially
we're
going
to
find
one
where
it
says
like
which
idea
it
came
from,
and
oh
right
here
perfect.
B
So
essentially
we
have
it
set
up
so
it'll
completely
lock,
and
this
adds
this
adds
up
to
some
really
cool
features,
because
if
I
come
over
here
and
I,
I'm
gonna
go
ahead
and
kill
well,
damn
I
can
come
back
here
and
say
you
know:
I'm
gonna
say
zero,
like
I'm,
just
going
to
scale
down
to
zero
I'm,
basically
getting
rid
of
it.
So
now,
like
wadam
was
dead.
B
Let's
say
it
had
died
for
some
reason
and
I
come
back
here
and
I
started
back
up
and
you're
actually
going
to
see
bam
a
whole
bunch
of
start
actor
commands
like
stop
actor.
Things
come
through,
as
the
events
come
through,
so
you'll
see
like
handling
received
event
after
stopped.
You'll
see
a
whole
bunch
of
them
come
through
because
it
stayed
in
the
Stream
and
got
persisted
and
could
re-re-picked
up
the
event
so
anyway,
that
is
currently
where
they
am
and
where
it's
at
so
just
wanted
to
share
them.
Any
questions.
B
Okay,
that's
fine!
So
anyway,
that
is
the
current
sass
over
Dan
we
started
some
real
work
on
it
really
awesome.
So
we've
we
started
the
work
on
that
I
just
wanted
to
show
people
we're
trying
to
give
a
little
bit
of
a
status
update
every
week
that
lends
itself
real
nice
into
bleed
over
into
the
next
topic,
which
is
something
new
we're
trying
with
our
sorry
our
projects
in
in
the
Watson
quad
repos.
B
So
what
we
have
right
here
is
the
new
GitHub
projects
and
so
for
waddam,
it's
a
little
bit
different
because
we
have
a
different.
B
We
have
a
different
thing
right
now
that
we'll
change
these
item,
we're
focusing
on
like
the
0.4
rewrite
and
everything,
but
we
have
two
views
where
we
can
see
like
every
single
task
with
like
which
thing
it's
on
and
in
our
case,
like
we
grouped
it
by
like
stages
of
work
that
we're
trying
to
get
done,
but
it
also
allows
us
to
give
us
a
kanban
view
of
exactly
what's
happening.
B
What's
done
like
things,
we're
waiting
for,
but
I
think
the
better
ones
are
going
to
be
actually
to
show
you
what
we
we've
tried
it
out
in
two
of
our
repositories
and
if
we
like
it
we're
going
to
roll
it
out
to
everything
else,
and
so
what
we've
done
is
set
up
inside
of
each
one.
We've
said
the
same
thing
that
has
all
tasks:
everything,
that's
a
PR
or
a
bug
or
a
PR
or
an
issue
gets
added
to
here
automatically
and
then
it
gets
put
into
triage.
B
And
so
what
this
does
is
it
helps
anyone
in
the
community
NS
maintainers
realize,
okay,
which
things
do
we
need
to
like
figure
out,
and
then
we
have
a
discussion
stats
that
says
like
hey,
we
started
talking
about
it,
but
we
don't
have
an
exact
answer
yet
and
then
we
have
things
that
are
ready
for
working
are
put
into
to
do,
and
so
the
the
goal
is
that
anyone
who
is
working
on
the
repositories
and
anyone
in
the
community
who
wants
to
see
them
can
come
over
here
and
say
you
know
what
I
what
can
I
work
on,
and
so
they
can
come
in
and
say:
oh
here's,
two
different
things
that
they've
like
triaged
and
are
done
and
are
ready
to
do
and
then,
if
it's
in
progress
like
we
can
move
into
progress
when
somebody
starts
work
on
it
and
it
gets
assigned
by
default.
B
When
I've
created
these
in
the
repositories,
I've
added
every
single
issue,
even
though
we
might,
they
might
be
a
technically
to
do
so.
We
can
go
back
through
and
work
through
this
list
and
say
yeah
this
one's
ready
to
go
and
we
can
drag
it
over.
So
it
gives
us
a
view
of
everything
that's
going
on
and
if
you
actually
go
and
see
these
issues
you'll
see
that
it
gets
like
it's
assigned
to
a
project.
B
You
can
actually
change
the
status
from
here
and
then
there's
all
sorts
of
other
things
we
can
do
in
the
future,
because
we
could
do
we
can
do
like
reports
and
all
sorts
of
things
on
here.
So
we
can
filter
by
certain
stuff,
like
in
this
case,
I've
sorted
by
labels
and
removing
any
better
in,
like
the
done
state
to
be
able
to
like
go
through
and
see
exactly
what
things
are
being
done.
B
You
can
also
like
get
these
Insight
things
which
is
not
going
to
give
us
much,
but
it
starts
to
show
us
like
what
things
are
done
and
I'm
assuming
we
can
modify.
These
I
haven't
really
configured
anything
with
the
charts
yet
so
anyway,
that's
what
we're
currently
working
on
with
the
projects.
We'd
love
your
feedback,
if
you
like
it
hate
it
like
we'd
love
to
hear
from
you,
but
if
we
continue
to
like
this,
then
we're
going
to
try
to
roll
it
out
to
all
of
our
main
projects
and
check.
B
Projects
are
technically
all
independent
of
repos,
but
you
can
link
them
to
repost,
so
you'll
notice
that
we've
linked
to
most
of
these.
So
if
we
go
to
like
the
capability
providers
stuff
like
if
we
go
to
any
of
these,
we
can
come
in
and
we
can
say:
oh
hey,
like
we
have
projects
you'll,
see
one,
and
it
shows
that
it's
like
a
linked
project
for
the
capability
provider.
So
there
you
go
any
questions
from
the
audience
or
these
streams.
A
B
A
It
looks
like
we
had
some
test
ones
in
there
unless
Connor
Smith,
256's
Untitled
project
is
where
we
put
all
the
secret
work.
B
It's
our
secret
secret
super
secret
place,
I
should
say
anyway:
okay,
I'll
go
ahead
and
stop
sharing.
B
So
anyway,
hopefully
that
was
helpful
for
people.
That's,
like
I,
said
what
we're
really
looking
forward
to
to
showing
off
is
the
Witham
stuff
where
we're
at
and
then
the
Project
work
we're
doing
so
like
I
said.
Please
let
us
know
if
people
don't
like
it,
we
won't
use
it.
People
really
like
it
we'll
keep
using
it
and
it
just
seemed
like
it
was
actually
gonna.
Be
really
helpful
for
everybody
to
kind
of
keep
track
of
the
state
of
everything,
but
that'll
pass
back
bricks.
A
I'm
already
yeah,
thank
you.
Thank
you,
Taylor.
That
was
huge,
just
gonna
gonna
re-up
that
thought
that
if
you
have
any
any
feedback,
good
or
bad
about
the
whole
Project's
organization,
please
feel
free
to.
Let
us
know
all
right,
then
I
think
next
on
the
list,
I'm
gonna
go
ahead
and
pass
it
over
to
Roman
who's,
going
to
be
talking
about
the
wasmcloud
host
implementation
that
he's
been
working
on
Roman.
A
Would
you
mind
I
I
know
you
probably
got
a
demo
in
a
little
things,
a
couple
things
that
you
want
to
talk
about.
Would
you
mind
just
giving
an
overview,
and
this
might
again
be
in
your
demo,
but
just
of
what
this
actual
project
is
like
what
what
this
whole
work
is
supposed
to
be
encompassing.
C
Yeah
sure
So,
currently
in
another
club
OTP,
a
hosts
we
use
was
Max
Library,
which
is
providing
the
elixir
of
nif.
Rapping
wasn't
done
with
the
hood
and
it
works
fine.
But
there
are
a
few
very
interesting
things
right
now
happening,
though
it
wasn't,
time
work
things
different
new
specs
being
implemented,
and
we
need.
C
You
want
to
be
able
to
try
to
things
out
quickly
and
provide
these
accessibility
to
use
for
users
and
it's
complicated,
but
using
this
more
general
purpose
was
Max,
which
is
a
great
project,
but
just
for
our
use
case,
we
want
to
be
able
to
really
iterate
quickly
and
for
that
it
makes
sense
for
us
to
have
a
library
which
we
can
use
and
quickly
Implement
things.
And
then
we
have
this
Library
directly
tailored
for
Watson
Cloud
usage,
rather
than
just
general
purpose,
Library.
C
So
another
thing:
we
also
noticed
that,
for
example,
there
are
multiple
hosts
being
written
for
Watson
file
and
we
don't
have
also
one
standardized
place
that
which
we
can
all
contribute
to
one
repository,
one
Library.
We
could
all
share
and
reuse.
These
people
need
to
reinvent
the
wheel
and
times
for
each
host
right.
C
So
there's
basically
an
idea
so
just
being
able
to
experiment
it
wasn't
time
quickly
and
to
have
this
one
shared
host
for
everyone
to
use,
and
so
what
you
want
to
do
is
it's
a
rust
Library
we're
going
to
provide
C
bindings
for
it
and
also
as
the
case
for
things
like,
maybe
go
and
things
like
that.
But
it's
all
up
to
discussion
and
maybe
you'll
see.
What's
the
community
helps
Community
ticket
and
like
what
is
actually
necessary.
C
A
C
So
I'll
cook
your
show
just
because
of
the
structure
for
now
they
have
it's
very
simple.
So
for
now
what
works
for
now
is
just
the
actor
execution
capability
providers.
What
they're
working
on
right
now
so
for
now
the
built-in
providers
is
almost
done.
So
next
step
would
be
like
I,
think
the
actual
existing
capability
provider
support
have
some
tests
and
an
example.
So
maybe,
let's
start
with
an
example,
so
it
already
runs
FL
actor.
C
It's
sorry
for
the
delays,
because
the
video
call
and
screen
sharing
right
so
I'll
actually
show
the
example
itself.
C
C
We
generate
a
keeper
sign
the
module,
just
like
you
do
with
wash
right
normally
and
W3
dot
module.
We
use
the
runtime,
the
library,
that's
just
I've,
been
working
I'm
working
on
right
now.
Now
we
can
instantiate
after
so,
basically
once
we
pre-load
the
module,
we
can
instantiate
10
times,
so
it
will
be
done
currently,
for
example
as
well,
so
each
actor
instance
gets
its
own
store
and
the
things
that
it
should
be
good
for
performance
right.
So
we
don't
need
to
recompile.
C
This
was
a
module
every
time
we
want
to
instantiate
it.
We
also
can
it's
designed
to
be
very
blockable
and
accessible,
so
you
can
plug
in
your
own
log,
implementation
or
or
on
random
number
generation
implementation.
If
you
want
to-
and
this
actually,
you
can
see
it's
here
so
I
have
this
capability
module
a
different
logging
and
another
gen
program,
essentially
adapters
right
so
for
logging.
I
have
maybe
let's
see
here.
C
I'll
say:
there's
a
slog
create
between
the
normal
rust
block,
create
right,
so
there's
an
adapter
for
that
lock
rate
for
the
default
log
implementation
for
that
for
those
who
want
to
use
log
for
logging.
But
if
you
want
to
use
tracing
like
you
need
your
own,
let's
say
for
the
tests.
I
have
a
different
logger
here.
It
says
right
so
I
also
employee
order
again
just
Implement
simple
trades.
C
It's
a
simple
restraint
which
is
doing
to
login
yeah,
so
for
for
external
Community
providers,
you're
going
to
be
able
to
bring
your
own,
probably
just
a
closer
callback
right,
so
you
can
use
nuts
if
you
want,
if
you
want
to
use
something
else
right,
so
it's
basically
just
SDK
for
you
to
be
able
to
build
your
own,
your
own
host,
As,
You
Wish.
C
Well,
probably
as
part
of
this
effort,
probably
we're
gonna
also
have
the
Ros
host,
which
will
be
maybe
simple
just
for
testing,
but
maybe
it's
gonna
go
on
a
bigger
project.
You'll
see
how
it
goes,
but
yeah
also
I
can
see.
I'll
show
you
maybe
like
the
simple
test
that
I
have
currently
running
an
actor
which
does
logging
and
rather
random,
number
generation,
and
you
can
see
here
we
have
this
nice
Trace
with
all
the
calls
that
the
actor
has
actually
done.
C
Yeah,
let's
stay
tuned
and
it's
gonna
get
much
more
interesting
soon.
I
think
I'll
start
to
fall
PR,
so
it
wasn't
Cloud
repository
for
the
POC
of
this
and
then
would
be
glad
to
get
your
feedback
pretty
any
questions.
A
Yeah
so
Roman
I
saw
like
in
that
that
main
example
and
I
know
that
you're,
you
know
you're,
creating
this
and
and
working
through
testing
and
everything
that
is.
This
was
kind
of
like
an
not
quite
this
one
was
this,
the
one
that
you
showed
just
a
second.
C
C
A
Yeah,
my
my
real
question
was
just
gonna,
be
you
know
what
does
this
look
like
and
I
I
know?
You
said
that
you're.
Writing.
Writing.
This
is
a
library.
What
kind
of
functions
are
you
thinking
of
exposing
from
the
library
like
what
kind
of
level
of
abstraction
will
other
hosts
be
working
with.
C
Correct
so
until
start
with
the
runtime
there's
a
runtime
Builder,
it's
a
common
rust
pattern.
You
can
use
the
defaults
if
you
want
to
configure
it.
Maybe
you
know
set
to
maximum
memory
users.
You
want
that
so
after
runtime
there's
an
actor
module.
So
this
is
something
that
you
read
from
from
disk
again
like
it's.
It's
really.
It
usually
wasn't
time
under
the
hood,
but
it's
not
exposed
to
the
user.
Potentially
this
could
support
different
run
times
right,
so
it
could
be
using
other
temperatures
and
whatnot
so
essentially
yeah.
C
So
the
runtime
is
the
first
thing
that
is
going
to
share
it's
a
long
list
object
that
actor
module
you
as
long
as
you
want
to
run
the
same
actors.
Well,
that's
gonna!
You're
gonna
have
to
keep
that
in
memory.
At
an
instance,
it's
a
short-lived
kind
of
just
instance
of
an
actor
that
you
can
kind
of
do
and
because
scale
to
n
or
zero
as
you
as
you
wish.
So
these
are
like
this
is
the
core
of
what
this
library
is
going
to
to
have
right.
C
That's
just
what
you
need
to
actually
execute
stuff.
So
I'll
also
add
capability
providers
here
as
well,
but
we
are
thinking
also
about
adding,
for
example,
personality
like
maybe
helping
you
with
the
nuts
or
just
whatever
messaging,
you
put
everything
you
want
to
use
right
so
like
to
handle
the
topics
and
whatnot.
A
That
answers
my
question
and
then
I
might
have
a
a
follow-up
one
as
well,
because
I
was
really
just
kind
of
curious.
What
it
would
look
like
if
you
were.
You
know,
writing
your
own
example
or
using
this
Library
through
the
CE
ffi
I
guess.
A
The
the
other
thing
I
wanted
to
ask
about
was
around
networking,
because
I
know
that
we've
run
into
a
few
instances
of
portability
with
rust,
like
two
of
the
big
things
that
I
can
think
of
when
working
with
rust
is
that
it's
like
tying
to
a
specific
libsy
version
or
like
tying
specifically
to
open
SSL
or
even
with
rust,
TLS
I,
think
that
depends
on
ring
which
can
get
kind
of
difficult
when
it
gets
to
compiling
to
lower
devices
or
more
embedded
devices.
A
Anyways
a
little
bit
out
of
my
depth
on
on
that
one.
But
I
was
really
curious
about
if
this
would
just
be
essentially
a
wrapper
around
wasm
time
to
manage
all
the
wasm
operations
and
if
we
were
going
to
be
doing
any
Nats
networking,
because
I
I
think
that
we
could
definitely
help
people
get
set
up
with
like
the
right
topics
and
everything.
But
I
can
see
some
difficulties
around
actually
encapsulating
that
in
this
Library
did
you
have
some
thoughts
here.
C
Yeah,
so
so
again,
it's
basically
the
idea
is
that
you
never
have
to
pay
for
things.
You
don't
use
right.
So
if
you,
if
you
don't
want
to,
if
you
don't
use
the
logging
Craig
to
look
great
right,
it's
optional,
like
it
shows
here
in
the
top
right
so
like,
for
example,
are
you
by
default?
C
You
have
these
two
default
features
that
you
have
the
Imports
right
with
the
log
crate
and
the
random
trade,
which
are
only
imported
if
you
actually
opt
in
by
default,
the
software,
but
it's
opt
out
of
my
way,
but
so
similarly,
we
could
do
also
for
things
like
nuts
right.
So
you
could
provide,
says
the
provider
that
could
use
the
Callback
right.
C
So
it's
all
supposed
to
be
sensible,
so
we
could
have,
for
example,
a
NASA
rotation
for
this
external
provider,
which
we
could
provide
where
it
could
be
again
configurable,
accessible
and
yeah.
So
it
would
also
be
like
opt-in
right.
It
would
be
a
feature
we
had
a
feature
flag
if
you.
C
You
don't
want
to
compile
it
to
the
compile
it,
but
if
you
do
want
it,
then
you
could
opt
in
into
this
feature
and
then
have
this
adapter
for
capability
provider,
but
to
share
actor.
Can
you
know,
go
to.
C
Yeah
so
I
guess
we
could
show
quickly
just
the
provider
right,
it
could
be
just
a
function
right.
A
function
is
well.
This
is
the
provider
from
the
perspective
of
actor
right
so
because
all
the
gas
is
well
The,
Binding,
namespace
operation
or
some
payload,
and
it
just
returns
some
payload
and
how
you
do
it?
Well,
it's
up
to
the
user
of
this
library,
but
it
becomes
absolutely
provides
some
personality
to
help
the
desperate
so
yeah,
okay,.
A
Cool
all
right,
that
was
it's
a
my
level
of
stuff,
but
Roman.
This
is
really
awesome
is.
Is
the
code
actually
published
yet,
or
is
this
still
kind
of
just
like
in
a
private
state
where
you're
working
on
it.
C
Yeah
so,
as
I
said
so
I'm
hoping
to
maybe
not
today
anymore-
maybe
tomorrow
already
for
what's
it
called
slash,
wasn't
our
repository
yeah
I
need
to
figure
out
how
to
scope
this
nicely.
So
it's
it's
a
smaller
chat
which
are
easy
to
review,
but
I
would
want
to
have
you
know
a
working
at
least
a
FL
actor
right
so
and
maybe
topical
music
providers
as
well
or
maybe
that
would
be
a
research
for
a
second
PR.
That
I'll
say
tomorrow,
watch
out
for
PRS
in
Amazon,
Cloud
and
and.
A
Yeah
awesome,
yeah
I
think
we've
been
looking
for
a
little
a
little
excuse
for
things
to
put
into
the
that
wasn't
Cloud
Watson
Cloud
repo
for
a
little
while
so
looking
forward
to
looking
forward
to
seeing
that.
Maybe
we
can
talk
about
a
little
more
next
week,
all
right!
Anybody
else
here
have
questions
for
for
Roman
on
this
work.
A
All
right
well,
thank
you
Roman!
That's
that's!
Really
awesome.
Looking
forward
to
seeing
that
evolve,
I
think
that's
the
end
of
our
official
agenda.
For
today.
Does
anybody
else
have
any
other
questions
or
General
things
in
the
Watson
Cloud
community
that
they
like
to
chat
about.
A
A
If
anybody
is
in
the
Los
Angeles
area
tomorrow
and
Friday,
Taylor
and
I
are
actually
going
to
be
over
there
for
scale
and
we're
going
to
be
doing
talks
on
Friday
and
Saturday.
So
please
feel
free
to
hit
us
up
in
the
wasmcloud
slack
and
we
can
go
get
a
coffee
or
a
soda
or
something
other
than
that.
I'll
see
you
all
next.