►
From YouTube: Jenkins Governance Meeting Jan 12, 2022
Description
Jenkins governance meeting from January 12, 2022. See the meeting notes for topics.
A
The
cloud
welcome
to
jenkins
governance
meeting
it's
the
12th
of
january
2022..
Oh
sorry,
daniel!
Yes,
I
should
have
should
have
had
you
there
thanks
all
right,
so
topics
on
the
agenda.
I've
got
the
today
news
end
of
your
blog
post
draft
just
for
information's
sake.
Administrative
access,
don't
know!
If
we'll
have
that
topic
much
more
to
do
on
it,
google,
summer
of
code,
shecodeafrica
contributon
and
highlights
from
the
mailing
lists
any
other
topics
that
you
need
to
add.
A
B
A
A
B
B
B
With
my
new
role,
I
expect
to
be
able
to
push
more
automation,
more
simpler
process,
different
rules
for
different
things,
to
to
simplify
a
bit
the
work,
because,
honestly,
as
a
newbie
coming
there,
I
don't
want
to
have
the
job
it's
so
complicated,
so
so
complex
in
general.
It's
something
that
has
to
be
simplified.
Otherwise
I
will
be
officer
for
for
life,
because
I
accepted
by
by
chance
I
will
say
or
not,
but
yeah
that's
a
bit
the
issue
there.
B
We
have
to
simplify
a
bit,
they
think
for
us,
but
also
for
the
different
people
being
involved
with
photo
being
voluntarily
involved.
I
will
say,
because
they
are
just
maintaining
a
plugin
that
need
to
be
also
simplified
for
them,
and
we
got
a
great
support
from
the
afra
team
for
the
different
configuration
stabilization
in
general,
so
that
was
great
in
term
of
content.
B
That's
interesting
to
have
seen
one
core
change:
that's
not
really
impacting
a
lot
of
people,
it's
mainly
for
people
without
the
security
room
being
configured
in
the
sense.
If
you
run
it
only
for
your
local
network,
we
don't
expect
anyone
with
a
team
or
a
company
using
that
no
security
run
approach,
so
not
a
big
impact,
but
if
you're
in
that
situation,
it's
pretty
big
impact,
I
would
say
otherwise,
multiple
plug-in.
I
think
we
got.
B
I
don't
remember
exactly
more
than
10
plugin
in
total,
it's
just
a
lot
of
plugins
with
at
least
three
high
vulnerabilities
that
were
corrected
and
also
around
10
plugins
that
were
not
corrected,
so
mainly
unmaintained
plugin.
We
have
they
publish
some
of
the
plugin
as
well,
so
trying
to
clear
a
bit.
The
list
of
plugins
and
that's
all
for
the
news
I
will
say
thanks.
B
A
Well,
thank
you
for
doing
it
thanks
very
much
to
you
and
to
daniel
both.
Thank
you.
Thank
you
to
the
security
team.
I
I
appreciate
gavin's
note
here.
We
we
did
have
infra
issues
and,
and
it's
it's
correct.
We
had
to
do
some
issues,
some
fixes
or
some
workarounds
for
things
that
ultimately
we
want
to
solve,
and-
and
so
thanks
very
much
to
the
infra
team,
also.
C
C
A
B
Yes,
sorry
thank
you.
Mark
forever
mentioned
that,
but
yeah
huge
thank
you
for
danielle.
Actually,
we
spent
eighty
percent
of
the
day
together,
so
I
completely
forgot
that
we
did
that
with
what
to
say
that
I
was
thinking
about
the
afra
team
in
particular,
but
yeah
daniel
was
the
necessary
mentor
during
these
trips
or
thank
you,
daniel.
A
Thanks
very
much
all
right,
so
next
topic
or
any
other
news
items.
Oh
yes,
I
take
it
back.
We
had
one
we
sort
of
got
passed.
Preview
sites
are
now
available
on
www.jenkins.io
pull
requests.
That
means
you
in
order
to
review
how
a
pull
request
looks
you
no
longer
have
to
actually
run
the
site
yourself
locally,
thanks
very,
very
much
to
gavin
for
his
his
effort
on
that.
A
Yeah,
it
is
it's
a
it's
a
thing
of
beauty
I
am,
I
am
so
pleased
with
it
and
yeah
thanks
very,
very
much
so
examples
like
okay,
guess
what
here's
a
pull
request
and
take
this
pull
request,
and
now
I
can
see
a
okay.
This
is
a
terrible
horrible
thing
to
see
all
these
changes
and
how
do
I
know
how
they
look
well
view
deployment
takes
me
to
this
site,
and
I
say
yes,
there
we
are,
and
now
I've
got
the
full
site
ready
to
go
and
ready
to
look
around
to
see.
A
A
A
Yeah,
sorry,
so
that
end
of
your
blog
post
has
has
been
a
working
copy
started
and
suggestions
have
been
received
on
the
mailing
list.
Thanks
very
much
for
those
suggestions,
if
you
have
others,
please
include
them.
I'm
sorry
that
I'm
a
little
slow
getting
it
generated
in
previous
years.
We
had
it
done
pretty
consistently
by
the
10th
day
of
the
new
year
this
this
year.
It
may
be
end
of
this
week
before
I'm
done
with
it
I'll
look
for
reviews
and
comments.
A
It
will
be
at
least
another
day
before
I
submit
a
a
pull
request
with
it,
and
thanks
very
much
for
everyone's
help.
The
exercise
of
reviewing
2021
reminded
me
just
how
many
things
happened
in
2021
for
the
jenkins
project
and
how
many
impressive
outcomes
we've
had
as
a
result
of
work
done
by
various
people
in
the
community.
Thanks.
A
A
A
So
we
also
we
started
the
planning
in
doc's
office
hours
and
we'll
do
more
discussions
in
a
wider
location
on
community.jenkins.io
in
upcoming
time,
so
that
we
can
get
project
ideas.
We
can
get
assure
that
we've
got
good
sponsorship,
whether
we'll
be
looking
for
some
funding
to
to
do
it
not
from
the
jenkins
project
but
from
commercial
companies.
So
we
think
cloudbees
will
fund
and
there
may
be
others
who
want
to
fund
as
well.
A
C
A
Yeah,
exactly
that's
and
that's
a
good
one
for
us
to
remind
people
of
we
don't
want
to
put
someone
into
a
condition
where
they're
volunteering
to
mentor
and
then
realize,
and
they
have
to
do
it
in
the
middle
of
their
night
or
the
wee
hours
of
their
morning.
Good
point
because
some
of
us
sleep-
I
mean
not
you
and
me,
but
some
people
here,
sleep.
A
Oh
yes,
right
right
exactly
january
22.
Thank
you
very
much.
We
should
note
that
2022
january
22
2022
is
the
removal
of
jruby
and
jython
based
plugins
from
update
center
right.
That's
what
we've
announced
announced
a
month
announced
you
at
end
of
december
2021
and
in
first
implementation
happened
to
mark
them
as
deprecated.
I
think
in
early
january,
and
I
think
it
was
literally
the
last
day
of
the
year,
but
it
was
about.
C
A
C
A
C
A
D
A
D
C
A
Right,
so
the
other
is,
if
we
look
just,
let's
take
one
other
sample
just
to
be
sure
yes,
cappy
tomcat,
whatever
it
is,
is
deprecated
good
all
right.
So
so
we
do
still
have
the
change
that
will
need
to
be
need
to
happen.
As
announced
january
22
and
daniel,
you
said,
that's
just
a
change
from
one
file
to
another
to
say.
Instead
of
just
warning,
it's
we're
going
to
stop
distribution
completely
right,
so
we
cut
and
paste.
A
A
For
your
info,
oracle
has
declared
that
their
premier
support
for
java
8
ends
in
march
of
2022,
but
extended
support
goes
until
2030
and
red
hat
says:
they'll
support
java
8
until
may
of
2026.
So
it's
not
that
we're
really
in
any
risk
of
having
java
itself
not
be
supported
by
the
vendors,
but
there
is
clearly
a
horizon
where
oracle
is
saying
hey.
This
is
changing
modes
for
us
in
march
of
2022.
D
So
one
thing
I
don't
know
whether
I
send
it
to
the
dev
list
as
well,
but
it
would
be
useful
for
us
to
decide
whether
we
want
to
adapt
our
usual
process
in
some
manner
here
or
whether
we
just
treat
it
as
any
other
enhancement.
We
merge
it
at
some
point
and
it
ends
up
in
in
lts
within
the
next
quarter
or
so
to
better
understand.
You
know
what
the
what
the
impact
is
for
exa
as
an
example
right
we
might
decide,
and
I'm
absolutely
not
advocating
for
this
just
to
be
clear.
D
Let's
keep
supporting
the
last
java
8
compatible
lts
line
for
longer
than
the
usual
three
months,
so
that
users
on
java
8
get
more
time
to
upgrade
their
java
version,
which
I
don't
think
we
should
do.
But
it
would
be
an
additional
argument
to
say
yeah
if
you're
on
java
8,
you
just
keep
using
that
line
and
work
on
the
migration
some
other
time,
and
we
can
just
integrate
it
into
whatever
weekly
release.
We
want,
because
it's
not
as
jarring
as
an
experience
to
upgrade
as
an
example.
D
A
A
A
Ui
modernization
is
continuing
and
you
can
see
it
already
in
jenkins.
2.330
includes
many
changes
more
to
come,
see
the
pull
requests
for
the
changes,
the
changes
that
are
happening
daniel.
I
I
saw,
for
instance,
that
you
had
given
some
good
feedback
to
jan
on
us,
some
specific
topics
and
it
to
me
it
looks
very
encouraging
that
we're
making
progress
there.
D
We
also
have
a
regression
fix
ready
for
the
narrow
configuration
forms.
Oh
that's
right
that
that
one's
a
bit
fun
because
change
log
feedback
indicates
that
the
narrower
configuration
forms
are
so
bad
that
people
had
to
downgrade
again,
which
I
cannot
quite
believe.
But
that's
what
the
weather
report
in
the
changelog
says.
So
we
have
a
regression
fix
for
that
ready
and
it
will
go
into
the
next
weekly.
So
that
would
be
233.
A
C
It
would
be
nice
to
see.
I
mean
this
is
something
daniel
who
goes
or
mark
who
goes
to
every
meeting
ever.
It
might
be
nice
to
see
some
of
this
kind
of
announcements
in
the
form
a
bit
more,
not
something
we
need
like
a
formal
blog
post
for,
but
a
bit
more
screenshots
to
see.
What's
coming,
you
know
always.
I
know
we're
not
getting
a
lot
of
feedback
on
pr's
from
external
people,
but
the
more
we
do
it.
The
more
people
will
see
them
the
more
they'll.
C
B
C
Are
coming,
we
would
like
feedback,
maybe
some
links
to
some
pr
just
so
that
people,
if
they're
curious,
can
see
it.
And
then
you
know
if
anyone
outside
of
the
meetings
is
interested,
they
can
share
it
on
social
media
if
they
want,
but
I
don't
think
we
should
spend
a
lot
of
effort
doing
it.
I
just
want
to
give
people
the
opportunity
who
don't
follow
every
pr
good.
A
C
A
C
Finished
the
marriage
yesterday,
people
are
some
of
the
infant
team.
Members
have
gotten
a
lot
of
emails.
I
assume
you
have
as
well
mark,
but,
yes,
yeah,
a
lot
of
emails
that
got
all
got
migrated
over.
I
think
people
are
generally
pretty
happy
in
both
cases
that
you
can
have
the
new
forms.
The
new
github
issue
form.
So
we
can
be
a
lot
more
pushy
on
what
fields
get
filled
out
and
how.
A
Yeah
so
working
well
now
we
still
have
to
we.
We
don't
do
security
issues
through
github
right,
and
so
that's
that
still
continues.
The
pattern
we've
had
in
the
past
that
security
issues
go
through
jira
because
we
can
keep
them
private,
but
general
intra
issues
hey
this
or
that
issue
github
issue
forms
are
actually
easier
and
more
accessible
for
many
of
our
users.
A
D
A
A
C
A
C
A
C
Tim
has
also
migrated
the
hosting
repo
to
github.
The
good
thing
about
that
is,
it's
now
fully
user,
what's
called
retriggerable.
So
in
the
past,
whenever
there's
issues
with
hosting
requests
and
we
had
to
wait,
someone
had
to
trigger
the
bot
and
then
you
know
you
make
a
change.
You
trigger
the
bot
again
and
all
that
is
now
done
to
github
actions
and-
and
you
know,
with
the
forums
and
the
drop-downs,
and
they
make
sure
that
people
have
jira
accounts
and
artifactory
accounts
before
we
even
attempt
to
start
the
hosting
process.
C
So
you
know
there
are
a
couple
minor
changes
there,
but
it's
a
lot
easier
to
integrate
and
deploy
and
a
lot
less
copy
and
pasting
everywhere.
So
we
haven't
had
any
new
hosting
requests.
We've
had
a
couple:
what
is
it,
what
are
they
called
they're
moving
something
out
of
core
splitting
off,
like
so
just
some
libraries
that
got
spit
off
they're,
not
really
new
plugins,
so
there's
nothing
such
yeah
right.
So
nothing
really
new
testing.
C
All
the
new
flow
so
we'll
have
to
see
how
that
goes
with
like
regular
new
people,
but
it
seems
to
work
better
mostly
for
the
common
integration,
and
I
do
have
like
six
hosting
requests
that
I'm
way
behind
on
that.
I
gotta
finish
reviewing
and
get
out
the
door,
and
then
we
can
move
everything
into
github.
C
D
A
This
report
and
issue
page
that's
available-
gives
me
a
way
to
report
a
bug
and
it
will
go
to
github
if
the
plugin
is
using
github
or
it
will
go
to
jira
to
report
a
security
issue
and-
and
that
page
is
for
me,
has
been
just
a
great
benefit
of
okay.
This,
if
you
want
to
report
a
security
issue,
click
this
button
and
it
will
take
you
to
the
right
place
to
do
it.
Yeah
very
good
point
also.