►
From YouTube: Jenkins UI/UX Hackfest - Results
Description
This session concludes the Jenkins UI/UX Hackfest. It will happen on June 01, 2PM UTC. Thanks to everyone who contributed to the project during this event, we have delivered a number of important changes which will help Jenkins users!
At this session we will celebrate the key results and achievements, events statistics and the data we have collected during the event. We will also talk about the next steps (swag, feedback, etc.).The session will be held in Zoom Webinar. RSVP to get a link.
References:
* Main Hackfest page: https://www.jenkins.io/events/online-hackfest/2020-uiux/
* List of contributors: https://github.com/jenkinsci/ui-ux-hackfest-2020#contributors
A
Okay
and
we
are
being
recorded
so
welcome
to
the
you,
a
hot
chest
and
welcome
to
the
last
meeting
called
aux
harvest.
So
today
is
June
1st
and
we'll
also
summarize
a
key
achievement
of
the
project,
talk
about
them
and
talk
about
what's
next
for
the
project,
so
let's
say
the
main
objective-
and
this
is
just
a
summary
call,
so
we
will
be
publishing
the
recording.
A
Okay,
so
first
of
all,
I
would
like
to
thank
all
the
contributors
thanks
for
your
participation
during
the
event.
In
total,
the
53
contributors,
as
you
may
imagine,
I
could
have
put
names
on
this
slide.
But
if
you
want
to
see
more
details,
that
is
a
link
about
you
can
find
actually
all
the
information
and
links
so
now
you're
a
hot
website.
So
you
can
find
more
details
here.
We
are
still
processing
late
reports
for
the
contributions.
So
when
we
the
final
number
yeah,
it
may
change
a
bit
but
yeah
anyway.
A
We
got
a
really
good
number
of
contributions
and
thanks
to
everyone
who
participated
so
yeah,
we've
got
a
lot
of
people
working
in
documentation
on
New,
York,
States
and
from
watching
Jenkins
and
all
sunshiny
Bible
stories.
So
it
was
amazing
for
one
we
went
during
the
working
week.
So
thanks
to
everyone
who
was
able
to
dedicate
some
time
and
help
us
to
move
the
Jenkins
forward
and
thanks
to
the
work
team
and
special
interest
groups
who
this
went
to
happen.
A
So
it
was
a
lot
of
overtime,
work,
a
lot
of
late
night
fixes
and
reviews
to
keep
this
event
going.
So
it's
a
much
appreciated
and
thanks
and
of
course
thanks
our
sponsors,
which
part
and
with
prizes
for
the
events
you
wrote
about
the
wait
time,
but
again,
thanks
to
everyone
who
contributed
to
this
event,
that's
from
sometime
and
discuss
at
the
highlight
you
Fred,
so
first
track
we
had
is
about
user
enter.
So
if
you
see
this
slide,
it's
not
a
definitely
a
reference
user
interface,
but
it's
just
quick
summary.
A
So
what
we
have
got
Union
base
hot
fast.
So,
first
of
all,
we
had
to
don't
legend
creation,
preview,
release
and
emotions,
but
creatures
just
your
testability
testing.
There
we've
released
the
preview
of
the
dark
theme
and
there
were
many
improvements
in
various
components
like
credentials,
management,
plug-in
script,
security,
Jenkins
code
and
many
other
components.
A
So
there
should
be
no
links
to
the
demos,
as
you
may
see,
I
forgot
to
put
it
on
the
slides,
but
I
can
show
you
how
to
find
it.
So
you
think
they
went
through
using
things
online
it
up
in
order
to
record
all
these
sessions.
We've
had
and
we're
recording
today's
session
as
well,
and
if
you
want
to
find
a
recording
of
the
sudden,
you
can
just
go
here
and
you
can
find
all
the
sessions
here.
If
this
list
is
too
big
for
you,
you
can
also
go
to
the
jinkies
value
X
harvest.
A
A
Just
but
thanks
to
everyone
who
presented
their
demos,
I
will
just
show
a
number
of
key
stories
but
yeah.
There
is
also
a
lot
of
improvements
and
then
later
we
will
be
following
up
with
a
blog
post
with
a
full
list
of
contributions,
so
the
whole
story,
as
we
said,
redundant
configuration
so
now
it's
available,
so
everyone
who
manages
Genesis
code
now
you
can
switch
your
configuration,
the
read-only
mode,
so
that
you
can
endure
patiently
change
the
settings
and
we
will
keep
working
that
in
order
to
make
more
thickness
ability.
A
Analytic,
analytics
tools
available
for
read-only
administers
another
achievement.
We
had
Jenkins
dog
team,
so
we
started
basically
from
now
where
the
number
of
teams,
but
we
created
a
new
one,
shut
out
contributors
and
especially
two
teams
at
home
who
was
driving
this
project.
So
now
we
have
an
adduct
team
in
preview
right
now
that
is
Jenkins
weekly
release,
which
is
going
to
be
released.
A
Maybe
in
a
few
hours
starting
from
this
release,
this
preview
will
be
official,
but
even
now
you
can
try
it
out
on
your
instances
and
if
you
watch
it,
the
reporting
tool
definitely
variable.
So
it
wasn't
just
taking
over
new
dog
team,
it's
basically
the
considering
how
Jenkins
say
he
makes
this
extensibility
works,
we
switch
the
drink,
is
called
CSS
variables,
so
now
themes
to
take
just
dozens
of
wine.
A
So
definitions
instead
of
hundreds
of
ions
like
they
used
to
be
before,
and
we
also
spend
a
lot
of
time
on
the
york's
testing
capability
and
the
ability
tested
for
this
theme.
So,
for
example,
if
you
go
to
the
repository
and
discover
a
lot
of
reported
issues-
and
this
is
just
issues
which
haven't
been
fixed,
yet
my
issues
have
been
fixed
during
the
hot
fest
and
if
you
interested
to
contribute
you're
welcome,
so
this
will
be
released
just
a
few
hours
after
this
recording.
A
The
next
thing
we
worked
on
was
mutation
of
a
user
entered
of
configuration,
user
interface
from
our
tables
to
DS,
so
it
improves
visualization
of
screen,
especially
on
mobile
devices.
Jaws
just
makes
it
look
better
for
configuration
pages.
This
feature
hasn't
been
in
integrated
yet,
but
we
are
working
on
that
and
again
we
invite
all
contributors
to
participate,
but
still
the
you
know
this
hard
test.
We
did
some
testing,
and
now
they
have
confidence
about
this
change
and
hopefully
we'll
be
able
to
integrate
that
human
needs,
or
maybe
in
no
month.
A
A
There
you
can
manage
approvals,
you
can
define
them.
You
can
see
usages
of
script
approvals
and
management.
So
it's
a
major
improvements,
improvement
for
Jenkins
admins
who
allow
custom
scripting
from
the
Bay
instances.
What
else
ad?
For
example,
there
was
improvement
in
Auto,
gradient,
plugin
viola
Hafner.
Now
it
supports
accelerator
schemes,
so
many
reports,
many
static
analysis
reports
and
summary
pages
now,
even
more
sensible
than
they
were
before.
A
That's
it
regarding
features
again.
This
list
is
not
fooled.
We
were
still
working
on
particular
cases
and
Yerkes
I
mentioned
some
names,
but
in
general
we
had
more
than
30
contributors,
so
working
on
this
area.
So
thanks
to
everyone
who
helped
to
improve
Jenkins
visual
interface
and
to
deliver
improvements
in
plugins
and
let's
switch
to
the
documentation
recommendation
is
also
a
great
part
of
user
experience.
We
have
good
news
to.
B
B
What
I
wanted
to
highlight
was
that
we've
had
wonderful
contributions
to
the
user
documentation.
One
of
our
one
of
our
beginning
points
was
that
we
have
lots
of
information
that
is
in
the
Jenkins
wiki
that
would
be
better
suited
and
better
presented
if
we
moved
it
to
Jenkins
at
I/o,
and
we've
succeeded
in
moving
over
40
documentation
pages
from
the
wiki
to
Jenkins
at
I/o.
B
In
addition
to
that,
it's
now
actually
30
or
more
plugins
that
during
the
last
week,
advanced
their
motion
from
using
their
documentation
on
the
wiki
to
instead
putting
the
documentation
right
inside
their
github
repository,
so
that
it
can
be
managed
as
code.
We
love
that
transition,
both
the
wiki
and
transition
from
wiki
and
the
transition
from
wiki
a
for
plugins
to
documentation
as
code
for
plugins
excellent
result.
In
addition,
we
did
documentation
updates
using
various
sources
of
content.
The
doctor
solutions
page
has
been
improved.
B
The
many
sections
have
been
added
to
using
Jenkins
to
managing
Jenkins
and
a
substantial
improvement
to
the
Jenkins
system.
Property
list.
There's
a
summary
recording
available.
The
link
is
there,
and
what
I'd
like
to
highlight
further
is
some
additional
changes.
We
switched
to
using
github
issues
instead
of
using
the
JIRA
system
for
our
documentation
issues,
and
that
has
been
a
major
positive.
B
We
identified
a
number
of
issues
that
a
good
first
issues
and
new
contributors
picked
up
these
good
first
issues
and
and
did
great
work
with
them.
Six
of
the
eleven
open
good
first
issues
that
are
currently
open
in
our
issue
tracking
already
have
someone
working
the
issue:
great
progress,
nine
of
the
12
closed.
First
issues
were
closed
during
the
hackfest
just
last
week.
B
26
of
the
57
closed
issues
that
have
been
closed
in
the
lifetime
of
our
time
on
github
issues.
Whether
closed
last
week
during
the
hack,
fest
and
16
of
the
currently
open
pull
requests
are
from
hackfest,
so
we're
getting
great
results
by
using
github
issues
and
great
results
from
contributors.
Like
you,
thanks
very
much
now,
there's
still
more
to
be
done.
We
have
over
200
pages
on
the
wiki
that
need
to
be
migrated.
We've
triaged,
roughly
one-third
of
those
and
need
more
people
to
help
us
triage
them.
B
The
triage
process
needs
someone
to
look
at
the
wiki
page,
decide
where
it
belongs
in
the
jenkins
documentation
set
and
then
to
create
an
issue
in
github
to
track
that,
so
we
need
more
reviewers
we're
looking
for
those
I'd
like
to
like
to
highlight
some
of
the
pages
that
that
have
come
as
a
result
of
last
week's
Hatf
at
hackfest.
So
first
thing
to
note:
thirty-six
pull
requests
were
merged
last
week
and
there
are
16
new
pull
requests
still
to
be
reviewed
in
the
managing
Jenkins
documentation.
We've
got
a
number
of
new
additions.
B
We've
got
additions
in
the
using
Jenkins,
including
using
local
language,
including
how
to
use
fingerprints,
including
how
do
you
reference
another
project,
page,
those
things
added
by
new
contributors
as
by
transferring
content
from
the
wiki
into
Jenkins
style,
thanks
very
very
much
now.
In
addition,
we're
grateful
that
Devon
Nussbaum
one
of
the
experts
on
pipeline
extracted
the
pipeline
CPS
method,
mismatches
documentation
from
the
wiki
and
placed
it
here
doing
a
serious
and
significant
rework
to
be
sure
that
it
was
current
and
correct.
So
the
wiki
transformation
process
is
not
just
copying
content.
B
It's
thinking
very
carefully
about
is
this.
The
correct
thing
to
say
is
this
current
and
accurate.
Similar
happened
for
the
Jenkins
CLI
and
we're
especially
grateful
to
daniel
back
for
his
work
on
jenkins
features
controlled
with
system
properties.
This
page
describes
many
of
the
properties
that
are
in
jenkins
that
are
control
by
very
various
special
flags,
and
it
helps
users
to
know
what
those
flags
are
so
that
if
they
have
to
control
something
they
can
well.
B
This
one
is
worth
noting
for
me,
because
Daniel
had
to
clean
up
a
mess
that
I
had
left
behind
and
he
did
a
brilliant
job
of
it
so
that,
when
I
hover
over
this
link,
it
just
works
when
I
click
links
here,
it
just
works
in
addition
to
the
benefit
of
what
he
did
there.
The
glossary
now
has
the
same
exact
capability,
so
I
can
point
to
one
of
the
terms
in
the
glossary
and
the
links,
work
and
layout
beautifully
special
thanks
to
Daniel
and
sorry
that
he
had
to
clean
up
my
messes.
B
It
was
wonderful
grateful
also
for
the
plug-in
migration
progress
that
over
400
plugins
have
now
migrated
to
documentation
is
code
and
there
are
PO
requests
pending
for
another
90,
plus
really
great
results
from
the
documentation
portion
of
the
one
week.
Long
hackfest
and
Oleg
I
think
that's
that
covers
mine.
Do
you
want
me
to
continue
showing
slides
or
do
you
want
to
take
the
control
back?
I
can
take
all
the.
A
Control.
Okay,
thank
you
for
the
summary
mark,
okay,
and
so
our
third
trick
was
spread
the
word.
Basically,
it
was
about
promoting
Jenkins
and
reporting
user
stories
and
we
actually
had
some.
So
do
you
like
the
hot
rest.
We
recorded
10
knowledge,
transfers
and
demo
sessions
for
urging
users
and
Jenkins
developers
I
would
represented
this
link.
You
can
find
the
recording
today
also
we
were
promoting
Shang
stories
on
changes
and
the
way
portal.
We
had.
A
So
just
let
me
show
you
this
comics
first,
so
thanks
a
lot
to
comic
strip
for
creating
rate
and
thanks
a
lot
for
everyone,
so
we
all
have
some
of
these
comics
soon.
Also
thanks
a
lot
for
your
posts,
I've
just
put
a
number
of
them
on
the
page.
They
work
more
so
thanks
to
everyone
who
said
they
experienced
from
the
hard-faced
experience
from
using
Jenkins
information
about
new
features,
it
helps
us
to
promote
the
project.
A
It
helps
us
talk
about
the
remote
contributors
and
finally,
it
helps
the
junkies
users,
because
the
project
gets
a
lot
more
features
and
visible
again.
So
thank
Co
and
we
appreciate
the
feedback.
So
let's
talk
a
bit
about
what's
next
for
the
hottest
participants
and
for
those
who
would
like
spittin
such
bands
in
the
future.
So
first
of
all,
we
said
that
there
would
be
spark
and
prizes
and
would
be
so.
We
are
Protestant.
The
hot
West
results
will
be
contacting.
A
The
participants
on
BT
shows
other
goodies,
we'll
be
distributing
soon
so
stay
tuned
and
we
have
your
contacts.
So
it
will
just
happen
in
a
few
weeks
because
we
still
need
to
finalize
some
details,
but
we
definitely
do
that
and
we
will
also
to
your
feedback
about
the
hot
fest
about
how
we
could
improve.
Again.
It
was
our
first
experience
of
doing
online
hottest
lag
red.
We
had
a
few
events
before,
but
they
rather
focused
on
a
particular
topic,
or
they
were
part
of
October
1st
or
the
wider
events.
A
So,
if
you
would
like
your
insides,
please
fill
in
the
feedback
form.
This
feedback
is
full
anonymous
and
we
what
shape
any
suggestions
and
about
what
we
could
do
better
and,
of
course,
if
you
have
something
positive
to
share
about
your
experience
or
something
prequel
to
the
post,
it
would
be
also
much
appreciate
because
we
could
use
of
this
information
for
the
future.
Hopefully
it
won't
be
our
last
event
of
such
kind.
We
have
already
started
discussing
having
events,
so
your
feedback
would
be
very
appreciated.
A
I
will
share
links
later
in
the
email
to
all
the
contributors,
but
if
you
want
you
can
find
it
here
and
after
Damon
we
invite
you
to
keep
contributing
so
hot
first,
it
was
just
an
event,
but
a
giant
his
project
is
open
24/7
any
day
any
time
of
the
week.
We
appreciate
your
contributors.
We
have
documentation
which
describes
how
to
contribute.
For
example,
if
you
want
to
code,
if
you
want
to
help
use
the
permutation
on
this
design,
you
have
some
stories
for
you.
A
If
you
want
to
help
use
infrastructure
and
other
things,
we
also
have
some
documentation.
So
we
will
appreciate
any
kind
of
your
contributions
to
the
project
and
we
invite
you
to
keep
contributing
to
the
aging
project
type
of
event.
There
are
some
programs
happening
now,
for
example,
there
is
a
boo
boo
season
of
dogs
for
those
who
are
interested
in
documentation,
and
they
will
be
other
events
for
hikers
Oktoberfest
in
October
and
maybe
the
organize
more
events.
A
But
if
you
see
a
mission
Jenkins
in
box,
your
user
experience,
if
you
want
to
contribute
to
fixing
that
mod
by
writing
code
but
just
helping
to
plan
this
issue,
I've
been
helping
to
find
proper
solutions
or
to
facilitate
contributions
to
this
survey.
We
were
to
shade
that
and
if
you
need
any
help,
if
you
can't
find
a
way
to
want
to
build
the
right
channels,
ones
from
new
comer
contributors,
another
one
for
you
not
focusing
and
not
VHT.
A
The
am
so,
for
example,
as
a
way
I've
got
50
500
contributors,
and
this
number
keeps
rising.
So
thanks
to
everyone
who
helps
to
implement
these
finishes,
reviews
review,
which
is
the
deliver
them
and
the
same
formation,
so
that
we
can
help
users
to
use
all
the
same
fishes
we
deserve
than
the
project
thanks.
Oh
okay,
are
they
any
questions.
B
A
A
B
I
was
truly
impressed.
A
number
of
the
new
contributors
chose
issues
that
I
thought
and
actually
had
described
as
hey.
This
is
more
challenging
topic,
they
picked
them
and
they
started
working
on
them
and
they
made
great
progress.
It
was,
it
was
quite
surprising
to
me
I
thought.
Oh,
this
is
going
to
be
a
very
hard
issue.
No
way
will
we
get
progress
on
this
during
the
hack,
fist
and
I
was
wrong.
We
got
really
interesting
progress
on
some.
A
A
Jenkins
share
its
a
internal
theme
you
create
for
your
company.
You
will
be
able
to
benefit
from
this
story
and
there
are
already
follow-up
developments
so,
for
example,
team
J
Tom.
He
started
working
on
a
better
way
to
select
themes
and
to
get
them
adopted,
including
user-defined
things.
So
here's
a
jank
issue
that
would
be
able
to
choose
themes
without
asking
your
demeanor
to
change
everything
globally.
There
was
some
experience
with
marketplaces
with
discoverability
of
the
plugins,
so
there
is
a
lot
of
stories
which
will
still
happen
or
have
already
started
happening.
Also
yeah.
A
A
Iced
tea
means
Indian
Standard
Time,
so
it's
definitely
something
you
would
provide
as
a
kid
back
in
the
feedback
form
so
yeah.
We
just
think
everything
in
UTC.
There
are
online
time
converters,
but
we
didn't
use
them
on
the
website
because,
for
example,
indications
of
fat,
for
example,
if
you
go
to
online
Meetup
I
ate
seven
more
challenging
than
just
UTC,
because
so
they
need
help.
A
Would
you
like
it
in
London
time,
which
is
UTC
plus
one
at
the
moment,
and
we
want
people
who
do
located
in
London,
sometimes
confused
so,
but
unfortunately
we
can't
easily
change
that
without
changing
the
platform.
At
the
same
time,
we
could
change,
make
it
better
on
our
side
because
of
our
services.
So
if
you
see
things
like
that,
please
just
share
that
and
you
take
it
back
home.
A
Okay,
if
not
we'll
just
processor,
this
recording
publish
it
online
and
after
that,
a
realist
artists
working
with
other
contributors,
synchronously
to
get
more
information
and
to
publish
summaries.
I
have
already
start
working
on
a
blog
post
for
your
improvements,
this
much
to
start
working
on
a
book
post
for
documentation.
There's
always
it
will
take
a
while,
but
we'll
do
that
and
stick
and
publish.
B
A
C
Yes,
just
wanted
to
father's
as
well
just
wanted
to
thank
you
again,
Aliyah
and
Mark
for
organizing
this
in
perfect
manner,
I
guess
so
allowing
everybody,
including
newcomers,
to
contribute
in
any
possible
way.
To
this
event,
it
was
nicely
organized
and
I
hope
that
you
will
have
very
good
results
for
everybody.
Just
on
a
quick
note-
and
this
is
I-
guess
more
related
to
mark
our
results
of
this-
a
quest
guild
to
be
somehow
considered
for
google
seasonal
Doc's
application,
assignations
and/or,
it
separately.
B
So
if
I
understand
google
seasonal
darhk's
correctly,
one
of
the
ways
that
they
assess
participation
is
active
participation
in
things
like
this
so
and
my
expectation
is
that
this
would
be.
Contributions
to
this
would
be
considered
valuable
and
viewed
positively
as
part
of
the
evaluation
process
for
google
season
of
dogs.
Now
Oleg's
got
more
experience
in
this
field
than
I.
Do
all
like
your
comments.
Yeah.
A
B
A
So
you
know
if
anyone
is
interested
to
contribute
to
the
and
spent
a
bit
more
time
with
the
jenkees
project
working
on
documentation,
you're
welcome
to
join
Google
Docs
program
and
you
will
see
what
will
be
the
number
of
contributors
applying
because
yeah
Google
seasonal
Docs
has
limited
number
of
slots,
but
we
still
have
other
options
like
community
breach,
like
maybe
hosting
another
program.
So
if
you're
interested
in
documentation
and
the
jenkees
project,
please
contact
us
and
let's
see
what
we
can
do
there.
A
A
B
I
may
have
frozen
Oleg.
Can
you
still
hear
me
yes,
I
kind
of
but
yeah
you
definitely
okay,
so
so
the
documentation
contributions
are
welcomed
and
encouraged
go
to
Jenkins
dot
IO
and
you
can
see
on
the
contribute
page
on
the
participate
page.
There's
a
documentation
link
there.
It
gives
a
number
of
places
and
ways
that
you
could
help
documentation
and
they
include
things
like
revisions
to
existing
pages
migration
of
wiki
pages,
converting
plugins
from
using
wiki
to
using
github
as
their
documentation
source,
all
sorts
of
different
ways
that
you
can
contribute
to
documentation.
A
Basically,
you
welcome
any
kind
of
contribution.
Interactive
digital
Jenkins,
just
I
think
what
is
missing
under
the
commutation.
Try
to
improve
that.
If
you
are
looking
for
something
new
newcomer
herstory
this
way
you
can
basically
find
their
different
tickets
and
I
guess
we
still
need
to
put
a
link
to
Jane,
say
you're
here,
but
I
mean
to
be
capricious,
but
the
in
general.
You
can
find
all
the
information
here
right.
B
A
Okay,
I'll
probably
still
stop
the
recording
and
see
you
again,
junkets
online
meetups
or
other
events,
so
the
next
online
meetup
is
scheduled
to
Thursday.
It
will
be
a
story
about
beautifying
builds
with
Captain
and
Jenkins.
So
if
you
interested
in
coordinated
environments,
please
feel
free
to
join
us
today,
bye
for
now,
thanks
all
bye.