►
From YouTube: Backdrop Weekly - June 10th, 2021
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
Hello
folks,
it's
june
10
2021.
This
is
the
backdrop
weekly
developers
call
we
get
together
every
week
to
talk
about
priorities
for
backdrop.
This
week
is
a
special
one
where
we
are
going
to
be
looking
at
priorities
for
the
1.20
release.
The
release
will
be
coming
out
september
in
september,
but
before
we
dive
in
too
deep
we're
going
to
do
some
introductions,
my
name
is
nate
lampton,
I'm
quick
sketch
on
the
internet
and
I'm
a
core
committer
and
I
live
in
oakland
california.
A
Let's
get
an
introduction
from
greg.
Please.
B
Hi,
my
name
is
greg,
I'm
usually
in
australia,
but
now
joining
from
greece
interested
in
anything
related
to
backdrop,
and
this
meeting
is
going
to
be
interesting
as
well,
because
we're
going
to
decide
on
certain
other
features
that
we're
going
to
push
for
yeah.
That's
it.
C
Team,
my
name
is
tim
erickson,
st
paul
tim,
I'm
in
deerwood,
minnesota
and
yeah,
nothing
new
to
say,
I'm
here
to
hear
what
our
priorities
are.
Thank
you.
Olaf.
D
I'm
olaf
garbienski
from
hamburg
in
germany
and
yeah,
I'm
part
of
the
project
management
committee
of
backdrop.
I
also
care
sort
of
the
localization
server
or
translation
server
for
backdrop.
So
if
you
have
any
question
regarding
translations,
please
ping
me
in
zootlet,
for
example,
and
yeah.
I
am
looking
forward
to
this
meeting
and
I
don't
see
everyone
else,
because
I'm
on
the
phone
so
yeah.
E
I'm
robert
lang
bug
folder
on
the
internet
from
altadean,
california
and
I've
no
particular.
F
I'm
justin
christopherson,
I'm
in
denver
colorado.
I
volunteer
for
infrastructure
services
and
help
out
wherever
I
can.
G
I'm
jen
lampton
joining
from
oakland
california,
as
I
mentioned
in
the
last
meeting,
I've
been
super
busy
and
backed
up
and
dribbling
the
last
few
weeks,
so
yeah
it's
gonna
be
exciting,
also
because
I'm
working
on
drupal
backdrop
upgrade
so
hopefully
I'll
help
make
that
process
less
painful
in
this.
This
job
too
it'll
be
great.
G
So
did
you
guys
talk
about
flex
lighter
paragraphs
last
week?
No,
I
think
we
skipped
the
whole
section
last
week
so,
oh
well,
maybe
I
should
do
more
modules
than
this
anyway.
I
was
really
excited
when
I
saw
the
backdrop.
Gotta
flex
lighter
paragraphs
port,
so
anyway
that's
ready.
We
also
have
gallery
tyler
and
field
default
token,
which
were
both
both
came
out
this
week.
So
that's
great
and
then,
let's
see.
G
Oh,
I
don't
have
the
link
anymore
well
there.
It
is
just
really
quick,
I'm
checking
to
see
if
there's
anything
else
until
last
week,
so
this
would
go
all
the
way
back
to
may
27th
views.
Summarize
you
talking
about
views
summarize
nope
nope.
We
summarize
this
out
and
I
know
we
talked
about
image
magic
before
that.
So
I
think
that's
all
of
them
redirect
import.
Oh
right,
I
did
that
one
too
yeah.
A
Great
there
are
also
some
website
updates
and
I
think
we,
you
know
we're
trying
to
get
to
the
120
portion
of
the
meeting,
but
there's
been
some
activity.
That's
important
to
note
the
main
backdrop
cms.org
web
server
that
runs
pretty
much
everything
in
backdrops
infrastructure
was
upgraded
to
php
7.4.
A
Thank
you,
justin
for
doing
that,
upgrade
and
and
keeping
our
servers
up
to
date.
There
have
been
a
couple
of
hiccups,
though
the
packager
was
briefly
broken
and
sandbox
demos
also
were
affected
for
a
little
while
both
of
those
things
are
corrected
now.
But
if
there
are
any
other
parts
of
the
website
that
anyone
in
the
community
notices
that
there's
an
issue,
you
can
get
a
hold
of
justin
on
zulip
he's
lara's
design.
A
Did
you
just
grimace
justin
or
you
can
write
an
email
to
info
backdrop
cms.org
if
you
want
to
just
reach
a
large
group
of
people
to
make
sure
that
somebody
gets
your
message,
that's
the
best
contact
location.
A
Let's
see,
there's
also
a
note
here
about
the
events
site.
Maybe
tim
is
that
or
jen
is.
Is
that
something
you
guys
would
like
to
mention
just
we're.
A
C
G
C
To
elaborate
slightly
we'll
be
sort
of
sprinting
and
just
getting
a
few
things
ready
for
backdrop
live
on
sunday
at
one
o'clock
pacific
time.
So
if
anybody
wants
to
join
us
and
just
help
us
get
ready
for
backdrop,
live
feel
free
to
to
find
us
in
zula.
A
Okay,
there's
also
one
last
note
here
about
adding
markdown,
possibly
to
some
of
the
backdrop
cms.org
sites,
but
apparently
that
was
covered
in
the
last
meeting.
A
So
if
you're
interested
in
hearing
the
discussion
about
that
check
out
the
recording
from
the
previous
meeting,
okay
and
then
we'll
go
into
the
1.20
planning
speaking
of
recordings,
I
feel
like
it's
important,
that
we
say
our
express
apologies,
that
last
week's
meeting
for
some
reason
the
broadcast
failed
to
record
to
youtube
we're
absolutely
certain
that
we
sent
it
to
youtube
and
but
the
the
actual
video
file
seems
to
have
disappeared
into
the
ether
and
we
are
not
sure
what
happened
to
it.
A
So
it's
a
bit
of
a
bummer
because
we
covered
like
four
issues
pretty
in
depth
last
week.
But
what
we'll
do
is
we'll
do
a
little
bit
of
a
recap
on
what
those
issues
were
before
trying
to
get
into
some
new
items.
A
So
generally,
what
we're
about
to
do
is
we're
taking
a
look
at
the
survey
results
for
what
community
members
feel
are
the
most
important
features
to
include
in
backdrop
core.
You
can
see
the
survey
site
at
survey.backdropcms.org
and
that's
has
a
list
of
high
priority
features
that
people
submitted
through
the
forum,
and
then
we
did
a
survey
asking
like
what
allowing
people
to
vote
for
the
things
that
they
thought
was
most
important.
A
Although
that
list
is
not
canonical,
and
it's
not
really
special,
it's
just
what
people
brought
up.
It
happens
to
be
pretty
comprehensive,
as
for
including
things
that
we've
been
trying
to
get
done
for
a
long
time,
some
of
them
all
the
way
back
to
the
original
release
of
backdrop,
and
also
things
that
everybody
recognizes
as
being
like
a
high
priority
thing.
So
so
we're
going
through
that
list,
even
though
it's
not
comprehensive.
A
If
you
wanted
to
focus
on
something
else,
absolutely
is
that
choice,
but
our
objective
here
is
to
kind
of,
as
always,
draw
attention
to
particular
issues,
build
enthusiasm
for
these
issues
and
try
to
focus
our
community's
attention
onto
specific
issues
so
that
we
can
get
some
of
these
issues
done
rather
than
fragmenting
and
moving
forward,
but
not
completing
like
a
dozen
different
issues.
A
So
we'll
first
go
over
the
items
from
last
week
and
kind
of
a
quick
summary
on
them,
the
the
most
popular
feature-
and
this
is
an
order
of
the
the
features
that
receive
the
most
votes.
A
So
the
most
voted
for
item
was
adding
field
group
functionality
to
core,
and
the
summary
points
on
that
one
is
that
I
think
that
the
the
most
direct
route
forward
on
that
one
is
to
put
field
group
module
functionality
into
core.
Essentially,
as
is
the
issue,
got,
has
gotten
bogged
down
with
ideas
of
doing
like
major
revamps
to
the
ui
and
the
way
that
it
works,
and
the
kind
of
outcome
of
that
issue
was
I
it's
like.
A
A
The
most
promising
approach
for
that
issue
is
that
there
is
a
contrib
module
called
html5
upload
that
solves
the
problem
in
contrib
and
the
most
likely
success
route
is
that
if
we
could
take
that
module's
approach
and
adapt
it
to
core,
then
that
would
be
a
great
way
to
go.
A
We
also
discussed
a
little
bit
about
not
including
a
third-party
library
like
dropzone.js,
because
html
has
already
matured
to
the
point
that
multiple
file
uploads
is
not
really
a
special
thing
for
browsers
to
handle.
So
we'd
prefer
a
direct
browser
implementation
over
building
a
third-party
library
to
do
the
uploading.
A
A
The
big
caveats
to
its
adoption
are
that
we
don't
have
upgrade
paths
for
the
various
different
other
types
of
references:
that's
user
reference
and
node
reference
and
entity
reference
as
well
as
taxonomy
term
references.
So
there's
four
different
modules
that
we
conceivably
need
to
support
in
an
upgrade
path
and
that's
been.
I
did
work
on
upgrade.
G
A
Yeah
and
that's
the
thing
is
that
we
can't
like
assume
that
we
can
move
everybody
to
a
new
module
and
have
it
be
automatic,
like
you
can't
be
part
of
update.php,
there
needs
to
be
an
opt-in
process
to
volunteer
into
those
upgrades,
because
if
you
have
custom
code,
you
know
or
views
configured
like
all
of
there's
other
stuff.
That
ties
in
it's
not
just
the
migration
of
the
data
and
I
think.
A
Yeah
so
so
I
think
generally,
we
were
thinking
that
possibly
those
upgrades,
because
it's
been
the
sticking
point
for
so
long.
Maybe
we
could
work
on
something
leave
the
upgrades
out
for
the
time
being
and
either
delegate
that
to
contrib
work
on
it
as
a
follow-up,
but
not
have
it
be
a
requirement
to
reference
module
in
core.
B
Yeah-
and
I
think
that
there's
a
point
there,
because
fair
enough
about
d7
moving
to
backdrop
but
sites
that
have
been
built
in
backdrop
from
the
scratch,
if
they
start
using
whatever
is
available
in
core,
which
would
be
the
preferred
way.
Then
eventually
we'll
have
less
of
an
issue
with
the
upgrades
or
you
know
they
can
contribute.
Modules
will
start
getting
used
less.
G
Yeah
dealing
with
upgrades
is
going
to
get
harder
and
harder,
though,
because
right
now,
they're
all
written
assuming
you're
coming
from
drupal
7,
and
so
they
use
all
the
drupal
7
upgrades
with
the
like
update
last
whatever.
As
soon
as
we
introduce
people
who
are
now
running
backed
up
versions
of
those
modules,
we
now
got
to
support
two
different
upgrade
paths,
one
for
somebody
going
from
drupal
7
to
backdrop
and
one
from
someone
going
from
backdrop
to
backdrop
on
the
same
module
switches.
So
that's
gonna
get
really
complicated.
G
A
Yeah,
it's
stuck
exactly
so
to
unstick
it.
The
suggestion
is,
is
that
we
separate
that
we
don't
make
upgrades
as
part
of
the
requirement
for
putting
a
reference
module
in
core
the
next
step
here
for
reference
module
actually
is
not
related
to
core.
It's
just
purely
that
the
reference
module
as
it
exists
and
contrib
has
never
had
an
official
release,
and
that
has
made
it
so
that
it's
not
accessible
from
the
module
installer
and
it's
not
on
backdropcms.org
as
a
listed
module.
A
G
It
does
have
a
release,
it
was
just
not
named
yeah.
We
just
need
to
make
another
one,
so
we
changed
the
name
convention
so
that,
if
you
added
like
beta,
it
wouldn't
show
up
anywhere.
B
Yeah
because
then
we'll
have
to
take
care
of
the
upgrade
from
that
and
adding
that
module
to
the.
I
can't
remember
now
what
the
function
is
called,
I
think,
merged
something.
A
Yeah
backdrop:
core
merged
modules,.
A
C
A
G
G
There
are
three
issues
that
are
marked
as
release
blockers,
so
I
might
check
on
those
and
see
these
are
ones
that
mike
labeled
as
release
blockers
when
he
was
maintaining.
So
I
want
to
make
sure-
and
they
there's
some
that
seem
to
be
kind
of
like
access
related
and
something
that
might
cause
fatal
errors.
So
getting
those
knocked
out
wouldn't
be
good
before
I
think
this
people
are
gonna
start
installing
it
from
the
ui.
You
wanna
make
sure
they're
not
gonna
break
their
site
in
a
way
that
they
can't
get
out
of
it.
But
okay.
D
F
A
All
right,
let's
see
and
then
the
last
one
that
we
covered
last
week,
was
adding
a
recipe
project
type
to
backdrop,
issue
3763.
A
The
let's
see
I
don't
have
too
many
notes
on
here
other
than
we
have
a
a
bug
that
we'd
like
to
get
fixed
issue
3224
that
has
to
do
with
running
config
sync
when
a
module
is
installed,
because
that
would
unblock
most
of
what
we've
been
talking
about
as
recipes,
you
could
implement
just
simply
as
a
module
that
included
a
bunch
of
config
files
like
a
recipe
would
be
a
module.
A
So
that's
kind
of
the
the
state
on
things
there
is
that
recipes
wouldn't
be
a
new
thing
potentially,
for
now
they
would
just
be
modules
that
bundle
config.
So
first
item
is
fix
the
bundling
of
config
with
modules,
and
that
is
issue
3224
and
the
second
one
is
exposing
the
labels
on
backdrop
cms.org,
so
that
you
can
find
modules
that
have
specified
their
particular
tags
in
their
dot
info
file,
which
I,
I
think,
there's
an
issue
on
backdrop.
Cms.Org's
queue
for
that.
But
I
I
don't
have
it
offhand.
A
Tim
or
jen
do
you
guys
have
additional
feedback
on
that?
One.
A
Okay,
all
right!
Well,
let's
get
into
some
of
the
new
ones.
Then
we
have
lots
of
time
left
in
the
meeting
to
banter
over
these
next
four
items
that
were
the
most
popular
items
in
the
survey
results.
G
I
know
wes
has
been
doing
some
work
so
even
though
icon
fonts
are
sort
of
like
the
proven
solution.
Right
now
and
there's
a
bunch
of
weird,
like
cutting
edge
stuff
that
brennan
developers
are
really
excited
about.
I
was
really
worried
about
the
new
stuff,
just
because
it
sort
of
goes
against
our
philosophy.
G
But
wes
has
an
example
of
something
that
he's
working
on
for
backdrop
core,
where
he
created
a
svg
based
icon
solution
for
red
hat,
and
he
mocked
up
a
version
of
what
that
might
look
like
for
backdrop
too,
and
so
it
looks
to
me
like
it
solved
all
of
the
things
that
we
wanted
to
have
solved
by
having
another
confront
in
core
and
it
might
be
worth
having
other
people
evaluate
that
too.
Instead
of
just
putting
in
a
pot.
A
G
A
Same
sort
of
thoughts
here
that
icon
fonts
they've
always
been
a
convenient
way
to
achieve
something
that
has
always
been
kind
of
like
wow,
that's
kind
of
a
hack.
You
know
it's
like
it's
kind
of
like
using
flash
for
fonts.
You
know
before
you
could
load
fonts
like
I
feel
like
it's,
it's
a
shim
to
make
it
so
that
you
can
do
iconography
in
a
way
that
is
broadly
supported
across
all
browsers.
A
So
I'm
excited
about
the
this
new
idea,
but
there's
other
things
about
icon,
fonts,
that
people
like
like
being
able
to
attach
an
icon
just
by
adding
a
particular
class
right.
That's
the
the
thing
that
people
love
so
much
about
font
awesome.
Is
that
as
a
very
consistent
naming
convention,
you
say:
f
a
you
know,
dash
whatever
the
icon
type
is,
and
then
it's
like
bam.
You
can
make
the
icon
really
easily.
A
So
I
think
the
ease
of
use
is
something
that
we
may
want
to
preserve,
even
if
we
don't
use
an
actual
icon
font.
I
think
that's
the
approach
that
wes
has
been
taking
right.
It's
like
it's
not
using
an
icon
font
anymore,
where
you're
loading,
a
custom
font
on
the
page,
it's
using
svgs,
but
it
still
has
the
naming
convention
mechanism
of
an
icon
font
is
that.
Does
that
sound
right,
jen.
G
Yeah,
it's
a
little
bit
different
because
he's
not
doing
it
like
he's,
actually
creating
a
new
html
element,
a
web
component,
so
it
it
is
going
to
be
a
little
like
you'd
actually
have
to
include
that
element,
but
it
does
have
the
same
like
standard
class
naming
convention
and
because
they're
svgs
you
have
the
option
to
like
color
them,
depending
on
how
crazy
you
want
to
get
with
your
css
but
yeah,
it's
it's
sort
of
like
a
it.
G
A
Yeah,
looking
at
this
now
in
this
issue,
as
a
code
pen,
that
kind
of
proof
of
concepts
it
and
yeah
it
make
making
a
custom.
Html
element
is
a
little
bit.
A
A
G
Is
the
kind
of
thing
where
you
know
we
could
get
really
excited
about
it
and
put
it
in
core
and
then
it
could
like
die
next
year
and
we'd
be
like
well,
we've
got
it
in
core
and
we
tried
something
new,
but
you
know,
icon
fonts
have
been
around
for
a
long
time.
You
could
just
say:
well
that's
the
standard,
we're
going
to
put
it
in
core,
but
then
you
know
it's
it's
it's
this
trade!
It's
this
constantly
evolving
web
problem
that
we're
always
going
to
have
so
worth.
Considering.
A
Well,
this
I
mean
even
even
making
new
custom
elements
isn't
exactly
new.
You
know,
we've
had
brian
talk
about
the
hacks
editor
at,
like
the
last
backdrop,
live
and
he's
been
talking
about
hacks
for
the
last
three
or
four
years.
You
know,
and
so
that's
entirely,
based
on
making
custom
html
elements,
so
this
technology
isn't
exactly
new
but
yeah.
I
share
your
concern
a
little
bit
that
it
could
be
different.
A
One
thing
that
actually
works
almost
in
this
system's
favor,
however,
is
that
by
making
it
a
dedicated,
html
element,
it
just
doesn't
suddenly
show
up
absolutely
everywhere
throughout
your
entire
site,
like
like
fon
awesome
does
fauna
some
actually
can
be
problematic
that
people
can
start
adding
font
awesome
icons
in
the
middle
of
their
body
text,
because
it's
just
you
know
an
an
eye
tag
with
a
class
on
it,
and
so
one
of
the
other
concerns
about
icon
fonts
is
that
it
basically
would
be
so
broad
and
be
so
accessible
absolutely
everywhere
that
you
would
never
be
able
to
remove
it
from
core.
A
If
we
put
it
in
core,
we
can
never
take
it
back
out,
because
people's
content
would
start
depending
on
it,
and
I
think
that
that
wouldn't
be
the
case
with
something
like
this
that
that,
like
we
could
probably
make
these
systems
available
in
backdrop
core,
but
it'd
be
pretty
unlikely
that
someone
would
use
it
in
their
text.
Formats.
G
I
mean,
I
think,
if
someone
wants
an
icon
in
their
text,
format
they're
going
to
put
it
in
their
text
regardless
of
what
tools
we
give
them
to
do
it,
and
the
good
thing
about
having
fun
awesome
is
that
it's
easy
for
them
to
do
that,
and
just.
B
Disagrees,
I
think,
I
think
that
the
main
use
cases
for
core
like
when
it
comes
to
core.
It
would
be
the
admin
bar
icons
that
we
currently
have,
and
then
things
like
the
dashboard
icons
and
the
main
configuration
page
like
this
last
admin
config
but
yeah.
B
And
also
maybe
the
the
the
status
messages
like
the
ticks,
the
eyes
and
the
exclamation
marks
for
the
errors
and
the
warnings.
A
Yeah
yeah,
possibly
yeah
well
anyway,
I'm
not
quite
sure
where
to
say,
like
you
know
what
what
approach
we
should
take
on
this,
because,
if
we're
still
really
kind
of
we're,
not
really
at
implementation
point
yet
we're
still
kind
of
in
the
brainstorming
phase
here.
So
I
don't
really
think
that
we
can
say
you
know
like
yeah.
Let's,
let's
go
forward
like
you
know
on
this
one
for
1.20,
because
we
don't
really
know
if
that
experimentation
and
discussion
will
really.
You
know,
be
finished
in
time.
A
So
I
think
for
now
take
everybody
if
you're
interested
in
that
sort
of
thing
take
a
look
at
issue.
364
provide
feedback
to
the
work
that
has
been
happening
there
and
way.
You're
like
put
in
your
opinions
as
to
how
you
think,
icon,
fonts
or
icons
just
in
general,
should
be
implemented
and
how
how
they
would
be
used,
like
your
preferences,
for
the
way
that
you
would
want
to
use
icons
in
core.
B
And
I
think
the
other
use
case,
at
least
in
drupal
land,
is
for
custom
menus.
I
think
this
is
a
contrib
module
that
does
that
allows
you
to
prepend
icons
to
your
menu.
E
A
Okay,
well,
let's,
let's
move
on
to
the
next
one,
which
is
automatic,
updates
issue
2018.,
so
automatic
updates
is,
is
in
a
number
of
various
states.
The
this
issue,
2018,
is
a
meta
issue
that
has
a
number
of
smaller
issues
inside
of
it
right
now.
A
This
is
effectively
on
my
plate
to
kind
of
take
the
lead
on
on
implementation.
Here,
where
we
are
on
this,
is
we
have
a
number
of
issues
that
have
been
started
like
issue
3714?
A
That's
digital
signatures
that
john
franklin
put
together
a
mechanism
for
having
backdrop
cms.org
sign
packages,
so
that,
when
a
backdrop
site
downloads
those
packages,
it
can
verify
that
they're
real
packages
that
came
from
backdropcms.org.
So
it's
a
good
security
improvement.
A
A
I'm
actually
surprised
that
I'm
not
seeing
it
here
that
there's
a
drupal
7
module
that
in
a
actually
a
drupal,
7
and
drupal
8
module
for
enabling
automatic
updates
within
drupal,
and
that
module
primarily
provides
a
whole
set
of
pre-flight
checks
to
make
sure
that
it's
safe
to
do
an
automatic
update.
It
does
things
like
checking
if
any
core
files
have
been
modified,
checking
to
make
sure
permissions
are
all
set
up
correctly.
A
A
There,
also,
in
theory,
that
module
supposedly
does
the
actual
automatic
updating
which
is
an
unanswered
question
in
ours.
We
have
a
issue
414.
That
is
the
automatic
part
of
the
update
and
the
big
question
there
is.
How
does
update.php
get
run
because,
right
now,
even
with
backdrop
core,
when
you
have
backdrop
core
self
update,
you
still
have
to
go
to
update.php
like
as
an
administrator
to
actually
run
database
upgrades
so
figuring
out
how
drupal
has
solved
that
problem
would
be
a
big
boost
towards
this
project.
A
If
you'd
like
to
start
working
on
adapting
some
of
those
things
from
from
the
drupal
project,
that
would
be
a
good,
a
good
place
to
join
in.
A
Let's
see
olaf
mentioned
before
the
call
got
started,
there's
also
just
a
small
bug
that
issue
3008
covers
sim
links
that
if
you
have
a
sim
link
to
your
document
root
and
then
that
backdrop
inside
of
that,
that
self
updates
currently
don't
work
and
if
self
updates
don't
work,
then
automatic
updates
definitely
won't
either,
and
so
that
is
just
a
bug
that
has
a
pull
request
that
could
use
some
review.
A
A
Already
myself
and
john
franklin,
who
wrote
the
original
code,
I'm
committed
to
continuing
and
finishing
at
least
that
portion
of
automatic
updates,
so
I
I'd
like
to
at
least
still
be
mostly
responsible
for
automatic
updates,
but
I
definitely
would
love
some
some,
some
more
developer
time
from
from
people
that
are
interested
in
some
of
these
other
issues
that
are
also
related
to
automatic
updates,
like
pulling
in
the
stuff
from
the
drupal
project,
would
be
a
great
place
to
have
some
help.
A
Okay,
we'll
go
to
the
next
one.
Then
we've
got
about
15
minutes
left,
so
the
next
one
is
exposing
fields
to
visibility,
conditions
within
layout
module.
That's
issue
4728.
A
I
I
like
this
issue
because
I
get
to
punt
it
to
someone
else
jen.
This
was
an
issue
that
you
advocated
for
last
release,
and
you
know
it's
in
the
top
10
list
of
people
of
features
that
people
think
should
be
included
in
core
sooner
so
I'd
be
curious
to
hear
your
thoughts
about.
You
know
the
state
of
this
and,
if
we're
likely
to
see
some
activity
for
the
next.
G
Release
so
I
think
this
issue
is
actually
pretty
close.
We
already
have
a
contrib
module
that
does
most
of
what
we
need
and
we
have
a
core
patch
that
I
started
that
improves
a
little
bit
on
the
user
interface,
and
so
I
think
all
we
need
to
do
is
make
the
contrib
module,
not
a
module
like
make
it
leverage
layout,
instead
of
being
its
own
modules,
plugin
and
then
add
the
user
interface
improvement.
So
it's
definitely
likely
to
happen
in
terms
of
the
amount
of
work
involved.
It's
not
a
lot.
G
A
And
for
this
one,
let's
see
there
is
a.
There
is
already
a
pull
request.
A
G
A
Yeah,
which
is
a
big
feature
I
mean
it
would
have
a
lot
of
flexibility,
but
that
also
means
it
has
a
kind
of
a
complex
interface.
Just
like
fuse
does
yeah,
and
so
what
are
we
shooting
for
here?
We're
shooting
for
doing
the
full
contrib
solution.
C
G
C
A
The
value
of
a
field-
yeah-
okay,
so
you
could
potentially
say
like-
have
a
date
field.
E
A
G
I
don't
think
so,
and
I
don't
think
that
the
current
value
it
only
well,
I
don't
know
I'll,
have
to
look
at
the
kindred
module,
but
there
is
some
issue
about
like
a
fields
keys
like
it
by
default
for
text
they're
almost
always
value
but
like
for
date
it's
different
and
for
address
it's
different
for
email.
It's
different,
and
I
noticed
there
was
a
problem
in
the
drupal
solution
where
email
fields,
weren't
getting
checked
so
I'll
check
and
see
if
that
problem
exists.
For
backdrop
too,.
A
Okay,
well,
the
last
one.
We
don't
have
too
much
to
discuss
on
because
it's
it's
really
getting
close
to
being
solved,
and
that
is
the
feature
to
add
a
file
name
filter
to
the
media
library,
dialog
issue
3293..
A
This
is
seeing
a
lot
of
progress
in
the
past
week.
Laryn
was
the
is
the
advocate
for
it,
but
he
was
also
the
advocate
for
last
release
and
he
has
created
a
new
pull
request
that
effectively
solves
the
problem,
which
is
great.
A
It
makes
it
so
that
any
exposed
filters
that
you
add
to
the
view
now
work
correctly.
So
in
a
way
this
is
not
necessarily
even
a
a
new
feature
improvement.
This
is
actually
could
be
like
a
bug
fix
that
exposed
filters.
Don't
work
right
now
in
the
media
library,
dialogue
and
his
pull
request
fixes
that
so
it's
a
bug,
it
could
be
considered
a
bug
fix.
A
A
You
know
like
the
way
that
people
have
themed
their
sites
or
something
so
that
issue
has
been
moving
forward.
I
tested
it
out
this
week.
It
works
absolutely
great,
exactly
like
you
would
expect,
and
so
I
think
that
one
at
the
very
least
will
be
in
1.20,
because
it's
yeah,
it's
perfect.
Basically,
so
thanks
lauren
for
putting
in
some
time
and
figuring
that
one
out.
A
I
also
understand
that
it
was
inspired
by
some
of
bw
panda's
work,
so
nice,
I'm
glad
that
that
has
all
panned
out.
A
So
that's
it
for
the
the
items
that
I
pulled
from
the
survey.
We
also
have
some
opportunity
here
to
talk
about
other
things
that
you
know.
If
just
anyone
present
wants
to
mention
their
favorite
issue,
then
we
can
do
that
now.
I
see
that
greg
is
starting
to
put
something
in
here
before.
C
Before
greg
starts
talking,
I
on
a
general
note
like
to
mention
that
this
is
the
1.20
I
put
on
my
outreach
hat
the
1.20
release,
which
is
it
has
that
round
number
magic
which
you
know
it
feels
like
a
big
release
because
it's
the
20th,
I
don't
know
if
that's
even
true,
because
it
might
be
the
21st
depending
on
how
you
count
right
so
but
but
still
it's
got
the
the
2o
and
you
know
I.
I
sometimes
ask
that
question
like
there's
different.
You
know,
there's
what
we're
most.
C
It's
developers
excited
about
adding
decor,
but
there's
also
the
pr
value
like
for
1.20.
What
what
issue
might
we
be
able
to
leverage
for
some
some
outreach
in
pr,
and
I
think
automatic
updates
might
be
a
good
one
for
that
I'd
be
curious.
What
other
people,
what
people
think
might
have
the
most
sort
of
outreach
appeal
or
or
pr
appeal
for
you
know
this
could
be
sort
of
any
release,
but
for
the
1.20,
maybe
a
little
more.
So
any
I'm
just
looking
for
feedback
on
that,
yeah.
B
I
agree
with
that.
The
automatic
updates
is
a
big
thing
field
group
as
well,
and
reference
these
other
three
that,
I
think
are
key
reference
is
already
something
that
is
a
drupal
8
and
beyond
core
feature.
So
if
someone
is
comparing
products,
they
might
bring
that
argument
into
the
discussion.
A
Yeah,
as
far
as
pr
value,
I
think
automatic
updates
has
the
greatest
value
out
of
these.
Although
I
I
think
reference
is
probably
more
important
like
on
on
the
whole,
but
because
reference
module
has
like,
if
you're
comparing
us
to
drupal
reference
modules
been
in
drupal
for
all
of
drupal
8..
A
I
don't
think
it
has
quite
the
same
impact
as
saying
like
you
know,
we're
ahead
of
the
curve
on
something
I
guess
wordpress
is
on
automatic
updates,
so
we're
not
ahead
of
the
curve
there
either
but
yeah,
but
I
think
the
the
the
highest
pr
value
is
in
automatic
updates,
but
the
highest
user
value
is
probably
in
reference,
so
yeah.
I
would
probably
lean
more
towards
like
automatic
updates.
A
Anybody
else
I,
like
your
thought
process,
though
tim
yeah,
the
the
2-0,
even
though
it's
not
2.0
it'll,
definitely
catch
a
lot
of
people's
eyes.
That
1.20
looks
an
awful
lot
like
you
know,
version
2.,
let's
see
greg,
you.
A
Of
q,
additional
ideas
for
things
that
weren't
mentioned
from
the
survey,
or
at
least
not
in
these
top
eight,
do
you
want
to
cover
one
or
two
of
them.
B
Yes,
so
the
safe
drafting
core.
This
was
something
that
peter
vw
panda
intended
to
work
on
for
this
release,
but
due
to
life
and
work,
obligations
said
that
he
would
not
advocate
anymore.
So
if
he
indeed
doesn't
have
time,
I'm
keen
on
starting
that
one,
we
already
have
an
issue.
I
don't
have
the
the
issue
number
handy
right
now,
where
we
are
splitting
the
help
text
for
the
publishing
options.
So
this
is
a
start
to
sort
of
like
unblock
or
make
things
clear
for
safe
draft.
B
So
basically
we
should
have
those
options
reflected
in
the
submit
button
for
saving
the
node
yeah.
This
is
something
that
I
wanted
to
do
like
a
long
time
same
as
in
merging
the
update
pages,
and
then
the
other
point
that
I
have
is
yep.
B
That's
the
one
three
three
one,
five,
seven,
that's
the
issue
thanks
nate
and
then
the
other
thing
is
it
ties
to
the
automatic
updates
and
I
was
looking
at
the
automatic
updates,
contrib
module
for
drupal
and
they
have
two
phases
and
phase
one
does
mention
being
able
to
roll
back.
Oh
no
sorry
phase,
two
of
it
mentions
testing
and
rollback
features.
B
So
if
we
are
to
provide
automatic
updates,
we
need
to
also
make
sure
that
people,
if
something
goes
wrong,
are
able
to
reverse
or
have
a
recent
backup.
I
know
that
most
people
would
design
their
infrastructure
to
take
automatic
updates
of
their
database.
I
guess
and
files
if
they
have
automatic
core
updates
on,
but
we
can't
rely
on
them
them
actually
doing
that.
B
So
we
have
a
step
step
even
in
the
during
the
running,
update
php,
where
it
says,
stop
now
just
go
and
back
up
your
database
and
files
visits
recommended.
So
it
would
be
great
during
that
point,
to
not
have
the
users
go
and
do
another
task
and
then
come
back.
It
would
be
great
to
have
a
checkbox
and
say
yes,
please
take
a
backup
and
that'd
be
the
default,
so
yeah.
B
C
B
Yeah
and
the
the
other
thing
I
I
did
not
add
config
management
improvements.
I
think
thing
you
out
of
that
is
the
discussion
that
we
had
last
night.
C
Well,
we
briefly
talked
about
the
config
management
stuff
last
week
is
just
something
that
I've
had
some
drupal
developers
complain
to
me
about.
I
keep
running
into.
I
feel
like
it's
it's
a
bit
of
a
problem
and
tying
into
the
backup
and
migrate.
The
big
thing
one
of
the
big
frustrations
is
like
you
can
schedule
back
well,
I
could
I'm
sure
there
are
ways
to
do
this,
but
I
can
use
backup
in
my
great
module
to
automatically
back
up
my
database
and
my
file
directory.
A
If
there's
a
priority
at
all
on
having
the
backup
portion
only
like
is
that
like?
Is
that
like
a
first
step,
or
is
it
like
the
only.
G
A
Possibly
where
it's
like
just
provide
the
backups
don't
provide
the
imports,
because
the
restoration
has
a
huge
set
of
problems
just
by
itself,
but
the
backup
portion,
if
it's
really
just
like
saving
some
files
and
then
there's
a
documentation
page
on
how
to
restore
from
it.
Then
that
would
be
a
much
smaller
problem
to
solve.
C
Sure
I've
never
thought
of
that
before,
but
I
think
most
of
us
don't
need
you
know,
you
know
we
want
backups
all
the
time
and
hope
we
never
need
to
use
them,
and
so
it
might
be
a
big
step
forward
to
know
that
you
have
a
backup
and
then,
if
you
need
to
use
it,
you
know
maybe
it's
acceptable
to
send
people
and
say:
okay,
you're
gonna
need
to
use
contrib.
You
know
install
backup
and
migrate
or
something.
B
A
B
A
Or
or
maybe
not,
you
know
like
a
backup
and
migrate,
the
way
that
it
is
written
it.
It
does
a
lot
of
work
to
like
connect
to
the
database,
it
like
through
backdrops,
apis
and
stuff
like
that,
which
makes
it
actually
like
database
agnostic,
and
so
it
because
it
came
from
drupal7
where
it's
like
it
needed
to
work
with
everything.
A
And
so
backup
and
migrate
could
still
be
valuable,
potentially
is
like
a
like.
It
has
its
own
backup
and
import
mechanism
that
might
be
more
comprehensive
or
more
easy,
or
something
like
that.
So
maybe
it
would
still
do
everything
and
backdrop
core's,
backup
module
could
potentially
be
like
you
know,
have
it
have
a
different
format
for
its
backups
that
are
like
geared
towards
manual
imports
rather
than
automatic
ones
like
like
backup
and
migrate
provides?
A
A
Yeah,
maybe
maybe
potentially
we
could
still
have
both
you
know
like
if
backup
module
is
doing
the
thing
on
updates.
You
know
when
it
runs
an
update.
It
makes
a
backup
and
backup
and
migrate
is
still
used
for
like
moving
between
sites.
Something
like
that.
You
know
like
different
problems
being
solved.
E
C
I
think
a
backup
feature
in
core
also
has
some
pr
value
to
like
end
users
to
people
who
are
building
their
own
site.
I
think
it's
less
popular
amongst
developers
who
have
their
own
solutions
to
this.
A
lot
of
us
that
build
a
lot
of
sites
maybe
rely
less
on
backup
and
migrate.
But
if
you
just
want
to
build
your
own
site
having
having
that
in
core
could
be
a
good
one.
Yeah
and.
B
I
think
that
luke
has
brought
this
up
many
times
as
his
favorite
that
he
sort
of
like
tests
things
on
a
on
a
platform.
It
could
be
pantheon,
it
could
be
a
demo
site
and
then
they
want
to
back
that
up
for
whenever
they
have
time
again
to
test
things
right,
so
they
can
restore
them.
So
yeah
I've
brought
this
site
into
a
status
where
I
like
it,
export
everything.
A
Cool,
let's
see
we
are
at
the
top
of
the
hour,
there's
one
more
thing
to
mention
as
a
like
ongoing
thing
and
that's
telemetry
telemetry
isn't
particularly
slated
for
1.20,
but
it
is
our
only
initiative
right
now.
A
That
is
like
a
long
running
thing
and
telemetry
is
not
in
a
bad
place
as
far
as
like
getting
it
core
ready,
especially
the
core
module
itself
that
would
just
collect
data
and
start
sending
it
up
to
backdropcms.org
so
that
telemetry,
let's
see,
do
we
have
a
main
issue
for
this
issue.
A
285
is
the
telemetry
meta
issue
and,
let's
see,
if
that's
the
best
spot.
Yes,
that
is
that
looks
like
that's
the
best
spot
for
like
what
the
most
up-to-date
state
of
things
is.
So
telemetry
is
also
like
a
good
candidate
there
for,
like
a
you
know,
80
percent
of
the
work
is
done,
and
we
just
have
little
bits
here
and
there
to
actually
get
it
all
wired
up
and.
C
Completed
I'd
like
to
point
out
that,
in
terms
of
prioritizing
issues,
there's
a
couple
of
different
factors:
one
is
pr
value.
One
is
what
is
the
real
use,
but
the
other
is
how
close
to
complete.
Are
they
right?
No,
there
are.
There
are
some
issues
that
might
have
high
pr
value
and
could
very
easily
be
completed
just
because
they're
so
close
already,
and
that's
something
else
to
think
about.
A
Yep
totally
agree
yeah
that
that
recipes
issue,
the
bug
fix,
is
issue
3224..
B
A
Tomorrow
you
know
if
if
it
got
reviewed
and
tested,
then
then
we
could.
Then
we
could
merge
that
in
and
that's
not
even
dependent
necessarily
on
a
minor
version,
because
it's
a
bug
so,
but
maybe
we
would
want
to
use
it
like
you
say
to
maybe
for
some
pr
value.
Nonetheless,
you
know.
C
C
C
A
C
C
The
ideas
for
advocates
is
that
you
just
pick
an
issue
that
you
feel
passionate
about,
even
if
you
can't
solve
it
yourself
and
just
help,
keep
it
on
our
agenda
to
keep
it
up
to
date,
and
so
that's
one
way
you
could
take.
What
we
talked
about
today
and
implement
into
action
is
just
become
an
advocate
for
one
of
these
issues
and
sort
of
keep
pushing
it
forward
as
much
as
you
can
and
encouraging
others
to
work
on
it.
A
Yeah
and
also
related
to
advocates
what
we
had
been
doing
in
weekly
meetings
was
we
encouraged
the
advocate
to
be
at
the
weekly
meeting,
so
they
could
give
a
status
update
on
their
particular
issues.
A
It's
been
proposed
that
we
start
changing
the
format
of
our
weekly
meetings
and
for
the
past
two
weeks
we've
been
doing
these
planning
meetings
so
that
hasn't
factored
in,
but
starting
next
week.
You
know
we
haven't
made
a
decision
on
this,
so
maybe
there's
actually
question
to
tim,
jen
and
greg.
You
know
like,
should
we
start
pivoting
our
weekly
meetings
to
the
new
format
of
them
being
almost
more
like
working
sessions
where
those
people
that
need
help
on
particular
issues
or
want
to
do
deep,
dives
on
particular
issues.
A
We're
going
to
basically
have
open
sessions
where
we're
going
to
have
people
come
forward.
They'll,
hopefully
put
into
the
agenda
a
little
bit
of
preparatory
information,
so
people
get
familiar
before
the
meetings
and
then
during
the
meetings
we'll
just
like
discuss
and
try
to
work
out
the
problems,
in
particular
issues
like
real
time.
F
B
For
quest
quite
a
long
time,
so
let's
try
that,
let's
give
it
a
go:
okay
and
yeah,
and
particularly
for
document
when
he
watches
the
this
recording
later
on.
I
did
post
a
question
on
zulep
with
regards
to
would
that
new
format
sort
of
like
answer
the
the
concerns
that
he
posted
with
regards
to
you
know:
circling
around
the
same
things
without
moving
on
during
the
these
meetings.
A
Yeah
and
what
will
get
bumped
is
the
status
report
on
like
the
issues
that
are
in
1.20
and
prioritize
issues
that
are
in
like
119.
Instead,
we'll
just
be
like
going
on
on
pretty
much
whatever
issues
people
bring
forward
unless
there
are
no
things
to
discuss
like
if
no
one
comes
forward,
then
we'll
probably
fall
back
to
doing
the
status
update,
as
we
had
been
doing
for
major
issues
in
119
and
120..
C
I'm
happy
to
try
this
new
format.
My
concern
is
that
it
I
mean
my
understanding
of
this
format.
Is
that
basically,
the
main
change
is
that
rather
than
items
showing
up
automatically
week
after
week,
is
that
unless
somebody
specifically
nominates
an
issue
for
a
particular
meeting,
you
know
we
don't
necessarily
talk
about
it,
and
if
we
talk
about
something
one
week
that
doesn't
mean
it's
automatically
on
the
agenda
the
following
week:
right
it
has
to
get
renominated
each
week,
and
you
know
my
concern
is
that
we're
going
to
lose?
C
A
F
A
G
A
F
A
Okay,
okay:
greg!
Do
you
have
any
last
things
to
say:
okay,
all
right!
Well,
we'll
call
it
a
meeting,
then.
Thank
you,
everybody
here
for
for
being
present.
Thank
you
for
people
out
there
on
the
internet
that
watch
these
weekly
calls
fingers
crossed
this
video
will
post
and
everybody
will
be
able
to
watch
it
because
we
covered
a
lot
today.
So
thank
you
very
much
everybody
out
there
and
thank
you
see
you
guys
next
week.