►
From YouTube: 2021 03 25 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
To
google
season
of
docs
office
hours,
this
is
25th
of
oct
of
25th
of
march
and
great
to
be
here.
Let's
see
so
I
had
one
two
or
three
topics
for
propose
for
the
agenda.
Declare
office
hours
are
the
docsig
meetings.
A
So
that's
a
topic
for
this.
So
first
was
talk
about
the
contribution
status.
To
be
sure
that
we're
okay
there
then
talk
about
office,
docs
office
hours
be
becoming
the
official
meetings
of
the
doc
special
interest
group
and
I'll
give
a
brief
overview.
Why
that
and
season
of
docs
I'd
like
to
do
a
final
review
of
the
project
plan
and
the
or
the
organization
proposal?
Let's
see,
let's
call
it
what
it
is.
It's
the
organization
proposal.
A
A
B
So
what
I
wanted
to
talk
about
still
falls
under
contribution,
so
I
think
it's
fine.
Maybe
when
we
start
this
question.
Okay,
great.
B
So
right
now
we
wrapped
up
applications
last
week
friday
and
we
had
over
180
applications
from
ladies
who
wanted
to
contribute
to
open
source,
and
we
kind
of
don't
have
enough
open
source
projects
currently
like.
We
just
have
three
open
source
projects
interested
jenkins,
deploy
hub
and
br5.
B
So
we
were
wondering
if
jenkins
could
take
in
more
mentees
so
that
at
least
we
can
be
able
to
take
in
more
updates,
because,
right
now
we
can
only
take
in
12,
considering
the
numbers
the
open
source
organization
submitted,
and
that's
like
okay,
no,
no,
it's
now
14
because
they
are
five
increases.
We
can
only
take
you
14
out
of
182
applications,
which
is
quite
low,
so
we
were
wondering
if
jenkins,
could
I'm
probably
taking
more
participants?
B
I
remember
you
mentioning
something
about
the
project's
idea
of
replacing
old
terminologies
in
documentation
and
things
like
that.
I
don't
know
if
we
have
other
ideas
that
we
could
that
this
participants
could
work
on,
would
really
really
appreciate,
then
also
for
the
pipeline
examples.
If
we
could
take
in
more
participants,
they're
going
to
be
working
on
the
same
project.
A
Very
good,
okay!
So,
let's
how
about
we
take
those
in
inverse
order?
Because
I
think
I
think
we
can
take
more
people
more
participants
on
the
pipeline
examples
topic,
especially
if
they're
willing
to
sort
of
work
together,
as
as
they
bump
into
challenges,
contact
each
other
and
and
yeah.
So
I
think
that
that
is
doable.
I
would
guess
we
can't
take
much
more
than
seven
or
eight,
so
we
currently
plan
for
three.
B
A
Could
increase
that
one
to
increase
to
let's
say
well,
let's
see
what
do
you
think?
What
if
we,
what
if
we
went
to
what
if
we
went
to
eight
and
said
eight
or
even
nine
and
said
okay,
we're
going
to
allow
that
we'll
find
a
way
to
because
the
the
the
the
project
idea
has
huge
potential
in
terms
of
of
what
people
can
do
with
it
and
the
number
of
places
that
need
changes.
A
So
if
I
remember
correctly,
the
list
of
top
10
plugins,
let's
see
where
is
my:
where
is
my
page
that
takes
us
to
the
sheet
the
pivot
table?
Here
we
go
this
one.
So,
let's,
let's
this
is
yeah:
okay,
good!
We
look
at
the
pivot
table
and
here
down
at
the
whoops
down
at
the
bottom
of
it,
there
were
10
plugins.
A
Or
30
of
them,
so
it
doesn't
seem
like
it
seems
like.
Yes,
this
is
a
reasonable
way
to
to
approach
it
and
there's
lots
of
work
to
be
done
here.
So
so,
if,
if
you
think
you've
got
contributors
willing
and
they
wouldn't
mind
helping
on
this
sort
of
larger
effort
to
make
this
better-
I
I
would
say
let's,
let's
let
me
let
me
propose
it
at
least
to
others-
suggesting
hey
we're
going
to
attempt
to
accept
nine
and
try
our
best
to
mentor
those
nine.
B
A
Let
me
propose
it
to
the
community
to
to
others,
and
I
will
attempt
to
enlist
more
more
mentors.
C
B
Okay,
so,
okay,
one
two,
three
four
five,
so
another
thing
I
wanted
to
ask
is
for
the
java
requirements:
it's
compulsory
that
the
person
has
to
have
like
some
experience
using
java
right.
A
Not
I
I
wouldn't
even
call
it
let's,
the
the
intent
really
is
just
that
they
have.
They
have
have
some
experience,
compiling
code
with
java
or
otherwise
and
are
willing
to
learn,
because
I
don't
think
you
need
particular
java
skills
to
do
these
tasks.
Many
of
them
are
more
about
explore
and
then,
during
during
development,
they
will
have
to
run
the
java
compiler
and
they'll
run
it
with
maven
following
the
instructions
here,
and
so
I
don't.
A
I
don't
think
you
should
set
a
precondition
good
if
they've
got
java,
if
they
don't
have
java,
but
they
have
some
experience
compiling
something
else,
either
using
yarn
to
do
to
do
javascript
based
compile
or
make,
or
you
know
those
kind
of
things
the
the
there's
nothing
special
about
java
here.
In
that
sense,.
B
Okay,
because
most
of
the
applicants
kind
of
like
have
more
javascript
experience,
front-end
and
things
like
that,
we
don't
have
as
much
java
applicant
though
we
have
some,
but
I'm
not
sure
if,
after
the
interview,
we
are
going
to
be
able
to
get
up
to
nine
or
ten
participants
that
have
experience
with
java
itself.
But
we
have
applicants
with
other
programming
languages,
majorly
javascript.
A
C
A
B
B
You
know
things
they
are
not
really
conversants
with
and
we
should
make
more
preference
for
those
who
seem
really
interested
and
enthusiastic,
enthusiastic.
B
Than
I
do,
okay
yeah
all
right,
that's
fine,
then
thank
you.
A
A
We
could
take
on
additional
people
if,
if
you've
got
people
who
could
assist
there,
the
skills
are
typically,
it's
java
java
compilation,
interacting
with
with
jenkins,
to
see
that
their
change
made
it
and
then
submitting
pull
requests
and
the
the
bigger
challenge
here
is
that
there
are
times
when
they
would
need
some
in
or
they
would
need
an
introduction
to
the
concepts
and
the
places
where
they
can
make
changes
and
where
they
cannot.
B
Okay,
okay,
so
at
the
end
of
the
day,
I
think
the
maximum
we
are
going
to
be
able
to
take
in
for
jenkins
is
still
going
to
be
around
nine
because
we
are
looking
at
20
because
you
know
sc
is
going
to
have
to
pay
each
of
them.
B
A
B
Now
left
for
jenkins
to
decide
if
you
want
all
of
them
to
work
on
the
pipeline
examples,
or
if
you
want
some
of
them
to
work
on
terminology
replacements,
others
to
work
on
pipeline
examples.
A
A
Target
projects-
and
that's
a
good
excuse
for
me
to
have
a
conversation
with
people.
I
know
I
have
a
number
of
people
who
say
we'd
like
to
do
terminology
replacement.
I
intentionally
chose
this
one
because
of
what
I
thought
was
a
good
mix
between
the
development
experience,
but
this
terminology
replacement
is
work.
We
very
much
want
to
do
so.
This
will
be
a
good.
It's
good
conversation
for
me
to
have
with
some
people
in
jenkins
project.
Thank
you.
A
A
If,
if
we
need
one
with
start
of
day,
so
our
intent
was
when,
when
you
tell
us
who
the
who
the
participants
are
we'll
ask
them
to
help
find
what
would
be
a
time
that
we
could
meet
with
them
to
do
a
to
once
a
week
to
have
good
mentoring
sessions
and
we've
got
two
teams
available,
so
one
could
meet
early
day
before
working
day
or
early
start
of
working
day
in
africa.
The
other
could
work
meet
after
working
day
and
and
so
the
idea
was,
when
you've
got
the
participants
assigned,
we
will.
B
Aha,
this
just
reminded
me
of
something
else
I
wanted
to
mention.
I
forgot
so
wanted
to
have
like
an
onboarding
call,
probably
next
week,
wednesday
or
thursday,
thursday's
1st
of
april.
So
I
don't
know
if
we're
going
to
have
it
wednesday
or
thursday
1st
of
april,
to
introduce
the
selected
participants
to
jenkins.
B
That's
the
mentors
so
would
like
a
suitable
time
for
you,
so
we
can
share
with
selective
and
selected
participants
at
the
end
of
the
day,
because,
right
now
we
are
already
in
the
process
of
I'm
already
scheduling
interviews.
So
after
the
interviews,
the
next
thing
will
be
to
select
participants
that
will
be
participating
in
the
bootcamp
and
introduce
them
to
the
mentors.
B
So
that
brings
me
to
the
question
I
want
to
ask
what
time
will
be
convenient
for
jenkins
to
have
the
onboarding
call
on
wednesday
or
thursday.
A
So
any
time
after
the
end
of
your
working
day,
there
would
be
would
be
fine,
our
kristen
whetstone
and
I
are
easily
reachable
at
this
time.
When
this
meeting
happens
and
the
the
other
mentors,
I
think,
are
also
reachable
even
the
ones
that
are
in
europe
and
meg
mcroberts.
We
can
ask
her
to
get
up
early
that
day
and,
if
she's
not
able
to
attend,
that's
still,
okay,
we
we
can
introduce
her
separately.
B
Okay,
so
could
you
share,
I
don't
know
when
I'm
sending
the
email,
I
don't
know
if
you
could
share
the
contact
details
for
all
the
mentors,
so
I
could
include
everyone
in
the
email
I'm
going
to
be
sending
out
to
the
mentors
and
also
the
invites
for
the
onboarding
call.
A
B
And
so
okay,
so
go
ahead.
B
Yeah,
so
I
think
why
I
brought
that
up
was
because
I
think
the
onboarding
call
would
be
a
good
avenue
to
discuss
meeting
times
and
agree
on
meeting
times
with
the
mentees
and
things
like
that.
A
B
Just
jacob
okay,
all
right!
Yes,
we're
going
to
shadows
separate
times
for
different
musicians,.
A
A
All
right,
so
the
next
one
is
just
a
a
piece
of
sort
of
business.
For
me,
it
is
that
we,
I
have
docs
the
doc
sig
meetings
happen
once
a
month,
however,
no
one
but
mark
attends,
and
for.
B
B
A
A
And
I'll
just
update
the
so
long
as
you
don't
object,
I'll
just
update
the
pages
on
jenkins.io
that
declare
that
this
is
how
we're
doing
it
and
that
way
we're
not
wasting
time
and
I
can
cancel
tomorrow's
meeting,
because
we've
got
lots
of
good
progress
in
the
doc
special
interest
group
without
having
to
do
a
separate
meeting.
And
then
the
one
thing
that
I
have
to
do
is
mark
periodically
collect
and
report
the
metrics.
A
A
B
Come
on
yeah,
so
I
wanted
to
ask
a
question
about
the
google
season
of
dogs.
I
saw
a
legs
mail
to
the
mailing
list
about
mentors
and
orga
admins,
so
I
wanted
to
ask
if
there
was
like
some
sort
of
requirements
or
something
like
that
to
be
a
mentor
before.
A
There
is
not
in
fact,
we've
had
we're.
Looking
I'm
looking
forward
this
year
to
having
mentors
who
were
previous
so
mentors
in
google
summer
of
code,
who
last
year
were
students
in
google
summer
of
code,
so
no
requirement
at
all
other
than
willing
to
be
a
mentor.
So,
for
instance,
if
you
are
interested
in
being
a
mentor
this
year
would
love
to
have
you.
A
B
A
So
zena
willing
to
be
a
mentor
for
google,
seasonal
docs,
good,
very
good,
excellent
that
that
that
actually
makes
a
nice
incentive
for
why
they
should
choose
us,
because
not
only
did
we
do
the
project
last
year,
but
we're
having
the
contributor
who
did
last
year's
help
us
with
this
year's.
That's
a
great
story!
Thank
you.
A
And
deepen
it
so
jenkins
on
kubernetes
continues
the
theme
of
this
and
and
what
they
asked
this
year
was
hey.
What
are
the
problems
you
have
and-
and
my
description
was
a
deploying
jenkins
on
kubernetes-
uses
lots
of
different
components
and
any
one
of
them
could
be
cause
a
problem
or
get
in
your
way.
So
jenkins
on
kubernetes
is
complicated
and
needs
better
documentation
about
all
sorts
of
aspects.
A
C
A
Part
time,
and
in
that
six
months,
part-time,
what
I've
proposed
is
several
phases.
One
is
a
preparation
phase
where
get
the
writer
confident
and
comfortable
with
kubernetes,
and
that's
something
we
didn't
do
with
you
and
I
think
it
might
have
might
have
helped
you.
If
we'd
admitted
we
were
going
to
spend
some
time
having
you
be
comfortable
with
kubernetes.
A
Okay,
well,
I
I'm
I'm
one
of
the
powerful
things
about
asking
your
review
is
I'm.
I
would
love
to
have
additional
insights
from
you
and
say:
oh
no,
that
wouldn't
have
that
won't
help,
or
this
might
help
so
docker
images
is
a
place.
We
know
we
have
a
need.
People
are
continuing
to
make
mistakes
and
how
they
define
their
docker
images,
and
so
we
need
documentation
that
guides
them
to
choose
well
how
they
create
the
docker
images
that
they'll
use
in
kubernetes
and-
and
these
two
topics
are
specific
to
that.
A
A
C
A
This
is
how
you
do
static
agents,
and
yet
you
still
are
running
in
a
kubernetes
cluster,
okay
and
then
the
last
phase
was
a
solution
page
now.
I've
got
actually
two
more
phases
after
that,
but
oleg
correctly
guided
and
said:
hey
more
than
four
phases
is
probably
too
much
to
fit
into
even
a
six-month
project.
B
B
I
think
this
is
good,
but
I
still
have
to
just
maybe
look
at
a
later
one
to
see,
but
for
now
I
think
this
is
fine.
Then
also,
I
think,
oleg's
idea
of
having
more
than
four
faces
is
also
correct.
Considering
you
know
you
might
have
some
blockers
or
issues
along
the
way
and
you
wouldn't
want
to
overwhelm.
B
Whoever
is
writing,
but
if
the
person
is
able
to
finish
the
four
phases
within
the
six
months
and
there's
still
time,
it's
okay
to
add
more
content,
but
for
now-
and
I
think
this
is
fine-
you
could
just
probably
have
it
like-
maybe
future
work
or
something
so
in
case,
if
you're
able
to
finish
everything,
then
you
could
start
working
on
that
and
if
not,
it
could
be
part
of
the
person's
project
report
or
something
that
this
is
what
I
was
able
to
do,
and
this
is
where
you
can
continue
from.
A
A
C
A
B
Exactly
yeah,
like
the
skeleton
working
on
the
scale,
I
say
how
do
I
start
working
on
the
install
dock
before
oleg
mentioned?
Wouldn't
it
be
great
to
have
like
a
skeleton
of
what
you
want
to
work
on?
First,
there's
something
like
this
that
you
just
did
now
right
before
starting
the
writing
process.
So
I
think
that
process
would
actually
help
this
to
go.
A
Great
okay,
so
so
you're,
okay
with
that
concept,
then
the
next
was,
let's
see
so
measuring
project
success
was
was,
I
think
we
we
can
look
at
the
google
page
results.
So
the
google
track
clicks
through
on
our
pages,
to
see
how
we're
doing
on
references
to
the
kubernetes
specific
pages.
Also,
I
thought
hey.
We
would
look
for
positive
feedback
in
our
feedback
spreadsheet
right
this
sheet,
that
collects
comments
from
people
that
they
give
to
us,
and
we
would
look
at
hey
our
issues,
we're
not
getting
a
bunch
of
new
issues
on
kubernetes
kubernetes,
documentation.
A
C
B
It
so
that's
a
big
question,
so
would
whoever
is
working
on
this
project
have
to
complete
all
the
writing
faces
like?
Is
it
compulsory.
A
It
is
not
so
I
would,
I
would
assume
if
we
get,
I
will
feel
great
if
we
get
through
phases,
one
and
two
that
will
already
be
a
dramatic
improvement.
So
for
me
I
am
not
envisioning
that
this
is.
We
must
complete
all
four
phases.
B
No,
you
weren't
so
because
I
was
thinking
like
definitely
in
measuring
project
sources.
B
We
would
need
to
kind
of,
like
include
the
number
of
writing
faces,
that
you
should
at
least
be
able
to
complete
within
six
months.
That
is
very,
very
reasonable,
say
within
all
whatever
issue
that
might
come
up
or
any
obstacles
at
least
you
should
be
able
to
complete,
say,
probably
faces
one
and
two.
A
B
A
C
A
A
Needs
minimum
to
complete
right,
because
if,
if
we
spent,
if
we
spent
google's
google's
funds
and
only
got
through
phase
one,
I
would
not
feel
good
about
it
that
just
that
for
me
that
that
that
that
would
not
be
success.
I
think
you've
got
a
good
point.
I
was
thinking
more
of
external
measurements,
but
I
think
you're
right
that
we
want,
if
we
can't
say
yes,
we
did
this
and
we
did
this.
Then
I'm
not
ready
to
say
that
it
was
a.
B
C
A
C
C
A
A
C
A
Give
up
to
nine
to
the
jenkins
project,
and
my
initial
proposal
was:
let's
put
all
nine
of
those
people
as
many
of
up
to
that
nine,
as
they
can
on
the
pipeline
examples
idea,
because
of
the
number
of
different
plugins
that
will
all
benefit
from
these
pipeline
examples.
So
it's
actually
independent
work
that
each
of
the
each
of
the
participants
can
do
in
their
own
pla
pipe
own
own
plug-in.
We
just
have
to
split
them
out
and
be
sure
that
they
understand
okay,
you're
working
on
this
when
you're
working
on
this
one.
C
There's
only
like
the
declarative
example
and
not
a
scripted
example,
one
thing
that
I
personally
ran
into
with
work
recently
then,
and
I
never
really
could
couldn't
really
find
a
good
answer
for
it
and
it'd
be
a
good
place
to
investigate
is.
Can
I
use
a
library
from
another
library,
maybe
some
examples
of
that
I'll?
Do
some
exploration
and
just
kind
of
doing
some
tightening
best,
recommend
or
best
practice
stuff
too,
so
not
only
updating
the
actual
steps,
but
just
in
general,
covering
our
the
documentation
for
the
pipeline.
A
So
in
terms
of
the
number,
are
you
okay
with
us,
adding
additional
participants
on
this
same
project?
So
thinking
that
I
think
I've
found?
Oleg
has
agreed
that
he's
willing
to
help
as
needed
and
angelique
yard
has
also
offered
her
help.
She's,
not
sure
she
can
be
available
as
often
as
needed,
but
she's
offered
some
help,
and
I
think
we
could
recruit
additional
to
support
us.
So
my
sense
was
taking
more
people
on
on
the
same
project
where
they
can
help
each
other
when,
when
the
mentors
aren't
available
may
be
a
real
positive.
C
A
That's
more
about
documentation,
whereas
this
pipeline
examples
exercise
they're
really
going
to
be
in
their
compiling
code.
They'll
be
modifying.
You
know
changing,
admittedly,
the
changes
they're
making
are
in
html
files,
but
still
it's
it's
about
a
code
experience,
whereas
this
one
is
more
about
a
documentation,
experience
right.
C
C
Right
and
yeah,
it
almost
feels
like
some
of
the
best
documentation
and
stuff
is
be
actually
using
the
snippet
generator.
So
it's
like,
if
there's
a
way
that
we
could
kind
of
try
to
make
this
closer
for
make.
A
Right
well
and-
and
we've
actually
got
a
a
step
in
this
in
this
tasks-
document
that
talks
about
encouraging
them
to
use
the
snippet
generator
writing
into
every
one
of
these
plug-in
documents.
A
All
right,
so
that
was
that
one
then,
oh,
the
other
change
was
I'm
I'm
proposing
that
we're
going
to
declare
that
this
meeting
and
the
earlier
meeting
on
mondays
are
officially
doc
sig
meetings
rather
than
just
office
hours,
because
I
get
we
get
much
better
participation
here
than
we
do
at
the
doc
sig
meetings.
So
I'm
going
to
cancel
the
doc
sig
meetings
that
happen
once
a
week
or
once
a
month,
and
instead
these
twice
a
week
meetings
are
going
to
be
it
and
no
objections
from
you.
I
hope.
C
A
Just
one
item
and
I've
put
it
here
and
that
is
reporting
metrics
okay,
I
I
report
how
well
we're
doing
at
handling
of
pull
requests,
for
instance,
and
how
quickly
do
we
resolve
them
and
how
many
contributors,
those
kind
of
things
so
and
those
are
good
things
to
gather.
But
I
can
report
those
here
in
three
minutes
just
as
readily
as
do
it
in
the
in
the
other
meeting.
C
A
All
right,
so
I
think
thanks
thanks
zenob
for
your
patience.
Thanks
for
your
insights
on
google
season
of
docs,
one
last
topic:
pending
pull
requests,
so
oleg
had
asked
hey:
should
we
should
we
merge
the
pull
request
as
a
here?
Let's
go
read
his
phrasing.
I
like
it.
Should
we
merge
it
as
a
work
in
progress.
Just
admit
that
mark's
not
been
very
successful
at
making
this
happen.
A
A
Okay,
great,
then,
then,
I
will
go
ahead
with
that
as
well.
Sorry
that
I've
been
such
a
block
on
this
one,
thanks
kristen
for
your
patience
and
being
willing
to
offer.
A
C
Yeah
sure,
and
then
you
know
maybe
someone.
This
is
a
good
another
good
example.
It
says
work
in
progress.
Is
there
an
easy
way?
We
can
highlight,
like
oh,
make,
suggestions
to
this
page,
because
I
know
that
there's
that
option,
but
it's
maybe
I
don't
know
if
the
disclaimer
has
a
an
extra
highlight
for
a
if
you
have
any
extra
questions
or.
C
C
A
A
All
right
zenob,
thank
you
very
much
and
thanks
again
for
presenting
yesterday
we'll
talk
again
in
a
week.
Thank
you.
Thank
you.
Awesome.