►
From YouTube: wasmCloud Community Meeting - 17 May 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
A
So
to
start,
my
demo
is
going
to
be
around
the
burrito
releases
that
we're
doing
with
wasmcloud
from
version
63
and
onwards
and
how
wash
supports
those
along
with
some
extra.
You
know
some
extra
little
goodies,
of
course,
and
then
we've
got
a
lot
of
discussion
time
for
and
we've
actually
renamed
this
RFC,
but
decoupling,
the
RF,
the
washboard
from
the
host
transitioning,
the
feature
Focus
to
rust,
and
then
the
stale
issue,
bot
that
came
out
of
a
couple
of
discussions
yesterday
in
the
in
the
waslam
cloud
slack,
actually
so
without
further
Ado.
A
So
I've
got
a
big
terminal
window
here
that
I'm
going
to
Crunch
down
a
little
bit
and
for
those
of
you
who
have
worked
with
wasmeplad
before
you
install
wash,
and
then
you
do
something
like
wash
up
in
order
to
start
naps
and
wasm
cloud
and
as
of
version
18,
which
is
in
Alpha,
Testing
right
now
will
also
start
a
lot
on
the
application
deployment
manager
and
when
you
run
wash
up
this
downloads,
all
those
utilities
on
your
local
system
to
the
wash
downloads
directory
and
then
starts
them.
A
So
this
demo
is
a
little
bit
special
because
I'm
not
just
showing
version
18..
This
is
actually
going
to
go
in
in
version
19,
but
this
is
starting
our
burrito
releases
instead
of
downloading
the
wasmcloud
tarball
and
then
unpacking
it
to
the
directory.
So
as
far
as
what
you're
going
to
have
to
care
about
as
a
developer,
it's
basically
nothing
the
difference
between
the
previous
wash
or
the
previous
wash
version,
and
this
version
with
wasm
Cloud
63
is
effectively
nothing.
When
you
run
wash
up.
A
It
starts
all
those
things
when
you
hit
Ctrl
C
or
you
run
in
the
background
and
then
run
wash
down.
It'll
stop
those
resources.
The
difference
is
under
the
wash
downloads
directory.
Now
everything
is
still
saved
by
a
version
for
the
host,
but
instead
of
seeing
the
bin
and
the
erlang
runtime
and
everything
you'll
see
that
this
is
just
a
single
binary
called
was
inside
hosts.
If
we
take
a
look
at
this,
it's
actually
a
single
executable,
there's
a
little
bit
of
special
things
going
on
with
the
executable
I'm,
pretty
sure.
A
Technically,
this
is
a
zig
binary
that
then
unpacks
the
wasm
cloud
host
to
a
directory,
a
library
directory
on
your
system
and
then
every
time
you
run
it
from
then
on
out.
This
will
fail
because
I'm
not
running
Nats,
you
can
just
execute
it
like
a
single
binary
and
so
I
really
want
to
shout
out
Roman.
Who
has
talked
about
this
in
a
couple
of
previous
Community
meetings
about
how
much
nicer
this
is
for
actually
running
the
wasum
cloud
application.
It's
a
single
binary.
A
If
you
take
a
look
at
the
actual
dependencies
locally,
there's
effectively,
nothing
otool
is
the
Mac
equivalent
of
ldd.
So
if
you
like,
take
a
look
at
this
on
Linux
we're
not
actually
dynamically
linking
to
openssl
anymore,
which
is
huge.
It's
going
to
it's
going
to
vastly
simplify,
deploying
to
different
Linux
targets.
It's
static
on
Windows
and
Mac
anyways
talking
a
lot
about
platform
support.
A
Really
what
you're
going
to
notice
is
that
this
will
just
work
a
lot
nicer
on
a
variety
of
platforms,
which
is
you
know
the
whole
benefit
to
this
whole
thing
called
webassembly
that
we're
trying
to
take
advantage
of
now.
I
wanted
to
also
shout
out
to
another
of
the
another
contributor
to
wasmcloud
Aishwarya,
who
put
in
a
PR
to
support
wash
up
starting.
Multiple
hosts
in
quick
succession
have
essentially
taken
that
work
and
combined
it
with
this
version.
63
PR,
because
burritos
make
it
a
little
nicer
for
us
to
be
able
to
start
multiple
hosts.
A
So
as
of
version
19
I
want
to
show
you
a
little
bit
of
how
this
might
look,
so
you
run
wash
up
put
in
the
background.
What
this
does
launches.
Nats
and
wasmcloud,
and
everything
we're
actually
now
saving
the
logs
to
the
the
name
wasmcloud
and
then
the
port
that
the
wasmcloud
dashboard
is
running
on.
If
we
run
that
again,
that
will
actually
see
that
you've
already
been
running,
Nats
and
and
wadham
and
find
the
next
open
port
for
the
Watson
Cloud
dashboard
to
run
on
and
then
save
those
logs
to
new
file.
A
You
can
continue
doing
this
to
your
Arts
content.
I
think
I
scan
up
to
Port
5000,
so
you
can
start
approximately
a
thousand
hosts
on
a
single
machine
if
you'd
really
like
to.
But
what
this
is
really
nice
for
is
just
starting
multiple
Watson
Cloud
hosts
in
quick
succession.
You
can
put
different
applications
on
different
hosts.
You
can
have
them
all
connected
to
to
each
other.
This
would
just
be
really
nice
for
if
you're
testing
out
a
couple
of
different
scenarios
in
wasmcloud
and
you
want
to
run
multiple
hosts
now.
A
What
also
comes
with
this
is
a
change
to
wash
down,
because
washdown
was
essentially
meant
to
be
the
counterpart
to
wash
up
is
like
hey.
You
know,
I
launched
some
resources
with
wash
up
now.
Please
turn
them
down.
Washdown
now
has
to
take
into
account
that
you
might
be
running
multiple
hosts
and
in
that
scenario,
what
we
do
is
we
ask
for
you
to
either
Supply
a
host
ID
or
use
the
dash
dash
all
flag
to
stop
all
running
posts.
A
So
if
you
do
wash
down-
and
you
stop
a
single
host,
that
will
send
a
request
over
the
control
interface
to
stop
that
host.
But
then,
since
there
are
other
hosts
running
still
doing
their
thing,
we're
going
to
exit
a
little
quicker
to
avoid
stopping
Nats
or
watam
so
that
you
can
still
interact
with
those
currently
running
hosts.
A
Now
the
way
that
this
works
is,
if
you
wanted
to
stop
the
rest
of
them,
you
can
do
washdown
dash
dash.
All
this
will
send
a
stop
host
request
to
every
single
host,
that's
running
and
then
close
down,
wadham
and
Nats
after
that.
A
A
One
should
be
able
to
finalize
version
18
here
in
the
next
couple
of
days
that
one
is
out
as
a
that
one's
out
as
an
alpha
release
now,
but
I'd
like
to
release
that
with
a
newer,
maybe
the
full
0.4
release
of
Autumn
and
then
this
breaking
change
can
go
in
separately,
I'm
trying
to
avoid
you
know
as
a
general
rule
packaging
too
many
crazy
things
into
a
single
release.
A
So
does
anybody
have
any
questions
as
to
you
know
the
new
burrito
releases,
the
way
that
wash
up
and
wash
down
will
work.
A
All
right
cool
well,
this
is
a
draft
PR
out
in
the
wash
repository
now
I'm
going
to
be
setting
that
up
is
ready
for
review.
I've
got
all
of
the
tests
passing
locally,
but
just
going
to
be
kind
of
coordinating
some
of
those
releases
so
keep
an
eye
out
for
that.
I'll,
of
course,
do
announcements
in
the
waslam
cloud
slack
and
everything
as
we
release
those
but
yeah.
Looking
forward
to
you
all
trying
it
out.
A
Alrighty
now,
if
we
go
back
to
the
right
sneeze,
if
we
go
back
to
the
agenda
next
thing
on
the
list
is
discussing
this
RFC
for
and
I
said,
I
renamed
it
we'll
change
it
in
the
notes
for
for
decoupling,
the
washboard
from
the
host
and
I
won't
give
too
much
preface
because
I
think
Kevin
is
here,
and
probably
you
know,
as
the
author
be
better
to
talk
a
little
bit
more
about
the
the
background,
motivation
and
kind
of
a
summary
of
this
RFC
Kevin.
B
All
right
so
I'll
try
and
keep
the
the
summary
short.
The
the
ROC
itself
goes
into
quite
a
bit
of
detail
about
the
motivation
and
why
we
want
to
do
it,
but
the
the
main
reason
is
that
the
the
washboard
is
specifically
designed
for
developers
to
use
as
a
tool
for
manipulating
the
lattice.
It's
basically
a
a
lattice
control,
client
and
the
the
problem
is
that
you
have
to
be
running
a
local
host
in
order
to
access
the
washboard
functionality,
and
that's
not
quite
the
the
kind
of
distributed
easy
to
use
tooling.
B
That
we
wanted
to
have.
What
we
really
want
is
to
be
able
to
manipulate
a
lattice
the
same
way
you
can
with
wash
but
using
the
washboard
up,
or
you
know,
whatever
we
end
up,
calling
it
the
washboard
application.
So
I
want
to
be
able
to
launch
this
thing
from
a
machine
that
may
not
even
have
washing
the
the
Muslim
Cloud
host
installed
on
it
and
we
go
through
a
number
of
alternatives,
for
you
know
different
options
that
we
have
for
building
a
decoupled
washboard.
B
There
are
some
that
are
kind
of
straightforward,
like
you
know,
using
go
or
rust
to
embed
a
react
application.
B
B
And
then
what
Bailey
was
talking
about
is
I
did
a
little
bit
of
mad
sciencing
over
the
weekend
to
verify
that
I
can
use
flutter
and
dart
to
talk
to
Nets,
and
not
only
can
I
do
it
over
websockets,
but
I
can
do
it
over
regular
Nats
TCP
as
well,
and
it
will
actually
choose
whether
it's
going
to
use
websockets
or
TCP
based
on
what
environment
or
what
platform
you've
targeted.
B
So
pretty
amazing
stuff
there
yeah
one
of
the
other
options
was
to
use
you,
which
is
another
rust,
front-end
development
framework
that
uses
webassembly.
B
If
there
are
other
options
that
we
didn't
enumerate,
there
feel
free
to
I.
Guess
just
add
a
comment,
since
this
isn't
technically
a
PR
yeah
I,
think
that
covers
most
of
it.
C
Hey
Kevin:
do
you
want
to
talk
through
versus
like
creating
a
static
application
like
a
react,
HTML
thing.
B
It
yeah
the
pros
and
cons
they're
kind
of
listed
in
there.
It
just
may
not
be
called
out
as
part
of
like
static
app
versus
non
but
yeah
one
of
the
problems,
one
of
the
potential
downsides
to
building
an
external
washboard
as
a
web
application
is
that
it
becomes
a
little
bit
more
difficult
to
deploy.
B
Having
to
do
things
like
create
a
rank,
react
application
and
then
shoehorn
it
into
a
binary
like
a
go
or
a
rust.
Those
are
all
things
that
are
pretty
high.
Friction
I've
been
down
that
road
before
and
it
looks
easy
when
you
start,
but
it
ends
up
being
a
dumpster
fire
when
you
try
and
get
it
working
for
real
yeah
Jordan.
Embedding
view
is
pretty
much
the
same
as
embedding
reacts.
It's
the
embedding
part.
B
That's
that's
annoying,
but
you
know
having
a
static
application
means
that
you
know
all
the
good
stuff
that
Brooks
just
showed
where
you
know
you've
got
these
single
single
binaries
that'll
work
anywhere.
If
we
have
a
static
application,
that's
a
single
binary,
that'll
work
anywhere.
B
B
If
we
did
something
like
flutter,
where
you
automatically
gain
the
ability
to
Target
mobile
devices
like
Android
and
iOS,
and
and
things
like
that
and
like
I
said,
I
I
expected
that
to
be
hard,
but
it
wasn't,
and
I
was
able
to
get
that
stuff
to
use
to
communicate
with
the
Nance
Leaf
node
that
wash
up
starts
without
any
modification.
A
So
Kevin,
oh
Bailey,
are
you
talking
you're
muted,
but
you
can
okay,
Kevin
I.
You
know
kind
of
taking
a
look
at
this
PR.
It
seems,
like
the
you
know,
effectively.
The
requirement
for
a
Watson
Cloud
dashboard
is
to
be
a
user
interface
and
be
able
to
communicate
with
naps,
and
once
you
have
that
it
can
issue
control
on
our
face
commands,
it
can
listen
to
events
to
update
state
or
you
know
otherwise,
query
lattice
for
information.
A
B
Protocol
I,
believe
we've
got
that
at
least
partially
documented
out
on
the
ones
and
Cloud
site,
but
what
it
really
ends
up
being
is
that
you
need
to
make
requests
sending
Json
payloads
over
Nets,
and
you
can
do
that
either
through
the
regular
Nats
TCP
protocol
or
if
you,
if
you
have
control
over
it,
you
can
have
Matt
start
up
a
websocket
endpoint
and
you
can
talk
to
that
as
well.
The
difficulty
with
the
websocket
endpoint
is
that
it's
still
it's
still
raw
and
unvarnished.
B
So
when
you
talk
to
the
websocket
endpoint
on
Nets
you're,
not
talking
high-level
stuff,
like
you,
don't
make
a
request
to
the
websocket
endpoint,
you
actually
send
the
Nats
protocol
message
across
on
that
endpoint
and
then
you
will
wait
more
and
that's
vertical.
Reply
is
on
the
same
thing.
So
it's
more
like
you've,
just
swapped
websockets
for
TCP,
and
you
still
have
to
re-implement
the
protocol
on
top.
B
A
Makes
sense,
I
feel
a
general
poll
towards
a
couple
of
a
couple
of
different
possible
Alternatives,
I
I.
Don't
really
feel
the
pull
to
keep
it
in
and
I'm
just
going
to
State
some
opinions,
and
then
we
can
talk
about
it
and
go
from
there.
I
I
don't
really
feel
the
desire
to
take
like
a
to
take
like
the
the
Phoenix
app
and
and
separate
it,
and
then
bundle
and
release
it.
That
seems
to
bring
on
a
lot
of
the
portability
that
OTP.
A
You
know
some
of
the
some
of
the
things
that
are
downsides.
I
do
kind
of
want
I
kind
of
want
it
to
just
be
like
a
regular
like
JavaScript,
HTML,
CSS
front
end
and
like
no
external
goodies,
I
mean
like
whether
it's
react
or
view
just
to
make
things
a
little
easier
to
manage.
State
and
stuff
that's
cool
but
like
doing
that
seems
like
it
would
give
us
the
benefit
right
away
of
like
we
could
take
advantage
of
tooling
around
Distributing
web
assets.
A
A
If
we
just
have
a
you
know,
if
we
have
a
table,
that's
misaligned
or
something
people
who
know
nothing
about
rust
or
the
underlying
things
of
walls
and
Cloud
could
come
in
and
help
us
out
with
some
CSS
stuff,
like
that.
A
I
think
that
that,
on
a
first
glance
seems
like
the
my
favorite
option,
although
I
selfishly
of
course
want
to
be
able
to
play
with
flutter
and
would
probably
lean
more
in
that
direction.
If
we
saw
a
future
for
the
Watson
Cloud
dashboard
to
be
on
a
a
really
wide
variety
of
of
screens,
so
I
set
a
lot
of
said
a
lot
of
things
there,
but
Kevin.
That's
how
you
raise
your
hand.
So
let
you
go.
B
Yeah,
so
for
me
personally,
there
are
a
couple
of
things
that
I
would
like
to
make
either
easy
or
default,
so
it
should
be
super
easy
to
distribute
and
I.
Don't
ever
consider
things
like
JavaScript
apps,
easily
distributed
I
know
there
are
bundling
tools
and
so
on,
but
it's
still
messy.
You
still
end
up
with
a
giant
pile
of
node
module
files.
B
It's
possible
that
that
just
triggers
my
own
frustration,
I
know
other
people
don't
mind
the
node
module
stuff,
but
I
like
I,
like
the
Simplicity
of
a
single
binary
I,
don't
really
care
what
the
binary
is.
But
I
do
like
the
the
ease
of
just
having
a
single
binary.
B
B
The
other
thing
that
Lachlan
brought
up
is
that
one
of
the
things
that
I
think
should
be
a
requirement
that
I
didn't
really
include
in
the
RFC
is
Patrick.
The
single
binary
with
embedded
web
assets
is
like
three
of
the
five
options,
one
of
the
things
that
and
now
I've
lost
my
train
of
thought
here.
C
B
Yeah
so
there's
the
the
One
requirement
that
that
I
think
I
need
to
go
back
and
modify
the
RFC,
because
I
think
it
should
be.
There
is
I
want
to
be
able
to
type
wash
UI
and
have
it
bring
up
whatever
this
happens
to
be
and
message.
So
that
should
be
super
easy
to
do
and
wash
UI
should
go
get
it
and
we
should
be
able
to
update
it
easily
and
things
like
that,
but
I
should
be
what
I
want
for
requirements
are.
B
I
should
have
no
big
giant
pile
of
dependencies
to
manage
for
it,
and
it
should
be
able
to
talk
to
Nets,
either
through
regular
Nets
or
through
websockets,
and
if
we're
talking
preferences
I
think
I
would
prefer
to
go
with
something
like
a
static
app
like
flutter.
Just
for
the
reason
that
we
do
get
the
the
single
freestanding
binary
for
any
of
the
platforms,
and
you
know
we
also
gain
the
future
potential
to
put
it
on
different
screens.
B
C
Okay,
I'm
gonna,
add
I,
took
notes
for
all
of
this.
Thank
you,
Kevin
I'm,
going
to
add
it
to
as
a
comment
in
the
issue
and
Jordan
or
Justin
anybody.
Actually
that's
got
experience
with
any
of
these
options,
especially
you
Jordan,
because
you've
done
some
experimentation
already
and
you
probably
have
a
good
idea
of
what
it
takes
for
the
websocket
option.
C
If
you
could
drop
any
information,
you
have
to
help
us
make
the
right
decision.
It
would
be
awesome.
Oh
Liam,
you
have
your
hand
raised.
A
Okay,
cool
well
I
know
that
I
I've
got
a
couple
of
notes
here
that
that
I'll
be
putting
in
the
in
the
community
call
notes,
but
just
as
a
takeaway
I
I'm,
probably
gonna
I'll
leave
a
PR
PR
a
comment
on
the
issue
around.
A
You
know
kind
of
my
desire
to
have
something:
that's
really
easy
to
contribute
to
and
just
people
anybody
can
come
in
and
and
kind
of
make
little
fixes
and
Kevin
you're
you're
too
proposed
requirements
about
being
able
to
run
wash
UI
to
to
be
able
to
start
this.
A
Maybe
this
even
comes
up
when
you
run
wash
up
right
and-
and
so
you
kind
of
get
the
whole
experience
in
the
dashboard,
as
you
did
before,
and
the
other
requirement
that
you
should
be
able
to
run
this
on
a
system
that
that
does
not
have
wash
so.
A
You
know
you
could
kind
of
hook
into
hook
into
the
the
lattice
without
having
the
the
tooling
installed
there
and
the
strong
preference
to
have
something
that
can
compile
down
to
a
single
freestanding
binary
that
doesn't,
you
know,
doesn't
have
platform
dependencies
that
we
can
distribute
around
it
all.
It
all
sounds
sounds
really
good.
I
think
we're
prioritizing
the
right
right
things
around
packaging.
This
thing
up.
A
There's
a
little
bit
of
a
little
bit
of
chatter
in
the
chat
I
can
I
can
certainly
see
us,
in
my
opinion,
I
kind
of
feel
like
the
two
things
that
we're
going
to
decide
between
is
using
straight
up,
JavaScript
and
some
common
framework
and
and
writing
the
dashboard
and
that
or
using
flutter
because
of
how
cool
it
is,
and
it's
just
an
observation.
I
I,
don't
know
if
that's
quite
fair
to
call
at
this
point.
Kevin.
B
Yeah
I
just
want
to
point
out
that
the
reason
for
having
flutter
on
this
in
the
in
the
options
list
isn't
because
it's
cool
it's
while
some
of
us
may
not
be
as
familiar
with
flutter
as
we
are
with
things
like
rust,
flutter,
it's
it's
by
now.
B
It's
in
the
boring
category
already
and
there
are
I
I
was
trying
to
type
it
in
the
chat.
But
there
are
a
ridiculous
amount
of
flutter
developers
out
there
that
I,
just
I
I
had
no
idea
that
Community
was
so
large,
but,
like
I
said,
the
main
reason
why
it's
on
that
list
is
because
it's
cross-platform
it
produces
a
single,
freestanding
binary.
A
A
All
right
well
we're
going
to
jump
from
RFC
to
RFC
the
next
one
that
we
really
wanted
to
talk
about
today.
A
Kevin
also
wrote
this:
one
up
is
around
transitioning
the
feature
Focus
to
rust
when
it
comes
to
writing
new
Lawson
Cloud
features,
and
there
there's
a
this
one
is
is
completely
you
know,
just
like
all
the
other
ones
completely
worth
reading
through
the
rationale
and
the
the
rationale
behind
it
is
important
and
the
retrospective
around
the
last
two
years
of
working
on
wasmcloud
is
you
know,
I
I've
been
working
on
it
for
the
last
two
years
and
I
couldn't
have
put
it
any
better.
A
This
is
a
wonderful
summary
of
what
we've
worked
on
and
the
things
that
we've
experienced
working
with
Elixir
and
OTP,
and
some
of
you
may
know
the
the
effort
that
we've
been
putting
in
around
taking
some
of
these
runtime
elements
and
pulling
them
into
the
rust
run
time,
which
is
a
little
lower
level
than
a
full
wasn't
Cloud
runtime
But.
A
It
includes
like
wrapping,
wasn't
time,
The
Primitives
of
starting
and
stopping
webassembly
actors
and
I
think
the
best
thing
to
kind
of
leave
up
on
the
screen
as
I
hand
it
over
to
Kevin.
Is
this
kind
of
this
this
graph
of
essentially
what
we're
planning
on
doing
over
time
when
it
comes
to
maintaining
and
adding
new
features
to
our
our
different
various
runtimes
Kevin?
Would
you
like
to
say
a
little
bit
more?
There.
B
Sure
the
the
super
short
version
is
that
not
too
long
ago,
the
OTP
host
started
talking
to
a
new
rust
crate
underneath
for
its
for
its
web
assembly
or
on
time.
At
that
time,
we
were
able
to
switch
from
using
wazmer
as
the
low-level
engine
to
wasm
time,
and
that
gave
us
immediate
access
to
things
like
the
the
bleeding
edge
version
and
support
for
experimental
components,
and
things
like
that.
So
that
was
a
win-win
all
around
and
the
as
the
the
chart
shows
here.
B
Basically
we're
planning
on
investing
all
of
our
future
features,
time
in
the
rust,
crate
and
I
think
in
the
RMC
it's
put
in
there
somewhere.
But
the
order
of
priority
is
if
we
can
put
it
in
the
reusable
rust
crate.
We
will,
if
we
can
put
it
in
the
rust
host,
we
will
and
then,
if
it
needs
to
be
something
that
only
exists
in
the
OTP
host.
We
will
do
that
in
order
for
things
like
bug,
fixes
and
backwards.
B
Compatibility
and
things
like
that,
but
so
put
another
way,
is
that
the
OTP
host
isn't
deprecated,
but
it
is
on
the
road
to
deprecation.
It's
still.
The
host
that
you
should
be
using
it's
still
a
production
grade,
ready
to
use
hosts
that
you
know
cosmonic
is
using
for
all
of
its
backend.
B
Basically,
what
will
happen
is
at
some
point.
The
rust
host
will
reach
feature
parity
with
the
OTP
host,
and
when
that
happens,
that's
that's
likely
when
we
will
efficiently
declare
the
OTP
host
deprecated,
but
we've
got
some
work
to
do
to
bring
the
rest
hope,
Russ
host
to
feature
parody.
A
A
One
thing
that
I
that
I
want
to
mention
when
we
talk
about
different
wasm,
Cloud,
hosts
or
or
what
technology
we're
going
to
be
building
them
in
especially
around
this
compatibility
note,
is
that
the
the
goal
for
developers
of
wasm
cloud
is
to
not
care
about
what
actual
host
is
running,
their
business
logic,
whether
it's
running
in
an
OTP
host
or
rust,
host
or
a
browser
host,
the
portability
that
you
get
with
webassembly
and
the
whole
point
around.
A
Development
I
think
this
kind
of
order
list
here
is
really
important
and
the
the
bottom
line
is
that
you,
as
a
logical
Cloud
developer,
are,
will
be
able
to
swap
out
an
underlying
host
without
actually
caring
about
what
technology
it's
it's
written
in,
and
this
RFC
talks
more
and
more
about
the
benefits
of
the
different
Technologies,
but
I
think
it
was
I.
Just
think.
It's
important
to
to
point
that
out
as
an
end
user
perspective.
A
I
think
now
would
be
a
good
time
to
open
the
floor.
Does
anybody
have
any
questions,
especially
for
for
Kevin,
on
this
RFC.
A
That's
my
zoom
window
there
all
right
sounds
good
well.
Thank
you.
Thank
you.
Kevin,
for
for
both
of
those
rfcs
and
for
detailing
both
of
them
in
the
in
the
conversation
is
really
great,
I.
Think
now
we
can
move
on
to
our
last
agenda
item
of
today,
which
is
just
around
something
that
we
had
been
something
we've
been
talking
about
for
a
little
bit
in
the
wasm
cloud
across
the
entire
wasp
Cloud
at
work,
around
issue
and
PR
management.
A
There
has
been,
there
have
been
issues
and
PRS
that
have
sat
out
there
for
a
little
while
whether
we're
waiting
on
a
fix
from
someone
or
you
know
kind
of
temporarily
shelved
it
for
for
other
priorities,
and
there
are
a
lot
of
repositories
under
the
Watson
Cloud
organization.
We
have
a
separation
for
a
couple
of
our
different
key
aspects
of
our
project
and
something
that
you
know
sometimes
I
I
go
through
a
little
bit
of
a
mood.
A
I
was
doing
a
little
spring
cleaning
the
other
day
where
you
know
I
was
going
through
some
issues
that
were
maybe
you
know
a
year
or
two
old
and
they
didn't
apply
anymore,
or
they
were
something
that
has
been
you
know,
kind
of
since
then
fixed
and
someone
in
the
community
I
can't
remember
if
it
was
was
Conor
or
someone
else.
A
Many
other
orgs
and
open
source
use
it
and
that's
the
stale,
bot
and
so
I
wanted
to
bring
up
just
as
a
point
of
discussion
and
to
let
people
know
that
we've
put
this
across
a
lot
of
our
different
key
repos
in
wasm
Cloud
now
so
looking
at
this
actual
manifest
and
if
you're
curious,
if
you're
working
in
open
source
community-
and
you
want
to
use
this
I
just
installed
it
into
the
wasmcloud.org
from
the
GitHub
Marketplace,
it's
really
easy.
Essentially
we
have
this
manifest
in
a
lot
of
our
different
repositories.
A
Now
that
when
an
issue
or
a
request
has
been
open
for
over
two
months
and
no
activity
has
happened
in
there,
meaning
no
comments,
no
additional
commits,
then
the
stale
issue,
bot
kind
of
goes
through
marks
it
as
stale
and
then
we'll
wait.
Another
seven
days
before
closing
the
issue.
We
have
a
couple
of
labels
that
are
exempt
for
this.
If
we've
planned
it
for
the
road
map
or
if
we've
pinned
it
intentionally,
then
it
won't
be
cleaned
up
and
then
security
fixes
will
not
be
automatically
or
security.
Things
will
not
be
automatically
closed.
A
This
is
the
full
implementation,
just
in
case
anyone
else
is
curious,
but
what
this
actually
looks
like
I
put
this
into
the
watsonpod
was
impod
repo
yesterday
and
there
was
a
PR
or
an
issue
that
Roman
put
in
I
guess
it
was
a
like
right
on
the
dot
60
days
ago
and
the
stale,
as
you
bought
kind
of,
came
in
and
said:
hey
we've
been
marking
this.
A
We
marked
this
as
stale
because
there
hasn't
been
recent
activity
and
then
added
the
won't
fix
label,
and
this
is
why
I
thought
it
was
a
little
too
aggressive
to
say,
won't
fix
because
we're
going
to
fix
this
one,
so
I
change
it
to
stale
instead,
and
you
can
see
that
this
will
kind
of
work
here.
We
did
the
same
thing
with
this
RFC
around
link
management
and
I.
A
Put
in
a
comment
this
morning
saying
you
know
essentially,
we've
started
addressing
this,
but
we
we're
going
to
need
to
prioritize
the
second
half
of
this
RFC.
A
That's
just
something!
That's
automated!
That's
going
to
happen
after
a
certain
amount
of
time
since
we
just
merged
it
in
I
can
see
we're
probably
going
to
get
a
lot
of
them
marked
as
stale
over
the
coming
days
as
I.
Guess
it's
a
batch
job
I
don't
actually
know
how
it
works,
but
it
takes.
You
know
a
couple
of
hours
to
actually
scan
through
the
issues
so
I'm
going
to
be
going
through
those
and
making
sure
that
they're
appropriately
marked
as
as
we
go
through,
but
just
a
heads
up.
A
If
you're,
if
your
issue
gets
marked
as
stale,
please
feel
free
to
just
take
that
as
a
gentle
encouragement
to
improve
you
know,
continue
activity
on
that
and
I
think
this
is
going
to
be
really
helpful
for
us
as
maintainers
to
make
sure
that
we
don't
have
any
too
many
outstanding
too
many
outstanding
issues
and
that
we're
properly
prioritizing
the
work
that
we're
doing
in
the
open
source.
A
I
know
there's
a
lot
of
talking,
and
this
isn't
it's
not
really
too
much
to
that
one.
But
does
anybody
have
any
any
questions
or
I
I
know
that
we
went
kind
of
back
and
forth
in
slack
around
the
amount
of
time
that
we
want
to
leave
for
issues
to
go
stale
and
how
long
to
close
them
afterwards
happy
to
discuss
that
as
well.
C
C
Maybe
it
wasn't
Cloud
size,
maybe
even
bigger
one
thing:
I
I
really
enjoyed
working
in
6cli
is
when
we
had
bug
scrub
and
Eddie
runs
that
bi-weekly
and
it's
just
where
a
couple
of
the
maintainers
get
together
and
We've
run
through
all
of
the
issues
created
for
like
Cube,
cuddle
and
customize
and
other
places,
and
it
was
pretty
cool
because
you
know
we
were
able
to
basically
say
all
right,
I'm
on
Windows
you're
on
a
Mac
like.
Can
we
wrap
this
thing?
C
Real,
quick,
yes
or
no,
and
if
none
of
us
could
wrap
it,
then
you
can
immediately
be
like
hey.
I
tried
the
latest
version,
because
you
know
it's
not
working
and
it
was
nice
because
you
got
good
feedback
back
to
people,
but
that
was
necessary
because
obviously
keep
cuttle
has
a
lot
of
users
and
a
lot
of
issues
get
filed.
A
Well,
if
anybody,
if
anybody
has
experience
with
working
this
in
a
in
a
bigger
organization
or
over
time
and
and
wants
to
give
us
feedback
the
boss,
Club
slack,
is
always
open.
You
can
find
a
link
to
the
Watson
Cloud
slack,
especially
if
you're
tuning
in
on
one
of
our
various
streaming
platforms
on
the
bottom
of
the
watsoncloud.com
site.
So
please
feel
free
to
come
over
hang
out
and
give
us
your
thoughts.
A
Today
we
had
some
really
really
good
discussion
around
the
rfcs
that
are
out
and
I
was
really
happy
to
show
you
the
little
demo
of
doing
a
bunch
of
wash-ups
and
wash
downs
and
things
I
think
this
is
a
great
time
for
just
general
discussion
around
around
the
waslam
cloud
Community
or
things
in
the
broader
webassembly
ecosystem
I
feel
like
I,
usually
look
to
Bailey
for
updates
around
the
you
know,
wozzi
component
model
by
code
Alliance
all
those
things,
but
this
is
just
general
free
time.
A
By
a
group
today,
all
right
friends,
well,
then
I
think
that
we'll
call
it
for
this
community
meeting.
I'm
gonna
hang
out
on
the
call
afterwards
if
anybody
wants
to
continue
to
chat,
but
otherwise.
Thank
you
so
much
for
tuning
in
and
we'll
see
you
next
week.