►
From YouTube: Backdrop Weekly, May 9th
Description
Today’s development agenda: http://bit.ly/2JaGZci
A
Welcome
to
watch
that
video
to
see
how
things
are
coming
along
there
I
love
the
translation
site
section
on
here,
because
I
didn't
know.
If
you
wanted
to
add
anything.
Oh,
but
no,
okay,
I
want
to
say
thank
you
since
you're,
here
in
person
for
doing
all
the
great
work
of
figuring
out
what
was
up
with
translations
and
getting
changes
into
the
last
version
or
into
the
next
version
of
vector
poor.
They
don't
make
translating
sites
much
easier,
so
I'm
really
looking
forward
to
that
yeah
and
then
for
backdrop.
C
Yeah,
so,
okay,
first
of
all,
there
are
some
issues
that
are
still
in
the
1
12
7
release,
which
is
112,
is
the
current
minor
version
of
backdrop,
and
so
112
7
will
be.
The
final
version
probably
released
on
May
15th,
along
with
113,
and
we've
got
a
couple
of
issues
that
we're
trying
to
work
through.
That
will
be
invoked
both
that
version
and
the
113
release
this
first
one
supporting
multiple,
equivalent
equivalent
security
releases
issue.
C
So
if
we,
if
we
do
manage
to
make
that
functionality
work,
it
would
be
nice
if
we
could
actually
have
that
be
in
place
for
the
112
release
during
the
entire
time.
While
it's
contagious
to
be
supporting
to
114
comes
out,
so
maybe
that
won't
make
it
for
112
7,
but
maybe
we'll
still
be
able
to
make
it
in
112
8
or
something
like
that.
Even
after
we
officially
stop.
C
You
know
developing
new
features
for
112,
just
because
112
will
still
be
under
security
coverage
and
we
want
that
security
coverage
to
be
reflected
accurately
when
you're
using
it.
So
so
I
don't
know,
maybe
we'll
see
about
the
impact
it's
possible.
That's
112
might
get
that
one
new
feature
or
both
effects,
even
after
we're
in
security
only
updates,
because
it
pertains
so
heavily
to
the
security.
A
period
of
that
release.
C
Let's
see
one
last
issue
that
we've
got
for
112,
7
well,
I
should
say
one
one
last
issue
that
we
keep
calling
out
on
these
meetings
is
that
we
have
one
more
RTL
issue
with
CK
editor
icon
source,
still
showing
a
broken
and
RTL
languages,
and
so
issued.
3504
currently
needs
review,
but
I
think
it's
been
in
that
state.
For
a
couple
of
weeks
now,
I
think
we
just
need
some
eyeballs
on
it
from
someone
to
test
it
out
and
see
if
they
think
it's
ready
for
committing.
C
113
is
the
next
minor
version
of
backdropped
will
be
coming
out
really
soon
less
than
a
week
on
Wednesday.
Next
week,
May
15
2019.
We
had
Fiji
breeze
a
little
over
a
week
ago
and
we
got
in
a
lot
of
things
that
are
exciting,
but
I'm
not
going
to
recap
those
since
I
imagine
that
was
already
covered
last
week
when
I
wasn't
here,
but
we
are
working
through
some
last
items
still
in
the
next
week
and
if
we
get
them
completed,
then
that'll
be
great.
C
Let's
see,
in
the
past
week
we
took
field
formatter
settings
actually
before
code
freeze,
we
merged
field
formatter
settings
module
into
court
this
past
week.
We
made
it
so
that
if
you
have
the
controversion
of
that
module
installed,
it's
gracefully
disabled
for
you
and
switched
over
to
the
core
implementation.
Instead
in
issue
3742,
so
that's
been
merged.
We
have
a
follow-up
in
issued
3760
right
now.
We
have
several
places
where
a
control
has
been
merged
into
core.
C
You
may
remove
it
from
your
filesystem,
and
that
means
that
we
currently
have
the
exact
same
code
in
a
couple
of
different
places
where
we've
merged
controls
into
court,
and
so
3760
is
an
issue
in
which
clonus
has
consolidated
that
code,
where
we
have
exactly
the
same
code
in
multiple
places
made
it
into
a
generic
function.
So
that
could
be
useful
for
ensuring
consistency
when
we
merge
modules
of
the
core,
as
well
as
simplicity,
making
it
so
that
thing,
the.
C
C
This
one
is
currently
held
up,
not
really
held
up.
It
needs
redrawing
because
right
now
we're
moving
some
fees
around,
but
not
quite
all
of
them.
It
looks
like
we
move
the
recent
comments
view
into
common
module
and
we
move
the
taxonomy
term
listing
pages
into
taxonomy
module,
but
the
promoted
view,
which
is
basically
the
homepage
which
is
slash
node,
is
not
moved
into
node
module,
and
so
the
requests
on
that
one
is
that
we
moved
that
third
view
out
of
views
module
and
into
node
module,
so
that
all
three
modules
in
their
respective
views.
C
Unfortunately,
that
needs
some
work
still,
and
so
it's
likely
that
this
is
this
issue
of
of
getting
comments.
Converted
the
comment
administration
listing
can
Road
to
a
view.
It's
probably
going
to
get
stuck
and
not
be
in
113
because
of
being
held
up
on
this
other
dependent
issue.
But
3306
is
where
we
need
to
start
first
and
then
once
3306
is
in
place,
then
549
to
be
completed.
C
There's
no
pull
request
behind
this
code.
Yet
it's
it's
just
a
suggestion,
so
I'm
kind
of
thinking
that
this
is
unlikely
to
be
and
one
one
thirteen
as
well
so,
but
if
a
lot
of
take
a
stab
at
it,
you
know
we
could
potentially
still
make
that
happen,
and
that's
all
I've
got
for
the
one.
Thirteen
issue
list,
like
are
a
number
of
items
that
we
have
still
pending
for
one.
Thirteen
is
really
small,
because
you
know
at
this
point
we
don't
really
want
to
make
an
extensive
amount
changes
so
yeah.
That's
it!
C
Next
up
on
the
agenda,
we're
going
to
trying
to
build
out
some
planning
for
114
the
next
minor
version.
We
have
a
whole
bunch
of
milestone
candidates
that
are
tagged
in
github,
with
the
tag
literally
milestone
candidate
minor,
and
so
we
have
a
number
of
issues
that
we
want
to
discuss
as
being
possible
candidates
for
114
Jeff.
Do
you
want
to
jump
in
here
as
well?
I'm
with
we
don't
really
have
an
official
decision
making
process
for
prioritizing
things
in
the
next
release.
C
Usually
it's
a
combination
of
where
there's
enthusiasm,
combined
with
what
we
think
is
important,
like
as
a
community
and
see
if
we
can
actually
trim
up
some
enthusiasm.
But
historically,
what's
happened.
Is
that
even
things
that
we
as
a
community
might
decide
are
important,
has
necessarily
received
a
lot
of
enthusiasm,
and
so
we
can.
We
can
try
to
drum
up
with
dizzy
as
I'm
and
make
it
so
that
we
can
prioritize
certain
things,
but
that
doesn't
mean
it
always
succeeds.
So.
C
What
we're
going
to
do
now
at
least
trying
to
figure
out
you
know
what
items
we
would
like
to
drive
enthusiasm
towards,
but
possibly
also,
you
know
what
things
could
be
realistic.
As
far
as
you
know,
there's
already
enthusiasm
behind
these
things
and
we
would
just
like
to
see
them
to
completion
yeah.
A
Signing
trusted
hos
patterns,
putting
something
like
honeypot
in
core
putting
something
like
van
or
auto
fan,
either
back
in
horror,
import
afresh,
adding
an
email,
obvious,
cater
setting
up
a
better
way
to
handle
two-factor
authentication
I'm,
putting
the
SMTP
module,
which
would
require
an
occasional
Fitzgerald
service
and
backup
and
migrate,
which
is
our
number
one
most
used
background.
A
So
those
are
just
ideas
based
on
like
okay,
oh
wow,
there's
a
whole
bunch
of
stuff
in
here.
That's
security
related
that
we
could
kind
of
put
it
a
bunch
of
effort
time
and
we
can
make
factor
of
significant
ility
like
more
secure
and
one
release,
which
would
be
really
good
and
it
would
kind
of
coincide
with
our
like
announcing
of
our
new
security
policy,
the
blog
post.
A
That's
blowing
up
all
of
that
stuff
that
has
been
happening
recently,
but
nimi
also
mentioned
last
week
in
this
meeting
that
there
are
a
bunch
of
really
good
issues
that
had
previously
been
scheduled
for
milestones
have
been
bumped
that
maybe
we
should
revisit
one
of
those
included
getting
references
and/or.
There
were
layout
relationships
which
are
really
close
for
a
long
time,
but
never
managed
to
get
in
beautiful
files,
which
is
like
only
stucked
in
the
usability
department
but
functionally
it
works,
and
then
there's
a
bunch
of
other
stuff
that
awesome.
A
It's
been
funk
because
it
hasn't
been
getting
actively
like
this
past
release.
We
bumped
save
draft
in
court,
so
there's
stuff
like
that
where
it's
like.
Oh,
we
thought
these
were
good
ideas
that
they
never
really
caught
on,
like.
Obviously
it
wasn't
important
enough
for
anybody
to
feel
that
they
personally
had
to
work
on.
Is
it
worth
trying
to
bring
those
back
in
and
say?
Okay,
let's,
let's
look
at
this
again?
A
Like
you
know,
maybe
we
have
one
person
on
something,
but
we
didn't
get
enough
people
to
get
it
done,
but
we
all
really
like
the
idea-
or
we
could
you
know
just
take
kind
of
a
poll
of
whoever's
in
this
meeting,
whoever
joins
in
and
get
or
whoever
has
conversations
otherwise
about
what
they
think
priorities
should
be.
We
have
started
at
forum
topic
last
week
about
what
people
might
want
like.
A
What's
most
important
for
them,
trying
to
backdrop,
I,
don't
think
I
saw
anything
in
there
that
related
to
current
core
issues,
but
that's
also
something
that
we
can
kind
of
keep
an
eye
on
collect
that
information
create
core
issues
out
of
things.
If
there
aren't
ones
already
and
flagging
will
question
can
be
to
review
release
from
now
three
months
from
now
or
whatever.
We
could
also
kick
this
decision
to
the
project
management
committee
since
they're,
supposedly
in
charge
of
the
direction
of
the
project.
A
One
thing
I
would
like
to
note,
though,
is
that
getting
consensus
from
the
project
management
committee
or
even
a
vote
can
be
a
service
low
process.
So
I
think
it
would
be
better
if
we
could
have
a
proposal
for
them
to
review
rather
than
saying,
please
make
a
decision
on
something
without
a
proposal
other
propose
so
I,
don't
know
if
you
guys
want,
have
had
a
chance
to
review
this
lessons
last
week
and
have
thoughts
about
what
we
should
put
back
on.
A
It
I
personally
really
liked
the
idea
of
having
releases
that
are
pneumatic
like
oh,
this
one's
on
these
are
experience
this
one's
on
security
improvements,
this
one's
on
APN
compatibility
or
whatever
it
is,
but
it
seems
to
be
that
we
adjust
organically
based
on
the
issues
that
are
getting
the
most
attention
and
it
could
be
that
halfway
through
a
cycle,
all
the
issues
that
we've
decided
a
priority
have
been
completely
ignored,
but
there's
a
whole
bunch
of
new
stuff.
That's
come
up
with
getting
a
lot
of
attention
that
we're
like.
A
D
A
Feel
the
pulse
of
the
community
and
what
people
are
currently
fighting
with,
or
working
and
getting
those
in
so
I
have
like
conflicting
feelings
about
it.
Obviously,
but
yeah
I,
don't
know,
I
think
that,
now
that
we
have
this
label,
we
have
a
better
idea
to
take
a
better
way
to
take
the
pulse
of
what
the
community's
wanting,
which
is
good.
But
now
we
have
to
figure
out
like
how
do
we
use
this
label
to
make
our
priority
list
for
the
next
choice?
So
yeah
I
don't
know.
A
D
Is
that
is
there
added
value
there?
I
don't
know?
Maybe
it
doesn't?
Maybe
it
doesn't
matter
any,
but
ultimately,
really
all
it
is
is
a
sort
of
a
list
of
hey,
or
these
are
things
we
think
are
important.
You
know
we
hope
people
will
work
on
so
I.
Don't
know
you
can
decide
how
official
you
think
you
need
to
make
that,
but
I
think
you're
right
that
at
the
very
minimum
we
would
need
to
provide
the
PMC
with
some
suggestions
right.
They
don't
have
the
time
to
like
do
the
work.
D
I
am
inclined
I,
you
know
truthfully.
I
mean
I
I
have
advocated
in
the
past
for
making
space
for
people
to
bring
up
new
things,
but
that's
very
different
than
like
making
decisions.
So
I'd,
like
you
know,
my
ideas
have
been
more
around.
How
do
we?
How
do
we
surface
items
which
we
might
not
have
been
thinking
about
and
I'm,
not
I'm,
less
sure
about
how
down
like
focus
on
them?
I
know
that
when
I
look
at
the
list,
you
know
as
I
scan
through
that
list.
D
It's
like
really
hard
for
me
to
evaluate
you
know
it's
like
I
go
to
the
ones
that
are
that
are
most
important
to
me,
not
necessarily
what
I
think
are
most
important
to
the
community
and
I'm
curious.
If
people
have
ideas
about,
how
do
we
decide
like
I
may
not
be
the
best
capo,
whether
right?
What
are
the
improvements
that
are
gonna
make
backrub
best
for
the
largest
number
of
people.
A
Yeah
I
struggle
with
that
too
I
mean
I
feel
like
you,
you
are
a
member
of
the
backed
up
community.
A
So
that's
something
that's
important
to
you
is
valid
in
the
same
way
that
I'm
important
me
a
salad
but
I,
don't
know
if
you
know
your
perspective
is
more
valid
than
mine
or
vice-versa
right,
like
that's
really
hard
to
gauge,
and
with
that
without
having
like
hundred
voices
to
all
like
back
behind
you
or
me
or
whatever,
that's
that's
hard
to
count,
which
I
think
is
that's
where
we
want
the
pmc
to
come
in
where
we're
like.
We
have
all
these
good
ideas.
A
A
We
also
previously
had
talked
about
scheduling
things
for
more
than
one
release
in
the
future,
to
which
we
had.
We
sort
of
vaguely
done
that,
but
not
specifically,
but
I.
Think
now
that
we
have
this
milestone
candidate
label.
That
might
be
something
where
it
would
be
easier
for
us
to
do
that
right
where
we
could
be
like
okay.
Well,
this
this
release
is
going
to
be
security,
focused
and
actually
gonna,
be
editorial
focused.
A
A
few
more
voices
in
conversation
do
a
point
but
yeah,
so
I
think
I
think
my
priority
right
now
would
be
focused
on
feature
parity
with
either
Drupal
7
can
trim
modules
that
we
wanted
for
things
like
reference,
and
you
know
files
over
things.
That
I
think
will
be
really
great
to
have
like
no
no
like
ban
something
but
I
also
don't
know
like,
because
we've
had
these
issues
like
failable
files
and
reference
and
core,
and
you
know
layout
relationships
if
that's
a
feature:
parity
with
Drupal
7
panels.
C
And,
in
all
fairness,
all
three
of
those
issues
relationships
fill
those
files
and
references
all
had
actually
a
lot
of
activity
and
a
lot
of
contributions
to
them,
but
they
got
held
up
on
just
like
the
complexity
of
the
problem,
space
and
where's,
my
guy,
it's
easier,
just
leave
it
in
to
Tribble,
or
something
like
that
like
that,
it
seems
to
be
more.
What's
happened.
It
hasn't
been
a
lack
of
code
or
backing
it's
just
been
like.
C
A
I
think
is
the
issue
is
the
giving
up
right
like
there
was
never
a
decision.
That's
like,
oh,
you
know
filled
full
files
is
better
than
contribu
little
files,
stinking
chipper
backdrop.
That
was
just
like
one
person
really
put
in
a
lot
of
effort,
and
then
it
missed
the
milestone
and
then
no
one
had
ever
worked
on
it
again,
since
so
I
think
it's
it's
like
we
need
to.
We
need
to
figure
out
like
if
this
is
really
important.
Let's
you
know,
let's
get,
let's
assign
some
responsibilities
like
Jen.
D
I
think
like
addressing
that
question
of
how
to
unstick
issues
that
that
there
was
momentum
behind
the
got
stuck
is
important.
It
also
ties
into
the
like
setting
priorities
like
what
what
does
it
mean
to
set
a
priority
and
I'm
thinking?
An
example
is
we
had
a
successful
sprint
day
recently
right,
and
that
seemed
like
something
worth
repeating,
and
so
maybe
one
way
we
help
unstick
issues.
D
A
Print
is
the
right
place
for
a
hard
problem.
I
feel
like
a
sprint
is
a
great
place
to
get
a
whole
bunch
of
little
things
done,
but
for
the
kind
focus
that
you
need
to
work
on
a
big
hard
problem
like
that
you
need
to
be
uninterrupted
and
a
sprint
is
the
kind
of
place
where
you're
gonna
be
interrupted,
so
I
mean
I,
don't
know
if
we
can
dedicate
be
like
hey
everybody's,
been
working
on
faster
up
this
day.
A
Maybe
let's
not
interact
with
each
other
okay,
so
the
one
person
working
on
the
hard
problem
can
or
we
could
have.
You
know
some
kind
of
focus.
That's
like
that.
It's
like
okay,
like
we're
all
here
to
help
you
know,
help
deaf
well,
not
with
whatever
it
is
that
he's
working
on,
but
we're
not
gonna
like
ask
anything-
and
you
know
we're
just
we're
here
to
test
the
stuff.
A
If
you
have
a
poor
brush,
you
want
tested
we're
here
to
do
it,
but
you
know
the
rest
of
the
people
didn't
do
themselves
with
other
stuff
right,
so
it
would
be
like
committed
to
supporting
the
person
who's
doing
the
hard
problem,
but
not
bothering
them
that
what
else
would
be
really
good
too
so
I,
don't
know
where
the
balance
is
there.
You
just
got
a
guy
I
guess.
D
That'll
make
sense,
I
mean
if
a
sprint
isn't
the
right
way
right.
So
what
is
and
I
think
you
just
made
a
suggestion.
Another
you
know:
I
I
hesitate
to
go
this
route,
but
is
another
way
that
we
need
to
figure
out
some
way
to
to
raise
some
money
that
on
the
really
hard
problems
we
can
offer
about
the
or
hire
somebody
right
and
say
here's
a
really
difficult
problem,
and
and
and
maybe
the
solution
to
these
really
hard
problems.
It's
a
fundraising
campaign
or
you
know
a
Kickstarter
or
something
I,
don't
know.
Yeah.
A
D
A
I'm
not
sure
if
money
is
the
answer,
I
feel
like
the
problem
with
throwing
money
into
the
problem.
Is
that
you
and
you
decrease
everybody
else's
desire
to
contribute
if
they're
not
getting
paid,
if
one
one
person
is
or
small
group
people
are
but
yeah
trying
to
find
some
way
to
support
those
people
and
that
are
willing
to
do
the
hard
work.
I
think
is
important.
I,
don't
know
what
that
is.
B
A
The
next
release,
and
also
be
like
we're
all
here
to
support
the
one
person
on
the
hard
edge
you
and
I
think
if
we
can
do
that,
really
we're
not
gonna
bother
you,
but
if
you
have
any
right
thing,
you
need
to
test
it
or
anything.
You
want
to
bounce
ideas
off
of.
We
could
do
that
I
think
that's
worth
trying
and
seeing
we
can
make
that
work,
especially
in
a
remote
situation.
The
person,
if
they
don't
wanna,
be
bothered
they
can
like
disappear
from
Gitter
for
a
while
right.
A
D
A
A
Like
a
bit
like
that,
MailChimp
sign
up
checkbox
I
took
four
of
us
something
this
week,
yeah
that.
D
Almost
something
the
other
thing
I
just
want
to
you
talk
about
the
security
release
and
to
me
like
that,
might
be
fundamentally
a
really
important
thing.
There
might
be
huge
gaps,
maybe
but
personally,
like
it
sounds
really
unexcited
to
me,
because
I'm
not
perceiving
security,
to
be
a
big
problem
right
now.
It's
like
you're.
A
Individual
IP
addresses
or
rageous
or
whatever,
and
so
I'm
trying
to
say
like
these
are
like
pain
points
we
can
solve.
If
we
did
a
security
bug
Chili's.
There
are
definitely
some
things
in
there
that
it's
like
not
very
exciting
but
I.
Think
there's
also
like
I
agree
with
you
that
we
should
not
do
a
release.
That
does
not
have
any
exciting
features
in
it
for
everyone,
but
that
doesn't
mean
we
can't
do
like
a
security
release.
We're
like
two
things:
you'll
benefit
from
and
three
things
you
don't
really
understand.
E
Yes,
so
they
I'm
working
yeah,
so
yeah
it's
hard
to
say
so.
There
are
so
many
fields,
and
you
know
if
you
could
ya
make
something
need
something
and
yeah
I
sometime
thing
would
be
good
to
get
new
people,
however,
and
it
don't
have
to
be
so
many
people
I
think,
because
my
impression
is
that
developing
bedrock
is
much
easier
than
the
helping
Drupal
8,
where
the
last
futures,
for
example,
for
Drupal,
8.7
I,
don't
know
if
you
read
the
blog
post,
so
they
wrote
for
this
feature
which
now
got
stable
into
core.
E
They
worked
128
people
for
a
long
time
and
I
think
if
we
had
5
people
more,
we
could
do
a
lot
of
things.
We
don't
need
hundred
people,
it
could
be
nice,
but
I.
Think
developing
for
petropia
is
quite
easy
in
comparison
and
yeah.
So
maybe
it
would
also
be
an
idea
to
to
talk
with
people
and
ask
them
that
they
want
to
do
something
so
talk
with
individual
persons.
E
D
I
think
to
tie
that,
to
the
having
set
priorities
right
is
that
there
are
people,
I,
think,
there's
a
lot
of
people
who
will
help
if
you
just
ask
them
right
and
if
you
have,
if
we've
defined
a
priority-
and
we
know
oh,
this
person
is
good
at
that.
They
can
help
us
with
that.
Then
we
have
a
specific
request:
hey
can
you
help
us
with
that
and
that's
harder
to
do
when
you
don't
have
priorities
right,
yeah?
C
You
know
somebody,
that's
that's
championed
it
in
the
past
that
basically,
just
you
know,
got
stuck
on
something
basically,
there's
the
will
to
review
or
community
buy-in
or
whatever
it
was
find,
the
ones
that
have
high
likelihood
of
you
know
getting
contributors
working
on
those
things,
and
then
saying
you
know
this
is
a
combination
of
we
have
the
the
will
it's
their
us.
We
think
that
it's
also
valuable
and
then
make
the
list
that
way.
Then.
E
A
Jonathan
tiger
hurt
also
did
a
bunch
of
work
on
feelable
files
and
he's
been
looking
for
ways
to
contribute
to
backdrop
lately.
That
might
might
be
good
to
get
him
back
in
on
that
one
too.
If
we
have
too
many
days
of
scientist
comma
but
yeah.
Let's
do
that.
Let's
run
through
this
list.
I
like
this
idea
and
I
also
like
this
idea
going
forward
where
we
feel
like
these
are
the
things
that
we
have
patient
people
that
are
passionate
about
we're
going
to
work
on
them.
A
These
are
the
people,
so
we
have
a
pairing
of
those
and
we
put
that
on
the
agenda
for
the
next
release.
So
now
it's
the
PNC
they'll,
say
yeah
that
sounds
great
or
no,
it
doesn't.
And
then,
if
that
person
doesn't
have
time
that
release,
we
can
bump
it
to
the
next
one.
So
we're
not
like
Jen.
A
You
have
to
do
this
by
whatever
date
or
like
chocolate,
whatever
it
is,
make
it
be
like
you're
responsible
for
this
issue,
but
you're
not
obligated
to
it,
but
then
that
way,
I
think
people
will
don't
feel
good
about
the
responsibility,
but
they
won't.
Hopefully,
they
won't
feel
too
much
pressure
from
the
obligation
and
if
they
can
say,
I
definitely
am
NOT
gonna
have
time
in
the
next
four
months.
We
can
schedule
it,
it
doesn't
really
factor
and
see
if
there's
a
way
to
make
that
work.
A
C
A
C
D
C
Like
that,
Chester
is
Gregory,
okay,
so,
let's
start
so
at
the
top
of
the
lists
based
on
the
way,
this
has
been
organized,
which
is
somewhat
haphazard,
but
we've
got
the
list
of
scary
items
your
first,
the
top
one
we
have
is
package
signing
issue
1992,
in
which
this
was
something
that
we
actually
had
a
chance
of
making
in
113
that's
been
bumped.
Our
advocate
is
John
Franklin,
it
seems
like
we've
got
the
resources
in
the
will
necessary
to
make
this
one
happen
in
the
near
future.
So
that's
a
good
candidate.
C
Do
we
want
to
go
any
further
than
that?
I
think
that's
enough
information
thing
trusted
host
patterns
issued
2568
Gregory
closes
our
advocate
for
this
one
again
like
something
that
could
have
actually
been
put
into
113,
but
but
got
bombs,
so
another
good
possibility
there.
Although
a
trusted
host
patterns
is
hardly
going
to
be
a
banner
feature
for
any
version,
just
whatever
gets
at
it.
It's
like
a
nice
to
have
not
really
a
killer,
feature
honeypot
and
core
issue.
C
D
Can
I
suggest
something
here
quickly
which
an
advocate
like
I
could
add
me
an
advocate
for
one
of
these
issues,
but
if
I
were
that
doesn't
mean
I'm
gonna
solve
it
yeah,
but
it
might
mean
that
I'm
gonna
adopt
it
and
I'm
going
to
promote
it,
and
you
know,
try
and
help
recruit
somebody
and
if
I
can't,
then
you
know
say
that,
like
hey,
I've,
tried
I
mean
an
effort,
we
we
don't
have
anybody
right
now.
So.
D
Just
throwing
that
out
there
there
might
be.
You
know,
I,
don't
know
John
Franklin
well
right,
but
maybe
he
is
the
technical
person
to
get
something
done,
but
he
needs
an
advocate
to
work
with
him
right
to
sort
out
like
it
pushed
the
issue.
So
this
kind
is
distinguished
between
the
person
who's,
maybe
going
to
do
the
hard
work
that
they
may
not
actually
be.
The
advocate
for
the
issue
right.
Maybe
the
Advocate
is
Gregory
or
I,
who
are
are
just
sort
of
helping
them
out
and
removing
roadblocks
or
or
representing
that
issue
with
meetings.
D
C
D
If
I'm
the
technical
person
that
stuck
you
know,
I
might
actually
appreciate
somebody
just
coming
back
asking
me
how
it's
going
right.
Well,
what
can
we
do
to
help
so
I'm
part
of
what
I'm
trying
to
do
is
like
say:
I
I
might
be
an
advocate
for
one
of
these
that
encouraged
me,
like
honeypot,
I,
think
back
up
in
my
grade
or
SMTP,
but
if
I
cook
that
on
it
would
be
like
okay
I
will
try
to
work
with
somebody
else.
Who
can
do
that
hard
work
because
I
can't
I'm,
not
the
one
who's
gonna.
D
B
D
B
B
C
Yeah,
let's,
let's
keep
rolling
I,
think
Terry
Louis
is
gonna,
take
forever
so
honeypot
in
coral
1169,
gem,
possibly
saying
maybe
something
in
here,
but
there's
no
obvious
candidate.
Looking
through
the
issue
there.
If
somebody
that's
like
pushing
hard
on
it
to
the
point,
they've
actually
written
some
code
or
call
it
up
for
months
or
anything
like
that.
Like.
D
I
say
I
would
take
one
of
these
and
then
like
be
an
advocate
for
trying
to
find
somebody
like
use,
Twitter
and
other
things
and
say:
hey
I'm
really
trying
to
get
this
into
core.
Can
you
help
me,
but
I
don't
know
if
honeypot
is
the
one
I
should
take,
it
seems
like
it
might
be
a
good
one,
because
it
seems
like
an
easier
you
see
compared
to
some
of
the
others.
Yeah.
C
I
I
wonder
like
for
something
like
this,
where
we
don't
have
somebody
obvious
already
like.
Maybe
we
need
to
evaluate
like
even
if
we
had
an
advocate.
Would
this
be
one
that
we
chose?
You
know
Jeff,
so
maybe
we
shouldn't
be
chasing
down
advocates
for
issues
that
we
might
not
think
are
high
priorities
anyway,
I
I'm
a
little
bit
wofully
on
honeypot,
my.
A
D
A
C
A
C
So
yeah,
let's
keep
moving
on
these
anyway
ban
IP
addresses
issue
1878,
we
removed
ban
capabilities
in
a
very
early
version
of
backdrop.
Actually,
backdrops
focus
has
changed
a
lot
since
then
actually
like
when
we
were
first
doing
that
we
were
just
like
stripping
out
everything
from
Drupal
7
that
nobody
used
or
that
was
less
commonly
used
less
than
the
8
percent
use
yeah.
C
Another
performance
impact
to
it
was
like
the
very
first
query
that
Drupal
did
before
I
did
anything
was
checking
the
band
table
so
anyway,
1878
again
like
possibly
spam,
like
prevention,
looks
like
actually
enthusiasm
for
ban
itself.
Is
you
know,
there's
some
there,
but
people
are
more
interested
in
having
something
to
automatically
bans,
something
that
was
a
little
bit
more
proactive
and
maintenance.
Free
I
saw
Jason
post
a
comment
recently
that
they
actually
have
a
clients,
auto
band
module,
developed
by
hope,
42
that
could
potentially
be
ported
for
kind
of
achieving
that
purpose.
C
I
imagine
like
most
custom
things,
though
it's
probably
very
targeted,
like
you
know,
if
you
like
certain
URLs,
like
a
really
good
one,
just
like
WP
admin
like
on
a
site.
That's
clearly
not
WordPress,
you
know.
If
that
happens,
five
times
then
banned
the
address,
something
like
that
they
probably
end
up
with.
C
So
we
don't
have
any
clear
takers
on
that,
although
the
discussion
there
is
is,
is
active
and
engaging.
So
you
know
there's
the
potential
for
enthusiasm.
It's
also
like
the
actual
problem.
Space
of
banning,
especially
with
the
flat
IP
address
list,
is
not
challenging.
You
know,
and
it's
easy
to
create
a
module
that
achieves
that
basic
purpose.
C
A
C
A
C
C
D
A
C
I
feel
like
for
something
from
this
we're
really
pretty
much
any
feature
like.
We
should
really
only
be
adding
it
to
core
if
we
think
that
it
should
be
turned
on
by
default.
Yeah
you
know,
and
because,
if
it's
something
you
turned
on
manually
later,
well
we're
not
helping
people
in
the
out
of
box
experience,
and
it
would
would
be
just
as
well
that
it
was
entered
module.
In
that
case,
let.
A
Me
put
it
I
think
we
need
a
more
discussion
around
it.
I
was
just
thinking
if
we
can
protect
people
out
of
the
box.
That
would
be
better
and
then
Timothy
w6.
We
don't
want
it
songs,
giveaway
to
turn
it
off.
I
think
that'd
be
fine,
but
if
we
don't
think
the
majority
people
would
feel
like
they
were
being
protected
if
we
think
they
were
feel
like
we
were
interfering
with
this
approach.
Okay
to
them.
That
would,
but
it
was
only
tagged
recently
so
I
think
it
needs
more
discussion.
Well,.
D
A
good
solution
is
to
provide
a
good
alternative
to
put
in
your
email
in
the
body
field
right
so,
for
example,
multiple
contact
forms
like
if
you
have
one
of
the
places
that
emails
show
up
a
lot
is:
there's
fines
to
have
people
at
the
site
and
they
want
the
user
to
be
able
to
contact
any
of
the
five.
So
they
put
all
five
of
their
email
addresses
there.
A
A
Email
addresses
in
the
body
field
as
long
as
BOTS
can't
read
them
in
humans
can
ya
the
day
right,
but
I
think
there's
a
use
case
for
both
we're
like.
Maybe
you
have
a
comment,
forms
and
thinking?
Are
you
a
web
form
or
something?
And
you
want
that
protection
there?
That's
totally
fine
contact
forms
are
sometimes
problematic.
Like
me,
user
experience
standpoint
where
it's
like,
okay,
like
yes,
it's
better
to
have
people
fill
out
the
form,
but.
A
You
just
want
to
click
a
link
and
like
take
an
email,
so
I
think
both
are
valid.
I
think
it's
just
what
we
don't
want
to
have
is
have
like
put
in
something:
that's
gonna
hurt
people
right
like
we
can't
make
the
email
I
just
hidden
until
you
like
click
on
it
or
something,
but
it
just
needs
to
look
like
it
always
looks,
but
then,
like
boss,
can't
find
it
or
only
really
smart
BOTS
can
find
it
stuff
like
that.
Okay,
oh
yeah!
Anyway,
let's
talk
about
it
in
the
issues.
I
think
there.
C
A
B
C
C
Them
all
tore
the
hell
out
of
the
user,
login
form
or
like
just
like
rip
out
the
important
thing
entirely
and
use
something
completely
different,
because
it's
just
like
what
port
provides
right
now,
it's
just
so
focused
on
the
normal
user
name/password.
The
combination
that
it's
it's
difficult
to
hook
into
in
any
way
and
some
DP
module
and
core
issue
$31.99.
A
This
is
also
a
little
tricky
because,
in
order
to
use
it,
you
have
to
use
an
external
service,
so
basically
be
like
putting
like
a
thing
in
that's
unusable
on
its
own,
but
it
because
it's
so
common
that
people
have
their
websites
on
a
different
machine
than
their
email.
These
days
like
if
they
apply
Google,
managing
their
mail
or
whatever,
it's
pretty
common,
that
your
backup
site
can't
deliver
mail
without
it.
So
when
I,
like
I,
feel
very
conflicted
about
that,
one
yeah.
C
And
this
has
been
covered
in
that
issue.
There's
been
some
discussion
about
like
getting
different
email
concepts,
all
mixed
together
about
like
my
mail,
HTML,
mail
and
SMTP
and
I
think
I
think
it's
been
covered
in
the
issue.
That's
we're
definitely
just
talking
about
the
problem
of
delivery.
That
is
the
issue
that
we're
facing
that
any
email,
server
or
any
web
server
today.
Basically,
it's
impossible
to
get
it
into
people's
inboxes
without
using
a
service.
C
It's
a
thing
that
we
should
be
focused
on
or
that
with
that
we
want
to
have
focus
on
then
then
this
is
almost
a
requirement,
but
yeah
we
wouldn't
I,
don't
think
I,
don't
think
we
would
cater
towards
any
one
provider
or
another.
It
just
be
like
you
know,
configure
email
server
by
the
extent
of
what
I'm
imagining
is
basically
like.
You
know:
checkboxes
use,
built-in
email,
server
use,
SMTP
server
like
what's
your
server
username
and
password
like
when
and
that's
that's
kind
of
it.
C
D
An
example
where
I
think
I
could
find
I
could
recruit
somebody,
a
colleague
or
somebody
to
help
me
work.
That's
I,
wouldn't
do
it
myself,
but
I
think
you're
right.
It's
pretty
simple.
It.
A
Is
that
backdrop
chord
doesn't
handle
more
than
one
male
handler
at
a
time
right,
so
I
think
we
need
to
solve
that
problem
too,
so
it
can't
get
a
little
messy
your
neck,
like
so.
The
way
SMTP
works
is
just
like,
oh
of
course,
use
mine,
but
there's
a
bunch
of
other
stuff,
like
HTML
mail,
looks
like
throw.
What
I
was
currently
is
to
use
nine,
and
if
you
try
and
use
these
two
things
together,
like
I,
want
to
send
the
HTML
email
securely
it.
C
A
C
Exactly
so,
I
needed
the
complex
situation
of
multiple
systems.
All
time
together
then
contribute
could
basically
continue
doing
what
it's
doing
right
now,
but
out
of
the
box,
we
would
provide
an
SMTP
and
alert
and
then
provide
an
option
in
the
UI
French
return
it
on
the
the
mail
system.
Right
now,
one
of
the
most
unfortunate
things
is
its
user
interfaces.
Just
like
it's
so
confusing.
A
C
C
C
C
I'd
be
concerned
about
this
back
of
my
great
is
that
its
library
that
uses
as
far
as
I
know
is
kind
of
huge,
because
it
it
doesn't
use
like
my
sequel
dump.
It
like
manually
runs
everything
through
PHP
like
selecting
stuff
out
of
the
table
and
then
writing
it
into
a
dump
file,
because
they
think
that
at
the
time
what
was
written,
it
probably
still
is
the
case
today.
You
couldn't
assume
that
my
sequel
dump
was
accessible
on
the
server
or
that
the
database
system
even
was
my
sequel,
we're
in
a
slightly
better
situation.
C
A
A
C
A
C
C
E
E
A
A
Push
this
button
and
I
think
that
if
we
have
something
in
court
that
handles
the
backup
anyway,
it
would
probably
be
pretty
easy
to
provide
a
user
interface
that
has
that
button
on
it
and
I
think
that,
whether
it's
database
and
configure
just
database
or
database
files
config
whatever
that
functionality
I
think,
would
cover
the
80%
of
what
the
control
people
and
we
could
stop
there
in
terms
of
backup.
Oh
my
god
like
it,
doesn't
have
to
be
backup
a
migrating
module
in
core.
A
You
can
just
be
like
what
is
this
one
feature
that
everybody
needs
that
they're
installing
this
module
for
and
then
that
can
grow
to
like
once
we
get
that
and
then
we
realize
that
back
and
migrate
is
still
our
number
one
module
really.
But
what
else
do
they
need?
It
doesn't
have
to
all
go
anyone's.
So
we
can
start
with
like
first
backup
before
you
do
an
automatic
update.
C
C
C
A
Would
like
to
back
that,
because
I
have
a
ton
of
sites
these
panels
in
Drupal,
7
and
moving
them
to
backdrop
is
gonna
be
hard
without
this
feature.
I
think
that,
like
most,
you
there's
workarounds,
you
can
do
by
using
like
contextual
filters
and
like
creating
blocks
that
hard-code
a
relationship
and
then
placing
like
well
if
these
get
view
and
I
thought
of
a
block.
But
it's
not
ideal
and
I.
Think
if
we
had
this,
even
if
the
UI
is
tricky.
C
C
But
as
it
is
right
now
is,
actually
it
doesn't
even
do
these
are
interface
and
I.
Think
that
might
be
my
design
yeah
by
design
and
also
where
this
issue
got
potentially
tied
up
is
I
posted
some
screenshot.
So
it's
like
here's
some
ways
that
we
can
make
this
happen
like
that
would
be
super
awesome.
Super
awesome
and
hard
like
that.
You
know
dynamically
adding
relationships
rather
than
adding
them
upfront,
which
would
be
very
cool
like
if
you
could
just
add
them
on
the
fly.
C
Well,
maybe
we
should
see
which
way
it's
more
manageable
and
then
start
there
I'm
at
a
time,
I
need
to
leave
okay,
I
kind
of
think,
maybe
that
we
have
yeah.
We
should
put
a
pen
in
this
and
come
back
to
it
next
week.
We
still
have
you
know
the
next
week
will
be
focused
on
1:13
anyway.
The
next
meeting
will
actually
be
the
day
after
1:13
is
released.
So
we
can,
you
know
pop
the
champagne
and
celebrate
our
accomplishments
and
then
stress
out
about
what
we're
going
to
do
next.
I.
C
A
C
C
Let's
keep
cracking
on
the
bug,
fixes
for
112
7
and
those
last
couple
of
items
for
113
and
we'll
do
what
we
can
and
the
next
week.
So
I
will
be
doing
the
release
on
Wednesday,
okay,
I
think
because
of
some
scheduling
eleven
upcoming
later
of
the
day,
but
yeah
we'll
coordinate
that
if
we
have
get
her
and
make
a
mission
get
out
and
start
scheduling
it
and
do
all
of
that
jazz.
So
alright,
that's
it!
So!