►
From YouTube: AsyncAPI SIG meeting 61 (November 9, 2021)
Description
This is the recording for the AsyncAPI Special Interest Group (SIG) meeting #61.
Agenda and notes: https://github.com/asyncapi/community/issues/133
Chat:
17:08:05 From Alejandra Quetzalli : Holaaaaa Barbaño :D
17:08:05 From Lukasz Gornicki : https://github.com/asyncapi/spec/pull/594
17:08:20 From Barbaño : Hi :)
17:09:58 From Sergio Moya : I’ll need to leave in about 10 mins! But how cool is to see all your faces :D
17:10:09 From Alejandra Quetzalli : Que bueno verte Sergio :D !
17:10:54 From David Boyne : Yeah sorry got camera off I’m sorting out kids haha whilst listening
17:11:35 From Aayush Sahu : Hurry up Lukasz! :D
17:11:39 From Alejandra Quetzalli : Haha the joys of fatherhood, Dave
17:11:46 From Aayush Sahu : with the recording*
17:12:37 From Jonas Lagoni : https://github.com/asyncapi/community/discussions/157
17:16:20 From Sergio Moya : https://github.com/asyncapi/community/issues/163
17:16:57 From Alejandra Quetzalli : It’s so cool!!
17:19:58 From Alejandra Quetzalli : I like that idea!!
17:20:07 From Alejandra Quetzalli : A slack channel for changing to spec v3 could be so sueful
17:20:11 From Alejandra Quetzalli : useful*
17:25:00 From Sergio Moya : Have to leave. Don’t say anything Lukasz keep going with live video.
17:25:06 From Sergio Moya : Will keep up later
17:25:14 From Jonas Lagoni : Cya Sergio!
17:25:16 From David Boyne : Cya 👋
17:25:21 From Maciej Urbańczyk : Bye!
17:25:31 From Barbaño : Bye Sergio!
17:26:09 From David Boyne : If we git clone Jonas x 50 we can get the 3.0 release for Jan 🤠
17:26:16 From Alejandra Quetzalli : OMG hahahahahahah
17:26:21 From Alejandra Quetzalli : Git clone jonas
17:26:24 From Alejandra Quetzalli : 😂
17:27:29 From Alejandra Quetzalli : Thank you barbaño !!
17:27:34 From Alejandra Quetzalli : :D
17:29:15 From Lukasz Gornicki : https://drive.google.com/drive/u/1/folders/1QBwLkkcVSFWL125ZvA22_quiRNbXQeXg
17:38:05 From _acebuild : This is super awesome!!!
17:40:45 From Lukasz Gornicki : https://github.com/asyncapi/spec/issues/622
18:03:38 From _acebuild : Thanks Guys
18:04:27 From Alejandra Quetzalli : Wohooo 🥳
18:05:18 From _acebuild : Lukasz send my swagggggggg
18:05:34 From Alejandra Quetzalli : All the SWAG
A
A
A
It's
a
proposal
that
addresses
a
request.
Reply
pattern
in
the
in
the
spec
yeah.
We
advised
marek
to
join
the
meeting,
to
yeah,
to
explain
the
request
for
change
and
then
and
preach
for
for
the
community
to
join
the
discussion
in
the
proposal,
but
I
don't
see
mark
on
the
list
of
the
of
the
of
the
people
that
joined
the
meeting
like
on
the
list
of
the
participants.
A
Okay,
cool
so
and
yeah.
I
just
realized
that
I
usually
first
ask
people
and
welcome
people
for
the
first
time
and
not
jump
coldly
into
the
agenda.
So
anybody
has
any
questions
answers
before
we
go
further
with
the
with
the
action
items
that
we
have
on
the
list,
or
maybe
you're
here
for
the
first
time
and
you'd
like
to
introduce
yourselves
to
the
group.
That's
now
that's
the
best
moment
to
do
it
so
please
feel
free
to
unuse
and
speak.
A
A
B
B
B
C
I'm
sorry
I'm
sorry.
If
this
is
a
silly
question,
I
was
just
wondering
whenever
you
start
to
try
to
set
up
these
meetings.
Are
you
going
to
try
to
choose
the
time
that
works
for
all
the
time
zones?
Are
you
thinking
about
doing
more
than
one
meeting
kind
of
like
how
lucas
does
with
this
one
or
or
what
were
your
hopes
for
that?
I
was
curious.
B
Yeah,
it's
a
great
question
because
it's
one
of
the
things
that
have
not
been
decided
in
any
way-
and
that
was
also
one
of
the
perspectives-
is:
how
can
we
do
it?
Should
we
do
it
like
we
do
with
the
sick
meeting
just
one
week,
it's
eu
times
next
week,
it's
central
america
times
or
whatever
it's
up
for
discussion.
So
if
it's
needed
that
we
have
these
split
time
zones,
then
let's
do
it
it's
all
about
who
actually
wants
to
join
right,
but
it's
a
good
suggestion.
B
B
B
E
Yeah
I
want
to
highlight
something:
you
mentioned
this
concept
of
working
group
or
whatever
cool
name.
You
want
to
validate
there,
so
something
we
have
been
talking
just
you
know
random
from
that.
It
would
be
nice
to
gather
people
for
this
kind
of
concept
of
working
group
like
freelance
working
group,
so
it
doesn't
have
to
be
the
same
people
that
joined
those
calls
right
and
not
all
of
those
should
attend
the
meetings
but
at
least
to
gather
more
people
interested
on,
follow
and
collaborate
with
the
release
of
v0v300.
E
Something
I
want
to
also
add
here
is
that
we
created
a
an
issue
which
is
very
short
right
now
that
is
going
to
be
about
keeping
a
a
journal
for
the
release
process.
So
a
simple
journal
where
we
will
be
writing
comments
that
will
act
as
a
as
a
locks
for
everything
it's
not
going
to
be.
I
guess
not
going
to
be
everything
in
there,
because
for
that
reason
we
have
issues
and
so
on,
but
like
a
very
summarized
idea
right.
E
E
D
E
Yeah,
I
guess
I
guess
it's
just
it.
Shouldn't
have
to
be
very
formal
process
right.
It's
just
thanks
to
github
comments.
I
think
we
can
just
write.
For
example,
I
wrote
today
that
during
today's
meeting
we
will
mention
that
jonas
will
mention
the
fact
that
we
want
to
create
these
meetings,
these
recording
meetings
and
so
on
so
feel
free
to
to
add
anything
you
you
feel
it
should
be.
There.
D
Was
the
only
reason
I
asked
was
because
I
think
if
you
tag
in
other
issues,
if
we
tag
that
if
we
tag
that
particular
journal,
then
github
will
automatically
put
it
in
there,
won't
it
and
as
a
reference
it's
been
referenced.
But
I
don't
know
if
that's
that'll
be
too
much,
but
it's
just
a
thought.
But
anyway,
let's
keep
it
simple
for
now.
As
you
said,.
B
B
D
B
I
mean
for
me,
it
makes
sense
just
to
to
have
it
in
the
spec
channel
unless
there's
very
specific
reasons.
We
I
can't
because
the
spec
channel
isn't
used
that
much.
So
I
don't
think
it's
going
to
create
too
much.
Everything
is
relevant
within
that
channel,
but
it's
definitely
something
you
can
look
at.
B
C
A
A
C
C
F
A
So,
to
jump
to
another
topic,
I
let
me
be
serious
for
a
sec
and
and
yeah,
so
I
I'm
all
with
you
for
the
meeting.
I
think
we
need
to
do
them.
At
least
we
need
to
try,
because
that's
my
one
of
my
findings
when
working
on
the
conference
that
I
wanted
to
do
everything
guessing
with
the
community,
but
I
have
a
feeling
that
if
there
would
be
a
synchronous
meeting.
A
It
would
be
easier
to
take
people
on
board
to
get
help
from
them.
At
least
that's
how
I
would
do
it
next
time,
but
I
will
leave
my
comment
as
well
in
the
in
the
discussion
like
I'm
pretty
much
biased
if
it
comes
to
the
naming
like
sick
or
working
group,
so
I
suggest
you
don't
use
it,
but
I'm
gonna
explain
myself
in
the
discussion.
A
A
A
A
Unfortunately,
I
don't
have
yet
all
the
recordings,
but
so
far
so
good.
We
started
marketing,
but
I
mean
if
you
want
to
know
more
details.
I
would
put
anyway
summary
in
the
in
the
discussion
where
we
were
talking
about
the
marketing,
but
if
you
ever
think
about
spending
money
on
twitter
adwords,
don't
don't
waste
the
effort
so
but
yeah
we
have
already
432
registrations
and
we
also
don't.
A
Don't
say
like
don't
hide
that
we
will
also
stream
the
conference
to
our
social
media
so
that
people
don't
have
to
register
so
looks
good.
In
my
opinion,
the
the
swag
setup
is
also
ready.
Barbano
put
a
update
on
on
discussions
as
well.
Like
we
already
know
what
swag
pack
community
thinks
is
the
best,
and
once
the
conference
finish,
yeah
we'll
start
contacting
people
on
where
to
send
swags.
A
A
So
it's
gonna
be
super
busy
on
twitter
next
few
days
before
the
conference,
and
I
guess
it's
pretty
much
it.
I
just
need
to
drag
fran
to
steal
his
brain
on
how
to
set
up
all
the
streaming
services
because
he
was
doing
it
for
the
last
conference
we
had
last
year,
but
nothing
so
far
shows
that
we
will
cancel
the
event.
C
C
Oh
okay,
cool
cool.
I
have
another
question.
The
other
thing
that
I
was
wondering
was
in
the
future.
Besides
just
sending
to
you
directly
and
you
know
annoying
you
with
20
recordings
of
conference
talks
that
we
all
just
made
and
the
powerpoint
slides.
Why
not
create
a
google
drive
and
just
tell
us
all
drop
your
stuff
there?
I
was
curious
about
that
because
I
was
wondering
if
there
was
something
I
didn't
know
about
about,
why
that
couldn't
be
done.
C
A
A
A
Yeah,
but
one
like
the
the
conference
is
on
webex
and
webex.
Has
this
feature
that
we
can
make
pools
and
one
of
the
pool
will
be
definitely
asking
people
like
what
do
you
think
about
having
a
convert
like
conference
next
year
in
person
like
in-person
event,
and
I
hope
everyone
will
say
yeah:
let's
do
it
so
spoiler
alert.
There
will
be
some
pools
yeah.
A
C
Now
this
made
me
wonder
whenever
we
feel
that
it's
safe
enough
to
consider
doing
the
conference
in
person,
I
was
hoping
that
we
would
still
consider
the
offering
of
doing
it
in
person,
but
also
online,
so
that
people
who
don't
feel
safe,
traveling
yet
can
still
participate
and
people
that
don't
have
money
to
travel
can
still
watch
the
conference.
So
I
was
curious
about
that.
A
I
mean
when
I
said
like:
do
it
more
professional
and
and
engaging
more
with
linux
foundation,
I
was
thinking
like.
Basically,
they
have
a
lot
of
experience.
That's
why
I
want
to
hand
over
to
them
and
definitely
do
a
hybrid,
because
they
already
know
how
to
do
it,
because
they
do
it
on
a
huge
scale,
with
cncf
and
their
kubecon
and
like
so
for
this
year.
A
Since
I
was
the
only
one
pushing
much
so
much
for
the
conference,
I
took
the
liberty
to
decide.
It's
gonna
be
full
online,
especially
also
because
of
the
time
frame,
but
I
was
I
just
wanted
to
be
like
respectful
to
everyone
that,
like
especially
to
countries
that
don't
have
access
to
vaccines
as
easy
as
other
countries
to
be
respectful
to
other
community
members,
but
next
year
it's
like
it's
different.
It's
and
I
think
it's
a
it's
a
place
for
hybrid
approach.
A
H
H
So
yeah,
a
few
months
ago,
in
the
10th
september,
I
created
the
proposal
for
the
specification
to
allow
defining
the
schema
format
other
than
the
default
one,
because
at
the
moment
we
have
the
the
default
one
schema
format.
It's
called
the
essence.
Api
schema
object
and
it's
a
something
like
the
superset
of
the
json
schema,
because
it's
exactly
the
json
schema,
but
we
also
add
the
few
additional
keywords.
As
I
remember
the
three
discriminator
deprecated
and
texts.
H
Then
you
can
only
use
it
in
the
message
payload.
You
cannot
use,
for
example,
in
the
message
headers,
where
you
can
also
define
it
as
the
schema
or
in
the
channel
parameters
yeah.
So
this
is
the
so
this
is
the
problem.
How
to
exactly
tell
the
specification
that
this
schema
is
in
the
another
format,
so
my
proposition
is
to
extend
the
schema
object
to
the
union
type,
because
at
the
moment
you
can
only
write
it
as
the
you
know.
H
The
json
object
yes
or
yam
if
you
use
diamond,
but
it's
exactly
the
json
so
to
extend
to
the
union
type,
so
the
first
type,
with
a
form
of
the
chord
one
yeah.
So
it's
the
normal
yam
or
json,
but
the
second.
It
will
be
something
like
the
object.
The
json
object
with
two
fields:
the
schema
in
the
schema
format.
Yes,
so
exactly
as
we
have,
for
example,
I
will
show
that
so
in
the
message
object
we
can
have.
We
have
something
like
the
schema
format.
H
H
H
So
exactly
in
my
proposition,
it
works
in
the
same
way,
but
we
have
the
schema
format
field
exactly
inside
the
schema.
Yes,
the
second
type
of
the
of
new
union
type
of
the
schema
object
yeah.
So,
as
you
can
see
this
type,
the
old
one
is
exactly
the
same,
so
you
can
define
the
schema
in
two
ways,
but
it's
exactly
compatible
with
each
other
yeah.
I
think
that
it's.
H
H
Yeah
keep
the
old
approach
and
then
you
approach,
I
will
talk.
Why
I
want
to
you
know:
have
this
old
approach
also
yeah,
because
yeah
to
the
old
approach
and
because
I
think
that
it's
a
very
good
thing
to
have
something
like
the
default
schema
format
in
the
root
in
the
root
of
the
specification
like
the
default
content
type.
H
So
it
means
that
if
you,
for
example,
want
to
define
all
schemas
in
the
specification
in
the
avro
in
the
other
format
or
ram-
or
I
don't
know-
maybe
in
protobuf
also
that
you
can
reuse
some
models
defined,
for
example,
for
the
old
application,
and
you
want
to
describe
it
in
the
essence
api
with
the
essence
api.
Then
you
can
define
in
the
root
exactly
the
different
schema
format
and
then,
if
you
define
some
schema,
it
exactly
infer
the
schema
format
from
this
root
field
yeah.
H
So
it's
very
very
similar
to
the
default
content
type
because,
for
example,
you
can
define
the
the
content
type
in
the
message
object
and
it
overrides
the
different
content
from
the
root
and
it's
usually
the
application,
json
yeah.
So
it's
very,
very
similar
yeah.
There
are,
there
is
a
example
with
the
protobuf.
I
don't
know
how
to
exactly
call
the
schema
from
that
for
protobuf.
H
E
H
Yeah.
Thank
you.
Thank
you
very
much,
sorry
because
I
don't
see
the
panels
for
okay,
okay,
so
yeah.
So
there
is
examples
yeah
and
it's
also.
This
proposal
works
with
the
binding
extension,
because
if
you
will,
if
you
have
some
binding
like
http,
then
as
I
remember
in
the
headers,
you
must
exactly
write
some
schemas
for
the
headers
object
yeah.
H
So
you
can
also
make
it
with
this
proposal
and
also
with
the
extension.
So
it's
example
for
the
extension,
but
some
extension
like
they
need
schema
then
is
schema
and
you
exactly
define
the
schema
format
in
the
schema
and
this
given
format
yeah
about
the
person
implementation.
I
know
that
it's
the
imprint
implementation
details,
but
it
it
will
be
very,
very
easy
to
implement
in
the
parser
not
only
in
the
purchase,
but
also
for
the
another,
like
the
goal
parser,
because
we
make
something
like
the
inferencing
values.
H
Yes,
if
we
check
that
the
given
schema
has
the
schema
field,
then
we
can
make.
Then
we
can
read
these
values
from
the
schema
like
this
one
yeah.
So
the
notes,
I
think,
that
the
schema
format
at
the
message
level
should
be
deprecated,
so
it
will
be
breaking
change,
so
we
should
go
with
that
in
the
next
major
version.
H
Add
the
new
field
in
the
root,
the
default,
schema
format
and,
of
course,
change.
The
schema
object,
type
to
the
union
type,
the
second
one,
with
the
schema
in
the
schema
format,
fields,
yeah,
yeah
and
also
yeah,
and
the
last
thing
I
wrote
that
this
proposal
don't
doesn't
solve
the
problem
of
making
the
references
for
the
deep
values.
But
I
think
that
I
will
talk
about
that
after
your
question
to
the
first
part,
because
this
proposal
has
also
the
second
part.
H
A
A
H
Exactly
because,
of
course,
you
have
something
like
the
avro
and
drum
and
you
can
define
is
with
the
json
format.
Yes,
but
the
problem
is
something
like
the
string
format.
I
call
that
this
as
the
string
format
like
the
exactly
protobuf
grab,
color
and
x
as
that
and
because
you
cannot
make
you
know
the
xml
annotation
xml
tags
inside
the
json,
so
you
must
treat
it
as
the
string
so
by
this
I
would
like
to.
I
would
like
to
you
know,
show
that
with
this
proposal
you
can
also
use
the
string
format.
A
Yeah
yeah
yeah,
but
how
about
like?
So
because
I
don't
so.
My
question
would
be
like
I
guess
silly
because
I
don't
remember.
I
remember
that
some
time
ago
I
think,
from
with
nick
from
ibm.
I
had
similar
discussion
about
strings
in
here
when
we
were
talking
about
avro
and
I
think
he
asked
if
he
can
pass
afro
schema
as
a
string
and
not
formatted
json.
A
A
H
So
it
will
be
also
breaking
changes,
because
in
every
places
where
exactly
you
can
define
the
schema
object,
we
should
change
it
to
the
any
type.
Yes,
because
in
my
proposal
I
added
the
default
and
the
default
schema
format
field,
and
it
indicates
that,
for
example,
if
you
write
that
every
schema
in
your
specification
will
be
the
protobuf,
so
it
will
be
the
string
format.
H
B
Change
that,
but
it's
it's
gonna
be
a
bit
of
a
because
we
kind
of
pushing
the
limits
of
what
yaml
and
jason
can
even
represent
right.
That's
kind
of
the
core
issue
here
is
that
you
cannot
define
it
with
the
structure
that
avro
or
protobuf,
like
the
short,
their
structure
for
defining
messages
or
the
schema.
Whatever.
A
You,
as
far
as
I
understand
it's
only
a
challenge,
if
you,
if
the
proposal
also
wants
to
address
protocol,
if
it's
only
about
making
other
officially
supported,
schema
formats,
support
well
check,
wait.
Wait
because
I
I
just
realized
the
sentence
that
I
want
to
say
it's
so
complicated
that
I
don't
understand
it
already.
A
A
And
there's
nothing
about
protobuf,
and
what
I
want
to
understand
is
like
this
string
thingy
that
we're
now
discussing
it's
only
for
protopuff
case
right.
So
if
you
would
like
to
support
avro,
open
api
ram
data
models
or
whatever
or
json
or
actually
or
even
like
pure
json
schema
in
the
components
in
schemas,
you
can
do
it
without
this
change
for
string
support.
A
H
My
question
yeah
yeah,
as
I
remember
I
understand,
but
as
I
remember
there,
we
have
also
another
issue
for
that
that
at
the
moment,
with
the
current
specification,
we
cannot
define
the
other
or
ram
schemas
inside
the
component
schemas,
because
we
have
some,
probably
the
back
inside
the
json
schema,
but
it's
not
related
to
specification
yeah.
But
we
have
the
the
issue
for
that.
H
B
A
Yeah
exactly
actually
but
basically
schema
formats
that
anyway,
I
think
api
officially
does
not
support
yeah.
That's
what
I
wanted
to
clarify,
like
just
I'm
just
looking
at
the
proposal
like
what's
breaking
change
and
what's
really
needed
to
be
there
and
cause
the
breaking
change
and
what
is
a
actually
still
a
value
added,
but
doesn't
have
to
break
the
spec
yeah.
So.
H
Of
course,
if
you
go
only
with
the
json,
but
if
you
want
to
go
with
the
string,
the
problem,
but
I
wanna
support
also
the
string
formats,
because
we
have
the
item
in
the
future
or
panel
on
the
our
roadmap.
Yes,
so
for
that
I
also
add
some
examples:
how
to
exactly
handle
that
the
string
format
but
yeah
we
can,
for
example,
making
in
the
iteration.
Yes
go
first,
only
with
the
with
the
yama
formats
and
then
go
with
the
string
in
the
next
major
version.
It's
not
the
problem.
B
B
H
H
A
H
Resolver
or
something
like
that,
so
it
treats
the
the
content
from
the
file
that
it
isn't
the
json
as
the
normal
string.
Why?
Because,
if
you,
for
example,
parse
the
parts
some
value
to
json,
yes,
that
you
want
make
from
the
string
to
the
json
object,
some
value
that
isn't
the
object,
you
exactly
have
the
string
or
the
number,
because
the
string
and
the
number
is
also
the
instance
of
the
json
yeah,
because
I
don't
know
how
to
call
that.
But
it's
exactly
the
the
instance
of
the
json.
B
B
It's
it's
not
stated
anywhere.
I
think-
and
this
is
this-
is
more
or
less
a
problem,
so
we
actually
have
a
more
larger
problem
with
reference
altogether
in
the
specification
and
in
tooling,
which
lucas
will
try
to
clarify
in
a
couple
of
couple
of
days,
because
it's
I
just
had
a
discussion
with
with
ben
from
json
schema
as
well,
because.
B
With
the
newer
versions
of
json
schema,
ref
means
something
different
than
it
does
in
draft
seven
that
we
use
and
the
way
that
we
define
a
reference
object
in
the
specification
does
not
align
with
these
new
behaviors,
because
at
the
moment
we've
referenced
some
specification
about
json
referencing
back
in
2013.
I
think
it's
referencing
and
json
schema
does
not
use
that
anymore
and
it's
the
same
with
open
api,
open
api
define
their
own
behavior
for
what
ref
really
means.
B
B
B
Yes
and
our
password
fully
supports
and
allows
kind
of
this
inheritance
kind
of
behavior,
because
the
underlying
library
we
use
are
bugged
or
doesn't
follow
what
the
spec
actually
defines,
and
this
is
a
problem
for
go
java,
whatever
libraries
that
we
might
need
it
for
there
isn't
any
common
specification
and
tooling
to
this.
It's
all
kind
of
hands
off
and
say
this
is
just
the
behavior
that
we
decided
to
do
so.
We
are
kind
of
in
a
limbo
here.
A
We
don't
make
decisions
on
the
course,
so
I
shared
the
link
to
this
proposal
in
the
in
the
chat.
So
whoever
wants
to
jump
here
into
the
proposal
later
just
feel
free
to
do
it,
and
I
suggest
you
like
sync,
with
fiannas
on
his
findings
and
something
that
is
in
the
contribution
guide
and
I'm
gonna
talk
about
it
on
the
conference.
A
B
H
H
Yeah,
okay
yeah,
but
at
the
end,
because
I
said
that
this
proposal
has
two
parts:
the
first
part
with
this
references
with
the
string
formats
and
the
second
is
to
how
to
exactly
make
the
pointers
to
the
given
given
model
nested
models
inside
the
custom
format.
Because
at
the
moment
we
followed
by
the
json
pointers
and,
as
I
remember
in
the
other
ram,
you
have
the
another
format
for
the
pointers.
And
this
is
also
the
problem.
H
B
A
A
Okay,
thank
you
and
so
the
la
we
have
like
one
minute
left.
So
the
most
important
topic
can
you
stop
sharing
yeah,
so
the
most
important
topic,
which
is
normally,
I
would
do
it
at
the
beginning
of
the
meeting.
I
just
forgot
about
the
hackathon
and
maybe
somebody
just
joined
to
learn,
who
won
the
asking
ap
hackathon.
A
A
A
B
A
A
Well,
we
promised
to
announce,
then
we
will
up
from
when
then
we
make
sure
that
our
promises
are
made,
the
winner
of
the
asean
gpi
hackathon
by
so
we
had
like,
maybe
some
organizational,
so
we
had
10
people
from
the
community,
both
that
volunteered
to
go
through
the
submissions
of
the
hackathon.
We
had
nine
submissions.
A
E
A
Gonna
drop
him
a
dm
on
slack.
Definitely
so
congratulations
to
zovik
and
we
don't
have
a
third
place
because
votes
for
for
the
second
and
third
place
where
the
number
was
the
same,
like
the
same
amount
of
people
voted
for
two
submissions,
you
know
what
I
mean
right.
So
basically,
we
have
two
submissions
on
the
second
place
like
runner
up,
and
these
two
submissions
are
one
is
the
even
discovery
agent
with
async
api
output
from
greg
meldrum
and
the
other
one
is
async
api
blocks.
A
So
from
all
those
three
people
I
see
a's
on
the
call,
so
ace
congrats
for
being
a
runner-up,
and
we
also
like
by
like,
together
with
people
that
were
voting
on
proposals,
because
we
did
not
really
know
what
to
do
with.
If
we
have
two
people
like
two
people
having
a
second
place,
how
do
we
share
money?
A
So
basically,
the
decision
of
the
group
was
that
we
will
simply
have
two
second
prices,
so
we
don't
summarize
and
divide
by
two,
but
basically
both
people,
both
persons,
both
people
will
get
three
thousand
dollars
and
yeah.
The
first
place
gets
five
thousand
dollars
and
it's
mainly
because
we
can
do
it
and
we
can
be
so
nice,
mainly
thanks
to
our
platinum
sponsors
that
gave
us
enough
money
to
do
it,
but
I'm
not
gonna
now
quickly
mention
them.
A
A
So
that
will
all
follow.
Probably
today,
after
this
call
and
the
link
to
the
item
where
I
describe
it,
it's
gonna
be
it's
gonna,
be
in
the
in
the
meeting
notes
and
yes,
ace.
We're,
definitely
gonna,
send
you
some
swags
and
actually
every
participant
in
the
hackathon.
So
all
the
all
nine
people
will
get
a
swag
pack,
but
yeah
we're
gonna
contact
you
offline
and
yeah.
It's
five
minutes
pass.
Thank
you
all
for
joining
again.
Next
week,
tuesday,
wednesday
thursday,
we
have
a
passing
api
conference.