►
From YouTube: Closing Session
Description
Closing session of the Jenkins Contributor Summit, June 25, 2021.
A
A
Just
some
patience
there
is:
there
are
not
that
many
slides.
So,
first
of
all,
thanks
to
everyone
who
contributed
and
who
stayed
until
the
end
yeah,
it
was
almost
six
hours
by
now
and
yeah.
It
was
quite
a
packed
agenda
so,
but
I
think
that
it
worked
pretty
well
because
yeah
there
were
a
lot
of
discussions.
We
had
a
really
active
state
of
the
union
session
next
time
you
should
maybe
make
it
even
faster
and
user
friendly.
A
B
I
was
delighted
with
it.
We
had
a
relatively
small
group,
three
presenters,
five,
six
and
seven
participants,
and
we
talked
about
topics
that
were
interesting
to
them,
thanks
very
much
to
them
for
being
involved.
It
was
a
great
thing,
I
think,
we're
going
to
get
some
plug-ins
adopted
as
a
result,
and
I
know
we're
getting
more
help
from
some
people
who
are
wanting
to
be
more
involved
thanks.
B
A
Great
yeah,
currently
we
have
contributing
to
jenkins
playlist
on
jenkins
youtube
channel,
so
you
can
find
it
there.
I
won't
spend
time
right
now
to
find
it
but
yeah.
I
believe
that
mark
will
put
recordings
there
as
well,
so
that
you
can
take
a
look
and
there
are
already
a
lot
of
recordings
from
previous
sessions.
A
So
thanks
a
lot
for
driving
with
mark
also
yeah.
I
think
that
breakout
sessions
were
pretty
good.
I
jumped
into
almost
every
session
they
were
nice
discussions.
There
were
some
action
items
so,
for
example,
for
terminology
update.
It
was
really
a
nice
discussion.
The
github
actions
was
awesome.
Yeah,
I'm
just
looking
for
repeating
is
a
jenkins
online
meetup,
maybe
with
hundreds
of
participants
cloud
events,
integration
was
pretty
good
as
well.
A
Another
separator
was
brought
up
in
telemetry
again
they
had
a
great
discussion
between
basically
junkies
and
junk
and
sex
communities
here
so
again,
some
hard
joint
experience
with
visualization
completely
and
others
so
plugging
into
that
live
policy
that
we
even
have
a
planner.
So
last,
when
I
was
leaving
this
session
last
time,
they
were
driving
a
kind
of
decision,
three,
how
we
actually
decide
whether
plugin
is
inactive
or
not,
which
is
a
quite
a
challenging
question.
A
So
I'm
looking
forward
to
it
being
adopted
as
a
kind
of
jab,
because
it
was
a
struggle
for
us
for
a
long
time.
We
made
at
least
three
attempts
to
standardize
it
and
always
failed
and
yeah.
It
takes
one
interoperability,
junkie,
section
all
of
them
your
good
discussions
for
java
11,
maybe
james
or
summarize
it,
because
I
failed
to
visit
this
session
or
james
left.
B
Offline
well
or
oleg,
if
you'd
like,
I,
can
give
a
brief
summary:
oh
yeah
yeah,
let's
go
ahead
so
java
11
was
discussed
in
depth.
Looking
at
alternatives,
including
hey,
should
we
drop
support
for
java
8?
We
were
really
grateful
to
have
some
some
users
attending
with
us,
marcel
and
and
jonathan,
and
it
worked
very,
very
well
for
us
to
have
those
users
there
to
assist
and
discuss
outlined
a
rough
plan.
We
think
is
appropriately
conservative
and
looks
still
forward
to
the
future.
B
B
A
So
thanks
to
all
participants
of
these
sessions
and
thanks
to
all
hosts-
because
hopefully
it
helped
us
to
push
the
projects
forward,
ignite
talks-
and
that
was
here,
which
was
just
well
again
a
fun
time,
and
I
hope
it
was
also
a
learning
experience
thanks
to
hashi,
thanks
to
ernest
for
great
presentations,
yeah
again
areas,
I'm
looking
forward
to
to
see
the
full
presentation,
maybe
even
a
solutions
page
about
jenkins
for
date
of
science
and
life
science,
because
yeah,
I
know
that
you've
written
a
lot
of
blogs,
so
maybe
it's
time
to
aggregate
them
and
yeah
for
how
yeah
looking
forward
to
jsokjamas
and
thanks
a
lot
for
working
on
your
project
and
yeah.
A
Currently
we
are
closing
down,
so
we
are
going
going
slightly
over
time,
but,
yes,
I
believe
that
it's
still
using
reasonable
limits
so
for
feedback.
First
of
all,
we
have
discourse
channel.
Oh
it
works,
so
rank
is
contributor
summit
feedback.
So
if
you
want
to
discuss
it
in
this
course,
here's
a
channel
for
you
or
several
topics
so
just
put
your
feedback
here
register
it's
just
the
registration
through
github
and
then
you
can
post
a
comment.
A
A
So
if
you
want
to
get
them
there
is
a
feedback
form.
Please
fill
it
out,
it's
actually
not
a
huge
deal,
so
there
is
only
one
required
question:
how
was
the
event
all
the
rest
is
optional,
but
we
will
appreciate
feedback
and
yeah
if
you
reach
the
end
spoiler
left
for
those
who
are
here,
you
can
actually
order
a
t-shirt,
so
this
feedback
form
is
anonymous,
but
the
t-shirt
black
form
is
not
anomalous
because
we
need
shipping
address
and
all
other
kinds
of
personal
data,
so
we
are
by
filling
it
out.
A
We
agree
with
us
storing
this
personal
data
for
some
time
before
lisa
sends
t-shirts,
and
then
we
will
delete
it.
So
we
do
not
store
this
information,
we
don't
send
spam,
etc
and
yeah
again
any
feedback
will
be
appreciated
and,
as
I
said
before,
we
intend
to
do
the
next
event
in
asian
and
pacific
time
zone
so
ready
for
the
next
summit
there.
There
are
three
yes
answers.
A
Please
choose
one,
you
prefer
okay,
so
yeah,
that's
the
plan,
and
yes
thanks
to
cloudbees
for
sponsoring
t-shirts,
I
believe
there
will
be
stickers
and
other
things
we
using
jenkins
is
the
way
but
yeah
again,
if
you
want
to
contribute
artwork
for
the
next
summit.
You're
welcome
to
do
so.
We
will
appreciate
that
okay,
so
for
moderators.
A
A
So,
for
example,
here
presentations
we
had
quite
a
lot
of
presentation
and,
for
example,
migrating
plugin
docs,
just
first
random
one.
So
here
you
can
find
the
guidance
and
the
recording
references,
etc.
So,
something
like
that
and
it's
available
as
code.
If
you
want
to
mark
down
it's
one
of
the
ways
another
way
just
to
put
them
on
this
course
again
with
all
the
links
as
you
prefer,
but
we
will
appreciate
if
you
could
post
these
sessions
and
for
recordings,
how
to
do
that,
you
can
post
them.
A
For
example,
on
your
google
drive,
make
it
public
and
then
mark,
or
maybe
somebody
else
from
youtube
managers.
They
will
publish
them,
process
them
and
make
them
available
to
everyone,
and
then
we
will
be
able
to
use
our
social
media
sets
with
promote
events,
because
we've
had
a
lot
of
great
demos.
We
definitely
should
promote,
for
example,
github
actions.
The
conversation
was
awesome:
great
demos,
angelic
batiste
for
go
up,
update,
et
cetera,
et
cetera.
A
So
there
is
a
lot
of
great
content
to
share
and
why
not
and
spread
the
word
so
whatever
twitter
linkedin
community
junkies,
it's
much
appreciated
again.
Jenkins
community
needs
more
contributors
and
needs
more
users,
and
doing
promotion
is
one
of
the
ways
to
get
that
if
it's
related
to
particular
decisions.
If
you
can
use
special
interest
book
managers,
the
developer
managers,
for
example,
for
jabs
et
cetera,
we
still
expect
it
to
happen
in
million
keys
so
for
unfortunate
discussions.
Community
jenkins
io
is
fine
for
formal
decision
making.
A
We
can
be
asked
to
use
medicals
at
the
moment
and
external
communities,
for
example,
technology
ability,
cloud
events
open
telemetry.
Please
use
this
external
channels
as
well,
because
again,
working
together
with
other
communities
is
our
opportunity.
So
why
not
jenkins
shouldn't
be
just
a
lockdown
in
its
own
community?
That's
why
we
started
working
with
foundations
talking
to
end
users
etc,
because
we
should
be
more
open,
and
I
hope
that
we
will
make
agencies
the
great
place
to
contribute
for
everyone.
A
Even
if
you
don't
try
to
code
and
yeah
as
event
officer,
I
invite
everyone
to
think
about
doing
combined
meetup,
especially
for
those
who
did
user
facing
sessions
or
developer
facing
sessions,
because
we
do
developer
meetups
well,
because
yeah
jinx
online
meetup
is
another
platform
for
us
to
promote
events.
And
if
you
have
a
talk
while
not
presenting
that
okay
and
yeah
also
apply
to
one
of
the
next
conferences,
but
yeah
devops
fault
call
for
papers
is
over.
Maybe
we'll
have
contributor
summit
there.
A
Maybe
we'll
have
something
for
you
for
users,
but
it's
to
be
determined.
So
at
the
moment,
jinx
line
meetup
is
actually
the
best
opportunity.