►
From YouTube: Jenkins Governance Meeting February 6, 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
So
items
on
the
agenda
today,
I've
got
news
action
items
and
then
late
additions
to
the
agenda.
Sorry,
they
didn't
get
into
the
published
draft
jira
license
changes,
Google
summer
of
code
and
then
highlights
from
Community
activity
and
there
Alex
I
was
hoping
you'd
be
willing
to
talk
to
your
experience
at
at
fosdom
and
then
I've
got
a
topic
on
artifactory
any
other
topics
that
need
to
be
on
our
agenda
today.
A
Okay,
all
right,
then,
let's
go
through
so
news
items.
Two
days
from
now,
Jenkins
2.375.3
will
release
release
candidates
available
for
testing
encouraged.
Everything
looks
right.
The
the
changelog
has
been
merged.
Alex
I,
believe
you
are
the
release
lead.
Is
that
correct?
Yep?
That's
correct!
Great!
All
right
next
item
is
that
the
next
LTS
Baseline
will
be
2.387.1.
It
will
release
March.
The
8th
release
lead
not
yet
determined.
As
far
as
I
understand.
A
And
the
January
2023
newsletter
has
is
in
preparation
right
now,
I
believe
the
pull
request
or
a
draft
pull
request
has
been
started
and
we
can
take
off
the
fasm
news.
We'll
talk
about
it
a
little
later,
any
other
news
items
that
should
be
on
on
the
list.
A
It
thank
you.
Thank
you.
My
apologies
thanks
very
much
so
election
badges
not
done
no
progress,
easy
CLA.
As
far
as
I
know
no
progress
empty
end.
Agenda
entry
worked
this
time.
I
did
it
we'll
keep
it
there
for
now
all
requests
for
the
com
converging
to
a
single
concept
of
working
groups
not
done
yet
but
I'm
back
contributing
to
docs
a
little.
So
there's
hope
for
that.
A
Next
topic
was
a
proposal
to
retire
the
Chinese
Jenkins
site.
I
had
another
reason
that
I
needed
I
needed
to
talk
to
Rick
and
so
I
asked
Rick.
The
same
question
and
Rick
replied
with
a
recommendation
that
we
redirect
the
Chinese
pages
to
their
English
equivalents.
I.
Take
that
as
his
implicit
agreement
that
we
should
go
ahead
and
end
the
Chinese
side,
we're
also
getting
new
bug
reports
due
to
the
Chinese
documentation
being
out
of
date.
A
For
example,
we
got
a
bug
report
recently
that
said,
hey
I
can't
do
a
Linux
install
and
they
quoted
the
Linux
install
instructions
that
are
available
on
the
Chinese
website
two
years
out
of
date,
and
we've
had
significant
changes
to
our
install
process.
That
are
just
not
reflected
there.
I
think
that's
a
disservice
to
these
Chinese
readers
for
them
to
see
something
in
Chinese.
C
A
I
think
it
sounds
great.
No,
no.
This
is
one
where
I'm
not
sure
I
should
call
for
a
vote
or
not
so
I
it
did
it
felt
like
this
is.
This
is
just
a
good
healthy
thing
for
us
to
do.
I,
don't
think
that
the
board
has
to,
and
if
there
was
some,
if
someone
brought
back
the
Chinese
documentation
or
fresh
translation,
we
could
always
bring
it
back.
It's
not
that
this
is
never
never
to
be
done
again.
A
Okay,
good.
All
right
last
item
was
archive.
The
docs,
the
governance
meeting,
notes.
Sorry,
no
progress
for
me
on
this.
One
and
I
still
have
the
action
to
check
with
what
the
response
was
from
infra
team
and
bring
it
back
to
our
group.
A
Okay,
next
topic,
then
jira
license
changes
will
affect
the
Jenkins
project.
So
the
I
was
reminded
of
this.
When
Andrew
grimberg
of
the
Linux
Foundation
replied
to
a
support
ticket
I
raised
asking
that
they
refreshed
the
license.
He
reminded
and
we've
known
about
this
for
a
year
or
two,
that
effective
February
of
2024
atlassian
no
longer
will
have
their
standard
product
available
in
a
hosted
solution.
It's
all
going
to
atlassian
Cloud.
A
But
there
are
some
barriers
to
us,
preferring
to
remain
to
us
remaining
with
jira
that
we've
got
to
work
out
with
atlassian.
The
best
would
be
if
we
can
persuade
atlassian
to
give
us
a
jira
data
center
license.
Then
a
Linux
Foundation
continues
to
host
us.
If
Linux
Foundation
continues
to
host
us,
it
looks
no
change
to
us.
They
just
upgraded
our
license
and
we're
done
if
we
can't
get
a
jira
data
center
license
from
them
and
have
to
go
to
atlassian
Cloud.
That
means
we
have
to
live
in
the
limitations
of
atlassian
cloud.
A
A
D
B
I
agree
with
only
here:
I
think
we
don't
need
to
hope
for
the
worst
case
here
but,
like
I,
said
2024,
there
is
still
a
year
away,
but
like
giving
us
some
spare
time
to
consider
something
and
reach
out
to
them
to
get
us
the
license,
but
yeah,
but
I
also
think
we
can't
get
rid
of
Dira,
because
the
entire
security
workflow
is
so
embedded
with
jira.
We
can't
just
go
to
GitHub
or
any
other
alternative
that
easily.
A
Agreed
I
think
I,
think
they're
willing
and
Basils
basels
provided
a
number
of
other
points
about
why
jira
is
a
much
richer
way
of
managing
issues
in
this
developer
mailing
list.
He
notes
notes
that
there
are
capabilities
in
jira
that
the
most
recent
GitHub
issues
just
don't
represent
those
things
and
that
that
will
be
a
sacrifice
if
we
have
to
do
without
those
so
good.
Okay,
so
I'm
going
to
continue
I'll
plan
to
report
status
on
this
periodically.
C
Can
we
make
the
most?
How
can
we
make
the
most
compelling
argument
for
them
to
give
us
that
license
that
we
need?
Is
it
because
they're
are
they
giving
us
a
license
already
for
the
current
hosted
installation?
They.
A
Are
a
different
one,
yeah
they're,
giving
us
a
license
already
for
the
current
hosted
one,
the
The,
crucial
things
that
are
most
compelling
to
me
and
that
I
thought
were
persuasive
and
that
I
included
in
my
last
email
to
Chrissy
was
that
they've
got
an
upper
bound
of
30
000
on
their
jira
instances,
and
we
have
well
over
a
hundred
thousand
on
ours.
A
A
A
Well
and
I
think
there
may
be
more
arguments
beyond
that.
I
will
certainly
reiterate
that
one
to
Chrissy
again
as
as
she
and
I
go
through
these
discussions,
but
licensing
then
the
the
using
our
own
ldap
is
for
us
somewhat
of
a
win,
because
we
don't
have
to
do
a
transition
of
a
hundred
thousand
or
even
ten
percent
of
that
ten
thousand
users
to
get
them
in
addition
to
having
their
existing
Jenkins
account
and
the
GitHub
account
they
use.
A
They
would
now
also
have
to
have
a
bit
an
atlassian
account
and
and
that
that
feels
like
that
would
be
a
significant
loss
to
us.
It's
much
healthier
if
we
can
persuade
them
to.
Let
us
keep
continue,
bringing
our
own
authentication,
but
in
order
to
bring
our
own
authentication,
we
have
to
run
our
own
server,
which
means
jira
data
center,
which
means
Linux
Foundation.
C
A
And
that's
my
hope.
Now,
Andrew
grimberg
of
the
Linux
Foundation
seems
ready
and
willing
to
continue
hosting
us
so
long
as
they
can
get
the
data
center
license.
He
indicated
to
me
that
they
have
one
or
more
other
of
their
solutions.
That
is
using
a
data
center
license,
but
they
have
to
be
granted
to
the
project
right,
so
so
they've
it's
got
to
be
granted
by
atlassian.
It's
not
something
we
can
just
get
magically.
A
Okay,
great
thank
you.
Next
topic
was
Google
summer
of
code
and
this
one
I
brought
to
governance
board.
Just
for
your
awareness.
Our
application
is
due
tomorrow:
Alyssa
Tong,
John,
Mark,
Mason
and
Chris
Stern
are
the
org
admins
for
Google
summer
of
code
in
the
Jenkins
project,
they're
preparing
that
that
application,
Bruno
Marsden,
is
also
helping
there
with
organization
admin
we're
looking
forward
to
that
application.
We're
expecting
it
to
be
submitted
today,
because
final
deadline
is
tomorrow
and
it
does
change.
A
and
I
think
we
should
just
accept
I've
accepted
that
we
won't
be
doing
she
code
Africa
contributon
in
2023,
because
we
want
to
do
Google
summer
of
code
very
well,
I'm
open
to
other
opinions,
other
ideas
or,
if
others
want
to
volunteer.
My
experience,
was
it's
a
a
good
experience.
It's
a
low-cost
experience
for
the
Jenkins
project,
Cloud
bees
donates
about
six
thousand
dollars
and
and
then
that
funds
six
or
seven
new
contributors
from
Africa
for
a
period
of
four
weeks.
A
D
A
Great
next
topic,
then
Jenkins
project
at
fosdum,
Alex
I,
wanted
to
hear
from
you.
How
was
the
experience
I
understand
that
you
were
there
and
that
you
were
at
the
booth
and
Etc
I
have
pictures
as
evidence
of
that.
B
Yeah
I
was
at
the
booth,
at
least
at
Saturday,
and
the
booth
was
pretty
busy
and
active
as
they
already
knotted
down.
People
were
much
interested
in
Jenkins,
ranging
from
people
who
are
using
it
for
decades
and
newbies
around
I,
don't
know
a
couple
of
years
and
renting
to
possible
g-soc
students,
Your
Mark
had
conversations
with
so
yeah.
It
was
pretty
interesting
experience,
given
so
much
people
were
actually
interested
in
Jenkins,
ranging
from
so
many
different
background
and
yeah.
A
B
I
just
spent
the
Saturday
at
the
booth,
the
Sunday
I
left
for
the
others,
because
a
pretty
it
was
a
pretty
stressful
day
and
I
also
wanted
to
attend
a
few
talks
and
meet
other
people.
But
yeah.
The
Jenkins
Community
dinner
on
Saturday
evening
was
pretty
well
visited.
I
would
say
the
people
you
have
on
the
list
were
there
Stefan
speaker
was
there.
Oh.
B
Yeah
with
a
couple
of
his
fellows,
he
brought
with
him.
Oh
yeah
Stefan
was
also
there
just
added
them
to
his
list.
A
Okay,
next
topic
was
in
community
news.
We've
got
an
a
project
ongoing
with
jfrog
to
reduce
the
bandwidth
use
from
our
artifact
repository
they've,
been
providing
us
with
log
files.
We've
been
doing
analysis
of
those
log
files
and
the
analysis
has
detected
some
quite
heavy
users
that
we've
unnecessarily
heavy
users
that
we've
been
actively
reaching
out
trying
to
contact
them.
We
were
successful
on
one
of
them.
A
A
And
that
proxy
right
now
is
just
doing
plug-in,
builds
it,
but
other
other
projects,
like
the
bill
of
materials,
are
coming.
A
And
then
they've
recommended
our
jfrog
has
recommended
some
permission:
changes
that
are
actively
under
development.
They've
set
a
a
goal
for
us
to
do
a
goal
to
do
the
first
Brown
out
test
drive
of
the
new
permissions
in
mid-February,
we're
behind
schedule,
we're
behind
schedule
on
that
because
of
these
other
changes
that
were
more,
that
were
more
high
impact
and
had
a
better
chance
of
doing
an
immediate
reduction
of
bandwidth
use
so
that
brownout
and
the
plan
test.
A
C
A
So
I
think
I
think
we
I
would
like
to
see
this
week's
logs.
They
should
be
coming
to
us
today
or
tomorrow
and
I'll
go
through
those
buzzle,
rather
than
take
your
time
to
do
it,
but
after
I've
been
through
them.
I
may
ask
you
to
do
one
more
look
there,
just
because
I
suspect
the
next
level
down
we're
going
to
have
to
do
that
analysis
and
look
for
things.
A
C
So,
are
you
good,
would
you
would
you
get
in
contact
with
me
when
you
want
me
to
analyze
the
logs
again
or
should
I
be
putting.
A
A
Yeah,
so
the
so
the
problem
is
outbound
bandwidth
and
you.
You
asked
an
interesting
question
only
because
it's
the
same
question
we
asked
we
were
a
little
concerned.
We
write
a
lot
of
incrementals.
Are
you
really
frustrated
at
how
many
incrementals
we
write
and
their
answer
is
not
in
the
least
that's
not
a
problem
at
all.
Keep
writing
so
so
I
was
I
was
really
pleased
because
we
could
certainly
expire
the
incrementals
after
a
year
or
you
know
we
could.
We
could
set
expiry
and
they
said
no,
don't
bother.
A
D
A
Right
we,
we
certainly
could
expire
well,
every
build
of
every
plugin,
with
incrementals
enabled
pushes
an
incremental
or
every
build.
That's
current
to
tip
current
to
the
tip
of
the
master.
Branch
will
push
an
incremental
and
therefore
we're
storing
lots
and
lots
of
those.
But
but
their
answer
really
was
no.
That's
not
the
big
issue.
The
big
issue
is
outbound
bandwidth.