►
From YouTube: 2022 10 04 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
Can
you
still
hear
me?
Yes,
okay,
okay,
everyone
welcome
to
the
Jenkins
weekly
infrastructure
meeting
I'm,
currently
trying
to
open
the
correct
Windows.
On
my
on
my
machine.
We
are
the
fourth
of
October
2022.
Today
we
have
Mark
Wade
Stefan
Merle,
Daniel,
Beck,
Ervin,
Kevin,
Martinson,
I,
dementia,
Porter;
okay,
the
nuts
are
being
started.
A
B
A
Announcements,
so
the
devops
word
and
the
contributor
submit
did
not
happen
because
Yuri
can
try
to
go
to
that
conference,
so
yeah
a
bit
that
no
one
who
has
hurt
and
everyone
is
safe.
So
that's
the
good
news,
which
means
that
we
have
a
few
tasks
that
had
been
delayed,
especially
discussing
and
walking
on
the
election
process
on
the
artifactory
system,
even
though
they
did
quite
a
great
job
on
some
of
these
areas
and
the
Twitter
account
recovery,
because
kosuke
never
fly
to
the
conference.
A
Another
announcement,
I
rotated,
all
my
keys,
but
I
mentioned
it
now.
I
had
a
security
shown
my
auto
room,
so
my
laptop
was
indulged
my
security
key
well
with
me,
so
it
it
was
missing.
A
second
factor.
I
checked
the
boots.
It
was
shut
down
and
no
one
rebooted.
It
I
saw
no
access
on
either
the
Gita
blogs
in
a
commit
and
push
even
read.
A
So
now,
if
you
think
about
something,
I
should
have
rotated,
don't
hesitate
because,
with
the
stress
of
the
travel
losing
my
things
and
being
a
bit
ill,
I
might
have
forgotten
something
so
I
used,
my
I
get
the
cheat
sheet
for
such
events,
but
still,
if
you
think
about
something,
not
hesitate.
B
So
I'm
on
the
devops
world
topic,
I'm
I've
started
a
think
document
about
how
we
approach
the
contributor.
Summit
I
haven't
shared
it
with
anybody.
Yet
I
it's
going
to
have
to
be
online
I
think
we
need
it,
but
I
don't
think
we
should
attempt
an
all-day
event.
Online
things
tend
to
work
better
if
we
do
one
or
two
hour
segments.
I'll
start
that
document
share
it
around
and
invite
people
to
comment
and
then
I'll
share
it
more
widely
in
the
community.
Once
I've
once
I've
gotten
alignment
with
a
relatively
smaller
group
of
people.
B
B
A
A
A
We
think
because
what
issues
did
we
add
during
the
last
security
issues
for
the
LTS,
where
there's
some
yeah?
That
will
be
worth
it
to
double
check
after
the
meeting?
If
there
are
things
to
be
backboarded,
because
last
time
we
had
issues,
at
least
on
the
docker
images,
minor
issues
not
blocking
the
release
process,
but
still
annoying
for
the
end
users.
A
We
need
to
just
check
because
I
remember,
some
things
were
to
be
discussed.
I
think
it's
related
to
the
judica
AIDS
being
overridden.
B
Okay,
so
so
that
sounds
like
that
should
probably
be
part
of
our
weekly
checklist
for
today
that
we
we
look
into
those
things.
Yes,
maybe
you
can
send
them
to
me
or
or
drop
me
suggestions.
I
know
that
the
LTS
packaging
was
being
reviewed
carefully
by
so
Chris
Stern.
The
release
lead
proposed
a
pull
request.
Alex
brandes
looked
at
it
and
bustle
Crow
looked
at
it,
so
I
think
we're
I
think
we're
in
place
there.
A
But
there
are
things
that
cannot
be
checked
during
the
weekly,
especially
the
missing
backboards
from
the
master
Branch
to
the
stable,
Branch.
Okay.
A
If
we
have
a
patch
change
or
something
last
time,
I
remember
the
issue
was
that
we
accidentally,
we
had
a
more
recent
version,
but
that
opened
the
C
group
version
to
support
for
continue
image,
but
that
created
bugs
that
we
were
lucky
to
have
a
Bazil
and
Jesse
at
least
we'll
cook
the
issue
quite
early.
So
they
were
able
to
push
odd
fixes
on
on
the
plugins
impacted
plugins
with
that
version,
but
that
might
be
one
of
the
impacts.
We
need
to
be
careful
on
that.
A
Okay,
just
a
word
on
unless
you
have
something
else
to
add
on
the
announcement
and
upcoming
okay,
so
word
about
the
tests
that
were
done
or
closed.
Last
week
we
had
a
few
issues
related
to
let's
say
a
repository
permission
updater,
which
weren't
really
issues
so
I
saw
that
team
open.
He
had
an
issue
with
expired
credential,
which
is
word,
but
the
the
really
the
repository
permission
of
data.
A
We
checked
it
at
least
once
a
day
was
suffering
no
issue
no
failed
build,
so
it
was
working
as
expected
and
it's
monitored.
So
I,
don't
remember
exactly
what
was
the
root
issue
that
team
detected.
So
he
closed
it.
A
Okay,
so
he
had
a
failure
in
the
upload
to
the
repo
on
his
plugin,
and
so
that's
why
the
maven
reports-
I,
don't
know
you
are.
You
are
not
allowed
to
push
the
release
because
it
was
partially
released.
Release
are
not
important
in
with
that
setup,
so
we
had
to
increment
the
number
and
do
a
new
release
so
no
issue.
In
our
case
this
time
some
login
resets
some
some
people
answer
some,
not
thanks
very
on
the
mark
for
taking
care
of
that
same
for
the
multiple
commit
permission.
A
A
Let
me
try
to
remember
I,
don't
know
a
great
work,
Airway
and
Adrian
the
old
Lupine
ill
scoring,
which
is
now
deployed
in
production
ready
to
roll.
So
now
it's
being
updated
constantly.
A
Acceptance
test
hardness-
it
was
already
done
before
the
devops
world
weeks
ago,
but
it
has
been
confirmed
that
everything
is
set
up
and
went
because
they
published
a
new
tag
and
they
made
was
pushed
and
I
know
that
Alex
brandes
was
annoyed
by
the
failing
linting
of
the
docker
file
when
he
tried
to
change
the
operating
system
of
that
image,
which
shows
that
it's
working,
because
that's
a
nice
negative
test,
he
was
breaking
things
and
it
was
blocking
his
pull
request.
A
So
work
very
well
thanks
team
for
all
the
archiving
and
finally,
core
release
staging
not
working
anymore.
Yes,
so
Daniel
I'm,
not
sure.
Yes,
are
you,
okay,
with
basil
analysis
about
the
fact
that,
with
the
old
Maven
plugin
changes,
not
the
one
I
propose,
but
all
the
other
that
you
and
basil
at
least
worked
on.
Now
the
staging
should
looks
good
right
or
it
should
be
solved.
I,
don't
know
if
you
were
oh,
we
could
test
it
in
real
life.
C
I
think
his
analysis
makes
sense.
I
have
come
to
the
same
conclusion
when
I
read
the
log
and
which
commands
we're
using
that
we're
always
staging
and
always
staging
to
a
custom
report.
It's
just
that.
Sometimes
the
custom
repo
is
also
the
default
repo
same
URL
and
so
bazel
pointing
out
it
access
using
custom
using
alternate
deployment.
Repository
is
what
con,
what
I
think
we
wanted
to
see.
So
this
seems
resolved
cool.
A
C
To
another
issue
that
I
just
saw,
the
anti-spam
system
was
triggered
the
first
done
entry,
so
the
response
to
reporter
got
was
that
there
is
no
user
registered
with
that
email,
but
the
anti-spam
system
would
prevent
user
registration.
So,
let's
kind
of
expected
no.
D
Yes,
yes,
I
miss
my
my
question.
Wasn't
really.
As
you
said,
yes
existed,
I
checked
the
Blacklist
in
the
app
and
I
didn't
see
any
relationships
between
this
person,
name
or
surname
on
the
domain
with
The
Blacklist.
So
I
don't
see
immediately
why
it
has
been
triggered.
C
A
Yes,
it
was
deployed
I,
don't
remember
something
to
be
checked.
Are
they
do
you
mind
trying
to
check
on
the
logs
I?
Don't
I
don't
know
by
like.
C
This,
when
someone
hits
the
spam
check,
an
email
is
sent
to
a
private
mailing
list.
I
think
it's
called
account
admin
or
something
yeah
about.
D
C
So
I
mean
as
long
as
it's
a
private
list
I,
don't
particularly
care
a
thing
so
correction.
C
This
is
a
very
high
volume
list,
so
I
would
suggest
to
not
send
the
emails
to
a
regular
list
like
this
is
just
an
archive
that
you
occasionally
need
to
search
so
I
would
leave
it
as
a
separate
list
and
you
just
never
get
emails
for
it
in
your
subscription
settings.
You
say
you
don't
want
emails
and
whenever
someone
hits
the
help
desk,
you
just
browse
their
in
the
interface
or
something
that
would
be
my
suggestion.
C
We
can
probably
just
clear
out
the
list
of
IP
addresses.
I,
don't
know
that
might
be
something
to
check.
You
know,
spend
half
an
hour
or
so
to
look
at
recent
blocked
account
signups
whether
the
IP
block
list
is
doing
anything
that
looks
useful
because
we
have
so
many
IP
addresses,
blocked
and.
D
D
I
know
this
is
the
link
I
put
in
the
chat
allows
to
have
its
coding
an
open
source
collaborative
Blacklist,
I.
C
I
mean
sorry:
I
was
busy
looking
at
the
IP
address,
so
we're
we're
blocking
an
entire
slav
16
here.
So,
okay,
that's
that's
bound
to
it,
some
folks
that
are
innocent
regarding
any
other
Integrations.
C
Is
it
worth
spending
time
on
the
account
app?
So
what's
what's
the
situation
with
the
others.
D
We
didn't
progress
on
Kick,
look
or
anything
since
far
long
time.
The.
D
A
Is
that
we
need,
we
are
constrained
by
an
infrastructure.
Network
issue
is
that
that
application
should
run
on
a
private
Network
which
is
not
today.
So
that's
why
we
are
not
moving
it.
Key
Cloud
was
going
on
that
direction,
but
we
have
infrastructure
issue
and
then
it
requires
time
and
right
now
our
time
has
been
hit
on
by
the
by
G5
stuff.
C
Makes
sense,
yeah
so
I
think
in
the
short
term,
we
can
probably
do
without
the
block
list
until
we
see
actual
spammer
activity
again.
Some
of
the
block
list
entries
have
explanations
like
comments
pointing
to
IP
scans
that
look
like
a
spammer
but
I,
don't
know
how
useful
they
are
like
five
to
ten
years
later,.
D
A
A
So
first
one
is
about
Jenkins
release
Twitter
account,
so
we
were
planning
to
ask
kosuke
to
do
a
two
or
three
person
key
rotation,
so
we
could
access
the
dlver
account.
We
currently
have
access
to
the
Twitter
account.
The
question
was
that
we
need
dlverter
account
to
see
why
the
automation
is
failing
since
weeks.
A
That's
the
status,
RV
came
with
a
proposal
that
was,
let's
remove
the
lvr
token
and
integration,
and
we
can
rebuild
a
new
automation.
As
a
reminder,
the
goal
of
that
Twitter
account
is
to
is
only
to
tweet
about
new
plugin
updates,
where
the
source
of
Truth
is
the
RSS
feed
from
Channel
Kentucky.
A
D
Also,
the
Twitter
together
action
has
significantly
been
updated.
This
last
time,
and
now
it
seems
now
really
compelling
I.
Think
automation
for
this
account
and
eventually
the
Jenkins
official
account
could
be
really
great.
You
can
check
your
tweets.
You
can
do
pearls,
you
can
add
media,
you
can
do
a
lot
of
things
and
it
will
allow
to
have
a
review
on
a
repository
with
a
different
team.
Reviewing
it
and
validity
meet
and
figuring
it
for
70
time
or
anything
so
yeah.
D
That
could
be
a
good
entry
point
to
to
see
how
it
works
and.
A
D
D
A
A
Next
topic
is
still
for
your
way:
statues
of
the
artifact
caching
proxy
for
cig
and
kinsayu.
So.
D
D
Successfully
created
the
I
guess,
public
cluster
and
dedicated
to
for
analysis,
artifact
casing
proxy
as
soon
as
I
have
some
I'm
currently
working
on
the
network
load,
balancing
integration
and
as
soon
as
it's
working
I'll
be
able
to
to
create
separate
requests
and
see.
It
doesn't
also
plugins
where
we
will
test
this
functionality
with
all
provider
available
on
Azure
digitalization
on
AWS.
A
Okay,
so
as
I
remember
there
for
everyone,
one
of
the
reason
why,
while
it's
taking
time
it's
because
we're
hosting
it
on
on
kubernetes
clusters,
but
for
digital
Lucian
and
Amazon
eks,
we
have
that
issue.
That's
the
freight
model
of
the
container
region
from
cidenkins
IU
are
expected
to
run
on
cluster
kubernetes
cluster,
which
is
only
targeted
at
doing
that.
So
adding
a
service
with
load
balancer
exposed
publicly
is
not
part
of
the
equation.
That's
why
we
have
to
create
separated
cluster.
A
The
over
red
course
in
term
of
infrastructure
is
low
because
we
don't
pay
a
lot
for
another
cluster,
but
the
issue
is
that
we
need
this
clustering,
the
same
network
area
but
in
the
same
network
region,
but
not
the
same
networks,
so
that
took
us
a
bit
of
time
to
create
a
new
infrastructure.
The
good
thing
is
that
now
we
are
able
to
manage
way
more
clusters,
which
is
a
good
thing
in
terms
of
reliability
and
validating
our
processes.
A
Next
topic
can
ask
any
questions
so
publish
pipeline
Step,
Dogs
generator
and
backend
extension
indexer.
So
these
two
see
these
two
repositories
generate
static
files
that
are
then
used
for
generating
the
jenkins.io
website.
The
issue
is
that
these
files
are
generated
inside
cig
and
Sayo
in
the
form
of
when
the
build
is
on
the
main
branch.
If
it's
success,
then
it
archives,
the
artifact
and
since
its
public
access
files,
then
the
generator
for
Jenkins
IO
downloads,
this
file
from
CI
Jenkins.
A
So
the
goal
of
that
issue
is
to
ensure
that
these
things
are
built
somewhere
else
and
pushed
on
public
reports
check
into
your
websites,
alongside
with
all
the
other
reports,
so
we
started
working
on
migrating.
These
jobs
inside
the
infra.ci,
the
private
controller,
enabled,
with
the
build
log
on
the
GitHub
access,
so
the
build
log
and
not
the
deployment
log,
but
the
build
log
is
available
to
contributors.
A
And
now
it's
a
matter
of
ensuring
that
we
have
the
same
feature
set
between
cig
and
kinsayon
in
Russia.
That's
a
problem
we
never
had
until
today,
but
we
have
it
now.
The
problem
was
between
cig
and
kinsayu
and
release
untrusted.
Until
today
reason
is,
we
need
the
same
tools
with
the
same
name
and
the
same
inside
Jenkins
and
the
same
label
also,
so
it's
not
complicated
it's
just.
A
We
have
to
carefully
review
and
it's
a
back
and
forth
so
trying
the
the
pull
requests,
but
almost
there,
and
once
it's
done,
the
reports
will
be
published,
so
we
will
be
able
to
open
a
pull
request
to
Jenkins.
So,
instead
of
downloading
the
static
file
from
cig,
it
will
download
them
from
the
public
website
reports.
Jenkins.
A
A
A
A
The
main
goal
is
to
ensure
that
we
don't
have
any
leftover
from
me
or
mine,
but
the
investigation
showed
that
that
user
was
manually
managed
on
the
virtual
machine
for
for
almost
five
years,
so
there
were
some
hidden
Chrome
tab
which
are
quite
important
because
they
run
every
hour
to
synchronize
all
the
latest
plugin
updates
to
the
mirrors,
which
can
be
quite
useful
right.
So
the
goal
is
to
create
a
separated
new
account
with
a
dedicated
name,
which
is
not
mirror
brain
and
try
to
put
everywhere.
A
So
the
goal
will
be
first
step,
create
that
account,
and
then
we
will
start
to
moving
the
permissions
scripts
and
tasks
to
that
new
account
and
see
if
it
breaks.
So
the
goal
is
to
have
at
least
one
change
per
day
when
it
will
be
ready
and
in
any
case
we
can
roll
back
to
the
current
mirror
mine
and
then,
after
one
full
week
of
this,
taking
care
of
synchronizing
everything
we
can
delete
safely.
A
A
So
that
means
the
new
machine
in
a
record
will
be
responsible
for
every
hour
or
when
it's
asked
remotely
to
synchronize
the
change
to
the
host
USL
mirrors
to
the
gadget
inside
your
mirror
reference
and
cash,
so
that
part
will
move
away
from
AWS
as
well,
which
means
in
terms
of
bandwidth.
We
won't
have
download
public
bandwidth.
That
cost
us
a
lot,
but
we
might
have
some
outbound
bandwidth
from
The
Trusted
CI
agent,
that
generates
the
new
plugin
updates
to
that
machine.
A
That
bandwidth
wasn't
existing,
or
at
least
not
costing
us
a
lot
because
it
was
cross
regions
which
won't
be
the
case
anymore.
However,
we
were
already
pushing
to
a
cslr
to
Azure,
so
the
outbound
won't
change
a
lot,
but
keep
in
mind
that
this
this
might
create
some
Mayhem.
So
I
will
try
to
be
careful
and
ask
at
least
someone
else
on
each
time
to
wig
a
bit
carefully.
I
won't
try
to
push
things
too
quickly.
There.
A
The
goal
was
to
work
on
it
during
the
community
Summit
last
week,
which
did
not
happen
so
I
need
some
help
for
reviewing
that
end
of
week,
but
my
plan
is
I've,
put
the
proposal
which
will
be
enabling
authentication
only
on
the
mirrors
on
the
repo
Jenkins
Maven
and
try
keeping
public
the
rest
that
might
have
some
impact,
so
the
community
and
contributor
must
be
asked
for
advices
there,
because
we
there
are
clearly
some
elements
that
will
be
impacted
either
the
Palm
domain
build
pump,
or
at
least
the
way
we're
under
documentation
for
developers
if
they
need
to
be
authenticated.
A
The
goal
is
to
follow
up
the
assumption
that
we
don't
cross
the
g-frog
download
limits
only
with
the
Jenkins
artifact
themselves,
but,
as
they
told
us
most,
probably
that's
the
free
mirror
of
most
Maven
repository
for
free
for
everyone
on
the
internet.
That
will
cause
some
downloads,
so
the
goal
here
will
be
avoid
making
mandatory
authentication,
so
we
won't
be
overwhelmed
by
the
amount
of
companies
crying
because
now
their
mirror
of
chenkins
repository
need
an
account
and
it's
complicated
and
stuff,
while
in
fact
we
only
target
the
developers.
A
If
you
are
Developer
there
should
be
no
issue
for
you
to
encode
your
drinking
Zelda
password
on
your
Maven
setup.
So
you
can
use
the
mirrors
that
we
provide
or
cig
inside
you,
of
course,
with
the
work
that
Harvey
is
doing.
So
that's
the
the
Earth
of
The
Proposal.
Now,
let's
see
we
need
advice,
a
lot
of
opinion
and
go
to
a
consensus
on
that
part.
B
So
so
Damian
I'm
not
sure
how
to
configure
my
or
can
I
get
some
coaching,
not
here
in
the
meeting,
but
can
I
get
some
coaching
on
how
to
configure
my
settings
on
XML
I
certainly
have
credentials
that
I
use
to
push
are
those
same
credentials.
Then
usable
when
I,
when
I
pull
in
this
new
world
of
authenticated
access.
A
Yes,
the
credential
that
you
define
on
your
own
M2
settings
XML.
They
are
scapped
by
using
the
repository
ID.
So
if
we
have
an
exhaustive
list
that
come
from
Mostly
from
the
pump
around
on
Jenkins
that
Define
today,
the
Republican
CI
public,
which
has
an
ID-
and
there
is
a
second
one
for
incremental.
A
So
it's
like
I
think
Jenkins,
public
and
incremental
are
the
IDS
inside
Maven
setup.
So
once
you
know
this
ID
that
doesn't
change.
Often
you
can
set
okay,
that
couple
of
encrypted
credentials
for
the
repository
with
ID
Jenkins
public.
That
one
is
for
whatever
my
company,
private,
whatever
my
personal,
private
and
then
Maven
links
them
by
ID.
So
you
can
have
multiple,
that's
the
idea,
so
that
will
work
if
you
use
the
correct
snippet.
D
And
that's
that's
linked
with
the
other
one
down
and
I'm
working
on
the
Windows
part
of
them.
I
managed
to
deal
with
the
Azure
ones
with
the
cloud
in
it,
injection
for
the
AP
API
key
and
now
I'm
working
on
the
ec2
version
of
it
and,
on
the
same
time,
I'm
working
on
improving
the
the
checks
on
the
availability
check
that
we
had
before
and
to
have
more
to
improve
all
those
checks
for
the
Linux
parts
and
for
the
windows
ones.
D
A
D
I
will
need
your
help.
I
I
did
manage
one
thing,
but
I
I
cannot
mix
within
the
same
dashboard.
A
B
A
A
Yeah,
most
probably
they
messed
up
the
encryption
of
the
password
on
Maven.
That's
the
usual.
A
Is
there
except
telling
them
to
use
CD?
Is
there
something
else
that
we
could
do.
A
C
If
you
check
within
five
minutes
of
the
error
occurring
because
yeah
correct
jfrog
uses
extremely
aggressive
log
rotation-
and
it's
also
stupid
log
rotation,
because
every
few
minutes
they
truncate
the
file
to
nothing
so
there's,
basically
a
next
to
zero
percent
chance
that
you
see
the
log
messages
from
the
two
seconds
before
they
do.
That
I
would
emphasize
Marx
response,
because
I
think
there
are
ways
to
encrypt
Maven
passwords
that
are
very
different
from
what
artifactory
does,
which
is
why
we
have
very
detailed
instructions.
B
Yeah
Daniel
to
support
what
Daniel
said.
That's
been
a
consistent
pattern
that
we've
repeatedly
had
people
who
needed
to
be
reminded
these
State.
These
instructions
are
exactly
this
way
because
they're
the
ones
we
know
work
and
there
are
lots
of
other
places
where
you
can
read
about
instructions
that
ultimately
don't
work.
B
C
Right,
yeah
so,
and
the
instructions
are
weird
like
download
this
file
and
ignore
90
of
its
content.
That's
not
what
would
usually
be
on
the
success
path
of
any
same
process
but
Mark
you
commented
there.
Then
there
was
another
comment
and
it
seemed
like
the
reporter.
Just
responded
to
the
last
comment.
There
I
would
like
them
to
acknowledge
that
they
have
done
what
Mark
asked
yeah.
They,
the
reporter
just
responded
to
Damien's
comments.
C
So
I
suggest
you
ping
them
and
ask
them
to
confirm
that
they
followed
the
instructions
exactly
that
Mark
linked.
A
So
that
means
that
we
should
have
a
look
for
a
reminder.
The
configuration
of
this
job
is
not
in
France
code.
I
hope
we
will
be
able
to
do
it
one
day,
but
right
now
it's
manual
manually
managed
still
on
cig
and
Sayo,
so
the
goal
will
be
to
look
I
fear
that
infra
being
a
GitHub
repository
operation
scanning
that
we
might
need
to
move
stories
away
from
that
triple.
A
B
So
Damian,
if
you're,
okay
with
this
one
I'm,
so
what
you,
what
I
heard
you
just
say,
is
I
could
test
this
by
configuring,
ci.jenkins.io
interactively
and
I'm,
actually
reasonably
good
at
that
I'm
happy
to
do
that.
So
how
about,
if
I
take
this
one?
Would
that
be
okay
rather
than
having
you
do
it
because
it's
this
is
not
an
automation,
one
and
and
I'll
take
it
on
because
I'm
also
interested
in
this
site
as
part
of
advocacy.
A
Okay,
may
I:
ask
you
if
Stefan
orme
is
interested
just
to
pair
for
knowledge
sharing.
That
will
be
a
great
exercise
for
one
of
them
also
or
reminder
to
see
the
manipulate
the
Jenkins
concept,
such
as
GitHub
organization
scanning,
which
might
have
impacts
on
stories.
If
you
have
to
move
it
and
that
will
show
so
since
you
are
really
experimented
with
the
UI,
that
will
help
them
to
learn
on
the
process
and.
A
Second,
one
is
a
pipeline
graph
View
and
release
cig
I.
Guess
everything
was
done
before
the
weekly
release.
So
once
the
weekly
release
is
finished,
we
will
check,
but
I
think
they
did
everything
correctly
and
we
merge
so
to
be
checked.
Stefan
can
I
ask
you
to
check
this
one
since
you
are
underlying
the
plugin
and
car
updates.
Yes,.
A
Verification
on
Twitter
I
guess
it's
not
really
infrastructure
there,
but
the
advocacy
part
of
the
board.
Even
so
it's
about
asking
Twitter
from
that
account.
So
they
are.
They
have
the
Blue
Tick
to
say:
that's
a
validated
account
by
Twitter
themselves.
A
I
have
no
idea.
What
are
the
proof
that
are
needed?
Some
person
are
validated
some
more
nodes
that
but
I'm
not
in
these
things,
but
we
don't
have
access
to
the
account.
So
not
sure
should
we
send
an
email
since.
B
I'm,
a
member
of
the
board
and
I'm
permitted
to
post
to
that
account.
Why
don't
you
assign
it
to
me
and
I
I,
don't
know
that
I'll
get
to
it,
I'm,
not
sure
we
should
put
it
in
this
upcoming
work,
but
but
I
think
it's
a
reasonable
thing
to
say:
yeah.
We
should
do
it
eventually
and
as
a
board
member
I'm,
a
good
candidate
and
since
I
have
access
to
that
account.
I'm,
probably
a
doubly
good
candidate.
A
B
So
the
only
the
only
topic
for
me
was
elections
and
that's
when
Damien,
where
I
took
an
action
item
in
board
meeting
yesterday
to
get
with
you,
since
we
missed
doing
it
at
devops,
world
I
used
the
excuse
that
hurricane
Ian
disrupted
us
and,
of
course,
Gavin
Mogan,
said
how
can
a
hurricane
interrupt
an
online
election
and
so
it's
a
we
dami
and
I
didn't
get
together.
So
you're,
okay,
I
assume
the
two
of
us
pair
up
later
and
and
do
some
prep
for
elections.
Yes,.
D
May
want
to
speak
about
the
VPN
certificate,
something
you
spoke.
This.
A
Morning,
yes,
to
wrap
it
up,
we
will
open
an
issue
on
that
Milestone.
We
have
to
regenerate
the
crl
for
the
VPN
it's
the
earlier
six
months.
The
goal
is
to
have
Stefan
making
it
on
me
in
support.
It's
well
documented.
That's
that
should
be
uneventful.
We
receive
the
notification
on
the
calendar
that
should
happen
in
three
week.
Roughly,
so
that's
the
idea.
I
missed
them.
A
So
since
we
are
out
of
time
thanks
for
the
reminder,
but
I
will
add
the
issue
on
the
current
Milestone
I
know
that
Stefan
won't
forget
about
it.