►
From YouTube: 20171220 - community.k8s.io ad-hoc meeting
Description
00:12:49 jaredbhatti: Keeping meeting notes here: v
00:12:51 jaredbhatti: https://docs.google.com/document/d/1UuD4g2srEBeYMTPMoATGIMX3jIetyfYzsrDe8AqIo2s/edit#
00:13:21 paris: Did ihor freeze or is that me?
00:13:29 jaredbhatti: He froze
00:25:53 Zach Corleissen: We're migrating the blog into the docs repo website, and we're figuring out how to automate review of blog content without passing it through the main SIG-Docs review cycle.
00:26:02 Zach Corleissen: TLDR: +1 to Jennifer
00:26:47 Ihor Dvoretskyi: Is it possible to use a separate repo for *.k8s.io subdomain?
00:27:54 Ihor Dvoretskyi: Ideally, we have to use *.k8s.io domain space for the similar content, but avoid affecting the general SIG-Docs workflow
00:29:12 Jennifer Rondeau: +1 to: where content lives, how it’s approved is separate issue from where it’s published
00:30:45 Jennifer Rondeau: Ok ya’ll, time to share my screen
00:31:29 Jennifer Rondeau: I can hear you, I’m having trouble with screen sharing UI, just give me s ec
00:32:37 jaredbhatti: I’ve got to drop. Godspeed everyone.
00:52:57 Ihor Dvoretskyi: +1 Joe!
00:59:05 Jessica Yao: Was it contribX that made the other stats dashboard?
01:00:08 Jessica Yao: sorry, that’s not super descriptive, but I remember seeing a slick dashboard with graphs related to kubernetes contributions (not sure what the URL is)
01:00:16 Zach Corleissen: +1 to Jennifer. It happens at all levels of contributor experience.
01:03:51 Zach Corleissen: "Leveraging the knowledge of the docs team" requires attention/resources from SIG docs. It's clarity about ownership and availability that concerns us.
01:04:09 Chris Short: I'm happy to help too
01:04:22 Chris Short: Especially if it's Hugo
A
A
A
You
know,
use
that
metadata
to
do
slicing
and
dicing
and
analysis
and
filtered
views
and
colored
things
based
on
the
state
that
they're
in
that
type
of
thing,
and
and
and
and
some
of
this
is
inspired
by-
say,
the
the
pet
process
in
the
Python
world,
where
you
can
actually
go
and
look
at
all
these
proposals
and
figure
out
broad
categories
and
I
think
we
can.
We
can
take
it
even
further
than
than
what
the
Python
folks
do
there.
A
Some
of
that
value
is
making
the
stuff
more
accessible
to
the
rest
of
the
community,
and
some
of
that
is
being
able
to
clearly
build
connections
where
it's
difficult
to
do
that
right
now,
and
so,
as
we
add
value,
we
end
up
motivating
more
process.
So
that's
the
idea
around
that
this
has
been
primarily
driven
out
a
cig
architecture
and
and
as
we
look
to
roll
this
out,
further
I
wanted
to
start
building
some
of
the
scaffolding
so
that
we
can
add
some
value.
A
B
I
can
add
a
few
words
about
the
contributor
website
and
how
we
add,
CN
CF
Toto
supportive
of
this
ad
year,
so
I
just
like
to
highlight
it
in
parallel
with
startin
investigating
the
ability
to
develop
the
same
website,
the
same
set
of
website
for
all
our
CNC
of
projects
and
heaven,
heaven
one
for
kubernetes
and
with
kubernetes
is
our
the
biggest
project
and
the
most
fast-growing
project.
It
would
be
great
idea,
so,
if
we're
speaking
about
some
like
contributor
web
site
work
and
everybody
find
any
available
information
about
how
to
join,
see
and
see.
B
B
A
A
A
B
Okay,
so
I've
been,
just
speaking
about
contribute
to
website
the
original
proposal
that
flowed
into
the
mail
in
trade,
so
at
C
and
C,
which
was
all
supportive
of
this
idea.
We
in
parallel,
we
had
a
similar
idea,
was
having
the
contributor
website
for
all
our
ciencia
projects
to
to
be
represented
at
something
like
contribute,
contribute,
dot,
C
and
C
F
dot
IO
so
having
the
similar
effort
for
kubernetes
is
absolutely
welcome.
C
C
B
Yeah
I'm,
sorry
about
it
yeah.
So
our
initial
idea,
before
before
their
proposal
about
contributing
to
community,
contributed
okay,
it
has
good
hair
website
has
shown
up.
So
we,
our
initial
goal,
was
to
have
something
like
they're
they're,
disconnected
to
repo
on
the
C&C
F
organization,
on
mid
hub
where's,
that
it
should
be
like
they
did
have
pages
or
something
like
there
did
dedicated
website
where
all
people
who'd
like
to
contribute
to
some
CN
CF
projects
can
find
any
relevant
information
for
them.
C
A
quick
question,
so
it
sounds,
like
you
say,
see
it
like
when
you
say
scene
CF.
Are
you
planning
on
doing
a
community
site
for
all
of
CN
CF
for
all
projects,
or
are
you
thinking
like
there
will
be
a
plan
to
do
individual
contributions
or
kubernetes
and
say
one
for
sheriff?
You
see
and
one
for
link,
Rd
and
Mike?
Are
you?
Are
you
trying
to
create
a
community
site
to
rule
them
all?
Is
that
your
scope,
or
are
you
trying
to
create
one
for
each
of
the
products?
Oh.
B
Or
contributing
to
container
D
or
contributing
to
invoice
or
to
any
other
project.
So
all
these
guidelines
can
be
cannot
be
simply
merged,
but
having
a
single
place
where
every
person
can
champion
and
take
a
look
which
it
was
our
initial
idea
as
an
alternative
we
can.
We
can
create,
like
the
same
simple
portal
with
the
links
to
to
the
designated
project.
Websites
like
contribute,
C
and
C
of
the
Deo
may
include
some
link
to
contribute
gate
as
the
deal
where
a
person
who'd
like
to
contribute
to
divinities
may
find
some
weld
information
about.
A
A
I
I'm,
not
sure
that
that
that's
something
that
makes
a
ton
of
sense
in
my
mind
for
kubernetes,
specifically
I,
think
the
biggest
problem
we
have
a
contributor
facing
side
with
kubernetes
is
that
we
have
a
lot
of
information
spread
in
a
bunch
of
different
places
that
overlaps
and
confusing
ways,
and
so
you
know
bringing
that
together.
I
think
we'd
add
a
lot
of
value
above
and
beyond
sort
of
the
more
specialized
things
like
how
the
heck
do
we
do.
We
display
caps,
yeah.
C
F
D
D
Sorry
in
the
community
repo
right
now,
but
I
think
we
are
at
a
point
now
where
people
can
jump
in
like
if
people
on
this
call
are
interested
in
helping
they
can
jump
into
one
of
the
umbrella
issues
and
take
a
task,
but
I
think
you
know
from
a.
Where
are
we
now
we're
about?
50%
done
so,
we
still
have
a
few
more
weeks
to
go.
We
can
definitely
expedite
this
with
some
help,
but
Gwyn
and
George
and
others
have
been
kind
of
taking
task
by
task
on
that.
D
G
You
know
there's
there's
some
explaining
to
do
and
what
I've
hacked
together,
it's
very
much
a
hack
and
there
are
connectors
connecting
parts
that
aren't
working.
But
if
you
all
want
to
see
what
this
would
actually
look
like
hosted
on
kubernetes
IO
I
can
go
ahead
and
demo
I
don't
know.
If
Jared
you
wanted
to
say
anything
more.
Whether
show-and-tell
is
the
point
is
the
point
that
we're
at
or
not
I.
C
Think
all
seems
like
a
a
good
thing
to
talk
about
that.
I
feel
like
I
feel,
like
we
all
agree
in
the
overall
goals
of
like
getting
all
the
contribution
getting
all
the
contributing
material
together
in
one
place,
having
actual
meeting
point
for
all
of
its
keps
being
a
part
of
that,
you
know,
I.
Think
there's
probably
gonna
be
some
debates
over
things
like
access
infrastructure
who
has
the
like
review
and
then
admin
rights
and
things
like
that
and
I'm.
You
know
all.
H
A
I
A
Want
to
understand
a
little
bit
of
yeah,
it's
like
what
is
the
process
here.
I
feel
like
the
the
the
quality
bar
and
the
and
the
the
sort
of
process
bar
is
different
for
this
content,
then,
for
the
main,
kubernetes
IO
site,
I
think
you
know
we're
moving
from
essentially
a
free-for-all
to
something
where
we're
trying
to
we're
trying
to
get
our
arms
around
it.
A
little
bit.
A
I,
don't
wanna
well,
I,
think,
there's
a
danger
here
that
we
overcorrect
right,
that
we
go
too
far
in
the
other
direction
and
all
of
a
sudden
people
continue
to
actually
make
it
a
free-for-all,
because
there's
so
much
process
involved
in
terms
of
actually
getting
stuff
merged
to
the
main
site.
Yeah.
C
C
A
G
Anders
can
probably
speak
best
to
you
know
how
we're
thinking
of
doing
this,
and
but
the
idea
is
automate
includes
from
other
repos
not
to
require
folks
to
go
through
the
docs
review
process,
and
does
that
make
sense?
So
we
would
we
ours
got
to
be
lower
there
right,
I
mean
no
exactly
I
mean
for
the
contributor
guide.
You
know
that
bar
gets
set
by
the
folks
who
work
on
that
markdown
file
in
that
repo,
and
then
we
pull
it
it
we
scoop
it
into
the
doxa
right.
G
A
I
just
want
to
make
sure
like,
as
we
do
things
like
branching
of
the
site,
for
you
know,
for
versions
as
we're
doing
a
freeze
for
a
version.
That's
all
external
facing,
like
the
contribute
contributing
Doc's,
will
continue
to
evolve
separate
from
that
versioning
stuff
right.
It
really
is
sort
of
a
different,
separate
type
of
thing.
That's.
A
C
I,
don't
have
an
answer
to
your
question.
Okay,
that's
that's
the
I!
Do
not
we
do
not
have
a.
We
are
exploring
options
for
doing
it
because
we
have
to
do
it
for
us-
and
this
is
like
why
there's
a
bit
of
nuance
in
the
email
and
also
I
want
the
call
like
we
were
figuring
this
out
for
the
blog
already
and
there's
already
work
being
done
to
do
that.
We
don't
want
to
own
the
contents
and
I
I.
Don't
I,
don't
want
to
own
that
and
I
don't
want
to
own
the
approvals
and
I.
C
Don't
want.
Zack
totally
doesn't
want
to
know
the
approvals
to
the
blog.
It's
a
different
audience,
different
contributors.
This
seems
to
be
in
a
similar
vein.
It's
a
similar
problem
that
we're
trying
to
solve.
So
it
would
be
nice.
We
came
up
with
a
standardized
solution
for
how
to
do
this,
for
all
the
groups
that
want
to
have
content
on
the
site,
but
not
go
through
the
sig
Docs
maintainer
process
that
we
use
for
official.
C
A
Maybe
quick
I,
don't
I,
don't
care
whether
the
content
is
on
the
main
kubernetes
site
or
not
like
I'm
perfectly
happy
to
have
community
decades
do
or
caps
decades
don't
I,
oh
right,
yeah
I,
don't
feel
like
there's
a
ton
of
value
to
having
this
integrated
with
with
the
the
menus
and
the
control
flow
and
everything
else.
That's
actually
happening
on
the
main,
kubernetes
dot
IO
site.
A
Now
that
that's
a
difference
in
requirements
and
then
the
blog,
perhaps
right,
but
for
the
contributors
not
really
I
mean
these
like
dashboards,
Fred,
hither
and
yon,
it's
like
we
don't
lack
for
random
URLs
that
people
have
to
remember
having
one
that
actually
becomes.
The
meet
me
point
here:
I
think
is
actually
a
vast
improvement
and
it
doesn't
have
to
be
kubernetes
io
or
we
could
have
a
link
to
something
that
looks
different.
That
says:
hey
you
want
to
contribute,
here's
the
contributor
and
that
links
to
the
other
site,
but.
G
A
I
We've
been
thinking
that,
like
the
of
late
that
the
criminais
is
the
I/o
site
should
be
somewhat
of
a
portal
to
make
sure
like
anything,
you
want
to
find
related
to
criminate.
At
least
you
have
a
touch
point
there,
whether
it's
necessary
hosted
in
the
repo
I
think,
is
sort
of
a
separate
issue.
So
there's
a
couple
things
going
on.
I
So
we
can
like
link
to
even
if
it's
in
a
different
repo,
like
the
the
key
documents
that
people
would
need
in
order
to
be
able
to
contribute,
and
then
like.
A
third
issue
which
we've
only
reached
just
like
in
since
cube
con
been
talking
about,
is
all
the
SIG's
have
all
these
different
documentation
buried.
A
Hear
what
y'all
are
saying
and
I
think
that
makes
sense,
I
think,
just
from
a
practical
point
of
view,
when
I
ask
the
question
of
how
are
we
going
to
integrate
content
from
a
bunch
of
different
reef
into
a
single
site?
The
answer
is,
we
don't
know
we're
still
figuring
that
out,
whereas
if
I
were
to
ask
the
question
of,
can
we
actually,
you
know,
use
you
know,
Jekyll
plus
Natalja
Phi,
to
actually
published
a
community
on
kubernetes
dot,
IO
and
then
connect
the
dots
later
like.
That
should
be
a
couple
days.
A
Work
to
get
that
scaffolding
set
up
so
I
think
there's
a
certain
amount
of
like.
Do.
We
want
to
optimize
for
the
perfect
solution
of
having
everything
on
the
same
site,
even
if
we're
pulling
from
different
repos
or
doing
on
and
want
to
optimize
to
start
making
progress
in
terms
of
actually
getting
this
stuff
indexed
up,
someplace
starting
to
bring
it
together
and
I
definitely
lean
on
the
other
side,
I,
don't
care
if
it's
on
the
same
site
as
long
as
we
can
start
publishing
this
stuff,
you
know
as
soon
as
possible.
C
G
So
this
you
know
Joannie
horn,
whoever
else
hasn't
seen.
It
is
what
we
have
been
working
on
with
the
kerbin
ad
stocks
user
journeys.
For
the
last
number
of
months
now,
Jessica's
been
part
of
this
small
working
group
Andrew
and
a
designer
from
the
Linux
Foundation
have
been
putting
in
a
ton
of
time
and
getting
this
both
designed
and
then
developed.
G
But
this
this
will
show
you.
You
know:
we've
gone
down
this
path,
aways
already,
it's
not
like
we're
starting
from
scratch.
So
if
you
can't
landed-
and
this
is
what
you
would
get
as
the
new
landing
page
for
the
kubernetes
documentation-
it
could
actually
live
someplace
else
too.
In
fact,
yeah
here,
I
can
show
you
I
just
went
in
and
hacked
the
landing
page
for
kubernetes
the
this
is
the
community
link
right
from
the
main
community
site
and
I
just
stuck
links
to
the
contributor
guide
and
the
kept
process
here.
G
G
Don't
have
the
left
pane
toc
showing
here,
but
what
we
would
get
eventually
is
a
better
UX
for
the
contributor,
a
guy
gets
long
because
it
will,
even
though
we're
trying
to
compress
and
condense
it,
you
know
we
still
need
that
our
navigation,
so
there'll
be
a
TOC
like
there
is
on
the
regular
Doc's
pages.
I
mean
the
left
pane
to
help
people
navigate
through
the
contributor
guide.
This
is
the
work
in
progress
readme
that
Paris
has
been
in
charge
of.
G
G
G
Now
these
these
links
are
dummy
links
at
this
point.
They
don't
work,
I
didn't
set
it
up
properly,
but
in
fact,
they're
really
odd,
but
the
way
the
you,
the
overall
UX
of
this
redesign
of
the
landing
pages
works
we
provide
this
and
I
picked
the
kubernetes
api
at
random
as
a
thing
that
might
not
go
in
the
developer
guide.
It
might
be
something
a
code,
contributor,
Whitney
or
be
interested
in
learning
it
out.
G
So
that's
what
that
would
be
like
and
you'll
notice
here,
Joe
I've
got.
This
link
is
out
to
the
well
in
well.
I'll
show
you
next
those
out
to
the
actual
documentation
how
the
cap
works
and
then
I
had
I
hacked
a
list.
There
isn't
actually
a
list,
yet
there
aren't
keps
living
in
different
cig
directories,
so
I
couldn't
really
do
that,
but
I
could
pretend
to
write.
G
So
that's
what
that
UX
would
be.
Like
all
of
the
you
know.
All
of
this
text
is
up
for
grabs
easy
to
change.
This
is
just
an
attempt
to
show
you
what
it
could
be
like
right,
and
this
is
what,
if
you
clicked,
I'm,
not
sure
where
this
comes
from
exactly
from
the
previous
UI,
because
I
had
to
stick
some
manual
links
in
this
demo.
G
But
you
know
here:
we've
got
the
contributor
guide
again,
basically,
the
same
content,
and
so
again
you
know,
link
out
to
the
contributor
guide,
keep
scrolling
down.
We
can
link,
you
know,
read
about
that.
The
API-
and
this
is
I'm
gonna
hack,
this
stuff.
This
is
not
really
pulling
in
from
other
repos.
Okay.
This
is
a
very,
very
ugly
branch.
That's
gonna
get
deleted
very
soon,
but
here
we've
got
the
current
kept
process.
Documentation
we've
got
it
all
in
one
place
right
and
then
this
would
be
a
set
of
includes
you
know.
G
We'd
have
to
pull
in,
and
this
one
I
couldn't
fix
up.
I
did
something
weird
with
the
markup
and
I
just
couldn't
get
to
it
last
night,
but
that's
what
the
UX
that's
that's
one
way
that
we
could
include
the
UX,
the
contributor
guide
and
the
kept
process
in
the
model
that
we
are
have
currently
been
developing
and
thinking
about
for
contributors
within
the
framework
of
the
larger
community
site.
I
A
Know
so
I
mean
any
submission
of
this
stuff
will
still
be
through
through
github
and
PRS.
That's
that's
part
of
the
process.
The
state
of
those
things
will
be
metadata,
that's
in
front
matter
on
those
documents,
and
so
it's
just
a
matter
of
how
do
we
take
advantage
of
that
metadata
to
to
create
a
good
experience
for
for
exploring
the
caps
I?
A
What
is
my
homepage
that
I
go
to
to
understand?
What's
happening
from
the
contribution
point
of
view
right?
What
are
the
you
know,
quick
links
to
all
of
the
all
of
the
various
you
know
dashboards
that
I
really
need
to
actually
pay
attention
to
right.
What
are
the?
What
would
it's
a
milestone?
What
are
we
doing
with
code
freeze?
What
is
actually
happening?
You
know
for
the
next
week
right.
A
What
is
the
you
know,
the
list
of
SIG's
and
how
do
I
actually
get
to
that
so
I
know
who
I
talk
to
about
certain
things
right
and,
as
we
get
more
and
more
metadata,
you'll
be
able
to
navigate
from
SIG's
to
all
the
different
code
that
those
SIG's
own,
so
that
you
can
actually
map
back
and
forth
for
hey
this
component,
this
piece
of
code
maps
to
this
sick
right.
Those
are
the
types
of
things
that
I
think
experienced.
A
Contributors
are
going
to
actually
care
about,
and
I'm,
not
sure,
that's,
starting
with
the
kubernetes
dot
IO
site.
With
this
sort
of
you
know,
induction
type
of
sort
of
wizard
approach
to
figure
out
what
type
of
user
you
are
is
going
to
work
for
that
more
experienced,
developer.
I
think
this
is
great
for
it's,
like
hey,
you're,
new
to
kubernetes.
You
want
to
start
contributing
this.
A
This
is
exactly
what
we
need
the
stuff
that
I'm
thinking
about
is
how
do
we
start
adding
value
for
folks
who
have
you
know
a
page
full
of
bookmarks
that
they
manage
themselves?
How
do
we
actually
get
people
to
actually
have
a
shared
vision
of
sort
of
like
what
the
status
of
the
project
is?
Some
of
that
status
of
the
project
is
the
caps,
but
there's
going
to
be
other
things
that
we
really
want
to
be
able
to
publish
there
also
and
that
stuff's
going
to
be
updated.
A
All
the
time
and
I
think
we're
going
to
definitely
have
you
know.
Different
SIG's
are
going
to
have
different
ways
that
they
want
to
publish
stuff
to
the
to
the
rest
of
the
community,
so
yeah
so
I
again,
I
I'm,
not
sure
that
it's
I
question,
whether
whether
it's
worthwhile
to
try
and
cram
this
community
facing
like,
like
you,
know,
what's
happening
with
the
project
now,
which
is
really
a
dashboard
in
some
ways,
into
the
information
architecture
of
the
documentation
site
as
it
exists
right
now,
because
I
think
this
is
fundamentally
you're.
A
Viewing
this
as
a
documentation,
exercise
and
I
think
there's
an
aspect
to
the
community
site,
which
has
to
be
more
of
like
a
dashboard
of
what's
happening
inside
the
community,
and
the
caps
are
really
back
and
forth
right.
There
is
a
dashboard
of
like
what
are
the
active
caps.
What
is
the
you
know?
What
is
the
current
status?
Let
me
sort
these
things
by
this.
A
A
A
A
A
The
stuff
that
I'm
talking
about
includes,
like
hey,
you
know
the
documentation
site
is
now.
You
are
now
checking
into
this
branch,
and
so
here's
the
current
process
or
we're
in
this
mode
as
we
get
down
to
release,
and
so
here's
the
information
that
you
need
to
know
about.
What
exactly
are
the
rules
for
getting
code
or
documentation
or
whatever
n
right?
A
It's
very
much
like
I
view
this,
as
buddy-buddy
with
the
community
meeting
that
we
have
right
right
like
we
go
to
the
community
meeting
every
Thursday
and
we
produce
notes
out
of
that,
but
there's
a
of
announcements.
Well,
where
would
we
put
those
announcements
if
people
wanted
to
see
what
is
the
latest
announcement
right?
This
is
the
the
community
portal
is
like
the
place
of
where
we
would
put
this
and
it
would
complement
sort
of
those
announcements
that
happened
during
the
community
meeting.
A
A
I'm,
fine
with
that
I
think
it's
just
a
matter
of
like
I.
Don't
like
I,
don't
know
what
I
don't
see!
I
I,
don't
know
like
what
is
it
gonna
take
so
that,
like
how
long
is
it
gonna
take,
so
that
like
we
can
check
something
into
kubernetes,
slash
community
and
it
shows
up
here
right
like
we
got
to
get
that
process
down
and
and
and
if
we
start
pulling
in
this
content
cross
cross
repo
net
Lofa
is
not
supported
for
that.
It's
not
something
that
anybody's
done.
Yet.
It
feels
like
we're.
A
D
D
Actually,
you
know
100%
in
agreement
with
you
and
what
you're
saying
is
to
what
we
need
like
it
would
be
cool
if
we
could
embed
the
YouTube
videos
forcing
meetings
on
the
site
so
that
people
could
see
what
we
are
working
on,
because
I
think
the
sake
videos
are
kind
of
the
the
truth
of
where
everyone
is
and
what
everyone's
doing
so
I
just
don't
know
myself
kind
of
what
goes
into
the
development
of
of
that
and
who
would
own
it.
And
things
like
that.
I
I.
A
Mean
I:
this
is
contributor
experience
to
some
degree.
In
my
mind
we
did
things
like
we
did
the
we
did
the
signal
so
that
we
could
auto
generate
a
bunch
of
the
the
markdown.
That's
on
the
community
site
right
now
and
I
think
you
know,
Caleb
disagrees,
but
I
think
there
was
a
huge
step
forward
because
now
there's
a
consistent
source
of
truth
of
like
who
the
sig
leads,
are
and
all
the
webpages
look
alike,
and
we
can
Auto
generate
that
BigTable.
That's
super
useful
right!
A
D
Was
just
gonna
start
by
filing
issues,
I'm
actually
in
the
middle
of
filing
an
issue
right
now
to
take
the
second
blank
community
calendar
at
the
bottom
off
until
we
can
figure
out
what
content
should
actually
go
into
that
community
calendar
I
think
we've
got
some
ideas
from
the
contributor
experience
group,
but
doesn't
seem
like
anybody
necessarily
at
the
time
to
do
it,
but
I'm
filing
that
issue
today.
Momentarily
so
I
mean
that's,
that's
just
how
I
was
gonna
start
with
you,
just
very
simple
baby
steps
of
a
redesign.
A
Yeah
I
mean
like
I'll,
give
you
an
example
of
like
I,
just
I,
don't
know
like
we
got
to
start
getting
a
handle
of
this
I'm.
Looking
at
the
community
tab
of
kubernetes
dot,
IO,
which
I
guarantee
you
nobody
who's
actively
working
on
kubernetes
on
a
day
to
day
basis
really
looks
at,
or
at
least
I,
don't
and
there's
a
link
there
to
list
of
SIG's.
A
That
goes
to
the
wiki
that
nobody's
updated
in
forever,
and
that
thing
then
like,
if
you
go
a
list
of
SIG's
and
you
have
to
do
another
link
to
the
actual
list
that
generated
from
the
SIG's
damo
right.
So
there's
like
two
levels
of
indirection
there,
because
we,
you
know
it's
too
hard
to
updates
like
like,
we
have
a
wiki.
We
have
markdown,
we
have
markdown
spread
across
all
sorts
of
different
and
repose,
and
then
we
have
that
site
itself.
A
I
I
To
creating
a
sub-domain
and,
like
you
know,
spinning
up
a
separate
site
because
I
think
the
initial
concern
when
you
know
to
have
this
meeting
was
just
to
make
for
all
of
our
efforts
were
coordinated.
But
to
that
specific
point
like
in
terms
of
like
nullify,
it's
easy,
we
can
just
like
point.
You
know
a
subdomain
to
a
repo
and
a
branch,
and
then
you
know
it'll
it'll
host
it.
That's
that's
easy.
So
is
there
any
objections
to
spinning
up
another
site
under
a
subdomain
of
Kate's
that
I.
I
J
My
objection,
I,
don't
know
that
it's
an
objection
so
much
as
it's
just
a
question
who
undertakes
the
maintenance
and
the
upkeep
of
that
site
who
undertakes
the
responsibility
of
keeping
entirely
separate,
tooling
chains
from
developing
or
increasing
the
technical
debt
required
to
maintain
both
documentation
community.
What's
basically
who-who
minimize
this
technical
debt
and
who
wondered
who
actually
undertakes
that
upkeep
and
who
commits
to
doing
that
on
a
long-term
basis.
D
While
necessarily
want
to
volunteer
I
feel
like
this
is
something
that
same
experience
should
own
and
you
know
ultimately
be
the
ones
that
would
be
maintaining
this
I
don't
know
again,
I,
don't
know
what
your
thoughts
are
on
that,
but
and
that's
just
what
I
feel
you
know
from
a
scope
perspective
and
from
this
just
makes
sense
perspective,
I,
think
construct.
You
know,
contributor
experience
who
you
know
who
owns
this
kind
of
responsibility
would
be
best
served
so.
D
Yeah,
that's
that
the
hesitancy
is.
We
have
not
talked
about
this
at
all.
So
that's
why
you
hear
the
giggle
in
my
voice,
hey
I,
think
this
might
be
us,
but
ya,
know
I
think
we
would
definitely
need
to
have
a
larger
conversation
and
in
our
next
meeting
about
this
specifically
about
the
maintenance
and
who's
going
to
own
it.
But
I
can
foresee
my
role
and
George
and
a
couple
other
community
managers
that
are
on
the
project
full-time
undertaking.
This.
A
It
can
be
uglier,
I
mean
I,
I,
think
in
terms
of
a
separate
tool
chain:
I'm,
not
religious,
about
the
static
site,
generator
that
we're
using
I
mean,
if,
like
you
know,
if
it
makes
sense
to
to
say,
hey
we're
gonna
use
Jekyll
across
both
of
these
things,
that
that
is
seems
totally
reasonable.
To
me,
there
is
the
question
with
respect
to
you
know
just
sort
of
closing
the
loop
a
little
bit
towards
like
what
Igor
has
been
talking
about.
A
You
know
do
the
patterns
that
we
set
here
actually
get
imported
into
other
CN
CF
projects?
Is
there
a
way
for
this
stuff
to
be
leveraged,
if
not
directly,
but
in
terms
of
you
know,
saying
hey
if
you
do
XY
and
Z
there's
a
base
of
knowledge
that
you
can
draw
upon
and
so
you're
going
to
actually
have
an
easier
time
right.
A
So
if
we,
if
we
pick
jack,
o
plus
neckla
Phi,
we
can
crib
a
bunch
of
stuff
from
the
main
docks
repo
without
having
to
think
too
hard
that
you
know
it's
not
exactly
the
same
tool
chain,
but
it's
it's
it's.
At
least
you
know.
If
we
have
questions
or
somebody
would
get
asked
right,
who
might
have
a
clue
of
having
an
answer
just.
B
One
note
if
we
are
struggling
with
designating
some
cabinet
is
Vallejo.
Okay,
it
is
go
to
your
space
for
this
effort.
We
can
use
cnc
of
the
day
or
four
days
and
cnc
of
rapers,
and
everybody
will
be
working
on
this
stuff
and
contributing
some
sent
to
this
designated
trip
before
this
website
will
be
invited
to
the
cnc
organization
as
a
contributor.
So
it
shouldn't
be
a
problem
with
we're
speaking
only
about
domain
and
website
issues.
So
when
we
can,
we
can
use
different
spaces
to
do
a
so
musician.
J
It's
not
so
much
this.
It
is
not
the
domain
that
is
problematic.
It
is
specifically
I'm
thinking
about
the
maintenance
burden.
So
the
thing
is
that
if
we
adopt
the
static
site
tool
chain
that
we
use
to
generate
kubernetes
tayo
right
now
they
ultimately,
yes,
the
the
maintenance
burden
does
fall
back
on
sick
dogs,
because,
if
that
is
the
basis
from
which
we
operate,
then
the
the
basis
of
iteration
also
falls
upon
us
in
a
consulting
role,
if
not
an
implementation
role.
J
So
I
guess
I
don't
want
to
say
I
am
on
board
with
having
a
community
site
that
actually
works
and
serves
relevant
content
and
is
is
sort
of
is
everybody's
new
bicycle,
to
make
an
analogy
when
one
that
actually
serves
content,
it's
relevant
to
to
the
kubernetes
community.
What
I
don't
want
to
do
is
say
yes
to
easily
to
undertaking
site
development
when
we're
not
sure
where
we're
the
long-term
arc
of
maintenance
and
upkeep
falls.
So.
A
That
when
you
say
long
term,
maintenance
and
upkeep
like
what
exactly
are
you
thinking
about
there?
Because,
like
honestly,
you
know
if
we're
talking
about
the
content
itself
like
we
couldn't
do
any
worse
than
where
we're
at
right
now
we're
just
all
that
we
have
across
and
different
things
right.
So
that
is,
you
know.
That
is
the
core
problem
that
we're
facing.
Are
there
other
tasks
that
you
think
are
part
of
that?
That
sort
of
upkeep
that
that
we
need
to
keep
in
mind.
J
J
A
Just
thinking
like
the
review,
something
content
specific
stuff,
we
already
have
that
problem
right
now
with
the
sprawl
that
we
have
right
and
so
I
don't
think
like
and
again.
Some
of
this
is
the
bar
right.
The
quality
bar
for
this
doesn't
have
to
be
as
high
as
the
quality
bar
for
our
user
facing
site.
It's
a
much
smaller
community.
We
can
definitely
lean
on
the
individual
contributors
to
actually
maintain
their
own
little
subsections
of
this
in
terms
of
like
site
performance,
I.
A
I
But
there
is
a
maintenance
load
like
to
speak
to
Zach's
point
like
just
fork:
Rene's
I/o,
for
example.
Right,
like
you
know,
we've
had
to
do.
You
know
like
the
move
to
nullify
we've
had
to
like
SEO
is
working.
We've
had
to
like
restructure
documents.
We
had
to
you
know,
look
into
i18n
like
there's
a
bunch
of
things
that
you
know,
keeping
up
the
site
or
improving
it.
That's
more
than
just
you
know,
managing
the
content
on
the
site
so.
A
A
I
Just
specific
points,
but
the
general
idea
is
that
you
know
we.
We
need
basically
website
engineers
that,
for
any
sort
of
you
know
change
or
future
or
something
where
you're
modifying
the
you
know
the
foundation
of
the
site.
You
need
someone
to
do
that,
and
the
question
is
who
owns
that
because,
like
I'm
on
board
with
Zack
in
terms
of
like
as
sig
Docs
I,
don't
think
we
want
to
own
that,
like
I
find,
if
you
want
to
you,
know,
have
your
own
site
and,
like
you.
I
A
Know
I
totally
hear
you
and
I
think
I
think
you
know
channeling
Paris
here,
I'm
gonna,
I'm
gonna
volunteer.
Her
I'm,
like
I,
think
getting
contributes
to
own.
This
I
think
makes
a
ton
of
sense.
I
also
think
that
it's
going
to
be
an
order
of
magnitude,
less
work
than
the
main
site.
I,
don't
think
the
maintenance
burden
of
this
site
is
going
to
be.
A
G
You
know
a
check-in
that
somebody
just
wasn't
quite
paying
attention
to
a
commit
that
you
know
a
PR
that
somebody
merged,
because
it
seemed
perfectly
innocuous
and
only
after
the
fact
did
all
sorts
of
issues
sort
of
cascade
into.
Oh,
my
god,
you
know
we
can't
even
publish
I
mean
this
stuff
happens
with
any
website.
It
doesn't
matter
how
low
the
bar
take
SEO
take
out
internationalization,
take
out,
you
know,
sort
of
any
of
those
small.
You
know
sort
of
bits
and
pieces
anytime,
you're
pumped
you're,
pushing
new
content
to
a
website.
G
G
That's
all
and
that's
not
an
argument
against
doing
it.
I'm
just
I'm,
trying
to
express
in
a
more
general
way
the
concern
that's
hard
to
give
good
examples
of
right
now,
because
a
lot
of
the
stuff
that
we
noodle
on
on
a
daily
basis
is
this
more
documentation,
specific
stuff,
but
some
of
it's
just
generic
website
maintenance.
No.
A
A
So,
in
my
mind,
I
think
there's
also
there's
also
the
question
of
of
the
tool
chain
that
we
pick
in
some
ways
defines
the
people
who
are
gonna
be
managing
it
right.
So
I
would
be
more
comfortable
personally
using
something
like
Hugo
instead
of
instead
of
Jekyll
cuz
it's
go
and
there's
that
skill
set
is
is
a
lot
more
common
across
the
the
contributing
population
here
and
so
maintenance
of
that
is
going
to
be
perhaps
easier
with
that
tool
chain.
A
J
A
But
it
was
a
merge
conflict
as
you're
doing
stuff
across
branches.
Was
that
it?
Yes,
ok
I,
just
like
we
can
argue
about
these
specific
things,
but
I,
don't
think
we're
gonna
be
doing
sort
of
like
filly
sprinkles
on
this
thing
right
so
like
that
particular
issue,
I
think
the
main
point
I'm
just
saying
like
fundamentally
like
it's
just
gonna,
be
a
simpler
thing,
but
I
totally
hear
what
you're
saying
I
mean
there
is
always
a
chance
that
this
stuff
breaks,
I
think.
A
A
D
I'm
very
yeah,
I'm,
very
happy
and
I
know
Chris
on
the
call
and
Josh
and
and
I
know,
George
would
be
happy
to
help
as
well,
so
I
mean
we've
got
people
to
do
it
and
to
do
the
work.
It's
just
you
know.
You
know
like
I
think
what
Doc's
is
saying
is
that
we
actually
need
to
step
up
and
promise
that
we're
gonna
do
the
work
and
to
pretty
much
sign
our
firstborn
children.
To
that
we're
gonna.
Do
the
work
and
I'll
keep
the
work
so
well.
H
Was
actually
gonna
suggest
that
using
a
different
tool
change
would
somewhat
prevent
Doc's
from
having
to
get
involved
unnecessarily
or
just
through.
The
fact
that
no,
this
is
documentation
is
amount
right
a
year
from
now
it
kind
of
prevents
the
docs
team
from
the
whole
Newton,
which
I
think
would
be
beneficial
and.
E
Well,
one
of
the
other
things
that
we're
gonna
need
to
look
at
is
requirements
for
stuff,
because
I
can
definitely
see
for
the
kept
requirements
to
actually
save,
for
example,
want
some
dynamic
content
as
opposed
to
strictly
static
content,
and
if
we
decide
that
we
want
that,
then
is
a
completely
different
direction
in
terms
of
culture.
So
the
I
think
you
know.
E
A
D
A
I
So
I
can
I
can
add
you
to
the
to
the
kubernetes
organization
that
that
I
have
that's
in
the
fie
and
so
basically
there's
a
dashboard.
And
what
you
can
do
is
create
a
new
Liffe
eyesight's
at
a
github
repo
and
branch,
and
then
that
then
it
will
do
a
build
and
we
can.
We
have
it
set
up
so
that
we
can
automatically
assigns
to
a
subdomain
of
Rene's.