►
From YouTube: 2022 05 26 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
B
Okay,
thanks
welcome
to
doc's
office
hours
for
jenkins.
This
is
the
european
edition
for
thursday
may
22nd
the
26th
today's
agenda.
We
have
some
action
items
that
if
mark
wants
to
go
over
the
dock
mailing
list
archival
and
switching
to
the
community.jenkins
io
for
docsig,
we
have
our
google
summer
of
code
update
regarding
pipeline
steps,
stock
generator
and
vahanas
here.
So
we
can
talk
more
about
that
localization
and
internalization
progress
report
from
alex
if
he
joins.
B
We
can
definitely
talk
about
that
right
now,
since
he's
not
here,
mark
will
be
the
stand-in
for
us.
B
The
june
lts
change
log
upgrade
guide
and
blog
post
is
something
that
I'm
working
on
and
we'll
be
able
to
speak
to,
and
we
have
the
require
java
11
epic
as
well
in
addition
to
the
june
lts,
so
I'm
working
on
the
documentation
there
as
well
and
finally,
we
have
some
recap
info
and
since
we're
getting
towards
the
end
of
our
chicago
africa
partnership
mark's
going
to
have
an
update
for
us
there
so
first
off
mark.
Did
you
want
to
go
over
the
this
topic
here?
A
Just
to
remind
me
that
I've
got
to
do
it,
we've
got
we've
got
agreement
and
consensus
that
the
docs
mailing
list
is
too
low
usage
to
justify
keeping
it
and
google
groups
is
just
not
evolving,
whereas
community.jenkins.io
and
the
discourse
server
that
hosts
it
evolves
very
nicely.
Has
a
great
user
interface,
much
easier
moderation
tools,
it's
just
better
for
us,
so
we'll
follow
the
model
that
some
other
communities
have
done
of.
Switching
from
a
google
groups
based
mailing
list
to
using
a
disk
or
size
site.
In
our
case,
community.jenkins.io.
A
I
think
that's
where
we
let
welcome
vietnam,
so
vihan
tell
us
something
about
yourself
and
give
us
an
introduction
to
the
into
the
project.
C
Hello,
everyone,
this
is
vihan
and
I'm
from
pune
maharashtra,
india
and
I've
been
selected
as
a
gsoc
contributor
for
the
pipeline
step,
documentation,
generator
improvements
and
under
this
project
I
aim
to
improve
the
pipeline
steps
that
are
generated
on
the
chain.
Gauge.Io
website,
and
specifically
there
were
a
couple
of
things
that
were
that
were
in
my
mind,
right
now.
So
first,
the
first
thing
was
improving
the
layout
of
the
page.
C
So,
as
you
can
see,
the
page
has
a
lot
of
information
that
is
not
abstracted
or
abstracted
in
a
very
the
least
way
possible
for
the
user,
and
this
creates
this
actually
crowds
a
page,
a
lot
and
if
a
user
wishes
to
find
a
piece
of
information
that
they
want,
it
becomes
eventually
harder
for
them.
C
So
the
first
improvement
I
thought
of
was
to
go
ahead
and
create
a
navigation
bar,
a
sidebar,
a
sort
of
structure
and
I've
included
that
in
my
proposal
as
well,
so
first
of
all
the
navbar
that
we
have
on
our
documentation
currently,
even
for
that,
if
you
see
if
you
scroll
down
so
if
you
have
a
longer
page
and
you
scroll
down,
that
navbar
sticks
to
the
page
and
it
eventually
disappears
when
you
scroll
further
down
so
first
thing,
a
general
improvement
on
the
entire
documentation
site
would
be
to
create
a
sidebar
that
is
static
on
the
page,
which
is
does
not
move
so
user
will
be
able
to
navigate
easily.
C
Then
what
we
can
do
is
for
pipeline
steps
specific
documentation.
I
plan
to
create
a
separate
sidebar,
which
will
be
stacked
under
the
main
sidebar
much
like
the
java
documentation.
If
you
would
have
seen
that
so
the
oracle
documentation
from
java,
you
have
those
classes,
and
then
you
have
those
objects
different
different.
So
you
have,
for
example,
awt,
and
then
you
have
all
the
classes
for
that.
So
something
like
that
for
the
steps
as
well
so
for
every
plugin.
C
We
would
have
a
section
for
them
and
when
a
user
clicks
that
in
the
nav
bar
it
expands
and
shows
them
all
the
steps
associated
with
that
section,
and
when
a
user
clicks
on
that,
they
will
be
led
onto
that
page
and
that
page
again
would
consider
which
would
be
consisting
of
a
sidebar
that
has
all
the
parameters
of
the
steps
so
for,
for
example,
if
we
take
a
step
as
checkout
step
so
for
that
we
have
different
parameters,
so
those
parameters
would
be
listed
down
and
eventually
what
will
happen
is
some
and
a
piece
of
information
that
was
present
on
a
single
page
for
a
user.
C
It
would
be
divided
and
the
way
I
plan
to
do
it
would
be
either
configuration
based.
So
we
know
exactly
what
steps
need
to
have
a
separate
page
of
their
own,
so
what
parameters
need
to
redirect
to
a
different
page,
so
that
can
be
configured
either
manually
or
we
can
do
it
automatically
by
considering
a
fixed
threshold
value
of
the
length
of
the
documentation
for
those
parameters.
C
So
these
were
the
two
basic
things
that
I
had
in
my
mind.
Right
now
and
yeah.
I'm
in
a
phase
of
actually
learning
how
the
documentation
generated
I'm
trying
to
get
some
pull
requests
on
jenkins.io,
as
well
as
the
pipeline
stepdoc
repository
to
get
a
look
around
the
code
so
yeah.
Thank
you.
B
Wonderful
that
all
sounds
really
amazing
beyond
I'm
excited
to
see
what
happens
and
what
you
got,
what
you're
able
to
get
done
with
that
and
just
as
a
just
as
just
a
piece
of
info,
kristin
and
mark
who
is
the
other
mentor
for
the
google
server
code.
A
B
Going
to
share
that
the
mentors
for
the
google
summer
recruit
project
are
more
often
in
the
asian
hours
for
the
doc's
office
hours.
So
if
you
want
to
collaborate
with
them,
it
might
be
easier
to
connect
with
them
at
that
point
in
time.
It's
totally
up
to
you.
You
don't
have
to
go
to
that
meeting,
but
they
are
typically
there
as
far
as
just
being
able
to
meet
them
talk
to
them,
get
and
get
some
more
info
from
them.
B
So
and
if
you
don't
have
the
link
to
that,
we
can
share
that,
and
it's
also
on
the
jenkins
events
calendar.
So
you
should
have
that
if
you
have
access
to
getter
and
everything
else.
C
Yeah
sure
so
we
actually
discussed
a
probable
meat
time
for
us
and
as
of
now
christian
has
not
reverted
to
that
mail,
but
we
would
probably
find
thursday's
office
are
to
be
more
suitable
because
fridays
is
slightly
early
for
me,
it's
like
7
30
in
the
morning,
so
this
is.
This
is
perhaps
a
time
that
is
fine
for
me
and
the
other
two
mentors
are
neem
kosher
and
hershey
chopra,
and
they
both
are
also
from
india.
C
So
I
guess
it
actually
depends
on
them,
so
we'll
we'll
probably
discuss
and
find
out
a
suitable
time
for.
A
Don't
be
shy
at
proposing
an
alternate
time
for
asia
office
hours
if
if
it
turns
out
that
harshit
and
kristen
can
could
have
a
better
chance
of
meeting
if
we
were
to
shift
asia
office
hours
one
hour
later,
we
could
do
it.
Two
hours
later
gets
a
little
bit
more
of
a
push,
but
one
hour
later
is
quite
easy.
A
So
so
don't
be
shy
about
saying:
hey,
there's
the
the
reason
for
thursday's
eight
for
the
eight
friday
asia
docs
office
hours
is
so
people
in
asia
can
get
there
and
if
that
hour
of
the
day
doesn't
work.
Let's
look
for
a
better
time
now
you
have
to
be
mindful
that
I'm
12
hours
away
from
you
and
and
therefore
choose
carefully
if
you
choose
noon
india
time,
you'll
have
to
have
to
do
it
without
me,
because
midnight
is
is
just
too
late
for
me.
A
Right
well,
and
that
was
why
that
was
why
the
docs
office
hours,
the
asia
docs
office
hours
were
set
where
they
were,
as
they
are
exactly
after
the
old
asia
office
hours.
Now
now
that
now
that
docs
now
that
gsoc
office
hours
have
changed,
they
are
now
only
happening
during
europe
time,
but
so
so
that
gives
us
more
flexibility
on
when
we
want
to
do
asia,
docs
office
hours.
A
C
A
So
vihan
did
you
want
to.
Did
you
have
any
desire
to
show
us
any
screenshots
of
ideas
that
you've
already
prepared?
It
sounded
like
you've
done
quite
a
bit
of
of
good
research.
Do
you
have
anything
you
want
to
show
us,
because
it's
kind
of
fun,
sometimes
in
these
office
hours,
to
let
let
a
contributor
share
their
screen
and
show
us
something?
C
So
yeah
current
firm
proposal,
I
only
I
had
a
design
which
were
not
implemented
in
the
website.
So
currently
I
have
not
prepared
it
on
the
jenkins
at
io
website,
like
as
it
is,
but
I
plan
to
do
that
very
shortly,
because
the
the
problem
with
that
is
I'll
have
to
understand.
We
have
to
create
a
different
number
right,
so
we'll
have
because
boost
we'll
have
to
use
something
that
is
not
in
the
bootstrap
which
is
used
in
jenkins.I
o,
because
bootstrap
has
a
very
fixed
navbar
layout.
C
So
even
in
the
recent
pull
requests,
if
you
would
have
seen
I've
changed
like
in
the
bootstrap
now
bar
the
default
behavior
changes
slightly
to
suit
our
needs.
So
I
have
to
add.
A
C
And
I
just
had
perhaps
one
doubt
regarding
that
by
itself,
so
it
was
like
if
we
create
a
navbar
that
stays
stationary
on
the
page.
That
would
create
an
issue
in
the
mobile
view,
so
that
was
something
that
I
clearly
overlooked
by
writing
a
proposal.
So
I
forgot
about
the
mobile
view,
so
I
wanted
to
get
some
ideas
from
the
community
of
how
we
can
manage
that
that
kind
of
a
navbar
in
a
mobile
kind
of
view.
A
A
But
if
you
were
to
ask
the
question,
for
instance,
this
might
be
a
good
excuse
to
open
a
question
on
community.jenkins.io
and
say:
hey,
let's
talk
about.
Maybe
what
you
do
is
open
the
topic
as
jenkins,
dot,
io
navigation
bar
and
that
would
inspire
gavin
mogan,
who
maintains
the
plugin
site
plugins.jenkins.io
that
uses
the
same
navbar
to
to
give
his
inputs
and
gavin
has
very
good
insights
into
how
to
do
that.
Well,
so
so,
if
you're
willing
just
open
the
question
on
community.jenkins.io.
A
B
Wonderful,
and
did
you
have
anything
else
you
wanted
to
mention
or
talk
about
before
we
move
on
to
the
next
subject
or
where?
Where
are
you
at?
I
guess
that
doesn't
feel
my
side.
Thank
you.
Okay,
no
worries
thanks.
So
much
and
mark
do
you
want
to
go
ahead
and
discuss
the
localization
and
internationalization
internalization.
B
Oh,
that
was
right.
The
first
time
internationalization
with
grading.
A
A
To
do
internationalization
because
it
requires
code
changes,
and
so
this
is
a
good
opportunity
for
us
to
look
forward
to
hacktoberfest
or
to
other
contributing
events.
So
devops
world
contribute
contributions,
sequences
workshops,
those
kind
of
things
and
in
those
places
we'll
try
to
encourage
people
to
help
us
internationalize,
plug-ins
and
jenkins
core.
B
In
this
case,
there
are
going
to
be
some
changes,
since
the
lts
will
be
getting
released
in
a
few
weeks,
there
will
be
some
changes
that
need
to
happen
to
the
documentation
and
some
updates
in
regards
to
the
requirements
and
base
line
or
not
baseline,
but
the
java
version
that
is
being
used,
among
other
things,
for
the
backwards
are
expected
due
to
the
amount
of
change.
That's
gonna
be
happening,
and
one
of
the
bigger
changes,
that's
going
to
be
noted
in
a
blog
post.
B
That
I'm
going
to
be
writing
is
that
the
gif
and
png
images
in
jenkins
core
have
been
updated
to
svg
images,
and
the
idea
is
that
it's
going
to
create
a
better
user
experience.
The
images
will
be
higher
quality,
more
clear
and
will
just
overall
lead
to
a
better
view
of
jenkins.
In
that
regard,
there
are
some
hang-ups
with
the
plugins
that
we'll
need
to
address,
but
they'll
have
to
be
addressed
by
the
maintainers.
B
So
I'm
keeping
all
that
in
mind
when
creating
the
blog
post
and
making
sure
that
everything's
very
clear
and
and
descriptive
enough
that
we
should
be
able
to
get
everything
taken
care
of
it's
gonna,
be
it
may.
The
lts
will
may
appear
differently
and
from
the
weekly
to
some
degree
due
to
the
release
cycle.
But
all
the
information
should
still
be
100,
correct
and
accurate
and
valid
so,
and
then
we
also
are
looking
towards
the
future
and
the
requiring
java
11
epic,
that
we
have
so.
B
The
package,
documentation
and
user
documentation
will
need
to
be
updated,
which
are
the
two
tasks
that
I'm
currently
working
on
as
well.
I've
again
checked
in
with
basil,
checked
in
with
mark
and
collaborated
with
the
community
team
to
get
a
sense
of
what
needs
to
be
updated
and
what
we
need
to
be
on.
B
The
lookout
for
and
thankfully
everything's
been
very,
very
collaborative
symbiotic,
just
clear,
concise
whatever
you
want
to
put
it
that
I
know
what
to
do
and
take
care
of
and
who
to
ask
if
there
are
any
questions
along
the
way.
My
goal
is
to
have
a
lot
of
that
taken
care
of
by
the
end
of
next
week,
beginning
of
the
week
the
next
week,
but
it'll
come
in
time.
A
B
Oh
okay,
yeah
also
working
on
screenshot
updates
for
jenkins
itself,
so
I'm
working
on
that
to
get
the
screenshots
updated
and
be
reflective
of
what
jenkins
is
now
as
opposed
to
what
it
was
previously.
B
Yeah,
I
think
that's
all
for
me
on
that
stuff
mark.
If
you
have
any,
do
you
have
anything
to
add
or
want
to
forget
as
well.
B
Yep
great,
then,
if
you
want
to
go
ahead
and
talk
about
and
share
about
the
code
after
contribution-
and
I
know
it's
wrapping
up
shortly
or
soon
so.
A
Yeah
so
I'll
be
creating
a
blog
post
and
a
brief
video.
A
Screenshot
updates
is
really
timely
because
of
the
june
lts
that
will
change
the
ui
in
significant
ways:
inclusive
naming
we
made
good
progress
and
identified
a
number
of
places
where
we
still
need
to
do
more
checks
to
see
have
we
removed
as
much
of
the
inclusive
naming
issues
as
many
of
the
inclusive
naming
issues
as
we
can
and
then
pipeline
help
we
got
three
or
four
good
pull
requests
there
on
a
relatively
complicated
topic.
A
That's
it
for
me,
okay,
yeah
and
so
do
by
end
of
this
week.
Oh
there
is
a
I
take
it
back.
There
is
one
more
thing
on
saturday
saturday.
A
B
B
Thank
you,
of
course
great.
Well
that
covers
our
agenda
for
today,
thus
far
mark
van,
did
you
have
anything
else
that
you
wanted
to
bring
up
talk
about
mention
here
in
the
office
hours.
B
Yep,
I
guess
that's
it
from
my
side
as
well.
Thank
you.
Thank
you.
Thank
you.
So
much
appreciate
it
great.
So
in
that
case,
we'll
stop
recording.