►
From YouTube: Backdrop Weekly Aug 10th
Description
Today’s development agenda: http://bit.ly/2u8Lqyk
A
A
A
A
A
B
B
C
C
Some
of
them
did
also
move
into
d8
and
I
know
this
like
code-wise.
There
might
be
a
lot
of
differences,
but
we
can
for
those
we
can
keep
up
at
least
feature
wise
sort
of
like
some
parity,
but
the
main
thing
is
security.
Security
fixes
are
being
followed
as
far
as
I
know.
It's
just
that
we
need
to
yeah
follow
up
with
fixes
and
new
features.
B
Yeah
great
idea,
yeah,
we
we
do
keep
track
of
security
fixes
primarily
because
you
know
there's
special
announcements
and
the
security
queue
and
those
things
that
we
pay
a
lot
more
attention
to
than
today.
Today,
bug
fixes
one
thing
that
we'll
probably
have
a
a
bit
of
well
information
like
management.
That
needs
to
happen
is
that
we
need
to
first
of
all
establish
what
version
of
every
module
we
even
started
with
and
then
and
then
go
from
there.
B
I'd
probably
say,
unlike
the
Drupal,
where
we
make
a
very
likely
making
issue
for
every
release
of
Drupal
or
sometimes
week,
we
can
find
a
release
or
two
of
Drupal
into
into
one
big
meta
issue
with
contributors
prep.
So
maybe
we
could
just
have
one
like
rolling
meta
for
each
control
that
we
have
and
just
every
time
a
new
release
comes
out
or
some
actually
doesn't
even
have
to
be
released
like
we
could
just
keep
track
of.
You
know
if
there
was
some
major
feature
or
functionality
that
came
into
Couture
montreux.
B
We
could
just
add
it
to
the
meta
of
you
know:
functionality
we
need
to
port
over
and
that
way,
I
think
for
most
controls.
You
know
they're
they're
moving,
you
know,
they're
they're
mostly
fixed,
but
you
know,
there's
have
changes
every
now
and
then
and
some
of
them
are
more
active
than
others.
So
that's
what
I'm
thinking,
probably
just
one
major
issue
per
module
and
if
it
ever
gets
like
unwieldly.
Like
you
know,
we've
got
like
hundreds
of
comments,
then.
Maybe
we've
just
closed
it,
making
a
meta
tracking
from
that
point
forward.
B
C
Know
have
an
idea
we
could
set
a
Drupal
7
site
with
all
those
contributors
then
enable
the
email
notification
when
there's
new
releases
for
that,
and
we
keep
it
updated
to
the
releases
that
we
have
actually
made
the
commits
for.
So
it's
done
that
there's
a
change.
We
receive
an
email
with
a
list
of
new
releases,
and
then
all
we
have
to
do
is
compare
what
the
detailed
or
vision
with
what
we
have
on
that
site
and
then
figure
out
that
maybe
have
another
script
that
pulls
out
the
commits
for
that.
For
those
that.
B
C
B
Okay
yeah:
these
are
all
great
ideas,
yeah
and
there's
just
a
lot
of
a
lot
of
maintenance
involved
in
you
know
something
that
is
this
largest
backdrop.
So
I'm
really
pleased
to
see
you
know
continuing
dedication
to
just
making
sure
that
our
product
is
stable
and
updated
and
we're
fixing
bugs
continuously.
B
B
You
can
check
it
out
by
visiting
the
backdrop,
issues,
queue
and
check
out
the
1.72
release
and
those
are,
as
always,
just
items
that
we
think
that
we
can
finish
or
things
that
we
believe
are
slightly
higher
priority
and
that's
right,
packed
with
1.72,
but
any
fixes
that
we
have
available
we'll
roll
them
into
the
next
bug
fix
release.
I
was
assuming
there
a
non-breaking
of
course,
1.8
1.8
is
the
next
minor
release
of
backdrop.
It's
three
weeks
from
code
freeze
and
we've
got
got
some
work
to
do.
B
I
think
it's
probably
time
that
we
start
looking
at
what's
feasible
and
maybe
adjusting
our
expectations
about
tackling
some
of
these
really
big
things
and
start
looking
at
you
know
easy
wins
that
have
that
are
highly
visible,
that
wouldn't
take
quite
so
much
work.
But
let's
go
over
the
the
big
list
of
Meadows
here,
the
first
one
is
twenty
one.
Thirty
four
layout
relationships
layout
relationships
as
a
functionality
didn't
get
in
last
release,
but
even
at
the
end
of
last
release
was
relatively
close.
B
So
no
updates
there,
but
still
I,
think
within
the
window
of
a
possibility
for
us
to
actually
manage
media
library
is
a
meta
issue
at
14,
48
and
there's
a
lot
of
sub
items
here,
and
this
is
definitely
an
area
where
I,
don't
think,
will
be
comprehensive
in
our
objectives.
But
there's
so
many
like
smaller
items
that
we
could
still
knock
out
several
of
them
before
the
1.8
release
and
I
know
ones
that
are
currently
in
progress.
Uploading
a
file
manually
I
saw
there
was
a
PRS
recently
as
in
just
in
this
past
week.
B
That
is
great,
just
adding
the
ability
to
add
a
file
without
any
entity
attached
to
it.
That's
26
33
and
that
one's
looking
good
configurable
configurable
file
entity
bundles,
that's
basically,
field
types
as
26:32
that
one
there
was
some
back
and
forth
there,
and
I
thought
that
we
were
going
to
get
a
little
bit
more
movement
before
some.
B
B
A
So
this
is
something
that
I
muted.
You
know
this
woman
that
has
been
on
the
list
for
a
while
to
figure
out
how
to
do
multiple
file,
uploads
and
I
think
we
had
an
issue
that
originally
was
just
like
used
to
html5
multiple
attribute,
but
it's
expanded
a
little
bit.
There's
a
bunch
of
additional
modules
in
Drupal
7
that'll
allow
multiple
file
uploads
in
a
way
that
it's
pretty
nice
and
somebody
recommended
I,
don't
remember
who
it
was
I,
don't
know
if
you
remember
Gregory
this
new
module
called.
A
A
Drupal
8
chosen,
our
previous
method,
which
was
to
use
a
multiple
file
and
multiple
image
modules
from
triple7,
and
the
only
caveat
I
think,
is
that
the
module
description
on
your
bolo
arc
says
that
only
works
for
modern,
browsers,
I,
don't
know
what
it
actually
is
about
this
particular
process
that
makes
it
not
work
on
older,
browsers
and
there's
something
in
the
JavaScript.
I
was
looking
for,
like
HTML,
not
to
beat
so
weren't
supported.
They
couldn't
find
anything.
It
could
just
be
the
multiple
thing.
A
C
Yeah
well
I
used
to
play
a
lot
with
simply
destiny.
So
I
guess
there
are
a
lot
of
modules,
even
though
not
even
real
sites.
So
I
was
familiar
with
that
module.
I
can't
remember
what
it
was
that
I
do
recall.
Vaguely
they
issue
about
modern
browsers,
but
I
can
remember
the
cause
of
it
like
the
darude,
oh
yeah,.
C
Which
is
good
news
because
usually
notes
like
that
might
be
left
for
a
long
time
like
years
and
years
there,
so
it
might
be
irrelevant
there,
yeah
cuz,
the
modern
browsers
might
be
the
norm
there
so
or
or
worse
comes
to
worst.
We
can
fall
back
to
something
that
works
with
these
barrels,
as
well
like
like,
like
the
multiple
thing,
yep.
B
Yeah,
it's
also
worth
doing
that.
You
know
supporting
the
multiple
property,
that's
something
that
also
only
works
in
quote
modern
browsers,
like
at
most
of
it
also
be
curious
to
see
just
how
up
you
know
if
this
degrades
gracefully,
which
it
looks
like
it
should
looks
like
I,
might
even
just
like,
take
the
normal
file
fields
and
just
like
a
JavaScript
to
it.
Yeah.
B
Does
and
so
how
this
all
works
is
intriguing
to
me,
because
it
basically
would
avoid
the
need
to
actually
support
the
multiple
property,
which
would
be
good
because
it
would
shortcut
all
of
that.
A
API
requirements
like
I
mean
because
supporting
found
multiple
are
the
multiple
property.
It's
really
challenging,
honestly
as
as
I
noticed,
and
that
is
that
great
very
quoted
from
ages
ago,.
B
Looks
looks
like
an
interesting
option.
The
one
downside
of
this
is
that
it
would
only
work
within
feel
to
you
I.
It
wouldn't
work
outside
of
jail
DUI,
if
it
just
enhanced
legit
the
widgets,
rather
than
better
than
enhancing
the
actual
file
elements,
but
still
could
be
worth
putting
into
is
worth
looking
to.
Okay,
I'll.
A
A
So
if
you
wanted
to
upload
a
new
document
or
change
any
file
name
or
something
like
that,
you
can
do
that
through
that
interface,
I
haven't
figured
out
how
to
get
the
add
file
page
to
work
and
that's
the
piece
that's
missing,
but
I
think
that
if
we
wanted
to
move
forward
on
the
one
that's
there
that
could
be
easily
separated
into
two
separate
issues.
One
that's
out
of
file,
one,
that's
edit
a
file,
so
it
can
use
review
now.
B
Okay
and
then
the
last
item
that
we've
got
here
as
far
as
like
large
Medes
or
large
items
for
one
point:
a
is
config
translation,
and
this
is
the
ones
that
I
volunteered
to
do.
That.
I
think
it's
most
likely
on
the
chopping
block
here,
because
we
have
basically
an
idea,
but
I
mean
with
no
actual
code
behind
it.
I
feel
like
we.
B
We
could
better
spend
their
time
trying
to
like
going
after
things
that
are
more
achievable,
like
UX
features
and
working
on
the
ones
that
we've
got
here
rather
than
trying
to
start
a
large
efforts.
You
know
at
the
very
tail
end
of
the
cycle,
so
so
probably,
unless
somebody
else
picks
this
one
up,
like
I'll,
probably
be
backing
off
of
attempting
to
implement
it
for
1.8
and
spend
that
time.
You
know
working
on
smaller
pieces
of
functionality
and
and
helping
facilitate
all
of
the
other
issues
that
that
we
that
we've
got
tackled
so
far.
B
D
B
D
B
Yeah
and
actually
I
mean
our
standard
response.
Here
was
like
oh
well,
you
could
port
a
Drupal
7
module
that
did
that
almost
all
Drupal
7
modules
that
add
different
authentication
capabilities
or
they
do
so
may
form
altering
the
login
forms,
and
then
they
just
kind
of
hijack
the
login
process
from
the
forms
themselves,
which
is
not
not
a
real
great
solution.
B
Yep
I
totally
agree
that
we
should
facilitate
alternative
login
mechanisms
in
court
like
a
much
more
in
a
much
more
central
manner
than
just
you
know,
saying
you
know:
oh
there's
a
form
and
you
just
modify
the
form
in
order
to
make
it
work
with
other
systems.
I
think
would
be
much
better
if
we
somehow
made
its
ahead.
B
B
Yeah
yeah,
basically,
like
a
probably
you
know,
like
anything
else,
that's
swappable,
it
probably
end
up
being
in
class.
It's
like
you
know,
is
a
class
that
implements
the
authentication
mechanisms
and
then,
if
you
wanted
to
support
authentication,
you
would
add
your
own
class
that
added
functionality,
but
things
for
like
two-factor
authentication,
where
there's
like
actual
changes
to
workflow.
You
know
additional
screens.
They
need
to
be
interjected.
Ask
for
additional
information.
B
Yeah,
there's
a
lot
of
work
to
be
done
to
actually
support
that
functionality,
yeah
and
so
totally
go
for
it
make
an
issue,
especially
if
you've
got
some
ideas
about
how
it
could
be
implemented.
Then
EF
flushed
out
your
idea
in
the
issue,
because
we
would
love
to
have
something
like
that
and
it
shouldn't
be
a
core
functionality.
C
A
I
mean
the
big
picture.
Is
that
being
backdrop?
One
is
likely
limiting
adoption
and
if
we
were
backdrop
we
might
grow
faster.
So
we
have
a
marketing
incentive
to
become
backup.
We
do
not
necessarily
have
any
technical
incentive
to
become
backdrop,
because
we
can
continue
to
add
new
features
to
factor
up
on
as
long
as
is
necessary
and
so
we'd
added
this
to
the
agenda
because
we
are
like
well.
Maybe
we
should
think
about.
Like
you
know,
what
are
our
driving
factors
to
becoming
backtalk?
A
Are
we
going
to
have
an
on
API
braking
major
version,
and
can
we
even
do
that
with
our
infrastructure,
and
so
we
have
some
good
ideas
about
things
that
might
make
it
worthwhile
for
people
upgrade
for
a
backdrop,
one
to
backdrop,
including
automatic
updates,
an
ability
to
import
or
upgrade
from
WordPress,
and
if
we
wanted
to
include
those
features,
even
if
we
had
a
non
API
break.
Breaking
release
would
that
be
viable
in
the
amount
of
time
left.
A
I
think
that
as
soon
as
doctor
up
one-point-eight
comes
out,
we
can
say
we
don't
have
time
to
make
backdrop
to
happen.
January,
15th,
I,
don't
think
one
release
is
enough
time
to
get
organized
and
and
figure
that
out,
but
if
we
wanted
to
look
into
whether
we
can
run
two
versions
of
controls
the
same
time,
four
core,
there
is
a
little
kind
of
due
diligence.
We
could
do
ahead
of
time
to
see
what
our
software
might
look
like
if
we
wanted
backdrop
to
to
support
Bach
drop
one
and
back
drop,
two
modules,
I.
A
We
need
to
figure
that
out
in
the
next
21
days,
if
we
can't
do
it,
it's
a
non-issue
and
we'll
just
say
dr.
up
will
be
an
expression
of
backdrop.
The
same
way
triple
age
is
the
next
version
of
Drupal
7
and
everything
has
to
be
ready,
I
think
that
puts
more
burden
on
our
community,
but
if
we
can't
do
it
technically,
it
doesn't
matter.
A
That's
what
we
have
to
do
and
we'll
just
have
to
be
careful
about
the
breaking
changes
that
we
do
make
to
make
sure
that
they're
not
going
to
be
too
much
so
I,
don't
know
I
I
in
and
not
having
time
personally
in
the
next
21
days
to
focus
on
what
backdrop
to
you
will
look
like
I
haven't
seen
anyone
else
be
as
excited
about
it
as
I
am
so
I'm
guessing.
That
means
that
probably
no
one
is
super
motivated
to
figure
it
out,
which
I
think
would
mean
that
back
up
to
won't
be
happening.
A
January
15th,
the
earliest
it
would
happen,
will
be
made
15th,
which
would
be
the
same
time
as
we
would
normally
do
backdrop
1:10,
which
might
work,
but
we
also,
since
we
don't
know,
haven't,
haven't
really
decided
like
as
a
community.
What
backdrop
to
means
we
might
need
more
time
than
that
as
well.
So
if
anyone
wants
to
do
any
of
the
technical
research
to
figure
out
what
backdrop
can
do
without
much
modification
to
the
core
and
expending
one
days
that
we
fantastic.
If.
D
A
C
C
So
I
think,
maybe
that's
that
don't
be
enough
to
join
us
like
it
now
would
be
the
time
to
say.
Maybe
you
should
start
actually
implementing
these
I
know.
I
know,
there's
not
enough
time
for
us
and
we
we
don't
have
the
manpower
that
the
doctor
has,
but
we
need
to
get
started
at
some
point.
I
think
so
why
not?
Why
not
for
January.
B
B
You
know
that's
why
we're
on
like
chrome,
59
or
whatever
it
is,
and
they
just
consider
you
know
they
basically
kind
of
break
things
every
time
and
they're
just
a
lot
more
honest
about
it,
like
we
break
small
things
and
minor
releases
on
a
pretty
regular
basis
and
that
probably
true
semantic
versioning,
you
would
actually
be
making
a
major
releases
on
a
great
I'll
like
constantly
so,
but
all
of
those
things
yeah.
We
need
to
refactor
how
like
our
infrastructure
works
and
how
compatibility
works
in
how
much
was
defined.
C
C
A
It
would
make
sense
if
we
knew
what
the
but
a
tomb
grant
should
contain
like
if
we
decide
we
are
gonna,
do
breaking
changes
like
API
breaks,
then
we
can
start
working
on
these
2x
issues
that
are
breaking
I'm
at
them
only
to
the
2x
branch.
But
right
now,
since
we
haven't
figured
out
what
do
dot
X
means.
Yet
we
don't
want
to
commit
anything.
You
know
would
like.
We
would
later
have
to
roll
back.
I
understand.
C
A
C
C
The
other
thing
that
I
wanted
to
mention
was
I've
mentioned
that
before
and
I
think
it's
a
good
practice
that
the
FDA
does
with
the
experimental
modules,
and
we
have
discussed
that,
and
we
said
that
if
we,
if
we
charge,
if
we
start
putting
experimental
modules
consumables
into
core,
maybe
then
they
will
start
moving
slower,
but
I
think
I
think
I
saw
like
had
an
idea.
We
had
the
project
installer.
C
So
this
would
have
the
same
effect
as
in
the
age
sort
of
inviting
more
people
to
test
them,
without
so
like
locking
them
with
the
pace
that
the
core
dance
or
they
would
be
able
to
is
still
involving
the
trip,
but
at
the
same
time
would
communicate
the
same
message
that
v8
does
for
its
people.
So
we
are
thinking
of
adding
these
two
core
and.
A
Is
not
something
that's
a
chord
change
right
if
it's,
if
it's
project
project
installer?
Well,
maybe
it
is
I,
don't
know,
but
it
could
just
be
a
change
in
the
way
that
we
report
module
information
to
the
project
module
like
there's.
There
are
parts
that
we
can
do.
The
won't
involve
chord
changes
that
we
could
do.
Even
if
the
whole
thing
you
know,
we
can't
get
anything
into
1.8,
yeah.
C
I've,
given
this
some
thought,
I
thought
that
the
only
on
the
right-hand
sidebar,
where
we
have
the
issue
queue.
That's
sorry
that
project
you.
We
could
have
this
on
space
beneath
it,
so
we
could
have
sort
of
like
it
would
be
like
a
promotional
ad
thing
that
these
are
for
candidates
and
then
another
another
place
would
be
sort
of
like
I.
C
B
C
B
A
So
your
belly
was
last
weekend.
Annie
and
I
went
down
there.
We
gave
a
tough
on
back
up
on
Sunday
morning,
which
sometimes
can
be
a
little
rough
people
play
too
hard
on
Saturday
night
or
want
to
fly
home
early,
but
we
actually
had
a
really
great
turnout.
A
lot
of
people
came
up
and
talked
to
us
about
it
on
Saturday
and
then
came
to
our
session
on
Sunday.
A
We
had
a
bunch
of
people
who
had
seen
back
drop
early
in
our
development
cycle,
but
hadn't
seen
it
recently
and
we're
very
impressed
so
good
job,
everybody
for
continuing
to
add
new
features,
but
surprise
people
when
they
come
back
a
year
later
and
there's
more
better
stuff
going
on.
We
had
a
bunch
of
fantastic
questions
asked
at
the
end
of
the
session,
which
I
thought
was
really
great.
A
E
B
A
B
B
C
My
feeling
was
always
that
maybe
we
should
have
a
discussion
or
an
article
or
something
that
if
you
do
not
like
run
the
lines
of
shorter
than
that,
but
if
you
do
not
like
the
idea
of
working
with
d8-
and
you
know
that
at
some
point
you
will
have
to
make
a
decision
because
d7
is
coming
to
an
end.
Why
aren't
you
considering
backdrop
so
I?
Have
you
first
of
all,
do
you
know
its
existence
and
then,
if
you
know
why,
what
makes
you
hesitation
from
maybe
that
would
give
us
a
lot
of
mounts
viscous.
C
But
that's
that's
lately.
It's
time
that
I
was
reading
a
post
from
a
person
this,
at
least
this
question
was
just
lingering
I
mean.
There's
all
the
comments.
It's
like
all
the
people
were
saying:
I
want
it.
Basically,
I
want
to
keep
most
of
my
customers
that
are
low-budget
or
nonprofits
in
d7,
and
there
was
some
comments
then,
but
saying
all
right:
I
don't
want
to
work
with
the
age,
so
I'm,
probably
gonna,
move
away
then
to
pull
together
and
I.
B
We
have,
we
still
had
the
opportunity
that,
thanks
to
the
efforts
of
herb
duel
and
others,
think
that
one
of
the
compelling
things
for
nonprofits
right
now
were
small
organizations
is
the
availability
of
service
area
and
they
were
specifically
promoting
they.
Wouldn't
it
be
great
if
Drupal
8
supported
silly
CRM
I.
Can
we
need
to
have
that
in
order
to
make
this
possible?
B
E
Was
in
the
weekly
drop
today
that
how
to
do
it
for
Drupal,
8.
B
B
B
D
D
All
of
us,
so
it's
almost
the
same
mustard
on
top
social
mustard,
on
whatever
they
are
relatively
big.
Now
all
the
big
domains
so
already
taken
by
investors
trying
to
sell
them
at
bigger
prices,
because
they're
not
expecting
to
be
very
big
and
I,
think
that
this
is
a
good
time
for
a
CMS
like,
like
your
backdrop,
to
consider
how
to
integrate
with
that,
so
that
we
can
get
a
role
in
the
next
generation
social
media.
D
My
my
understanding
of
the
development
is
that
we
will
see
a
huge
movement
towards
self-hosting
so
that
we
will
have
both
our
own
website
blogs,
like
powered
by
laptop
with
also
our
own
Twitter,
and
they
are.
They
are
syndicated
federated
everywhere,
and
this
is
the
content
management
part.
The
categorization,
the
the
collaboration
part,
must
be
handled
by
a
CMS.
That
is
not
something
that
the
the
Twitter
like
things
can
handle.
They
are.
D
B
D
You
go
to
one
of
the
master
doughnut
holes.
You
will
get.
If
you
have
accounts
there,
you
will
get
higher
limits.
You
can
have
tweets
up
to
1,000
characters
instead
of
the
500,
which
is
the
default.
If
you
create
logins
and
almost
all
the
other
mastodons,
they
are
sticking
to
a
500
limits.
But
when
you
are,
when
you
have
the
bigger
one,
all
the
others
will
still
display
them
display
them.
So
you
don't
have
the
limits.
That's
your
most
amount
of
hosts
this
one
of
those
who
have
this
higher
limit
on
open
source.
D
C
D
And
not
every
things
is
well
structured
into
into
lookups
and
stuff,
but
actually
the
functionality
is
already
already
there
and
it's
it's
growing
relatively
fast,
so
I
have
bought
one
of
the
very
few
domains
that
wasn't
that
was
left
now.
I
have
I,
have
mastered
on.com,
which
I'm
going
to
get
into
kind
of
a
campus
for
for
campaigns
and
I
want
to
link
that
with
CMS.
D
D
B
The
tip
yeah:
well,
let's,
let's
wrap
up
this
meeting
it
looks
like
I,
would
have
our
strap
already.
So
thanks
doing
it
for
the
big
idea,
that's
something
that
we
looked
into
you.