►
From YouTube: 2021 02 22 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
Okay,
so
jenkins,
contributor
summit,
jenkins,
2.271,
changelog
and
277.1
change,
log
an
upgrade
guide
and
then
she
code,
africa,
sponsorship
status
report.
B
A
Well,
I
yeah,
and
I
I'm
not
gonna
claim
one
way
or
the
other.
I
had
specifically
poked
them
in
slack
and
then
asked
the
question
and
then
was
willing
to
poke
again
and
had
the
additional
benefit
that
alyssa
was
also
helping
with
the
poking.
A
So
so
multiple
pokes,
maybe
the
magic
solution
and
and
really
nothing
to
report.
Officially
so,
but
but
conversations
look
promising
for
at
least
one
corporate
sponsor.
A
And
that's
that's
a
good
sign,
yes
and
then
mark
will
is
willing
to
coordinate
project
proposals
for
the
jenkins
project.
A
So
so
any
other
topics
from
you,
contributor,
summit,
changelog
and
upgrade
guide
and
she
code
africa
looks
good
to
me.
Okay.
So
then,
let's
talk
contributor
summit,
the
crucial
thing
that
I
need
vlad
silverman
can't
be
with
us
today.
He's
he's
out
unavailable
away
from
his
desk.
A
So
the
question
I
had
for
you
is:
I
saw
that
you
hadn't,
registered
for
contributor
summit
yet
and
vlad
hasn't
registered.
I
preemptively
assumed
you
were
both
registered
anyway
and
put
you
on
the
list,
but
now
the
question
is:
when
would
it
work
best
for
the
for
you
meg
for
us
to
do
a
contributor
summit
documentation
track
for
one
to
two
hours,
either
tuesday
afternoon
or
wednesday
afternoon?
Your
time.
B
A
Yeah
and-
and
my
expectation
was
that,
if
you
didn't
register
because
you
and
I
had
talked
about
it
so
much-
it
didn't
matter
that
you
didn't
register,
no
requirement
that
you
need
to
register
no
expectation
that
you
would
register.
I
was
using
the
registration
just
as
a
way
to
pull
people
which
areas
were
interesting
to
them.
I
know
yours
documentation
and
which
times
were
available
for
them,
and
I
know
yours
in
general-
it's
afternoons
in
in
u.s
time
zone.
You
know
in
california
time
zone
afternoons.
A
B
A
It'll
be
recorded,
okay,
absolutely
and
then
the
last
30
minutes
is
a
coordinating
session
where
we
find
the
times
when
the
tracks
will
work
best
for
track
participants,
and
since
you-
and
I
are
already
doing
that-
there's
no
reason
for
you
to
be
up
at
that
early
hour
of
the
morning
to
attend
to
attend
that
session.
So
so
the
intent
here
is:
let's,
let's
not
even
assume
that
you
will
attend
that
session
or
the
thursday
session,
because
the
thursday
session
will
just
be
a
a
summary
of
the
results
of
all
the
tracks.
A
So
then,
these
afternoon
sessions,
what
happens
in
those
those
are
the
working
sessions
where
we
talk
about
where
we're
going,
where
we
review,
for
instance,
we'll
do
review
exercises
around
the
the
framework
or
the
outlines
that
I'm
going
to
assemble.
Hopefully
later
tonight,
we'll
do
discussions
about
hey.
What
would
it
mean
to
have
search
site
search,
enabled
on
the
jenkins
documentation
site?
What
would
it
mean
to
have
an
improved
site,
search
on
the
plugin
site
and
those
kind
of
questions
we'll
discuss
with
gavin,
mogan
and
others?
A
B
A
A
Okay,
so
it's
so
tuesday
afternoon
after
three
after
3
p.m,
works
for
you
is
the
same
for
wednesday,
wednesday
afternoon
after.
A
A
All
right,
great
so
and
I'll
I've
still
got
to
check
with
vlad
to
see
what
his
calendar
is
like.
I
know,
and
I
don't
know
jonathan's
either
jonathan,
I
think
strongly
prefers
this
time
slot
because
of
his
work
schedule.
This
is
just
after
his
working
day
has
ended
in
brazil.
Okay,
so
my
bias
is
towards
choosing
this
time
slot
again,
because
I'd
like
jonathan's
input
he's
one
of
the
key
players
in
the
site,
search
questions
and
right,
hey.
What
are
what
are
the
things
that
work
well
and
what
don't?
A
B
Okay,
actually,
three
o'clock:
california,
is
like
7
a.m.
Isn't
it
in
australia
and.
B
A
Oh
good
yeah,
so
canon
can
welcome
asia-pacific
asia
contributors
at
that
time.
I'm
also
welcome.
I'm
also
willing
to
meet
during
a
time
that
works
very
well
for
eight
contributors
from
asia
if
they
come.
So
that's
that's
one
where
I've
got
several
that
have
expressed
interest
from
asia,
specifically
from
india
in
documentation,
and
I
want
to
send
them
a
meeting,
send
them
a
question.
Saying:
hey
you've
expressed
interest
in
this.
A
Some
of
them
didn't
actually,
I
should
show
well,
I
can't
show
you
just
a
minute.
Let
me
turn
off.
Let's
see,
am
I
screen
sharing.
I
am
right,
yes,
yes,
okay,
so
I'm
going
to
briefly
pause,
my
sharing,
bring
something
up
and
show
you
this
really.
No.
I
guess
I
can't
because
we're
recording,
but
I've
got
what
I've
got
is
the
people
who
have
registered
have
provided
so
the
the
people
that
have
registered
have
provided
their
preferred
times.
A
Times
use
that
to
suggest
times
even
before
we
start
the
meeting
tomorrow,
because
you
can
imagine
3
p.m.
Utc
is
terribly
early
for
the
u.s
west
coast
and
almost
unbearably
a
bad
time
for
asia,
pacific
right
for
japan,
it's
that's
just
or
beijing,
china.
That's
like
the
dark
middle
of
their
night.
B
A
And-
and
so
so
many
of
them
who
might
have
been
contribute
who
might
have
been
interested,
may
not
be
available
or
willing
to
attend
that
open
session,
but
they
might
be
willing
to
suggest
hey
if
you
could
meet
at
this
time,
tuesday
evening
or
wednesday
evening
or
wednesday
morning,
whatever
they
might
be,
it
might
be
willing
to
contribute.
So
so
I'm
gonna
offer
ask
that
question
later
today
to
them
in
an
email.
A
A
A
Current
outline
review
process,
that's
the
one
we
had
discussed
over
the
course
of
the
last
several
weeks.
Hey.
We
need
a
let's
talk
about
the
chapters
in
the
jenkins
handbook
and
which
content
goes
into
which
places
in
those
chapters
and
which
content
doesn't
fit
in
a
chapter.
So
I
think
we've
got
lots
of
places
where
good
dialogue
between
us
could
really
help.
B
A
Well,
and-
and
I
I
just
had
experience
with-
was
who
was
it
janet,
janet
gregory?
I
think
it
was
who
introduced
me
to
a
tool
that
that
I
may
try
as
an
experiment
in
the
docs.
I
think
it's
called
jamboard
dot,
google
yeah,
so
it's
this
post,
that's
post-its
on
a
big
whiteboard
digitally,
and
we
may
do
something
like
this
in
the
docs
in
these
docs
sessions,
just
as
a
way
to
try
to
get
ideas,
collected,
etc.
A
B
A
We
have
we
have
two
or
three
different
categories
of
people
involved
right,
so
jonathan,
let's
take
let's
take
going
from
east
to
west,
so
zenob
is
has
been
predominantly
a
writer,
but
has
has
a
little
bit
of
tooling
experience,
but
predominantly
writing
for
us
and
then
kristen
whetstone
lots
of
tooling
experience.
She
wrote
the
thing
that
the
original
implementation
of
the
thing
that
extracts
pipeline
documentation
and
makes
it
publishable
on
the
jenkins.io
site,
so
lots
of
coding
and
tooling
experience.
A
A
Therefore,
probably
first-time
contributors
fabulous
well.
If,
if
they
attend
great
many
times,
you
get
a
first-time
contributor
who
registers
and
they
don't
even
bother
to
attend.
I'm
I'm
okay
with
jonathan
venesh
jonathan
morris
as
well
is
a
is
clearly
a
tooling
expert.
Who's
also
done
some
writing,
but
his
his
real
forte
is
clearly
tooling
he's
very,
very
good
at
it.
B
A
So
so
we've
got
a
mix
and
and
we'll
try
to
shape
the
conversations
to
fit.
Whichever
group
is
in
that
particular
session.
So
if,
as
I
suspect
in
the
european
africa
session,
we
get
jonathan
and
zenob,
we
will
likely
likely
spend
about
half
the
time
on
tooling
and
half
the
time
on
content
and
structure,
because.
B
A
And
then
the
the
the
u.s
west
coast,
one,
I
think,
will
be
dominated
by
writing
portion
unless
gavin
chooses
to
join
and
if
gavin
chooses
to
join,
then
we'll
talk
pretty
deeply
about
what
search
means
and
what
he's
learned
from
the
plug-in
site
where
he
implemented
search
using
a
commercial
search
engine.
B
A
A
Very
good,
okay,
so
I
think
we
covered
that
the
the
crucial
parts
are
there.
I've
got
actually.
Maybe
I
should
show
my
slides.
Let's
talk
about
the
docs
slides
because
I've
I
created
some
slides
for
the
contributor
summit
and
I
would
love
to
have
feedback
on
them
if
you
want
to,
if
we
can
just
go
two
or
three
minutes
through
them,
it's
it's
like
like
one
or
two
slides
and
see
if
I
missed
something,
I'm
good
for.
A
Here
it
is
okay,
so
here
is
the
slide
deck
and
we'll
have
welcome
and
intro.
Why
we're
doing
this?
What's
the
schedule,
and
then
we
skip
rapidly
down
to
jenkins
releases
jenkins
user
experience
platform,
sig
documentation,
okay,
so
here's
my
piece:
oh,
I
need
to
put
artwork
on
this
just
a
minute:
okay,
which
which
jenkins
artwork
do
we
want
to
choose.
A
I
I
think
I
like
the
the
one
with
the
rapier
the
sword
here,
because
that's
my
preferred
one
so
far,
because
we
don't
have
one
with
a
book.
B
A
I've
used
this
one
before
so
I'm
going
to
go
ahead
and
just
grab
that
one
for
now,
okay,
and
if
we
get
a
better
one,
we
can
always
insert
a
better
one
later
right
because
we
did
have.
We
did
have
one
from
somebody
in
in
the
in
asia.
If
I
remember
right
where
they
had
a
a
like
a
scholar,
kind
of
thing,
it
wasn't
a
book.
A
Okay,
so
there
we
go
all
right.
So
what
I
said
was
hey.
We've
had
made
great
progress
on
migrating
documentation
to
github
over
half
the
plugins
have
migrated,
which
is
actually
quite
amazing,
with
as
many
plugins
as
there
are,
and
in
the
varying
states
that
they
are.
We
completed
google
season
of
docs,
and
that
means
we've
got
dramatically
better
kubernetes
kubernetes
documentation.
Thanks
to
that
work
from
xenoblade
car.
A
A
Yeah
good
kubernetes
jenkins
on
kubernetes.
A
A
That's
that's
fair,
good
point,
okay
and
then
on
the
what's
next
in
documentation,
I
said:
hey,
we
want
improved
site
search
on
the
plugin
site.
We
want
site
search
for
the
jenkins,
docs
site,
change,
log,
automation,
and
I
don't
know
how
to
that.
One
makes
me
a
little
nervous
because
that
one
really
needs
oleg
and
I'm
not
sure,
he's
available,
but
I'm
going
to
put
it
there,
just
in
case
okay,
okay
inventory,
the
current
documentation
and
proposed
document
proposed
destinations.
A
So
this
is
the
this
is
the
work
that
we've
described
earlier
and
improving
the
contributor
onboarding
experience
that
one
is
is
definitely
a
need.
We've
seen
with
zenob
that
the
documentation
development
has
to
have
a
for
for
most
convenience.
You
need
a
linux
computer
and
that's
not
something.
Every
contributor
has.
B
A
B
A
B
How
would
you
rank
the
current
contributor
onboarding
experience
if
one
is
running
mac
or
linux?
Is
that
good?
It
is
yeah?
Okay.
This
is
a
windows
issue.
B
A
A
B
A
B
A
These
things,
it
will
be
a
push
yeah,
some.
A
A
A
A
Those
four
need
need
some
alert
and
discussion
and
framing
them
in
your
user
terms,
and
the
release
candidate
is
scheduled
to
be
available
wednesday.
A
A
24Th
with
final
delivery
release
scheduled
for
march
10.,.
A
Now,
there's
also
additional
benefit
for
others
with
this
that,
for
instance,
corporate
products
oftentimes
can
base
their
change
logs
on
the
jenkins
whoops
on
the
jenkins,
open
source
change
log,
and
so
I
have
people
who
are
asking
from
a
business
perspective
hey.
When
do
we
have
the
change
log
available
so
further
motivation
to
get
this
thing
done,
I
would
love
to
have
reviews
of
it,
but
the
reviews
are
somewhat
complicated
because
it's
done
using
a
it's.
A
data
driven
change
log
that
has
a
very
specific
style
guide.
B
A
Yes,
so
if
there
well,
it
depends
on
what
you
mean
so,
for
instance,
if
there's
something
that
is
changing
a
core
component,
then
then
it's
expected
that
they
will
submit
proposed
changes
to
the
documentation
to
support
that
that
change
in
the
core
component,
jesse
glick,
for
instance,
submitted
as
part
of
the
the
x
stream
and
the
the
let's
see
it
was
x
stream
and
it
was
extreme
and
oh
scg
as
part
of
that
he
submitted
two
different
blog
posts
or
a
blog
post.
That
then
I
supported
with
another
one.
A
So
this
was
his
blog
post
on
hey.
Here.
Are
these
major
changes
coming?
This
is
what
it
means,
and
this
is
where
you
go
for
more
information.
You
go
to
either
this
page
or
you
go
to
this
page
and
then,
if
you'd
like
to
see,
if
there
are
open
issues,
you
click
these
links
to
see.
Okay,
any
issues
open,
none
for
that
one.
B
Looked
do
we
have
screenshots
all
over
the
place,
the
the
change
in
the
doing
the
tiling
for
the
managed
jenkins
page
and
all
that
sort
of
thing
do
we
have
screenshots
that
have
been
impacted
by
that
all
over
and
everything.
A
We
do
and
those
have
not
been
updated.
So,
for
example,
we
did
zenob
just
submitted
the
updated
jenkins
installer
for
windows
screenshots,
and
they
are
correct
and
complete
nicely
done,
but,
for
example,
the
any
pipeline
screenshots
or
let's
take
a
different
one,
pipeline's,
probably
a
poor
choice,
because
it's
actually
not
largely
not
affected
by
by
this
2.271
7.1.
But
if
we
were
to
look
instead
at
system
administration,
if
there
are
any
screenshots
here,
you
would
expect
them
to
be
now
be
out
of
date
because
because
things
have
changed,
let's
see
what
we've
got
here.
A
B
A
A
A
So
there's
one
and
now
you
see
okay
notice,
there's
a
message
about
deprecation
right.
There
is
information
here
about
when
it
was
released.
That
is
no
long.
That
is
not
in
this.
This
screenshot
version
number.
So,
yes,
we
definitely
need
an
update
to
our
to
our
screenshots
and
no,
we
haven't
done
it.
B
A
A
A
A
B
A
B
A
This
thing
has
been
switched
so
that
all
of
its
screenshots
are
now
no.
Are
they
all?
Oh
here
we
go.
I
changed
this
screenshot
as
an
example.
This
is
the
new
ui,
and
yet
there
are
old
screenshots
in
here
that
I
still
need
to
take
again
so
so.
This
is
a
good
example
of
needs,
more
work
to
update
the
screenshots
to
reflect
the
new
ui,
because
the
new
ui
is
much
more
attractive
in
terms
of
its
layout
than
this
layout
is
great.
B
A
Unless
somebody
does
it
that,
maybe
we
ought
to
put
that
as
as
a
topic,
because
really
screenshot
updates,
updates
based
on
the
2.27.1
user
interface
and
that
that
might
be
an
excellent
candidate
for
a
she
code.
Africa
project
project
to
to
get
better
screenshots
to
get
current.
A
Right
well,
and-
and
this
is
this-
is
more
of
a
documentation
effort
than
it
is
a
plug-in
code
development
effort
right.
So
we
could
also
do
pipeline
pipeline
examples
submitted
to
to
plug
in
source
code
as
as
a
as
a
another
candidate,
and
that
would
be
more
development
focused,
but
with
an
html
spin
on
it.
B
A
Okay,
good!
That's
that's
a
good
one!
Thank
you
for
helping
helping
discover
that
all
right,
so,
let's
see
anything
else
to
discuss
on
2.277.1.