►
From YouTube: 20170309 Kubernetes Community Meeting
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
Release 1.6, 1.5; SIG Scheduling, SIG Testing, Demo Bulk LGTM tool; Community Survey Discussion
B
C
C
D
D
Has
the
early
train
keeps
going
and
here
to
give
an
update,
so
we've
been
putting
out
these
No
Go
Go
status
report
and
currently
we're
in
an
notice
so
as
an
we're
not
currently
ready
to
big
relief
for
enough
the
things
are
preventing
that
11.
Is
there
still
ugly
fisting
in
the
1.6
miles,
Jono
get
up,
there's
totally
distinct,
and
you
can
see
the
breakdown
by
stick
as
long
as
the
bar,
as
well
as
the
changes
rotting
yesterday,
there's
also
some
space
that
should
try
to
get
some
of
this
as
a
milestone
and
someone's
done.
D
A
really
good
job
is
trying
to
get
rid
of
it,
but
we
should
keep
ish
going
on
trying
to
so
if
there's
a
place
that
in
the
milestone
that
cuz
it's
like
in
a
very
long
time,
strip
of
it.
Otherwise
we
should
decide
whether
this
is
a
release.
Locking
plate
and
magic
decision
should
be
made
at
the
state
level.
D
F
Yeah
so
dress
aburre
forbid
from
me.
We
have
29
th,
put
them
on
data
package
in
one
of
the
six
we
anniver,
so
fun.
Element
of
them
and
I
would
also
share
my
respect
to
people
who
are
who
ever
dated
this
nature
fidgets
with
the
features
we
is
to
release
mouth
and
with
the
documentation,
and
this
is
also
the
coal
for
the
Caza
teacher
illness,
who
haven't
yet
done
that.
C
You
so
much
so
for
when
applies
I
reckon
is
unable
to
join
us,
so
I'll
just
go
and
read
his
points.
It
does
about
15
or
was
released
on
Tuesday,
and
next
up
is
when,
outside
that
size,
approximately
somewhere
between
mar
17
and
20
of
this
one.
We
can
expect
that
okay
and
for
why
not
for
is
just
about
here,
I.
B
E
I'm,
just
gonna
do
a
brief
overview
of
high-level
items
for
16
right
now.
We're
currently
in
sort
of
lockdown
for
16
release,
so
folks
are
looking
at
the
lakes
are
also
looking
at
bugs
and
there's
a
couple
of
occupation
items
that
are
still
remaining
the
highlights
for
the
16
release.
The
biggest
thing
to
note
is
the
promotion
from
alpha
to
beta
for
a
series
of
API
modification.
A
Klaus
had
worked
on
the
multi
scheduling
off
promotion.
A
veteran
Marik
had
made
changes
to
paints
and
celebration,
so
that
should
be
in
beta
stage.
E
Robbing
myself
had
made
changes
to
node
and
pollen
affinity
and
also
added
a
slight
gate
for
the
chike
folks.
So
they
can
turn
on
support
for
the
Alpha
annotations
should
be
DQ
for
a
transition
period.
During
the
Olympics
released.
There
was
a
lot
of
cleanup
work
on
code
coverage.
I
know
a
lot
of
the
books
from
IBM
had
helped
out
there.
So
many
things
there
is
a
new
google
earth
at
spin.
Spinning
up
this
early
cycle.
E
Bobby
some
summits
agree
besides
nothing
so
he's
going
to
be
helping
David
Oppenheimer
along
the
way
and
helping
with
reviews
and
whatnot.
Some
other
highlights
for
the
16
release.
Is
that
there's
been
a
sort
of
amount
of
cleanup
to
be
able
to
convey
meaningful
information
when
your
pod
is
not
scheduled
change
it
a
lot
of
work.
There
there's
been
some
modifications
to
add
features
to
the
scheduler
extender
and
lastly,
during
this
release
cycle,
there's
a
lot
of
effort
to
clean
up
the
backlog
and
Q
of
items
such
that
we
can
broaden
the
tenth.
E
So
we
can
have
more
folks
contributing
it
and
being
able
to
plug
into
the
fig
scheduling
in
a
meaningful
way
right
now,
there's
contributions
from
google
red
hat
IBM
until
while
I
have
fuel
and
other
folks
I
think
a
biggest
pain
point,
which
kind
of
could
lead
into
Brendan's
talk
a
little
bit
later.
Is
that
as
these
new
folks
try
to
come
online,
there's
so
much
documentation
is
so
much
information.
They
just
want
to
go
from
zero
to
making
a
contribution.
E
So
it's
a
little
difficult
for
them
to
understand
the
minutia
of
how
the
community
works.
They
also
have
had
a
lot
of
pain
with
ree
bases
and
having
enough
people
to
review
their
changes.
So
that's
kind
of
the
overall
picture
of
six
scheduling
for
the
16
release
and
if
you
have
any
questions,
feel
free
to
FM
and
I.
Probably
folks
go
now.
C
A
A
A
Instead
of
individuals
and
potentially
like
restructure
the
tester
that
the
package
structure
so
there's
more
closely
mirrors
with
sig
structure,
I'm,
not
sure
if
we're
over
Conway
lying
this
or
not-
but
that's
you
know,
that's
a
proposal
that
work.
We're
looking
for
comments
on
so
a
couple
cool
things
that
the
group
is
put
together
to
sort
of
help
us
out
here.
A
There
are
many
short
aliases
available
at
go
tapes,
bio.
So
we
have
an
on
call
URI,
where
you
can
see
who's
on
call
right
now
to
build
top
and
who
the
release
team
is.
You
can
go
to
the
test
history
URI,
which
will
tell
you
the
tests,
but
it's
like
most
in
the
past
24
hours
and
which
suite
sets
late
to
the
past
24
hours
most
frequently,
and
we're
currently
experimenting
with
a
sort
of
alternate
view
of
this
data.
A
Recalling
it
is
like
a
triage
board
where,
instead
of
focusing
on
like
which
test
is
failing,
focus
on
the
cause
of
the
failure
and
see
how
many
tests
that
causes
happening
across
it's
super
cool,
you
can
drill
down
there
a
bunch
of
graphs
we're
really
looking
forward
to
presenting
this.
A
little
bit
more
actively
to
the
release
for
announcing
to
help
us
sort
of
triage
out
which
which
are
affecting
us
unless
something,
of
course
I
definitely
want
to
give
a
shout
out
to
you.
A
A
Martha!
So
that's
good
progress
and
we
also
have
some
rate
as
now.
So
we're
trying
to
sort
of
make
that
a
little
bit
more
authoritative
in
terms
of
don't
know
those
signals,
and
we
would
welcome
back
on
what
could
make
that
more
useful,
just
sort
of
an
incidental
thing,
I'm,
not
sure
how
many
people
are
really
interested
or
familiar
with
the
sausage-making
of
how
we
test
up.
A
But
there
is
a
good
bit
of
Jake
and
developed,
and
we've
been
trying
to
remove
as
much
of
that
as
possible,
say
for
a
good
while
we've
been
using
this
program
called
proud,
which
you
know,
helps
us
sort
of
giving
it
a
given
a
github
event.
Do
a
thing
and
it's
we're
really
really
really
close
to
using
Cooper
Nettie's
to
test
Cooper
daddy's
on
Cooper
Nettie's.
All
of
the
cute
brunette
can
I
say
to
benetti's
anymore.
A
So
we're
we're
really
enthusiastic
about
that
and
then
the
the
other
thing
I
guess
I'll
talk
about
is
britain
has
made
a
proposal
about
sort
of
test
clinginess
and
whether
or
not
we
want
to
you
know
start
getting
this
knit
q
on
it,
and
I
think
this
sort
of
gets
to
a
broader
I.
Don't
have
a
bullet
point
for
this,
but
I
just
want
to
sort
of
put
out
there,
the
ethos
or
the
concept
that
perhaps
we
have
way
too
many
end-to-end
tests
and
we're
actually
were
like.
A
We
could
definitely
test
the
same
logic
at
the
unit
level
or
the
immigration
laws,
and
we're
really
interested
in
figuring
out
how
to
have
this
conversation
with
the
right
people
with
the
right
side
owners.
But
in
the
meantime,
we're
very
strong
proponents
of
this
idea
of
shutting
down
the
submit
to
you
if
the
flakiness
is
is
way
too
high.
So
I'm
not
sure
that
we're
necessarily
going
to
be
the
champions
or
implementers
of
this,
but
I
think
the
president's
proposal
which
I
yes
I,
have
linked.
A
G
I'm
happy
to
drive
that
far
as
as
we've
seen
before,
I
think
we've
actually
reached
a
place
where
it
is
enough
consensus
that
we're
going
to
merge
it
and
we're
going
to
build
out
the
signal,
and
maybe
we'll
run
it
for
a
week
and
say
like
hey.
This
is
what
the
data
says
and
now
we're
going
to
start
closing
down
the
queue
or
maybe
we'll
just
start
with
a
Q
close
down.
Joe
penny
did
a
great
little
hack
together,
script,
from
which
the
low
bar
and
I
mean
I.
G
G
The
everything
I
would
say
about
what
you
said
is
like.
Historically,
we've
always
felt
like
integration
tests
would
be
a
good
thing
and
test
command
sort
of
does.
That
sum,
but
we've
just
never
had
a
good
framework,
and
so
I
think
the
reason
that
a
lot
of
the
testing
has
ended
up
in
e
de
testing
is
because
ed
is
where
we
have
the
most
robust
framework
for
things
that
are
bigger
than
unit
f,
like
Louis.
A
G
G
I
agree
with
that,
too.
I
mean
the
long-standing
project
if
anybody's
looking
for
a
cool
project,
a
long-standing
project
that
I
wanted
to
do
is
basically
build
an
HTTP
proxy
that
measures
restful
api
coverage
basically
take
our
swagger
schema,
fit
and
proxy
requests
through,
and
you
can
basically
build
up
this
like
API
coverage.
Metric
nobody's
ever
done
it,
but
it
would
be
really
a
useful,
interesting
thing
to
do.
Yeah.
H
A
I
A
quick
comment,
one
I
think
you're.
Absolutely
right,
I
think,
is
massive
amounts
of
mobile
app
interesting
and
you
could,
by
looking
at
coverage,
we
could
systematically
reduce
their.
The
other
observation
is
you
know
if
we
can't
revised
reliable
test
against
Cuba
native
API,
then
in
all
likelihood,
people
cannot
write
reliable
applications
against
the
communities
API.
So
this
is
a
kind
of
validation
value
in
that.
F
A
Strongly
agree
with
all
that
so
I,
you
know
I'm
putting
this
opinion
out
there
there's,
maybe
a
broader
conversation
to
have
about
sort
of
project
policy
and
I
want
to
get
things
and
whether
or
not
sick
testing
should
be
in
King
charged
with
all
of
that.
But
it's
encouraging
to
hear
that
you
know
we're
not
alone
in
thinking
like
while
we're
trying
to
optimize
the
problem
of
super
flaky
etv
tests
that
exercise
the
entire
system.
Maybe
we
could
get
more
reliable
signal.
A
B
A
C
C
G
Leave
adventure,
that's
the
other
part.
Can
you
see
that
alright
cool,
so
one
of
the
things
I've
been
thinking
a
lot
about
lately
is
basically
how
can
we
accelerate
the
PR
process,
especially
for
small
pr's?
A
lot
of
people
get
small
PRS
that,
are
that
add
a
lot
of
load,
but
mostly
because
of
the
flow
of
like
finding
it
opening
it
clicking
on
it.
G
So
this
is
basically
what
it
looks
like
I
can
go
over
here
to
login
I've,
actually
already
logged
into
github.
So
it's
just
going
to
do
the
OAuth
flow
and
you
won't
actually
see
the
github
login
page,
but
if
I
hadn't
already
logged
into
github,
it
would
go
through
the
get
up,
login
clock
page,
but
now
it
sees
that
it
knows
this
is
me
and
it's
actually
doing
some
dipping
in
the
background,
and
so
now
you
can
see
here.
I
have
this
dip
here.
G
G
G
Scroll
down
low,
so
it's
added
in
lgtm
and
release
note
none
in
from
using
the
github
api's,
and
so
this
point,
def
PR
is
lgtm.
It's
removed
from
here
and
I
can
move
on
down,
so
I
have
a
complete
list
here
of
you
know
small
changes
that
I
can
run
through,
and
you
know
this
one
looks
pretty
good
to
follow.
Prove
that
one
I
can
run
through
really
quickly.
It's
kind
of
like
my
goal
is
for
people
to.
G
You
know
how
to
be
a
five-minute
hand,
you
to
break
from
coding
I'm
just
going
to
run
through
an
lgtm,
a
bunch
of
both
PR.
They
don't
have
to
be
assigned
to
you
at
the
time
they
get
assigned
you
in
the
in
the
meantime,
when
you,
you
click
the
button,
so
that's
about
it.
I'm
going
to
work
with
the
submit
you
folks
to
get
it
up
onto
the
main,
submit
cube
site.
It's
ready
to
go
at
point,
and
so
hopefully
people
will
start
using
it.
It
works
right
now.
G
K
G
G
G
Crime
at
all-
and
you
want
Michelle-
do
you
owe
me
to
go
on
to
phase
two
of
what
I
want
to
talk
about
or
absolutely
def
want?
Let's
just
connect
over
there
as
I
phase.
Two
of
what
I
want
to
talk
about
is
the
results
of
the
community
survey
I
apologize
for
preventing
this
via
the
forms.
Interface
I
tried
to
like
put
it
into
a
pretty
PowerPoint,
but
you
have
to
go
through
a
spreadsheet
and
the
data
got
messed
up.
G
I
think
I'm
going
to
package
it
up
as
a
CSV,
let's
Jupiter
notebook,
so
that
anybody
wants
to
play
around
with
this
thing
can
use
Jupiter
2
like
it
out,
however,
I
feel
like
breaking
it
out
and
we'll
distribute
that
soccer
image
and
people
can
just
run
it,
but
to
start
out-
and
please
interrupt
it
anytime.
If
you
have
questions
I'm
going
to
run
through
this,
so
we
got
315
responses,
which
is
great.
G
G
40-Ish
percent
said
they
were
doubt
developers
and
a
few
of
the
other
rolled.
So
people
in
general,
who
are
answering
the
survey,
were
pretty
heavily
involved
in
the
community
if
a
pretty
even
split
between
people
who
have
been
involved
for
less
than
one
year,
people
who
involved
for
one
to
two
years.
That's
the
majority
of
people,
that's
not
a
surprise
and
then
about
twenty
percent
of
people
who
out
there
a
long
time,
members
of
the
community,
again,
sadly,
I,
haven't
broken
out
responses
based
on
time
in
the
community.
G
I
think
that
would
be
a
really
interesting
thing
to
look
at.
If
somebody
wants
to
do
the
analysis
or
eventually
I'll
get
there
as
well
again,
they
see
a
great
deal
of
engagement
from
people,
so
you
know
sixty
percent.
Sixty-Five
percent
of
people
have
asked
a
question
on
slack
or
stack
overflow.
Fifty
percent
of
people
have
answered
a
question,
so
that's
really
I
like
to
see
that,
because
it
means
people
are
not
just
asking
for
help,
but
they're
actually
helping
others
as
well.
I
think
that's
a
real
sign
of
a
healthy
community.
G
Lots
of
people
have
filed
or
commented
on
issues.
That's
also
not
a
shock
to
people
via
time.
You
know
and
we
have
a
lot
of
issues
and
then
you
know
people
have
participated
in
Game
two
burnetii
to
meet
ups,
as
well
as
a
very
high
percentage.
I
think
that
again
points
to
the
strength
of
the
community
that
we
have
on
now
getting
into
sort
of
the
more
substantive
data.
G
This
is
the
first
question
we
asked.
I
have
a
clear
understanding
of
where
the
communities
project
is
going.
I
would
say
that
this
is
largely
positive,
so
we
have
you
know
roughly
seventy-five
percent
of
people
that
have
some
level
of
agreement
between
we're
done
about
where
the
project
is
going.
I
think
it's
a
little
bit
problematic
that
you
know
twenty
five
percent
of
people
are
either
unsure
or
disagree
that
they
only
have
ten
percent
of
people
in
the
community.
Don't
know
where
the
project
is
going.
G
That,
probably,
is
something
that
we
need
to
work
on,
although
as
well
see
you
as
we
go
down,
there's
more
things
to
work
on
on
the
flip
side,
however,
it's
really
great
to
see
that,
basically,
everybody
is
either
staying
neutral
or
increasing
their
interest
and
enthusiasm
for
the
project.
So
that's
again
a
sign
that
we
are
we're
healthy
and
in
the
right
direction.
Most
everyone
is
either
staying
the
same
and
actually,
honestly
most
people
are
getting
more
excited
by
a
large
percentage.
G
G
Keep
rolling
this
is
the
beginning
of
what
I
would
I
think
is
maybe
a
little
bit
of
a
more
of
a
concern.
I
would
say
so.
Twenty
percent
of
coke
twenty-five
percent
of
folks
I,
are
in
neutral
or
negative
on
different
opinions
are
valued
and
listen
to
you
know,
I,
don't
think
you
know
this
can
never
be
perfect,
but
this
this
to
me,
I
would
like
to
food
like
to
see
the
different
opinions.
Grass
look
a
little
bit
more
like
the
enthusiasm
grab.
G
So
I
think
this
points
to
the
fact
that
sometimes
in
our
discourse,
we
don't
you
know
we're
not
always
as
even
as
we
could
be
as
we
go
forward.
There's
some
data
here,
I
haven't
had
a
chance
to
go
through
the
human
responses.
I
think
it's
important.
To
contrast,
the
difference
of
the
different
opinions
are
valued
and
listen
to
graph,
with
the
ideal
welcomes
grass
right,
so
I
think
this
actually
points
to
a
really
strong
community
of
people.
G
Welcoming
people
in
I'd,
say
ten
percent
neutral
I'd
still
like
to
see
that
a
little
bit
lower,
but
it's
pretty
good.
You
know
in
three
percent
of
people
who
don't
feel
welcome.
That's
not
that
doesn't
make
me
happy,
but
I
think
overall,
headed
in
the
right
direction
and
generally
pretty
good,
but
then
I
think
we
come
back
down
and
we
see
my
contributions
are
valued
in
the
communities
community
and
we
see
real
distinction
there
between.
G
You
know
effectively
everything
everyone
feels
welcome,
and
then
every
one
of
the
metrics
goes
down
for
the
contributions
being
valued
and
I
think
that
this
begins
speaks
to
a
sense
of
a
welcoming
community,
a
sense
of
an
exciting
community,
but
possibly
a
community
where
not
everybody
feels
like
they.
Their
contributions
are
welcomed
and
that
I
think
that's
a
problem
that
we
need
to
work
on,
and
then
we
get
to
the
really
challenging
ones.
G
I
think
which
is
I
understand
how
project
decisions
are
made
right,
and
so
here
good
in
the
sense
that
you
know
a
40.
Ish
percent
of
people
agree
that
at
some
level
that
they
may
understand
a
project
decisions
are
made,
but
on
almost
equal
percentage
of
people.
You
know
thirty
percent
of
people
disagree
that
they
understand
and
about
twenty
five
percent
are
neutral
and
I
think
this
is
a
question
where
we
shouldn't
have
people
who
are
uncertain
right.
G
We're
talking
a
lot
about
different
roles,
we're
not
necessarily
talking
as
much
about
how
people
make
decisions
I
think
we
should.
We
should
have
a
real
conversation
about
how
we
will
leave.
Canonically
decisions
should
be
made,
and
we
should
make
sure
that
we
followed
by
the
that
process
for
all
decisions
and
then
likewise,
I
understand
how
I
can
participate
in
the
communities
community.
G
G
I
think
these
two
graphs
together
really
reflect
the
bulk
of
the
work
that
we
need
to
do,
which
is
we
need
to
give
people
better,
more
clear
direction
about
how
we
make
decisions
and
about
how
they
can
participate
and
help
us
make
those
decisions
all
right
pause
there.
Any
questions
about
this
or
dogs
yeah.
G
H
Why
I've
been
begging
for
help
on
the
developer
Docs
and
we're
also
discussing
building
some
kind
of
FG
k
for
the
API
machinery
to
make
it
much
easier
to
get
started
in
building
something
new?
And
there
have
been
discussions
about
documenting
onboarding
guides
for
different
areas
of
the
project
by
dentists
or
whatever,
I
think
all
those
would
be
great.
G
I
think
it's
likely
in
it
also
where
we
should
see
if
we
can
maybe
lean
on,
because
I
think
these
are
also
projects
that
historically
have
been
hard
to
get
people
to
do.
And
so
maybe
this
is
the
place
where
the
CNCs
or
other
kinds
of
like
we
can
actually
vendor
this
out
right
and
as
a
as
a
task
for
someone
to
take
on
for
pay,
as
opposed
hoping
that
the
community
shows
yeah.
H
I
never
been
to
challenges
with
that.
One
is
I've,
had
a
huge
amount
of
trouble,
getting
people
to
be
able
to
make
progress
when
they're,
not
when
they
don't
actually
understand
the
community
and
up
in
the
house
is
already
this.
Actually,
since
the
problem
is
they're
not
documented
yeah,
and
the
second
is
that
so
far,
cntf
hasn't
offered
enough
money
to
get
over
the
ramp
up
time
required
for
a
vendor.
Yeah
okay
are
willing
to
pay
for
the
ramp
up
time,
but
not
for
doing
any
work
after
the
ramp
up
time.
Yeah
yeah,
yeah.
B
So
I
will
go
ahead
and
reach
out
and
try
to
find
a
anyway.
You
want
to
recommend
for
various
community
manager
process
work
within
our
community.
That
would
be
super
helpful
with
me
and
then
be
Yale
trying
to
make
everyone
to
get
more
or
onboarding
even
getting
started
before
we
get
rich
person.
Yeah.
B
G
B
Other
thing
that's
important
in
this
is
the
first
time
I've
done
the
survey.
So
this
is
our
baseline
and
I
would
bet
if
we
da
affiky
I'm
able
to
get
productive
humanities
developer
three
or
six
months
ago,
but
it
would
have
been
skewed
lower.
So
the
work
that
we've
been
doing
has
been
changing
english
and
I
would
love
to
see
this
again
in
three
months
or
six
months.
Yes,.
G
And
we
do
plan
on
doing
this
and
we
commit.
We
actually
also
collected
some
longitudinal
data
from
people
voluntarily.
We
can
actually
do
individual
correlations
across
time
as
well
as
the
aggregate
across
time,
and
that
will
signal
if
we're
moving
in
the
right
direction
and
then
the
last
piece
I'm
able
to
successfully
manage
applications
using
cure
benetti's.
This
is
just
a
clean,
win,
I
think
right.
G
So
ten
percent,
if
you
feel
five
percent
of
people,
six
percent
of
people
are
negative,
that's
I
mean
I,
think
that's
about
as
good
as
probably
you're
ever
going
to
do.
Unless
you
really
are
perfect,
six
percent
of
people
are
neutral
and
then
you
know
ninety
percent
of
people
say
they're
able
to
successfully
manage
applications.
I
think
this
speaks
a
lot
to
the
effort
that
we
made
in
making
this
thing
easier
to
use
and
the
product
as
a
whole,
and
likewise
so
interesting
statistic.
G
Most
of
you
are
not
using
a
managed
container
is
going
to
manage
community
solution
6040
and
then
likewise,
I'm
unable
to
effectively
manage
my
career
benetti's
cluster
is
similarly
positive.
It's
not
quite
as
positive
as
I
can
manage
my
apps,
which
I
think
speaks
a
little
bit
to
some
of
the
complexity
that
we're
still
trying
to
weigh
down.
But
I
think
this
is
again
like,
as
Sarah
said
like
if
we
had
asked
this
questions
six
months
ago.
I
doubt
it
would
look
grandeur.
G
Honestly,
I
think
that
if
a
book
is
going
to
be
people
to
play
around
with
them
and
retreat,
which
is
not
as
as
friendly
any
other
last
questions
I'm
going
to
try
and
also
put
this
together
into
a
blog
post,
and
so,
if
anybody's
interested
and
helping
do
the
data
analysis
for
that
blog
post.
Please
please,
please,
let
me
know
it
will
help
make
that
thing
a
lot
better
I'm
and
thank
you
to
everybody
who
who
took
the
time
to
fill
it
out
and
to
a
special
shout-out
to
speed.
G
C
A
G
G
C
C
We'll
continue
the
meeting,
and
let's
talk
about
the
week
of
coupon
and
the
week
after
so
we
decided
to
cancel
the
March
30th,
meaning
due
to
cook
on
and
clubbing
at
them,
and
the
question
now
is:
do
we
want
to
have
a
meeting
pls
week
after
tooth
con
again,
which
is
the
same
thing
that
we
did
after
the
Seattle
could
run?
We
have
me,
thought
yeah
I,
the.
A
A
C
Sounds
good
okay,
so
what
that
will
just
go
into
notices?
There
is
a
to
brandi's
day
on.
In
a
second
add,
the
openstack
stomach
and
Austin
csps
are
open
until
March
twentieth.
If
you're
interested
go
check
that
out
sophos
preschool,
please,
there
is
also
some
opportunities
for
international
travel
or
maybe
not
international
trouble
with
your
non-american.
C
Two
percent
at
CMC
fancy
a
sponsored
events
such
as
the
open
source
Senate
in
Tokyo,
which
is
May
31st
22
seconds
and
container
Karan
/
linux,
com+
clouds
open,
which
is
in
beijing
on
jun
19th
and
goes
till
June
twentieth
and
the
cfps
for
tenor,
open
till
March
18
reach
out
to
you
team.
If
you
have
any
content
for
either
of
those
and
there's
also
travel
finding
available
for
women
and
other
underrepresented
minority
speakers,
I
think
that's
it
for
the
agenda.
So
does
anybody
have
any
other
items
they'd
like
to
attack
that
analysis?
B
H
B
B
B
C
H
H
A
I
guess
I
have
one
quick
thing
just
because
I
don't
know
how
clearly
it's
being
communicated,
but
for
the
last
16
burn
down
meeting.
If
your
issue
or
pull
request
is
in
the
be
16
milestone,
it
is
considered
a
release.
Blocker,
that's
the
only
thing
we're
looking
at
we're,
not
looking
at
priority
labels
we're
not
looking
at
the
release.
A
Blocker
labels
we're
just
looking
at
whether
or
not
your
thing
is
in
the
be
16
miles,
though
it
or
not,
and
so
we're
going
to
start
to
get
a
little
more
vocal
about
whether
or
not
it
actually
belongs
from
the
people
in
six
miles
to
the
meeting
start
to
get
daily
next
week.
I
think
so,
just
attending
on
to
the
dance
update,
I.
H
A
I
A
That
they
are
currently
priority,
/
critical,
urgent
priorities,
/
important
soon,
but
there's
also
a
priority.
/
p0
priority
/
t
1
it's
kind
of
unclear
what
the
documented
process
refers
to
it's
unclear.
What
the
tooling
actually
pays
attention
to
so
since
we're
kind
of
in
flux
and
we're
just
sort
of
trying
to
simplify
we're,
just
going
to
look
at
work
in
be
16
or
not,
and
I
Rionda.
A
H
Certainly,
the
correct
thing
is
not
documented
in
the
tools
are
definitely
not
consistent
with
the
direction
that
we
want
to
go
I.
Think
at
the
end
of
the
release
cycle,
the
milestone
needs
to
necessarily
have
a
more
narrow
meaning
than
at
the
beginning
of
the
milestone
when
people
are
just
starting
to
work
on
stuff
and
they're,
not
sure,
what's
going
to
land
and
what's
not
at
this
point,
unless
it
really
needs
to
be
in
16,
it
doesn't
belong
in
a
milestone
anymore.
So
I
think
it's,
I
think,
the
puck
that
approach
me
Sookie
I,.
J
Will
say
that,
right
now
there
are
a
hundred
and
seventy
issues
in
the
milestone
with
no
owner,
and
so
it
seemed
unlikely
that
those
are
really
being
investigated,
which
is
like
a
signing
and
owner.
Now
would
be
why
and
if
we
can't
figure
out
an
owner,
we
need
to
figure
out
what
to
do
with
this
issue.
Yeah.
I
A
So
I
would
encourage
all
of
you
who
are
concerned
about
this
to
show
up
at
the
release
burn
down
meeting
tomorrow.
It
is
an
open
invitation
and
if
you
have
any
questions
about
where
to
find
this
invitation,
you're
welcome
to
ping
me
or
pink
ribbon,
Eddie
said
or
paying
when
perhaps
the
Cooper
Nettie's
milestone
burned
down.
Google
group,
because
that's
that's
the
policy
as
far
as
I've
heard.