►
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
A
We
have
several
topics
to
cover
the
first
one:
a
quick
update
to
the
version,
1.8,
the
developer
of
the
development
status
and
then
I'll
share
the
the
you
know
the
analysis
report
of
the
com,
our
first
community
survey
we
delivered
several
weeks
ago
and
the
third
part
I'll
talk
about
some
job
sites.
Knowing
issues
I
know
some
guys
have
meet,
have
met
some
issues
from
the
job,
search
or
replication
or
how
to
say.
A
Okay,
next
part
I'll
talk
about
some
upcoming
community
events.
Now
those
events
were
related
with
harbor,
okay,
I'll
give
some
introduction
about
the
events.
A
Then
it's
the
damn
parts.
We
all
you
met
duncan
and
daniel,
who
are
also
harbor
committee
nurse
to
give
some
demo
about
the
pre-perform
refactor
and
the
oil
this
is
supporting.
I
think
the
prepare
flow
is
very
important.
It's
critical
for
you
to
you,
know,
install
or
deploy
the
harbor
into
your
environment.
A
We
have
do
lots
of
you
know
a
refractory
work
on
this
part,
okay,
as
a
regular
wheel.
Also,
we
will
left
several
minutes
for
you
guys
to
you
know
to
ask
a
question
to
raise
preparatory
issues
if
you
have
okay
quickly,
so
first
part
I'll
cover
the
version
1.8
device
development.
Progress
updates
here
is
main
features
of
the
version
1.8
you
can
see
from
the
list.
Most
of
the
primary
features
are
already
done.
Okay,
in
the
version,
a
1.8
robot
account.
Here's
a
check
api.
Now
you
can
use
this.
A
Is
this
api
to
check
the
total
overall
health
citizen
of
a
harbor?
We
add
a
new
master
role
and
we
also
build
the
swanger
ui
into
the
portal.
You
can
use
those
portal
to
you
know
to
bronze
the
harbor
api.
Also,
maybe
you
can
trigger
some
api,
of
course.
Okay.
We
also
provide
a
crawl-like
schedule.
A
So
with
this
crawl-like
schedule,
you
can
you
know,
customize
your
schedule
with
a
flexible.
You
know
a
pattern.
Okay,
we
also
reflect
the
configure
management
and
remove
the
admin
server.
You
know
to
make
the
hardware
to
make
the
configuration
management
more
or
you
know,
a
lightweight
okay,
and
we
also
reworked
the
prepare
script
to
simplify
the
overall
prepare
flow.
A
This
will
be
covered
by
today's
demo
and
we
also
support
otc
supportion.
This
part.
We
also
have
a
demo
to
to
cover,
so
this
part
is
severe
on
the
on
the
development,
but
it's
already
closed
to
the
end.
Maybe
we
can
mark
it
down
in
next
week.
Okay,
the
next
part
is
the
replication
ng.
A
Yes,
the
next
generation
replication
is
the
core
of
the
application
is
almost
done
now
we
are
working
on
to
improve
the
quality
fixed
box
and
implement
some
adapter
to
you
know
to
support
the
replica
harbor
ways
across
other
non-harbor
registries,
so
in
the
first
in
the
1.8
will
support
the
dog
harp
native
docker
registry.
A
Okay,
I
think
the
overall
scissor
is
close
to
end.
Maybe
we
can
mark
it
down
in
field
in
next
several
weeks.
Okay,
so
for
the
1.8,
the
overall
code
of
phrase
data
is
april.
20,
the
ga
data
is
possible
properly
in
the
near
the
middle
of
may.
The
concord
did
not
settle
yet
okay.
This
is
the
overall
of
the
1.8
development.
A
Okay,
so
next
part
I'll
share
the
survey
analysis
report
yeah.
We
have
send
the
survey
link
to
you
guys
through
our
new
group
and
our
recharge
group
and
our
channels.
Some
of
you
guys
may
have
attended
participated
in
this
survey
today.
I'll
share
the
overall
report.
A
A
Okay,
okay,
so
you
can
see
my
screen
now
I'll
show
the
survey
response.
Iris
survey
result
report.
Okay,
this
is
our
first
survey.
You
know
targeted
to
the
harvard
community.
A
It's
closed
in
last
last
week,
so
first
question:
we
have
to
ask
some,
you
know
if
you
use
in
this
way
where
want
to
learn.
What's
your
role
in
the
harvard
community,
you
can
say
most
of
the
participants
are
users.
Okay,
it's
the
percentage
of
the
user.
Nearly
65
and
the
next
one
is,
you
know,
is
some
cloud
cloud
native
architecture.
A
This
is
so
next
one
is
the
contributor.
I
think
we
need
more.
You
know
more
users
to
participate
in
the
you
know
in
the
community
to
do
some
contribution
and
then
become
a
contributor,
but
we
have
a
low
percent
of
the
contributors.
A
Okay.
This
is
the
first
question.
Next
we
ask
about
the
location
of
the
survey
participants
think
actually
we
lose
some
participants
from
the
asian
pacific.
So
look
from
the
relator
we
can
say
most
of
the
participants
are
all
from
the
asian
pacific
from
china,
india
and
some
other
asian
part.
The
next
one
is
north
america,
the
last
one
is
european,
so
I
think
we
need
to
do
more
work
to
promote
the
harbor
in
the
european
region.
A
Okay,
next
one
is
a
way
to
learn
the
version,
the
harder
versions
they
use
in
their
environments.
Okay,
we
a-
fortunately,
we
got
you
know
or
positive
results.
Most
of
the
users
have
have
already
upgraded
their
harbor
to
the
latest
version.
1.7,
only
a
small
percent
keep
in
the
legends
legend
letters
version.
So
this
is
a
it's
a
positive
result.
A
So
the
phrase
to
talk
about
the
approach
of
installing
the.
A
A
Okay,
the
more
that
hover.
Okay,
the
next
part
is
the
harm
chart.
Okay,
so
I
think
yeah
of
the
installer
is
a
still
the
primary
way
to
deploy
hardware
in
the
user's
environment.
A
Okay,
next
one
is
about
what
functions.
Functions
are
of
hardware.
They
are
using
okay.
So
this
way
we
can
ignore
so
everywhere
nearly
everywhere
uses
the
proportion,
the
core
function
of
a
push,
so
we
can
say
the
the
highest.
You
know
the
popular.
The
most
popular
feature
is
the
vulnerability
scanning
modes.
Okay,
72
percent
users
are
like
one
business
scanning.
The
next
one
is
the
air
diaper
and
adaptive
integration
then
replication.
This
is
a
top
three
popular
features
of
harbor
sames
saves
the
content.
Trucks
dig
to
signature.
You
know
it's
less
user.
A
Select.
This
part
we
need
to
learn.
You
know
some
router
calls
why
they
don't
like
the
digital
signature.
A
A
The
highest
the
first
priority
new
feature
they
are
expecting
is
the
cd
pipeline
integration.
I
think
this
may
include
as
a
robot
account
or
some
other
you
know,
support
feature
to
make
the
cct
public
integration
more
smoothly,
because
this
is
the
first
one,
then
is
the
hra.
A
A
We
also
support
h.a
in
the
ham
charter,
deploy
approach
and
for
the
replication
will
also
release
a
replication
ng
in
the
coming
1.8
version.
That
means
we
are
in
the
right
way
to
deliver
the
features
which
are
expecting
by
the
users.
Okay,.
A
So
this
is
a
good
thing
for
us
to
keep
going
on.
We
also
see
some,
you
know
customized
response,
so
this
is,
you
know
not
in
the
high
priority
quarters
open
shift
integration,
import
label
from
dockerflare
or
oh
this
rope
service
account.
We
already
have
okay
I'll,
take
more
time
quickly.
A
A
Those
are
you
know,
you
can
say
nearly
80
percent.
That's
a
good
thing
too.
Okay!
Next,
one
is,
if
you
are
willing
to
do
confusion
to
the
hardware
community
future,
which
domain
are
you
feeling
we
can
see?
Most
of
the
participants
are
from
the
devops
at
the
back
end,
less
less
from
the
front
front
of
front
front
end
development.
A
That's
the
real
kit,
because
of
most
of
our
contributors
of
covering
the
you
know
in
the
back
end
and
devos
domain.
Okay,
so
so
for
the
other.
Two
questions
is
it's
for
the
events
to
get.
If
they
have
attended
some
hardware
community
activity,
that
means
we
can
get
a
as
a
popular.
The
the
popularities
of
harbor
community
seems
more
than
a
hover.
Nearly
60
percent
participants
had
you
know,
did
not
attend
any
harbor
community
activity
before
so
that
means
we
have.
We
still
have
a
long
way
to
promote
our
hardware
community.
A
You
know
to
a
widely
scope
to
let
more
people
know
okay.
So
this
is
the.
A
Okay,
next
party,
about
the
job
service,
annoying
issue
in
the
in
the
you
know
in
the
github
repo
week,
received
several
issues
from
I
related
with
the
job
service.
Here
I
want
to
clear
flat-
or
I
want
to
tell
you-
tell
the
community
that
we
have
got
the
question
on
the
usuals
related
with
your
job
service.
We
have
studied
as
a
fixed
plan
to
improve
how
to
fix
the
related
bugs
for
job
service.
To
improve
the
to
make
it
more
suitable.
A
Okay
is,
a
related
fix
will
be
delivered
into
definitely
delivered
into
the
1.8.
Okay,
maybe
check
check
pick
to
the
1.7
tags
depends
on
the
requirements.
Okay,
so
there
is
a
three
typical
or
property.
One
is
the
job
status
say
some
javascript
will
be
phrased
to
a
specified
one
most
times
they
will
be
phrased
in
pending
sitters
like
us,
zombies,
drawbacks,
okay
and
it
weren't
now
to
be
changed
anymore.
A
So
this
may
cost
okay
the
root
cause
properly
because
of
the
you
know,
still
standard
thinking,
breaking
between
job
or
size
and
the
core
service.
Okay,
so
well
enhanced,
enhances
the
status
of
a
hulk
and
enhance
all
and
also
simplify
the
job
of
status.
Persistent
flow
okay
to
make
it
more
effect
effective
to
make
sure
the
webber
hulk
will
finally
report
the
job
status
to
the
core
service.
Okay,
and
sometimes
some
jobs
are,
you
know,
failed
to
stop
or
to
castle.
A
Okay,
so
for
this
usual
will
remove
some
command
synchronization
channel
across
the
multiple
instance
and
will
enhance
the
condition
of
a
location
job
which
can
be
stopped
at
cast
anyway.
We'll
do
improvement
to
to
fix
the
the
related
issues.
Okay,
sometimes
the
into
the
timing
interval
for
the
periodic
job
for
this
one.
A
A
Okay,
next
party,
about
our
upcoming
community
events,
so
the
first
part
is
about
open
source
hacksaw.
Actually
we
have
mentioned
this
event
before
so
this
event
is
the
only
target
for
the
you
know.
For
the
you
know,
chinese
community
users,
so
I'll
use
chinese
tool
quickly
describe
the
details
of
this
part.
Okay,
so
open
source.
A
Okay,
so
this
is
about
the
open
source
hacksaw,
I
think.
Maybe
we
have
mentioned
in
last
community
meetings.
There
is
some
we
will
hold
some
hardware.
A
Events
co-located
in
the
you
know
covers
both
european
and
china,
so
the
kubacon
european
will
be
heard
in
may
20
and
may
26th
way
or
heard
a
you
know,
a
separate
harbor
meet
up,
and
you
know
in
this
I
mean
I
have
a
fold
and
the
drinks
will
be
provided.
A
So
if
you
are
planning
to
attend
the
kuba
khan,
european
or
kubercon
china,
maybe
a-
and
you
have
some
related
or
interesting
topics
related
with
harvard
with
cloud
native.
You
can
contact.
You
know,
connect
us
to
you
know
to
reserve
a
a
a
chance
to
share
your
topics
in
those
harbor
meetups.
A
Okay,
so
though
the
meters
will
be
both
heard
in
kubercon,
european
and
the
cubacon
china,
so
I
think
I
think
some
of
our
community
contributor
or
end
users
will
attend
on
some
kubocon
conference,
so
welcome
topical
sharing.
If
you
have
good
topics,
please
contact
us,
we'll
reserve
time
for
you
to
share
your
topics,
so
this
is
about
the
upcoming
community
events.
A
Because
today
we
have
a
lot
of
content,
so
I
will
not
ask
your
question
now.
After
demo,
we
can
left
some
time
to
to
ask
a
question
or
to
trigger
some
discussions.
So
it's
now
it's
it's!
It's
demo
time.
A
First,
I'd
like
to
invite
the
harbour
retainer
chen
dong
to
give
us
a
a
demo
about
the
prepare
flow
reflector.
B
Okay,
before
the
diamond
and
I'll
introduce
some
the
function
of
the
prepared
square
before
your.
B
B
Okay,
you
know
in
the
previous
version
the
preparer
squared
is
used
to
use
it
for
preparing
the
environment
for
travel
to
running
and.
B
Create
the
directories
the
hubble
need
required
and
and
generate
some
files
like
secret
keys
and
karen,
because
some
historical
issues,
the
prepared
squabble-
is
a
a
very
huge,
a
big
fire
and
is
too
messy
to
maintain.
B
You
can
say
before
the
preparer
is
one
giant
fire
here
now
in
this
version
we
refactored
the
prepared
fire
and
I
split
the
big
fire
into
different
parts
and
every
you
can
say
this
is
a
structure
of
the
calendar,
preparer
module
and
now,
besides
the
prepare
functions,
and
we
also
move
the
template,
rendering
function
to
the
prepare
module,
which
is
a
which
impressed
version
is
the
user
is
down
by
the
cell
command
and
in
make
file,
because
the
seed
is
cannot
rendering
the
complex
template.
B
So
we
introduce
the
jinja
to
our
template
engine,
so
we
can
navigate
the
ginger's
function
to
gen
to
generate
templates
using
more
complex,
logical
ads.
So
currently,
the
prepare
module
have
two
main
functions.
First,
one
is
to
prepare
the
environment,
the
secondary
generates
the
templates,
and
I
also
we
also
wrapped
it
into
the
container
image.
So
all
the
dependencies
don't
don't
need
the
user
to
consider
rates.
B
In
this
directory,
like
a
chat,
server
or
clairol
code,
this
is
we
put
the
ginger
template
in
on
this
fire.
So
this
template
is
used
to
generate
the
rail
fire
used
in
harbor,
and
the
uterus
is
the
python
file
we
can
use
in
this
to
do
the
function
like
like
their
name,
for
example,
if
the
third
third
in
this
file
is
all
is
all
related
to
generator
search
and
the
chat
is
used
to
generate
a
chat,
related
files
or
something
like
this.
B
Okay
and
the
currently
we
using
the
prepared
script.
B
B
B
There
are
lots
of
items
here
and
the
format
is
a
configure
password
like
formatter,
and
currently
we
removed
a
lot
of
items
because
the
sourcing
pr
they
they
remove
the
admin
server
container.
So
we
also
also
we
move
the
item
because
you
know
you
can
you
can
say
this
this
table,
we
split
the
content.
Here
we
split
the
configurator
into
two
class
system
setting
and
the
user
setting
and
the
system
setting
can
only
sell
on
the
configure
file
and
the
user
settings
are
all
removed
from
the
configure
file
user
can
configure
it.
B
B
You
can
see
the
config
item
left
here
and
this
is
a
host
name,
and
this
is
a
as
the
previous
version
and
we
remove
the
pro
tackle
item,
because
if
you,
if
you
want
using
http,
you
just
uncomment
http
item
here,
if
you
want
to
use
https,
you
just
uncomment
the
http
as
config
and
put
the
certifier
here,
and
we
also
can
configure
the
portal
here.
You
know
in
the
first
originally
the
the
portal
number
is
fixed,
only
18
for
http
and
443
for
https.
B
B
You
can
say
here
uncomment
the
external
database
item
here
and
you
can
configure
the
database,
the
host
port,
username,
pencil
and
ssl
mode,
and
we
are
using
the
external
database
for
hardware
and
this
configure
will
cover
replace
the
local
database
configs
like
the
password,
if
you,
which
means,
if
you
are
using
the
external
database,
the
password
while
using
use
the
the
x
no
database
password
and
okay,
let's
see
the
other
item,
the
data
value
is
introduced
in
this
version.
B
B
How
about
registry
and
the
configuration
is
the
same
as
the
official
hubble
registry?
You
can
refer
this
link
and
the
next
is
the
claire
and
the
job
service.
I
think
this
configuration
is
the
same
as
before
and
the
log
you
can
configure
the
node
library
here.
This
is
harder
to
configure
in
previous
version.
You
should
change
the
email.
B
Okay,
this
is
the
version.
This
is
the
configuration
items
left
it's
more
content,
and
now
I
can
currently
I
show
you
how
to
install
this
most
of
operation
is
the
same
as
before,
and
the
only
thing
you
need
you
know
in
in
the
before.
There
are
three
ways
to
install
harbor
the
offline
package
online
package
and
build
the
hubble
using
source
code.
The
online
package
and
the
offer
of
the
front
source
code
method
is
the
same
as
before
is
transparent
for
users
and
the
current.
B
Only
there
is
a
little
bit
different
is
offline
packaging,
because
all
the
prepared
scrabbler
are
wrapped
into
the
container.
So
you
need
to
know
the
con
prepare
container
before
you
run
the
install
sure,
so
you
you
must
be
sure
that
run
prepare
scraps
of
beef
or,
after
your
first
time,
around
install
the
chair.
For
example,
if
you
you
you,
you
need
a
wrong
installation.
B
B
B
B
And
I'll
show
you
in
the
previous
version
and
the
the
other
difference
is
that
in
the
previous
version,
if,
if
you
want
to
run
travel
with
claire
or
lottery
or
chat,
museum
and
the
hubble
will
generate
three
different
files
of,
for
example,
this
is
a
hubble
1.7,
you
can
say
if
you
wanna
using
the
other
component,
the
hubble
will
generate
the
chat,
museum,
canada,
yamaha,
notary
diamond,
and
if
you
wanna
run
this,
you
should.
B
Like
this,
you
you,
you
need
to
specify
every
files
by
yourself
by
canceling.
B
B
You
know
you
you,
you
saw
me
just
I
using
instruction
install
hello
with
three
components.
You
can
see
all
my
our
compose
file,
which
is
included
a
three
components
configure.
B
B
B
Okay,
you
can
say
the
dot
compose
file,
and
this
includes
you
can
see
a
postgrade
call.
B
B
B
B
B
B
A
Okay,
thank
you.
This
is
really
awesome.
So
I
think
this
is
very
critical.
You
know
change
for
users
to
deploy
their
harbor.
Oh,
I
do
like
to
reserve
two
minutes
for
you
guys
to
ask
a
question.
Okay,
so
as
a
regular
av,
you
are
not
good
at
speaking
english.
You
can
directly
use
chinese
to
answer
the
question.
A
A
A
A
A
Paper
flow
refactoring,
so
let's
move
to
the
next
part
next
part
is
the
oidc
supporting
so
from
the
analysis
report.
You
can
see
it's.
It's
also
a
you
know,
exciting
new
feature
from
the
community,
so
I'd
like
to
invite
harper
carmen
dinner
daniel
to
give
us
a
demo
about
this
card
lanier.
It's
your
time.
A
C
Yeah
you'll
see
my
screen
now,
okay,
so
the
best
one
is.
We
have
been
asked
about
supporting
the
sso
flow
for
a
while.
So
in
one
day
we
decided
to
make
some
progress
in
that
part,
so
the
choice
is
oidc
and
this
is
the
development
build,
because
some
of
the
code
is
not
merged
to
a
master,
yet
hopefully
in
the
next
one
or
two
days-
and
this
is
the
environment
fresh,
install
and
I've
logged
in
as
admin.
C
C
You
need
to
switch
the
outmode
to
idc
and
you
need
to
provide
the
following
parameters
such
as
the
name
of
the
provider,
the
oibc
endpoint,
which
will
have
to
be
a
oibc
compliance,
server,
endpoint
and,
of
course
you
need
oidc,
client,
id
client,
secret
and
or
this
is
go,
and
just
in
case
you
are
running
oidc
provider
with
your
self-signed
certificate
such
as
you
know,
if
you
are
running
tax
or
keep
up
with
your
self
sign
certificate,
you
need
to
check
this
box
to
skip
the
verification
of
the
certificate.
C
So
in
this
demo,
I'm
going
to
configure
hardware
to
use
google
to
login,
but
I
don't
want
you
to
see
my
secret
of
google,
so
I
I
need
to
run
a
script
to
do
the
configuration.
It's
just
called
a
configuration
api
of
power
to
do
the
configuration
and,
after
that,
if
you
refresh
yeah
here
it
is
so
I
applied
for
oidc,
client
from
google
developer
console
and
the
scope
you
need
to
contain
the
open
id
in
this
scope.
C
That's
a
part
of
the
standard
of
oidc
and
in
addition
to
that,
you
can
add
such
as
profile
and
the
email
so
that
when
we
onboard
a
user
to
harvest
database,
we'll
have
more
information,
and
this
offline
access
is
recommended
also
is
for
getting
the
refresh
token
so
that
your
token
will
not
be
expired
very
soon.
That
will
impact
the
use
case
when
using
double
cli,
which
I
will
demo
later
so
after
we
save
this
configuration.
If
I
log
out
you'll
see
there's
a
new
button
here,
I
can
log
in
via
the
oip
provider.
C
Okay,
so
here's
my
google
login
page,
if
I
choose
one
of
my
gmail
account,
it
will
challenge
me
with
my
password.
C
So
after
a
successful
authentication
I'll
be
ready
wrapped
to
cover
now
because
it's
the
first
time
I
log
in
using
my
google
account,
I
need
to
onboard
this
user
to
harbor,
so
I
need
to
provide
a
username
for
harvard
so
when
for
so
I'll
choose,
for
example,
daniel
here
click
save
okay,
I
mean
now
I'm
a
regular
user
in
harbor
now
I
can,
for
example,
create
a
project
called
demo
and
meanwhile,
if
other
user
create
a
product,
he
can,
you
know,
see
me
in
the
user
list
and
add
daniel
as
a
member
to
the
product.
C
So
it's
all
the
same
after
it's
onboarded
to
harvard.
So
that's
the
web
on
word
flow.
Addition
to
that
we'll
also
need
to
support
the
docker
cli.
One
challenge
here
is
that
in
this
example,
normally
you
can
use
the
your
password
of
the
external
authenticator
to
authenticate
against
cover
when
you're
using
docker
cli.
C
But
in
this
case
we
can't
do
that
because
we
don't
want
to
see
your
password
of
external
service
like
I
cannot
use
my
google's
password
and
send
it
to
power
is
very
insecure,
so
to
work
around
that
we
provide
a
concept
called
the
cli
secret
secret
that
will
be
associated
to
your
oidc
token
stored
in
harvest
database
and
when
you
are
authentically
using
this
secret,
harvard
will
try
to
verify
your
idc
token
if
it's
expired.
C
Cover
will
try
to
refresh
this
token
such
that
the
secret
will
be
valid
for
a
long
time,
and
just
in
case
I
remove
my
account
from
google
or
I've
been
removed
from
some
external
oidc
provider.
This
secret
will
be
invalidated
right
away.
So
currently
we
don't
support
retrieving
this
secret
from
ui.
C
C
C
There
it
is
so
that's
the
cli
user
experience,
so
this
part
is
still
working
in
progress,
but
most
of
the
workflow
we're
gonna
support
in
1.8.
I
have
demoed
later
then.
After
this
we
gonna
support
user,
getting
a
cri
secret
from
his
profile
pane,
and
we
probably
will
support
the
user
to
revoke
this
cri
to
improve
the
security
and
some
refinement
on
the
ui
or
or
label
etc.
A
C
C
C
A
No
all
right!
Okay!
Thank
you
thanks!
Thank
you,
daniel
for
the
awesome
demo
awesome.
I
think
we
have
a
lot
of
the
time.
So
I
will,
you
know,
use
one
minute
to
do
preview
for
next
comedy
meeting
next
coming
meeting.
We
may
do
some
more
preview
demo
for
the
replication
next
generation.
A
Yeah
replicate
both
image
and
harm
chart
from
harbor
to
non
harbor,
so
that
will
be
the
topic
for
next
community
media.
Okay,
so.
A
And
we
have
run
out
of
time,
but
I
will
not
ask
any,
as
I
don't
think
we
have
any
time
to
you
know
to
talk
about
the
other
topics.
Yeah.
If
you
have
any
other
questions,
you
can
release
into
our.
A
You
know
the
related
email
group,
though
the
information
you
can
be
found
in
the
github
report,
with
any
fair
okay.
So
the
meeting
is
recorded
and
the
word
the
recall
recording
will
be
updated
to
the
meeting
schedule
later.
You
can
also
find
this
file
in
the
github
community
record.
A
A
A
A
So,
okay,
it's
great!
So
thank
you.
Thank
you
for
the
demo
operator
presenters
at
the
our
community
user.
Let's
say
next
the
next
week
next
community
meeting,
okay,
bye-bye!