►
From YouTube: Backdrop Weekly - Dec 17th 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
are
live
today
is
thursday
december
17th,
and
this
is
our
weekly
development
check-in
meeting
before
we
move
on
with
the
agenda.
I'd
like
to
start
with
introductions
I'll
go
first,
my
name
is
john
lampton.
I
am
joining
from
oakland
california,
where
it
is
cold
and
there's
a
lot
of
beeping
outside.
So
I
apologize
advance
for
the
construction
noises,
but
let's
turn
it
over
to
greg.
B
Hi
I'm
greg
I'm
joining
from
greece,
usually
in
australia,
though
I'm
interested
in
anything
related
to
backdrop
and
here
to
help
and
progress
things
for
one
eighteen,
zero
and
phil.
B
C
I'm
phil
ward
out
of
wichita
kansas.
I
don't
have
anything
in
particular
that
I
don't
think
I
need
to
discuss.
I
think
one
of
the
items
that
I
kind
of
advocated
for
might
have
been
taken
care
of
already,
but
anyway,
just
kind
of
here
for
some
feedback
and
see
where
I
can
help.
Let's
go
to
tim.
D
E
Larian
living
in
memphis,
tennessee
and
here
to
listen
in
on
everything,
but
here
to
talk
about
primarily
the
search
field
in
the
image
library,
the
filter,
and
hopefully
we
can
figure
something
out
for
that.
F
Nope
hi
I'm
joseph
from
las
vegas
nevada.
I'm
working
on,
I
don't
know
a
bunch
of
things
like
hashtags,
so,
okay,
phil
did
you
go.
G
Okay,
I'll
go
I'll,
go
next:
hey
I'm
male
anthem
from
oakland,
california,
and
so
yeah,
we're
closing
in
on
on
118
now,
so
I'm
excited
to
go
over
the
issues
that
we're
getting
close
to,
I
think,
is
justin
the
only
one
left
justin.
G
I
think
that's
everybody,
then,
if
justin
is
just
listening:
okay,
jen,
let's
go
back
to
you
and
get
the
contrib
updates.
Sure.
A
So
since
our
last
meeting,
there's
been
three
new
contributed
modules,
front
page
multilingual,
which
will
help
translate
your
front
page
if
your
site
is
in
more
than
one
language
schema
and
preset
api
would
imagine
schema
is
a
port
of
the
triple
schema
module.
I
haven't
looked
at
this
and
preset
api
is
for
configuration
presets,
that's
pretty
cool,
so
yeah.
A
It's!
I
just
wanted
to
thank
all
the
people
who
have
been
working
on
contributed
projects,
not
only
those
who
are
creating
new
releases,
but
there's
also
been
a
lot
of
activity
on
previous
modules.
Recently
too,
so
that's
great
tim.
Do
you
have
some
announcements.
D
I
assume
we're
talking
about
sprints
right
now.
We
did
a
sprint.
Last
saturday,
I
think
we
had
about
four
or
five
or
six
people
participate
focused
on
you
know,
stuffer
for
the
backdrop
1.8
1.18
release.
D
Now
I've
realized
that
when
I
say
1.18,
I'm
also
also
including
the
1.17
bug
fix
release
that
goes
into
that.
So
we're
going
to
do
another
sprint.
We
have
another
one
scheduled
wait.
What's
going
on
with
my
map
here
for
january,
2nd
excuse
me
so
last
sunday
we
did
one
and
now
we're
going
to
do
another
one
on
january,
2nd
right
before
code
or
feature
freeze
for
1.18.
D
We
did
also
do
a
blog
post,
where
we
are
just
giving
people
a
chance
to
list
the
issues
that
they're
really
hoping
to
get
into
the
next
set
of
releases,
and
we've
got
a
number
of
people
to
submit
issues.
Therefore,
it's
on
the
blog
I'll
post,
the
link
in
zulup
again,
but
if
you
go
to
bankrupt.org
and
go
to
the
news
section,
you'll
find
the
blog
post
about
help
wanted
for
1.18.
D
G
Excellent
yeah,
I
got
a
number
of
same
sorry.
I
think
tim,
a
good
opportunity
to
focus
and
pay
attention
to
the
things
that
we're
worried
about
or
focused
on
for
for
118..
I
had
a
really
good
day
of
reviewing
things
and
getting
things
in.
We
got
the
webp
image
format
merged
in
that
day.
That
was
very
exciting,
so
yeah
it
was
very
productive.
B
I
have
some
time
over
the
weekends,
and
I
know
that
the
previous
screen
was
last
week
and
then
the
next
officially
planned
one
is
for
the
weekend
after
the
coming
one.
But
I
plan
to
also
spring,
maybe
by
myself,
for
anyone
that
has
some
time
and
energy
feel
free
to
join.
D
I
just
like
to
raise
the
point
that
I
think
if
anybody
else
wants
to
commit
gregory
to
a
two-hour
three-hour
block
of
time
and
you're
willing
to
like
open
up
the
zoom
room,
we
can
add
it
to
the
schedule.
I
just
don't
want
to
add
too
many,
unless
we
really
have
somebody
committed
to
be
there.
D
G
Okay,
great
thanks
tim
and
thanks
for
putting
together
the
code
sprint,
of
course,
and
and
the
next
one
that's
coming
up
as
well.
So
we'll
talk
about
those
at
the
end
of
the
meeting
all
right.
Let's
do
the
project
update
I'm
going
to
give
a
quick
update
on
117.5
and
focus
most
of
the
time
on
118
today,
117.5
is
the
current
bug
fix
release
that
we're
working
on
it'll,
be
the
next
bug
fix
version
that
comes
out
at
this
point?
G
It's
not
exactly
clear
when
that
will
be.
It
doesn't
have
a
whole
lot
of
fixes
in
it
currently
and
it
might
wait
until
the
release
of
118
and
come
out
in
parallel.
G
Was
gonna
note
that
actually
there
are
seven
issues
that
are
rtbc
in
the
queue
right
now.
That's
awesome,
thanks
for
the
reviewing
the
marking
of
those
things
to
you
to
get
them
in
none
of
them.
Oh,
wait,
wait!
One
of
them
is
one
of
the
ones
that
we've
been
talking
about
regularly
and
that
is
the
field
set.
Css
fixing
some
issues
with
its
display
when
it's
a
collapsible
field
set
in
the
seven
theme,
so
that
issue
4766
has
been
marked
rtbc
thanks.
G
So
much
for
doing
that,
work
really
important
issue
that
we
should
get
sorted
out
is
the
civic
crm
views.
Integration
is
broken
issue
47.45.
This
is
an
issue
related
to
my
sequel,
8
updates.
There
is
a
patch
there
that
has
been
working
and
it
currently
needs
review.
I
think
I'm
a
little
bit
conflicted
as
to
what
to
do
there
right
now
that
we
have
the
choice
to
use
the
patch
or
the
pull
request.
G
That's
in
there
that
a
couple
of
users
have
verified
that
it
works
or
we
could
cross-port
a
different
approach
to
my
sql
8
functionality
from
drupal
7..
So
we
could
basically
kind
of
iterate
on
the
approach
that
we
have
and
use
that
or
we
could
switch
to
the
approach
that
dribble
7
used.
So
two
different
approaches
there
to
to
fix
that
problem.
B
Yeah,
I
would
like
to
add
that
if
you
filter
the
list
by
just
vr
works
for
me
with
these
11
issues,
so
some
of
them
include
those
sorry
there's
11..
So
some
of
these
include
the
seven
issues
that
we
just
mentioned
that
are
rtbc,
but
there's
always
the
just
waiting
for
court
review
and
could
get
in
so
at
least
another
four
or
five
of
them.
G
G
The
milestone
tag
for
117.5
is
generally
kind
of
the
high
priority
bug
like
the
way
that
we
prioritize
like
what
something
needs
to
be
fixed
in
the
near
future
and
overall
in
117.5,
there's
64
open
issues
so
there's
the
seven
rtbc
ones
the
14
need
to
review
ones.
So
yeah
there's
a
good
chunk
of
code
there
that
could
be
moved
forward
with.
G
G
I
left
in
here
also,
probably
I
should
take
out
the
remove
the
the
block
title
for
the
search
box
issued.
34
76
has
been
sitting
there,
for
you
know
several
months
without
a
whole
lot
of
updates.
So
I'm
not
gonna
go
over
that
again,
but
it's
current
statuses
that
needs
work.
G
G
Okay,
all
right:
well,
let's
talk
about
118,
then
118.
We're
coming
right
up
on
feature
freeze
feature
freeze
is
usually
on
the
first
of
the
month
before
the
holiday
we've
yet
to
officially
establish
this,
but
we're
pretty
sure
that
feature
freeze
will
actually
be
january.
4Th
that's
the
first
weekday
after
the
holiday,
so
january,
1st
is
actually
new
year's.
Well,
it's
new
year's
day,
it's
on
a
friday
and
it's
a
holiday,
so
we'll
roll
over
code
freeze
until
monday
january
4th.
So
I'm
going
to
put
that
in
here
so
118
issues.
G
We
have
a
new
issue
that
was
brought
up.
I
think
two
weeks
ago
that
herb
jewel
wanted
to
introduce
a
new
option
for
configure
config
synchronization.
The
issue
number
is
4447.,
provide
an
option
to
skip
deleting
the
config
staging
files
after
a
config
sync
herb
dual
is
the
advocate
for
this
issue.
It
currently
needs
review.
G
We
had
some
back
and
forth
discussion
about
whether
or
not
there
should
be
a
ui
for
this
option,
how
it
should
be
set
where
it
should
be
documented,
but
I
think
we're
closing
in
on
agreements
on
all
of
those
questions.
So
4447
currently
needs
review.
G
It's
a
working
pull
request
that
adds
that
functionality,
it's
useful
for
people
that
are
maintaining
their
config
files
and
version
control
that
right
now,
when
you
run
a
config
sync,
it
empties
out
the
staging
directly
directory
to
be
helpful
for
you,
so
that
further
config
changes
don't
show
up
on
the
synchronization
pages.
G
It
could
either
throw
an
error
because
it
can't
delete
the
files
or
it
causes
a
problem
that
those
files
that
are
managed
in
git
have
now
been
deleted
out
of
their
physical
location.
So
the
git
history,
then,
has
issues
that
need
to
be
resolved
when
you
manage
your
files,
so
that
option
would
make
it
so
that
you
can
sidestep
those
particular
issues,
but
for
normal
users,
normal
users.
G
G
Okay,
next
up
is
exposing
the
file
name
filter
for
the
media,
dialog
issue,
3293
lauren
is
the
advocate
for
that
and
thank
you
for
joining
today.
Lauren.
Could
you
give
us
an
update
on
the
issue.
E
Yeah,
I
think
some
kind
of
power
equipment
just
started
up
outside.
So
hopefully
it's
not
overpowering
me,
but
so
the
the
basic
issue
is.
We
want
to
get
a
filter
into
the
image
library
so
that
you
can
search
on
file
name
and
especially
for
sites
that
have
a
whole
bunch
of
images
to
be
able
to.
You
know,
filter
it
down
to
a
small
subset
and
not
have
to
go
page
page
page
page
and
try
to
look
through
them
all.
E
So
you
can
add
an
exposed
filter
really
easily
in
views.
But
the
issue
is
that
it
seems
to
work
fairly
well
when
you're
doing
it
in
a
file
field.
But
when
you're
doing
it
in
the
ck
editor
modal,
then
it
kind
of
explodes
when
you
try
to
search
and
try
to
use
that
filter.
So
as
near
as
I
can
tell
it's,
because
the
modal,
the
insert
image,
form
pops
up
in
the
modal
and
then
the
view
inserts
the
second
form
inside
that
form.
E
E
We
have
some
movement
in
the
last
week
or
two
from
al
mooj,
not
sure,
if
that's
how
you
pronounce
it,
but
he
discovered
this
sort
of
magical
way
of
making
it
work,
which
is
inserting,
with
javascript
a
click
on
the
pager,
and
I
think
maybe
that
refreshes
the
form
somehow
and
then,
when
you
use
the
filter
it
works.
E
So
it
feels
a
little
clunky
and
hacky
and
magical,
but
it
works
so
I've
kind
of
pieced
together
a
pr
with
his
suggestions
that
he's
pasted
into
the
into
that
issue
and
and
so
there's
a
sandbox
people
can
can
play
with,
and
I
think
the
the
issue
of
you
know
a
brand
new
site
or
a
site
with
very
few
images.
E
E
Page
but
it
is
all
kind
of
you
know,
javascript
slate
of
hand
and
whatnot.
G
Interesting
yeah,
I
don't
know
about
that
idea
to
like
hide
the
filter.
If
there's
only
one
page
like
seems
like
that's
a
little
bit
magicky,
especially
if
that's
not
configurable,
and
it's
not
a
normal
views
option,
you
know
we
don't
do
that
sort
of
thing
anywhere
else
like
if
there's
only
10
nodes,
we
don't
hide
the
search
box
from
the
content
listing
form.
You
know
yeah.
G
I
think
that
those
are
the
sorts
of
things
that
we
should
probably
delegate
to
like
you
can
go
and
customize
the
view.
If
you
want
that
functionality,
the
out-of-box
functionality
should
be
the
clearly
obvious
functionality,
which
is
the
file
name
search
and
then
for
people
that
want
variations
in
the
way
that
their
media
search
functionality
works.
Well,
that's
why
we
have
the
view
that
you
can
go
and
configure
so
yeah.
That's
my
opinion
on
that.
G
But
that's
awesome
that
el
el
much
or
el
muche
has
been
been
doing
that
work.
The
implementation
is
a
little
bit
questionable.
I
think
I'm
gonna
have
to
take
a
little
while
and
look
at
that
and
see
what
kind
of
adjustments
need
to
be
made
there
long
term.
G
I
also
think
that
the
way
that
we
deal
with
dialogues
right
now,
it's
it's
an
efficient
mechanism
where
we're
loading
in
a
part
of
a
page
into
another
part
of
a
page
and
there's
no,
it's
all
it's
all
inline
and
I
think
I
think
that
a
long-term
solution
that
we
might
want
to
look
at
is
using
iframes
for
our
modals
so
that
we
don't
have
those
problems
of
the
stuff
inside
of
the
modal
accidentally
affecting
the
stuff
outside
of
the
modal,
which
is,
I
think,
what
you
were
describing
that
the
the
javascript
is
expecting
to
be
loaded
on
a
page
independently
and
it's
starting
to
affect
the
stuff
around
it
which
it
wasn't
wasn't
built
for.
A
G
Had
several
releases
where
the
media
library
has
been
using
this
same
approach,
which
is
the
same
basic
approaches
like
a
c
tools,
dialogue
in
drupal
7..
So
I
think
we
should
definitely
continue
that
for
the
time
being
get
this
feature
in,
but
then
long
term,
we'll
probably
want
to
figure
out
a
like
a
more
complete
modal
solution
that
that
make
makes
things
a
little
bit
safer.
G
Okay,
thank
you.
Lauren
really
appreciate
your
update.
Next
up
is
adding
a
setting
to
the
menu
block
for
changing
the
break
point
where
the
menu
turns
into
a
hamburger
or
not.
That's
issue.
G
We're
checking
right
now
to
make
sure
that
the
option
works
on
themes
other
than
basis,
and
they
spend
some
review
on
checking
it
against
bartik,
the
other
out
of
box
core
theme,
as
well
as
tatsu,
which,
which
is
the
tim's
version
of
of
basis,
that
is
kind
of
the
enhanced
contrib
version
of
basis
and
we're
working
on
validating
and
adding
test
coverage
for
for
the
display
of
that
option
outside
of
basis.
So
that's
great,
it
looks
like
right
now.
G
This
issue
currently
needs
work,
but
it's
being
very
actively
worked
on
and
seems
to
be
moving
forward,
and
I
think
that
we're
sure
that
the
approach
is
going
to
work
now,
which
is
great,
it's
all
just
working
out
the
the
technical
implementation.
G
D
Yup
well,
it
looks
like
we're
rtbc
again.
I
worked
on
that
at
the
sprint
and
got
feedback.
We
decided
that
we
couldn't
change
the
machine
name
because
of
possible
problems
with
contrib,
so
we
changed
the
the
display
name.
I
tried
to
document
it
nicely
in
code
so
anywhere
where
it's
talking
about
the
display
name,
but
then
has
a
or
the
raw
html,
but
has
a
machine
name
of
full
html.
D
I
tried
to
put
some
documentation
in
the
code
and
we
opened
up
a
follow-up
issue
based
on
the
conversation
from
two
weeks
ago,
which
basically
says
that
if
anybody
is
able
to
do
the
leg,
work
and
sort
of
confirm
that
maybe
this
is
an
overstated
problem
in
contrib
and
or
you
know-
work
with
contrib
authors
to
get
rid
of
the
problem
that
we
could
possibly
do.
We
changed
the
machine
name
before
to
point
backdrop
2.0.
Otherwise
this
would
be
on
the
agenda
for
backdrop.
D
C
Can
I
ask
a
real
quick
question
on
that?
What
are
what's
being
done?
I
guess
from
the
documentation
side
like
on
the
api
area
to
kind
of
say:
hey,
you
know
if
you're
coming
in,
if
you're
new
you're
used
to
full
html,
this
is
going
to
be
changing
to
raw
html
in
the
future.
I
guess
what
are
we
doing
to
prep
people
moving
forward
that
hey
the
machine
name
is
going
to
change
at
some
point
in
the
future.
You
need
to
keep
that
in
mind.
A
Well,
when
it
does
change,
it's
not
going
to
affect
them
at
all
for
existing
sites,
but
for
new
sites.
If
they
had
custom
code,
that
was
doing
it
the
wrong
way.
They
would
need
to
do
it
the
right
way.
C
Yeah,
I'm
just
I'm
trying
to
cover
you
know
somebody
comes
over
that's
new
and
they,
whether
they
port
or
they,
create
a
new
module
for
a
site.
You
know
and
they
use
the
old
machine
name,
which
currently
is
the
case,
but
it's
like
how
do
we
get
in
front
of
them
to
let
them
know
this
is
going
to
change.
So
you
need
to
keep
an
eye
on
this
for
future
releases,
because.
D
Right,
one
of
the
things
we've
decided
is
that
there's
no
real
reason
in
custom
code
for
well
in
triab
to
be
using
machine
names.
So
if
you're
doing
that
you're
doing
it
wrong,
anyways,
there's
there's
never
any
gear
if
you're,
using
a
machine
name
without
checking.
If
it
exists,
that's
a
problem
because
you
can
delete
it
anyways.
D
So
I
think
we're
debating
whether
or
not
there's
any
real
need
to
prepare
developers
for
this,
because
if
there
would
be
no
reason
to
write
a
code,
write
code
for
a
just
or
a
text,
filter
that
doesn't
exist,
and
you
need
to
check
that
first.
C
A
E
C
C
D
They
don't
exist
in
court,
they
they
get
built
during
the
install
profile.
So
all
we're
doing
is
changing
the
defaults
that
are
set
up
in
the
default
profile
and
the
only
reason
again
in
in
contrib
shouldn't
be
referring
to
them.
I
think
we've
decided.
D
D
F
D
I
mean
it's
a
good
question.
We,
you
know,
we
do
want
to
think
about
these
things,
but
I
think
we've
kind
of
thought
that
through
and
just
yeah
there
was
some
talk
about
whether
a
change
record
is.
Is
this
something
that
does
call
for
a
change
record
or
not
yeah.
G
Changing
the
label
doesn't
no,
because
it
doesn't
affect
any
anything,
nothing,
nothing
will
break
and
yeah
it's
it's
just
like
a
ux
change.
It's
like
changing
the
label
of
anything
right
and.
G
Yeah:
okay:
let's
move
on
to.
G
G
G
So
there's
that
also
that
updating
the
tests
might
not
be
so
trivial
if
the
tests
aren't
actually
even
passing
currently,
okay
anyway.
Moving
on
next
item
is
sorry
is
gregory's
issue
merge
all
of
the
updates,
the
various
things
modules,
modules,
themes,
layouts
and
core
update
pages
onto
a
single
page
issues.
2714..
B
Yeah,
so
this
is
really
close,
like
95
done
I'll,
probably
file
a
pull
request
in
a
couple
of
hours,
if
not
less
so,
what's
bothering
me
now
and
I'm
trying,
there
was
a
related
to
the
issue,
I'm
having
issue
bear
with
me
I'll
find
it
anyway.
My
problem
with
this
at
the
moment
is
that
if
you
don't
select
anything
to
be
updated,
like
the
checkboxes
are
blank,
you
get
an
error.
B
So
I'm
trying
to
get
some
javascript
and
states
going
on
so
that
you
get
a
prompt
to
first
select
something
before
you
click
and
then
you
get
the
error.
But
that's
you
know
me
tweaking
things
to
a
point
that
yeah,
but
it's
mostly
working
not
mostly
working.
It's
working
as
expected
from
what
I
saw
on
my
local
and
yeah
I'll
work
on
it
a
little
bit
more
and
should
be
ready.
G
G
That's
great,
so
there
isn't
any
pull
request
yet
to
review
right.
It's!
Okay,
it's
all!
Just
local,
okay!
Well,
that's
great
yeah!
The
screenshots.
Look
good.
You've
been
gathering
some
positive
feedback
in
the
issue.
Queue
as
well.
So
that's
great.
B
Yeah,
the
other
thing
is
that
now
and
I'm
sure
it's
going
to
come
up
like
we
we
sort
of
like,
I
think
we
didn't
decide
but
compromised
that
they
should
go
out
their
configuration
system
updates
and
it
makes
sense.
But
now
we
have
two
pages
that
list
and
also
we
link
to
them
differently
like
from
different
places.
We
have
two
places
where
updates
are
being
listed.
One
allows
you
to
action,
it
like
do
the
updates
and
the
other
one
is
just
a
report.
B
It
kind
of
feels
superfluous,
but
that
could
be
a
follow-up
or
we
can
see
that
like
if
we
could
consolidate
or
because
I
was
looking
at
reports
available,
updates
and
then
settings
should
that
go
in
the
reports
now
or
a
subsection
of
the
updates.
So
we
should
remove
the
section.
The
settings
thing,
anyways
I'll,
add
some
bullet
points
on
what
I
needed.
Sorry
feedback.
Four,
once
I
followed.
G
All
right,
let's
see
next
up,
is
advanced
caching,
support
for
cash
tags
and
the
cash
max
age.
Header
issue
4127
joseph.
Can
you
give
us
an
update.
F
Sure
so
I've
been
working
on
integrating
this
into
core.
I
think
I've
got
most
things
done.
However,
I
am
a
bit
concerned
about.
F
F
Basically
that
the
way
it
works
and
the
way
the
way
it
works
in
drupal
8,
is
that
it's
completely
integrated
and
it's
just
assumed
that
the
cache
system
works
that
way
in
drupal
7,
it's
added
by
a
contrib
module
which
provides
sort
of
like
a
cache
class.
That
is
a
container
around
another
cache
class,
and
so
I've
been
doing
it
the
drupal
8
way,
which
is
completely
integrating
it.
However,
I
think
I've
come
to
the
conclusion
that
that's
probably
not
a
good
idea,
because
it
will
involve
rewriting
any
contrib
cache
modules
to
emulate
the
behavior.
G
An
idea
joseph
for
that,
if
you
take
a
look
at
some
other
cases
where
we
have
some
legacy
code,
and
then
we
want
to
wrap
it
in
some
newer
code
hook.
Block
is
a
great
example.
Where
hook
block
is
super
weird
for
like
config
for
like
it
has
a
switch
on
it
for
like?
Is
it
the
config
form?
Is
it
the
display?
Is
it
the
save
handler
and
we
switched
blocks
from
being
driven
entirely?
G
By
hook,
block
to
you
can
use
hook,
block
info
to
expose
a
block,
but
then
point
it
at
a
class,
and
the
class
contains
different
methods
for
the
form
and
for
the
saving
and
for
the
display
and
all
those
things
and
the
class
version
basically
has
more
capabilities
than
the
hook
based
version.
But
we
have
one
class
called
legacy
block
that
wraps
around
the
old
implementation,
and
we
could
do
that
sort
of
thing
where
the
in-core
cache
handler
could
be
switched
to
could
be
switched
to
something
that
is
updated
and
an
object.
G
So
I
guess
what
I'm
saying
is
that
it
that
could
be
fine
and
we
probably
have
a
way
of
finding
a
way
to
make
that
backwards.
Compatible.
F
G
F
F
G
G
F
G
So
yeah,
okay,
all
right,
let's
see!
Oh,
we
should
also
mention
issue
4509
one
more
time.
Web
piece
support.
Indigo
zella
was
the
advocate
for
that
one.
That
issue
has
been
merged
very
exciting,
so
I
have
a
new
image
format
that
is
supported
in
court
and
an
issue
that
isn't
marked
for
118
yet,
but
doc
welmont
has
picked
it
back
up
again
and
is
moving
it
forward.
G
Is
the
concept
of
relationships
within
layouts
so
that
you
could
start
with
something
like
a
node
and
then
form
a
relationship
to
a
user,
for
example
and
start
pulling
or
formal
relationship
to
the
note's
author?
And
then
you
could
start
pulling
fields
off
of
the
author
to
place
them
into
the
layouts.
The
issue
is
2134..
G
Pull
request
is
not
quite
ready
for
review
yet,
but
it's
there's
some
new
activity
there
and
user
interface
and
screenshots,
and
things
like
that.
So
that
issue
would
be
good
to
start
collecting
feedback
on
it
as
stockholm
one
progresses
there
and
that
does
it
for
the
118
list.
Do
you
guys
have
anything
else?
You
guys
would
like
to
bring
up
for
118.
C
I'm
just
curious
if
jen
wants
to
try
and
push
forward
on
the
field,
visibility
for
118
or
if
we
want
to
try
and
kind
of
push
that
back
for
a
later
release.
A
Yeah,
so
that
this
is
an
interesting
problem
where,
if
you're,
creating
a
layout
or
a
block-
and
you
want
it
to
only
show
if
you're
on
a,
for
example,
a
node
where
a
field
has
a
specific
value,
c
tools
used
to
provide
a
access,
callback
or
access
plugin.
That
would
check
for
that
and
when
we
ported
all
this
util
stuff
to
backdrop,
this
was
one
of
the
things
that
got
left
out.
A
There's
a
handful
of
visibility,
rules
that
just
didn't
make
it
in,
like
the
user,
compare
one
and
then
taxonomy
term
vocabulary,
one
there's
like
a
bunch
of
stuff,
and
this
one
I
think
and
duck
walnut-
has
a
contrib
module
for
because
it's
fairly
common
or
some
of
the
other
ones
don't
exist
at
all,
except
it's
like
core
patches.
But
this
one,
I
think,
is
one
that,
even
though
maybe
not
eighty
percent
of
current
backdrop
sites
have
needed
it.
A
It's
the
kind
of
thing
that,
if
it
were
there,
I
think
it
will
be
used
a
lot
where
people
look
in
those
visibility
rules
and
they
don't
see
very
many
options,
and
so
they,
you
know,
find
other
ways
to
do
things.
And
so
I
started
porting
the
c
tools
plugin
before
I
realized
that
duckling
had
already
written
stock
moment
or
herb.
E
A
Already
written
a
kindred
module
for
it,
and
so
I
think
like
if
we
take
his
implementation
and
put
it
into
my
core
pull
request
that
could
be
pretty
close
to
being
ready.
So
I
don't
know
I'm
using
it
on
a
site
right
now.
I'm
motivated
to
fix
it
right
now.
The
site
is
gonna,
launch
or
be
done
around
january
6.
So
the
timing
is
perfect
to
make
that
get
a
push
for
118.,
but
I
wanted
to
gauge
other
people's
interest
in
it.
A
I
think
I'm
the
one
that
added
the
milestone
candidate
label,
so
it's
gonna
need
agreement.
C
I
personally,
like
the
idea
of
it
being
in
gore,
considering
everything
else
that
has
been
pulled
into
backdrop
between
c
c
tools
and
panels.
That
was
part
of
like
you
said
it
was
part
of
c
tools,
and
I
agree,
probably
80
of
the
folks
that
are
out
there
won't
ever
use
it
or
don't
need
it
for
a
site.
C
When
you
do
need
it,
it
is
you
you've
got
to
have
it,
I
mean
it's
just
hands
down.
You've
got
to
have
that
type
of
functionality,
so
I
do
like
the
idea
of
it
being
pulled
in
core
what
doc
has
doing
some
testing?
The
only
piece
that
I
have
found
so
far
that
does
not
work
is
the
null
empty
values
and
there
is
a
patch
out
there.
C
That's
been
floating
since
c
tools
could
grief
like
112
or
110
that
I've
been
following
for
about
the
last
five
or
six
years,
and
every
single
time
c
tools
gets
updated.
I've
got
to
go
re-patch
that
thing,
because
it
still
has
not
been
incorporated
in
core
c
tools.
Just
haven't
been
patched
yet
so
that
I
think
the
majority
of
the
work
is
done.
C
The
only
piece
that's
missing
is
like
dealing
with
images
or
multi-value
fields,
and
I
feel
like
guys-
let's
just
get
this
in
c
tools-
let's
create
another
patch
over
there
for
multi-value
fields.
C
So
there's
there's
a
few
issues
with
the
patch
that's
sitting
out
there
to
deal
with
the
empty
value
empty
null
value
fields,
but
some
of
those
can
be
taken
care
of
outside
of
what's
already
there.
It
works
for
probably
90
of
the
use
case.
What
we
need
it
for.
So
I
guess
my
question
is:
do
we
want
to
go
ahead
and
continue
to
develop
that
in
the
contrib?
For
now,
until
we
feel
like
it's
working
and
then
start
to
pull
all
that
into
core?
C
A
Well,
I
think
what
might
make
more
use
as
a
contrib
solution
is
one
module.
That's
a
collection
of
all
of
the
filters
that
are
missing
that
were
in
c
tools,
but
I
think,
having
an
individual
mantra
for
each
one
is
gonna,
maybe
not
be
the
best.
But
I
don't
know
if
that
was
his
plan
is
to
move
all
the
ones
from
c
tools
there.
This
one
is
just
specifically
for
this
field,
but
this
one
I
feel
like
is
it
sort
of
feels
like
an
obvious
omission
when
you're
playing
with
the
drop
down.
A
Isn't
there
a
field,
this
value
option
in
here
where
some
of
the
other
ones
like
user,
compare?
I
use
that
all
the
time
when
I'm
building
profile
pages
for
people
and
everyone's
like,
I
don't
understand
how
this
works
so
I'm
like
well,
you
have
to
have
this
use
case
where
people
are
looking
at
the
profile
pages
and,
if
nobody's
looking
at
profile
pages
on
your
site,
which
is
almost
backed
websites,
you
don't
need
it
and
so
that's
much
harder
to
even
explain
what
it
does
where
this
one.
B
Yeah,
so
my
main
issue,
besides
the
the
fact
that
I
find
the
functionality
well
compared
to
the
code
chains
useful,
is
that
we
claim
that
certain
modules
have
been
merged
into
core
and
we
are
working
on
the
as
part
of
the
outreach
initiative
to
to
get
the
upgrade
status
module
going
and
we.
What
are
we
going
to
be
telling
people
that
use
c
tools?
Is
it
ready
and
in
core
out
of
this?
B
So
because
we
keep
saying
that
yeah
c
tools
in
core?
We
should
like
obvious
submissions,
as
you
said
then,
like
that
should
be
there.
That's
that's
my
problem
with
being
against.
You
know,
keeping
it
in
contributing
against
having
it
in
court.
That's
my
main
problem
same
with
certain
things
that
the
date
module
used
to
do,
and
it's
not.
C
I
think
there's
some
good
points
in
there.
I
hate
to
upset
doc
because
nobody
wants
to
upset
anybody,
but
I
think
how
how
do
we
let
him
down
easy
that
hey
we're
going
to
go
ahead
and
get
this
moved
over
into
core,
even
though
you're
not
a
real
big
fan
of
that.
A
I
mean,
I
think
we
can
just
push
forward
on
it
and
see
what
he
thinks
you
know
I
think
going
forward
if
we're
like
here
it
is,
you
might
be
like
okay,.
G
There's
also
a
lot
of
precedent
for
putting
some
functionality
in
core,
but
then
leaving
the
remaining
things
like
contrib
is
like
an
enhancer
on
the
things
that
get
into
core,
or
sometimes
even
a
replacement.
So
just
if,
if
you
were
using
the
contrib
module,
having
the
contrib
module
in
place
like
takes
precedence
over
the
core
implementation
of
some
things,.
A
G
Oh
no,
I
was
saying
for
doc
well
months,
conditional
fields,
module.
I
thought
that's
what
what
phil
was
referring.
A
G
A
Not
conditional
fields
as
in
field
api,
as
in
layout
access
plug-in,
so
it
came
from
sequels
and
that's
missing
before
so.
There
could
so
that's
kind
of
where
I
was
going
with
like
one
contrib
module
that
adds
back
all
the
missing
functionality,
where
I
think
that
would
make
sense
where
it's
like.
Okay,
we
did
this
with
date,
where
we
left
date
repeat
in
kintrip,
where
it's
like.
A
This
is
obviously
not
going
in
core
because
it's
not
80
use
case,
so
here's
a
module
for
it,
but
I
think
in
this
case
we
didn't
do
that
there
wasn't
ever
the
decision
that
was
like
we're.
Definitely
not
putting
these
things
in
core.
I
think
it
was
like,
let's
just
get
a
minimum
viable
product
in
and
we
never
returned
to
all
the
list
of
you
know:
100
features
that
tools
includes
and
so
as
we're
now
using
it
we're
coming
across
them
going.
A
Oh
here's,
the
thing
we
forgot
and
I
think
that
if
we
wanted
to
make
a
concerted
effort
to
be
like
here's
all
the
stuff,
that's
in
c-tools-
that's
not
in
backdrop
and
have
that
line
and
be
like
eighty
percent
use
case
goes
in
other
things.
Jason
can
trip.
That
would
make
sense,
but
I
don't
want
every
missing
feature
from
c
tools
to
get
its
own
contrib
module
and
be
sort
of
piecemeal
added
as
people
run
into
problems.
So
I
feel
like
that's
going
to
create
a
lot
of
frustration
where
it's
like.
A
I
thought
it
was
in
core
here's
a
kindred
module.
Oh,
I
thought
this
was
in
chlorine.
Here's
a
kingdom
module
where
there
there
isn't
sort
of
the
up
front,
like
you
know,
easy
split,
like
date
and
date
repeat,
had.
C
Something
else
to
think
about
with
the
the
field.
Visibility
is
you
kind
of
mentioned
the
ux
right
now
with
the
contrib
that
the
doc
has
out
there
and
he
and.
A
C
Of
discussed
that,
but
it
hasn't
gone
anywhere
yet
right
now
it
literally
vomits
every
single
field
in
the
entire
system
on
you,
and
so
we
need
to
be
able
to
come
in
and
basically
do
some
filtration.
That
says:
hey
we're!
Looking
at
this
node.
A
Right
sort
of
limiting,
where
it
asks
you,
what
entity,
what
bundle
and
only.
A
Available
for
those,
so
I
think
that
if
we
take
all
of
the
work
that
he's
done
in
terms
of
like
you
know,
the
access
checking,
which
is
really
the
harder
part
and
just
put
it
inside
my
like
selecting
the
plug-in
thing
we
can
get
both
of
those.
E
D
C
G
A
G
G
Okay,
let's
see
we're
running
short
on
time
here,
we'll
move
on
to
initiatives.
G
I
think
you
guys
are
talking
about
ready
to
wear
a
lot
during
the
prior
meeting,
so
we
won't
cover
that
one
again
but
telemetry.
We
haven't
gotten
an
update
on
that
this
week.
Tim
do
you
have
any
thing
to
report.
D
G
D
I'd
just
like
to
make
kind
of
an
announcement
and
or
take
some
quick
feedback
based
on
some
conversations
in
the
last
meeting,
I'm
suggesting
and
went
ahead
and
posted
a
forum
post
with
a
prospective
date
that
we
do
a
virtual
user
group
on
dang
it
where's
the
date
the
I
went
and
changed
the
screen
anyways
the
first
tuesday
of
january.
D
That
is
a
lightning
talk
on
contrib
modules
and
the
goal
is
basically
to
have
people
do
short,
five
to
ten
minute
presentations
on
contrib
modules
that
we
can
record
individually
and
list
on
youtube
and
just
generate
a
better
library,
and
I
suggested
highlighting
under-appreciated
modules
and
I've
already
gotten
some
pushback
on
what
that
means.
So
I'll
leave
it
up
I'll
leave
it
up
to
every
individual
to
decide
what
is
under
appreciated.
D
G
Speaking
of
scheduling
things
a
week
from
today
is
christmas
eve,
it's
a
holiday
for
a
lot
of
people,
kind
of
similar
to
thanksgiving,
though
in
these
times
of
pandemic
and
people
being
at
home
and
not
having
other
events
to
attend.
We'll
almost
certainly
be
doing
the
backdrop
meeting
again
next
week,
despite
the
holiday,
so
we
will
be
having
that
week
from
today.
At
the
usual
time,.
B
I
have
a
question
like
a
quick
one.
The
first
of
jan
falls
on
a
friday
and
that's
usually
when
we
have
the
feature
freeze.
Are
we
going
to
extend
it
to
the
next
monday.
D
I
think
nate
mentioned
that
before,
but
that
leaves
two
just
two
weekly
meetings
right
before
next
week
and
then
there'll
be
one
more
before
future.
Freeze.