►
From YouTube: 2020 07 06 Jenkins 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).
B
B
Well,
participant
in
Google
sees
no
dogs
or
it's
better,
to
focus
on
specific
item
and
provide
as
much
detail
as
possible,
because
I
noticed
that
several
applicants
right
now
have
very
wide
kind
of
area
and
most
of
the
comments,
as
far
as
I
understand,
are
related
to
trying
to
focus
the
applicants
on
specific
areas
where
they
will
contribute.
Yeah.
A
So,
at
least
for
me,
and
now
you
really
you're
you're
you're,
gravely
you
you've
entered
the
seriously
dangerous
zone
of
mark
weights,
opinion
and
I
apologize
for
putting
you
in
the
zone
of
mark
weights
opinion.
That's
that's
a
that's.
A
difficult
own
to
be
in
I
had
assembled
a
sort
of
a
checklist
of
ways
that
I
was
using
to
assess
proposals
and
that
checklist
I
had
assembled.
A
It
was
a
personal
checklist
for
me,
but
it
had
things
like
more
detail
was
better,
at
least
for
my
view
was
better
than
less
because
it
helps
me
understand
more
clearly
what
the
what
the
technical
writer
is
offering.
What
they're
proposing
the
the
breadth,
the
width
of
the
themes,
the
BRIT
was,
was
not
that's
not
one
I
would
know
how
to
guide
on
because,
for
example,
kubernetes
is
a
very
wide
topic,
and
yet
it's
also
a
very,
very
intensely
valuable
topic.
Therefore,
I
like
that
a
lot,
but
we
also
proposals
which
said
hey.
A
I
would
like
to
do.
Migration
of
plugin
documentation
from
wiki
to
github.
We've
got
about
a
thousand
plugins
still
that
need
that
migration.
That's
a
much
more
narrow
thing
and
yet
also
intensely
valuable.
So
so
here,
I'm
gonna,
I'm
gonna
waffle
or
be
a
little
bit
ambiguous
and
say
no
no
strong
opinion
whether
it
should
be
wide
or
narrow,
I've
seen
good
proposals
in
sort
of
both
both
areas
where
very
very
intensely
focused
or
much
broader,
brush
and
and
good.
A
B
A
A
A
Help
I,
don't
don't
be
shy
if
it
suggests
a
grammar
change
in
your
Google
Docs
session.
Consider
it
if
it
suggests
a
spelling
change.
No
none
of
us
should
be
intimidated
by
thinking.
We
need
perfect
English
language
because
we're
all
well
we're
all
working
towards
that
me
from
my
flawed
western
United
States
others
from
different
positions.
Don't
be
shy
about
that,
but
submitting
something
with
with
misspellings
is
awkward
and
an
awkwardness
that
Google
Docs
can
help.
You
avoid.
C
No,
just
you
know
the
standard
things
you
keep
your
syntax
simple.
Don't
try
to
do
really
really
complicated
phrases.
Thinking
it
makes
you
sound
better.
Most.
A
A
There
are
so
many
so
many
terrible
things
we
do
in
the
English
language,
with
with
phrasal
verbs
I,
don't
know
that
anybody
else
cares
as
much
about
it
as
I
do
about
this
one,
but
this
one
has
surprised
me
more
than
once,
as
I
try
to
speak
in
Italian,
sometimes
oh,
how
do
I
express
this
terrible
phrasal
verb
in
English?
It's
two
or
three
words
strung
together
to
make
a
single
verb.
A
A
A
A
If
you
have
no
Jenkins
experience,
this
is
pretty
much
expected
and
it's
not
a
problem.
That's
just
fine!
A
technical
writing.
Writer
without
Jenkins
experience
would
be
exactly
the
kind
of
person
we
would
expect
to
find
in
this,
and
that's
what
Google
season
of
Docs
is
trying
to
encourage.
Now
a
person
who
is
who
is
coming
to
Google
see
some
Doc's
with
no
technical
writing
experience.
That's
not
typical,
because
Google
season
of
Docs
has
focused
on
experienced
writers
who
are
interested
in
starting
their
work
in
open
source.
A
Okay,
then
we
had
a
question
on
stat
project
proposal
reviews.
All
reviews
are
now
complete.
We
completed
those
before
end
of
last
week.
If
you
have
a
proposal,
and
it
does
not
have
any
comment
from
me
on
it.
That
means
somehow
I
did
not
see
your
proposal
and
and
then
you
need
to
get
get
that
link
to
me
as
quickly
as
you
can
so
that
I
can
give
you
my
review
comments
as
soon
as
possible.
A
See
so
we
had
a
question
on
a
long-running
project
so-
and
this
was
a
good
one,
because
Google
season
of
Docs
has
two
concepts
on
a
standard
duration
project,
which
is
ten
weeks
middle
of
September
through
end
of
December
or
a
long-running
project
project
which
runs
six
months.
Long
running
projects
have
a
little
more
flexibility.
A
little
are
a
little
more
relaxed.
The
10-week
projects
have
are
do
a
little
more
intense
work
in
that
10
week
period
and
the
decision
on
whether
it
should
be
a
long-running
project
or
not.
A
It
is
yours
to
make
in
the
proposal.
That's
not
something
that
will
make
for
you.
If
you
say,
hey,
I
would
prefer
to
do
this
as
a
long-running
project,
say
that
in
their
proposal
and
include
it
in
your
timeline
for
the
proposal,
our
bias,
our
assumption
will
be.
If
your
timeline
tells
us,
it's
gonna,
be
a
10-week
project.
We
take
it.
It's
a
ten
week
project,
not
a
long-running
project.
A
Then
the
question
was:
are
there
any
shortcomings
for
long-running
projects
in
the
context
of
Google
season
of
Docs,
any
special
risks,
risks
or
benefits,
and
okay?
This
was.
These
were
just
advice
on
general
attributes
of
longer
running
projects.
In
any
context,
any
software
development
project
construction
project,
whatever
they
tend
to
miss
schedules
more.
They
tend
to
be
hard
to
predict,
and
but
they
can
also
deliver
more
value
because
there's
more
time
to
do
the
work
in
terms
of
jenkins
and
google
season
of
Docs,
we
didn't
see
any
practical
difference.
A
A
B
A
That's
a
good
question
and
that's
a
that's
a
that's.
A
good
question
leads
into
the
next
topic,
which
was
what,
if
things
change
during
the
project
itself,
right
and
I
would
expect
that
if,
if
the,
if
something
catastrophic
happened
in
the
in
the
for
the
selected
technical
and
technical
writer
that
they
said,
I
had
proposed
long
running,
I
need
to
change.
That
would
probably
require
that
we
negotiate
with
Google,
inform
them
and
form
the
organization
admins
that
we
were
doing
that
kind
of
structural
change
to
the
project.
A
I
would
I
would
guess
it's
possible
because
I
don't
think
that
there's
any
strong
attachment,
you
must
do
a
long-running
project.
If
you
said
you
were
going
to
do
a
long-running
project,
but
that
would
absolutely
invoke
the
organization
admins
we
would
have
to
have
their
involvement.
We
would
prefer
not
to
do
that.
But
if
difference
that
you
contracted
kovat
19
and
said,
I
have
to
take
two
weeks
off
to
to
get
to
get
healthy
again
and
that
will
change
completely
the
scope
of
my
project.
Then
we
would
probably
negotiate
and
start
those
discussions
with
Google.
C
D
C
A
Then
then
I
think
the
answer
is
so
if
we
can
fit
it
within
the
scope,
it
is
even
if
it's
by
reducing
work
that
we
we
accomplished.
We
just
handle
that
inside
the
project
team.
So
this
is
minor,
changes,
changes
to
scope
and
whatnot.
We
just
do
it
inside
the
project
team.
If
we're
doing
something
where
I
say:
hey
I
thought
I
could
do
this,
and
I
can
only
do
10%
of
that
that
we
at
least
notify
the
org
admins.
Because
then
the
org
admins
know
all
right.
We've
got
a
bigger
change
here.
A
As
far
as
Oleg
and
I
could
tell
the
only
time
we
have
to
formally
notify
Google
is
if
the.
If
the
writer
has
something
so
catastrophic
that
they
have
to
abandon
the
project,
and
then
we
would
inform
Google,
because
we
we
don't
want
to
mistreat
Google's
funding
of
these
these
50
people
that
are
doing
technical
writing
for
open-source
projects.
A
Okay
and
I
think:
oh
then
we
had
one
more
question,
which
was:
could
a
technical
writer
act
as
a
mentor
if
they
were
not
accepted?
As
a
writer
and
I
thought?
That
was
a
key
in
question.
A
very
interesting
question:
if
you
have
Jenkins
knowledge,
that's
the
key
attribute
for
a
mentor
for
a
mentor.
They
need
to
know
Jenkins.
If
you
have
Jenkins
knowledge,
then
that
would
be
great.
You
could
also
act
as
a
mentor.
A
Applicants
could
become
Mentors
if
so
long,
as
you
know,
Jenkins
that
would
that
would
be
quite
a
surprise,
but
I
guess
I
can
give
you
the
experience
we've
had
with
Google
Summer
of
Code.
We've
got
mentors
this
year,
who
were
students
last
year
and
who's.
It's
working
great
I,
love
that
what
our
mentors
are
doing
and
and
their
experience
as
on
the
other
side
of
the
equation
last
year,
has
helped
them
as
they
help
new
participants.
A
A
There
was
this
thing
and
in
that
mentor
meeting
we
reviewed
what
I
had
done
is
I
assembled
a
document
that
included
hyperlinks
to
every
one
of
the
proposals
and
that
document
document.
Would
it
help
you
if
I,
if
I
show
it
here,
we
intentionally
made
the
public
documents
so
that
people
could
see
some
of
the
things
that
that
we
had
that
I
had
thought
about.
A
So,
let's
see,
Google
sees
the
docs
now
I'm
gonna
stop
sharing
my
screen,
so
I
can
look
for
it
because
I
I
had
a
private
one
where
I
was
making
my
own
personal
notes
that
I'm
not
really
willing
to
share,
but
I've
got
a
public
copy
where
it's.
You
just
talked
about
the
kinds
of
things
that
I
was
doing
to
review.
So
hang
on
just
a
minute,
while
I
stop
my
screen
sharing,
find
that
document
and
I
will
bring
it
up.
Oh.
A
A
A
Okay,
there
it
is,
and
now
let's
click
through
the
link
to
be
sure
it
actually.
So
this
is
yeah
okay
good.
So
here
we
go
so
this
was
mentor
notes
and
it
captured
who
are
the
candidates,
and
so
we've
got
six
or
eight
different
candidates
from
various
locations,
links
to
their
proposals
and
I
put
them
in
order
in
which
I
had
received
them.
So
there
is
not
not
any
thing
that
should
be
inferred
by
the
order
of
the
links
list
there.
A
A
C
A
Sorry
about
that
I'm
talking
like
you,
could
read
what
I'm
writing
and
you
can't
okay.
So
these
are
mentor
notes
that
I
took
during
the
mentors
meeting
and
things
that
I
had
prepared
while
getting
ready
for
that
meeting.
It
includes
a
link
to
all
the
project
proposals
that
I've
seen
so
far.
So
let's
double
check
proc
are
yours
is
here
Vlad,
yours
is
here
yes,
so
and
then
the
evaluation
criteria.
These
were
things
that
that
I
had
thought
of
as
I
was
going
through
the
evaluation
process.
A
B
All
right
just
mark
in
general
or
in
case,
if
somebody
from
applicants
would
like
to
get
link
to
this
document,
which
you
prepared.
Is
there
any
simple
way
there.
A
A
There
we
go
yeah.
Thank
you
yeah
that
way
it's
it's
there,
it
really.
When
I
met
with
with
Oleg
and
with
Kristen,
it
was
specifically
noted
that
I'm
making
this
document
publicly
visible,
so
we
don't
put
anything
that's
sensitive
in
there.
We
don't
put
any
comments
about
specific
proposals.
Typically,
the
specific
proposal
comments
will
be
inside
the
Google
Doc
that
the
person
who's
making
the
submission
has
sent
us
the
link.
E
E
A
Think
be
sure
that
you've
reviewed
and
responded
to
resolved
comments
that
were
made
on
your
proposal.
That's
that
if
I
made
a
comment
on
a
proposal
and
it
was
ignored
that
probably
wouldn't
be
viewed
very
positively,
so
hope.
So
that's
that's
one
just
as
guidance,
then.
The
other
is
be
sure
that
you're
in
on
time
that
that
one
is
the
most
Awkward
of
any
to
have
to
tell
someone.
Oh
oops,
you
missed
the
deadline.
A
A
D
Yes,
I
do
intend.
What's
then,
I've
been
having
mixed
feelings
about
it,
and
I
just
wanted
to
take
my
time
to
learn
more
about
the
Jenkins
and
probably
opts
in
next
year,
for
when
I
have
a
much
better
just
times,
I,
don't
know
much
of
the
wood,
so
I
want
to
like
used
like
one
year
and
throw
at
me
do
anything.
I
could
not
come
back
and
say
kick
I'm
fully
grinded
with
what
Jake
is
the
boat
and
the
whole
foundational
stuff.