►
From YouTube: wasmCloud Community Meeting - 7 Jun 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
Yeah,
hey
everybody
Welcome
to
the
wasmcloud
community
meeting
for
Wednesday
June.
The
7th
we've
got
a
pretty
exciting
demo
to
start
us
off
today
and
then
we're
going
to
be
talking
about
some
one,
current
release
that
we
put
out
earlier
in
the
week
and
then
an
upcoming
release
for
wash
and
then
an
update
on
our
cncf
project
status.
Yeah,
hey
everybody
Welcome
to
the
was
that's
me
all
right,
I!
A
Think
with
that
Taylor,
you
know,
go
ahead
and
hand
it
over
to
you
for
wash
spy,
which
you
know
I
just
came
back
from
a
little
time
out
of
the
office.
I
didn't
even
know
what
Washed
by
is,
and
now
here
you
are
demoing
it
would
you
mind
giving
as
as
well
as
the
demo
just
kind
of
an
overview
and
motivation
around
what
what
this
is.
B
Yeah
I
am
just
starting
up
some
providers
real,
quick,
because
I
realized
I
had
shut
down
my
my
local
wash
and
then
I
can
I
can
show
you,
but
basically
what
we
were
thinking
of
was
there's.
We
just
really
want
to
improve
a
lot
of
the
debug
experience
in
the
inner
Dev
Loop
for
people
as
we've
been
working
on
it
and
by
Nature
like
watching
Cloud's
a
distributed
system.
B
That's
the
targeted
thing
like,
even
even
when
you're
running
locally
it
assumes
distributed,
and
so
we
were
thinking
like
what
can
we
do
to
like
show?
What's
going
on
one
of
the
most
common
things
like
how
do
I
see,
what's
actually
being
sent
between
things
and
all
that
so
wash
spy
is
our?
Is
our
attempts
to
do
that,
and
so
this
is
an
experimental
thing.
So
we've
introduced
an
experimental
flag
that
that
does
this
for
us
that
you
can
enable
I
should
say
otherwise
it
won't.
Let
you
run.
B
B
And
then
Brooks
I'm
going
to
ask
a
Brooks
as
a
service
request
for
what's
the
current
version
of
KV
redis,
because
I
can
never
remember
it
off
the
top
of
my
head
I
think
19
19
is
at
least
new
enough.
I
thought
it
was
20.
but
shoot.
B
And
I
need
someone
to
look
I
actually
think
I
might
have
it.
My.
A
B
20.
this
is
zero.
Twenty
zero
I
was
right,
I'm
slowly
taking
over
Brooks
as
a
service.
Okay,
okay,
we'll
give
that
a
second
to
start
and
then
I
should
have
okay
perfect.
We
have
everything
there,
so
what
I
did
was
just
spin
up.
You
know
our
typical
Echo
and
KB
redis
things
so
the
so.
B
So
what
it'll
look
like
is
wash
spy
Echo
like
this
and
so
I
I'll
say
like
this.
This
right
here
can
be
an
actor
ID.
B
It
can
be,
it
can
be
the
something
and
something
that
matches
like
very
Loosely
matches,
either
the
call
Alias
or
the
name
of
the
actor,
so
there's
no
more
having
to
specify
an
actor
ID.
You
just
give
it
the
name
and
we're
gonna
actually
try
rolling
this
out
to
other
commands
soon.
So
you
don't
have
to
specify
IDs
we'll
try
to
do
the
same
thing
for
providers
and
whatnot,
but
I'll
even
show
you
like
I
can
do
this
with
the
like
here.
I
can
do
it.
B
And
so,
when
I
do
wash
by
Echo,
it's
going
to
say:
okay,
I'm
spying
on
an
actor
Echo.
So
if
I
come
over
here
and
I,
do
a
curl
of
just
the
echo
API
and
I.
Come
back!
I
see
this
thing
that
says:
okay
timestamp
from
HTTP
server
to
echo
on
this
host
and
here's
the
operation
and
the
message
that
was
sent,
and
so
then
I
can
also
do
this
with
like
the
KV
counter.
B
So
if
I
go
to
localhost
8081
and
pull
this
up,
we'll
probably
I
need
to
actually
go
spy
on
it.
So
I'm
going
to
come
back
here
and
say:
spy
on
EB
counter,
so
I'm
gonna
pull
the
chat
down
here
and
so
and
yeah
Kevin
asked
the
question.
The
host
in
the
output
is
the
host
that's
in
in
the
invocation.
So
it's
the
host
that
admitted
this
invocation
is
I,
don't
have
any
more
host
IDs
than
that.
So
we
can
try
to
specify
that
to
clarify
that
Sammy.
B
Here's
the
KB
counter
and
say
increment
and
if
I
come
back
to
here,
we'll
see
that
I
can
I
got
the
HTTP
request
so
from
HTTP
server
to
KB.
Counter
on
this
host
I
see
the
get
request,
all
the
headers
that
were
sent
and
then
I
say:
okay
from
KB
counter
to
KB,
redis
yeah
see
this
is
interesting.
So
it
has.
B
The
host
is,
is
different
here,
all
I'm
doing
is
pulling
the
host
from
the
the
field,
that's
in
the
invocation
and
then
I
say
operation,
key
value,
increment
and
then
I
say,
and
they
have
the
message
right
there.
So
what
this
will
attempt
to
do
on
the
on
the
inside
is
it's
going
to
decode
the
invocation
and
then
it's
going
to
try
to
decode
the
inner
message,
which
is
an
opaque
payload.
So
we're
just
doing
our
best
guess.
B
We
first
try
to
decode
it
as
message
pack,
which
is
the
most
common
thing
we
see
and
then
C
board,
because
we've
had
a
couple
that
do
that
and
then,
if
it
fails,
it
just
tries
to
format
the
data
as
like,
escaped
Unicode
string,
and
so
that
is
the
that's
the
basically
all
washed
by
does
and
apparently
discovers,
there's
a
bug
in
the
payload
I'm,
not
sure
why,
but
it's
there,
and
so
anyway,
totally
experimental.
But
you
can
like
I
said
it's
meant
to
be
as
simple
as
possible.
B
Give
me
the
actor
name
or
something
close
to
the
actor
name
and
then
I'm
going
to
show
you
every
every
type
of
communication
thing.
That's
going
back
and
forth
between
them
and
so,
like
I'm
I'm
able
to
do
this,
like
if
I
refresh
the
page,
we'll,
probably
see
all
the
HTTP
requests
for
the
assets
that
pop
up
and
then
like
the
KB
increment
yeah,
and
we
see
a
bunch
of
them.
So
we
see
like
okay,
like
I'm
from
this
HTTP
server,
here's
my
favicon!
B
You
know
that
I'm
getting
into
the
API
counter,
so
I'm
able
to
base
able
to
trace
all
the
different
requests
that
are
going
on,
so
the
idea
is
no
longer
do
you
have
to
sit
there
and
go
like
well.
What
is
my
actor
getting
her
like?
What's
going
across
the
wire?
This
automatically
goes
and
listens
to
every
single
topic
for
every
single
provider.
Your
thing
is
is
linked
to.
B
There
is
the
one
thing
that
we
can't
really
figure
out
for
it.
Right
now
is
actor
to
actor.
That's
one!
That's
a
little
bit
more
difficult
because
there's
no
linking
between
actors.
So
I
can't
like
say:
oh,
go!
Listen
on
this
topic
or
go!
Listen
on
this
thing.
B
We
might
add
that
in
the
future,
with
some
smarter
filtering
like
we
can
grab
like
any
actor
topic
and
then
filter
based
on
whether
it's
in
the
source
or
the
the
target
for
that
invocation,
so
actor
to
actor
won't
be
there,
but
it
will
Trace
pretty
much
everything
else
so
anyway,
that
is
wash
spy.
Any
questions.
A
It's
me
I'm,
not
audience
plan
I
I
am
actually
curious
and
I.
Think
I
can
see
it
here,
but
I
just
want
to
be
clear.
So
when
you
spy
on
an
actor,
it
looks
at
both
like
incoming
and
outbound
link,
definitions
and
I.
Think
I
can
see
HTTP
server
and
key
value
here,
but
like
so,
you
invoke
the
actor
with
HTTP
server,
and
so
you
can
see
that
incoming
invocation.
But
then
the
actor
itself,
like
that
webassembly
module,
sends
a
key
value
request
and
you
can
see
that.
B
A
So
that
that
operation
down
there
at
the
bottom
is
a
request
that
the
actor
itself
is
sending
right.
Yes,
because.
A
Cool-
and
are
you
doing
anything,
fancy
like
Russ
specific
in
here
or
is
this
just
like
wasmcloud
invocations
over
the
wire
so
like.
B
It's
it's
was
some
classifications
over
the
wire
that
I
capture
into
a
rust
stream.
This
is
entirely
reusable,
it's
part
of
washlibs.
So
if
you
want
to
do
your
own
spying,
you
can
actually
do
that
in
your
own
code,
but
yeah
this
will.
This
does
some
really
interesting
stuff,
if
you're
in
the
rest
and
ecosystem
with
30
transcode,
so
you
can
pull
it
back
between
two
different
protocols.
B
So
it's
pretty
awesome.
That
is
the
the
kind
of
like
only
wrestling
set
it.
It
was
just
more
just
making
sure
I
I
went
to
the
right
topics
subscribe
on
the
right
topics
and
then
listen
for
him.
A
B
B
Actually,
if
you
don't
mind
me
to
don't
mind
me,
tooting
was
on
cloud
torn
here,
because
we
are
in
the
Watson
Cloud
Community
call
the
this
is
where
wasn't:
Cloud
really
shines
as
being
a
little
bit
different
than
other
options
out
there,
because
you
can't
really
do
like
if
you're
gonna
be
tracing
like
this,
with
any
other
system
you're,
either
going
to
need
to
like
be
implementing
some
sort
of
like
Tracer
injector
type
of
thing,
which
we
still
have
tracing
they're
still
tracing
here
or
you're.
B
Gonna
have
to
like
capturing
actual
requests
and
going
through
here,
but
because,
like
we
control
the
protocol
and
we
control
everything,
that's
going
on
we're
able
to
inspect
all
this
stuff
for
you,
and
so
it's
a
great
debug
tool,
it's
even
great
debug
tool
for
for
wasn't
Cloud
operators,
those
who
do
who
actually
are
going
to
be
operating
this
in
production,
because
you
can
restrict
which
things
have
access
to
these
topics.
B
So
you
can
issue
creds
that
only
that
have
access
to
this
only
if
you're
like
an
admin.
So
it's
pretty
you
can
you
can
lock
it
down
pretty
good
if
you
want
to
so
it's
it's
a
great
debug
tool
for
local
Dev
and
also
for
actually
running
awesome
cloud.
B
Okay
and
then
Jordan
also
asked
a
question
around
deploying
laws
on
cloud
and
production.
That's
partially
related
to
this
I'm
guessing
but
the
whole.
The
whole
thing
there
is:
we
do
have
the
guide
for
it,
but
we
also
are
I'm
really
hoping
here
in
the
future.
We
can
actually
have
a
few
more
easy
to
deploy
guides
like
terraform
and
whatnot,
not
making
any
promises
yet,
but
that's
what
I'd
really
like
to
have.
So
it's
even
simpler
for
people
to
just
get
started.
B
That's
just
my
two
cents:
I'll
go
ahead
and
yeah
and
Kevin
also
brought
that
up.
That's
a
good!
That's
one!
Good
final
point:
before
I
stop
sharing
all
that
was
required.
Here
was
an
ass
connection.
Yeah
I'm
running
my
host
locally,
but
as
long
as
I
can
connect
to
the
Nats
cluster,
where
this
is
running,
I
can
spy
on
the
hosts.
I
don't
need
a
host
I.
Don't
need
to
do
anything
special
with
my
actors.
I,
don't
need
any
of
that.
B
A
I'm
going
to
put
you
a
little
bit
on
on
the
spot
here,
Taylor,
which
you
can
you
can
keep
sharing
or
not
so
the
wash
experimental
flag,
that's
a
little
from
what
I
can
gather.
It's
meant
for
more.
You
know
this
is
a
new
feature,
we're
just
trying
it
out
and
and
not
kind
of
committing
it
to
the
stable
API
that
we
try
to
you
know,
keep
with
with
all
wash
versions,
are
all
new
features.
Gonna
come
in
as
wash
experimental.
How
do
features
get
out
of
the
experimental
status?
A
B
The
idea
is,
if
it's
something
that
is
entirely
it
like
sorry
to
use
the
words
to
define
the
word
if
it's
an
experiment
right
like
I,
don't
know
if
this
is
a
good
idea
or
even
useful,
or
if
the
output
is
even
in
the
right
format
or
if
I
should
be
set
like
this
was
just
like:
hey
I
want
to
get
this
out
there.
This
is
one,
that's
actually
probably
gonna
graduate
from
being
experimental
fairly
quickly,
as
my
guess,
but
the
the
idea
is
just
saying
hey.
This
is
something
we
could
remove.
B
We
could
entirely
break
and
we
could
completely
change
how
it
works,
we're
offering
zero
guarantees,
but
we
want
to
get
it
in
front
of
you
because
we
consider
it
useful,
and
so
that's
where
the
experimental
comes
in.
That's
that's
essentially
why
we
have
that
so
there'll
be
a
couple
things
coming
out,
there's
another
one
I'm
working
on.
B
So
if
we
look
at
wash
something
I'm
looking
at
experimenting
with
today,
is
this
feature
right
here
being
able
to
just
like
capture
and
eventually
I
hope
to
replay
traffic,
but
like
being
able
to
capture
and
like
debug
something
for
those
who
are
Gamers?
It's
basically
like
being
able
to
like
press
a
button,
and
it
grabs
the
last
like
30
seconds
to
60
seconds
of
video
or
whatever
you
think
so
like.
Can
it
captures
the
past
for
you
and
then
you
can
save
that
clip.
B
This
is
the
same
thing
we
want
to
do,
but
with
with
all
these
implications
and
then
you'll
be
able
to
like
replay
it
with
the
with
the
like
wash
spy
type
thing
and
be
able
to
like
step
through
and
filter
is,
is
my
current
plan
so
we'll
go
through,
like
pointed
at
this,
like
essentially
core
dump
and
say
filtered
like
filter
by
actor
or
filter
by
provider
or
filter
by
actor
and
provider,
and
just
be
able
to
provide
some
basic
functionality
for
for
going
through
all
the
things
that
were
captured
over
the
past
hour
after
you,
like
you'd,
find
an
issue,
a
big
issue
that
happens,
and
you
know
everything
that
was
running
and
all
the
implications
that
it
just
run.
B
So
anyway.
That's
the
kind
of
thing
that
will
all
like
that's
very
experimental.
That
could
just
be
a
terrible
idea
and
or
just
not
be
used
or
really
not
be
useful,
and
so
that's
going
to
go
behind
an
experimental
flag
for
sure,
because
it
is
in
no
way
proven
out
or
considered
to
be
a
good
idea.
Yet.
A
I,
don't
know
how
this
specifically
works
in
the
CLI
I.
Guess,
since
you
used
an
environment
variable,
it
can't
be
a
feature
flag,
a
rust
cargo
feature
flag,
but
will
this
also
be
a
feature
flag
in
wash
lib
so
that
people
like
by
default
are
not
getting
the
experimental
stuff?
I,
don't
know
this
might
be
a
little
too
in
the
weeds
we
want
to
go.
We
don't
have
to
keep
going
into
it,
but
I'm
just
curious.
B
A
B
No,
it's
not
feature
flagged
on
the
lip
there.
We
could
probably
feature
flag
it
in
there
right
now
we're
playing
a
little
bit
more
in
loosey-goosey
with
washlet,
because
we're
really
the
only
ones
using
it
if
people
are
using
it.
Please
let
us
know
and
then
we'll
try
to
make
sure
we
feature
Flags.
You
know,
like
hey,
don't
touch
this
one
unless,
like
you
want
to
know
that
it
could
break
you
know,
that's
the
kind
of
thing
that
I
we
would
want
to
do,
but
it
is
a
little
bit
more
of
a.
B
It
is
a
little
bit
more
of
a
like
kind
of
just
out
there.
It's
there
in
watch
live
so
anyway.
I
think,
there's
some
interesting
discussion
going
on
around
like
Nats
are
back
in
that
setup,
so
yeah,
no,
it's
a
soapbox
I
get
that
so
we've
actually
been
trying
to
make
that
better.
There's
one
thing
we're
going
to
move
in
so
for
Jordan
for
those
who
who
are
not
who
are
in
the
like,
live
stream.
Jordan
was
asking
a
question
around
like
how
is
this
security
like?
B
How
can
we
lock
down
something
like
Washed
by
actually
believe
it
or
not,
and
the
Watson
Cloud
Docs.
B
We
have
inside
of
the
widam
section,
which
is
something
we're
going
to
we're,
going
to
move
some
of
this
content
out
to
the
main
page
of
the
main
like
running
Watson
Cloud
page,
that
like
we
have
because
credentials
are
important.
Credential
management
is
important
for
the
damn
stuff
as
well
and
right
here
we
have
a
whole
like
this
is
how
you
create
a
sample
account
end
users.
B
So
this
is
like
the
most
basic
thing
to
be
able
to
get
users
that
are
like
locked
down
to
work
with
withdam
and
only
like
credentials
that
are
only
for
Witham
and
interacting
with
the
lattice
and
credentials
that
can
be
used
for
your
hosts,
and
so
this
is
the
kind
of
thing
that
that
you
can
actually
look
for
and
I
will
send
this
out.
So
they
can.
This
can
be
put
into
the
various
chats
and
so
inside
of
here
you
can
actually
see
how
you
set
up
Nats
credentials.
B
B
But
that's
how
this
is
like
the
basic
basic
way
of
of
doing
it.
If
you're
gonna,
like
start
locking
things
down
for
real
when
you're
running
it
out
in
the
wild.
B
A
Speaking
of
autumn
I
would
love
to
use
it,
but
it's
been
as
an
alpha
release
for
a
while
and
as
if
it
could
just
stop
being
an
alpha
release.
Then
I
would
totally
use
it
in
my
project.
Could
we
well
Taylor?
What
is
this.
B
Yes,
so
in
case
you
didn't
see,
we
finally
got
with
m0.4.0
out.
Yes,
you
can
use
this.
Yes,
there
are
still
rough
edges
as
with
any
newer
software,
but
you
can
actually
do
this
now
before
we
continue
with
our
high
school
play
transitions
of
moving
from
topic
to
talk
topic
provided
by
Brooks.
B
We
do
have
these
all
listed
down
here
about
known
issues
and
missing
functionality,
so
there's
things
that
just
are
kind
of
a
little
bit
still
janky
and
rough,
but
like
the
the
core
functionality
is
fairly
well
tested.
We
have
a
full
e
to
e
test,
Suite
that
runs
on
this
now
and
you
can
like
you
can
actually
see
like
all
the
the
different
tests
we're
running,
but
it
makes
sure
we're
like
running
on
multiple
hosts
with
multiple
with
dams
and
so
we're
fairly.
B
Confident
at
this
point,
like
it's
not
just
gonna
break
on
you,
you
might
have
to
deal
with
the
some
of
these
rough
edges
that
we
have
listed
here,
but
like
it,
it
works
like
it
actually
does.
What
it's
supposed
to
do
we're
working
on
rolling
it
into
wash
0.18?
B
The
big
note
is
just
know
that
you
have
to
be
running
the
latest
version
of
the
host
the
0.63
chain,
essentially
because
we're
versions,
because
we
have
to
have
some
new
things
that
are
in
there,
that
we
actually
discovered
because
of
Woodham
and
and
those
bug
fixes,
went
back
into
the
host.
So.
A
B
Are
all
there?
We
have
issues
and
everything
in
there
too,
if
you're
interested
in
helping
out
some
of
these
are
definitely
open
for
the
the
taking.
It
is
very
it
it
there's
some
complexity
in
the
code,
I'm
I.
One
of
my
goals
is
to
add
an
architecture
diagram
around
the
code
itself,
no
matter
why
and
how
things
are
set
up,
but
I'll
get
to
that
in
the
next
couple
weeks,
I'm
just
trying
I'm
just
trying
to
get
these
features
out
for
people
to
use.
So
that's
all
there.
B
The
documentation
is
already
linked
in
the
chat
here
in
zoom
and
then
hopefully
link
that
to
other
people.
That
shows
you
how
you
can
run
it.
It
shows
you
the
whole
widam,
API
and
you're
able
to
interact
with
it
with
wash
here
soon
as
well.
So
anyway,
just
wanted
to
point
out
that
we
have
that
now.
0.4
is
out
we'll
continue,
releasing
adding
some
additional
changes,
fixing
some
things
and
please
let.
A
B
B
A
Nobody
can
see
outside
whether
it's
very
hazy
actually
air
quality
is
not
good,
but
let's
see
what
is
next
on
the
agenda,
so
I
believe
we're
going
to
be
talking
about
the
next
release
of
wash,
which
Taylor
you
actually
transitioned
to
pretty
well,
so
wash
0.18
is
going
to
be
coming
up
pretty
soon,
we've
got
a
couple
Alpha
releases
that
we've
been
testing
in
terms
of
deploying
Wood
Dam
0.4
alongside
the
latest
version
of
the
host,
which
is
version
63.1.
A
These
are
the
the
beam
burrito
releases.
Essentially
what
this
changes
and
and
we've
talked
about
it
in
previous
Community
calls,
but
it
changes
the
wasm
cloud
release
application
from
a
tarball
with
files
in
it
into
an
executable
that
extracts
its
own
to
our
balls.
Roman
has
put
a
lot
of
work
into
this
to
make
it
more
compatible
with
different
platforms.
A
You
can
actually
see
on
the
I
believe
it's
on
the
OTP
repo
I,
have
it
as
a
pinned
issue,
so
it
doesn't
get
marked
as
stale
in
terms
of
platform
support
where
we're
at
so
these
releases
are
going
to
be
and
I'll
zoom
in
a
bit.
They
don't
have
any
platform
dependencies
on
on
Mac
OS.
They
depend
on
CA
certificates
on
Ubuntu
Debian
and
then
on
the
Alpine
or
muscle
Linux
one.
It
does
depend
on
live
GCC,
but
we're
not
worried
about
that
for
now
and
again
fully
static
for
Windows.
A
So
for
you
you're
not
going
to
really
notice
a
difference
in
terms
of
moving
to
this
new
version,
but
it's
mostly
worth
talking
about
because
there
are.
It
is
going
to
be
a
change
that
when
you
supply
the
wasmcloud
version,
The
Wash
0
to
18,
it
has
to
be
version
63
or
newer
because
of
this
new
structure.
A
Additionally,
we're
going
to
be
flattening
some
of
the
CLI
commands
and
updating
the
top
level
help
text
for
wash.
So
if
you
take
a
look
in
RFC
538,
which
I've
linked
here
in
the
community
meeting,
this
was
an
RFC
that
I
put
together
around
reworking
the
structure
of
wash
commands
both
to
group
them
into
nice.
A
Easy
categories
to
understand
kind
of
what
you're
getting
into
when
you
hit
the
top
level
help
text
for
wash
I
find
this
really
useful
with
a
lot
of
go
clis
and
though
rust
doesn't
have
like
a
built-in
way
to
do
this
out
of
the
box.
It's
pretty
easy
to
do
it
kind
of
manually,
so
this
is
going
to
be
a
new
structure
for
the
topical
help
text.
A
It's
breaking
change,
I,
guess
but
I'm
sure
nobody
is
parsing
that
you
know
manually
and
additionally,
Victor
has
actually
put
in
a
lot
of
work
in
what
we've
called
an
effort
of
flattening
the
Washi
along.
A
So
a
lot
of
these
commands
that
were
linked
between
behind
many
different
sub
commands
like
watch,
control,
link,
put
between
an
actor
and
a
provider
or
wash
control,
stop
actor,
have
moved
into
wash
link
and
washed
up
same
thing
with
wash
ragged
push
and
pull
is
just
wash
push
and
pull
and
I
think
there
was
one
more
yeah
start.
A
It
does
the
same
thing,
so
you
can
kind
of
see
an
overview
of
what
this
looks
like
here
and
there's
actually
a
pull
request
out
right
now
that
Victor
put
out
this
morning,
which
were
he
kind
of
put
out
for
a
discussion.
But
this
is
kind
of
what
the
actual
top
level
text
is
going
to
look
like,
and
the
only
other
thing
that
I
want
to
point
out
here
is
that
I
know
I've
been
using
wash
well
yeah
I've
been
using
wash
since
version
one.
A
A
lot
of
us
have
been
using
wash
for
a
while,
so
changing
from
something
like
wash
control,
start
actor
to
wash
start
actor
and
then
eventually
something
like
wash
dark
and
then
the
reference
is
going
to
take
time,
and
even
though
we're
calling
this
a
breaking
change,
because
there's
new
top
level
commands
all
of
the
old
commands
will
continue
to
work.
So
your
all
of
your
scripts,
that
you
have
watch,
control,
start
watch,
control,
link
and
things
like
that.
Will
work
all
the
same
and
we're
just
putting
out
a
deprecation
message.
A
You
know
warning,
but
we
don't
really
plan
on
actually
deprecating
those
for
for
quite
a
while
I
kind
of
spitballed
when
we
call
Wash
1.0
is
a
good
time
to
actually
deprecate
those
commands,
but
anyways.
It's
it's
not
going
away
in
0
to
19.
You
know
0.20
or
anything
like
that.
A
So
I
really
wanted
to
just
take
part
of
this
community
called
to
talk
about
some
of
those
changes
that
we're
putting
in
wash
18
has
a
lot
of
things
that
it's
modifying,
but
from
like
user
and
developer
perspective,
it's
not
going
to
feel
very
different
in
in
terms
of
what
it
does
like
running.
A
Wash
up
is
going
to
launch
walls
and
cloud
and
and
that's
the
same
way
they
did
before
all
the
commands
are
going
to
work
the
same,
but
just
worth
calling
out
some
of
those
bigger
changes
and,
of
course,
we'll
get
those
release
notes
put
out
on
GitHub
and
then
potentially
on
the
on
the
website
as
well.
A
I
saw
a
good
bit
of
chat
in
well
chatter
in
the
chat.
I.
Don't
think
it
was
explicitly
related
to
this
part.
Anybody
have
any
questions
on
wash
0.18
release.
Some
of
the
new
features
coming
in
there.
A
Sweet
then,
the
last
thing
that
we
have
on
the
community
meeting
today
is
really
short,
but
really
sweet.
I
just
wanted
to
officially
announce
that
we
have
not
clicked
on
that.
Rfc
Watson
cloud
has
officially
started
the
process
for
applying
for
incubation
status
as
a
product
or
as
a
project.
A
How
convinced
we
are
that
we're
putting
out
a
a
stable
API
things
like
that,
and
so
this
is
a
pretty
big
move
for
wasn't
cloud
and
it's
a
really
really
exciting
one
in
terms
of
where
we
want
to
go
in
terms
of
stability
of
the
project.
I've
been
around
for
a
little
over
three
years
now,
and
so
we're
super
confident
and
in
making
this
application
and
there's
not
much
really
to
share
here
over
the
next
couple
of
weeks.
A
You
know
things
like
an
official
official
PR
from
a
cncf
incubating
sponsor
will
come
out
and
in
terms
of
tracking
our
status,
but
we're
pretty
confident
that
we've
met
the
guidelines
for
incubation
we've
been
putting
in
the
work
around
and
special
shout
out
to
both
Taylor
and
Bailey
for
putting
things
together
like
the
contributing
guide,
Community
guide,
the
governance
talking
about
how
org
maintainers
work
and
many
many
things
in
the
open
source
world
that
are
standardized
and
really
important
for
running
a
successful
organization.
A
So
that's
it
I,
actually
don't
have
any
links
or
anything
to
share,
but
it's
just
exciting
and
we
definitely
wanted
to.
Let
you
all
know
that.
That's
where
that's,
where
we're
at
so
all
fun,
stuff,
I,
guess
anybody
is
welcome
to
ask
questions
about
the
incubating
stage
for
for
wasm
cloud
and
they
just
pop
it
over
to
Taylor
anyways,
but
in
general,
I
think
this
is
a
good
time
to
start
kind
of
our
open
floor
time
before
wazzam
Cloud.
A
All
right,
anyone
else
have
any
last
last
minute,
topics
or
questions
they
wanted
to
talk
about.
A
Sweet
then
I
think
we.
This
will
be
a
quick
one.
Today
we
can
call
it
a
little
bit
early
I'll
go
ahead
and
cut
off
the
stream
thanks
everybody
for
tuning
in.