►
From YouTube: 2022 05 27 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
this
is
documentation
office
hours
for
the
jenkins
project.
It's
the
27th
of
may
asia
time
thanks
for
being
here
and
we
will
the
topics
I've
got
on.
The
agenda
include
localization
internationalization
june
lts,
that's
not
from
kevin
the
java
11
epic
chico
africa
contributon
and
the
one
we've
had
good
success
on
recently
working
down
a
few
outdated
poll
requests
any
other
topics
you'd
like
to
put
on
the
agenda
dhiraj.
Do
you
want
some
time
to
talk
about
about
your
get
your
gsoc
project.
A
A
No
weekly
change
logs.
We
rely
on
people
to
review
them
during
the
week
or
review
them
on
monday.
So
we've
got
the
lts
change
log
that
we
we
certainly
will
discuss,
but
weeklies
we
rely
on
reviews.
I
guess
I
guess
I
do
have
one
more
item,
which
is
next
week's
meeting.
A
And
that
one
is
mark
is
out
of
the
office
playing
in
eastern
u.s.
A
Children
actually
a
child,
not
grandchild
child
and
his
wife
and
we're
going
to
go,
have
fun
and
he's
going
to
show
me
his
jenkins
installation.
But,
okay,
let's
stay
on
topic
mark
all
right,
so
anything
else
that
needs
to
go
on
the
agenda.
C
A
All
right,
so
next
key
topic
here
on
localization
crowd
in
is
progressing
no,
I
believe,
no
growth
in
on
number
of
a
number
of
plug-ins
on
the
site.
In
the
last
week.
A
I've
got
an
example
in
the
priority
sorter
plug-in
that
I've
just
completed
and
darren
pope,
and
I
intend
to
do
another
contributing
to
open
source
modernizing
a
plug-in
session.
This
time
on
internationalizing
a
plug-in.
A
Okay,
gsoc
proc
projects.
Kristen,
you
want
to
share
a
brief
description
of
the
pipeline
step
stock
generator
and
what
the
plans
are
there.
D
Sure
so
one
of
the
one
of
the
projects
van
is
working
or
vihan
is
working
on
this
for
improving
some
of
the
more
complicated
steps
for
the
doc
generator,
including
mostly
the
infamous
stage
or
I
think,
step
one
of
the
ones
where
it
takes
like
it's
very
poorly
displayed.
D
So
we're
part
of
it
is
related
to
code,
so
he's
going
to
go
through
and
fix
the
display
of
that
and
make
some
general
improvements
to
the
generator
and
like
just
to
make
it
a
little
bit
more
usable,
maybe
extendable
outside
everything,
so
we're
trying
to
get
together
to
be
able
to
start
like
figuring
out
when
to
work
on
the
project.
Even
though
I
know
that
he's
already
set
up
an
environment
has
like
been
able
to
test
things.
D
The
doc
sigs
meetings
either
one
that
he
can
make
just
to
kind
of
see,
what's
happening
or
like
to
be
able
to
share
progress
and
then
maybe
especially
like
help
get
reviews,
especially
for
the
first
part
of
the
project,
is
going
to
be
figuring
out
what
it
should
look
like
and
we'd
really
appreciate
some
like
documentation,
reviews
to
make
sure
it's
readable,
like
it
looks
in
a
good
format.
D
Just
so
we
start
going
down
like
you
know,
coding
the
right
thing:
don't
really
want
to
create
like
all
this
work
and
have
this
documentation
generated
and
be
like.
Oh
that
doesn't
make
any
sense
or,
oh
you
know
so
like
we
should
have
that
type
of
improvement,
so
be
helpful
for
the
any
type
of
feedback
we're
using
the
documentation,
getter
channel
to
talk
about
the
project.
So
again,
if
you
have
anything
that
you'd
like
to
share
or
on
the
project,
you
can
watch
it
happen
on
the
getter
and
and
everything
should
be
good
cool.
A
A
A
So,
what's
changed
is
gif
and
png
images
have
been
dropped,
replaced
by
svg
images,
but
that
means
plugins
need
to
adapt
their
usage
so
that
they
don't
refer
to
these
long
gone
plugins,
there's
a
worksheet
of
the
plugins
that
are
affected
and
pull
requests
for
many
of
them,
etc.
So
any
questions
there.
B
So
why
did
they
replace
jeff
and
png
images?
Is
it
due
to
some
space
constraint.
B
A
A
A
A
Okay,
next
topic,
then,
is
the
require
java
11
epic.
This
one
is
a
a
nice
example
of
effective
use
of
jira.
What
we
see
here
is
the
issues
the
tickets
that
have
been
the
issues
in
jira
that
have
been
identified
related
to
java
11
and
we're
seeing
progress
on
them
as
we
go
forward.
So
we've
got
two
documentation
tasks
here.
A
A
A
A
C
A
A
A
C
A
Okay,
next
topic,
then
she
caught
africa
contribute
on
so
saturday
is
the
king
is
the
wrap,
is
the
concluding
meeting
the
project
is
done.
The
reports
are
written,
you
can
read
them
on
read
the
reports
on
community.jenkins.io.
A
And
some
reviews
still
pending
two
or
three.
A
Oh,
oh
yeah,
so
so
in
my
case
I
found
it.
It
was
a
little
more
stressful
this
year
than
it
had
been
in
previous
years,
because
we
didn't
have
as
many
people
helping
with
it,
but
it
was
the
projects
themselves
were
more
successful,
I
think
than
last
year,
because
we
chose
simpler
projects.
Two
of
the
three
projects
were
quite
straightforward,
and
that
was
very
important
because
these
brand
new
contributors
have
to
overcome
all
sorts
of
hurdles
as
they
are
preparing
to
contribute.
Their
contribution
can
be
blocked
by
things
that
are
for
long
time.
A
Users,
it's
not
not
a
problem,
but
for
a
brand
new
user,
hey
I've
got
to
get
git
installed.
I
have
to
install
jenkins.
I
have
to
understand
what
a
pipeline
is.
I
have
to
start
it
running
and
deal
with
it
on
my
computer.
I've
got
to
download
and
install
java
all
sorts
of
things
that
any
one
of
them
could
be
a
barrier
and,
and
so
the
choosing
simpler
projects
was
a
good
thing.
B
Yes,
it
did,
and
also
I
read
in
the
two
reports
of
the
participants
and
under
the
section
of
any
room
for
improvement.
I
think
I
noticed
that
both
of
them
suggested
that
onboarding
should
be
like
more
easier
for
them.
So
what
do
you
think
about
that?
Is
it
like
something
that
can
be
improved,
or
is
it
just
something
due
to
the
fact
that
they
were
new.
A
B
A
Think
I
think
it
is
very
much
something
that
can
be
improved.
The
the
on
so
good
observation,
key
key
points
to
improve
better
onboarding
experience
for
the
new
contributors.
A
Now
we've
got
detailed
instructions,
we
had
detailed
instructions
for
them,
but
did
not
emphasize
strongly
enough
that
they
need
to
follow
the
detailed
instructions
and
do
exactly
what
is
stated
there
and
prove
that
they
did,
whereas
last
year
what
we
did
was
we
we
were
quite
rigorous.
You
must
do
step
a
and
you
must
show
us
a
picture.
You
must
do
step
b
and
show
us
a
picture.
A
B
A
A
So
it's
just
it's
it's
one
of
those
where
we
may
want
to
do
something
like
may
may
want
to
do
a
do
an
online
lab
or
something
like
that.
A
C
A
A
Likewise,
the
inclusive
naming
when,
when
they
made
the
changes
correctly,
did
not
require
a
recompile.
A
Because
what
they
were
doing
was
looking
for
places
where
they
could
make
safe
textual
substitutions,
and
we
had
told
them
where
they
were
safe
now
pipeline
pipeline
steps
they
definitely
or
pipeline
help.
They
definitely
did
have
to
recompile.
But
in
that
case
the
two
people
who
were
assigned
were
both
developers.
Who'd
been
doing
development
work
already
professionally
for
a
year
or
two,
and
it
was
done
done
on
local
computers
for
them.
C
A
We
did
we
spent
two
weeks
of
of
onboarding
yeah
and
in
those
two
weeks
we
tried
to
well.
For
instance,
we
we
gave
them
a
tutorial
on
git
and
github
and
the
github
command
line,
and
they
was
very
well
received
and
they
were
all
of
them
were
universally
grateful
for
those
those
tutorials
to
get
them
started.
I
think
they're
correct
in
observing
that
there's
still
more
to
improve
in
getting
started.
A
A
C
A
A
C
C
C
A
C
D
D
D
C
A
And
we're
going
to
go
play
in
the
eastern
u.s
any
I
don't
know
if
any
of
the
rest
of
you
have
access
to
the
zoom
account.
So
I'm
prone
to
say:
let's
just
cancel
the
meeting,
any
objections
to
canceling.
A
A
C
B
A
Well-
and
I
think
we
still
don't
right
so
what
we
have
is
in
sega
interoper
in
the
interoperability
sig
they've
used
the
word
job
to
describe
what
the
jenkins
project
calls
right
of
the
moment
project,
but
the
the
barrier
there
was
tyler,
for
instance,
felt
like
really
and
and
others
who
know
the
jenkins
object
model
say:
look
it's
not
a
project
or
it's
not
a
it's.
Not
a
job.
A
Job
is
a
very
specific
thing
in
a
in
the
jenkins
object
model,
and
for
me,
as
a
user,
I'm
I'm
less
concerned
about
the
object
model
and
more
concerned
that
when
I
refer
to
the
thing
that's
running,
I
call
it
a
job
or
I
call
it
a
build
is
running
and
the
thing
that
defines
it
is
a
job.
C
A
C
A
C
A
A
A
B
C
A
A
C
C
A
C
I
guess
what
I'm
what
I
would
love,
but
you
know
it's
just
me
is
to
give
the
definition
that
match
is
the
operability
sig,
and
you
know
that
this
is
done
to
match
the
operability.
Sig
and
some
members
of
the
jenkins
community
prefer
the
other
or
something
and
just
note
it.
I
don't
know-
and
maybe
that's
too
messy.
Maybe
that's
the
historian
in
me
that
just
wants
to
keep
all
the
history
everywhere.
A
C
Because
I'm
in
a
discussion-
and
some
people
are
talking
about
a
job
and
some
are
talking
about
a
project
and
I
want
to
know
what
the
difference
is
and
I've
got
partisans
of
the
opposite
way.
It
confused
you
know
so
then
do
I
stand
up
to
one
really,
I'm
a
junior
person.
I
stand
up
and
say
no,
no,
that's
the
wrong
meaning
of
job
according
to
glossary,
and
maybe
that's
what
we
want.
I
mean
I
don't
know,
but
I
I've
done.
I
mean
a
lot
of
places
and
I've.
C
A
B
D
A
D
Part
of
it
is
people
might
not
even
really
noticed,
and
it's
more
like.
I
know
that
we've
gone
over
the
whole.
What
is
the
colloquial
use
of
this
versus
like
what
is
the
coding
use
for
the
different
pieces
and
it
I
almost
want
to
argue
like
we
should
use
the
cool
version,
because
that's
how
people
are
going
to
reference
it.
D
A
A
A
D
A
D
It's
like,
even
if
project
is
technically
what
it's
called
in
the
code
that
sometimes
things
change.
I
mean
we're
close.
As
we
say,
workflow
is
still
all
through
the
plug-in,
even
though
we
call
it
a
pipeline.
I
think
that
it
might
be,
even
though
it's
called
a
project
in
the
code.
It's
referred
to
as
a
job
like
and.
A
A
A
A
C
D
A
C
Oh
yeah,
I
I
was
yeah.