►
From YouTube: Kubernetes Contributor Experience SIG 20180606
Description
Join us every Wednesday!
A
Hi,
everyone
welcome
to
the
June
6th
edition
of
Corinne
ADIZ
contributor
experience.
My
name
is
Paris
co-chair
of
this
fine
group.
We
have
a
small
crew
today
and
not
too
many
agenda.
Items
I
feel
like
everybody
is
in
full
motion
with
stuff
that
they're
working
on.
So
that's
awesome.
So
let's
do
our
reoccurring
items
first
and
that
would
be
new
contributors
on
the
call
I.
Don't
flatten
may
have
introduced
yourself
last
time.
If
you
did,
it
feel
free,
but
I
think
everybody
else
on.
A
The
call
is
a
current
contributor
and
I
know
all
you
fools
just
kidding
all
right
all
right.
All
right
next
topic
is
hosts
for
the
committee
meeting.
We
have
a
hole
in
the
schedule
for
next
week.
So
if
anybody
is
interested
in
hosting
and
I
also
have
a
minor
flub,
George
I
am
supposed
to
be
hosting
tomorrow,
but
I'm
actually
on
vacation
I
did
do
the
work.
B
A
A
A
C
Like
a
month
and
a
half
later,
I
I
think
the
graph
of
the
week
made
a
lot
of
sense
when
we
still
had
a
lot
of
stuff
we
hadn't
gone
through,
but
at
this
point
we've
been
through
kind
of
all
of
the
graphs
yeah
and
for
that
matter,
I'm
not
convinced
that
it's
necessarily
all
that
interesting
to
most
of
the
people,
yeah,
partly
based
on
our
turnout
for
the
dev
stat
session
at
coop.
Con
Copenhagen
yeah.
E
A
It's
a
very
niche
set
of
people
that
are
super
interested
in
it.
I
do
like
how
we've
been
giving
other
random
statistics
about
the
community,
so
we
shouldn't
do
stats
chart
of
the
week.
Maybe
we
should
call
it
like
community
health
metric
of
the
week
and
then,
like
you
know,
we've
been
doing
slack
and
YouTube
and
well
I
think
we
should
even
do
mailing
list,
which
don't
mental
note
for
us
as
we
need
to
respond
to
Brian
grant
and
tell
him
to
put
us
on
his
owners
for
the
K
tab
and
K
users.
A
Let
me
put
this
on
the
agenda
so
that
we
can
have
a
larger
discussion
about
it:
moderation,
okay,
cool
yeah,
and
if
there's
anybody
else
that
can
help
me
take
notes,
because
you
know
I
talk
a
lot.
I
don't
want
to
type
in
your
ear.
That
would
be
awesome.
So
I
just
put
moderation,
there's
a
place,
a
placeholder
all
right.
A
G
H
H
Well,
that's
bizarre,
okay,
so
long
story
short.
We
we
had
a
meeting
yesterday
I
was
supposed
to
be
the
we
was
originally
calling
it
a
non
dev
contributor
guide,
realizing
that
did
a
bit
of
a
disservice
to
many
of
the
efforts
that
developers
are
doing,
not
the
least
of
which
is
Doc's
not
getting
nearly
enough
love,
but
also
some
of
the
other
aspects
like
p.m.
and
architecture,
and
things
like
that.
H
A
B
A
B
Yeah
I
think
it
would
also
help
out
with
the
like,
if
it's
an
if
it's
all
in
the
contributor
like
if
you
go
to
the
contributor
guide,
and
then
you
decide
okay,
what
do
I
do
code?
Are
these
don't
cook
things
they're
all
kind
of
listed
in
the
same
place
that
way
that
way,
one
or
the
other
isn't
doesn't
look.
You
know
what
I
mean
it's
like.
A
G
F
We
we
talked
about
talked
about
a
bunch
of
stuff
throughout
the
the
meeting
they're
essentially
establishing
the
mission
and
how
to
formalize
this,
and
I
think
this
is
the
good
one
to
end.
What
is
a
project
under
the
contributor
guide
and
we
talked
a
lot
about
identifying
non-code
focus
trolls,
so
we
kind
of
ironed
out
a
lot
of
those
which
I
think
helps
us
when
we
look
at
different
different
documentation
that
we
want
to
write
so
making
sure
that
we
have
the
rules
properly
defined.
F
A
A
H
B
A
Next
is
moderation,
which
we
just
briefly
touched
on,
so
Brian
grant
brought
up
the
point
that,
or
at
least
it
sounds
like
we
should
start
moderating
almost
all
of
the
mailing
lists.
There
is
a
huge
fan
issue
going
on
and
I
guess
that's
to
be
expected
as
time
goes
on,
but
the
problem
is
most
of
our
mailing
lists
are
quote,
say
owned,
which
means
that
personal
folks
have
that
on.
A
Our
individual
folks
have
that
on
their
personal
accounts,
which
makes
it
difficult
for
us
to
moderate
and
do
and
do
kind
of
like
spam
attacks
and
one
of
those
main
groups
is
crew
net
users,
the
other
one
is
kubernetes
development.
They
are
spammed.
All
of
the
time
I
mean
steering.
Committee
is
as
well
I
kind
of
giggle
at
that,
because
it's
like
people
selling
kubernetes
stuff.
The
steering
committee.
A
But
so
I'm
trying
to
think
of
a
way
what
mate,
which
makes
sense
to
contributor
experience
for
us
to
moderate.
These
lists
I've
been
toying
with
the
idea
of
us
getting
on
all
of
the
sick
lists
and
like
having
a
team
of
people
who
might
be
already
in
those
SIG's
or
on
those
lists
to
take
up
the
moderation.
A
J
A
F
A
B
K
I
That
IO,
which
they
do
most
of
their
stuff
through,
but
they
also
steering
private
and
that's
the
one.
Where
could
conduct
violations
or
anything?
That's
super
private,
I
think
I,
don't
think,
there's
anything
they
can
do
about
that,
one.
That
one
has
to
stay
open
but
closed,
but
they
actually
do
allow
non
steering
committee
members
to
join
the
steering
committee
general
lift
yeah.
B
A
A
I
It's
possible
the
other
thing
that
I
was
I,
was
kind
of
thinking
like
again
trying
to
piece
the
whole
picture
together.
I
know
dan
from
the
CN
CF
had
mentioned,
that,
like
the
CN
CF
could
also
put
especially
for
the
big
lists.
They
could
take
over
moderation,
as
in
particular
of
spam
and
being
able
to
clear
out
the
spam
queue
as
part
of
their
responsibilities,
and
maybe
we
won't
want
to
do
that
for
the
bigger
list.
A
B
L
A
I
Well,
the
other
thing
that
might
be
a
good
idea
just
for
like
a
break
glass
disaster,
recovery
kind
of
thing
is
I,
don't
know
if
we
have
like
a
quote-unquote
like
a
service
account,
something
that
is
locked
away
and
like
a
one
password
or
a
key
pass,
or
something
like
that.
That's
like
a
generic
account
that
gets
added
as
the
owner
so
that
if
people
individuals
end
up
going
away,
there's
a
way
to
still
get
in
yeah
I.
I
This
problem
with
Google
Groups,
because
it's
decentralized
there
isn't
like
a
none,
tiered
access
control
system.
I
know:
we've
looked
at
before,
potentially
moving
over
to
like
gee,
sweet
stuff
and
moving
over
to
Kate
Kao,
which
then
there
would
be
a
tiered
access
control
system
and
somebody
who's,
an
account
owner
would
be
able
to.
You
know,
restore
access,
give
rights,
take
away
rights
that
kind
of
stuff,
because
the
other
thing
is
like
giving
owner
rights
on
it
on
a
Google
Group
and
that
kind
of
stuff.
I
D
B
B
B
That's
a
challenge
I'm
in
I'm,
+100,
yeah
I'm,
in
fair
with
that,
and
eventually
the
self
moderation
stuff
will
sort
itself
out
with
discourse
yeah
like
between
myself,
Bob
and
Paris
like
and
there's
like
I,
purposely
didn't
make
Josh
like
an
admin,
but
he's
participated
enough
or
he's
getting
the
rights
they're
like
so
like
the
more
you
participate,
the
more
right
you
get,
so
that
also
kind
of
helps
deal
with
like
time
zone
issues
and
things
like
that.
But
then
again
we
haven't
had
someone
purposely
attack
us
yet
either
it.
B
A
B
You
know
what
I
mean,
but
if
it's
one
of
those
things
are
it's
like
well
he's
more,
maybe
concerned
about
as
we
grow,
it's
gonna
grow
out
of
control
like
I'm
wondering
how
like,
if
he's
like
spending
an
hour
a
day,
dealing
with
this
and
stuff,
then
I
think
we
can
make
the
justification
for,
like
sorry,
normal
email
kind
of
sucks.
For
this.
B
I
Don't
think
we're
gonna
get
away
from
mailing
lists
period
playing
for
all
for
all
discussions,
I,
just
I,
don't
think
we're
gonna
be
able
to
do
that.
Okay,
users
yeah
there
might
be
there
might
be
something
there
and
I
would
suggest
a
first
run
at
by
steering
just
for
me
like
political
standpoint
and
seeing
like
how
how
do
they
feel
about
that
yeah
and
then,
if
we
they
were
okay
with
it,
then
putting
out
a
console,
probably
2k
users
itself,
like
hey
how
many
of
you
are
going
to
like
grab
your
pitchforks.
If
we
try.
B
B
New
people
can
go
to
like
the
sexy
thing
and
then
you
know
you're
not
taking
away
the
whole
thing,
but
I'm
just
curious
as
far
as
like
how
much
overhead
there
is
4k
users
and
ke
dev
I
feel
we're
going
to
be
stuck
doing
that
which
I
think
it's
fine.
My
concern
is
safe,
working
group,
mailing
lists
and.
B
B
I
That,
because
we
know
we're
gonna
need
to
do
that.
We
can
maybe
reduce
that
workload
for
4k
users,
but
we're
gonna
need
to
do
it
in
some
have
at
least
a
plan
in
some
form
that
that
we
can
handle
it,
and
it's
not
just
for
necessarily
spam
moderation.
But
it's
also
like
you
know,
if
somebody
posts
something
that
would
violate
code
of
conduct
to
a
list.
Yeah.
E
B
I
feel
with
you
know,
helping
when
I
help
things
create
less
like
those
leads
have
admin
on
those
lists
like
I
feel
like
by
the
way
you're
also
responsible.
You
know,
if
you
c-span,
for
policing
up
your
own
list.
I
could
see
that
scaling
very
well.
It's
one
more
thing
for
sig
leads
to
do,
but
they
already
do
it
though
yeah
exactly.
A
Discussion
yeah,
all
that
stuff
is
under
discussion
right
now,
whether
or
not
like
they
need
a
liaison
that
somebody
that's
on
the
moderation.
I
have
spoken
very
heavily
for
everyone.
That's
a
moderator
should
be
on
the
code
of
conduct
committee
so
that
there's
no
need
to
kick
somebody
out
that
they
can
just
be
empowered
to
do
it,
but
yeah
I
know
all
of
that
stuff
is
way
more
complicated
than
we
can
complicated.
I
mean
my
perk,
like
like
a
personal
opinion,
is
that
we
should
just
be
able
to
propose
K
users
gone
and
I.
A
Don't
think
anybody's
gonna
have
any
objections
to
moving
it
and
then
for
sig
lists.
We
could
add
on
to
the
see
creation
checklist
that
maybe
they
should
find
someone
in
contributor
experience
that
will
be
willing
to
help
moderate
their
group,
and
then
we
can
have
a
contributor
experience
owner
on
every
group.
At
least
I.
Don't
know
again
right.
That
would
that's
that's
rough
thoughts,
but
we
need
to
find
anyway.
We
need
in
them
in
the
interim.
We
need
to
respond
to
Brian
about
who
take
it
on
these
lists.
A
B
I
Whatever
we
decide,
we
also
just
need
to
make
sure
it's
codified,
so
that
way
you
got
but
like,
even
if
that
sig
leads,
especially
when
they're
setting
up
these
lists.
They
know
okay,
who
do
I
need
to
add
from
code
of
conduct
or
who
do
I
need
to
add
from
to
Trebek
to
end
up
end
up
doing
those
things
what's
written
down
and
then
codified,
because
I
think
it's
conversation
circle
back
around,
because
when
sig
architectures
lists
were
set
up,
they
were
set
up
that
anybody
can
post.
I
B
I
C
A
C
I
mean
I.
You
have
to
go
in
through
the
Google
UI
to
do
it
rather
than
just
sending
an
email,
you're
logged
into
your
Google
account.
But
if
you're
logged
into
Google
account
anybody
who's
logged
into
Google
account
can
in
post,
and
if
we
change
that,
then
we're
going
to
need
to
look
at
how
that
affects
the
the
teams
that
need
to
post
across
a
lot
of
the
project.
A
Would
be
what,
if
a
part
of
the
state
creation
procedure,
we
no
longer,
let
say
leads,
create
their
own
groups
and
whoever
is
setting
them
up,
would
put
five
people
from
contributor
experience
and
then
contributor
experience
when
total
own.
All
the
mailing
lists
and
godsakes
yeah,
so
you're
saying
just
centralize
all
the.
B
L
I
B
A
It
mentions
a
bunch
of
things
that
we
no
longer
do
so.
I
think
this
is
the
time
to
really
rethink
that
and
again,
that
being
us
being
the
owners
of
all
of
this
stuff,
I
mean
between
all
of
the
owners
that
are
currently
in
the
community
management.
Sub-Project
I
feel
like
we
could
take
this
on
and
I
think
the
ramp
up
would
be
the
most
work,
but
I
feel
like
the
maintenance
of
it
would
not
be
too
much
work.
B
I
think
we
should
just
start
with
updating
this
and
creation,
one
that
way
new
groups
will
start
doing
it
the
correct
way
and
then,
as
far
as
moving
the
existing
stuff
I
think
we
should
just
start
with
ours
and
then
maybe
I
mean
developer
and
users.
We're
gonna
have
to
do
right,
start
with
those
two
and
then
go
from
there.
Maybe.
B
A
E
I
B
And
now
see
and
I
actually
have
I
have
a
policy
that
got
PR
des
and
everything
we
just
haven't.
We
haven't
figured
out
the
execution,
part
and
I'm
sure.
Like
Josh
mentioned,
you
know,
groups
posting
to
all
lists
because
they
can
there's
probably
a
lot
other
edge
cases
that
we
haven't
thought
about
that
this
might
affect
that.
We
should
probably
do
a
little
bit
due
diligence
on
I'm
thinking
right
all.
A
Right
so
a
lot
of
actions
from
that,
but
I
was
gonna,
say
LLC
and
I
are
doing
a
training
today
with
Chase
to
do
github
projects
so
we'll
do
we'll
start
doing
github
projects
and
umbrella
issues
and
really
get
the
contributor
experience
sake.
Some
little
bit
more
project
management.
I
know
everybody
might
be
cringing
right
now,
but
just
to
keep
our
heads
on
straight,
we'll
have
board
yeah.
I
would
actually
like
that.
So
we're
we're
gonna
sit
down.
A
M
So
in
the
last
I
think
we
install
the
were
like
a
week
ago
now
and
I
did
some
like
number
I
kind
of
like
ran
some
numbers
to
figure
out
what
we've
you
know,
what
we've
actually
like
showed
and
how
kind
of
I
don't
know
successful.
It
was
so
far
given
that
this
was
like
the
first
week
of
a
really
meeting
data
was
there's
a
kind
of
an
interesting
experience,
I
once
again,
I'm
gonna
share
screen.
M
Can
you
see
the
two
charts
I
mean
it's,
the
the
numbers.
Aren't
big
but
like
so
on
this
kind
of
storing
side
we
saw
like
90
over
the
last
week
we
solved
97
things
that
look
like
conversations
that
were
like
a
question
answer
and
we
kind
of
said
hey.
This
looks
useful.
Can
we
store
this
so
that
was
like
97
times
and
then
out
of
that
64
times?
M
So
over
kind
of
like
the
week
that
I've
been
monitoring
this
like
in
a
being,
this
was
a
little
bit
more
I
kind
of
turned
it
down
to
not
ask
a
store
as
much,
because
there
was
like
a
complaint,
then
the
other
thing
I
noticed
is
that,
like
I
was
kind
of
messing
a
lot
with
the
text
that
actually
shows
out
for
this.
Originally,
it
says
something
along
the
lines
of
like
hey.
This
looks
useful.
Can
we
store
it?
There
was
like
zero
clicks.
M
So
then,
I
put
like
a
little
description
of
what
the
hell
that
bot
actually
does
and
like
puts
a
little
thingy
in
it.
Then
you
know,
because
the
text
was
a
lot
bigger
on
the
message.
I
think
it's
like
a
lot
more
people
noticed
it
and
more
people
started
like
and
one
person
actually
said
like
hey,
you
know
what
the
hell
is
this
thing
doing.
M
Those
notifications
for
a
while
and
kind
of,
like
so
I've,
been
also
talking
to
the
person
that
you
know
one
person
that
mentioned
this
too
often
somebody
else
kind
of
when,
when
the
when
George
disabled,
the
bot
first
I
can
like
person
that
kind
of
to
the
party
reaction
thingy
to
it
in
slack
so
I
talked
to
both
of
those
people
and
they
were
kind
of
like
yeah.
You
know
they
kind
of
provided
some
like
really
valuable
feedback.
Saying
like
it's.
So
it's
loud,
you
know
here's
some
stuff
to
do
so.
M
I,
basically
kind
of
for
them
I
created
a
mutant
feature.
Only
a
couple
of
people
really
muted.
It
I
think
only
that.
So
this
I
looked
up
last
night.
It
was
like
three
people,
muted
it
so
that's
kind
of
on
the
storing
side.
It
seems
like
it's
kind
of
getting
there
I'm
working
on
right
now
and
so
I,
like
I,
was
looking
at
the
actual
stuff
that
was
stored
in
the
first
few
days.
It
was
because
the
question
I
think
was
more
vague.
M
It
was
probably
stored,
like
you
know,
but
people
just
kind
of
click
through
and
said
you
know
whatever
I
don't
care
so
now
you
know
now
text
is
a
little
different
like
hey.
This
is
gonna,
be
showing
up,
and
this
is
useful
mo
blah,
so
I
think
now
people
are
kind
of
putting
a
little
bit
more
emphasis
or
thought
into
it,
because
the
first
question
stored
was
something
like
hey
or
something
weird.
M
So
now
people
are
putting
a
little
more
emphasis
on
it,
but
like
what
that
means
is
we
got
to
go
and
review
all
the
previously
stored
stuff
and
modify
that
so
I'm
actually
currently
working
on
this
like
a
little
dashboard.
They
need
to
be
able
to
go
and
like
or
like
a
little
admin
tool
to
be
able
to
go,
and
you
know,
modify
the
answers
and
hide
them
delete
them.
B
A
M
M
To
it,
yeah
sure
yeah
I'll
just
copy
the
charts
and
stuff.
So
that's
not
so.
On
the
storage
side,
it's
it's
pretty
good.
You
know,
and
it's
been
I've
been
kind
of
like
focusing
a
lot
on
that
to
figure
out
how
to
you
know,
show
enough
of
information
or
show
enough
of
the
like
the
messages
and
not
annoy
people
at
the
same
time.
So
that's
I
think
that's
been
kind
of
in
a
steady
state.
M
Now
where
people
are
adding
stuff,
we
need
to
go
back
and
like
review
this
stuff,
that's
been
added
to
make
sure
that
actually
makes
sense.
I
mean
right
now,
it's
only
like
twelve
things
that
were
added
so
we'll
do
that
net
on
the
kind
of
retrieval
side
or
on
the
like
suggestion,
side,
there's
been
20
times
where
it
provided
so
like
looking
at
yesterday
was
20
times
that
it
provided
a
suggestion.
Like
you
know,
one
of
the
so
like
it
like
understood
the
question
that
somebody
is
asking-
and
it
said
hey.
M
This
looks
similar
so
previous
question
and
then
provide
his
suggestion
and
out
of
that.
So
when
the
suggestion
pops
up
there's
a
little
button
at
the
bottom,
it's
like
was
this
useful,
yes
or
no,
so
out
of
that
twelve
people
selected
response
and
out
of
that
only
two
were
actually
selected
as
helpful.
M
Then
it's
about
like
indexing,
all
of
the
Doc's,
that
you
know
the
kubernetes
Doc's
and
then
kind
of
providing
those
as
feedback
as
well.
Snow
and
they'll
happen
over
the
following
week
or
like
them
not
this
week.
You
know
next
week
or
something
like
that.
Maybe
a
week
from
now,
just
I
don't
want
to
like
do
it
too
early,
because
I
don't
want
to
start
with
showing
people
a
lot
of
crap
right
away
right.
A
Two
questions:
what's
our
benchmark
for
success
here,
like
I
mean
you
said
earlier
like
oh,
that's,
not
good
or
helpful,
or
that
kind
of
thing
like.
Are
we
trying
to
reach
like
a
number
that
says
like?
Oh,
this
works
and
then
also
like?
Have
we
had
have
we
set
up
a
time
box
for
this?
As
far
as
like,
oh
in
three
months,
we're
going
to
either
continue
this
forever
or
or
not?
Do
this
anymore,
I
was
not
at
the
last
meeting,
so
I
apologize.
M
So
first
answer
I:
do
it
the
thing
that
I'm
looking
at
is
this?
Basically,
this
number
is
the
valuable
feedback.
One
is
that
like?
How
often
is
it
that
we're
showing
somebody
a
message
and
they're
clicking
like
yes,
that's
valuable
or
yes
that
answers
my
question.
So
that's
not
like
that
number
is
basically
the
thing
that
I'm
looking
at
most
in
terms
of
knowing
it.
We
didn't
set
up
a
time
box.
M
A
I
think
we
should
set
one
up.
You
said
you
installed
it
one
week
ago
and
I
think
we
should
give
this
I
don't
know
somewhere
between
30
and
60
days.
So
let's
see
that
would
take
us
to
pretty
much
end
of
July.
Does
anybody
have
any
concerns
with
July
31st
meeting
making
a
final
evaluation
of
the
tool?
If
we
haven't
already
any
objections.
L
M
I
mean
sure
I
have
no
problem
with,
like
whatever
data
I
think
we'll
we'll
probably
have
a
better
idea
by
then
anyway,
you
know
I
think
it's
like
it's.
Let's
see
like
if
we
continue
talking
once
a
week
like
I
mean
if
this
is
interesting
as
I
can
continue.
Having
this
you
know
be
part
of
the
status
every
week
and
I
think
we
can
kind
of,
like
you
know,
figure
it
out
from
there
like.
M
If
this,
if
the
metric
of
like
providing
value
is
going
up,
then
you
know,
then
it
because
the
feeling
like,
if
you
give
it
like
a
specific
date,
I'm
a
little
worried
that
it's
like
here's,
some
roadmap
items
to
like
make
it
better
right
and
those
are
always
gonna
evolve.
So
it's
by,
like
you,
know
two
months
from
now.
You
say
this
is
exactly
the
cutoff
date.
Then
you
know
here's
some
we're
gonna
roadmap
items
that
we've
been
considering
for
lunch,
the
next
few
weeks,
for
example,
that
might
not
make
it
within
that
cutoff
date.
M
A
D
A
No
no
I
know
that's
something
that
I
think
we
should
definitely
work
out
like
whenever
we're
trying
something
out
within
contributor
experience.
We
should
give
it
a
time
boxed
window
of
some
sort.
So
let's
think
about
that
from
and
from
a
longer
term
perspective
and
then
also
update
our
charter,
because
our
charter
can
include
something
like
that.
So
if
we
are
prototyping,
then
then
people
can
see
the
house,
so
what
I'm
actually
gonna
take
that
as
an
end.
B
A
M
F
B
B
Okay,
so
here
the
church
for
the
week,
everything
is
up
and
green,
mostly
because
I
posted
on
the
official
blog.
If
you're
ever
wondering
whether
of
posting
on
the
official
blog,
who
actually
reads
this
and
uses
RSS
and
reads
Bloods,
it
was
a
lot.
So
in
fact,
our
users
have
almost
doubled
since,
like
our
last
status,
where
what
760
now
something
Bob.
If
we
add
these
up,
it
was
scary.
Earlier
today,
yeah,
it's
yeah
731
active
non
system,
users
yep,
as
you
can
see
the
last
seven
days,
which
is
like
from
the
last
week.
B
The
views
and
everything
are
going
up.
Participation,
however,
is
not
as
awesome
as
it
could
be.
That's
what
this
means.
This
is
like
daily
participation,
but
the
eyeballs
are
certainly
there.
We
just
got
to
get
people
talking
about
more
stuff
and
related
to
the
moderation
stuff.
This
is
the
users
press,
trust
level,
which
is
when
someone
joins
they.
Basically,
the
system
doesn't
trust
them,
as
users
use
the
site,
the
site,
trust
them
more
and
eventually
so
three,
these
three
people
are
like
me,
Bob
and
Paris.
B
Here,
as
people
move
up
in
trust
level,
the
system
gives
them
more
power.
So
if
let's
say
someone
were
to
spam
and
as
users
flag
spam
comments,
the
people
who
would
trust
more
get
more
weight
right.
So,
for
example,
if,
if
someone's
participating
a
lot,
basically
we
trust
them.
They
have
more
moderator
power
versus
spam.
I
just
want
to
kind
of
explain
that
as
that
pertains
to
the
discussion
we
had
earlier
other
than
that,
I've
got
PR
Xin
to
link
it
from
the
kubernetes
IO
web
page
and
you
wanna.
B
B
You
do
a
project
yeah,
so
the
other
two
bits
is
I
submitted
to
put
in
the
footer
of
the
kubernetes
io
websites
and
in
the
blog
and
someone
actually
found
a
bug
with
the
kubernetes
blog
saying
that
there's
no
blog
comments
on
kubernetes
blog
posts
and
that
would
be
interesting
so
ends
up.
We
can
embed
discourse
threads
as
kind
of
pseudo
block
comments
and
I
propose
that
as
a
solution,
because
we
would
be
able
to
use
our
existing
moderation
and
stuff
like
that
and
apply
that
to
blog
comments
as
well.
B
So
I
thought
that
was
like
a
cool
hey
I
can
I
can
sort
that
as
well
and
the
last
bit
I
posted
this
on
the
channel.
We
also
have
a
method
to
automatically
import
and
auto-close
issues
and
github
and
make
them
into
threads.
So
if
we
ever
have
a
situation
where
there's
valuable
discussion
there,
but
maybe
you
know,
someone
has
made
a
decision
or
something,
but
users
still
want
a
place
to
discuss
stuff.
B
I
Yeah
so
I
just
wanted
to
like
give
an
update
to
the
group
on
a
couple
things
I've
been
pushing
forward.
I
talk
week
about
labeling
updates
and
that
kind
of
stuff
that
is
all
complete
at
this
point.
So
we've
now
expanded
and
normalized
a
whole
bunch
of
labels
across
both
kubernetes,
as
well
as
I,
was
able
to
get
access
and
normalized
labels
across
the
Cabrini
SIG's
org
as
well.
So
our
standard
set
of
labels
is
now
on
both
organizations
in
every
repo
that
also
normalizes
out
the
github
default
label
set.
I
I
I've
also
as
part
of
that
moving
the
needle
on
good
first
issue.
A
good
first
issue
is
now
that
github
standard
label
is
now
again
applied
and
created
in
all
of
our
repos
yeah.
We
don't
yet
we
don't
yet
have
the
command
or
the
policies
yet,
but
I
pinged
the
issue
yesterday
and
Quinn
and
Nikita
and
Carolyn
all
jumped
on
to
that
thread
and
are
all
picking
up
pieces
so
that
one
is
actually
moving
ahead
and
hopefully
I'm
hoping
before
next
meeting.
I
E
A
A
O
A
Carolyn's
been
doing
doing
it
for
sake,
service,
catalog
and
she's
been
excellent,
with
getting
new
contributors
issues
and
figuring
out.
What
a
good
first
issue
is,
which
is
what
they're
pretty
much
writing
out
right
now
with
the
content
guidelines.
So
I
was
thinking
along
the
lines
of
her
doing
the
workshop
for
sig
leads
and
those
leads
could
like
dive
deeper
into
how
their
folks
could
better
issue.
A
O
A
E
B
L
J
A
Right,
I
think
we're
done
for
the
day
unless
anybody
has
anything
Oh
Luke
do
I
see
Lucas
on
with
dev
stats.
It
looks
like
we're
gonna,
possibly
get
a
new
skin,
which
is
awesome,
I
know
you're
working
with
Austin
I,
don't
know
if
you're
listening
anymore,
you
probably
tuned
us
out,
but
I'm
super
excited
for
the
work.
That's
going
on
on
the
front
end
with
dead
stats,
Zak
I
think
just
times
lose
a
champ
yeah
yeah
I
was
super
pumped
that
he
just
like
jumped
into
that.