►
From YouTube: 2022 09 16 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,
it's
the
16th
of
of
September,
and
this
is
documentation,
office
hours,
Asia
topics,
I've
got
on
the
list
for
today,
action
items,
devops,
World,
2022,
techtoberfest
and
any
other
topics
that
you'd
like
to
add
to
the
list.
B
B
A
You
were
you
were,
you
were
marvelous
and
it
was
a
great
story
to
tell
the
show
hey,
look
we're
making
progress
in
every
office
hour
session,
so
this
earlier
today,
when
we
did
it
in
Europe
office
hours,
it
was
the
first
time
they've
actually
processed
anything
for
Oktoberfest,
so
action
items,
nothing
to
report
of
positive.
The
things
are
all
still
on
the
backlog
and
probably
will
stay
there
for
six
weeks.
I
do
have
to
actually
I
guess.
I
should
warn.
A
A
A
A
Great
foreign
thanks:
okay
devops
world,
so
we've
had
several
blog
posts,
arrive.
A
On
various
topics
for
devops
world-
and
you
can
read
them
Etc
and
the
modernizing
a
plug-in
pull
request
has
been
switched
to
Ops
bad
choice.
Let's
try
that
that's
what
I
get
for
embedding
an
old
URL
just
a
minute
we'll
go
find
the
real
one.
Now
so.
A
This
thing,
and
if
I'm
lucky
it
will
here's
the
blog
post
properly
giving
credit
for
me
and
for
diraj
writing
it
and
I
upgraded
diraj's,
biography,
based
on
his
submission
for
a
Google
summer
of
code
and
so
Meg
you're.
Certainly
welcome
to
review
would
love
to
have
reviews
anyone
else
who
can
so
the
here's,
the
the
link
now
oh
right,
I
know
what
it
was
I
had
to
change
the
location
because
I
had
scheduled
it
in
the
last
guest
published
in
June,
and
it's
only
September.
Now.
B
Okay-
and
you
meant
to
have
this-
the
video
here
showing
Oktoberfest
of
2021
yeah.
B
A
The
video
is
just
a:
this
is
a
link
to
the
to
a
playlist
of
of
five
videos
that
were
all
created
during
that
time.
A
So
this
one
is
in
part
two
and
it
jumps
into
it.
However,
deep
in
order
to
show
that
step
such
good
work
yeah,
it's
been
fun.
It
really
has
so
so
plan
to
merge,
September,
21
reviews,
welcomed
and
encouraged
and
happy
to
hear
any
improvements.
Etc.
B
A
Okay,
next
topic,
then,
is
hacktoberfest,
and
this
one
is
where
the
work
happens.
So
we've
now
got
a
page
on
jenkins.io
for
Oktoberfest
2022.,
and
it
highlights
how
you
get
connected,
what
you
do
list
of
repositories
marked
for
Oktoberfest,
so
there
are
right
now
71
in
the
Jenkins.
Oh,
this
is
the
wrong
yeah.
This
is
no.
This
is
the
right
one.
He
has
71
repositories
currently
marked
for
Oktoberfest
and
Etc.
A
So
now
the
challenge
for
us
in
the
doc
Sig
is:
we
need
to
identify
good
first
issues
and
others.
Now
I
learned
that
there's
a
we
had
initially
done
a
marking
of
these
to
say:
hey,
we'll
mark
them
with
hacktoberfest.
If
they
are
need,
some
skill
need
some
experience
and
we'll
mark
them
only
with
good
first
issue.
If
they
are
good
for
a
first-time
contributor,
but
the
problem
is
hectroberfest
instructions
say
Mark.
All
pull
request
are
all
issues
as
hacktoberfest,
so
good,
first
issue,
plus
Octoberfest
means
it's
easy
and
only
hacktoberfest
means
it's
more
challenging.
A
B
A
Are
not
okay,
although
actually
this
one
so
good
thing,
you
asked
that
so
here's
one
that
is
incorrectly
marked
that
way.
So
let's
fix
that
or
is
that
going
to
be
grabbed
by
somebody
that,
like
maybe
someone
who
is
familiar
if
they
were
thinking
about
no
well
see
the
problem
we've
got,
is
any
of
these
Wiki
migration
proposals
end
up
creating
more
work
for
us
than
than
they're
actually
worth
because
we've
got
a
lot
of.
A
They're
now
mistaken
that
are
just
wrong,
and
so
now
we
have
to
have
an
expert
that
goes
in
and
corrects
all
of
the
mistakes
in
the
page
and
the
reality
is.
If
we
look
at
all
the
bug
reports
that
are
listed
with
the
wiki
migration
label
or
all
of
the
the
pull
requests
with
Wiki
migration,
there
are
about
10
of
them
that
are
blocked
right
now,
because
nobody's
done
the
the
done
the
whole
whole
bunch
of
work
to
go
in
and
correct
all
the
all
the
errors
in
them.
A
B
Does
an
outsider
know
that
our
do
we
have
does
a
description
of
each
issue
include
information
that
the
wiki
information
itself
is
obsolete.
So
this
involves
that
or
if
we
or
do
we
have
a
general
or
maybe
an
octo
said
everything
that
is
currently
marked
as
Wiki.
Migration
are
things
that
do
not
are
not
easy
migrations
or.
A
We've
so
we've
definitely
got.
We've
definitely
got
instructions
here
in
office
hours
that
say:
Wiki
migration
is
not
recommended
for
hacktoberfest,
but
I
think
you've
got
a
good
point.
Maybe
what
we
ought
to
do
is
also
put
text
on
each
of
these
Pages
saying
this
requires
additional
skills,
or
rather
it's
it's
not
so
much
these
as
here
the
issues
that
are
Wiki
migration,
because
the
the
pull
requests
that
are
Wiki
migration
there's
they
just
have
to
be
reviewed
by
experts,
but
these
issues
should
not
be
marked
as
oh,
okay,
a
redirect.
A
A
A
A
A
B
A
A
B
A
A
A
A
A
It
would
be
rephrased
as
something
even
more
more
blunt
than
the
blue
ocean
disclaimer
that
we
put
into
other
other
pages
right,
because
this
one
blue
ocean
is
is
actively
being
maintained
but
not
being
enhanced.
Evergreen
is
not
being
maintained,
not
being
enhanced
and
is
shut
down,
mm-hmm,
so
so
yeah,
but
now.
A
Now
the
question
is:
what
do
we
do
with
it?
So
we
should
we
could
I'm,
seeing
the
challenge
for
me
is
I'm
not
comfortable
that
a
new
person
could
successfully
do
that
one.
It
could
be
a
Oktoberfest
topic,
because
I
think
I
think
it
might
be
worth
saying.
Hacktoberfest
and
saying:
look
Evergreen
has
been
shut
down
the
page,
the
pages
that
reference
Evergreen.
A
A
A
A
B
A
A
We
certainly
can
apply
tags
after
the
fact
right.
If
someone
says
Hey
I
want
to
do
this
and
they're
successful.
The
bigger
problem
we've
had
in
the
past
has
been
people
saying:
I
want
to
do
this,
and
then
they
don't
do
anything
so
so
I'm
I'm
we're
more
than
happy
to
tag
something
hacktoberfest
after
after
they've
started
on
it.
That
would
be
just
fine
foreign.
A
A
B
A
See
a
quote
reply:
okay,
got
it
now.
The
documentation
on
that
page
on
that
page
should
note
the
risk
that
and
incorrectly
entered
email
address.
A
A
A
A
A
Laughs,
okay,
yeah.
For
me,
the
problem
is
this:
one
really
needs
skills
and,
and
when
I
talked
with
Damian
de
portal
about
it,
he
thinks
it
may
be
that
the
best
thing
we
can
do
is
completely
replace
this
particular
tutorial
with
use
something
done
using
Docker
compose
to
create
the
multi-component
thing
that
we
really
need
for
this
tutorial.
A
So
I'm
hesitant
to
I
in
fact,
I'm
unwilling
to
mark
this
one
as
a
good
first
issue,
because
it
it
requires
a
level
of
skill
that
if
I
picked
it
up,
I
think
I
would
spend
three
or
four
days
working
on
it
before
I
was
confident,
I'd
fixed
it.
Okay,.
A
We
don't
tell
you
that
in
order
to
use
agent
Docker,
you
have
to
have
a
certain
set
of
plugins
installed
and
you
have
to
have
a
certain
set
of
permissions
on
your
on
what
your
Jenkins
controller
is
allowed
to
do
with
Docker
and
it's
uncommon
for
people
be
to
be
allowed
to
do
that,
and
this
one
assumes
that
you've
probably
got
executors
enabled
on
your
controller
or
you've
already
added
an
agent,
and
of
course
it
never
says
any
of
those
things
and
and
it's
it's,
this
thing
is,
is
really
really.
A
Oh
no
I
think
what
he's
it's
saying
here
is
a
bewildering
number
of
Docker,
plugins
and,
and
that
is
correct.
There
are
multiple
doctors,
each
with
a
different
approach
to
how
you
do
Docker
with
Jenkins
and
and
therefore
it
makes
it
amplifies
this
even
worse,
which
plug-in
is
it
that
provides
the
docker
declarative
step,
and
you
have
to
find
that
one.
B
A
No,
no
wait
a
sec
this
here,
the
the
user
says
installing
the
docker
pipeline
plug
and
fix
the
problem.
Maybe
we
should
Mark
this
as
hacktoberfest
yeah,
that's
enough
and
then
maybe
you
have
them
as
part
of
it.
You
know
clearly
test
the
documentation,
but
if
this
is
all
it
takes,
I
think
this
could
be
great.
B
A
B
A
A
A
A
A
A
A
B
A
A
Do
you
want
to
just
look
at
look
at
documentation?
We
could
put
the
three
of
us
in
parallel.
We
could
look
at
the
pages
together.
Looking
for
things,
for
instance,
a
common
area
where
we
had
problems
before
was
in
the
developer
guide.
No
developer
is
probably
a
bad
choice
for
first-time
contributors.
Isn't
it
yeah.
B
B
A
A
B
A
B
B
I,
don't
like
straight
glossaries
I
think
they
tend
to
be
useless
and
annoying
and
stuff
like
that.
But
but
like
for
I,
think
plug-in
there
was
a
link.
I,
don't
know
where
it's
going.
B
A
The
links
within
the
glossary
are,
and
so
it
might
be,
that
what
each
one
should
say
is
for
more
information
about
this
topic.
Go
here
and
then
take
you
to
a
better
page
or
try.
A
more
in-depth
page
agent,
for
instance,
could
easily
say:
hey
here's
this
page,
all
about
agents
pipeline.
Here's,
here's
a
whole
section
of
the
document
about
Pipelines.
A
Yeah
so
now
is
the:
is
it
likely
to
be
a
source
of
significant
contention
when
someone
chooses
to
link
to
using
Jenkins
agents
instead
of
linking
to.
A
Managing
agents
managing
nodes,
and
so
My
worry
is,
is
that
two
that
there
may
be?
There
may
be
enough
contention
there
to
make
a
poor
experience
for
this
first-time
contributor.
B
Well,
on
the
other
hand,
they
should
be
able
to
look
I
mean
they've
got
a
brain,
keep
looking
just
because
you
found
one
reference,
keep
looking,
and
maybe
you
know,
and
for
for
a
lot
of
these
things
you
may
you
know
that
makes
sense.
You've
got
here's
how
you
use
it,
here's
how
you
manage
it
or
here's
how
you
troubleshooting
to
take
any
of
those
topics
and
make
sure
that
they
flow
through
to
each
other
core.
Would
how
do
you
install
core.
B
A
B
Right
and
there's
a
security
section
on
agent
security,
I
think.
Isn't
there.
A
A
Yeah
I
don't
see
it
at
the
moment,
but
but
it
there
could
be,
could
well
be
something
so
the
agent
listen
port,
for
instance,
is
certainly
there.
So
this
is
your.
Your
suggestion
is
extend
the
glossary
so
that
it
becomes
not
just
a
definition
of
the
term
but
also
links
to
other
useful
content
related
to
that
term.
In
the
in
the
documentation
right.
B
If
you
wanted
to
Bulletproof
the
thing
of
course,
we
could
make
a
series
of
we
could,
instead
of
having
one
big
one
you
could
have.
You
know,
make
the
agent
glossary
item
link
to
other
docs
make
the
control.
You
know
we
could
just
and
we
could
hand
feed
it.
We
could
say
make
it
point
to
here
and
there
right,
then
writing
the
then
it'd
be
easier
to
do
the
work
than
to
make
the
tickets.
A
B
But
that
meant
to
go
and
I
mean,
but
it's
also
I
mean
it's
a
good
well,
and
you
know
what
else,
because
it
is
Hot
Chocolate
Fest.
If
you
got
some
people
who
are
interested
in
this,
you
could
two
or
three
could
sit
down
with
somebody
with
one
of
somebody
who
knows
stuff
and
go
and
look
through
and
say
you
know,
and
we
could
Point
some
things
out,
because.
A
B
B
B
A
B
A
Sure
sure,
so,
let's
let's
talk
about,
for
instance,
what
if
we
said
agent
and
node
Gloucester
entries,
they
make
a
logical
grouping
right.
What
are
are
there?
Some
others
like
that
so
job
and
build
and
artifact
might
be
well
connected.
Oh
cloud
cloud
probably
connects
to
logically
to
agent
executor,
probably
connects
logically
to
agent.
Yes,.
A
The
the
evil
term-
please
don't
use
it,
use
the
correct
term,
okay,
cool,
absolutely,
even
even
that
one
could
include
a
link
to
hey
and
here's
the
blog
post
that
describes
that
it's
deprecated,
oh.
A
B
A
B
I
actually
think
it's
bad.
That
slave
is
not
listed
here
and
because
people
in
talking
still
I
mean
one
thing
that
a
glossary
is
useful
for
is
if
you're
in
a
conversation
and
people
are
throwing
out
terms-
and
you
don't
know
what
they
are
they're
a
quick
memory
thing
and
if
some
and
people
still
talk
about
your
slaves,
where
they
talk
and
I
go,
look
and
I
got
nothing.
Mm-Hmm
tell
me
it's
an
old
evil,
bad
word,
you
shouldn't
use
it
and
here's.
A
B
B
What
about
making
the
issue
like
this
would
be
extend
agent
and
related
entries
and
then
for
the
top
just
for
the
title
and
then
have
the
list
inside
the
description.
Good.
A
Now
the
challenge
here
is,
we
need
destinations
for
them
and
I'm,
not
sure
there
is
one
for
cloud
agent
glossary
entry
should
connect,
should
link
to.
A
B
May
be
security,
but.
B
A
B
A
B
A
B
Agree
but
I
I
think
that
what
I'm
saying
is
I
think
that
information
is
someplace
information
about
how
the
agent
is
kept
secure.
Oh
there's
another
one,
ephemeral
agents
are
safer,
there's
also
the
issue
of.
If
you
use
an
agent
over
and
over
again,
it
could
get
tainted
by
malware
and
affect
another
build
there.
A
A
A
A
A
Oh,
oh,
well,
that's
a
good
point.
There
are
yeah,
so
for
me,
cloud
is
Cloud
in
the
context
of
the
glossary
was
talking
about
agents
in
the
cloud
right,
Dynamic
agent,
provisioning
through
Azure
and
ec2.
No.
A
A
B
B
A
What
I
was
looking
for?
More
was
Cloud,
so
Adobe
Cloud,
actually
Adobe
Cloud
manager
would
be
another
one
that
let's
see
what
extension
points
it
has
nope.
Okay,
so
so
maybe
Cloud
providers
are
not
done
through
extension
points.
A
A
A
B
A
And
that's
and
that's
definitely
not
the
no,
not
the
ec2
plug-in
right.
A
Okay,
so
well
all
right
back
to
our
okay.
We've
got
Cloud
I'm,
so
cloud
entries
should
late
or
how
about
this.
The
cloud
entry
should
link
to
more
plugins
for
it
shouldn't
it
should,
including
all
right,
Oracle
cloud,
Adobe,
Cloud
manager,.
A
I
think
hetzner,
let's
see
who
else?
Oh
Google
Cloud.
B
B
A
But
let's
include
it
Azure
and
fingers.
A
A
And
now
I
really
do
want
to
check
to
see.
If
hetzner
has
one
I
thought
they
did.
This
is
a
German,
yes,
hetzner,
Cloud,
okay,.
A
Yes,
okay,
all
right,
so
that
was
that's
one.
Addition
to
the
glossary
are
there,
others
that
are
as
promising,
for
instance,
build?
And
what
else
might
we
link.
A
B
B
A
A
B
A
A
B
B
Yeah
there's
a
subsection
for
install
for
kubernetes.
A
B
A
A
Okay,
now
on
that
theme
should
be:
should
the
glossary
entry
that
says
Linux.
Oh
there
isn't
one
okay
good.