►
From YouTube: What does a career in Open Source look like? #DemoDays
Description
Emma Irwin, Senior Program Manager, from Microsoft's Open Source Program Office speaks through her own journey in open source and resources that she created as a result of her OSPO research.
0:00 - Start
2:01 - Emma's open source story
7:30 - Pushing through adversity and broadening my skillset
11:10 - Open source learning based on research
13:05 - What do I need to be competent in to work in open source?
16:49 - Our approach to onboarding
27:03 - Final thoughts
https://opensource.microsoft.com/program/
https://github.com/microsoft/ospo-courses/
https://github.com/microsoft/OSPO-Courses/tree/main/mapping-your-oss-career
A
Hello,
everyone
welcome
to
demo
days,
hope
you're
all
doing
well,
wherever
you
are
today,
I'd
like
to
introduce
you
to
emma
erwin
senior
program
manager,
who
has
conducted
some
pretty
neat
research
on
open
source
from
microsoft's
open
source
program
office.
Emma.
Can
you
set
the
stage
for
us?
Where
should
we
begin.
B
B
The
components
based
on
research
that
we
use
to
bring
people
into
open
source
inside
of
microsoft
and
I'll
also
be
sharing
a
lot
of
those
resources
for
you
on
github.
So
some
of
the
courses
and
research
tactics
that
we
use
are
available
for
you
to
use
as
well,
so
whether
you're,
an
individual
that
are
new
to
open
source
you're,
just
starting
to
tinker
or
you're
someone
that's
within
an
organization
trying
to
think
about
what
the
next
level
is
for
your
team.
B
I
hope
there's
something
here
for
everyone
and
I'm
definitely,
as
I
said
here,
to
take
your
questions
a
bit
later.
So,
as
I
said,
hi
my
name
is
emma.
I'm
a
pm
which
is
program
manager
on
the
open
source
programs
office
here
at
microsoft
and
you'll
often
hear
me
refer
to
that
as
an
ospo,
and
that's
also
a
terminology
that
you're
here
here
out
in
the
wild
as
well.
B
So,
as
I
said,
I'm
going
to
start
by
telling
you
a
bit
of
how
open
source
my
open
source
story.
I
think
we
all
have
ours
and
there's
no
two
stories
alike,
but
I've
been
working
in
open
source
since
2001
and
as
I
wrote
that
the
other
day
I
was
like
wow,
like
that's
a
that's
quite
a
long
time.
I've
seen
a
lot
of
change
and
experienced
a
lot
of
change,
and
you
know
I
really
am
excited
to
share
a
bit
of
that
with
you.
B
B
B
But,
as
I
mentioned
like
somebody
did
hire
me,
I
finished
my
one
year
program,
so
I
I
don't
have
a
degree.
I
have
a
diploma.
A
business
diploma
is
a
computer
programmer.
I
did
I've
done
a
lot
of
learning
through
open
source.
So
that's
something
also
that
I
extend
to
you
when
I
did
get
my
first
job.
My
first
paid
job.
B
I
remember,
actually
ran
out
and
got
a
gift
from
my
cat,
and
my
dog
was
the
first
thing
I
did
with
my
first
paycheck,
but
it
was
still
kind
of
considered
open
source
at
the
time
was
kind
of
a
back
basement.
Hacker
set
of
tools
which
is
was
kind
of
true,
was
fun.
There's
definitely
a
lot
of
freedom
around
it.
There's
a
freedom
to
do
more
and
achieve
more
kind
of
than
than
might
be
possible.
Otherwise
there
wasn't
even
a
github.
B
Yet
there
wasn't
even
get
our
version
management
system
back
then
was
cbs,
and
so
I'm
definitely
fast
forwarded
grateful
that
some
of
those
tools
exist
now
and
through
this
experience
of
starting
to
develop
with
some
of
these
tools,
I
started
to
understand
that
open
source
also
meant
community
right.
It
meant
meeting
other
people
learning
new
skills,
it
meant
collaboration
and
friendship,
and
I
started
to
learn
a
lot
more
than
I
set
out
to
so.
As
someone
who's,
an
avid
learner,
open
source
is
a
fantastic
place
to
be,
and
I
was
hooked
quite
early
on.
B
I
would
have
been
pretty
skeptical.
I
would
have
hoped
so
because
I
loved
it
so
much,
and
I
I
saw
so
many
ideas.
But
you
know
a
year
off,
as
which
I
took
for
my
baby,
and
I
would
never
change
that
definitely
made
me
doubtful
and
if
I
had
known
that
my
second
baby
would
be
born
with
cancer
that
we
would
spend
a
year
taking
her
through
chemotherapy
and
a
bone
marrow
transplant
and
that
she
would
survive
and
thrive.
B
B
The
answer
for
me
at
this
time,
after
you
know
sort
of
I
think,
probably
eight
to
ten
years
in
the
industry,
was
that
I
wanted
to
pay
it
forward.
I
wanted
to
start
teaching
others
like
I'm,
hopefully
teaching
you
today.
I
felt
that
really
positive
energy
that
comes
out
of
helping
others
succeed,
and
I
wanted
to
do
that.
B
B
I
did
a
lot
of
teaching
I
learned
to
teach,
which
was
something
that
I
found
out
that
I
loved
and
I
did
a
lot
of
teaching
on
github
as
well,
so
that
was
starting
to
emerge
as
not
only
a
technical
hub
for
collaboration
but
a
fun.
One
too.
I
was
able
to
accomplish
more
and
help
others
accomplish
more
as
well
and
this
direction.
B
You
can
read
the
slide,
but
I
really
is
to
make
it
easy
for
businesses
inside
organizations
like
microsoft,
to
include
open
source
in
their
strategies
and,
to
you
know,
have
excellence
in
those
practices,
but
also
to
enable
everyone
inside
the
company,
whether
they're
new
to
open
source
or
they're
moving
into
another
team
that
works
in
open
source
or,
however,
they
come
through
the
door
to
be
successful
in
their
goals,
to
use,
contribute
release
and
grow
and
ospos
are
becoming
more
and
more
popular.
There's.
B
A
group
together
under
the
linux
foundation
called
the
to
do
group
where
lots
of
companies
come
together
to
learn
about
open
source
and
osbos
you'll
find
them
inside
companies
like
microsoft,
government
agencies,
academia,
non-profits
and
beyond.
So
it's
really
becoming
a
way
of
working
for
open
source
inside
companies.
B
And
one
of
the
things
that
we've
built
at
microsoft
is
a
learning
program.
So
learning
is
a
theme
throughout
everything
that
I
talk
about,
but
I
think
it's
also
so
central
to
how
we
build
and
learn
open
source
and
how
we
empower
others.
So,
there's
a
link
here
at
the
bottom,
the
github
ospo
courses.
This
is
where
I'm
publishing
some
of
the
courses
that
I'll
be
talking
about.
B
There's
a
couple
in
there
now
which
I'll
get
to
but
yeah
so
open
source
learning
is
a
program
of
the
ospo
microsoft's
ospo
and
a
lot
of
what
we
are
building
and
we've
built
comes
from
research.
So
again,
learning
not
coming
so
much
with
an
opinion,
but
with
a
willingness
to
listen
to
what
people
are
struggling
with,
and
you
may
have
ideas
and
thoughts
about
that
as
well.
B
If
you're
in
an
organization
I'll
just
mention
that
we've
shared
all
of
our
survey,
questions
in
this
repository
at
the
bottom
called
ospo
surveys
anyways
through
the
research.
We
learned
that
you
know
there's
kind
of
this
equal
split
between
what
people
want
to
learn
in
the
capacity
that
skill
sets
are
important
and
a
lot
of
times.
When
we
talk
about
engineering
engineering
practices,
we
do
like
learners
get
a
little
bit
not
stuck
but
like
over
focused
on
technical
as
being
the
primary
skill
that
people
need
to
learn.
B
But,
as
we
saw
in
this
survey
like
half
of
what
people
were
requesting,
in
fact,
there
was
almost
like
an
equal
request
for
cultural
and
training
around
people.
So
people
wanted
connection
they
wanted
to
learn
from
each
other
to
meet
each
other.
To
share
stories
to
ask
questions.
You
know,
probably
more
than
ever,
a
need
with
hope.
It
happening
and
people
isolated.
B
So
I
really
took
this
as
a
important
call
to
action
to
ensure
that
the
people
part
of
open
source
is
equal
to
the
skills
that
we
teach
and,
if
you're
wondering
how
we
think
about
competency
areas
in
open
source,
maybe
you're
asking
yourself
as
I
go
through
my
career.
What
are
the
things
that
I
need
to
be
competent
in
to
you
know
find
my
the
career
that
matters
to
me
through
open
source.
B
These
are
the
ones
that
we
focus
on
and
we
build
policy
tools
procedure,
not
just
training,
but
these
are
the
common
series
which
are
using
open
source.
So,
if
you're
building
a
product,
an
ingesting
open
source,
there's
a
series
of
competencies
around
that,
of
course,
contributing
to
open
source
really
important.
B
Releasing
and
growing
sometimes
you'll
find
that
people
talk
about
releasing
open
source
and
growing
in
the
same
kind
of
bucket
or
area.
But
I
think
it's
really
important
to
separate
those
two,
because
there's
a
lot
involved
in
each
and
then
we
can
be
a
lot
better
at
each
by
kind
of
breaking
them
down
a
bit
more
then
again
to
the
cultural
components.
This
is
true
inside
organizations.
B
So
you
know,
community
building
comes
up
as
a
kind
of
a
way
that
people
describe
what
we
do
for
our
for
external
communities,
but
it's
really
really
important
inside
of
organizations
and
companies
as
well.
You
know,
microsoft
is
part
of
the
open
source
community
in
and
we
want
to
make
sure
that
we
are
like
honestly
and
humbly
achieving
our
goals
with
others
that
we're
collaborating
with.
B
B
I
mean
you
can
have
tools
where
people
don't
know
how
to
use
them
or
policy.
They
don't
know
where
to
find
them.
Then
they're
not
really
enabled
purpose.
Of
course,
there's
so
much.
You
know
there's
the
purpose
of
the
product
that
you're
working
on,
but
connecting
to
the
bigger
impact
in
the
world
or
for
your
customers,
or
you
know,
there's
just
there's
so
much
in
that
category
as
well,
and
the
importance
of
vulnerability
and
trust
be
possible,
so
that
psychological
safety
is
something
that
we
try
and
embed
in
all
of
our
training
as
well.
B
From
this,
we
build
a
series
of
workshops
and
training
programs.
These
are
some
I'm
not
going
to
dive
into
the
meaning
of
each
but
inclusive
governance
is
that
you
know
code
of
conduct,
etiquette
guidelines,
making
sure
that
those
who
have
been
traditionally
harmed
and
marginalized
in
open
source
are
set
up
for
success.
B
We
also
have
self-study
options,
so
we
have
something
called
github
and
microsoft.
101,
there's
lots
of
great
training
programs
for
online
and
in
other
places
for
github.
This
one
is
specific
to
the
context
of
that
inside.
So
we
have
standards,
for
example,
that
every
repository
needs
to
have
a
code
of
conduct
file
and
there's
specific
standards
for
licensing,
so
this
kind
of
gets
the
things
that
are
over
and
above
what
you
might
find
on
like
traditional
or
online
training
programs
for
github,
which
we
also
encourage
people
to
take.
B
The
etiquette
guidelines
is
just
a
self-study
course
of
that
inclusive
governance
and
then
mapping
your
open
source
career
is
probably
the
most
relevant
to
this
talk
and
is
also
available
in
the
ospo
courses.
Github
repository
that
I
mentioned
and
I'll
give
you
a
link
to
that
on
the
very
last
slide
and
encourage
you
to
take
that,
because
that's
a
lot
of
what
I'm
presenting
here
today
is
kind
of
bucketed
in
there.
B
And
so
we
found
ourselves-
or
I
found
myself
with
like
a
lot
of
different
information.
We
have
all
these
workshops.
We
have
training,
programs
or
sort
of
the
self-study
programs.
We
have
policies
and
documentation.
We
have
things
like
meetups
where
people
can
come
to.
We
have
a
newsletter.
So
that's
like
a
lot
of
information
to
to
throw
at
people-
and
I
don't
know
what
it's
like
at
your
company
or
your
school.
But
onboarding
rarely
looks
like
this.
B
It
really
looks
a
lot
more
like
this,
so
one
of
the
things
that
we
thought
about
was
how
to
make
that
a
little
bit
more
digestible
as
people
came
into
the
company
or
people
transitioned
wanted
to
provide
them
with
an
onboarding.
So
we
embed
in
existing
programs,
so
part
of
the
role
of
an
ospo
is
not
to
kind
of
live
in
its
own,
recreate
things.
We
try
and
embed
an
existing
program,
so
existing
onboarding
programs
for
employees.
We
embed
this
training
it's
one
hour
again
we
bring
people
together
and
I'll.
B
Just
gonna
walk
you
through.
I
thought
it
might
be
helpful
for
your
own
thinking
around
onboarding
to
open
source,
how
we
do
that,
how
we
bring
our
employees
into
that.
I
love
this
photo
so
quick
onboarding
overview.
So
these
are
the
high
level
topics
that
we
cover.
The
first
thing
is
we
introduce
people
to
inspiring
folks
inside
the
company,
but
I
know
in
my
early
days
of
open
source
that
people's
story
was
really
important.
B
One
of
the
earliest
inspirations
for
me
was
angela
angie
byron
at
the
drupal
project,
webchick
on
twitter,
having
the
those
sort
of
inspirational
people
that,
where
you
see
like
you
know
that
they
they've
made
come
from
a
background
like
yours
is
really
important,
so
I'm
gonna
actually
play
one
of
the
videos.
We
have
three
production
videos
that
we've
made
of
open
source
maintainers
at
microsoft
and
you
can
find
all
of
those
in
the
github
repository
for
mapping
your
open
source
career
they're
all
linked
from
there,
but
I'm
just
going
to
play
one.
C
C
I
didn't
actually
major
in
computer
science,
I
majored
in
theater,
so
after
college,
I
did
a
year-long
certificate
program
at
the
university
of
washington
to
learn
more
about
programming
in
a
professional
context.
Here
at
microsoft,
I
am
microsoft's
representative
on
the
board
of
directors
for
the
newly
formed
rust
foundation.
I
also
work
on
rust
usage
within
microsoft.
C
I'm
working
on
a
project
called
clearly
defined,
which
combs
the
web
combs
package
repositories,
chrome's,
github,
repos
and
more
to
find
license
information
for
lots
of
different
open
source
components.
You
want
to
be
the
source
of
truth,
for
if
someone
is
using
an
open
source
component
wondering
about
its
license,
they
can
come
to
clearly
defined
and
find
out
that
information.
C
There
are
two
qualities
that
make
a
great
leader
in
the
open
source
world
and
they
are
humility
and
empathy,
and
I
want
to
empathize
those
qualities
can
be
learned
when
it
comes
to
technical
challenges.
I
learned
the
hard
way
that
I
needed
to
use.
The
acronym
halt.
Halt
stands
for
hungry,
angry
lonely
or
tired.
If
I
am
one
of
those
things,
I
shouldn't
respond
right.
At
that
point,
I
need
to
step
back.
Take
a
walk
eat,
something
do
whatever
it
is
to
get
myself
out
of
that
state
and
then
coming
back.
C
My
interactions
are
always
so
much
better.
Recently,
I
have
discovered
the
joy
of
gardening,
and
one
of
my
favorite
things
to
grow
is
greens,
because
I
have
three
pet
rabbits.
It's
not
only
a
good
way
for
me
to
unwind
at
the
end
of
the
day,
working
in
my
gardens.
It's
also
a
wonderful
way
to
produce
food
for
my
wife
and
I
and
our
pet
rabbits.
B
Yes,
so
nell
is
actually
one
of
the
members
of
the
open
source
programs
office,
ospo,
really
inspiring
person.
I
love
you
know.
I
told
you
a
bit
about
my
story
where
I
started,
and
you
know
that
nell
started
as
a
theater
major
and
is
now
on
the
russ
foundation
board.
I
mean
just
shows
you
the
potential
when
you're
asking
yourself
that
question
about
where
can
open
source
take
me.
Where
do
I
want
it?
Where
do
I
want
to
go
so?
B
The
second
part
is
that
we
introduce
people
to
inspiring
projects,
but
in
the
context
of
you
know
this,
this
just
came
from
someone's
idea
right.
So
babylon.js
is
a
3d
web,
rendering
package
that
came
as
an
idea
of
a
microsoft
engineer
who
pitched
it
to
his
manager,
who
then
signed
off
on
a
pilot
to
test,
releasing
it
as
an
open
source
project
and
since
then
it's
grown
to
have
its
own,
really
vibrant
and
a
collaborative
community.
B
The
there's
also
a
team
that
works
on
this
at
microsoft.
So
when
we're
onboarding
folks,
we
want
them
to
know
that
their
ideas
matter
and
that
open
source
is
a
way
that
they
can
get
there
and
having
a
tangible
example
of
that
is
really
cool.
If
you've
ever
used,
microsoft
teams
and
the
heart
button,
emojis
or
the
hand
clapping,
that's
actually
babylon
js.
That's
powering
that.
B
So
I
always
sort
of
make
a
point
of
that
when
we're
going
through
as
well
and
then
again,
part
three
is
really
just
awareness,
the
training
that
I've
already
been
through
that
and
there's
that
link
again
at
the
bottom,
I'm
trying
to
link
as
much
as
possible-
I'm
not
sure,
maybe
at
the
end,
how
to
share
those
but
yeah.
Just
that.
There's
training
that
we're
here
for
you
that
it's
not
just
skills
that
we
want
you
to
figure
out
how
to
talk
to
have
those
manager.
B
Conversations
with
you
know
one
of
the
things
that
I
hear
is.
I
need
to
make
sure
that
my
manager
understands
why
this
matters,
why
contributing
to
the
upstream
is
important
and
how
that
skill
building
is
important.
So
this
course
is
really
set
up,
not
just
for
people
to
feel
successful,
but
that
they
can
talk
to
their
manager
about
how
that
scopes
to
the
things
they
want
to
do
for
their
career
and
for
their
team.
B
Part
four
is
the
similarities
and
differences
with
inner
and
open
source.
So
I
don't
know
if
inner
source
is
a
term
you're
familiar
yet
familiar
not
with,
but
basically
inner
source
and
open
source
are
the
same
in
that
they're
about
collaboration
outside
of
the
the
outside
of
the
team
that
owns
a
product.
B
B
And
my
slides
just
went
away:
okay
they're
back,
so
it's
really.
I
found
that
at
the
beginning,
when
I
started
inside
of
organizations,
this
is
used
interchangeably
because
they
are
so
similar,
but
it's
really
important
to
also
know
the
differences,
because
then
you
can
ask
better
questions,
and
I
love
a
meme
here
and
there
part
five
is
the
importance
of
contribution,
something
that
we
encourage
everyone
to
do
at
microsoft
and
have
many
many
ways
of
encouraging
that
and
rewarding.
B
There's
testing,
there's
reviewing
and
validating
prs,
there's
diversity
and
inclusion,
and
I
could
go
on
so
being
a
board
member
and
that
sort
of
thing.
So
we
really
make
this.
We
really
want
to
make
this
feel
critical
because
it
is.
This
is
like,
hopefully,
a
cartoon
you've
seen,
there's
a
tiny
peg
maintained
by
a
developer
in
nebraska,
actually
no
developer
nebraska,
but
he
says
this
is
not
about
him.
B
Part
six
is
we,
you
know
we
have
a
security,
serious
talk,
I
mean
you've,
seen
probably
in
the
news.
There's
lots
of
incidents.
You
know,
there's,
there's
lots
of
threats
out
there
threat
actors
so
really
walking
people
through
initially
what
the
their
responsibility
is
to
building
secure
software
so
and
some
of
those
are
just
basic
best
practices,
don't
put
keys
tokens
in
your
your
code
and
publish
it,
so
we
walk
through
that
pretty
simply
so.
B
The
way
that
we
have
sought
to
solve,
that
is
to
use
github's
project
feature
to
create
an
onboarding
experience,
and
so
what
that
does
is
that
each
column
is
broken
into
a
time
period.
So
the
the
first
column,
I
don't
know
how.
Well
you
can
read
this
I'll,
just
quickly,
read
it
to
you.
It
says
first
step
so
serve
in
the
in
the
first
week.
There's
things
that
we
absolutely
you
know,
need
people
to
do
or
that
we
know
that
they
will
need
in
the
future.
B
B
I
don't
know
what
these
are
called
component
over
to
the
the
done
column,
which
you
actually
can't
see
in
the
screenshot.
Second,
steps
are
in
the
next
month,
the
third
or
as
you're
getting
settled
in
so
the
goal
of
this
is
just
to
make
sure
that
people
are
onboarded
properly
and
that
they're
not
overwhelmed
and
it
feels
achievable
to
them
and
then,
at
the
end
of
the
day,
they
can
talk
to
their
manager
and
show
their
progress
as
well.
B
B
And
so
finally,
I've
covered
a
lot,
hopefully
some
of
that
inspired
your
thoughts
and
your
vision
for
yourself
for
your
team
for
your
organization.
Certainly
there's
a
lot
more.
That
could
be
said
and
I'm
sure
that
you
have
experiences
that
you'd
want
to
share,
but
I
think
the
question
to
ask
ourselves
continually
is:
where
do
we
want
to
go
now
and
how
can
open
source
take
us
there?
B
How
can
it
take
each
of
us
there
and
I've
linked
here
at
the
end,
the
mapping,
your
open
source
career,
which
is
very
lightweight
based
on
some
of
our
hr
resources
for
career
mapping
and
the
potential
for
open
source?
I
encourage
you
to
take
that
feedback
is
warmly
welcomed
issues
prs.
Anything
that
you
feel
is
missing
is
also.
You
know,
we'd
love
your
contributions
as
part
of
that.