►
From YouTube: Kubernetes Community Meeting 20170817
Description
We have PUBLIC and RECORDED weekly video meetings every Thursday at 10am US Pacific Time.
https://docs.google.com/document/d/1VQDIAB0OqiSjIHI8AWMvSdceWhnz56jNpZrLs6o7NJY
A
All
right,
hi
everybody
I,
am
Harris
Pittman
I
just
started
with
Google
under
Sara
Novotny
working
on
kubernetes
community
stuff
I
do
not
necessarily
represent
one
sig,
but
I
will
be
working
across
SIG's
on
many
upcoming
programs
like
awesome
mentoring,
this
election
and
many
other
things.
So
just
a
reminder
to
please
mute
when
you're
speaking,
we
do
have
a
demo
today
and
a
few
save
updates
and
demo.
First
up
is
Ed,
Lee
and
or
you
want.
B
C
C
C
Is
to
going
to
make
it
easy
to
use
governor
needs
to
get
work
done
so
equivalent
is
provides
orchestration
for
containers,
obviously,
and
so
kind
of
our
ago.
That
kind
of
provides
another
choreography
for
works,
that
you
run
in
committees
to
make
it
easy
for
users
to
submit
jobs
and
to
make
sure
not
the
kubernetes.
Your
covert
govern.
D
C
Cluster
is
well-fed
and
ended
for
at
the
URLs
for
our
github
project
and
so
on,
which
I'll
touch
up
on
a
little
bit
later,
so
it
was
like
okay
next
slide.
So
what
is
the
continued
native
workflows
or
what?
What
this
are
go?
Do
Argo
is
a
workflow
engine
and
where
each
step
in
the
workflow
is
a
container
which
you
can
define
to
be
whatever
you
want.
C
It
also
has
ensure
that
wizard
integrated
artifact
management
since
oftentimes,
when
you're
running
a
workflow
you're
going
to
generate
a
derived
objects
or
artifacts,
will
be
output
by
one
step
and
then
you'll
want
to
consume
them
in
another
stuff.
In
order
to
do
additional
processing.
It
also
has
something
called
fixtures
which
you
can
think
of
it
as
a
easy
way
to
spin
up
services.
Their
comments,
like
you,
know
many
deployments.
C
D
C
C
C
Dent
or
doctor
in
Ducker
integrator
with
system,
because
often
time
we
find
out
when
you're
using
containers
to
you
know,
run
workflows
and
so
on.
You
often
to
run
other
containers
from
their
workflow
I,
say,
run
dollar
bills,
or
things
like
that.
So
this
functionality
is,
you
know
you
get
it
straight
out
of
the
box,
so
you
can
without
doing
anything
else,
you
can
see
me
do
to
start
running
containers
from
your
container
ID.
C
Then
we
also
have
an
admission
control
system
built
in
the
system,
since,
if
you
have
a
lot
of
users
submitting
a
lot
of
drawers
and
some
of
those
jobs
are
large
parallel
job,
they
can
overwhelm
even
even
the
mid
or
large
shoe
kubernetes
cluster,
and
so
you
don't
want
too
many
jobs
piling
up
in
the
system.
It
could,
in
some
cases,
caused
instability.
If
you
have
a
lot
of
churn
in
your
containers
or
if
one
of
the
particularly
minion
knows
go
down
and
come
back
up,
then
all
of
the
pots
out
to
be
restarted.
C
It
gives
you
a
brief
overview
of
our
go
and
then
has
some
simple
instructions
to
get
started.
Basically,
you
just
need
to
download
the
agro
COI
and
then,
when
you
run
our
cluster,
it
will
install
both
a
kubernetes
cluster
as
well
as
the
argo
system
on
top
of
the
cluster,
we're
working
on
a
version
that
will
let
you
just
in
the
article
on
any
existing
kubernetes
cluster.
But
today
you
you
need
to.
It
will
create
a
separate
cluster
on
your
AWS
account.
C
C
Added
a
not
our
goal:
project
directory
to
it
and
within
the
Argos,
a
directory
we've
created
a
couple
of
the
mo
house.
All
of
our
workflows
are
specified
as
llamo
take
a
look
at
the
mo
to
see
what
it
looks
like
so
here's
kind
of
the
high
level
workflow
it's
called
in
books,
BBC
I,
had
say,
example,
CI
reply.
C
You
say
CI
workflow,
mainly
because
most
people
are
familiar
with
how
the
eye
works,
although
I
really
think
that
workflows
longer
term
should
really
be
it'll,
probably
use
more
for
things
that
are
not
the
eye,
especially
by
average
users,
they're
useful
relief
to
get
any
kind
of
work
done
to
automate
jobs
and
so
forth.
So
we
actually
expect
that
a
lot
of
the
workflows
will
be
non
CI,
but.
C
One
you
can
kind
of
see
by
the
structure
death.
First,
there
is
a
kind
of
a
description
section
at
the
top
and
then
there's
an
input
output
section
in
this
particular
case.
This
work
will
have
no
output,
so
don't
have
inputs.
The
two
inputs
are
the
commit
ID
and
the
repo
that
you
want
to
build,
and
then
the
steps
of
the
workflow
consists
of
doing
a
checkout
building
the
code
and
then
running
a
couple
tests.
C
Test
as
well
as
a
kind
of
an
end-to-end
test,
end
to
end
test
is
going
to
actually
spin
update
in
those
DB
instance
that
was
built
bill
previously
and
then
run
run.
Some
requests,
I
guess,
I,
think.
Another
thing
you'll
notice
is
that
between
these
cells
were
testing
artifacts
as
arguments
between
the
stuff.
So
this
first
argument,
for
example,
is
a
code
artifact
which
was
generated.
C
From
the
checkout
step,
which
is
the
previous
step,
the
unit
test
step
also
takes
this
about
the
same
artifact
in
select
CVE
to
each
have
a
slightly
different
artifact,
its
face
with
an
input
BB
binary,
which
will
generate
an
artifact
as
an
output
from
the
build
step.
So
this
is
the
kind
of
artifact
management
really
makes
it
easy
to
kind
of
pass.
The
rod
objects
between
sets
and
those
the
naming
everything
for
you
and
delete
any
artifacts
that
are
not
necessary
based
on
the
schedule
or
one
thing
along
with
it
now
take.
C
C
Basically
IP
address
of
the
input
CD
of
this
fixture,
which
we
defined
us
here.
So
the
idea
originally
assigned
automatically-
and
this
is
the
way
or
there's
networks
as
this
service.
Once
the
data
has
been
loaded
incidence
of
CD,
it
will
run
a
consumer
stuff
which
basically
does
some
gifts
on
input
CB
to
get
the
data
that
was
stored
in
system.
Ok,
as
we
look
at
that
in
this
book,
DB
server
stuff
itself-
you
see
it's
very
simple.
C
C
Okay,
at
a
local
IP
tells
it
to
use
the
template.
That's
stored
locally
on
my
workspace
other
than
on
the
committed
it
may.
It
makes
it
very
easy
to
modify
your
template
play
around
with
it
without
having
to
constantly
commit
them
and
create
kind
of
garbage
in
your
github
repository.
So
as
you
are
in
the
developing
your
template,
this
is
a
very
convenient
feature.
Ok,
the
job
is
and
submit
it.
C
C
C
C
So
this
will
basically
just
bring
up
the
status
of
that
particular
job
that
we're
running,
and
you
kind
of
you
see
that
you
know
it's
currently
running
the
build
stuff.
You
can
look
at
the
llamó
if
you
like,
as
well
from
here
and
I,
showed
the
course
book
by
Emma
corresponding
to
that
particular
step.
C
Of
browse,
what's
happening
and
what's
depth
in
your
code
is
actually
being
executed
along
the
top
here.
You'll
see
a
few
other
tabs,
though
you
can,
for
example,
look
at
all
the
artifacts
that
are
being
generated
and
download.
These
are
the
stuff
that
you
like.
Okay,
let's
see
there,
you
could
also
look
at
all
the
logs
that
are
being
generated.
So
if
you
anything,
goes
wrong,
the
log
file
and
see
what
happened
and
there's
also
a
job
summary
and
one.
C
C
Yes,
I'm
almost
done,
this
is
on
110,
you
can
yeah,
and
so
this
was
in
particular
was
a
CI
workflow,
but
obviously
you
could
run
any
kind
of
a
flow.
In
particular
it
might've
run
kind
of
accumulation.
Did
he
have
a
lot
of
like
parameter?
He
wants
to
run
simulations
create
a
very
simple
workflow
that
runs
at
all
and
Terrell
will
get
it
done.
So
that's
it.
Thank
you
very
much.
B
Those
meetings
have
been
happening,
Monday,
Wednesday
and
Friday
string
last
week
and
this
week
and
next
week
they
will
go
to
a
daily
cadence
because
we're
going
to
be
getting
closer
and
closer
to
crunch
time
on
the
release.
So
in
my
update,
you'll
see
we're
still
sorting
out
a
lot
of
broken
tests,
especially
upgrade
tests.
My
commentary
is
this
happens.
B
Github
is
always
the
record
of
note,
but
there
are
occasionally
times
where
people
update
a
spreadsheet
and
not
necessarily
reflect
that
change
in
github,
and
that
seems
to
be
what
has
happened
this
time.
So
we're
taking
this
as
a
retro
item
and
we're
going
to
work
very
hard
to
to
reconcile
that
for
1.9
and
moving
forward,
there's
no
risk
there
necessarily
to
the
release
other
than
that
we're
just
trying
to
have
full
understanding
of
of
what
is
what
is
different
between
those
two
things.
B
So
the
idea
of
a
centralized
feature
management
process
feels
like
it's
a
little
out
of
sync
with
what's
happening
in
this
release,
so
that
that,
in
some
ways
is
good.
I
think
that
that
the
people
who
are
contributing
code
and
we're
participating
in
sakes
should
have
a
direct
feeling
of
tying
their
work
to
what
those
things
are
that
are
being
delivered.
B
B
and
also
Sagarika,
texture
and
also
sig
release,
because
these
program
management
types
takes
all
have
a
lot
of
cross-cutting
concerns,
and
we
need
to
make
sure
that
those
are
being
spoken
for,
because
the
work
of
product
management
team
is
extremely
important
and
is
how
a
lot
of
great
work
gets
done
to
share
with
the
community
what
what
delivery
are
valuable
or
delivering.
So
it
doesn't
in
any
way
mean
that
SiC
p.m.
is
not
relevant.
It
just
means
that
there's
ways
in
which
the
work
is
being
completed
and
and
managed
that
are
diverging.
B
There's
also
the
fact
that
one
buddy
was
supposed
to
be
a
quote
unquote.
Stabilization
release
did
not
feature
focus,
yet
we
are
sitting
at
a
backlog
of
30
alpha
features
going
in
this,
so
it
doesn't
feel
like
we
necessarily
accomplish
that
goal
per
se.
That
said,
I
want
to
give
my
standard
disclaimer
and
reassurance
that
this
is
very
high
quality
code.
There's
nothing
about
it
that
needs
stabilization.
It's
not
an
unstable
release.
It's
simply.
Where
are
we
focusing
our
efforts?
B
Less
good
is
that
this
is
all
this
is
happening
late
in
the
process,
and
that
is
unfortunately,
because
we
didn't
have
visibility
of
this
sort
of
disparity
until
recently,
because
but
the
work
to
finalize
what
features
are
in
flight
and
such
and
also
working
on,
release,
notes
draft,
that's
where
all
that
stuff
gets
documented
and
it's
pretty
pretty
late
in
the
process.
For
that.
So
as
a
release
team,
we
have
tried
very
hard
to
do
late,
late
changes
in
this
process.
B
So
what
we're
going
to
do
is
we're
going
to
directly
reach
out
to
sakes
and
to
solicit
feedback
on
what
sig
level
prioritization
was
for
the
release.
So
in
some
cases
like,
for
example,
sig
note
there,
their
release
theme
is
actually
more
of
a
rationale
for
the
cigs.
In
the
first
place,
which
is
providing
really
high-quality,
stable,
extensible
code
at
the
node
level
and
less
like
the
specific
features
related
to
to
there
to
this
release,
other
sakes
certainly
will
have
some
themes.
Like
sake,
cluster
heir
apparent
cluster
lifecycle
will
have
some.
B
So
don't
worry,
there's
nothing
really.
Concerning
about
this.
It's
the
natural
and
in
healthy
evolution
of
our
processes,
and
thankfully
we
have
a
community
and
a
bunch
of
governance
around
this.
That's
emerging,
that's
helping
guide!
This
work
and
I
feel
confident
that
we're
going
to
deliver
high-quality
release
regardless
so
before,
I
move
on
any
questions
about
all
that,
because
I
was
a
lot.
B
Okay,
silence
equals
lazy
consensus
except
Robert
Bailey.
What
makes
us
believe
that
this
is
the
case?
Yes,
yeah.
E
I
guess
I
was
just
curious.
You
say
we
think
it's
better
for
end
users.
Why
do
we
think
it's
better
for
end
users
and
who
are
those
end
users
right?
Do
we
expect
end?
Users
are
saying
I
really
care
about
a
new
networking
feature.
Therefore,
it's
better
that
they're
really
started
to
organize
into
networking
being
separate,
that's
storage,
and
that
could
totally
be
the
case,
but
I
would
be
surprised
if
end
users
want
or
should
need
to
care
about
the
substructure
we've
create
within
our
project
to
be
as
things
I.
F
Guess
I
have
some
thoughts
on
that
I
think
it's
important
to
start
educating
the
users
of
the
project
so
when
they
inevitably
run
into
bugs
and
ask
for
feature
requests,
they
know
they
have
at
least
some
idea
in
their
in
their
head
and
I.
Don't
think
we
would
ever
move
away
from
having
component-based
release
notes
as
well,
but
just
ahead
level
like
what
the
sig
does.
What
they're
focused
on
and
I
linked
in
the
sig
node
sig
level
theme
and
the
cluster
lifecycle.
F
Slack
chat
just
like
a
link
to
where
that
link
pages
in
the
community,
because
so
they
can
start
to
build
these
mental
models
in
their
head.
So
they
can
start
associating
that
the
cupola
is
owned
by
take
note
of
ADM
is
owned
by
cluster
lifecycle
same
with
cops
just
to
help,
because
we
I
mean
we're
going
to
start
breaking
down
the
mono
repo,
and
so
they
will.
F
People
will
definitely
need
a
guide
to
help
them,
and
so
I
think
everything
we
do
should
reinforce
the
underlying
structure
of
the
project,
and
just
this
is
just
one
way
one
attempt
of
trying
to
do
it
and
just
we're
gonna.
Try
it
we'll
see
if
people
if
it's
useful
people
will
see
that's
a
good
point.
Yeah.
B
Thanks
killed,
that's
spot-on,
also
that
what
we
didn't
want
to
do
was
try
and
manufacture
themes
like
look
at
this
and
try
and
figure
out
what
those
things
might
have
been
I
think
that's
worse
the
whole
the
whole
intent
of
release
notes
is
really
to
serve
people
who
are
trying
to
evaluate
communities
as
far
as
doing
one
upgrade
to
this
version
are
the
things
that
I
need
to
know
about
this
that
are
irrelevant
to
my
use
case.
What
is
the
impact?
Where
are
the
things
that
I'm
getting
so
it's?
B
It's
really
less
developer
focused,
and
so
it's
a
really
interesting
balance
that
we
have
that
right.
What
is
the
right
level
of
detail
but
I
think
the
things
like
in
networking,
for
example,
see
and
I
work
is
just
absolutely
that's
crossing
release
boundaries.
It's
it's
huge!
It's
it's
so
important
to
the
to
the
the
lifecycle
of
communities
as
a
whole
that,
in
my
opinion,
deserves
to
be
called
out
that
isn't
that's
a
big
deal
and
there
are
their
sinks
with
equal.
B
B
All
right
moving,
hopefully
rapidly
along
that
there's
a
timeline
in
the
communities
community
meeting
notes,
basically
that
links
to
the
timeline
for
the
release
that
we
developed
eons
ago,
which
is
varying
levels
of
correct,
but
I
share
it
because
that's
a
debtor's
our
playbook.
To
date.
The
big
things
this
week
are
that
we
are
trying
to
do
code
unfreeze.
B
That
was
supposed
to
happen
yesterday,
but
we're
doing
it
today,
largely
because
we
want
to
have
the
best
signal
we
can
out
of
tests
and
specifically
upgrade
tests,
and
that
was
not
happening
so
we're
working
very
hard
to
resolve
flakes
and
get
those
tests
giving
a
solid
signal,
and
so
once
that's
good
and
in
place,
we
will
go
ahead
and
cut
the
beta
got
one
and
unfreeze
the
submit
queue
for
things
that
do
not
have
the
or
will
unfreeze.
This
would
make
you
in
the
sense
that
you
won't
have
to
have
the
1.8
milestone
anymore.
B
You
want
to
have
to
have
the
the
requirements
in
place
for
that,
so
1.9
essentially
will
the
work
on
that
will
begin.
The
moment
that
that
gets
cut
over
we're
doing
tech
documents
and
there's
we're
reviewing
and
triaging
open
issues
that
open
issue
count
is
currently
70,
which
is
a
little
concerning,
but
we're
going
to
go
through
those
and
see
what
actually
are
released
blocking.
They
are
considered
release
blocking
by
default
until
they're,
either
pulled
out
of
the
milestone
or
closed.
B
So,
if
you're,
a
sync
with
one
of
those
issues,
please
put
all
hands
on
deck
to
resolve
or
pull
those
out
of
the
milestone
as
soon
as
possible.
Because
if
the
the
release
timing
slips,
it
will
absolutely
be
as
a
result
of
this,
and
if
it
is
a
result
of
that,
I'd
like
it
to
be
because
we're
actually
doing
the
right
thing
and
fixing
critical
issues
and
having
a
high-quality
release
as
opposed
to
just
atrophy
or
maybe
issues
not
getting
terminated
properly
or
resolved
properly.
B
There's
more
detail
in
this
about
the
the
nuts
and
bolts
about
this
week
feel
free
to
ask
any
questions
in
the
sig
release
channel.
If
you
have
those
next
week,
we'll
have
daily
burndown
meetings
will
cut
the
1.8
release,
canada
on
Wednesday
and
the
my
big
ass
sir
from
the
CUNY
is
please,
please
start
playing
with
that
release.
Put
it
through
its
paces.
Do
whatever
you
need
to
do,
because
that
is
a
key
indicator
of
release
health
and
we'll
definitely
need
that
as
soon
as
possible.
G
Hi,
this
is
anthony,
we're
four
one.
Six
great
thanks.
That's
all
for
one
six
ten
is
out,
but
I
don't
have
anything
particular
to
call
out
there,
but
I
do
want
to
take
this
chance
to
reiterate
that
there's
an
issue
with
stateful
said
if
you're
starting
on
something
lower
than
one
seven
you'll
need
to
watch
out
for
this
if
you're
upgrading,
either
to
one
seven
or
even
to
one
eight.
B
H
H
Okay,
so
first
is
a
cube
control
plugin,
it
is
alpha
in
wonder,
grant
to
be
paid
in
one
night
and
the
document
already
and
the
next
is
to
move
cube
control
to
its
own
repo.
So
it
has
to
start
first
eliminate,
eliminate
but
dependencies
its
work
in
progress
and
the
second
step
is
figure
out
how
we
can
test
it
and
how
to
release
it
after
move
it
out.
H
So
for
the
first
step,
so
we
need
to
break
back
bad
dependency,
including
not
depend
on
the
internal
tabs
and
also
move
some
shared
utility
to
to
repo,
which
is
criminally
utils
and
community
common.
The
first,
the
YouTube
repo
has
been
set
up,
but
the
common
repo
is
not
yet
planned
to
be
set
up
at
the
beginning
of
q4,
and
next
is
exploring
Brian's
declarative
application,
application
management
approach.
H
H
H
Currently,
the
code
base
for
this
is
really
hard
to
maintain
and
extent,
and
then
reactor
reacted
hectoring,
the
apply
logic
so
the
current.
What
flowing
applies
first
to
again
and
then
calculate
the
deef
and
the
dance
under
hatch
I
did
the
new
approach
is
to
again
under
calculate
the
deep
and
applied
patch
locally
and
then
do
a
put.
H
A
B
Totally
make
Brian
do
this,
but
he's
got
a
cold
and
he
can't
so
I
as
a
dutiful
sick
person
we're
giving
our
update
quarterly
here,
which
is
basically
that
I've
got
a
link
to
our
meeting
minutes
and
recordings.
Our
meeting
time
is
60
minutes
and
links
every
Thursday.
It
happens
at
8:30
in
the
morning
sometime
when
p.m.
is
Eastern
and
1700
UTC.
B
We
have
an
alternating
schedule
of
office
hours
on
the
weekend.
The
full
meetings
on
the
other
this
week
constituted
a
full
meeting
next
week
will
be
office
hours
just
a
quick
bit
about
office
hours.
We
use
that
time
to
discuss
that's
not
a
time
where
we
would
typically
make
decisions
or
have
procedural
related
things
happen
it's
really
about.
If
people
have
architecture,
questions
that
they
need
answered,
or
they
just
wanted
to
run
things
by
the
the
group
or
the
sig
leaders
or
lead
just
generally
speaking,
and
that's
the
time
to
do
it.
B
It
also
is
sometimes
we're
all
organized
the
backlog
of
things
that
we
need
to
bring
to
the
next
meeting.
There
is
a
architectural
backlog
in
github
and
there's
a
link
to
that
in
the
the
meeting
minutes.
I
right
now.
Our
strategy
since
we're
relatively
new
sig
is
to
get
processes
in
place,
and
then
we
want
to
run
proposals
through
it
to
validate
our
approach.
The
processes
are
mainly
related
to.
How
do
we
review
proposals?
How
do
we
take
in
those
things
and
get
commentary
set
timelines
on
ratifying
or
asking
for
more
question
or
it's?
B
So
there's
a
few
things
in
there
bugs
that
Brian's
going
to
work
on
today
and
tomorrow,
but
essentially
trying
to
make
sure
that
proposals
have
a
home
in
each
sake
and
that
allows
us
to
to
make
sure
that
we
know
who
to
contact
for
the
evolving
architecture
there
and
again.
So
ownership
is
clear,
there's
also
a
proposal
in
process,
its
community
pull
request,
nine
six,
seven
and
that
is
related
to
how
we
handle
RFC's
as
a
community.
B
So
I,
hopefully,
will
get
some
good
feedback
on
that
and
close
that
out
by
the
29th
of
this
month,
that's
being
driven
largely
by
Caleb
and
yeah.
If
you
have
questions
about
any
of
this
hit
me
or
Brian
up
and
we'll
be
more
than
happy
to
help,
there's
also
the
sega
architecture,
slack
channel
and
the
cigarette
texture
mailing
list.
Any
questions
about
that.
A
I
So
border
registration
closed
yesterday,
so
everyone
who's
either
applied
for
membership
status.
You
should
have
gotten
an
email
with
the
confirmation
of
your
status
and
if
you
see
the
second
link
there
on
the
notes,
Paris
has
put
together
a
voter
guide
that
has
a
list
of
all
the
important
it's,
including
when
the
election
is
going
to
start
who,
what
address
you're
going
to
get
the
email
from
which
is
a
CS
Cornell
edu
email
address.
So
you
might
have
to
whitelist
that
so
expect
something
from
that
address.
I
I
Candidates
are
going
to
be
submitting
the
little
platform
pages,
so
you
can
get
to
know
them
a
little
bit
better
know
whether
running
and
anything
that
you
need
will
be
put
in
this
voter
guide,
including
at
the
very
bottom,
a
link
to
the
email
address
of
the
current
bootstrap
committee.
If
you
have
any
questions,
concerns
or
anything
like
that
feel
free
to
ping
us
on
slack
or
the
email.
Thank
you.
Yeah.
A
The
motors
guide
is
a
live
dock,
so
we
will
be
updating
it
as
we
continue
on
through
the
election
cycle.
Also,
if
you
do
not
see
a
candidate
link
to
their
bio
right
now,
don't
fret
just
come
back
and
it'll
be
linked
and
I
think
that's
it
for
the
election
update
thanks,
George
and
I
just
had
one
more
update.
A
All
right,
we
are
going
to
start
engaging
with
an
organization
called
outreach
org.
This
may
have
already
happened
in
the
past
with
certain
individual
slash
things
get
equate
and
get
acquainted
with
the
site.
This
is
a
fully
funded
stipend
internship
for
underrepresented
folks
in
text.
It
acts
like
an
internship,
but
they
help
us
contribute.
The
docs
team
is
now
putting
together
a
project
proposal.
So
if
anybody
on
here
is
interested
in
mentoring,
anyone
would
be
an
unfair
person,
an
individual
in
tech.
Please
get
in
contact
with
me.
A
The
excuse
me
the
outreach
e
RG
information
is
going
to
be
in
the
note
section
as
well,
but
this
is
not
a
call
to
action.
This
is
just
a
call
to
see
if
you're
interested
but
reach
out
to
me
individually,
either
slack
or
I'll.
Put
my
my
Google
email
address
on
the
dots
as
well,
but
anyone
else
have
any
other
quick
announce.
Actually,
no
sorry,
we
have
a
an
election
question.
Yeah.