►
From YouTube: 2021 11 08 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
So
here
are
the
topics
that
I
had
on
my
list:
a
status
report
on
oops
status
report
on
adding
more
copy
editors
and
review
of
the
2.320
changelog.
I
think
those
are
the
the
change.
Changelog,
I
think,
is
the
single
most
important
thing
to
do
today
and
if
that's
all
we've
completed,
I
would
feel
good
about
this
session.
A
B
The
one
I
have
for
security
is
part
of
adopt
a
plug-in.
Actually,
so
oh.
B
I
don't
have
we
don't
have
much.
I
had
I
heard
from
daniel
that
the
he
has
he
survived
the
security
release
and-
and
he
was
yeah,
I've
said-
and
you
know
he
was
just
like
I'll
get
into
this
and
I'm
like
daniel
take
a
break.
We
know
what
you've
been
through.
You
know
can't
do
it
not
anymore
people,
so
that's
there.
I
have
one
for
after
adopt
a
plug-in
if
we
get
to
it.
B
There
is
an
old
more
than
a
year
old
pr
out
there
that
I
reviewed
and
it
was
done
before
the
ui,
changed
and
but
and
I've
been
thinking
about
working
in
this
space
anyhow,
so
sort
of
a
high
level
discussion.
And
then
I've
got
some
ideas
and
I
can
get
to
work.
D
B
D
B
A
Okay,
great
all
right,
so
then,
let's,
let's
do
the
topic
so
copy
editors.
I
sent
the
request
to
the
developer
list.
All
the
responses
were
positive,
so
it's
approved
you'll
all
be
members
of
the
triage
team
after
a
mentoring
period
and
we'll
choose
what
that
time
is
then
we'll
make
you
members
of
copy
editors.
A
Test
drive
the
the
change,
because
it
should
be
much
easier
than
the
current
the
current
technique.
The
current
technique
requires
that
you
sign
a
pdf
file
with
your
physical
signature
and
scan
it
or
no,
you
have
to
do
something
with
a
gpg.
Key
all
sorts
of
complexity,
and
this
easy
cla
sounds
a
lot
better.
A
B
A
Okay,
so,
while
that's
running
getting
itself
ready,
let's
look
at
it
and
make
it
big
enough
to
read.
Okay!
Is
that
readable
to
everyone.
A
A
A
A
A
A
kind
of
cool,
ibm,
mainframe,
okay.
Next
one,
this
one's
got
a
really
strange
character
there
that
I
do
not
understand
why
it
got
there.
So
we've
got
to
fix
something
there,
but
I'm
going
to
look
for
others
to
help
me
understand
what
we
need
to
change
in
order
to
fix
that
somehow
or
other
it
got
an
extra
thing
inserted
prior
to
being
called
a
major
request
for
enhancement.
A
A
B
E
B
A
A
Wait
a
second!
Oh,
oh,
oh
maybe
this!
Maybe
I
I
don't
know
if
that
that
would
be
it
because
I
love
what
that
does.
Is
that
makes
it
a
link
to
the,
although,
let's
see
there's
something
suspicious
hiding
in
there?
No
that's
perfectly
reasonable.
A
A
That
it
could
be
yes,
that's
true,
so
I
this
this
is
all
that
would
would
remove
it,
and
so
I
could
replace
this
with
a
a
link
to
the
ac
to
the
pull
request
that
presents
it
in
a
different
format.
So
it's
46.40,
the
one
that
he
used
is
really
nice,
because
it
presents
a
a
an
actual
textual
description.
A
Oh
it's
already
there:
okay,
there
it
is,
and
that
might
be
it
making
a
wild
guess.
B
B
A
A
And
that's
their
icon,
so
that's
not
anything!
We
can
actually
fix
uh-huh.
So
so
my
hunch
right
now
is
we're.
We
may
have
to
edit
this
one
after
the
fact.
After
the
release,
I'm
not
sure
how
to
how
to
fix
that,
because
I
don't
know
what's
at
the
root
of
it.
So
how
about
we
go
to
the
next
one
and
see
if
we
can
do
okay,
something
similar
here,
so
this
one
is
add
ability
to
upload
a
plug-in
via
the
url
and
he
says
okay,
so
I
disagree
with
this
one.
A
C
A
A
Much
user
visible,
allow
plug-in
upload
by
url,
in
addition
to
plug-in
upload
by
file.
How
about
that
better
phrasing.
A
B
A
A
A
A
A
A
F
Interesting
is
this
comment
here
and
it
says
we
would
like
to
eventually
use
as
the
default
class
loader,
and
I
don't
normally,
I
would
say
it's
a
dependency
update.
We
probably
don't
need
to
do
it,
but
I'm
wondering
if
we
want
the
historical
tracker
of
coming
back
and
saying
it
was
in
this
release
is
when
we
did.
A
B
A
Well,
so
one
of
the
patterns
we've
used
in
the
past
is
to
help
people
in
the
reading.
We
state
the
from
and
the
two
versions-
oh
okay,
but
but
in
this
case
it
states
neither
and
so
let's
to
2.25,
and
usually
we
will
include
a
hyper,
a
reference
link
to
the
change
log.
For
that
that
version-
and
here
where
is
the
change
log
for.
A
A
B
B
A
A
Oh
need
to
do
that.
Thank
you.
C
Not
really
like,
we
have
this
new
view,
which
is
under
the
oh.
A
A
A
A
Okay,
then
any
any
comments
there
anything
you
want
to
improve
on
that
phrasing.
A
A
Right
it
is
that
that
class
loading
no
longer
reports,
a
linkage
error
when,
when
yeah,
the
class
loader
no
longer
reports,
linkage
errors.
A
B
A
Okay,
so
prevent
class
loading
linkage,
error.
F
A
A
A
A
A
A
C
A
A
A
Wow:
okay,
this
one
will
need
editing
after
the
fact
to
include
the
reference
to
the
upgrade
guide
etc.
But
the
text
itself
looks
good
to
me
any
objections
to
the
text.
B
A
A
A
A
A
D
A
A
A
A
E
A
A
A
B
B
E
D
F
B
A
A
A
F
A
A
A
A
F
B
A
A
A
A
Why
would
a
because
there
is
no
user
visible
change
on
this
one?
This
is
this
is
a
the
beginnings
of
the
content
security
policy
changes,
but
the
user
perceives
no
change
and
that's
good.
A
Me
know
what
changes
will
be
needed
after
the
release,
including
okay,
now
help
me
remember
what
they
were.
Let's
see
add
reference
links
for
change
logs
and
that's
in
bouncy
castle,
and
there
was
one
other
right,
diraj
bouncy
castle
and
oh
and
asm.
A
Right,
good
other
minor
changes
outs
that
outside
yeah.
Let's
just
leave
it
at
that:
okay,
agreeable.
So
far,
okay,
good!
So
we
we
completed
task
number
one.
A
A
Not
quite
yet
there
now,
it's
ready
all
right,
so
developer
guide
now
has
the
adopt
a
tutor
plug-in
tutorial.
This
is
this
is
on
our
working
working
development,
copy
and
notice
all
of
these
sections,
each
of
them
a
a
step
in
a
a
modernizing
a
plug-in
as
part
of
adopting
it.
So
here's
the
first
one
add
a
jenkins
file
with
a
video
link,
create
a
pull
request
and
instructions
on
how
you
do
this
likewise
update
the
parent
palm.
A
Likewise
review
build
status.
Now
this
one
we've
got
to
fix
some
images
but
update
the
minimum
jenkins
version.
Okay,
add
more
spot
bugs
checks,
and
it
just
keeps
going
like
this
now
dhiraj
was
there.
I
think
there
are
some
here
that
don't
have
the
embedded
video
yet
but
videos
available.
So
I
need
to
go
through
and
do
the
add,
the
video
connections,
because
darren's
videos
are
there.
We
just
have
to
find
the
right
location
to
insert
them
like
this.
A
It's
so
they
are
in
the
in
the
google
document,
but
they
are,
let's
see,
let's
get
contribute,
let's
open
the
google
doc
and
you
can
see
where
they
are
contributing
to
open
source.
What
I
did
is,
I
put
them,
live
stream.
Videos
here
so
here
are
part
one
through
five
and
then,
if
you
open
that
individual
video
and
let's
see
how
do
I
no,
I
do
not
need
to
see
that.
Yes,
I
have
to
wait
for
the
ad
okay.
A
Are
we
done
okay
there
now,
if
we
go
down
here
into
the
show,
more
here
are
the
hyperlinks
to
the
to
the
specific
topics,
oh
nice,
and
so,
if
I
copy
this
link
address
and
paste
it,
it
puts
in
the
time
when
that
segment
starts,
oh
nice,
and
so
in
the
page
when
the
user
is
it
clicks
here
if
they
click
this,
this
play
button.
It
actually
jumps
inside
right
to
that
segment.
B
A
A
A
B
Can
you
click
on
the
storing
secret
section?
I
want
to
see
what
you've
got
secret
under
security.
You've
got.
A
A
A
Well,
I
I
would
like
it
to
be
part,
but
I
think
first
dhiraj
and
I
have
to
be
sure
we
we
believe
the
content
and
we
think
the
contents
got
the
right
things
in
it.
Then
fixing
or
improving
the
navigation
here
on
the
left
side
that
the
code
is
already
there
in
the
user
handbook,
we
just
have
to
figure
out
how
to
apply
it
to
the
developer
guide
right.
E
Sorry
I
missed
it,
you
said:
there's
a
problem
where
the
third
one
review,
ci
jenkins.
C
A
A
A
A
Okay,
right
images,
slash
image
too,
got
it
okay,
so
it
would
need
to
go
into
content,
but
I
think
we'll
want
it
in
a
subdirectory
of
content,
slash
images
and
I'm
not
sure
what
that
subdirectory
should
be,
because
there's
a
content,
slash
images,
slash
developer
and
it
and
there's
a
yeah.
So
it's
probably
to
match
everything
else.
We
should
probably
put
it
in
tutorial
dash,
adopt
and
create
a
new
directory
like
that.
A
A
A
C
G
A
A
A
How
somehow
into
separate
subsections
where
the
list
of
all
sections
goes
at
the
end
still,
but
subsections
might
have
headings
like
I
don't
know
what
we
would
call
them
even
initial
stuff
and
then
or
maybe
it's
basics,
and
then
it's
automation,
okay
and
then
it's
code
changes.
A
A
In
addition,
now
this
one,
if
I
remember
right,
no,
it
doesn't
have
the
navigation.
Okay.
The
other
thing
that's
missing
here
from
my
taste
is
navigation
links
at
the
top
of
the
page
exactly,
but
that
we've
already
got
in
the
user
handbook,
so
we
can
do
it
in
the
user.
We
can
just
steal
it
from
the
user
handbook
and
make
it
fit
here.
E
C
F
B
F
A
B
B
A
Right
see
that
and
that's
that's
the
nicety
here
of
the
user
handbook
does
have
the
the
collapsing
and
expanding
based
on
your
current
page
and
current
section.
So
when
I
go
when
I
go
here,
it
bolds
this
and
the
navigation
bar
up
here
will,
let
me
get
to
the
next
page
and
the
previous
page.
So
so
there
is,
there
is.
A
A
Tutorial
haven't
done
anything
yet,
except,
let's
see,
we've
got
one.
I
think
we
had
one
thing
which
was
which
may
not
be
here
yet,
which
is
on
enabling
automated
security
scans
yeah.
So
it's
not
here,
but
it
is
in
this
document.
So
so
that's
when
we've
still
got
to
add,
which
is
just
where
did
darren,
and
I
do
that.
It
was
code
ql
up
no
code
ql.
Here
we
go
enable
jenkins,
specific
security
scanning.
B
B
What
I
don't
know
if
you
saw
the
discussion
derraj
and
I
were
discussing,
but
there's
a
whole
bunch
of
stuff-
that
plug-in
developers
need
to
do
for
security
right
and
what
I
was
going
to
propose.
I
actually
have
a
little
pr.
That's
a
nascent
file
that
in
this
and
another
thing
background
one
of
the
things
in
the
security
stuff
is
daniel,
wants
a
place
where
he
can
go
periodically
and
scan
through
that
and
say.
Yes,
everything
about
security
is
here.
B
So
and
so
what
I
carded
was
a
small
file,
that
is,
security,
things
for
plug-in
developers
and
maintainers,
or
something
like
that,
and
it's
almost
a
checklist
with
links
to
the
other
docs
that
have
the
details
about
it:
okay,
and
what
I'm
thinking
is
we're
gonna
go
nuts.
If
you
start,
if
you
have
other
security
stuff
in
here,
we're
gonna
go
nuts.
B
Maintaining
this
like
last
week,
security
release
had
a
big
one
that
affects
plug-in
developers
and
that
if
we
just
had
that
one
checklist,
that's
there
and
then
the
security
thing
could
say
you
are
responsible
for
making
sure
that
your
plugin
is
secure.
It
does
everything
right
go
here
and
you
could
link
to
that
file
and
then
we've
just
got
one
file
that
we
have
to
keep
updating
for
new
issues.
A
I
like
that,
so
so
link
review
how
about
if
we
called
it
review
the
plug-in
security
checklist,
and
then
this
would
be
a
hyperlink
to
your
see
the
plug-in
security
checklist.
A
B
B
B
B
A
A
C
C
Document
so
it's
like
it's
the
instructions
for
the
it's
specifically
for
the
plug-in
maintainers,
so
we
need
to
figure
out.
Where
do
we
put
those
instructions,
because
these
instructions
that
we
see
on
the
screen
are
specif
not
specifically
for
plug-in
maintainer?
It
can
be
done
for
anyone
who
can
send
a
pr
right.
A
Right
yeah,
so
for
me,
that's
another
form
of
sort
of
sub
categorization
right,
so
we've
got
the
there's
things
that
I
mean
things
that
a
contributor
can
do,
and
that's
this
list
of
10
plus
pages
of
things
that
a
contributor
can
do.
These
are
things
in
this
section.
This
couple
of
pages
worth
are
things
that
only
a
maintainer
can
do
so.
There's
there's
no
point
in
a
a
contributor
attempting
to
enable
release.
Drafter,
that's
that
requires
maintainer
permissions.
A
There's
no
point
in
a
contributor
trying
to
enable
continuous
delivery
it
and
there
really
isn't
any
point
in
a
maintainer
reviewing
the
plug-in
security
checklist.
I
guess
they
could,
but
if
there's
any
outcome
of
it,
they're
now
having
to
follow
the
security
process
to
just
to
to
report
the
issues.
A
E
B
Very
top
of
the
stock
okay,
the
intro
thing
is
it
some
place?
No,
no,
the
other
one,
the
one
that
we
had
that
had
deraj
is
listed
there.
We
go.
Okay,
sorry!
This
is
a
starting
point.
It
explains
common
steps
that
improve
a
plug-in
and
help
help
prepare
a
developer
to
adopt
the
plug-in
but
you're
saying
most
of
these
things.
They
can't
do
unless
they
have
adopted
the
plug-in
or
the
maintainer.
B
A
A
B
A
B
B
Right
and
then
yeah,
just
I'm,
I'm
so
bad
with
all
this
stuff,
I've
gotten
as
bad
as
the
developers.
I
don't
read
those
introductory
paragraphs.
I
scan
over
them
right.
A
And
reviewing
and
I'm
okay
with
that
right,
because
if,
if
they,
if,
if
a
developer,
says
yeah,
maybe
I
would
like
to
adopt
a
plug-in.
Maybe
the
other
alternative
we
could
say
here
is.
We
could
call
this
modernizing
a
plug-in
rather
than
adopt
a
plug-in,
because
it's
also
modernizing
a
plug-in.
I
don't
know
which,
which
is
more
more
intimidating
or
less
intimidating,
more
inviting
less,
inviting
contributing.
A
A
B
What
you
said
yeah,
because
this
we
don't
get
the
clarity
here,
that
you
can
contribute
and
fix
some
stuff,
there's
big,
then
a
maintainer
is
responsible
for
doing
these
things,
one
of
one
of
them,
I
think,
being
when
there
are
security
fixes
that
affect
plug-ins.
You
may
have
to
test
your
plug-in.
You
may
have
to
modify
your
plug-in
to
comply
or
something
you
know,
but
that's
that's
not
clear
here.
D
B
B
A
However,
if
we
look
instead
at
a
different
plug-in,
let's
pick
what's
another
plug-in
with
substantial
documentation
how
about
github
branch
source
this
one,
I
think,
oh
no,
that
doesn't
have
any
how
about
this
one
yeah
this
one!
Okay,
this
one!
I
can't
link
to
the
hyperlinks
between
changes
right.
G
A
A
B
A
B
B
A
C
F
Does
I
this
is
so
helpful
like
when
this
goes
out
there
like
this
would
be
so
nice,
especially
for
the
plugins
who
could,
even
even
if
there's
someone
doesn't
become
a
maintainer
just
to
get
the
updates
in
there
and
just
getting
started
being
able
to.
Maybe
maybe
someone
will
use
it
to
commit
a
a
feature
that
they
need
be
so
great.
A
A
A
A
All
right
thanks,
everybody
recording.