►
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,
I
think
we
have
16
people
let's
get
started
so
welcome
everyone
to
join
harbour,
commission
meeting.
A
Done
this
meeting
for
a
while
due
to
the
chinese
holiday,
I
think
this
is
the
first
meeting
this
year
after
chinese
spring
festival,
even
though
the
corner
of
rhinos
is
still
spreading,
but
most
of
I
think
all
folks
from
harbour
team
from
email
are
coming
back
to
work.
So
we
will
fight
against
veterans
and
we
will
continue
our
harbor
project
as
well
as
before.
A
A
Today
we
have
very
short
agenda.
We
mainly
want
to
go
over
the
harbor
2.0
features
that
progress
there
will
be
two
sessions.
One
is
presented
by
vincai
about
the
overall
status
of
all
the
sub-component
features.
Another
is
also
wang.
Yang
will
give
us
a
harvard
ui
demo.
Currently,
his
code
is
not
merged
to
master
it.
It
is
on
his
staff
environment.
C
Yeah,
okay,
I
will
introduce
the
development
features
of
1.0.
Briefly,
there
is
only
a
one:
an
anchor
filter
being
covered
to
be
the
cloud
nature
registry
to
support
osa
artifact,
the
key
module
artifact
module.
Well,
it's
almost
done,
and
now
you
can
pull
push
artifacts
from
to
hover
list
and
get
delete
the
artifact
and
check
the
metadata
of
the
four
different
kinds
of
artifacts
of
rhi
and
the
ui
work
is
in
progress.
C
One
will
give
us
a
simple
demo
for
what
we
have
done
for
now
and
another
part
of
what
that
in
progress
it
to
look
for
other
features
along
with
the
new
artifacts.
A
C
D
D
In
the
artifact
list
page,
we
can
see
a
discrete
light
contents,
many
artifacts
each
artifacts
contain
attributes
digest
text
size,
one
basis,
labels
push
time
and
put
time
at
present,
the
the
length
of
data
store.
We
display
is
only
first
80
bits,
but
it
can
objectives
according
to
needs
for
artifacts
the
operate
operation
weak
the
operation.
D
B
All
right,
so
I
just
want
to
add
something
real
quick
can't
hear
me
yeah.
I
just
wanted
to
add
something.
Real
quick
is
that
you
know
the
biggest
change
here.
Is
that
previously
the
rules
represented
tags,
but
they
now
represent
artifacts,
so
you
can
see
that
every
tag
actually
has
has
already.
B
If
your
artifact
has
a
tag
column,
so
an
artifact
could
have
multiple
tags
on
it.
That's
what's
the
biggest
change
in
terms
of
ui
display
in
terms
of
how
we
display
the
actual
container
images
and
home
charts
and
such.
E
B
A
Yeah
so,
but
it
can
still
be
access
to
soon
attacks
right.
E
I
know,
but
if
you,
if
you're,
if
you're,
if
you're
a
consumer-
and
you
have
like
a
lot
of
tags
and
a
lot
of
repositories,
would
be
impossible
for
you
to
know.
What's
what
like,
let's
go
from
the
beginning
again
so
go
to
projects
one
more
time
really
quickly.
If
you
don't
mind.
A
Actually,
actually,
I
think
so
within
this
report
ring
there
will
be
different
artifacts
right,
so
those
artifacts
come
here
at
least
as.
A
Right
so
the
tag
column,
I
think,
most
of
the
time,
the
column
should
have
only
one
tag
right
unless
somebody
has
tagged
in
the
same
artifact
with
different
tag
names.
So
you
will
see
multiple,
so
you
can
most
of
the
time
you
can
still
see
in
attack,
clearly
of
which,
which
artifact
it
referred
to.
E
G
Yeah
this
video
is
similar
like
the
gpr
yeah,
the
issue,
the
artifacts
as
the
primary
of
objects
and
attack
is
just
the
property
of
that
artifact.
So
far,
is
the
only
I
think,
meaningful
property
if
for
the
artifact
is
just
a
number.
So
if
we.
H
E
E
H
F
I
E
F
I
have
a
comment.
Sorry,
I
have
a
comment
about
this
ui
on.
Will
we
support
user
to
somehow
collapse
or
unfold
the
artifact
to
show
the
properties
of
each
pad.
F
Current
you
know
the
the
current
way
for
to
display
the
test
has
is
a
little
problematic,
because
in
notary
the
signature
is
against
tag,
so
it's
possible
that
they
have
their
fort
have
only
one
tag
inside.
G
G
Class
or
yeah
embedded
checklist.
F
E
G
F
F
G
C
G
G
B
B
G
Information
are
displayed,
display
information,
you
don't
need
to.
You
cannot
change
the
the
property,
for
example,
building
history
summary
dependencies
values.
These
are
only
read
the
only
information,
but
for
tags
you
can
remove
a
tag
and
add
a
new
tag,
so
this
is
very
different
with
other
information.
F
Yeah
yeah,
I
think
they
should
be
show
in
the
detail
page
very
important,
yeah,
I'm
not
telling
you
okay.
I
answer.
G
F
Your
question:
okay,
oh
yeah,
and
how?
How
will
we
show
like
in
that
or
manifest
list.
B
Want
to
worry
about
recur,
move
on
so
this
solves
the
issue
of
previously.
When
you
delete
a
hardware
tag
or
docker
tag,
it
deletes
the
adapters
on
tags
that
share
the
digest.
So
you
know
looking
at
this
for
any
given
digest.
We
can
now
choose
to
selectively
delete
tags
without
affecting
the
digest
itself.
So
that's
the
biggest
that's
the
biggest
advantage
that
we
gained
from
doing
this
refactoring
or
one
of
the
biggest
issues
that
we
we're
trying
to
to
address
in
the
manifest
list.
D
Okay,
I
continue
the
demo.
D
D
E
B
If
you
go
back
to
the
artifact,
what
has
that
changes?
The
breadcrumb?
I
just
want
to
say
something
about
that
is
any
artifacts.
B
B
Yeah,
the
icon
is
a
problem
that
hasn't
been
addressed,
but
essentially
on
the
previous
page.
That
was
a
bundle.
It
was
an
oci
index,
essentially
that
contains
yeah
a
list
of
artifacts
shown
here
different
os
and
architectures
right.
So
this
is
something
that
we
didn't
previously
support:
the
ability
to
push
a
fat
manifest
or
an
outside
index
onto
harbor.
B
B
E
B
E
So
I'll
give
you
guys
my
advice
and
and
take
it
to
the
grain
of
salt,
like
just
like
when
you
look
at
tags,
you
show
that
this,
let's,
let's
look
at
the
first
image
right,
50
b8,
568
right.
We
show
that
there's
tax
12
with
one.
Then,
when
you
look
at
the
artifacts,
if
the
artifact
is
a
bundle,
we
should
put
a
bracket
and
indicate
how
many
numbers
are
in
the
bundle
and
allow
them
to
click
on
the
number
to
actually
drill
into
the
bundle.
E
Yeah,
just
like
you
have
tags,
have
it
also
in
the
bundle.
The
the
second
thing
is:
can
a
tag
be
the
same?
Let's
say:
can
I
tag
one
of
these
artifacts,
the
first
one
with
tag,
one
two
three
and
then
tag
the
last
one
with
the
tag.
E
A
E
I
E
E
E
I
agree
with
you
what
I'm
saying
is
that
they
don't
usually
so
we
need
to
support
a
situation
where
someone
is
pulling
an
image
based
on
their
their
ability
to
to
understand
the
tag.
Only
right.
B
E
So
I
mean
I'm
putting
it
in
chat,
but,
like
I
mean
I
just
copy
the
pull
command
from
the
hardware
ui,
and
this
is
what
it
looks
like
it's
project
repository
tag.
So
what
I'm
saying
now
is
you
can
this?
The
previous
pokemon
needs
to
work,
even
in
this
situation
or
with
a
new
ui?
So
can
the
tag
bionic
here
match
multiple
artifacts
and
if
it
does
we're
going
to
hit
problems.
A
Yeah
yeah,
that
is
yeah
that
is
checked
michael,
I
think
you're.
I
I
didn't
I
didn't
quite
on.
I
think
what
you're
saying
there
so
currently.
If
we
have
multiple
tags,
the
user
I
mean
most
users
are
using
tag
right,
so
they
are.
Those
users
might
be
confused
if
they
see
the
this
ggg.4
right.
They
cannot
easily
to
find
its
tag,
and
in
that
problem
you
are
concerned
right.
E
Well,
I
mean
we
should
be
able
to
fix
it
by
search
or
or
or
ideally
most
people
are
not
going
to
tag
the
same
charm
multiple
times.
E
E
So
that's
you
could
see
something
like
that,
but
outside
of
latest
or
stable,
I
don't
see
people
tagging
something
multiple
times,
but
obviously
you
could
be
wrong.
A
E
A
Yeah
yeah,
that
is,
that
is
mature.
F
A
G
B
G
G
A
F
Actually,
I
have
another
comment:
does
this
docker
icon
reflects
the
type
of
the
artifact?
Yes,.
F
F
H
G
F
F
Well,
I
mean
why
young
could
you
click
one
of
the
char,
the
no
no
the
regular
one,
not
the
manifest
yeah.
I
think
there
there's
a
user
in
the
comments
saying
that
we
should
not
allow
user
to
add
a
tag.
B
He
so
this
bj151v
yeah
I
can.
I
can
talk
with
him
offline.
E
E
All
right,
by
the
way,
this
powerful
demo-
this
is
awesome.
I
think
everybody's
excited
about
the
work
that's
going
in
so
I
know
asked
a
lot
of
questions,
but
this
is
what
happens
when
you
have
a
new
change
in
the
ui,
but
this
is
great.
A
Yeah,
given
into
the
time,
I
will
stop
the
sharing
and
stop
the
recording,
and
so
before.
I
close
any
further
questions.
E
This
is
awesome,
look
at
that
harvard
in
dark
mode
cool.
Thank
you.
All.
Everybody
have
a
great
rest
of
your
evening
afternoon
morning.
A
Okay,
thank
you
michael
and
thank
you
all
for
current
meeting
so
see
you
next
time
have
a
close
meeting.