►
From YouTube: Backdrop Weekly - Oct 31, 2019
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).
B
B
A
C
B
A
B
A
B
I
mentioned
this
last
week,
but
just
in
case
I
didn't
I
wanted
to
welcome
Bob
Christiansen
as
a
new
contributed
module
offer
he's
offered
to
port
use,
selective
filters,
but
I
wanted
to
make
sure
that
we
caught
that.
Thank
you
out
there
and
then,
after
that
we
had
a
couple
of
things
we
were
talking
about
in
the
outreach
meeting
related
to
backdrop
CMS
org.
B
So
if
you're
curious
about
what
we're
doing
there,
I
will
say,
watch
the
video
for
outreach
meeting,
but
they
are
mostly
related
to
getting
people
to
sign
up
for
our
newsletter
in
a
way
that
we
are
legally
allowed
to.
You
know,
but
also
there's
some
other
so
much
other
great
content.
Changes
that
happen
recently.
Oh
I
know
you're,
not
always
in
this
meeting.
I,
don't
know.
If
you
have
anything,
you
want
to
add
about
the
translation
site,
but
if
you
do
now's
the
time.
A
Yeah
all
of
these
here,
after
invitation
so
I,
have
an
idea.
Oliver
mentioned
the
previous
meetings
that
there
is
a
problem
because
of
our
UX
improvements
and
because
we
see
user
experience
flaws
as
part,
and
we
introduced
text
changes
very
often.
It
makes
it
harder
for
the
translators,
so
I
have
an
idea
that
would
sort
of
make
happy
everybody
developers,
translators
and
end
users,
but
I'm,
not
sure.
If
it's
it's
a
little
bit
of
work.
Where
is
it
should
I
say
now,
so
she
started
discussing
it?
A
Okay,
so
so
we
rely
on
Pio
files,
all
right,
and
these
Pio
Files
rely
on
a
string,
a
specific
string
and
then
the
its
translation
for
its
string
relies
on
that
string.
So
even
if
you
add
a
dot
there
or
even
a
some
punctuation
that
might
be
necessary
for
readability,
it
means
that
translators
have
to
do
that
all
over
again.
So
I
was
thinking
that
the
T
function
now
accepts
a
string,
and
then
it
accepts
optionally,
an
array
which
holds
placeholders
within
that
string
and
I
would
like
to
propose
another.
A
A
third
parameter
there,
which
is
an
API
addition,
not
an
API,
an
optional
parameter,
which
would
hold
an
ID,
so
I
know
that
there's
some
translations
that
have
an
America
instead
of
having
the
literal
thing
account
remember.
If
it's
it's
not
products,
it's
called
something
else
and
if
you
feel
find
out
this
specification
of
that,
but
my
idea
was
that
we
keep
the
current
mechanisms
that
rely
on
PL
files,
but
developers
amass
slowly
can
add
a
third
parameter
in
the
T
functions
that
are
actually
an
America,
adding
weights.
A
So
it's
gonna,
be
it's
gonna,
be
all
see.
That's
why
I
said
it's
gonna
be
some
resistance,
but
but
what
that
gains
us
is
that
we
have
the
freedom
to
change
the
strings
whenever
we
want
without
upsetting
that
the
translators,
because
it's
time
that
this
happens
and
they
complain,
are
given
in
modules.
Slowly
just
an
add.
An
ID
there,
which
can
be
I,
haven't
figured
out
everything
how
long
that
will
be.
A
Should
it
be
a
UUID
that
seems
too
much
for
me,
but
the
thing
is
that
the
current
mechanisms
will
have
the
PL
files
a
source
of
truth
when
they
are
doing
the
imports
and
exports,
and
if
they
don't
find
those
strings
that
they
need
to
be
translated,
they
might
fault
those
IDs
fallback,
sorry
to
those
IDs.
So.
B
B
A
I'm,
adding
to
the
the
and
the
English
version
is
the
source
of
truth,
like
the
origin
of
what
needs
to
be
translated.
I'm
saying
that
if
the
origin
of
what
needs
to
be
translated
is
not
found
because
we
changed
something,
then
if
the
function
includes
an
ID,
then
we
fall
back
to
whatever
that
IDs
and
translators.
B
B
So
how
would
that
work
if
we
actually
change
the
text
like,
for
example,
this
description
text
change
right,
like
we
have
a
string
translation
for
description
so
everywhere?
In
course,
description
is
used,
which
is
probably
hundreds
of
places.
We
use
one
translation,
we're
now
changing
that
to
something
completely
different.
Like
final
name,
we
don't
want
description
to
be
translated
as
file
name
right.
We
want
the
final
name,
translation
that
exists
everywhere
else
in
core
to
be
used
instead,
yes,
so
key
them
just
filename
instead
and
change
the
key
when
we
change
yes,.
A
E
A
We
don't
do
it.
The
the
current
system
of
using
do
files,
and
whatever
is
is
the
in
translation,
will
take
effect
so
long
as
we
don't
change
that
string
right,
but
there
would
be
a
second
set.
I
haven't
decided
if
and
I
need
to
check
the
PIO
specifications.
Can
we
include
that
in
PL
files
or
will
it
have
to
be
an
additional
file
which
adds
a
burden,
but,
as
I
said,
this
will
be
an
optional,
an
additional
step.
Then
it's
time
that
people
complain,
we
say:
ok,
yeah,
let's
add
an
ID
there.
A
Let's
add
an
ID.
So
this
iteratively
at
some
point
will
reach
a
point
where
we
have
the
the
old
system
which
will
still
keep
in
place,
and
that
would
be
the
how
we
do
things.
The
simple
thing
that
everybody
knows
and
there's
documentation
about
it.
But
we
will
also
have
this
optional
thing
which
doesn't
break
the
API.
It's
an
addition
and
it's
sort
of
like
solve
the
problem.
B
Of
really
like,
if
this
gets
away
from
using
English,
is
the
like
canonical
source
I
feel
like
it's
a
little
bit
more
fair.
That
way,
just
have
anything
really
weird
that
happens
in
English
that
doesn't
have
an
another
link
it
just.
We
won't
be
trying
to
like
work
around
that
we'll
just
fold
the
like
correct
language,
hurt
the
juice.
A
A
What
makes
it
harder
and
that's
why
I
said
we
need
to
keep
everybody
happy.
Users
will
be
kept
happy
because
the
translations
will
be
more
resilient
as
society
changes
translators.
Eventually,
they
will
have
to
do
a
little
bit
more
work
gradually.
It
doesn't
have
to
do
translate
everything
now,
but
as
they
see
things
that
have
they're
missing,
they
cannot
dose
that
idea
and
that
that
becomes
future
proof
because
it
uses
the
idea
the
idea.
Now
the
thing
is
with
developers.
A
If
we
did
what
you
just
mentioned
now,
like
change
the
source
of
truth
to
be
an
ID,
we
think
code,
we
would
write.
For
example,
the
description
of
the
element
description
equals
one
two,
three,
four:
zero
something:
what
that's
not
friendly
for
developers
and
they
will
stop
nagging
with
this
solution,
which
is
a
hybrid.
Would
we
still
get
to
keep
T
and
the
English
strengths
there,
which
can
be
updated
or
not,
but
it
will
be
T
strengths
to
be
translated,
optional
array,
optional,
ID,
then
so
yeah
I
would
I
would
like
to
explore
that
option.
A
B
A
F
A
A
Don't
that's
why
I
wanted
to
bring
it
up.
I
know
that
Olaf,
maybe
maybe
some
of
the
things
that
we
discussed
is
too
technical
for
you,
but
I
needed
technical
sort
of
like
direction
from
the
people
that
understand
what
what's
gonna
happen
in
code.
The
the
thing
that
you
need
to
know
is
that
we
have
the
potential
to
now
make
the
translations
more
resilient.
Even
if
the
string
changes
with
a
little
bit
of
more
work,
we
can
make
the
translations
be
more
easily,
and
so
it
doesn't
upset
I.
Also.
A
B
It
might
be
a
good
idea
like
when
we
first
introduced
this
to
grab
like
the
most
commonly
used
strings
in
core
and
give
them
IDs.
So
things
like
configure
edit,
like
really
obvious
things,
and
that
way
we
would
have
a
good
like
basis
to
use
as
a
test
case,
and
then
we
could
write
tests
that
were
like
change.
The
string
edit
to
like
something
else.
A
So
one
technical
problem,
one
technical
challenge-
I-
would
say
that
comes
with
that
and
the
reason
it's.
Finally,
what
triggered
this
whole
thing
so
that
the
the
moment
that
we
added
the
label
for
needs
translation
update
this
started
being
at
the
back
of
my
head
all
the
time
I
was
thinking
of
all
of
because
I
really
want
to
join
the
multilingual
team
having
English
as
a
second
language,
I
really
want
to
translate
things
to
Greek.
So
it's
a
back
project
to
me.
A
So,
interestingly,
someone
mentioned
something
in
the
forum
about
adding
additional
mime
types
for
media
and
then
I
created
issue
for
one
double.
Seven
and
I
noticed
that
it's
time
that
we
want
to
add
a
new
mime
type,
we
have
an
array
which
has
numbers
like,
and
this
go
from
one
two,
three
four
five
six
and
then
it
goes
to
350,
and
that
happened
because
we
still
need
needed
to
keep
the
to
keep
the
values
alphabetical,
but
the
array
already
had
reached
349.
A
So
this
is
the
problem,
the
same
problem
that
will
face
with
those
IDs
we've.
The
challenge
is:
how
do
we
know
like
if
these
are
incremented?
How
do
we
know
what's
the
last
one
and
if
you
have
multiple
pull
requests
that
in
court
that
include
IDs?
It's
the
same
problem
that
we
have
with
update
hooks?
So
if
you
have
three
PRS
for
the
same
release
that
target
the
same
install
file
and
they
all
need
update
hooks,
they
will
go
to
the
next
one,
but
they
will
all
have
the
same
thing.
A
So
the
the
one
that
gets
committed
first
wings
and
then
the
other
ones
need
to
update
there.
So
it
will
be
a
same
thing.
The
same
thing:
I,
always
I'll
figure
out
the
specifics.
I'll
put
down
an
issue
with
points
like
action,
points
and
decision
points
that
we
need
to
make
and
at
some
point
I
would
like
to
have
a
crack
at
it.
I.
D
A
C
A
D
A
Sure
but
yeah
look,
we
think,
there's
what
we
can
do
is
like,
because
this
doesn't
have
to
be
like
we
can
be
adding
digits.
We
can
make
it
like
if
it's
an
integer
integer
last
eight
years.
Yes,
you
had
zeros
and
that's
it
but
yeah.
My
initial
thought
was
you
you
IDs,
but
you
do.
Ids
are
like
they
will
even
in
code
when
we
add
that
as
a
parameter,
it
will
take
a
lot
of
space.
A
A
Because
he's
sending
integer,
we
can
just
add
zeros
where
it's
at
the
end.
It
would
still
not
mess
it
up.
So
if,
if
pio
files
allow
you
to
have
multiple
sort
of
like
origins
like
ever,
have
both
a
string
and
a
number
for
origin,
it
would
be
perfect,
but
I
don't
think
you
would
allow
it
so
yeah
implementation
wise.
It
might
be
a
little
bit
tricky,
but
I'm
prepared
to
just
do
something.
A
Call
that
because
I
don't
want
to
stop
updating
like
or
losing
the
ability
or
I
don't
want
to
scare
people
that
are
interested
like
UX.
Have
another
thing
to
think
about,
like
maybe
I
shouldn't
change
that,
because
it's
gonna
upset
the
translators.
If
something
needs
to
be
updated
to
make
more
sense,
it
should
it's
a
UX
bar
any
genetics,
even
if
it's
just
punctuation.
Sometimes
it
makes
a
difference.
Oh
yeah.
C
B
B
A
But
I
respect
the
fact
that
I
made
not
like
holding
back
those
changes,
but
then
people
like
Olaf
and
whoever
because
all
the
flip
presents
a
lot
of
people
had
actually
doing
the
translation
and
I
don't
want
the
disappearance.
Then,
if
it's
all,
this
is
too
much
work,
it's
time
that
they
have
a
release
and
breaks
things.
Yeah.
E
A
Was
sort
of
like
I
was
trying
to
please
everybody
and
I
was
also
trying
to
keep
in
mind
the
developer
aspect
of
it.
This
is
why
I
didn't
say
you
you
IDs,
because
I
wouldn't
I
know
that
if
we
use
u
UI
basic
will
be
sort
of
like
messy
in
the
code
yeah,
so
yeah,
we'll
figure
it
out.
We
have
a
good
brainstorming
team,
so
yeah
I'm
company.
B
F
Possible
yeah
yeah,
that's
gonna,
be
interesting
to
work
through
it.
I
I
think
I've
heard
this
proposed,
like
hosts
of
dozens
of
times
actually
over
the
years
in
Drupal,
by
lots
of
different
people,
but
there
has
always
been
a
lot
of
pushback
of
like
either
that's
too
hard
or
that's
a
lot
of
work
and
so
yeah.
A
F
F
So
that's
just
kind
of
you
know,
as
we
get
time
like.
That
would
be
a
good
task
for
anybody
to
pick
up.
It's
it's
usually
fairly
straightforward.
Porting
those
things
over
because
our
code
compatibility
is
still
very
strong,
even
though
it's
it's
out
of
date.
So
the
objective
is
there
is
to
get
it
not
out
of
date
with
Drupal
7
and
make
it
much
more,
actually
increase
the
similarities
between
the
two.
F
Let's
see,
we
also
have
an
issue
for
flexible
templates
follow-up
issues.
Another
big
meta
at
40,
46,
I,
haven't
seen
any
of
these
in
particular
that
have
had
any
activity.
Yet
do
you
guys
have
anything
that
is
related
to
flexible
templates?
That
has
seen
any
motion.
That's
worth
the
worth
discussing.
A
A
It's
time
that
we
changed
it,
I
was
stuck
because
the
issue
that
came
up
during
QA,
like
during
testing,
was
that
they
wouldn't
update.
It
worked
on
my
local
because
I
had
disabled
or
caching,
but
it
wouldn't
work
on
the
sandbox.
So
then
I
got
myself
into
a
rabbit
hole
of
adding
tokens
into
images
like
cash
tokens
at
the
end,
but
we
can
work
around
that
by
randomizing
the
names
for
now.
F
G
A
F
Okay,
great,
let's
see
any
other
114
to
items,
there's
looking
at
the
milestone,
there's
currently
49
issues
that
are
tagged
for
that,
a
lot
of
which
are
in
needs
review,
which
is
fantastic.
Do
you
guys
mind?
You
would
like
to
bring
up
as
being
like
interesting
of
note
or
something
needs
discussion
and.
C
I
have
one
one
issue
of
personal
interest:
its
issue:
41
58
and
I've
made
a
poor
request,
it's
about
when
Adam
old
or
a
tidy
attribute
to
an
image.
A
part
of
the
text
gets
stripped
when
there's
a
cologne
in
the
string,
and
we
had
a
similar
problem
with
image
captions
a
while
ago,
and
and
now
it
turns
out,
that's
also
in
the
old
that
I
do
attribute
and
I
would
like
some
feedback
to
the
PR,
because
it's
it
changes
security-related
code
and
I.
Can't
I
can't
evaluate
it's
dangerous.
What
I'm
doing
there?
C
Yeah
because
it's
seen
as
part
of
a
protocol
like
HTTP
or
JavaScript
:
yeah,
it
looks
like
they're.
F
A
E
A
A
Don't
know
why
so
it
is
I
have
to
dig
I
promise.
I
will
get
to
that
eventually
as
well.
It's
I've
added
it
in
one
of
my
favorite
things
to
review
so,
okay,
it's
Teddy,
giving
thanks
thanks
for
that.
Don't
thank
me
yet
because
I
said,
I'm
really
swamped
for
the
next
three
weeks,
but
I'll
try
to
find
time.
Okay,.
A
F
A
A
G
A
F
Would
take
taking
that
patch
and
putting
it
back
in
the
Drupal
7
issue
and
seeing
what
people
say:
that's
a
good
way
to
solicit
feedback,
to
figure
out.
Why
why
they're
doing
something
different
than
than
we
are?
It
also
would
be
good
to
take
the
Drupal
7
patches
at
some
test
additions
like
we
should
yes
take
those
and
apply
those
to
your
approach,
just
to
make
sure
that
you
get
the
same
result.
Yeah.
A
F
Let's
see
that
was
issue
41
58
just
for
reference,
okay,
so
115
we'll
move
on
to
the
next
minor
version
of
backdrop
that
will
be
coming
out
to
January
fifteenth,
twenty
twenty
with
feature
freeze
on
January,
1st
or
thereabout.
Again,
like
seems,
like
our
feature,
freeze,
always
manages
to
land
on
holiday.
F
That
usually
means
that
we
push
it
to
it
to
the
next
day,
but
we'll
see
as
that
approaches,
let's
see
so.
The
first
item
that
we've
got
here
is
issue.
4031
moved
the
contents
of
the
manage
file
display
page.
This
is
related
to
the
file
entity,
functionality.
It
went
into
114
Jen.
You
are
the
advocate
for
this.
You
want
to
give
us
an
update,
yeah.
B
I
noticed
there
was
another
issue
in
the
key
that
was
just
about
adding
fields
to
pseudo
adding
settings
to
pseudo
fields,
but
I
thought
we
should
probably
do
it
with
something
that's
using
it,
rather
than
it's
only
just
that
we
haven't
actually
use
of
it
in
core
issues
that
require
like
the
title
sets
file
filled
things
much
more
complicated
example,
but
we
have
a
bunch
of
places
so
we're
gonna
use
it
so
I'm
working
on
here,
we'll
see.
We
think
this
is
a
good
enough
place
to
put
it
in
with,
but
progress
anyway.
B
F
Yeah
I
go
either
way;
it
just
depends
on
complexity,
but
I
think
you're
on
the
same
page,
though
it's
like,
if
it's
if
it
turns
out
to
get
really
gnarly,
then
separate
them.
Okay,
let's
see
next
item
that
we've
got
here
is
at
an
image
library.
Modal
to
image
fields
issued
3297
Lauren
is
not
on
the
call
today,
but
this
has
been
seeing
a
lot
of
activity
this
past
week.
Let's
see
Graham's
been
involved.
Jen,
you
posted
a
comment
or
two:
do
you
have
any?
F
F
F
F
F
H
E
F
Was
or
was
not?
Okay,
okay,
so
there's
so
much
activity
there.
We
don't
know
what's
going
on
because
it's
changing
faster
than
when
you
can
look
at
it,
which
I
guess
is.
You
know
not
a
bad
place
to
be
alright,
so
this
and
this
overall
I'll
just
save
lots
of
progress.
That's
great
to
see
these
two
gallon
moving
forward.
That's
probably
like
some
of
these
other
things
get
a
little
esoteric
and
that's
a
very,
very
direct
improvement
for
editors
and
authors.
So
that's
a
great
one.
F
F
D
E
F
On
to
the
next
one,
which
is
the
recent
news
block
in
the
dashboard
issued
thirty
five
sixty
six
Tim
near
the
advocate
for
this
one-
oh
it
says
here
no
status
update
since
last
week.
Is
that
the
case?
Ok,
ok,
ok,
I'll,
just
keep
rolling
then
provide
wait
to
rename
disabled
text
formats
issue
1575,
Gregory
you're
the
advocate
for
it,
but
says
here
no
status
update
since
last
week.
Yes,
I
as
I
said.
A
G
F
I
recall
the
last
change
that
I
did
really
threw
a
wrench
in
things,
so
I'm
happy.
Yes,
you
guys
bad
idea
and
just
take
that
back.
So,
let's
see
alright.
Next
up,
we've
got
issue
1992
digital
signatures
on
packages,
this
one's
my
issue
that
I'm
an
advocate
for
so
we
I
did
make
some
progress.
I
moved
code
sign
into
its
own
contribute
positively.
F
Some
modules
code
code
sign
PG
our
site,
GPG
and
code
sign
OpenSSL,
so
different
alternatives
to
signing
packages.
I
also
did
some
minor
code
updates
to
fixing
the
API
and
as
I
get
into
it
and
I'm
actually
trying
it
out
running
into
a
number
of
things.
So
I've
started
using
the
issue
tracker
in
that
control
to
start
tracking
things
that
potentially
need
to
be
fixed.
F
That's
gonna.
Take
me
a
little
bit
of
work
investigating
it,
but
one
of
those
issues,
I
filed
is
add
documentation
because,
like
we
need
to
be
able
to
have
you
know
lots
of
people
testing
this
in
order
for
it
to
be
effective
and
approved.
So
still
it's
it's
encouraging
to
move
forward
on
that.
I
also
found
out
that
GPG
wasn't
installed
on
my
local
host,
which
immediately
makes
me
suspicious
about
using
that
as
a
viable
signing
option.
If
it's
not
usually
installed
but
I,
think
open.
F
Ssl
was
the
one
that
we've
kind
of
been
saying:
that's
the
most
widely
available
one
anyway,
so
yeah
anyway.
It's
all
it's
very
interesting
I'm,
having
kind
of
some
fun
diving
into
that,
so
I,
don't
I!
I
can't
really
tell
people
how
to
try
it
all
out.
Yet,
though,
it's
in
project
module-
and
it's
in
the
code
sign
repository
now,
you
can
clone
both
of
them
locally
and
start
playing
around,
but
because
there's
almost
no
documentation
whatsoever.
F
F
F
A
Have
one,
but
not
for
115,
necessarily
it's
by
Allan
14
174
about
this
is
about
specifically
allowing
it
falls
into
the
d8
parody
B
arm
of
issues.
But
we
have
a
larger
issue
than
that
which
says
that
certain
things
should
be
allowed
to
be
overwritten
in
settings.php,
which
is
that
other
issue
is
oh.
A
F
B
A
F
A
Been
a
long
time
so
last
it
was
abated
back
in
April
and
I
haven't
taken
a
look
at
the
actual
proof.
I
can
remember
how
its
intimated
I'm
just
there's
a
screenshot
in
that
issue
and
I
like
the
the
UI
UI
implementation
of
it.
But
what's
the
number
one
my
turn
to
2
H
0
5
and
if
you
scroll
to
24th
of
April,
we'll
see
one
of
those
comments
saying
that
is
updated
the
concept
and
he
has
this
feature
there.
F
A
F
H
A
F
Goodness
so
many
things?
Yes,
okay,
oh
it's!
This
issue!
That's
funny!
I
love
it
when,
when
it's
an
issue,
that's
been
stuck
in
a
quagmire
and
then
something
amazing
comes
along
that
like
solves
everything,
so
14
or
so
1475
being
one
of
those
ones.
That's
like
it's
been
going
through
a
few
several
iterations
of
discussion.
F
A
Yes,
so
this
is
sort
of
like
to
make
a
decision
on
the
policy
and
I'm
inclined
to
say:
I
agree
with
the
end
unless,
unless
the
issue
has
been
like
closed
yesterday-
and
we
found
that
there's
a
body
we
didn't
reopen
it,
but
otherwise
I
prefer
keeping
the
milestones
and
then
having
a
follow-up
and
mentioning
the
previous
tickets
there.
So
if
we
found
out
that
something
was
amiss
with
something
that
we
committed,
I
prefer
a
separate
issue
as
a.
H
B
B
A
F
Speaking
speaking
of
the
bath,
that's
not
working
I'm,
sorry,
I'm,
gonna
go.
Take
us
down
a
rabbit
hole.
Jenna
mentioned
to
me
this
past
week
about
github
actions,
a
new
feature
that
they
currently
have
in
Veda.
That
allows
you
to
respond
to
API
events
in
an
automated
fashion
and
trigger
any
other
API
actions.
It's
basically,
you
would
imagine
like
rules
for
github.
F
That
could
be
an
interesting
thing
to
allow
us
to
do
automation
like
this,
hopefully
without
needing
to
have
any
maintenance
overhead
of
running
our
own
surface
on
some
server
that
you
know
goes.
You
know
that
we
don't
know
how
to
maintain
or
that
restarts
or
kills
itself,
and
only
one
person
knows
how
to
use
it.
F
A
Speaking
of
automation,
there
was
another
thing
that
was
mentioned
on
git
or
anything
automatically
closing
all
the
issues
with
that
is
inactive
and
I.
Think
that
Jen
mentioned
that
so
long
as
it
doesn't
close.
We
have
a
way
like
to
exclude
things
by
a
label
that
will
be
okay.
It's
just
that.
I
know
that
I
work
in
support,
so
I
know
that
having
big
issue
queues
is
annoying
and
cumbersome.
A
But
I
don't
want
to
see
issues
being
closed
because
if,
like
we
give
the
wrong
message
to
the
people
that
has
opened
the
the
ticket
and
after
one
year
or
two,
we
haven't
solved
it
and
we
dismiss
it,
we're
being
dismissive
and
we're
closing
it
automatically
as
well.
Above
does
that
I?
Don't
want
us
to
be
that
kind
of
community
yeah
I
prefer
tickets
to
linger
on,
and
then
someone
like
myself
or
Peter
BW
panda
goes
and
just
digs
through
the
queue
in
reverse
order.
Yeah.
E
A
B
I
think
issues
should
remain
open
until
they
are
either
resolved,
or
it's
determined
that
they
will
not
be
resolved
or
requests
if
they
get
really
old.
I
might
be
okay
with
those
getting
closed,
because
they're
gonna
need
to
be
rebased
anyway,
and
it's
not
like
200
requests
that
get
close
to
the
branches
get
deleted.
There's.
A
B
B
H
I'm
sympathetic
to
all
these
arguments,
but
the
discussions
on
this
on
this
thing,
you
know
it
sounds
like
there's
a
lot
of
flexibility,
so
I
think
most
of
the
concerns
were
raising
could
be
addressed.
I'm,
not
sure
how
important
it
is,
but
like
it
doesn't
have
to
close
the
issue.
It
could
just
mark
them
as
stale
I'm,
assuming
that
there
might
also
be
an
option
to
when
it's
closed
to
actually
post
a
note
saying:
listen,
you
know
we
don't
mean
to
dismiss
this
issue,
but
there
hasn't
been
any
activity.
Please
feel
free
to
reopen.
H
B
F
H
I
I
think
it
was
triggered
because
p.w
bamboo
went
through
and
like
was
closing
a
bunch
of
issues
and
somebody
else
just
said
yeah.
We
could
automate
this,
so
he
doesn't
have
to
spend
the
time
doing
it
and
I
think
he
does
it
and
I've
done
it
too.
Just
because
sometimes
it's
nice
to
see
the
number
go
down
there.
H
B
A
A
And
in
the
grand
scheme
of
things
like,
we
have
almost
2,000
tickets
open
and
over
the
past,
like
three
or
four
months,
we
might
have
closed
like
30
of
them.
That
way
so
yeah
I
don't
see
any
big
profit
by
automating
that
there
is
profit
I'm,
not
I'm,
not
dismissing
it,
but
yeah.
We
need
to.
We
need
to
consider
the
human
factor
as
well.
I
do.
B
I
E
H
But
they're
still
open
that
way.
Somebody
like
Peter
could
just
click
on
that
tank
and
more
easily.
I
mean
I
know
it's
still.
You
can
just
like
do
it.
There
are
other
ways
of
doing
this
filter,
but
if
there
were
a
tag
that
said
hey,
this
issue
is
two
years
old,
still
open.
That
might
make
it
easier
for
people
to
go
back
and
review
them.
We.
B
An
issue
with
like
having
too
many
labels
is
also
problematic
for
new
people,
but
I
do
like
this
idea
of
having
something
easy
for
someone
to
click
on.
Maybe
this
is
something
we
can
put
on
our.
How
do
use
the
core
htq
page,
where
we
can
build
this
link
by
adding
those
filters
and
then
put
that
link
and
get
like
hey.
B
You
want
to
help
us
close
old
issues,
here's
a
link
and
so
I
think
the
more
of
those
things
like
if
we
already
have
tools
to
build
that
list
with
the
current
tags
or
sort
or
whatever,
let's
make
those
links
for
people
and
make
it
so
that
there
is
something
easy
for
people
that
click
on
I
like
I
like
that
idea.
Okay,.
H
A
As
I
said,
if
we
have
a
way
to
exclude
tickets
from
being
desire,
I
had
this
problem
with
certain
issues
that
what
the
milestone
and
then
they
got
forgotten
and
they're
like
hidden
gems,
like
I,
go
back
to
them
at
the
arm.
This
should
have
been
done
earlier
and
it's
now
lost
in
the
work
of
mucked
up
too
many
issues.
So
this
is
what
I'm
trying
to
avoid
closing
issues
that
are
legitimate
ones
by
a
robot,
yeah
and
I'm.
Just
telling
you
now
I
watch
the
queue
anyway.
So
if
the
robot
closet
I
would.
D
B
If
it's
it,
so
if
it's
a
bug-fix
issue
and
it
has
a
poor
request,
it
can
be
added
to
the
bug
fix
milestone
and
if,
even
if
you
added
the
PO
request,
that's
totally
fine,
you
are
allowed
to
add
it
to
the
milestone.
The
only
one
that
needs
verification
is
if
the
issue
doesn't
have
a
pull
request,
but
you
think
it's
super
important.
You
could
add
master
and
candidate
label
and
then
someone
else
would
have
to
add
just
a
milestone.
A
If
you
wanna
add
a
milestone
to
it,
you
can
add
the
milestone
candidate
tag
and
then,
let's
get
her
know
like
post
on
gear,
that
hey
guys
I
think
this
is
a
milestone
candidate.
If
anyone
agrees
because
that's
the
process,
actually
someone
tags
it
as
a
with
a
label
and
then,
if
that
second
person
agrees,
they
can
milestone
it
yeah.
E
A
E
A
A
E
E
B
B
I
You
should
like
to
bring
up
it's
along
the
same
lines,
but
it's
gotta
for
the
best,
and
so
maybe
I
don't
agree
that
it's
a
milestone
one.
They
can
do
that.
It
came
about
as
a
result
of
me
writing
tests
for
the
backdrop
console
and
route
module
to
test
a
multi-site
support
and
I
realized
that
the
backdrop
calls
install
script
like
installed
on
SH
doesn't
support
multi
sites.
So
there
is
an
issue
I
prayed
for
that
with
full
request,
which
is
issues
41:51,
so
just
knew
how
under
test
and
review
that
for
me.