►
From YouTube: Keynote: From “Open Source” to “Development in the Open”
Description
Keynote: From “Open Source” to “Development in the Open” - Chris Dias, Principal Program Manager, Microsoft
Microsoft’s history with Open Source Software actually began long ago, but recent projects like Visual Studio Code and TypeScript are some of the most popular, most active, and most “open”. What do these projects do differently, and what can we all learn from them?
Chris Dias
Microsoft
Principal Program Manager
Chris Dias is a Principal Program Manager at Microsoft working on Visual Studio Code, TypeScript, and Azure. VS Code and TypeScript are two of Microsoft’s flagship open source projects, enabling developers on Mac, Linux, and Windows to easily build and deploy modern Node applications. Chris works with many teams across Microsoft to ensure that Azure is a great platform to run modern, enterprise ready, global scale Node based applications in the public and private clouds.
A
And
if
you
look
under
the
azured
organization,
a
few
others
there's
I'm
sure
quite
a
bit
more,
but
we
all
haven't
always
done
open
source
that
well,
and
so
what
I
wanted
to
talk
about
today
is
sort
of
the
learning
and
the
journeys
that
we're
going
through
as
a
company
and
how
we
do
open
source
at
Microsoft
and
and
we're
going
to
use
the
the
story
of
Visual
Studio
code.
To
tell
that
story.
We're
talk
about
visual
Co
Co.
A
A
It
doesn't
stop
there
who
watches
Silicon
Valley
all
right,
not
as
many
people
as
usual
Visual
Studio
code,
but
more
are
going
to
use
it
because
of
Silicon
Valley,
because
in
the
last
episode
of
the
the
season
finale
finale
of
Silicon
Valley,
if
you
zoom
in
there
on
the
lower
left-hand
corner
they're,
actually
using
Visual
Studio
code.
So
that's
good
good,
free
advertising
for
us.
We
didn't
have
to
pay
for
that
at
all.
So
most
of
you
know
what
Visual
Studio
code
is
it's
our
cross-platform
lightweight
open
source
editor.
A
The
whole
idea
is
it
integrates
with
other
tools?
It's
not
a
contained
IDE
where
everything
happens
inside
use
it
with
other
tools.
We
try
to
release
it
as
a
service,
so
it
releases
every
day
as
a
matter
of
fact,
and
we
do
what
we
call
development
in
the
open.
So
they
just
do
your
code
didn't
just
sort
of
pop
up
out
of
out
of
nowhere,
oops,
sorry,
actually
before
I
go
there.
Let
me
talk
about
the
momentum.
A
Yes,
sorry,
so
we
do
have
quite
a
bit
of
good
momentum
on
there's
more
than
four
million
active
monthly
users
vs
code.
There's
more
than
seven
thousand
there's
almost
nine
thousand
in
the
gallery
right
now
we
have
an
NPS
score
of
62.
If
anybody
tracks
NPS
scores,
it's
a
very,
very
high
number,
it's
not
as
high
as
your
Apple
iPhone,
but
it's
still
pretty
good,
especially
for
a
developer
tool,
and
we
saw
that
just
a
to
JavaScript
survey
that
came
out
at
the
end
of
last
year.
A
We
were
pretty
clearly
in
first
place
for
a
number
of
tools
out
there
for
JavaScript
development
and
we'll
talk
about
what
that
means
in
a
minute.
But
as
I
was
saying
before,
Visual
Studio
code
didn't
just
come
out
of,
you
know
thin
air.
A
few
years
ago
we
were
sort
of
looking
at
our
developer
tools
and
we're
looking
at
the
audience,
and
we
were
saying
hey.
You
know
we
talked
to
dotnet
developers
on
Windows.
A
We
do
a
really
good
job
of
that
with
Visual
Studio,
but
there's
a
whole
set
of
developers
out
there
that
that
we
don't
have
a
conversation
with
and
I
like
to
tell
the
story
kind
of
like
this.
If
you
go
into
Starbucks
and
you
sit
down,
you
look
around.
There's
a
bunch
of
really
cool
kids
like
most
people
in
this
room
sitting
there
with
their
Mac,
they
get
their
headphones
on
and
they're
typing
away
and
they're
programming.
A
They're
doing
all
the
latest
frameworks
to
do
an
open-source
if
I
come
in
as
somebody
from
Microsoft
I
may
have
you
know
Visual
Studio,
which
is
a
really
really
great
development
tool,
as
some
of
the
best
debugging
and
intellisense
out
there.
If
I
want
to
talk
to
you,
I
can't
I
can't
walk
up
your
hey,
really
cool
kid
with
a
Mac.
A
I've
got
a
great
development
tool
for
you,
but
in
order
for
you
to
use
it,
you've
got
to
close
your
Mac
go,
get
a
Windows
machine,
download,
a
bunch
of
stuff,
the
dotnet
and
all
this
stuff.
So
there
was
no
way
for
us
to
have
that
conversation.
So
we
decided
that
we
really
need
to
go
in
and
and
be
where
the
developer
is
meet
the
developer,
where
they
are
not
say
hey,
you
know.
If
you
want
a
program
for
our
platform,
it's
great!
You
need
to
come
to
us
and
that
doesn't
work
anymore.
A
So
we
decided
to
build
vs
code
and
build
it
in
a
way.
That's
cross-platform,
but
it's
open
source.
We
also
looked
at
it
like
it
can't
just
be
open
source
because
the
people
that
we're
talking
to
are
not
just
slinging
code
over
the
wall,
which
is
what
Microsoft
has
done
in
the
past.
No,
we
really
had
to
embrace
this
idea
of
development
in
the
open.
So
what
does
that
mean?
A
So
the
development
team
for
Visual
Studio
code
is
really
comprised
of
about
20
22
engineers
were
distributed
globally
as
half
in
Redmond
half
in
Switzerland,
but
the
team
really
consumes
hundreds
of
open-source
projects
in
building
BS
code,
starting
with
electronic
chromium.
Hundreds
of
node
modules
that
we
use
inside
vyas
code
goes
on
and
on
and
on,
and
we
contribute
back
to
a
number
of
these
projects.
Just
you
know,
because
we're
working
on
them,
what
we
try
to
do
is
have
a
transparent
and
open
roadmap
right.
A
So
everything
that
we
do
the
conversations
the
planning
everything
goes
on
github
first
kind
of
drives.
Some
people
inside
Microsoft
a
little
bit
crazy
because
they
want
to
have
reviews
of
schedules
and
a
lot
of
stuff
and
go
look
at
it.
It's
fine,
but
we
try
to
put
everything
there.
Our
iteration
plans
our
test
plans
and
games.
So
at
the
beginning
of
every
month
you
can
see
what
it
is
that
we're
actually
doing.
Everyone
on
the
team
participates.
A
If
you
join
the
BS
code
team,
the
first
thing
you
do
doesn't
matter
if
you're
running
documentation
or
doing
customer
research
or
program
management,
you
go
on
your
write
code
and
you
contribute
back
to
the
product.
Everyone
test,
everyone
writes
documentation.
It
really.
This
isn't
like
hey
we're
great
we're
patting
ourselves
on
the
back,
but
we're
really
trying
to
live
this
model,
where
the
whole
team
participates,
we're
all
contributing
we're
all
putting
it
back
out
into
into
the
world.
A
Like
I
said
before,
we
try
to
ship
as
a
service
right,
so
we
ship,
you
know
daily
pretty
much,
not
so
much
on
the
weekends,
but
we
have
something
called
the
insiders
release
and
the
insiders
release
is
the
exact
same
version
that
we
use
to
build
vyas
code
and
ships
every
single
day
and
I
really
would
encourage.
Is
anybody
use
the
insiders
build
the
green
icon?
Okay,
good
more
people
should
use
it.
A
We
actually
built
a
tool
that
will
go
through
and
look
at
the
you
know
we
get
a
hundred
PRS
a
month.
It's
it's
a
credible
number
that
we
have
to
sort
of
process
through.
We
built
a
tool,
actually
will
go
through
and
pull
out
who
presented
them,
and
we
make
sure
that
we
recognize
people
for
the
contributions
back
to
the
project
and
what
we
also
try
to
do
is
you
know
not
in
the
distant
and
development,
but
we
try
to
have
this
sort
of
frontline
customer
engagement.
A
There
is
no
line
between
the
engineering
team
and
customers
right.
We
are
on
Twitter,
we've
got
165
thousand
followers
on
the
at
code.
Twitter
handle,
which
is
one
of
the
coolest
Twitter
handles
ever
didn't
cost
us
anything.
Everybody
asked
that
question.
So
everybody,
every
engineer
is
always
participating
in
all
those.
So
you
have
really
a
full
conversation
with
people.
A
What
issues
that
come
in
from
github
there's
over
a
hundred
issues
a
day
and
we
see
every
single
one
of
them
every
day
we
rotate
every
engineer
and
the
team
is
what
we
call
the
the
inbox
tracker
and
they
process
every
single
issue
that
comes
in,
we
farm
them
out
and
we
work
on
them.
We
have
debt
weeks
until
the
past
month,
September
yeah
we're
in
October.
A
Now
the
September
iteration
was
primarily
about
reducing
our
debt
overall,
and
so
we
sort
of
just
started
really
trying
to
work
out
in
the
open
and
the
hardest
thing
and
folks
talked
about
this
earlier
is
really
the
learning
was
how
to
become
humble
on
how
to
listen.
We
had
issues
in
github
that
were
just
sort
of
like
these.
These
very
passionate
discussions
about
things
like
tabs,
the
icon
did
anybody.
Remember
the
different
colored
icons.
A
People
were
very
passionate
about
that
and
we
had
to
listen
and
we
had
to
learn
and
we
had
to
respond
in
the
open
and
that's
what
we've
done.
We've
come
to
do
with
vs
code,
and
so
the
other
model
that
we
also
follow
is
this
idea
of
no
broken
windows,
and
so,
if
something
happens,
something
negative
happens.
We
want
to
reach
out
and
understand
what
was
going
on
and
see
if
we
can't
fix
it.
A
So
we
had
this
article
came
out
why
I
won't
be
switching
to
be
his
code
anytime
soon
it
hurt
us
deeply,
and
so
we
reached
out
to
this
guy
and
we
said
hey
what
what
what
are
the
issues
you're
having
and
actually
saw
the
community
reaching
out
to
this
guy
and
saying
hey?
What
are
the
issues
you're
having
we
didn't
want
to
berate
him
didn't
want
to.
A
A
The
villa's
code
is
a
better,
so
it's
just
a
little
bit
of
effort
a
little
bit
of
you
know,
interacting
with
the
community
and
and
you
can
turn
your
situations
around
just
like
this
and
there's
what
happens
is
when
you
have
this
community
that
is
sort
of
engaged
because
you're
engaged
with
the
community.
It
empowers
growth
of
the
product
itself.
It's
like
I,
said
the
state
of
JavaScript
survey.
What
that
does
when
that
comes
out.
People
say
it's
great:
that
causes
other
people
to
want
to
go
and
try
the
product
over
here
at
number.
A
2
we
have
West
boss,
maybe
wes
is
here,
is
Wes.
Are
you
here?
That
would
be
really
weird.
Wes
wrote
the
book
on
sublime,
like
there's
a
book
on
sublime
the
pearl
power
sublime
book,
Wes
wrote
it
one
day,
I
said:
hey,
I'm,
gonna
redo
my
machine
or
something
interested
in
what
people
are
doing.
Somebody
said:
hey
go,
try
be
his
code,
so
we
did
and
he
found
a
bunch
of
problems.
A
So
we
contacted,
we
said
what
are
your
issues
and
he
went
through
them
and
some
we
had
solutions
for
and
some
we
add
to
the
product
and
then
West
boss
switched
over
to
BS
code
and
now
he's
you
know
a
big
supporter,
but
he's
got
million
followers
same
thing
with
Smashing
Magazine.
We
did
some
work
with
with
those
folks
and
they've
got
over
a
million
followers,
and
so
when
they
tweet
about
it,
it's
way
more
impact.
Like
I
said
we
have
a
hundred
and
sixty
thousand
followers.
A
You
get
somebody
with
a
million
followers
and
they're
tweeting
about
the
product.
The
whole
community
sort
of
builds
upon
itself,
and
this
is
really
what
happens
when
you
sort
of
work
in
the
open,
not
just
open
source
you
work
in
the
open
and
for
us
from
Microsoft.
It
really
helps
to
change
perceptions
of
Microsoft
because
for
a
while
I
admit
there
was
some
negative
perceptions
of
Microsoft
and
we're
not
out
of
the
woods
we're
trying
to
improve
that,
but
a
lot
of
people
that
we
could
never
talk
to.
A
You
know
this
guy,
you
know
told
me,
fifteen
years
ago
my
favorite
editor
on
Linux
would
be
made
by
Microsoft.
I'd
have
laughed
at
you
right,
so
those
are
great
things
to
see
so
by
doing
development
in
the
open
we
connect
with
customers
much
more.
You
know
frequently
and
easily.
It
drives
development
and
growth
of
the
product
and
also
helps
us
change
the
perception
of
Microsoft,
so
people
are
more
open,
more
able
to
come
and
talk
to
us
about
other
things
we
may
have,
and
my
time
is
up.
Thank
you
very
much.
Happy
coding.