►
From YouTube: Roadmaps for Open Source Projects - Experience Report - Mark Waite & Oleg Nenashev, CloudBees
Description
Roadmaps for Open Source Projects - Experience Report - Mark Waite & Oleg Nenashev, CloudBees
Speakers: Mark Waite, Oleg Nenashev
As open source projects grow, develop, and evolve, a "roadmap", or shared plan for future improvements can encourage new contributors to join the project and guide the efforts of existing contributors. Oleg and Mark will share the experiences of the Jenkins project as it has developed a roadmap and used the roadmap to improve the project. We'll share the principles that have guided the creation of the roadmap, the challenges we've encountered, the techniques we've used, and some of the successes and failures of the roadmap. We'll review the history of the Jenkins project roadmap from its beginning at FOSDEM 2020 to its current state.
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
Welcome
to
cdcon
2021.
This
is
road
maps
for
open
source
projects
and
experience
report
by
oleg
nanachev
and
mark
waite.
We're
so
grateful
that
you're
here
joined
with
us
and
look
forward
to
questions
and
answers
after
the
presentation
is
complete,
oleg's
unavailable
to
join
me
for
the
recording
portion
of
this.
But
we
look
forward
to
having
him
with
us
while
we're
doing
question
and
answer.
A
What
that
means
is
that,
when
oleg's
involved
with
jenkins
he's
tends
to
work
on
jenkins
core
at
its
cons
at
its
center,
the
very
basis
on
which
all
jenkins
work
happens,
he
makes
sure
that
that
core
is
healthy
and
well
constructed
runs
well.
Oleg
also
works
on
presenting
jenkins
online
meetups.
He
shares
what
he's
learned
shares
his
experience
and
helps
others
in
as
they
learn
how
to
use
jenkins
more
effectively
he's
also
a
key
player
in
the
google
summer
of
code
project
in
jenkins
and
has
been
for
multiple
years.
A
Our
results
in
google
summer
of
code
have
been
nothing
sort
of
delightful
thanks
to
oleg's
work
and
google
summer
of
code
he's
also
a
maintainer
of
the
jenkins
configuration
as
code
plugin
and
a
great
contributor
there
in
helping
to
assure
that
jenkins
installations
can
be
configured
as
code
can
be
cared
for
with
source
code
and
can
be
maintained.
Readily
he's
also.
The
creator
and
primary
maintainer
of
jenkins
file
runner
a
way
to
run
jenkins
as
a
function
in
the
cloud-based
environment.
A
This
talk
is
about
the
jenkins
road
map
and
why
we
think
other
open
source
projects
may
want
to
consider
adopting
road
maps,
how
they
could
use
road
maps
and
what
they
might
do
to
help
them.
We're
going
to
use
our
story
and
our
experiences
as
a
way
to
hope
that
we
will
be
able
to
share
with
you
some
of
the
insights
we've
gained.
A
While
this
presentation
talks
about
jenkins,
it's
not
so
much
that
we
intend
for
it
to
be
about
jenkins,
as
we
want
it
to
be
about
what
we've
learned,
while
working
with
developing
the
jenkins
roadmap
and
refining
and
improving
it.
You
can
find
these
slides
at
this
through
this
qr
code
at
bitly,
cdcon
2021
roadmaps.
A
Now
what
is
a
roadmap?
Well
in
the
jenkins
environment,
a
roadmap
is
a
flexible
planning
vehicle
that
we
use
to
support
strategic
and
long-range
planning.
We
want
to
match
short-term
and
long-term
goals
and
help
them
help
us,
as
the
jenkins
project
evolves.
Other
projects,
I
think,
would
want
something
similar.
They
would
likely
want
to
be
able
to
help
their
developers,
their
users
understand
where
they
are
now
and
where
they
are
going
as
thing
as
time
advances.
A
If
we
look
at
the
interoperability
special
interest
group
in
the
continuous
delivery
foundation,
we
get
one
view
of
a
roadmap.
This
is
a
a
good
view
in
terms
of
they
see
things
that
are
currently
on
their
roadmap
as
more
specific,
more
granular
and
more
detailed
as
they
advance
their
roadmap.
Further
things
that
are
just
near
term
are
a
little
wider
focus
and
have
greater
flexibility
and
things
that
they've
put
into
their
future
bucket
have
a
very
broad
scope,
very
flexible,
that's
one
way
of
representing
a
road
map.
A
A
Likewise,
the
jenkins
roadmap
has
a
presentation
that
shows
us
time
oriented
what
are
the
things
that
are
already
released
and
are
on
the
roadmap
or
what
things
are
in
preview.
Development
has
begun
and
we're
actively
working
with
them.
Now,
how
is
it
going
or
things
that
are
currently
under
development?
A
A
A
Today,
millions
of
developers
and
software
engineers
I've
joined
the
jenkins
community
to
build
great
software.
It's
amazing.
The
different
things
that
have
been
built
with
jenkins
and
that
use
jenkins
part
of
the
jenkins
story
is
how
we
tell
people
and
how
they
tell
us
why
jenkins
is
the
way
for
them
to
do
what
they're
doing
and
their
ins
their
inspire
responses
are
quite.
A
Inspiring,
so
if
we
look
back
at
the
many
years,
we
can
see
presentations
by
kosokay
that
will
highlight
15
years
of
over
15
years
of
software
evolution.
Those
15
years
of
evolution
give
us
a
highlight
of
what
it
is
to
create
a
a
flexible,
extensible
automation,
server
that
can
be
used
worldwide
in
many
many
ways.
A
A
It
is
a
component
that
relies
on
plugins
to
perform
its
major
extensions,
and
there
are
over
a
thousand
seven
hundred
plugins
available
for
jenkins
to
help
get
its
work
done,
there's
a
very
large
community
of
users
and
developers
who
maintain
and
care
for
it.
And
if
you
wish
to
have
commercial
support,
there
are
companies
in
the
around
the
world
that
provide
commercial
support
for
jenkins.
A
Now,
what
is
it
that
has
made
jenkins
successful
and
that
other
projects
might
use
as
a
model
to
decide
how
to
how
to
do
open
source
software
that
becomes
widely
used?
Well,
one
it's
extensible
jenkins
is
designed
was
designed
from
the
very
beginning
to
be
extended
in
ways
that
help
users
its
general
purpose,
rather
than
being
focused
on
a
very
specific
task.
It
allows
many
different
tasks
to
be
performed
in
very
general
ways,
and
it
has
a
vibrant
community
that
encourages
and
invites
contributions
from
others.
A
A
Those
people
who
are
willing
to
help
get
to
define
how
it
evolves
it's
open
to
anyone
either
an
individual
or
a
company
and
maintainers
are
granted
full
freedom
in
their
plugins
to
implement,
as
they
see
fit,
that
freedom
allows
them
the
flexibility
to
move
rapidly
and
to
evolve
capably
now.
What
does
that
mean
in
terms
of
how
jenkins
looks
well
as
an
example?
In
2019,
there
were
67
core
releases
of
jenkins
over
2600
plug-in
releases
from
over
5
000
contributors
in
111
countries.
A
A
A
A
It
may
also
be
daunting
for
new
contributors
to
join
an
initiative,
because
they
may
not
be
aware
that
the
initiative
exists,
or
they
may
not
know
how
to
connect
with
it
or
there
may
be
other
barriers
there.
All
challenges
that
can
get
in
the
way
of
the
continued
growth
and
development
of
a
community.
A
So
what
does
the
jenkins
community's
history
look
like?
Well,
we
started
in
2011
with
open
governance
and
open
governance
meetings
as
a
standard
way
of
operating
in
2015.
Four
years
later,
we
found
that
we
needed
some
more
structure,
so
we
added
the
concept
of
teams
and
of
jenkins
officers
and
sub-projects.
A
That's
where
we
developed
the
infrastructure,
sub
project
and
and
the
release
officer
and
the
security
officer
now
in
jenkins
in
2017,
the
jenkins
enhancement
proposal
process
came
into
being
that
allows
us
to
define
how
we're
going
to
do
major
jenkins
enhancements.
These
could
be
process
related,
they
could
be
feature
related.
They
may
be
compatibility
related
or
platform
related
jenkins
enhancement.
Proposals
have
helped
us
as
we've
refined
and
improved
jenkins.
A
In
2018.
We
added
jenkins
special
interest
groups.
Special
interest
groups
allow
a
group
of
individuals
to
gather
together
on
a
specific
topic.
For
example,
cloud
native
is
one
of
our
special
interest
groups
or
the
documentation
special
interest
group
or
the
user
experience
special
interest
group.
Each
of
those
special
interest
groups
gathers
together
a
group
of
interested
contributors
working
on
a
general
sub-topic
in
2019.
We
implemented
governance
board
elections
and
became
a
member
of
the
continuous
delivery
foundation.
A
A
public
roadmap
was
the
idea
what
happened
was
in
february
of
2020
at
the
contributor
summit.
We
hosted
at
fosdem
in
belgium,
we
began
initial
discussions
of
the
concept
of
a
jenkins
roadmap.
This
is
february
2020.
in
march
of
2020.
The
first
jenkins
enhancement
proposal
was
brought
forward,
jep
14
to
do
a
jenkins
roadmap
and
then,
in
april
the
initial
preview
of
the
jenkins
roadmap
was
published
for
the
next
three
months
april
may
and
june.
We
reviewed
the
roadmap,
we
discussed
it
in
mailing
lists.
A
A
A
A
A
A
Now
the
j
public
roadmap
looks
like
this.
In
its
presentation,
we
see
time
listed
from
left
to
right
things
released
all
the
way
through
to
things
that
are
in
the
distant
future.
We
see
categories
and
topics.
This
presentation
is
focused
on
jenkins
users
so
that
they
know
where
things
are
in
the
roadmap.
It's
focused
on
jenkins
contributors
so
that
they
can
easily
click
an
item
in
the
roadmap
and
go
find
ways
to
contribute
to
that.
It's
focused
on
jenkins,
adopters
and
vendors
so
that
they
know
what's
coming.
A
Now
there
are
initiatives
in
every
area
of
the
project
represented
on
the
roadmap.
For
instance,
various
important
features
are
represented
on
the
roadmap.
How
we
package
or
ship
or
deliver
jenkins
is
on
the
roadmap,
which
tools
we
use
or
how
we
want
to
refine
and
improve.
Those
tools
are
on
the
roadmap.
A
A
Here
you
see
that
on
the
leftmost
column
in
the
production
use,
we've
got
dark
theme
and
ui
theme
management
there.
Those
are
ui
things
and
user
experience,
things,
site,
search,
again,
user
experience
and
modernizing
the
mirror
infrastructure,
because
that
is
very
much
about
the
experience
that
a
user
has
as
we
advance
through
time.
We
see
other
things
like
documentation,
improvements
that
are
again
part
of
the
user
experience
terminology,
cleanup
part
of
the
user,
experience,
accessibility,
all
components
of
user
experience
and
how
its
roadmap
is
fitting
to
meet
the
needs
of
users.
A
Cloud
platforms
likewise
have
a
similar
evolution.
Kubernetes
is
a
significant
portion
of
where
our
cloud
platform
strategy
is
going.
It
highlights
how
we
want
to
be
readily
usable
in
a
kubernetes
environment,
meetups,
documentation,
specific
plugins
and
storage,
build
results.
All
part
of
the
evolution,
pluggable
storage
just
makes
sense
in
cloud
native
environments.
In
addition,
the
jenkins
file
runner
is
part
of
our
our
cloud
platforms
roadmap.
All
part
of
the
evolution
shown
by
the
roadmap.
A
Now
the
jenkins
roadmap
is
not
just
about
features.
It
is
used
by
the
community
to
track
much
more
than
features,
and
other
projects
probably
should
consider
the
same
thing
that
a
road
map
is
more
about
the
people
we're
trying
to
serve
than
it
is
about
the
items
on
the
map.
Community
initiatives
are
on
our
roadmap.
For
instance,
how
do
we
onboard
new
contributors?
How
do
we
reach
out
to
underserved
communities
or
to
underserved
teams
and
individuals
which
tools
should
we
use?
A
A
Read-Only
configuration
is
code.
Now
we
not
only
have
the
ability
to
configure
jenkins
with
code,
but
we
can
actually
define
the
permissions
in
jenkins
such
that
the
configuration
can
only
be
changed
through
code
that
users
are
can
be
taken
from
them.
The
ability
to
reconfigure
their
jenkins
ui,
so
they
have
to
do
it
as
code.
In
addition,
the
ui
management
now
supports
the
dark
theme
and
other
user
selectable
themes.
A
A
It's
used
now
uses
https
to
access
those
mirrors
instead
of
http,
and
it
provides
status
reports
for
users
and
for
administrators
to
understand
how
the
mirror
network
is
operating.
There
have
been
some
challenges
and
you
should
be
aware
that
the
challenges
are
predictable
and
likely
to
happen
to
any
project
that
uses
a
road
mapping
technique.
A
A
Now
we've
had
cases
where
an
item
was
added
to
the
roadmap
and
then
the
progress
just
seemed
to
stall
it.
It
paused
either
because
it
was
much
bigger
than
expected,
or
it
was
much
more
difficult
to
coordinate
many
different
possible
reasons.
People
may
have
needed
to
leave
or
temporarily
suspend
their
work.
A
Some
of
our
solutions
have
been
to
make
things
more
publicly
visible
about
this.
Progress
highlight
hey.
This
is
what's
happening
so
that
we
can
encourage
others
to
join
and
to
help
out.
The
initial
instigators
of
a
roadmap
item
do
not
necessarily
need
to
be
the
ones
who
complete
it.
We've
also
found
that
it
helps
significantly
if
we
have
special
interest
groups
leading
those
initiatives
by
having
a
special
intrigue
interest
group
lead
the
initiative.
A
A
A
A
As
an
example.
Here's
a
snapshot
of
infrastructure
and
services
as
the
category
highlighting
that
there
actually
aren't
that
many
items
on
the
jenkins
roadmap
relative
to
infrastructure
and
services
helps
people
see
if
they
just
choose
that
one
thing
relatively
solid,
simpler
item
and
that
guidance,
number
of
items
per
category
filtering
and
categorization
have
been
a
great
help
for
us
in
managing
roadmap
bloat.
A
Now
what
about
off-road
initiatives
that
are
off
the
road
map?
As
an
example,
we
may
have
someone
who
has
a
great
idea
and
they
start
it
well,
we
embrace
that
we
would
love
for
that
to
be
included
in
the
roadmap
when
it
makes
sense
and
to
assure
continuity.
We
tend
to
encourage
those
things
that
came
in
from
off-road
map
to
join
a
special
interest
group
or
a
sub-project,
so
that
if
there
were
any
question
with
regard
to
continuity,
we
could
carry
it
forward
in
the
special
interest
group
or
the
subproject.
A
A
A
It's
just
an
indicator
of
where
the
next
things
are
that
we're
working
on
and
what
things
we
are
currently
working
on
intentionally,
not
including
dates,
has
been
very
helpful
for
us,
because
we
don't
have
to
have
date-based
disputes
and
discussions.
We
talk
about
what
things
are
being
done
and
which
things
are
not
being
done
now
roadmaps
do
not
make
any
promises.
A
We
don't
promise
this
that
or
the
other
thing
it's
just
a
view
to
what
is
coming
or
may
be
coming
and
as
the
final
most
crucial
point,
the
road
map
is
not
the
travelers.
The
people
who
are
involved
in
the
project
are
the
travelers
they're,
the
ones
that
matter
the
users,
the
contributors,
the
involved,
the
participating.
A
Now
we'd
like
to
remind
you
that
it's
a
great
time
to
contribute
it's
a
great
time
to
contribute
to
open
source.
It's
a
great
time
to
contribute
to
projects
like
jenkins
jenkins
has
ways
to
contribute,
including
you
could
join
us
to
present
at
meetups.
You
could
share
implementations
of
code.
There
are
lots
of
plugins
and
many
components
that
you
could
help.
A
You
could
assist.
Other
users
help
them
get
the
most
out
of
jenkins
in
their
experience
by
answering
their
questions
or
guiding
their
efforts.
If
you're
a
native
language
speaker
in
a
non-english
language,
you
could
help
by
translating
jenkins
into
other
languages.
You
could
assist
us
by
testing
jenkins,
either
interactively
or
with
automation.
We
love
automated
tests.
We
love
interactive
tests,
we're
grateful
to
have
testers
and
look
forward
to
their
contribution.
A
You
can
help
us
document
jenkins,
make
it
easier
for
others
to
get
started
using
jenkins
if
you're
a
web
designer
or
interested
in
user
experience,
you
could
help
help
us
by
improving
the
design
and
the
ui
that
jenkins
runs.
You
could
also
help
us
review
code.
We
look
forward
to
all
those
contributions
and
would
be
very
grateful
to
have
them.
Please
share
your
questions
online.
We
look
forward
to
those
questions
very
grateful
that
you've
joined
us
today
at
cdcon
2021
thanks
very,
very
much.
B
Okay,
I
think
we
can
unmute
ourselves
right.
So
thanks
a
lot
to
everyone
who
participated
in
the
talk
and
for
so
many
questions
we
are
happy
to
continue.
There
are
many
community
channels
you
can
join
and
yeah
thanks
a
lot
to
mark
for
doing
the
entire
recording
because
yeah
it
wasn't
completely
unavailable.
Last
week
and
yeah
you
know
last
week
was
a
bit
beyond
the
deadline.
So
thanks
a
lot
so
much
for
doing
call
vertical
thing.
C
B
Yeah,
so
I
hope
you
answered
all
questions.
If
not
again,
you
have
a
chat.
Well
mainly,
I
suggest
that
now,
if
you
have
a
question,
you
would
rather
join
our
discourse
channel
community.jenkins.org
and
we
will
do
our
best
to
create
a
threat
there,
just
after
this
call,
so
that
everyone
is
welcome
to
join
and
ask
about
roadmaps,
etc
and
yeah
for
other
communities
who
are
interested
to
learn
from
us.
Just
join
one
of
our
governance
meetings
or
engage
in
the
mail
increase
yeah.
B
We
know
that
tracy
and
other
artists
team
members,
so
they
reached
out
to
us
to
share
some
experiences
and
to
learn
from
us
and
yeah.
We
will
talk
about
that
and
yeah.
There
is
an
interesting
question
from
tracy.
Is
there
a
secret
to
keeping
contributors
engaged
yeah?
The
secret
is
easy,
just
carrying
water
and
chopping
food.
So
it's
not
a
single
activity.
It's
a
lot
of
various
activities
here
and
there
like
maintaining
social
media,
maintaining
communication
channels
engaging
with
contributors,
encouraging
them
to
present.