►
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 a rapid feedback loop.
https://crates.io/search?q=wasmCloud
https://packagecloud.io/wasmcloud/core
#wasm #github #community #node #js #compiler #compile #browser #cloud #computing #programming #development #software #inspect #data #application #contracts #microsoft #archive #metrics #oss #opensource #wasmcloud #webassembly
A
Okay,
everybody
welcome
to
the
watson
club
community
meeting
for
february
the
10th
2021
wasn't
cloud
is
working
to
simplify
event-driven
distributed
development.
I
don't
think
we
have
any
new
members
today.
So
we'll
turn
it
right
over
to
bill
for
his
a
quick
walk
through
on
all
the
new
ci
cd
stuff,
so
bill
I'll.
Give
you
the
ability
to
share
your
screen.
I
don't
know
if
you
thank
you
walk
through
or
not.
Yeah
sounds
good.
A
B
Am
running
on
linux,
so
you
never
know
cool
so
yeah,
so
actor
interfaces
is
something
we've
spent
a
good
deal
of
time
on
automating
this
week,
so
I
mean
just
kind
of
walk
you
through,
for
example,
we
have
actor
core
underneath
actor
core.
We
have
each
language
represented,
so
obviously
rust
and
with
all
of
these
we
have
added
github
workflows.
B
So
if
you
check
into
main
on
this
repository,
it's
going
to
run
through
some
basic,
you
know:
cargo,
build
cargo
test
format,
make
sure
clippy's
happy
just
to
actually
get
that
you
know
committed
in
and
then
when
we
tag
specific
tags.
So
it's
basically
per
interface.
It's
basically
the
name
dash
v
in
the
version
when
you
set
that
tag,
it's
actually
gonna
go
through
and
do
the
release.
So
this
will
create
the
github
release.
We'll
then
create
the
cargo
push
that
up
to
create
scio
and
also
for
this
one.
B
We
have
assembly
scripts,
so
that
is
going
up
to
npm,
and
so
that's
pretty
much
the
workflow
for
all
of
them.
It
should
be
pretty
easy
to
add
actor
interfaces
as
we
go
along.
This
is
pretty
much
a
template
and
you
can
change
the
the
name
of
the
working
directory
and
the
tag,
and
obviously
the
name
and
just
for
an
example.
B
So
that's
the
crates
that
I
o
russ
section
and
then
it's
pretty
much
the
same
for
npm.
If
my
browser
will
let
me
so,
you
can
see
where
these
are
a
little
old.
The
npm
stuff
was
just
added
this
morning,
so
those
get
released
before
the
end
of
the
day.
But
it's
pretty
much
the
same
thing.
We
have
a
wasm
cloud
organization.
I
can
link
this
in
the
wasm
cloud
chat
and
so
all
of
our
assembly
scripts
packages
will
be
located
here.
B
C
B
C
I
was
just
going
to
make
a
couple
of
quick
comments.
I've
been
trying
to
keep
up
with
that
checklist
in
the
wasm
cloud
channel,
which
is
pretty
much
like
the
remaining
work
that
we
have
on
external
dependencies
like
outside,
of
the
wasm
cloud
core
project,
our
product
and-
and
it's
going
great,
I
mean
all
of
our
actor
interfaces
are-
are
published
to
crates.I
o.
Now
we
have
two
more
that
we
need
for
tiny
go
to
be
complete
there
for
our
capability
providers.
C
We
I
wanted
to
make
a
quick
comment
that
we've
set
ourselves
to
kind
of
a
rough
standard.
To
start
with
this
release,
which
is
to
release
everything
with
cicd,
which
makes
it
take
a
little
bit
longer
than
if
we
were
releasing
individually.
But
what's
awesome
about
this
is
any
future.
Release
is
as
simple
as
bumping
a
version
and
then
pushing
a
github
release.
So
we
like
put
in
the
work
in
the
beginning
and
now
for
any
future
releases,
is
going
to
be
painless
and
and
simple
and
tested.
A
It's
great,
and
it
did
anybody,
have
any
challenges
on
the
naming
convention.
We
seem
to
kind
of
adopt
there
where,
in
the
you
know,
folder
structures.
You
know
we're
not
repeating
wasm
cloud,
but
it
like
creates
that
io.
We
thought
we
should
tag
everything
all
out.
You
know
with
wasn't
cloud
at
first.
Did
that
make
sense
to
everybody
feedback,
wise
yeah,
that
makes
sense.
C
A
C
A
Okay,
that's
awesome,
I
feel,
like
you've
got
a
little
bit
of
color
there
in
your
head.
I
don't
know
if
it
would,
if,
ultimately,
you
know,
you're
just
gonna
grind
them
all
out,
which
is,
I
feel
like
what's
been
happening,
or
maybe
a
little
bit
of
that
color
might
help
someone
else
pick
up
if
you
just
put
some
like
a
comma
and
then
what's
remaining
on
those,
but
thank
you
so
much
brooks.
A
Okay,
awesome,
so
real,
quick,
I'm
gonna
go
ahead
and
just
share
there's
a
few
events.
You
should
probably
take
action
on
today,
one
you
should
probably
take
action
on
today
and
that's
the
early
bird
kubecon
and
wasm
day
registration
just
to
call
out
that
through
the
sunday
valentine's
day,
there's
a
special
discount
early
bird
registration.
That's
a
significant
discount
for
the
online
conference.
We
we
are.
There
is
a
plan
for
kubecon
us
to
have
an
in-person
component.
A
Is
the
sort
of
you
know
rough
draft
at
the
moment?
So
you
know
you
know
we're
already
kind
of
planning
and
working
out
from
there.
The
second
thing
to
take
action
on
is
the
cfp
for
cloud
native
wasm
day
is
open.
So
if
you
would
like
to
submit-
or
if
you
have
a
project
that
you're
excited
about,
I
encourage
you
to
go
ahead
and
submit
kevin
ralph,
and
I
are
on
the
process
committee
for
that.
A
So
we're
obviously
trying
to
make
sure
that
we
help
support
a
broad
and
inclusive
community
of
people
that
are
excited
about
cloud
native
stuff,
and
I
I
fully
hope
to
see
you
know
some
crosslit
stuff
and
a
few
other
things
on
the
on
the
agenda.
The
web
assembly
summit
is
cfp,
for
this
is
closed,
but
this
is
in
flight.
A
D
A
D
No,
I
think,
brooks
pretty
much
covered
it.
We're
just
trying
to
make
sure
that
all
of
the
changes
that
we
have
in
flight
settle
down
I
mean
odat
15
has
basically
been
ready
to
go
for
a
little
while
we're
just
making
sure
that
all
of
the
automation
stuff
is
able
to
push
out
the
releases
that
we
need.
A
Okay,
that's
great
quick,
org
announcement.
The
watson
cloud
llc
is
like
an
actual
thing,
so
we
do
have
trademarks
in
flight
on
on
all
the
components
in
you
know
now,
our
intention
is
is
that
at
some
point
all
of
this
work
will
be
moved
to
some
kind
of
a
standards
body
when
an
appropriate
conduit
exists.
You
know
a
la
like
a
cncf
type
motion
or
something
like
that.
So
I
will
keep
everybody
up
to
date.
A
I
didn't
have
anything
else.
Anyone
else
have
anything
open
floor.
They
wanted
to
bring
up
or
talk
about.
Maybe
I
would
just
point
out
real
quick
matt's
from
google
did
an
awesome
like
little.
You
know
google
doc
of
his
experience
going
through
some
of
the
tutorials
and
got
some
great
feedback
on
things
that
worked
and
didn't
work,
and
you
know
challenges
he
had.
I
would
encourage
anyone
else,
as
we
kind
of
start
to
wrap
up.15
help
us
you
know
run
through.
You
know
some
scenarios.