►
From YouTube: Kubernetes Community Meeting 20170831
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
B
C
Architecture,
a
machinery
so
I
wanted
to
sort
of
like
just
get
the
ball
rolling,
open
up
a
discussion
figure
out
like
how
we
would
kind
of
approach
this,
because
obviously
I
think
the
docks
would
probably
end
up
on
the
communities
that
I
Oh
website.
But
we
were
planning
to
coordinate
like
you
know
what
people
are
things
to
be
and
I'm
kind
of
what
it
should
look
like
and
that
sort
of
thing
and
I've
been
working
on
a
larger
project
called
user
journeys.
So
the
idea
is
create
kind
of
a.
C
C
B
Sorry,
thanks
for
starting
this
discussion-
and
there
has
been
some
additional
discussion
about
whether
or
not
these
remain
very
user
focus
versus
contributor
focused.
So
that
may
be
part
of
this
conversation
in
your
issue
892
as
well,
but
this
is
this
should
be
a
really
important
thing
and
you're
right.
It's
gonna
cross.
B
C
Just
used
to
be
a
lot
interested
in
like
adding
some
documentation,
specifically
for
Co
contributors
to
the
kubernetes
project.
Right
now,
our
documentation
more
focused
on
like
users,
like
application
developers
like
poster
operators,
that
sort
of
thing,
but
there
seems
to
be
a
need
to
kind
of
help,
onboard
people
who
are
contributing
to
the
like
carbonates
codebase.
You
know
showing
them.
Maybe
some
design
patterns,
common
design
patterns
that
you
couldn't
burn
anything
like
that,
so
that
they,
you
know
to
help
Gotham
when
they
write
code
or
kubernetes.
C
D
Long
here
to
drive
it
and
find
contributors
who
are
knowledgeable
to
contribute
content,
the
existing
Doc's
are
in
the
community
repo,
the
contributors
about
directory,
I
begged
for
help
a
while
ago
and
organizing
does
didn't
really
get
much
help
couple.
A
couple
of
attempts
that
didn't
get
finished
so
I
think
the
great
thing
I
do
you
think
the
documenting?
There
are
multiple
audiences
for
documentation,
as
we
discussed
in
the
TOC
discussions,
and
things
like
that.
D
There
are
various
flavors
of
into
user
just
like
cluster
admins
application
operators,
application
developers,
communities
that
I
know
should
be
focused
on
users.
There
are
developers
who
are
building
on
top
of
communities
using
the
client
libraries
that
publish
I,
think
that
is
fair
game,
because
they're
different
user
base
their
gimme
those
two
additional
things.
On
top,
so
we
find
it
might
make
sense
to
have
I'm
using
indigenous
plan
writers
or.
D
There
already
and
the
only
envisioned,
using
this
tablet
approach
different,
we
show
different
mazes,
are
missing
the
API
there,
and
so
some
things
like
how
do
you
see
our
DD,
which
is
intended
to
be
used
for
people
to
build
on
top
of
kubernetes
things?
We
would
add
tip
along
there
for
that
pursue
another
audience
that
developers
building
opportunities,
but
contributors
who
are
contributing
to
communities,
project
inquiries
or
exam
repos
I
think
is
fine
for
that
information
to
stay
on
github.
D
D
Into
a
different
place
for
what
it
is
that
the
current
community,
new
repo
but
I
would
want
to
preserve,
get
history
when
we
move
in,
like
we
did
last
time,
but
I
think
the
biggest
blocker
is
actually
getting
contributions
from
people
who
actually
know
what's
going
on
to
help
with
that
to
people.
You
know
what
the
current
state
is
to
know
with
industries,
so.
E
I
will
just
say
from
the
infinitive
perspective:
it
can
be
a
little
confusing
it's
just
or
go
to
one
place
for
one
set
box
in
a
completely
different
place
for
a
different
set
of
thoughts.
I
think
this
idea
that
keyword
is
not
an
either
should
be
only
Easter
facing
I'm,
hoping
that
it's
calm
that
is
documented
somewhere
and
you
know
I
think
like
it
just
seems
weird
to
me
that
developer
Docs
should
be
devoted
to
a
lesser
level
of
user
experience
or
certification
or
what
happened.
I
think
developer.
Documentation
is
just
as
important
as.
E
E
E
Concerted
effort
over
weeks
actually
wants
and
as
a
single
individual,
over
a
single
to
be
with
individual
books
to
dozens.
It's
not
something
that
not
be
organically,
contributed
to
do
with
little
pilots
right,
it's
an
entire
folder
that
needs
to
be
pushed
on
at
home
and
I
think,
instead
of
getting
caught,
you
might
actually
be
searched
through
the
community.
The
question
might
be:
other
races
should
be
dredged
through
the
existing
content.
B
D
B
C
D
B
D
I
think
I
think
a
few
of
these
things,
like
Indian
conventions,
we're
trying
to
update
that
baptism.
The
contributors
devout
directory
kind
of
undertaking
that
to
take
architecture,
Sydney
care
machinery,
in
addition
to
the
guide,
crowded,
building
guys.
What
we're
looking
to
do
is
actually
try
to
create
an
SDK
to
make
it
easier
to
build.
If
you
guys
so
not
just
documentation,
I
mean
II
do
need
to
document
this
date
that
exists.
So
that's
again
a
situation
where
that
documentation
is
spread
in
multiple
different
places.
Like
now
I-28
got
machinery
is
split
into
separate
repos.
G
G
E
E
E
H
E
E
E
E
I
I
K
L
B
B
G
M
N
G
B
Fill
out
the
form,
if
you
think
you
should
vote
and
you're
participating
in
the
community
and
want
to
be
a
member
of
standing,
please
also
sign
up
on
the
form
and
tell
us
why
he
knew
with
our
list
that
we
generated
initially
that
it
was
going
to
be
in
group
week
as
an
example.
I
was
not
part
of
that
list,
so
we
we
know
that
it
is
incomplete.
So
please
do
go
out
and
add
your
name
to
the
form.
If
you
think
that
you
are
you.