►
From YouTube: 2023 05 18 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
Foreign
welcome
this
is
the
18th
of
May
2023.
It's
documentation,
office
hours
topics,
we've
got
today.
Kevin
Martens
is
unavailable,
April
newsletter
transition
from
java
11
to
Javan
17
in
the
documentation,
Google
summer
of
code,
and
then
the
other
items
I
think
it's
safe
to
just
leave
them
in
the
list,
they're
they're
more.
To
remind
that,
we
need
to
be
sure
we
get
them
all
the
way
to
closure
anything
else
that.
A
The
idea
there
was,
let's
accept,
that
the
documentation
transition
from
java
11
to
Java
17
will
be
delayed
and
encourage
others
Bruno.
You
me
Alyssa
I've
asked
Meg
McRoberts
as
well
to
review
pull
requests
in
his
absence
and
I'll
handle
the
change
logs
for
the
weeklies
and
the
changelog,
and
upgrade
guide
for
the
upcoming
LTS
at
the
that
happens,
May
31st
any
suggestions
or
guidance
there
that
you
want
to
change
or
recommend
something
different.
A
C
A
Good,
the
next
topic
is
just
to
say
that
the
documentation
transition
is
delayed.
We've
got
a
ticket
that,
if
other
contributors
would
like
to
contribute
here
here
is
a
list
from
Kevin
of
the
pages
that
need
to
be
visited
and
he
started
an
initial
pull
request
for
one
of
those
steps.
If
someone
would
like
to
pick
it
up.
A
Okay
next
topic
was
Google
summer
of
code,
so
we're
pleased
to
welcome
vandit
Singh
as
working
on
the
Jenkins
documentation
project
to
re:
rework
the
jenkins.io
website,
so
that
it
supports
multiple
versions,
much
the
same
way
as,
for
instance,
this
site
does
so
here.
I
can
look
at
the
documentation
for
the
reference
manual
for
say,
git,
config
and
notice
that
up
here
at
the
top
there's
a
choice
that
lets
me
look
at
old
documentation
versions.
We
want
something
similar
like
that
for
the
Jenkins
documentation.
A
C
It's
not
forgetting
that
well,
first
time
being
because
it
was
difficult
to
find
a
correct
time
slot
for
all
of
the
mentors
and
ashutosh,
but
we'll
have
our
first
meeting
tomorrow,
so
hopefully
we'll
progress.
We
already
have
defined
our
communication
channels
and
I
think
we'll
work
on
the
plan
tomorrow.
B
That
one
no
nothing
to
share
okay,
so
only
I'm.
A
Afraid
right
so
May,
20,
May,
28th
10
days
from
now
will
end
the
community
bonding
period
and
start
phase
one
of
the
project
development.
That's
great
thanks.
The
last
three
items
really
are
just
status
reports.
There's
no
change
on
the
on
the
pipeline
steps
reference.
It
still
works;
let's
just
prove
it
to
be
sure,
so
it
works
by
going
here
pipeline.
The
pipeline
steps
reference.
If
we
search
for
checkout.
A
And
we
open
it,
it
has
the
full
content
good
so
still
working
the
the
test.
That's
in
the
code
defends
us
against
breaking
changes
no
time
yet
for
anyone
and
probably
not
for
a
month
or
more,
for
investigation
of
what
actually
broke
that
and
any
question
on
that.
One:
Bruno,
no
Mark
thanks,
okay,
so
low
risk,
low
risk
test,
defend
us
from
a
breaking
change.
A
So
other
topics
are
idling
until
we
get
more
traction,
we
just
got
another
request
on
a
community
thread
asking
about
support
on
Centos
7,
and
the
answer
is
hey.
We
intend
to
remove
Centos
7
support
the
submitter
said:
oh,
that's,
okay,
we're
gonna,
we're
gonna,
keep
using
it
anyway
and
here's
the
change
that
they
did.
But
the
reality
is.
We
don't
intend
to
continue
supporting
Red,
Hat,
Enterprise,
Linux
7
and
its
derivatives
for
a
long
time.
C
A
No,
and
and
certainly
we,
we've
got
lots
of
places
where
the
Jenkins
project
actually
uses
Centos
7
in
not
in
its
own,
our
own
build
processes,
but
we
will
reference
things
from
Centos
7
and
so
we've
got
work
to
do
to
to
get
it
cleanly
removed,
but
the
sooner
we
start,
the
sooner
it'll
get
done,
yeah
all
right.
That's
all
that
I
had
anything
else.
Bruno.