►
From YouTube: 2022 12 22 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
to
the
Jenkins
documentation
office
hours:
this
is
the
December
22nd
U.S
EU
Edition.
Today
we
have
myself
Mark,
Waite
and
Bruno
varachan
joining
us.
So
quick
note,
just
as
aside
next
week,
we
will
not
have
Jenkins
documentation,
office
hours,
we'll
be
out
of
office,
most
people
will
be
busy
with
holidays
and
whatnot.
So
next
week
we
won't
be
anything
just
as
a
heads
up
aside
from
that.
A
We
have
some
action
items,
just
a
quick
note
on
the
pipeline,
Docker
plugin
and
what
that
means
for
documentation
and
for
the
most
part,
just
looking
at
the
just
the
2022
recap,
newsletter
topics
and
ideas,
and
then
a
couple
of
pull
requests
to
take
a
look
at,
and
just
make
note
of
considering
that
these
sort
of
things
are
going
to
be
really
important
when
we
get
back
into
the
new
year
and
just
get
them
forward
for
Jenkins
and
Mark's,
adding
a
note
regarding
the
Jenkins
backlog
so
we'll
get
to
that
at
the
end
as
well.
A
Does
everyone
have
anything
else,
they'd
like
to
add
or
anything
I
missed
all
right,
then
so
first
action
item
here
on
the
list
is
right.
Now,
what
I'm
doing
is
going
through
the
Jenkins
jira
and
find
and
going
through
all
the
website
certificates
specifically
Alex
Brandon
submitted
a
ticket
to
the
help
desk
to
make
sure
that
this
is
taken
care
of,
and
these
issues
are
cleaned
up
closed
if
we
don't
need
them
or
migrated.
A
If
we
should
talk
about
them
further,
so
I'm
going
through
that
list
right
now,
I've
gotten
to
about
60
to
70.,
there's
about
100
or
so
altogether.
So
a
lot
of
them
have
been
able
to
get
closed
out
because
we've
just
got
in
the
documentation
now
so
yeah
that'll
be
again
something
that
gets
finished
up
in
the
next
couple
months,
probably
sooner
than
that
and
we'll
be
discussing
those
those
really
valid
and
potential
additions,
as
we
go
next
thing
on
the
action
items
is
archiving
the
doc
mailing
list.
A
This
will
be
something
that
gets
started
in
January,
Mark
and
I
will
be
discussing
what
we
need
to
do
to
get
to
the
starting
point
and
what
needs
to
happen
after
that,
so
more
information
to
come.
But
just
so
you
know,
and
then
I
wanted
to
highlight
a
couple
of
blog
posts
that
we've
published
recently.
One
is
Sean
Mark,
messen's
blog
post
for
the
Google
summer
of
code
mentorship.
It
just
goes
really
in
depth
on
what
mentorship
means.
A
What
a
mentor
looks,
what
mentorship
looks
like
in
Google
summer
of
code,
the
expectations,
what
opportunities
they
have
et
cetera,
et
cetera,
but
Google
summer
code,
is
super
in
progress
where
the
call
for
papers
is
coming
up
in
just
about
two
weeks.
I
think
January
5th
is
the
call
for
papers
deadline,
so
we're
in
full
swing,
looking
forward
to
Google
server
code
right
now.
A
So
if
you
have
any
interest,
you
want
to
speak
chat,
ideas,
topics
how
you
can
mentor
how
you
can
participate,
whatever
have
you,
we
have
plenty
of
resources
and
blog
post
is
a
great
way
to
start.
A
The
other
blog
post
that
I
wanted
to
call
out
and
highlight
here
is
the
recent
post
from
basil
Crow.
He
wrote
a
wonderful
and
very
detailed
blog
post
about
the
new
Baseline
requirement
for
Jenkins
plug-in
development,
which
is
Java
11..
This
is
a
more
recent
update.
The
Java
level
requirement
has
been
part
of
Jenkins
itself
for
a
few
months
now,
but
the
Palm
itself
was
upgraded
to
utilize
Java
11..
A
A
Anything
else
on
the
action
items
or
good
to
go
cool
all
right.
Nothing
for
me
all
right,
then
next
small
note,
just
the
pipeline
Docker
plug-in,
maybe
we're
looking
at
deprecation
there.
This
is
going
to
have
far
reaching
impacts,
Beyond
just
Jenkins,
so
but
you
need
to
figure
out
and
and
really
do
some
research
and
find
out
what
the
impact
will
be
for
Jenkins
for
other
companies
for
other
usage
platforms,
etc,
etc.
A
This
is
not
something
that
can
just
be
done
without
anyone
noticing,
so
Mark
is
going
to
work
with
Darren
Pope
Damien
de
portal
and
myself
we're
going
to
figure
out
what
needs
to
happen
and
then
once
we
know
what
kind
of
impacts
we'll
have
we'll
start
updating
documentation
and
making
the
necessary
modifications.
But
again,
that's
not
something
that's
going
to
happen
in
the
next
week
or
anything
so
New
Year
and
then
again
we
have
our
December.
A
The
December
newsletter
is
actually
going
to
be
a
2022
recap
newsletter
for
us.
So
when
we
post
it
in
January
and
most
likely
in
the
first
week,
we'll
we're
going
to
be
looking
back
at
all
the
wonderful
accomplishments
we've
had
over
the
last
year.
A
A
We
have
been
able
to
create
this
list
previously
and
we're
still
continuing
to
use
this
as
an
outline
and
kind
of
just
a
marker
for
where
we
should
be
and
what
we
should
be,
including
so
we've
got
themes
like
platform,
modernization,
development,
acceleration
website
improvements
so
for
jenkins.io,
localization
and
simplification
or
Outreach
and
advocacy
security,
infrastructure
and
sponsors.
And
we
want
to
make
sure
that
we
celebrate
and
highlight
as
much
as
we
can
with
this
Bruno
and
Alyssa
are
working
on
the
newsletter
itself.
A
B
I'm
sorry
to
interrupt
you
get
it
go
for
it,
so
the
source
of
Truth
keeps
being
the
same
document
we've
been
using
for
the
monthly
newsletter.
It's
not
that
Jenkins
dog's
office
hours
document
am
I
right,
I'm
keeping
yeah
okay!
Thank
you.
Absolutely.
A
Correct
for
now,
the
the
for
the
Jenkins
newsletter,
we're
still
going
to
be
using
the
draft
template
that
Alyssa
created
and
set
up
and
has
shared
with
everyone.
So
that's
still
the
one
source
of
Truth
for
all
of
this.
This
is
just
the
list
that
we've
been
working
on
to
make
sure
that
if
anyone,
you
know
forgets
one
of
the
many
many
many
many
things
that
have
happened
this
year,
we
can
help
fill
in
the
blank
a
little
bit.
A
Okay,
I'm
sure
stuff,
like
Java,
11
and
17,
and
a
lot
of
these,
like
a
lot
of
these,
were
very,
very
large
things
that
I'm
sure
won't
go
missing,
but
we've
also
had
other
things
happen
like
the
development.
Acceleration
is
a
lot
of
behind
the
scenes,
stuff
and
work
that
is
not
necessarily
seen
But
felt
so
making
sure
we
call
and
highlight
that
stuff
out
is
really
important.
A
We
have
a
lot
of
great
Developers
and
maintainers
in
Jenkins,
so
these
are
really
things
where
we
want
to
make
sure
everyone
gets
a
chance
to
be
recognized
even
if
their
name's
not
attached
to
it.
Everyone
knows
what
they've
been
working
on
so
yeah,
and
then
we
might
end
up
moving
some
of
these
things,
like
the
localization
simplification
may
be
switched
over
to
development,
acceleration
or
platform
modification
or
website
it
can
be.
Some
of
these
are
not
so
hard
and
fast
fat
in
stone.
A
I
had
a
few
things
about
the
elections
and
we
moved
everything
into
Outreach
and
advocacies
because
it
just
makes
sense
and
then
things
like
the
community
site,
which
I
mean
for
me
now.
It
seems
like
it's
just
always
been
the
case,
but
I
I
realize
that
that's
new.
So
these
are
all
things
that
we
want
to
make
sure
people
are
aware
of
the
community
site's
really
nice
and
has
a
wonderful
area
for
everyone
to
discuss,
Jenkins
and
any
capacity.
They
wish.
A
B
C
Okay
yeah,
this
is
all
be
still
yeah.
My
my
assumption
is
it'll,
be
at
least
January
1
now
I'm
I'll
start
I
hope
to
start.
My
writing.
Today
on
my
pieces,
the
the
governance
board
topic
and
some
of
the
some
of
the
items
that
are
that
are
in
the
early
list,
the
platform,
modernization
things
I'm,
gonna
I'm
planning
to
do
most
of
the
writing,
a
bunch
of
writing
there
and
development
acceleration
and
I
may.
C
In
my
past
role
as
as
docs
officer
and
as
Google
summer
of
code
Mentor
do
things
on
the
website
improvements,
because,
because
of
how
personally
grateful
I
am
to
vihan
Farah
for
what
what
he
did
there,
so
so
that
that
piece,
but
that
will
need
at
least
several
days.
So
if
it's,
okay
with
you
Bruno
that,
of
course,
if
it's
until
January
1,
we
don't
intend
to
publish
until
after
the
first
of
the
year.
But
if
you
need
more
lead
time,
we
could.
B
Needed
no,
no,
that's
perfect
with
me,
I'm,
not
in
a
hurry.
So
that's
that's
fine!
Thank
you
and
sorry.
I
had
another
thing
in
mind.
I
saw
earlier
today
because
you
were
speaking
about
g-soc
2023
that
two
people
wanted
to
become
mentors
for
this
year
or
two
more
people.
So
that's
a
good
thing
for
us.
Oh.
A
That's
awesome,
I
hadn't,
seen
that
I
must
have
missed
it.
Thank
you
very
much
for
passion.
That's
awesome,
the
more
mentors
the
better.
Obviously
we
can
reach
more
help.
More
people
work
with
more
people,
the
more
resources
we
actually
have,
and
it's
no
small
commitment.
We
absolutely
appreciate
every
Mentor
taking
on
the
time
and
effort
work
that
comes
along
with
it.
But
that's
that's!
That's
amazing,
I'm,
so
happy
to
hear
more
and
more
people
are
getting
interested.
A
Thank
you
and,
as
far
as
my
update
goes
I'm
looking
right
now,
I'm
doing
a
lot.
The
documentation
of
things
not
listed
here,
but
my
idea
right
now
is
just
to
highlight
and
share
how
much
contributions
and
changes
have
happened.
A
I'm
working
right
now
with
the
community
stats
to
just
kind
of
recap
how
many
blog
posts
have
been
created.
How
many
authors
have
you
know
participated
in
the
blog,
the
number
of
pull
requests
we've
gotten
merged
over
the
last
year,
which
is
almost
900.
It's
that,
like
stuff,
like
that,
so
I
want
to
I'm
working
on
making
sure
that
we're
highlighting
the
community
and
and
their
documentation
contributions
as
well.
So
excellent,
yeah
lots
of
good
stuff
to
come
and
yeah
like
I
said
I'm.
A
Also
writing
up
little
things
for
a
lot
of
these
items.
Just
in
case,
like
I,
said
the
Gap
is
there
so
we'll
have
something,
even
if
I'm,
not
the
most
well-versed
on
something
I
have
enough
in
me
to
go
and
figure
it
out
so
yeah
and
then
water
cool.
What
again
others
will
be
working
on
the
security
stuff
and
so
we'll
just
keep
chugging
along
that
and
we'll
get
that
taken
care
of
and
yeah
most
likely
somewhere
around
January
3rd
to
the
5th
I.
Would
imagine
so.
A
Anything
else
on
the
December
newsletter
or
okay,
no,
no
worries
I'm.
No
thank
you
so
much
for
now
and
then
so
just
to
as
we're
reaching
the
bottom
of
the
agenda
here.
The
second
to
last
item
is
pull
requests
of
note.
A
These
are
just
a
couple
of
items
that
are
coming
up
and
that
have
been
submitted
that
we
want
to
bring
to
everyone's
attention.
First
and
foremost,
the
2.375.2
LTS
release,
which
is
going
to
be
January,
11th
I've
gotten
the
change
login
upgrade
guide
created
that
pull
request
is
submitted
and
open
for
feedback.
So
if
anyone
wants
to
take
a
look
and
review
I
appreciate
that
and
thank
you
in
advance
and
then
the
second
item
here
is
the
web
components
for
jenkins.io.
A
This
is
something
that
Gavin
Mogan
has
been
working
on
for
some
time
now
and
has
made
a
lot
of
Headway
and
we've
got
the
header
and
footer
already
kind
of
working
in
the
plug-in
site,
and
this
is
just
adding
more
Jenkins.
I
o
components
in
addition,
removing
a
bunch
of
stuff
that
we
don't
need
anymore,
so
making
the
page
load
lighter.
We
get
the
consistency
of
look
and
feel
across
multiple
sites,
regardless
of
whether
or
not
they're
Jenkins
plugins.
A
Whatever
have
you,
they
can
all
use
the
the
web
components
so
that
there's
Unity
across.
So
this
is
a
fantastic
he
does.
We
do
want
to
get
some
more
review
and
testing
on
this,
just
to
see
how
everything
looks
and
works,
but
this
is
a
really
fantastic
effort
from
Gavin
and
again
really
appreciate
all
the
work
he's
doing
for
this
Mark.
Is
there
anything
I
missed
on
the
components
that
we
should
also
mention,
or
does
that
cover
everything?
No.
B
C
So
grateful
for
Gavin
to
Gavin
for
being
willing
to
to
bring
It
Forward,
it's
even
being
considered
for
possible
inclusion
inside
Jenkins
core.
Oh
all,
right!
So
now,
now
the
the
exact
components
Gavin's
creating
don't
belong
in
Jenkins
Court.
They
don't
make
sense
they're
just
for
the
Jenkins
website.
But
but
the
concept
of
web
components
is
a
is
an
interesting
and
very
attractive
kind
of
thing.
A
Nice
Definitely,
that's
fantastic,
great,
thank
you
Mark
and
lastly,
on
the
agenda
here,
just
the
pull
request
backlog.
So
one
thing
that
we
want
to,
of
course
always
do
is
encourage
users
to
participate
and
contribute
to
Jenkins
the
pull
request.
Backlog
is
right
now
at
43..
We
can
absolutely
get
it
lower,
but
we
want
to
make
sure
that
people
feel
they're
being
heard
and
their
participation
is
noticed
and
is
being
acted
on.
A
So
our
goal,
when
we
get
back
from
break,
is
to
make
sure
that
we
we
start
getting
this
cleaned
up
and
and
closing
out
some
tickets
are
merging
things
that
can
be
merged
and
making
sure
that
you
know
we're
acting
on
these
things,
they're
not
just
sitting
there,
waiting
contributors
want
to
make
sure
that
they're
heard
felt-
and
you
know
at
least
talk
to
if
not
worked
with
further.
So
this
is
the
absolute
easiest
way
to
get
started
on
that
and
make
that
impact
for
them
and
hopefully
Empower
them
to
continue
contributing.
A
We've
had
a
lot
of
great
additions
and
improvements
this
year
from
the
Google
summer
of
code
projects,
you
code,
Africa
from
all
of
the
you
know.
Different
projects
we've
participated
in
this
year
have
been
immensely
fruitful
for
Jenkins
as
a
whole,
and
we
want
to
keep
that
going
strong
into
2023.,
so
yeah
more
to
come
on
that,
but
something
that
we'll
be
taken
care
of
in
due
time
now
with
that
that
takes
care
of
everything
on
the
agenda.
A
Did
anyone
have
anything
else
they
want
to
share
or
add
before
we
stop
the
recording
for
today's
session
and
say
happy
holidays,
if
not
great
I'll
go
ahead
and
stop
the
recording,
it
will
be
available
within
24
to
48
hours
and
again,
thank
you
to
everyone.
For
the
past
year,
2022
has
been
amazing.
We've
had
so
many
Jenkins
they're,
just
advanced
in
general,
whether
it's
jenkins.io
actual
events
or
just
the
projects
and
participations
we've
been
able
to
collaborate
on.
So
thank
you
to
everyone.