►
From YouTube: 2022/01/13 Backdrop Weekly Dev 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,
everyone:
it
is
january,
13
2022,
and
this
is
the
backdrop
weekly
developer
call.
We
get
together
every
week
to
talk
about
the
latest
priorities
and
happenings
in
backdrop
core
and
other
peripheral
things.
So
backdrop
121
comes
out
day
after
tomorrow.
So
that's
going
to
be
our
big
topic
for
today.
What
kinds
of
things
we
still
have
yet
to
do
and
the
things
that
we've
gotten
done
in
the
past
week
or
so
we'll
get
some
quick
introductions
to
kick
off.
A
My
name
is
nate
lampton,
I'm
quick
sketch
on
the
internet,
a
court
committer
and
I
am
coming
from
oakland
california,
let's
go
to
tim
and
then
to
robert.
A
Great
joseph
and
then
finally
bw
panda.
A
All
right,
then,
finally,
bw
panda.
A
All
right:
well,
thank
you.
Everybody,
let's
see
before
we
get
deep
into
the
agenda.
Let's
do
the
contributed
project
and
community
update
jen.
Do
you
wanna
give
us
the
rundown.
C
Sure
so
we
have
three
four
new
modules
this
week,
site
alert,
use,
calc,
distinct
and
rename
admin
paths.
I
guess
that's
three.
A
A
Okay,
great
so,
let's
see
we
have
a
forum
post
from
forum.backdropcms.org,
it's
posted
every
week
for
people
to
accumulate
any
points
of
discussion
if
they
think
of
something
that
they'd
like
us
to
discuss
during
these
meetings,
they
can
post
a
comment
on
that
forum
post
the
item
raised
today.
One
of
them
has
already
been
discussed
in
the
previous
meeting
disabling
comments
across
an
entire
content
type
that
was
in
the
ux
meeting.
The
only
other
topic
that
was
raised
was
by
indigozella,
which
is
php
8.1
support.
That's
issue,
53.98.
A
A
I
don't
think
that
she
or
gregory
have
flagged
anything
says
like
this
looks
like
it's
almost
done,
except
for
x
or
y.
It
looks
to
me
like
they're,
saying
everything
should
be
ready
to
go.
So
that's
pretty
exciting
issue.
3879
could
use,
could
use
some
analysis.
A
How
safe
this
is
it's
another
thing.
I
guess
that
needs
to
be
evaluated.
A
If,
if
this
looks
safe
for
us
to
do
as
soon
as
possible,
looks
pretty
safe,
just
taking
a
look
at
it
initially,
we
could
still
get
that
in,
even
though
the
releases
day
after
tomorrow,
I
might
feel
a
little
bit
more
comfortable
waiting
on
it
if
it
turns
out
that
it's
possibly
risky
but
anyway,
it
looks
like
this
is
a
great
item
for
us
to
to
take
a
look
at
53.98.
A
It's
not
in
a
milestone
yet
so
needs
to
simply
be
found.
A
All
right,
let's
see
I've,
got
the
item
in
here
about
phpcs.
I
think
that
this
has
been
stalled.
Yes
for
a
while
now
issue,
52
50
45.
be
great.
If
we
can
get
some
focus
back
on
that
at
some
point
could
help
with
our
code
reviewing
process
quite
a
bit
having
automated
code
checks,
it's
issue
52
45,
but
there's
no
updates.
There
tim.
I
think
you
might
have
just
put
something
in
the
agenda
here
about
office
hours.
You
want
to
say
a
word
or
two
about
that.
B
B
B
We've
had
people
every
week,
that's
that's
too
too
self-deprecating
people
have
been
showing
up
and
we're
gonna,
I'm
gonna
keep
that
on
the
schedule
for
the
next
quarter
and
and
then
we'll
keep
it
on
the
schedule
for
the
next
quarter.
After
that,
okay.
A
Thank
you,
wilbur
yeah,
it's
funny
because
wednesdays
are
typically
one
of
my
most
productive
days
for
doing
backdrop,
but
I'm
not
in
the
habit
of
joining
in
the
meeting.
I
just
do
it
quietly
all.
A
But
yeah
I'd
like
I'd
like
to
personally
start
leveraging
that
that
opportunity
that's
been
put
forward
more
frequently.
B
B
C
A
Or
indigo
zala,
who
is
aggressively
removing
browser
cookies,
at
least
from
from
backdrop,
because
one
of
the
changes
that
we
got
in
just
recently
was
the
removal
of
the
show
hide
columns,
show
hide
weights
cookie.
So
that's
like
the
only
front-end
cookie
that
backdrop
tends
to
set
and
that
cookie
has
been
removed
and
replaced
with.
A
Yeah
yeah,
I
really
don't
like
show
hide
table
weights
in
the
first
place,
but
it's
nice
that
it,
it
is
now
no
longer
causing
like
deprecated
cookie,
will
not
work
warnings
in
your
browser,
so
great
enhancement.
A
Okay,
let's
see
we
have
121,
as
I
mentioned
comes
out
day
after
tomorrow.
I
don't
really
have
a
lot
to
say
about
items
that
we're
still
working
on
other
than
we
made
a
a
lot
of
progress
in
the
past
week.
I
think
we've
gotten
in
like
around
15
issues
or
so
we're
really
working
through
the
one
dot.
What
is
this
sorry?
The
1.20.4
milestone
is
where
a
lot
of
the
high
priority
bug
fixes
are
going.
A
Let's
check
out
that
milestone
real
quick.
There
are
currently
32
open
issues
still
in
that
milestone,
but
there
are
22
closed
issues
in
that
milestone
because
we've
been
making
a
lot
of
progress
there
recently.
A
Also
the
the
rtbc
list
is
still
got
quite
a
few
items
in
it.
I
think
it
is
13
13
items
in
the
rtbcq,
so
we're
continuing
to
work
through
those.
A
We
are
trying
to
be
a
little
bit
more
conservative
right
now.
Considering
our
testing
window
of
people
working
on
the
latest
version
of
core
is
getting
really
really
short,
but
any
of
these
fixes
that
are
well
tested
and
have
a
low
chance
of
a
negative
impact
or
we're
going
to
continue
getting
these
changes
in
as
they
become
ready.
A
It's
very
exciting
lots,
lots
and
lots
of
things,
one
that
gets
a
special
call
out.
I
think,
is
this
issue
4441,
removing
all
instances
of
blacklist
and
whitelist
from
core.
This
is
going
into
1.21
only
actually
because
it
does
have
some
minor
impacts.
A
C
Sure
so
there
are
a
couple
of
issues
for
backdrop
core,
there's
this
one
and
then
there's
a
another
one
about
removing
master
slave
terminology
that
are
just
you
know,
there's
a
lot
of
words
that
we
use
in
the
tech
world
that
we've
been
using
for
a
long
time
without
thinking
about
and
public
implications
of
them
and
how
they
might
make
some
people
feel-
and
this
gives
us
a
chance
to
sort
of
wipe
the
slate
clean
and
replace
words
with
more
accurate
descriptions
of
what
they
do.
C
So
a
white
list
has
been
replaced
with
allow
list
when
it's
used
as
a
noun
and
allow
is
a
verb
and
blacklist
has
been
replaced
with
denying
list
or
deny
when
it's
used
in
core,
so
just
some
clean
up
there
on
old
stuff
that
has
just
you
know,
been
around
for
forever
and
gives
us
a
chance
to
do
better.
Now
that
we're
aware
of
it.
A
Does
this
have
any
compatibility
concerns.
C
I
don't
think
so.
There
is
a
function,
there's
a
drupal
function.
That
was,
I
forget,
which
one
it
was.
It
was
something
like
drupal
check,
whitelist
or
something
like
that
where
we
now
have
a
couple
of
there's
like
another
backwards,
compatible
wrapper
in
there.
C
I
think,
and
then
we
have
one
placing
core
where
we
had
a
setting
in
that
was
set
in
the
settings
file
that
we
had
to
check
for
both
the
old
setting
in
the
new
setting
to
make
sure
that
if
there
was
an
old
setting
with
a
white
list
name,
we
were
maintaining
that
name.
So
there's
a
couple
of
places
where
we
haven't
completely
gotten
rid
of
it
in
order
to
keep
the
backwards
compatibility
in,
but
there's
we're
moving
2.0
marked
on
there
so
that
we
can
get
rid
of
those.
The
next
major
version.
A
Interesting
also
kind
of
interesting.
A
Allow
list,
and
what
is
it,
allow
list
deny
list
denialist.
C
We
decided
not
to
use
block
because
block
has
a
specific
meaning
for
user
accounts,
and
so
we
thought
it
would
be
good
to
use
something
that
didn't
already
have
a
meaning.
In
dribbling
backdrop,.
A
Yeah,
I
I
deny
list
also
is
a
little
easier
to
say
in
my
opinion,
but
allow
list
is
a
la
la
la
la.
A
A
A
Right
away,
I
think,
just
generally
speaking,
yeah
we'll
just
say
it
again,
that
our
focus
is
on
bug
fixes
the
release
is
in
two
days.
A
Everything
seems
to
be
on
schedule
and
right
now
we're
in
a
in
a
way
kind
of
like
the
calm
before
the
storm,
because
there's
a
finite
amount
of
change
that
we
can
actually
implement,
and
our
focus
right
now
is
on
is
on
the
release.
1.22,
the
great
sorry,
our
numbers
are
getting
so
big,
yeah
1-22
the
release
that
will
be
coming
out
after
this
one
will
start
working
on
planning
meetings
and
road
mapping.
A
A
I
don't
have
any
anything
else
to
really
cover
today.
It
seems
odd.
I've
only
been
talking
for
10
minutes
go
ahead.
Tim.
B
So
often
at
this
stage
in
the
cycle,
I'm
trying
to
figure
out
what
we
can
still
squeeze
in,
but
it's
this
this
this
release
cycle.
I
just
feel
like
there's
so
much.
That's
already
went
in
and
I'm
just
rooting
for
what
what's
already
there
in
the
queue
that
needs
to
be
reviewed.
But
what
I
wanted
to
raise
was
we
talked
a
little
bit
about
this
in
the
outreach
meeting.
The
release
in
two
days
is
an
outreach
pr
opportunity.
B
B
But
is
there
anything
we
can
do
social
media
wise
and
I'd
like
to
take
one
more
stab
if
anybody
thought
of
anything
since
last
week,
I
could
help
facilitate
that.
I
don't
know
the
only
the
only
I
threw
out
the
idea
like
to
ask
people
to
send
us
screenshots
or
something
of
their
their
backdrop
sites
on
our
birthday,
but
I'm
not
excited,
I'm
not
that
excited
about
that.
C
I
know
that
there
are
some
high-profile
sites
that
are
switching
to
backdrop
soon-ish
and
are
starting
pr
around
that
process.
I
don't
know
if
they're
going
to
be
ready
to
make
those
announcements
on
the
15th,
but
I
might
reach
out
and
find
out
if
that's
possible,
because
that
could
be
good
too.
That
would
sort
of
all
coordinate
the
release
in
the
birthday
and
everything.
B
B
A
We
could
make
requests
for
fan,
art.
A
We
could
I
mean
this,
is
this
is
less
technical?
We
could
ask
people
about
to
post
their
favorite
dragon
related
story.
A
Or
or
post
dragon
themed
birthday,
cakes.
A
B
Okay,
well
thanks:
we
still
got
48.
B
I
mean
I
liked
your
idea,
the
direction
your
ideas
are
going:
nate
they're,
but
they're.
Not
I
don't
know,
I'm
not.
A
Yeah
they're
not
on
brand
necessarily
or
not
they're,
fine.
B
Well,
like
draken
related
stories
or
fan
art,
both
I
just
think
are,
might
be
too
much
work
quickly.
Like
you
know,
they
did
say
you
come
up
with
something
in
48
hours,
maybe,
but
I
like
the
playfulness
of
them
and
just
sort
of
the
fondness
of
them.
I'm
just
not
sure
how
to
implement
them.
This
quickly.
C
Could
do
is
because
drupal
7
end
of
life
is
coming
up.
We
can
ask
people
who
have
backed
up
sites
for
screenshots.
We
could
also
ask
people
who
don't
yet
have
backdrop
sites
if
they're
thinking
of
moving
to
backdrop
and
sort
of
like
prompt
people
and
be
like
hey
today
is
backed
up
seventh
birthday
who's
going
to
be
adopting
backdrop
this
year.
A
C
So
yeah,
and
that
way
we
could
solicit
like
links
to
drupal
7
sites,
or
you
know,
people
are
doing
new
sites
or
what
have
you
in
addition
to
screenshots
of
existing
sites?
I
don't
know
here's
a
couple
of
those
ideas
like
show
us.
Your
current
sites
show
us
your
coming
soon
sites
describe.
B
C
A
All
right
any
other
topics
I
scroll
down
to
the
bottom
of
our
agenda,
and
I
see
we
have
the
initiatives
down
there
at
the
very
bottom
that
I
don't
normally
scroll
down
to,
because
most
devices
come
to
come
to
a
ramp,
but
telemetry
is
down
there
and
it
might
be
worth
mentioning
telemetry
things
that
are
happening
because
that
that's
affecting
the
release,
somewhat
telemetry
module,
got
enabled
in
1.21.
A
The
release
that
will
be
downloaded
out
of
the
box
doesn't
affect
existing
sites
still,
but
we're
having
funny
repercussions
from
doing
that.
That
telemetry,
because
it's
now
turned
on,
is
being
turned
on
on
demo
sandboxes
when
you
spend
them
up
on
backdrop,
cms.org
they're
being
turned
on
on
sandboxes
when
you
get
a
pull
request,
sandbox
and
they're.
Also,
it's
also
turned
on
when
we
run
the
tests,
all
of
which
is
causing
a
lot
of
artificial
inflation
in
the
telemetry
data.
A
So
we've
been
working
to
solve
those
problems,
doc
walmart
filed
a
pull
request
to
disable
it
in
sandboxes
and
then
gregory
and
the
godzilla
work
together
to
disable
its
during
test
runs
based
on
the
work
that
document
did
to
disable
it.
In
sandboxes,
so
we're
closing
in
on
fixing
those
that
the
skewing
of
data
problems
there.
A
Both
of
those
changes
are
already
merged
and
I
think
telemetry
data
only
persists
for
about
24
hours,
so
we're
hoping
by
tomorrow.
Our
telemetry
data
will
come
back
down
to
real
real
levels.
Again,
oh,
and
we
also
added
web
server
as
another
tracking
data
point.
So
now
we're
collecting
four
pieces
of
data,
which
I
know
is
that
we're
still,
we
still
have
a
lot
of
other
things
that
we
could
potentially
be
collecting.
But
now
it's
web
server
operating
server
operating
system,
php
version
and
database
version.
A
My
sql
version
so
still
lots
more
to
collect
but
yeah
definitely
moving
along.
A
All
right,
then,
I
don't
think
there's
anything
else
for
this
week,
so
maybe
we'll
call
it
a
meeting
thanks
again,
everyone
for
all
of
the
great
work.
There's
a
lot
of
momentum,
a
lot
of
great
things
happening,
I'm
hoping
just
maybe
this
is
speaking
for
myself
that
maybe
we'll
be
able
to
keep
momentum
after
with
the
release,
the
two
that
would,
because
we've
got
so
much
going
right
now.
A
I
kind
of
feel
like
there's
going
to
be
at
the
very
least,
a
little
long
tail
here
of
like
of
things
that
we
just
will
need
to
keep
wrapping
up
post
release
as
well.
A
So
that's
it
thanks
folks
for
for
being
here
today
and
thanks
to
those
people
that
are
out
there,
that
watch
these
meetings
and
thanks
everyone
for
all
of
their
hard
work
on
backdrop.
This
weekend
always.