►
From YouTube: Backdrop Weekly - Nov 15th
Description
Today’s development agenda: http://bit.ly/2RE53Wa
A
A
Anybody
can
join
these
meetings
as
always
they're
open
the
easiest
way
to
get
a
hold
of
one
is
to
follow
us
on
Twitter
or
check
the
git
er
chat
channel,
where
the
link
to
the
Hangout
is
posted
just
minutes
before
it
happens,
and
on
Twitter
the
agenda
is
posted
publicly,
with
a
link
to
the
agenda
will
then
ultimately
include
the
Hangout
link
as
it
is
created,
so
updated
live
as
we
do
these
meetings.
So,
let's
get
started
today
updates
from
the
PMC.
It
will
reiterate.
A
I
think
this
announcement
happened
last
week
that
we
passed
a
PMC
votes
to
make
it
so
that
GPL
three
is
considered
acceptable
in
contributes.
While
we
still
encourage
GPL
two
and
everything
is
always
GPL,
2
or
higher.
We
encourage
you
bill
to
by
default,
but
GPL
3
within
reason.
If
you
need
to
incorporate
apache
license
dependencies,
then
GPL
3
is
considered
acceptable.
A
We
don't
have
any
community
updates
I,
don't
think
the
only
contributed
project
we've
gotten
in
the
past
week
is
that
image
formatter
link
to
image
style
is
that
the
whole
name
of
the
module?
Is
it
that's
a
great
thought
quite
like
name
there,
but
it
says
what
it
does
I
suppose
so
fairly
limited
activity
over
there
in
the
crib,
but
yeah
still
lots
of
action
happening
throughout
backdrop.
A
Website
related
tasks
we
got
backed
up
CMS
org
we've
got
an
ongoing
issue,
an
issue
400
gin
Lampton
has
been
putting
some
efforts
into
making
modules,
themes
and
layouts
search
functionality
work
better.
You
can
follow
over
in
that
issue.
442
I
think
that
so
far
there
isn't
anything
to
look
at
as
far
as
updates
are
concerned,
I
think
that
she's
just
stated
that
she's
making
some
progress
on
it
and
to
keep
a
lookout
for
changes
coming
down
the
pipe
in
that
issue.
A
Let's
see
476
is
an
issue
that
covers
sandbox
functionality
and
the
way
that
slide
476.
In
the
backdrop
CMS
fork
issue.
2
is
some
discussion
about
the
way
that
sandbox
is
work
and
the
way
that
we're
using
Pantheon
we
kind
of
covered
this
extensively
in
the
outreach
meeting
just
prior
to
this.
So
if
you're
interested
in
hearing
about
some
changes
coming
about
how
we
can
do
the
try
a
demo
button
on
the
home
page,
then
you
can
check
out
that
video
recording
and
we've
got
some
interesting
things
coming
along
there.
A
A
Let's
see
we
don't
have
any
updates
on
the
forum.
The
API
site,
or
the
translation
site
so
I'm
going
to
skip
over
those
sections
for
today,
let's
go
into
the
project
progress
report,
which
is
how
development
is
coming
along
about
backdrop
CMS
itself,
we've
got
a
number
of
items
here
slated
for
the
next
bug
fix
release,
which
is
one
11.3.
A
A
392
is
330.
209
3209
is
an
issue
for
adding
predefined
colors
games
to
basis.
There's
been
some
concern
that
we
should
run
the
color
schemes
that
come
or
that
are
being
suggested
there
through
an
accessibility.
Checker
we've
been
trying
to
get
some
design
eyes
on
that,
but
considering
the
continued
designer
lack
of
presence,
I
think
it
I
think
it
might
be
good.
If
you
know
we
don't
need
to
be
a
designer
to
look
look
over
and
I
think
we've
had
to
people
can't
say
yeah.
A
It
looks
pretty
good
to
me,
so
we
can
waive
that
if,
if
there's
no
other
people
available
for
doing
the
design
review,
it
might
be
best
just
to
go
ahead
and
merge
it
in
one
great
thing
about
these
color
schemes.
Is
that
I?
We
can't
actually
change
them
at
any
time
without
negatively
affecting
existing
sites.
A
A
We
have
a
confirmed
version
on
that
issue,
but
there
hasn't
been
any
code
put
behind
that
as
you
get
one
small
regression
regarding
the
new
info
status
message,
it
affects
the
available
updates.
Page,
that's
issued
30305.
That
issue
is
marked
ready
to
be
committed,
so
we've
even
tested
my
community
so
that
one's
just
on
our
core
team
to
to
do
the
merging
that's
great
recently
discovered
a
rather
substantial
regression
that
clean
URLs
cannot
be
enabled
after
the
initial
site
installation.
A
Thanks
joseph
for
bringing
this
to
our
attention
for
this
meeting,
that's
issued
2488
that
one
has
a
pull
request
already
needs
review,
I!
Think
it's!
Actually.
It's
marked
review
tested
by
community
in
the
issue
queue
here,
so
yeah
there's
two
pull
requests.
Actually
both
of
them
are
required.
It
looks
like
this
is
marked
ready
to
be
committed,
so
we
should
get
core
committer
eyeballs
on
that
as
soon
as
possible.
A
Recently
brought
up
that
backdrop
when
it
creates
class
names,
it
does
not
allow
underscores
it
changes
them
all
to
hyphens
in
CSS
classes.
That's
33
65.
This
has
become
an
issue
for
sites
that
are
trying
to
implement
them
style
classes.
We
do
need
some
feedback
and
discussion
on
that
one,
because
there
might
be
some
backwards.
Compatibility
effects
there
that
the
class
names
might
change
because
of
that
modifying
underscores
to
hyphens
like
whenever
we
pass
a
machine
name
through.
A
B
B
A
B
So
this
was
a
problem
that
was
causing
PHP
notices,
wind
paragraphs
nodes
with
paragraphs
were
being
added
and
deleted,
but
not
when
they
were
being
updated.
So
there
is
a
pull
request
and
it's
been
RTB.
Seed
has
in
it
fixes
things
and
it
looks
like
the
code
is
okay.
What
we
need
there
is
a
decision
because
there
was
a
hint
at
the
beginning
of
the
issue
whether
this
should
be
sold
same
core
or
if
it
belongs
in
country,
but
if
we
can
fix
things
a
gorgeous
yeah,
so
it
will
it's
not
invisible.
It
needs
people.
B
B
A
So
so,
there's
finally
an
issue
or
a
new
release
of
Drupal
8.
It's
new
functionality,
bug
fixes
non
security,
related
bug,
fixes
and
actually
a
few
API
editions
and
classes
Krish
ooh
at
3375
that
covers
all
of
the
commits
that
are
in
Drupal
7
dot
61,
with
the
fair
number
pull
requests
actually
already
porting
a
number
of
those
patches.
So
we
can
merge.
Those
in
our
policy
is
really
to
do
them
as
soon
as
possible.
A
We
don't
need
to
wait
for
a
minor
version
for
implementing
cross
ports
unless
their
API
additions,
and
then
we
might
push
a
few
of
those
over
to
1.12,
so
lots
of
things
that
are
in
the
next
milestone
for
one
11.3
also.
This
was
mentioned
a
while
back
that
we
had
a
problem
with
the
installer
that,
when
it
automatically
was
doing
localhost
versus
127.0.0.1
conversions
that
wasn't
working
quite
correctly,
I
think
we
have
a
TBC
on
that
issue
as
well,
but
I
didn't
put
that
in
each
ended
before
you
and
so
I.
A
Don't
have
the
number
handy
anyway,
lots
of
reasons
for
us
to
progress
and
make
the
one
dot
11.3
Louise
kind
of
sooner
rather
than
later,
because
we've
got
a
fair
number
of
items
that
are
starting
to
add
up
there
all
right
next
up,
1.12
one
at
12,
is
the
next
minor
version
that
will
be
coming
out:
January
15th
at
2019
on
bat-ropes
4th
birthday
and
we've
got
it.
Some
really
interesting
things
that
are
being
tackled
here.
Automatic
updates
is
an
issue.
A
2018
is
the
big
meta
and
then
there
is
a
sub
issue
actually
where
most
of
the
activities
happening
in
414,
and
this
still
needs
just
more
feedback
and
more
more
testing.
Basically,
it
does
look
like
everything
works.
The
way
that
we
would
expect
yeah.
That
has
many
updates
here
recently.
So
I
won't
recap
this
too
much,
but
automatic
updates
is
something
to
leave
that
pushing
forward
and
would
add
a
really
big
usability
enhancement
and
maintenance
ability,
enhancement
for
backdrop.
A
A
Issue.
Number
1005
is
options
element
in
the
core
user
experience
enhancement
to
making
select
list
options.
There's
been
a
lot
of
comments
on
that
saying.
People
have
trended
out
and
they
think
it
looks
awesome,
but
we
haven't
had
anybody
so
bold
as
to
market
reviewed
and
tested
by
community
yet
so
that
one
still
needs
review.
Although
code
wise,
it
looked
good
to
me
last
time,
I
gave
every
review
I
think
maybe
that
might
be
primarily.
A
A
A
It
would
also
make
reviewing
the
pull
request,
a
lot
easier
if
it
weren't
so
massive,
so
would
reviewed
every
view
that
recently-
and
it
looked
really
great
like
from
as
far
as
the
code
is
concerned,
even
though
it's
absolutely
massive
it
just
it
is
a
little
bit
concerning
just
about
the
size
of
it.
So
I
would
say
it
would
be
an
agreement
there
if
there's
anything
that
is
holding
up
with
a
pull
request.
We
should
start
looking
at
what
we
can
remove
if
those
things
are
being
blockers
for
ancient
pleaded.
A
B
Yeah,
basically,
the
feedback
is
how
its
implemented
now
is
different
from
the
d8
version,
as
in
nothing
gets
blocked.
If
it's
not
configured,
and
even
when
you
configure
it,
it
doesn't
block
the
site.
So
it's
just.
This
is
just
an
error
message
in
the
star
spades
to
indicate
that
this
exciting
has
not
been
configured
in
settings
PHP,
but
beyond
that
it
doesn't
do
anything
else.
So
my
thoughts
were
that
perhaps
because,
as
you
said,
this
feature
is
causing
a
lot
of
frustration
to
d8
people.
B
Maybe
we
should
demote
it
from
an
error
to
a
warning
and
then
also
there's
discussions
in
the
d8q
in
the
drupal.org
queue
of
whether
there
should
be
setting
UI
provided
in
the
the
admin
interface
for
to
set
it
from
the
admin
interface
and
the
questions
there
are.
Should
we
include
it
in
the
installer
as
well?
B
So
so
the
message
includes
a
link
with
DDOT
oligarchical,
which
explains
in
detail
with
the
possible
the
possible
dangers
for
vulnerabilities
security,
vulnerabilities,
so
I
thought,
maybe
you
or
someone
with
better
knowledge
of
stuff
like
that,
could
give
it
a
review
and
see
how
how
severe
the
possibility
of
height
being
site
being
hacked.
Yes,
if
it's
not
much
of
an
issue,
we
could
demoted
to
a
warning
and
let
it
be
yeah.
A
Yeah
recently,
clients
that
I've
had
encountered
this
have
the
Apache
like
the
hostname
configured
at
the
Apache
levels.
So
it's
not
even
possible
to
do
this
functionality,
which
kind
of
is
a
curiosity
for
me
about
whether
or
not
this
is
like
a
hosting
problem
by
something
in
the
hosting
sphere.
That
probably
is
not.
That
might
not
be
even
appropriate
for
port
backdrop
to
push
into
people's
faces.
A
A
Okay,
well,
that's
yeah.
I
haven't
had
a
chance
to
look
over
okay
documentation
there.
So
we'll
take
a
look
at
it
and
yeah
everybody.
Please
post
your
own
feedback
about
that
option
at
23,
82,
okay
and
lastly,
in
the
1.12
queue
is
working
on
getting
our
libraries
up
to
date,
there's
been
several
new
versions
of
ckeditor
and
we
would
like
to
update,
see
cater
to
the
latest
version
at
33,
55
jet
query
and
jQuery
UI.
A
We
continue
to
kind
of
have
some
questions
around
how
to
deal
with
that
right
now,
right
now,
we're
still
running
the
unsupported
version
of
the
one
dot.
Next
branch
of
jQuery
and
moving
to
three
dot
X,
which
is
the
current
version,
poses
some
challenges
for
us
like
doing
backwards.
Compatibility
layer
might
be
an
option,
but
it
might
also
not
be
an
option.
I,
don't
think,
there's
anything
that
provides
all
of
the
layers.
We
need
altogether.
The.
B
Compatibility
layer
is
actually
for
the
2
dot,
X
version
as
far
as
I
can
recall,
so
you
currently
currently
have
one
to
text
to
the
text
and
three
dot:
X
2
dot
X
has
a
an
additional
sort
of
like
module
that
you
can
install.
That
provides
the
pretty
much
the
same
thing
that
we
do
with
the
e
function,
wrappers
or
deprecated
functions,
so
I
think
baby
steps.
So
if
we
are
considering
to
upgrade,
maybe
the
safest
option
would
be
to
go
to
2
dot,
X
right.
A
Ok,
that's
it
for
the
1.12
status,
update,
there's
more
issues
as
always
get
up.
Issue
tracker
for
the
1.12
milestone.
I!
Think
that
Jeff
isn't
around
to
give
an
update
on
backdrop
for
good,
so
we'll
go
into
just
general
discussion
in
Q&A.
If
you
guys
have
anything,
you
guys
would
like
to
bring
up
on
the
recording.
C
Yes,
oh
right,
I
think
the
taxonomy
translation
topic
so
yeah.
It's
about
an
issue
to
provide
taxonomy
translation,
which
means
the
translation
of
taxonomy
terms,
which
then
would
mean
that
terms
have
a
language
and
that
so
we
don't
have
translation
sets
for
taxonomy,
but
we
can't
provide
a
language
for
for
the
terms
and
came
up
a
question
about
it
in
the
issue.
It's
number
twenty,
nine.
C
Think
yes
quite
interesting
discussion,
but
I
guess
we
could
need
some
more
feedback
on
it,
because
we're
discussing
it
with
three
persons
up
to
now
and
yeah
I
am,
for
example,
I
had
the
idea
with
the
content,
translation,
calling
the
content,
translation,
the
content,
language
but
I'm
absolutely
not
sure
it
seems
like
a
good
idea
to
me
but
yeah.
It
also
seems
a
good
idea
to
me,
like.
B
From
a
workflow
perspective,
it
seems
that
the
proper
thing
to
do,
but
the
implementation,
wise
and
there's
some
challenges
as
I
said
and
then
help
mentioned
like.
Perhaps
if
we
need,
if
we
implement
the
minimal
product
we
can
implement
to
have
terms
and
slided,
we
can
leave
that
for
a
follow-up
mm-hm,
but
my
main
concern
with
that
is
that
so
long
as
we
make
sure
that
with
the
implementation,
we
do
not
like
block
any
of
the
available
options
for
the
follow-up.
A
B
B
Inflation,
it's
gonna
be
different,
entirely
different,
which
translation
sites
would
give
you
a
deal
thing
to
do,
because
then
you
could
provide
a
tab
in
each
term
when
you
edit,
it
says,
translate
and
then
you
could
translate
it
to
different
languages,
but
we
don't
have
that
currently
in
core
I.
Think
that's
what
we
would
like
to
go
to,
but
I
don't
think
we're
ready
for
that.
Yet
yeah.
C
B
Simple,
so
yeah
the
Lion
module,
the
sorry,
the
internationalization
module
is
a
big
module.
It's
a
beast,
so
it
will
take
us
time
to
implement
everything
that
it
offered
all
most
of
the
things
that
people
expect
in
core,
so
that
could
take
a
year
could
take
two
in
the
meantime.
If
we
have
that
that
intimidation
of
allowing
languages
to
be
specified
for
its,
then
it
can
be
an
intermediate.
So
a
black
state,
yeah
and.
A
C
C
B
A
I
think
so
up
anything
else
or
anybody,
okay.
Well,
let's
call
up
the
end
of
the
meeting
then
thank
you
all
for
joining
this
meeting.
Once
again,
thank
you,
everybody
out
there.
That's
watching
these
backdrop
updates
we'll
reconvene
again
next
week
same
time,
as
always
Thursdays
at
1:00
p.m.
Pacific
time.
So
thank
you
all
see
you.