►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Foreign
today
is
Thursday
September
28th.
This
is
our
weekly
office
hours
discussion
for
cluster
API
provider.
Azure
cap
Z
is
a
part
of
cluster
API
and
said
cluster
lifecycle.
We
abide
by
the
code
of
conduct.
We
are
polite
to
one
another
respectful
we
are
open
and
as
best
as
we
can,
we
raise
hands
or
we
want
to
speak.
We
welcome
all
voices.
A
B
Hi
myself
channel
so
I'm
working
in
a
job,
math
and
I'm,
also
a
maintainer
of
Open
Source
litmus
chaos
project,
that
is
in
incubation
street,
so
I'm
just
exploring
another
project-
and
this
is
the
project
I
came
up
with
so
I-
also
raised
first
contribution
here.
As
a
testing
like
couple
of
unit
tested,
you
know
I'm
trying
to
explore
more
to
do
some
Port
contribution.
You
know.
A
Let's
get
to
the
formal
part
of
the
discussion:
okay,
we've
got
two.
A
Agenda
items
here
and
then
maybe
we
can
do
a
little
bit
of
Sprint
Style
backlog
scrubbing
if
we
want,
but
we'll
get
to.
This
looks
like
this
is
a
PSA
public
service
announcement
to
fill
out
the
survey
on
behalf
of
Sig
cluster
lifecycle.
So
here's
a
link
I'll
go
ahead
and
copy
this
link
to
chat
here
in
case
folks.
Don't
have
this
Google
doc
open.
So
please
everyone
click
through
that
link
and
fill
out.
The
Sig
cluster
lifecycle
survey
go
ahead.
C
Sorry
Jack
that
I
put
that
down.
So
that's
actually
not
so
we
don't
want
everyone
to
fill
it
out.
We
want
to
fill
it
out
once
as
a
project.
That's
the
same.
C
A
Did
the
new
tab
follow
screen
share?
Can
we
all
see
yeah,
okay,
I'll,
give
a
little
bit
of
a
intro
for
folks,
because
because
I
was
witness
to
this
same
exercise
in
cluster
API,
I
think
it
was
last
week
so
we
are
going
to
on
so
the
sincluster
life
cycle
asks
each
project
to
essentially
self-report
at
the
end.
I
think
this
is
an
annual
survey.
A
Is
that
right,
so
we're
going
to
go
through
a
list
of
questions
and
in
real
time
produce
a
consensus
response
to
each
of
these
questions
so
that
we
will
as
a
group
which
so
we're
going
to
represent
cap
C
cluster
API
provider,
azure
register
R
answers
for
this
form
with
sequester
lifecycle,
so
this
one
is
easy:
Mr
API
provider
Azure.
Does
anyone
want
to
criticize
the
grammar
there
good
enough?
C
A
A
B
A
A
Anyone
does
this
carry
any
differential
outcomes
if
I
say
between
10
and
25.
Does
that
mean
that
we
get
more.
A
I
was
just
feeling
aspirational
like
yeah.
We've
we've
reached
this
so
just
between
either
way.
That's
fine
all
of
us
today
and
everyone
who
watches
this
recording.
We
have
I
think
on
regular
occasion
exceeded
10,
so
we're
doing
great
as
a
subclass
life
cycle.
Okay,
we
are
yes
thank
you
for
everyone
who,
over
the
years,
has
done
this
I
feel
like.
We
have
really
good
notes.
A
Sorry,
if
I'm
not
reading
the
question,
are
you
keeping
meeting
notes
in
a
doc
share
with
the
Sig
mailing
list,
I'm
going
to
go
ahead
and
if
I
feel
super
confident
that
there's
an
obvious
answer,
I'm
going
to
answer,
but
please
feel
free
to
interrupt
me.
So,
let's
wave
the
raised
hands
rule
here
if,
if
I'm
doing
something
without
the
consensus
of
the
community,
here,
okay
meetings
recorded
are
publicly
available
in
the
Sig
playlist.
That's
yes
again!
Thanks
for
everyone
who
manages
that
playlist
I
know
it's
not
me.
A
F
E
C
A
The
reason
it
could
count
is
because
we
don't
typically
put
it
on
the
agenda
and
we
we
sort
of
self-organize
in
real
time
after
the
meeting
is
over
and
we
dismiss
folks
who
don't
want
to
participate
for
whatever
reason.
So.
I
think
that
you
could
convince
yourself
that
that
fits
the
definition
of
ad
hoc.
A
A
Political
back
channeling
anything
like
that
happening.
No,
none
of
that.
Okay,
great
okay!
In
the
next,
oh
Mac,
sorry
Mike
go
ahead.
I.
D
Was
just
curious:
do
we
throw
on,
like
the
I,
know,
you're
doing
the
kind
of
the
Cappy
sub
group
around
the
managed
control
plane?
Would
that
is
that
more
happy,
or
is
that
kind
of
cap
Z,
because
it
does
affect
the
managed
control
plane.
A
A
A
Yeah
I
think
that's
possible.
One
thing
that's
occurring
to
me
is
that
the
the
project
maintainers
do
maintain
a
sort
of
mental
roadmap
often,
and
we
talk
about
it
in
meetings
so
astronauts.
For
example,
when
you
were
working
on
the
work
with
identity
stuff.
A
lot
of
we
do
work
on
things
that
are
sort
of
macro
in
nature
and
are
understood
to
be
six
months.
Nine
months
down
the
road
I'm,
not
sure
if
we've
formalized
that
into
something
that
you
could
Define
as
a
roadmap,
but
it's
a
seal.
C
Oh
yeah,
actually
we
do
have
a
roadmap
I
just
remembered
and
found
it
some
of
the
Lincoln
chat
so.
C
Time
I
think
last
time
it
was
updated
by
David
to
start
I,
don't
know
if
she's
on
the
call,
yeah
and
I
think
we
had
talked
about,
maybe
updating
it
like
every
two
releases
or
something
but
I
think
we
kind
of
forgot.
So
this
is
a
good
reminder.
A
A
G
Going
to
say
that
since
since
I
am
kind
of
mentally
in
planning
mode,
I
I
haven't
actually
forgotten,
although
it
may
seem
like
that,
and
I
was
gonna.
I
was
I
was
actually
having
that,
on
my
my
mind,
to
to
look
at
I
I.
Think
right
now
is
a
good
time
to
kind
of
refresh
it
and
I.
Don't
think,
there's
a
extreme
difference
in
what
we
are
going
to
list
there,
but
I
do
think.
There's
some
minor
updates.
A
Okay
cool
so
I
think
in
the
interest
of
being
exceedingly
literal
with
this
question
this
was
updated
eight
months
ago.
So
that's
a
no
assuming
that
we
consider
this
as
a
community
to
be
our
roadmap.
G
Yeah,
we
also
have
the
roadmap,
which
I
think
I
should
update
in
the
update
in
that
link,
as
well
because
of
the
roadmap
project
view,
which
is
a
little
more
active,
so
cool
yeah.
A
Cool
we're
halfway
there
folks,
ish,
okay.
Is
there
an
onboarding
and
growth
path
for
contributors
in
your
project?
Definitely
the
answer
is
yes.
Do
we
want
to
provide
more
detail,
yeah
cool
I?
My
experience
in
cap
C
is
that
the
onboarding
and
growth
path
for
new
contributors
is
straight
down.
The
line
vanilla
inherited
from
kubernetes,
so
I
think
yes,
is
an
appropriate
response
to
this.
We're
not
doing
it
in
a
in
a
super
novel
way.
A
Okay,
as
a
project,
what
programs
do
you
participate
in
for
new
contributors,
EG
Google
summer
code?
A
F
F
A
Thank
you
so
much
okay,
trying
to
think
of
what
the
turn
of
your
response
to
this
could
be
who's
binary
to
me.
But
anyway,
yes
is
the
answer.
I
think.
A
Does
your
project
have
contributors
from
end
user
companies?
Yes,
it
does
I'm
looking
right
at
you,
Mike,
okay,
the
project
team.
Have
you
reviewed,
updated
the
owner's
file
in
the
last
six
months,
I'm
pretty
sure
the
answer
is
yes,
we
want
to
do
a
quick
sanity
check.
A
A
A
Oh,
it
doesn't
give
me
the
red
and
the
green,
so
I'm,
just
going
to
drill
down
so
I've
got
an
add
to
maintainers
congrats
oshtosh
we've
got
a
ad
to
reviewers
all
right,
so
these
These
are
both
just
promotions.
A
D
A
A
A
This
was
why
isn't
it
giving
me
a
date?
I
just
want
to
make
sure
that
that
was
within
the
last
six
months.
That's
the
cutoff,
I
think
I
think
this
is
before
six
months
right,
yeah.
My
son
was
born
February
8th
and
we're
telling
everybody
he's
seven
months
old,
so
I
think
that
means
okay,
cool.
A
All
right,
please
interrupt
me
if
I'm
going
too
fast
as
a
project
team,
do
you
need
help
in
any
area
now
we
would
be
silly
to
say
no
right,
foreign.
A
A
David
T,
you
are
in
a
unique
position
relative
to
the
rest
of
us,
where
we
are
like
nine
engineers
in
year,
but
one
pm
is
that
to
just
maybe
we
could
use
some
more
PM
resources.
G
Yeah
yeah
I
think
I.
G
G
I,
don't
know
I
mean
there's
always
there's
always
more.
You
could
do
but
I
think
you
know
we
kind
of
tend
to
have
a
prq
of
30
or
so
I.
Don't
know,
and
that's
that's
it's
and
that's
just
with
our
current
base.
You
know
and
that's
that's
not
as
bad
as
many
kubernetes
projects.
I
know
they
have
even
way
more
so
I
think
we're
doing
good
relatives
to
the
rest.
G
But
if
you
think
about
a
you
know
overall
project,
it's
I
think
it's
still
good
to
have
more
more
people
that
are
that
are
contributing,
especially
outside
of
Microsoft.
D
D
D
Right
but
you
know
a
lot
of
people,
you
know
when
I
talk
to
people
and
explain
what
we're
doing
with
it.
A
lot
of
people
don't
necessarily
know
about
it
and
I
do
find.
People
are
like
wow,
that's
really
interesting,
but
so
it
appears
that
there's
an
awareness
issue.
So
somehow
you
know
how
to
get
promotional
awareness
or
something
with
that.
C
A
D
A
A
Does
anybody
want
to
help
me
with
the
language
here
I
think
that's
a
great
call
out
and
even
though,
as
you
say,
Mike,
this
is
something
that's
probably
appropriate
to
many
many
projects
and
not
capsi
specific
I.
Think
it's
good
to
get
this
message
up
the
up
the
chain
so
that
if
there
are
some
folks
who
are
also
aware
of
this
and
trying
to
get
support
for
investing
in
that
stuff,
that
would
be
great
too
plus
one.
A
Cool
I
I
wanted
to
go
back
to
what
David
was
saying,
because
I
I
sort
of
like
rubbed
him
in
here
I've
often
thought
that
in
in
the
cncf
kubernetes
ecosystem.pm.
A
Role
contributions
are
really
an
unsolved
problem
and
there's
a
very
default
sort
of
gesture
in
terms
of
soliciting
help
towards
engineering,
Tech
concerns
and
the
outcomes
for
that
are
pretty
predictable.
Where
you
have
in
the
successful
projects,
you've
got
lots
of
folks
contributing
and
doing
concrete
work
to
move
the
project
forward,
but
less
you
know
that
doesn't
scale
well,
if
you
don't
have
sort
of
comparable
reinforcing
organizational
efforts
going
on
to
keep
those
progressions,
sane
and
so
I
would
love
to
be
able
to
I.
A
G
G
I
agree
across
not
just
let's
say,
cap
Z,
but
the
broader
set
of
projects
right
I
mean
and-
and
so
you
know,
as
you
know,
I
mean
I'm
even
now,
I'm
touching
a
number
of
different
open
source
projects,
as
I
know,
like
you,
you're
on
others
as
well,
and
so
trying
to
kind
of
manage
a
lot
of
different
open
source
things
that
aren't
really
yours
to
try
and
pull
together
a
story
and
I
feel
like
that's
a
lot
of
where
my
my
PM
energy
has
gone,
and
it's
and
it's
really
challenging
because
you're
trying
to
Shepherd
a
lot
of
Open
Source
things
like
I
said
that
you
don't
necessarily
have
direct
control
over
right
sure
you
could
contribute,
but
yeah
it's
hard
and
especially
in
terms
of
growth
of
Cappy
and
cap.
G
Z
I.
Think
the
the
missing
boost
to
not
not
just
cap
Z
but
just
Cappy
all
up
is
is
the
the
kind
of
end-to-end
connection
to
bigger
things
and
I
know
like
Mike,
has
done
a
lot
of
awesome
stuff
with
showcasing
that
his
kind
of
end-to-end
stock.
But
again
that's
that's
kind
of
that's
his
flavor.
You
know
and
I
think
there's,
there's
I
think
there's
still
a
lot
that
could
be
done
to
try
and
help.
You
know
pull
pull
together
the
end-to-end
story
for
for
our
open
source.
G
You
know
Z
and
Cappy,
and
a
number
of
different
things
to
kind
of
have
more
show
more
of
the
power
and
the
the
things
that
would
make
people
realize
the
goodness.
That's
there
so
and
that's
and
that's
that's
a
lot
right.
That's
that's
more
more
PM
horsepower
than
I
think
one
one
person,
but
it's
it's
hard
to
quantify
right.
A
Okay,
as
a
project
team,
what
are
you
doing
in
order
to
increase
your
contributor
base?
Well,
the
first
thing
that
occurs
to
me
is
that
we
are
a
welcoming
project
and
we
value
and
put
effort
into
retaining
new
contributors
over
time.
That
should
have
the
outcome
of
having
more
contributors.
Is
there
a
way
to
say
that
okay,
Cecile
is
typing
good,
first
issue,
just.
A
Let's
say
and
at
home
help
any
any
other
thoughts.
A
A
I
am
proud
of
tests
in
cap
Z.
Anyone
else
proud
of
other
things,
take
notes
Here.
What
are
we
proud
of.
A
A
G
Yeah
I
mean
I
think
that
that
ties
into
that's
a
foundation
for
the
the
amount
of
releases
and
the
quality
of
releases
right.
So
you
you
have
you
know
if
you
don't
have
a
good
confidence
in
your
testing,
then
you
have
maybe
a
lot
more
problems,
more
releases
or
you're,
more
hesitant
to
release
so
I.
Think
that
contributes
those
two
go
hand
in
hand.
G
But
another
Kudos
I
would
give
to
the
team
is
a
quick
response.
I
feel
like
to
you
know
slack
and
community
and
issues
and
things
not
everything
necessarily
gets
simply.
But
everything
I
feel
like
has
a
good
response
quickly.
Right
like
we,
we
acknowledge
and
we
interact
with
those
who
come
into
to
the
community.
A
Okay,
so
I've
already
said
that
do
we
want
to
maybe
put
in
parentheses,
reliable.
A
I
go
shift
enter
here
to
Mario
some
examples
of.
F
A
A
A
A
This
is
a
really
weird
phrased.
Question
like
when
I
first
read
this
sentence,
it
did
not
remind
I,
did
not
remotely
think
of
it
in
this
context,
but
I
guess
they're,
providing
that
as
the
do.
We
want
to
just
go
with
their
word
and
use
this
as
an
as
an
excuse
to
talk
about
what
we're
struggling
with,
or
we
want
to
answer
this
literally,
which
doesn't
imply
a
struggle.
G
I
think
one
thing
that
Mike
would
be
nice
to
call
out,
because
I
think
this
is
similar
for
cluster
API
and
for
us
is
help
with
like
what
like
website
documentation.
Refactoring.
That's
just
like
that's
just
like
a
lot
of
work
and
it
all
tends
to
get
de-prioritized
and
at
least
I
know
you
know,
cncf
has
people
that
can
actually
help
with
that,
but
those
people
are
also
usually
crazy.
Overwhelmed.
G
It's
like
two
people
to
you,
know
hundreds
of
projects
kind
of
thing,
but
that
would
be
super
like
super
helpful
I
know
in
other
other
projects,
I've
gotten
help
from
those
folks,
and
it's
been
really
awesome.
A
G
Yeah
I
mean
you
could
put
a
general
thing
of
trying
to
try
trying
to
put
people
together
or
collaborate
amongst
different
open
source
projects
or
maybe
not
collaborate
because
collaborates.
It's
generic,
there's,
there's
I'd,
say
generally
speaking,
people
are
are
open
and
you
can
talk
but
like
making
traction
on
cross
projects.
D
A
Okay,
cool
as
a
project:
do
you
consider
your
CI
signal
adequate
to
the
project
maturity,
I
vote?
Yes?
Does
anyone
else
have
any
other
votes?
Yes,
no
or
other?
Let's
try
to
skip
other
for
the
in
the
interest
of
time
and
just
say:
should
we
choose
yes
or
no.
B
A
As
a
project,
you
consider
your
documentation
adequate
to
the
project,
maturity,
I'm,
gonna,
actually
solicit
responses
from
Mike
and
shavesh
and
chandan
you
joined.
Have
you
recently
consumed
the
documentation?
What
are
your
thoughts?
What
are
your
thoughts
from
the
user
Community
out
there.
B
D
Mike
yeah
I
feel
it's
pretty
good
for
a
project
of
this
level
of
maturity
as
with
all
open
source,
documentation
and
all
projects.
It
could
always.
You
know
if
it
doesn't
have
a
dedicated
doc
writer,
there's
always
room
for
improvements,
but
I
think
that
we're
it's
in
really
good
shape.
A
F
A
B
C
A
C
A
Okay,
I'm
just
gonna,
use
language
here
so
cluster
API,
or
is
this
meant
to
be
signature
life
cycle,
so
we
could
say
Sig
cloud
provider.
Is
that
asig.
C
A
So
is
cath
a
part
of
this
or
not
no.
C
A
Cool
so
copy
paste.
C
A
F
A
Okay
I
mean
we
do
regularly
interact
with
other
providers,
but
I
think,
let's
just
not
worry
about
that.
A
A
All
right
cool-
it
is
44
past
the
hour.
C
Yeah
I
mean
sorry,
I
was
just
gonna,
say:
I'm
I'm
really
excited
to
see
John's
like
walk
through
that
he
signed
up
for
on
the
agenda.
So
if
we
can
give
a
bit
of
time
for
that,
that
would
be
great
but
yeah
I
I,
don't
want
to
make
suggestions
for
this
question
because
I'm,
the
one
taking
the
suggestion
so
I
think
it'd
be
great
to
hear
from
others.
A
G
Yeah
I
would
say
one
suggestion
would
be
having
folks
present
ideas
that
maybe
cross
like
cross
cigs
kind
of
like
proposals
that
involve
multiple
books.
G
So
I
I
think
I
I,
don't
know
this
is
just
not
something
to
write
down,
but
just
as
a
note,
one
thing
I
will
give
give
credit
for
is
what
they're
doing
in
multi-cluster
right
now
they
have.
They
have
like
Ping
like
multiple
open
source
projects
filed
issues,
and
they
have
a
spec
that
they're
that
they're
trying
to
push
that
unifies.
G
The
the
cluster
joint
scenario,
so
that
I
feel
like
is
a
good
example
of
the
type
of
thing
that
I
think
there
needs
to
be
more
of
and
I
also
know
that
they
would
probably
have
feedback
on
how
challenging
it
is
to
try
and
get
that
kind
of
thing
to
happen.
But
I
think
we
need
a
lot
more
of
that.
Yeah
and
and
maybe
yeah
go
ahead.
A
Cool
I
was
going
to
say.
Hopefully,
this
is
I,
think
that
this
is
a
very
concrete
statement
of
feedback
that
would
improve
all
the
things
that
you
just
talked
about.
A
Okay,
I
do
want
to
give
John
time
so
I'm
going
to
click
submit.
Do
we
want
this
I'll,
do
this
and
then
I'll?
So
if
anybody
wants
it,
I'm
happy
to
forward
it
from
my
Gmail.
A
A
A
Take
a
run,
no
just
joking,
okay.
That
was
something
that
we'll
do
six
months
from
now
again,
John
I
am
giving
you
the
floor.
Do
you
need
host
key
for
sharing.
H
Yes,
being
able
to
screen
share
would
be
appreciated.
Okay.
A
Cool
so
I'm
gonna
stop
and
I'm
going
to
do
this
is
your
slack
open.
C
Jack
I
think,
since
you
already
claimed
hosts,
you
need
to
make
him
co-host.
He
can't
claim
host
over
you.
Oh.
A
Okay,
so
you're
saying
there's
nothing
to
do.
A
May
more
oh
name
or
okay,
you
should
be
up
John.
Sorry.
H
B
H
Right,
so
this
is
going
to
be
a
lot
of
source
code
for
good
or
for
ill.
So
please
bear
with
me
all
right
so
to
kind
of
start
from
the
very
beginning,
one
of
the
main
jobs
of
cap
Z
is
to
create
and
manage
resources
in
azure,
and
we
tried
to
do
that
consistently
for
many
many
kinds
of
resources,
and
we
separate
these
in
the
cap
Z
code
base
into
what
we
call
services
and
to
try
and
share
as
much
logic
as
possible
between
these
Services.
H
The
async
package
here
provides
a
framework
for
reconciling
any
kind
of
azure
SDK
resource
and
that
heavily
uses
this
resource
spec
getter
interface,
which
is
a
thin
wrapper
around
an
Azure,
SDK
resource
object
and
just
to
kind
of
take
one
example.
This
parameters
method
takes
an
existing
parameter,
which
is
empty
interface
and
it
returns
empty
interface
to
be
able
to
accommodate
any
kind
of
azure
SDK
resource.
H
So,
for
example,
where
in
one
place
where
this
is
implemented,
this
is
the
NAT
gateways
service,
and
so
in
its
parameters
method,
we
can
see
that
it
has
to
take
this
same.
Empty
interface
parameter
to
fulfill
the
interface,
and
one
of
the
first
things
it
has
to
do
is
type
check
that
existing
object
to
see.
Okay,
is
this
actually
a
Nat
Gateway,
even
though
we're
99.9
sure
that
it
is,
but
we
just
want
to
be
extra
safe,
because
we
definitely
don't
want
to
panic
in
the
controller
at
runtime.
H
H
So
for
the
ASO
flavor
of
things,
we
have
a
similar
ASO
resource,
spectator
interface,
and
this
is
a
generic
interface
parameterized
by
a
type
parameter
T,
which
this
will
refer
to
a
ASO
go
object
like
a
resource
Group
or
a
virtual
machine,
or
something
like
that,
and
we
can
see
its
implementation
of
the
parameters.
Method
takes
in
one
of
those
things
as
the
existing
and
it
returns
one
of
those
things.
So
here
the
compiler
will
actually
check
okay.
H
So,
if
I
look
to
see
where
this
is
implemented
for
resource
groups,
we
can
see
its
parameters.
Method
does
take
an
existing
Resource
Group
and
it
returns
a
resource
Group.
So
in
here
we
wouldn't
need
to
do
that
same
sort
of
type
checking
to
see.
Okay,
is
this
thing?
Actually,
a
resource
Group,
because
the
compiler
already
checks
that
for
us
up
front,
so
there
are
a
few
different
places
where
these
kinds
of
bumps
do
get
smoothed
out,
which
is
pretty
cool.
H
So
I
did
start
looking
at
that
and
got
something
working
there
too,
which
is
pretty
cool
so
to
go
backwards
a
little
bit
today.
H
So
now
the
ASO
package
does
provide
a
generic
service
struct
that
works
the
same
way
where
we
parameterize
this
over
a
t
which
is
the
same
ASO
resource
type
like
Resource,
Group
or
virtual
machine,
and
a
scope
which
is
kind
of
glue
between
the
cab,
Z
resources
and
these
services,
and
this
service.
Struct
type
does
Define
the
same
reconcile
and
delete
methods,
and
they
follow
kind
of
the
same
pattern
where
we
have
some
boilerplate
Loop
through
all
the
resources,
Creator
update
them
and
then
update
status
at
the
end.
H
Now
embeds
this
ASO
service
for
resource
groups
and
B
group
scope,
and
we
don't
even
Define
the
reconcile
and
delete
methods
because
we
just
inherit
them
from
this
ASO
service.
So
this
takes
out
a
ton
of
code
and
I
think
this
will
propagate
throughout
all
the
services
where,
as
we
convert
these
to
ASO,
we'll
be
dropping
a
lot
of
code
along
the
way
which
I
think
is
pretty
cool
and
throughout
all
this,
we
still
have
all
the
type
safety
type
things
that
I
showed
earlier.
H
So
there's
no
empty
interface
or
any
types
anywhere
like
that,
so
those
are
kind
of
the
main
highlights
from
that
ASO
generics
PR.
H
So
if
you're
interested,
please
feel
free
to
take
a
look
and
leave
any
comments
or
questions
you
have
there
I
know
we
only
have
a
couple
minutes
left
and
I've
been
sorely
neglecting
chat,
but
I
will
take
a
look
at
those
now
or
if
anybody
has
any
questions
feel
free
to
raise
hand
and
I
will
be
happy
to
answer
those.
A
Yeah,
this
is
great.
The
only
thing
that
I
would
say
with,
because
we've
all
been
using
go
for
a
long
time,
and
so
this
new
abstraction
concept,
as
you
just
totally
demoed,
reduces
like
more.
C
A
Than
your
even
your
adjectives
are
using
like
this
is
going
to
reduce
a
ton
of
code,
but
it
is
going
to
replace
that
code,
that's
in
source
with
some
more
burden
in
the
individual
human
maintainer's
brain,
because
there's
a
little
bit
of
magic
going
on
so
I
I
would
love
to
to
get
everyone
who's
involved
in
the
project
more
exposure
to
this,
so
that
we
can
prime
our
brains
to
sort
of
interpolate.
What's
now
missing
in
apps,
you
know
actual
concrete
code.
A
This
is
like
fabulous.
It's
just
an
a
novel
like
exposure
to
this
there's
like
a
little
bit
of
magic
because
it
just
seems
like
wow
and
unlike
something
like
Java,
which
imposes
more
at
like
this
sort
of
comparable
level
of
abstraction
in
a
language
like
Java
imposes
a
lot
more
boilerplate
requirements
in
my
experience
and
so
the
as
you're
maintaining
and
reading
through
the
code.
You
do
have
that
like
on
paper,
so
to
speak,
what
those
abstractions
are
actually
doing,
whereas
this
I
think
there's
there's
less
it's
like
even
more
concise
than
that,
but.