►
From YouTube: 2022 09 09 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
A
A
Okay,
so
action
items,
I've
made
no
progress
on
the
archiving
or
on
the
blog
post.
It'll
just
have
to
wait,
given
that
devops
world
is
coming
and
I'm
full
on
focus
there.
That'll
it'll
be
at
least
october
or
more
likely
november.
Before
I
get
there
before
I
get
to
those
action
items.
Google
summer
of
code,
though
this
one's
fun,
because
in
a
we
saw
from
vihan
thora,
the
demonstration
of
the
pipeline
steps
reference
and
its
coding
is
done.
A
A
A
This
is
something
that
he
actually
proposed
and
reviewed
with
kristen
whetstone,
okay,
and
so
they
they
came
up
with
it
together,
vihan
implemented
it
and
he's
he's
the
one
who
structured
who
made
some
nice
structural
changes
in
addition,
but
I
believe
the
concept
of
this
partitioning
and
split
came
with
a
combination
of
him
and
kristen
working
together,
fabulous
yeah,
very,
very
nice.
So
now,
in
addition
to
that
now
there
is
still
there's
one
page,
that's
needing
some
work
and
I've
got
the
action
item
to
see
if
we
can
fix
the
plug-in
source
code.
A
A
That
hints
that
something
went
badly
wrong
and
notice
that
it's
still
loading
the
page
and
the
page
is
quite
quite
huge
and
but
vihan
indicated
what's
wrong.
Is
there
is
some
misformatted
html
inside
the
page
and
the
scanner
thing
can't
handle
that
that
badly
formatted
html
so
but
we
may
be
able
to
just
fix
the
plugin,
that's
contributing
it.
A
A
A
An
extension
point
is
a
way
for
a
a
component
in
jenkins
to
declare
other
people
can
connect
to
this
and
extend
me,
and
so
this
tool,
the
extensions
generator
has
existed
for
years
and
has
been
generating
this
page
well.
This
page
previously
had
80
entries
in
it
now,
thanks
to
fixes
from
basel
crow
it
has
a
hundred
plus.
A
Won't
actually
need
to
because
of
this,
this
piece
is
not
something
that
plug-in
maintainers
or
plug-in
yeah
new
new
plug-in
maintainers
even
need
to
know.
Okay.
B
A
A
A
A
A
B
A
A
A
C
A
Great
yeah
so
and-
and
it
feels
right
now-
it's
it's
feeling
pretty
good.
There's,
certainly
lots
of
work
to
do
because
you
can
imagine
with
25
plug-ins
every
one
of
them
needing
some
modernization
steps,
we're
spending
lots
of
time
figuring
out
what
those
steps
are
and
making
sure
they
work.
That
means
that
it
takes
work
to
do
that.
So,
let's
see,
let's
take
an
example
here:
here's
the
ms
build
plugin
and
we
see
its
source
code
here.
A
B
A
A
A
A
C
A
A
Oh,
this
is
this
is
brand
new
for
this
year.
It's
never
been
done
before,
I'm
not
sure.
Yet
how
well
it's
going
to
work
it's
it's
still.
We
got
to
see
what
what
the
rules
are,
etc,
but
very
interesting
concept.
So
this
allows
things
like
people
who
do
translations
from
one
language
to
another.
Even
if
they
don't
do
it
through
submitted
pull
requests
can
get
credit
for
those
translations.
A
So
the
challenge
for
us,
though,
is
is
this-
is
the
bigger
picture
challenge
for
the
documentation
team?
Is
we
need
to
find
a
set
of
issues
that
are
easily
approachable?
Well,
let
me
let
me
put
a
higher
level
first,
what
I
think
I've
found
is.
There
are
two
key
areas
where
we
can
do
something
with
hacktoberfest
and
do
it
well,
but
there
is
one
where
we've
tried
it
in
the
past
and
it
just
didn't
work,
and
so
I'm
this
year
recommending
we
intentionally
avoid
it.
So
two
yeses
and
one
no.
A
So
the
idea
on
the
yeses
are
jenkins:
dot
io,
those
are
those
are
good
yeses
we
can.
We
can
have
people,
we
can
identify
issues
on
www.jenkins.org
and
create
good
first
issues
or
label
them
so
that
people
can
come
in
and
help
us
with
that
site
and
submitting
documentation
to
the
site
is,
is
not
that
difficult,
so
they
can
do
that.
A
So
that
means
we've
got
to
do
reviews
because
right
now,
if
we
look
at
these
lists,
good
first
issues
is
tiny.
It's
got
five
items
and
hacktoberfest
is
tiny.
It's
only
got
four
items
where
we've
got
146
issues
that
are
candidates,
so
we
need
to
do
a
review,
and
the
proposal
here
for
today
was
in
this
session.
Let's
review
these
and
let's
talk
about
which
ones
we
think
are
good
first
issues
and
which
ones
we
think
are
approachable
for
a
new
contributor.
If
they've
got
jenkins
experience.
A
The
first
one
jenkins.io
we're
the
reviewers,
so
we
absolutely
can
can
control
how
well
and
how
frequently
we
review
the
pull
requests
this
next,
one
plug-in
documentation.
Migration.
So
remember
that
plug-in
word
means
that
we
can't
control,
because
it's
migration
to
the
plug-in
repositories.
Therefore
it
needs
the
plug-in
maintainer.
A
C
C
A
C
A
A
Not
a
good
one,
it
really
it
at
least
it
wasn't.
Last
year
it
didn't
work
as
well
as
I'd
hoped
so.
Here's
an
example:
here's
the
ansible
plug-in
with
21
000
installations
and
the
work
is
listed
as
to
do.
But
when
we
click
ansible
here
and
go
to
github,
we
read
a
pull
request
that
was
opened
a
year
ago
to
move
the
documentation
to
github.
A
A
A
Good
all
right
so
now
now
on
to
the
sort
of
the
bad
news
side.
These
are
tasks
that
we
had
tried
to
do
in
past
hacktoberfest
events
and
we
actually
had
had
people
take
on
the
tasks
and
some
of
them
have
have
finally
been
merged.
However,
it's
turned
out
to
be
much
more
difficult,
so
what
we
have
is
a
notion
of
general
documentation,
migration
to
github.
These
are
pages
that
are
typically
on
the
wiki
and
they're,
describing
some
capability
of
jenkins
either
a
topic
of
this.
A
B
B
Was
just
I
was
glancing
and
listening
to
you
so
not
reading,
but
I
that
that
the
it
looks
like
it's.
It's
still
the
pros
from
when
we
were
all
drinking
the
kool-aid.
The
blue
ocean
was
the
future
of
jenkins
and
we
put
the
disclaimer
in
and
most
of
it
kind
of
stands
up,
but
I
know
there's
a
sectional:
what
is
it
what
happens
to
classic
ui
and
we
say:
well,
it's
not.
We
still
love
it.
It's
not
going
to
be
buried
in
the
backyard,
but
you
know
so
it
would
be.
A
A
B
C
So
it's
about
the
topic
you
and
bazel
were
discussing
about
backend
extension
indexer,
so
I
also
link
shared
the
link
of
the
pull
request
in
the
chat.
So
I
want
my
concern
is
to
understand
what
is
it
doing
and
how
is
it
going
to
be
related
to
the
plugin
help
scoring
project?
If
there's
any
link.
A
C
Because
I
got
a
comment
from
her
lemur
if
I
pronounced
his
name
correctly,
so
he
messaged
us
on
our
project
channel
on
getter
to
sharing
the
link
of
this
pr
and
wondering
if
these
would
affect
the
plugins
course
or
not.
So
I
came
here
to
understand
more
on
that.
A
I
see
okay,
all
right
so
so
then
there
are.
There
are
two
facets
to
it
right,
so,
let's
it
might
be
that
we
want
this
to
affect
the
plug-in
health
score,
but
let's
fir
let
me
first
give
you
an
overview
of
what
the
back
did.
Let's
see,
were
you
here
for
the
discussion
about
the
extensions
concept?
A
No
okay,
so
let
me
give
you
an
overview
of
that.
That
way,
you
understand
what
this
thing
is
and
what
it's
doing,
okay,
so
the
the
extent
extension
indexer
takes
the
list
of
all
jenkins,
plugins
and
extracts
from
them.
The
implementations
of
things
that
jenkins
calls
extensions.
A
Extensions
are
a
way
that
one
component
can
allow
other
components
to
add
functionality
to
it.
For
example,
the
git
plugin
may
want
to
allow
other
people
to
add
additional
repository,
browsers
or
additional,
let's
see,
what's
additional
ways
of
choosing
particular
builds,
and
so
it
implements
that
as
an
extension
and
then
declares
by
creating
a
java
class
that
hey
this
thing
is
an
extension
other
people
can
implement
and
then
other
people
implement
it,
and
it
can
be
interesting
to
know
who
implemented
extensions
for
this
thing.
A
A
So
the
build
chooser
here
is
implemented
by
okay.
The
git
plug-in
implements
several,
but
then
the
garrett
plug-in
garrett
trigger
plug-in
the
flaky
test
handler
and
the
alternative
build
chooser
all
implement.
That
extension.
So
does
this?
Does
this
help?
You
see
what's
happening
here
it's.
This
is
a
an
index
into
the
extension
points
that
are
implemented
in
jenkins.
C
Yes,
so
it
gives
you
an
higher
level
view
of
what
others
have.
I
mean
how
others
have
extended
a
particular
jenkins
or
a
core
functionality.
A
Okay,
and
so
so,
what
what
the
challenge
was
is
that,
prior
to
the
work
of
basel
crow,
this
list
of
extensions
only
had
about
80
items
in
it
and
what
what
had
happened
is
over
the
years,
the
code
that
was
generating
this
page
had
not
kept
up
to
date
with
current
jenkins
development
and
because
it
had
fallen
behind
it
was
not
generating
the
list.
An
accurate
list
of
all
the
extensions.
A
B
Yes,
I'm
sorry,
I
wasn't
looking
at
it,
but
I
can
see
it.
A
A
A
A
A
Yes,
so
it
has
a
jenkins
file,
but
it
is
depending
on
jenkins
2.289.
So
that's
about
60
version.
Therefore,
that's
six
months
older
than
actually
nine
months
or
even
12
months,
older
than
the
recommended
version.
Now
it's
getting
its
documentation
from
the
wiki,
so
that's
not
been
changed
and-
and
so
this
thing
probably
is
just
badly
out
of
date.
It
may
not
even
compile
with
java
11,
yet.
A
A
C
So
that
means
that
plug-in
is
outdated
in
some
way
and
by
some
way
it
could
be
like
it
does
not
have
java
version
recommended
hours
or
minimum
base
jenkins
version,
or
something
like
that.
So
it's
an
indicator
that
there
are
some
pre-needed
steps
that
needs
to
be
updated.
A
A
A
A
C
A
A
More,
oh,
I'm
sure
there
are
more.
I
I
don't
know
what
the
others
are
usually
when,
when
fixing
something
like
that,
it's
it's
a
process
of
discovery
to
understand
this
is
broken.
Oh,
and
this
is
how
we
fixed
it.
This
is
broken,
and
this
is
how
we
fix
it,
and
I
don't
know
all
the
all
the
problems
by
any
means.
A
Much
later
correct
this,
this
is
not.
This
is
not
enough
of
an
impact
on
a
user
to
be
nearly
as
important
as
things
like
are
dependable,
updates,
being
used
and
processed
are
j.
Is
the
jenkins
version
reasonably
current?
Is
the
parent
palm
reasonably
current
is
spot
bugs,
not
disabled,
you
know
is
spot
bugs
allowed
to
run.
Those
kind
of
things
are
much
more
valuable.
I
think
for
users.
C
Okay,
sure
that
makes
sense,
so
I
think
that's
it
from
this
topic.
I'll
also
go
through
this
page
that
you
have
opened
up
extensions
index
and
try
to
understand
more.
So
thanks
for
this
intro.
A
C
And
it's
so
the
list
that
you
were
showing
it
does
not
show
all
the
plugins,
because
not
all
of
them
have
extension
points
defined
within
the
repo
right.
That's
correct!.
A
A
C
A
Okay,
yeah
and
that
that
makes
the
the
probe
even
less
interesting,
at
least
to
me,
because
to
say
that,
oh
you
don't
have
any
issues
with
extension
points
may
mean
you
don't
have
any
issues
because
none
are
implemented
and
if
none
are
implemented.
Why
should
that
be
considered
a
plus
or
a
minus
they're
just
not
implemented?
A
C
A
B
That
that
section,
the
first
thing
is
hardware
recommendations
and
then
it
talks
about
architecting
for
scale
which
references
hardware
recommendations.
So
I
think
those
should
be
and
there
it
needs
to
be
edited
through.
I
was
sitting
there
half
listening
and
but
there's
some
examples
of
some
editorial
changes.
A
B
B
A
B
A
A
B
A
B
I
was
thinking
if,
if
there
was
because
some
of
it,
because
the
tutorials
in
general
should
be
somewhat
duplicating
information,
that's
in
the
other
in
certain
cases,
so
there
might
be
a
subject.
That's
missing
that
you
can
say
here's
your
source,
material
and
you
know,
extract
an
appropriate
amount
of
that
for
the
tutorial
right.
Oh,
but
this
wasn't
one
of
those
so.
A
A
B
A
B
A
A
B
B
A
A
A
A
C
A
A
Okay,
so
that'll
remind
me
to
come
back
and
look
at
it.
We
have
run
out
of
time
on
mike
o'clock
anything
else
that
we
need
to
touch
on
before
we
close
for
the
for
the
day.
Meg.
B
Potential
very
quicky,
I
I
got
mailed
that
you're
having
a
gradle
class
the
day
before
devops
world
you're
having
gradle
training.
Okay,
if
you
skip
to
page
four,
we
have
36.89
and
36.90
that
are
have
plug-in.
Release
page
does
not
have
gradle
equivalent
might
mark
those
attacktoberfest,
and
maybe
somebody
involved
in
the
training
would
like
to
do
those.