►
From YouTube: Carvel Community Meeting - April 19, 2021
Description
Carvel Community Meeting - April 19, 2021
We meet every Monday at 11:30am PT / 2:30pm ET. We'd love for you to join us!
Agenda notes from this meeting can be found here: https://hackmd.io/F7g3RT2hR3OcIh-Iznk2hw?view#April-19-2021-Agenda
A
A
So
please
read
and
abide
by
our
code
of
conduct,
which
is
listed
here
in
the
agenda
when
you
attend
these
meetings,
if
you
have
anything
you
wish
to
discuss
while
attending
this
community
meeting,
please
do
so
do
add
that
to
the
discussion
topics
or
if
there's
any
triage,
help
you
can
place
it
replace
this
note
with
your
trial
triage
help
issue
or
down
here,
replace
it
with
your
discussion
topic
and
we
will
get
to
it
for
anything
that
we
don't
get
to.
A
A
However,
this
the
next
time
we
meet
for
carnival
office
hours
is
this
week
on
april
22nd
and
we've
modified
it
a
little
bit
and
have
turned
it
into
a
kind
of
a
working
group
session.
A
The
goal
here
is
to
discuss
this
particular
proposal
and
you
know
get
feedback
on
the
document.
We
we
invite
the
community
to
join
us
for
that
particular
working
group
session
and
just
you
know,
provide
all
the
feedback
that
you
may
have
regarding
this.
So
I
encourage
you
to
read
that
over
and
attend
that
meeting,
which
again
is
april.
22Nd
11,
30
a.m,
pacific
time,
2,
30
p.m.
Eastern
time,
and
with
that,
I
will
kick
it
on
over
to
aaron
hurley,
to
start
off
with
status
updates
and
the
rest
of
the
agenda
items.
B
Let's
see
I'm
trying
to
think
about
other
announcements
and
I
think
on
the
release
front,
we
we
did
release
a
patch
release
of
image
package,
zero,
6.1,
some
some
bug
fixes
in
there
that
were
discovered
last
week.
I
don't
know
anything
else
to
share
on
that.
B
One,
no
cool
some,
some
fairly
minor
bug
fixes,
but
let's
maybe
chat
about
where
we
are
with
our
various
tracks,
so
schemas
v1.
It
is
currently
in
progress.
I
know
john
or
carrie,
one
of
you
all
wanna
share
how
the
past
week
went.
C
Yeah
we're
making
progress.
We
can
do
this
together.
Carrie
there's
actually
like
quite
a
bit
of
work
that
got
done
this
last
week.
Carrie
will
talk
to
this
like
to
the
point
where
we
feel
like
it's
really
important,
that
we
focus
on
getting
a
release
available.
C
C
In
order
to
incorporate
some
of
the
features
we
want
out
of
schema
things
like
being
able
to
overlay
on
nulls
being
able
to
detect
when
a
file
a
yaml
file
is
a
template
when
it's
not
in
and
choose
the
right
behavior,
which
has
been
something
that
folks
have
been
wanting
for
some
time,
there's
a
bunch
of
stuff
in
there
and
we're
in
the
process
of
pulling
together
the
the
contents
for
that
release.
C
But
we
continue
on
to
stay
focused
on
getting
this
first
milestone
for
schema
as
complete,
which
is
about
thoroughly
supporting
type
checking
in
all
the
different
parts
of
ytt,
including
libraries
and
things
of
that
sort
kerry.
Can
you
think
of
anything
in
there?
I
might
have
missed
in
terms
of
like
progress
this
week
or
anyone
else,
but.
B
Sounds
good,
thank
you
and
then
we
also
have
some
schemas
v2,
so
so
work
outside
of
type
checking.
That
is
on
our
radar
and
actively
being
defined.
A
couple
proposals
here
are
listed.
The
accept
unattended,
unannotated
yaml
as
data
values,
best
practice
layers.
Call
it
plain
yaml
since
unannotated
is
difficult
to
say
and
then
another
proposal,
that's
currently
being
defined
being
written
is
support
exporting
open
api
from
ytt
schemas.
B
C
Yeah
we're
pretty
excited
about
the
the
value
in
going
through
the
proposal
process
here,
actually
helped
us
make
some
great
choices.
With
that
first
proposal
we
were
actually
looking
at
creating
a
special
type
of
file
mark
within
ytt
and
on
further
reflection.
As
we
were
working
through
the
conversations
around
the
proposal,
we
realized
that
there
was
a
better
compactness
to
thinking
about
this
input.
C
As
an
actual,
it's
obvious
when
I
say
it
out
loud,
like
an
extension
of
the
data
values
flags
so
so
anyway,
so
we've
actually
reworked
a
whole
bunch
of
that
proposal
to
take
in
that
insight,
so
we're
actually
really
excited
about
getting
that
release.
It's
going
to
affect
not
just
those
who
are
integrating
with
ytt,
but
those
who
are
actually
using
it.
C
We're
hoping
it's
going
to
improve
the
overall
experiences
folks
get
started
with
that
and
then,
in
terms
of
the
open
api
support,
we've
got
a
whole
bunch
of
work
there
that
we've
defined
out
in
terms
of
hey,
given
a
ytt
schema,
convert
that
to
open
api
json
schema
and
also
looking
into
exploring.
How
can
we
support
some
of
the
use
cases
beyond
just
knowing
what
are
the
configuration
items,
but
maybe
even
providing
a
way
for
capturing
some
ui
hints?
C
So
if
you
have
a
gui
tool
that
is
presenting
making
a
giving
a
nice
presentation
to
the
end
user
that
you
can
actually
include
hints
about
like?
Oh,
I
only
want
to
show
this
if
this
condition
occurs
or
I
want
to
use
this
widget
for
this
particular
data
value,
or
this
is
not
even
something
you
should
present
in
a
gui,
so
we're
looking
and
exploring
in
those
things
within
that
work
as
well,
but
yeah
click.
The
links
take
a
look,
always
love
your
feedback.
B
E
B
Cool
and
then
we
also
have
a
track
of
work
ongoing
around
the
package
manager,
api,
mvp,
eli
or
daniel.
I
want
to
share
there.
F
B
B
C
C
Cool
other
there
was,
there
was
one
one
bit
about
the
oh,
I
think
it's
in
in
the
new
new
issues
pipeline.
So
it's
that
same
epic,
but
the
new
new
issues,
yeah.
C
So
this
one
we
were
talking
about
bring
it
in
yeah.
D
Yeah
we've
had
a
couple
of
people
from
the
community
ask
when
the
next
ytt
releases,
and
so
we
have
sort
of
been
prompted
to
figure
out
what
has
been
changed
since
our
last
release
on
january
11th.
D
So
this
issue
is
specifically
to
just
track
that
and
like
gather
the
release,
notes
for
what
has
been
changed,
because
the
amount
of
work
on
develop
is
a
little
bit
larger
than
our
usual
releases.
We
decided
to
create
a
entire
issue
to
track
this,
so
there's
some
work
that
will
be
part
of
this
that
are
specific
to
schemas
and
behind
the
schemer
in
feature
flag
and
then
there's
some
work
that
is
not
behind
the
schema
future
flag,
such
as
a
couple
of
things.
D
That
john
was
mentioning
at
the
beginning
of
the
meeting
overlaying
onto
null
values.
The
default
merge
operation
for
array
items
when
you're
overlaying
an
array
item.
The
default
operation
is
now
to
append
them.
So
we
want
to
get
these
things
out
in
a
release
and
this
stories
to
track
them.
B
Cool
that
sounds
good.
Do
you
want
to
point
this
story
and
discuss?
I
don't
know
surface
any
complexities.
C
B
Yeah,
maybe
I'll
just
open
it
up.
If,
if
folks
like
do
folks,
have
any
additional
comments
be
on
what
what
kerry
and
john
have
shared.
B
All
right:
well,
maybe
we
don't
need
to
further
discuss
this.
One
then
does
this
look
like
the
right
spot
in
the
backlog.
Is
this
prioritize
that
I
guess
as
like
the
next
thing
we'll
pick
up.
D
B
B
So
I
know
that
we
have
this.
This
image
package
story
provide
copy
progress,
feedback,
any
ideas,
if
we're
unblocked
here,
yet
we're
still
blocked
we're
waiting
for
gcr
to
cut
a
release.
Okay,
leave
that
one
there,
and
then
we
have
two
other
image
package
stories
here
at
the
top
again,
this
is
a
shortened
week.
I'm
I'm
guessing
that
the
amount
of
stuff
that
we
already
have
pointed
it's
probably
going
to
be
plenty
of
runway,
especially
since
we
are
trying
to
paralyze
on
on
the
schema's
track
as
much
as
possible.
A
Twice,
okay
sounds
like
we
had
a
pretty
short
community
meeting
this
go
around,
which
is
nice
ties
into
our
short
week,
we're
having,
which
means
we
have
earth
day
to
celebrate
this
week.
So
please,
you
know,
do
what
you
can
to
celebrate
the
planet
that
we
live
on,
but
I
do
encourage
you
to
also
meet
with
us
this
thursday
for
our
office
hours.
We
do
have
some
lengthy
discussion
there
to
be
had
again
that's
on
the
agenda
and
also
put
it
within
the
youtube
description
while
you're
watching
this
from
home.
A
We
meet
for
those
office
hours
every
second
and
fourth
thursday
of
the
month
at
11,
30
a.m,
pacific
time,
2
30,
p.m,
eastern
time,
and
then
we
meet
every
monday
for
our
carville
community
meeting.
At
the
same
time,
11
30
a.m,
pacific
time,
2,
30
p.m.
Eastern
time,
so
we
look
forward
to
seeing
you
around
thanks
again.