►
From YouTube: Jenkins Governance Meeting, Jul 29, 2020
Description
Recording of the regular Jenkins Governance Meeting. At this meting we discussed the recent news (core release automation, next LTS baseline, public roadmap), reviewed results of the "Jenkins master" term replacement voting and next steps, CDF graduation status, Core Infrastructure Initiative checklist and the Jenkins Epipheo video proposal, Full agenda and meeting notes: https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.cgd8zbewht8o
A
We
have
a
few
topics
for
today,
so
we
will
discuss
what
are
the
recent
news
in
the
project
and
we
will
discuss
terminology
updates,
core
release
infrastructure
and
talk
about
the
cdf
graduation
process
and
epiphany
videos
and
also
discuss
our
communication
channels
going
forward
there.
Any
other
topics
which
we
are
missing
here.
A
B
B
Timing
is
very
good,
we're
delighted
with
the
progress
we
expect
that
the
next
release
of
the
lts
in
mid-august
will
also
use
the
court
release
automation.
We
think
we're
we're
ready
to
go
so
yeah
and
that's
and
yes,
olivia
has
agreed
to
host
an
online
or
to
do
an
online
meetup
in
august
discussing
what
we've
learned
from
core
release,
automation,
etc.
A
Yeah
so
sorry
I
haven't
announced
the
meetup
here.
I
will
do
it
tomorrow:
okay,
so
yeah,
thanks
to
all
contributors,
because
it's
a
major
update
and
during
that
we
also
experienced
a
lot
of
issues,
for
example,
this
windows
packaging
thanks
a
lot
to
alex
for
that.
Well
for
fixing
all
the
stuff
and
yeah.
Now
we
are
also
ready
to
ship
the
new
windows
installation
lcs.
A
So
we
will
be
officially
able
to
close
this
item,
which
has
been
in
preview
for
more
than
one
year,
which
is
a
great
achievement
as
well:
okay,
okay,
anything
else
on
corus
automation,
okay,
I'm
going
with
lcs
baseline
selection.
So
it's
just
for
information
of
all
contributors.
Okay,
we
changed
the
process
in
this
spring.
So
now
we
start
the
lcs
baseline
selection
two
weeks
earlier,
and
there
is
a
developer
manufacture
thread
about
choosing
the
new
version,
so
the
version
which
is
expected
to
land
in
mid-september-
and
currently
we
are
working.
A
A
A
B
C
A
Yeah,
I
know
one
topic
related
to
that
is
terminology
backwards,
because
we
agreed
at
the
last
meeting
so
that
we
would
like
to
backport
terminology
so
yeah.
For
me,
it
was
a
particular
interest
to
see
whether
it
would
happen
in
this
release,
but
if
not,
it
will
land
in
september.
So
it's
not
a
huge.
A
A
A
And
only
about
agents
coordinator,
it's
a
bigger
story
or
whatever
it's
called.
We
will
talk
about
it
just
in
a
few
minutes:
okay,
yeah,
just
to
clarify
agent
terminology,
okay,
so
next
important
note
to
that
yeah,
as
we
discussed
at
the
last
governance
meeting,
we
published
the
roadmap.
So
all
the
changes
are
integrated
thanks
a
lot
to
alexa
for
being
a
bdfl
delegate
in
this
story.
A
A
A
D
Sure
so
can
you
guys
hear
me
okay,
yes,
so
the
poll
is
closing
today
mark
I'm
not
sure
what
time
that
actually
happens,
but
the
poll
is
closed
and
then
we
can
take
the
recommendations
from
that
poll
and
bring
them
into
a
governance
meeting
to
discuss
the
replacement
term
or
terms.
However,
we
want
to
define
it,
so
we
should
be
able
to
do
that
in
the
next
governance
meeting.
D
A
Then
next
is
manager
which
95
to
35
so
taking
the
total
number
of
votes,
it's
a
significant
lead
and
then
a
coordinator
which
is
quite
close
to
manager,
then
primary,
which
is
quite
close
to
coordinator
and
then
main
director
lead
and
executive.
Quite
behind.
So
basically
we
have
one
front
runner
three
terms
which
got
pretty
much
similar
results.
A
D
Run
them
through
google
translate
and
see
kind
of
if
there's
any
reach
out
some
of
the
members
of
the
community
who
speak
those
languages
and
have
them
give
us
a
little
bit
of
feedback
just
so
we
don't
pick
a
term
that
has
negative
connotations
in
another
language
or
some
bias
as
well.
So
we
we
just
want
to
make
sure
that
from
that
from
this,
we
don't
introduce
additional
issues.
So
that's
why
I'd
like
to
wait
until
next
governance
meeting
to
discuss
it.
A
D
Agreed
that
was-
and
I
apologize
for
not
responding
to
that
on
the
mailing
list.
I
think
this
one
is
specifically
about
the
server
is
kind
of
what
we're
talking
about
the
node
term
is
something
that
we
can
that
we
can
also
think
about,
but
I
I
agree
that
controller
does
not
make
sense
for
the
main
node
or
what
used
to
be
called
the
master
node.
So
that
is
definitely
something
we
need
to
think
about
as
well.
A
B
A
D
That's
going
to
take
a
lot
of
research
and
so
forth,
because
it's
all
over
the
place-
and
I
I
know
it's
it's
not
as
visible
as
within
the
ui
and
documentation
things
like
that,
but
it.
I
know,
lots
of
people
go
look
at
the
source
code
when
they're
doing
things,
and
so
it
is
still
a
very
visible
portion
that
would
be
nice
to
to
fix
up
things
like
dumb
slave.
You
know
that
that
would
be
one
of
my
very
first
things
that
I
would
want
to
to
address
and
things
like
that.
A
C
Alex
could
clarify
whether
you
would
say
the
source
code,
changes
or
internal
changes
are
within
the
scope
of
the
master
renaming,
or
is
that
a
separate
project
altogether?
Because
so
far
I
had
the
impression
that,
similar
to
what
we
did
with
agent,
we
would
look
at
labels,
documentation
and
such
first.
D
Yeah
that
you're
absolutely
correct.
It's
not
part
of
this
current
master,
it's!
It
is
a
next
step
in
the
process
of
cleaning
up
terminology
and
jenkins.
It's
not
part
of
this
master
rename.
So
it's
not
something
that
I'm
looking
at
doing
as
a
short
term
or
or
you
know
within
this
rename.
It
is
something
for
the
future.
C
A
D
A
A
Probably
we
want
to
break
it
down
and
move
for
epa
and
classes
to
future
because
yeah,
basically
it
makes
sense
to
update
agent
terminal,
jpi
and
master
terminology
api
at
the
same
time.
Theoretically,
but
yeah,
it's
a
implementation
detail.
I
just
agree
with
daniel
that
we
won't
be
able
to
do
it
soon.
D
A
D
I
think
we
communicate
once
we've
decided.
We
already
said
that
the
poll
is
is
closing
on
july
29th,
so
I
don't
think
we
need
to
resend
out
information
about
that.
However,
I
think
definitely,
once
we
make
the
decision,
we
can
send
something
out
to
the
dev
list
as
a
follow-up
to
the
terminology
updates
thread
that
we
had.
A
D
A
B
A
A
C
C
C
D
Yeah
and
that's
something
that
we
brought
up
on
the
mailing
list
too,
I
think
or
in
the
governance
meeting
a
few
weeks
ago,
or
something
that
definitely
it
doesn't
have
to
just
be
a
search,
replace
white
list
to
allow
lists
and
so
forth,
to
actually
look
at
what's
written
there.
And
if
it's
there's
a
better
way
to
explain
the
context,
then
that's
absolutely
great.
C
A
Okay
yeah:
this
is
a
great
thing
actually,
so
we
should
also
keep
cleaning
it
up.
Fortunately,
the
exposure
in
the
code
base
is
much
lower
well,
except
the
white
list
annotation
in
pipeline
api,
but
yeah.
I
think
that
we
can
do
something
about
that,
because
annotations
can
be
inherited.
So
it's
basically
a
small
matter
of
programming
to
get
it
updated.
A
Okay,
let's
move
on
then
so
to
pick
up
this
one
is
current
transaction
initiative,
so
I
posted
the
update
to
the
developer
mailing
list,
so
great
news
actually
officially
passing
the
ci
criteria
so
what
it
means
that
we
have.
We
are
compliant
with
all
the
basic
criteria
defined
by
call
infrastructure
initiative.
A
So
you
can
find
there
are
some
descriptions
and
answers
which
provide
more
details
about
what
we
do,
what
we
don't
do,
etc
and
in
addition
to
that,
we
started
reviewing
criteria
for
silver
and
gold
level,
so
in
cia
in
total
you
can
get
to
300
so
right
now
we
at
133,
but
it's
enough
to
get
a
passing
page.
So
right
now
it's
applied
and
it's
also
available
on
our
call
request.
Alright.
So
now,
if
you
go
here,
you
can
actually
see
cia
bridge
just
to
have
it.
A
So
this
story
is
far
from
being
completed,
because
if
we
go
after
silver
and
gold
criteria,
there
is
a
lot
of
requirements.
Some
of
these
requirements
well
they're
quite
arguable,
but
they
want
to
comply
with
them.
Some
of
them
are
quite
reasonable
and
it's
a
matter
of
improvements
so
yeah
we
can
do
a
lot,
but
it's
not
on
the
table
right
now.
So
if
someone
wants
to
keep
working
on
that,
please
feel
free
to
contribute
to
suggest
changes.
I
will
be
happy
to
incorporate
them,
but
yeah,
at
least
in
the
coming
months.
A
Looks
like
no
okay,
the
next
one
is
cdf
radiation.
So
yeah,
like
we
discussed
at
the
last
meeting,
I
submitted
a
request
to
cdf
to
start
the
graduation
process
on
july
21st.
There
was
a
cdf
talk
meeting
where
we
briefly
presented
what
we
changed
in
the
process
and
we
presented
our
compliance
checklist,
which
is
full
green
and
just
second
I'll
show
it
to
you.
A
Cdf
talk
started
offline
vote
in
the
mailing
list,
so
you
can
see
the
results
of
vote
here.
Actually,
the
vote
is
still
ungoing,
but
we've
got
a
bunch
of
plus
ones,
including
a
number
of
plus
ones
from
talk
members,
so
by
make
ones-
and
it
looks
like
really
positive,
so
we
are
waiting
for
official
announcement,
but
it
looks
like
everything
is
on
track
there.
There
was
no
concerns
and
I
believe
that
we
will
do
it
as
planned.
D
A
E
Yeah,
so
thanks
to
cloudbees,
they
gave
me
as
a
chunk
of
many
money
to
to
create
a
video
that
talks
about
jenkins
and
the
goal
of
the
video
is
to
help
basically
promote
jenkins
and
see
to
let
people
know
why
jenkins
is
so
great
right
and
we
we
want
to
attract
more
jenkins
users.
Of
course,
more
people
to
the
community,
and
my
goal
is
to
have
this
played
on
jenkins.io
and
in
social
media
as
well.
A
E
E
B
E
A
A
E
B
Could
no
we
should,
I
think
it
should
be.
We
should,
I
think
we
should
host
the
video
on
youtube,
but
we'll
present
it
through
the
page
on
jenkins.io
from
the
youtube
hosting
oleg.
I
think
what
your
your
observation
was
is
we
need.
We
need
somebody
assigned
that
takes
that
and
says:
okay,
let's
make
sure
it
works
within
the
context
of
that
page
and
that'd
be
part
of
the
pull
request
to
make
it
work.
A
Yeah,
so
we
can't
easily
put
it
on
jumbotron,
because
most
likely
everything
will
go
crazy.
If
you
try
to
embed
video
here
right,
yeah,
embedding
it
here
in
a
static
context.
Yes,
it's
doable
at
the
same
time.
You
have
never
tried
it
so
right.
Well,
somebody
would
need
to
implement
it
and
yeah.
If
it's
hosted
on
youtube,
we
could
embed
player.
We
actually
did
it
for
a
few
blog
posts
before
so
we
used
embed
video
there
just
second
I'm
looking
for
a
blog
post.
We
should
be
doing
that.
A
B
So,
oh
like
this
is
when
I'd
propose,
let
me
take
the
assignment
to
work
with
alyssa
on,
given
that
it's
I've
got
the
documentation
officer
title,
and
this
is
really
something
that
goes
into
the
docs.
Let
me
take
that
and
if
I'm
not
able
to
fit
it,
capacity-wise
I'll
go
looking
for
somebody
else
to
help
me.
A
A
B
E
C
C
C
C
A
D
A
A
A
E
A
A
At
least
you
know,
we
see
people
because
yeah
in
rc,
it's
also
difficult
to
get
participants.
So
it's
not
something
like
university.
We
had
more
participants,
especially
during
july
august
time
frame,
so
I'm
not
too
concerned
about
switching
to
zoom.
My
main
concern
is
actually
about
correctly
doing
meeting
nodes
because
if
you
are
doing
it
in
irc,
basically
everything
is
recorded.
Everything
can
be
tracked
by
participants,
but
if
you
do
it
in
zoom,
then
just
we
have
video
publishing
delay.
A
B
A
B
Agreed
and
that
feels
like
a
good
role
that
whoever
the
scribe
is,
could
take
to
do
that
that
way,
the
the
board
members
don't
have
to
carry
that
burden
and
but
you're
right
absolutely
if
we've
got
a
thread
in
the
dev
list.
That
is
the
place
to
confirm
that
the
governance
board
chose
this
rather
than
making
those
people
go,
find
the
the
governance
board
notes.