►
From YouTube: Jenkins Governance Meeting September 5, 2022
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
A
A
Okay,
then,
let's,
let's
go
ahead
so
in
terms
of
news,
the
lts
comes
out
wednesday,
thanks
to
so
many
people,
who've
done
so
much
to
get
us
ready
for
this.
That
will
be
the
release
that
the
first
long-term
support
release
that
no
longer
includes
java
8
support,
thanks
to
chris
stern,
as
the
release
lead
and
thanks
very
much
to
basel
and
to
others.
Who've
done
an
amazing
amount
of
work
to
get
it
there.
A
A
I
think
that
is
an
increase
good,
so
the
funds
may
actually
have
arrived
now
very
good.
All
right
thanks
that
one
is
resolved.
A
Okay,
doc
sig
mailing.
This
transition
not
started
yet
probably
won't
happen
until
october,
at
the
earliest,
possibly
november,
a
blog
post
for
contributor
summit,
I'm
prone
to
just
drop
it.
Given
my
inability
to
get
this
one
done,
we've
got
so
many
other
things
happening
any
objections.
If
I
dropped
this
one
didn't.
A
A
All
right
and
I've
still
got
the
action
item
to
request
full
access
to
the
cdf
zoom
account.
This
is
one
of
two
different
paths.
We
could
take
right
well,.
B
A
Right,
that's
that
all
the
action
items
I'm
aware
of
next
topic
was
plug-in
adoption
process
clarifications.
There
are
two
pull
requests
open.
One
is
this
clarification
submitted
by
tim
jacom
to
update
the
document
to
state
what
what
I
think
is
a
natural
way
to
do
things.
A
B
C
This
this
isn't
only
natural,
because
otherwise,
that
timeout
would
be
quite
I
mean
it's
a
pointless
time-out,
because
no
one
can
make
it
any
shorter
than
what
it
is,
but
I
mean
in
general
it's
a
good
idea
to
codify
this,
this
implicit
knowledge,
because
then
we
can
refer
to
it
later.
If
we,
if
we
want
to
make
changes
to
it.
So
I'm
I'm
very
much
in
favor
of
codifying
these
implicit
processes.
C
The
only
the
only
piece
of
feedback
that
I
would
give
is
as
we
codify
them.
It
would
be
nice
to
include
the
rationale
for
each
piece
that
we
codify,
because
often,
if
you're
going
back
in
the
future
and
looking
back
at
these
decisions,
we'll
we'll
sometimes
want
to
ask
our
past
cells
not
only
what
we
codified,
but
why
we
codified
it,
which
is
going
to
be
obvious
to
us
today,
while
we're
making
these
decisions,
like
you
know,
for
me,
it's
obvious
at
least
like
yeah.
C
This
is
this
is
obvious,
because
otherwise
the
timeout
would
just
always
be
two
weeks
and
there's
no
way
to
decrease
it.
If
there's
zero
maintainers,
so
I
mean
in.
A
C
Case
it's
fairly
obvious,
but
in
other
cases
the
reasoning
might
be
lost
to
the
future
versions
of
ourselves.
So
that's
really.
My
only
piece
of
feedback
is
how
to
find
more
things
and
include
the
reason
and.
A
Yeah
well
so
so
basil.
To
be
sure,
I
understand
because
I
think
I
think
this
text
is
describing
that,
but
it
would
require
that
you,
the
the
reader,
has
to
do
a
get.
History
dig,
whereas
I
thought
what
you
were
suggesting
is.
We
would
prefer
to
put
it
actually
in
the
in
the
text
of
itself,
with
the
rationale.
C
Yeah
I
mean
I,
I
don't
feel
strongly
about
where
the
rationale
lives.
Ideally,
I
think
it
would
be
in
the
text
itself
because
that
that
kind
of
forces,
the
rationale
to
be
summarized
into
the
most
succinct
form
possible,
but
you
know
I'm
not
fussy
about
where
we
put
it
like
if
it's
in,
if
it's
in
a
big
discussion
in
the
pull
request,
that
could
definitely
be
good
enough
as
long
as
it's
captured
somewhere.
A
No,
no!
No!
Thank
you.
Okay,
all
right!
So,
given
that
we've
got
approval
from
vanic
and
from
me,
we've
got
enough
approvals
here.
Any
objection.
If
I
go
ahead
and
merge
this.
B
A
Correct
fair
enough
good,
so,
let's,
let's
go
to
the
next
one,
a
proposal
that
what
we
have
right
now
is
code
owners
on
jenkins
dot,
io
and
governance.
Documents
are
actually
listed
with
governance
board
as
code
owners.
This
document,
however,
that
tim
had
just
proposed
the
poll
request
to
is
actually
not
in
the
in
the
governance
tree
and
therefore
was
not
listed
under
governance,
responsibility
for
code
reviews.
A
B
A
C
It
makes
sense,
but
the
only
question
I
had
is:
how
has
how
has
this
worked
in
the
past
for
com?
For
comparison
I
mean
is
this:
is
this
another
case
of
codifying
what
is
already
a
de
facto
policy,
or
is
this
a
change
in
paul?
It
seems
to
me
that
it's
just
our
existing
de
facto
policy
and
we're
just
codifying
it
so
that
that
seems
fine.
B
Well,
the
default
editor
is
copy
editors,
so
I
don't
know
if
necessarily
there
was
a
previous
one,
but
that
plug-in
adoption
process,
and
this
has
not
really
been
changed
in
like
10
years.
B
A
A
B
B
A
A
B
C
A
B
C
B
The
query
right
now,
when
a
when,
let's
say,
for
example,
a
plugin
is
adopted,
one
of
the
hosting
members
still
has
to
go
to
the
bot,
that's
sitting
on
irc
and
run
a
bunch
of
manual
commands
to
give
someone
github
access.
B
C
C
Remove
myself,
but
I
think
a
lot
of
people
forget
to
do
that,
so
they
end
up
not
having
rpu
upload
permissions
start
a
factory
but
still
retaining
their
github
right
access,
which
is
a
bit
inconsistent.
B
C
In
other
words,
if
you've
lost
artifactory
access,
you
should
also
lose
github
right
access
and
vice
versa,
but
I
think
that
that
effort
writing
the
script
would
be
one
thing
I
mean
someone
could
do
that
at
an
afternoon,
but
the
more
difficult
piece
would
be
like
doing
a
dry
run
and
seeing
what
that
would
really
mean
in
practice,
because
I
think
it
could
cause
a
lot
of
hiccups
if
we're
not
very
careful
about
how
we
roll
it
out
so
that
to
me,
that
would
be.
C
B
Actual
big
effort
is
that
artifactory
is
ldap
and
github
is
github,
and
so
we
have
no
way
to
map
the
two,
which
is
what
the
original
thread
was
talking
about
and
yeah.
So
I
have.
I
have
to
go
back
and
finish
the
proposal
and
the
discussion,
but
my
plan
was
to
only
make
initial
version
of
the
script
to
only
be
additive
and
not
so
attractive.
B
C
C
There
are
a
lot
of
people
that
get
pinged
unnecessarily
because
they
still
have
right
access,
even
though
they're
no
longer
maintaining
something
and
it
can,
it
can
send
mixed
messages
to
users
when
they
approve
a
pr
and
they've
got
the
green
check
mark,
even
though
they're
not
actively
maintaining
the
plugin
anymore,
whereas
if
they,
if
they,
if
we
remove
their
write
access
at
the
same
time
as
removing
artifactory
upload
permissions,
then
that's
not
only
logically
consistent,
but
it
also
kind
of
sends
a
unified
message
to
outside
contributors,
which
I
think
is
helpful.
A
Nope,
okay,
next
topic
upcoming
elections,
so
our
annual
elections
of
officers
and
board
members
are
scheduled
for
or
slated
for
december.
Gavin
and
evelina
are
both
up
for
re-election.
We
had
the
question
last
time,
who's
running
it.
I
still
have
the
action
item.
Sorry,
I
failed
to
do
it
last
time.
I
need
to
mark
to
confirm
with.
B
A
So
tomorrow's
in
for
meeting
and
that'll
be
the
first
day
that
damian's
back
in
the
office
so
good
time
to
talk
to
him.
What
a
nice
surprise!
Yes,
welcome!
Back,
here's
some
here's,
a
task.
A
Okay,
I
assume
that
we're
still
good
with
let's
use
the
same
process
as
last
year
register
through
community.jenkins.io.
You
go
through
the
system
at
cornell
yep
great.
Usually
we
reserve
cdf
topics
for
oleg
with
oleg.
Not
here
I
don't.
I
guess
I've
got
one
cdf
topic
a
blog
post
coming
on
wednesday
for
jenkins
2.361.1
written
by
kevin
martins,
with
help
and
reviews
from
from
basel
and
from
a
number
of
others,
highlighting
some
of
the
history
of
jenkins
and
some
of
the
ways
that
it's
been
evolving
over
time,
etc.
A
I
guess
I
should
highlight
one
that
is:
jfrog
is
working
with
the
jenkins
infra
team
to
reduce
data
transfer
costs
for
our
repository
server.
B
So
I
was
thinking
about
that
today,
the
helm
chart
installs
plug-ins
every
time
it
boots
up
is
the
installing
plug-ins
part
of
artifactory
or
is
something
that
we're
hosting
externally.
That's.
A
Something
we're
hosting
externally.
C
A
I
was
looking
at
at
the
hosting
we've
only
had
three
outages,
only
three
outages
in
eight
plus
months,
thanks
to
their
hosting
that's
a
lot
better
than
we
used
to
do
when
we
hosted
it
ourselves
dramatically
better.
So
much
appreciated
and
more
up-to-date,
more
secure.
A
A
A
It
used
to
be
that
when
I
wanted
to
find
out
how
to
do
a
checkout,
I
would
do
control
f
and
search
through
this
page,
and
it
took
me
three
or
four
false
hits
before
I
got
to
the
place.
I
wanted
thanks
to
what
vihan
did
now.
I
type
checkout
there.
It
is
very
nice
next
step
when
I
would
press
the
checkout
thing
and
open
it.
It
would
take
a
frighteningly
long
time
to
load
because
all
sorts
of
content
is
hidden
under
these
expandable
expandable
elements.
A
Well,
thanks
to
what
vihan
did
he's
now,
separated
those
expandable
elements
out,
so
that
when
I
click
on
really
large
ones
like
this
one,
it
gives
me
a
hyperlink
and
takes
me
to
a
new
page
that
is
much
smaller
than
the
original
page
in
mass
much
easier
for
my
web
browser
to
process
and
much
more
comfortable
for
me
to
navigate
so
special
thanks
to
vihan.
It's
it's
been
absolutely
delightful
at
how
well
that
work
has
gone,
reminds
that
contributions
to
open
source
are
much
more
than
just
pure
software.
A
There
are
certainly
there
are
certainly
several
more
pages
yeah,
but
I
don't
think
this
has
made
it
any
worse.
Okay,.
B
Okay,
then
that's
that's.
My
concern
is
that
I
don't
know
how
I
really
kind
of
want
to
like
not
use
the
algolia
doc
search
and
just
use
a
goalie
itself
and
do
it
manually
because
then
like
we
can
control
it
a
lot
better,
but
I
don't
know
how
they're
mapping
and
stuff-
and
I,
like
some
of
these
pages,
are
going
to
return
results.
We
don't
care
about
for
search,
you
know,
so
I
was
just
worried
about
that.
But,
as
you
said,
it
doesn't
look
like
that's
the
case.
We're
good.
A
I
I
didn't,
I
didn't
see
it
as
dramatically
worse,
although
I
see
that
our
algolia
search
our
doc
search,
page
search,
is
getting
worse
and
gets
getting
steadily
worse,
so
we've
still
got
the
ticket
on
infra
to
find
a
way
to
fix
that
doc
search
definition
so
that
it
uses
their
new
thing.
Instead
of
the
old
thing
we
used
before.
B
And
I
do
want
to
figure
out
more
about
that
pipeline
syntax
generator,
because
I
we
have
talks
about
putting
someone's
information,
probably
this
specific
information
into
the
plug-in
site,
and
I
would
love
to
start
auto
linking
in
the
forums
as
well.
So
if
someone
says
the
word
checkout,
it
comes
to
this
well,
the
previous
page,
so
yeah,
those
are
other
ones.
I
want
to
find
someone-
or
I
want
to
look
into
some
point
right,
good.
A
So
there's
also
another
move
in
place.
We
had,
we
had
attempted
an
initial
look
and
feel
improvement
from
a
a
new
contributor
ended
up
that
we
had
to
pull
it
out,
but
we've
got
another
pull
request
now
from
jan
farachik
and
tim
jacom
has
done
some
detailed
checks
on
it.
I
haven't
done
detailed
checks
on
it,
yet
there
needs
more.
C
B
Muted,
I
would
say
if
you
want
more
reviews,
because
at
the
moment
I
don't
think
anyone
really
gets
pinged
on
those
throw
a
thing
on
the
dev
list,
possibly
even
the
users
list,
because
this
is
not
a
normal
java
topic
because
yeah
I
can
review
like
physically.
Does
the
code
look
fine,
but
I'm
not
in
any
way
a
layout
and
css
kind
of
person.
So
it's
like
looks
fine
to
me.
B
A
B
Good
yep,
I
think
one
of
the
boards
gonna
have
to
sign
the
github
project
action
stuff.
A
B
Yeah,
I
don't
really
have
any.
I
mean
there
are
a
couple.
We
saw
an
increase
like
every
once
a
while.
We
see
increases
into
the
type
of
questions
on
the
forum,
but
they
don't
seem
to
be
actually
related
to
a
bug.
They
just
seem
to
be
all
of
a
certain
type
come
in
one
day,
one
day
and
then
they
never
get
talked
about
again.
A
B
Oh
there's
the
the
one:
let's
promote
it
this
week,
the
slack
one.
A
On
their
jenkins
deployment.
B
B
Discuss
well,
I
mean
yeah
even
later
week,
someone's
talking
about
on
the
on
the
dev
list
about
merging
and
retiring
old
plugins
that
have
replacements.
C
C
C
A
So,
to
be
sure,
I
understand
the
context
is
this
thing's?
I
think
the
original
conversation
was
around
kevin
martin's
offering
to
adopt
a
plug-in
that
seems
to
have
a
good
successor
already.
There
are
certainly
others
like
that
right.
There's
the
multi
multi-branch
project
plug-in
that
has
multi-branch.
Is
that
what
it
is
that
is
declared
deprecated
and
the
preferred
replacement
is
pipeline,
but
we
certainly
continue
to
still
support
and
ship,
or
we
still
ship
that
plug-in.
A
B
C
Definitely
deserves
its
own
thread,
but
I
mean
the
the
the
contributor
identified
a
problem
and
did
not
really
propose
any
solutions,
and
I
think
that's
really.
The
next
is
the
you
know.
The
next
step
is
to
come
up
with
some
proposed
solutions.
I
could
envision
a
lot
of
different
solutions
to
this,
and
obviously
it
would
take
time
and
effort
to
implement
any
solution
if
it's
decided
on,
because
fundamentally,
the
problem
of
deprecating
and
migrating
is
hard
is
a
hard
problem.
If
it
was
an
easy
problem,
then
we
wouldn't
be
talking
about
this.
C
I
mean
it's
also
a
perennial
problem
in
jenkins
in
the
jenkins
project.
C
If
you
look
at
things
like
the
blue
ocean
docker
image,
you
know,
which
is
a
great
example
of
something
that
is
kind
of
at
the
end
of
its
life,
but
which
needs
a
little
more
effort
to
formally
deprecate
and
to
help
users
migrate
to
the
replacement,
and
this
kind
of
thing
requires
documentation,
training,
support,
there's
a
lot
of
dimensions
to
it,
and
it's
fundamentally
a
difficult
task
and
there's
there's
reasons
why
a
lot
of
people
continue
to
use
very
old
technology
just
because
that
migration
barrier
can
be
difficult.
C
Sometimes,
so
it's
it's
a
worthy
challenge,
but
also
not
a
not
a
simple
problem
either
so
yeah.
Definitely
something
that
interests
me
a
lot,
because
I've
done
a
lot
of
these
migrations
over
the
years,
and
I
I
have
an
appreciation
for
how
much
effort
it
takes,
but
also
how
worthwhile
it
can
be
once
the
entire
community
has
migrated
over
that
enables
us
to
innovate
more
quickly
once
we're
all
on
this
on
a
common
ground
rather
than
being
kind
of
bifurcated
into
all
these
different
usages.
C
So
something
that
I'm
very
passionate
about,
but
also
a
lot
of
work.
And
I
can
I
can.
I
would
definitely
look
forward
to
that
contributor
if,
if,
in
a
couple
of
months
they
still
have
an
interest
in
this,
I
think
there's
a
lot.
We
could
do
to
come
up
with
some
solutions
and
try
implementing
some
of
them.
B
C
B
On
that
note,
though,
because
this
reminded
me,
I
have
now
figured
out
how
to
merge,
getter,
irc
and
matrix
into
one
room
it
takes
involving
their
support,
but
I
have
done
it
so.
We
now
have
a
jenkins,
infra
and
I'll
talk
to
damien
later
matrix
channel
that
has
this
link
to
the
getter
channel,
which
is
linked
to
the
rsd
channel.
It's
all
three
are
in
the
same
spot.
B
So
I
think
alex
is
trying
to
get
me
to
do
the
releases
one
next.
So
hopefully
when
there's
all
the
support
for
all
the
all
matrix
and
getter
are
are
low,
like
they're
they're
kind
of
not
it's
not
a
heavy
commercial
product,
so
they
only
have
like
one
a
couple
agents.
So
I'm
hoping
this
week,
they'll
get
back
to
us
and
we'll
have
jenkins
releases
into
one
merged
channel
soon,
and
then
I
just
gotta
keep
going
through
that
list.