►
Description
Learn how to contribute to AsyncAPI Initiative with our contributor guide https://github.com/orgs/asyncapi/discussions/487
A
A
Hello
hi
welcome
to
the
async
API
October
face
live
stream.
This
is
our
second
live
stream
and
I'm
I'm
your
host
for
today,
I'm
Haze
and
yeah
you'll,
be
saying
this
face
a
lot
and
yeah.
So
in
today's
into
this,
live
stream.
A
We'll
be
talking
about
how
to
start
contributing
to
with
the
leader
as
the
first
time
contributor
and
how
to
become
a
champion
for
modelina
and
yeah
I'm,
pretty
sure
you
guys
are
going
to
enjoy
this
live
stream
because
I
have
with
me,
I
have
with
me
in
a
guest
called
somebody.
A
I'm
gonna
call
her
Sam
for
short,
so
she
she's
she's
a
modeling
a
champion
and
she
started
contributing
to
modeling
as
a
first
time
contributor,
so
I
I
can
see
like
who
else
can
I
invite,
if
not
how
right
so
I'm
gonna
bring
out
hope
to
the
stage
and
yeah.
So.
A
A
I'm
sorry
give
me
a
few
seconds:
I
have
a
power.
B
B
A
B
Yeah,
okay,
so
hi
everyone
I'm
somebody
I'm,
currently
working
in
thoughtworks,
India
and
I
started
contributing
in
async
Asia
from
last
last
year,
December
from
December
and
yeah
and
people
I'm
modeling
a
champion
like
for
a
typescript
and
JavaScript.
A
Okay,
so
how
do
you
do
start
like
what
type
do
you
mind,
sharing
the
open
source
Journey
with
me.
B
Yeah
definitely
so
I
started
my
open
source
Journey
from
the
hack
to
office
19
itself,
so
that
time,
the
first
time
I
started
contributing
in
open
source
and
get
to
know
about
projects.
What
kind
of
so
and
after
contributing
in
hacktoberfest,
then
I
just
keep
exploring
other
projects.
B
So
it
just
fascinated
me
to
explore
more
new
projects,
something
which
interests
me
since
I
have
majorly
worked
in
JavaScript
so
far,
so
I
keep
on
looking
for
the
that
kind
of
project
on
the
githubs
and
then
in
the
last
year,
in
December,
I
just
came
to
know
about
async
API
through
g-soc,
when
I
was
looking
for
contributing
in
gsog,
then
I
came
to
know
about
that.
B
Ac
gave
us
so
I
just
land
up
here
and
luckily
I
got
a
good
first
issue
to
work
on
and
I'm
really
thankful
to
Lucas,
who
really
helped
me
to
get
and
just
get
better
understanding
of
the
code
base
in
the
setup
process
also
and
yeah.
So
that's
how
I
just
came
to
async
API
through
open
source.
A
A
Say:
hey
I'm,
giving
a
shout
out
to
he's
always
been
a
good
boy
shout
out
to
you
Lucas
thanks
for
onboarding,
some.
B
It's
it's
really
amazing.
It's
really
like
I,
really
I
would
like
to
thank
everybody
in
the
async
API
every
TSC
members.
Everybody
is
very
well
welcoming
here,
like
and
always
very
responsive
on
the
channel.
B
Also,
if,
whenever
you
face
anything
or
any
doubt
say
everybody
helps
in
like
that
is
a
very
good
teamwork
or
you
can
say
that
I
really
like
about
the
async
API,
because
as
a
as
a
first
timer,
it's
very
important
because
you
face
some
issue
and
if
you
write
down
your
doubts
and
it
it's
not
get
as
addressable
in
their
channel,
so
it's
kind
of
very
disappointing.
So
that
is
the
very
good
thing
about
the
easing
API.
B
Here
we
get
a
very
quick
responses
and
they
really
welcome
you
and
if
they
even
help
you
to
find
the
like,
follow
the
right
path,
so
yeah,
the
first
time,
I
started
contributing
with
the
note
template
at
that
time.
Lucas
help
me
a
lot
with
the
set
of
things
and
he
also
asked
asking
about
the
feedback
if
I
have
any.
B
So
this
is
a
very
good
thing
and
after
that,
I
keep
exploring
a
different
repositories
which
on
which
we
can
again
work
so
sometimes
I
have
like
I'd,
initially
I
wasn't
able
to
find
the
right
ones
on
which
I
can
work
on
so
I
asked
for
the
help
from
Lucas.
B
So
he
really
helped
me
by
suggesting
me
some
good
first
issues
in
the
repositories
based
on
my
interest
and
then
I
keep
working
on
that
and
then
I
worked
on
website
and
the
one
of
the
a
nice
thing
I
really
liked
about
it.
That
is
like
they
appreciate
you
like.
If
you
work
on
something
they
appreciate
you
by
providing
you
as
a
contributor
member
like
adding
you
as
a
in
the
readme
and
giving
you
work
on
that,
like
they
have
different
emoji
G's
for
each
type
of
contribution.
B
B
Just
then
I
just
keep
exploring
and
finding
issues
to
work
upon,
get
understanding
on
the
code
base
which
I
can
work
on
more
frequently,
and
so
that
then
I
I
want
to
look
into
the
some
back-end
code,
which
interests
me
more
so
based
upon
that
I
come
to
know
about
the
modeling,
so
I
just
keep
exploding
for
the
good
first
issues,
which
foreign.
B
Because
it's
not
possible
to
understand
the
whole
code
base
at
a
first
glance,
so
by
picking
the
small
issues,
we
can
pick
up
a
small
piece
of
code
and
we
can
read
it
again
and
again
review
it
and
then
started
understanding
the
code
base
like
if
we
keep
contributing,
then
we
keep
understanding
the
code
more
and
more
so
yeah.
It
was
really
really
helpful
me
to
learn
how
to
read
code
because
writing
a
code
from
a
scrap
scratch.
B
A
That
was
that
was
that
was
an
amazing
breakdown.
Some,
like
you,
you
literally
work
from
zero
to
100.
That's
us
that
was
awesome.
So
thanks
so
much
now
you
can
see
how
Sam
got
into
open
source
and
how
she
got
to
find
out
about
async
API
and
how
she
became
addicted.
Should
I
should
I
use
the
word
addicted
or
fell.
You
fell
in
love
with
you
think
API
right
just
because
of
the
community,
and
this
is
this-
is
just
it
right.
A
It's
a
kpi
is
one
of
many
of
one
of
few
communities
out
there
that
treat
their
community
members
as
part
of
the
team
right.
So
we
are
a
community
first.
So
before
anything,
we
we
we
take
Community
First
right,
so
I
would
say
we
are
a
community
fresh
project,
so
the
community
comes
before
the
project
right,
and
that
is
one
thing
we've
always
you
know,
keep
at
the
at
the
front
of
our
heart
is
just
to
keep
the
community
work
with
very
welcome
community
and
do
everything
we
can
for
the
community.
A
We
also
give
back
to
the
community
right.
Give
back
to
the
community
based
on
an
example.
Is
is
doing
the
the
Escape
mentorship
program
right,
so
many
folks
from
the
I
think
API
mentorship
program
are
actually
contributors
are
regular
contributors
right,
but
we
want
to
give
back
to
the
community.
So
we
started
we,
we
we
thought
of
doing
the
thinking
mentorship
program,
which
it
is
a
way
for
us
to
give
back
to
the
community,
and
it
isn't
just
that
right.
A
We
also
have
upcoming
programs
that
we
are
looking
for
a
way
to
give
back
to
the
community
and
an
example
of
that
is
the
ambassador
program.
So
the
ambassador
program
is
also
a
way
to
give
back
to
the
community.
And
yes,
of
course,
we
are
always
exploring
ways
to
to
give
back
to
the
community
and
yeah
I'm,
pretty
sure
Sam
you,
you
would
be
really
interested
right.
We
have
to
give
back
to
you
and
that
that
is
what
we
are
going
to
do,
yeah
so
Sam.
Would
you
like
to
share?
B
I
started
with
some
good
first
issues
and
just
understanding
the
code
base,
little
like
by
each
by
that
images,
to
make
PRS
very
frequently,
like
I,
started
with
some
documentation,
adding
examples,
initially
understanding
what
exactly
how
things
are
going
and
the
other
few
things
I
really
learned
about
here.
The
coding
thing,
like
writing
a
code.
Anybody
can
do
that
anybody
can
write
a
code,
but
writing
a
quality
code
is
very
important
as
a
developer.
B
So
that
is
a
very
key
learning
and
the
part
from
that
when
I
started
contributing
I
also
learned
so
many
new
things
like
a
code
smell
and
how
how
to
write
test
cases
so
follow
tdd,
which
is
a
very
important
thing
like
a
testament
development.
If
anybody
don't
know
like
what
tdd
is
so
like
is
very
important,
so
in
very
initially
I'll
open
the
pr.
So
every
time
ask
me
you
miss
the
test
you
miss
the
test.
I
was
like.
Why
like?
What
is
the
point
of
adding
test,
then,
when
I?
B
Just
then
I
understand
why,
after
sometimes
okay,
this
is
important
of
test.
When
you
write
a
code
to
to
write
a
unit
test
to
check
the
functionality
and.
B
So
this
is
a
very
good
thing
like
you
keep
it
just
it
keeps
growing
you
with
the
time
with
the
each
contribution.
You
learn
a
new
thing
like
every
time
when
you
make
a
PR.
It's
just
a
encourages
you
to
okay,
let's
work
on
another
issue,
because
every
time
we
got
something
new,
we
learn
something
new
like
so
that
is
also
very
important.
So
I
just
frequently
keep
working
on
the
model.
You
know
understanding
the
code
base
and
making
it
easy.
B
No
I
like
finding
less
Improvement
in
my
codes,
foreign.
B
A
Definitely
some
so
I'm
an
example.
I
I
would
say
is
right.
I'm
gonna
live
an
example
of
what
you're
saying
right
about
giving
back
to
his
community.
I
was
also
I
was
once
a
contributor
right.
I
was
a
contributor
assistant
kpi,
you
know,
I
I
did
a
lot
of
things
and
yeah.
By
giving
back
to
me,
I
I
I
found
my
play.
I
found
myself
in
a
place
of
joining
the
Singapore
Court
team,
and
that
is
that
was
a
very,
very
good
news
for
me.
A
Right
yeah,
how
did
I
start
I
started
by
contributing
as
a
regular
contributor,
then
I
went
in
via
Google
summer
of
code.
I
I
did
the
first
decision,
which
I
was
a
runner
up
and
yeah
I,
just
kept
contributing
and
yeah,
even
even
beside
the
fact
that
I
joined
the
secret
prayer
courting
I.
Think
I
was
already
given
back
to
me.
You
know,
based
on
the
years
of
experience
and,
and
so
many
things
I
get
to
learn
so
much
yeah.
Also
Alexander
is
also
the
test
case
right.
A
A
These
are
experiences
where
you
know
people,
people
always
quote
it
and
say:
oh
in
order
to
get
this
experience,
you
have
to
work,
you
have
to
get
a
job
at
a
startup
or
at
a
big
company
to
get
this
experience
from
the
senior
Engineers
right,
but
here
at
City
kpi
you
get
everything
like
for
free,
like
isn't
that
amazing
and
the
the
maintainers
the
contributors
are
like
I
like
one:
they
don't
no
discrimination,
nothing
of
course,
because
I've
contributed
to
a
lot
of
Open
Source
projects
before
I
I
joined
a
ckpi
yeah
I've
seen
you
know
my
my
pull
request
pending
like
forever
right,
I,
don't
get
attention,
I,
don't
get
anything
yeah,
so
I'm,
pretty
sure
you
can
relate
right
and
now
those
are
one
of
the
things.
A
Definitely
why
it's
it's
a
kpi
is
different
right
and
yeah.
So
we
have
said
seems
like
we
have
another
awesome
idea.
So
we
share
the
link
in
the
in
the
in
the
charts
in
place
where
we
list
all
contributors.
We
have
a
set
of
badges
that
we
assigned
to
them,
so
contributors
are
gonna,
start
having
badges,
which
is
which
is
awesome
and
yeah.
You
say
we
we
are
not
stopping
like
we
just.
A
We
just
have
to
keep
appreciating
every
single
contributor
in
the
community
because
it
takes
a
lot
to
to
contribute
to
open
source,
and
we
appreciate
that
we
don't
take
that
for
granted,
yeah
so
Sam.
Would
you
like
to
tell
us
what
it
means
to
be
a
champion?
What
is
a
champion?
You
know:
I
I,
I
love
the
term
that
you
guys
say
champion
and
I
want
to
become
one
right,
but
in
order
to
become
a
champion,
I
first
have
to
know
what
is
a
champion.
What
do
you
mean
by
UA
champion.
B
Okay,
so
yeah,
basically
a
champion
being
a
champion,
so
means
that
you
have
a
few
responsibilities
like
let's
say
in
order,
we
have
divided.
We
have
divided
it
with
a
different
zones
like
we
have
different
sections.
We
have
different
languages,
which
is
there
like
typescript
JavaScript,
Java,
C
sharp.
So
we
divided
it
in
a
different
section
than
people
with
a
particular
Tech
interest
area
of
which
they
want
to
work
on.
So.
B
As
a
champion,
you
need
to
like,
for
that
particular
language.
Let's
say
I'm
a
champion
for
a
typescript
in
JavaScript,
so
if
there
will
be
any
equal
request
related
to
typescript
in
JavaScript
code,
I
will
because
I
will
be
responsible
for
the
code
review
any
Improvement
in
that
and
if
there
is
need
to
make
any
changes
in
that
particular
that
I
skipped
in
JavaScript,
so
I
would
be
responsible
for
everything
related
to
that
particular
piece
of
code.
So
that's
the
response,
possibilities
and
the
role
of
it.
B
We
have
to
look
after
that
the
particular
sections
for
which
they
are
assigned
form.
You
can
be
Champion
for
multiple
sections,
like
you
can
model,
you
know
like
I,
am
sampling
for
the
JavaScript
and
typescript.
Likewise,
it
can
be
a
champion
for
a
Java
and
multiple
other
sections
like
Json
format,
and
they
are
different
sections
on
which
can
do
that.
So
it's
like,
but
yeah,
it's
not
like
just
you
get
the
thing
like,
but
you
have
to
be
there.
B
Then
you
have
to
do
that
also,
so
it's
like,
if
you
take
the
responsibility,
so
you
you
should
do
that
justification
with
that,
like
you
need
to
be
do
it
by
like
you
need
to
follow
those
things
like
you,
you
are
just
become
a
maintainer
of
that
particular
Tech
stack.
You
need
to
look
after
it
every
like
everything.
Is
there,
like
from
infra
to
code,
review,
testing,
documentation,
everything?
It's
your
responsibility
now
like
it's.
What.
B
Is
there
not
a
single
person?
I
can
say
everybody
would
be
there
like.
It
doesn't
matter
who
you
can
even
like
you
need
to
Ping
anybody.
It's
not
like.
You
need
to
Ping
it
on
the
group.
You
can
personally
pick
anybody.
Everybody
is
so
much
welcoming
here
they
will
respond.
You
help
you
out
with
any
of
your
doubt
anytime.
They
can
just
you
need
two
things.
It's
not
like.
You
have
to
do
anything
alone.
B
B
To
check
if
it
is
functionality
is
right
or
wrong,
so
he
statistic
means
not
a
big
deal
because
we
all
are
alone.
So
it's
not
a
problem.
Sometimes
we
also
make
mistake.
So
sometimes
it's
totally
fine
making
mistakes,
it's
just
like
keep
learning.
So
that
is
more
important.
So,
oh,
it's
fine
that
if
you're
not
able
to
get
it,
you
can
ask
what
other
thing
is
happening
or
if
any
particular
thing
we
will
help
you
or
if
it's
God,
that
is
not
the
case.
B
Whatever
the
problem
you
are
facing,
you
can
ask
any
time:
it's
not
a
big
deal.
If
you
have
any
suggestion,
you
can
give
it
or
if
you
have
any
doubt
you
can
ask
it.
So
it's
like
that
that,
like
it's
not
like,
you
have
to
do
everything
alone.
Well,
if
you
become
a
champion,
it's
not
like
it
feels
like
a
burden.
B
It's
like
a
very
responsibility,
because
so
many
learning
things
so
many
like
you
just
got
to
learn
about
technical,
you,
it's
not
like
growing
technically,
but
also
with
them,
like
with
everyone
like
a
community.
It's
going
along
with
the
community.
A
Awesome
that
was
that
was
like
that
was
amazing.
That
was,
that
was
what
I
was
open
to
yeah,
because
when
I
said,
when
I
had
you
say
a
champion,
I
was
thinking,
Champion
seems
catchy
right
being
a
champion
and
I
was
like.
There
has
to
be
something
behind
me
in
Champion
right,
so
I
was
thinking,
it's
it.
I
I
feel
which
is,
as
you
put.
A
It
is
also
a
role
as
a
maintainer,
but
in
this
time
you're
not
alone
right,
yeah,
wait
or
or
all
the
people
participating
in
the
projects
right
you
you
you're
able
to
like.
If
you
get
stuck,
you
can
reach
out
to
other
Champions
or
other
maintainers
to
get
help,
which
is
which
is
really
really
awesome,
and
you
you
keep
saying
you
keep
mentioning
Jonas
and
yeah
he's
a
cool
guy
and
I
hope.
I
will
be
able
to
bring
him
in
one
of
these
live
streams.
A
These
days
to
to
you
know,
give
give
us
more
information
about
modelina
and
what
modeling
and
is
and
and
all
interesting
stuff
about,
modeling
and
yeah,
so
I'm
looking
forward
to
that
day,
I
can't
wait
to
bring
and
yeah
so
I
think.
My
next
question,
for
you
is
actually
pretty
straightforward
right.
So
as
an
October
fresh
participant
right,
how
do
you
think
I
can?
Is
there
a
chance
for
me
to
become
a
champion
from
udalina
really.
B
Welcome
everybody,
it's
a
different.
We
have
a
different
kind
of
gesture
to
appreciate
everyone
like
initially,
if
you
do
a
contribution,
so
we
add
you
either
in
the
firing
to
just
appreciate
your
efforts
and
whatever
you
put
till
in
our
project
or
or
else
like,
if
you
stay
for
a
long
or
you
just
keep
contributing
there
and
you
just
get
a
better
understanding.
Maybe
the
code
base,
maybe
like
like
we
feel
like
like
a
the
team
members,
feel
the
person
has
a
good
quality
of
knowledge
with
a
code
base,
better
understanding.
B
A
B
Yeah
definitely
technically,
like
the
good
part,
is
sick.
Here,
it's
not
like
a
it's
for
just
a
quarter
because
it's
like,
if
you're,
not
good,
they
cannot
put
the
coding
anything,
but
still
you
have
a
good
good
proficient
with
the
English
and
the
good
documentation
skills
you
can
all
contribute
put
it
there,
even
and
now
in
the
foreign.
A
A
B
A
Yeah
definitely
folks,
if
you're
interested
in
in
becoming
a
champion
I
feel
now
is
your
chance.
You
know
you
could
and
we
we
have
some
as
part
of
of
the
champion
and
you
can
easily
reach
out
to
her
on
on
on
on
GitHub.
Do
you
mind
sharing
your
GitHub
handle
some.
B
A
You
do
you,
can
you
share
your
Twitter
undo
just
for
folks,
you
know
watching
these
stream
later
for
October
1st,
and
they
are
willing
to
reach
out
to
you
for
to
talk
more
about
modeling
on
how
to
get
started.
You
mentioned
your
Twitter
undo
and
also
I'm
gonna
I'm
gonna
share
a
little
link
to
the
community
slack
Channel,
just
for.
A
Yeah,
so
you
can
join
the
it's
okay,
slack
Channel
and
feel
free
to
drop
a
message
for
Sam
on
slack
and
also,
if
you're,
not
on
slack
she's
gonna
share
Twitter
undo.
So
you
can
also
reach
out
to
our
via
Twitter,
if
you're
interested
in
discussing
open
source
as
a
whole
or
talking
about
how
to
get
started
as
a
model
in
a
champion
or
as
a
regular
contributor
for
modelina
foreign.
A
Okay,
so
what
what
was
you
know?
You've
you've
been
a
champion
for
modeling
you've
started
contributing
you,
you
have
so
so
so
much
experience
and
participating
in
October
1st
right.
So
if,
if
you'll
be
giving
a
first-time
contributors
or
people
that
are
just
starting
like
they
just
started
contributing
to
October
1st
should
I
say
an
advice
or
something.
What
would
it
be.
B
For
a
person,
contributors
I
would
like
see
that
I
would
just
suggest
them
to
look
for
easy,
like
some
good
first
issues,
because
at
first,
if
you
go
to
any
repositories,
it
will
look
overwhelming
and
it
might
just
dishearten.
You
also
like
it
makes
you
like:
okay
I'm,
not
able
to
do
it,
it's
very
hard
to
read
the
code,
but
soon
so
just
don't
think
about
anything.
Just
pick
the
right
one
in
the
GitHub
we
get
very
different
options.
B
To
look
for
the
language
is
specific
and
anything
so
you
can
just
who,
if
you
are
not
still
not
able
to
find
the
good
first
issues.
Maybe
you
can
reach
out
the
right
person
from
the
organization.
Okay,
I
am
not
able
to
figure
it
out.
They'll
definitely
help
you
and
you
can
simply.
Then
you
can
just
look
for
the
good
first
issues
and
read
it
like.
B
Maybe
like
I
started
it
with
the
like
updating
the
documentation,
because
I
find
it
easy
too,
because
in
the
documentation,
I
think
when
we
just
make
changes
in
the
documentation,
we
read
the
documentation
and
get
the
understanding
of
the
code,
also
because
documentation
is
very
important
part
of
any
repository,
because
from
there
we
get
how
to
set
up
the
that
particular
project.
That
is
also
very
important
like
right
way
to
set
up
a
project,
run
it
with
a
successful
like
getting
what
actually
the
it
is
so
yeah
like
reading
a
documentation.
B
Maybe
you
can
pick
up
the
documentation,
start
working
on
the
readme
files
or
any
other
document
file,
if
you
think
so,
if
not
on
the
documentation,
actually
only
work
on
the
code
part.
So
maybe
in
that
case
people
can
pick
up
the
issues
with
the
small
changes
where
they
can
pick
the
small
article
feature
they
can
work
upon
and
they
can
get
a
better
Clarity
how
the
flow
goes
on.
What
are
the
things
like,
whether
the
code
followed
or
not?
What
are
the
key
encoding
practices?
B
They
follow
it
there
and
how
to
open
a
pull
request
and
how
to
like,
like
follow
the
certain
guidelines
like
if
it
is
the
codes
in
the
JavaScript.
So
what
are
the
ways
to
write
the
code
in
a
JavaScript?
What
are
the
syntax
and
syntaxely
needs
to
use
it
in
the
code?
So
these
are
the
small
things
like
it
seems
small,
but
these
are
the
basic
things
that
makes
you
a
good
developer
or
that
helps
you
to
write
a
quality
code,
so
that
is
very
important
that
we
neglected
in
the
contributing.
B
We
just
look
for
the
issues
like
putting
in
DSA
problems,
so
it
won't
help
in
the
long
term
basis.
So
rather
it
would
be
like
going
for
a
easy
issues.
They
go
for
something
that
will
help
you
to
establish
a
good
basic
concepts
also,
because
that
that
will
help
gives
a
long-term
benefit
in
writing
a
quality
code
following
the
good
practices
that
we
should
follow
while
learning.
So
these
are
the
few
things
I
would
like
to
suggest.
B
The
new
contributors
like
don't
go
for
the
easy
one
just
to
get
the
this
is
together.
Please,
and
do
the
four
people
request
if
you
really
want
to
and.
B
Keep
this
thing
with
you
so
just
start
looking
for
good
issues,
good
repositories,
which
you
can
as
per
your
interests
and
find
the
issues
where
I
feel
difficulty
go
to
the
that
Repository
owner
and
ask
for
the
help.
Read
the
documentation
set
up
the
project,
focus
it
properly,
set
up
to
and
set
up
a
project
and
just
go
through
the
code
like
how
it
is
happening
like
if
it's
a
look
at
the
website
or
thing
like
how
it
is
like
looking
what
the
UI
is.
B
It
is
negative,
finally,
sometimes
like
initially
I
remember
when
I
started,
contributing
I
look
for
the
documentation
in
the
website
versions,
because
at
that
time
I
was
doing
web
development
so
that
that
person
needs
me
more
so
I
look
for
the
U.S
stuffs
like
bought
the
Improvement
I
can
make
for
suggestions
and
like
if
you
think
this
is
going
wrong.
You
can
also
open
an
issue,
it's
sort
of
for
raising
a
PR.
Only
you
can.
B
B
I'll
find
an
issue
you
can
raise
a
like,
you
can
open
an
issue
and
if
you
think
you
can
fix
it,
that's
a
very
great
thing
you
can
like
simply
write
down
like
you
can
note
down.
The
like.
Even
writing.
Issue
is
like
it's
a
very
important
so
that
any
other
person
can
understand
it
so
write
it
like.
If
the
repository
has
a
template,
it's
a
like
a
very
good.
B
If
not,
then
you
can
follow
the
few
things
like
and
add
the
owner,
or
maybe
search
on
the
Google
somewhere
like
how
to
write
an
issue
in
a
proper
way
like
so
that
other
person
can
also
reproduce
it
and
see
the
what
is
the
difference
between
the
actual
and
the
expected
behavior,
and
if
you
think
you
can
like
work
on
it,
and
you
can
fix
that
issue.
You
can
also
write
it.
B
There
like
yeah
I,
can
fix
it
so
that
I
can
work
on
it
and
then
you
can
go
ahead
and
raise
your
VR,
so
that
is
also
a
one-way.
You
can
start
it
or
like
directly,
if
you're
not
able
to
find
a
good
first
issue.
Maybe
you
can
look
for
the
issue
and
then
we'll
open
an
issue
and
work
on
it,
so
it's
like
either
way
you
can
just
start
it
with
that.
A
That
was
that
was
amazing,
Sam
and
yeah.
I.
Think
you
you
actually
let
me
just
say:
I
actually
asked
you:
okay,
Sam
go
just
a
little
bit,
but
I
love
the
fact
that
you
went
so
deep
to
actually
make
the
explanation
as
easy
as
possible.
You
like
explain
to
me
like
I'm
five,
which
was,
which
is
very,
very
awesome,
Sam
thanks.
B
For
me,
it
was
really
really
helped
me
a
lot
in
growing
because
before
that,
I
have
contributed
in
so
many
open
source
projects,
but
after
after
like
when
I
started
contributing
it
here.
So
I
really
like.
It
really
helped
me
to
build
my
basics,
like
really
because
I
actually
learned
about
the
TVD
I
learned
about
the
how
to
write
a
quality
career.
Because
let
me
write
a
code
then,
when
we
raise
the
pr
here,
we
have
different
negative
actions
or
flow
setups
here.
B
Just
May
that,
like
put
just
Gibson,
come
to
you,
though,
your
code
is
not
good,
just
keep
working
on
it
more
so
that
is
like.
It
really
helped
me
to
establish
my
Basics
and
like
also
like
containers
they
they
also
just
keep
look
into
that
thing
also
like,
if
anything.
B
Very
nicely
one
more
thing
that
I
like
about
the
ECT
which
I
I
noticed
here
like
they,
they
use
emojis,
which
is
very
nice
just
to
Express
gratitude
towards
the
other
person.
So
that
is
like
a
very
good
thing
like
yeah,
so
they
are
like.
This
is
how
it
really
helped
me
here:
I
I
can
actually
see
the
growth
from
from
zero
to
something
like
I'm
still
learning
here,
because
getting
a
new
thing
and
getting
different
things
every
time
when
I
contribute
I
just
got
okay,
this.
B
This
is
how
we
can
we
have
to
do
like
even
for
writing
the
documentation.
There
is
a
way
for
writing
like,
even
if
you
have
to
work
on
a
design,
then
you
need
to
follow
this.
This
thing
they
currently
followers.
B
And
then
design
it
and
then
get
it
approval
yeah.
This
is
fine,
then
start
working
on
it.
So
there
is
a
way
to
do
certain
things.
So
as
I
like
as
a
fresher,
you
don't
know
because
you
don't
have
experience
but
like
here
it
just
like
when
you
keeps
working
on
and
just
the
only
thing
is
that
the
consistency,
if
you
be
consistent
here
in
the
easy
character,
you
will
really
learn
the
Lord.
If
you
think
you
can
take
it
in
a
month
or
in
a
week,
it's
not
possible.
B
If
you
be
consistent,
keep
with
them.
If
you
just
stay
with
the
community,
then
definitely
you
will
learn
and
they
did
really
appreciate
your
contributors
members
in
a
different
way
and
every
time
they
work
upon
just
expanding
their
community
and
always
cherish
your
idea.
If
you
have
any
idea,
they
will
welcome
it.
If
you
have
any
feedback
suggestion,
just
can
give
it
on
the
slack
in
this
Channel
anywhere
and
everybody
is
so
like
welcome
your
feedback
and
you.
B
So
that
is
a
very
a
good
thing
and
a
very
positive
thing
about
the
community
and
I
think
that
is
the
major
thing
that
holds
the
new
joiners
and
everybody
to
stay
with
the
community.
A
Okay,
thanks
so
much
some
that
was,
that
was
really
impressive.
Yeah,
as
you
can
see
you
shouldn't,
have
it.
You
shouldn't
have
a
second
doubt.
You
know
joining
the
second
pack
community
as
a
contributor
or
you
can
even
become
a
maintainer.
You
know
it's
very,
very
easy
and
his
phone.
You
have
tons
of
people
that
are
really
really
ready
to
help
you
in
whole
aspects
of
contribution
right
it
could.
You
can
be
a
designer
and,
and
I
can
remember,
I
I,
we
have
a
contributor
called
me
called
Maya.
A
She
is
a
designer
and
she
joined
a
Singapore
to
build
a
skill
and
she
was
saying
she
she
she
doesn't
know
how
she
don't
know
how
to
she
doesn't.
Even
she
wasn't
even
familiar
with
GitHub
right,
she's,
a
designer
and
now,
with
the
help
of
wukash,
she
actually
submit
a
Facebook
request,
which
is
amazing,
a
designer
for
Christ's
sake,
yeah.
She
she
has
no
idea
how
GitHub
work
few
weeks
back,
but
now
she
opened
the
first
few
requests
and
she's
been
doing
amazing,
stuff
and
yeah.
A
That's
that's
why
you
can
say
is:
doesn't
just
welcome
coders,
like
people
that
write
code
right
if
a
designer,
a
technical
writer,
a
developer,
all
kind
of
fields,
you
can
contribute
to
a
Sync
API,
and
we
have
amazing
folks
that
are
always
on
standby
to
to
help
you
get
started
right
and
that's
why
I'm
giving
this
better
shout
out
to
my
co-host,
which
is
wukash,
the
guy
is
amazing,
right,
he's
I'm,
pretty
sure.
That's
why
he's
growing
old
so
fast,
because
he's
always
doing
a
business
tough
with
the
community.
So
that's,
that's!
A
That's
all
the
questions
I
have
for
you.
Some
I
really
appreciate
you
honoring.
This
call
and
I'm
actually
looking
forward
to
to
putting
you
on
more
calls
in
the
future
and
yeah.
That's
that's!
That's!
That's
all
my
questions
for
you
and
if
you
would
love
to
have
anything,
what
would
you
like
to
add.
B
A
Yeah,
so
we
we
so
before
we
round
up
before
we
round
up
I'm
kind
of
actually,
you
know
we
are
having
this
conference,
which
is
November
3rd
to
November
5th.
So
it's
gonna
be
an
amazing
conference
So
for
anybody
watching
this
live
stream.
Please
you
should
create
a
day
on
your
calendar
for
this
conference
right
and
also
Sam
I'm.
Looking
forward
to
seeing
you
at
the
conference,
you
know
we
have
amazing.
B
A
On
the
on
the
speaker,
lineups,
we
have
amazing
topics
right,
so
it's
gonna
be
so
much
fun.
You
know,
I
can't
wait
for
the
for
the
event
to
start
so
yeah
me
too
yeah,
so
so,
just
for
anybody
watching
your
chocolate
later
or
even
this
call,
you
should
look
for.
We
are
looking
forward
to
meeting
you
at
the
event
and
I'm
pretty
sure
it's
going
to
be
fun,
so
that
will
be
everything
from
my
end.
A
Sam
thanks
for
joining
this
call,
I'm
open
to
seeing
you
in
more
calls
and
looking
forward
to
more
contributions
from
you
and
also
yeah.
You
should
be
looking
forward
to
seeing
another
champion,
so
thanks
so
much
for
joining
this
call
catch
you
later,
Sam,
bye.