►
From YouTube: Jenkins Governance Meeting Nov 17, 2021
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Welcome
to
jenkins
governance
meeting
it's
the
17th
of
november
2021
remind
everyone
that
we
abide
by
the
jenkins
code
of
conduct,
so
be
nice
to
each
other
agenda.
Topics
that
I
had
include
news.
Election
status
report
and
gavin
will
put
you
on
that.
One
highlight
from
the
mailing
list
and
community
forum
anything
else
that
needs
to
be
on
the
list.
A
Oh
actually,
I
wanted
to
thank
you
for
creating
the
draft
draft
agenda.
It
made
my
life
much
better
by
what
you
did
so
thanks.
Very
much
gavin
also
wasn't
me,
but
thank
you.
Oh
whoever
created
it
that
it's
really
marvelous
that
we've
got
it
college
is
now
here
super.
So
news.
An
election
status
report
and
mailing
list
highlights
were
the
three
topics
I
had
oleg
any
topics
that
need
to
be
added
to
the
agenda.
C
So
yeah
sorry,
I
have
been
a
bit
disconnected
over
the
past
weeks.
The
last
time
we
yeah.
We
had
some
discussions
related
to
ownership,
but
it
was
brought
up
to
the
infrastructure
team
yesterday.
C
So
I'm
not
sure
whether
it
makes
sense
to
discuss
it
today
until
we
get
some
clear
details
from
the
linux
foundation
about
what
they
actually
expect.
C
So
this
is
a
the
story
about,
so
the
linux
foundation
would
like
to
have
the
admin
github
account
registered
as
an
owner
for
all
project
representatives
and
organizations.
A
A
Okay
and
so
news
2.321
has
released
with
new
table
layout
very
attractive.
It's
looking
really
good,
actually
and
a
new
plug-in
manager,
some
plug-in
manager,
layout
improvements
and
fixes
to
a
number
of
regressions
that
had
crept
into
2.320.
A
thanks
very
much
to
jan
farachik
and
to
tim
jacom
for
their
work
there
and
uli
hoffner.
It's
it's.
It's
really
pretty
cool
to
see
what's
happening
in
in
the
jenkins
ui.
A
The
2.319.1
release
candidate
has
arrived.
It
needs
deeper
testing,
I
think
than
usual,
because
it's
got
six
back
ports
that
were
six
different
poles
changes
that
were
back
ported
and
has
some
some
thing.
Major
improvements
like
the
inclusive
naming
changes
that
we've
got
to
be
sure
we
get
into
the
upgrade
guide
and
well
described
in
the
change
log
kathy
chan
is
a
release
lead.
This
is
her
first
time
doing
a
release
lead.
She
is
in
the
same
team
that
works.
B
We
debated
whether
how
much
information
we
want
to
share
publicly,
but
I
think
we
can
safely
say
we
have
about
40
er.
So
we
have
about
50
of
the
registered
voters.
Voters
have
now
read:
let's
try
that
again.
50
of
the
registered
voters
have
now
voted,
so
we
we
still
have
another.
What
two
weeks
for
everyone
to
vote.
So
we
should
be
nudging
probably
again
to
remind
people
to
vote
this
year.
Was
there
was
a
snag
that
we
have?
You
have
to
activate
your
email
with
concordia
for
grpc
reasons.
B
A
B
Yeah,
I
am
I'm
only
peripherally
on
the
election
stuff,
so
we
can
bring
it
up
with
olivier
if
you
want,
but
considering
the
next
meetings
two
weeks
away,
I
can
nudge
them,
but
I
think
we'll
stick
with
traditional
methods.
I
don't
know.
A
B
A
C
Well,
I
don't
have
much
to
share,
so
there
is
a
kind
of
abstract
request
with
quite
clear
justification
that,
in
the
event
that
current
maintainers
means
become
unavailable,
linux
foundation
would
like
to
have
an
opportunity
to
take
over
the
repositories
so
that
the
projects
could
continue,
which
is
generally
a
good
safeguard,
and
this
linux
foundation
cncfr
do
for
all
important
projects,
but
yeah
engines
also
onboard
it.
C
It
wasn't
done
for
jenkins
and
now
it's
a
kind
of
reasonable
question,
but
we
want
to
have
such
recovery
plan
b,
especially
since
we
have
a
lot
of
confidential
information,
including
unreleased
security
fixes
some
private
repositories
and
jenkins,
and
of
course,
if
we
give
owner
access
to
github
organization
to
account
with
unknown
number
of
users
having
access
to
that.
Basically,
it
means
that
any
of
these
users
can
potentially
exploit
our
continuous
delivery
pipelines
and
release
something
just
by
direct
push,
for
example,
so
security
wise
there
are
concerns.
C
C
A
A
They
felt
like
hey,
let's
go
ahead
and
put
them
in
the
triage
team,
even
if
they
don't
have
a
signed
contin
signed
cla,
because
the
permissions
are
so
light
on
the
triage
team,
no
real
risk
there
and
we
hadn't
previously
mandated
it
now.
When
we
in
some
future
day
promote
them
to
become
copy
editors,
then
they
must
have
a
cla.
So
so
it
would
be
good
for
us
to
get
the
easy
cla
implemented,
but
it's
not
a
it's,
not
an
urgent
or
emergency
kind
of
thing.
A
C
A
And
I
think
I
think
we
had
plus
ones
all
around
for
yes,
it
was
okay
to
go
ahead.
Had
it
been
discussed,
I
thought
it
had
been
discussed
in
the
dev
list.
Do
you
feel
like
there
needs
to
be
more
discussion?
Are
you
looking
for
more
plus
ones,
or
no?
It's
just
okay.
On
my
to-do
list,
perfect
great.
All
right
next
topic
was
end-of-life
plan
for
java
8..
Olivier
lami
had
noted
that
jetty
9.4
9.4
will
end
of
life
in
the
next
one
to
two
years
and
that's.
C
A
A
Right
right,
no
shock
at
all
right:
it's
it's
they've
already
got
jetty
10
and
jetty
11,
so
no
no
surprise
that
they
would
eventually
stop
supporting
9.4.
A
When
that
happens,
that
would
be
very,
very
significant
to
jenkins,
because
that's
that's
where
wins
winston
depends
on
that
right
so,
and
jetty,
10
and
jetty
11
do
not
support
java
8.
A
C
A
And
so
the
the
current
warnings
are
not
are
not
an
official
deprecation,
but
they
are,
they
are
there
are
current
warnings,
and
so
your
notion,
the
question
was:
shall
we
explicitly
declare
java?
8
is
deprecated
with
some
targeted
end
of
life
date.
C
C
Plus
we
still
have
a
related
question,
but
you
would
like
to
allow
plugin
maintainers
to
release
java
11,
plus
only
plugins,
because
we
have
all
the
support
inside
the
jenkins
code
for
that
and
inside
update
centers.
We
just
need
to
make
a
call
and
allow
to
release
java
11
only
plugins,
but
obviously
for
java
8
users.
It
will
cause
some
options
most
likely
they
will
be
sharing
non-core
tools,
for
example,
plugin
installation
manager
for
sure,
or
maybe
other
tools
to
line
continuity
directly.
C
A
Right,
good,
good
insight,
so,
and
I
don't
I'm
in
terms
of
gavin,
I
think
you
highlighted
for
us
in
our
last
session.
This
section
of
this
meeting
is
really
noting
things
where
the
board
does
not
define
these
things
and
is
not
necessarily
responsible
for
them.
The
community
will
choose,
choose
that,
probably
based
on
an
eventual
proposing
some
some
plan
of
action.
A
A
B
Yes,
so
prototyping
is
going
decently.
We
can
read
all
the
teams
relatively
quickly.
I
think
we
figured
it
was
less
than
a
minute
to
read
all
the
teams
and
all
the
members.
B
The
next
steps
would
be
kind
of
defining
a
format,
there's
some
debate
right
now,
because
the
rpu
was
designed
for
one
purpose
and
it's
slowly
migrating
for
another
purpose,
and
that
means
some
of
the
schemes
are
a
little
schema
is
a
little
bit
confusing.
B
B
B
So
research
is
coming
along.
I
think
it'll
be
a
positive
win.
C
B
Yeah,
I
kind
of
don't
care
about
those.
I'm
only
doing
teams
and
all
repositories
have
access
or
should
have
access
by
teams.
B
So
I'm
not
going
to
manage
the
individual
republic
or
contributors,
I'm
just
going
to
be
managing
the
team
so
that
people
get
invited
properly
and
everything
like
that
and
teams
are
a
lot
easier
to
get
data
back
out
because
any
for
we
have
a
json
file
that
lists
every
user
and
what
teams,
what
repository
they
have
access
to
and
the
mins
just
can't
be
listed
there
because
technically
they
get
returned
for
every
repo.
B
So
the
teams
fix
that
by
having
a
very
concrete
this
team.
Has
this
users
ignoring
and
made
or
not
admitted
it's
just.
These
teams
have
these
members,
so
I
think
we're
going
to
stick
with
teams
and
then
we
don't
have
those
nearly
as
many
edge
cases
and
at
least
to
start.
I
don't
intend
to
delete
anyone
from
them.
B
Members
yeah
and
then
we
can
get
a
report
of
what
you
need
to
be
deleted.
I
don't
really
sure
we
have
even
the
bot.
I
don't
think
the
bot
can
remove
members
either.
So
you
know
at
this
point
we
can
only
add
them,
and
then
you
know
if
that
works
well
and
smooth,
then
we
can
start
having
it
be
the
source
of
truth.
So
the
team
members
get
added
removed
from
this,
but
that's
a
longer
project,
but
I
think
doing
it
as
teams
makes
it
very
clean
and
neat.
A
Last
item
was
just
a
word
of
note
that
fosdem
is
going
to
be
virtual
this
year,
so
the
fosdem
conference
in
brussels
will
happen
in
february,
and
olivia
vernon
had
stated
that
he
plans
to
assist
with
others
in
again
having
a
ci
cd
dev
room.
C
For
me,
yeah,
I
might
have
some
topic
for
the
next
governance
meeting,
but
yeah
right
now,
I'm
still
a
kind
of
onboarding
part
of
my
new
job.
You
know
my
personal
stuff.
A
B
A
B
Meeting
will
be
with
the
new
board
or
do
does
that.
We
usually
wait
another
week
or
two,
oh
okay,
next
week,
we'll.
C
Be
with
the
results
preview,
I
guess
so
effective
date
for
the
new
birthday
is
december
3rd
as
listed
okay.
So
basically
he
will
have
both
members
elect
or
something
like
that,
because
by
this
time
the
poll
will
be
closed.
You'll
get
the
immediate
results.
With
this
steps,
though
there
will
be
some
period
way.
People
basically
can
do
last
considerations,
but
yeah
thinking
the
number
of
candidates
yeah.
I
don't
think
that
there
is
much
things
to
consider.