►
From YouTube: GitHub Virtual Meetup Africa
Description
5:06 - Start
Hosted by GitHub’s own Martins Ewere https://www.linkedin.com/in/martins-ae/ Community co-host Namaara Racheal https://www.linkedin.com/in/namaara-racheal-a631b566/
The month of May, we'll be discussing all things InnerSource, Open Source management, GitHub Actions and community.
14:17 - Zack Koppert: Innersource in Government
https://twitter.com/ZacheryK89
43:22 - Anita Ihuman: GitHub Actions and Open Source Management
https://twitter.com/anita_ihuman
1:03:47 - Catherine Kiiru: Tech Hiring Season - Red flags to watch out as you apply for jobs
https://twitter.com/CatherineKiiru
https://www.meetup.com/GitHub-Africa
A
A
B
B
B
B
A
A
A
C
B
A
Now
one
thing
I
like
to
do
on
this
meetup
is
I
like
to
know
where
you
are
watching
from
so
please
let
us
know
in
the
chat,
yeah,
andrea
you
can.
You
can
share
the
share
your
screen.
Let
us
know
in
the
chat
where
you
are
watching
from
I'm
from
nigeria.
Currently
I'm
in
lagos,
nigeria
and
looking
forward
to
learn
all
of
our
repeats
viewers
here
on
github.
A
A
Yeah
perfect,
so,
basically,
here
at
github,
I'm
an
account
executive
and
you
know
I
talk
to
developers,
customers
all
the
time
and
I
have
people
with
github
technologies,
I'm
also
a
crypto
enthusiast
and
a
rookie
investor.
So
definitely
check
me
out
on
twitter
and
see
all
the
things
I
do
over
there
and
richard
over
to
you.
B
All
right,
thank
you
so
much
martins,
my
name
is
namara
rachel.
I'm
a
software
advocate
in
simcoe
and
singapore
is
a
femte
company
based
in
uganda
in
africa.
Almost
I
also
happen
to
be
our
mediatek
network
global
ambassador.
I'm
really
so
glad
to
meet
everyone
here
and,
if
you're
overcome,
let's
learn
from
one
another.
B
A
And
basically,
today
we'll
be
going
through
some.
You
know,
git
up
news
and
also
we
have
three
speakers
lined
up
for
you
today,
we'll
be
talking
zach
I'll,
be
talking
about
inner
source
in
government
and
anita,
and
it
has
been
here
several
times
and
it
I'll
be
talking
about
how
you
leverage
data
actions
in
open
source
management
catering
cure.
A
A
A
A
Now,
where
you
can
preview
the
dependencies
that
you
are
importing
into
your
code
right
before
right
before
you
build
your
you,
build
them
into
your
code
base.
So
you
know
the
way
dependable
used
to
work
before
after
you've
built
your
application.
You
you
then
see
the
dependencies
that
you
had
within
your
application,
but
now
you
can
actually
preview
what
dependencies
you
have
in
a
given
packet
before
you
consume
them.
A
So
and
obviously
you
you
guys
should
already
know
that
dependable
helps
you
to
keep
your
dependencies
up
to
date
and
it's
a
it
has
you
you
can
automate
that
process.
So
as
you
beauty,
open
source
projects,
as
you
contribute
to
open
source,
your
presence
projects
depend
about.
Preview
will
help
you
to
be
more
secure
in
your
development
practices
and
make
sure
that
you,
you
are
using
the
right
standards
for
all
your
development
all
right.
A
A
Github
advanced
security
is
available,
and
we
also
want
to
hear
back
from
you.
We
are
continuing
to
improve
the
product.
So
if
you
have
a
feedback,
you
can
just
use
the
code,
the
the
barcode
to
give
us
feedback-
and
let
us
know
if
you
detect
any
experts
on
on
the
product-
and
we
are
more
than
happy
to
to
get
us
feedback
from
you.
B
Oh
yeah,
I
think
that's
it.
Thank
you
so
much.
Thank
you
so
much
martin
for
right
now.
Now
we
have
amazing
speakers
who
are
lined
up
who
are
going
to
talk
to
us
the
evening
or
today
morning.
So
our
first
speaker
is
called
copper.
He's
a
aselia
devops
engineer
at
github.
He
hopes
he
helps
customers
get
adopted
to
github
and
maybe
get
familiar
with
github
transformation,
devops
transformation.
D
D
D
First
before
we
get
started
if
you're
not
familiar
with
inner
source,
what
I'm
referring
to
when
I
talk
about
inner
source
is
really
it
is
a
way
of
applying
the
open
source
way
of
working
inside
of
an
organization
so
inside
of
a
government
or
a
company,
or
anything
like
that
and
by
the
open
source
way
of
working.
I
just
mean
lots
of
sharing
lots
of
software
reuse
and
anyone
can
contribute
type
of
model
and
so
open
source
obviously
isn't
appropriate
for
every
project
that
everyone
work
on,
that
everyone
works
on.
D
It
allows
you
to
leverage
different
groups
of
people
across
the
entire
organization,
but
then
still
to
to
work
on
it
together
and
get
that
benefit
of
collaboration,
not
sure
about
you
folks,
but
I
know
that
when
I've
worked
on
projects
in
collaboration
with
somebody
else,
they
always
turn
out
better.
Two
minds
are
better
than
one.
D
So
I
do
want
to
reassure
you,
though,
that
you
know,
based
on
my
experience,
working
with
github
customers
and
governments,
and
particularly
large
governments
and
agencies
in
the
u.s,
is
more
my
experience,
but
it
is
possible
to
to
do
intersourcing
government,
and
you
don't
just
have
to
take
my
word
for
it
either.
I'll
supply
some
examples,
so
if
we
look
at
at
examples
of
inner
source
in
government,
so
there's
there's
things
working
at
the
small
scale
and
then
there's
also
things
working
at
a
very
large,
like
intergovernment
agency
scale.
D
So
on
the
small
scale,
I
can
tell
you
about
the
va,
notify
project
and
the
va
is
the
department
of
veterans
affairs
in
the
us.
It's
a
us
agency
and
they
have
built
this
notification
system.
They
actually
pulled
in
an
open
source
project
and
made
it
inner
source-
and
you
know
modified
it
specifically
just
for
the
va,
but
essentially
they
have
multiple
different
products
right,
so
they've
got
a
website.
D
They've
got
an
app
they've
got
back-end
health
services
systems
and
databases,
and
a
lot
of
these
different
systems
all
need
the
ability
to
be
able
to
notify
their
customer
the
veterans
in
this
case,
and
so
instead
of
building.
You
know,
12
different
solutions,
one
for
each
product
that
all
worked
differently.
D
They
decided
to
consolidate
and
just
build
one
notification
platform
that
actually
is
usable
in
all
those
different
areas,
so
they're
inner
sourcing
there
and
that's
used
across
all
of
that
u.s
agency.
So
that's
an
example
of
a
relatively
small
scale
compared
to
the
size
of
the
us
government,
a
way
for
them
to
sort
of
save
time
and
money
and
effort
by
reusing
and
intersourcing.
D
D
So
if
you're
not
familiar
with
that
term,
it
just
means
it's
about
putting
software
development,
software
security
and
software
operations
kind
of
all
into
one
platform,
and
so
that
different
agencies
within
the
us
government
can
just
pick
up
this
software
factory
platform
and
use
it
to
be
able
to
develop,
secure
and
deploy
their
their
code
so
yeah.
So
the
the
scale
is
massive,
and
you
start
to
notice
too,
when
you
get
to
this
larger
scale
that
there's
a
a
community
around
it,
there's
training
that
goes
with
it.
D
So
it's
not
just
like
the
code
is
being
shared,
but
there's
actually
a
community
built
around
the
code,
just
like
happens
in
open
source
where
you
start
to
get
to
know
the
people
that
are
working
on
it
and
you
can
ask
people
questions
and
makes
the
software
actually
usable
or
reusable
in
this
case
so
yeah.
It's
also
worth
noting
that
that
there
are
some
projects
that
exist
for
government
reuse
on
the
open
source
side.
D
D
Then
I've
listed
out
a
couple
here.
So
we've
got
engineering
efficiency,
economic
impact,
community
and
transparency
so
on
the
efficiency,
one
we'll
tackle
that
first
and
economic
impact
together,
because
those
are
really
tied.
A
gallup
poll
in
2009
found
that
you
know
americans
perceived
50
percent
of
their
government
funding.
D
If
we
keep
that
in
our
minds,
just
fifty
percent
of
government
funding
goes
to
waste
as
perceived
by
the
people
in
2021,
the
u.s
budgeted
92.2
billion
dollars
for
it
spending
so
computers
and
software
development
and
all
this
stuff.
And
so,
if
you
think
about
those
numbers
are
sort
of
staggering
right
like
if
you
can
create
a
more
efficient
government
and
then
you
know,
50,
there's
a
large
opportunity
to
be
able
to
to
save
a
lot
of
money
which
could
lead
to
significant
economic
impact.
D
If
you
look
at
this
for
smaller
countries
too
they're
looking
to
do
more
with
less
funding
because
of
their
relative
size,
and
so
it's
even
more
important
in
the
in
the
small
organizations
to
be
able
to
increase
the
efficiency
here.
So
that's
a
big
pull
for
most
folks
to
be
able
to
start
looking
at
inner
sourcing
seriously
and
say,
oh,
is,
is
this:
you
know
something
that
that
we
should
do
so.
A
a
common
source
of
this
waste,
though,
when
we're
talking
about
like
government
waste
on
the
I.t
side
is
rework.
D
So
like
that
example,
the
notification
system
I
gave
they
would
have
had
to
spend
you
know
if
it's
if
the
notification
system
is
going
to
be
used
in
five
different
places,
and
it
was
going
to
be
all
developed
differently,
because
maybe
they
weren't
aware
that
everyone
needed
it.
Then
you
know
in
terms
of
the
waste
there
they
would
have
had
to
spend
five
times
as
much
as
they
did
to
be
able
to
develop
it.
So
normally
in
a
software
organization
in
the
private
sector,
you
know
just
regular
businesses.
D
They
have
software
architects
that
are
responsible
for
identifying
these
opportunities
across
the
entire
business
to
sort
of
consolidate
things
like.
Oh,
it
looks
like
all
these
projects
need.
You
know
this
one
piece
and
so
we'll
develop
it
once
and
use
it
everywhere,
but
in
governments
sometimes
the
way
that
they
get
sectioned
off
into
different
ministries
or
agencies.
D
So
if
you're
in
a
government
agency
and
you're
developing
software,
you
can
contribute
your
piece
of
software
to
this
internal
website,
this
catalog
of
reusable
existing
solutions,
so
that
when
people
are
developing
new
things,
they
can
go
there
and
look
first
and
say:
has
this
already
been
done
somewhere
else?
You
know
most
folks
already
do
this
with
open
source
if
I'm
as
a
developer,
get
assigned
to
develop
a
website.
D
First,
I
go
look
at
all
the
open
source
components
that
I
can
use,
so
I
don't
have
to
write
them
myself
and
I
use
that
to
build
my
website.
Well,
we're
adding
in
another
step
before
or
after
the
open
source,
but
before
we
go
and
build
it
ourselves
to
also
look
for
existing
solutions
in
inner
source.
D
So
that's
again
increasing
our
engineering,
efficiency
and
economic
impact.
So,
but
let's
take
a
look
at
the
community
piece.
Actually
so
there's
this
poetic
nature
to
governments
practicing
community
in
their
in
their
software
and
building
communities
around
pieces
of
software,
because
governments
are
meant
to
govern
bodies
of
people
right
communities,
that's
a
part
of
what
they
do.
D
That
sort
of
that
democracy
allows
for
the
organization
of
folks,
with
similar
interests
to
organize
inner
source
communities
on
the
other
side
are
going
to
enable
this
for
for
government.
So
a
couple
of
examples
of
that
that
I've
seen
personally
in
working
with
different
government
agencies,
is
a
community
or
sometimes
they're
called
communities
of
practice,
around
security
and
specifically
software
security.
D
D
Again
we
talked
about
the
visibility
problem
that
you
don't
have
visibility
into
all
these
different
areas.
So
then,
when
software
architects
come
together
out
of
these
different
groups
and
start
to
chat
with
one
another
about
what
they're
working
on
and
what
they're
building
in
their
respective
teams,
then
sharing
across
those
teams
can
happen
a
whole
lot
easier.
D
So
the
community
pieces
is
a
really
important
benefit
there
and
then,
let's
take
a
look
at
the
last
step
and
that's
going
to
be
a
step
towards
transparency,
so
the
more
that
you're,
intersourcing
and
and
open
sourcing
within
the
government
within
any
organization.
It
can
provide
a
fantastic
amount
of
transparency
into
what
the
code
actually
does,
what
the
processes
actually
are
and
what
technologies
are
actually
being
used.
D
So
if,
let's
say,
one
team
is
struggling
with
their
their
use
of
react
to
be
able
to
build
websites,
but
another
team
is
very
experienced
in
that
and
they
don't
normally
talk.
If
we
add
some
transparency
into
that
by
allowing
them
to
share
their
code.
Well,
then
we're
able
to
make
those
connections
and
identify
that
and
build
those
relationships.
D
So
government
has
just
traditionally
been
plagued
by
an
over
reliance
on
the
the
principle
of
least
privilege
and
and
just
what
that
means
from
a
security
standpoint
is
only
give
people
permission
to
do
only
what
they
need
to
do
for
their
job
and
nothing
more.
Otherwise
it
creates
a
security
risk
and,
while
that's
true
and
it's
a
good
principle
to
live
by,
it
can
be
overdone.
D
That
seems
to
expand
and
that
can
make
security
folks
a
little
bit
nervous
and
rightfully
so
so,
there's
a
balance
that
we
want
to
strike
between,
making
everything
transparent
and
making
everything
open,
as
well
as
keeping
the
appropriate
things
locked
down
and
closed,
but
not
too
much
so
so
you
can
consider
how
this
might
be
applied
to
inner
source
as
well
right.
So
some
things
are
going
to
be
shared,
maybe
just
between
specific
groups.
D
You
know
in
the
us.
Sometimes
they
share
things
but
share
things
only
between
the
military
groups
of
the
government
and
not
the
the
other
half
and
so
yeah.
One
thing
to
consider
is
to
decide
for
your
government
or
for
your
organization
about
sort
of
a
decision
framework
for
like
how
do
we
make
decisions
about,
what's
appropriate,
to
share
and
what's
not
and
if
you
already
have
some
sort
of
decision
tree
or
matrix
to
be
able
to
decide
that
well,
is
your
software
included
in
that
and
what's
appropriate
to
share
in
your
software.
D
So
I
really
I
really
enjoy
this
comic
and
I
I
normally
call
it
some
things,
never
change.
So
if
you
look
on
the
right
hand,
side
there's
these
folks
that
are
trying
to
transport
some
rocks
across
the
distance
and
they've
got
some.
If
you
notice
they've
got
square
wheels
on
their
little
cart
there,
and
you
can
imagine
how
bumpy
and
difficult
that
might
be
to
drag
through
the
dirt
and
then
there's
this
guy
over
here
on
the
left.
D
Who's
got
some
round
wheels
and
looks
like
he's
offering
them
hey.
You
know
you
want
to
try
these
instead,
but
their
response
is
almost
hilarious
right,
so
they
say
no
thanks.
We're
too
busy
like
we
have
a
lot
of
work
to
do
it's
very
hard
work.
There's
no
time
to
upgrade
to
these
round
wheels
and
and
try
and
get
those
working
or
no,
our
our
leaders
won't.
D
Let
us
you
can
imagine
some
of
the
excuses
that
they
might
have,
but
it's
obvious
to
all
of
us
as
people
outside
of
this
process
and
people
outside
of
doing
the
hard
work
every
day
and
not
looking
up
that,
it's
really
silly.
If
they
just
took
the
short
term
cost
of
upgrading
their
wheels,
they
would
have
significant
long-term
benefits
of
being
able
to
get
around
faster
and
not
have
the
work
be
as
hard.
D
So
this
is
a
a
model,
a
foil,
a
an
image
really
of
what
happens
with
inner
source
a
lot
and
especially
intersourcing
government.
This
is
that
we
sort
of
propose
hey.
We
have
this
way
of
sharing
code,
reusable
code
and
we'd
like
to
sort
of
upgrade
the
way
that
you
do.
Software
and
many
folks
in
government,
especially
very
hard-working
folks,
are
like
oh
no.
We
don't
have
time
to
change
things
out
or
change
the
way
we
do
things
we've
got
to
get
this
done.
D
We've
got
deadlines
and
all
these
things,
and
so
it's
important
to
recognize
some
of
these
issues
and
to
the
thing
that
I
normally
do
is
I
try
and
term
turn
these
obstacles
that
they
that
they
bring
up
into
motivators
right.
So,
if
there's
not
enough
time
well,
there's
actually
you
know
if
you
take
a
second
and
look
at
it,
there's
not
enough
time
for
you
to
waste
continuing
doing
things
the
same
way,
because
you'll
gain
so
much
time
by
this
upgrade
that
it'll
really
pay
off
or
you
know,
there's
no
leadership
buying.
D
No,
you
know
leaders
don't
want
more
transparency
or
something
like
that.
They
just
want
us
to
keep
keep
doing
things.
The
way
that
we
have
been
we'll
turn
that
into
an
opportunity
to
convince
leadership
and
to
be
the
one
to
convince
them
of
this
good
idea
and
then,
when
it
pays
off,
the
leadership
looks
back
at
you
and
says:
oh
wow.
That
was
a
really
good
idea:
you're
you're
kind
of
smart
person.
So
so
that's
nice
and
then
there's
a
number
of
other
things
that
I've
heard
too.
D
Like
oh
well,
we've
got,
everyone
has
different
githubs,
and
so
we
can't
we
can't
share
things.
Well,
we
can
overcome
that.
You
know
we
can
consolidate
github
organizations
or
add
outside
collaborators,
and
things
like
that.
So
my
point
is:
there's
solutions
to
all
of
these
things
we'll
go
ahead
and
hit
the
next
one.
D
This
is
really
about
inspiring
folks,
with
your
vision
for
a
more
transparent
government
for
a
more
open
government
for
a
more
efficient
government,
whatever
that
that
headline
goal
of
that
it
makes
inner
source
attractive
to
you.
That
should
be
the
thing
that
drives
you
to
inspire
others
in
your
organization
to
hey
in
the
future.
We
could
be
more
this
efficient
or
whatever.
D
If
we
try
out
this
inner
source
thing
and
that'll,
give
folks
motivation
to
put
in
the
effort
to
try
and
change
the
way
that
they
work,
which
just
as
humans,
we
don't
like
to
change
the
way
that
we
work,
we
like
habits
and
patterns
and-
and
so
it's
sort
of
sometimes
against
our
nature.
But
we
just
need
to
revive
that
spark
of
curiosity
to
try
things
out
which
can
sometimes
get
worked
out
of
our
lives,
so
we
need
to
keep
that
alive,
but
also
we
want
to
outline
tangible
next
steps.
D
D
What
are
some
concrete
things
that
we
can
do
so
that
motivated
folks
can
now
actually
contribute
to
accomplishing
this
it's
effectively
like
crowdsourcing
the
effort,
so
sometimes
those
next
steps,
look
like
okay,
we're
going
to
create
a
repository
where
everybody
can
put
in
a
list
of
what
they're
working
on
so
that
we
can
just
see
and
have
visibility
into
what
other
folks
are
working
on.
Sometimes
that
looks
like
changing
the
permissions
on
your
github,
repo
and
saying
okay.
D
This
is
instead
of
going
to
be
private,
it's
going
to
be
open
internally
and
so
yeah
just
listing
those
out.
You
also
want
to
align
to
your
agency's
goals
and
strategies.
So
it
often
times
if
you
try
and
start
inner
source
or
anything
like
that,
then
if
it's,
if
the
leadership
is
trying
to
go
this
direction
of
like
what
we're
really
focusing
on
right
now,
is
you
know
more
software
features
and
delivering
them
faster?
So
we
can't
do
inner
source,
because
you
know
we
don't
have
enough
time.
We
have
to
go
faster.
D
You
need
to
make
sure
that
you
present
how
inner
source
can
actually
help
accomplish
the
goals
that
the
leadership
is
trying
to
do
so
that
they
don't
you're
not
working
against
each
other.
Hopefully
that
makes
sense
and
then
find
champions,
and
what
I
mean
by
that
is
just
find
people
that
you
can
help
understand
the
idea
of
inner
source,
how
how
the
sharing
leads
to
benefits
and
how
what
those
benefits
could
really
do
for
the
organization.
D
D
They
they
can
see
written
down.
Oh
well,
these
are
the
things
that
have
changed.
We
used
to
do
things
that
way
it
was
much
slower
now
we
do
it
this
way
and
it's
faster,
and
so
they
can
say.
Oh
well,
maybe
we
should
keep
going
with
this
and
keep
doing
this
way,
not
go
back
to
the
old
way,
so
that
can
be
really
encouraging
for
folks,
especially
new
folks
to
the
organization
and
then
the
last
one
is
just
to
measure
based
on
impact
targets,
I'll
break
that
down
a
little
bit.
D
So
if
you
are
in
an
organization
that
is
data
driven
or
wants
to
make
decisions
based
off
of
sort
of
recorded
information,
so
it
proves,
for
example,
that
something
is
working.
You
want
to
make
sure
that
you
measure
the
right
thing
so
in
inner
source.
If
you're
saying
oh,
let's
do
this
inner
source
thing
and
the
leadership
says
okay.
Well,
you
can
do
that.
Just
make
sure
that
you
know
you
are
intersourcing
10
new
projects
a
week.
D
Okay!
Well,
that's
a
choice,
one
thing
to
measure,
but
it's
not
necessarily
a
good
thing
to
measure,
because
you
can
imagine
maybe
at
the
beginning
that
works
really
well,
but
then
you
start
to
run
out
of
projects.
So
should
we
shut
everything
down?
No,
that's
not
the
right
idea,
and
so
you
want
to
make
sure
that
you're
measuring
the
right
thing
at
the
right
time.
D
You
know
a
better
way
to
communicate
between
different
teams,
different
things
like
that,
because
the
needs
change
over
time
and
it's
just
important
to
keep
that
in
mind.
So
yeah.
I
think
thank
you,
though,
for
the
time
me
being
able
to
share
my
experience
here.
It's
really
great
to
be
able
to
sort
of
take
all
of
this
information
of
different
government
folks
that
have
worked
in
one
place
and
hopefully
help
other
people
kind
of
not
make
the
same
mistakes
or
or
guide
them
better
on
on
how
to
do
an
inner
source
practice.
D
B
A
Oh
yeah,
I
I
really
love
the
analogy
of
the
of
the
cartoons
we're
like
around
with
on
the
square
that
was
hilarious.
It's
just
how
we
are
stuck
in
our
own
both
ways
and
we
don't
want
to
change
and
we're
like
too
busy
heads
down
doing
the
wrong
things
over
and
over
again.
So
that's
great,
don't
reinvent
the
wheel,
reuse
things
that
you
have
within
your
organization.
I
think
that's
one
of
the
key
takeaway
you
know.
Thank
you!
Thank
you
zach.
B
B
C
These
have
actions,
help
you
to
view
tests
and
deploy
your
applications.
It
can
also
be
used
to
automate
customize
and
execute
yourself
to
develop
network.
You
write
your
repositories
on
your
github,
so
github
provides
github
action,
alongside
with
other
cool
features
such
as
the
code
review
tool
on
an
issue
tracker
that
are
perfect
for
managing
and
managing
and
maintaining
your
open
source
project.
So
how
do
github
actions
work?
Human
acts.
C
C
But
then
it
is
always
crucial
and
to
ensure
that
the
software
code
base
is
carefully
and
continuously
tracked
and
managed,
and
when
you,
in
a
case
where
you
want
to
manually,
manage
and
maintain
the
code
base
of
particular
software,
you
get
you
notice
that
by
time,
you're
done
going
through
the
pull
request
on
the
difference.
In
let's
say,
your
project
has
about
five
repositories
and
you
have
to
check
each
one
one.
C
In
a
case
where
you
have
to
take
only
single-handedly
maintaining
eight
projects
single-handedly
without
the
aid
of
any
tool,
you
would
have
you
always
experience
the
kids
situations
of
still
and
unattended
issues.
Either
the
issues
have
been
fixed
but
then
have
not
been
closed
because
nobody
actually
would
have
to
close
them
or
the
issues
have
been
created,
but
nobody
attended
to
them
and
is
taking
like
forever
to
actually
attend
to
them.
I
will
come
and
experience
a
hard
time
with
an
open
source
project.
C
Where
I
wanted
to
make
a
contribution,
then
I
I
observed
that
the
issues
the
issues
were
dating
back
to
two
years
to
three
years
and
at
first
I
thought
it
was
funny,
but
of
course
it's
actually
fun
to
see
that
issues
are
that
long.
But
it
made
me
wonder
and
ask
myself
like
lots
of
questions
like
what
happened,
that
these
issues
are
still
here
tomorrow.
C
Is
that
the
maintainers
have
not
taken
notes
of
these
particular
issues,
or
they
don't
know
that
these
issues
are
still
open
and
some
of
them,
when
you
make
a
comment,
they'll
tell
you
that
these
issues
have
been
fixed.
So
why
is
it
still
open,
and
these
are
some
of
the
problems
that
you
have
when
you
actually
manually
have
to
like
maintain
the
projection
position,
and
then
it
wastes
the
maintenance
time
as
a
maintainer.
C
You
don't
you
have
to
like
manually,
go
through
it,
which
is
like
time
consuming
and
it
gets
exhausting
at
the
end
of
the
day.
It's
you
get
slow
response
to
slow
response.
You
see
that
there's
always
slow
response
to
comments
and
issues
that
are
already
created.
Now.
As
a
contributor,
you
drop
a
comment
on
a
particular
issue,
and
then
it
takes
about
a
week
before
the
maintainer
of
that
particular
project
gets
back
to
you
and
tells
you
whether
we
should
go
on
and
fix
it
or
the
issue
has
already
been
tackled.
C
I
had
an
encounter
similar
to
this
one
and
I
create
I
saw
I
came
across
an
open
suspicion
as
I
was
exploiting
the
top
tech
issues.
So
I
I
came
across
this
issue
that
I
thought
I
was
actually
going
to
like
tackle
like
it's
easy,
because
it's
just
a
documentation
and
then
I
commented
I
want
to
take
on
this
issue,
but
it
took
about
two
to
three
days
before
the
meeting.
Actually
I
signed
that
issue
to
me.
C
You
can
imagine
how
that
would
be,
because
it
took
like
how
many
how
many
days
we
attended
to
me.
So
imagine
I
make
another
correction.
How
many
days
again
before
you
come
back
to
review
correction,
I
already
get
this
things
become
very,
very
discouraging
from
new
contributors
to
a
particular
project,
and
also
you
ignore
new
contributors,
because
they're
they're,
like
because
the
open
source
operation
probably
has
about
24
representatives
or
40
representatives,
depend
on
the
size
of
a
particular
project.
C
It's
going
to
take
a
long
time
before
you
attend
to
every
single
contributor.
That
drops
a
comment.
It
will
take
a
long
time
before
you
manually
go
through
each
and
every
repository
checking
for
contributors
that
need
help
and
at
the
end
of
the
day
you
neglect
most
of
the
contributors
that
are
not
very
familiar
with
working
with
open
source
organizations
and
also
there
are
no
standard
contribution
contributing
guide.
C
There
are
know
standards
for
contributing,
so
you
can
this
most
organizations
always
stick
with
a
particular
pattern
which
their
their
contributions
should
go
and
in
a
case
where
somebody
does
not
actually
go
through
through
this
cross.
This
pattern,
then
the
appropriate,
don't
get
messed
so,
but
then,
when
you
don't
have,
when
you're
manually,
making
your
look
like
this
they'll
be
very
they're,
very
high
chances
that
the
standards
for
your
particular
projects
are
no
good
signing,
because
not
everybody
breathes
through
contribution,
guys.
Some
persons
just
ignore
the
contribution
guy
and
the
good
thing.
C
C
Let's
say
you
want
your
project
to
always
have
an
icon
that
is
attached
to
it
once
you're
creating
a
pre-request
most
contributions
are
not
actually
muted
documents
or
the
documents
of
your
particular
supremacy
keep
out
that
particular
item
and
you
wouldn't
notice,
because
you
have
over
20
requests.
You
review
any
particularly.
You
might
just
keep
that
particular
on
this,
like
no
consistency
projects
quickly.
C
So
where
does
github
action
come
in
with
the
action
now,
when
you
automate
github
action
for
your
open
source
repository
you
get
notified,
if
your
slack
or
on
your
email
once
an
event
is
through
that
and
once
somebody
makes
a
pull
request
or
wants
somebody
job
to
comment
on
an
issue
as
a
maintainer
of
a
particular
project.
You
are
aware
that,
yes,
somebody
just
dropped
a
comment.
C
Let
me
go
and
immediately
you
attend
to
the
person,
and
then
that
is
one
of
the
things
that
github
action
takes
care
of
another
organization
and
also
it
says,
standards
for
the
contributors.
So
I
recently
started.
I
contributed
to
layer
five
organization
last
year
and
that
was
like
my
very
first
time
hearing
about
a
sign
off
and
as
a
newbie
to
google.
So
I
was
like,
what's
the
sign
of
this
happening,
whenever
I
explained
it
to
somebody,
I
probably
wasn't
putting
it
in
the
right
words.
C
I
guess
so,
but
whenever
I
explained
that
I
was
expected
to
do
this
particular
thing,
I
was
willing
to
sign
up
somewhere,
like
I've,
never
signed
up
for
creating
a
crew
request
before
you
should
go
and
check
it
again
and
I
kept
getting
errors
whenever
I
create
a
pull
request.
It
gets.
I
kept
getting
errors
until
someone
in
the
community
directed
me
to
the
contributing
guy
that
says
you
have
to
sign
off
before
your
pull
request
is
merged,
so
the
bit
of
action
there.
C
You
restrict
any
contribution
that
is
not
signed
off,
so
this
actually
creates
a
particular
standard
for
your
addition,
your
requisite
representative.
If
this
is
not
done,
then
your
focus
don't
get
meshed
and
also
it
helps
to
maintain
consistency
and
and
then
take
it
to
a
case
of
the
image,
compressing
action.
So
if
you
want
your
repositories
to
have
a
particular
size
of
graphics
or
anything
that
this
request
is
related
to
an
image,
but
then
they
should
have
a
particular
size.
C
C
Now,
whenever
I
go
to
an
open
source
project-
and
I
make
a
contribution
and
this
slide,
but
the
the
bot
the
git
bot
tells
me
thank
you
for
contributing
to
this
project,
it
always
makes
me
so
happy.
I
always
feel
so
happy
and
I
feel
like
that's
that's
how
most
of
the
person
is
contributing
to
the
process.
Projects
feel
because
the
little
appreciation
you
give
them
it
serves
as
an
encouragement
for
them
to
come
back
and
make
another
contribution.
C
So
when
you
have
when
you
automate
your
piece
of
actions
in
a
way
that
is
appreciate
the
members
of
your
community,
it
keeps
the
community
look
welcoming
for
the
contributors.
Also,
it
closes
still
issues.
You
can
always
automate
a
github
action
in
a
way
that
if
an
issue
is
extends
or
exceeds
like
two
weeks
or
or
one
month
or
three
months,
whatever
the
time
frame,
you
truly
may
be
what,
whenever
it
exceeds
six
months
after
it's
been
opened,
a
night
is
created
either
it
has
been
fixed
or
it
has
not
been
fixed.
C
Then
the
issue
should
be
closed
and
then
move
to
skill
issues
yeah
this.
This
is
another
feature
that
github
actually
can
always
take
care
of
and
then
keeps
the
project
at
a
little
action
always
keeps
the
project
active,
because
once
a
contributor
comes
to
the
project
and
sees
that
yeah.
The
last
issue
that
was
created
was
yesterday
and
so
speaks
yet
today
this
morning
and
it
has
been
messed
up,
I'll,
be
wild,
I'm
always
wild
and
you're
like
okay.
This
community
is
like
very
active
and
the
maintenance.
I
update
the
contributors.
C
C
Using
github
action
has
like
so
many
benefits,
but
what
makes
it
stand
out
is
that
github
action
is
free.
It
has
a
great
free
plan,
so
you
don't!
Oh,
you
actually
have
to
pay
for
it
as
an
open
source
organization
over
as
an
open
source
project,
you
don't
have
to
say
it
is
accessible
to
everyone,
and
also
github
actions
are
built
in
github.
C
C
If
you
go
through
the
guitar
market
place,
you
will
see
that
there
are
so
many
github
action
templates,
there's
so
many
different,
seven
different
frame
properties,
so
you
can
always
explore
as
such
the
templates
that
suits
the
purpose
that
you
actually
wanted
to
copy
and
then
include
this
in
your
code
without
any
stress
and
then
another
great
feature
is,
you
have
totally
are
completely
in
charge.
You
can
always
customize
the
workflow
to
your
taste,
then
that
is
wherever
and,
however
you
want,
or
you
can
always
find,
a
new
template
on
the
github
markets
place.
C
C
So
all
you
have
to
do
is
just
get
this
the
code
and
put
it
in
your
copies
and
you're
good
to
go.
You
don't
always
have
to
write
it
all
the
way
again.
Whatever
your
feature
that
you're
looking
for
somebody
must
have
coded
and
tested
it
like
kept
its
open
source
and
little
marketplace
waiting
for
you
to
integrate
it
to
your
project
and
then
it
is.
C
It
makes
everything
automated
so
in
a
way
that
you
get
updated
on
every
event
that
is
triggered
on
that
particular
project.
Like
I
mentioned
earlier,
you
can
always
automate
your
actions
in
a
way
that
you
get
notified
by
slack
for
email,
which
makes
everything
less
of
a
hassle
for
you
as
a
project
maintainer
or
as
a
product
manager,
and
it
eases
stress
which
makes
github
action,
makes
code,
review,
branch
management
and
issue
tracking
a
lot
more
easier
for
the
project.
C
Maintainers
and
also
it
makes
it
sets
a
way
of
making
projects
or
that
arranged
in
an
orderly
manner
and
also
maintains
consistency
across
projects
could
be.
Another
benefit,
is
github.
Action
does
not
select
the
computer
language,
so
it's
available
for
most
programming
languages,
so
whatever
programming
language
is
that
your
project
runs
on
github.
Action
probably
has
the
templates
for
that,
so
it
doesn't
actually
stick
to
just
one
programming
language.
C
Let's
see
python
or
just
have
a
speech
ability
from
those
programming
languages,
and
then
you
can
use
it
for
most
almost
operating
system
operating
system,
so,
whether
you're
using
windows
or
using
mac
or
you're,
going
to
whatever
it
is
that
you're,
using
whatever
operation
system
that
you
run
your
code
or
youtube
action
is
most
it's
most
definitely
available
on
it,
and
then
you
can
use
continuous
deployments
to
other
clouded
platforms
like
on
google,
aws
or
whatever
clouding
platform.
It
is.
C
I
have
project
users,
you
can
always
use
the
continuous
manual
for
it
and
then
one
another
very
good
benefits
of
getting
action.
Is
you
are
totally
and
completely
in
charge
of
your
project,
so
whatever
it
is
that
you
want?
You
should
feel
like
an
action,
does
not
lead
well
enough
for
you.
You
can
always
make
adjustments
to
it
on
them.
C
You
can
always
customize
your
own,
your
own
actions
and
then
put
this
out
there
in
the
market
space
also
for
people
to
like
review
the
github
action
makes
you
completely
and
to
sell
it
in
charge
of
your
project.
So
that
brings
us
to
the
end
upon
this
talk
and
then
thank
you
so
much
for
your
time
and
thank
you
for
listening.
You
can
connect
with
me
via
github
or
twitter,
and
then
I'm
actually
ready
to
take
any
questions
right
now,
if
you
have
for
me,
thank
you
for
listening.
A
All
right,
thank
you,
thank
you,
anita,
and
it
has
been
one
of
my
favorite
presenters
here
on
on
the
meetup.
Thank
you
for
that
presentation.
I
I
did
drop
some
good
actions
on
the
chats
on
youtube,
so
make
sure
you
go
take
a
look
at
some
of
those
actions
and
you
can
browse
through
the
marketplace
website
to
reuse
or
create
more
action,
so
even
beautiful
actions
will
be
a
way
for
you
to
differentiate
yourself
as
an
upcoming,
a
developer.
B
Oh
yes,
thank
you,
so
much
anita
that
was
really
so
deep.
That
was
an
interesting
talk
about
the
github
action
and
I
always
feel
so
glad.
Every
time
I
see
like
feminine
tech
people,
girls,
who
called
women
intake
like
me,
I'm
really
so
happy
to
have
you
here.
So
our
next
speaker,
we
are
going
to
have
catherine
and
kill
she's
from
hashnow
she's
going
to
take
her
through
the
tech
hurling
session.
B
B
E
So
knowing
this
job
red
flag
will
protect
you
from
being
overworked
working
in
underpaying
jobs
and
roles
that
do
not
contribute
to
the
growth.
Additionally,
you
will
also
gain
confidence
in
your
skills
and
by
gaining
power
when
you
learn
how
to
read
between
the
slides.
So
about
a
bit
about
me,
I'm
a
technical
writer,
I'm
a
front-end
developer
and
a
digital
marketing
specialist,
so
just
to
get
started.
Some
of
this
red
flags
to
look
out
for
is
a
job
description
that
overuses
buzzwords.
E
So
these
are
non-descriptive
words
that
do
not
actually
convey
the
purpose
of
the
job
or
the
responsibilities
that
you
will
actually
do
within
the
company.
So
some
of
these
buzzwords,
you
know
someone
will
talk
about.
We
are
a
fast
growing,
disruptive
startup
or
be
ready
to
work
in
an
intense
environment
or
we
are
looking
for
a
growth
hacker
marketer
or
you
know
we
need
someone
who
will
hit
the
ground
running.
So
this
kind
of
words
are
simply
feelers.
They
don't
describe
exactly
what
you'll
be
doing.
E
E
E
E
So
the
the
other
problem
about
companies
that
overuse
these
passwords
is
the
company
may
not
fully
understand
their
product,
their
customers
and
the
impact
the
product
has
in
the
market.
So,
for
example,
someone
might
say
that
they
are
a
fast-growing,
disruptive
startup.
What
exactly
have
they
disrupted?
Have
they
disrupted
a
whole
new
market?
Are
they
leading
in
terms
of
market
share?
E
E
E
Some
companies
are
publicly
listed,
so
you
can
look
at
their
financial
reports
and
press
releases
most
times
they
actually
most
times
they
tend
to
cover
this
kind
of
changes
about
the
company
within
their
company
reports.
So
it's
important
for
you
to
know
if
a
company
conducts
frequent
layoffs
and
restructurings
so
that
you
know
also,
how
long
are
you
going
to
dedicate
time
in
that
company?
Will
you
be
able
to
work
for
one
year?
E
Will
you
be
able
to
work
for
two
years
and
how
much
of
that
time
will
it
contribute
to
your
growth?
So
this
is
an
important.
This
is
an
important
red
flag
to
look
out
for
the
other
red
flag
to
be
careful
about.
Is
a
company
that
has
a
work,
hard,
quote-unquote
a
work
hard
and
play
hard
attitude,
meaning
that
they
expect
you
to
work
hard
and
stretch
yourself,
giving
more
more
work
and
also
spend
more
time
building
a
product
or
or
whatever
job
responsibilities
that
you
have
gotten.
However,
will
they
pay
you?
E
Will
they
compensate
you
just
as
much
as
you
have
worked,
so
most
companies
tend
to
expect
you
to
stretch
yourself.
However,
when
it
comes
to
compensating
you
for
that
much
work,
it
becomes
a
question
of
you
know
they
will
they
will
play
around
with
whether
you
need
to
be
compensated
for
the
match,
work
that
you
have
done
so
working
long
hours
on
occasion
is
okay,
because
sometimes
you
have
tight
deadlines
or
you
know
you
want
to
work
long
hours
out
of
choice.
E
However,
a
healthy
work,
life
balance
should
be
the
norm
in
a
company
rather
than
the
exception,
so
to
get
the
kind
of
work-life
balance
and
culture
a
company
has.
During
your
interview,
you
can
ask
your
interviewer
if
they
expect
you
to
be
on
call
after
official
working
hours
and
on
weekends,
and
if
you're
expected
to
work
after
hours
and
on
weekends,
are
they
going
to
pay
you
over
time?
For
that
time,
the
other
thing
you
can
ask
to
gauge
the
kind
of
culture
they
have
is
you
can
ask
them?
E
E
Let's
say
you're
the
type
of
person
who
likes
to
clock
in
and
clock
out
exactly
as
what
your
contract
states.
So
it's
important
for
you
to
know
this
kind
of
detail
so
that
you
don't
walk
into
a
an
environment
where
they
expect
you
to
walk
beyond
the
official
hours.
They
expect
you
to
work
beyond
official
hours,
and
that
is
not
what
you
thought
you
were
going
to
get.
E
E
E
So
if,
let's
say
it's
22
days,
and
they
are
getting
back
to
you
after
60
days,
that
shows
you
that
that
company
is
quite
indecisive
or
they
are
disorganized
or
they
are
unable
to
make
decisions
quickly.
So
the
other
red
flag
to
look
out
for
is
a
job
description
that
has
unrealistic
expectations,
especially
within
the
tech
community.
You'll
find
a
job
description.
That's
talking
about.
We
need
someone
who
is
a
front-end
and
back-end
developer.
We
need
someone
who
owns
the
the
whole
software
development
process.
E
You
know
that
might
be
unrealistic,
because
if
you
expect
one
password
to
own
the
whole
software
development
process,
are
they
being
given
the
necessary
resources
to
make
sure
that
that
process
is
completed
in
good
time
if
they
expect
a
full
end
and
a
back-end
developer
all
in
one
do
they?
Are
they
also
paying
you
for
your
worth?
So
this
is
important
for
you
to
look
out
for
because
we've
had
cases
where
companies
will
talk
about.
E
This
is
an
entry-level
job
that
requires
five
years,
experience
that
isn't
realistic
or
jobs
that
require
six
years
experience
in
a
specific
language,
yet
that
language
was
that
language
or
framework
was
released
five
years
ago.
So
that
shows
you
also
that
in
as
much
as
they
have
high
expectations,
they
do
not
fully
understand
exactly
what
they
are
interviewing
for.
So
this
is
another
red
flag
to
look
out
for
so
that
brings
me
to
the
end
of
red
flags.
E
To
look
out,
for
these
are
not
all
the
red
flags
that
are
available
there
whenever
you
go
for
an
interview,
make
sure
to
just
do
your
due
process
to
understand
the
company
that
you're
working
for
and
the
expectations
that
they
have
of
you
for
that
particular
role
and
also
the
kind
of
feedback
they
get
from
customers
and
even
former
employees,
so
that
you
get
the
kind
of
culture
that
you
are
working
in.
So
on
the
other
hand,
we
have
the
red,
the
green
flags.
E
What
are
the
good
things
to
look
out
for
in
a
job
description?
What
does
a
good
job
description
looks
like
so
one
of
the
things
to
look
out
for
is
that
they
give
a
straightforward
summary
of
what
the
company
does,
what
they
need
and
what
they
need
for
that
role.
So
they
give
a
you
know
it's
a
very
straightforward
summary:
it's
not
too
colorful.
E
It
doesn't
have
a
lot
of
buzzwords,
they
go
straight
to
the
point
and
they
tell
you
that
this
is
what
the
company
does.
This
is
the
size
of
what
you
know.
This
is
the
market
that
we
are
working,
and
this
is
the
role
that
we
need
you
to
feel.
The
other
thing
to
look
out
for
is
a
straightforward
breakdown
of
job
responsibilities,
expectations
and
reporting
lines.
So
a
good
job
description
will
tell
you
exactly
what
you're
working
on
not
in
victims.
So
let's
say
you
are
joining
a
company
to
be
a
front-end
developer.
E
They
will
state
the
kind
of
frameworks
that
you
want,
that
you'll
be
working
with
the
kind
of
languages
that
you'll
be
working
with
what
they
expect
from
you,
and
also
the
reporting
lines.
Will
you
be
reporting
today?
Technically,
it
will
you'll
be
reporting
to
the
product
manager,
so
they
will
be
very
clear
on
that.
The
other
good
thing
to
look
out
for
is
they
expect
they
request
for
reasonable
qualifications
that
are
commensurate
with
their
responsibilities.
E
So
if
they
expect
a
you
know,
seven
years
experience,
the
responsibilities
also
match
the
kind
of
qualifications
they
are
requesting
for
the
other
thing
to
look
out
for-
and
this
is
a
bonus
companies
that
list
benefits
and
and
and
and
and
packs
that
they
offer
so
a
company
that
lists
paid
time
off
growth
opportunities
available,
medical
cover
paid
incentives.
This
is
a
company
that
understands
that
they
are
trying
to
attract
the
best
talent
and
they
also
understand
that
a
job
description,
a
job
ad,
is
a
two-way
street.
E
It
is
not
just
you
know,
a
company
telling
you
why
we
need
you
and
and
telling
you
the
responsibilities
that
you
will
be
doing.
They
will
tell
you
the
responsibilities
they
have,
what
they
expect
and
also
what
you
can
expect
from
them,
because
they
understand
that
it
is
a
mutually
beneficial
relationship.
E
And
finally,
the
other
thing
to
look
out
for
is
a
job
description
that
does
not
include
non-descriptive
qualities
right.
These
are
things
like
you
know,
a
company
that
is
asking
for
people
who
are
determined
or
someone
who
is
a
self-starter,
a
hard-working
person.
These
traits
do
not.
They
do
not
describe
much
right,
anyone
can
be
hard-working.
E
E
I
hope
that
this
tips
will
help
you,
as
you
apply
for
opportunities
out
there
and
also,
as
you
go
on
to
your
interview
process,
always
try
to
research
as
much
as
possible
and,
of
course
be
prepared
and
have
all
the
information
that
you
need
so
that
you
can
get
the
best
offers
for
your
skills.
So
thank
you
for
your
time
and
I
wish
you
a
good
day
and
a
good
evening
ahead.
Thank
you.
E
A
A
Yeah,
I
was
just
saying
that
software
engineers
are
incredibly
important
for
the
whole
world
right
now,
I
was
someone
said
a
long
time
ago
that
software
is
eating
up
the
world.
So
if
you
walk
in
the
it's
space,
if
you're
a
software
engineer,
your
skill
set
is
extremely
valuable,
so
you
shouldn't
be
getting
an
entry-level
job
with
five
years
of
experience
right.
So
if
you
see
a
job
description,
that
is
talking
about
you're,
getting
an
entry-level
dev
job
and
you
have
five
years
of
experience-
that's
a
red
flag,
so
you
should
definitely
learn
about.
A
You
know
the
prevailing
compensation
in
your
market,
whether
you're
in
kena,
kenya
or
nigeria,
or
in
egypt,
make
sure
you
understand
what
you
what
you're
worth
and
make
sure
you
get
what
you're.
What
and
don't
don't
fall
for
these
tricks.
You
shouldn't
you
shouldn't,
be
doing
all
the
job,
doing
backhand,
front-end
and
doing
no
kind
of
software
development
and
you're
getting
paid
as
as
a
junior.
There
so
definitely
understand
your
work
and
make
sure
you
you
get
paid
for
your
work.
You're
very,
very
important.
A
Github
is
here
to
make
sure
that
you
have
the
resources
you
need
there's.
A
lot
of
almost
everything
we
have
on
github
is
available
for
free
to
to
open
source
software
development.
So
really
really
thank
you,
catering,
and
I
want
to
thank
all
the
other
speakers
that
gave
us
a
lot
of
wisdom
today,
anita
zach
and
catherine.
A
Thank
you
every
one
of
you
guys,
and
so
we
do
this
meet
ups
every
month,
so
there
will
be
another
meet
up
in
june
and
after
now
we
want
to
go
quickly
into
zoom.
If
you
have
any
questions
for
any
of
the
speakers
that
we
have
here
followed
the
link
on
oh
yeah,
you
cannot.
If
you
also
want
to
be
a
a
speaker
for
any
of
this
made
up,
you
can
send
your
proposer
what
you
want
to
talk
about
what
topics
on
relating
to
any
given
technology.