►
From YouTube: 2021 09 06 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
B
B
And
today
is
a
holiday
in
the
u.s,
so
we
may
not
have
anyone,
but
you
and
me
attending
so
I
had
jenkins
2.310
change,
log
preview
and
then
inclusive
naming
improvements
is
probably
worth
some
time
and
contributor
summit
further
time
for
more
time.
So
are
there
other
topics
you'd
like
to
discuss
diraj.
B
Okay.
Okay,
so
that's
that's
enough
all
right!
If,
if
there
are
more,
we'll,
certainly
add
them,
okay,
so
so
I
we
learned
from
our
last
week's
our
last
review
of
the
automated
change
log
that
changes
to
the
pr
are
discarded
until
the
release
is
published.
So
what
we
need
to
do
is
when
there's
a
change
we
need
to
make.
We
update
the
pull
request
with
that
correction
and
then
rely
on
the
tooling
to
pull
in
the
updated
pull
request.
B
B
B
So
let's
speculate
that
there's
something
here.
That
needs
to
be
changed
that
we
can't
fix.
Okay,
so
this
is.
This
is
a
good
reminder
to
me.
I
need
to
use
correct
formatting
the
automation
fixed,
the
formatting
that
I
had
put
in
last
week
and
the
fix
that
it
made
is
correct.
It
indented
underneath
the
top
level
thing
by
two
spaces
before
putting
the
dash
so
mistake
on
my
part.
B
B
And
it
goes
through
jnr
posix
bump
from
317
to
318..
We
don't
want
type
to
do,
and
so
I
think
we
need
to
go
edit.
This
pull
request
now.
The
problem
here
is,
you
don't
have
permission
to
edit
pull
request
text.
If
I
remember
right,
do
you
could
you
could
you
dhiraj?
Could
you
open
your
this
one
on
your
side
and,
let's
see
if
because
I
I
suspect
you
have
to
be
allowed
to
merge
before
you
can
edit
the
text
of
a
pull
request?
B
B
B
So
what
that's
done
is
if,
in
this
use
model
the
the
only
people
who
can
fix
these,
so
you
could.
You
could
offer
a
correction
here
and
say:
hey
this
needs
the
following
fixes,
but
not
you
wouldn't
be
able
to
give
a
to
fix
it
right
in
place.
So
I'm
going
to
go
ahead
and
attempt
the
fix
here,
because
now
I
want
us.
I
want
us
to
also
learn
one
more
item,
which
is
that
we've
got
another
problem,
which
is
that
depend
about
pull
requests.
B
B
B
D
So
we
are
searching
for
jnr
posix
release,
notes
for
3.1.8
version
right,
correct.
B
B
So
so
maybe
what
the
answer
here
is
for
defensive
copy
improvements
for
for
various
for
code
improvements.
B
B
B
B
B
C
D
So
we
edited
the
pr
to
be
to
align
it
with
the
standard
template
that
we
follow
and,
as
you
said,
depend
upon,
does
not
follow
that.
So
we
did
that
because
next
time
the
automatic
change
log
is
done,
so
it
will
be
able
to
better.
B
Correct,
at
least
that
was
my
attempt,
but
I'm
not
sure
that
that
will
even
that
will
fix
everything
because
type
is
listed
as
to
do
here,
and
it's
not
clear
to
me
that
the
changes
we
made
will
fix
this
one
category
developer.
That's
that's
correct!
That's!
Okay!
Although
this
is
a
developer
item,
that's
very
high
in
the
list
and
developer
items
by
the
rules
should
be
very
bottom
of
the
list,
so
the
location
is
wrong.
Let's
note
that
as
well.
B
B
B
D
Yes,
so
what
is
the
frequency
at
which
this
automatic
change
log
does
its
work
so
like
I
used
to
write
it
every
tuesday
morning.
So
what
about
this
automatic.
B
C
D
B
D
B
B
B
B
So
so
now,
let's
continue,
though,
because
there's
more
frustrate
review.
Okay,
so
this
one
says
all
right:
there's
a
request
for
enhancement
and
it's
registered
dependency
class
loader
in
the
default
plugin
strategy
as
okay.
So
here
it
is,
it
says:
jenkins,
27,
3,
23,
784
load
classes
from
plugins
in
parallel.
B
B
C
B
B
B
B
B
B
Okay,
then
there's
this
bug,
agent,
controller
security,
kill
switch
and
the
check
box
labeled
enable
agent
to
control
or
access
control
in
the
form
would
always
start
out
as
disabled.
It
could
then
cause
a
configuration
change.
Oh
yes,
okay
and
I
think
in
the
past
we've
used
regression
in
yeah.
We
put
the
full
stop
at
the
end
after
the
regression
in
right.
B
B
B
B
B
B
B
Okay,
all
right,
so
I
think
I
think
we're
ready.
Okay,
oh
let's
see
we
need
to
submit
this
review
so.
D
D
No,
not
this
one,
the
the
this
the
check
box
labeled
enable
agent.
Yes,
this
one
so
here
the
type
was
major
bug
in
the
manual
changelog,
but
here
it's
just
bug.
B
B
B
E
B
B
C
C
B
D
Yes,
last
question
is
so
let's
say
next
week
before
this
meeting
half
an
hour
before
this
meeting
starts.
I
want
to
work
on
the
pr
I
want
to
work
on
the
change
log
so
I'll
be
following
the
same
steps
right
going
through
the
prs
that
first
of
all,
going
through
the
change
log
that
the
bot
has
generated
and
then
look
at
the
pr's
and
if
there's
any
problem
in
a
pr
in
terms
of
any
grammatical
mistake
or
anything.
D
So
I
would
go
to
the
pr
and
then
add
a
comment
for
now
right
and
then
someone
like
you
or
anyone
else
would
update
the
pr
suggested
by
me
before
looking
at.
If
my
solution
is
right
or
not,
and
then
that
will
be
done
for
that
entry,
because
then
the
bot
will
be
able
to
write
it
write
the
change
log
correctly
are
those
the
steps.
B
Yes,
that
would
be.
That
would
be
a
great
way
to
do
it.
Then,
in
the
meeting
we
copy
those
those
comments
into
the
text,
and
then
we
may
want
to
see
if
we
can
negotiate
with
with
tim
or
someone
else
to
allow
comments
to
be
part
of
the
the
automated
changelog
processing
right,
because
if
we
could
do
that,
then
your
comments
could
be
used
to
to
fix,
fix
specific
problems
in
like
the
ones
in
this
one
right.
B
B
B
B
B
B
I
think
I
and
we
we
don't
see
the
hard
stops
the
full
stops
on
those
lines,
but
we
added
those
so
the
layout,
no
no
disastrous,
surprises
in
this
layout.
As
far
as
I
can
tell
yes
all
right
so
dhiraj
in
terms
of
your
idea,
how
do
we
get
the
knowledge?
How
do
we
get
the
information
from
you
into
into
the
pull
request
description?
B
I
think
you've
got
the
right
idea.
You
just
add
a
comment
here
for
now,
because
that
you
can
do
and
if
that
comment,
if
that
comment,
then
I
can
oh
no
not
here.
Sorry,
you
add
a
comment
into
the
specific
pull
request
and
say:
hey.
I
think
the
change
log
should
be
this
paste
that
text
and
then
we
can
go
in
and
copy
that
from
there
and
paste
it
up
here
as
needed
during
the
meeting
sure.
B
B
B
B
B
In
many
plugins,
because
they,
the
tests,
often
assume
master
as
a
the
label
on
the
built-in
node
bazel
and
daniel
beck,
proposing
pull
requests
to
fix
them.
B
B
D
Written
down
in
our
jenkins
community
that
portal
that
jenkins,
this
one
contributor
summit
would
be
on
october,
2,
right
and
devops
starts
at
september
29th.
So
it's
like
a
week
long
so
summit.
B
B
E
B
D
C
A
B
Like
that,
oh
yeah,
I
think
tim
would
love
it.
Shall
we
take
a
look
at
it
now,
we've
got
four
minutes
left.
Let's
take
a
look
at
it
now
and
see
see
if
we
could
do
something
with
it
ourselves.
A
B
B
B
A
B
So
if
we
wanted
to
do
if
we
wanted
to
do
dependencies,
we
could
put
an
entry
here,
a
line
here
and
say:
if
entry
type
is
if
labels
includes
dependencies,
then
make
it
an
rfe
or
a
bug
or
whatever.
B
Specifically
this
thing
says:
if
it's
a
regression
fix
we're
just
going
to
call
it
a
bug,
not
always
call
it
a
major
bug,
and
I
think
if
we
were
to
look
at
the
history
of
this
thing,
we
would
see
that
it.
Yes,
here
we
go
oleg
changed.
It
do
not
consider
regressions
as
a
major
bug
by
default,
so
so
we
see
that
he
intentionally
switched
it
this
way.
B
C
D
D
Yes,
a
very
quick
question,
so
I
tried
to
run
this
script
by
myself,
but
I
was
having
problem
of
github
or
authentication
something.
So
I'm
not
sure
what
was
the
reason
behind
that.
Like
do,
I
need
to
know
some
credentials
for
specific
to
get
jenkins
repository
in
order
to
run
the
script.
B
B
D
Okay,
because
tim
suggested
me,
if
I
can
do
some
changes
and
improve
the
script
I
can
so
I
tried
to
do
it
that
day,
but
I
was
not
able
to
run
it
due
to
this
same
thing.
B
D
B
B
D
Yes,
exactly
so,
it
was
replacing
it
with
nobody,
slash
something
something,
oh
interesting,
because
it's
hardcoded
somewhere
there,
nobody
something
like
that.
B
Okay,
okay,
now
way
to
say
curl
underscore
off:
okay
github
see,
I
would
have
expected
if
you
define
github,
underscore
auth
to
be
diraj,
joda,
colon
and
then
a
personal
access
token
generated
for
this
purpose.
It
should
authenticate
you
correctly
as
you
now
I
haven't
tried
it
though,
but
that
I
think
it's
worth
trying,
because
I
think
this
must
be
passed
in
in
the
case
where
it's
called
from
the
from
the
job.
That's
running
it.