►
Description
Presented by Thomas Aiden Curran, Co-Founder and Co-CTO, Ory sh
About GitHub Satellite 2019
A community connected by code
Explore our interconnected community—and how collaboration turns ideas into innovations.
Join us in November at San Francisco's Palace of Fine Arts for GitHub Universe - https://githubuniverse.com/
A
A
Please
take
a
look
at
it.
It's
the
topics
are
very
much
in
a
security
realm,
open
authentication,
open,
ID,
connect,
ap
security
and,
of
course
we
love
your
support.
What
I
want
to
talk
about
today
is
actually
how
you
build
inside
your
enterprise
or
inside
your
company,
a
community
of
developers
that
work
on
github
and
collaborate
on
github,
more
or
less
like
an
open
source
project
would
work.
A
So
I
have
have
done
some
different
projects
in
the
past
and
had
different
roles
and
larger
companies
and
I'm
going
to
use
that
experience
to
draw
on
and
as
I
go
through
the
next
10
slides
and
help.
You
understand
some
of
the
opportunities
you
have
to
use
github
in
your
company
and
not
only
the
tools
and
technologies,
but
also
some
of
the
methodologies
so
for
the
managers
out
there
I
mean
one
thing:
that's
often
asked
besides
the
price
of
any
new
software
platform
infrastructure.
A
Is
you
know,
why
do
you
need
this,
and
most
companies
today
are
using
some
kind
of
source
code
control,
some
kind
of
configuration
management,
some
kind
of
deployment
pipeline?
All
these
things
are
absolutely
typical.
So
the
question
of
why
github
is
a
very
valid
question
and
I
met
a
post.
Last
year
we
had
a
similar
talk
at
cbut
I'm,
very
happy
by
the
way
that
I
was
one
of
the
last
speakers
in
the
last
seebut
ever
so
that
was
good.
A
One
of
the
things
github
does
besides
solve
all
these
software
issues.
Is
it
lets
you
find
things
in
your
company,
and
you
know
this
is
not
a
very
funny
problem.
Most
organizations
especially
you
know
they
have
email
systems,
they
have
databases
etc,
but
for
source
code
is
extremely
difficult
to
find
and
maintain
across
an
organization
a
lot
of
the
intellectual
property
and
just
any
property
that
software
developers
have
done
combined
with
the
fact
that
most
companies
today
don't
do
that
themselves.
A
I
mean
they
do
a
lot
of
stuff
outsource
and
so
bringing
that
into
the
company
and
being
able
to
have
one
very
easy
thing
being
able
to
search
across
the
different
products
and
projects
and
source
code
in
order
to
understand
risks,
security
issues,
opportunities
to
reuse
software,
etc.
These
things
are
very
important.
Another
thing
that
you
obviously
need
and
don't
often
have,
especially
if
you're
in
a
managerial
role,
is
insight
into
who
does
what
in
the
company.
Now
again,
this
is
no
joke,
I
mean
if
you're
managing
a
thousand
or
2,000
or
more
developers.
A
To
some
extent,
speed
is
very
important,
but
also
the
ability
to
be
resilient
and
change
things
and
move
fast
is
is
a
goal
for
many
operations
that
are
software
companies
and,
of
course,
many
companies,
banks,
insurance,
production
of
cars,
etc.
These
companies
in
the
past
have
not
moved
that
fast.
Some
of
the
reasons
are
their
customers.
A
So
the
first
thing
I
would
say,
insight
and
learning
from
open
source
is.
How
do
you
build
software
products?
Now
again,
many
organizations
are
structured
around
business
lines,
different
sort
of
IT
conventions.
You
have
a
database
Department,
you
have
a
security
department,
you
might
have
QA,
which
is
separate
from
those
as
well,
and
one
of
the
things
and
the
learnings
I
think
we
can
draw
on
from
the
last
30
years
of
open
source
is
that
that
doesn't
really
work?
You
need
an
integrated
product
team
with
the
skill
sets
that
are
that
are
sufficient.
A
A
What's
the
right
word
sort
of
different
skill
sets
put
into
one
organization
so
that
the
team
can
operate,
and
again
this
is
not
just
about
technology.
This
is
more
about.
How
do
you
organize
your
teams
to
your
org?
How
do
you
organize
your
developers
to
take
advantage
of
the
technology
platform
that
github
brings
to
bear
now?
You
might
have
seen
it
today
this
morning,
etc.
A
lot
of
the
even
the
new
things
that
github
is
doing
is
really
focused
on
bringing
the
power
to
these
teams
and
operational
capabilities
that
they
have
to
deliver
software.
A
Why
is
this
important
again
today
we
have
a
lot
of
new
technologies
that
affect
the
way
you
build
and
deliver
software.
Just
give
you
an
example:
docker
might
be
a
good
one
or
cloud
might
be
another
one
and
having
people
that
you
know
like
to
go
home
and
look
at
these
things
and
do
things
when
they
come
back
to
the
office.
Why
not
organize
them
into
community
support
those
communities,
give
them
some
cookies
or
some
coffee
and
a
place
to
do
stuff?
A
It's
not
that
hard,
but
I
think
the
main
thing
is
that,
especially
on
github
and
especially
the
way
you
can
build
communities
using
give
up
these
practice,
communities
helped
really
drive
a
lot
of
the
new
inventions
and
the
way
you
experiment
with
deployment
systems.
So
they
look
into
that
next
thing.
It
was
again
observation.
A
Let's
face
it,
a
lot
of
so-called
IT
organizations
or
big
enterprise
production
departments
are
really
managing
projects.
Oftentimes.
You
find
that
people
are
not
that
familiar
due
to
other
job
responsibilities
with
the
software
stack
that
developers
are
using
github
gives
you
a
very
unique
way
of
being
able
to
interact
with
with
the
technologies
with
the
software.
You
can
set
things
up.
It
can
be
highly
automated
we'll
get
into
that.
A
But
the
good
news
is
Hubb
is
a
platform
that
also
makes
learning-by-doing
a
very
easy
task
to
get
into,
especially
for
people
that
are
not
day-to-day
involved
in
in
a
project.
An
open-source
has
really
made
itself
evolved,
almost
like
an
animal
evolved
to
be.
You
know.
If
you
want
people
to
do
stuff
for
your
project,
it
has
to
be
easy
to
get
into
you
have
to,
for
instance,
in
Ori.
We
have
a
five
minute
demo
and
we
really
time
it
so
you
can
go
there.
You
can
look
at
everything.
A
A
You
can
collect
over
time
because
one
you
help
teams
by
getting
that
information
to
github
gives
you
a
lot
of
things
that
you
would
not
otherwise
have
as
an
actor
in
any
kind
of
organization.
So
one
of
the
nice
things
about
github
repositories.
As
an
example
is
you
can
see
the
build
health
of
any
repository,
you
can
also
collect
that
data
and
make
that
publishable
to
other
people
that
might
be
involved
in
the
process.
A
A
Now,
when,
when
companies
deploy
github
in
the
beginning,
it's
very
seldom
again,
as
I
mentioned,
you
know
you're,
not
starting
from
scratch.
You
have
subversion,
you
have
bitbucket,
you
might
have
PVCs
some
type
of
clearcase,
some
type
of
environment
that
you
would
have
been
using
prior
to
deploying
github
and
all
of
those
environments
also
come
with
their
own
sort
of
data
set
and
the
way
they
manage
configuration
so
creating
something.
A
That's
consolidated
and
github
will
take
a
little
bit
of
time
and
energy,
and
let
me
just
explain
some
of
the
things
that
I've
seen
companies
do.
One
thing
that
again
when
you're
deploying
new
platforms,
you
have
often
the
opportunity
also
to
insert
new
processes
and
new
ways
of
working
github
as
an
example
keeps
the
whole
idea
of
working
in
parallel.
That's
manifested
in
github
is
designed
to
let
teams
work
very
fast,
but
also
keep
sort
of
in
sync,
with
branches
etc.
A
So
pull
requests
become
a
very
new
and
important
dynamic
for
companies
and
especially
teams
in
order
to
augment
their
day-to-day
work
without
getting
left
behind.
So
how
do
was
it?
You
know
before
github
it
was
you
checked
out
some
code.
You
did
some
stuff.
You
were
a
little
bit
nervous,
it
didn't
build,
so
you
didn't
really
want
to
check
it
back
in.
So
you
went
for
a
week
or
maybe
more
of
basically
frozen
code
in
a
repository
and
github
and,
of
course,
for
Linux
was
really
disastrous.
A
So
that's
why
I
get
became
a
tool
that
lets
you
a
lot
of
people
work
in
parallel
ways
without
needing
to
create
what
we
would
call
long
pull
requests
long
transactions,
so
instead
one
of
the,
for
instance,
data
points
you
might
want
to
look
at
is
the
velocity
of
pull
requests
across
all
repositories.
This
gives
you
also
a
sense
of
other
things
that
you
might
want
to
look
at
and
try
to
help
teams
with.
As
an
example,
you
find
people
that
move
from
subversion
to
github
in
companies.
A
They
really
learned
how
to
build
mono
repositories,
so
you
can
consolidate
all
of
that
code
base
into
one
place
and
then
basically
data
fie
that
whole
repository
and
give
the
entire
flavor
of.
What's
going
on
to
people
that
are
potentially
affected,
they
could
be
s
Ari's,
they
could
be
DevOps,
they
could
be
just
programmers
or
managers
etc,
but
you
want
to
be
able
to
give
the
entire
dynamic
of
a
repository
and
an
infrastructure
to
everyone
affected
by
it,
and
so
github
has
the
get-up,
Enterprise
or
github.
A
The
product
gives
you
some
opportunities
to
collect
and
analyze
data
around
now
now.
The
other
good
thing
about
the
github
system
is
that
there
are
many
other,
obviously
open
source
products,
but
even
any
products
that
are
hooked
in
to
github
and
give
you
additional
give
you
additional
information
and
data
about
what's
going
on
in
the
product
development.
So
as
an
example,
if
you're
using
coveralls
for
Co
coverage
or
if
you're,
using
Cypress
for
integrated
testing,
you
have
quite
a
lot
of
data
points
that
you
can
then
bring
back
into
some
system.
A
A
That's
really
what
you
need
to
do
in
order
to
start
automating
things.
So
automation,
of
course,
depends
on
data.
If
you
want
to
you
know,
a
lot
of
companies
today
have
elaborate
gardener
group
based
reports
on
RP,
a
robotic
process,
automation
and
all
this
stuff.
They
want
to
do,
and
you
look
at
it
and
today
I
mean
again
going
into
some
companies.
A
It
just
seems
like
well
isn't
that
what
you're
doing
isn't
that
software
development
I
mean
you're
taking
this
process,
you
put
some
stuff
into
Excel,
you
fill
out
some
forms,
you
put
it
on
a
website
and
then
you
check
it
and
see
if
everything's,
okay
and
you
need
a
scripting
tool
to
do
that.
Well,
the
problem
is
again
but
automating
processes
when
they
get
disjunct
from
what
else
is
going
on
in
the
business
it
becomes
by
itself
a
future
time
bomb,
because
that
becomes
something
that's
hard
to
maintain,
etc.
A
So
one
thing
about
automating
processes
and
one
things
important
about
getting
github
into
your
enterprise-
is
that
you
have
to
go
all-in
and
believe
me
I'm,
very
radical
about
that.
Everything
goes
in
github
or
else
you
don't
do
it.
The
reason
for
that
is,
then
you
have
visibility
again,
search
talent,
etc,
but
you
can
also
augment
the
data
with
new
processes,
new
scripts
and
look
at
all
the
stuff.
That's
coming
out,
console
terraform
all
of
the
deployment
technologies.
Imagine
now
applying
them
in
your
company
and
being
able
to
automate
many
things
that
people
do
compliance.
A
There
are
people
in
the
financial
industry
in
banking,
insurance,
food
production,
etc.
You
know,
step
by
step
by
step
by
step.
They
have
to
check
things,
and
it's
not
just
see
to
your
pants,
that's
good.
We
all
benefit
from
that,
but
you
need
an
infrastructure
that
helps
you
implement
that
compliance
over
time
and
github
can
also
do
that.
Why
why
it
github
creates
audit
trails,
github
lets
you
go
back
and
forth
almost
in
along
a
timeline.
Github
produces
a
interface
to
testing
tools.
Github
also
produces
the
interface
to
Jenkins
or
circle
CI
or
Travis.
A
Having
all
of
those
things
integrated
gives
you
a
much
better
data
set
about
compliance,
and
you
would
get
by
asking
you
know
two
guys
in
the
compliance
department
to
take
a
look
at
this
repository.
So
believe
me,
automation
of
compliance
is
a
very
big
opportunity
that
companies
have
today
when
they
deploy
github
Enterprise
and
by
the
way,
we're
not
talking
in
this
slide
about
deployment.
A
But
you
want
to
basically
automate
almost
everything
possible
and
think
about
open
source
projects
yeah,
you
know
in
order
to
really
get
people
excited
about
any
open
source
product,
they
need
to
be
able
to
see
at
work
that
it
needs
to
be
really.
The
automation
needs
to
be
in
place
in
order
for
the
audience
to
have
immediate
feedback
about
their
contributions
and
I.
Think
companies
more
and
more
are
coming
to
that
point,
where
even
developers
and
and
other
parties
again
integrated
teams,
product
teams.
A
You
know
people
for
marketing
also
want
to
see
stuff,
work
and
I
think
that's
important
for
integrating
and
working
with
the
github
enterprise
infrastructure,
but
also
just
getting
the
community
of
people
that
you
need
involved
in
more
and
more
products.
A
lot
of
companies
talked
about
this
today.
You
know
they
want
to
interface
with
customers.
They
want
to
understand
customers
they,
but
really
isn't
that
part
of
a
bigger
issue
which
is
they
don't
really
understand
the
products
they
produce
and
they
can't
because
they
don't
have
the
visibility
they
don't
have
the
contact.
A
They
don't
know
where
to
go
to
ask
people
even
a
website
a
lot
of
times
today,
even
in
even
in
modern
companies.
It's
very
seldom
that
you
can
just
call
up.
Someone
say:
how
does
this
work
I'm
on
a
chat
system?
I
have
a
call
from
a
customer
so
bringing
the
community
aspect
of
github
again
I,
don't
know:
I
saw
36
million
today,
if
that's
right
or
wrong.
Let's
say
it
is
right,
so
lots
of
people
are
in
a
community
across
the
globe
that
are
working
on
one
infrastructure.
A
Think
of
getting
everyone
in
your
development
in
github
on
an
enterprise.
So,
first
of
all
this
sounds
strange,
but
it's
not
strange.
If
you're
in
a
company
you
know
you
can
communicate
with
someone
that
you
didn't
know
that
works
in
another
department.
You
don't
need
to
send
an
email
to
his
boss
and
ask
him
if
it's
ok,
to
talk
to
him.
You
can
do
everything
in
one
github,
community
and
I.
Think
that's
super
important.
A
The
other
thing
is
again
when
you're
automating
and
when
you're
using
DevOps
many
tools,
you
have
the
whole
repository
build
up
and
tool
integration
that
you
can
do
in
one
place,
which
makes
it
much
easier
for
companies
to
see
what
they're
doing
across
the
board.
But
it
also
makes
it
easier
for
maintainer
''s
inside
your
company
to
get
the
automation
effects
that
they
would
otherwise
be
expected
to
have
from
implementing
a
system
like
github
Enterprise,
again,
toolchain,
look
we're
in
a
probably
I
guess,
one
of
the
best
errors.
I
can
imagine
in
software.
A
A
A
So
having
this
capability
to
get
new
things
in
new
inventions,
be
able
to
try
them
put
them
in
a
github
tool,
train
or
in
a
DevOps
tool
chain
and
having
that
capability
to
interact
with
the
system
gives
you
a
whole
new
way
of
working
and
I.
Think
we'll
see
in
this
era
of
software
that
that's
really
a
good
thing
for
business
and
by
the
way
you
have
a
proving
ground
of
now
36
million
people
that
have
tested
this
and
see
that
it's
actually
ok
to
get
the
big
benefits,
though
it
a
big
bang.
A
Out
of
a
lot
of
these
things,
you
need
to
be
able
to
get
to
real
time
from
a
business
standpoint.
What
does
that
mean?
That
means
you
need
to
be
able
to
implement
communication
infrastructures
that
don't
work
on
email,
because
email
kills
almost
any
good
idea.
It's
bad
for
software
development,
it's
bad
for
software
developers,
it's
also
cumbersome.
It
tends
to
reinforce
unnecessary
hierarchies
in
business,
and
you
know
most
of
the
time
it's
just
a
pain
in
the
ass
to
read.
A
So
you
have
all
this
email
and
you
want
to
do
your
code
and
instead
you
have
stuff
to
do.
That's
disjunct,
that's
out
of
sync!
That
was
yesterday's
problem
and
that's
called
email
in
order
to
get
your
developers-
and
this
is
very
important.
Part
of
of
integrating
with
github
is
to
get
the
information
that
github
produces
into
your
company
in
some
way
a
lot
of
people
probably
use
slack.
You
know
I've
used
and
implemented
slack
in
numerous
companies.
It
tends
to
be.
A
It
tend
it
tends
to
be
a
very
big
moment
of
truth
for
businesses,
because
they
thought
they
knew
what
they
were
doing
and
then
implemented
system.
Like
slack
people,
start
building
communities,
because
they're
allowed
to
do
that
they
get
information
that
they
otherwise
wouldn't
have
had,
and
they
can
do
it
all
very
quickly
and
they
can
operate
on
that
information
in
a
way.
That's
also
archived
and
and
synchronized.
So,
first
of
all,
you
can
do
every
automation
from
github
in
slack,
so
everything
every
time
you
do
a
pull
request.
A
Every
time
you
do
a
release,
all
that
information
can
be
provided
via
robots
into
slack
if
you're
dealing
with
customers
slack
also
helps
you
do.
That
slack
is
not
part
of
the
github
enterprise
platform.
Just
to
make
that
clear.
It's
part
of
another
platform,
that's
revolutionizing
the
way
companies
and
employees
and
companies
communicate.
A
One
thing
that
slack
does
do,
though,
is
it
gives
you
also
branches
to
and
capabilities
or
channels
to
work
with
with
companies
that
you
would
partner
with
as
a
business
or
customers
at
Horry.
We
use
discord
to
communicate
with
our
developer
community
discord
for
those
that
haven't
heard
about
it
is
popular
in
the
gaming
community.
It's
extremely.
A
Targeted
I
would
say
to
that
type
of
community,
but
for
us
and
working
with
software
developers
around
the
globe
that
are
in
in
Horry,
we
find
it
a
very
good
way
to
get
immediate
feedback.
Real-Time
information
about,
what's
going
on
with
the
software
we
build,
and
the
customers
and
community
of
contributors
that
we
want
to
connect
with
those
are
just
two
examples.
A
There
are
other
things
out
there
that
that
are
able
to
facilitate
and
and
help
but
I
think
a
very
important
thing
when
you
decide
to
go
with
a
platform
like
this,
be
realistic
about
the
real-time
opportunities
that
companies
like
github
platform
will
provide
your
business,
and
then
you
have
to
really
exercise
on
doing
that.
So
it's
a
change
on
many
different
levels
and
by
the
way
you
know
it's
just
like
websites
and
blogs.
A
Again,
that
gives
the
whole
company
a
way
of
getting
feedback
and,
in
some
sense,
a
way
of
interacting
with
customers.
Now
you
know,
I've
been
around
quite
a
long
time
in
the
software
area
and
I.
Don't
think
you
really?
You
can
do
and
build
great
software
by
just
asking
customers
what
they
want.
I,
don't
think
that's
really
a
great
approach,
because
software
by
itself
is
art.
It's
it's,
not
science,
it's
something
that
you
need
to
think
about.
A
Imagine
and
create,
but
feedback
helps,
especially
if
something's
broken,
and
especially,
if
you
want
to
get
information
about
new
new
features
that
you
thought
of
and
creating
a
scenario
and
a
system
by
the
way,
using
github,
maybe
even
using
a
public
github
repository
outside
of
your
enterprise
gives
you
a
capability
and
gives
customers
a
capability
of
of
working
together.
I'll
just
give
you
an
example.
A
A
Now,
in
order
to
work
with
that
cloud
company,
we
needed
to
have
a
way
of
giving
them
the
capability
of
cooperating
and
developing
and
testing
all
the
source
code
and
some
of
the
data
that
was
provided
and
every
day
the
teams
could
get
feedback
from
each
other.
What
was
working,
you
know
they
would
try
stuff.
They
were
located
in
Seattle,
doesn't
matter,
they
could
try
stuff
in
their
office.
We
could
do
stuff
here
in
Germany
and
having
that
interaction
and
that
sort
of
way
of
working
was
extremely
effective
and
github
was
the
base.
A
For
that-
and
you
know,
I
can
say
honestly,
there
wasn't
even
a
discussion.
We
had
one
phone
call.
We
set
up
the
project,
we
got
everyone
on
github,
everyone
already
had
their
github
users.
The
company
is
in
Microsoft
by
the
way.
So
you
know
this
is
again
how
old
work
and
how
you
get
interaction
and
feedback
for
new
software
and
new
inventions
today
depends
a
lot
on
your
ability
to
structure
things
and
work
with
things
and
get
your
company
involved.
In
that
now
we
talked
about
compliance.
A
We
talked
about
security,
but
let's
also
just
talk
about
mindset.
You
know
the
single
biggest
challenge
that
every
company
has
it's,
not
technology.
It's
not
policies,
it's
the
way,
you
think
about
things
and
letting
employees
work
in
a
way
that
where
they
can
collaborate
with
Google
or
Microsoft
or
github
and
do
stuff
and
exchange
information
is
very,
very
difficult
for
Joe
manager
to
understand.
Why
is
that
were?
How
is
that
going?
I
might
lose
my
job
if
somebody,
you
know,
provides
the
wrong
information.
A
That
mindset
is
not
going
to
change
because
you
implement
github
enterprise
or
any
other
technology,
but
that
mindset
will
change
because
you've
changed
the
way
you
work
and
the
potential
to
work
in
new
ways
is
a
highly
effective
way
of
shifting
the
thought
process
in
companies.
So
that's
a
benefit
that
you
would
get
from
implementing
this
whole
infrastructure.
A
So
when
I
say
that,
that's
because
you
know
the
silos
and
companies
are
built
around
politics,
power
money,
not
technology,
not
software,
not
developers.
So
some
of
these
structures
that
you
want
to
break
down,
you
also
need
structures
to
break
down
the
old
structures,
and
one
of
the
things
I
think
I
would
encourage,
along
with
the
implementation
and
rollout
of
inter
source
in
general,
is
to
really
have
a
dedicated
product
development
lab
now
everyone
here
knows
you
can
do
that.
A
Virtually
you
don't
need
to
go,
ask
Joe
manager
for
budget
or
get
some
permission
from
someone
you
can
set
up
a
lab
as
part
of
an
organization
inside
github
and
then
get
people
to
come
and
collaborate
on
new
things.
Let
me
give
you
some
examples:
new
programming
languages.
You
want
to
set
up
a
go
infrastructure
with
JavaScript
and
have
some
simple
apps
deployed.
Oh
by
the
way
my
manager
wants
to
see
how
you
program
an
app
on
the
iPhone
or
program,
an
app
on
any
phone.
A
Just
simple
things
where
you
can
then
get
people
come
show
push
this
button.
Look
at
this
code.
Make
a
change.
Do
a
pull
request.
Try
this
out:
it's
not
gonna,
break
anything,
no
customer's
going
to
see
this,
but
getting
people
in
this
lab
and
teaching
them.
How
to
do
things
is
a
critical
part
again
because
of
the
mindset,
because
of
the
fact
that
you
know
we
don't
have
the
luxury
in
business
of
going
back
to
school
every
day.
I
think
that's
a
shame.
A
I
think
people
should
be
learning
more
but
again
using
this
infrastructure
to
set
up
a
lab
and
give
people.
The
permissions
is
important
when
you
implement
github
Enterprise.
There
are
many
different
ways
to
do
it
speaking
here
from
my
own
perspective
and
experience
make
one
organization
don't
try
to
make
the
organization
that
was
there
today
or
is
there
yesterday?
A
Don't
try
to
implement
that
organization
and
get
up
because
you'll
fail
you'll
fail
because
the
benefit
of
inter
source
and
getting
to
inter
source
as
a
sort
of
business
philosophy
requires
you
to
open
up
the
whole
kimono.
Now
you
might
have
some
secret
sauce
if
you're
coca-cola
or
whatever
company
and
you
can
protect
different
repositories,
but
the
benefit
of
implementing
new
types
of
software
production
platforms
is
that
you
get
maximum
involvement
from
everyone
in
the
company.
A
Even
people
that
don't
do
software
should
be
on
github
and
the
reason
for
that
is
they
can
do
other
things.
They
can
write
documentation.
They
can
write
customer
stories,
they
can
add
things,
including
issues.
They
can
look
at
how
the
software
is
working,
don't
look
at
github
enterprise
and
Inter
source
in
general,
as
an
experiment
that
you
use
to
reduce
cost
big
mistake.
Look
at
this
as
a
way
of
all-inclusive
changing
the
philosophy
about
how
people
view
and
look
at
your
software
today.
A
You
know
again
just
one
example:
the
a
lot
of
times
companies
can't
maintain
the
software
they
have.
The
reason
for
that
is
they
have
people
that
worked
on
that
software
that
are
no
longer
alive
or
no
longer
in
the
company,
so
giving
those
repositories
an
option
to
have
other
people.
Look
at
it
and
you
know
I'm
happy
to
admit
I
developed
stuff
on
the
mainframe.
You
know
I
can
look
at
that
today
and
still
make
some
assessment
of
whether
it
can
be
changed
or
not.
A
A
lot
of
companies
have
opportunities
to
open
up
what
they've
done
in
the
past
to
their
current
employee
base
and
gain
information
from
that.
So
thank
you
very
much.
I
hope
that
that
was
helpful
for
you
and
I
look
forward
to
being
around
and
talking
to
you
about
any
of
the
topics
here
or,
of
course,
my
favorite
topic
of
today,
ory
and
I
have
even
brought
the
whole
company
with
me
in
case
you
have
some
security
and
API
challenges
that
you
want
to
discuss
as
well.
Thank
you
very
much.