►
From YouTube: Backdrop Weekly - May 2nd
Description
Today’s development agenda: http://bit.ly/2ZC6KIj
A
All
right
we're
on
air,
it
is
Thursday
May
2nd-
and
this
is
a
meeting
usually
reserved
for
all
of
the
active
work
we
have
going
on
for
backup
core,
but
because
yesterday
was
May
first
and
that
was
code
freeze.
We
did
a
ton
of
stuff
recently
and
I'll
go
through
that,
but
we
are
dropping
a
lot
of
other
stuff
on
this
agenda
because
we
have
more
exciting
things
to
do
today.
She'll
get
to
later,
alright,
so
starting
off
with
what
was
merged.
Recently,
we
had
a
fix
to
the
translation,
Pio
files.
A
A
We
have
a
one
issue
remaining
I
think
about
right-to-left
issues
in
ckn,
or
at
least
one
of
the
four
requests
that
poem
for
us
is
currently
marked
means
for
you,
I
think
I
originally
wrote
it
and
then
Gregory
fix
something
that
I
hadn't
gotten
right
and
so
great
great.
If
somebody
else
could
review.
A
Gregory
and
myself,
that's
issue
number
35
over
four,
and
then
this
is
one
that
I
would
love
to
see
get
in
sooner
rather
than
later.
Is
that
right?
Now,
if
you
have
the
security
release
for
back
drop
core
and
you
are
running
back
drop
111,
there
is
a
secure
version
of
ectric
111
for
you,
but
your
website
will
still
yell
at
you
as
though
that
version
is
not
secure
because
it
expects
there
to
be
only
one
reaching
the
secure
version
instead
of
two.
So
this
comes
from
our
switch
to
semantic
versioning.
A
It
wasn't
written
for
that,
but
we
need
to
make
it
so
that
it
is
that
issue
in
the
queue
is
number
35.
24,
there's
no
pork
west
there
yet,
but
it
does
look
like
there's
an
outline
in
the
issue
for
what
the
code
should
do.
If
anyone
is
interested
in
writing
that
and
those
are
all
of
the
high
priority
issues
we
have
slated
for
the
bug
fix
release
112
seven
that
will
coincide
with
a
big
release
113.
A
But
of
course
there
are
a
gazillion
other
bug
fixes
that
could
use
review.
They
are
all
in
the
1
or
12
7
milestone
and
the
way
that
it
works
to
get
above
fixed
release
slated
for
a
milestone
is
it
needs
to
have
a
pore
request
on
it
and
as
soon
as
that,
bug
fix
has
a
flaw
request
on
it.
That's
in
a
testable
format,
then
you
can
add
the
milestone
or
anyone
can
add
a
milestone
for
the
next
bug
fix
release.
A
So
only
the
only
issues
that
should
that
don't
have
pork
press
that
are
tech
for
a
milestone
are
ones
that
we
have
deemed
significantly
important
and
a
good
example
of
that
one
is
this
one
that
will
allow
multiple,
equivalent
security
releases?
So
it's
important
to
note
that
all
right,
so
items
for
113,
nice,
I'm,
so
excited
I
can
tell
dashboard
got
merged.
That's
issue
number
four
and
I
knew
that
right.
A
So
that
was
something
that
was
sitting
in
a
needs
test
State
for
a
very
long
time
and
Nate
took
it
over
this
weekend
to
start
doing
a
code
review
and
he
was
like,
oh
my
god,
the
code,
it's
a
mess
and
so
I
think
our
takeaway
from
that
is
that
we
should
do
code
reviews
earlier
just
getting
more
eyes
on
the
cone.
There's
good
in
there's
a
couple
of
reasons.
A
The
code
was
a
mess
number
one
I
wrote
it
all
for
Drupal
and
I
had
introduced
several
issues
that
had
never
been
noticed
in
the
Drupal
version,
which
I
will
now
go
and
fix.
Now
the
native
code
view
my
Drupal
module,
but
some
of
the
other
ones
were
just
left
over
from
the
fact
that
when
doc
won't
want,
I
think
first
wrote
this.
He
just
wrote
it
as
a
proof
of
concept.
He's
like
hey
look,
you
can
take
this
Drupal
Mon
will
turn
it
into
a
backdrop:
module
isn't
that
great
and
it
almost
like?
A
A
Maybe
we
should
use
those
for
putting
new
stuff,
so
it
wasn't
really
that
it
was
a
mass
so
much
that
like
we
just
could
do
it
differently
and
Sony
took
some
time
this
weekend
to
kind
of
reformat
it
and
make
it
more
backdrop
friendly,
and
so
he
did
that
and
then
at
some
point
there
was
a
magic
test
ferry
that
showed
up
and
read
a
bunch
of
tests
for
it.
My
theories
that
it
might
be
jonathan,
dagger,
heart
cuz,
he
was
writing
tests
during
the
sprint.
A
A
He
did
a
couple
of
things
to
the
tests
like
switched
it
from
running
regular
profile
to
running
the
testing
profile,
and
then
he
kicked
it
over
to
me
once
the
tests
were
written
but
failing
and
then
I
was
able
to
go
through
and
sort
of
fix,
all
the
tests
they
weren't
failing
and
then
together.
Last
night
we
helped
iron
out
a
couple
of
unrelated
test
failures
like
with
module
installation
or
the
administrative
pages
or
whatever
else
so
I
think
we
got
all
of
the
tests
passing
booboo
right
around
10:00
p.m.
A
so
we
didn't
quite
make
our
9:00
p.m.
East
Coast
cutoff
time,
but
because
we've
been
putting
in
so
much
work
on
that
module,
I,
think
sort
of
even
on
Friday.
Last
week
he
decided
that
was
fine
and
rich
in
any
way
and
that
we
had
dinner
at
10:30
yeah,
because
we
were
trying
to
get
that.
But
I
thought
that
was
ok
sacrifice.
There
were
a
bunch
of
people
on
chat.
At
the
same
time,
Gregor
was
offering
to
like
review
stuff
for
us,
which
was
really
great.
So
thank
you.
A
Everybody
for
jumping
in
and
helping
us
get
those
last
few
issues
sorted
out
now
it's
in
it's
not
perfect.
We
have
15
days
to
perfect
it,
so
anyone
wants
to
pull
down
or
clone
the
latest
version
of
that
report
and
give
it
a
test.
We
have
time
to
find
and
fix
any
other
issues
that
may
come
up.
If
there
is
weird
stuff
on
the
dashboard,
you
know
find
useful.
We
could
take
it
off
if
there's
other
things
on
the
dashboard
that
you
would
want
that
are
more
useful.
A
We
can
create
some
tests,
so
those
people
in
the
next
release
we
just
sort
of
need
to
get
an
idea
of
what
it
is.
People
want
on
their
dashboard,
I
went
and
did
a
quick,
so
WordPress
I've
got
a
clone
of
Joomla,
but
I
haven't
set
it
up,
but
I
would
love
to
get
some
sort
of
more
comparisons
to
other
things,
they're
out
there
and
make
sure
love
writing
thanks
for
useful,
so
yeah,
hey,
dashboard,
there's
a
couple
of
other
things
that
went
in
in
113
as
well.
A
We
had
an
issue
for
field
floor
matters
that
were
available
in
Drupal
6
that
were
trapped
in
Drupal
7,
and
we
have
put
back
into
backdrop
in
particular,
when
you
have
a
taxonomy
term.
You
cannot
have
like
a
comma
separated
list
of
tags,
rather
than
just
I
would
look
at
stacks
list
of
the
way
triple7
you
normally
on
that
scale
to
their
elephant,
go
in
separate
divs,
and
so
this
came
from
a
contributing
in
Drupal.
Well,
in
fact,
if
also
in
Drupal
7
called.
A
The
something
what
matters
field
formatter
settings,
but
because
that's
it
can
triple
for
backdrop
as
well
as
for
Drupal.
We
need
to
include
the
upgrade
path
just
like
we
said
we
would
and
document
the
fact
that
this
contribute
much
less
will
merge
into
core
and
that
the
great
process
will
be
handled
by
floor
for
you.
So
there
is
a
follow
up
issue
for
that
one.
It
is
numbered
3742
to
get
that
a
free
class
story
about
and
that
one
needs
to
get
done
before
113
is
released.
A
Another
one
that
was
merged
is
getting
translatable
strings
to
find
for
all
core
config
files.
So
this
is
number
34,
55
I
think
herb
does
a
bunch
of
work
on
that
and
it
was
able
to
get
that
reviewed
and
merged
in
last
night,
and
then
there
are
a
couple
of
other
things
on
the
radar
here
that
went
in
that
weren't
necessarily
on
our
agenda
every
week,
but
we
got
vertical
tabs
added
to
the
text.
On
the
term
page,
we
got
an
entity
access
API.
A
So
this
is
something
that
entity
access
function
was
added
by
entity,
API
module
in
Drupal
7,
but
had
been
missing
from
backtrack.
So
we've
got
that
mountain
course
or
basically
making
it
backed
up
or
more
important
to
the
Drupal
7
entity,
API
module,
which
is
going
to
make
upgrading
easier
and
there's
a
ton
of
other
stuff.
A
If
you
want
to
check
the
issue
checker
for
113
0,
you
can
say
I
think
there's
four
tasks
we're
meeting
and
we
can
get
in
before
code,
freeze,
freeze
before
release,
see
and
everything
else
has
been
bumped
to
the
either
the
next
milestone.
If
there
had
been
activity
on
it
recently
or
if
there
hadn't
been
any
active
activity
on
it,
since
the
last
major
version
or
minor
version
of
active
came
out,
it
got
bumped
entirely,
but
I
did
add
the
milestone
candidate
on
to
anything
that
has
been
in
a
milestone.
A
A
I,
think
doc
will
not
came
up
the
idea
recently
to
help
us
figure
out
what
should
be
a
priority
for
that
report,
and
rather
than
just
talking
about
it
by
ourselves
in
this
meeting
every
week,
we
thought
it
would
be
really
good
to
make
this
a
more
open
process
for
anyone.
Who's
working
on
backdrop,
contagion
issue
as
being
something
that
they
think
is
the
priority,
and
as
long
as
multiple
people
agree
that
this
issue
is
a
priority,
we
can
put
it
onto
our
list.
A
What's
another
one
in
case,
anyone
wants
to
have
a
look.
Oh
good
needs
back.
A
C
Well,
one
thing:
I
wanted
to
woo
we're
hooked.
Kevin
was
a
entity
access
which
is
probably
the
last
item
that
you
guys
just
talked
about
the
big
things
to
moonray,
who
basically
single-handedly
put
all
that
together
and
then
we
just
kind
of
made
minor
adjustments
over
the
intervening
months
to
get
that
completely
ready.
So
that's
that's
very
exciting.
That's
a
nice
helpful
thing
that
could
help
move
forward.
Our
references
work,
so
that's
very
exciting.
Yeah.
A
I
think
I
also
ran
into
an
issue
with
that
recently
in
Drupal
7,
where
they
didn't
have
an
enemy
access
function.
So
I
had
to
essentially
copy
the
enemy
access
function
out
of
the
entity,
API
module
and
put
it
into
the
module
that
I
was
using
because
I
needed
to
do
that.
So
just
the
fact
that,
like
that's
so
necessary
for
contributing
in
copies
of
that
function,
I
think
is
gonna,
be
really
any
Purbeck
drop
could
trip
to
all
of
it.
C
C
We
can
continue
following
up
like
we
put
in
that
initial
issue,
but
really
as
far
as
end-user
experience
like
there's
nothing
new,
because
we've
had
the
translatable
strings
and
config
files
for
all
of
one
well,
oh,
this
will
make
it
so
that
113
actually
has
some
files
that
that
use
it,
but
still
the
end
user
experience
is
going
to
be
the
same
and
translator
experience
is
going
to
be
the
same
until
the
PIO
2x
mantra.
Look,
it's
updated!
C
A
C
A
A
So
I,
don't
think
anyone
has
done
any
homework
on
this,
except
for
me
because
it
didn't
tell
anyone
that
it
was
time
to
do
it,
but
I
did
review
a
handful
of
the
issues
that
were
typed
with
this
label
and
I
noticed
a
sort
of
a
pattern
where
there
were
a
lot
of
issues
around
security
that
I
thought
might
be
wheat.
This
might
be
a
good
opportunity
to
make
a
focused
release.
A
These
are
modules
that
help
prevent
spam
bots
from
putting
comments
and
locking
registers
on
your
site,
BAM
also
prevents
up
like
a
sort
of
a
brute
force
attack
to.
If
there's
like
one
IP
address,
that's
like
come
on
your
site,
you
can
block
it,
which
could
be
nice
to
have,
and
then
two-factor
authentication
is
always
a
good
idea
for
security.
There's
been
an
issue
for
that:
an
email
abuse
cater.
This
is
something
where
one
of
my
organization's
that's
running.
A
backdraft
site
was
recently
targeted.
A
What
do
they
call
it
spear
phishing
where
they
went
to
the
website?
They
peeled
all
of
the
email
addresses
off
of
the
contact
form
and
they
crafted
an
email
that
looks
like
it
came
from
me,
as
the
president
of
the
organization
had
sent
it
to
every
one
of
the
members
of
the
board
or
the
snot,
but
asking
for
a
secret
behind
doors.
You
have
to
go
get
me
cash
parts
right
now,
operation
which
seems
super
shady,
and
the
only
reason
they
were
able
to
do
that
I
think
is
because
they
had
crawlers
out
there.
A
That
detected
like
here's,
a
page
full
of
email,
addresses,
and
so
there's
something
in
in
the
old
days
we
used
to
do
is
obvious,
get
all
of
the
email
and
just
as
he
put
on
websites
so
that
it
would
take
JavaScript
to
be
able
to
read
them.
A
foot
prevent
the
less
savvy
crawlers
from
noticing
their
emails
on
the
page
and
steal
your
email
and
spamming
you
now
it's
it's
a
higher
risk
of,
rather
than
just
them,
they're,
usually
not
very
specific,
targeted
attacks.
A
So
I
thought
it
might
be
good
to
revisit
that,
and
it
turns
out
there
was
already
a
quarry
she
created
for
adding
an
email
skater
they
mentioned
feature
parity
with
WordPress
WordPress
apparently
has
a
function
in
there
that
lets
them
do
it.
I
was
thinking
that
it
should
be
a
field
formatter
on
the
email
field,
but
when
I
thought
about
those
two
things
together,
look
there
was
a
handy
function
in
core
that,
let
you
you
know,
obviously
anything
we
could.
A
This
would
be
part
of
the
filter
system
that
converts
an
email
address
into
a
link
that
we
could
put
it
in
so
many
places
where
it
could
be
about
equal,
so
I
just
wanted
to
throw
that
out.
There
is
a
possible
item
for
our
next
release
and
then
the
last
one
on
this
list
was
SMTP.
This
is
a
module
that
will
have
here
a
backup
site
identity
for
sending
outgoing
mail
that
would
prevent
mail
sent
by
your
site
committing
having
people
spam
folders,
especially
if
the
site
is
running
your
website.
It's
not
the
site.
A
That's
running
your
organization's
email
does
require
third-party
integration,
so
you
would
have
to
choose.
Smtp
provider
sounds
a
little
bit
more
questionable
as
being
a
good
core
candidate,
but
I
do
wanna,
throw
those
all
out
there
as
potential
security
related
items
we
could
put
into
the
next
release.
There
are
also
a
handful
of
editorial
experience
items
that
did
not
make
the
113
release
I
thought.
A
If
we
were
gonna
do
focus
releases,
we
maybe
could
set
up
an
editorial
release
that
Michaelmas
114
and
we
could
put
the
things
that
didn't
make
113
like
save
as
draft
before
on
to
the
list
verb:
1
15,
if
114
was
going
to
be
security,
focused
so
there's
also
a
ton
of
other
interesting
issues
in
this
queue.
A
C
Well
and
I
I
do
always
think
it's
a
good
idea
for
us
to
look
through
our
previous
releases
and
see
which
features
we
have
prioritized
previously,
that
still
aren't
a
part
of
court
and
whole
ideas
from
there,
because
if
we
prioritized
it
once
it's
probably
important
and
if
it's
still
not
done
you
know,
it
just
means
we're
going
longer
without
some
kind
of
feature
that
we
thought
was
important
like
years
ago.
It
probably
still
is,
and
so
well.
A
A
B
D
A
So
this
is
the
milestone
candidate
for
the
next
minor
release,
which
would
be
for
114
115.
The
other
label
is
for
bug,
fix
release.
So,
generally
speaking,
any
bug-fix
issue
that
has
a
poor
request
can
be
assigned
to
a
milestone.
But
if
we
have
something,
that's
really
important
that
doesn't
get
before
request
that
we
still
think
it
needs
to
be
a
candidate
for
a
bug-fix
release.
A
good
example
is
the
supporting
multiple
equivalent
security
releases
that
one
doesn't
have
a
poor
request
on
it,
but
it's
really
important,
so
it's
typed
with
next
milestone.
A
And
I
did
go
through
all
of
the
bug,
fix
tags
and
make
sure
none
of
those
items
were
Marcos
features
just
before
this
meeting
and
if
they
were
I
reassign
them
to
the
minor
milestone.
So
they
should.
This
should
be
an
accurate
reflection
of,
but,
like
those
types
should
be
in
the
right
place
me
do
you
know
I'm
gonna
hub.
Is
there
a
way
to
get
an
easy
list
of
anything
that
had
been
previously
typed
with
a
milestone?
I.
C
A
A
A
All
I
did
is
take
all
of
the
issues
that
were
tagged
and
split
them
to
either
one
together,
so
nothing
should
be
lost,
but
the
amount
of
candidate
tag
in
general
we've
had
only
for
this
one
release.
It
came
out
like
right
after
the
last
really
stuck
one
one
said:
hey
shouldn't:
we
have
a
better
way
of
determining
priority.
This
is
the
person
reading
it
yeah.
C
So
I
think
that
between
now
and
next
week
we
should
go
and
collect
more
candidates
and
put
them
into
this
list.
Okay
abandon
we
should
I
might
better.
Maybe
we
should
have
the
PMC
not
necessarily
make
a
decision,
but
just
like
waiting
your
call
to
action,
saying
hey
I
mean
it
can
be
a
community-wide
actually
like
hey.
Why
don't
we
start
suggesting
milestone
candidates
for
the
next
thing
and
then
and
then
we
can
look
at
it
next
week.
A
B
But
this
is
going
in
at
it
in
that
direction
by
looking
at
what
people
have
already
talked
about,
as
opposed
to
just
like
what
are
setting
aside
what
we've
been
talking
about
in
the
past,
what
what
are
the
biggest
issues
were
facing
right
now?
You
know,
like
I've,
heard
a
lot
of
talk
in
the
last
couple
months
about
a
upgradability
right
and
we're.
So
if
we're,
if
we
were
picking
a
focus
or
something
where
am
I,
is
this
a
good
time
to
be
focused
on
that?
B
A
Would
be
the
ultimate
decider
on
that,
though,
or
you
are
one
of
the
other
poor
viewers,
because
if
you
look
at
an
upgrade
tap
and
you
decide
it's,
you
know
more
than
just
converting
variables
and
maybe
it's
a
big
deal.
It
needs
to
wait
for
a
minor
lease
that
also
could
happen
but
I'm
starting
them
all
office
bug
picture
leases
because
you
could
be
upgrading
today
and
you
want
that
fix
to
be
in
the
next
available
version,
so
yeah
some
of
them
might
be
really
hard,
though.
C
Yeah
I
get
what
you're
saying
Tim
that
that
you
know.
Maybe
some
of
the
things
we
want
to
prioritize
are
too
broad
for
an
issue,
or
maybe
just
they're
just
documented
in
an
issue
yet,
but
I'm
also
kind
of
thinking
that,
and
even
if
it's
really
broad
and
not
something
that's
actionable
through
code
or
something
that
we
haven't
discussed.
Yet
we
should
probably
have
an
issue
for
it.
C
A
Is
that
issued
to
him
is
that
I
have,
in
all
of
my
organizing
of
the
issue
case
and
I
did
set
up
projects
so
anything
that
I
found.
That
was
too
big
to
be
a
meta
issue.
There's
a
project
for,
and
there
is
specifically
one
project
for
an
upgrade
path
from
Drupal
7
there's
another
project
for
backwards,
compatibility
and
there's
one
for
turbo
feature
or
duplicate
feature,
parity,
WordPress,
feature
parity
and
then
some
other
random
things
like
breadstix,
editor
and
media
and
stuff
like
that.
A
Compatibility
and
upgrade
path
would
be
projects
that
I
would
recommend
you
take
a
look
at
I'm
gonna,
throw
a
link
to
the
upgrade
from
Drupal
7
1,
both
into
the
Gator
chat
in
the
group
chat
for
this
meeting,
but
that's
something
to
look
at
and
if
you
come
across
anything
else
like
this.
That
is
too
big
to
handle
this
issue.
I
would
encourage
anyone
to
use
the
project's
section
of
github
to
assemble
all
the
issues
that
we're
working
on
for
any
given
project.
Yes,
I.
B
Suggest
something
which
is
how
about
we
opened
up
I,
think
part
of
what
I'm
getting
at
is
a
lot
of
what
you're
talking
about
assumes
that
people
have
some
knowledge
of
the
issue
queue
and
what's
going
on
in
it
already
right
and
just
providing
some
opportunity
for
people
who
have
no
knowledge
of
what's
been
talked
about
before
to
just
say,
hey.
This
is
what
would
be
really
important
to
me
today,
yeah
just
to
get
it
out
there
right,
maybe
it
maybe
it
is
already
in
the
issue
to
you.
B
Maybe
there's
a
history,
but
not
everybody
knows
that
and
it
doesn't
have
to
be
binding
or
anything.
But
it's
just
sort
of
a
little
brainstorming
thing
and
this
could
be
done
outside
of
the
meeting
like
I
was
just
thinking.
Maybe
we
should
just
open
up
a
forum
topic
yeah,
one
topic
that
just
says
we're
about
to
start
a
new
cycle,
we're
preparing
for
release
1.14.
What
are
the
most
important
issues
for
you
drop
that
we
should.
A
B
A
I
think
it's
great
because
probably
if
those
people
don't
know
about
the
issue,
queue
they'll
either
be
mentioning
creative
issues.
For
that,
maybe
we
haven't
prioritized
that
we
need
to,
or
you
bring
up
new
things
that
maybe
we
don't
have
issues
soon.
We
need
to
capture
so
I
love,
I
love.
That
idea,
would
you
be
comfortable,
creating
not
belong
post,
okay,.
A
All
right,
well
me,
I,
don't
know
if
you
want
to
do
some
burning
of
old
issues.
I
know
a
couple
of
them
offhand,
like
our
field
to
profile
entity
bundles,
is
something
that's
kind
of
on
my
mind,
just
being
like
probably
important,
but
hasn't
got
any
attention,
and
then
there
was
something
else
too
that
I
think
had
been
on
a
reference
module
and
then
on
and
off
that
list.
You
know
so
just
figuring
out
like
how
to
get
how
to
get
those
things.
A
C
A
D
I,
don't
know
if
any
mentions
are
for
quite
the
color
schemes
in
Bates
has
thing
has
done
they're
pretty
for
peer
review
again.
Yes,
okay,.
E
A
Alright,
well,
if,
if
nothing
else,
then
let's
go
ahead
and
wrap
this
meeting,
we've
got
a
lot
of
warehousing
of
issues
and
wrapping
up
of
bug,
fixes
for
113
and
then
an
exciting
future
for
114
and
beyond.
So
thanks
guys
for
coming
in
this
meeting
thanks
mate
for
happening,
even
though
you
had
a
another
meeting
same
time
and
I
think
Tim
for
volunteering
to
open
up
the
conversation
in
life.