►
Description
Soon we are going to introduce a new public Jenkins roadmap. It will highlight the key initiatives happening in the Jenkins project: new features, documentation, infrastructure, developer tools, and community. It will help Jenkins users, contributors, and vendors to properly plan their work and to contribute to the projects they are interested in.
During this meetup Oleg Nenashev will present the current roadmap draft and initiatives which have been already added by special interest groups, sub-projects, and plugin teams. We will also discuss the public roadmap process and how to add your initiatives to the roadmap.
References:
* Slides: https://bit.ly/jenkins-meetup-roadmap
* Roadmap: https://www.jenkins.io/project/roadmap/
* JEP-14: https://github.com/jenkinsci/jep/tree/master/jep/14
* Meetup page: https://www.meetup.com/Jenkins-online-meetup/events/271768902/
B
So
if
it's
your
first
time
participating
tonight,
Meetup
and
this
moment,
we
hostess
I-
think
it's
community.
We
talk
about
anything
related
to
drinking,
so
it's
user
stories,
he
studies,
various
features
like
in
development,
etc,
etc,
and
if
you're
interested
you're
welcome
to
join
and
you're
welcome
to
participate
at
this
Meetup.
The
main
idea
is
so
that
is
made
up
organized
by
contributors
for
contributors,
so
we
do
not
focus
too
much
on
slides
and
presentations.
Instead
of
that,
we
facilitate
live
discussion.
B
B
So
if
you
haven't
met
me
yet
my
name
is
a
Latino
chef,
I'm
jinx
commentator
and
one
of
Jenkins
governance
board
members
I
work
on
a
various
new
shapes,
including
community
architecture,
changes
and
I
also
maintain
multiple
plugins,
probably
too
many
but
I'm
doing
my
best
to
improve
the
Jing
is
a
system
at
this
Meetup.
Actually,
I
will
be
speaking
of
one
of
the
efforts.
I
was
working
over
the
past
several
months,
its
publishing
his
road
map-
and
it
wasn't
only
me
working
on
that.
B
It
was
a
joint
effort
by
multiple
contributors
to
the
project
in
order
to
provide
better
transparency
of
how
on
Jenkins
evolves
and
today,
I'm
going
to
show
a
preview
of
the
road
map.
So
again,
it's
a
preview,
the
restful
changes,
but
hopefully
we
will
be
able
to
release
it.
Some
so
I
mostly
focus
changes,
contributors,
maintenance
and
advanced
users
who
want
to
understand
where
the
project
goes
and
how
it
evolves
and
what
new
features
to
expect
in
the
future,
and
especially
if
you
can
see
the
contributing
to
the
project.
B
B
Overview
of
the
roll
open
jail-
if
you
have
any
questions
during
the
presentation,
please
use
zoom
Connie
mark-
is
an
event
today.
Mark
will
be
monitoring.
Questions
I
will
be
doing
some
breaks
during
the
presentation,
ask
questions
and
for
the
rest,
we
will
do
Pawnee
at
the
end
of
the
talk
after
they
meet
up.
B
If
you
want
to
discuss
roadmap
or
otherwise,
rod,
modest
discussion
thread
and
the
jenkees
developer
mailing
list,
you
can
find
all
the
information
there
and
the
result
should
read
forum
where
you
can
share
your
feedback
about
this
Meetup
and
also
feedback
about
the
roadmap
and
the
features
you
would
like
to
see
in
the
project.
So
if
you
have
a
few
minutes
to
fill
in
this
feedback
form
after
the
meetup,
it
will
be
much
appreciated.
B
All
the
slides
are
already
available
in
public.
There
is
a
link,
BTS
Jenkins
winter
road
map,
so
you
can
just
go
to
this
link
and
find
all
the
information
day.
Ok,
let's
start
discussion.
I
will
begin
with
a
short
history
dive
and
because
yeah
Jenkins
is
a
quite
old
project.
It
has
been
started
more
than
50
years
ago,
and
there
is
a
lot
of
things
happened
in
the
project
over
time.
I
will
reference
his
blog
post
from
Kassadin,
taking
about
shifting
gears
where
he
referenced
three
main
factors
of
success
of
the
Chinese
project.
B
B
Also,
this
tool
is
general-purpose,
so
basically
you
can
apply
it
to
any
domain
in
the
industry
and
we'll
say
in
your
permission,
whiskey's
and
wasn't
but
not
least,
it's
a
Jenkins
coming
James
community
is
what
streaming
driving
the
project
and
what
helps
it
to
evolve,
and
this
is
a
great
experience
for
me
and
for
I
hope
for
many
other
contributors.
So
what
are
the
main
factors
of
the
Jenkins
come
in
here?
Firstly,
it's
open
governance,
starting
from
Jenkins
renamed
in
2011.
James
project
has
had
open
governance
where
everybody
can
participate.
B
B
Consulting
for
that
you're
welcome
in
the
jenga's
community.
You're
welcome
to
participate
in
any
means,
and
we
try
to
improve
this
experience
at
the
same
time,
James
community.
It
provides
a
lot
of
freedom,
so
if
you
are
making
it
or
plugin
or
another
component,
basically,
you
have
full
power
step.
So
you
know
that
there
are
1700
plugin
in
Jenkins,
but
basically
every
plug
in
every
plugin.
Maintainer
still
is
an
independent
entity
in
the
Jenkins
project
and
they
can
make
decisions
about
evolution
of
their
components,
about
rules,
contributing
guidelines,
etc.
B
So,
while
we
host
these
plugins,
there
is
no
strict
guidelines
and
everything
is
quite
relaxed.
This
has
been
our
approach
in
Jenkins
from
the
very
beginning
and
for
the
record.
I
do
not
think
that
this
approach
needs
to
be
changed
in
principle
because
it
works
radio
world,
so
yeah
I
mentioned
the
700
plugins
and
there
is
a
lot
of
changes
in
Jenkins
over
15
years.
We
have.
B
Well,
basically,
the
biggest
automation
project,
at
least
open
source
project
in
the
world.
There
were
more
than
250,000
installations,
with
only
one
switch
submitter.
One
statistics
and
agendas
project
keeps
going
on
growing,
so
every
year
we
receive
more
and
more
contributors
sample
lustre
yeah.
We
had
moderner
5000
contributors
to
the
project
and
after
15
years
the
community
grows
and
a
lot
of
changes
happened
there.
It's
a
not
usual
to
see
here
that
in
such
old
projects,
but
it's
a
pleasure
to
see
it
in
Jenkins.
B
If
you
want
on
some
comparison
with
other
projects,
for
example,
we
have
a
diagram,
we
share
it
so
SEF
and
to
do
it
since
you
have
projects-
and
you
can
see
that
Jenkins
is
basically
the
second
biggest
project
after
kubernetes
and
kubernetes
is
huge,
but
Jenkins
is
also
huge
and
the
smaller
circles.
There
are
actually
a
pretty
big
projects.
It
is
healthy
and
communities
with
hundreds
of
contributors,
but
Jenkins
is
really
big
and
it
evolves
many
directions.
B
So
yeah,
you
may
have
used
the
drinks
for
years,
but
you
can
see
that
the
evolution
of
the
project-
and
that
is
a
lot
of
new
features
being
introduced
so
just
to
highlight
some
which
have
been
introduced
relatively
recently
in
the
jenga's
project.
Its
pipeline
is
called,
it
doesn't
mean
I,
think
a
pipeline
plug
in
the
Chi
system.
You
can
use
other
tools
like
job
daresay
other
plugins,
but
you
can
define
your
size.
The
pipeline
cess
code.
B
Also
configuration
is
code
which
allows
to
build
the
entire
system
as
code
to
apply
infrastructure
port
and
the
whoops
practices
through
jenkees
management
and
along
this
pipeline
is
called.
Basically,
you
can
manage
your
entire
instances
code.
We
keep
introducing
new
plugins
and
integrations
for
many
tools
how
it
happens.
If
somebody
wants
an
integration,
they
contribute
time,
and
this
happens
again
for
the
most
of
recent
tools.
We
have
to
provide
plugins
from
the
debate.
B
Centers
also
Jenkins
doesn't
stay
as
it
used
to
be
was
in
2008
when
there
was
a
war
file
distributions,
it
provides
modern
packaging,
for
example,
for
docker
for
pollinators
Wilhelm.
Also,
there
is
a
new
project
which
provides
edging
preheated
for
kubernetes,
and
there
is
a
lot
of
other
changes
in
packaging
and
always
how
we
distribute
the
project
and
also
there
are
distributions
for
public
cloud.
B
So
in
many
cases
you
don't
have
to
spend
too
much
time
on
the
configuring,
your
Jenkins
and
to
setting
up
it
up,
because
there
are
also
packages
which
provide
required,
plugins
and
figurations
to
quickly
bootstrap
your
Jenkins
instance
in
the
cloud
I
just
mentioned
a
few
projects.
There
is
a
lot
more
of
them,
but
I
want
to
highlight,
but
the
project
evolves
well,
and
there
is
a
lot
of
changes
happening
in
the
project.
B
At
the
same
time,
there
are
some
obstacles,
I
wish
we
a
heat,
and
we
these
obstacles
are
not
exactly
new
to
open
source
community.
We
are
no
exception
in
this
room
and
just
those
few
firstly
taking
the
size
of
the
project
we
put
a
lot
of
is
rated.
Some
communities
mean
having
full
independence.
Integrity
is
great,
but
at
the
same
time
example,
there
are
common
approaches
and
expectations
from
users
for
security
process,
and
we
still
need
to
deliver
on
these
expectations
and
when
there
are
multiple
communities
say
we
should
frequently
communicate
with
each
other.
B
Otherwise,
a
lot
of
disconnect
happening
and
again
we
experienced
it
in
our
project
and
we
try
to
fight
with
it.
Also.
There
is
a
lot
of
transparency.
It's
not
because
there
is
intentional
lack
of
transparency.
You
can
go
to
GA,
you
can
go
to
many
trees
and
you
can
discover
a
lot
information
and
also
on
github
the
same
time
you
as
a
user.
If
you
just
go
to
the
junkies
website
yeah,
you
may
struggle
to
find
the
information
you
need.
So
you
don't
know
where
to
start.
You
do
not
know
where
the
project
is
going.
B
Yes,
by
investing
a
lot
of
time.
You
can
find
this
information
it's
hard
to
understand
how
some
decisions
are
made,
what
the
plans
etc,
etc.
Also,
it
may
be
perceived
as
a
lack
of
focus
because,
again,
as
I
said,
Jenga
solution
happens
in
directions
where
we
get
contributions
and
it
means
so
that
a
100
contributors
interest
in
different
topics.
So
then
Jenkins
may
be
evolving
in
100
different
directions.
B
At
the
same
time,
if
you
are
interested
to
join
initiatives,
it
may
be
also
hard,
because,
even
if
there
is
a
lot
of
initiatives,
you
can
find
information.
How
to
join,
how
to
contribute
and
how
to
participate
in
an
particular
initiative
in
some
pieces.
You
can
find
this
information.
In
some
cases,
it's
very
hidden
or
implicit
may
be
obvious
to
experienced
contributors,
but
probably
not
obvious
to
the
community
in
general
and
with
all
these
factors
with
huge
community
agencies
has
a
relatively
small
core
team.
B
What
quality
means?
It's
not
a
Jenga
score,
it's
a
team
of
contributors
for
interest
in
the
project
and
a
system
in
general
who
invest
that
time
to
maintain
a
chi
system
in
general,
not
particular
components,
and
for
me
this
contributor
said
but
born
on
the
community,
because
they
help
the
project
to
grow.
They
help
other
contributors
to
join
the
project.
They
facilitate
various
programs,
provide
expertise,
and
this
is
critical
for
the
open
source
coming
again.
B
You
also
add
three
officers
introduced
multiple
sub
projects,
infrastructure
changes
every
meet
ups
like
the
technical
projects
like
remote,
encouraging
evergreen,
and
this
helped
us
to
creating
group
of
contributors,
focusing
on
particular
efforts
to
somehow
coordinate
these
efforts
within
these
groups.
Well,
716.
We
also
started
outreach
programs
resuming
go
to
onboard
contributors
and
the
Tron
board,
not
only
new
contributors,
but
also
on
board
contributors
from
plugins
and
other
peripheral
sub
communities
to
the
core
team.
B
So,
basically
growing
this
smaller
core
team,
which
basically
focuses
on
a
sustainability
of
the
project,
then
in
2017
we
got
Jenkins
enhancements
proposal
process.
So,
basically,
it's
a
process
which
allows
to
publicly
propose
changes,
including
architecture
ones,
process
ones,
and
this
process
by
now
got
more
than
40
jobs
submitted
and
many
of
them
have
been
implemented.
B
So
it
helped
us
again
to
become
more
transparent
about
being
in
shapes.
We
have
and
to
provide
the
venue
for
reviews
and
discussions
in
2018
I
have
introduced
special
interest
groups.
It's
basically
working
groups
interested
on
particular
topics.
For
example,
what
platform
special
interest
group
was
the
first
one
to
be
created,
and
there
was
cloud
native,
special
and
group
advocacy,
a
Chinese,
localization,
etcetera,
etcetera.
So
these
working
groups
focus
on
particular
topics
in
the
community
and
people
devolution.
B
They
have
their
own
plans,
so
they
try
to
faciliate
contributors
to
day
six
and
they
deliver
on
various
initiatives
within
the
scope
of
interest,
those
Alan
Menken.
There
was
advocacy
and
outreach
she
introduced
and
one
of
objectives
of
this
six
grow
awareness
about
the
project,
grow
contributions
and
help
new
contributors
to
join
the
project
and
to
be
efficient
there.
B
This
took
over
various
events,
outreach
programs
and
also
where
does
things
like
contributing
the
communication
and
they
it
helped
us
get
more
contributors
and
to
provide
the
support
from
where
they
begin
public
contribution
experience.
Then
in
2010
had
a
governance
board
elections,
so
our
government
support
guru
from
three
people
to
five.
We
also
start
with
the
governance
meeting.
We
say
which
were
a
bit
dormant
for
a
few
months.
B
We
followed
and
the
project
started
evolving
in
many
directions,
because
when
we
have
more
governance,
board
members
and
when
governance
board
members
that
getting
involved
in
particular
initiatives
and
starting
these
initiatives
mean
we
can
have
more
focus
on
particular
areas.
So
this
is
the
current
state
and
actually,
if
you
can
see,
the
jump
is
community
scares.
It's
not.
There
is
a
lot
of
various
community
entities
available
in
the
project
and
this
entities
grow.
They
have
plans.
So
from
the
project
standpoint
we
actually
do
have
some
plans.
We
do
have
some
transparency.
B
We
do
have
a
ways
to
contribute,
but
there
is
still
difference
between
a
project
and
a
community,
because
community
involves
Jenkins
users
adopters
who
are
not
fully
involved
in
the
project,
etc,
etc.
And
since
we
have
some
transparency
inside,
maybe
we
could
also
provide
some
returns
policy
outside
so
that
we
can
help
users
to
understand
what's
going
on
in
the
project.
B
A
I
haven't
seen
any
but
I
was
I
was
particularly
impressed
by
your
observation
on
the
transparency
it
was
becoming
public
about.
Our
plans
makes
it
so
that
people
can
see
very
rapidly
where
we're
going,
not
just
having
to
do
an
awful
lot
of
research
to
go,
find
the
direction
in,
amongst
all
the
public
resources
we
have.
So
so
I
love
this
this.
For
that
reason,
it
makes
it
consistent
and
consolidated
so
that
people
can
find
readily.
B
That
yeah,
okay,
let's
move
on
and
let's
finally
talk
about
the
roadmap,
so
yeah
public
Jenkins
roadmap
is
the
way
we
put
in
focus
ability
of
initiatives
happening
in
the
community
and
we
started
discussing
public
roadmap
for
real
at
FOSDEM
southern
20
contributor
summit
in
Brussels
and
Brussels.
It
was
in
February
before
that
inhibitor
standards
me
very
implicitly
discussing
roadmaps,
like
Beijing
as
goals
etc,
but
we
have
never
put
effort
to
communicate
a
wider
Road
map.
B
We
were
talking
about
particular
features
particular
initiatives,
but
there
was
no
on
southern
feat
overview
of
the
jenkees
project,
so
they
do
off-road
magazine.
She
did
to
provide
it
and
we
started
working
on
that
in
February
much
we
created
the
Jenkins
enhancement
Raposo,
which
basically
means
roadmap
process.
Again,
it's
a
public
process,
so
everybody
was
able
to
review
and
contribute
to
this
roadmap
and
the
process.
Then
we
published
the
first
preview
and
the
natural
2020.
B
We
had
the
first
road
map
meeting,
hopefully
in
July,
maybe
in
a
few
weeks-
hopefully
next
week,
we
will
be
able
to
publicly
release
that-
and
this
is
an
objective
for
me
and
the
to
this
meeting-
to
provide
heads-up
contributors
about
what
what's
going
on
there
and
what
to
expect
and
how
to
contribute.
Okay,
just
to
spend
time
I'm
a
bit
on
the
roadmap.
I'll
probably
just
show
it
to
you
so
that
we
are
not
just
talking
about
roadmap
without
anything.
B
So
this
is
our
road
map
review,
which
is
currently
published
on
JSA
on
this
road
map
is
publicly
accessible.
It
is
various
initiatives,
is
a
focus
on
Jenkins
users
and
the
community,
so
we
focus
not
on
particular
special
interest
groups,
not
own
particular
entities
but
user
use
cases,
example
by
time,
authoring
tools
and
integrations
user
experience,
management
drinks
on
the
cloud
etc.
So
we
also
list
the
initiatives
which
are
a
part
of
the
community.
So
again,
regardless
of
what
is
the
area
of
initiative,
you
can
put
it
on
the
roadmap.
B
Initiatives
which
help
contributors
to
develop
Jenkins
also,
we
have
initiatives
focused
on
contributor
onboarding
and
facilitating
changes.
Contributors
on
advocacy,
outreach
and
also
an
internal
stuff
I
think
is
in
infrastructure.
So
the
rest
parts
of
the
national
strategies
which
are
visible
for
you
I,
will
just
click
this
button.
So,
for
example,
we
have
an
initiative
for
related
to
modernize.
Ingenious
mirrors
it's
about
user
experience
because
it
makes
a
infrastructure
more
stable.
B
It
writes
plugins,
it's
faster
setup
of
techniques,
but
at
the
same
time
some
projects
are
basically
hidden
and
have
no
user
impact,
still
they
important
for
the
project
sustainability
and
for
its
evolution.
So
we
listed
on
the
roadmap
and
lost,
but
this
will
have
governance
listed.
So
this
what
we
have-
and
you
can
find
a
lot
of
items
there
so
for
pipeline
as
llamó
they
do
a
presentation
at
the
Jenkins
online
meet
up
in
ten
days.
B
Also
there
are
various
initiatives
like
13,
which
you
can
already
try
out:
plugins
like
machine
learning
or
get
performance
and
with
objects
weathers
coming.
In
give
an
example,
may
we
have
your
yurt
slugfest
and
you
can
find
it
here
because
again,
it's
pretty
important
to
improve
user
experience
and
interfaces
and
also
you
can
find
weather
changes
related
to
administration
for
the
system.
B
Great
admission,
also
script,
security
improvements,
but
management,
various
things
like
pluggable
storage,
so
you
can
find
all
of
that
there
and
same
for
the
cloud
you
can
find
some
initiatives
there
again
at
the
moment
we
didn't
list
the
entire
well.
There
is
still
some
initiatives
which
might
be
missing
and
we
might
contributors
to
submit
their
initiatives
and,
if
they're,
working
on
something
big.
So
if
you
go
to
this
link,
how
to
suggest
a
new
road
map,
I
can
actually
find
guidelines
which
describe
how
to
do
that,
and
this
process
is
really
simple.
B
You
basically
go
to
Jamie's
REO
and
submit
a
pull
request
against
our
Yama
file.
So
this
gamma
file
basically
templates
open
data
for
the
project
and
for
the
road
map,
and
you
can
find
a
lot
of
initiatives
listed
here.
So
we
initiative
names
and
description
status,
link
to
details
where
you
can
find
more
information,
contributing
guidelines
etc
and
put
some
labels
which
help
us
to
filter
initiative.
B
So
if
you
want
to
contribute
item,
you
just
get
this
toad
movement
leaders
in
a
fork
submit
a
pull
request
and
then
it
will
be
attributed
to
by
the
governance,
both
death
and
hopefully
published
on
the
road.
So
this
is
a
quick
introduction
how
it
works
and
I
also
want
to
describe
how
it
works
in
principle.
So
the
main
idea
is
to
have
open
process
so
that
everybody
can
contribute
decisions
and
devolution
of
the
roadmap
are
fully
transparent
and
that
you
can
access
this
information
about
these
decisions
and
about
why
we
mail
them.
B
Also,
there
is
open
data,
so
everybody
can
access
current
snapshot
of
the
road
map
and
its
history,
if
you're
interested
in
that
and
if
you're
interested
to
take
it
and
use
for
your
decision-making
process.
So,
for
example,
if
you're
urging
this
vendor,
you
discover
an
initiative
like
system,
critical
mission
and
think,
okay,
probably
it's
time
to
invest
in
supporting
weight
for
my
users
or
probably
it's
time
to
prepare
and
to
train
my
teams.
It's
also
possible-
and
this
is
why
we
provide
the
roadmap
as
users.
Here.
B
You
can
also
see
what's
happening
and
you
and
prepare
to
new
features.
If
you
see
new
features
in
preview,
and
actually
we
have
quite
a
number
of
them-
it
means
that
you
can
try
them
out
and
we
will
appreciate
any
feedback
you
share
and
also
us
user
can
explore
them
and,
for
example,
prepare
to
the
adoption
or
set
for
the
year
dr.
Moten.
So
again,
the
road
map
could
be
helpful
for
users
and
everything
is
activated
on
a
single
page.
B
So
another
thing
which
is
important,
that
everybody
is
welcome
to
contribute,
so
anybody
can
say
road
map
I.
Can
we
encourage
share
special
interest
groups,
teams
and
some
projects
to
contribute
items,
but
in
fact
anybody
can
do
that
and
we
appreciate
contributions
by
England
and
the
toad
map
is
for
the
community
driven.
So
it
means
that
if
you
are
interested
in
something
then
road
map
can
help
you
to
facilitate
the
process.
B
You
can
try
to
find
all
contributors
and
if
you
find
them,
you
can
also
put
them
on
another
road
map.
Start
discussion
answer
special
interest
group
on
many
of
these
and
hopefully
facilitate
the
change
speed.
Even
if
you
don't
write
code
on
you
know
it's
how
community
works,
because
you
can
facilitate
changes
without
commitment
on
your
own.
B
The
same
time
build
map
is
a
community
roadmap,
so
it
means
that
there
is
no
commitment
on
days
and
many
means
basically
Jamie's
contributors
work
on
that
we
make
no
commitment
on
deliver
days
or
for
the
record,
no
commitment
delivery
at
all
at
any
time.
Even
there
is
no
contributor
to
them.
Initiative
may
die
off
then
at
some
point.
Somebody
make
take
it
over
and
we'd
survive
again
a
part
of
their
open-source
process,
and
we
have
no
intention
of
changing
anything
there.
B
A
B
Tod
maps
are
not
supposed
to
have
deets
yeah.
There
are
different
approaches
in
tech
industry,
but
yeah.
It's
a
completely
separate
topic.
Okay,
my
briefly
summarized
what
we
have
on
the
road
map
and
protists.
So
I
will
just
give
this
slide,
and
actually
I
would
like
to
spend
a
few
minutes
about
how
it
works
in
principle.
So
we
haven't
discussed
these
stages,
so
we
have
released
stage,
which
is
quite
obvious.
It
means
that
the
initiative
is
completed
and
that
there
is
no
major
force
needed
to
do
that.
B
We
have
started
using
for
that
modern,
yellow
and
soon
preview,
because
we
know
that
we
need
to
update
it
the
process
in
order
to
address
changes
in
how
a
bit
heart
occasions
work
and
same
from
other
icons.
So
preview
basically
provides
you
a
snapshot
of
what
you
can
try
and
there
are
guidelines
how
to
tried
it.
A
current
is
what
we
are
working
on.
It
means
that
there
is
something
there
there
is
ongoing
development.
At
the
same
time,
there
is
no
trivial
way
a
to
try.
B
It
out
you're,
welcome
to
join
this
project
to
contribute,
and
we
feed
back
many
pieces
as
possible
to
try
this
changes
out,
but
it
just
not
trigger
me
at
all
I
mean
so
that
initiative
is
planned
to
be
worked
on
soon
and
there
were
contributors
who
the
create
they
intend
to
work
on
that
and
we
expect
it
to
start
soon.
There
might
be
some
contributions,
proof
of
concepts,
but
generally
there
is
nowhere
a
push.
You
should
say
that
let
us
say
that
it's
in
current
state,
so
this
is
what
we
expect
to
happen.
B
Let's
say
well
in
this
fusion,
no
dates
given
and
future.
It
means
that
there
is
consensus
in
the
community
that
we
want
to
do
something
about
it.
At
the
same
time,
we
do
not
provide
explicit
timeline
for
when
it
would
happen.
It
doesn't
necessarily
mean
that
there
is
no
contributors
who
are
interested
to
work
on
that,
but
maybe
contributors
understand
that
there
is
no
time
the
same
time.
I
may
want
to
list
it
on
the
roadmap
to
highlight
that
this
is
a
directions
where
the
project
the
world
and
there
are
directions
where
we
invite
contributions.
B
Okay,
so
yeah
this
roadmap,
since
there
was
no
questions
in
the
chat.
I
will
briefly
finish
the
presentation,
and
then
we
can
talk
about
various
aspects
of
the
roadmap.
So
what
are
the
next
steps
from
you?
Firstly,
to
keep
addressing
great
feedback
and
top
date,
the
Jenkins
enhancements
proposal
to
reflect
their
to
state
on
the
roadmap,
but
the
moment
what
we
really
is
feedback
so
that
we
can
improve
visualization
of
the
roadmap.
Maybe
atma
details
some
o8
motor
map
items
and
it
would
be
great
if
you're
interested
to
submit
your
at
the
same
time.
B
B
Next
week
we
plan
to
hold
edging
his
governance
meeting
where
we
will
discuss
whether
this
roadmap
process
is
ready
to
go.
We
battle-tested
governance
meetings,
who
request,
reviews
and
person
I
believe
that
it's
ready
to
go
on
the
governance
meeting.
We
will
vote
ready.
It's
ready
to
go
or
not
so
I'm,
not
sure
whether
it
will
be
published
but
we'd
see.
One
of
key
contributors
today
is
Alex,
oh
and
thanks
to
him
for
becoming
a
beautiful
delegate,
because
it's
not
me
who
doesn't
a
decision
about
publishing
this
job.
B
B
So
today
is
that
introduction
for
contributors
we
also
try
not
to
facilitate
traffic,
can
feed
back
to
Rodman
and
again
we
will
keep
working
on
the
content
and
improving
that
so
that,
if
you
have
something
share
and
then
you
can
bet
very,
it's
definitely
not
only
conjul
i15
soul
eater
and
we
will
keep
a
regular
road
map
meetings
like
documented
in
the
process.
So
if
you
open
this
job,
you
can
find
that
there
is
a
lot
of
items
and
one
of
their
items
is
road
map
to
be
meeting
and
volume
are
Halen's
guidelines.
B
So
basically,
these
are
two
sections
which
determine
how
we
go
further
so
and
followed
map
review
meeting.
We
will
be
doing
a
quarter
there.
Public
road
map
review
most
likely
as
a
part
of
agendas,
governance
meetings
later
student
Commedia
technical
steering
committee
is
on
our
roadmap,
so
once
it's
there,
we
may
change
the
process,
but
right
now,
every
quarter.
We
will
be
hosting
governor's
meeting
about
that,
and
it's
not
that
we
will
be
a
breaking
this
roadmap
every
quarter.
B
It's
not
just
governance
board
members
and
that's
how
we
achieve
always
the
right
decisions
of
the
board.
If
you
do
man,
if
you
disagree
with
them,
so
yeah
that's
all
about
process,
and
hopefully
it
will
help
our
users
so
too
many
takeaways
about
the
roadmap.
So
public
road
map
should
help
all
community
members
to
get
more
insights
into
the
project,
how
to
balls,
what
are
very
estimations
and
what
I
mean
she
keeps
happening
with
it,
and
community
members
include
so
users,
contributors,
vendors,
adopters,
etcetera,
etcetera.
B
Basically,
anybody
who
uses
Jenkins
or
whose
company
uses
Jenkins
they
can
discover
where
the
project
goes
and
there.
At
the
same
time,
from
the
community
standpoint,
a
public
road
map
can
help
us
to
facilitate
the
changes
in
the
project,
because
when
we
publish
a
list
roadmap
items,
actually
we
have
a
good
chance
of
beating
contributors
interested
in
this
project
or
we
could
find
our
early
adopters,
who
would
provide
feedback
to
commuters,
etc,
etc.
B
So
public
roadmap
not
only
helps
our
users,
but
it
also
helps
us
to
keep
the
evolution
of
the
project
and,
if
you're
interested,
it's
actually
a
great
time
to
contribute.
So
if
you
would
like
to
contribute
to
Jenkins,
we
have
Jenkins
io
/
participate,
page,
which
the
comments,
various
kinds
of
contributions,
including
code
documentation,
design
with
realizations.
B
So
whatever
you
interested
in
in
a
project
of
Jenga
scale,
I
believe
we
can
find
something
which
could
be
good
fit
your
interest
and,
for
example,
if
you
want
to
write
code,
there
is
a
lot
of
links
that
are
links
to
a
new
hammer
from
the
issues.
So
there
is
sections
for
newcomers
where
you
can
find
issues
you
could
start
from
if
you're
interested
or
if
you
want
to
contribute
on
larger
scale,
yes,
but
is
notifying
documentation
for
other
psychons.
Hopefully
we
can
do
this.
B
I
can
use
to
the
road
map
as
well,
but
you
can
find
this
information
here
and
it's
not
only
about
code
everything
it's
valuable
to
the
community.
We
will
appreciate
three
versions
to
any
area
whether
it's
content
management,
whether
it's
the
commentation,
the
communication
open
source
projects,
is
really
important
and
contact
markridge.
If
you
would
like
to
contribute
and
also
reviews
any
kind
of
feedback
helping
users
all
of
that
counts.
So
if
you
insist,
contribute,
please
do
so
and
yeah
that's
it.
B
B
Please
do
so
because,
yes,
the
project
levels
on
a
particular
note,
if
you
want
to
improve
the
roadmap,
the
layouts
again,
it's
totally
possible
so,
for
example,
eight
materials
or
guidance
to
roadmap
items
or
improve
your
layouts
I
am
NOT
a
web
UI
developer.
So
I
guess
the
top
of
my
JavaScript
skills
was
actually
implementing
this
filtering.
But
if
you
see
some
improvements,
for
example
in
any
search
or
provided
by
the
critical
Equalization,
it
would
be
appreciated.
B
A
Like
there
have
been
some
comments
in
the
chat
channel
that
that
page
you
head
up
would
be
great,
would
you
be
okay
if
I
ask
you
some
questions
based
on
that
road
map
page?
Yes,
though,
so
I
think
there
were
some
questions
that
might
be
highlighted
by
you,
showing
people
the
information,
that's
behind
some
of
these,
these
fields
that
it's
not
just
individual
blocks.
Here
words,
there
is
really
quite
a
bit
of
detail
behind
any
one
of
them.
A
B
Let's
take
a
look
so,
for
example,
here
one
of
items
which
is
quite
popular
at
this
days
is
a
terminology
cleanup.
So
there
was
a
lot
of
interest
in
and
a
lot
of
questions
of
how
changes
project
transport
on
the
to
terminology.
It
includes
obsolete
slave
terminology,
which
was
replaced
by
agents
in
2016,
also
master
blacklist
or
whitelist,
and
for
that
we
have
to
read
map
items.
B
So
here
aging
terminology
cleanup
is
in
progress,
terminology
clean
up
for
my
steps,
indigenous
near-term
and,
for
example,
here
for
interim
I-
think
I
just
have
a
little
and
to
the
main
list.
So
there
is
no
specific
project
page,
but
if
you're
interested,
you
can
find
a
lot
of
discussions
and
constant
the
context
here.
B
So
if
you
are
not
a
member
of
this
mailing
list,
a
later
start
from
the
first
thread-
and
you
will
be
to
follow
the
discussion
and
update
for
items
in
progress,
we
provide
more
information
so,
for
example,
agent
terminology
cleanup
if
you're
interested
in
that
you'll
click
on
that,
and
actually
in
this
case
you
just
get
to
a
peak
and
Jamie's
JIRA,
and
on
this
epic,
you
can
find
some
description
summary.
You
can
find
a
guidance
how
to
contribute,
including
new
comer
friendly
issues.
So
yeah
you
can
just
start
contributing
monthly.
B
It
was
already
represented
documentation.
She
also
that
is
a
full
list
of
school
plugins
to
particular
items
the
communications
and,
if
you
log
into
JIRA,
you
will
also
be
able
to,
but
at
least
officious,
which
has
shade
is
decided.
I
deliberately
do
not
login,
because
I'm
at
what
you
see,
what
common
decency
and
same
for
others
so
dependent
cannot
be
implementation.
B
So,
for
example,
here
system
with
permission
it's
as
to
Jenkins
enhanced
on
proposal,
because
changes
enhancement
proposal
is
that
the
best
documentation
and
includes
motivation
and
a
good
balance
and
puts
a
references
to
existing
implementations
and
JIRA
issues.
So
here
you
just
go
here,
and
there
are
multiple
examples,
but
basically
we
provide
a
lot
of
freedom
about
what
school
getting
clean
as
long
as
it
provides
enough
details
to
users
who
interest
to
contribute
some
items
just
litter
to
the
website,
something
so,
for
example,
user
interface
overhaul.
B
A
B
Layer
and
okay,
and
so
it
consists
of
two
parts,
and
actually
this
roadmap
is
modulus
filed
by
blue
ocean,
which
you
may
have
seen
several
years
ago.
Lotion
roadmap
was
fully
implemented
in
JavaScript,
for
this
roadmap
we
actually
went
is
another
solution
and
the
solution
is
actually
called
Hamel,
so
Jenkins
website
uses
documentation
as
code
and
basically
everything
is
written
as
a
business
code.
B
So
Road
marker
ish,
it's
listed
here,
so
you
can
see
that
the
Sun
take
like
eight
lines
of
code
in
total,
including
text
listed,
and
it
displays
the
entire
page
after
that
it
uses
JavaScript
to
just
render
filters,
doesn't
do
anything
else
in
JavaScript
and
also
it
uses
CSS
in
order
to
render
well
basically
I
built
it
and
yep.
Maybe
you
may
not
like
Hummel,
but
this
is
quite
short
and
it's
quite
familiar
to
Jenkins
contributors
who
contribute
to
the
website.
So
that's
why
I'm
a
decision
to
place
it
with
such
an
invasion
so.
A
B
And
so
it's
quite
safe
for
to
implement
it,
and
hopefully
it's
even
more
easy
for
users,
because
llamó
file
is
quite
straightforward
and,
for
example,
I
use,
Visual
Studio
code
to
develop
llamo
files
and
actually
even
without
llamo
schema
without
all
components.
Visuals
to
be
Cote
is
able
to
pursue
the
structure
and
make
some
assumptions
on
the
schema
and
without
any
phoniness
etcetera.
You
get
some
warnings
in
existing
components
and
you
can.
A
Elegant
so
there
was,
there
was
one
other
question
that
just
arrived:
oh
it
was.
It
was
related
to
the
plug-in
manager,
entry
specifically
on
the
on
the
roadmap,
so
it
may
be
more
detailed
than
you
want
to
go
into,
but
there
was
a
there
was
an
entry
for
plug-in
manager
and
I
know
that
Jenkins
2.2
hundred
35.1
did
significant
improvements
to
plug-in
manager.
I,
don't
recall
so
I'm.
B
There
are
two
parts,
so
improving
plug-in
manager
extreme
up.
Yes,
you
can
see
that
they
actually
the
link
points
to
the
road
map
itself.
How
could
it
mean
so
that
there
is
no
data
provided?
And
there
is
no
data
provided
by
me,
because
it's
me
who
edit
this
roadmap
item
and
I
promise,
so
that
they
will
fix
it
by
the
government's
making
corner
next
week,
but
yeah?
There
is
a
description
somewhere
in
my
drawers.
A
Now
and
I
see
so,
for
instance,
on
the
user
experience
row
there
there
there
are
things
in
different
different
stages
or
States.
Is
this
an
evolutionary
thing?
Can
you
describe
how
things
flow
from
from
the
right
hand,
side
towards
the
left
hand
side?
What
typically
happens
is
they
move
along
the
path?
Okay,.
B
So
we
go
between
the
future
in
near-term,
a
transition
happens
when
somebody
declares
intend
to
work
on
this
initiative
in
short
term,
whether
we
know
that
there
is
something
plant
and
whether
there
are
experiments
but
the
basically
it's
a
declaration
of
intent,
then,
from
medium
to
current,
when
the
work
really
starts.
For
example,
one
depository
is
first
to
request
created
the
developer.
B
My
name
is
discussions,
coordinated
effort.
Then
it's
in
progress
or
current.
It
goes
to
preview
when
something
is
released
and
available
to
users
by
a
various
ways.
For
example,
this
roadmap
is
premium.
It's
published
is
available.
You
can
just
go
to
the
page,
but
there
is
a
disclaimer.
That's
why
it's
in
premium
for
other
projects,
for
example,
for
machine
learning
plug-in
for
data
science.
A
Just
a
reminder
to
to
everyone:
could
you
bring
up
the
the
link
to
the
feedback,
form
I,
think
I've
been
posting
a
different
link,
and
so
it
would
be
good
if
the
feedback
form
linked
we're
visible.
We
encourage
people
to
please
use
that
that
feedback
form
that's
a
great
way
to
help
us
do
a
good
job
of
tuning
refining
and
improving
these
kind
of
webinars
mm-hmm.
B
B
A
I
can
just
I
just
we
just
received
two
questions:
that's
okay,
yeah!
So
so,
let's
see
oh
ok.
So
the
question
one
question
is:
hey
I'd
like
to
propose
the
least
use
a
consistent
terminology,
whether
it's
agent
or
otherwise,
and
where
would
this
contributor
put
that
proposal
and
how
is
I
think
the
question
that
is
being
asked:
okay,.
B
So
if
you
want
to
make
a
proposal
but
are
two
ways,
one
way
is
to
submit
a
pull
request
to
this
road
map.
When
you
no
way
it
would
go,
and
at
least
approximately,
where
you
already
have
documentation,
etc,
and
another
option
is
that
you
start
from
the
developer
mailing
list,
because
usually
roadmap
items
include
some
references
and
documentation
in
developer.
B
This
discussion
would
be
with
reference
that
reference
roadmap
idea
wouldn't
be
published
anyway,
so
you
can
start
from
a
submitting
a
proposal
in
the
developer
mailing
list,
for
example,
I
want
to
unify
terminology
something
like
that,
and
we
can
start
a
discussion
there
after
that,
once
there
is
some
progress
once
there
is
some
consensus,
otherwise
how
it
could
be
completed,
it's
not
necessary
to
follow
this
process,
but
yeah.
It
will
be
my
recommendation
how
to.
A
Start,
thank
you
and
then
one
more
question
came
in
which
was
and
I'm
going
to
rephrase
the
question
a
little
bit.
How
do
you
see
the
roadmap,
interacting
with
the
Jenkins
JIRA
system?
Is
the
coupling
strong?
What
sorts
of
what?
How
do
you
see
the
two
of
them
sitting
next
to
each
other
or
interacting?
Now,.
B
B
So,
for
example,
here
we'll
have
documentation
integration
to
generate
Celje,
so
this
initiative
has
documentation
and
has
get
a
ticket,
but
at
the
same
time
we
don't
create
all
tasks
for
the
communication
creation
there
anyway,
so
probably
will
change
the
listing
later.
Instead
of
that,
we
actually
operate
through
pull
requests.
There
is
a
project
for
that,
but
generally
it's
a
community
driven
effort,
which
is
the
command
needed
by
the
communication
ship
and
yet
on
the
link.
You
can
find
information,
but
this
might
be
different.
It
doesn't
have
to
be
jitter.
B
If
you
want
to
use
jitter,
my
recommendation
will
be
to
actually
use
epics,
because
these
initiatives
are
usually
quite
big
and
it
means
that
there
are
multiple
deliverables
and
such
case
I
would
recommend
using.
We
don't
have
support
for
the
kinds
of
grouping
in
JIRA.
So
if
you
want
the
epical,
free
pics
or
something
like
that,
we
doing
support
them
jenkins,
jitter,
but
at
least
some
protein
companionship.