►
Description
wasmCloud is a platform for writing portable business logic that can run anywhere from the edge to the cloud, that boasts a secure-by-default, boilerplate-free developer experience with rapid feedback loop.
#wash #code #programming #wasm #webassembly #development #IT #newcode #community #github #oss #opensource #career #software #browser
A
B
Hello,
my
name
is
brian
slatten.
I
am
an
independent
software
consultant
with
about
30
years
of
software
development
experience.
I've
been
tracking
indirectly,
what's
been
going
on
here
through
ever
since
I
read
kevin's
awesome
book
and
now
I'm
writing
a
book
for
o'reilly
on
webassembly,
and
I
want
to
understand
this
better.
But
I
also
am
very
interested
in
the
particular
confluence
of
technologies
and
the
approach
that
you're
taking
and
so
I
hope,
to
to
become
a
bigger
part
of
the
community.
A
That's
awesome,
brian
and
we're
super
glad
to
have
you
please
let
us
know
how
we
can
help
support
you
on
your
efforts
and
there's
a
bunch
of
other
adjacent
folks
here.
That
may
be
interesting
to
you
as
well.
I
know
andrew
brown's
on
the
call
intel
working
on
the
yzn
stuff.
That's
in
was
just
put
into
wasm
time,
for
example,
so
perhaps
a
bridge
across
the
community,
as
we
can
help
just
a
real
quick
call
to
action
final
day
for
t-shirt
order.
A
Please,
if
you're
us
based,
you
can
just
use
the
forms
as
they're,
linked
in
slack
if
you're
international,
just
pm
me
whatever
you
want
you're
more
than
happy
to
order,
one
of
every
style.
If
you'd
like
or
multiple
styles
of
t-shirts,
as
usual,
we
try
to
start
each
meeting
with
some
sort
of
a
demo
or
presentation.
I
think
we've
got
two
really
short
ones
this
week,
so
I'm
going
to
turn
it
over
to
kevin
real
quick
to
talk
about
other
work
on
accurate
actor
calls
all
right.
Let's
see,
if
I
can.
C
C
C
So
now
with
0.15.2
you
can.
We
now
have
fully
functioning
acted
actor,
calling
supported
with
what
we
call
what
we're
referring
to
as
call
aliases.
So
in
the
scenario
where
you
want
one
actor
to
talk
to
another
one,
we
don't
want
you
to
have
to
try
and
we
don't
want
you
to
have
to
hard
code
the
actor
public
keys
into
your
actors,
because
those
public
keys
can
change
if
the
signer
of
the
actor
change
changes.
C
So,
if
you're
in,
if
you're
on
your
laptop
with
and
you
have
your
own
set
of
keys
or
if
you're
in
a
staging
environment
or
dev
or
qa
and
those
are
all
using
different
keys,
then
production-
we
don't
want
you
to
have
to
recompile
your
actor
to
take
to
to
deal
with
that.
So
when
you
sign
an
actor
module,
you
can
now
sign
it
with
this
call
alias,
and
so
in
this
case
I've
signed
it
with
an
example
called
or
with
a
call,
alias
called
wasmcloud.
C
Slash
example
slash
ponger,
and
this
is
for
the
ping
pong
sample
that
we
have
available
now
the
code
is
actually
fairly
straightforward.
You
just.
We
now
have
a
call
actor
function
in
the
rust
actor
core
and
in
go
and
assembly
script.
We
will
we'll
have
this
convenience
function
shortly,
but
you
can
still
do
it
quote
unquote,
the
hard
way
still
just
by
passing
the
call
alias,
and
so
in
this
ping
pong
example.
C
We
have
one
actor
that
receives
an
http
request
and
in
response
it
calls
another
actor
which
handles
this
ping
request,
and
what's
interesting
here,
is
that
this
ping
request
handler
looks
just
like
any
other
request
handler
put
another
way.
You
can't
you
can't
tell
from
here
whether
a
capability
provider
is
sending
this
message
or
whether
an
actor
is
sending
that
message
and
that's
by
design.
So
we
have.
We
have
an
actor
interface
here
called
ping
and
we're
using
the
interface
here.
C
C
In
other
community
meetings,
you
can
test
all
this
stuff
out
in
the
rebel
by
invoking
any
of
these
actors,
and
so
you
should
still
be
able
to
poke
and
prod
them
either
in
automated
tests
or
through
the
rebel,
and
it
should
be.
It
should
be
easy
regardless
there's
an
integration
test
in
in
the
wisdom
cloud
main
repository
that
invokes
the
ping-pong
demo,
but
you
can,
you
can
play
with
it
on
your
own,
just
by
grabbing
them
out
of
the
out
of
the
examples.
A
C
C
A
A
A
So
I
will
continue
to
feed
some
examples
in
here
of
things
that
are
labeled,
but
I
sure
would
appreciate
some
feedback
on
how
we
lay
this
out
and
tell
it.
I
think
the
story
would
go.
Is
that
we'd
start
and
we'd
have
one
of
these
boxes
pop
up
and
then
label
it
individually
and
then
we'll
have
a
layer
appear
at
the
gray,
it'll
be
a
different
color,
but
we'll
have
that
sort
of
appear
and
call
that
lattice
and
then
have
the
lattice
layer
show
and
then
we'll
talk
about.
A
F
When
I
look
at
this,
I
was
kind
of
thinking:
it'd
be
cool
to
have
like
a
hover
pop-up
window
on
each
of
those
layers
of
our
architecture.
That
shows
the
command
to
instantiate
that
layer
of
the
architecture.
So
you
know,
if
you've
got
a
host
on
the
bottom,
you
hover
the
command.
You
get
a
small
window
pop
up.
That
shows
you
know:
install
wasm,
runtime,
yeah,
okay,.
A
I,
like
that
yeah,
it's
pretty
cool,
it's
interactive,
it's
kind
of
fun.
I
I
don't
yet
have
a
plan
for
how
I'm
gonna
surface.
You
know
the
wash
control
demon
on
the
side.
Maybe
it
comes
up
as
like
a
heads-up
console
from
the
bottom
to
you
know
to
like
interact
and
issue
commands,
and
then
that
shows
things
connecting
like.
Maybe
we
show
the
bind
and
we
can
do
a
whole
story
there.
What
I
will
likely
try
to
do
is
I'm
behind
on
getting
wasn't
cloud.com
the
landing
page,
the
clear
value
props
out.
A
You
know
the
wash
repel
or
even
the
plea
and
then,
as
you
type
commands,
you
sort
of
see
things
come
down
and
bind
through
the
lattice.
You
know,
regardless
of
where
they
are,
and
then
we
can
have.
You
know
some
narrative
along
the
sides
there.
So,
as
I
get
some
examples
into
into
slack,
you
know
a
feedback
on
this
please
and
this
o'brien
for
you.
This
will
all
be
licensed.
A
You
know
everything
in
wasn't
cloud
is
in
an
llc
and
we'll
all
be
licensed
open
source,
including
all
of
our
graphics
and
and
everything
else.
So
it'll
all
be.
You
know,
apache
or
mit
license
something
copied
left
so
more
than
welcome
to
reuse
and
and
share
this
in
any
kind
of
explainers
or
blog
posts
or
chapters
or
anything
like.
C
I,
like
the
idea
that
of
you
know
as
you
move
your
mouse
around
or
you
click
on
certain
areas
that
you
know
different
pieces
of,
that
architecture
can
light
up
in
response
to
it,
and
you
can
see
you
know,
what's
involved
there
and
and
how
to
how
to
control
that,
but
also
maybe
where
to
go
for
more
information
on
it.
You
know
that
could
be
a
way
to
get
into
different
parts
of
the
documentation,
and
oh
that's
what
yeah.
C
I
think
I
also
mentioned
earlier
this
morning,
like
the
idea
of
where,
if,
if
the
gray
is
the
the
lattice
layer,
it
shouldn't
be
isolated
in
these
stacks,
it
should
actually
be
used
as
the
way
to
connect
all
of
those
stacks.
So
just
having
the
the
gray
layer
be
one
single,
solid
piece
that
spans
all
of
the
hosts
on
the
bottom.
A
A
You
know
like
clear,
glass
layer
here
so
that
way
you
can
see
there's
some
substance
to
it,
but
it's
still
translucent
and
you
can
see
the
layers
below
it,
because
I,
I
think
the
sort
of
trick
here
is
going
to
be
to
show
a
bunch
of
lattices
all
like
to
give
the
the
feeling
that
you
know
where
the
important
bit
is
that
it
doesn't
matter
topologically.
Where
things
are
deployed,
you
don't
have
to
make
any
changes
to
your
application.
It
just
works.
Yeah.
C
A
Like
if
you
put
the
box
in
here
like
it's
sitting
in
three-dimensional
space,
that
was
our
original
yeah
and
kevin,
you
know
obviously
the
that
was
our
original
intention.
You
know
here
when
we
were
designing.
The
logo
was
that
you
know
we
wanted
something
that
had
multiple
layers
of
dimensionality.
So
it's
not
just
the
w
it's
the
inverted
box
here.
A
So
if
I
kind
of
you
know,
drag
something
in
and
I
don't
know
how
to
send
something
to
the
back
yeah
I'll
google
all
that
later,
but
I
did
toy
with
some
of
that
and
it
looked
like
absolute
hot
garbage
kevin.
I
tried
to
tilt
the
logo
and
everything
else,
I'm
not
a
graphic
designer.
So
I
think
I
should
probably
hand
all
this
to
somebody
off
to
somebody
who
is
once
we
get
past
like
initial
concept.
Yeah,
I'm
no
expert.
A
I
think
so,
but
we'll
we'll
do
some
experimentation
and
see.
I
originally
thought:
maybe
we'd
lay
the
logo
on
top
of
the
box
or
something
like
that.
So
lots
of
things
we
can
toy
with
there
and
our
color
palette
and
all
of
our
logos
are
all
checked
in
already
just
just
fly
off
any
any
other
comments
or
questions
on
on
that.
A
Okay,
a
couple
other
just
quick
administrative
things
and
then
we
can
move
on
cfp
is
obviously
closed
for
a
wasm
day.
The
committee
is
supposed
to
be
through
reviews
on
those
by
friday
for
final
decisions,
so
hopefully
that
happens
shortly.
Webassembly
summit
still
on
track.
The
schedule
was
announced
just
recently.
If
everybody
wants
to
check
that
out
looks
like
there's.
Some
really
amazing
talks
there
and
then
the
wasm
time
bible
meeting
is
next
thursday
at
one
o'clock
ping
me.
A
G
I've
been
putting
in
a
couple
of
issues
into
the
wash
repo
or
and
and
the
wasm
cloud
repo,
any
of
the
any
of
the
like
feature,
requests
that
we've
been
talking
about
in
community
meetings
or
in
slack
trying
to
put
those
into
writing
and
available
for
any
comments.
That's
an
rfc
that
we've
been
sorry
dogs
being
annoying.
That's
an
rfc
that
we've
been
going
back
and
forth
on
a
lot
just
to
improve,
like
the
initial
experience
of
starting
an
actor
in
the
first
place.
G
G
So
you
know
this
would
be
a
feature
for
the
rebel
where
you
could
start
it
without
launching
nats,
which
means
all
you
would
need
in
order
to
start
with,
like
developing
with
wasm
cloud
is,
is
wash
locally,
so
that
would
make
the
the
initial
experience
a
lot
easier
if
we
cut
out
the
oci
registry
important
to
keep
it
so
that
we
can
pull
remote
resources.
But
if
we
cut
that
local
part
out,
then
that
reduces
the
friction
by
a
lot.
G
So
this
is
something
that
I've
been
working
on.
I've
just
started
it
pretty
recently.
A
big
project
that
I
just
finished
and
merged
into
wash
is
like
a
whole
suite
of
unit
and
integration
tests.
So
we
have
like
a
full
testing
suite
that
you
know.
Every
additional
feature
now
is
going
to
be
checked
against.
I
was
pretty
proud
of
of
that
a
lot
of
work
and
went
into
that
pr.
G
C
Absolutely
I
think,
well
he's
setting
that
up
too.
I
think
one
of
the
other
things
I
don't
remember
exactly
which
issue
it's
on,
but
one
of
the
other
things
that
we
were
talking
about
is
that
the
idea
of
being
able
to
monitor
a
a
wasm
file
as
an
actor
that
you
want
running
so
whenever
you
recompile
it
with
rust
or
whatever
that
wasn't
file
just
gets
relaunched
into
your
host
and
one
of
the
the
implicit
assumptions
in
order
to
be
able
to
do.
C
That
is
that
you
have
a
wasm
cloud
host
that
runs
longer
than
your
wash
cuddle
command,
and
so
one
of
the
things
we
might
want
to,
I
think
we
need
to
look
into
is
how
maybe
one
of
the
things
that
wash
does
is
sort
of
spawn
a
wasm
cloud
host
as
a
demon
in
response
to
some
or
all
of
its
commands.
So
if
you
run
a
wash
cuddle
command
and
there's
no
host
running
wash
should
maybe
start
one
up
and
then
keep
track
of
it
so
that
it
can
use
it
for
subsequent.
G
Commands
yeah
that
one
is
possibly
dependent
on
the
no
nats
mode,
wa
like
the
rebel
pr,
but
if
we
can
get
wash
to
pay
attention
to
a
local
signed
wasm
that
either
like
rebuilds,
when
you
save
in
your
ide
or
or
like
reschedules,
whenever
an
update
comes
in
then
that'll
keep
the
developer
loop.
The
feedback
loop
for
an
actor
release,
really
small
and
and
that'd
be
great.
G
G
So
the
the
demo
that
I
had
is
a
pretty
short
demo.
I've
got
a
lot
of
garbage
commands
sitting
in
here
right
now,
just
to
show
it
off,
but
I
wanted
to
call
out
a
few
people
who've
been
contributing
to
wash
thank
you
to
steve
lr.
That's
the
github
handle
I'm
forgetting
the
last
name,
but
they
submitted
a
couple
of
issues
into
the
or
a
couple
feature
requests
into
the
repo
which
have
been
great
to
work
on.
G
G
The
other
part
of
this
is
it's
potentially
difficult
to
see
over
zoom.
But
if
you
look
at
the
title
of
the
log
pane
and
the
rebel,
whichever
one
you're
actually
focused
on,
is
bold
open
to.
If
this
is
not
quite
like
accessibility
friendly,
like
it's
not
very
obvious,
then
we
can
add
in
a
potential
different
like,
like
parentheses,
focus
or
something,
but
some
other
indicator
other
than
this
log
saying
where
the
focus
is
where
your
commands
are
going
is
it
was
nice
to
have
yeah?
I
think.
A
A
I
love
that
you
know
on
that
on
that
topic
brooks
the
my
favorite
part
of
this
call.
So
far
was
earlier,
someone
else
was
talking
and
they
used
our
project,
and
I
love
that
that
actually
made
me
feel
really
good
right
here
like
to
have
like
anybody
that
shows
up
on.
This
call
feel,
like
you
know,
hey.
This
is
as
much
mine
as
it
is.
Anyone
else's
that
to
me
is
like
my
goal.
A
Is
that
no
one
ever
thinks
of
blossom
cloud
as
kevin's
project
no
offense
to
kevin
ordered
brooks's
project,
but
that
they
think
of
it
as
our
project
as
a
community,
and
I
think
that's
what
we're
really
trying
to
do
with
all
that
intentionality
around
writing
out
the
rfcs
and
the
grooming
on
on
good
first
issue
and
is
really
try
to
pull
in
and
make
this
a
sticky
community
easy
to
get
into
and
happy
to
be
a
part
of.
So
thank
you
so
much
brooks
for
leading
by
example
on
that.
A
G
I
can
just
do
I
can
do
one
more
thing.
I
wanted
to
thank
the
github
user,
javier
camano
and
our
own
justin
james,
for
contributing
features
and
and
the
actual
code
to
this
swash
release.
That's
going
to
come
out.
So
thank
you
for
doing
that
and
to
steve
for
contributing
issues
that
are
going
to
be
merged
in
this
milestone.
A
E
I
don't
know
not
news,
but
I
want
to
talk
about
the
integration
unit,
testing
of
the
wasm
cloud
project.
I
personally
have
not
been
able
to
get
all
of
the
integration
tests
running,
I'm
still
troubleshooting
that,
but
they
make
assumptions
on
having
redis
and
gnats
running
locally
and
the
unit
tests.
E
I
could
certainly
have
many
more
of
those
because
wondering
whether
or
not
you
guys
would
accept
a
pr
that
adds
a
lot
of
unit
tests,
it's
hard
to
do
as
somebody
who's
not
involved
in
day-to-day
work,
because
I
might
be
testing
things
that
are
not
going
to
live
very
long
and
then
tests
become
a
burden.
So
I
want
to
get
your
thoughts
on
on
how
to
improve
the
testing
of
wisdom
cloud
so
that
it's
easier
to
contribute
to.
C
C
We
use
the
redis
provider.
I
think
a
little
bit
too
much
for
some
of
the
integration
tests
and
it's
just
because
it's
it's
almost
like
a
crutch,
because
we
we
have
that
redis
provider
and
we've
had
it
since
the
beginning.
So
we
use
that
and
it
makes
it
so
that
you
have
to
have
radius
running
we
should
we
should
definitely
make
it
so
that
redis
doesn't
have
to
be
running,
or
you
know
that
we
do
that.
We
me
we
take
advantage
of
some
of
the
in-memory
stuff
whenever
possible.
C
E
A
little
hard
to
get
to
so
what
might
be
helpful
for
someone
like
me
who
wants
to
contribute
is
to
know
what
parts
of
wasm
cloud
you
aren't
looking
at.
So
if
there's
active
development
in
a
certain
portion
where
signatures
or
methods
might
change,
it's
not
really
worth
it
for
somebody
to
from
the
outside
contribute
tests.
But
if
there's
a
chunk
that
you
consider
stable
or
unlikely
to
change
in
the
near
future,
that
might
be
a
good,
a
good
place
to
start
so.
C
Right
now
things
that
I
mean
the
the
public
api
for
the
host
should
be
considered
as
as
stable
as
anything
else
just
about
everything
should
be.
You
know
it's
no
more
or
less
stable
than
everything
else.
I
think,
as
things
were
a
little
difficult
to
deal
with
between
0.13
and
0.15,
because
we
basically
just
rewrote
everything
wholesale
in
theory,
we're
not
planning
on
doing
any
of
those
massive
front
to
back
rewrites
again.
A
You
know
we
really,
I
think
the
dot
15
release,
I
think,
was
needed
because
it
was
based
on
a
bunch
of
feedback,
but
we
had
too
much
in
that
release.
You
know
we
slipped
a
little
bit
on
our
delivery.
I
think
what
we
should
do
is
we
should
maybe
start
thinking
about
looking
ahead
to
if
it's.
If
the
next
release
focuses
on
the
usability
which
I
love
especially
heading
towards,
may
the
fourth
which
is
kubecon
eu,
you
know
we
will
be
a
part
of
wasn't
a
nominally.
A
Wasn't
cloud
is
or
a
related
entity
is
one
of
the
key
sponsors.
So
there
will
be
a
lot
of
prime
time
opportunity
for
us
to
take
what
we're
working
on
and
what
we're
doing
and
give
a
message
to
the
broader
community.
So
I
really
underplayed
the
even
the
dot
15
release
planning
on
us
really
doubling
down
on
like
marketing
and
those
sorts
of
efforts.
Community
growth
around
may
the
fourth.
A
So
I
think,
if
we
want
to
maybe
spend
some
time
in
slack
sort
of
thinking
about
what
is
reasonable
for
us
to
put
on
the
agenda
for
the
next
call.
It
45
to
you,
know,
55
days
or
so,
and
make
sure
that,
if
we're
targeting,
you
know
15,
2
or
even
a
major
release
for
the
ecosystem.
That
we've
got
a
good
story
to
tell
and
some
great
demos
for
may
the
4th,
because
it's
going
to
be
our
best
opportunity
from
then
until
the
fall
with
kubecon
us.
A
C
Yeah
so
0.15
was
released.
I
think
one
of
the
main
focuses
between
now
and
all
the
demos
at
cubecon,
the
the
focus
there
is
all
basically
stabilizing
and
making
things
easy
to
use,
making
sure
that
the
experience
is
better
and
that
the
exposure
that
we
have
to
new
developers
is
as
smooth
as
possible.
So
all
of
that
stuff
should
get
easier
and
smoother.
C
A
I
I
think
I
agree
kevin.
That
sounds
like
a
really
solid
plan
and
I
think,
if
I
had
a
short
list
for
my
dream
items
that
we
could
get
done
by,
then
it
might
be
a
set
of
code
code
tutorials.
We
have
a
really
great
sketch,
for
example,
for
wash
brooks
in
the
last
demo.
You
did
in
your
little
demo
script
and
you
walk
through
all
the
key
features
of
wash,
but
that
needs
to
be
part
of
a
broader
story
that
starts
with.
A
A
If
we
think
about
this
little
short
pamphlet
of
you
know:
hey
here's
the
let's
just
install
all
the
tooling,
you
know
katakota
tutorial,
let's
which
may
feel
basic,
but
I
feel
like
we
would
behoove
us
to
have
the
the
gentlest
on
boarding
possible
to
people
to
be
the
most
welcoming
group
then
go
to
actor
101
then
maybe
wash,
and
then
maybe
it's
capability,
10101
or
102,
and
then
a
platform
or
something
I
don't
know
if
we
even
had
those.
First,
three
chapters
or
first
two
chapters.
A
C
C
B
A
So
many
of
the
pieces
are
already
out
already.
If
you
look
at
the
docker
composes
getting
checked
in
and
like.
I
know
that
we're
like
the
raw
materials
are
on
the
counter
here.
You
know
they
just
need
to
be
like
put
in
order.
I
don't
know
if
anybody's
interested
in
volunteering
to
not
to
help
drive
the
effort
forward.
A
If
somebody
would
be
interested
in
yes,
you
know
kind
of
like
taking
the
lead
on,
like
you
know,
setting
up
a
our
katakota
account
and
at
least
sketching
out
the
plan
and
coordinating
like
pulling
in
and
where
we
need
people's
attention.
That
would
be
great,
I
yeah,
so
I
can
hound
people
offline
and
try
to
ball
and
beg
people
to
do
that,
but
we'll
see
just
pull
the
free.
A
A
That
would
be
a
different
kind
of
a
giveaway
for
giveaway
bicycle
shorts,
but
the
the
cycling
hoodies,
you
know
with
the
pockets
in
the
back
so
we'll
see,
and
we
also
do
have
the
ability
to
do
email
addresses
I've
not
rolled
those
out
to
anyone.
I
I
only
set
up
the
domain
because
part
of
what
I
want
from
may.
The
fourth
is
that
experience
around
having
like
security,
wasn't
cloud.com
published,
and
you
know
having
some
documentation
written
up
for
how
do
I
report
a
vulnerability?
A
How
do
I
report
a
violation
of
community
standard
and
some
of
that
grooming
kind
of
stuff?
And
that's
in
anticipation
of
new
people
joining
you
know
like
there's
potential
friction.
I
want
to
make
sure
we
plan
and
account
for
that.
So
there's
lots
of
things
that
you
know
goodies
that
we
can
put
on
the
table.
I
don't
know
if
we
ever
if
I
didn't,
even
if
we
wanted
to
do
team
email
addresses
or
you
know
whatever
the
case
is,
you
know,
that's
that's
always
a
possibility.
C
D
In
here
I
just
I
have
to
drop
off
soon.
Something
else
just
to
be
aware
of
that.
Probably
it's
one
of
those
mutually
beneficial
things
is
pressler
is
moving
towards
1.0,
probably
in
the
next
few
months.
Basically,
networking
is
our
last
big
feature
that
we
have
to
do.
That's
why
I
was
asking
that
question
earlier
in
slackkevin
was
we're
just
trying
to
make
sure
we
can
get
networking
and
networking
is
bad
enough,
but
trying
to
make
it
work
in
a
way.
D
That's
extensible,
for
anybody
is
even
worse,
so
we're
working
on
that
right
now
after
I
eventually
take
on
updating
the
wasn't
cloud
provider
which
I
am
dreading,
if
I'm
being
honest,
because
I
have
to
update
that
and
tokyo,
so
yeah
sorry
kevin
for
any
future.
Large
amounts
of
slack
messages
I'll
be
sending
you
on
that.
But
the
the
point
of
this
besides
my
meandering
is
that
once
we
get
that
out,
we're
gonna
be
doing
our
own
polishing,
and
so
networking
could
take
anywhere
from
one
month
to
three
months.
D
C
D
Going
to
come
soon
and
that's
going
to
allow
for
both
projects
to
bask
in
the
glow
a
little
bit,
because
wasn't
cloud
provider
is
one
of
the
big
ones
coming
out
so
anyway.
Anyone
who
also
wants
to
contribute
there
would
be
much
appreciated
we're
not
as
big
of
action.
We
don't
use
all
the
advanced
features
of
wazing
cloud,
because
it's
just
it's
it's
shoehorning
it
into
into
kubernetes.
So
there's
not
a
way
to
use
all
the
advanced
features.
D
So
if
there's
people
who
know
it
better
and
want
to
like
mess
around
with
it,
it
is
now
in
the
awesome
cloud
org
on
github.
It
is
all
there
and
so
any
help
or
things
or
improvements
would
be
helpful
there,
because
that
will
help
both
projects
out
here,
because
president
going
want
to
know
and
having
that
as
being
one
of
the
things
that's
going
to
direct
people
towards
watsonville
and
get
them
interested
and
it'll
reflect
back
on
us,
because
anyone
interested
in
wasn't
that'll
say:
oh,
I
can
run
in
kubernetes.
D
D
We
have
that
out
there,
it's
gonna
be
hitting
1.0
soon,
so
I
guess
just
be
aware
at
the
very
minimum
and
if
anyone
wants
to
help
out
in
the
community,
who's
interested
in
those
things
feel
free
to
reach
out
there
or
in
the
crested
channel,
in
the
washington
slack
or
the
kubernetes
slack
for
any
questions
or
things
so
yeah.
That's
that
that's.
A
All
I
have
absolutely
taylor
and
thank
you
so
much
for
the
call
outs
there
and,
as
always,
you
know,
you
know,
I
think
there
is
just
such
a
natural.
You
know,
you
know
demonstration
point.
You
know
with
the
between
the
two
projects,
as
we
even
start
planning
for
kubecon
us,
which
I
think
would
be
a
bigger
push
on
our
part.
A
You
know
maybe
there's
opportunities
for
another
workshop
like
we
did
explore
wasm
last
summer
or
something
along
those
lines
so
100,
just
let
us
know
how
we
can
help
you
to
be
successful.
We
do
have
a
logo
exchange
officially
with
wasmcloud
llc.
I
have
a
request
into
microsoft
or
I
have
one
on
the
way
or
it's
in
flight,
and
then
I
I
did
get
a
couple
back
already
from
some
of
the
more
prominent
community
members.
A
So
when
we
get
wasmcloud.com
up
we'll
start
to
have
that
little
scrolling
bar
of
look
at
all
these
amazing
organizations
that
are
as
enthusiastic
about
this
technology
as
we
are,
and
also
hopefully
using
it
yeah
anyone
else
open,
call
across
the
board
all
right.
Well,
I'm
gonna
go
and
stop
recording
and,
as
always,
everybody
can
hang
on
and
we
can
chit
chat.
Do
the
meeting
after
the
meeting.