►
From YouTube: 2023 02 16 Docs Office Hours
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
Jacob's
documentation,
office
hours
today
is
the
February
16th
Edition
here
in
2023
for
EU
and
us
today
we
have
myself
Mark
Waite
I
am
Bruno
Rockton
welcome
and
thank
you
all
for
joining
us
as
I
appreciate
it
always
for
the
agenda.
A
couple,
a
couple
notes
here,
so
one
we
have
the
January
newsletter
was
published.
A
Last
week
we
have
an
update
on
the
gsoc
preparation
and
a
link
to
the
blog
post
that
John
Mark
had
written
just
a
couple
weeks
ago
we
have
the
Jenkins
awards
for
2023..
These
have
just
been
opened
and
will
go
into
a
little
bit
of
info
on
how
to
participate.
A
There's
discussion
about
the
documentation,
documentation,
transition
to
Java
17,
we're
approaching
fast
so
talking
about
getting
that
put
into
the
documentation
as
a
basis
to
use
and
then
something
that
Mark
and
I
had
been
discussing
previously
an
end
of
life
checklist
for
documentation,
so
making
sure
that
if
something
reaches
end
of
life,
we're
making
sure
that
we
can
update
and
remove
any
instances
that
we
need
to
there's
some
information
regarding
the
Cento
7
end
of
life.
A
This
is
just
a
proposal
at
this
point
in
time,
so
just
discussion,
nothing
moving
just
yet
and
Mark
has
added
a
note
about
end
of
life
website
and
Jenkins,
so
we'll
check
in
when
we
get
to
that
point
and
Mark
and
tell
us
more
about
that.
That's,
okay,
anything
else
that
we
need
to
add
to
the
agenda
or
does
that
cover
everything
for
the
most
part.
B
A
That
is
correct.
It
is
recording
so
first
things.
First
again
action
items,
just
the
January
newsletter
was
recently
published.
A
Again
we
all
had
our
big
big
22
recap
newsletter
in
January
and
this
math
month.
We
just
want
to
share
again
what
we
always
want
to
share
highlights
from
around
Jenkins
and
important
updates
from
the
Sega
leaders
and
just
real
quickly
big,
thank
you
and
shout
out
to
Roxanne
from
CD
foundation
for
creating
these
header
images,
really
spices
up
the
blog
post
and
appreciate
vibrating.
It's
really
nice.
A
A
We're
expecting
Jenkins
to
be
announced
as
that,
but
if
there
is
some
reason
that
it's
not
we'll
go
from
there,
but
we're
expecting
to
be
part
of
Google
summer
of
code
this
year,
foreign
and
there
will
be
there's
additional
timelines
for
Google
summer
code,
but
everything's
going
to
happen
after
the
the
organization
participation
announcement.
So
we'll
discuss
that
when
it
comes
down
next
up,
so
the
Jenkins
awards
for
2023
have
officially
opened
these
have
been.
A
These
are
now
three
separate
GitHub
issues
that
Alyssa
Tong
has
opened
up
and
we
have
one
for
most
valuable
Jenkins
contributor,
the
Jenkins
security
MVP
and
the
most
valuable
Jenkins
Advocate.
A
Each
of
these
issues
is
its
own,
separate
conversation
area
to
nominate
and
discuss
candidates
for
that
award.
Specifically
previously,
we
would
Host
this
on
the
CD
Foundation
site
repo
this
year.
A
The
projects
are
hosting
them
themselves,
which
is
why
we
have
these
issues
on
GitHub
this
year,
I've
also
gone
ahead
and
created
a
label
specifically
for
Community
stuff,
so
that
we
can
tag
things
accordingly
and
make
sure
that
people
see
that
this
is
something
for
everyone
to
participate
in,
as
opposed
to
an
issue
to
resolve
or
something
like
that
nominations
are
completely
open.
So
you
can
make
your
case
nominate,
whoever
you
would
like
to
and
there's
some
information
here.
A
There's
some
instructions-
and
one
thing
to
be
aware
of-
is
that
the
last
year's
winners
cannot
win
the
same
award
this
year
so,
for
example,
for
the
most
valuable
Jenkins
contributor
basil
won
last
year.
So
you
can't
win
this
year,
unfortunately,
but
he
can
still
be
nominated
for
the
other
things
so
yeah
anyone
can
still.
A
You
can
nominate
anyone,
everything's
open
and
then
voting
will
take
place
via
Google
form
once
the
nomination
period
has
closed,
that
is
March
3rd,
so
that
Friday
March
3rd
is
when
nominations
close
and
voting
will
open
the
following
week
and
we'll
close
at
the
end
of
March
and
then
the
results
will
be
announced
at
cdcon,
along
with
presenting
the
winners
with
their
Awards,
so
lots
to
look
forward
to
and
the
this
is
something
since
we're
hosting
them
in
our
repository
it's
something
new
for
this
year,
but
and
they're
they're
there
it's
a
great
opportunity
to
really
highlight
and
show
gratitude
and
appreciation
for
someone.
A
That's
done
a
lot
for
Jenkins
this
past
year.
So
if
you
have
anyone
in
mind,
please
go
ahead
and
submit
a
nomination
next
up
the
documentation
transition
to
Java
17..
So
this
is
something
that's
going
to
be
happening
in
around
April
May,
with
the
newest
Debian
12
release,
so
we're
going
to
transition
to
using
Java
17
in
the
documentations
for
installation
and
other
processes.
A
This
is
not
to
say
that
Java
7,
Java
11
support
is
being
dropped,
but
we
now
support
Java,
11
and
17,
and
with
17
being
or
having
more
functionality
and
being
more
newer.
The
idea
is
that
we
move
people
and
encourage
people
to
get
onto
Java
17.
Sooner
than
later,
we
can
move
forward
a
lot
smoother
and
there's
less
worry
down
the
line
as
time
moves
on
when
things
approach
end
of
life.
We
can
avoid
a
lot
of
that.
A
If
we
be,
if
we
are
proactive
about
it
now-
and
this
is
going
to
be
across
all
the
Jenkins
documentation,
this
won't
be
just
installing,
but
this
is
something
that
we'll
have
to
work
and
develop
as
we
get
closer
and
closer
to
that
date.
A
And
then
one
thing
that
I'm
going
to
be
doing
is
emailing,
Ginger,
comb
and
letting
him
know
about
this
transition
so
that
there
are
no
surprises.
He
is
release
officer.
So
it's
better
to
make
sure
everyone's
on
the
same
page
and
aware
of
what's
going
on
as
opposed
to
surprises,
I
can
see,
and
then
again
this
is
something
that
Mark
and
I
were
just
discussing,
but
having
an
end-of-life
checklist
is
something
that
we
can
really
consider
and
it
probably
should
have
with
things
approaching
end
of
life.
A
There
are
a
handful
of
things
coming
up
within
the
next
12
months,
or
so
so
Ubuntu
18,
Alpine,
3.14
and
3.15.
Those
three
are
all
going
to
be
happening
this
year,
and
so
we
want
to
make
sure
that
we
can
check
throughout
the
Jenkins
site
repository
in
any
other
locations
that
they
might
contain
some
of
this
information
or
documentation
and
ensure
that
it's
updated
or
removed.
A
This
can
cause
issues
down
the
line
if
things
are
not
updated
accordingly
or
it
could
be
misinforming
users
who
are
trying
to
perform
many
of
the
actions
here
in
Jenkins.
So
this
is
a
big
one,
and
this
is
really
important
to
make
sure
it's
taken
care
of
prior
to
any
big
release
and
any
release
at
all.
But
this
is
something
that
I
think
is
a
great
idea
and
something
that
I
want
to
work
on
and
get
created
so
that
we
have
that
that
just
that
peace
of
mind
going
forward.
A
And
then
these
are
some
of
the
idea,
the
places
that
we
were
discussing,
checking
so
stuff,
like
obviously
the
documentation,
the
packaging
sites
and
repository
the
release
repository
again
for
things
that,
if
there
are,
is
there's
tooling,
that
depends
on
certain
versions
of
it
and
that
versions
reaching
end
of
life.
We
can
run
into
issues,
so
that's
another
big
one
container
images
and
the
Jenkins
updates
site.
A
So
we've
got
a
great
list
going
if
there
are
more
places
to
we
can
check
or
that
we
should
be
checking
I'm
more
than
happy
to
entertain
everything
please,
you
know,
drop
a
message
here
at
it.
As
a
comment.
Send
me
a
message
regardless.
This
is
something
that
we
want
to
make
sure
is
front
of
mind
when
these
major
changes
come
foreign
next
up
is
the
prep
for
cent07
end
of
life,
so
Mark
I
was
wondering
if
you'd
be
okay
speaking
to
it
a
little
bit.
I
know
sure,
but.
B
Yeah,
so
the
the
idea
here
is
that
Centos
7
the
Jenkins
project
officially
only
supports
operating
systems
which
are
supported
by
the
Upstream
provider.
If
an
upstream
provider
ends
support,
the
Jenkins
project
ends
support
for
that
thing,
so
that
means
that
Centos
7
would
officially
be
supported
until
June
of
2024.
However,
we're
seeing
the
erosion
of
support
for
Centos
7
elsewhere
in
the
world,
and
with
that
erosion
of
support
and
my
personal
biases
against
it,
it's
weighing
in
that
I
think
we
ought
to
consider
dropping
it.
B
So
some
of
the
the
compelling
things
to
say
there
are
hey
our
RPM
installer
doesn't
support
it
now
and
we
deliver
a
Docker
container.
We
deliver
one
or
more
Docker
container
images
with
Centos
7,
but
the
Upstream
of
Centos
7,
container
image
on
which
we
are
building
has
been
unmaintained
and
deprecated
since
late
2022..
B
So
we're
building
on
on
something
that
our
own
standards
say,
we
would
not
support
the
Upstream
doesn't
is
not
maintained
and
therefore
we
should
we
should
consider
getting
rid
of
it.
So
the
steps
I
think
that
are
needed
is
I.
Think
this
one
I'm
going
to
go
ahead
and
propose
a
Jenkins
enhancement
proposal,
a
Jep
that
suggests
to
accelerate
the
end
of
life
for
Centos
7..
Now
that
doesn't
mean
it's
immediate.
It
rather
means
we
will
go
through
a
systematic
discipline
process
to
drop
and
clarify
to
people,
but
we
are
dropping
support
for
centos7.
B
And
I
did
I
did
do
some
work
on
this,
so
the
documentation
references
to
Centos,
7
to
be
removed,
I
submitted
a
pull
request
to
reduce
the
Centos
7
and
references
in
our
documentation.
I
was
surprised
at
how
relatively
few
there
were,
so
it
wasn't.
It
wasn't
nearly
as
dismaying
as
I
thought.
It
was
going
to
be
there
there
just
weren't
that
many
that
many
places
where
we
referred
to
cento7
and
where
we
did.
A
B
A
Karen
such
a
good
guy,
he
always
comes
in
when
he
needs
to
so
great
all
right.
Thank
you
very
much
Mark
and
this
kind
of
goes
back
into
the
end
of
life
checklist
and
everything
that
we
were
discussing
as
well,
so
super
relevant
super
applicable
to
things
that
we
want
to
accomplish
and
set
up
and
template
out
eventually
so
yeah
super
important.
Thank
you
very
much,
and
then
Mark
I
noticed
you'd
put
this
this
last
item
on
here
at
the
end
of
life
website
and
Jenkins
yeah.
B
So
could
you
could
you
click
that
Kevin
and
let's
talk
about
it
for
a
minute?
So
one
of
the
challenges
for
me
is
how
do
I
know
when
things
are
reaching
end
of
life
and
other
people
had
this
Challenge
and
somebody
created
this
open
source,
open
maintained
website
called
endoflife.date,
and
it's
actually
so
good
that
I've
been
using
it
for
months
now,
without
realizing
that
it
was
entirely
an
open
source
effort.
B
I
thought:
oh,
somebody
was
really
nice,
some
business
did.
The
very
nice
thing
turns
out:
it's
not
a
business
at
all.
Somebody
just
did
this
because
they
had
a
question
they
wanted
to.
They
wanted
to
solve
their
question
and
they
found
a
way
to
present
it
very
clearly
and
the
person
that
interacted
with
me
is
actually
someone
I've
interacted
with
in
the
Jenkins
community
in
years
past.
So
it
was
oh
wow,
that's
cool!
This
is
a
name
I
recognize.
B
So
so
what
you
see
on
the
left
is
various
products
and
their
end
of
life,
and
so,
if
you
scroll
down
Kevin,
you
can
find
Jenkins
here.
This
was
added
only
a
few
days
ago
to
the
list,
but
here
you
see
what
it's
showing
is
a
brief
description
of
Jenkins
and
then
category
the
type
of
release
it's
documenting.
How
long
ago
it
was
released,
is
it
currently
supported
and
what's
its
version,
number
wow
and
the
story
that's
being
told
here
is
that
we
support
the
current
weekly
release
2.391..
B
Right
and
that's
and-
and
that's
part
of
the
Elegance
of
this
thing
right
is
the
the
weekly
version.
Number
I
did
nothing
to
update
that
and
it's
going
to
it
should
just
keep
up
to
date,
and
likewise
the
latest
on
the
LTS
line
should
keep
up
to
date.
The
thing
that
my
pull
request
was
changing
was
the
original
layout
that
the
the
first
Creator
had
done.
Confused
me
and
I
was
able
to
persuade
him
that
hey.
We
should
change
this
layout
to
look
more
like
Alpine's
layout.
B
So
if
Kevin,
if
you'll
click
the
Alpine
Linux
on
the
left,
you'll
see
how
similar
we
are
to
Alpine
Linux
a
release
when
it
was
released,
does
it
have
green
or
red?
And
what's
the
latest
version,
and
if
you
were
to
look
at
Debbie
and
you'd,
see
it's,
we
look
a
lot
like
Debian
as
well
right.
So
it's
it's
the
same
pattern
of
okay.
Let's,
let's
look
like
these
other
very
popular
open
source
projects.
A
B
One
has
a
commercial
life
cycle
and
has
a
hardware
component
and
has
all
sorts
of
things
that
go
with
commercial
operating
systems
right
and,
and
so
it
represents
that
in
a
much
more
complex
and
much
more
useful
for
its
consumers
way.
But
for
us
I
think
the
simple
presentation
we're
using
is
a
lot
better
and
we
don't.
We
certainly
don't
have
this
kind
of
tiered
life
cycle
that
Ubuntu
does
for
theirs.
C
Mark
sorry
I
have
an
idea.
Oh
she
says
not
that
good,
but
we
have
the
king
of
automation
in
the
Jenkins
team.
You
know
available
and
I
was
wondering
if
we
could
use
that
API,
because
it
looks
like
this
website
has
an
API
that
we
know
that
some
components
or
OS
version
that
we
are
using
are
not
supported
anymore
and
put
them
automatically
in
the
documentation
or
even
in
our
containers,
or
you
know
that
what
you
wanted
to
do
with
the
jab.
C
B
B
Well,
and
and
hey
that
that
rabbit
hole
is
quite
helpful
because
for
me,
for
instance,
as
the
maintainer
of
the
platform,
labeler
plug-in
I
keep
track
of
the
end
of
life
dates
of
project
of
operating
systems.
So
that
I
know
when
to
say
it's
unsupported,
but
this
API.
If
it
can
really
answer
that,
may
then
be
able
to
fill
in
these
fields
so
that
cool
I
don't
have
to
bother
with
it
anymore.
B
B
A
A
B
Yeah
well
and
a
good
point.
So
why
not?
Let's?
Let's
do
some
looking
and
consider
because
we
certainly
already
are
doing
website
generation
right.
Our
our
site,
generator
is
a
program
and
the
fact
that
it
generates
a
static
site
is
not
a
barrier
to
this
kind
of
thing,
because
we
could
read
this
data
and
inject
it
into
the
static
site.
A
A
B
A
We'll
have
to
get
there
first,
but
maybe
but
yeah,
so
that
takes
care
of
everything
that
I
had
on
my
agenda
for
doc's
office
hours.
Is
there
anything
else
that
we
want
to
talk
about
or
any
other
items
that
we
want
to
add
on
here?.
A
Okay,
well,
if
that's
okay
with
everyone,
then
on
the
interest
of
time,
we'll
call
it
here.
Thank
you
very
much.
As
always,
the
recording
will
be
available
in
24
to
48
hours
and
yeah
have
a
great
rest
of
your
day,
thanks
for
joining
and
take
care.