►
From YouTube: 2022 02 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
A
She
code
africa,
contributon,
adding
a
troubleshooting
section,
the
switch
from
system
five
in
it
to
system
d,
a
whoops
wait
a
sec.
How
do
my
other
things
not
get
on
what?
Oh?
Yes,
that's
right,
and
that
was
one
that
this
is
one
that
needs
some
guidance
because
there's
I
wanted
to
have
a
discussion
here
in
the
group
about
about
that
specific
one,
because
it's
it's
a
structural
question.
What
other
topics
need
to
be
on
our
list
for
today?
A
Oh,
oh,
let's
see,
should
we
yeah
we've
got.
I
had
put
on
my
list
the
two
dot.
A
A
B
Yes,
one
thing
I
am
curious
about
yesterday
is:
does
jenkins,
has
any
tests
that
it
performs
like
a
normal
project
does,
and
I
think
I
know
the
answer
just
wanted
to
ask
it
anyways
test
like
yeah
like
there's
a
product,
and
I
see
it
currently
in
the
product,
I'm
working
with
so
there's
like
some
manual
regression
tests
that
are
written,
so
this
is
jenkin,
has
it
or
not,
because
yeah,
because
when
we
release
something
new
it
it
introduces
some
bugs.
So
I
was
thinking
like.
B
Why
can
we
decrease
those
bugs
so
just
want
to
discuss
on
that.
C
A
B
Okay,
a
set
of
tests
on
the
ui
just
to
see
make
sure
that
all
after
the
new
icons
are
introduced
I'll,
do
some
tests
and
see
whether
they
are
not
breaking
anywhere
or
not.
Before
releasing
it.
To
jenkins,
I
mean
to
the
public
yeah.
A
A
Okay
change,
login
upgrade
guide
is
needed
for
2.332.1,
I'm
not
ready
for
that.
Yet
so
it's
going
to
take
more
work.
The
next
opportunity
we'll
have
to
review
it
will
be
next
thursday.
I'll
probably
send
you
all
of
you
a
request
to
review
the
content
before
then
so
that
we
can.
I
can
get
your
feedback
asynchronously.
B
Yep
so
I'll
try
to
put
paint
the
picture
better
this
time,
so
there's
a
product,
let's
say,
and
it
has
some
test
cases
predefined
on
polarian
and
those
are
like
the
manual
tests
as
per
the
web
ui
that
it
has
similar
to
jenkins
it's
like
click
on
this
make
sure
this
is
seen,
and
this
is
visible.
I
mean
type
this
type
that
so
there's
like
lots
of
test
cases
now
coming
to
jenkins.
B
Does
it
have
these
test
cases
which
are,
I
think
I
know
the
answer,
but
doesn't
have
all
these
test
cases
which
are
performed
before
we
release
any
new
releases
of
jenkins
so
that
we
don't
see
some
recurring
issues
from
the
jenkins
users
and
we
tackle
them
before,
releasing
it
from
our
end,
so
yeah
so
mines.
B
A
I
think
I
think
it
does.
It
does
explain
it
and
it's
a
it's
a
this
is
a
really
fun
topic,
so
so
you've
you've
sort
of
touched
on
a
hot
button
for
me
dhiraj,
but
maybe
not
in
the
way
you
might
expect.
So
this
is
great.
So
no,
we
don't
have
those
types
of
descriptions
and
the
reason
we
don't
have
those
types
of
descriptions
is
most
of
the
time.
A
Those
types
of
descriptions
don't
actually
help
us
find
bugs,
in
many
cases
a
scripted
style
of
test,
which
is
what
you're
describing
here
and
if
you
refer
to
refer
to
james
bach,
michael
bolton,
let's
see
who
are
some
others
cam
kaner
for
the
the
surprisingly
high
cost
of
using
that
style
of
testing
compared
to
other
styles
of
testing
and
the
relatively
low
low
benefit
that's
received.
A
A
And
how
did
they
get
past
the
poll
review
process?
Yes,
so
so,
let's,
let's
talk
or
is,
is
that
sort
of
what
you're
asking
or
is
there
something
different?
You
wanted
a
guide
on.
A
A
To
detect
issues
sooner
right,
I
I
think,
is
what
you're
asking
so
2.335
had
several
bugs
in
visual
elements,
and
it's
that's
a
sort
of
a
a
first
for
us.
It's
been
a
long
time
since
we
had
that
many
bugs
and
visual
elements,
and
if
we
look
at
the
list
of
bugs
and
the
changelog
you'll
see
that
hey
this
set
here
gives
us
a
hint
of
the
kinds
of
bugs
we
had.
A
A
So
those
those
kind
of
reports,
what
could
we
do
to
to
avoid
them?
And
now
there
are
several
of
them
where
we'd
say
well,
let's
see
what
could
we
do.
A
A
A
A
It
was-
and
there
are
several
like
this
in
that-
are
that-
are
really
interesting
edge
cases,
but
but
when
we
have
300
000
installations,
edge
cases
are
everywhere
right.
So
the
reality
is
calling
it
an
edge
case
is
not
very
satisfying
because
everyone
sees
ed's
cases
because
there
are
so
many
installations.
A
So
so
calling
it
an
education
doesn't
excuse
it.
It
just
says:
okay,
that's
a
that's
a
tough
one
to
decide
how
we
would
attack
that
generally
right.
Exactly.
B
A
Now,
maybe
let's,
let's
look
at
several
more
just
to
get
a
sampling,
so
visually
right,
there's
a
visual
problem
there,
let's
look
at
another
one,
just
to
get
another
visual
thing
and
and
then
let's
talk,
maybe
okay,
so
github
organization
folders
were
not
rendered
correctly.
Now
this
one
was
very
visible
on.
If
you
had
a
let's
see
what
was
the
specific
condition,
it
was
that,
in
order
to
see
it,
you
had
to,
I
forget
the
details,
but
there
was
again
some
rather
obscure
thing.
A
However,
it
showed
up
for
get
lab,
giddy
and
git
and
github,
and
then
we
got
an
additional
report
after
336
was
fixed.
That
said,
oh
and
there's
still
a
problem
in
one
more
case
with
bitbucket
and
the
bitbucket
one
is
really
novel,
so
so
the
bitbucket
one
required
that
you
have
a
very
specific
reverse
proxy
configuration
order
to
see
it
so
so
most
interesting
now
back
to
the
question:
what
could
we
have
done
to
detect
those?
B
B
So
that
would
be
a
little
difficult
as
well
right.
Well.
A
That
one,
so
so
in
many
cases
we
need
specific
plugins
in
order
to
see
the
issue
right.
Yes,
exactly,
I
think
that's
what
you're
saying
and
so
for
that
one.
So
we
here
we
would
need
to
find
a
broken.
A
broken
image.
A
A
F
E
G
I
was
just
thinking
like
I
can
imagine
that
when
people
were
reviewing
this,
they
just
took
common
things
and
they
were
like.
Oh,
it
works
for
what
they're
used
to
seeing,
and
so
it's
probably
another
reason
why?
Because
it's
like,
even
if
you
were
visually
checking
as
a
human,
unless
you
knew
to
do
certain
types
of
cases,
you
were
probably
you
just
look
at
what
you
have
or
like
look
at
things
that
you
know
about,
and
it
rendered
I
mean
not.
Many
people
immediately
disable
a
folder
after
they
create
it.
A
G
F
A
B
A
Software
testing
ast
has
a
a
multiple
course
series
that
includes
foundations
of
let's
see
foundations.
I
think
it's.
The
first
course
bug
advocacy
is
the
second
course
so
foundations
of
software
testing
bug
advocacy.
A
Let's
see
what
else
test
design,
I
believe,
is
their
third
third
course,
and
each
of
these
is
a
six
week
intensive
course.
Just
to
give
you
a
hint,
I
flunked
bug
advocacy.
My
first
attempt
I
failed,
and
that
was
after
15
or
20
years
in
the
business.
I
still
failed
the
course.
The
first
try
so
so
they're
very
serious
about
this
particular
these
courses
and
and
they
are
really
cool,
there's
a
brilliant
book.
A
The
bug
advocacy
workbook
is
five
millimeters
thick
right,
10
millimeters
thick,
so
it's
a
thick
book
filled
with
instructions
on
how
to
do
a
good
job
of
submitting
good
bug
reports
and
that's
just
about
how
to
write
a
good
bug
report
and
when
you
report
a
bug
and
why
and
why
you
don't
report
a
bug.
So
so
it's
fascinating
and
this
the
the
the
the
whole
the
whole
thing
is,
is
just
brilliant
and
of
course,
dr
kaner
and
james
bach,
michael
bolton
and
several
others
were
involved
in
creating
it.
It's
it's
marvelous
material.
A
A
C
Said
something
about-
we
wouldn't
run
this
against
every
pr,
but
we
always
talk
about
some
tests
that
you
don't
run
against,
but
maybe
once
a
week
right
against
everything,
that's
in
master,
at
least
at
least
we
might
get
a
heads
up
on
it.
Before
I
mean
you
could
say
we
run
it
the
night
before
we
release,
but
then
that
opens
up
a
rather
large
possibility
of
getting
like
this
would
have
been
a
mess.
What
we
have
held
the
release
then
and
how
to
explain
it,
etc.
A
Yeah
and-
and
I
don't
know
that
we
would
have-
but
we
certainly
would
have-
could
have
informed
people
that
hey
this,
this
detected
it
so
that's,
I
think
it's
worth
considering,
could
consider
more
layers
of
tests.
A
So
do
some
things
only
weekly
right
right,
because
because
it's
there
there
are,
there
are
values
to
some
tests.
Some
tests
are
more
valuable
than
others,
and-
and
we
want
to
do
the
more
valuable
things
more
frequently
the
less
valuable
things
or
the
things
that
are
less
likely
to
detect
a
problem.
C
C
G
A
D
G
G
It
now
like
these
things
would
have
yeah
hindsight
20
20.
It
would
have
been
a
lot
better
to
have
it
in
place
before
we
did
a
lot
of
these
updates
and
I'm
quite
frankly,
not
sure
when
we're
gonna
do
another
overhaul
for
something
like
this,
where
we
would
run
into
these
problems,
I
mean
I
can
maybe
maybe,
if
we're
planning
on
doing
any
type
of
visual
change
like
coming
up
soon
like,
and
that
maybe
is
something
that
gets
developed
ahead
of
that.
G
So
maybe
we
just
this
is
a
learning
opportunity,
like
a
learning
that
we
take
out
of
this
and
then
do
it
the
next
time
we
decide
to
do
ui
updates,
but
I'm
just
like
me.
I
just
keep
looking
as
like.
If
it's
going
to
be
relatively
stable,
we're
putting
a
lot
of
effort
into
running
something,
that's
just
going
to
keep
returning.
A
Right
so
it
I
wonder
to
to
address
yours,
it
may
be
that
it'd
be
more
valuable.
Just
to
admit
explorers
guided
by
what
they
know
has
been
changed
in
pull.
Requests
may
be
much
faster
than
any
automation.
We
could
do
okay,
they're,
not
as
repeatable,
but
we
don't
actually
care
about
repeatability.
We
care
about
detecting
problems.
G
F
G
Yes,
I
just
like,
oh
man,
we're
taking
a
lot
of
time
and
it's
like
could
that
time
be
used
for
something
else
or
if,
like
we
do
know
that,
there's
a
massive
view
like
another
ui
effort
or
something
coming
up
with
new
icons
or
anything
else,
then
maybe
I
would
see
a
little
bit
more,
but
to
me
it's
like
now
we're
just
creating
a
whole
bunch
of
tests.
That
will
always
be
green
right
right
and
it's
and.
G
A
Yeah
and
and
that's
sort
of
why
I
was
thinking
this
thing-
would
just
look
at
everything.
It
would
admit
to
not
being
not
being
specific
to
anything
if
any
page
is
detected
with
a
broken
image.
That's
a
that's
questionable
and,
and
then
humans.
Reviewing
pull
requests
again
is,
is
nice
and
focused,
but
you're
right?
I
I
can't
see
investing
writing
specific
test
cases
even
for
these
individual
bugs.
I
really
I
look
at
those
bugs,
and
I
think
you
know
what
I
don't
get
enough
benefit
out
of
trying
to
check
for
the
existence
of
that
icon.
C
G
Right
yeah,
like
I
remember
the
jenkins
2
upgrade
like
there
was
a
lot
of
manual
testing
in
that,
because
it
was
a
lot
of
what
are
people
doing
it's
a
big
deal
right.
It's
like
that's
a
lot
going
to
be
a
lot
faster
than
any
type
of
like
test,
but
yeah
it
required
it.
That
was
just
a
massive
effort
on
the
whole,
but
it's
just
kind
of
like
a
maybe
not
something.
If
we
know
that
we're
having
ux
changes
it
might
be.
A
Happening
but
but
again,
I'm
not
sure
I
want
to
risk
slowing
down
those
rapid
improvements
they
are.
They
are
really
breathtaking
they're
doing
such
a
good
job
that
I
think
this
kind
of
breakage
for
me
is
an
acceptable
result
from
from
the
fast
movement
that
we're
making.
Yes,
it's
it's
awkward,
saying
wow.
That
was
a
bunch
of
stuff
that
was
broken,
but
one
week
later,
it's
fixed.
A
A
G
G
G
A
C
C
Strikes
me
is
how
many
pages
I
mean
if
you
told
me
to
go
and
look
at
every
web
page,
I'm
not
sure
I
would
do
it.
Oh.
A
Yes
see
my
problem
with
that
kind
of
thing
is
it's
that's
very
human-intensive,
and,
and
this
open
every
web
page
is,
is
very
much
robot
right.
It's
a
machine
can
do
should
be
able
to
conceptually
do
this,
and
and
therefore
it's
just
it's
expensive
to
run,
but
it's
still
cheaper
than
putting
10
human
beings
to
do
it.
A
A
This
is
new
and
and
during
this
transition
I
learned
a
bunch
of
things
that
I
wasn't
aware
of,
and
I
think
I'm
a
pretty
experienced,
unix
administrator,
so
so
the
the
experience
was
good.
Now
the
question
to
to
all
of
us
is
where
would
a
page
on
managing
systemd
services
belong
in
the
jenkins
documentation.
A
C
A
No,
these
are
this,
is
this
is
material
for
so
oh
a
good
point
here
we
got
viewing
logs,
so
this
one
already
will
need
a
change
and
it's
actually
got
to
change
now
for
system.
So
so
I
think
that
lobby's
in
favor
of
your
argument,
it
should
be
in
system
administration,
good,
okay,
others,
sorry,
mag.
I
interrupted
no.
B
C
I
think
we
had
that
discussion
too.
What's
the
difference
between
the
managing
and
system
administration
and
it
was
sort
of
managing,
was
supposed
to
be
more
routine
stuff
and
then
administration
was
more
sophisticated.
What
about
the
kubernetes
chapter?
Is
that
going
to
take
a
hit
from
this?
Does
this
affect
kubernetes?
Also,
it.
A
C
A
F
A
A
A
F
C
G
A
G
Was
just
copying,
what
is
this
administrating
administering
jenkins
on
kubernetes,
and
it
turns
into
is
like?
Is
this
kind
of
administering
yeah
right
there?
It's
like
is
this
administrating
jenkins
on
linux,
or
is
this
or
is
this
kind
of
more
like?
Would
it
fall
under
a
page
like
this,
as
like
a
section
on
systemd.
F
A
That's
excellent
because
thank
you
for
asking
the
question,
because
I
had
not
even
considered
the
question,
so
a
linux
administrator
could
choose
to
use
the
jenkins
war
file
and
manage
it
themselves,
either
with
a
docker
container
or
with
their
own,
their
own
setup,
without
using
system
d
at
all.
So
my
thought
was.
A
This
thing
needs
to
be
very
specific
to
system
d
and
it's
relatively
involved
because
well
because
here
all
the
different
topics
that
I
identified,
we
would
need
to
describe
in
it
just
at
first
attempt-
and
this
is
this-
is
by
someone
who's
relatively
inexperienced.
With
with
this
thing,
so
I
found
one
two
three,
four,
five,
six,
seven,
eight
eight
topics,
and
so
for
me
I
thought
you
know
what
it's
it's,
not
linux.
It
is
actually
linux
specific,
but
it's
not
the
only
way
to
do
things
on
linux.
There
are.
A
A
G
It
would
be
a
system
or
it
would
be
a
section
within
a
page
of
linux.
So
if
you
had
the
option,
you
would
be
able
to
see
it
like
I'm
almost
like
I'm
actually
kind
of
interested.
Now
it's
like.
Oh,
we
don't
have
one
for
windows,
so
you
like
come
down
that
it's
like.
Oh,
I
wonder
if
that's
like,
because
I
know
the
windows
is
a
whole
process
thing
as
well,
but
or
at
least
like.
G
Maybe
since
there's
not
a
lot
of
there's,
no,
it's
just
still
a
little
under
construction
triangle
for
the
kubernetes
one
I
didn't
know
if
like
this
is
something
that
is
like
a
okay,
I'm
on
linux.
I
click
here
and
then
here's
the
different
ways
I
can
use
it
on
linux.
A
It's
it's
a
good!
It's
a
good
question.
I
I
don't
want
to
get
into
the
into
the
discussion
of
all
the
variants
of
linux
that
they
could
do,
because
this
one
already
is
has
enough
interesting
things
in
it
that
that
need
to
be
described.
I'd
like
to
describe
one
path
and
recommend
it
and
tell
those
people
who
are
doing
exotic
stuff
like
like
this,
who
are
staying
on
system,
five
they're,
a
relatively
small
group
and
tell
them
sorry.
You're
gonna
have
to
figure
that
out
on
your
own.
A
C
C
C
G
Yeah,
it's
like,
I
guess.
The
thing
is
like
is:
is
system
d
as
a
topic
enough
alone
to
be
a
height
like
a
standalone
page,
or
is
it
like
information
that
would
be
on
another
page
yeah?
My
argument
was
like
I
think
I
I
would
see
it
personally
as
something
that's
on
it
like
on
a
page,
but
I
don't.
I
don't
care
enough.
I.
C
G
A
See
if
I
can,
if
I
can
persuade
you
why,
I
think
it's
it's
large
enough.
There's
three
examples
here.
So
here's
one
from
digitalocean
notice
the
size
of
this
scroll
bar
for
the
description
of
system
control,
so
so
this
is
systemd
on
on
digitalocean
and
they're,
not
even
an
operating
system
provider.
Now,
if
we
look
at
red
hat's
description,
page,
theirs
is
even
bigger
on
how
you
do
system
d,
so
my
my
thinking
was
wow.
C
C
Mean
is
it
again,
that's
another
little
bit
this
we
get
into
all
the
yes
right
where.
A
Right
and
and
that's,
I
think,
that's
consistent
with
our
picture
that
we
think
managing
jenkins
is
really
a
description
of
things
that
are
visible
and
directly
accessible
under
the
managed
jenkins
page
right.
So
so
configuring,
the
system
configuration,
is
code
tools,
whereas
this
one
is
relatively
niche
right
it.
This.
F
A
Good:
okay,
thanks
everybody;
okay
with
so
kristen,
I'm
I'm
like!
Oh.
A
B
So
I
spent
some
like
a
good
amount
of
time
to
understand
the
current
code
base
in
order
to
see
how
things
are
working
before
thinking
about
proposing
some
ui
related
changes,
so
so
to
do
that
in
greater
detail,
I
wanted
to
run
it
via
debugger
because
I
just
got
introduced
to
debugger
and
I
think
it's
so
cool
and
just
wanted
to
run
it
via
that
and
see
what
are
the
values
that
are
there
in
the
this?
This
variable
that
variable,
what
have
what
is
getting
fetched?
How
is
it
getting
used?
B
How
is
it
getting
stored?
So
that's
the
aim
from
my
side.
So
after
that
I'll
be
able
to
think
about
hey,
I
can
use
this
data
to
propose
this
ui
change.
So
question
is:
how
can
can
we
run
it?
Can
we
run
this
project
on
debugger
mode
on
any
ide?
Let's
say
eclipse,
because
I
tried
that
I
see
so
saw
an
error,
so
I
thought,
let's
first
discuss
maybe.
A
G
No
vsc
visual
studio
code.
A
A
G
G
Running
it
again,
but
yeah
like
a
lot
of
it
too,
like
comes
from
a
lot
of
there's
some
areas
where
it's
like
there's
the
trust
that
the
plug-in
manager
stuff
ends
up
kind
of
worked
or
like
taking
lifted
directly
from
the
plug-in
manager
code.
So.
G
That
stuff
was
like
all
right.
Well,
it
works
so
low
jenkins
stuff.
Some
of
the
information
in
there
was
a
little
a
little
hairy
like
it
was
a
lot
of
digging
through
jenkins
core
to
figure
out
what
what's
going
on,
but
yeah.
So.
A
G
G
Yeah
so
yeah,
I
got
to
look
at
that
again,
but
it's
been.
It's
been
a
couple.
It's
been
several
years
so.
C
Did
you,
but
did
you
use
visual
studio
code
to
develop
that
yeah?
How
did
you
debug
it
then.
C
G
Yeah,
so
I've
run
it.
I
basically
stood
it
up
a
whole
bunch
of
times
and
then
just
kind
of
ran,
trust
and
then
yeah.
I
did
a
lot
of
console
blog
debugging,
because
I
was
trying
to
make
output
into
a
file
or
into
like
ascii
dock
anyway.
So
a
lot
of
it
was
just
kind
of
like
what
am
I
printing
and
asking
like.
Is
this
actually
showing
up
an
ascii
dog
so
yeah
like
a
lot
of
that
type
of
situation,
but
yeah?
G
H
G
C
B
F
A
G
B
Yes,
because
I
see
that
vs
code
is
an
option
so
I'll
I
have
exp,
I
do
work
with
it,
so
I'll
try
to
run
it
on
vs
code
and
see
how
it
goes
and
then
I'll
ask
my
question
directly
on
gator
channel
on
gsoc
channel
right
great,
yes,
excellent.
A
A
One
of
the
questions
I
have
is
I'm
looking
for
mentors
during
the
africa
daylight
hours
to
help
with
some
of
these
project
ideas,
and
so,
if
you're
available,
send
me
email
or
let
me
know,
if
you're
willing
to
assist
there.
I
put
several
of
your
names
here
in
danger
mode,
saying:
okay,
I
know
meg
you,
I
think
kristen
you
as
well
had
mentored
last
year,
and
so,
if
you're
willing
again,
please
let
me
know
and
we'll
we'll
think
how
we
approach
it.
A
G
A
C
Okay,
yeah,
I'm.
I
would
be
willing
to
do
it
as
long
as
they're
doing
projects
where
they
need
a
writer
and-
and
I'm
not
doing
a
meeting
where
every
issue
is
we
wish
mark.
Was
there.
C
C
What
I
was
thinking
about
is
whether
this
troubleshooting
section
for
the
user
handle
handbook
is
a
potential
project
that
could
actually
be
done
by
a
team
of
participants,
because
I
mean
it
would
be
a
lot
of
research
and
trying-
and
you
know
talking
to
people,
you
know
it
would
be
a
chance
to
learn
a
lot
of
good
documentation,
skills
and
there's
so
much
there
and
it.
I
did
get
the
impression
from
our
participants
last
year
that
a
lot
of
them
might
have
been
more
comfortable
working
in
a
team.
C
C
But
everything
we
do
now
is
individual
things,
and
that
might
be
you
know
and
then,
of
course,
the
problem
with
them
is
when
one
of
one
of
we
have
three
people
on
it,
one
of
them
bails
out,
do
the
other
two
get
hurt,
but
but
if
they.
A
A
C
A
C
There
as
a
possibility-
and
nobody
applies
for
it-
we
have
we're
not
any
farther
behind
than
we
are
now
with
it.