►
From YouTube: 2021 07 26 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
All
right
so
top
of
the
top
item.
A
B
A
Yeah
and
thanks
very
much
again
dearaj
for
your
help
with
jenkins
contributor
summit
in
june.
That
was
really
exceptional.
You
were
wonderful,
you
made
it.
You
made
it
much
more
credible
when
the
newcomer
contributor
segment
had
two
brand
new
contributors
who
were
saying
yeah.
This
is
how
you
become
a
contributor.
A
Great
yeah
that
that
what
you'd
shown
us
earlier
was
great
as
well,
so
we'll
we'll
do
that
all
right!
So
topics
that
I
had
on
my
list:
technical
writing
conventions.
I've
got
a
question
that
meg
really
needs
a
consultation
with
you,
because
me
talking
about
these
kind
of
topics
is
really
dangerous.
I
tend
to
say
things
that
are
just
wrong
and
then
the
jumbotron
update
upcoming
events
hacktoberfest.
A
Let's
see
dhiraj,
there
was
one,
I
think
that
you
and
I
should
probably
discuss
which
is
weekly
change:
log
automation,
our
weekly
change,
log,
yeah,
weekly
change,
log
and
weekly
change.
Log
automation-
I
haven't
done
my
my
review
yet,
but
I
think
it's
worth
a
discussion
for
your
sense
of
it,
etc.
There
was
a
concern
raised
by
daniel
and
I
wanted
to
hear
your
opinion
what
you
think.
A
D
I'm
muted
I'm
talking
away
and
you're.
Ignoring
me.
Sorry,
meg,
that's
quite
not
your
fault
for
devops
world
did
we
do
anything?
Did
we
try
to
virtual
like
get
people
to
contribute
for
the
first
time
like
we
did
when
we
had
in
person
devops
world,
and
if
not,
do
we
want
to
try
it
or
is
it
just
too
much
with
the
remote.
A
A
When,
at
the
last
contributor
summit,
johannes
presented,
hey
here's
how
I'm
doing
using
jenkins
in
biological
research
and
another
presented,
hey
here's,
how
we're
using
jenkins
to
do
software
development
for,
in
their
case,
elastic
and
elastic,
search
and-
and
there
are
all
sorts
of
other
cool
stories
like
that
and
user
presentations-
would
be
a
great
excuse
for
someone
to
be
a
first-time
presenter,
say:
hey
here's,
how
we're
doing
jenkins.
D
E
A
A
Right
and-
and
there
are
a
lot
of
things
like
that
right,
we
were,
we
were,
we
were
seeking
to
better
understand
the
users
and-
and
I
think
we
achieved
that,
but
the
what
we
didn't.
What
we
didn't
do
then
was
we've
got
more
to
capitalize
on
it,
using
what
johannes
did
and
what
others
did
to
say.
Look,
here's
a
story,
jenkins
is
the
way
is
a
good
example
of
those
kinds
of
stories.
A
A
D
F
A
Excellent
and
thank
you
for
your
contribution.
Diraj!
That's
great!
Thank
you!
So
much.
Thank
you
all
right.
So
let's
go
back
to
agenda,
and
so
the
idea
was
we've
got
first,
this
technical
writing
conventions
topic.
Oh,
we
were
trying
to
figure
out.
If
there
are
other
topics
meg,
you
had
a
question
on.
Do
you
devops
world?
So
is
it
okay?
If
we
take
that
further,
when
we
get
to
that
in
the
agenda,
absolutely.
A
Alyssa's
and
olegs
ask
me
anything
is
another
good
one,
but
it's
already
done
and
we're
past
the
point
where
we
could
take
new
speakers.
So
so
it's
yeah
we've
had
our
chance
there
right.
C
A
A
D
Again,
I
muted
and
you
you
were
ignoring
me,
you
were
correct
and
to
take
care
of
is
kind
of
informal
anyhow.
A
A
D
A
D
A
A
Then
the
next
one
was-
and
this
is
one
I'm
accustomed
to
using
the
impersonal
form
where
I
don't
use-
we,
but
the
the
the
writer
changed
it
to
re.
We
is
there
a
sense
there
of
hey
either
is
okay,
give
me
some
guidance
there
there.
Oh,
this
is
religious,
oh
okay,
so
it's
not
likely
to
get
real
guidance.
It's
more.
D
Right
it's
and
it's
I'm
I'm
with
you,
but
then
people
think
I'm
cold-hearted
anyhow
with
my
writing
style
so
but
yeah
the
and
I,
and
sometimes
I
do
it-
I
actually
go
back
and
forth,
but
you
know
I'm
not
crazy
about.
Please
do
this
and.
D
D
D
A
A
A
A
Okay,
good,
that
was
okay.
That
was
perfect.
That
was
what
I
needed
thanks.
Meg.
Okay,
now
question
is:
is
that
something
we
should
consider
codifying
in
the
style
guide?
The
style
guide
has
has
other
things
in
it,
but
doesn't
specifically
talk
about
that.
One,
let's
see
if
we
look
at
handbook
section
here.
It's
this
one
handbook
style
guide
guides
us
on
how
to
use
links
and
using,
for
example,
instead
of
eg,
and
why
we
use
section
headers
instead
of
bullets,
etc.
D
D
A
All
right,
so
I'm
gonna
leave
it.
As
is
then
thanks
thanks
for
that
anything
else.
On
conventions
before
we
go
next
topic,
yeah,
I'm
good.
Okay!
Next
one
is
I've
submitted
a
pr
we
meg
and
I
actually
created
the
pr
last
week
for
for
the
devops
world
announcement
and
oleg
reviewed
it
and
said:
hey.
We
really
need
a
page
focused
on
this.
It
was
where
is
the
devops
world?
He
said
hey,
please
give
me
a
page
on
the
slash
events,
which
makes
sense.
A
We've
got
a
slash
events
play
page
for
other
things
like
for
contributor
summits.
Why
shouldn't
we
have
one
for
devops
world?
It
happens
consistently.
We
should
put
it
up
there
and
I've
still
got
to
create
that.
The
other
pieces,
I
think,
are
okay
and
we're
in
general
approved
or
were
no
objections.
A
If
you've
got
insights
mark
to
discuss
with
alyssa
tong
for
the
content.
D
When
these
events
are
passed,
do
we
have
a
place
where
you
can
go
and
see
events
that
have
happened
say
in
the
last
year
I'll
light
something
or
something.
A
Them
there
or
we'll
put
links
to
the
notes,
etc
or
move
these
into
a
different
place.
So
it's
pretty
common
that
we
would
find
a
way
to
retain
the
content.
But
it's
not.
We.
D
D
A
A
A
D
A
A
A
Controller
agent
inbound
agent
outbound
agent,
both.
A
A
D
A
Going
to
reach
end
of
life
and
and
when
it
reaches
end
of
life,
we
better
have
been
on
java
11
for
a
while.
D
A
A
A
nope
java
11
has
jenkins
default
jdk
there
we
go
okay.
So
this
is
the
draft
document
and
would
be
happy
to
have
comments
and
feedback
on
it.
I've
still
got
an
awful
lot
to
do
in
it
I'll
get
it
done,
hopefully,
within
the
next
one
to
two
days
and
submit
it
as
the
as
a
formal
jenkins
enhancement
proposal.
D
How
much
of
the
rest
of
the
doc
is
going
to
have
to
I'm
sitting
here
sweating
with
my
normal
with
my
training?
How
much
of
the
rest
of
the
doc
is
going
to
have
to
be
modified
for
this.
A
And
we
look
forward
to
it
and-
and
I'm
actually
one
of
the
speakers
zinab
and
I
will
be
talking
about
the
she
is
she
called
africa
and
getting
open
source
more
widely
into
africa.
A
One
of
the
things
that
we
most
need-
there
is
contributor
summit,
and
this
is
where
we
need
planning
and
coordination.
I'm
happy
to
take
any
volunteers.
A
Promotion
dear,
as
you
say,
you're
willing
to
assist
yes
excellent.
Thank
you
great.
A
E
A
E
E
Yeah,
the
the
the
doc's
room
was
a
little
quiet,
but
it
was.
It
was
nice
because
you
know,
I
think,
the
one
or
two
people
that
did
come.
It
was
yeah.
It
was
very,
you
know.
D
E
A
E
Right
is
there
anything
that's
going
to
be
rolling
like
any
type
of
programs
or
anything
for
jenkins
or
even
like
cdf,
like
that's
on
like
in
rolling
up
to
contributors
summit,
or
is
it
just
kind
of
the
one
day.
A
Well,
so
we'll
do
I
I
I
hope
what
we'll
do
is
we'll
do
active
promotion
of
the
event
right,
but
but
active
promotion
event
is
usually
not
enough.
It
will
be
a.
I
suspect
this
time
will
register
through
a
jenkins
online
meetup.
E
A
Last
time
we
used
cdf
to
handle
the
registration,
they
did
an
awesome
job
of
promoting
okay.
They,
the
number
of
registrations,
was
mind-boggling.
Jenkins
online
meetup
has
been
our
vehicle
in
the
past,
and
then
we
don't
have
to
make
people
actually
enter
data
that
they
may
be
uncomfortable
entering.
A
We
will
host
it
with
zoom
again
so
zoom
webinar
for
the
presentations
and
then
zoom
what
they
call
them.
Breakout
rooms
for
the
discussions
and
interaction.
A
A
So
if
you,
if
you
hear
of
users
by
all
means,
help
us
recruit
more
people,
particularly
in
asia,
pacific
right,
one
of
the
challenges
for
this
is
many
of
the
users.
We
that
talked
at
the
last
session,
we're
all
european
based
and
their
their
time
zones.
Just
don't
work
for
this
asia
pacific
presentation.
So
we
need
people
in
australia
in
india,
in
china,
in
japan,
in
malaysia,.
C
Well,
there's
a
lot
due
to
gsoc,
mainly
and
yes,
due
to
gsoc.
There
are
some
engagements
from
colleges
college
students
side.
So
yes,
there
is
a
lot
going
on
right
now.
A
Okay,
well
so
meg.
To
give
you
a
an
indication
oleg
presented
at
a
webinar,
hosted
by
a
student
team
in
india,
and
I
think
there
were
hundreds
of
attendees.
D
A
D
A
A
C
Yes,
so
I
just
wanted
to
know
here
that
there
are
some
like
if
you
look
at
bump
access
modified
annotation
from
this
to
this
and
access
modified,
checker
and
matrix
or
so,
which
one
should
I
include
here
and
which
one
should
I
comment
out.
So
we
previously
previously
suggested
me
that
I
need
to
look
at
the
same
name
its
occurrence
previously
and
look
at
it
whether
it
was
previously
commented
out
or
written
out.
So
I
looked
at
it,
but
some
of
them
were
occurring
here
for
the
first
time.
A
A
A
A
A
A
A
A
A
D
D
D
D
A
C
A
A
A
A
Is
him
cleaning
up
the
terminology
so,
whereas
the
terminology
used
to
show
master,
it
now
says
uh-uh
if
you're,
if,
if
we
did
not,
if
we
see,
let's
read
the
logic
if
distributed
builds
are
enabled
so
the
controller
is
there
or
no,
there
are
agents
available.
So
if
agents
are
available,
then
it
won't
show
it
and.
A
A
A
D
A
D
D
A
A
A
Why
is
this
flagged?
Okay,
all
right,
so
I
think
we
may
have
a
an
open
issue
there.
This
is
really
dhiraj.
It's
been
flagged
as
internal,
but
I
don't
see
internal
is
that?
Oh
no.
He
says
that
it's
internal
only
so
there's
nothing
to
so,
since
it's
internal,
that's
why
you
put
the
internal
keyword
there
right
mirage.
B
A
E
E
A
A
A
D
A
E
A
A
Okay,
so
I'm
gonna
actually
approve
it
optional
comments
for
consideration.
A
A
A
A
He
notes
hey
if
we're
losing
the
ability
to
copy
edit
and
curate
change
log,
why
have
it
and
tim's
response
is?
We
can
still
copy
edit?
A
And
daniel's
concern
was,
nobody
is
going
to
bother
doing
that
and
my
thought
was
dhiraj
you
and
I
actually
may
be
quite
willing
to
do
that.
So
what
this
automation,
what
this
machinery
does
is.
It
creates
the
pull
request
for
us
and
then
we
can
at
any
time
go
in
and
modify
or
submit
additional
changes
to
the
poll
request.
C
D
A
D
E
I
kind
of
like
it
because
it
makes
it
it's
there
automatic
you
don't
have
to
worry
about
generating
it
right.
C
A
A
Correct,
I
I
think
you've
said
it
well,
it's
automating
the
the
right
now
diraj
and
before
dhiraj
I
did
and
before
I
did
it.
Daniel
did
runs
a
script
that
assembles
the
a
draft
of
the
change
log.
Then
dhiraj
will
provide
copy
editing
to
make
sure
that
it
is
correctly
laid
out
that
it
looks
right
and
you'll
paste
an
image
of
that
of
that
revised
that
revised
and
copy
edited
change
log
in
this
pull
request.
D
D
A
A
A
A
E
So
k
whetstone,
oh.
A
A
C
A
No,
I
think
I
think
there
is
still
there's
there's
still
a
hype.
Well,
there
are
a
number
of
other
barriers
to
full
automation.
Things
like
the
original
pull
request,
doesn't
describe
it
well
enough
or
is
badly
formatted,
and
the
tooling
can't
extract
the
the
comments.
There
are
all
sorts
of
things
that
can
go
wrong
there,
but
this
feels
like
a
good
first
step
towards
automating
it
towards
that
eventual
day
where
we
might
envision.
It
would
be
fully
automated
like
release
draft
well
something
even
better
the
release.
Drafter
does.