►
From YouTube: Opening Keynote - GitHub Satellite 2017
Description
We kicked off GitHub Satellite with a keynote by GitHub CEO & Co-founder Chris Wanstrath and Platform Engineering Manager Kyle Daigle. They shared a few platform updates, including the launch of GitHub Marketplace, a new way to discover and buy the apps you need to customize any workflows.
At Satellite 2017, attendees came to exchange cutting edge practices on how to bring together the people and tools you need to build great software. Watch the recordings to find out what GitHub's been working on, and hear how other teams use the GitHub ecosystem to customize the way they work.
We'll be getting together again in San Francisco on October 10th-12th for GitHub Universe. We hope you'll join us for three days filled with the creativity and curiosity of the largest software community in the world.
For more information, go to githubuniverse.com.
A
Good
morning
good
morning,
thank
you
welcome
to
github
satellite,
it's
so
amazing
to
be
here
today.
This
has
been
a
long
journey
for
a
lot
of
people.
A
lot
of
hard
work
has
gone
into
this
so
before
we
begin
talking
about,
what's
up
what
we've
been
working
on?
What's
coming
for
the
few
couple
days
that
we
have
together,
I
really
just
wanted
to
start
with
a
huge
shout
out
to
the
github
events
team,
to
to
kelsey,
to
chris
kelly,
to
drew
to
brittany
to
everyone
that
helped
put
this
thing
together.
Thank
you.
A
So
this
is
me,
there's
some
cool
animations,
so
there's
a
lot
of
cool
stuff
happening.
If
this
is
your
first
time
joining
us
welcome.
If
this
is
your
second
time,
if
you
were
here
for
github
satellite
in
amsterdam
last
year,
welcome
back,
there's
gonna
be
a
lot
of
great
sessions.
Today,
we've
got
this
stage
here.
We
also
have
another
stage
across
the
way.
Over
there
check
out
the
website
check
out
the
the
lineup
there's
gonna
be
a
lot
of
great
talks.
Don't
miss
the
closing
keynote
tonight.
A
A
There's
a
big
there's,
a
big
area
with
chairs
and
tables-
and
it's
called
ask
github-
and
this
started
for
us-
is
like
a
single
little
booth,
where
we
kind
of
had
some
support
people,
some
sales
people
and
you
could
come,
you
could
chat
with
them.
Ask
them.
Questions
turns
out.
People
like
that,
and
we
like
it
too,
so
we've
really
grown
it,
and
now
we
have
support.
We
have
sales.
We
have
a
bunch
of
different
groups
that
are
out
there.
A
People
that
work
for
github
go
say,
hello,
go
talk
to
them,
go
ask
questions,
and
we
also
have,
as
I
mentioned
our
support
team
here,
so
we're
doing
a
little
bit
of
a
survey,
a
community
survey
to
try
to
help
shape
the
future
of
our
own
support
and
figure
out
like
what
do
you
all
want?
What
do
you
all
need?
You
know,
how
can
we
do
better
at
support
and
particularly,
if
you're
here,
what
are
your
needs
and
what
are
some
things?
We're?
Maybe
not
thinking
about.
A
A
A
Also,
thank
you
to
our
sponsors.
Obviously
this
is
a
github
produced
event,
but
you're
here
there's
a
lot
of
different
people
that
are
involved
in
making
this
happen
inside
github
and
outside
github,
and
so
you
can
go
out
to
the
courtyard.
You
can
see
some
of
the
fine
food
that
our
sponsors
have
helped
us
sort
of
curate.
You
can
also
go
into
the
main
area
over
there
and
see
some
of
the
booths,
and
some
of
things
like
that,
so
huge.
Thank
you
to
all
of
our
sponsors.
A
If
you
haven't
checked
out
any
of
these
companies,
yet
there's
going
to
be
people
here
that
can
answer
your
questions
and
talk
to
you
about
them,
they're,
all
pretty
great,
and
if
you're
building
any
sort
of
software
you
can
find
a
use
for
all
these
things
and
what
you're
doing
so.
We
wanted
to
talk
a
little
bit
today
about
like
what
is
the
point
of
this
event.
What
is
the
point
of,
let's
say
github?
Where
are
we
going
and
a
little
bit
around?
How
do
we
think
about
the
future?
A
How
do
we
think
about
github
itself?
And
so
lately
we've
been
talking
a
lot
about
this
idea
of
an
open
ecosystem,
as
you
can
see
from
the
slide.
So
it
has
to
be
true
because
it's
up
on
the
screen,
but
what
we
mean
by
this
is
really
this
idea
of
when
github
started,
git
already
existed,
it
was
an
open
source
project
and
I
was
a
big
fan
of
git.
A
My
co-founders
were
big
fans
of
git,
but
we
found
it
a
little
bit
difficult
to
use
and
to
share
code
with
other
people,
and
so
that's
really
where
github
came
from
is
we
wanted
an
easier,
more
approachable
way
to
share
code
and
work
with
others,
and
we
were
big
open
source
fans,
but
we
were
also
really
forced
into
this
world
of
git
because
it
was
already
there,
and
by
that
I
mean
immediately.
We
had
people
that
were
using
the
site
that
were
using
windows.
A
They
were
using
linux,
they
were
using
mac
because
git
itself
had
so
many
different
clients,
so
many
different
options,
so
many
different
ways
to
interact
with
it
and
use
the
protocol.
Github
was
sort
of
grandfathered
into
that
is
we
inherited
this,
this
really
great
ecosystem
and
we
immediately
became
a
part
of
it
without
really
doing
much
and
so
over
the
past
nine
years,
because
github
actually
just
turned
nine
in
april,
which
is
pretty
amazing,
but
over
the
past
nine
years
we've
tried
to
embrace
this
fact.
A
I
mean
we
are
first
and
foremost
a
company,
that's
for
developers
and
was
started
by
developers
and
so
there's
a
lot
of
philosophies.
We've
learned
through
building
software
that
we
wanted
to
carry
forward,
but
also
we
just
think
this
is
a
huge
advantage
to
us
is
that
if
we
can
be
a
part
of
this
ecosystem,
you
know
if
we
can
help
lift
up
the
git
community
and
help
participate
and
make
software
development
better
for
our
peers
for
even
some
of
our
competitors.
A
So
these
are
some
of
our
numbers.
You
can
see
that
they
are
numbers
but
they're,
pretty
cool
right.
So
when
github
started
there
was
only
a
couple.
People
using
it,
and
really
we
thought
the
market
or
the
opportunity
for
git
were
a
couple
thousand
people
who
wanted
to
build
software
in
a
weird
way
and
were
like
creepily
into
cats.
A
I
guess
turned
out
a
lot
of
people
really
like
cartoon
cats
and
a
lot
of
people
really
like
git,
and
so
we
can
see
there's
over
21
million
people
using
github
every
day
with
with
authenticated
accounts.
This
is
not
to
say
anything
other
people
that
are
logged
out
and
what
they're
working
on
are,
as
you
know,
millions
and
millions
of
projects
which
we're
really
proud
of,
but
I
think
a
lot
of
websites
or
companies
would
use
a
stat
like
this
to
show
their
own
success
and
yeah.
A
Github
is
really
big
and
it's
been
it's
bigger
than
we
could
have
ever
hoped
for,
and
for
that
it's
it's
like
amazing,
but
when
I
look
at
these
numbers,
I
don't
think
that
this
is
necessarily
a
product
of
of
github
success.
This
is
not
me
sharing
with
you
how
the
company
has
been
doing
in
ra
ra.
This
goes
to
show
that
we're
part
of
something
that's
really
massive.
A
I
we
see
reports.
I
see
reports
of
how
many
software
developers
there
are
in
the
world
and
it's
from
companies
that
are
paid
to
do
research
and
they
try
to
figure
out
how
many
jobs
there
are
that
are
classified
as
developers
and
and
this
and
that,
and
they
come
out
with
a
number
and
number
we
hear
often
is
20
million
developers.
A
We
hear
there
are
20
million
professional
developers
in
the
world,
so
we
have
21
million
people
using
github,
and
so
either
there
are
more
people
on
github
than
there
are
developers
in
the
world
which
I
refuse
to
believe
or
we
we
really
don't
know
what's
going
on
out
there
and
I
think
that's
actually
closer
to
the
truth
is
our
classical
definition
of
a
software
developer
is
changing.
A
lot
of
the
jobs
are
changing.
A
A
lot
of
the
work
is
changing
and
I
I
think,
probably,
if
there's
ever
a
reason
or
a
platform
in
which
to
say
you're
preaching
to
the
choir.
This
is
it
right
now,
but
it's
real
right,
like
our
numbers,
are
bigger
than
the
numbers
that
we're
being
told
represent
the
entire
industry,
and
while
I
think
github
is
a
really
big
deal,
no
one
thinks
github
is
the
entire
industry.
So
software
development
is
still
growing
and
it's
still
kind
of
hard
to
understand.
A
It's
growing
at
a
very
rapid
rate
and
we
don't
all
really
understand
or
see
every
piece
of
it
and
to
me,
that's
exciting
to
me
that
says
that
there's
a
lot
of
opportunity
there
for
software
developers
for
companies,
but
what's
more
exciting
to
me,
is
what's
going
to
come
out
of
that.
What
are
the
projects
people
are
going
to
make?
What
are
the
innovations
people
are
going
to
come
up
with?
What
is
the
technology
that
someone's
going
to
invent?
That's
so
maybe
someone
here,
maybe
someone?
A
So
a
part
of
that
is
tied
into
our
philosophy.
We
call
it
meeting
you
where
you
are,
but
we've
always
wanted
to
get
up
to
feel
like
whatever
tools
you
use
whatever
operating
environment,
you're
working
in
whatever
sort
of
developer
you
are,
we
want
it
to
feel
like
github
works
for
you.
If
you're
a
windows
developer,
building
c-sharp
applications,
we
want
to
get
up
to
like
really
well
in
your
visual
studio
environment
if
you're
using
linux
and
you're
all
in
vim
and
you're
just
using
the
terminal.
A
We
want
that
to
be
a
very
premier
experience
for
you.
We
want
to
feel
like
very
first
class
and
if
you're,
somewhere
else,
if
you're
using
a
mac-
and
you
want
to
use
a
gui
client
and
maybe
you're-
writing
a
lot
of
python
or
something
we
want
you
to
feel
like
github
is
there
for
you
and
it
really
integrates
into
your
workflow,
and
this
is
a
lot
of
what
we
mean
when
we
talk
about
an
open
ecosystem.
A
So
why
are
we
here
today?
Well,
github
is
a
lot
of
things,
and
one
of
them,
like
I
said,
is
the
community
and
we're
not
just
in
the
united
states,
we're
not
just
in
north
america.
Github
is
very
much
a
global
community
and
one
of
the
reasons
that
we're
here
today
in
europe
is
because
you're
here
in
europe,
because
the
community
is
here
in
europe.
Over
the
past
year,
we've
had
over
30
percent
in
in
europe
alone.
A
To
our
website,
so
we
have
tons
of
big
enterprise
customers
here.
There's
tons
of
open
source
happening
here,
but
ultimately
you
know
just
because
our
headquarters
is
in
san
francisco
doesn't
mean
that
that's
where
a
lot
of
the
community
is
or
where
a
lot
of
the
growth
is,
and
in
fact
we
see
tons
of
growth
from
asia
and
tons
of
growth
from
europe.
A
So
it's
super
exciting
to
us
to
see
this
sort
of
like
community
growing
all
over
the
world,
but
we
also
have
always
felt
that
a
big
part
of
github
is
what's
online
what's
on
the
web,
but
a
bigger
part
of
github
is
what's
here
in
reality.
What's
here
in
meat
space,
what's
what's
here
physically,
and
so
we
want
to
be
on
the
ground
meeting
with
you
talking
with
you
sort
of
figuring
out
where
you
live
and
how
you
like
to
work.
So
we
can
start
to
integrate
that
back
into
what
we're
building.
A
A
Also,
these
are
our
top
five
countries
in
europe.
So
if
you're,
not
in
one
of
these
countries,
go
tell
all
your
friends
right.
So
these
are
the
most
popular
european
countries
using
get
up
today.
There's
a
lot
of
opportunity
there.
If
you
live,
I
don't
know
anyone
from
czech
any
other
countries
there.
A
Let's
get
some
more
numbers
on
there
anyway,
over
the
past
year,
we
certainly
been
growing
geographically,
but
we've
also
been
trying
to
embrace
this
ecosystem
idea
in
more
ways
than
just
a
keynote
talk
and
slides,
we've
actually
been
trying
to
go
and
figure
out.
What
does
it
really
mean
to
see
what
someone's
environment
is
like
and
integrate
into
it
in
a
way
that
feels
very
natural
to
them
and
one
place
where
we
know
that
we've
been
really
missing
out
over
the
past
nine
years
is
game
developers
is
like
unity?
A
Is
this
massive
platform
that
people
are
using
to
build
all
sorts
of
mobile
games
and
desktop
games
today,
and
so
we
now
have
a
github
integration
in
unity,
which
is
pretty
awesome.
You
can
check
it
out
it's
available
online,
but
for
us
this
is
an
example
of
people
are
building
software
using
unity,
and
we
want
their
experience
on
github
to
feel
very
natural.
We
don't
want
to
be
in
the
way.
We
don't
want
to
be
a
hurdle
or
a
barrier.
We
really
want
to
be
the
opposite
of
that.
A
We
want
github
integration
in
unity,
to
unlock
doors
and
to
really
lower
barriers
for
people,
and
so,
if
you're,
a
game
developer,
if
you've
been
playing
with
unity,
if
you're
interested
in
anything
like
that,
we
have
github
integration
available.
Now
you
can
check
it
out.
It's
pretty
awesome
if
you're,
not
a
game
developer,
if
you've
never
tried
this
stuff,
but
if
you've
ever
been
interested
in
games
check
out
unity,
it's
a
really
great
framework.
It's
a
great
place
to
start.
A
There's
a
really
great
community
built
around
that
we're
trying
to
be
a
big
part
of
that,
and
I
think
it's
going
pretty
well.
Similarly,
I
already
kind
of
mentioned
the
c-sharp
developers
sort
of
the
microsoft
world.
If
you've
been
reading
the
news
lately,
you
probably
have
learned
that
I
guess
microsoft.
How
do
you
say
this?
I
don't
know
microsoft
was
killed
and
replaced
by
a
clone
who's
like
much
friendlier
to
open
source.
I
guess
and
has
very
different
ideas.
A
It's
very
strange
transition
they've
gone
through
in
the
past
couple
years,
but
it's
a
whole
different
company
and
they're
embracing
open
source
in
a
very
real
way.
They're
embracing
linux,
they're
part
of
the
linux
foundation
now
and
so
we've
become.
We've
become
great
friends
with
them,
and
one
of
the
best
parts
of
that
is
this
opportunity
for
us
to
sort
of
understand
their
ecosystem,
their
development
platform
a
bit
more
and
to
help
make
that
better,
and
so
now
visual
studio
ships
with
github
integration.
You
can
find
it
online.
We're
really
excited
about
it.
A
Visual
studio
itself
just
started
recently
shipping
for
mac.
So,
even
if
you
don't
have
windows,
you
can
start
participating
in
the
microsoft
ecosystem
and
again
this
is
just
an
example
for
us
of.
We
want
github
to
come
to
you.
We
want
it
to
work
where
you
are,
and
even
if
it's
in
a
part
of
development
that
hasn't
really
felt
touched
or
reached
out
to
by
github
in
the
past,
we're
working
to
to
get
in
there
and
make
it
feel
very
native.
A
Does
anyone
here
use
adam
a
couple?
People
all
right,
cool,
cool,
hello,
everyone?
So
there's
this
thing
called
atom.
It's
a
hackable
text
editor
for
the
21st
century
22nd.
I
hope,
but
21st
right
now
so
adam
for
us
has
always
been
sort
of
a
an
ideal.
It's
this
it's
this
really
amazing
piece
of
technology,
but
it's
also
open
source.
It's
also
hackable.
It's
also
has
a
community
behind
it
and
we
always
just
thought
it
was
really
cool.
A
We
always
thought
it
would
be
something
that'd
be
very
useful
to
anyone
who
wanted
to
be
a
developer,
but
we
were
never
kidding
ourselves
with
I'm
sure.
A
lot
of
people
use,
vim
or
emacs
or
sublime
like
an
editor,
is
a
very
personal
choice,
so
we
never
really
launched
adam
with
the
expectation
that
every
hand
would
be
raised.
I
don't
think
that
there's
going
to
be
any
developer
software
ever
where
everyone
uses
it,
it's
kind
of
one
of
the
awesome
parts
about
development.
Is
we
all
use
our
own
tools?
A
We
can
modify
them
and
whatnot,
and
yet
adam's
growth
and
adam's
success
has
really
blown
us
away,
and
it
kind
of
reminds
me
a
little
bit
of
you
know
we
started
github,
we
wanted
some
people
to
use
it
and
a
lot
of
people
used
it,
and
that
was
amazing.
Adam
adam
has
a
similar
story
and
you
know
when
we
talk
about
the
ecosystem.
When
we
talk
about
meeting
you
where
you
are
yeah,
it
does
mean
a
github
integration
inside
unity.
A
We
always
want
everyone,
whether
they're,
the
beginner,
that's
learning
at
the
very
first
day
or
they've,
been
programming
for
30
years
to
have
access
to
the
same
power.
What
we
want
to
do,
though,
is
help
guide
the
approach
to
learning
how
to
use
that
software
or
using
it-
and
I
think
adam-
is
a
great
example
of
that
atom
is
a
really
powerful
piece
of
software.
It's
very
professional.
You
can
use
it
for
all
sorts
of
real
development,
but
it's
also
really
great
to
just
get
up
and
running
on.
A
It's
costs:
zero
dollars,
it's
open
source,
a
lot
of
classrooms,
use
it
it's
a
great
educational
tool,
and
if
you
learn
on
adam-
and
you
learn
a
lot
of
the
principles
in
that
text,
editor,
you
can
definitely
switch
to
something
else.
I
think
the
reality
is.
I
have
like
three
text
editors
in
my
task
bar.
I
don't
even
code
that
much
anymore,
so
a
lot
of
people
are
using
more
than
one
text.
A
Editor
and
atom
is
a
really
great
place
to
get
your
foot
in
the
door
more
so
than
that
the
growth
is
is
has
just
been.
I
mean
I
don't
even
know
what
to
say.
It's
awesome
at
universe,
get
up
universe.
The
end
of
last
year
we
had
just
about
a
million
people
using
atom,
and
that
was
seven
or
eight
months
ago.
Now
we
have
two
million.
So
in
less
than
a
year,
we've
added
more
than
a
million
active
users
to
adam.
A
So
if
you
want
to
sit
here
and
tell
me
that
there's
20
million
developers
in
the
world
and
10
of
them
are
using
adam,
I'm
just
going
to
tell
you-
I
don't
believe
in
that
there
are
so
many
developers
that
are
just
starting
today
that
are
growing
into
this,
that
are
going
into
all
sorts
of
jobs
and
work
and
using
open
source
and
contributing
to
it.
And
these
numbers
just
don't
lie
there
are
so
many
people
using
adam.
A
We
also
have
a
standalone
client
for
using
github,
because
our
our
dream
has
always
been
yeah.
We
support
the
git
client.
We
have
people
that
work
on
it
all
the
time,
we're
big
fans
of
it,
but
if
you
want
a
gui,
if
you
don't
want
to
use
the
command
line
tool,
we
also
want
to
provide
something
where
you
can
just
get
up
and
running.
So
we've
had
github
desktop
for
a
long
time
and
we
recently
rolled
out
a
new
version
which
is
built
on
electron.
So
now,
github
desktop
is
open
source.
It's
available
on
electron.
A
A
If
you
want
everyone,
I
think
here
knows
about
open
source,
but
we're
really
happy
that
github
desktop
is
now
available
using
electron
and
is
open
source
and
anyone
can
try
it
out
today
modify
it
as
you
see
fit
or
just
play
with
it
as
it
comes
because
it's
pretty
great
piece
of
software
and
I've
mentioned
this
a
few
times
we
have
a
platform
called
electron.
Has
anyone
ever
built
an
app
on
electron?
A
couple
people,
okay,
cool.
B
A
Right,
yeah
whistle
it's
amazing,
so
electron
I
don't
want
to
get
too
into
it,
but
it's
a
platform
for
building
desktop
applications
and
you
use
web
technologies
to
do
it.
So
you
basically
make
desktop
apps
as
web
pages,
but
they
run
locally.
So
you
have
access
to
the
hard
drive.
You
have
access
to
any
of
the
local
operations
you
really
want,
and
even
better
than
that
it
runs
cross-platform
so
like
there
was.
A
This
write
once
run
anywhere
dream
that
I
don't
want
to
bring
anyone
back
to
any
bad
memories
of
their
java
days,
not
not
java.
Today,
but
java
like
15
years
ago.
Electron
is
actually
trying
to
do
that
and
it's
kind
of
working
is
we
have
a
lot
of
companies
now
that
are
building
applications
like
a
slack
or
even
microsoft,
and
with
electron.
These
applications
run
on
windows,
mac
or
linux.
Pretty
much
out
of
the
box.
A
That's
amazing,
but
the
other
thing
we're
seeing
is
a
lot
of
companies
now
are
using
electron
to
build
internal
apps,
and
I
think
for
us
in
our
position
as
github.
We
see
a
lot
of
companies
in
a
unique
way.
We
see
how
they're
using
github
and
what
they're
building
software
with
and
a
lot
of
times
that
turns
into
a
cool
open
source
library
or
a
cool
piece
of
technology,
some
of
which
we're
going
to
talk
about
later
today,
but
sometimes
that
turns
into
novel
uses
or
things.
A
A
What
people
are
using
electron
for
is
really
surprising
us
and
it's
really
amazing,
and
so
we
are
seeing
big
fortune
500
companies
that
are
using
electron
as
a
platform
for
writing
internal
applications
and
they're
increasingly
having
software
developers
build
bespoke
software
for
the
company
for
the
way
they
work
internally
and
a
lot
of
that's
on
a
web
app
a
lot
of
that's
mobile
apps.
I'm
sure
a
lot
of
us
have
interacted
or
even
worked
on
stuff
like
that,
but
more
and
more
we're
seeing
a
lot
of
these
applications
being
built.
A
As
native
desktop
applications
using
electron-
and
that's
that's-
awesome-
we're
really
happy
about
that
anything
that
gets
people
building
more
software,
collaborating
more
we're
really
thrilled
with
and
to
see
electron
as
a
way
for
companies
to
write
their
own
internal
software
that
runs
on
the
web
or
as
a
desktop
application.
That's
really
cool!
A
We
have
electron
conf
coming
soon
in
july
in
seattle,
so
you
can
google
it.
If
you're
going
to
be
in
the
u.s,
you
should
check
it
out.
Otherwise,
you
can
find
the
talks.
You
can
find
out
a
lot
of.
What's
going
on
there,
it's
going
to
be
the
first
one.
We've
done
we're
pretty
excited
about
it,
so
you
know
please
attend
if
you
can,
but
if
not,
there's
going
to
be
a
lot
of
great
content
related
to
electron
coming
out
of
that
in
july.
A
All
right!
So
we're
going
to
go
back
in
time
now
and
talk
about
github
as
a
platform.
We've
always
had
a
hard
time
describing
github,
because
the
very
basics-
it's
like
a
company
and
it's
a
website
and
it's
a
community
and
you
can
just
go
on
and
on
and
on,
and
so
someone's
like
what
is
github
and
you
kind
of
have
to
ask
them
like
well.
What
do
you
know
right?
You're,
almost
like
negotiating
in
a
way
but
like?
A
What
do
you
think
github
is,
and
then
I
can
explain
you
what
I
think
github
is
and
that's
not
a
great
place
to
be,
but
one
of
the
things
that's
been
sort
of
consistent
for
us-
and
I
think
for
a
lot
of
y'all
is
github-
is
a
platform.
Github
is
a
place
where
you
can
build
things
on
top
of
it
and
that
started
really
on
march
12
2008.
So
this
was
about
a
month
before
the
official
launch
of
github
itself,
and
this
is
when
we
rolled
out
our
first
version
of
our
rest
api.
A
This
is
not
pretty.
This
is
not
very
cutting
edge
or
anything
like
that.
But
you
know
websites
have
apis
and
you
build
things
on
top
of
them.
The
reason
we
did
that
was
because
we
are
a
website.
We
want
people
to
build
things
off
of
it,
but
we
also
want
people
to
extend
github,
to
build
additions,
to
github,
to
build
plugins
and
just
do
weird
stuff
with
it,
but
also
productive
stuff
with
it.
A
So
right
away,
we
had
the
api
available,
but
it
wasn't
as
good
as
it
is
today
which
we'll
talk
about
in
a
minute,
but
even
still
github
itself
launched
in
april
2008.
So
the
api
was
available
for
the
official
launch
and
then
we
kept
working
on
the
api
in
the
early
days
and
obviously
it's
not
as
exciting
as
the
fork
queue
or
some
of
the
new
pull
request
stuff.
A
That
was
a
little
bit
less
glamorous,
but
was
getting
a
lot
of
adoption
and
one
of
the
things
we
did
really
early
on
was
we
introduced
web
hooks
to
the
site,
and
so
this
is,
if
you
haven't
used
it.
Basically,
you
can
give
us
a
url
and
when
an
event
happens
on
github
we'll
do
a
post
request
to
the
url
and
we'll
slam
it
with
a
bunch
of
data
json
data,
and
you
can
do
whatever
you
want
with
that.
So
you
can
run
you
can
build
something
you
can
run
a
test.
A
Now
there
were
some
issues
with
the
api
and
the
web
hooks
at
the
time.
The
first
version
of
the
api
does
anyone
remember
this?
We
only
did
200
status
codes.
So
if
there
was
an
error,
you,
like
the
status
code,
was
part
of
the
json
of
what
it
should
have
been,
but
the
actual
header
was
200..
Some
people
didn't
mind.
Other
people
wrote
really
mean
emails
to
us,
I'll,
never
forget
it,
but
it
was
true
and
we
fixed
it
later,
but
the
the
api
was
a
little
rough
at
the
beginning.
A
This
is
also
actually
where
it
started.
We
didn't
roll
out
a
full-on
github
api,
which
is
how
I've
convinced
myself
we
did
do
it,
but
when
we
look
at
the
actual
truth,
that's
not
what
happened.
What
happened
was
we
only
rolled
out
commit
api
at
the
beginning,
and
so
this
is
interesting,
because
I
think
it
really
makes
a
statement
that
how
we
envision
people
building
on
top
of
github
was
getting
access
to
the
get
data
we
wanted
people
to
get
access
to
the
code.
A
That
was
our
first
priority,
and
I
don't
remember
this
as
being
controversial
or
us
not
listening
to
feedback.
I
think
this
was
the
feedback.
It's
people
didn't
really
want
the
oauth
and
the
user
data
on
day.
One.
Of
course
people
wanted
that,
eventually
what
they
wanted
on
day.
One
was
access
to
their
code,
access
to
their
data
and
that's
what
we
gave
them,
and
so
we
really
just
started
with
two
endpoints.
A
Furthermore,
we
started
with
jason.
Of
course,
we
had
xml,
believe
it
or
not
and
yaml.
I
don't
know.
If
anyone
remembers
yellow,
we
actually
had
yaml
endpoints
available
for
the
api,
so
we
were
kind
of
just
doing
whatever
to
get
people
the
data
without
a
lot
of
let's
say,
philosophy
behind
it,
and
there
was
one
page
of
documentation
and
page
might
be
generous.
I
used
really
big
fonts
and
double
spaced
things,
but.
B
A
Wasn't
a
lot
around
there,
so
that's
where
we
were
in
2008.
now
fast
forward,
maybe
four
five
six
years
and
travis
ci
starts
the
private
data
in
august
2012
and
I'm
sure
you
can
talk
to
anyone
from
travis.
Here
things
did
not
advance
dramatically
between
2008
and
2012.
There
were
still
a
lot
of
issues
with
the
api
there.
It
was,
it
wasn't
extremely
mature.
It
wasn't
our
first
priority.
It
wasn't
our
first
order,
our
business.
We
were
very
much
in
a
reactive
mode
around
the
api,
and
I
mean
we
didn't.
A
If
we
only
serve
200
status
codes,
you
can
just
imagine
the
level
of
quality
that
went
into
it.
We
cared,
but
it
wasn't
our
first
priority.
So
travis
starts
building
a
business
based
on
this
api
in
2012.
So
four
years
later-
and
this
for
us
was
a
real
real
big
moment,
because
we
started
to
almost
realize
that
this
is
more
than
just
building
scripts
and
one-offs
and
hacks
and
convenience
things
on
top
of
the
api
people
really
wanted
more
agency
over
their
data.
They
really
wanted
to
interact
with
it.
A
A
lot
more
and
the
other
side
of
that
is
people
could
actually
build
companies.
On
top
of
this
thing,
you
can
actually
create
services
that
work
really
well
with
github,
and
that
could
be
a
business
on
its
own
and
that's
that's
really
amazing
opportunity
and
that's
really
cool
for
us
to
be
a
part
of
that.
A
So
today,
where
we've
gone
in
the
time
since
that
is,
we've
spent
a
lot
of
time
in
the
api.
We've
had
a
lot
of
improvements
to
it.
We
have
things
now
like
a
dedicated
api
blog.
We
have
a
really
cool
pre-release
feature,
but
I
think
there's
a
lot
more.
We
can
be
doing
and
one
of
the
things
that's
really
interesting
today
about
the
api.
A
But
this
is
another
way
to
see
that
too,
is
we
actually
get
more
traffic
to
our
api
to
our
rest,
api
than
we
get
to
our
website,
and
I
don't
know
that.
That's.
I
think
that
a
lot
of
big
companies
have
to
experience,
but
we
do
so
more
and
more.
Our
api
is
becoming
for
us,
not
a
thing
that
we
want
to
roll
out
with
only
200
status
codes,
but
a
thing
that
is
for
a
lot
of
companies
and
a
lot
of
scripts
and
a
lot
of
tools,
it's
their
version
of
github.
A
A
Very
interesting
data
for
us
and
it's
a
different
way
for
us
to
think
about
how
we
drive
the
product
and
how
we
drive
the
community
for
you
all,
because,
like
you're
using
our
api
more
than
using
our
website,
we
care
deeply
about
the
website.
But
we
should
also
care
deeply
about
the
api
and
really
look
at
how
you're
using
it.
A
What
are
you
not
getting
today,
and
what
can
we
add
so
the
other
side
of
this
is
over
five
million
people
on
github
are
using
integration,
and
so
integration
is
our
word
for
anything
that
plugs
into
github
like
a
travis
or
a
slack.
It
has
some
sort
of
official
or
unofficial
way
of
interacting
with
the
api
or
driving
github.com.
So
over
five
million
people
are
involved
in
a
team
or
something
that
uses
an
integration
today,
which
is
just
a
massive
number
and
oauth
usage
on
github
itself.
It's
doubling
every
year.
A
A
A
But
it's
there's
a
lot
of
metal
work
around.
Getting
these
things
up
and
running
that
we
just
see
is
totally
unnecessary.
So
even
despite
all
this
growth
and
the
api
being
the
main
way,
people
interact
with
the
site,
it's
still
not
a
great
experience,
so
we're
seeing
this
this
cert,
this
surge
of
traffic,
but
like
kind
of
in
spite
of
it,
we're
not
doing
anything
to
help
make
that
easy.
So
it's
hard
to
find
these
tools.
A
A
I
don't
know
that
crappy
python
script,
that
you
read
that
you
wrote
that
you
wanted
to
see
like
very
private,
very
personal,
stuff
right
and
so
oauth
really
needs.
We
need
more
of
it
and
we
need
to
ask
more
of
it
and
give
back
more
to
it.
But
we
need
something
that
can
think
about
the
problems
of
today
and
not
the
problems
that,
let's
say
a
social
network
had
10
years
ago
and
the
other
side
of
it
are.
Does
anyone
remember
any
of
these
technologies?
Anyone
used
soap.
I'm
sorry!
A
I
luckily
avoided
xml
rpc,
I'm
sorry
to
anyone
that
didn't
and
then
I
loved
rest.
I
grew
up
as
a
ruby
on
rails
developer.
I
started
using
rails
right
when
it
came
out
and
rails
really
promoted.
Rest
apis
in
this
way
of
thinking
about
the
web,
and
I
was
super
into
that
especially
coming
from
soap.
Rest
was
very
clear.
It
was
very
appealing
to
me
and
even
though
I
got
introduced
to
it
through
rails
and
the
rails
community,
it
seemed
like
a
web
technology.
A
I
didn't
feel
like
it
was
a
ruby
technology,
although
now
maybe
I
feel
differently,
but
at
the
time
it
really
seemed
like
this
was
a
web
technology
that
ruby
was
embracing,
and
so
I
knew
that
my
my
colleagues
and
my
peers,
using
python
or
perl
or
anything
I
was
hoping
that
they
would
also
be
using
rest
in
a
similar
way
and
it
would
sort
of
not
matter
anymore
what
technologies
and
libraries
we
use.
That
would
fade
into
the
background,
so
I
was
a
huge
fan
of
rest,
but
that
was
12
years
ago.
A
Right
rest
has
been
here
for
a
while,
and
it's
gotten
us
very
far,
but
I
think
similar
to
oauth.
There
are
a
lot
of
things
that
are
different
about
the
world
and
a
lot
of
the
context
that
rest
was
created
in
and
imagine
in
it's
changed
it's
different.
Now
the
world
is
different.
I
don't
think
that
when
rest
was
created
there
were
major
websites
that
were
mostly
hit
through
their
api.
Like
this
was
not
the
world.
We
were
envisioning
when
we
created
rest.
A
What
we
were
thinking
about,
I'm
saying
we
had
no
part
in
it,
but
when
we
were
creating
rest,
what
we
were
thinking
about
was
access
to
your
data,
actually
taking
the
http
protocol
seriously
stateless
communication:
these
were
the
things
not
a
website
like
github,
that's
handling,
major
data
that
has
a
huge
development
team.
That's
building
software
that
you're
also
building
software
against
that's
changing
all
the
time.
This
is
just
not
the
concerns
that
rest
had
so
we're
thinking
about
all
these
things
sort
of
coming
together.
You
know
our
api
is
soaring
in
usage.
A
We're
seeing
companies
like
travis
but
tons
more
build
their
own
businesses
on
top
of
github,
our
own
frustrations.
Frankly,
in
trying
to
juggle
between
all
these
different
applications
that
plug
into
github
and
then
at
the
end
of
the
day.
Rest
is
it's:
it's
dead
technology
it's
not
over,
but
it's
dated.
I
think
the
cycle
is
ending
and
we're
ready
for
something
new.
The
world
is
ready
for
a
new
way
to
talk
about
apis,
a
new
way
to
interchange,
data
and
something
that
needs
to
be
focused
on
developers,
and
this
is
really
the
idea
behind.
A
Github
is
github
was
created
for
developers,
it
was
created
by
developers.
I'm
sure
you've
heard
that
before
I've
said
it
already
today,
but
ultimately,
a
lot
of
what
we
wanted
to
do
with
github
was
build,
something
that
you
wanted
to
use,
and
so,
when
we
think
about
the
future
of
our
api,
that's
exactly
how
we're
thinking
of
it.
A
Soap
and
xml,
rpc
and
rest
were
really
powerful
for
moving
our
mindset
and
a
lot
of
our
boss's
mindset
to
allow
us
to
make
this
data
open
to
allow
us
to
spend
time
building
an
api
to
allow
us
to
share
the
stuff
with
the
world,
and
that
was
a
hurdle
because
we
wanted
to
do
it.
A
lot
of
us
developers
wanted
to
do
it,
but
we
had
to
convince
the
manager.
It
was
a
good
idea.
A
Soap
really
helped
with
that
and
rest
really
helped
with
that
and
the
prevalence
of
apis
and
a
lot
of
this
open
data
economy.
These
memes
these
ideas,
these
buzzwords.
They
got
people
thinking
in
this
direction
and
that's
over
now.
I
think
the
apis
have
won.
There's
it's
not
controversial
anymore,
and
so
now
we're
in
a
world
where
it's
that
by
default,
we
want
to
start
developing
with
open
apis
and
sharing
this
data.
But,
like
is
this
the
best
tool?
A
Are
these
api
development
tools
now
built
to
buy
developers
for
developers,
we've
convinced
your
boss
and
my
boss
and
me
that
we
should
be
sharing
data,
but
like
are
you
doing
it
in
the
best
way
possible?
Are
the
tools
built
for
you?
Are
the
tools
built
by
you,
and
the
answer
is
no.
Rest
is
not
that
rest
is
trying
to
salvage
the
http
protocol,
which
is
ancient
and
turn
it
into
something
that
we
can
really
use.
Well,
it's
not
rethought
with
the
context
of
today
with
the
problems
that
we
have
today.
A
So
what
we're
going
to
talk
about
today
are
our
ideas
about
the
future
of
apis,
the
future
of
rest,
the
future
of
working
together,
and
so
I'd
like
to
bring
to
the
stage
mr
kyle
daigle
at
github
who's
going
to
talk
a
little
bit
about
some
of
the
new
things
we're
doing
and
some
of
our
opinions
on
the
future
of
apis,
a
lot
of
which
I
think
you'd
be
really
interested
to
hear
about.
So
please
join
me
in
welcoming
kyle
to
the
stage.
C
Hey
everybody-
I
am
super
excited
to
be
here:
github's
the
best
platform
to
collaborate
on
software,
build
tools,
find
the
best
tools
for
your
workflow,
and
I
really
think
what
we're
up
to
and
what
we're
gonna
talk
about
today
is
going
to
be
what
you
all
have
done.
You
all
built
tools,
you've
built,
integrations,
you've
extended
our
platform
like
chris,
said
the
api
that
we
have
right
now
is
nine
years
old.
You've
all
worked
with
it.
You
felt
the
joys
of
using
it.
You
felt
the
pains
of
using
it.
C
You've
been
limited,
sometimes
in
what
you
can
do.
We
think
an
open
ecosystem
is
the
best
way
to
move
forward.
Lets
you
build
your
best.
Workflow
find
your
best
workflow
using
an
extremely
powerful
platform,
and
so
I'm
going
to
talk
about
three
things
today
that
we're
releasing
they're
going
to
help
you
do
that.
The
first
one
is
graphql.
C
We've
released
an
early
access
for
graphql
at
github
universe
last
year,
and
we
gave
the
community
a
new
way
to
get
at
data.
It's
a
technology
that
facebook
created
in
open
source
and
it
allows
you
to
build
a
query,
get
exactly
the
data
that
you
need
and
get
a
response
in
the
same
exact
shape
of
that
of
that
data.
C
The
important
thing
is
that
github
has
changed.
How
we
build
features
to
make
this
possible
now
at
github,
when
we
build
a
new
feature
for
github.com
or
github
enterprise,
we
first
build
a
graphql
api
and
then
we
consume
that
ourselves.
It's
a
big
change
to
the
way
we
used
to
work
like
chris
mentioned,
where,
if
anyone
has
built
a
rest
api
before
you
build
a
feature,
usually,
then
you
go.
Oh,
I
need
to
build
an
api
for
this.
You
build
an
api,
and
inevitably
they
get
out
of
sync.
Graphql
helps
us
fix
that.
C
So
just
a
quick
example
on
the
left,
you'll
see
a
simple
graphql
query
saying
I
want
to
know
who
I
am.
I
want
the
login
and
the
bio
and
on
the
right,
you
get
back
structured
data.
That
looks
basically
the
same,
and
this
is
powering
all
of
our
new
features
at
github
and
externally,
as
well
as
our
integrators
are
starting
to
adopt
this
during
the
early
access
I'd
like
to
walk
you
through
a
couple
of
features
that
are
powered
in
part
by
graphql
on
github.
C
Some
of
you
might
have
seen
the
new
code
review
features,
including
suggested
reviewers,
allows
you
to
choose
someone
that
you
think
you'd
like
them
to
review
your
code.
This
is
backed
by
graphql
projects,
our
new
project
board
that
launched
at
github
universe
last
year.
This
is
also
backed
by
graphql
a
little
bit
of
a
meta
fact.
The
rest
api
is
actually
backed
by
graphql
itself
for
the
projects
api.
C
And
finally,
we
have
adam
excuse
me
topics
and
with
topics.
We
allow
you
to
choose
different
keywords
that
allow
you
to
say
what
this
repository
is
about
is
about
and
let
you
find
different
repositories
within
your
organization
or
across
all
of
github
that
have
those
topics
and
with
that
now
topics
is
100
built
from
scratch
from
graphql,
and
so
we
are
committing
to
changing
the
way
we're
building
github
to
allow
you
to
have
the
same
exact
power
as
our
own
internal
engineers.
C
Right
now,
since
we
release
the
early
access,
we're
doing,
125
million
graphql
queries
per
day.
A
lot
of
that
is
internally.
So
when
we're
using
graphql,
that's
a
lot
of
these
queries,
but
it's
also
through
our
early
access.
We've
seen
integrators,
join
us
and
build
new
features,
but,
like
chris
said,
part
of
the
ecosystem
is
on
desktop,
and
last
week
we
released
the
atom
package
that
had
git
and
github
integration.
C
These
features
in
tools
are
all
powered
by
graphql
and
the
package
is
open
source.
So
if
you'd
like
to
go
and
change
the
way
that
we
show
the
pull
requests
now
in
this
package,
it's
using
open,
graphql
apis
that
you
can
use,
there's
no
secret
sauce,
there's
nothing
that
we're
keeping
from
you
in
order
to
build
the
best
integration
during
early
access,
we've
been
working
with
a
variety
of
integrators,
but
one
of
those
has
been
heroku
on
the
dashboard
page.
C
Now,
when
you
look
at
your
heroku
pipeline,
you
can
see
the
statuses
of
all
your
builds
and
they've
reached
out
because
they
said
we
couldn't
give
this
feature
to
our
users
and
we
wanted
to
because
the
rest
api
made.
So
many
calls
necessary
to
get
at
this
data
with
graphql.
We
can
make
one
call
and
ship
a
feature
to
production,
and
so
this
is
live
now
powered
by
our
graphql
api.
C
So
the
exciting
news
today
is
now
graphql.
Is
production
ready?
So
if
you've
been
waiting
to
join
the
bandwagon
from
the
early
access,
you
can
join
in
and
know
that
we're
committed
to
a
platform
that
we're
going
to
work
with
you
we're
going
to
code
with
you
we're
going
to
build
alongside
each
other.
As
we
use
this
new
api.
C
C
If
you're
someone
using
our
new
business
plan
or
if
you're,
an
organization
that
wants
to
protect
some
of
your
data,
it's
an
all
or
nothing.
You
can't
use
oauth
most
of
the
time,
because
you
don't
want
to
give
the
keys
to
the
kingdom
to
everyone
github
ourselves.
We
can't
use
our
integrators.
We
can't
use
the
tools
they
build.
We
love
them,
but
we
can't
use
them.
In
a
few
cases,
we
have
to
write
custom
code
because
we're
uncomfortable
granting
oauth.
So
we
know
we
needed
to
fix
this
with
github
apps.
C
We
allow
you
to
choose
just
the
repositories
that
you
want
and
then
much
more
fine-grained
permissions
than
we
ever
offered
you
before,
and
so
we
enable
options
like.
I
would
just
like
you
to
read
this
code,
or
I
would
just
like
you
to
have
read
access
to
issues
or
down
to
a
single
file.
So
for
integrators
that
have
a
metadata
file
and
you
just
want
to
get
to
the
heroku.yaml
file,
you
can
ask
for
permission
just
for
that.
C
One
file
we're
letting
the
customers
choose
how
they
want
to
give
access
and
making
it
more
likely
for
integrators
to
have
success
reaching
those
customers
when
you
install
no
longer
does
your
entire
organization
have
to
get
that
super
scary
screen
that
says
this
integration
would
like
to
access
everything
that
you
have
underneath
it
and
people
don't
normally
click
that
with
github
apps.
Once
you
install
it
it's
installed
once
and
everyone
can
use
it
with
a
simple
screen
that
basically
says
your
organization
has
allowed
this
go
ahead
and
use
it.
C
If
you've
used
oauth
and
you've
used
an
integration
a
lot
of
times,
the
integration
will
completely
act
as
some
random
employee
in
your
organization.
That's
usually
the
person
that
installed
the
integration,
and
so
with
this
we're
going
to
allow
the
by
itself
to
take
actions.
It
can
make
comments.
It
can
change
and
create
issues
it
can
do
whatever
it
needs
to.
In
order
to
be
clear
that
this
is
an
integration
that
you're
using,
but
also
allow
you
to
act
on
your
own
behalf.
C
Thank
you,
since
we
put
this
into
early
access,
we've
noticed
a
huge
uptick
in
the
number
of
people
that
are
actually
using
integrations
because
it's
so
much
easier
to
install
and
you
feel
a
lot
safer
and
so
you'll
see
we
have
over
100
000
users
using
this
and
some
very
large
organizations
across
the
5000
organizations
that
have
joined
during
the
early
access
into
the
in
the
period
that
we
very
clearly
said.
Please
don't
use
this
in
production.
The
demand
was
so
high
that
they
used
it
anyway.
It's
been
very
successful.
C
One
of
our
integration
partners.
Waffle
is
very
excited
about
this
one
of
the
things
that
inevitably
comes
up,
especially
in
project
management.
Apps,
where
you
have
both
developers,
project
managers,
designers,
lots
of
people
collaborating
how
it'll
be
much
easier
for
them
in
order
to
get
everyone
working
in
one
place
using
their
project
management
tool.
C
C
C
It
allows
you
to
find
the
tools
that
will
fit
your
workflow
best
and
very
easily
find
a
plan
that
works
for
you,
click
it
and
buy
it
using
your
github
account.
Have
it
set
up
in
minutes
so
no
longer
do
you
have
to
go
and
find
the
right
tools
or
make
sure
that
you
know
the
right
tools
or
go
on
a
bunch
of
news
sites
to
find
out?
What's
the
cool
new
thing
you
don't
have
to
go,
find
someone
in
your
organization
that
has
the
credit
card
that
you
can
use.
C
C
We
offer
a
variety
of
plans
that
the
integrators
choose
and
set
up
by
themselves,
and
so
I
think
that
we
need
the
bootstrap
plan,
and
so
I
can
choose
that
and
then
very
quickly
have
all
those
features
in
a
simple
purchase
flow.
If
I'm
an
organizational
admin,
I
can
buy
it
and
have
it
set
up
very
quickly
for
our
launch.
We
have
four
categories
in
the
monitoring
category:
we're
talking
about
monitoring
code
changes.
C
We
want
to
measure
performance,
track
errors
and
sometimes
analyze
your
application.
This
is
one
of
the
more
popular
areas
in
which
we
think
people
need
this
sort
of
tool,
so
we
have
sentry
blackfire
and
rollbar
in
project
management.
It's
all
about
automating
code
review.
Excuse
me
in
code
quality,
it's
all
about
automating
code
review,
testing,
the
style
quality,
the
security
with
that
we
have
code,
cov,
codec
and
codebeat
and
in
project
management.
C
If
you
don't
want
to
use
our
projects
tool,
if
you
don't
want
to
use
issues,
you
can
find
the
tool
that
works
best
for
you,
including
zenhub,
waffle,
code
tree
and
zub,
and
then
finally,
continuous
integration
run
your
tests
easily
and
quickly.
You
can
get
it
set
up
by
purchasing
travis,
circleci,
appvayer
or
percy,
which
is
a
very
cool,
visual
testing
and
review
tool.
So,
if
you're
a
designer,
I
definitely
you
should
check
that
tool
out.
C
And
if
you
are
an
integrator
or
if
you
hear
about
what
we're
offering
today
with
our
platform
and
you
think,
now's
the
time
to
join
in
you
can
join
our
marketplace,
you
can
come
in.
You
can
get
your
app
listed
in
the
one
of
the
most
vibrant
ecosystems
that
are
out
there
to
our
21
million
developers.
C
The
apple
of
seamless
integration
will
handle
getting
you
the
audience
that
you
need
to
make
sure
you
can
find
the
customers
that
are
right,
for
you
make
it
easy
to
click,
buy
and
install,
and
then
you
can
find
out
how
to
focus
just
on
the
thing
that
makes
you
unique
and
not
have
to
focus
on
all
the
other
parts
of
building
a
business
around
your
integration.
You
can
find
more
details
about
this
at
github.com
marketplace
and
you
can
apply
today.
C
With
graphql
github
apps
and
marketplace,
we've
created
the
most
powerful
platform,
yet
whether
you're
using
our
graphql
api,
which
allows
you
to
make
one
call
to
get
all
the
data
that
you
need,
whether
you're
installing
a
new
integration
using
github
apps,
which
lets
you
just
install
where
you
want
it
with
just
the
permissions
that
you
need
or
finding
and
buying
the
ideal.
Continuous
integration
workflow
in
our
marketplace.
B
B
When
developers
want
to
find
the
best
tool
for
the
job
or
the
tool
that
takes
them
to
the
next
step,
they've
always
come
to
the
same
place.
Introducing
github
marketplace
get
the
tools
you
need
to
do
your
best
work
with
the
largest
community
of
developers
on
earth.
It
isn't
really
a
new
idea.
It's
just
a
really
good
idea,
find
out
more
at
github.com
marketplace.
A
Hello
again
cool,
so
I
just
want
to
say
thank
you
again
to
the
teams
for
everything
they
launched
today.
I
hope
you're
excited
about
it.
Please
check
out
graphql
the
marketplace:
github
apps,
you
know
I've
told
the
story
a
million
times,
so
I'm
not
going
to
bore
you,
but
we
didn't
start
github
as
a
company.
We
started
github
as
a
side
project
because
we
were
doing
other
companies,
but
it
was
really
just
for
ourselves.
It
was
a
product.
A
It
was
a
piece
of
software
that
we
wanted
to
use
to
collaborate
on
git
and
when
we
saw
how
it
affected
people,
when
we
saw
how
obsessed
we
were
with
it,
and
we
saw
what
people
wanted
to
do
with
it.
That's
when
we
decided
this
could
be
a
real
thing.
This
could
be
a
real
company
and
we've
got
to
figure
out
some
way
to
make
money,
but
like
this
could
be
something
interesting
and
that's
where
the
company
started.
Github
now
is
nine
years
old,
we're
going
on
to
be
a
decade
we're
growing.
A
We
have
a
lot
more
people.
We
have
a
lot
more
interest,
we're
all
over
the
world,
but
that
sort
of
sentiment
that
idea
of
we're
building
things
for
the
community,
with
the
community
for
developers
by
developers
that's
becoming
stronger
than
ever
for
us
and
as
we
become
a
big
company,
we're
not
losing
sight
of
that.
We're
actually
betting.
A
Everything
on
that,
so
the
future
of
github
and
what
we're
launching
today
and
what
this
represents
is
about
a
future
that
we're
building
together,
like
we're
excited
about
the
marketplace,
because
we're
excited
about
what
you're
going
to
build
inside
of
it
and
what
we're
going
to
put
inside
of
it
too.
We're
excited
about
the
future
of
github,
because
we're
excited
to
see
what
you're
going
to
build
and
what
you're
going
to
do,
and
the
only
reason
we're
here
today.
A
The
only
reason
I'm
on
stage
the
only
reason
to
get
up
satellite
is
possible
is
because
of
you
it's
because
of
what
you've
built,
what
you've
put
on
github,
what
you've
shared
with
the
world,
how
your
company's
built
software
github
is
in
itself
a
pretty
cool
thing,
but
ultimately
the
github
community,
the
software
development
community.
That's
the
real
rise,
that's
the
real
amazing
thing:
that's
what
these
numbers
represent.
So
we're
not
just
taking
advantage
of
this
and
sort
of
saying
we
know
best
and
we're
just
going
to
run
with
it.
A
We're
saying:
let's
talk,
let's
do
this
together!
We
want
to
build
software
with
you,
we're
using
the
same
apis
that
we're
building
internally
we're
making
them
available
to
you
the
same
way
we're
building
projects
and
features
internally,
we're
making
them
available
to
you
we're
here
we
want
to
talk.
We've
got
the
community
staff,
we've
got
developers,
we've
got
sales
people,
we
want
to
build
github
with
all
of
you,
and
this
is
not
just
something
that
we're
doing,
because
we
feel
like
we
need
to
give
back,
because
we
do
feel
like
that.
A
This
is
what
we
think
is
the
future
of
software
development.
We
believe
in
an
open
ecosystem.
We
believe
in
a
diverse
and
inclusive
ecosystem,
and
we
think
the
future
is
a
lot
of
smart
people
working
together,
not
against
each
other,
not
to
reinvent
the
wheel,
but
to
solve
real
problems
and
just
forget
about
all
the
crap
that
gets
in
your
way.
So,
thank
you
again
for
coming
to
satellite.
Thank
you
for
everyone
who's.
Putting
on
this
event.
I
hope
you'll
help
us.
A
I
hope
you'll
be
there
with
us,
but
I
mean
you
already
are
you're
here
you're
sitting
here,
you've
put
software
on
github.
You've
contributed,
we've
worked
together.
We
believe
that
this
is
the
future
and
these
numbers.
These
are
just
proof
points,
and
so
we're
really
excited
to
see
what
people
build
on
marketplace.
So
people
build
with
graphql,
but
we're
not
worried.
A
We
know
it's
going
to
be
amazing,
because
we've
done
nothing
but
be
amazed
so
far
over
the
past
10
years
by
what
all
you
have
done,
so
we
want
to
figure
out
what
you're
going
to
do
next,
we're
going
to
figure
out
how
we
can
make
it
possible.
So
thank
you
again
to
everyone.
Please
check
out
the
marketplace
check
out
graphql.