►
From YouTube: Let's talk about contributing - Documentation
Description
A
Yeah
so
hi
everyone,
I'm,
Hayes
and
I
in
today's
I
thought,
if
you
have
seen
I've
had
a
couple
of
let's
talk
about
contributing,
live
stream
and
if
you
haven't,
you
know
this
is
your
first
time
I
would
recommend
you
also
like
check
out
our
previous
live
streams
about
you
know
contributing
to
racing
API,
and
you
know
you
know
we
try
to
like
make
these
discussions
as
diverse
as
possible,
right
from
engineering
to
designs
to
dogs
right
and
in
today's
stream.
Right
I
have
with
me.
A
You
know
a
lot
of
amazing
folks
and
I'm
pretty
sure.
You're
gonna
enjoy
today's
trade,
because
I
think
I've
got
some
jokes
right.
I,
just
pretty
laugh
so
today,
with
me,
I
have
some
amazing
folks
and
from
the
community
actually,
and
these
folks
are
actually
pretty
interested.
You
know.
I've,
actually,
you
know,
did
some
collaboration
with
some
of
them
and
also
it's
my
first
time.
A
You
can
do
some
some
of
them
also,
so
they
are
actually
the
current
double
season
of
dogs,
participants,
artists
and
kpi,
and
so
in
today's
stream
we
are
going
to
be
talking
about
how
to
contribute
to
Executive
recommendations.
So
we'll
talk
about
yeah,
open
source
journey,
I
decided
contributing
to
open
source
how
they
ended
up.
You
know,
choosing
their
singapi
and
yeah
we're
gonna
learn
so
much
about
you
know
documentations
in
general.
A
You
know
from
with
you
know,
people
with
different
perspective
right,
so
we
have
like
four
guests
today,
I
think
four
yeah.
So
we
have
like
four
guests
today
without
no
further
Ado.
We
have
to
get
right
into
it,
so
I'm
gonna
bring
them
up
yeah.
Why
am
I
doing
nervous
right?
Why
should
the
host
be
nervous?
Isn't
that
weird
yeah
really
weird
so
bringing
you
guys
up.
A
A
A
B
B
A
D
Yeah
sure
hi
everybody,
my
name
is
Nelson
Michael
I'm
from
Nigeria
I'm,
a
developer
Advocates
thank
God,
that's
true!
Yeah
yeah,
so
I
I
stay
contributing
to
open
source
sometime
last
year
and
then
I
got
the
opportunity
to
intern
for
Google
system
updogs.
So
that's
what
I'm
on
right
now
and
it's
been
an
exciting
Journey.
So
far,.
E
E
Yeah
sure
hi
everyone
nice
to
meet
you
all.
First
of
all,
I'm
super
excited
to
be
here.
My
name
is
pratik:
I
live
in
Mumbai
India
I
am
a
student
developer
currently
studying
in
India
Maharashtra
and
I've
been
working
on
the
generator
to
documentation
for
the
past
six
months
or
during
the
Google
season
of
docs
documentation,
program
and
yeah.
I'm
really
glad
to
be
here.
A
Same,
we
are
also
all
glad
to
have
you
here
today:
Patrick,
it's
an
honor
so
for
some
reason,
I
think
Thule
is
having
internet
issues
so
we're
gonna
have
to
kick
off.
You
know
without
her,
so
once
she
comes,
we
can
invite
her
back
to
the
party
okay
yeah.
So,
as
you
all
know,
I'm
amazed
I
think
I
have
a
title
but
I
love
to
go.
Call
myself.
A
You
know
the
preacher
at
Jason
kbi,
so
I
love
to
preach
the
gospel
I,
love
to
know,
I'm,
a
big
fan
of
inventive
and
architecturals
and
I.
Think
API
is
where
my
heart
is
so
I.
Try
to
like
Show
event,
apis
and
effect
API
off
to
people's
throats.
So
don't
have
a
choice
you
just
have
to
like
do
it.
You
have
to
know
it.
So
that's
that's!
Basically
what
I
do
I'm
a
preach:
artistic
API
and
I'm?
A
F
F
Okay,
I
I'm,
not
a
boss,
boss,
don't
sound
like
me!
First
of
all
so
I'm,
truly
a
technical
writer.
What
else?
Let
me
think:
okay,
I'm,
truly
I'm,
a
technical
writer
data
scientist
I
am
based
in
Cape
Town
yeah,
that's
it
for
those
who
don't
know
me
I'm
sure
somewhere.
Somehow,
if
you're
watching
the
I
think
API
conference,
you
might
know
this
face
so.
A
A
C
D
A
Yeah,
so
thanks
for
the
introduction.
Actually
so,
as
I
was
saying
before
I'm
Ace,
oh
God
I
introduce
myself
again
I'm
Haze
I'm,
a
preacher
artistic
API.
So
if
the
API
was
a
church,
so
I'll
be
the
pastor
thanks,
that's
basically
what
I
do
right.
So
that's
just
a
quick
introduction
about
me.
So
in
today's
trade
right
we're
going
to
be
talking
about,
you
know
how
to
start
contributing
to
dogs.
Basic
API,
docs
I
can
become
a
contributor.
A
You
know
just
don't
need
to
open
source
what
you've
learned
so
far
contributor
in
terms
of
in
terms
of
documentation
now
Jay
Cutters
and
your
challenges,
and
how
you
eventually
like
made
this
phone
right.
The
business
is
fun,
but
I
can
say
it's
kind
of
hard
for
a
lot
of
people.
Also
so
I'm
gonna
start
myself.
Right.
I
have
to
lead
by
example
right
since
I'm,
a
pastor
so
and
you're
my
like
what
what
do
they
call
people
that
come
to
church
members.
A
Yeah,
so
I'm
gonna
give
a
quick
every
time
they
started
open
source
right.
So
I
was
in
the
library
in
this
Library
in
one
of
my
projects,
and
there
was
a
typo,
it
wasn't
actually
a
typo,
but
it
was
a
typo,
so
I
was
really
documentation
and
they
there
was
this
unfortunately
statement
but
I
feel
it
was
supposed
to
be
East
right
and
it
was,
it
was
written.
Worse
and
I
was
like
that,
doesn't
make
sense.
Then
I
opened
an
issue
and
told
him
and
Taylor.
A
A
Him
it
has
to
be
well,
he
is
not
was
and
I
was
like
fine,
fine,
fine,
just
fix
it.
That's
that's
correct
it.
You
want
is
fine,
just
put
ease,
then
I
fix
the
typo
and
change
it
to
ease,
and
it
was
like
really
you
did.
It
was
like
really
you
you
open
the
pull
request
for
that
and
I'm
like
yes,
then
it
matched
the
pull
request
and
that
was
actually
open,
like
that
was
my
turn
into
open
source.
A
simple,
random,
weird
stuff,
right,
I,
understand.
C
D
A
Amazing,
like
this
is
fun
right,
not
not
my
project,
somebody's
house
projects,
my
contribution
is
there
ever
since
I
started,
doing
a
lot
of
contributions
so
for
the
laptop
reacts
parcel
right
and
eventually,
where
I
finally
found
where
my
heart
is
right,
I
believe
from
my
heart
up
and
down
and
open
Souls,
then
I
found
this
API,
so
I
fell
in
love,
love
by
special.
That
was
that
is
real.
A
This
is
the
real
team
right
nobody's
first
side
I
get
to
experience
it
as
an
API
because
of
the
amazing
Community
they
have
and
I
felt
a
part
of
it
instantly
right,
then
I
think
that's
I
don't
have
to
go
in
depth.
This
is
not
my.
This
is
not
my
stage.
It
is
all
yours,
so
any
thoughts
when
I
go
first
I.
C
C
And
at
that
time,
I
just
started
my
journey
into
Tech
right
so
I
know
as
a
new
techie
you're
always
wanting
to
like
go
to
conferences,
and
you
want
to
network
and
meet
people
and
all
of
that
I
I
never
heard
about
open
source.
I
just
wanted
to
be
there.
So
then
different
speakers
spoke
about
open
source.
C
You
know
I
learned
from
there,
but
I
still
didn't
contribute
right
after
the
doors
of
that
conference,
so
fast
forward
to
like
August
later
that
that
same
year,
I
like
read
an
article
by
someone
and
then
she
she
wrote
about
how
to
contribute
to
open
source
for
beginners
right
and
I
I
loved
All,
She
Wrote
inside
of
the
article,
and
luckily
she
added
her
Twitter
handle
inside
of
that
article.
So
I
reached
out
to
her
on
Twitter
and
I
was
like
okay.
I
want
to
contribute
to
a
close-ups,
but
it's
really
like
I
I.
C
How
would
I
put
it
it's
it's
it's
kind
of
strange
for
me
and
I.
Don't
know
how
to
start
I
don't
know
where
to
begin
who
do
I
speak
to
even
if
I
see
an
organization
I
want
to
contribute
to
so
I
reached
out
to
her
and
she
she
was
very
nice
and
friendly
and
literally
handheld
me
right
to
contribute
to
one
of
the
organizations
she
was
contributing
to
at
that
time.
C
So,
and
she
made
me
understand
that
there
is
Thomas
contribution
is
beyond
just
like,
maybe
contributing
to
the
code
base
or
something
you
can
also
contributes
through
documentation
as
simple
as
fixing
typos
like
you've
said
so,
and
she
returned
me
and
then
that
was
it.
That
was
my
first
contribution
to
open
such
documentation
and
since
then,
I've
been
contributing
mostly
through
documentation.
So
yeah
I
am
as
well
as
the
just
augmented.
A
C
B
D
F
D
C
D
F
E
Yeah
sure
yeah,
so
my
my
very
first
contribution
was
back
in
2020,
so
I
remember:
I
got
into
open
source
because
there
were
a
few
friends
of
mine
who
got
selected
in
jsop
and
I
got.
At
the
same
time
the
popularity
of
Open
Source
in
India
was
Rising
like
it
was
very
high.
At
the
time.
I
saw
a
lot
of
YouTubers
doing
a
lot
of
great
stuff
and
then
I
shifted
to
Twitter
and
every
tweet
I
saw
was
how
to
get
started
in
open
source.
The
benefits
of
Open,
Source
and
I'm.
E
So
I
just
went
on
to
the
gsoc
organizations
page
and
at
the
time
I
was
doing.
Android
development
and
I
selected,
an
organization
of
an
Android
app
and
their
documentation.
Page
I
just
fixed
a
small
typo
at
that
time,
because
that
that
app
had
a
separate
documentation,
Channel
and
at
that
time
I
was
way
too
afraid
to
directly
jump
into
the
development
related
stuff
and
fix
the
small,
typo
and
I
remember
having
a
lot
of
setup
issues
and
all
that
and
getting
very
nervous
about
that.
E
But
I
think
the
experience
of
your
first
PR
getting
merged
it's
like
greater
than
anything
else
and
then
straightforward
to
G
salt,
2022
I
started
working
on
the
real
world
documentation.
So
in
the
beginning,
I
just
I,
remember,
I.
Think
resource
interns
will
remember
it.
There
was
an
definition
of
event-driven
architecture
missing
from
one
of
the
pages
and
I,
along
with
a
friend
of
mine,
who's,
also
a
regular
contributor
in
async
API.
We
actually
fixed
and
added
that
documentation
in
the
in
the
main
website,
documentation,
Channel
and
yeah.
F
F
So
I
heard
about
outreaching
during
she
called
Africa,
so
I
applied
and
I
got
in
the
first
round
was
done,
then
the
second
one
was
contributing
into
open
source.
So
I
didn't
start
by
fixing
a
type
of
gnome,
but
I
had
to
create
like
a
notebook
where
we
had
to
take
like
Wikipedia
articles
and
I
can't
really
remember
the
details
of
the
the
whole
project,
but
yeah.
That
was
my
first
contribution
to
open
source.
F
A
C
E
F
A
A
C
So
I
went
through
each
of
them
and
I
think
API
being
the
first
on
the
list,
like
I,
actually
took
my
time
like
studying
a
box
I
think
if
yeah
and
all
of
that
and
when
Alejandra
made
it
sweet
about
like
she's
looking
for
interns
right
to
work
on
the
project,
I
signified
my
interest
and
then
joined
the
slack
community.
So
I
sent
her
a
message
that
I
would
love
to
participate
in
the
program
and
then
forwarded
my
my
email
to
her
and
all
of
that.
C
So
she
conducted
interviews
and
I
was
ready
because
I've
made
my
research
and
all
of
that,
so
I
was
ready
for
the
interview
and
then
after
the
interview,
I
was
surprised.
I
got
in,
like
you
know,
after
applying
to
other
kind
of
open
source
programs,
and
then
you
are
rejected
and
you
you
saw
yourself
like
you
know,
being
accepted
to
one
of
the
best
open
source
programs.
You
feel
happy
and
it
felt
so
surreal,
so
I
was
so
excited
about
the
opportunity.
I
knew
that
I
was
definitely
going
to
learn
and
grow.
C
What
made
me
feel
that
I'm
in
the
workplace,
the
community,
is
very
welcoming
I,
really
love
the
fact
that
everyone
in
the
community
were
really
like
ready
to
accept
you
in
Alejandra
was
there.
She
was
willing
to
give
you
resources
to
like
put
you
up
to
speed
on,
because
I
had
no
idea
about
what
event
driven
architecture
is
all
about
mostly
a
front-end
person.
My
own
is
just
to
design
build
web
interfaces
right.
C
So
when,
when
I'm
hearing
about
Evangeline
architecture,
I'm
like
okay,
I,
don't
know
about
this
thing
and
yeah
I
am
and
I
have
to
contribute
right,
give
my
best
shot.
So
she
was
really
there
like
very
helpful
she's
shared
a
lot
of
resources
that
put
me
up
to
speed.
Lucas
also
did
a
couple
of
onboarding
videos
that
really
helped
as
well.
So
the
community
is
very,
very
welcoming
and
I'm
definitely
still
going
to
be
contributing
right
after
Jesus.
So.
A
Yeah
I
can
vouch
for
that,
so
you
would
eventually
still
contribute
because
I
I
was
I
actually
started
contributing,
but
I
was
also
a
good
season
of
dogs
I'm.
Sorry,
this
isn't
good
enough
code
participants
that
was
last
year
at
Postman,
right
and
I
was
so
interested.
I
said
inventive
and
architecture,
so
I
was
like
API.
I
was
doing
a
lot
of
stuff
right,
but
then,
after
the
program
right
I
couldn't
just
leave,
I
was
I
was
so
involved
right,
I
was
having
so
many
cool
stuff.
I
was
building
amazing
tools.
A
B
B
Okay,
I,
don't
think
I
chose
the
same.
Kpi
I
feel
like
the
first
time.
I
came
across
I.
Think
a
guy
was
on
Twitter
when
I
saw
the
Tweet
by
Alejandra
about
that
she
was
accepting
of
the
certain
interns
and,
during
that
time
frame.
I
was
also
like
looking
through
the
list
and
trying
to
figure
out
something
that
I
could
contribute
to
and
from
the
application
process.
B
I
asked
her
about
how
can
I
get
started,
contributing
and
stuff
like
that,
and
she
gave
me
a
a
link
to
the
list
of
issues
that
are
there
on
GitHub
and
told
me
to
look
through
it
and
see.
If
there's
something
that
interests
me
and
I
knew
from
that
point,
even
if
I
didn't
get
accepted
as
an
intern,
I'd
still
really
really
love
to
contribute
and
I
sit
down
six
months
down.
The
line.
B
I
also
really
feel
sad
that
this
side
is
coming
to
an
end,
because
I
feel
like
I,
really
hate
awesome
people
and
I
think
that
they
initiative
is
really
really
nice
and
generally
watching
with
everyone,
has
been
Pleasant
learning
a
lot.
It
just
feels
like
I'm
part
of
this
community,
so
even
after
this
is
naturally
still
going
to
contribute
so
yeah.
A
That
was
awesome,
so
I'm
gonna
give
a
special
shout
out
to
Alejandra
like
for
real,
even
even
the
fact
that
we
are
like
on
the
same
team.
I
still
learn
a
lot
from
her
and
she
doesn't
just
provide
resources
for
you
guys.
Also.
She
gives
me
love
just
tons
of
resources
right
and
I
really
like
appreciate,
so
a
special
shout
out
to
Alejandra.
No,
you
you're
the
best
you're
the
best.
You
did
amazing
stuff
for
the
community
for
real
Nelson
you're.
The
next
person
I
can
say.
D
D
When
I
saw
the
proposal
for
gsod
right,
it
was
very
articulate
and
then
I
kind
of
knew
what
they
wanted
from
the
program
right
and
what
they
wanted
to
achieve.
So
I
felt
like
okay,
I
could
align
my
goals
with
this
and
it
was
very
clear
for
me
fulfill
it
right.
So
that
was
like
my
exciting
part
of
the
day,
but
then
again,
another
very
important
factor
was
I
felt
very
welcome
because
Alejandra
kind
of
made
it
seem
like
we
were
all
part
of
one
big
family
right.
D
So
even
during
the
application
process,
it
was
still
like
sharing
resources.
Do
this
helping
you
learn
how
to
contribute
even
before
the
program
started.
So
all
of
this
and
I
was
a
junior
I'm,
a
junior
to
contributing
two
dogs.
So
all
of
this
put
together
just
helped
me
decide.
Okay
I
wanted
to
do
this,
and
this
is
the
right
place
for
me.
E
E
So
the
first
time
I
joined
is
the
reason
I
joined.
Async
keeper
initiative
was
that
basically
it
was
the
first
organization
listed
in
the
short
one
I
clicked
on
it,
and
I
saw
a
post
created
by
Alejandra
I,
think
yeah.
It
was
Alejandra
and
it
specifically
stated
that
hey
we
welcome
beginners
and
that
was
kind
of
well
comforting,
because
I
think
we
were
all
beginners
when
we
joined
it
and.
C
E
I
joined
the
slack
channels,
I
think
everybody
was
very
active.
The
community,
especially
Alejandra,
was
very
active.
I
remember
the
first
day
the
day
I
joined
I
had
some
setup
issues
and
I
asked
someone
from
the
async
API
community
and
Alejandra
replied
to
me
and
on
the
same
day,
we
had
a
meeting
like
a
Google
meet
where
she
resolved
my
issues,
and
that
was
very.
That
was
very
exciting
aspect
for
me,
because
no
one
had
really
responded
that
quickly
to
me
so
I
got
I.
E
A
Awesome
right
so
I
think
I
can
also
relate
to
your
story
project,
so
I
think
when
I
started
like
what
contributes
into
smkpi
I
was
stuck
right.
I
was
working
on
an
issue
and
I,
so
we
have
an
amazing
and
amazing
folk
called
Magic
in
the
community
and
to
my
first
time
contributing
right,
I
just
reached
out
to
him
instantly
like
I.
It
was
as
if
he
knew
me
already
right.
I
know
is
this
my
first
time
performance
into
the
community
right
to
the
project
and
we
were
going
back
and
forth.
A
We
went
I
went
directly
to
Red
to
his
DM
right.
Isn't
that
crazy?
So
we
had
a
really
nice
conversation
and
I.
Think
that's
one
thing
about
the
community
right.
We,
we
are
very,
very
amazing.
I,
don't
even
know!
Amazing
is
not
a
word
to
use
right.
That's
on
that
qualified
for
us
right.
So
that's
why
we
are
Community
First
right.
We
put
the
community,
even
our
public
project
right
so
and
I
think
what
Alejandra
is
doing
and
what
she
did
is
amazing
for
the
community
right,
Yes.
Actually.
F
Okay,
so
my
story
coming
across
with
I
think
API
I
didn't
know
that
Jesus
was
open
actually
until
I
saw
Alejandro,
Street
and
I'm
lazy.
So
this
whole
thing
of
writing
proposals.
I
wasn't
really
into
it.
Actually.
So
when
she
said
okay,
you
don't
need
to
write
in
full
puzzle.
You
need
to
book
a
set.
I
said:
okay,
let
me
just
apply
and
see
how
it
goes.
I
didn't
know
anything
about
us
in
kpi.
I
didn't
know
anything
about
event
trigger
architecture
until
I
met
earlier
that
day,
so
yeah.
F
So
one
thing
later
from
the
Tweet
to
inbox
inbox
to
the
meeting
as
well,
then
I
had
a
nice
chat
with
Aliana.
She
was
so
welcoming.
We
were
like
in
a
conversation
we're
so
in
sync,
I
mean,
like
our
conversation,
lasted
more
than
30
minutes,
of
which
it
was
not
supposed
to
happen
like
that.
Then
I
got
a
notification
that
I
got
in.
My
slack
was
buzzing
actually
that
day
and
my
WhatsApp
like
people
say
hey,
congratulations.
F
We
hear
that
you
entered
I
didn't
even
know
that
day
as
well,
so
yeah
so
fast
forward,
like
I,
didn't
know
anything
about
edas
or
asynch.
Api
then
later
on,
I
got
onboarded
by
Lucas
and
also
karuna
one
of
the
resort
intense
on
board
a
new
using
git
as
well.
Then
one
thing
led
to
another,
then
I
started
contributing
understanding.
What
Eda
is
and
yeah
that's
how
it
has
been
so
far.
A
A
A
I
want
to
do
this.
I
want
to
be
the
face
of
the
community
at
this
particular
event
or
I
want
to
also
let's
talk
contribution,
live
stream
just
like
this
right.
You
want
to
be
the
host
I
just
stepped
down
right
because
we
are
all
part
of
the
community
is
equal
and
I.
Think
that's.
That
is
amazing,
because
we
treat
all
of
us
saying
so
and
I
think
that
is
one
thing.
I
feel
a
lot
of
social
Community
out.
A
There
are
missing
most
of
them,
so
it's
the
projects
where
I
can
communicate
and
we
for
the
Community
First
it's
a
project
because
without
the
community
there
is
no
project,
so
We
Are
Family.
Actually
so
here's
your
family,
so
yeah,
so
so
so
far.
You
know
you
guys,
like
Florence,
reminded
me,
which
you
should
not
remind
me
that
because
of
my
dogs,
is
coming
to
an
end.
A
F
It's
been
a
great
experience.
Actually
I
learned
a
lot,
especially
when
it
comes
to
communication.
Collaboration
writing,
especially
special
technical
documentation,
like
I,
said,
I,
didn't
know
anything
about
EDH
and
funny
enough.
My
first
dog
was
the
most
hardest
dog
that
I
got
like
to
create
servers.
There
was
nothing
literally,
nothing
I
had
to
like
go
back
and
forth.
F
I
can't
remember
how
many
comments
were
in
my
pull
request,
I
think
we're
over
80
or
something
so
really
really
hard,
but
thank
you
so
much
aleandra
for
assigning
me
that
job,
because
it
made
me
a
resilient
I
tested
me
like
in
all
ends
like
communication,
wise
writing,
wise
technical
documentation,
researching
as
well,
using
my
image,
JS
creating
diagrams
as
well,
because
the
funniest
fun
part.
So
it
was
all
a
good
experience.
Learning
experience,
learning
curves
and
it
was
it
has
been
fantastic
and
I
can
I
can't
say
enough.
A
A
F
Yes,
I
did
face
imposter
syndrome
because
I'm,
like
okay
I,
don't
know
the
engineers
I,
don't
know.
Lucas
I
haven't
spoken
to
Lucas
I,
don't
know,
say
jail,
I,
haven't
spoken
to
say:
I,
don't
know
Fran.
So
how
do
I
approach
those
people
like
to
ask
okay?
What
I
wrote
is
it
correct?
Can
I
have
resources?
Can
you
review
my
pull
request?
So
those
are
some
of
the
challenges
before
the
stream
room
number
one
that
I
can
make
me
a
highlight,
but,
like
I
said,
I
think
API
Community
is
a
family.
F
Everyone
is
welcoming.
Everyone
is
willing
to
jump
there
and
say:
oh
okay.
This
is
where
you
got
wrong.
This
is
where
you
got
right.
This
is
how
to
go
and
provide
resources
as
well
and
Direction,
and
everyone
was
willing
to
say.
Okay,
if
you
don't
understand
anything,
let's
jump
into
a
call
and
I'll
explain
everything.
So
yeah
important,
overcoming
importance
syndrome
was
one
of
the
challenges
that
I
faced
so.
A
E
Yeah
sure
so
one
of
the
challenges
I
faced
was
I.
Remember
thinking
that
before
writing,
documentation,
I
need
to
know
each
and
every
aspect
of
the
generator
tool,
because
I
work
on
the
generator
tool
under
Lucas
and
I.
Remember
thinking
that
and
being
super
nervous
about
it,
but
as
the
program
went
and
Lucas
also
told
us
that
it
was
good
that
we
are
learning
about
the
generator
tool
as
we
are,
writing
talks
about
them.
So
that
was
a
different
experience.
Learning
bits
by
bits
about
different
components
of
the
generator
tool.
I
remember.
E
E
As
you
must
have
known,
Alejandra
is
very
strict
about
checking
them,
but
I
don't
relate
and
it
was
full
of
learnings
I
received,
like
I,
had
a
lot
of
merge,
conflicts
and
I
received
I,
resolved
them
and
also
learned
bunch
of
new
stuff
and
yeah
I.
Think
that
was
very
fulfilling
learning
about
the
generator
tool,
as
well
as
technical
writing
in
general.
E
Yeah
I
did,
but
it
was
I
was
quick
to
overcome
it,
because
there
were
a
lot
of
helpful
people
from
the
community,
as
someone
said
that
they
were
always
ready
to
jump
in
a
meeting.
If
we
didn't
understand
something-
and
we
did
a
lot
of
meetings
like
that
me
and
Lucas
and
Alejandra
whenever
I
did
not
understand
something,
they
actually
sat
me
through
the
meeting
and
explained
every
bits
of
it
and
so
yeah.
There
was
imposter
syndrome,
but
the
people
in
the
community
made
it
very
easy
to
overcome
it.
A
Awesome
so
I
I,
you
folks,
might
be
asking
or
might
be
thinking.
Oh
white
Ace
asking
us
if
you
had
imposter
syndrome.
So
the
reason
I
was
asking
because
when
I
started
contributing
to
watching
API
right
so
I
started
like
appearing
before
so
is
everybody's
old
Community
meetings
and
I
used
to
attend
Community
meetings,
but
I
never
had
my
camera
on
so
you'll
notice
that
right
so
I
attend
meeting
people.
I
never
had
my
camera
at
home
and
the
notice
that
they
reach
out
to
me
I
think,
look
at
it
specifically
I'm,
saying
Ace.
A
Why
are
you
always
like
I?
Would
like
I'm
scared?
Oh
I,
don't
it
was
like?
Are
you
a
monster?
I
was
like
no
I'm.
You
want
like
sure
if
you're
human
just
have
a
camera
on
so
the
next
meeting
I
had
my
camera
on,
but
I
couldn't
talk.
Just
looking,
I
have
questions
right,
I
could
ask.
Then
you
noticed
that
again,
it
came
back
to
my.
C
D
D
In
the
process
of
Json,
if
I
was
actually
going
to
give
our
colleagues
to
Lucas
here,
because
who
does
this
tell
you
what
you're
doing
wrong
or
you're
supposed
to
do
right
and
then
to
do
it?
Talk
to
me
and
like
during
the
rest
of
the
experience
and
then
kind
of
smoothing
the
whole
system?
Yeah
I
mean
it's
easy
for
me
to
contribute,
and
all
of
that
so
I.
D
As
for
importance
from
I
had
my
own
first
year
of
personal
syndrome,
because
I
remember:
I
wanted
to
go
to
something
that
I
had
no
idea
about,
because
I
didn't
know
what
I'm
even
dripping.
That
picture
was
I
watched
a
lot
of
tutorials
braid
articles
just
to
wrap
my
hand
around
it,
but
let's
do
not
coming
together
and
so
after
Lucas
did
the
whole
live
stream,
where
we
have
five
episodes,
I
think
so
that
kind
of
hits.
You
know
this
is
the
context
of
me
and
then
helped
me
pass
my
apostle.
B
C
Okay,
so
my
experience
has
been
amazing.
Actually
I
learned
quite
a
lot
I,
you
know,
like
I,
said
and
yeah
I
had
no
idea
about
event
driven
architecture.
So
there
was
a
lot
of
reading
to
do
right.
You
know
from
Reading
different
blog
posts
to
watching
the
tons
of
YouTube
tutorials
on
async,
API,
Channel
and
then
Lucas
was
really
helpful
with
the
onboarding
videos
he
did,
which
Nelson
mentioned,
like
that
kind
of
put
a
lot
of
things
into
order
right,
like
you
know
from
that.
C
That
really
helped
me
understand
the
projects
more
and
then,
like
things,
I,
had
that
the
idea
of
things
to
write
about
and
all
of
that
so
for
the
challenges
right.
The
first
challenge
I
had
when
I
joined
this
in
kpi
was
the
setting
up
the
project
on
my
PC,
my
pc.
At
that
time,
I
could
not
like
run
the
build
locally
on
vs
code.
So
that's
to
use
like
the
cheat
pod
that
that
was
also
mentioned.
The
alternative,
so
still
her
ad
issue
with
that.
C
So
Lucas
helped
me,
like
you,
know,
be
solving
that
issue
and
that's
one
of
the
challenges
imposter
syndrome
as
well.
I
had
my
fair
share
at
some
point:
I
was
like:
oh
can
I
do
this?
Will
I
be
able
to
do
this
since
I
had
no
knowledge
about
event-driving
architecture
but
I
kept
on?
You
know
like
telling
myself
you
can
do
this.
You
can
do
this.
You
know
learning
how
to
code
itself.
It's
a
thing
so
trying
to
like
learn
something
you
should
not
be
strange.
C
So
you
are
someone
who,
like,
for
example,
like
myself,
switching
from
a
different
background
to
Tech,
so
I
felt
that
I
can
do
this
and
with
the
help
of
Alejandra
as
well,
she
really
made
it
like
awesome
that
okay,
yes,
she
was
really
patient,
very,
very
patient,
so
she
kept
on.
You
know
telling
me
that
okay,
yes,
that
you
can
do
this
and
all
of
that
so
yeah
yeah.
We
are
thank
you.
D
B
F
C
F
E
C
F
D
F
A
F
A
A
Back
now
so
I
mean
it's
a
lot
of
I'm
gonna
watch
the
recap
of
his
videos
to
watch
where
I
meet
right
so
and
I.
Guess
it's
been
so
much
fun.
You
guys
will
spoke
about
how
Eastern
kpi
eventually
helps
you.
You
know
also
not
just
help.
You
contribute
right.
They
also
bring
out
the
best
in
you
and
I.
Think.
That's
that's
amazing,
right,
I
I,
also
I
I,
before
I
couldn't
even
appear
on
on
strings
right.
So
look
at
me
now.
I'm
always
like
chilling
on
live
streams.
A
I
want
to
do
live
streams
every
time.
Is
it
amazing?
So
it's
I
I
actually
started
doing
this
thing
because
it
seems
fun
right.
It's
a
kpi.
The
community
helped
me
bring
down
the
beasts
that
was
sleeping
in
me
like
the
up
and
now
I
always
I'm,
always
pumped.
You
know,
I'm
mostly
Community
meetings
coming
to
meetings,
I'm
building
myself,
just
because
the
community
told
me
I
can
I
can
do
it.
A
A
Right,
so
if
you,
if
you
so,
we
I'm
pretty
sure
I
would
also
be
at
a
couple
of
conferences
like
next
year,
which
Oscar
face
is
part
of
it.
So
we'll
be
part
of
the
sponsors
of
Oscar
Fest
I'll,
try
my
best
to
make
sure
I
post
my
sponsors,
the
next
Oscar
Fest
and
also
another
conferences
coming
up
which
I
will
be
into
this
country
where
I
get
to
confirm.
B
A
So
if
you,
if
you
even
after
the
division
of
dogs
right,
you
can
still
be
part
of
the
family
right
too,
but
an
example.
You
say
so.
The
ambassador
program
so
basically
is
currently
like
working
on
an
ambassador
program.
Right.
You
could
be
part
of
the
ambassadors
right
you,
you
help
preach
the
gospel.
You
you
talk
about
ckpis
conferences,
you
get
something
back
in
return
right,
so
that's
part
of
the
things
you
can
also
like
do
after
the
Google
scene
of
dogs
right.
We
also
like
have
mentorship
programs.
A
So
if
you
feel
oh
after
ecosystem
of
dogs,
I
want
to
do
mentorship
right,
we
do
it
every
year,
so
you
guys
are
like
the
first
set
of
the
I
think
this
is
our
first
time
participating
and
you're
the
first
set
of
people
that
actually
you
know,
and
also
our
mentorship
program.
Also
we
started
this
year
so
which
is
also
yeah,
so
special
shout
out
to
you
guys.
So
that's
it.
There
are
tons
of
ways
to
like
keep
contributing
to
recent
API.
You
know
I'm,
really,
I'm
I,
don't
know
a
lot
about.
A
You
know,
writing
docs,
well,
I!
Think
I'm.
Also,
like
learning
so
much
now,
because
Alejandra
I'm
a
student
actually
so
I'm,
not
I'm
a
student
because
she's
helping
me
a
lot.
You
know
to
know
understanding
how
Dr
All
I
Do
Is
Write
codes,
but
now
I'm
more
diverse.
You
know
all
right,
I'm
I'm
trying
to
write
documentations
also
so
I
also
have
questions
right
and
I
feel
you
guys
will
be
like
so
I
see
myself
as
as
as
a
beginner
right
in
writing.
A
Dogs
right
in
writing,
documentations
and
as
a
beginner
and
a
few,
maybe
other
people
that
are
watching
this
stream
later
would
eventually
be
beginners
also,
and
they
might
have
some
questions.
Also
so
I'm
gonna
stand
not
act,
I'm,
a
beginner,
so
I'm
not
going
to
act
as
a
beginner,
because
I'm,
a
beginner,
so
I
have
a
couple
of
questions
right.
So
my
first
when
I
was
I,
was
asking
a
particular
documentation
about
how
changes
are
introduced
to
the
specification
right.
A
A
So
no
for
real
and
to
me
I
was
like
what
do
you
mean
it's
like
a
blog
post
and
I
was
like
this?
Is
the
dogs
not
a
blog
post
I'm,
not
like
I,
don't
understand
so
it
was
like
she
was
like,
so
dogs
are
not
meant
to
be
that
long.
So
this
looks
like
an
article,
but
now
I
have
a
question.
So
how
do
I
know
when
this
should
be
an
article
and
when
this
should
be
dogs?
It
was
dude.
To
be
honest,.
F
The
dogs
straightforward
straight
to
the
point:
I'm
I'm,
the
nails,
so
when
you
hit
the
nail,
is
called
straight
pump.
So
that's
what
dogs
are?
Dogs
have
concise
straight
to
the
point.
They
don't
explain
a
whole
lot
of
stuff.
There's
no
storytelling!
Actually,
unlike
blog
posts,
blog
post
is
more
Australia
storytelling
and
keeping
the
user
engaged
and
with
docs
is
just
something
that
is
straightforward.
Okay,
do
you
want
to
use
git
or
do
you
wanna,
install
python
3.6,
you
just
go.
F
Peep
install
3.6
star
stand
that
stocks
for
you,
but
if
you
want
to
write
a
blog
post,
then
you
need
to
start
through
storytelling
and
say:
okay,
you
want
to
install
python.
This
is
how
you
do
it.
This
is
how
you
go
about
it.
Facebook
install.
Why
do
we
use
people?
Why
do
we
say
install
next?
So
that's
those
are
the
differences
between
dogs
and
blog
posts.
A
Oh
really
so
I
I
think
for
the
explanation
so
and
I
I
think
because
I
felt
oh
I
would
change
the
interest
to
the
specification.
Then
I
was
like
falling
everything
now
so
I
was
to
be
honest,
it
was
long
and
I
was
told.
This
doesn't
look
like
a
documentation.
This
looks
more
fanatical.
So
with
that
help
right
we
were
able
to
like
reduce
it,
reduce
it,
reduce
it,
and
we
had
just
really
smart
content,
and
that
was
it
don't
sound
like
wow.
D
A
Okay,
okay,
now
I
understand
so
imagine
now.
I
have
a
question.
Another
question.
Actually,
so
if
I
am
like
new
to
contributing
right
to
dogs
right,
how
would
you
advise
me
to
get
started
right?
What
are
some
things
I
have
to
know
so
in
order
to
start
API
as
from
the
docs.
So
what
do
I
have
to
know
what
I
know
there
are
tons
of
issues
that
are
redox
related
on
on
GitHub,
right
and
maybe
I
want
to
pick
one
I'm.
Just
gonna
pick
one.
How
do
I
go
about
it?
A
C
When
I
see
a
project
that
you
like
or
that
resonates
with,
maybe
your
skill
level
or
something
the
best
thing
is
to
like,
maybe
reach
out
to
the
community
like
join
the
slack
Channel
and
then
ask
questions
and
then
also
visit
the
repositories
and
then
check
out
the
issues.
The
one
they
built
with
good
first
issues
or
fast
I.
Think
good.
C
So
if,
if
it's
not
assigned
to
someone,
you
can't
be
assigned
to
that
task,
and
then
you
start
contributing,
and
also
when,
when
you're
new
to
a
particular
project
is
always
good
to
like
Community
contribution
guidelines,
so
that
when
you
contribute
whatever
you
do
is
in
line
with
what
the
the
organization
or
the
project
requires.
So
it's
always
good
to
like.
First
off
ask
questions.
You
know,
reach
out
to
the
maintainer
and
then
read
the
contribution
guidelines
and
then
contributes
that's
based
on
my
experience.
A
C
A
D
Please
ask
questions
about
contributing
so
in
case
maybe
the
only
conditions
guide
in
addition
to
certain
projects,
you
can
talk
to
someone
on
the
NVM
community
and
then
get
outside.
So
does
it
have
an
idea
of
complex
about
make
sure
you
multiplications
guide
and
be
a
part
of
the
snap
Channel
and
then
just
be
there.
A
F
Reach
out
to
anybody
that
you
see,
we
have
participated
in
dogs,
we
are
all
we
have
all
been
there.
Actually,
so
I
think
we
are
the
best
people
to
ask
questions,
but
if
you,
you
can
also
like
check
on
the
how
to
contribute
Channel
or
you
can
send
a
message
on
the
docs
Channel
as
well.
Anybody
who's,
awake
or
who's
online
at
that
moment
who
they
help
you
to
assist.
You.
A
A
A
So
I'm,
like
we
have
this
issue
well,
I
was
I,
don't
know
how
it
applies
to
dogs
right,
so
I
feel
right,
maybe
I
I'm
trying
to
like
make
other
feature
or
fix
the
ball
right
and
comment
and
comment
and
comment
and
comment
and
comments
and
I'm
I'm
feeling
like
no
in
terms
of
dogs.
Does
that?
How
do
you?
How
do
you
think,
as
a
new
contributor
I,
can
handle
the
patient
right?
Imagine
having
80
.
A
B
F
Feedback
is
very
important
like
for
me.
My
first
dog
like
I,
said
I,
think
I
got
over
80
I'm,
not
I,
can't
remember
the
exact
number
it
was
over
80.,
so,
but
each
and
every
time
there
is
feedback.
I
got
to
improve
I
got
to
understand
better
I
got
to
apply
the
knowledge
that
I
got
a
little
bit
better,
so
be
open-minded,
accept
feedback.
It
comes
and
apply
that
into
your
dogs
or
into
your
code
or
whatever.
The
case
may
be
so
be
happy
that
they
are
comments
there,
rather
than
not
having
a
pull
request.
F
B
We've
been,
you
can
add
on
to
what
that
he
has
said
so.
I
remember
my
first
request
here
at
a
Sync
API.
It
has
to
be
moved
by
Alejandra.
It
cost
less
75
comments
like
one
like
the
very
first
time
and
I.
Remember:
I,
felt
really
really
overhealth
and
I
was
procrastinating
on
addressing
the
issues
and
like
checking
all
the
feedback
that
was
left,
but
during
our
next
meeting
with
Alejandra
I.
B
Remember
her
telling
me
that
she
left
she
has
reviewed
my
PR
and
that
once
I
have
not
yet
started
it
because,
as
it
was
a
lot
of
feedback,
I
got
over
fund
I,
procrastinated
and
I
I.
Don't
have
the
motivation
to
like
open
it
and
address
it
because-
and
she
told
me
most
of
the
feedback
that
you
have
left
are
suggestion,
so
I
feel
like
if
you're
contributing
to
dogs
in
Arkansas
most
of
the
feedback
that
will
be
left,
especially
for
the
for
the
reviews.
B
A
Yeah,
so
if
you're
watching
this
live
stream-
and
it's
your
first
time
contributing
or
you're
interested
in
computational
documentation
and
you're
scared
right,
but
Instagram
is
real
and
open
source
you
might
feel
I,
don't
know
these.
Folks,
oh,
is
my
product.
Is
my
protocol?
Is
gonna
hang
in
there
forever
without
actually
getting
mad?
A
What
can
I
do
so?
I'm
gonna
give
you.
This
is
right.
I
feel
sick.
Api
is
the
best
style
from
the
contributing
and
I'm,
not
sure.
I
can
I
can't
even
say
I
can't
even
vouch
I'm,
not
sure,
there's
a
proof
request
that
seems
important
right
and
sometimes
you
can
just
paying
the
maintenance
between
your
product
isn't
getting
enough
response
and
yeah.
They
will
make
sure
it
gets
enough
attention
squares
right.
So
this
is
open
source,
big
projects,
personal
contributing
to
dogs.
I
can
tell
this
is
a
this.
A
Is
your
best
bet
to
contribute
to
async
API,
and
we
have
you
know
and
many
folks
that
can
help
you
when
we
have
a
Nissan
truly
or
sure
sure.
So
you
can.
You
can
say
a
lot
of
food
would
really
really
help
you
you
know
fix
whatever.
It
is
of
trying
I
think
that's
my
question
concerning
dogs,
so
I'm
gonna,
so
we
are
kind
of
out
of
time.
So
I'm
gonna
just
ask
the
one
last
question
right.
E
Yeah,
it
was
one
of
the
first
few
tips
I
received
from
from
Alejandra.
So
once
you
go
to
the
async
by
repository
and
the
first
thing
you
do
as
a
beginner
is
look
for
good,
first
issues
with
docs
and
good
good.
First
issues
Stacks
with
them,
and
there
are
a
lot
of
times
you
are
not
like.
All
of
these
issues
are
taken
already
or
as
a
new
contributor.
E
You
are
not
able
to
complete
all
of
them,
so
the
thing
you
can
do
is
go
through
the
existing
documentation
from
the
main
website
and
if
you
find
any
errors
or
any
typos
or
any
mistake,
you
can
just
create
a
new
issue
in
the
GitHub
repositories.
So
this
is
allowed
in
the
async
API
community
and
the
maintainers
will
review
that
issue,
and
if
it
is
a
legit
issue,
you
can
ask
the
maintainers
hey
I,
want
to
work
on
this
issue.
E
C
C
Okay,
so
one
thing
I
would
just
like
to
add
is
that
when
it
comes
to
contributing
to
open
source,
it's
very
important
to
be
patient
right,
because
there
are
like
lots
of
contributors
to
a
project
and
very
few
are
maintainers,
so
they
have
tons
of
work
to
do
and
all
of
that.
So
if
you're,
like
okay
I've
done
this
and
my
pre-request
is
not
merged,
I
feel
patience
is
really
key.
C
If,
like
at
some
point,
you
don't
get
response,
you
can
just
like
you
know
had
okay,
please
can
you
help
review
my
pull
requests.
I,
love
your
feedbacks
and
all
of
that,
but
it's
just
really
important
to
be
patient,
because
you
know
the
number
of
maintainers
to
contributors
is
very
like
the
Gap
is
really
large.
So
it's
very
important
to
be
patient
when
it
comes
to
contributing
to
all
source.
F
Yes,
be
open-minded
as
well
on
top
of
being
patient
very
important
like
when
you
receive
feedback,
you
must
be
open-minded
and
be
willing
like
to
implement
feedback,
because
I
know
sometimes,
like
we
said
our
first
peer
requests.
We
had
a
bunch
of
comments,
a
bunch
of
feedback.
It
can
get
overwhelming.
Somebody
can
get
offended
even
like
okay,
I've
put
so
much
work
into
this.
F
B
Yeah
sure
I
think
from
my
time
contributing
at
a
Sync
API.
The
major
take
away
that
I
have
is
to
learn
how
to
be
a
good
communicator
like
to,
especially
when
you're
working
in
open
source.
You
really
need
to
invest
in
your
communication
skills
and
also
be
really
receptive
to
feedback,
because
most
of
these
projects
are
maintained
by
a
lot
of
people,
so
they
they
pull
request.
A
Well,
that's,
that's
big,
that's
more
than
big
enough
for
me!
Take
away!
So
actually
that's
that's!
Nice!
Actually,
I
feel
you
guys.
Accent
is
clear
for
folks
that
are
interested
in
contributing
to
open
source
right
for
the
first
time
and
also
you
also
make
it
even
more
clearer
in
terms
of
contributing
to
async,
API,
docs
and
I.
Think
that
is,
that
is
more
than
more
than
enough
right
and
I'm
pretty
sure.
A
If
folks,
that
would
be
watching
this,
the
live
stream
later
on
would
eventually
learn
a
lot,
because
even
me,
actually
that
I
started
like
spending
more
time.
Writing
dogs
I
actually
learned
a
lot
from
what
to
leave.
Florence
said
about
communication
and
I
think
that's
a
big
part
actually
and
I
felt
if
I
wasn't
familiar
with
the
open
source
right.
A
If
I
wasn't,
if
it
was
my
first
time
actually
contributing
to
open
source
I,
think
I
would
be
pissed
right,
because
I
I
had
like
this
comment
back
and
forth
back
and
forth
back
and
forth
and
I
was
I
would
have
said.
Oh
it
I'm
done
like
yeah.
Actually,
because
and
that's
it
I
think,
the
communication
is
is
a
big
part
and
also
patience
right
and
you
have
to
be
patient
also
and
that
consult.
We
are
few
maintainers
and
a
lot
of
contributors.
So
that's
that's
not
an
easy
work
to
do
so.
F
A
They
they
give
enough
time
to
like
review
your
progress.
You
know
right
and
also
Patrick
said
something
amazing
right.
You
should
be
able
to
also
like,
if
you
find
something,
create
a
visual.
If
you,
let's
say
I
understand,
maybe
you
just
started
computer,
which
opens
and
in
a
list
of
issues
you
didn't
see
anything
you
feel
you
can
handle
right.
Maybe
there
are
more
bigger
than
you
think
we
can
also
create
an
issue
yourself,
maybe
find
some
something
like
a
typo
or
something
that's
not
clear
enough
right.
You
can
open
it.
A
It
bad
with
them
right
so
feel
free
to
create
an
issue
then
privilege
to
open
a
pro
request
for
that,
because
we
accept
all
types
of
contributions
right
from
dogs
to
designs
to
a
lot
of
things
right.
So
as
far
as
the
countless
contributions
So
since
today
is
an
application.
I
felt
to
learn
so
much
about
documentation
and
you
are
your
journey
into
open
source
is
amazing,
like
definitely
amazing,
I
thought
I
had
the
best
Journey,
but
well
at
all.
You
guys
won
already
one
so
I'm
gonna
keep
my
story
to
myself.
A
E
C
A
So
I
really
really
appreciate
you
guys.
You
know
honoring.
This
call
I
said
it
earlier
today,
I
was
hoping
to
just
have
one
person,
but
the
old
house
turn
up
so
this
this
has
been
fun
right
and
I
hope.
Maybe
later
just
live
stream
or
maybe
later
we
could
have
another
live
stream.
Where
we
might
talk
about
dogs.
A
A
Yes,
so
I'll
also
try
to
like
work
towards
that,
because
I
don't
want
this.
This
is
our
first.
Let's
talk
about
contributing
that
is
dogs
related
right
and
I.
Don't
want
it
to
be
the
last
right,
because
one
of
the
things
I'm
trying
to
do
is
to
be
as
diverse
as
possible
in
this
life.
Let's
talk
about
contribution
strips
right
so
from
designs
to
documentation
to
all
sort
of
things
right.
A
C
E
A
A
Yes,
so
that
is
the
end
of
today's
live
stream
and
yeah,
because
you
see
today's
game
was
formed.
We
had
a
lot
of
folks
today,
I'm
most
all
the
folks
we
have
today
are
all
your
participants
of
the
Google
summer
of
dogs
2022,
and
they
are
doing
amazing
stuff
with
the
community
and
you
can
see
their
journey
to
open
source
and
how
you
can
start
contributing
to
open
source.
So
they
actually
explain
how
you
can
contribution
to
open
source
based
on
their
understanding.
I
can
say
completely
interesting
API,
based
on
your
understanding.
A
So
why
why
children
contribute
to
say
we
have
amazing
communities
and
yeah.
So
that's
basically
everything
for
today's
live
stream.
So
if
you
like
this
video
or
you
find
this
stream
helpful
right,
don't
forget
to
like
And
subscribe
and
also
feel
free
to
join
our
slack
channel
GitHub,
so
just
start
contributing
because
open
source
is
live.
So
thanks
guys
for
joining
us
today,
I'm
looking
forward
to
seeing
you
guys
next
time,
peace.