►
From YouTube: Backdrop Weekly - Dec 5th 2019
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
A
All
right,
well,
the
assumed
says
for
on-air.
So
today
is
Thursday
December
5th,
and
this
is
our
weekly
meeting
for
backup
CMS.
Here
we
usually
talk
about
development
tasks
and
other
various
things
that
come
up
up
for
the
week
last
week
we
sort
of
had
a
meeting,
but
nobody
showed
up.
So
we
didn't
finish
it
because
we
didn't
adequately
announced
that
there
would
either
definitely
be
or
not
be
a
meeting.
So
those
of
us
in
the
United
States
were
celebrating
Thanksgiving.
A
So
that's
probably
why
most
of
us
weren't
there
and
then
non-communication,
is
why
the
non-us
sirs
weren't
there.
So
apologies
for
that.
We
did
enjoy
our
holiday
nonetheless,
this
week,
because
we
had
a
week
off
last
week,
there's
a
whole
bunch
of
great
stuff
happening,
which
is
great
as
far
as
community.
There
are
three
new
people
who
have
created
contributes
this
week.
Stern
Hegel
created
image
field,
caption,
Matthew
Connerton
had
poured
abuse
field
view
a
while
ago,
but
finally
moved
it
into
the
contributory.
A
She
was
great
so
thanks
for
that
and
bought
the
Christians
and
I
think
is
ported
one
module
before,
but
this
week
also
did
use
selective
filters.
So
a
lot
of
progress
there
and
speaking
of
module
being
lay
out
progress.
This
week
we
also
had
five
or
in
the
past
two
weeks,
we've
had
five
new
releases:
Instagram
feed
unit
user
reference,
URL,
widget
security
review,
a
Facebook
page
plug-in
in
one
page
navigation.
So
lots
of
people
doing
lots
of
great
work
over
the
holiday,
which
is
great
I'd
like
to
turn
it
over
to
Nate.
B
They
throw
a
fatal
error
when
they're
left
blank,
which
is
a
kind
of
a
big,
potentially
data
loss,
type
situation
where,
if
you're,
creating
a
piece
of
content
and
the
site
fatal
Zevon
you
because
you
left
a
field
blank,
that's
not
good,
so
issue.
38
73
is
actually
already
arts.
Bc
I'll
try
to
take
a
look
at
it
after
the
meeting
and
get
that
merged
in
views.
Cross
ports
are
something
that
we
bring
up
every
week
issue
36
85
we're
trying
to
keep
pace
with
Drupal
7
views
module.
B
There
hasn't
been
any
updates
to
any
of
those
issues,
though
that's
a
great
area,
if
you're
looking
to
contribute,
though
36
85,
is
the
issue
that
just
has
a
bunch
of
some
issues
for
porting
things
over
from
Drupal
to
backdrop
and
there's
a
lot
of
work
to
be
done.
They're
just
moving
things
across
there's
another
big
meta
issue
for
flexible
templates
new
feature
was
added
in
vector
114.
The
big
meta
is
40.
B
46
I
went
through
all
the
sub
issues
there,
which
there's
about
a
dozen
or
so
and
found
a
couple
of
items
that
need
review
issue.
4104
Gregory
has
been
working
on
this
neat
feature
that
makes
it
so
that,
as
you
create
a
layout,
it
will
make
an
icon
to
match
the
layout.
So
it
creates
a
custom,
tiny
little
thumbnail
using
GD
to
represent
what
that
layout
actually
looks
like
it
needs
a
little
bit
more
work.
B
I
posted
some
comments
on
that
that
it
could
be
optimized
a
little
bit,
but
some
other
feedback
from
other
people
would
also
be
appreciated,
and
another
issue
related
to
flexible
templates
that
needs
review
is
issue.
41,
61
Jenna
actually
posted
this.
A
couple
of
weeks
ago,
making
adding
a
feature
to
make
it
possible
to
disable
flexible
layouts
for
sites
that
don't
want.
It
currently
needs
review.
B
Let's
see
that's
those
are
the
only
ones
that
have
had
any
activity
on
the
flexible
templates,
so
I'll
move
on
to
the
next
issue,
which
is
this
issue
that
Olaf
brought
up
before
the
meeting.
It's
not
actually
in
the
114
milestone
yet
because
there
are
different
approaches
that
could
be
taken,
but
its
issue
41
58,
that
the
XSS
filter
it
mangles
title
and
alt
attributes
which
can
affect
the
way
the
certain
characters
are
out
put
in
an
alt
tag
that
is
issue
41
58
need
feedback
and
testing
on
the
approaches
that
have
been
suggested.
B
There's
two
different
approaches
that
have
been
put
out
there.
They
touch
on
some
of
the
main
security
filtering
functions
within
backdrop,
and
so
we
need
some
technical
expertise
to
take
a
look
at
that.
If
you're
familiar
of
that
system,
the
please
provide
feedback
issue.
There
are
other
issues
in
1:42,
like
I
said:
I
was
working
through
them
earlier
today,
there's
still
a
bunch
more
that
need
looking
at
there's.
B
B
Alright
first
issue
that
we've
got
is
adding
an
image
library
modal
to
image
fields
issued
3297
Lauren
is
not
here
today,
although
he
did
post
status
updates
in
here
and
I'll.
Just
read
it
out
since
I
haven't
had
a
chance
to
look
at
this.
Unless
someone
else
is
familiar
with
this
issue
and
would
prefer
to
give
the
update,
ok,
I'll,
just
read
it
then
okay,
so
status
is
Graham.
72
has
made
progress
on
an
alternate
pull
request
which
opens
in
a
modal.
B
That's
great
functionality
is
not
all
in
place
yet
and
I've
posted
some
preliminary
comments
on
the
forward
quest
itself:
Graham
72
added
a
file
name
filter
to
the
core
image
library
view
and
I've
added
an
exposed
sort
for
date
and
name
up
for
discussion.
This
works
in
the
new
modal
pop-up
he's
working
on,
but
breaks
the
functionality
in
the
WYSIWYG
modal
image.
Modal
for
some
reason.
There's
a
related
issue,
re-exposed
filters,
breaking
the
WYSIWYG
image
library
at
issue,
32
93;
here's
a
quick
screencast
demo
walkthrough
of
the
current
status.
Oh,
that's
awesome!
B
B
B
Well
still,
this
is
interesting.
This
part
here
or
select
from
the
image
library
visually
is
a
very
large
element.
This
seems
like
we
may
need
some
UX
work,
probably
just
deciding
the
way
things
should
look
a
little
bit,
but
it's
great
functionality
looks
like
it's
coming
along,
really
well,
I'm
really
excited
to
see
it
in
the
modal
I
think
that's
a
big
improvement
from
previously.
It
was
just
like
right
there
in
the
middle
of
the
page.
B
B
B
B
B
Okay,
give
the
thumbs-up
all
right
next
up
move
the
contents
of
the
manage
file
display
page
issue,
40:31
Jen
you're,
the
ad
kit,
for
this
says
no
update
since
last
meeting.
Okay
keep
rolling
along
I'll.
Just
next
up
is
Gregory.
He
was
in
the
last
meeting
that
was
here
prior
to
starting
the
recording
/
running
a
way
to
rename
disabled
text
formats.
This
one
continues
to
be
really
close,
but
he
says
that
there
hasn't
been
any
updates
since
the
last
meeting.
B
Next
up
is
my
issue.
Digital
signatures
on
packages
issue
1992
I
also
have
no
updates
to
reports
again
like
we
have
project
module
and
can't
read
I'm
sorry
code
signing
can't
rip
now,
there's
no
official
release
but
I'm
working
separately,
an
issue
queue
over
there
and
me,
but
it's
interested
in
helping
collaborate
on
that.
You
can
go
over
to
the
code,
sign
back,
drop,
contribute
and
trip
project
and
start
working
on
those
issues
that
I've
been
filing
over
there.
B
A
B
B
B
Okay,
it
looks
like
so
I
posted
a
comment
three
weeks
ago
saying
that,
if,
if
we're
only
interested
in
making
it
better
for
to
trigger
possible
for
to
trip
to
make
forward
revisions
right
now,
it's
it's
ridiculous.
You
have
to
jump
through
a
whole
bunch
of
hoops
to
make
it
possible
to
have
a
forward
revision
and
not
publish
it,
and
my
suggestion
is
that
perhaps
we
just
make
it
so
that
we
simplify
that
and
make
it
a
lot
easier
for
it
contribute
and
Allah
problem
of
forward
revisions
and
dark
moment
says
that
sounds
reasonable.
B
So
his
is
a
pull
request,
is
pretty
simple
already
but
adds
a
checkbox
for
like
make
this.
The
active
revision
that
I
personally
found
to
be
slightly
confusing
that
you
would
uncheck
that
checkbox
and
then
it
makes
basically
an
unpublished
version,
but
how
that
interacts
with
like
scheduler
starts
getting
confusing.
A
B
B
First
up
is
a
couple
of
weeks
ago.
There
were
a
number
of
modules
on
drupal.org
that
were
marked
unsupported
by
the
security
team
and
we
have
the
Drupal
security
team
and
we
have
a
couple
of
those
modules
also
existing
within
the
backdrop
contribute
so
what
happens
in
the
backdrop
contribs
base
when
a
module
is
might
unsupported
within
the
gerbil
space.
C
A
D
A
And
a
lot
of
people
got
notices
about
those
modules
being
unsupported
and
a
bunch
of
issues
got
opened
and
all
the
triple
Q
is
going.
Oh,
no.
What
do
I
do
I
need
this
module
and
I've
been
told,
I
can't
use
anymore
and,
at
the
same
time,
a
whole
bunch
of
people
stepped
up
and
said
I'm
willing
to
maintain
X
module.
A
I
know
I
was
using
three
advanced
ported
modules
on
some
sites
that
I'm
working
on
and
I
picked
up,
all
of
them
and
all
of
them
had
people
recommending
they're
offering
to
be
new
maintainer,
except
for
one
so
I
figured.
It
looks
like
none
of
those
modules.
We're
gonna,
be
unsupported
for
very
long.
I
ended
up
volunteering
to
do
the
other
ones.
I
knew
that
that
one
wasn't
gonna
be
unsupported
either
so
for
modules
that
aren't
gonna
be
unsupported,
I,
don't
think
it.
A
What
our
reaction
in
backdrop
should
be
any
different
from
any
other
security
release
where
we
know,
there's
gonna
be
security,
release
in
the
next
week
or
two
or
whatever,
and
so
we'll
just
wait
for
that
to
happen
and
then
handle
it.
The
same
way,
we
do
security
releases
for
batch
job
for
a
lot
of
those
modules.
A
30
days
and
after
30
days,
the
security
fix
or
the
security
issue
becomes
public,
and
then
we
would
get
anyone
in
the
world
can
get
access
to
what
the
issue
is
and
we
can
produce
a
fix
really
quickly.
On
the
backdrop
side,
so
if
you're
not
interested
in
maintaining
a
Drupal
version
of
the
module,
but
you
are
interested
in
maintaining
the
backdrop
version,
there's
a
30-day
waiting
period
between
when
the
module
gets
marked
unsupported
and
when
the
release
gets
publicized,
and
so
we
would
just
need
to
be
part
of
that
waiting
period.
B
B
That
the
current
situation
is
that
we
can
still
have
these
mod.
The
modules
can
be
maintained
on
the
backdrop
site
and
not
maintained
on
the
Drupal
side.
If
you're
not
willing
to
become
or
the
backdrop
maintainer
x'
aren't
willing
to
become
Drupal.
7
maintain
yours
when
that
window
is
complete,
like
those
issues
will
become
public,
so
will
actually
know
them
and
then
the
backdrop
maintainer
can
fix
the
issue
and
make
any
release.
B
A
Know
it
seems
only
fair
to
do,
is
fix
this.
You,
like
you,
don't
have
to
do
anything
else
in
the
Drupal
module,
so
to
be
a
maintainer
project.
Oh
you
are
you
gonna
collaborate
with
a
security
team
if
there's
a
security
issue,
because
a
lot
of
these
triple7
projects
are
sort
of
you
know
mostly
in
and
the
only
thing
that
really
matters
is,
if
there's
a
security
issue,
so
that's
all
they're
looking
for
and
if
that's
what
you're
gonna
do
today
anyway,
because
that's
what
you
want
to
do
for
your
backdrop,
project.
A
In
my
case,
I
took
over
node
Q
and
I
had
been
doing
a
ton
of
work
on
the
backdrop
Bertino
anyway,
so
they're
really
searchable.
I
included
a
bunch
of
really
minor
user
interface
changes.
So
it's
not
entirely
abandoned
like
there's
so
many
who
are
happening
but
yeah,
you
don't
have
to
agree
to
do
all
of
the
work
on
the
Drupal
project.
Oh,
you
have
just
security
issues
as
they
come
up.
C
C
The
API,
for
that
is
no
longer
gonna,
be
supported
very
shortly,
and
it
hasn't
been
maintained
that
the
module
hasn't
been
maintained
or
updated,
and
so
he
was
first
like
what
should
we
do
about
it?
And
then
he
went
ahead
and
created
a
new
module
based
on
something
to
burn,
and
so
then
the
question
became:
what
do
we
do
with
this
old
module
that
might
not
be
working
anymore?
C
How
do
we
handle
that
there's
and
it's
somewhat
theoretical,
because
usage
stats
show
one
to
three
people
using
that
module
and
I
know
I'm,
one
of
them
so
I'm,
not
sure
if
anybody
else
is,
but
in
theory
like
how
do
we
handle
a
scenario
like
that?
Where
we
know
a
module
is
broken
or
based
on
a
broken
API?
Do
we
have
a
policy
for
deprecating
that,
or
the
discussion
was,
do
we
unpublish
it
from
backdropped
org
and
then
just
leave
it
and
get
hub
for
somebody
that.
A
A
Well,
to
answer
the
question:
we
have
a
maintenance
status
option
on
dr.
of
module
seams
and
layouts,
and
so,
if
something
becomes
unmaintained,
we
can
mark
it
as
such,
it's
actually
called
unsupported.
So
that
would
be
one
way
to
indicate
to
people
that
the
module
you're
using
isn't
going
to
be
supported
anymore.
I
would
also
recommend
putting
something
in
the
info
file.
That
says
you
know
this
module
is
not
gonna
work
right,
so
that
people
who
are
using
it
if
they
go
to
the
project
page
or
the
github
repository
will
see.
A
Like
you
know,
Instagram
API
has
been
abandoned
or
whatever
is
causing
that
module
not
to
work
anymore
and
then
I,
don't
think
we
have
a
way
to
automatically
link
different
projects
together,
like
this
one's
a
recommended
next
alternative,
but
I
would
put
that
in
the
info
file
too
so
like.
If
you
know
we
have
a
new
module
that
works,
this
old
one
isn't
going
to
you
could
say
this
module
is
unsupported.
Here's
the
one
that
we
recommend
and
that
way
a
file.
B
A
B
Addition
to
that,
just
like
Drupal
modules,
we
have
the
ability
to
specify
the
recommended
version
like
if
a
new
version
comes
out
version,
1
versus
version
2.
We
can
edit
the
note
on
backdrop.
Cms
Dorgan
say
that
you
know
version
1
is
no
longer
supported,
or
in
the
case
of
like
completely
unsupported
module.
We
say
none
of
the
versions
are
supported
and
what
that'll
do
is
update
status
will
then
put
a
big
flag
on
them
on
the
sites
that
are
running,
that
module,
saying
you're
running
a
module
is
no
longer
supported.
A
B
A
B
B
B
B
B
Okay,
well,
while
you're
working
that
out
Jen
we
can
go
to
the
next
item-
is
that
okay,
yeah,
okay,
so
the
next
item,
100
of
fun,
to
talk
about
is
Port,
something
like
CTools
to
ease
the
process
of
porting
modules.
There
already
is
a
backdrop
contribs
module,
but
it
is
a
placeholder
basically
documenting
how
or
why
you
shouldn't
use
ctools
in
backdrop.
So
her
module
made
this
a
nice
module
that
is
actually
just
to
read.
Me
I'll
share
my
screen
again,
just
to
show
you
guys
what
this
looks
like
here.
We
go
so
so.
B
There's
no
reason
to
install
this
module
array.
However,
that
doesn't
mean
that
it's
necessarily
easy,
so
I
think
the
key
will
item
here
is
plugins.
I
might
be
wrong
that
maybe
some
of
these
other
things
are
still
clickable,
but
I
think
you
know
it
covers
the
way
that
backdrop
deals
with
these
things
and
a
lot
of
them
definitely
have
full
replacements.
Like
X
portables,
we
have
config
management
modal's.
B
We
have
built-in
modal's
that
sort
of
thing
make
it
so
that
you
know
we
don't
need
a
lot
of
these
same
things,
but
plugins
are
conceptually
just
a
very
different
concept
that
if
we
recap
real
quickly
what
a
plug-in
actually
means
in
C
tools.
It
is
a
file
that
you
create.
That
has
a
set
of
functions
inside
of
it,
and
it
also
has
a
declaration
kind
of
like
an
info
hawk
that
provides
information
about
what
that
plugin
is
and
then
CTools
can
automatically
discover
that
thing
and
all
the
other
things
like
it.
Like
a
try.
B
B
Plugins
were
desirable
because
in
concept
you
put
all
of
the
code
related
to
something
all
in
one
place,
as
opposed
to
an
info
hook,
which
is
in
one
place,
and
then
the
file
that
contains
the
code
is
in
a
second
place.
So
the
only
thing
that
a
plug-in
really
does
is
it
does
both
of
those
things
at
the
same
time,
so
yeah
we
have
this
documentation
on.
B
You
know
backdrop
uses
info
hooks
and
callback
functions
instead
of
plugins,
because
conceptually
if
these
two
things
are
two
different
ways
of
solving
the
same
problem,
we
should
do
it
all
either
one
way
or
all
the
other
way
and
what
happened
with
Drupal
8
is
that
they
decided
that
plugins
were
the
way
to
go,
and
that
resulted
in
a
massive
massive
refactoring
of
just
about
all
info
hooks
into
plugins
and
considering
it
like
considering
the
impact
that
that
has
on
backwards
compatibility.
That's
something
that
we
wanted
to
avoid.
B
However,
we've
got
this
batch
of
control
projects
that
does
use
plugins
and
doesn't
use
info
hooks.
So
now
we're
in
this
conundrum,
where
we
want
consistency,
but
we
also
want
backwards.
Compatibility
with
Drupal
7
modules
that
have
you
been
using
plugins,
so
I
think
your
suggestion
was
that
potentially
we
make
some
kind
of
C
tools,
alternative
module
or,
like
maybe
just
a
subset,
maybe
just
like
C
tools-
plugins
module.
That
makes
it
easier
for
people
moving
from
Drupal
7
support
their
modules
to
back
trip
without
having
to
do
this
plugins
to
info
hook,
conversions.
B
A
Could
do
something
that
was
like
a
wrapper
that
would
like
take
a
see,
tools,
plug-in
and
run
it.
The
way
see
tools
would
have
run
it
or
even
see.
Jules
could
do
that,
but
the
problem
with
that
is
that
Oh
like
at
some
point,
the
modules
gonna
need
to
be
converted.
I
mean
it
I.
Guess
there's
nothing
wrong
with
having
it
like
we
had
what
was
that,
like
it
Andy
we
had
some
weird
entity,
middle-ground
module
right
until
we
got
the
support
we
needed
in
core
for
converting
entities
over.
A
And
you're,
not
it
so
address
fields.
Let's
see
I
did
so.
I
did
two
modules
that
took
me
a
long
time
to
port
I
just
filled
with
one
of
them
it
took
about
a
week
and
meta.
Tex
was
the
other
one.
I
don't
think
meta
tags
had
siege
was
plugins,
but
maybe
it
did,
it
could
have
had
like
I,
don't
remember,
but
it
would.
It
would
have
made
sense
if
it
did
the
way
in
it.
A
The
way
it's
structured,
and
it's
really
like
it's
complicated
like
in
terms
of
what
you
have
to
do
mentally,
like
the
gymnastics
to
be
like.
Oh
I,
just
have
to
copy
that
like
get
info,
subclass
like
method
or
I
have
to
like
copy
this
random
array
from
the
top
of
the
file
into
an
info
hook.
But
what
you're
changing
is
actually
very
little
about
the
module
you're
just
taking
the
array
turning
an
info
hook
and
then
info
hook
pointing
to
the
other
file.
A
So
the
amount
of
actual
code
change
that
happens
between
the
two
is
rather
minimal.
So
I
put
in
the
in
the
agenda
like.
Would
it
be
possible
for
code
or
upgrade
to
do
those
kind
of
conversions
like
it
seems
like
since
the
code
changes
rather
minimal?
You
would
just
create
an
info
hook
that
has
everything
from
the
array
and
we
could
give
it
some
examples.
I
mean
I,
don't
know
the
problem.
Is
it?
A
Ctools
is
a
little
like
use
it
for
anything,
but
there
are
some
common
patterns
that
we
could
put
in
there
and
see
if
it
matches
this
pattern.
This
is
what
your
info
look
like
and
just
point
at
the
file
where
the
other
one
is
common
out.
The
array
definition
the
top
and
then
see
I,
haven't
tried
doing
any
work
on
code
or
upgrade
module,
so
I'm
not
sure
how
complicated
that
sort
of
change
would
be,
but
in
my
mind
conceptually
it
seems
like
it
should
be
possible.
A
B
B
A
A
I
also
have
some
documentation
that
I
started
to
write
up
when
I
was
doing.
Some
of
these
conversions
I
have
one
little
bit
of
documentation
and
they
came
from
address,
be
a
little
documentation
that
came
from
something
else
that
I
converted
where
it
was
the
same
thing
where
you
sit
down
in
here.
Like
oh
geez,
it's
a
siege.
Whole
thing,
it's
gonna
be
hard,
but
once
you
kind
of
wrap
your
brain
around
how
the
mapping
works,
the
actual
code
change
was
not
that
hard.
A
B
Like
I,
haven't
looked
at
go
to
upgrade
recently
either,
but
I
know.
Carter
upgrade
has
the
ability
to
not
necessarily
change
everything
but
flag,
Y
numbers
and
just
say,
and
just
link
to
documentation
and
saying
you
know
this
doesn't
work
anymore,
but
try
this
and
then
link
to
documentation
and
I
think
maybe
that
by
itself
would
be
a
big
improvement.
If
we,
if
we
don't
have
that
already
receipt,
ool's.
B
So
I
don't
know
this
might
not
be
what
people
want
to
hear.
But
you
know
what
sounds
like
this
discussion
is
trending
towards.
We
need
better
documentation,
not
another
module
that
actually
provides
a
mapper,
and
maybe
that
would
you
know
we
can
build
tools
to
help
make
those
conversions
easier,
but.
B
Providing
a
wrapper
I
mean
wow
possible.
We
really
want
to
get
people
off
of
using
these
plugins
in
the
first
place,
because
it's
creating
a
split
in
the
mental
processes
of
how
backdrop
modules
are
written.
It's
like
dude.
Are
they
written
with
plugins
or
are
they
written
with
info
hooks
and
we're
trying
to
say
everything
it
uses
info
hooks.
D
B
B
We're
not
going
to
too
many
details.
There
are
some
pending
things
in
our
security
queue
that
also
need
to
be
cleared
out,
and
so
we
need
I
think
it
would
be
preferable
of
us
to
get
those
out
at
the
same
time
as
the
next
release.
So
so
yes
there'll
be
a
release
because
we
are
starting
to
accumulate
a
large
number
of
fixes
and
also
we
have
a
couple
of
security
fixes
that
are
basically
ready
to
go.
So
so
yes,
I,
think
that's
it
does
have
anything
else.
You
guys
would
like
to
discuss
to
talk
about.