►
From YouTube: 2020 06 08 Jenkins Docs Office Hours
Description
Jenkins documentation office hours from June 8, 2020. Topics included a review of the Google Season of Docs site and discussion of patterns for creating good project plans for submission by the July 9, 2020 due date.
A
Thanks
everyone,
this
is
Jenkins
Doc's
office
hours
remind
you
that
we
adhere
to
the
Jenkins
Code
of
Conduct,
so
be
nice.
If
someone
were
to
be
disruptive
in
the
meeting,
our
ultimate
solution
is
just
end.
The
meeting,
so
don't
be
shy
about
it.
If,
if
you
feel
like
something's
going
to
miss,
we
will
just
stop
the
meeting
if
we
were
to
be
Zoom
bombed,
etc.
Whatever
that
may
be,
we
will
happily
stop
this
meeting
and
not
feel
at
all
shy
about
it.
A
A
A
There
so
here's
the
google
season
of
Doc's
2020
timeline.
This
is
the
second
year
for
season
of
Docs.
This
is
the
first
year
that
the
Jenkins
project
has
been
accepted.
The
season
of
Docs
we've
had
multiple
experiences
with
Summer
of
Code
and
we're
using
those
experiences
to
help
guide
us.
We
are
in
a
beginning.
Tomorrow
we
enter
the
Technical
Writer
application
period
that
period
lasts
for
a
month.
That's
the
deadline
for
technical
writer
applications
is
July,
9
2020,
so
in
this
month
this
is
where
technical
writers.
A
Well,
let's
look
and
see
what
their
guidelines
are
rather
than
me
me
telling
you,
let's
read
what
they
have
to
say
so
technical
writer
exploration
phase
we've
completed
this
is
where
today
is
the
last
day
of
it.
You
look
at
the
the
organizations
that
are
available
to
you,
discuss,
project
ideas
and
you'll
find
several
project
ideas
in
the
Jenkins
projects
page.
So,
let's
get
that
just
to
be
sure,
we've
got
it
ready
and
Jenkins
is
here.
Oh.
A
Silly
silly
bad
link,
it
is
here
the
Jenkins
project.
This
should
link
to
the
actual.
Now
they
didn't
link
to
the
project
idea.
Shame
on
them!
Okay!
Well,
we'll
look
at
them
this
week.
The
project
ideas
are
here
in
the
season
of
Docs
section
on
the
Jenkins
website
and
we
went
through
these
last
week.
A
A
So
now
tomorrow
we
enter
the
Technical
Writer
application
phase,
and
in
this
phase
you
apply
to
be
part
of
google
season
of
Docs
and
then
the
program
administrators
at
Google
forward
the
details
from
your
application
to
the
organization
Jenkins,
the
organization
administrators.
So
that's
Oleg,
Menasha
and
I
believe
Marquis
Jackson,
Jackson
Talia
act
as
the
room
as
the
beginning
of
the
reviewers,
and
then
they
with
the
mentors
like
me
and
Kristin
whetstone,
select
the
projects
that
should
be
mentored.
A
B
Mark,
if,
if
I
can
just
ask
one
question
about
the
process,
it
looks
like
we
can
submit
this
application
starting
tomorrow,
but
in
case,
if
I,
for
instance,
would
prefer
to
discuss
this
application
with
a
mentor
before
submitting.
Does
it
make
sense
and
environment
yeah
my
understanding
that
you
kind
of
a
mentor,
a
good
mentor
or,
as
you
mentioned,
so,
would
it
possible
to
discuss
possible
applications
with
you
before
submitting
them
yeah.
A
Not
only
is
it
not
only
is
that
a
good
idea,
we
highly
recommend
it.
One
of
the
things
we
learned
from
google
Summer
of
Code
was
that
submitters,
who
submitted
things
without
having
discussed
them
with
with
the
mentors
and
with
project
involves
people
ended
up
submitting
significantly
weaker
proposals
than
if
they
had
taken
the
time
to
submit
those
things
to
the
to
the
public
mailing
list
for
discussion
and
for
review,
so
that
a
typical
pattern
was
created.
A
Googledoc
shared
publicly
share
a
link
to
that
doc.
Allow
comments
on
it
and
do
that
relatively
early,
say
one
week
into
this
application
phase,
so
that
there
are
two
or
three
weeks
of
time
that
you
can
use
to
encourage
other
people
to
review
the
proposal
to
make
suggestions
to
recommend
alternatives
or
paths.
So
it's
it's
actually
quite
important
that
what
we
found
with
Google's
Google
season,
google
Summer
of
Code,
was
that
when
students
in
that
project,
now
they
it
was
a
different
thing
than
the
season
of
Docs.
A
But
the
pattern
was
that
when
they
submitted
something
that
they
had
not
discussed
with
anyone,
it
was
inevitably
filled
with
the
kinds
of
mistakes
that
good
open-source
reviewers
would
have
detected
and
helped
them
prevent,
and
it
just
it
was.
It
was
awkward
for
them
and
most
of
those,
in
fact,
I
think
this.
Last
year,
all
of
them
were
rejected.
There
were
enough
proposals
that
had
been
reviewed
and
discussed
that
none
of
none
of
the
just
parachute
in
kind
of
proposals
were
accepted.
Did
that
address
your
question?
Glad?
Yes,
absolutely
so.
A
A
Have
to
go
looking
for
that,
but
it
needs
some.
It
needs
some
some
information.
Oh
all,
right!
That's
part
of
your
your
if
you
got
it
yes,
so
you
submit
that
form
from
there
yeah
inside
that
form,
you'll
provide
name,
display,
name,
email
address,
so
that
they
can
contact
you
and
then
information
about
your
experience.
So
the
crucial
thing
here
is
you
describe.
This
is
basically
a
curriculum
vitae,
write
a
CV,
it's
a
chance
to
describe
hey
I've
done
this
form
of
technical
writing.
A
A
This
proposal,
can
you
can
submit
up
to
three
on
your
single
application
form,
and
the
guidelines
here
are
are
very
good
for
you
to
you
to
review
and
be
sure
that
you
comply
with
these
we've.
We
expected
and
it's
it's
very
sensible-
that
you
review
this
in
detail
and
assure
you're
complying
with
all
of
the
all
of
the
details
of
what's
required.
So
the
organization
name
Jenkins
right.
That's
us
the
name
of
your
proposed
writing
project,
so
it
might
be.
A
A
Then
the
detailed
description
of
the
kinds
of
things
that
you're
proposing
to
do-
and
here
you
really
will
need
multiple
paragraphs
and
all
of
these
project.
All
of
those
project
ideas
are
assumed
to
be
multi-month
efforts,
they're
assumed
to
be
from
10
to
20
hours
a
week
for
the
period
from
I
think
it
was.
Let's
see,
we've
got
to
check
the
timeline.
The
the
actual
time
was.
A
It
the
projects
are
announced
in
August
and
documentation
of
development
begins
in
September
and
then
concludes
at
the
end
or
in
in
December.
So
we've
got
September,
October,
November
and
December,
so
a
three
month
period
where
you'd
be
working
for
10
to
20
hours
a
week
on
these.
These
projects
that
you
proposed.
C
A
C
A
Okay,
so
other
other
alternatives.
So
there
is
a
choice
between
a
standard
length
or
a
long-running
project,
and
if
you
have
a
project
that
requires
a
longer
time,
we
need
to
discuss
that
with
the
Jenkins
project.
So
if
you
think
Oh
I'm
going
to
need
six
months
or
more,
that's
that
needs
discussion
with
the
project.
It
is
assumed
that
the
project
you're
proposing
will
be
a
three-month
project
unless
you
say
differently-
and
we
have
a
discussion
about
why
it
means
to
be
different
than
that.
C
A
That's
correct
so
accepting
the
season
of
Docs
stipend
here
they
they
will
pay
some
apportion
us
a
small
stipend
to
and
to
the
technical
writers
that
are
accepted,
and
if
you
read
here
my
recollection,
it
has.
It
has
a
relatively
complex
formula
that
decides
how
it
is.
It's
called
purchasing
power
parity,
they
start
with
six
thousand
US
dollars
and
then
adjust
it
based
on
country,
purchasing
power,
parity
and
I
confess
I
have
not
looked
at
what
that
means.
I
cannot
help
you
with
the
arithmetic
of
that
for
your
particular
country,
or
what
that
would
mean.
A
I'll
rely
on
you
to
read
through
that
and
decide
how
that
works.
Now
in
terms
of
the
payment
of
the
stipend,
it
happens
at
the
end
of
documentation,
development
and
it's
calculated
based
on
where
you're
at,
like
based
on
your
geographic
location.
Oh
here
we
go
and
they've
got
examples.
So
if
we
took
if
we
took
Raziel,
3600
or
Nigeria
I
believe
was
the
other
one,
and
it's
at.
A
A
C
A
I
think
I
think
their
expectation
is
that
it's
10
to
20
hours
a
week
across
the
full
three
month
period.
I
know
that
with
google
Summer
of
Code,
they
clearly
set
the
expectation
to
the
students
that
they
should
plan
to
work
full-time
now
this
is
seasonal.
Docs
is
different,
is
known
that
that
the
season
of
Docs
contributors
are
probably
already
working
in
a
company.
This
is
a
additional
time
they're
taking
so
they
set
the
expected
hours
lower
ten
to
twenty,
instead
of
the
assumption
of
forty
plus
from
the
students
in
Summer
of
Code.
A
So
this
one
is
known
to
be
part
time,
but
still
expected
that
it
is
a
significant
time
commitment
during
the
fixed
timeline
and
the
timeline
is
rigorously
fixed.
They
don't
they
don't
allow
any
variation
in
the
timeline
at
all.
It's
they
will
live
to
this
timeline.
Precisely
if
you
as
an
example,
if
you
submit
just
a
few
minutes
late
on
this
July
9,
they
will
they
will
reject
your
application
completely.
A
B
Wanted
to
ask
this
timeline,
which
google
provides
specifies
three
months
project
and
it
looks
like.
Applicants
are
allowed
to
discuss
at
least
six
months
longer
projects,
especially
regarding
documentation.
When
we
write
in
tutorials
or
solutions,
it
can
be
on
different
platforms,
using
different
technologies,
and,
and
so
so
endless
so
about
the
time,
and
when
we
should
discuss
this
length
of
the
project
during.
A
A
Ok,
my
example
might
be
this
one
where,
if
we,
if
I
look
at
this
one
right
here,
Jenkins
on
kubernetes
I,
think
that
one
is
huge
sure
I
think
there's
a
lot
hiding
in
that
one
and
an
awful
lot
of
a
very
complicated,
fascinating
and
interesting
system,
and
therefore
it
might
easily
be
justified
to
say
this
is
a
six
month
project,
the
other
one
that
is
is
high
potential
for
a
long
time.
This
one
might
be.
If
you
don't
choose,
not
read
enough
this
one,
the
reorg
might
need
more
time.
A
C
B
I
guess
previous
meetings
office
hours,
we
have
this
Google
Doc,
where
we
posted
our
discussions.
What
our
puzzles
and
just
during
the
previous
discussion,
I
shared
my
ideas,
it's
about
implementing
doc
resolution.
But
of
course
this
is
also
huge,
because
there
are
many
many
solutions
which
we
can
just
provide
for
docker
images.
But
it's
about
shifting
from
old
previous
blue
ocean
docker
image
to
latest
Jenkins,
Jenkins
docker
image
and.
D
B
Drought
hit
Orioles
work
and
I
just
started
working
on
this
documentation
based
on
issues
provided
by
Mark,
for
instance,
and
also
administration
pages,
something
like
I
mean
there
are
many
many
things
to
do,
but
specifically
docker
would
be
interesting
for
me
because
I
guess
everybody
is
using
this.
Everybody
needs
this
and
in
case
it
will
succeed.
There
may
be
like
natural
evolution
to
kubernetes,
because
it's
kind
of.
D
A
A
A
Where
is
that
I
was
looking
for
a
forum
and
I
don't
see
it
so
I
think
it
is
I'll
have
to
double
check
with
our
org
admins
Jonathan
I.
Think,
okay,
it
is
it
is
it
might.
Your
application
must
include
the
content
that
they
listed
here
so
name
etc.
But
okay
doesn't
look
like
they've,
given
us
a
specific
Google
Docs
template
to
to
use
as
that
as
a
base
for
it.
D
A
Fact
that
that
was
our
at
least
with
Summer
of
Code.
That
was
our
experience
as
the
best
way
to
do.
It
is,
if
you
just
use
a
Google
Doc,
make
it
publicly
readable
and
allow
public
comments
and
then
share
the
link
to
the
Google
Doc
in
the
documentation
mailing
list
and
invite
feedback
there,
because
then,
then,
mentors
like
me
can
come
in
or
org
admins
like
Oleg
can
come
in
can
make
comments
on
the
proposal.
Saying
hey,
we
need
this
or
what
about
this
or
here's?
This
challenge?
Okay,
yes,.
D
A
Absolutely
one
of
the
one
of
the
behaviors
we
saw
in
a
particular
proposal
for
season
for
Summer
of
Code
was
blatant
plagiarism
and
we
found
that
very
irritating
all
right.
So
so
it's
great
that
we
gather
ideas
from
one
another.
We
should
not,
however,
wholesale
steal
content
from
each
other
and
put
it
in
as
the
world.
Okay.
D
A
Good,
so
so
I
would
think
that
what
you'd
want
to
do
there
is
in
your
project
proposal.
You
would
identify,
probably
for
your
benefit
and
certainly
for
mine
as
a
mentor,
a
series
of
milestones,
hey
I'd,
like
to
do
this
phase,
and
then
this
phase,
and
then
this
phase
in
this
phase,
and
they
would
each
be
interestingly,
deliverable
portions
of
the
work
so
that
we
could
see.
Oh
yes,
progress
is
being
made
I'm
I'm,
much
less
open
to
a
suggestion,
I'll
work
for
three
months
and
show
you
what
I've
got.
A
We
would
much
rather
have
two
or
three
days
or
a
week's
worth
of
work
and
a
pull
request
to
improve
something
another
set
of
changes
and
a
pull
request
to
improve
something.
So
your
project
plan
should
identify
logical
milestones
that
make
sense
to
you.
That's
one
of
the
ways
of
showing
the
org
admins
that
you've
thought
carefully
about
whether
this
meet
okay.
D
A
Delays
happen,
life
happens
and,
and
then
the
project
more
more
crucially
many
times
what
happens
is
a
project
plan
is
in
general
for
us
in
its
of
code
we've
seen
this
a
project
plan
is
assembled,
it's
the
best
plan
we
could
assemble
at
that
time
and,
while
executing
the
project,
we
learned
important
information
that
we
didn't
know
previously.
We
changed
the
plan,
and
that
was
perfectly
okay,
so
this
this
plan
is
not
immutable.
It
is
not
never
changing
it's.
A
D
E
A
B
A
Might
end
and
they
allow
up
to
three
not
more
than
three
but
yours.
Your
single
proposal
could
propose
up
to
three
projects
and,
you
might
say,
I
propose
this
documentation
improvement
this
this
improvement
project
and
this
kubernetes
project
and
those
those
two
things
would
be
valid
things
to
include
in
your
project
proposal.
A
A
E
A
So
the
the
crucial
things
then
are
in
we're
in
the
phase
we
enter
tomorrow.
It's
this
project
plan
that
you're
preparing
and
your
involvement
with
community
members,
like
me
with
mentors
like
me,
is
vital
at
this
point,
so
you
should
probably
start
a
Google
Doc
fill
it
in
following
this
outline
and
relatively
quickly
here,
share
share
your
that
first
draft
with
the
mailing
list
and
the
get
'red
chat
channel
so
that
people
can
give
you
feedback
on
that
proposal.
D
A
So
that's
a
good
question.
That's
an
excellent
question.
So
I
think
what
your
question
was
is
may
I
reference,
my
recent
contributions,
either
from
the
hackfest
or
elsewhere
in
my
application
and
yeah
absolutely
should
that
that
is.
That
is
a
compelling
value
for
us
and
it
shows
your
interest
in
the
project
and
gives
gives
mentors
and
org
admins
material
that
they
can
a
value.
So
they
can
say.
Oh
yes,
here
is
this.
That
was
written.
Look
it
had
this
characteristic
and
here
was
their
engagement.
A
So
absolutely
you
should
mention
your
involvement
now,
if
you
don't
have
that
enrollment,
that's
okay
too,
but
it's!
This
is
a
good
time
to
be
involved
and
if
you
already
have
examples
of
your
involvement
show
them.
You
know
this.
Those
examples
could
also
be
from
your
professional
work.
You
might
say:
oh
look
here
is
this
product
that
I
assisted
with
the
creation
of
its
documentation?
B
Just
in
continuation
of
Jonathon
question
mark
I
just
wanted
to
clarify
when
we
submit
this
links
to
our
previous
documentation,
which
we
did,
for
instance,
within
Jenkins
project,
should
we
address
only
our
pull
requests
or
we
can
address
also
issues
reported
by
us
and,
as
I
understand
we're
not
limited
to
the
time
frame
of
hackfest.
We
can
like
address
something
which
was
done
before
head
west
as
well.
You.
A
Are
correct:
you
are
not
limited
to
the
time
frame
of
hackfest
you're,
not
limited
to
only
pull
requests.
You
could
district
list
issues,
you
could
list
things
you've
created
in
the
Jenkins
JIRA
system,
either
issues
or
epics
any
of
those
are
perfectly
valid.
You
could
you
could
if
you
wish
link
to
mailing
list
posts?
Those
are
all
good
ways
to
show
active
contribution
and
to
show
that
you've
given
serious
thought
to
how
you
can
help
the
project.
B
And
my
another
question:
if
you
don't
mind
well,
they're
asking
us
to
provide
links
to
the
Queen
tation
which
we
need,
but
we're
luckier,
that
Jenkins
project
has
public
the
condition
publicly
available,
but
many
companies
they
have
behind
the
firewall
kind
of
private
clouds
and
so
on
doesn't
make
sense
to
say
well
we're
clear
in
this
this
years
on
this
product.
But
documentation
is
kind
of
well
not
not
available,
because
it
is
hidden
inside
behind.
A
The
firewall
risk-
absolutely
if,
if
you
don't
miss
in
first
note,
is
that
but
a
link
to
your
work
says
samples
is
optional
all
right,
so
it's
not
mandatory,
but
if
you
can
provide
it,
that's
great
if
there
is
something
publicly
accessible,
if
it's
not
publicly
accessible,
but
you
can
provide
a
sample.
That's
great
too,
if
all
you
can
do
is
describe
the
thing
on
which
you
worked.
A
That's
already
something
Meg,
for
instance,
one
of
the
the
charm
things
for
me
about
Meg
is
that
she's
worked
for
some
very
large
companies
in
that
have
a
very,
very
large
component
in
the
UNIX
space,
as
in
she
worked
for
Bell
Labs
for
a
while,
didn't
you
Meg,
and
so
that
was
interesting
right.
It's
like
oh,
okay,
somebody
who's
worked
in
that
environment
has
a
different
experience
than
somebody.
Maybe
who's
worked
in
describing
mobile
phone
applications
or
who's
worked
in
describing
infrastructure
implementations.
A
All
of
those
things
are
interesting
to
us,
and
even
if,
for
instance,
you
can't
give
us
a
piece
of
your
work.
Oh,
you
may
say:
I
worked
in
a
defense
industry
for
let's
see
for
Jonathan
I
worked
in
a
Brazilian
defense
industry.
I
can't
share
the
work
with
you
at
all,
but
I
can
tell
you
that
that's
where
I
worked
and
that
helps
us
understand
your
background.
A
A
So,
in
terms
of
the
the
project
plan
that
you
submit
these,
these
paragraphs
are
crucial
and
and
read
them
carefully
work
through
them.
One
of
the
things
that
may
be
missed
here
is
that
just
how
valuable
it
is
for
you
to
get
get
feedback
from
others
on
your
ideas
and
keep
your
discussions
in
the
public
forums.
So
there's
a
there's,
a
temptation
sometimes
to
reach
out
to
one
another
individually,
point-to-point
and
and
a
reminder
is
that
it's
an
open
source
project
and
we
value
that
openness
intensely.
A
Therefore,
we
we
prefer
our
conversations
be
done
in
public
now,
sometimes
you
may
have
something
which
absolutely
has
to
be
done
privately.
Okay,
that's
fine,
but
usually
you
should
encourage
the
mentors
and,
on
your
own,
have
those
conversations
in
public
wherever
possible.
As
an
example,
now
old
entourage
in
our
wazoo
Sewell,
a
so
Larry
and
and
I
had
a
great
session
in
the
Gitter
channel
for
Jenkins
CI
sty
stocks
doing
a
session
a
working
session
on
interacting
with
git
and
managing
branches,
etc.
A
A
So,
let's
see
other
things
that
I
should
probably
flag
to
you,
the
the
crucial
thing
so
after
acceptance
were
a
month
or
where,
if
we
look
at
the
timelines,
we've
got
a
reminder.
So
July
9
one
month
from
tomorrow
will
is
the
deadline.
Then
the
project,
the
Jenkins
project,
will
have
a
period
of
three
weeks
to
do
evaluations
to
review
it
to
internal.
You
are
welcome
to
encourage
to
continue
contributing
to
the
Jenkins
project.
During
that
period,
then
July
31
project
selections
will
be
notified
to
Google.
A
Google
review
will
give
themselves
two
weeks
to
review
them,
and
then
they
will
announce.
We
are
very
careful
that
we
will
not
pre
announce
anything
we
communicate
from
the
Jenkins
project
to
Google
here,
but
not
to
you.
We
won't
tell
you,
oh
we
like
this
and
didn't
like
that.
Those
kind
of
feedback
liked
and
didn't
like
needs
to
have
happened
prior
to
this
July
9
end
of
the
proposal
period.
D
A
Yes,
at
least
our
experience
previously
was
that
we
give
that
kind
of
feedback
already
here
in
this
period
between
June
9
and
July
9,
and
if,
if
that,
if
that
feedback
already
was
not
enough,
we
are
certainly
also
open
to
give
additional
feedback
as
an
example
with
Summer
of
Code
I
had
one
submission
that
came
in
very,
very
near
the
deadline
and
as
such
had
not
had
much
much
review
from
from
people
from
the
mentors
and
so
I,
provided
that
submitter
review
feedback
after
the
fact.
So,
yes,
I
think
we
will
do
that
as
well.
C
Because
well,
if
I
submit
a
plan,
I
mean
I,
think
the
odds
are
good.
That
there's
going
to
be
many
good
plans
that
do
not
quote
unquote,
win
the
contest
and
that.
But
that's
what
I'd
like
to
know
that
the
community
thinks
this
would
be
worth
it
to
do.
What?
If
you
wanted
to
go
ahead
and
do
it
right
also.
C
A
Yes,
and
in
fact
that's
that's
a
very
good
example
of
a
case
where
the
whether
or
not
a
plan
is
accepted
to
Google
season
of
dogs,
it
can
be
independent
of
whether
or
not
you
choose
to
continue
working
on
it.
You
might
say:
I
am
so
interested
in
this
I've
learned
enough
during
this
there's
June
9
to
Deline
ein
exploration
period,
the
tech
right
or
application
period
that
I
think
I'm
just
gonna
go
ahead
and
do
it
anyway,
and-
and
that
is
great,
because
we
will
likely
still
mentor
you
right.
A
D
A
A
B
Meantime,
maybe
is
it
possible
to
ask
a
question
also
about
the
process,
for
instance
in
case,
if
let's
say
somebody
will
be
choosing
to
write
in
a
tutorial,
for
instance,
many
of
those
which
are
acquired
is
assumption
that
technical
writer
will
implement
those
three
tutorials
tried.
Will
try
out
this
specific
solution,
for
instance
before
writing
about
them,
or
he
or
she
should
rely
on
pre-existing
implementations,
for
instance,
or
either
way,
is
fine.
What
is
my
function?
He.
A
Oh,
this
only
works
in
one
place.
No
they're
for
tutorials
are
interestingly
challenging
for
the
from
the
infrastructure
perspective
and
the
tutorials
we
have
right
now
are
very
carefully
crafted
that
they
will
in
fact
run
on
Mac,
OS,
Linux
and
windows,
and
but
it
takes
an
impressive
amount
of
work
to
get
them
to
that
point.
So
there's
an
awful
lot
of
behind
the
scenes
that
oh,
that's
such
an
easy
command.
A
A
That
I
need
and
that's
a
question
that
needs
to
be
discussed
during
this
application
period,
because
it
may
be
that
we
can
get
funding
or
some
infrastructure
support
from
the
Jenkins
project
to
help
you
if,
for
example,
you're
proposing
to
do
the
kubernetes
project
you're
going
to
have
to
have
access
to
kubernetes,
and
if
you
don't
already
have
access
to
kubernetes
through
an
employer,
that's
probably
an
expense
that
you
should
be
discussing
with
the
mentors
during
this
application
period.
How
would
I
get
access
to
a
kubernetes
cluster?
B
Well,
there
is
like
intonations
obvious
with
kubernetes:
it
is
kind
of
open
source,
also
project,
so
we
can
buy
ourselves.
Technic
writer
can
install
Jenkins
on
the
top
of
benares.
It
depends
who
is
hosting,
but
I
understand
that
we
need
to
discuss
all
of
this
stuff
before
actually
submitting
discuss
infrastructure.
Basically,
all
right.
A
And-
and
that's
that's
it's
a
good
thing.
We
we
don't
want.
We
would
not
expect
you
to
spend
personal
funds
on
running
a
kubernetes
cluster.
That's
great
if
you've
got
that,
but
I
would
be
truly
astonished.
That's
kubernetes
is
typically
cloud
hosted
and
usually
hosted
on
one
of
the
major
cloud
vendors
and
therefore
not
free
and
never
going
to
be
free
in
the
sense
of
execution
costs.
A
B
A
A
C
C
You
say
so
what
are
the
practicalities
here
if
I'm
so
I'm
working
on
this
for
three
months,
but
every
two
to
four
days,
I'm
submitting
a
PR,
so
we
get
the
PR
where
it's
good
that
gets
merged
into
my
private
four
core?
Does
that
get
merged
to
master
or
does
it
depend
I
mean
because
there's
some
there's
some
things
in
documentation
where
it's
time
to
merge
it,
but
you
don't
necessarily
want
to
publish
it
to
the
world
I.
Don't.
A
A
The
final
thing
that
that
will
look
like
ultimately
you'll
see
plenty
of
pages
on
the
Jenkins
site
that
have
a
disclaimer
at
the
top,
which
says
this
page
is
still
under
development,
and
that
would
be
just
fine,
that's
no
problem,
so
the
preference
is
that
you
submit
PRS
and
they
are
reviewed
and
you
get
guidance
on
them
very
quickly,
so
that
if
something
is
amiss,
if
something
is
a
mistake
or
wrong,
we
can
correct
it
speedily
so
that
you
don't
spend
a
lot
of
time
on
something
that
isn't
isn't
what
was
ultimately
desired.
I.
A
A
B
Maybe
some
silly
question
in
case:
if
one
of
us
will
be
dedicated
to
work
on
google
seasonal
dogs
project,
is
it
like
possible
or
advisable
to
work
on
general
issues
happening
in
jenkins
project
like
fixing
some
issues
with
documentation
or
any
other
stuff
and
plugins,
and
so
on?
Or
it's
not
best
practice
to
split
between
this
then.
A
B
A
I,
don't
have
a
I,
don't
have
a
concept
on
that
yet
I
don't
know.
I
can
tell
you
what
my
limited
experiences
weren't
been
with
google
Summer
of
Code,
where
the
student
that
is
working
on
the
get
plug-in
project
that
I'm
mentoring
right
now.
He
has
been
involved
in
other
things,
and
it's
been
very
positive
for
that
student
by
being
involved
in
those
other
things,
because
the
student
gained
knowledge
that
they
would
not
have
obtained
otherwise,
now
should-should
would
I
want
that
student
to
derail
completely
their
project
to
work
on
other
things.
A
No,
that
would
be
a
bad,
a
bad
trade-off,
but
the
comp,
the
contribution
from
that
student
had
actually
been
very
helpful.
I
was
I
was
actually
a
little
proud.
The
student
submitted
something
that
made
it
all
the
way
into
a
Jenkins
core
release.
Recently
the
student
made
a
fix
and
it
got
all
the
way
to
Jenkins
core
is
like
that:
that's
cool,
so
so
the
and
and
the
student
learned
a
bunch
by
doing
that.
A
Did
that
address
your
question?
Yes,
all
right,
so
a
the
recording
of
this
will
be
available.
I'll
post
it
separately
after
we've,
concluded
the
session
and
thanks
everybody
for
taking
time
we'll
meet
again
in
a
week.
Oh
oh
I
should
I
should
remind
that's
right.
Olegmon
Asha
has
offered
a
poll
of
meeting
times
for
other
office
hours.
A
What
he
suggested
is
office
hours
during
the
morning,
European
time
so
Zeinab,
for
instance.
For
you,
it
may
be
much
easier
to
join
a
session
with
Oleg
on
the
morning
hours
European
time,
based
on
where
you're
at
geographically.
That
way,
it's
not
so
delayed
in
the
evening
for
you
you're,
welcome
to
join
one
or
both
or
none
of
those
office
hours.
But
Oleg
has
sent
the
poll
out
to
the
docks
the
docks,
git
er
channel,
all
right.
Okay,
thanks
everybody
and
I'll
post
things.