►
From YouTube: Kubernetes Community Meeting 20160609
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
Demo node problem detector, 1.4 release schedule, PM working group update.
A
So,
as
I
start
every
community
meeting,
this
is
public
and
recorded
and
today
is
Thursday
jun
9th,
and
this
is
the
Cooper
nidhi's
community
meeting
that
happens
weekly
this
morning,
we
have
on
the
agenda
a
node
problem,
detector
that
will
be
demoed
and
that's
with
lentil
oof.
Then
we
have
we
have
no.
Why
do
you
contribute
segment
this
week?
We
will
begin
those
next
week
while
we're
return
to
those.
A
We
didn't
have
enough
people
joining
from
time
zones
where
it
was
more
convenient,
and
the
next
notice,
of
course,
is
now
is
the
time
to
get
your
documentation
into
1.3,
and
if
you
want
to
help
us
figure
out
how
to
celebrate
Cooper
Nettie's
first
birthday,
please
send
a
note
to
me
or
Bob
Burtynsky
and
the
our
emails
are
both
in
the
notes.
So
with
that
lantau,
are
you
game
to
get
started
and
give
us
that
devil?
Oh
yeah,.
A
B
Everyone
I'm
nan,
Chao
Maggie's,
have
IDs
randomly
oh
I'm
from
the
google
corn
in
haste
no
team,
and
today
the
topic
is
about
node
Club
problem
detector
is
an
alpha
feature
introduced
in
Coober
Nick,
his
1.3
o
summa
Sarah,
ok,
son,
oh
sorry,
and
so
shall
it
is
just
a
daemon
running
on
each
node
trying
to
detect
the
node
problem
and
to
the
API
server
and
the
motivation
of
doing
this
is
as
simple.
During
the
last
several
releases,
Cooper
was
really
suffering
from
the
node
problems,
especially
other
problems.
Sometimes
the
colonel
encountered
dialogue.
B
Sometimes
the
talker
just
hung
there
forever
and
when
that
happened,
a
couplet
can
do
nothing
and
but
for
now
Corinne
he
doesn't
have
any
knowledge
about
this.
It
will
keep
on
scheduling
newport
to
the
bad
note,
and
the
court
will
feel
and
keep
on
and
schedule
another
one
field
keep
doing
this,
and
so
this
problem.
Firstly,
we
need
to
make
this
kind
of
problem
visible
to
the
control
plan,
and
if
we
have
this,
then
we
can
try
to
divide
some
remedy
system
to
remedy
the
band.
No
to
save
the
pulse
on
the
node.
B
Something
like
that.
So
the
node
problem
detector
is
just
for
the
first
step
to
make
the
node
node
problems
available
and
now
the
node
problem
attacker
is
demo
site
planning
on
each
node,
detect
problems
and
report
them
to
the
PI
server,
and
we
know
that
people
running
coordinated,
some
various
environment
may
be
different.
Ost
shows
different
hardware's
and
different
runtimes
a
lot
of
arrows.
We
know
that
no
Damon
can
not
handle
all
these
different
environment,
so
we
make
the
problem
problem,
the
capital
totally
accessible.
B
B
B
It
is
just
a
dedicated
folk
awareness
and
wood
which
really
like
to
work
with
our
community
friends
to
integrate
with
your
existing
solution
to
make
it
make
the
to
make
it
more
powerful
to
make
grunting
who
ended
his
more
stable
and
after
this,
in
the
future,
we
may
introduce
the
remedy
controller
to
try
to
remedy
the
bad
note,
but
that
is
the
future
scope
enough
now
and
for
the
user
facing
API.
The
node
problem
detector
will
report
the
problem
as
node
condition
and
event.
The
null
condition
is
just
a
field
in
the
nose
stickers.
B
We
already
have
some
conditions
like
radial,
node
out
of
disk
or
something
and
in
the
future.
The
note
prompt
problem
detector
will
report
the
permanent
problem,
which
makes
the
note
available
for
other
animals.
The
bottom
has
no
condition
such
as
Colonel
devil,
bad
disk
value.
Cpu,
dr.
Khan,
something
hand
for
the
temporary
problem
with
would
also
like
to
collect
these
kind
of
information.
So
with
a
result
of
nice
event
event-
and
this
is
a
carbon
stickers
of
the
node
calm
problem-
detector-
a
eighties
it
now,
it
is
an
atom,
hard
running
a
enabled
by
default.
B
In
GC
is
running
on
each
node,
each
node
and
we
having
to
introduced
the
first
problem
game
on
Colonel
monitor.
It
is
just
afore
the
current
his
urgent
requirement
and
also
as
a
reference
of
other
ones.
It
monitors
the
colonel
log,
detect
some
known
issues
following
predefined
rules
and
it
will
report
colonel
dialogue
condition
here.
Instead,
it
is
totally
extensible
you
can
clear
it
is
here.
B
Is
the
config
file
of
the
colonel
monitor
and
see
that
old
conditions
and
the
mighty
problem
matching
Titan,
totally
config
book,
and
this
list
can
be
extended
over
time
one
way
in
filter.
We
have
only
encounter
some
other
doctor
or
Colonel,
but
don't
panic.
Maybe
we
can't
detect
this
hopefully,
and
then
it
is
a
sample
time,
because
we
don't
have
a
really
don't
really
have
a
bad
note
in
hand.
So
we
can
only
inject
some
I
logs
with
we
have
seen
before
to
mimic
the
idol
and
now.
B
Wait
wait
now
we
can
catch
some
temporary
arrow,
such
as
autumn
allocating
and,
for
example,
this
one
they
see
the
permanent.
I
will
wait.
We
have
debug
debug
this
for
quite
a
long
time
to
unicorn
is
one
point:
release
it's
a
kernel
bag.
It
is
still
there
or
not,
but
we
have
a
work
on
so
in
filter.
If
this
hadn't
heaven
at
least
we
can
detect
this
problem
and
maybe
avoid
to
schedule
calling
on
to
the
node
in
the
filter
and
some
other
iosys
guys,
dr.
Hong
ifs,
more
corn,
something
okay
and.
B
The
demo
script
is
just
a
single
strict
squid
that
went
for
the
demo
and
weight
already
had
I
study
this
class,
or
yesterday
we
have
phone
off
running
and
wave
or
they
study
either.
No
problem
can't
receive
any
ice
when
I
snowed
and,
let's
just
care
about
a
random,
select
one
this
one.
Let's
just
care
about
this
one.
B
We
can
see
that
now
we
have
a
new
kernel,
dialogue,
condition.
It
is
false
and
it
means
that
the
car
no
votes
will,
and
there
is
no
event
now.
Firstly,
lies
inject
a
meaningless
love.
This
log
is
full
of
Colonel
Locke
if
the
knowledge
granita
is
running
daughter
and
if
we
inject,
if
we
inject,
there's
nothing
to
heaven.
So
let's
have
a
try.
Oh.
B
B
B
B
And
the
condition
should
be
changed
yeah.
You
can
see
that
still
colonel
dialogue
and
within
stalker
Hong
and
yeah
with
the
I
message.
Yeah
in
fact
that
this
does
it.
That's
it
and
I
mentioned
that
the
the
the
configuration
is
totally
extensible
in
filter.
We
can
oh,
we
can
detect
more
and
more
Colonel
box
and
darker
issues
and
here's
the
Future
fan
so
detective,
not
detect
the
problem
in
just
the
first
step
after
that
way.
After
that,
we
know
that
there
are
some
panels
we
want
to.
B
We
will
try
to
ram
did
and
in
the
future,
maybe
we'll
introduce
the
remedy
controller.
It
just
monitored
the
noticed.
A
Thursday's
convert
convert
the
problems
we
ought
to
attend
latent
field,
the
10th
the
10th
is
introduced.
Also
in
also
an
alpha
feature
introduced
in
1.3.
It
is
similar
risk
and
schedule,
but
not
exactly
exactly
the
same.
B
If
you
are
interested
to
work
with
us
or
you
have
any
comments,
feedback
feel
free
to
contact
us.
This
is
my
email,
give
a
body
and
are
you
can
also
join
our
signals?
Group
22
or
value
show
animals
okay,
and
we
have
trapped
design,
dog
umbrella
issue,
and
now
it
a
no
problem.
Detector
is
separable
under
the
porn.
It
is
directly
yeah.
That's
it
lantau.
B
C
Bob
asked
us
to
see:
yeah
I
was
always
just
a
clarification.
Man
I
think
it
seems
like
on
the
surface,
that
demon
said
is
exactly
the
mechanism
the
you
with
that
that
was
built
with
handle
cases
like
this,
where
you
need
to
run.
You
know
one
one
thing
per
node,
for
example
you
monitoring
activity.
So
my
question
here
is:
why
not
use
daemon
set
for
this?
This
is
tim.
It.
D
A
D
I'm
looking
are
yeah,
we
all
look
under
to
provide
the
alternative
or
a
continental,
for
example,
for
1.4.
Have
the
rattling
hiss
1.0
release,
which
is
a
lot
alternative.
The
red
container
enter
yes,
and
we
also
talked
to
the
oci
compatible
runtime
support
and
we
asked
for
community
help
and
the
from
many
different
partner,
and
so
they
can.
They
can
provide
an
excellent
I'm
cracking.
So
we
are
working
on
the
interface
at
this
moment
and
make
that
cocky
easier
and
have
the
mode
as
well
requirement
for
each
children
time.
A
E
E
I
like
are
they?
Are
there
particular
problems?
You've
already
decided
that
fund.
That
would
be
like
not
appropriate
to
detect
using
the
solution,
just
wondering
if
we
should,
if
the
queen
is
looking
to
help
other
certain
areas
that
we've
already
thought
about.
That
would
probably
not
good
fits
for
this
problems
affect
their
and.
D
How
to
actually
don't
know
the
problem?
The
character
is
just
said
already
well,
I
/,
incriminate
his
mold
and
how
we
are
going
to
crack
the
problem
and
how
we
are
going
to
propagate
with
other
and
the
moster
problem
detected
a
is
dry
as
a
separator,
a
beam
inside
we're
also
talking
about
that.
Maybe
this
is
a
negative,
is
kind
of
a
human
egg,
and
we
talked
about
this
kinda
miss
not
having
to
follow
last
night.
D
What's
the
macbeth,
but
there's
a
lot
of
problem,
and
so
we
have
only
stuff
as
an
Entenmann's
in
other
one
who
customers
know
the
problem,
detector,
that
demon
said
we
make
you
could
plug
into
different
a
different
problem.
Female
Robin
detector
be
met
and,
if
example,
for
how
to
our
issues.
Actually,
no,
we
talked
to
the
entire
day.
They
really
won't
have
on
the
five
things.
I
think
you
guide
the
memory
protection
to
liquid
once
they
have
that
demon
Randy's.
D
We
can
pack
into
our
loaded
penalty
exit
scene
inside
and
then
we
put
those
problem
for
some
our
baby's
kisses.
We
also
have
not.
There
are
internal
TKE
Mexican,
the
MIP,
and
then
we
have
some
signal
give
to
us.
So
we
can
say:
okay,
dced
knows
that
there's
something
which
one
of
node-
and
there
are
some
issues
this
one
to
make
it
a
thousand
and
propagate,
and
you
also
talk
about
chillin
enter
people's
community,
constantly
have
some
few
sauce
in
idiot.
The
problem,
though,
if
you
seek
knowledge
when
human,
it
also
is
pad
awful.
A
I'm
gonna
have
to
cut
us
off
here
the
best
place
to
go
discuss.
This
is
signaled
correct
and
if
you
end
up
to
break
off
to
another
group,
then
you
guys
get
to
do
that.
So
there
was.
There
was
a
comment
or
two
from
Justin
Santa
Barbara
about
other
status
names.
Things
like
that.
It
sounds
like
those
should
have
social
side
into
the
signal
group.
So
thank
you
very
much
lenta
for
the
demonstration
and
we
will
jump
on
to
the
next
topic.
Oh.
F
A
F
F
F
No
that's
great,
but
then
pivoting
go
1.4
1.5.
We
want
to
start
to
set
out
our
schedule
and
goals
for
when
we
can
launch
these
things
so
just
for
I
wanted
to
put
it.
This
is
actually
on
our
community
wiki,
so
you
can
see
github
to
come.
Cooper,
Nettie's,
community,
repro
and
then
wiki
is
here.
So
anyone
can
edit
this
I
guess,
don't
don't
go
deleting
it
or
giving
anything
too
crazy,
but
just
for
history,
so
we
launched
in
July
of
2015.
F
So
that's
sort
of
what
things
are
looking
like,
so
I
sort
of
took
that
as
an
input
and
the
other
input
I
took
as
axiomatic
was
that
we
want
to
have
two
more
minor
version
releases
this
year.
So
in
2016
we
would
want
to
have
both
a
1.4
and
a
1.5,
and
so
given
that
it
looks
like
we'll
have
to
move
a
little
bit
quicker,
compress
the
milestones,
and
so
this
is
kind
of
how
1.4
and
1.5
would
lay
out.
F
Given
those
items
for
1.5
I
picked
December
9th
as
a
Friday
that
gives
us
about
a
one-week
buffer
to
the
16th.
If,
if
things
slip,
I've
been
a
week
after
the
16th
is
the
23rd
and
that's
probably
not
a
really
time
that
we'd
want
to
release
there'll
be
a
lot
of
people
on
vacation,
and
things
like
that.
F
F
F
You
know:
that's
that's
a
toss-up
if,
if
we
can
move
to
four
I,
think
that
we're
putting
a
lot
of
effort
into
flakes
and
submit
cube
fixes
now,
and
so
if
the
submit
Q
stays
healthy,
that
will
certainly
help
getting
everything
in
the
last
few
weeks
with
coding
if
we
keep
the
flakes
under
control.
Obviously
that
helps
during
stabilization.
So
it's
a
it's
a
little
aggressive
on
the
timeline,
but
I
don't
think
it's
unreasonable.
A
F
Totally
so
that's
basically
it
the
only
other
note
is
41.5.
I
did
do
five
weeks
of
stabilization
and
release
because
the
Thanksgiving
us
thanksgiving
holiday
is
in
there,
but
but
the
winter
holidays
would
not
be
in.
We
probably
will
start
1.6
January.
Second,
something
like
that,
but
looking
for
feedback
and
everything
I
think
that
we're
relatively
constrained,
though,
if
we
actually
want
to
get
to
minor
releases
out
this
year,.
A
You'd
been
talking
more
broadly
about
moving
to
a
time-based
released,
as
opposed
to
a
feature-based
release.
Is
that
really
by
saying
we're
going
to
do
two
more
this
year?
Is
that
really
the
proposal
here
is
that
we
will?
We
will
do
the
two
more?
That's
the
the
presupposition,
as
you
said,
and
and
we
will
fit
the
features
that
fit
into
them
as
they
come,
and
then
they
will
slip
any
feature
that
doesn't
make
the
release
cut
off
will
slip
to
the
next
one.
Yeah.
F
I
think
that's
what
we
we
would
have
to
full-on
make
the
pivot
to
say:
that's
how
the
project
works
and
how
the
project
runs
in
1.3.
We
did
hold
ourselves
to
a
pretty
high
standard
on
this
feature.
Complete
date
saying
there
are
several
things
were
very
close
and
we
push
them
out
and
that's
painful
at
times,
but
stabilization
has
been
better
this
time
than
in
past
time.
So
I
think
we've
seen
the
result
of
that
up,
really
cutting
down
mature
and
on
time,
so
yeah
I
think
it
would.
F
F
The
definition
is
that
we've
said
that
you're
in
the
queue
with
all
code
required
for
new
features,
plus
in
to
end
tests
in
1.3.
We
said,
but
not
counting,
Docs
and,
of
course,
not
accepting
that
the
code
could
be
party.
There
could
be
flakes
like
there's
a
lot
of
things
that
you
discover
after
the
feature
goes
in
and
really
gets
beat
up
by
the
PR
builder.
F
H
G
I'm,
asking
from
the
perspective
of
the
Eric
Tunes
fantastic
work
on
the
so
whole
feature
proposal.
Workflow
I
was
sort
of
curious
if
we're
actually
like
committing
to
doing
that,
and
using
that
to
sort
of
document
what
feature
is
and
what
feature
complete
is
and
what
the
steps
are
to
move
through
the
process.
That
sort
of
thing
yes,.
F
Definitely
I
I
do
want
to
go
use
that
I
think
that
will
help
a
lot
towards
the
end
towards,
like
you
say,
both
ensuring
what
features
feature
complete
applies
to,
of
course,
and
then
also
the
end
of
milestone.
As
we
go,
build
docs
and
go,
you
know,
build
all
the
collateral
around
announcing.
It
will
have
that
sort
of
ready
in
one
place.
A
J
A
So
we
generally
do
a
retrospective
after
the
release
in
this
community
meeting,
and
we
were
not
as
good
last
time.
Okay,
so
1.2,
we
kind
of.
Did
it
at
hawk
one
or
sorry
1.1.
We
did
it
at
hawk
1.2.
We
did
it
with
about
four
hours
notice,
so
people
didn't
feel
that
there
was
a
lot
of
time
to
give
feedback,
and
this
time
I
will
put
it
on
the
schedule.
Right
now,
for
the
week
after
the
release,
I.
C
D
C
A
K
K
Sorry,
TJ
and
I
are
in
the
same
room,
not
projected,
so
that's
the
failure.
Alright.
So,
as
we
talked
about
last
week,
we
want
to
formalize
the
feature
process
I,
which
things
get
approved
and
into
Cooper
Nettie's
as
a
whole
for
those
that
have
been
paying
attention
on
the
coup,
benetti's
dev
mailing
list
or
at
last
week's
community
meeting
we
shared
many
times.
K
I
also
tried
to
reach
out
to
as
many
folks
as
I,
possibly
could
track
down
to
ensure
that
everyone
was
aware
of
the
formation
of
this
group
and
that
we
are
currently
in
the
process
of
putting
together
some
plans.
Since
then,
we've
already
engaged
and
started
to
create
some
high-level
documents.
Right
now,
we
do
currently
have
a
feature
repository
that
you
can
go
and
create
features
in
there's
a
walkthrough
for
how
to
go
about
that
and
things
like
that.
But
most
importantly,
we
do
have
a
feature
proposal
of
which
I
believe
all
right.
K
Yes,
so
we
do
currently
have
a
feature
proposal,
and
this
is
again
how
we
would
like
to
run
the
organization
as
a
whole
or
the
project
hole
where
the
community
decides
on
the
features
that
ultimately
make
it
similar
to
some
other
best
practices
that
we've
seen
across
the
you
know
open
source
world,
so
I
guess
without
further
ado.
Would
you
like
to
present
a
proposal
and
walk
us
through
your
thinking,
yeah.
L
So
there
are
a
number
of
kind
of
absurd
on
Doc.
There
are
a
number
of
proposals.
That's
been
around
right,
so
we
started
with
proposal
Eric
and
mother
I
believe
put
together
back
in
April
right.
This
is
a
proposal
that
describes
the
idea
of
feature
repository
right,
and
so
we
basically
we
created.
He
currently
created
a
second
document.
We
should
probably
go
to
merge
into
this
one
if
everyone
agrees
right,
so
this
document
I
think
there
has
been
a
number
of
comments
and
kind
of
it's
more
about
how
to
create
the
feature.
L
What
should
be
in
the
feature?
What
happens
with
the
feature
next
right?
Then
so,
and
there
is
a
faq
on
why
it's
important,
and
so
what
we
did
is
extended
further
kind
of
chick
specifies
on
the
features.
Let
me
quickly
walk
beep
over
it
right,
and
so
the
document
link
is
shared
for
the
cone
is
open
for
the
comments.
L
So
there
is
basically
it
you
built
a
kind
of
erotica
project
management
to
on
top
of
github,
which,
as
all
of
us
know,
please
get
help
is
non-trivial
and
and
the
point
of
B
or
having
it
kind
of
well
I.
Think
of
a
lot
of
people.
The
experience
was
it's
wild,
a
bunch
of
PRS
it's
pretty
hard
to
track
here,
are
quickly
what
features
actually
go
in
into
the
release.
What
you
said
state
of
the
features
people
use,
sticks,
community
meetings,
constantly
asking
questions.
So
what
happened
to
his
pad
sets?
L
What
happened
to
Z
is
what
happens?
Is
that
right?
So
there?
It
is
to
kind
of
as
much
as
possible
to
automate
this
process
and
be
able
to
maintain
continuous
dashboard
on
top
of
github
features
and
undo
I
NPR's
about
the
status
of
each
issue
right.
So
we
start
these
features
kind
of
all.
The
features
need
to
be
created
based
on
previous
document
and
then
when
people
start
creating
pr's
right.
L
The
suggestion
is
instead
of
carefully
embedding
links
to
all
the
PRS
into
the
future,
which
kind
of
may
or
may
not
happen
to
insist
that
the
otrs
should
be
labeled
specifically
non
bug.
Pr's
right
things
like
feature
proposal
documentation
and
to
end
test.
They
all
should
be
contain
a
label
with
speech
in
its
ID
or
something
of
this
type,
so
that
we
can
build
some
simple
code
to
scan
all
the
Reapers
and
basically
automatically
link
the
RS
into
the
feature
set
into
the
fee
into
the
features
that
way
we
can
maintain.
L
L
Why
specifically
call
out
John
dog,
TRS
I
mean
kind
of
we
can
define
kind
of
right.
This
is
a
proposal.
Would
I
am
open
to
kind
of
suggestions
right,
but
he
is
the
kindest
feature
or
discussion
proposal
or
documentation
right,
the
ID.
It
has
to
belong
to
some
feature
box.
Maybe
the
box
from
the
previous
life.
G
Sure
I
interest,
in
the
context
of
like
the
current
release
cycle
right,
like
there's
still
a
lot
of
bugs
that
are
open,
that
we're
going
to
squash
before
we
get
the
release
out
so
I'm
trying
to
understand,
if
bugs
or
something
that
are
the
closure
of
bugs,
is
not
necessary
to
reach
feature
complete
or
if
the
closure
of
bugs
is
necessary
to
reach
feature
complete.
So.
L
Yeah,
so
it's
kind
of
the
below
was
right.
So
if
the
bug
Israel
clearly
related
to
the
future
here
all
right,
then
yeah.
It
should
be
labeled
to
the
feature
right,
but
sometimes
their
box,
which
come
out
out
of
previous
releases
and
say
it's
hard
to
Utley,
be
contribute
to
current
set
of
features
being
released.
So
I,
don't
think
those
necessarily
have
to
be
labeled
right.
L
G
L
So
I
mean
the
it's
scalable
only
up
to
a
point
right,
so
we
have
to
rely
a
lot
on
sig
leads
or
if
they
have
a
lieutenant
to
whoever
they
kind
of
heaven,
zc
great,
who
is
responsible
to
foreign
force
in
this
behavior
right.
The
alternative
is
just
automatically
not
merge.
The
any
would
any
PRS
that
don't
have
related
Fisher
label.
L
What's
the
status
of
this
particular
feature,
so
the
other
things
kind
of
and
that
shouldn't
relief
with
the
dates
at
TJ
proposed
some
of
the
proposals
observations
from
one
to
three
and
prior
to
that
right
all
features
must
have
an
owner
and
committed
implementers
bye
week,
for
this
is
arbitrary
date.
We
can
do
weeks
three
week
why,
if
I
know
that
stopped
discussion
is
TJ
and
community,
basically
its
future
proposal.
Freeze,
what's
happened
in
one
two
three:
is
there
a
bunch
of
features
which
came
out
of
cigs?
L
They
will
mark
t0
and
then
half
meets
through
the
cycle.
It
turned
out
that
nobody's
implementing
them
because
resources
were
moved
so
to
avoid
this
situation
and
then
all
PRS
with
actual
implementation
proposals
need
to
be
lgtm
bye
week.
Seven
and
the
idea
behind
it.
There's
limited
number
of
maintainer
pretty
busy
people.
So
if
you
can
front
load
all
the
approver
approves
of
proposals,
it
will
help
tremendously.
L
A
C
L
C
O
P
L
K
L
H
Also
think
that
we
kind
of
have
made
a
decision
all
along
that
we
need
to
enable
people
to
use
vanilla
github,
like
just
random
people
who
run
up
to
the
project,
and
so
the
concern
was
a
lot
of
these
tools.
Is
that
they
that,
while
they
provide
utility,
they
kind
of
make
in
ellicott
hub
impossible
to
use
I
know.
A
O
K
O
I'm,
just
kind
of
had
like
a
feature
like
like
signo
much
XO,
again
adding
device
not
for
accounting,
supporter
right
and
majority
that
work
is
in
the
advisory,
so
I'm
just
wondering
like
do
we
have
to
plan
everything
around
all
these
can't
mentally
throws.
With
this
in
mind,
order
it
like
speak,
like
the
labeling,
would
have
been
kind
of
not
well
served
on
that
particular
future.
So
I'm
just
trying
to
think
through
that
yeah.
K
I
mean
this
is
not.
This
is
neither
process
for
processes
say
ignored.
Do
we
have
to
have
like
a
hundred
percent
like
every
you
know,
one
hundred
percent
solution
on
day
zero?
Our
goal
is
that
it
should
be
the
exception.
Not
the
rule.
Orcses
me,
the
rule,
not
the
exception,
that
everything
follows
this
guy
and
you
know
if
if
it
makes
have
an
exception
or
something
like
that,
if
the
community
decides
that
hey
it's
okay,
then
fine.
You
know
we
we're
not
worried
about
this,
but
right
now
we
have
no
process,
no
rule
whatsoever.
G
G
L
G
K
Yeah,
I
don't
disagree.
I
mean,
I
think,
that
the
two
things
that
are
that
are
here
the
only
two
things
that
are
captured
here
is
we
really
don't
want
to
have
kind
of
the
issue
that
we
ran
into
this
time,
which
is
there
were
a
set
of
poesy
rows
where
owners
were
not
identified
early
on
and
and
they
just
kind
of
languished
out
there
number
one
and
number
two
there's
the
reality
of
when
our
code,
freezes
and
and
and
those
are
the
only
two
realities
represented
here.
G
K
So
we
absolutely
do
have
that
it's
not
represented
here.
You
please
go
to
the
crew
benetti's
feature
repo
and
click
on
issue
template
in
that
you
have
a
series
of
gates
where
needed
to
alpha
beta,
stable,
I'll
posted
in
the
what'd.
He
call
it
and
each
one
has
a
set
of
check
marks
next
to
it
that
are
required.
So
it's
not
it's
not
date
driven,
but
it
is
kind
of
stability
or
I,
guess,
completeness,
driven
and
and
we've
heard
from
the
community
generally
that
dates
or
even
t-minus
dates
are
aren't
fantastic.
K
G
I
L
Enough
and
then
I
mean,
if
they're
features
which
have
to
be
kind
of
merged
past
this
deadline
right,
we
need
to
all
kind
of
go
with
it,
so
there
has
to
be
elders,
community
p.m.
whatever
the
group
has
to
do
the
discussion
and
approve
it
at
least
informally,
and
there
should
be
fully
understanding
that
it
means
there
is
a
scope
creep
and
that
Mary
jeopardize
release
dates.
So.
L
And
as
I
said,
I
did
old
box
race
to
the
feature
should
contain
official
able
to
track
it
back
and
then
the
other
observation
wasn't
planning
right
out
of
lust
123
planning.
There
were
a
lot
of
cigs,
which
came
out
only
with
p0
type
features.
I,
don't
think
it's
fully
realistic
I
think
they
should
be
kind
of
right.
There
should
be
some
ratio
where
there
is
some
amount
of
p0.
Some
amount
of
p1
sp2
sp3
is
coming
out
of
this
planning
right.
I
am
kind
of
open
to
discussion.
L
What
the
ratio
should
be
one-third
p0
is
50%,
p0
is
just
my
generation.
We
cannot
have
six
coming
out
and
saying
you're
going
to
tempe
zeroes,
that's
not
gonna
end
well
and
then
so.
The
reality
in
1230
a
bunch
of
features
with
deprioritized
in
the
middle
of
the
release
cycle,
2,
p-10
features,
and
so
why
not
don't
we
accept
the
reality
from
get
go
to
slightly
better
prioritization
up
front
and
split
it
issues
this
way
and
then
kind
of
reiterates
a
little
bit
right.
So
owners
of
the
features
need
to
align
the
resources
by
week.
L
K
I
mean
to
be
to
be
clear,
you
know
if
you
have
the
people
and
you
have
the
proposal
in
and
the
community
feels
like.
This
is
a
good
thing
and
you
can
accomplish
it
within
the
milestone.
It's
kind
of
set
to
go.
It's
not
like
you
know,
you're
gonna,
put
in
something
that
we
feel
is
that
that
you
know
person
a
says,
well,
I,
I,
don't
care
about
this
feature
at
all
a
person
be
sis
I
care
about
it
deeply
and
I'm
ready
to
allocate.
K
L
Know
when
agreement
it
just
kind
of
it's
nice
to
have
this
discussion
advance
it's
that
instead
of
marking
somethin
as
whatever
is
a
priority,
see
and
then
turns
out
it's
again.
It's
all
just
too
it's
the
clarity
and
then
turns
out
that
nobody
align
actually
any
people
to
work
on
it.
So
I
kind
of
that
may
go
back
to
the
features
repository
to
have
at
least
some
proposed
list
of
github
IDs.
L
Who
is
responsible
for
this
feature
so
that
if
people
ask
questions
in
all
from
to
reach
out
and
then
I
kind
of
another
proposal
is
to
introduce
and
I
think
this'll
a
kind
of
exists
that
owners
and
maintainer
should
abide
by
it.
So
ang
features
they
manage
right
and
if
they
manage
way
too
many
features
that
maybe
this
feature
should
be
dropped
in
advance
right.
It
just
doesn't
scale
and
it
just
leads
to
a
lot
of
the
archer
nan's.
The
end.
L
L
L
A
A
A
We
can
catch
up
with
cigs
next
week,
then
that
sounds
like
a
plan
for
running
rapidly
out
of
time.
So
let
me
cover
notices
again
for
the
people
who
weren't
here
at
the
very
beginning,
we
tried
the
Asia
friendly
timing
for
two
months
on
one
one
meeting
a
month
and
we
had
more
people
for
whom
it
was
super
inconvenient
than
people
appearing
that
where
it
was
more
convenience
at
that
time.
A
A
There's
a
point
about
documentation.
Tj
mentioned
that
documentation
was
not
part
of
feature
complete
this
time.
1.3.
That
means
now
is
the
time
to
get
your
documentation
in.
We
had
a
lot
of
trouble
around
1.2
getting
documentation
in
after
the
release,
so
we
want
to
get
as
much
of
it
in
before
the
release.
So
please
prioritize,
please
ask
for
help.
A
If
you
need
help,
please
please
get
us
documentation
in
for
the
1.3
release
and
then
my
last
notice
is
the
Cooper
Nettie's
first
birthday
is
july
twenty
first
and
we
want
to
do
some
fun
celebrations
around
the
world
and
I
need
help
with
that,
as
does
bob
produce
key
to
make
that
happen
in
more
locations
than
just
where
we
are
so,
please
send
us
emails.
If
you
are
interested
in
helping
plan
celebrations,
maybe
it's
a
special
meet
up.
We
can
help
with
you
know:
I,
don't
know
cake
and
cookies
and
pie
or
something
anyway.
A
E
E
E
For
example,
like
someone
you
know
jobs
when
I'm
a
big
guy
right,
someone
goes
into
scheduled
jobs
right.
What
sig
is
that
associated
with
and
like
in
my
head,
I
could
say:
oh
no
machinery
but
I
participate
on
that.
Suddenly
there
so
I
guess
very
much
little
puzzle
is
tied
for
cigs
and
I
feel
like
a
lot
of
the
features
we
work
on
this
in
this
way
associated
with
a
clear
cigarette
right
now
and
maybe
I'm
wrong
in
that
assumption.
Now.
A
A
A
E
E
Yeah
I
mean
I,
think
it'd
be
a
little
bit
like
the
set
of
features
that
we've
worked
on
us
Adam
just
to
ask
where
they
align,
but
if
you're
asking
next
week
in
the
community
meeting,
I
guess
I
don't
know
if
I
will
have
the
time
to
prepare
for
that.
But
it's
just
an
open
question
and
they
we
can
talk
about
it
on
communities
down.
Okay,.
A
H
A
H
E
E
The
ad
hoc
signet
will
form
around
something
if
you're
touching
it
like,
like
whoever's
like
if
you
I'll
just
pick
an
example
like
if
you
want
to
do
a
feature
in
jobs
like
whoever
is
the
current
listing
of
owners
and
like
a
job
package
that
seems
like
the
ad
hoc
cig,
you
should
work
together
on
this,
and
maybe
we
should
update
the
workflow
proposal
to
kind
of
reflect.
What
we
anticipate
would
be
more
ad
hoc.
H
A
We
are
at
eleven
o'clock.
It
seems
like
there's
enough
that
this
discussion
should
continue,
maybe
on
the
email
list
or
in
the
slack
channel
and
brian
has
also
been
sending
notes
in
here
about
the
owner,
where
the
owners
are
documented
and
asad
that
he
will
lead
either
has
created
or
will
create
github
teams
for
future
owners.
So
there
is
more
discussion,
it
sounds
like
so
apologies
it
does
eleven
o'clock.
I
am
losing
my
room
and
I
will
see
you
all
next
week.