►
From YouTube: Jenkins Governance Meeting, Jun 16, 2021
Description
Jenkins governance meeting June 16, 2021, with topics including:
* Jenkins 2.289.2 release candidate now available
* Contributor Summit
* Deprecating Ruby runtime
* Jenkins funding - status report
* Plugin End-of-Life Policy
* Discourse evaluation status report
A
Welcome
everyone:
this
is
the
jenkins
governance
meeting
it's
june,
the
16th
2021
thanks
for
being
here,
we've
got
agenda
items,
including
news
contributor
summit,
deprecating,
ruby,
runtime,
jenkins
funding,
updates,
plug-in
end-of-life
policy.
Possibly
I
had
put
lfx
mentorship
budget,
but
I'm
not
sure
I've
got
anything
to
talk
to
it
and
discourse.
A
Okay,
great
and
let's
keep
it
brief
and
to
the
point
so
by
way
of
news,
contributor
summit
is
coming
june.
25
we'll
talk
about
it
in
more
depth.
Later
in
this
meeting
end
of
the
month,
we've
got
jenkins
2.289
coming
and
we've
switched
from
freenode
to
libra
for
our
in
irc
chat
system
and
the
discourse.
Proof
of
concept
is
ongoing.
B
C
B
C
B
I
know
I
know
at
least
some
people
love
these
who,
from
time
to
time,
go
to
rc
channel
to
ask
questions.
They
were
surprised
last
week
that
nobody
was
answering
questions
anymore
and
they
did
not
follow
all
the
drama
around
free
notes,
and
so
that's
what
I
mean
that
we
should
write
a
small
blog
post.
I
mean
it
doesn't
have
to
be
really
big.
Just
like
dubai.
Freeload
is
dead
and
we
are
moving.
C
A
B
I
think
that
would
be
nice.
I
remember
that
we
wanted
to
discuss
about
switching
from
rc
to
something
else.
I
think
the
first
move
was
first
to
leave
freenode
because
yeah
because
of
three
nodes.
Next
I
mean
we.
We
can
then
introduce
a
discussion
about
if
we
want
to
use
matrix
or
something
else
great,
but
yeah
at
least
for
now.
We
just
want
to
be
sure
that
we
need
three
nodes
and
everybody's
aware
of
that.
C
I
think
yeah
say
we've
left,
throwing
a
comment
saying:
there's
also
getter
and
there's
also
discourse
great.
Don't.
A
C
Yeah
I
mean
there's
not
a
lot
to
share
it's
going
pretty
well,
we
have,
I
don't
know
I
haven't
looked
recently
but
like
40
or
60
users
about
20
of
them
are
posting
stuff.
So
it's
pretty
good.
As
oleg
pointed
out
in
twitter,
I
really
like
the
show
off
category,
because
a
lot
of
people
are
posting
all
kinds
of
things
like
the
books.
They've
written
and
you
know
upcoming
plugins
tim
did
the
blue
ocean
thing.
A
B
Screen,
if
you,
if
you
want,
because
I
would
like
to
share
the
skill
you
bet
so,
if
you're
new
to
the
two
discussions
so
next
week,
we'll
have
a
contributor
submitted,
we
are
still
discussing
about
how
to
organize.
Today.
We
want
to
obviously
hide
that
some
major
change
in
the
jenkins
project.
I
mean
initiatives
that
are
running
right
now.
We
would
like
also
to
have
a
decision.
So
let
me
share
my
screen,
so
you
can
see
this
keyboard
first.
B
So
I
hope
you
can
see
the
screen
here
so
so
yeah
before
I
introduce
what
the
schedule
is,
so
we
would
like
to
cover
a
different
kind
of
aria.
We
would
like
to
highlight
project
update.
We
would
like
to
update
highlights
on
sig
updates.
We
also
want
to
take
this
opportunity
to
to
discuss
major
changes
that
we
want
to
bring
to
them
to
the
jenkins
projects.
B
That's
something
that
we
usually
do
during
the
contributor
summit,
and
we
would
also
like
to
save
some
space
for
highlighting
some
specific
work
like
on
a
specific
plugin
or
whatever.
Something
important
to
keep
in
mind
is
the
time
is
aligned
with
the
silicon
which
is
east
u.s
time
zone,
so
it
will
so.
B
I
created,
I
created
a
draft
for
the
day,
so
the
first
thing
is
obviously
because
the
amount
of
people
on
different
time
zone-
I
just
put
the
major
on
time
zone
so
just
to
help
you
identify
if
it's
possible
for
you
and
then
we
would
have
four
main
categories.
The
first
one
is
project
update.
As
I
said
here,
you
can
expect
update
from
board
members
officer
of
the
jenkins
project.
B
I
was
thinking
to
have
a
contributor
track.
Initially
my
understanding
was.
We
were
on
the
pdt
time
zone
so
with
west
coast,
which
was
a
little
bit
more
difficult
for
people
from
europe,
but
we
don't
have
that
constraint
anymore.
So
something
that
I
would
like
to
suggest
is.
We
first
do
the
project
update.
Then
we
do
the
sig
updates
and
then
we
continue
with
the
contributor
track.
So
we
have
more
people
from
everywhere
in
the
u.s.
B
B
What
I
need
right
now
is
to
finalize
the
the
schedule,
so
I'm
really
looking
for
feedback
on
this
schedule
and
also
I'm
looking
for
people
to
either
talk
or
leave
discussion.
So,
for
instance,
in
the
case
of
the
project,
update
or
seek
update,
the
idea
is
to
have
someone
who
can
do
a
quick
update,
five
or
ten
minutes,
but
in
the
case
of
the
contributor
track.
B
The
idea
here
is
more
to
be
a
moderator
and
to
drive
a
discussion,
so
we
would
like
to
have
as
many
contributors
interested
by
those
specific
topics
of
those
plugins
those
topics
that
we
identify.
I
mean
you
can
still
change
those
topics,
but
one
of
them
is
plug-in
end-of-life
policy.
Several
people
bring,
I
mean
that
they
would
like
to
introduce
that's
a
policy
to
deprecate
some
plug-in,
and
I
think
that's
a
great
good.
I
mean
that's
a
good
place
to
discuss
about
that.
B
We
always
a
session
contributing
to
jenkins
mark
will
lead
that
session.
He
does
a
pretty
good
job
on
that
area.
Some
people
reported
that
they
would
like
to
discuss
about
how
to
upgrade
guava
in
jenkins.
I'm
not
a
java
developer,
so
I
cannot
go
too
much
into
the
details
there,
but
I
know
that
batismati,
but
batiste
was
interested
to
leave
that
discussion.
A
leg
requested
a
session
on
the
outreach
program
that
we
would
have
in
the
coming
months.
B
Instead,
something
that
I
have
to
identify.
If
someone
else
can
take
the
lead
on
this
one,
we
would
like
to
have
a
discussion
on
java,
11,
java,
8
and
obviously
java
17,
because
service
java
17
will
be
the
new
test
java
test
release
in
september.
B
So
if
you
are
interested
by
that
topic
feel
free
to
manifest
yourself
and
finally,
another
session
that
I
would
like
that
I
would
like
to
cover
is
governance,
because
we
will
have
governance
in
around
october
and
november.
That
would
be
the
third
time
that
we
organized
the
election
on
the
jenkins
project.
B
We
organized
two
times
following
two
different
processes
with
different
kind
of
results,
and
so
I
would
like
to
go
back
in
time
to
understand
what
we
did
well
and
what
we
want
to
change
based
on
our
last
two
attempts.
So
those
are
the
contributor
track.
B
If
you
have
any
other
topic,
you
want
to
bring
feel
free
to
manifest
yourself.
You
still
have
one
week
to
change.
Sig
updates,
I'm
still
trying
to
identify
people
to
do
to
do
an
update
here,
I'm
trying
to
convince
and
try
to
find
a
way
for
people
from
asia
to
particip
to
participate
as
well.
A
B
Okay
good
to
know
thanks
question
for
you
olovich
and
giving
if
you
have
a
specific
topic
that
you
want
to
cover
during
the
contributor
summit
yeah
to
manifest.
We
also
have
to
work
on
the
slide
for
the
project
update
and
the
seed
updates
yeah.
I
myself
can't
participate
because
I
have
lectures
the
whole
day
and
that's
yeah.
Almost
this
the
whole
time
slot
is
during
my
lectures.
B
So
I'm
sorry
that
I
can't
help
here.
At
least
yeah
speak.
That's
fine!
I
mean
there
are
always
some
it's
also
6
a.m.
For
me,
it's
all
right.
A
Two
either
way,
I'm
not.
B
Okay
good
to
know
as
well
yeah,
that's
I
just
needed
your
confirmation.
Otherwise
we
have
another
google
doc.
Do
I
have
a
link
to
this
one?
Let
me
see
if
I
can
find
it.
B
So
I'm
also
looking
for
feedback
on
this
one.
So
I'm
going
to
put
the
link
to
the
agenda.
B
B
If
you
have
some
ideas
for
the
unconference
part,
so
that's
a
small
presentation
on
jenkins
or
no
people
who
would
be
interested
to
participate.
I'm
looking
for
speakers
in
the
last
session,
so
right
now
we
have
I'm
looking
for
jenkins
and
tecton,
inter
into
our
interoperability,
I've.
I
got
confirmation
that
we
can
have
a
session
on
jenkins
and
jenkins63
jenkins
and
the
open,
telemetry
plugin
and
the
work
done
by
elastic
and
yeah.
I'm
looking
for
more
topic
here.
A
D
I'm
eastern
time
so
I'm
usually
up
at
five
o'clock
in
the
morning
to
feed
my
cats.
So
time
is
not
really
a
problem.
A
A
Excellent.
Thank
you
very
much.
Any
other
topics
we
need.
Let's
see
a
draft
email
invitation,
email
has
been
posted,
olivier
gave
some
feedback
there
suggesting
we
should
use
discourse
as
the
contact
point
I'll,
create
a
new
topic
under
the
contributing
on
discourse
and
invite
people
to
reply
there.
So
that
way,
we'll
try
to
motivate
them
if
they
have
some
issue
when
they
receive
the
invitation,
email
they'll
go
to
the
discourse
community
and
post
their
question.
There.
B
So
yeah,
that's
that's
one
of
the
things
that
still
needs
to
be
done,
and
another
discussion
which
is
happening
at
the
moment
is
how
we
manage
the
swipe
and
how
we
send
the
swipe.
So
I
think
we
still
have
an
open
question
on
who
will
pay
for
the
swag
and
how
much
we
have
to
pay.
Obviously,
it's
difficult
to
know
in
advance
how
many
swag
we
want
to
send
but
yeah
we,
I
don't
have
the
answer
at
the
moment,
I'm
just
sharing
that
we
are
discussing
with
alissa
and
the
cdf
and
other
people.
A
No,
that's
all
for
me
at
least
for
now.
Okay,
the
deprecating
ruby
run
time,
I'm
not
sure,
there's
anything
we
need
to
report
there.
We
had
an
item
for
daniel
to
continue
reviewing
it
to
review
it.
I
assume
that
I've
not
seen
anything
indicating
that's
been
reviewed,
so
I
think
we're
still
on
hold
there
jenkins
funding
updates.
As
far
as
I
understand
it,
gavin
and
evelina
both
have
access
to
the
to
the
funding
system.
So
that's
in
progress,
nothing
other
that
I
need
to
report
unless
someone
else
has
something
they
need
to
report.
A
Okay,
great
and
I
understand-
we've
got
plug-in
end-of-life
policy
as
a
topic
for
the
contributor
summit.
I
don't
think
there's
anything
more.
We
need
to
discuss
here
except
being
aware
that
it'll
be
a
topic
at
contributor
summit.
Prepare
ourselves,
be
sure,
we're
ready
to
discuss
and
have
good
plans.
A
This
is
continuous
delivery,
if
you,
if
you
don't,
have
to
download
it
every
five
minutes,
it's
dead.
Okay!
A
A
B
Great
people
can
register
an
icon,
can
ask
questions
can
participate.
We
already
saw
nice
demo
in
the
show
off
section
that
garrett
created
a
garrett
giving
created
sorry,
so
I
think
it's
working
well.
The
only
thing
that
we
may
do
you
may
have
is
more
option
like
being
able
to
use
twitter
to
authenticate
or
whatever
that's
something
that
we
can
improve
in
the
future,
but
for
now
I
think
we
already
have
something
working
pretty
well.
C
C
I
only
got
one
in
the
last
year,
so
I
the
more
options
we
have
for
social
logins,
the
probably
the
better
I'm
going
to
send
out
another
blast
old
email
list
next
week,
probably
maybe
a
week
after
I
want
to
make
sure
that
people
have
time
to
not
get
it
too
often,
and
then
I've
been
talking
to
advocacy,
sig
ux
sig,
and
what
did
I
say,
the
other
one
was
oh
and
mark
was
talking
about
doc,
sig
about
possibly
moving
the
majority
of
their
communication
to
discourse
so
try
it.
C
Out
so
I
don't
know
how
much
we're
going
to
do
that,
but
I
oh
okay,
that's
the
zoombi
having
the
dots
yeah,
I
don't
know
like
I
said
I
don't
know
if
they're
there
uli
said
ux
is
interested
but
and
mark
said
docs
is
interested.
We
haven't
moved
forward
to
any
of
them.
Yet.
A
B
A
B
So
when
you
arrive,
when
you
arrive
on
community
that
changes
that
io,
that's
usually
the
view
that
you
see
you
have
I
mean
you,
you
see
the
active
discussions,
something
that
we
we
started
to
try
to
understand.
How
we
do
is
the
categories,
so
we
can
organize
discussion
by
categories.
B
It's
still
I
mean
we
still
have
to
improve,
but
for
us
what
we
thought
was
to
have
one
major
category
with
champions
using
jenkins
community
contributing
providing
feedback
on
the
site
feedback,
and
we
also
have
specific
categories
for
language
groups,
espanol,
french
and
so
on,
and
so,
for
instance,
if
you
go
to
contributing
you,
we
could
add
a
subcategory
so
right
now
we
only
have
in
the
subcategories
infrastructure
and
g-stock.
B
So
let's
say
we
could
imagine
ux
if,
if
you
want
and
then
when
you
create
a
new
topic,
you
just
start
a
discussion
and
then
can
specify
the
different
categories
that
you
want
to
have.
So
you
can
only,
for
instance,
specify
the
top
category,
which
is
contributing
you
could
specify
contributing
infrastructure
and
the
way
it
works
is
as
a
user.
You
can
have
filters,
you
can
say,
I'm
only
interested
by
topic
in
infrastructure
under
contributing,
and
so
it's
really
easy
to
identify
what
you
want
to
read.
Basically,
so
that's
that's
how
it's
working
right
now.
B
Does
it
answer
your
question
about
having
a
ux
category,
so
the
the
the
biggest
challenge
that
we
have
at
the
moment
is
to
have
enough
categories.
So
we
can
organize
discussion,
but
not
too
much
so
people
are
lost
in
the
different
categories
because
you
can
have
level
one
categories,
then
you
can
have
level
two
categories
and
level
three
and
so
on.
You
don't
really
have
a
limit.
B
It's
just
like
level,
one
and
level
two
is
really
easy
to
see
from
here,
because
the
top
level
is
the
the
big
box
using
jenkins
community
contributing
the
level.
2
is,
let's
say,
infrastructure,
gsoc
announcement.
Even
so
those
are
the
blue
box
that
you
see
and
then
level
3
categories.
It's
a
little
bit
harder
to
identify.
C
Oh,
no,
sorry,
no
olivier!
We
have
the
calendar
enabled.
So
when
you
create
your
events
for
the
contributing
assignment,
you
should
make
sure
that
there,
the
post
has
a
date
set
to
it,
the
hamburger
at
the
top
right.
Okay,
that
way,
it'll
show
up
in
calendar,
so
we
can
start
seeing
events
that
are
happening
around
as
well.
C
B
B
You
is
this
course
only
available
in
the
browser
it's
they
have
like.
B
C
So
I've
been
looking,
I
mean
we
can
create
a
new,
a
new,
actually
a
new
wikitalking
topic
where
people
can
add
clients
and
tooling
their
views.
So
that
might
be
not
a
good
idea
as
well.
C
B
B
D
D
B
A
Yeah,
I
think
I
think
we
would
want
a
larger,
larger
group
and
and
a
more
detailed
review
yeah
that
that
how
about
we
propose
that
asynchronously
is
you're,
worried
that
the
roadmap
may
be
outdated
as
published
to
jenkins.io,
because
we
reviewed
it
two
or
three
weeks
ago
in
in
governance,
okay,
so
yeah.
I
have
to
double
check.
So
maybe.