►
From YouTube: 2020 08 24 Docs Office Hours
Description
Jenkins documentation office hours August 24, 2020 with topics including Google Season of Docs, Jenkins 2.249.1, terminology updates, and the Jenkins update center
A
Okay,
welcome
everyone.
This
is
the
jenkins
documentation
office
hours
for
the
24th
of
august.
We
excuse
jonathan
morais
he's
got
work
that
needs
to
keep
him
occupied
in
brazil.
Where
he's
based,
we
excuse
meg,
mcroberts
she's
got
other
things
going
on
that
need
to
keep
her
unavailable
great
to
have
marky
jackson.
Here
we'll
go
ahead
and
let's
look
at
the
agenda.
A
B
A
A
We
did
this
kind
of
meetup
for
2.235.1
and
felt
like
this
next
release
is
large
enough
to
justify
doing
it
again,
I'm
doing
it
with
the
features
for
that
release.
Then
terminology
updates.
We
should
discuss
and
look
at
progress
and
talk
further
and
then
a
brief
mention
of
jenkins
update
center
improvements.
A
A
A
A
B
B
A
One
of
the
things
that
that
is
most
of
interest
is,
what's
what's
an
effective
way
to
structure
the
material,
so
that
people
will
understand
what
they're
how
to
get
there
etc.
And
with
your
experience
I
would
particularly
with
your
experience
on
the
kubernetes
project.
I
think
you
may
have
some
good
insights
on.
Oh,
we
should
introduce
this
way
and
then
this
way-
and
then
this
way
she's
open,
I
believe,
to
refining
and
revising
her
plan
based
on
feedback
and
input.
So
the
plan
is
here
linked
from
this
document
and
we
have
a
startup
meeting.
A
B
B
A
A
B
A
No
crisis
there
we're
in
community
bonding
right
now
and
community
bonding
is
a
time
when
we
know
that
it's
it's
not
expected
that
she's
working
the
20
to
30
hours
a
week
during
community
bonding.
This
is
just
get
things
prepared,
but
oleg's
olegs
observation,
I'm
sure
you
saw
in
google
summer
of
code-
is
that
most
projects
that
fail
fail
already
in
community
bonding
and
that's
the
most
visible
problem.
So
so
we
want
to
be
successful
in
community
bonding
to
assure
that
the
project
itself
will
be
successful.
A
A
A
A
So
it's
it
takes
more
work.
It
will
need
review
by
docs
team
member
by
docs
sig
members.
It
will
need
testing
and
assessment
to
be
sure
that
it's
well
described
and
then
for
lts.
We
provide
an
upgrade
guide
and
the
upgrade
guide
in
this
case
is
crucial,
because
this
is
the
first
lts
where
we're
going
to
drop
support
for
the
ancient
microsoft.net
version
that
we'd
use
for
service
management.
Previously
we're
now
going
to
use
microsoft.net
4.
A
A
A
A
A
A
A
A
Okay,
next
piece
and
this
one's
one
marquee,
where
you
may
be
able
to
assist
we've
got
an
online
meet
up
that
I've
proposed
I've
started.
A
draft
haven't
yet
submitted
it
to
the
advocacy
and
outreach
mailing
list,
but
I've
proposed
to
host
an
online
meetup,
describing
the
ui
improvements
talking
through
windows
upgrade
and
then
also
the
looking
forward
to
the
next
lts
to
alert
people
that
tables
to
divs
is
coming.
A
A
B
B
A
Suggestion
was
wait
till
after
the
release
to
give
us
a
day
or
two
of
getting
the
feedback
from
people,
so
that,
if
there's
something
we
need
to
desperately
tell
them,
we
could
do
it
in
the
meeting,
so
the
thought
was
make
it
the
11th
rather
than
the
10th
or
the
11th,
so
that
it's
actually
after
the
release.
I
think
that's
a
good
idea.
I
think
it's
a
very
good
idea.
B
A
A
I
was
just
looking
at
jenkins
core
today
and
saw
as
an
example
the
word
blacklist,
and
that's
one
that
we've
got
an
agreed
use,
a
different
context
to
use
it
use
a
better
word
than
blacklist
so
deny
list
or
an
even
better
term.
If
one
is
available
for
the
context,
so
we
got
a
bunch
of
pull
requests
to
make
there.
B
B
A
Proud
of
it
yeah
delighted
delighted
with
the
results,
and
I'm
really
glad
that's
great
so
last
item-
and
this
is
more
informational
for
folks
who
are
working
on
docs.
The
jenkins
update
center
for
the
last
15
years
has
delivered
its
data
over
http
and
we're
now
upgrading
it.
Daniel
beck
and
tim
jacom
have
have
made
the
changes
that
finish
the
work
that
olivier
bernin
started
to
get
us
from
http
to
https
and
still
using
mirrors.