►
From YouTube: 2022 09 20 Jenkins Infra Meeting
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
A
Let's
get
started
with
announcement.
First
of
all,
this
the
new
weekly
has
been
re-uh,
published
checklist
almost
done
thanks
Mark.
The
image
should
be
available
in
a
few
minutes.
I've
manually
started
the
trusted
CI
job
yep
thanks
Mark.
So
sorry,
I've
made
a
bit
of
noise
on
the
IRC
Channel,
because
I
saw
in
the
build
logs
messages.
I
took
it
was
stopping
the
release,
but
it's
not.
A
It
has
been
released
correctly,
but
that
means
we
have
tests
not
sure
if
it's
flacky
test
or
real
issue,
but
you're
better
to
mention
it
we'll
see
if
infrasia
is
down
for
the
next
days.
B
No,
the
the
thanks
very
much
for
checking
I'm
glad
you
checked,
because
it's
that
that
probably
should
have
failed.
The
build
I
think
it's
a
Surefire
bug,
I
think
it's
a
maven
bug
that
it
didn't
fail.
The
build
and
I
think
the
maven
bug
is
an
interesting
Corner
case
that
needs
more
exploration.
Thank
you.
A
Thanks
Mark
for
the
explanation,
then
so
we'll
see
second
announcements:
devops
War
next
week,
which
mean
next
week
we
will
cancel.
It
has
been
removed
from
the
calendar,
but
next
week
team
meeting
is
canceled.
So
don't
expect
a
meeting
next
week,
meeting
canceled
Mark
do
we
have
a
weekly
next
week.
B
A
A
C
A
A
I
heard
it
was
removed,
I'm,
not
sure.
If
it's
is
it
still
kept
I.
B
Haven't
followed
the
email
Daniel
sent
a
public
email,
sent
an
email
to
the
public
security
advisories
list,
saying
that
there
will
be
a
plug-in
security
update
tomorrow
that
the
plug-in
security
release
affects,
but
the
plugins
affected
by
the
security
release
are
less
than
installed
in
less
than
one
percent
of
Jenkins
installations
in
the
world.
So
it's
a
relatively
low
impact
when
I
I
did
want
to
spend
a
minute
on
this
one.
We
made
a
mistake
two
weeks
ago,
when
we
mentioned
that
today
there
that
tomorrow
there
would
be
a
security
advisory.
B
We
knew
that
two
weeks
ago,
but
we're
not
supposed
to
disclose
that
to
the
world
until
the
Jenkins
security
team
says
it.
So
just
a
reminder
to
all
of
us
as
we
assemble
the
agendas.
Sometimes
we
have
information
that
we
have
to
filter
before
we
put
it
into
the
agenda.
Sorry,
oh
no!
You
know
it
was
it's
no
big
deal.
It's
just
a
reminder
to
all
of
us
that
oh
yeah,
that's
right:
security,
Advice
security,
Communications
come
from
the
security
team,
including
the
dates
of
things.
B
Now
the
the
date
of
something
is
actually
a
relatively
low
risk.
Piece
of
information,
but
in
a
conversation
with
them,
Daniel
noted
that
sometimes
it
can
be
disruptive
if
people
expect
a
security
advisor
and
then
it
doesn't
happen.
A
Okay,
in
terms
of
actionable,
to
be
sure
that
we
don't
already
rely
on
ourselves
because
I,
don't
trust
myself
on
that
kind
of
area.
Do
you
remember
because
I
I
think
I'm
not
on
the
I'm
not
reading
the
mailing
list,
the
advisory
mailing
list?
Could
you
share
in
the
link
to
that
advisory
link?
If
it's
public,
we
have
a
mailing
list
that
we
can
all
check.
So
that
will
be
the
source
of
Truth
for
our
next
meeting
and
we
don't
have
to
worry
about
filtering
ourselves
or
not
so.
B
A
B
Mark
for
that,
and
and
even
if
you're
not
subscribed
to
the
the
list,
it's
a
Google
group
and
therefore
it's
visible
by
by
just
opening
a
web
page.
So
I'll
put
that
into
the
notes.
Cool.
A
A
Yep
I
think
that's
all
for
the
upcoming
calendar.
So
just
not,
since
we
are
canceling
next
week,
the
upcoming
Milestone
will
span
for
across
two
weeks
and
not
only
one
week.
A
However,
I
challenge
you
in
time
of
project
management
to
only
keep
that
Milestone
as
if
it
was
spending
only
one
week,
because
most
of
the
team
will
be
traveling
disrupting
the
amount
of
time
we
can
spend
on
running
tasks
and
I.
Don't
want
to
overload
the
poor
Stephen
next
week,
who
is
not
going
to
the
devops
world
because
it
will
have
to
under
the
infrastructure
alone.
So
please,
folks,
let's
consider
these
two
expand
as
if
it
was
only
one.
Thank
you.
A
Okay,
so
if
it's
okay
for
you
I
propose
that
we
get
started
on
what
has
been
done
so
welcome
Kevin
I'm,
taking
the
the
issues
as
they
are
on
the
notes
there,
the
the
Sorting
may
be
different
on
what
you
see
on
my
right
screen,
so
I'm,
taking
on
the
left,
so
welcome
Kevin
to
the
copy
editor
GitHub
organization
group,
thanks
for
merging
your
first
pull
request
on
the
jenkins.io
website,
thanks
Mark
for
mentoring
him
and
thanks
everybody
for
validating
these
permissions
yeah.
Then
thank
you
to
everyone
for
helping
me
get
to
this
point.
B
Everything
I've
had
of
this
then
and
yeah
it's
nice
to
be
part
of
the
team.
A
Cool
happy
to
have
you
next
point
was
requesting
access
to
Jenkins
project
VPN.
So
we
have
now
David
nusman,
not
nurseman,
I'm
I'm.
Sorry,
if
I'm
not
pronouncing
correctly,
please
correct
me
so
I
can
make
an
effort.
A
Cool
okay,
so
no
spam
welcome
so
he's
working
on
the
security
team
and
now
has
full
access
to
the
cell.ci
agent
King's
controller
used
by
security
team.
That
was
a
good
opportunity
to
clean
up
the
update,
CLI
process
and
update
dependencies
for
our
Docker
VPN
system.
But
the
documentation
that
Stefan
and
Airway
contributed
to
improve
in
the
past
month
is
is
working
very
well
because
it's,
the
seventh
person
that
has
access
without
an
issue.
A
Next
one
CI
Jenkins
IO
container
agent
or
missing
SSH
agent
with
the
new
all-in-one
and
also
the
second
one
new
agent
Uranus
Lee
renegas
Roots.
So
let
me
put
this
to
bug
as
a
victory,
because,
thanks
to
First
the
work
of
Stefan,
then
hervey
and
then
again
Stefan.
We
now
have
for
Linux,
literally
the
same
environment
on
every
agent
on
cigen
kinsayo,
whether
there
are
virtual
machines
or
container,
which
means
we
build
the
same
thing.
We
have
the
same
tool
with
the
same
version
on
the
same
location.
That's
the
same
definition.
A
Obviously
that
seems
like
magic
and
we
had
some
some
hiccups.
Let's
say
some
bootstrap.
Initially
there
were
some
unknown
issues
because
of
the
fact
we
are
dealing
with
containers
that
don't
have
exactly
the
same
package
sets
as
virtual
machines.
So
we
focused
on
our
usual
tool,
KDK
Maven
that
works
very
well
has
been
tested.
A
So
you
did
great
work,
but
we
were
beaten
by
the
fact
that,
for
instance,
the
default
Ubuntu
image
in
the
context
of
kubernetes
might
not
have
the
same
Char
sets
by
default
than
the
previous
images
or
the
virtual
machines
resulting
on
some
weird
character.
Unicode
encoding
are
resulting
on
the
default
user
of
the
container
being
root
for
sometimes
no,
that
was
just
minor
hiccups,
except
it
was
frustrating
for
the
developers,
so
sorry
for
the
inconvenience,
but
no
security
issue,
no
no
outage,
and
now
we
have
that
all
in
one.
A
So
next
step
will
be
windows
and
thanks
a
lot
Stefan
for
helping
a
lot
on
fixing
these
issues,
because
that
was
a
lot
of
unknown
there,
and
thanks
basil,
of
course,
for
your
celebrity
in
mentioning
and
Reporting
the
issues
and
confirming
it
was
fixed
on
your
site
as
well.
Nice
teamwork,
folks,
I'm,
really
happy
for
that
outcome.
You.
A
Absolutely
I
think
there's
really
a
new
issue
but
good
point.
The
proposal
that
Stefan
is
currently
working
on
is
to
improve
the
we
have
a
job
on
cig
in
sayu
that
Mark,
initially
created
I,
think
or
Taylor
robot
that
run
regularly
a
Nils
check
and
acceptance
ills
check.
He
tried
to
spawn
some
different
agents
based
on
the
labels
that
we
provide
to
the
Developers.
A
So
the
goal
is
to
improve
what
is
tested
not
only
with
the
ability
to
spawn
these
agents,
but
also
some,
let's
say
context
of
this
agent
is
the
default
user.
Still
Jenkins,
for
instance,
could
be
one
that
Jenkins
cannot
run
a
pseudo
command
that,
and
there
is
a
span
of
element
that
we
want
to
be
tested
that
could
be
tested
easily
in
in
that
job.
So
that
will
be
the
outcome,
the
free
elements
that
has
beaten
us
on
the
deployment
of
all
in
one
container.
A
A
Add
user
to
keep
our
secret
manager
plugin
developer
team,
so
I
think
team
yakumba
took
care
of
that.
That
was
a
let's
say:
usual
repository
permission
for
contributor
of
prekins,
not
really
infra,
thanks
Tim
for
that
did.
I
forgot
some
tasks
that
we
definitively
closed.
A
A
Relying
repo
Jenkins
CI
org
mission
that
one
we
will
discuss
that
on
the
contributor
submits
the
statues
is
I've
started
the
draft
gep
Jenkins
and
unsol
proposal
announcement
proposal.
The
goal
is
to
define
the
strategy
we
want
to
adopt
in
order
to
bring
the
bandwidth
usage
of
repo
Jenkins
CI
under
10
terabytes.
So
g-frog
continue
to
sponsor
us,
so
the
project
is
kept
sustainable.
A
The
next
step
is
today:
I
have
to
send
an
email
to
the
developer
mailing
list
to
Point
DC
demand
and
this
issue
and
start
the
discussion.
The
peak
of
the
discussion
should
happen
during
the
contributor
Summit
in
Orlando
next
week.
The
goal
is
to
uncompare
the
pro
and
con
solution
gather
the
opinions
of
every
major
contributor
involved
in
that,
especially
the
one
with
Legacy
knowledge,
and
then
we
will
have
to
take
a
decision.
A
A
B
A
Oh,
we
do
okay,
yep,
so
can
I.
Let
you
just
explain
every
while
I
should.
C
A
Exactly
that's
the
goal
to
differentiate
from
issues
that
are
rotting
on
the
issues,
lists
that
are
still
in
tryaging
state
or
on
dead
States.
As
soon
as
they
are
there.
We
can
scan
these
regularly
and
ping
or
close
the
issues
or
ask
people
to
act
on
this.
So
that's
a
way
for
us
to
limit
the
amount
of
routing
issue.
If.
B
C
Issue
I
think
we
don't
have
any
to
put
it
in
any
Milestone,
just
close
that
it's
not
planned.
Okay,
thank
you.
A
Absolutely
thanks
a
lot
everybody
for
that.
So
if
it's
okay,
if
it
meets
I'm
moving
the
current
Milestone
to
the
node,
the
recollection
number,
because,
as
you
confirm
Mark,
it's
a
really
easy
discussion
so
important
to
have
it
on
help
desk,
it's
a
centralized
place
but
no
actionable
for
us.
No
action
from
the
team
looks
good.
A
Okay,
next
topic
mirror
stat
reports
wrong
results
so
that
one
is
still
a
straight
edge,
I've
added
it
to
the
current
milestone.
So
the
I'm
not
sure
this
is
still
a
legit
issue
in
the
sense
that
the
mirror
stats
shows
the
mirror
stats.
I'm
asking
the
question
loudly
because
the
file
mentioned
by
Alex
is
served
by
multiple
repositories,
so
there
is
no
issues
for
the
mirroring
service.
A
The
thing
is
that
this
mirror
were
used,
so
they
are
on
the
history,
so
I'm
not
sure
of
the
actionable.
Should
we
spend
some
time
scrapping
the
current
configuration
and
see
if
these
mirrors
haven't
been
updated,
we
can
remove
them
or
disable
them
I'm,
not
really
sure.
My
knowledge
of
the
mirroring
system
is
not
good
enough
there,
but.
B
So
they
are,
they
are
mirroring
our
content
and
aliyun.com
is
another
mirror
that
is
online,
but
we're
not
using
them
to
offload
offload
bandwidth
demands,
and
so
both
of
those
would
benefit
and
I
believe
we
have
one
in
Singapore
as
well,
but
for
me,
I
think
those
are
all
part
of
a
whenever
when
we
get
to
it,
improve
the
mirroring
by
adding
that
Singapore
mirror,
adding
back
the
serverion
mirror
and
adding
the
alleyun
mirror
and
and
they're
all
part
of
the
same
story.
This.
B
A
For
but
the
fact
that
the
appear
here
means
they
have
been
added
in
the
database
of
our
own
service,
I'm
I,
don't
remember
exactly
if
the
number
here
is.
Is
it
a
mirror
reporting
to
get
Jenkins?
It's
okay?
Is
it
the
our
system
that
sure
that
it
is
it
because
they
are
disabled.
B
A
A
Okay,
do
you
think
it's
a
topic
that
we
should
keep
on
the
upcoming
milestone.
B
A
A
Next,
one
is
introduce
an
artifact
caching
proxy
for
CI
Jenkins
IO.
So
that's
also
top
priority
subjects.
It's
the
work
that
everybody
is
doing
on
having
caching
system
for
to
to
decrease
the
the
amount
of
thing
we
download
from
g-frog
I
reckon
you
give
us
a
quick
status.
C
Yes,
so
I
have
a
notification
proxy
running
on
Azure
on
the
the
public
carry
test.
Cluster
I've
created
a
new
digitalization
cluster
to
host
proxy
on
it
to
so.
It's
separated
from
the
cluster
dedicated
to
cider
jenkins.io
agents
as
a
security
precaution,
since
we
can't
be
sure
Origins
can
do
malicious
thing
and
I'm.
Currently
looking
at
creating
a
public
AKs
cluster
on
iws
to
ask
the
C
proxy
on
it,
Second
Use
case
I've
dedicated
a
big
cluster.
A
Cool
so
some
elements
that
might
be
outcomes
of
the
current
discussion
of
the
contributor
submits
for
that
specific
topic.
The
first
one
is
that
we
might
decide
to
mirror
everything
and
not
only
repo
Jenkins,
here.org
I.
Think
that
seem
already
a
sane
element
to
do.
What
do
you
think
since
Republic
today's
mirroring
most
of
the
usual
Maven
external
repositories?
So
that
would
be
a
centralized
point
for
us,
because
it
still
downloads
that
we
will
do
from
repo.
B
Yeah
I
think
that
makes
sense
to
me
the
anything
we
I
don't
see
how
we
would
confidently
distinguish
between
them.
I
think
it's
a
lot
simpler
to
just
say:
yes,
let's
mirror
anything
we
ask
for
that,
we
would
have
requested
from
reproducts
jenkinsci.org
and
given
how
much
it's
mirroring
I
think
that's
large
chunks
of
the
internet.
C
C
This
is
a
proxy
need,
a
require
or
a
notification.
Yeah.
A
Requiring
client-side
Authentication,
okay.
So
in
the
case,
if
we
need
to
authenticate
or
to
enable
authentication
on
repo
Jenkins,
so
the
Upstream
we
might
have
to
create
technical
accounts
on
the
ldap
and
add
these
credentials
directly
inside
the
nginx
configuration.
So
nginx
would
authenticate
with
ldap
credentials.
A
B
The
game
is
a
little
slow
on
my
Maven
cash
long
time,
since
it's
been
cleaned
I'm
only
at
33
gigabytes,
so
Airway.
If
that
helps
you
and
on
another
system
I'm
only
at
22
gigabytes,
and
there
are
two
systems
that
I
use
quite
actively.
So
in
terms
of
total
disk
space
used
by
that
cash
I'll
be
surprised
if
we
hit
a
terabyte.
C
Yeah
I
was
thinking
about
the
same.
It's
it's
what
it's
a
number
you've
quoted
recently
it
I
mean
if
I'm
correct,
thank.
A
You
yep
worst
case
is
the
world
stores
3.5
terabytes,
so.
B
A
C
B
A
We
are
validated
two
images
already
and
we
add
to
contribute
to
the
CD
plugin
process
because
we
had
to
annotate
tags
because
right
now,
until
that
change,
when
you
were
releasing
a
plugin,
it
was
publishing
to
GitHub
release,
which
was
creating
a
tag,
but
the
tag
was
Associated
to
the
date
of
the
commit
it
was
pointed
to,
which
means
it
was
on
the
day
when
you
publish
the
release
on
creating
publicly
the
new
release.
It
was
the
day
of
the
commit
when
the
commit
was
merged.
A
Consequence
is
if
Jenkins
or
any
tool
looks
at
that
date
time.
It
was
older
than
expected
by
switching
to
an
annotated
tag
with
the
so
with
the
git
command.
It's
adding
only
adding
the
dash
a
it's
a
bit
different
in
our
case
with
GitHub
actions,
but
we
were
able
to
make
it.
The
goal
is
to
add
some
content
that
will
change
the
tag
that
will
prove
the
owner
of
the
tag,
sign
the
release
and
we'll
add
a
new
date
date.
A
A
I
still
have
some
work
to
do
on
this
one
context:
the
PKG
big
machine
that
host
Update
Center,
but
also
plugins
and
updates,
and
some
formal
mirrors,
artifact
mirror.
Brain
user
is
also
used
by
every
element
that
we
use
for
releasing
raising
plugins,
releasing
Co
using
subproject
and
synchronizing
everything
so
I'm
right
now,
working
on
creating
a
technical
user
dedicated
for
that
which
role
will
be
then
to
be
the
main
user
honing.
A
So
that
will
be
a
step-by-step
process,
because
the
risk
is
breaking
almost
every
release,
things
that
we
have.
So,
let's
not
go
too
fast
on
this
one
right
now:
I'm
testing
it
locally
and
I
will
try
your
green
blue
deployment.
First,
new
user
will
switch
as
much
as
possible
and
we
correct
issue
when
they
occur,
and
then
we
can
start
removing
the
robot
and
user
and
fix
the
issue
that
we'll
create
still
context
a
bit
more
context.
That
machine
hasn't
been
automatically
managed
or
documented
during
the
past
four
or
five
years.
A
A
Next
topic
we
have,
we
have
we
have
Missing
data
dog
Matrix
for
AKs
cluster.
We
don't
understand
that
one.
It's
not
major,
so
I
will
clear
Milestone.
Unless
someone
want
to
work
on
this
one,
because
we
have
a
good
set
of
metrics
on
both
graphene
and
data
docs.
So
no
blockers
there,
it's
really
minor
inconvenience.
A
C
C
You
and
as
I've
finished
I
think
or
at
least
the
first
session.
So
now
we
have
to
create
a
basically
SQL
database
in
Azure,
with
germa
from
Repository
and
the
place.
A
Okay,
otherwise,
currently
in
holidays,
I,
don't
remember
with
taking
care
of
that.
But
the
idea
is
to
see
if
we
can
work
on
this
before
taking
the
plane
this
weekend,
because
that
will
be
nice
at
the
devops
were
to
show
a
first
initial
version
of
the
application.
C
They
have
an
issue
in
the
under
Cafe.
The
earlier
isn't:
okay,
we
can
discuss
this
later,
but
yeah.
We
can
get
our
first
session
running.
B
A
May
I
ask
you
Stefan
to
take
the
lead
on
the
database
part
of
this
one,
or
do
you
feel
to
take
Take
the
Lead,
so
the
goal
will
be
to
add
a
new
database
and
the
new
user
like
we
did
for
updates
and
usage
it's
terraform
manage
so
then
air
vehicle
and
I
could
take
over
on
the
M
chart.
Installation.
C
C
A
What
do
we
have
next
publish
pipeline
Step,
Dogs
generator
and
back-end
extension
indexer
I
feel
like
I
will
want
to
start
rocking
on
this
one
tomorrow,
but
to
not
too
much
so
I
propose
we
clear
the
milestone
for
this
one.
The
thing
is
that
one
is
required
to
build
the
Chinese
Jenkins
IU
website,
which
hasn't
been
updated
since
beginning
of
the
month.
That's
why
it's
slightly
important
if
it's
okay
for
you
I'm,
adding
it
to
the
two
weeks,
Milestone
I
will
try.
A
A
Now
we
have
the
all-in-one
great
jobs
that
we've
mentioned
earlier.
So
the
next
step
for
this
one
is
being
able
to
build
Windows
container
with
speaker.
So
there
is
a
currently
working
progress,
pull
requests.
Anyone
who
want
to
try
can
is
Power
share
low-level
things.
It's
just
calling
the
correct
commercial
version
on
the
container,
but
almost
there
so
I'm
gonna
remove
the
milestone
for
this
one
and
move
it
in
Nefra
team
sync.
Next,
because
it
will
be
important.
But
after
the
devops
world.
A
C
Yes,
but
for
now
it's
on
a
terrible
basis.
We
have
to
update
the.
A
So
I
think
we
have
an
issue
yeah
organization
scanning
weep
on
and
short,
so
that's
the
M
chart
that
transform
yaml
definition
into
groovy
job
DSL
with
our
Default
job
settings
on
infrasti.
So
we
need
to
implement
the
job
of
kind
GitHub
organization.
A
So
then
we
only
have
to
put
a
Jenkins
underscore
update
Jenkins
file
underscore
update
pipeline
that
will
be
taken
for
only
the
update
cliche.
We
also
have
a
slightly
minor
bug.
Is
that
since
we
have
two
multiband
jobs
pointing
to
the
same
repo,
we
have
some
of
the
GitHub
check
by
default
that
have
the
same
ID,
so
sometimes
it
will
direct
one
or
to
the
other
generally
to
the
last
job
that
finished
the
check.
A
A
Okay,
so
I'm
I
propose
to
remove
the
Milestone
and
put
it
back
to
the
infra
team
next
meaning
we
will
have
to
walk
later
after
the
devops
work.
A
B
A
I,
forget
it
sorry
Stefan.
Can
you
give
us
a
status
on
this
one?
Almost
there
missing
the
the
windows
part
for
it,
I.
C
A
You
explain
that
so
the
goal
is
to
provide
to
the
end
users
a
dashboard
with
metrics
about
the
agent,
so
if
they
have
a
build
of
their
plugins
or
Coral
contribution
and
cigo,
they
have
free
access
to
the
machine
metrics
to
correlate
with
what
was.
Did
it
use
that
amount
of
memory?
Did
it
crash
because
of
of
om
Etc?
So
we
have
to
give
them
a
dashboard
foreign.
A
Yes,
absolutely
so.
The
first
step
is
to
have
a
dashboard
that
will
be
private
by
default
and
add
the
correct
filters,
and
once
we
validate
as
a
team,
the
dashboard,
then
we
can
open
it
to
developer
and
communicate
to
the
mailing
lists.
So
developer
could
use
that
additional
tool
for
to
observe
the
state
of
the
agents
in
the
Pipelines.
B
A
Then
public
thing
that
was
in
the
initial
definition
that
I
might
have
yes
make
the
datadog
data
available
for
developers,
so
there
is
no
implementation
path
there.
So
the
proposal
is
a
dashboard
because
we
use
dashboard
for
statues,
Jenkins
IU
with
Olivier
last
year,
that
was
working
pretty
well
and
so
Windows
VMS
so
great
job,
because
it
was
a
lot,
a
lot
of
lot
of
tiny,
minor
things
that
took
a
lot
of
time,
so
great
job
Stefan.
Thanks
for
that,
thank
you.
A
A
A
A
A
A
I
saw
that
has
been
discussed
as
a
topic
on
this
week,
contributor
board.
Is
it
a
topic
that
we
should
discuss
during
the
contributor
submit?
That
will
be
a
good
way
to
just
pave
the
way,
so
that
means
I
will
have
to
ask
Olivia
sometimes
this
week,
if
he
can
give
me
some
some
notes
or
tips
on
the
path
in
order
to
have
this,
does
it
looks
good?
We.
B
B
Maybe
it's
good
for
you
and
me
to
sit
down
together
and
look
at
at
what
the
parts
and
pieces
are
that
are.
Are
there
there's
announcement
Etc
and
we
may
be
able
to
get
those
out
even
before
contributor
Summit,
so
that
at
the
contributor
summit,
we're
just
reinforcing.
A
So
we
need
to
start
as
soon
as
possible
the
process-
okay,
major
topic
during
the
country
as
well-
well.