►
From YouTube: Steering Committee Meeting 20180131
Description
Recording of the Steering Committee meeting. See also:
https://github.com/kubernetes/steering
Chat transcript (times may be slightly off):
00:08:13 Aaron Crickenberger: https://docs.google.com/document/d/1qazwMIHGeF3iUh5xMJIJ6PDr-S3bNkT8tNLRkSiOkOU/edit#
00:08:27 Aaron Crickenberger: https://github.com/kubernetes/website/issues/6525
00:10:38 Timothy St. Clair: It’s not trivial
00:12:01 Timothy St. Clair: Sure.
00:25:57 Joe Beda: interface and starting implementation.
00:26:55 briangrant: https://github.com/kubernetes/community/blob/master/sig-governance.md#sig-governance
00:41:09 Quinton Hoole: Could someone put a link to Brendan’s doc in the notes?
00:41:36 Aaron Crickenberger: https://docs.google.com/document/d/1yauW9zMtWgXN8xh4q6144B2xBTPuIOLGc0L6aQPMj1I/edit?ts=5a3c8c55
00:41:39 Aaron Crickenberger: Linked in doc as well
00:50:34 Joe Beda: cluster lifecycle should have picked a shorter name
00:52:40 Timothy St. Clair: sgtm
00:53:07 briangrant: https://github.com/orgs/kubernetes-sigs
00:53:11 briangrant: You all should be invited
00:57:41 Joe Beda: Let's make it official
A
I,
don't
sweet
all
right,
so
we're
having
the
bi-weekly
steering
committee
meeting
for
kubernetes
today
is
Wednesday
January
31st
and
this
is
being
publicly
recorded
and
will
be
posted
to
YouTube
later
on.
I
am
a
clean
is
best
in
the
day,
so
I'm
just
running
through
the
agenda
which
I'll
paste
and
chat
again.
If,
although
have
quick
access
to
it,
we
got
wind
of
an
issue
about
how
pastures
as
an
exclusive
word,
and
there
was
a
request
to
change
the
word
master
to
something
else,
master
in
the
context
of
the
kubernetes
master
suite.
C
C
F
G
I
I
hear
all
y'all,
but
the
truth
of
the
matter.
This
is
one
of
almond
space.
I.
Think
it's
worthwhile
for
us
to
be
here.
I
also
think
that
master
is
not
the
most
accurate
term
here
right.
It
implies
that
there's
like
a
single
thing
that
that's
essentially
the
master
and
you
really
have
a
district
controlling.
B
G
A
Yeah,
we
heard
your
sandwich
order.
This
is
bizarre
No.
So
my
my
my
input
to
this
is
just
that
I
think.
If
it's
a
decision
we
feel
like
we
need
to
revisit.
It
would
be
helpful
to
have
just
at
least
an
estimate
of
the
cost
of
this
of
this
change,
because
it's
not
just
changing
documents
right,
I'm,
pretty
sure
the
word
master
is
referred
to
throughout
the
code.
It
might,
heaven
forbid,
even
be
referenced
in
an
API
or
or
two
which
might
need
to
require
like
a
long
ranging
deprecation
policy.
B
G
G
G
G
And
you
know
my
personal
take
on
it
is
that,
even
though
we're
not
using
the
term
slave,
which
obviously,
like
you
know,
we
kind
of
dodged
that
bullet.
You
know
a
lot
of
folks
that
sort
of
brings
up
those
connotations
and
so
I
don't
think
it's
totally
invalid
to
actually
sort
of
have
concerns
here.
It's.
A
D
B
D
D
A
H
So
we
can
actually
write
blog
posts
about
any
one
of
these
values
at
some
point
later,
to
explain
more,
but
values
should
be
really
tight,
really
strategic,
really
high-level,
so
I've
got
two
revisions
that
are
still
open
on.
Distribution
is
better
than
centralization
and
community
of
a
product
or
company
the
other
three.
If
you
guys
are
good
with
them,
then
we
can
just
leave
them
as
they
are.
H
H
Is
better
than
centralization?
The
scale
of
the
kubernetes
project
is
only
viable
through
high
trust
and
high
visibility.
Distribution
of
work,
which
includes
delegation
of
authority,
decision-making,
technical
design,
code
ownership
and
documentation
distributed
asynchronous
ownership,
collaboration,
communication
and
decision-making
are
the
cornerstones
of
our
worldwide
community.
H
H
Because
and
that's
what
I
was
that's,
why
I
left
those
is
because
I
was
cutting
out,
two-thirds
of
the
words
community
over
a
product
or
company.
We
are
here
as
a
community.
First,
our
allegiance
is
to
the
intentional
stewardship
of
this
project
for
the
benefit
of
all
its
members
and
kubernetes
users.
Everywhere
we
support
working
together
publicly
publicly
in
with
the
common
goal
of
a
vibrant,
interoperable
ecosystem,
providing
an
excellent
experience
for
our
users.
H
G
H
H
H
A
C
C
G
A
C
G
A
I'll
definitely
point
out
that
I
haven't
gone
through
and
reviewed
this
and
that
so
maybe
my
question
is
answered
there,
but
nobody
who
was
working
on
this
was
present
at
the
community
meeting
when
I
announced
a
sig
leadership
change,
and
so
people
were
wondering
like
what's
going
on
with
how
people
change
sig
leads,
and
so
I
talked
about
this
briefly.
I
just
mentioned
that
there
was
a
survey
out
and
that
what
was
coming
was
going
to
be
more
of
a
choose.
A
Your
own
sig
adventure,
it's
type
of
like
best
practices,
did
I
miss
characterize
this
document,
or
is
that
the
intent
of
this
that,
like
not
that,
once
this
is
released
like
every
citizen,
need
to
go
immediately
reconcile
how
they're
running
with
this
document?
This
is
more
like
a
suggestion
for
how
you
could
run
your
sig
if
you
so
choose.
If.
A
C
G
I
think
there
might
be
a
companion
and
hopefully
I'm,
not
gonna
freak
Phil
I
think
there
might
be
a
companion
document
here
in
terms
of
this
is
what
the
project
expects
from
SIG's,
and
we
should
outline
that
and
then
it's
up
to
SIG's
to
be
able
to
actually
fulfill
that
this
document
is
a
suggestion
or
sort
of
a
starting
point.
That
sieves
can
then
go
ahead
and
and
take
and
build
upon
and
modify
I.
C
Yeah
we
we
do
have
a
pre-existing
doc
that
covers
a
little
bit
of
expectations
of
six
it'll,
be
good
to
expand
to
include
some
of
these
other
things
like.
We
expect
there
to
be
a
process
for
replacing
weeds
or
something
like
that.
That's
kind
of
the
approach
this
seems
you
have
taken
as
well,
where
there
are
the
graduation
criteria
that
specified.
We
expect
projects
to
meet
these
criteria
like
you
must
have
the
code
of
conduct.
C
A
E
I
had
my
hand
this
way
the
I
was.
There
are
parts
of
that
document
that
call
out
a
set
of
processes
and
responsibilities
that
I
don't
know
if
it's
even
possible
for
a
volunteer
army
to
fulfill
and
I
called
that
out
in
part
of
the
review
and
I
think.
Maybe
we
can
expand
a
review
next
time
because
it's
very
difficult
to
expect
some
parts
of
a
volunteer
army
to
have
on-call
rotations
and
that
type
of
engagement,
when
some
of
these
folks
may
have
other
responsibilities.
E
So
there's
there's
aspects
of
responsibilities
that
I
think
need
to
be
refined,
separate
from
the
roles
and
I.
This
document
kind
of
inflates
in
hits
both
right.
There's
a
and
I
realized
that
certain
roles
should
have
certain
responsibilities,
but
we
need
to
make
sure
that
that
it's
clearly
defined
and
it's
accomplishable
by
all
parties
right,
yeah.
I
C
A
A
H
I
I
C
G
Think
that's
a
great
start
and
I'm
I'm
happy
to
help
and
first
of
all,
I
just
want
to
say
you
put
a
ton
of
work
into
this
man
and
I
really
appreciate
it.
I
think
this
is
this
is
a
huge
step
forward.
I
think
you
know
we
need
to.
We
need
to
keep
on
at
it,
but
like
this
is
definitely
moving
in
the
right
direction.
Yeah
I.
A
Mean
part
of
me
talking
about
this
at
the
community
was
to
like
inform
people
that
you
know
we've
been
doing
great
work
here
and
there
was
general
like
nodding
of
heads.
Let
that
approach
of
making
it
checklist
that
you
can
just
check
off.
You
know
specifying
the
what
not
to
how
was
was
cool
so
like.
If
you
have
something
of
substance
you
want
to
talk
about
tomorrow,
you
can
do
that.
Otherwise
it
sounds
like.
Maybe
we
should
think
about
having
a
broader
discussion
next
week,
I.
G
Do
want
to
say,
I
think
that
we
might
have
something
in
this
sort
of
interface.
That
is
something
along
the
lines
of
have
a
fair,
documented
process
for
picking
sig
leads
right
mode,
be
one
of
those
things
and-
and
we
probably
and
I
think
this
is
a
question
that
we
need
to
struggle
with.
This
is
what
level
of
oversight
do
we
want
the
steering
committee
to
have
do
we
want
to
ratify
for
partners,
and
so
hers
and
those
processes
to
make
to
ensure
that
there
continue
to
be
fair,
just
wait
for
people
to
raise
exceptions.
G
A
A
really
good
question:
I,
don't
know
if
there's
room
in
the
community
meeting
tomorrow,
maybe
asking
about
charter
files.
They
shouldn't
be
a
good
idea,
because
I'm,
assuming
the
way
to
enforce
this
going
forward,
will
be
to
ask
that
by
some
certain
deadline,
all
sakes
have
charters
and
those
charters
must
spell
out
these
things.
J
Yeah
I
guess
I,
look
at
this
kind
of
with
Tim's
point
of
like
not
all
SIG's
are
equally
sized
and
then,
if
not
all
SIG's
can
meet
the
responsibilities
that
we
want
them
to
meet
back
to
the
project,
then,
like
some
of
those
discussions
will
be
difficult
to
say,
maybe
we
should
collapse
some
SIG's
together
or
right,
but
I
will
look
at
that
and
then,
like
no
I,
just
think
we
should
start
there.
To
be
honest,
we
just.
A
J
H
G
A
A
A
Okay,
next
up
resolving
that
disconnect
between
code
organization
and
owners,
so
I
rolled
out
an
initial
implementation
and
a
pull
request
to
the
community
repo,
as
well
as
an
issue
describe
roughly
what
we
think
some
projects
are
the
way
we
want
them
to
be
that
way.
I
got
a
smattering
of
feedback
from
some
people
in
the
community.
I
didn't
ask
the
steering
committee
for
a
more
concrete
feedback.
So
the
question
is:
is
this
good
enough
to
roll
out
now
and
how
do
we
roll
it
out?
A
You
know
we
could
merge
the
PR
as
is
and
then
iterate
on
it,
but
having
if
I
were
a
sig,
lead
I.
Think
my
SIG's
read
me
change.
How
from
underneath
of
me
would
seem
a
little
weird,
especially
for
some
sakes.
Who's
read
me
becomes
like
a
lot
less
readable
or
concise.
Would
like
API
machinery
as
ton
of
stuff
listed
in
there
thing
also
it
might
come
across
as
being
voluntold
that
suddenly
you
own
all
these
sub
projects,
when
maybe
you
didn't
necessarily
have
any
input
into
this.
A
C
I
think
I'm
in
favor
of
doing
both
of
those
things
like
saying
that
this
is
not
final,
but
also
explaining
what
we're
doing
and
asking
for
input
we
could
send
email
to
the
sig
leads
if
that
hasn't
already
done
and
asked
them
to
communicate
to
the
relevant
people
and
their
SIG's.
Take
a
look.
Okay,
I,
don't
think,
there's
really
any
great
guillotines
and
notifications.
C
Don't
work
very
well
anyway,
especially
with
the
fader
bot,
pinging
everything
but
yeah
between
the
cichlids
Cabernets
dev
and
the
community
meeting
I
think
that's
a
reasonable
number
set
of
places
that
should
reach
most
people
and
long
reach
everybody,
or
that
you
know
it's
impossible
to
reach
everybody.
Okay,.
C
A
C
A
Is
why
I
specifically
have
made
sure
I,
just
in
focusing
on
just
this
drama
in
like
human,
readable
and
also
machine
consumable
implementation
before
I
start
charting
it
over
all
the
repositories?
So
what
I
could
use
your
help
with
Brian
or
somebody's
help
with
is
getting
a
list
of
the
sub
projects
out
of
Brian's
head?
So.
C
C
A
Just
add
it
there
or
if
you
want
to
work
offline
and
put
together
like
a
Google
Doc
or
something
that
we
can
then
PR
into
that
after
we've
presented
to
the
community,
whatever
just
like
I
I'm,
taking
a
best
guess
at
single
repo
things.
What
I
lack
is
the
context
for
multi
repo
or
multi
package
or
multi
directory
sub
projects.
Okay,.
C
A
Ok,
so
my
hope
is
to
I
will
present
about
this
at
the
community
meeting
tomorrow,
I'll
get
an
email
out
to
the
leads
and
later
today
and
lazy
consensus
to
get
that
pull
request
merged
by
next
week,
and
then
this
will
spill
over
into
next
month.
As
far
as
what
our
sprint
is
and
I
plan
on
starting
to
write,
some
automation
to
consume
this,
to
make
sure,
are
those
owners
files
even
present
start
talking
about
the
adding
the
sub-project
and
sig
fields
and
owner
fields
and
stuff
to
owners
files
after
I
talk
with
Brian
offline.
A
The
other
thing
I
could
use
Brian's
help
with
or
I
can
take
a
pass
at
that
I
need,
maybe
Brian
to
look
at
is
merging
the
maintainer
and
owner
role
in
the
community
membership
ladder,
because
I'm
not
sure
whether
it's
emerging
up
or
emerging
down.
As
far
as
some
of
the
requirements
and
duties
go,
it's.
C
A
F
Went
through
and
I
addressed
all
comments
unless
things
have
been
added
since
then,
I
wanted
to
go
through
one
more
time
and
given
the
given
the
fact
that
the
comments
were
addressed,
see
if
there's
any
other
concerns
or
if
we
can
socialize
at
communities,
community
or
kerbin
a
stove,
because
the
next
step
I
was
going
to
take
was
going
to
be
to
sell
I.
It.
F
J
F
J
This
is
Derek.
I
made
a
number
of
comments
explicitly
with
that
concern
like
for
six
months,
eight
projects
I
see
little
motivation
for
folks
to
want
to
go
work
on
that
project.
It
there,
for
example,
that
they
can't
create
a
v1
image
and
publish
it
to
a
you
know,
container
registry
somewhere
like
and
to
me
and
like
one
of
the
things
that
we
expected,
that
of
incubators
was
that
they
could
frequently
demonstrate
releases
and
tag
them
and
like
people
could
start
to
utilize
them.
J
I
feel
like
the
six
sponsored
repo
works
should
also
allow
people
to
frequently
tag
their
repo
as
a
version
release
and
be
able
to
push
images
for
their
efforts
somewhere
and
whether
or
not
they
are
officially
blessed
up
into
a
corker
when
I
was
released,
is
like
a
disjoint
issue
to
me,
but
I.
Don't
know
why
I
don't
know
why
the
GA
terminology
is
getting
coupled
with
like
from
an
end
user.
Like
a
is
there
an
image,
that's
built
with
this
release,
all.
F
F
Maybe
the
meta
question
for
the
steering
committee
is:
do
we
believe
that
we
want
to
have
a
kubernetes
project
level,
a
notion
of
what
GA
means
and
if
we
do
that,
I
believe
that
we
need
this
mechanism
force
consistency
for
what
GA
means.
If
we
don't,
then
it
doesn't
matter,
but
I
kind
of
feel
like
we
should
have
a
consistent
notion
of
what
GA
means,
and
that
means
deprecation
policy
and
everything
else
like
that.
We.
C
F
C
So
I,
so
what
I
was
thinking
about
as
I
commented
on
January
10th
and
you
responded
that
it
was
discussed
when
I
was
out
and
the
decision
was
things
that
anything
in
a
cover
days
really
should
be
in
core.
So
I
guess
I
should
have
responded
to
that
comment
because
I
didn't
understand
how
the
the
release
nough
student
being
in
core
didn't
seem
like
it
got
folded
back
into
their
criteria.
It's
not
any
bulleted
list.
F
C
Guess
my
higher-level
feedback
on
this
whole
thing
was
I,
I,
guess
two
things
one
is
in
November.
We
had
agreed
as
an
interim
measure
to
unblock
SIG's
by
allowing
them
to
go
to
Sagarika,
texture
and
just
say:
hey
can
I
have
a
repo
and
I
got
another
request
for
a
few
repos
today
that
I
said
I
can
discuss
tomorrow
and
the
other
is
I
think
it's
better
to
convey
our
goal
in
terms
of
we
want
to
divide
up
the
repos
into
these
three
categories,
and
these
are
the
reasons.
C
But
there
are
a
lot
of
implementation
details
to
to
work
out
like
the
sig
contributor
experience.
Folks
have
provided
feedback,
saying
hey,
we
don't
know
how
much
tooling
this
you're
going
to
require,
or
if
it's
actually
easier
to
put
more
repos
into
an
Oregon
build
tooling
for
that,
as
opposed
to
having
30
orgs
so
I'd
just
like
to
decouple
sort
of
the
the
goals
and
the
directional
aspect
of
we're.
Gonna
have
these
three
kinds
of
repos
and
have
some
sort
of
interim
process
ton
block
SIG's
and
should.
F
F
I
would
just
say
that
so
I
would
just
say:
there's
three
kinds
of
repositories:
there's
associated
repositories,
there's
sig
sponsored
repositories
and
there's
corresponds
to
hers
and
I'll
strike
all
of
the
naming
stuff,
and
all
of
that
that's
you
know
basically
I'll
strike
anything.
It
is
vaguely
controversial
and
and
say
we
expect
more
consistency,
TBD
yeah.
E
F
F
G
I
there
you
make
a
suggestion
that
if
we
do
do
something
in
the
interim
like
moving
stuff
out
of
the
kubernetes,
org
is
gonna,
be
incredibly
fraught
and
painful
for
a
lot
of
folks,
no
I'm
not
suggesting
we
change
the
status
quo
at
all.
If
we,
let
somebody
sort
of
say,
hey,
create
a
repo
in
kubernetes
now
and
then,
like
a
month
from
now
we're
like.
Oh,
you
need
to
move
that
repo
out
into
some
sort
of
sig
specific
thing.
I.
F
G
A
The
owner
of
a
project-
that's
lived
in
curators
incubator
for
over
12
months,
I
have
met
all
of
the
graduation
criteria.
What
does
this
proposal
do
for
me?
There's
a
fact
at
the
bottom.
That
says
exactly
what
the
answer
is.
It
says
it
does
nothing
to
me.
That's
going
to
be
frustrating
to
me
if
I've
been
waiting
for
a
long
time
with
the
suggestion
that
this
is
going
to
answer
graduation
yeah.
F
F
A
So
in
the
today
interim
world,
if
I
go
to
take
architecture
and
my
project
gets
denied
to
go
into
kubernetes
I'm
still
stuck
back
in
kubernetes
incubator,
no,
you
can
go
to
a
cig
and
get
a
sick,
dispensary
buddy.
We're
saying
we
don't
know
where
six
can
create
the
repos,
so
we're
just
gonna
elastics
to
create
reposing,
kubernetes,
incubator.
Well,.
F
F
It's
not
true.
Actually
right,
I
mean
the
way
that
you
do
this
with
a
CLA
bought
the
way
that
the
honestly,
the
way
that
the
Microsoft
CLA
bought
works
is
that
the
bot
is
added
as
an
opener
and
the
bot
can
find
all
projects
that
it's
an
owner
of
from
the
github
API.
And
then
those
are
the
law
as
it
goes
and
scans,
but.
K
Concrete
place
this,
could
we
create
a
kubernetes
cigs
organization
that
follows
these
rules
and
then,
if
we
have
to
move
it
out
of
there,
we
can
because
I
mean
we
can
get
the
bottom
of
one
more
word:
that's
not
the
problem.
It's
the
fan
out
of
works,
that's
the
problem.
If
we
create
kubernetes
eggs
and
the
only
way
you
get
in
there
is
if
the
Stig
owned
you,
we
don't
necessarily.
G
G
G
F
J
Just
want
to
make
sure
I
understand
the
process
here
there
so
like
as
a
cig,
lead
who's.
Also,
a
steering
committee
member
that
wants
to
get
a
new
repo
for
a
signal
use
case.
Did
you
know
dotto
repair.
Do
I
should
I
anticipate
at
the
outcome
of
this
that
we
will
have
a
kubernetes
SIG's
organization.
My
new
repo
will
go
there,
I
go
to
cig
architecture
to
get
agreement
on
the
use
case
and
repo,
and
that's
that's
no.
F
J
F
J
F
J
K
J
F
And
I
think,
let's,
let's
split
off
the
GA
discussion,
because
I
sort
of
agree
that
it's
orthogonal
and
say
like
looks
that's
a
different
discussion
about
what
it
means
to
be
GA
and
and
we'll
decide
whether
we
think
there's
a
community
wide
standard
for
GA
or
not
and
we'll
just
apply
that
separately.
So.
G
C
A
F
A
H
G
A
H
A
H
And
Cohn
has
asked
and
not
dead.
Actually,
this
time
it
was
Chris
and
a
chick
has
asked,
he
really
really
really
wants
us
to
decide
that
we
want
to
graduate
we've
met
all
the
criteria.
He
doesn't
want
to
hurt
anyone
else.
First,
he
wants
us
to
graduate
first
and
or
as
a
group
together
with
a
couple
of
projects.
So
are
we
okay
being
graduated.
D
C
C
However,
the
size
of
the
project
makes
it
really
challenging.
So
I
think
you
know
it's
not
gonna
be
better
than
it
is
I.
We
do
have
a
steering
committee
that
was
elected.
We
are
moving
forward
if
not
as
fast
as
everyone
would
like
on
on
some
of
the
governance
issues
we
do
define.
You
know,
have
a
definition
of
number
of
standing.
We
have
a
defined
contributor
letters
so
yeah
and
we
need
the
basic
basic
criteria
and
amusingly
some
other
projects
are
mirroring
some
of
the
things
that
we
do
verbatim.
C
Some
of
the
things
have
been
copied
into
like
fluency
governance
talks,
and
things
like
that.
So
we
are
setting
a
precedent
whether
we
want
to
or
not
little
do.
They
know
we're
making
it
up
as
we
go
along
yeah
and
you
know
one
good
ones
recorded
one
thing:
one
thing
I'm
pushing
in
scene
CF
as
well,
is
to
make
some
marketing
changes.
C
Yes,
is
there
any
concrete
downside
to
graduating
that
we
should
be
aware
of
no
there's.
There's
not
really
like
the
governance
is
intended
to
be
very
light
touch,
and
you
know
the
requirements
really
have
been
crafted
around
kubernetes
and
and
the
expectations
about
how
it
should
operate.
I
mean
even
there's,
I
did
I
would
say
it's
maybe
even
gone
overboard
where
some
services
and
help
and
contact
that
have
been
offered
to
some
of
the
smaller
projects
we
want,
even
aware
of
because
they
just
assumed
that
we
didn't
want
to
be
bothered
by
that.
C
So
I
think
there's
no
there's
no
downside
for
us
and
it's
all.
It
would
be
good
for
CNCs
and
for
the
other,
to
to
move
forward
with
this,
and
that's
that's
my
current
feeling
I'm
my
greatest
concerns
that
had
been
addressed
or
no
longer
relevant
cool
I
grew
up
and
by
the
way,
I
do
plan
to
run
again
for
the
TOC
in
March.
So
you
know
there
would
still
be
someone
familiar
with
kubernetes
on
the
QC.
If
I
get
reelected.
D
H
K
C
J
C
C
What
the
TSE
does
is
they
actually
do
it
through
email
and
has
multiple
benefits?
One
is
that
has
it
can
be
answered,
asynchronously,
not
everybody
can
necessarily
attend
the
the
call
or
whatever,
and
it
has
a
permanent
record
that
is
less
easily
changed
like
yeah.
Permissions
are
such
that
people
can
go
back
and
edit
things
pretty
easily
and
do.
K
K
J
C
C
C
J
A
Okay,
we
have
one
minute
left
and
we
also
don't
have
a
proposed
bin
for
next
month,
which
I
completely
forgot
and
at
the
beginning
of
this
so
I'm
going
to
carry
over
everything
that
we're
working
on
that
isn't
close
to
assume.
That's
part
of
our
current
sprint
can
put
out
a
pull
request
to
update
this
backlog
file
and
we
can
banter
about
whether
or
not
we've
captured
the
appropriate
scope
of
Sprint's
for
February,
Sarah
and
I
apologize.
We
didn't
have
time
to
get
to
your
items.
A
You
provide
feedback
to
Paris
running
the
Mitch
alert
program,
lead
doubly
so
and
Phil.
Should
we
have
a
weekly
update
at
the
community
meeting
I
think
we
should
have
an
update
at
the
same
cadence
that
we
have
this
meeting,
certainly
because
this
seems
to
be
there's
something
to
talk
about
I
plan
on
starting
it
off
tomorrow,
and
if
there
are
other
things
you
want
to
talk
about,
I'm
feel
free
to
add
at
the
community
meeting
notes.
Okay,.