►
Description
The goals for the first meeting:
Introduce teams and individuals wanting to participate
Discuss a framework for participation
Outline some early goals and next steps
A
A
This
is
unfortunately
the
way
we
all
have
to
meet.
Now
it's
forever
think
and
thanks
for
everyone
for
showing
up
I'll
I'll,
kick
it
off
by
just
saying
you
know
this
is
this
is
a
pretty
exciting
thing.
You
know
Ben
and
I.
Had
this
conversation
back,
what
was
it
January,
Ben
and
I?
Think
as
a
journey
goes,
there's
a
lot
of
teams
out
here,
doing
cool
stuff
for
natives,
and
so
it's
I
think
it's
time
for
this
to
be
like
a
formal
part
of
the
project
and
that's
a
I
think
that's
a
good
idea.
A
The
goals
that
I
had
stated
in
the
meaning
just
to
kind
of
put
a
structure
around
it
and
I'll
stop
talking
after
I
say
this
just
so
we
can
get
any
kind
of
input
we
need,
but
I
just
want
to
make
sure
we.
You
know
we
know
the
teams
that
are
going
to
want
to
work
on
this
because
I'm
assuming
I
know
there
are
teams
out
there,
but
I
want
to
just
know
like
write
down
who
who's
working
on
it.
Maybe
get
some
contact
information.
A
A
B
A
C
E
F
A
E
I
G
J
F
Hey
I'm,
Chris
I,
don't
think
I
really
know
any
of
you.
Besides.
The
people
I
work
with
I
work
at
Apple
with
Nate
and
David
Chapple
who's
also
appears
to
be
on
the
line.
We
currently
do
run
a
fair
bit
of
Cassandra
on
top
of
kubernetes
in
production.
Right
now
we
don't
have
a
operator,
it's
been
something
we've
been
looking
into.
We
do
have
some
cases
where
we
use
some
customer
resource
definitions
to
achieve
it,
but
yeah
variation.
This
kind
of
stuff,
mm-hmm.
A
K
A
A
Okay,
very
good.
Thank
you
all
right,
so
this
is,
and
thank
you
everyone
for
showing
up.
This
is
probably
a
little
more.
This
is
what
I'm
really
not
sure
about
and
Nate
and
been
especially
Nate
from
the
project
standpoint,
this
participation
of
like
how
we
this
framework
of
participation,
you
know
I,
think
we're
gonna
have
a
lot
of
people
that
want
to
participate,
and
how
is
that
gonna
happen?
You
know.
Is
it
another
repo
I.
D
Think
this
is
opening
line.
It's
it's
best
to
do
this
type
of
thing
as
a
documentation
where
initially
is
like
part
like
a
container
improvement
process,
type
thing,
so
everybody
can
come
and
put
some
comments
on
it
and
input
at
leisure
or
along
in
coordination
with
the
issue.
This
sort
of
points
to
the
dock,
I
think
is
the
best
thing
to
do
like
similar
to
what
we
do
with
sidecar.
Having
issue
have
the
doc
discuss
it?
D
You
know
bring
stuff
to
the
mailing
list
if
it
needs
to,
but
like
it
just
needs
to
happen
in
public.
Like
that
and
the
more
of
these
calls
we
can
do
to
sort
of
get
people
on
the
same
page,
the
better,
there's
nothing
against
that
so
long
as
we
don't
make
decisions
here,
we
take
stuff
back
to
list
type
of
thing,
sure
and.
A
I
am
recording
all
of
these,
and
I
have
no
problem
doing
this
like
every
couple
of
weeks
or
every
week,
whatever
we
feel
like
the
pace
needs
to
be,
my
zoom
account
is
cheap,
but
posting
the
recording
up,
I
think
it's
helpful.
Let
me
ask
this
too:
is
the
this
time
frame
was
supposed
to
be
like
West
Coast,
u.s.
Asia
friendly
is
that
true
did
I
do
a
good
job
of
that.
A
D
Idea
or
not
I
think
it's
it's
the
only
way
to
get
everybody
in
at
the
same,
to
be
able
to
participate
and
people
who
want
to
go
to
both
probably
should
because
the
people
who
have
the
most
production
experience
I've
seen
so
far,
Patrick
correct
me
if
I'm
wrong
is
all
the
guys
at
orange
France
yeah
because
and
the
folks
over
there.
Cuz
they've
been
working
hard
on
this
for
like
two
or
three
years
now,
and
they
have
their
open-source
operator
out
there.
D
A
D
Guess
both
I
I,
don't
there's
not
like
a
established
way
to
do
this
so
much,
particularly
when
it's
not
clear
if
we're
going
to
take.
This
is
like
a
donation
from
somebody
if
we're
gonna
stake
roll
something
new
or
what,
but
it's
it's
a
good
place
to
start
sort
of
get
requirements
down
and
who
wants
to
do
what
and
like
what
direction.
A
B
You
know
that
way.
It
means
that
we
turnout
been
a
whole
bunch
of
time
trying
to
boil
the
ocean
and
the
CEP
being
like.
Well,
what
do
we
do
if
we
start
from
scratch?
What
if
we
do
it's?
If
it's
a
donation-
and
you
know
we
kind
of
you-
know
limit
the
possibilities
to
what's.
Actually,
you
know
possible
based
on
various
organizations,
you
know
interest
and,
and
that
kind
of
thing
you
know,
I,
think
you
know
just
making
sure
it's
all
happening.
B
There
is
obviously
the
right
way
to
go,
but
you
know
having
a
well-defined
starting
points.
Gonna
make
this
a
lot
easier.
You
know
it'll
be
really
interesting
to
see
of
what
you
know.
The
folks
from
the
coast
called
Project
have
to
say,
you
know
I.
Think,
they're,
probably
you
know
the
ones
that
are
probably
doing
this
in
production,
the
the
biggest
and
the
baddest.
You
know.
We've
certainly
got
a
few
smaller
deployments
with
our
operator
in
production,
but
it's
nothing.
B
A
E
You
never
get
used
to
this
I've
been
I've,
been
working
remotely
for
forever
yeah,
so
I
think.
From
my
perspective,
we
should
just
figure
out
what
do
all
these
operators
have
in
common?
What
like
what
is
the
feature
set
of
each
of
them
offered
right
now
and
then
what
is
what
features
are
missing
between
them?
I
think
going
for
something
that
offers
a
base
like
a
feature
set
of
you
spit
up
a
cluster,
and
you
can
expand
the
cluster.
You
can
shrink
a
cluster
using
this
operator.
I.
E
A
Yeah,
that's
that
sounds
like
a
good
starting
place
like
there's.
I
know
that
the
operator
doesn't
have
a
ton
of
features
it
can
do,
but
that's
a
good
place
to
start.
If
we
can
do
some
deltas
between
because
there
I
think
a
lot
of
them
are
the
same.
But
there's
probably
some
nuance.
That's
pretty
interesting
dan
or
somebody
else
from
New
Relic.
A
I
Sure
yeah
I
guess
what
I
would
say
is
so
we're
New
Relic
we're
very
early
in
the
process.
We've
really
haven't
even
begun
to
investigate
sort
of
the
operator
options
that
are
out
there
right
now.
So
all
of
this
activity
is
coming
in
at
a
really
good
time.
I
think
what
we're
most
interested
in
like
I
agree
is,
is
kind
of
starting
with
you
know,
pretty
you
know
basic
functionality
and
what
we're
we're
most
interested
in
is
kind
of
you
know,
working
with
and
choosing
the
operator
that
the
community
is
moving
towards.
You
know.
I
One
of
our
concerns
was
always
like
you
know,
picking
something
you
know,
picking
a
project
that
wasn't
that
may
not
have
like
a
long-term
future
so
yeah.
So
the
idea
that
there's
sort
of
a
you
know,
momentum
around
a
community
solution
is
exactly
what
we're
looking
for.
So
we're
hoping
to
support
that.
A
A
There's
that
kind
of
important
thing
I'll
tell
you
they'd
say
it's
on:
there's
a
Casandra
wiki,
it's
the
in
the
same
place
where
I
had
I
spent
the
link
for
this
meeting.
There's
a
grand
total
of
one
CEP
in
there
and
I
think
after
this
we
should
have
two
thanks,
Dan,
so
yeah
and
it's
not
exclusive,
but
to
get
edit
rights
which
you'll
need
you
need
to.
You
know
someone
needs
to
give
them
to
you,
but
once
you
have
the
rights,
so
you
can
give
it
to
somebody
else.
A
A
B
A
B
J
A
A
B
One
one
question
I
had
for
the
broader
team,
because
we've
got
a
number
of
companies
here
that
are
in
very
much
the
you
know:
development,
sandbox,
testing,
weight
and
look
stage
of
things.
You
know
and
that's
been
my
primary
experience
with
you
know:
we've
been
working
on
a
operator
and
its
various
versions
and
implementations
for
a
year
or
two
now,
and
you
know
this
there's
definitely
been.
A
E
H
Does
that
to
some
extent
they
have
a
protocol
version
they
had
so
a
year
ago,
when
I
spoke
with
them,
they
had
that
was
kind
of
in
planning
stages,
but
I
think
like
some
late,
like
like
August
September
timeframe
or
something
like
that
I
think
they
had
an
initial
stab
at
that
John
salmon.
You
you
know
where
they're
at
with
that
I
remember.
They
had
something
going
for
that.
Yeah.
K
K
Don't
know
if
it's
in
production
I
had
kept
up
with
some
lately,
but
I
mean
I,
I
know,
stuff's
been
merged
and
it's
you
know,
they're
ongoing
when
I
had
last
talked
with
him
about
it,
he's
since
left
to
Amazon,
but
before
he
left
it
was
all
in
their
internal
repos
and
then
shortly
thereafter.
So
it's
probably
president
of
last
year
it
was
put
in
the
public
github
repo
and
they
put
out
a
blog
post
about
it.
So
they've
definitely
made
a
lot
of
progress
since
then,
I'm
not
sure,
if
they're
using
it
in
production.
K
L
It's
been
interesting
to
see
kind
of
the
kubernetes
ecosystem
mature
with
regards
to
multi
cluster,
a
multi-threaded,
collector
deployments
or
cross
region
deployments,
and
that's
definitely
one
of
the
iterations
they're
seen
a
few
solutions
in
this
space
from
like
Submariner,
which
does
IPSec
tunnels
between
regions,
you
could
tear
your
cloud
providers
together
or
you're
on
friends
to
cloud
and
and
just
hope
that
the
networking
works
out
or
even
look
at.
You
think
something
like
a
proxy
layer.
L
So
integrating
with
something
like
convoy
to
handle
that
within
your
group,
tiny
bass
and
they
all
have
different
pros
and
cons
and
I'm
curious.
What's
the
shape
of
the
kamini
light
operator?
Would
what
kind
of
target,
or
would
it
be
kind
of
malleable
as
to
whether
or
not
you
go
one
way
or
the
other.
B
I'm
happy
to
take
it
and
I
stab
at
this.
This
is
something
that
we
have
very
purposely
not
implemented.
Despite
multiple
people
asking
for
it
and
looking
to
tackle
it,
you
know:
we've
learnt
very
quickly
that
trying
to
build
on
kubernetes
is
like
building
on
quicksand.
You
know,
especially
when
you're
touching
internal
api's
and
and
that
kind
of
thing,
and
so
we're
very
much
hold
off,
trying
to
take
a
stab
at
multi-region
kubernetes
until
they
had
a
solid
community
census
around.
B
What
that
looks
like
at
the
control
plane
side
of
things,
I
know
that
doesn't
help
people
who
have
a
hard
requirement
to
do
this
stuff
sooner
rather
than
later,
but
you
know
we've
kind
of
left
it
to
be,
but
you
know
kind
of
left
some
functionality
off
the
end
where
it's
like.
As
long
as
you've
got
tcp/ip
connectivity,
you
know
you
can
add
in
some
extra
config
and
it
should
work,
but
it
hasn't
been
in
anything.
We've
tried
to
tackle
from
having
a
sensible
answer
on
the
control
plane
side
of
things,
I.
A
Can
talk
too
extensively
with
the
sky
team
and
hopefully
they'll
be
on
tomorrow,
the
next
meeting
they
are
trying
to
make
multi
the
multi
data
center
and
it
sounds
like
they're
not
only
doing
it
on
the
from
an
operator
standpoint,
but
they're
also
doing
some
bending
on
the
kubernetes
side
as
well.
The
I
think
the
quote
that
I
got
was
kubernetes,
wasn't
quite
ready
for
this
and,
like
the
networking
layer
was
not
okay
with
that
and
so
with
gossip
etc.
A
No
I
I
think
that's
another
opportunity
to
is
is
how
much
I
mean
we
may
need
to
engage
the
kubernetes
community
and
for
some
things
as
well,
and
that
that'll
be
interesting
and
I
I'm.
Also
in
the
TOC
for
CN
CF
and
the
software-defined
networking
sig
is
heating
up
right
now
they
may
want
to
get
involved.
We.
H
L
It
might
be
interesting
to
take
a
look
at
what
some
of
the
service
meshes
are
doing
in
this
space,
though,
where
they
have
in
some
instances
they
followed
the
same
pattern
where
you
have
a
single
kubernetes
cluster.
That's
like
the
control
plane
to
the
other
kubernetes
clusters,
but
then
another
deployment.
There
are
a
solutions
where
you
run
a
next
best
management.
K
L
H
What
versions
of
unifying
the
versions
and
things
like
that
so
think
it
had
a
master
version
of
the
like
a
master
control
plan
or
whatever,
but
when
you
get
to,
if
you
want
to
go
multi
multiple
clouds,
where
you
have
kubernetes
engines
involved,
are
you
going
to
say
that
each
region
is
going
to
have
access
and
and
sovereignty
over
its
own
resources
and
and
like
the
gke?
Is
gonna
operate
and
do
the
specific
stuff
in
GK?
And
then
you
have
a
you
know
a
KS.
H
A
H
B
I
mean
I
think
what
it
does
highlight
is
you
know
there
is
no
strong
answer
from
the
kubernetes
the
kubernetes
community
around.
This
is
the
way
you
should
do
it
and
you
know
I
think
you
know
we
gotta
lean
on
them
and
for
what's
what's
the
solution,
because
otherwise
we're
going
to
end
up,
you
know
going
down
a
way
that
works
for
some
and
and
probably
doesn't
work
for
all
you
know
and
omegle.
B
So
we
just
need
to
have
an
acknowledgement
that
you
know
as
we
work
on
this
particular
CEP
they'll,
be
folks
with
production
requirements
that
push
them
in
a
different
direction.
You
know,
at
least
for
the
time
being,
until
we
can
harmonize
in
you
know
it's
it's
hard
when
you're
trying
to
build
for
everyone
wrote.
This
is
just
scratching
your
own
itch,
so
I
think
you
know,
maybe
maybe
starting
to
lean
on
the
kubernetes
community.
A
I
do
know
that
there
are
folks
in
the
and
the
CN
CF
that
are
super
interested
has
been
mentioned
like
this
is
really
a
cool
idea.
Cassandra
there's
not
really
a
much
of
a
database
solution
stack
in
the
in
that
world
and
it's
kind
of
a
flat
tire.
You
know
it's
like
okay,
we
need
this
right
and
there
are
some
projects
like
bitna
sand,
tik
b
or
TI
DB
tika
DB,
which
is
a
key
value
store
and
then
of
course
Etsy
D,
but
not
like
you
know
what
Cassandra
can
do
so
I
will
bet.
L
Think
we
can
all
agree
that
that's
that's
pretty
easy,
but
the
stateful
applications
become
kind
of
second
tier,
both
with
the
components
that
make
up
state
law
applications
inside
remarries.
Now
a
staple
sets
and
persistent
volumes
and
I'm
curious
to
see
what
that
time.
For
its
going
to
look
like
for
doing.
A
Yeah
I
think
these
are
all
really
good
points.
I'm,
just
keeping
the
clock
in
mind,
you
know
I
did
schedules
for
half
an
hour
just
so
that
we
didn't
have
to.
We
could
probably
talk
about
this
for
hours,
but
I
think
the
time
for
that
is
coming
near
I.
You
know
if
there's
any
other
pressing
issues.
Of
course
you
know
bring
them.
This
is
a
good
time,
but
I
think
the
takeaway
here
is.
A
You
know
now
I'll
feed
this
over
to
the
next
meeting
as
well
as
Ben
and
I,
and
then
hopefully
somebody
else
will
start
a
CEP
start
gathering
comments.
Gathering
requirements
start
hashing
it
out
in
Docs,
as
Nate
put
it
but
super
happy
to
see.
You
know
a
lot
of
participation
already
like
I'm
glad
to
see
it's
not
just.
You
know
me
and
Ben,
because
I
love
that
but
it's
nice
to
see
other
folks
involved
but
yeah.
So
if
there's
anything
else,
I'll
just
let
it
leave
the
mic
open.
L
All
right,
it's
the
EP
materialises.
Are
you
looking
for
comments
on
that
or
edits,
because
I
know,
there's
been
a
reasonable
amount
of
research
into
a
number
of
operators
and
some
of
the
challenges
that
we're
going
to
encounter
going
into
multi
cluster,
given
Reddy's
deployments,
that
kind
of
thing
yeah.
D
B
And
and
really
I
think-
and
you
know
putting
some
words
into
Patrick's
mouth
as
well
a
little
bit
here,
but
you
know
you
know
we'll
kick
off
the
save,
hey
but
I
think
really
it'll
be
primarily
around.
You
know:
scaffolding
and
structuring
the
doc
getting
it
all
planned
out.
What
we're
going
to
talk
about
you
know,
because
otherwise
you'll
just
have
to
vendors
navel-gazing
at
how
amazing
their
own
offerings
are.
You
know
which
will
be
fun
for
me
and
Patrick,
but
you
know
not
particularly
useful
for
everyone
else.
A
K
D
Mean
that
that's
an
excellent
question
that
would
be
one
of
the
things
I
think
we
could
come
out
as
part
of
this,
whether
they
want
to
take
that
as
like
a
sub
repo
like
we
have
with
so
many
other
stuff
or
like,
but
that
lives
somewhere
else.
Just
like
a
that,
I,
that's
exactly
type
of
thing,
I
see
the
shake
out
of
this
is
like
consensus
on
whether
it
should
be
there
or
some
real
yeah
and.
B
I
mean
you
know,
I'm
more
than
happy
like
sham.
Might
my
view
on
this
like
straight
from
day,
one
is
I,
think
it's
pretty
clear
from
everyone
attending
and
talking
about
this
and
what
everyone's
built
that
you
know.
This
is
wildly
useful
beyond.
What's
everyone's
doing
internally,
and
you
know,
I'm
pretty
strongly
believe
that
this
is
something
that
should
live
under
the
project.
If
I've
got
a
broader
appetite
for
it
to
be
there,
and
you
know
I'm
kind
of
all
in
on
that
direction,
you
know,
even
as
someone
that
you
know
would
I.
B
H
K
D
H
Okay,
because
I
mean,
if
we're
gonna
go
in
the
direction
of
having
a
project
sponsored
kubernetes
operator
than
having
potentially
having
something
that
it
can
test
with
in
a
kind
of
like
a
continuous
testing
environment
or
whatever
having
something
standard
that
people
can
rely
on
that
works
with
the
operator
might
be
handy,
I,
don't
know
if
there's
that
much
coupling
that
needs
to
happen
there,
but
I
just
thought
that
might
be
a
helpful
thing
to
have
any
conjunction
with
it.
I.
L
Think
that's
a
good
point,
bringing
it
in
entry
or
under
project
ownership
also
gives
a
little
bit
more
credence
than
it
being
community
driven
from
the
doctor
community
and
then,
if
there
are
any
changes
that
need
to
happen
to
enable
some
of
the
functionality
like
a
sidecar
it'd
be
nice
to
know
for
to
be
able
to
publish
images
with
the
sidecar
president.
And
what
have
you
and
actually
has
it
backing
the
project
versus
saying.
I
L
Installed
it
from
the
docker
image:
that's
out
there.
That's
not
ours
and
I
mean
obviously
that's
how
the
stance
of
the
community
would
take,
but
it
just
makes
it
more
difficult
if
it's
not
entry
and
and
having
kind
of
project
involvement
with
it.
Especially
one
of
the
things
that's
been
frustrating
for
us
is
the
we
want
to
work
with
for
dotto
and
the
community.
Docker
images
don't
have
for
dough
at
all,
so
it'd
be
nice
as
to
get
into
Lake.
D
D
K
Question
so
if
the,
if
the
operator
project
does
live
under
some
project
of
cassandra
with
the
office,
the
PMC
members
or
the
folks
that
are
involved
of
doing
oversight
right
word,
but
involve
for
voting
for
releases
and
whatnot,
would
those
be
the
same
folks
that
would
be
providing
that
same
oversight
for
this
sub
project?
Yes,
that's
good
to
know
yeah,
so
that
I
think
that's
something
to
stop.
Consider
because
I'm,
you
know,
there's
they're
two
different
moving
at
two
different
speeds,
Cassandra
established
and
fair,
to
say
some
inertia.
A
D
This
precedent
for
this,
the
ASF,
where
projects
like
beam,
where
you
have
tons
and
tons
of
sub
modules,
where
people
move
independently
I'm
gonna
sub
modules,
depending
on
like
what
is
needed
upstream
from
there.
That's
that's
one
of
the
first
ones
that
come
to
mind,
but
like
a
couple
project,
a
dupe
ecosystem
work
that
way
as
well.
K
Yes,
this
is
more
than
you
had.
My
questions
are
more
about
yen,
so
oversight
may
not
been
the
best
word
because
not
in
terms
of
how
the
the
project
in
terms
of
the
community
is
involved.
That's
one
thing:
that's
separate,
I'm
thinking
more
the
technical
side,
late
yeah
releases,
approving
PR,
something
you
know
that
not
so
much.
D
H
Okay,
let's
do
4.0
and
until
for
dodo
ships,
we
can't
do
another
version
of
the
operator,
but
they're
completely
decoupled
and
groceries
separately,
you're
thinking,
oh
yeah,
I,
guess
it
depends
on
the
functionality,
that's
required,
or
are
you
saying
that
it's
gonna
live
in
project
and
and
go
out
with
each
release
now
I,
just
I
would
put
this
in
a
different
module,
just
exactly
that's
what
I
guess
that
is
that
what
you're
asking
John
is
to
say
that
it's
decoupled,
so
you
can
have
a
different
release.
Cadence
and
well.
K
That's
part
of
it
I
think
different
least
games
and
I
think
that
there
are
I
mean
they're,
obviously,
intersecting,
concerns
and
interests
here.
Obviously,
but,
like
Patrick
said,
you've
got
people
coming
in
it
from
both
ends
of
this,
so
I'm
one
into
the
spectrum.
You've
got
Cassandra
committers
and
people
like
SOI
data
stacks.
K
By
way,
it's
EOP,
who
are
you
know,
I
mean
just
Cassandra
gurus
and
then
you've
got
other
people,
the
other
in
a
spectrum
that
are,
you
know,
C's
people
to
work
on
their
operators
and
you
know,
may
be
stronger
a
lot
start
on
the
crew
and
Eddie's
beside
of
things
and
and
not
as
much
in
the
cassandra
side.
And
so
it's
you
know,
there's
I
think
sometimes
so
that
I'm
just
thinking
about
that.
K
How
that
will
mesh
if
the
same
people
that
are
going
to
decide
whether
or
not
you
know
provide
that
when
I
say
oversight,
for
example,
let's
say
decide
about
whether
or
not
a
PR
should
get
merged
and
into
upstream
for
Cassandra
also
would
be
the
ones
that
making
that
call
for
the
operator
project.
Yeah.
D
I
mean
as
as
part
of
this
I
would
anticipate
taking
on
their
quickly
adding
people
who
commit
errs
to
like-
and
this
is
my
personal
opinion.
I
can't
speak
for
anything
here
but
like
I
would
anticipate
taking
people
on
as
committers
on
when
we
brought
in
something
like
a
sophisticated
module
like
this,
and
if
somebody
was
focused
on
that
that
I
would
be
the
type
of
thing
where
you
have
committee
right
stand
again.
Ii
do
the
same
same
thing
with
beam
work.
D
You
know,
they'll
bring
in
a
plug-in
or
a
module
and
you'll
have
a
couple
commuters
for
that
and
they're
being
committers,
but
they
just
that's
where
they
hang
out,
because
that's
what
they
know
and
it's
anything
any
kind
of
votes
like
that
are
lazy
consensus.
So,
even
if
one
person,
two
votes
plus
one
for
release,
you
release
it.
A
That's
how
it
works,
I
think
these
are.
This
is
gonna,
be
an
interesting
structural
conversation
because
you
know
there's,
this
is
all
I
can
go
and
all
the
rest
of
the
projects
in
in
Java,
so
I
mean
we
have
some
mm-hmm
impedance
mismatches
along
the
way.
I
was
gonna.
Ask
anybody
from
New,
Relic
or
Bloomberg
I
mean
we're
talking.
People
who
you
know
we're
a
lot
of
vendors
who
have
one,
but
you
know
that
people
who
want
to
use
one
do
you
have
a
preference
of
like
where
it
lives
or
how
it
lives.
G
I'd
like
to
see
it
live
somewhere,
where
it's
very
clear
that
it's
the
the
sort
of
officially
supported
project
I
like
the
idea
of
having
it,
you
know,
being
being
able
to
kind
of
run
on
its
own
release.
Cadence
I
am
a
little
bit
curious
like
how
it
would
fit
in
with
with
the
idea
of
a
management
process
or
a
sidecar
and
like
what
the
division
of
responsibilities
are
there,
but
but
yeah.
A
A
Okay,
we're
a
little
over
a
little
bit,
but
that's
fine
not
like
we're
going
anywhere
right.
You
know
I,
think
I'm
just
going
to
stay
at
home
today.
So
I
know
these
jokes
are
not
getting
old.
Are
they
if
there's
anything
else,
pressing
going
once
going
twice?
Okay,
let's
call
it
a
meeting.
Thank
you.
Everyone
for
showing
up
and
participating
I
again
I'm
recording
this
so
I
will
post
both
of
those
in
tandem
tomorrow
so
and
then
I'll
have
some
better
notes
around
that
as
well.
A
I
think
the
next
things
you
can
expect
all
once
the
notes
are
together
and
the
recordings
up
Oh
put
that
on
the
dev
list
and
probably
tweet
it
as
well.
I,
don't
know
how
you
found
this,
but
there
it
is,
and
we'll
hopefully
have
some
artifacts
to
work
from
like
EEP.
So
we
can
put
some
comments
together
and
start
working
on
that,
and
you
know,
pmc
can
help
with
some
structure
around
that
and
but
didn't
I
heard
more
of
this
kind
of
meeting
is
awesome,
so
I'm
all
for
it
sure.