►
From YouTube: 2022 04 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
Welcome
it's
april
the
8th
2022,
and
this
is
jenkins,
documentation,
office
hours
agenda.
We've
got
news,
she
code,
africa,
contributon,
google,
summer
of
code,
and
I
had
something
on
weekly
changelog
process,
but
I
don't
think
we
need
anything
on
that
make
any
other
topics
you
want
to
put
on
the
list
that
does
it
for
me
sounds
good
okay.
A
So,
by
way
of
news,
oh
a
good
one,
she
could
africa
has
started
started
april
5th,
we're
in
the
two-week
period
for
community
bonding,
so
getting
to
know
each
other
understanding
the
project
talking
about
how
we'll
deal
with
each
other
preparing
blog
posts,
those
kind
of
things
and.
A
Correct
last
year
we
did
four
weeks
started
and
stopped
and
boom
and
and
this
year
we're
making
sure
that
they're
configured
ready
to
do
the
work
that
they're
introduced
to
the
team.
That
they've
had
some
introductory
training
those
kind
of
things
well
before
we
actually
start
the
official
work,
excellent.
C
A
A
Now
there
are
our
detailed
notes
in
the
meeting
notes
from
our
meeting
earlier,
so
the
meeting
that
was
yesterday
in
calendar
time
has
a
bunch
of
notes
on
things
that
we
described
took
them
through
a
tour
of
the
two
of
the
contributor
two
of
the
chico
africa
women
that
were
there.
We
talked
about
the
steps
they
do
to
download
and
run
jenkins,
create
a
github
account,
create
an
account
on
gitpod.io
so
that
they
can
do
video.
They
can
do
website
development
and
there's
this
tutorial.
A
A
These
are
the
people
nope
I
closed
the
sheet.
Maybe
I
hit
it
away.
So
what
I've
got
is
a
worksheet
that
lists
every
plugin
sorted
by
installation
count,
and
then
I
assigned
15
of
them
to
the
first
person
piece
of
okafor
and
15
to
the
second
catherine
quito
and
kiru,
and
then
we
alternate
back
and
forth
and
what
I
was
just
doing
was
doing
some
sanity
checking,
searches,
looking
for
inclusive
naming
failures
in
those
and
in
each
in
the
first
two
or
three
blocks
of
15
that
I
checked.
A
C
A
So
those
are,
those
are
good
things
and
many
of
them
have
been
solved
right.
Many
of
them
are
there
there's
no
reference
to
slave
or
no
reference
to
master
and,
and
so
that's
good-
that's
a
win,
but
having
just
found
a
few
that
says
this
exercise
of
having
them
go
through,
it
is
valuable.
It
will
help
us
weed
out
those
last
few
remaining
things,
even
in
those
high-volume,
plug-ins,
yep
excellent.
A
So
that's
really
the
topic
I
had
there,
then
for
google
summer
of
code,
we've
got
ongoing.
Reviews
of
projects
are
needed,
plans
are
needed,
of
proposals
are
needed
and
due
by
april
9,
so
that
the
candidates
can
refine
and
submit.
A
In
time
for
the
deadline
which
is
april
19th,
I
recall
correctly.
A
We
have
we
have
three
or
four,
or
maybe
five-
that
are
all
being
actively
reviewed
on
different
different
topics:
two
that
are
very
active
on
the
get
get
idea,
idea
two
that
are
very
active,
two
or
three
that
are
active
on
another
one
and
then
the
plug-in
health
topic.
We've
got
one
very
serious
one.
So
it's
it's
looking,
okay,.
C
A
A
So
good
question:
let's
put
open
pr's
there.
I
think.
That's
what
you're
talking
about
right
so
mark
still
has
not
negotiated,
has
not
made
the
trade
with
the
security
team
for
some
of
their
time.
So
I'll
I'll
talk
with
them.
It
may
not
be
tomorrow,
but
I
hope
to
talk
with
them
before
before
we
meet
next
week.
Yeah.