►
From YouTube: CNCF Harbor's Community Zoom Meeting - July 13, 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
Okay,
hello,
everyone,
my
name
is
orlan
and
I'm
the
community
manager
for
harvard.
Today
we
have
our
weekly
community
meeting
and
it's
official
community
meeting.
So
please
follow
the
code
of
conduct.
Today
is
july,
the
13th,
and
with
that
I
would
like
to
kick
off
today's
session
feel
free
to
add
all
your
topics
or
your
attendance.
If
you'd
like
to
be
listed
there,
I've
just
posted
in
the
channel
on
the
chat,
the
link
to
the
community
meetings,
notes
and
I'm
gonna
share.
A
C
A
I
think
we
have
some
new
faces
in
the
in
the
attendance,
at
least
I'm
not
sure.
If
I
saw
you
before
james,
can
you
introduce
yourself
please.
C
Hi
yeah,
I'm
james,
I've
been
well.
I
work
for
ibm.
I
work
for
some
of
the
ibm
cloud
packs
and
we
obviously
do
a
lot
with
containers
and
there's
some
interesting
things
going
on
with
the
registries
that
I'm
I'm
interested
in
in
helping
with
a
lot
of
our
customers
will
use
harbor
for
doing
for
managing
their
local
registries
alongside
their
kubernetes
clusters.
So
it's
it's
somewhere
where
I
feel
like.
C
I
might
be
able
to
help
make
their
lives
easier,
so
I
thought
I'd
come
and
come
and
get
involved.
The
main
issue
I
wanted
to
talk
about
is
one
there
and
I
want
to
see
if
other
people
see
that
same
problem
and
and
find
out
if
it's,
if
it's
more
of
a
community
thing
or
whether
it's
just
something
that
that
ibm
hit.
A
C
Everybody
yeah
I've
been
doing
mainly
code
in
the
distribution
repository
rather
than
directly
in
harbor
at
the
moment,
but
obviously
harbour
is.
It
is
front
end
that
most
of
my
customers
see.
C
D
A
To
have
you
on
board
to
be
great
if
you
can
contribute
and
if
you
need
anything
from
my
site
as
a
community
manager
or
anything
from
the
other
maintainers
feel
free
to
reach,
we'll
try
to
help
you
out
as
much
as
we
can
with
that.
I
think,
if
added
your
topic
second,
but
do
you
want
to
go
and
then
we
can
not
to
like
distribute
the
flow
too
much.
C
Sure
can
do
if
that's
what
you
want
to
do,
yeah
just
bring
it
up.
So
there's
quite
a
long
description
there
I
think
yeah,
the
the
basic
issue
behind
all
of
this
is
at
ibm.
We've
gone
in
we've
gone
heavily
into
using
fat,
manifests
manifest
lists,
oci
indexes,
whatever
you
want
to
call
them
to
make
sure
that
we've
got
platform.
Support
for
our
containers
obviously
ibm
have
a
few
different
platforms.
We've
got
z
and
p
and
as
well
as
x,
86,
and
so
so.
C
A
lot
of
our
software
is
supports
multiple
platforms
and
we
wanted
to
use
manifest
lists
to
make
sure
that's
easy
and
make
sure
that,
when
a
world
of
cross
architecture
clusters
comes
comes
to
to
pass,
which
I
expect
it
will
do
more
heavily
at
some
point,
but
we're
prepared
for
it.
The
other
thing
that
we
do
is
in
order
to
enforce
consistency
and
make
sure
that
our
applications
and
software
using
exactly
the
images
we
want
them
to
use.
We
reference
all
our
images
by
digest.
C
So
all
of
our
software
running
on
kubernetes
is
pointed
at
using
the
digest
for
the
image
so
that
we
know
exactly
that
is
that
version
and
that
it's
kind
of
referenced
by
content.
So
that's
exactly
what
we
want
to
do.
Unfortunately,
that
means
we
had
a
little
bit
of
a
problem
with
mirroring.
So
a
lot
of
our
customers
use
restricted
network
environments
where
their
clusters
can't
get
directly
to
the
internet.
C
The
problem
happens
when
we
get
a
customer
who
says
well,
I've
only
got
x86
systems
or
I've
only
got
p
systems.
I
don't
want
to
have
to
mirror
the
z
and
the
x86
content
or
whatever
the
the
other
platforms
are,
that
they
don't
care
about,
because
that
kind
of
triples
the
amount
of
data
they
need
to
use.
It
triples
the
amount
of
images
they
need
to
scan
because
a
lot
of
the
customers
are
scanning.
C
These
images
on
their
local
registries
before
they
put
them
in
to
make
sure
that
they're
covering
their
their
vulnerability
requirements
from
for
compliance
and
things
like
that,
and
they
can't
do
it
and
the
reason
they
can't
do
it
is
because
in
the
registry
it
won't.
Let
you
upload
a
manifest
list
if
the
images
that
that
manifest
list
refers
to
don't
already
exist
in
the
registry,
so
I've
gone
in
and
I've
made
a
pr
already
to
the
distribution.
C
Code
base
that
enables
a
configuration
flag
which
allows
the
user
the
registry
administrator
to
say.
Actually
I
don't
I
don't
want
you
to
do
that-
check,
accept
a
manifest
list,
whatever's
in
it
and
then,
when
the
client
tries
to
pull
that
manifest
list.
If
their
architecture
isn't
there,
then
it'll
fail
right
and
that's
that's
fine
right.
C
That's
that's
what
our
customers
actually
want
and
yeah
it
hasn't
been
merged
yet
because
well,
the
the
distribution
repo
doesn't
seem
to
have
much
active
maintenance
at
the
moment,
which
is
another
question
that
maybe
you
guys
can
talk
about
with
me,
but
that's
the
situation
at
the
moment.
I
just
wanted
to
bring
it
to
this
meeting
and
say
well.
B
C
So
we
have
customers
who
would
like
to
in
their
local
mirrors
only
have
to
mirror
individual
platforms
rather
than
having
to
mirror
all
of
the
platforms,
make
up
a
manifest
list.
Yes,.
B
C
B
B
C
B
C
C
Side
to
support
that,
it's
because
the
distribution
so
from
what
I
understand-
and
I
could
be
entirely
wrong
here-
harbor
uses
the
distribution
repository
as
it's
kind
of
core
for
when
it
kind
of
starts,
writing
data
to
disk
and
all
that
kind
of
stuff
yeah.
Is
that
right,
exactly
yeah
we're
wrapping
the
double
distribution?
Basically,
so
what
happens
in
docker
distribution
is
when
you
try
and
push
a
manifest
list.
C
C
That's
what
they're
starting
and
distribution
and
then
after,
if
I
can
get
that
merged
in
distribution,
I
will
probably
come
up
to
harbor
and
have
a
look
at
the
harbour
code
and
say
right.
So
how
is
harbor
configured
because
I
don't
know
yet
and
and
work
out
how
to
make
sure
that
change
is
useful
to
harbor
customs.
B
And
the
contribution
that
you
did
to
to
crane
or
not
or
to
scope
scorpio,
I
think
scorpio
right
yeah.
C
So
so
there
was
at
the
time
there
was
no
way
really
to
mirror
a
manifest
list
without
without
the
client
tooling
attempting
to
copy
the
all
of
the
platforms
first,
so
I
made
some
extensions
to
scopio
to
say:
okay,
well,
let's
add
an
option
to
scope
up
here.
That
just
says
just
copy
the
manifest
list
and
don't
copy
any
platform.
So
then
you
can
just
copy
the
platform
images
you
want
so
just
like
just
x86,
for
example,
and
then
copy
the
manifest
list
without
scopio
trying
to
copy
all
of
the
child
images.
C
B
C
Interestingly,
it
kind
of
already
was
in
the
distribution
spec
there's
nothing
in
the
distribution
spec
that
says
that
a
registry
has
to
enforce
the
existence
of
child
images
before
accepting
a
manifest
list.
There's
some
information
if
you
go
to
commit
and
just
look
at
the
look
at
one
commit,
I
don't
know-
is.
C
Yeah
yeah,
sorry,
no,
that
is
the
right
place.
Isn't
it
okay,
so
yeah
underneath
push
there
yeah
a
second
green
edition.
A
registry
may
reject
a
manifesto
type
uploaded
if
it
references
manifest
or
globs
that
do
not
rise.
The
only
thing
I
was
changing
there
was
just
to
make
it
really
explicit
that
it
is
not
a
requirement
in
the
spec
that
you
have
to
validate
the
existence
of
the
references
just
to
make
sure
that
I
I
don't
think,
there's
a.
I
don't
think
it
would
make
sense
to
put
into
the
spec
a
statement.
C
B
B
And
is
this
change
accepted
or
or
is
it
open
yes,
that
changes
in.
C
The
spec
yes.
C
I've
had
good
discussions
with
the
with
the
oci
team
on
the
mailing
list
and
things
so
that
went
in
fine.
The
scopio
changes
are
all
in
there's.
I
made
some
changes
to
the
image
library
so
that
for
because
a
lot
of
tooling
will
use
the
container
image
library
to
pull
images
and
the
error
messages
from
that
weren't
great
because
they
would
just
say.
Oh,
I
couldn't
pull
this,
but
not
explain
why
so
I've
gone
in
there.
C
I've
improved
the
error
so
that
if
you
try
and
pull
an
image
and
it
finds
a
manifest
list
and
then
the
platform
doesn't
exist
in
that
manifest
list,
it
will
tell
the
user
hey.
I
found
a
manifest
list,
but
the
your
platform
wasn't
there
right,
so
they
know
what's
going
on
rather
than
just
oh,
it
failed
and
just
to
try
and
make
sure
that
the
ecosystem
wasn't
made
any
worse
by
making
these
kind
of
changes.
C
Okay,
okay,
so
yeah!
So
then
the
state
that
it's
in
at
the
moment
is
the
distribution
repository
that
the
maintainers
in
there
haven't
really
engaged
with
it.
So
I
wanted
to
find
out
if
other
people
had
the
same
problem,
because
that
might
help
with
engagement
and
and
yeah.
If
anyone
here
has
any
advice
on
how
to
help.
B
C
B
Have
I
have
the
not
the
feeling,
but
my
view
or
my
perception
is-
is
similar
to
yours
so
that
the
docker
distribution
is
a
kind
of
a
slow
moving
project
or
was
a
slow
moving
project.
I
think
they
promised
to
to
increase
the
velocity
and
and-
and
you
know,
the
planning
for
the
3.0
release,
but
generally
there
are
yeah
slow,
moving
and.
C
Okay,
well,
I'm
continuing
to
work
with
I'm
looking
at
other
issues
in
their
repositories
and
I'm
trying
to
be
more
involved.
Yeah,
hopefully,
that'll
help
we'll.
B
See
what
we
do
at
harbor
is
that
when
we
see
some
functionality
that
is
relevant
to
our
community
or
the
the
product
at
harbor,
we
spec
explicitly
merge
in
patches.
You
know
that
are
upstream,
or
you
know,
patches
that
are
planned
or
proposed
that
are
maybe
not
merged,
but
not
released
or
not
released
or
not
merged.
We
merge
them
in.
So
there
are
a
few
patches
that
we
already
use.
One
is
the
10
gigabyte
limit
that
is
there.
We
we
now
accepted
it.
B
This
will
be
part
of
26
and
there
is
also
some
other
redis
related
patches
that
we
apply
for
have
a
project
on
on
the
docker
distribution,
because
we
we're
building
docker
distribution
ourselves,
yeah.
Okay,
so
is
that
something.
C
B
Use
this
patch
that
you,
you
know,
propose
for
the
for
the
docker
distribution
and
you
know
put
it
in
in
in
in
harbor
and
in
the
docker
distribution
that
we
compile
in
harbor.
This
would
be
the
process
if
you
would
like
to
have
it
before
it's
in
the
docker
distribution.
C
B
Yeah
yeah
you
could,
you
could
take
a
look
at
the
process
is
quite
easy.
You
open
a
pull
request
and
and
like
take
a
look
at
this
one,
for
example,
with
10
gigabyte,
which
is
you
know,
basically
a
similar
pull
request.
You
know
so
it's
basically
add
the
builder.
Extend
the
builder
add
another
patch.
You
know
like
this
is
the
patch
two
eight
one
five
for
the
ten
megabyte
and
then
you
just
add
it
and
open
up
the
pull
request,
and
then
we
will
see
if
we
can
merge.
C
B
C
D
End
yeah
hi
james-
I
actually
did
not
got
chance
to
discuss
with
your
proposal
with
other
maintenance,
I
mean
the
distribution,
vendors,
oh
yeah,
and
actually,
from
my
my
point
of
view,
is
not
a
high
priority
for
for
us
I
mean
the
distribution
maintainer.
We
we
have
to
discuss
the
the
behavior.
This
is
the
fundamental
behavior
change
right,
but
yeah.
I
will
follow
this
and
then
I
will
talk
me
to
another
maintenance
from
distribution
group
to
discuss
about
them.
D
With
the
change
to
I
mean
one,
whether
to
what
is
it
the
existence
of
the
reference,
I
mean
the
index
reference
images
yeah,
so.
C
C
B
Yeah
because
it
would
be,
you
know
bad
if
if
this
pr
is
rejected
by
the
distribution
and
is
there
in
harbor
right,
so
this
will
be.
You
know
quite
a
lot
of
problems
for
the
project.
B
B
Yeah
exactly
so,
this
is
something
that
the
same.
What
happened
here
for
the
10
gigabyte,
because
we
know
this
one,
this
10
gigabyte
patch,
will
be
in
the
next
three
libraries
you
know
and
that's
why
we
kind
of
already
fetched
it
now,
because
you
know
it
will
be
one
day.
It
will
be
there
and
if
it's
the
same
for
the
for
this
functionality,
I
think
it's
chances
are
higher
to
accept
it
from
our
side
as
well.
C
D
No,
oh
so
so
for
2.8,
we
I
mean
the
distribution
release
for
the
2.8.
We
only
merged
for
the
security
patch
or
squid
fix,
and
for
for
your
proposal
or
pr
if
it
will
be
in
if
it
is
merged
in
future,
in
the
main
release
and
every
eventually
in
the
3.0
release,
and
we
are
planning
for
these
3.0
release
for
some
changes.
But
actually
we
do
not
have
any
exactly
due
date
for
3.0
harbor
yeah
will
then
yeah
yeah.
You
do
that.
D
Use
that
build
to
to
package
harbor
release,
I
mean
so
yeah
get
one
eight
words
into
the
main
branch.
The
harbors
still
cannot
consume
it
because
it's
it's,
it
is
not
in
any
a
major
release
of
distribution.
I
mean
two
by
eight.
C
D
D
B
Okay,
so
let's
look
at
this
topic
and
I
found
out
recently
that
the
project.
B
Called
harbor
terraform
provider
is
from
from
a
bestseller
company,
they've,
been
maintaining
and
and
supporting
this
this
terraform
provider
for
quite
some
time,
and
now
they
stopped
using
harbor
and
also
stopped
using
supporting
and
developing
the
the
telephone
provider,
and
I
would
like
to
you
know
note
that
this
provider
is
quite
often
used
within
the
community
of
harvard.
You
know.
B
So,
there's
a
lot
of
a
lot
of
community
members
using
this
this
project-
and
I
would
like
to
discuss
if
there
is
someone
from
the
community
who
would
like
to
take
over
this
project
or
the
other
option
is,
if
we
could,
you
know,
kind
of
in
in
a
source
this
project
as
part
of
harbor,
and
you
know,
get
some
maintainers
that
will
try
to
maintain
this
project
under
the
umbrella
of
harbor,
but
we
still
need
to
find
some
contributors.
You
know
there
are
currently
4
30
34
contributors
registered.
B
Maybe
some
of
them
will
continue
contributing
it
if
it's
under
the
umbrella
of
harbor,
but
from
harbor
side
we
need
to
then
probably
automate
a
few
things
and
then
you
know
make
it
make
it
work
but
yeah.
So
I'm
trying
to
open
discussion
if,
if
there
is
first,
if
there
is
someone
interested
in
contributing
and
maintaining
this
project
and
secondly,
if
this
should
be
under
the
umbrella
of
the
project,
harbor.
C
B
B
B
Yeah
so-
and
I
have
670
releases,
so
it
seems
like
they're
they've,
been
constantly
releasing
new
functionality.
Everyone
in
once
in
a
while
adapting
to,
however,
so.
B
I
know
I
think
you
know.
The
point
is
that
a
lot
of
harbor
users
are
using
this
project.
So
there's
a
lot
of
a
lot
of
hardware.
Users
are
actually
using
this
product,
you
know
using
this
functionality
and
and
because
there's
it's
heavily
used.
I
think
it's
would
be
yeah
valuable
for
the
project
to
to
continue
maintaining
it.
You
know.
C
So
there
is
the
option
of
just
saying:
well,
there's
no
point
having
it
sitting
in
the
best
seller
organization,
move
it
to
the
harbour
organization
and
still
leave
it
as
this
isn't
actively
maintained
and
we're
looking
for
someone
who
can
take
ownership.
C
A
Yeah
and
the
chance
that
we'll
find
someone
from
our
community
to
maintain
it
is
bigger
than
if
he's
there.
So
what
I
can
do
I
can
reach
out
to
the
current
contributors
or
maintainers
and,
if
they're
willing
to
transfer
that,
I
think
we
have
to
change
check
with
roger
as
well.
If
that
fits
in
under
the
umbrella
of
the
overall
project,
but
I
think
we
should.
A
We
definitely
can
do
that.
So
from
communication
stand
point
of
view,
I
I
can
drive
this
one
for
sure
and
see
how
we
can
migrate
it
and
then
get
it
running.
B
Here's
the
issue
I
can
by
pasting
the
issue
with
where's
the
application.
B
So
here's
the
issue
that
is
related
to
this
one
and
I
think
you
should
talk
to
lesser
guards
hold
yeah.
I.
B
And
maybe
brett
brett
wright
is
is.
A
Okay,
I'm
I'm
gonna
open
an
issue
here,
maybe
or
try
to
contact
someone
from
and.
B
B
Okay,
let's,
let's
move
this
thing
forward
and
see
how
this
is
moving
so
from
my
side,
I'm
done
on
the
topics.
A
So
please
everyone
take
a
look,
because
we
will
start
implementing
that
as
a
process,
so
get
acquainted
with
the
with
the
information
there,
how
we're
gonna,
introduce
new
features
and
how
we're
going
to
deprecate
old
features
that
are
not
needed
anymore.
C
A
B
A
So
yeah,
just
everyone,
take
a
look
and
be
aware
of
the
the
process
and
the
the
document.
What
else
william
can
I
open
the
list?
I'm
gonna.
D
A
B
A
So
yeah,
I
have
a
question
about
the
new
release.
253.
We
released
it
like
almost
like
two
weeks
right
after
two
five
two
because
of
some
cvs
found
right.
A
My
question
here
is
like
purely
from
curiosity,
why
we
didn't
didn't
catch
the
cvs
and
the
issues
in
the
252.
D
Oh
yeah,
it
is,
it
is
the
processing
the
router
is
actually
drafting
for
that
and
the
the
process
is.
We
should
firstly,
release
the
patch
and
then
public
the
information.
C
D
Yeah
so
now
roger
is
drafting
for
that
and
we
probably
can
public
out
of
them
by
the
end
of
the
week.
This
week.
A
A
My
my
ask
here
is,
if
you
can
just
keep
us
all
up
to
date
with,
if,
if
your
talk
is
accepted
or
not,
so
we
can
start
planning
accordingly
and
also,
I
think,
jan
you
submitted
the
maintainers
track
for
kubcon
detroit
right,
yes
yeah,
so
we
have
to
keep
track
on
this
one
as
well,
because
I
think
this
time
it
will
be
huge
and
I
think
if
we
can
make
the
the
maintainers
track
in
person
will
be
great
most
probably
I'll
be.
A
There
depends
on
my
my
talks
and
my
other
activities
there,
so
I
personally
think
we
should
aim
for
in-person
talks
and
in-person
maintainers
track.
A
So
whenever
we
have
all
the
answers
to
to
the
question,
are
our
talks
accepted
or
not?
We
can
discuss
that
again.
I
just
wanted
to
bring
that
topic
up,
so
we
can
keep
in
mind
to
do
like
the
necessary
talks
with
our
management
depends
on
the
country
and
company
if
we
can
be
older
and
do
the
things
in
in
person.
A
So
next
thing
is
the
maintenance
attention
to
the
repository.
It's
something
that
practically
I'm
going
to
bring
every
single
time
from
now
on,
so
we
need
to
improve
the
maintenance
attention
to
prs
and
issues
in
the
repository.
B
A
Extending
okay
yeah
so
yeah,
it's
just
be
mindful
for
the
for
the
folks
that
actually
spend
their
time
like
james,
to
contribute
to
our
project
and
respond
in
time.
Please
follow
the
the
the
repository
for
new
pr's
new
issues
and,
let's
be
your
citizens
of
the
cncf
landscape
and
vadim.
What
was
that
clean
branches?
A
B
Clean
branches
and
my
other
topic,
because
it's
a
related,
so
the
thing
is
that
if
we
take
a
look
at
the
harbor,
the
the
project,
I
see
look,
we
have
really
a
lot
of
branches
and
I
think
it
is
quite
confusing
to
have
so
many
branches,
and
I
think
we
should
not
have
that.
Many
branches.
B
You
know
there's
so
many
stale
branches,
look
how
many
we
have.
So
it's
really
really
a
lot
and
accept-
or
you
know,
kind
of
this
fixed
this.
This
bug
fixed
branches
that
we
have.
You
know
we
should
not
have
all
other
branches.
You
know
like
this.
You
know
this,
this
pr
branch,
the
fifth
that's
five
years
ago
or
nightly
test
build.
You
know
what
I
think
we
should.
B
If
we
do
contributions,
we
should
not
do
contributions
on
the
on
the
harbour
repository.
So
we
should
have
an
own
fork
of
harbor
and
then
create
a
pr
to
this
to
main
harbor,
and
there
is
a
good
github
action
that
synchronizes
the
europe
you
private
harbor
fork
with
the
main
one
you
know,
so
we
could
keep
it
up
to
date,
but
we
should
not
open
up.
B
You
know
branches
or
outside
in
harbor,
and
we
should
clean
up
a
lot
of
those
branches
because
they
could
yeah.
A
A
A
A
Well,
I
think
we
can
open
issue
for
this
one
and
discuss
it
there,
how
we
gonna
approach
this
one
and
if
someone
is
not
forking
the
repository
and
making
the
prs
from
its
own
fork,
I
think
we
should
change
that
like
in
procedural
way
how
how
people
contribute,
but
I'm
super
proud
to
answer
that
question
right
now.
If
we
have
it
in
the
contribution,
maybe
we
have
james.
A
C
In
the
I
haven't
looked
closely
at
writing
code
for
hardware.
I've
only
looked
at
distributions
is
that
what
you're
saying
yeah.
A
Now
for
hubber,
I
I
cannot
remember
if
we
have
it
in
the
contributions
documentation,
but.
D
D
A
I
think
it
was
listed
like
create
a
fork
and
do
this
and
do
that
at
the
remote
and
whatever
but
yeah
yeah,
four
composers,
yeah,
okay,
yeah.
D
We
probably
can
you
probably,
can
have
a
good
action
to
remove
this
and
use
the
branches
yeah.
D
C
A
A
A
D
A
Are
using
forks
and
yes,
new
branches
for
future?
Okay,
okay
I'll
drop
a
line
to
about
that
in
the
maintainers
manic
list.
So
we
we
can
make
sure
that
everyone
is
following
the
same
procedure:
okay,
cool.
A
And
the
last
one
for
today
that
I
have
is,
maybe
you
saw
that
we
have
decreased
the
stale
issues
by
almost
30
to
35,
so
from
almost
1000
issues.
Now
we
have
640
ish,
which
came
out
to
be
an
issue
for
some
some
folks
around
that
we
were
like
say.
Should
I?
How
should
I
say
that
closing
state
issues
too
aggressively?
A
So
I
tuned
a
bit
this
tail
action,
so
we
have
now.
The
grace
period
is
60
days
and
then
30
days
prior
closure.
So
practically
we
have
three
months
issued
to
stale,
which
is
more
than
enough
someone
to
respond
or
to
look
for
feedback.
I
think
so.
Overall,
I
think
the
stale
right
now
is
working
fine
and
that's
a
good
and
healthy
amount
of
issues
that
we
have
active
and
that
will
be
if
someone
else
finds
that
as
an
issue
that
we
reduce
so
much
issues.
A
A
True,
yeah
yeah,
okay,
it's
not
like
100,
true,
always
right,
but
yeah,
but
still
I
mean
the
project
is
like
community
driven.
So
we
cannot
answer
any
all
the
issues
are
there
always
so
something
can
slip
but
yeah.
B
I
just
pasted
a
link
to
an
issue
that
came
up
today
seems
to
be
a
bug
in
the.
B
D
D
Because
we
we
spend
two
weeks
to
on
the
urgent,
critical
security
issues
fixed
so
yeah,
two
one
2
5
2
and
3.
yeah.
A
Okay,
yeah,
that's
okay!
By
the
way,
that's
a
good
like
transition
to
another
question.
Anyone
is
having
is
having
like
a
planned
summer
vacations
for
the
next
months,
because
it's
like
in
europe
at
least
it's
is
the
it's
the
summer
time.
So
folks,
like
me,
I'm
going
to
be
off
august
and
half
of
september.
A
Okay,
yeah,
so
that's
the
overall
question
for
for
the
for
the
audience.
If
someone
can
take
the
community
meetings
for
august
and
half
of
september,
it
would
be
great.
I
won't
be
having
so
much
access
to
internet.
So
I'm
not
sure
if
I
can
leave
these
these
meetings,
if
it's
not
that
I'm
leading
right
now,
though,
thank
you
vadim,
but
I'm
upgraded
to
the
to
the
new
mac
and
it's
not
working
okay,.
A
Thank
you
just
one
thing
you'll
be
online
during
the
release
of
this
to
six
right,
yeah
jan,
can
you
please
work
with
vadim
on
on
that
release?
I
mean
in
the.
A
Yeah,
because
we
still
have
that
in
our
agenda
that
we
should
release
in
the
non-vmware
way
and
with
him
is
like
yeah
yeah
and
after
that
release
after
the
summer
vacations
and
all
the
absences,
we
should
work
forward.
The
github
release
cycle
and
and
processes
just
fyi,
and
if
you
can
yeah
include
with
him
into
that
release,
will
be
super
fantastic.