►
From YouTube: 2021/12/16 Backdrop Weekly
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,
it
is
december
16th
2021.
This
is
the
backdrop
weekly
developer
call.
We
get
together
every
week
to
talk
about
priorities
and
tasks
for
backdrop
core
and
beyond.
We'll
do
some
quick
introductions.
My
name
is
nate
lampton,
I'm
quick
sketch
on
the
internet
based
in
oakland,
california,
and
we'll
go
to
joseph
and
then
robert.
A
Great
thanks
joseph
robert
and
then
greg.
A
That
was
great
greg
and
then
jen.
D
I
am
greg
I'm
joining
from
greece
generally
interested
in
anything
that
has
to
do
with
backdrop
in
any
way
that
I
can
help
excited
about
the
upcoming
release,
so
yep.
D
F
I'm
jen
lampton,
I'm
joining
from
oakland
california
and
I
just
want
to
say
I'm
so
excited
about
all
of
the
activity
that's
been
going
on
in
the
issue
here
lately
I
haven't
read
all
of
the
issues
or
all
of
the
emails,
but
I've
seen
them
all
come
in
and
I'm
really
excited
to
get
caught
back
up
on
all
the
fantastic
work
everyone
is
doing.
So.
Thank
you,
everybody
for
all
your
time.
That's.
H
F
Sure
so
this
week
we
have
one
new
application
to
join
kentrip.
I'm
actually
not
sure
it
looks
like
it
came
in
a
week
ago
today.
So
I
don't
know
if
that
was
before
after
the
meeting
or
if
you
guys
talked
about
it.
But
there
is
a
new
module
called
s3fs
which
looks
like
it
was
previously
a
drupal
module
in
a
sample
imported
to
backdrop.
A
Superior
all
right,
thanks
jen
for
the
between
the
update
there
and
welcome
to
our
new
contrib
members.
A
A
She
has
a
question
about
how
to
deal
with
the
distribution
of
jquery
ui
versus,
what's
in
core
versus
what
is
distributed
by
the
jquery
project
and
there's
a
big,
maybe
not
big,
but
a
small
problem
in
that
jquery
has
restructured
their
distribution
that
they
deliver
as
a
package
a
couple
of
times
actually
in
the
in
the
lifetime
of
jquery
ui,
and
it
differs
from
what
drupal
7
originally
had
included
in
core,
and
then
we've
carried
that
forward
that
now
jquery
ui
is
always
just
delivered
as
one
giant
bundle
of
functionality
and
backdrop
core
includes
every
individual
component
separately
as
needed,
and
so
indigozella's
point
here
is
that
there's
no
easy
way
to
get
the
files
into
the
current
structure
and
the
answer
to
that
question
I
believe
is
that
is
correct.
A
There
is
no
easy
way
to
take
the
current
files
and
get
them
into
the
current
structure.
I
think
last
time
we
did
this.
We
took
all
of
the
files
from
the
source
code,
renamed
them
all
to
match
the
current
file
file
patterns,
and
then
we
also
compressed
them
using
uglify.
I
think,
and
so
I
think
that's
the
same
thing
that
we'll
need
to
go
through
for
this
release
as
well
for
better
worst
jquery
ui
doesn't
update
very
often,
and
so
we
haven't
run
into
this
very
frequently.
A
D
A
Yeah,
I
think
that's
a
great
idea.
Yeah
the
ck
editor
process
is
also
it's
not
it's
not
too
bad.
It's
actually
even
gotten
better.
A
But
yeah,
I
agree
that
that
would
be
good
to
to
document
exactly
how
this
whole
process
works.
Maybe.
D
We
can
do
it
as
part
of
that
issue
that
raised,
because
it's
a
different
issue,
we'll
just
upgrade
with
it
I'll
do
that.
A
A
Okay,
pretty
sure
it
was
me
I
apologize
for
passed
me.
Okay,
let's
see
greg
opened
up
issue
5398
this
week
for
php
8.1
support.
A
A
D
Well,
if
people
are
testing
things
that
are
not
production
like
on
the
environments
and
they
they
can
easily
switch
php
versions.
It
might
be
a
good
idea
if
they
switched
to
like,
for
example,
I
use
my
local,
my
local
test
environments,
all
use
php
7.4
by
default,
but
I'm
going
to
switch
it
so
at
least
some
of
them
to
8.1.
So
we
can
surface
the
issues
and
then
maybe
address
it.
So
I
switched
that
issue
to
be
a
meta
issue,
although
it
has
the
pull
request.
D
So
if
you
come
up
with
any
issues,
yeah,
basically
just
soliciting
help
from
others
in
reporting
issues
with
php
8.1,
and
if
you
know
how
to
to
contribute,
then
either
use
my
pull
request
or
file
things
pull
requests
again.
My
against
my
brands
just
help
in
any
way
that
I
can
great.
A
Yeah
and
and
kind
of
like
what
happened
with
php
eight
well.
First
of
all,
we
have
an
advantage
that
now
we're
on
github
actions.
I
think
we
can
jump
to
php
8.1
really
pretty
easily.
Just
by
updating
the
yaml
file.
I
haven't
checked
to
make
sure
that
they're
compatible
with
php
8.1
yet,
but
I
see
that
lando
for
local
development
added
php
one
8.1
support
two
weeks
ago.
D
D
A
Yeah
so
doing
it
locally,
lando
is
a
good,
is
a
good
bet
and
then,
when,
finally,
the
pull
requests,
we
can
add
in
the
new
8.1
just
replace
8.0
from
the
from
the
testing
matrix
in
the
github
actions
file.
A
Okay,
let's
see
those
are
kind
of
the
only
items
that
were
brought
up
specifically.
F
A
Been
a
lot
of
activity
in
the
issue
cube
recently
yeah,
so
there's
like
a
lot
to
choose
from
as
far
as
like
areas
that
probably
need
some
attention
go
ahead.
Greg.
D
Maybe
now
it's
a
good
opportunity
to
also
mention
something
that
was
decided
by
the
pnc
last
week
and
we
announced
it
which
is
related
to
that.
So
up
until
now
backdrop
was
supporting
officially
supporting
php
version,
5.3
a
specific
version
and
above
and
the
decision
is
made
that
after
the
next,
the
the
next
minor
release
after
the
next
minor
release.
So
two
releases
minor
releases
from
now
will
drop
support
for
any
php
version
before
php
5.6.
D
So
5.6
will
be
basically
the
the
the
only
php
5
version
that
we
support.
Officially,
that
goes
to
say
that
we
will
try
to
not
intentionally
break
things,
but
we
might
so.
A
Yeah,
I
wonder
if
that
that
needs
to
be
clarified
more,
that
you
know
backdrop
has
a
constant
that
says
its
minimum
php
version,
and
it
will
refuse
to
do
absolutely
anything
if
that
constant
variable
is
like
not
met,
and
so,
if
we're
dropping
support
for
5.6.
Does
that
mean
that
we
update
that
constant
and
therefore
just
like
completely
bail
out
of
any
trying
to
do
anything?
If,
if
the
php
version
is
too
old,.
H
That
my
break
team,
you
muted
we're
supporting
5.6,
not
prior
to
that
and
greg
last
week
you
brought
up
or
we
would
make
an
effort
to
keep
it
available.
But
my
understanding
from
from
other
people
was
that
there
are
things
we
want
to
implement,
which
will
break
older
versions.
Okay,
so
we
should
not
mislead
people
into
thinking.
H
So
you
know.
Basically
I
said
that
in
the
in
the
blog
post,
the
blog
post
says
after
five
or
after
may
15th.
You
know
we
will
be
probably
adding
things
that
will
break
old
sites,
so
people.
A
I
think
I
said
mention
this
that
as
soon
as
we
take
out
php
5.3
from
the
testing
matrix
test
failures
will
happen,
because,
if
we're
not
testing
it,
then
it's
inevitable.
That
failures
will
occur
and
we
won't
know
about
it.
So,
unless
we're
going
to
keep
testing
php
5.3.
D
A
Yeah,
I
wonder
quite
what
we
can
do
about
that,
because
we
can't
update
any
existing
sites
that
haven't
been
updated
yet,
but
we
could
add
in
something
into
the
1.21
release
cycle
so
that
at
least
then
there's
like
a
couple
months.
If,
if
they're
a
keeping
their
backdrop
site
up
to
date,
while
b
not
updating
their
php
servers,
which
is
an
a
kind
of
unlikely
combination
but
but
possible.
D
I
have
an
issue
open
for
adding
warnings
about
php.
Maybe
I'm
not
sure
if
it
was
closed
rejected
at
that
point.
Maybe
it's
worth
reopening
that
so
that
it
can
trigger
errors
in
the
status
report
for
people
that
are
running
older
versions.
A
Yeah,
that's
a
that's
a
good
idea
and
I
wonder,
like
you
know,
we
could
decide
on
how
aggressive
we
want
to
get
with
that
that
you
know
we
could
start
giving
people
warnings
if
they're
running
unsupported
by
the
php
community
php
versions,
possibly,
but
there
is
kind
of
a
big
a
little.
Well,
I'm
not
sure
if
it's
a
big
bird
in
there,
but
there
is
a
burden
there
that
a
lot
of
operating
systems
upgrading
your
php
version
can
be
pretty
difficult.
A
F
F
A
D
Yeah
we
can
decide
if
it
is
a
warning
or
an
error,
but
it
seems
like
an
error
is
more
and
I
think
that
we've
nate.
I
think
this
was
one
of
your
suggestions.
Did
we
suppress
the
error
messages
from
the
rest
of
the
site
and
just
kept
the?
I
think
that
we
merged
that
change.
That
now
doesn't
bug
people
about
errors
in
every
page.
It
just
has
the
notification
icon
right.
E
B
F
A
That
removes
it
from
other
pages,
but
what
were
you
thinking
about?
Bringing
that
up,
you're
saying
that?
Do
you
think
that
that
would
be
good
or
bad
in
this
situation?
Yeah.
D
Because
olaf
mentioned
that
you
know
there's
legitimate
versions.
Maybe
we
can
do
both
things
now,
because
we
were
discussing
both
of
these
things
in
the
past,
a
to
warn
about
php,
outdated
php
versions
and
b,
stop
bugging
in
every
single
bugging
site
administrators
in
every
single
page
right.
So
we
could
now
make
it
a
an
error
for
php
versions,
have
the
little
notification
icon
in
the
indicator
in
the
admin
bar
and
then,
if
we
hide
it
from
everywhere
on
the
side.
Besides,
I
don't
know
status
fades,
then
that
could
be
a
compromise.
I
don't
know.
F
A
Yeah,
oh
and
there's
also
this
weird
performance
thing
that
happens
because
if
you're
checking
the
update
status
like
the
status
report
on
every
single
page
load,
then
that
also
has
like
a
performance
impact
that
it's
like
doing.
That
is
also
like
an
expensive
operation
so
and.
D
Also
yeah
and
also
status
messages
get
cast
sometimes
so,
even
if
you
fix
it,
it's
still
there
or
yeah.
G
Yeah,
coming
back
to
the
status
of
the
messages,
so
I
think
before
the
release
when
we
switch
or
when
we
drop
the
support,
we
it
shouldn't,
be
an
error,
but
just
a
warning,
because
until
then
it's
working.
So
it's
not
an
error.
A
In
in
the
case
of
dropping
php
support
for
5.6
or
below
5.6,
I
think
an
error
is
important
that
we
flag
it
as
like.
You
need
to
fix
this
right
now,
because,
if
we're
only
giving
them
three
months
to
upgrade
their
php
version,
they
need
to
get
off
of
it
immediately.
A
F
A
Working
if
you're
running
an
old
version
of
php,
I
think
we
need
to
do
an
error
for
this
round.
If
we
have
like
less
aggressive
cutoff
dates,
a
warning,
I
think,
would
have
been
sufficient,
but
this
is.
This
is
really
important
that
they
fix
it
as
soon
as
possible.
A
I
mean
if
we
wanted,
this
is
kind
of
a
I'm,
not
sure
if
it's,
even
if
it's
underhanded,
but
because
there's
no
way
for
us
to
flag
an
error
on
people's
sites,
we
could
make
a
security
release
that
does
nothing
except
for
says:
hey.
The
php
version
has
been
increased
because
really
this
is
a
security
issue
and
then,
when
they
upgraded
to
the
new
version
to
make
the
security
error
go
away,
they
would
get
another
error.
That
says
you
need
to
upgrade
your
php
version.
A
That
would
be
a
way
to
like
force
an
error
onto
people's
sites,
but
I
I'm
not
sure
that
that
just
seems
like
that's
a
cumbersome
way
to
proceed.
We
have
the
news
block
and
we
can
definitely
use
that.
We
have
the
great
blog
post
that
tim
drafted.
I
think
the
news
block,
plus
the
blog
post
is
and
tweeting
all
of
those
things
should
probably
be
sufficient.
H
D
I
have
something
related
to
securities
security
releases,
though
so
we,
I
know
that
we,
we
are
adding
sa
no
nodes
in
b.org
for
core
releases,
but
we're
meant
to
be
doing
that
for
contrib
as
well,
right
and
because
country
bothers
do
not
have
access
unless
they
are
part
of
that.
The
team
that
manages
the
the
board.
D
I
think
that
we're
missing
some
contribution.
I
will
need
help
of
the
contrib
there's.
F
There's
no
way
for
a
contrib
release
to
be
a
security
release
without
the
involvement
of
the
security
team,
because
they
have
to
go
into
backdrop
and
cmso
are
going
to
open
this.
F
So
when
that
happens,
that
person
will
also
draft
a
security
advisory
and
hopefully,
with
the
help
of
the
person
who's.
Creating
the
release
they'll
be
like
here
give
me
here's
the
template
for
an
advisory.
Please
tell
me
what
to
put
in
there
and
then
they'll
write
the
advisory
and
we
can
just
post
it.
D
The
reason
why
I'm
mentioning
this
is
because
there
was
a
security
release
of
the
search
api
page
module
recently,
which
was
the
the
maintainer
did,
create
the
release.
I
I
poked
them,
they
create
the
race
and
I
might
deflect
it
as
a
security
release,
but
then
I
needed
to
create
that
node
and
I
realized
that
I
would
need
to
start
incrementing
it
as
a
contrib001.
F
Yeah,
there's
probably
a
handful.
We
should
make
a
list,
though,
because
just
because
there
should
be
doesn't
mean
there
isn't,
but
we
can
definitely
go
back
and
create
the
security
advisories.
Now,
probably,
what
we
should
do
is
set
them
to
all
publish
at
the
same
time,
so
that
when
people
get,
they
won't
get
like
a
bunch
of
emails,
so
it
should
be
like
we're
getting
caught
up.
Here's
eight
and
everyone
will
because
everyone
will
get
an
email
when
that
goes
out
yep.
D
I,
if
someone
compa,
helps
me
compile
the
list
of
the
past
contrib
modules
that
had
releases
and
make
sure
how
back
we
have
been
missing
like
is
it
this
year?
Only
or
does
it
go
back
to
last
year.
F
Yeah,
okay,
I
think
there's
probably
a
way
we
can
just
build
a
view
to
check
which
releases
or
security
releases
and
then
I'll
play
with
that
on
my
local
site
and
see
if
we
can
get
that
working
and
then
that
might
be
something
that
we
just
have
on
the
live
site
that
we
can
check
periodically
and
make
sure
that
we
have
all
of
the
security
advisories
up.
D
A
All
right,
let's
see,
we've
got
about
20
minutes,
let's
run
through
the
the
1.21
milestone.
If
there's
nothing
else,
so
wonder,
21
is
the
next
minor
release
of
backdrop
feature
freezes
on
well,
it's
normally
on
the
first
of
the
month
prior
to
the
release,
so
it
comes
out
january.
15Th
feature
freeze,
therefore,
would
be
january.
1St
january
1st
is
a
saturday
per
current
policies.
A
We'd
like
push
that
to
the
end
of
any
holiday
weekend,
so
virtue
freeze
is
january,
2nd
2022.,
I
believe,
that's
correct,
because
I
think
new
year's
day
is
being
observed
on
the
31st
as
the
holiday
that
may
vary
by
country.
Of
course.
A
So
I'm
curious
to
hear
if
there's
any
other
countries
that
have
their
holiday
on
the
third
instead
of
the
31st,
we
can
kind
of
make
a
decision
there
about
what
day
feature.
Freeze
really
is
I'm
not
sure
that
we've
had
this
particular
thing
happen
before.
A
H
H
A
Okay,
that
sounds
wonderful.
Let's
see,
we
currently
have
10
open
issues
for
1.21
first,
one
in
the
list
actually
yeah,
we'll
start
from
the
top
enable
telemetry
module
on
new
installs
in
1.21.
A
H
H
Oh,
we,
the
the
the
php
thing,
became
the
priority
last
week,
we'll
try
and
make
this
a
priority
this
week
see
if
we
can't
come
to
any
kind
of
decision
quickly,
because
I
don't
think
we
can
move
on
well,
we
could
add
more.
We
could
add
more
features
to
the
telemetry
right
without
turning
the
module
on,
but
to
turn
the
module
on
we'll
need
a
pmc
action
right.
A
Yep
yeah
yeah,
there's
still
lots
of
things
to
to
potentially
be
added.
I
think
web
server
was
one
item
that
specifically
was
raised,
as
we
should
be
tracking
that
I
think
officially
we
only
support
apache,
which
is
a
little
bit
interesting.
Considering
like
backdrop,
cms.org
itself
runs
in
genex
right,
so
there's
a
little
bit
of
fuzzy
requirements
there
and
it
would
be
good
to
start
collecting
that
information.
A
Okay,
next
up,
we've
got
pull
request.
Add
display
settings
for
book
navigation.
I
believe
jen
is
the
advocate.
You
open
the
issue
jen,
but
it
doesn't
say
that
you're
the
advocate,
but
I
think
this
issue
is
really
straightforward,
that
it
just
adds
this
the
the
book
navigation
previous
next
and
go
to
parent
as
a
display
setting
option
like
using
hook
field
extra
fields
right,
so
you
can
move
it
up
and
down
or
turn
it
off.
Is
that
right.
F
A
Oh,
I
see
and
her
boson
actually
filed
it.
Oh
looks
like
he
just
made.
He
made
it.
He
just
made
it
configuration
settings
for
book
module,
so
book
module
has
a
settings
page
and
he
just
made
settings
on
that
form.
For
would
you
like
to
display
this,
the
navigation
or
not?
A
A
Okay,
the
current
state
of
it
is
that
has
a
pull
request
that
needs
needs
review.
A
H
No,
we
actually
I'll
share
my
spring
real
quick.
We
did
so.
We
had
a
problem
last
week
with
a
with
the
pr
excuse
me,
but
thanks
to
dr
mount,
we
fixed
that.
So
this
is
the
current
pr.
Although
it's
been
modified
by
olaf,
that
in
testing,
so
it
looks
a
little
different.
The
images
themselves
are
our
plan
to
change.
I
think
olaf
has
offered
to
maybe
help
us
pick,
some
better
images
out,
but
the
the
current
pr,
basically,
what
it
does
is,
adds
three
cops:
three
three
cards
with
images.
H
All
of
this
one
of
the
things
I
think
he
was
doing
with
this
example
was
pointing
out
how
easy
it
is
sort
of
break
the
layout.
Whether
or
not
that's
an
issue
or
not,
and
the
other
thing
this
pr
does
well,
it
adds
a
new
content
type
called
parts
which
is
a
hidden
path,
content
type,
and
then
it
adds
this
view
on
the
front
page.
It
also
modifies
the
text
a
little
bit
so
the
text,
all
of
this
text
is
supposed
to
be
explanatory.
H
The
node,
that's
actually
in
the
pr,
is
more
explaining
about
cards
and
stuff,
and
basically,
at
this
stage
I
think
we're
just
looking
for
well,
we
need
new
images,
but
olaf
has
suggested
just
doing
one
card
instead
of
three
there's
a
few
different
ideas
out
there,
but
I
think
the
biggest
thing
we
need
feedback
is
on
the
text
itself
and
and
sort
of
the
overall
layout.
There
is
a
blocker
to
this.
H
I
believe
it's
a
blocker
in
that
these
are
supposed
to
be
hidden
path,
content,
but
the
the
links
excuse
me
the
links
work
and
for
a
regular
user.
They
would
take
you
to
a
page
not
found,
and
we
want.
We
want
backdrop
to
not
make
those
links
if
it's
a
didn't
path,
content
type,
that's
the
summary
any!
A
F
H
A
H
G
F
Iffy
because
we
have
to
make
it
change
to
the
node
template,
because
the
link
is
hard
coded
in
the
template.
It's
not
like
pre-processed
or
added
in
any
way
that's
easy
to
alter,
but
that
is
sort
of
a
bigger
issue
in
general.
So
we
should
never
link
a
node
title
to
a
node
that
is
going
to
provide
a
access
to
knight
or
403
or
whatever,
when
someone
clicks
on
it.
So
I
don't
think
it
should
block
this,
but
I
just
figured
I
mentioned
that.
H
F
The
broader
issue
will
fix
it
for
this
use
case
too,
but
that's
just
any
any
node
title
for
whatever
and
there
I
don't
know
that.
There's
a
dedicated
issue
for
this
use
case.
Okay,
I
think
oh.
H
F
Or
I
mean
there's,
there's
others
like
we
could
ship
core
with
a
template
that
overrides
this
node
type.
For
this
view
mode
or
all
view
modes
or,
however,
we
would
need
to
put
some
solution
into
the
current
pull
request,
but
it
doesn't
have
to
be
the
absolutely
yeah.
A
F
F
A
Yeah,
but
it
does
help
with
the
image
style
problem
that
olaf
mentioned,
that
we're
using
the
same
image
style
for
both
the
full
and
the
card
which
honestly
making
a
display
mode
for
card
is
again
one
of
the
most
common
use
cases.
So
it
might
not
be
a
bad
idea
to.
F
A
F
H
Big
yeah
I'd
like
to
quickly
raise
that
we
all
seem
to
be
settling
on
the
word
card,
although
there
are
still
a
few
people
who
have
sort
of
objected
to
that,
but
I
just
don't
think
we
have
a
better
solution
and
yeah.
H
You
know
the
main
objections
is
that
there's
a
sort
of
an
idea
of
what
a
card
is
out
there
and
that
this
might
not
be
it,
but
I
think
I
don't
know
in
a
way
this
to
me.
This
is
kind
of
what
a
card
is,
although
this
content
type
can
be
used
for
other
things
as
well.
So
you
know
some.
You
could
argue
that
it's
too
specific,
but
I'm
not
too
worried
about
that.
A
It
wouldn't
be
a
pageless
node
yeah,
it
would
be,
it
would
be
different,
it
would
be
cards
the
posts
yeah,
but
yeah.
There's
there's
this
this.
This
is
what
it
comes
down
to
and
it's
like
you
know.
If
we're
trying
to
ship
stuff
out
of
the
box,
it
has
to
be
opinionated
in
some
way
and
it
won't
be
the.
G
Yeah,
I
think
it's
not
the
most
accurate
term,
but
what
I
like
is
pretty
short
and
so
very
similar
to
page
and
post.
So
that's
really.
Nice.
G
So
maybe
I
don't
know
if
you
have
the
time,
but
I
brought
up
an
issue
which
I
have
with
the
current
approach
that
I'm
not
sure
if
it's
robust
enough,
so
I'm
thinking
it's
very
easy
to
break
unintentionally
and
also
if
people
want
to
adapt
it.
It's
not
so
easy.
G
But
I
was
I
would
like
to
get
feedback
if
it's
possible
now
or
in
the
issue,
queue
about,
if
it's
not
better,
to
choose
a
more
simple
approach
which
is
not
looking
so
nice,
but
also
nice,
in
my
opinion,
for
example,
with
the
gray
background
and
one
one
card,
because
so
I'm
I'm
thinking
it's
quite
problematic
because
other
things
like,
for
example,
tim,
I'm
speaking
to
you
now,
you
were
often
concerned
how
easy
it's
to
break,
for
example,
with.
A
D
Sorry
so
I'm
looking
at
the
beat.org
site
currently
for
examples
and
I'm
seeing
that
sort
of
like
a
use
case
for
these
cards
would
be
the
the
black
section
where
we
have
the
upgrade
from
drupal
section
that
has
three
three
cards:
70
plus
included
modules.
D
Can
everybody
see
the
paints
yeah,
so
basically,
what
we
have
now
is
something
like
that
it
doesn't.
I
think
I
think
these
things
lead.
They
actually
lead
to
pages,
maybe
something
like
that,
but
in
a
vertical
horizontal
instead
of
very
cool
thing,
and
then
all
of
you
are
suggesting
something
like
this
with
more
text
right.
Yes,.
G
D
Yeah,
if
we
are
blocked
on
that,
I'm
happy
with
this
as
well.
Although
I
don't
know,
maybe
we
can
showcase
er
team,
I'm
not
sure
what
you
think.
Maybe
we
can
find
a
a
solution
for
this
card.
This
card
thing
that
is
actually
a
view
with
actual
notes,
not
pageless
things
right
and
then
we
can
implement
something
like
this
to
showcase
the
cards
or
the
page
list.
Node
example,
which
could
be,
I
don't
know
some
text
and
a
link
to
our
documentation.
F
D
F
Like
that,
reducing
it
to
adding
one
more
card
on
the
homepage
isn't
nearly
as
compelling
as
if
we
could
get
something
that
looked
more
like
a
real
website
with
a
three-column
grid
grid.
D
Well,
I'm
not
exactly
throwing
it
out,
I'm
trying
to
play
devil's
advocate
or
olaf's
advocate
in
this
case
and
say
we
can
have
both
of
these.
We
can
have
the
cards
as
they
are
now
be
an
actual
view.
So
we
demo
how
views
work.
D
H
D
G
D
G
Okay,
so
yeah,
I
like
the
idea
at
first
sight,
but
that
is,
I
said,
completely
different
issue
or
request
yeah.
So
it
has
had
nothing
to
do
with
pagerdust
notes.
So
yeah
nice
idea,
but.
D
G
Yes,
so
I
see
it's
a
pity,
but
I
think
it's
the
best
to
do
because
it
won't
break
things
and-
and
I
think
the
main
goal
wasn't
to
have
a
better
homepage-
it's
a
nice
result,
but
that
wasn't
the
goal.
The
main
goal
was
to
promote
this
very
special
content
type
and
I
think,
even
if
you
would
place
it
on
a
less
prominent
place,
for
example
on
the
about
page
in
the
sidebar,
we
still
would
have
the
content
type
and
people
would
go
to
the
content.
G
Type
page
would
see
it
and
see
the
description
and
could
work
with
it
and
without
breaking
things
and
having
issues
and
having
to
yeah
very
quickly
release
next
bug,
fix
versions
because
we're
breaking
all
the
things
I
think
it's.
I.
F
Still
feel
like
it's
really
important
if
we're
gonna
introduce
a
new
content
type
for
people
to
know
what
it
is
and
how
it
works,
and
if
we're
just
going
to
place
it
like
a
block
in
a
sidebar
there's,
there's
no
obvious
reason
why
people
would
choose
one
over
the
other,
and
when
you
have
something
like
a
home
page
where
you
have
three
in
a
row
like
it's
a
very
specific
different
thing,
then
I
think
it
it's.
It
will
make
more
sense
to
people
than
if
we
just
create
another
thing.
F
G
G
The
images
must
fit
the
in
the
aspect,
ratio
and
so
on,
and
even
so,
if
then,
if
you
think
oh
I'd
like
to
have
five
of
these
there,
it's
quite
hard
to
do
that
and
oh
I
I
only
want
two
of
them,
and
so
you
have
to
change
many
many
things,
and
I
don't
agree
that
this
is
the
special
thing
that
you
can
put
three
cards.
Let's
say
cards
in
a
row:
we
can
do
that
also
with
posts.
That's
not
the
specific
quality
of
cards
right.
F
See
it
and
identify
it
and
be
like?
Oh
that's
how
people
build
these
pages
where's
posts
in
a
row?
We
already
have
examples
of
that
like
we
already
have,
maybe
not
horizontally,
but
we
already
have
like
posts
feeding
to
the
home
page.
Yes,.
G
F
Yeah,
I
agree,
that's
why
we
like
the
three
there
too
same
same
reasons.
I
think
we
can
solve
both
the
problems
with
the
aspect
ratio
by
using
an
image
style
and
the
text
by
putting
some
description
text
at
where
that
is,
and
I
also
think
that
you
know
ability
to
change
number
of
items
in
a
view.
You're
right
is
not
really
the
issue.
F
It's
the
fact
that,
once
you
change
the
number
of
items,
it's
not
going
to
look
the
same,
but
I
don't
think
we
need
to
worry
about
that
too
much
for
core.
If
we
can
make
it
look
good
in
basis
and
in
seven-
and
you
know,
using
something
like
the
views,
grid,
style,
that'll
work
with
any
theme,
then
it
should
be
that
if
someone
starts
changing
that
stuff,
it's
not
going
to
be
it's
not
gonna,
be
terrible.
I
mean
it's
not
gonna.
F
Look
beautiful
like
it
is
when
we
originally
lay
it
out
in
three,
but
they
it
it's
not
too
hard
to
get
that
working
and
we
could
even
write
some
like
documentation
or
blog
posts
on
like
I
only
wanted
to,
or
I
wanted
five
or
whatever.
F
To
do
that,
it's
just
a
matter
of
like
adjusting
all
of
the
things
like
the
you're
right,
a
lot
of
things
about
the
image
style
and
the
amount
of
text
provided
and
the
number
of
items
per
row,
and
I
think
that
the
I
am
less
worried
about
people
trying
to
change.
What's
there
and
ending
up
with
something.
That's
not
perfect,
then
not
knowing.
B
F
Like
not
understanding
the
tools
that
we're
providing-
and
I
also
we
talked
about
this
a
little
bit
too
but
after
we
started
this
idea,
what
the
main
point
was
sort
of
expanded
and
there's
now
like
eight
main
points,
and
so
this
particular
issue
doesn't
solve
all
of
them.
It
solves
some
of
them
and
I
think,
like
providing
the
content.
Type
out
of
the
box
is
one
but
also
like
improving
the
homepage
is
another
one,
and
a
place
to
put
text
is
another
one
and
all
of
this
stuff.
F
I
think
you
know
there
are
other
ways
that
we
can
solve
all
the
other
issues
that
we
want
solved
too,
and
we
just
need
to
figure
out
how
like
what's
the
best
way
forward,
and
I
don't
know
if
that
in
this
case
is
the
safest
way
forward.
We
can
definitely
place
one
block
on
the
sidebar
or
one
block
on
the
home
page,
but
it
just
won't.
It
won't
be
as
compelling
a
change
when
we're
introducing
a
new
feature
where
I
think
that
we
have
the
room
to
do
that
later,
when
it's
not
new.
F
Try
this
thing:
you're,
not
gonna,
understand
I
think
it'll
be
a
little
better
if
we
have
something
more
robust,
go
ahead.
G
Yeah
so-
and
I
also
wanted
to
mention-
I'm
not
absolutely
against
it,
but
from
the
experience
of
the
last
release,
so
we
were
also
or
we
thought
we
were
quite
ready
to
put
it
in
the
release
and
then.
G
Release
freeze
and
we
don't
get
it
in
and
I
think
if
we
want
to
do
it
in
the
way
how
it's
planned.
Now
it's
much
work,
because
we
even
so
I
quickly
looked
at
it
and
kind
of
broke
it,
and
but
I
we
have
to
check
a
lot
more
things.
I
think,
and
especially
the
long
text
problem.
G
H
You
know
so,
to
be
honest,
I
mean
I
see
your
point,
but
I
don't
really
see
that
as
a
bug
or
a
broken,
I
mean
anybody
could
build.
I
I
it
isn't
that
uncommon
that
I
build
cards
like
this
and
then
I
accidentally
put
too
much
content
in
them
and
it
sort
of
breaks
and
well
that's
not
the
way
it
was
designed.
I
mean
if
you
use
something
the
way
it's
not
designed
for
it's
not
going
to
look
good
and
that
happens
in
core
all
the
time.
H
H
So
to
me
that's
not
difficult
to
solve,
and
some
of
the
I
don't
you
the
other
things
that
you've
raised.
I
think
we
can
improve
upon
fairly
easily,
so
I'm
not
too
worried
about
them.
It's
it
we're
not
trying
to
make
this
foolproof.
People
will
be
able
to
make
it
look
ugly
that
but
yeah
I
just
we
there's
other
things
in
core
right
now
that
function
the
same
way
as
far
as
I'm
concerned
that
you
know
people
really
easily
depending
on
how
they
use
them.
They
don't
look
good,
but
we
don't
worry
about
that.
J
I
think
it's
up
to
individual
people,
users
developers
how
they
build
their
site.
We
can
give
them
an
idea
of
how
something
might
look
out
of
the
box
if
they
change
this
up
to
them
to
build
their
site,
the
way
that
they
want.
I
don't
think
we
should
be
trying
to
build
a
system
where
they
can
build
stuff
a
whole
website
without
getting
into
views
or
code
or
whatever
else.
That's
like
that,
squarespace,
that's
other
things.
That's
not
backdrop.
In
my
opinion,.
F
Yeah
I
I
also
build
cards
for
most
of
my
client
sites
and
they
you
know,
we
tell
them.
It's
only
going
to
look
good
if
you
use
30
words
or
less,
and
I
think
we
can
do
the
same
thing
with
a
little
description
field
on
the
body.
That's
like
for
a
card.
It
will
look
best
with
whatever,
and
that
doesn't
mean
you
can't
put
in
more
characters
than
that.
F
If
you
want
all
your
cards
to
have
more
text,
but
at
least
it'll
be
a
guide
it'll
be
like
this
will
look
best
in
this
particular
format
and
then
it's
up
to
them
to
decide
whether
they
want
to
follow
that
recommendation.
I
do
the
same
thing
with
my
images
where
it's
like
recommended
image
size,
and
you
know
if
they
put
in
some
image
where
you
cut
off
someone's
head
or
something
they
know,
because
the
aspect
ratio
was
there,
they
could
go
back
and
put
in
something
better
if
they
wanted.
F
I
do
think,
though,
as
we're
working
through
this
every
time
you
see
something
like
that
where
you're
like.
Oh,
this
is
gonna
cause
problems.
We
should
know
about
it
so
that
we
can
try
and
see.
If
there's
anything,
we
can
do
to
make
it
easier
for
people
to
do
the
right
thing.
A
I
think
we
have
to
wrap
up
where
we
pushed
over
the
hour
quite
a
bit
but
yeah.
Thank
you
all
for
the
discussion.
Olaf
in
particular.
Your
patience
is
unrivaled
admirable
all
right,
but
let's
wrap
up
for
today
there's
more
issues
to
discuss,
but
we
can
do
so
on
the
internet
in
the
issue
queue.
The
1.21
milestone
is
open
with
10
issues
in
it.
So
there's
more
things
to
be
discussed
there
and
sounds
great.
A
Thank
you
all
for
for
joining
as
always
every
week
and
we'll
catch
you
guys
on
the
internet.
Maybe
hopefully
some
of
you
will
attend
the
sprint
on
sunday,
so
meeting
location.
For
that
tim
will
we
likely
be
using
this
zoom.