►
From YouTube: 2022 09 02 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
A
A
B
Yeah,
it
looked
pretty
good.
I
got
a
tuesday's
or
yeah
our
meeting
that
we
have
together.
Man
showed
off
like
his
code
and
it
looked
pretty
good,
so
very.
A
Well,
we'll
show
it
we'll
show
it
on
the
live
site
now,
yeah,
there's
there's
still
some
bumps,
but
the
bumps
are
minor
compared
to
the
improvements.
So
exactly
all
right
great.
If
nothing
else,
then
let's
go
ahead
and
start
through
the
list,
so
I
still
haven't
archived
the
docs
mailing
list
that's
pending
and
I
still
owe
a
couple
of
blog
posts.
A
A
A
We
had
to
work
through
an
issue
where
the
site
generator
was
making
a
mistake
and
not
doing
a
recursive
unzip
and
that's
fixed
now,
and
so,
let's
look
at
how
it
how
it
looks
and
feels
so
pipeline
steps.
Reference
is
here
and
if
I
were
to
search
for
checkout,
finds
it
nice
and
quickly.
Here
I
click
this
one
notice
how
quickly
that
page
loaded
yeah
boom
it's
there
now.
This
is
still
presenting
the
same
page.
However,
when
I
try
to,
and
so
when
I
click
on.
A
Let's
click
on
a
less
popular,
it's
scm
like
harvest,
okay,
there's
it
shows
it
opens
and
closes
genexis
again
opens
and
closes,
but
when
I
click
one
of
the
really
big
monstrous
ones
like
git
scm,
it
converts
it
to
a
hyperlink
and
then
I
click
the
hyperlink
and
it
opens
it
in
a
new
tab.
Now
that
opens
it
in
a
new
tab
is,
I
think,
a
little
bit
of
a
surprise.
That
was
one
I
had
missed
during
review.
I
think
we
want
it
to
stay
on
the
same
page,
but.
C
A
Likewise,
let's
see
what
was
the
one
that
vihan
showed
vihan
showed
a
different
one,
but
which
showed
the
same
exact
behavior.
It
was
that
hey
the
pages
load
much
faster
and
the
system
is
much
more
responsive
because
of
it
now
vihan
did
know
that
there
was
one
page
that
surprised
him
in
the
in
the
process
and
I
think
he's
still
investigating
that,
but
even
with,
and
that
page
was
just
because
it
took
it,
had
an
unexpected
layout.
Let's
see
if
I
can
find
his
comment
in
the
pull
request.
A
A
A
C
A
I
I
don't
know
well
so
so
what
we
see
here
is
this
thing
has
a
very
long
list
of
of
classes
that
are
hit,
and
some
of
them
may
in
fact
be
quite
large.
I
I
don't
know
for
sure,
but
I
suspect
some
of
them
may
be
very
large,
and
so
it's
not
clear
to
me
what's
going
on
that
causes
this
page
to
behave
like
this
I'll
make
a
note
of
it
in
our
notes.
Just
to
be
sure,
we've
got
it.
C
What
is
the
god,
I'm
trying
to
remember
the
plugin
that
we
got
burned
on
for
last
year's?
She
codes
africa,
the
one
that
has
all
that
stuff
in
it
that
I
actually
had
thought
was
part
of
jenkins
itself,
chicken's
core,
but
it's
actually
a
plug-in.
B
A
B
A
B
A
C
B
C
B
I
was
like,
I
think
I
know
you're
talking
about
okay.
This
is
a
huge
one
and
we've
actually
we've
been
kind
of
talking
about
in
the
our
little
meeting
for
summer
code
about
like
what
to
potentially
do
here,
because
it's
just
right.
C
B
A
A
Well
and
notice
notice
again
back
to
no
notice
the
benefit
of
the
load
performance.
That
page
is
loaded
and
if
I
show
the
show
the
page
source,
okay,
the
scroll
bar
size
gives
you
a
hint-
it's
not
a
huge
page
anymore,
whereas
previously
it
was
enormous.
Yes,
so
so
the
split
that
has
been
done
is
is
a
dramatic
improvement.
A
C
A
B
A
B
But
yeah
yeah,
I
he
did
an
amazing
job
beyond
beyond,
has
done
an
amazing
job
with
the
documentation
and
like
the
layout
like
making
things
so
much
faster.
It's
it's
been
a
great
project
and
he's
done
phenomenal
work
so
very,
very,
very
like
it's.
What
he's
done
is
so
cool.
It's
been
so
nice
to
have
him
focusing
on
that
and
the
layout
coming
up
with
new
ideas
for,
like
you
know,
looking
at
it
with
a
fresh
set
of
eyes
and
having
some
good
ideas
and
then
being
able
to
work
on.
It
has
been
wonderful.
A
Oh
yeah-
and
I
just
had
a
conversation
with
john
mark
yesterday
and
he's
proposing
us
to
to
do
a
final
round
of
presentations.
A
A
A
A
A
A
A
A
C
A
C
A
A
Well
and
so,
let's,
let's
cheat
and
copy
that
link
address,
we're
gonna,
cheat
and
bypass
the
redirect
by
inserting
a
few
slashes.
A
C
A
C
A
C
A
A
A
And
it
doesn't
need
any
terminology
updates.
As
far
as
I
know,
let
me
double
check
just
to
be
sure
no
mention
of
master
no
mention
of
slave
other
than
in
java
source
code.
References
yeah
and
those
are
not
fixable
yet
okay,
so
we
don't
need
any
mention
of
terminology
updates
and
the
to
migration
tutorial.
A
Azure
devops
and
team
foundation
server:
this
is
dead,
the
plug-in
is
no
longer
distributed,
oh
because
there
are
known
vulnerabilities
and
it
had
a.
There
are
three
known
vulnerabilities
and
it
had
an
issue
where
we
were
concerned
that
it
was
had
a
non-open
source
component
in
it.
So
this
is
a
won't.
Do.
A
A
A
C
A
A
A
Okay,
next
migrate
process
tree
killer
this
one
I'm
going
to
take
out
of
good
first
issue
because
after
a
conversation
with
basel
crowe,
he
noted
that
he's
not
persuaded.
We
really
want
to
be
documenting
this
technique
and
it's
already
in
process,
so
it
makes
no
sense
to
have
it
listed
as
a
good
first
issue.
A
A
A
A
So
well,
let's
take
a
look
at
no
that
doesn't
help
okay,
what
it
used
to
say
example
of
the
layout
for
the
for
the
ui
ux
hack,
fest,
oh
okay
notice!
Here
I
see
what
he's
saying
this:
on
the
far
right
hand,
side
may
25
through
may
29.
That
is
definitely
fixed
here.
As
far
as
I
can
tell
devops,
world
2022
is
a
multi-day
event
and
it's
well.
Maybe
all
right
so
needs
needs
investigation.
A
A
A
C
A
Yeah
see
I
I
feel
like
that
this
is
when
daniel
will
probably
have
to
be
the
one
who
phrases
it,
because
he
already
did
this
phrasing
right
and
this
improvement,
I
thought
was-
was
very
good.
It's.
What
he's
added
is
a
why
we
announced
learn
why
we
announced
this
link
to
to
these
security
advisories,
so
hey
when
we
say,
there's
no
fix
for
it,
learn
why
we
tell
you
that.
C
Yeah
yeah
psy,
okay,
how
about
the
installing
linux
page
has
now?
Where
did
it
just
go.
A
A
A
Well,
and
and
those
if,
if
you,
if
knowing
a
little
bit,
is
enough,
you
could
do
that,
we
could
just
call
those
good
first
issues.
I
think.
Oh,
oh
now,
here's
one
use
the
same
navigation
for
dev
docs.
As
for
the
user
handbook,
this
one
is
probably
complicated,
but
wow.
Would
it
be
a
great
thing
thing
to
do?
A
C
A
C
B
C
A
C
C
B
B
B
C
C
A
A
C
C
A
C
A
That
also
fits
with.
Oh
we've
got
another
one
like
that
which
is
not
expressed
as
an
issue.
Here,
that's
a
very
good
one
meg.
You
have
prompted
an
additional
one.
Let's
look
at
I'm
going
to
show
you
a
closed
pull
request
and
now
I'm
going
to
create
an
issue
to
match
this
closed,
pull
request.
We've
got
to
look
back
a
little.
There
was
a
pull
request
that
did
a
major
rework
of
the
look
and
feel
and
the
problem
was.
A
It
was
so
dramatic
that
it
broke
a
number
of
places
on
the
site
and
so
what
the
counter
proposal
from
daniel
beck
was
hey.
This
is
nice
work,
but
we
can't
have
the
site
broken.
So,
let's
split.
A
C
A
Right
so
the
idea
is,
each
change
should
be
atomic
self-contained
and
clearly
explained.
A
A
I
don't
know
which
see
the
the
challenge
for
me
is
then
you've
got
to
you've
got
to
take
it
yeah.
This
one
might
be
a
very
good
hacktoberfest
topic,
but
it's
it's
not
it's
something
that
someone
will
need
to
read
the
that
original
pull
request
and
extract
things
one
at
a
time,
piecewise
right.
So
I
I'm
it's
it's
much
more
involved
than
just
write.
Some
html
right
write
some
javascript
in
this
case
or
some
css,
but.
A
A
A
A
C
So
for
okay,
maybe
not
good
first
edition
for
a
writer
who
could
by
research,
go
back
in
and
read
the
actual
pipeline
documentation.
C
You
know
and
again
because
I
would
see
this
as
not
a
single
pr.
C
All
they're
working
for
here
is
a
t-shirt
and
a
bit
of
glory
right.
That's
correct!
I'm
wondering
if
it's
good
one
of
the
things
that
bugs
me
about
gsoc.
I
mean
for
very
good
reason,
because
there's
real
money
involved,
we
can't
ever
do
teams
and
the
idea
to
work
together
with
a
team
to
collaborate,
is
one
of
the
great
joys
and
strengths
of
open
source.
A
A
Yeah
that
that's
a
team
might
choose
to
self-organize
and
and
take
this
on.
I
think,
given
that
this
will
require
multiple
pull
requests.
I
think
that's
feasible.
I
just
don't
know
who
you
would
find
to
mentor
that
because
you'd
probably
need
somebody
to
say:
hey,
I'm
willing
to
coach
you
as
you
do
it.
A
C
A
C
A
bunch
of
little
pr's
right,
we
don't
need
to
put
it.
You
know,
could
just
put
that
as
a
j
we're
and
I
don't
think
we
want
to
get
in
the
business
of
organizing
these
teams
either.
But
when
we're
announcing
hacktoberfest,
we
could
point
out
a
couple
of
these
that
you
know
you
might
want
to
get
a
team
for.
C
A
Yeah,
so
what's
happened
is
the
search
results.
Have
the
quality
of
the
search
results
have
decreased
and
they've
decreased
because
we're
using
an
old,
older
crawler
to
do
our
content
crawling
and
algolia
has
upgraded,
but
we
haven't
made
the
changes
to
upgrade
it.
Okay,
and
this
one
is
really
one
that
it's
probably
got
to
be
done
by
either
gavin
mogan
or
me,
because
I
think
it
requires
permissions
on
the
algolia
doc
search
site.
C
True,
well,
if
somebody
I
mean
it
isn't
that
for
heck,
they
couldn't
go
in
there
and
say:
oh,
I
love
working
with
algolia
you
it's.
This
is
not
exclusive.
This
is
the
these.
Are
things
to
help
them
find
stuff,
but
they
can
go
through
and
pull
out
something
else
right
and
apply.
They
can
apply.
They
can
grab
an
issue
that
isn't
marked
for
good
first
issue
or
hacktoberfest.