►
From YouTube: Inclusive Language Initiative Working Group - Celeste Hogan, Cloud Native Computing Foundation
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Inclusive Language Initiative Working Group - Celeste Hogan, Cloud Native Computing Foundation
A
B
Hello,
everyone,
my
name,
is
celeste
horgan.
I
am
one
of
the
co-founders
of
the
inclusive
naming
initiative
along
with
priyanka
sharma,
who
is
not
in
the
room
today
and
steven
augustus,
who
is
in
the
room
today.
I
am
a
staff
technical
writer
at
the
cloud
native
computing
foundation
by
day,
and
I
also
run
the
initiative
as
a
part
of
that
purview.
B
B
We
were
officially
founded
in
june
2020
and,
as
of
earlier,
this
year
are
now
a
linux
foundation
directed
fund
all
of
our
own
applause.
Please,
we
have
over
300
contributors
from
various
different
companies.
Most
are
contributing
just
on
their
spare
time,
actually,
as
well
as
contributions
from
cisco,
microsoft,
ibm,
red
hat,
splunk,
canonical
akamai,
guest,
maroptograph,
llp,
and
many
many
more.
B
B
So
a
little
bit
about
how
the
inclusive
naming
initiative
works,
because
this
is
a
very
high
level
and
kind
of
weird
topic.
What
we're
really
set
up
to
do
is
to
produce
language
recommendations,
push
those
language
recommendations
into
open
source
projects
into
individual
companies
and
hopefully
into
standards
bodies,
and
there
are
two
ways:
main
ways
that
we
sort
of
take
in
recommendations.
B
Is
that
there's
a
lot
of
companies
who
are
very,
very
desperate
to
help
out
to
do
better
and
to
really
improve
kind
of
their
language
situation,
but
they
don't
have
the
expertise
in
house
to
do
it
so
a
bit
of
a
dual
pronged
effort
in
that
regards.
It's
one,
helping
larger
companies
take
their
work,
open
source
and
bring
it
to
the
community
and
it's
helping
community
companies
by
providing
a
place
where
they
can
acquire
those
recommendations
and
have
a
conversation
around
dei
stuff.
B
What
we're
working
on
right
now,
as
I
mentioned
language
recommendations,
that's
kind
of
the
bread
and
butter
here.
We
have
three
sets
of
recommendations
based
on
the
severity
of
the
term
involved,
as
well
as
how
embedded
something
actually
is
in
a
particular
computing
system,
or
how
complicated
would
it
be
to
actually
remove
and
replace
something
something
we're
also
producing
is
guidance
for
companies
and
open
source
projects
on
how
to
implement
language
changes
without
breaking
the
world
and
how
to
advocate
for
them
in
different
organizations.
B
So
I'm
gonna
break
for
a
little
bit
and
demo
a
little
bit
of
how
we
work
on
a
language
recommendation.
I
would
say
the
largest
component
of
people
who
contribute
to
I-
and
I
are
technical
writers.
We
work
with
actually
not
one
but
two
taxonomists,
which
is
a
job
that
exists
only
in
very
strange
corporations
like
ibm,
but
also
any
corporation,
where
they
have
a
lot
of
terminology
that
they
need
to
manage
centrally.
B
B
Chinese
wall
turned
up
a
couple
of
times
from
a
couple
of
different
companies,
crippled,
turned
up
many
other
times
we're
going
to
follow
bulletproof
through
its
recommendation
cycle.
So
first
things
first
was
gathering
this
information
from
our
members.
At
this
point,
this
spreadsheet's
probably
like
a
few
months
old
at
this
point.
So
at
some
point
I
imagine
we'll
do
another
survey,
but
that's
not
on
the
road
bam
right
now
from
there.
We
kind
of
consolidated
our
recommendations
and
started
picking
them
apart
to
see
who's
going
to
do
what
work.
B
From
there
this
month's
directly
to
the
language
work
stream,
where
we
started
the
work
on
the
actual
recommendation,
we
have
a
sort
of
template
that
we
follow
for
these
recommendations,
and
this
document
is
actually
not
particularly
marked
up.
But
after
writing,
the
recommendation
there's
usually
a
smaller
group
of
us
who
work
on
any
one
recommendation.
B
We
then
open
a
pull
request
in
our
website
repository
and
the
broader
initiative
of
around
300
contributors
then
provides
its
comments
and,
once
again,
there
is
an
incredibly
long
tale
around
how
that
works.
Once
things
are
merged
and
I'll
just
sort
of
go
through
this
real
quick
they
land
on
the
word
list
that
we
produce
so
like
I
said,
the
entire
point
of
this
is
to
drive
sort
of
consensus-based
recommendations.
B
The
other
thing
that
we're
really
looking
for
here
is
to
categorize
things
into
tears,
things
that
need
to
be
replaced
immediately
because
the
harm
they
provide
in
terms
of
language
is
so
strong
things
which
you
should
probably
consider
replacing
and
things
which
are
not
great,
but
they
aren't
nearly
as
egregious
as
the
other
two.
So
we
currently
I'm
not
actually
sure
about
the
total
of
what
we
have
published
is
now,
but
you
should
definitely
take
a
look
at
the
word
list.
B
Take
a
look
at
the
overview,
so
you
understand
the
process
a
little
bit
more
and
while
you're
on
the
website
also
take
a
look
at
the
language
evaluation
framework
to
understand
how
we
decide
what
is
harmful
and
what
isn't
so,
that's
a
little
demo
of
how
the
entire
process
works.
It's
really
just
a
document
drafting
process,
it's
not
particularly
mysterious,
but
it
does
involve
a
lot
of
discussion.
B
B
B
B
I
am
a
technical
writer
and
usually
when
things
like
this
happen,
people
look
for
the
writer
in
the
room.
They
said.
Oh
no,
we
said
something
bad.
We
gotta,
we
gotta
find
the
writer
just
learn
how
to
say
something
good,
just
yeah,
simple,
simple
right,
but
the
the
thing
that
I
would
drive
home
to
is
that
your
writers
are
often
not
empowered
to
be
decision
makers
so
to
succeed
in
an
initiative
like
this,
you
need
to
empower
your
writers
and
the
way
that
you
do,
that
is
by
having
high
level
management
sponsorship.
B
If
you
work
in
a
tech
company,
which
I
assume
most
of
you
do,
if
you're
here
at
kubecon,
the
other
thing
you
really
need
to
do
is
find
a
high-level
technical
sponsor,
particularly
when
it
comes
to
changing
code
bases
and
particularly,
if
you're,
not
the
person
who
owns
the
code
base
again
as
writers
often
aren't.
You
need
extremely
senior
level
technical
sponsorship
for
this
kind
of
initiative,
or
you
will
run
into
some
very
angry
engineers.
B
B
B
Are
there
marketing
materials,
internal
company
policy
documents?
Do
you
follow
standards,
organizations
or
all
of
the
above,
and
what
realistically,
can
you
actually
tackle
the
example
that
I'll
give
is
kubernetes
which
imports
go
modules
into
almost
every
single
repository
and
those
go
modules?
Don't
always
have
the
greatest
words,
because
we
don't
have
control
over
what
go.
Does
it's
not
necessarily
feasible
for
kubernetes
project
owners
to
go
in
and
try
and
change
go.
That's
not
the
best
use
of
their
time,
so
you
have
to
figure
out
where
your
limit
is.
B
B
The
next
prepare
policy
document
for
dissemination
within
the
organization
to
essentially
tell
people.
This
is
what
we're
doing.
This
is
what
we
are
and
aren't
going
to
change,
communicate
the
policy
and
kind
of
get
your
people
together,
start
assigning
roles
and
start
actually
taking
like
tackling
the
action
plan.
B
Aspect
of
that,
particularly
from
a
technical
aspect,
be
very,
very
mindful
of
dependencies,
and
you
need
to
make
sure
that
testing
is
incorporated
into
every
step
of
this
process
when
you're
going
around
securing
buy-in
from
your
sponsors
be
prepared
to
have
some
really
difficult
conversations
with
people
who
may
not
understand
the
importance
of
this,
or
they
may
only
partially
understand
the
importance
of
it.
I
think
it's
safe
to
say
I
don't
know
that.
I
fully
understood
the
importance
of
this
when
I
started
this
work,
you
can
grow
through
it
and
that's
fine.
B
B
A
few
other
things
to
consider
as
you
move
forward,
sponsoring
underrepresented
minority
groups
in
your
companies
and
connecting
them
to
your
writers
is
a
great
idea.
Building
inclusivity
into
your
business
processes
is
also
a
great
idea
and
requiring
your
vendors
to
use
inclusive
language
and
the
products
and
documentation
they
supply
to.
You
will
all
go
a
long
way
into
not
introducing
that
language
into
your
companies
to
begin
with,
okay
kind
of.
In
conclusion,
how
can
your
company
help
the
inclusive
naming
initiative?
As
I
mentioned,
to
some
people
earlier?