►
From YouTube: 2023 03 02 Docs Office Hours 1
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
Okay,
welcome
to
Jenkins
documentation,
office
hours
today
is
March
2nd,
and
this
is
the
US
EU
Edition
today
in
as
far
as
attendees
go,
we
have
myself
Bruno,
Brockton
and
Mark
White.
A
Thank
you
for
joining
and
if
anyone
joins
in
while
we're
going
through
things,
we'll
welcome
them
as
well
on
the
agenda
today,
I
have
a
few
action
items,
just
some
new
blog
posts
to
mention
and
point
out
specifically
Bruno's
newest
one
that
we
published
this
week
updates
on
the
week
leave
of
this
past
week
and
LTS
2.38
7.1.
A
Some
talk
about
the
the
Jenkins
Awards
2023.
There
is
some
timeline
that
we
want
to
talk
about.
The
nominations
close
tomorrow,
documentation
transition
to
drop
a
17
and
what
that
might
entail.
Look
like
improving
end
of
life
notifications.
So
when
we
do
get
to
end
life
of
some
of
these,
these
platforms
products
different
softwares.
A
We
can
go
through
and
make
sure
that
everything
is
updated
and
modified
accurately
correctly
and
then
talk
in
addition
to
that
and
a
checklist
to
make
sure
we're
going
to
the
right
places
places
that
we
might
not
think
of
right
off
the
top
of
our
head
or
just
in
general,
good
places
to
look
for
anything
that
needs
updating
some
preparation
for
the
cento7
end
of
life.
This
is
Mark's
proposal
and
something
that
we've
been
discussing
for
a
few
weeks
now
so
just
more
discussion
on
that.
A
Is
there
anything
else
that
you
want
to
put
on
the
agenda
or
does
that
cover
things
for
everyone
at
this
time?.
A
Very
much
Mark,
okay,
so
first
things,
first
again,
some
blog
posts
that
we've
had
published.
Recently
we
have
our
fostom
recap,
which
is
really
wonderful
and
lovely
and
is
was
created
by
all
of
our
Jenkins
attendees
to
fostem.
So
lots
of
wonderful
insight
and
experiences
and
stories
to
share
there
and
some
really
great
photography
as
well.
A
We
published
the
Google
sort
of
code
participation
announcement,
so
Jenkins
has
been
announced
as
a
participating
Organization
for
mentorship.
So
that's
just
us
celebrating
that,
and
it
has.
It
contains
links
to
other
pieces
of
Google
summer
of
code
information
tips
for
mentors
contributors
proposal,
ideas
Etc.
We
also
published
a
blog
post,
announcing
the
CDF,
the
CD
Foundation
Awards,
so
these
are
now
being
hosted
by
each
project
individually
if
they've
graduated
to
that
level.
A
So
that
means
us
and
tecton
I
know
for
sure
have
their
own
awards
that
we're
hosting
these
are
being
hosted
in
the
jenkins.io
repo.
So
one
of
the
biggest
differences
between
this
year
and
last
year-
and
we'll
talk
more
about
that
in
just
a
moment
and
then.
Lastly,
this
is
again
the
blog
post
that
we
have
published
this
week.
This
is
direct
from
Bruno
and
how
to
build
an
unsigned
Jenkins
MSI
on
your
Windows
machine
Bruno.
Is
there
any
in
any
sort
of
elevator
pitch
or
anything?
Well,.
C
I'm
afraid
it's
really
straightforward,
it's
a
no-brainer
just
copy
and
paste,
and
this
should
work
for
you.
You
know
what
you
don't
know
yet
how
to
build
one,
it's
kind
of
difficult,
but
once
you
follow
the
instructions.
Frankly,
it's
pretty
simple
and
I
know
it
already
has
help
warm
people
so
goal
reached
thanks
for
your
help
in
reviewing
that
short
piece
of
documentation,
Kevin.
A
A
Okay!
Next
up
we
have
our
weekly
of
this
week,
which
was
2.393
that
went
successfully.
Change
log
has
been
updated
and
merged
accordingly.
So
that's
up
to
date
for
this
weekly
and
we'll
continue
the
same
process
as
we
go
forward
and
we
fit
each
weekly.
A
We
also
have
our
next
LTS
releasing
on
March
8th,
so
next
Wednesday
this
is
going
to
be
version
2.387.1.
So
a
very
large
change.
A
Mark
Wilson
needs
to
do
his
review,
but
he's
aware
of
it
so
I'm
not
gonna
mention
that
again,
but
yeah
any
notes
on
the
LTS
release,
Mark
or
anything
else
that
we
should
be
aware
of.
B
A
It's
okay:
it
was
pretty
recent
time.
No
worries
cool
next
up
on
the
list
are
the
2023
Jenkins
Awards,
in
conjunction
with
the
continuous
delivery
Foundation.
So
we
have
three
Awards.
We
have
the
most
valuable
Jenkins
contributor
award,
the
Jenkins
security
MVP
award
and
the
most
valuable
Jenkins
Advocate
award.
We're
hosting
these
like
I,
said
in
the
jenkins.io
repo
and
to
contribute
a
nomination
or
submit
a
nomination.
A
All
you
would
need
to
do
is
go
to
the
respective
award
you'd
want
to
nominate
for
and
provide
a
comment
here
explaining
who
you
want
to
nominate
and
why
the
people
can
you
know,
voice
off
in
the
comments
or
the
Emojis
and
respond
to
it.
Let
people
know
that
they're
in
favor
of
this
I'm
pretty
sure
there's
a
lot
more
nominations
on
the
Jenkins
Advocate
yeah.
So
we
are
getting
some
action
on
here
and
we'd
love
it
if
more
of
the
community
want,
would
participate
and
engage
as
well.
A
If
there's
someone
you
can
think
of
that,
you've
worked
with
by
all
means
feel
free
to
highlight
them
here,
even
if
they
aren't
winning
it.
It's
still
nice
to
know
and
still
great
to
have
that
appreciation
coming
from
anywhere
denominations
are
open
until
tomorrow,
Friday
March
3rd.
So
you
do
have
time
between
today
and
then
to
submit
those
nominations
and
then,
when
the
nominations
close
voting
will
take
place
later
via
Google
form
and
that'll
be
distributed
and
handed
handled
by
both
Jenkins
and
the
continuous
delivery
foundation.
A
So
more
details
to
come
on
that
you
do
need
a
GitHub
account
to
vote
and
nominate
since
the
issues
are
in
GitHub,
and
something
to
note
is
that
last
year's
winners
cannot
win
the
same
award
this
year.
So
basil
cannot
be
the
most
valuable
Jenkins
contributor
again,
despite
how
I
might
feel
about
that
Jenkins
security
MVP,
so
lodic,
unfortunately,
cannot
be
MVP
again.