►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
D
C
D
B
C
F
E
H
E
Know
the
like:
is
this
the
part
where
I
start
talking?
How
does
this
go
yeah?
Why
didn't
you
introduce
the
topic
sure
so
recently,
sig
Docs
adopted
a
policy
for
how
we
handle
third-party
content
and
the
response
to
that
has
been.
The
response
to
this
policy
has
been
quite
strong
because
there
are
some
deficiencies
in
it
and
there
are
some
deficiencies
in
the
way
in
which
we
collaborated
and
did
not
collaborate
around
the
implementation
of
this
policy.
E
E
E
Refusing
to
host
third-party
content
that
unless
it
meets
three
conditions,
that
it
is
in
the
kubernetes
org,
that
it
is
in
the
Caribbean
at
e-cigs
org,
or
that
it's
in
the
CN
CF
incubator-
and
this
is
not
a
desire
for
purity.
This
doesn't
come
from
a
drive
to
have
pure
definitions.
It
comes
from
the
desire
to
make
sure
that
we
are
best
serving
users
with
information
that
is
hosted
in
one
place,
that
is
accurate
and
up-to-date
and
serves
them
well
and
for
a
bit
of
history.
I
I've
put
some
issues
into
the
agenda.
E
E
Sometimes
we
find
content
that
is
from
a
third-party
provider,
and
it's
not
immediately
clear
whether
this
is
content.
That's
replicated
elsewhere,
whether
it
is
the
freshest
version
of
this
information
and
there
are
competing
instances
where
sometimes
the
version
of
this
information
in
kubernetes
features.
Doc's
isn't
current.
Sometimes
it
is
the
most
current,
even
when
it
exists
in
other
places.
So
this
is
a
drive
to
provide
clarity
for
users
to
make
sure
that
users
are
finding
that
what
users
find
in
kubernetes
stocks
is
current,
accurate
and
helpful.
E
So
it's
an
example
of
if
a
if
a
project
is
archived,
for
whatever
reason
the
the
people
who
maintain
that
project
aren't
necessarily
going
to
have
the
bandwidth
or
the
presence
to
come
in
and
archive
or
deprecated
all
of
their
documentation.
It's
you
know
a
projects
going
to
wither
up
and
dry
away.
So
it's
a
question
of
being
able
to
remove
a
link
rather
than
having
to
go
through
and
analyze,
which
content
to
remove
and
likewise
there's
a
great
deal
of
content
that
qualifies
as
more
or
less
a
vendor
pitch.
E
E
The
upshot
of
all
of
this
is
that
there
are
no
clear
guidelines,
or
at
least
weren't
until
recently,
there
were
no
clear
guidelines
on
what
could
and
could
not
go
into
kubernetes
feature
documentation
what
the
bar
was
for,
whether
that
content
was
allowed
or
disallowed,
and
what
we
did
with
this
third-party
content
policy
was
try
to
clarify
some
of
those
goals.
Now
that
said,
I
think
there's
a
great
deal
of
valid
feedback
that
we
did
not
do
that
well
and
I.
Take
responsibility
for
that.
E
So
we've
taken
the
feedback
that
we
need
to
proceed
well,
stop
these
changes
right
now,
walk
them
back,
open
a
cap
go
through
the
cap
proposal
due
to
the
scope
of
stakeholders
involved
in
the
scope
of
changes
proposed,
get
buy-in
and
then
proceed
from
there.
So
Jim
angel,
who
is
one
of
the
Sigma
X
co-chairs,
is
here
as
well.
I'm
gonna
ask
Jim
that
seems
reasonably
complete
or,
if
there's
anything
that
you
would
like
to.
I
Okay,
hi
Zach.
Thank
thank
you,
for
you
know
explaining
the
whole
background.
Sorry,
how
we
went
about
I
have
a
part
to
play
in
that
as
well.
So
apologies
for
that
so
I
think
it
kind
of
like
took
us
by
surprise
I
think
to
see
that
and
when
Brian
went
digging,
we
couldn't
find
you
know
discussion
as
well,
so
which
was
which
made
it
a
little
bit
harder,
I
think
so
I.
So
I
just
wanted
to
start
by
saying:
okay,
sorry
about
that,
the
Holtz,
you
know
didn't
really!
I
F
Effectively
just
encountered
circular
references,
they
were
just
first
references
in
the
agenda
and
then
issues
and
NPR's
and
the
policy
appeared
to
emerge
like
a
month
and
a
half
ago
out
of
whole
cloth,
and
there
was
no
discussion
on
that
PR.
So
on
you
know,
I
just
without
and
I
checked
the
mailing
list,
as
well
so
without
having
been
in
the
room.
I,
don't
think
anybody
else
was
could
really
be
aware.
I,
he
didn't
slack
the
archives.
F
The
links
to
the
spark
arc
I
was
just
basically
pointing
to
one
since
Lord
of
all
so
so
there
was
just
lack
of
clarity
to
I
workout
started
now.
I
was
involved
and
Docs
early
on
in
cig,
Docs,
so
I
understand
the
motivations
or
I
could
Intuit
motivations
for
wanting
to
bound
scope
and
introduced
clarity
and
fairness,
and
that
kind
of
thing
so
basically
I
started
asking
questions
to
try
to
clarify
the
policy
and
how
it
came
about
I.
Don't
think
all
those
questions
have
been
answered
yet,
but
I
haven't
followed
the
latest
responses.
F
My
notifications
are
kind
of
a
disaster,
but,
for
example,
wasn't
you
know
you
mentioned
kubernetes
core
wasn't
clear
if
there
was
a
different
policy
for
community
SIG's
and
you
know
whatever
non
core
projects
is
just
an
example:
I
assume
that
through
the
cap,
all
that
will
get
sorted
out
and
you
know
if
people
review
the
cap,
then
we
can
make
sure
that
those
things
are
covered
by
the
Kemp
and
I.
Think
that
will
just
help
bring
clarity
all
around
I
know.
F
D
Think
the
the
intent
was
good-natured
right,
I,
just
how
everything
executed
was
the
was
the
part
that
was
a
little
bit
troublesome
for
I
only
got
looped
in
because
of
as
a
sick,
chair
I
people
were
very
loud
and
boisterous
in
angry
to
the
point
where
they
had
poked
me
several
times.
I
think
I
had
like
seven
or
eight
red
notifications
on
this
particular
topic.
So
as
a
community,
you
know
the
kept
processes
are
unified
standard
by
which
we
communicate
across
sync
boundary
lines,
and
it
helps
us
to
do
that.
D
I
think
when
in
doubt
it
never
hurts
to
file
an
issue
with
steering
so
that
we
can
help
to
socialize
it
to
get
better
traction
and
awareness
with
the
broader
community.
It's
a
sort
of
grease
the
wheels
so
to
speak
before
it
goes
out
the
door
that
way
at
least
there's
broader
awareness,
so
that
there's
less
I'm,
not
freaking
out
that
can
occur
in
the
community
because
the
community
is
so
diverse
and
across
so
many
different
time
zones
with
so
many
different
groups
which
have
different
stakeholders
and
operate
in
different
mindsets.
F
I
On
on
the
side
of
like
what
what
do
we
do
next
right,
so
I
am
I
right
in
assuming
that
you
will
come
up
with
some
sort
of
checklist
that
people
can
follow
to
see
if
the
PR
that
they
are
going
to
propose
will
be
accepted
or
not.
So
you
essentially
know
put
a
sign
on
the
door
saying
you
know.
This
is
what
we're
going
to.
Let
in
would
is
that
the
kind
of
thing
that
that
you
are
looking
at
in
the
cap.
E
A
Do
we
want
to
dig
into
sort
of
you
know,
give
you
some
feedback
and
sort
of
like
what
those
guidelines
might
be
and
sort
of
drive
into
that
discussion,
or
do
you
think
it's
best
to
just
sort
of
you
know,
put
a
straw,
straw
dog
out
there
with
the
cap,
and
then
we
can
sort
of
iterate
on
that
I.
Don't
want
us
to
ramble
right
now
on
something
that
may
not
be
useful.
E
F
Yeah
I
agree
is
actual
an
actual
document
that
outlines
the
content
guidelines.
There
was
just
no
discussion
that
was
published
around
the
how
those
guidelines
were
created
and
they
kept
would
serve
that
purpose.
So
I
think
they
have
a
starting
point
for
guidelines
from
that
and
from
the
other
feedback
that
was
received,
and
you
know
we
can
go
from
there.
I
think
consolidating
the
cap
would
be
the
most
constructive
way
forward.
A
H
Think
I'd
also
encourage
in
the
cap
solution
of
the
general
problem.
So
if
like
staleness,
because
one
of
the
things
I
heard
was
effectively,
we
don't
want
to
have
to
remove
old
seal
vendor
con
content.
I
think
maybe
we
can.
If
we
talk
about
staleness
instead
of
talking
about
vendor
specific
stuff
that
might
solve
some
of
the
problems
in
general,
beyond
focusing
on
vendor
or
not.
F
I,
do
I
guess
a
couple
of
comments
to
respond
to
that
I.
Remember
back
earlier,
we
were
very
liberal
about
taking
content,
including
you
know,
other
cloud
providers
and
things
and
I
definitely
experienced
the
problem
of
that
content
becoming
inconsistent
with
other
sources.
So
I
think
that's
a
special
problem
which
maybe
staleness
is
not
the
Asian
only
issue.
I
think
the
dual
source
or
multi
source
is
definitely
an
issue
where
you
can
no
longer
tell
what
is
the
most
authoritative
or
up-to-date
document
so
there
it.
There
is
a
you
know.
F
Maybe
it's
not
just
vendor
content,
but
multi
sourced
content
is
also
an
issue
there.
So
I
think
that
is
good
to
cover
by
the
guidelines.
I
think
also,
once
the
guidelines
have
been
agreed
upon
and
communicated
communicating
the
the
list
of
documents
that
are
going
to
be
removed
or
changed.
I
think
would
also
be
helpful.
F
So
if
the
stakeholders
or
owners
of
that
content
can
have
an
opportunity
to
do
something
about
it
or
I
could
copy
it
to
another
location
or
offer
a
link
to
link
out
to
or
whatever
the
appropriate
solution
is
for
that
content
like
I
already
started,
circulating
some
of
the
documents
that
were
in
that
issue
with
people
who
either
authored
that
content
or
might
be
interested
in
that
content.
But
I
don't
know
if
that's
a
complete
list,
so
you
know
if
there
were
some
way
to
surface
that.
C
So
it
sounds
like
one
of
the
issues
here
is
not
just
been
there
about
hosting
content,
for
which
we're
not
the
authority
or
the
authoritative
source
for
that
information,
and
so
maybe,
as
part
of
this,
just
calling
out
our
goals
for
why
we
would
host
documentation
that
we
are
not
the
authority
of
the
source
of
information
on
it
on
our
website,
of
which
there
aren't
legitimate
reasons.
But
then
that
just
gives
us
something
to
refer
back
to
like
when
we're
debating
specific
policies
right.
Does
it
meet
the
goals
were
setting
out
to
do.
A
I
think
it's
also
worth
recognizing
that
there's
gonna
be
some
trade-offs
here.
In
terms
of
you
know,
usability
for
users
versus
having
this
content
I
mean
we
should
recognize
as
part
of
the
cap
that
we
may
be
regressing
to
you
know
in
the
favor
of
neutrality,
I
mean
just
looking
around
right
now,
I
think
there's
one
page
all
posted
in
the
chat.
A
This
is
the
kubernetes
Doc's
set
up
like
the
first
thing,
and
this
has
this
huge
chart
of
like
pointers
to
like
a
bunch
of
stuff
in
the
ecosystem,
like
I
think
this
is
a
great
example
of
like
we're.
Never
going
to
keep
this
stuff
up
to
date,
and
you
know
it's
just
gonna
be
a
lot
of
churn,
and
it
is
this.
Is
this
where
we
want
to
be
spending
our
time,
but
this
may
be
a
place
where
you
know
new
users
are
like
okay.
I
want
to
do
kubernetes.
How
do
I
even
get
started?
A
C
I
One
another
thing
twist
to
this
is
like,
for
example,
the
page
where
we
have
the
list
of
the
sea
and
ice
and
the
cube
CTO
for
each
of
the
sea
and
ice
I
always
go
to
that
page,
because
I
know
it's
there
and
it's
standard
and
there's
like
seven
of
them
and
I
can
cut
and
paste
from
there.
That's
extremely
valuable.
You
know
so
things
like
that.
I,
don't
know
you
know.
I
C
We
can
always
treat
the
policy
to
say
this
is
like
is
our
idealized
world
and
here's
how
we're
going
to
look
at
new
documents
without
immediately
having
to
you
know,
rip
out
everything
that
doesn't
mean
that
policy
because,
like
as
you
mentioned
it
for
no
other
reason,
people
already
a
bookmarked
and
everyone
knows
it's
there,
and
so
maybe
it's
useful
for
to
them
versus
documentation.
That's
new
doesn't
have
that
problem.
A
H
I
F
C
F
F
H
F
I
think
just
the
caution.
What
we
found
with
previous
communications
is
that
we
got
a
lot
of
questions
about
hey.
How
do
I
vote
for
people
who
haven't
been
engaged
and
didn't
read
the
previous
communications,
like
all
the
emails
we
sent
about
like
well,
you
have
to
be
in
Villiers
Indian.
What
not
so,
please
don't
send
to
social
unless
you
link
to
one
of
those
messages
with
those
instructions.
I
A
A
B
G
F
B
F
I
B
The
waiting
list
is
active
for
a
new
contributor
workshop
right
now
and
then
waitlist
for
those
who,
like
have
we're,
not
kubernetes
github
board
members,
since
we
have
so
many
and
we
have
so
many
less
seats
for
those
but
yeah.
We
know
we
plan
to
open
those
up.
October
I
think
it's
15th
or
20th,
but
I
have
a
feeling
it's
gonna
sell
out
before
then
so
waitlist
will
probably
not
be
if
like,
if
I'm
a
gambling
person
I,
don't
think
waitlist
for
current
contributors
will
get
in
new
contributors.
That
new
contributors
is
another
story,
though.
I
B
Went
live
without
Ricci
today,
which
means
we
have
three
open
internships
available,
one
for
multi-tenancy,
another
for
contributor
experience
and
another
for
cluster
api
shouts
shout
out
to
Red
Hat
for
providing
funding
for
two
of
those
Sancia
for
the
other.
So
we'll
have
some
really
good
projects
to
present
in
the
spring
of
20,
but
out
Ricci
right
now
has
roughly
600
applicants
that
are
looking
at
the
looking
at
everything
that's
available,
including
the
kubernetes
projects.
B
What
this
means
for
you,
though,
as
contributors
is,
you
should
be
labeling
your
stuff,
help
on
it
or
good
first
issue,
because
there's
going
to
be
new
folks
that
are
going
to
comb
through
that
as
part
of
their
application
process.
They
have
to
make
a
contribution
so
just
note
that
the
uptick
in
people
claiming
issues
and
things
like
that
is
going
to
increase
I'd,
say
within
the
next
two
to
three
weeks.
J
I
Okay,
so
there
were
two
things:
one
is
the
diversity
scholarship
itself
from
CNCs
for
San
Diego
is
already
announced
the
list
of
P
there's
a
bunch
of
people
who
made
it
so
thanks
to
ciencia.
For
that
the
other
one
was
just
travel
scholarship
for
people.
We
think
we
need
they're
like
people
who
are
working,
who
ever
role
in
cig
release
and
things
like
that
for
San
Diego.
What
we
had
discussed
was
that,
if
sig
release
or.
I
Some
of
the
other
six
have
a
need
for
it.
It'll
be
a
one
on
one
basis,
just
let
let
us
know
and
then
we'll
run
with
it,
but
for
the
next
upcoming
summits,
CN
CF
will
come
up
with
a
program
which
will
which
they
will
roll
out
across
all
projects.
I
have
to
check
on
exact
status,
of
that.
That
was
the
intent
when,
on
the
PR
or
issue
there,
where
we
were
trying
to
come
up
with
a
policy,
but
I
have
to
go
back
and
check
with
them.
K
I
guess,
if
there's
nothing
else,
my
name's
Chris
Conway
I'm
new
to
the
group,
so
I
thought
I
would
introduce
myself
I'm
a
software
engineer
at
sa
P
I
spent
the
last
three
years
focused
on
blockchain
technology
and
ruined
my
work.
I
learned
about
kubernetes
and
used
it
a
little
bit
so
I
think
I
want
to
spend
a
couple
hours
a
weekend,
maybe
giving
back
a
little.
If
people
have
suggestions.
Are
nice
live
in
the
Bay
Area
and
want
to
get
coffee
feel
free
to
say
hi.
K
D
All
right,
Tim,
you
wanna
just
put
on
the
shades
one
more
time.
I
know
it's
the
last
sunglasses
battle
all
right,
so
so
we're
gonna
have
to
get
some
sent
to
Tim's
and
Aaron
and
the
new
folks,
maybe.