►
From YouTube: Contributor-first @AsyncAPI #2
Description
Date: 6th of October 2021
Edition: 2
Meeting designed for AsyncAPI contributors that can come and ask for help with first contribution.
All scheduled meeting can be found in AsyncAPI calendar https://calendar.google.com/calendar/u/0/embed?src=tbrbfq4de5bcngt8okvev4lstk@group.calendar.google.com
A
Hey
welcome
on
a
another
meeting
which
will
be
the
same
as
the
meeting
in
the
morning,
but
for
people
from
different
time
zone.
It's
a
contributor
first
meeting
for
async
api
community,
I'm
just
live
on
twitch,
twitter,
linkedin
and
youtube
and
of
course,
as
usual,
I
need
to
first
check
if
I'm
ready
live.
I
just
don't
trust
the
technology
that
much
and
I
just
need
to
make
sure
that
I'm
actually
audible,
because
in
the
past
I
had
a
bit
different
experience.
A
A
Okay,
cool,
it's
I'm
audible,
I'm
actually
audible,
to
get
some
more
viewers.
A
A
A
Now
let
me
check
if
we
can
get
a
bit
more
people
here,
I'll
put
a
message
in
slack.
A
A
A
A
If
we
just
have
two
viewers-
and
I
don't
know
anyway-
know
that
it's
just
you
and
and
jonas,
so
I
will
skip
with
a
regular
explanation
what
the
meeting
is
about
and
I
will
jump
to
explain
what
you
need,
but
before
I
need
to
do
some
promotion,
because
I
learned
a
a
new
tool,
actually
not
not
the
new
tool
I
use
it.
I
used
it
already
for
the
sick
meetings
for
asking
api,
but
the
tool
is
photo
pair,
dot,
com.
A
Yes,
jonas
is
helping
alejandra
today
on
a
spanish
speaking
conference.
So
good
luck,
yes,
yeah
but
yeah.
I
learned
a
new
tool
to
edit
photos
so
because
this
meeting,
I
also
on
these
meetings,
I
want
to
promote
our
conference
sponsors
and
look
what
I
have
like
get
ready
for
it.
A
A
So
whoever
is
watching
recording,
go
to
the
website
and
join
us
on
both
events
and
the
events
like
prices
for
the
hackathon
winners
like
you
can
win
5k
bucks,
if
you,
if
you
actually
win
the
hackathon,
so
I
think
it's
worth
it
and
we
have
like
in
the
morning.
I
had
this
stream
already
like
morning
my
morning,
which
is
europe
morning,
and
I
was
talking
about
one
sponsor
which
is
ibm,
but
now
I'm
gonna
talk
about
two
sponsors
and
wait
for
it.
Wait
for
this
amazing
graphical
stuff
that
I
did.
A
Ibm
that
joined
just
recently
as
a
platinum
sponsor
today,
like
I
think,
20
minutes
before
this
stream.
We
got
another
platinum
sponsor,
so
we
have
already
5k
a
bucks,
so
we
have
actually
prices
like
the
hackathon
is
now
covered,
thanks
to
these
two
amazing
platinum
sponsors,
which
is
ibm
and
ugly
real
time
so
huge.
Thank
you
to
both
of
ya.
Like
it's
amazing.
A
A
I
know
that
the
the
ugly
icon
has
those
white
edges,
but
it's
not
my
fault.
They
were
there
when
I,
when
I
woke
up
so
not
sure,
really
how
to
fix
them,
but
it's
pretty
good
anyway.
A
And
now
mark
so
interesting
question.
So
let
me
hide
those
amazing
sponsors
for
a
sec
and
let
me
show
a
comment
from
mark
so
by
the
way
hi
mark.
A
A
Oh,
there
is
a
google
mid
link,
but
I
didn't
add
it
really
yeah
yeah,
so
you
can
yeah.
So
basically,
the
idea
is
to
reach
as
many
people
as
possible,
so
also
people
that
are
shy
and
don't
want
to
join
life.
But
if
somebody
wants
to
like
join
me
like.
A
Like
a
human
showing
face
and
speaking
you're,
I
mean
feel
free
to
just
let
me
know:
I'm
gonna
invite
you
but
like
for
a
wider
audience,
it's
it's
a
stream
and
just
interact
through
the
chat.
A
So
that's.
If
it
comes
to
the
answer
to
the
question
from
mark
now,
anand
writes
google
counter
shows
it.
It
just
adds
it
on
its
own.
I
think
yeah,
that's
like
that's
my
that's
my
feeling.
Actually,
because
I
was
not
configuring.
Any
google
meets
stuff.
A
A
Okay,
now
I
I
think
I
removed
it,
so
it's
not
gonna
be
confusing
next
week's,
so
you
should
not
see
the
strange.
The
strange
google
meet
link
yeah
but,
like
I
said
like,
if
you
want
to
join
for
free,
just
let
me
know
but
yeah.
So
I
already
explained
the
like
the
sponsors
and
again
like
I'd
like
to
make
a
like
super
huge
shout
out
for
restream
io,
so
to
do
this
stream,
I'm
using
restream,
io
and
actually
the
conference
next
month
for
the
conference.
A
A
A
Okay,
so
alejandra
was
also
confused,
so
yeah,
sorry
for
about
the
confusion
that
should
be
removed
now
from
the
invite
and
and
but
yeah
you're
still
invited
to
jane
okay,
so
I
talked
to
you
about
the
the
sponsors
restream
I
o.
What
else
should
I
clarify?
A
I
don't
think
I
have
to
clarify
again:
what's
the
purpose
of
the
meeting,
so
basically,
if
you
are
interested
about
the
purpose
of
this
meeting,
why
I'm
here?
What
I'm
going
to
talk
about?
A
A
This
meeting
is
for
you,
so
you
can
ask
questions.
I
can
give
you
some
replies,
maybe
in
future
other
community
members
will
also
join
like
other
maintainers
and
explain
things
and
then
basing
on
your
feedback
on
your
questions.
We
know
what
knowledge
we
have
to
pass
on
you,
so
you
can
be
a
contributor
like
you
can
become
a
contributor
in
a
easier
way
for
you.
A
So
that's
the
that's.
The
plan
for
the
meeting
grab
your
not
like
grab
your
experience
and
and
then
work
on
on
contribution
guidelines,
but
we
also
have
oktoberfest
like
every
year,
so
we
have
some
issues
for
october
october
1st.
You
can
also
ask
this
some
questions
about
the
oktoberfest
issues
during
the
meeting
and
last
but
not
least,
we
have
also
a
asking
api
hackathon,
which
is
now
running
over
october.
A
I
know
there
are
some
teams
working
on
some
solutions,
so
whoever
wants
to
feels
blocked
or
did
not
start
yet
working
on
anything
and
need
some
guidance
just
feel
free
to
come
to
the
stream
and
ask
questions.
I
can
give
you
some.
Some
ideas
help
you
out
to
promote
what
you
produce
for
the
hackathon,
because
I
will
not
be
among
the
the
people
that
decide
if
given
hackathon
solution,
wins
or
not,
I'm
out
of
the
group.
So
I
can
give
you
advices.
A
A
A
Although
it's
a
good
time
for
vodka
by
the
way,
at
least
in
poland,
so
so
the
question
from
anand
is
as
a
contributor,
I
do
not
understand
the
github
actions
about
the
releases.
Can
you
talk
about
that?
And
yes,
I'd
love
to
talk
about
that
now
I
don't
have
any
ready
explanation,
because
the
question
was
not
asked
like
up
front,
which
is
totally
fine.
A
Even
if
you
would
ask
it
yesterday,
I
would
not
be
able
to
prepare
anything
specific.
So,
yes
mark
it's
water,
so
whatever
I'm
gonna
cover
I'll,
probably
just
jump
on
different
topics
about
releases
and
github
actions,
hopefully
help
understanding.
It
then
confusing
even
more
but
yeah.
Let
me
show
your
screen.
A
And
yeah,
so
the
anand
asking
is
asking
actually
because
anand
is
also
now
contributing
to
a
goldwater
mill
template.
A
A
It's
because
I'm
sure
anand
is
interested
like
by
the
how
it
works
that
we
get
that
we
get
this
this
version
here.
Okay,
because,
as
you
can
see,
the
version
is
not
created
by
a
human,
but
it's
created
by
a
a
bot,
which
is
definitely
not
a
human.
A
So
yeah,
first
fact
to
know
is
that
it's
fully
automated
like
there
is
no
single
person
behind
the
the
release
process.
The
whole
release
is
done
by
a
bot,
and
the
last
step
done
by
a
human
is
to
click
on
the
merge
button
of
the
pull
request,
and
the
only
requirement
that
must
be
done
has
to
be
done
by
a
person
that
is
merging,
pull
request
is
to
make
sure
that
there
is
a
proper
prefix
on
the
commit
message.
Now
what
I
mean,
let
me
show
you.
A
Let
me
show
you
now:
where
are
we
because
we
don't
see
any
requests
here?
Let's
explore.
First
of
all,
some
some,
oh
yeah,
you
see
like
how
amazing
rhythm
we
have
for
the
organization.
A
A
Oh
yeah
cool
and
it's
even
apr
from
daylane,
so
we're
gonna
do
some
practicing
on
them
on
a
request
from
dale.
So
to
explain
like
how
the
release
automation
of
the
release
works
is
again
like
so
showing
in
practice.
What
I
mean
by
the
prefix.
Is
you
create
a
a
title
for
for
your
pull
request
and
the
title
of
the
pull
request
always
needs
to
have
a
prefix.
A
A
Wow,
it's
it's
super
odd,
come
on
like
why
it's
not
here.
Is
it
because
it's
completed
successfully,
maybe
instead
of
react.
Let's
see.
A
No,
it's
a
draft.
You
have
all
the
draft
pr's.
No,
this
is
one.
This
one
is
not
okay.
So
it's
a
support
for
swagger
to
zero.
A
What
is
swagger
anyways
and
you
can
see
oh
yeah.
A
So
there,
on
the
on
the
ci
level,
when
you
create
apr,
we
have
a
dedicated
github
actions,
workflow.
That
makes
sure
that
your
pr
title
has
a
prefix,
and
so
that's
the
that's.
The
automation
that,
like
the
first
automation,
which
is
release
related
we're
making
sure
on
the
pr
level
that
that
the
title
is
created
with
a
proper
prefix
and
then
when
we
merge-
and
I
won't
be
able
to
merge
click
on
merge
here.
A
So
we
we
click
on
squash
and
merge
and
we
always
make
sure
that
whatever
was
in
the
title
is
reflected
in
the
comment
in
the
main
message
of
the
comet.
That
will
go
to
the
master
branch
so
and
that's
the
last
last
moment,
when
a
human
still
interacts
with
the
release
process,
we
have
future
plans
to
also
get
rid
of
it.
So
a
human
just
makes
a
comment
in
a
pr
like.
A
Please
merge
and
bot
will
merge,
but
for
now
that's
the
last
step
where,
where
human
is
involved
and
what
human
has
to
do
about,
the
prefix
just
needs
to
make
sure
that
the
prefix
has
is
named
properly
and
now.
Okay,
I
was
talking
about
this
prefix
all
the
time
now.
What
is
this
prefix
all
about.
A
So
there
is
a
I
mean
we
are
asking
api
spec.
So
obviously
we
love
other
specs.
So
there's
a
a
another
specification.
A
Called
conventional
comments,
which,
like
specifies
how
to
write,
comment,
messages
which
are
not
only
human,
readable
but
also
machine,
readable
so,
and
it's
basically
like
a
mandatory
step
for
us
to
have
release
automation
because
both
needs
to
know.
First
of
all,
if
both
has
to
release
something
and
if
it
has
to
be
master,
a
major
minor
or
a
patch
release.
And
that's
what
we
need
conventional
comets
for
and
quick
summary.
So,
basically,
so,
basically.
A
A
This
like
giving
hints
to
make
it
like
easier,
yeah,
exactly
okay,
so
like
the
basic
prefixes,
we
recommend
to
use
from
the
list
of
other
conventional
comets,
so
we
have
like
when
you
do
fix
bot
will
interpret
it
as
as
that
the
bot
has
to
release
a
patch
release
right
now,
then
we
have
feet
and
bot
will
interpret
it
as
okay,
it's
a
future,
so
it
should
be
a
minor
release.
A
Then
dogs
or
test
refactor.
These
are
a
aprs
that
are
not
released
triggering
and
they
are
just
to
to
understand
really
what's
happening
in
a
given
comet
so
that
it's
the
documentation
really
the
documentation
related.
It's
just
tests
related
or
refactoring,
so
you
know
what's
happening
in
the
comet
and
why?
Basically,
it's
not
triggering
a
release.
Now
the
major
release
can
be
triggered
by
any
of
the
prefixes
as
long
as
you
add
a
exclamation
mark.
So
let's
say
the
refactor,
maybe
is
not
changing.
A
The
the
refactor
is
not
like
changing,
let's
say
api,
but
it's
like
dramatic
dramatically
changing
the
the
the
the
architecture
of
the
library
and
you
would
like
to
have
a
major
release.
Then
you're
gonna
do
a
refactor,
exclamation
mark
column
and
then
the
name
of
the
comment,
and
but
here
we're
still
talking
about
just
a
specification.
A
It's
not
doing
really
any
automation.
It's
like
with
asking
api.
You
can
write
as
an
api
file
but
like
if
you
don't
have
tools
to
support
it.
It's
not
super
useful
right,
but
I'm
happy
honest
that
it's
already
helpful
for
you
what
I
just
explained
but
yeah.
So
we
have
so
you
know
what
is
happening
on
a
on
a
pr
level,
pr
title,
human
interaction
and
when
bot
starts
and
the
specification
behind
the
automation
now
now
what
really
happens
when
you
merge.
A
So
when
you
merge,
we
have
a
github
workflow.
A
That
is
called
if
node.js
release,
basically,
which
means
that
this
workflow
is
going
to
run
a
release
process,
but
but
only
for
node.js
projects.
A
A
Because
it's
designed
in
the
way
that
it
can
be
just
replicated
one
by
one
in
every
repo,
so
any
specific
customizations
to
the
release
like
let's
say
your
release
needs
a
bit
more
to
release
like
a
bit
like
additional,
specific
npm
package
or
whatever.
For
this
we
have
additional
workflows
and
that's
actually
with
react
component.
A
I
hope
I'm
not
putting
too
much
like
knowledge
on
you
now
and
to
not
complicate,
but
just
wanted
to
mention
like,
for
example,
because
you
can
think
like
how
can
you
have
a
generic
release
workflow
for
all,
so
it's
possible
because
we
we
basically
have
this
a
core
of
the
release.
But
if
you
have
some
something
custom-
and
I
think
we
have
it
only
for
two
different
projects-
you
simply
can
create
additional
workflow.
A
That
will
react
once
the
github
release
is
created
and
then
you
can
release
additional
stuff
like
in
case
of
react
component,
we're
also
releasing
a
web
component
and
and
other
things
but
yeah.
So
so,
basically
we
have
this
if
node.js
release
workflow
that
runs
whenever
there
is
a
push.
A
To
to
master
branch
and
then
in
some
cases
to
next
branch
or
a
release
branch,
that's
related
to
the
spec
release
and
and
some
release
candidates.
Let's
maybe
not
go
too
deep
in
this.
Let's
just
talk
about
like
there's
a
commit
done
to
the
master,
because
we
merged
a
request
with
a
prefix
and
what
happens
like
yeah
testing,
blah
blah,
blah,
boring
and
then
yeah.
We're
checking
out,
of
course,
then
checking
if
it's
really
node.js
project.
A
So
we
can
have
those
ifs
in
every
step
to
make
sure
that
there's
a
packages,
and
so
we
have
to
do
the
release,
we're
installing
dependencies.
A
But
the
most
important
is,
is
this,
so
every
single
repository
that
wants
to
is
a
node.js
project
and
not
yes,
I
said
yeah
a
nodejs
project
and
wants
to
be
released
to
npm
on
the
async
api
scope
on
npm
and
needs
to
have
needs
to
have
this
step
and
the
step
is
just
triggering
a
npm
run.
Release
script
from
package.json
and
yeah
has
some
secret
stuff,
and
what
is
this
npm
run
release
doing.
A
Npm
run
release
is
calling
semantic
release
and
that's
where
the
spec
meets
tools.
So
basically,
conventional
comets
is
a
specification
to
enable
machine,
readable
comments
and
semantic
release.
It's
like
it's
super
powerful
configurable,
with
a
lots
of
plugging
a
tool
to
that.
Can
that
supports
the
spec
and
can
actually
do
the
the
automated
releases,
so
you
just
call
semantic
release.
So
basically
it
means
you
have
to
have
semantic
release
in
your
development
dependencies
and
you
have
to
add
a
release
related
property
to
your
packet
jason.
A
Run
the
following
plugins
in
the
following
order:
so
there's
going
to
be
a
commit
analyzer
that
follows
typical
conventional
comments,
so
the
commit
analyzer
after
we
merge
commit
analyzer
checks,
all
the
comments
that
were
done
since
the
last
tag,
creation
or
release
creation
and
through
prefix
by
analyzing
prefix,
the
the
plugin
knows.
If
it's,
if
the
release
should
happen
and
what
kind
of
release
then
another
plugin
is
generating
the
release
notes
so.
A
This
is
purely
generated
from
the
from
the
comment
message
and
the
link
to
the
pull
request
and
to
the
comment
so
so
this
this
is
generated
thanks
to
this
plugin,
and
then
we
have
an
npm
plugin
with
information
for
the
plugin,
which
directory
should
be
used
for
a
for
a
for
publishing,
and
this,
as
the
name
shows
like
this
plugin
is
responsible
for
pushing
the
library,
the
new
version
of
the
library
to
the
to
npm
and
last
but
not
least,
also
do
it
in
the
in
the
github
releases,
so
yeah.
A
So
here
and
yeah.
All
those
plugins
of
course
have
to
be
in
in
conventional,
not
in
conventional
in
the
in
the
death
dependencies,
so
yeah,
that's
that
would
be.
That
would
be
it.
So
if
it
comes
to
the
spec
behind
the
automation,
you
know
what
it
is
now
if
it
comes
to
the
tooling
behind
it,
you
know
what
it
is
now
some
details,
I
guess
would
be
useful.
A
A
It
is
called
this
property
yeah
publish,
config,
that's
a
yeah
npm
specific
thing.
So
basically,
if
you
don't
have
this
property
in
your
package.json
and
you
did
not
yet
release
a
package
under
any
version
and
it's
your
first
package
release,
it's
going
to
fail,
it's
a
protection.
They
added
at
some
point
of
time,
because
people
were
complaining
that
by
mistake
they
were
publishing
a
package
and
it
was
by
default
public
public,
which
I
think
it's
user's
fault
and
should
not
be
changed
but
yeah
anyway.
A
Look
at
this
like
seven
days
ago
in
the
go
water
meal
project
I
created
manually
this
pretty
dummy
release
and
marked
it
as
zero
zero
one.
Now
the
reason
is.
A
The
reason
is
because-
and
I'm
not
hundred
percent
sure
about
the
reasoning
here
who
actually,
who,
like
initially
in
the
semantic
release,
plugin
decided
to
do
it,
but
basically
semantic
release
tool,
treats
semver
specific
like
semver
december.
A
specification
now
december
is
like
guidelines.
How
do
you
say
like
best
practice.
A
A
How
do
you
mark
release
candidates,
etc,
etc,
etc,
and
the
the
semantic
release
tool
treats
semantic
versioning
specification
in
the
way
that
if
you
release
a
package
for
the
first
time,
it
must
be
1,
0,
0
or
1.0.0,
which
it
should
be
a
major
release
when
you
first
release
and
therefore,
if
I
would
not
create
this
initial
zero
zero
one
release
with
the
first
release,
we
would
get
a
water
me
released
under
one
zero
zero.
A
Now
why
they
decided
this
way.
I
think
it's
a
discussion
on
for
probably
different
call
and-
and
we
could
make
a
good
argue
here-
that's
something
that
we
did
not
yet
discuss
in
async
api
in
our
maintainers
group.
There
are
different
opinions
here
and
I
I
personally
have
mixed
feelings
about
the
approach.
A
If
we
should
always
release
major
first
and
then
simply
go
further
or
or
if
it's
a
good
habit,
that
the
community,
like
development
community,
like
javascript
developers,
community,
took
that
you
work
on
the
library
forever
and
do
not
release
major
release,
which
makes
you
always
on
a
safe
position
that
okay,
it's
not
major,
so
you
should
not
use
it
in
production,
so
I'm
safe.
If
you
complain
and
I'm
safe.
A
If
I
want
to
break
api
and-
and
many
people
think
this
way
and
choose
not
to
release
major
quickly,
so
they
can
work
for
a
very
long
time
on
a
package
before
it
reaches
a
major
release.
A
You're,
not
gonna,
break
api.
Just
like
this
for
patch
releases
or
for
a
minor
releases,
you
will
feel
like
you're.
You
should.
I
mean
at
least
I
would
feel
responsible,
like
for
the
community
of
my
library,
that
I
probably
should
not
be
breaking
api.
A
That
often
so
when
I
in
the
past
was,
I
was
supporting
this
kind
of
approach
that
you
can.
A
Not
release
major
forever,
but
but
last
month's
I'm
I'm
thinking
that
it
leads
people
to
an
approach
that
they're
just
afraid
of
releasing
major
while
at
the
end
like.
A
For
me,
it's
just
a
signal
that
the
version
is
actually
somebody's
working
on
the
on
the
on
the
library
quite
often
so
yeah
it's,
I
don't
think
it
I
mean.
Basically,
this
whole
conversation
doesn't
make
sense
in
the
topic
of
explaining
how
the
automation
works
but
yeah,
for
now
we
did
not
yet
have.
We
did
not
have
yet
any
open
discussion
about
it.
So
we
always
follow
this
old
approach,
so
we
make
a
manual
0,
0
1
release
and
then
go
further
with
next
releases.
Until
we
do
a
major
release.
A
Now
what
else
should
I
explain
yeah?
What
else
should
explain?
One
more
thing
like
what
about
other
languages
I
mean
like
as
like
in
async
api.
We
don't
have
only
javascript
typescript
packages.
We
have
also
go.
We
have
java,
so
the
cool
stuff
is.
We
can
still
do
the
same
and
we
don't
even
have
to
have
package.json
in
go
project
like
who
would
like
to
see
a
packages
in
a
go
project
right
so
I'll.
Just
quickly
briefly
show
you.
A
And
look,
but
the
the
release
is
still
done
by
semantic
release
package.
Even
though
semantic
release
package
is
a
npm
package,
we,
what
we
just
do
is
instead
of
having
an
npm
script,
which
is
not
needed,
because
there's
npx
right
so
and
in
github
actions,
the
node.js
environment.
A
A
We
only
need
to
do
two
additional
things
manually
install
one
of
the
plugins,
which
is
the
conventional
changelog
conventional
comets
plugin,
where
we
enforce
the
the
classical
conventional
comets
and
one
more
thing
is
the
configuration
for
semantic
release
which
normally
you
put
in
the
package
json,
but
you
don't
have
to
so.
We
have
a
release
rc
file
where
we
have
probably
whatever
you
see
here.
You
probably
already
understand
that
it's
the
same
as
you
could
see
in
the
packages
that
I
showed
like
a
list
of
plugins
commit
analyzer
release,
notes
generator.
A
Npm
plugin
is
not
used,
obviously,
because
we're
not
pushing
go
packages
to
npm,
and
then
we
just
go
with
github
plugin
and
in
this
case
we're
just
pushing
some
assets.
Some
like
generated
executables
like
binary
files
to
to
github
release,
because
in
github
release
you
cannot
touch
some
additional
files.
A
A
And
aha
yeah,
you
might
think
like,
so
why,
in
the
other
project
you
had
to
install
some
plugins,
and
here
you
just
have
to
install
this
particular
plugin.
It's
because
after
some
time,
unfortunately,
I
didn't
know
it
up
front.
The
semantic
release
package
is
pre-bundled
with
some
default
plugins,
so
the
the
plugins
like
commit
analyzer
release,
notes
generator
github,
they're,
already
part
of
the
semantic
release
package.
A
So
if
you
ask
me,
I
wish,
but
I
know
I
will
probably
never
have
time
to
do
it.
I
wish
that
we
simplified
the
configuration
in
our
nodejs
templates
because
I
think-
and
I
guess
you're
unders.
You
agree
with
me
like
having
this
and
just
mpx
semantic
release
and
such
a
simple
file.
A
It's
much
cleaner
for
me
than
the
whole
versioning,
with
package.json
having
packages
and
polluted,
with
the
release,
configuration
and
especially
like
the
the
problem
of
handling
like
the
the
versions
of
the
plugins.
A
A
I
don't
think
we're
gonna
ever
do
it.
I
mean
it
works
now
and
we
have
better
things
to
to
improve
than
just
having
a
cleaner
configuration.
I
guess.
A
So
anand
did
I
answer
it
the
right
way
or
are
there
some
still
open
topics
I
did
not
cover
if
it
comes
to
the
release,
automation.
A
We
have
a
release,
announcements
workflow,
so
we
basically
when
the
release
is
published.
We
send
also
a
slack
message
in
our
dedicated
slack
channel
with
information
like
this
package
got
released,
but
we
do
it
for
any
release
and
in
case
of
major
on
minor
releases,
we
also
automatically
send
a.
A
Sentence:
a
tweet
to
asking
api
initiative
twitter
account
with
the
information
about
the
new
release
and
who,
who
created
the
release
you
can
see
so,
for
example,.
A
A
Promotion
so
I'd
like
to
thank
you,
send
a
thank
you
to
our
platinum
sponsors
for
asking
api,
hackathon
and
a
conference.
A
So
we
have
ibm
that
joined
us
yesterday
or
actually
two
days
ago
as
a
platinum
sponsor,
so
they
were
first
actually
to
support
the
hackathon
and
the
conference,
and
today
we've
got
ably
so
the
this
logo
represents
ugly
real
time.
A
I
think
I
can
actually
show
you
the
website,
like
everybody,
knows
ibm,
and
I
think
many
people
should
also
know
ugly
real
time,
because
apple
realtime
also
integrates
with
async
api
they're
doing
quite
some
cool
stuff.
A
A
A
In
the
meantime,
I'm
gonna
share
something
with
you.
Maybe
it's
gonna
be
interesting
for
you,
so
the
this
this
contributor
first
meetings
is
not
the
only
way
we
want
to
help
out
people
to
become
contributors.
A
We
also
have
like
the
conference
that
we
have
in
november.
It's
a
three
days
conference,
but
the
first
day
first
day
is
purely
contributor
related.
So
it's
a
contributor
summit,
so
I
will
share
a
link,
a
share,
a
screen,
and
I
think
I
have
some
caption
ready.
Yeah.
A
Contributor
summit,
but
wait
with
the
overlay
my
head,
but
it's
not
visible.
I
have
to
show
my
face
come
on.
I
need
to
turn
it
off.
So
we
we
have
a
discussion
in
our
community
repo
about
the
contributor
summit
feel
free
to
get.
There
suggest
what
talk
topics
you
would
like
to
have
covered
or
if
you
would
like
to
cover
some
topic
for
contributors.
A
There
are
three
proposals
so
far,
so
I
proposed
a
talk
that
is
called
contributor
journey
to
become
as
an
api
tsc
member
a
how
to
contribute
to
asking
api
specification
and
also
there's
a
proposal
from
alejandra
about
how
to
contribute
to
an
api
developer
documentation.
A
A
I
think
it's
a
perfect
platform
for
you
to
explain
how
to
contribute
to
modalina
project,
so
you
can
attract
a
wider
community,
especially
in
the
topic
that
we
discussed
some
time
ago
about
like
getting
more
people
from
different
areas
that
know
different
programming
languages
to
contribute
to
modeling.
So
we
can
also
generate
models
for
different
programming
languages,
so
might
be
that
contributor
summit,
it's
a
good
place
to
to
talk
about
it
like,
in
short,
like
how
to
start
with
modelina.
A
What's
the
point
and
how
to
contribute
or
like
anand
might
be
that,
like
think
about
it,
maybe
you'd
like
to
present,
like
your
experience
with
the
with
the
contributions
you
you
did
to
the
project
like
you,
basically
rewrote
one
code
generator,
maybe
and
consider.
A
Maybe
it
would,
I
I
think
actually
not
maybe
like
it
would
be
nice
to
have
a
a
talk
on
the
contributor
summit
that,
where
we
cover
like
how
to
create
a
a
generator
template,
how
to
contribute
a
generator
template
that
might
be
super
useful
for
for
contributors
so
think
about
it.
A
Think
about
it,
like
the
the
cool
thing
about
contributor
summit,
is
that
this
contributor
summit
is
not
part
of
the
regular
call
for
papers
so
because
call
for
papers
cover
only
the
second
and
the
third
day,
and
the
contributor
summit
is
mainly
like
on
the
contributor
summit.
You
only
have
people
presenting
the
people
that
are
maintainers
or
psc
members
or
people
like
fully
involved
in
the
project
that
can
talk
about
the
about
yeah
contributing
to
the
to
the
project.
A
So
the
list
of
people
is
pretty
small.
We
won't
get
so
many
proposals
and
it's
up
to
us
maintainers
and
tsc
members
to
decide
like
what
talks
we
think
should
be
there
on
the
agenda.
So
it's
much
it's
much
easier
to
get
on
the
on
the
list.
A
I
personally
recommend
starting
as
a
speaker,
it's
it's
cool
thing
and
gives
you
adrenaline,
which
is
also
a
good
thing.
I've
heard.
A
So
I
think
it's
almost
like
it's
it's
the
end.
So
let
me
finish
with
some
words.
I'm
just
gonna
share
with
you
like
what
I
did
in
yes,
I
will
display
a
comment
from
jonas
because
I
think
he
has
a
wish
that
most
of
us
have
and
I'm
afraid
that,
if
48
hours
that
at
some
point
of
time,
48
hours
would
not
be
enough
for
the
day,
but
yeah
would
be
awesome.
A
Come
on
jonas,
you
can't
be
so
again
like
what
attitude
like
like
no.
A
The
thing
about
creating
talks
is
that
it
takes
time
only
when
you
start
doing
it
like
it's
your
first
presentation,
maybe
second,
maybe
third,
but
then
over
time.
It's
easy.
It's
easy,
like
coding,
really
like
believe
me,
it's
super
easy,
that's
why
you
should
practice
and
you
should
actually
apply
and
do
a
presentation
about
modelina.
A
A
So
what
I
wanted
to
show
you
at
the
end
is
that
when
I
was
doing
the
stream
in
the
morning
there
were
not
so
many
specific
questions
like
I
didn't
get
any
nice
like
nice.
Like
very
good
specific
question
about
the
like
anans
asked
about
explaining
the.
A
I
I
can't
when
I'm
trying
to
be
serious,
I
cannot
read
chat
like
I
seriously
cannot
reach
out.
I
have
to
improve
in
the
future
and
probably
block
jonas
so
and
what?
What
else?
What
was
I
supposed
to
talk
about?
Yeah
yeah,
so
there
I
mean
now
during
this
stream.
I
was
talking
about
release
a
lot
because
of
a
great
question
from
anand
in
the
first
stream.
I
did
not
have
too
many
too
many
questions
like
specific
that
I
would
have
to
explain.
A
So
I
know
that
there
are
some
comments
in
the
chat.
I'm
not
gonna
read
them
now.
So
what
you
see
can
see
on
the
screen
is
that
I
was
real
time
working
on
a
on
a
like
plan
for
the
presentation
for
for
what
for
for
the
contributor
summit.
A
So,
like
jonas,
look,
how
simple
it
is
you
just
open
a
mind
map
you
just
and
it
took
me
like.
I
don't
know,
20
minutes
to
come
up
with
a
first
set
of
slides
ideas,
about
open
governance
and
the
same
like
the
others
will
also
take
not
much
time.
I
guess
I
think
I
try,
I
believe
so.
A
So.
Look
like
it's
not
really
complicated,
like
with
proper
attitude
with
proper
attitude.
You
you
can
do
it,
you
can
do
it
now.
There
is
a
question
from
aryun
hi
aryan.
By
the
way,
I
just
checked
that
the
output
volume
in
all
the
stream
platforms
is
kind
of
low
or
is
it
just
me?
I
don't
know
cans
like
you
mean
even
even
youtube.
A
Okay,
thank
you
aland.
So
I'd
love
to
help
you
anand
aryan,
but
it's
four
past
seven
here.
A
And
what
I
think
perhaps
booker
speaks
softly.
Oh
thank
you.
I
always.
I
always
knew
my
my
voice
is
soft
and
calm,
and
I
I
make
people
feel
good
when
I'm
speaking.
Thank
you
alejandra.
Thank
you
at
least
that's
what
I
understood
from
your
question.
I
and
I
don't
really
care
if
I'm
wrong
so.
A
A
A
I
personally
don't
expect
more
than
10
submission
submissions
for
the
hackathon
would
be
nice
to
have
more,
but
we
organized
everything
pretty
late
if
we
get
at
least
10
submissions
for
the
hackathon,
that
would
be
awesome
but,
like
it
basically
means
if
we
have
10
submissions
and
we
have
three
prices-
five
thousand
dollars,
three
thousand
dollars
and
one
thousand
dollars.
A
A
Who
says,
I
can't
basically
who
says
I
can't
and
by
the
way,
like
looking
on
alejandra
and
jonas,
how
they're
handling
the
chat?
I
wish
you
good
luck
on
your
presentation
in
few
hours
or
and
basically
like,
because
we
have
some
some
other
vlogs
here
I
could
like.
A
A
I'm
trying
to
find
it.
Yes,
yes,
yeah,
I'm
gonna
share
a
screen.
A
A
A
Two
hours:
okay,
so
if
you
are
from
the
americas
time
zone
12
pm
pst,
which
means
in
two
hours
alejandra,
will
have
a
presentation.
A
workshop
on
a
conference
called
ccoss,
which
is
cc
open,
source
software,
como
country,
como,
contributor
country,
como,.
A
Open
source
software,
dot,
org
and
alejandra
will
talk
about
how
to
contribute
to
as
an
api,
and
the
workshop
is
gonna
be
in
spanish.
So
you.
A
As
I
see
you
have
a
good
time
there,
so
yeah,
you
definitely
have
to
join
share
the
share.
The
information
with
your
friends
who
knows
spanish
are
from
from
yeah,
basically
the
whole
america.
A
Yeah:
okay,
it's
enough!
It's
seven!
I
have
to
spend
some
time
with
my
kids
and
my
wife
as
well,
so
thanks.
Thank
you.
A
lot
for
joining
next
stream
is
next
wednesday.
A
Next
week,
wednesday-
and
I'm
already
sad
that
we
have
to
wait
until
next
wednesday
but
yeah,
there
are
other
things
to
do
as
well.
So
yeah,
bye,
bye.