►
From YouTube: Velero Community Meeting / Open Discussion - Feb 2, 2021
Description
Feb 2, 2021
Status Updates - items working towards roadmap
carlisia:
Addressing code review for:
https://github.com/vmware-tanzu/velero/pull/3004
https://github.com/vmware-tanzu/velero/pull/3190
PR reviews
bridget:
Focusing on PR reviews
Continuing on multiple credentials support
Will open more PRs once dependent PRs are reviewed/merged
dave
Community support
Upload progress tracking design
jonas
New website layout: https://github.com/vmware-tanzu/velero/pull/3279
Discussion Topics
pranavgaikwad (Pranav Gaikwad)
Need help building Velero CLI
Community Shoutouts
None this week (lots of PRs pending reviews)
A
B
B
C
C
I
think-
and
that's
looking
really
good,
but
she's
made
some
changes
since
I
need
to
to
follow
up
and
review
that
I
am
also
going
to
be
starting
on
the
pr4
restore
progress,
because
that's
one
that
I
think
yeah
it's
a
bigger
change,
so
I
think
I've
been
focusing
on
trying
to
get
some
of
the
easier
ones
through.
So
now
I
need
to
put
more
time
and
effort
into
the
bigger
ones
I'll
be
doing
that
this
week.
C
Aside
from
that
being
continuing
on
multiple
credential
support,
I
have
a
couple
of
prs,
which
are
up
which
are
kind
of
dependent,
well
they're
kind
of
the
initial
work
that
I
had
done
with
regard
to
refactoring
some
of
the
the
existing
code
and
making
some
initial
changes
there.
So
I
have
more
branches
locally
and
I'll
push
those
once
the
pr's
that
they
depend
on
are
merged
just
in
case,
I
don't
think,
there's
any
point
in
push
pushing
them
in
case
I
need
to.
D
D
So
we
want
to
have
those
happen
in
the
context
of
the
backup,
but
we
have
other
plugins
that
do
background
work,
and
we
don't
monitor
that
at
the
moment,
and
so
we
want
to
be
able
to
monitor
that
and
call
that
out
whether
there's
any
failures
as
part
of
the
backup
and
be
able
to
understand
that
the
backup
is
actually
completed
and
all
the
data
is
moved
to
stable
storage
and
we
should
be
able
to
push
the
uploads
and
the
uploads
currently
happen.
In
the
background.
We
simply
don't
monitor
them
and
now
we'll
monitor
them.
D
A
A
A
So
now
all
websites
will
be
run
on
hugo
instead
of
jekyll,
which
is
super
nice,
but
we
didn't
have
to
do
that
migration
for
valero,
because
we
already
did
that
seven
or
maybe
even
eight
months
ago,
but
we
do
have
some
updates
in
here
and
I
wanted
to
show
you
the
what
it
looks
like
on
the
site
and
then
we
can
dig
into
your
comments
as
well
carlesia.
So
the
first
one
I
want
to
point
out
is
the
resources
one.
A
So
we've
cleaned
up
the
resources,
so
it's
no
longer
just
a
list
of
different
resources,
but
actually
showing
like
community
meeting
playlists
podcasts.
So
here's
where
we
can
add
in
even
more
recent
content.
We
also
talked
about
having
the
discussions
kind
of
tie
into
this.
So
we
want
to
see
how
that
works
as
well
with
the
the
shout
outs
and
the
the
interesting
resources
piece
there.
There
are
some
external
blog
posts
as
well
from
other
people,
so
that's
the
resources.
A
A
One
thing
that
we
did
with
the
documentation
is
to
make
sure
that
it
is
can
be
made
wider
properly,
so
the
whole
side
itself
actually
widens
up.
So
it's
no
longer
locked
to
the
very
minimal
width
that
it
was
locked
to
before.
So
we
actually
have
more
space
for
the
text.
That's
something
that
we
wanted.
A
You
might
also
notice
that
we
have
this
table
of
contents
here
to
the
right
instead
of
having
it
as
we
do
currently
here
in
the
middle
or
in
the
beginning,
we
can
have
that
to
the
right
there.
That
also
disappears,
if
you
make
the
the
window
smaller
or
if
you're
on
mobile,
so
it
doesn't
take
up
a
lot
of
space.
One
thing
we
also
added
in
here
is
simple
edit
and
report
issues
links.
So
if
you
find
an
issue
on
this
specific
page,
it
will
directly
point
to
hey.
A
We
got
an
issue
here
on
page
basic
install
which
is
neat
and
then
also,
if
you
want
to
edit
we'll
start
an
edit
here,
and
of
course
this
will
create
a
fork
into
your
your
handle,
and
then
you
can
create
a
pr
and
it
has
a
standard
signed
off
by
a
dco
sign
off
here
as
well.
So
that's
always
there
so
simple
edits
that
we
wanted
to
kind
of
clean
up
as
well.
A
One
thing
that
were
that
we
were
investigating
as
well
was
the
possibility
of
making
these
into
not
folders
but
kind
of
foldable
menus
because
they
are,
it
is
pretty
long.
You
have
to
scroll
a
bit
depending
on
if
you're
zoomed
in
or
not
valero
is
still
pretty
small
compared
to
several
other
open
source
projects
where
this
menu
goes
on
pretty
much
forever.
I
don't
see
the
the
folding
structure
really
necessary
here,
but
we
want
it
as
an
option
for
websites
to
kind
of
turn
it
on.
If
we
want
to.
B
I
know
bridget
also
left
comments
after
my
comments.
Maybe
she
wants
to
bring
bring
up,
bring
them
up,
but
I
do
have
a
comment:
if
you
can
go,
the
the
community
page
looks
great
perfect,
the
resource
pages.
I
think
if
we
could,
the
next
iteration
an
improvement,
at
least
in
my
mind,
is
if
we
could
have
tabs
across
the
top
with
the
different
sections,
because,
if
you
think
about
it,
if
we
have
a
bunch
of
like
we
have
more
podcast
shows
with
the
team
members
than
two
in
blog
posts,
for
example,
it's
just
unattainable.
B
A
Yeah
yep,
that's
that's
good
feedback,
the
resources
page
isn't
for
all
podcast
shows
and
all
external
videos
it's
for
the
ones
that
we
want
to
feature
essentially.
So
I
think
yeah.
Many
of
the
other
videos
that
we
have
down
here
are
older
now,
and
we
can
definitely
find
the
newer
ones
that
might
fit
better
in
here
same
with
the
external
blog
posts,
yeah.
B
D
A
A
E
C
So
I
I
left
a
comment
on
the
pr
itself,
but
I
think
that
that
was
just
the
main
kind
of
point
of
my
comment
was
kind
of
following
on
from
what
carlesia
said
about
the
kind
of
conditional
rendering
of
the
toc
page
and
when
it
should
be
rendered
when
it
shouldn't.
So
there
are
some
there's
a
couple
of
pages
where
we
don't
have
there
isn't
a
toc,
but
then
you
still
get
that
on
this
page
and
then
it's
kind
of
empty.
C
So
it's
just
making
sure
that
we
have
some
kind
of
conditional
kind
of
check
there
to
make
sure
whether
it
makes
sense
to
have
that
part.
But
then
also
I
wanted
to
ask
about
in
the
case
where
we
have
like
a
large
toc
or
just
a
toc
in
general.
Should
it
be
both
at
the
top
of
the
page
and
on
the
side.
So
just
wondering
is
that
going
to
be
like
a
follow-up
to
remove
it
from
the
top.
A
C
Yeah
that
was
kind
of
the
main
point
and
other
things
that
I
mentioned
was
whether,
although
I
think
this
is
going
to
be
an
action
for
the
maintainer
team
who
have
access
to
making
changes
to
actual
repo
itself
as
to
whether
we
could
create
like
a
specific
issue
template
for
this,
so
that
we
can
have
some
kind
of
action
so
that
it
gets
like
labeled
correctly.
So,
rather
than
just
being
a
plain
issue,
we
can
apply
some
labels
and
stuff
to
it
as
well.
C
But
I've
I've
noticed
them
a
few
folks,
who've
been
opening
prs,
who
haven't
been
able
to
apply
labels
to
their
pr.
So
I'm
wondering
if
applying
labels
is
a
restricted
thing
based
on
permissions
on
the
repo.
So
that's
something!
I
think
that
we
need
to
look
into
and
check
the
permissions
there
as
to
whether
people
who,
who
don't
have
kind
of
admin
or
maintain
your
permissions
on
the
repo,
whether
they
can
apply
labels
to
issues.
So
that's
just
something.
I
think
that
yeah
like
say.
We
need
to
look
into.
A
C
Yeah
because
because
we've
been
had
added
some
or
we'd
added
a
new
link
whenever
creating
a
new
issue
to
try
and
encourage
people
to
use
the
github
discussions
board
and
just
whenever
I've
been
looking
in,
that
I've
seen
some
other
kind
of
settings
within
github
issue
creation
and
various
other
things.
So
I
think
yeah,
like
you
say
you
can
apply
labels
to
the
url,
the
same
way
that
you
do
with
the
body.
But
I
don't
know
if
that
is
a
permissions
based
thing.
C
A
C
A
D
A
A
E
I
think
my
only
comment
is
to
make
it
less
of
like
a
panel
on
the
side
and
more
of
like
a
box
like
to
shorten
the
the
the
coloring
on
the
bottom,
to
make
it
maybe
stand
out
a
little
bit
more
or
have
like
just
have
it
be
more
like
a
box
instead
of
a
full
panel
like
to
be
shortened
so
like
under
yeah,
just
cut
off
the
coloring
there.
So
it
looks
more
like
a
box,
I
don't
know
if
that
would
look
better
or
not.
A
F
Yeah
so
I
made
a
few
changes
in
the
literal
describe
command
and
I
was
just
using
the
default
make
build
to
create
a
new
binary
and
I
so
I
don't
think
my
changes
took
effect
after
building
a
new
binary.
So
I
was
not
sure
if
I'm
missing
something
is
this:
is
there
a
dock
which
describes
or
an
example
shows
how
to
build
with
our
csi.
B
F
A
All
right
so
nolan
was
supposed
to
go
through
the
the
road
map
this
week,
so
we're
we're
aiming
to
do
the
the
road
map
and
kind
of
go
through
the
board
and
everything
in
the
the
beginning
of
the
month,
but
we'll
do
that
next
week.
Instead,
I'm
gonna
walk
through
where
we're
at
and
what
we're
working
on
and
no
community
shout
outs
this
week.
Thank
you,
kalisia
for
for
running
the
script
and
checking
so
with
that.