►
From YouTube: My Open Source Journey - Why don't you come along?
Description
Meet Ewelina Wilkosz, Jenkins Governance Board Member and open source contributor. Ewelina shares her journey on how she become a developer, open source contributor and now a member of the distinguished Jenkins Board. Ewalina has a gentle message for other women who are considering a career in this area and how important an open source community can be towards building that career.
A
Okay,
everybody
thank
you
for
attending
this
september,
2021
cdf
meetup.
I
am
tracy
reagan.
The
host
of
this
madness.
I
have
been
for
a
little
over
a
year
now
and
we've
had
some
really
amazing
talks
over
the
course
of
the
last
two
years,
and
this
one
is
in
particular
of
interest
to
me
because
of
my
continued
effort
to
bring
more
women
into
the
open
source
community,
but
before
we
jump
into
that,
let
me
just
give
you
a
few
tips
here.
I
will
shortly
I
am
going
to
unmute
everyone.
A
So
if
you
ask
questions
during
this
presentation,
you
can
so
please
be
considered
and
mute
yourself
once
I
unmute
you
so
that
if
there's
no
background
noise
and
if
there
is
then
I
will
mute
you
if
I
can
figure
out
where
the
background
noise
is
coming
from,
but
that
would
be
super
helpful
and
just
a
discussion
about
what's
coming
up
for
the
cdf
online
meetups,
we
will
not
be
doing
one
in
october
october
is
a
busy
month.
We
have
the
end
of
the
coming
towards
the
end
of
this
month.
A
We
have
devops
world
and
then,
following
that,
we
we'll
go
right
into
the
october
season.
There's
kubecon
coming
up,
so
there's
quite
a
there's,
a
kind
of
a
lot
of
stuff
happening
over
the
course
of
the
next
six
weeks.
So
we're
not
going
to
compete
with
that,
but
we
will
be
doing
a
something
probably
just
before
thanksgiving.
A
I
am
looking
at
bringing
on
a
woman
by
the
name
of
roslyn
radcliffe,
who
is
a
distinguished
engineer
at
ibm
and
has
been
recently
published
on
testing
in
the
cd
pipeline
and
if
any
of
you
have
ever
spoken
to
me,
you
know
that
I
keep
harping
on
the
fact
that
we
need
to
have
more
testing
information
and
testing
thought
leadership
when
it
comes
to
devops
and
the
cd
pipeline.
So
I'm
hoping
that
we
can
get
her
to
speak
and
that
will
probably
be
sometime
in
the
middle
of
november.
A
A
I
think
devops
world
is
a
free
virtual
event
and
I
believe
kubecon
has
a
virtual
component
to
it,
so
you'll
be
able
to
attend
most
of
the
sessions.
I
believe
I
think
the
thing
you'll
miss
out
on
is
probably
walking
through
the
the
show
floor
and
maybe
someday
we'll
have
little
robots
when
we
get
to
walk
through
the
show
floor,
which
would
be
really
cool.
A
So
on
that
I
am
going
to
introduce
evelina
vilcott
she
okay.
I
found
her
because
I
saw
her
name
pop
up
on
a
governance
board
for
jenkins
and
of
course
I
got
very
excited
because
there
was
a
woman's
name
for
being
on
the
governance
board
for
the
jenkins,
open
source
community
and,
if
you've
ever
looked
at
the
jenkins
community,
you'll
see
that
women
are
probably
underrepresented.
A
So
I
was
super
proud
that
the
jenkins
community
introduced
her
as
a
governance
board
member
and
we
chatted
a
bit,
and
I
asked
her
to
tell
her
story
about
how
she
got
involved
in
open
source.
Now
for
the
ladies
out
there
we
are
not
represented
well
in
open
source.
We
need
to
do
better,
and
I
understand
why
that's
the
case.
A
A
So
those
of
you
who
are
out
there,
who
can
I
encourage
you
to
do
so,
and
I
think
that
evelina's
presentation
might
help
do
that.
So
in
that
I
want
to
give
a
a
warm
welcome
and
applause
for
evelina,
even
though
we're
remote,
it's
kind
of
weird
to
say
and
applause,
but
let's
celebrate
her
and
evelina.
It's
all
yours
thank.
B
B
Yes,
I
want
to
share
my
open
source
journey
with
you,
but
as
as
tracy
mentioned,
I'm
a
woman
and
certain
aspects
of
the
talk
will
will
touch
upon
that
subject.
But
but
of
course
there
are,
there
are
big
parts
of
of
becoming
involved
with
open
source
that
that,
I
think,
will
be
of
interest
to
to
every
one
of
you
so
now
I
just
have
to
make
my
presentation
work.
Who
am
I?
My
name
is
evelina
vilcoche
and
I
work
as
a
consultant
at
verify.
B
I'm
based
in
sweden
and
in
my
consultant
work.
I
specialize
in
continuous
integration,
continuous
delivery
and
a
lot
of
things
that
are
happening
around
it
and
at
the
end
of
the
day
I
I
just.
I
just
wish
that
the
developers
I
work
with
are
just
are
liking
their
work
a
little
bit
more
or
maybe
at
least
they
don't
hate
it
more
than
they
did
before.
After
what
I
did
for
them.
I
have
experience
from
before
as
a
web
developer.
B
B
That
interesting,
and
probably
everyone
has
a
very
similar
experience,
and
then
I
realized
that
this
is
the
way
I
I
often
think
about
myself,
maybe
now
a
little
bit
less,
because
I
met
great
people
at
work
or
in
the
community,
so
I
feel
a
little
bit
more
confident
about
myself,
but
it's
still,
you
know
around
this.
This
thought
that
you
know
it's.
B
It's
nothing
special,
but
tracy
asked
for
a
meeting
and
and
and
we
talked-
and
I
actually
shared
part
of
the
journey
with
her,
and
then
I
realized
that
yeah
I
mean
this
is
this
is
not
that
bad
I
enjoy
talking
about
it
at
least
so
maybe
some
of
you
will
enjoy
listening
and
yes,
that's.
Why
we're
here
so
before
I
can
talk
about
how
I
ended
up
being
involved
with
open
source.
B
So
I
do
honestly
believe
that
this
bringing
women
to
I.t
becomes
in
a
kindergarten
or
somewhere,
not
where
the
women
are
are
at
the
university
and
you're
just
trying
to
drag
them
to
the
companies.
I
I
think,
that's
an
important
work
too,
but
I
think
it
should
start
much
much
earlier,
so
my
parents
were
very
focused
on
making
sure
that
I
think
for
myself
and
I
make
decisions
for
myself
based
on
something
that
makes
sense,
not
because
sylvia
is
doing
that.
That
was
never
a
reason
good
enough
for
them
to.
B
Let
me
do
something
and
it's
not
like
they
didn't.
Let
me
do
anything
but
but
it
it
was
important
for
them
to
to
to
make
sure
that
I
understand
that
I
have
to
think
before.
I
do
certain
things
and
no
one
can
tell
me
what
I
can
and
cannot
do
or
what
I'm
capable
of
and
and
that
stuck
and-
and
I
think
it
helped
me
be
a
little
bit
more
brave
and
think
a
little
bit
more.
Every
time
before
I
make
an
important
decision,
what
I
feel
about
it.
B
She
yeah,
maybe
the
fact
she
was
a
woman,
helped
her
to
have
this
compassion
and
focus
on
on
making
sure
that
this
girl
will
will
will
work
hard
because
because,
apparently,
she
she's
capable
of
doing
a
little
bit
better,
but
she
she
did
much
more
than
that.
She
showed
interest
and
and
spent
a
lot
of
energy
on
everyone.
It's
not
like.
B
There
were
some
people,
professors
or
students
that
were
not
even
allowing
me
to
prove
anything.
They
were
just
like.
I
don't
talk
with
girls
about
math,
so
so
that
feels
so
silly.
I
was
just
like
okay,
I'm
gonna
forget
about
you,
but
but
the
majority
of
the
people
weren't
like
that.
Obviously,
and
they
were
really
really
great
professors
that
were
very
encouraging
and
I'm
I'm
I'm
a
carrot.
Kind
of
person
stick
doesn't
work
on
me,
but
if
someone
someone
behaves
like
they
believe,
I'm
gonna
do
best.
B
B
I
don't
really
know
how
it
exactly
looks
in
other
countries,
but
I
know
in
poland,
and
probably
countries
around
poland
or
or
east
from
poland.
It's
not
that
easy
to
make
a
living,
and
if
you
want
to
be
an
independent
person,
doesn't
matter
if
you're,
a
man
or
a
woman,
you
have
to
work
in
I.t
or
it
is
one
of
the
few
areas
where
you
can
work
and
actually
earn
decent
money.
So
so
there
it
is.
The
choice
was
quite
simple:
I
felt
good
at
technical
stuff.
B
I
think
it
was
2017
when
I
moved
out
of
krakow
to
join
a
consulting
scandinavian,
consulting
company
called
pragma
and
I
didn't
really
know
much
about
them,
except
the
fact
that
they
seem
to
be
doing
exactly
what
I
was
doing
the
last
time
I
was
happy
at
my
previous
employer
and
I'm
like.
Yes,
I
want
to
work
for
these
guys
and
then
I
got
to
meet
the
founders
and
my
potential
future
colleagues
and
they
seemed
so
happy
at
work.
B
B
So
I
I
got
a
little
bit
of
time
to
make
myself
familiar
with
this
jenkins
code
solution.
They
they
had
and
off.
I
went
to
the
customer
and
the
jenkins
instance
they
had
was
giving
me
heart
attack
every
day,
almost
because
it
was
so
old
and
so
shaky
and
unstable.
I
was
really
really
worried
to
to.
You,
know,
touch
anything,
and
the
first
step
was
to
actually
bring
this
instance
to
a
state
where
they
can.
They
can
build
stuff,
so
just
just
make
it
work.
B
B
I
was
taking
a
screenshot
before
making
a
change,
because
there
is
no
undo
button
in
jenkins,
or
there
was
nothing
like
you
know,
preserving
the
configuration
except,
of
course
I
could
save
xml
files,
but
it's
not
the
easiest
file
to
read,
and
I
I
I
I
survived
that
and
the
jenkins
was
working.
We
started
talking
about
introducing
the
solution.
B
I
mentioned
before,
and
then
I
just
fell
in
love
with
the
solution
instantly
because
it
actually
allowed
me
to
skip
the
whole
screenshot
experience
and
just
just
do
stuff,
and
if,
if
things
didn't
work,
I
could
always
revert
to
the
to
the
state
that
I
had
saved
in
the
configuration
files.
So
on
the
result
site,
the
solution
was
perfect.
The
usability
site
was
not
that
great.
B
It
required
jenkins
to
restart
every
time.
You
wanted
to
make
a
change
and
it
was
a
little
quite
time
consuming,
and
it
also
required
me
to
write
a
piece
of
groovy
code
for
every
plugin
I
wanted
to
configure,
and
that
was
fun
because
you
know
I
I
enjoy
troubleshooting
and
I
enjoy
like
solving
those
little
little
issues,
so
it
it
was
interesting
and-
and
as
I
say,
I
had
a
little
bit
of
fun,
but
at
some
point
it
it
becomes
a
little
bit
exhausting.
If
you
have
a
lot
of
plugins.
B
B
So
we
did
want
to
make
this
as
code
solution,
also
something
that
you
know
it's
worth
sharing
and
I
didn't
feel
that
it's
it
well.
It
was
worth
sharing,
but
it
it.
It
wasn't,
maybe
good
enough
that
everyone,
even
people
without
a
software
development
experience,
could
use
because
there's
a
lot
of
jenkins
maintainers
administrators
that
are
really
not
software
developers
and
expecting
them
to
write
a
piece
of
code
figure
out
what
to
write
every
time.
They
want
to
configure
something.
B
Well,
I
guess
some
of
them
wouldn't
like
it,
so
I
started
talking
with
my
colleagues
and
if
we
can
make
it
better,
if
we
can
make
it
work
faster,
if
we
can
skip
the
restart
requirement,
because
when
you
use
jenkins
in
a
traditional
way,
you
don't
have
to
restart
it
every
time
you
want
to
make
a
change
like
change
the
amount
of
executors
or
on
on
a
build
agent,
or
something
like
that.
You
don't
have
to
restart
jenkins
for
that,
so
why
we
have
to
have
this
requirement
in
our
solution.
B
B
Who
were,
I
guess
already
before
thinking
about
a
very
similar
solution,
because
I
have
to
admit
I'm
not
the
person
who
came
up
with
the
idea
that
jenkins
should
be
configurable
as
code.
There
is
plenty
of
people
around
the
world
that
were
hoping
for
a
solution
like
that
or
were
trying
to
prepare
a
solution
like
that
and
again
thanks
to.
As
far
as
I
understand
it,
of
course,
thanks
to
pragma's
involvement
with
open
source,
the
the
communication
channels
between
between
jenkins,
community
and
and
pragma
were
were
open
and
like
well
established.
B
So
it
was
easy
to
to
start
being
involved
with
the
community
in
in
in
a
like
a
very
direct
way.
So
so
that's
how
it
started
really.
I
met.
I
had
a
meeting
with
koskinen
and
nicola
and
some
other
people
probably
had
been
there
too,
but
it
was
a
long
time
ago.
I'm
sorry,
I
don't
remember
all
the
names
we
we
talked
about
what
we
are
working
on
and
what
what
they
are
expecting
from
a
solution
like
that,
I
remember
I
had.
B
I
had
a
little
piece
of
paper
with
the
with
things
that
I
wanna.
I
want
the
new
solution
to
have
that
I
believe
are
important
and
and-
and
I
think
costco
was
the
first
one
talking
about
their
expectations,
and
I
was
just
listening
and
looking
at
this
at
this
paper
in
front
of
me
and
then
I'm
like
okay.
He
speak
talks
about
that
and
that
and
that
it's
like
totally
aligned
with
what
I
want
and
that
felt
so
good.
B
B
We
decided
that
we
want
to
make
the
configuration
as
code
solution
and
we
started
working
nicola,
olegnan,
chef,
metz
nielsen
and
a
few
other
colleagues
from
pragma
very
quickly.
I
think
some
other
people
that
were
jenkins
community
members
contributors
already
or
some
some
completely
new
people
started
started
joining.
B
B
There
was
a
lot
of
work
and
and
and
really
great
software
developers
all
around
the
world
involved
that
that
did
did
some
magic
there
and
I
I
feel
like
I
have
to
say
it,
because
I'm
very
grateful
for
for
for
for
them
for
doing
that
to
them
for
doing
that.
But
but
do
I
I'm
saying
it
also
is
to
highlight
the
fact
that
you
know
you
don't
have
to
be
a
developer,
superstar
or
feel
very
confident
about
your
skills
to
actually
contribute
in
a
significant
way
to
open
source
project.
B
There
are
community
tasks.
There
are
events
where
you
can
talk
there
are,
you
know
like
the
functionality.
You
can
try
to
help
plan
a
lot
of
things
around
creating
the
software
that
are
not
related
to
writing
software.
That
a
lot
of
people
can
do.
I
think
many
projects
suffer
from
documentation
and
contributing
to
documentation
or,
like
some
demos,
is,
is
a
huge
benefit
for
the
users
or
whatever
of
whatever
software
or
project
people
create.
B
B
A
very
small
companies
are
very
big
companies
that
are
using
jenkins
in
very,
very
different
ways,
and
I
I
learned
what
are
some
of
the
pains
and
they
are
facing
and
some
weird
things
they
are
doing
and
and
some
some
crazy
things
they
are
doing,
but
also
yeah.
What
what's?
What's
the
most
difficult?
What's
the
biggest
challenge,
why
would
they
decide
to
move
to
another
software
or
why
would
they
decide
to
stay
with
jenkins?
B
And
I
think
that
that
part
of
my
experience
helped
me
make
my
way
to
jenkins
governance
board,
and
I
was
talking
with
some
of
the
some
of
the
members
after
I
was
nominated
before
like
I
was,
I
was
trying
to
figure
out.
Should
I
should
I
accept?
Should
I
not
and
yeah?
Maybe
at
this
point
it's
it's
also
interesting
to
mention
again
as
a
woman
in
I.t.
I
always
always
have
this
thing
at
the
back
of
my
head.
B
So
there
was
a
lot
of
doubts
like
that
around
in
my
head,
but
but
after
some
consideration
talking
to
oleg
that
helped
me
a
lot
I
I
realized
that
this
is
not
helping
anyone
I'll
just
I'll,
just
try
to
participate
in
the
election,
be
a
candidate
and
and
see
how
it
goes,
and
also
all
like
in
a
very
nice
way
explained
why
he
believes
this.
This
governance
board
would
benefit
from
me
being
part
of
it,
highlighting
this.
B
The
fact
that
I
do
have
a
direct,
a
contact
with
a
lot
of
very
different
jenkins
users,
and
that
made
a
lot
of
sense
and
I
think,
a
lot
of
in
in
a
lot
of
situations
when
I
was
having
doubts,
I
was
just
very
lucky
to
to
have
good
people
around
me.
The
the,
as
I
mentioned
kind
words
from
from
some
or
or
or
just
figuring
out
that
me
and
them
think
this
are
thinking
the
same
way
is
it.
It
was
a
boost.
B
What's
how
this
person
speaks,
because
if
you
don't
know
someone
and
you
you
speak
to
that
person-
and
you
just
read
what
this
person
writes
in
the
mail
on
the
message
board,
jira
issue
guitar
wherever
you
you
project
some
things
you
can.
You
can
imagine
that
this
person
is
very
angry
with
you,
because,
because
that's
what
you
would
write,
if
you
were
angry
and
and
the
person
on
the
other
side
might
be
very
calm
and
kind
and
just
have
a
certain
way
of
communicating
things.
B
So
that
is
challenging
and
also
even
if
you
meet
people
you
know
I
at
the
beginning
was
very
intimidated.
Whenever
I
was
meeting
the
the
those
those
people
that
I
knew
were
involved
with
with
the
community
for
a
long
time
and
and
were
names
that
I
I
knew
so
I
was,
I
was
scared
of
oleg
or
or
I
remember
there
was
a
situation
with
some
security
issue
that
I
mentioned
without
actually
knowing
that
there
is
a
certain
procedure
and
of
course
after
I
I
was
told
that
I
I
did
it
in
the
wrong
way.
B
B
There
is
a
few
things
that
I
I
want
to
share
with
people
that
never
contributed
to
open
source
or
are
just
starting
or
are
figuring
out
out
if
they
really
want
to
do
that,
and
of
course
again,
this
is
my
experience.
This
is
not
you
know,
silver
bullet.
This
is
not
like
only
true
true
facts
that
and
nothing
else
matters.
This
is
how
I
feel-
and
this
is
what
I
learned
so
the
the
way
for
me
to
start
contributing.
B
Now,
if
I
wanted
to
join
totally
different
project,
you
know
find
a
project.
You
know
about
and
figure
out
the
community
around
it
the
way
they
communicate
and
which
tools
they
are
using,
and
I
think
it
helped
for
me
with
with
jenkins
and
jenkins
configuration
as
code,
that
I
was
really
excited
about
the
solution
and
I
really
wanted
to
make
it
better
and,
and
probably
people
have
different
motivators
and
it's
easy
for
some
to
just
jump
anywhere
and
and
do
stuff.
B
It
was
important
for
me
that
I
really
cared
about
the
the
project,
and
so
I
knew
a
little
bit
about
jenkins.
I
knew
what
I
want
from
configuration
is
code
and
and
then
I
got
involved
with
the
community
and
each
community.
I
guess,
have
different
way
of
communicating
and
they
use
different
tools.
It's
it's.
It's
pretty
complicated
with
jenkins
right
now
for
me,
because
I'm
losing
the
track
of
of
what
and
where,
but
I
I
think
we're
we're
trying
to
make
it
clear-
or
maybe
maybe
it's
clear
for
everyone.
B
Maybe
I'm
just
messy
and
the
bottom
line
is
there
are
different
tools
and
if
you
want
to
work
on
a
project,
you
have
to
be
able
to
communicate
with
people
so
check.
If
sometimes
there
is
a
guitar
button
in
the
readme
file
of
the
repository
for
the
project
that
that
you're
interested
in
contributing
to
so
you
can
jump
there
and
just
start
talking
to
people
or
maybe
they
just
use
github
issues.
B
Well,
you
have
to
you
have
to
figure
out
yeah.
Then
you
find
the
source
code
and
you
clone
it
or
4k.
Sometimes
I
was
actually
trying
to
find
a
project
that
has
a
nice
contributor's
guide
and
I
didn't,
but
I'm
sure
there
are
projects
that
have
it
perfectly
were
described.
How
are
you
supposed
to
what's
the
workflow?
B
B
The
project
you
want
to
contribute
to
before
you
make
any
changes,
because
if
you
start
messing
around
and
then
you
try
to
build
it,
then-
and
it
fails-
you
never
know
if
it's
you
or
I
mean
there
are
ways
to
figure
out,
of
course,
but
it's
nice
to
have
a
clean
project.
You
haven't
touched.
It
figure
out
how
to
build
it,
and
I
I
did
find
a
in
few
jenkins
plugins.
B
I
was
trying
to
figure
out
that
there
was
a
very
nice
information
in
the
readme
how
to
build
it
so
first
make
sure
that
your
build
is
in
in
good
shape,
and
you
know
that
it
works
and
then,
when
you
start
playing
so
you
do
stuff
whatever
you
want
to
do,
and
sometimes
it's
it's
only
a
documentation,
update
and,
of
course,
only
is
a
very
bad
word
to
use
here,
because
I
do
think,
as
I
mentioned,
a
lot
of
projects
would
benefit
from
improved
documentation.
So
there
is
nothing
little
about
about
improving
documentation
but
yeah.
B
It
can
be
that
it
can
be
a
change
in
the
code
and
then
most
likely
you
just
submit
the
pr
and
you
you
see
who
picks
it
up
and
how
it
goes
further.
So
it
really
is
simple,
I
think,
and
this
this
this
slide.
Actually
I
don't
know
what
it
was
two
years
ago
when
I
was
presenting
for
the
second
time
at
a
devops
world,
and
maybe
it
was
called
jenkins
worlds.
B
Then
still
I
don't
remember
perfectly
well,
but
anyway
it
wasn't
my
first
time,
but
but
it
was
the
first
time
I
was
presenting
along
and
I
was
I
made
a
little
few
changes
in
the
presentation
and
I
added
a
little
slide
about
how
to
start
contributing
to
open
source,
and
it
was
basically
clone.
It
find
a
way
to
to
to
build
it
and
submit
the
pr
and
for
me
it
was
like
this
is
like
the
most
basic
thing
and
like
no
one
will
really
pay
that
much
attention
to
it.
B
It's
so
easy
to
assume
that
what
you
know
is
obvious,
it's
easy
for
me
again.
I
can't
speak
for
the
rest
of
you,
but
very
often
there
are
things
that
I
didn't
have
didn't
know
how
to
do
had
no
idea,
and
then
I
learned,
and
they
became
those
things
that
are
very
difficult
to
explain
suddenly,
because
they
are
so
basic
and
it's
in
no
way
me
disrespecting
people
who
don't
know
it
doesn't
know
it.
Yet.
B
I
just
I
just
I
just
don't
think
that
you
know
I
did
something
great
because
I
figured
it
out,
so
it
must
be
basic
anyway.
People
are
very,
very
grateful
and-
and
I
got
some
some
kind
words
from
from
attendees
who
said
that
it
was
cool
thing
to
show.
So
so
yes,
here
it
is
a
little
bit
extended
and
there's
a
few
things
that
I
think
you
should
remember
when
you
consider
contributing
to
open
source
when
you're
starting.
B
Yes,
there
are
many
people
that
know
much
more
than
you
do,
but
they
can
probably
still
learn
something
from
you
or
others
will
learn
something
from
you.
So
so,
just
you
know,
don't
start
by
comparing
yourself
with
others.
I
did
and
it
was
scary
and
then
those
people
turned
out
to
be
very
kind
and
very
helpful
and
very
willing
to
share
the
knowledge.
B
B
I
earn
money
when
I'm
at
the
customer
and
I
do
something
for
them,
but
I
do
believe
that
more
and
more
open
source
projects
are
finding
their
way
into
big
or
small
companies
and
well
those
project
projects
have
to
have
to
work,
somehow
be
maintained
somehow,
and
it
becomes
more
and
more
clear
for
for
for
people
who
make
decision
about
money
that
investing
in
open
source,
it's
not
wasting
money
really
so
yeah.
I,
as
I
say
that
was
a
little
bit
shocking
for
me
until
I
understand
how
this
whole
model
works
but
yeah.
B
B
A
Well,
I
would
say
you
are
exactly
on
time.
We
try
to
go
40
minutes
of
discussion
and
then
questions.
I
want
to
say
thank
you.
That
was
a
brilliantly
done
presentation
and
some
of
the
things
that
you
talked
about
really
hit
home
for
me,
and
I
want
to
really
give
the
jenkins
community
kudos
for
fostering
you.
A
Basically
in
the
beginning,
listening
to
you
and
understanding
that
as
an
end
user,
you
have
a
lot
to
input
and
the
cd
foundation
in
particular
right
now
is
really
trying
to
grow
their
end
user
community,
and
I
think
that
your
story
really
defines
why
an
end
user
community
is
important,
and
I
speak
to
people
often
and
try
to
encourage
them
to
join
open
source
communities.
And
I
tell
them
just
as
you
pointed
out.
A
One
of
the
first
ways
to
get
involved
is
to
understand
what
features
you'd
like
to
see
in
the
product
and
have
a
conversation
with
the
community,
and
that
is
the
way
you
begin.
So
thank
you
for
pointing
that
out
and
applaud
to
all
of
the
jenkins
contributors
who
brought
you
up
into
this
world
and
allowed
us
to
have
this
conversation
today,
because
I
think
there's
a
lot
of
women
who
need
to
hear
it.
You
do
have
a
few
questions
and
oleg
and
krosuke.
B
I
actually
haven't
looked
what's
going
on
there
yet,
but
definitely
especially
since
I
I
don't
know,
I
I
feel
this
becoming
a
jenkins
governance
board
member
is,
is,
I
don't
know
it's
something
that
I
appreciate
and
I
want
to
step
up
my
game.
So
yes
definitely
and
then
I
also
there.
There
is
a
lot
of
projects.
There
is
google
google
summer
of
code,
and
I
I
think
there
was
a
lot
of
jenkins
related
projects
happening
around
this.
B
I
know
of
a
another
woman
and
that
I
think
started
with
the
google
summer
of
code.
I
I'm
saying
I
think,
because
I
don't
really
remember
for
for
sure.
I
tried
to
check
that
with
her,
but
I
didn't
manage
to
get
in
touch
with
her,
but
I
think
natasha
stoppa
started
with
the
with
one
of
this.
Those
those
projects
were
where
she
worked
on
the
jenkins
plugin
manager.
That
was
very
much
needed
to
be
solved.
I
was
actually
hoping
I'll
hear
from
her
how
she
got
involved
with
open
source
community,
but
but
yeah.
B
Well,
you
know
what
worked
for
me.
I
had
a
great
employer
that
that
that
empowered
me
and
encouraged
me,
so
I
think
yeah
I
don't
know
I
because
I
I'm
sorry,
I
I
don't
have
an
answer
clear
answer.
I
just
feel
very,
very
lucky
that
I
had
good
people
around,
so
you
know
just
look
who's
around
you
and
try
to
encourage
someone
who's
around
you.
A
Yeah,
that's
sort
of
how
we're
approaching
it.
You
know
the
ortillius
community
really
looks
up
to
the
jenkins
community.
We
try
to
follow
everything
that
the
jenkins
community
has
done,
and
we
have
found
that
in
terms
of
getting
more
women
involved,
it
does
take
us
reaching
out
to
them
doing
more
mentorship
and
sort
of
helping
them
and
really
encouraging
them,
which
is
a
question
that
steve
taylor
had
is.
Did
you
have
a
mentor.
B
I
did
have
the
like
yeah.
I
would
call
him
a
mentor
boo,
my
colleague
that
went
to
the
first
customer
with
me
and
I
was
like
really
looking
up
to
him
and
he
was
involved
in
open
source,
so
he
was
also
very
encouraging,
and
I
I
you
know
impostor
syndrome
is
not
the
not
the
rare
thing
in
id,
especially
the
for
women,
although
I'm
pretty
sure
there
is
a
lot
of
very
confident
women.
So
I'm
not
saying
that
every
woman
suffers
from
that.
B
But
yes,
I
personally
needed
this
carrot,
as
I
mentioned,
and
I
needed
this
this
this
someone
who
will
kind
of
bring
me
up
a
little
bit
and
and
make
me
think,
help
me
think
a
little
bit
better
or
more
more
confident
about
myself
and
and
he's
a
great
guy
he's
he's
a
a
very
skilled
guy
and
it
was.
It
was
nice
to
learn
from
him.
So
I
think
that
did
help
a
lot
that
I
was
not
alone.
A
I
I
think
that
is
the
case
for
anybody
male
or
female,
but
I
think
that
women
in
particular
need
a
little
more
encouragement.
So
I'm
glad
to
hear
that
that
happened
for
you
and
then
oleg
asked
a
follow-up
question
about
what
your
experiences
are.
Connecting
your
customers
as
working
as
a
consulting
firm
and
end
users
to
the
open
source
projects.
Were
you
able
to
recruit.
B
And
then
I
I
I'm
not
the
only
person
that
is
involved
and-
and
there
is
a
lot
of
initiatives
coming
from
them,
but
I
think
the
fact
that
a
few
times
when,
when
we
had
the
issue
with
jenkins,
that
was
pretty
pretty
well
too
difficult
for
me
to
solve.
I
was
just
reaching
out
mailing
list
or
or
something
and
then
the
problems
got
solved.
So
so
I
think
this
is
a
way
for
them
to
understand
that
this.
This
open
source
contribution
is,
is
an
important
thing.
B
So
actually
I
I
think
I
I
get
to
work
on
open
source
projects
on
the
customer
time,
sometimes
because
they
know
that
in
the
end
they
are
the
ones
benefiting
from
it.
But
I
do
in
generally
see
the
trend
of
company's
having
some
kind
of
attempt
into
creating
some
kind
of
community,
and
sometimes
it's
just
a
community
within
the
company.
Sometimes
it's
switching
out
reaching
out
further,
but
the
customer
I
currently
work
with
is
in
general,
pretty
interested
in
in
learning
about
the
yeah.
A
And
this
next
question's
from
henry-
and
this
is
a
meet
up-
if
we
were
all
in
person
in
a
room,
we
would
all
feel
comfortable
with
you
know
making
comments,
and
this
is
not
just
for
evelina
to
answer.
I
think
he
asked
when
starting
to
contribute
to
open
source.
How
do
you
quickly
learn
the
code
base?
B
C
Yeah,
I
mean
I'd
like
to
think
like
one
thing
jenkins
got
going
with
it's
a
very
modularized
code
base,
so
you
know
the
core
which
did
grow
over
time,
but
still
kept
me
really
small
compared
to
the
other
massive
projects,
so
I'd
actually
think
it
helped
new
people
get
into
it
really
easily
compared
to
other.
Similarly,
sized
projects.
D
Well,
I
listen
steve.
I
think
one
of
the
things
is
when
you
look
at
the
code
base
is
like
koski
said,
is
looking
at
how
it's
been
modulized
and
focus
on
just
one
particular
part
that
you
really
understand
and
start
there
and
then
work
your
way
out
and
spread
out
from
there.
I
think,
if
you're
gonna
dive
into
like
you
know,
trying
to
make
changes
to
the
linux
kernel
that
has
to
do
with
kubernetes.
A
And
you
know,
I
thought
it
was
interesting
evelina
when
you
did
your
presentation,
that
everybody
that
you
got
feedback
about,
showing
how
to
do
a
pull
request,
and
I
and
I
appreciate
the
fact
that
the
the
the
comment
on
documentation
and
demos-
I
think
that,
in
terms
of
on
the
ortilla
side,
that's
the
part
we
struggle
with
the
most
and
creating
a
a
contributor
environment.
That
is
easy.
A
B
Them
right
exactly
if
you,
if
you
go
to
the
github
repository
and
you
find
easily
how
to
build
the
project
and
what's
the
what's
the
procedure,
should
I
forge,
should
I
clone?
How
do
I
create
a
pr
if
this
is
easy
to
find,
then
this
project
feels
very
welcoming
to
me
if,
if
it's
not
clear
up
front,
it
feels
like
it's.
You
know
it's
some
kind
of
exclusive
group
that
knows
about
it,
which
is
not
always
the
case
in
most
most
situations.
It's
not,
but
that's
the
impression
I
I
would
get.
A
A
A
Well,
everyone.
Thank
you
so
very
much
for
attending
this,
and
this
was
really
super
helpful
and
I
hope
that
we
can
get
this
out
to
as
many
women
as
possible
so
that
they
can
hear
your
story
because
it's
an
important
one,
and
I
love
the
fact
that
you
said
it
was
scary,
because
I
think
that
is
something
that
every
woman
can
hear,
that
it
can
be
scary
and
it's
okay.
If
it
is
yes,.
A
All
right,
everybody,
we
hope
to
see
you
at
devops,
world
or
kubecon,
and
then
we
will
do
our
next
one
in
again
in
november
hearing
about
testing-
and
I
really
really
would
like
to
have
more
conversations
in
2022
around
the
testing
topic
and
the
cd
pipeline,
because
things
are
changing
with
microservices
and
it's
an
area.
I
think
that
we
really
should
focus
on
on
that.
We
will
sign
off
and
thank
you
again,
evelina
for
a
great
job.