►
From YouTube: 2023 03 03 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
everyone:
this
is
the
third
of
March
2023.
It's
documentation,
office
hours,
agenda
topics
for
today
include
action
items,
LTS,
2.387.1,
documentation,
transition
to
Java,
17.,
improving
end
of
life,
notifications,
preparing
for
Cento
7
end
of
life.
We
should
probably
put
even
before
any
of
those
introductions.
A
And
yeah,
so
let's
do
introductions.
Are
there
any
other
topics
you
want
to
put
on
the
agenda
for
today.
B
I
was
just
thinking
of
the
record.
You
know
also
review
the
PRS
that
intention
this
once
I
guess
I
mean
we're
going
to
spend
around
five
minutes
on
that.
B
Mean
these
people
requests.
Okay,
all
right!
You
already
have
no
wait.
I'm
gonna
share!
These
are
the
same
ones.
I
was
talking
about
the
ones
which
was
around
this
pla
beginning.
Oh.
A
A
B
Hi
everyone
I'm
film
and
I'm.
Actually,
a
currently
a
CS
student
in
India,
I
have
been
I,
mean
I,
have
joined
Jenkins
from
the
last
four
months
or
so,
and
I
have
just
been
looking
around
and
then
finally,
apparently
I'm
a
printer
for
one
of
the
politics
which
are
coming
up
in
the
Google
summer
of
code
and
I'm.
B
Here
to
just
learn
more
about
the
I
mean
like
how
the
how
Jenkins
works,
because
I
feel
that
documentation
is
a
very
core
sign
of
how
any
or
any
odd
apocalypse
so
yeah
I'm,
just
here
to
learn
analytics
like
have
some
fun.
A
C
C
Be
muted,
unmuted,
sorry
about
that
I'm
I'm,
a
technical
writer
I've
been
with
the
Jenkins
project,
I
think
for
five
and
a
half
years
now,
the
last
year
or
so
I've
been
working
less
on
Jenkins
and
more
on
some
observability
open
source
tools
like
Captain
and
open
feature
and
open
Telemetry
and
all
of
these,
but
I
still
love
Jenkins
and
I
love
Mark.
So
I
check
in
this
keeps
my
fingers
in
the
pot
here.
A
Super
thank
you
Meg
and
Meg
is
Freya.
Meg
is
delightful,
I
love,
working
with
and
learning
from
Meg.
She
is
the
extraordinary
technical
writer
I
come
from
a
software
development
background
Meg's.
Actually
a
writer
and
a
writer
who
has
who
has
worked
at
places
like
at
T,
Bell,
Labs,
writing.
So
so
she's
she's
got
deep,
wonderful
experience
and
is
is
a
tremendous
asset
for
what
we
do
in
the
Jenkins
project.
So.
A
Yeah,
let's
see
so
how
about
I'll
I'll
play
the
same
game.
I
am
a
I,
am
a
Jenkins
contributor,
so
I'm
a
core
maintainer
I
maintain
the
get
plug-in
documentation.
Contributor
I
spent
several
years
as
the
documentation
officer,
which
is
kind
of
strange,
because
my
background
is
actually
mechanical.
I
have
a
degree
in
mechanical
engineering
and
I
left
the
university
with
that
degree
and
told
the
recruiter
that
I
didn't
want
to
do.
A
C
Mark
is
a
delightful
software
person
who
really
does
understand
documentation,
so
you
can
have
Market
that's
what
Mark
and
I've
had
a
lot
of
fun
together,
because
we
can
really
sit
down
and
talk
about
how
you're
going
to
do
so.
So
often,
the
engineers
are
like
the
software
works
right,
whatever
you
want
to
about
it,
I
don't
care,
and,
and
vice
versa,
so
Mark
and
I
have
had
a
lot.
We've
had
good
times.
C
C
C
From
what
are
you
actually
working
on
right
now?
Are
you
working
on
the
the
plug-in
installer
I'll
plug
in
installation
management?
Okay,
yeah.
A
B
Yeah,
so
at
2021
I
was
a
contributor
at
that
ask,
and
in
2022
I
was
a
inventor
at
Joomla
yeah
sure
I
have
had
my
fair
share
of
documentation
and
entering
students
to
actually
start
documenting,
because
I
feel
that,
like
documenting,
is
one
of
the
requirement
of
those
skills
where
which
aren't
exactly
taught
in
the
university
courses.
You
know
like
they
actually
I
mean
the
actual
importance
of
this
in
in
any
kind
of
a
project.
A
Okay,
then,
let's
quick
review
of
action
items
I've
got
two
open,
Action
items,
2.387.1
releases
next
Wednesday
and
the
change
login
upgrade
guide
needs
to
be
merged
and
then
we've
got
some
long-standing
pull
requests.
Vandit
Singh
created
a
really
an
amazing
pull
request
for
the
an
upgrade
guide
for
Jenkins
and
it
needs
needs
further
refinement
and
merge.
A
Yeah,
so
this
is
this
is
in
when
Debian
12
releases
that'll,
be
our
our
excuse
and
we'll
make
that
transition
across
everything.
Okay
and
the
Tim's
been
informed
now
in
the
next
piece.
This
is
a
new
piece,
so
one
of
the
things
that
we've
realized
is
we've
got
a
number
of
things
that
are
reaching
end
of
life
and
we
need
to
communicate
that
end
of
life
to
users.
A
We
also
have
some
Docker
contain
some
container
images
that
we
want
to
end
of
life
to
stop
supporting
right
and
but
no
way
to
communicate
that
to
users.
You
mean
ahead
of
time
well,
even
during
so
yeah,
so
what
we
would
like,
for
instance,
with
Java
11.
We
announced
the
end
of
life
and
caused
them
to
see
a
pop-up
and
they
closed
the
pop-up.
Okay,
we
at
least
warned
them.
Then,
when
we
actually
hit
the
end
of
life,
we
caused
another
pop-up,
saying
hey
you're
beyond
end
of
life.
Here.
C
A
They
need
to
get
to
the
newer,
the
newer
environment
to
the
newer
version,
it's
basically
right,
and
so
in
a
conversation
in
the
platform
Sig,
the
idea
came
out:
hey,
let's
generalize
this
thing
so
that
we
could
have
a
data
file
in
a
directory
in
the
Jenkins
home
directory
or
a
series
of
data
files,
a
directory
of
data
files,
which
are
these
end
of
life
announcement
things,
and
if
that
file
exists,
we
will
show
you
that
end
of
life
announcement,
nice,
the
thought
was
hey.
If
we
do
this,
we
have
a
way
to
tell
people.
A
So
now.
What
we
really
need,
though,
is
I've,
got
to
create
a
Jenkins
enhancement
proposal,
a
Jep
needed
to
launch
the
idea
and,
and
then
we
will
then
we'll
apply
it
to
get
to
the
things
like
the
blue
ocean
container
image
that
we
need
to
kill
off
and
I
hope
we
will
apply
it
to
Centos,
7,
container
image
and
probably
the
Arch
Linux
agent
container
image
and
more
right.
So
we
want.
We
want
those
kind
of
this.
A
Well,
we
don't
actually
today
ship
any
ubuntu-based
container
images,
so
it's
no
harm
that
when
this
1804
one
is
going
to
be
more
complicated
because
we
don't
control
the
file
system
where
they
write
it
when
we're
doing
a
Docker
container
when
we're
doing
a
container,
we
control
the
file
system.
Oh
so
so
it's
there's
more!
That's.
Why
there's
more
to
be
done
on
this
concept
right?
We
don't
fully
understand
it
yet.
A
A
A
A
A
A
A
A
B
B
Are
you
guys
able
to
see
my
screen?
Yes,
okay,
perfect!
Let
me
just
hide
this
annoying
thing,
but,
okay,
all
right,
good,
okay,
okay!
So
this
is
something
I've
done.
Remember
the
gsock
student
ad
task,
so
the
simple
idea
is
that
you
kind
of
have
the
simple
dock,
where
you
kind
of
just
give
an
overview
of
all
the
commands,
or
at
least
all
the
code
commands
of
any
software.
And
then
this
is
simply
called
10
minutes
to
das
or
10
minutes
into
a
task.
B
So
in
this
case
we
have
a
simple
like
code
example:
you
just
import
the
task,
libraries
and
finally
create
some
objects,
and
then
so
on,
but
like
the
the
idea
is
that
this
thing
gives
a
very
simple
overview
of
how
to
actually
get
started
and
or
how
to
pick
your
hands
dirty
inside
the
library
from
the
first
time,
from
the
very
first
time
you
use
it
so
I
mean
okay,
so
like
do
we
like
have
something
and
Jenkins
as
well
like,
for
example,
I
think
this
is
the.
A
Okay,
guided
tour
will
take
you
through
a
tour
of
introducing
you
to
Jenkins
and
how
to
create
a
pipeline
to
then
use
that
pipeline
to
do
something
Etc
with
videos
Associated.
So
you
can
perfect.
Okay,
perfect
good.
Now,
if
that
tour
is
not
enough,
then
if
you
go
back
to
the
tutorials
on
the
left,
click
the
yeah
Jenkins
pipeline
tutorials,
so
that
one
will
give
you
more
more
tutorials
and
now
here's
a
page
filled
with
tutorials
of
various
types.
So
a
guided
tour.
That
was
the
easy
one.
A
If
you've
got
hey,
I
want
to
do
something
more
involved.
The
pipeline
tutorials
tab
section:
there
gives
you
much
more
involved
things
or
if
you
scroll
down
to
the
using
build
tools,
maybe
you
say:
hey
I'm,
a
python
user
show
me
how
to
do
something
with
python.
Well,
there's
the
build
a
python
app,
no
I'm,
a
node.js
user
or
a
react
developer.
Okay,
here's
one
for
react!
I
do
Java!
B
A
A
A
A
So
the
submitter
submitted
changes
in
well.
First,
let's
look
at
the
goal
right.
The
goal
was
implement
this
enhancement
request.
Security
warnings
should
be
shown
by
default
and
the
way
that
Daniel
proposes
to
do
that
is
make
the
existing
view.
Security
warnings,
command
line
argument,
a
no-op
so
that,
if
someone
gives
it,
we
we
see
it
and
ignore
it
and
add
a
new
Option
hide
security
warnings
that
says:
oh
I,
don't
want
to
show
them
so
that
by
default,
the
user
will
always
see
security
warnings.
A
Now,
there's
an
additional
subtlety
here
that
we
need
to
check,
which
is
that
These
Warnings
must
not
go
to
standard
out.
They
must
go
to
standard
error.
I
know
right
right
exactly
so,
because
standard
out,
one
of
the
things
that
the
contributing
guide
for
the
plugin
tells
us
is
standard
out,
is
reserved
for
output
that
should
go
into
the
plugins
text
or
the
plug-in
Channel
file.
So
it's
reserved
for
definitional
output,
not
for
informational
or
message
based
output.
A
A
B
Just
one
second:
actually,
the
line
number
50.
What
is
the
running
location
right?
Because
yeah
I
mean
he
has
that
so
view
all
security
violence?
Oh.
A
Fram
you're
right,
I
read
it
incorrectly
cancel
very
good.
Thank
you.
There's
power
and
two
of
us
doing
this.
This
is
view
all
security
warnings
exactly
and
that's
not
by
default
happening
right,
you're,
correct,
absolutely!
Thank
you
very
good,
okay,
and
so
that
is
this
line
here,
good
all
right,
so
we're
fine,
okay!
Next,
then,
so
in
the
command
line,
options
comment
here
that
tells
us
view
security
warnings
is
deprecated
but
not
removed.
So
that's
good
and
the
variable
is
that
stores
the
value
is
deprecated
and
then
hide
security.
A
A
A
So
this
says,
creates
a
configuration
class
with
configuration
specified
okay,
so
it
is
intentionally
initializing
everything
right,
even
deprecated
things
are
being
initialized
here.
So
I
think
this
should
remain.
A
B
You
just
scroll
up
a
bit
we'll
just
have
a
look
at
these
surrounding
ones.
If
they
have
anything
specific.
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
Which
is
sort
of
sort
of
silly
right,
because
this
is
not
one
that
takes
a
value,
but,
okay,
that's
that's
correct.
The
default
is
it's
not
set,
then
clean,
the
and
now
login
file.
We've
done
and
oh,
we
need
to
say
what
directory
we're
using
and
the
directory
we're
using
plug-in.
Download
directory
is
plugins.
A
A
A
C
A
B
I
was
just
saying:
we'll
also
just
have
a
look
at
how
how
this
interacts
with
plugin.
B
So
it
does
not
exactly
have
any
audience
right,
so
we'll
just
make
sure
that
it
also
follows
that
oh.
A
A
I
wonder
if
that's
what
we
want?
Okay,
so
do
you
see
what
happened
here?
It
says
on
the
standard
error.
It
wrote
let's,
let's
double
check,
that
it's
really
standard
error.
C
A
A
B
I
would
say
for
now
this
I
mean
I.
Guess
we're
going
to
sleep
on
this
for
now,
but
I
think,
like
the
pr
solves
the
issue,
so
I
think
you
can
just
go
forward
with
this
for
now
and.
A
A
Then
I
I
think
we
go
ahead
and
say
that
this
is
ready
to
merge.
Let's
see,
I
do
need
to
label
the
pull
request,
so
this
is
a
what
would
we
call
it?
This
is
really
an
enhancement
right,
I,
don't
think
I
I
wouldn't
call
it
a
bug.
Security
wordings
by
default,
for
me,
is
a
everybody.
Okay.
If
we
call
it
an
enhancement,
absolutely
okay,
all
right,
then,
let's
go
through
and
back
to
Groove.
Okay,
one
option:
oh,
let's
read
the:
what
was
the
question
that
I
had
no
I
don't
want
to
cancel
the
review.
A
I
was
oh
right,
one
optional
question:
no!
No!
No!
Let's
just
get
rid
of
that.
Let's
not
do
that
at
all.
Delete
I,
don't
like
giving
people
questions
without
an
action.
Basel
Crow
has
taught
me
that
that's
a
bad
thing.
We
should
give
them
either
a
specific
action
or
not
burden
them
with
the
thing.
Okay,
so
reviewed
in
doc's
office
hours
with
Fram.
A
B
It
did
so
I
will
just
okay,
so
my
question,
my
Joshua
behind
this
was
that
okay,
so
now,
I
have
like
a
very
set
number
of
like
steps
to
follow
while
I'm
reviewing
the
prsl
I.
Just
I
just
want
to
like
have
a
look
at
like
how
this
thing
works
in
this
organization
as
important,
good
yeah.