►
From YouTube: 2021 05 27 Docs Office Hours
Description
Jenkins documentation office hours for May 27, 2021. Primary focus on the tasks that can be shared from Mark Waite to others. Reviewed preparation for the contributor summit and preparation for upcoming community events that might contribute to documentation, like Hacktoberfest.
A
A
C
A
Great
okay,
yeah
so,
and
I
think
that
probably
fits
in
the
sharing
the
work
so
the
the
dirac
I
was
assuming.
We
would
go
through
the
changelog
process
on
during
next
monday's
office
hours,
but
we
could
also
do
it
now
because
there
certainly
have
been
changes
merged
to
the
jenkins
main
line.
So
we
could
have
you
do
a
test
change
log
today,
if
you'd
like
to.
A
A
A
So
in
terms
of
of
other
other
topics
so
kristin,
I
had
largely
assumed
that
you
were
probably
not
available
to
help
with
spreading
the
spreading
the
work
around
that
you're
you're
already
engaged
as
much
as
you
can
be
in
the
in
the
docs.
The
docs
work
that
we're
doing
is
there
anything
that
you
say?
Oh
hey.
I
would
be
willing
to
help
with
that
and
interested
enough
to
do
it.
B
A
B
Open
source
focus
is
probably
gonna
be
on
that
for
at
least
like
the
period
of
time
until
that's
over
the
summer,
but
I
really
do
want
to
be
more
involved
with
kind
of
actually
like
migrating
some
of
the
documentation
and
maybe
upgrading
some
of
our
like
looking
into.
I
think
we
even
saw
some
of
the
like
the
steps,
generator
work
or,
like
you
know,
fixing
some
of
that
stuff
to
make
it
run
locally,
or
even
just
the
when
we
were
investigating
how
to
build.
B
Because
remember
we
were
looking
at
the
build
step
over
right.
I
wanted
to
be
able
to
dive
into
that
a
little
bit
more.
I
started
looking
into
it,
but
I
didn't
you
know
it
was
only
for
a
couple
days
and
then
it's
like
okay.
Well,
they
they
don't
have
they
moved
on
to
other
topics
and
are
working
on
other
things.
So
I
don't
want
to
change
their
focus
so
like
digging
into
more
of
that
type
of
stuff,
but
I
probably
will
not
be
able
to
look
at
that
seriously
until
after
the
summer.
A
B
I
really
do
want
to
do
more
stuff
with
the
documentation,
like,
I
think,
there's
so
much
we
could
do
or
even
like
how
we
were.
I
brought
up
that
one
suggestion
I
still
I
need
to
move
into
our
summary
document
about
like
hey.
Is
there
something
where
you
can
do
like
getting
started
with
like
getting
started
with
jenkins,
like
that
type
of
piece,
like
maybe
doing
some
type
of
program
for
next
year,
for
like
devops
world,
just
going.
A
Which
makes
total
sense.
That
is
absolutely
the
right
thing
to
do
right,
the
the
the
results
we've
you
think
about
what
we've
received
from
google
a
summer
of
code
over
the
years
right
last
year
alone.
It
was
let's
see,
let's
make
the
git
plug-in
faster
the
year
before
that
it
was.
Let's
do
a
git
lab
branch
source
plug-in
and
all
sorts
of
things
like
that
this
year
it's
two
different
cloud
projects
and
and
remoting
improvements.
I
mean
right.
B
B
A
B
A
You
know
you're
combining
multiple
weekly
releases
plus
back
ports,
plus
plus
all
sorts
of
different
levels
of
plus
you're
doing
some
human
based
filtering
to
decide
which
things
should
we
describe
and
which
shouldn't
we
and
all
those
things
are
prone
to
error
and
begging.
For
somebody
who
knows
knows
what
it
means
to
work
on
jenkins,
core.
A
C
C
A
Last
week
last
after
our
last
session,
steps
worked,
okay,
that
that
that
actually
is
quite
impressive,
because
the
I
think
the
first
and
second
times
I
did
it,
I
had
to
go
back
to
original
video.
Oh,
this
is
what
I'm
supposed
to
do.
Oh,
this
is
what
I'm
supposed
to
do.
So
you
are.
You
are
impressive.
Well
done.
A
A
A
A
A
All
right,
then,
the
next
idea
was
have
someone
lead
the
documentation
track
for
the
contributor
summit
and
our
fallback
here
is
it's
also
okay,
if
we
choose
not
to
discuss
docs
at
the
summit,
because
we've
had
good
discussions
in
february.
We
understand
many
topics,
and
this
june
contributor
summit
will
will
have
a
lot
of
different
topics
happening
in
it.
A
A
A
A
A
It
includes
docs
track
one
and
docs
track
two
now
for
the
the
june
25th
summit,
we
will
have
no
more
than
one
track.
We
tried
an
experiment
in
february
where
we
tried.
We
did
two
tracks
widely
separated
from
one
another
by
time,
so
that
we
could
get
asia
and
australia
on
one
track
and
europe
on
the
other
track.
A
A
A
A
A
Deep
dive,
or
something
like
that
and
what
this
these
are.
These
are
just
topics
that
might
be
considered
and
it's
best
to
discuss
those
and
have
mailing
list
discussions
before
they
ever
come
to
the
meeting,
so
that
the
meeting
is
very,
very,
very
effective
at
choosing
which
things
we
should
do
and
which
things
we
should
delay.
D
C
A
A
A
C
A
A
A
A
A
A
A
Okay,
great
yeah,
so
so,
and
we've
seen
some
we've
seen
some
really
cool.
Some
really
positive
things
happen
when
when
we
did
recognition
of
results,
I
believe
it
was
this
ui
ux
hack,
fest,
where
we
actually
used
a
a
github
repository
to
track
who
was
contributing
and
in
the
end
we
had
30
or
40
people
with
their
pictures
on
this.
This
page,
showing
here,
are
the
contributors
for
this
event,
but
but
it's
it's
work
just
to
plan
one
of
these
kind
of
events
and
it
needs
promotion.
It
needs
mailing.
C
A
So
so,
as
the
as
the
leader
of
this,
this
documentation
track,
you
would
probably
be
the
one
proposing
hey
I'd
like
to
run
this
event,
and
this
event
would
be
a
month-long
thing
that
would
give
us.
The
goal
is
to
invite
a
bunch
of
people
to
help
and
you'd
say
I
would
like
to
propose.
We
send
stickers,
send
five
stickers
to
each
person
that
contributes
five
pull
requests.
A
A
A
Okay,
so
that
that's
one
one
one
idea
and
there
there
are
certainly
other
ideas
like
that
where
oh,
what
if
we
did
this
or
what,
if
we
did,
what,
if
we
were
to
to
make
it
what?
If
what
if
we
just
did
a
preparation
for
hacktoberfest,
so
another
alternative
might
be,
and
here's
a
here's,
an
interesting
one,
prepare
for
hacktoberfest
and
and
or
maybe
I
should
say
it
differently-
use
hacktoberfest
to
improve
documentation.
A
C
A
A
A
A
A
A
A
A
A
A
C
D
A
E
A
So
it
is
possible
for
first
it's
possible
for
a
github
issue
to
be
linked
to
a
pull
request
and
when
the
pull
request
is
merged.
The
github
issue
is
automatically
closed,
but
that
doesn't
always
happen
and
therefore
the
condition
you're
describing,
I
think,
is
very
much
possible
not
terribly
frequent
but
very
much
possible
that
there
could
be
a
github
issue.
A
E
E
B
A
A
Okay,
great
all
right.
Well
then,
let's
continue
so
we
were
talking
about.
What
we
were
discussing
was
what
it
would
mean
to
prepare
the
documentation
track
for
the
contributor
summit,
and
we
were
discussing
different
ideas
of
things
that
might
be
discussed
in
that
contributor
summit
things
like
wiki
replacement.
What
would
it
mean?
What
would
it
mean
for
us
to
technically
replace
the
current
read-only
wiki
wiki.jenkins.io
with
something
else,
a
static
website
or
redirects
to
www.jenkins.io
or
something
else,
so
those
were
those
were.
A
The
kinds
of
that
was
one
topic
that
might
be
on
and
before
that
topic
reaches
the
contributor
summit.
It
should
be
discussed
in
the
jenkins
docs
mailing
list
and
and
ideas
should
be
checked.
Possibly
prototypes
should
be
done
so
that
people
can
be
thinking
about
it
before
they
ever
come
to
a
meeting
about
it.
For
the
contributor
summit.
E
E
A
Yeah
the
and
I
agree
wholeheartedly.
If
we
have
the
capacity,
I
would
love
to
see
it.
I
know
I
don't
have
the
capacity,
and
so
we
would
need
volunteers
to
do
that
and
for
me
the
use
hacktoberfest
seemed
like
okay,
that's
probably
more
likely
to
be
successful
rather
than
doing
a
separate
event,
but
it
still
requires
a
lot
of
time
and
effort
to
be
sure
that
we
have
well
one.
Let's
see,
for
instance,
we've
got
to
be
ready
to
show
an
online
meetup
ready
for
a
jenkins
online
meetup.
A
E
A
C
A
That
was
very
well
received
and,
if
you're
aware
of
other
organizations
like
that,
that
would
be
very
interesting.
We're
happy
to
go
talk
to
other
places
about
hey.
This
is
this
is
where
we
can
do,
and
that
makes
it
even
more
important
that
we
have
lots
of
things
ready
to
receive
it.
If
we
get
100
students
who
all
want
to
contribute,
each
of
them
is
going
to
take
a
good
first
issue,
and
we
therefore
had
to
have
at
least
100
issues
ready.
E
A
A
A
C
A
Great
excellent
would
love
well
and,
and
that
that
may
be
a
different
space.
That's
there
is,
it
would
be
feasible
to
say
hey.
We
would
like
to
do
an
advocacy
segment,
an
outreach
segment
in
the
contributor
summit
as
well.
There
is
an
advocacy
and
outreach
special
interest
group
that
would
love
to
have
your
insights
on
ways
to
reach
university
students,
ways
to
reach
college
students,
because,
because
we're
confident
there
are
many
that
would
be
interested
in
and
glad
to
learn
about
jenkins
and
glad
to
contribute.
A
A
And
either
of
those
places
there
are
people
who
are
or
are
working
diligently
to.
So,
if
you'd
like
to
be
involved
in
how
to
reach
university
students
how
to
reach
college
students,
that's
that's
a
great
way
to
do
it.
Alyssa,
and
I
can
even
give
you
a
name.
Alyssa
tong
is
very
interested
in
reaching
college
students.
A
D
A
D
C
C
A
So
the
the
other
topic
then
was
and
again.
This
is
all
part
of
this
potential
contributor
summit.
We
could
talk
about
lfx
community
bridge
project
ideas,
we've
been
talking
about,
should
we
continue
jenkins
on
kubernetes
as
a
funded
project
right
now,
ry
sudakar
is
working
on
the
the
topic
without
even
being
funded
and
first
pr
has
been
submitted
and
the
first
pr
was
for
plug-in
installation
manager.
A
A
C
A
A
A
And
there
are
all
sorts
of
things
like
that:
let's
see
we
used
to
have
things
called
white
lists,
which
is
now
an
allow
list,
and
we
have
blacklists,
which
is
now
a
deny
list
and
there's
a
long
set
of
terminology
like
that,
and
those
terminology
updates
require
changes
to.
Let's
see
they
require
require
plug-in
changes,
they
require
core
changes.
A
A
A
So
this
page
will
like
take
a
little
bit
of
time
to
x,
to
open
yeah
there
we
go.
What
this
shows
is
the
progress
we've
made
migrating
plug-in
documentation
from
the
wiki
into
the
source
code,
repository
of
the
of
the
plugin,
and
you
can
see
that
we've
successfully
completed
684,
but
we
still
have
over
1
000.
Yet
to
do.
C
A
A
All
right,
I'll,
post,
the
recording,
probably
later
today
or
tomorrow,
thanks
everybody.
Thank
you
very
very
much
now
I
will
be
available
again
next
week
on
this.
At
this
same
time,
but
two
weeks
from
now,
I
will
not
that
will
be
post-surgery
for
me
thanks
very
much
for
all
you're
doing
I'll
look
forward
to
talking
to
you
at
future
office
hours.