►
From YouTube: Jenkins Governance Meeting October 3, 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
So
items
I
had
on
the
agenda
news
action
items
antler
with
Basel,
leaving
that
discussion
then
upcoming
elections
and
that's
mostly
me
giving
a
status
report
and
CDF
topics
if
Oleg
joins
us
or
if
there
are
others
to
talk
there
and
then
forums
and
Community
topics
and
Gavin,
we
usually
have
you
lead
that
one
are
there
other
topics
that
need
to
go
on
the
agenda.
A
Okay,
then,
let's
go
ahead,
so
we've
got
two
open,
open,
Action
items:
oh
whoops,
let's
go
back
to
news
for
excuse
me
news.
So
next
LTS
is
coming
out
on
Wednesday
two
days
from
now:
2.361.2
relatively
smaller
set
of
changes
in
it,
as
is
Pretty
common
for
a
DOT
two
release.
Thanks
Basel
for
your
contributions.
A
There,
thanks
Kevin
as
well,
hacktoberfest
has
started
and
contributions
are
coming
in
at
a
at
a
really
quite
pleasing
Pace,
it's
good
to
see
lots
of
interaction
on
the
chat
channels,
it's
good
to
see
many
pull
requests
arriving
and
they
are
in
generally
useful
and
helpful
I've
seen
relatively
few
spammy
pull
requests.
So
it
looks
like
the
the
technique.
The
digital
oceans,
using
this
year
that
they
learned
from
last
year
to
reduce
spam
has
really
helped
a
bunch
Gavin
thanks
very
much
to
digitalocean.
A
If
there
are
any
there's
anybody
you
that
you
can
share
our
thanks
to
in
the
company,
we're
very
grateful
to
them.
Yeah
I
can
do
that,
and
next
piece
of
news
devops
world
was
postponed
thanks
to
Hurricane
Ian,
it's
it's
not
it's
not
gonna
happen
live.
It
will
be
virtual.
So
the
postponement,
their
their
plan,
is
to
create
a
virtual
conference
but
they're
trying
to
work
out
the
details.
What
it
will
mean
to
do
that
virtual
conference.
That
means
that
the
contributor
Summit
was
postponed
and
we've
got
to
have
some
more
thinking
on
that.
A
A
Done
so
one
last
item
I
have
is
that
two
weeks
from
today,
I
will
be
out
of
the
office
I'm
going
to
go.
Take
some
vacation
time
with
my
spouse
and
she
and
I
are
going
to
be
out
of
country.
I
need
a
volunteer
to
lead
the
meeting.
Gavin
you've
got
Zoom
access.
Would
you
be
willing
to
be
the
the
zoom
zoom
recording
person,
Etc
yeah.
A
Okay
action
items,
then
I've
still
got
the
action
item
to
use
community.jenkins.io
for
the
docsig.
The
doc
Sig
mailing
list
continues
to
be
almost
no
traffic.
It's
just
going
to
take
a
while.
This
certainly
won't
happen
until
November
at
the
earliest.
A
B
Yeah
I
suspect
they
don't
want
to
get
replies
because
a
lot
of
times
when
you
sign
up
for
Google
group,
if
you're
not
paying
attention,
you
have
the
don't,
send
me
things.
A
B
A
A
A
A
C
Remember
there
was
a
previous
discussion
about
this
on
the
developer
list
about
a
year
ago,
maybe
or
many
months
ago
and
I
think
the
but
I.
What
I
recall
was
that
we
wanted
to
keep
it
disabled
to
decrease
the
barrier
to
entry.
B
C
So
I've
been
investigating
this
bug
regarding
Jenkins,
not
compiling
on
Java
18
or
newer
and
I've
realized
that
this
problem
is
caused
by
our
use,
very
old
version
of
antler
dating
back
to
around
2007.,
and
this
is
still
used
for
two
features:
the
cront
tab,
parsing
and
parsing.
The
label,
expressions
for
build
agents
and,
in
particular,
this
Maven
plug-in
that
we're
using
does
not
appear
to
have
survived
the
migration
from
subversion
to
git.
C
C
It's
one
of
those
things
that
is
so
old
that
that
is
prohibitively
difficult
to
make
any
changes
to
it
at
all,
leaving
the
only
viable
path
forward
to
be
an
upgrade
to
antler
4,
which
is
the
current
version
of
antler.
That's
actively
developed
and
I've
I've
spent
some
time
on
Twitter
reading,
tweets
from
the
antler
community
and
I
identified
a
consulting
firm
and
reached
out
to
Federico.
C
Who
is
the
principal
of
this
consulting
firm
that
has
experience
performing
migrations
from
antler
2
to
antler,
4.
and
Federico
is
kind
enough
to
scope
out
the
work
confirmed
that
there's
interest
in
the
project
scoped
out
the
work
and
has
written
us
a
proposal,
including
a
very
kind
discount,
because
we
are
an
open
source
project.
And
so
my
my
goal
in
this
meeting
is
to
go
over
that
proposal.
I've
already
discussed
it
on
the
developer
mailing
list
on
the
technical
side,
and
there
wasn't
really
any
major
concerns
there
expressed.
A
A
B
No
I
mean
I.
Think
basil
pointed
out
the
fact
that
we
I
mean
it's
a
little
overkill
for
the
use,
we're
using
it
for,
but
I
think
No
One's
Gonna
ever
get
around
to
fixing
it
or
removing
it.
So
I
think
we
should
just
fix
it
and
I'm
a
big
I
think
we
should
spend
some
of
the
money
that
we
have
been
fully
hoarding
for
the
last
couple
years,
so
in
general,
I'm
in
favor
of
it
I
don't
have
any
concerns.
A
Well
and
it's
and
it
is
well
I-
can
confirm
it's
well
within
our
budget.
We've
got
over
7
000
in
the
account
currently
so
so
the
2700
Euro,
that's
proposed
will
will
readily
fit
and
I
think
I
agree
with
you
Gavin.
That
I
think
it's
much
more
practical
for
us
to
spend
these
funds
on
Experts
to
do
this
than
it
is
for
us
to
ask
somebody
to
develop
antler
4
skills
for
what
is
a
relatively
narrow
use
case.
Let's,
let's
just
get
it
done.
I
I
think
you're
right.
C
C
Like
I
mentioned
in
that
a
little
point,
you
know
it's
not
out
of
the
question
that
we
could.
We
write
this
functionality
from
scratch,
but
nobody
has
really.
You
know
volunteered
to
do
that,
and
this
does
seem
to
be
the
easiest
path
of
least
resistance,
that
I
can
identify
with
the
lowest
risk
to
causing
regressions
and
also,
you
know
the
most-
the
kind
of
the
most
straightforward
path
that
involves
the
least
amount
of
code
change
to
what
we
have
already.
So
that's.
B
B
C
Yeah
I
mean
it,
could
it
could
be
done?
You
know
from
scratch,
I
think.
For
example,
Alex
Earl
has
Rewritten
the
parser
for
token
macro
in
the
last
couple
of
months
to
be
it
from
scratch.
Parser,
rather
than
using.
C
There
was
some
framework
that
he
was
using,
that
I
think
he
got
rid
of
and
simplified
so
I
mean
things
like
that
are
not
out
of
the
question.
It's
just
that
someone
needs
to
volunteer
to
do
it
and
nobody
has,
which
is
why
I've
kind
of
gone
this
other
route
instead
of
updating
what
we
have
already.
A
C
Sure
so
so
this
code
already
has
automated
test
coverage,
so
that's
kind
of
one
of
the
main
points
in
our
favor.
You
know
this
should
not
be
a
high
risk
engagement.
C
The
the
project
builds
with
Java
11
we've
got
tests
and
that
can
be
run
in
IntelliJ
or
at
your
favorite
IDE.
So
it
should
be
pretty
straightforward
to
go
and
adjust
this
code
if
you
scroll
down
further
this
kind
of
this
document
kind
of
talks
about
the
credentials
from
this
consulting
firm
but
they've
been
very
involved
in
the
antler
project,
as
well
as
doing
these
kinds
of
migrations
and
other
types
of
programming
language
projects.
C
So
I
was
very
confident
in
reading
everything
that
I
read
from
not
only
their
own
marketing
materials,
but
in
seeing
their
engagement
on
Twitter
and
on
you
know,
other
other
resources,
like
stack
Overflow,
you
know
they're
very
active
in
the
antler
Community,
which
gave
me
a
lot
of
confidence
in
this
particular
group.
If
you
want
to
scroll
down
further
I
think
the
next
page
talks
about
the
what
we're
asking
for
specifically.
C
So
the
ask
on
our
side
was
for
instrumenta
to
prepare
a
pull
request
and
essentially
to
do
what
it
takes
to
get
that
plug
Quest
across
the
finish
line
and
I
volunteered
myself
as
the
point
person
to
work
with
them
during
that
period,
including
helping
them
with
any
development
questions
that
they
might
have,
as
well
as
doing
code
reviews
and
doing
everything.
That's
needed
from
our
side
to
Shepherd
this
change
across
the
Finish
Line.
C
So
the
way
it
works
is
that
the
grammar
files
are
kind
of
compiled
by
antler
into
some
Java
classes,
and
then
we
kind
of
extend
those
classes
in
the
Jenkins
code
base,
so
they're
going
to
be
operating
at
that
boundary
of
the
grammars
and
the
immediate
consumers
on
the
Java
side,
and
we
have
clarified
that
we
want
all
of
the
automated
tests
to
pass
for
this,
pull
request
will
be
accepted,
so
they've,
provided
here
I
think
they've
provided
a
period
of
two
months
that
they've
guaranteed
that
the
tests
will
pass.
C
So
this
is
not
the
kind
of
thing
that's
going
to
change
after
it's
integrated.
Basically,
if
it
works
on
day
one
it's
just
going
to
keep
working,
so
that's
the
offer
from
their
side.
If
we
move
on
to
the
next
slide,
this
is
going
through
the
cost,
and
you
can
see
that
oh
I
actually
put
the
wrong
number
in
the
agenda.
It's
actually
1890
Euros
I,
put
the
first
number
by
accident,
I.
C
Think
because
there's
a
30
discount
that
they've
offered
there
was
a
question
about
the
tax,
because
if
you
go
down
two
paragraphs,
they
write
that
the
client
has
to
be
a
registered
business
to
avoid
the
value-added
tax
and
then
Mark
and
I
were
not
sure
whether
we
meet
these
registration
requirements.
So
we
may
have
to
pay,
may
or
may
not
have
to
pay
the
tax,
but
that
is
really
about
it.
So
that's
the
cost
and
that's
the
tax
and
I
think
that's
all
I
have
to
present
about
this.
A
Thank
you
so
so
one
of
their
comments,
early
on
I,
think
you
you
meant
you
described
it
very
well,
they
they
say
hey,
they
will
refactor
the
grammar
and
they
will
have
to
make
some
changes
in
order,
because
antler
two
to
antler
4
is
more
than
just
a
minor
change
right,
so
they're
going
to
do
those
changes,
and
that's
part
of
this
part
of
this
bid
part
of
this
proposal
right
exactly.
Okay,
great!
Thank
you.
Any
questions
from
others.
C
Yes,
I,
the
number
I
put
in
the
agenda
is
the
wrong
number.
That's
the
post
discount
number!
If
you
look
at
my
left
side,
that
needs
to
be
corrected.
C
Oh
I
forgot
to
mention
one
more
thing
as
far
as
the
as
a
token
of
our
appreciation
for
the
discount,
we
also
offered
to
publish
a
blog
post
on
the
Jenkins
blog
that
is
technical
in
content,
so
not
not
a
marketing
blog
post
but
we're
planning
on.
Basically
writing
a
thank
you,
blog,
post
and
I
think
we've
kind
of
done
this
in
the
past.
With
other
organizations
that
offer
us
discounts,
including
digitalocean.
You
know,
we've
wrote
a
blog
post
for
them
recently.
So
that's.
D
C
Planned
as
part
of
this
and
I'll
work
with
strumenta
to
get
that
blog
post
written
and
published.
But
we
thought
that
would
be
a
nice
gesture
to
thank
them
for
offering
us
a
discount.
D
A
So
next
topic,
then,
is
a
vote
votes
on
the
proposal,
so
I'm
going
to
start
with
mine
Mark
is
plus
one
I'm
a
board
member.
Therefore,
it's
a
it's
a
binding
vote.
Gavin.
Do
you
want
to
share
your
vote?
Yeah
I'm
in
favor
of
it?
Okay?
A
So
we
we
lack
one
more
person
for
a
majority
of
the
board,
so
I
don't
have
a
vote
yet
for
Oleg.
A
vote
for
Evelina
I'll
have
to
ask
for
those
separately
and
kosuke
is
The.
Other,
Board
member,
so
I'll
I'll
I
would
propose.
We
put
this
as
tentative
I
assume
Basel
and
Kevin
you're.
Both
plus
one
can
I
confirm
that
with
the
two
of
you.
Yes,
okay,.
A
Okay,
so
what
I'll
do
is
I'll
use,
email
to
ask
for
Oleg
and
Evelina
and
kosuke
to
give
their
vote
on
it,
and
once
we
have
a
majority
I
think
we
can
proceed.
The
deadline
that
they
set
is
October
8th,
so
Mark
to
complete
the
the
requests
and
get
responses
from
at
least
one
by
October
8th.
A
So
we
can
so
we
can
proceed
so
that's
Saturday,
correct
that
is
Saturday
yeah!
That's
it's
this
week
right.
B
A
Good
question:
yes,
so
let
me
put
that
on
my
list
as
well,
so
Mark
to
well
and
and
no
matter
what
we
need
to
reach
out.
We
need
to
contact
the
Linux
Foundation
to
be
sure
they
are
able
to
process
this
payment
that
there
are
no
surprises
Etc.
So
so
that's
a
good
thing
connect
with
Linux
Foundation
to
understand.
If,
if
that
is
required
and
to
confirm
they
can
make
the
payment.
B
I'm
not
concerned
about
making
the
payment,
because
that's
all
through
done
expensify,
but
yes,
that
that
is
concerning
I
mean
not
even
concerning
I,
suspect
Linux
is
definitely
registered
business,
but.
A
Right,
it's
I
for
me,
given
how
infrequently
we
do
these
kind
of
things
I
think
it's
healthy
for
me
to
be
sure
that
I
check
with
them
to
understand
which
things
do
we
need
to
be
sure,
we've
done
in
order
for
this
to
be
smooth
and
successful.
I
don't
want
to
create
undue
burden
on
strumenta
or
on
Basel
in
dealing
with
the
financial
side
of
this.
C
C
B
Yeah
I
don't
have
any
concerns
about
for
this,
because
I
believe
they
just
submit
a
report
to
expensify
and
then
we
give
and
then
whoever
has
access,
which
is
not
me.
It's
improved
button,
so
Mark
is
probably
we're.
Definitely
old
like,
but
maybe
mark.
Okay.
C
A
That
sounds
good.
Yes,
that
does
thank
you,
basil
and
and
you're
you're,
certainly
welcome
to,
if
you
feel
you
need
to
you're,
welcome,
to
share
the
notes
and
even
a
pointer
to
the
recording
of
the
meeting
so
that
they're
confident
that
we
are
interested
if
there's
any
concern
from
them
that
we
we
very
much
want
to
want
to
engage
with
them
and
we
will
do
our
best
to
meet
their
their
October
8th
gating
date.
I
like
that.
Okay,
all
right
next
topic
was
upcoming
elections
and
I
have
to
apologize.
We've
been
disrupted
a
little
bit.
A
A
A
So
what
this
means
practically,
though,
is
we've
gotta
I
think
we
need
to
adjust
the
timeline
we're
in
October
now,
and
so
we
need
to
gather
the
candidates
in
their
statements
and
finalize
the
candidates
by
end
of
October
so
that
we
can
do
voting
in
November
foreign.
Are
you
okay
with
that?
Or
does
that
feel
too
rushed
to
you?
Do
we
need
to
ask
for
a
change
of
of
schedule?
Are
you
comfortable
that
hey?
We
can
get
the
voting
done
in
in
a
month
in
November.
B
Sorry,
honestly,
in
my
past
experience,
I
think
the
people
who
are
going
to
sign
up
are
going
to
be
people
who
sign
up
in
the
first
week
both
voting
and
candidates.
So
honest,
I,
don't
have
any
concerns
about
this
great
okay.
A
A
So
we
will
plan
to
use
the
same
process
as
last
year
and
going
forward
any
questions
about
upcoming
elections.
A
Nope
sounds
good.
Okay.
Next
was
then
CDF
topics
oops.
So
here
just
there
is
a
new
proposal
from
Damien
on
the
jfrog
topic.
They've
been
working
very
cooperatively
with
us
to
try
to
identify
ways
to
reduce
the
amount
of
data
transfer.
We're
doing,
and
what
Damian
has
proposed
is
a
Jenkins
enhancement
proposal,
draft
of
an
approach
to
to
work
on
it
and
so
I
encourage
people
to.
Please
read
his
draft.
A
A
D
Okay
well,
like
hi
Olas,
sorry
I
was
distracted
by
layoffs
in
one
company
and
yeah
forgot
about
the.
A
Meeting
thanks
for
being
here,
much
appreciated,
so
we,
if
you're,
okay
or
like
we'd
like
to
backtrack
a
little.
We
had
a
proposal
from
from
Basel
to
invest:
19
1
900
Euro
in
an
upgrade
of
our
antler
grammar
from
antler
2
to
antler
4,
using
a
Consulting
service,
strumenta
they've,
given
us
a
quote
and
buzzle
presented.
His
summary
of
it
gave
us
a
good
overview.
A
Gavin
and
I
were
both
plus
one
on
it.
If
we
would
I
was
going
to
get
your
vote
separately,
but
would
love
to
have
your
vote
now
or
if
you've
got
questions,
we'd
be
happy
to
go
over
and
try
to
address
any
questions.
You
have
well.
D
D
Need
to
go
through
the
proposal,
but
yeah
I
think
it's
a
plus
one.
Unless
there
is
something
really
bad
coming
topic
I
mean
if
there
is
no
potential
conflict
of
interest,
Etc
I
think
plus
one.
A
D
C
Yeah
thanks
Alec
and
if
there's
any
other
questions,
feel
free
to
reach
out
to
me.
A
Or
how
do
you
see
it?
I
was
assuming
we
do
it
through
LFX
I'm,
not
sure
it
would
be
mentorship,
but
I
don't
so
we
want
LFX
to
or
whoever's
whoever
manages
that
seven
thousand
dollars.
That's
in
our
budget.
We
have
them
or
in
our
account
we
have
them
pay
this
amount
to
this
to
stroment
of
this
company.
D
D
I
think
it
looks
perfectly
fine,
so
the
only
concern
is
a
taxation
Etc,
but
here
as
long
as
they
ended,
Foundation
take
care
of
it
and
perfectly
fine.
A
Great
all
right,
thank
you,
okay,
so
that
takes
care
of
my
action
item.
So
I
have
one
action
item:
to
connect
with
the
Linux
Foundation.
To
be
sure
that
we
understand,
if
the
that
we
know
how
to
pay
these
the
people
at
stromenta
and
if
any
value-added
tax
is
assessed.
There
was
a
concern
in
The
Proposal
that
we
have
to
be
a
registered
business,
and
so
we
got
to
check
his
Linux
Foundation
registered
in
the
way
that
would
satisfy
that
need
or
not.
D
Mm-Hmm
so
who
does
currently
have
access
to
the
expansify
backend?
If
I
recall
correctly,
I
asked
for
membership
all
board
members,
maybe
one
year
ago,
but
since
that
the
board
changed
and
yeah
I'm,
not
sure
whether
all
the
access
was
granted.
A
So
is
that
something
I
should
take
up
with
them.
In
my
conversations
as
well,
Oleg
is
be
sure
that
board
members
have
approval
permission.
D
So
you
can
ask
one
big
problem
for
this
system
that
it
supports
on
the
one
I
mean
from
as
far
as
LFX
concerned.
Obviously,
the
painful
of
expenditure,
because
currently
I
have
a
problem
with
Captain.
All
the
accounts
were
created
by
the
Linux
Foundation,
and
now
they
cannot
transfer
access
to
us,
got
it
yeah
for
Jenkins.
So
the
project
belongs
to
me.
I
believe
and
expensive
account.
D
I'm
looking
right
now
but
yeah,
it's
probable
that
it's
just
me.
D
Yeah
I
have
permission
so
I
approved
oneix
request
recently,
so.
A
All
right,
so
we've
got,
we've
got
a
path
forward,
very
good
anything
else.
On
the
on
the
antler
con
contract
proposal.
A
So
next
topic,
then
we
were
discussing
upcoming
elections.
Damian
and
I
have
got
more
work
to
do
there.
The
plan
is
that
we'll
announce
the
elections
in
October
gather
candidates
in
their
statements
and
finalize
them
for
November
voting,
so
that
we
can.
We
can
proceed
with
installing
the
new
officers
in
early
December
as
scheduled,
sorry
that
we
missed,
but
Damien
was
disrupting
Damien
and
I's.
Work
together
was
disrupted
thanks
to
Hurricane
Ian,
keeping
me
away
from
Florida
and
stranding
him
in
Florida.
A
All
right
next
topic,
then
CDF
topics
so
jfrog
making
progress.
Damien
has
proposed
a
Jenkins
enhancement
proposal
of
how
we
repurpose
or
redefine
the
mission
of
repo.jenkinsci.org
in
order
to
reduce
its
bandwidth
demands,
and
he
believes
that
we're
going
to
need
a
multi-step
process
and
that
each
of
the
steps
along
the
way
will
want
to
measure
the
impact
of
that
to
see
how
close
are
we
to
our
goal
of
reducing
data
transfer
from
50
terabytes
a
month
to
less
than
10
terabytes
a
month.
A
D
Let's
just
do
it
when
we
can
So
currently
yeah
this
doc
user
could
buy
trees
contribution,
so
we
are
launching
the
process
and
another
opening
reviews,
but
at
any
moment,
you're
welcome
to
join.
D
D
So
I'm,
looking
in
the
LFX
Jenkins
account
as
far
as
I
can
tell
it's
just
me:
okay
boxes,
okay,.
D
A
Thank
you,
okay,
very
good,
so
I
think
in
terms
of
that,
then
Basel
I
think
we're
ready
to
have
you.
Let
let
strumenta
know
that
it's
approved
great
thanks
for
thanks
for
bringing
the
proposal
and
please
thanks
drumenta
for
the
discount,
we're
very
grateful
for
the
30
discount
they're,
so
kindly
offering
sir
any
other
CDF
topics
Oleg
that
that
we
need
to
be
reviewing
no
okay.
The
next
topic,
then,
was
forums
and
Community
topics.
Gavin
are
there
topics
there
that
you'd
like
to
highlight.
B
Not
really
you
already
mentioned,
the
new
Jenkins
is
away
story
and
I
was
pretty
happy
with
unhappy
with
how
how
frustrating
nitpicky
the
system
was,
but
it
did
work
out
itself
out
pretty
quickly.
A
Yeah
actually
I
was
I
was
thoroughly
impressed.
I
I
will
yet
find
a
way
to
get
it.
Jim
klimov
had
asked
hey.
Could
he
get
a
T-shirt
and
I
I
have
promised
myself?
I
will
find
a
way
to
get
him
a
t-shirt.
I
don't
know
how
that
will
be,
but
we
will
find
a
way
to
get
him
a
t-shirt.
A
Jenkins
is
the
way
t-shirt.
Yeah,
it's
a
great
story.
It
is
really.
C
Interesting
Jim
has
been
very
helpful,
testing
changes
and
also
contributing
to
plugins,
including
just
a
few
that
I'm
familiar
with,
are
the
throttle,
concurrence
plug-in
and
the
lockable
resources
plug-in
and
also
I
think
the
IRC
bot
plug-in
he
is
involved
with
so
he's
been
a
great
member
for
our
community,
and
it
would
be
great
to
show
our
appreciation
to
him.
A
Wholehearted
agreement,
his
contributions
to
the
get
client
plug-in
and
and
the
technique
they're
using
are
real
positives,
so
yeah
very
grateful
to
him
all
right.
So
there
was
an
open
question
that
I
had
on.
There
was
a
question
raised
to
the
board
mailing
list.
Someone
asking
hey:
please
remove
a
reference
to
company
X
on
the
on
the
bug
tracker
when
I
look
at
the
reference,
it's
actually
pretty
trivial.
A
It's
a
host
name
is
all
that
the
reference
is,
but
what
I
wanted
was
General
guidance
on
the
technique
when
someone
asks
makes
a
request
like
this,
hey,
please
remove
this
reference.
How
do
we
handle
it?
Is
it
okay,
I
just
go
delete?
What
I
can
do
we
should
we
do
nothing
just
ignore
the
request.
What's
what's
the
guidance
in
general
I'm
not
familiar
with
the
process.
B
Personally,
on
this,
one
I
would
just
ignore
it.
It's
an
automated
request,
which
doesn't
really
have
any
real
purpose.
It's
like
don't
mention
this
hostname.
C
Well,
if
it's
this
was
from
jira,
it
was
this
from
a
jira
ticket
that
they
wanted.
The
hostname
removed.
Okay,
exactly
everyone,
everyone
who's
brought
up.
The
organization
has
edit
privileges
on
to
your
descriptions,
so
I
don't
think
that
they
need
us
to
do
this
right.
They
can
do
it
themselves
if
they
wanted
to.
C
It
seems
like
so
that
I
think
that
I
mean
if
it's
in
the
description,
I
guess
if
it's
in
a
comment,
I
think
you
can
only
edit
your
own
comments,
but
if
it's
in
an
attachment
or
an
description,
I
think
anyone
could
edit
it.
So
it
may
you
know,
may
very
well
be
a
reasonable
response
to
say
you
know
anyone
can
can
edit
this
so
just
go
and
make
the
change
yourself.
C
If
it's,
if
it's
something,
that's
in
a
comment
that
the
original
poster
cannot
log
in
again,
that
could
be
a
legitimate
reason
to
ask
an
administrator
to
edit
it.
If.
B
B
So
the
request
is
from
a
so-called
security
team
that
says
they
didn't
want
this
post
name
posted
I
mean
honestly
to
me.
That's
one
of
those
things
that
once
you
put
it
on
the
public
on
the
internet,
you
can't
really
take
it
away.
So,
yes,
someone
could
go
in
and
I
oh
I
said,
but
you're
right
that
the
accounting
question
is
no.
The
person
is
not
there
for
a
reason.
B
It's
an
old
account
or
old
email
for
old
ticket,
but
I
also
kind
of
been
like
I,
don't
even
know
who
how
many
people
have
actually
made
access
to
dear
to
go
in
and
edit
these
things.
A
Yeah
so
I
certainly
do
I'm
a
jury
administrator,
so
it
turns
out.
I
can
I
can
make
any
of
the
changes
here
that
would
like
to
be
done.
I
was
I
was
as
much
looking
for
what's
the
general
guidance.
So
in
this
case
the
request
is
hey.
Remove
references
to
this
thing.
I
could
delete
the
ticket
completely.
It's
it's
closed.
So.
A
Exactly
and
they
didn't
ask
for
a
deletion
on
the
migration
destination,
so
so
there's
a
piece
of
that
where
okay
I
could
do
I
I
could
certainly
remove
the
references.
You
know
images
that
might
have
it
in
it.
Any
of
those
things
that's
easy
to
do
and
I
can
I
will
happily
do
that
as
a
way
of
saying
hey,
we
did
it.
We
satisfied
your
request.
B
What
I
have
low
tolerance
for
automated
tooling
so
and
it's
like
the
same
thing
with
you
know:
I,
don't
know
if
you
were
in
the
docker
Channel
last
week,
when
someone
reported
there
was
an
issue
that
in
no
way
made
sense
there,
either
Windows
related
CVS
in
the
Linux
nation
in
the
Linux
Docker
image.
So
I
have
a
very
low
tolerance
to
these
automated
scanning
tools
that
don't
have
any
real
human
interaction
to
them.
So
when
someone
emails
us
and
says,
hey
our
tool
detected,
this
thing
you
should
remove
or
you're
like
yeah.
D
C
With
Gavin
that
it
doesn't,
it
doesn't
seem
as
important
if
it's
the
result
of
a
scanner
rather
than
a
a
human
initiated
contact.
So
you
know
we
were
debating
whether
you
scare
quotes
or
not,
but
I-
think
a
more
accurate
term
would
be
a
security
team
bot
asked
us
not
to
mention
a
host
name
right.
So
that's
very
different
from
an
actual
security
team,
making
the
request
in
the
sense
that
there's
a
higher
likelihood
for
it
to
be
low
priority
or
false
positive,
so
yeah,
I
I,
would
agree.
We
can.
C
B
If
you
want
to
deal
with
it,
you
can
deal
with
the
Mark
I'm,
not
gonna,
in
these
kind
of
scenarios,
I
usually
like,
unless
they
actually
specific,
like
I,
don't
know
it's
one
of
these
ones
where
they
only
caught
half
of
it
and
they
didn't
actually
look
at
the
content.
They
just
sent
us
email
and
you're
like
right,
and
the
the
concern
is
that
a
hostname
is
made
public
right.
B
Okay,
if
this
is
a
security
concern
to
you
and
it
shouldn't
be,
you
can
change.
You
should
probably
change
your
host
name.
If
this
is
the
concern
it's
already
on
the
internet,
so
yeah
it's
up
to
you
you're
the
amend
you
can
decide
what
to
do,
but
I,
don't
think
as
a
board.
There's
any
real
hard,
fast
rule.
We
don't
get
enough
of
them
to
make
a
big
deal
in.