►
From YouTube: SIG Contributor Experience 20180530
Description
Notes available here: https://docs.google.com/document/d/1qf-02B7EOrItQgwXFxgqZ5qjW0mtfu5qkYIF1Hl4ZLI/edit
A
C
D
A
Okay
graph
for
the
community
meeting
of
the
week
is
there
anybody
who
has
something
that
they
they
would
like
to
show
off.
D
Yeah,
so
he's
actually
gonna
do
an
introduction
to
the
kept
process
itself:
okay,
like
an
intro
and
then
from
then
on
we'll,
have
like
a
little
section.
That's
like
this
week.
Here's
two
caps
that
were
submitted
to
here's
two
that
we're
closed.
This
keps
open
and
closed
for
discussion,
that
sort
of
thing
to
kind
of
get
more
visibility,
two
caps,
but
I
think
him
and
Jo
had
lunch
and
and
I'd,
given
them
feedback
that,
like
I've,
contributed
to
two
caps
and
I
still
am
not
clear
on
the
process.
D
D
I,
just
I
added
it
to
the
agenda
because
I
know
we
were
discussing
it
last
week
and
I
saw
stuff
drive
by
on
github
and
I
was
wondering.
Are
we
all
set?
That
was
mostly
a
question
for
Christophe
like
I,
think
we're
all
satisfier
security
contacts,
for
our
sake,
I
mean
not
or
is
it
the
whole
repo
I'm,
not
sure,
and
he
could
be
okay,
so
I
don't
know
Christophe.
D
F
F
F
G
F
So
we
have
at
Cooper
Denny
thought:
io
/
security.
We
have
there's
a
very
detailed
page
that
lists
like
what
we
consider
a
security
vulnerability
through
to
contact
and
what
information
to
include
so
yeah.
That's
on
a
kubernetes
done,
iOS,
5
security.
All
these
files
need
security
contacts
file
and
all
the
repos
also
say.
This
is
not
a
public
disclosure
path.
F
We've
used
Cabrera's
at
iOS,
5
security,
not
to
the
right,
the
right
place
to
go
and
the
process
is
detailed
there
too,
but
at
a
very
high
level
if
the
information
gets
disclosed
to
para
security
team,
the
security
team
kind
of
has
a
rotation
of
who's
on
point
to
deal
with
a
security
issue.
So
there's
always
somebody
from
that
team
is
able
to
respond
in
a
timely
manner.
F
They
triage
the
issue
and
figure
out
like
how
impactful
is
it
and
who
do
we
need
to
bring
in
to
be
able
to
fix
it,
and
then
they
kind
of
proceed
from
there
and,
depending
on
the
type
of
vulnerability
and
the
severity
they
will
either
give
heads
out
to
distributors.
But,
like
hey,
you
know
right
or
DKE.
G
F
These
files
are
very
specifically
so
that
the
product
security
team
knows
like
who,
like
user,
specifically
that
are
responsible
for
the
code
and
that
who
and
that
those
users
have
already
like,
read
and
agreed
to
the
embargo
policy,
so
that
if
they
are
disclosing
information,
those
people-
these
are
the
people
who
will
uphold
the
embargo
and
be
able
to
like
triage
an
issue
to
get
get
it
better.
These
are
these
are
just
internal
contact.
The
public
stuff
is
always
ready.
It's
not
IO
flash
security.
B
Yeah
so
I
don't
know
I,
don't
kind
of
don't
know
how
to
go
at
approaching
or
an
introduction
here,
but,
like
so
I
saw
a
while
ago.
There
was
this
thing
called
pensive
on
or
pensive
and
know
how
Harry
Potter
people's
pronounce
it
there's
a
so
there
was
an
extension
on
the
slack
channel
which
basically
tries
to
automatically
answer
questions
for
you.
I
actually
I
saw
that
it
was.
B
The
one
interesting
thing,
though,
is
that,
like
I've,
been
I've
been
part
of
this
community
for
like
well
part
of
the
slack
channel,
for
you
know
something
like
eight
months
at
this
point
and
what
I've
been
using
to
train
my
model
or,
like
my
actual
chat
bot,
was
you
know
one
of
the
most
one
of
the
most
active
slack
channels,
which
is
the
kubernetes
slack
general
right.
So
what
I'm
trying
to
propose
is
you
know
putting
this
extension
onto
the
kubernetes
slack,
so
that
I
mean
the
basic
idea.
Is
that
it's
it's
about?
B
Like
answer
trying
to
automatically
answer
questions
for
people
like
if
somebody
you're
new
comes
on
the
channel,
they
don't
know
something
and
they
ask
a
question.
I
mean
if
you
look
at
the
current,
you
know
channels
and
look
at
the
current
questions.
There's
a
million
questions
that
are
just
never
answered
and
you
can
look
at
it
that
a
lot
of
them
probably
can
be
I,
don't
know,
I
can
share
screen
and
do
a
demo
or
so
it
kind
of
did
like
a
video
or
I
posted
link
to
the
video
there.
B
So
I
mean
I
kind
of
pre.
You
know
pre
created
this
example,
just
in
case
cuz,
you
know
I
get
nervous
in
front
of
demos,
I
guess,
but
so
basic
idea
is
that,
like
somebody
comes
on,
this
channel
asks
a
simple
question
like,
for
example,
is
like
hey:
where
do
I
find
the
you
know
focal
terms
of
service
and
based
on
previous
conversations,
this
was
already
stored,
so
this
will
come
up.
You
know
this
will
come
up
with
like
an
automatic
answer
like
hey.
B
Have
you
tried
any
of
these
things
before
and
then
you
can
say
yes
and
they'll
be
kind
of
useful
for
us.
Also,
if
you
click
yes,
it'll
kind
of
let
the
channel
know
like
hey.
This
conversation
has
already
been
answered,
or
this
this
questions
are
gonna,
be
answered
or
I'm.
Gonna
click
no
and
then
I'll
know
that
you
know
that
stuff
is
not
useful
and
I'll.
Try
not
to
show
it
up
as
much
anymore.
B
So
the
basically
where
this
kind
of
content
comes
from
is
one
of
two
places,
so
the
first
place
is
additionally
from
other
conversations,
correct.
Well,
there's!
So
you
know
again,
this
is
just
like
a
conversation,
I
kind
of
had
myself
earlier
on
a
test
channel.
You
know
I'd
kind
of
said,
like
hey
where's,
the
privacy
policy
I
had
like
a
support.
Connection
just
say,
like
hey
check
out
this
channel,
and
then
you
know
like
so
what
happens
is
basically
the
extension
will
figure
out
that
this
is
a
useful
conversation.
B
So,
as
you
imagine,
like
people
are
talking
through
the
through
the
channel,
you
know
this
thing
will
pop
up
and
roll
and
smell
like
hey
this
useful.
This,
like
seems
like
a
useful
question-and-answer.
Can
we
store
this
in
the
future?
So
the
idea
is
that,
like
yeah,
this
thing
will
detect
us.
If
it's
an
important
question,
you
click
yes
at
some
point
loads
guess,
like
is
a
little
slow
today,
yeah
yeah
minutes,
I
get
that
is
so
what
it
does
is
like
tries
to
understand.
B
The
question
tries
to
kind
of
summarize
it
and
then
it
says,
hey.
You
know
like
this
is
an
answer.
So
then
what
the
person
can
do
is
say,
like
you
know,
maybe
remove
some
of
the
you
know,
clutter
text,
that's
unnecessary!
You
know
like
this
is
kind
of
unnecessary
right
and
then
click
store,
they'll
store
the
conversation
or
store
the
context,
and
then
the
future
will
show
up.
So
this
is
the
first
source
of
this
kind
of
information,
and
then
the
second
source
would
be
then
scraping
something
like
kubernetes.
B
G
E
Yeah
I
think
this
is
really
cool
and
definitely
helps
to
answer
the
the
standard
questions
that
come
up
all
the
time.
I.
Think
tools
like
these
are
great
definitely
I
also
think
it
ties
kind
of
into
the
conversation
we
had
a
few
weeks
ago,
George
around.
What's
it
called
donut
meeting
people
online
in
slack,
it's
another
slack
integration
as
well.
So
if
you
have
a
question
and
they
might
not
get
answered,
then
you
might
be
paired
up
with
someone
who
actually
can
answer
that
question.
E
B
B
You
know
the
hope
over
a
couple
of
months
over
the
short
term
is
to
figure
out
like
okay,
maybe
I,
don't
know
the
answer,
but
hey
have
you
tried
talking
to
this
person
this
person
might
know,
and
by
kind
of
facilitating
that
question-and-answer,
you
actually
have
more
information
about
like
okay.
Well,
this
person
knew
the
answer,
but
then
now
I
can
actually
see
that
conversation
and
record
that
conversation
as
well
very
cool.
B
D
However,
the
way
that
was
structured
is
bob
who
couldn't
be
at
today's
meeting
and
I
would
get
a
ton
of
questions
and
that
we
would
individually
go
to
them.
It
sounds
like
this
lips
it.
The
other
way
around
is
you're
depending
on
the
users
of
the
channel
to
say.
Okay,
someone
answered
me
I
craft,
the
question
so.
B
D
B
So
the
only
message
is
it
does
actually
send.
Is
that
if
you,
if
you
get
it
quite
like,
if,
like
you
ask
me
a
question
and
then
I
you
know,
I
get
a
or
sorry
if
I
ask
you
a
question
and
then
I
get
a
notification
like
hey
this,
you
know.
Have
you
tried
this?
If
I
click?
Yes,
then
it
will
notify
the
channel
that
my
question
was
answered
so
that
you're,
not
you
know,
so
other
people
aren't
trying
to
answer
my
question.
Okay,.
I
Yeah,
this
is
really
cool,
just
just
three
questions.
One
of
the
thing
is,
you
know
when
people
ask
questions
many
times
there
are
multiple
people
off
his
phone
right
so
many
times.
The
answer
is
not
just
like
a
you
know,
one
single
answer:
it's
like
a
discussion
and
you
know
then
you
in
chili,
there's
like
okay
I
got
it
now
right.
I
You
know
for
something
like
Stack
Overflow,
for
example,
where
people
like
10
10,
15
answer
it
in
and
the
users
say
this
is
the
right
answer.
So
I
know
this
is
the
one
you
know
satisfies
the
users,
need
right
and
that's
the
answer.
Ideally,
you
want
to
show
it
to
as
response
to
the
question
so
how
I
mean
with
the
tool
I'm
just
learning
with
consideration
for,
for
that
kind
of
you
know,
questions
yeah.
B
It's
a
good
question,
actually,
so
what
we're
doing
so?
What
we
do
is
we
monitor
not
just
like
question
and
answer
what
we
do.
Is
we
like
kind
of
detect
a
question
and
we
monitor
the
entire
conversation
so
that
we
are
kind
of
like
the
goal
of
this
thing
is
like
figure
out
like:
where
is
that
conversation
where
it's
like
people
are
discussing?
What
is
the
right
approach?
B
And
finally,
when
that
kind
of
weird
thinking
that
that
conversation
is
over
some
heuristics
and
some
modern
data,
we
actually
summarized
that
conversation
and
we
try
to
remove
all
the
unimportant
stuff
and
we
show
that
message
of
like
do
you
think
we
should
store
this
conversation?
We
show
basically
to
the
most
active
user.
That's
not
the
person
asking
the
question.
It
was
kind.
B
So
I
mean
we'll
basically
summarize
this
thing
show
it
to
a
person,
that's
the
most
like
active
person
in
that
conversation
and
get
them
a
summary
and
say:
hey.
Can
you
summarize
this?
The
other
side
of
that
is
like
if
people
are
talking
and
we're
not
like
sure
of
you
know,
if
they're
like
new
to
the
channel,
they
might
not
know
about
this
yet
or
something
like
that.
We
can
whitelist
the
to
only
certain
people
are
able
to
add
questions
while
everybody
gets
answers,
cool
thanks,
yeah.
B
B
D
B
So
I
mean
you
don't
have
to
wait
a
while
as
soon
as
there's
questions
as
soon
as
there's
like
stored
answers.
I
can
start
answering
those
things
it's
just
about
like
like.
Because
of
this
is
a
you
know
fairly.
New
I
want
to
kind
of.
Do
it
slowly,
not
because
of
like
I.
Just
don't
want
to
annoy
the
crap
out
of
people
right
so
I
want
to
make
sure
that
the
relevance
is
up.
B
D
As
long
as
it's
not
spamming
by
default-
and
it's
doing
all
the
learning
in
the
background,
then
yeah
so
I'm
generally
a
plus
one
to
this,
because
I
really
I
use
the
Pennsy
fought
a
lot.
Even
though
a
lot
of
the
factoids
were
like
for
my
own
personal
they're,
like
what
time
is
a
community
meeting,
I
mean
they
were
just
silly.
Questions
like
that
that
I
just
used
in
contributes
but
I
I,
think
that
we
definitely
would
need
to
write.
There's
like
some
details.
We
should
go
over
right
like
who
owns
the
data.
You
know.
B
That
so
yeah,
definitely
you
guys
own.
The
data
I
mean
I
have
like
you
know
the
full
Terms
of
Service
and
Privacy
Policy.
If
you
care
about
any
of
that
stuff,
yeah
I
mean
I.
Guess
the
only
kind
of
question
with
all
this
stuff
is
with
the
world
being
part
of
GDP
are
I,
don't
know
if
you
guys
have
a
have
considered
like
I,
don't
know
how
that
slack
channel
kind
of
works
in
terms
of
like
you
know,
if
you
have
somebody
in
the
UK
that
leaves
the
slack
Channel.
What
do
you
guys
do.
D
Yeah
I
don't
know,
I
was
kind
of
hoping
we
weren't
gonna
talk
about
GDP
our
last
week,
yeah
so
yeah,
but
I
mean
to
me.
It
feels
like
those
are
just
crossing
the
T's
and
dotting.
The
I
I
mean
I
think
we
should
take
this
probably
to
the
mailing
list.
Okay,
yeah
I
get
feedback
as
Paris's
in
here
in
a
few
just
kind
of
outline.
What
you
want
to
do,
I'm
generally
plus
one
like
I,
was
telling
it
p.m.
even.
If
it's
only
terrible
and
gets
you
know
a
few
hundred
or
something
interceptions
a
day.
D
Let's
say
that's
like
it
can
help
a
lot
of
people
as
I
was
going
through
the
questions
there's
just
so
much
unanswered
stuff
that
just
gets
churned
through
that
channel.
It
was
like
even
if
worst
case,
all
that
does
is
like
hey
I
noticed
no
one's
answered.
Your
question
go
post
on
Stack
Overflow.
That
would
be
like
way
better
than
right.
Now
we
just
people
just
tend
to
get
ignored
so
I'm
generally
+1.
D
Yeah
and
then
what
we
did
is
I
think
we
turned
it
on
for
for
pen,
see
if
I
think
we
turned
it
on
for
novice.
First,
then
we
noticed
we
weren't
getting
any
data
and
then
turn
it
on
for
users
and
then
we
still
weren't
getting
any
good
data.
So
I
don't
know
we
might
want
to.
Try
contributes
channel
first,
maybe
with
some
of
our
stuff
or
not.
Probably
novice
first
I
think
is
that's
only
a
few
thousand.
How
many,
how
many
people
are
in
novice.
E
D
B
I
B
I
I
E
E
Then
you
can
convert
it
into
PDT
or
whatever
you
want
to
do,
but
it's
essentially
documenting
all
the
non-coding
roles
of
the
project
and
how
to
help
out
with
those
and
starting
with
a
section
in
the
contributor
guide,
and
there
are
a
bunch
of
different
interested
people
for
this.
So
if,
if
you
want
to
be
a
part
of
this,
make
sure
that
you
reach
out
to
know
what
as
well
so.
H
We
haven't
really
formally
figured
out
what
we're
gonna
do,
whether
it's
gonna
be
a
project
or
working
group
or
if
it's
just
for
people
on
a
zoom
or
what
so
we're
just
throwing
it
out
here
to
engage
interest.
Make
sure
everybody
that
had
some
idea
once
that
wants
to
be
involved
can
get
involved,
expand
it
once
we
get
past
our
first
okay.
What
are
we
actually
gonna?
Do.
A
H
E
F
F
Github
now
supports
updating
label
descriptions
like
first-class
label
descriptions
by
the
API
it
didn't
before.
You
will
had
to
go
through
the
UI
to
do
it
so
now
that
they
support
through
the
API.
We
can
actually
push
a
lot
of
the
descriptions
that
Aaron
had
written
written.
We
can
actually
push
them
up
to
the
API
and
they
display.
When
you
look
at
the
label
list,
it's
pretty
so
I'm
gonna
do
that
I
needed
to
like
edit
down
some
descriptions
because
there's
a
character
limit
of
a
hundred
characters
and
some
of
them
were
very
wordy.
F
So
the
code
itself
has
been
reviewed
and
tested
and
I've
actually
already
pushed
out
it
out
to
community
itself.
But
I'm
gonna
push
the
button
and
roll
it
out
to
everybody.
But
if
anybody
wants
to
review
those
label
descriptions
and
maybe
make
suggestions
on
better
ways
to
word
it
because
some
of
them
are,
they
have
to
be
buried
Turks
to
fit
in
the
hundred
character
limit.
So
anybody
wants
to
review
that.
I
would
appreciate
that.
F
So
when
you
create
a
new
repo
like
it'll,
create
a
repo
called,
the
label
called
buck,
but
we
actually
use
kind
flash
bug
to
denote
the
same
thing
so
that
eighty
129
migrates
one
label
to
the
other
and
creates
a
description
for
it
and
basically
makes
it
a
first-class
label
as
far
as
our
label
thinking
tool,
but
that
one
because
it
will
affect
existing
labels
on
repos
like
actually
migrating
and
changing
what
a
label
is
called
I
need
to
get
notifications
out.
For
that.
F
F
We
might
not
be
able
to
do
like
the
priority
failing
test
stuffs
because
of
the
the
way
the
milestone
Munder
for
the
relief
team
is
set
up,
but
we
might
be
able
to
move
some
of
the
other
like
kind
support
and
that
kind
of
stuff
into
their
their
final
spots,
as
well
as
good.
First
issue.
I
want
to
get
a
good
first
issue
out
there,
so
we
can
start
using
that
move
that
one
along
I.
G
Mean
I'll
say
the
one
change
that
required
extra
bits
where
I
would
rather
wait
until
we've
disabled
the
milestone
Munzer
in
favor
of
prow
and
moved
to
tied
is
priority
failing
test.
The
other
kind
changes
really
don't
affect
anything,
and
so
those
can
be
implemented
at
any
time,
and
that
includes
basically
blessing
two
of
the
kind
labels
and
marking
the
rest
is
deprecated
the
so
the.
G
F
G
Basically,
two
open
questions
with
good,
first
issue
that
just
honestly
need
somebody
to
make
a
decision
on
and
write
that
this
is
not
one
well
and
possibly
coated
up.
So
one
question
is:
how
does
good
first
issue
interact
with
help-wanted,
and
the
second
question
is:
what's
going
to
be
our
procedure
for
reviewing
updating,
expiring,
good
first
issue,
tagged
issues
to
make
sure
that
we
don't
end
up
with.
You
know,
300
good,
first
issues
that
are
things
that
are
actually
way
out
of
date
and
we
don't
want
to
implement
it.
F
Yeah
the
first,
the
first
question
seems
fairly
simple
to
me:
I
feel
like
they
should
be
additive
like
if
a
if
a,
if
an
issue
is
marked
good
first
issue,
it
should
also
have
Help
Wanted,
because
there's
call-outs
in
the
github
UI
for
Help
Wanted
issues,
so
the
two
labels
I
think
could
be
easily
additive
and
whichever
one
they
search
is
somebody's
just
looking
for
out,
wanted
they'll
find
and
notice
the
ones
that
also
say
good
first
issue
or,
if
you're
searching
directly
for
good
first
issue.
They'll
just
find
those
so
I.
F
C
Hey,
can
you
all
hear
me
and
I,
don't
believe?
Oh
god,
I'm,
not
muted,
sorry
about
that
yeah!
No
I
was
saying
that
good
cursed
issues,
so
actually
what
Phil
Whitlock
has
been
doing
for
me,
as
he
literally
curated
three
issues
for
me
to
get
me
started
on
a
project
and
those
labels.
Actually
implicitly,
in
this
case,
come
with.
You
know,
grouchy
support
from
upstream
and
just
now,
Garage
sorry
that
was
the
wrong
word.
I'm,
really
tired!
C
Sorry
guys
they,
basically
what
it
is,
is
a
way
to
tie
that
into
getting
started
on
a
new
repo
or
a
new
project.
You
know
to
have
a
new
contributor
cohorts.
Something
like
that.
I
see
would
be
really
awesome
to
just
kind
of
tie
that
in
I
know.
That's
asking
a
little
bit
more
effort
from
whoever
made
those
issues
right
because
help
one
it
is
like.
Oh,
my
god,
I
need
help.
C
I
can't
deal,
but
something
like
good
first
issue
might
be
nice
if
it
also
came
with
like
this
is
a
great
way
and
we
will
help
you
grow
into
the
repo.
Does
that
make
sense
if
we
could
somehow
combine
those
two
efforts?
That
would
be
pretty
great
because
it
looks
like
we
have
this
resource
for
like
well,
how
are
we
going
to
grow
like
new
contributor
cohorts
and
areas
and
well
I
feel,
like
you
know,
good
first
issues
are
a
natural
breeding
ground
for
that
sort
of
thing.
F
Yeah
I
think
the
two
pieces
are
the
the
technical
bits
to
make
it
happen
and
have
the
tooling
and
that
kind
of
stuff
and
the
policy,
and
if
somebody
feels
strongly
about
the
policy
like
I'd
suggest,
let's
just
get.
Let's
get
a
PR
open.
Let's
get.
Let's
get.
Let's
get
some
docs
around
it
of
what
what
we
want
to
establish
lease
is
an
initial
policy
and
we
can
it's
always
go
and
revisit
later
the
the
technical
bits
of
implementing
the
the
command
and
getting
the
label
set
up
and
synced
across
all
the
repos.
F
Okay,
great
yeah,
again
the
call
to
action.
There
is
any.
If
anybody
has
cycles
to
review
the
label
description
changes
in
eighty
one,
twenty
eight,
it's
just
the
one
filed
the
labels
yeah
mo.
That
would
be.
That
would
definitely
be
helpful
I'm
all
if
anybody
has
any
last-minute
changes.
I
can
implement
those,
but
otherwise
I'll
probably
merge
by
end
the
day.
A
D
I
will
go
really
fast,
so
part
of
the
campus
be
weekly
sharing.
The
stats
can
y'all
see
that
the
discuss
prototype,
so
everything
was
going
really
good,
as
you
can
see
here
from
our
monthly
stats
and
the
memorial,
they
happened
and
we
got
crushed
but
other
than
that.
The
monthly
stats
are
looking
good
as
far
as
user
growth,
and
we
are
now
at
about
450
users
here.
So
everything
appears
to
be
on
track.
One
thing
I
did
want
to
ask
is,
if
you
have
content
to
post
on
the
site,
I'd
really
appreciate
it.
D
So
we've
been
I've
been
asking
people
who
have
been
posting
like
kubernetes,
related
announcements
that
be
kind
of
maybe
a
little
bit
too
spammy
for
a
kubernetes
developer
list,
so
I've
been
reaching
out
to
them
to
post,
hey.
You
can
post
your
announcement
here
and
a
lot
of
the
ecosystem.
People
out
there
have
been
posting,
really
classy
announcements
about
their
products,
and
things
like
that,
so
it
gives
people
a
place
to
go
and
our
tube
cuddle
thread.
D
It's
a
tips
and
trick
tricks
thread
which
is
undiscussed,
has
been
really
blowing
up
thanks
to
some
help
from
the
CN
CF
kubernetes
twitter,
echo.
So
by
far
this
has
been
our
most
successful
thread
so
far
and
there's
lots
of
great
information
there
what's
really
great
about
this
is
this
is
something
that
will
be
off
topic
for
Stack
Overflow
and
maybe
not
as
easy
to
grok
through.
D
D
Lower
right,
oh
there,
it
is
big
red
button.
The
second
one
is
Justin
Garrison's
posts
of
how
is
kubernetes
failed
for
you,
which
has
the
second
highest
number
amount
of
views
this
week
at
845,
but
no
one's
posted,
so
I
think
people
are
afraid
so
I
just
thought
that
was
that
was
kind
of
interesting.
So
that's
your
stats
on
for
the
week
and
thanks
for
josh's
been
posting
a
lot
of
great
content.
Lately,
the
more
the
better.
D
I
think
part
of
the
you
know,
especially
because
there
is
overlap
of
a
lot
of
the
other
stuff
I
think
for
now
that
that
really
helps
out
and
I
think
I've
got
some
ideas
of
existing
mail
lists.
That
I
think
can
move
over
pretty
well
I'm,
not
quite
ready
to
like
rip
that
band-aid
off
and
make
a
lot
of
enemies
quite
yet
so
just
letting
the
site
grow.
Naturally,
now
gonna
had
a
list
of
the
site.
D
There's
a
blog
post
now
on
the
kubernetes
official
blog
that
went
live
today,
so
we're
gonna
naturally
grow
it
a
little
bit
and
give
give
people
a
reason
to
go
there,
as
opposed
to
like
some
of
the
other
open
source
projects.
We
looked
at.
You
know
kind
of
hey,
you're
moving
and
we're
shutting
the
old
thing
down
and
that
kind
of
jarred
a
lot
of
people.