►
From YouTube: Backdrop Weekly - May 21st 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
A
A
On
the
agenda,
there's
a
lot
of
stuff
going
on
in
the
pnc
issue,
keel
of
conversations
but
I,
don't
think,
there's
anything,
that's
ready
for
announcements,
so
just
chatter,
which
is
exciting.
However,
mm-hmm
in
the
contributed
project
world.
We
have
two
new
releases
since
last
week,
so
resaved
nodes
and
invite
module
both
got
their
first
stable
releases
out.
So
thank
you,
everybody
for
continuing
work
on
Jim
and
Nate.
B
So
we
did
some
changes
or
deployed
some
changes
that
had
been
queued
up
in
project
module
and
the
peripheral
modules
around
that,
including
github
API
and
the
custom
board
github
integration
module
and
we
made
some
changes
to
the
packager
that
the
packager
now
can
exclude
certain
files
and
right
now
is
excluding
files
related
to
CI
integration
when
a
package
is
created.
So
that
includes
as
NCI
amo
files,
Travis
CI
llamo
files,
github
actions,
yellow
files,
all
of
those
things
that
are
related
to
the
tooling
around
using
the
repository
and
the
CI
integration
stuff.
A
B
That
in
project
module
project,
module
now
has
a
hook
that
allows
modifications
to
take
place
and
the
modifications
are
in
the
or
github
modules
that
specify
what
our
exclusion
list
is.
Okay,
cool
and
so
yeah
I
had
been
talking
or
thinking
about
making
it
so
that
backdrops
packager
had
its
own
yeah
mole
or
JSON
file
that
configured
how
the
packager
would
work
like,
excluding
certain
files
kind
of
like
get
ignored
for
the
packager.
B
But
that
can
be
a
later
thing
if
we
decide
that
it
needs
to
be
flexible.
For
now,
it's
just
a
hard-coded
list
of
pretty
much
every
CI
platform
out
there,
oh
and
like
tugboat
and
stuff
like
that,
and
so
the
opportunity
that
affords
us
is
that
it
makes
it
so
that
we
can
manage
our
own
CI
processes
better
for
the
core
projects.
Probably
freaking
trip
to
I
saw
a
lot
of
control.
Projects
are
trying
to
set
up
Travis
CI
for
complicated,
automated
testing,
but
for
core
it
provides
us.
B
The
opportunities
where
right
now
is
NCI
is
promoting
our
sandboxes
and
Zen
C
is
providing
our
our
automated
testing,
but
the
configuration
of
like
what
PHP
version
we're
running
and
other
things
is
hard
to
find
and
hard
to
change.
And
now
we
can
start
moving
those
llamó
files
for
configuring,
how
the
automated
testing
works
directly
into
the
core
repository
without
cluttering
up
people's
downloads
of
the
of
the
zip
files.
B
So,
anyway,
it's
it's
affording
us
some
opportunities.
Oh,
and
we
laid
the
groundwork
of
getting
package
signing
put
in
place
that
the
new
version
of
project
module,
supports
code
sign,
but
code
sign
isn't
yet
on
backdrop.
Cms
tour!
Yet
so
anyway,
we're
moving
along
on
a
couple
of
fronts,
which
is
exciting.
B
B
So
that
was
May
15th.
It
seems
hard
to
believe
that
that's
been
less
than
a
week
ago
that
116
came
out.
We
don't
have
a
blog
post
covering
it
yet,
but
we
do
have
the
release
notes
on
github,
which
covers
the
numerous
features
and
functionality
that
we
got
it
on
116,
which
was
a
really
excellent
release,
so
I'm
very
excited
with
everything
that
we
put
into
116
and
yeah.
B
Now
that
the
door
is
open
again
into
you
know:
opportunities
for
117,
unlike
most
releases,
almost
everything
we
strove
to
get
into
116
actually
got
in,
and
so
usually
the
next
release
is
like.
Well,
let's
finish
the
stuff.
We
didn't
get
them
and
this
release
probably
finished,
like
almost
everything,
so
that
gives
us
some.
B
You
know
some
more
opportunity
than
usual
to
pick
some
new
directions
which
maybe,
in
some
part,
guided
by
initiatives
that
we
may
talk
about
in
a
subsequent
meeting,
but
I,
don't
think
we're
ready
to
do
it
today,
anyway,
I'm
getting
all
over
the
place,
116
came
out
and
it's
very
excited
in
color
module.
Some
PHP
notices
I
saw
that
some
changes
came
in
at
BW
panda.
Also
I've
been
merging,
which
I
really
appreciate
and
most
importantly,
though,
well,
oh
and
and
there
was
a
fairly
big
problem
in
the
new
filter.
B
You
asked
for
both
rupal
seven
and
triple
eight
and
as
usual,
we
had
to
coordinate
a
matching
release
for
backdrop.
So
one
sixteen
one
came
out
within
the
same
week
as
116
and
had
we
been
in
control
of
the
security
releases
would
probably
wouldn't
have
done
that,
like
we
don't
like
to
make
a
minor
release
and
then
immediately
make
a
security
or
at
least
four
days
later,
that's
not
ideal
for
our
users,
because
it
makes
it
I
feel
driven
to
update
to
the
latest
version.
B
So
yeah
lots
of
things.
We
learn:
Eastern
116,
116,
1
and
115
3
all
within
the
past
week,
so
116
116
is
now
the
next
bug
fix
release.
We
don't
have
any
major,
critical
issues
that
are
in
116
that
I
know
of
to
be
addressed,
because
we
already
fixed
those
small
issues
that
we
found
within
the
first
couple
of
days.
So
116
will
be
the
next
bug
fix
release.
But
we
don't.
B
Of
urgency
to
bring
up,
although
if
you
look
at
the
116
milestone
inside
github,
there
are
now
63
issues
in
there.
That
are
all
what
we'll
call
them
of
priority,
but
they're
usually
thinks
that
have
some
impact
in
some
situations
and
also
have
code
behind
them
already.
So
the
116
list
is
a
great
place
to
be
putting
your
attention
right
now,
if
you're
looking
to
contribute
some
reviews
or
code.
B
You
can
be
a
developer
or
you
can
not
be
a
developer,
but
we
hope
that
by
being
an
advocate,
you
get
increased
visibility
into
the
problem
and
we
add
it
to
these
weekly
agendas
so
that
we
can
talk
about
every
week.
But
you
do
also
have
to
post
an
update
every
week
with
the
status
of
of
that
project.
B
So
the
advocacy
approach
is
still
something
that
we're
doing
and
if
you
have
things
that
you're
interested
in
doing
and
what
17
that
might
not
require
a
whole
team
or
are
something
that
can
be
done
within
a
single
release.
I
highly
encourage
people
to
choose
some
issues
to
start
advocating
for
and
and
be
the
hero.
That
issue
needs.
B
Let's
see
117
yeah,
the
only
thing
that
got
bumped
from
116
is
that
we
wanted
to
deprecated
cash
play
role
and
we
didn't
get
around
to
removing
all
the
instances
of
that
in
116.
So
that's
like
a
small
thing
that
got
bumped
that
could
possibly
be
picked
up,
but
it's
not
really
a
high
impact
thing
so
that.
A
B
B
Not
a
horribly
difficult
thing
to
manage,
but
that's
it
117.
That
I
think
the
only
thing
I'd
to
reiterate
is
that
it's
kind
of
an
open
book
at
this
point
the
release
will
be
September,
15th
2020,
which
is
seems
like
it's
ages
away.
You
know
the
whole
summer,
but
as
always,
I'm
sure
it'll
be
here
before
we
know
it.
B
C
A
B
We
had
a
little
bit
of
a
philosophical
disagreement,
I
think
with
the
d7
Dean
key
maintainer,
and
maybe
that
discouraged
him
from
completing
the
contribu
occasion,
I'm
not
sure
but
related
to
that
I'll
express
my
opinion
and
whether
that's
popular
or
not,
that
multiple
themes,
support
and
backdrop
core
is
an
unusual
thing,
because
there's
no
capacity
to
actually
run
more
than
one
theme
at
a
time.
You
know
there's
only
enable
and
set
default,
but
you
can
have
multiple
themes
enabled
but
having
multiple
themes
enabled
us
absolutely
nothing.
B
A
It's
funny,
though,
that
feature
is
like
in
high
demand
in
the
world,
all
of
a
sudden
as
everybody
wants
dark
modes
on
everything,
but
rather
than
it
being
like
a
per
account
setting
it's
like
a
cookie
where,
like
you
as
a
visitor
logged
out
visitor
to
a
site,
you
can
click
dark,
unlike
anything
like
Twitter
or
whatever,
and
it'll
switch
it.
So
it's
interesting
that
that,
like
feature
is
back,
but
it's
now
implemented
in
a
way
that's
completely
different
than
it
was
when
it
wasn't
for
yeah.
B
Even
then,
though,
it
might
not
necessarily
mean
another
theme,
it
could
mean
you
know
another
stylesheet
within
a
theme
you
know,
and
it
could
be
a
feature
of
a
team,
a
theme
that
has
a
dark
mode.
So
I
don't
think
it
necessarily
means
that
core
needs
to
support
multiple
make
darts
modes
possible.
You
know,
and
this
it
already
has.
B
D
B
There's
the
unfortunately,
a
global,
named
theme
or
theme
key.
It's
funny,
there's
two
of
them
that
if
you
change
that
it
changes
the
theme,
that's
that's
used
on
the
page
and
that
my
proposal
had
been
when
pinky
was
being
ported.
That
pinky
really
should
take
over
the
responsibility
of
having
multiple
themes
enabled
in
the
first
place
and
backdrops
user
interface
should
really
be
focused
on.
What
is
your
front
end
theme
like,
rather
than
this
whole
life,
you
have
forefront
and
themes
enabled
which
one
do
you
want
to
be
the
default
like
it
really
should
be.
B
This
is
my
theme
and
it
disables
the
other
one
and
there's
none
of
those
multiple
themes
enabled
but
they're
not
really
doing
anything
feature
unless
you
have
a
module
like
theme,
key
installed
that
allows
for
switching
between
multiple
themes.
I,
don't
know,
that's
my
perspective
on
things.
I
also
think
that
Landman
themes
should
specify
whether
or
not
they're
admin
or
not,
and
you
shouldn't
allow
anything
to
be
an
admin
theme.
A
Think
I
think
I
wrote
an
issue
a
long
time
ago
about
removing
the
ability
to
have
more
than
one
enabled
theme
like
at
the
very
beginning
of
backdrop.
I'm
like
what
is
this.
Why
is
this
in
here?
We
should
get
it,
but
I'm
not
sure
it's
had
any
serious
attention
since
then.
The
thing
about
disabled
their
admin
themes
being
admin
only
or
needing
to
define
that
their
admin
is
new.
I
hadn't
heard
that
before
but
I
like
it
I
don't
I
want
to
add
a
new
key
for
that.
One.
B
A
B
B
B
D
B
C
It's
one
of
the
things
we've
all
gotten
used
to,
but
now
the
year
you
talk
about
it,
mate
like
like
you,
you
set
a
theme,
that's
looking
for
your
site,
but
you
only
know
it's
that,
because
it's
at
the
top
of
the
list,
that's
otherwise
undifferentiated
that
you
know
that
tops
the
top
spot.
Is
you
know
syntactically
incredibly
important,
yet
not.
B
C
B
C
B
It
would
be
much
more
clear
if
you
were
just
selecting
your
theme.
Site
theme
choose
your
site,
yeah
I
mean
yeah,
it
could
and
all
of
kinds
of
things.
You
could
have
multiple
admin
themes,
but
we
don't
promote
that.
You
know
you
only
get
one
admin
theme:
why
do
you
hit
only
one
when
there's
multiple
front-end
themes
for
some
reason,
I,
don't
know
anyway,
I
really
yeah.
We
can
move
that
functionality
can't
reboot
being
responsible
for
more
than
one
front
empty
I,
think
that
would
be
appropriate.
B
B
But
the
focus
right
now
or
had
been
on
automatic
updates
for
us
for
sites
that
were
not
managed
by
composer
and
it
doesn't
work
with
sites
managed
by
composer,
which
is
the
recommended
way
to
do.
Install
Drupal,
8,
so
I'm,
it's
a
little
bit
of
a
weird
conundrum
that
it
seems
like
the
effort
that
has
gone
forward
so
far,
isn't
necessarily
beneficial
to
Drupal
core
for
a
feature
that
they
would
add
in
the
future.
B
B
That
seems
like
a
little
tricky
bit
of
codes
that
is
now
out
there
and
available
for
us
to
to
modify
into
backdrop
if
we
want.
It
also
has
some
ability
that
I
haven't
figured
out
yet
to
run
update
PHP
and
right
now,
that's
been
one
of
our
sticking
points
for
automatic
updates
that
we
support
manual,
core
updates,
but
automatic
updates
are
difficult
for
us,
because
a
manual
update,
if
there's
an
update,
whp
run,
we
immediately
send
the
user
to
run
update
whp,
and
they
just
have
to
do
that
manually
and
an
automatic
update.
B
B
C
B
For
the
most
part,
I
would
say
no
like
if
you
update
a
module
or
update
cord
well,
first
of
all,
in
order
for
updates
to
be
rollback
complying,
he
talks
to
a
database,
backup,
yeah
and
even
right
now,
with
a
manual
update
that
you've
just
pulled
in
the
code
for
even
if
it's
managed
by
version
control.
You
know
when
you
visit
update
of
PHP.
B
C
So
this
is
one
of
the
things
we
would
inherited.
I
don't
understand,
like
my
understanding
of
like
you
know,
database
stuff
is
that
you
know
20
years
ago.
That
was
not
how
you're
supposed
to
do
it.
They
originally
I
mean
my
oscuro
didn't
have
didn't,
have
transactions
right,
but
it's
had
transactions
for
15
years
now,
all
right,
yeah.
B
Although
updates
the
way
that
they're
run
an
individual
update
can
be
successful
until
the
transaction
with
patients
successful,
but
the
next
request,
because
that
it
batches
them
like
you,
can
have
five
updates,
be
successful
and
the
sixth
one
fail
and
that,
even
if
that
was
contained
within
a
transaction,
you've
still
made
five
previous
transactions
that
were
successful.
That
the
whole
thing
needs
to
be
rolled
back,
probably
well.
C
I
mean
you
got
to
the
answer:
the
answer's,
no,
and,
and
now
we're
like
why
not
okay,
I
like
it
right,
that's
the
whole
point
of
transactions.
Right
is
if
your
while
you're
in
an
unstable
state
you're
inside
a
transaction,
if
it
doesn't
complete
you
roll
back,
there
be
a
new
transaction
to
the
Year.
Last
known,
stable
state,
Oh.
B
B
Yeah
the
focus
on
or
the
focus
very,
the
automatic
updates
module
has
been
trying
to
ensure
that
things
don't
go
wrong
before
they
do
and
then
I
mean
it's
sort
of
still
the
same.
You
know,
like
you,
know,
cross
your
fingers
and
hope
that
this
works
with
the
idea
that
sites
are
more
secure
or
more
likely
to
be
stable,
with
automatic
updates
that
have
risk
versus
sites
that
don't
have
automatic
updates
that
are
permanently
fraught
vulnerable
to
exploitation.
B
B
A
B
We
didn't
prepare
for
this,
and
so
there's
nothing.
We
can
do
other
than
to
tell
everybody
to
update
and
trust
them,
but
it
leaves
a
bad
taste
in
people's
mouths.
I
think
when
you
know
every
Drupal
site
you've
ever
built
got
hacked.
You
know
you
can.
Even
though
it's
your
fault,
maybe
it's
the
developer,
you
didn't
maintain
it.
You
know
like
it's
still.
B
B
B
We
had
someone
that
was
very
interested
in
doing
something
that
had
restoration
capabilities
quite
a
while
ago,
but
he
was
looking
at
doing
that
for
it
like
arbitrary,
can
up
to
any
CMS
with
rollback
capabilities
across
the
board,
because
the
rollback
functionality
was
so
complicated
by
itself
that
he
was
like
this
should
be
its
own
project
and
be
able
to
update
anything.
And,
of
course,
then
that
got
went
down
its
own
little
rabbit
hole.
D
B
B
Maybe
it's
my
belief
that,
in
order
for
automatic
updates
to
be
effective,
it
needs
to
be
they're
out
of
the
box
turned
on
by
the
fault,
and
it
needs
to
not
require
any
additional
setup
as
to
just
be
there,
because
if
it
requires
any
additional
setup
like
if
you've
got
back
trump
installed
and
automatic
updates
aren't
turned
on
as
part
of
that
I
think
a
new
user
would
say.
Oh
my
sites
running
and
not
follow
any
of
these
subsequent
sub
sub
sequential
steps.
B
B
You
know
we
built
up
the
background
fetch
and
background
cron
functionality
saying
and
we
increased
the
frequency
in
which
end
of
page
cron
is
run
to
make
it
so
things
like
scheduler
would
run
that,
although
it's
still
recommended
to
use
cron
dot
PHP,
to
run
it
more
frequently
and
on
a
dedicated
task
for
a
small
sites
like
setting
up
cron
is
like
not
a
required
thing
that
they
do
and
I
think
that
that
kind
of
mentality
is,
is
what
needs
to
be
preserved
for
automatic
updates
as
well.
That
needs
to
be
out
of
the
box.
A
Yeah
I
really
like
this
idea
to
back
up
the
migrate
is
currently
our
number
one
can
trim
on
shell,
so
I
think
it's
also
an
indicator
of
like
our
audience
are
the
kinds
of
people
that
are
gonna
want
to
use
a
tool
like
backup
and
migrate,
whereas
Drupal
audience
might
have
a
tool
like
Pantheon
or
a
Kuei
that
provides
that
service
for
them.
But
there
is
a
lot
of
funny
stuff
going
on
and
backup
and
migrate.
That
I
think
we
wouldn't
want
in
core
like
there's
a
whole
bunch
of
integration
with
like
Note
squirrel.
A
A
Don't
know
what
that
would
look
like
with
automatic
updates,
I
think
I
think
it
would
make
sense
to
be
like
make
a
backup
before
you
make
an
update,
but
if
this
site
it
does
get
broken
during
update,
you're,
not
gonna
have
the
interface
from
back
up
with
migrate
to
restore
either
right.
So
it's
like
if
it's
a
little
broken
you're
fine.
If
it's
totally
a
host,
you
are
totally
hosed
yeah.
C
A
Well,
we
already
have
some
scripts
that
ship
with
backdrops
that
do
things
like
reset
passwords
and
stuff
I.
Think
if
we
had
a
standard
location
of
like
there's
back
of
a
migrate,
the
backups
look
here.
The
name
is
formatted.
In
this
way
we
could
provide
script
that
would
be
like
restore
from
latest
backup.
Yes,
no
I
think
it's
a
yes
and
it
can
import
a
database,
but
that
might
not
be
enough.
I
mean
I,
don't
know
we're
in
the
process
it's
getting
garbled,
but
it
could
be
like
importing.