►
From YouTube: 2022 04 26 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
Welcome
to
the
inclusive
naming
project,
it's
our
weekly
planning
meeting.
This
is
the
26th
of
april,
thanks
for
being
here.
So
two
topics
I
had
on
the
agenda
were:
let's
talk
about
how
the
google
sheet
is
doing
and
how
your,
how
your
feeling
is
about
what
you're,
seeing
what
you're
exploring
etc.
So
I
think
we
should
make
most
of
this
session
focused
piece
on
how
to
help
you
and
catherine
how
to
help
you
to
be
sure
that
you're
comfortable
and
confident
and
are
able
to
start
making
progress
ready
to
submit
pull
requests.
A
B
Yes
mark
good
evening
hi
peace,
hi
mark
I
had
issues,
I
don't
know
if
it's
an
issue,
but
I
was
it's.
It
was
somehow
to
me
like
when
I
tried
when
I
a
plugin
when
I
searched
for
master
in
github
with
the
fox
plugin.
It's
not
going
to
show
anything,
but
when
I
search
for
master
with
the
original
plugin,
it's
going
to
show
me
a
list
of
technologies
that
requires
changes.
I
don't
know
why
it's
like
that.
A
B
Yeah
when
I
fought
in
the
original
represent
repository
in
in
my
own,
in
my
own
repository
when
I
search
for
master,
it's
not
going
to
show
me
any
technology
error,
but
when
I
go
to
the
original
repository
and
search
for
that
same
master,
I'm
going
to
see
a
list
of
technology
errors.
There.
A
A
Indexing
may
be
delayed
until
sometime
after
the
fork
is
created.
So
how
long?
I
assume
that
there
was
very
short
time
between
the
time
you
created
the
fork
and
the
time
you
did
the
search.
A
B
For
months
for
on
the
original
repository,
it's
going
to
show
some
master
technologies
that
needs
changes,
but
when
I
search
for
it
on
my
own
on
my
own
repository,
I'm
not
going
to
say
anything.
A
A
A
This
plug-in
is
listed
as
a
fork
from
a
long
ago,
plug-in
it's
long
long
ago
right
and
that
plug-in
was
was
hasn't,
been
maintained
in
many
years.
The
the
thing
that
from
which
it
was
forked.
So
now,
if
let's
try,
what
what
could
I
search
for?
That
would
be
a
good
check.
How
about?
Let's
find
a
word
that
we
know
exists
here
like
how
about
like
linux,
there's
a
there's,
a
word
that
we
know
exists?
A
C
A
From
the
upstream,
this
is
even
archived,
I
don't
even
know
if
it
includes
the
words
word
linux
anywhere.
Let's
see
if
it
does
how
about
in
how
about?
Let's
search
for
patched,
because
we
know
that
word
exists.
A
A
C
Interrupt
that
very
interesting,
because
the
other
day
when
I
was
trying
to
do
a
translation
for
jenkins,
one
of
the
helpers
on
the
communityjenkins.io
told
me
should
make
a
search
within
github.
You
know
on
the
jenkins
so
that
you
will
find
the
sentence
you
are
trying
to
translate
and
I
never
found
the
the
sentence
I
was
looking
for.
I
was
pretty
puzzled
and
I
thought
that
was
because
I
was
not
a
member
of
the
gentinky
community
on
github
and
I
was
totally
wrong
now.
C
I
suppose
that,
because
it
was
a
fork
from
another
repository
so
that
the
search
wasn't
working
for
me,
that's
maybe
the
reason
why
it
wasn't
working
wow
amazing.
Thank
you.
A
Peace,
peace.
Thank
you
very
much
for
being
so
observant,
so
so
excellent
thing,
great
work.
So
now
what
do
we
do
about
it
right?
So
how
do
we?
How
do
we
get
you
to
the
point
where
you
can?
Let's,
let's
look
at
some
of
the
sheets,
so,
let's
see
just
how
common
this
is.
So
I'm
going
to
open
up
scm
api.
A
And
if
I
go
to
its
github
repository,
it
is
not
forked.
So
here,
if
I
look
for,
I
bet,
linux
will
be
included
here
here.
It
does
a
correct
search
so
so,
when
it's
not
been
when
it's
not
listed
as
forked
from
another
repository,
it's
okay.
But
now,
if
I
look
at
my
fork
of
this,
let's
just
prove
it
to
show
that
peace
has
shown
us
a
behavior
of
of
github
that
I
didn't
didn't,
know:
okay,
I'm
going
to
search
for
linux.
Here.
A
A
So
so,
okay,
for
in
your
case
many
of
them
that'll
be
easy
enough.
You
just
remember
to
do
it
in
the
upstream
right
in
the
jenkins
ci
repository
like
this
one
and
and
these
two
that
I
just
checked
are
both
okay.
That
way,
however,
if
your
task
is
to
search
the
git
plug-in
you're
stuck
if
you
can't
use
github
search
facility
to
go,
find
it
in
here,
you're
gonna
have
to
use
a
different
method,
and-
and
that's
where
the
different
method,
I
apologize
for
how
how
awful
this
different
method
I'm
going
to
show
you
is.
A
But
if
you're,
okay,
I'm
going
to
show
you
this
different
method
and
and
that
way
you
know
how
to
use
it.
When
you
get
exactly
this
problem,
so
what
you
do
is
create
your
local
copy
of
it
and
use.
I
could
either
open
it
with
github,
desktop
or
open
it
with
visual
studio.
I
could
even
download
the
zip
for
me
it's
just
easier
if
I
do
a
git
clone,
so
I'm
going
to
bring
up
my.
A
A
A
Okay,
now
that's
interest,
oh
right,
I'm
in
the
jenkins
ci
repository,
so
it
found
them
good.
Now!
Oh,
no!
That's
interesting!
Okay,
so
that
that
tells
me
that
it
did
find
it
even
though
I'm
in
a
oh,
no,
no
wait
a
sec
yeah!
So,
okay!
Now
I
can't
explain
it
because
the
fork
I'm
in
a
fork,
but
when
I
searched
for
master
it
found
things
I
don't
get
it
me
neither
okay!
So
let's
go
to
my
fork
now,
just
in
case
so
switching
to
my
fork.
A
C
Sorry
to
interrupt
just
maybe
a
silly
idea
could
it
be
because
the
repository
has
been
archived.
A
A
If
I
click
here,
the
upstream
has
been
made
read-only
because
the
author
is
no
longer
doing
anything
with
it.
What
if
we
choose
another
one
that
doesn't
have
an
archived
upstream,
do
you
have
a
do?
You
have
a
suggested
repository
bruno
that
we
could
use,
or
should
I
just
go
exploring
to
find
one?
No,
sorry!
No
okay!
So
let's
try
get
client
see
if
it's
got
no
okay.
How
about?
Oh!
I
know
one
that
does
elastic
access.
A
Okay,
this
one
is
forked
from
toxons
and
toxons
is
not
is
not
archived.
Now,
let's
choose
a
some
interesting
word
like
coverage.
A
A
A
A
Oh,
oh,
has
not
been
indexed
okay,
so
that's
a
different
thing
all
right,
so
so
it's
probable
that
they
have
scheduled
an
indexing
operation
just
to
okay.
So
again
it
may
be.
We
have
to
be
aware
of
that
message.
Glad
you
caught
that
bruno.
This
hints
that
okay,
it's
not
indexed,
therefore
they're
probably
indexing
it.
Since
I
asked
for
it
now,
let's
go
back
to
the
to
the
to
the
original
one.
This
one
did.
It
say
the
same
thing.
If
I
search
for
the
word
configuration
does
it
say
it's
not
indexed.
A
C
A
A
A
Code
right
right,
so
it
did
not
find-
and
here
it
says
it.
Okay,
there's.
I
thought
I'd
seen
this
message
before
so
peace.
You
have.
You
have
shown
us
that,
in
fact,
what
they
say
here
is
correct.
Forked
repositories
are
not
currently
searchable.
Try
searching
the
parent.
A
So
so,
if
we've
got,
if
you've
got
repositories
in
our
list
that
have
a
parent
that
is
outside
jenkins,
then
you'll
have
to
use
this
other
technique
to
do.
The
search
you'll
have
to
use,
get
grep
peace.
Did
that
did
that
answer
your
question?
Are
you,
okay,
with
us,
we've
now
spent
like
10
minutes,
trying
to
prove
to
ourselves
what's
going
on?
Is
this
okay?
How
how
you've
seen
it
so
far.
B
The
reason
is
because,
while
you
were
showing
well,
you
were
doing
something
like
that.
My
necks
were
disconnected,
so
I'm
trying
to
oh.
A
Well,
if
you're,
okay
with
it,
let's
go
through
it
again
and
that
way
we've
got
it
in
the
recording
and
and
we're
sure
that
you've
you've
seen
what
what
what
the
what
the
message
is.
I
think
bruno
and
I
have
thanks
to
his
insights
and
some
luck.
We've
we've
decoded
what's
happening
so
so,
let's
talk
through
it,
and
this
will
give
you
some
insights
into
how
github
thinks
about
repositories
first
and
what
they
do
index
and
what
they
don't.
A
Okay,
okay,
so
so,
let's
take
a
plug-in
from
our
list
like
the
scm
api
plug-in-
and
here
is
its
github
repository
notice-
that
it
doesn't
have
any
text
right
below
it.
That
says
forked
from
something
it's
its
own
root
level
repository,
and
so,
when
I
search
in
it
for
the
word
linux,
it
will
find
code
matches
for
linux.
A
Now,
if
I,
if
I
look
at
my
fork
of
this
repository,
so
I
have
a
fork
of
that
repository-
let's
go
find
that
and
it
is
let's
see
we'll
just
do
this
we'll
go
here
and
then
we'll
change
that
url
so
scm-api.
So
now
now
this
is
the
jenkins
ci
one.
Now
I'm
gonna
go
to
my
fork
by
changing
this
to
my
username.
A
Oops,
it
would
help
if
I
learned
how
to
type
there.
Okay,
so
notice
here
it
says
forked
from
scm
api
plugin
now
to
prove
exactly
what
you
showed
us.
If
I
search
for
linux
here
in
this
repository,
it
finds
no
matches
and
when
I
click
on
the
code
button
there
the
code
line,
it
says
this
sorry,
forked
repositories
are
not
currently
searchable.
A
A
However,
we
have
some
cases
in
the
jenkins
project
where
the
the
final
parent
is
not
the
official
source
code.
So,
let's,
let's
do
a
little
differently.
Let's
look
at
the
one
bruno
and
I
just
searched,
which
is
the
jenkins
git
plugin?
Okay,
so
this
absolutely
is
the
official
source
code
for
the
jenkins
get
plug-in.
However,
as
a
legacy
of
its
history,
it
mistakenly
has
this
ancient
forked
from
or
if
we
look
at
the
elastic
axis
plug-in.
A
A
No
code,
and
yet
I
know
that
there
is
a
reference,
I'm
pretty
sure
anyway,
there's
a
reference
to
linux
in
the
jenkins
file
of
the
elastic
access
plugin.
So
if
I
look
here
in
this
jenkins
file,
here's
the
word
linux,
but
it
didn't
find
it
and
why
didn't
it
find
it
because,
as
you
told
us,
when
a
repository
is
forked
from
another,
github
doesn't
search
the
fork
now,
if
we're
lucky,
this
one
is
up
to
date,
which
in
my
case
it
we're
not
lucky.
A
It
is
not
up
to
date,
so
it
doesn't
have
all
the
many
changes
that
are
have
been
made
in
the
official
version
so
piece.
It
means
we're
sort
of
stuck
and
stuck
in
the
sense
that
we
can't
use
github
to
do
the
search.
If
the
repository
using
has
this
forked
from
text
below
it
is
that
comfortable
for
you?
Are
you,
okay,
with
that
much
description.
A
A
And
this
is
a
fun
one,
because
it
reminds
us
there
are
some
places
where
the
word
master
is
okay
and
others
like
this
comment,
where
it's
describing
history,
so
it's
okay,
there
aren't
any
other
uses
of
master.
Let's
try
a
slave
just
for
fun,
okay
and
here
in
a
translation
in
portuguese,
as
spoken
in
brazil
and
here
in
java
identifiers.
So
this
is
okay,
except
for
a
brazilian
translation
that
needs
to
be
corrected.
D
Hi
mark,
could
we
just
try?
Could
we
check,
for
maybe
whitelist
and
blacklist
sure.
D
Yeah
because
I
thought
I
was
running
into
the
same
issue
that
that
piece
raised
when
I
was
searching
for
whitelist
and
blackness,
but
yeah.
A
A
Now
there
is
a
use
of
the
word
master
and
it's
in
german
localization,
german
localization,
german
localization
and
in
a
test
where
that
is
that
is
harmless.
That's
never
shown
to
a
user,
and
now,
let's
see
the
other
check
was
slave
right
and
there
are
lots
of
references
to
slave,
but
they
appear
to
be
in.
A
A
A
A
C
Okay,
mark,
I
don't
know
the
goal
of
this
document,
but
maybe
you
could
give
a
list
of
the
three
commands
that
you
made
on
your
terminals
so
that
when
they
want
to
do
it
by
themselves,
they
can
just
get
inspired
by
the
three
commands.
You
know
the
git
clone
and
gitgrab.
C
Okay,
I
still
have
a
question.
Sorry
mark
I'm
pretty
new
to
all
this.
How
did
you
generate
or
find
all
the
url
that
catherine
and
peace
were
supposed
to
check
for
the
terminology
problems?
It's
just
a
list
of
all
the
plugins.
A
A
I
think
yeah.
So,
oh,
no!
I,
yes!
Yes,
because
what
we
wanted
to
do
is
we
wanted
to
focus
on
on
popularity
first
and
the
jenkins
update
center
has
a
popularity
count
and
this
url
or
a
base
of
it,
and
so
what
we
did
is
we
grabbed
the
json
file
from
the
jenkins
update
center.
That
lists
the
popularity,
the
install
count
of
a
plugin
and
the
the
identifier
for
it,
and
then
we
rewrote
it
as
a
url
in
this
show.
Okay,
that's
smart.
D
This
is
a
request
because
I
remember
during
last
the
last
meeting.
We
did
a
demonstration
of
how
to
change
the
terminology
on
github
and
I
think
we
agreed
during
this
meeting
we'd
go
over
the
the
process
of
doing
it
locally,
so
changing
the
terminology
locally.
If
you
could
just
go
through
that.
A
A
So
I'll
get
that
done
after
we
finish
this
session
so
that
you
can
actually
refer
to
the
recording,
very
good
good
suggestion.
C
A
A
D
I
think
the
one
that
we
did
was
a
little
bit
lowering
the
list
it
was
assigned
to
it.
A
A
A
A
A
If
a
plug-in
needs
20
changes
and
you
submit
20
pull
requests,
yeah
they're
going
to
they're
going
to
ask.
Please:
could
you
do
these
in
a
batch
so
that
I
can
review
them
all
at
once,
and
and
so
what
we
wanted
to
do
today
is
show
how
to
do
a
larger
batch
and
it's
easier
to
do
a
larger
batch
without
using
the
github
ui.
A
A
A
A
A
No
okay,
so
my
my
guessing
rate
is
actually
pretty
poor
here,
apparently
sorry
about
this,
how
about
let's
go
a
little
further
down
and
let's
look
at
checks
api
this
one,
I
don't
think,
is
getting
a
lot
of.
Oh
no!
It
was
last
release
two
days
ago.
So
it's
probably
long
ago
been
fixed
master
is
just
a
branch
name
yaml!
A
A
B
A
D
D
Yeah,
I
think,
there's
one
we
can
work
with:
okay,
the
slave
setup,
plugin.
D
A
A
A
We
see
many
matches
and
it
as
I
look
at
it.
For
instance,
this
one
absolutely
should
be
changed,
because
that
is
user
text.
This
one
I
can't
change,
but
there's
one
we
found
one
that
should
change
this.
One
should
be
changed.
This
one
should
be
changed,
so
there
are
several
here
that
need
to
be.
We
know
of
at
least
three
already
that
need
to
be
changed
so
with,
and
this
one
needs
to
be
changed,
because
it's
in
jelly
and
and
so
we've
got
four
already
that
we
know
need
to
be
changed.
A
A
A
B
A
Okay,
all
right,
so
so
the
things
that
you
need
to
do
is
first,
you
install
gh,
and
that
depends
on
your
operating
system
and
you
can
find
gh
it's
the
github.
This
is
the
one
that
we
talked
about
on
saturday
in
the
in
the
orientation
session
there,
the
github
command
line
interface
and
the
reason
I
like
this
you'll
see
shortly
so
get
love
lab
hub
command
line
interface,
you'll,
just
click
a
download
button.
If
you're
on
mac
os
it'll
suggest
how
to
get
it
from
mac.
A
A
Right
right,
exactly
very
good,
so
so
there
and-
and
there
are
several
different
ways
to
do-
the
install,
for
instance,
here
the
install
install
instructions
for
mac
os
on
windows.
There
are
like
four
different
ways
right.
So
as
as
bruno
noted
chocolaty
is
here,
that's
one.
Scoop
is
another.
Winged
is
another.
A
Each
of
those
are
different
ways
of
doing
install
that
work
just
great
on
windows,
on
the
others,
for
instance,
on
linux
you
can
use
homebrew
on
freebsd.
I
just
follow
the
linux
and
bsd
installation
instructions
and
they
work
great
for
me
any
one
of
these.
So
so
I
like
the
gh
command
because
of
what
it
does
for
me.
So
here
I've
got
it
and
it's
going
to
make
my
life
simpler,
so
the
one
we
were
going
to
do
was
slave
setup
right.
A
I
copy
that
url
and
I'm
going
to
do
gh,
repo,
clone
and
now
the
cool
thing
here
is
I
shorten
this
because
it
knows
it's
talking
to
github.
I
do
it
like
that,
so
this
says:
use
the
github
command
line
work
on
a
repository
clone
that
repository
from
this
location.
The
jenkins
ci
account
the
slave
setup
plugin
and
it
cloned
it.
Now,
I'm
going
to
cd
into
that
directory.
A
A
A
A
It
says:
okay,
I
created
it.
Would
you
like
me
to
add
a
remote
for
it?
Yes,
I
would.
That
would
be
very
good
now,
if
I
do
a
git,
remote
minus
v
now
it
says
slave
setup.
Plugin
is
my
origin,
and
upstream
is
this
one
anytime?
I
want
to
get
the
latest
changes
from
upstream
I
say
gh,
repo
sync,
and
here
it
is.
A
A
A
A
A
A
A
A
A
A
A
A
So
I
could
I
could
do
this
by
pushing
the
branch
and
by
then
creating
the
pull
request
in
github,
but
ghpr
create
will
take
me
through
it
from
my
local
command
line.
So
I
can
do
it
a
little
easier
and
faster
with
commands,
so
it
says:
where
should
we
push
this,
I'm
going
to
push
it
to
marquee
weight.
A
And
if
I
fill
in
these
are
this
is
a
checklist
and
if
I
fill
in
those
check
empty
boxes
with
x's,
it
says
that
I've
thought
about
and
completed
that
thing.
So,
yes,
I'm
opening
it
from
a
topic
branch.
Yes,
the
poll
request
title
matches
what
I
want.
This
is
the
title.
Yes,
I've
described.
What
I
did-
and
here
we
may
want
to
for
the
benefit
of
jenkins
project-
is
replacing.
A
A
So
catherine
and
and
peace
did
that,
are
there
questions
you
have
on
on
the
process?
I
went
through
the
steps
I
took
to
create
you'll,
see
that
it
has
three
commits
here.
They
are.
It's
now
running.
Running
checks
to
see
are
things
okay,
in
this
case
it's
actually
going
to
run
the
job
on
ci.jenkins.io
and
it
will
give
us
some
test
results
and
tell
us
hey.
How
did
it
do.
A
Great
well
and-
and
I
confess
I
find
the
the
gh
command
line
so
nice
as
a
way
to
deal
with
yes
get
the
github
web
interface
is
great
for
creating
pull
requests.
It's
really
very,
very
good,
but
there
are
things
that
I
can
do
simpler
and
faster
with
gh
than
I
do
from
the
github
web
interface,
because
I'm
already
sitting
at
my
at
my
command
line,
I'm
already
doing
editing
there,
I'm
already
working
there
and
therefore
it
was.
It
was
easier
to
use
it
rather
than
than
some
other
tool.
A
Oh
okay,
good
so
deprecated
plugins
do
not
need
any
of
your
attention
that
that's
probably
something
I
should
have
filtered
so
over
here
in
the
result,
column,
if
you'll
just
put
deprecated,
we
will
not
submit.
We
don't
want
to
waste
time,
submitting
pull
requests
to
deprecated
plugins,
because
deprecated
plug-ins
will
not
get
a
new
release
and
if
they're
not
going
to
get
a
new
release,
there's
no
reason
for
us
to
fix
their
terminology.
A
A
Well,
and
thank
you
thanks
bruno
for
joining
peace
and
catherine.
Thank
you
very
much
for
what
you
discovered
about
github
search
facilities,
and
I
learned
something
I'm
very
grateful.
This
is
great.
Thank
you,
we'll
plan
to
meet
again
next
week
and
I'll
get
this
recording
published
within,
say
the
next.