►
From YouTube: Backdrop Weekly - May 30th
Description
Today’s development agenda: http://bit.ly/2X9rMfO
A
All
right,
this
is
weekly
development
meeting
today
is
May
30th
I'm
gonna
check
in
on
a
backdrop
itself
is
coming
along,
but
before
we
get
into
that,
I
did
want
to
say
we
have
a
new
project
this
week.
Semantic
views
for
the
backdrop
so
I
think
they're
working
on
that
one
and
then
let's
talk
about
our
websites
and
backdrop
CMS
org.
A
We
talked
about
in
the
last
meeting
that
reach
means
something
wants
to
see
how
that's
coming,
and
you
can
watch
that
I
just
didn't
want
to
say,
I
think
the
home
page
demo
button
can
go
up
at
any
time.
We
just
need
to
make
sure
that
the
other
ways
to
install
the
backdrop
page
looks
ok,
so
we
need
to
find
a
view
or
the
panel
or
the
layout
or
whatever
it
is
it's
in
there.
That's
doing
that
and
look
at
it
and
make
sure
it's
presentable,
and
if
it
is,
then
we
can
switch.
A
To
that
note,
translation,
Sai
Olaf
has
been
doing
a
ton
of
work
on
the
translation
site
lately.
So
thanks,
Olaf
I
went
ahead
and
pushed
a
couple
of
changes
yesterday.
That
should
make
it
easier
to
manage
translations.
So
originally,
you
could
upload
a
translation
file
and
mark
them
as
needing
review,
but
in
that
case,
every
single
string.
We
need
to
be
approved
by
an
administrator.
B
A
Now,
when
you
upload
a
file,
they
all
just
go
in
and
they
don't
need
to
be
approved,
which
is
great
and
we're
also
going
to
change
the
default
for
these
bulk
uploads
from
Drupal
to
multiple
contributors
rather
than
a
single
contributor,
and
that
way
we're
not
interviewing
all
of
the
people
into
transitions
with
Drupal.
All
of
their
work
to
one
person
haven't
upload
the
file
under
backdrop.
Oh.
C
A
B
A
B
A
A
C
A
C
A
Yes,
no,
maybe
not
yeah
I,
don't
know
if
we
need
someone
actually
go
through
and
test
them
all,
but
I
thought
having
him.
There
would
be
a
good
first
step.
Another
thing,
too,
is
we
had
a
comment
in
the
forum
where
somebody
said:
hey,
I'm
gonna
work
on
translations.
Can
you
tell
me
how
the
translations
thing
works,
so
it
might
be
good
on
the
home
page.
A
We
don't
have
any
way
for
anyone
to.
Oh,
my
guess.
In
the
side,
Bart
says
download
translations,
but
I
was
thinking.
Maybe
we
should
put
the
downloads
for
the
latest
version
of
backdrop
on
the
home
page
and
for
all
the
languages
rather
because
that
other
grid,
it's
like
which
one
do
I
want
like
we
don't
really
need
to
I.
Think
it's
useful
to
have
this
for
all
versions,
but
I.
Think
for
the
home
page,
like
your
initial
version,
should
be
like
here's.
The
latest
version.
A
A
So
all
of
that
process
right
now
is
manual,
but
we
do
have
an
issue
in
the
queue
to
run
the
string-puller
outer
when
there's
a
new
version
of
backdrop
to
run
automatically
so
that
we
should
have
one
version
for
every
release.
We
don't
yet
have
that.
We
only
have
the
releases
that
people
have
done
that.
B
A
I
think
we
should
provide
all
of
these,
because
we
never
know
what
version
someone's
running
I'm,
not
sure
they
all
I
need
to
be
on
this
page
like
if
we
had
it
would
be
like
find
your
version
and
only
showed
supported
versions.
I
would
be
totally
fine
with
that,
but
most
of
this
thing
is
kind
of
hard
coded
to
the
way
Drupal.
Did
it
it's
not
in
views
or
anything,
that's
easy
to
adjust.
A
B
A
Still
think
it
wouldn't
add
an
X
like
Drupal
doesn't
have
any
I
mean
I,
don't
know.
Maybe
there's
only
one
such
I'll
look
at
I'll
try.
The
gerbil
only
has
one
set
of
translations
for
all
of
Drupal
7
because
they
try
not
to
change
them
between
versions.
Yep
could
be.
We
could
also
do
that
with
arts
or
like
if
we
had
one
for
113.
B
C
Hey
man,
sorry
I've,
been
all
over
the
place.
I
want
to
add
one
more
thing
to
backdrop,
CMS
org,
and
that
we
did
the
covert
last
night
of
backdrop,
CMS
org
the
flagship
website
over
to
the
new
debian
based
PHP
7.2
server,
which
is
super
great.
That
means
that
all
of
our
sites
that
were
still
in
that
are
still
abuse.
Diarrhea
DCU,
not
included
in
that
category
migrate.
A
C
Of
the
old
server
and
we're
not
using
the
old
server
for
any
of
the
main
sites
anymore,
which
is
great,
we
also
ran
the
utf-8
and
before
update
or
more
commonly
known
as
the
emoji
update,
and
so
now,
all
of
the
backup
sites
across
the
spectrum
are
all
now
emoji
compatible,
which
is
great.
So
we
can
start
playing
smiley
faces
and
our
bodies
and
URLs.
C
Yeah,
that's
all
I
had
to
say,
but
that's
yeah
under
the
status
report.
Let's
see
we
released
backdrop
1:13
one
I
think
actually
more
than
a
week
ago,
I
think
we
had
another
meeting
since
then
that
addressed
a
backwards
compatibility
issue
with
the
entity.
Type
method
had
been
made
static
and
broke
a
number
of
controls
that
provide
custom
entity
types.
That
change
was
reverted
to
prevent
the
backwards-compatibility
break
and
then
one
13:1
included
that
fix.
So
that
was
just
about
the
only
fix
that
was
in
the
1:13
one.
C
C
Currently
there's
only
three
additional
bug
fixes
that
are
in
that
version.
However,
one
of
them
is
kind
of
important.
The
self
updater
does
not
currently
work
because
we
added
some
new
test
modules
that
were
inside
of
the
profiles
directory
that
are
now
getting
picked
up
and
when
you
try
to
self
update
it,
there's
an
error
saying
that
it
doesn't
know
what
type
of
files
or
what
type
of
extension
some
of
those
modules
are,
because
it
was
missing,
type
equals
module
in
the
dot
info
file.
C
So
that's
been
fixed
in
issue
37
93
and
with
our
current
expected
schedule,
like
I
I.
Think
a
good
question
is
like.
Is
that
fix
alone,
plus
the
expectation
of
putting
out
a
release
two
weeks
after
the
current
version?
Like?
Is
that
good
enough
for
us
to
say?
Okay,
let's
go
ahead
and
cut
the
next
bug,
fix,
release
one
thirteen
two
and
then
push
that
out
to
all
of
the
up
streams,
Pantheon
and
darker
and
what-have-you.
C
Really
just
saw
that
most
okay
look
most
yeah
yeah.
We
have
one
issue.
That's
been
brought
up
here
in
the
agenda
that
we
have
a
an
issue
with
the
views
operator
in
when
you're
using
is
none
of
that
seems
to
have
been
broken
due
to
some
changes
that
we
pulled
over
from
Drupal
7
I
think
it's
issue
36
14
status,
for
that
one
is
that
we
have
a
solution
that
fixes
it,
but
that
we
need
tests
to
confirm
that
it's
actually
fixed
and
the
tests
are
actually
already
written.
C
We
just
need
to
re-roll
or
request
to
include
the
test
from
a
different
part
of
us.
Those
close
so
I
think
there
might
be
some
desire
that
maybe
we
can
fix
that
problem
before
113
2
is
pushed
out,
but
I'm
not
really
sure
that
we
should
wait.
You
know
like
wait.
Waiting
on
releases
seems,
like
you
know,
that's
a
bad
policy
to
get
into.
We
should
just
have
more
releases.
C
B
C
B
B
So
I'm,
not
sure
that,
with
whether
with
the
cross
boats
that
we're
gonna
do
eventually
we're
gonna
revert
the
change
that
we
made,
because
it
seemed
to
me
I
haven't
touched
Tedeschi
like
I,
haven't
looked
at
that
issue
for
like
at
least
two
or
three
weeks,
but
it
seems
to
me
that
we
might
be
preventing
the
changes
that
we
are
going
to
do
now.
I
might
be
wrong
thought
that
was
my
only
concern.
Yeah.
C
C
C
B
Okay,
splitting
those
tests
as
a
follow-up
to
the
37
ninety-three
thing,
the
ratio
that
I
mentioned
before
we
started
recording
how
about
fixing
the
the
issue
with.
So
it
happened
twice
or
three
times
already,
not
picking
up
the
the
up
data
being
blocked
because
they
was
being
the
proper,
proper
docking
profiles
with
the
type
thing.
So
we
need
to
fix
the
test.
We
had
three
separate
tests
or
layouts
modules
and
themes,
and
it
wasn't
taking
into
account
that
these
can
be
included
under
profiles.
So
he
wasn't
checking
the
slask
or
profiles
folder
at
all.
B
But
I
think
that
the
the
problem
is
that
this
happens
at
the
test
side,
but
the
updater
actually
does
check
up
of
house,
and
this
is
where
we
sort
of
like
come
up
with
don't
come
across
issues
with.
If
you
have
later
so,
I
think
that
we
should
make
the
tests
match
what
whatever
the
updater
is
doing.
A
B
That
would
cover
those
and
I
think
that
we
are
over
complicating
things
where,
whereas
we
could
be
just
taking
all
the
docking
profiles
everywhere,
but
I
need
direction
on
that
I
filed
a
pull
request
for
it
and
it's
green,
so
the
tests
pass,
but
I
was
kind
of
hoping
that
I
would
do
that
before
the
merge,
because
now
the
problem
is
actually
fixed.
So
we
don't
know
that.
So
we
needed
a
test
that
we'd
actually
pick
up.
The
problem,
yeah.
C
A
C
A
B
A
B
A
C
Like
so,
it's
still
no
it's
it's
the
same
thing
where
it's
like
it's
very,
very
similar
to
ienai
syntax,
but
it's
still
parsed
by
backdrops
like
Parsa
info
file,
but
it's
just
really
close,
but
you're
right
that
it
is
different
in
that
it
has
nesting
levels
in
the
tests
done
info
file
and
we
don't
have
nesting
in
all
of
the
other
types
of
projects.
Modules
themes,
my
own
yeah.
B
C
B
B
The
pull
request
is
actually
there
are
filed,
is
actually
removing
the
previous
and
replacing
them
with
a
generic
one.
That
says
test
project
info
file
content
instead
of
specific
thing
layout,
but
I'm
not
sure.
If
that's
the
right
way
to
go,
calling
me
that
nevertheless,
I
did
pick
up
six
six
files
that
were
missing
a
variant
that
will
not
pick
that
before
mm-hmm.
B
B
C
C
B
C
Great
well
sure
we
proceed
with
the
next
version
vector
of
114.
Yes,
okay,
so
let's
continue
planing,
but
let's
go
ahead
and
say
tomorrow
for
the
release
rather
than
today.
Now
that
I'm,
looking
through
the
queue
I
see
that
there's
also
one
PHP,
seven
point
three
issue
that
could
also
potentially
be
merged.
That's
trivial
that
would
be
nice
to
get
that
and
so
yeah
one
day
to
kind
of
get
some
of
these
things
tidied
up.
C
114
114
will
be
the
next
minor
version
of
backdrop
that
will
be
coming
out.
September
15th
2019
feature
freeze
on
September
1st.
We've
got
three
issues
that
we're
going
be
talking
about
as
having
focused
today.
The
first,
which
is
digital
signatures
on
packages,
issue
1992
once
again,
John
Franklin,
thanks
again
for
all
of
your
work,
which
has
been
accumulating
over
months
now
to
develop
the
code,
sign,
module
and
update
the
project
onto
the
bill
to
support
it.
C
This
past
week,
I
got
through
reviewing
some
of
the
changes
to
project
Montreux
issue
number
25
within
the
project.
Module
makes
it
so
that
the
project
release
XML
is
now
extensible
making
it
so
that
we
can
insert
code
sign
stuff
into
it,
rather
than
project
module,
just
creating
XML
and
then
not
having
any
ability
to
change
that.
That's
now
been
made
more
flexible
while
doing
the
card
deployment.
C
A
C
C
A
A
So
since
last
week,
I
grabbed
documents
for
request,
which
was
pretty
close
just
a
little
messy.
There
was
a
little
messy
because
triple
sevens
file.
Entity
solution
is
a
little
messy
and
so
I
wanted
specifically
to
focus
on
the
user
experience
part
of
it
and
try
and
take
the
very
strange
configuration
of
fields
and
turn
them
into
settings
forms
much
like
many
of
our
other
fields,
how
they
behave
and
so
far
I
have
rebased
the
pull
request
and
that's
it.
But
yeah
I
have
a
I,
have
a
plan
we'll
leave
it
at
that.
A.
B
So
that
needs
code
review
and
testing
and
perhaps
feedback.
Ultimately,
when
the
code
goes
in,
I
also
need
to
work
on
the
documentation
on
the
video
doors
I
just
around
this
new
feature
supported
and
I'm-
not
advocating
this,
because
it
does
bring
parity
with
Drupal
8,
but
at
the
same
time
it's
not
as
intrusive,
ultralight
or
should
I
say
as
restrictive,
and
it's
also
part
of
the
security
sort
of
like
meta
series
of
features
that
we
sort
of
like
like
to
focus
on
for
publishing
order.
B
B
C
B
A
A
Anything
to
like
I
know
there
are
people
who
are
really
passionate
about
specific
issues
that
may
not
have
time
right
now.
That's
okay,
if
you
want
to
add
your
name
to
an
issue
and
not
work
on
it
for
a
while.
That's
perfectly
fine
as
long
as
you're
planning
on
working
on
it
for
this
release.
That's
all
that's
really
necessary.
Also
I
know
they're
people
like
don't
know
what
you
should
choose
and
are
waiting
for
inspiration.
B
We
can
we
can
ask
that
question
though.
Luckily
people
that
are
locked,
beginning
picked
I
am
an
issue
just
say
who's.
Who
is
looking
for
issues
yeah
our
inspiration,
sucks
and
then
suggesting
to
them.
One
thing
that
I
would
like
to
point
out
not
specifically
for
114
but
towards
that
is
that
we
seriously
need
to
get
future
priority.
Sorry
sorry
commit
parity
with
the
viewers
thing.
There's
tons
of
commits
that
have
happened
in
between
so
I've
worked.
I
think
see
how
we
split
it
into
smaller
chunks.
B
B
A
A
C
B
I
started
because
I
want
to
work
with
smaller
issues
as
well,
that
are
feature
requests
and
they
don't
qualify
to
go
in
and
fix
releases,
so
so
either
for
those
ones,
work
or
ones
that
do
qualify.
I
started
putting
myself
as
an
assignee
and
started
working
on
them
just
because
I'm
bored
over
the
weekends
and
but
if
you
see
anything
assigned
to
me-
and
you
want
to
pick
it
up
just
you
just
go
ahead
and
do
it
because
sometimes
I
never
have
the
time
where
I'm
scattered
rain
dinner,
just
don't
return
to
that
or
pinging.
B
A
B
That's
mainly
because
see
that
the
vaishu
that
I'm
advocating
for
is
basically
waiting
for
someone
else
to
review
and
give
me
feedback,
and
that
is
not
happening
so
in
the
meantime,
I
do
want
to
work
on
other
things
and
there's
no
way
with
the
current
sort
of
like
policy
that
we
have
that
for
me
to
say:
yeah
I
don't
want
to
advocate
this
for
anymore,
because
I
want
to
work
something
else
and
I
return
a
locating
it
once
someone
has
provided
feedback.
That's
you
know,
anyways.
C
A
Yeah
I
asked
if
anyone
thought
we
should
number
one
add
things
to
that.
Milestone
like
I,
want
to
have
more
than
one
issue,
but
I'm
not
allowed
to
have
more
than
one
issue.
So
I
thought
this
might
be
a
loophole
where
I
could
have
one
issue
114
in
one
issue
and
115,
but
I
didn't
know
if
that
was
worth
it
and
then
I
also
thought
it
might
be
useful
to
indicate
to
the
world
sort
of
not
only
what
our
priorities
for
the
next
four
months
over
our
parish.
A
A
C
A
Let's
see
again
a
general
discussion,
okay,
this
is
an
interesting
question
that
came
up.
This
is
issue
number
38
22
and
the
question
is:
should
there
ever
be
a
situation
in
core
where
the
question
in
the
user
interface
will
override
the
themes
ability
to
change
it?
So
in
the
world
of
Drupal,
the
theme
always
wins
the
conversation
of
like
Oh.
A
A
B
So
so
he
was
herb
that
suggested
that
these
go
into
the
same
settings.
Similarly,
to
the
way
that
we
add
color
support,
for
example
in
themes,
and
it's
a
good
idea
if
you
look
at
it
from
a
developer
perspective,
but
what
I
would
like
to
do,
but
I
see
same
possible
hint
is
that
if
you
have
a
setting
in
the
user
interface-
and
you
somehow
have
the
ability
to
know
which
team
is
being
used,
then
if
this
has
been
overridden
like
settings,
do
not
show
that
setting
in
the
UI
does
that
make
sense.
Yeah.
A
B
Other
words:
we
have
a
setting
just
to
make
it
to
bring
an
example
so
that
we
make
it
clear.
So
we
have
this
issue
where
we
are
trying
to
add
the
backdrop
logo
and
have
two
versions
of
it:
a
black
on
white
and
white
on
black
there's,
a
setting
that
Peter
has
added
to
the
powered
by
Blue,
Book
and
I
thought:
okay,
let's
test
this,
but
when
I
tested
it
if
the
changes
weren't
reflected
in
the
theme
basis,
because
it
doesn't
have
support
for
it.
B
A
I
think
the
way
that
I
have
handled
this
in
the
real
world
is
when
athene
breaks
a
setting.
I
used
the
altar
in
the
theme
and
I
do
a
form
altar
and
I
disable
that
on
that
particular
block,
and
we
could
do
that
and
in
poor.
We
could
do
that
in
basis
where
we
know
basis
doesn't
support
that
we
can
turn
it
off.
We
can't
do
it
in
a
way
where
all
of
the
forms
are
automatic
and
they
can
tell
it
in
the
same
theme
is
over
in
them
or
not.
A
I
still
think,
because
the
theme
comes
after
core.
The
theme
needs
to
make
that
call
I
also
like,
in
all
of
my
backdrop,
themes
I
often
form
alter
the
block,
form
and
add
description
text
to
the
classes,
to
let
people
know
what
classes
are
available.
So
I
am
a
big
alter
ER
in
my
themes,
which
is
maybe
not
common,
but
it
is
possible
to
do
that.
A
Another
thing
I
was
thinking
too,
is
that
we
could
just
make
sure
that
all
of
these
settings
that
were
introducing
in
core
path,
support
and
basis,
and
so,
if
we
do
add
office,
definitely
just
make
basis
a
good
example
of
like
how
to
deal
with
this,
and
then
anyone
who
wants
to
do
a
contributing
basis
don't
make
it
really
complicated,
like
maybe
not
such
a
good
base
theme,
but
at
least
there's
an
example
there
for
people
to
follow.
If
they
don't
want
it,
they
can
remove
it.
So.
B
B
So
if
they
feature
like
say
a
drop-down
menu
or
something
in
core
relies
on
such
support,
then
we
could
be
taking
which
things
support
it
and
then
have
a
thing
other
than
if
it
says
likes
to
supports
this.
But
if
you're
using
any
other
thing,
you
want
series
or
something
like
that
or
make
it
disappear.
It's
making
it
disappear
from
the
electric
additionally
showing
those
controls.
Those
UI
controls
depends
on
like,
like
with
the
simplest,
the
simplest
huge
cage
will
be
better.
B
A
A
I
think
I
think
it's
an
interesting
conversation
to
have
in
terms
of
the
perspective
of
either
experience,
but
I
think
that
most
of
the
technical
solutions
are
sort
of
not
viable.
From
an
assumption
standpoint.
Both
of
you
also
just
mentioned
multiple
themes,
Nate
added
a
comment
into
the
chat
that
said
that
your
theme
has
to
be
active
on
the
admin
side
in
order
for
it
to
work
on
the
admin
forms.
Great
so,
like
my
form,
alters,
don't
work
unless
it's
the
same
theme
on
the
back
is
on
the
front
and
that's
also
ridic
pretty
uncommon.
A
Now
the
back
job
has
an
admin
team.
That's
pretty
good
I
would
imagine
most
people
leave
that
admin
team
as
the
admin
theme
and
then
at
your
front-end
theme
would
never
affect,
like
your
blog
configuration
settings,
because
those
are
always
using
admin
team,
so
yeah,
it's
definitely
a
bit
messy
and
it
that
same
thing
would
apply
if
it
was
a
theme
setting
right
anything
that
your
theme
is
tonight
as.
B
A
A
A
Like
like,
almost
every
setting
can
be
ignored
by
a
theme
and
hard-coded
like
you,
you,
for
example
like
what's
your
custom
block
title.
Oh
you
just
put
in
a
template
file
and
you
hard-coded,
so
printing,
the
title
of
them
now,
that's
irrelevant,
so
I
think
it's
this.
Is
it
wet
slippery
slope
where,
if
we
just
say
your
theme
always
wins,
it's
very
easy
for
people
to
understand.
It
was
from
the
theme
or
cyber
they're
like
okay,
now
I
always
override
the
things
they
don't
like
and
you
can
I
think.
B
Sorry
one
thing
to
consider:
they
say
there
is
that
people
that
have
access
to
those
settings
and
not
like
singing
it
on
the
level
of
sort
of
like
the
user.
As
you
have
content
or
authors,
they
will
not
come
across
these
things,
so
the
people
that
will
be
coming
across
those
things
would
be
site.
Builders.
They
know
not
necessarily
have
a
coder
background,
but
they
might
sort
of
like
understand
how
internals
work
this
does
not
apply
both
to
newcomers
like
people
that
come
from
WordPress
would
not
know
how
to
pause
and
backtrack
for
you.
B
B
A
A
A
B
A
A
Yeah,
okay,
maybe
I'll,
started
on
and
dropped
on,
blacktip
CMS,
org
and
then
I'll
leave
it
in
some
kind
of
unfinished
state
and
anyone
who
has
any
time
he
wants
to
jump
in
and
like
it
screenshots
or
fix
words
or
bad
stuff,
he's
looking
to
cause
that
them
then
they'd
still
be.
There
wants
something.
So
we
make
a
release.
Soonish.
A
A
A
It
alright
well
there's
nothing
else,
then:
let's
go
ahead
and
wrap
this
meeting
and
we
will
meet
again.
Next
Thursday
is
the
backdrop
minicamp,
and
so
it
is
not
very
likely
that
Nate
and
I
will
or
Tim
will
be
around
to
run
the
meeting.
But
if
anyone
else
wants
to
run
the
meeting,
we
do
have
a
document
on
how
to
do
it.
We
just
need
to
make
sure
we
get
you
set
up
with
access
to
the
backdrop
YouTube
thank.