►
Description
wasmCloud Weekly Community Call - this week featuring an overview of the new wasmCloud Documentation efforts and a glimpse at the health metrics of our growing community.
#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
I
think
it's
all
the
usual
suspects
so
for
our
demo
today,
we're
gonna
have
a
quick
preview.
We've
got
two
demos
today.
Actually
we've
got
a
quick
preview
here
of
the
upcoming
developer,
documentation,
site
and
kevin.
You
maybe
want
to
give
us
a
quick
little
narration
through
here.
You
know
some
of
the
things
we're
going
for.
B
A
B
Yeah
I
mean
the
the
general
idea
is
that
our
documentation
has
been
woefully
out
of
date
for
a
while,
basically
ever
since
we
started
the
0.15
rewrite
process,
and
so
now
now
that
we're
getting
ready
to
push
all
that
stuff
out
and
we're
essentially
feature
frozen,
we
can
start
documenting
everything
and
again
you
know
hindsight
being
2020.
We
can
learn
from
some
of
the
documentation
failures
we've
had
in
the
past
and
there's
essentially
four
different,
guided
paths
through
the
documentation.
There's
the
overview.
B
So
if
you're
just
hitting
this
and
you've
never
seen
any
of
this
stuff
before
we've
got
a
spot
for
you
to
go
if
you're
an
app
developer,
there's
a
specific
set
of
guides
and
tutorials
for
for
those,
if
you're
a
platform
builder.
So
if
you're
using
wasm
cloud
to
build
a
platform
on
top
of
it
for
for
other
people,
we
have,
you
know,
use
case
targeted
guides
there
and
then
underneath
it
all
is
the
reference
and
so
ideally
the
overview.
B
The
guides
for
app
devs
and
the
guides
for
platform
devs
will
all
link
to
the
various
sections
of
the
reference
that
are
that
are
applicable,
and
then
we
have
the
faq
underneath,
but
before
our
our
documentation
was
fairly
haphazard
and
just
kind
of
it
was
thrown
together
organically,
as
we
grew,
which
was
good
at
the
time,
but
we
we've
since
outgrown
that
style
of
documentation.
So
I
think
this
should
give
us
a
better
foundation
for
making
our
our
stuff
more
discoverable.
A
Know
that
that
was
kind
of
the
definition
that
we
had
daz.
You
know
we're
thinking
something
along
the
lines
of
why
stop
at
the
edge.
You
know
something
a
little
more
provocative
or
you
know
like
forward,
pushing
to
push
the
concept
or,
and
we
actually
have
some
marketing
brainstorm
around
that.
What
do
you
like?
I
agree.
That's
not
a
tag
line,
that's
more
of
like
a
a
definition
here
of
what
we're
you
know
a
project
description.
If
you
will,
what
are
your
initial
thoughts.
C
D
Got
it?
Thank
you.
Well,
look
at
the
please
go
ahead,
yeah,
it's
at
dallas's
point,
maybe
maybe
the
the
the
people
who
are
attracted
to
this
and
and
dealing
with
it
through
all
this
turbulence,
maybe
maybe
good
people
to
just
throw
out
ten
or
so
descriptions
because
we're
the
weirdos
who
are
who
are
really
really
curious
and
attracted
to
this
for
very
strange
reasons.
So
you
might
get
some
different
perspectives.
A
I
I
agree
with
you.
I
agree
with
you
all
entirely
on
this
and
I
think
if
we
can
view
this
first
demo
as
sort
of
a
call
to
action
here
on
you
know,
we'd
love
your
thoughts
and
contributions
either
via
slack.
You
know
just
start
throwing
stuff
up
on
the
wall.
We
can
create
a
tagline
thread
or
just
banding
it
about.
We
do
have
new
logos.
A
I
was
hoping
those
would
be
ready
for
today
we
have
them
in
flight
they're,
not
ready,
but
in
the
next
few
days
we'll
unveil
the
proposed,
wasn't
cloud
logo
and
we'll
start
rebranding
this.
This
branch
is
set
up
on
a
github
here,
so
we
can
start
just
taking
full
requests
and
thinking.
However,
I
need
to
get
it
the
netlify
stuff
ironed
out,
so
the
netlify
pieces
just
didn't
quite
pick
up.
I
have
a.
A
I
have
a
pr
that
fixes
that
I
I
got
it
set
up
about
two
seconds
before
the
meeting
started:
okay,
great,
so
yeah,
we'll
link
this
on
slack
and
I'll
link
it
in
the
documentation
when
the
netify
site
works.
So
we
all
have
the
kind
of
placeholder,
for
this
will
be
awesomecloud.dev,
which
will
be
linked
off
the
new
wasn'tcloud.com
landing
page,
where
you
know
to
your
point
as
well:
we'll
feature
that
hero
statement
a
little
more
crisply
and
cleanly
there
kevin
anything
else
to
add
on
this
on
this
particular
demo.
A
Thank
you
so
much
kevin.
I
really
appreciate
that
in
this
next
section.
I
want
to
do
a
quick
overview
of
you
know
when
you're
building
open
source,
you
know
what
you're
really
doing
is
building
community
and
there
are
certain
ways
that
you
need
to
behave
when
you're
building
community,
and
I
think
that
over
the
last
few
months,
if
you've
been
around
you've
noticed,
like
you
know,
we're
publishing
our
agendas
in
advance.
We're
you
know,
we've
got
our
little
youtube
channel
here.
Our
twitters
are
more
active
and
more
coordinated.
A
A
Now
this
is
a
new
startup,
that's
funded
by
andreessen
called
orbit.love,
and
I'm
in
there
kind
of
like
alpha
access
here
and
loving
it,
because
it's
a
bit
better
than
the
ways
that
I
was
doing
this
before
it
gives
us
the
ability
to
see
when
new
people
are
joining
the
community
understand
what
their
reach
is.
You
know
like,
as
far
as
how
many
twitter
followers
do
they
have.
A
You
know
where
they're,
where
they're
out
of
and
help
us
to
kind
of
like
loop
in
and
identify
people
that
need
to
be
called
out
for.
Congratulations
so
gustav.
I
don't
think
that
you're
on
today,
but
if
you
watch
this
video
later,
I
want
to
do
a
quick
call
for
all
your
hard
work
over
the
weekend
and
in
the
last
week
you
know
with
the
brooks
on
wash
and
everything.
A
It's
definitely
noticed
then
and
appreciated,
and
as
we
get
into
this
a
little
further
here-
and
we
start
to
have
some
real
crisp
metrics
around
you
know
the
sort
of
like
active
participants
around
the
total
engagement,
I'm
going
to
start
calling
some
of
this
stuff
out,
you
know,
so
we
can
sort
of
set
some
goals
for
ourselves
on.
You
know:
user
growth,
community
growth,
the
types
of
activities
we
want
to
see
are
we
are
we
as
a
community?
Are
we
being
welcome
welcoming
enough
by?
Like
writing?
Github
issues?
A
Are
we
answering
github
issues
quickly,
especially
with
dot
15,
when
I
think
people
are
gonna
have
a
real
ability
to
start
using
this
in
production,
so
any
thoughts
or
comments
or
questions
about
you
know
this
idea
this
initiative
do
people
like
this?
Do
we
should
we
do
this
every
week
or
does
this
feel
like
you
know?
Maybe
we
should
just
do
this
behind
the
scenes.
B
B
D
A
E
So
it's
you
know
one
of
those
things
where
it
was
one
of
our
early
projects
and
there's
you
know,
I
don't
think
I'm
breaking
any
rules
to
say
that
there
are
well
more
than
100
000
daily
users
of
it
around
the
world,
which
is
pretty
substantial
and
we
don't
do
anything
to
tie
it
to
microsoft.
And
yet
there's
still
that
perception
that
maybe
we
could
you
know
kind
of
thing,
so
the
stalkerish
possibility
is
there.
You
know
kind
of
deal
all
that
taken
into
account.
E
I
think
the
highest
priority,
for
this
kind
of
thing
is
not
what
you
do,
but
whether
you're
completely
transparent,
and
by
that
I
want
to
say
that
there
isn't
a
single
major
project
out
there
that
doesn't
track
image
downloads
forks
stuff
like
this,
but
I
don't
know
any
major
one
that
publishes
those
features,
those
numbers
so,
for
example,
kubernetes,
could
easily
publish
and
the
cncf
could
easily
publish
download
figures
for
the
images
of
the
popular
projects,
but
they
don't
do
that.
So
why
is
that?
E
And
I
have
a
feeling
that
this
kind
of
telemetry
is
stuff
that
we
typically
think
of
as
well?
Maybe
we're
tracking
people.
Maybe
you
know
what
kind
of
thing,
and
we
worry
about
that.
I
think
the
opposite
is
true.
I
think
that
if
we
actually
dump
more
information
out
that
you'd
be
you,
can
you
honestly
and
transparently
say
we're
looking
at
how
many
people
are
participating
and
how
fast
they
move.
Here's
a
graph
of
that.
E
E
E
I
think
you
could.
You
could
do
telemetry
up
the
wazoo
if
you're
completely
transparent
and
dump
the
numbers
out
and
show
everybody
what's
going
on.
Obviously
de-anonymized
and
things
like
that,
I
mean
you
know,
there's
a
limit
to
anything,
but
I
think
a
lot
of
people
in
open
source
want
to
see
the
numbers
they're.
You
know.
Telemetry
is
one
of
those
controversial
issues
in
open
source,
not
because
people
don't
want
it,
but
they
don't
know
how
to
share
it.
They
don't
know
what
they're
tracking
on
you
know
all
those
kinds
of
things
yeah.
A
A
You
know
how
I
was
thinking
and
you
know
what
I
would
what
I
was
doing
behind
the
scenes
and
I
definitely
feel
like
what
I
hear
is
that
there's
a
middle
ground
here,
where
we
should
share
a
subset
of
it,
but
make
sure
to
your
point,
we're
often
anonymized
and
I'll
make
sure
that
I
do
wipe
some
of
the
screens.
I
just
shared
on
the
video
that
I
post,
because
I
think
I
did
just
share
like
a
list
of
email
addresses
that
is
open.
A
Anybody
can
scrape
this
right
out
of
sure
and
all
that,
but
to
have
it
already
pre-scraped
you're
right,
but
I'm
thinking
very
hard
about
it
and
I'm
we're
putting
in
a
lot
of
time.
You
know
we're
working
on
we've
got
with
some
of
our
early
adopters.
We
have
some
case
studies
that
are
in
flight,
that
we're
gonna
surface
out
and
share
on
the
new
site,
and
things
like
that,
so
those
kind
of
marketing
and
community
building
activities
are
in
progress
just
for
general
awareness.
Sure
I'll.
A
E
If
somebody
turned
that
to
100,
I
think
you
could
collect
a
lot
more
information
as
long
as
people
could
see
where
the
information
went
yeah.
Basically,
what
I
take
to
be
the
balance
of
things
right
now
and
I
think
there's
some
blinders
on,
because
nobody
taking
it
is
different
than
sharing
it,
and
if
you
opted
to
share
more
appropriately
anonymized
and
so
forth,
for
wherever
it
makes
sense,
then
you
could
do
a
lot
more.
I
think
than
than
people
are
currently
doing.
A
Yeah
absolutely
okay.
Well,
let's
move
on
community
news.
We
have
just
as
a
quick
note
the
regularly
scheduled
losing
time
meeting
that
is
on
thursdays
at
one
o'clock
has
been
canceled
for
tomorrow,
so
that
one
will
happen
again.
Two
weeks
after
that,
I'll
get
the
date
surface
done
here
for
our
notes
later
and
I'm
tremendously
excited
to
preliminarily
announce
wasn't
a
for
kubecon
eu!
I
talked
to
chris
alphabet
about
this.
A
He
said
we
could
go
ahead
and
start
promoting
it
here,
but
the
day
before
kubecon
eu
there
will
be
a
hashtag
wasmday,
a
conference
that
will
be
available,
and
this
will
be
officially
rolled
out
early
next
week
with
a
call
for
papers
as
well.
As
you
know,
some
initial
scheduling
and
logistics
and
organization.
A
So
I
really
hope
to
try
to
rally
a
lot
of
the
folks
that
are
regular
contributors
here,
including
the
the
microsoft
team,
the
capital,
one
team,
the
folks
from
intel
and
others
and
get
them
submitted
and
to
help
promote
some
of
the
amazing
things
that
are
happening
in
this
community,
and
I
certainly
hope
that
wasn't
cloud
ends
up
as
a
submission
for
the
talk
as
well.
So
watch
your
twitter
feeds
early
next
week
for
some
new
landing
pages
and
announcements
around
that.
A
It's
a
good
article,
if
you're
not
following
that
project,
I'll
link
it
out
here
and
I
believe,
actually
that
phil
kitty
who's,
the
one
of
the
creators
of
wapc
has
now
joined
microsoft
and
is
working
around
that
space
as
well
in
their
r
d
group.
So
we
have
a
one
of
our
community.
Members
is
directly
connected
to
that
particular
team
as
well.
A
E
I
don't
think
so,
yet
you
know
you
you,
basically
the
the
the
high
order
bit
is
that
it's
happening
and
we're
really
thrilled
for
that.
The
nice
thing
is
that
it
doesn't
seem
to
really
conflict
with
very
much
going
on
that
day,
and
so
it's
in
the
one
thing
it
does
conflict
with,
which
is
edge.
You
could
probably
go
back
and
forth
between
items
because
we're
virtual
now
we
don't
have
to
be
in
a
room.
E
A
A
A
Okay,
I'd
do
that
all
right
I'll
get
some
confirmation
on
that
for
the
schedule.
Now,
let's
turn
over
to
sort
of
our
current
business
here
kevin
you
had
mentioned
a
possible.
You
know
date
forced
a
rally
to
earlier.
Did
you
want
to
publicly
say
that
or
you
know
that
what
we,
what
we'd
like
to
get
done
for
the
dot
15
release-
and
you
know,
wrap
everything
up
by.
A
Okay,
all
right
so
we'll
officially
write
it
down
january
31
2021
for
wasmcloud.one5.
That's
a
that's
a
huge
huge
milestone
there.
Bold
it
underline
it.
Do
all
the
things
and
along
those
notes.
Bill
has,
I
know,
couldn't
make
it
today,
but
he
dropped
some
notes
around
packaging.
Does.
Can
somebody
read
those
out,
so
we
sort
of
have
have
the
kind
of
status
on
that
if
somebody
doesn't
mind
doing
that.
For
me.
A
Anybody
all
right
so
bill
had
dropped
a
couple
notes
here.
Let
me
just
play
with
over
his
notes
all
right,
so
the
default
instructions
here
on
package
cloud
are
going
he's
got
a
couple.
Minor
he's
got
a
bug
on
one
of
the
raspberry
pi
platforms
he's
he's
working
through,
but
you
can
use
the
existing
packet
managers
here.
You
know
it's
kind
of
like
identified
off
the
off
of
package
cloud
dot,
io
forward.
Slash
wasn't
cloud
here
so
wash
is
up
here.
A
If
you
want
to
start
testing
and
playing
with
that,
and
it's
supported
across
a
handful
of
platforms,
there
are,
let's
see
the
homebrew
instructions
for
mac
are
in
flight.
It
looks
like
there's
a
test
version,
I'll
link
the
install
instructions
into
our
notes.
If
anybody
wants
to
play
with
the
the
sort
of
a
brew
cask
for
that
as
well,
did
I
miss
anything?
Kevin
brooks.
A
B
A
B
So
we
have
the
actor
interfaces
for
rust
that
we
need
to
do.
We
have
the
core
sample
ones
for
tiny,
go
that
need
to
be
started
and
finished,
there's
and
then
there's
making
sure
that
all
of
the
capability
providers
are
upgraded
to
the
new
actor
interfaces
and
then
making
sure
all
of
our
samples
are
upgraded
to
the
new
actor
interfaces.
A
B
A
F
I
think,
echoing,
where
kevin's
at,
where
we're
pretty
much
feature
complete
for
wasmcloud
same
same
deal
for
wash,
I
think
you
said
it
earlier,
but
just
to
make
sure
it's
known,
big
props,
to
gustav
for
doing
work
and
and
getting
a
fairly
big
pr
into
wash,
and
he
added
the
the
feature
to
get
all
the
commands
in
the
repl,
not
just
the
command
interface
ones.
So
hats
off
to
him
for
doing
that.
F
I've
filed
a
few
issues
across.
I
mostly
wash
one
on
wasmcloud.
That's
mostly
just
user
experience.
Stuff
that'll
make
it
better
for
the
like
initial
experience
for
somebody
following
a
tutorial,
so
I'm
working
on
those
alongside
the
actor
interfaces
so
that
when
somebody
visits
our
documentation
site,
does
that
initial
tutorial?
It's
crisp
and
it's
it's
it's
good.
So
that's
the
the
main
call
out.
A
F
So
what
I've
also
tried
to
do
here?
I
have
this
0.2.0
and
odot
3.0
milestones
and-
and
these
are
kind
of
soft
milestones,
but
what
I'd
like
to
do
is
release
the
2.0
release
with
wasm
cloud
15,
just
to
kind
of
segment
off
a
release
like
our
like
wasm
cloud
is
doing
a
minor
release,
so
those
2.0
ones
are
ones
that
I'd
like
to
finish
by
the
end
of
january.
So
if
any
of
those
have
good
first
issue
or
or
help
wanted
on
it,
but
please
take
a
look
at
those.
F
A
A
B
Yeah
having
this
implicit
dependency
on
version
numbers
creates
more
confusion
than
then
it
clears
up.
I
think,
because
you
know
if,
if
we
do
our
jobs
right,
then
the
communication
protocol
between
wash
and
the
wasm
cloud
should
continue
to
function
even
as
wise
and
cloud
goes
through:
odot,
16
and
17,
and
so
on.
B
A
F
I
do
have
one
more
thing
to
bring
up.
That
is
a
dependency
for
for
wasm
cloud
and
for
wash
we
we
have
issues
in
both
repos
to
remove
all
of
our
get
dependencies,
which
is
mostly
going
to
be
on
us
for
releasing
the
crates
that
we're
working
on
that
we're,
depending
on
one
in
there
is
the
oci
distribution
crate,
which
I
know
crosslit
is
planning
another
release.
F
F
A
A
Chris,
I
don't
know
if
the
a
crosslit
critical
stack
demo
is
possible,
but
that
would
be
a
great
little
demo
to
sort
of
you
know
get
people
excited
about.
You
know
those
kind
of
things.
Let
me
know
when
you
feel
like
you'd,
be
ready
to
do
those
demos
and
we'll
get
there.
I'm
also
gonna
drop
out
into
our
slack
a
call
for
our
wasn't
cloud
release
party.
A
So
we'll
do
a
big
open
call
and
I
think
half
the
folks
on
the
call
have
been
through
that
motion
before
you
know.
You
just
give
me
your
address
and
a
box
of
flavored
snow
globes
shows
up
for
you
to
enjoy
on
a
shared
community
call
so
watch
for
that
dropped
out.
All
they're
welcome
and
we'll
have
a
good
time
any
other
topics
we
wanted
to
throw
out
there
for
anybody.
D
So
the
the
the
demo
script
I
was
revisiting
that
trying
to
go
through
it
now
that
getting
closer
to
0.15
again,
and
I
can't
get
through
either
of
the
examples
due
to
due
to
commands
that
don't
exist
or
inconsistent
flags
options.
So
if
you
have,
if
you
have
a
like
a
a
cheat
sheet
that
stuff
that
I
can
use
to
update
those,
so
I
can
get
through
that
on
my
side,
then
I'll
contribute
to
the
documentation
but
yeah.
A
And
if
it's
all
right
with
you
I'll
I'll,
just
add
you
to
the
github
repo
and
we
can
create
this
repo
there.
If
you
want
for
building
building
things
out-
and
you
know
like
keeping
track
of
this
there-
that
would
it
might
help
more
people
to
contribute
here
and
I'll
make
sure.
I
link
this
in
the
notes
as
well.
A
Thank
you
so
much
for
running
through
this
and
helping
us
to
run
through
what
this
first
experience
is
like
no
problem,
great
awesome
share
by
the
way.
What
else
any
anything
else
that
we
wanted
to
do,
or
I
think
that's,
we
call
it
a
wrap
all
right,
everybody,
I'm
gonna,
stop
recording,
but
we
can
go
and
hang
out
afterwards
have
a
great
week.