►
From YouTube: What is the Kubernetes Code of Conduct Committee and What is it Working On - Karen Chu & Aeva Black
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2021 Virtual from May 4–7, 2021. 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.
What is the Kubernetes Code of Conduct Committee and What is it Working On - Karen Chu & Aeva Black, Microsoft
The Kubernetes community has its own elected Code of Conduct Committee (CoCC) but what exactly does this group do? In this session, we will cover the purpose and scope of the CoCC, introduce the current committee members, and share our progress on public, transparent process documentation as we continue to help build a healthy inclusive open source community.
https://sched.co/ekH7
A
B
Hey
everyone,
I'm
karen
chu,
I'm
an
open
source
community
pm
on
the
container
compute
uptreat,
also
at
microsoft,
azure
and
my
pronouns.
Are
she
and
her?
Let's
get
started
all
right.
So
in
today's
session
we're
going
to
talk
about
the
current
state
of
the
code
of
conduct
committee,
including
who
our
members
are.
What
our
purpose
is,
what
our
scope
is
and
our
plans
and
progress
around
documentation.
A
There
are
five
members
of
the
committee
three
in
addition
to
karen
and
I,
and
we
also
have
tasha
and
tim
at
vmware
and
celeste
at
the
cncf,
and
the
five
of
us
are
elected
or
appointed
by
steering,
but
then
given
separate
powers,
we
don't
actually
report
to
steering
one
of
the
few
committees
that
doesn't-
and
this
was
intentional-
both
of
these
committees
are
intentionally
separate
to
hold
each
other
accountable.
If
that
need
ever
were
to
arise.
A
Also,
to
note
is
that
no
more
than
two
members
of
the
code
of
conduct
committee
are
ever
from
the
same
company,
and
this
avoids
a
perception
of
single
party
control.
It
avoids
any
situation
where
a
conflict
of
interest
might
arise
and
if
one
were
to
arise
members
of
this
committee
do
we
do
recuse
ourselves
from
dealing
with
data,
and
so
there's
enough
of
the
committee
still
engaged
in
something.
A
Even
if
you
know,
let's
say
something
happened
involving
one
of
the
companies
now
our
purpose
as
a
committee
is
to
provide
and
support
and
enforce
a
well-considered
viewpoint
of
what
constitutes
acceptable
behavior
within
a
community
within
our
community,
and
to
do
this,
we
focus
on
a
restorative
model
that
believes
in
the
inherent
good
intent
of
all
members
of
the
kubernetes
community.
We
we
also
believe
that
codes
of
conduct
in
general
do
not
need
to
be
punitive
to
be
effective.
B
Okay,
so
let's
talk
about
the
scope
of
the
committee
here,
we've
mapped
out
some
examples
of
environments
that
fall
between
official
and
unofficial
spaces,
as
well
as
online
and
offline
spaces.
The
committee
is
invested
in
all
these
different
quadrants
because
they
may
involve
community
members
and
may
affect
both
the
health
and
behavior
of
the
community.
Ava.
Do
you
have
some
examples?
You
want
to
share.
A
A
There
are
less
obvious
ones,
our
podcasts
and
streams
that
people
run
or
a
personal
twitter
for
a
sig
lead
or
a
official
meetup,
or
an
unofficial
meetup,
or
even
just
a
couple
community
members
gathering
together
at
a
local
coffee
shop
to
hang
out
and
talk
about
what's
happening
in
their
working
group,
because
all
of
these
are
is
filled
by
members
of
our
community
acting
in
kubernetes
interest.
We
feel
that
this
is
part
of
what
makes
our
space
safe
and
welcoming
for
everybody,
and
especially
true
for
folks
who
are
in
a
leadership
position
in
the
community.
B
All
right
next
we'll
talk
about
committee
relationships
so
depending
on
the
environment.
Sometimes
we
work
in
conjunction
with
other
parties,
where
the
nexus
to
communicating
with
all
these
groups
when
there's
an
incident
or
concern
no
matter
where
in
the
community
it
may
have
come
from
so
we're
often
involved
in
routing
helping
to
gather
information
if
needed
and
deciding
what
actions
to
take,
but
we're
often
not
on
the
front
lines,
because
all
these
bodies
are
empowered
to
act
in
their
respective
domains.
B
So
think
of
us
as
tier
two
support
and
let's
dive
a
little
deeper
into
each
of
these
bodies
with
sig
contributor
experience,
we
loosely
advise
them
on
on
why
they
have
questions
around
like
cultural
aspects.
So
that's
something
we'll
work
with
them
on
with
slacking
github
admins
they're,
the
frontline
admins
in
their
spaces.
B
And
lastly,
when
in-person
events
are
a
thing
again,
the
linux
foundation,
event
team
members
are
the
front
line
admins
for
those
spaces,
because
they're
legally
responsible
for
venues
for
managing
event
staff,
hiring
security
et
cetera.
Nonetheless,
though,
we
are
there
for
them
to
help
provide
backup
and
to
provide
support
for
the
community
during
face-to-face
events.
A
So
what
we
do
to
foster
an
inclusive
and
welcoming
environment,
as
karen
mentioned.
Sometimes
we
support
working
groups,
but
we
also
support
community
members
directly.
So
if
you
are
leading
a
working
group
or
involved
in
one
and
would
like
our
input
on
something
you're
writing
or
doing
or
you
want
to
start
working
with
our
engagement
early
on,
please
just
reach
out,
but
if
you
feel
like
an
incident
has
happened
and
it's
very
subjective
also,
please
do
reach
out.
A
A
We're
all
human
and
historically,
we've
found
that
the
majority
of
bad
actors
that
we've
seen
were
not
actually
part
of
our
community.
They
just
showed
up
like
a
troll
on
twitter
or
a
troll
on
github
to
start
trouble,
and
while
we
have
found
that
there
are,
generally
speaking
a
very
small
percent,
but
some
bad
actors
in
any
system,
we
don't
ask.
We
don't
expect
anyone
in
the
community
to
distinguish
between
between
these
if
it
feels
unsafe
to
do
so.
A
We
asked
ourselves
some
hard
questions
to
try
and
understand
the
greater
context
and
what
people's
intent
was
before
coming
to
any
conclusion
or
making
any
decision
and
I'll
give
two
examples.
Both
happened
on
github
and
to
karen's
point
the
github
admins
were
the
ones
that
handled
these
initially,
but
both
were
gray
enough
that
they
came
to
our
attention.
A
In
the
first
example,
a
a
maintainer
was
perceived
as
sort
of
over
aggressively
closing
issues,
and
the
contributor
got
very
upset
eventually
fired
off.
Some
angry
comments
on
github
and
both
of
them
reached
out
the
code
of
conduct
committee
to
say,
hey,
something's,
wrong
with
the
person's
being
bad.
A
A
The
the
automation
had
over
aggressively
closed
things,
and
so
the
contributor
in
this
case
didn't
realize
that
their
issues
were
being
closed,
not
by
a
human
but
by
a
bot
and
their
anger
was
misplaced.
Meanwhile,
the
maintainer
realized
that
the
automation
tools
they
were
using
were
closing
more
issues
than
they
meant
to,
and
so
they
were
able
to
modify
the
tools
to
better
represent
the
intent
they
wanted
in
the
community
and
I'd
say
the
outcome
from
this
was
pretty
positive.
A
Yes
and
feathers
were
ruffled
in
the
beginning,
but
both
people
are
still
members
of
the
community
and
things
improved
now.
For
a
second
example,
this
happened
after
someone
just
had
just
joined
the
community
and
began
opening
their
first
couple
pr's
because
of
the
demographic
that
they
represent.
They
got
targeted
on
github
and
someone
began
posting
harassing
comments
on
their
pr's
and
they
were
kind
of
ignoring
it
at
first,
but
then
it
kind
of
it
continued
to
happen.
A
B
This
is
a
safe
and
private
space
when
you
come
and
talk
to
us,
and
what
exactly
does
that
mean,
though,
so
with
whichever
means
of
communications
you
choose
to
utilize,
we
never
disclose
to
one
party
what
another
party
is
said
about
a
situation
and
additionally,
we
seek
to
verify
reports
without
exposing
the
claimant,
while
also
avoiding
potentially
causing
more
emotional
distress
or
jeopardy.
For
that
matter.
B
Timeliness
is
important
to
all
of
us.
So
when
you
contact
us
we'll
try
to
provide
a
response
within
a
day
and
depending
on
the
scenario
we
may,
which
may
reach
out
for
more
information
just
remember,
our
goal
is
to
find
a
path
towards
community
healing
and
individual
growth
and
punishment
is
really
our
last
resort.
B
And
where
can
you
go
to
reference
all
this?
So
the
committee
is
still
fairly
young.
We
have
a
lot
to
do,
but
we're
committed
to
updating
and
publishing
documentation
around
our
goals
and
standardized
processes.
We're
hoping
that
by
making
everything
public
and
transparent,
the
community
will
have
clear
expectations
when
it
interacts
with
us.
B
B
So,
where
to
find
us,
if
and
when
you
need
to
reach
us,
you
can
email
conduct
kubernetes
dot,
io
to
reach
all
of
us
at
once.
But
if
you
do
want
to
reach
out
to
us
individually,
you
can
just
dm
us
directly
on
the
kubernetes
slack.
Our
job
is
to
be
here
for
the
community.
So,
as
we
mentioned,
you
should
get
an
initial
response
back
within
24
hours
of
reaching
out.
A
A
Please
know
that
also
our
our
work
happens
mostly
behind
the
scenes,
so
you
may
not
really
see
it
until
we
get
get
all
of
our
processes
matured
enough
to
create
transparency
reports,
you
might
not
see
what
we're
doing
in
the
community
unless
you're
in
one
of
those
six
or
working
groups
working
with
us,
but
know
that
we're
here
supporting
you
thanks
for
coming
to
our
talk
and
we'll
stick
around
for
some
questions.
Thank
you.