►
From YouTube: 2022 05 24 Inclusive Naming
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
Now.
Those
for
me
are
just
general
purpose,
and
so
I
think
they're
less
interesting
than
if
we
talk
to
the
specifics
for
you
as
individuals
and
and
I
think
actually,
your
individual
interests
can
be
of
more
benefit
to
to
open
source
projects
than
if
you
attempt
to
contribute
some
sort
of
generically.
I
became
well.
I
became
a
maintainer
of
the
git
plug-in
because
I
was
personally
interested
in
making
sure
it
didn't
have
bugs
and,
and
that
maintained,
maintaining
turned
into
a
very
helpful
thing
for
me
for
my
company
and
ultimately
for
me
professionally.
A
A
And
test
processes,
so
you,
when
you
submitted
a
change
at
least
a
few
of
the
changes,
caused
the
continuous
integration
process
that
was
supporting
that
to
break
oh
well,
hey,
there's
something
new!
You
made
a
change,
it
was
immediately
tested
and
that
immediate
testing
told
you
oh
hey.
This
is
a
problem
because
of
this
change.
So
that's
continuous
integration,
continuous
delivery,
those
kind
of
things.
A
A
C
Okay,
what
I
find
interesting
at
the
moment
is
the
documentation
side
of
it
because
well,
when
I'm
building
software,
I
really
just
have
to
respond
to
documentation.
C
A
C
Well,
currently,
I'd
say
I
I
don't
know
if
it's
I
don't
know
whether
it's
genetic
but
really
it's
the
whole
build
process
of
of
building
features,
adding
them
to
existing
software
yeah.
Those
mainly
those
two
things.
A
Okay,
adding
new
features
to
existing
software,
good,
very
good,
okay,
all
right!
Well,
so,
let's,
if
you're,
okay
with
it,
I'm
gonna,
take
and
I'm
gonna
sort
of
try
to
time
limit
myself
to
not
spend
more
than
five
minutes,
because
then
we're
gonna
switch
and
we're
gonna.
Ask
the
same
question
to
peace,
spend
five
minutes
on
it
and
then
ask
the
same
question
to
nafisa
and
spend
five
minutes
there.
A
So
I
don't
wanna,
I
don't
wanna
spend
a
lot
of
time
on
each
because
most
of
these
I
could
bore
you
for
a
very
long
time
and
I
could
talk
an
awful
lot
and
not
help
a
lot.
So,
let's
so,
let's
talk
about
documentation
cycles,
if
you're,
okay,
with
that
and
we'll
spend
I'll,
try
to
spend
roughly
half
the
time
on
documentation
and
half
on
build
process
and
how
you
could
help
in
an
open
source
project.
A
It
has,
let's
see
some
other
examples.
Oh
it's
got
yeah,
it's
got
developer,
documentation,
it's
got
developer,
tutorials.
A
Now
any
one
of
those
things
you
can
find
weaknesses
just
on
this
primary
website
where
oh
this,
this
thing
is
not
adequate,
or
this
thing
is
not
adequate
or
some
aspect
of
this
thing
is
not
adequate,
and
each
of
those
would
be
a
significant
contribution
where
you
would
learn
something
about,
in
this
case,
the
implementation,
language,
asciidoc
and
the
implementation
structures
that
are
being
used.
The
way
the
site
is
constructed,
how
its
content
is
organized,
etc.
A
A
So
each
of
those
is
is
sort
of
small
examples.
Now
now
you
may
say:
oh,
but
I'm
not
interested
in
the
primary
website
or
or
plugins
I'm
more
interested
in
documentation
as
it
relates
to
infrastructure.
Jenkins
infrastructure
is
maintained
in
public
repositories
and
needs
documentation
for
things
like
run
books.
A
run
book
is
a
set
of
instructions
to
guide
someone
how
to
perform
specific
tasks.
A
Structural
discussion
descriptions
how
things
work
together.
What
relies
on
on
what
that
kind
of
thing?
A
C
Yeah,
what's
what's
of
interest
me
is:
is
especially
the
user
documentation,
developer
and
api
documentation,
because
I
already
know
how
to
do
the
tutorials
and
blog
posts
yeah.
So
the
documentation
of
the
technical
side
of
it
is
what
I'd
be
interested
in.
A
Good,
okay,
well
so
yeah.
So
then,
let's,
let's
spend
just
a
minute
on
a
little
deeper
dive.
I'm
going
to
take
just
one
of
those,
this
api
reference
documentation
and
let's
look
at
on
the
jenkins
website.
As
part
of
google
summer
of
code,
we
had
a
project
that
was
proposed.
It
wasn't
this
one
ultimately
was
not
accepted,
but
this
automatic
specification
generator
for
the
jenkins
rest.
Api
was
a
project
proposal
that
came
in,
and
I
think,
if
we
look,
we
can
also
see
in
2022.
A
Yes,
here
it
is
good.
So
what
this
is
saying
is
hey
the
jenkins
rest.
Api
really
would
benefit
by
having
a
a
generated
document
that
describes
its
endpoints,
what
they
are,
how
they
respond,
etc,
and
there
are
many
many
of
them,
so
it
needs
to
be
automated.
So
this
is
a
project
idea
that
you
could
review
and
say
hey.
This
gives
suggestions.
A
And
now,
just
to
give
you
some
of
the
scary
factor
of
it,
this
was
assumed
to
be
based
on
our
initial
estimates,
at
least
175
hours
of
work,
and
you
may
say
I
can't
do
175
hour
project.
Then
you
might
look
at
one
of
these
new,
these
friendly
issues
and
say,
okay,
what?
If
what?
If
I
took
just
a
small
issue
like
how
to
improve
the
rest
api
documentation
for
one
of
these
plugins?
That's
described
here,
something
like
that
and
that
kind
of
thing.
C
A
A
And
again,
what
is
this
highlighting
there's?
There
are
interesting
things
to
be
done
in
in
that
area.
Now
we've
hit
my
five
minute
limit.
Are
you
okay?
If
I
shift
gears
catherine
and
we
may
come
back
to
the
adding
new
features,
the
build
process
and
adding
new
features
to
software?
If
that's
okay,.
A
B
Actually,
what
I
find
interesting
is
similar
to
what
catrin
said,
especially
the
documenting
apis.
I
find
documenty
api's
interest
thing.
I
find
creating
build
process,
thinking,
organizing
making
edits
and
creating
pool
requests.
Those
are
the
things
I
find
interesting.
A
A
So
since
we've
talked
about
documenting
apis,
maybe
we
take
your
suggestion:
let's
take
creating
build
processes
and
we'll
see.
If
I
can
give
you
some
some
ideas
of
ways,
you
can
contribute
there
and
then
then,
if
that's
that's
good,
we'll
continue
with
the
next
is
that
okay,
if
we
do
creating
build
processes,
then
yes,
okay,
all
right!
So
let's,
let's
look
at
some
places
where,
where
jenkins
has
jenkins
at
multiple
levels,.
A
A
I
don't
know
how
you
would
maybe,
let's
just
call
it
jenkins,
build
tools
and
then
jenkins
infrastructure,
and
each
of
these
has
places
where,
where
you
could
be
involved
in
a
build
process,
that
might
you
might
find
interesting.
So
as
one
example
jenkins,
core
delivers,
weekly
releases.
A
A
A
This
is,
and
let
me
get
here
we're
going
to
bring
it
up
so
that
you
can
see
it.
So
here
is
the
lts
checklist
that
has
been
started
for
the
next
jenkins
lts.
It
will
be
released
in
june
of
2022,
and
this
this
person,
alexander
brandis,
has
agreed
to
be
the
release
lead
under
the
guidance
of
our
release,
officer,
tim
jacom.
A
And
the
release
lead
assures
that
the
checklist
is
done.
There
are
a
number
of
relatively
interesting
technical
challenges
here.
This,
for
instance,
create
the
pull
request.
Oops
create
the
pull
request.
Where
is
it
back
porting?
Here
we
go
this
one
open
the
back,
porting
pull
request,
which
means
you
have
to
know
what
should
be
backported
you've
got
community
agreement
on
it.
So
there's
a
coordination
effort
that
happens
happens
here
and
conversation
this.
This
is
not
uncommon,
actually
also
in
large
corporations.
A
Where
deciding
to
do
a
release,
we
need
to
discuss
what
should
be
in
the
release
and
what
shouldn't
and
so
practicing
by
being
a
release
lead
for
a
jenkins
release.
Helps
you
get
ready
for
employment,
where
you
might
do
these
same
kinds
of
things
negotiating
what
should
be
in
the
release
and
what
shouldn't.
A
A
A
C
A
Well,
and
thank
you
for
being
thank
you
very
much
for
for
being
part
of
this,
and
I
think
I
think
there
is
much
for
us
all
of
us
to
learn
as
we
do
these
kind
of
things
right.
There
are
so
many
things
that
that
we
learn
about
this
that
we
can
also
then
apply
professionally.
Oh,
you
know
what
this
is
like,
what
we
did
in
the
jenkins
project
or
oh.
This
is
like
how
I
did
in
this
other
project.
I
was
helping.
I
helped
them,
and
what
do
you
know?
C
A
Oh,
absolutely
yes,
okay,
yeah!
Well,
okay!
Oh
that's!
You
know
what
I'm
gonna
go
back
now.
You've
you've
raised
a
very
good
question,
catherine.
That
is
that
you
that
I
I
have
to
go
back
for
this
one.
So
we
were
talking
about
documentation,
cycle
right
and-
and
all
I
talked
about
is
the
places
you
could
help.
But
what
I
didn't
didn't
mention
was
the
fact
that
there
are
people
who
would
love
to
encourage
you,
as
you
help
and,
and
that's
probably
even
more
important
than
the
places
right.
So
jenkins
has
documentation
office
hours.
A
I
should
not
be
continent-centric
there.
That's
not
fair
one
time
wondering
in
time
for
asia
and
western
u.s,
and
what
you
could
do
if
you'd
like
to
be
involved,
is
just
join
those
meetings.
A
And
let
me
put
a
link
to
their
page
because,
because
the
jenkins
documentation
office
hours
they're
mentioned
on
the
oh
here,
let's
just
go
this
way
jenkins
and
we're
going
to
look
in
sub
projects.
Nope
community
documentation,
the
special
interest
group-
and
it's
got
an
office
hours
link
here.
That
tells
you
when
they
meet
and
where
you
can
find
the
recordings
and
where
you
can
find
the
documentation
that
we
use
to
track
it.
So
our
next
meeting
is
this
thursday,
europe
time
this
friday,
asia
time.
A
B
A
A
A
Rpm
for
red
hat
and
others
like
open,
susie,.
A
And,
of
course,
the
the
root
of
them
all
is
the
war
file
which
is
done
with
java.
So
maybe
you
want
to
learn
something
about
how
the
packaging
works,
and
this
is
a
great
place
to
contribute.
Oh
one,
more
docker
for
containers.
A
A
Now
onward
to
plugins
and
modules,
so
if
you
choose
to
you
may
say
you
know
what
jenkins
core
is
big
and
kind
of
scary.
I'm
not
sure
I'm
ready
to
contribute
to
jenkins
core,
because
it's
so
big,
but
I
want
to
find
a
plug-in
they're
fairly
small.
A
A
See
if
we've
got
oh
here,
I
have
to
find
it
a
different
way.
So,
let's
see
apache
this
one,
this
little
plugin
says
it
is
up
for
adoption,
and
so,
if
I
click
this
label
adopt
this
plugin.
What
I
see
here
is
there
are
108
plugins
in
the
jenkins
plugin
set
108
of
the
1800
plugins
that
are
up
for
adoption.
A
You
may
say:
wow,
okay!
Well,
I'm
interested
in
maybe
you're
a
get
lab
user.
Okay,
git
lab
plugin
is
up
for
adoption.
Maybe
you're
you
say:
oh
no,
these
things
at
the
top
of
this
list.
There
are
lots
of
people
who
use
this
so,
for
instance,
this
one
that
I
just
opened
is
installed
at
almost
300
000
jenkins
controllers.
You
may
say
that's
too
big
for
me,
I'm
nervous
about
that.
Okay,
let's
take
something
small.
A
You
could
you
could
offer
to
adopt
that
one
others
like,
let's
see
what
are
some
I
recently
adopted
and
not
too
long
ago,
here's
one
port
allocator,
this
one's
a
fun
one,
because
maybe
you
have
a
specific
problem
where
you
say
I'm
working
on
something
I
need
to
to
improve
and
it
needs
to
allocate
a
port.
So
I
can
start
a
service
on
a
port.
A
That's
free,
and
this
thing
actually
does
that
for
you,
it
will
help
you
find
a
free,
tcp
port
on
your
jenkins
controller
in
case
you
need
to
use
it,
and
so
you
could
say
wow,
I'm
going
to
adopt
this.
Well
guess
what
you
get
to
learn
something
about
security,
because
this
plug-in
has
a
problem
that
needs
to
be
fixed.
A
A
A
And
that's
maintained
by
jenkins,
and
so
it
needs
it
may
need
enhancements.
Java
11
changes
in
the
build
tools
are
in
progress
right
now,
java
17
support
if
you're
interested
in
oh,
I
want
to
learn
something
about
new
versions
of
java.
A
A
So
when
I
go
here
to
manage
jenkins
manage
plugins-
and
I
see
this
very
attractive,
little
number
three,
that
number
three
says
there
are
three
plugins
that
are
have
newer
versions
on
my
jenkins
controller
than
are
on
my
then
are
installed.
So
this
one
needs
an
update.
This
one
needs
an
update
and
this
one
needs
an
update.
A
A
A
A
Okay
good,
so
so,
let's,
let's
talk
briefly
about
what
this
thing's
concept
is
because
it's
what?
Where
did
it
start
and
why
so
in
at
devops
world
2021,
I
did
a
workshop
called
contributing
to
open
source
and
as
part
of
that,
in
this
one
hour
workshop,
I
was
trying
to
persuade
people
why
they
should
help
open
source
projects,
in
this
case
jenkins
by
adopting
a
plugin,
and
so
what
this
does.
Is
it
takes
them
through?
Okay,
what
do
you
need
to
do
to
install
your
your
java,
11
development,
environment,
your
git,
maven,
etc?
A
A
I
can
do
one
thing
and
then
I
could
step
away
from
it
and
go
back
to
doing
other
things
and
it's
valuable.
So
it's
this
is
sort
of
the
sweet
spot
for
me
in
trying
to
find
ways
to
help
open
source
projects.
I
want
something
that
is
interesting
to
me,
small
enough,
that
I
can
accomplish
it
relatively
quickly
but
useful
to
the
project
that
I'm
submitting
it
to,
and
so
these
things
are
specifically
in
that
kind
of
area
where
you
say
hey.
If
a
jenkins
plugin
doesn't
already
have
a
jenkins
file.
A
A
So
it
says
in
that
one
liner.
We
put
that
in
build
plug-in
now
most
jenkins
plug-ins,
thankfully
now
have
this
already,
so
most
don't
need
it.
But
if
you
find
a
plug-in,
that's
interesting
to
you,
this
is
a
great
first
thing
to
do
and
it's
very
low
cost.
You
just
create
a
file
named
jenkins
file.
It
has
one
line
in
it:
build
plug-in.
A
Now,
if
we,
if
we
say
okay,
what
what
else?
That's
that's
done,
but
then
there
are
plenty
of
other
things
like
again
this
one
update
the
parent
palm
the
jenkins
build
process,
uses
maven
and
maven
uses.
This
thing
called
a
project
object
model
pom,
so
the
project
object
model,
the
palm
uses
a
specific
version
of
its
parent
and
very
frequently
that
parent
has
developed
newer
versions.
Newer
versions
have
been
released
and
the
plugin
is
not
using
those
newer
versions
and
the
newer
versions
have
new
capabilities
new
enhancements.
A
A
Oh,
I
need
to
do
this,
or
I
need
to
do
that,
because
updating
the
parent
palm
exposed
a
new
set
of
checks.
It
brought
in
a
new
set
of
rules
about
what
can
and
cannot
be
included
in
this
plugin
and
the
plugin
was
not
complying
with
those
rules.
So
you
may,
as
part
of
updating
the
parent
palm,
also
need
to
change
some
source
code
so
that
the
new
parent
palm
can
be
used
so
again,
add
a
jenkins
file
and
update
the
parent
palm
both
pretty
simple
things
to
do:
update
the
parent
palm.
A
A
With
this
now,
what
am
I
doing?
I'm
learning
about
maven
compilation.
This
will
run
automated
tests.
If
some
of
them
fail
now
I've
got
to
investigate
test
failures.
Then
I'm
going
to
commit
it
and
push
the
change,
create
a
pull
request
and-
and
I've
now,
with
two
simple
changes-
been
able
to
improve
the
plug-in
and
learn
something
myself
now.
A
The
other
changes
here,
for
instance,
the
base
jenkins
version
there
when
we
create
a
plug-in,
we
also
say
what
minimum
jenkins
version
is
it
supported
on,
and
that
needs
to
be
updated
periodically,
because
the
jenkins
project
does
not
support
really
old
jenkins
versions.
So
there's
no
reason
for
me
to
be
building
based
on
those
old
versions.
A
A
This
one
spot
bugs
will
teach
you
about
static
analysis.
Looking
for
bugs
that
a
program
can
detect
in
other
programs,
so
spot
bugs
is,
is
a
great
thing
to
use.
If
you're
doing
java
development
professionally,
you
absolutely
should
enable
spot
bugs
because
it
will
help
you
find
things
that
you
might
have
missed,
but
the
program
can
find
for
you.
A
Excellent
question
spot
bug
specifically
does
not,
but
there
are
other
tools
that
do
perform.
So
what
what
spot
bugs
is
doing
is
it's?
It's
a
form
of
analysis
called
static
analysis
and
what
static
analysis
is.
Is
it's
a
program
running
to
inspect
the
source
code
of
other
programs,
and
so
there
are
javascript
static
analysis
for
react.
A
And
let's
see
what
what
this
search
shows
us,
so
here
we
go.
Here's
one
locastic
offers
something
11
tools
to
help
you
catch
errors,
so
log
rocket
gives
us
gives
us
this,
and
so
here
are
several
that
eslint.
This
one
is
used
in
the
jenkins
project
prettier
this
one's
used
in
the
jenkins
project,
others,
I
I
think
I've
seen
some
js
hint.
I've
definitely
seen
pmd
I've
seen
yeah
I've
seen
somebody
use
lgtm.
I've
definitely
seen
use
of
sonar
cloud
and
we
use
that
depend
about
all
the
time
so
so
yeah
they.
A
A
So
back
to
the
notion
that
if
you're
interested
in
software
development
you'll
learn
things
by
contributing
to
open
source
that
you
then
apply
in
your
in
your
professional
environment,
where,
oh,
you
know,
what
static
analysis
can
help
me
write
better
programs,
because
any
bug
that
a
another
program
finds
in
my
program
is
a
bug
I
didn't
have
to
find
myself.
So
why
not.
A
A
Others
who,
for
whom
english
is
not
their
native
language,
need
us
to
internationalize
and
then
translate
and
and
the
techniques
to
do
that
are
both
interesting,
common
and
a
lot
of
work
so
where
we
just
started
effort
in
the
jenkins
project
to
do
a
better
job
of
internationalizing
and
localizing
and
part
of
that
has
led
us
to
a
a
company
called
crowdin
has
donated
a
service
that
they
host
for
jenkins.
The
jenkins
project
called
crowdin.jenkins.io,
and
this
thing
helps
people
contribute
translations.
A
So
here
we
see
well
look
at
this.
We've
got
multiple
contributors
to
every
single
one
of
these
projects,
and
if
we
look
at
a
plug-in
that
I
maintain
here,
you
see
chris
stern
submitted
the
simplified
chinese
and
the
traditional
chinese
translation.
Bruno
veractin
contributed
the
french
alexander
brandes,
the
german
and
ofato
italiano.
So
I
did
the
italian.
Yes,
I'm
not
really
good.
At
italian,
but
I'm
adequate,
so
here's
another
place
where,
before
any
of
this
could
happen,
I
had
to
internationalize
the
elastic
access
plug-in
so
that
these
people
could
then
provide
translation.
A
So
these
kinds
of
ideas,
now
this
whole
stack
of
things,
improve
the
plug-in
with
pull
requests.
All
of
these
things
can
be
done
without
ever
being
a
plug-in
maintainer.
You
could
pick
one
of
them
and
work
on
it,
and
that
would
be
it
no
requirement.
You
didn't
make
any
longer-term
commitment,
but
now,
maybe
you
say
hey
you
know
what
this
plug-in
has
been
interesting
enough
to
me.
I
want
to
maintain
it
well,
then
there
are
yet
these
other
things
you
can
do.
A
C
You
well
for
me,
I'd
like
to
explore
all
these
aspects,
especially
in
regards
to
jenkins,
because
I
feel
like
I'll
uncover
aspects
that
I've
not
encountered
before,
which
is
then
that
that's
the
time
I'll
get
clearer
questions,
but
right
now,
right
now
it
feels
like
we've
explored
at
a
higher
level
and
yeah.
It
needs
more
time
to
digest
everything
you
it's
great.
We've
talked
about
here,
yeah.
A
Maybe
I
go
out
all
the
way
out
to
the
very
tail
end
of
it
and
look
at
which
which
of
these
might
be
interesting
to
me.
So
if
I
look
a
little
bit,
I'm
actually
interested
in
software
configuration
management,
scm,
and
so
this
one
might
be
interesting
to
me
file
system
scm,
but
you
might
be
interested
in
software
test
reporting,
so
test
link
might
be
interesting
to
you
or
you
might
be
interested
in
static
analysis
like
java,
ncss
and
and
okay.
A
C
Okay,
so
I
have
a
question
right
now:
I'm
working
on
an
e-commerce
application
which
requires,
of
course
using
a
couple
of
plugins
when
integrating
some
features.
So
are
there
plugins
that
relate
to
that
e-commerce?
Realm.
A
C
Yeah
because
I've
seen
some
there's
some
aspects
where
you
need
to
integrate
like
payments,
you
need
to
integrate
shipping
and
you
need
to
use
plugins,
for
that.
So
does
jenkins
have
such
plugins
that
are
used
for
that.
A
A
A
A
A
C
A
C
Okay-
well
I'll
not
be
available
this
week,
I'll
probably
next
start
next
week,
but
I'm
sure
we'll
meet
somewhere
within
the
jenkins
universe.