►
Description
Whether you're someone looking to make their first contribution to open source, or you're on a dev team trying to improve the quality and time to ship of your code, this video is for you.
@Eddie Jaoude and Andrea Griffiths take us on an intense discussion about the major whys and hows of open source software, especially when you just want to get things done. More than just "how do I contribute" or "how do I use open source" the two of them really dig into the thoughts and processes that are necessary pre-requisites before contributing to or consuming software.
If you've been following along with Demo Days, we've primarily focused on deep dives into specific GitHub product features, but this time around we've switched things up to focus on the fundamentals of open source...but perhaps not in the way you might expect.
In these videos, we're going even further down this train of thought and talk about the best ways we know how to make open source a viable and effective partner... and help you ship even more amazing code than you thought possible.
For contributors:
2:02 - Intros and start of program
3:38 - Discussion start
6:23 - First contributions
9:23 - How can you do open source professionally? Why would companies embrace or run away from open source
12:57 - Why is being welcoming so important to you? What difference does it make to the code?
15:14 - The importance of checking assumptions and fresh 👀
19:00 - How to get strong references for your work
24:05 - How to get a job at company X?
43:00 - Preventing burnout
For companies:
20:51 - How and why should companies consume open source?
24:35 - How to save time and money building an open source team
28:43 - Using open source on purpose instead of by accident
31:59 - How to open source sustainably?
37:10 - How do I sell open source to my boss?
44:23 - How can companies make money with open source?
48:14 - When is the right time to open source a project? (+ keys to security)
51:00 - "But we're not a tech company." The future of work.
54:06 - Is open source more or less secure than closed source?
59:29 - How can open source be monetized?
1:00:48 - It's not just about evaluating code quality
1:05:01 - Shortening development cycles with open source
1:08:35 - Non-code contributions
1:08:14 - Upcoming events
twitter: @eddiejaoude
github: https://github.com/eddiejaoude
GitHub Virtual Events:
https://www.meetup.com/GitHub-Presente/
https://www.meetup.com/GitHub-Africa/
https://www.meetup.com/github-planeta/
A
B
Thank
you
aj.
What
a
warm
welcome!
I
love
that
thank
you
and
thank
you.
Everyone
who's
tuning
in
to
watch
this
very
special
edition
of
demo
days
and
special
edition
special
guest.
I
mean
we
are
joined
today
by
the
one
and
only
eddie,
judo
eddie.
Thank
you
for
being
here.
I'm
so
happy.
I've
been
a
fan
of
yours
for
a
very
long
time,
as
I'm
sure
there's
many
people
in
the
audience
who
are
also
big
fans
of
your
work,
you're,
a
fantastic
mentor
coach.
B
Every
time
I
see
your
followers
interacting
they
do
it
with
such
just
huge
respect
and
thoughtfulness,
and
I
think
that
all
comes
from
you
and
your
influence
and
impact
on
them.
So
super
excited
to
have
eddie
here
with
us
today
and
he's
been
a
professional
developer
for
15
years
and
he's
done
all
things
open
source
he's
been
a
contributor,
a
participant,
a
collaborator
he's
encouraged
others
to
start
their
open
source
journey.
So
thank
you.
Thank
you
for
being
here.
B
C
I'm
fine.
Thank
you.
Thank
you
so
much
for
that.
Warm
welcome,
like
it's
amazing
to
be
here.
We've
been
geeking
out
for
so
many
years
on
twitter,
so
it's
great
to
finally
geek
out
with
you,
like,
I
would
say
in
person,
but
not
in
person,
but
like
virtually
in
person
and
to
geek
out
with
your
audience
and
community,
I'm
seeing
the
chat
just
going
like
crazy,
and
it's
just
amazing
that
we've
got
people
interested
in
open
source
from
all
around
the
world.
So
I'm
super
excited.
I
can't
wait
to
hear
everyone's
questions.
B
Thank
you
eddie
awesome,
so
I
have
some
questions
because,
like
I
said,
I
am
also
a
fan,
so
I
have
my
own
questions
and
then
we'll
we'll
grab
some
questions
as
well
from
the
audience
so
start
thinking
about
what
you
want
to
know
about
eddie
about
open
source
about
github
and
just
dropping
together.
So
I
I
read
this
quote
from
I
mean
I'm
gonna
age
myself
right
now.
B
It's
from
the
cathedral
and
the
bazaar
and
yeah
that's
a
very
old,
now
old
is
a
very
experienced
collection
of
essays,
and
it
has
like
really
one
quote
that
stuck
out.
That
said
that
every
good
work
of
open
source
software
starts
by
scratching
a
developer's
personal
niche,
and
I
can
attest
to
that
in
that.
B
The
way
I
came
into
this
world
is
because
I
wanted
something
that
didn't
exist
and
I
wanted
to
try
and
figure
out
how
to
make
it,
and
I
think
that
it's
true
for
many
of
us
who
get
involved
into
open
source.
Looking
for
that
collaboration
and
to
learn
so
eddie.
Can
you
tell
me
like
what
was
your
first
thing
that
you
did
in
the
operations
world
like
what
was
the
itch?
Was
it
an
itch.
C
C
C
You
know
finally
got
you
know
100
100,
stars
or
200
stars.
Even
I
think
facebook
contacted
me
because
of
the
project
and
and
so
forth,
and
just
I
was
like
open
source
is
amazing
and
github
have
really
changed
the
landscape
and
lowered
the
barrier
for
everyone
to
to
get
involved,
which
is
what
I
love.
I
can't
wait
till
we
dig
deeper
into
that
shortly
as
well.
B
There
you
go,
I
mean
that
would
have
been
so
maintainer
tired,
trying
to
figure
it
out,
and
but
you
did
that
so
and
you
did
it
in
a
way
that
wasn't
nearly
as
user-friendly
as
it
is
now
with.
You
know:
github,
cli
and
desktop
and
calm
so
kudos
to
you.
Thank
you.
I
appreciate
those
very
very
valid
contributions,
so
you
scratch
the
itch
you
started
to
contribute
you
I
wanna
dare
say,
fell
in
love
with
open
source.
I
definitely
fallen
in
love.
B
B
You
know
you're
a
consultant
and
you
do
things
that
involve
some
open
source
aspects,
so
I
just
wanted
to
know
like
what
do
you
think
an
open
source
professional
is?
Did
you
see
yourself?
Did
I
make
an
assumption?
Did
you
see
yourself
as
an
open
source,
professional
and
then
just
kind
of
take
me
a
little
bit
through?
How
do
you
use
open
source
code
in
your
day-to-day
work?.
C
Okay,
I
think
we've
got
a
few
questions
in
there.
So
if
I
go
off
track,
you
know
bring
bring
me
back.
So
I
think
there
are
so
many
people
that
are
open
source
professionals
without
even
realizing
and
you're
right.
I
would
call
myself
an
open
source,
I
suppose
professional
I'm
a
consultant.
I
do
help
companies
understand
the
benefits
of
open
source.
C
I
do
this
by
diving
in
into
their
current
understanding,
because
different
companies
are
along
the
journey
at
different
points
and
they
have
a
different
understanding,
and
you
know
some
people
think
I
mean
just
a
side
note.
Some
companies
think
that
by
making
their
project
open
source,
their
data
is
going
to
be
publicly
available.
Things
like
that.
C
I
mean
everyone
eventually
gets
the
bug,
I
think,
and
they
go.
You
know
what
this
open
source
is
awesome.
There
are
so
many
benefits
again
we'll
dig
into
those
benefits
shortly,
and
I
just
I
just
I
just
love
doing
that
and
for
me
ever
since
kind
of
you
know,
github
came
about
and
changed
the
landscape
ever
since
I
started
working
as
a
consultant
in
the
open
source
space.
To
be
honest,
I've
never
worked
a
day
in
my
life.
C
Really
I
love
what
I
do,
because
if
I'm
working
for
an
open
source
project
on
the
side
or
working
with
my
awesome,
eddie
hub
community,
I'm
wearing
a
mascot
at
the
moment
or
rabbit
and
it
to
me
it's
the
same.
I
just
feel
I'm
collaborating
with
people
from
all
around
the
world
who
have
different
backgrounds,
different
skills,
different
experiences,
different
yeah,
just
so
many
different
points
of
view,
and
I
can
learn
so
much
for
them.
C
B
No,
I
think
you
got
it
all.
Actually
I
wanted
to
know.
Did
you
consider
yourself
an
open
source
professional
and
how
do
you
use
it
in
your
daily
life
and
what
you
share
is
so
important.
It's
such
a
great
misconception,
sometimes
of
industry,
that
if
you
open
source,
if
you
use
open
source
you're,
you
know
someone
can
just
come
and
take
all
your
code
and
steal
your
business
idea.
B
B
That's
one
of
my
favorite
things
about
open
source.
The
fact
that
I
can
interact
with
folks
in
korea
and
africa
and
russia,
like
everywhere.
We
have
an
opportunity
to
collaborate
on
a
project,
so
you're
working
with
the
best
people
in
the
world
and
that's
really
really
unique.
So
I
love
that
as
an
open
source
professional
as
someone
who
is
obviously
been
part
of
the
open
source
ecosystem
for
a
long
time.
I've
noticed
as
part
of
eddie
hove
and
hey
shout
out
to
eddie
hub
everybody.
B
Your
community
is
awesome.
These
folks
obviously
have
come
to
you
and
you
do
more
than
just
mentor
and
coach
about
open
source.
You
do
many
other
things
with
this
community,
but
I
don't
know
like
why
do
you
think
it's
important,
especially
to
hone
in
to
encouraging
people
welcoming
them
into
open
source,
welcoming
them
into
exploring
the
ways
that
they
can
use
open
source?
As
a
professional
like
why?
Why
did
you
hone
into
that.
C
I
just
felt
it
was
my
calling
and
I,
when
I
collaborate
with
other
people
and
I
can
learn
from
them-
it's
just
amazing.
I
mean
because
the
eddy
hub
community,
we
don't
focus
on
code,
and
that
sounds
strange,
and
so
let
me
explain-
and
we
say
collaboration
first
code,
second,
because
if
we
think
about
it,
we
raise
an
issue
first
on
a
project
and
that's
a
discussion
point.
We're
going
to
discuss,
discuss
our
idea,
what
we're
going
to
changes,
we're
going
to
make
etc
and
so
on.
And
so
that's
that's
collaboration.
C
That's
communication,
that's
really
important
and
then
one
person
will
or
two
people
will
go
and
make
those
changes
and
then
they'll
raise
a
pull
request
and
that
pull
request
is
like
an
issue,
but
it's
got
code
or
code
changes
or
documentation,
changes
or
test
changes
attached
to
it,
and
that
again
is
starting
the
conversation
on
the
changes.
So
we
have
an
issue
that
starts
a
conversation
before
any
changes,
and
then
we
have
a
pull
request.
That
effectively
starts
the
conversation
on
the
changes
that
have
been
made
and
then
more
changes
may
happen.
C
You
know
more
issues
might
get
raised,
some
more
ideas
and
so
on.
So
it
is
mostly
collaboration
and
communication
first
and
you
know
kind
of
code,
documentation
and
tests,
and
so
on.
Those
changes
are
kind
of
second
and
we
can't
build
projects
by
yourself.
Well,
we
can,
but
there's
only
so
far
we
can
go
there's
only
so
many
hours
in
a
day
days.
In
a
week,
we've
all
got
family.
C
We've
got
work,
we've
got
you
know,
so
many
other
commitments
that,
by
collaborating
on
open
source,
we
can
really
help
each
other,
like
I
see
with
so
many
of
our
community
projects
in
the
eddy
hub
community
that
I
might
raise
an
issue
or
raise
a
pull
request
and
I
wake
up
in
the
morning
and
it's
already
been
reviewed
by
four
or
five
people,
and
I'm
like.
I
didn't
think
about
that
such
a
great
point
of
view,
and
even
some
people
say
I
want
to
get
involved,
but
you've
got
over
15
years
experience.
C
And
how
can
I
review
your
work?
Oh,
my
god,
you
can
review
my
work
because
your
point
of
view
will
add
so
much
value
and
it
would
just
add
so
much
value
because
there'll
be
things
that
I
didn't.
I
didn't
think
of.
I
missed,
or
I
just
assumed
it
worked,
so
it
works
I
kind
of
moved
on
and
when
someone
questions
it
I
might
think.
Well,
actually
it
works,
but
can
it
be
improved?
Can
it
be
made
more
clear?
I
mean
to
give
a
concrete
example.
Many
years
ago
I
think
projects
have
stopped
doing
this.
C
A
lot
of
projects
said
hey
to
contribute
or
to
get
started
on
our
project,
get
clone
our
project
and
then
I'll
use
a
node
project
as
an
example,
npm
install
and
so
many
people
were
talking
about
well
I've
cloned
the
project
step,
one
I've
done
step
two
and
it
says
package.json
not
found
and
it's
like.
Oh
you
got
a
cd
into
the
directory,
but
everyone
just
on
the
project
made
the
assumption
that
that's
a
given
and
we
shouldn't
make
assumptions.
We
should
be
inclusive
and
show
that
step
one.
You
need
to
clone
it
step.
C
I
love
saying
to
them.
What
do
you
think
of
this
project?
What's
it
about,
and
and
what
do
you
think
and
I'm
like?
Aren't
you
gonna
give
me
like
an
introduction?
It's
my
first
day,
I'm
like
no,
because
if
you
can't
understand
what
the
project
is,
there's
nothing
wrong
with
you
there's
something
wrong
with
us
in
our
project
and
we
can
make
it
better
by
you
asking
questions
for
the
next
person
so
with
open
source
it
can
just
kind
of
get
better
and
better.
C
Every
time
someone
has
a
look
at
the
project
like
forget,
making
huge
feature
contributions
just
by
getting
involved
and
asking
a
question.
They
are
adding
value
and
I
think
that's
what
software
development
and
open
source
is
about.
Is
it's
about
adding
value
to
the
project
kind
of
job
titles
years.
Experience
to
me,
don't
mean
anything
anymore.
I
interview
for
you
know
high
street
banks.
I
interview
government
departments
in
the
uk
and
for
me,
experience
kind
of
doesn't
really
matter
it's
like.
B
B
Well,
do
some
tests
check
out
the
docs
see
if
there's
steps
missing,
like
you
just
mentioned,
that
is
so
valuable,
sometimes
when
you're
looking
at
something
for
a
very
long
time,
you
kind
of
tend
to
put
blinders
on,
and
it's
so
nice
to
have
a
fresh
of
like
pair
eyes
to
come
in
and
say
yeah,
you
say
to
go
there,
but
that
doesn't
exist.
So
what
do
we
do?
So
that's,
that's
super
unique
and
you
know
so
many
advantages
to
collaborating
this
environment.
You're
augmenting
the
open
source
ecosystem
you're,
making
it
better
for
everyone.
C
To
be
honest,
I
just
you
know,
planted
the
seed
and
the
community
have
just
really
run
with
it.
I
mean
we
have
things
like
we
talk
about
our
language
to
be
inclusive,
like
we
don't
allow.
You
know,
hey
guys
in
the
chat
people
you
know
kind
of.
We
have
a
bot
that
checks
or
other
one.
What
someone
else
will
say,
do
you
mind
being
more
inclusive?
You
can
say:
hey
folks,
hey
people
simple
things
like
that.
C
We
kind
of
usually
just
kind
of
it's
like
water
for
ducks
back
and
I
think
that's
kind
of
really
helped
our
community
grow
and
become
become
stronger
and
I
love
it
when
you
know
people
help
each
other
like,
for
example,
the
amount
of
notifications
I
get
on
twitter
and
and
linkedin
or
people
saying
hey
eddie.
Can
you
write
me
a
reference
and
it's
like
I've
never
spoken
to
you.
I
don't.
I
don't
know
you
I've,
you
know.
C
B
I
love
that
listen
up
folks.
This
is
a
good
opportunity
if
you've
never
contributed
or
if
you're
thinking
about
it.
I
think
it's
key
to
find
a
friendly
community,
and
this
is
what
I
love
like.
They
know
js
folks
and
python
folks
they
have
just
fantastic,
strong
communities
that
are
so
friendly
to
beginners
right.
So,
if
you're
a
bit
hesitant
about
diving
in
they'll,
guide
you
and
help
you
and
that's
awesome,
so
everyone
check
out
eddie
hub
for
sure.
B
Well
so
beyond
the
independent
individual
contributions,
these
things
that
we're
doing
that
are
meant
ecosystem
for
everyone.
I
want
to
talk
a
lot
a
little
bit
about
the
role
of
open
source
in
you
know,
mode
of
the
organizational
and
company
enterprise
space
I
mean
I,
I
would
dare
say
that
most
of
the
top,
I
guess,
top
quality,
maybe
companies
in
the
world
those
protocols
really
take
off
when
they
start
contributing
to
open
source
for
such
as
being
consumers,
because
you're
also
helping
solve
the
problems
and
make
the
open
source
project
better.
B
You
know,
contributor
and,
and
you
love
what
you
do
and
then
hello
if
you
can
get
paid
to
do
it,
that's
even
better,
but
I
wanted
to
just
hear
a
bit
about
your
experience
with
companies
hear
about
how
you
have
helped
and
understand
what
the
consumption
of
open
source,
how
to
create
sustainable
relationships.
Did
you
ever
encourage
companies
to
actually
be
contributors,
and
not
just
consumers,
so
just
a
bit
about
the
relationship
that
you
had
there?
If
you
could
perfect.
C
Question
I
love
that
it's
great
to
look
at
the
other
point
of
view
as
well.
Absolutely
so
I
encourage
all
my
clients
to
open
source
their
projects,
because
I
really
believe
they've
all
got
something
that
they
could
open
source
and
the
benefit
to
them
is
is
massive,
and
you
know
they
don't
really
quite
understand,
as
I
briefly
mentioned
before,
they
think
their
data
is
part
part
of
their
code
base
and
it's
not,
and
they
can
benefit
so
much
one,
because
the
quality
of
the
project
will
massively
increase
just
by
open
sourcing
the
project.
C
Even
if
it's
documentation,
if
it's
you
know
the
front
end
back
end
full
stack,
doesn't
matter,
it
will
improve
massively,
because
the
people
that
they're
paying
their
employees
to
to
work
on
the
project
will
automatically
just
pay
more
attention
to
the
detail,
because
they
will
think
well,
I'm
putting
this
out
there.
You
know
my
peers
are
gonna,
see
it
a
future
employer.
C
You
know
future
colleagues,
they
they'll
be
a
bit
more
kind
of
proud
of
their
work
and
it's
not
gonna.
Take
any
more
effort
to
just
pay
that
little
bit
more
attention
to
it.
So
the
quality
straight
away
goes
up.
So
when
you,
when
you
get
go
for
code
review
within
the
team,
when
it's
propriety,
you'll
see
a
lot
of
when
it's
closed
source
you'll
see
a
lot
of
kind
of.
C
You
know
the
the
format
it's
not
consistent
with
formatting
or
something
like
this,
whereas
when
you
make
that
project
open
source
as
a
company,
people
will
make
sure
it's
consistent
because
they
don't
want
to
get
all
these
comments
on
their
pull
requests.
And
it's
not
about
not
having
comments
on
the
pull
request.
It's
about
having
the
more
valuable
comments,
so
I
think
from
what
I've
seen
in
my
experience
with
you
know.
C
Clients,
like
I
said
you
know,
big
big
companies
down
to
you
know
startups
that,
after
a
while,
you
kind
of
get
comment
fatigue
and
if
you
you
first
notice,
the
small
things
and
you
mention
those
and
after
a
while,
you
think,
okay,
I've
put
10
comments,
can't
put
any
more
it's
it's.
It
doesn't
feel
right,
but
you
might
be
missing
out
on
on
security
improvements
efficiency.
C
Look
good
to
me.
Look
at
me
with
no
comment.
People
want
to
add
so
much
value
and
that's
great
and
then
from
that
they
can.
These
businesses
can
get
the
community
getting
involved.
So
if
I
want
to
work
for
company
kind
of
ex,
you
know
a
good
way
for
me
to
get
on
their
radar
is,
to
you
know,
get
involved
in
their
open
source
project.
C
So
therefore,
if
I
do
apply-
or
they
might
reach
out
to
me
and
we'll
get
back
to
that
in
a
second,
then
you
know
when
that
when
my
cv
or
however
it
works,
goes
to
the
hiring
manager,
they'll
say
I
recognize
this
name.
It's
come
up
in
our
github
repo,
quite
a
lot
right.
They
know
our
project,
they
know
how
we
collaborate.
We
know
their
collaborative
person
that
just
really
helps
your
chances
of
getting
getting
a
job
there.
C
If
that's
what
people
want,
but
also
so
many
of
my
clients
when
they
say
like,
for
example,
I
think
government
department
in
the
uk
they
when
I
first
joined
them
as
a
contractor,
they
said
look
we
want
to
build
the
team,
we're
struggling
to
hire
people
it's
like.
Well,
you
have
an
open
source
project
right.
C
I
said
yes,
why
don't
you
go
to
the
contributors
and,
let's
just
contact
the
first
like
10
or
20
people
on
there
and
see
if
any
of
them,
you
know
want
to
get
paid
for
doing
what
they're
doing
and
even
if
they
only
contribute
like
kind
of
once,
every
three
months
they've
got
used
to
the
kind
of
the
flow
they
can
hit
the
ground
running
and
yeah.
We
built
a
team
of
like
20
people
in
a
few
weeks.
This
usually
takes
months
and
everyone
hit
the
ground
one
running.
C
Everyone
got,
I
mean
half
the
people
felt
like
they
knew
each
other
already,
because
they've
seen
each
other
on
github
they've
never
actually
been
on
a
call
and
spoken
to
each
other,
and
I
think
that
was
a
big
eye-opener
for
my
client
to
say:
wow,
actually,
we
saved
money
on
you
know,
hiring
costs
and
recruitment
costs.
It
was
a
lot
more
efficient.
There
wasn't
this
back
and
forth
for
months
of
interviewing
people.
Yes,
they
still
interviewed
people,
but
you
kind
of
already
knew
what
they
were
like.
C
It
was
more
just
that
kind
of
last
last
check
just
to
make
sure
everything's.
Okay
and
it's
just
easier
for
everybody
for
the
candidate
for
the
employer,
so
there
are
so
many
benefits
I
I
can't
actually
see.
I
struggled
to
see
downside.
I
think
the
challenge
is
getting
people
the
decision
makers
to
to
understand
the
benefits
and
to
understand
the
the
downsides
and
some
of
the
downsides
and
let's
be
completely
open
and
transparent.
C
Here
is,
you
might
get
a
bit
more
noise
on
the
project,
and
that
gives
a
little
bit
of
overhead
to
the
people
on
the
project.
You
know
issues
might
get
raised
that
are
duplicate.
They
might
have
to
then
close
those
and
then
put
a
comment
and
say
I'm
closing
this,
because
it's
a
duplicate
of
another
issue.
But
to
be
honest,
if
I'm
completely
completely
honest
here,
the
community
will
help
with
that
too.
C
I
I
cannot
like
I
cannot
keep
up
with
my
github
notifications
and
that's
a
good
good
problem
to
have,
but
most
of
the
time
when
I
get
to
my
github
notifications,
99
of
the
time
the
community
have
already
put
in
a
comment
saying
it's
a
duplicate
of
this
or
they've
reviewed.
The
pull
request-
and
I
can
just
kind
of
you
know,
delete
the
notification
kind
of
move
on
it's
been
taken
care
of,
and
I
think
companies
don't
realize
that
it's
a
two-way
street
rather
than
just
a
one-way
street.
C
Everyone
can
benefit
because
when
people
contribute
to
a
project,
yes
they're
on
the
radar
of
the
company
or
the
maintainers,
but
they'll
learn
so
much
they'll
learn
how
to
write
a
better
issue:
how
to
write
a
better
pull
request,
how
to
do
something
differently.
I
can
talk
about
this
for
ages
and
and
so
I've
probably
gone
down
a
rabbit
hole
as
always,
but
I
hope
that.
B
Absolutely
I
agree
with
you
a
hundred
percent
when
you
have
skin
in
the
game,
you
are
going
to
pay
attention
right.
You're
gonna
be
a
bit
more
dedicated
about
what
you're
doing,
and
I
love
the
bit
about
the
way
you
review,
pull
requests
from
videos
all
look
good
to
me:
click
because
you're
actually
going
to
pay
attention
to
the
code,
it's
associated
with
your
work.
I
love
to
also
highlight
something
that
you
said
that
I
I
am
a
full
proponent
of
this.
B
If
you're
looking
for
a
job
at
a
specific
company
find
their
open
source
technology,
they
use
contribute
start
getting
your
name
out
there,
because
I
have
seen
people
hire
because
of
that
it
happens
just
find
out
and
if
you're,
at
a
company
right
now
and
you're
wanting
to
learn.
Some
new
technology
then
find
some
open
source
project
that
your
company
is
using
as
a
dependency
and
then
propose
it
as
work
you're
still
getting
paid,
but
you're
now
learning
new
tech
and
you're
contributing
to
a
project
that
will
make
your
company
even
more
successful.
B
So
there
are
so
many
things
that
can
really
accelerate
the
way
that
businesses
work.
When
they
adopt
open
source,
so
that's
really
really
cool.
I
appreciate
you
like
really
sharing
in
depth
how
to
and
why
it's
important
now
that
we
talked
a
little
bit
about.
You
know
why
it's
important
for
companies
to
embrace
it.
Oh,
and
let
us
not
forget
that
you
definitely
can
find
better
developers
when
you're,
focusing
on
open
source
too,
for
the
reasons
you
mentioned
right.
These
people
are
already
doing
the
work.
They've
been
there.
They
know
how
you
work.
C
I
think
most
companies,
what
I've
noticed
with
my
clients
is
a
lot
of
them.
Don't
realize
that
they're
actually
already
consuming
open
source,
so
they're
already
kind
of
in
that
world,
which
I
think
is
so
interesting.
So
many
say:
oh
no,
we
we
don't.
We
don't
do
anything
open
source.
You
know
we
don't
use
it.
We
don't
contribute
to
it's
like
your
entire
project
is
built
with
open
source
projects.
Have
you
paid
for
one
license?
No
everything
is
open
source.
C
Why
not
benefit
more
from
from
that
community
and
and
then
it
kind
of
does
open
their
eyes
if
they
think
really?
Oh,
I
didn't
know
that
we
were
already
kind
of
consuming
it.
Even
some
of
my
clients
are
strict
in
kind
of
you
know
the
banking
space
they
they
say.
Okay,
yes,
we
can
use
open
source,
we
want
to
use
open
source,
but
we
have
to
check
the
licenses
just
to
make
sure
that
you
know
we're
not
liable
for
anything
in
the
future,
et
cetera
and
that's
fine.
C
That's
again
why
it's
really
important
for
every
open
source
project,
be
it
from
someone.
Who's
got
a
small
project
to
a
company
who's
open
sourcing,
their
project
to
have
an
open
source
license
that
that's
really
clear.
So
people
can
you
can
use
it,
and
if
companies
want
to
check
that's
that's
great,
it
means,
like
you,
said:
they've
got
skill
in
the
game
and
they're
thinking
right:
okay,
I've
gotta
be
fully
invested
in
this
and
I'll
be
I'll
struggle
to
find
a
company.
C
C
B
Yeah,
no,
please
please
do
we're
just
having
a
conversation
here,
so
I
love
the
just
like
genuine
interactions.
That's
awesome!
So
I
I
really
appreciate
what
you
said,
because
yeah
you're
right,
a
lot
of
companies
are
not
don't.
Have
that
clear
understanding
of
what
they're
consuming
and
now
with
github
and
all
the
security
features
like
there
are
ways
that
you
can
do
things
safely
and
yes,
there
are
companies
that
depend
on
open
source.
I
think
we're
one
of
them.
B
Yet
if
there
was
no
get,
I
don't
think
there'll
be
a
github.
So
it's
definitely
important
to
you
know,
keep
that
top
of
mind
and
there
are
projects
that,
even
for
large
large
companies
they're
not
positive.
Look
at
kubernetes
like
there
are
so
many
just
different
projects
that
have,
even
though
they
started
from
you
know
the
brainchild
of
a
large
corporation.
They
become
something
so
positive
and
just
help
accelerate
progress
for
everyone.
So
it's
really
cool.
It's
a
really
cool
cool
place
to
be
in
so
we
talked
a
bit
about
your
experiences.
B
How
you
kind
of
guide
folks
into
yes,
you
are
consuming.
Let
me
help
you
find
out.
The
licenses
are
okay
and
there's,
obviously
a
different
approach
when
you're
dealing
with
an
enormous
company
or
like
a
whole
sector
of
the
government
like
you,
have
and
then
a
smaller
project
right,
and
so
I
feel
like
for
smaller
projects,
we're
always
depending
on
the
community.
Largely
you
know,
the
maintainers
are
doing
the
work
for
free,
or
maybe
they
have
a
github
sponsors
shout
out
now.
B
Corporations
can
sponsor
open
source
projects
or
eddie
also
is
unsponsored
so
sponsored,
but
you
know,
for
the
most
part,
smaller
projects
sort
of
depend
on
that
individual
generosity
on
the
people
who
are
passionate
about
or
maybe
is
something
that
they
want
to
use
and
they
feel
like
it
could
improve
the
way
they
work
too.
So
what
do
you
think
drives
this
and
like
a
little
bit
beyond
the
yes?
B
I
do
it
because
I
want
to
learn
like
how
can
we
continue
to
maintain
this
sustainable,
smaller,
open
source
projects,
in
a
way
that
you
know
helps
them
grow?
Helps
them
be
part
of
the
community,
have
an
active,
vibrant
ecosystem.
You
know
in
the
face
that
we
have
all
these
large
back
company
projects.
C
I
think
that's
the
the.
I
think
it's
a
great
question
and
I
love
this
question
because
I
think
the
beauty
of
open
source
is
it
levels,
the
playing
field,
there's
no
kind
of
barrier
to
entry.
If
you
know
someone
some,
you
know
young
kid
in
their
bedroom
wants
to
open
source
the
project
and
start
it,
and
you
know
they
could.
It
could
be
the
next
massive
project
that
underpins
so
many.
They
can
do
that,
there's
no
cost
in
vet
investment.
C
You
know
github's
free,
and
so
I
I
really
really
love
that
it's
it
eliminates
that
kind
of
david
and
goliath
scenario,
and
I
think
that's
just
so
important.
It's
the
whole,
it's
inclusive,
open
source
is
inclusive,
and
so,
if
you
people
wanna,
you
know
contribute
to
a
bigger
faster-paced
project
they
can.
If
people
want
to
contribute
to
a
smaller
project,
they
can.
C
I
think
there's
pros
and
cons
to
both
and
everyone
who
gets
involved
will
benefit
like
there
is
no,
it's
not
like,
there's
a
limited
amount
of
benefit
and
then
it's
you
kind
of
got
to
share
it
between
you
all
the
rest,
the
more
we
put
in
the
more
we
get
out.
It's
it's
it's
an
abundance
of
benefit
and
that's
what
I
love
seeing.
C
I
know
that
every
day
when
I
get
involved
in
the
community
or
you
know
open
source
and
so
forth,
I
know
that
I
will
get
twice
as
much
out
of
it
than
I
put
in
because
I'll
meet
new
people
like
I'll
grow.
My
network,
I
will
learn
something
new
or
I
see
a
different
perspective.
I
might
not
do
it
that
way
in
the
future,
but
now
I've
got
an
appreciation
for
their
challenges.
C
You
know
they
might
not
have
a
powerful
enough
machine
to
run
something
or
big
enough
internet
and
it
it
just
gives
us
that
different
different
perspective.
So
yeah,
I
think
you
know
it's
important,
that
projects
are
kind
of
well
maintained
and
and
make
and
make
them
kind
of
inclusive,
like
code
of
conduct.
Licensing
have
maybe
an
issue
template
everything
gets
a
reply.
So
don't.
If
someone
raises
an
issue
or
pull
request,
the
maintainer
shouldn't
just
close
it.
They
should
write
a
comment
if
they
are
closing
it
and
they
they
can
totally
do
that.
C
But
is
it
a
duplicate?
Is
it
some?
You
know
idea
that
doesn't
want
to
be
done,
that's
fine,
but
they
should
put
a
comment
in.
I
think
that
goes
for
kubernetes
elastic,
or
you
know
me
with
my
small,
my
small
project
of
I
don't
know
100
stars
and
50
forks
whatever
it
is,
or
even
zero
and
zero
it
doesn't.
It
doesn't
matter.
C
I
think
it's
important
is
that
we
show
that
we're
being
collaborative
and
that's
that's
why
I
just
love
open
source
and
what
has
done
github
has
done
the
project
is
there
to
solve
a
problem?
It's
it's
not
there
for
any
other
other
reason,
and
if
it
doesn't
solve
that
problem
for
someone
else,
then
they
might
not
use
it
or
they
still
might
use
it
and
still
might
get
involved
with
it
because
they
like
the
idea,
but
it's
not
something
that
they
would
have
thought
of.
C
B
Absolutely
yeah
a
hundred
percent
that
and
beyond
whether
it's
a
small
project
or
not,
I,
the
burden
of
maintainership
is
real
and
you
know
folks
who
are
so
out
in
the
community
and
helping
so
much
do
get
burned
out.
They
get
tired
and,
like
you
said,
you
know
having
that
presence
having
the
template,
making
it
as
simple
as
possible
for
people
to
contribute
right.
I
see
projects
that
are
very
successful
because
they
have
actually
like
a
mentorship
path.
Very
much
like
what
you
do.
Eddie
you
know.
B
If
you
want
to,
we
can
pair
an
apple
request
or
start
here,
and
let
me
know
what
you
think
and
then
you
know
there
are
projects.
I
just
listened
to
this
podcast
not
long
ago,
but
you
remember
the
htop
project.
It
was
a
brazilian
developer
and
he
literally
muted
his
notifications
on
gmail.
That
included
the
word
hey
because
he
was
working
and
living
life
and
trying
to
have
a
work-life
balance,
and
he
was
he
created
that
for
himself
got
it
to
the
point
where
he
felt
like.
B
This
is
good
enough
for
what
I
need.
However,
there
were
many
people
in
the
community
who
loved
it
started
to
want
to
improve
it,
and
then
eventually
this
just
decided.
You
know
what
we're
just
going
to
fork.
It
form
a
group
of
maintainers,
and
now
the
project
keeps
growing
thriving
and
the
original
creator
was
absolutely
delighted.
B
So
I
I
love
that
you
share
that
when
we're
thinking
about
approaching
folks
and
kind
of
just
let's
say
I
want
to
sell
the
idea
to
my
boss
that
we
should
open
source
a
part
of
our
code
or
we
should
open
source
our
documentation
which,
by
the
way
with
them-
or
we
should
you
know,
just
be
a
bit
more
open
about
certain
things
like
have
you
got
any,
I
don't
know
actual
tips,
any
things
that
we
can.
You
know
maybe
lean
on
to
influence
those
decision
makers
beyond
showing
the
pros
and
cons.
B
C
Absolutely
the
documentation
is
a
great
example,
because
so
many
companies
don't
realize
that
the
overhead
of
not
having
open
source
is
massively
higher.
Let
me
give
you
an
actual
concrete
example.
So
there
was
a
mistake
in
the
documentation.
It
was
hadn't
been
updated
with
the
new
version
of
the
proprietary
code
base,
and
so
when
the
the
user
of
the
project
had
discovered
that
they
they
they
sent
in
a
support
ticket
and
by
the
time
it
went
through,
got
to
the
developers.
They
made
the
changes
and
cut
a
long
story
short
by
time.
C
C
The
consumer
gets
it
like
four
weeks
later,
if
you're
doing
like
two
week,
sprints,
for
example-
and
you
are
quite
agile-
most
cases
it's
worse,
but
let's
take
a
kind
of
in
a
good
situation
for
now
four
weeks,
so
the
user
is
missing
out
on
the
benefit,
not
a
single
user
right.
These
are
many
people
and
the
overhead
for
that
ticket.
I
think
we
calculated
it's
kind
of
like
three
people
days
just
to
fix
this.
C
You
know
one
line
because
of
the
way
people
had
to
read
it
check
it
pass
it
on
to
the
next
person
all
the
rest,
and
that
is
that
is
crazy,
whereas
if
they
had
open
sourced
it
rather
than
sending
a
support
ticket,
someone
could
just
send
a
pull
request.
It's
done.
Everyone
benefits
like
immediately
and
when
I
explain
this
to
them
actually
quantified
it.
We
took
a
concrete
example
and
quantify
and
took
them
through
it.
C
C
You
know,
rather
than
looking
at
what
it
is
they're
trying
to
understand,
like
you're,
trying
to
decipher
someone
else's
ticket
rather
than
you
know,
a
line
change,
that's
marked
as
read
and
marked
as
green
that
it
is
what
it
is
right,
trying
to
explain
to
someone
what
the
difference
is
between.
I
don't
know
a
sports
car
and
an
suv
is
harder
than
just
having
showing
someone
about
what
it
is
right.
You
can
see
it
straight
away.
C
It
just
is
what
it
is
and
they
were
like
wow,
and
so
then
they
made
their
documentation
open
source,
and
that
was
them
stepping
in
that
direction,
and
then
yeah
more
and
more
got
open
source
from
that,
like
libraries,
they
had
used
between
their
projects,
they
made
open
source
and,
and
then
it
snowballed
from
there.
So
I
think
yeah
people
companies,
don't
realize
the
the
overhead
of
not
having
open
source.
C
They
think
it's
more
secure,
which
is,
you
know,
completely
wrong,
because
people
are
more
likely
to
commit
private
keys
and
tokens
because,
like
it's,
a
private
repo,
it's
okay,
it's
like!
No,
it's
not!
Okay,
it's
not
when
people
say
I'm
making
my
project
private,
because
I
want
to
commit
some
passwords
or
tokens.
It's
like
there's
no
reason
to
make
it
private.
C
Sometimes
that
helps
because
some
companies
are
so
big
they're
trying
to
open
source
a
project
and
they're
going
through
the
struggles,
but
another
department
is
kind
of
going
through
the
same
struggle
speaking
to
different
people.
I
think
it's
important
to
speak
to
other
departments
and
just
you
know,
work
together
again
collaborate.
It's
just
kind
of
this
whole
thing
is
just
underpinned
by
collaboration
like
collaborate
on
trying
to
get
the
company
to
to
open
source,
a
project
that
benefits
etc,
and
once
you
do
one
it
just
becomes
like
a
lot
easier
to
do.
Two.
C
B
Yeah,
thank
you
so
much
for
sharing
that.
So
definitely
lean
into
that
when
you're
trying
to
sell
it
to
your
company
or
even
adopt
it.
I
saw
a
comment
come
through
someone
that
says
they
do
it.
They
realize
it
on
their
own
company
building
because
they
realize
how
important
it
is.
I
love
it
that
you
touched
on
security
because
it's
so
important
now,
like
developers,
are
only
in
security.
More
and
more
is
shifting,
left
and
yeah.
Why
not?
You
also
just
be
able
to
stop
a
lot
of
these
things
before
they
even
happen.
B
C
I
will
everyone
know
everyone
who
does
know
me
knows:
I'm
like
completely
transparent
as
much
as
I
can
be,
so
anything
just
ask
and
while
everyone's
thinking
of
their
question,
if
I
can
kind
of
give
another
tip-
because
you
mentioned
before
which
I
love
like
you-
know-
mental
health
and
work-life
balance-
and
that's
really
important-
don't
burn
out.
It
is
an
awful
place
to
be
because
it's
very
hard
to
come
back
from
it
and
I
think
people
think
open
source
right.
I
need
to
do
a
hundred
hours
this
weekend
and
it's
okay.
C
There
aren't
100
hours
of
the
weekend,
but
they
get
the
idea.
It's
like
no
there's
no
value
in
there.
It's
like
going
to
the
gym
and
go
I'm
going
to
work
out
for
12
hours.
Today,
I'm
not
going
to
work
out
for
six
months
that
doesn't
doesn't
work.
It's
got
to
be
like
working
out.
It's
got
to
be
like
brushing
your
teeth
little
and
often,
and
if
you
miss
a
day,
because
you
know
someone
in
your
family
needs,
more
attention
is
unwell
or
whatever.
It
is.
C
That's
fine,
nothing
wrong
with
that
at
all,
but
over
the
weeks
over
the
months,
the
benefit
to
the
open
source
project
to
the
community
and
to
yourself
is
just
huge.
So
I
think
companies
sometimes
think
right.
We've
got
to
make
all
our
projects
open
source
in
one
day,
and
it's
just
like
that.
Doesn't
work
like
that.
Just
you
know
pick
one
of
the
smaller
ones.
Try
it.
C
You
know,
you'll,
learn
so
much
from
that
and
yeah,
and
even
people
who
want
to
contribute
to
projects
just
little
and
often
try
and
do
you
know
15
30
minutes
a
day
and
if
you
miss
a
day,
that's
also
fine.
So
I
think
if
you
aim
for
like
a
day
or
every
other
day,
then
you
at
least
do
a
few
times
a
week
and
the
benefit
over
time
will
be
great.
C
C
Question
that
is
a
good
question
yeah.
I
love
that.
So
I
got
a
couple
of
answers
here.
So
one
is,
I
went
to
an
event
before
the
pandemic,
and
so
on
or
many
years
ago
actually-
and-
and
someone
said,
you
should
really
open
source
your
projects,
because
no
one
is
going
to
steal
your
company
idea
because
they
have
their
own
kind
of
silly
company
ideas,
and
you
know
startup
ideas
and
all
the
rest,
and
it's
so
true
that
I
don't
know
of
anyone.
C
Who's
had
their
project
stolen
because
everyone's
got
their
own
ideas
and
want
to
build
their
own
startups,
their
own
projects
and
so
forth
and
people
might
contribute
to
yours,
but
they
don't
seem
to
have
that
mentality
of
wanting
to
see
that
people
want
you
to
succeed.
It's
like
when
you
go
to
a
conference.
You
don't
watch
somebody
standing
up
on
stage.
You
go,
oh,
I
hope
they
mess
up.
I
hope
they
get
this
all
wrong,
you
don't
you
want
them
to
succeed
and
you
want
to
benefit
from
their
knowledge
and
hopefully
connect
with
them
afterwards.
C
I
think
the
same
goes
for
our
open
source
projects.
We
want
our
open
source
projects
from
our
friends,
our
network,
or
even
people.
We
don't
know
yet
to
succeed,
and
so
I
think
you
know,
I
think
I
think
that's
one
thing:
we've
got
to
kind
of
change
the
mindset
of,
and
there
are
so
many
open
source
companies
that
some
have
been
sold
for
millions
or
billions
and
they
seem
to
be
doing
okay-
and
you
know
there
are
loads
of
examples
they
weren't
mentioning
now
any
names.
C
I'm
sure
people
in
the
chat
will
probably
mention
loads,
but
you
know
I
mean
yeah
they're
huge.
I
can
think
of
some
again.
I
want
to
avoid
the
names
to
give
anyone
any
advertisement,
but
some
of
them
have
been
sold
for
billions
and
they're
open
source.
They
they
did
all
right
and-
and
so
I
think
it's
possible
definitely,
but
if
some
companies
are
you
know,
super
super
nervous,
they
shouldn't
stop
them.
Maybe
they
can
open
source,
and
I
have
known
companies
to
do
this.
C
They
could
open
source
90
of
the
code
base
so
that
maybe
the
micro
services,
but
not
the
the
kind
of
the
the
crown
jewels
that
join
it
all
together
for
their
platform
like,
for
example,
netflix.
I
shouldn't
mention
any
names,
damn
it
sorry,
but
they
open
source
a
lot
of
their
a
lot
of
their
projects
and
microservices
and
libraries
and
benefits
they're
doing
okay.
C
Once
you
go
to
someone's
when
you
see
someone's
contribution
on
your
project,
someone
else's
trying
of
go
down
this
rabbit
hole,
you
just
find
out
what
other
projects
they're
working
on
what
other
organizations
they're
doing.
I
think
nick
mentioned
one
of
our
awesome
mods
in
the
chat
mentioned
that
you
can
join
our
github
organization
for
eddie
hub
and
the
great
thing
about
that
is
people
then
can
discover
you
from
our
community
and
vice
versa.
Everything's
a
two-way
street
people
can
discover
our
community
from
your
profile.
C
B
Absolutely-
and
we
are
more
interconnected
than
ever-
and
it's
it's
yeah-
you
definitely
make
connections
and
github
the
home
for
all
developers,
home
for
open
source
with
people
from
everywhere
all
walks
of
life,
and
they
can
bring
different
perspectives
to
your
project,
so
super
important.
I
love
that
collaborative
aspect
of
it.
That's
really
great,
let's
see,
are
there
any
other
questions,
I'm
not
seeing
okay
here
we
when
to
consider
the
closed
source
project
ready
for
open
sourcing
within
a
company
when
oh.
This
is
a
great.
C
Question,
when
are
you
ready
the
day?
The
project
is
thought
about,
or
kind
of
you
know
conceived,
that's
when
it
should
really
go
open
source.
Ideally-
and
I
mean
that
I'm
not
trying
to
be
a
purist
here
or
you
know
anything
like
that-
I
actually
mean
that,
because
one
it
will
be
more
efficient,
two,
it
will
be
more
secure
and
you
may
think:
how
can
it
be
more
secure?
C
Well,
it
can
be
for
two
two
reasons:
one
no
one
will
accidentally
commit
anything
to
the
repo
because
or
if
they
do
they'll
go
reset
that
token
or
something
like
that,
because
it's
on
their
mind
that
it's
public,
whereas
I
see
a
lot
of
places.
Unfortunately,
they
have
to
get
rid
of
all
the
history
from
the
years
of
working
on
that
project,
because
they're
not
sure
if
a
token's
ever
been
committed
and
if
it
has
was
it
reset.
C
So
by
doing
it
by
day,
one
you
are
making
it
more
secure
and
it's
also
more
secure
because
you're
getting
other
eyes
on
it.
The
the
people
in
the
team
are
going
to
be
focusing
more
on
when
they
review
each
other's
work
and
what
they
commit
and
push
up
and
so
forth
so
from
day
one
and
if
you're
doing
it
at
a
later
date,
because
the
project
hasn't
been
open
sourced.
Yet
then
that
is
fine,
but
the
benefits
of
open
source.
C
You
know
hiring
people
higher
quality,
more
efficient
or
efficiency
of
project
is
more
efficient
because
people
start
automating
things
and
other
people
in
the
community
will
start
automating
things
for
you,
github
actions.
It's
a
github
change
the
landscape.
Whenever
it
came
out
like
10
12
years
ago,
github
actions
in
the
last
couple
of
years
has
again
changed
continuous
integration
and
continuous
deployment.
Massively,
it
is
amazing,
and
people
are
automating
more
and
more,
and
I
see
so
many
people
contributing
to
company
projects
or
their.
C
You
know
friends,
projects
just
by
with
a
few
lines
of
yammer
or
config,
because
they
think
well.
They've
got
a
lint
command
that
that
people
should
run
locally.
They
might
forget,
but
they're
not
running
it
on
github
actions.
Yet
well,
you
know
what
a
few
lines
of
yammer
config.
I
can
grab
the
same
command
that
they
run
right
now.
It's
the
amount
of
value
that
adds
is,
is
phenomenal
and
not
to
plug
github
too
much.
C
C
I
haven't
come
across
anything
that
isn't
isn't,
isn't
free
and
they're
all
open
source,
so
you
can
even
fork
if
you
want
to
make
some
changes
for
it
and
customize
it,
but
most
actions
that
you
need
are
already
available
out
there
and
literally
with
copying
and
pasting
some
yammer
config
you're,
going
to
get
huge
benefits
to
your
project
and
again
it
helps
the
quality
and
efficiency,
because
you
get
faster
feedback
rather
than
you
know,
someone
reviewing
your
pull
request
tomorrow.
Actually,
let
me
take
a
step
back
pandemic.
Aside.
C
Pandemic
has
obviously
been
awful
and
terrible,
but
one
of
the
positive
things
is:
it's
brought
our
world
closer
and
open
source
was
doing
that
already,
but
so
many
companies,
like
you,
know,
law
firms
that
aren't
tech
companies,
although
they
actually
are
nowadays
every
company's
a
tech
company
they
weren't
taking
benefit
of
that.
But
I
think
the
the
pandemic
has
made.
People
realize
that
you
know
async
working
remotely
is
is
the
is
the
future
and
the
weight
and
the
way
to
work.
C
I
love
seeing
how
companies
who
are
now
you
know,
might
not
have
a
code
base
or
anything
like
that,
but
they're
using
kind
of
github
projects
boards
to
kind
of
manage
their
their
workflow
and
again,
that's
them
dipping
their
toe
in
in
the
in
the
water
signing
to
people
and
so
forth,
and
so
I
lost
my
trailer
thought
but
automating
everything
async
is
really
important
because
you
know
you
might
make
a
change,
make
a
pull
request.
You
kind
of
go
to
bed.
Someone
else
is
a
different
time
zone.
C
It
takes
three
days
to
get
merged
in
it's
actually
easier
to
turn
for
us
not
to
say
this
is
my
code,
I
own
it.
No
we're
all
here
to
add
value
to
the
project,
and
so,
if
someone
else
is
reviewing
it,
it's
it's
easier
not
to
make
the
comment
probably
easier,
just
to
go
and
make
the
change
merge.
The
pull
request
done-
and
you
know
you
can
put
in
a
comment
still
and
still
make
the
change
there
for
the
person
knows
for
next
time.
B
No,
you
100
correct
about
you
know
like
when
you
shoot
a
dot
when
it
when
it's
the
time
for
the
company
to
be
ready
and
to
tie
that,
together
with
the
last
question,
I
think
that
definitely
the
future
of
businesses
is
very
correlated
with
their
open
source
adoption.
That
is,
a
hundred
percent.
What's
going
to
happen,
and
I
love
what
you
said
about
all
companies
being
software
companies
because
they
are
it
doesn't
matter
what
you
do.
B
You
are
a
software
company,
especially
now
in
this
world
today,
more
than
ever
so
those
were
really
really
great
questions.
Thank
you
to
our
audience.
Let's
see,
is
there
any
other
questions
here
we
are
from
anna.
Do
you
think
security
could
be
compromised
with
open
source
project
wow?
This
is
a
really
good
question
and
actually
in
following
series,
we're
gonna
go
in
depth
on
open
source
and
security,
but
eddie.
Would
you
like
to
like
just
reply
to
that
high
level
that'd
be
great.
C
Sure,
well,
you
know,
github
has
you
know
so
many
tools
already
kind
of
built
in
for
security,
which
is
which
is
super
helpful
and
there
are
third-party
parties
that
you
can
use
to
tie
in.
We
can
have
actions
etc
and
so
on,
and
so
I
think
a
lot
of
companies
will
benefit
from
the
different
eyes
on
on
the
projects
right
away.
Like
I
said
you
know,
developers
or
whoever
is
working.
Any
technical
person
working
on
on
the
project
will
pay
more
attention
to
what
they're
doing
even
their
commit
messages
will
improve.
C
Everything
will
improve,
so
I
think
security
will
get
better
and
also
I
worked
for
another
company
and
we
wanted
to
use
a
third
party
service
to
do
security,
but
by
the
there's,
a
private
project,
but
by
the
time
we
got
the
sign
off
to
have
like
the
20
or
30
per
month
or
whatever
it
was
months
had
gone
by.
So
we
were
losing
the
security
checks
from
this
third-party
provider
that
we
wanted
all
to
get
signed
off
on
like
30
dollars.
C
C
Not
only
will
people
pay
more
attention
to
their
contributions
and
what
they
do,
but
we
could
use
this
third
party
service
for
free
because
it's
free
for
open
source
projects,
so
you
kind
of
it
just
seems
it
seems
crazy,
and
this
company
was
such
a
big
company
that
they
the
reason
why
it
took
so
long.
One
was
a
big
company
and
two
they
struggled
to
sign
off
thirty
dollars.
C
They
couldn't
sign
off
things
that
were
less
than
500,
so
it
was
kind
of
like
really
really
odd
and
on
a
similar
note
I
know
andrea
mentioned
github
sponsors
and
I
know
some
companies
who
want
to
sponsor
people,
which
I
think
is
great.
It's
such
a
you
know
game
changer,
but
some
companies
also
struggle
to
pay
less
than
this.
C
You
know
a
certain
amount,
so
some
people
have
their
tiers
like
one
dollar
25
up
to
25,
etcetera
and
so
on,
but
some
companies
can't
they
can't
justify
the
the
admin
cost
of
of
that
kind
of
cost.
So
just
you
know
bear
that
in
mind.
Have
that
higher
tier?
If
company
wants
to
give
you
more
money
for
your
great
work,
let
them
give
you
more
money
for
it.
C
I
think
that's
really
important,
but
hopefully
it
will
change,
and
on
that
note,
and
I
will
cycle
back
to
the
security,
if
you
do
have
like
ten
dollars
to
give
to
someone
in
open
source.
I
say
this
to
people
who
wanna
kind
of
sponsor
me.
Please
don't
give
me
the
ten
dollars.
Please
just
give
me
the
one
dollar
and
go
give
them
900
to
somebody
else.
I
think
it's
important
to
kind
of
spread
that,
because
the
motivation
that
I
get
from
receiving
one
dollar
or
ten
dollars
is
the
same.
C
I
think,
if
you
can
have
ten
people
get
that
motivation
from
just
getting
that
one
dollar
to
that
person.
I
think
is
really
really
important,
so
yeah
just
like
that,
but
back
to
security,
I
think
it
improves
it.
It
really
really
does
and
I've
even
seen
projects
or
they've
come
by
mistake
kind
of
made
a
security
not
committed
a
token,
but
something
wasn't
very,
very
secure.
They
weren't,
you
know
hashing
the
password
enough
and
all
the
rest
and
someone
in
the
community
just
said.
Look.
I
think
this
is
better.
C
Here's
a
there's,
a
link
to
an
official
documentation.
He
should
use
this
and
do
this
instead
and
the
library
that
you're
using
is
actually
you
know
out
of
date
or
you're,
not
using
a
library
you're
doing
it
manually.
It's
it's
not
great,
it
hasn't
got
the
right,
entropy
et
cetera
and
so
on,
and
it's
like
oh
wow.
Let's
bring
that
back
in.
C
That
wants
it
to
succeed
and
will
point
it
out
to
you,
which
I
think
is
really
important,
but
people
can't
point
out
if
it's
not
open
source
and
companies
again
are
struggling
to
understand
that
they
think
security
by
obfuscation
and
then
just
not
being
aware
of
it,
is
secure
and
that's
not.
That
is
just
literally
putting
the
wool
over
your
eyes
and
just
kind
of
you
know
fingers
it's
like
driving
through.
I
don't
know
a
tight
road
and
closing
your
eyes
looking
down
and
going.
I
hope
it
works.
It's
like
have
your
eyes
open.
C
Have
the
people
like
on
the
side
of
the
road
you
know
kind
of
giving
you
pointers
like
go
a
bit
to
the
left,
go
a
bit
to
the
right
like
parking.
A
car
have
people
next
to
you
like
imagine.
You
had
your
friend
by
your
pa
next
year
when
you
park
in
your
car.
Just
no
I'm
gonna
park
the
car,
but
you
can't
watch
they
can
help
you
like
navigate
back.
If
you
haven't
got
your
cameras
and
parking
sensors
like
we
do
in
modern
day
now,
and
I
think
trying
to
give
an
example.
C
B
B
If
there
are
is
there
another
question,
maybe
folks
are
thinking
about
it
while
they're
thinking
about
it?
I
would
like
to
invite
all
of
you
to
follow
our
new
enterprise
handle
on
twitter.
It's
at
github
ent,
and
this
is
where
you're
going
to
start
seeing
announcements
for
all
the
enterprise
events,
be
it
demo,
training
events
so
just
follow
that
handle,
of
course
follow
eddie
on
twitter
and
all
the
places,
so
you
can
keep
up
with
eddie
hub
and
yeah
definitely
keep
in
touch.
Let's
keep
that
feedback
coming.
B
C
Question
it
is,
and
I
want
to
give
like
two
answers.
Well
definitely:
yes,
like
100,
yes,
it
can
be.
I
mean
I
I
do
it
and
if
people
want
to
kind
of
you
know
see
my
setup,
I
do
it
and
I'm
able
to
you
know,
fund
lots
of
geeky
setups
and
tools,
hi
everyone
and
so
forth.
So
yeah,
it's
absolutely
absolutely
possible
and
one
way,
as
you
mentioned
before,
github
sponsors,
it
is
the
the
the
direct
way
to
to
make
money.
C
That's
the
direct
way
and
there's
you
know,
that's
the
best
way.
I
think,
because
other
services
take
a
big
car.
It
takes
no
car.
I
just
think
it's
phenomenal
indirect
way.
Is
people
get
to
see
your
work
when
clients
come
to
me
or
before
I
was
a
consultant
when
people
used
to
offer
me
jobs,
I
didn't
go
hunting
for
jobs.
C
But
then
they'd
get
like
a
really
good
developer
on
board,
for
example
a
good
tester
or
good
whatever
it
is
business
analyst
project
manager
whatever,
but
they
can't
collaborate.
I
think
the
great
thing
about
github
is
it's
not
just
about
the
changes?
It's
also
about
the
collaboration.
I
know
when
I
interview
for
when
I
help
interview
when
I
interview
for
my
clients,
as
in
I'm
they're,
trying
to
build
a
team
trying
to
help
them
build
a
team
and
so
forth,
I'm
doing
the
interviews
for
them.
C
I
definitely
100
look
at
everyone's
github,
but
I
don't
look
for
what
people
think
I'm
looking
for,
I'm
not
looking
for
how
amazing
is
your
code
today?
No,
I
do
look
at
your
code
today,
but
I
just
want
to
check
it's
better
than
it
was
three
months
ago
just
to
show
that
you're
still
learning
and
moving
forward,
because
you
know
big
spoiler
alert
text
moving
all
the
time
forward,
but
the
one
thing
I
do
look
for
is:
how
do
people
collaborate
with
people
there's
nothing
worse
than
having
someone
who's
a
great.
C
I
know
technical
person,
but
they
can't
collaborate
with
people,
no
no
open
source
project.
No
company
project
is
really
by
one
person.
You
need
to
have
ux,
ui,
testers
developers,
business
or
a
huge
list
of
people,
and
you
need
to
collaborate
with
people.
So
that's
really
really
important
and
again
going
back
to
what
I'm
saying
when
I
interview
people
I
I
can
see
if
someone
contributes
to
open
source
straight
away,
I'm
not
saying
contribute
code.
C
I
didn't
say
that
I
said,
contributes
or
gets
involved
to
open
source
because
they
will
explain
things
very
differently
and
one
of
the
tests
that
I'm
going
to
give
secret
here.
One
of
the
tests
I
do
is
I
ask
people
to
raise
an
issue
on
our
project.
It
might
not
be
an
official
issue,
it
might
be
on
a
bit
of
paper
or
explain
it
to
me,
and
you
can
really
see
the
difference,
because
we'll
have
a
conversation
about
something
I
think
brilliant.
You
you've
thought
of
an
idea
and
improvement.
C
Can
you
raise
the
issue
and
the
people
who
don't
contribute
to
open
source
will
say
following
our
discussion?
I
think
we
should
do
x.
It's
like
great
in
two
days
time.
I
want
to
forgotten
what
discussion
is,
and
there
are
a
lot
of
people
here
who
weren't
involved
in
discussion,
where
someone
who
contributes
to
open
source
will
say
will
quote
you
know
part
of
the
discussion
or
copy
and
paste
it
from
slack
or
disk
whatever.
C
It
is
and
say
you
know,
following
our
discussion,
we
should
make
these
changes,
but
there's
context
there,
there's
not
this
back
and
forth
back
and
forth.
Like
kind
of
you
know,
tennis
table
trying
to
understand
what's
going
on,
and
you
have
like
two
pages
in
this
issue
of
of
just
trying
to
understand
what
the
issue
is
about.
So
it's
very
different
and
companies
look
for
that.
Companies
want
to
hire
people
to
help
that
they
might
even
hire
you
on
a
contract
basis.
Can
you
come
in
and
help
us
write
better
issues?
C
I've
seen
people
in
the
open
source
community
get
hired
just
to
help
that
company
make
better
pull
requests
and
better
issues
in
their
private
project.
And
yes,
of
course,
they
go
in
and
help
and
encourage
them
to
make
it
open
source.
Of
course,
like
that's
a
that's
a
given,
and
so
yes
indirectly,
you
definitely
can
it's,
I
think,
and
more
and
more
over
the
last
15
or
it
hasn't
been
around
15
years.
But
you
know
how
long's
been
around
for
I've,
seen
it
more
and
more
become
more
of
our
kind
of
cv.
C
I
know
that
upsets
some
people
because
they
say
look.
I
haven't
got
time.
I've
got
family,
I've
got
kids,
I've
got
a
dog,
I've
got
unwell,
parents
and
I
I
I
agree
to
be
able
to
contribute
as
much
as
many
of
us
do.
It
is
definitely
a
privilege
to
have,
but
little
and
often
don't
think
of
it
like
you
have
to
do
loads.
I'm
gonna
repeat
this
again,
because
I
think
people
automatically
rule
themselves
out
and
say
look.
C
I
can't
benefit
from
learning
from
open
source
networking
or
to
make
money
from
open
source,
because
I
I
don't
have
the
time
just
try
and
make
you
know
15
minutes
a
day
every
other
day
and
over
time.
That
will
massively
massively
help
and
you
can
even
if
someone's,
got
a
good
project
another
way
to
make
money.
I've
seen
people
do
this,
is
they
can
provide
support
for
their
project?
So
some
companies
use
your
project.
C
You
can
have
a
hosted
version
as
well,
that
they
pay
monthly
to
use
the
hosted
version
and
then
they
pay
for
support
to
use
it.
And
yes,
at
the
beginning,
I've
seen
as
a
company
saying
oh
we'll
host
ourselves.
We
don't
need
support,
we'll
use
documentation,
but
then,
when
they
want
to
rush
really
fast,
like
they've
got
a
deadline
and
I've
seen
this
before
actually
in
a
government
department.
Okay,
can
I
tell
a
quick
story?
Do
we
have
time
I'll
keep
it
short?
I
promise.
C
C
Okay,
this
is
a
true
story.
I
was
working
in
government
department
and
they
said
we
want
to
use
this
library,
but
we've
got
a
really.
You
know
short
time.
It's
this
framework
really
short
time
to
use
it.
So
look.
This
is
not
in
my
team
skill.
If
you
want
to
use
it,
I
think
it's
a
good
decision
for
us
to
use.
It
would
help
us
in
the
long
term,
but
I
think
you
should
get
you
know
one
of
the
contributors
or
maintainers
to
come
and
get
us
up
and
running
in
two
weeks.
C
They'll
save
us,
like
two
months
of
trying
to
get
it
right,
learning
teething
issues.
They
went
yeah
perfect.
If
we
can
save
two
months,
then
no
matter
what
it
costs,
then
that's
fine
and
so
we
reached
out-
and
everyone
said
you
know
we're
kind
of
busy
and
I
was
like
just
throw
more
money
at
them.
They
can
take
two
weeks
off
hopefully
and
help
us
and
they
can
get
money
to
invest
more
into
their.
You
know
personal
life
or
project
whatever
they
want
to
do.
C
I
know
money's
not
the
answer
to
everything,
but
you
know
you
can
kind
of
sweeten
the
deal
a
bit,
and
so
you
know
one
of
them.
Top
five
contributors
said
yep.
I
can
come
for
two
weeks.
That's
what
I've
got.
I
can't
give
you
a
month.
I
can
give
you
two
weeks
we're
like
great
the
two
weeks
from
that
person
who's
an
expert
is
gonna.
Gonna
help
us,
and
I
remember
going
down
to
reception-
and
I
was
I
was
copied
in
some
of
the
emails,
but
I
didn't
look
up
the
person
I
trusted.
C
They
were
one
of
the
main
contributors.
I
think
I
looked
at.
You
know
some
of
their
collaborations
just
to
see
they
can
communicate
with
people
and
so
on,
and
they
they
flew
into
london
from
from
germany
and
for
some
reason
this
is
really
bad
of
me
and
I'm
I'm
so
upset.
This
happened
like
many
years
ago.
I've
learned
a
lot
since
then,
but
when
we
went
down
to
reception
because
top
security
government
department,
I
was
looking
for
someone
older
than
me
because
they
just
seemed
like
such
an
expert
that
I'd
assumed
they
were
older.
C
It
was
a
university
student
who
was
19
and
I
was
like
I'm
looking
for
this
person
and
they
were
like
oh
it's
over
here.
I'm
like,
I
was
just
really
surprised,
just
seeing
someone
who
was
like
you
know
so
young
and
they
were
just
so
humble.
I
was
like
brilliant
and
the
whole
team
was
shocked,
but
we're
still
happy
but
right,
great
and
this
person
was
at
the
time,
was
getting
paid.
C
I
was
a
contractor,
so
I
was
getting
paid
well,
but
they
were
getting
paid
four
times
what
I
was
getting
paid
at
a
fraction
of
my
age
and
a
fraction
of
my
experience,
but
they
were
an
expert
in
this
library
and
they,
more
importantly,
they
over
delivered.
They
finished
three
days
early.
They
said
I
finished
early.
I've
got
my
hotel,
I'm
still
here.
What
can
I
help
you?
But
we've
got
this
new
feature
coming
up
the
following
month.
Can
you
get
started
and
in
those
three
days
they
literally
didn't?
They
wrote
some
documentation.
C
They
were
amazing.
So,
after
that,
when
we
had
any
tight
deadlines,
it
was
just
like
look.
We've
got
this
piece
of
work.
Can
we
send
it
to
you?
Do
it
in
your
own
time
whenever
you
want,
we
need
it
in
kind
of
two
weeks,
it's
kind
of
a
day's
work
for
you
and
so
forth,
and
I
can't
believe
that
person
was
still
the
student.
So
I
think
you
know
your
age
doesn't
matter
where
you're
from
doesn't
matter
your
experience
and
all
those
sorts
of
things
doesn't
matter.
C
B
Thank
you
so
much
eddie.
This
has
been
so
much
fun.
I
appreciate
everyone
that
participated.
Your
questions
were
so
thoughtful.
Your
answers
were
so
helpful.
I
learned
a
lot
from
you
today,
so
I
very
much
appreciate
it.
Let's
quickly
now,
let's
quickly
see
what
what's
happening.
I
know
from
our
end,
I
like
to
share
that
our
international
global
virtual
meetups
are
happening
all
next
week
on
tuesday.
So
if
you
weren't
aware
that
we
do
this,
this
is
happening.
B
You
can
go
to
meetup.com
for
slash,
github
virtual
dash,
meetup,
and
then
you
can
find
the
region
and
the
language
that
you
like
to
engage
in,
and
we
have
meetups
happening
in
four
different
languages
this
time
around.
So
it's
there's
something
for
everyone,
so
definitely
check
it
out.
Eddie.
Do
you
have
anything
coming
up
that
you
want
to
share.
C
C
In
the
chat,
but
you
said
in
different
languages
and
that's
what
I
love
so
you
don't
have
to
be
a
techie
to
be
involved
in
open
source
and
to
give
an
example
because
of
my
youtube
channel,
I
have
a
full-time
video
editor.
It
is
amazing
she's
in
ukraine,
and
so
she
contributes
to
our
open
source
projects
by
translating
into
russian,
and
you
know,
she's
not
a
coder
or
a
techie,
but
I
feel
that
everyone's
a
techie
everyone's
kind
of
in
it
open
source
really
is
for
everybody
because
they
can
help.
C
C
So
important
to
include
the
people
who
can
translate,
and
then
that
includes
more
people
like
it's
it's
this
kind
of
snowball
effect.
It
just
keeps
getting
better
and
better
for
everybody
and
society
and
the
community
involved
in
terms
of
things
coming
up.
I
do
live
stream
every
monday
and
friday
and
we
do
this
kind
of
eddie
radio,
where
people
can
join
me
on
the
livestream
just
with
audio.
C
Only
so
you
join
via
our
discord
and
nick
who's
in
the
chat
does
an
amazing
job
of
bringing
people
up
for
a
few
minutes.
They
can
ask
a
question,
give
them
some
shout
out
and
they
can
help
me
coding.
They
compare
with
me,
but
people
can
also
join
me
on
a
live
stream.
If
they
want
nick
remind
me,
do
you
have
anything
particularly
coming
up?
I
think
you
know
we
have
stuff
coming
up
all
the
time.
C
I
don't
think
anything
kind
of
you
know
massive
at
the
moment,
just
if
people
want
to
get
involved
in
open
source
and
want
a
an
inclusive
community
in
a
supportive
community
where
everyone
is
a
mentor
as
well
as
a
mentee.
That's
one
thing
we
promote
if
you're
one
month
into
your
career
or
one
month
into
open
source,
we
have
people
who
have
20
years
experience
in
tech
but
they're
new
to
open
source.
C
You'll
learn
so
much
by
by
helping
other
people
I
did.
I
find
I
do
by
helping
other
people,
I
learn
so
much
and
it
kind
of
you
get
to
see
the
other
side
of
the
table.
So
your
questions
and
and
your
research
just
gets
better
all
the
time,
because
you
see
how
people
are
asking
questions
you
think.
Well,
they
haven't
given
enough
information
or
given
too
much
and
so
yeah
definitely
join.
Our
awesome
community,
of
course,
subscribe
to
my
youtube
channel
and
we
can
geek
out
some
more
I'm
just
loving
all
this
chat.
B
The
chat
it's
going
too
fast,
you're,
all
amazing,
it's
hard
yeah,
but
they
can
follow.
You
on
twitter
follow
subscribe
to
your
youtube
channel,
and
then
you
know
you
can
keep
in
touch
with
eddie.
I
can
attest
that
he
does
reply
and
he
definitely
geeks
out
online.
So
let's
do
it.
Thank
you,
everyone!
So
much.
I
wanted
to
ask
the
question.
So
let's
do
this
and
this
can
be
the
closing
eddie
you're
not
allowed
to
answer,
because
you
probably
know
the
answer
already
and
it's
like
a
little
bit
of
trivia.
B
So
I
would
love
for
all
of
you
to
follow
the
enterprise
twitter
handle
github,
github,
ent
and
so
go
ahead
and
add
us
with
the
answer
and
then
I'm
gonna
take
a
look
and
see
who
did
it
first
and
reach
out?
Maybe
there'll
be
a
surprise
there
for
you,
so
I
want
to
know.
Can
you
tell
me
anyone
in
the
audience?
What
do
you
think
the
first
example
of
free
and
open
source
software
so
developed
by
a
company
and
it
was
open
source
and
I
will
give
you
a
hint.
B
It
was
well
before
both
our
time
setting
well
well
before
so
have
a
think
about
that
answer
it
at
github
ent
and
then
I
will
be
in
touch.
Thank
you
so
much
everyone
who
joined
eddie.
Thank
you
so
great
to
be
with
you
and
just
learn
so
much
from
you
and
thank
you
for
everything
you
for
the
community.
It's
people
like
you
that
just
make
this
job
so
enjoyable.
So
thank
you.
So
much.
C
Thank
you
and
thank
you
for
this
awesome
geek
out
session.
I
look
forward
to
next
time
on
github's
channels
or
you're
welcome
to
join
me
on
mine,
and
we
can
just
geek
out
some
more.
I
think
my
community
would
love
geeking
out
with
you
and
just
yeah.
Thank
you
so
much.
I
had
so
much
fun,
I'm
going
to
be
on
a
high
for
the
rest
of
the
weekend,
yeah
and
if
I
can
leave
one
kind
of
action
for
everyone,
everyone
get
involved
in
open
source
today
or
coming
up
today.
C
It's
friday
tomorrow
get
involved
and
don't
think
of
it
big
think
of
it.
Small,
like
brushing
your
teeth.
Little
and
often,
and
over
time
it's
is
you're
gonna
benefit.
It's
gonna
be
massive,
like
even
just
customizing
your
github
profile,
just
just
you
don't
even
have
to
make
a
big
customization
just
create
that
repo.
That's
the
same
name
as
your
username
and
that's
it.
But
now
the
repo
is
there
for
someone
else
to
you
know:
go!
Oh!
I
know
your
socials.
I
can
add
it
to
your
to
your
customized
profile.