►
Description
Kubernetes Public Steering Committee Meeting for 20220606
A
Soon's
been
weird
all
right,
we
are
recording.
This
is
a
kubernetes
community
meeting.
We
adhere
to
our
code
of
conduct.
This
june
6
2022
meeting
will
end
up
on
youtube.
So
just
please
be
mindful
of
going
to
come
back
during
the
meeting.
I'm
the
boson
today,
first
time
newbie
being
imposing
and
who
do
we
have?
Who
can
help
on
notes?
Does
anybody
want
to
formally
volunteer
then
okay
cool,
we
do
have
a
quorum.
We've
got
a
couple
folks
from
community
welcome
ryan
mahav
nice
to
see
you.
A
If
you
have
anything
that
you
would
like
to
discuss.
If
you
want
to
drop
it
in
towards
the
end
of
the
topic
list,
we
will
make
sure
we
get
a
time.
I
think
we
have
a
relatively
light
agenda
today,
so
there
shouldn't
be
any
issues
at
all
there
and
first
up
in
the
normal
set
of
things,
is
csf
updates?
So
there
was
quite
a
bit
of
discussion
around
code
of
conduct,
topics
at
kubecon
and
we've
got
some
follow-on
actions
there
that
we
are
starting
to
take.
B
A
Yeah,
it
may
be
useful
for
the
recording
or
anybody
who
follows
along
later
there.
There
was
a
public
incident
that
people
may
have
seen
have
awareness
of,
but
this
is,
I
think
we
can
treat
this
as
distinct
from
that.
Where
there's
a
lot
of
discussion
happening
beyond
just
the
kubernetes
project,
where
we
have
a
robust
process,
that's
been
operating
successfully
for
quite
a
while.
There's
a
growing
need,
that's
presenting
itself
for
something
that's
across
the
ecosystem,
beyond
just
individual
projects
and
at
kubecon
the
linked
session.
A
There
was
kind
of
a
birds
of
a
feather
set
of
subject
matter.
Experts
who
are
passionate
about
the
space
and
want
to
step
to
this
community
need
to
make
sure
that
we
have
something
sustainable
and
equitable,
and
the
details
are
tbd.
What
actually
gets
coalesced
out
of
that,
but
there's
at
least
a
positive
start
there,
and
that
there's
a
coalition
of
the
willing,
I
think,
performing
to
take
some
action
here.
So
that's
for
everybody,
following
along
in
the
the
history
and
the
recording
or
whatever
that's
kind
of
the
context
right.
B
B
You
know
how
it
works
with
a
special
issues
committee
or
something
like
that.
We
are
trying
to
do
something
which
is
going
to
be
like
a
mixture
of
things
from
both
the
toc
and
the
gv
and
trying
to
get
to
the
point
where
there
is
going
to
be
a
bunch
of
people
and
they're
going
to
decide
how
things
are
going
to
work
in
the
future.
A
C
A
A
So
one
other
cncf
update
that
I
had
was:
there
is
a
sort
of
a
board
town
hall
meeting
this
week
on
the
calendar.
That's
cross
project
thing
so
we'll
be
representing
the
project
there.
I
don't
know
how
this
has
happened
or
if
it's
happened
in
the
past
since
I'm
newer
on
our
stream
committee.
Is
this
like
an
annual
thing,
or
is
this
the
first
go-around
on
it?
This.
E
A
F
A
A
C
C
E
C
C
A
A
Okay,
then
general
topics
the
annual
report.
There
should
be
a
yay
there.
It's
out,
I
dropped
a
couple
of
links
into
the
the
report
and
the
blog
post.
We
have
gotten
a
little
bit
of
nice
commentary
around
it
and
I
saw
over
the
weekend
also
some
discussion
on
twitter
around
help
wanted
things.
So
it
looks
like
it
is
getting
eyeballs
and
getting
some
thought
and
consideration
and
conversation.
So
that's
a
positive.
D
E
Yeah
I
feel
like
if,
if
I'm
not
here,
I
don't
see
y'all
doing
this
like,
I
think
it
would
just.
I
think
it
would
just
go
away
and
that's
not
sustainable,
like
that
means
that
there's
one
person
that's
holding
it
up
and
then
we're
all
elected
into
these
roles.
So
then,
that
that
what
it's
gonna
die
on
the
vine
with
the
next
with
the
next
crew,
so
I
feel
like,
unless
we
figure
out
how
to
automate
this
and
how
to
and
how
to
have
liaisons
like
pull
the
things
that
are
needed
from
groups.
A
A
A
Is
that
the
issue?
Oh
no?
Okay!
I
wasn't
sure
if
you
were
facing
an
issue
on
that
there
were
a
couple
of
questions
that
had
come
up
in
the
prior
one,
so
I
will
work
on
getting
some
issues
that
are
closed
out.
Hopefully
I
think
the
the
discussion
around
code
of
conduct
at
cubecom
helps
on
the
discussions
that
we're
having
around
how
we
do
elections
there
to
to
make
sure
that
our
process
is
clean
and
tidy
and
understood
by
the
community
so
I'll
this
month
get
some
things
into
github.
On
that
front,.
A
Kubecon
so
dems
mentioned
the
the
kova
test
reports,
1.7
percent
of
attendance.
One
of
the
interesting
things
I
heard
after
was
that
we
hardly
got
lunch
on
friday
because
a
quarter
of
the
site
staff
had
tested
positive
by
the
end
of
the
week
and
were
unable
to
work.
So
it
was
definitely
a
big
spreader
of
of
covid,
but
it
also
seemed
to
have
gone
off
pretty
darn
smoothly.
All
things
considered
of
7
500
people
really
good
conversations
in
the
hallway
track
and
in
sessions
I
was,
I
was
pleasantly
surprised.
A
H
D
A
D
There
was
a
lot
of
good
conversations
regarding
sustainability
and
reliability
at
the
unconference
session.
There
were
three
big
take
away
follow-up
actions
from
that
one
is.
We
want
to
start
tracking
bugs
so
items
that
are
tagged
as
triage,
accepted
and
kind
bug,
and
also
to
map
that
to
per
sig
and
like
area
component.
D
More
groups
want
to
formally
get
going
on
mentoring
programs
to
get
people
into
needed
areas,
which
was
nice,
we'll
see
how
the
actual
follow-up
on
that
happens,
and
then
the
last
thing
was
implementing.
I
think
it
was
code
coverage
reporting
to
try
and
get
an
idea
of
where
there
are
uncovered
areas
essentially.
D
B
A
One
of
the
reasons
the
annual
report
process
is
so
important,
though,
like
we
have
had
a
lot
of
turnover
and
sustainability
like
those
are
a
couple
of
very
specific
technical
points
on
things
to
do
with
sustainability,
but
it
was
coming
up
in
pretty
much
every
talk.
I
attended
some
aspect
of
sustainability
and
the
human
aspect
and
turnover
and
loss
of
institutional
memory
or
loss
of
bandwidth
or
minimal
bandwidth
and
how
to
how
to
make
sure
that
we're
keeping
the
lights
on
was
a
really
common
topic
across
the
week.
A
D
D
C
D
D
E
E
This
has
been
so
difficult
for
me
over
the
last
five
years.
Y'all
like
this
is
probably
one
of
the
hardest
elements
of
my
job,
which
is
the
wildest,
because
we
have
some
of
it
figured
out
so
liaisons,
please
ping
your
crews
and
ask
them
what
they're
doing
about
mentoring
and
not
junior
folks,
either
like
how
are
they
out?
How?
What
is
the
outreach
like
for
people
to
get
to
reviewer
like?
Are
they
do
they
have?
E
E
E
That
says
here's
areas
where
we
need
your
help:
here's
the
here's,
the
maintainers
and
their
times
that
they're
available,
like
that's
the
kind
of
like
outreach
that
we
need
more
of
all
of
the
time
like
we
get
really
good
responses.
When
we
ask
people
do
we
get
flakes
absolutely
like
that's
the
name
of
the
open
source
game
at
this
point,
and
we
should
already
include
the
fact
that
half
of
the
people
that
said
they're
going
to
help
are
going
to
go
away
in
a
week
like
that's
the.
E
E
E
One-On-One
doesn't
scale
like
it
doesn't
like
as
much
as
much
like
as
I
love
preaching
the
good
word
of
one-on-one
mentorship.
It
does
not
scale
for
open
source
projects
period.
It
doesn't
so
that's.
Why,
like
I
think
any
time
I
say
the
word
mentoring
to
maintainers.
They
like
retreat
in
a
cave
because
they
think
that
I'm
gonna
take
their
time
for
one-on-one
individuals
and
like
that's,
not
how
I
don't
want
to
do
that
either,
like
I'm
building
programs
that
I
think
are
scalable
and
things
that
I
can
even
do
myself.
E
So
I
think
that
we
as
a
crew
here
need
to
reach
out
to
some
of
these
leads
and
tell
them
to
please
participate
in
some
of
these
groups
like
even
when
we
ran
the
maintainer
survey.
Like
one
of
the
questions
was
like.
Does
your
organization
support
you
maintain
earnings,
mentoring,
60
said
yes,
so
where
are
you
60
60?
F
A
There's
a
thread
on.
I
think
this
was
on
twitter
over
the
weekend
where
somebody
was
talking
about.
We,
we
talked
about
code
and
non-code
contributions.
One
of
the
the
underserved
areas,
maybe
of
non-code,
is
like
again
get
harping
back.
I
expect
steven
to
unmute
when
I
say
like
management
and
project
management
and
that
there
is
a
necessary
skill
there
and,
as
you
become
a
maintainer
or
something
that
is
part
of
what
tends
to
be
on
your
plate,
you
have
to
build
a
team
around
yourself
to
make
things
sustainable.
A
C
Yeah,
no,
I
think
I
mean
I'm
I'm
also
sensitive
to
like
the
flip
side
of
this,
and
I
think
all
of
us
have
been
part
of
some
effort
in
some
way
shape
or
form
at
some
point
where
we've
had
to
kind
of
drag
something
along.
That
was
not
working
and-
and
I
think,
there's
a
there's
a
bit
of
there's
a
bit
of
stress.
That's
involved
with
that
too,
so
like
finding
how
to
balance
the
yes
come
and
do
this,
but
like
is
there
a
way
that
we
can.
C
C
A
All
right
moving
on,
I
noticed,
as
I
was
setting
up
the
agenda
link
for
today,
that
we
haven't
retroactively
linked
our
prior
recording,
so
all
on
after
today's
cloud
recording
I'll
get
an
email.
I
think
saying
that
I
recorded
it
to
the
cloud
I'll
drop,
that
link
in
and
pull
in
the
other
ones
for
the
past
couple
meetings
as
well.
Just
so
it's
up
to
date.
B
A
A
All
right,
paris,
thank
you
for
noting.
I
have
a
code
of
conduct
in
my
head
because
it
comes
first
in
the
lineup,
but
we're
also
about
to
get
into
overall
steering
election,
and
I
think
it
was
dems
typing
in
there
dennis
jordan
and
bob
all
have
terms
ending.
So
we
we
here
also
have
quite
a
turnover
coming
as
well
and
we'll
need
to
get
set
up
with
election
officers.
D
C
D
C
D
A
Again,
thinking
about
sustainability,
I
think,
does
it
say
really
an
inclusivity.
It's
been
great.
That
josh
has
led
this
effort
for
a
long
time,
but
also
that
can
preclude
him
from
participating
as
a
candidate.
So
I
think
we
should
maybe
even
start
out
with
checking
where
he
wants
to
be
on
that
in
case
he's
interested
in
running,
so
that
he
can
be
eligible
versus
thinking
that
we're
just
asking
him
to
run
the
election
again,
which
excludes
him
from
potentially
participating
as.
B
D
B
A
America
we
had
an
election,
retro
last
fall
and
there
were
a
variety
of
code
changes
or
infosec
things
with
the
new
system.
That
need
is
sorted
out
a
bit,
so
we
should
also
check
on
that,
because
we
have
some
time
to
tie
it
off
if
there
are
outstanding
issues
there.
I
do
believe
that
has
been
worked
on.
E
F
A
A
A
F
E
C
So
I
think,
there's
also
a
people
being
burnt
out
thing
related
to
this.
Where
related
to
the
the
I
mean
you
know
similar
to
the
the
election
check-ins,
if
we
set
some
sort
of
timeline
for
a
monthly
check-in
with
sigs
instead
right,
whether
it's
like
the
you
know,
like
the
same,
the
the
the
leads
chairs
meeting
right,
where
it's
like
hey
take.
You
know,
use
this
as
some
time
to
think
about
what
your
sig
has
worked
on
this
month
right
and
then,
by
the
time
they
get
to
the
annual
report.
C
D
C
And
I
mean
if
you
you
take
this
sorry,
I
mean
if,
if
you
take
this
as
like,
if
you
look
at
the
you
know,
enhancement
collection
as
well
right,
that's
that's!
The
kind
of
thing
that
you
know
preparing
your
caps
for
the
next
season
is
the
thing
that
can
happen
during
code
or
can
should
happen
during
code
test.
Freeze,
thaw
right,
that's
also
a
good
time
to
as
you're
looking
at,
essentially
what
your
sig's
roadmap
is
being
able
to
put
together
that
content
too.
C
So
I
think
you
know
I
I
think
one
of
the
problems
that
we've
seen
is
that
you
you
get
so
caught
up
in
executing
the
release
right
that
you're
like
okay.
Well
now
I
have
a
break,
and
I'm
like
okay.
Well
now,
the
next
cube
con
is
starting
or
the
next
election
is
starting
or
the
next
thing
is
starting.
The
next
release
is
starting,
but
that
is
that
that's
supposed
to
be
the
right
time
to.
F
A
I
think
we
happen
to,
coincidentally,
have
a
nice
intersection
in
the
past
between
the
quarterly
release
cycle
and
the
quarterly
updates
in
the
community
meeting,
though
having
to
do
the
sig
update,
there
was
also
considered
really
onerous
and
it
was.
It
was
something
that
had
to
be
pulled
together
to
present,
at
least
from
from
some
of
the
folks
in
the
cigs,
but
it
also
gave
a
little
better
frequency.
It
brought
the
documentation
closer
to
when
the
thing
happened
versus
getting
to
a
year
later
and
trying
to
coalesce
things,
but
it
had
the
same.
A
E
It
was
monthly
and
like
because,
like
we,
though,
the
governance
requirement
said
quarterly,
but
that's
like
what
would
happen
is
people
would
cancel
and
then
we'd
have
to
fill
in
the
slot,
and
then
some
people
went
in
the
beginning
of
the
release
and
none
of
the
information
was
like
the
same
at
the
end
by
the
end
of
the
release,
and
it
was
just,
in
my
opinion,
a
mess
like
I
mean
it
was.
It
was
a
mess
from
the
back
back
of
the
house
like.
A
G
C
D
E
E
E
So
I
thought
that
was
really
super
helpful
and
I
think
maybe
one
of
our
practices
as
liaisons
as
we
should
just
go
to
their
meetings
and
not
necessarily
dm
them.
I
mean,
obviously,
if
it's
something
very
personnel,
you
know
related
sensitive,
related
stuff
like
that,
then
obviously
dms
are
great,
but
if
we
show
up
at
their
meetings
as
the
liaison
like
I
do,
I
feel
like,
then
we
are
like
a
part
of
their
thing
and
not
necessarily
like
you
know
someone
telling
them
they
have
to
do
something.
C
C
I
I
don't
believe
like
to
tim's
point
yeah
we're
not
gonna,
you
know
and
and
to
your
point
like
yeah,
we're
not
going
to
write
the
thing
for
you,
but
we
should
be
able
to
distribute
the
load
of
you
know
from
contributor
experience
side
of
being
able
to
say
like
here's,
where
all
the
things
are.
Here's
you
know
here.
Here's
the
toolbox
here
you.
G
C
A
Cultural
things,
too,
is
still
working
on
improving
the
culture
around
written,
durable
communications,
whether
it's
on
the
dev
list
or
in
issues
or
in
caps
or
just
meeting
minutes,
and
that
is
an
opportunity
for
new
folks,
perhaps
to
help
on
organizing
or
capturing,
but
where
they
have
a
question
where
they
didn't
understand
something.
They
also
need
the
leads
around
responsive
to
them
being
able
to
pause
and
say:
oh
you're,
probably
not
the
only
person
who
didn't
understand
that.
A
Let
me
kind
of
get
into
a
little
bit
more
detail
on
what
that
is,
and
that
could
then
help
them
bringing
up
their
reviewer
and
improver
rings
by
bringing
people
into
a
little
more
organizational
awareness
on.
What's
going
on
really
this,
I
feel
like
this
process
should
be
easy,
because
it's
just
collecting
existing
artifacts
if
they
exist.
D
D
C
So
I'm
hearing
kept
website,
I'm
hearing
ctl,
which
exists
and
does
have
the
capability
to
do
queries
right
now.
I
also
want
to
address
the
comment
here
from
madov
around.
You
know,
okay,
so
something
I
was
thinking
about
that
echoed
with
bob
and
steven's
point
and
if
every
release
each
sig
could
maybe
give
details
largely
two
folds
one
cap
updates.
This
will
be
available
readily
through
what
we
just
said,
the
data
that
exists
and
two
a
small
and
small
and
minimal
questionnaire.
This
could
be
three
questions.
C
Any
new
sub
projects,
any
leadership,
changes
any
non-cap
efforts
based
on
what
info
was
in
this
year's
annual
reports
and
yeah.
The
the
second
point
that
I
was
going
to
make
with
is
kind
of
to
the
second
point
here,
which
is
that
there's
so
much
happening
that
is
not
captured
in
caps.
Right
caps.
Are
you
know
in
in
terms
of
like
code
content?
C
C
If
caps
are
the
single
one
thing
that
is
used
to
denote
code
policy,
what-have-you
changes-
and
I
think
the
answer
based
on
the
staleness
of
that
issue,
wherever
it
is,
is
that
no
they
aren't
because
people
are
doing
things
a
few
different
ways.
I
think
once
you
fall
out
of,
I
think,
once
you
fall
out
of
core
kubernetes
and
you
fall
out
of
strictly
that
code
range,
then
you
kind
of
open
the
window
up.
C
So
this
is
similar
to
the
code
versus
non-code,
but
it's
also,
like
you,
know,
entry
versus
out
of
tree.
How
do
we
solve
for
the
other
80
of
the
changes
right
that
does?
That
is
going
to
take
some
individual
and
contextualized
like
editorializing
of
what's
happening
in
that
sig?
So
that's.
You
know
one
that
that's
one
component
of
it
and
then
there's
another
of
like
how
can
we
make
it
more
more
clear
that
the
context
for
which
we're
delivering
the
annual
report
is
to
everyone
right
like
is
it?
C
B
So
this
was
interesting
for
me
because
you
know
one
anecdote
from
my
side
here
is
so
in
vmware
we
were
rolling
up
everything
into
like
kubernetes
kubernetes
q
units
right,
like
even
things
in
capi
or
anywhere
else,
that
we
were
doing
some
stuff.
It
was
all
rolled
into
like
kubernetes
right
like
take
the
number
of
people
working
on
kubernetes
like
oh,
we
have
50
people
working
on
kubernetes,
but
in
in
reality
it
was
only
like
five
right.
B
D
As
far
like,
I'm
sorry
when
it
comes
to
like
automating
doing
sort
of
thing,
the
I
still
think
I
know
there's
the
whole
slew
of
work-
that's
not
captured
in
caps
and
and
crosses
release
and
all
that.
But
it's
all
about
reducing
the
amount
of
work
and
toil
that
goes
into
this
so
like.
If
it's
easy
for
people
to
do
that
sort
of
thing,
and
then
they
just
have
to
add
a
couple
sentences
about
the
the
non-kept
work.
E
Yes
and
our
focus
then
could
be
on
the
education
of
the
other
things.
This
is
that's
where
we
want
the
focus,
but
instead
our
focus
is
busy
on
editing
and
formatting
for
40
plus
hours,
and
that's
where
it's
like.
No,
the
automation
isn't
going
to
solve
a
lot
of
the
stuff
that
we're
dealing
with,
but
it
is
going
to
solve
our
time
and
focus
into
the
areas
where
we
need
to
focus
in
so.
J
J
This
is
not
specifically
one
of
them
to
improve
our
generator
and
to
try-
and
at
least
specifically,
for
the
annual
report
process
and
like
the
the
pr
templates
and
that
kind
of
stuff-
it's
mostly
there,
but
there's
still
a
lot
of
things
that
were
just
like
too
complicated
to
do
rapidly.
At
the
end
of
the
year
last
year,
I'd
like
to
collect
together
a
wish
list.
I
can
definitely
like
I
can
do
as
the
person
who's
created
this
generator
a
couple
times.
J
I
think,
at
least
from
my
perspective,
going
back
to
what
a
common
paris
made
at
the
beginning,
like
I
at
least
see
the
value
to
our
annual
report
like
it
continues
to
show
value
to
me
from
my
perspective
and
there's
the
feedback
that
I'm
getting
from
other
folks
around
the
community
and
at
my
organization
they
see
the
value
to
this
report,
but
we
do
need
to
make
it
sustainable
and
I
think
next
year's
opportunity.
This
is
our
second
annual
report.
J
If
we
get
to
three-
and
it's
still
a
slog,
then
maybe
we
do
need
to
reconsider
how
we,
how
we
end
up
doing
it.
But
I'd
like
to
see,
at
least
from
my
perspective,
what
can
we
do
in
the
next
six
months
to
improve
the
the
process
for
everyone
both
for
sig
chairs
and
maintainers
and
and
that
kind
of
stuff,
as
well
as
for
us
that
are
going
through
and
building
the
report
afterwards?.
C
Yeah,
just
really
gonna
sharpen
the
point
on
making
sure
that
we're
highlighting
everything-
that's
not
in
gaps,
because
those
are
the
things
that
are
often
forgotten
their
glue
work.
It's
you
know.
Those
are
several
areas
where
people
already
feel
like
they're,
not
necessarily
recognized
for
their
work.
So
we
need
to
over
rotate
on
making
sure
that
stuff
is
highlighted.
E
E
I
think
I
actually
added
in
the
in
the
github
retro
area,
like
I
think
we
should
really
tailor
our
questions
to
what
exactly
it
is
that
we're
looking
for
at
board
level
like
for
one
of
the
like
one
of
the
questions
should
absolutely
be.
Do
you
have
any
areas
that
have
single
maintainers,
or
maybe
under
10
reviewers,
like
whatever
the
n
number
is?
We
need
to
figure
out
what
that
is,
because
we
bury
the
lead
in
so
many
of
these
areas
still
like
we've
gotten
better
at
it
like.
E
Can
we
continue
to
get
better
at
our
communication?
In
my
opinion,
like
you
know,
this,
isn't
doom
and
gloom
like
this?
I'm.
I
genuinely
think
that
this
report
is
better
than
last
year's
based
on
the
like
the
just
the
feedback
that
I'm
getting
as
well,
but
we're
burying
the
lead
in
so
many
places
and
that
lead
is
what's
going
to
get
us
the
help
and
the
things
that
we
need.
E
So
that
is
a
role,
so
we
can
have
a
steering
member
take
like
pre-prep
right
and
then,
as
we
go
along,
we
each
have
rolled
now
that
now
that
I've
done
this
twice,
I
see
all
of
the
roles
that
we
can
have
and
in
the
actual
annual
report
process
itself,
we
each
get
tasked
out
with
one
theme
one
like
one.
What
have
you
like?
I
tried
to
do
that
at
the
end,
and
by
that
time
we
were
all
so
busy
with
our
other
lives
that
nobody
could
really
get
to
them.
E
So
I
think,
having
roles
for
us
to
prepare
this
would
be
amazing
and
then
the
other
thing
is
sort
of
like
a
shout
out
and
like
midhave,
and
so
many
other
folks
jumped
in
with
the
data
collection
pieces
that
we
needed
that
really
helped
to
unbury.
These
leads.
So
I
just
wanted
to
give
a
shout
out
to
a
lot
of
it.
E
I
I
Was
that
one
was
that
if
you
collect
all
the
data
towards
the
end,
that
is
at
the
end
of
the
year,
things
are
not
going
to
be
as
easy
as
you
think,
and
the
other
is
that
when
they
spend
time
on
collecting
this
data,
they
probably
aren't
going
to
spend
time
on
the
things
that
are
actually
important,
which
is,
in
my
opinion,
at
least
like
the
help
wanted
section.
That's
the
one.
I
It's
not
impossible,
but
it's
like
really
difficult,
sometimes
so
for
now,
even
though
we
aren't
capturing
all
the
data
of
all
the
work,
that's
being
done
outside
of
caps,
maybe
going,
maybe
that
can
be
like
the
north
star
and
for
now
the
goal
can
be.
How
do
we
minimize
missing
out?
How
do
we?
How
do
we
minimize
the
amount
we
miss
out
on
in
the
data
we
capture
and
like
doing
it
per
release,
will
actually
help
minimize?
A
That
was
the
one
thing
that
I
was
going
to
wrap
up
with.
We
need
targeted
point
tools.
Somebody
can
run
a
simple
command
to
get
a
monthly
or
quarterly
or
leastly
update
up
on
a
few
nuggets
of
info,
but
and
that'll
be
helpful
and
that'll
make
it
easier,
but
it
is
always
to
some
extent
going
to
be
toil
because
you
can't
just
trivially
automate
the
generation
anything
aside
from
a
group
of
maybe
a
dozen
people
and
probably
whether
there's
a
pm,
who
largely
writes
the
status
report.
A
I've
never
seen
one
of
these
super
super
automated
that
didn't
just
turn
into
800
pages
of
copy
pasta.
That
was
nonsensical,
so
summary
is
hard
and
but
we'll
keep
working.
I
I
really
do
appreciate
the
comments
along
the
way
last
little
bit
that
we
do
see
value
in
this.
This
isn't
a
discussion
of
like
there
is
no
value
here.
We
shouldn't
be
doing
it,
but
how
do
we
refine
it?