►
From YouTube: Kubernetes SIG Service Catalog 20161212
Description
SIG service catalog welcomes new SIG leads from Deis, Google, and IBM, discusses repo philosophy and next steps on planning
Agenda - https://docs.google.com/document/d/10VsJjstYfnqeQKCgXGgI43kQWnWFSx8JTH7wFh8CmPA/edit
A
All
right,
hello,
everybody
and
welcome
to
the
Monday
December
12
2016,
medium
cornetti
6
service
catalog.
Today
we
have
an
action
packed
agenda
full
of
administrivia
for
you
I'm,
putting
the
link
into
the
chat
now
and
I'm
going
to
continue
speaking
because
I
am
first
on
the
agenda
having
the
bully
pulpit
so
first
matter
of
gender
today.
A
Is
that
as
everybody
who
has
been
tuning
in
to
these
meetings,
watching
them
on
YouTube
can
probably
tell
we
have
a
lot
of
activity
going
on,
and
we
also
have
a
number
of
companies
that
are
devoting
significant
resources
to
this
effort.
So
the
pattern
that
we
have
for
those
things
in
urban
any
cigs
is
that
we
have
multiple
leaders
of
a
cig,
so
I
have
reached
out
to
aaron
schlessinger,
Doug,
Davis
and
Brendan
Melville
from
Deus
IBM
in
Google
respectively,
odd
too.
Yes,
you
are
resources.
A
A
Second,
now
I
have
sent
a
message
to
the
the
mailing
list
for
the
group,
which
I
believe
all
of
you
are
probably
on
I,
with
a
proposal
to
limit
the
amount
of
working
against
one
another
that
that
we
have
to
know
very
good
share
technique.
Here,
Jessica
limit
the
amount
of
working
against
one
another
that
we
have
to
do
and
I
basically
get
some
economy
of
effort.
A
Iran
cube
con
submissions
because
there
are
many
people,
probably
interested
in
submitting,
but
only
only
maybe
one
or
two
will
get
in.
So
what
I
propose
is
that
we
that
we
have
a
panel
and
official
panel
submission
going
to
sig.
The
reason
to
go
with
a
panel
is
that
on
a
normal
CFP
response,
there
are
a
max
of
two
presenters
I
think
that
we
have
more
than
two
parties
that
would
like
and
deserve
representation
on
on
an
official
cute
punish
thing.
A
So
I'm
going
to
suggest
that
we
do
a
panel
I'm
going
to
start
writing
up
an
abstract
for
the
panel.
We
can
do
a
demo
or
that,
and
that
way
we
can,
we
can
get
the
books
that
should
have
representation
up
there
and
also,
let
me
just
note,
I-
think
an
official
ish
submission
is
also
one
that
we
should
collaborate
on
an
integer
everybody's
comfortable
with
the
messaging
around,
since
we
all
have
our
different
designs
on
this
catalog.
A
So
if
folks
think
that
is
a
good
idea,
I
will
ask
that
we
avoid
the
individual
submissions
that
might
be
out
of
band
or
that
the
wider
group
might
not
know
about.
Of
course,
I
can't
stop
any
of
you
from
doing
that,
but
in
the
spirit
of
good
sports
person,
ship
I
ask
you
to
do
that,
and
if
there
are
any
questions
or
concerns
about
that,
we
can
certainly
talk
about
it
on
slack
or
offline.
Somehow,
I
and
I
think
that's
about
it.
For
that
any
thoughts
on
that
before
we
move
on.
B
A
So
I
offer
my
cat
wrangling
services
I,
have
a
very
fancy
net
that
I
tend
to
use
for
cats
and
some
other
cat
wrangling
devices,
contraptions
etc.
However,
since
I
am
over
scheduled
in
my
professional
life,
if
someone
else
would
like
to
step
up,
I
am
happy
to
hear
I
hear
a
voice
respondent
the
affirmative
to
that,
with
the
caveat
that
I
am
already
kind
of
on
the
hook
for
this,
my
own
work
life.
So
maybe
we
can
collaborate.
D
A
E
Hey
okay,
so
what
is
it?
It's?
Oh
yeah
planning,
so
I
had
this
discussion
earlier
today
with
with
the
leads
it's
my
main
question
that
I
wanted
to
bring
up.
Was
you
know,
we've
been
doing,
we've
been
doing
work,
but
it's
larger
than
unfocused.
How
can
we
bring
focus
to
this?
What
what
are
we
going
to
n?
Are
we
going
to
start
planning
deliverables
and
what
are
what
are
the
road
maps
to
get
us
to
those
deliverables?
E
How
can
we
start
prioritizing
our
our
work
items
and
managing
them
appropriately,
I
think
from
a
discussion
we
had
earlier
today
that
we
probably
can't
dig
into
all
of
that
in
this
meeting
right
now,
but
we
can
definitely
plan
for
a
meeting
which
we
can
plan.
Perhaps
later
this
week,
I
think
Paul,
you
you
would
like
after
wednesday,
I
have
yeah
I
have
a
shady
friday,
and
so
maybe
thursday
is
a
good
day
for
whoever's
interested
in
joining
that,
yes,.
A
E
E
Let's
see
I've
lost
my
view
of
the
doc.
Give
me
a
moment:
oh
right,
okay.
So
now
the
next
agenda
item
I've
noticed
that
in
a
lot
of
our
you
know
a
lot
of
our
PR
work
it
out
of
having
existential
crises
or
philosophical
crises
around
various
things
like
naming
or
or
how
our
repo
is
set
up
and
I
felt
like
it
was
important
to
you
know
just
answer
some
questions
once
and
for
all,
so
that
we
can
start
increasing
velocity
on
our
work
around.
E
E
E
We
really
want
to
prioritize
progress
over
correctness
over
perfection
over
over
doing
things,
the
right
way
and
doing
things
that
the
long
term
way,
and
so
we
came
up
with
a
list-
that's
already
in
the
notes
of
some
of
the
some
of
the
concrete,
concrete
things
that
that
we
want
to
do
in
order
to
prioritize
accordingly.
The
main
point
I
think
that
Paul
is
in
the
terminology
of
the
crew,
benetti's
incubator.
E
So
let's
bring
a
lot
of
that
discomfort
into
issues
where
we
can
discuss
them
in
a
more
active
environment
and
then
the
the
second
side
of
that
is
any
PRS
that
come
out
with
some
some
sort
of
contention.
You
know
that
can
arise
during
the
review
process,
let's
not
block
PRS
on
getting
those
settled.
E
Let's
allow
those
PRS
to
go
through
and
make
sure
that
whatever
is
contentious
or
whatever
is
whatever
is
challenging,
gets
turned
into
a
follow-up
issue
or
PR
or
whatever,
where
we
can
then
discuss
those
uncomfortable
things
and
and
do
do
whatever
changes
needs
to
be
done
after
the
fact.
But
the
main
point
is,
let's
make
sure
that
we're
getting
PRS
through
as
quickly
and
as
comfortably
as
possible,
because
we're
so
young-
and
there
are
so
many
moving
pieces
and
things
that
we
have
philosophical
arguments
about
right
now
may
end
up
being.
E
A
A
It
was
two
months
less
why's
that
if
I
could
go
back
in
time
hop
in
my
handy
time,
machine
I
would
probably
do
or
an
attempt
to
do
a
better
job
at
messaging
around
some
of
the
stuff,
but
I
didn't
so
and
I
don't
have
a
time
machine,
so
I
can't,
but
I
will
say
it's
been
a
learning
experience
and
I
can
also
say
that
I
totally
appreciate
preferences
around
a
rebuilding
app.
That
might
be
a
counter
to
what
Cooper
Nettie's
does
I'll
just
leave
it
at
that.
A
A
D
A
I
can
appreciate
your
escalation
attention,
but
it
is
denied.
No
I
will
not
be
made
meeting
I.
None
of
those
things
like
take
a
second,
oh,
no
yeah,
I,
think
maybe
we
can
call
it
after
this
week
for
the
year
I
personally
will
be
around,
but
I
know
that
other
folks
are
traveling,
but
I
do
wonder
what
the
group
thinks
about
this.
E
A
I,
so
if
we
were
to
meet
after
this
week,
I
would
say
it's
probably
most
important
to
make
progress
on
getting
the
API
server
to
the
point
where
it
can
serve
the
API
that
we
are.
We
are
designing
and
to
continue
design
discussion,
but
if
people
want
to
do
things
like
end
time
with
their
families,
you
know
relax.
I
think
that
is
acceptable.
D
D
Okay,
the
other
issue
that
I
want
to
bring
up
today
was
face
to
face.
I
believe
we
were
talking
about
doing
one
in
january
based
upon
the
phone
call
got
earlier
today.
It
sounds
like
the
my
first
possible
week
might
be
the
week
of
january,
twenty
third
being
a
little
bit
selfish,
thursday
and
friday
that
week,
otherwise
we
make
it
push
down
until
it
leave
februari,
but
I
want
to
get
a
sense
from
the
group
and
what
you
guys
think.
E
D
E
F
A
F
C
A
Noted
so
I'm
not
sure
we
can
arrive
at
a
conclusion
in
this
meeting.
I
wonder
I
think
from
talking
with
the
other
leads
earlier.
We
agreed
to
kind
of
circle
the
wagons
and
see
what
our
logistical
and
budgetary
capabilities
were,
so
that
might
inform
a
decision
on
where,
if
not
when
I
did
this
sense
that
I'm
getting
is
then
probably
the
week
of
the
23rd
is
the
earliest
that
we
could
do
it
with
that
inconveniencing
or
stressing
out
people.
E
A
A
So
that
leaves
us
out
of
agenda
items,
and
so
the
decision
I'd
like
to
oppose
to
the
group
is,
I
think
that
we
had
a
pretty
decent
meeting
on
friday
for
those
of
you
to
join
us
about
reviewing
the
API
server
work
that
Morgan
Bauer
has
done
and
talking
about
some
preliminary
next
steps.
I
would
like
to
have
a
follow
on
to
that,
but
I
think
it's
more
of
a
one-hour
item
than
a
30-minute
item.
A
I
I
would
be
happy
to
start
talking
about
it
now
or
we
could
talk
about
it
tomorrow
in
a
one-hour
meeting,
since
everybody
has
such
copious
time
that
they're
like
cool
another
hour
meeting.
That
sounds
great.
How
do
people
think
about
that?
Or
how
do
people
feel
about
that?
And
what
do
you
think
I
open.
D
C
A
So
yeah
we
can,
we
can
do.
We
can
do
that
and
I
think
what
I
might
go
ahead
and
do
now,
since
not
everybody
was
here,
is
just
give
a
tour
of
what
an
API
group
looks
like
can
I
just
can
it
if
anybody's
not
familiar
with
the
concept
of
Cooper
Nettie's
API
group,
will
you
speak
now
or
forever
hold
your
peace?
What
is
an
API
group?
Okay,.
C
A
A
A
An
API
group
means
a
set
of
resources
that
are
presented
behind
a
single
rest,
endpoint,
basically
or
that
share
a
common
ancestor
in
the
rest
hierarchy
got
it.
Thank
you
so
retracing
some
other
footsteps.
Morgan
Bauer
at
IBM
has
been
the
head
of
the
spear
and
has
spent
the
last
couple
weeks
on
a
solo
mission
to
basically
bootstrap
our
own
API
server,
which
is
a
feat
not
to
be
underestimated,
because
the
the
documentation
for
doing
this
is
not
basically
Morgan's.
A
Writing
it
as
it
goes
because
we're
one
of
the
first
groups
that
wants
to
build
baby,
Cooper,
Nettie's
and
part
of
a
baby
Cooper
Nettie
Zora
Cooper
Nettie's,
is
an
API
server.
So
we
are
now
at
the
point
where
I
merged
it
was
sometime
this
weekend
or
earlier
today.
Don't
remember
it
doesn't
matter
I've
merged
his
skeletal
API
server
that
you
can
run.
You
can
point
cube
CTL
at
it
and
it
thinks
it's
talking
to
a
Cooper
daddy's,
but
it's
empty
right
now
and
the
hump
that
we
need
to
get
over,
maybe
not
hump.
A
But
next
steps
are
that
we
now
need
to
add
an
API
group
to
the
API
server.
We've
been
designing
an
API
based
on
conversations
that
we've
had
in
the
face
to
face
after
we
agreed
on
sort
of
some
generalities
of
what
the
workflow
should
be
like
in
the
API,
and
as
many
of
you
have
been,
you
know,
attending
and
taking
part
and
we've
had
some
follow-up
discussions.
A
We're
now
at
the
point
where
our
next
step
is
really
to
get
our
API
server
to
actually
serve
this
API,
and
that
will
allow
us
to
start
writing
controllers
against
that
API
server.
There
are
some
some
folks
that
built
you
eyes
around
things
that
I'm
sure
would
like
to
have
an
API
server
that
works
that
they
could
integrate
with,
and
this
is
sort
of
like
the
linchpin
in
baby
Cooper
Nettie's
effort,
which
I
will
refer
to
henceforth
as
baby
Nettie's
odd.
I
A
A
So
the
internal
API
we
also
call
unburdened
API
is
a
superset
that
has
to
be
able
to
realize
any
particular
versioned
API
inside
of
it
and
you'll
see
you'll
see
here
we
have
this
file,
I'm,
highlighting
conversion
go
and
another
one
called
double
z,
generating
conversion
go
so
part
of
an
API
group.
In
order
to
achieve
this,
translate
ability
is
a
set
of
methods
to
do
conversions
from
the
version
API
into
the
internal
API,
and
here's
where
I'm
going
to
I'm
going
to
switch
context
for
a
moment.
A
A
I
should
match
11
with
our
initial
version,
but
we're
making
a
hedge
that
in
the
future,
the
future
service,
catalog
API
scientists
will
come
up
with
stunning
advances
that
will
just
completely
blow
our
minds
that
will
want
to
take
advantage
of
so
we're
going
to
have
an
internal
one
that,
in
addition
to
the
version
one,
so
we
can
vary
them
independently,
all
right
now,
switching
back!
Let's
look
at
what's
in
this
directory,
so
going
through
an
order.
A
We
have
this
types,
swagger
doc
generated,
go
I
know
that
some
folks
have
been
particularly
keenly
interested
in
what
type
of
documentation
we
have
for
this
effort,
which
is
a
right
and
good
thing
to
be
interested
in
and
want
the
types
swagger
doc
generated.
Go
is
a
file
that
contains
the
swagger
API
that
we
generate
from
the
go
doc
comments
and
API
resource
types.
All
right-
and
this
is
this-
is
the
actual
file
that
serves
the
API.
A
A
So
the
next
one
going
down
the
list
in
water
is
register
go,
and
this
is
a
file
that
basically
tells
the
API
server
infrastructure.
These
are
the
resources
that
are
in
this
API
group.
Next
is
double
z,
generated
defaults
and
what
defaults
are
for.
Those
that
aren't
familiar
with
concept
in
good
Nettie's
is
defaults.
Are
a
set
of
operate
shins
that
run
to
populate
the
state
of
objects
as
they
are
created
in
the
API
server,
so
their
defaults
there.
What
they
sound
like
the
doubles.
A
Where
monologue
is
the
case
may
be,
and
this
types
taco
file,
I
I,
think
everyone's
probably
familiar
with
this
as
idiomatic
name
of
the
file
that
contains
the
types
for
a
package
I
skipping
back,
we
have
types
generated
code
which
is
actually
a
yamo
parser
and
for
those
of
you
lucky
enough
to
be
unfamiliar
with
the
ins
and
outs
of
parsing
animal.
That
also
includes
a
JSON
parser,
because
y
ml
is
a
superset
of
JSON.
A
So
the
origin
of
this
is
that
we
found
at
a
certain
point
that
the
generic
llamo
parser,
that
we
were
using
in
Cuba
Nettie's,
was
a
hot
spot
within
the
API
server.
So
we
have
some
infrastructure
in
the
project
which
we
will
probably
be
the
head
of
the
spear
to
reuse.
This
I
would
love
to
be
wrong
on
that,
but
I
think
we'll
probably
be
the
first
first-class
reuse,
er
this
generation
to
generate
a
yamo
parser
that
understands
this
particular
set
of
API
types
so
skipping
ahead
here
or
just
resuming
our
order
in
its
descent.
A
Through
this
directory
listing,
we
have
generated
up
tbo,
and
this
is
a
generated
protocol.
Buffers
based
wire
format
for
these
api
resources
over
the
wire
for
anybody
that
isn't
familiar
protocol
buffers
is
a
basically
a
way
to
generate
a
wire
format
which
is
much
more
efficient
for
transmitting
structured
data
than
it
is
to
send
like
serialize
dmo
in
cooper
Nettie's.
We
use
this,
but
we
use
it
between
infrastructure
components
only
because
we've
found
that
it
is
much
harder
to
support
an
end
user.
A
That
has
has
some
kind
of
problem
when
they're
using
protocol
buffers,
so
it
is
used,
but
it's
basically
for
the
system.
End
users
are
going
to
be
sending
serialized,
yell
or
JSON
meta.
Echo
is
not
something
that
you
we
will
have
in
our
API
group.
It
is
where
the
implementation
of
v1
object,
meta
lives,
object,
meta
is
a
type.
It's
not
a
resource,
but
it's
a
type
that
is
used
by
all
resources
that
holds
information
like
namespace
name,
API
version,
etc,
etc,
etc.
So
next
we've
got
some
more
generated.
A
Stuff
we've
got
doubles
that
generate
deep
copy.
It's
what
it
sounds
like
it's
a
generated
set
of
deep
copy
functions
since
they're
no
fun
to
write
easy
to
get
wrong
and
easy
ish
to
generate
next.
We've
got
double
site
generating
conversion,
which
is
what
it
sounds
like.
It's
a
set
of
generated
conversion
functions.
I,
anticipate
that
initially
there
should
be
no
need
for
boutique
conversions,
which
are
the
next
file
conversion
naco.
But
the
infrastructure
exists
to
have
boutique
conversions
if
you
need
them
for
a
particular
type.
A
We
shouldn't
need
those
because
you
tend
to
need
them
as
you
accumulate
things
like.
We
change
the
API
in
this
API
group
version,
and
now
we
need
to
be
backward
compatible.
We
won't
have
to
worry
about
that
at
first
helpers
that
go
when
sounds
like
not
material
to
this
discussion
and
doc.
Doc,
oh
I,
have
been
told,
is
not
idiomatic
completely
doing
it
wrong
place
to
put
package
doc
for
going
on.
I
A
There's
there's
one
and
it's
in
type
stock
girl
and
the
types
die
generated
code
generated
at
PB,
go
and
actually
the
other
generated.
A
compilation.
Units
like
generated
defaults
generated
the
copy
generated
conversion,
basically
are
all
derivative
by
type
psycho.
So
there's
this
like
ecosystem,
probably
terrible
word
to
use
set
of
generator
things
that
go
and
wicked
types
go
and
generate
their
different
piece
of
it.
H
A
A
I
think
that
it
is
totally
possible
to
live
without
them,
with
the
caveat
that
you
will
immediately
see
the
value
of
generating
them
when
you
have
to
debug
a
deep
copy
that
doesn't
work
or
a
conversion
that
doesn't
work
so
by
all
means.
I
think
it
is
totally
valid
to
proceed
without
using
the
conversion
facilities.
A
D
G
D
I
I
A
I
And
other
generated
files
generated,
auto
band
I.
Guess
my
the
answers
below?
Yes,
rather,
you
basically
point
some
curb
Randy's
repo
to
others,
and
it
will
spit
out
a
file
than
we
check
in.
So
we
don't
have
to
copy
all
of
the
cogeneration
machinery
into
our
repo,
we're
just
gonna
clone
commodities
on
the
side
and
call
the
right
tools
now.
A
A
I
think
probably
it's
it's
probably
debatable
what
the
exact
right
thing
is
to
do.
We'll,
probably
not
do
the
exact
right
thing
at
first
but
like
I
would
totally
take
if
we
could
just
calling
those
binaries
to
generate
the
thing
at
first,
like
lifting
the
binaries
from
Cooper
Nettie's
into
this
project.
Don't
check
them
in
just
use
them
to
generate
stuff
and
we'll
figure
out
the
right
way
to
like
vendor
that
stuff.
In
am
I
answering
the
question
that
was
asked
this
time.
Yeah.
A
D
So
Paul
before
we
run
out
of
time,
I'm.
Okay,
are
you
doing
this
right
here,
but
before
would
be
for
the
top
of
the
hour?
Can
you
at
some
point
either
point
to
where,
in
the
make
files,
the
generation
happens
over
point
to
the
exe
s?
That
would
that
do
the
generation
just
so
Morgan
at
something
to
start
pulling
on
a
thread
absolutely.
A
A
Okay,
this
looks
acceptable.
I
think
your
face
will
still
be
intact.
So
let's
take
a
look
at
this
block
of
text
here,
and
this
is
the
generated
conversion
to
convert
a
v1,
AWS
EBS
volume
source
to
an
internal
API,
AWS
dds
volume
source.
Does
anybody
not
know
what
a
volume
sources
before
we
talk
about
this
thing.
A
Source
is
in
E
in
the
pod
spec.
The
volumes
array
is
a
list
of
volume
sources,
so
there's
an
API
object,
called
volume,
source
and
volume
sources.
A
union
type
that
can
be
one
of
I
think
that
we're
probably
up
to
like
10
15
different
types
of
volumes,
yeah
15
sounds
in
the
neighborhood,
and
so
those
15
different
volume
types
are
all
like
further
qualified
in
their
names.
A
Aws
elastic
block,
store
volume
source
is
the
name
of
the
API
type
than
models
in
AWS
GBS
volume,
and
this
is
this
is
the
piece
of
code
that
converts
the
one
version
of
that
thing
into
internal
rashad.
Okay,
and
this
takes
a
as
an
input.
Woops
takes
a
v1,
oh
god,
what's
happening
all
right,
I
hate,
trackpads,.
A
Okay,
all
right,
oh
this
takes
as
an
input
takes
a
v1
AWS
elastic
block,
store
volume.
Source
takes
an
as
an
output.
Well,
it
takes
is
a
parameter,
a
pointer
to
an
internal
API,
AWS
elastic,
store
volume,
sort
of
it
that
thing
internal
API,
that
bang
try
saying
that
three
times
fast,
your
tongue
will
be
tied
in
a
knot.
I'm
not
liable
for
your
dental
surgery
bill
and
a
conversion
scope
which
I'm
going
to
be
completely
honest
with
everybody
on
this
call.
A
A
The
Jessica
brain
trust
is
all
out
of
ideas,
but
basically
this
code
looks
really
boring
right.
It
takes
the
output
volume,
I
d,
fs
type
partition
read-only
flag
and
assigns
all
of
those
things
from
the
input
and
by
the
way,
this
returns
an
error.
So
this
thing
returns
null
alright
and
the
the
other
way
around
is
basically
like
very,
very
similar
takes
a
internal,
a
pointer
to
an
internal
API,
AWS
elastic
block,
store
volume,
source
and
a
output
parameter
of
v1
AWS
elastic
block,
store
volume,
source
conversion,
scope
returns.
A
A
I
A
A
A
A
A
A
A
Okay,
set
default
config
map,
so
set
default.
Config
map
I
says
that
if
the
data
field
of
the
config
map
that
comes
in
which
none
of
this
is
material
to
understanding
what
is
happening
here
by
the
way
it's
just
some
stuff,
so
this
set
default
config
map
is
where
the
actual
defaults
for
this
type,
lib
and
I
am
actually
surprised
in
this
case
that
there
is
something
into
false
taco
which
remember.
These
are
boutique
defaults
that
we
can't
generate,
but
maps
are
extremely
uncommon
in
the
communities
api.
A
We
only
use
them
for
data
in
a
couple
places,
so
probably
the
generator
doesn't
care
about
can
like
generating
defaults
for
maps,
and
that's
why
we
have
them
here
but
yeah.
So
that's
that's
the
kind
of
chain
of
custody
for
defaults
and
we're
just
about
out
of
time.
So
any
questions
on
this
stuff
before
I
boot,
you
all
out
back
to
the
internet,
that
you
came
from.
F
J
You
thank
you.
We
are
looking
into
adopting
cover,
ladies
here
at
Walmart,
and
we
would
like
to
contribute
to
the
open-source
effort,
so
we
would
like
to
crawl
before
we
walk
before
we
run
so
any
pointers
into
any
bugs
that
you
guys
have
that
we
can
look
into
and
try
to
solve.
Even
if
it
is
simple,
we
would
love
to
get
more
involved.
A
So
that's
I
I
welcome
you
and
I,
especially
welcome
anybody
willing
to
it's
not
just
willing
but
eager
to
solve
crew
benetti's
bugs
this
is
probably
not
the
most
applicable
forum
to
discuss
that
I.
Welcome
you
to
ping
me
on
slack
its
p,
more
EP,
mor
IE,
and
I
can
point
you
in
the
right
direction.
Awesome.
C
All
right
anything
else,
so
do
we
have
a
this,
is
jumping
the
gun
to
Thursday's
meeting.
I
know
I
want
to
ask
now,
though,
do
we
have
any
plan
or
and
or
volunteers,
to
get
some
of
the
code
generation
tools,
setup
and
or
also
to
write
some
of
the
end
points
that
we
know
will
need
like
get
for,
let's
say
for
brokers
or
something
so.
A
The
the
endpoint
piece
we
have
a
generic
rest
stuff
that'll
do
that
for
you.
So
there's
a
few
different
facets.
There's
the
code
generation.
We
need
the
generic
rest
stuff
to
come
in
Morgan,
I,
don't
know
if
you
started
looking
at
that
at
all.
We
need
someone
to
introduce
a
the
V
1
alpha
1
AP
lie
version
API
for
this
API
group
and
a
pinch
of
spice
to
make
it
nice
and
make
sure
all
that
stuff
works
together.