►
From YouTube: GitHub Africa Virtual Meetup - October 2020
Description
5:31 - Start of program with Brian Douglas, Staff Developer Advocate (https://www.youtube.com/user/ilikerobot/)
7:55 - Git action traction
18:18 - Automate workflow process using GitHub Actions - Shodipo Ayomide (https://twitter.com/developerayo)
35:56 - Making Actions and Open Source software development tools more accessible - Martins Ewere, GitHub Account Executive
49:30 - How to get involved as a beginner in Open Source - Ruth Ikegah (https://twitter.com/ikegahruth)
1:00:23 - Documenting your Open Source projects - Shedrack Akintayo (https://twitter.com/coder_blvck)
1:21:35 - Your roadmap to frontend development - Ikram Babs-Lawa (https://twitter.com/code_quinn)
1:39:18 - Closing remarks
Download the video: https://github.co/3o9h9ro
Join our Africa Meetup group: https://github.co/Africa
GitHub is excited to host our second monthly Africa Meetup! This month we will be talking about how to get started contributing to open source, using actions and doing frontend development. Please join us on Tuesday, October 20th, from 3pm to 5pm WAT to 5pm WAT / 7am to 9am PDT.
A
B
B
The
sars
branch
of
nigeria
police
force-
and
I
just
want
to
let
you
know
that
github
stands
firmly
with
our
nigerian
friends
and
our
developers
everywhere
and
yeah,
and
we
we
are
hosting
this
event
specifically
for
you
and
for
you
to
be
able
to
amplify
your
voices
and
showcase
the
work
that
you
were
doing
in
your
community.
So
thank
you
for
that,
and
I
just
wanted
to
just
make
that
acknowledgement
up
front.
So,
let's
just
jump
into
the
event.
This
is
a
remote
event.
B
If
you
are
here
in
the
chat,
feel
free
to
type
ng,
we'll
use
that
as
our
either
that
the
you
can
use
the
clapping
emoji
as
well.
If
you
know
how
to
do
that
as
well,
so
give
us
a
hello
if
you're
here,
if
you're,
listening
if
you're
well.
Thank
you
very
much
excellent.
So
I'm
brian
douglas-
and
this
is
our
africa
meetup.
This
is
the
first
time
I'm
hosting.
B
This
is
our
second
time
doing
it
as
well,
and
I'm
super
happy
to
have
the
opportunity
to
hear
from
so
many
great
speakers
and
get
to
know
all
you
folks
as
well.
So
if
you
are
using
github
feel
free
to
drop
your
your
github
name
as
well.
I
know
we
have
our
real
names
here
on
on
youtube.
As
I
mentioned,
on
b
ducky
as
well,
and
what
I
want
to
do
is
I
want
to
jump
into
some
content
that
I
had
prepared
specifically
around
github
actions,
this
sort
of
high
level.
B
B
And
go
into
present
mode
and
there
we
go
all
right
so
yeah
this
this
really
quickly.
This
this
talk,
I'm
gonna,
give
us
around
to
get
up
action,
get
action
traction
specifically
around
github
actions.
It's
something!
I've
been
spending
a
lot
of
time
in
my
day.
Job
doing,
and
if
you
don't
know,
I
like
to
call
myself
the
beyonce
of
github.
This
is.
It
sounds
like
a
lot
of
hubris,
but
I
have
a
lot
of
respect
for
beyonce,
because
beyonce
she's
a
world
renowned
superstar.
B
I
had
the
opportunity
of
opening
up
for
beyonce
in
china.
Technically
I
did
it.
I
spoke
in
three
cities
away
from
shanghai
after
she
spoke
or
she
played
seven
weeks
later.
So
I
didn't
get
to
actually
open
up
for
her,
but
I
did
speak
in
china
around
the
same
time
that
she
was
there
sort
of
give
or
take
a
month
or
two,
but
I
what
I'm
getting
at
is
beyonce.
B
She
has
a
very
large
following
and
worldwide
so
which
I
mentioned
beyonce,
because
she's
she's
well
known-
and
I
hope
to
get
to
that
point
eventually,
but
here
at
github,
I'm
a
developer
advocate
at
github.
Brian
douglas,
that's
me
on
twitter.
This
is
me
on
github,
I'm
bdugi
on
github
and
I
actually
go
by
b
dougie
as
well,
so
feel
free
to
call
me
either
or
I'll
respond
to
both.
B
B
I
will
shout
out
to
you
as
well.
Get
up
universe
is
happening
in
a
couple
months,
so
definitely
check
that
out.
I'm
happy
to
answer
questions
about
that,
but
two
years
ago,
at
github
universe,
we
launched
this
feature
called
github
actions
and
github
actions
is,
if
you
are,
if
you're,
if
you're
really
familiar
with
github
actions,
just
give
us
a
wave
and
say
yes
or
no
in
the
chat
but
github
actions,
it's
a
really
powerful
feature
and
what
it
really
does
it
integrates
and
hooks
into
our
github
api.
B
It
provides
a
better
integration
experience
for
folks
who
just
want
to
do
things
like
automating.
Your
workflow,
which
I
know
are
our
next
speaker,
will
actually
go
into
detail
about
as
well.
But
what
we've
done?
We
take
these
primitives,
like
authentication
primitives
like
web
hooks
and
permanence,
like
the
the
api
itself
and
we've
sort
of
co-located
that
directly
inside
your
repos,
to
give
you
the
ability
to
do
some
really
cool
things.
So,
if
you
have
not
checked
about
checked
out,
github
actions
definitely
check
out
our
actions
landing
page.
B
B
One
of
my
repetitive
tasks
during
hacktoberfest
was
actually
reviewing
prs
and
the
way
I
I
managed
reviewing
prs
is,
I
would
get
a
someone
coming
through
with
the
pr
and
the
first
thing
I
do
if
you're,
the
first
person
or
first
time,
you've
actually
contributed
to
the
project.
You
get
a
welcome
message.
That's
powered
by
an
action,
and
what
I
do
with
this
welcome
message
is
actually
powers.
B
This
action
to
point
you
directly
to
the
discord,
because
what
I
want
is,
I
want
folks
to
have
a
great
experience,
the
first
time
they
sort
of
are
introduced
to
the
project
I
maintain.
So
with
that
being
said,
I
give
them
a
welcome
message.
I
thank
them
very
much
for
their
contribution
and
then
I
try
to
get
them
to
talk
to
me
in
the
discord
and
that's
really
the
focus
there,
because
I
want
them
to
have
an
interaction
with
me.
B
I
want
them
to
have
a
face
to
the
project
and
I
feel
like
they're,
just
sort
of
opening
prs
to
avoid
hoping
that
the
main
maintainer
will
accept
this
pr.
So
that's
what
I
use
if
github
actions
has
one
one
use
case,
and
I
use
this
use
case
and
I
use
this
analogy
too
as
well.
So
I
imagine,
a
lot
of
us
are
familiar
with
basketball,
but
I
I
come
from
the
the
experience
of
stan
lee
who's,
the
creator
of
marvel
comics.
He
has
this
quote
called.
B
Imagine
every
issue
is
your
first
issue
or
imagine.
Every
issue
is
the
reader's
first
issue.
So
if
you
don't
know
about
basketball,
I'm
about
to
explain
some
basketball
concepts
to
you.
Apologies.
You
already
know
this,
but
this
is
for
the
benefit
of
everybody
in
the
room.
So
this
is
a
basketball
court.
If
you
go
football
or
soccer,
basketball
is
basically
very
similar,
except
instead
of
dribbling
with
your
feet,
you
dribble
off
your
hands
and
the
object
is
to
get
the
ball
in
the
opposing
team's
hoop.
B
So
I
have
a
basketball
that
I
have
on
the
screen.
That's
going
directly
into
the
hoop.
This
is
the
concept
that
we
call
and
that
was
very
popular
in
the
in
the
mid
2000s
called
full
court.
Layups
allen
iverson's
one
person
who
might
might
be
familiar
with
folks,
I'm
a
bit
older
than
some
people,
so
I've
been
watching
basketball
for
a
long
time
and
well
for
a
while,
and
so
the
idea
of
full
court
layups.
B
When
you
have
five
people
on
a
team
you,
the
the
object,
is
to
leverage
your
entire
team
to
score
the
points.
But
there
was
like
this
phenomenon
where
only
one
player
would
do
all
the
work
and
the
rest
of
the
players
would
be
decoys
and
that's
okay,
like
if
you're
the
solo
developer
on
a
team
or
you
work
for
a
agency
and
you're
doing
all
the
work.
I
think
that's
fine,
but
when
you
want
to
really
get
that
sort
of
10x
developer
experience
the
tedx.
B
Actually
it's
actually
leveraging
the
entire
team,
and
not
just
yourself
so,
and
maybe
that's
just
my
perception
of
what
that
should
mean.
But
what
I'm
getting
at
is
with
full
court
layups.
You
probably
don't
do
that.
You
don't
want
to
be
the
only
one
shipping
code.
You
don't
want,
the
only
one
that
has
the
keys
to
merge
pr's.
B
B
So
they
took
statistics
applied
to
the
nba,
and
then
they
found
out
that
there's
one
point
in
the
basketball
court,
where
you
have
the
highest
percentage
of
making
the
shot
and
having
it
go
in
and
they
call
this
area
31.,
and
I
I
am
going
to
bring
this
to
a
point,
and
this
will
make
sense
eventually
so
bear
with
me.
But
area.
31
is
the
point
where
it's
so
cl,
it's
close
to
the
net
or
to
the
hoop
itself
that
the
way
you
shoot
it
with
the
arc,
it's
it's
very
difficult
to
defend
against.
B
So
what
happens
is
most
teams
they
they
over
index
and
they
optimize
their
place
to
get
the
ball
to
that
point
of
the
hoop
or
the
point
of
the
court
to
make
the
the
actual
the
point
go
in.
So
what
I'm
getting
at
is.
There
are
certain
things
that
you're
doing
in
your
code
base
certain
things
in
your
developer
workflow
and
your
the
workflow
lifecycle
that
you
can
over.
You
can
actually
automate
and
optimize
inside
of
your
workflow.
B
B
B
B
The
way
we
submitted,
we,
we
took
submissions
for
the
hackathon
itself
was
through
a
github
repo,
so
this
entire
website
was
powered
by
one
github
repo,
which
is
it
sounds
pretty
obvious,
but
what
I'm
getting
at
is
that
these
submissions
were
also
pull
requests
onto
the
same
repo.
That
was
powering
the
view
site
that
we
were.
We
had
power,
and
we
did
this
through
this
open
source
repository
and
tool
called
github
script,
and
it
literally
looks
like
this.
B
B
So
what
you
just
saw
on
the
screen
was
our
featured
actions
page
and
what
I
would
do
is
I
would
just
take
a
label
and
label
the
pr
and
then,
if
it
was
meant
to
be
featured,
it
would
go
directly
to
the
home
page.
If
it
wasn't,
then
it
would
just
basically
just
be
merged
in
and
folks
would
get
a
notification
saying
that
their
their
pr
was
merged.
So
this
is
what
I'm
doing,
and
this
is
again
this
is
part
of
that
automation.
The
area
31
like
I
know,
I'm
going
to
get
prs.
B
I
know
I'm
gonna
have
to
either
merge
them
or
or
or
close
them,
and
at
this
point
the
other
thing
I
didn't
mention
is
that
we
were
leveraging
actions
to
validate
the
actions
that
were
submitted
so
once
you've
opened
the
pr
we
actually
have
validation
that
actually
kicks
off
as
well,
which
is
like
a
whole
another
story
which
I'll
go
way
more
in
detail
at
github
universe.
So
definitely
shout
out
to
github
universe
check
it
out.
It
will
be
actually
be
on
this
youtube.
B
B
So
I
bring
this
up
because
this
was
a
way
for
me
to
automate.
We
were
able
to
take
this
entire
project
to
our.
We
have
50
million
developers
worldwide.
We
didn't
have
that
many
people
submitting
actions,
but
I
was
able
to
accomplish
this
with
two
of
my
other
teammates
and
all
we
had
to
do
was
just
label
issues
or
label,
pull
requests
and
move
forward
through
the
the
process
of
getting
people
their
swag
and
stickers.
B
Shout
out
also
on
youtube.
I
do
a
youtube
series
called
get
action
attraction,
which
is
the
name
of
this.
This
talk
definitely
find
me
over
there.
You
can
find
me
by
go
typing
in
I,
like
robot
or
b
dougie,
both
of
them
work.
There's
a
whole
nother
story
about.
I
like
robot,
but
you'll
have
to
ask
me
later
and
with
that
being
said,
that's
my
information,
and
I
thank
you
very
much
for
listening
to
me.
B
Talk
about
actions,
one
of
the
one
of
my
favorite
things
to
talk
about
so
without
further
ado,
we're
going
to
transition
into
our
first
speaker,
who
I
will
call
io,
io
being
a
nickname.
What's
your
last
name,
thank
you
very
much
for
showing
up
and
providing
this
talk.
Io
is
a
senior
developer
advocate
and
also
a
github
star,
as
well
as
a
media
developer
expert
as
well
for
clattonary,
so
io
makes
definitely
an
expert
in
a
lot
of
different
areas,
but
I'm
looking
forward
to
hearing
what
you're
talking
about
github
action.
C
C
It's
been
a
lot
going
on
here
in
niger
and
we
need
as
more
support
as
we
can
get
and
we're
happy
that
github
stands
with
us
and
the
developers
in
the
country
so
yeah
without
further
ado.
Let's
get
into
the
talk,
so
my
slides
awesome.
So
today
I'm
gonna
be
talking
about
how
to
make
workflow
processes
using
github
actions.
So
byron
did
a
whole
lot
of
talk
about.
Basically,
what
github
actions
is
and
github
actions
was
released
in
november
13th
a
couple
of
years
ago,
so
basically
yeah.
C
Let's
just
get
right
into
the
talk,
so
you
get
to
see
what
all
this
is
about
and
yeah.
Okay,
add
some
animations,
so
I
am
shady
by
amir:
a
senior
developer
and
developer
programs
manager
also
a
github
star
culture,
9,
media
developer
expert,
and
I
love
to
refer
to
myself
as
a
community
evangelist
based
on
I
love
doing
community
work.
I
love
working
with
the
community
at
large
planning
conferences
and
small
meetups
across
different
locations
and
really
a
whole
bunch
of
work
that
has
to
be
working
with
the
community
at
large,
so
yeah.
C
You
can
find
me
on
twitter
and
github.
It's
developer,
that's
developer,
then
eoio
twitter,
github
and
follow
me
there
and
you
can
get
to
see
what
I
took
about.
I
tweeted
a
lot
there
and
I
have
products
and
you
hope
you
could
contribute
to
or
yeah.
So,
let's
move
forward,
I
like
that
so
yeah,
let's
talk
about
workflow
automation,
so
gigabytes
allows
you
to
write
or
set
up
individual
actions
and
combine
them
to
make
a
complete,
workflow
automation.
C
C
This
is
an
action,
and
that
is
one
action
that
does
this
then
another
action
that
does
probably
once
it
has
been
where
progress
has
been
made
automatically
deploys
to
firebase
automatically
deploys
to
azure,
using
using
github
actions
that
were
developed
by
these
companies
who
owns
these
products.
So
we
have
all
of
these
actions
put
together.
So
when
we
automate
processes
like
this,
that's
automatically
called
a
github
actions.
C
Workflow
you're,
basically
automating
a
whole
bunch
of
workflows
that
yeah,
you
can
just
automate,
and
you
don't
need
to
really
concern
yourself
with
manually,
doing
them
yourself
and
it's
exciting
that
github
were
able
to
release
this
kind
of
feature
that
will
make
things
easier
for
people
who
are
moderating
open,
source
projects
and
yeah
working
on
them.
So
workflow,
automation,
literally,
is
this,
so
we
have
the
first
responders
things
we
have
like.
These
are
all
actions
that
so
when
this
happens,
this
happens.
This
happens
all
actions.
C
So
when
you
put
all
this
together,
you
call
them
workflows
because
they
all
run
different
assignments.
They
all
run
different
things.
This
one
also
assigned
this
auto
assignment.
So
once
this
proquest
has
been
made,
automatically
alternately
assigns
the
pro
requests
being
opened
to
you,
or
is
you
been
opened
to
someone
on
the
team?
Who
is
a
maintainer?
That's
an
action
that
can
be
configured
when
issues
are
being
created.
What
should
happen
next
when
requests
have
been
made?
C
What
should
happen
as
if,
if
the
abu
test
is
passed,
what
exactly
should
be
merged
immediately
or
should
someone
be
notified
immediately?
What
should
happen
so
this?
These
are
actions,
and
these
are
workflows
we
can
put
together
and
we
can
automate
a
whole
bunch
of
things
in
our
open
source
projects.
Trust
me,
you
would
want
to
automate
almost
everything
in
your
project.
Just
to
you
know
it's
going
to
relieve
you
so
much
headache
that
comes
with
like
really
large
open
source
product
during
the
hack
super
first
program.
C
C
So
literally,
everything
in
your
open
source
product
can
be
automated
thanks
to
really
github
actions
that
it
has
really
changed
so
much
in
open
source
program
and
how
open
source
maintainers
really
moderate
their
projects,
because
a
whole
bunch
of
issues
like
lot
projects
like
react.js
is
a
very
luck,
project,
vgs
firebase
and
all
these
tools
out
there
that
we
use
constantly
that
are
always
receiving
poor
requests
and
issues.
And
we
cannot
really
look
at
everything.
We
have
like
a
six-man
team
and
like
a
really
huge
open-source
product
used
by.
C
Let's
say
three
million
people
worldwide.
That's
a
lot!
That's
a
lot
of
people
and
a
lot
of
my
developers
who
want
to
create
pull
requests
to
fix
other
things.
So
automating
most
of
the
process
that
has
to
be
progressed
would
be
literally
increased
productivity
and
I'm
happy
that
github
has
this
feature.
So,
let's
move
forward
so
every
event
that
happens
in
your
repo
can
trigger
an
automated
action.
So
every
single
event
you
can
phantom.
You
can
think
about
it's
possible
to
create
and
automatically
trigger
a
gig
of
action.
C
So
when
a
prayer
is
being
pushed,
an
action
can't
come
up
when
an
issue
is
opened,
an
action
can
do
something
when
a
new
branch
is
created,
an
action
can
do
something
when
anything
is
created
at
all,
and
an
action
can
always
do
something.
When
things
automatically
push
to
github
to
github
repo
automatic
deployment
is
possible
and
more
a
whole
bunch
of
things
you
can
put
out
there.
You
can
create
your
own
actions.
You
can
also
use
actions
that
were
created
by
other
people,
but
in
the
community.
C
So
literally
you
can
automate
almost
everything
in
your
open
source
projects.
Isn't
that
amazing?
That's
super
amazing.
I
love
doing
this
and
if
anything
I
could
automate
anything.
I
would
definitely
make
that
so
as
developers.
One
major
thing
is
when
we
have
problems
that
we
have,
for
example,
I'm
not
so
great
with
colors.
C
So
I'm
saying:
hey,
I'm
really
bad
at
picking
colors
when
I'm
working
on
projects
when
I'm
designing
I'm
really
bad
at
colors,
but
then
I
can
just
get
an
image
saying
I
want
to
get
all
the
colors
in
this
image
and
just
get
them
and
use
whichever
one
I
want.
So
I
created
image
hive.
So
all
I
basically
image
have
basically
helps
you
pick
colors
from
images
that
you
have
so
I
just
got
there.
C
C
That
has
to
wait
yeah
automation,
so
you
can
also
consider
github
actions
as
this
reasonable
piece
of
code
that
so,
for
example,
we
can
think
about
like
an
npn
like
like
npm.js
package
manager,
so
where
you
can
create
usable
libraries
and
packages
you
can
push
over
there
and
people
can
really
pull
and
reuse
in
your
project
rather
than
writing
things
from
scratch.
For
example,
let's
talk
about
something
as
simple
as
let's
say,
react
share,
so
react
share.
C
Is
a
package
over
any
pm
that
basically
helps
you
implement,
share
buttons,
facebook
share
twitter
share
and
all
of
the
share
buttons
into
your
project
and
clicking
this
button
sends
it
somewhere.
So
if
you're
writing
all
of
this
from
the
beginning,
you
can
just
use
this
package.
So,
instead
of
you
writing
actions
from
the
beginning,
you
can
just
really
use
to
see
there's
an
action,
github
access
marketplace
where
you
can
visit
and
use
actions
that
has
been
created
by
other
people
and
you
can
modify
it
to.
C
C
C
So
now
github
actions
you
do
yeah,
you
don't
just
like
create
a
wrapper,
then
create
a
file,
actions
or
yaml
or
main
or
yaml,
or
anything
or
yaml.
It
doesn't
work
that
way.
There
is
a
directory
where
the
yaml
folder
for
the
actions
workflow
that's
most
likely,
must
be
present.
So
there
is
a
dot
file
called
dot
github.
Then,
in
that
file
we
have
the
workstool
another
folder.
Then
in
that
works,
the
workflow
folder
is
where
we
have
the
yaml
file
that
has
to
do
with
our
github
actions.
Now
github
actions
will.
C
We
would
not
automatically
find
this
yammer
file
if
it's
outside
this
directory,
because
why
this
is
the
way
it's
been
configured
to.
So
you
don't
configure
your
github
options
automatically
when
you
go
over
to
actions
create
a
new
workflow,
as
we
have
right
here
in
the
slide,
and
once
you
click
this,
it's
going
to
take
you
to
a
preview.
I'm
going
to
show
you
later
on
the
slide
on
how
it
looks
like
then
just
create
this.
This
project-
workflow,
you
don't
have
to
create
this
manually.
C
It's
automatically
been
created,
I'm
going
to
show
you
as
we
move
forward
so
yeah,
it's
not
like
travis.
That's
we
created
javascript
yamaha
in
our
main
project
now
roots
in
that
roots.
For
the
obviously
traffic
store
yamaha.
No,
it
has
to
be
inside
a
protocol.
The
github,
then
the
workflow
folder,
that's
where
we
can
have
our
yammer
file
and
github
actions
can
really
find
the
file
and
run
the
actions
that
we
initiated
in
that
main
file.
C
So
we
can
have
min
yammer.
We
can
help
deploy
the
yamo.
We
can
just
name
it
whatever
we
want,
based
on
the
kind
of
actions
we
are
running
in
that
file,
so
yeah,
so
once
you've
created
a
workflow,
it's
going
to
show
automatically.
So
this
is
a
report
created,
gives
us
a
figure
actions,
so
this
is
a
folder,
then
the
next
we
have
another
dot
file
called
dot.
Github
then,
inside
that
github
we
have
the
works
flow.
Then
we
have
the
file
the
github
actions
file.
C
That's
the
main.yaml
file,
where
we
have
our
github
configurations,
and
this
is
where
we
write
all
of
our
workflow
as
simple
as
that.
So
once
you
commit
this
to
your
main
project
and
it's
gonna,
it's
gonna
be
saved
inside
this
directory.
Then,
once
you
go
under
the
github
actions,
folder
for
that,
this
automatically
is
being
seen,
and
once
you
push
a
pro
request,
whatever
you
write
here,
say,
for
example,
when
a
progress
has
been
opened,
it
should
run
this
tax
automatically.
C
That
basically
happens,
because
why
it
finds
this
file
and
says
hey,
let's,
let's
run
this
tax,
so
there's
also,
as
I
said
before,
there
are
also
actions
that
has
already
been
pre-created
by
the
communities
that
can
be
reused,
so
the
actions
that
has
to
do
with
go
that
has
to
be
attacked.
So
we
set
up
java,
sdk
and
all
of
these
actions
that
we
can
all
see
here,
yeah
all
different
actions
that
we
can
initiate
any
time
I'm
working
on
a
project.
C
So
again,
yes,
so
this
is
a
github
actions
marketplace,
so
we
have
the
apps.
We
have
all
of
these
categories
where
we
have
different
kinds
of
tools
we
can
integrate
into
our
projects,
but
there
is
a
path
for
the
github
actions
where
we
have
all
of
these
github
actions.
Extension
yeah
give
up
actions.
Rather,
so
we
have
the
deploy
attacks
for
amazon
aws.
C
C
You
want
click
on
the
repo.
You
can
always
click
on
the
automatically
see
what's
present
and
reach
through
the
code.
Basically,
you
can
just
like
click
on
readme
click
on
actions
or
yaml.
You
can
click
on
the
github
workflows.
You
can
click
on
src
and
look
what's
inside
and
before
you
basically
literally
use
it
for
anything,
it's
all
open.
So
so
this
is
simple
github
actions
and
basically
what
this
does
is
it's
going
to
be
verifying
pull
requests.
So
this
is
the
name
of
the
github
button,
so
this
is
a
prerequisite.
C
Yammer
file
that
remember
is
going
to
be
in
our
directory.
Github
workflow
directory,
so
gonna
verify
all
progress.
Then,
basically,
it's
gonna
after
the
final
process,
it's
to
get
a
list
of
all
pull
requests
that
we
have
opened
on
whatever
products
for
our
repo.
We
are
working
on
every
pro
request.
I'm
gonna
send
everything.
So
it's
gonna
slide.
It's
gonna
get
a
slack
token
and
basically
send
all
of
that
requests
that
open
to
a
slack
channel.
That's
literally
on
really
simple
what
this
github
actions
does
so
constantly
on
a
kind
of
basis.
C
He
gets
every
pull
request.
That's
opened
on
our
regular
hub
report
and
sends
all
of
those
open
pull
requests
to
a
slash
channel
where
we
we're
going
to
configure
our
actions
on
the
slack
channel,
and
so
yes,
let's
talk
about
appearance.
So
github
is
super
general.
How
github
actions
has
been
commercialized
and
so
for
say
for
public
repositories,
it's
free
to
use
github
actions.
So
you
are
free,
two
thousand
so
yeah,
two
thousand
million
minutes
per
month.
On
the
pro
version.
We
have
three
thousand
minutes
team
version.
C
We
have
three
thousand
and
enterprise,
we
have
fifty
thousand
minutes
per
month.
Then
they
also
have
runners,
that's
linux
or
another
windows
on
my
cores
and
the
circle
set
which
is
free.
Then
these
are
all
paid
and
the
link
that's
version
of
so
cars.
Two
cars
of
seven
gigabytes
is
0.008
us
dollars.
C
So
github
actions
is
available
for
github
free
tier
automatically,
so
you
can
start
using
github
actions
starting
right
now.
Therefore,
github
pro
is
available.
Github
team
github
enterprise-
your
passions
are
available
for
across
everyone
who
uses
basically
github.
You
have
access
to
github
actions,
you
can
use
already
made
github
actions
or
you
can
also
write
your
own
github
options.
C
So
a
log,
as
we
all
know,
is
how
we
see
the
processes
being
run
under
the
hood.
If
anything
goes
wrong,
we
can
always
go
to
the
blog
and
find
out,
basically
where
processes
are
also
for
github
actions.
Also,
there's
always
a
log
here.
So
this
is
a
simple
screenshot
of
this.
What
a
log
looks
like
so
here
we
have.
The
last
run,
basically
what's
wrong
last,
what
did
was
it
successful?
Did
it
fail?
We
have
this,
then
we
also
have
this.
C
So
when
you
also
when
you
automatically,
for
example,
say
push
the
pro
request,
this
doesn't
say
tick.
This
basically
shows
a
round
bar
saying
it's
going
to
show
yellow
if
it's
still
processing
is
trying
to
load
up
trying
to
run
the
github
actions.
So
this
also
is
our
workflow.
Basically,
the
workflow
and
what
basically,
what
jobs
are
being
run,
so
this
is
obviously
so.
This
is
just
the
workflow
then
here
it's
just
the
jobs
have
been
run.
Then
right
here
is
the
steps
that
are
being
run
so
yeah.
C
You
can
so
click
on
this
button.
It
helps
you
download
the
log
and
basically
how
long
it
takes
each
job
to
run
it.
So
it
took
setting
up
the
job.
Talks
took
two
seconds,
so
this
also
took
a
second
so
yeah.
Basically
it's
as
simple
as
that,
this
basically
log.
We
all
know
how
to
read
logs
as
long
as
you're
a
developer.
You
should
know
how
to
read
a
log
and
how
all
of
this
works.
C
So
then,
this,
basically
all
the
log
you
can
scroll
through
and
see
all
of
these
things.
So
the
next
thing
you
can
also
expand
the
jobs.
So
once
you,
for
example,
once
you
install
so
remember
what
I
said
before
about
the
stick
pass,
so
is
when
the
actions
automatically
successfully
run,
then
it
shows
the
check.
If
not,
it's
going
to
show
you
something
is
failing
so
you're
going
to
say
the
red,
then
some
passed
so
some
failed.
C
So,
as
you
can
see,
also
go
into
our
log,
we
can
see
that
three
of
our
jobs
pass,
but
one
one
field
so
clicking
this
button
right
here
expands
the
job.
Then
we
can
see
the
description
of
how
exactly
and
what
exactly
failed.
While
this
job
was
running,
so
we
can
know
how
exactly
to
fix
this
so
moving
forward.
We
also
have
the
search
log
so
there's
some
times
where
your
jobs
are
failing
at
the
same
time,
so
you
might
know
exactly
what
are
you
looking
for?
C
So
you
can
also
go
straight
to
the
search
log
under
the
github
actions,
log
and
search
for
it.
What
the
what
exactly
you're
looking
for
and
find
the
error
and
basically
just
read
it
out
and
fix
the
solution,
there's
always
a
search
bar
there.
You
can
search
the
logs
on
so
there's.
Also,
this
amazing
subtle
badge
status,
badge
of
honor
that
I
just
want
to
call
it
so
so
I
got
a
status
badge
of
honor
so
for
the
gig
of
action.
C
So
if
you
give
a
chance
of
spill,
you
can
also
have
this
on
your
website
where
you
can
save
this
pass.
So
if
you,
okay,
have
actions
is
passed.
You
can
also
have
this
on
your
readme
file,
so
everyone
can
see
that
you'll
give
back,
give
her
actions
as
passing
at
this
time
and
if
it
fails,
you
can
also
see
that
it's
failing
so
yeah.
You
can
also
add
this
to
your
project,
so
some
resources,
you
might
need
so
the
repo
I
show
you
where
I
have
the
simple
gear
boxes
running.
C
If
you
go
to
github.com
for
starts
developer
io
for
such
github
hyphen
africa,
hyphen
actions,
you
can
get
to
see
that
repository,
then
events,
no
more
banking,
have
actually
just
physically
hub.com
for
such
features
for
us
as
actions
and
that's
the
official
website
for
github
actions
so
yeah.
Thank
you
so
much
you
can
so
I'm
up
with
questions,
and
you
can
follow
me
on
twitter
and
github
as
developer.
B
B
Excellent
yeah,
thank
you
very
much,
so
I
think
we're
gonna
transition
to
our
next
speaker,
and
our
next
speaker
is
martens.
Martin's,
actually
is
a
corporate
sales
representative
here
in
san
francisco.
Actually
here
with
me
and
passionate
about
technology
and
loves
helping
engineers
as
well
so
martin,
please
take
it
away
all
right.
Thank
you.
Thank.
D
You
brian,
like
brian,
mentioned,
I'm
a
corporate
account
executive
here
in
san
francisco
bay
area
and
I'm
also
in
nigerian.
I
recently
moved
and
moved
to
the
u.s
about
five
years
ago
and
I
go
back
and
forth
all
the
time
because
I
still
have
family
over
there.
So
so
I'm
really
excited
to
talk
to
you
guys
talk
to
africans
all
around
the
world,
specifically
in
africa
and
in
nigeria,
and
I
I
would
also
like
to
lend
my
voice
to
the
ongoing
protests
in
nigeria.
D
So
I
know
I'm
wearing
this,
the
exact
exact
same
sweater
I
was.
I
was
trying
to
trick
you
guys
to
make
you
believe.
I'm
always
hearing
this
all
the
time,
but
I
I
I
decided
to
just
wear
the
same
sweater
and
put
the
same
picture
here,
but
I
don't
sleep
in
the
sweater
bar.
I
love
this
water
very
much
so
yeah,
so
I
just
turned
this
around.
D
D
So
if
you,
if
you,
if
you're
looking
to
get
your
startups
off
the
ground,
definitely
check
out
their
website
for
their
startup
programs
and
and
and
sign
up
for
it
and
with
github
actions
plugged
in
you
can
really
get
your
your
business
off
the
ground
or
get
your
your
startup
off
the
ground
and
I'll
talk
to
I'll.
Also
talk
through
how
you
would
be
able
to
get
our
flagship
gear
of
enterprise
cloud
for
free
for
your
startups.
D
D
There
are
over
5000
applications
that
have
already
been
built
that
you
can
use
for
your
projects
and,
like
he
mentioned,
make
sure
you
you
look
for
very
high
star
ratings
for
the
applications
and
also
make
sure
that
they
are
verified
by
github,
and
you
can
always
go
through
to
their
repositories
to
figure
out
the
code
that
builds
the
app
and
you
know
just
getting
their
testings
out
and
you
know
have
fun
so
beyond
github
actions.
I
also
like
to
talk
through
github
mobile
experience.
D
We
this
this
was
launched.
We
acquired
some
companies
to
have
this
launched
last
year
and
and
it
became
generally
available
this
year
and
the
the
reason
we're
building
this
out
is
to
make
sure
that
you
can.
You
know,
access
your
github
pull
request
on
the
go.
We
understand
from
some
analysis
that
the
mobile
the
the
mobile
platform
mob
platform
is
very
highly
penetrated
in
in
africa.
D
D
So
while
you
are
going
going
going
back
home
after
after
a
long
long
day
of
work,
you
can
you
can
still
review
pull
requests
and
quickly
access
your
issues
and
keep
tabs
on
on
the
projects
that
you
that
you
have
going
on,
and
I
actually
tried
to
confirm
that
github
mobile
is
currently
available
in
africa.
I
I
talked
to
a
developer
in
nigeria
yesterday
and
he
was
he
confirmed
that
girafmobo
is
currently
working
in
nigeria.
D
D
I
would
talk
about
how
all
of
these
tools
that
we're
building
you
can
get
it
within
the
github
free
tier,
so
you
can
use
github
actions
on
the
on
the
free
tier
and
you
can
use
the
gita
mobile
app
with
the
free
tier.
So
around
the
background
for
this
is
we
wanted
to
really
reduce
the
barrier
for
all
developers
all
around
the
world,
including
africa,
so
that
they
can
easily
adopt
github
and
get
started
with
their
with
their
projects?
D
So
we
we
came
up
with
the
github
free
tier
plan
and
it
allows
you
to
get
you
know.
Github
actions
get
all
the
the
basics
of
github
of
the
gita
platform,
and
you
can.
You
can
start
from
there
and
collaborate
with
your
friend.
There
is
no
limit
to
the
number
of
collaborators
you
can
have
on
this
plan
and
you
can
you
can
get
it
today.
D
It's
it's
free
for
all
of
your
history,
for
teams
and
it's
free,
for
there
is
no
limits
to
the
number
of
collaborators
you
can
have
on
the
get
up
free
plan
so
and-
and
lastly,
I
want
to
talk
through
the
the
github
enterprise
cloud
for
startups
program.
So
we
have
we
as
you.
As
you
know,
we
we
are
well
supported
by
microsoft
and
there
is
a
platform
there.
There
is
a
program
to
get
you
a
flagship,
github
enterprise
product
for
free.
As
far
as
you
you,
your
startup
and
you're.
D
Looking
to
you
know,
be
more
secure,
have
a
better
product
overall
to
use
for
your
company,
and
you
can
sign
up
for
the
github
for
for
the
microsoft
startup
program
and
you'll
get
github
enterprise
cloud,
which
is
used
by
all
sorts
of
organizations
all
around
the
world
to
develop
collaborate
and
and
ship
great
products
that
you
use.
So
you
can
sign
up
for
this
program
on
on
the
microsoft
page.
I
would
I
will
send
some
links
after
now.
D
In
the
chat
for
you
to
sign
up
for
this
and
the
the
cool
thing
is
with
this
program,
you
you
get
all
of
the
things
on
on
the
enterprise
platform.
This
is
just
our
landing
page
and
all
of
the
best
enterprises
in
the
world
use
this
for
for
the
organizations
to
collaborate
and
to
get
talent-
and
you
know,
get
the
best
of
the
platform
totally.
So
this
is
something
you
can
get
with
github
enterprise
cloud
and
it's
it's
powered
by
the
microsoft
4
startups
program.
D
So
so
beyond
beyond
this,
I
also
like
to
point
point
out
that
this
this
program
is
for
free.
It
is
available
all
around
the
world
it's
available
for
every
african
country,
so
you
just
need
to
sign
up
for
it,
and
you
can
also
contact
me.
If
you
need
more
information,
you
can
contact
me
on
linkedin,
I'm
happy
to
help
out
with
this
with
this
product.
Another
another
way
to
think
about
how
to
use
this.
D
Is
that
if
you,
if
you,
if
you're
working
for
a
company
or
you're
working
for
a
startup-
and
you
guys
are
looking
to
you're
looking
to
introduce
the
the
the
gita
platform
you're
looking
to
bring
it
up
to
work,
this
is
an
easy
way.
A
cost-effective
way
there
is.
There
is
no
cost
to
get
started
with
with
the
platform
with
our
flagship
platform.
D
So
that's
one
more
thing
to
to
think
about
and
that's
about
it,
so
all
in
all
we're
building,
github
actions,
we're
building
github
mobile,
we're
giving
github
for
free
and
if
that
doesn't
meet
your
basic
needs,
you
can
then
sign
up
for
the
for
the
startups
program,
and
that
would
get
you
the
best
of
the
platform
for
free.
So
that's
all.
D
I
have
to
say
keep
in
mind
that
most
of
the
cloud
providers
all
have
all
have
a
startups
program,
so
you
can
all
you
can
always
sign
up
for
all
of
it
all
of
all
of
the
platforms
and
then
plug
it
all
together
on
on
the
getup
platform,
and
you
know
make
make
make
the
your
best
do
your
best
work.
So
with
that
I'll
say.
Thank
you
for
listening
I'll,
pass
it
back
to
brian,
so
he
can.
B
Keep
us
going
here.
Yes,
thanks,
martin,
so
appreciate
the
the
talk
you've
given
and
yeah
we're
gonna
move
right
along
to
our
next
speaker,
who
I'm
super
honored
to
have
here
as
a
also
a
recent
star.
Ruth
is
not
just
a
recent
star,
but
also
self-taught
python,
programmer
she's,
also
a
contributor
to
gnome
project
and
as
well
as
been
involved
with
she
coach
africa.
I
had
an
opportunity
to
meet
ruth
last
week.
At
an
event.
E
E
Okay,
back
to
me,
I'm
ruth
kega
from
nigeria,
I'm
a
python
developer,
a
technical
writer
and
an
open
source
contributor,
and
one
very
good
thing
about
me-
is
I
love
eating
cakes,
a
lot
and
almost
every
time.
So
today
I'm
going
to
be
talking
about
how
to
get
involved
as
a
beginner
in
open
source.
This
this
topic
actually
resonates
with
me
because
I
started
off
with
open
source
as
a
beginner.
E
E
E
Now.
First
of
all,
I
want
to
like
start
with
debunking
some
beliefs
with
especially
amongst
beginners,
with
contributing
to
open
source,
like
most
of
most
of
the
reasons
why
they
shy
away
so
first
off,
is
they
always
like?
Have
you
always
have
this
notion
that
contributing
to
open
source
is
about
code?
You
just
put
contributions.
You
can
make
it
open
source,
but
that's
not
actually
that
that's
not
actually
true,
because
there
are
other
means
and
very
vital
ways.
E
You
can
contribute
to
an
open
source
project
without
having
to
write
code,
so
contributing
to
open
source
is
not
just
about
code
contributions
yeah.
So
the
next
thing
I'll
talk
about
is
that
your
level
of
skill
set
no
matter
what
level
you
are,
whether
you're
a
beginner,
it
could
be
intermediate
developer
or
a
senior
developer.
Your
level
of
skill
set
and
open
source
contributions
is
welcome.
Like
will
always
say,
quality
over
quantity
welcome,
so
you
should
focus
on
the
quality
of
bringing
to
that
project
when
contributing
to
an
open
source
project.
E
Now.
Also,
there's
the
there's
a
belief
that
or
contributing
to
open
source
is
just
free
work
and
there
are
no
benefits
to
you
as
a
person,
but
that's
not
actually
true.
That's
not
that's
not
true
entirely,
because
there
are
amazing
benefits
with
contributing
to
open
source.
You
get
to
improve
your
skill,
set
you
get
to
work
with
you
get
people's
skills
you
they
are
like
paid
opportunities
with
working
open
source
in
open
source
projects.
E
So
another
point:
I
would
like
to
point
out
that
people,
especially
designers
I
want
to
let
you
know
that
designers
can
also
contribute
to
open
source,
just
like
I
pointed
earlier
that
contributing
to
open
source
is
not
just
about
code,
but
designers
can
also
contribute
to
open
source,
and
one
great
way
to
contribute
is
the
open
source
design
team,
which
aerial
fox
is
actively
handling.
So
I'm
going
to
talk
about
that
as
we
move
forward.
E
E
So
we
are
in
the
month
of
october,
and
this
is
the
month
of
october
first
so
october.
1St
is
an
annual
program
where,
in
the
month
of
october,
it's
a
month-long
contribution,
open
source
contribution
where
you
are
required
to
get
four
pull
requests
matched
and
you
get
a
reward
of
a
t-shirt
or
you
get
to
plant
a
tree.
So
one
way
you
can
get
involved
in
open
source
is
you
can
utilize,
this
month
of
october,
first
to
start
contributing
to
open
source?
E
Because
there
are
a
whole
lot
of
projects
that
are
on
github
that
are
engaging
in
the
oktoberfest
program,
so
you
just
I
I'm
going
to
share
the
slides
later,
so
you
just
click
on
go
to
oktoberfest.com
and
you
register
and
start
looking
for
projects
on
github
and
they
are
very
useful
resources
and
videos
that
would
help
you
get
started
yeah.
So
next
thing
is
finding
open
issues
on
github
to
tackle
on.
E
So,
if
you
use
the
search
query,
you
can
use
the
search
query
on
github
to
find
open
issues
you
can
even
github.
Has
this
feature
where
you
get
to
search
by
label
you
get
to
search
for
good
first
issues
and
first
time
are
only
issues.
So
once
you
put
that
once
you
put
that
up
a
search
comes
up
and
you
see
a
good
number
of
repositories
with
so
many
good
open
issues
that
you
could
start
up
on
so
another
another
way
is
writing
or
contributing
to
project
documentation.
E
Like
I
mentioned
earlier,
it's
not
just
about
code
contributions
yeah,
so
you
can.
You
can
contribute
to
the
project
documentation.
You
can
help
improve
the
dogs.
You
can
help.
You
can
help
with
fixing
up
typosing,
no
matter,
no
matter
how
small
the
contribution
is.
It
is
valued
at
your
giving
quality
to
that
project
right.
So
next
up,
you
can't
help
with
planning
and
organizing
events.
So
people
saying
like
this
is
not
something.
E
This
is
a
valid
contribution
in
open
source
in
open
source
projects,
because
for
projects
you
you
need
to
actually
for
you
to
have
for
you
to
have
good
quality.
You
need
to
be
able
to
organize
the
project
well
or
be
the
software,
so
you
can
help
as
a
contributor
in
planning
and
organizing
events
so
good
enough.
There
are
so
many
virtual
events
that
need
hands-on
to
plan
because,
but
you
know,
virtual
events
have
you
need
more
like
more
planning
for
virtual
events,
so
there
are
so
many
better
events.
E
You
could
help
organize
so
many
open
source
virtual
events
so
another
way
and
that
valid
way
to
like
get
involved
in
contributing
to
open
source,
is
answering
questions
and
reviewing
code
and
helping
out
in
the
community.
So,
most
of
the
time
when
people
hop
into
communities,
it's
usually
very
hard
for
them
to
find
their
way
around,
and
for
you
who
has
been
in
the
community,
you
can
help
them
out
showing
them
their
way
around
answering
questions
you
can
review
code
and
code
pull
requests.
You
can
do
a
whole
lot
in
the
community.
E
So
another
point
is
supporting
an
open
source
project
or
even
open
sourcing.
Your
project.
So
with
the
github
feature
sponsoring
feature,
you
could
support
an
open
source
project
or
you
can
open
source.
I
see
some
people
observe
their
portfolio
or
their
projects.
They
have
view
just
to
help.
Others
in
the
community,
because
mainly
open
source,
is
about
the
community,
so
I
have
accumulated
some
useful
resources
and
that
would
help
you
get
started
with
contributing
to
open
source
as
a
beginner
and
this
resources.
For
me
it
has.
E
It
has
really
been
helpful
because,
initially,
when
I
got
when
I,
when
I
started
with
contributing
to
open
source,
it
was
really
very
helpful
to
me,
like
a
first
timers,
only
it's
like
a
site
where
you
can
find
a
good
number
of
open
source
projects
that
you
can
contribute
to.
As
a
beginner
like
a
curated
list
of
open
source
projects,
you
can
use
the
github
explorer
explore
kind
of
github
explore
to
search
for
projects.
As
for
your
staff,
let's
say:
you're
a
python
developer
or
a
a
javascript
person.
E
You
can
search
your
project
as
per
stop
topics,
the
ones
that
are
trending.
You
can
engage
in
open
source
and
contribute
to
open
source
friday.
There's
always,
I
think,
there's
always
like
an
event.
Every
friday
you
can
check
out
code
triad,
24,
pull
requests
up
for
grabs
a
whole
lot
and
also
first
contributions.
E
If
you
are
very
especially
for
beginners
most
of
the
time,
I
think
one
frustrating
thing
is
understanding
how
to
do
the
github
workflow
contributing
pushing
your
code
committing
so
for
first
contributions.
First,
contributions
actually
has
it's.
It's
a
project
to
help
beginners
contribute
to
open
source,
to
understand
that
github
and
get
workflow.
So
you
might
want
to
try
that.
I
think
that
was
the
first.
That
was
the
first
contribution
I
made
just
adding
my
name
to
the
repository.
E
It's
really
very
cool,
and
I
I
got
I
got
to
post
on
twitter
and
I
was
like
I
made
my
first
contribution
today
and
I
was
getting
so
many
congratulations
that
was
so
so
nice
and
good,
so
also
open
source
design
for
designers.
You
could
get
involved
here,
check
out
the
website
and
check
out
the
repositories
on
github
to
get
you
involved
with
open
source
design.
E
So
I
want
to
end
of
this
talk
with
saying
you
should
make
yourself
that
software
you
use
and
the
world
at
large
better
by
contributing
to
open
source
today.
Thank
you
for
listening
and
you
can
connect
to
me,
via
my
social
media,
handles
github
at
this
link
and
on
twitter
at
kedarroots.
Thank
you
for
listening.
B
Thank
you
ruth.
I
appreciate
that
and
folks
that
was
really
insightful
and
I
I'm
I
love
contributing
open
source.
I
love
folks
sharing
their
details
and
sharing
how
to
also
get
you
involved
in
doing
open
source.
So
if
you're
interested
definitely
hang
around,
follow
the
meetup
follow
this
youtube
channel
as
well,
but
we
do
have.
We
have
more
talks,
we're
not
ending.
So
our
next
speaker
is
shedrack.
Not
only
is
shadrach
doing.
This
talk
he's
also
doing
two
other
talks
today,
because
I
know
you
yeah.
B
F
Okay,
okay,
perfect
hi,
everybody,
my
name
is
akintayo,
and
today
I'm
going
to
talking
about
documenting
your
open
source
project
on
this
test
and
I'm
giving
this
talk.
Anyways,
I'm
very
excited
about
it.
So
I'm
about
me,
I'm
a
developer
advocate
for
class
running
foundation
and
we
have
open
source
platforms
for
also
an
open
source
community
media
with
open
source
africa
coming
to
africa.
So
let's
just
what
are
we
going
to
discuss
today?
We're
going
to
talk
about?
F
What's
the
documentation,
just
the
basics
of
everything,
importance
of
documentation,
oh
open
source
tips
for
writing,
effective
dots
traits
of
successful
oss
dogs,
then
tools
to
write
a
good,
open
source
documentation.
Then
they'll
give
a
simple
possible
structure
for
your
orchestra's
documentation.
Then
finally,
you're
just
going
to
see
quick
quickly,
just
see
some
examples
of
good
open
source
documentation.
So
before
we
begin,
this
is
something
I
always
encourage
people
to
do.
Read
the
docs.
F
Read
them
they're,
very,
very
important
for
you
and
they're,
very,
very
important
for
for
you
to
understand
the
software.
So
the
maintainers
know
why
the
right
dog.
So,
instead
of
asking
questions
and
stuff
about,
do
you
know
that
you
could
actually
read
the
docs
and
get
your
questions
answered.
So
please
read
the
talks.
Thank
you.
So,
let's
get
started.
F
So
what
is
documentation
so
I
mean
we're
looking
at
the
communication
physically
in
programming
in
open
source,
so
conversational
programming
design
is
basically
any
text
illustration
or
media
that
gives
detailed
information
about
the
particular
software.
So
this
information
could
be
anything
it
could
be
from
how
to
use
the
software
how
the
software
operates.
It
could
be
a
roadmap
for
how
the
software
should
evolve.
So,
basically,
so
information
is
basically
anything
written
text
or
media
that
basically
tells
us
about.
F
If
you
give
us
information
about
a
particular
software,
so
forms
of
documentation,
I
mean
a
lot
of
us
really
just
think
documentation
stops.
Actually
in
text
I
mean
just
seeing
the
readme
dot
md
file
and
that's
documentation
just
seeing
you
hosted
version
of
the
reading
the
md
file,
so
documentation
is
way
more
than
that
right.
So
we
have
written
text
like
like
the
most
popular
form
of
documentation
is
with
me.
Then
we
also
have
release
notes.
F
So
this
note
contains,
like
the
release,
candidates
and
every
single
thing
about
that
particular
release,
so
that
could
also
serve
as
the
documentation
for
that
particular
software.
We
have
illustrations
so
illustration
coding
for
an
update.
An
open
source
project
would
include
the
roadmap,
how
the
the
maintainers
envision
the
software
to
grow,
how
the
the
what
the
maintainers
are
planning
for
the
software
in
the
future
time
also
illustrations
previously
includes
graph,
so
basically
on
graph
of
on
maybe
a
benchmark
test
or
et
cetera
for
your
facilitator
software.
F
So
if
you
look
at
testing
javascript
users,
you
will
see
given
different
graphs,
comparing
videos,
javascript
beauty,
bluetooth
and
your
speed,
etc.
So
we
also
have
videos
I
mean
you
can
have
various
forms
of
tutorial
videos
confronted
in
ambassador
class
software,
so
that
can
also
serve
as
documentation.
This
is
audio,
it's
not
so
popular,
but
we
also
have
audio
forms
of
documentation.
Then
comments
in
code
which
specially
this
is
pretty
popular
among
developers.
F
So
when
we
put
certain
comments
about
this
particular
code
block
that
will
also
serve
as
documentation
for
the
particular
structure
or
the
particular
code,
so
importance
of
documentation
in
oss.
So
I
mean
the
open
source
is
like
a
very,
very
open
source
hostel.
So
it's
like
quite
popular.
I
mean
this.
A
lot
of
people
are
using
it.
A
lot
of
people
are
actually
doing
open
source.
So
I
mean
what
what
is
the
importance
of
documenting
your
open
source
project?
F
I
mean
this
number
first,
the
first
thing
I
would
say
to
help
educate
people
and
keep
track
on
all
of
the
software.
So
the
reason
why
people
would
want
to
use
your
open
source
software
is
because
they
know
how
to
use
it,
so
that
is
where
documentation
comes
in.
You
have
to
educate
people
on
how
to
use
your
personal
class
software
and
also,
like
I
said,
with
these
notes,
we
did
not
cancel
the
pro
a
a
form
of
tracking
all
of
aspects
of
the
software
like
setting
development
in
the
software.
F
So
that's
one
of
the
importance
of
documentation
in
open
source.
It
improves
the
quality
of
the
software.
I
mean
every
good
software
has
great
documentation,
no
matter
how
good
a
particular
software
is.
A
particular
open
source
project
is
if
the
documentation
is
not
great,
a
lot
of
people
will
use
it
it
could,
it
could
be,
it
could
be.
It
could
do
many
things.
It
could
compress
an
image
from
it.
F
So
if
you
click
on
it,
every
single
one
of
them
most
of
them
comes
with
release
notes.
So
these
notes
basically
tell
us
what
updates
were
made.
What
updates
were
shown?
What
particular
features
of
the
pattern
plus
open
source
restrictions
where
children
are
removed,
so
it
informs
people
on
what
aspect
of
the
software
is
currently
being
worked
on
the
maintainers
owned
by
the
maintenance
of
the
oss
project.
Like
I
said
with
the
roadmaps,
the
roadmaps
are
very
important
because
people
want
to
know
what's
next
like
after
we
have
this
particular
feature.
F
What's
next
for
us,
so
it's
good
for
you
as
the
oss
maintainer,
to
have
a
good
map
for
your
particular
project.
It
doesn't
necessarily
have
to
be
something
big.
It
doesn't
necessarily
have
to
be
something
large.
It's
just
be
what
you
think
what
you
features
that
you
think
should
come
in
for
the
particular
software,
so
word
maps
are
always
really
good
to
have
so
tips
for
writing
effective,
open
source
documentation.
F
So
I
mean
I
have
an
open
source
software
now,
so
how
do
I
write
a
documentation
that
increases
the
quality
of
my
software,
of
increasing
the
quality
of
the
project?
So
now
the
first
thing
you
would
do
like
I
mean
this
is
not
even
just
in
documentation,
you're
writing
in
general.
The
first
thing
you
do
is
to
define
a
style
guide
guide
for
your
documentation
and
enforce
it.
F
I
would
say
you
should
be
strict
with
your
style
guide,
because
sagar
gives
you
a
vision
for
how
you
envision
your
open
source
documentation
to
look
like
so
defining
a
style
guide
for
your
documentation
and
enforcement
is
very
important.
You
can
find
various
open
source
documentation
or
documentation
style
guides
on
the
internet.
You
can
also
check
right.
The
talks
right
dogs
have
very
great
side
guides
for
you
to
follow
so
pick
up
your
markup
style
and
stick
with
it.
F
I
mean
it's
very,
very
important
for
you
to
pick
your
paper
to
play
markov
style
and
enforce
this
also
documentation.
Consistency
would
make
people
feel
comfortable
that
okay,
this
particular
person
really
knows
what
he
or
she
or
they
are.
You
are
doing
so
focus
on
using
an
active
voice.
Very
important.
I
mean
people
using
your
software.
F
People
using
your
open
source
project
are
humans
are
humans
right,
so
you
need
to
be
our
means
to
maybe
create
a
conversational
tone
so
use
you
use
us
use
on
passive
voices
where
you
feel,
like
I
mean
you're.
Just
talking
to
the
person
make
it
a
collaborative
effort,
be
so
is
very
important
when
you're
writing
on
your
open
source
documentation
so
make
use
of
simple
and
short
sentences.
This
will
encourage
efficient
communication.
So
a
lot
of
people
do
not
want
to
read
a
long
sentence.
Just
look.
F
Try
your
best
to
make
use
of
simple
sentences
and
instead
of
writing
two
lines.
Look
for
a
way
to
write
a
single
line.
This
is
very
important
because
people
get
bored,
so
the
attention
span
of
people
gets
really
short
as
they
grow
older.
So
you
would
try
your
best
to
make
sure
that
sentences
are
simple
and
short.
I
get
bored
myself
when
I
write
when
I
read
long
documentation.
F
F
I
know
I
cannot
be
looking
for
where
authentication
is
just
put
a
sidebar
that
choose
every
single
thing
from
from
how
your
documentation
is,
but
people
need
to
know
where
things
are
so
that
in
introduces
development
time
for
them
whenever
they
are
using
your
on
source
documentation
and
when
it's
open
source
design.
People
need
to
know
where
particular
styling
so
for
open
source
people
that
are
for
designers,
designers
that
do
open
source
to
decrease
tigers
for
particular
open
source
software.
F
So
if
these
things
are
documented
properly,
people
spend
less
time
on
documentation
and
more
time
using
software
using
your
personal
software,
that's
also
very
important
include
code
sample
code,
an
example
I
mean.
If
you
are
building
a
software,
you
need
to
show
people
that
this
is
what
you
can
do.
This
is
an
example
of
how
to
use
it
like,
like
I
said,
even
though
I
will
give
an
example,
a
username
for
people
to
read
the
documentation.
Most
people
do
not
read
documentation.
Sometimes
I
might
try
myself
because
you
have
not
read
the
documentation.
F
I
don't
go
straight
to
the
code,
samples
that
are
available
or
the
examples
and
just
read
it
and
see.
Oh,
this
is
how
I'm
supposed
to
use
this
thing.
I've
not
read
the
complete
documentation
so
for
we
have
to
make
provision
for
those
people
that
those
people
like
me
and
many
other
people
that
do
not
read
the
documentation,
and
so
you
can
just
say
these
code,
samples
and
examples
that
are
available
for
us
to
use
immediately.
So
we
use
visual
devices
to
represent
information.
F
So
most
of
the
time
like
I
said,
the
attention
span
of
people
go
very
low
as
they
grow
older.
So
you
need
to
be
able
to
be
accommodative
for
every
single
type
of
person.
So
a
lot
of
people
prefer
to
see
visual
things
and
to
actually
read
sentences.
So
one
thing
you
can
do
is
add
locations
tables
graphs
of
certain
concepts.
In
your
documentation,
so
that
you
can
be
more
inclusive
for
every
type
of
testing
and
also
people
that
are
finding
it
very
difficult
to
read
stuff,
so
I
mean
you
need
to
be.
F
You
need
to
be
inclusive
in
when
you're
writing
a
particular
documentation
that
I
expect
a
lot
of
people
to
use.
They
expect
people
in
general
to
use.
So
one
of
the
important
thing
is
they'll
check
your
documentation
to
avoid
errors.
There
are
a
lot
of
documentation.
I've
seen
still
failing
errors
that
has
made
me
confused,
so
you
need
to
you,
do
not
want
your
users,
people
that
will
use
your
open
source
project
to
be
confused
on
how
to
use
the
particular
thing
or
confusing
building
using
your
your
open
source
software.
F
So
you
should
always
check
your
spell
check
your
documentation
to
avoid
errors.
This
is
very,
very
important,
provide
contribution
guidelines,
so
I
mean,
while
we
are
talking
while
we
are
specifically
talking
about
open
source
documentation.
Another
very
important
thing
to
do
is
to
provide
on
contribution
guidelines,
because
if
you
provide
a
guideline
for
how
people
should
contribute
to
your
project,
you
would
definitely
see
less
error
on
contributing,
so
providing
guidelines
is
also
a
very
good
important
example
of
writing.
F
Effective
oss
documentation,
so
the
traits
of
on
successful
oss
dog.
So
this
is
like
from
my
experience
of
what
I've
seen
in
open
source
documentation.
The
very
first
thing
is
easy
access
to
information
regarding
core
aspects
of
the
software.
Like
I
said
most
of
these
well
built
out,
documentation
have
a
sidebar
of
things
that
show
where
you
can
find
certain
information
about
your
apartment
as
a
particular
software.
So
well,
so
one
other
thing
is
well
a
well
structured.
F
So
if
your
documentation
is
well
structured,
it
will
allow
people
to
have
access
to
information.
Like
I
said
very
fast,
so
you
don't
want
people
to
spend
more
time
within
documentation.
We
need
to
make
people
spend
less
time
during
documentation
and
more
time.
Building
with
our
software
very
important
now
helps
new
developers,
listen
to
the
oss,
to
use
your
poison
soft
to
your
opponent's
software
quickly.
F
This
is
very
important
with,
like
I
said,
we
do
not
need
people
to
spend
more
time
doing
documentation,
we
need
more
people,
people
to
let
them
grab
certain
concepts
about
open
source
to
it
and
using
our
software
immediately.
So
when
else
we
have
a
very
great
open
source,
though
people
are
people
get
information
they
need
to
get
and
they
can
easily
grab
whatever
they
need
and
go
and
start
building
so
simplified
usage
of
the
open
source
documentation.
F
F
Users
of
your
open
source
documentation
need
support.
One
thing
is
every
good.
Open
source
documentation
reduces
the
amount
of
time
people
spend
looking
for
support.
People
spend
checking
om
stack
overflow,
so
when
people
have
access
to
great
information
on
your
open
source
documentation
whenever
they
have
issues,
they
check,
you
see.
Okay,
the
documentation
already
explained
how
to
use
this
particular
thing.
Then
there
would
no
need
to
go
to
other
platforms
start
searching
for
open
source
for
for
solutions
to
using
your
particular
software.
F
So
that's
also
very
important,
so
some
tools
for
writing
good
open
source
documentation,
docker
servers,
so
the
customers
make
it
very
easy
for
people
to
maintain
open
source
documentation,
software.
It
is
built
by
facebook
and
it's
currently
so
I'm
currently
on
created
by
currently
maintained
by
facebook,
and
it's
also
an
open
source
project.
So
the
customers
basically
generate
a
website
for
hosting
our
open
source
documentation.
So
syncs
is
also
a
very
good
one.
It's
called
a
documentation
generator
and
it
basically
takes
a
bunch
of
source
files
in
plain
text.
F
So
it's
very
easy,
then
generates
a
bunch
of
product
or
something
mainly
html,
so
it
basically
takes
a
bunch
of
your
source
file
very
easy
to
use
and
create
html
directly
from
it.
So
one
other
I
mean
the
most
popular
form
of
writing.
Your
documentation
is
github
using
your
github
readme
on
creating
using
a
github
pages
to
create
a
website
for
it,
so
to
use
github
for
documenting
your
software.
F
All
you
just
need
to
do
is
to
fill
in
the
readme
markdown
very
easy
to
use,
and
if
you
want
more
than
just
one
sheet
of
formatted
text,
you
can
take
advantage
of
github
pages
too,
and
it
can
even
route
to
a
custom
domain.
It's
also
very,
very
easy
to
use.
I
think
it's
one
of
the
most
popular
form
of
on
writing.
F
Documentation
hosting
documentation,
also
read
the
docs
so
really
dope,
simplified
software
documentation
by
automating,
building
and
posting
version
of
your
docs,
so
which
detox
is
also
very,
very
easy
for
you
to
use.
So
it's
also
very
easy
for
you
to
use
sorry
possible
structure
for
your
documentation.
The
first
thing
you
could
do
is
far
down
the
interruption.
The
first
thing
you
could
do
is
getting
started,
so
a
possible
structure
for
your
customers.
F
Documentation
is
you
need
to
create
getting
started,
highlight
then
also
the
architectural
design
in
production.
Then,
when
you
have
the
artificial
vision
for
your
software,
it
makes
people
to
understand.
Like
I
said,
visual
devices
make
people
understand
how
to
how
the
thought
process
for
you
of
how
you
use
your
particular
software.
Is
there
then,
in
production
usage
guide,
also
very
important.
F
A
lot
of
people
use
this
software
that
will
make
in
production
not
just
development,
so
they're
certain
processes,
they're
testing
with
people
investing
these
people
use
a
particular
software
in
development
and
in
development
and
in
production.
So
we
need
to
create
a
guide
for
how
people
can
use
the
in
production,
but
at
the
end
of
the
day
we
actually
want
to
build
production
grade
software
so
use
cases
I
mean
we
have
you
have
a
software
right.
F
So
how
can
people
use
this
for
various
reasons,
so
the
use
cases
can
also
stop
it
in
a
section
in
your
documentation.
The
reference
is:
where
did
you
pick
testing
things
from
your
software?
Where
did
you
pick
certain
links
to
settings
software?
I
mean
at
the
end
of
the
day
we
need
we
lift
code
from
settings
different
places
to
actually
make
sure
so
referencing.
F
The
particular
code
that
we've
used
is
also
very
important
that
your
roadmap,
so
the
roadmap
gives
your
users
people
that
actually
use
your
open
source
software,
a
guide
on
what
is
coming,
what
new
features
are
coming?
What
do
you
envision
for
the
particular
project?
It's
also
very
so
this
is
right.
Here
is
just
a
basic
structure
of
how
I
envision
a
great
documentation
would
look
like
so
some
example
of
good,
open
source
documentation
began
the
gap.
Documentation
is
really
really
great.
F
You
spend
the
time
using
using
documentation
and
more
time
building
on
the
via
ds.
Docs
talked
about
most
concepts
that
you
actually
need
to
understand.
How
to
use
react.
The
vgs
drug
is
one
of
the
most
perfect
documentation.
I've
seen
with
the
release
of
you
three
I
checked
the
latest
documentation.
It
was
like
really
really
awesome
great
jobs
to
be
entered
using
for
particular
one.
F
Then
the
chat,
ui,
doc
chatter,
uid
library
used
here
in
ninja
the
doc-
is
also
very,
very
easy
to
use
and
very
helps
developers
get
started
immediately
with
this,
with
their
with
chaka
ui,
so
the
github
open
api
dock
I
mean
most
of
us
would
not
like
most
of
us
have
used
github
api
for
certain
reasons,
and
all
we
like
to
use
github
api
for
a
particular
project.
It
was
really
really
easy
to
get
started
with.
Everything
is
the
every
single
thing
you
need
is
there.
F
The
api
is
properly
documented
and
opened
on
then
cloud
foundry
docs,
so
cloud
functions
are
like.
Like
we,
the
company,
I
work
at
the
open
source
project.
It's
one
of
the
best
platform
that
provides
developer
experience
on
kubernetes,
so
the
documentation
is
really
really
easy
and
very
easy
for
people
to
just
start
with
them.
Bootstrap
a
lot
of
us
use,
bootstrap
and
bootstrap
and
open
source
software,
so
bootstrap
gets,
makes
it
easy
for
you
to
build
accessible,
uis
and
also
great
uis.
Very,
very
easy.
F
F
She
says
if
you
read
the
manual,
then
make
a
better
manual,
so
I
mean,
if
you
want
people
to
actually
read
your
documentation,
you
need
to
make
a
better
documentation,
so
people
can
spend
less
time
searching
for
answers
on
how
to
use
the
software
in
other
places
and
spend
more
time
viewing
me
actually
with
your
software.
So
references
are
resources,
so
this
here
right
here,
a
couple
of
references
and
resources
that
I
feel
like
everybody
here:
databases
where
the
stock
should
read
and
spend
your
time
reading.
F
So
most
of
it
is
from
google
on
the
open,
source.com
blog
and
some
from
the
google
open
source
blogging,
apache
lab
just
from
rbo,
and
I'm
talking
about
the
part
of
this.
This
particular
that
gives
the
breakdown
of
what
currency
arrived
means
in
this
particular
image.
So
thank
you,
everybody
for
coming
to
my
talk
once
again.
Thank
you
for
the
interaction
how
to
connect
with
me.
You
can
connect
with
me
on
twitter
at
schooldownload4black.
F
You
can
check
me
out
on
github
activities123
and
if
you
want
to
send
an
email
to
me
on,
for
any
partnership,
also
or
just
just
to
reach
out
and
say,
thank
you.
You
can
reach
out
to
me
at
akitashi,
jimmy.com,
100
documented.
It
really
feels
good.
Thank
you
so
much
everybody
for
coming
to
my
talk
once
again
and
lastly,
I
would
like
to
enjoy
the
attention
of
the
act
of
the
entire
world
in
africa,
I'm
with
habitat
living
in
nigeria,
cases
of
politicality
and
in
namibia.
F
We
are
also
facing
cases
of
killing
symptoms
with
congo,
and
africa
is
20
billion.
So
I
would
like
everybody
to
be
kind
to
what
is
going
on
here
in
africa.
We
treat
to
create
awareness
and
educate
yourself
more
what
happened
in
africa,
because
without
africa
at
the
end
of
the
day,
there's
no
such
thing
as
departure
of
africa.
So
thank
you.
So
much
everybody
once
again
for
coming
to
my
dog.
B
Excellent
thanks
shadrach
yeah,
that
was
great
content
and
yeah.
It
was
a
lot
of
great
examples
up
into
as
well
for
folks
who
want
to
get
involved
in
documentation
and
set
up
their
documentation
properly.
Definitely
check
out
that
and
follow
shedrack
on
twitter
too,
as
well.
You'll,
probably
share
your
slides.
If
you
haven't
done
already.
B
G
G
G
So
this
one
will
cover
what
color
what
is
web
development?
What
is
front
end
development?
Why
is
line
front
end
development?
Wi-Fi
development
is
better
than
back
end
and
full
stack.
What
do
I?
What
do
you
need
to
be
effective?
Developer
left
front
end
development
in
these
few
steps,
learning
resources,
what
you're
free
to
do
add
bye.
G
So
what
web
development
according
to
google
web
development
is
the
work
involved
in
developing
a
website
for
the
internet
or
intranet?
Why
do
you
have
a
courage
from
developing
a
simple
single
starting
page
of
play
text
to
compress
the
web-based
internet
application,
electronic
business
and
social
network
services?
Let
me
put
in
super
tips.
G
One
development
is
using
a
bunch
of
code,
it's
a
languages
to
make
a
webpage
so
you're
making
my
website.
Let
me
just
make
your
webpage
you
like,
if
well,
if
I
ask
you
you're
doing
a
website
for
you
yeah,
oh
you're,
working
for
your
company
right
now,
so
what
you're
doing
why
you
want
to
build
a
website
for
them
or
wait
for
it?
Okay,
let's
use
freelance
for
your
client.
You
have
to
know
what
they
the
website
you
are
making
should
also
promote
their
business.
G
G
It
has
to
do
something
one
may
propose
I
should
promote
here,
so
we
have
three
sections
of
whether
or
not
all
types.
We
have
the
front
end
package
footsteps,
but
we're
only
going
to
focus
our
front
developer
today,
so
the
front
developer,
I
like
to
call
it
what
an
engineer
or
the
web
developer
or
designer
the
photo
develop.
Web
development
is
a
process
of
converting
to
converted
data
to
a
graphical
interface
through
the
use
of
html
css
javascript,
so
the
user
can
view
and
interact
with
that
data.
G
Like
design
a
picture
of
a
food
to
the
main
food,
they
are
going
to
eat
right
here,
for
they
are
going
to
dig
into
it.
That's
what
it
is
very
simple:
it's
just
converting
a
design
or
a
graphical
interface
to
a
an
interactive
website
through
the
use
of
html
css
javascript
order
at
the
front
of
developer
substantive
skills.
Html
javascript
react
viewer,
oh
there's,
a
type
area.
Sorry,
it's
w!
It's
a
view
v-u-e
or
any
other
framework.
You
can
use
bootstrap
or
any
other
css
free
book.
G
G
That
is
always
stressful,
well
and
other
than
that,
but
you
need
to
like
bootstrap
sal
s-a-s-s
scss
until
I
make
it
easier
same
with
javascript,
so
things
like
that,
but
you
you
can
actually
make
a
website
that
can
blow
someone
away
without
html
css.
I've
done
that
a
lot
and
it's
been
the
best
thing
I've
ever
done
without
I'm
currently
using
it
for
my
usa,
but
I
didn't
just
make
it
more
extraordinary
because
it
gives
more
functional
functionality.
G
So
let
me
go
to
this
side,
so
why
should
I?
Why
should
you
like
this
photo
development
like
I
want
to
play
something
without
knowing?
Why
should
I
leave
it
like?
Do
you
have
to
use
my
life?
Wouldn't
it
improve
my
life?
So,
first
of
all,
if
I
demand
as
much
as
other
sections
back
at
the
belt,
where
full
stack
mobile,
they
are
all
in
demand.
G
But
I
me
personally,
I
took
according
to
google.
41
developers
are
very
intimate
than
the
others,
so
you
can
work
as
a
self-employed
philosopher,
you
cannot
find
organization
anything,
and
this
is
also
in
the
creative
career
according
to
google.
Again
goodness
my
best
friend
I
live
in
my
pastor
web
developer
as
well.
All
that's
so
pleasing.
G
This
is
one
of
the
most
flexible
carriers
according
in
general,
it's
very
flexible.
This
skill
set
you
acquire,
allow
you
to
work
in
different
areas
like
image,
entity,
ux,
ui
boy.
Well,
okay,
that's
really!
Where
I
grew
up,
I
forgot
to
remove
it.
I
was
trying
something
else
so
things
like
that
it
works
it
design
everything.
So
this
brings
us
to
creativity.
G
Protect
white
women
is
all
about
creativity,
create,
create
problem.
Solving
I
refer
to
the
web
developer.
You
have
the
skills
to
build
customized
websites
to
create
the
best,
possibly
do
that
in
topics.
I
know
what
they
doesn't
need
to
keep
and
for
the
developer.
Please
be
good
with
user
experience.
Like
I
don't
say
I
don't
see
you
later,
it's
like
user
experience,
so
you
know
how
they
use
the
interactive
state.
G
G
So
I'll
also
be
creative,
maybe
maybe
okay,
the
client
wants
you
to
feel
the
text
for
them.
You
can
break
up
text
niche
different
things.
Even
is
it
very
good
at
the
photo
developer,
you
should
have
basic
designing
skills,
so
maybe
you
want
to
add
an
image,
but
you
want
it
to
match
with
the
height
elegancy,
so
you
have
to
design
something
to
make
it
elegant.
G
So
it
is
really
good.
I
wait
in
front
of
everybody
back
and
make
my
website
you
can
create
a
successful
career,
though
that
you'll
be
happy
with
I'll
active.
I
yeah
I'll
keep
commenting
in
between
please.
If
you're
not
enjoy
working
at
a
workplace,
maybe
you're
having
a
problem
with
it
or
the
boss,
the
boss
dog
grades,
you
it
doesn't
like
it
doesn't
motivate
you
like.
The
copy
itself
is
just
bad.
You
cannot
cope
with
it.
It's
not!
It's
not
like
you
enjoy
your
work.
They
take
control
of
my
of
your
side
projects.
G
Now
let
me
use
javascript
exactly
translate,
keep
vegan
framework
from
here
there.
Every
time
like
when
did,
I
think
next
gs
just
came
out.
I
think
this
year,
or
was
it
oxygen
one
of
them
they
came
out
this
year.
You
could
never
get
bored
in
this
career.
You
know
it's
always
available
changing
with
more
skills
and
you
get
to
interrupt
with
new
skills.
Let
your
skill,
it
will
keep
you
very
engaged.
You
can
never
get
bored
of
when
you
have
been
except
you
stick
to
one
language.
G
You
usually
get
bored,
I'm
sorry
but
you're
trying
to
get,
but
it's
actually
provide
a
lot
of
opportunity
if
you're
at
your
creativity,
it's
very
I
don't
know
how
to
say
anything,
but
creativity
is
the
best.
So
far
the
developer
is
basically
so.
This
is
the
rush.
The
picture
I
don't
have
a
good
picture
quality,
but
this
is
kind
of
a
road
map
to
her
photo
developer.
The
oh
everything
you
have
to
do
on
the
further
developer.
G
G
So
I'm
going
to
close
sh.
So
now,
let's
go
to
the
left
side.
Why
is
front
end
better
than
bucket
at
first
time?
That's!
That's!
I'm
just
saying
it.
I
know
what
I
say.
Some
people
actually
think
that
why
would
they?
Why
would
the
worst
section
be
better
than
the
other
side?
I
can't
tell
is
better:
all
of
them
are
good.
G
G
So
but
none
is
better.
None
is
better.
All
of
them
are
different,
otherwise,
the
same.
They
have
the
same
level.
You
gotta
say
because
I'm
back
and
rape,
I'm
better
than
you
I'm
better
than
you
other
friend,
because
you're
infertile
driver
okay,
grandpa
better
than
protect
the
back
of
the
director.
No
all
of
you
the
same,
don't
drug
with
anyone,
even
even
though
you're
better,
please
don't
say
that
it
might
actually
make
some
people
give
it
peace.
G
I
give
up
so
differences
between
footed,
a
bucket
protector
development,
further
developer
work
or
what
the
user
can
see.
Backhand
building
infrastructure
that
supports
it.
The
temperature
refers
to
the
user
interface,
the
interaction
everything,
but
the
theme
back-end
meets
the
server
application
and
database.
That's
the
simple
and
major
difference.
I
can
give
you.
So
what
do
you
need?
Elevator,
developer.
G
G
When
a
few
things
redux
yeah
really
documentation,
you
can
also
watch
a
project,
so
I
want
to
read
the
conversation
it
actually
take
notes.
Maybe
there's
a
certain
you
need
to
just
take
it
out.
Okay,
so
let's
see
I'm
not
really
good
with
this
number
two.
By
doing
it
puts
concept
into
practice
when
you
learn
something
put
it
into
plato's
face,
so
you
can
stick
to
this
braid
to
your
best
part
of
the
body,
but
it's
going.
The
water
will
appear
everything
so
put
the
consent
into
practice.
G
Take
us
day
to
year,
so
make
projects
continue.
Make
a
project
like
daddy
topsy,
says
always
be
beauty,
always
be
building
code
code
code
refactor
your
code
like
make
improve
it,
remove
the
bug
and
all
this
thing
actually
appears
to
others,
so
they
can
criticize
so
like
to
say
what's
wrong.
Maybe
it's
the
way
that
maybe
it's
all
responsive
enough
and
all
those
things-
and
I
got
this
from-
but
I'm
on
twitter
he's
some
css
developer
developer,
but
he
doesn't
want
css.
He
also
creates
twitter.
G
Also,
you
are
free
to
doubt
you're
free
to
think
you're,
free
to
communicate,
you're
free
to
ask
questions
you're
free
to
make
mistake,
you're
free
to
leave
from
your
mistake.
You
are
free
to
google
and,
most
importantly,
you're
free
to
have
fun
in
learning.
Always
affordably.
Don't
forget
to
google.
Google
is
a
developer
best
friend,
so
you
can
live.
So
what
can
I
do
whatever?
So
you
can
learn
from
food
cooker,
but
that
will
deal
with
stock
development.
You
can
live
from
code
academy.
You
can
therefore
javascripty.com.
G
G
Suite
you
can
check
its
speed.
Tweet,
that
is
between
explain
to
it
is
a
lot
of
resources.
So
this
is
the
link,
then
one
of
the
starters,
the
big
one.
So
thank
you
and
bye.
So
if
you
love
technology,
if
you
enjoy
creating
a
great
user
experience
and
are
looking
for
and
are
looking
for
an
exciting
career
with
a
lot
of
good
potential,
further
qualifications
might
just
be
the
best
career
for
you.
So
thank
you
and
I
will
actually,
if
you
have
a
question
you
might
trip,
I
delivered
that,
but
thank
you.
G
B
A
B
G
B
Okay,
excellent
well
folks,
thanks
for
joining
us
for
the
the
github
africa
meetup,
I
just
want
to
mention
that
we
do
have
a
meetup
page.
So
if
you
are
interested
in
finding
out
when
the
next
meetup
will
be
next
month,
definitely
check
out
the
meetup
page,
I
think
we
could
drop
the
link
somewhere
in
the
chat.
Are
you
gonna
meet
dot
com
and
search
for
github
africa
too,
as
well
trust
me,
it'll,
be
the
only
one
that
comes
up
but
yeah,
so
we
have
this
event.
B
It's
going
to
be
happening
monthly.
I
wanted
this
shout
out
if
anybody
is
interested
in
joining
us
in
the
future,
if
you
are
looking
to
speak
as
well,
we're
looking
for
always
looking
for
great
speakers
and
great
content,
so
definitely
leverage
this
this
platform
for
showcasing
your
skill
and
your
talent
and
what
you're
doing
in
africa,
and
we
appreciate
that
they
hear
from
you
so
tell
your
friends.
Tell
your
family
also
tell
your
friends
and
family
about
github
universe.
Github
universe
will
be
a
free
event.
B
This
december
and
it's
gonna
be
focused
around
talking
about
the
things
we're
shipping
at
github.
We've
been
shipping
a
lot,
a
lot
of
new
features,
we'll
be
shipping.
A
lot
of
new
features
this
december
as
well,
so
make
sure
you
rcp
and
register
for
the
event
and
say
hello:
we'll
have
a
lot
of
opportunity
for
the
community
to
join
together
and
collaborate
on
different
things.
So,
with
that
being
said,
appreciate
all
yeah
and
yeah.
Thank.