►
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
There
we
go
hello,
everyone
and
welcome
to
the
valero
community
meeting
today
is
april.
27
2021.,
as
you
can
see,
we've
got
a
bunch
of
attendees
here
which
is
fantastic.
I
love
it.
It's
a
new
attendee
list,
so
please
add
your
name
in
there
we're
going
to
start
up
with
some
status
updates.
Then
we
have
a
few
discussion
topics
and
contributor
shoutouts,
just
like
a
regular
community
meeting.
So
first
off
we
have
dave
with
some
team
updates.
A
B
So,
just
let
everybody
know
nola
and
I
are
swapping
hats,
so
nolan's
gonna
take
on
the
architect
cat
and
I'm
gonna,
be
the
team
tech
lead
rolling
forward
other
than
that
no
real
changes
at
the
moment.
B
All
of
the
stuff
we're
doing
as
far
as
the
one
seven
payload
remains
the
same
and
then
for
myself
trying
to
get
the
upload
progress
back
finished
off,
made
some
minor
changes
to
that,
and
we
need
to
review
that
and
get
that
merged
in,
and
you
know
working
with
the
team
as
a
whole
to
get
all
the
design
stuff
going.
A
Awesome
so
we'll
we'll
have
to
do
a
slight
update
to
the
the
website.
I
think
yes
put.
A
That's
good
all
right.
Any
questions,
comments
for
dave.
A
C
A
C
Yeah
so
relevant
to
the
roadmap.
I've
been
getting
up
to
speed
on
the
carvel
suite
of
tools.
I'm
sorry
carvel
like
marvel
this
is
this
will
be
for
packaging
up
valero
in
a
way
that's
compatible
with
the
tkg
product
going
forward,
but
all
other
people
may
can
certainly
use
it.
So
I'm
pairing
with
carlysi
on
that,
but
I
I
do
need
to
get
up
to
speed
on
this
suite.
I'm
not
super
familiar
with
everything
and
then
the
other
relevant
item
is.
C
I
think
it's
fairly
simple,
but
it
requires
an
update
to
go
116
and
I
want
to
describe
how
we're
going
to
package
some
of
the
crash
diagnostics
or
crash
d
scripts
into
the
binary
before
I
actually
start
coding
work
on
that.
So
those
are
the
two
big
things
for
the
roadmap
during
this
two-week
sprint
that
we've
kind
of
done
internally.
C
I'll
also
mention
carlysi
and
I
are
going
to
be
joining
dylan
murray,
who
is
contributor
in
the
valero
community
at
kubecon
eu
for
a
session
on
conveyor.
I
do
not
have
the
time
in
front
of
me,
but
we're
meeting
up
to
to
discuss
that
stuff.
This
week,
too,.
A
I'll
make
sure
that,
let's
add
it
to
the
meeting
notes
here
as
well,
the
link
to
the
session,
that's
so
cool
and
yeah,
I'm
guessing
within
the
next
few
weeks,
we'll
have
a
design
conversation
around
the
debug
command.
C
Yeah
and
honestly,
I
think
the
the
biggest
change
will
be
in
the
build
process,
but
I
haven't
actually
like
dove
in
because
it
will
require
inserting
some
text
into
the
valero
binary,
but
I
know
go
win16,
build
tools
allow
for
that.
So
that's
the
main
thing
I
want
to
get
in
the
design
dock,
but
it's
not
produced
yet.
A
Sounds
good
all
right
next
up,
bridget.
D
Hey
everyone,
so,
for
the
last
week
I've
been
mostly
spending
my
time.
I
continue
the
work,
the
design
work
for
plug-in,
versioning,
maybe
feeling
a
little
bit
behind
schedule
now,
but
I'm
hoping
to
have
an
initial
draft
of
a
design
dog
up
by
the
end
of
this
week
for
folks
to
review,
because
I
know
it
impacts
a
lot
of
the
the
other
work
that
we're
applying
for
one
seven.
So
I
want
to
get
feedback
from
that
as
soon
as
possible.
A
So
having
a
design
talk
conversation
around
that
too.
D
Yeah,
unfortunately,
I
won't
be
at
the
next
creamy
mean
because
I'm
moving
twice
next
week,
but
I'm
hoping
that
if
I
can
get
the
the
initial
draft
night
folks
I'll
have
time
to
review
and
then
maybe
we
can
pick
it
up
at
the
meeting.
After
so
in
two
weeks.
E
A
E
Last
week
I
did
a
I
assisted
dave
with
mckay
with
the
valero
walkthrough,
but
that
was
very
cool.
We
had
plenty
of
time
to
discuss
little
details
of
bolero.
E
Yeah,
I
thought
you.
I
sorry.
E
I
need
to
find
out
what
this
moving
thing
is.
It's
driving
me
nuts.
I
have
been
also
continuing,
researching
carvel.
I
have
my
next
step
in
the
process
is
installing
it
I'm
not
installing.
I
have
already
installed.
So
it's
really
plain
using
it
to
figure
out
what
the
possibilities
are.
I
do
still
have
to
open
a
ticket
I'll.
Do
that
today
to
get
like
figure
out
what
the
requirements
are.
First,
that
we
need
to
fulfill
to
to
get
this
done
and
then
for
the
next
prints.
E
I
will
have
the
design
document
done,
but
that's
farther
down
the
line
and
try
to
catch
up
with
pr
reviews.
There
are
some
house
cleaning
items
that
I've
been
working
on.
I
have
some
pr's
open
here
and
there
and
that's
it
for
me.
A
Jordan,
sweet
all
right,
diving
into
the
discussion
topics.
Eleanor.
F
Yes,
I
had
two
questions.
One
is,
I
know
that
there
was
kind
of
pain
around
people
have
been
asking.
Yay
people
are
coming
to
the
valeria
slack
channel
on
kubernetes,
but
people
are
asking
a
bunch
of
support
questions
and
I
know
that
we
were
trying
to
drive
them
to
github
so
just
last
week.
I
realized
that
I
especially,
I
think,
can
do
more
of
the
driving,
because
if
an
engineer
goes
and
says,
hey
go
elsewhere,
it's
kind
of
like
well
engineer.
Why
aren't
you
answering
my
question?
F
D
D
Situation
on
the
channel
and
I
feel
like
I've,
immediately
forgotten
what
it
was
like
last
week.
Yeah,
maybe
I
think
maybe
last
week
was
like
a
little
bit
quieter.
But,
yes,
I
think
it.
It
was
helpful.
I
think
things
went
there.
I
hope
they
were
addressed.
Sorry,
I'm
doing
a
terrible
job.
F
F
Was
like
a
huge
problem,
so
I'm
gonna
keep
trying
to
encourage
people
to
post
on
github
because
then,
as
as
it
says,
dave,
I
think,
pinned
a
post
saying
it
makes
it
easier
to
look
back
at
old
issues
and
the
corollary
to
that
is
oh,
and
by
the
way
I'll
mention,
I
asked
a
bunch
of
people
to
move
it,
and
most
people
were
like.
Oh
I'm,
so
sorry
or
a
few
people
didn't
respond
at
all
at
all,
and
then
I
guess
their
shoe
got
resolved
elsewhere.
F
But
there
were
some
kind
of
general
discussion
questions
and
I
guess
the
thing
I
wanted
to
bring
up
here,
especially,
is
what
kind
of
discussions
do
we
want
on
the
slack
channel
versus
what
do
we
want
on
the
github
general
discussion
page?
So
to
me,
a
hey.
Is
this
going
to
be
on
the
roadmap,
or
what
do
you
think
of
the
roadmap
should
definitely
be
on
the
slack
channel,
because
that's
very
much
a
like
team-wide
everyone
eyes
on
it
sort
of
question.
F
I
do
know
that
there
are
some
questions,
I'm
just
pulling
it
up
now
that
were
like,
oh,
maybe
maybe
another.
F
You
know
kind
of
does
valero
do
this,
does
vlaire
do
that
those
I
don't
know
what
to
do
with
so
I'm
gonna,
just
for
instance,
does
valero
pick
up
the
pending
delete
crds
for
deletion
and
delete
corresponding
backups
eventually,
what
do
we
folks
think
should
that
be
driven
to
github?
Is
that
a
support?
Is
that
a
discussion
but
for
github,
or
is
that
discussion
for
slack.
C
I
think
a
metric
that
might
be
helpful
is
if
it
takes
more
than
10
minutes
to
really
respond,
including
back
and
forth.
I'm
going
to
include
back
and
forth
to
respect
our
time.
Then
it
should
probably
go
to
github
that
specific
one,
I
think,
could
be
answered
with
yes,
but.
C
E
I
have
one
more
one
additional
take
on
the
answer
to
this
question.
I
I
would
ask,
would
the
answer
to
this
question
be
used
for
would
be
durable
and
useful
to
other
people
in
the
future.
If
the
answer
is
yes
should
go
in
the
github
q,
a
because
it's
much
easier
to
find
in
there
it
for
things
that
are
ephemeral,
sure
you
just
use
slack
it's.
I
think
it
makes
more
sense.
F
And
I
will
say
nolan
I
like
your
metric
of
10
minutes,
unfortunately,
because
I'm
so
new
to
valero
tech,
wise.
I
have
no
idea
if
it's
a
10
minute
thing
or
not,
I
can
probably
evaluate
on
carlesia's
metric.
Maybe
I
can
guess
so,
should
I
maybe
suggest
maybe
I'll
just
yeah,
maybe
I'll
write
up
a
little
like
blurb.
I
can
make
it
as
a
pin
post
and
I
can
copy
it
in
saying
what
carlesia
said.
How
do
folks
feel
about
that
and
to
be
clear
I
just
want
to
do.
F
I
want
to
help
you
all
out.
I
want
to
make
it
help
you
all
out
like
not
getting
questions
where
you
don't
want
them
and
of
course
I
want
to
help
the
community
by
having
a
good
collection
of
answers,
so
it
doesn't
matter
to
me
either
way.
So
do
you
want
me
to
maybe
take
carlesia's
answer
condense
it
down
and
direct
it
to
those
kind
of
more
general
questions.
B
I
think
so
I
think
we
want
to
keep.
I
mean
slack
should
be
like
quick
conversations
like
hey.
Did
this
tr
get
merged
things
like
that?
The
good
thing
about
getting
the
discussion,
so
we
have
the
the
discussions
and
the
pull
requests
on
github
and
the
good
things
about
getting
stuff
into
both
of
those
is
that
you
can
google
search
for
them
and
if
somebody
does
a
google
search,
they
don't
see
what
happened
in
the
slack
channel.
B
F
F
My
other
question
was
to
be
blunt.
F
You
know
in
vmware
we
kind
of
certainly
track
our
open
source,
not
term,
but
we
kind
of
have
an
open
source
meeting
where
we
talk
about
our
projects
and-
and
one
of
the
questions
was
like,
what's
community,
what's
the
health
of
the
community,
and
I
know
that
there
are
a
few
metrics
that
would
make
sense
to
think
about
the
health
of
the
valero
community
and
I'll
mention
I
mean
I
was
asked
this
in
the
meeting,
but
I
do
think
it's
a
really
good
thing
to
track.
I
want
to
know,
are
we?
F
Are
we
helping
the
valero
community
grow?
So
I
know
that
we
can
think
about
tracking
contributors,
or
we
can
talk
about
think
about
tracking.
Like
prs.
Has
anyone
in
the
past
tracked
valeria,
community,
health
and
jonas?
Forgive
me
if
this
is
directly
to
you.
A
Yeah,
it
is,
and
yes
we
have
so
we've
been
doing
community
health
checks
on
a
roughly
half
year
basis.
F
A
Last
year,
and
then
we
did
another
one.
In
january,
in
february
we
started
deploying
a
a
proper
measurement
system
as
well
for
for
certain
things,
so
that
is
still
being
built
out,
but
I'm
happy
to
show
you
what
we
have
so
far
and
see
if
that's
useful,
for
you.
F
A
Yeah
we
we
want
to
make
those
things
as
public
as
possible
later
on
as
well
the
that's
the
plan.
F
A
Yeah
and
for
and
for
the
other
community
as
well
so
right
now
within
vmware,
we
have
project
guidelines
like
a
checklist
of
things,
that
every
project
should
do
as
they're
getting
open
sourced
or
just
after
they're
being
open
sourced
like
opened
up
on
github
and
then
the
the
health
check.
We
actually
have
the
measurements
written
down
as
well
and
both
of
the
the
guidelines
and
the
health
check
are
being
open
sourced
within
the
next
couple
of
weeks.
So
we
can
always
point
to
those
things.
A
G
I
just
have
a
question
on
the
visioning
blocking
versioning.
Do
we
have
any
update
on
that
yet.
D
So
I'm
currently
working
on
a
design
dock
which
mentioned
earlier,
but
I
will
yeah
I'll.
Hopefully
my
plans
have
the
the
draft
of
the
design
doc
shared
by
the
end
of
the
week
and
I'll
tag.
You
and
my
plan
was
to
tag
both
you
and
and
scott,
and
it's
ensure
doing
work
which
depends
on
getting
that
feature
into
valero.
So
I
will
I'll
include
you
in
the
the
review
for
the
design
dock
and
then
we
can
hopefully
bring
that
information
forward
to
help
progress.
D
Problem
yeah
then,
hopefully
as
well,
we
can
once
once
we
progress
a
little
bit
more
in
the
design.
Then
we
can
start
to
to
work
together
a
bit
more
on
those
features
that
require
the.
C
Yeah,
so
the
first
two
are
some
some
typos
that
we
certainly
appreciate
having
fixed
I'm
going
to
apologize
and
I'm
not
sure
how
to
separate
this.
This
name
arun.
Okay,
thank
you.
Arun
for
fixing
up
the
typo
also,
I
believe,
jose
for
fixing
up
another
typo,
those
things
sneak
in,
and
we
appreciate
your
help
in
cleaning
that
up
the
next
one,
I
think,
is
a
little
bit
of
sad
news
for
us.
Carlos
panato
is
stepping
down
from
helping
maintain
the
helm
chart.
C
He
was
a
great
help
while
he
was
working
on
it,
but
he
he's
moving
on.
So
thank
you
very
much
for
all
the
time
you've
put
in
and
all
your
help
with
helm
carlos.
We
appreciate
it
and
hopefully
enjoy
the
free
time.
C
The
next
one's
genting
is
is
a
maintainer
on
the
valero
team,
but
I
just
want
to
give
him
a
shout
out
for
continuing
to
move
stuff
forward,
cleaning
up
the
issue
templates,
making
sure
there's
some
other
helm
things
in
here.
Let's
see
basically,
genting
has
been
driving
a
lot
of
the
helm,
chart
work
and
really
appreciate
that.
That's
been
super
helpful,
he's
a
fixed
home,
upgrade
issues
and
he
also
helped
fix
up
some
issues
on
our
aws
plugin.
A
Great
to
have
you
here,
genting,
I'm
gonna,
give
you
some
some
more
fantastic
feedback
on
things
you've
built
here.
C
C
No,
that's,
okay!
Thank
you
for
finding
this
issue
and
and
fixing
it
I
know,
helm
with
crds
is
tricky
and
often
there's
it's
easy
to
run
into
issues
with
with
helm
and
crds.
So
thank
you
for
finding
this
and
fixing
it
up,
and
then
the
next
one
was
some
changes
to
the
aws
build
process.
I
believe
yeah
the
publishing,
so
thank
you
for
fixing.
Oh,
this
was
github
actions.
Wasn't
it
thank
you
for
fixing
that
up
and
thank
you
for
all
your
contributions
to
the
project.
A
E
E
Have
a
hard
time
pronouncing
some
names
that
should.
E
Sorry,
I
didn't
link
to
the
answer,
but
the
other
contributor
as
well,
for
let
me
see
he
she
well.
This
person
does
not
have
a
spelled
out
name
on
the
github
profile
and
I'm
not
even
gonna
try
to
pronounce
that,
but
they
answered
questions
on
the
github
discussion
and
they
were
marked
tests.
The
correct
answer
so
thank
you.
A
Awesome,
thank
you
all
contributors.
You
are
fantastic,
and
so
with
that
that
er
ends
the
valero
camera
meeting
for
april
27th
2021
have
a
fantastic
rest
of
the
week.
Everyone
see
you
all
on
slack
and
everywhere
else,
tatsu.