►
From YouTube: Jenkins Governance Meeting, Dec 02, 2020
Description
Recording of the Jenkins Governance meeting. At this meeting we announced the 2020 election results and reviewed other ongoing projects in Jenkins governance. Meeting notes: https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.v4sls9rnbtoa
A
A
A
A
A
Can
you
say
that
the
elections
are
over
thanks
to
everyone
who
participated?
It
was
a
several
months
long
process
with
a
lot
of
different
steps
involved,
but
yeah.
Finally,
we
finished
it
be
able
to
turn
on
the
results
and
yeah.
What
are
the
current
results
and
the
final
results
that
for
jenkins
governors
most.
A
Riek,
fred
and
andre,
so
just
I
think
I
would
like
to
say
it
there
that
we've
got
nine
awesome
contributors
and
community
members
on
the
ballot.
So
thanks
to
everyone
who
participated
and
yeah
this
votes
basically,
for
me
it
was
a
really
tough
choice
to
prioritize
the
results.
It
is
the
same
for
many
others.
A
The
final
results
that
mark
and
gavin
will
join
the
governance
board
as
discussed
mark
kind
of
joined
because
of
the
affiliation
requirement.
Unfortunately,
it
happens
a
second
year
in
the
row
and
yeah.
Maybe
so
we
had
some
more
discussions
before
like
expanding
the
jenkins,
the
governance
board
or
maybe
making
additional
adjustments.
A
B
This
is
a
awesome
project
and
I
know
there's
been
a
lot
of
people
that
have
done
a
lot
of
work
here
and
I'm
I
kind
of
lost
for
words,
which
is
a
striking
thing
because
I'm
never
lost
for
works.
I
want
to
thank
those
that
voted.
I
also
want
to
thank
those
that
were
nominated,
there's
a
lot
of
people
that
I'm
extremely
close
to
and
and
do
a
lot
of
work
in
this
community,
so
I'm
just
thankful
all
around
for
everybody.
Thank
you
very
much.
C
D
Congratulations
to
everybody.
It
was
really
impressive
again
how
many
people
voted
and
yeah
I'm
happy
about
that.
We
are
have
three
new
members
or
two
new
members,
so
yeah,
because
mark
again
is
not
allowed
to
join,
but
maybe
we
can
change
change
that
in
later
on.
If
we
have
it
in
the
next
election
that
we
have
more
people
in
the
pawn.
E
F
Hi,
this
is
tracy
yeah,
just
going
to
say,
congratulations
all
round
great
additions
to
the
board
mark
you
you,
you
get
to
to
win
it
without
actually
having
to
join.
I
think
that's
a
good
and
we've
got
a
cdf
newsletter
going
out,
so
I
think
we
will
add
a
line
in
there
just
to
to
mention
that
in
the
newsletter
sounds
like
great
news
to
share
far
and.
F
A
A
Thanks
everyone
for
the
feedback
and
again
governance
support
is
mostly
a
representative
body.
We
have
a
lot
more
community
leaders
helping
with
different
roles,
including
all
participants
on
this
list
and
many
other
contributors
so
yeah.
The
jenkins
community
is
strong
because
we
have
a
lot
of
participants
in
different
roles
official
or
not,
and
it
helps
us
to
move
forward.
A
Okay,
speaking
of
other
roles,
we
also
had
elections
for
jenkins
release
officer,
as
it
was
announced
in
the
developer
mailing
feast.
Oliver
decided
to
step
down
starting
from
december,
so
we
have
just
had
jenkins
lcs
release,
2.
263.1
and
this
release
was
created
by
oliver
in
terms
of
backporting,
and
it
was
the
last
release.
I
would
like
to
thank
oliver
for
all
his
hard
work
on
this
position,
because
oliver
was
leading
lcs
process
since
2013
or
2012.,
so
it
was
long
ago
and
yeah.
It's
much
appreciated.
A
A
Okay,
so
for
release
officer
results.
Unfortunately,
we
don't
have
team
on
the
call,
as
I
proposed
in
the
mailing
list,
we
will
do
another
session,
maybe
next
week
with
introductions.
Maybe
we
even
organize
it
as
online
meetup
and
something
to
discuss
yeah
again
for
the
release
officer.
We
had
three
awesome
contributors
who
helped
these
jenkins.
So
team
has
been
active
contributors
to
the
jenkins
core
over
the
past
two
years
he
created
operations
called
plugin,
also
dark
team.
A
Also,
you
have
batista
matus
and
victor
martinez
participating.
Most
of
them
also
contributed
to
various
areas
of
the
gentiles
coming,
including
release
processes,
automation
and
the
jenkins
corman
cannons
thanks
to
them
and
again
yeah.
Both
of
them
are
contributors
and
let's
keep
working
in
the
community.
A
B
A
A
A
No,
I
didn't
so
that's.
Basically,
it
concludes
the
elections,
so
the
next
steps
is
to,
firstly
send
the
announcement
in
the
developer
mailing
list.
I
will
do
it
tomorrow
on
the
morning
in
my
time
zone
and
I
also
have
a
blog
post
works.
I
target
to
publish
it
in
24
hours
or
so,
but
before
that
I
will
send
it
for
review
by
others,
so
it
might
be
slightly
delayed
and
in
the
worst
case
we
might
miss
publishing
it
tomorrow,
but
the
official
announcement
will
go
to
the
developer
manager.
A
This
retrospective
document
is
mostly
at
the
moment.
My
suggestion
is
that
we
do
it
asynchronously,
so
every
contributor
is
welcome
to
participate
and
share
feedback,
and,
after
that,
we
process
this
feedback
and
think
how
we
could
make
the
next
elections
better.
These
elections
were
the
second
ones
in
the
jenkins
history.
Last
elections
in
2019
have
been
driven
by
tracy
olivia
mark,
and
it
was
our
first
experience.
A
F
Yeah
and
just
to
add
like
I,
I
got
to
step
back
and
just
enjoy
it
as
someone
voting
this
year
and
certainly
from
my
perspective,
it
all
seemed
to
go
really
smoothly
and
really
well
done,
and
no
one's
counting
votes
for
months
to
come
so
but
yeah.
No.
I
I
think
it's
really
nice
to
see
so
many
candidates
and
to
see
all
the
the
interest
in
the
community
that
the
elections
bring
so
yeah.
Congratulations
all
around.
E
I
think
your
observations
on
points
of
feedback
in
the
document
are
spot
on
are
exactly
correct.
Low
registration
numbers
is
an
interesting
one
that
I'm
not
sure
how
we
address
it,
but
I'm
fascinated
by
it.
Last
year
we
had
we
had
we,
we
must
have
sent
what
almost
100
000
email
messages
and
and
had
a
larger
registration.
We
did
this
year,
but
this
year
we
decided
not
to
bomb
mailbomb
people
at
the
same
way.
We
did
last
year.
C
A
So
last
year
it
was
almost
300
votes.
This
year
was
almost
17.,
so
yeah.
If
you
want
to
see
the
numbers,
you
can
just
go
here
so
here
the
numbers
are
here.
So
this
is
governance,
board
collections,
65,
volters
and
94
registered
voters.
So
it's
after
processing
of
registrations,
duplication
clarification,
so
the
numbers
are
considerably
lower
than
in
previous
year.
A
A
E
A
A
A
Anyway,
think
that
we
can
park
this
topic
and
again
thanks
to
everyone
who
participated,
who
voted
thanks
to
all
the
candidates
and
yeah
it's
great
to
have
the
elections
over
and
hopefully
small
contributors
and
roles.
Now
we
can
continue
pushing
the
jenkins
project
and
thinking
involving
its
roadmap
and
facilitate
other
critical
initiatives.
We
have
community
and
shapers
and
technical
initiatives.
C
A
A
A
E
E
I
received
a
call
this
morning
about
about
six
hours
ago
from
microsoft:
support
in
europe
reporting
that
gee
didn't
you
do
asking
didn't
you
do
something
that
fixed
it?
No,
we
really
didn't
and
they
are
now
going
to
report
back
trying
to
find
the
root
cause
from
their
side
olivier's
plan.
There
is
to
switch
back
to
the
to
the
original
solution,
either
late
this
week
or
early
next
week,
because
it
does
seem
to
be
running
again
and
it
lets
us
use
azure,
azure
file,
storage
in
a
very
elegant
and
direct
technique.
E
G
A
A
Okay.
So
again,
thanks
to
everyone
who
was
involved
and
yeah,
it
was
quite
an
expected
outage,
but
yeah
into
this
we
were
able
to
basically
rebuild
the
functionality
using
another
platform
and
yeah.
This
is
a
functionality
that
serves
hundreds
thousands
of
downloads
every
month.
So
it's
not
something
scale,
matters
mirrors
matter
and
also
there
is
a
lot
of
associated
costs
little
bit
so
that
they
will
be
able
to
fix
it
quickly.
A
Okay,
lcs
release
yeah.
We
have
one
again
thanks
to
everyone
who
was
involved,
and
I
guess
it's
all
in
place
now.
So
if
you
go
to
changelog's
table,
you
can
see
the
release.
There
are
upgrade
guidelines
and
everything
looks
pretty
good,
so
yeah
this
process
runs
well
and
again
it
uses
a
new
automation
infrastructure.
A
A
So
for
us
another
interesting
topic
that
we
will
be
doing
the
winter
break
according
to
our
current
process,
we
should
have
created
the
release
candidate
in
late
december,
and
you
should
have
done
the
final
release
on
30th
of
december
or
something
like
that
for
the
two.
So
we
decided
to
postpone
it
by
two
weeks
and
yeah.
A
Okay,
anything
else
about
releases.
Okay,
then
the
quick
update
on
google
summer
of
code.
It
will
happen,
there'll
be
some
changes
in
the
process,
but
largely
it
remains
the
same.
In
the
previous
years,
you
have
restarted
office
hours.
We
are
looking
for
mentors
project
ideas,
so
if
everyone
is
interested,
if
anyone
is
interested,
please
join
us
using
the
standard
channels
and
everything
is
in
place.
A
A
A
I
think
we
could
just
do
office
hours
if
the
timing
is
fine
with
you
and
you
could
revisit
timing
if
you
want
to
find
another
slot.
So,
okay,
thank
you.
Historically,
we
start
our
main
meetings.
One
of
the
student
application
phase
is
over
because
this
one
we
need
to
make
decisions
to
review
the
applications
and
to
do
other
to
do
other
sensitive
things
which
just
cannot
be
discussed
in
public.
A
Then
yeah
just
for
your
information,
there
is
a
discussion
about
jenkins
3x.
This
discussion
has
been
started
by
james
north
days
ago,
so
almost
one
week
by
now
there
is
a
lot
of
feedback
and
clearly
we
have
no
consensus
in
this
trade
at
the
moment,
but
yeah.
My
call
is
that
since
now
we
have
a
new
release
officer
board
members
and
we
definitely
need
to
get
back
from
stakeholders
to
understand
whether
we
want
to
plan
for
jps3,
because
it
would
involve
many
different
actions
required
from
the
community
and
from
the
teams
and
plus.
A
A
Largely
it
was
explained
by
the
breaking
changes
we
introduced,
including
tables
to
divs,
which
still
needs
to
be
still
revised
towards
the
next
lcs
release,
plugins,
which
haven't
been
updated
and,
in
addition,
extreme
sdg
security
update
to
string
security
and
jquery
updates,
plus
a
lot
of
other
minor
break
and
changes
here
and
there
mostly
for
duplications,
so
yeah
from
technical
standpoint.
It
might
be
justified
and
we
need
to
discuss
it.
A
C
A
A
So
moving
on
jinx,
kubernetes,
iterator
updates
and
just
we
copied
on
the
status,
so
the
your
development
is
in
different
areas.
Now
we
have
two
operators.
One
is
called
jenkins
iterator,
which
is
the
original
one,
and
now
it's
back
to
the
active
phase
of
the
development
as
it
was
announced
by
victor
schwab.
So
there
is
some
development
happening
in
this
repository.
It's
great
and
yeah.
Thanks
a
lot
all
stakeholders
contributing
and
and
yeah.
A
A
A
On
the
same
topic,
there
is
also
a
trademark
some
sub
license
request,
because
schwab
has
launched
a
commercial
product
based
on
the
original
jenkins
separator.
Well,
they
haven't
launched,
yet
they
just
announced
a
private
preview.
So
it's
not
a
face
of
wide
announcements,
and
that
is
a
pending
print.
B
A
Yeah
there's
a
history:
some
bits
of
this
history
are
in
public
in
the
developer
mannequin
threads.
Also
there
is
a
government
sport.
We
are
participating
in
communications
between
parties
looking
for
potential
solution
yeah,
so
there
is
also
a
private
conversation
part
but
yeah.
Well,
not
that
much
of
the
private
part
on
this
stage.
Let's
this
one.
A
A
A
A
A
A
I
suggest
that
we
just
start
a
new
doodle
because
we
have
more
contributors
joining
and
yet
this
slot
has
been
considered
as
complicated
before,
especially
for
europe,
so
we
can
try
to
find
another
slot,
maybe
even
on
another
day,
let's
see
whether
we
can
find
something
I
will
start
the
doodle.
Maybe.
A
B
A
B
B
E
A
A
B
A
B
C
A
So
I
didn't
expect
to
get
them
soon,
because
from
what
I
discovered
the
october
first
main
block
force
and
mail
status
report
is
not
ready
yet
okay,
so
the
breakfast
team
is
especially
focusing
on
getting
their
own
results
out
of
the
door
and
after
that
they
may
be
able
to
help
provide
this.
For
us.
A
For
example,
continuous
delivery
foundation
has
already
posted
a
blog
post
today
or
yesterday
about
oktoberfest.
We
shared
some
details
and
statistics
which
was
collected
from
the
public
resources
but
yeah.
That's
a
problem
with
hyper
fest,
because
we
cannot
identify
overall
contributors
say
with
the
current
process.