►
From YouTube: Backdrop Weekly - July 9, 2020
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
We
are
on
air,
it
is
Thursday
July
9th,
and
this
is
our
weekly
backdrop
for
developer
meeting
before
we
get
into
the
agenda.
I'd
like
to
have
everybody
go
around
and
introduce
yourselves
say
where
you're
from
and
if
you
have
something
that's
not
on
the
agenda,
you
want
to
share,
feel
free
to
go
ahead.
Rick
you
are
in
the
talk
left
again.
Would
you
like
to
introduce
yourself
first.
A
D
E
Okay,
look,
maybe
I'm
Luke
mcCormick
I'm
in
San,
Ramon,
California,
I'm,
leading
an
initiative
called
be
ready
to
weary
of
letting
intent
is.
Is
that
I've
back
drop,
easy
to
use
out
of
the
box
and
I
have
a
webcam
on
a
baby
bird
or
a
nest?
That's
that's
growing
in
my
foyer
and
you're
monitoring
that
for
exciting
developments.
D
Sorry
I
thought
I
had
turned
off
my
camera,
while
I
was
moving
there,
I
am
Tim
Eriksson
I'm
reporting
from
near
Deerwood,
Minnesota
and
I
have
been
away
for
a
bit
and
over
the
last
week,
have
been
trying
to
get
back
into
the
flow
here.
I
don't
have
any
issues
I'm
advocating
for
right
now,
so
my
goal
is
to
get
figure
out
what
I
want
to
work
on
for
the
next
release,
so
that
I
have
things
to
bug
you
about
in
future
meetings.
A
All
right
we
have
community
member
who
supported
the
cache,
exclude
module
from
Drupal,
7,
D
bond
or
depandi
or
depandi
I,
don't
know
anyway,
new
github
member
who
looks
like
maybe
their
first
community
contribution,
so
I've
posted
a
comment
in
the
queue
trying
to
help
guide
them
through
the
process
of
getting
that
project
onto
github
and
into
the
vector
of
kinship
queue,
but
I
did
say
for
fester
replies
to
try
its
dilip.
So
if
anyone
sees
this
person
show
up
and
do
look
asking
for
help,
please
help
also
new
contributed
project
updates.
A
This
week
we
have
four
new
contributed
modules,
which
is
great.
We
have
the
big
blue
button,
which
I
saw
people
chatting
about
this
past
week
in
Zulu,
so
great
job.
Getting
that
one
out
menu,
item,
visibility,
lateral
and
node
feedback
are
all
also
out.
They
believe
lateral
is
a
new
theme,
so
we're
getting
a
bunch
of
a
new
theme,
so
I
think
it's
also
really
great
yeah,
that's
exciting.
C
Okay,
so
backdrop,
one
16.3
is
the
next
bug-fix
release
of
backdrop,
and
we
have
a
lot
of
issues
that
we've
been
working
on
to
just
generally
improve
the
stability
of
our
current
release.
So
one
issue
that
is
probably
one
of
the
higher
priority
things
is
issue:
40
407,
a
visual
regression
in
the
text.
Format
order
on
the
text,
format
settings
overview
form.
This
is
a
regression
from
115
that
when
we
redid
the
UI
for
editing
text
formats,
we
also
have
this
regression
in
the
way
that
text
formats
are
displayed
that
they're
out
of
order.
C
When
you
go
and
look
at
the
list
of
them
so
issue,
40
407
still
doesn't
have
any
pull
requests
or
anything
behind
it.
Yet
so
we
need
a
developer
to
take
a
look
at
that
issue
and
submit
a
pull
request
to
try
to
get
that
fixed
I.
Don't
even
think
that
it's
particularly
hard
to
show
I
just
think
that
nobody's
had
time
to
take
a
look
at
it.
Yet
so
44,
our
seven,
not
beat
support,
request,
see
next
issue.
We
have
restored
views
pager
by
date,
issue
27
66.
C
This
makes
it
so
you
can
sort
items
and
page
them
by
things
like
month,
so
you
could
say
previous
month
next
month
and
a
views
pager
and
it's
been
reviewed
a
couple
of
times.
It
might
be
ready
to
move
to
our
TBC
dr.
Elmont
came
in
and
compared
it
or
applied
the
core
change
combined
with
the
control
and
didn't
have
any
issues
with
it.
I
think
that
there
might
be
some
hesitation
there
that
perhaps
more
testing
would
be
valuable
before
that
gets
moved
to
our
TBC
so
2766.
C
Let's
see
speaking
of
views,
we
have
this
big
meta
issue:
36
85
for
views
cross
boards
pulling
in
all
of
the
patches
that
have
been
applied
to
the
Drupal
equivalent
version
of
views.
I
think
that
it
would
still
be
valuable
if
we
have
extra
time
like
these
are
good
issues
to
simply
apply
in
mass,
that
you
take
the
Drupal
seven
patch
reapply
it
and
then
make
pull
request
for
it
back
drop,
and
we
have
several
versions
of
views
that
we
need
to
catch
back
up
to
just
cuz
every
now,
and
then
we
get
an
issue.
C
C
Let's
see
next,
we
have
PHP
CS
automated
code
checks.
That's
the
suggestion
here
in
issue.
32
13
is
that
when
we
file
a
pull
request,
we
should
have
automatically
apply
linting
rules
to
identify
things
like
if
you're
using
tabs
instead
of
spaces
or
where
your
new
lines
are
and
that
sort
of
things
so
issue.
C
32:13
is
currently
still
in
discussion
mode
about
ways
that
we
could
potentially
apply
linting
to
the
backdrop
project.
Let's
see
the
last,
we
check
this
github
released
a
generic
linting
tool
called
that
they
call
the
super
linter.
It
did
get
PHP
supports
two
weeks
ago,
but
it's
not
really
very
comprehensive.
It's
just
like.
Does
your
PHP
code
have
any
syntax
errors
in.
A
C
C
C
Little
bit
back
ssin,
that
would
be
pretty
cool
and
a
nice
way
to
handle
things,
but
anyway,
that's
basically
still
kind
of
in
research
phase
about
what's
the
best
way
to
proceed
with
with
that
kind
of
capability
to
our
infrastructure.
C
A
E
A
A
A
C
I
think
that
sounds
like
a
very
good
place
to
put
it
because
it's
relevant
to
people
that
are
interested
in
security.
You
know
if
they
go
to
backdrop,
semester,
learning,
slash
security,
probably
interested
in
knowing
what
security
updates
we've
had,
what
kind
of
practices
we
follow.
I
think
that
would
be
a
good,
reasonable
place
to
put
it
deep.
B
A
E
A
A
B
E
C
B
C
Yeah,
but
my
concern
is
that
there
are
a
crap
ton
of
badges
available
for
like
putting
on
your
github
repository
and
I
think
that
it
just
becomes
noise
like
you
know,
I'm,
not
sure
what
value
we're
really
delivering
by
having
a
string
of
badges
along
the
bottom
and
I'm
sure
that
there's
ones
that
are
more
valuable
than
others.
And
my
comment
in
the
issue
is
that
I'm,
probably
somewhat
tainted
by
the
era
of
like
the
90s,
where
you
put
the
string
of
badges
at
the
bottom
of
your
website.
C
That
said,
like,
oh,
this
site
was
built
with
Clara's
homepage
and
its
best
on
Netscape
Navigator
on
a
Macintosh.
You
know
it's
just
like
it
just
had
this
whole
string
of
buttons
that
down
at
the
bottom,
that
was
just
like
kind
of
cliche
and
I.
Think
that
that's
what
that's
the
vibe
I'm
getting
from
like
repository
buttons
in
general,
is
that
I
see
projects
that
have
like
16
buttons
along
the
bottom
and
I'm.
Just
like.
C
Like
each
one,
the
badges
means
something
but
sometimes
I'm,
just
not
sure
if
it's
like
some
kind
of
campaign
to
increase
backlinks
to
the
provider
of
the
button.
You
know-
oh
my
god,
I
love
that
skepticism
there
too
and
I.
Don't
think
that's
the
case
for
this
particular
one
but
I,
don't
know
I'm
just
a
little
wary
of
them.
C
It's
like
when
we
we
have
the
powered
by
weird.
We
already
do
kind
of.
In
a
way
we
have
the
powered
by
backdrop
block
that
is
enabled
of
the
box.
It's
kind
of
funny
that,
like
when
we
ported
that
from
Drupal
7,
you
remember
we
got.
We
got
rid
of
all
the
images
because
they
used
to
have
actual
image
badges
that
were
there
in
the
Drupal
7
era,
or
maybe
that
was
even
Drupal.
6
era,
yeah
they're,
just
kind
of
out
of
vogue.
C
A
A
C
C
Yeah
I
actually
I
like
that.
This
idea
of
it's
possible
that
badges
will
provide
value
but
put
it
like
just
throwing
them
all
and
the
readme
might
not
be
the
right
solution.
You
know
that
every
time
a
new
patch
comes
up,
it's
like
well,
let's
try
to
find
the
right
place
for
that.
You
don't
make
a
whole
badges
MD
file
and
just
put
all
your
badges
in
it.
C
Okay,
that's
what
we've
got
for
the
116
three
lists.
117
is
a
next
minor
version
of
backdrop.
It
will
be
coming
up,
September
15th,
with
feature
free,
September
1st.
We
currently
have
two
issues
like
I.
Have
a
new
one?
Add
it
as
of
this
week
for
emphasis
in
that
release,
and
first
one
is
one
gem
that
you're
advocating
for
issue
44
10
using
an
admin
theme
for
the
login
forms.
Can
you
give
a
status
update
on
that
issue?.
A
So
I
think,
where
we're
at
right
now
is
that
it
works
great.
Except
for
that,
if
you
make
the
change
and
then
visit
a
page
it
doesn't,
it
doesn't
show
the
change
right
away
because
the
cache
does
need
to
be
cleared.
So
my
next
step
was
to
force
a
catch
clear
all
after
the
setting
was
changed,
and
that
was
accidentally
do
that.
C
B
So
you're
mrs.
yes
or
the
response
yeah.
So
the
issue
that
you
mentioned
with
the
field
set
jumping
up
and
down.
That's
that's
a
known
issue.
It
happens
with
anything
that
goes
at
the
bottom
of
the
page,
but
yeah.
So
my
only
concern
there
is
that
I
can
file
a.
Let
me
rephrase
everything
just
get
my
thoughts
on
doping.
B
Would
you
like
me
to
file
a
new
request
and
Bree
purpose,
and
we
title
that
issue
or
close
that
issue
in
or
keep
it
open
and
field
and
raise
a
separate,
so
we
can
test
both
Thanks
and
the
other
thing
is
that
if
we
remove
it
completely,
people
now
have
an
easy
way
to
just
click.
One
thing
and
say:
I:
don't
care
just
use
the
same
thing
always,
whereas
now
you
would
have
to
select
specific
administration
in
and
then
select
another
one
option
and
then
then
speech
you
with
a
login
adds
another
tick
box
there.
B
So
it's
like
three
options
that
go
away
with
a
single
click
that
now
will
be
on
people's
faces
all
the
time:
yeah
I'm,
okay,
I'm,
okay,
with
filing
a
separate
pull
request
to
also
see
because
I
think
that
the
recommendation
will
simplify
the
code.
So
it
might
that
in
itself
might
be
a
compelling
reason
to
do
it.
But
yeah
yeah.
C
I
think
a
separate
request,
but
in
the
same
issue,
so
okay,
it's
like
a
different
alternative,
because
I
think
that
we're
going
to
do
one
or
the
other
and
not
both.
You
know,
because
Sookie's
are
alternatives
to
each
other
and
it's
up
to
all
of
them
are
about
that
terminology
of
use
default
theme.
You
know
as
an
option
the
Select
list
so
yeah.
So.
B
B
They
had
an
option
that
no
matter
how,
with
which
thing
they
changed
to
be
the
admin
theme,
sorry
that
the
fault
thing
that
would
always
be
used
for
the
admin
theme,
and
now
they
have
to
do
two
things:
select
the
default
change
the
default
theme
and
update
the
admin
theme
and
most
likely
those
checkboxes
as
well,
the
one
for
the
content,
editing
and
the
one
for
the
login
screen.
Yeah.
C
Because,
because
the
way
it
is
right
now
out
of
the
box,
we
already
say
that
seven
is
the
administration
theme
and
there's
different
theme
bases
as
your
front-end,
and
so,
if
you
wanted
to
make
basis,
be
used
for
both
of
them.
You'd
have
to
change
two
options
right
now,
anyway,
you'd
have
to
first
change
your
default
theme
to
something
else,
and
then
you'd
have
to
go
down
and
you'd
have
to
change
the
administration
thing
from
seven
to
use
the
default
theme.
When
you
also
could
just
as
easily
say
you
know,
use
the
current
theme.
C
B
C
B
C
B
No,
the
issue
that
you're
thinking
now
and
this
came
to
mind.
Students
do
use
the
words
that
you
were
saying
previously
is
the
one
that
removing
the
notion
of
disabled
themes
right.
So,
yes,
you
would
have.
You
would
have
a
list
of
things
that
are
available
in
the
system
and
then
you
will
have
to
pick
another
thing
and
a
default
thing
and
that's
it
in
other
words,
and
maybe
not
called
a
default.
But
then
again
front-end
seems
to
think
King
thing.
C
Okay,
so
the
new
issue
that
we
have
for
this
week
is
that
document
has
picked
up
an
issue
to
advocate
issued
3750
and
I
haven't
fully
wrapped
my
head
around
it
yet.
But
the
title
of
the
issue
is
custom
contexts
for
layouts
and
from
what
I've
read.
My
understanding
is
that
this
would
allow
contexts
to
be
created
and
stored
in
CHEM
fake,
like
config
files.
C
So
I
think
the
idea
is
that,
right
now
we
have
contact
in
layouts
for
like
your
on
a
node
or
your
on
a
user
page,
and
it
makes
it
so
that
you
can
place
fields
from
a
node
inside
of
the
layout
and
I
think
what
this
is
about
is
making
it
so
that
there
can
be
user-defined
context
that
aren't
necessarily.
This
is
on
this
node
or
I'm,
sorry
on
any
node
or
on
any
user,
but
I
don't
exactly
understand
the
full
details
of
it.
Yet
so.
A
This
is
a
copy
of
the
custom
context
that
were
available
for
panels
where
you
could,
for
example,
be
on
a
landing
page
that
was
created
with
layouts.
That
doesn't
have
any
context,
and
you
could
say,
make
the
context
for
node
14
available
on
this
page,
and
then
you
can
add
all
the
fields
from
node
14,
the
page
that
wouldn't
normally
have
had
that
context.
You
can
add
a
context
to
an
existing
page.
I,
see
I,
see
yeah.
C
So
that
means
that
you
could
make
it
pull
it
out
of
nowhere,
but
you'd
have
to
provide,
unlike
the
current
context,
handling,
which
says,
get
a
parameter
from
the
URL
like
get
the
node
ID
and
then
load
the
context.
For
that
you
would
have
to
then
provide
or
say
what
mechanism
you
want
to
use
to
provide
the
parameter
into
a
context.
A
C
A
It
was
an
argument
that
was
an
option
so,
like
you
could
say,
it's
node
ID
you
pull
from
r3
or
you
could
say
like
I'm
on
a
page
for
node,
12
and
I.
Want
you
to
add
a
term
context.
The
term
ID
is
in
the
tags
field.
So
it
would
let
you
chain
contexts
together,
where
you're
on
a
node
context
and
you're,
adding
the
term
context
formerly
to
term
yeah.
C
A
A
C
Anyway,
the
issue
3750
seems
like
it's
going
to
add
a
lot
of
capability,
or
maybe
just
groundwork,
for
more
capability
to
layouts,
which
is
highly
appreciated
and
and
continues
to
make
layouts
like
you
know,
one
of
the
central
features
of
backdrop,
so
that
issue
currently
needs
review.
As
a
poll
request,
that's
working
and
put
together
and
yeah
more
discussion
and
more
eyeballs
would
be
appreciated
on
issue
3750.
A
Another
thing
I'd
like
to
just
start
out
there
is
that
this
week,
I
did
a
like
proof
of
concept
of
how
to
build
things
in
Tripoli
and
I
used
panels
and
was
really
disappointed.
That
panels
did
not
have
any
of
this
context.
Support
in
Tripoli,
even
though
it
had
it
in
triple
7,
so
I
think
if
we
can
get
this
context,
support
that
panels
had
in
Drupal
7
into
core
and
backdrop
it'll
make
backdrop
a
much
more
powerful
layout
tool
than
Drupal
II.
It
has
available
to
it
at
the
moment
and
I.
A
C
C
C
C
A
B
A
A
A
So
I
feel
like
how
did
how
to
make
this
data
a
publicly
available
display.
It
should
be
like
the
last
thing
on
our
list,
like
I,
think
we
need
to
figure
out
what
we're
collecting,
how
we're
collecting
it,
where
we're
storing
it
before
we
figure
out
what
we're
how
it
gets
displayed
to
people,
but
I
wonder
if
his
solution
isn't
also
tied
up
and
all
of
that
other
stuff.
A
So
I
don't
know
that
would
be
good,
but
then
also
my
follow-up
question
was
like
what
can
the
rest
of
us
do
like
what
he's
still
working
on
this
I
noticed
that
I
think
it
was
you
jumped
in
doc,
Loma
jumped
in
and
I
wanted
to.
Don't
like
it
like.
We
have
this
list
of
things.
A
We
want
to
collect
you
from
sites
while
he's
working
on
the
infrastructure,
to
figure
out
like
how
we're
managing
data
would
it
be
helpful
to
have
the
rest
of
us
right
like
some
kind
of
plugin
or
hook
or
something
that
would
collect
that
information
like
during
cron?
Or
what
can
we?
How
can
we
be
helpful
to
him
while
he's
doing
other
things
so
I
know
if
he
has
a
plan
for
that
yet
or
not.
A
Yeah,
we
also
have
anything
that
has
an
advocate
question
mark
I'm
here.
I'm
thinking
about
I
have
a
lot
of
a
lot
of
little
tiny
things
that
have
been
bothering
me
lately
and
drop,
and
I
was
thinking
about
I've
just
advocated
for
this
one
thing
that
I'm
hoping
will
get
done
quickly
but
I'm
thinking
about
making
like
a
medalist
of
like
here's
like
15
little
tiny
things.
I
want
to
clean
up
and
run
it
by
you
guys
and
be
like.
A
Are
these
good
can
like
core
candidates
for
the
next
release
or
not,
and
then
I'm
not
sure
that
none
of
those
would
be
really
exciting
enough
for
like
a
blog
post
or
something?
But
they
would
really
make
me
happy
if
we
got
them
done
and
I
think
they'd
be
small
enough,
it
would
be
easy
to
take
on
it.
A
B
A
A
B
So
we
have
other
issues
raised
for
replacing
that
menu
selection
the
norm,
at
least
with
some
sort
of
menu
tree,
which
is
something
more
like
once
it's
out
of
the
way.
The
weight,
the
stupid
weight
thing
I
think
it's
it's
the
next
step
to
pursue,
but
that
would
be
a
bigger
sort
of
like
goal,
but
from
what
I'm
reading
the
respected?
Indeed
org
issue
they've
done
some
usability,
tastings
and
yeah
people
get
confused,
it's
not
usable,
so
they
were
moving
it
and
reading
through
that
issue
made
sense
to
me
as
well.
B
B
C
B
Yeah
I'll
do
that
that's
one
of
the
other
annoying
things,
but
it's
not
in
the
UI
d,
XD
yeah
I'm,
not
not
yet
I'm,
not
sure.
If
the
functions
that
are
calling
the
I
think
it's
called
being
list
themes
and
it's
called
tasting
list
separate
for
the
projects.
So
we
don't
have
anything
for
layouts.
So
this
kind
of
annoyances
is
blowing
the
some
functions.
Yeah,
there's
some
long,
lasting
ones
like.
C
A
C
C
E
For
one
for
the
first
time
in
several
weeks,
I'm
not
driving
while
I'm
trying
to
give
me
the
update.
So
that's
that's
that's
a
step
in
the
right
direction.
So
so
I'm
boldly
like
doing
stuff
and
and
then
you
know,
open
to
suggestions
and
corrections
later
on,
but
I
I
guess
a
lot
of
it's
wrapped
in
I
put
into
the
the
agenda.
I
created
a
sandbox
site
on
Pantheon
for
the
initiative.
E
A
E
Right
well
like
like
it
until
there's
a
reason
not
to
I'll
just
leave
it
like
that,
and
basically
the
approach
that
I'm
taking
to
just
try
to
try
to
power
through
to
MVP
is
to
create
a
site
that
the
demos
themes
I
installed.
The
content
theme
module
that
lets.
You
apply
a
different
theme
to
each
content
type
and
then
I'm,
just
creating
a
content
type
for
each
theme
and
applying
it.
So
that's
it
so
that
so
that
we
can
create
I
can
create.
E
E
Presentation
ready
themes,
they
the
backup
themes,
I,
can
find
there's
a
small
list
that
I've
turned
through.
You
know
a
few
of
them
as
we
kind
of
start
discussion
like
okay,
like
look
how
close
yeah
I
mean.
This
is
literally
the
low-hanging
fruit.
Well,
once
we've
once
we're
able
to
kind
of
quickly
a
be
compare,
different
themes
try
to
try
to
get
a
sense
for
how
close
this
is
to
to
where
we
can
push
things
out.
I
anticipated
getting
2/3
of
the
way
they're.
E
You
know
what
to
look
the
same
and
and
a
long
way
by
by
creating
a
sample
site
I
want
to
unearth
the
the
other
things
that
they
come
to
play.
You
know
layouts
and
content
and
various
other
pieces
of
information
that
we
need
to
know
to
really
understand
this
topic
area
which
might
lead
into
you
know
how
to
docs
or
menus
or
bundling
things
and
there's
a
bunch
of
content
tool
related
issues
that
have
popped
up
as
part
of
this.
E
Any
other
place
is
what
we're
think
she
up
and
in
do
and
the
issue
queue
and
things
like
that
as
it
may
well
be.
The
other
thing
that
I
wanna
sort
of
arbitrarily
announce
slash
proposed
is
is
I
want
to
have
a
weekly
meeting
for
anybody,
who's
interested,
which
might
just
be
me
and
I,
want
to
do
that
Wednesday
evening,
Pacific
time
so,
and
I
wanna
throw
that
out.
E
B
C
E
That's
probably
probably
better
pressure,
so
they
I'm
gonna
throw
that
in
as
one
suggestion
they.
You
know
trying
to
imagine
using
my
schedule
like
what's
the
farthest
away
from
this
time,
that
could
still
work
for
me
just
to
see
if,
if
that,
if
that
pulls
in
people
who
haven't,
haven't
been
participating
in
the
noon
meetings
because,
for
whatever
reason,
just
doesn't
work
for
them.
This.
B
B
A
E
Okay,
so
that's
that's
kind
of
the
summary
those
those
two
things
there
there's
a
site
there
there's
a
time.
I'm
gonna
do
some
sprinting
on
it
tomorrow,
I,
don't
anticipate
that
you
know
no
announcement
or
anything
that
it'll
be
anybody
with
me.
But
if
anybody
was
curious,
I'll
be
working
on
it
tomorrow
afternoon.
B
C
C
A
C
C
I'm
not
sure
that
there's
a
setting
inside
at
oh
boy
to
automatically
delete
previews,
we
use
a
cron
job
that
back
top
CMS
door.
It
keeps
track
of
the
ID
so
if
they
took
both
previews
that
are
created
and
then
on
cron
jobs,
it
loops
through
the
ones
that
are
old
and
deletes
them,
and
so
it's
possible
that
deletion
code
might
not
be
cleaning
things
up.
I
checked.