►
From YouTube: Backdrop Weekly Oct 8th, 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
All
right
we're
on
air.
It
is
october
8th.
This
is
our
weekly
development
meeting
and
this
week,
instead
of
going
through
our
normal
set
of
bug,
fix
issues,
we're
very
excited
to
work
on
potential
issues
for
backdrop
118.
and
before
we
get
to
that.
Let's
go
through
everyone
in
the
meeting
and
have
you
all
introduce
yourselves
greg?
Would
you
like
to
go
first.
B
Yep
hi
I'm
greg
I'm
joining
from
grace,
usually
in
australia,
though
interested
in
anything
related
to
backdrop
and
try
to
help.
However,
I
can
excited
about
this
meeting.
Tim
wanna
go
next.
C
Hi,
I'm
tim
st
paul
tim
coming
to
you
from
deerwood
minnesota,
possibly
one
of
the
last
decent
days
I
can
come
to
outside.
I
had
to
put
on
both
my
backdrop
and
my
bad
camp
sweatshirts
for
to
stay
warm
today.
E
Hi,
I'm
jason
from
las
vegas
man,
I'm
a
back-end
developer
and
I'm
here
to
see
what's
going
on
figure
out,
what's
going
on
with
life
joseph.
F
G
I'm
nate
lampton
from
oakland,
california,
and
I'm
a
court
committer
and
yeah.
I'm
excited
to
chat
about
our
possibilities
today,
jen
back
to
you.
A
I'm
jen
lampton
also
calling
from
oakland
california,
and
I
am
very
excited
about
the
future,
in
particular
what
issues
to
work
on
for
118..
We
did
also
just
admit
justin.
I
don't
know
if
you'd
like
to
introduce
yourself
but
we're
at
the
end
of
our
introduction
period,
so
welcome.
A
Thanks
for
joining
great
this
week,
we
have
a
ton
of
new
contributed
modules
that
appeared
in
the
contrib
group.
So
a
lot
of
our
current
maintainers
have
been
really
busy
and
we
have
a
couple
of
new
people
who
are
contributing
new
module
ports
to
backdrop,
in
particular,
bug
folder,
who
recently
got
their
contrib
application
approved,
has
been
doing
a
lot
of
work
so
special
thanks
to
them
the
modules
we
have
this
week
that
are
new,
oh
geez,
okay,
nate's,
adding
who
did
each
of
them.
Okay,
we've
got
a
whole
bunch
of
them.
A
Uber,
cart,
mini
cart.
Block
is
something
that
larry
imported,
so
thank
you.
Larry
views
be
grid,
herb
dual
ported,
so
thank
you.
Herb
em
image.
Maximum
crap
is
bw
panda,
so
thank
you.
Amanda
spam
sand
me
or
me,
aliases
no
to
clone
tab
and
rules
once
per
day
we're
all
by
bug.
Folder.
Oh
wait
and
comment
hide
subject.
So
thank
you.
Bug,
folder
and
then
term
body
class
was
by
olaf
and
it
looks
like
civi's.
Serum
kron
was
also
from
laryn,
so
a
lot
of
our
usual
suspects,
plus
a
ton
from
bug
folders.
A
So
thank
you.
Everybody
for
being
super
active
part
of
the
reason
that
list
is
so
long
is
because
we
did
not
have
a
meeting
last
week,
so
we
skipped
a
handful,
but
there
were
so
many
in
the
last
two
weeks
we
had
to
talk
about
all
of
them
just
very
exciting.
A
Also
in
the
past
few
weeks,
bw
panda
has
been
doing
a
ton
of
work
on
backdrop,
cms.org,
I
think
in
the
last
meeting
I
said
thank
you
to
peter
for
working
on
the
forum.
Was
it
the
forum
site
was
the
api
site.
It
was
the
api
site
because
he's
been
working
on
the
form
api
page
there
this
week
he's
been
working
on
backdrop.
Cms.Org
he's
already
made
a
massive
improvement
to
our
showcase
site,
which
was
looking
a
little
bit
funny,
depending
on
the
size
of
screenshots
that
people
were
posting.
A
A
Oh,
that
was
me.
Oh
I
don't
know
he.
He
improved
that
too.
So
yeah,
there
are
a
couple
of
different
changes
to
the
modules
page.
One
of
them
was
just
an
aesthetic
change
that
I
made
after
greg,
and
I
watched
the
classic
press
demo.
We
saw
how
pretty
their
little
module
boxes
looked,
and
I
was
like
oh,
we
could
do
that
on
our
site,
so
I
fixed
the
module
boxes
and
by
switching
that
from
using
fields
in
the
view
to
using
a
view
mode.
It
made
it
much
easier
to
make
other
changes
like.
A
I
think,
we've
been
doing
something
weird
with
fields
and
the
search
thing
where
we
were
doing
a
combined
field,
filter
or
something
like
that,
and
that
was
causing
issues
with
search
results.
I
don't
remember
why
we
decided
to
do
that
in
the
first
place,
so
video
panda
fixed
it
by
switching
it
back
to
using
a
search
index
and
now
all
the
search
results
are
coming
out
in
the
right
order.
Yay
teamwork.
A
So
I'm
really
glad
to
see
those.
I
don't
remember
what
the
problem
was
with
search
in
the
first
place.
We
searched
the
ishiku
and
couldn't
find
it
should
that
come
up
again.
We
will
address
it
in
the
future
when
that
problem
comes
up
again.
So
anyway,
I
think
it's
better
than
it
was
before
so
yeah
fantastic
work
on
all
that
stuff.
A
A
Not
the
let's
and
script
certificates
are
old
certificates
that
we're
replacing
just
a
little
worried,
but
because
we're
using
the
new
certificates,
we
didn't
have
to
worry
about
it.
So
that
was
great
and
then
nate
says.
Are
there
any
other
updates
from
justin
on
server
stuff
that
we
should
know
about.
H
I
don't
have
anything
else.
I
was
thinking
I'd
just
make,
maybe
six
months
worth
of
tickets
for
monthly
updates
like
one
per
month
and
then
just
knock
those
out.
So
I
don't.
Maybe
we
should
do
it
every
month,
I've
been
doing
it
every
quarter,
trying
to
remind
myself.
A
H
Do
we
are,
we
gonna
need
anything
for
the
cv
crm
so.
A
We,
the
current
plan-
and
I'm
not
sure
how
near
far
this
is,
is
that
jack's
company
has
a
bunch
of
experience
working
with
civvy
crm
and
we
did
an
initial
consult
on
how
we
could
use
civi
for
backdrop,
and
they
recommended
that
we
install
civvi
on
our
current
site
so
that
we
could
leverage
our
current
user
table
as
a
starting
point
for
all
of
our
consumers
or
whatever's
the
c
in
crm
for
us,
and
so
that
way
it
would
make
it
a
better
starting
point
rather
than
starting
with
a
brand
new
empty
site.
A
But
it
I
don't
know
how
much
work
is
involved
in
bolting
a
new
database
onto
an
existing
website
like
that,
especially
with
civi.
I
know
there's
like
some
install
scripts
that
do
a
bunch
of
like
copying
and
synchronizing
and
stuff,
but
the
plan
was
to
do
that
on
a
local
site.
Get
it
ready.
Do
it
on
a
beta
site,
run
a
test
and
then
do
it
again
on
the
production
site.
A
And
so
hopefully,
all
that
would
be
needed
is
a
new
database
and
then
running
whatever
scripts
are
required
in
order
to
get
that
done,
and
they
were
going
to
work
on
the
scripts
in
the
development
environment
and
test
them,
etc,
so
that
it
would
be
fairly
straightforward
to
deploy.
But
we
haven't
made
very
much
progress
on
that
and
because
I'm
not
involved
in
everything,
you
know
the
technical
sides
of
everything.
A
I
asked
him
to
take
a
look
at
what
that
would
be,
because
I
know
he's
really
interested
in
working
on
the
crm
angle
of
things,
and
maybe
it's
not
as
scary
as
it
sounds
to
me.
A
So
tim's
going
to
do
a
little
r
d
on
that
and
figure
out
what's
necessary
and
we
will
know
more
when
he
learns
more
as
to
whether
that
plan
is
still
going
to
be
our
best
course
of
action.
But
that's
where
we
are
currently.
H
C
I
If?
Because,
if
that
was
a
blocker,
we
could
you
know,
do
something
like
that.
Having
that
as
an
option,
I
think
knowing.
C
A
Okay,
let's
move
on
to
backdrop
cms
core
stuff.
It
says
here
nate's
in
charge
of
that,
but
this
is
my
list,
so
I.
G
Don't
know
yeah
I'll
I'll
run
through
the
things
that
we
know
for
sure
that
we're
doing
and
that's
actually
not
at
the
bottom
of
the
agenda
that
items
that
we
have
slated
for
118
include
my
sequel,
8
support.
That's
issue
4238
still
investigating.
If
that's
something
we
can
actually
get
in
earlier.
G
It's
currently
marked
works
for
me,
and
more
testing
would
be
appreciated
on
that,
but
so
far
we
have
all
the
test
passing,
it
seems
to
be
seems
to
be
working
really
pretty
well.
We
also
could
merge
it
into
118
like
right
now
and
then
just
have
it
in
core
for
the
next
couple
of
months
or
something
like
that
and
then,
if
it
turns
out
that
we
have
encountered
no
problems
with
it
over
that
time
span,
then
we
could
possibly
backport
it
into
117
a
little
sooner
than
the
next
release.
B
I'm
I'm
in
favor
of
that
like
getting
it
sooner
so
that
we
can
get
more
eyes,
and
this
is
going
to
be
a
bunch
of
us
that
are
getting
the
most
recent
code
base
on
their
local
to
just
test
things.
B
So
we're
gonna
have
the
opportunity
for
to
test
this
thing
and
see
if
it
breaks
things
with
the
current
database
and
then
there
were
at
least
a
bunch
of
people
that
are
have
been
sort
of
like
actively
complaining
about
the
lack
of
support,
so
we'll
leave
that
testing
for
the
actual
my
simple
age
to
them.
B
G
Interesting,
this
person
tested
it
early
bird
which
who
I
love
their
handle
and
they
tested
the
site
on
my
sequel,
eight
and.
G
5.7
yeah
and
they
got
a
regression
in
my
sequel,
eight,
which
is
interesting
because
it
doesn't
really
matter
if
they're
running
the
patched
version
on
both
of
them.
The
code
is
is
the
same
for
both
of
them,
so
I
don't
think
that
it's
caused
by
core
code
but
interesting,
it
might
just
be
configuration
differences,
because
my
sql
configuration
can
really
drastically
affect
your
performance.
G
G
Okay,
continuing
on
webp
support
is
a
new
image.
Format
to
replace
jpegs
lauren
is
advocating
for
this
issue
in
4509
and
status,
says
it's
that
it
currently
needs
review.
G
There
is
also
a
small
issue
to
add
a
new
token
for
user
accounts.
That
user
accounts
want
to
be
able
to
have
a
link
token
that
turns
a
link
or
returns
a
usernames.
You
the
username
token
into
a
link
to
their
profile
page,
so
that's
issue
4584
and
that
one
is
already
marked
rtbc.
So
those
are
the
items
that
we
have
slated
for
118
right
now
and
the
rest
of
the
time.
G
Today,
we're
going
to
be
talking
about
other
things
that
we
could
potentially
pursue
in
118,
and
it's
kind
of
going
to
be
just
an
open,
informal,
like
brainstorming
session
for
issues
that
people
are
interested
in
and
jen
is
the
one
that
seems
to
be
most
excited
about
new
features.
So
when,
as
put
a
nice
list
here
in
the
agenda,
if
anyone
else
has
things
putting
them
in
the
agenda
would
be
great,
but
should
we
give
other
people
an
opportunity
first
gen,
or
do
you
want
to
just
go
right
into
your
list?.
A
Yeah
so
this
list,
I
just
I
think
I
went
through
the
milestone
candidate
tag
and
I
might
have
added
a
lot
of
milestone
candidates
to
issues
like
maybe
more
than
everyone
else.
But
that's
because
I
see
something
and
I'm
like.
Oh,
I
really
like
this,
but
then
when
it
comes
time
for
me
to
actually
choose
which
one
to
work
on
for
a
next
milestone,
there's
so
many
things.
A
A
That's
required
in
order
to
make
those
user
experience
changes,
and
so
those
issues
kind
of
all
go
together
and
then
there's
some
that
are
big
features
that
I
think
would
be
really
killer
for
backdrop
to
have
as
like
a
competitor
to
drupal
8
and
that's
something
big
like
adding
hashtags,
which
we
know
can
be
done
on
drupal
7,
because
there's
a
contributing
module
for
it,
and
so
in
theory,
it
could
be
down
on
backdrop
too,
and
that
could
be
something
that
I
think
people
come
and
say:
oh
backdrops,
like
drupal
7,
but
what
about
hashtags
and
it
would
be
really
cool
if
we
could
say.
A
Oh,
we
have
that
because
it's
one
of
the
things
that
I
think
sets
drupal
8
apart.
It
also
lines
up
our
philosophy
in
that
making
things
faster
is
good
for
us,
so
yeah,
there's
just
stuff
like
that.
A
Then
there's
a
bunch
of
other
things
here
like
that
were
determined
by
usage.
So
things
like
right
now,
our
number
one
contrib
module
is
backup
and
migrate.
B
Sorry
with
regards
to
backup
and
migrate,
it's
not
only
the
usage
of
it.
There's
places
that
we
urge
people
to
just
take
a
backup
like
during
the
module
update
process,
which,
instead
of
pointing
them
to
documentation,
we
could
just
have
a
checkbox.
That
says.
Yep
also
take
a
backup
for
me,
and
I
think
we
have
an
issue
for
that
as
well.
So
that
would
help.
A
B
A
And
I
think
in
particular,
cleaning
up
the
update
process
is
also
going
to
be
beneficial
for
people
coming
from
triple
seven,
because
we
now
have
this
ability
to
manually,
update
and
maybe
someday
automatically
update,
and
I'm
hoping
that
more
people
are
going
to
be
using
that
in
backdrop,
so
spending
some
time
to
rethink
how
we
handle
reporting
and
the
action
of
doing
those
things
could
be
good
too.
I
Because
do
you
have
the
add
the
image
library
to
immense
fields
as
well.
D
I
I'm
excited
about
adding
backup
and
migrate
into
core
because
because
that
that
at
least
approximates
to
some
extent,
wordpress's
export
and
import
site
functionality,
at
least
yeah.
C
Some
of
it
I'm
also
interested
in
in
that
feature-
I
you
know,
I'm
very
interested
in
forward
facing
features
that,
like
a
site
builder,
would
would
recognize
and
use
and
I'm
weak
in
like
understanding
what
are
the
big
behind-the-scenes
features
that
we
really
need
to
fix
and
things
so
but
anyways
so
the
backup
and
migrate.
C
Yeah
field
group
functionality
also
seems
like
that
would
be
a
powerful
feature.
H
G
That
they're
generally
better
for
our
project
have
these
kinds
of
things
that
are
end-user
accessible
and
something
like
advanced
hashtags.
I
get
that
that's
like
a
developer
concern,
but
it's
really
not
something
that
would
be
a
real
seller
for
end
users.
I
don't
think,
but
I
don't
know,
I'm
not
saying
that
we
shouldn't
put
in
cash
tax
because
I
think
they're
awesome
but
yeah.
I
agree
with
your
sentiment
of
end
user
facing
stuff.
Just
could
be
preferable.
C
Well,
my
point
is
that's
the
stuff
easiest
for
me
to
comment
on,
but
sometimes
I
worry
that
I'm
neglecting
because
we
do
have
to
pay
attention
to
those
other
back-end
things
and
there's
a
certain.
You
know
a
certain
group
of
decision
makers
that
that
might
you
know,
be
really
influenced
by
things
like
hashtags,
and
so
I
you
know,
I'm
glad
that
we
do
have
people
in
our
community
paying
attention
to
those
as
well.
C
Sorry
thing
you
got
muted
and
I
muted
myself
I'll
just
list
a
couple
of
other
things
that
are
forward-facing
things
that
I
know
I've
wished
for
dismissible
blocks
or
accordion
blocks.
C
Config
recipe:
this
is
something
I
started
to
work
on.
At
one
point,
I
have
sort
of
a
contrib
module
for,
but
the
idea
to
sort
of
have
features
like
functionality
using
config,
I
think,
would
be
helpful.
We
need
to
figure
out
what
we
need
in
core
to
make
that
more
possible
changing
the
full
html
to
raw
html
is
something
we've
been
talking
about
for
a
while.
I
think
we're
close
on
at
least
a
consensus
on
what
to
do
just
need
to
make
it
happen.
C
Yeah,
well,
a
starter
kitten
basis.
Is
I
don't
know
if
we,
I
don't
think
we
have
consensus
on
that,
but
it's
it's
an
idea
that
it's
interested
being
basically
something
to
make
something
easier
and
there
might
be
a
different
solution,
but
anyways
that
those
are
my
some
of
the
things
that
I
had
to
kind
of
skim
through
the
future
list
to
see
some
of
the
things
that
in
the
past,
who
got
me
excited
because
I'd
forgotten
some
of
these
anybody
else.
G
Related
to
your
recipes,
config
recipes.
G
We
have
an
issue
for
making
it
simple
to
export
an
entire
content
type
with
all
of
its
peripheral
stuff
in
practice
and
in
development.
I've
not
actually
found
that
to
be
something
I
run
into
frequently,
but
because
for
me
I
just
export
the
whole
site
and
then
honestly,
that
seems
to
be
what
I
want
almost
all
of
the
time,
so
that
turned
out
to
not
be
as
important
as
I
had
once
thought,
but
config
recipes
could
be
a
better
alternative
to
that.
Honestly.
C
Sure
another
related
to
backup
and
migrate
and
config
is
that
I
keep
finding
it
out
that
there
isn't
like
when
I'm
backing
up
by
backup
and
migrate.
It
has
database
files
and
code,
but
well
there
is
a
there's,
a
separate
config
export
feature,
but
I've
been
trying
to
figure
out
like
if
I'm
backing
up
my
site.
D
D
B
Yeah
there's
an
old
issue
about
it.
I'll
share
the
thing
I'll
find
it
and
share
it
with
you.
We
called
it.
We
called
it.
We
called
it
recipes
and
lack
of
any
better
well.
A
A
A
If
you
install
a
site
with
nothing
on
it,
people
think
your
site
does
nothing
so
sort
of
is
the
wrong
first
impression,
whereas
if
you
give
them
something,
that's
a
functional
website,
then
it's
an
easier
place
for
people
to
start,
but
for
for
more
advanced
users,
everybody,
not
everybody,
but
a
lot
of
people
in
the
drupal
community,
like
specifically
choose
to
start
with
minimal.
It's
called
minimal
yeah.
It
doesn't
have
anything.
E
E
D
That's
not
I
I
mean
I
mean
if,
if
I
inherit
a
site,
basically
you
know
if
someone
says
hey,
you
know
I've.
I've
got
this
thing
called
drupal.
I
I
don't
know
what
it
is.
What's
going
on
like
like
I
go
in
and
there's
a
certain
thing.
I
go
to
the
the
content
types
and
look
and
see
what
content
types
are
there.
Then
I
go
with
you
know,
poke
around
the
fields
and
see
what
fields
are
in
there.
I
look
at
the
taxonomies.
A
This
is
really.
This
is
interesting
because
I've
been
working
on
doing
like
estimates
in
drupal
7
sites
and
what
I
really
want
is
this
report
right,
because
it
gives
me
a
list
of
all
the
stuff
that
I
have
to
move
from
triple
seven
to
backdrop.
So
it's
interesting
like
the
concept
of
making.
That
report
sounds
super
appealing
to
me
because
then,
if
I
had
to
like
do
an
upgrade
from,
I
don't
know
a
backdrop
to
something
else.
Getting
that
report
out.
A
It's
a
lot
of
value
and
we
haven't
the
ability
in
backdrop
to
determine
whether
the
configurations
for
any
of
these
things
are
in
their
default
state
or
overwritten.
So
we
could
even
tell
like
if
the
basic
page
content
type
has
never
had
anything
changed.
We
could
put
that
on
the
report
at
the
bottom
being
like
this
was
default,
never
changed,
but
if
somebody
had
like
added
a
field
to
it,
we
could
add
that
too
so
yeah
interesting.
I
like
that.
I
like
the
idea
of
a
report.
D
Yeah,
I
I
mean
it,
it's
not
necessarily
purple,
but
just
just
sort
of
sort
of
that
they
have
kind
of
packaging
away.
The
the
the
best
example
I
can
think
of
is
is
like
if
you,
if
you
buy
a
car
right
like
like
there's
things
you
have
to
know
to
run
the
car,
you
know
where
the
you
know
how
to
turn
it
on
and
how
to
turn
on
the
radio
and
stuff
like
that.
D
But,
like
there's
also
like
a
service
manual
that
you,
you
know,
you
open
up
the
hood
and
you
can
change
the
oil
and
change
the
spark
plugs
and
do
all
sorts
of
stuff.
You
know
change
the
brake
pads
and
all
those
things
are
doable
things,
but
I
feel
like
like
we
have
all
that,
like
change
the
oil
level
things
on
the
inside
of
the
car
in
the
passenger
compartment,
where,
like
people
that
don't
know
how
to
change
the
oil
are
nevertheless
faced
with
that
menu
item.
B
Are
you
talking
about
a
simplified
administrative
ui
where
only
the
basic
things
are
shown
like
a
an
advanced
advanced
section,
so.
D
Yeah
but-
but
I
mean
I
mean
part
of
it-
is
not
not
to
strip
it
away
now,
because
a
problem
with
like
beginners,
you
know
like
putting
things
into
like
beginner
and
expert
stuff,
is
the
beginner
stuff
ends
up
being
useless.
You
end
up
not
being
able
to
actually
do
anything
with
it
and
you
don't
you
don't
really
get
to
get
anything
done
until
you
turn
that
off
and
wade
through
the
stuff.
D
B
C
Okay,
the
second
thing
you
were
talking
about
it
sounded
like
we
added
the
editor
role,
but
I
think
what
you
would
probably
respond
to,
that
is
the
ability
to
switch
between
them
so,
like
maybe
the
ability
to
to
be
an
editor,
but
just
to
to
like
by
choice,
not
because
you've
been
given
that
role
right
to
say,
put
me
in
editor
mode.
C
D
Yeah
yeah,
that's
good,
I
mean
roles
lock
you
out
of
stuff
right
rules
would
be
like
you
have
the
car
and
you
need
a
key
to
get
into
the
into
the
engine
compartment.
You
can
get
the
anti-apartment
just
by
popping
it,
but
most
people
choose
that.
I
don't
want
to
do
that
right
now
and
and
and
the
thing
is
the
reason
why
I
think
it
matters
is
that
there
are
stuff
that
people
do
have
to
do
and
they're
hard
to
find
because
they're
they're
lost
in
these
mountains
of
things
that
they
don't.
F
D
To
do
so
so
it
makes
the
findability
of
the
stuff.
That's
actually
relevant
difficult,
because
because
you
have
to
wonder
these
things,
you
don't
know
what
they
are
right
and
they're
dangerous.
You
can
totally
up
your
site
if
you
hit
the
wrong
thing
right,
so
so
you
you
want
to
be
able
to
have
like
a
safe
place
to
go
where
you
know
what's
going
on
and
where
you
can
look
at
all
the
things
and
make
changes.
I
don't
know
so
yeah,
but
I
I
haven't
gotten
into
that,
because
it
can
involve
fairly.
D
It
involves
us
diverging
substantially
from
drupal
and
and
we've
been,
you
know,
largely
built
on
being
backwards
to
power
to
people.
So
so
these
are
definitely
kind
of
forward
looking
things
for
because
because
once
once
you
once
you
go
down
that
road,
there's
no
going
back,
so
I
you
know
yeah
yeah,.
B
It
sounds
it
sounds
like
what
team,
but
it
sounds
like
what
tim
said
like
a
role
switcher
something
for
users,
so
that
they
can
disable
permissions
that
have
been
granted
to
them
temporarily,
but
they
could
switch
them
back
on
like
I
know
that
I've
been
grounded,
editor
and
administrator
role,
but
right
now
I
just
need
every
permission
that
the
editor
role
gives
me
not
the
administrator,
and
I
just
need
a
checkbox
to
enable
that
give
me
all
the
admin
stuff
thingy
thing.
B
Yeah
yeah!
That's
interesting!
I
wonder
if
we
can
do
something
in
country,
but
then,
if
it
works,
then
bring
it
in
core.
I
would
like
to
point
out
like
in
general,
I
would
like
us
to
focus
on
what
zen
said.
Some
killer
features
that
will
would
sort
of
like
either
bring
us
in
parity
with
major
features
that
v8
hasn't
we
lack,
or
that
would
be
it
would
make
an
impact
for
the
announcement
of
118,
and
I
think
that
we
have
been
doing
a
really
great
job
at
that.
B
So
we
usually
pick
quite
a
few
of
them.
Not
all
of
them
may
make
it
and
then,
at
the
end,
maybe
the
last
month
we
work
on
some.
You
know
low
hanging
fruits
so
that
the
the
release
doesn't
seem.
You
know
poor,
I
would
say
so
we
should
we
should.
I
think
that
we
should
stick
to
that
like
find.
Some
killer
features
try
to
work
on
them.
C
D
F
I
think
we
might,
I
like
that
idea,
but
I
think
we
might
run
into
some
of
the
same
issues.
Features
did
such
as
like
the
in
a
it
has
a
hard
time
when
dealing
with
fields
or
on
turning
off
features
that
it
the
stuff
that
the
feature
provided
doesn't
actually
go
away,
because
it's
in
the
database
well.
D
Features
is
really
brittle.
I
I
mean
I
I
mean
there
are
other
problems
with
it,
but
the
thing
I
always
found
is
that
is
it
you?
You
would
run
into
endless
situations
where
you
couldn't
enable
it,
and
and
and
since
you're,
relying
on
being
able
to
add
these
things
and-
and
you
had
to
get
to
like
a
really
deep
technical
level
to
get
past
that,
like
it,
made
it
hard
to
recommend
as
being
like
a
drop-in
thing
like,
like
features,
ended
up
being
just
a
way
to
to
to
do.
F
D
It
was
code
right
so
so
like
if
it
didn't
work
100,
you
couldn't
use
it
all
like
you
need.
You
need
some
failable
features.
You
need
something
where
you
know
you.
It
can
work
partially
and
you
can
be
like.
Is
that
good
enough?
Do
you
wanna
just
stick
with
what
you
got?
Is
that,
and
you
know,
give
the
user
an
option
to
accept
that.
F
F
If
you
wanted
to
rename
something
or
remove
something
and
those
we
always
had
to
write
manual,
update
hooks
for
and
the,
I
think
the
reason
for
that
is
just
because,
when
you
rename
something
it
was
going
to
rename
a
database
table
and
features
just
absolutely
refused
to
do
anything
if
it
was
going
to
touch
your
schema.
F
And
I
think
we
might
run
into
the
same
problems
where
we're
either
going
to
be
like
it's
fine
to
change
your
schema
or
it's,
and
then
we
put
up
with
the
chance
that
we
might
mess
up
your
code,
because
your
database
tables
or
fields
suddenly
have
different
names
or
we
say
like
we
will
absolutely
not
import
a
config
file
that
will
change
your
schema.
B
Yeah,
so
the
the
I
think
that
the
major
difference
between
the
way
features
worked
and
what
we
envisioned
for
recipes
is
that
pictures
had
versions
right.
You
needed
to
upgrade
the
feature
that
you
had,
whereas
recipes
started
more.
I
haven't
looked
at
the
issue
for
quite
a
while,
but
it
started
as
automating
tasks
right,
so
it.
A
B
Yeah,
so
it
was
like
in
order
to
get
a
blog.
I
need
to
install
these
modules
and
get
these
things
done
so,
instead
of
manually
wasting
time
doing
that,
which
is
pretty
much
just
following
documentation
right,
something
like
that
I'll
have
a
script
or
a
series
or
a
thingy
whatever
we
call
it
that
helps
me
do
all
that,
but
once
I
do
it,
this
doesn't
have
to
be
installed.
This
doesn't
have
to
be
part
of
the
site
anymore,
like
it
automates
the
tasks
that
I
routinely
do
and
I
waste
time
doing
it.
G
I
wonder
I
wonder
gregory
you're
saying
that
makes
me
think
that
this
would
be
really
excellent
for
demonstrating
themes.
You
know,
but
there's
a
lot
of
sites
that
are
like.
I,
I
want
my
site
to
look
like
this
and
in
wordpress
lane
the
theme
also
includes
a
lot
of
functionality
and
if
you
were
like,
I
want
to
see
everything
that
this
thing
can
do.
G
The
theme
could
start
becoming
highly
opinionated
like
this
is
a
theme
for
a
very
particular
purpose,
and
it
also
comes
with
this
configuration,
but
rather
than
having
themes
come
with
configuration,
there's
a
recipe
that
happens
to
include
the
theme,
so
we
can
flip
it
around.
I
know,
there's
been
some
requests
of
having
themes,
have
configuration
and
I'd
be
way
more
comfortable
with
this
inverted
approach.
Where
there's
a
recipe
that
includes
the
theme
and
also
includes
the
content.
Types
seems
like.
F
G
F
G
F
I
think
I
was
actually
one
of
the
people,
or
I
think
I
created
that
issue
to
let
themes
have
config
and
the
big
thing
there
was
moving
color
module
settings
into
config
because
right
now
it's
its
own
custom
thing.
That
is
not
the.
D
A
F
G
Always
be
progress
honestly,
getting
excited
again
speaking
of
things
that
getting
excited
again,
I'm
just
gonna
put
it
out
there.
G
The
automatic
updates,
I
still
think,
is
the
thing
that
it's
been
mostly
pending
on
review
from
my
side
and
I'm
going
through
the
issues
that
we
have
on
automatic
updates
and
it's
so
crazy
that
all
of
them
have
been
started
and
have
a
substantial
amount
of
work
on
them
and
that's
just
like,
and
now
it's
like
the
final
little
hard
part,
and
so
so
I'm
gonna
put
it
out
there
that
I'll
I'll
try
to
bring
that
up
again.
G
It's
like
let's
move
forward,
at
least
on
some
of
these
things,
and
I
I'm
not
sure
I'm
gonna
commit
to
like
automatic
updates
will
be
in
118,
but
maybe
some
progress
on
it.
G
Well,
the
meta
issue
is
2018.
and
we've
got
a
number
of
things:
digital
signatures
making
it
so
that,
first
of
all,
we
have
to
sign
packages
and
then
we
have
to
check
the
signatures.
So
it's
kind
of
a
two-part
thing.
G
I've
got
an
issue
for
deprecating
or
removing
authorized.php,
which
isn't
really
a
blocker,
but
it's
like
a
cleanup
task
that
automatic
updates
and
authorize.php
are
in
conflict
with
each
other.
Conceptually.
That
authorize.php
is
like.
When
you
update
a
module,
you
would,
in
theory,
be
able
to
enter
your
ftp
credentials
to
install
the
module
as
that
user
instead,
but
if
it's
automatic,
then
the
web
server
can't
ask
for
ftp
credentials
during
an
automatic
update,
unless
you
did
something
crazy.
Where,
like
the
web
server
sent
you
an
email
says
hey,
I
need
you
to.
G
I
need
you
to
give
me
some
credentials
so
that
I
can
update
myself,
but
then
it's
not
really
automatic
anymore,
let's
see
and
then
the
automatic
part.
We
have
a
big
problem
that
it's
not
clear,
how
to
run
update.php
in
an
automated
fashion
like
right
now.
That
is
something
it
has
to
be
run
through
manually,
and
we
need
to
figure
out
a
way
to
make
it
so
that
did
its
thing
automatically.
A
I'm
also
not
hearing,
like,
I
think
backdrop
should
prioritize
new
features
over
user
experience,
improvements,
or
vice
versa,
which
is
kind
of
what
I
was
thinking.
People
were
going
to
be
like
leaning
towards
it
sounds
like
everybody
still
is:
okay
with
all
the
things
which
is
the
problem
that
I
was
in
when
we
started
what
was
the
answer
you're
hoping
to
get?
A
What
was
what
was
the
answer
you
were
hoping
to
get?
I
was
just
hoping
to
get
any
answer
like
new
features
are
more
important
than
usability
improvements,
or
this
kind
of
feature
is
more
important
than
that
kind
of
feature
like
maybe
performance
is
more
important
than
security
or
like
why?
Why
do
sorry?
What
why
do
these
have
to
be
explicit
like
well,
just
because
I
have
a
hundred
things
I
want
to
work
on,
it
doesn't
have
to
be
forever.
It
just
happens
to
be
like
john.
You
should
work
on
x,
gregory.
A
B
C
C
So
you
know
a
part
of
advocating
for
for
an
issue
too,
for
me
is
figuring
out
one
that
I
can
get
excited
about,
but
also
one
that
I
understand,
and
I
have
some
like.
I
want
something
that
I
can
help,
even
if
I
can't
solve
it,
I
can
help
get
it
to
the
finish
line
in
two
or
three
months.
Backup
and
my
grade
is
one
of
those
that,
like
I'm,
not
sure,
I
don't
know
how.
I
have
no
idea
how
big
of
a
project
that
would
be
so.
B
So
with
regards
to-
and
this
is
because
I
remember
that
you
were
excited
about
telemetry
and
you
were
involved
as
an
advocate
there-
then
the
the
initiatives
separate
to
what
we're
doing
now
or
yes
yeah.
So
so
a
person
can
be
an
advocate
in
one
of
these
issues
and
still
be
an
advocate
for
the
initiative
right
sure,
yeah,
that's
where
I
was
getting
up
so
so.
You
already
are
busy
with
the
telemetry
thing
kind
of
fix
that
and
you're
trying
to
figure
out
for
an
issue
as
well
like
a
teacher
right,
yeah.
C
B
Look
from
a
marketing
perspective
that
meta
about
the
google's
paid
speed
thing
is
a
is
a
big
win
like
a
marketing
sort
of
like
win,
you
know,
just
to
say
bankrupt
is,
will
get
you
better
rankings
out
of
the
books,
yeah.
A
I
A
Hard
like
there
are
a
couple
of
things
that
already
have
sub
issues
that
are
getting
a
lot
of
pushback
for
various
different
reasons.
So
yeah
it's
it's
a
meta.
We
would
probably
need
to
pick
like
one
of
the
sub
items
and
focus
on
that
and
then
another
one
in
the
next
release
and
focus
on
that
and
try
and
figure
out
how
to
get
the
biggest
wins
in
first.
H
How
about
the
markdown
module
encore.
A
We
do
we
do
have
an
issue
in
court
that
talks
about
switching
from
using
html
and
translatable
strings
to
markdown,
but
I
think
that
sort
of
would
go
in
the
same
thing
here
where
it's
like.
If
we're
going
to
switch
from
html
to
markdown
in
translatable
strings,
which
that
would
be
like
a
core
like
support,
markdown
and
core
a
bigger
picture
issue
too,
that
might
be
a
2.x
issue.
Yeah
interesting.
B
So
government
agencies
that
are
using
the
gov
cms
platform,
the
content
editors,
are
being
sort
of
like
I'll
use.
The
thing
in
quotes
forced
to
learn
html
because
they
want
to
do
a
little
bit
more
with
their
content,
editing
without
having
to
go
to
their
developer
partner,
each
time,
which
means
more
cost.
B
So
if
we,
if
we
find
solid
evidence
that
for
non-developer
people
that
have
never
had
a
any
anything
to
do
with
html,
it's
easier
for
them
to
understand
and
write
in
markdown,
maybe
that
could
be
a
drive
for
that
issue,
but
from
memory
that
was
one
of
the
arguments
in
the
that
issue
that
was
filed
is
really
marked
down
easier
and
for
who
is
it
like?
The
target
audience
here
should
be
content.
Editors
and
html
is
code,
so
so,
and
so
is
markdown,
but
which
one
is
easier.
D
I've
also
noticed
I
mean
intuitively,
it
just
seems
like
if
you
look
at
markdown,
you
know
at
something
a
markdown
formatted
document.
If
you
don't
know
that
markdown
exists,
it
like
turns
it
into
a
formatted
thing.
It
looks
just
like
how
people
dress
up
code,
so
it's
like
you,
don't
even
know
where,
whereas
with
html
there's
there's
no
such
thing,
you
see
a
page
of
html.
D
You
know
that
you
know
somebody
didn't
just
happen
to
write
that
so
so
I
I
would
suspect
that
that
without
being
taught
it,
you
could
give
somebody
something
written
in
markdown
and
and
just
tell
them.
You
know
edit
this
and
there's
a
good
chance.
They'll
get
it
right.
I
mean
they
won't.
They
won't
know
how
to
add
new
features.
But
if
you
do,
if
you
have
something
existed,
you
can
edit
it.
H
H
B
A
B
Yeah
from
from
a
marketing
perspective,
as
I
said,
I
think
that
we
should
focus
on
things
that
bring
like
the
loudest,
as
in
selling
points
that
marketing
people
could
be
convinced
to
use
like
in
agencies
and
then
and
then
also
one
thing
that
should
be
a
focus
for
the
next
a
few
years
until
d7
is
end
of
life
is
making
it
easier
to
upgrade.
So
anything
that
has
to
do
with
making
it
easier
to
upgrade
from
d7
should
be
prioritized.
B
A
Okay,
so
if
that's
kind
of
what
I
was
thinking
too,
but
then
that
also
brings
up
the
question
like
what
kinds
of
issues
are
things
that
are
most
important
to
people
who
are
upgrading
from
seven
like
is:
is
that
like
adding
more
backwards
compatibility,
something
that's
important
or
is
like
streamlining
the
upgrade
process
to
like
automate
things
or
like
there's
so
many
options
of
ways
that
we
could
try
and
make
that
better
that
we're
not
currently
working
on-
and
I
don't
know,
and
and
does
this
stuff
need
to
go
in
core
if
we
know
that
long-term
people
aren't
going
to
be
moving
from
drupal
7,
or
should
it
be
stuff
that
happens
in
like
coder
module
or
develop
module?
A
Or
I
don't
know
it's
it's
tricky.
B
Yeah,
so
one
thing
that
I
keep
because
I
don't
actually
do
any
migrations,
I
keep
bringing
it
up.
I
get
an
answer
and
then
I
forget
it.
B
Most
people
seem
to
be
either
using
feeds
to
get
their
content
over
to
the
backdrop
side,
there's
some
people
that
are
doing
the
upgrades,
but
do
we
have
the
option
to
just
create
a
blank
site,
a
blank
backdrop
site
and
then
point
it
with
credentials
to
our
database
and
have
it
all
things?
Do
we
have
that.
A
Yeah
but
you
don't
actually
create
a
blank
backdrop
site,
you
create
a
code
base
and
then
you
point
it
at
your
drupal
7
database
and
then
it
just
converts
everything
for
you
and
that's
the
recommended
way
to
move
an
existing
site.
It's
the
same,
like
your
bull,
six,
one,
two
triple
seven
or
triple
five,
one
two
table
six
and
it's
built
in
and
it
yeah.
B
But
better,
but
but
the
way
that
the
way
that
it
works
now
is
people
get
a
code
base
and
they
point
it
to
an
existing
database,
a
d7
database
and
it
converts
it.
What
I
was
talking
about
is
blindside
fully
installed
and
pointed
to
the
database
and
then
say:
yep
full
content.
All
users
pull
these
pull
that
with
checkboxes
like
there's
an.
A
Issue,
that's
what
I
put
in
the
queue.
It's
called
upgrade
ui
module
similar
to
migrate
july
interpolate,
where
it
essentially
would
be
the
same
ui
as
you
have
in
triple
eight
and
it
would
it
would.
You
would
think
it
was
working
the
way
you're
describing,
but
in
reality
what
it
would
do
is
take
that
freshly
installed
database
you
just
made
and
throw
it
away
and
replace
it
with
the
triple
seven
database.
But
at
least
it
provides
people
a
working
user
interface
to
get
to
that
step.
E
E
B
Demo
boxes
right
so
from
my
david's
destroyer,
a
digital
agency
perspective
that
wants
to
evaluate
backtrack
right.
They
wonder.
Oh,
we
have
those
three
four
sites
that
we
need
to
migrate.
How
well
is
it
going
to
work?
How
like
people,
keep
saying
people
in
the?
In
the
backdrop,
land
keep
saying
promising
that
it's
going
to
be
easy,
but
how
easy
is
it
going
to
be?
B
And
if
we
can
get
to
a
point
where
we
tell
them
spin
up
a
demo
site
point
it
to
a
database
and
see
how
much
it
gets
you
to
where
you
want
to
go,
and
then
that
should
give
you
an
idea.
So
that's
that's
a
selling
point.
That's
that's
how
I
see
it!
That's
why
I
sort
of
like
I
said
that
this
is
important
to
get
it
even
if
it
was
a
contrib
module.
B
B
G
All
right,
what
should
we
wrap
up
for
today?
I
kind
of
agree.
We
didn't
get
definitive
things,
but
I
think
that's
fine.
I
I
think
that
really
for
deciding
what
to
work
on,
we
should
still
follow
the
normal
procedures.
You
know
milestone
candidates
and
advocates,
and
this
is
really
just
kind
of
like
brainstorming
exercise.
G
A
G
C
What
I
would
have
what
I
would
have
liked
is
to
sort
of
go
around
and
hear
what
everybody
again
not
making
a
decision,
but
just
hear
what
everybody
is
excited
about
and
or
what
they
think
would
be
valuable
and
there
might
be
other
ways
of
doing
that
asynchronously
either
in
zulu,
or
maybe
I
create
an
issue
in
the
form
which
we've
kind
of
already
done,
but
but
the
difference
would
be
that
I
really
go
out
and
we
like
point
people
at
this
list
of
issues,
and
we
say:
hey
pick
the
one
or
two
that
you
really
like
and
just
tell
us
it's
not
a
commitment
to
do
it.
B
C
Right,
yep,
except
that
they
actually
decide
what
is
they're
going
to
work
on
based
on
those
quotes
right
and
to
me
it's
like.
We
can't
say
that
the
thing
that
wins
is
what
the
thing
we're
going
to
work
on,
because
we
we
don't
know
if
anybody
wants
to
work
on
it,
but
if
we
at
least
knew
what
people
were
interested
in,
it
could
influence
us.
B
B
G
Maybe
maybe
and
yeah
and
as
always
thank
github,
so
yeah
and
next
week
everybody.