►
From YouTube: Jenkins Governance Meeting September 19, 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
2.361.2
releases
scheduled
for
October
5.
Chris
Stern
has
volunteered
to
be
the
release
lead.
The
release
checklist
is
open.
The
back
porting
pull
request
at
least
the
first
backporting
pull
request
has
been
merged
and
a
changelog
draft
pull
request
or
change.
Log
pull
request
has
been
submitted
thanks
to
Basel
thanks
to
Kevin
Martin's,
a
bunch
of
progress.
A
Additional
item
hacktoberfest
is
coming
welcome
to
prep
Timber
John
Mark
Mason
has
posted
a
blog
post
and
preparations
are
happening
in
the
ux
Sig,
the
doc
Sig
and,
in
other
places
to
be
sure
we're
ready
for
Oktoberfest.
A
If
you
didn't
see
the
recording
of
the
ux
Sig's
last
ux
meeting,
you
should
probably
watch
that.
That's
the
third
highlight
Jan
farech
and
Tim
Jacob
are
preparing
a
presentation
that
they'll
give
at
devops
World
on
some
ideas.
They've
got
for
a
major
change
to
the
Jenkins
UI
and
Tim
noted
Gavin
I.
Think
you'll
be
delighted
with
this
one
pipeline
graph
view
is
now
rendering
much
more
correctly
much
closer
to
what
blue
ocean
did
than
it
ever
did
before.
A
A
C
Well,
there
was
CDF
mini
Summit
at
the
open
source
conference.
There
was
one
presentation
about
the
Jenkins
surveyor,
mostly
about
pipeline
libraries
and
all
the
system
for
Jenkins
at
scale.
C
Yes,
so
it
was
open
source
Summit
in
Dublin.
Okay,
thank
you.
C
A
Okay,
next
topic,
then,
was
action
items
I'm
I've
made.
No
progress
on
community.jenkins.io
is
the
replacement
for
the
doc
Sig.
It's
going
to
be
a
while,
yet
because
I've
got
to
get
ready
for
devops
world
and
after
that
I'm
taking
some
some
holiday
time
to
go.
Vacation
next
was
request.
Full
access
to
the
CDF
Zoom
account
Gavin.
You
indicate
you.
We've
got
a
group
now
so
I
just
need
to
contact
Michelle
and
ask
her
to
add
that
group.
A
A
B
C
So,
for
me,
it's
mostly
the
documentation
part
during
the
first
pass,
I
cleaned
up
everything,
including
manually,
that
you
know
no
longer
used
Etc,
but
the
guidelines,
the
central
repository,
is
still
not
what
we
would
like
to
have
for
easy.
Silly.
A
Excellent
thanks
Oleg.
Thank
you
very
much.
Okay.
If
we
carry
that
one
forward,
then
as
an
action
item,
easy
CLA
needs
to
be
documented.
A
A
So
the
the
notes
from
our
last
session
were
that
we
would
ask
Damien
if
you
would
be
willing
to
run
the
elections
as
in
for
officer.
He
said.
Yes,
he
needs
to
have
a
discussion
with
Olivia
Bernal
to
be
sure
that
he
understands
the
detailed
process,
but
I
hope
that
we'll
have
a
discussion.
Further
discussion
of
that
on
in
for
in
info
meeting
tomorrow.
B
A
A
B
A
A
A
B
A
B
B
A
A
B
A
A
A
But
they're
moving,
they
the
system
that
we're
running
right
now
or
repo.jenkinsci.org,
is
relatively
old
and
is
somewhat
of
a
one-off
for
them.
They'd
like
us
to
be
on
the
similar
kind
of
platform
as
they
use
for
all
the
other
open
source
projects
that
they
sponsor
and
so
they're
planning
that
move.
They
don't
expect
it
to
be
a
significant
downtime
but
they're
working
through
the
process
to
get
that
move
prepared.
C
C
So
my
understanding
of
the
CDF
wants
it
to
happen
eventually
over
as
the
budget.
Another
things
you've
provided,
but
yeah
I
think
that
it
would
be
nice
for
the
project
to
present
there
like.
A
C
Definitely
not
me
who
should
be
presented
because
I
haven't
been
connected
too
much
to
drink
it's
in
the
recent
year
because
of
a
lot
of
the
stuff.
A
C
It's
mostly
good
getting
some
confession
coming:
it
was
coming
into
so
the
goal
is
not
to
present
all
the
updates
in
the
recent
three
months.
Okay,
the
goal
is
mostly
a
show
whether
where
the
project
is
going,
especially
with
regards
to
CDF
statuses,
so
we're
using
this
is
graduated
project,
so
we
are
not
going
anywhere
at
the
moment,
but
there
are
still
a
few
beats
like
Security
reviews,
which
we
haven't
completed
when
graduating
kind
of
which
should
happen
eventually.
C
A
A
Was
another
topic
that
so
and
that's
one
that's
coming
to
the
contributor
Summit,
so
those
kinds
of
things:
security,
supply,
chain,
security,
those
sorts
of
topics-
that's
what's
interesting,.
C
Every
way
because
of
the
supply
and
shade
and
seek-
and
obviously
there
are
parties
that
are
interested
to
push
this
topic,
for
example,
chain
guard,
but
in
reality,
yes,
there
is
expectation
for
new
deliverables
that
they
would
be
signed.
C
C
Think
so
and
the
well,
the
question
is
also
look
at
images
for
what
so
once
we
moved
to
the
new
packaging
flow.
Yes,
they
have
signing
committed
data,
but
it's
not
all
the
images
we
ship
in
the
project,
yeah.
B
I,
don't
know
I'm
not
on
I'm,
not
really
involved
that
you
thought
I
saw
signing
what's
happening
for
docker.
C
So
for
Jenkins,
core
images,
yes
for
sure
for
Jenkins
images,
if
I
recall
karaoke
I'll
see
yes
yeah.
This
definitely
covers
most
of
the
use
cases.
I
can
also
say
for
sure
that
is
foreign
signed.
But
what
is
the
concern
for
the
most
of
contributors
in
the
project?
I
guess
not,
but
yeah.
This
is
a
question
of
whether
there
is
anything
else
and
the
health
charts
is
a
good
example
of
that,
because
we
kind
of
have
them,
but
I
literally
have
no
idea.
What
is
the
current
release
flow?
There.
A
C
If
you
check
open
ssf
best
practices,
then
Eve
Jenkins
wants
to
press
it
further.
Then
release
process
is
one
of
the
key
Milestones
Force
got
it.
Okay,.
C
Is
just
about
signing
distribution,
so
there
are
also
things
Everyone
likes
called
s-bomb,
which
is
again
probably
not
that
difficult
for
Maiden
right
but
more
difficult
for
other
packaging
types
like
well
docket
images
again,
so
it's
also
something
that
we
might
want
to
pay
or
put
on
the
list.
If
we
talk
about
having
a
couple
security
audits
in
the
future,
okay.
A
C
I
can
add
it
to
the
agenda.
I
just
I
need
to
know
who
would
be
presenting
and
when
so
the
next
meeting
is
next
week
next
week,
I
guess
it's
not
a
good
option
taking
devops
Waltz
but
yeah
two
weeks
after
it's
something
that
could
be
used.
B
B
C
So
for
Jenkins
there
is
no
specific
time
when
it
needs
to
be
done.
So
even
November
is
fine.
It's
just
some
something
that
could
make
sense.
C
One
hour
two
meetings
ahead
is
definitely
a
safe
timeline.
Okay,
so
basically
it's
the
same
as
injunctions
yeah
we
park
in
topics
until
the
agenda
is
full
okay
and
while
it's
rarely
full,
so
you
know
nothing
really
specific
to
this
meeting.
C
So
yeah
the
one
in
three
weeks
is
definitely
available.
The
one
is
in
five
weeks
is
also
available.
One
thing
that
for
five
weeks
there
will
be
coupon,
so
there
will
be
much
less
people,
but
I
will
be
around
to
host
it
if
needed,
seven
weeks.
Well,
it's
probably
six
week
beyond
beyond
my
normal
planning
Horizon
these
days,
so
it
should
be
available
soon.
A
A
The
items
I
had
were
that
the
contributor
Summit
will
be
September
27th
agendas
available
from
this
Google
doc
and
we're
thrilled
that
Tim
Jacob
Jan
farachick,
Willie,
Hoffner,
Alex
brandus,
several
others,
so
Damien
deporto
me
badek
felonier
will
will
be
there
for
that
Summit.
It
looks
to
be
a
very
good
Summit,
we'll
capture
the
notes
and
share
them
afterwards.
A
Github
project
actions
from
Google
summer
of
code
was
an
open
question
two
weeks
ago
and
we
don't
have
a
a
conclusion
on
it.
This
one
was
specifically
asking
what
would
it
take
to
register
the
Jenkins
file?
Runner
GitHub
action
under
under
a
GitHub
action
with
some
registration
process
and
I
apologize
I've
done
no
further
work
on
this.
Are
there
others
who
have
anything
to
report
there.
C
Well,
it's
basically
me
who
recommended
to
bring
it
up
to
the
community,
so
I
guess
it's
me
who
also
should
have
responded,
no
matter
what
needs
to
be
done
for
every
organization.
We
need
to
basically
assign
an
additional
agreement,
which
is
super,
straightforward,
I,
don't
think
there
could
be
any
kind
of
legal
Connections
in
this
particular
case,
because
he's
just
a
publishing
content
on
Marketplace
and
once
this
agreement
is
signed,
actions
would
appear
on
the
market.
Please.
C
A
D
Thanks
all
right
for
anything,
we
publish
might
be
interesting
to
know
how
we
expect
to
handle
reports
of
security
issues
that
are
coming
in
to
make
sure
that
yeah
third
parties
know
what
to
expect
until
we
expect
to
handle
that.
If
this
is
anything
resembling,
an
official
Jenkins
project
deliverable
right.
A
D
And
I
mean
it
might
be
as
simple
as
I
need
to
add
a
new
component
in
the
security
gr
project,
but
would
also
what
would
also
be
important,
as
students
has
come
up
a
bit
in
the
past,
with
basically
everything.
That's
not
just
a
plug-in
who
owns
this
who's
responsible
for
the
component.
So
that
would
also
be
interesting.
A
B
I
didn't
know
this
was
gonna,
be
ongoing,
but
sorry
so
I
did
infra
and
I
did
releases.
So
the
IRC,
the
getter
and
The
Matrix
rooms
are
all
linked
up
into
one
spot.
Now,
I
haven't
heard
any
complaints,
but
I
also
don't
know
how
many
people
are
using
them.
So.
B
Yeah
the
key
thing
here
that
I
think
there
might
have
been
confusion
earlier
I'm,
not
linking
all
IRC
channels
to
one
spot,
all
my
guitar
channels
to
one
spot
I'm
only
linking
the
verticals
across
one
right,
making
it
a
horizontal
link,
so
all
releases
channels
will
be
together.
All
infra
channels
will
be
together.
Eventually,
the
Jenkins
IRC,
the
Jenkins
getter
and
the
Jenkins
Matrix
will
be
together,
but
I'm
not
making
them
all
one
giant
room
got
it.
A
B
A
B
A
A
D
B
It's
a
it's
a
win
right:
let's,
let's
call
it
a
win
for
that.
A
B
I
have
there's
nothing
across
maleness
or
chat.
That
I
saw
that
should
get
brought
up.
I
would
love
to
see
some
sort
of
screenshot
or
demo
in
the
forums
about
the
new
cleaned
up
pipeline
viewer,
but
yeah.
A
Oh,
oh,
oh,
that's,
that's
an
easy
one
right!
Well,
actually,
so
so
I
have
to
admit:
Darren,
Pope
and
I
are
going
to
do
a
live
stream
tomorrow.
A
That
will
include
the
pipeline
viewer
as
part
of
it.
So
so
we
can
post
that
a
link
to
that
video
into
the
into
the
channel
if
into
one
of
the
community
Pages.
If
that's
okay
with
you.
A
B
A
Show
the
pipeline
graph
viewer
and
for
me
it
was
it
was
really.
It
was
a
delightful
thing
that
I
was
actually
able
to
remove
blue
ocean
from
my
Jenkins
installation
and
still
can
render
pipeline
graphs
and
see
them
that
I'm,
not
as
thrilled
with
the
log
viewing
experience.
But
it's
it's
workable.
So.
B
And
the
big
reason
I
wanted
to
make
sure
that
we
mentioned
that
plug-in
like
when
we're
doing
the
the
blue
ocean.
Docs
was
because
it's
contributable
solution
is
not
right
and,
while
you
can
spend
you
know
three
months
trying
to
figure
out
how
to
build
blue
ocean
the
it's
not
really
sustainable.
If
anyone
knew.
B
B
Okay,
so
I
got
all
all
the
the
rooms
and
things
so
in-friend
releases
are
done.
Some
point,
I'll
do
the
others,
but
I
just
wanted
to
see
how
well
they
work
before
I
touched
them
again.
Anything
else.
D
Regarding
chats,
would
it
be
a
good
idea,
I
think,
to
update
Jenkins
IO
chat,
so
the
documentation
there,
especially
if,
if
we're
doing
linked
channels,
I
think
that
the
entire
page
needs
an
overhaul,
because,
right
now,
it's
basically
split
by
technology
or
I,
don't
know
I
just
thought.
You
know
this
might
need
some
documentation.
Basically,
there's
the
release,
chat
and
whatever
technology
you're
using
you
can
join
it.
We
are
these
methods
that.
A
B
Yeah
I
was
actually
yeah
figuring.
It
was
going
to
be
something
I'd
help
out
with
anyway,
so
of
course
great
all
right
and
then
once
we
get
this
working
like
once,
this
is
working
reliably.
No
one
has
any
major
complaints,
I'll
go
back
to
the
Matrix
and
get
her
people
and
be
like
here's
our
list
of
all
the
rooms,
and
we
want
to
migrate
all
of
them,
but
I
figure.
These
were
somewhat
easy
low
traffic
ones
that
didn't
involve
the
entire
Community.
To
start
with
great.