►
From YouTube: SIG Architecture meeting 20171220
Description
A
All
right,
good
morning,
everybody
welcome
to
the
sig
architecture
meeting
for
the
communities.
Community
today
is
Thursday
December
21st,
2017
I
am
Jay
singer.
Demars
and
I
am
your
moderator
for
today's
meeting.
We
are
approaching
this
meeting
on
a
informational
basis
and
probably
just
to
get
an
idea
about
where
some
things
in
progress
are
at,
but
we're
not
gonna,
try
and
make
this
a
decision-making
effort.
So
without
further
ado
saw
Dahle.
You
are
number
one
on
the
agenda
to
discuss
the
permanent
home
for
current
ICSI.
B
Yeah,
so
this
is
an
F
9,
getting
container
storage
interface
into
kubernetes.
We
made
good
progress
on
it
and
got
it
out
as
alpha
a
lot
of
the
components
required
for
enabling
a
external
container
storage
interface
driver
require
sidecar
containers
that
know
how
to
interact
with
kubernetes.
The
idea
is
that
the
CSI
driver
itself
can
be
completely
agnostic
to
kubernetes
and
it
gets
paired
with
these
kubernetes
specific
sidecar
containers.
B
In
addition
to
that,
there's
some
example:
volume
plugins
we
wanted
folks
to
have
to
play
around
with,
and
some
utilities
for,
text,
testing
and
documentation,
and
things
like
that
for
development.
We
created
our
own
repository
github.com,
slash
kubernetes
CSI,
where
we
put
all
this
stuff
a
couple
of
problems
with
this
one
is
there's
no
official
CLA
on
it,
which
kubernetes
legal
is
probably
not
going
to
be
happy
whether
C
and
C
is
legal
or
whoever,
and
second
is.
B
We
have
a
couple
of
existing
kubernetes
repositories
where
this
stuff
should
probably
go
github.com,
slash,
kubernetes
or
github.com,
slash,
kubernetes
incubator,
and
we
don't
have
to
make
the
decision
in
this
meeting.
But
the
decision
that
I
would
like
to
make
is:
where
should
we
move
forward?
Should
we
migrate
these
this
route?
The
contents
of
this
repository
somewhere
else,
or
is
there
a
way
to
have
this
officially
kubernetes
blessed
and
make
it
okay,
where
it
is.
C
C
C
C
This
is
a
fairly
straightforward
extension
of
the
efforts
of
the
of
the
storage
sig,
whether
you
know
where
sub
projects
like
that
should
be
hosted
and
how
we
track
those
to
something
that
we
don't
have
good
process
around
right
now
and-
and
it
really
is
a
pretty
critical
problem,
so
I,
don't
think
anybody
necessarily
doing
anything
wrong.
I
think
it
just
really
highlights
the
need
that
we
need
to
get
get
this
stuff
figured
out
so
that.
E
D
D
A
D
D
Sorry
I
would
have
seen
this
I
think
the
only
way
it
isn't
gonna
work
is.
If
we,
if
we
somehow
force
people
to
register,
then
it
is
an
official
communities
project
and
then
we
can
have
automation
that
checks
for
the
CLA,
bots
and
code
of
conduct
and
all
that
stuff
I
feel
like
a
manual
process.
Here.
Is
it's
not
gonna,
not
gonna
scale.
F
F
Of
projects
that
conform
to
the
CLA
bought
and
I
guess,
the
code
of
conduct,
whatever
whatever
a
set
of
things
we
want
to
consider,
is
a
requirement
for
grants
project
and
by
doing
that
list
we
may
make
it
there.
There
is
less
pressure
to
become
an
official
project
if,
instead,
you
have
a
list
of
projects
that
are
conforming
to
the
community's
ethos.
But
in
this
specific
case
I'd
say
there
are
two
things,
one
of
which
is.
B
There
there's
two
sets
of
repositories:
one
is
the
container
storage
interface
repository,
which
is
completely
independent
of
kubernetes,
and
the
idea
there
is
it
hosts
the
spec
for
CSI,
which
any
CEO,
including
Bezos,
docker,
and
us
can
implement
the
components
in
this
particular
repository
or
components
that
are
only
for
kubernetes
CSI.
So
it's
a
quick.
C
B
C
D
C
Yeah
I
know
I,
hear
you
Brendan
I
I
think
there's
there's
two
ways
out
of
it.
We
can
have
org
sprawl
or
we
can
build
tool
ability
that
actually
essentially
reduces
the
amount
of
reliance
on
the
github
model
and
replaces
it
with
bots
and
stuff
right
and
we've
been
moving
further
and
further
down
that
path.
One
of
the
big
missing
pieces
there
is
just
managing
membership
based
on
yamo
files,
and
so
that's
a
big
big
missing
piece.
There
I'm
not
sure
that
doubling
down
on
relying
on
the
git
hub
or.
D
Channeling
Brian
a
little
bit
there,
but
but
but
I
also
think
it
works
to
it
than
just
the
board.
Membership
I
think
one
of
the
other
one
of
the
other
issues
is
the
decentralization
of
decision-making
about
when
you
can
have
a
new
org
right
like
if
we
put
everything
in
convinced
your
NetID
or
arm
a
sorry
Indy
everything
is
orgs
and
like
first
centralizing
decision-making
about
when
you
can
have
a
new
repo
and
I'm,
not
sure
that
scalable
eyes,
welled
up.
Okay,
all
right.
C
Well,
I
think
we
do
need
to
have
some
process
in
terms
of
what
code,
what
projects
is
kubernetes
as
a
project
signing
up
to
take
on
right
and
and
roughly
that
swivel
into
repos
and
and
whether
or
not
that
needs
to
be
a
heavy
process
or
super
sent
to
us.
I
think
there
needs
to
be
a
process
there.
Err
to
actually
take
that.
D
C
There's
I
hear
what
you're
saying
code
is
code
is
code.
It
should
we
shouldn't
stand
in
the
way
of
folks
writing
code.
There's
there's,
there's
other
implications
there
of
having
something
be
like
an
official
repo
and
and
like
there's,
both
legal
and
and
community
locations
of
that
that
I
think
we
have
to
think
through,
but
Joe.
C
D
C
C
C
D
Everything
it
comes
in
and
it's
a
practical
look
that
I
just
ran
into
is
like
with
the
virtual
cube
list.
I
I
can't
have
code,
come
in,
that's
not
CLA
effectively
and
so
like
right.
Now,
it's
under
the
Microsoft
CLA,
because
I
have
to
have
some
CLA
and,
and
so
then
I'm
gonna
have
to
basically
like
Ricci,
Elliot
and-
and
it
also
is
off-putting
right
if
someone's
coming
and
thinking
they're
contributing
in
general,
the
kubernetes.
C
C
That's
something
close.
The
loop
I
asked
personally
like
the
like,
like
starting
an
open-source
project
with
the
CLA
outside
of
this
CNC
F
is
a
difficult
thing
to
actually
get
right,
and
it's
going
to
definitely
it's
going
to
definitely
be
a
drag
on
contributions
like
when
we
started
doing
the
authenticator
stuff
with
AWS
the
relationship
at
the
CLA
versus
versus
doing
a
DC
Oprah
type
of
process.
If
we'd
been
a
CLA,
it
would
have
been
a
much
more
difficult
thing
to
actually
get
lined
up.
Then
the
second
thing
Matt
I,
totally
agree.
C
B
One
more
thing,
I
wanted
to
add
on
the
or
versus
repo
discussion.
We
have
multiple
components
and
ideally
we'd
like
to
leave
each
individual
component
in
a
separate
repo,
so
that
we
can
cut
branches
and
do
releases
for
that
particular
sub
feature.
Instead
of
having
one
mom
Ando
like
CSI
repo,
that
we
have
to
stuff
everything
in
which
makes
cutting
releases
much
more
challenging.
You.
C
Know,
I
think
that
that's
that's.
We
should
make
it
so
that
it's
easy
enough
to
create
repos
for
smaller
components.
We
had
this
discussion
and
CLI
yesterday,
hey
about,
as
we
start
taking
like
utility
libraries
in
packages.
Do
we
actually
put
those
in
the
cube
control
repo?
Do
we
put
them
in
like
say,
client
go
or
something
do
we
do
staging
stuff?
Do
we
create
lots
of
small
repos
or
one
big
sort
of
kitchen-sink
repo?
So
these
these
these
problems
aren't
unique
to
to
this
case
yeah.
D
I'll,
just
to
be
the
devil,
to
remember
a
time
when,
like
the
versions
to
do
of
different
things,
that
you
could
have
deployed
in
your
cluster
with
Easter
at
cube,
DNS
and
everything
else,
it
was
really
bad.
Actually
right,
and
so
there
is
some
degree
in
which
having
alignments
and
versioning
is
actually
not
a
terrible
idea.
But.
C
D
C
C
One
support
I,
sir
I
mean
I,
don't
know
anyway
yeah
so
so
so
sorry
I
think
getting
the
CLA
turned
on
yesterday
is
probably
a
high
priority.
There
VI
and
then
you
know
in
terms
of
like
wanting
a
place
to
land
this
and
so
I
think
this
is
definitely
it
yet
more
fuel
for
for
the
argument
that
we
need
to
actually
get
this
figured
out
sooner
rather
than.
B
B
E
E
D
We'll
we'll
get
on
it,
I
I
said:
I
took
action
to
go
and
suppose
something
I
have
opinions,
but
we
need
to
get
enough
people
and
steering
committee
to
agree
and
so
far
the
right
way
to
do.
That
has
been
to
propose
things
and
force
people
to
object,
as
opposed
to
try
and
build
consensus
in
the
group.
So
I'll.
C
E
C
E
D
I
guess
I
was
I,
would
really
agree
with
Joe
here
and
I
feel
like
we
built
this
project
so
that
this
stuff
shouldn't
matter
right
like
there
is
there
should
be
at
this
point
literally
nothing
that
you
that
being
in
the
kerbin
Nettie's
org
is
good
for,
except
for,
like
PR
and
PR,
probably
have
bad
reasons
being
in
the
world,
and
so
like
I
really
would
like
to
push
back
and
I.
Don't
mind
high
I,
don't
mind
bottlenecking
a
different
level.
C
D
No
and
I
think
there
are
things
where
we
should
definitely
do
that,
but
I
am,
and
this
is
why
I
have
always
pushed
for
a
differentiation
between
effectively
like
internal
sig
sponsored
projects
versus
external
I,
built
the
singie
project
right
like
if
it's
coming
up
organically
from
inside
a
sig.
Well,
then,
clearly,
it's
like
it's
closer
to
the
core
anyway,
just
because
the
sig
is
doing
it
rather
than
like
some.
You
know
some
external
questions,
I.
E
Don't
think
so
I
just
bright,
but
we
got
to
get
this
figured
out.
I
I'd
like
to
bring
up
one
use
case
we
haven't
talked
about.
There
are
a
number
of
companies
who
want
to
contribute
things
and
they
can
just
freely
contribute
to
kubernetes.
But
if
it's
not
part
of
the
kubernetes
org
now
they
have
to
jump
through
all
kinds
of
legal
hoops
which
stop
them.
That
is
currently
a
case
today
for
a
number
of
boundary.
That's.
E
B
We
had
this
issue
with
the
CSI
spec.
The
CSI
spec
was
a
collaboration
between
folks
from
kubernetes,
mezzo,
stocker
and
cloud
foundry.
We
went
out
created
a
github
repo
and
just
started
collaborating
there.
We
technically
are
not
under
the
CN
CF
CLA,
because
the
project
has
not
yet
been
become
part
of
the
CNC.
Yes,
so
we're
kind
of
flipping
around
without
a
CLA
right
now
and
we're
figuring
that
out
internally
within
that
group.
But
that
kind
of
issue
where
you
have
projects
that
are
being
incubated
not
yet
part
of
CN
CF,
not
part
of
kubernetes.
B
D
C
I
mean
so
that
yeah
this
is
there's
discussions
actively
on
going
with
the
CNC
F
to
essentially
I
hasn't
taken,
call
incubator,
because
there's
this
assumption
that
things
can
graduate,
but
essentially
some
sort
of
sandbox
where,
where
people
can
create
and
have
you
know,
projects
that
are
illegally
owned
by
the
CNC
a
yet,
there
is
no
sort
of
marketing
stink
on
it.
So
it's
just
a
way
for
them
to
get
those
legal
protections
without
necessarily
getting
the
lift.
G
So,
let's
see
in
that
sexual
like
the
send
books
for
for
the
projects,
but
again
or
somewhere
or
here
how
how
your
project
can
be
headed
to
CN
CF
as
an
official
project
even
to
if
you're,
looking
for
some
abilities
how
this
project
can
be
like
it
shouldn't
be
an
official
CN
CF
project
right,
but
should
be
protected
by
CN
CF.
They
understand
correctly,
did.
E
So
so
here's
a
question
no
to
and
and
I
don't
want
to
have
the
answer
now,
but
one
of
the
things
that
can
give
you
some
of
these
productions
is
Adi
Co,
which
the
CN
CF
solves
and
is
our
problem
that
if
it
wants
to
come
into
kubernetes,
then
you
have
to
do
the
translation
from
a
TCO
to
a
CLA.
But
if
we
did
D
cos
and
we
could
just
accept
the
DCO
when
something
comes
in,
would
that
solve
a
lot
of
the
issues?
Well,
I
want.
E
Yeah
well,
some
of
it
is
there
are
some
companies
where
they
can't
go.
Do
the
work
unless
it's
part
of
kubernetes
they
are
not
allowed
to
go,
contribute
right.
So
we
will
stop
certain
contributions
where
they
have
to
keep
it
internal
because
they're
not
allowed
or
they
have
to
go
through
lots
and
lots
of
legal
loopholes
to
jump
through
to
go.
Do
this
or
they
have
to
kind
of
avoid
their
lawyers
and
hope
they
don't.
E
Then
it's
like
oh
I,
can't
contribute
to
that
because
it's
not
part
of
kubernetes
and
now
I've
got
to
go,
get
permission
to
contribute
to
something
new
or
to
work
on
it
and
release
something
new
and
that's
a
lot
of
legal
loopholes.
And
that
has
been
a
complaint
that
has
come
up
more
than
once
on
this
issue
and
why
people
want
to
be
able
to
just
have
a
playground
in
kubernetes
to
go
work
on
these
things,
because
they
can
contribute
carte
blanche
to
kubernetes.
E
D
D
I
mean
we
gotta
weigh
these
things
against
each
other.
I
just
agree
exactly
exactly
I'm,
not
saying
like
we
should
slam
the
door,
but
I
think
that
we
should
understand
like
if
we
get
to
a
place
where
we
say
it's
all
under
one
CLA.
Is
that
good
enough,
and
can
you
then
take
that
back
to
a
company
and
say
like
hey
the
contribution
agreements?
The
same?
Can
we
get
a?
Can
we
give
a
sign-off
at
the
contribution
agreement
level
as
opposed
to
the
you
know,
the
org,
the
github
org
level,
so.
E
D
C
C
C
E
Now
so
I
I'm
just
actually
channeling
other
people's
issues,
not
my
own
just
to
highlight
the
thing
that
is,
that
causes
a
lot
of
heartburn
here
and
the
reason
we
do
things
the
way
we
do.
This
is
actually
not
so
much
an
issue
that
I
have
I'm
just
channeling
others.
So
that
way,
when
you
talk
to
it
realize,
there's
some
other
big
players
so.
G
F
It
can
be
my
words
corpse
will
then
say:
oh
well,
CNC
SEO
plays
what
we
care
about
and
maybe
maybe
make
it
easy
side
to
move.
It
will
definitely
get
easier,
so
it
feels
like
we
can
then
have
a
list
of
all
those
projects
which
might
lend
and
some
might
take
away
some
of
the
prep
sure
those
being
are
the
communities
or
it
feels
like
it's
a
no-lose
and
I.
Don't
think
it
actually
that
hard
I
think
that
she's
a
bot
so
the.
C
Question
in
my
mind,
Justin
I
think
this
is
a
question
for
the
CNCs
lawyers
is:
are
their
responsibilities
for
owning
ownership
for
random
code?
So
if
somebody
goes
through
and
take
something,
that's
patented
or
copyrighted
puts
it
under
a
cnc
fcl
a
license.
Does
that
create
headaches?
For
for
the
lawyers
right?
You
know,
you
know
it's
not
as
simple
as
being
like.
Let's
put
a
stamp
on
it,
I
think
there
might
be
other
implications,
and
so
there
might
be
some
level
of
somebody
has
to
look
at
it
together.
That's
not
insane
yeah
I
mean.
F
E
H
H
G
E
Yeah
is
there
a
way
to
formation
for
updating?
You
know
we
can
take
this
offline,
probably
because
we're
rambling
on
now,
but
to
to
make
the
BOP
more
automated.
So
we
can
do
some
of
this
more
automation
that
Brendon
talked
about
with
auditing
and
maybe
some
of
these
additional
projects,
but
I
can
ping
you
offline
about
that.
Yeah.
G
A
You
as
a
to-do
item
to
look
into
whether
this
year
and
CN,
CF
CLA,
could
be
applied
to
a
broader
suite
of
things
without
necessarily
having
to
be
under
the
auspices
of
CN
CF.
So
look,
let
us
know,
maybe
in
a
week
or
two
how
that
conversation
goes.
Thank
you,
Joe
Beda.
You
have
some
updates
on
the
kept
stuff
in
the
the
status
area.
There
can
you
let
us
know.
What's
going
on
there.
C
C
The
next
step
there,
in
my
mind,
is,
is
to
start
getting
something
that
can
actually
act
on
and
use
that
metadata
to
do
interesting
things,
because
all
you
have
kept
going
to
be
some
metadata
for
being
able
to
actually
understand
where
things
are,
and
so
that
led
on.
You
know,
based
on
the
last
sake,
architecture,
meeting
a
rabbit
hole
of
like
well.
C
Do
we
need
to
like
a
site
or
do
have
like
a
more
you
know,
community
site
that
brings
in
a
bunch
of
other
stuff,
so
I
started
a
thread
with
cig
architecture,
contraband,
sig,
Docs
and
like
hey,
what
should
we
do
for
a
site?
That's
community
oriented
that
can
include
the
Cape's,
but
also
maybe
other
contributor
guide
so
that
we
move
from
a
sort
of
pile
of
markdown
file,
spread
across
like
a
gazillion
repos
to
something.
That's
more
accessible
and
really
targeted
towards
users,
along
with
that
I
I.
C
Think
that
my
ideal
for
what
this
thing
would
be
like-
and
this
is
something
that
I've
been
talking
to
if
to
some
of
the
the
members
of
contra
backs,
you
know
individually
about,
is
I'd
love
to
get
to
the
point
where
it's
like
the
contributor
homepage,
where
it's
like
I
go
to
a
place,
and
it's
like
here's,
where
the
next
like
release
is
here's
where
you
know
we
are
with
respect
to
emerging.
You
know:
here's
like
we're
working
on
this
branch
on
Docs.
C
You
know
that
type
of
stuff
that
is,
like
you
know,
hey
I'm,
a
contributor
where
do
I
start
my
day
in
terms
of
looking
at
stuff
that
brings
together
all
that
stuff,
including
caps.
That's
what
I'd
love
to
see
that
turn
into
so
I
naively
started
a
mailing
thread,
saying
hey
what
I
got
to
do
to
get
a
site
up,
and
it's
no
bald
a
little
bit.
We
had
a
meeting
yesterday
and
the
the
recording
was
sent
out
to
to
the
cig
architecture
mailing
list.
C
C
C
We
would
decide
the
tool
chain
to
use
for
that.
Knowing
that
you
know,
there's
a
trade-off
between
being
doing
the
same
things
that
the
docs
folks
are
versus
stuff.
That
may
be
more
milliard
to
the
development
audience,
so
that's
kind
of
where
we're
at
right
now,
but
we'll
probably
end
up
creating
like
a
community
at
kubernetes,
dot,
bio
or
contributors,
kubernetes,
io
or,
like
other
names,
suggested
we
can
bike
shed
on
that,
but
creating
a
site
that
really
becomes
that
that
portal,
that
home
page
for
contributors,
so
that's
kind
of
where
we're
at
there.
C
C
C
Names
for
that
thing,
I
mean:
what
do
you
think
community
I
mean
like
community
is
bigger
than
just
the
folks
that
are
contributors
contributors?
Actually,
you
know
has
this
connotation
of
like
that.
Nobody
wants
to
own.
What
is
the
right
term
for
this
sort
of
project
facing
portal
versus
you
know,
user
facing
portal?
G
What
do
you
think
you're
yeah
I'd
like
I'd
like
to
see
it
is
a
user?
Looking
back
to
her
yesterday,
conversation
about
actually
the
same
idea
for
CNC
of
contributor,
sir
I'd
like
to
see
that
the
using
faced
in
portal
for
first
of
communities
for
potential
contributors
for
existing
contributors?
No,
no,
like
some
high-level
and
eBay
yourself.
C
A
C
C
C
C
C
And
rust
also
is
very
much
developed
up
or
focused
in
a
way
that
that
you
know
obviously,
kubernetes
is
not
because
kubernetes
actually
covers
a
whole
range
beyond
just
developers,
including
sort
of
operators
and
non-programmers
and
such
so
I,
don't
know,
I'm
looking
for
good
templates
here
in
terms
of
other
projects
of
how
they
actually
deal
that
duality
of
users
versus
developers.
Linux
is
obviously
like
I,
don't
know
like
random
aspects.
File
I
was
checked
into
and
to
get
along
with.
C
C
E
C
Just
real
I
mean
like
at
some
point:
the
name
becomes
a
token
and
people
really
wrap
their
heads
around
just
pick
one
and
go
something
like
that.
So
this
is
interesting.
So
Apache
has
this
page
across
the
entire
Apache,
which
is
Apache
org,
slash
dev,
which
is
Apaches
developers
in
contributors
overview.
This
covers
a
lot
of
this
sort
of
process
sort
of
like
legal,
easy
type
of
stuff,
that's
going
on
there,
but
it
seems
like
a
lot
of
these.
C
C
G
Jura
sauce
is
good
from
open,
steakhouse
supporter
Lincoln,
ditch
its
don't
open
standard
or
contributors
and
I'm,
not
sure
that
it's
it's
the
best
way
for
us.
I,
don't
want
to
include
a
contributor
recommendation
into
contribute.
Information
into
a
cabinet
is
the
commutation
because
it's
way
different
well.
C
I
think
the
quality
bar
and
the
requirements
that
are
gonna
be
very
different,
like
we
really
feel
like
like
the
the
the
developer
facing,
or
that
the
contributor
facing
portal
is
going
to
be,
but
I
even
I
said
it
developer.
Facing
the
contributor
facing
portal
has
got
to
be.
You
know,
up
to
date
and
and
sort
of
relevant
is
gonna,
be
more
important
than
being
pretty
or
grammar,
and.
E
I
would
argue
that
one
of
the
things
that
the
documentation
folks
been
targeting
at,
which
is
to
break
things
down
by
different
personas
or
different
roles,
to
look
at
who's
doing
what
to
make
it
very
clear,
I'm
in
this
role
and
here's
the
documentation
for
me
and
if
you're
consuming
kubernetes,
it's
a
radically
different
role
from
somebody
who
is
developing
it
and
that
the
content
you
need
and
so
making
that
distinction
very
clear.
No
matter
how
we
do
it
would
be
important.
Yeah.
C
I
think
you
know
this
is
something
that
the
jennifer
demoed
during
that
meeting,
which
is
a
sort
of
like
the
way
that
they're
thinking
about
guiding
people
to
the
correct
set
of
documentation
based
on
their
persona,
where
it's
like
I,
am
looking
to
do.
Why
right
type
of
thing
and
that
actually
brings
them
to
the
right
place.
I
think
that's
good
for
sort
of
inducting
people
into
this
world
for
new
contributors
and
leading
them
down
the
right
path
so
that
it
becomes
a
sort
of
soft
entrance.
I.
Think
there's
a
different.
C
A
I
think
that
there's
real-world
concerns
here
that
are
gonna
be
solved
by
having
something
like
this,
for
example,
holder
turn
around
what
documents
are
required
for
or
what's
required
to
do
the
release
you
know
so
the
document
deadline
is
in
10
days
the
code
freezes
in
7
days,
or
you
know
some
some
kind
of
interactive
things
like
that
would
be
tremendously
valuable
to
the
community.
I
mean
that
sort
of
contributor
level
single-pane
dashboard
would
be
amazing.
C
Well-
and
we
do
this
stuff
with
like
announcements
at
the
community
meeting
right
but
like
those
are
sort
of
like
point
in
time,
and
then
they
show
up
in
the
notes
and
maybe
they
show
up
in
an
email,
you
know
getting
that
stuff
to
the
yeah,
so
inverting
that
a
little
bit
I
think
so
that's
there.
So
that's
what
I'm,
gonna
try
and
get
you
know
work
with.
You
know,
or
at
least
kick
that
off
and
get
some
of
that
movement
in
the
right
place.
Yeah
there
I.
A
C
C
So
the
idea
is
that
that
what
we
mean
is
what
we
accomplished
is
that,
like
we
can
do
a
website,
we
have
decided
that
it's
not
insane
to
have
that.
What
might
not
be
part
of
kubernetes
IO
and
that
provisionally
made
contributes,
is
going
to
be
the
one
sort
of
pointing
that
thing
long
term,
because
everything-
and
my
gut
is
that
we
want
to
turn
kubernetes
slash
contributor,
that
github
repo
into
the
thing
that
compiles
into
that
website.
And
so
we
just
build
on
that.
F
C
It's
hilarious
because
you
look
at
these
open
source
projects
that
are
more
sort
of
front-end
or
oriented,
and
they
have
these
like
websites
like
that's
what
those
folks
did
I
mean
while,
like
you
know,
kubernetes
has
sort
of
you
know:
media
for
internal
infrastructure.
Cuz,
like
we
all
know
how
hard
a
command
line
driven
website.
G
C
That
was
her.
She
said
she
had
a
branch
/
PR,
or
that
was
not
good.
She
was
just
playing
with
sort
of
prototyping.
Some
of
this
stuff
I
mean
feel
free
to
reach
out
to
her
and
actually
see.
Okay,
I
can
only
but
I'm,
not
sure
where
that
work
in
progress
is
and
how
much
of
that
is
on
a
branch,
how
much
it
is
for
personal
stuff
versus,
because.
G
C
And
I
mean-
and
if
we
can
actually
get
this
sort
of
you
know
community
portal
stuff
up
and
running
and
established
that
as
a
pattern,
then
that's
the
type
of
thing
where
it
would
be
great
to
have
an
index
page
at
the
CNCs
saying
like
hey.
If
you
want
to
get
involved
in
in
these
projects,
here's
their
community
portal,
here's
the
way
to
actually
yeah.