►
From YouTube: 2020 07 03 Jenkins Docs Office Hours
Description
Jenkins documentation office hours
A
Our
agenda
navigate
it
welcome
everyone,
it's
Doc's
office
hours
and
we
are
being
recorded.
Please
remember:
we
have
the
Jenkins
community
code
of
conduct
I'm
going
to
go
ahead
and
share
my
screen
and
let's
take
a
look
at
the
agenda
and
put
things
on
to
it
that
we
need
okay,
so
all
I
had
put
for
today
was
question
and
answer.
A
A
So,
let's,
let's
walk
through
the
questions
and
be
sure
that
we've
got
a
combined
understanding.
So
what
let's
see
we
I
confirmed
with
Oleg
and
he
I
talked
in
more
depth
about
community
bridge
and
community
bridge.
Very
much
is
on
his
mind
and
he's
actively
seeking
funding
to
do
in
addition
to
google
season
of
Docs
a
community
bridge
project.
Now
one
of
his
concerns
is
that
we've
got
to
be
sure
we
have
enough
mentors
in
the
in
the
Jenkins
community
to
ready
to
support
a
community
bridge
writer.
A
B
A
A
Would
and
that
would
be
exceptional
we've.
We've
realized
that
the
most
precious
thing
that
we
can
receive
in
terms
of
people's
contribution
is
their
time
and
mentoring.
Google
season
of
Docs
we're
expecting
will
take
roughly
the
same
kind
of
effort
that
is
required
for
google
Summer
of
Code
and
that's
from
four
to
eight
hours
per
week,
and
so
we
want
to
be
very
clear
to
the
Mentors.
This
is
what
you're
agreeing
to
do
for
a
period
of
ten
weeks.
A
B
A
Here's,
my
friends
all
right
so
then
reminder
on
the
timeline.
July
9,
so
we're
six
days
away
from
the
application
deadline
recommended
to
submit
on
July
8,
so
that
you're
absolutely
sure
it
made
it
on
time.
Then,
from
July
9
to
July
31.
The
Jenkins
organization
will
review
the
final
proposals
and
select
them
and
then
they'll
send
their
selection
on
to
Google.
So
at
July
31
the
selections
will
not
be
announced.
A
They
go
to
google,
google
reviews
the
proposals
and
then
August
16
Google
will
announce
the
selected
projects
and
Oleg
agreed
with
my
answer
from
last
from
Monday,
can
an
inexperienced
technical
writer
be
part
of
google
season
of
Docs
an
inexperienced,
as
in
doe
Jenkins
experience?
Absolutely
not
a
problem
in
experienced
as
in
no
technical
writing
experience?
Yes,
but
it's
a
little
more
challenging
so
and
he
refined
my
answer
said:
it's
focused
on
technical
writers
who
are
interested
in
working
on
open
source.
A
Okay,
so
in
terms
of
status
report
on
proposal
reviews
proposal,
first
proposal
reviews
are
done
so
done
as
of
July,
I,
think
I,
finished,
July,
2
and
so
I
know.
I'll
visit
visit
the
comments
again
to
see
if
see
how
they're
going,
but
if
you
have,
if
you
have
submitted
a
proposal
and
haven't
received
feedback
from
me,
I
left
at
least
some
comment
on
every
single
proposal.
So
if
you
have
a
proposal
and
I
didn't
do
feedback,
that
means
I'm
not
aware
of
your
proposal.
I
need
to
see
it
any
questions
there,
Jonathan
yeah.
B
A
A
All
right
so
then
the
question
on
long-running
project
so
long-running
project.
If,
after
the
discussion
with
Oleg,
he
confirmed
that
long-running
project
is
a
decision
from
the
person
proposing
the
project
they
are
saying,
hey
I
would
like
to
do
this
work
over
the
course
of
about
six
months
instead
of
ten
weeks.
It's
also
asking
for
the
mentoring
organization
to
assign
mentors
for
the
entire
six
months.
So
yes,
it's
both,
and
if
the
project
proposal
does
not
say
it
is
a
long-running
project,
we
will
assume
it
is
not
based
on
what
we
read
in
the
timeline.
A
A
And
this
one
application
should
specify
if
it
wants
to
be
long-running,
so
the
question
was:
can
a
project
proposal
specify
alternatives?
Yes,
you
could
say:
hey.
Here's
it
described
as
a
as
a
regular
project
or
here
as
it
described
as
a
long-running
I,
would
think
the
projects
are
quite
different,
regular
versus
long-running
and
to
use
your
your
sprint
metaphor,
Jonathan
the
way
Oleg
described
it.
A
He
was
assuming
that
a
regular
length
progress
will
be
a
regular
length
project
will
be
more
intense
than
a
long-running
project
that
it's
it's
a
higher
intensity
of
effort
for
that
10-week
period
than
the
comparable
effort
spread
across
six
months.
Yeah,
okay
and
then
the
question
was
we
had
one
about
hey
what
if
things
change
like
environments
or
we
really
learn
something
and
realize
hey
this
is
this
needs
a
completely
different
way
of
approaching
it?
A
Oleg
and
I
talked
through
several
different
scenarios,
and
he
first
immediately
acknowledged
adaptation
is
allowed
and
accepted
even
I'd,
say
embraced
right,
it's
it's
welcomed.
Who
do
we
inform
of
changes,
and
that
depends
on
the
type
of
change,
so
minor
changes
stay
right
inside
the
project
team?
No
one
needs
to
be
notified
outside
the
project
team,
so
the
mentors
and
the
writer
significant
changes
should
be
notified
to
the
organization
admin.
So
in
this
case,
I
think
it's
Oleg
and
marki.
A
So
that
they
can
help
if
they
need
to
that's
so,
for
example,
if
we
change
dramatically
the
delivery
deliverables,
what
we're
going
to
create
or
when
we'll
have
them
available
or
if
we're
adjusting
mentors.
So
if
we
realize
hey,
one
of
the
mentors
is
unable
to
help
and
we
bring
another
one
on
or
we
add
two
more.
We
tell
the
org
admins
because
they
need
to
record
some
things
at
Google
about
who
our
mentors
are.
B
A
I
would
I
would
significantly
reduce
that
that
estimate
a
number
of
pages
to
do.
It
would
be
wonder
if
we
could
wonderful
if
we
could
do
that.
But
typically
there
is
a
I.
Would
guess
it's
on
average,
one
or
two
days
in
total
of
effort
for
a
writer
to
make
the
transition
of
plug-in
documentation
from
from
outside
of
the
code
to
inside
the
code,
and
that's
yeah,
it's
not
that
that's
a
contiguous
one
or
two
days
it's
rather
the
initial
extract
extract,
submit
a
preliminary
pull
request.
Watch
the
build
oh
whoops.
B
The
I
QPR's
in
our
experience
month
and
each
migration
takes
me
and
16
hours,
16
hours
and
because
I
need
to
press
the
left,
take
screen
shorts
and
a
writing
liquid
turns
gray.
We
can't
change
it.
So
how
do
you
think
about
I
change
this
number
four
to
fifty
and
if
you
can
achieve
more,
there's
no
problem.
It's.
A
A
So
the
we
had
we
had
a,
we
did
have
an.
We
did.
Have
the
mentor
meeting
I
had
a
conversation
with
me
and
Oleg
and
Kristin
wetstone
this
morning
went
well.
We
discussed
various
proposals,
we
looked
at.
Okay.
Are
there
other
questions?
We
need
to
ask
and
felt
like.
We
were
comfortable
understanding
things
so
that
that
was
a
positive.
We've
got
the
right
people
now
on
your
question,
Jonathan.
They
were
delighted
to
answer
the
question:
could
a
Technical
Writer
act
as
a
mentor?
A
A
A
B
A
B
A
So
then,
so
it's
it
would
have
typically
been
jo
n,
a
ta
n
yeah,
very
good.
Okay,
that's
I
thought!
Oh,
maybe
there's
a
secret
because
in
in
the
Italian,
an
H
after
a
after
a
let's
see
an
H
H
has
a
very
specific
to
the
letter.
C
will
harden
the
C,
whereas
a
vowel
after
the
letter
C
will
soften
it.
So
yeah.
B
A
B
A
Thank
you
for
joining
I'm
sure
it's
daunting.
We
love
having
international
contributors.
It's
amazing,
particularly
you
from
Brazil.
It
makes
me
so
proud.
Yes,
we've
got
someone
from
Brazil
who's,
helping
our
project.
That
is.
That
is
a
great
hang.
So
we
appreciate
you
very
much
so
thank
you
all
right,
we'll
we.
We
will
have
office
hours
again
on
Monday
and
if
we
see
you
then
great
thanks
very
much.
Okay,.