►
From YouTube: Open Source is for Everyone, Anyone, Everywhere! - Morgan Carroll, Brittany Barnes & Dixsie Wolmers
Description
Open Source is for Everyone, Anyone, Everywhere! - Morgan Carroll, Brittany Barnes & Dixsie Wolmers, IBM
Speakers: Brittany Barnes, Dixsie Wolmers, Morgan Carroll
We are three IT professionals in the early stages of our careers working in diverse areas. Marketing, front end user experience design, and cognitive software. We were all intrigued by open source and joined a jump start program as mentees to learn more. This is our journey from knowing nothing at all about open source, to choosing open source projects that we felt we could learn from and bring value to, to how we are all now three successful open source committers. This led us wanting to share our stories, the good bits as well as the bad bits, the mistakes we made and the things we wish we could tell ourselves before we had started. Whether you're an experienced project lead wanting to attract more newbies like us, whether you're not sure how far out of your comfort zone to go dipping your toes into open source projects, come and hear our thoughts, feedback and ideas.
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
B
Hi,
I'm
dixie,
I'm
based
out
of
boston,
texas.
I've
been
at
ibm
for
about
two
years
now.
I
do
not
have
a
computer
science
degree.
I
actually
have
a
bachelor
of
science
in
education
prior
to
college.
I
was
in
the
military.
I
was
a
radar
technician
for
about
five
years
and
then
I
went
to
school,
got
my
degree
in
education
and
taught
as
a
science
teacher,
ran
code
clubs
and
fell
in
love
with
coding,
and
here
I
am
now
front
end
developer
at
ibm.
A
So
that
was
one
of
the
things
I
really
liked
about
ibm
because
they
gave
me
like
some
free
time
to
actually
explore
those
interests
and
work
in
that
area
as
well
and
just
like
with
open
source
coding,
there's
a
coalition
we
could
join
and
now
I'm
an
open
source
community.
So
I
think
ibm
is
so
big
and
so
broad
that
was
one
of
the
things
that
led
me
to
it.
Yeah
one
of
the
sweetest
things
is
when
the
girls
will
say
wow.
A
B
I
would
like
to
see
more
women
doing
other
things
you
know
outside
of
design
outside
of
front
end
development.
We
do
have
some
back-end
engineers
who
are
women
on
different
time
zones,
but
I
feel
like
an
open
source
as
a
whole.
As
a
community,
I
don't
know,
have
you
guys
had
a
lot
of
experience
with
women
in
the
field
or
have
you
worked
with
other
women
in
open
source.
A
A
I
think
it
would
be
interesting
to
see
like
if
there's
a
way
to
find
you
know
open
source
projects
that
are
focused,
and
I
don't
even
know
if
this
is
a
thing
you
know
focused
on
diversity
like.
If
I
want
to
be
part
of
a
diverse
project,
is
there
a
place?
I
can
go
to
do
that
or
is
it
just
up
to
us
to
make
that
diversity
ourselves?
I
like.
B
B
You
know
fresh
learners
who
are
just
in
school
learning,
something
new
and
new
technology
who
are
getting
introduced,
senior
people
who
maybe
have
never
done
open
source
or
want
to
switch
to
something
else
to
gain
some
more
experience,
and
then
just
people
who
are
super
experienced
and
have
so
much
to
contribute.
I
think
you
know,
as
community
members
we
should
be
looking
and
reaching
out
to
people
and
saying
hey
anybody
can
do
this.
You
can
do
this.
We
want
you
here,
even
if
you're
just
learning
we
want
you
here,
contributing.
A
I
know
I
joined
one
and
it
was
a
small,
long-running
close-knit
open
source
community.
So
it's
a
little
bit
more
difficult
for
me
because
they
were
really
close
and
tight-knit,
and
I
felt
kind
of
scared
at
first
to
ask
them
questions.
So
I
know
when
I
made
my
first
contribution,
you
had
a
minimum
number
of
pull
requests
that
you
had
to
get
and
being
new
to
the
whole
experience.
I
had
about
75
of
them
and
I
couldn't
get
the
last
one
that
I
needed
and
I
waited
like
a
week
and
I
was
so
worried.
A
I
was
like
how
am
I
gonna
get
this?
I'm
gonna
have
to
talk
to
someone
I'm
going
to
bother
them
because
I
felt
like
it
was.
It
was
going
to
bother
them
since
they
were
so
close,
and
you
know
they
weren't
really
talking
about
the
small
pieces
of
it,
which
is
just
reviews.
So
I
finally
worked
up
the
courage
and
I
sent
them
an
email.
A
You
had
to
send
email
in
this
community
because
they
didn't
have
slack
or
anything
new.
It
was
just
the
newsletter
blast
so
that
in
its
own,
was
another
hurdle
for
me,
because
I
thought,
okay,
I'm
sending
an
email
that
feels
way
more
official
than
it
should,
but
I
sent
it
out
basically,
and
it
was
so
much
more
casual
than
I
was
expecting.
The
team
was
very
welcoming
and
it
actually
spurred
another
discussion
where
we
brought
up
that.
A
If
you're
making
like
a
smaller,
straightforward
change,
then
maybe
we
would
lower
the
pull
request
count
and
it
was
because
I
was
new
and
bringing
up
these
new
topics
to
the
team
that
we
we
made
some
change
happen,
whereas
they
had
been
in
it
the
whole
time
they
were
already
familiar
with
it.
So
even
just
having
one
fresh
new
perspective,
it's
really
interesting
to
see
how
it
changes
the
community,
like
that.
B
B
A
B
A
Think
we're
all
thinking
the
same
thing
because,
like
you
get
into
like
you
know,
people
think
if
you're
contributing
to
open
source
like
I've
got
to
go,
add
like
a
whole
new
feature.
So
I'm
like
no
it
you
usually
have
to
start
out
with
something
simple
and
for
me
that
was
documentation
because
I
was
so
nervous.
I
was
like.
I
can't
do
this.
Oh
my
gosh,
I
mean
you
know.
I
shouldn't
think
that
way.
A
We
all
think
that
way,
but,
like
I
was
like
you
know
what
I'm
just
gonna
start
with
the
documentation
like
this
one,
simple
thing
I
wanted
to
do
more
than
that,
but
I
was
like
this
is
just
something
you
know.
Reading
the
documentation
and
understanding
it
is
going
to
help
me
understand
the
project
and
being
a
fresh
set
of
eyes
on
the
documentation
is
going
to
show
me
like.
B
B
New
developers
feel
like
they're,
not
super
experienced,
everybody
has
a
talent,
everybody
has
a
skill,
and
everybody
has
something
to
bring
to
the
table
whether
it's
translations
or
accessibility
design
documentation.
What?
What
do
you
call?
Technical
writing?
Yeah,
technical
writers,
everybody
has
a
skill
and
everybody
can
be
a
valuable
member
of
a
team
if
they
choose
to
work
on
that
project.
A
Yeah
and
the
variability
of
your
contributions,
it
really
makes
the
experience
as
hard
as
you
want
it
to
be,
unless
you
scale
it
to
your
capacity,
because
you
can
choose
to
start
out
with
those
smaller
contributions
that
are
straightforward
or
documentation
or
you
can
come
in
and
say.
I
really
understand
this
content
and
I'm
going
to
write
100
lines
of
code
right
now
and
that's
just
wednesday.
A
You
can
really
come
in
and
choose
which
one
that
you
want
to
be
and
make
the
experience
yourself
yeah
for
sure
this
conversation
is
making
me
think,
like
you
know,
if
I
want
to
start
contributing
more
to
open
source
like
I
have
to
think
of
something
you
know,
maybe
that
I'm
interested
in-
and
I
love
dogs
just
wondering
if
there's
some
kind
of
open
source
community,
that's
just
all
about
dogs
that
I
could
contribute
something
to
now.
I'm
gonna
have
to
look
into
it
because
it
doesn't
have
to
be
code.
B
You
know
what
they
say
with
apps,
there's
an
app
for
everything.
There's
literally
like
a
project
for
everything
you
go
on
github.
There
are
tons
of
readmes
that
have
different
open
source
projects
on
there.
You
know
hey,
get
started
on
this
one
or
hey
you.
Looking
for
this,
like
these
are
a
list
of
projects
you
can
do.
There
are
tons
of
resources
online.
My
personal
friend,
favorite
is
dev.2.
B
B
B
Mansplaining
mansplain
yeah,
so
mansplaining
you
guys
can
define
it
a
little
bit
better
than
me,
but
mansplaining
is
explaining
a
concept,
but
explaining
things
like
on
five
is
a
good
thing.
If
that's
what
the
person
wants.
But
if
I
ask
a
question
about
something
technical,
I
don't
need
it
automatically
broken
down.
Like
I'm
five
immediately.
I
don't
need
someone
saying:
oh,
do
you
get
that
or
oh
do
you
understand
this?
It
is
good
to
follow
up
to
see
if
I'm
tracking,
but
it's
the
tone,
you
know
it.
B
You
have
to
watch
your
tone
in
slack
messages,
discord
messages,
whatever
messaging
system
that
you're
using,
sometimes
even
in
code
reviews.
It
could
be
a
little
demeaning
whether
it's
the
code
review
or
the
explanation
and
most
of
the
times
like,
I
would
say,
95
99
of
the
time.
It's
good
intentions,
it's
not
meant
to
harm.
It's
not
meant
to
make.
You
feel
bad,
but
don't
assume
you
know,
we
don't
know
things
and
vice
versa.
The
other
way
around
like.
I
should
always
ask
my
questions.
I
shouldn't
feel
like.
B
A
I
love
they
brought
that
up
too,
because
I
think
sometimes
people
will
just
assume
we
don't
know
something
without
maybe
asking
like
do
you
do
you
know
how
to
do
this
instead,
just
launch
straight
into
well.
Here's
how
you
would
do
it.
You
know,
and
that
brings
up
implicit
bias.
We
all
have
implicit
bias,
but
you
know
if
you
see
women
who
are
you
know
if
I
say
I'm
a
software
engineer,
front-end
developer
whatever,
like
we
don't
need
to
be
questioned
on
our
credentials.
A
We
don't
need
someone
to
assume
like
well.
Are
you
really
or
do
you
like?
You
know?
I've
been
asked
plenty
of
times,
so
you
write
code
and
I'm
like
god.
What
do
you
think
this
means
you
know
and
that's
it's
it's
just
not
cool,
and
I
know
maybe
it's
just
from
most
of
the
time,
a
place
of
confusion.
You
know
they're
just
not
used
to
seeing
women
in
the
field.
So
it's
like
a
sort
of
a
knee-jerk
reaction,
but
it
doesn't
help
us
because
you
know
it
makes
us
kind
of
feel
bad
like.
A
Oh
now,
I'm
questioning
myself
do.
I
even
belong
here.
So
I
think
you
know
people
within
a
community
as
long
as
they
just
don't
make
any
assumptions
about
anyone
until
you
know,
maybe
if
they
ask
a
question
assume
then
from
their
question
I
guess
yeah,
that's
one
of
my
biggest
pet
peeves
is
when
they
just
launch
into
a
description
of
what
something
is
without,
like
you
said
asking
because
they
just
assume
they
need
to
explain
this
to
you
without
even
giving
you
the
benefit
of
the
doubt
that
you
actually
understand
what
you're
working
on.
A
But
for
me,
one
of
the
issues
is
when
I
will
ask
a
question
or
if
someone
else
asks
a
question,
that
they
might
be
female
or
any
sort
of
minority,
and
someone
is
asking
that
doesn't
make
sense.
That's
not
true,
and
then
another
someone
in
the
field,
who's
respected
or
looks
more
like
them
will
come
and
say
no,
that's
right,
and
I
have
that
experience
as
well
and
suddenly
they
fully
understand
it.
A
C
B
It's
not
like
an
intentional
thing:
it's
maybe
like
their
subconscious
like,
oh
maybe
she
doesn't
understand,
and
I
should
come
in
here
and
sit
and
explain
it
so
they
get
it
like.
Would
you
explain
that
to
your
male
counterpart
in
that
manner?
Or
would
you
say
it
you
know
as
a
matter
of
factly
like
you
know
to
him,
as
you
would
to
me.
A
I
think
it
gets
better
over
time
too.
I've
gotten
a
little
more
comfortable
with
asking
questions
and
I've
kind
of
paired
it
with
like
making
fun
of
myself
a
little
bit
like
I'll.
Ask
a
question
I'm
like
I
know
this
is
maybe
not
the
best
question
and
it's
gonna
make
me
look
dumb,
but
you
know
what
I'm
struggling
with
it
right
now.
We've
all
been
here.
So,
let's
just
let's
figure
it
out.
B
A
C
A
B
Kind
of
reminds
me,
like
code
review
behavior.
I
know
most
projects
have
community
guidelines
and
look
up
suggestions
on
how
to
give
a
code
review,
but
I've
had
experiences
before
and
I've
had
I've
known
other
people
to
have
women
to
have
this
experience
before
where
they
would
get
a
code
review
comment,
and
it
just
kind
of
I
don't
know
the
tone
kind
of
made
them
feel
bad
like
you
should
know
this,
it
didn't
work
verbatim
say
you
should
know
this,
but
it
came
off
as
you
should
know
this.
Why
are
you
doing
this?
B
A
A
Could
you
help
me
explain
why
you
did
this
more
or
what's
the
logic
behind
this,
because
that
really
gives
them
an
opportunity
to
show
you
what
their
headspace
is
like
and
you're,
not
putting
them
down
you're
just
gathering
more
information,
so
I
I
think
again
just
changing
the
perspective
like
you
were
saying,
and
the
phrasing
and
the
tone-
and
it
all
comes
together
to
be
a
more
welcoming
environment.
In
that
case,.
B
Yeah
personally,
I
like
to
say
we
in
my
code
review
comments
like
if
I
see
something
that
needs
to
be
changed.
Maybe
we
should
try
this
and
then
I'll
provide,
maybe
like
an
example
or
a
linked
documentation,
or
something
like
that
to
make
it
more
of
a
partnership
versus
a
you
made.
A
mistake
fix
this.
This
is
wrong,
like
we
just
makes
a
little
more
gentle.
A
B
There
are
those
who
have
a
personality
where
they,
you
know,
naturally
take
charge
and
lead
within
the
call,
and
and
that's
that's
how
they
would
operate
in
person,
and
sometimes
it
could
be
a
little
overpowering
within
meetings,
because
they
may
forget
to
pause
between
comments.
So
one
trick
that
I
like
I'm,
not
one
of
those
people.
A
Yeah
it's
hard
to
read
body
language
over
a
webex.
You
know
like
if
you're
all
sitting
at
a
table.
If
you
know,
if
I'm
like
want
to
say
something,
I
could
just
go
like
I'm
going
to
put
my
finger
up
or
something
like
that's
a
really
good
point
and
then
just
take
it
away,
but
you
it's
kind
of
hard
to
do
that
on
a
web
x
like
so
I
don't
know,
I
think
you
know,
as
people
people
who
are
speaking
it's
kind
of
on
them
to
make
the
change
in
this
situation
I
mean.
A
A
I
think
it's
almost
been
giving
me
more
practice
like
where
I
have
to
talk
to
my
team
virtually
now.
That's
how
I
would
normally
communicate
with
an
open
source
community,
because
everyone
is
so
widespread
in
different
time
zones,
so
I
almost
feel
more
practiced
and
ready
to
jump
into
different
communities
because
we've
been
doing
it
in
our
everyday
life
now
so
I've
I've
been
thinking
of
it
as
an
opportunity
to
gain
more
insight
in
how
I
can
communicate
better
with
outside
communities,
because
I'm
having
to
do
it
in
my
natural
everyday
working
community.
A
B
Really
like
what
you
said,
brittany,
it
really
resonates
with
me.
I
feel
like
now
that
we
are
working
from
home.
We've
gone
digital.
We
really
have
to
be
intentional
about
our
communication.
There's
you
can't
just
assume
something's
gonna
happen.
You
can't
assume
somebody's
gonna
understand
something
you
need
to
clear.
Ask
clarifying
questions
summarize
at
the
end
of
the
call,
maybe
rephrase
somebody's
question
to
make
sure
you
get.
You
understood
what
was
being
asked
before
you
answer
it.
B
A
Yeah,
I
just
feel
like
it's
strange,
no
go
ahead,
it's
gonna
say
I
feel
strange,
just
like
sitting
in
front
of
my
laptop
like
this
all
day
like
like
I
want
to
like
be
around
people
like
in
person.
It's
just
so
much
more.
It's
a
little
draining,
you
know
being
on
webex
calls
all
day,
and
I
don't
know
what
it
is
exactly,
but
you
know
it.
It
does
revamp
me
a
little
bit
when
I
see
somebody's
dog
in
the
background
or
chat
or.
B
Yeah,
you
know
cameras
on
too
they're,
it's
okay,
not
to
be
camera
ready,
five
times
out
of
ten
and
that
camera
ready
morning.
Meetings
before
I
had
my
coffee,
definitely
not
camera
already,
but
seeing
a
face
adding
the
face
to
a
voice,
especially
when
you're
on
larger
calls
with
other
community
members.
B
It
just
adds
that
little
bit
of
a
personal
touch
that
keeps
you
connected
to
the
call
personally,
if
I'm
in
a
meeting
with
10
other
people,
nobody
has
their
cameras
on
kind
of,
like
I
kind
of
lose
focus
a
little
bit
and
I
kind
of
don't
feel
as
connected
to
the
conversation.
But
if
everyone
has
their
cameras
on,
I
could
see
your
facial
expressions.
I
could
see
your
reactions
like
if
I
say
something
and
you
go
then
I
know-
maybe
I
need
to
you
know,
throttle
back
and
revisit
something
so
cameras
on
sometimes.
A
You
mentioned
seeing
people
and
establishing
those
connections
and
like
keeping
you
engaged
it
brings
me
to
when
I
was
joining
an
open
source
community.
I
didn't
know
who
was
in
the
community.
I
have
seen
some
names
on
emails,
but
that
was
it,
so
it
was
kind
of
hard
to
actually
throw
myself
into
it.
A
When
I
didn't
feel
a
connection
with
anyone-
and
I
thought
what
are
people
going
to
see
when
they
see
my
name
so
I
went
to
you
know
my
github
profile
and
it
just
had
my
name
and
so
I'm
thinking,
okay,
I
should
put
a
bio
or
a
blurb
here.
Some
pictures
that
way
people
know
you
know
this
is
who
is
brittany
when
I
see
that
name
coming
through
the
community,
and
so
I
started
going
through
and
looking
up
different
people.
A
B
A
Yeah
absolutely
like
I
mean
I,
I
remember
both
of
y'all's
animals.
Now,
like
your
dog
and
your
cat
over
here,
I
love
that
you
know
just
seeing
somebody's
name
in
an
email.
I
am
not
going
to
remember
anything
you
know
about
like
whatever,
but
you
know
just
actually
having
that
human
element,
the
human
connection
on
calls.
I
love
that
idea.
B
Yeah
we're
all
humans,
you
know
no
matter
how
digital
we
get
or
how
you
know
virtually
disconnected.
We
are,
we
still
crave
personal
interactions
and
personal
connections.
I
feel
like
teams
are
more
cohesive
with
those
personal
connections,
like
you
said,
be
a
garden
or
a
pet,
or
you
know
right
now.
You
guys
are
in
my
home,
I'm
in
your
home
how
personal,
how
much
more
personal
can
we
get?
B
If
you
send
me
an
email
versus
somebody,
I
don't
have
a
face
to
the
name
to
I'm
probably
going
to
reply
to
your
email.
First,
I
mean
depending
on
what
the
email
is
about,
but
you
know
personal
connections
are
really
important.
We
as
humans
will
probably
go
the
extra
mile
if
we
feel
connected
to
somebody.
A
A
So
I
suggested,
let's
do
it
every
quarter
and
at
first
I
I
didn't
get
a
lot
of
everyone
speaking
up,
but
and
I
was
starting
to
worry.
Okay,
maybe
they
don't
like
this.
It's
getting
annoying
and
I
decided
to
ask
for
a
poll
and
it
was
actually
really
successful,
they're
like
no.
We
want
to
keep
doing
this.
A
It's
been
working
well
for
us
and
we
like
having
that
time
to
talk
to
everyone,
so
I
had
thought
it
in
my
head
that
I
was
annoying
them
with
this
new
suggestion,
but
it
was
actually
something
that
was
really
positive,
so
just
break
out
of
your
comfort
zone.
A
little
bit
don't
feel
like
this
is
something
I
want
to
do.
They
won't
do
it.
You
should
just
really
try
it
and
it
could
be
worth
it.
B
Retrospectives
are
real,
like
that's
a
relationship,
building,
trust
building
exercise,
if
you
think
about
it,
because
everybody
is
kind
of
making
themselves
vulnerable
by
expressing
you
know
what
went
well,
what
didn't
go
well
what
they
would
like
to
change
and
it
does
take
a
little
bit
of
courage
to
bring
it
up,
especially
when
you
are
newer
on
a
project
or
you
know
not
too
familiar
with
with
processes,
but
retros
are
very,
very
important
on
my
team.
We
do
this
really
neat
thing.
B
We
have
retros
every
two
weeks
by
the
way
we
have
a
lot
of
videos,
but
that's
really
neat
thing
where
our
lead
will
have
these
little
emojis
on
the
screen
and
you
drag
a
smiley
face
or
like
a
meh
face
or
like
a
stabby
face,
and
so
we
start
the
retro
with
putting
those
emojis
there
to
say
how
each
of
us
felt
anonymously
about
our
sprint
and
then,
if
we
have
all
happy's,
we
know
we
had
a
good
sprint.
We
have
a
couple
mez
like.
B
Maybe
something
needs
to
be
revisited
and
stabby's
whoa
something
went
wrong.
We
need
changes
absolutely
and
just
kind
of
seeing
those
it's
like
a
temperature
check
almost
and
we
could
see
how
everybody
felt
and
it
kind
of
opens
up
that
conversation
where
everybody
can
feel
comfortable
in
in
giving
suggestions
or
giving
feedback.
A
A
We
have
here
at
ibm
like
a
tj
bot,
where
you
put
a
raspberry
pi
in
this
little.
You
can
3d
print
it
or
put
it
make
it
out
of
cardboard.
It's
just
a
little
robot
that
like
moves
his
arm
and
he
can
has
a
little
light
and
he
could
do
stuff.
I
really
would
like
to
see
a
3d
printed
version
of
the
tj
doggie,
so
there's
like
a
little
dog
version.
B
B
You
know
high
schools,
inner
city,
high
schools,
with
with
tons
of
kids,
who
have
the
potential
who
haven't
necessarily
been
given
the
opportunity,
because
of
you
know,
maybe
they
can't
get
to
the
tech
computer
summer
camp.
Maybe
they
don't
have
money
to
go
to
after-school
tutoring
or
maybe
they
don't
have
wi-fi
at
home,
but
yeah.
I
think
that
would
be
my
legacy.
A
A
We
invite
them
to
see
our
campus
and
to
follow
that
path
and
to
actually
see
some
of
those
girls
that
I've
worked
with
at
the
girl
scout
camps
and
the
local
schools
actually
come
and
join
and
work
for
us
at
ibm.
I
would
love
to
still
be
working
at
ibm
and
see
them
join
in
and
maybe
have
a
mentor
program
with
them.
I
think
that
would
be
so
awesome
to
have
him
come
full
circle.
B
Hi
everybody,
I
hope,
can
you
hear
me
as
my
mic
on?
I
hope
you
guys
enjoyed
our
ted
talk.
It
was
really
fun
putting
that
together
we
got
to
know
each
other
a
lot
and
talk
about
our
different
experiences
and
it
was
super
fun.
So
we
have
a
few
minutes
now
we'd
like
to
open
up
the
floor
for
any
q,
a
if
you
have
questions
you
can
type
it
in
the
chat
or
feel
free
to
you
know
ping
us
individually.
B
So
I
know
me
personally,
I
got
started
with
development
camp
and
after
my
boot
camp
I
felt
really
insecure
about
my
skills.
I
was
like.
I
don't
know
where
to
go,
what
to
do
and
october
rolled
around
and
there
was
this
event
called
hacktoberfest
which,
basically,
if
you
haven't
heard
about
it,
it
is
this
event
that
encourages
everyone
to
contribute
to
open
source
and
several
projects
throughout
github
will
have
a
hacktoberfest
tag
associated
with
some
of
their
issues.
B
B
Changes
that
I
could
make,
and
my
very
first
open
source
contribution
was
spanish
translations
on
an
app
called
code
combat
which
teaches
kids
how
to
code,
and
it
was
super
exciting
when
my
pull
request
was
finally
merged,
and
I
saw
my
name
there
as
a
contributor-
and
I
was
like.
Oh
I
can
code,
I'm
a
contributor.
I
am
a
developer,
I'm
an
open
source
person,
so
yeah
hacktoberfest
is
one
way
to
start.
A
I'm
really
obsessed
with
this.
I
remember
when
you
first
told
us
about
it
that
you
did
the
translations.
I
would
have
never
thought
of
that.
Like
I'm
always
thinking
like
all
right,
I
need
to
create
a
button
for
some
kind
of
application
or
you
know
for
me.
My
first
thing
was
just
like
updating
the
documentation
but
doing
translations.
That's
kind
of
awesome.
A
Oh,
I
guess
another
good
place
for
people
to
look.
This
is
actually
how
I
got
started
is
internal
internally
to
your
company.
So
here
at
ibm
we
have
a
developer
jump
start
program
for
new
hires
and
it
basically
kind
of
shows
us,
as
you
know,
if
you're
fresh
out
of
college
and
you're,
just
starting
as
a
developer,
you
go
through
all
these
different
events
and
stuff
and
they
just
teach
you
a
lot
of
really
cool
things
and
you
make
a
lot
of
friends.
So
that's
how
I
got
started.
A
They
actually
had
an
open
source
cohort
as
they
called
us
and
they
taught
us
like
here's.
What
open
source
is
here's
how
to
get
started
contributing
and
they
paired
us
up
with
mentors
and
our
mentors
actually
like
helped?
They
literally
like
held
our
hand
and
walked
us
through
the
whole
process,
which
was
really
cool
because
I
was
really
intimidated
by
it.
I
was
like
I
don't.
I
don't
know
what
to
do,
but
he
was
like.
No,
no
look.
It's!
A
B
How
do
we
gauge
where
we're
at,
and
I
think,
when
you
get
started
with
open
source,
a
lot
of
people
want
to
jump
in
there
and
change
the
world
with
their
very
first
commit
and
drop
like
some
extra
large
change
new
feature,
we
don't
have
to
do
that,
like
you,
can
come
in
there
and
start
with
something
really
really
small.
Get
your
toes,
wet
documentation.
Change
is
small.
A
Yeah,
it's
like
the
ultimate
empathy
test,
like
you
have
to
figure
out
like
what
exactly
is
this
other
person
could
be
thinking
you're.
Looking
for
and
that's
a
really
good
point
about
the
tags
too,
you
know
as
a
new
contributor
you
that's
what
you
want
to
go
look
for
the
tags,
but
also
as
people
who
are
established
in
the
communities.
We
need
to
make
sure
that
we're
actually
adding
these
you
know
maybe
simpler
issues.
A
B
But
if
you
hand
over
the
baton
to
somebody
else,
they
might
not
necessarily
hit
the
ground
running
right
away
and
they
might
need
a
little
bit
more
guidance
with
you
know,
patterns
consistency,
issues,
decisions
that
were
made
in
meetings
and
stuff
that
might
have
not
been
documented.
Those
things
should
be
documented,
so
yeah
that
that's
another
little
tidbit
that
could
share
with
mentoring.
B
B
I
don't
know
I
have
a
lot
of
words
sometimes
and
well.
I
guess
you
know
that
yeah
with
having
a
lot
of
words
always
feel
don't
feel
like
your
voice.
Doesn't
matter
your
voice
does
matter
your
questions
do
matter.
If
you
have
a
question,
somebody
else
has
the
same
exact
question:
either
now
or
down
the
line
don't
feel
discouraged
and
every
contribution
is
a
positive
contribution,
whether
it's
learning
personal
learning
for
you
learning
for
the
community,
a
contribution
project,
everything
is
positive
and,
and
you
know
we
want
it.
B
B
Yet
this
is
a
great
opportunity
for
them
to
build
their
resume
high
school
students
who
are
trying
to
build
some
of
their
experience
that
this
is
a
great
way
for
them
to
do
it
as
well,
because
it's
teaching
them
communication,
it's
teaching
them
programming,
engineering,
community,
building,
it's
just
a
really
well-rounded
experience
and
as
far
as
the
younger
grades,
possibly
there
could
be
projects
that
are
appropriate
for
younger
grades
and
that's,
I
think,
that's
an
area.
I'd
love
to
explore.
A
Yeah,
I
know
they
have
tons
of
like
robotics
projects,
for
you
know
like
elementary
or
junior
high
level
students
and
I'm
glad
that
that
you
brought
this
up
because,
as
brittany
mentioned
earlier,
you
know
she's
from
a
rural
area,
and
I
am
too
so
in
these
smaller
schools.
We
typically
don't
have
like
computer
science
or
programming
classes
or
whatever
you
know
back
in
high
school,
so
open
source
is
a
really
good
place.
A
If
you,
if
you
want
to
learn
this
stuff,
but
I
mean
you
know
when
I
was
a
kid
we
had
dial
up.
So
you
couldn't
really
go
on
the
internet
and
watch
videos
to
learn
how
to
do
stuff,
but
nowadays
you
know
and
for
fear
of
aging
myself
here
you
definitely
can
you
could
just
go
and
you
could
kind
of
teach
yourself
how
to
code.
It
doesn't
have
to
be
anything
extravagant,
but
you
know
if
that's
something
that
you're
interested
in
you're
like
yeah.
I
want
to
learn
how
to
do
this.
B
Now
that
you
bring
up
that
you're
from
a
rural
town
that
goes
for
almost
any
town,
sometimes
it's
hard
to
find
a
mentor
in
your
immediate
community.
I
know
when
I
was
in
school
there
weren't
a
lot
of
people
who
looked
like
me,
who
were
going
into
engineering,
and
that
was
very
discouraging
for
me
personally,
like
I
felt
like
I
didn't,
belong
but
being
an
open
source.
Your
world
went
from
like
this.