►
From YouTube: Jenkins Governance Meeting, Jan 27, 2021
Description
Recording of the Jenkins Governance meeting. We discussed the recent news, FOSDEM, cdCon, and the Jenkins contributor summit. Full agenda and meeting notes: https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.v4sls9rnbtoa
A
A
B
A
Yeah,
so
it
might
be
related
to
the
changes,
no,
no,
and
so
for
frequency.
We
also
have
new
release
with
additional
patches.
So
please
upgrade
to
the
latest
version,
and
here
we
have
four
regressions,
but
all
of
them
are
reported
to
the
token
macro,
plugin
and
yeah.
This
was
actually
fixed
long
ago.
So
I
didn't
quite
get
what
happened,
but.
A
B
B
A
B
D
B
Yeah,
so
so,
with
a
good
question,
we've
got
olivier.
Bernini
has
outlined
that
the
stand
has
a
website
that
we
can
use
to
place
some
content
on.
He
recommends
that
we
have
an
agenda
so
that
we
can
invite
participants
for
specific
topics,
and-
and
so
during
your
session,
for
instance,
it
might
be
a
great
excuse
if
you'd
be
willing
to
talk
about
warnings
and
how
to
use.
I
just
had
a
request
today
on
hey.
B
How
do
we
use
static
analysis
and
how
do
we
present
results
and
if
you
would
be
willing
to
demonstrate
that
during
your
time
we
could
put
that
on
the
agenda.
During
my
time
I
proposed
hey,
I'm
going
to
talk
about
the
git
plug-in
things
that
I
already
know
and
we
can
we
can
discuss
the
idea
was
that
way
they
have
agenda
items
their
people
know.
Oh,
go
there
to
talk
to
so,
and
this
person
about
this
specific
topic.
D
D
B
F
F
F
If
there's
interest
from
the
community
to
go
beyond
the
normal
cd
con
and
do
something
like
a
contributor
summit-
and
I
bring
that
up
because
we're
working
with
the
spinnaker
community
and
and
they're
going
to
be
doing
a
kind
of
spinnaker
summit
colo
with
cdcon
so
yeah.
For
now.
I
just
encourage
folks
to
register,
submit
talks
and
then
maybe
tomorrow's
advocacy
and
outreach
meeting
is
a
good
place
to
get
into
some
deeper
discussions
about
jenkins
presence
at
there.
F
F
D
B
B
B
F
B
C
So
I've
never
actually
made
it
to
one
of
the
contributor
summits.
So
when
you
pitch
the
idea
of
doing
it,
you
know
the
the
concept
or
sorry
pitch
the
idea
of
and
the
suggestions
of
people
to
do
them
no
that's
backwards.
The
suggested
topics
that
people
might
want
to
do
is
what
you
were
talking
about.
I
actually
really
like
the
idea
of
doing
the
communication
channel.
C
B
Good
good
point
and
so
gavin,
if
it's
okay,
let
me
take
that
up
with
you
I'll
try
to
outline
it
in
the
in
the
document
here
framing
what
I
think
is
a
rough
agenda
and
then
I
may
ask
for
some
of
your
time
one-on-one
to
help
me
refine
it
better,
so
that
you,
as
my
first
test,
can
tell
me
mark
that
didn't
help
me
at
all.
I
need
this
other
information.
C
B
Perfect,
so
I
will,
I
will
engage
with
you
for
that,
because
that
I
wasn't
sure
that
the
communication
channels
topic
would
be
selected,
but
I
thought
you
were
a
great
candidate
for
it.
I
would
love
you
as
my
test
drive,
even
if
we
ultimately
don't
do
that
topic.
You're
a
great
test
drive
to
see
that
I
get
the
right
instructions
we'll
do.
That
sounds
good.
B
B
Right
and
then
there
is
a,
I
drafted,
a
security
track
that
for
me,
wasn't
so
much
about
pipeline
as
about
general
security
topics,
and
but
I
think,
securing
the
pipeline
is
probably
going
to
get
more
interest
and
more
attention
and
we
may
set
aside
the
notion
I
had
of
a
security
track
and
those
those
are
all
fine.
That's
why
this
agenda
is.
There
is
a
rough
draft
and
we'll
we'll
continue
to
refine
it,
and
that's
that's
really
all
that
I
had
on
the
topic
for
contributor
summit.
F
B
We'll
we'll
just
at
least
my
assumption
is
that
the
the
opening
and
the
closing
will
be
zoom
sessions,
and
I'm
assuming
most
of
the
sessions
during
will
also
be
zoomed.
You
know,
most
of
the
tracks
will
be
zoomed,
for
instance,
I'll
probably
put
the
documentation
track
on
my
personal
zoom
account
just
to
make
make
it
easy
for
me
to
administer
and
the
the
opening
and
the
closing
will
definitely
use
the
jenkins.
The
cd
foundation
zoom
account.
A
So
what
we
had
today
is
we
are
contributing
onboarding
junkie
security
became
a
part
of
the
contributor
summit,
and
then
we
have
six
communication
channels
and
terminologically
now.
So
this
what
we
discussed
as
priorities,
so
I
wonder
whether
we
see
any
other
priorities
we
would
like
to
facilitate
and
to
highlight
the
fun.
B
B
A
F
Yeah
one
thing
I
was
just
going
to
add:
I
see
the
point
about
working
closely
with
cdf.
I
think
to
maybe
just
try
and
facilitate
that,
as
we're
also
kind
of
doing
our
planning
for
the
year
at
the
moment
is
maybe
at
the
next
board
meeting
we'll
we'll
have
a
survey
which
we'd
love
to
farm
out
to
to
maintainers
and
contributors
and
just
hear
individuals
feedback
on
yeah.
F
What
programs
of
cdf
are
useful,
what
people
are
aware
of
and
what
other
things
like
jenkins
folks
would
like
to
see
from
cdf,
so
yeah,
maybe
at
the
next
governance
meeting,
we'll
we'll
bring
that
along
and
provide
a
link
and
ask
that
you
share
with
the
community
or
certainly
feedback
from
the
governing
board.
So
we
can
plan.
F
F
D
F
New
events,
we're
likely
to
to
kind
of
follow,
cncf's,
lead
and
switch
to
bevi
as
a
platform,
so
we'll
be
encouraging
anyone
who
wants
to
adopt
it.
The
folks
who
are
using
it
says
there's
a
bit
of
a
like.
It's
a
there's,
a
bit
of
a
step
to
to
transfer
meetups.
So
you
know
that
will
be
optional,
but
folks
who
want
to
start
new,
meetups
or
kind
of
meetups
focused
on
a
slightly
different
angle.
F
F
F
C
C
F
F
F
They
are,
I
think,
launching
it
imminently
like
relaunching
it,
even
though
the
tools
have
been
around
for
a
while,
but
we'd
love
to
have
a
conversation
about
like
jenkins
on
these
tools,
and
you
will
see
as
part
of
that
sweet
there's.
The
insights
which
you
know
jenkins
already
has
a
page,
but
we
need
to
kind
of
sync
with
you
to
work
out
if
that's
useful
or
if
there's
stuff
you'd
like
to
see
there
and
then
there's
a
link
to
community
events
and
under
the
hood,
that's
just
going
to
be
bevy.
A
F
So
but
yeah,
I
think
this
is
something
down
the
road
I
haven't
really
dived
into
it
too
much.
So
that's
like
at
the
moment.
I
could
funnel
any
requests
straight
through
to
the
team,
but
I
think
there's
going
to
be
lots
of
powerful
things
there
for
communities
to
take
advantage
of.
So
if
anybody
does
want
to
start
looking
around
and
playing
with
stuff,
we
I'd
love
to
kind
of
work
with
you
to
map
out
which,
which
bits
you
care
about,
which
bits
we
should
make
more
useful
and
and.
B
A
A
A
Yeah
also
for
us,
easy
cla
is
useful
because
our
current
cle
process
is
well.
Firstly,
it's
still
reliant
on
spi.
Secondly,
it's
semi-broken
and
hard
to
manage,
so
we
definitely
could
adopt
that
mentorship
crowdfunding.
We
already
do
it
yeah
and
yeah
what
else
and
there
are
models
before
maybe
somewhere
on
the
tops.
F
A
F
A
Yeah,
I
hope
it
redirects.
So
like
oh,
no,
it's
not
yeah.
I
thought
we
fixed
that,
but
yeah
looks
like
not
so
yeah.
Basically
you
can.
It
still
refers
to
this
community
reach,
but
yeah
generally,
it's
effects
crowdfunding
now
great
okay,
you
can
see
that
we
have
some
money
actually
in
the
coffers.
So
just
in
case
we
need
the
swag
or
other
things.
C
F
C
A
A
A
C
Again,
so
there
was
one
where
the
I
think
it
was
the
github
pull
request
builder
this
week,
specifically
like
I'm,
I
was
against
it
and
I
mean
I
documented
it,
but
I
was
against
it
and
other
people
were
for
it.
If
the
plan
is
to
allow
it,
I
think
it
just
needs
to
be
communicated
in
that
in
a
normal.
In
a
like
formalized
way,
this
the
discussion,
the
should
I
do
it
shouldn't.
I
do
it.
That
thing
is
kind
of
weird.
A
C
C
Do
we
want
to
start
making
sure
that
any
of
the
that
kind
of
marketing
is
is
live
on
our
blog,
even
though
it's
done
by
another
company
and
then
do
we
want
to
make
sure
that
our
blog
gets
auto?
I
talked
to
again,
it's
probably
an
advocacy
thing,
but
I
talked
about
earlier
getting
like
rss
feeds
into
the
various
channels
or
into
the
twitter
thing,
so
that
we
make
sure
that
we're
making
noise
wherever
possible,
because
I
saw
again
on
the
threads
about
jacket,
3.0
we're
having
a
marketing
issue.