►
Description
Presented by: Duane O'Brien & Abigail Cabunoc Mayes
Join this conversation with Duane O’Brien, Director of Open Source at Indeed.com. Learn how Indeed approaches open source sponsorship using GitHub Sponsors, the FOSS Contributor Fund, and more.
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
A
I
lead
github's,
open
source,
maintainer
programs
and
I'll
be
your
host
for
today.
So
we
have
a
great
fireside
chat
as
part
of
GitHub
Universe.
We'll
have
a
conversation
with
indeed
on
how
they
approach
open
source
sponsorship
using
GitHub
sponsors,
the
Foss
contributor
fund
and,
more
so
joining
me.
Today.
We
have
Dwayne
O'brien.
He
is
the
director
of
Open
Source
at
indeed,
and
the
creator
of
the
fox
contributor
fund.
He
loves
telling
the
story
of
Open
Source
through
collaboration
and
conversation.
A
B
A
B
A
B
I
was
talking
about
is
the
idea
that
we
need
to
think
about
the
open
source
ecosystem,
the
way
you
think
about
a
forest
and
the
health
of
the
ecosystem.
The
way
you
think
about
the
health
of
a
forest
ecosystem,
and
so,
if
you
go
in
and
clear
cut
a
bunch
of
trees
in
a
forest,
it
takes
ages
for
that
Forest
to
recover
right
and
there's
all
kinds
of
activity
in
the
forest.
Besides
the
trees
that
is
really
important,
there
are
things
happening
in
the
understory.
There
are
things
happening
under
the
dirt.
B
There
are
all
of
these
different
aspects
of
activity
in
in
the
ecosystem
and
I.
Think
that's
very
true
of
what
we
see
in
open
source
as
well.
There
are
some
big
trees
that
everybody
knows
about.
There
are
some
big
organizations
that
to
go
into
force
and
they
may
or
may
not
behave
responsibly
in
that.
But
if
we
want
that
that
ecosystem
to
survive
for
us
long
term,
we
have
to
care
for
it
the
way
that
you
would
care
for
any
other
ecosystem.
Yeah.
A
I
love
that
and
I
think
especially
this
conversation
on
sustainability,
the
environment
is
really
what
comes
to
mind.
So
I
think
that's
a
perfect
metaphor
for
the
space
cool
so
going
back
a
little
bit
more
Dwayne.
Do
you
want
to
tell
me
about
yeah
your
open
source,
origin
story?
How
did
you
get
into
this
space
and
how
did
you
get
started.
B
B
My
first
contribution
was
on
a
bug
tracking
system
called
mantis,
which
probably
no
one
remembers
at
this
point
and
I
had
tripped
over
a
bug
where
it
was
well.
This
might
date
it
where
it
was
working
on
Regular
window
systems,
but
not
Windows,
NT
right
and
when
I
identified
the
one
line,
change
that
would
fix
this
I
reached
out
to
the
maintainer
and
told
them
what
it
was
and
they
they
said.
B
B
B
We
drive
our
work
in
the
open
source
programs
office
through
Three
core
initiatives.
We
enable
the
effective
use
of
Open
Source,
we
sustain
our
open
source
infrastructure
and
we
tell
compelling
stories
about
our
work,
and
so
we
do
some
work
internally
to
make
sure
that
Indians,
who
want
to
use
open
source
have
the
support
that
they
need
and
and
have
help
from
us
in
trying
to
identify
if
projects
are
healthy
or
unhealthy
and
look
for
opportunities
to
help
people
get
better
at
using
it.
The
open
source
that
we
depend
on.
B
We
want
to
play
an
active
role
as
sustainers
in
those
projects.
We
do
a
lot
of
that
through
funding.
We
do
some
of
that
through
code
contributions
and
also
making
sure
that
those
conferences
that
you
mentioned
are
are
supported
in
healthy
places
for
the
community
to
come
together
and
then
telling
compelling
stories
about
our
work.
We
go
out
and
we
do
talks.
We
write
blog
posts
internally.
We
we
are
excited
about
the
work
that
we
do
and
we
love
to
telling
people
about
it.
So.
A
B
B
Sometimes
we
sponsor
them,
but
may
not
show
up
just
to
help
make
sure
that
there
are
community
events
happening
in
different
areas.
We
do
sponsorship
of
Foundations
and
member
organizations
and
trade
organizations,
the
Apache
software
Foundation
software,
Freedom,
conservancy,
and
so
on.
We
also
fund
interns
through
outreaching,
I,
guess
so.
B
There's
five
categories
we
fund
interns
through
Outreach,
you
I,
think,
is
a
different
stream
and
then
we
do
a
lot
of
funding
of
projects
and
people,
and
the
fast
contributor
fund
is
the
framework
that
we
use
to
decide
which
projects
we
want
to
sponsor.
And
then
we
have
a
different
process
to
identify
which
people
we
want
to
sponsor
and
we
look
for
people
who
are
having
a
broad
impact
across
a
wide
range
of
of
dependencies
as
opposed
to
activity
within
a
single
project.
A
B
Hear
more
sure
we
developed
a
framework
in
2018
and
started
applying
it
in
2019
called
the
Foss
contributor
fund,
and
that
is
our
decision-making
framework
for
identifying
projects
that
indeed
relies
on
that.
We
want
to
financially
support
the
way
the
fost
contributor
fund
works.
Is
everyone
at
indeed
who
makes
open
source
contributions
over
a
given
period
of
time,
gets
the
opportunity
to
vote
on
dependencies
that
indeed
uses,
and
it
doesn't
have
to
be
necessarily
in
a
product
stack
or
an
infrastructure
stack.
B
B
So
we
built
up
a
new
process
that
looks
at
all
contributors
across
all
of
our
projects
and
breaks
them
into
different
cohorts
by
a
language
ecosystem
and
looked
at
how
many
contributions
they've
made
and
how
much
are
that
we
appear
to
be
using
that
project
and
how
many
projects
they've
contributed
to.
And
we
use
that
as
the
starting
point
for
the
investigation
that
we
do
to
figure
out
who
the
people
are,
that
we
want
to
sponsor
and
there's
some
other
pieces
that
go
into
our
ultimate
decision
making
there.
B
But
that
has
I
think
that's
a
interesting
compliment
to
funding
projects,
because
projects
have
a
scope,
projects
have
goals.
Cut
projects
might
have
specific
improvements
that
they
want
to
fund
or
specific
things
they
want
to
accomplish
with
their
goals.
They
might
also
have
governance
models
that
can
support
influxes
of
larger
funding
individuals
who
are
looking
to
self-fund
their
work
or
to
earn
a
little
money
by
making
open
source
contributions.
A
That's
super
interesting
yeah,
so
I
really
enjoy
your
like
the
fast
contributor
fund
process.
How
you've
opened
up
the
process
itself
said
it's
really
the
whole
company.
That's
deciding
this
and
you're
making
sure
that
you're
giving
money
to
the
yeah
the
projects
that
most
need
this
or
that
that's
most
used
by
your
your
community.
Why
is
directly
supporting
maintainers
important
to
you
and
indeed.
B
We
keep
coming
back
to
this
idea
that
open
source
is
people
right
like
there's
there's
code,
yes,
but
people
create
that
code
right
projects,
don't
burn
out.
Maintainers
burn
out
right
when,
when
a
project
reaches
a
point
of
Crisis,
the
maintainer
pulls
it
down,
because
they
can't
maintain
it
anymore
or
the
maintainer
is
underwater
and
the
project
becomes
unhealthy
or
there
is
a
suddenly
a
high
profile
of
vulnerability
in
the
project
and
they
don't
have
the
support
that
they
need.
The
code
doesn't
doesn't
have
the
ability
to
to
to
change
anything.
B
It's
the
people
who
can
change
things
right
and
so
supporting
people
if
you
care
about
open
source
sustainability
is,
is
the
only
way
to
get
there
right
and
there's
there's
a
lot
of
different
forms
that
support
can
take.
We
talk
a
lot
about
money,
because
money
is
sort
of
an
easy
thing
for
for
companies
and
people
to
understand
that
somebody
still
has
to
turn
money
into
Time
and
Time
into
code,
and
those
are
people
right,
and
so
we
want
to
support
the
people
who
are
involved
in
these
projects.
A
Looking
at
the
open
source,
ecosystem,
I
think
a
lot
of
Burden
Bird
right
now
to
keep
the
project
running
to
do
all
this
work,
so
I'm
really
glad
that
people
like
you
are
really
thinking
about
getting
that
money
directly
to
maintainers,
even
though
we
know
that
so
much
more
than
money
is
needed,
I
think
it's
a
great
start.
So
thank
you
for
that.
One.
A
Yeah
that
makes
sense.
I
was
talking
to
Fernando
Perez
out
of
the
Jupiter
project
a
couple
weeks
ago,
and
he
was
saying
he
they
weren't
getting
taken
seriously
for
funding
until
they
sent
their
written
governance,
documentation
to
the
big
company
they're
getting
funding
from
and
I
just
yeah
it
yeah.
It
gives
so
much
more
trust
in
the
project
that
it's
like.
Oh,
these
are
grown-ups.
You
know
what
they're
doing,
but
it
is
very
different
for
a
person.
A
B
A
B
To
to
other
people
that
you
know,
there
may
be
value
in
the
work
that
this
person
is
doing
and
you
should
pay
attention.
There
are
definitely
people
who
self-fund
entirely
through
their
open
source
work
and
who
aspire
to
self-funded
entirely
through
their
open
source
work,
but
at
least
based
on
what
I've
seen.
That's,
not
the
vast
majority
of
people.
The
vast
majority
of
people
like
if
they're
asking
for
money
would
like
a
little
bit
of
something
to
to
say.
Thank
you
have.
B
Started
sponsoring
someone
toward
the
beginning
of
the
year
and
we
were
one
of
their
very
first
sponsors
and
our
sponsorship
is
extremely
small
right.
It
might
have
been
on
the
order
of
of
20
to
50
a
month.
I,
don't
remember
off
the
top
of
my
head
and
they
emailed
us
right
away
and
expressed
like
so
much
gratitude
because
they
had
been
working
on
a
project
for
years
and
they
were
just
starting
to
see
this
kind
of
recognition
for
their
project,
and
you
know
they.
B
They
talked
about
how
that
that
kept
them
going
right.
You
know,
you
know
what
it's
like
you're
working
hard
and
when
someone
takes
the
time
to
stop
and
say,
hey,
I,
see
you
working
hard
and
thank
you
that
has
an
energizing
effect,
especially
if
you
spent
a
lot
of
time
buried
in
feature
requests
from
people
who
don't
understand
the
complexities
of
the
project
or
Fielding
issues
from
people
who
are
angry,
that
something
doesn't
work
and
you
don't
have
any
context
for
their
issue.
A
Yeah,
that's
great
yeah,
there's
a
lot
of
Demands
on
open
source
maintainers,
so
I'm
glad
we're
starting
to
surface
that
more,
so
people
are
understanding
it
and
starting
to
fund
them
more.
So
we've
been
talking
a
bit
about
selection.
So
what
hurdles
exists
in
getting
funds
to
to
these
people
or
in
selecting
the
projects?
B
Those
into
two
different
questions,
hurdles
and
getting
funds
to
people
platforms
like
open,
Collective
and
GitHub
sponsors
and
some
of
the
other
funding
platforms
have
helped.
Certainly
it
is
very
difficult
for
an
organization
like
indeed
or
or
any
other
significantly
large
company,
to
write
a
check
to
a
random
person
somewhere
in
the
world
right
there.
B
There
are
procedural
problems
for
a
good
reason
inside
organizations
that
prevent
that
there
are
legal
Frameworks
for
good
reasons
that
prevent
that
right,
and
so,
if,
where
I
think,
the
platforms
have
really
helped
us
is
they've.
Enabled
companies
like
indeed
to
deal
with
a
single
vendor
to
to
write
a
bunch
of
checks.
We
sponsored
on
the
order
of
150
or
so
maintainers
at
the
first
part
of
this
year,
if
I
had
to
process
150
individual
transactions
for
folks
that.
A
B
The
the
challenge,
though,
is
that
there's
a
lot
of
Open
Source
that
doesn't
happen
on
these
platforms
right
and
if
there
are
projects
who
are
looking
for
funding
and
they're,
not
on
on
the
platforms
where
it's
easier
for
organizations
to
pay
them.
That
money
is
going
to
flow
in
the
path
of
least
resistance.
B
A
B
Explicitly
never
want
money
are
getting
support
in
the
other
forms
that
they
need
it
right.
I
guess
another
issue,
and
this
Bridges
us
from
projects
to
people
is
understand.
What's
really
important
in
your
organization
is,
is
not
an
easy
task
right,
it's
a
it's
a
complicated
task
and
I.
We
have
spent
a
lot
of
time
and
invested
a
lot
of
time,
analyzing
our
dependencies
understanding
our
dependencies
and
when
I
say
dependency
here,
I
want
to
come
back
to
that
metaphor
of
of
money
flowing
through
the
path
of
least
resistance.
B
The
easiest
information
to
get
about
your
dependencies
comes
out
of
your
package
dependencies.
There's
all
kinds
of
infrastructure
underneath
that
that
doesn't
show
up
in
in
your
in
your
package
dependencies,
and
so
we've
spent
a
lot
of
time
to
understand
what
those
dependencies
are
and
really
try
to
get
a
handle
on
it.
B
B
We
don't
have
time
right
or
tell
us
what's
important,
we'll
we'll
sign
a
check
and
and
in
particular,
if
you
talk
to
Executive
sponsors
who
are,
are
Technical
and
understand
open
source,
you
don't
have
to
convince
them
that
open
source
is
important
to
your
organization
and
if
you
tell
them
an
organization,
a
project
or
an
open
source.
Community
is
in
financial
distress
and
needs
help
they're
likely
to
say,
like.
B
And
so
it's
the
other
end
understanding
what's
important.
Now
in
2020,
Julia
farioli
gave
a
great
talk
at
the
state
of
the
source,
about
understanding
your
dependencies
and
and
how
to
identify,
which
ones
are
important
to
your
organization.
I
encourage
people
to
go
check
that
out.
One
of
the
things
that
we
have
to
do
is
first
off
break
them
into
language
areas,
because
if
you
just
sort
by
popularity
or
number
of
commits
or
something
like
that,
the
the
JavaScript
typescript
Community
is
extremely
granular
and
they
dominate
like
the
the
list
of
counts
right.
B
So
you
you
have
to
break
it
according
to
to
language
cohorts
for
one.
You
also
have
to
break
it
by
sort
of
areas
of
business
importance,
and
so
there
is
a
lot
of
work
involved
in
the
process
and
trying
to
get
it
right.
That
work
will
teach
you
about
your
dependencies,
but
you
can
only
spend
the
time
that
you
have
on
it.
So,
like
don't
be
daunted
by
the
task,
the
more
you
investigate
your
dependencies,
the
more
you
understand
them,
the
better.
B
Your
decisions
will
be
occasionally
you're
going
to
make
decisions
that
aren't
optimal,
and
you
use
that
as
information
to
make
better
decisions
down
the
line
when
it
comes
to
funding
people
and
deciding
who
we're
going
to
fund
and
how
much
we're
going
to
fund
them.
One
of
the
problems
is
that
across
those
150
maintainers
or
contributors,
they
all
have
different
goals,
they're
all
offering
different
models
for
sponsors
for
sponsorship.
Some
of
them
don't
want
to
do
sort
of
a
transactional
style.
B
They
don't
want
to
say
I'll
fix
bugs
for
fifty
dollars
or
host
a
talk
for
five
hundred
dollars
right
they're,
just
looking
for
20
to
40
dollars,
and
maybe
they'll
say.
Thank
you.
Managing
that
at
scale
is
very
challenging
understanding
how
to
account
for
all
the
factors
and
who
you're
going
to
support
is
a
challenge.
You
know
if
you've
got
two
maintainers,
both
of
them
looking
to
raise
500
a
month
if
one
of
them
is
extremely
well
funded
and
the
other
one
is
not
extremely
well
funded.
B
B
There
are
all
these
other
areas
in
which
you
have
to
pay
attention.
You
have
to
look
at
how
you're
are
you
funding?
Are
you
flowing
your
funds
equitably
through
the
ecosystem?
Are
you
gauging
the
right
level
of
sponsorship
versus
anticipated
impact
or
health
of
the
projects
that
you're
that
you're
wanting
to
sponsor?
This?
Is
it's
complicated,
but
it
doesn't
get
less
complicated
by
not
trying
I
think
we're
collectively
still
learning
as
an
industry
how
to
measure
the
impact
of
these
kinds
of
financial
sponsorships.
B
You
know:
do
we
see
projects
getting
healthier
when
we
are,
we
are
when
we
are
funding
them.
Do
we
see
people
getting
healthier
when
we
are
spending
and
sponsoring
them?
You
know,
there's
a
there's
a
lot
of
work
there
to
do
for
forever.
There's
a
lot
of
work
there
to
do
for
everyone,
but
I
think
we're
working
on
the
problem.
We've.
A
B
The
the
evolution
of
the
platforms
is
definitely
one
thing.
You
know
one
of
the
one
of
the
things
that
I
think
GitHub
sponsors
has
done
for
us
as
an
unintended
but
extremely
positive
side
effect.
Is
we
now
have
a
machine
readable
file
that
we
can
go
digging
for
to
try
to
figure
out
how
many
projects
even
want
funding
right?
It's
not
perfect.
There's
a
lot
of
Open
Source
that
isn't
covered
there.
B
There's
a
lot
of
open
sources
mirrored
on
GitHub,
but
maybe
isn't
actively
developed
there,
but
four
years
ago,
if
I
wanted
to
figure
out
which
of
my
dependencies
were
thinking
about
asking
for
money
or
or
had
any
kind
of
sponsorship
goals
or
which
of
my
which
of
the
contributors
to
my
dependencies
had
their
had
their
own
sponsorship
goals.
There
was
just
no
way
to
get
at
that
information
at
scale
and.
A
B
That
is
a
that
is
a
thing
I
will
come
back
to
when
it
comes
to
organizations
being
involved
in
open
source.
We,
it
does
no
good
if
every
project
has
their
own
way
of
doing
it.
I
have
thousands
of
projects
that
I
have
to
figure
out.
What
like
who
and
what
to
fund
right.
I
have
to
prioritize
the
ones
that
are
important
and
I
have
to
understand
this
problem
at
scale
and
I
think
we're
still
getting
there,
but
the
evolution
of
the
platforms
has
made
this
easier
for
projects.
B
It's
made
it
easier
to
unlock
funding
from
individuals
and
from
organizations
we're
starting
to
see.
You
know
machine,
readable
information
across
the
ecosystem
at
scale
for
projects
that
are
looking
for
funding
and
we've
seen
a
couple
of
really
interesting
outcomes.
One
of
my
favorite
is
the
the
work
that's
gone
on
in
the
in
the
eslint
community,
where
they
started
receiving
funding.
B
A
B
I
know
this
was
happening
you
know
before,
but
we're
getting
visibility
into
these
kinds
of
things
as
well.
I
think
it's
a
really
neat
outcome
and
a
good
example
of
what
can
happen
when
you
show
up
for
a
project
and
say
we
want
to
support
you
and
they
have
a
good
governance
model
they
turn
around
and
take
that
and
needs
it
to
support
their
broader
Community.
B
What
does
it
mean
to
curate
the
Forest
right
and,
and
so
that
that
is,
that
is
definitely
we've
seen
a
shift
in
that
over
over
the
few.
Over
the
past
few
years,
I
think
we're
also
seeing
more
experimentation
with
organizations
who
are
looking
to
spread
funding
out
across
their
dependencies.
Century
has
done
great
work
here.
B
Stripe
has
done
great
work
here,
a
couple
of
really
interesting
models,
and
then
there
have
been
other
folks
who
have
adopted
the
fox
contributor
fund
framework
like
I
like
I
described
Spotify,
ran
something
very
much
like
it.
They
run
one
at
Microsoft.
They
run
one
at
Salesforce
and
so
I
I
like
seeing
the
experimentation
from
organizations
who
are
trying
to
figure
out
how
to
effectively
fund
and
sponsor
open
source,
because
it
means
they're,
learning
and
they're
going
to
get
better
at
it.
B
Part
of
Good
Forest
management
is
knowing
when
to
clear
out
the
underbrush
and
and
to
cut
down
trees
that
aren't
healthy
anymore
and
so
on,
and
there's
this
tremendous
sense
when
you've
created
something
like
an
open
source
project
like
that
represents
hours
of
lost,
sleep
and
excitement
and
joy
and
frustration
and
and
and
all
the
time
and
all
the
time
that
you've
spent
in
it
and
that
the
community
spent
into
it.
And
sometimes
it
can
be
hard
to
to
let
go
of
that.
B
But
if
we
continue
to
create
more
and
more
projects
and
more
and
more
of
those
projects
continue
to
request
funding,
we
run
the
risk
of
not
prioritizing
things
that
need
it.
The
most
I
really
want
us
to
to
be
willing
to
have
some
of
those
hard
conversations
about
when
it's
when
it's
time
to
de-prioritize
funding
for
some
projects,
because.
B
A
We
are
starting
to
see
people
sort
of
leave
the
space
and
like
they're,
done
with
their
open
source
project,
and
we
haven't
seen
a
ton
of
it
just
because
software
is
relatively
new,
but
we'll
see
more
and
more
of
it
as
people.
You
know
retire
and
move
on
to
other
careers
and
I
think
we,
as
a
community,
haven't
thought
of,
like
appropriate
response
to
that
I.
A
Think
a
lot
of
people
like
are
trying
to
save
those
packages
or
those
repos,
but
I
think
in
a
lot
of
cases,
it's
okay
to
let
them
let
them
die
and
just
tell
people
to
move
on
to
the
new
package.
That's
built
using
newer
technology.
Maybe
you
don't
have
to
use
this
old
stuff,
so
no
I
I
think
those
it's
a
bit
of
a
downer,
but
I
think
it
is
really
important
conversation.
So
thanks
for
going
there
doing
sure.
B
The
other
thing
that
I
hope
for
is
that
we
continue
to
get
better
at
surfacing
this
information
at
scale
for
large
organizations
who
have
a
lot
of
dependencies
who
want
to
make
good
decisions
about
who
and
what
they
should
fund
understanding
health
of
of
projects.
Over
time
understanding,
when
your
funding
interventions
have
been
successful,
when
mobilizing
people
has
been
successful
and
being
able
to
get
at
this
information
through
the
lens
of
an
organization
with
a
lot
of
concerns,
rather
than
through
the
lens
of
an
individual
project
right.
B
So
by
way
of
example,
if
you're,
if
your
project
sets
up
a
great
dashboard,
that
tracks
contributor
health
over
time
and
and
code
code
change
rate
over
time,
an
issue
open
and
close
rate
over
time
that
might
be
really
really
useful
for
community
and
for
your,
your
community
of
adopters
I
can't
look
at
2000
dashboards.
I
I
need
to
see
this
information
through
through
a
more
Consolidated
interface
and
so
and.
B
A
B
First
thing
I
would
say
is
that
you
can
start
today
with
any
amount
like
you,
don't
have
to
create
a
giant
program
to
to
support
the
open
source
that
you
depend
on.
You
can
get
two
or
three
people
in
a
room
and
do
a
show
of
hands
and
pick
a
project
that
you're
that
you're
going
to
sponsor
you're,
going
to
learn
from
that
engagement
and
you're,
going
to
make
better
decisions
down
the
line.
So
you
don't
have
to
be
funding
at
indeed's
level
or
at
Microsoft
level
or
Google's
level.
B
In
order
to
be
effective
in
the
space.
You
just
need
to
start
where
you
are-
and
you
know
I
I
mentioned
that
it
takes
a
lot
of
time
to
understand
your
dependencies
and
spend
the
time
that
you
have
but
commit
to
supporting
them.
If
you're
looking
for
tools
to
help
you,
we've
published
all
of
the
materials
for
the
Foss
contributor
fund,
they're
available
for
anyone
to
use,
we
wrote
a
book
about
it
with
O'reilly
last
year,
I'm
happy
to
answer
questions
and
excited
to
get
people
involved
in
using
that
framework
and
within.
B
Quarters
we
will
be
releasing
the
code
that
we
use
to
do
that.
Contributor
analysis
that
I've
mentioned
to
help
us
identify
people
that
we
want
to
fund
and
making
that
available
for
everyone.
If
you
want
any
information
about
either
one
of
those,
you
can
email
the
open
source
team
at
opensource
indeed.com.
B
B
Want
to
come
back
to
that
that
metaphor
of
the
open
source
ecosystem
is
a
forest.
If
you
want
to
understand,
if
the
forest
is
healthy,
you
need
to
go,
take
a
walk
in
it.
You
need
to
touch
some
leaves
and
rummage
around
in
the
dirt
and
push
over
a
log
and
see
what's
underneath
it
and
so
on.
You
don't
have
to
take
an
eight-hour
hike
through
the
woods,
but
spending
an
hour
walking
through
it
to
understand
how
things
are
doing.
B
If
the
only
thing
that
you
do
is
find
a
project
that
you
heavily
depend
on
and
go
through
their
old
bugs
and
identify
which
ones
still
happen
and
which
ones
can
be
closed,
you're
helping
the
project
right.
So
there
are
so
many
ways
that
you
can
help
to
sustain
your
open
source
projects
find
the
one
that
works
for
you
and
and
get
started.
A
Ones
that
are
no
longer
needed,
that
is,
that
would
be
so
incredibly
helpful.
Thank
you.
So
much
for
sharing
that,
and
thanks
for
joining
us,
Duane
I
learned
a
lot
and
I
really
hope
that
this
conversation
will
just
help
us
as
a
community,
really
understand,
what's
important
when
we're
sustaining
open
source
and
how
it's
more
than
just
the
money
so
yeah
tune
in
to
the
rest
of
GitHub
universe
and
we'll
see
you
all
later.