►
From YouTube: WG API Expression Bi-Weekly Meeting for 20210413
Description
WG API Expression Bi-Weekly Meeting for 20210413
A
All
right
welcome
to
working
group
api
expression,
it's
the
13th
of
april
2021..
I
think
today's
our
artificial
deadline
right.
B
It's
the
15th,
so
we
have
two
days.
B
Yeah,
do
you
do
we
want
to
talk
about
that?
How
do
we
want
to
talk
about
the
items
first,
and
I
don't
know
if
eddie
eddie
john
hanging
out
nothing
specific,
okay,
okay,
let's
maybe
start
with
the
whatever.
However,
you
want
carrying
it's
your
item.
A
Yeah
yeah
I'd
love
to
if
more
people
have
ideas.
I
was
like
scratching
my
head
a
bit,
but
especially
merging
part.
I
I
don't
know
too
much
details,
I'd,
probably
link
to
some
places,
but
yeah
it's
hard
to
come
up
with
the
differences
from
scratch.
A
B
A
C
A
C
A
I
mean,
though,
by
the
way,
I
think,
your
membership
pr
got
merged
right.
A
All
right,
sub
resources.
How
are
we
doing.
B
B
D
B
I
mean
I'm
hoping
we
can
get
it
much
by
the
end
of
the
week.
That
would
be
nice.
A
B
And
so
we
just
want
to
make
sure
that
if
apps
b2
deployment
happens,
that
we
have
the
right
mapping
to
find
the
field
and
also
when
we
see
a
version
that
we
don't
know,
we
are
removing
the
entire
entry
and
we
don't
want
to
make.
We
want
to
make
sure
that
we
don't
remove
entries
just
because
we
forgot
to
update
the
mapping.
B
A
E
B
E
It
down
on
it.
Okay,
if
you
all
want
to
take
a
look,
it's
pretty
fresh.
They
also
demoed
at
the
last
6
cli
bi-weekly.
If
you
want
to
dig
up
that
recording,
I
can
send
it
to
you.
That's
that's
good!
Okay,.
B
A
A
A
D
A
All
right,
yeah
and
the
last
one
remaining
is
the
client
go
sub
resource
support
was
that
the
extract.
B
B
Yeah,
that's,
I
think
so.
One
of
the
two
is
launched
first
and
the
second
one
is
not
much
because
it
depends
on
the
sub
resource
field.
It's
three
commits,
I
think,
they're
good.
We
need
someone
to
approve
them
and
I've
actually
split
entry
fpr
into
the
sub
resource
field
and
the
tracking,
so
that
we
can
maybe
maybe
more
easily
match
the
first
part
and
unstuck.
B
But
I'm
I
can,
I
can't
get
an
upper
ball.
I
need
to
ping
jordan
and
daniel
again
to
get
the
pool
on
the
subway
so
spout.
B
F
So
for
documentation,
is
there
any
prs
or
I
know
the
blog
is
like
the
entry
point,
but
do
we
need
to
discuss
anything
at
seek
a
dark
meeting
today?
They
are
looking
into
anything
that
we
want
suggestions,
so
I
can
represent
our.
B
B
And
so
I
had
the
feedback
from
karen,
who
had
already
helped
me
on
some
other
set
of
play,
pl
so
she's.
I
think
she's
somewhat
familiar
with
the
topic.
She
made
a
lot
of
good
comments
and
feedback,
so
I'm
gonna
fix
it,
and
I
was
thinking
about
just
talking
to
her
about
general
improvements.
She
had
in
mind,
so
we
can
talk
about
it
during
the
sick
meeting
or
we
can.
I
can
trust
doctor
khan.
I
think
that's
also
fine.
F
I
think
it
is
good
if
we
we
put
it
in
on
their
door,
so
they
can
take
a
look
but
anything
that
makes
it
easy
for
you,
I'm
open
to
your
suggestion.
So
what
do
you
think.
D
F
If
we
need
ideas
or
technical
details
that
is
related
to
our
own
things,
we
cannot
ask
there,
but
if
there
is
something
that
they
just
need
to
approve
it
for
sick
dogs,
they
can
facilitate
that,
but
other
than
that
there
is
nothing
that
they
can
do.
So
if
you
are
confident
about
like
I'm,
not
sure
what
what
we
want
to
put
in
and
like
I
see
there
are
like
changes
and
the
comments
from
daniel
and
kevin
also
reviewed
it.
B
B
We
have
many
different
types
of
users
or
different
scenarios
and
it's
sometimes
hard
to
know
what
and
who
are
we
documenting
for,
and
so
I'm
curious
if
they
have
suggestions,
maybe
on
how
we
should
organize
the
documentation
like
we
have
operators,
we
have
users,
we
have
api
authors
and
it's
kind
of
a
massive.
F
Find
I
can
talk
about
this
the
last
time
I
bring
up
this
about
like
what
are
the
best
practices
that
we
can
look
into,
or.
F
Suggestion
was
just
attending
these
meetings
and
we
learned
together
about
the
best
practices,
so
there
were
not
something
that
they
can
point
to,
but
I
think
by
going
yeah
by
going
into
today's
meeting,
I
can't
find
out
more
and
yeah
sounds
good.
A
B
B
Okay,
I
think
we
need
to
the
the
piece
that
is
missing.
So
a
lot
of
these
comments
that
we
can
see
on
your
screen
about
documentation
are
about
the
type
specifically
of
the
topology,
so
I've
tried
to
address
all
of
these
in
this
vr.
B
There's
probably
comments
we
can
make
in
the
crd
authoring
section,
even
if
it's
just
pointing
to
this
section,
specifically,
I've
made
a
pr
in
the
api
convention
so
that
people
write
apis,
know
how
to
go
and
look
for
this
page,
but
it
probably
applies
also
to
people
writing
crds,
so
we
may
want
to
mention
it
in
the
crd
documentation.
I
don't
think
we
have
I'm
going
to
do
something
wrong
here.
Okay,
I
don't
think
we
have
this,
so
we
would
ideally
need
someone
to
look
at
these.
B
Well,
I'm
leaking
my
entire
team
at
google,
but
does
anyone
want
to
work
on
the
default
in
api
conventions.
A
B
I
will
find
it
like
this,
but
I
think
this
is
addressed
in
ipr,
but
it's
not
specifically
for
serious.
So
I
think
this
link
is
kind
of
missing.
A
lot
of
these
things
are
already
addressed,
such
as
this
map
type.
That's
more
like
a
programming
option.
B
If
we
think
someone
should
use
the
list
map
keys,
we
want
to
print
a
warning.
B
C
B
B
Question,
do
I
I
don't
know
we
should
ask,
can
you
ask
ciao
ciao,
I
think
you
know
yeah.
I
think
in
my
memory
knows
about
the
client
go
about,
so
maybe
he
knows
about
the
documentation.
A
Maybe
I
don't
know
if
you
can
put
examples
or
if
you
already
have
examples
in
the
in
the
go
codes
to
show
in
the
go
doc,
but
do
we
also
want
to
or
will
controller
runtime
do
that
add
like
they
have
those
this
controller
runtime
book
docs
book
how
to
build
a
controller?
Do
we
want
to
be
in
there.
A
While
I
was
doing
this
this
document,
I
actually,
I
think
I
asked
it
last
time-
I'm
not
even
sure
how
field
deletion
works.
Is
it?
Is
it
true
that
we
can
just
set
a
field
to
null
and
it
will
be
emptied.
B
We
already
have
some
things
about
deletion
in
the
main
documentation
and
I've
seen
people
some
team
at
google
created
some
machinery
on
top
of
these
mechanisms,
and
so
it's
we
should
do
a
better
job
of
documenting
these
yeah.
B
But
it
depends
on
many
things:
that's
the
prime
right!
If
it's
built-in
type
and
we're
talking
about
it,
depends
if
we're
talking
about
a
struct
or
field
that
is
omit
empty
or
yeah.
That
is
a
pointer
or
not.
If
it's
a
panel,
then
it's
probably
gonna
remove
it.
If
it's,
if
it's
not
a
pointer,
then
it's
probably
gonna
reset
it
to
the
zero
value
which,
if
it's
too
many
times
g,
is
probably
going
to
remove
it.
B
A
A
A
Yeah,
exactly
like
the
lesion
would
be
one
topic
where,
where
I
could
imagine
that
stuff
changed
on
the
way
and
the
documentation
is
not
the
news
anymore
yeah,
I
I'd
hate
to
to
have
a
good
release,
but
actually
still
surprise
people
with
stuff.
That's
documented
a
different.
A
B
I'm
good:
let's
try
and
get
these
dogs
pr
merged
as
soon
as
possible.
I
don't
think
the
15th
is
going
to
be
reasonable,
but
let's
try
and
get
them
merged.
Ideally
this
week.