►
From YouTube: 2022/04/21 - Backdrop Weekly Dev
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
looks
like
we're
live
on
youtube.
I
didn't
get
a
confirmed
box,
I
don't
know
if
anyone
else
did
anyway.
Well,
we
look
live
today
is
thursday
april
24th
and
first
and
this
is
our
weekly
developer
check-in
meeting
for
miscellaneous
core
issues
and
similar
before
we
get
into
our
agenda.
We
should
go
around
to
do
some
quick
introductions
if
you
want
to
share
what
your
name
is
where
you're
from
and
something
excited
something
you're
excited
about
to
share
with
the
community.
You
can
definitely
do
that.
A
I
like
to
do
popcorn,
which
means
one
of
us,
will
call
on
another
one
at
random
and
then
we'll
go
around
until
everybody
has
introduced
themselves,
I'm
happy
to
go
first.
My
name
is
jen
lampton
joining
us
from
oakland,
california,
and
I've
been
working
on
a
lot
of
backdrop
sites
this
week
and
I'm
very
pleased
that
it's
not
a
lot
of
drupal
sites.
So
that's
what
I'm
excited
about.
Let's
see
joseph,
do
you
want
to
go
next.
C
Here
we
go
my
name's
tim
and
I'm
st
paultium,
I'm
in
dewey
minnesota
and
I
suppose
the
excitement
of
my
life
is
setting
up
a
a
linux
desktop
which
led
to
some
turmoil
in
terms
of
getting
zoomed
to
work
today.
But
it
seems
to
be
working
today
and
that's
why
I
have
two
two
two
zoom
windows
open,
but
for
now
so
ignore
the
other
10.
It's
an
imposter
robert.
C
E
I
am
martin
yorkshire
pudding
on
the
internet.
I've
been
I'm
working
on
their
backdrop
site,
but
I'm
also
doing
some
stuff
with
b,
which
is
the
command
line
tool
and
trying
to
make
it
work
better.
If
you're
installing
with
complex
passwords,
because
at
the
moment
it
doesn't
work
very
well
if
you've
got
complex
passwords.
E
So
I'm
trying
to
improve
that
and
just
pick
up
on
our
discussion
earlier,
I'm
I'm
also
gonna,
try
and
pick
up
where
jeff's
kind
of
started,
but
then
left
off
on
maintenance
mode
for.
F
E
A
So
thanks,
let's
see
so
in
the
last
week
it
looks
like
we
have
two
new
projects
out
so
contributed
projects
for
there's,
one
called
jquery
rss
block,
which
looks
like
it
holds
in
content
from
an
rss
feed
with
javascript,
which
is
kind
of
neat,
and
we
have
one
called
simple
tester,
which
I
guess
allows
you
to
run
an
individual
test
at
a
time
rather
than
doing
the
entire
test
speed
at
once.
A
A
We
didn't
get
a
forum
post
up
for
very
long
before
this
meeting,
so
I
don't
think
we
have
any
comments
from
the
forum,
but
if
anyone
has
anything
they'd
like
to
talk
about
in
today's
meeting,
we
do
have
a
open,
general
discussion
section.
If
there's
any.
G
A
G
G
That's
important
from
milestones,
maybe
sure
yeah
I
mean.
A
So
yeah
there's
a
couple
of
things
in
the
milestone
stuff
that
I
haven't
seen
before.
Yet
there
is
the
improved
styling
of
color
input
elements.
This
looks
cool,
it's
marked
rtbc,
that's
great.
A
No
and
then
we
also
have
the
add,
a
link
to
the
backdrop
cms.org
on
each
on
the
module
list
for
each
module.
A
C
You
know
the
somebody
worked
on
it
rakesh
and
he's,
I
think,
still
working
on
it.
So
I
don't
know
if
he
updated
his
pr
yet
or.
C
C
Do
we
have
this?
Is
there
a
screenshot
in
this
issue
anywhere
yeah.
C
There's
not
there's
a
well
the
the
screenshot
is
greg
greg.
Would
you
like
it
to
be
not
not
what
it
actually
is,
so
maybe
I
should
at
least
get
a
screenshot
I'll
try
to
work
on
that.
A
Yeah
interesting,
so
this
is
something
that
might
be
hard
for
a
first-time
contributor
to
sort
out,
but
essentially
the
module
list
lists
every
individual
module,
including
sub-modules,
for
a
project,
but
sub
modules
don't
have
their
own
page
on
drupal.org.
A
It's
only
the
parent
project
that
has
a
page
and
so
trying
to
find
something
that
we
can
use
consistently
consistently
for
a
link
on
the
modules
list
is
hard,
so
we
would
need
to
pull
the
project
name
and
use
that
and
then
decide
if
we
want
to
have
duplicate
links
for
sub
modules
or
if
we
only
want
to
link
when
the
parent
project
matches
so
yeah,
I
don't
know,
could
be
tricky.
C
A
Interesting
so
the
project
he
is
actually
only
usually
provided
an
info
file
if
the
module
belongs
to
a
different
project
than
its
own
name.
So
if
we
only
ever
added
a
link,
if
project
was
present
that
could
present
an
issue.
C
Okay,
I
just
put
a
screenshot
in
the
issue
for
anybody
that
helps.
C
Well
for
context
for
cash
again
came
from
that
code
spread.
He
was
one
of
the
top
pr
writers
during
that
sprint
and
has
expressed
an
interest
in
continuing
to
help
out
a
little
bit.
So
if
we
could
give
him
a
little
bit
of
support
on
this
issue,
I
think
he'd
be
willing
to
try.
It
dig
deeper
and
learn
a
little
bit,
but.
A
A
So
it
does
look
like
the
latest
version
of
the
pull
request
does
not
have
the
changes
that
nate
recommended
in
it
and.
C
Right,
basically,
what
he
said
was:
oh
should
I
just.
I
think
he
did
something
like
what
nate
suggested
earlier
and
then
he
switched
it
and-
and
that
said
that
you
know
rakesh
had
the
idea
before
and
so
rakesh
asked.
Should
I
just
go
back
to
this
version
of
it,
and
I
can't
answer
that.
I
don't
know
if
just
going
back
he's
got
a
link
this
one
and
basically
I
think
what
he's
asking
is.
If
I
did
this,
would
it
work
and
if
somebody
could
say
yes
or
no,
that
might
help.
C
A
I
mean,
I
think,
probably
what
we
should
do
is
try
it
with
the
bwp
and
recommended
the
references
module
that
has
sub
modules
of
user
reference
and
node
reference
and
see
what
links
it
generates
for
those
sub
modules.
A
And
then
we
should
decide
if
we
should
either
not
generate
a
link
in
the
case
where
we
don't
have
the
project
or
generate
a
link
to
the
project
page
for
the
parent
project,
for
the
sub
modules,
also
because
it
could
be
that,
like
the
parent
project
is
something
like
this
is
not
a
real
example,
but
something
like
vbo
and
then
the
name
of
the
module
inside
would
be
like
views
underscore
bulk
underscore
operations.
A
A
G
C
A
There's
also
layout
ui
allow
blocks
to
be
disabled
or
hidden
instead
of
removed.
I
would
love
that.
C
C
This
is
the
first
issue
inspired
by
our
survey.
Doc.
Will
this
this
breached
the
top
eight
issues
in
our
survey
and
doc
said:
oh,
we
have
a
contrib
module
for
that
and
he,
you
know
quickly,
converted
the
contrib
module
into
a
core
pull
request.
A
Just
got
tests,
this
is
fantastic.
One
thing
that
we
might
test
is
the
accessibility
of
the
disabled
color,
because
that's
something
we've
had
problems
with
in
various
interfaces
before.
C
H
C
I
don't
know
if
it's
gotten
a
seal
of
approval
if
anybody's
like
tested
it
against
to
be
sure,
but
it
was
worse
into
godzilla
raised
that
issue.
Doc
wilmot
made
it
a
little
better
olaf.
Do
you
know
if,
if
it's
good.
I
Enough,
no,
it's
not
and
we
have,
but
we
have
another
issue
where
we
try
to
solve
that
also
for
use
for
the
list
of
the
views
and
so
on,
but
it's
not
clear
yet
how
we
solve
it
so
but
yeah.
So
it
has
been
addressed
to
match
other
pages.
A
We
could
get
it
so
that
we're
not
introducing
excessively
it's
just
that's,
probably
a
pipe
dream,
but
I
might
go.
Do
a
google
after
this
and
see
if
drupal
came
up
with
a
interface
for
disabled
stuff
that
doesn't
use.
H
A
Or
gray,
so
they
probably
did
some
testing
so
I'll
just
go.
Look
at
it.
C
H
A
We
should
maybe
add
the
so.
The
tables
color
probably
won't
solve
the
block
interface
issue,
so
we
might
want
to
make
sure
we
have
this
because
it's
the
same
problem,
but
the
code
will
need
different
code
to
fix
it.
So
we
might
want
to
add
a
specific
issue
for
the
layouts.
A
Saying
that
out
loud
sure,
okay,
there
is
another
issue:
allow
forms
to
set
custom
validation,
error
messages
on
required
required
fields.
This
is
apparently
a
feature
that
exists
in
drupal,
8
and
there's
a
blocker
for
inline
form
errors
which
I
think
greg
is
motivated.
E
A
A
So
yeah,
it
looks
like
it
hasn't,
hasn't,
had
any
activity
since
january
and
the
request
is
for
clarification
on
whether
we're
doing
it
or
not.
It
looks
like
this.
Is
I
mean
I
don't
I'll
have
to
look
at
it
in
more
detail,
but
it
looks
like
what
this
is
is
sort
of
an
api
change
to
support
the
rest
of
stuff
that
can
happen
around
it.
It
confirmed
it's
not
actually
a
blocker
for
inline
formers,
but
it's
apparently
a
good
improvement
anyway.
A
So
maybe
I
don't
know,
maybe
we
should
see
what
it
actually
if
it
does,
if
it
does
anything
visually
different
immediately
in
the
pull
request.
If
we
have
any
examples
or
anything
like
that,
where
we
can
see
an
action
or
if
it
just
is
a
change
in
the
way
that
we're
handling
form
validation
errors,
that
could
be
interesting,
I
don't
know
if
we're
doing
it
or
not,.
B
C
E
C
Okay,
well
sounds
like
we
can.
There's
nobody
work
actively
working
at
this
anyways
right
now,
right.
A
Because
it's
probably
possible
to
do
and
can
trip,
that's
usually
why
they
like.
Let
me
let
me
see
what
I
was
thinking
add
something
on
the
pull
request
here.
A
Well,
all
of
those
other
changes
would
also
just
have
to
be
in
the
module,
so
there
is
like
a
inline
porn
errors,
module
for
drupal
7,
for
example.
I
don't
know
if
it's
doing
it
the
same
way
that
drupal
8
is
doing
it,
but
just
where
the
like,
whether
this
issue
was
a
blocker
for
a
core
or
not.
I
don't
know
I
have.
I
haven't
looked
at
it
recently
enough,
but
in
general,
when
I
added
contrib
candidates,
it's
like
oh,
this
could
be
a
module
instead
so
like.
A
If
we
don't
want
to
do
this
feature
in
core,
it
can
still
exist
and
someone
could
write
a
module
to
do
it
instead,
and
so
I
don't
know,
I
don't
know
where
this
is
right
now.
I
need
to
look
at
it
again,
but
I
obviously
was
having
that
thought
at
some
point,
which
is
why
I
put
the
label
on
it.
But
I'll
go,
look
at
it
again
and
add
a
comment.
Stockholm.
D
Yeah
greg
made
a
comment
dated
december
7th
when
we
pointed
out
that
we
would
go
through
all
of
our
quote:
validate
or
something
validate,
something
submit
functions
to
move
out
custom,
form-set,
error
logic
that
was
handling
these
things
individually
and
then
use
the
new
property
and
that
I
don't
think,
there's
a
clean
way
to
do
that.
Sort
of
change
as
it
contribute.
A
I
don't
know,
though
I
need
to
review
it.
I
haven't
looked
at
it
in
a
while
yeah.
I
can
also
read
the
drupal
8
issue
and
that'll
help
too.
I
don't
know
where
it
stands,
but
anyway,
I
document
deserves
an
answer
as
to
why
I
put
that
label
on
there.
So
I've
got
something.
F
A
A
That's
everything
on
the
122
issue,
with
the
exception
of
the
hidden
path,
content
type
issue
which
I
don't
know
if
we
want
to
talk
about.
We
talked
about
a
little
bit
before
the
meeting.
C
Well,
I
would
mainly
because
olo
is
here-
and
he
has
invested
deep
interest
in
this
issue-
that
we
should
update
him,
sorry
and
verify
which
one
so
olaf,
the
cards,
the
cards
content
type.
So
are
you?
Okay?
If
we
just
remove
the
image
styles
for
now
and
separate
that
issue
out,
I
think
you
indicated
that
in
the
issue
I'm
just
confirming
it.
C
Yeah
and
it's
yeah,
we
have
very
different
opinions
in
terms
of
trying
to
fix
that.
So
I
would
say
let's
and
it
might
be-
I
think,
the
new
issue
that
I
opened.
I
think
people
are
associating
it
too
much
with
this
issue
and
that's
causing
chaos
where
I
don't
know
that
there
should
be,
but
if
we
just
separate
it
out
deal
with
it
later,
it
might
be
cleaner.
I
H
A
Help
editors,
I
think,
that's
a
great
idea
for
the
card.
Node.
H
A
A
A
C
I
don't
think,
there's
anything
else
and
if
you
have
nothing
else
urgent
to
say
all
of
them,
we
don't
probably
need
to
talk
about
this
issue
anymore.
Most
of
john's
feedback,
I
think,
was
pretty
straightforward,
except
for
that
one.
I'm
going
to
sort
out
that
radius
thing
so,
but
I
think
that
charles
looking.
H
H
C
H
A
A
Milestone,
what
do
you
guys
want
to
do?
Do
you
want
to
look
at
the
bug
fix
milestone,
or
should
we
well.
G
A
I
keep
thinking
that
field
group
and
core
could
be
a
quick
win.
I
know
there's
like
a
bunch
of
user
experience,
stuff
we'd
have
to
work
on,
but
I
still
think
it
could
probably
go
in
as
a
standalone
module
which
makes
it
a
lot
faster
than
some
of
the
other
potential
things
for
new
features
in
core
but
yeah.
I
don't
know
I
feel
like
it's.
You
know
so
popular
already.
H
C
C
Okay,
well
so
it
could
be
a
quick
win,
but
I
think
it
would
require
that
somebody
with
a
sufficient
skills,
you
know
get
behind
it
and
answer.
C
E
C
Yep,
so
is
there?
Are
there
any
other
quick
wins
on
this
list?
This
is
our
survey.
Well,
a
nikon
font.
Decor
probably
isn't
like
a
super
complicated
issue
other
than
deciding
how
to
do
it,
because
I
know
that's
been
divisive
yeah.
Maybe
it
is
complicated,
but.
A
There's,
I
think,
that's
one
that
is
likely
to
spark
a
lot
of
debate,
because
I
think
when
I
originally
created
it,
I
was
thinking
about
font
awesome.
But
since
then,
font
hanzo
must
become
closed
source,
and
so
then
we
need
to
use
fork
awesome
and
it's
not
as
up
to
date,
and
it's
just
it's
one
of
those
things
where
you
know
people
will
be
like
we
should
make
our
own.
I
just
think
there's
a
lot
more
conversation
that
has
to
happen
around,
even
though
technically
it's
not
very
complicated.
It's
a
lot
of
decisions,
yeah.
C
That's
been
talked
about
enough.
I
reference
module
the
core.
I
think
nate
said
recently
that
we're,
while
we're
getting
close
on
that,
my
understanding
is
that
he
doesn't
think
we're
close
enough.
C
Automatic
updates
up
in
my
go
ahead.
Somebody
would
say
something
just
confirm
for
me.
This
automatic
updates
used
to
be
on
our
weekly
agenda,
because
it's
sort
of
my
understanding
that,
like
a
lot
of
the
work,
is
done
right.
What
it's
just
isn't.
A
Yeah
we're
working
on
something
called
package
signing
which
basically
would
make
project
module,
include
not
only
a
link
to
where
get
to
get
the
project,
but
like
a
hash
of
what
that
file
would
look
like,
and
that
will
make
sure
that
when
you
get
the
file
the
system
can
hash
it
and
compare
those
hashes
and
make
sure
it
got
the
file.
It
thought
it
was
getting
and
that's
really
important
before
we
start
automatically
updating
us
we're
not
introducing
something
where
someone
can
sort
of
stand
in
the
middle
and
be
like.
A
Oh,
you
wanted
package
a
I'm
going
to
give
you
a
package
b
instead
and
then
you
install
something
really
dangerous
on
someone's
computer,
so
yeah,
and
I
think
that
nate
has
a
really
good
proof
of
concept
up
for
how
that
would
work.
But
I
know
he
and
jay
franklin.
Maybe
franklin
wrote
the
first
version.
I
don't
know
there
was
something,
but
because
it
required
changes
to
project
module
in
addition
to
changes
to
core
it's
been
hard
to
move
that
forward.
A
C
Back
up
and
migrate
functionality
decor,
it
probably
doesn't
feel
too
easy.
So
number
six
here,
that's
the
one
that
we
do.
We
might
actually
get
into
court.
We
have
a
pr
john
just
made
a
case
for
field
group.
Functionality,
move
title
display
settings.
B
Custom
field
hook
to
like
put
it
into
the
the
manage
form
thing.
A
Yeah,
so
we
would
just
be
removing
it
like
there's
a
sec,
a
section
called
display
settings
and
I
think
what
we
would
want
to
do
is
move
everything
from.
Is
this
title?
No,
this
is
just
title
yeah
it
would,
it
would
make
it.
I
think
it's
called
a
pseudo
fields,
like
hook
pseudo
field.
Whatever
I
don't
know
on
the
in
even
in.
A
A
Yeah:
okay,
right
yeah,.
C
This
has
been
inactive
from
since
2019,
but
but
it's
obviously
got
some
interest
here.
It's
on
the
top
down
of
our
our
survey,
so.
C
If
anyone's
inspired
that
one.
A
A
C
Okay,
well,
if
anybody's
inspired,
there's
another
one
that
may
or
may
not
be
low-hanging
fruit,
that
would
address
a
pretty
popular
issue.
So
once
we
get
past
the
top
10
items,
you
know
we're
getting
down
down
to
items
that
have
only
12.
C
A
C
Is
this
the
one
you're
talking
about
allow
admin
to
hide
title
and
comments?
No.
E
I
remember
the
disabling
comments:
there's
a
lot
of
discussion
about
a
number
of
different
scenarios,
so.
F
C
Allow
option
to
globally
disable
comments.
That
was
the
one.
A
A
C
Well,
yeah,
and
then
you
know
was
it:
was
it
working
at
the
time?
Pr
needs
work,
okay!
Well,
that's
something!
Somebody
could
look
at
and
see
if
how
much
work
might
be
involved
in
that,
so
we
do
have
the
while,
I'm
sharing
my
screen,
I
will
just
remind
everybody:
I
created
the
the
blog
post,
so
people
can
if
they
want
to
list
issues
that
are
their
priorities
or
if
they're
looking
for
this
was
something
we
could
have
kind
of
walked
through
to,
although
I
think
we
touched
on
most
of
these
issues.
C
F
A
C
E
See
the
the
typo
in
the
heading
of
five
five.
Ninety
has
been
corrected
on
github,
but
hasn't
come
through
on
to
the
on
to
maybe
it's
just
on
the
blog
post,
as
opposed
to
feeding
through
right.
C
I'll
do
that
after
anybody
who
has
access
to
edit,
you
should
feel
free
to
edit
this
list.
If
you
have
edit
access
on
bankrupt.org,
otherwise
just
flag
me,
an
office
yeah.
C
A
All
okay:
well,
we've
got
10
minutes
to
go
fix
maintenance
mode.