►
From YouTube: Jenkins Governance Meeting January 9, 2023
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
Build
monitor
view,
plugin,
governance
board,
meeting
time
and
date
lost
donations
from
ffis.de,
CDF
Outreach
and
if
Oleg
joins
us
CDF
topics
and
then
Community
activity,
any
other
topics
that
need
to
go
on
the
agenda
today.
A
Okay,
great,
then,
let's,
let's
go
ahead
with
news
Wednesday
we
will
release
Jenkins
2.375.2
the
next
LTS
in
the
2.375
line,
thanks
very
much
to
everyone
involved.
Chris
Stern
is
release
lead
thanks,
Kevin
for
writing
the
changelog
in
the
upgrade
guide.
A
The
December
2022
newsletter
is
being
prepared
thanks
to
Bruno
Marsden,
for
submitting
the
pull
request
to
Alyssa
Tong
for
Gathering
it
and
to
the
contributors.
There
are
a
number
of
things
that
I
still
have
to
contribute,
so
we're
not
ready
to
merge
yet.
But
thank
you
very
much
for
the
progress
we
had
a
Jenkins
webinar
on
Google
summer
of
code
last
month
and
upcoming
we've
got
fosdum
in
Brussels,
February,
4th
and
5th
Alyssa
is
coordinating
the
Jenkins
booth.
A
Okay
action
items
Alex
had
the
action
item
to
to
help
us
require
that
Community,
Sig
office
and
other
lists
have
a
member
of
the
board
as
a
manager
or
owner,
so
that
in
case
of
issues
we
can
get
involved
and
actually
make
a
difference.
Anything
you
want
to
report
there
Alex.
B
Better,
yes,
better,
okay,
okay,
yeah
last
week,
I
had
a
chat
with
Costco
K
and
he
handed
over
ownership
of
the
Brazilian,
the
Korean
and
the
Japanese
mailing
list
to
me,
which
I
yeah
yeah
those
three-month
Brazilians
one,
the
Korean
one
at
the
Japanese
one.
B
A
B
A
A
A
Kevin
had
the
action
item
to
use
the
community
for
the
Jenkins
docs
mailing
list
and,
as
far
as
I
understand,
Kevin
no
progress
there.
This
is
again
a
mark
weight
thing.
A
Easy
CLA
documentation
by
Oleg
no
progress
as
far
as
I've
seen,
but
no
requests
in
the
ensuing
month
either.
A
Thanks
to
everyone
who
contributed
to
this
agenda,
it
was
really
nice
that
I'm,
not
the
only
one
typing
agenda
proposals.
Thank
you
very.
Very
much
next
topic
was
combine
the
sub
projects
and
sigs
into
a
single
concept.
Working
groups.
That's
no
progress,
but
Mark
to
complete
by
end
of
before
next
meeting,
I
also
will
submit
road
map
updates.
A
A
Oleg
had
the
action
item
to
send
a
proposal
to
Rick
to
retire
the
Jenkins
Chinese
site.
The
site
is
not
getting
updates
and
hasn't
been
receiving
updates
for
multiple
years
no
progress
as
far
as
I
know
does
anyone
else
have
other
information.
A
We
need
a
need,
a
destination
repository
and
I
have
the
action
item
to
bring
that
to
closure,
whether
it
should
be
in
Jenkins
infra
or
in
the
Jenkins
CI
organization.
It's.
The
question
was
raised,
backed
by
the
infra
team,
raised
a
question
about
the
location
of
the
Repository.
A
Okay
next
topics,
then
we
had
discussed
in
our
last
meeting
this
open
proposal
to
allow
up
to
two
elected
board
members
from
a
single
company
and
said
we
would
bring
it
to
this
meeting
to
try
to
bring
it
to
final
closure
now
Uli
I
know.
One
of
your
concerns
was
that
you
were
minus
one,
as
you
want
to
further
explain
your
concerns
here
so
that
others
hear
them
and
then
then
we
can
have
further
discussion.
D
Yeah
I
think
there's
no
much
discussion
required
I
just
looked
before
I
work,
I
gave
my
minus
one.
I
wasn't
sure
what
your
you
know.
What
was
the
reasoning
for
the
whole
thing
because
it
was
started
before
I
entered
the
board
and
yeah
since
nobody
actually
replied
to
this
requirements.
This
new
requirement,
so
yeah
I,
think
I'm,
not
minus
one,
but
I'm,
not
plus
one
so
I'm
here,
actually
I,
don't
know
why
we
are
doing
it
really,
because
you
know
I,
don't
see
the
need
to
change
anything
now,
but
I'm
not
against
it.
E
I'm,
sorry,
if
you
open
the
next
message,
I
did
reply
to
the
question.
Yeah.
D
Yes,
the
reason
is
sorry,
nobody
else.
So
my
my
my
thinking
about
it
was.
We
need
to
have
a
discussion
of
all
Jenkins
developers
about
this
topic
and
since
nobody,
besides
basil,
replied,
we
have
no
much
developers
left
in
Jenkins
who
are
really
interested
in
this
in
this
topic,
so
yeah,
so
I
won't
block
it
just
because
I
said
it
once
before.
D
The
next
election
is
so
I
mean
it's
quite
some
time
to
go
and
the
reasoning
or
why
I'm
wondering
is
I,
think
yeah.
It's
it's
not
really
important.
So
let's
make
the
decision
and
yeah
I'm
fine
with
it.
So
I'm,
not
plus
one
but
I
will
not
block
it.
D
A
Well,
but
isn't
it
that
if
we
don't,
if
we
don't
allow
this
rules
change,
we
are
assured
that
in
the
next
election
we
can
at
most
have
one
person
from
cloud
bees
and
this.
This
reasoning
that
that
Basel
gives
and
that
I
agree
with
a
second
person
from
cloud
bees
gives
us
a
chance
to
do
more,
get
more
work
done
on
governance,
action
items.
D
A
We're
also
looking
at
I'm,
the
biggest
most
guilty
party
here
is,
is
the
challenge
so
so
things
that
that
I've
struggled
to
complete
include
pull
requests
right.
Olegs,
completion
of
the
Chinese
website,
olegs
completion
of
easycla
I,
mean
I.
Think
we've
got
a
number
of
things
that
have
lasted
for
a
very
long
time
as
as
open
Action
items
on
the
on
the
board's
list
of
of
action
items.
A
D
D
D
Currently
we
we
have
this
problem
in
the
definition,
because
Costco
is
and
part
of
cloud
piece
or
of
his
own
company,
but
if
we
change
the
rule
in
the
other
way,
that
means
that
we
do
not
allow
from
these
four
members
which
are
elected
regularly.
We
can
have
a
new
rule
saying
that
no
company
is
allowed
to
have
two
seeds
of
these
four
members.
Then
this
problem
will
disappear
as
well.
D
A
D
A
D
A
A
A
A
Okay,
Basel
you're
next
on
my
visible
list.
C
A
Okay,
so,
based
on
that,
my
interpretation
is
we
carry
this
forward
with?
Yes
accept
the
change.
A
E
Sir,
the
build
monitor
if
you
plug-in
it's
non-standard
and
it's
hosting
and
release
process,
and
this
has
caused
a
number
of
pain
points
over
the
years.
For
example,
when
I
was
working
on
the
guava
project,
I
had
to
get
a
new
release
of
this
plug-in
out
and
it
was.
It
was
difficult
to
do
that,
given
its
non-standard
release
process.
E
E
So
every
so
often
when
this
topic
comes
up,
I've
offered
to
help
normalize
the
release
process
for
this
plug-in
by
moving
it
to
our
standard
model
of
but
Jenkins
CI
GitHub
organization,
using
Jenkins
for
CI
I'm,
using
our
standard
project,
wide
CD
setup
and
using
release
drafter
to
document
the
contents
of
the
release.
E
So
I
think
this
would
solve
the
pain
for
users,
because
this
would
avoid
creating
releases
for
dependency
updates,
which
our
process
does
not
do
unless
the
developer
label
is
applied
and
also
it
would
give
us
release
notes
with
release
drafter
and
in
general.
It
would
make
it
much
easier
to
do
releases
of
this
plugin,
for
example,
if
there's
a
future
UI
chains
that
requires
that
plugin
to
be
adapted,
it
would
be
much
easier
to
release
that
change
if
this
plugin
was
using
our
standard
process.
E
So
I
had
a
discussion
with
the
author
of
this
plugin
and
he
noted
that
there
were
some
conditions
that
he
wanted
our
assurances
about
in
order
to
transfer
the
repository
to
our
GitHub
organization,
and
one
of
them
was
retaining
a
note
about
the
original
author
in
the
readme,
which
I
thought
should
be
non-controversial.
That
seems
something
that
we
could
easily
accommodate.
E
The
other
request
was
to
retain
the
current
non-invasive
footer
linking
to
his
website.
So
this
is
on
the
bottom
right
corner
of
the
user
interface.
There's
this
link
to
the
author's
website
inside
of
the
Jenkins
UI.
So
you
could,
you
could
call
it
branding,
for
example,
but
so
that's
so
this
is
already
there
in
the
current
code,
that's
hosted
in
his
GitHub
organization,
but
we
are
currently
publishing
this
on
our
Update
Center
and
have
been
for
a
very
long
time.
E
So
this
wouldn't
be
a
new
addition,
but
rather
rather
this
would
be
assuring
the
author
that
this
existing
link
could
be
retained
even
as
we
move
the
hosting
of
the
repository
into
our
own
GitHub
organization.
E
So
that
was
a
topic
that
I
didn't
feel
that
I
could
give
him
an
answer,
one
way
or
another
as
an
individual,
which
is
why
I
wanted
to
bring
this
topic
to
the
board.
But
if
the
board
does
confirm
that
these
conditions
are
acceptable,
then
I
can
proceed
with
normalizing.
The
hosting
and
release
of
this
plugin.
B
B
A
D
Do
we
have
a
screenshot
of
this?
How
this
footer
looks
like
I
I,
don't,
okay
and
I
might
I
don't
mean
the
code,
the
how
it
looks
in
Jenkins
right.
A
A
E
E
A
chord
change
that
breaks
this
plug-in.
So,
if
you
look
at
the
releases,
tab
of
this
you'll
see
the
problem
that
users
have
been
complaining
about,
which
is
that
none
of
this
information
is
really
is
relevant.
I
mean
it's
all,
there's
no
there's
no
information
about
the
content
of
these
releases.
It's
actually
not
even
picking
up
on
this
page,
the
newer
builds
from
2022
and-
and
all
of
this
is
all
this
is
due
to
the
non-standard
scheme
that
is
being
used,
which
is
not
it's
not
a
bad
scheme.
E
C
D
E
D
It
makes
sense
to
move
it
to
Jenkins
CI.
D
C
E
Yeah
I
think
it's
I
think
it's
a
good
idea
just
to
normalize
and
improve
consistency.
So
there
was
one
other
requirement
that
John
had
about
making
sure
that
his
test
Suite
was
still
enabled
so
I'm
still
discussing
that,
but
there's
some
problems
with
the
test
Suite
as
well
that
that
that
basically
the
test
Suite
is
not
currently
working.
E
So
we
have
to
figure
out
what
to
do
about
that,
but
I'm,
confident
that
I
can
come
to
a
conclusion
with
John
about
the
test
Suite
as
long
as
these
other
conditions
are
accepted.
E
Yeah
the
tests
are
not
currently
passing,
so
the
question
I
think
is:
do
we
want
to
go
ahead
with
moving
it
to
the
Jenkins
CI
GitHub
organization
without
running
the
tests,
I.E
turning
them
off,
which
I
think
I
think
John
didn't
want
us
to
turn
off
the
tests,
but
my
perspective
was
more
that
I,
don't
think
we
could
I,
don't
think
I
would
be
making
the
situation
worse
by
doing
that
since
they're
already
broken
so
right,
we've
got
to
figure
out.
E
If,
if
somebody
can
get
these
tests
passing
again
or
how
much
work
that
is,
they
also
use
a
non-standard
test
harness.
So
that's
another
complicating
Factor,
but
I
think
we
could.
We
could
probably
come
to
a
conclusion
about
that
with
some
more
discussion.
Hopefully,
we
could
find
a
way
to
just
fix
these
tests,
but
if
we
can't
then
I'm
sure
that
we
could
find
a
way
to
at
least
not
make
it
any
worse
than
it
is
today
great.
A
A
Or
I
can,
if
you
want
to
just
post
the
location
of
your
of
your,
your
screen,
share
that
you
uploaded.
E
It's
a
private
link,
so
it'll
be
easier
if
I
just
share
my
screen:
great
okay.
Okay,
can
you
see
my
screen
now.
E
Yes,
yes,
so
this
is.
This
is
a
screenshot
of
the
plugins
UI
and
if
you
see
on
the
bottom
right
corner,
it
just
says
brought
to
you
by
John
Molek.
A
C
B
E
Basel
plus
one.
A
A
D
A
Yes,
because
for
now
it's
pretty
fun
right.
In
fact,
that's
a
good
point.
We've
found
in
the
past
that
when,
when
governments
change
clocks,
we
typically
want
to
adjust
our
meeting
time
to
fit
our
our
our
personal
schedules
again,
and
so
we
will
just
plan
to
negotiate
that
next
time
the
government's
medal
with
clocks
plea,
please
Lobby
your
elected
representatives
to
stop
government
meddling
with
clocks,
but
that's
a
different
problem.
A
A
All
right
next
topic
was
lost
donations
from
ffis.de,
so
Uli
I
guess
this
one
starts
with
Kevin
closing
out
the
website
topic
and
you
bringing
it
back.
Could
you
share
with
us
some
of
the
status
Etc
yeah.
D
Actually,
the
item
which
is
in
this
issue
is
not
about
the
website.
It's
about
the
Lost
earnings
we
got
from
the
German
donations.
I
think
we
had
a
couple
of
thousand
dollars
which
were
and
this
website
ffis.de.
This
is
a
German
yeah
affiliation
or
it
was
a
German
affiliation.
Now
I
think
the
link
is
almost
dead
and
I
think
they
don't
work
anymore
and
we,
it
was
in
my
election
period
or
in
my
last
election
period.
D
I
started
to
work
on
this
issue
because
I'm
from
Germany,
so
I
tried
to
reach
the
contact
person
and
actually
they
still
exist,
but
they
don't
react
so
without
yeah
using
a
lawyer,
I
think
we
don't
have
a
chance
to
see
or
get
our
money
back
so
I'm,
not
sure
if
it's
worth
the
effort,
so
I
think
it's
okay
to
close
this
issue
and
yeah.
Now
we
have
a
good,
documented
approach
on
a
well.
The
donations
should
go
and
we
should
not
yeah
make
such
spin-offs
in
the
future
anymore.
A
Thank
you
well
and
thanks
for
your
work
on
that
that
I
I
was
really
impressed
to
see
this
from
two
years
ago.
Official
documentation,
making
the
request
Etc
thanks
for
doing
that
and
I
I
agree
that
I
don't
think
it's
worth
our
energy
to
attempt
to
follow
legal
recourse,
because
I
suspect
the
money
is
gone
and
the
person
will
just
at
least
if
it's
consistent
with
U.S
law,
we'll
just
waste
money
on
a
lawyer
and
still
not
get
any
money.
Yeah.
A
Great,
thank
you
yeah,
so
Linux
Foundation
is,
is
our
their
Community
Bridge
system
is
our
way
of
accepting
donations
now,
and
that
feels
like
a
much
more
trustworthy
location
and
I
agree
with
your
phrasing
no
spin-offs
in
the
future.
No
no
alternate
paths
to
attempt
to
to
collect
donations.
A
Okay,
CDF
Outreach
reboot.
This
is
just
FYI
that
the
meeting
was
held
and
now
will
be
happening.
I
believe
once
a
month,
they'll
meet
as
an
Outreach
group
from
CDF
to
help
increase
the
adoption.
Some
of
the
action
items
that
came
out
of
that
meeting
include
included
ways
to
help
the
Jenkins
project
as
we're
broadening
and
deepening
involvement
in
Google
summer
of
code,
how
to
encourage
more
mentors,
Etc
I'm,
going
to
delete
the
CDF
topic
since
oleg's,
not
here
today.
A
The
last
topic
I
had
was
Community
activity,
and
this
is
just
in
my
attempt
to
summarize
things
that
I'm
seeing
in
the
online
forums
and
communities
so
Google
summer
of
code
interest
is
definitely
growing.
We
are
certainly
needing
more
act,
more
mentors
and
more
project
ideas
thanks
to
Basel,
to
Bruno
and
to
several
others
for
good
ideas
across
a
broad
range
of
topics.
Everything
from
documentation
site
to
plug-in
maintenance
to
remoting
improvements
are
all
included
in
the
set
of
ideas,
more
ideas,
welcomed
and
more
mentors,
certainly
encouraged.
A
A
So,
as
we
go
forward
being
aware
of
those,
we
may
find
ways
to
better
document
them
better,
describe
them
or
address
the
questions
in
advance
and
then
the
big
one,
thanks
to
Bruno
for
assembling
for
Basel,
for
suggesting
topics
and
Concepts
and
to
Kevin
for
Content
work.
The
December
newsletter
is
intended
to
cover
12
months
of
Jenkins
progress,
so
basels
or
Bruno's
submitted
the
pull
request.
I've
got
some
things
that
I
need
to
add
to
it
I'm
sure
and
as
we
were
going
back
over
the
list,
it's
an
amazing
thing.