►
From YouTube: Velero Community Meeting - November 15, 2022
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
All
right,
hello,
everyone
today
is
November
15th
and
that's
the
official
community
meeting
for
Valero.
Please
follow
the
comic
conduct.
My
name
is
Irene
wasillaf
and
I'm.
The
community
manager
with
that
said,
I
I've
pasted
the
link
to
the
hack
MD.
So
you
can
add
yourself
if
you
feel
like
it
into
the
hack
MD
page
for
our
meeting
and
add
your
topics
as
well.
A
I
can
see
a
few
folks
already
done
that.
Thank
you
very
much.
So
with
that
I
think
we
can
kick
off
with
Scott.
He
he
had
added.
He
added
some
status
updates.
Let's
go
go
ahead.
Yeah.
B
Sure
so
the
ongoing
review
of
the
async
item
action
design
that
we're
again
hoping
to
get
in
early
in
the
111
development
time
frame.
B
Basically,
the
original
design
just
had
a
couple
of
fields
had
a
couple
of
fields
for
items
completed
in
items
total,
which
the
intent
in
the
context
of
a
volume
upload
was.
You
know,
total
number
of
bytes
and
upload
a
number
of
bytes,
but
discussion
with
Daniel
and
others.
We
kind
of
realized
that
that
wasn't
flexible
enough
to
handle
kind
of
the
anticipated
set
of
use
cases,
and
so
one
suggestion
given
was
hey.
B
Let's
just
make
it
a
Stringfield
put
yaml
in
it
and
I
kind
of
sort
of
thought
about
that
and
kind
of
came
up
with.
Another
idea
am
I
concerned
with
the
yaml
approach
was
you're,
essentially
adding
another
part
of
the
API.
B
It's
going
to
be
kind
of
undocumented
because
the
plug-in
and
the
Valero
server
are
going
to
have
to
agree
on
the
ammo
format
and
if
we're
going
to
be
doing
that,
we
might
as
well
just
add
the
fields,
because
we're
already
in
the
context
of
a
struct
of
several
fields
that
are
part
of
that
API
definition.
So
I
modified
it
to
be
a
little
more
flexible.
B
We
still
have
a.
We
still
have
Fields
total
and
completed,
but
there's
now
no
assumption
that
it
means
bytes,
there's
a
separate
units
field.
So
that
way,
all
of
these
storage
plugins
can
identify
their
units
as
bytes.
So
Valero
can
aggregate
those
values
based
on
unit.
But
if
you
have
some
other
plug-in,
you
know
where
maybe
you're
cracking
the
number
of
images
copied
or
maybe
you're
tracking
some
other
in
a
metric.
B
You
can
use
a
different
unit
and
then
I've
also
added
a
string
field
for
just
a
freeform
description,
because
you
may
be
writing
a
plug-in
that
does
you
know
that's
interfacing
with
some
service
that
doesn't
give
you
a
percent
completion.
It
might
just
give
you
a
phase
so
we're
in
the
you
know.
Pending
phase
the
uploading
phase,
the
the
validation
phase,
whatever
this
provides
a
plug-in
a
way
to
give
a
description
of
where
the
progress
is,
even
if
it
can't
be
Quantified
or
summed
up
by
Valero.
B
So
that's
the
change
I
made
in
response
to
feedback
and
discussion.
I'm
still
awaiting
review
of
that
at
this
point,
I'm
hopeful
that
we're
near
the
end
of
this
cycle
and
are
ready
to
approve
it
once
we
can
get
this
approved
and
merged
I
then
have
some
other
PRS
open.
I
didn't
link
them
this
time,
but
you
can
look
at
last
week's
to
see
and
basically
there's
the
actual
detailed
API
design
changes
that
kind
of
flow
out
of
this
PR.
B
One
thing
those
are
now
out
of
date,
because
this
change
I've
made
to
progress,
reporting
I
have
not
yet
leveled
that
down
into
the
detail.
Designs.
I
want
to
wait
until
it's
approved
at
this
point
because
I'm
not
certain,
that's
the
final
change
so
once
we
approve
this
design,
I
will
update
those
more
detailed,
API
design
documents,
plug-in
API
design
documents
to
reflect
that
change.
B
B
Once
all
these
design
PRS
are
approved,
we're
basically
ready
to
start
implementing
and
merging
on
Main,
because
that's
no
longer,
you
know
going
to
110.
so
it'll
be
ready
for
when
the
11
development.
A
But
nope,
okay
I,
have
few
topics
for
today
again:
Keep
Calm,
Europe
23,
the
close
of
cfps.
This
Friday
we
discussed
with
Scott
we're
gonna,
apply
again
with
the
one
that
we
did
on
the
open
source
Summit,
maybe
a
bit
more
extended
on
the
demo
side,
and
today,
I'm
gonna
have
a
discussion
with
Dylan
from
ahead
to
apply
with
the
kind
of
discussion
about
backup.
So
if
someone
wants
to
join
us
on
that
feel
free
just
drop
a
line
slack
and
we
can.
A
We
can
discuss
that
thing.
Last
time
we
applied
and
we
were
redhead
VMware
they'll
cast
in
so
Dave
was
from
Custom
and
who
else
I
forgot,
but
yeah.
For
some
reason
we
were
not
selected,
but
yeah
we'll
try
again
next
thing.
First
name
is
the
European
open
source
conference
opened
the
cfps
and
the
end
date
is
I'm.
Gonna.
Add
that
it's
December
15th.
A
So
if
someone
is
from
from
Europe
and
wants
to
to
join
I'm
gonna
apply
there
for
sure
and
next
thing
all
right.
Last
time
I
think
we
discussed
some
swag
and
if
we
can
send
some
something
I
think
I
can
arrange
that
till
the
end
of
the
year,
but
I
just
wanted
to
get
some
feedback.
What
do
you
want
pretty
much
like
t-shirts
is
the
easiest
thing
to
do,
but
it's
maybe
the
most
boring
one.
A
So
I
was
thinking
something
like
this
kind
of
trick:
hats
or
baseball
hats
or
some
kind
of
hoodies
for
the
cold
days.
What
do
you
think
I'm
I
cannot
promise
anything
right
now,
but
I'm
just
getting
ideas
from
I
hope
I
can
get
some
ideas
from
you.
What
do
you
want
or
what
you?
What
what
you
want
to
wear
or
show
off.
A
A
The
next
thing
is
with
the
release
for
110
and
111
and
in
general,
the
release
cycle.
I
think
we
have
pradeep.
Maybe
that's
a
bit
sucks:
okay,
tiger!
Okay,
that's
a
good
idea!.
A
Yeah
cold
feet:
yeah,
yeah,
okay,
once
I
have
something
I'll
check
what
we
can
do
in
terms
of
budget
and
practically
sending
in
around
the
world.
Okay,.
C
Yeah
so
kind
of
what
what
I'm
thinking
about
like
1.10
is
around
December,
early
December
or
maybe
enough
number.
So
we
don't
know
exact
date
based
on
the
rcnfc.
It
would
come
typically
in
my
mind,
we
should
be
doing
at
least
three
release
in
a
year
or
precisely
three
degrees
in
a
year,
so
that
we
are
kind
of
evenly
balanced
and
we
can
do
multiple
patches
on
on
those
releases.
C
So
when
I
say
it
releases,
it
means
these
minor
ones,
the
the
three
releases
and
then
patches
on
that
can
be
as
many
as
depending
upon
what
issues
we
found
so
based
on
that
I'm
thinking.
If
we
do
release
sometime
in
early
December,
we
can
plan
next
lease
typically
around
April,
and
we
can
go
always
plus
minus
one
month
depending
upon
content
and
scope,
but
we
should
have
that
kind
of
regular
Cadence,
not
too
frequent
and
not
to
kind
of
do
far
releases.
C
So
that's
the
way,
my
planning,
what
I
was
doing
over
the
last
couple
of
days.
So
we
have
a
kind
of
a
you
know
on
the
GitHub
issues
we
created
a
label
called
1.11
candidate,
and
there
was
some
of
those
candidates
were
already
tagged
by
the
our
team.
C
Also,
some
of
the
candidates
were
tagged
by
either
Valero
Community
Engineers,
so
I
also
started
kind
of
going
through
the
all
open
issue
in
the
last
six
months,
like
the
issues
which
is
open
the
last
six
months,
precisely
from
first
of
March
till
now
and
then
felt
wherever
we
can
do.
A
kind
of
this
1.11
as
a
candidate
so
feel
free
to
kind
of,
go
and
see
candidate
and
then
put
your
comments.
C
If
you
want
to
work
on
it
or
if
you
see,
if
we
should
do
or
not
do
that
so
thumb
rule
which
I
am
thinking
about
the
things
which
is
more
related
to
a
kind
of
a
the
bug
for
the
quality
purpose,
that
can
be
one
issue.
We
should
look
that
the
issue,
which
gives
more
flexibility
in
terms
of
backing
up
resources,
backing
up
volumes
that
gets
Cuts
in
anything
with
respect
to
restrict
I'm,
not
too
Keen.
C
However,
if
the
issue
seems
to
be
generic
like
it
may
not
be
only
restricted
specific,
it
may
be
with
the
copy,
also
then
I'm
kind
of
putting
them
as
a
candidate,
so
that
we
we
handle
the
more
of
a
quality
issue
at
generic
level.
So
these
are
the
kind
of
ideas
in
my
mind,
there
are
some
big
ticket
items.
I
didn't
find
those
kind
of
GitHub
issues
for
them.
C
For
example,
for
data
mover,
there
was
not
enough
GitHub
issues
which
I
can
tag
it,
so
we
should
work
on
data
mover
at
least
design
part
freeze
it
as
soon
as
possible
and
work
on
that.
We
should
look
at
the
the
windows
cluster
support,
NFS
support,
I'm
hearing
those
from
some
of
those
customers
who
are
doing
a
kind
of
multi-cloud
Journey
with
respect
to
Containers.
So
so
they
have
a
kind
of
multi-cloud
multiplatform.
C
B
You
and
I
should
note
too
the
the
item
action,
progress
thing
I
was
talking
about
the
design
and
we
have
several
issues
in
the
one,
the
way,
a
tag
with
111
that
were
the
implementation
of
the
bits
part
as
part
of
this
design,
and
these
are
all
prerequisites
to
data
mover.
So
you
know
my
thinking
is
that
that's
kind
of
for
for
111.
You
know
for
me
that
stuff
is
really
the
highest
priority.
You
know
and
then
maybe
you
get
the
data
we
were
designed.
B
You
know
done
by
111,
but
but
certainly
get
this
implementation,
because
also
on
the
red
hat
side,
we're
intending
to
make
use
of
that
item
action
progress,
work
in
our
next
ODP
release
as
well,
so
we
definitely
want
those
in
111.
C
Yeah,
yes,
so
I'm
good
with
that
so
kind
of
because
as
soon
as
design
is
approved,
and
then
you
are
passionate
about
do
that
work
and
anyway
it's
fun
to
foundational
work
for
data
movers
so
feel
free
to
kind
of
I.
Don't
know
the
timing,
how
much
time
it
will
take.
You
only
have
to
tell
it
so
so
do
you
think
those
items
if
design
is
approved
will
be
done
by
March,
April
time
frame
or.
B
Oh,
yes,
certainly
I'm
hoping
to
get
most
of
it
done.
You
know
well
before
then,
but
you
know
certainly
by
March
I,
think
all
that
stuff.
We
should
be
able
to
get
that.
Okay,
yeah.
C
So
at
Heil
ballpark
level
we
are
kind
of
looking
up
real
around
April.
It
can
be
plus
minus
one
month.
So
if
we
finish
early,
we
have
a
good
quality.
Another
thing
I
want
kind
of
more
focus
on
CVS
and
also
being
a
this
community
project.
Sometimes
we
don't
do
that
much,
but
recently
there
was
some
scan
happen
through
US
API
tools
and
all
we
found
a
lot
of
CVS
and
then
we
found
we
need
to
update
some
cool
language
version
and
other
things,
and
also
we
need
to
kind
of
make
sure
every
release.
C
We
do
that.
We
we
try
to
kind
of
at
least
do
scanning
and
then
address
some
of
those
things
where
so
that
it
becomes
easy.
If
you
use
those
components
in
your
commercial
Solutions
as
well,
you
don't
have
to
worry
about
those
things
so
as
much
as
we
can
fix
in
the
Upstream.
That
will
be
kind
of
much
better
approach.
D
Aside
from
the
I
think,
Wes
included
a
link
to
the
kind
of
stuff
we've
been
thinking
about
already
for
111..
Do
we
have
plans
to
formalize
a
release?
Cadence
I
know
I,
know
that
like
we're
shooting
for
about,
you
know
three
releases
a
year.
Is
there
some
you
know?
Should
we
maybe
have
a
a
formal
something
something
we
actually
submit
to
the
repo
and
vote
on
from,
like
a
community
perspective,
yeah.
C
So
what
I
am
thinking
this
four
months
is
a
kind
of
very
bad
perk,
but
at
least
three
days
in
a
year
and
plus
minus
one
month.
Also,
whenever
we
do
kind
of
release
planning
like
right
now
we're
doing
1.11.
So
we
should
put
a
content
in
a
one
discussion:
let
people
vote
it
or
we
create
a
label
and
kind
of
some
kind
of
way
where
we
could
tag
it
and
then
start
preparing
that
content
little
bit
early
as
soon
as
1.11
contains
is
Frozen.
C
We
can
kind
of
start
with
1.12
contents
and
also
so
we
have
to
kind
of
little
bit
more
things
on
lineup
for
future
things,
much
in
advance
that
I
am
supportive,
I'm,
not
sure
like.
If
we
can
pin
down
like
let's
release
a
month
month
of
March
and
month
of
this
month.
Of
this
we
have
to
be
flexible
depending
upon
some
time.
If
one
item
is
very
important
and
it's
kind
of
needing
another
month,
we
can
be
flexible.
So
four
month
is
a
ballpark.
Where
sometime
we
can
do
three
months
sometime.
C
E
D
Great
well
I
really
appreciate
you
bringing
this
up
and
spearheading
this
one
thing
I
think
I
think
what
you're
getting
at
is.
Maybe
what
we
need
to
do
is
more
formalize,
and
this
is
something
that
I
think
I
mean
this
conversation
we've
gone
on
for
months,
maybe
but
back
with
Eleanor.
D
We
started
this
conversation
as
well,
finding
a
way
to
formalize
the
release,
planning
process,
kind
of
an
ad
hoc
and
GitHub
in
the
past
and
I'm
wondering
if
we
could
take
an
opportunity
to
maybe
you
know
just
from
an
organizational
perspective,
we've
got.
D
You
know
multi-multiplaning
on
our
end
that
maybe
if
we
could
find
a
way
to
share
that
knowledge
with
with
you
guys
easier,
it
may
make
some
sense
to
just
formalize
exactly
what
the
planning
process
looks
like
and
then
obviously
we
don't
need
to
set
the
actual
Cadence
directly
a
year
in
advance
or
anything
like
that.
But
we
have
a
process
in
place
for
okay
once
the
requirements
are
set.
We
we
plan
to
ship
about
this
time
after
the
planning.
Stone
right.
Does
that
sound
like
a
good
idea.
B
Through
that
one
before
formalizing
the
process
is
this
something
that
we
would
want
to
actually
formalize
in
the
context
of
the
governance
docs,
since
this
is
something
that
involves
the
you
know,
all
the
maintainers
and
and
kind
of
governance
to
sort
of
the
plan
for
how
the
project
is
run
so
I
think
release
planning
might
be
something
that
we
would
want
in
that
document.
B
F
Perhaps
I
mean
it
would
just
bring
Clarity
I
think
to
the
things
you're
you're
speaking
to
pradeep,
if
we
kind
of
illustrate
that
out
in
in
governance
in
writing,
yeah.
C
We
can
yeah,
we
can
discuss
that.
So,
let's
kind
of
our
line
is
here.
If
needed,
we
can
start
a
thread
and
come
to
some
kind
of
conclusion,
and
then,
if
you
are
all
aligned
to
that,
we
can
put
in
the
garden
stock.
I
would
still
kind
of
keep
it
like
it's
a
bit
flexible,
but
not
kind
of
completely
out
like
plus
minus
one
month
or
like
three
years
in
a
year
is
not
about
every
four
months.
A
B
Is
that
one
of
the
things
that
you
know
I've
seen
over
the
course
the
last
couple
years
with
a
lot
of
you,
know,
changes
and
you
know
develop
people,
you
know
developers
on
the
team
and
management
and
all
that
is
that
you
know
some
of
this
knowledge,
sometimes
when
it's
not
written
down
kind
of
gets
lost.
Well,
how
did
we
do
this
last
year?
Well,
I,
don't
know
because
here
anymore,
you
know
I've
been
just
in
the
document
now
we
know
how
we
do
it,
because
it's.
A
A
Yeah
and
also
it
to
make
the
project
governance
so
much
predictable
for
newcomers
if
they
want
to
join.
They
can
just
read
that
not
to
like
ask
around
for
someone
to
guide
them,
how
we're
gonna
release
and
when
or
whatever
yeah
I'm
I'm.
Definitely,
if
ever,
we
should
put
that
really
in
written
somewhere
in
the
repo
yeah.
So,
as
Dylan
said
Dylan,
you
mentioned
something
that
you
you
can
like
reuse,
some
good
practice
from
red
hat
or
like
I,
got
it
wrong.
D
No
I
think
I
was
saying
that
we've
had
a
informal
process
like
ad
hoc
in
the
past
that
I
started
with
Eleanor
months
ago.
I,
don't
know
that
it's
I
don't
know.
If
anyone
even
is
aware
of
it.
I
was
just
using
these
labels
at
the
time
for,
like
one,
nine
and
one
ten,
but
you
know
that.
D
That's
only
because
at
the
time
like
really
red,
hat
and
VMware
were
the
only
two
setting
requirements,
I,
don't
know,
there's
other
people
like
other
stakeholders
that
are
interested,
but
you
know
we
probably
need
to
create
some
formal
process
that
if
there
are
other
stakeholders
and
contributors
that
have
requirements,
how
do
they
Supply
them?
Right
generally,
we've
opened
a
GitHub
issue
and
requested
people
to
just
comment
on
it.
D
B
Yeah,
that's
another
advantage
of
having
this
documented
in
the
governing
stock.
Is
that
so,
if
there's
other
stakeholders
that
are
interested,
you
know
the
contributors,
other
people
using
Valero
that
want
to
participate
in
the
process,
the
revenue
stock
will
tell
them
how
they
are
able
to
participate.
A
F
Right,
do
you
think
we're
open
to
I
realize
we're
meeting
every
two
weeks
here,
but
for
these
milestones
for
these
three
releases
and
for
for
the
planning
for
those
that
we
would
have
a
separate
or
or
this
meeting
would
be
converted
into
a
planning,
discussion
live
once
those
issues
are
collected
and
kind
of
organized
and
we'll
walk
through
and
and
to
some
degree,
make
some
decisions
in
the
in
planning
meeting
for
a
release,
or
that
would
just
all
be
done.
Async.
C
Most
of
the
things
we'll
do
async,
but
it's
still
kind
of
the
scooping
based
on
the
labels
and
all
that
type.
I,
don't
want
to
kind,
of
course
like
this
is
the
what
we
want
to
do
as
a
is
the
community
right,
so
people
have
to
little
bit
vote
and
also
that
flexibility
I
want
to
keep
it.
But
yes,
once
we
have
an
idea
like
okay,
these
are
the
top
voted
issues
or
top
issues
which
you
believe
you
should
label
it
much
in
advance
for
a
release
and
then
do
kind
of
bucket
them
properly.
C
So
so
I
can
create
anything
I
needed
from
my
side
and
then
you
can
create
from
your
side
and
then,
if
that
I
don't
know
to
kind
of
kind
of
say
if
I
create
something,
and
then
you
don't
want
to
force
some
user
to
work
on
that,
even
they
had
something
more
important
in
their
mind
and
they
want
to
vote
for
that.
So
still
it's
more
of
a
process
where
everybody
creates
things
what
they
want
and
and
if
they
sign
up
to
do
that,
then
it's
much
easier.
C
If,
if
nobody
sign
up
to
do
that,
then
voting
and
all
and
then
based
on
that,
we
can
decide
it's
more
important
and
all,
but
we
should
do
a
little
bit
more
regularly
so
that
we
are
much
prepared
in
advance.
So
so
it's
kind
of
planning,
but
more
asynchronous,
and
maybe
before
kind
of
kicking
off,
we
can
have
one
community
meeting
where
we
can
say
these
are
the
item.
We
are
all
kind
of
trying
to
do
like
two
weeks
before
the
kicking
of
a
new
release.
F
A
And,
and
was
you
asked
if
those
things
can
go
to
111
right.
C
A
C
So
all
these
GitHub
issues
also
had
been
labeled
as
1.11
candidate,
because
this
is
a
page.
So
if
you
go
to
the
issues
list
pays
over
sharing
screen
only
then
you
will
find
there
is
a
label
1.11
if
you
select
dot
111
candidate,
yeah
yeah.
C
So
all
of
them,
which
was
in
that
page,
is
also
on
this
page,
but
there
are
more
than
that
so
which
I
kind
of
and
I'm
kind
of,
asking
even
some
of
the
community
members
from
our
side,
film,
VMware
side
to
also
see
if
they
can
also
sign
up
for
some
of
them.
If
we,
if
we
can
sign
up
for
most
of
them,
it's
good
otherwise
we'll
move
from
1.1
to
1.12.
C
What
kind
of
looking
at
the
description
and
all
these
or
the
my
ideas
like
somewhere,
these
may
be
kind
of
important
I
may
not
be
very
accurate,
but
I
looked
at
a
lot
of
people.
Comments
is
called
some
places.
Some
Daniel
has
commented:
okay,
there's
an
issue,
needs
enhancement
and
there's
an
issue
which
you
don't
know,
but
we
should
fix
it
so,
based
on
that,
I've
done
some
triage.
At
my
end,.
C
The
110
is
around
December.
We
will
get
released
sometime
in
end
of
November
or
early
December.
That's
what
I'm
hearing
based
on
the
current
kind
of
the
rate,
current
kind
of
speed
we
are
working
on
that
and
1.11
will
be
sometime,
April
plus
minus
one
month.
We
can
say,
like
it
just
put
tentatively
April,
but
we
can
release
in
my
March
or
maybe
depending
upon
if
we
get
done
early
or
if
we
kind
of
think
so.
A
C
B
Just
worth
noting
that
the
rc.1
for
110
was
released
last
week,
so
you
know
at
this
point
it's
really
just
a
question
of
continuing
to
test
that
and
bugs
found
and
how
long
it
takes
to
fix
those
bugs.
C
Yeah,
it's
all
depends
on
that.
That's
what
I
was
hearing
also
from
Daniel,
so
he
mentioned
like
yeah
tentatively,
we
planned
FC
23rd
November,
but
that
seems
little
bit
challenging
because
there
are
some
issues
they
have
found.
Also,
so
we
said,
I
can
be
in
depth
number
or
early
December.
That's
what
he
was
mentioning
to
me
but
feel
free.
If
we
kind
of
ready
before
we
can
always
at
least.
A
Foreign,
okay
and
for
the
formalizing
of
the
process,
I'm
gonna,
take
that
and
I'm
gonna
write
up
something
put
it
in
GitHub
and
we
can
always
consider
and
make
it
that
we
fit
our
our
process
and
our
how
we
see
everything.
A
Names
not
faces
because
it's
only
me
with
camera,
but
I
can
see
some
new
names
on
on
the
list.
Anyone
wants
to
introduce
themselves.
E
Hi,
oh,
this
is
about
it,
so
I
work
for
this
organization,
so
I've
been
using
or
with
little
extensively
for
the
past
one
year.
So
my
recent
involvement
into
this
community
is
to,
like
you
know,
get
people
into
like
you
know
about
the
tool
itself
is
like
you
know,
heading
towards
hand,
and
if
at
all,
if
I
could,
like
you
know,
contribute
down
in
the
future,
would
like
to
do
that.
So.
A
Yeah
nice
welcome
to
the
community.
Thank
you.
As
you
see,
we
we
need
help.
So
if
you
feel
like
it
contributing,
it
will
be
great
yeah.
A
Can
you
reach
out
to
me
it's
a
personal
ask
work
related,
though.
E
A
You
reach
out
to
me
in
swac,
in
slack
not
swag
slack
to
if
you
can,
if
we
can
chat,
how
you
use
Valero
and
we
can
make
something
like
and
if
you
feel
like,
sharing
that
with
the
with
the
public
that
you
use
Valero
internally.
A
All
right
anyone
anyone
else
wants
to
discuss
some
topics
like
some
PRS
or
some
issues.
We
can
convert
that
super
easily
right
now
to
an
office
hours
if
someone
wants
has
is
having
some
topics.
I'm.
Sorry,
my
my
language
today
is
not
the
best.
A
C
A
Thank
you,
yeah
one.
One
thing
is
that
thing
that
we
set
it
up
on
Mondays
to
to
have
like
a
a
half
an
hour
to
review
PRC.
Is
that
actually
working
for
everyone?
Is
that,
like
make
sense
still
or
we
should
change
it.
F
To
I
know,
people
get
very
busy
and
I
don't
know.
If
we,
if
we
did,
we
add
a
calendar
kind
of
invite,
like
we
have
for
this
meeting
or
I.
F
Is
it
possible
just
to
Ping
everyone
in
the
channel?
Hey,
we
have
a
meeting
or
office
hours
coming
up
instead
of
just
maintaining.
A
That's
another
thing:
that's
that's
another
issue
that
we
we've
opened.
If
you
can
recall
to
restart
the
office
hours
yeah
was
it
issue
or
discussion.
I.
A
I'm
talking
about,
we
discussed
that
we
is
going
to
be
great
if
we
can
do
like
a
async
PR
triaging
like
every
Monday,
so
I
set
it
up
a
reminder
on
swac,
it's
like
to
to
remind
you
practically
to
to
read
all
the
PRS
and
then,
if
you
yeah,
just
to
dedicate
some
time
to
do
that,
and
the
other
thing
that
we
discussed
was
the
office
hours.
A
That
thing
was
to
restart
them,
asynchronously
on
on
Slack
in
specific
time
period.
So
all
the
maintenance
and
contributors
can
like
be
online
and
just
watch
the
channels
for
some
questions.
So
if
you
can
so.
A
I'm
Jeffrey,
if
we
can
do
that
in
the
kubernetes
Slack
yeah.
Okay,
no
can
I
do
Channel,
no
yeah.
They
they
disabled
that,
otherwise
it
would
be
super
noisy
and
everybody
was
will
go
like
oh
Channel
or
wherever.
A
But
yeah
I'm
I'm
gonna
get
into
3D
with
the
kubernetes
slack
admins.
If
we
can,
because
right
now,
the
the
reminder
is
towards
maintainers,
and
maybe
we
can
extend
that
group
a
bit
and
with
everyone
who
is
practically
maintainer
and
contributor.
So,
but
there
is
no
other
way
to
to
address
the
channel
right
now.
A
A
Anyone
else
any
topics,
if
not,
can
I
use
the
time
to
to
discuss
the
I
mean
everyone
is
welcome,
but
I
just
want
to
use
the
time
to
discuss
with
Dylan,
because
the
final
discussion
for
for
the
for
the
kubecon
Europe
is
the
one
still
still
with
us.
No
thank
you
all
right.
Thank
you,
yeah.
Thank
you.
A
Yeah
Dylan
left
everyone.
Okay.
The
idea
was
to
to
get
a
group
of
people
on
stage
and
and
discuss
different
approaches
towards
backup
and
how
we
see
the
future
backup
and
especially
in
the
cloud
native
stuff.
A
So
if,
if
someone
of
you
wants
to
to
be
on
that
stage
and
and
be
part
of
that
discussion,
you're
super
welcome
to
to
join,
we
have
to
figure
out
just
yeah.
We
are
limited
by
six
I
think
it's
got.
It
was
six
last
time
right.
Can
we
recall
that
or.
A
Whatever
five
or
six
so
yeah,
if
someone
wants
to
be
in
that
stage
and
and
and
join
the
discussion,
will
be
super
helpful,
so
please
drop
a
line.
We
can.
We
can
figure
out
this
until
Friday.
We
have
everything's
like
all
the
text
and
everything
is
there,
so
we
just
have
to
add
the
names.
A
Okay
with
that
that
was
everything
that
I
had
for
today.
Thank
you
very
much
for
everyone
for
for
joining
today.
I
hope
you
have
a
great
rest
of
the
day.
Bye.