►
From YouTube: Backdrop Weekly - Jan 7th, 2021
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).
B
Okay,
I
didn't
get
the
agenda
open
yet,
but
welcome
everybody
to
the
backdrop
dev
meeting
for
january
7th.
If
you
don't
want
to
be,
we
are
recording
this.
If
you
don't
want
to
be
recorded,
turn
off
your
camera,
but
I
think
we
all
know
that
that
are
here:
let's
go
ahead
and
do
introductions
first,
just
your
name
where
you're
from
and
a
quick
anything
you
want
to
share.
I'm
kim
erickson
saint
paul
tim
coming
to
you
from
deerwood
minnesota.
B
The
deer
were
here
earlier.
I'm
doing
my
quick
deer
check.
I
don't
have
anything
where
we
got
a
release
coming
up
and
I'm
excited
about
that.
A
lot
of
interesting
work
happening
some
of
it
didn't
quite
make
it,
but
but
we'll
be
ready
for
1.19
nate.
You
want
to
go
next.
C
Yeah
I'm
nate
lampton
from
oakland,
california
and
yeah.
We
do
have
some
some
very
interesting
things
to
cover
the
the
things
that
didn't
get
in.
There
were
several
of
them
that
were
super
close
and
we'll
talk
about
those
and
yeah.
I'm
excited
about
some
of
the
ci
improvements
that
we've
got
coming
in
right
now,
so
we'll
be
talking
about
those
two
phil.
Can
you
give
us
an
introduction.
A
Hey
bill
ward
out
of
wichita
kansas,
basically
site
builder,
I'm
here
to
just
kind
of
provide
any
feedback
where
I
feel
like.
I
can
offer
some
assistance.
B
B
B
Nobody
knows
my
apologies
to
early
bird
or
bug,
but
on
the
the
I
thought
it
was
early
bug,
the
the
the
but
the
the
release
note
said
berg
and
we
also
have
pan
zoom
images
by
jen.
Thanks
for
those
I
know
I
there's
some
other
issues
are
interesting
modules.
I
think
coming
in
the
way
that
I've
seen
some
people
working
on.
So
it's
nice
to
see
the
steady
stream
of
contrib
modules
that
continue
to
get
ported.
B
It
looks
like
we
have
a
note
here
to
thank
bw
panda
2
for
his
work
on
tugboat
sandboxes.
That
might
be
old
because
I
know
he'd
done
that
a
while
back,
but
it's
still
very
valuable,
and
I
know
lately
he's
been
doing
a
bunch
of
stuff
on
backdrop
dot
or
I
think.
B
C
The
new
enhancements
there,
I
think,
include
that
he's
setting
up
tugboat
sandboxes
for
the
backdrop
cms.org
sites
themselves,
so
every
pull
request
we
make
against
those
projects
we'll
be
getting
sandboxes.
So
that's
great
progress.
There.
B
Yeah
we've
certainly
talked
about
that
because
there's
a
there's
at
least
one
pr-
that
for
adding
info
to
dot
or
more
information
fields
to
dot
info
files
on
modules,
it's
kind
of
hard
to
test
the
pull
re,
pull
really
or
the
pull
request,
and
I
think
the
tugboat
will
help
with
that.
C
Sure
so
so
feature
freeze
feature.
Freezes
happened
happened
on
january
4th,
which
was
monday
this
this
week,
and
that
means
that
from
here
on
out
for
that's
the
next
eight
days
backdrop
118
will
be
coming
out
on
january.
15Th,
that's
next
friday,
but
for
the
next
week
and
one
day
we
will
no
longer
be
putting
in
new
features,
but
we
can
still
put.
D
C
Bug
fix
bug
fixes,
so
the
117.5
is
the
next
bug
fix
release
that
will
also
be
coming
out
on
january
15th
and,
if
you're
looking
for
something
to
do
between
now
and
the
release
of
january
15th.
Of
course
you
can
work
on
115
or
sorry
1,
19
issues
that
will
be
the
next
version
of
backdrops.
C
That
will
come
out
in
four
months,
but
if
you
want
to
get
something
in
this
next
release
that
is
coming
up
in
the
next
eight
days,
then
putting
your
attention
on
the
117.5
milestone
is
where
we
can
continue
to
put
in
bug
fixes
and
those
will
also
end
up
in
the
118
release.
C
So
we'll
go
over.
The
117.5
bug
fix
releases
issues
that
we've
got
going
on
this
past
week.
We
merged
in
the
civic
crm
views
integration
fix
that
was
related
to
my
sql
8
support.
The
issue
is
4745
that
is
now
merged
in
so
the
next
version
of
backdrop
will
properly
support
database
queries
across
databases
across
databases
again,
so
that
fix
is
now
in.
C
C
Some
issues
that
we
have
been
bringing
up
pretty
regularly
that
haven't
had
a
whole
lot
of
progress,
include
the
site
getting
stuck
in
maintenance
mode,
shoot,
39.56,
a
warning
on
the
max
input,
vars
variable
3824,
removing
the
block
title
for
the
search
block,
search
box,
3476
views
or
behavior,
not
acting
quite
correctly.
3415.
C
C
All
of
those
issues
haven't
received
any
updates
in
the
past
week
or
a
couple
weeks.
Actually
I
think
either
these
issues
need
to
start
getting
some
attention
or
we
should
start
shaking
up
what
it
is
that
we
bring
up
in
our
weekly
calls
every
week,
because
these
same
issues
have
been
dragging
on
for
a
couple
of
months
now
without
a
whole
lot
of
progress.
C
C
B
So
the
front
page
to
home,
paging
core,
it's
issue
2162
and
I'm
bringing
it
up
because
this,
the
last
I
think
you
commented
on
it
nate,
was
that
you
were
a
question
whether
or
not
there
was
consensus
on
whether
or
not
to
do
it
or
not.
We
had
a
pull
request
that
was
rtbc.
B
Peter
took
away
the
rtbc
status
because
there
seemed
to
be
mixed
feelings
about
it.
So
what
I've
been
trying
to
do
this
last
week
is
to
figure
out.
If
there
is
is
consensus
or
you
know
what,
where
the
consensus
it's
it.
This
is
an
odd
issue,
because
a
bunch
of
work
has
already
went
into
changing.
B
We've
already
changed
some
things
from
front
to
home,
and-
and
this
issue
was
kind
of
intended
to
finish
that
work,
so
I
basically
put
some
people
on
the
spot
and
said
if
you
know
you're
not
in
you
know,
if
you
don't
think
this
is
a
great
idea,
are
you
suggesting?
B
Do
we
go
backwards
or
do
we
stay
in
this
intermediate
step,
and
I
think
the
you
know,
peter
in
particular
has
said
that
he's
in
favor
of
this
indigozella,
I
think
had
expressed
some
reservations
but
also
acknowledged
that
the
current
status
is
not
is
the
worst
option
and
I
think,
would
rather
see
us
move
forward
than
not
do
anything.
B
So
I'm
just
wondering
what
we
need
to
do
it.
If
I
understand
correctly,
the
pr
was
ready
to
be
committed
other
than
do.
We
have
enough
consensus
and
right
now
I
don't
know
of
anybody
who's.
C
C
And
there's
been
a
lot
of
new
feedback,
it
looks
like
since
then,
regarding
which
way
we
should
go
with
things.
B
I
think
the
main
feedback
has
been
that
this
is
a
big
deal
for
translators
and
that
we
need
to
be
cautious
about
doing
this
kind
of
thing,
because
a
lot
of
it
requires
changes
in
translation,
but
then
the
follow-up
feedback
is
kind
of
like
we've
already,
you
know
started
this
process
and
we
just
we
had
the
the
needs.
Translation
tag
has
been
added
since
that
feedback
came
out.
C
Yeah
and
yeah
there's
also
some
the
the
trending
direction
is,
is
towards
home
page
correct,
like
that's,
that's
the
suggestion
and
that's
what
the
pull
request
does.
B
Part
of
the
reason
I
bring
this
up
is
that
there
are
a
couple
of
other
issues
related
to
the
home
page
and
it's
like
every
time.
I
see
these
issues
it's
like
well
that
are
about
the
home
page.
It's
like
well,
are
we
talking
about
the
home
page
or
the
front
page,
because
right
now
we're
in
this
limbo?
So
in
some
ways
I
mean
to
me
this
isn't
an
urgent
issue.
C
Api
side,
I'm
sure
that
there's
lots
of
api
things
that
we
can't
easily
touch
you
know
like
there's
the
api
function.
Like
backdrop
is
front
page
the
front
pre-processed
variable,
that's
in
all
of
the
templates
or
is
fronts
maybe
and
then
the
front
placeholder,
with
the
angle
brackets
so
yeah.
This
is.
This
is
again
it's
it's
kind
of
similar
to
actually
tim.
Your
issue
on
raw
html
versus
full
html.
C
It's
like
we
can
change
the
label,
but
we
can't
change
a
lot
of
the
back
end
for
compatibility's
sake
of
it.
B
Well,
there's
no
urgency
in
doing
this
today,
but
I
just
want
to
get
it
on
the
attention
of
a
meeting
because
I
feel,
like
the
the
issue,
is
totally
bogged
down
and
if
anybody
can
provide
any
additional
feedback
or
reasons
you
know
it
was
rtbc
at
one
point
and
the
the
only
objection
there
were
technical
objections
raised.
The
question
was:
do
we
have
consensus
and.
D
D
D
B
But
the
current
status
isn't
that
there
is
nobody
objecting
to
it
right
now
and
the
gazelle
raised
some
concerns,
but
also
acknowledged
that
you
know,
in
her
opinion,
it's
going
to
happen
and
she's
not
standing
in
the
way
so-
and
I
don't
know
of
anybody
else
objecting
yet
that
seems
to
be
the
reason
that
it's
stuck
is
because
there
wasn't
enough
consensus.
So
I
don't
know
if
we
really
need
more
consensus
or
if
it
needs
to
go
to
the
pmc.
A
C
B
Actually,
in
my
opinion,
the
consensus
is
that
the
way
things
are
going
is
the
worst
outcome
that
we're
stuck
with
the
worst
option,
because
we'd
be
happy
with
home
or
we'd,
be
happy
with
front.
But
having
this
ambiguity
about
which
we
should
be
doing
is
the
worst
scenario,
and
that's
where
we're
stopped
right
now
is
we're
stuck
in
not
knowing
whether
it's
the
front
page
of
the
homepage.
B
Okay,
so
to
me
there
are
other
more
stuck
issues
that
maybe
need
to
go
to
the
pmc.
I'm
not
sure
this
one
does,
but
if,
unless
you
know
the
core
committers
feel
like
that
would
be
helpful
to
them,
if,
if
they're
ambiguous
about
it
and
want
us
to
take
it
to
the
pmc.
C
Yeah
things
like
this,
that
are
largely
I
mean,
I'm
not
sure
if
I
would
call
it
totally
subjective,
but
largely.
C
You
know
like
it's
funny
as
as
a
core
committer.
What
I'm
usually
looking
for
is
consistency
and
that
things
are
working
and
that
the
code
is
written
in
a
way
that
matches
everything
else,
but
for
something
that's
like
this
that
it's
like
this
is
not
really
a
code
issue.
This
is
a
this
is
about
terminology
and
you
user
experience
and
stuff
like
that.
It's
really
not
a
core
committer's
purview.
To
like
be
an
expert
in
that
particular
realm.
I
don't
think,
but
maybe
it
is
like
you
know,
as
gatekeepers.
B
C
Yep
and-
and
I
think,
as
long
as
you
felt-
and
I
think
I
would
agree
with
this-
that
you
know
we're
all
on
the
same
page,
there
is
no
opposition,
you
know
the
functionality
is
working.
Okay,
then,
then
that
is
ready
to
be
committed.
You
know
I
mean
everybody.
Is
everybody
is
in
agreement
that
the
pull
request
is
better.
I
think
than
the
current
situation.
B
C
That's
it
okay,
great
one.
One
other
issue
that
is
in
the
1175
milestone
is
automated
code
style
checks
which
isn't
really
an
end
user
feature,
but
it
helps
us
in
doing
our
own
development
on
core
this
year's
32-13.
C
I
spent
some
time
on
it
this
week
and
got
github
actions
working
and
actually
running
code
style
checks
on
pull
requests
and
there's
a
pull
request
there.
That
is
an
example
of
the
code
style
checks
being
run.
I
change
one
file
in
core
and
then
it
causes
it
to
fail
automated
testing,
because
the
code
styles
is
not
up
to
date.
C
This
will
open
up
all
kinds
of
problems
honestly,
because
there's
a
lot
of
inconsistency
where
we're
not
following
code
style
in
a
lot
of
files
right
now
and
I
haven't
been
able
to
get
it
to
run
just
on
the
changed
lines,
it
runs
on
the
changed
files
so
for
something
like
a
views
file
where
views
doesn't
follow
a
lot
of
the
coding
standards
and
naming
conventions,
there's
just
a
lot
of
stuff
that
needs
to
be
updated.
C
Changing
one
line
in
a
views
handler
means
that
you
have
to
change
like
30
lines,
because
a
lot
of
views
code
style
needs
to
be
updated.
I
think
that'll
probably
end
up
being
the
case
for
a
lot
of
files,
that
if
you
change
one
line,
the
code
style
checks
will
run
and
then
you'll
have
to
change
a
whole
bunch
of
lines
so
how
we
want
to
handle.
That
is
going
to
be
kind
of
an
open
question.
C
It
would
be
great
if
we
could
get
code
style
across
the
board,
all
to
be
matching
and,
where
necessary.
Like
add,
you
can
ignore
particular
code
style
rules
but
yeah.
If
we,
if
we
add
in
this
new
feature-
and
it
continues
working
the
way
that
it
does
we'll
need
to
put
forth
some
effort
to
like
go
across
the
whole
code
base
and
try
to
get
as
much
as
of
it
as
we
can
updated
to
match
code
style.
C
So
anyway,
that's
it.
I
could
use
an
some
looking
at
21
or
to
13..
C
We
also
have
a
matching
issue
that
we
need
a
coder
review
module
to
get
updated
to
a
newer
version
of
phpcs
joseph
flatt
filed
a
pull
request
to
get
it
updated.
I
filed
another
pull
request
that
also
gets
it
updated,
but
uses
a
different
approach,
but
both
of
them
will
get
us
to
a
point
where
we
could
start
using
those
rules
and
core
would
then
course
ci
would
then
be
dependent
upon
coder
review
to
maintain
and
update
those
those
rules
as
we
go
forward.
C
Okay,
let's
move
on
so
118
118
is,
of
course
the
the
next
version
it's
coming
out
a
week
from
tomorrow.
There
is
a
preview
release
out
that
came
out
on
tuesday.
You
can
get
it
from
the
backdrop.
Github
release
page
there's
a
tag
up
there
at
the
top
118
dash
preview.
C
C
The
new
features
that
are
in
the
118
preview
are
listed
in
the
release,
notes
of
that
that
project
on
github-
and
I
also
want
to
give
another
shout
out
to
bw
panda
because
he
created
or
set
up
a
release,
notes
tool
that
looks
at
the
milestone
after
the
milestone
has
been
closed
and
automatically
generates
release
notes
now,
so
we
no
longer
have
to
manually
generate
release,
notes,
I'm
so
excited
about
that.
It'll
save
us
like
an
hour.
C
Every
time
we
make
a
release
and
it's
I
also
give
a
shout
out
to
spring
the
spring
framework.
The
the
java
framework
is
where
that
tool
came
from,
and
it's
awesome
like
it
works
really
great.
It's
just
a
really
easy
thing
to
set
up
in
github
actions
that
maps
our
particular
tags
to
categories,
and
then
it
looks
at
the
milestone
and
pulls
out
all
the
issues.
It
just
works
absolutely
perfectly
the
way
that
we
would
want
to
generate
release
notes
it
creates
them
just
the
way
we
would.
C
We
would
want
so
really
great
automation
there
and
I'm
excited
about
having
that
new
tool
for
releases
in
the
future.
Let's
see
next
up
is
just
to
note
that
the
119
milestone
has
been
opened.
C
The
119
milestone
contains
the
issues
that
were
bumped
from
118
and
unfortunately,
that
was
kind
of
a
lot
of
issues
that
didn't
quite
make
it
of
those
the
media
library
exposed
file,
name
filter,
got
bumped,
32
93,
the
advanced
caching
functionality
field
has
visibility,
condition
for
layouts
and
layout
relationships
all
got
bumped
into
the
next
release.
Oh
and
gregory's
combined
the
update
pages
all
into
one
update
page.
So
the
combined
update
pages
and
the
layout
relationships
both
were
so
close
like
we
could
have.
C
We
could
have
rushed
them
and
merged
them
in
anyway,
but
there
was
like
you
know
they
were
they
were
they
hadn't
received
adequate
testing
yet,
and
there
was
still
some
outstanding
feedback
even
on
the
day
of
of
code
freeze.
However,
both
of
them
are
super
close.
We
could
probably
get
them
completed.
C
You
know
within
the
next
week
or
two
and
then
we'll
have
them
ready
for
119.
C
Let's
see,
I
don't
really
have
much
else
to
say
about
the
current
releases.
If
you
want
to
get
something
into
118,
you
really
should
be
looking
at
the
issues.
Tagged
ux,
because
those
are
still
allowed
to
get
in
during
this
code
freeze
period
or
just
work
through
the
bug
fixes
that
are
currently
outstanding,
which
are
actually
tagged
with
the
117.5
milestone.
C
B
B
Unfortunately,
I
didn't
prepare
my
notes.
We,
the
telemetry,
had
been
kind
of
stuck
on
at
least
me
being
able
to
get
in
and
test
the
work
that
that
nate
had
done.
I
was
finally
able
to
do
that.
It
basically
seems
to
be
working,
but
it's
still
unfinished
and
there's
some
pretty.
We
couldn't
get
anything
into
1.18
because
there's
some
sizable
issues
that
need
to
be
resolved
before
we
can
get
this
in.
B
We
debated
whether
or
not
to
try
and
get
just
even
a
non-working,
or
you
know
even
an
disabled
version
of
the
telemetry
module
in
so
that
we
could
better
test
it,
but
I
think
we
decided
there
was
little
value
in
that
and
that
we
can
probably
do
all
the
testing
we
need
without
that.
B
So
I
do
feel
like
we.
We
made
a
little
step
forward.
Probably
my
next
steps
are
to
take
better
notes
on
the
testing
and
and
make
a
checklist
of
what
has
to
happen,
and-
and
we
talked
about
that
again
quite
a
bit
on
saturday.
So,
for
example,
I
think
the
big
decision
we
need.
Some
of
the
big
decisions
that
have
to
be
made
is
like
how
it's
going
to
work
out
of
the
box.
Right,
I
think,
is
this
module.
B
C
B
C
Nope
I
and
well
yes,
actually,
that
we
could
also,
like
the
the
state
of
the
project.
Module
component
seems
like
it's
in
a
place
that
could
already
be
merged
into
the
project,
module
and
could
be
deployed
to
backdrop
cms.org,
and
that
would
make
testing
tremendously
easier.
C
B
C
Yep,
okay,
well
without
luke
here,
to
do
any
update
on
ready
to
wear.
I
think
that
we
can
say
that's
kind
of
it
for
the
initiative
updates.
Do
we
have
anything
just
generally
like
unrelated
q,
a
anything
that
we'd
like
to
discuss
before
we
close
out.
B
I
I'm
just
going
to
mention
that
it's
the
first
of
the
year.
We
talked
briefly
about
this
in
the
the
outreach
meeting
that
last
year
after
the
release,
we
did
some
special
meetings
for
sort
of
goal
setting
for
the
next
year
and
I'd
like
for
us
to
think
about
how
that
went
last
year
and
maybe
have
some
similar
meetings
and
for
this
year.
But
I
don't
know
if
we
need
to
discuss
that
right
now.
Just
start
thinking
about
it
and
get
it
on
our
calendar.
C
Yeah,
can
you
remind
me
when
we
actually
did
those
goal
setting
meetings?
Wasn't
it
two
weeks
after
the
release?
Wasn't
that
when
we
finally
got
together
to.
B
Right
well,
yeah,
and
they
got
postponed
a
little
bit.
I
think
it
might
have
been
early
february
before
they
actually
happened,
but
I
don't
remember
for
sure
I
could
look
that
up,
but
I
would
my
memory
is
that
they
happened
sometime
in
early
february
that
originally
we
scheduled
them,
but
then
didn't
really
publicize
them
and
they
got
bumped.
You
know
so
we
put
out
the
delay
a
little
bit,
but
they
they
did
happen
and
I
think
we
had
pretty
good
attendance.
B
C
Well,
I
guess
we'll
keep
that
in
mind
for
the
upcoming
meetings
and
we
can
continue
to
brainstorm
like
you
know
what
those
those
should
look
like
and
what
the
takeaways
should
be
like
the
action
items
that
we
like,
where
we
document
them
and
sure
how
we're
going
to
organize
you
know
rally
people
to
to
actually
do
the
work.
C
Okay,
yeah
next
week,
will
be
the
day
before
the
release,
but
usually
you
know
like
the
real
rush
has
already
happened
like
feature
freeze
this
past
week.
That
was
the
real
crunch
time
and
probably
what
we
have
in
the
150
or
sorry.
118
preview
is
going
to
be
really
close
to
what
we
have
in
the
118
final
release,
so
yeah
the
next
week
is
not
particularly
a
very
trying
time.
Usually:
okay,
okay!
C
Well
thanks
everybody
for
for
attending
this
meeting,
and
thanks
everybody
out
there
for
watching
and
yeah,
we'll
see
you
guys
next
week.