►
From YouTube: Kubernetes Community Meeting 20161020
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
Demo: Kubernetes community gamification port; Release 1.4.3; Release 1.5; PetSet rename; Kubecon
A
Good
morning,
everyone
or
good
local
time
to
you,
it
is
Thursday
October
20th,
and
it
is
three
weeks
from
Kubek
on
which
is
a
terrifying
thought
and
also
an
awesome
thought,
because
we'll
get
to
see
all
of
you
in
Seattle.
So
this
morning
we
have
a
demo
from
the
team
and
a
president
who
has
been
building
a
advocacy
tool,
and
I
will
let
Ryan
tell
us
more
about
the
adventure
of
tracking
contributions
to
key
pernetti's,
a.
B
B
Excellent
well,
hello,
everybody
I
appreciate
the
opportunity
to
talk
with
everyone
today.
My
name
is
Ryan
Quackenbush
and
I
run
an
internal
community
and
advocacy
program
at
a
friend
of
now.
I
want
to
spend
the
majority
of
my
time,
showing
you
what
we've
done
and
not
stepping
through
slides,
but
I
need
to
set
a
bit
of
context.
First,
our
intention
going
into
this
is
to
help
drive
this
initiative
in
the
community,
and
it's
really
all
about
helping
to,
as
the
slide
says,
cultivate
and
engage
community
of
cumin
ASAP,
it's
through
gamification
and
rewards.
B
B
Additionally,
you'll
also
earn
performance-related
badges
now
beyond
the
challenges
that
get
posted
regularly.
Community
members
will
also
be
recognized
and
compiled
points
for
the
things
that
they're
already
doing
today
and
what
I
mean
by
that
is
that,
most
importantly,
we
built
out
a
full
integration
with
github.
This
means
that
there's
no
new
account
to
create
and
no
changes
need
to
be
made
in
your
day-to-day.
In
order
for
you
to
be
recognized
for
what
you're
already
contributing
it
get
up,
this
integration
will
enable
us
to
automatically
recognize
various
activities
that
users
are
doing
and
assign
points.
B
Now,
before
we
walk
you
through
the
actual
demo,
I'd
like
to
point
out
that
there's
a
number
of
challenges
already
created
in
the
sandbox
environment
and
these
mimic,
those
that
are
going
to
be
followed
in
the
actual
hub
itself,
actually
they're
identical.
The
points
that
we've
assigned
to
all
the
various
activities
are
completely
arbitrary
at
the
moment.
So
this
is
an
area
that
we're
hoping
all
of
you
can
provide
a
little
bit
of
input
to
specifically
on
what
you
feel
is
most
important
to
the
community
to
incentivize
and
deserving
of
more
recognition.
A
B
True,
that's
true
thank
you,
but
what
would
that
said?
Let
me
show
you
what
the
hub
is.
So
what
you're
seeing
here
is
me
pretending
that
I'm,
a
new
advocate?
What
you
see
is
what
the
new
advocates
will
see,
with
the
exception
of
the
branding
up
top
speaking
of
needing
help.
This
is
an
area
that
will
work
with
others
in
the
communities
about
branding
and
logo
and
this
octa
cat.
So
we're
going
to
click
this.
B
This
brings
us
right
to
get
up
we're
going
to
authorize
this
application
and,
as
you
can
see,
the
permission
is
limited
to
public
data
only
and
we're
going
to
authorize
that
and
that
will
redirect
us
back
to
the
fort
and
will
create
a
quick
backup
password
for
this
click.
Next
fields
are
invalid.
Oh
wait,
my
name,
my
name
is
kid
icarus
and
my
password
and
my
email
is
bake.
Cakes
for
@
yahoo.com,.
B
Okay,
click
next,
we'll
save
that
password
and
welcome
to
the
case
force.
Now
it's
going
to
ask
me
to
really
quickly
configure
my
profile:
I
am
jumping
arrow
Oh,
shooting
hero,
my
company's
NES
and
we're
going
to
continue
profile
updated
now.
This
here
is
the
final
step.
This
is
the
first
challenge
to
make
sure
that
you
get
credit
for
linking
up
across
your
github
account,
so
we
go
here.
Basically,
this
just
asks
us
to
create
our.
B
Put
in
our
github
user
name
and
our
stack
overflow,
user
name
and
no
problem
here
are
my
creds
and
we
get
the
points
for
completing
the
challenge
and
it
says:
hey.
You
have
a
bunch
of
new
challenges
that
you
can
see
now
and
there
we
go
now
in
order
to
fully
test
the
work
we
did.
I
created
a
shell
repository
at
github
and
essentially
cemented
this
sandbox
environment
to
it,
and
that
gave
me
control
over
green
lighting.
All
the
activities
are
rather
than
having
it
wired
up
to
the
Guru
nineties
project.
B
So
now
here
are
a
number
of
different
challenges.
That
populated
just
to
give
you
a
quick
idea
of
what
they
can
expect.
The
sea
advocates
will
receive
weekly
or
bi-weekly
challenge,
digesting
their
emails,
inviting
them
into
the
hub.
But
regardless
of
whether
or
not
they
respond
to
the
emails
they're
going
to
continue
to
get
automated
points,
we
get
up.
So
let's
go
down.
Take
a
look
at
this.
Follow
Friday
Josh,
for
example,
is
a
challenge.
I
can
exist.
You
know
every
Friday.
B
It
invites
different
candidates
to
go
ahead
and
follow
different
members
of
the
crew
Bernie's
community.
In
this
case,
I
have
highlighted
Sarah
and
if
we
want
to
say
somebody
came
out
with
the
cool
demo
that
we
want
to
show
off,
we
can
go
ahead
and
post
one
of
their
demos
in
this
invite
the
advocates
to
go
directly
to
it.
B
Watch
it
on
YouTube,
possibly
leave
a
comment
if
you
liked
it
so
on
and
so
forth,
if
somebody's
very
active
within
the
hub
itself,
we
of
course
can
recognize
that
now,
whether
that's
recognize
them
for
the
total
points
over
the
past
30
days,
maybe
they've,
you
know
issued
a
bunch
of
different
commits
or
poll
request.
However,
we
decide
we
want
to
incentivize
that
we
can,
and
then
we
can
Chris
fix
review
here
here
you
go
if
they
have
any
recent
content,
we
want
to
link
to
make
it
and
redirect
at
a.
B
We
can
turn
this
into
a
multi-stage
challenge
and
have
it
redirect
back
to
their
video
blog.
What
have
you
so
on
and
so
forth?
If
we
want
to
share
it
on
social
able
to
have
to
do
that
as
well
and,
let's
say
somebody's
done,
some
really
cool
stuff
outside
of
this
hub.
Well,
we
can
go
ahead
and
recognize
them
here
as
well.
So
let's
say
somebody
went
on
Twitter
and
highlighted
the
fact
that
slack
as
well
over
8,000
members
and
for
the
community-
and
they
use
a
cool
gift
to
do
so.
B
B
I
think
the
the
the
percentage
of
answered
questions
for
KU
burnett
is
somewhere
in
the
40,
so
we
could
use
this
possibly
as
a
tool
to
maybe
push
up
that
percentage
somewhat,
and
I'd
like
to
also
point
out
that
this
gentleman
here,
whose
picture
you
see,
Jason
software,
engineered
a
friend
of,
doesn't
participate
a
ton
and
the
internal
advocacy
program
that
we
have
here.
But
he
got
the
automated
email
that
I
mentioned
a
few
minutes
ago
and
came
back
into
the
sandbox
environment
and
answered
a
budget
of
the
least
a
couple
questions.
B
So
I
thought
that
was
pretty
cool
and
now
I
kind
of
want
to
show
you
what
the
auto
racket
automatic
recognition
for
what
you're
doing
looks
like.
So
this
is
the
github
repo
test
environment
that
I
created
and,
as
you
can
see,
Austin
Parker,
who
is
a
software
developer
here
42
minutes
ago,
I
put
in
a
full
request
that
I
accepted
as
a
coach
commit.
So
if
I
bring
you-
and
he
also
did
so
completely
independent
of
the
hub
I-
think
that's
important.
B
So
then,
if
I
go
behind
the
scenes
as
an
administrator
and
see
all
the
individual
users
and
contributions,
we
will
see
Austin
41
minutes
ago
created
this
new
commit
it
got
points
for
it.
This
is
being
recognized
and
rewarded
with
an
arbitrary
number
of
points,
of
course,
and
it's
automatic
from
github
and
rewards
in
this
program
a
sport.
B
So,
in
short,
we
r
directly
engaging
the
community
through
challenges
in
highlighting
the
work
is
being
done
amongst
its
members
with
gamification
and
a
simple
performance
based
system
now
through
github
authorization,
we're
recognizing
contributions
automatically,
meaning
that
its
members
won't
have
to
create
new
accounts
and
with
that
being
said,
I'd
like
to
open
this
up
to
any
feedback.
You
guys
have
we're
really
excited
about
what
we
have
in
place
today
and
have
planned
to
bring
out
to
the
community
use
and
hope
that
you're
as
excited
by
what
you
see
is.
B
We
were
to
show
it
to
you.
So
we've
been
working
on
this
for
about
the
past
month
and
a
half
and
so
on
a
really
it'll
pump
to
get
it
out.
So
my
contact
info
is
listed
below
right
here.
Please
don't
hesitate
to
reach
out
to
me
directly
and
Sarah.
Thank
you
for
inviting
me
present
today
and
I'd
like
to
spend
the
next
few
minutes,
opening
up
to
the
floor
for
feedback
and
questions.
B
A
A
A
So
the
bottom
of
screen
is
chat,
but
I
can
read
some
of
them.
Slack.
Integration
was
one
of
the
first
suggestions,
because
so
much
of
the
conversation
happened
on
slack.
We
have
requests
to
to
redeem
points
for
Bitcoin,
which
may
be
a
little
bit
harder,
but
we
could
totally
talk
about
Google
cloud
platform
credits
there's
and
we
have
lots
of
getting
ideas
for
for
rewards
as
well
as
what
activities
we
want
to
reward.
Most
highly
Mike
suggested
that
we
give
credits
for
reviews
more
highly,
because
we
want
to
incentivize
people
to
do
more.
A
C
A
Mad,
that's
a
really
interesting
question
because
there
are,
there
are
two
possible
places
for
that.
One
would
be
contributor
working
group
contributed
working
group
and
then
there's
also
been
some
discussion
about
a
meta
sig
about
community,
and
maybe
this
is
a
thing
that
starts
that
sig
being
moved
on,
but
I
would
have
us,
go
through
the
same
proposal
process
to
to
propose
a
sink
community
totally.
D
Makes
sense,
yeah,
I
work
out
a
couple
suggests
the
contributor
experience
working
group
for
now
there's
plenty
of
space
in
that
working
group
to
discuss
this
and
it's
very
aligned
with
the
goals
of
that
working
group.
I
think
this
looks
awesome.
They're
still
going
to
be
said.
You
know,
we've
also
been
talking
about
Patricia
dashboards
and
the
need
to
get
more
data
to
monitor
how
well
review
about
review
load
is
balanced
and
things
like
that
so
I
think
discussing
all
that
together
would
be
useful.
It.
C
A
All
right
anybody
else
have
things
or
do
we
just
want
to
say
thank
you
and
a
huge
round
of
kudos
to
ride
and
Ryan
in
the
team
at
a
frienda.
For
all
this
work,
all
right
we'll
go
the
round
the
younger
out
of
kudos.
Many
points
to
Ryan
went
into
the
chat.
If
you
haven't
found
the
chat,
there
are
many
points
waiting
for
you
there.
Oh
look.
A
D
Specifically
on
annotations,
so
we've
been
using
annotations
for
as
a
way
to
add
experimental
fields
effectively
to
more
mature
API.
So
two
beta
or
ga
ap
is
so
that
that
would
still
allow
for
changes
in
the
representation
of
the
field
or
potentially
been
nuking.
The
features
completely
if
they
didn't
work
out
much
like
bursting
for
whole
api's,
the
there
been
a
number
of
problems
with
the
indications
and
moving
between
alpha
beta
and
GA.
D
You
know
it
as
NGA.
The
features
are
just
represented
as
fields,
but
did
the
annotations
don't
work
very
well
with
conversion
logic
and
representing
the
same
field
effectively
the
same
information
in
multiple
different
places
and
the
same
resource
basically
cannot
possibly
work
ever
so
so
that
we
came
up
with
a
sort
of
a
long-term
proposal
and
discuss
short-term
options
and,
in
the
short
term
not
much
is
changing
from
from
what
we
do
currently
just
because
there's
not
enough
time
in
the
1.5
time
frame
to
do
much
so
anything
being
added
is
alpha.
D
We're
still
recommending
the
use
of
annotations
for
now
and
things
moving
from
alpha
to
beta,
where
possible,
we
sort
of
depends
on
who
the
consumer
of
the
annotation
is.
You
know.
One
thing
we've
done
in
the
past
is
just
half
the
consumer
accept
both
alpha
and
beta
annotations
and
not
actually
convert
automatically
alpha
to
beta
I.
Think
we're
staying
with
that
same
recommendation
for
now
as
well,
some
things
since
alpha
technically,
we
said
we
could
break
compatibility.
Some
things
may
just
get
me
named
alpha
to
beta
with
no
you
know.
D
So
I
also
would
just
stop
stop
working
thought.
There's
an
issue
for
the
discussing
the
longer
term
design.
The
TLDR
of
that
is,
will
create
a
lighter
weight
mechanism
to
produce
new
API
versions.
So
that
way
we
can
leverage
the
full
API
machinery
to
do
the
conversion
between
different
guy
versions,
and
the
key
thing
is:
the
client
needs
to
be
able
to
request
what
version
of
the
field
day
effect.
D
So
that's
something
that
can
be
done
with
our
existing
API
machinery,
but
creating
a
new
API
version
is
pretty
heavy
weight
at
the
moment
since
you
have
to
copy
technically
the
entire
API
surface
for
that
a
guy
group.
So
the
proposal
is
a
lightweight
version
of
that,
where
we'd
annotate
the
fields,
versioning
information,
there
are
details
to
be
flushed
out
there.
It's
not
going
to
be
implemented
until
next
year,
but
I
think
we're
all
in
agreement
that
that's
the
direction
we're
going
to
go
and.
A
E
F
I
right
I
mean
what
one
thing
here
is
that
you
know
I.
Thank
you
for
giving
the
update
in
the
group
here.
You
know,
as
the
stuff
gets
decided,
you
know
just
sending
out
a
summary
so
that
so
that
sort
of
the
salient
points
are
widely
distributed
and
aren't
hidden
behind
sort
of
you
know.
A
hundred
hundred
item
issue
would
be
would
be
awesome.
F
D
F
Think
there's
I
mean
API
machinery.
Stuff
is
a
little
bit
special
in
some
ways,
because
a
lot
of
the
decisions
that
you
guys
are
making
are
going
to
have
quite
a
bit
impact
on
other
stuff.
That's
in
ongoing
and
so
I'd
love
to
see
through
the
lines
of
communication
in
summaries,
be
the
more
you
know,
broader
yep.
A
A
Is
a
request
we
have
heard
and
we
will
continue
to
try
to
make
that
make
that
happen
more.
We
brought
in
two
additional
leads
to
say
gay
p
I
machinery
recently,
so
hopefully
we
can
and
I
think
we've
seen
some
responses
and
updates
from
them
as
well.
So
maybe
we
can.
We
can
spread
the
issue,
this
issue
across
more
people.
A
Okay,
also
many
other
questions
on
API
machinery
and
the
annotations
decisions.
Oh
alright!
Well
you
all
know
how
to
find
Brian
anyway,
if
you
have
further
questions
all
right
so
on
to
sig,
apps,
Michelle
and
Matt,
are
you
available
to
tag
team
and
chat
about
the
charts,
repo
and
1.5
targeted
work?
Yes,.
G
So
hello,
I'm,
Michelle
and
Matt
Brina
is
on
the
line
as
well
we're
here
to
talk
to
you
about
big
apps,
and
this
is
our
first
formal
update.
So
sig
apps
as
purpose
is
twofold:
insta
gaps,
we
discussed
how
to
sign
Brian
and
manage
applications
in
Coober
Nettie's,
and
we
also
discuss
and
facilitate
technical
priorities
in
coober
Nonis
development
itself
that
relates
to
running
apps,
looks.
H
G
A
There
is
a
topic
there's
a
room
in
the
developer
summit
that
is
going
to
have
the
is
a
topic
and
what
is
a
service?
What
is
an
application?
How
do
we
define
them?
How
do
we
make
them
easier
to
to
work,
and
how
do
we
have
a
consistent
view
on
this?
So
I
think
that
is
a
question
that
lots
of
people
voted
up
when
we
put
out
the
topics
for
the
dev
summit,
so
we
will
have
more
conversations
about
that.
Thank.
G
I
threw
me
off
Carter
a
little
bit,
so
basically,
we
have
a
one-hour
meeting
every
monday
or
around
40
people
give
or
take
a
few.
We
generally
do
announcements,
demos,
some
stand-ups
on
our
technical
priorities,
and
then
we
have
scheduled
discussion
topics
followed
by
a
discussion.
So
Gemma's
are
a
big
part
of
cig
apps.
Lately
the
theme
has
been
see
I
CD,
and
then
we
also
do.
G
We
also
have
done
demos
of
tools
built
on
top
of
your
guys
in
the
past,
and
we
also
have
demos
on
features
it's
so
such
as
deployments
volumes
and
jobs,
and
sometimes
these
are
demos
from
developers
themselves
and
other
times
their
demos
by
people
using
the
features
so
in
the
future,
we'll
probably
go
towards
talking
about
the
app
development
workflow,
as
well
as
the
user
experience
and
onboarding
of
people
onto
Cooper
Nettie's
for
running
application
and
still
hangs
over
to
not
here
to
discuss
the
technical
priorities
that
we've
been
focusing
on.
So.
I
I
They
were
adding
a
whole
lot
of
features
and
now
it's
moving
towards
stability,
which
is
what
will
drive
towards
release
candidates
when
it's
ready,
and
so,
if
you
want
to,
please
submit
an
issue,
go
check
it
out,
because
at
this
point,
I
just
want
to
make
it
stable
and
then
home
to
go
along
with
home.
Whenever
you
have
that,
we
also
have
the
charts
repo.
I
You
know
work
with
pet
sets,
and
things
like
that
nature,
but
stable
ones
are
things
that
they
now
consider
to
be
stable
and
ready
to
go
and
there's
some
criteria
around
that
what
it
takes
to
get
into
stable.
But
there
are
21,
charts
and
they're
working
on
a
development,
best
practices
guide
to
just
kind
of
teach
people
how
to
go
about
doing
that,
and
so
that's
a
helm
in
the
charts.
The
next
one
is
stateful
applications,
pet
sets
and
I
understand.
Somebody
will
be
talking
about
later
in
this
meeting.
I
The
renaming
of
that
too,
maybe
about
our
name,
but
we're
basically
continuing
to
champion
that
and
move
forward
with
it,
and
some
of
the
parts
are
starting
to
poke
at.
How
do
you
use
pet
sets
well
and
then
the
next
one
is
app
controller.
It's
the
idea
of
how
do
we
have
dependencies
and
order
dependencies
when
you're
starting
stuff
up,
and
so
we
there
are
folks
working
on
doing
that.
I
In
fact,
we
just
got
a
demo
of
that,
and
so
those
are
the
just
a
real
quick
overview
of
the
different
topic
areas
that
we're
working
on.
We
are
doing
a
meet
up
at
coop
gun
for
on
monday
at
four
thirty-
and
I
thank
you
so
here's
our
contact
information
if
you've
got
questions
is
there
anything
else.
Let's
see,
is
there
anything
in
chat.
I
G
Maybe
yes,
okay,
go
to
that
q
and
A's
charts
revo
and
check
out
some
of
the
the
charts
we
have
in
there
there's
21
of
them.
So
it's
a
place
to
get
started,
for
example
with
applications
like
maria
gb
or
wordpress.
Wordpress
is
the
example
that
we
give
people
so
you
can
go
in.
You
can
grab
helm.
You
can
install
this
chart
in
your
cluster
using
helm,
and
then
you
can
also
configure
the
chart
to
meet
your
needs
because
we
understand
not.
G
A
And
then
there
will
be
many
discussions,
I'm
sure
about
all
all
of
the
things
application
related
at
the
developer
summit
and
it
cuber
Nidhi's,
because
we'll
have
lots
of
users
cube
con
because
we'll
have
lots
of
users
talking
about
how
they're
using
Cooper
Nittis.
Thank
you
very
much
Michelle
and
Matt
and
of
course
you
can
always
find
them
on
the
sig,
eps,
select
channel
and
I'm
sure
100
other
ways
and
we'll
put
the
link
to
the
deck
into
the
meeting
notes
so
on
to
our
next
topic
releases.
A
So
we
have
the
trailing
release
and
forward-looking
release.
So
tell
us
Jessie
about
the
1.4
released.
A
J
We
release
1.43
on
sunday,
I
guess,
but
you
should
update,
because
there's
a
security
fix
in
there
for
certificates
on
off
and
then
we're
probably
gonna
do
the
next
one
not
this
week,
but
the
week
after
just
to
like
get
back
into
the
every
other
week
flow
as
long
as
nothing
huge
comes
up.
So
just
keep
like
see.
Seeing
on
your
cherry
pick,
PRS
that
you
wanted
met
and
that's
about
it
also
any
questions.
A
K
The
1.50
alpha
1
release
went
out
last
week
we're
trying
to
keep
a
bi
weekly
schedule,
so
next
one
should
be
about
a
limped
away.
Ahh
next
up
reminder
that
code
freeze
is
less
than
three
weeks
away.
That
means
all
the
plan
code
changes
you
want
for
1.5
make
sure
they
are
merged
by
november.
Seventh,
if
you
missed
that
date,
you're
going
to
have
to
go
through
an
exception
process
and
finally,
we're
planning
on
cutting
the
1.5
branch
earlier
than
a
normal
milestone.
K
The
reason
for
this
is
that
in
the
past
we've
discovered
it
takes
multiple
weeks
to
set
up
the
test
infrastructure
for
new
branches.
The
long-term
goal
is
to
fix
that
process
so
that
it
doesn't
take
so
long,
but
we
have
the
ability
to
cut
a
branch
and
then
fast-forward
it
a
few
weeks
later.
So
for
this
release,
we
want
to
get
started
on
cutting
the
branch
early,
getting
the
test
infrastructure
set
up
for
it,
and
then
we
will
fast-forward
it
around
code
freeze
time
to
match
up
with
head.
A
Fantastic,
you
do
have
audio
working.
Thank
you.
So
there
has
been
discussion
on
going
for
six
months
or
so
about
renaming
pet
sets,
because
there
have
been
concerns
raised
by
a
few
people
that
headsets
can
be
considered
or
view
defensive
from
vary
from
varying
cultural
perspective.
So
Dan
I
will
let
you
go
ahead
and
talk
a
little
bit
about
your
process
and
plan
for
or
finding
the
next
thing.
Yeah.
L
L
We
wanted
to
try
to
get
this
name
change
done
before
we
move
into
beta,
so
we
only
have
a
few
more
weeks
left
for
that
and
that's
that's.
What's
been
one
of
the
forcing
function
in
terms
of
trying
to
get
this
new
name
set
up
I
yesterday
sent
out
a
poll
and
took
kind
of
the
most
popular
names
that
were
in
that
thread
and
send
that
out
to
say,
hey,
let's
vote
on
these
to
figure
out
what
we
should
set,
the
new
name.
I
did
get
a
lot
of
feedback
or
some
feedback
yesterday,
asking
hey.
L
Why
weren't
some
of
the
names
that
I
liked
included
on
this
list
and
so
as
a
result,
I
stopped.
The
polling
said
well
how
about
this?
Let's
change
the
plan
so
that
we
can
solicit
new
names
until
5pm.
Today,
we'll
gather
up
some
new
names
here
and
we'll
come
up
with
another
list
and
I'll
resend
a
poll
later
tonight.
L
That's
the
current
plan
right
now.
If
you
want
to
solicit
like
new
names
that
you
think
should
be
on
the
list
for
contention,
you
can
add
those
as
a
comment
in
that
kid
hooklink.
We
have
a
couple
of
us.
Any
issues
that
we're
still
working
through
today,
probably
the
first
one
is,
is
whether
we
should
offer
pet
sets
as
an
option
or
not,
and
that's
been
kind
of
one
back
and
forth
in
terms
of
like
hey.
L
If
this
is
an
offensive
term,
then
you
know,
then
the
whole
goal
of
this
was
to
change
the
name,
but
if
we
keep
that
as
an
option,
maybe
it's
not
changed.
So
that's
still
going
back
and
forth
and
the
second
is
what
would
the
migration
like
for
existing
users
that
are
already
using
pets
and
already
yep
that's
created
on
what
would
that
be
like
because,
as
part
of
beta
we'd
be
creating
a
new
set
and
I
think
Erikson's
comments
there
about
what
the
migration
compatibility
would
look
like
in
that
type
of
situation?
L
So
that's
currently
where
we
are
another,
a
lot
of
questions
but
I
think
we
can
probably
take
try
to
answer
some
of
them
here.
I,
don't
miss
it,
but
that's
the
latest
in
terms
of
like
what
we're
working
on
in
terms
of
those
three
pay
for
that
sense.
So.
A
Let's
start
with
breaking
that
apart
does
anyone
have
here,
have
concerns
and
what?
What
are
those
concerns
about
the
renaming?
Are
they
simply
the
complexity
of
the
renaming
and
what
the
migration
path
is
or
their
additional
concerns?
I.
A
Hit
all
of
them
all
the
concerns,
okay
or
somebody's
on
mute
all
right,
so
we
need
to
understand,
then
clearly
the
complexity
of
the
change
and
what
the
path
is
to
the
change
in
making
this
decision.
Okay.
So
then
our
people
comfortable
with
Dan
soliciting
more
ideas
in
names
today
and
then
reopening
the
fall
for
feedback
and
contribute
or
feedback
end
and
a
vote
this
evening.
F
So
just
real
quickly,
I
think
some
of
the
concerns
around
headset
is
around
offensiveness
because
it
brings
in
the
whole
street
and
cattle
in
the
head
thing
just
to
be
clear
for
people
who
weren't
clear
on
that
I
think
some
of
it,
though,
is
that
it's
it's
kind
of
an
inside
joke
and
insight
thing.
You
have
to
understand
pets
versus
cattle
and
be
sort
of
steeped
in
that
to
really
have
a
thing
have
any
meaning
to
you
and
so
I
I
guess
is
that's
probably
the
larger
concern
there
right.
D
Please,
if
you
suggest
a
name,
do
think
it
through
go,
read
the
thread
and
some
of
the
considerations
that
are
put
into
some
of
the
names
and
think
about
context
in
which
it's
going
to
be
used
and
discussed
right
and
how
users,
who
are
new
and
looking
to
apply
this
thing
to
the
out
to
the
obvious
use
cases
find
it
and
then
how
you
know,
considerations
like
how
do
you
describe
instances
of
other
thing
and
things
like
that.
So
much
of
those
considerations
are
discussed
in
the
in
the
issue
that
was
posted
to.
H
L
Just
to
be
clear
what
we
did,
what
I
did
yesterday
was
I
didn't
take
I
mean
I
started
with
all
the
suggestions
that
came
up
in
that
in
that
issue
Greg
when
I
filter
those
out
into
the
ones
that
you
know.
We
had
some
discussions
and
said
why
some
are
not
good
somewhere,
someone,
okay
and
there
was
a
filter
list
that
was
like
I,
think,
eight
or
so
suggest
names.
L
That's
a
list
of
people
said
well,
you
know,
there's
other
names
that
I'd
like
to
propose,
and
so
that's
why
the
pole
was
closed
and
saying
to
say
now
we
have
another
34,
more
suggestions
right
now,
but
if
you
have
other
suggestions,
feel
free
to
add
them
to
that
list
and
that's
what
will
be
added
I
didn't
we,
the
initial
poll,
wasn't
every
single
suggestion
that
ever
came
up
and
I
bet
it
just
to
be
clear.
It
was
a
subset
of
those
and
I
think
that's
what
maybe
some
of
the
issue
was
so.
H
N
So
there
will
be
it,
there
will
be
a
process
which
we
hope
will
be
as
in
transparent
as
we
possibly
in
of
translation
from
the
issue
into
the
pole.
Github
doesn't
have
polling,
so
we
can't
do
it
there,
where
we're
going
to
move
it
from
there
to
the
pole.
That's
what
dan
is
working
on.
Please
voice
your
thoughts
in
that
issue.
Not
here
please
in
the
issues,
so
everyone
can
see
and-
and
we
will
do-
that
translation
process
as
transparently
and
openly
as
we
possibly
can
also.
O
The
sorry,
if
not
it's
a
ranked
choice
voting
if
there's
lots
of
options,
it
feels
unsatisfactory
to
say,
like
we
pick
the
winner,
it
had
three
percent
of
the
vote
which
you
yet
if
you
just
did
plane,
pick
one
polling
so
with
ranked
choice,
you
get
more
information
for
each
person,
and
so
when
we
do
pick
result,
it
has
more
weight
because
considered
more
information
from
people.
That's
why
it's
not
and
get
up.
One
reason.
M
And
if
we
think
about
this,
this
is
the
first
time
we've
ever
really
tried
to
do
something
like
this
in
the
community,
so
I'm
pretty
sure
we're
going
to
screw
it
up
right.
Nobody
loves
democracy
until
they
want
their
opinion
heard,
and
then
everybody
hates
democracy
when
they
don't
like
what
everybody
else
chooses.
So
you
don't
forget
you
don't.
N
B
M
Really
important
to
that,
like
the
lesson
that
we
get
out
of
this
is
a
community.
Is
there's
going
to
be
a
lot
of
feedback
in
a
lot
of
opinions
and
the
goal
is
really
to
pick
the
thing
that's
going
to
be
best
for
the
project
over
all
right
to
get
a
name.
That's
going
to
really
represent
cube
to
all
the
users
is
going
to
be
easy
to
understand.
So
please
put
that
consideration
in
accountin
bit
when
voting
claim.
Oh
yeah
I.
H
A
H
Right,
you
might
want
to
know
how.
C
Did
you
say
the
polls
could
be
announced?
What
about
this
I'm
thinking
about
subscribing
to
27
4
30
I
just
said
that
weird
I'm
just
subscribing
to
the
notifications
on
that
issue
so
that
if
anything
else
gets
posted
there,
including
the
pole,
I'll
know
it.
What
if
everybody
that's
interested
subscribes
to
it,
so
that
we
get
the
email
notification
specifically
yeah.
L
D
Q
D
R
A
S
So
the
quick
met,
a
question
here-
or
I
would
say
meta
proposal-
is
that
we
shouldn't
be
putting
this
much
energy
into
naming
things
when
they're
at
the
alpha
stage.
But
clearly,
when
things
are
going
from
alpha
to
beta
I'm,
just
proposing
that
we
can't
put
this
much
energy
into
the
naming
of
every
new
thing.
But
we
do
need
to
get
the
names
right
when
it's
clear
they
are
going
to
be
important.
So
just
a
proposal
for
consideration
is
to
make
the
naming
thing
be
sort
of
an
alpha
to
beta
transition.
A
S
D
O
Transition,
this
will
I
envision
this
to
be
breaking.
It
would
be
sad
if
we
had
a
vote
and
everyone
was
like.
Yay
were
happy
with
the
political
process
and-
and
they
said
oh
crap-
I
have
to
turn
down
my
pet
sets
and
throw
them
up
into
my
winner
of
the
vote.
Sets
so
wanted
to
put
that
out
there
that
when
we
pick
a
new
name
its
alpha,
that's
does
anyone
want
to
talk
to
the
Alpha
breakage
thing
I.
A
Think
that
is
one
of
the
things
that
we
determined
we
need
to
evaluate
in
in
this
name.
Change
is
what
is
what
is
the
path
to
new
name,
so
we
will
vote
on
a
new
name,
but
also
make
sure
we
understand
what
it
does.
So
we
have,
we
end
up
with
a
new
name
and
what
is
the
path
to
the
breakage
through
the
breakage
for
the
end
user,
so
that
we
have
both
of
those,
as
as
decision
points
on
changing
the
name.
O
O
I
feel
having
worked
on
this
twice
with
job
each
time.
It
has
shocked
me
how
much
more
complicated
it
was
to
do
this
type
of
to
do
something
new
in
the
API,
the
CSI
code,
then
yeah.
M
We
can't
yeah
we
should.
We
should
have
a
longer
discussion
about
this
I
think
people
should
be
aware
of
the
consequence
of
it,
but
we
did
do
this
at
least
once
with
minions
and
in
some
of
the
other
renames.
We
do
have
at
least
some
of
the
machinery
here,
but
you're
right.
It
should
not
be
treated
as
zero
cost
Eric.
K
A
A
A
O
A
Alpha,
I
think
the
key
point
is
its
alpha.
Okay,
so
forward
with
the
vote,
put
your
opinions,
many
and
varied
though
they
may
be
into
the
github
issue.
Dan
welcome
to
the
community
trial
by
fire
is
always
fun.
You've
handled
this
graciously
Eric
and
Clayton.
Thank
you
both
for
your
thoughts
and
opinions
as
well
and
bringing
up
the
the
concerns
from
all
the
different
sides
in
this
and
talking
through
it.
A
Tweet
all
right,
then,
my
last
couple
of
topics
here
are
about
the
road
to
coop
con,
so
pucon
sold
out
yesterday.
We
knew
it
was
going
to
happen.
We
knew
it
was
a
little
too
tight,
but
if
you
didn't
get
your
ticket
already
get
on
the
waitlist
now,
because
I
suspect
there
will
be
some
turn
and
some
possibility,
but
get
on
the
waitlist
now,
even
if
you
don't
know
for
sure,
if
you're
going,
if
you
think
you
might
and
you
didn't
get
a
ticket
yet
please
do
that.
A
There
are
going
to
be
a
bunch
of
face-to-face
meetings
for
sega
stirring
coupe
con,
and
there
is
a
link
to
a
document
that
Igor
has
been
set,
that
you
are
set
up
to
try
and
schedule
those
face-to-face
meetings
in
this
document
in
the
community
meeting
notes-
and
there
is
also
space
being
offered
by
the
cloud
native
compute
foundation
during
during
the
conference
in
the
a
hacker
group
space
so
on
the
Cooper
Nettie's
cig
leads
mailing
list
there.
Those
negotiations
are
happening,
but
take
a
peek
at
the
face-to-face
meetings
document
to
see.
A
If,
if
you
can
attend,
if
you
want
to
suggest
times
for
your
cigs
and
also
just
help
help
your
sig
leads
figure
out
when
to
meet
and
where
at
coupon
last
thing
in
the
road
road
to
kbron
is
the
developer
summit
so
invites
went
out
last
week
to
people
based
on
a
rubric
of
asking
a
number
of
companies
to
submit
all
of
the
people
that
they
wanted
to
talk
to
at
the
developer
summit,
as
well
as
a
few
names
from
their
own
companies,
and
that
plus
cig
leads
plus
a
list
of
the
topics
that
were
selected,
which
will
be
published
as
a
schedule
later.
A
A
A
So
it's
a
semi
unconference.
If
you've
ever
done
unconference
we
aren't
going
to
spend
the
first
hour
to
two
hours
of
the
day,
developing
the
schedule.
We've
developed,
half
the
schedule
already
and
then
half
the
schedule
is
going
to
be
developed
on
site.
I,
see
a
question
that
coupe
con
was
a
thousand
people.
Yes,
there
are
going.
A
It
was
a
thousand
people
with
the
cab,
and
that
is
a
fire
marshal
limit,
which
is
why
we
are
now
sold
out,
which
is
awesome,
but
it
also
gives
us
more
information
for
next
fall,
which
is
going
to
be
bigger
and
matter
and
crazier
more
fun.
So
a
bob
is
there
going
to
be
a
session
on
appropriate
project,
naming
only
if
you
lead
it
and
yes,
we
can
do
camping
outside
the
conic
you
want,
but
it
is
Seattle
and
okay.
Now
we've
moved
on
to
snark,
sorry
Joe,
that's
a
vacation
arc.
R
A
A
Stubbornly
York
stuff,
yes,
and
also
integrate
all
of
what's
happened
and
maybe
make
progress
against
things
before
trying
to
report.
I
can
happily
cancel
this
meeting
that
week.
If
we're
all
on
top
of
that
all
right.
Well,
we
can.
We
can
continue
to
discuss
it,
but
it
is
I
think
it's
a
great
idea
because
we
will
have
seen
so
much
of
each
other
that
week,
all
right
any
other
topics,
notices,
thoughts,
snarky
comments,
all
right,
happy
Thursday,
and
thank
you
all
for
having
such
an
awesome
discussion
about
headset,
namings
and
getting
a
scene.