►
From YouTube: 2022/09/22 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
Hi
folks,
it's
September
22nd
2022,
and
this
is
the
backdrop
weekly
developer
meeting.
We
get
together
every
week
to
talk
about
priorities
and
happenings
in
the
world
of
backdrop,
development
with
a
focus
on
core.
Usually
so
it's
been
just
a
week
since
the
123
release
that
all
seems
to
be
going
pretty
well
and
we'll
touch
on
that
lightly,
and
we
have
some
other
topics
that
were
brought
up
from
the
weekly
Forum
post.
We'll
do
some
introductions.
A
First,
my
name
is
Nate
Lampton,
quick
sketch
on
the
internet,
I'm
a
core
committer
for
the
backdrop
project
coming
from
Oakland
California
we'll
go
to
Jen
and
then
Joseph.
B
I'm
Jen
LinkedIn
also
joining
from
Oakland
California,
currently
in
the
middle
of
a
backdrop,
upgrade
I'm
hoping
to
do
very
quickly,
we'll
see
how
it
goes.
I'll
report
back
on
that,
but
yeah,
let's
see
Tim.
C
Tim
Erickson
St,
Paul
Tim
and
then
Deerwood
Minnesota
today
and
yeah
I,
just
as
I
said
in
the
last
meeting,
I've
been
saying
for
the
last
three
weeks
that
I'm
launching
the
site
today
I
think
it's
really
official.
We
did
that
the
Public
Announcement
was
made
friends
of
the
Mississippi
River
fmr.org
is
was
a
Drupal
7,
upgrade
to
background
one
I'm
really
happy
with
and
hope
to
be
sharing
more
about
later.
That's
it.
A
Wonderful
thanks,
Tim
Joseph
and
then
Martin.
D
I
am
Martin
from
the
United
Kingdom
Josh,
putting
on
the
internet
around
that
crop.
A
All
right,
thank
you.
Everyone
Jen,
there's
some
activity
in
contrib
this
week.
Can
you
give
us
a
little
update
over
there.
B
Sure
so,
let's
see
this
week,
we
have
a
handful
of
new
contributed
modules,
which
is
pretty
exciting.
We've
got
file
or
filter
permissions,
ref
tagger
views,
role-based
Global
text
and
seek
editor
code.
Snippet
all
have
new,
stable
releases
this
week.
B
A
Well,
I
guess
you
know,
let's
pause
for
a
second
and
talk
about
123,
since
we
haven't
had
the
moment
to
talk
about
its
release
yet
since
it
was
made
after
last
week's
meeting,
so
123
came
out
September
15th
of
one
week
ago,
pretty
late
in
the
day,
but
it
did
come
out
on
time
as
usual,
so
yay
celebrate
the
release
of
123
very
successful
and
a
rather
large
release.
A
Actually
lots
of
new
features
and
functionality
are
in
the
123
release
in
a
really
excellent
release
for
us
just
lots
of
new
features,
and
we
gotten
things
in
of
well
ahead
of
time.
We
got
in
almost
all
the
features
we
wanted
to.
It's
a
really
great
release.
A
Let's
see
the
release
came
out,
we
yeah
we,
we
don't
have
an
announcement
yet
which
isn't
great.
We
did
I
think
see.
I
saw
that
the
site
update
notifications
went
out,
though,
and
pointed
to
the
wrong
here.
Tim,
but
I.
Think
I
saw
a
little
notification
in
the
news
block
on
backdrop,
sites
that
that
points
to
the
release
notes,
which
does
give
you
a
pretty
good
overview
of
everything.
That's
in
123.
I
love
that
news
block
by
the
way
I
just
think
that
is
the
greatest
thing.
A
A
Yeah
for
my
client
site,
I
love
to
dashboard
enabled,
but
I
turned
off
all
of
the
blocks,
except
for
the
list
of
the
user
accounts,
the
content
counts,
they
have
a
a
custom
administrative
menu
and
then
the
news
block
and
the
update
block,
and
so
like
the
update
Block
in
the
news
block
kind
of
for
one
column
and
that's
like
hey.
This
is
what's
happening
outside
of
your
website
and
then
the
other
column
is
what's
happening
inside
your
website.
It's
really
great
foreign,
okay,
so
yeah
123
great
release.
A
A
So
every
week
we
have
a
forum
post
it's
over
on
forum.backdropcms.org
under
meetups
and
events,
there's
a
a
a
an
issue
every
week
for
the
weekly
meetings
for
people
that
want
to
have
stuff
brought
up
or
discussed.
A
So
if
you
run
into
anything
that
you'd
like
to
talk
about
or
have
talked
about
during
the
meetings,
even
if
you're
not
going
to
be
present
just
pop
a
comment
into
that
Forum
post
kind
of
with
a
description
of
what
it
is
that
you
want
discussed
and
maybe
hopefully
link
over
to
a
GitHub
issue
that
like
covers
it
more
in
depth.
So
first
issue
that
we've
got
here
is
one
that
Tim
has
brought
up
around
some
contrib
modules
that
are
having
some
problems.
A
I
saw
that
this
is
related
to
MailChimp
and
there's
separately.
Another
person
filed
on
the
Forum
post
that
they're
having
some
trouble
with
MailChimp,
and
maybe
that's
where
this
spun
out
of
but
yeah
Tim.
Do
you
want
to
kind
of
give
us
a
rundown
on
the
problems
that
we're
seeing
and
if
you
have
any
ideas
for
for
what
we
should
do.
C
Sure
that's
a
quick
thing
was
that
Forum
post
that
that
popped
up
somebody
was
having
problems
with
the
MailChimp
poncho.
The
MailChimp
module
doesn't
have
a
lot
of
users
for
backdrop,
and
it
might
be
because
of
some
of
these
problems.
I
don't
know,
but
anyways.
There
was
a
discussion
in
Julep
about
it
and
I
think
Archie
piano
identified
the
part
of
the
one
of
the
reasons
that
the
MailChimp
launcher
wasn't
working.
C
Was
it
had
a
dependency
on
The
Entity
wrapper
module,
I
forget
which
has
been
merged
into
core,
and
if
you
try
to,
if
you
try
to
enable
MailChimp,
it
says
you
need
this
other
module
that
tries
to
install
that
and
it
generates
a
manner
like
a
white
screen.
Now
it
turns
out,
it
actually
does
enable
the
module
or
install
the
module
button,
but
it's
a
pretty
serious
error
in
the
process
and
so
I.
C
We
don't
we
it's
at
least
it's
a
Time
unless
somebody's
done
anything
this
entity
wrapper
module,
that's
been
merged
into
core
I.
Think
there
is
a
note
on
thebackrep.org
page
that
says
this
has
been
merged
into
court.
Don't
you
don't
need
it,
but
in
cases
where
there's
a
module
that
requires
that
somebody
could
easily
install
that
without
knowing
that
they're
not
supposed
to
install
it
and
I'm
just
wondering
should
that
even
still
be
on
backdrop.org.
B
B
C
Well
but
sure
so
that
that
fix
happened.
So
then
there
was
the
issue
of
there's
the
issue
about
that
module
itself,
which
it
apparently
isn't
needed
anymore,
but
it's
still
on
backprep.org
and
then
there's
the
issue
of
modules
that
require
it.
The
MailChimp
would
be
one
doc.
Wilmot
went
ahead
and
already
fixed
the
problem
with
the
requirement
and
he
released
a
MailChimp,
a
new
version
of
MailChimp
so
that
that
that
that
part
of
it
that's
been
solved.
C
B
That's
a
good.
This
is
a
good
policy
question
in
general.
What
do
we
do
with
modules
that
are
like
unsupported
and
I
think
in
Drupal
they're
all
left
online
but
marked
as
unsupported?
B
We
don't
even
Mark
modules
as
unsupported
in
backdrop,
so
we
could
start
doing
that,
but
even
if
we
did
remove
it
entirely
from
backdropcms.org
we're
not
going
to
stop
any
module
from
requiring
it
if
they
want
to
acquire
it.
So
that's
not
going
to
fix
that
problem.
B
So
the
question
is
like:
what
do
we
want
our
public
record
to
be,
and
do
we
want
anything?
That's
marked
as
unsupported
to
be,
for
example,
like
not
installable
through
the
project
browser-
and
you
know
we
have
some
additional
concerns
that
I,
don't
think
affect
Drupal
in
the
same
way.
So
we
might
want
to
come
up
with
a
different
answer
for
that
right.
C
C
B
Well,
it
usually
means
that
there's
no
one
taking
care
of
it,
and
so
the
security
team
is
like
no
throw
a
big
red
arrow
on
it
from
anyone
whose
site
is
running
it
but
I,
don't
maybe
we
need
another
word
for
backdrop
too.
That
you
know
would
be
more
severe
than
that.
Well,.
C
But
it's
it's
saying:
don't
use
it
not
because
there's
nobody
supporting
it,
which
there's
a
difference
right
right,
like
the
Drupal
version.
Is
the
module
might
work
for
you,
but
there's
nobody
supporting
it.
It
could
be
dangerous,
whereas
this
is
a
module
that
we
know
doesn't
work
right.
It's
not
a
question,
it
might
work
for
you.
It.
B
Doesn't
right
right
so
I
think
I
think
the
question
is
like:
what
do
we
do
with
our
history
right
like
do
we
want
to
erase
our
history,
which
I
think
the
answer
is
absolutely
not,
but
then
the
question
is:
how
do
we
protect
anyone
in
the
present
by
not
being
injured
by
our
history
and
so
I
think
we
might
need
a
new
status
for
that
and
if
it's
not
go.
A
Well,
there's
another
thing:
we
can
do
as
well
and
that's
and
this
isn't
a
strong
wording,
but
it
has
a
technical
effect
and
that's
the
recommended
version,
so
you
can
set
like
1.x
or
2.x
is
the
recommended
version
and
if
you
set
recommended
version,
To
None,
then
that
Flags,
the
modules
being
unsupported
in
update
status.
B
Okay,
I
like
this
can
I
feel
like.
We
need
to
document
this,
though,
because
we're
going
to
run
into
this
like
two
years
from
now,
we
did
how
about
we
have
I'm,
just
gonna
brain
start
this
and
then
I'll
write
it
down.
If
you
guys
think
it
sounds
good.
How
about
we
have
through
the
backdrop
contrib
issue
queue.
We
have
the
way
to
Mark
a
module
as
deprecated
or
I,
don't
know
whatever
we
want
to
call
it.
So
you
can
open
an
issue
and
be
like
hey.
B
This
module
broke
everything
on
my
website,
I
want
to
let
you
know
and
then
have
whoever
it
is
who's
responding
to
that
issue
queue
so
right
now,
it's
like
me
and
Tim
and
Greg
or
whoever,
but
whoever
who
also
usually
has
access
to
modify
those
nodes
on
backdropcms.org
can
read
the
issue
in
the
issue
with
you
and
go
yes.
Thank
you
for
letting
us
know,
and
then
the
process
would
be
to
change
the
recommended
version
and
Mark
it
as
deprecated
or
not
unsupported.
B
If
we
don't
have
a
deprecated
option,
but
I
think
it
might
be
good
to
add
a
deprecated
option
and
then
also
update
the
info
file
to
specifically
point
to
the
replacement
project.
If
there
is
one
like
in
this
case,
so
that
if
you
look
at
it
backdrop.s.org,
it
will
say,
use
this
module.
Instead,
you.
B
B
A
And
someone
else
could
and
to
be
really
clear.
Sorry,
that's
backdrop:
Dash
Ops,
slash
background.
Yes,
yes,
which
is
the
application
cue
and
like
that
I
need
help
with
my
module
queue.
I
need
help
with
a
contrib
module.
A
Yeah,
okay,
yeah,
that
that
sounds.
That
sounds
really
good.
As
far
as
like
you
know,
that's
something
that
we
can
do
right
away.
There's
kind
of
like
this
long-term
thing
that
editing
like
for
a
contrib
author
everything
happens
through
the
GitHub
UI.
A
Like
you
create
releases,
you
create
tags,
you
you
do
everything
through
GitHub,
but
there
are
still
corresponding
project
notes
on
backdrop,
cms.org
that
is
done
by
our
integration,
with
GitHub
and
kind
of
the
problem
that
we
have
is
that
only
I'm
elaborating
just
on
your
explanation:
Jen
I
hope!
That's!
A
Okay,
the
only
site
administrators
on
backdropcms.org
have
access
to
modify
project
nodes
directly,
so
it's
different
than
the
way
that
contrib
Works
in
triple
land,
where
all
of
the
management
is
done
on
on
drupal.org,
including
creating
the
releases
and
like
modifying
the
the
settings
as
to
like
recommended
versions
and
stuff
like
that,
and
we
have
a
little
bit
of
a
problem
that
not
everything
can
be
done
through
the
GitHub
UI,
and
this
is
one
of
those
things
that
if
a
module
has
a
new
release
like
a
2.x
version,
there's
no
way
for
the
module
author
to
say:
I
want
to
switch
from
1.x
to
2.x
as
being
the
default.
A
They
have
to
ask
someone
for
help
currently,
so
anyway,
that's
marking
stuff
is
there
is
no
recommended.
Version
also
requires
a
site
administrator
on
backdropcms.org,
and
so
that's
going
to
be
our
workaround
for
now.
So,
although
that
this
marking
something
is
no
recommended,
version
effects,
update
status
and
we'll
say
this
module
is
unsupported,
I,
don't
know
if
it
will
affect
project
browser.
A
So
there
could
be
another
aspect
there,
I
I,
yeah
I
mean
we
definitely
have
an
opportunity
to
try
here
with
entity
metadata
wrapper
to
see
what
happens,
because
I
think
that
this
is
you
know
the
right
thing
to
do
is
we
should
be
removing
this
thing
as
shooting
recommended.
We.
C
Have
a
related
issue,
and
maybe
we
can
solve
both
of
these,
which
is
something
in
the
last
one
or
two
backdrop
lives.
There
was
a
lot
of
discussion
about.
Was
that
sort
of
modules
that
are
on
GitHub
in
sort
of
alpha
state
that
aren't
available
that
work,
but
aren't
available
on
backdrop.org
and
people
are
afraid
to
move
them
and
I
think
that
we
have
some
general
consensus
that
we'd
like
to
be
able
to
have
like
Alpha
modules
or
beta
modules,
be
released
on
backdrop.org,
but
not
have
the
project
browser
install
them.
C
I
I
feel,
like
we've,
talked
about
that
and
there's
General
agreement
that
that
would
be
a
good
way
to
handle.
That
is
that
you
can
still
find
the
modules
you
just
couldn't
install
it
through
the
installer,
and
it
seems
to
me
like
this
is
a
relate
a
similar
situation
right
where
we
have
a
module
which
we
want
visibility
of,
but
we
don't
want
people
to
accidentally
install
Break,
yeah.
B
We're
supposed
to
already
have
that
first
use
case
in
place
where,
depending
on
the
format
of
your
version
string,
it
either
should
or
shouldn't
be
available,
but
I
don't
think
that's
working,
so
we
might
just
need
a
follow-up
issue
to
fix
that.
It
might
not
be
related
to
this.
This
I
think
we
don't
have
anything
that
supports
this
and
we'll
definitely
need
to
add
something
and
I.
Don't
know
if
the
version
string
is
the
same.
B
C
B
C
C
The
MailChimp
is,
is
I,
don't
know
that
we
need
to
talk
about
at
the
time
the
MailChimp
module
was
just
sort
of
broken,
and
there
was
no
maintainer
I
believe
that
it's
now
been
fixed
enough
that
it
does
install,
and
you
know
it
doesn't
obviously
break
a
site.
So
I
don't
know
that
there's
any
action
that
we
need
to
take
on
MailChimp
other
than
to
let
people
know
that
this
seems
like
it
should
be
a
really
popular
module.
C
A
Yeah
I'm
looking
I,
take
a
quick
look
here
at
the
project
browser
code,
which
is
custom
code
on
backdropcms.org
that
Returns
the
search
results
and
it
it's
only
consideration
is:
does
a
project
have
releases
or
not,
so
it
actually
doesn't
even
care
if
it's
alpha
or
beta
or
whatnot
or
unrecommended
or
unsupported
I
mean
it
really
only
cares.
If,
if
there's
any
release
at
all,
then
it
shows
up
in
Project
browser.
A
So
it's
for,
like
Alpha
and
beta
modules,
like
those
will
show
up
as
soon
as
they
have
a
release,
and
so
that
that
does
do
something
to
to
project
browser
already,
and
so
it's
actually
detrimental
for
our
current
situations,
though,
where
we
want
to
remove
something
from
Project
browser,
we
need
to
make
a
modification
to
that
custom
code.
That's
on
backdropcms.org,
to
say
like
which
stuff
should
I
show,
but.
B
Will
will
it
work
if
we
remove
it
from
GitHub,
but
it
doesn't
Oh,
you
mean
the
release.
Node
interesting,
well,
it'll
probably
get
put
back,
though
right
if.
B
A
B
A
B
Even
without
any
code
changes
today,
what
we
could
do
is
Mark
no
releases
being
recommended,
delete
the
release,
note
for
the
problematic
release
or,
if
there's
more
than
one
all
of
them,
and
that
would
remove
it
from
the
project
browser
immediately
and
then
I'll
note
that
here
in
the
issue
I'm
working
on
but
long-term
solution,
we
would
want
that
same
behavior
if
a
module
was
marked
as
deprecated
or
not
supported.
B
A
Yeah
well
I
think
in
the
future
we
should
have
if
there's
no
recommended
version
at
all,
like
I'm,
sorry,
no
supported
version,
then
it
shouldn't
show
up
in
Project
browser.
A
There's
a
difference
between
you
know,
Alpha
and
recommended
then
supported
and
so
there's
an
option
in
Project
module
for
like
is
this.
Is
this
release
branch?
Is
this
entire
Branch
supported
and
we
should
say
if
there's
no
supported
Branch,
it
shouldn't
show
up
yeah.
C
So
to
clarify,
if
I
or
someone
finds
a
module,
that
is
just
plain
broken
it's
breaking
sites
upon
install
and
it's
on
backdrop.org.
We
can
open
an
issue
in
the
backdraft.org
or
the
backdrop
Ops
encrypt
q,
and
then
someone
like
me,
who
does
have
permission,
is
authorized
to
go
in
to
make
these
changes
right.
A
Yes,
as
we
should
make
sure
that
you
also
understand
that
marking
a
module,
unsupported
will
also
affect
update
status
and
throw
an
update
error
like
not
saying
you
can't
update,
but
actually
like
putting
that
module
in
red.
When
you
view
the
update
status,
saying
this
module
is
unsupported
with
a
big
exclamation
point,
which
may
also
be
a
good
thing.
You.
C
A
It
really
is
and
they
need
to
get
off
of
it.
So,
but
usually
I
mean
speaking
from
the
experience
of
Drupal.
When
a
module
is
marked
unsupported,
it
usually
causes
a
further
and
then
somebody
comes
in
and
fixes
the
module.
So
it
can
be
marked
supported
again
because
that
really
freaks
people
out
when
they
did
nothing
and
then
suddenly
their
site
is
throwing
an
error.
C
C
Well
for
now
I'm
thinking
I
would
only
do
that
if
I
know
it's
like
the
installation
of
it
is
breaking
a
site,
but
there's
conceivably
somebody
that
installed
it
at
some
point
in
the
past.
It
may
still
be
working
for
them,
even
though
it's
not
installing
on
new
sites,
I
think
that's
possible
and
that
that's
where
that
could
come
up
right.
Yep.
D
Do
we
need
to
also
consider
about
where
modules
have
moved
from
contrib
into
core
within
this
and
having
making
sure
they're
dealt
with
consistently.
A
That's
a
good
question,
so
Macho's
moved
into
core,
they
do
a
couple
of
things.
So,
first
of
all,
when
you
run
update.php,
it
throws
a
little
message
saying
a
warning
that
says
this
module
has
been
moved
into
core.
You
should
remove
your
copy,
but
if
you
miss
that
when
you
run
update.php,
then
another
message
is
shown
in
the
status
report.
Also
a
warning,
not
an
error,
saying:
there's
two
versions
of
this
module
on
your
site
and
currently
the
contrib
module
one
will
win
because
that's
the
you
know
the
order
of
importance
thing.
A
The
core
modules
are
the
least
important
in
terms
of
like
when
it's
searching
for
modules,
and
so
the
contrib
one
will
actually
be
the
one
that's
running,
which.
A
Yeah
that
okay,
that's
true
if
the
module
has
been
merged
into
another
module
like
path,
Auto
being
merged
into
path
module,
but
if
there's
literally
two
modules
like
entity,
reference
and
entity
reference,
the
contrib
and
the
core
one,
then
it
has
a
behavior
of
like
telling
you
there's
two
modules
running
at
the
same
time:
I
guess
yeah,
there's
two
situations
here,
but
I
guess
as
far
as
like
marking
them
supported
or
not.
You
know
the
process
may
end
up
being
similar
or
the
same,
but
yeah
it's
a
it's
a.
B
We
have
like
CK,
editor
and
stuff
in
cantrip,
where
we've
handled
this
before
redirect
and
for
those
on
the
module
page
itself.
We
just
add
a
big
message
that
says
like
this:
module
is
only
works
on
before
versions
whatever,
but
one
thing
that
we
could
do
is
in
the
info
file.
We
could
add
a
version
requirement
to
backdrop
course
so
that
it
would
only
run
on
versions
before
the
version
where
the
core
module
was
introduced.
Yeah
that
might
also
help.
A
That's
a
pretty
good
idea
that
we
should
yeah
that,
then
that
would
prevent
the
module
from
being
used
in
any
newer
version,
but
it
would
still
like
leave
it
there,
because
we
don't
really
want
to
explicitly
throw
errors
and
stuff
like
that
on
people's
sites
that
just
haven't
updated
fast
enough,
but
I
guess
there's
also
like
a
question
of
like
once.
It
moves
past
the
two
releases.
So
once
it's
been
six
wait.
What
would
that
be?
A
Eight
months
once
it's
been
eight
months
and
that
version
of
backdrop
core
is
no
longer
supported?
Should
we
be
going
back
and
like
saying,
hey,
you
gotta
upgrade,
because
this
thing
isn't
supported
anymore,
like
nobody's
going
to
be
maintaining
it
at
that
point,
or
at
least
there's
no
there's
no
stated
obligation
for
anybody
to
maintain
it.
After
the
two
mining
releases.
B
I,
don't
I,
don't
think
eight
months
is
long
enough
to
assume
that
everybody
will
have
updated
their
sites,
so
I
think
I'm.
Setting
a
message
is
fine,
but
I
don't
know
if
we
want
to
be
any
more
heavy-handed
than
that.
A
Update
status,
something
unsupported
like
if
they
went
into
their
site
and
checked
update
status,
then
it
would
say:
hey
you're,
running
on
supported
stuff,
but
that
might
just
cause
new
levels
of
confusion
where
it's
like.
They
try
to
update
that
module
and
they're
like
there
is
no
new
version
of
this
module
right
and
that's
because
the
solution
isn't
to
update
the
module.
It's
update
core
right.
C
A
Yeah,
okay,
boy,
yeah:
sorry,
we
really
went
down
a
rabbit
hole
there.
I
didn't
even
notice
how
much
time
we
were
spending
on
it.
Yeah.
Let's
move
on
to
the
next
topic,
then
so
this
is
issue
number
four
thousand
and
seven,
the
title
of
which
is
add
alt
and
title
fields
to
the
image
file
type.
A
D
I'm
happy
too
okay,
so
at
the
moment
there
there's
no
well,
certainly
in
brand
new
backdrop
installations,
there's
no
alt
or
title
Fields
stored
against
image
when
you
upload
it
through
manage
files,
or
you
go
to
look
at
an
image
through
manage
files.
It's
there's
nothing
there.
When
you
upload
something
through
the
node
or
you
add
an
existing
image
to
a
node.
D
You
have
the
option
through
the
content
type
settings
to
say,
enable
alt,
enable
title,
and
you
you
add
it
there
and
it's
stored
against
that
node.
If
you
then
reuse
that
image
on
another
node,
you
have
to
enter
it
up
all
over
again,
even
if
it
in
that
case
is
the
old
title
is
the
same.
D
So
what
what
we're
looking
at
is?
How
can
we
reduce
some
of
that
pain?
Make
it
possible
to
reuse
the
Alton
title
whilst
retaining
flexibility
to
override
that?
Where
I
I
can
think
of
lots
of
occasions
where
the
title
would
need
to
be
different
and
there's
a
few
where
they're
the
old
would
need
to
be
different.
So
we
what
we've
done
is
just
thought
about
how
that
might
work
for
users
going
forward.
D
We
haven't
got
anywhere
on
the
technical
implementation
that
there
was
a
question
a
while
back
about
where
it
would
go
in
the
database,
and
so
it
will.
It
could
possibly
go
in
file
metadata
or
it
could
possibly
have
its
own.
D
D
Alton
title
or
I
want
to
override
it,
and
you
would
be
able
to
update
the
olden
title
in
manage
files
and
it
would
update
to
all
of
those
who
haven't
overridden
it.
So
that's
the
the
general
use
case
and
you
could
you
could
upload
it
either
in
manage
files
or
you
could
upload
the
image
in
the
node
and
wherever
you
created
it
first,
you
would.
That
would
be.
That
would
be
the
default
alt
and
title
than
any
future
ones.
D
You'd
have
the
option
to
use
that
or
override
it
that
that
was
the
General
approach
and
I.
Think
what
where
we
got
to
in
the
design
meeting
was
we
we
wanted
to
get
input
from
car
committers
as
to
how
how
far
we
should
go
from
that
and
how
we
should
think
how
it
should.
We
should
think
about
implementing
that.
A
Yeah,
the
discussion
here
looks
like
it's
great
and
it's
covered
the
the
you
know
the
the
concerns
that
I
would
have
about
alt
and
title
reuse,
having
one
Central
title
in
alt
and
then
using
it
everywhere
throughout
the
site
is
problematic
because
other
people
have
pointed
out
in
the
issue
already
yeah
Olaf
put.
Some
good
notes
in
here
has
to
Indigo
dial
up
and
yeah.
It's
totally
right
that,
like
alt
text,
often
needs
to
be
different
on
based
on
where
the
image
has
been
used.
A
A
So
a
global
global
Central
thing
is
not
great,
but
I
like
really
where
you're
heading
here,
where
it's
like
the
central
one
actually
just
becomes
the
defaults
and
then
on
every
time
you
place
an
image
or
reuse
an
image.
You
have
the
option
to
enter
in
your
own
alt
text
and,
at
the
very
least
the
default
would
be
used
to
populate
the
fields.
A
There,
the
one
thing
that
gives
me
pause
is
that
pretty
much
anytime,
you
have
like
a
global
versus
override
situation.
It
causes
a
lot
of
confusion
about
which
one
is
being
used
where
and
yeah
I
think
that
that
part
we
may
need
to
work
out
a
little
bit.
A
I'd
also
like
to
hear,
if
there's
any
alternatives
to
this,
because
I
think
that
that's
going
to
be
helpful,
you
know
saving
people
entering
the
same
thing
again,
but
it
will
be
confusing
I
think
when
people
go
to
the
well
if
they
modify
like
one
files,
alt
text
like
it's
not
clear
to
them,
maybe
if
they're
modifying
it
other
places
and
if
they
go
to
the
central
one
and
modify
the
altitext,
it's
also
not
clear
how
how
many
pieces
of
content
that
will
affect
you
know
like
whether
or
not
they
use
the
default
or
whether
or
not
they're,
using
an
override
but
I
I
think
you
know
that
that
I
don't
know
what
it
would
look
like.
D
C
A
You
uncheck
the
box
and
then
it
uses
the
default,
and
now
you
can
change
it
and
that
that
determines
you
know
you
know.
Is
this
used
or
not
and
I
guess
that
probably
would
be
the
status
of
that
checkbox?
A
That
would
probably
need
to
be
a
column
in
the
table.
The
same
table
that
stores
the
alt
and
title.
D
D
A
D
A
But
yeah
there'd
be
another
column
there
and
then,
if
checked
then
that
would
go.
You
know
get
the
alternate
title
from
the
The
Entity.
Instead,
yeah
yeah,
you
know,
let's,
let's
try
it.
It
sounds
good.
A
A
There
is
kind
of
a
question
of
like
how
special
do
you
want
those
fields
to
be
like?
Do
they
come
like?
Are
they
always
there
like?
Can
you
disable
them?
Do
they
have.
C
A
Says
which
field
is
the
alt
field?
Which
field
is
the
title
field,
or
do
we
make
it
not
configurable?
At
all?
You
know.
A
module
like
image
or
file
module
could
declare
that
this
entity
type
bundle
image.
The
file
image
bundle,
file,
entity,
image,
bundle,
it
just
always
has
this
field,
you
know,
and
you
can
you
can
make.
Those
like
a
like
the
the
body
field
essentially
is,
is
one
of
these,
like
special
Fields,
where
it
exists
out
of
box
and
I.
A
Don't
even
think
you
can
delete
it.
It's
just
like
this
field
is
like
always
there
and
just
whether
or
not
you
want
to
add
it
to
your
bundle
or
not,
and
that
makes
it
so
that
it
doesn't
get
the
the
field
prefix
like
the
the
custom
fields
that
you
create
as
user
all
prefixed
with
field
underscore,
but
modules
can
provide
fields
that
are
namespaced
differently
or
not
namespaced
at
all,
like
the
body
field,
so
I
I
would
lean
a
little
bit
towards
that
direction.
C
A
Or
yeah
something
or
alt
attribute
and
title
attribute
or
something.
D
A
And
I
think
that's
fine
if
it's
exclusive
to
image
the
image
media
type,
specifically
yeah
and
people
could
get
them
into
like
some
weird
issues
where
it's
like.
Well,
what
happens
if
they
add
another
image?
A
Bundle
type
you
know
like
I've
seen
sites
that
use
SVG,
for
example,
is
a
different
image
bundle
they
wouldn't
they
might
not
get
the
alt
and
title
fields
and
maybe
for
the
first
iteration.
That's
that's
fine.
A
D
C
C
Something
that
used
to
happen
in
the
triple
issue
too.
That
doesn't
happen
at
backdrop
much
more,
but
I've
done
it
occasionally,
and
that
might
be
helpful
here.
Martin
is
to
update
the
original
issue.
That's
issue.
Somebody
I
think
we
tend
not
to
do
that
in
background.
Drupal
would
do
that
a
lot
and
so
like,
rather
than
have,
somebody
have
to
read
through
the
entire
issue,
to
get
all
the
different
points.
C
If
you
updated
the
either
the
original
image
or
just
wrote
an
image
summary
in
one
of
the
comments
and
then
maybe
linked
to
it
from
the
original.
But
it's
nice
if
somebody
is
coming
to
the
issue
for
the
first
time
and
they
can
sort
of
immediately
jump
to
a
summary
and
not
have
to.
D
Yeah,
okay,
I'll
I'll,
probably
do
yeah
if
I
do
a
new
comment
and
then
I'll
link
to
it
from
there
link
to
it
from
the
top.
So
we
we
don't
lose
all
the
history.
A
Yeah,
okay,
we've
got
about
10
minutes
left,
we've
got
one
more
topic
from
The
Forum
and
that
is
related
to
batcamp.
That's
coming
up.
Batcamp
is
Bay
Area
Drupal
camp.
This
will
be
the
return
to
in
person.
Events
for
BAD,
Camp
I
think
the
last
well
one
year
they
just
canceled
it
and
one
year
it
was
virtual
and
the
third
year
I'm,
not
quite
sure
what
happened.
A
That's
incredible
like
how
long
this
pandemic
has
been
happening
at
this
point,
but
it's
back
in
person
this
year.
My
understanding
was
also
that
the
virtual
aspect
of
it
has
been
minimized,
so
it
thought
that
it
looked
like
it
was
going
to
be
hybrid,
but
now
it's
kind
of
moved
to
being
mostly
in
person.
A
But
let's,
let's
go
back
in
history.
A
little
bit
back.
Batcamp
has
historically
been
very
kind
and
welcoming
to
backdrop
contributors
for
several
years.
We
had
a
backdrop
Summit,
which
was
sometimes
a
half
day,
sometimes
an
all-day
event,
and
sometimes
the
training
as
well
at
BAD
Camp,
and
then
we
also
normally
have
a
couple
of
presentations
that
are
during
the
conference.
Camp
proper.
A
A
lot
of
those
things
are
happening
again.
This
year
we
have
a
couple
of
presenters
that
are
coming
from
community
members
that
are
happening
during
the
conference
itself
and
the
day.
Let's
actually
hang
on
Jen
I'm
just
going
to
pass
this
over
to
you,
as
for
like
the
schedule
for
the
day,
because
there's
both
a
summit
and
a
Sprint
that
are
both
happening.
So
can
you
talk
about
those
sure.
B
So
the
backdrop
Summit
happens
Friday
morning,
9
A.M
to
12
noon,
BAD
Camp
time
Pacific
time,
and
we
currently
have
Zach
Chandler
from
Stanford
who's,
going
to
be
there
probably
around
10
to
give
a
little
talk
about
his
projects,
and
we
can
do
a
couple
of
other
showcases
or
answer
questions
or
whatever
else
as
needed
and
then
after
lunch
I
think
starting
at
one
Irina
is
going
to
be
running
a
Sprint
on
backdrop
or
end
of
Drupal.
7
is
end
of
life
issues
maybe
contribute
stuff
too.
B
We
have
a
spreadsheet
or
a
Google
doc
where
we're
trying
to
figure
out
what
to
work
on
there
and
then
I
did
also
want
to
mention
that
Kevin
Runyan
from
CU
Boulder
is
also
giving
a
talk
about
how
they
chose
to
go
with
Drupal
9,
and
he
thinks
that
they
made
a
mistake
and
should
have
chosen
backdrop
and
so
he's
giving
a
talk
about
how
he
you
know,
regrets
the
decision
that
they've
made
to
go
in
that
direction,
which
is
going
to
be
kind
of
interesting.
B
So
yeah
it'll
be
two
higher
ed
institutions.
Talking
about
backdrop,
one
that's
like
yeah,
it's
great,
the
other
one's
like
oops.
We
should
have
used
it,
so
that
should
be
fun
for
people
to
hear.
A
Yeah,
which
so,
let's
see
it,
says
this,
which
day
is
the
summit
and
which
day
is
the
Sprint
they're.
A
B
C
A
C
I'll
just
add
the
the
Sprint
there's
a
again.
We
talked
about
this
a
little
bit
in
the
break.
I.
Think
arena
is
really
looking
forward
to
really
kind
of
starting
a
longer
term
initiative
on
on
trying
to
improve
the
backdrop
upgrade
process
and
she
my
understanding
that
she
has
a
couple
of
sites
that
are
in.
B
C
Pipeline
and
wants
to
fix
things,
and
maybe
has
some
even
to
have
some
funding,
and
so
this
Sprint
is
kind
of
designed
to
kick
that
off.
I
think
she
was
also
motivated
by
the
fact
that
the
the
softening
relationship
or
the
improving
relationship
between
the
D.A,
the
Drupal
community
and
backdrop
it
since
this
is
a
chance
for
us
to
sort
of
talk
to
them
about
how
we
can
better
work
together
and
that
all
tied
into
this
brand.
But
what
we
need.
C
What
we're
doing
right
now
is
figuring
out
what
what
our
priorities
are
and
what
we
can
do
to
prepare,
not
just
for
this
Sprint,
but
maybe
for
an
extended.
You
know,
effort
to
to
make
the
backdrop
process
easier.
C
She's
identified
one
issue
that
is
this
back
or
upgrade
UI
to
import
a
database
from
Drupal
7
directly
into
backdrop,
is
one
issue
she
wants
to
work
on.
Dr
Beaumont
has
a
proof
of
concept:
module
ready
that
we
can
use,
but
I
think
also
talking
about,
like
the
back
crop,
upgrade
status,
module
for
Drupal,
there's
a
bunch
of
open
issues
on
that
and
those
are
things
which
can
get
better.
A
Yeah
great,
so
my
plan
is
that
I
will
be
participating
in
the
in
the
in-person
Sprint
Irena,
yes,
is
our
organizer.
So
it's
funny
because
she
has
an
agenda
like
personal
one
and
not
like
okay
I
mean
she
also
probably
will
have
an
agenda
for
the
day.
A
I
hope,
which
would
be
great,
but
that's
fine,
I
I
think
that
that
sounds
great
like
if
you
know
if
we
have,
if
we
want
to
have
a
particular
Focus
point
for
the
Sprint
to
you
know,
to
to
work
on
upgrades
in
particular.
Sounds
sounds
great.
A
Yeah
I
see
that
you
know
doc
well
months,
D
to
B,
migrate,
module
triple
to
backdrop.
Migrate,
module
is
potential
starting
points
and
yeah.
That
should
be
fun.
It's
also
kind
of
interesting,
like
I'm,
not
sure
how
many
contributors
will
potentially
get,
but
if
anyone
is
attending
bed
camp
and
they
would
like
to
participate
in
backdrop,
development
or
just
have
some
questions
answered.
I
encourage
you
to
come
to
both
the
summit
and
the
Sprint
day
because,
like
all
Sprint
days
like
you
know,
you
usually
don't
walk
away.
A
Like
the
end
of
the
day.
With
something
saying
we
did
it,
you
know
like
there's,
not
a
release,
usually
there's
rarely
even
a
commit.
You
usually
the
best
thing
that
you
get
out
of.
It
is
the
ideas
and
the
momentum
to
actually
execute
something
after
the
Sprint
has
been
complete.
So
even
if
you're
not
interested
in
doing
this
particular
upgrade
initiative.
A
If
you
are
interested
in
learning
anything
about
backdrop,
development
or
participating
in
any
way
show
up
and
yeah
we'd
be
more
than
happy
to
talk
to
anyone
about
their
particular
interests
or
issues
that
they
they
may
be
facing.
A
So
yeah
this
this
sounds
great
yeah,
we'll
we'll
see
an
online
component
Tim,
maybe
also
like
you
know.
We
can
say
that
you
know
I
I,
don't
quite
know
what
we
should
commit
to
there,
because
usually
the
in-person
aspect
is
so
overwhelming
with
and-
and
you
know-
requires
people's
attention
that
I
don't
think
I
could
like
commit
to
like
saying:
hey,
I'm
gonna
be
reviewing
issues
at
this
time
because
I'm,
that's
not
what
I'm
going
to
be
doing.
C
I
think
I
think
think.
What
we
need,
though,
is
a
greeter.
We
ideally
we'll
have
somebody
commit
to
being
in
a
zoom
room
or
in
a
Jitsu
room
for
the
time
of
the
Sprint,
to
just
sort
of
welcome
people
and
answer
questions
online.
They
don't
have
to
be
a
commitment
core
committee,
I,
don't
think
or
anything
like
that,
but
you're
right.
We
can't
count
on
so
I'm,
not
sure.
C
Yet,
if
I
will
be
in
the
room
or
online,
if
I'm
not
in
the
room,
I
will
volunteer
to
do
that
online,
but
there's
a
good
chance
that
I'm
actually
going
to
get
out
there
and
be
in
the
room.
So
let
me
ideally
we
would
have
somebody
else.
That's
committed
to
being
just
at
least
a
breeder
in
the
room
that
welcome
people
and
answer
questions.
A
Okay,
yeah
that
I
I
love
that
yeah
we've
got
a
couple
of
weeks
to
figure
that
out,
but
not
not
anymore,
so
I.
C
D
C
Of
hang
out
in
the
room
and
talk
to
anybody
that
trims
up,
that's
the
minimum.
We
need
from
you
there's
a
chance
that
Wilbur
might
be
willing
to
do
some
of
that.
But
somebody
else
would
be
helpful
as
well.
A
Yeah,
let's
see
do
we
have,
there
should
be
a
thread
in
meetups
and
events
on
the
Forum
to
discuss
this
I
think
that
would
be.
A
Place
for
it
so
yeah,
because
it's
it's
definitely
a
meet-up,
an
event
so
yeah,
it's
funny
because
yeah
this
just
just
hit
my
radar
like
last
week
that
it's
like.
Oh
this
is
happening
and
then
it
it's
very
quickly.
Turning
into
a
thing
you
know.
A
Yeah
yeah-
that
would
be
great,
okay,
well
we're
all
out
of
time
for
today
again
great
job,
everyone
on
the
123
release.
It
was
a
big
hit
and
yeah
we'll
talk
more
about
124
and
priorities
in
the
next
couple
of
weeks.
Although,
since
we're
talking
about
Bad
Camp,
you
know
the
next
meeting
will
be
during
Bad
Camp,
which
may
occupy
several
people
in
this
room's
time.
A
If
Tim
is
here
here,
I
say
here
because
we're
in
the
Bay
area
as
well
so
yeah
we'll
see
at
one
time
we
did
like
a
live
from
Bad
Camp
meeting,
which
may
end
up
happening,
but
we'll
talk
more
about
that
next
week,
as
we
as
we
get
closer
to
the
event.
So,
okay,
all
right.
Well,
let's
call
it
for
today,
thanks
again
and
we'll
see
everyone
online.