►
From YouTube: Jenkins Governance Meeting, Nov 04, 2020
Description
At this Jenkins Governance Meeting we discussed the recent news and Jenkins releases. Then we discussed the 2020 elections status, search on jenkins.io, and the Kubernetes Operator open governance proposal status. Full agenda and meeting notes: https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.v4sls9rnbtoa
A
A
So
we
have
a
few
topics
in
the
agenda
today.
I
will
firstly
start
from
news
and
vegas:
I'm
going
to
events
in
the
junkies
community
and
we
will
talk
about
jenkins
selections.
Mark
has
an
update
about
pfa
video.
I
have
an
update
about
trademark,
which
we
know
update.
We
will
get
there
and
also
we
wanted
to
quickly
discuss,
search
for
jenkins
io
and
our
options
there.
A
Okay,
let's
start
from
the
beginning,
so
for
jenkins
selections,
we
have
announced
2020
board
and
officer
candidates,
so
you
can
find
at
least
on
the
website.
There
was
a
separate
announcement
about
that.
You
can
see
that
there
are
nine
candidates
for
governance
board.
You
have
two
positions
after
election,
so
if
you
want
to
support
any
particular
candidate
now
it's
a
great
time
to
actually
register
so
that
you
participate
in
the
elections
starting
next
week.
So
there
is
a
big
red
register
button
here.
A
You
can
also
find
ways
to
register
here
in
the
bottom
and
we
will
also
have
elections
for
the
jenkins
release
officer.
We
have
three
candidates
at
the
moment
for
the
rest
of
the
officers.
After
the
initial
discussions
with
the
nominated
contributors,
we
ended
up
with
only
one
contributor
running
for
the
elections,
what
it
means
that
there
may
have
been
more
contributors,
but
then
they
decided
not
to
compete
in
the
elections.
And
finally,
we
got
four
uncontested
officers,
so
elections
will
happen
on
the
photo
positions.
A
A
B
2.249.3
released
today,
it's
it's
a
relatively
small
update
compared
to
2.249.2
two
regressions
fixed
and
one
additional
fix.
We've
released,
2.264
with
the
tables
to
divs
implementation,
and
we've
got
some
additional
upcoming.
Bold
changes
coming,
oh
and
plug
in
security
release.
Good
observation,
yeah,
yeah,.
A
B
A
A
B
So,
where
jenkins
has
used
for
many
many
years,
an
old
version
of
a
security
framework
that
we're
now
upgrading
to
replace,
with
current
version
of
spring
boot
security
and
very
grateful
to
jesse
glick
for
doing
that,
work
he's
doing
that
work
through
a
jenkins
enhancement
proposal
and
it's
looking
like
within
the
next
one
or
two.
Maybe
three
three
weeklies.
We
should
have
that
in
it
won't
be
visible
to
users
of
the
lts
until
march
of
2021,
most
likely.
A
Yeah
and
this
change
includes
incompatible
modifications
in
api
in
apis,
so
there
is
ongoing
fixing
for
plugins
and
the
user.
Software
cs
may
actually
get
the
versions
with
updated
plugins,
but
it
should
shouldn't
impact
the
behavior
according
to
the
jabs,
so
yeah
in
ideal
situation.
There
should
be
no
impact.
A
Yeah,
there
is
a
lot
of
other
changes
happening
here
and
there,
but
it's
nice
to
see
that
we
clean
up
the
technical
depth
in
our
dependencies,
because
each
of
these
dependencies
have
been
a
huge
money
maintenance
button
for
us.
So
once
we
get
them
over
the
line,
we
will
be
able
to
adopt
new
dependencies
which
have
been
blocked
and
also
we
won't
need
to
care
about.
Okay,
about
maintaining
our
forks.
B
A
A
A
B
A
A
I
guess
that's
all
these
action
items
we
had
before
I
had
a
quick
update
regarding
web
search
for
junkie
scion,
I'm
not
sure
whether
it's
the
best
venue,
I
will
just
summarize,
with
the
discovery
status
so
yeah.
As
you
know,
we
don't
have
search
engines.
I
o
one
of
the
reasons
is
so
that
they
have
concerns
about
using
any
particular
research
engine
because
of
vendors
need
tradition
and
because
of
data
collection.
A
A
B
A
A
B
C
A
D
A
A
A
Well,
I
wanted
to
do
it
for
a
long
time
and
yeah,
since
there
is
a
lot
of
user
feedback
coming
from
the
lack
of
search
and
actually
the
prototype,
I
was
doing
it
was
able
to
collect
from
multiple
subdomains.
So,
for
example,
the
same
search
was
working
for
the
plug-in
site
and
also
for
for
the
main
site
and
just
for
fun
for
jenkins.
It's
the
way
I
yeah
I'm
not
sure
whether
they
will
be
able
to
reproduce
that,
but
it
has
some
advantages
so
for
plug
for
login
index.
A
A
A
Okay,
so
this
one
so
again,
yeah
the
public
conversation
here
is
just
the
tip
of
the
of
the
iceberg,
because
there
was
a
lot
of
various
background
discussions,
so
it
started
from
heart
to
making
a
proposal
for
open
governance
of
the
junk
separator
project.
So
the
reason
that
the
previous
maintainers
have
to
show
up.
A
My
name
is,
after
that
one
of
jenkins
support
members
alexa
into
connection
item
to
reach
out
to
the
first
up
director
and
alex.
Did
it
and
we
got
a
response
after
more
than
one
month
of
waiting
and
pinion.
That
yeah,
but
I
will
just
stop
you'll,
be-
would
be
interested
to
continue
in
the
open
source
and
that
they
intend
to
respond.
A
So
the
search
update
from
alex
was
on
october
october
21st.
So
almost
two
weeks,
and
since
that
we
received
no
communication
from
different
stuff,
so
I
think
we
have
to
think
again,
but
ultimately
it
will
brings
us
to
the
issue
what
we
do
with
this
project,
because
there
we
spent
two
months
without
any
clear
progress
and
yeah.
This
is
definitely
a
good
tip
to
discuss
today.
D
A
So
we
discussed
multiple
options
in
august,
because
our
main
preference
remains
that
you
make
sure
that
the
current
upstream
works.
Fine.
We
have
an
option
of
creating
a
new
upstream,
especially
if
there
are
breaking
changes,
because
at
some
point
the
red
hat
team
made
a
proposal
about
the
jenkins
separate
roadmap.
Just
a
second
I'll
change.
The
screen
again.
A
A
D
Yes,
sorry
to
interrupt
about
this
point
like
because
we
have
discussed
all
already
all
the
options,
and
I
remember
that
my
own
opinion
was
to
to
indeed
move
to
to
another
fork
and
create
our
own
version,
but
it
has
been
decided.
I
mean
at
red
hat
level
with
product
management,
and
so
on
that
we
prefer
to
remain
with
the
single
community
of
users,
and
so
this
is
what
led
us
to
propose
a
new
governance
model
which
is
more
open
source
compatible,
so
yeah.
D
Changing
this
direction
will
be
also
a
huge
effort
for
us
right
now
and
so
yeah.
We
have
to
find
a
solution
which
is
suitable
for
maintaining
the
community
and,
at
the
same
time,
like
the
project
being
not
active
for
several
months.
That's
completely
normal
that
there
is
some
changes
in
terms
of
compatibility
and
that
we
cannot
maintain
the
same
feature
such
long,
especially
that
apis
were
on
alpha
stage,
which
means,
as
an
operator
perspective,
that
being
alpha.
D
D
A
A
Okay,
I
apologize
that
it
takes
so
long
but
yeah.
Ultimately,
we
cannot
get
a
response
and
yeah
at
some
point.
We
will
need
to
think
what
we
do,
because
with
the
assumption.
So
if
we
don't
get
a
response,
neither
from
thomas
who
is
officially
maintainer
as
far
as
the
jenkins
project
concern
or
from
victor
schwab,
which
is
the
fact
that
the
sponsoring
company
for
the
current
upstream
then
yeah
the
in
the
jenkins
project.
A
We
have
a
few
options,
but
ultimately
we
don't
have
a
process
of
transparent
definitions.
When
maintainer
is
actively
against
transferring
permissions,
so
then
yeah
it
will
be
a
tricky
situation
and
I
think
that
finally
we'll
end
up
voting
at
the
governance
meeting
but
yeah.
I
think
that
taking
the
delays
it's
this
way,
it
becomes
more
and
more
probable.
A
B
I
think
I
think
that
sounds
reasonable,
so
it
seemed
that
your
your
position,
your
strong
desire,
is
to
retain
the
current
artifact
id
and
thus
the
current
community,
and
therefore
you
would
need
to
be
allowed
to
take
maintainership
of
that
repository
co-maintaining
with
vertus
or
soul
maintainership
for
a
new
set
of
maintainers
right.
I
think
that's
what
you're
describing.
D
Yes,
that's
that's
what
has
been
I
mean
requested
by
the
global
red
hat
team
when
we
discussed
this
project,
so
we
still
want
an
open
governance
model.
We
want
to
maintain
the
same
artifact
idea
so
called
artifact,
because
it's
an
operator
it's
right
and
we
want
to
to
just
be
able
to
federate
the
existing
community
and
support
them.