►
From YouTube: 2023 04 14 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
Welcome
this
is
the
14th
of
April.
It's
documentation
office
hours,
thanks
for
joining
topics
that
I've
got
on
the
list
include
Google
summer
of
code.
Also,
it's
already
already
here
right.
So,
let's
just
move
it
up.
Yeah
alternate
ways
to
handle
stale
pull
requests
that
was
discussed
in
doc's
office
hours
Europe
about
12
hours
ago.
That
I'd
like
to
review
as
possible
ideas
and
not
nothing.
A
We're
wanting
to
take
action
on,
but
I
think
worth
discussing
end
of
life
notifications
in
Jenkins
core
that
Chris
I
would
like
to
review
with
you,
I
reviewed
it
earlier
with
with
Alex
Brandis
in
office
hours
Europe,
and
wanted
to
see.
If
what
you
thought
of
this
idea
and
early
end
of
life
of
scent
for
Centos
7
gets
a
new
topic,
because
there
was
just
recently
an
article
anything
else.
You
want
to
add
to
the
list.
Chris.
B
A
B
All
right-
and
we
just
have
one
more
mental
joint,
which
is
a
returnee
because,
as
you
mean
oh
good,
yes,.
A
Joined
as
a
mental
as
a
returning
yep
returning
after
being
a
contributor
last
year
right,
he
was
a
on
the
project.
Last
year
with
it
was
last
year's
Jenkins
file,
Runner
project
yep,
that's
correct,
great,
excellent,
all
right!
So
anything
else
that
you
wanted
to
highlight
there
Chris.
B
I
think
we
are
doing
okay
progress.
Wise
I
may
need
to
chase
some
of
the
mentors
for
evaluations.
Okay,.
B
A
No
I
did
receive
a
an
email
from
so
mark
frame
and
I.
Forget
who
the
other
one
was,
and
one
other
received
reminders.
A
From
John
Mark
today,
I
I
assume
you
were
copied
as
well,
so
we'll
meet
in
my
case
it
will
probably
be
likely
early
next
week.
B
A
A
All
right
good,
thank
you.
Okay
on
next
topic
then
alternate
ways
to
handle
stale
documentation,
pull
requests.
So
last
week
there
was
a
a
question
from
I
think
it
was
from
who
was
it
I
forget,
but
one
of
our
attendees
Kumar
asked
last
week
hey?
Why
don't
we
do
what
why
don't
we
just
run
stalebot
yeah.
A
Well,
there
are
those
of
us
who,
like
me,
who
have
pretty
strong
opinions,
no
I'm
not
willing
to
stay
a
lot.
Okay,
we
discussed
okay,
what's
the
what's
the
what's,
what
are
the
concerns?
What
are
the
reasons
for
that
and
why
would
we
care
and
that
for
me,
was
a
useful
discussion
so
yeah?
The
point
was
there
are
several
different
reasons:
a
pull
request
can
go
stale
right
right
if
it's
stale,
because
it's
not
valuable,
we
just
close
it
and.
B
A
There
we
had
an
example
just
today
where
Kevin
Kevin
Martins
had
asked
three
or
four
times
over
the
course
of
several
weeks
for
a
submitter
to
correct
some
mistakes
in
the
in
the
content.
They
were
trying
to
submit
no
response.
They
had
just
stopped
being
involved
and
Kevin
finally
said.
Look
what
you're
submitting
is
not
valuable
enough
for
me
to
complete
the
work
myself.
Okay,
we're
going
to
close
it,
so
that
that
was
that's
a
very
reasonable
thing.
A
B
A
And
we
talked
about
okay,
we
could
take
that
old,
pull
request
and
close
it
and
create
an
issue
to
track
the
content.
After
talking
with
Alex
Brandis,
he
said
well,
but
that's
not
how
Jenkins
core
does
it?
What
Jenkins
core
does?
Is
they
just
label
it
stalled
and
accept
that
it's
okay,
that
it's
open,
it's
just
not
progressing!.
A
This
good
well
and-
and
that
was
what
Kevin
felt
as
well-
was
that
okay-
let's-
let's
just
admit
it's-
okay-
that
we
have
open,
pull
requests,
but
we're
going
to
mark
them
installed
because
stalled
is
a
way
of
at
least
telling
us
hey.
This
thing
is
not
getting
progress
and
we
could
then
we
can
then
invite
new
contributors
to
help
with
some
of
the
stalled
pull
requests.
A
B
A
A
What
is
that?
It's
called
good
first
issue,
the
first
issue,
so
does
that
sound
reasonable
to
you,
Chris
I,
think.
A
B
A
B
A
B
A
A
B
A
The
the
Upstream
vendor
says
we
will
no
longer
support
it
to
the
open
source.
Community.
You
have
to
purchase
an
extended
support
contract.
You
have
to
pay
them
money
in
order
to
get
support
for
Ubuntu
18
after
May
31.,
and
at
that
point
the
Jenkins
project
says
it
is
unsupported
for
Jenkins,
but
we
have
no
way
of
notifying
people
that
it
is
unsupported
and
they're
running
on
an
unsupported
platform
yeah.
So
in
the
past,
when
we
said
hey,
Java
8
is
going
to
be
unsupported.
We
used
a
thing
called
an
administrative
monitor.
B
A
A
B
B
A
You
are
about
to
end
up
you,
you
are,
you
are
end
of
life.
What's
the
date
end
of
life,
31,
May,.
A
B
A
Dot
star
seven,
you
know
and
Etc,
then
we
so
the
idea
being
we
we
create
these
a
data
file,
one
or
more
data
files
that
Define
these
conditions
and
the
messages
the
condition.
So,
let's
see,
let's
talk
about
the
attributes.
Attributes
inside
this
data
file
are
the
file
name.
B
B
B
A
So
the
idea,
then,
is
okay.
Each
Jenkins
release
can
say
here
are
the
things
that
that
are
the
admin
monitors
that
we'll
be
checking
with
this
Jenkins
release
to
announce
to
people
that
they
are
on
some
obsolete
platform.
And
this
would
let
us
do
things
like
these
Linux
releases.
Those
are
pretty
easy
because
they
identify
by
files
and.
B
B
A
B
A
B
No,
not
really
no.
Okay,.
B
A
The
idea
I'm
and
now
that
we've
been
through
these
iterations
enough
times,
I
think
this
may
even
be
worth
just
doing
a
pull
request,
rather
than
bothering
with
the
Jenkins
enhancement
proposal
process,
because
the
idea
seems
sensible
enough.
Let's
just
let's
just
do
it
yeah
great
all
right,
any
other
suggestions
you
want
to
offer
on
that
one,
no,
okay,
all
right
next
topic,
then
early
end
of
life
for
Centos
7
in
the
Jenkins
project.
So
this
is
another
proposal
or
idea.
A
B
A
A
Okay,
so
so
for
me,
this
is
tempts
me
to
say
you
know
what
we
should
do
the
same.
We
should
do
something
similar
where
we
declare
that
we're
ending
life
for
Centos
7
in
particular,
because
this
is
the
one.
That's
that's
that,
for
me,
is
the
most
valuable
thing,
which
is
that
Docker,
the
the
Centos
7
container
images
are
already
unsupported
by
their
Upstream
maintainers,
okay.
So
what
that
means
is
that
Jenkins
container
image
is
based
on
them.
A
7
system
d
based
RPM
installer.
B
A
It's
and
and
Basel
Crow
who,
who
did
the
implementation
of
says,
not
supported,
so
not
supported,
and
let's
see
there
was
one
other
non.
Oh
yeah
I
remember
what
it
was:
sentos
seven
open,
SSH
7.4.