►
Description
This is our VOD (recording) from the Open Source Friday live stream on the 23rd October 2020, 2pm AEDT. We interviewed Tanner Linsley from React Query, an open source hook for fetching, caching, and updating data. We had the chance to deep dive into Open Source; what it is, how to get involved, what the community is like. Tanner gave us some top tips of building a product from scratch, giving yourself a challenge, and some of the cool GitHub features to enable to ensure success of your open source project.
Join us live for Open Source Fridays at https://www.meetup.com/GitHub-Virtual-Meetup
Tanner Linsley: https://twitter.com/tannerlinsley
React Query: https://react-query.tanstack.com/
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
Google+: http://google.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
Hello,
hello,
everyone
and
welcome
to
open
source
friday
hope,
you're.
All
doing
absolutely
amazing
today
welcome
in
to
all
our
australian
new
zealand
viewers.
It
is
friday
afternoon,
for
all
you,
lovely
people
and
for
everyone
else
over
on
the
us.
It
is
getting
to
light
thursday
night.
I
think
thank
you
all
for
tuning
in
and
welcome
all
I
hope,
you're
having
a
wonderful
day
or
evening
wherever
you
are
now.
A
I'm
super
excited
on
open
source
friday
on
the
github
twitch
channel
today,
to
have
a
very
amazing
awesome,
guest
with
us
again
shooting
to
us
from
the
evening
time
zone
as
well.
So
we
thank
him
so
much
for
staying
up
late
to
join
us
all,
because
you
know
that's
what
we
are
all
about.
What
open
source
and
being
part
of
the
community
is
just
getting
up
and
staying
awake
for
all
our
amazing
community
people
so
without
further
ado,
I'd
love
to
introduce
you
all
to
tana
lindsey
from
react
query.
How
are
you
going
tana.
B
A
We
definitely
thank
you
for
staying
awake
late
at
night
and
being
on
board
for
our
open
source,
friday
stream.
So
how
have
you
been
going
with
react?
Query
what's
been
happening
on
that
front
and
maybe
for
all
those
viewers
who
don't
know
before
we
jump
into
all
the
ins
and
outs
of
getting
involved
in
the
open
source
community.
How
about
we
have
a
little
chat
first
about
what
react
crew
is
those
people
who
have
absolutely
no
idea.
B
A
A
B
Yeah
and
it's
been
going
awesome,
so
it
has
like
14,
000
stars
and
almost
200
contributors
now
but
react
query.
Is
a
library
for
fetching
data
in
react?
Simply
put
I've
been
told
by
a
lot
of
people
that
it's
kind
of
like
the
missing
data
fetching
library
for
react,
but
it
does
a
lot
more
than
that,
but
that's
a
good
place
to
start.
A
I
like
it
now
if
we
go
and
jump
over
and
have
a
look
at
your
github
profile,
you
definitely
weren't
telling
lies
because
you
look
up
the
top
there.
14.3
000
stars
well
done
on
that.
So
that
is
amazing
and
if
we
scroll
down
here,
look
at
number
contributors,
190
contributors
and
used
by
over
two
and
a
half
thousand
people,
so
very,
very
awesome
and
great
work
on
that.
Now
you
talk
a
little
bit
about
like
route
query
and
like
what
it
actually
is,
and
you
only
started
a
year
ago.
A
B
React
query:
you
know,
I
didn't
just
wake
up
one
day
and
say
I'm
going
to
build
react
query,
but
it
it's
been
a
long
time.
Coming
honestly,
I
would
say
ever
since
I
migrated
to
react
from
angular
like
four
years
ago.
I
I
just
I've
always
wanted
something
like
react.
Query
in
react,
and
you
know
my
entire
journey
of
going
through
the
react
ecosystem
and
getting
into
open
source
has
kind
of
led
up
to
react.
B
Query
itself
getting
really
deep
into
redux
building
kind
of
redux
wrappers
that
maybe
weren't
super
popular
at
the
time,
and
now
they
are,
you
know,
building
other
libraries
that
that
maybe
aren't
as
popular
but
helped
me
practice.
My
open
source
foo
like
react
to
table,
but
at
the
end
of
the
day,
like
a
lot
of
things
led
up
to
react,
query
react.
Hooks
was
a
huge
one.
B
Anybody
who
has
used
react
query
knows
that
it's
hooks
only
so
that's
that's
kind
of
fun,
but
yeah
like
every
every
thing
about
fetching
data
in
react.
Just
never
felt
right
until
I
built
react
query.
So
a
lot
of
those
pieces
came
together
over
the
years
until
everything
kind
of
just
aligned
perfectly
to
release
the
library.
A
B
Yeah-
and
you
know
that
started
out
as
a
joke
from
one
of
my
friends
on
twitter-
and
you
know
he
he's
like:
oh
it's
so
funny,
you
should
call
it
the
tan
stack
and
I
kind
of
chuckled
at
first
like
oh,
that
would
be
interesting
and
he
kept
saying
it
over
and
over
on
twitter
and
even
made
a
hashtag
for
it,
and
other
people
started
jumping
on
board
and
I
was
like
okay,
you
know
it
kind
of
doesn't
sound
half
bad
now.
So
let's
do
it
here.
A
We
go
so
you
can
actually
subscribe
to
the
future
home
of
10
stack.
I
think
it's
yeah.
I've
got
every
time.
I
read
this,
I'm
like
jam
stack
or
tan
stack
like
what
other
kind
of
snack
is
it
I
quite
like
it
so
yeah.
As
you
mentioned,
you
had
a
brief
chat
to
me
before
you
jumped
on
this,
so
you
even
have
a
discord,
server,
410
stack
and
that's
what
you're
going
to
be.
I
suppose
that's
where
a
lot
of
your
community
live
right.
B
A
We've
had
a
chat
to
a
few
of
the
other
maintainers
on
open
source
friday
nights.
A
lot
of
them
seem
to
have
discord
servers
which
I
think
is
an
amazing
thing
right.
You
know,
when
you
talk
about
trying
to
find
communities
a
lot
of
maintainers
and
contributors
say
a
great
way
to
find
communities
through
discord
servers.
So
what
are
the
types
of
things
that
you
do
over
on
your
serving?
You
talked
about
people
like
supporting
one
another,
but
what
other
kind
of
conversations
that
go
on
like?
What
are
the
kind
of
things
happening?
B
Looking
for
help
all
the
way
to
like
very
in-depth
discussions
about
the
internals
of
the
libraries
that
I
write,
I
even
have
private
channels
there
for
all
of
the
contributors
of
all
my
libraries
so
that
they
can
plan
together
and
discuss
internals
and
ideas
without
you
know,
causing
causing
a
riot
in
the
normal
channels,
there's
a
channel
for
each
library
there
so
that
people
can
discuss
specific
issues
and
yeah
like
it's
really
just
kind
of
all
over
the
place.
Another
fun.
B
One
too
is
we
have
some
new
stuff
coming
out
for
react.
Query
next
year
that
yeah
we're
kind
of
it's.
It's
not
really
a
secret,
but
you
know
we're
keeping
it
kind
of
down
low
for
now.
But
it's
we're
trying
to
make
react,
query
platform
agnostic,
so
you
could
use
it
with
any
other
framework.
Angular
spell
whatever
you
want,
and
I
have
met
some
of
the
coolest
contributors
who
are
so
passionate
about
these
projects
and
react.
B
Query
that
they
are
helping
me
write
these
new
bindings
for
it
and
they
all
have
their
own
channels
to
kind
of
work
together
and
anybody
can
become
a
contributor,
and
I
put
you
into
the
channel
and
you
can
help
contribute
to
these
new
libraries.
It's
very
cool
just
to
see
the
amount
of
collaboration
that
happens
inside
of
there
yeah.
A
That's
really
cool
and
I'm
I'm
really
interested
in
these
just
because
I'm
in
the
I'm
a
gamer,
so
we
obviously
have
a
lot
of
discord
servers
for
gaming
as
well,
and
I
think,
the
more
and
more
I
chat
to
maintainers
the
more
I
find
that
they're
all
using
these
servers
for
these
kind
of
things.
I
want
to
give
a
shout
out
to
ice
cream
tango
on
the
chat.
Thank
you
so
much
for
being
here
shout
out
to
everyone
else
in
the
chat
as
well.
Don't
forget
that
we
are
taking
questions
from
the
chat.
A
So
if
there's
something
you
want
to
know
about
open
source
about
react,
query
specifically
about
anything
just
pop
it
in
the
chat
and
I'd
be
more
than
happy
to
ask
now.
I
do
want
to
keep
on
this
discord
server
thing
for
a
little
bit
longer.
We've
had
some
questions
in
previous
weeks,
but
also
people
have
seen
me
quite
interested
in
how
you
actually
build
that
community
on
discord.
So
you
said
you
have
what
1500
people
on
discord.
A
B
Yeah,
I
didn't
find
it
too
challenging.
To
be
honest,
the
first
thing
I
did
was
just
create
the
server
and
give
it
some
good
branding.
You
know
make
sure
that
the
logo
is
on
there
and
that
it
feels
legit,
and
then
I
just
took
that
I
made
an
invite
and
put
that
invite
link
on
all
of
my
repos
every
everywhere
I
have
it.
B
I
made
that
landing
page
for
my
for
the
10
stack
and
I
put
that
link
there
too,
basically
anywhere
that
I
have
that's
public,
I
said
I
just
made
sure
that
people
can,
you
know,
go
here.
If
you
want
to
be
a
part
of
the
community,
you
know,
and
in
the
beginning
I
had
to
be
the
community
myself.
I
had
to
be
very
very
involved
with
discussing
every
single
question
and
every
single
topic,
so
it
is
very
involved
in
the
beginning.
B
If
you
want
to
kind
of
jump,
start
it
and
as
more
people
join
and
the
conversations
start
to
flow
better
and
also,
as
certain
people
start
to
come
out
as
kind
of
kind
of
ringleaders
inside
of
the
community.
You
know
people
who
are
moderating
for
you
and
answering
questions
on
your
behalf
and
you
know
kind
of
the
cheerleaders
of
of
the
project
itself.
B
Those
people
start
to
emerge
and
they
make
they
make
it
easier
than
to
kind
of
step
back
a
little
bit
and
just
kind
of
you
know
lead
people
and
manage
there
and
not
have
to
be
uber
involved
and
just
kind
of
jump
in.
You
know
when
there
needs
to
be
either
moderation
or
when
you
need
to
announce
something
new.
So.
A
You
kind
of
like
kickstart,
the
community
and
then
the
community
gets
big
enough.
They
can
cut
run
itself,
I
suppose,
like
any
other
community.
I
think
the
the
big
question
we've
been.
Having,
though,
is
how
do
you
actually
jump
start
that,
and
I
think
you've
answered
it
perfectly.
You
know
just
basically
everywhere,
where
your
community
currently
is
just
go.
Put
your
discord
on
everything.
B
A
B
Also
inside
of
the
issue
templates
in
github,
I
believe,
if
you
go
to
create
a
new
issue,
you're
going
to
see
a
template
that
says
you
know
what
do
you?
What
do
you
want?
Is
it
a
feature
request?
Is
a
community
chat
so
that
feature,
requests
and
questions
that
will
take
you
to
the
discussions
section
of
the
repo.
B
A
Hence
what
it
says
so
you've
set
these
up.
This
is
perfect.
There
you
go
go
straight
to
discord
and
then
you
can
join
the
discord
server
there
you
go.
That
is
really
really
cool.
Now
I've
got
a
question
from
the
chat
and
then
we're
going
to
come
back
to
the
discussions,
because
I
love
talking
about
discussions
and
definitely
get
some
of
your
thoughts
on
it.
A
I'm
going
to
question
the
chat
saying
that
if
you
are
new
to
open
source,
how
do
you
go
about
actually
starting
to
promote
the
libraries
you're
developing
without
like
an
existing
presence
we've
had,
but
I
want
to
hear
your
thoughts
now
I'll
give
you
some
thoughts
about
what
our
guest
last
week
spoke
about
from
hopscotch.
He
had
some
very
interesting
insights
on
how
to
go
about
promoting
yourself,
but
how
do
for
you
tana?
What
are
your
thoughts
on?
B
That's
a
tough
question,
but
I
think
the
way
that
I
have
approached
that
is
it
doesn't
matter
in
the
beginning.
It
doesn't
matter
how
much
marketing
you
do
or
how
much
presence
you
have
for
a
library
to
some
extent
unless
the
library
is
actually
good.
So
I
think
at
the
bare
minimum
you
need
to
make
sure
that
you
have
a
library
that
works
that
has
documentation
and
is
actually
solving
a
problem
either
in
a
way
that
is
different
or
better
than
the
tools
that
you're
trying
to
compete
against.
B
I
built
a
library
that
was
geared
towards
that
specific
problem,
solving
it
in
the
way
that
I
thought
was
best
and
from
there
I
mean
it
does
help
to
have
an
existing
presence
on
the
internet.
But
you
don't
need
a
presence
to
go
to
stack
overflow
questions
or
to
get
on
reddit,
or
you
know
really
to
go
to
the
community
portions
of
the
internet
and
just
kind
of
put
yourself
out
there.
B
You
just
have
to
say:
hey,
you
know,
here's
a
library
I
made
and
if
you're
having
this
type
of
an
issue,
it
will
probably
help
you
and
also
making
yourself
personally
available
in
the
beginning.
Just
like
the
discord
server,
you
have
to
be
there
for
the
very
first
users
of
your
library
making
yourself.
A
Definitely,
I
think
so.
We
had
lyrics
from
hopscotch
on
last
week
and
he
was
saying
very,
very
similar
things
to
you,
which
is
you
know,
find
where
your
audience
is
go
and
promote.
He
was
saying
to
like:
don't
like
shamelessly
self-promote
everywhere,
you
know,
jump
on
places
like
you
know,
start
building
your
twitter
following
jump
on
discord
servers.
You
know
start
like
get
on
the
reddit
sub
subreddits
and
things
like
that
and
if
you
do
want
to
read
a
little
bit
about
that
from
last
week.
A
Here
is
on
the
dev
two
posts
I've
put
together
and
one
of
the
things
he
says
is
you
know
just
basically
just
get
out
there
and
write
like
you
need
to
find
your
audience
and
find
out
where
they
are
now
before
we
jump
into
discussions.
Had
a
couple
of
questions
about
github,
dark
mode,
which
I
get
quite
a
lot
on
this
stream.
Light
mode
does
burn
my
eyes
too,
but
if
you
want
dark
mode,
we
don't
have
an
official
github
dark
mode
for
anyone
out
there
at
the
moment.
A
But
what
we
do
have
again.
Another
amazing
open
source
project
is
what
you
call
dark.
Reader,
so
dark
reader
allows
you
to
make
your
browser
dark
and
it'll.
It
goes
across
everything.
So
obviously
this
is
why
you
see
my
github
in
a
dark
mode.
If
I
go
to
any
other
website
as
well.
This
is
probably
why
yours
looks
a
bit
funky,
because
we've
got
dark
reader
on
so
I'm
gonna
turn
it
off.
It
goes
white
now
turn
back
on.
A
So
you
never
know,
and
if
you
ever
do
want
to
know
about
what's
happening
with
github,
you
can
always
go
check
out
our
public
roadmap,
so
we
released
the
public
roadmap
only
like
a
couple
months,
not
like
literally
not
that
long
ago,
and
you
can
go
jump
on
our
public
roadmap
and
see
all
the
things
that
are
coming
up
so
go
check
that
out.
But
our
discussions
tana
wouldn't
chat
about
this.
A
How
are
you
finding
discussions
and
what
are
you
actually,
you
kind
of
touched
on
a
little
bit
before,
but
so
for
those
of
you
who
don't
know,
we
launched
github
discussions
at
satellite
this
year
back
in
may,
which
is
being
that
long
and
it's
a
way
for
people
to
have
good
discussions
are
within
their
repo.
So
I
want
to
hear
from
you
with
how
you
are
finding
discussions,
but
also,
what
are
the
kinds
of
things
you're
using
discussions
for
within
the
query,
repo.
B
B
This
was
kind
of
a
missing
piece,
because
if
it
was
like
a
really
quick
question
or
like
a
question
that
maybe
was
asking
for
something
like
the
community
help,
that's
something
where
now
discord
can
fill
that
gap.
If
it
was
a
real
issue,
then
it
makes
sense
to
be
have
it
be
in
the
issues
right
and
and
tag
it
up
and
try
and
fix
it.
B
But
there
are
so
many
of
there's
so
many
issues
that
used
to
come
in
and
still
do
to
some
extent
that
are
just
kind
of
how
do
I
do
this?
How
do
I
do
that?
Hey,
I'm
seeing
this
thing
and
it
looks
kind
of
weird
I
don't
have
all
the
information
to
really
make
it
an
issue,
but
I'm
just
curious
about
what's
going
on
so
it's
kind
of
these
vague
things
that
come
in
through
issues.
I
really
don't.
B
I
didn't
like
the
what
we
did
before
is
we
kind
of
just
be
like
if
you
don't
have
a
reproduction
use
case,
I'm
going
to
close
your
issue,
but
now
in
instead
of
doing
that,
I
get
to
kind
of
just
say:
okay,
we're
going
to
move
this
over
to
discussions.
It
can
go
into
ideas
or
q,
a
or
just
kind
of
general
discussion.
You
know
and
it's
still
visible
to
the
internet.
B
It
gets
indexed
for
seo
people
you
know,
see
those
questions
coming
in
if
they're
watching
the
repo,
but
it
doesn't
necessarily
get
tracked
as
an
issue
and
it
doesn't
like
put
a
big
old
number.
You
know
above
your
issue,
count
saying
you
know
this.
This
repo
has,
you
know
600
issues.
Well,
it
turns
out
that
only
you
know,
100
of
those
are
actually
issues.
500
of
them
are
questions
that
the
contributors
and
maintainers
have
failed
to
close
or
triage.
So
I
think
it's
it's
been
solving
that
problem,
at
least
for
me,.
A
Thank
you
for
that
and
we've
got
some
react.
Query
love
in
the
chat,
we've
got
solution,
loves
react,
query
lit
share
for
various
reasons:
we've
disabled
link
sharing
so
feel
free
to
post
your
your
comment
again
and
I'll
post
the
link
for
you,
because
it
is
a
a
twitch
link,
a
github
link,
so
I've
posted
the
link
there
for
you
again,
let's
feel
free
to
write
your
comments
again
with
disabled
link
sharing
but
again
tana.
A
Thank
you
so
much,
but
I
love
hearing
that
kind
of
culture
around
discussions,
because
that's
one
of
the
main
reasons
why
we
built
discussions
is
for
for
the
exact
reasons
that
you're
talking
about
which
is.
You
know
you
notice.
Things
are
happening
in
an
issue
where
originally
issues
were
designed
to
open
an
issue
because
there's
an
issue
like
there's
a
thing
that
needs
to
be
fixed
or
a
feature
needs
to
be
implemented
rather
than
something.
A
Be
discussed
so
we're
super
happy
that,
like
you
know
you
discussions
being
used
to
that
and
I
think
you've
called
it
out
to
us
that
that
that
feature
to
be
able
to
change
something
or
convert
an
issue
to
a
discussion,
vice
versa.
So
if
you're
having
a
discussion
about
something
really
like
in-depth
thing,
okay,
no,
we
have
now
decided
that
we
want
this
to
be
a
feature
and
go
bang,
convert
to
an
issue
and
build
that
into
a
feature.
So
that's
really
cool
that
you're
using
it
in
that
way,.
B
A
Like
hit
that
button
enable
discussions
across
everything,
I
really
really
like
it,
just
double
checking
if
you've
got
any
other
questions,
keep
those
questions
coming
through
the
chat,
we'd
love
to
hear
from
you
all
now.
So
what
I
want
to
talk
about
next
is
route
query
as
an
open
source
product.
Now,
obviously,
it's
an
open
source
project
and,
as
we
showed
before,
you've
got
over
190
contributors,
almost
200
contributors.
A
B
B
Those
are
the
things
that
we
mark,
as
you
know,
good
good,
first
issue,
it's
good
for
a
first-time
contributor
and
from
there
it's
kind
of
like
if
you,
if
you
find
one
of
those
and
you
want
to
work
on
it.
The
next
thing
you
need
to
do
is
go
read
the
contributing
documentation
inside
of
the
repo,
so
most
repos
have
a
contributing
dock
right
inside.
It's
all
caps
yep-
and
everything
inside
of
here
is
supposed
to
tell
you
how
you're
supposed
to
help
us
work
on
this
repo.
B
There
might
be
some
suggestions
in
here
on
like
what
we
consider
issues
or
features
or
how
to
discuss
them,
and
you
can
actually
see
that
right
there.
It
says
issues
are
identified
as
implementation,
questions
or
non-issues
are
immediately
closed
or
redirected
to
github
discussions,
so
kind
of
teaching
you
kind
of
how
to
triage
issues
as
well,
which
is
something
that
is
extremely
helpful.
I
don't
think
newcomers
understand
that
contributing
to
open
source
doesn't
always
mean
writing
code.
B
It
doesn't
have
to
be
that
you
write
code
and
submit
a
pr
some
of
the
best
contributions
I've
had
are
from
people
who
just
kind
of
watch
the
issues
and
the
discussions
and
they'll
use
those
discussions
that
crop
up
that
are
just
kind
of
like
hey.
How
do
I
do
this,
but
you
know,
or
how
does
this
work,
and
it
gives
you
an
opportunity
as
a
first
time
contributor
to
learn
something
about
the
library
and
then
go
and
answer
that
question
and
that
doesn't
require
you
to
to
really
write
any
code
at
all.
B
It's
a
it's
a
great
way
to
get
involved
and
to
start
understanding
the
library
and
then
once
you
do
have
the
level
of
understanding
that
you
need,
and
also
by
helping
triage
issues
like
that.
You,
it's
really
nice
for
maintainers
to
see
that.
So,
if
you
ever
want
to
get
on
a
maintainer's
good
side,
go
into
the
issues
of
the
discussions
and
try
and
help
answer
questions
and
get
more
information
in
triage.
B
It
should
have
instructions
on
there
on
how
to
kind
of
spin
up
the
the
repo
to
clone
it
and
how
to
run
tests
right,
yep,
there's
the
one
click
set
up
right
there
and
all
the
instructions
you
need
to
commit
your
code
to
the
to
the
repo.
So
this
is,
and
this
is
pretty
standard
or
it
should
be
across
any
github
repo
that
you
come
to
this.
A
Is
a
pretty
good
contributing
document,
so
you're
saying
like
you
want
people
to
come
in,
you
want
them
to
read
the
contribution
guidelines
and
you
want
them
to
kind
of
be
part
of
the
community
a
little
bit
too,
like
you
know,
sitting
back
and
having
a
look
at
discussions
and
looking
at
the
issues
and
just
being
a
little
bit
involved.
We've
got
some
people
in
the
chat,
like
obviously
glenn
they're
saying
yes,
non-code
submissions
can
be
just
as
useful
as
code.
A
Submissions
exhibit
a
yes,
the
docs,
and
I
just
noticed
when
we're
going
through
the
issues
that
one
of
your
issues
is
tagged
with
documentation,
which
is,
you
know,
go
and
fix
some
documentation.
There
probably
write
something
new
or
go
and
do
some
bug
features
there.
You
go
remove
these.
Do
these
write
some
things
and
we've
also
got
brian
saying
improving
docs
and
examples
of
some
of
the
most
helpful
and
high
impact
ways
to
contribute,
which
I
think
is
amazing
and
on
that
hi.
B
A
A
Even
a
lot
of
the
open
source
projects
that
are
opted
in
for
for
hacktoberfest
are
actually
asking
people
to
provide
examples
and
more
examples
of
certain
things.
So
you
know
provide
an
example
of
this
code
working
in
xyz
and
I
think
that's
just
like
those
types
of
documentation.
I
think,
is
really
really
helpful.
B
B
B
So
the
code
sandbox
sources
of
truth
are
in
the
repo
in
this
directory,
and
so,
if
you
ever
want
to
add
a
new
example
or
improve
it,
you
just
do
it
on
code
sandbox
and
then
you
can
just
push
up
the
entire
folder.
It's
really
fun
and
it's
so
good
to
have
more
examples
and
lots
of
examples
for
your
library,
because
it
helps
people
also
submit
better
issues
for
your
project.
B
You
know
they
say
I'm
having
an
issue
with
the
the
infinite
scrolling
api
on
react,
query
I'll,
say:
well,
perfect,
there's
a
code
sandbox
for
infinite
scrolling
right
here.
How
about
you
just
fork,
it
and
kind
of
make
it
make
the
bug
happen
and
then
send
it
to
me.
Oh
it's
perfect
code.
Sandbox
is
another
tool
that
has
just
revolutionized
open
source.
For
me,.
A
I'm
gonna
grab
that
lame
code,
sandbox
and
I'll
pop
in
the
chat
close,
but
we've
also
got
a
few
people.
Echoing
up
your
sentiments
about
code,
sandbox
saying
it's
incredible,
it's
amazing
and
we've
got
some
people
there
in
the
chat,
looks
like
they've,
been
either
contributing
to
docs
themselves
or
at
least
contributing
to
some
open
source.
So
the
next
thing
I
want
to
talk
about
really
briefly
before
I
jump
into
a
little
bit
more
about
how
you
going.
A
Is
we've
you've
just
spoken
about
what
you
want,
first-time
contributors
to
do
when
they
come
to
your
repo?
You
want
them
to
to
read
the
documentation
to
read
the
contribution
guidelines
check
out
what
issues
are
there
then
be
part
of
the
discussions
to
understand
how
the
community
works.
Now,
what
are
your
top
tips
for
people
who
maybe
want
to
contribute
to
a
rat
query,
but
not
sure
about
how
to
go
about
it,
or
even
people
just
want
to
contribute
to
open
source
in
the
first
place?
A
B
Well,
I
think
one
important
thing
to
remember
about
contributing
to
open
source
is:
if,
if
you're
not
using
open
source,
then
it's
going
to
make
it
harder
for
you
to
contribute
to
it.
If
you
want
to
contribute
to
a
library,
you
need
to
start
using
it,
and
this
is
all
this
also
goes
along
with
that
saying
that
you
need
to
dog
food,
your
own
stuff.
That's
why
I
always
ask
myself
when
I
start
a
new
project,
am
I
going
to
use
this
project
myself
in
my
own,
you
know
side
projects
or
company
or
or
businesses.
B
Am
I
going
to
use
this
long
term,
and
if
the
answer
is
yes,
then
I'm
confident
that
I'm
going
to
be
able
to
dog
food,
my
own
library,
and
that's
that's
what
makes
you
a
good
contributor,
I
think,
is
knowing
how
to
use
it
in
the
real
world,
knowing
its
limitations
and
maybe
where
it
could
be
better
right.
If
you
don't
have
any
of
that
experience
using
a
tool
you're,
not
necessarily
going
to
know
how
to
fix
the
tool
very
well.
A
And
you've
been
a
maintainer
for
at
least
a
year
now,
obviously
throughout
query,
what
are
some
of
your
top
tips
that
you've
learned
from
maintaining
this
project
that
you
would
give
to
other
maintainers
top
tips
around?
Possibly
the
discord
discussions,
or
just
whatever
kind
of
top
tips.
You've
got
for
maintainers,
maintaining
their
projects.
B
B
Do
you
know
requiring
your
users
and
setting
up
the
expectation
to
use
code
sandbox
to
replicate
issues
and
making
that
easy
for
people
to
do?
You
know
it's
all
about
cutting
that
feedback
loop
down
to
the
smallest
amount
of
time
possible?
For
someone
to
tell
you
you
know
this
is
wrong.
It
needs
to
be
better
and
you
can
make
it
better
and
the
faster
that
you
can
go
through
that
cycle.
The
faster
your
open
source
library
is
going
to
be
able
to
grow.
A
Yeah,
I
think
that's
a
really
really
key
good
point.
You
know
we're
just
reducing
that
time,
because
obviously
people,
if
people
there
wanting
to
contribute,
they
want
to
know
that
that
as
a
maintenance,
you're,
the
one
that
you're
hearing
them
and
that
you're
actually
is
that
yes,
there's
a
good
contribution
or
no
it's
not
or
hank.
We
tweet
this.
If
we
tweak
that,
so
I
think
you
know
definitely
reducing
that
feedback.
Time
is
really
really
helpful.
B
Yeah,
if
you
are
going
to
start
a
new
project
in
the
beginning,
it's
very
easy
to
you.
You
have
to
have
full
ownership
of
that
code
in
the
very
beginning.
It's
it's
all
you
and
you
can't
really
expect
anybody
else
to
help
you
or
step
in
and
that
can
go
on
for
quite
a
while.
It
could
be
months
or
years
that
that
happens.
B
Even
if
your
project
gets
very,
very
popular,
you
might
be
the
only
person
that
can
actually
do
anything
about
problems
or
make
it
better,
and
you
think
that
might
that
might
be
the
hardest
part,
but
it's
actually
not.
In
my
opinion,
the
hardest
part
comes
when
the
community
starts
to
grow
and
you
do
get
contributors
and
people
who
want
to
help
there.
B
B
At
least
they
took
me
by
surprise
after
these
libraries
got
a
lot
of
traction,
so
nailing
that
down
early
on
and
really,
I
think
the
best
advice
I
can
give
is
just
be
kind
and
remember
that
it's
just
code
and
no
no
code
is
sacred
code.
You
know
the
we're
all
in
this
to
make
the
world
a
better
place
and
as
long
as
you're
making
the
software
the
best
it
can
be
to
help
other
people.
That's
really
what
matters
the
most
so
get
rid
of
your
ego
before
you
walk
in.
A
A
There
is
something
that
startups
experience
a
lot
too,
which
is
when
you're
growing
from
you
know
it's
much
easier
to
grow
from
one
to
ten
people
in
a
startup
or
one
to
twenty
people
than
it
is
to
grow
from
20
to
40
or
20
to
50.,
because
once
you
grow
to
that
size,
you
start
experiencing
all
things
that
you've
mentioned.
You
know
the
community
wants
to
get
involved.
How
do
you
you
know,
sort
out
disputes?
How
do
you,
you
know,
sort
out
clashes
in
culture
and
personalities,
and
how
do
you
actually
say
like?
A
A
A
B
B
B
B
We
we
reverse
engineer:
google
search
results
at
scale
so
for
very
large
fortune,
500
sized
companies
who
have
data
analysts
and
people
who
are
just
really
data
hungry
and
data
junkies.
They
need
all
of
this
data
at
scale,
so
they
can
make.
You
know
informed
decisions
for
their
marketing
team
and
seo,
and
we
are
one
of
the
very
few
companies
that
can
actually
supply
that
data
at
the
scale
that
these
companies
need.
So
we
are
just
crawling.
B
B
We
provide
that
back
to
people
either
through
an
api
or
obviously
the
front
end,
which
is
where
I
come
in
so
from
day
one
I
have
been
all
all
front
end,
so
all
ui
and
ux
for
nozzle,
and
I
have
one
employee
who
is
helping
me
now,
but
we
together,
we
have
built
all
of
the
application
and
marketing
and
front
end
everything
for
nozzles.
So
it's
been
a
lot
of
fun.
B
A
Coders
and
stuff
you
like
get
into
like
stops
and
things
it's
like
you
just
have
like
really
nice
websites,
everybody
just
looks
amazing,
so
nice
work
and
now
I've
got
a
question
from
the
chat
as
well,
which
is
back
onto
github
as
well.
So
if
you
want
go
check
out,
tana's
really
really
cool
startup
nozzle
I've
put
the
link
in
the
chat.
Is
there
as
well,
but
we've
got
a
question
from
the
chat
and
then
we're
gonna
finish
up
on
a
couple.
B
A
Yeah
so
so
essential
once
you
so
basically
there's
two
types
of
github
right:
there's,
github,
private,
there's,
github
public.
So
any
public
thing,
and
actually
I'm
going
to
ask
you
this
tanner
as
well.
Any
public
repo
is
publicly
available
technically
speaking,
that
doesn't
necessarily
mean
it's
open
source,
though.
A
So,
if
you
want
something
to
be
open
source,
you
need
to
have
an
open
source
license
that
states
that
your
code
is
open
source
that
allows
other
people
to
use
it
and
allows
and
says
that
you're
giving
everyone
else
a
license
to
go
and
use
that
there's
lots
of
really
cool
ones,
but
why
I
got
google
hours.
I
wanted
to
hear
from
tana
what
you
use
for
your
open
source
license
and
which
one
you
chose
for
your
open
source
license
for
react.
Query.
B
A
So
we've
got
the
mit
one
here,
so
you
can
grab
this
on.
We
also
have
the
other
one
that
I
just
posted
in
the
chat
for
those
people
who
are
keen
to
have
a
look.
Is
this
one
called
literally
choose
a
license,
so
the
mit
one
is
on
there,
but
it
basically
goes
through
like
what
you're
doing.
This
is
actually
a
very
interesting
point,
because
lots
of
people
have
no
idea
about
open
source
licensing
so
yeah.
A
Basically,
you
need
to
choose
a
license
that
gives
everyone
else
ownership
or
you
like
use
of
going
out
and
using
that
code,
because
if
you
just
put
up
a
public
repo
and
there's
no
license
on
it,
theoretically,
people
can't
go
and
then
open
source
to
everyone
else,
because,
as
the
writer
you
haven't,
given
everyone,
the
the
the
license
to
go
and
actually
use
that.
So
that
is
one
big
thing
is:
oh
there
you
go
glenn
say
thanks
for
making
it
mit,
then.
A
A
So
here
is
your
open
source
license,
so
everyone
needs
to
make
sure
you've
got
one
there
you
go.
Yours
is
the
mit
one
licensed
under
mit.
So
it
says
here
that
basically
tana
and
the
team
are
providing
this-
that
you
can
use
it
for
commercial
use,
modification
distribution
and
private
use.
There
is
no
liability
and
warranty
on
it
and
obviously
everything
is
written
down
here.
So
it's
really
really
easy
and
just
make
sure
you
have
it.
B
No
well,
I
actually,
I
have
been
looking
into
something
called
dual
licensing
lately,
so
not
for
react
query,
but
for
some
other
projects,
I'm
working
on
that
are
more
of
like
an
enterprise
product,
so
there
would
definitely
be
more
businesses
that
would
be
interested
in
using
it
than
just
kind
of
hobbyists
or
open
source
projects,
and
that
would
be
an
interesting
discussion.
We'd
probably
have
to
have
later.
B
But
it
sounds
really
exciting
to
me
because
I
know
there.
I
are
a
lot
of
businesses
that
use
my
open
source
software
and
when
I
see
those
business
names
I
kind
of
like
wow,
I'm
so
excited
that
they're
using
my
software
and
then
I'm
like
wow.
I
wish
they
could.
You
know,
donate
like
a
thousand
dollars
to
the
project
or
something
and.
A
B
B
Github
sponsors
has
been
great
and
it's
been
great
because
I
think
it's
enabled
more
businesses
to
contribute
back
to
open
source,
and
I
think
that's
been
the
biggest
problem
and
github
sponsors
is
not
technically
perfect.
I
have
calls
with
github
r
d
and
and
people
who
want
feedback
on
on
sponsors
all
the
time,
and
one
thing
I'm
always
telling
them
is
that
I
hope
very
soon
or
in
the
near
future
that
github
sponsors,
in
my
opinion,
should
should
be
better
built
to
help
sponsorships
from
companies
and
businesses.
B
B
We're
really
just
kind
of
moving
money
around
between
ourselves
right.
So
it's
like
open
source
money,
just
kind
of
circulating
and
what's
going
to
solve
kind
of
all
that
burnout
and
all
of
that
open
source
sustainability,
stuff.
That
kind
of
gets
talked
about
here
and
there
is,
is
having
more
money
come
in
from
businesses
that
that
are
using
open
source
software
and
being
very
successful.
So.
A
To
just
put
the
license
back
onto
the
licensing
is
that
licensing
is
boring
but
required,
and
we
could
literally
spend
hours
sitting
here
talking
about
licensing
copyright
iop,
but
yeah.
We
won't.
We've
only
got
about
a
few
minutes
left
so
turn
out
to
end
us
off.
I
would
like
to
you
to.
It
was
a
really
brief.
I
don't
know
how
long
the
story
is,
but
just
give
us
a
brief
insight
in
how
you
got
involved,
firstly
in
coding
and
then
secondly,
in
open
source.
B
Well,
in
high
school
I
wrote
my
first
html
and
it
wasn't
css
files
back
then,
but
my
first
styles
right
and
that
that
came
very
naturally
to
me
and
I
never
really
considered
it
to
be
like
a
career
path,
though
it
was
a
lot
of
fun.
Javascript
wasn't
super
powerful,
then
so
it
kind
of
wasn't
as
big
a
deal
as
this
today,
but
it
was
definitely
there
and
but
at
the
time
I
wanted
to
get
into
film
and
audio
engineering.
B
I
went
to
school
for
film
and
audio
engineering
for
a
while.
Actually
until
I
ran
out
of
money,
couldn't
go,
couldn't
keep
going
to
school
and
instead
of
going
into
debt,
I
decided
I
was
going
to
try
and
work
my
way
through
school
and
that's
when
I
decided
that
building
websites
was
actually
a
very
lucrative
way
to
make
money-
and
I
was
pretty-
I
was
pretty
good
at
it.
So
I
started
building
websites
and
eventually
you
know,
worked
my
way
into
the
wordpress
scene,
building
wordpress
sites
very
low
code
coding.
B
A
B
I
was
the
very
first
employee
of
my
own
startup
doing
all
the
front-end
work
and
then
eventually
I
became
a
co-founder
and
then
it
was
time
to
migrate
to
react
because
angular
1x
was
just
getting
old
and
angular
2
was
dragging
its
feet
for
a
couple
years,
so
yeah
that
that's
kind
of
the
quick
story
of
how
I
got
into
coding
in
general
and
react
from
there.
My
open
source
work
really
took
off.
When
I
contributed
to
chart
js,
I
needed
a
charting
library.
B
B
Yeah
and
really
chart
js
is
where
kind
of
things
really
took
off
after
that
chart.js
was
fun.
I
wanted
to
start
something
new,
so
I
got
into
I
started:
building
some
things
around
crossfilter
from
square
which
is
now
deprecated,
I
believe,
and
then
about
a
year
later
I
built
react
table,
and
that
was
the
very
first
library
I
had
that
really
took
off
after
react
table.
B
A
That
is
very,
very
cool.
I
like
how
like
everything's
just
kind
of
like
flown
from
one
to
the
next.
If
you
say
like,
I
just
started
building
websites
and
now
I'm
like
an
open
source
maintainer,
it
kind
of
like,
doesn't
really
compute.
But
when
you
talk
about
each
step,
you
know
you're,
like
yeah.
I
can
really
see
how
each
one
you
know
float
onto
the
next
and
how
you're
just
kind
of
like
at
the
right
point
in
time.
A
For
those
things,
I
think
that's
what
a
lot
of
people
don't
like
realize
that
you've,
you've
kind
of
you've
got
to
do
those
things
at
the
very
start.
You've
got
to
just
start:
you're,
building
random
websites
and
random
wordpress
plugins
and
finding
an
open
source
project
that
is
really
cool
that
you
want
to
use
that
you
then
go
hey.
A
It
could
be
better,
let's
fix
it
and
build
this
cool
thing
for
it,
and
I
think
that's
how
a
lot
of
people
get
into
open
source
now
to
end
us
off,
because
we're
nearly
there
at
the
end.
But
I
will
take
any
last
minute
questions
from
the
chat
as
well.
But
my
final
question
to
you
is
your
journey.
Is
amazing
and
you've
come
here
and
built,
so
many
really
cool
things
and
you've
got
to
start
up
you're
working
round
query
and
you've
got
this
really
really
cool
portfolio.
A
Underneath
you,
what
are
your
top
tips
for
people
who
are
sitting
there
going?
I
want
to
be
like
that.
I
want
to
learn
how
to
code
like
that.
I
want
to
get
involved
in
open
source
like
that.
What
are
your
top
tips
for
people
who,
like
maybe
haven't,
got
any
kind
of
any
kind
of
experience
in
that
kind
of
sector
or
what
are
your?
What
are
your
tips
and
advice
to
those
kind
of
people.
B
That's
when
open
source
becomes
a
gold
mine.
You
know
you
can
build
so
much
with
open
source
software
these
days
and
you
know,
but
you're
not
going
to
unless
you
have
to
so.
I
don't
know
for
me
personally.
I
think
the
best
motivation
for
learning
open
source
is
starting
a
business
and
trying
to
build
something
from
nothing
and
open
source
tools
are
going
to
be
essential.
A
We've
had
10
in
the
chat
said
very
nicely
said,
so.
Thank
you
for
that
tana.
I
want
to
thank
you
for
your
time
today
on
open
source
friday
chat.
Is
there
any
last
minute
words
or
thoughts?
Shout
outs
that
you'd
like
to
give
out
to
the
community
and
anyone
else,
who's
gonna
watch
the
recording
afterwards.
B
No,
not
really
just
go
check
out,
react
query
if
you
want
to
yeah.
If
you
want
to
make
me
happy,
go
check
out,
react.
Query
you
can
buy
my
course.
I
have
an
essentials
course
for
ref
query
right
there
on
the
homepage
of
it.
You
can
follow
me
on
twitter.
You
could
become
a
github
sponsor.
If
you
are
a
business
that
uses
my
software,
please
become
a
sponsor.
I
even
have
awesome
perks
for
people
who
become
sponsors.
B
B
A
I'm
not
even
following
you
yet
there
you
go
I'll,
give
you
a
follow
on
the
stream
everyone.
Everyone
else
say
that
I'm
following
you
so
again.
Thank
you
so
much
for
your
time
on
the
open
source,
friday
stream.
Today
we
absolutely
love
having
you
here
and
chatting
to
you.
I
loved
some
of
the
things
that
you
spoke
about,
which
is
you
know,
give
yourself
a
challenge.
If
there's
a
project
that
you're
already
contributing
to
or
a
project
you're
sorry
you're
already
using
go,
contribute
to
it,
learn
something
about
it.
A
If
you're
starting
your
project
yourself
just
get
out
there
and
just
promote
it
as
much
as
you
can
talk
about,
it
start
building
it
and
when
it
gets
to
the
point
where
you
are
building
a
community,
you
just
gotta.
Let
go
of
your
ego.
Let
go
of
your
sacred
code
because
there's
no
such
thing
as
sacred
code,
it's
all
open
source.
Let
go
of
that
and
just
like
send
it
out
to
the
community
and
just
you
know,
watch
it
go.
You
know
just
send
off
your
little
baby
out
into
the
wild.
A
As
santa
said
again,
startup
discord
server.
It's
a
really
really
good
place
to
collaborate
with
your
community,
enable
discussions
on
your
repo
set
up
your
issues
really
well
and
don't
forget
if
you
are
starting
or
you're,
maintaining
or
you're
wanting
to
run
an
open
source
project,
don't
forget
to
choose
a
license
for
it,
because
otherwise
people
can't
technically
use
it.
So
again,
I
want
to
thank
you
for
being
on
here
tana.
It
was
really
really
great
to
have
you.
Thank
you
for
staying
up
late.
I
know
it's
like
10
p.m.
A
Right,
stick
around
the
zoom,
we'll
have
a
quick
chat
afterwards
and
to
everyone
else
again,
thanks
so
much
again
for
being
here,
it
has
been
absolutely
awesome
to
have
you
all
on
the
stream
don't
forget
to.
If
you
haven't
already
give
us
a
follow
on
the
github
twitch
channel
and
don't
forget
to
go
on
to
our
virtual
meetups
page
and
actually
sign
up
and
be
part
of
our
virtual
meetup
group,
because
we
put
in
all
our
meetups
that
are
happening
for
open
source
friday,
so
the
next
one
will
be
happening
this
time
next
week.
A
I
believe
I
can't
even
remember
who
we've
got
on.
We've
got
cool
people
coming
on
the
stream.
Don't
forget,
there's
also
the
one
happening
on
the
american
time
zone
for
all
those
americans
in
the
channel
in
the
chat.
The
next
one
on
our
american
time
zone
is.
Let
me
have
a
quick
look
for
you.
We
have
bdoggie
we'll
be
chatting
to
one
of
our
people
from
the
github
command
line.
I
believe
it
looks
like
we've
got
on.
A
Oh
nope,
we've
got
create
react
app.
One
of
the
maintainers
of
create
react
app
and
we've
got
my
colleague
b.
Dougie
is
talking
to
them
friday
morning,
american
times,
if
you're
on
the
american
time
zone
go
check
that
out
and
also
as
we
mentioned
before,
we've
got
meetups
happening
on
lots
of
different
time
zones.
We've
got
africa,
russia,
india,
a
few
others
happening
as
well,
where
we
showcase
you
some
of
the
really
cool
things
that
are
coming
out
of
github
but,
more
importantly,
we
showcase
really
cool
developers
from
the
community.
A
We've
got
developers
in
each
of
those
places
coming
in
and
giving
their
story
and
finally,
for
those
gamers
out
there
in
the
channel
we
have
our
github
game
off
is
about
to
start
so
on
the
first
of
november,
the
github
game
of
2020
will
commence.
So
if
you
would
like
to
be
part
of
that
this
year,
we've
got
over
1200
people
who
have
already
signed
up
for
that.
The
theme
this
year
is
going
to
be
very,
very
cool.
A
I
know
what
it
is,
but
it's
not
announced
yet
but
go
join
the
game,
jam
and
yeah
sign
up
today.
It's
gonna
be
really
fun.
There's
no
winners.
We
like
to
showcase
all
the
cool
things
in
the
community.
Basically,
if
you
submit
a
game,
the
community
judges
you
and
if
you
submit
you,
get
to
judge
everyone
else
as
well.