►
From YouTube: 2021 11 01 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
Cloud
welcome.
It
is
doc's
office
hours,
it's
november,
the
2nd,
a
reminder
that
we
abide
by
the
jenkins
code
of
conduct
be
nice
to
each
other,
so
proposed
agenda
topics,
one
of
the
gaps
I'm
seeing
is
adding
more
copy
editors
review,
the
change
log
packtoberfest
results,
security
restructuring
and
adopt
a
plug-in
tutorial.
B
A
Oh
okay,
good
question:
okay,
so
let's
put
meeting
time
and
the
evils
of
of
national
modifications
of
time;
okay,
very
good,
all
right,
okay,
good!
So
we
we
will.
Let
that's
a
good
topic.
What
other
topics.
A
Okay,
cool
all
right,
so
let's
take
the
evils
of
national
modifications
of
time.
First,
I
live
near
boulder
colorado,
where
the
atomic
clocks
are
maintained
for
the
united
states
by
the
national
institute
of
standards
and
technology.
We
should
stop
modifying
clocks.
The
usual
pattern
here
is
meeting
time
continues
to
be
utc
based.
A
A
A
Okay,
so
all
right
thus
will
be
one
hour
earlier
next
week:
okay,
local
time
and
please
stop
messing
with
clocks.
A
A
I
love,
I
love,
show
low
area
and
the
white
mountains
are
beautiful,
but
that's
true,
it's
a
different.
Even
so,
my
kids
are
still
in
in
colorado
right
all
right,
so
end
of
plea
about
clocks
are
there.
Let's
see
adding
more
copy.
Headers
is
definitely
one.
I
want
to
discuss
with
the
two
of
you
and
and
see
your
your
sense
of
it,
etc.
A
So,
right
now
we're
shorthanded.
We
have.
How
do
we
do
that?
We
ask
for
permission,
and
then
we
grant
you
permission
if
it's.
If
the
community
discussion
accepts
that
it
would
be
allowed.
B
A
The
question
is:
are:
are
for
to
each
of
you
as
individuals.
Are
you
interested
in
this
additional
role?
Do
you
have
capacity
to
do
anything
with
it
right
now,
we've
got
oleg
who
is
heavily
loaded,
rick
who's
not
not
involved,
hardly
at
all
tim
who's
involved
and
I'm
involved.
So
we've
got
two
and
a
half
involved.
If
you
will
and-
and
I
think
we
need
more
bodies
just
to
schedule-
the
to
spread
the
load
more.
C
A
Right
right,
so
a
copy
editor,
a
copy
editor
is
a
reviewer
and
an
editor
of
content
for
the
jenkins.io
site.
So
they
operate
against
three
repositories:
the
plug-in
wiki
docs
repository
largely
nothing
to
do
there.
The
jenkins.io
repository
lots
to
do
there
that
happens
and
needs
review,
etc,
so
blog
posts
updates
to
documentation,
etc,
and
then
the
iep
repository
is
largely
unused.
It's
it's
for
infrastructure,
enhancement
proposals.
A
So
your
the
primary
role
is
to
review
poll
requests
and
merge
them
after
they've
passed
review
for
jenkins.io.
A
A
A
A
C
I
think
I'll
be,
I
hope,
I'm
having
some
more
time
come
up
boom,
but
who
knows
I'll
say,
but
I
can
definitely
take
some
time
and
even
I
guess,
reviewing
a
few
pull
requests
would
be
helpful
as
long
as
that's
good
for.
A
A
A
Improvement
over
what
what
we're
getting
now
so
okay,
so
I'm
going
to
go
ahead
and
put
as
a
yes
as
always
it's!
No!
No!
Yes,
and
we
understand
you
if
this
is
not
a
commitment.
This
is
not
a
guarantee
anything
like
that.
It's
you're
willing,
if
your
time
allows
if
your
personal
schedule
allows.
B
Could
I
be
a
like
a
silent
apprentice
or
something
mark?
I
could
read
over
them
at
least
flag
things
that
I
thought
you
needed
to
check
sure
yeah.
That
would
be
fine,
yeah.
B
A
Good
okay,
so
consider
copy
editor
in
the
future.
B
A
A
B
E
C
No
right
yeah,
it
sounds
like
even
just
kind
of
reviewing
it
to
ask
the
right
questions
to
bring
your
attention
to
something
that
we
might.
We
might
not
be
confident
like
meg,
and
I
might
not
be
able
to
confidently
say-
is
the
right
action
might
help
speed
up,
be
a
better
use
of
your
time
too.
Right.
B
Something
that
I'm
finding
just
in
the
various
things
I'm
doing
is
a
lot
of
times.
There
is
another
piece
of
documentation,
that's
referenced
from
something
that
sounds
like
the
right
title,
but
you
go
and
look
at
that
and
that's
a
mess
or
the
speech.
You're
reviewing
is
actually
in
conflict
with,
what's
in
the
other
piece
of
documentation,
and
that
takes
time
to
read-
and
I
can
at
least
look
and
say
these
can't
both
be
true.
I
cannot
judge,
which
is
the
correct
one.
A
A
B
But
I'm
saying
that's
something
that
you
could
put
out
also
for
people
like.
If,
if
I
saw
your
request
for
copy
editors,
I
would
not
volunteer
because
I
don't
think
I'm
qualified.
B
A
A
Okay,
all
right,
so
I
will
so
let's,
let's
put
I-
and
I
don't
think
dhiraj
is
here
so
let's
put
to
do
mark
to
propose
the
addition
to
the
jenkins
developers
list
and
and
we'll
see
what
the
conversation
goes.
There.
B
B
A
No,
so
daniel
is
commenting
here.
B
B
A
Okay,
oh
deepak,
gupta,
yes,
okay,
right,
yeah!
Well,
so
deepak
is
not
yet
experienced
enough
with
either
writing
processes
or
the
jenkins
project,
but
he
may
be
willing.
He
might
be
a
good
candidate
to
be
mentored,
just
like
just
like
dhiraj
would
probably
fit
the
same.
The
same
role
right
so
deepak
and
dhiraj
all
would
be
would
be
very
good.
Both
would
be
very
good
candidates.
B
B
Okay,
yeah
and
whether
that
any
of
the
technical
people
I
mean
that's
what
I'm
finding
there's
this
huge
problem
is
that
the
basic
documentation
here
is
just
missing
right.
B
C
A
B
B
The
managing
and
jenkins
administration
stuff
there's
nobody
to
have
that
conversa
to
officially
have
that
conversation
with.
If
I
wanted
to
hit
the
pipeline
stuff,
there's
nobody
to
have
that
conversation
with,
and
it
would
be
nice
if
we
had
a
technical
person
or
two
who
was
willing
to
sort
of
have
that
role.
A
A
A
We
could
also
consider
using
community.jenkins.io
as
a
discussion
spot,
but
for
me,
the
off
this
office
hours
and
the
chat
channels
are
pretty
simple
places
to
do
it.
Mm-Hmm.
A
So
so,
if
you're,
okay
with
that,
I
propose
let's
make
that
better
our
working
plan-
we
just
say
yes,
as
we
have
questions
about
what
should
be
in
the
user
user
handbook
and
where
let's
go,
find,
find
those
answers
ourselves
here
right,
I'm
perfectly
happy
with
that.
Just
pointing
out.
You
know:
okay,
okay,
all
right,
so
I
think
we
got
closure
on
the
copy,
editor's
question,
and
then
we've
got
this
structural
definition
topic
ready
to
go
on
to
change
log,
yep,
sure,
okay,
okay,
so
this
one
is
a
little
different.
A
A
C
A
B
A
A
A
A
B
A
A
B
A
And
by
doing
that,
you
shouldn't
have
any
intermediate
restarts
because
you've
done
the
the
restarts
by
doing
a
hard
stop.
B
Are
you,
okay,
okay,
shut
up.
A
A
A
B
B
A
A
A
B
A
B
A
B
A
A
A
Okay,
good,
so
ready
to
merge,
ready
to
review
when
experts
are
available,
yeah,
good,
excellent,
okay.
So
now
I've
got
an
opinion
question
and
then
I
think
we're
ready
to
switch
and
have
you
share
after
we
get
this
opinion
question
so
darren
and
I
have
completed
the
five
video
tutorials
on
adopting
a
plugin
and
it
was
I
I
kid
you
not.
It
was
a
lot
of
fun.
We
had
so
much
fun.
It
was
just
you
guys.
A
There
are
lots
of
places
that
people
can
help
us
make
improvements,
whether
or
not
they
adopt
the
plug-in.
These
are
steps
that
will
help
right,
and
so
the
idea
is
each
of
these.
Each
of
these
subheadings
here
becomes
a
single
page
on
jenkins.io
in
a
developer
tutorial
on
improving
plug
a
plugin
and
so
they'll
have
a
series
of
15
or
20
steps
that
they
can
take
to
improve
a
plugin.
A
A
A
D
A
B
A
Okay,
so
that's
that's
an
alternate
now.
For
me,
this
one
is
daunting
because,
as
a
reminder,
the
list
is
much
more
than
four
steps.
I
was
thinking
that
myself
yeah
and
for
me
putting
it
at
the
top
here
so
with
20
steps.
Here,
that's
going
to
be
a
serious
distraction
to
the
reader
right,
okay,
so
that
was
that
was
option
two,
and
now
I'm
going
to
show
you
the
third
option.
A
C
A
B
A
So
so,
back
to
the
the
the
the
first,
my
first
preference
for
the
moment
at
least,
is
to
attempt
to
get
this
style
of
layout
and
have
it
be
placed
in
the
now.
I
got
to
go
to
the
right
page
to
show
where
it
will
be
placed,
because
that's
the
other
part
of
this
is
it's
a
little
awkward
to
say:
hey
we're
gonna!
Do
it
because
this
page
does
not
really
have
a
table
of
contents
on
the
left.
Oh
hood,
we
could
restructure
this.
Maybe
that's
now.
B
C
Maybe
yeah,
because
that
way,
it's
consistent.
A
A
B
A
A
A
C
C
E
A
Okay,
so
we
answered,
we
answered
the
question
that
I
had
on
how
to
structure
it.
That's
that's
much
more
work,
but
it's
something
that
dhiraj
and
I
may
be
able
to
make
some
progress
on
and
work
together.
Just
thinking
about
it,
it's
yeah,
you
know
what
it
would
feel
better
if,
if
the
developer
documentation
had
more
of
a
navigation
sense
that
the
user
handbook
has.
A
A
Right
and
so
how
do
you
do?
How
do
you
do
well,
what's
the
architectural
framework,
how
does
it,
how
does
jenkins
think
about
itself
and
these
kind
of
pictures.
B
B
A
A
A
A
D
A
Okay
and
we
have
documentation
user
guide,
that
is
not
a
terribly
attractive
entry
point.
It
really
should.
Oh,
I
know
why,
because
it
this
thing
really
should
open
to
this
page
right
right,
because
truthfully,
the
that
page
isn't
even
accessible
any
other
way,
and
this
thing
doesn't
help
us
that
much.
B
And,
given
that
we
don't
have
the
resources
to
do
some
of
the
basic
stuff,
it's
like
sort
of
need
to
look
the
other
way,
but
right
because
one
thing
is:
I'm
a
developer,
who's
writing
applications
that
are
being
built
by
jenkins
and
I
go
to
the
jenkins
stocks
and
I
see
developer
documentation.
I
think
that's
for
me.
B
A
Yeah,
so
I'm
that
is
a
problem
I'm
not
ready
to
solve
yet
nope.
I
I
think
that's
a
that's
a
much
lower
threat
than
some
of
the
the
requests
for
hey.
Give
me
more
help
about
how
to
use
pipeline.
Give
me
give
me
more
examples
of
pipeline,
so
I'm
I'm
less
concerned
about
people
who
come
here
as
a
developer
who's
using
jenkins.
There.
A
B
B
Right
there,
those
the
first
section
we
take
that
material
and
flip
it
and
make
that
the
top.
When
you
open
the
developer
documentation
at
least
immediately
say
this
is
documentation
for
people
who
want
to
extend
the
functionality
by
of
jenkins.
Oh.
B
B
A
B
A
A
D
A
A
Since
you're
here,
we've
got
a
question
for
you
from
the
earlier
session.
So
let's
meg's,
going
to
test,
drive
a
video
hyperlink
for
us
here
and.
B
E
A
B
A
A
A
B
A
B
A
A
A
Down
a
little
bit,
so
it's
not
showing
oh
it
should
that's
interesting.
So
don't
worry
about
it.
There's
there's
no.
A
A
A
So
dhiraj
we
had
one
question
for
you:
I'm
going
to
share
my
screen
again
so
that
we
can
look
at
it
together
and
use
the
notes
so
right
here.
What
we
one
of
the
topics
we
started
with
earlier
was
adding
more
copy
editors
for
jenkins.io.
A
What
we've
got
right
now
is.
There
are
four
of
us
who
are
copy
editors
me
tim
jacom,
oleg
nanashev
and
rick
in
china,
and
I'd
like
to
propose
additional
copy
editors.
So
what
we
proposed
was
hey.
Meg
has
agreed
that
she'll.
She
would
like
to
be
more
involved
in
reviews,
but
is
not
yet
ready
to
be
a
copy
editor.
A
D
So
that's
an
easy,
yes
from
my
side,
okay,
learning
experience
and
I
would
love
to
yes,
thanks
wait.
All.
F
A
A
Yes,
yeah
just
at
reference
me
say:
hey
or
even
better.
If
you
can
just
leave
comments
or
or
even
go
ahead
and
approve
the
pull
request,
because
as
a
reviewer,
you
can
approve
it,
your
repo,
your
approval
is
non-binding
and
it
doesn't
let
you
merge,
but
when
you've
put
your
approval
on
it,
that
says
hey.
I
think
this
is
ready
to
merge
it's
a
good
way
for
somebody
else
to
realize
they.
They
probably
don't
have
to
do
the
same
level
of
detailed
review,
because
you've
already
done
a
detailed
review.
B
A
A
A
A
A
The
security
team
builds
builds
the
the
the
war
file.
A
D
A
For
something
like
that,
your
your
timing
is
marvelous
for
asking
that.
Thank
you
very
much
for
asking,
because
I'm
okay,
you
pay
him
for
that
yeah.
I
really
should
pay
you
for
that,
because
I'm
about
to
propose
some
things
to
to
my
my
employer,
proposing
that
we
use
linux
found
one
or
more
linux
foundation
funded
internships
to
accomplish
some
very
specific
needs
inside
jenkins.
A
A
And
that's
complicated
right
because
for
exa,
if
we
take
an
example,
the
guava
upgrade
that
just
arrived
on
the
jenkins
on
the
jenkins
weekly
release.
It
will
arrive
next
tuesday
11.0.1
to
31..
A
A
So
so
those
feel
to
me
like
good
candidates
for
a
linux
foundation,
internship,
the
idea
would
be
we
fund
a
three-month
internship
for
a
for
one
or
more
interns,
doing
the
work
mentored
by
experts
from
the
jenkins
community,
where
cloudbees
pays
the
salary
of
the
mentors
and
I
hope,
to
persuade
cloudbees
to
fund
the
outreachy
or
the
the
linux
foundation.
Internships.
A
A
It
is
it's
an
it's
an
evolution
of
that
thing.
Yes,
okay,
okay,
yeah,
so
it's
it's
the
darren
and
I
did
the
five-part
video
series
and
what
what
happened
as
we
were.
Creating
that
series
we
roughly
added
50
more
to
it
just
by
the
act
of
creating
it,
because
we
realized
oh
oops,
here's
another
thing
that
can
be
improved,
here's
another
thing
that
can
be
improved
and
I'm
confident
that
the
rate
of
expansion
of
those
topics
has
not
slowed
yet
so
there
are.
There
are
more
topics
yet
to
be
discovered.
A
Things
like
getting
rid
of
jota
time
using
getting
rid
of
jsr,
305,
annotations
and
using
spot
bugs.
Instead,
those
were
things
that
we
discovered
switching
to
api
plugins
instead
of
loading.
The
api
yourself
in
your
plugin.
Those
those
kinds
of
topics
that
are
hiding
behind
them
are
probably
still
other
things
like
that.
B
A
B
B
Right
and
okay
so
and
it
it
may
be,
but
I
guess
the
big
question
is
whether
we
are
going
to
support
both
elastic
search,
cabana
and
open
search,
and
I
don't.
C
Sorry,
it's
like
I
remember
reading
about
this
was
like
a
massive
drama
inside
of
like
the
open
source
community
stuff.
I
would
almost
say
that,
if
we're
going
to
do
it,
we
should
say
all
three
right
because,
like
people
are
still
going
to
pay,
probably
to
have
their
elasticsearch
stuff,
so
I'd
want
to
make
sure
that
we
like
recover
that
from
the
perspective
of
and.
B
It
may
initially
be
sort
of
like
ldap
and
yeah.
You
know
that
that
they
are
essentially
the
same
from
the
user.
C
A
Yeah
got
it
okay
yeah,
so
so
the
the
I
think,
the
more
immediate
thing
in
that
theme
is
a
thing
called
open
telemetry,
which
allows
observability
of
jenkins
pipelines
and
jenkins
operations
inside
elastic
or
inside
dynatrace
or
inside
other
observability
tools,
and
and
so,
but
that's
that's,
not
open
search.
That's
not
the
that's,
not
the
fork,
the
hard
fork
that
that
amazon
has
done.
This
is
a
very
different
thing.
B
A
Okay,
so
we
we've
hit
hit
my
time
if
you're,
okay,
with
this,
this
one
dhiraj,
let's,
let's
plan
that
we
have
you
and
we'll
do.
This
include
this
topic
in
future
office
hours,
because
I'm
going
to
have
a
discussion
really
pretty
quickly
here
with
people
about
potential
funding
for
several
linux
foundation.
Internships
to
do
these
kinds
of
these
kinds
of
things.
A
A
That's
that's
funded
by
google
but
restructure
the
developer
topics
into
a
developer
handbook.
D
So
how
do
you
differentiate,
like
which
one
is
for
linux,
which
one
is
for
google
season
of
talks?
So
is
it
because
is
it
in
google
season
of
dog
because
it
is
purely
documentation,
project.
B
A
B
A
And
at
least
when
I
read
them,
5500
compensation
to
the
intern,
so
so
a
reasonable
compensation.
Chico
africa
is
one
month
and
500
compensation.
B
A
Right,
oh,
I
see
what
you're
saying
yeah
good
good
idea
that
we
should.
We
absolutely
should
track
those
kind
of
things
and-
and
we've
got
pages
like
that
for
google
summer
of
code.
So
there's
no
reason.
We
can't
do
something
similar
for
google
season
of
docs
put
put
topics
out
there
on
the
jenkins.io
site.
That
say:
hey!
Here's!