►
Description
https://github.com/asyncapi/community/issues/18
Powered by Restream https://restream.io/
A
C
C
A
A
Let
me
be
cautious
now,
like
you
remember
last
time
when
I
was
swearing,
yes
yeah,
so
I
mean
be
aware
that
we're
live
streaming
and
it's
gonna
stay
in
the
recording,
but
that's
the
fun
part
right
yeah
I
mean
it's,
it's
it's
fun.
When
you
do
it
by
the
accident,
we
can
pretend
it
was
by
accident,
not
anymore,
because
you
said
it
out
loud:
okay,
camera
life.
A
A
B
A
A
B
B
B
A
B
B
It's
already
remember
you,
you
told
me
the
other
day
on
on
twitter,
that
you
were
wondering
how
many
people
were
thinking
that
it's
me
having
conversations
with
myself
on
twitter,
like
tweeting
from
the
async
api
account
and
then
replaying
myself
and
then
so
it's
already
starting
to
happen.
But
for
you,
like
you,
said
hola
in
spanish,
from
the
async
api
account
and
antoinette
is
saying.
Hola.
F
F
F
B
B
B
C
G
D
B
G
A
G
G
D
A
E
B
G
B
B
A
B
A
B
E
E
G
A
A
But
it's
important
to
share
one
important
news.
Some
of
you
probably
noticed
this
news
already
somewhere
on
twitter,
but
I
will
not
do
any
spoilers
I.
I
will
only
say
that
among
so
many
great
people
joining
the
meeting,
we
have
one
special
guest
chris
anishtik
and
I
will
not
introduce
this
guest
because
I
will
do
a
spoiler
already,
so
the
guest
has
to
introduce
himself-
and
I
will
like
the
last
time
because
we
have
unusual
situation
and
we
have
live
streams,
so
we
have
people
in
chats
as
well
pretty
active.
A
B
B
Lately
right,
you
might
have
heard
that
recently
we
joined
postman
and
just
doing
this
to
put
a
little
bit
of
context
for
those
who
don't
know
yet
right
and
and
since
then
it
was,
it
became
a
little
bit
more
clear.
Let's
say
that
it
was
more
important
than
ever
that
we
we
should
be
joining
a
neutral
ground
instead
of
doing
this
just
ourselves
and,
legally
speaking,
the
project
being
a
project
of
frank
mendes.
You
know,
that's
not
serious,
that's
not
formal!
B
B
B
That
would
be
amazing,
so
so
yeah
I
mean
summarizing
a
little
bit
on
the
on.
Why
we
did
it.
I
think
it's
clear
like
we
want
to
becoming.
We
want
to
join
a
neutral
ground,
so
this
becomes
a
community
project,
not
a
project
of
a
few
of
us
and
and
how
just
want
to
mention
that
this
is
going
to
be
done
following
a
strict,
open
governance
model
and
actually
the
charter
for
the
for
the
project
is
already
available
on
github
and
some
of
you
already
contributed
because
yeah
we
couldn't
hide
it
right.
B
It's
like
we're
an
open
source
project,
even
the
even
the
blog
post
for
the
announcement
today,
was
already
as
a
pull
request
three
or
four
days
ago
there,
because
the
website
is
also
open
source
price,
so
yeah
we,
we
were
already
spoiling
the
the
announcement
and
and
yeah
and
the
charter
as
well.
This
was
prepared,
together
with
linux
foundation,
trees
from
maybe
you
have
to
help
me
here,
king
tris
cersei.
G
B
I
Yeah,
I
know
I
mean
I'm
I'm
happy
to
kind
of
answer
any
questions
I
mean
hello,
everyone
for
those
who
don't
know
me
chris.
I
need
also
thank
you
lucas
for,
like
it's
very
rare,
for
someone
to
pronounce
my
last
name
accurately
so
jean-claude
for
for
that.
For
that,
for
that
one
for
sure,
so
no
we
are,
we
are
very
excited
to.
You
know,
have
an
opportunity
to
help.
You
know
async
api
essentially
get
to
kind
of
its
next.
You
know
level
of
growth.
I
You
know
a
lot
of
the
reasons
fran
outlined,
or
you
know
a
great
reason
why
projects
kind
of
come
to
the
linux
foundation
outside
of
the
neutrality.
We
also
help
with
ensuring
you
have
open
governance.
We
could
also
help
with
events.
Community
growth,
fundraising,
there's
kind
of
so
many
things
we
do.
The
linux
foundation
truly
is
what
I
call
foundation
as
a
service.
Now
we
host-
probably
oh,
I
keep
forgetting
maybe
like
four
or
five
hundred
projects.
I
Now,
probably
50
60,
you
know
foundations,
you
know,
call
them
the
house
projects
and
we're
happy
to
host
the
async
api.
We
host
some
other
api
initiatives,
such
as
graphql
open
api.
You
know,
depending
if
you
consider
things
like
grpc
and
proto
kind
of
api
things.
You
know
we
host
those
things.
So
for
me,
I
look
forward
to
kind
of
supporting
and
growing.
F
I
I
A
So
before
anyone
has
any
questions
from
my
site,
I
started
pasting
some
links
in
the
in
the
chat.
They
will
be
also
in
the
meeting
notes.
So
the
link
to
the
charter
to
the
blog
post
about
us
joining
the
linux
foundation
from
from
fran.
I
saw
that
chris
already
shared
the
communication
from
linux
foundation.
A
So
I
would
like
to
emphasize
this
this
chapter
and
the
the
governance
model
like
a
message
to
all
the
big
companies
that
would
like
to
be
in
the
technical
steering
committee
of
the
spec,
just
be
aware
that
we
made
a
backdoor
much
easier
to
join
the
technical
stream
committee.
So
you
don't
have
to
like
hire
someone
fresh
and
put
on
the
project,
so
the
person
works
hard
to
become
a
tsc.
A
B
B
E
Hey
fran,
can
you
speak
to
the
potential
of
or
what's
the
right
word,
I
don't
know,
async
api
being
kind
of
a
an
all-encompassing
spec,
meaning
it's
got
http.
It's
got
graphql.
So
the
fact
that
open
api
graphql
grpc
are
all
on
the
linux
foundation.
I
mean
it
sounds
like
pretty
good
opportunity
for
you
all
to
work
together
on
things
right.
B
B
Now
I
mean
I'm
kidding,
but
you
know
so.
One
of
the
things
we've
been
discussing
lately
has
been
the
the
road
map
and
the
vision
and
the
roadmap
right
and
the
goals
for
the
initiative
and
one
of
them.
That
was
like
at
least
the
vision
was
clear,
like
we
want
to
become
the
number
one
spec
for
working
with
apis
with
any
kind
of
apis,
not
just
even
driven
or
asynchronous
apis
right.
So
we
didn't
get
crazy
here.
B
B
I
don't
want
to
call
it
tool
single
tool
because
same
thing
happens
on
the
tool
inside
right
like
we're,
not
gonna
compete
with.
I
don't
know
apollo,
for
instance,
for
graphql.
That
would
be
stupid
instead,
what
we
do
is
that
we,
our
tooling,
will
integrate
with
apollo
and
with
other
graphql,
tooling
and
other
grpc,
tooling
and
other
rest
servers
right.
The
same
way,
the
spec
integrates
with
other
specs
right
and
and
ideally
for
the
user.
B
That
means
that
just
a
single
workflow
and
in
a
single
place,
they
can
have
the
rest
apis,
the
graphql
api,
the
event-driven
apis,
you
know,
rpc,
it
can
be
grpc.
I
know
sergio
one
once
mentioned
that
we
shouldn't
be
only
sticking
to
grpc,
but
to
rpc,
as
in
as
in
the
concept
right.
Grpc
is
just
one
implementation,
but
but
yeah,
so
so
yeah
in
the
future
in
five
years
from
now.
B
This
is
the
vision
we
want
to
be
doing
this
and
and
one
of
the
one
of
the
pillars,
if
we
want
to
make
it
happen,
is
that
we
grow
as
a
community.
This,
the
growth
needs
to
be
insane,
because
again,
the
growth
has
to
be
very
ambitious
right,
because
the
thing
here
is
that
we
cannot
handle
this
ourselves,
a
group
of
a
few
people
just
working
on
on
on
everything
right.
That
will
be
impossible
for
us,
so
we
need
to
get.
B
We
need
to
get
really
strong
as
a
community
right
and
and
the
reasoning
behind
this
vision.
If
you,
if
you're
wondering
why
we
we
suddenly
changed
this
vision,
let's
say
is
we
want
to
unify
the
user
experience
when
developing
apis
right?
So
so
far
it's
a
fragmented
space.
Like
I
mean
I
cannot
explain
everything.
I
did
a
talk
recently
on
postman
galaxy.
Where
I
explain
all
of
this.
I
don't
want
to
be
doing
the
same.
E
Yeah
I'll
add,
add
real
quick
to
that.
I
actually
got
to
jump
to
a
json
schema
call
and
trying
to
get
their
their
alignment
in
place
is.
Is
this
is
really
important
across
all
the
specs
as
as
fran
said,
and
I
would
encourage
you
all
if,
if
you're
on
graphql
conversations
or
you're
in
grpc,
you
know
help
them
be
aware
of
the
other
communities
and
we're
trying
to
you
know,
join
in
on
the
jason
schema
slack
channel
and
we're
gonna
try
to
get
some
of
the
same.
E
I
would
say:
jason
schema
was
very
much
learning
from
fraunh
and
and
what
lucas
has
have
done
as
far
as
the
governance
is
is
concerned,
as
well
as
the
community
building,
and
then
I
would
say,
the
open
api
is
watching
as
well
right
now
and
learning
from
what's
going
on.
So
I
think
there's
a
lot
of
of
cross-pollination
and
and
learning
experiences
as
well
as
sharing
of
resources
and
one
of
the
projects
I
have
right
now
with
json
schema
with
ben.
E
To
talk
about
is
redoing
all
of
their
documentation
and
getting
the
oai
to
pay
for
it
is
so,
and
you
know
the
way
I
offered
it's
not
like
we're
pushing
on
the
way
I
offered,
because
it's
dependent
on
json
schema
for
the
open
api
specification
and
it's
it's
with
the
3-1
release,
it's
very
important
to
the
oai
that
jason
schema's
docks
are
up
to
date,
and
so
this
is
this
go.
This
is
the
spec.
This
is
the
supporting
resources
for
the
specs
cross
pollination.
E
B
So
yeah
just
to
add
what
kim
said
is.
This
is
all
about
people,
it's
not
about
tools
and
specs.
In
the
end
right,
we
know
some
people
from
the
graphql
community
and
from
the
grpc
community,
and
they
all
feel
the
same.
They
all
have
the
same
feeling
right
and
so
one
one
of
the
things
that
we
want
to
start,
maybe
not
now
right
now
right,
but
we
want
to
start.
H
H
H
H
If
what
we're
doing
currently
is
looking
at,
basically
how
we
document
our
infrastructure
async
api,
which
includes
a
lot
of
sqs,
and
we
wanted
to
try
and
contribute
back
to
say,
hey
here's,
basically
how
we
think
you
should
do
bindings
for
sgs
and
sms.
What
is
the
approach
that
we
should
use
to
do
that
today?
H
B
I
will
say
that
the
answer
is
always
like
raising
issues
and
let's
have
a
discussion
there
like
this,
is
the
the
the
bare
minimum
the
default
and
and
now
we
get
a
process.
I
think
lucas
shared
before
we
have
the
contributing
document,
the
new
one
yeah
on
where
you
can
make
proposals
right-
and
this
is
like
simplifying
things
a
little
bit
summarizing
a
little
bit
is
like
stage
zero
stage,
one
stage
two
and
three
right.
B
B
On
top
of
your
mind,
this
means
it's
you
open
an
issue
you'll
have
there
an
option
to
choose
with
which
kind
of
proposal
you're
making
or
if
you
don't,
have
a
clear
proposal
on
how
to
solve
the
problem,
but
you
just
want
to
make
a
proposal
that
we
discuss
on
making
a
proposal
right
then
just
open
an
issue
and
let's
have
the
discussion.
I
think
that's
the
best
way:
okay,.
H
Dropping
an
issue
is
it:
would
it
be
a
help
for
throwing
an
issue
if
we
say
fought
the
relevant
repo,
some
kind
of
rough
out
version,
what
we
thought
might
be
appropriate
in
there
and
then
you
could.
We
could
discuss
that
and
then
say
they
think
this
is
the
way
to
go.
Don't
go
this
way,
etcetera
and
then
come
keep
iterating
that
becoming
a
more
solid
proposal.
Is
that
what
way
to
do
today.
B
So
proposals
can
be
either
an
issue
or
if
you
are,
if
you're
in
the
mood,
maybe
you
can
just
propose
a
a
pull
request
with
some
examples
with
or
with
some
changes
in
this
case
right
up
to
you
like,
of
course,
if,
if
it's
a
a
pull
request,
then
people
can
discuss
there
but
you're
risking
that
people
don't
really
want
to
work
on
this
and
you
lost
your
time.
Making
changes
that
are
that
probably
are
gonna,
be
dismissed
with
a
simple.
B
I
don't
know
a
simple
answer
about
something
you
didn't
know
or
something
I
don't
know,
that's
why
we
always
say
like
hey:
first
communicate
the
intention,
don't
lose
your
time,
yeah
and
and
then
once
everybody
agrees,
or
at
least
there's
a
someone
telling
you
like,
hey
yeah.
This
is
something
that
will
be
worth
exploring,
or
at
least
nobody
is
rejecting
the
idea
for,
for
whatever
reason,
then
you
open
the
pull
request
but
yeah.
H
B
B
H
B
B
B
H
Understand
your
accent,
sorry
yeah!
No!
I
was
just
saying
that
I
I
think
at
one
point
there
was
a
suggestion
that
you
would
like
people
to
wait
before
making
prs
about
the
spec
until
you
had
actually
joined
the
foundation
and
had
credited
new
guidelines.
So
I'm
just
guessing
we're
past
that
point.
There
yeah.
A
You're
you're,
mostly
interested
with
bindings
right
sns
and
sqls,
then
yeah
yeah.
So
with
bindings
you
don't.
You
did
not
really
have
to
wait
because
bindings
are
at
the
end,
they're
separate
from
from
the
spec
a
bit.
So
we
I
think
we
merged
one
pr,
even
during
the
cycle,
but
but
anyway,
in
in
case
of
sns
and
sqs.
Your
process
for
you
should
be
easier
than
than
any
other,
because
we
don't
have
anything
there
yet
yeah.
A
So
just
be
aware
that
if
you
will
submit
especially
this
first
pull
request
about
the
sns
and
sqs,
we
will
ask
you
like:
will
it
be
okay
for
you,
if,
like
after
merging,
you
will
be
happy
and
okay
with
also
reviewing
pull
requests
whenever
somebody
will
suggest
changes,
sure
yeah,
then
so
yeah?
Definitely,
if
you
have
you,
you
want
to
take
this
role
and.
B
We
call
this
championing
right
like
becoming
champion
of
of
a
feature
or
a
proposal
or
part
of
the
project
like
like
uka,
said
right
like
we
cannot.
A
few
human
beings
cannot
take
care
of
the
whole
project,
even
less
if
we're
gonna
grow
so
so
yeah
that
will
be
for
those
who
are
listening.
If
you're
interested
in
specific
part
of
async
api,
don't
wait
for
us
to
to
do
it
like
just
jump
straight,
and
let's
do
it
together.
C
B
Just
trolling
him,
so
what
is
your
view
on
the
dco
get
signed
off
by
for
contributions
going
forward
or
cla?
Okay,
so
to
me
I
mean
I
don't
have
a
clear
opinion
on
that
on
that
point.
To
be
honest,
like
I
like
it
from
the
legal
perspective,
if
you
want
the
mom
and
do
you
start
working
with
many
with
too
many
people
and
too
many
big
companies,
not
only
big
companies,
but
you
know
too
many
companies
and
the
project
grows
and
and
grows
a
lot.
A
So
luckily
we
don't
have
to
enable
any
cla
tooling
on
on
asking
api
tooling,
so
no
special
agreements
acceptance
whatever
to
contribute,
but
that's
because
at
the
end,
it's
code
that
if
somebody
claims
ownership
of
this
some
particular
part
of
the
code,
we're
just
gonna
rewrite
it.
The
only
challenge
here
is
with
the
spec
I
mean.
If
somebody
contributes
part
of
the
spec
I
mean
rewriting
is
not
an
option.
B
And
the
spec
becomes
a
a
challenging
part
if
you
want
to
become
an
iso
standard,
for
instance
an
international
standard.
Otherwise
it's
also
not
so
problematic.
I
will
say
I
think
so
as
far
as
I
know,
but
if
you
want
to
become
an
iso
standard
or
any
other
kind
of
international
standard,
you
need
people
to
resign
from.
You
know
claiming
the
ownership
of
part
of
the
spec.
You
know,
because
specs
are
a
little
bit
different
than
code
and
yeah.
That's
the
only
part
that
I
will
say.
C
I
A
We
almost
have
everything
in
place,
except
of
one
thing
like
we
can
start
the
whole
process
of
adding
stuff
to
the
spec,
but
we're
not
yet
in
a
position
to
merge
it
because
we
did
not
yet
agree
on
the
release
cabins
for
the
spec.
So
there's
an
I'd
like
to
like,
if
you're
interested
in
this
in
this
topic
of
releasing
specification,
then
I
just
pasted
the
link
and
again
it's
going
to
be
in
the
meeting
notes.
A
There's
a
discussion
started
by
fran
many
different
opinions
and
that's
something
that
that's
a
let's
say
next
big
thing
to
solve
for
the
spec,
and
once
we
solve
this,
we
can
like
start
pushing
whatever
we
want
like
crazy.
So
that's
one
thing.
The
other
thing
from
the
charter
point
of
view,
like
technical
steering,
committee
etc.
A
So
we
now
have
to
like
the
charter,
is
pretty
clear
about
how
to
become
a
technical
member
of
the
technical
steering
committee.
It's
at
the
end,
a
maintainer
of
a
given
repo
and
we're
gonna
like
manage
it
through
two
different
files.
It's
gonna
be
code
owners,
the
the
file
that
is
a
part
of
the
github
features
and
a
custom
file
called
voting,
and
so
for
us
like
like
to
like
the
finalize,
not
finalized,
like
makes.
A
A
So
we
need
to
know
just
formalize
that,
like
out
there
like,
for
example,
michael
from
from
solas
that
contributed
to
great
templates
to
the
into
this
pack-
and
we
have
michael
on
the
call
and
there's
going
to
be
also
pavel.
That
works
a
lot
on
the
on
the
jason
guppy
and
so
other
people
like
also
a
few
people
from
postman.
Of
course
that
contribute
regularly.
So
we
are
gonna.
A
A
I
mean
for
us
it's
great,
because
we
already
see
that
there
are
many
great
contributors
coming
to
the
to
the
organization.
So
we
want
to
handle
it
like
properly
and
like
respect
the
time
for
contribution
and
review
the
applications
so
like
next
two
weeks,
they're
gonna
be
crazy
for
us.
So,
like
huge
requests
to
you
like.
A
B
A
A
A
A
The
schedule
thanks
a
lot
for
all
of
you
for
joining
the
link
to
the
notes
it's
gonna,
be
on
slug
on
twitter,
youtube,
descriptive,
video
description
where
you're
gonna
see
all
the
links
everything
we
mentioned.
You
know
how
to
catch
us
to
ask
questions
offline.
Let's
do
it.
That's
fine
and
see
you
somewhere
out
there.
B
So
yeah
now
we're
nice
people
and
we
try
to
help
each
other,
sometimes
not
even
related
to
async
api.
So
we
sometimes
get
some
people
just
jumping
in
the
channel
on
the
slack
workspace
because
they
need
help
with
something
programming
related.
That's
not
necessarily
isn't
kpi
related
and
they
feel
so
comfortable
that
they
do
it
there.
So
yeah.