►
From YouTube: May 5, 2022 Backdrop Weekly Meeting
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,
everybody,
it
is,
may
5th
2022
happy
cinco
de
mayo
to
everyone
out
there.
This
is
the
weekly
backdrop
developer
meeting
where
we
get
together
every
week
to
talk
about
the
latest
happenings
in
the
world
of
backdrop.
Let's
see
before
we
go
further,
we'll
do
some
introductions
for
the
people
that
are
here.
My
name
is
nate
lampton,
I'm
quick
sketch
on
the
internet
and
a
core
committer
for
the
backdrop
project
we'll
go
to
jen
and
then
alejandra.
B
Hi,
I'm
jen
lampton
joining
from
oakland
california,
looking
forward
to
yeah
all
the
great
stuff
coming
up
in
the
next
release.
That's
it
for
me.
D
A
Nice
colorado
contingent
showing
strong
today.
Finally,
tim.
E
I
am
tim
erickson,
saint
paul
tim
and
the
issue
cues.
I
am
in
deerwood
minnesota
and
recovering
from
a
big
person,
or
you
know,
client
project,
as
well
as
the
release.
We
got
a
great
release
coming
out
and
just
got
through
feature
freeze.
A
Yeah
very
exciting,
and
before
we
go
further,
we
like
to
do
a
little
update
on
contrib
projects.
We've
had
a
couple
new
ones
come
through
this
week.
Jen.
Could
you
give
us
the
update.
B
Sure
we've
got
two
new
contrib
projects,
well-known
and
security
texts,
which
are
both
released
by
the
same
person
this
week.
I
think
they're
also
a
new
contributor,
so
this
is
from
daniel
j
r
may
they
had
a
contributor
application
recently
and
now
published
a
whole
bunch
of
modules.
So
that's
great
thanks
daniel.
A
Yeah,
wonderful,
all
right,
let's
see
so.
Every
week
we
have
a
forum
post
that
is
posted
to
forum
dot
backdrop
cms.org
under
the
events
category
for
anything
that
people
like
to
talk
about
during
these
weekly
meetings.
We
only
had
one
post
this
past
week.
That
was
actually
a
design
related
issue
and
sorry,
I'm
doing
this
out
of
order
jen.
But
we
didn't
have
a
design
meeting
today,
but
we
are
having
this
and
I
think
that
was
sorted
out
before
the
meetings
began.
It's
issue
5601.
B
So
it
hasn't
been
sorted
out,
it's
just
been
kicked
to.
We
need
more
opinions,
so
the
question
is:
should
buttons
have
a
little
hand
cursor
instead
of
the
arrow,
which
is
what
they
have
currently
and
the
internet
instructions
for
how
to
handle
buttons
very
clearly
say:
no
buttons
should
not
have
a
hand,
they
should
always
have
a
cursor
and
the
hand
specifically
indicates
a
link
and
a
link
never
causes
any
actions.
B
It
just
takes
you
to
another
page
and
it's
sort
of
a
visual
cue
for
people,
but
it
seems,
like
the
whole
internet
has
been
doing
this
wrong
for
a
very
long
time,
and
so
people
who
are
accustomed
to
using
the
inter
internet
really
like
it
when
the
buttons
have
a
different
icon
like
the
the
cursor
changes,
and
so
even
though
the
like
age-old
instructions
say
to
do
it
one
way,
it
seems
to
be
that
the
common
consensus
is
that
people
want
it
the
other
way,
and
so
we
had
this
issue
opened
against
backdrop.
B
Were
like,
but
apparently
hands
are
wrong
and
so
we're
like,
okay,
whatever
we
close
the
issue,
but
it's
come
up
again,
and
so
I
figured
it
might
be
worth
asking
people
in
general
again
and
it
could
be
just
that.
You
know
if
nobody
follows
the
standards
and
everybody
expects
it
to
be.
You
know
the
other
way
around
that
that
is
the
de
facto
new
standard,
and
that
might
be
something
that
we
should
consider
changing.
So
yeah.
B
Of
thing
where,
like
you
read
the
explanation,
you're
like
that
totally
makes
sense
to
me,
I
still
want
the
hand
right.
It's
like
I
get
it,
but
I
still
prefer
it
the
other
way.
So
yeah,
I
don't
know
I
just
figured-
maybe
more
voices
on
that
could
be
valuable.
It
might
also
be
good
if
we
could
get
like
accessibility
or
user
experience.
B
Experts
on
there
that
might
be
able
to
point
out
use
cases
for
it
one
way
or
the
other
that
those
of
us
who
see
it
every
day
just
aren't
aware
of
that
could
be
valuable
and
help
guide
our
decision
one
way
or
the
other
so
put
it
on
the
internet.
I
tweeted
it
to
see
if
maybe
people.
C
E
One
interesting-
and
so
I
was
somebody
else
brought
this
up,
but
I
was
researching
it
a
bit
myself
and
found
all
the
things
jen
just
said,
but
like
drupal
7
had
the
same
issue,
they
did
not
by
default,
but
I
went
to
drupal.org
and
drupal.org
now
has
a
hand
over
the
if
you
hover
over,
like
the
register
button.
So
even
though
that's
not
a
default
behavior
in
drupal
7,
I
don't
think
triple.org
and
I
you
know
I
tried
google,
I
tried
a
number
of
major
sites
and
all
of
them
have
a
little
hand.
A
Yeah
all
right
well
I'll
put
in
my
two
cents
on
that
issue
sounds
since
that's
what
we're
supposed
to
be
doing.
Let's
see.
That's
that's
great
thanks
for
the
background
research
and
thank
you
to
our
contributor
kit,
resa,
who
posted
that
issue
as
well.
A
All
right,
let's
see
here
other
news-
that
for
people
paying
close
attention
to
the
world
of
backdrop,
there
was
a
security
release
for
the
link
module
for
drupal
7
yesterday,
and
we
had
a
little
scramble
because
link
module
is
integrated
into
backdrop.
Core
has
been
for
several
years
now,
and
so
usually
when
a
security
release
affects
a
contrib
version
of
a
module
in
triple
seven
that
has
been
merged
into
backdrop
core.
It
usually
affects
backdrop
as
well
so
issue
5613
was
filed
publicly.
A
A
So
we
validated
that
it
wasn't
a
security
issue,
but
then
we
opened
up
5613
to
go
ahead
and
add
the
new
test
coverage
that
drupal
7
added
to
validate
that
everything
works
as
it's
supposed
to
in
backdrop
as
well.
So
we
didn't
end
up
needing
to
make
any
functional
changes
to
link
module,
but
while
we're
at
it,
we
decided
that
we
should
go
ahead
and
add
more
test
coverage
to
make
sure
that
we
don't
face
the
same
regression
in
the
future,
so
that
issue
5613
is
available
for
review.
A
All
right,
oh
gosh,
there's
so
much
news
that
happened
this
week.
The
biggest
thing
of
all,
of
course,
is
that
we
passed
backdrop
feature
freeze
for
the
122
release
and
so
on
may
2nd.
May
1st
was
the
feature
freeze
and
then
the
the
next
day
may
2nd.
We
published
the
122
preview
release,
which
is
now
available
for
download
from
github,
and
that
includes
all
of
the
new
features
that
will
be
in
the
122
release,
which
will
be
coming
out
in
10
days.
A
So
the
preview
release
is
intended
to
let
a
wider
audience
of
developers.
They
don't
necessarily
need
to
be
core
contributors.
Download
the
packaged
release
file.
Try
it
out
see
if
there's
any
regressions,
try
out
the
new
features
and
weigh
in
on
any
opinions
they
have
before
the
final
release
of
122..
A
E
On
the
preview
release-
and
there
are
any
thoughts
about
like
how
to
to
test
that
like
could
we
provide
any
guidance
for
what
somebody
that
would
be
interested
to
help
do
that
like
is
it?
I
suppose
one
thing
that
would
be
helpful
is
that
people
have
dev
versions
of
their
sites
that
they
could
apply
it
to.
B
A
Environments
where
you
have
a
local
environment
or
a
dev
environment,
that
would
be
the
ideal
place
to
go
ahead
and
do
those
checks
of
the
preview
of
the
preview
release.
A
Yeah,
but
those
are
the
best
places
to
to
try
things
out
and
it's.
It
is
extra
important
that
we
check,
update
hooks
in
particular.
Those
are
the
things
that
are
the
most
difficult
for
us
to
test
just
in
between
releases,
and
it's
also
the
most
useful
thing
to
like
see
what
happens
on
a
production
site
that
has
more
stuff
going
on
than
just
core.
A
E
I
I
asked
that
question
because
the
obvious
way
to
test
it
would
be
to
spin
up
a
new
site,
but
it's
kind
of
hard
to
test
some
of
the
things
on
a
new
site.
On
the
other
hand,
on
this
issue,
we
need
some
people
to
just
spin
up
a
new
site,
because
that's
the
only
way,
you'll
see
the
big
new
feature
well,
one
big
new
feature,
which
is
the
new
content
type,
and
so
that
it
would
be
great
for
some
people
to
spin
that
up
on
a
fresh
news
site
and
just
see
how
that
works.
A
Yeah
and
the
the
only
really
easy
way
easy
way
to
do
that
right
now
is
to
file
any
poll
request
and
you'll
get
a
sandbox
that
is
generated
with
the
latest
code.
I've
kind
of
toyed
with
the
idea
of
making
the
demo
sandboxes
on
the
home
page
run
the
preview
release,
but
I
don't
think
that's
a
good
idea,
because
when
you
download
backdrop
you
expect
it
to
match
what
you
saw
in
the
sandbox,
and
so
it
would
be
confusing
if
we
started
providing
future
releases
in
the
sandbox.
B
B
Still,
you
know,
we
don't
really
usually
do
a
release
between
preview
and
actual
release,
and
so,
if
we
know
there's
something
wrong
with
preview,
it
wouldn't
get
fixed
until
the
release
came
out,
but
speaking
of
demo
sandboxes,
it
would
be
cool
if
it
were
an
option
so
that.
A
Yeah
I,
when
it
when
this
makes
me
think
of
when
I
first
started
using
linux.
I
had
to
download
ubuntu
for
the
first
time
and
it
gave
me
an
option
of
like
which
version
to
download,
because
ubuntu
constantly
has
this
problem
of
it's
like
the
current
release.
But
then
there's
the
latest
lts
release
and
it's
really
confusing
which
one
you
should
choose
as
a
new
user.
A
It
turns
out
it
really.
There
isn't
really
a
right
answer,
which
is
probably
why
it's
so
darn
confusing
for
for
linux,
because
it's
like
do
you
want
something?
That's
a
year
and
a
half
old
or
do
you
want
something
that
is
stable
or
I
guess
a
year
and
a
half
old
and
stable
versus
like
something
that's
new
but
not
stable
and
it's
kind
of
a.
I
don't
know
it.
It's
a
very
confusing
decision
to
even
have
to
make.
A
All
right,
let's
see
yeah,
but
I
won't
let
my
own
confusion
color
our
own
decision
too
much
on
that,
I
don't
think
sure,
all
right,
so
122
122
we
finalized
all
of
the
functionality
that
we'll
be
getting
into
that
release.
We
brought
up
a
number
of
issues
last
week
for
which
we
we
finished
almost
all
of
them.
There's
issue
4645
the
new
date
formats.
I'm
I'm
pretty
excited
about
that
this
one.
That's
out
of
the
box.
A
Backdrop
now
defaults
to
internationalized
date
formats
instead
of
us-based
ones,
unless
you
select
the
us
time
zone
when
you
install,
which
is
selected
automatically
for
you,
so
really
for
the
united
states,
users,
nothing
changes
whatsoever,
but
u.s
dates
are
not
actually
the
default
anymore.
They're
now
the
exception
not
the
default.
So
that
was
a
really
excellent
change
to
make
a
more
global
out
of
the
box
installation
issue,
55.99,
just
a
small
display
issue
with
basis
an
issue
5331.
A
This
was
herbduel.
I
think
yeah
herb
dole
had
some
improvements
to
book
module
that
he
wanted
to
get
completed
and
we
added
some
new
functionality
and
way
like
interfaces
to
the
way
that
you
organize
and
structure
book
pages,
so
that
was
great
improvement.
There's
a
bigger
issue
3639
that
herb
is
working
on
just
making
book
module
better
across
the
board,
and
so
it's
nice
to
get
a
little
bit
of
movement
on
that
bigger
issue.
A
With
this,
this
specific
set
of
fixes-
let's
see
it's
not
on
this
list,
because
we
didn't
discuss
it
last
week.
I
don't
think,
but
we
also
added
a
new
image
format
or
image
style
for
cards
to
make
it
so
the
cards
are
sized
consistently.
A
All
right
so
yeah
122,
we
really
pretty
much
nailed
everything
that
we
put
into
the
milestone.
There
were
only
two
issues
that
got
bumped
issue
5348.
A
This
one
actually
had
been
marked
rtbc
a
couple
of
times
before
the
feature
freeze,
but
as
it's
adding
new
functionality
to
form
api,
and
we
didn't
have
a
lot
of
time
for
reviews,
I
went
ahead
and
let
this
one
slide
hoping
that
we
can
get
it
complete
early
in
the
123
cycle
instead
and
then
tim
pushed
forward
issue
4569
hiding
the
title
on
comments,
but
you
only
pushed
that
one
into
the
123
milestone
like
two
days
two
days
before,
once
your
other
issues
got
cleared
out,
then
you
pushed
that
one
in
which
is
great.
A
I
love
that
kind
of
enthusiasm,
but
yeah
that
one
we're
currently
going
back
and
forth
as
to
how
to
present
that
option
in
a
non-confusing
way.
A
So
that's
also
been
been
pushed
to
123.,
let's
see
yeah.
So
what
are
we
doing?
The
next
10
days?
We,
it
seems
like
a
lot
of
us,
are
taking
a
breather,
which
I
think
is
a
really
good
idea.
A
We
really
were
just
push.
Push
push,
go,
go,
go
there
for
the
last
couple
of
weeks
and
we
seem
to
be
in
a
really
stable
place
for
the
final
release.
A
However,
we
don't
need
to
be
if
you're
looking
for
something
to
do.
There
is
still
a
lot
to
be
done
and
the
place
to
look
for
things
that
we
can
do
in
the
meantime
is
the
bug
fix
tag.
So
121.5
is
the
next
bug
fix,
release
and
bug
fixes
are
not
restricted
by
feature
freeze.
We
can
continue
to
fix
minor,
bugs
and
user
experience
issues
all
the
way
up
until
the
day
of
release.
A
So
that's
where
activity
probably
will
be
going
on.
We
don't
actually
have
any
issues
from
the
121.5
milestone
to
mention.
We
did
have
a
big
week,
though
just
fixing
bugs
as
well.
So
let
me
see
the
121.5
milestone,
sorry
trying
to
get
this
listed.
Okay,
we
have
25
closed
issues
in
the
121.5
milestone,
which
is
a
pretty
big
set
of
bug,
fixes,
but
there's
still
37
open
issues
that
have
been
prioritized
into
that
milestone.
A
A
A
They
didn't
receive
any
feedback,
but
realizing
what
had
happened.
They
filed
an
issue
saying
you
know:
here's
my
pull
request
immediately
started
getting
some
traction
on
it,
but
they
were
like.
This
was
unfortunate
that
I
waited
for
months
and
didn't
get
any
feedback,
so
they
found
an
issue
saying
we
should
make
a
pull
request,
template
that
informs
people
when
they
file
a
pull
request.
A
You
should
also
make
an
issue
which
was
a
really
good
idea
and
something
that
was
a
little
bit
surprised
that
we
hadn't
done
yet
so
getressa
made
a
a
new
poll
request,
template
bug,
folder
came
in
and
helped
massage
some
of
the
language
a
little
bit,
and
now
that
is
now
merged
and
part
of
our
process
for
filing
pull
requests.
Now
we
now
have
just
when
you
file
a
github
poll
request.
A
You'll
get
a
nice
little
template
pre-populating
the
description
field,
with
mostly
comments
honestly
telling
you
things
you
should
know
as
you
file
the
pull
request.
A
Yeah,
so
that
was
a
really
great
little
enhancement.
Thank
you,
get
ressa
and
welcome
to
the
community.
A
That's
it
that's
it
for
today
we're
basically
you
know
in
the-
and
I
wouldn't
say
it's
the
calm
before
the
storm.
It's
the
calm
after
the
storm,
because
usually
our
release
days
are
really
pretty
chill
affairs
where.
E
B
A
That's
true
it.
It
shifts
our
I'm
painting
this
too
much
with
the
brush
of
development,
because
the
development
is
pretty
much
over
and
now
the
real
effort
needs
to
be
pivoted
towards
marketing
releases.
You
know
making
some
noise
after
the
release
comes
out
so
yeah,
that's
that's
where.
E
A
That's
true
sometimes
like
because
our
momentum
picks
up
so
tremendously
before
releases,
sometimes
that
that
tied
kind
of
or
that
wave
kind
of
continues,
even
though
there's
no
more
new
features
to
work
on
immediately
people
still
get
excited
about
the
next
release
coming
out
and
so
working
on
bugs
and
user
experience
fixes
yeah.
We
still
have
time
for
those
things
and
I'll
elaborate
more
on
that
that
the
user
experience
fixes
technically
could
be
considered
features.
A
A
We
allow
to
be
a
part
of
the
the
last
minute
changes
as
well.
So
it's
not
strictly
bug
fixes,
but
yeah
there's,
like
this
exception,
for
improvements
to
experience.
A
All
right
yeah
does
anyone
have
anything
they'd
like
to
to
bring
up
or
discuss
today.
A
No
okay!
Well
maybe
we'll
call
it
for
today's
meeting.
Then
I
appreciate
you
folks
being
here
today
and
of
course,
a
big
shout
out
to
our
community
doing
all
of
this
excellent
work,
making
122
a
really
excellent
release.
So
we'll
close
for
today
and
we'll
see
everybody
well
john
and
I
will
be
out
next
week,
but
there
will
still
be
a
meeting
on
may
12th,
which
will
be
the
last
meeting
before
the
release
of
1
20.
B
F
E
A
Okay,
all
right!
Well,
let's
close
for
today.
Thank
you
folks,
very
much
and
we'll
see
you
see
you
soon.