►
From YouTube: Kubernetes Community Meeting 20170907
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
A
Okay,
hi
everybody
today
is
Thursday
September
7th.
This
is
the
kubernetes
community
meeting.
This
is
a
community
meeting
and
will
be
posted
publicly
on
youtube.
So
please
be
mindful
that
what
you
say
is
being
recorded.
I
am
Erin
creaking
Berger
for
those
of
you
participating
in
zoom
right
now.
You
see
my
name
is
sig
testing.
That's
because
I
am
one
of
the
co
leads.
Obviously,
testing
shout
out
for
all
the
awesome
work
that
we
do.
We
need
to
x'
days,
I'm,
sorry
Tuesdays
at
1
p.m.
Pacific.
A
B
Here:
cool,
take
it
away!
Okay,
thank
you
share
screen
with
moon,
slides.
Okay,
good
evening
good
morning,
everyone
I've
talked
before
I've
presented
different
things
in
the
meeting
I'm
going
to
talk
today
about
shield
secrets.
It's
actually
something
that's
been
written
by
someone
called
Angus
Lee's,
but
Angus
or
Gus,
as
we
call
him
lives
in
Australia.
So
the
the
meeting
here
is
not
helpful.
The
time
is
not
good
for
him.
He's
sleeping
so
I'll
present
it
for
him.
B
We
both
work
at
bit,
nummy
I,
presented
Cube
last
couple
weeks
ago,
bit
nummy
focuses
on
apps
apps
apps.
You
know
you
I,
think
you
know
about
all
of
this.
What
is
shield
secrets?
The
problem
that
we
were
trying
to
fix
is
that
you
can
keep
all
your
communities
manifest
in
under
version
control.
Indeed,
except
your
secrets.
Why?
Because
the
secrets
are
not
encrypted,
the
content
of
the
secrets
are
not
encrypted
base64-encoded.
B
So
you
cannot
keep
your
secrets
under
version
control.
They
would
be
pretty
much
in
the
clear.
So
that
was
the
problem.
So
what
did
we
do
with
secrets?
It's
basically
an
extension
to
kubernetes.
We
create
a
new
kind,
a
new
object
which
is
called
a
sealed
secret,
which
is
truly
encrypted,
and
when
you
create
the
secret
with
cube
CTL,
there
is
a
controller
that
decrypts
it
and
then
creates
the
real
full
humanity's
secret.
B
The
code
is
open
source
github.com,
slash
bit,
nummy
sealed
secrets,
so
you
can
get
it,
and
indeed
it's
quite
straightforward.
Now
that
you
know
a
lot
of
people
have
talked
about
extensions
and
third-party
resources.
Here
are
these,
and
so
on
sealed
secrets.
There
is
a
TPR
right
now
we
haven't
yet
moved
to
CR
D.
We
will,
you
know,
definitely
pretty
soon,
truly
41.8,
but
right
now
it's
a
cheap
er
called
secrets,
and
then
there
is
a
controller
running
in
cluster.
In
go
this
controller.
B
When
you
start
it,
when
you
start
it,
it
generates
a
public
private
key
which
allows
you
to
then
decrypt
the
secrets:
okay,
yeah.
There
is
a
nice
block
by
Gus
himself.
If
you
want
to
go
through
the
details,
especially
details
about
the
encryption,
algorithms
that
are
being
used,
you
know-
and
you
actually
check
that
with
guys
from
sig
HOF
I'm,
not
sure
who
exactly
at
sing-off,
but
some
people
would
see
god
I
reviewed
the
the
encryption.
So
again
it's
so
the
controller
starts
generates
a
certificate.
B
Then
you
have
a
CLI
cube
seal
and
with
that
cube,
CL
CLI,
you
know
you
can
retrieve
the
public
key,
that's
in
the
stored
inside
the
controller
in
the
controller
logs,
and
then
you
encrypt
your
secrets.
It
creates
the
sealed
secret
and
then
you
can
store
that
in
get
under
version
control.
Okay,
so
you
have
your
secrets
in
get.
You
can
store
everything
and
get,
and
we
think
it's
great.
How
does
it
look
here?
You
know
I'm
going
to
go
through
this
demo,
but
here
you
have
a
little
snapshot.
B
You
create
your
secret,
so
with
the
dry
run,
you
can
just
create
the
JSON
of
a
traditional
secret.
We
know
this,
but
you
don't
store
that
under
version
control
and
what
you
do
with
cube
Co
the
command
is
that
you
cube,
sealed
your
your
and
generate
your
sealed
secret.
Actually,
I
made
a
mistake
with
that
comment,
and
then
you
see
that
the
the
content
of
the
actual
you
know
object,
that's
generated.
It
is
truly
encrypted.
B
B
You
see
that
at
the
bottom,
I
have
one
part
in
my
cube
system
in
namespace,
which
is
the
sealed
secrets,
controller.
So
I've,
you
know,
I've
created
I've
launched
it
before.
So,
if
I
look
at
my
third-party
resources,
you
will
see
that
I
have
a
secret
third
party
resource,
which
means
that
if
I
do
get
filled
secrets,
it
answers,
and
it
tells
me
you
have
nothing
if
I
know
how
to
type.
So
it
tells
me
I
have
nothing
and
if
I
look
at
my
secrets,
it
tells
me
I
have
no
just
the
default
secret.
B
B
So
now
what
do
we
have?
We
have
a
secret
that
Jason,
okay,
we're
back
on
our
feet.
You
see
the
data
and
it's
just
based
64
encoded.
You
don't
want
to
store
that
in
github.
So
now,
what
do
we
do?
We
use
our
cube,
see
command
and
we
get
the
secret
object
and
we
generate
a
sealed
secret.
So
you
need
to
generate
the
sealed
secret.
And
now,
if
we
look
at
this
secret,
you
go.
You
see
that
it's
said.
B
Amazing
I
have
a
fubar
secret
that
just
got
generated
by
my
controller
and
now,
when
I
look
at
the
data,
I
fall
back
on
my
feet
with
the
base64
encoded
version,
so
the
controller
decrypted
the
secret
and
generated
the
secret
object.
And,
of
course,
if
I
look
at
my
shield
secrets
my
object
is
there
my
fubar
sealed
secret,
ok,
so
I
hope,
that's
relatively
clear.
There
is
a
nice
garbage
collection.
So,
if
I
do
a
delete
field
secret
fubar,
if
you
delete
the
field
secret,
it's
going
to
delete
the
actual
secret.
B
A
C
B
So
I
mean
the
key
management
service
and
in
1.7
you
have
encryption
in
a
CD
of
the
secrets,
but
but
the
secret
it's
in
itself.
When
you
get
it
from
the
API,
it's
it's
still
base
64
encoded.
So
you
cannot.
You
cannot
stick
it
under
version
control
thanks.
So
so
we
still
secrets
you
have
proper
encryption.
You
know
outside
of
the
outside
of
the
communities.
Api
boundary.
D
Currently,
to
get
to
wax
poetic,
although
I'm
not
going
to
so
much
relief
given
to
everybody.
There's
a
lot
in
here
I
would
ask
that
you
just
read
the
notes
in
the
agenda
to
get
the
full
gist
of
this,
because
there's
a
lot
of
links
out
to
things
but
bottom
line.
We
have
begun
burndown
meeting
so
I
started
yesterday,
like
yeah
yesterday,
it's
been
a
hacker
week
and
there
is
a
link
in
the
agenda
to
the
meeting
notes
and
also
in
the
meeting
notes.
You'll
find
a
recording.
D
We
had
really
good
attendance
and
we
started
a
lot
of
the
conversations
that
were
going
to
be
continuing
throughout
the
release,
which
is
still
targeted
to
September
27th.
There
is
a
Google
Group
called
the
burndown
meetings
or
Nettie's
burndown
meetings
that
you
can
join
and
there's
a
link
there
that
you
can
get
an
invite
to
the
meeting,
and
you
can
also
contact
me
privately
and
I'll.
Add
you
directly
to
the
meeting,
if
that's
easier,
so
I
will
do
that.
D
We'd
planned
for
yesterday
heard
the
originally
agreed
timeline
to
do
the
beta
cut,
but
Adam
are
a
branch
manager
felt.
There
was
some
concerns
about
getting
good
test
signal
and
having
the
beta
actually
be
usable,
and
so
we
decided
to
punt
to
today
we're
kind
of
going
through
that
process
today
to
see
if
we
can
get
good
signal
on
all
the
tests
and
all
the
things
I
haven't
actually
checked
them
with
Adam.
You
know
the
super
recent
future
or
past
about
that,
so
I
will
figure
out.
What's
going
on
there
for
updates
on
that.
D
For
the
most
part,
you
can
just
go
to
the
sig
release
channel
and
ask
questions,
there's
known
as
there's
an
ominous
cat
behind
me
I,
and
so,
if
you
have
questions
about
the
release
process,
you
can
go
to
sig
release
right
now.
We
have
a
lot
of
missing
release.
Notes
in
the
draft
and
I
would
love
for
us
to
get
more
traction
on
getting
those
sig
labels
checked
off
in
there.
If
you
are
a
Sagan,
you've
already
done
your
draft
and
are
done
and
didn't
check
that
off.
D
D
We
have
a
large
disparity
between
the
37
marked
as
active
in
the
tracking
spreadsheet,
versus
the
61
open
issues
in
the
1.8
milestone
and
the
features
repo.
That's
not
great
if
you
artist
sing
and
you
have
decided
that
your
feature
is
not
going
to
ship
in
1.8
and
you
have
not
filed
for
a
an
extension.
Please
go
in
and
remove
the
1.8
milestone
and
change
it
to
next
or
1.9,
but
anything
but
one
at
8.
D
There
are
113
current
open
issues
in
the
1.8
milestone,
just
a
reminder
that
we
are
going
to
start
curating
these,
because
this
is
one
of
the
core
pieces
of
signal
we
have
about
the
health
of
release.
So
if
something
is
in
a
test
and
there's
a
an
issue
out
there,
that
indicates
we
have
a
problem.
That's
key
to
us
determining
usability
the
release
in
the
long
term
and
open
issues
will
be
taken
very
seriously
by
the
team,
as
it
should
I.
D
So
right
now,
I
think
Maria
put
in
an
update
in
about
the
munchbot,
but
essentially
I.
You
can
look
for
the
issues
that
have
been
removed
by
the
munchbot
as
we
move
forward
by
filtering
out
the
milestone
and
remove
label
lots
of
failing
released
master
blocking
tests.
Unfortunately,
this
is
still
happening.
If
you
look
at
that.
The
test
grid
summary
for
that
not
looking
great.
This
is
currently
what's
hampering
our
ability
to
cut
the
beta.
D
D
Lastly,
this
is
just
a
PSA
about
the
release
notes
label
in
the
future.
We
are
going
to
be
relying
more
on
the
release,
notes
section
of
the
template
for
PRS,
so
just
if
you
can
make
sure
that,
when
you're
putting
in
the
that
release,
notes
section
of
the
PR
I'm
trying
follow
the
guidelines
that
are,
in
the
actual
example,
or
look
up
other
PRS
that
have
that
in
place.
D
Just
so,
you
can
make
sure
that
formatting
is
correct,
because
there
are
some
fine
work
going
on
right
now
to
automate
the
scraping
of
those
release,
notes
into
some
sort
of
usable
format
and
that
relies
on
good
source
data.
So
thank
you
for
that.
Are
there
any
questions
and
I
have
not
seen
chat
yet
and
I'm
scared
to
look
today.
E
So
I
wanted
to
add
one
thing.
This
is
from
the
point
of
view
of
the
futures
repo,
the
part
of
the
release
team
and
the
PM
sig
will
be
talking
about
what
the
messaging
is
overall
for
the
release
and
for
the
blogpost
next
week
early
next
week.
So
it's
important
to
make
sure
that
the
description
is
just
reaffirming
what
Jay
said
important
to
make
sure
that
the
descriptions
are
accurate
and
the
status
of
each
feature
are
accurate,
because
that's
how
we
will
select
what
the
release
themes
are
that
are
gonna,
be
highlighted.
D
Yes
and
Christopher,
in
which
Jenna
asked
if,
if
the
release
notes
should
be
in
the
Google
sheet,
the
Google
sheet
as
a
as
a
mirror
of
the
github
data,
so
github
is
the
source
of
truth
for
all
these
things.
So
please
make
sure
that
the
release
notes
draft
is
updated
and
that
the
sig
that
you
are
part
of
is
checked
off
that
list
and
yeah
release
themes.
D
This
is
something
we'll
probably
talk
about
when
do
the
retrospective
this
time,
but
this
was
supposed
to
be
a
quote-unquote
stabilization,
analyse
and
and
there's
a
lot
of
features
in
it.
So
we
need
to
as
a
community
start
through
that
and
I'm,
not
necessarily
worried
about
it,
because
it's
something
that
we'll
figure
out,
but
it's
something
that
we
definitely
need
to
talk
about.
A
Any
other
questions
from
Anthony
was
about
whether
or
not
there
is
a
raw
auto-generated
list
of
poll
request.
Release
meant
posted
someplace,
so
in
the
past,
somebody's
run
a
tool
called
rel
notes
which
generates
a
bulleted
list
of
full
requests,
along
with
a
one-line
thing
that
was
scraped
out
of
her
lease
notes,
and
then
everybody
has
dived
in
and
picked
those
apart
and
sort
of
treated
their
individual
changelogs.
From
that
we're
not
doing
that.
This
time
around,
we
have
somebody
I.
A
What
we,
on
the
same
basic
basis,
find
important
people
haven't
done
a
fantastic
job
of
adding
sink
labels
to
pull
requests,
even
though
there's
no
BOTS
nagging
them
to
do
this,
so
you
should
be
able
to,
for
your
cig,
go
construct
to
get
up
query
that
it
looks
for
all
the
pull
requests
that
were
closed
by
a
certain
date
that
had
your
sakes
label
applied,
and
you
could
use
that
as
a
source.
This
was
something
I
think
that
Phil
would
Rock
raised
during
the
release
meeting
or
released
burned
out.
D
That's
correct
and
I'm
shared
a
link
in
the
zoom
chat,
which
is
bitly,
slash,
1/8,
rel
notes.
This
is
my
own
painful
attempt
at
looking
at
these
released.
Note
label
equals
true
and
merged
equals.
True,
so
you
can
see
how
all
over
the
map,
those
those
release.
Note
indicators
are,
and
that's
why
I
was
asking
about
and
we
make
sure
that
we
normalized
the
data
in
those,
because
it's
really
unusable
right
now
and
it
doesn't
have
to
be
that
way.
D
I
think
people
are
just
struggling
with
the
format
and
so
we're
gonna,
try
and
I'm
sure
this
will
come
up
in
Trebek's
as
well.
We're
gonna
try
our
best
to
make
this
easier
and
more
straightforward.
It's
just
a
process
and
we're
in
the
process.
You
know
going
through
improving
it
as
we
go
and
so
SIG's.
If
you
do
want
to
see
those
the
release
note
equals
true
merged
PRS
that
that
link
I
provided
in
chat
will
get
you
there.
So
any
other
question.
A
One
other
one
other
bit
of
color
I
wanted
to
provide
is
the
at
least.
According
to
the
schedule.
We
have
posted
right
now,
code
freezes
for
tasks
to
be
lift
by
Wednesday
September
13th,
based
on
the
fact
that
we
haven't
caught
the
beta,
yet
that
may
be
at
risk.
If
you
want
to
find
out
more
information,
we
will
be
keeping
communities
that
have
updated
and
attending
that
really
spend.
Our
meetings
would
be
helpful.
A
The
reason
I
raised
the
code
freeze
date
is
that
some
of
you
may
have
noticed
that
the
Amazon
or
tops
ahead
of
us
are
cops
presubmit
job
that
runs
on
your
pull.
Requests
is
failing,
but
things
are
still
merging.
Despite
that,
that's
because
it
would
make
its
move
to
you
non
walking
a
little
while
ago,
when
we
discovered
that,
for
some
reason,
the
code
being
tested
wasn't
the
code
in
the
pull
request.
A
We
believe
we
result
that
we
believe
we've
resolved
quota
issues
around
the
account
that
was
being
used
to
run
these
pull
request
jobs,
and
so
our
intent
is
to
move
that
back
to
a
block
increase
in
the
job
that,
yes,
you
shouldn't
pay
attention
to
by
lifting
code,
freeze,
sorry
by
the
list
of
countries
which
would
be
Wednesday
September
13th,
unless
we
determine
otherwise
along
the
way.
Okay,.
A
A
F
Yeah,
a
quick
update
from
the
sig
you
I
side
got
some
funky
lens
player
happening,
but
this
works
because
I'm
in
Seattle,
so
it's
reflective
of
the
atmosphere
outside
right
now,
yeah
I,
I
added
into
the
agenda
a
link
to
our
biggest
new
feature,
which
is
going
to
be
in
the
next
release
of
dashboard,
which
is
authentication
login
I
would
have
done
a
demo
for
that,
but
I
wasn't
able
to
get
that
set
up.
So
basically
just
a
login
screen
to
see
and
there's
still
design
refinements
happening
there.
F
That
hasn't
gotten
a
lot
of
UX
attention
yet.
But
that's
something
we're
excited
about
that
now
dashboard
will
respect
our
back
and
the
our
back
that's
set
for
a
cluster
right
now
we
have
three
e
main
ways
to
authenticate
basic,
just
being
username
a
password
via
a
token
or
by
a
cube
config
file
that
they
can
choose
to
upload.
F
So
that
will
be
I
think
will
be
around
the
same
time
as
the
one
eight
release
I
think
will
be
one
seven,
so
we're
out
of
sync
again
but
I
think
unless
we,
unless
it
was
a
new
version
of
client,
go
released,
that
that
is
the
current
plan
to
at
least
one
seven
and
then
follow
up
with
one
a
some
point
in
the
future.
After
that,
so
logins
a
big
new
thing,
we're
excited
about
other
than
that.
F
There's
some,
some
more
minor
updates
that
maybe
now
you
can
download
blogs
the
log
page
and
traditional
Chinese
is
now
supported
and
then
future
work.
We're
looking
to
the
big
things
are
to
improve
the
search
functionality
to
have
autocomplete
I.
Think
that'll
be
a
big
usability
improvement
for
people
and
adding
in
a
settings
page,
so
we
can
have
integrations
with
third-party
tools
and
be
able
to
manage
those
there
and
then
adding
in
live
reload,
and
so
what
we
have
we're
now
respecting
any
are
back
set
by
the
command
line.
F
Are
back
management
via
dashboard
is
still
not
something,
that's
supported.
So
that's
something
we'll
look
to
make
progress
on
right
now.
We
mostly
just
have
two
developers
working
on
dashboard,
so
that's
it's
a
little
bit
of
a
slower
pace
than
it
could
be,
but
hopefully
we're
thinking
about
ways
to
recruit
more
and
get
more
interest.
F
We've
got
coop
con
coming
up
and
at
the
least,
we'll
be
hopefully
kind
of
repeating
the
same
survey
that
we've
done
in
the
last
two
coupons,
just
kind
of
getting
a
perspective
on
how
people
are
using
dashboard
and
how
it's
serving
their
needs.
And
then
beyond
that,
maybe
doing
some
evangelism
and
trying
to
get
some
people
interested
in
contributing,
and
we
moved
our
weekly
segment
to
Nabi
Thursdays
at
9:00
a.m.
Pacific.
G
I'm
sure,
eventually
get
to
that
where
people
realize
you
know
it
was
one
of
the
things
we
had
an
open
stack.
That
was
really
tricky.
You
get
all
the
basic
authentication
working
the
UI
and
then
you
realize
oh
crap.
The
federated
identity
is
a
slightly
different
path
or
the
redirects,
and
just
something
to
think
about.
A
Okay,
I
think
maybe
actually
be
it
for
so
you
take
updates
today,
I
see
sac
has
been
making
some
notes
on,
say,
Docs,
noting
that
he
sick
talks
may
be
able
to
help
with
release
notes.
Formatting
probably
wants
to
collaborate
with
Jace
on
that,
and
actually
the
mention
of
sig
Docs
reminds
me
of
something
that
came
up
during
the
burndown
meeting
yesterday.
A
A
A
H
A
Think
we
had,
we
had
some
discussion
about,
maybe
like
locking
down
master,
preventing
people
from
making
pull
requests
against
master
as
well.
That
so
discussion
about
that
in
cig
docks
would
be
appreciated
as
a
just
like
the
right
same
strategy
going
forward.
I
think.
I
J
We're
talking
about
Doc's
something
I've
run
into
recently,
as
I've
been
doing
client
work
as
I've
found
that
there's
a
bunch
of
protocols
that
are
really
poorly
documented,
for
example,
like
how
we
encode
protobufs
I,
think
that
is,
there
is
Doc's
the
right
place
to
house
that
sort
of
thing,
or
do
you
think
we
need
to
do
retrospective
proposals
or
what
it?
What
is
the
right
solution?
I
think.
K
H
So
kubernetes
to
do
is
for
user
Docs.
However,
people
building
on
top
of
kubernetes
api
is
our
one
flavor
of
user
right,
so
those
Doc's
I
think.
Do
you
need
a
home
on
communities
that
IO,
as
opposed
to
contributor
dots
for
people
hacking
on
communities
which
don't
belong
in
communities
that
I
oh
yeah,.
H
J
That's
one
of
them,
but
actually
also
like
our
proto
encoding,
is
for
magic,
bytes,
plus
proto,
encoded
unknown
object
with
a
raw
field.
That
is
then
the
proto
encoding
of
the
actual
object
question
and
the
actual
the
only
reason
I
know
this
is
I
managed
to
go,
find
the
code
that
actually
does
the
encoding
and
I
read
the
code.
A
H
Yeah
science,
so
in
the
reference
section
I
I
mean
hopefully
eventually
we'll
have
more
complete
Doc's
for
people
writing
clients,
our
communities,
dot,
IO,
but
right
now
we
do
have
the
reference
section
and
we
do
have
API
Doc's
there.
So
putting
something
relating
to
this
there
would
be
uncle
okay.
A
I
think
somebody
was
talking
about
what
we
could
or
should
do
with
proposals
through
their
lifecycle
to
turn
them
into
documents.
That's
probably
something
to
be
discussed
if
it
hasn't
already
at
big
architecture,
which
I
believe
is
in
charge
is
in
the
process
of
refining
the
proposal
process.
Yeah.
H
H
A
Okay,
cool
as
representative
of
state
testing,
I'm
gonna
hijack
real
quick
to
show
one
tiny
little
thing:
there's
been
a
lot,
that's
been
going
on
in
cig,
testing
and
I
hope
to
give
a
fuller
update
later,
but
we
have
a
new
new
dashboard
in
test
grade
called
kubernetes,
pre-submitted
I'm.
Looking
at
the
summary
tab
right
now,
and
it
shows,
roughly
speaking
the
passing
flaky
or
failing
status
of
every
single
job,
that's
run
as
the
priests
event.
No,
not
all
of
these
are
blocking
pre
submits.
A
So,
like
I
said
earlier,
the
AWS
one
is
not
a
block
increase
event
because
we
can
see
for
the
past
day
or
so
it's
been
failing,
but
it
was
kind
of
seen
at
one
point
and
we're
working
on
making
it
passing
again.
So
this
is
historically
something
I've
had
to
go
like
sift
through
a
bunch
of
pull
requests
one
on
one
or
go:
look
through
goober
nadir
to
find,
and
now
you
can
just
go
to
one
page.
A
It's
test
read
I
know:
I
already
lost
it,
because
the
presenting
thing,
kubernetes,
pre,
submits
I
click
on
this.
It
takes
me
to
be
summary
tab
by
default
and
I
can
see
the
status
of
all
of
the
runs.
The
wording
is
wrong,
except
on
the
past
week,
it's
like
the
past
24-hour
period,
but
yeah
just
a
little
sign
of
improvement
in
the
testing
for
the
world.
L
And
thirteen,
the
13th
and
for
membership
for
voting,
that's
a
form.
All
this
stuff
is
also
going
to
be
located
on
the
voters
guide
to
so
lots
of
hot
links
on
there
anything
else.
The
election
itself
star
on
the
19th,
since
only
the
last
two
weeks
decision
will
be
made
on
the
community
meeting,
that's
October
5th,
with
a
blog
post
to
follow
with
decisions
yep.
M
A
A
We're
on
the
original
list
of
it
handles
that
signify
that
you
have
standing
to
vote,
but
you
must
fill
out
the
Associated
Google
form
in
order
to
collect
your
email
address
that
you
can
actually
receive
about
ballot
to
vote.
So,
if
you're
not
filled
out
the
form,
please
do
so
and
I
believe
Clinton
was
going
to
send
out
a
painter.
George
was
sent
out
of
follow.
People
who
are
listed,
Handel
was
listed.
A
M
Sebastian
to
answer
your
question:
we
have
about
375
people
who
have
standing
at
this
point
and
only
a
handful
that
we
have
said.
No,
please
keep
contributing
you're
super
awesome
and
we
want
your.
We
want
your
work
in
your
efforts
and
you
know
next
time
you
will.
You
will
have
had
enough
time
in
the
community,
so
the
Eric,
the
voter
registry,
has
not
been
published.
Yet,
although
the
initial
list
of
people
with
standing
that
we
know
knew
was
incomplete,
is
in
the
early
emails
about
this,
we
will
be
following
up
with
more
I
guess.
K
H
M
We'll
make
sure
that
we
get
it
published
ahead
of
time
ahead
of
the
13th
so
that
we
can.
We
can
do
double
we're,
also
cross-checking
with
that
full
initial
list
of
standing
to
make
sure
that
we
continue
to
get
out
the
vote
from
those
people.
So
you
would
get
an
email
if
you
are
not
in
the
of
standing
or
sorry
if
you
are
not
registered
list,
but
you
were
in
the
original
of
standing
list.
M
M
Actually
don't
know
if
we
sent
confirmations
to
the
people
who
were
in
the
original
list,
we
may
have
that
one
I
don't
know
Swarna
says
you
should
have
gotten
an
email
from
Tim.
She
did
so
we'll
double-check
for
you
Eric
and
then
also
send
out
more
more
messages
asking
for
people
who
were
in
the
original
lists
to
register
if
they
haven't.
L
Answered
Doug's
question
about
the
instructions
on
the
BIOS:
all
the
nominees
will
have
instructions
for
BIOS
once
we're
live
with
the
voters
guide.
The
people
in
there
now
did
it
due
to
travel
reasons
and
and
other
things.
So
if
you,
you
know,
you're,
not
gonna
vailable
the
next
48-72
hours
to
do
a
PR,
then
just
get
it
in
there
now
or
you're
out
later.
G
G
The
bio
is
them.
The
statement
of
you
know.
The
their
vision
of
what
they
want
to
accomplish
is
something
different
in
it.
You
know
well,
I
wanted
to
drive
this
in
the
community.
I
want
to
make
the
UI
the
best
thing
ever.
I
want
to
make
sure
it's
in
or
operable.
We've
used
that
in
other
communities
and
it's
kind
of
a
nice
touch
it's
kind
of
like
their
little
pitch
and.
A
M
J
J
I
would
also
emphasize
that,
like
I,
don't
really
don't
think
the
steering
committees
job
is
to
really
push
any
particular
agenda
other
than
the
functioning
right
like
it's
not
to
add
emphasis,
it's
not
to
push
any
particular
project.
It's
it's
really
to
ensure
that
everything
moves
everything
moves
smoothly
and
all
the
decisions
that
happen
in
the
SIG's
are
the
things
that
shape
the
project.
Yes,
going.
M
J
Just
just
to
be
100%
clear
if
you
believe
that
you
want
to
have
large
impact-
and
you
are
going
to
do
this
via
the
steering
committee-
I
guarantee
you.
The
time
spent
on
the
steering
committee
will
actually
have
a
negative
impact
on
your
ability
to
have
impact
on
the
project
and
you
should
go
work
in
a
sig
technical.
J
J
Although
even
there
I
think
we
plan
on
pushing
a
lot
of
that
stuff
into
sig
governance,
I
mean
code
of
conduct,
maybe
is
one
where
we
will
actually
cover
it
anyway.
I
just
wanted
to
really
emphasize
the
fact
that
we
really
view
this
as
a
service,
because
the
community
not
a
way
to
get
something.
Your
particular
pet
project
committee.
H
A
Those
things
seem
incredibly
mundane
or
mind-numbing
to
you.
The
steering
committee
is
probably
not
the
place
if
you
find
these
to
be
deeply
exciting,
I'm,
maybe
a
little
worried
for
your
mental
health,
but
look
forward
to
collaborating
with
you
on
these
things,
because
these
are
the
chopping,
wood
and
carrying
water.
Things
that
make
this
project
run
more
smoothly.
H
A
M
19Th
at
some
time,
which
is
still
to
be
inserted
in
the
voters,
registration,
voter
registry
guide
and
then
it
will
end
in
two
weeks
after
that
and
then
on
the
fifth
Thursday,
the
5th
of
October.
We
will
announce
the
announce
the
winners
here
in
the
community
meeting
and
then
published
immediately
all
of
the
stats
and
a
blog
post,
saying,
goat
and
all
of
that,
and
there.