►
From YouTube: Jenkins Governance Meeting May 18, 2022
Description
Jenkins Governance meeting May 18, 2022 with topics including:
* News
* Action Items
* She Code Africa Contributhon
* Google Summer of Code
* Forums and community topics
A
A
All
right,
so,
let's,
let's
do
the
news?
Look
at
all
the
people!
Exactly
isn't
that
wonderful,
so
I'm
gonna,
I'm
gonna
start
with
a
news
section
then.
So
yesterday
we
had
a
plug-in
security
advisory
thanks
to
the
jenkins
security
team,
for
posting
it
a
number
of
fixes,
interesting
things,
csrf,
etc.
A
So
vulnerabilities
in
various
layers,
credential
exposures,
all
good
fixes
to
have
cross-site
scripting
one
glaring
one
was
the
get
plug-in
released
with
a
problem
in
it.
On
windows
controllers.
The
release
has
been
delivered
to
fix
that
problem.
Sorry
about
that
obviously
didn't
test
well
enough
before
we
released
it
next
piece
june
lts
is
coming
june.
A
A
Next,
next
item
on
the
news
is
java:
11
will
be
required,
no
more
java,
8,
beginning
june
22
21
2022,
so
that
that
release
we
expect,
will
drop
support
for
java,
8
and
jenkins.
That's
in
preparation
for
the
september
lts
that
will
drop
support
for
java
8
all
as
part
of
jenkins
enhanced
proposal.
236
we've
got
jira
epics
that
are
tracking
the
work
thanks
to
basel
thanks
to
audrey
and
le
charpentier
and
others.
This
java
11
phase
5,
is
a
great
example
of
of
a
wonderful
way
to
track
things.
A
C
A
A
All
right
next
part
is
the
action
items
and
I
have
the
action
two
action
items
that
I've
made
no
progress
on
and
won't
make
any
progress
on
for
a
while
fosdem
funds
transfer
from
tracy
miranda
and
linux
foundation,
funds
transfer
from
gsoc
alyssa
tong
on
the
gsoc
one
has
provided
me
some
help
for
pointers,
so
I
may
get
further
traction
there.
Over
the
next
month,
I
asked
cdf
for
a
survey.
Survey
participation
count
on
their
their
survey
and
their
answer
was
right.
Now
they
have
only
18
people
registered
for
the
survey.
A
B
C
To
that
end,
it
might
be,
it
might
be
helpful
to
list
the
services
that
are
already
being
provided
by
the
cdf,
for
example,
one
that
I'm
aware
of
is
the
jira
hosting,
which
is
very
valuable
service.
For
us
I
mean
I
rely
on
jira
to
do
all
of
this
project
tracking
work,
but
maybe
if
we
enumerated
all
of
these
services
that
might
help
people
to
think
to
themselves.
Oh,
I
use
that.
Oh
I
rely
on
that.
You
know
maybe
it'll
be
good
for
me
to
provide
some
positive
feedback
about
this.
B
B
A
Yeah,
so
so
I'm
going
to
ask
those
who
are
here
any
objections
from
any
of
you
if
we
were
to
shift
this
meeting
three
hours
later
for
those
who
are
from
from
the
eu
for
their
benefit
later
or
earlier
later.
Truly
later,
no
earlier
is
bad
for
them
because
it
collides
with
their
work
because
they
intentionally
wanted
to
put
it
in
in
what,
for
me,
sounds
like
the
dark
of
the
night
bruno
with
you
being
in
europe.
It's
probably
your
best
gauge.
A
So
I
take
so
let
me
call
for
I
need
to
see
thumbs
up
to
say
yes,
if
you're,
okay,
with
that
suggestion
for
three
hours
later,
either
way
it's
the
middle
of
my
work
day.
It
doesn't
matter
to
me,
okay,
great
okay,
and
I'm
going
to
assume
those
that
I
don't
see
a
thumbs
up
for
that
you're,
okay,
you're,
not
casting
a
vote,
so
we're
gonna
say
that,
yes,
this
is
approved
and
mark
move.
The
calendar
item.
A
Okay
next
topic,
then
she
code,
africa,
contributon
we've
entered
the
final
reporting
phase
that
will
last
for
roughly
two
weeks,
then
we'll
do
a
concluding
blog
post
on
jenkins.io.
The
posts
on
community.jenkins.io
are
a
reminder
how
much
easier
it
is
to
post
to
community.jenkins.io
than
to
create
a
blog
post.
So
here
is
peace,
peace,
okafor's,
concluding,
post,
nicely,
formatted,
good
headings,
etc.
A
A
We
had
four
or
five
projects
that
we
had
submitted
as
ideas
with
mentors
with
good,
solid
project
plans
with
good
candidates,
and
so
we
hope
we
don't
know
how
many
of
those
will
be
chosen
and
we
won't
know
until
they
officially
announce.
But
we
hope
that
we'll
be
chosen
and
we
look
forward
to
running
those
throughout
the
summer.
A
A
A
Now
we
still
need
we've
still
got
some
some
gaps
there.
One
of
the
gaps
is
internationalizing,
a
plug-in
is
not
as
straightforward
as
it
should
be,
because
the
documentation
is
is
behind
what
the
current
preferred
practices
are,
and
so
one
of
the
things
I
hope
to
do
is
in
the
doc
sig.
We
hope
to
put
better
documentation
about
that
internationalization
process,
so
that
people
do
it
right,
the
first
time
as
they
work
through
their
their
plug-in
development.
D
A
C
A
B
B
B
C
B
C
B
And
I
I
mean,
on
a
personal
level,
that
I
do
want
to
write
up
a
canned
response
for
the
forums
and
maybe
even
for
the
chat.
Oh
there
is
a
board
topic.
Yes,
I
want
to
create
a
kind
of
response
for
just
something
like
I
see
you
have
a
difference
between
environments.
These
are
how
you
can
debug
it.
You
know
like
how
to
print
them
and
stuff
like
that,
but
and
that's
not
a
bug
per
se.
B
That's
just
something,
you
know
stop
gap,
but
there
are
I've,
seen
a
couple
posts
last
couple
weeks
about
people
saying
so,
and
so
it's
broken
and
you're
like
yeah
you
have
to
so
maybe
we
can
make.
I
don't
know
how
we
could
do
it
as
a
on
a
board
level,
but
try
to
make
it
easier
for
people
to
know
that
bugs
are
probably
better
than
chat
rooms.
C
A
B
A
B
That's
not
the
point
of
it,
but
it
could
be
done.
Yes,
the
the
point
was
to
make
the
jenkins
irc
channel
and
the
jenkins
gator
channel
talk
to
each
other,
so
that
you
know
someone
who
wrote
in
one
could
see
it
in
the
other.
I
see
because
right
now
it's
split
and
some
people
are
in
one
sum
in
the
other
got
it:
okay,.
A
A
B
B
There's
stack
overflow,
there's
irc,
there's
getter,
there's
forums,
there's
mailing
lists,
there's
websites,
there's
twitter,
there's
linkedin,
you
know,
and
anyone
needs
help,
picks
one
and
probably
not
the
right
one,
because
only
half
people
are
there
as
much
as
I
would
love
to
see
the
developer's
mailing
list
move
to
the
community
site,
I'm
thinking
it
might
be
worth
just
moving.
The
other
ones
so
like
docs
right
now
is
pretty
heavily
not
using
the
mail
list,
so
it
might
be
a
good
one
to
be
like
hey
we're.
Shutting
down
posting.
B
There's
ability
in
discourse
to
do
a
read-only
clone
of
the
mailing
list,
so
anyone
who
posts
to
the
forums
would
get
a
moderate
post
to
the
topic.
I
don't
know
it's
just
something
that
I'm
like
at
some
point.
We
should
probably
have
discussion
about
this,
but
like
infrastructure,
the
mailing,
this
isn't
really
used.
It's
moved
most
of
the
stuff
is
moved
to
help
desk
and
then
a
few
things
left
over
on
the
info
list.
The
ux
one
is
definitely
not
used
and
those
are
the
ones
I'm
on
I'm
sure,
there's
more
mailings
than
that.
B
A
B
B
A
B
A
A
B
Docs
you
know
my
my
concern
is
that
if
someone
has
a
question
or
they
post
the
wrong
space,
it's
impossible
to
do
anything
about
it.
You
know
we
had
that
issue.
For
the
longest
time,
people
were
posting
for
a
mailing
list
asking
about
their
install
you're
like
nope.
You
got
the
wrong
spot
and
that's
it.
That's
the
end
of
the
conversation
at
least
putting
it
to
the
forums
we
can
be
like
nope
we're
moving
into
this
category.
B
C
A
B
A
A
B
And
then
I'd
like
I
mean
I
could
do
a
demo
at
some
point
in
the
future,
but
the
nice
thing
about
discourse
is
you
have
very
fine
notification
controls
so
I'll
just
for
everyone's
thing
here
on
the
right
of
the
page,
you
have
that
little
bell
right.
You
can
actually
control
what
how
your
notification
will
be
on.
B
B
They
get
an
email,
but
not
every
reply
to
it
and
so
on,
like
you
can
control
it
like
it's
all
manageable
in
your
preferences
as
well,
you
don't
have
to
go
to
each
tag
and
do
it
manually,
but
like
it's,
it's
very
customizable
in
the
same
jira
sense
of
it
right
and
that's
one
thing
that
the
mailing
lists
don't
have.
Is
you
either
get
all
of
it
or
none
of
it
so
yeah?
I
just
think
centralization
is
better,
not
necessarily
that
the
forums
are
the
best
place.
B
B
Yeah
and
we
were
trying
to
abstract
that
as
much
as
we
could
in
the
plug-in
site,
because
people
were
doing
it
anyways
so
that
you
can
very
easily
you
know
have
a
list
of
issues
you
don't
have
to
think
about
where
it
is.
But
I
agree
that
was
one
of
the
issues
we
I
mean
even
years
before.
Most
of
the
people
on
this
caller
were
around.
People
were
wanting
to
use,
get
help
and
we're
like
it
should
be
one
or
the
other,
not
both
both
of
them.
D
And
as
a
very
new
jenkins
user,
I
find
it
really
difficult
to
interact
with
people
within
guitar
and
there
are
so
many
channels
I
think,
last
year,
when
it
was
a
contributors
summit,
you
listed
97
guitar
charm.
I
think
it's
just
like
impossible
to
do
something
seriously
with
that
many
channels.
So
having
a
more
centralized
system,
yes,
would
be
very
useful
for
young
tigers,
yeah.
B
B
A
C
For
all
the
getter
channels,
I'm
sorry
are
they
called
channels
or
rooms?
I
guess
they're
called
rooms
yeah.
Maybe
it
might
help
if
we
define
a
naming
scheme.
For
example,
you
know
x-sig
is
a
namespace
for
these
official
special
interest
groups
and
you
know
you
have
like
x,
dash
plug-in
yeah
for
and
then
so
we
could.
B
Yeah,
I'm
if
it
was
if
it
was
purely.
If
I
could
be
like
dictatorship
and
choose,
it
would
be
getter
matrix
for
any
live
chat,
a
community
site
for
for
everything
else,
and
then
you
know
I
don't
really
care,
but
jira
or
github
for
issues
like
I
said
one
or
the
other
honestly.
If,
if
we
could
integrate
things
a
little
bit
better,
we
probably
wouldn't
even
have
to
worry
about
what
the
answer
is.
You
know,
but
I
it's
so
hard.
It's
be
hard
to
dictate
this.
B
You
know
because
it's
so
spread
out,
so
the
best
we
can
do
is
fix
the
outliers
and
make
the
more
people
who
are
using
community
site,
the
more
we
can
put
on
to
it
and
the
easier
it
is
to
migrate
things
to
it.
So
that's
why,
because
mark
likes
it,
docs
is
my
first
order
of
business
but
yeah,
I
think
renaming
channels.
If
we
can,
I
don't
know
if
we
can
even
rename
channels.
A
C
A
B
Gator
channel
was
created
today
mark.
How
would
you
find
out,
I
I
would
not.
So
how
would
you
know
if
there
are
new
channels
or
not?
Oh,
fair,
point,
okay,
yeah,
I
mean
I
don't
know,
I
don't
know
when
79
was
calculated.
I
don't
know
how
we
did
it
either
so
yeah
I
either
way
it's
just.
This
is
one
of
the
things
that's
been
bugging
me
for
a
long
time
and
I
don't
have
a
solution
for
and
the
only
solution
I
have
is
funnel
people
as
best
we
can
into
one
spot.
A
All
right:
let's,
let's
do
the
experiment,
let's
try
it.
I
like
it
shutting
down
shutting
down
putting
a
tombstone
on
the
the
docs
mailing
list
should
be
pretty
easy
and
if
it
works
and
we
make
it,
we
don't
successfully
make
it
read
only
then,
then
we
shift
the
conversations
to
to
community.jenkins.io
and
we're
set
yeah
yeah.
C
Yeah,
I
think,
in
the
long
term
we
need
to
come
up
with
a
plan
for
the
issue
trackers
because
it's
it's
too
difficult
to
do.
Project
management
with
a
split
yeah
view
of
the
work,
and
there
are
certain
certain
features
or
areas
of
functionality
that
are
present
in
some
issue
trackers,
but
not
others.