►
From YouTube: Contributor-first @AsyncAPI #8
Description
Date: 27th of October 2021
Edition: 8
Meeting designed for AsyncAPI contributors that can come and ask for help with the first contribution.
All scheduled meetings can be found in the AsyncAPI calendar https://calendar.google.com/calendar/u/0/embed?src=tbrbfq4de5bcngt8okvev4lstk@group.calendar.google.com or as a list here https://github.com/asyncapi/community/labels/meeting
A
Noon,
hello,
my
name
is
vukash
and
I
welcome
you
on
the
eighth
episode
of
contributor
first
meeting,
and
I
know
that
my
first
words
always
go
to
nowhere
unless
you're
watching
the
recording.
A
So
before
I
jump
into
the
topic
that
we're
gonna
handle
today
like
more
explanation
on
what
we're
gonna
gonna
do
and
like
basically,
what's
the
meeting
for
and
let
me
first
double
check
and
make
sure
that
everything
works
as
expected
in
youtube.
A
Although
we
are
streaming
to
other
social
media,
so
just
bear
with
me.
A
So
yeah,
so
the
the
contributor
first
meeting
is
for
people
that
want
to
contribute
for
the
first
time,
but
not
necessarily
for
the
first
time.
Maybe
you
just
want
to
contribute
to
some
different
part
of
fasting
api
and
you'd
like
to
ask
some
questions
to
one
of
the
maintainers.
A
So
that's
that's
the
main
goal
behind
contributor
first
to
be
here
mainly
only
for
contributors,
because
for
other
community
members
we
have
different
meetings
at
using
api.
This
one
is
purely
for
contributors
and
it
was
supposed
to
be
only
in
october,
which
means
like
this
episode
should
be
the
last
one.
A
It
was
just
a
trial
like
I
just
wanted
to
make
sure
that
it
makes
sense
to
do
it
that
people
will
come
that
people
will
find
it
useful
and
also
learn
from
from
you
folks,
like
what
questions
you
have
in
your
heads
in
your
minds
when
you
want
to
contribute
to
the
project
like
to
understand,
because
we
know
that
we
need
to
provide
a
good
contribution
guidelines
in
the
project,
but
like
it's
always
better
to
to
understand.
First,
the
audience
and
like
the
problems
you
have.
A
Yeah,
I
think
it's
the
result
is
pretty
good.
People
like
it
and
we're
gonna
continue,
not
sure
yet
the
schedule
long
term.
Definitely
it's
not
gonna
be
every
week
twice
a
day.
A
It
might
change
to
every
week
once
a
day
or
like
with
the
sick
community
meetings.
We're
just
gonna
switch
with
the
sikh
meetings
like
one
week,
segmenting
the
other
a
week,
contributor
first
meeting,
but
let's
say:
let's
see
how
it
goes,
but
until
the
conference
we're
gonna,
do
it
the
same
way.
We
did
it
in
october,
so
twice
twice
a
week
so
but
yeah
so
we
I
see
some
people
are
already
in
the
like
watching
this
stream.
A
A
A
Let's
see
if
the
overlay
works
unfortunately
still
doesn't
work.
I
need
to
talk
to
the
restroom
io
folks,
so
you
cannot
see
all
the
comments
so
because,
and
the
issue
is
that
you
can't
see
all
the
comments
is
that,
like
some
people
watch
us
on
twitch,
some
people
watch
us
on
youtube
and,
like
you
can't
see
all
the
comments
like
when
you're
in
twitch,
you
can't
see
youtube
comments
so
yeah.
Basically,
let's,
let's
show
so
here's
jonas
positively
set
for
the
meeting.
A
B
B
Okay
sure
hi
everyone
for
anyone
that
doesn't
know
me,
I'm
alejandra
online.
You
can
find
me
there
and
I
joined
a
postman
working
for
the
open
source
size
about
it
was
like
august
30,
something
like
that.
So
I'm
pretty
excited
to
be
here.
I
really
like
it,
and
I
have
to
say
that,
because
lucas
is
watching
this
so.
A
A
A
More
companies
that
would
like
to
be
platinum
sponsors.
Just
please
let
me
let
me
know,
I'm
good
on
go
good,
taking
money
from
the
companies,
so
I
can.
I
can
approach
them
okay,
so
I
think
the
best
way
would
be
if
we
start
with
complaining
on
current
documentation
like
saying
how
bad
it
is.
B
Oh
wait:
let
me
make
sure
that
I
only
have
stuff
for
this
studio
live
thing.
Give
me
one
second,
to
open
up
my
stuff.
A
A
So
like,
basically,
today
we're
gonna
talk
about
like
first
okay,
I
don't
have
to.
A
A
A
For
me,
it's
okay,
but
like
can
you
confirm
in
the
in
the
chat
folks
like?
Is
it
okay?
Can
you
can
you
see
like
the
navigation?
A
So
if
alejandra
will
complain
on
the
names
of
the
headings
or
particular
documents,
you
know
what
she's
referring
to
just
at
least
one
person.
Please
please
write
in
comments
like
all
is
nicely
visible.
A
B
B
No,
it
doesn't
nope,
oh
so,
but
we're
not
really
going
to
read
the
documentation,
so
I
think
it
could
work.
We
just
need
to
be
able
to
see.
What's
going
on,
I
guess
all
right
cool,
so
one
of
the
things
that
we
want
to
change
is
having
a
better
section
for
tools.
B
So,
for
example,
right
now,
if
we
go
to
our
current
section
and
tooling,
you
can
see
that
it's
just
one
very
long
page.
That
shows
you
of
course,
a
list
of
all
the
tools
and
then
we
could
go
ahead
and
click
on
each
one
of
these
and
see
what
where
these
tools
are
hosted
or
the
github
repo
and
see
if
that
repo
has
documentation
in
the
readme.
But
that's
not
really,
you
know
a
good
experience
right.
B
That's
not
really
the
way
you
wanna
document
tools
in
a
documentation
website,
so
now
that
we
actually
have
a
bigger
team
to
where
we
can
start
making
some
of
these
improvements,
one
of
the
things
that
we're
going
to
work
on
is
making
an
actual
tool
section
that
actually
has
subsections
documenting
how
all
of
our
different
tools
work.
B
The
other
thing
is:
if
we
go
over
here
to
tutorials,
you
can
see
that
we
only
have
really
two,
and
I
mean
that's
better
than
nothing
of
course.
But
of
course
we
have
a
lot
more
tutorials
that
need
to
be
written
and
a
lot
more
beginner
things
to
explain
to
people
that
are
new
to
async
api.
So
we
absolutely
need
to
add
a
lot
more
tutorials.
B
The
other
thing
that
I
want
to
talk
about
and
that
lucas-
and
I
are
both
very
excited
about
as
well-
is
that
you'll
notice
our
current
content
buckets.
We
have,
for
example,
this
getting
started
section
and
it
walks
us
through
building
an
async
api
file
and
document
and
how
each
of
those
sections
work
and
it
we
also
have
a
section
introducing
us
to
what
event
driven
architectures
are.
B
But
you
know
we
don't
really
have
a
concept
section
where
we
explain
all
the
different
terms
in
the
async
api
spec
and
really
dive
into
a
deeper
detail
of
what
they
are
and
how
you
use
them.
And
we
do
have
this
specific
say.
Sorry,
words
in
english
specification
section
here
and
yes,
it
has
does
a
really
great
job
with
the
definitions
section
of
explaining
at
least
the
the
you
know.
At
least
it
gives
you
a
brief
introduction
to
what
each
one
of
these
things
are
each
one
of
these
terms.
B
But
I
don't
know
about
you
if
I'm
completely
new-
and
I
don't
know
anything-
I
want
to
know
a
lot
more
than
one
tiny
paragraph
about
what
a
producer
is
and
also
these
are
not
the
only
things
that
need
to
be
defined
and
explained.
There's
other
terms
like,
I
believe
the
word
traits
that
term
and
concept
also
needs
to
be
added.
B
So
we
want
to
have
a
whole
section
where
we
actually
deep
dive
and
explain
in
more
detail
and
with
diagrams,
and
you
know,
good
images
to
explain
visually
each
of
these
concepts
and
terms
and
then
really
we'd
end
up
having
kind
of
like
new
content
sections,
you
wouldn't
see
it
exactly
the
way
you're
seeing
these
main
headers
here,
you
know
getting
started
tutorial
specification
community,
so
that
would
actually
change,
and
let
me
show
you
folks
a
little
bit
more
about
what
we're
talking
about.
B
So
I'm
going
to
open
another
site
that
I
want
us
to
look
at
and
can
you
guys
see
it
okay?
Does
it
look
good.
B
B
Cool
awesome,
so
I
want
to
introduce
you
to
this
methodology
if
you
haven't
used
or
heard
of
it
before
did,
and
I
hope
I'm
pronouncing
it
correctly.
B
The
attacks,
the
ataxis
framework-
and
it
basically
is
an
engineering
documentation
framework
that
classifies
documentation,
content
and
usually
about
four
main
buckets,
and
so
we're
looking
at
things
that
you've
probably
already
heard
of
before,
like
the
content
of
tutorials
like
that,
makes
sense
and
then
something
reference
you've
probably
seen
that
before,
and
that
would
be
things
such
as
putting
the
cli
and
the
spec
information
underneath
reference
and
then
explanation
or
concepts
which
we
were
just
talking
about
earlier,
that
we
want
to
add
ourselves
to
our
site
and
then
there's
this
other
idea
of
a
how-to
guide
and
on
this
methodology.
B
If
you're
wondering
what
the
difference
is
between
a
tutorial
and
a
how-to
guide,
basically
think
of
it
as
a
tutorial
is
something
to
introduce
your
audience
a
user
accompany
anyone
to
the
main.
You
know
things
of
abcs,
of
how
to
spin
up
an
environment
or
how
to
do
a
thing
with
your
product
or
your
api
or
whatever.
It
is
that
you're
working
with
so
it's
not
that
it's
for
beginner
audiences
that
are
new
to
tech.
It's
that's
not
what
I'm
going
for
I'm.
B
What
we
mean
here
is
typical
startup
beginner
use
cases
as
in
getting
started
being
a
beginner
with
this
framework.
B
What
are
typical
things,
you're
gonna
need
to
know
to
get
started
and
then
a
how-to
guide,
on
the
other
hand,
is
going
to
be
more
about
very
specific
use
cases
that
you're
going
to
run
into
when
you're,
a
more
advanced
user
or
when
you're
someone,
that's
you
know
doing
a
lot
of
things
on
the
product
more
deep
dives,
and
it's
also
going
to
be
to
help
document
troubleshooting
for
your
user
on
typical
error
scenarios
and
issues
that
you
know
they're
going
to
encounter.
B
So
obviously
we
know
that
no
product,
no
api,
nothing
is
ever
100,
perfect
right,
there's
always
some
issue,
some
bug
that
we're
consistently
working
on
fixing
and
improving.
So
you
want
to
do
a
favor
to
your
users
and
your
community
and
make
sure
that
you
have
specific
how-to
guides
dedicated
to
those
troubleshooting
scenarios
and,
as
you
can
see,
that's
different
from
a
tutorial
that
we
just
explained
and
I'm
gonna
go
ahead
and
just
exit
out
of
that,
and
I
think
I'm
done
screen
sharing
for
now.
B
But
I
think
that
kind
of
gives
a
good
introduction
of
what
are
the
things
that
we
noticed
need
to
be
improved
in
our
current
doc
site.
I
gave
you
all
of
my
complaints
and
I
also
showed
you
now.
What
is
the
upcoming
thing
that
we're
trying
to
sorry
we're
trying
to
get
words?
B
And
then
I
also
showed
you
what
framework
we're
using
to
determine
our
new
content,
buckets
for
our
documentation,
site.
A
So
when
we
talk
about
those
content
buckets
does
it
mean
like
when
you,
when
you
showed
the
framework,
and
you
showed
this
diagram-
that
there
are
four
different
content
packets?
A
Does
it
always
does
it
map
directly
to
how
it's
going
to
look
like
in
the
ui
that
when
you
go
to
the
docs
view
you
will
first
have
you
will
actually
have
visual
four
different
sections
with
a
specific
bucket
name,
some
some
links
there
like
that,
would
that
this
will
be
a
starter
right
or
will
you
go
like
with
click
on
docs?
You
will
go
right
to
the
docks
like
now.
A
Is
it
so
my
question
is:
is
it
one
one
to
one
going
to
be
mapped
with
the
ui?
How
you
how
you
see
it,
because
now,
when
you
go,
you
go
into
the
navigation
into
docs,
you
select
getting
started
and
then
you
land
in
the
like
directly
in
the
docs.
You
have
everything
in
the
navigation
it
can
can
be
somehow
overwhelming.
A
A
Now
then,
then,
do
we
stay
with
the
top
nav,
where
we
have
dogs
and
then
getting
started
instead
of
specification?
We're
gonna
have
reference
instead
of
I
don't
remember,
what's
what's
what's
what
are
the
other
things
but
like
tutorial
and
how
to
and
then
we
click
on
them
and
then
land
on
some,
like
kind
of
a
landing
page
with
some
paths,
some
documents,
how
do
you?
How
do
you
see
it
like
in
action.
B
A
B
Okay
cool
so
for
a
second
I'm
going
to
go
to
our
main
website,
which
is
just
asyncapi.com
and
in
our
main
navigation.
B
We
have
this
stuff
like
learning
tools,
community
and
you're
like
okay,
but
you
know:
where
are
the
docs
right?
That's
my
first
question:
when
I
land
there,
of
course,
I
might
be
you
know
biased,
but
so
then
lucas
was
saying
hey.
So
then
is
this
going
to
stay
the
same
when
they
open
this
sub
navigation?
Are
we
still
going
to
see
these
main
options
getting
started?
B
Tutorials
use
cases
coming
soon.
You
know
so
in
my
mind,
I
visualize
this
changing
to
docs.
Instead
of
learning,
it'll
save
docs
and
then
it'll
display.
Instead,
the
new
content
buckets
that
we're
going
to
restructure
in
our
information
architecture.
B
So
now,
instead
of
saying
getting
started,
it
could
probably
say
concepts
and
tutorials
of
course
stays
the
same.
We'll
have
how-to
guys,
how-to
guides
sorry
and
then,
instead
of
a
sync
api
specification,
it'll,
probably
say
reference
and
explain
that
references.
You
know
our
spec
in
our
cli
here
in
the
and
then
when
we
go
to
the
actual
docs.
B
I
lucas
was
just
saying
how
the
current
experiences-
you
click
on,
say,
getting
started
and
then
boom
you're
straight
in
this
section
of
getting
started,
and
even
if
I
was
to
go
to
google
and
you
know,
go
to
sinkify.com
it
redirects,
as
lucas
just
pointed
out
to
here
the
getting
started
section.
It
takes
you
straight
to
the
introduction
and
there's
no
actual
home
page
really
to
the
docks
right.
So
this
is
what
you
first
land
on
and
so
I'd
to
what
lucas
was
saying
was
when
you
land
on
here?
B
Are
we
going
to
have
different
images
or
showing
a
road
map
or
something
that
explains
to
them
like
hey?
These
are
now
the
new
content
sections,
the
new
content
buckets,
and
so
I
agree
with
what
lucas
is
asking
about.
I
visualize
it,
for
example,
and
I'm
not
the
designers,
of
course,
we'll
ask
missy
turco
about
that
later,
but
I
basically
visualize
it
as
you
would
first
land
on
the
home
page
that
explains
to
you
like
hey.
These
are
our
four
or
five
main
content
buckets.
B
In
our
case,
we
determined
that
we're
going
to
have
concepts.
Tutorials
how-to
guides
reference
and
tools,
so
in
our
case
it's
going
to
be
five
content
buckets,
and
so
I'm
assuming
that
will
work
with
our
amazing
awesome.
New
ux,
ui
designer
and
she'll
help
us,
you
know,
find
a
nice
asset
or
design
how
those
five
content
blocks
can
be
introduced
to
you
in
the
first
home
page,
and
then
you
know
after
you
see
hey.
B
These
are
the
five
content
buckets
you
can
decide
where
to
click
on
and
go
through
there
or
maybe
here
you
know
in
the
navigation
it'll
now
have
you
know
the
new
content
buckets
those
five
ones
and
you
could
also
from
there
in
the
left
navigation
go
directly
to
the
new
stuff.
So
that's
kind
of
like
some
of
the
improvements
that
I
would
see,
but
of
course
I
emphasize
I'm
not
the
designer
and
we
still
need
to
work
with
missy
on
that.
A
Okay,
so
just
first
of
all,
a
reminder
for
others.
If
you'd
like
to
ask
some
questions,
feel
free
to
do
it
in
the
chat
and
again
I
forgot
to
put
a
link
so
there's
gonna,
I'm
gonna
send
a
link
to
twitch
and
youtube
if
you
want
to
join
us,
live
now
and
and
talk
together
with
us
on
this
topic,
you're
also
most
welcome.
So
you
can
join,
live
us
here
or
just
ask
in
the
in
the
chat,
but
going
back
to
the
topic.
A
So
let
me
try
to
summarize
so
f
like
so
we
want
to
basically
like,
of
course,
we
have
some
documentation
for
tools
and
like
some
existing
documentation,
but
we're
basically
restructuring
everything
from
scratch
right.
I
think
it's
safe
to
say
that
okay,
so
we're
first
of
all,
we're
gonna
have
to
like
the
work's
gonna
be
done
on
redesigning
the
the
website,
of
course,
in
docs
related
sites.
A
Right
then,
the
next
like
next
or
something
in
parallel.
A
We
will
have
to
come
up
with
the
with
probably
the
new
names,
so
we're
so
not
not
sure
how
you
saw
it,
but,
like
I
immediately
imagine
that
we
just
take
what
we
have
now
and
we
try
to
basically
like
in
the
excel
sheet
or
whatever
we
just
put
in
like
information.
Now
it
is
in
under
getting
started.
It
should
go
under
concepts,
probably
rename
title
and
some
content
adjustment
is
needed.
A
That's
how
I
imagine
like,
but
but
then
we
see
what's
missing
and
we're
adding
to
this
excel
sheet
or
whatever
it
doesn't
have
to
be
an
excel
sheet,
but
like
yeah,
I
don't
want
to
make
any
comments
about
microsoft
and
excel.
So,
let's
leave
it,
let's
leave
it
as
it
is
so
we're
gonna
we
first
we
actually
have
to
write
down
more
or
less
what
documents
we
are
missing
as
well
and
where
they
fit
in
under
which
packet
right
so
like.
How
do
we
call
it
like
planning?
It's
not
like
it's.
C
B
B
A
C
A
A
B
I
think
we
would
do
something
similar
to
what
we
did
for
hacktoberfest,
where
we
as
we
after
we
did
the
planning
and
realized
and
identified.
This
is
the
list
of
things
of
issues
that
need
to
be
done
for
the,
in
this
case,
the
docs.
Then
we
can
share
that
excel
or
whatever
we
use
could
be
a
git.
Our
github
project
board
excel
whatever
we
end
up
using,
we
can
there
share
that
with
our
community
and
now
say
hey
now.
B
A
Okay-
and
I
have
to
show
one
comment
from
youtube-
I
think
it's
a
perfect
comment
to
just
put
it
on
twitter
and
you're.
Gonna
have
like
thousands
of
retweets,
so
yeah
good
to
have
other
non-excel
fans
here
and
looking
at
the
comment
from
from
louis
like
basically,
I
think
it.
A
It
is
kind
of
pre-planning
session
we're
just
discussing
like
what's
what
is
needed
to
get
us
from
current
documentation
to
rocking
documentation
like
that
is
like
explaining
many
concepts
we
need
to
plan
it
and
then
share
the
plan
with
the
community
and
get
people
on
board
to
contribute
so
yeah.
C
A
B
One
that
comes
to
my
mind
is
I
definitely
admire
megan
sullivan
from
gatsby,
so
she's,
the
one
that
was
is
because
I
think
she
just
left
gatsby,
but
for
a
long
time
she
was
in
charge
of
the
gatsby
docks
and
she
actually
ended
up
doing
the
work
for
gatsby
docs
that
I'm
about
to
do
with
you
guys
for
our
docs,
and
she
used
the
same
framework
that
we
talked
about
today
and
she
relied
on.
B
You
know
social
media
and
things
like
I
don't
remember
she
uses
discord
or
if
they
use
slack,
but
she
also
relied
on
things
like
that
to
receive
community
feedback
for
changes
that
she
was
doing
to
the
docs,
and
then
I
know
that
she
would
also
receive
community
contributions.
Now
I
never
contributed
myself
to
gatsby
ducks,
but
I
know
that
that's
one
example
that
I
know
they
were
doing.
Megan
was
doing
a
really
good
job
with
that.
B
Oh
another
example
that
comes
to
mind
actually
is
kurt
temple.
I
think
his
twitter
handle
is
the
worst
dev
and
he
works
right
now:
a
developer
relations
manager
for
apollo
graphql,
and
so
he
and
his
team
and
the
developer
educator
team.
There
also
do
a
really
good
job
of
working
with
a
community
contributions
and
from
the
open
source
community
related
to
graphql
stuff.
So
I
would
say
that
he
and
his
docs
are
like
another
open
source,
good
one
that
I
I've
seen
do
cool
stuff
like
that.
A
Yeah,
I
think
it's
like
the
most
important
is
like
to
enable
people
to
contribute
like
because
now
we
have,
we
just
have
few
dogs,
and
I
mean
we're
gonna,
where
you're
gonna
put
additional
missing
dogs
like
we
just
have
one
bucket,
I
would
say
like.
Of
course
we
have
tutorials
getting
started
but
like
in
the
end
like
we
would
we
don't
have
any
specific
role
rules
to
follow,
so
it
was.
It
would
always
be
like
handled
case
by
case,
but
if
we
have
a
framework
in
place,
we
have
a
structure.
A
B
A
You
mean
dave's
tool,
the
the
one
that
he's
working
on
now.
Yes,
the
pushing
the
the
push
process.
B
And
all
the
cleanup
work-
that's
not
necessarily
writing
new
docs
and
the
nice
thing
about
creating
issues
for
cleanup
work.
Is
that
that's
a
contribution?
That
is
definitely
a
pretty
easy
to
do
so,
if
you're
newer
to
open
source
or
you're
new
to
technical
writing-
and
maybe
you
feel
shy
or
nervous-
maybe
picking
up
an
issue
to
create
a
new
doc
or
provide
ideas
for
a
new
tutorial
seems
very
daunting.
But
helping
with
all
these
important
cleanup
tasks
is
something
that,
like
you,
shouldn't,
feel
shy
or
scared
about.
B
A
So
exciting,
exciting
awesome
so
like.
Let
me
now
jump
into
the
what
what
alejandra
refers
to
so
basically
at
the
beginning,
alejandra
mentioned
that
we
have
in
the
current
docs.
We
have
these
tools
and
it's
just
a
list
of
tools
like
basically
a
mix
of
community
tools
and
tools
that
we
have
a
dozen
api.
A
So,
basically,
if
you
want
to
read
about
generator
you're
gonna,
you
want
to
read
about
modelina
parser,
whatever
you
have
to
go
to
github
and
and
read
markdown
files
there
now
in
case
of
parser,
it's
okay,
because
there's
not
much
docs.
Most
of
it
is
in
readme
plus
there's
an
api
markdown
generated,
so
not
much
docs.
But
then,
if
you
want
to
learn
modelina,
you
want
to
learn
generator.
A
There
are
many
documents
which
are
just
separated
by
by
markdown
files
put
in
a
repo.
So
you
end
up
going
to
docs.
You
have
bunch
of
markdown
files
like
if
you,
if
you
as
a
maintainer
of
the
repo
you
want
to
nicely
navigate
the
user,
then
you
have
to
maintain
special
readme
files,
like
with
some
a
bunch
of
links,
something
that
we
have
in
in
modelina
or
as
in
generator.
We
choose
to
still
put
most
of
the
content
in
one
markdown
file,
just
to
make
it
easier
to
navigate.
B
B
A
Actually,
that
was
the
like:
I'm
not
good
in
making
sure
that
I
have
my
t-shirts
ironed
ironed.
I
yawned,
how
do
you
have
this
iron
right,
so
that
was
the
only
one
I
had
in
my
in
my
drawer
that
was
still
like
good
to
wear.
The
rest
is
waiting
for
my
iron
anyway.
B
A
So
let
me
show
now
I
can,
I
think
I
can
share.
A
A
I
don't
think
it's
still
something
to
decide
to
have
a
discussion.
If
you
have
some
ideas
then,
like
just
like,
we
can
have
a
discussion
in
our
github
issues
on
the
on
the
website,
but
most
important
is
that
like
for
now,
when
you
want
to
read
about
generator,
you
just
just
select
generator.
A
You
see
some
nice
introduction
like
highlight
of
features
even
some
interactive
way
of
selecting.
What
templates
are
you
can
copy
some
code
kinda
nice,
but
then
you
have
to
go
to
view
on
github
and
then
go
to
docs
and
like
read
about
authoring
and,
like
super
super,
lengthy
markdown
file.
Now
the
idea
is
basically
that
you
don't
have
to
go
to
github
at
all,
unless
you
want
to
give
us
a
star
to
the
project
which
would
be
nice,
but
you
basically
go
to
like
you.
A
Have
this
like
a
landing
page
for
the
tool
you
go
to,
like
you,
have
some
button
like
read
the
docs
or
something
and
and
once
you
click
it,
you
get
this
kind
of
view
with
documentation
headings
on
the
left
and,
of
course,
once
you
select
a
given
document,
you
can
read
documentation
from
for
a
given
topic
and
now
how
do
we
do
it
like?
Of
course
we
will
not.
We
don't
want
to
duplicate
documentation,
so
have
it
under
generator
and
have
it
under
website.
A
We
also
don't
want
to
just
have
documentation
on
the
under
website,
because
that's
not
really
aligned
well
nice
with
the
I'm,
not
sure
if
it's
called
methodology,
but
basically
a
way
of
working
with
dogs
which
is
dogs
as
cold.
You
want
to
have
docs
in
a
repo.
A
You
want
to
work
with
them
the
same
way
as
you
do
with
code,
but
like
imagine,
if
you
have
some
code
in
repo
generator,
and
you
have
some
docs
related
to
generator
in
ripple
website,
then
like
the
the
life
cycle
of
the
dock,
is
totally
disconnected
from
the
from
the
life
cycle
of
the
code
of
the
generator.
So
you
you
should,
whenever
you
update
the
code,
you
should
update
documentation
at
the
same
time
and
best
do
it
in
the
same
pull
request
and
not
to
separate
repos
right.
So
we
want
to.
A
We
want
to
do
something
that
we
already
do
with
the
spec
so
with
the
spec.
What
I
meant
by
what
we
do
with
the
spec
when
you
go
to
learning,
and
you
read
async
api
specification
and
you
see
a
documentation
here,
it's
actually
one
to
one
like
content-wise,
it's
one-to-one
what
you
can
see
in
the
spec
repo
under
the
spec
document
and
it's
possible,
because
we
basically
have
a
github
workflow
that
listens
to
all
the
merge
I
commit
to
to
to
default
branch
events
on
github.
A
We
we
check
if
the
the
changes
in
the
default
branch
were
done
to
async
api
dot,
md
file,
and
if
we
see
that
like
actually
the
specification
file
was
modified,
then
we
have
a
special
work.
Workflow
that
takes
a
website.
A
Replaces
old,
spec
file
in
the
website
with
the
new
one
opens
up
apr,
and
then
we
have
bots
working
for
us
so
basically,
as
an
api
bot
opens
apr
and
github
actions
bot
and
merges
it
into
the
website,
and
it's
automatically
published
to
the
to
asking
api.com
and
like
if
we
can
do
it
with
the
spec,
if
we
can
do
it
with
technical
steering
committee
members
list,
because
we
do
something
similar
with
with
that
list,
why
not
scaling
it
to
to
the
dogs?
A
So,
basically,
whenever
we
have
a
pull
request,
where
we
modify
something
in
the
authoring.md
file,
the
workflow
will
pick
up.
Okay,
some
updates
were
done
in
documentation.
We
need
to
push
it
out
to
the
website.
So
again,
workflow
creates
a
pull
request
to
the
website,
repo
that
is
automatically
merged
by
a
bot
and
and
changes
are
redeployed
and
the
latest
documentation
with
some.
A
I
don't
know
like
bug,
fixes,
spinning
mistakes
or
actually
new
features
documented.
Everything
is
directly
visible
on
the
website.
A
That's
something
that
like
dave,
is
now
working
on
to
like
be
because
now
with
spec,
we
were
just
doing
it
like.
It
was
a
special
case,
but
it
worked
pretty
well
and
and
and
dave
is
putting
it
into
a
working
solution.
There
is
a
did
you
do.
You
know
where
to
find
the
the
issue
alejandra.
I
think
it's
in
the
website
report
should
be
in
the
website
right.
A
See
if
I
have
it,
I'm
gonna
quickly
open
it.
I'm
pretty
sure
that
they've
opened
apr
today,
yeah.
A
So
yeah
just
just
have
a
look
it's
still
in
draft,
but
there's
an
issue
linked
where
we
were
discussing
the
whole
concept
and
brainstorming
about
how
to
how
to
solve
it.
But
yeah.
Basically,
you
see
documentation
from
other
repos
also
in
the
website,
and
when
you
see
a
button
that
tells
you
edit
the
page
on
github,
it
will
not
open
on
the
website
repo.
A
It
will
open
in
a
specific
repo
where
the
content
is
actually
located,
which
is
really
neat
so
now,
once
you
know
more
or
less
how
it
works.
A
This
is
where
we
also
need
help.
So,
if,
like
once,
we
have
this
workflow
ready,
maybe
actually
I
actually
have
to
start
sharing
again
so,
for
example,
to
have
nice
nice
navigation
on
the
left
to
manipulate
the
order
of
the
files
in
what
order
they
will
display
in
the
in
the
navigation.
A
A
There
we
go
so
that's
the
front
matter
right,
so
you
put
a
title
that
will
be
visible
in
the
navigation.
The
date
not
necessarily
is
needed,
because
I
don't
think
anyone
would
edit
it.
So
probably
we
don't
need
it,
but
then
in
the
in
the
menu
you
can
say
like
okay,
it
should
be
visible
under
the
getting
started
or
tutorial
or
something
else,
and
this
one
is
the
words
that
it's
one
of
the
words
in
english.
A
A
You
have
to
mute
me.
Sorry,
I
have,
I
see
someone
in
the
waiting
room.
Can
you
hear
me?
Can
you
note
if
you
can
hear
me?
A
Okay,
I
think
you
can
hear
me
so
just
wait
a
minute.
I'm
gonna,
let
you
in,
but
I
just
want
to
finish
the
the
sentence
about
different
matter
so
like
basically
before
there's
like
we
have
someone
that
would
like
to
join
the
stream.
So
I'm
gonna,
let
you
in
in
a
second
but
just
don't
want
to
lose
the
flow
so
the
so
that's
the
that's
the
front
matter
that
we
will
have
to
add
to
this.
These
documents
like
if
we
want
to
push
documentation
from
modelina
to
the
website.
A
We
first
need
to
add
this
front,
monitor
like
decide
how
the
order
of
the
files
will
will
show
up
in
the
in
the
navigation
in
the
in
the
docs
site.
We
also
need
to
most
probably
especially
in
case
of
generator
in
case
of
parser.js,
we're
going
to
have
to
restructure
existing
markdown
files
into
smaller
markdown
files
and
add
the
front
matter.
A
So
that's
one
of
the
parts
where
we
will
also
need
help
like
not
much
about
writing
docs,
but
rather
restructuring
like
refactoring
of
the
of
the
documentation
like
splitting
it
into
smaller
pieces,
decide
which
one
is
for
what
parent
like
for
what
content
bucket?
Is
it
like
just
a
concept
like?
What's
the
parser
for,
or
maybe
it's
a
reference
documentation
like
api
documentation
for
the
library,
so
yeah?
That's
these
are
the
things
the
other
things
that
alejandra
referred
to
and
let
me
let
me
enable.
A
D
You
know
so
I
have
done
my
first
contribution
to
using
api.
I
have
fixed
the
code
that
contact
me
so
on
the
home
page
profile
and
yeah.
D
A
A
Sorry
come
again
like
could
you
like
like
like,
so
we
understand?
How
did
you
end
up
here
on
the
stream
like?
How
did
you
learn
about
the
stream?
How
did
you
learn
about
the
asking
api?
Can
you
share.
D
Yeah
so
currently
I'm
working
to
a
commerce
group
called
palabella,
and
then
there
we
use
a
lot
of
even
even
architecture.
You
know,
so
I
was
trying
to
to
to
get
a
tool
to
help
me
to
the
command
and
and
design
the
q
and
process
that
there
are
there
in
place.
D
You
know
so
I
came
across
the
sync
api
and-
and
it
was
like
I
thought
that
was
I
I
need
to
improve
my
my
gaming
communication
and
also
use
these
tools
to
to
make
the
info
clear
to
the
stakeholders.
You
know
so
it
is
quite
complicated
on
the
event
driven
architecture
to
document
to
to
to
have
some
kind
of
belief.
What's
the
know
what
gets
to
it
which
self
community
communicates
to
each
other,
you
know
so.
D
A
Okay,
awesome
welcome
again,
I'm
I'm
always
happy
when
somebody
just
comes
new
and
like
and
is
brave
enough
to
actually
join
the
stream.
So
it's
it's
awesome.
A
So
so
the
work
on
the
docs,
it's
still
like,
as
you
can,
as
you
can
see,
it's
still
like
in
pre-planning
the
idea,
like
the
issue
about
content,
buckets
it's
there
in
the
website,
so
it's
not
yet
kicked
off
there.
We
know
where
we
need
help,
but
also
there
is
not
sure
if
you're
familiar
with
oktoberfest
so
because
the
in
october
there's
always
oktoberfest.
A
We
also
have
some
some
issues
that,
like
not
all
of
these
issues
were
solved
during
the
because,
like
october
1st
ends
and
this
week
and
I'm
gonna
paste
the
link
to
the
excel
spreadsheet
again
excel.
A
Actually
it's
not
excel.
It's
google
spreadsheet
right
yeah,
I
mean,
but
it's
everything
with
those
cells,
it's
excellent
from
excel
anyway.
So
the
the
excel
sheet
it
it
links.
It
lists
all
the
issues
from
different
repos,
especially
provided
for
october
first,
to
make
them
as
easy
as
possible
for
anyone
to
start
contributing
and
feel
comfortable
with
the
project
and
one
the
the
ones.
That
might
be
super
interesting
for
you,
especially
if
you
want
to
start
with
dogs,
but
also
a
bit
of
code.
A
He
prepared
many
different
many
different,
not
actually
many
similar
issues
where,
where
he
wants
to
get
help
on
providing
more
examples
on
how
to
use
model
in
a
library
but
the
work,
it's
not
you
don't
have
to
learn
much
to
do
it.
So
the
task
is
marked
as
moderate,
but
it's
about
the
complexity,
not
difficulty.
So
it's
like
just
complex.
A
So
I
think
this
would
be
super
cool
for
you
to
contribute.
First
to
so
because
they
touch
docs,
so
current
doc
structure
that
in
one
of
our
tools,
but
it's
some
coding
like
you-
have
to
provide
some
tests,
but
all
is
well
documented
in
the
issues
and
jonas
is
always
there
helping
like
not
only
on
us.
D
Cheshire
I'll
take
a
look
at
that.
I
saw
this
file
previously,
but
I
didn't
find
anything
clearly
related
to
dogs.
I
saw
those
issues
also
I
featured
by
job
squared
by
go,
and
I
didn't
sound
something
simple
that
I
that
could
be
a
good
first
issue
for
me.
A
Think
that
jonas
scared
people
by
saying
that
it's
typescript
related
like,
but
it's
always
it
depends
on
the
on
the
on
the
on
the
person
that
creates
issues.
For
me,
it's
more
related
to
dogs
and
markdown,
because
I
think
you
create,
as
as
much
typescript
code
there
in
those
issues
as
as
the
markdown
content.
A
So
it's
a
mix,
but
it's
like
it's
really
just
most
of
most
of
it
copy
paste
where
you
just
learn.
Mainly
the
structure,
learn
the
project
and
what
is
it
about
what
it
gives
you?
So
that's
why?
I
think
it's
it's
easy.
Just
just
try
with
one.
It
seems
like
it's
complicated,
but
it
it
really
isn't
and
especially
that
some
of
these
were
already
solved
during
the
october
fest.
So
you
can
just
see
the
the
pull
requests
that
were
already
merged.
A
B
Thing
that
I
wanted
to
add
is
that
you
know
just
stay
tuned
and
keep
checking
up
the
posts
on
social
media
because
we'll
be
posting
when
we
finally
have
done
the
plan.
The
pre-planning
and
we
have
a
list
of
issues
for
the
docs
and
so
just
keep
an
eye
out.
And
when
you
see
us
announcing
hey,
we
finally
have
a
list.
Then
you
can,
you
know,
get
exhausted
with
me
as
much
as
you.
A
In
this
case,
it's
easy.
We
already
have
live
streams
where
we
explain
trades,
but
if
there's
some
concept
that
we
are
missing
documentation
for
it
needs
to
be
documented,
and
you
need
to
first
be
introduced
into
the
concept
we
will
for
sure
find
someone
in
the
community
that
can
make
an
online
session
with
you,
where
you
can
hit
this
person
with
lots
of
questions,
get
answers
and
and
produce
the
content.
A
So
that's
something
that
we
can
definitely
offer
as
well.
B
A
I
hope
he's
still
here
and
listening,
but
but
we
are
nice
to
jonas,
we
promoted
madalina,
so
he
should
be
happy.
A
So
it's
one
minute
to
seven
like
do
you
have
some
questions
because
we
can
make
it
a
bit
longer.
If
you
have
some
specific
question,
we
don't
have
to
finish
now.
A
A
So
I
definitely
have
to
use
this
opportunity
to
meet
with
my
friends,
I'm
not
sure
if
they're
watching
this
stream,
because
I
told
them
that
I
have
to
finish
the
stream
first,
so
hello
to
my
friends
from
poland,
so
yeah
thanks
a
lot
alejandra
for
for
joining
and
having
this
very
cool
discussion
about
the
the
docs
and
lutima
the
team.
Do
I
pronounce
it
correctly.
A
Yeah,
okay,
so
thanks
a
lot
for
joining
it
was.
It
was
a
pleasure
to
have
you
here.
So
thanks
a
lot.
Thank
you!
So
much
and.
D
A
To
all
the
people
in
the
in
the
chat,
the
streaming
will
be
automatically
available
on
twitch,
twitter,
linkedin
and
youtube
and
hear
you
next
wednesday.
8
am
utc
and
4
pm
utc
bye.