►
From YouTube: Backdrop Weekly - Oct 4th
Description
Today’s development agenda: http://bit.ly/2QeEfv0
A
All
right
we
are
on
air,
it
is
Thursday
October
4th,
and
this
is
a
weekly
developer
check.
In
for
backdrop,
Cygnus
starting
off
the
top
of
the
meeting
I
want
to
thank
Graham
72
for
all
his
fantastic
work
on
Bach
Jeff,
Kent
rib
he's
got
another
contributed
project
released
this
week:
beauty
tips,
API
and
Symphony
ones.
He's
teasing
beauty
tips
on
Drupal
7.
That
salable
will
for
backdrop.
A
So
thanks
Graham
for
working
on
that
and
usually
Nate
would
be
here
to
do
our
rundown
of
backdrop,
core
issues,
but
he's
got
another
meeting
at
the
same
time
today.
So
I
don't
know
Jeff.
If
you
wanted
to
run
cities,
if
you
would
rather
I,
do
it,
but
Nate's
already
been
to
the
agenda
and
had
a
little
updates
to
each
issue.
A
Jeff
doesn't
want
me
to
do
it,
alright,
so,
starting
for
backdrop,
one
11.0,
it
looks
like
there
are
no
critical
updates.
That
would
require
us
waiting
on
pushing
that
release
to
upstream.
So
we
can
go
ahead
and
do
that.
I
know
on
my
agenda.
I
think
it's
the
docker
image
or
any
of
the
other
up
strings
like
Pantheon,
where
platforms
are
probably
ready
to
get
updated
as
well.
A
For
backdrop,
one
11.1,
we
are
currently
scheduling
a
tentative
release
date
for
next
Wednesday,
October
10th,
so
Jeff
I'm
not
sure
here
around
next
Wednesday,
but
that
is
when
we
will
be
doing
our
next
bug
fix
release
and
that
will
include
hopefully
a
couple
of
predefined
color
schemes
for
basis.
There's
issue
3209,
where
that's
getting
reviewed,
there's
a
pull
request.
A
We
do
end
up
with
enough
contrast:
I
don't
know
what
the
opposite
of
that
would
be,
so
just
to
make
sure
that
everyone
can
read
it
clearly,
but
that
would
be
really
good.
It's
great
that
we've
got
some
default
color
schemes
going
in
there.
The
next
issue
is
our
color
preview
tool.
So
when
you're
changing
colors
and
basis,
if
you're
in
Safari,
the
preview
is
inconsistently
working,
so
there's
an
issue
for
that.
A
3295
I
think
there's
some
version
information
there,
for
which
version
of
Safari
that's
presenting
an
issue
on
so
we'll
just
need
to
use
that
browser
stack
or
something
to
confirm
that
that's
an
issue
and
if
so,
figure
out
what
a
solution
might
be
for
it
again.
It's
not
mission-critical,
but
it
would
be
great
if
we
get
that
fixed
by
next
Wednesday.
A
Anyone
is
curious
about
what
other
issues
we
have
going
on
in
111
one.
There
should
be
a
milestone
on
backdrops,
AMS,
org
queue
or
sorry.
Effective
CMS
choose
queue
to
track
that
anything.
We
can't
get
fix
late
then
it
would
be
great
if
not
it'll
just
get
bumped
to
the
next
bug
fix
release
alright.
So
for
backup
112,
this
is
our
next
minor
release.
It's
scheduled
to
come
out
on
January
15th
2019,
which
will
be
backdrops
fourth
birthday
right.
A
Yeah
we've
got
a
couple
of
interesting
issues
on
the
horizon
around
core
updates.
In
this
last
version
of
backdrop,
we
put
in
a
core
Update
button,
but
it
is
currently
disabled,
there's
no
easier
interface
for
it.
So
for
the
next
release,
we
want
to
turn
on
that
user
interface
that
people
can
go
ahead
and
use
the
button
to
update
their
sites.
It
looks
like
we
haven't,
had
any
progress
since
last
week,
but
there
is
a
pull
request.
That's
getting
worked
on,
I,
don't
know
Jeff.
If
you
have
any
updates
on
that.
One
for
us.
A
I'm,
just
gonna,
okay,
a
couple
other
things
we're
working
on
like
package
signing.
This
is
something
we'll
need
to
get
done
before
we
do
automatic
updates.
It
would
be
great
if
we
could
get
it
done
before
manual
updates
that
I,
don't
think
that's
a
necessity,
and
then
another
part
of
the
karate
issue
is
to
deprecate
authorize,
dot
php'.
It
looks
like
we
have
a
pull
request
where
most
of
the
authorization
has
been
removed,
but
there's
also
a
filed
transfer
system.
That
was
pretty.
A
That
was
previously
used
only
by
the
update
mechanisms
that
we
can
also
remove
to
get
some
work
craft
out
of
core,
so
that'll
probably
be
a
follow
up
issue
to
get
that
out
there
and
that
also
won't
be
required
to
do
by
112.
We
could
probably
get
that
done
at
any
time
after
the
deprecation
of
whopper
a
subpage.
He
goes
in
there.
Actually,
that
might
have
to
be
another
follow-up
that
comes
much
later,
because
if
we're
using
the
file
transfer
system
for
something
that's
deprecated,
it's
entirely
possible.
A
There
are
other
things
that
are
using
it
while
it's
deprecated,
so
it
probably
shouldn't
be
removed
until
off.
There's
that
PHP
is
removed
entirely,
but
you
can
do
some
cleanup
all
right,
so
that's
it
for
core
updates.
We
have
another
issue.
One
of
our
longest-standing
high
priority
issues
is
issue
number
37
for
tags
for
modules.
There
is
a
pull
request
on
that
issue.
It
does
need
review
and
feedback,
so
just
some
people
to
test
the
sandbox.
A
Try
the
modules
page
see
if
the
addition
of
tags
makes
sense
see
if
the
tags
that
were
added
makes
sense
to
you
to
try
and
find
particular
modules.
That
issue
really
just
includes
a
new
setting
on
the
info
file
for
all
core
modules
that
will
have
less
filter
the
modulus
on
the
modules
page
but,
more
importantly,
those
tags
for
modules
will
also
be
used
on
backdrop
semester
or
when
you're
searching
for
modules
and
in
your
module
installer.
A
A
What
this
does
is
it
actually
transforms
that
massive
text
field
into
a
bunch
of
individual
fields
where
you
can
define
the
every
item
on
an
individual
row,
and
if
you
want
to
define
the
keys
it
gives
you
specific
ability
to
do
that
gives
you
the
ability
to
automatically
determine
the
keys
based
on
the
strings.
It's
a
lot
more
of
an
intuitive
interface
than
just
a
giant
text
area
and
what
we're
working
on
is
taking
that
options,
element
module
and
putting
it
directly
in
core
for
all
fields
in
backdrop.
A
So
if
you
create
a
field
that
would
be
a
select,
let's
check
boxes
or
radio
options,
it
would
include
the
it
would
include
this
form
element,
and
this
one
element
would
also
then
apply
to
webform.
So
the
Drupal
7
control
only
works
for
webform,
and
this
is
expanding
it
to
work
for
chord
fields
as
well.
In
backdrop,
so
that's
issue
1005,
it
looks
like
there
is
a
pull
request
that
was
recently
updated
and
it
just
needs
more
revealing.
A
So
if
anyone
wants
to
take
a
look
at
that,
sandbox
I
think
that's
gonna,
be
huge
usability
improvement,
I'm
really
looking
forward
to
it.
Getting
me
next
issue
is
something
that
we
have
long
identified
as
being
necessary
for
a
backdrops
file
system,
and
this
is
feel
the
bull'
files
pipes.
So,
for
example,
if
you
wanted
to
have
an
image
that
would
have
a
photographer
credit
and
caption
on
it
and
maybe
a
PDF
that
might
have
a
date
and
field
those
fields
are
different.
A
We
need
to
be
able
to
distinguish
the
difference
between
the
PDF
and
an
image
and
add
those
different
fields
to
each
one.
So
that's
something
that
we've
been
working
on
for
a
while.
It
had
been
slated
for
a
couple
of
earlier
core
minor
releases,
never
got
done
and
got
bumped.
Now
we
have
a
version.
That's
done
this.
It
again
is
issued
26:32.
A
It
would
be
great
if
we
could
get
a
bunch
more
review
on
that
before
it
gets
merged,
but
it
does
look
like
it's
definitely
going
to
make
it
for
112.
So
this
helps
us
get
a
little
closer
to
thing,
including
file
entity,
which
was
a
kinship
module
in
Drupal
7.
In
for
for
backdrop,
it
also
gets
us
a
little
closer
to
what
media
provides
for
Drupal
7,
so
it'll
help
us
flush
out
our
media
handling
in
backdrop
to
get
us
a
little
closer
to
an
ideal.
A
We
only
talk
about
the
highest
priority
issues
in
this
meeting,
but
if
you're
curious
about
other
stuff
that
we've
got
in
the
queue
there
is
a
milestone
for
112
on
github,
everyone
is
welcome
to
check
out
and
if
anyone
wants
to
know
we're
working
on
longer-term,
you
do
have
a
road
map
page
on
backdrop,
CMS
org
inspector
see
my
Stewart
slash
road
map
and
we
should
have
a
rough
outline
of
features
that
we
want
included
in
the
next
version
there,
as
well
as
stuff
that
wanting
to
look
every
previous
version
so
yeah,
it's
not
super
nailed
down
yet
because
obviously
people
can
still
have
great
ideas
between
now
and
January
and
we'll
put
those
in
if
we
can
but
a
general
guideline.
A
Is
there
all
right?
That's
all
I
have
for
backdrop
core.
If
there
isn't
anything
from
anyone
else,
we
can
move
on
to
backdrop
for
good
I.
Don't
know
if
you
have
a
quick
update
for
us
here.
Jeff
at
last,
we
spoke
about
it.
Looked
like
it
was
moving
along
nicely.
There
is
an
issue
queue
on
github.
Anyone
who
has
time
to
contribute
to
that
project
is
welcome
to
participate
in
grab
an
issue
assign
it
to
yourself
or
bust
okay.
A
Next
up
and
probably
our
most
exciting
discussion
for
today,
under
the
general
discussion
section,
we
have
a
bullet
here
to
talk
about
contribute.
Itíll
is
follow,
WordPress,
like
policies,
but
this
is
specifically
relating
to
licensing
for
kinship
projects.
So
Taryn
I,
don't
know
if
you
want
to
give
a
little
introduction
here.
C
Well,
hopefully,
it's
not
that
exciting,
because
I,
don't
I,
don't
think
there's
as
much
controversy
here
as
there
has
been
in
Drupal
regarding
this,
so
the
drupal
policy
is
to
remain
compatible
with
GPL
to
for
everything
hosted
from
drupal.org
from
concord
to
contribute
and
at
the
distribution
level.
This
has
always
been
very
problematic
because
there's
a
lot
of
common
modules
that
require
non
GPL
to
compatible
code
to
be
added
as
an
additional
step
and
with
Drupal
8
and
composer.
C
That
becomes
a
lot
easier
to
to
install
as
part
of
the
it
isn't
they
download
this
specific
release
from
here
and
uploaded
into
your
libraries
folder.
It's
all
happening
the
same
way
that
the
builds
are
happening.
So
the
conversation
has
shifted
a
bit
that,
with
distributions
the
ability
to
prepackaged
all
the
things
someone
would
want
to
use
becomes
problematic
because
you
can't
include
like
the
amp
library
from
Google
as
licenses
Apache
too,
and
so
you
can't
include
that,
so
you
can't
actually
enable
that
functionality
by
default
in
a
distribution.
C
You'll
find
all
kinds
of
GPL
3
only
and
Apache
to
code
in
their
modules
and
their
modules
are
the
in
the
standard
and
processes
a
lot
more
like
what
backdrop
expects,
where
someone
downloads
the
the
project
from
from
github
or
from
WordPress
and
then
uploads
it
into
their
site,
and
the
hope
is
that
all
of
the
pieces
come
with
the
initial
download.
So
it's
not
a
big
hassle
to
go
and
find
additional
things
and
get
those
uploaded
to
the
right
right
places.
C
So
this
ties
in
to
look
like
some
of
the
conversations
about
hacks
and
Elementor
as
alternative
editing
interfaces.
Elementor
requires
an
Apache
2
license
library
that
is
included
and
can
be
installed
for
WordPress
from
the
UI,
but
for
drupal
it
has
to
be
a
multi-step,
install
and
I'm
guessing
the
backdrop
you
would
want
it
to
be
an
easier
install
process.
C
So
it
there's
definitely
like
a
lot
of
documentation
regarding
this
not
being
illegal,
not
being
a
violation
of
the
GPL
and
I
completely
understand
keeping
backdrop
core
GPL
2
compatible
to
remain
with
the
same
license
as
Drupal,
but
for
the
contribs
like
it
would
make
more
sense
to
adopt
WordPress
as
policies
regarding
licenses.
Amen
stick
with
with
drupal's,
so
I
posted
the
issue.
Everyone
who's
commented
has
been
in
favor
of
clarifying
that
and
I.
Don't
really
know
if
there's
anything
else
needed
for
the
PMC.
C
A
B
A
If
we
want
the
next
version
of
the
backdrop
module
to
contain
the
latest
version
of
a
library,
we
are
going
to
run
into
this
licensing
conflict
and
there's
also
documentation
a
couple
different
places
that
contradicts
itself.
So
in
some
places
we
say:
choose
whatever
license.
You
want
GPL,
two
or
three
for
your
kinship
and
then
other
places.
A
We
say
you
must
install
the
GPL
2
license
file,
so
I
think
this
might
be
something
we
already
thought
about
and
just
haven't
made
clear
to
everybody
what
the
decision
is
on
how
the
license
can
share
projects
and,
where
atlas,
what
the
decision
is.
That
needs
to
be
made
clear
number
one
but
number
two
I
think
now
that
we
have
some
real-world
scenarios
where
we
can
see
how
it'll
affect
us
to
make
a
more
restrictive
licensing
requirement
here,
it
will
shed
some
light
on.
C
You
can
still
require
that
the
PHP
written
for
the
the
module
B
license
is
GPL.
It's
the
distribution
clause,
and
this
is
where
Drupal
doesn't
didn't
want
to
cut
hairs
regarding
JavaScript,
a
lot
of
JavaScript
doesn't
even
have
to
be
open
source
license
to
be
packaged
in
distributive
a
GPL,
because
it
only
runs
on
the
client
side,
there's
no
cross
memory,
resource
utilization
and
it
doesn't
even
use
Drupal's
api's,
and
so
the
the
decision
in
the
Drupal
community
was.
C
We
didn't
have
the
resources
to
try
to
vet
all
of
these
requests
as
to
how
the
JavaScript
is
actually
used.
So
we
just
had
a
blanket
statement
across
the
board,
for
all.
Javascript
must
also
it
concluded
in
a
module
must
also
follow
these
these
rules.
But
you
can
you
try
to
be
more
granular
with
the
difference
between
distribution
and
what
what
the
PHP
people
are
writing.
So
that
is
another
option.
C
It
is
a
confusing
option
and
one
that
WordPress
chose
not
to
not
to
go
with
so
I
think
we're
WordPress,
that,
like
the
activity
and
like
lack
of
barriers
for
people
to
get
started
and
get
things
out
in
front
of
other
users
and
share
their
code
freely
like
speaks
a
lot
for
the
that
approach,
working
well
versus
Drupal's
previous
power
requirements,
and
then
these
very
restrictive
licensing
requirements,
kind
of
hindering
the
the
innovation
that
happens.
A
trim
layer,
yeah.
A
That's
also
a
great
point
so
where
we
are
with
us
right
now,
I
opened
a
issue
for
the
PMC
to
review
Kevin's
issue
which,
if
you're
interested,
is
issue
number
294
in
the
back
drop,
can
shred
Sheol
but
I
think
that
we
should
get
its
assertion
quickly
and
then,
hopefully
clarify
all
the
documentation
about
how
you
can
license
to
your
kingship
projects
so
that
it's
not
contradicting
itself
in
two
different
places.
C
Posted
a
sneak
preview
of
what
alex
has
been
working
on
for
us
to
leverage
the
hidden
path-
nodes.
Okay,
I'm
super
super
excited
about
this
so
but
I'm
not
gonna
ruin.
His
he's
put
a
lot
of
work
into
this,
so
I'm
not
gonna,
not
gonna
spill.
Everything
he's
been
working
on,
but
that's
those
with
something
look
forward
to
and
we
neglected.
We
shifted
gears
a
bit
after
getting
our
initial
blog,
install
up
and
running
and
haven't
been
adding
the
content
to
that.
C
But
we
hope
to
get
that
done
in
the
next
week
or
so,
and
then
we
should
put
ourselves
on
whatever
list
there
is
to
be
nagged
and
nudge
to
actually
create
content.
So
if
there's
a
sign-up
for
people
to
create
content
as
far
as
a
Content
schedule,
let
us
know
and
we'll
happy
to
have
people
encourage
us
to
do
what
we
already
said.
We
were
going
to
do.
C
A
C
A
I
think
the
big
takeaway
for
today
is
that
PNC
has
to
review
the
issue
for
licensing
and
can't
read
just
to
make
sure
that
that's
clarified
and
hopefully
is
open
and
at
least
roadblock
II
as
possible
for
our
community,
but
yeah
I
think
everything
else
is
sort
of.
As
expected.
This
week
we
do
again
a
reminder.
We
are
going
to
have
a
bug
fix
release
next
Wednesday
October
10th.