►
From YouTube: CNCF's Harbor Community Zoom Meeting - April 6, 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
B
A
I
I
can
see
the
demon
nodding,
so
I
suppose
okay,
so
I
I've
added
few
stuff
over
here.
A
So
I
want
to
go
first
and
then
we
can.
We
can
continue,
there's
a
discussion
open
for
the
notary
deprecation.
A
A
So
please
share
your
thoughts
there
for
the
rest
of
the
list
that
I've
added
here
are
all
the
that
are
aimed
to
be
in
two
six.
So
I'm
not
sure
if
it
doesn't
make
sense
to
go
over
each
of
any
each
of
each
of
this
and
then
discuss
it
over
here.
It
depends
on
you.
If
you
want
to
do
discussion,
we
can
start
with
the
notary
or
we
can
jump
to
some
something
else
that
it's
more
urgent
right
now
at
the
someone
else's
agenda.
A
Please
also
make
sure
you
add
yourself
to
the
to
the
discussion
list
over
here.
I'm
going
to
share
that
in
the
channel
hey
mark.
C
Nice
to
payover
here:
do
you
want
me
to
introduce
myself
yeah
yeah,
so
I'm
I'm
mark.
I
work
at
cisco
as
an
sre.
C
I
work
at
etni,
which
is
the
kind
of
the
incubator
business
unit,
cisco
and
we
started
using
hardware
a
little
bit
over
six
months
ago,
so
it
etn
itself
is
about
incubating
small
projects,
starting
small
projects
working
with
the
design
partners
to
work
on
those
projects,
and
we
needed
a
solution
to
distribute
the
projects
that
we
work
on.
So
we
initially
we
use
dcr,
but
the
authentication
and
the
permissions
there
wasn't
really
the
best
solution
for
for
our
purposes.
So
we
decided
to
go
with
hardware.
B
C
C
I
think
you
probably
saw
me
on
slack
from
time
to
time
and
on
any
various
issues.
We
had
some
issues,
some
of
them
we
were
able
to
work
around
some
of
them.
C
A
Great
great
to
have
you
here
so,
as
you
can
see
the
the
chat
list
that
those
are
normally
the
folks
that
can
be
able
to
help
you
out
with
your
issues
so
yeah
more
than
welcome.
I
can
see
also
alexander
parth,
I'm
sorry
if
I
mispronouncing
names,
I'm
not
sure.
If
I
see
your
name,
I've
seen
your
name
in
our
meeting
so
far.
D
Hi,
can
you
hear
me
now
yeah
great
great
thanks,
yeah,
I'm
I'm
first
time
here,
I'm
I'm
working
at
mercedes-benz
group
hd
in
germany
and
we
are
using
the
harbor
registry
since
one
year
I
think,
roughly
and
yeah
we
use
it
in
three
different
regions,
so
in
the
emea,
apec
and
nasa
region
with
different
amount
of
images,
our
biggest
region
is
emea,
with
over
520
000
images.
Currently.
D
Yeah,
I'm
I'm
I'm
the
product
owner
of
the
platform
with
my
with
my
team,
and
maybe
you
also
saw
me
in
different
issues
from
the
past,
because
currently
we
have
some
issues
open
issues
which
are
not
fixed,
yet,
hopefully
they
will
be
fixed
in
new
versions
or
in
in
the
near
future
like
or
our
biggest
issue
at
the
moment
is
the
api
calls
stuff
how
this
is
working?
D
A
Yeah,
as
young
said,
thanks
for
the
issues
and
welcome,
can
I
ask
you
alexander
and
then
and
you
mark,
if
you
can
reach
out
to
me,
I
really
want
to
discuss
your
use
cases
and,
if
you're
happy
to
to
be
added
to
the
doctors
list
with
your
use
cases
and
to
be
like
officially
in
the
into
the
harvard
family,
it's
a
company-wise.
I
mean.
A
A
A
I
I
used
to
work
for
a
little
bit
like
a
year
to
from
restaurants
bank
and
we
were
located
in
srigath
at
the
time.
So
I
was
just
curious.
A
Okay,
okay,
not
sure
if
someone
else
added
anything,
I'm
gonna
check
again
the
lists
to
the
agenda
for
today.
A
Anyone
with
any
topics
or
we
can-
we
can
discuss
a
bit-
the
notary,
deprecation
and
some
of
the
other.
A
So
I've
created
that
that
discussion,
because
we
somehow
prematurely
announced
that
we're
going
to
deprecate
nutri
without
discussing
it
with
the
with
the
community.
So
there
is
nothing
much
right
now.
A
So
please,
if
you
have
some
doubts
about
deprecating,
notary
or
if
you,
if
you
want
to,
have
it
longer
or
you,
whatever
all
your
thoughts
will
be
nice
to
have
there,
because
the
initial
plan
was
to
deprecate
it
in
two.
Seven
correct
me
young,
if
I'm
wrong,
but
that
will
not
allow
enough
time
for
folks
to
migrate
to
cosine
or
some
other
solution.
A
A
A
What
else
the
all
those
are
from
roger?
He
asked
me
if
I
can,
if
I
can
go
through
that,
not
sure
if
it
makes
sense
to
go
over
all
of
them
right
now,
but
those
are
for
the
two
six
build
and
they're
all
in
the
road
map.
I
think
some
of
them
are
by
young
others
are,
I
think,
from
vadim
is
very
active.
A
So
let's
go
like
this.
A
F
F
G
And
we
have
already
agreed
a
sub
a
repository
in
the
undercoat
harbor
and
to
do
a
limitation
to.
Firstly,
we
just
want
to
support
the
arm.
G
And
then
we
can
extend
the
project
to
support
other
cannot
platform,
but
the
current
status
is
that
the
contributor
from
the
community
is
continue
working
on
that
project.
But
it's
not
a
guarantee
for
2.6.
G
G
F
What
do
you
know?
What
does
the
contributor
needs
to
do
so
in
order
to
complete
it?
Is
there?
Is
there
some
task
on
their
side
that
they
need
to
complete,
or
is
it
is
other
tasks
on
our
site
that
we
need
to
do.
G
E
G
We
are
using
this
repository
to
tracking
implementation
and
the
issue.
We
just
create
issues
for
tasks.
G
You
can
see,
the
main
contributor
is
is,
which
is
the
community
contributor.
G
Yeah
yeah,
but
we
can
risk
graduate
to
meet
others
who
have.
A
Yeah,
because
I
I
I
was
I'm
not
seeing
that
that
that
event
in
the
project
calendar,
so
it's
something
set
up
between
you
folks
or.
A
A
If
you,
if
you
can,
can
you
send
it
to
the
mailing
list
so
it
can
enter
the
the
project
channel,
the
project
calendar
and
if
someone
wants
to
join
and
if
you
also
can
record
those
meetings
will
be
great.
So
people
can
like
me
and
vadim,
which
are
in
different
time
zone,
can
can
follow
up
afterwards.
A
A
If
you,
if
you
don't,
have
the
the
zoom
account
for
harbor,
I
can
share
that
with
you
and
and
that
will
be
automatically
uploaded
into
youtube.
And
then
we
can
create
like
a
a
different
playlist
in
youtube.
Just
for
for
those
discussions
and
then-
and
then
this
topic
in
particular.
G
The
the
regular
meeting
is
hosted
by
the
google,
not
me
so
do
you
mean
that
I
I
should
share
the
since
I've
come
to
jupiter
I
I
don't.
G
G
All
these
things
are
public,
because
that
and
juve
is
not
it's
just
a
farm
community
and
this
project
is
100
houses
by
a
community
and
not
by
the
maintainer.
I
mean
I
just
provide
my
my
technical
support
and
select
suggestion
for
to
their
proposal
under
their
implementation,
but
they
are
the
they
are
hosting
this
project
and
so
but
yeah
yeah.
I
will
ask
drupal
to
add
the
information
about
meeting
black
schedule
or
link
into
this
project.
A
F
I
mean
it
has
some
nice
potential
for
the
project
itself
because
they
are
working
on
on
modifying
and
updating
the
make
files
and
the
build
system
to
support
the
multi
architecture.
So
this
can
be.
I
mean
we
can
benefit
by
that.
If
you
know
updating
the
the
project,
project
manifests
and
and
make
files
as
well
or
make
them
more
understandable,
because
I
mean
there's
like
I
think
yeah,
I
see
a
few
potentials
here
that
we
could
use
from
their
work
for
our
for
ourselves.
F
You
know
not
just
for
the
multi
architecture,
but
also
you
know
how
they
you
know,
building
and
making
the
project,
because
this
this
current
work
that
I
see
here
in
the
make
file
that
you're
scrolling
now
it
it
looks.
I
mean
it
looks
better
than
what
is
in
the
project
harbor.
You
know,
because
the
project
harbor
is
currently
already,
I
would
say,
quite
mature
and
also
a
lot
of
things
there,
which
might
not
be
needed
and
not
that
clean.
F
A
And
another
question
for
myself:
the
release
for
for
x86
and
for
arm,
for
example,
they'll
go
in
parallel
or
like
we
release
two
five
or
whatever
to
six
for
for
x86,
and
we
release
264
arm.
G
Yes,
the
future
will
we
will
align
these
two
projects,
but
maybe
arm
will
delay
for
one
or
two
weeks
after
go.
Harbor
is
released.
G
G
I
think
we
can
just
ship
a
arm
in
this
sub
project,
not
just
the
stripped
in
the
upstream.
I
mean
gohan
harbor,
I
I
I
we
can
just
add
a
link
in
to
maybe
to
bonsai
when
at
least
knows
to
point
that
there
is
a
arc.
A
I'm
asking
because
many
many
other
projects
are
when
they
release
their
release
for
all
the
architectures
that
they
have
in
their
support
list
and
maybe
the
effort
of
releasing
that
and
keeping
the
source
code.
Sync
and,
as
the
team
said,
like
all
the
make
files
and
everything
all
the
processes
for
releasing
are
just
the
same
and
we
actually,
we
have
one
release
process
and
we
release
everything
at
once.
G
G
A
Yeah
so
yeah
that's
definitely
get
roger
in
for
this
discussion.
E
A
A
Okay,
next
one,
I
think
it's
from
you
actually
for
the
the
kids.
G
A
So,
what's
the
questions
here
I
mean
all
the
all.
These
issues
that
are
listed
here
are
aims
to
be
into
this
to
six
release
so
yeah.
We
should
either
discuss
them
or
everyone.
I
I
don't
want
to
waste
everyone's
time
on
discussion
this
one
by
one.
So
please,
everyone
take
a
look
at
this
every
every
single
one
of
this
and
and
and
and
check
what's
this
status,
and
if
you
can
help
out
with
this
one
to
to
get
it
into
six.
A
F
It
is
already
approved,
you
know
it
does
have
the
the
minimum
required
approval
of
two,
so
it
could
be
technically
merged.
Yes,.
G
Yeah
yeah,
the
the
other
just
have
have
already
created
the
engineering
story
airbag
in
the
harbor
republic
and
and
as
someone
sub
tasks
like
issues
between
the
ipad.
G
Associated
with
this
proposal-
and
he
has
already
created
one
full
request-.
A
A
So
from
process
point
of
view,
I'm
I'm,
I
think
roger
has
to
be
here,
but
I
think
we
we
should
first
close
the
proposal
and
and
we're
sure
about
what
exactly
we
have
to
to
work
on
and
then
create
the
issue
and
link
it
to
the
closed
proposal.
Because
now
we
have
the
proposal
open
and
in
the
same
way
we
have
the
issue
and
it's
kind
of
messy,
at
least
in.
A
G
I
think
we
can
just
merge
this
proposal
right
now,
since
we
have
already
got
two
upfront.
A
If
you
can
get
someone
else
from
the
engineering
team
to
take
a
look
at
this
one
and
then
we
can
merge,
I
otherwise,
my
my
my
approval
will
just
fake
just
to
be
able
to
merge
it
which
doesn't
work.
G
G
A
About
that
I've
created
something
into
the
website.
I
think
only
for
now
I've
created
the
the
web
decod
code
owners
like
this
for
the
website
repository,
and
I
think
we
should
create
the
same
thing
and
I
think
I've
opened
that
pr
into
the
main
repository.
A
Or
maybe
I
didn't,
but
we
should
create
a
code
owner
file
into
the
main
repository.
So
if
someone
creates
an
issue,
pr
gets
a
subset
of
all
the
maintainers
associated
automatically.
So
we
don't
miss
a
pr,
because
we've
I've
seen
that
someone
opens
the
pr
and
that
pr
stays
there
for
four
weeks
without
being
even
reviewed
from
single
person
or
notified
by
by
the
the
creator
to
to
the
maintenance
team.
A
So
I'm
gonna
open
the
pr
for
this
one.
So
we
can
get
get
like
a
proactive
notification.
If
someone
creates
a
pr
there.
A
I'm
just
curious
if
you
want
to
create
the
whole
maintenance
team
to
be
assigned
to
this
one
or
just
like
a
subset
of
the
maintenance
team,
like
a
representative
subset
like,
for
example,
yuyan,
vadim
and
tianon
as
the
main
three
organizations
representing
the
the
project
right
now,
and
of
course
it
could
be
more
folks
from
from
vmware
and
then
folks
from
the
other
organizations
as
well.
A
F
D
F
A
A
Okay,
so
let's
see
the
other
proposals,
at
least
to
fix
the
proposals.
F
So
I
remember
this
this
functionality,
so
it's
a
user
proposed
kind
of
a
conversations
con
conversion
service
to
nidis,
which
is
a
different
image,
packaging
format
and
he
wanted
to
integrate
this
into
harbor,
and
so
our
our
proposal
was-
or
I
mean
it-
wasn't.
It
was
a
response
that
was
communicated
to
the
user,
but
it
was
our.
I
would
say,
a
consensus
that
I
still
remember
was
to
say
this
is
not
something
for
harbor,
you
know,
and
so
that's
why
nobody
responded
there
or
nobody
approved
or
disapproved
the
progress.
F
There
was
some
feedback
on
the
code
and
and
things
like
this,
but
there
was
no
yeah,
no
approval
disapproval
to
the
user.
So
that's
why
it's
kind
of
still
in
this
pending
state.
We
didn't
say
yes
or
no.
F
A
G
So
for
for
this
one
we
have
already
present
in
the
community
meeting,
maybe
in
the.
G
And
we
we
made
a
decision
that
we
should
create
a
stub
repository
for
acceleration
service.
That
means
we
want
to
create
a
acceleration
as
spec
for
harvard
to
do
the
further
integration
and
they
have
already
working
on
this
project
and
all
of
the
contributors
are
from
alibaba
our
company,
and
we
have
a
regular
weekly
meeting
to
discuss
the
progress
and
tasks
so.
G
It's
visible,
we
have
a
public
repository,
we
have
public
suck
channel,
we
we
have
present
the
proposal
in
the
community
meeting
and
discard
the
proposal
and
make
the
decision
not
in
the
community
meeting.
So
all
those
things
are
public,
I'm
not
sure
which
one
which
part.
Do
you
mean
it's
not.
F
G
For
the
detailed
discussion
we
just
used
the
slack
channel,
I
forgot
the
name,
it
should
be
hardware,
slash
amy,
accelerator,
yeah
yeah.
We
just
need
that
channel
to
discuss
some
more
details.
G
A
Hey
you
say:
there's
a
effort
going
on
in
in
in
this
one.
F
A
And
it's
it's
when
it's
in
different
repository
and
not
linked
and
then
slack
channels
not
linked
it's
kind
of
hard
to
follow.
If
something
is
going
on
or
not
so
ian,
can
you
what
was
the?
What
was
the
slack
channel?
You
say.
F
G
These
are
two
the
proposal
not.
G
We
can
just
refer
to
the
sub
repository
of
the
add
link
to
yeah
this
one.
This
one
is
just
for
the
us,
but
this
is
another
one.
Actually,
okay
switch
back
to
the.
G
Yeah,
this
is
the
original
proposal
for
exercising
service,
but
the
other
one
is
just
one
kind
of
implementation.
G
On
what
I'm
sorry,
what
implementation?
Yes,
it's
just
one
kind
of
image,
acceleration
surveys.
G
But
that
one
is
just
a
spec:
we
just
want
to
define
the
interface
that
for
harvard
to
do
the
further
integration
with
extension
surveys,
but
this
one
is
just
one
of
the
implementation.
G
And
a
convention
just
want
to
submit
their
acceleration
service
to
harvard,
I
mean,
contribute
their
service
to
harvard,
but
this
service
just
follow
the
spec
defined
by
another
proposal.
A
A
In
long
terms
with
which
one
is
the
okay,
is
it
correct
if
I,
if
I
change
them
like
this.
A
That
this
initial
one
for
the
conversion
service
kind
of
created,
the
the
one
for
the
acceleration
service
and
that's
the
and
that's
the
repository
that
is
currently
worked
on.
G
The
167
is
is
just
for
this
accelerator
service
pack,
I
mean
we
just
use
that
project
to
define
the
interface
to
what
how
the
accelerator
service
will
interact
with
harbor
and
for
the
165.
G
It's
just
one,
even
implementation,
based
on
the
spike
I
mean,
based
on
the
system.
A
Okay,
so
that
chain
is
correct.
Okay,
do
you
think
that
who
had
that
to
end
up
as
supported
part
of
the
harbor
implementation?
G
We
just
have
we,
we
have
some
discuss
around
it,
but
for
the
first
phase
one,
we
just
do
the
simple
integration
with
the
harvard.
That
means
the
hardware
just
send
up
a
webhook
to
the
service,
and
then
the
service
will
convert
the
image
back
to,
however,
so,
but
for
the
first
phase
two,
we
want
to
do
some
further
integration
with
hardware
harder,
but
this
is
still
under
the
stars.
G
G
Currently,
we
can
see
it's
a
separate
project
at
some
harbor.
A
Okay
but
looks
like
we
have
a
lot
of
this
proposal
hanging,
so
I
think
we
should
set
up
a
regular
triaging
of
the
of
the
repositories,
so
we
can
clean
up
old
ones
and
then
and
give
space
to
the
new
ones
and
and
see
decide
if
we're
gonna,
I'm
in
favor
actually
to
if
something
is
staying
there
and
nobody's
taking
care
of
it.
For
the
last.
I
don't
know
seven
seven
months,
just
let's
close
it
and
it
doesn't
make
sense
if
just
to
stay
there
and
to
not
to
be
active
at
all.
A
So
what
do
you
think?
That's
a
question
for
for
everyone
if
we
set
up
once
a
month
at
least
a
triage
session,
so
we
we
can
go
over
issues
prs
and
proposals,
maybe
not
in
that
order,
but
to
clean
up
a
bit
of
repo
and
to
get
some
motion
into
monitoring
the
the
repository
and
answering
prs
and
answering
issues.
F
Yeah
yeah,
so
there's
I
mean
the
proposals
are
not
so
many,
so
the
proposals
we
can
discuss
in
each
community
meeting
because
it's
usually
one
proposal
every
I
would
say
a
month
or
something
you
know
so
that's
easy
to
discuss,
but
issues
are
currently
quite
quite
a
few
I
mean
we
have
like
1
000
issues
open
still,
and
I
would
say
that
you
know:
90
percent
of
those
issues
can
be
closed
or
need
to
be
trashed.
You
know
and
summarized
together,
so
this
yeah.
F
This
is,
I
think,
a
big
chunk
of
the
work
there
and
we
can
then
kind
of
automate
a
few
things
that
issues
that
don't
have
engagements
can
be
closed,
and
so
we
need
to
yeah.
We
need
to
close.
We
need
to
get
rid
of
those
thousand
issues
there
because
yeah,
it's.
F
Like
stale
ones
and
such
or
exactly,
for
example,
if
they
stale
switch
or
summarize
them,
or
you
know,
bring
red
relative
ones
together,
and
then
we
we
see
how
many
issues
that
are
related
to
each
other
and
then
we
can
address
them
in
in
a
separate.
You
know,
change
change,
request
or
change.
B
F
Yeah,
but
we
can
you
know,
I
mean
we
don't
have
to
do
it
immediately,
but
it's
just
somewhere
along
the
way.
B
A
Yeah,
so
we
we
can
try
to
fix
something
for
next
week,
for
example,
and
work
on
like
an
hour
or
something
with
this
one
I'll
try
to
get
roger
in
that
as
well,
because
he
has
the
overview
of
the
project
itself.
So
it's
good
that
we
have
someone
from
from
that
site
as
well,
not
only
engineering,
okay,
I'll
I'll.
A
Take
that
and
I'll
talk
with
roger
tomorrow
about
this
one
and
and
we'll
we'll
set
up
something
because
it's
not
it's
not
cool,
to
have
a
thousand
issues
in
the
repository
at
all
shows
how
to
say
not
much
of
engagement
from
the
towards
the
community.
A
So
we
have
to
work
on
this
one,
okay,
okay,
that
that
took
a
lot.
We
have
a
few
more
minutes
left
anything
else.
We
can
go
on
and
on
on
this
this
list.
But
let's,
let's
leave
it
for
next
week.
A
Jan
just
one
question
for
you:
did
you
make
any
progress
on
the
reported
issue
about
the
replication
that
I
found
this
morning?
I
mean:
are
we
gonna
release
tomorrow
or
we
will
leave
it
for
for
next
week?.
G
I'm
working
on
fix,
probably
we
can
have
another
rc
build
tomorrow
and
hopefully
we
can
actually
end
up
this
week.
A
A
Mm-Hmm
thanks
a
lot
for
yeah
just
for
fyi
for
everyone.
I
was
working
on
the
block
proposal
for
the
cosign
integration
and
I
found
the
issue
that
replication
doesn't
work
as
expected.
So
jan
is
working
now
on
this
one
to
fix
it.
A
Okay,
so
five
minutes
more
anything
else
from
the
new
folks
on
the
co.
Did
we
bore
you
to
death
with
with
this
very
improvised
triaging,
and
if
you
want
to
add
something,
if
not,
I
think
we
can
have
five
minutes
for
the
next
one.
I
suppose
many
of
us
are
having
upcoming
meeting
in
five
minutes.
C
Yeah,
it
is
interesting
to
see
how
these
community
meetings
go.
I
mean
this
is
great,
I
guess
we'll
talk
to
each
other
offline
or
or
somewhere
and
as
I
mentioned,
I
do
have
a
couple
of
topics
in
my
head
that
we
could
talk
about
and
I
bring
those
up
there
and
then
we
can,
I
don't
know,
decide
whether
they're
worthy
for
this
meeting
as
well,
and
maybe
we
can
talk
about
them
next
time.
A
Yeah
feel
free
to
reach
on
slack
our
response,
I
think
we're
in
the
same
time
zone
or
pretty
much
the
same
time
zone.
So
I.
A
Yeah,
it
would
be,
it
would
be
easy
all
right
by
the
way
my
shirt
is
that
from
is
that
from
copenhagen
the
copenhagen
mark.
Sorry,
the
t-shirt
is
that
from
the
cucumber
island
or
oh.
F
A
B
F
B
A
Whatever
works
for
you,
you
can,
you
can
ping
me
in
slack
and
we
can
chat,
we
can
set
up
a
very
short
meeting
and
we
can
just
discuss.
My
idea
is
just
to
to
get
some
kind
of
information
from
your
site.
How
are
you
using
cover?
What's
your
use.
A
Stuff
like
this,
and
if
you
feel
comfortable
sharing
that
with
the
public
just
to
formalize
it
in
a
few
sentences
and
to
add
you
add
your
logo
at
your
use
case
and
that's
it
pretty
much,
no
engagement
more
than
that.
Just
pretty
simple.