►
From YouTube: Jenkins UI/UX Hackfest: Kick-off session
Description
On May 25-29 we will be organizing an online UI/UX hackfest, and we invite you to join this event! The goal is to get together and improve the Jenkins user experience, including but not limited to user interface and user documentation. We also invite you to share experiences about Jenkins and to participate in UX testing. Everyone is welcome to participate, regardless of your developer experience and time you could dedicate. Newcomers are welcome. The event follows the Jenkins is the Way theme and the most active contributors will get special edition swag and prizes!
At this online meetup the organizing team and project leaders will talk about the hackfest and answer questions from participants:
* Hackfest program overview
* Communication channels and events
* How to participate and contribute? How to report contributions?
* Track introductions: “User Interface”, “User Documentation”, “Spread the Word”
* Q&A
Links:
* Event page: https://www.jenkins.io/events/online-hackfest/2020-uiux/
* Registration to hackfest: https://forms.gle/8A4jJwDVCekLp9ER8
* Slides: https://docs.google.com/presentation/d/1wZpEnD6AkIiufNuvzbJZJhj649fBBAXkeQrOnaU8A-E/edit?usp=sharing
* Meetup page: https://www.meetup.com/Jenkins-online-meetup/events/270644129/
A
A
Okay,
yet
today
we
will
do
a
quick
introduction
to
the
hot
first.
We
will
discuss
how
to
contribute,
how
to
record
the
contributions
and
then
I
will
have
quick
introductions
to
project
IDs
and
tracks
by
their
leaders,
and
after
that
we
will
have
plenty
of
time
for
cony.
If
you
are
interested
to
find
these
slides
and
everything
is
open,
everything
is
public
and
I'm
going
to
just
post
it
in
our
channel.
So
you
can
find
the
slides
here.
A
So
this
is
our
little
chat,
it's
open,
24/7
and
if
you
have
any
questions,
please
feel
free
to
reach
out
to
them
and
later
we
will
talk
about
ma
communication
channels.
If
we
have
several
presenters
on
the
call
and
I
guess,
every
presenters
will
introduce
themselves
the
presentation,
so
I
will
just
do
a
quick
introduction
to
the
Meetup.
So
we
use
Jenkins
online
metre
platform
and
we
will
be
using
it
for
many
training
sessions
during
this
online
hug
fest.
A
So
main
idea
is
to
have
presentations
the
by
contributors
for
contributors,
so
we
won't
be
a
targeting.
Slides
may
be
many
sessions
won't
have
slides
at
all.
Instead
of
that,
we
focus
on
live
demos
on
Show
and
Tell
on
just
shame
experiences
and
everybody
is
welcome
to
contribute.
So
if
you
have
any
questions,
please
feel
free
to
ask
you
can
raise
hand.
You
can
grant
your
voice
permissions
if
needed,
and
you
can
use
connect
chat
for
any
questions.
A
So
if
you
want
to
ask
questions
during
the
presentation,
you
zoom
the
risk
on
a
feature
and
please
use
that
also
we
will
be
organizing
additional
office
hours
during
the
hawk.
First
I
mean
we
will
talk
about
them
and
for
foreign
communication
we
have
a
good
shot
at
medicals.
So
that's
how
communication
channels
and
let's
place
it
with
the
main
part
of
the
presentation.
So,
as
you
probably
know,
we
have
a
drink,
enjoy
your
ex
hot
fest
this
week.
So
it
actually,
we
plan
to
have
a
kickoff
session
today
at
1
p.m.
A
UTC
and
stuff
after
that.
But
we
forgot
to
put
time
zones
now
invitations.
So
officially
the
harvester
started
yesterday
and
we
also
had
a
number
of
contributions.
So
well,
it's
good
news
so
just
to
explain
some
context
of
this
hot
fest.
If
you
are
an
active
Jenks
user,
you
may
have
different
experiences
with
it,
but
one
of
the
top
feedback
we
get
from
jenga's
users
that
it's
a
user
experience
could
be
improved
and
specifically
user
interface,
the
commentation.
A
After
some
discussions,
we
started
talking
about
your
York's
hot
first
first
time
it
was
discussed
the
contributor
summit
in
Brussels-
and
here
we
are
so
we
are
doing
this
event
and
we
specifically
focus
on
improvement,
user
interfaces,
user
documentation
and
also
on
sharing
the
world
about
Jenkins.
So
any
success
stories
and
knowledge
transfer
so
they're
welcome
using
this
event,
and
we
invite
all
contributors
to
participate
and
event
of
the
event.
We
will
be
distributing
some
Swart
and
prizes
and
we
will
talk
how
to
random
waiter
so
yeah.
This
is
a
quick
introduction.
A
One
common
question
is
what
harvest
means,
because
when
we
reference
that
people
start
imagine
hackathon,
so
just
all
the
well
apart,
so
I
get
together
for
one
day
two
days.
Basically,
how
can
sleep?
So
that's
not
what
we
are
doing
actually
we're
doing
a
quite
opposite
thing.
We
know
that
everybody
has
commitments
and
we
invite
everyone
to
just
spend
as
much
time
as
you
can
want.
A
So
if
you
can
spend
a
few
hours,
it's
fine
if
you
cannot
spend
a
whole
week,
yeah,
it's
awesome,
but
it's
quite
unlike,
and
so
whatever
time
you
dedicate
is
fine
and
we
mostly
focus
on
learning
sharing
experiences
and
having
some
fun.
So
we
will
recognize
a
number
of
training
sessions.
We
can
do
at
hawk
ki
Tisa
during
the
presentation.
So
during
the
event-
and
of
course
we
welcome
any
kind
of
contributions.
A
A
We
asked
people
to
provide
top
three
things
that
they
would
like
to
change
in
Jenkins,
and
we
got
quite
a
number
of
responses
there
thanks
everyone,
we
will
be
placing
this
response
and
publishing
them
later,
but
we
definitely
know
that
there
are
some
York's
issues.
We
could
address
another
point
about
this
hackfest
that
it's
a
newcomer
friendly,
so
you
don't
have
to
be
an
experienced
during
his
developer
or
you
didn't
have
to
be
an
experienced
developer
at
all.
A
There
are
topics
which
which
can
be
handled
by
everyone
and
if
you
want
to
just
contribute
in
to
Jenkins,
it's
a
good
app
again
to
do
that.
So
I
would
like
to
thank
the
entire
team
which
made
the
dissident
possible.
So
there
was
a
lot
of
transport
to
make
it
happen,
thanks
to
Mark,
to
Tracy
CA,
to
team
mark
and
ELISA
who
helped
with
different
aspects
of
the
preparation,
and
also
thanks
to
all
the
special
interest
group
members
who
helped
to
review
the
initial
stories
project
ideas
and
provided
a
lot
of
feedback
during
the
event.
A
A
Okay,
so
we
can
continue.
I
will
talk
how
about
participating
to
this
event
and
again
we
will
talk
about
topics
so
how
to
get
started
if
you
registered
it
to
the
heart.
First,
you
have
already
received
an
email
which
summarizes
common
steps.
We
also
have
it
on
the
Jamie's
website
and
I
will
just
quickly
show
to
you
so
first
thing:
if
you
haven't
registered
yet,
please
feel
free
to
register.
You
can
do
it
at
any
moment
during
the
hot
fest.
A
So,
for
example,
if
you
decide
participate
on
Friday,
it's
still
possible
just
to
do
it,
and
this
is
actually
quite
short
form
a
short
guess,
but
you
can
see
my
responses,
so
they
know
okay.
So
basically
we
ask
you
to
provide
your
email
address.
We
will
need
it
for
the
liberty
of
schwa,
because
we
need
to
contact
you
somehow,
if
you're,
not
comfortable
with
that,
you
can
just
register
in
the
editor
channel.
So
just
say:
I
want
to
contribute
and
we
will
track
that
and
then
specific
it
hop
ID,
which
we
need
for
information.
A
My
display
name
and
also
you
ask
how
much
time
you
would
like
to
spend
whatever?
Would
you
like
to
work
on
yeah
these
three
things
you
would
like
to
improve?
You
have
to
say
your
feedback
and
after
that
also
some
details.
So
once
you
register,
the
next
step
is
to
actually
join
our
Geetha
channel
again
Jake
this
guy
/
hot
fest.
Everything
will
be
discussed
here.
It
is
for
the
moment.
Maybe
later
some
teams
will
be
using
different
channels,
but
for
any
kind
of
pony.
Please
join
this
channel.
A
So
then,
well,
you
already
participating.
Can
they
kick
off
session?
So
we
no
need
to
spend
time
on
this
step,
but
we
will
publish
the
recording
and
make
it
available
and
after
that
you
just
need
to
take
a
look
at
the
project
ideas
and
to
think
about
what
you
would
like
to
work
on
we'll
get
to
that
later
and
after
bit,
that's
it
you
can
start
contributing.
So
it's
quite
straightforward
and
let's
talk
about
how
to
contribute
on
the
Jenkins
project.
We
actually
invest
a
lot
of
time
in
maintaining
contributor
guidelines.
A
So,
for
example,
if
you
want
to
work
on
a
code
you
can
go
here,
you
can
find
some
guidelines.
You
can
find
the
locations
of
our
repositories.
You
can
also
find
some
guidelines
for
newcomers,
including
references
to
newcomer
ratios
and
useful
links,
which
described
how
total
tribute
and
basically
similar
information
is
available
on
all
pages.
So
please
refer
to
this
website.
A
During
the
big
hug
fest,
you
can
actually
contribute
20
array,
which
is
related
to
user
experience.
We
have
three
threads,
but
still
you
can
do
something
else
regarding
development
yeah,
if
you
know
Java,
if
you
know
JavaScript,
there
is
plenty
of
opportunities.
If
you
want
to
write
something
can
go.
We
also
have
projects
like,
for
example,
gems,
but
not
the
superior
or
CLI
and
go
you
can
embed
and
basically
you
can
find
other
languages.
For
example,
we
have
companies
in
c-sharp
and
C++,
and
a
lot
of
development
to
link
is
in
various
scripting
languages.
A
If
you
want
to
contribute
in
the
current
documentation,
the
most
of
our
documentation
is
in
documentation
as
caught
at
the
moment.
So
it's
a
flavored
mug
down
or
a
ski
dog.
We
also
invite
you
to
do
user
experience
testing.
It
may
be
in
the
testing
of
documentation,
for
example,
installation
guidelines,
tutorials
and
my
recommendation
pages
are
new
features.
We
are
working
on
all
of
the
views.
A
All's
appreciated,
as
well
as
creating
new
content,
like
blog
post,
videos,
etc,
and,
last
but
not
least,
you
can
just
help
others,
for
example,
as
answering
questions,
pointing
them
to
the
communication
channels.
It
also
counts
as
a
variant
rebuking,
so
we
do
not
really
have
to
quote
it
during
this
event,
you
can
do
other
types
and
later
we'll
talk
how
to
do
it.
A
We
have
three
tracks.
One
is
focused
on
user
interface.
Improving
can
feel
improvement,
accessibility.
We
also
have
a
major
project
for
RIT
on
the
configuration
browsing,
your
a
things
visualization
later.
We
will
talk
about
that
in
details.
Also,
there
is
user
documentation
which
is
mostly
related
to
Jenkins
I
or
to
the
plug-in
documentation,
and
we
have
spread
the
word,
which
is
a
track
focused
on
promoting
Jenkins
sharing
experiences
at
session.
What
it
was
mentioning
before.
A
Example,
if
you
want
to
quote
something
yeah,
obviously,
user
interface,
that
there
is
a
lot
of
things
you
could
do,
but
user
documentation
of
my
awesome
evolve.
Some
coding,
surprisingly,
because
to
our
website
gates,
config
documentation
is
code,
but
it
also
has
a
mention.
For
example,
it
includes
a
lot
of
JavaScript
for
rendering
otherwise
CSS
files.
Also,
we
have
a
plug-in
side
which
is
basically
written
in
JavaScript,
react
and
other
components
and
again
code
contributions.
There
will
be
a
welcome
simple
user
interface
between
features.
A
A
Ok,
I
said
contributions.
Maybe
100
times
already,
so
let's
talk
about
how
to
do
that.
So,
if
you
do
contributions
is
quite
straightforward:
you
just
pull
request
to
proper
locations.
They
will
be
reviewed,
it's
a
less
straightforward,
for
example,
if
you
want
to
publish
not
video,
if
you
do
it
on
your
website,
it's
also
possible
and
in
order
to
support
it,
we
created
a
github
repository
which
we
will
be
using
to
report
issues
so,
for
example,
yeah.
This
is
our
website
and
actually
just
a
lot
of
automation
for
the
boats.
A
And
if
you
want
to
report
your
contribution,
you
just
go
to
Isha's
click,
a
new
show
there,
and
then
you
get
the
issue
templates
for
various
kinds
of
contributions.
So,
for
example,
you
are
UX
enhancements
bug,
fixes,
documentation,
etc,
etc.
So
I'm
the
morning
Caillou
presented
an
example
way.
I
just
did
that
myself,
but,
for
example,
today
we
could
try
something
else.
You
know
that
Olivia
one
of
Jenkins
infrastructure
officer
and
one
of
active
Jane's
contributor
he
helped
a
lot
with
redirects
for
Jenkins
infrastructure,
so
just
second
hundred
central
Jenkins
intra.
A
A
A
Okay,
so
I
put
some
text,
I
submit
a
decision
and
whether
we
get
this
ticket
so
like
then
what
we
can
do
now.
Somebody
from
orchid
means
we'll
process
this
contribution
and
we
just
use
all
contributors
for
that.
So
he
Olivier
is
the
communication
and
reviews
questions.
I,
don't
have
to
worry
about
what
exactly
I
write,
because
it
has
a
lot
of
magic
under
the
hood
to
recognize
text
and
okay.
So
now
we
got
pull
requests.
We
measure
this
pull
request.
A
So
what
is
OK
merge
that
and
after
that
we
have
only
be
on
the
list
done
and
if
you
want
to
submit
your
contribution,
basically
we
do
the
same
so
that
we
can
trace
this
ticket
and
just
create
reports
later
obviously
focal
contributions.
We
cannot
collect
your
requests
later,
but
we
would
appreciate
if
you
follow
the
same
approach
so
that
we
can
collectibility
so
yeah.
A
Another
part
of
this
topic,
which
we
again
they
didn't
mention
that
we
don't
have.
We
don't
require
contributor,
license
agreements
from
contributors,
so
you
have
to
be
silly,
but
this
really
applies
only
to
contributors
who
get
special
permissions,
for
example,
in
the
Jenkins
infrastructure
or
documentation
us
contributor
doesn't
I,
don't
have
to
do
anything.
If
you're
allowed
to
submit
code,
you
can
submit
code
if
you're
not
allowed
to
submit
code,
then,
even
in
the
such
case,
you
can
still
do
something.
A
Okay
continue,
so
another
question
is
about
communication
channels,
so
we
have
this
little
chart
if
you're
not
comfortable
with
the
charts
we
also
have
made
in
please.
So
there
are
three
main
increase:
form
user
experience,
documentation
and
rotation
outreach,
so
we
straight
one-minute
list
and
for
general
questions,
so
that
is
also
developer,
demand
increased.
We
will
build
organizing
office
hours
so
that
it's
just
a
common
meeting
in
Google
hangout,
which
you
can
join
and
basically
discuss
any
question.
So
just
chat
with
people
about
anything
related
to
Jenkins.
We
will
have
daily
sessions
at
8:00
a.m.
A
UTC
and
we
also
have
session
set
to
be
a
magician.
So
you
are
welcome
to
join
any
of
this
session,
we'll
see
if
you're
interested
and
if
that
teams
can
create
their
own
sessions
on
demand
right.
If
you
want
to
navigate
through
these
sessions,
we
have
an
event
can
handle
specifically
played
for
this
event.
I
look
on
the
calendar
link
so
yeah.
A
We
will
be
still
announcing
more
sessions
to
Thursday
and
Friday,
and
everyone
is
welcome
to
join
and
present
something
if
you
are
interested
but
yeah,
this
the
source
of
truth
for
the
events,
and
we
will
try
to
keep
it
up
to
date,
we
experienced
some
issues
with
Google
hangout
weddings
because
it's
really
difficult
to
manage
to
them
after
the
recent
changes
but
yeah
the
most
of
the
meetings
actually
happened
in
some
except
office
hours,
which
really
happen.
Google
hangout.
A
Ok,
another
flavor
of
meetings
is
online
meetups.
As
we
said,
there
will
be
a
number
of
training
sessions
for
different
topics,
mostly
for
developers
and
contributors,
but
they
will
be
some
user
focused
sessions,
and
if
you
want
to
find
all
these
sessions,
you
just
can
go
on
jenkees
online
meter
platform,
and
here
you
can
find
a
list
of
upcoming
events.
You
have
to
go
here
because
so
this
list
currently
doesn't
fit
to
the
default
layout
of
five
meetings
but
yeah.
A
This
is
our
sessions
we
already
have
published
and
you
can
see
that
you
can
just
add
SVP
and
then
join
this
session.
You
can
add
them
to
the
calendar
you
clean
up
after
that.
You
just
welcome
to
participate
again.
If
you
want
to
host
your
own
session.
For
example,
you
want
to
talk
about
user
experience
of
particular
component
or
you
want
to
share
some
best
practices,
how
to
improve
user
interfaces
or
documentation.
Please
let
us
know
in
the
chat
and
we
will
help
you
to
get
this
session
hosted.
A
So
we
have
a
number
of
orchid
means
who
can
help
with
it
during
the
event,
please
also
be
aware
of
code
of
conduct
and
we'll
have
one
in
Jenkins.
This
code
of
conduct
is
based
on
contributed
covenant.
The
main
idea
of
that
is
just
be
nice,
so
you
want
to
make
this
event
a
great
experience
for
everyone,
so
there
will
be
participants
of
different
level
of
experience,
but
this
held
them
and
this
big
country
during
the
communications,
and
if
anything
happens,
is
that
organizers
no,
but
hopefully
it
will
be
fine.
A
B
C
Such
well
first
I
should
introduce
myself
cause
I'm
Jeremy
harshly
I'm
I'm,
a
programmer
working
at
cloud
base,
I
work
on
open
source,
Jenkins
and
also
on
some
cloud
leads
and
towers
there.
So,
first
of
all,
I'd
like
to
say,
a
lot
of
new
work
is
being
done
on
the
new
Jenkins
UI,
so
we
started
work
on
what
we
called
the
new
Jenkins
UI
at
the
end
of
2019
goals.
Very
briefly,
is
to
learn
from
blue
ocean,
so
we
abandoned
that
project.
C
We
flowed
up
by
working
on
the
footer.
We
working
the
buttons
we're
working
on
new
typography
to
work
on
a
new
navigation
sidebar.
We
work
on
new
iconography
next
slide.
Please
and
really
I
just
want
to
make
a
cause
action.
If
people
beyond
this
hack
first
are
really
serious
about
helping
out
the
Jenkins
UI,
please
come
and
join
us
at
the
Jenkins
user
experience
special
interest
group.
We
started
this
late
last
year
we
meets
every
two
weeks.
That's
3
p.m.
C
C
A
We
take
a
look
at
the
project
ideas,
so
if
you
participated
in
the
morning
session-
and
we
just
went
through
the
list-
suggest
something
quite
good,
so
we
have
quite
a
number
dodge-
it's
published
for
yo
I,
your
ex,
so
starting
from
the
bottom.
One
of
the
items
is
for
Jeremy
described,
just
a
look
and
feel-
and
there
is
a
number
of
related-
a
new
comer
friendly
issues.
You
could
register
queries
for
almost
everything.
A
So,
for
example,
here
you
can
see
that
there
is
a
number
of
issues,
for
example,
related
to
Jenkins
course,
warnings
and
G,
plugin,
etc.
If
you
want
to
find
more
issues,
for
example,
this
one
and
just
newcomer
friendlies
with
remove
this
label
and
we
will
see
all
the
issues
and
you'll
get
something
like
300.
A
Obviously
some
of
them
may
be
invalid.
Some
may
need
some
processing,
but
for
this
we
are
quite
confident
that
they're
relevant
and
you
could
work
on
them.
If
you
want
to
start
working
on
something
example:
destination
folder
authorization
plugin,
then
one
button
doesn't
work
and
admissibility
is
already
working
on
that,
because
I've
seen
that
there
might
be
just
new
UI
for
the
plug-in.
But
let's
take
let's
find
something
which
is
not
assigned
at
the
moment.
A
Okay,
so
drink
Scott
has
no
default
assign.
So,
for
example,
if
I
wanted
to
work
on
decision
yeah,
you
would
need
to
have
access
to
Jenkins
jitter
and
after
that
you
can
just
send
a
to
yourself.
Example.
Well,
I'm
not
on
that
is
today,
but
yeah
I
can
assign
it.
I
can
start
progress
and
I
can
start
working
on
that
and
then
submit
a
pull
request
and
everybody
who
visits
this
issue
will
be
able
to
see
that
it's
actually
a
quite
so
this
how
you
can
modify
that
for
the
components.
A
Sometimes
we
use
changes
data.
Sometimes
you
use
github,
which
we
have
wishes.
We
get
happy
issues.
Our
recommendation
is
just
put
a
comment
because
you
have
to
have
write
permissions,
not
assign
a
mission
so
yeah
in
our
case,
we'll
just
recommend
putting
a
comment
and
then
it
will
be
handled
okay,
so
this
is
Luke
and
Phil
updates.
Another
third.
Well
that
is
actually
accessible
again.
A
There
is
a
number
for
projects
and
the
idea
is
totally
make
Jenkins
usable
for
everyone
and
doesn't
include
groups
with
disabilities
or
network
connections,
but
also,
for
example,
mobile
devices.
If
you
have
ever
tried
using
Jenkins
on
mobile
device,
you
probably
know
what
I'm
talking
about,
and
there
is
number
of
projects
which
could
help.
One
of
the
major
projects
which
we
have
ongoing
is
changing
Jenks
duration,
UI
from
tables
to
leaves.
A
D
Sure
so,
for
so,
since
the
beginning,
the
Jenkins
layout
has
been
done
using
tables
which,
back
when
it
was
originally
built,
was
how
layouts
was
done
for
a
long
time.
Since
then
that
has
not
been
the
standard,
and
it's
made
some.
It's
made
modernizing
your
way
quite
difficult,
so
Josh.
So
if
about
a
year
ago,
no
more
than
a
year
ago
now
started
working
on
trying
to
modernize
there
I
think
there's
been
one
or
two
previous
attempts
as
well,
but
this
is
the
one
that's
gotten
the
closest.
D
So
we
have
a
fully
functional
conversion
from
tables
to
dibs
and
what's
possible
to
do
that,
because
most
of
the
controls
are
all
inside
of
Jenkins
core,
so
plugins
use
either
jelly
or
groovy.
Usually
in
don't
muck,
don't
write
much
HTML
directly
so
because
of
that
we've
been
able
to
change
all
the
central
controls
and
we've
made
a
few
UI
improvements
as
part
of
this
as
well.
So
you
see
they're
out,
that's
element
they
only
just
hit
opens
they
just
closed
so
see.
There's
now
a
visual
indication
when
something
is
associated
to
a
parent.
D
So
you
see
the
source
code.
Management
is
a
child
at
modern
ECM
and
then
get
as
a
child
of
source
code
management.
So
it
helps
you
associate
the
illness
to
the
UI,
it's
kind
of
works
in
the
current
implementation,
because
they're
all
moved
over
to
the
side.
That's
some
of
them.
It
doesn't
work
so
well
on
others.
Some
other
improvements
is
that
mobile
works
really
well
on
this
without
any
effect
for
it.
So
this
wasn't
done
at
all
from
oh
well,
but
it
just
it
just
works
out
of
a
box
for
a
lot
of
functionality.
D
So
that's
that's
what
the
configure
page
looks
like
and
just
in
general,
most
of
the
elements
we
move
to
the
top
and
the
fields
on
the
bottom.
So
what
we're
mostly
looking
for
is
any
testing
well,
the
biggest
issue
we
have
right
now
is
we
just
want
to
get
there's
a
good
amount
of
tea
stinking
on
it,
so
that
we're
confident
shipping
it
any
fixes
or
improvements
and
other
plugins
to
be
useful.
D
We
have
made
some
changes
to
a
few
plugins
and
the
plugins
that
are
likely
to
break
ones
that
write
the
UI
themselves
directly
if
they
include
the
table
tag
and
they
plug
in
somewhere,
it
probably
won't
work
and
we
have
bridging
codes
and
as
examples
in
the
doctors
that
got
there's
a
how-to
guide
and
the
documentation
for
how
to
do
that.
Totally.
It's
just
showing
you
at
the
moment
and
the
others
is
Java
scripts.
There
is
tied
to
the
current
implementation
of
the
UI,
and
that
needs
to
be
able
to
handle
both
approaches.
D
There's
not
a
lot
of
JavaScript
in
Jenkins
in
most
isn't
quite
central
plugins.
So
in
general
it's
not
such
an
issue.
Those
are
the
most
likely
cases
to
break
I.
Think
we've
probably
contested
most
of
the
default
plugins.
So
in
Jenkins,
there's
a
default,
plug-in
concept
or
recommended
plug-in
concept
when
you
first
started
up
and
you
just
get
the
default
plugins,
but
there's
problem
with
some
other
popular
plugins
that
we've
missed
and
that's
where
we'd
like
some
help
and.
A
Okay,
there
are
also
some
other
issues
that
related
to
user
experience
and
accessibility,
which
of
failure.
Miner
and
somebody
is
welcome
to
start
working
on
them
and
the
case
we
can
see
that
Raman
has
already
started
working
on.
One
of
them
so
feel
free
to
take
a
look,
and
we,
if
he's
hit
malicious,
please
report
them
so
that
we
can
also
process
them,
giving
the
hard
Festo
later.
A
Firstly,
it's
a
larger
project
for
user
experience
seek,
and
there
is
a
lot
of
storage
to
be
handled
so,
and
the
next
big
project
for
us
is
system
big
permission,
so
why
it's
important?
There
is
ongoing
adoption
of
Jamie's
configuration
as
code.
It
doesn't
mean
on
Jake
asks
like
and
maybe
holes,
for
example,
Jenga
separated
for
kubernetes
hound,
charts
or
just
all
style
configuration
management
tools
and
groovy
hoops.
All
of
that
basically
allows
you
to
manage.
Jenkins,
says
code
and
various
interests
also
make
a
better
user
interface
for
that.
A
So,
for
example,
that
admins
can
browse
configurations
or
even
browse
agent
configurations
access,
Diagnostics
information
without
having
opportunity
to
modify
something
and
then
intentionally
break
something.
So
this
is
one
of
major
drivers
and
thanks
to
team
for
driving
a
job
to
talk
for
which
is
a
foundation
bid
for
system
with
permission,
Sakai
system
so
team.
Would
you
like
to
introduce
this
project
as
well.
D
D
D
Agents
didn't
actually
do
anything
so
as
part
of
this,
what
we've
started
from
system
rate
but
extend
it
to
read
own
agents
as
a
whole,
so
it's
basically
about
allowing
your
users
to
consume
Jenkins
from
from
all
the
levels,
so
they
can
see
if
their
bill
goes
wrong.
The
user
has
all
the
information
available
to
them.
They
can
see
at
the
system
level
they
can
see,
so
they
can
see
the
logs.
They
can
also
contribute
to
your
Dinkins
as
well.
By
a
configuration
this
car
they
can
see
what
plugins
are
installed.
D
They
can
see
the
current
configuration
and
they
can
also
see
who's
allowed
to
do
what
they
need
to
know.
I
think
that
grid
to
contact
they
can
see
who
the
admin
of
the
instances
all
the
information-
that's
just
not
available
out
of
the
box
so
doing
turning
this
on
allows
you
to
basically
have
a
full
read
experience
and
questa
learnt
a
lot
of
other
CI
systems
as
well.
D
D
So
there's
the
three
different
permissions
for
system
agent
and
jobs,
there's
how
to
adapt
and
I've
tried
to
put
guidance
with
jelly
and
groovy
as
it's
quite
similar,
but
if
you're
not
used
to
them.
That's
slightly
different
that
took
me
a
bit
of
time
to
figure
out
groovy,
especially
because
there's
a
lot
less
crew
beings,
examples
which
makes
it
more
complex.
A
So
follow
these
guidelines
and
again
any
kind
of
experience
and
feedback
would
be
nice.
So
the
difference
that
this
feature
basically
runs
in
the
weekly
release,
I'm,
not
sure
whether
it's
out
or
not,
but
it
definitely
will
definitely
happen
in
a
few
hours.
So
you
can,
you
will
be
just
able
to
take
the
recent
weekly
version
and
start
using
bed
for
tables
too
leaves
you
will
have
to
use
Jenkins
built
from
the
pool
request,
but
still
it's
quite
straightforward
to
set
it
up
and
get
running.
D
Lasting
on
the
system,
readers
there's
a
epoch
which
has
a
number
of
open
issues
in
there.
So
there's
a
couple
of
bugs
in
the
number
of
enhancement
requests.
So
two
things
we're
looking
for
is
more
ideas
for
what
should
be
covered
and
what's
currently
missing,
and
someone
to
pick
these
up
and
implement
them.
A
lot
of
them
should
be
quite
straightforward
to
do
right.
Just.
A
Okay,
thanks
team,
so
other
topic,
a
we'll,
be
finishing
the
export
zone,
so
other
topic
is
about
themes,
so
many
people
use
different
themes
in
Jenkins
and
they
can
actually
improve
user
experience
quite
a
lot
and
we
invite
contributors
to
contribute
to
improving
existing
teams
to
make
them
aligned.
With
the
recent
changes
delivered
in
Jenkins,
there
is
also
a
high
demand,
for
example,
in
a
dark
theme
for
Jenkins.
So
every
work
on
this
topic
personally
I'm
planning
to
spend
at
least
some
time
on
that
tomorrow
and
on
Wednesday,
we'll
have
a
training
session
for
themes.
A
Okay,
so
I
guess
with
salt
about
themes.
We
also
have
an
advanced
project
for
pipeline
visualization.
As
Jeremy
said,
the
emotion
was
a
part
of
story
for
pipeline
visualization.
It's
still
a
part
of
the
story,
but
there
is
demand
to
improve
something
around
it
and
if
anybody
is
interested
to
contribute
you're
welcome,
so
there
are
multiple
directions:
I
wish
it
could
take,
including
creating
a
new
browser,
the
ability,
for
example,
as
a
plug-in
or
maybe
doing
something
else.
Unfortunately,
we
don't
have
new
comer
friendly
ticket
so
there.
A
But
if
you
would
like
to
work
on
this
error
and
improve,
please
let
us
know
we
will
try
to
help
as
much
as
we
can,
and
so
we
also
have
some
stories
for
credentials.
Ui
improvement,
it's
a
story
submitted
by
King,
because
credentials
management
imaging,
is
quite
complicated
and
not
always
trivial.
So
if
you
would
like
to
improve
something
can
be
said,
please
do
so
and
pretty
much
for
almost
every
other
plugin.
If
you
see
something
uncomfortable
to
you,
if
you
submit
a
pull
request,
we
will
always
to
help
it
get
landed.
A
Last
but
not
least,
the
developer
tools
in
order
to
help
origin
is
developers
to
create
better
plugins.
We
need
tools,
so,
for
example,
we
have
a
plug-in
name
is
for
your
samples,
which
includes
examples
of
common
themes,
so
well,
this
plug-in
doesn't
even
have
written
it.
So
definitely
there
is
a
lot
of
opportunities
for
improvement,
and
if
you
want
to
create
a
new
samples,
for
example
today
we
will
be
doing
a
presentation
about
how
to
improve
user
interface
in
Swiss
JavaScript
libraries.
A
A
A
This
plugin
also
includes
really
the
framework
and
the
framework
support
which
we
use
for
managing
kiss
your
eyes,
and
if
you
wanted
to
create
new
yorky
types
for
javascript
based
plug-ins,
so
base
the
boilerplate
templates
everyone
and
copy
and
create
their
own
plugins
based
on
that
you're
welcome
to
do
it.
So
this
is
just
a
list
of
stories.
We
have
on
the
table
again.
This
list
is
not
complete,
so
if
you
want
to
work
on
something
else,
please
do
so
and
yeah.
A
B
B
So
we've
got
several
different
aspects
of
improving
the
documentation.
One
is
that
the
user
and
administrator
documentation
has
many
areas
that
you
can
improve
just
by
reviewing
and
renewing
it
to
be
sure
that
it
reflects
the
current
behaviors
and
the
current
to
look
and
feel
of
Jenkins.
You
could
also,
if
you're,
a
JavaScript,
coder
or
interested
in
looking
at
how
documentation
lays
out
you
can
improve
the
navigation
I
help
us
have
tables
of
contents
that
are
better
suited
to
users
who
need
to
find
what
they
are
looking
for.
B
Now,
in
addition,
we've
got
an
awful
lot
of
very
useful
content
that,
over
the
course
of
the
many
years
of
Jenkins
development
has
collected
in
the
Jenkins
wiki.
What
we're
doing
now
is
we've
got
a
project
as
part
of
this
hack,
fest
and
ongoing
afterwards.
That
wants
to
convert
content
from
the
Jenkins
wiki
into
Jenkins.
Thought
I
owe
that
conversion
process
lets
us
use
the
knowledge
that's
been
captured
in
those
wiki
pages
refine
and
improve
it
and
place
it
into
the
official
destination
on
Jenkins
style,
the
wiki
exporter
tool.
B
That's
hyperlinked
here,
will
give
you
assistance
in
making
that
conversion
from
wiki
format
into
asciidoc.
Here
it
is
what
you
do
is
into
the
top
field.
You
paste
in
the
URL
of
a
wiki
page
press
that
can
change
the
convert
output,
format
to
asciidoc
and
then
press
the
convert
button,
and
it
does
the
conversion
for
you
and
gives
you
the
brutal
entry
asciidoc
ready
to
go
so
that
wiki
exporter
will
help
you,
as
you
make
that
trying
to
help
us
make
this
transition.
B
In
addition,
if
you
wonder,
oh,
which
page
should
I
work
on
well,
we've
placed
into
github
issues.
The
top
50
most
accessed
wiki
pages
as
issues,
so
you
can
choose
one
of
these
wiki
migration
issues
and
start
working
on
that
page,
knowing
that
it
is
in
the
top
50
pages
accessed
from
the
wiki
in
the
last
roughly
90
days.
B
So
github
issues
easy
to
navigate
easy
free
to
find.
When
you
find
one
that
you
say,
I'd
like
to
work
on
this,
you
just
open
that
issue
and
place
a
comment
in
it
which
says
I'm
working
on
this.
That's
enough!
We
just
rely
on
each
other
to
read
the
comments
to
not
pick
up
something.
Someone
else
is
working
on.
B
So
that
the
wiki,
the
wiki
migration
project
is,
is
a
good
help.
Let's
go
on
to
the
next
slide,
you
that
was
great
Oleg.
In
addition,
we've
got
user
experience,
improvements
that
we're
looking
for
in
places
like
initial
installation
or
in
the
experience
as
you
work
through
a
tutorial
both
of
those
are
places
where
you
can
help
users
by
assuring
that
the
installation
works.
The
way
it's
described
and
you
can
run
Jenkins
on
lots
of
different
places
in
lots
of
different
ways.
B
We
also
have
tutorials
linked
here,
included
both
the
guided
tour
and
a
number
of
language,
specific
tutorials
that
we
want
to
be
sure,
still
are
working
correctly
and
well
behaved
each
one
of
them
takes
you
through
a
series
of
steps.
We
have
things
from
how
you
use
my
user
with
maven
how
you
might
create
a
multi
branch
project,
how
you
could
do
parallel
testing
all
sorts
of
different
ways
to
work
with
either
Python
or
node
or
or
you
choose
it.
A
I
like
to
it
that
you
know,
I
think
this
is
an
automation
server,
so
such
use
cases
are
really
important
because
if
you
develop
something
in
case
most
likely,
you
want
to
automate
something
so
real
world
experience
for
different
tools
is
essential
for
users.
It
could
help
a
lot
and
it
would
save
them
a
lot
of
time.
A
So,
if
you're
going
to
write
a
new
tutorials
for
tools,
use
its
welcome
and
also
we
have
solution
pages
which
basically
also
describe
the
various
use
cases
from
user
side,
for
example,
if
you
work
with
github
or
if
you
develop
in
Java
or
if
you
develop
in
C++,
you
can
find
something
here
and
here
you
can
see
two
obvious
issues
one,
but
we
could
have
much
more
solution
pages,
so
they
would
definitely
benefit
from
something
specific.
And
if
you
have
technology
you
use,
it's
just
submit
a
pull
request.
A
If
you
want
to
talk
about
practices
like
continuous
integration,
DevOps
continuous
deployment,
whatever
you
can
also
write
specific
pages
for
that
and
for
existing
pages,
they
also
would
benefit
from
some
improvement.
So,
for
example,
if
you
go
to
Java,
you
can
see
that
layouts
could
be
improved.
Also,
the
content
is
probably
a
bit
obsolete.
So
if
you
want
to
improve
pages,
it
would
be
much
appreciated,
because
this
is
something
jenkies
users
would
like
to
see
when
they
work,
for
they
use
cases.
B
It's
it's
impressive.
The
number
of
times
we
receive
requests
to
the
Jenkins
I/o
site,
asking
for
a
C
tutorial,
your
a
C
or
a
C++
programmer.
Don't
be
shy
at
offering
a
tutorial
that
how
you
might
use
Jenkins
to
do
C
and
C++
based
development.
It's
it's
a
very
common
need.
Lots
of
people
would
love
to
have
it
yeah.
A
A
B
I
think
that
was
next
on
the
list
right
so
plug
as
part
of
the
effort.
Special
thanks
to
Gavin
Mogan,
the
plug-in
site
has
been
revamped
and
is
significantly
better.
That
change
has
brought
us
the
ability
to
do
plugins
and
host
their
documentation
in
github
as
code,
instead
of
hosting
it
on
the
wiki
page.
So
what
you're,
seeing
right
now
that
Oleg
is
showing
is
plug-in
documentation
extracted
straight
from
github
and
placed
into
the
plug-in
site.
B
A
B
The
migration
progress
process
is
in
progress
right.
There
are
over
a
thousand
five
hundred
plugins
in
Jenkins
and
with
available,
and
that
many
plugins
there
are
a
lot
that
need
their
documentation.
Migrated
here
is
the
list
that
you
can
see
of
plugins
and
their
various
migration
states.
So,
as
you
scroll
further
down,
we
eventually
reach
a
point.
Oh
here
are
some
plugins.
The
nice
white
rose
that
have
not
been
migrated
yet
they're
to
do.
B
A
We
also
have
the
table
guidelines
how
to
process
a
bit
referenced
from
the
side
because
yeah
this
blue.
This
is
just
a
skeleton
it
usually.
The
communication
pages
require
some
copy
editing
and
when
we
immigrated
the
communication
will
be
encouraged
to
improve
the
documentation
as
they
go,
because
there
may
be
obsolete
technology,
they
might
be
just
obsolete
screenshots.
We
still
see
a
screen
shows
she
was
Hudson
interface
from
2007
or
so
so,
although
that
could
be
improved
and
when
the
immigration
we
will
appreciate
such
contributions
and
as.
B
A
personal
note:
the
process
of
converting
documentation
from
wiki
to
github
for
a
plug-in
I
maintain
made
all
the
difference
in
the
quality
of
that
documentation.
So
it's
good
that
when
we
do
this
transformation,
we
apply
brainpower
to
it.
Now,
tomorrow,
Oleg's
going
to
take
us
through
a
live
demonstration
of
how
to
convert
a
plug-in
documentation
and
yes,
it
will
be
the
Chuck
Norris
plug-in.
We
look
forward
to
Chuck
Norris
being
converted
from
wiki,
so
you
get
hub
based
documentation,
yeah.
A
That's
my
plan
and
we
also
have
a
session
by
Mark,
which
talks
about
I
think
desire
documentation.
So
again,
if
you
go
to
the
list
of
events,
so
we
have
a
session
today
with
earlier
than
we
have
a
session
today
with
Alisa
and
then
a
number
of
sessions
tomorrow,
including
through
the
communication
sessions
and
the
system,
will
commissioned
my
team
so
and
please
feel
free
to
join
any
of
these
sessions.
If
you're
interested
in
documentation-
and
we
will
do
a
deep
dive
there.
B
A
Okay,
then
really
a
short
introduction
to
the
third
break,
spread
the
word
so
a
haven
content
having
documentation
is
not
enough.
You
also
need
to
make
this
documentation.
This
information
visible,
and
it's
always
good-
to
share
the
stories
and
to
celebrate
achievements
in
the
project,
and
we
really
rely
on
generous
users
and
contributors.
We
invite
you
to
sure
to
share
these
stories.
A
Several
weeks
ago,
we
have
launched
Jenkins's
the
web
program,
so
this
problem
basically
invites
you
to
share
your
user
story
or
key
study
and
we
start
publishing
a
kiss
that
is
from
different
users
here
by
t-mobile,
etc.
You
can
go
inside
and
read
the
details
and
if
you
have
an
interesting
story
or
to
share
about
Jenkins,
please
do
so.
You
can
just
submit
a
story
on
this
website
and
we
will
appreciate
that
so
later,
today,
at
least
we'll
be
talking
about
Jenkins's
the
way
program
I
in
details,
but.
A
A
We
have
a
lot
of
announcements
here,
but
if
I
mean
the
key
study
or
sanity
any
worse
story
about
Jenkins
review
that
and
help
to
get
published
same,
you
can
do
it
when
external
resources,
for
example,
if
you
use
mediums
at
home,
you
can
do
that
during
the
hot
phase,
and
you
can
also
just
post
about
your
experience
and
new
features
which
happen
during
this
hard
Fest,
which
has
been
recently
released,
and
if
you
want
to
record
a
meteor
and
publish
it,
please
also
do
so.
It
solves
half
of
Genesis.
A
A
A
B
Continue
to
be
impressed
at
the
number
of
people
and
the
number
of
ways
that
Jenkins
is
used,
that
I
think
are
fascinating.
I
talked
just
last
week
with
somebody
who's
doing
audio
engineering
with
with
Jenkins
I
have
enough
a
family
member
who
works
on
robotics
with
Jenkins,
and
we
would
love
to
hear
your
story
about
how
you're
using
Jenkins
don't
forget
that
the
way
you're
creating
software
is
interesting,
novel
and
probably
distinct
from
the
way
others
are
doing
it.
Jenkins
supporting
it
thanks
very
much
for
being
willing.
A
Thank
you,
and
actually
it
was
last
slide.
So
if
you
have
any
questions,
we
can
discuss
them
now.
You
have
something
like
27
minutes
reserved
for
this
session
and
yeah
we
have
one
hour:
kill
will
be
begins
his
presentation
about
improving
user
experience
for
Jenkins
plugins.
So
any
questions
any
comments.
Does
anyone
want
to
talk
about
other
stories?
A
E
E
E
We
had
some
issues
with
unit
testing
frameworks.
We
were
assessing
whether
should
we
use
a
test
unit
to
test
our
applications,
but
we
encountered
a
moustache
body.
Ms/Ms
working
actually
work
with
some
other
volumes
like
flex
unit
and
the
unit,
but
it
was
only
optimized
for
m/s
test.
So
in
terms
of
performance,
we.
E
We
conclude
that
m/s
test
was
the
slowest
one
of
the
three
frameworks
that
we
tested,
but
when
we
tested
it
from
Jenkins
it
was
actually
the
fastest.
The
question
is:
I
haven't
been
developing.
This
particular
project
anymore,
but
I
wanted
to
know
if
making
an
exit
or
making
some
actual
making
more
plugins
to
be
available
for
the
community
to
use
to
develop
with
top
net
is
actually
something
that
you
can
see
that
or
if
you
don't
think
like
that,
much
Don
spot.
A
So
to
answer
this
question:
if
somebody
wants
to
create
a
plug-in
for
dotnet,
it
will
be
a
modern
welcome.
We
have
a
quite
a
number
of
plugins,
as
you
may
see,
which
you
have
some
problems.
Mr.
Gannon
kind
discovered
it
because,
for
example,
a
math
test
I
mean
doesn't
appear
there
and
they
should,
and
we
welcome
contributions,
though,
for
the
net.
We
have
historically
one
mission.
A
E
B
E
A
A
Actually,
it
can
include
distributions
for
dotnet
and
also
botnet
core
with
native
executables,
so
we
should
do
not
require
that
you
know
on
the
instance
right
now
we
have
a
number
of
projects
today
which
actually
related
to
user
experience,
for
example,
verification
all
the
configurations
and
supporting
Hamilton
tribulations,
because
right
now
it's
on
the
XML.
So
if
you
interest
to
contribute
to
this
area,
you're
also
welcome
to
do
that.
So
documenting
use
cases
for
the
10:00
sharp
it's
covering
issue.
Cases
which
a
mission
and
just
contributing
some
quotes
is
also
welcome.
A
B
So
Oh
like
are
there?
Are
there
ways
that
contributors?
So,
for
instance,
just
this
week,
we've
got
new
arrivals
on
the
user
experience
in
the
weekly
build.
Are
there
any
things
we
need
to
forewarn?
People
are
interested
in
testing.
Hey,
try
this
in
the
new
weekly
build,
so
they
just
be
looking
at
the
changelog.
What's
what
are
there's
a
very
specific
guidance?
We
should
offer
them
on
particularly
Jenkins
to
that
238.
A
A
Enhancements
there
so
rate
once
a
box,
blue
ones
and
transplants
and
approvals
improvements,
for
example,
style
their
help
button
a
number
of
Admissions
a
number
of
improvements
for
system
redesign.
So
you
can
find
such
areas
in
the
change
log.
This
is
one
of
the
ways
or
to
discover
issues.
Another
way
is
to
actually
go
to
the
Jenkins
roadmap
so
which
work
and
progress
roadmap.
Where
we
publish
like
key
and
going
stories
and,
for
example,
there
are
stories
which
I
likely
interest
to
hottest
participants.
A
For
example,
pipeline
is
llamo,
there
is
working
prototype
and
we
did
project
further.
There
is
those
projects
for
each
performance,
unification
for
local
improvements,
a
lot
of
projects
for
administration
and
also
some
other
projects
like
jinx
kubernetes,
separated
changes
for
various
docket
images.
So
if
you
want
to
try
something,
you
can
take
a
look
at
this
column,
but
I
guess
all
of
these
projects
would
benefit
from
some
user
experience,
testing
and
feedback
and
all
of
these
projects
available
for
trying
out,
at
least
in
some
sense,
for
recent
releases.
A
You
can
also
refer
to
the
Jenkins
blog
major
stories.
We
encourage
come
to
middle
school,
publish
their
stories
so,
for
example,
here
Windows
docker
images
general
availability,
so
we
have
just
released
it.
If
you
want
to
try
it
out,
if
you
using
windows
kubernetes
or
in
docker,
it's
definitely
something
you
could
try
out
renaming
cream
adjusts
also
help
identification
support
which
has
been
released
recently.
So
team
was
working
on
that
and
now
we
have
JSOC
student
working
on
follow
up
projects
like,
for
example,
integration
with
github
checks,
API
than,
for
example,
credentials
for
Asia,
etc.
A
So
if
you
just
go
through
this
list,
you
can
discover
a
lot
of
recent
stories
and
if
you
see
missing
features,
you
can
actually
write
about
them
because
an
Jenkins
we
have
around
40
to
50
releases
every
day
in
terms
o
Jenkins,
core
plugins
and
other
components,
and
most
likely
in
these
releases.
You
can
find
something
interesting
to
you.
A
Okay,
so
we
have
45
minutes
before
the
next
session.
I
would
like
to
thank
everyone
who
participated
in
this
call
and
who
is
watching
with
a
recording
have
a
great
week,
and
we
are
looking
forward
to
work
with
you
and
the
drink
is
project.
If
you
are
a
newcomer,
contributors
are
very
experienced
contribute.
We
hope
that
this
event,
it
will
be
a
great
experience
for
you
if
you
have
any
questions
after
the
event
again,
please
ask
indicator
chat
and
we
will
be
able
to
continue
the
discussions
there.