►
From YouTube: Kubernetes Community Meeting 20160218
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
Kmachine demo, clusterops SIG formed, new k8s.io website preview. 1.2 update and planning 1.3
A
A
A
C
A
C
The
doctor
cookbook,
which
has
a
community's
chapter
with
some
help
from
Joe
beta,
wrote
that
and
skip
box.
We
have
three
main
drivers,
the
first
one,
which
was
the
first
idea
that
got
me
started
when
I
was
doing
poker
and
the
humanities
was
to
create
a
cumulative
toolbox
very
much
like
the
docker
toolbox.
C
The
second
driver
is
to
create
an
app
store
application,
because
I
don't
really
want
to
work
on
the
internal.
The
communities.
Lots
of
people
are
doing.
This
very
well.
I
really
want
to
focus
on
the
applications,
so
I'm
working
on
an
app
store
and
in
the
config
sig
in
you,
know
we're
working
with
DN
and
so
we'll
have
an
app
store
coming
up
and
then
a
life
cycle
solution
which
will
be
in
kind
of
a
given
based
solution.
C
Looking
at
apps
in
humanities,
but
today
here
you
know
we're
just
talking
about
the
toolbox
and
very
much.
The
idea
was
to
meet
the
doctor
users
where
they
are
so
dr.,
as
you
know,
of
course,
gotten
lots
of
people
to
use
it
and
dr.
package,
the
tool
box,
which
contains
the
doctor
engine,
the
document
Enoch
a
composed,
the
UI,
cosmetic
and
I
thought
hey.
Let's
do
the
same
thing
for
privileges,
pretty
much
the
same
tools
so
that
people
who
are
familiar
with
the
the
daughter
tools
they
can
easily
start
using
derivatives.
C
So
it's
it's
me
has
an
easy
on-ramp
to
preventive.
So
we
took
boot
to
docker
for
that
and
created
food
to
ks.
So
it's
virtualbox
iso
image
that
has
a
single
node
credited
deployment.
We
took
dhaka
machine
for
kid,
so
I
am
sorry
lots
of
fort,
but
it's
apache
license.
So
you
know
dr.
machine
it
and
created
k
machine
that
I'm
going
to
talk
about
dr.
Campos.
We
fought
lip
composed
the
go
version
of
dr.
C
Campos
and
created
composed
Kelsey
Hightower
had
written
composed
to
cue
it's
very
similar
but
integrated
in
a
talker
compose
full
mechanism
and
then
for
the
UI
docker
ask
agentic.
So
we
created
a
small
desktop
UI
based
on
NW
Jess,
which
is
the
our
skip
skip
box.
You
I
everything
is
open
source.
Of
course
it's
on
github
and
there
are
skip
box
organization.
You
can
find
the
boot
UK
as
the
Commission
the
compose
everything
we
got,
lots
of
other
things
on
there,
like
ansible
recipes,
terraform
plan,
a
built
on
Raspberry
Pi.
C
That
I
worked
on
several
months
ago
and
the
app
store
is
in
the
works
it's
in
there
right
now,
after
its
deployment
manager
and
helm
charts
arm
by
it
will
it
will
get
better.
So
you
know,
of
course,
check
them
out.
I
would
love
to
get
some
feedback.
That
would
be
terrific.
The
UI
looks
like
this:
it's
desktop-based,
so
it's
not
meant
the
replacement
to
the
dashboard.
There's
a
few
nice
things
like
integration
with
the
app
store
and
ability
to
use
multiple
endpoints,
create
these
endpoints,
ok
machine,
a
fork
of
dr.
C
machine,
as
I
said,
and
what
I
wanted
to
do
was
to
put
the
provisioning
of
humanities
inside
the
code.
So
you
get
a
single
binary
and
you
run
it.
We
could
have
done
it
differently
with
a
wrapper
on
the
Commission.
You
could
do
it
with
dr.
composed
and
there
are
lots
of
ways
to
do
this,
but
I
thought
that
using
dr.
Michelle
was
it
was
kind
of
kind
of
like
the
current
release
allows
you
to
use
q
manatees
1.12
I'm,
struggling
with
a
few
things
with
service
accounts
to
be
able
to
move
the
release.
C
The
problem
are
linked
to
the
doctor
ice
cube,
let
which
causes
problem
with
service
accounts
which
causes
problems
gns
important
things
like
this,
but
it's
almost
solved.
That's
the
good
news.
As
I
said
it's
a
single
node
communities
deployment.
It's
not
meant
to
be
a
cluster
deployment,
so
it's
really
easy
setup
single
instance
get
come
here
is
greatest
everything
is
dr.
based.
It's
really
the
single
note,
dr.
deployment
recipe
that
we
have
in
the
documentation
for
the
virtualbox
support.
C
The
couplet
runs
actually
as
a
service,
and
that's
why
right
now,
I
do
have
service
accounts
working
properly.
In
virtual
blocks,
hope
we
will
fix
that
so
that
it
will
work
for
all
the
other
cloud
providers.
Since
it's
a
fork
of
dr.
machine,
we
inherited
all
the
support
for
digital
ocean
in
AWS
and
all
the
the
cloud
provider,
so
it
just
worked
on
on
the
other
providers.
So
that's
my
contacts.
A
good
skip
box
at
set
go
of
course,
love
to
get
contribution,
feedback
issues.
Let
me
know
and
quick
demo.
C
C
It
returns
the
command,
k,
machine
and
fubar,
and
when
you
run
this,
if
your
family
doctor
machine
you
get
the
environmental
variable
to
set
up
the
doctor
and
for
what
we
added
was
also
some
commands
to
set
up
the
cutest
context.
So
if
you
exact
that
will
set
up
a
new
context
in
your
cube
control,
config
and
now
when
you
do
nodes
EP,
you
have
created
this
endpoint
on
digital
ocean,
exactly
the
same
way
that
you
use
the
Commission,
it's
very
nice
because
of
course
you
can
have
multiple
headphones.
C
C
But
you
get
ya,
you
get
the
note.
It
shows
up
as
localhost
we
may.
We
may
have
to
change,
except
if
I
use
the
pods
you'll
see
that
it's
AWS
now
I
put
the
name
here.
So
let
me
let
me
switch
to
the
virtualbox
one,
because
that's
that's
the
one.
That's
working
quite
well
and
managed
to
fix
that
today
the
proper
service
account.
C
So
if
you
you
end
up
with
a
joined
up
with
a
working
community
standpoint,
you
can
set
up
the
dns
at
on
and
also
putting
the
the
dashboard.
So
you
get
your
service
for
the
dashboard
and
then
you
know,
of
course
you
end
up.
If
I
find
my
chrome,
you
had
up
with
a
dashboard
working
on
your
virtual
box
IP
here
and
you
have
a
free
working
communities,
dashboard
running
in
your
chemistry,
node,
it's
quite
nice
because
it's
still
dr.
me,
it's
still
dr.
C
machine,
so
you
can
do
ssh
file
for
bathroom,
and
here
it
looks
like
it's
good
to
daughter
because
that's
how
we
build
boot
to
ks,
it's
good
to
docker
and
it's
all
dr.
bass.
So
if
you
go
dr.
PS,
you
get,
of
course
all
your
containers
from
your
dns
and
your
bash
board,
but
you
also
get
your
controller
manager,
your
API
server.
Everything
is
running
in
containers
with
the
hypercube
each
and
once
once
you're
done.
A
C
And
composed
is
even
better
composedly.
Could
you
take
a
doctor
compose
file
automatically
translated
in
communities,
objects
or
charts
for
help
or
deployments?
You
can
pick
and
any
any
targets.
Your
teammate
is
endpoint
automatically,
so
you
do
compose
up
and
it
takes
your
daughter,
compose
and
boom.
You
have
your
abilities
application
running
so.
D
Sebastian
long
term,
what
are
your
plans
for
this
in
terms
of
maintaining?
Are
you
going
to
take
the
fork
and
develop
it
independently?
Are
you
going
to
try
and
you
know,
I,
you
know
reapply
your
patches
and
sort
of
update
it
as,
as
you
know,
dr.
machine
moves
forward.
Do
you
dude,
like
are
you
just
using
dr.
machine,
is
sort
of
a
starting
point
with
sort
of
you
know,
ideas
on
and
where
you're
going
to
take
it
from
there.
C
Yeah,
that's
that's
a
good
question.
My
guess
is
that
if
we
were
to
try
to
send
the
Apaches
upstream
to
dr.
machine
autocar
Campos,
they
wouldn't
infect
them,
but
I'll
try
I'll,
reach
out
I'll
reach
out
to
them,
and
you
know
I'll
try
to
see
what
they
what
they
think,
though
I
doubt
that
they
will
take
them.
So
the
point
is
that
if
the
community
face
it's
interesting
and
that
we
get
some
type
of
critical
mass,
you
know
we
could
keep
maintaining
it.
C
You
know
if
it's.
If
its
use
and
I
also
addressed
the
K
machine,
I
mean
you
know:
people
know
how
to
create
a
community,
sent
it's
easy
for
to
get
started.
I
think
the
compose
is
more
interesting
as
a
as
a
way
to
move
from.
Somebody
who
has
worked
is
container
images
develop.
Your
QT
containers
that
are
linked
now
wants
a
real
applications
right.
E
So
Sebastian
an
alternative
to
upstream
all
this
into
doctor's
tools
would
be
to
up
often
to
refactor
doctors
home,
so
that
you
can.
We
give
all
the
parts
of
them
that
you
need
without
forking.
Oh
right,
if
you
repack
sure
all
the
bits
that
you
use
into
a
library
that
you
could
think
it
yeah
go,
do
another
weight
again
because
let's
go
where
the
Martin
I
deal
with
each
person
yeah
the
parts
of
this
to
just
create
bm's
and
different
providers
seems
likely
to
be
a
journal
before
novel
example.
E
C
Mean
what
well
yeah
what
I
didn't
mention
is
that,
because
it's
dr.
machine,
if
you
do,
if
you
do
dr.
PS
directly
from
your
desktop,
you
still
have
the
doctor
endpoint
properly
set
up.
So
you
get
the
benefit
of
book
and
same
thing
with
the
compol
that
we
worked
on
you
can
you
can
still
use
compose
as
a
as
a
pure
dr.
tool,
but
you
have
the
option
to
use
the
religious
hook,
someone
but
yeah
I'm
open
to
any
feedback
to
see
how
you
know
what
could
be
the
long-term
strategy
here
in
terms
of
maintainability.
A
A
Awesome
alright,
so
next
up
on
our
agenda
is
a
use
case.
So
does
did
anybody
want
to
talk
about
their
experiences?
Use
of
Coober
Nettie's
right
now,
I
didn't
have
anyone
scheduled
with
a
particular
use
case,
but
if
someone
has
something
they'd
like
to
discuss,
be
it
asking
for
help
or
just
sharing
what
you're
working
on
for
a
couple
of
minutes?
That
would
be
fine.
A
A
F
So
we
presented
a
demo
last
week,
fans
here
in
it
yeah,
so
we
guess
we're
looking
at
a
very
specific
use
case
with
cupones
namespaces.
We
were
wondering
if
the
community
could
help
first
wish.
You
are
thinking
about
a
net
worth
isolation
within
the
namespaces,
so
namespace
one
can
be
prevented
from
contacting
in
space
to
some
kind
of
network
isolation.
Is
it
possible
or
is
it
in
the
roadmap
for
the
coming
visions.
G
So
I
can
chime
in
here
miss
Casey
from
Project
calico.
The
network
sig
has
been
talking
about
this
a
lot
for
the
past
couple
months
and
we
are
currently
just
kind
trying
to
tie
down
a
proposal
that
would
allow
this
and
it'll
be
kind
of
in
the
first
stage
is
implemented
using
API
extensions
like
third-party
resources.
But
yes,
this,
you
should
be
able
to
do
this
soon.
G
A
A
A
H
Okay
and
we're
scheduled
to
kick
off
I
wasn't
ready
to
coordinate
it
earlier
in
the
week,
so
I
scheduled
it
for
friday,
as
the
kickoff
meeting
and
I
sort
of
and
people
are
welcome
to
make
other
suggestions.
I
sort
of
thought
of
this
not
quite
as
a
full
happy
hour
meeting
but
friday
afternoon,
so
my
thought
is
to
collect
stories
at
the
end
of
the
week,
cliff
recommend
cluster
ups
and
then
so.
H
H
I
want
to
reinforce
one
thing
that
I'm
really
trying
to
accomplish
and
I'm
hoping
people
help
recruit
for
is
I
really
like
to
see
cluster
ops
be
a
place
where
operators
can
collect
in
you
know
in
the
OpenStack
world
that
we
did
this
ad
hoc
and
I'd
like
to
be
a
little
bit
more
controlled,
which
means
pull
the
operators
together,
give
them
a
place
to
compare
notes
and
actually
have
give
them
an
identity
and
a
voice
so
part
of
the
gophers.
For
cluster
ops
is
to
actually
sell
right
if
you're.
H
You
know
here's
a
place
where
you
can
share
stories
and
sorry,
I'm
not
sure
how
to
do
this
yet.
But
I
want
to
offer
that
if
somebody
has
a
an
environment
where
they
don't
feel
like,
they
can
share
the
details
of
that
environment.
It's
the
corporate
environment,
they
don't
have
permission
to
talk
about
it,
we'll
figure
out
some
way
to
anonymize
people
during
and
during
a
presentation.
So
they
can
say
all
right.
You
know
I
work
for
mumbled
and
you
know
we
have
mumble
servers
running
goober
Nettie's
and
you
will
figure
that
out.
H
A
H
H
A
So
I
don't
know
if
not
Baldwin
is
on
the
call
he's
been
doing
a
lot
of
work
with
Cooper
Nettie's
meetups,
at
least
in
specifically
in
San
Francisco
Seattle
in
New,
York
and
I.
Think
he's
also
participating
in
some
of
the
German
ones,
but
he
is
also
very
focused
on
user
experiences,
user
stories
and
Cuban
Eddie's
user
feedback
and
ways
to
engage
that
community.
So
if
he
isn't
part
of
your
outreach,
he
should
be
and.
A
Are
Matt
Baldwin
from
stack
point
cloud,
excellent?
Actually,
those
three
words
could
be
in
any
order
in
his
company
name.
It
could
be
like
that
point
chart
yeah,
but
all
three
of
them
are
in
there,
but
you
can
find
him
and
I'm
not
sure.
If
he's
I
don't
think
he's
on
the
collar,
he
would
have
jumped
up
and
said,
hey
I'm
here.
Let
me
speak
for
myself
by
now.
Well,.
H
H
A
Worried
about
time
zones
is
an
interesting
one
for
this
meeting,
so
I'm
gonna
now
jump
into
that,
because
I
don't
think
we
have
another
cig.
That
is
written
report
out
unless
somebody
wants
to
quick
write
their
name
in
the
agenda,
but
this
meeting
works
okay
for
Europe
dandy
for
Pacific
us
fine
for
the
East
Coast
us
but
terribly
for
Asia.
So
one
of
the
things
we
had
discussed
was
was
moving
at
least
one
a
month
to
a
different
time
slot.
A
So
I
will
come
up
with
I
recommended
what's
a
month,
that
we
do
it
at
least
late,
at
least
in
a
time
zone
four
or
an
Asia
friendly
time
zone.
My
team
here
actually
is
lit
across
the
world
and
we
alternate
our
weekly
meetings.
But
let's
start
with
maybe
one
a
month
and
we'll
try
that
for
a
bit
and
see
if
how
that
cadence
works,
but
I'll
make
sure
that
I
publish
very
clearly
that
we're
doing
in
Asia
friendly
time
this
week
or
euro
friendly
time
this
week.
Awesome
that
immigrated
yeah.
A
A
But
it
five
or
six
specific
is,
then
you
know
eight
or
nine
p.m.
eastern
time
so
and
in
europe
is
5
or
6
p.m.
pacific
is
middle
of
the
night
for
europe.
So
so
we'll
just
see
we'll
try
it.
You
know,
give
it
a
shot
and
see
what
sort
of
engagement
we
get,
but
I'll
pick
a
date
and
I'll
put
it
in
the
sand
and
try
and
try
to
get
us
to
do
one
of
them
in
an
asian
friendly
time
status
at
least
a
test.
A
A
A
A
A
J
J
This
there's
this
is
a
work
in
progress.
This
is
the
very
first
sort
of
doc,
complete
version
of
the
site,
I'm
working
with
a
company
called
United
creations
to
create
the
assets
for
this,
but
basically
you're.
Looking
at
what
we're
thinking,
the
next
version
of
the
docs
is
going
to
look
like
the
pocs
are
grouped
as
opposed
to
one
long
toc
like
we
had
before,
and
what's
currently
up
on,
Qumran
I
thought
I.
Oh
right
now
we
group
them
into
guides
reference
samples
and
support.
Some
reference.
J
Samples
are
all
the
various
places
that
we
have
stashed,
canonical
examples
of
how
to
do
things
with
Cooper
Nettie's
support,
pretty
obvious
troubleshooting
reaching
out
to
the
community,
and,
but
you
know,
you'll
probably
spend
a
lot
of
time
in
guides
where
we
explain
how
to
use
stuff
going
to
reference
when
you're
deep
within
using
a
particular
API
or
tool.
There's
a
lot
of
CSS
problems
right
now,
because
this
is
all
being
imported
from
the
old
site
and
stood
up
with
the
new
design.
So
bear
with
me
on
that.
J
J
That's
kind
of
what
the
site
visually
feels
like
right
now:
there's
not
any
marketing
content
up
outside
of
the
docks,
but
things
get
really
exciting.
Oh
here
I
like
this
tool.
I
wish
this
page
had
better
CFS
and
that
pre
fills
out
a
github
issue
for
us
right.
So
you
can.
Let
us
know
what's
going
on
so
right
now,
this
site
is
available
as
a
pure
get
up
pages.
Repo.
J
J
J
So
that's
an
important
change
for
everyone
to
know
is
that
no
longer
is
the
docs
repo
are
the
docs
were
piled
like
source
of
truth,
a
subfolder
in
the
main
communities
repo.
So
if
I
add
a
little
note
here,
hi
everyone
to
the
landing
page
with
dots,
then
when
we
get
to
church
zooms
black
blocking
my
screen
right
now,
so
excuse
me
area.
J
We
get
to
this
whenever
it's
done
standing
up,
sometimes
just
like
30
seconds
to
build,
and
then
basically
you
see
the
changes
instantly
and
your
fork
at
this
URL,
which
is
pretty
awesome
and
I,
can
do
the
same
thing.
It
works
the
same
locally.
So
while
that's
thinking,
let
me
go
ahead
and
clone
the
repo.
A
A
J
J
So
this
is
my
local
machine,
as
you
can
see
that
none
of
this
existed
a
second
ago
I,
just
cloned
it
and
ran
Jekyll,
sir,
which
is
an
open-source
thing
and
all
it
takes
few
minutes
to
set
up-
and
here
I
am
on
my
local
machine-
it
runs
exactly
like
it
does
live,
and
if
I
make
a
change,
it
should
show
up
pretty
dang
instantly.
I
have
a
snappy
markdown,
editor
called
mouth
or
MOU.
However,
this
pronounced
hi
everyone
hi
dr.
J
J
Looking
at
your
for
kincaid
OBO
or
looking
at
your
local
clone,
it's
a
period
of
pages
project,
a
lot
of
things
we
used
to
do
with
scripts
of
now
being
done
by
native
Jekyll
capabilities,
for
example
the
toc
s,
which
used
to
be
munched
in
our
actually
generated
by
simple
yanil
files.
Here
I'll,
I
guess
I
could
let
dreamweaver
open
that.
But
that's
kind
of
heroic.
A
J
So
I'm
gonna
be
working
with
a
team.
This
is
how
the
TLC
is
laid
out
by
the
HTML
file
used
to
be
a
bunch
of
allies
and
ul's
that
were
created
from
script.
Now.
All
you
do
is
edit
this
I'm
getting
over
to
generated
docks
the
right
now
I'm
punting,
but
what
we'd
like
to
do
is
and
punting
looks
like
this
basically
link
over
to
to
generate
a
dockside
get
up.
J
Don't
see
any
questions
in
chat
yeah,
so
if
you
want
to
be
intrepid,
you
can
fork
this
circle
on
this
and
have
a
look
at
it
down
start
doing
it
work
well
once
again,
probably
not
going
to
accept
your
pull
request.
So
that's
a
super
benign,
but
it's
going
to
be
much
much
simpler.
Those
who
have
tried
to
edit
the
dockside
I'm
sorry
I
swear
I'm,
making
it
as
easy
as
possible.
Thanks,
hey
John,
oh
yeah,.
J
F
J
Know
what
actually
they
did
stand
that
up?
If
want
to
see
that
if
you
got
a
cube,
dot,
United
creations,
dot
XY
see
they
did
stand
up
the
homepage,
it's
a
little
huge
I,
find
it
good
sort
of
zoomed
out
at
seventy-five
percent.
That's
just
the
way
it
looked
coming
out
of
their
photo
shops.
They
said
they're
working
on
it.
Oh
I'm,
not
getting
the
graphics
right
now.
G
J
J
H
A
K
K
That
schedule
had
us
branching
tomorrow
from
head
into
a
1.2
branch
reopening
ahead
to
allow
any
feature,
three
factors:
major
major
code
edits
and
then
spending
the
next
two
weeks,
ish
burning
down
the
final
bugs
in
the
1.2
milestone
and
then
releasing
that
second
week
of
march,
which
is
also
the
cube
con
ieu
conference.
So
that
aligns
nicely.
I
spent
the
last
couple
days
kind
of
looking
over.
A
K
Counter
folks,
we've
got
the
issues
and
in
certain
milestones
it
seems
like
we're
that
I
probably
not
as
super
shock
since
we
split
a
feature
complete
out
a
little
bit
so
just
as
an
overview
like
the
v
1.2
milestone
has
135
issues
and
80
of
those
or
p
0
or
p
1.
So
that
tells
me
we
have
at
least
those
80
things
that
we
know
we
need
to
finish
off
and
then
there's
another
70
or
so
in
the
feet.
K
1.2
candidate,
milestone
that
are
sort
of
pending
a
triage
on
people,
making
a
call
on
how
important
it
is,
etc.
That
said,
there
are
36
PRS
in
the
beat
1.2
mile
stone
and
the
submit
q
looks
to
be
about
40
items.
Deep,
so
I
think
there's
a
lot
of
throughput
happening
this
week,
just
on
bug,
fixes
I
guess.
So.
K
The
question
is:
when
do
we
branch
and
in
the
trade-off,
as
always,
is
if
you
branch
early,
you
have
a
lot
more
cherry,
picks
of
the
bugs
and
keeping
the
two
branches
in
sync
and
if
you
branch
late,
it's
delaying
the
amount
of
time
where
we
can
open
up
head
to
larger
features
and
1.3
era
stuff.
So
that's
basically
the
trade-off.
K
You
know
looking
at
how
things
went
for
1.0
or
1.1.
It
sounds
like
it's
probably
a
little
early
to
branch
tomorrow
on.
If
we
have
a
triple
digit
number
of
issues,
we
think
we
need
to
fix,
but
that
is
absolutely
up
for
for
discussion,
see
what
people
think,
but
I
would
think
we'd
wanted
to
lay
the
branch
by
on
the
order
of
a
week.
But
again
that's
going
to
depend
on
how
the
burn
down
goes
and
it's
hard
to
predict
how
many
thorny
issues
will
get
chicken
out
the
last
couple
weeks
of
a
milestone.
L
K
K
Yeah
so
I
mean
we
have
everything
is
in
the
milestones,
so
anything
in
the
v
1.2
milestone
or
the
v
1.2
dash
candidate
milestones
are
things
that
the
project
could
totally
use.
Help
on
in
general,
people
keep
the
assignee
field
relatively
clean,
so
anything
on
a
sign
with
definitely
difference
pushing
the
milestone
forward.
If
something
is
assigned
but
hasn't
seen,
movement
in
you
know
call
it
a
week.
It's
probably
an.
K
E
A
E
M
E
E
E
Rates
pretty
great
yeah,
so
I,
nothing
else
really
stands
out.
I
mean,
like
TJ,
said,
look
for
things
that
are
on
a
sign
or
things
that
don't
seem
to
have
activity
and
ask
what
you
can
do
to
help.
Another
thing
you
can
do
to
help
is
try
out
some
of
the
new
features
we
have
lots
of.
New
API
is
going
to
beta
V
1.
E
L
I
guess
I
didn't
actually
hear
an
answer
about
how
long
we
as
a
community
are
comfortable
deferring
the
decision
to
branch,
and
it
sounds
like
at
the
very
minimum,
we're
kind
of
expecting
a
lot
of
people
too
send
upon
issues
and
ping
people
asking
if
that's
really
important
right.
That's
that's
the
that's!
The
takeaway
I
heard
not
a
decision
on
whether
or
not.
A
H
So
I
guess
I
guess
the
question
I
would
ask
is:
are
we
doing
effectively?
Would
you
consider
that
week
by
week
slips
or
if,
in
the
end
of
who
you're
saying
that
I
would
just
say,
push
it
two
weeks
we
are
slipping
day
by
day,
apparently,
okay,
I,
don't
just
don't
know
that
community
sentiment
about
that
type
of
communication
and.
H
E
E
Jumping
in
to
help
now
is,
can
be
somewhat
difficult
for
some
of
these
things
for
people
who
are
unfamiliar
with
the
code
and
the
status.
But
you
know
we're
trying
to
put
together
a
coherent
picture
of
where
we
are
across
the
whole
object
and
all
the
features,
and
you
know,
as
we
develop
a
better
understanding
of
that.
We
will
definitely
share
that
with
the
community.
A
L
A
L
Guy
would
make
as
a
member
of
the
community
as
it's
been
about
16
days
since
I've,
seen
a
1
dot,
2
alpha,
release,
get
cut
and
I'm,
not
sure.
If
that's
because
there's
some
there's
been
some
trend
going
on,
but
I
think
I'm
having
another
build
on
like
having
another
release
on
the
github
page
sometime
soonish
would
contribute
some
confidence
to
velocity
here.
That's.
E
E
Yeah
I
mean
these
kinds
of
things
you
know
are.
The
responsibility
is
borne
by
a
very
small
number
of
people
so,
depending
on
whether
those
people
are
able
to
do
it
or
whether
the
head
is
stable
or
not,
can
materially
impact,
whether
release
happens
or
not
like
in
some
cases.
In
the
past,
there's
literally
only
been
one
or
two
people
who
are
able
to
build
a
release,
and
you
know
that
definitely
needs
to
change
if
we're
going
to
get
more
consistently
sure.
L
I
guess
I'm
just
sort
of
illustrating
that
there
it
seems
like
there
used
to
be
relatively
weekly
releases
to
give
us
some
kind
of
cadence
about
like
without
having
built
everything.
What's
the
state
of
1.2
today,
if
you're
a
wider
pool
of
beta
testers
for
sort
of
release
candidate
type
of
stuff,
and
if
we're
trying
to
move
towards
that
phase,
it's
just
unclear
to
me
why
we've
sort
of
slowed
down
on
those
our.
K
Plan
cadences
every
two
weeks
and
so
I
haven't
actually
looked
at
the
alpha
releases
to
see
how
close
we've
been,
but
we're
trying
to
get
a
release
out
every
two
weeks
and
then
the
goal
was
to
one
sweet
branch
release
on
that
new
branch
and
call
it
beta,
which
you
know
in
a
perfect
world,
would
have
been
tomorrow.
Although
it
looks
like
we'll
miss
that,
and
so
that's
why
there
hasn't
been
an
alpha
this
week.
N
A
K
Google
internally
has
been
looking
at
what
they
want
to
do
for
1.3
and
it
looks
like
we
would
be
ready
to
present
sort
of
our
plans
for
what
we're
going
to
contribute
to
March.
Third,
that's
a
that's
a
thursday!
That's
a
community
meeting
day,
so
that's
sort
of
an
initial
spot
where
we
could
be
able
to
present
our
thoughts
and
I
wanted
to
see.
If
that
aligns
with
anyone,
elses
timeline
or
you
know
how
community
feels
would.
A
N
O
O
These
are
just
the
things
that
we
as
Google
would
like
to
see
in
the
product
and
that
we
are
assigning
people
to
work
on
and
thereby
we
can
make
some
form
of
or
have
some
form
of
certainty
or
some
level
of
certainty
about
what
will
actually
here
in
13,
because
we
know
that
people
who
are
going
to
work
on
it
and
they're
going
to
be
committed.
This
is
not
product
planning
for
the
entire
product,
as
I
said.
You
know.
O
We
very
much
want
this
to
be
a
community
effort
and
if
you
say
well,
we
you
know
somebody.
The
committee
says:
hey,
there's
this
great
feature:
I'd
like
it
to
be
in
13,
I'm
willing
to
work
on
it
and
the
team
feels
like
hey.
That's
actually
a
great
direction,
we'd
love
to
do
it
then
so
be
it.
It
is
in
13.
O
A
E
I
think
that
will
help
get
people
involved
early
in
participating
as
well.
If
the
other
people
see
that
some
feature
is
going
to
be
under
development
than
making
join
in
that
effort
earlier,
rather
than
later,
which
is
necessary
in
order
for
them
to
be
able
to
contribute
effect,
we
also
to
help
us
plan
how
much
time
we
have
to
spend
on
reviews
for
different
areas,
which
consumes
basically
all
my
time
and
a
lot
of
the
time
of
other
people
on
the
team
as
well.
E
A
My
question
about:
did
you
did
you?
The
community
need
the
Google
list.
First
was
were
planning
to
bring
it
to
the
community
meeting
on
March.
Third,
is
that
a
day
do
you
do
you
all
want
to
target
March,
third
or
march
10th,
to
bring
your
lists
and
then
we
can
pull
together
in
some
sort
of
synthesis
and
have
a
longer
discussion
on
either
the
10th
or
the
17th.
A
A
O
A
Well,
we
are
out
of
home.
Would
you
pick
this
up
war
unless
somebody
has
burning
desire
to
send
to
tell
us
more
all
right?
Apologies
if
I
cut
someone
off
one
two
things
of
note:
google
Summer
of
Code
participation
if
we
as
a
cooper,
Nettie's,
project,
community,
etc,
want
to
be
considered
for
google
Summer
of
Code.
We
need
to
know
who
mentors
are
and
we
need
to
know
today
tomorrow,
at
the
latest,
I
sent
a
note
to
the
dead
list.