►
Description
OpenShift Commons Gathering in Seattle on Nov 7, 2016 "Upstream This!" panel moderated by Alex Williams (The New Stack) with panelists from Google, Microsoft, RedHat, and CoreOS
A
B
B
B
C
B
Hey
everyone
I'm
Alex
Williams,
the
new
stack
we're
a
technology
news
publication.
We
write
about
the
container
ecosystem,
just
a
little
bit,
kuber
Nettie's,
just
a
little
bit
quite
a
bit,
actually
our
focus
on
application,
development
and
management
at
scale.
We
focus
on
explanation,
analysis,
we're
having
to
pancake
breakfast
this
week
with
our
pancake
robot,
so
we'll
be
3d
printing
pancakes
tomorrow
morning
and
wednesday
morning,
so
come
on
by
and
get
a
pancake
printed
yeah.
A
B
The
3d
printer
pancake
from
the
robot
itself
so
talking
about
robots
here
we
are,
you
know
the
world
of
automated
services,
open
source
ecosystems.
You
know
the
kuru
Nettie's
world.
You
know
if
there
are
a
lot
of
people
here
who
are
who
are
customers
who
may
not
be
as
familiar
with
things.
I
would
just
love.
You
guys
get
your
take
on
things.
Where
are
we
right
now?
Well,
you
know
what's
actually
happening
in
this
world.
What
is
it
that's
interesting
to
you
and
talk
up
a
little
bit
about
the
dynamics
of
the
ecosystem?
D
D
D
The
next
step
here
is
that
we've
developed
a
powerful
form
that
has
very
very
low
level
primitives
and
what
we're
starting
to
see
out
of
the
ecosystem
is
kind
of
out
leveling
it
making
it
easier
for
people
who
aren't
necessarily
the
early
adopters,
who
initially
just
fundamentally
get
it
they're
able
to
more
easily
map
to
their
existing
ways
of
thinking
and
leverage
the
platform
underneath
by
taking
some
of
their
existing
thinking's
on
how
they
deploy
applications,
how
they
operate
those
applications,
how
they
monitor
those
applications,
I
think
that's
kind
of
where
we're
at
right.
Now.
C
I'm
going
to
sort
of
echo
that
a
little
bit
of
I
guess
but
taking
a
slightly
different
direction,
which
is
I,
also
think
we're
starting
to
see
people
starting
to
think
about
what
this
means
for
how
they
build
applications,
which
is
to
say,
like
it
started
out
people
just
kind
of
experimenting
and
playing
around
and
learning
some
stuff
and
and
in
some
ways
taking
what
they
had
and
putting
it
into
the
space
and
I.
Think
what
you're
gonna
say.
C
One
of
the
analogies
I've
drawn
in
the
past
is
you
know,
object-oriented
programming,
mainstreamed,
I,
would
say
with
C++
sort
of
in
the
mid-80s,
85
86
ish,
and
then
in
the
early
90s.
You
see
this
explosion
of
patterns,
books
of
people
kind
of
stepping
back
and
doing
an
analysis
of
like
okay.
We
have
this
new
tool.
How
do
we
build
software
using
this
new
tool
and
I
think
we're
sort
of
going
to
start
entering
into
that
phase,
where
it's
no
longer
Oh?
What
is
this
tool?
How
do
I
understand
this
tool?
C
What
do
I
do
with
this
tool?
It
starts
being
like
what
are
the
best
practices
for
this
tool?
What
are
the
ways
that
this
you
know?
What
are
the
patterns
that
make
sense
for
this
world
and
I
think
that's
sort
of
the
phase
I'm
looking
out
into
the
future.
That's
sort
of
the
phase
where
I
think
we're
in
where
yeah.
E
So
I
think
we're
in
the
phase
where,
on
the
infrastructure,
sighs
the
patents
have
expired.
You
know
the
ideas
around
these
things
like
this
idea
that
I
have
a
strategic
advantage,
because
the
way
of
I
the
way
I
manage
my
software
or
my
hard
work
with
my
software.
So
you
know
we
would
tease
out
these
white
papers
kind
of
give
you
clues
on
some
of
the
design
principles,
but
there
is
no
way
most
people
could
actually
build
an
implementation
from
that.
E
So
what
we're
seeing
now,
though,
instead
of
a
white
paper
you're
getting
an
open
source
project,
sokku
bearnaise
represents
that
kind
of
open
source
project
around
these
I.
So
now
that
the
patents
are
wore
off,
everyone
is
able
to
participate
and
build
on
top
of
them
without
fear
of
retaliation
or
so
forth.
I.
F
But
it's
it's,
like
you
say,
like
the
ideas
are
out
there,
but
they're
unevenly
distributed,
and
the
other
part
I
think
is
really
important-
is
figure
out
how
to
type
process
to
this
stuff,
because
everybody's
process
is
different,
it'll
never
be
the
same,
but
the
primitives
for
process
kind
of
depend
on
what
you're
actually
doing
you
know
if
you're
doing
with
source
code
and
builds,
then
you
deploy
it
the
mechanism
and
the
place
where
you
deploy.
What
kind
of
process
you
have
do
tests?
Do
you
not
test?
F
B
Before
I
go
any
further,
I
probably
should
introduce
our
panelists
here
and
the
lousy
moderator
that
I
am
so
Brandon
Phillips
of
crow
ass,
your
brand
of
burns
microsoft.
We
have
Kelsey,
Hightower,
google
and
Clayton
Coleman,
bread
hat,
but
what
you
bring
up
is
to
me
gets
to
really
the
heart
of
how
open
source
communities
actually
work
and
like
with
new,
with
like
a
lot
of
new
kind
of
involvement
and
open
source
right.
B
So
the
way
we
think
about
it,
the
new
sack
is
like
softwares
at
the
center
of
business
right,
there's,
no
doubt
about
it.
Right
and
open
source
is
increasingly
at
the
center
of
software.
So
if
that
is
the
case,
then
that
means
a
lot
of
changes
for
both
the
you
know
for
actually
have
the
software's
built
and
how
it's
supported
and
how
its
managed
and
how
it's
a
ploy
and
all
and
everything
else
around
it.
A
lot
of
a
lot
of
companies
out
there
really
not
accustomed
to
this
kind
of
this
new
kind
of
world.
B
How
do
you
guys
balance
that
what
are
the
some
of
the
things
you're
trying
to
do
to
help
people?
You
know
to
help
manage
this
process
with
them,
because
there's
lots
of
different
diamond
dynamic,
dynamic
factors
here,
such
as
economic
interest,
that
you
guys
have
as
ender's
there's
there's
the
expense
requirements
that
fee
that
the
customers
have
there's
a
lot
of
different,
actually
dynamics
here.
That
I
think
have
to
be
taken
into
consideration
because
curious
on
your
guys,
perspectives
on
that
I
think.
F
One
thing
that
I
always
try
and
keep
in
mind
is
that
none
of
this
is
new.
They're,
like
we
always
like
to
like
everything,
old
is
new
again
and
I.
Think
you
know,
there's
been
alluded
to
is
most
of
the
patterns
are
things
that
we
and
instinctively
understand
and
a
lot
of
the
the
easiest
way
to
bridge
that
gap
is
to
help
people
find
the
metaphors
and
the
patterns
that
move
them
from
where
they
are.
How.
F
And
I
think
you
know
as
an
example.
Containers
as
a
pattern
are
really
just
virtualization
taken
one
step
further
and
so
I've
had
I
can't
even
count
the
number
of
discussions
I've
had
where
someone
says
well,
what's
this
whole
container
thing
I
said
well,
do
you
remember
what
it
was
like
to
virtualize
your
software
and
for
some
sets
of
people
that
was
all
they
needed
here
was
like?
Oh
we'll
just
go.
Do
that
again?
What's
the,
what
are
the
things
that
are
different
and
putting
it
in
that
frame
of
context?
E
So
I
think
when
you
talk
about
how
open
source
has
influenced
software
and
how
software
is
influencing
business,
I
think
it's
the
same
thing
that
kind
of
happened
to
the
music
industry
I
think
we
are
no
longer
under
the
control
of
a
few
select
vendors
who
can
actually
get
software
onto
the
shelves
so
we're
in
the
github
error
right.
So
the
github
error
is
very
similar
to
the
YouTube
error.
Even
if,
without
a
record
deal,
you
can
make
an
album
and
release
the
whole
thing
on
YouTube
or
your
website.
E
And
if
you
become
popular,
that's
it
you
get
to
go
on
tour.
You
may
not
make
very
much
money
on
your
album
sells
very
similar
to
software.
You
can't
really
sell
packaged
software
anymore,
but
you
can
actually
start
to
dominate
and
get
whatever
you
want
out
into
a
community
and
see
adoption,
probably
even
quicker
than
the
old
distribution
mechanisms
of
strength
software,
so
I
think
right
now
is
anyone
any
single
person.
I
think
doctor
is
a
great
example.
It
wasn't
one
of
the
big
vendors
that
came
out
with
docker
right.
E
This
was
kind
of
like
almost
a
side
project
implementation,
detail
of
a
much
larger
system
that
was
put
out
there
on
github
and
it
exploded
across
the
world
with
no
major
influence
really
from
the
vendor's
I.
Think
the
vendors
came
in
and
made
it
made
it
work
right,
like
the
big
tours
need
help,
but
I
think
that
is
an
example
that
now,
as
new
ideas
come
out,
there
is
no
one
gating.
When
these
new
ideas
get
to
be
released.
B
When
you
get
into
open
source,
you
know
when
you
get
in
these
open
source
ecosystems.
As
you
know,
Brandon
was
saying
especially
communities.
You
have
these.
You
know
it
gets.
It
gets
very
there's
some
real,
deep
complexities
here,
so
Brendan
I'm
curious
in
your
perspective
and
how
you
you
know
how
you
take
down
into
consideration
as
well
sure.
C
I
think
actually,
in
many
respects,
the
whole
goal
was
to
make
it
easier.
I,
don't
know
if
we
succeeded,
maybe
I,
maybe
we're
continuing
to
try
and
make
it
succeed
and
I
think
that
you
do
have
to
learn
some
new
ideas,
just
as
if
you
were
going
from
an
you,
know,
imperative
see
you
have
to
learn
about
this
like
what's
this
class
thing
like
why,
why
should
I
care?
C
What's
inheritance,
there's
there's
extra
stuff
to
learn
but
I
think
at
the
limit
what
you
actually
realize
once
you
learn
those
things
and
once
you
start
building
patterns
based
on
those
things,
is
it's
actually
easier
right?
It's
gotten
it's
harder
to
have
your
codes
sprawl.
If
somebody
tells
you
like
you
have
to
organize
your
code
into
this
thing
that
we're
going
to
call
an
object
and
it
kind
of
should
have
a
meaning,
and
it's
going
to
have
a
name
that
kind
of
defines
what
it
is
and
I
think.
C
More
importantly
and
I
think
this
is
also
about
the
open
source
community.
By
doing
that,
suddenly
we
started
talking
and
identifying
that
we
had
the
same
objects.
You're
like.
Oh,
you
have
a
you
know:
a
foo
over
there.
Well
I
have
a
fool
over
here
and
like
as
I
developed,
my
foo.
It
turns
out
that
this
is
a
best
practice
and
that's
and
so
I
think
there
was
more
learning
I
think
when
we
moved
to
having
shared
knowledge
and
shared
words
that
we
used
for
our
infrastructure.
C
Think
the
net
of
that
is
actually
a
win
for
most
businesses,
because
you
go
from
a
bunch
of
like
localized
areas
of
knowledge
to
a
place
where
we're
collaborating
on
knowledge
and
best
practices
around
the
world.
So
I
feel
like
we're
developing
this
shared
vocabulary
that
helps
us
sort
of
up
level
everybody
by
talking
about
the
same
so.
B
If
I
may
just
ask
a
follow-up
question
for
you
right
and
so
so
you're
with
microsoft
now
and
your
work
on
azure
and
cooper
Nettie's
in
and
azure
right,
so
that
shared
language
that
you're
discussing
here
and
that
knowledge.
How
is
that
transpiring
into
when
to
your
own
development
of
the
on
top
of
the
how's?
Your
project?
Well,.
C
But
I
guess
the
other
thing
I
would
say
that
is
a
truism
sort
of
points
to
what
Kelsey
said
as
well,
which
is
I.
Don't
think
anybody
in
infrastructure
wants
to
get
locked
in
again
right,
I
think
that
it's
very
clear
this
open-source
thing
has
made
everybody
realized
that
there
is
actually
a
place
where
their
code
can
go
anywhere
and
for
a
vendor
of
data
centers
effectively,
which
is
what
we
are.
C
That
means
we
have
to
provide
a
really
really
great
data
center
right,
great
performance
at
a
great
price
and
all
that
sort
of
stuff,
and
that
means
I
mean
at
some
level
it's
it's
harder.
You
know
as
a
business
right,
because
people
can
take
their
business
anywhere
with
it
with
Cooper
Nettie's,
but
it
also
means
we
produce
better
products
for
people,
so
I
think
it's
a
win
for
everybody.
In
the
end.
B
D
So
when,
when
I
think
about
doing
open-source
work
and
I
think
a
lot
of
people
think
this
way
is,
you
are
looking
at.
How
do
you
enable
capability?
So
if
you
look
at
like
say
that,
what's
the
difference
between
an
Android
device
and
the
Linux
kernel
like
the
Linux
kernel
enables
a
lot
of
different
capabilities
and
they
Android
like
when
you
get
an
android
device,
there's
actually
a
finished
product.
That
leads
you
to
an
end
and
experience
and
I
think
that's.
D
It's
really
the
difference
when
people
are
thinking
about
when
they
contributed
open
source
community
or
how
they
engage
and
balance
that
between
their
business
interests
in
there
and
the
overall
the
source
community
interest
it's.
How
do
we
create
these
kind
of
share
eight
languages
and
these
shared
patterns?
And
how
do
we
make
that
something
that
ensures
that
the
customer
and
the
ecosystem
doesn't
get
locked
into
any
single
vendor?
How
do
we
ensure
that
capability
ends
up
in
the
open
source
project
and
then,
when
you're
doing
that
whole
process?
D
How
does
that
actually
end
up
creating
like
an
indented
experience
for
the
user?
That's
like
compelling
and
solves
the
problems.
They
have,
and
generally
it's
like
very
niche
specialized
problems,
as
the
COO
benetti's
community
is
sort
of
this
general
platform.
Today,
a
lot
of
those
problems
are
really
integration
problems.
How
do
I
integrate
with
my
storage
how
to
integrate
with
identity?
How
do
I
integrate
with
my
security
compliance
over
time?
It'll
be
more
about
you
know.
D
B
With
that
so
with
that
that
product
experience
correct
right,
so
so,
let's
you
know
hypothetically,
we
have
a
customer
out
there
and
there's
all
these
companies
competing
right
for
that
same
customer
and
we
have
open
source
projects
in
the
open
source
projects
are,
are,
you
know,
are
fairly
open
and
you
know
those
those
customers
can
go
upstream,
whatever
they
want
and
basically
kind
of
like
say:
oh
I,
can
you
know
I
can
work
on
this?
Why
should
I
work?
You
know
why
should
I
work
with
you
I'm?
You
know
that
seems
like
you
know.
D
So
we
have
that
expertise,
and
so
we
provide
that
as
a
service
and
then
people
they
sign
subscribe
essentially
to
that
service
and
they
get
it
delivered.
I
think,
similarly,
like
you
have
to
make
smart
business
choices
like
it
doesn't
make
sense,
always
to
build
a
team
of
10
engineers
that
are
focusing
on
making
Coover
Nettie's
great.
Instead
of
making
your
product
eight
he'll
see
what
are
your
thoughts
so.
E
We
sing
this
the
bit
in
some
of
the
larger
businesses.
We're
given
the
same
scenario.
You
may
say,
if
I'm
paying
10
million
dollars
in
licensing,
how
many
developers
can
I
hire
and
if
you're,
smart,
you
go
to
github
and
you
look
at
the
names
like
wow.
You
hate
your
company.
You
really
hit
your
current
employer
because
I
can
see
that
all
your
commits
come
at
seven
pm.
E
Are
prime
hires
I
think
Facebook
was
a
good
example
of
bringing
in
some
of
the
postgres
core
members
right
on
that
saying
that
they
hid
it
there
pretty
former
companies,
but
sometimes
it's
cheaper
to
hire
the
core
maintained
errs,
have
them
on
site
and
when
you
do
that,
you
have
the
responsibility
of
allowing
them
to
continue
to
contribute
to
that
community.
Red
Hat
is
probably
the
biggest
example
of
something
like
this
right.
E
Like
red
hat
is
able
to
enter
new
spaces
by
going
in
and
saying
you
know,
Red
Hat
could
partner
with
some
of
these
other
projects
and
have
them
be
standalone,
but
I've
noticed
a
pattern
of
Red
Hat
just
independently
that
they
build
up
that
army
of
expertise
and
gain.
You
know
respect
with
that
community,
either
by
being
direct
contributors
or
hiring
in
the
entire
team
sent
to
us.
E
F
I
think
I
really
I
would
say
a
really
interesting
point
to
that
is
that
there
are
typically
fixed
pools
of
experience
in
these
sorts
of
areas
and
I.
Think
that's.
One
of
the
challenges
is,
if
you
think
about
acquisitions,
like
that,
where
you
hire
an
entire
group
of
developers
and
if
you
aren't
responsible
as
Brendan
Brendan
were
alluding
to
to
making
them
available
for
other
companies,
you've,
essentially
locked
and
asset
away,
that
you
might
have
been
dependent
on
I.
F
D
F
F
Think
everybody
on
this
panel
absolutely
believes
in
you
know
every
one
of
these
guys
has
demonstrated
being
responsible
in
these
communities
to
ensure
that
we
create
a
more
vibrant
ecosystem.
Even
though
you
know
there
may
be
specific
vendor
goals
that
may
run
against
us.
I
think
everybody
has
kind
of
demonstrated
that
level
of
professionalism
any.
B
D
So
I
think
there's
like
a
few
lessons
to
be
learned
there
and
one
of
which
is
you
need
people
from
the
beginning.
You
care
about
ensuring
that
the
governance
of
the
important
bits
of
intellectual
property
are
well
governed
from
the
beginning
and
I.
Think.
That's
probably
the
lesson
that
was
learned
here
and
that,
like
the
scene,
CF
and
Cooper
Nettie's
community
overall,
has
been
really
conscious
and
careful
to
ensure
that
not
just
like
the
community
as
a
software
project
is
doing
well.
B
E
I
think
no
GS
was
a
good
example
of
fork.
The
whole
thing
right
fork
it
go,
do
something
else
and
push
it
harder
than
what
you
thought
you
saw
before,
because
that's
also
the
other
power
of
open
source.
You
know
some
of
these
licenses
are
tailored
around
that
that
we
won't
always
agree,
and
you
have
the
power
to
hit
that
fork
button
and
kind
of
continue
off
in
a
different.
You
know
a
different
route
and
we
have
to
be
okay
with
that.
E
The
good
thing
about
nodejs
civils,
brought
back
we're
joined,
decided
that
having
two
communities
around
the
project
was
not
in
the
best
interest
of
everyone
involved,
so
I
think
a
lot
of
times
that
fork
button
is
really
what
allows
that
community
to
actually
have
some
say
right.
It
gives
you
that
real
power
to
fork
and
move
development,
where
you
see
it
so
it
kind
of
evens
the
playing
field
for
everyone,
even
a
lone
developer,
to
hit
that
button.
I
think.
B
F
B
I
just
want
to
get
a
kind
of
a
glimpse
of
who
who's
out.
Here.
You
have
a
question
about
this
at
all.
No
okay,
that's
fine!
Okay!
So
then
the
question
that
I
ask,
then
is
ok,
you
say
just
say
for
kit,
okay,
so
so
what
happens
when
you
are?
You
know
that
when
there's
two
kind
of
there's
a
dependency
between
Princeton's
to
open
source
organizations
right
and
then
and
and
you're,
maybe
you're-
you
know
you
what
you're
trying
to
get
way.
Would
you
trying
to
get
through
one
community
actually
doesn't
get
accepted
right
answer.
E
So
I
think
the
biggest
problem
is
what
causes
the
forks,
usually
Forks,
or
calls
when
there
is
no
way
to
get
the
change.
You
want
to
happen,
I
think
court,
I.
Think
Cooper
Nettie's
did
a
really
good
job
of
saying
we're
going
to
make
all
this
kind
of
API
driven.
You
can
add
what
feels
like
core
functionality.
E
I
think
third-party
resources,
one
of
the
biggest
things
that
Brendan
championed
you
saw
Korres
just
released
this
thing
called
operators
and
core
OS
was
able
to
do
that
without
recompiling,
all
of
Coober
Nettie's,
getting
the
whole
Cooper
Nettie's
by
community
to
agree
that
they
could
even
use
this
term.
They
were
able
to
put
that
out
without
in
the
open,
because
the
api's
are
there
so
API
to
me:
remove
a
lot
of
tension
from
these
projects.
Okay,.
F
Get
to
I
get
to
follow
up
the
new
json',
which
is
I,
think
the
best
thing
about
this
industry.
If
you
wait
a
few
years,
it
all
changes,
and
everyone
forgets
everything
that
happened
two
years
ago.
So
I
think
one
of
the
one
of
the
things
that
makes
this
particular
area.
So
interesting
is
the
amount
of
people
involved
from
a
whole
subset
of
communities
which
doctor
is
fantastic.
Docker
has
done
things
that
have
enabled
technologies.
There's
lots
of
other
people,
who've
done
that
before
and
there'll
be
lots
of
people
who
do
that
after
and
I.
F
Think
one
of
the
things
is
is
that
even
when
there
may
be
disagreements
between
communities
or
interests?
What
inevitably
happens
is
that
people
take
the
fundamental
technologies
and
they
rebuild
things
that
enable
them,
and
sometimes
that's
good
and
sometimes
that's
bad
and
the
goal
is
to
try
and
build
these
ecosystems
that
survived
even
disruptive
changes
like
that.
The.
B
E
E
E
Think
here
is
that
in
this
particular
case
and
not
and
not
all
of
docker
but
I-
think
people
really
weren't
clear
on
what
the
foundation
actually
was
in
the
case
of
decorative
foundation
was
the
Linux
kernel
and
is
still
there
is
still
open
and
it
still
has
the
API.
So
everything
that
allowed
docker
to
exist
allowed
lxc
to
exist
allows
rocket
to
exist.
You're
going
to
see
this
even
at
Microsoft
they
have
their
own
container
implementation,
that's
close
to
their
their
OS,
so
I
think
a
lot
of
times.
E
I
think
we
all
lost
track
of
where
the
foundation
was
so.
It
did
feel
very
shaky
because
you're
just
standing
on
the
subfloor
right,
there's
concrete
underneath
there
and
the
colonel
is
pretty
solid,
and
the
good
thing
about
the
colonel
is
that
there
are
a
lot
of
people
who
understand
how
to
add
that
value.
So
I
think.
The
reason
why
we're
all
pretty
confident
upstream
is
that
there
are
enough
people
in
the
industry
to
support
a
very
stable
foundation,
and
actually
what
you
actually
need
is
a
lot
less
than
what
people
saw
in
dhaka.
E
Doctor
is
great
because
it
gives
you
that
the
developer
workflow
it
gives
you
all
these
other
tools,
but
that
work.
That's
going
on
in
the
open
container
initiative
to
take
those
parts
that
are
the
foundation.
The
image
format
things
that
we
rely
on
some
of
the
AP
is
to
allow
those
pieces
to
work
with
any
OS
level
thing.
So
I
believe,
truly
that
your
investment
is
safe
because
a
lot
of
us
and
we're
out
here,
educating
more
and
more
to
show
people
where
the
actual
foundation
is
so
find.
Comfort
in
that
so
Brendan.
C
B
F
Thing
I
think
it's
actually
really
smart,
because
most
of
the
technologies
that
we're
talking
about
are
not
very
complex
technologies
in
terms
of
their
independent
pieces.
So,
like
the
registry
and
the
image
format
is
a
great
example,
just
a
bunch
of
tar
files
and
a
manifest,
and
we
can
pretty
it
up
and
format
it
and
standardize
it
and
make
tools
that
work
with
it
pretty
easily.
But
I
have
no.
F
I
have
no
concerns
that
there's
going
to
be
some
massive
disruption
in
either
image
format
or
container
running
that
are
going
to
really
impact
people
up
the
stack
because,
like
that's
the
beauty
of
open-source,
like
you
know,
regardless
of
whether
anyone
Forks
you
can
just
keep
using
the
old
version,
that's
supported
by
like
a
half
dozen
distros
at
this
point.
If-
and
you
know,
there's
always
going
to
be
time
to
react
to
these
things
and
that's
part
of
what
I
think
everybody
on
those
panels
job
is
to
do.
E
Last
thing,
let's
be
sure,
even
though
doctor
isn't
up
here,
they
are
very
much
a
part
of
this.
They
are
contributing
to
the
OC.
I
spec
you
see
their
names
I,
always
check
the
commit
messages
to
see
who's
participating.
The
doctor
engineers
are
participating.
We
may
not
all
agree
on
everything.
Even
between
companies.
There
aren't
doctor,
we
don't
agree
on
everything,
so
they
are
participating.
So
it's
not
that
you
know
it's
like
everyone
again.
Stalker
right
doctor
does
a
great
deal
of
work
across
the
board.
E
B
Well,
thank
you
guys
very
much
for
participating
in
a
very
interesting
discussion
here
and
look
forward
to
having
more
discussions
and
you're
going
to
be
following
up
with
the
discussion
on
the
container
ecosystem.
Aren't
you
yes
so
so,
who
would
like
to
see
a
3d
prettier
pancake
made
by
a
robot
tomorrow,
raise
your
hand,
alright
hope
to
see
you
there
in
the
morning,
then
thanks
a
lot
guys
bye,
bye
thanks.