►
From YouTube: Backdrop Weekly - July 15, 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).
A
Hello
out
there
it's
july
15
2021,
and
this
is
the
backdrop
weekly
development
meeting.
We
get
together
every
week
to
talk
about
priorities
and
possibilities
for
backdrop.
We'll
do
some
quick
introductions.
My
name
is
nate
lampton,
I'm
quick
sketch
on
the
internet
and
I
am
a
core
committer
luke.
Could
you
introduce
yourself
please.
D
Justin
justin,
christopherson
and
denver
colorado
and
I
just
contribute
to
infrastructure
when
I
can.
E
Sure
can
you
hear
me?
Yes,
okay,
cool
hi,
I'm
joseph
flatt
from
las
vegas
nevada.
Although
I
am
currently
in
seattle,
washington
and
I
I
don't
know-
do
back-end
development
and
how
power
I
can.
A
All
right,
thank
you
folks.
So
the
structure
of
these
meetings
is
that
we
solicit
topics
for
discussion
and
then
we
talk
about
them.
We
had
a
shortcoming
this
week
that
I
did
not
post
to
the
forum
the
link
to
the
agenda,
so
we
did
not
get
any
suggestions
from
the
forum.
I
apologize
for
that,
and
so
we
have
fewer
things
than
than
normal
to
discuss.
A
I
guess
maybe
the
pmc
is
also
discussing
it,
but
from
my
perspective,
jen
and
I
have
started
transferring
the
trademark
backdrop
cms
over
to
the
software
freedom
conservancy
they're,
our
fiscal
and
legal
sponsor,
so
that
effectively
is
transferring
the
trademark
from
a
like
a
personal
legal
responsibility
to
a
community
legal
responsibility.
A
So,
instead
of
it
being
a
personal
asset
of
myself
and
gen,
it's
being
moved
into
the
community
arbiter
holder
of
of
the
trademark.
So
the
paperwork
has
begun
on
that.
I'm
I'm
only
seeing
the
paperwork
side
of
things
and
not
the
discussion
side
of
things.
So
that's
coming
out
of
the
pmc,
so
that's
kind
of
exciting
to
get
that
done.
A
We
also
just
need
to
renew
the
trademark
because
it's
been
five
or
six
years
and
united
states
patent
office
requires
that
you
renew
your
trademarks
roughly
that
time
period
every
six
years,
they're
a
little
bit
loose
about
it,
but
they've
started
sending
us
notices,
saying
hey
it's
time
to
renew
your
trademark.
Otherwise,
it
goes
into
a
dormant
status
and
then
other
people
can
claim
the
same
thing
so
so
we're
using
the
opportunity
of
we
need
to
renew
the
trademark.
We
might
as
well
transfer
it
at
the
same
time.
A
Let's
see
contributed
projects,
we
don't
have
any
new
contributed
projects.
This
week
we
do
have
a
lot
of
updates
on
the
community
side
of
things.
However,
that
we
completed
backdrop
live
this
past
weekend,
friday
and
saturday,
there
was
a
global
event
in
which
they're
three
hours
on
three
hours
off
of
presentations
backdrop
live.
This
was
the
third
time
that
we've
hosted.
It
was
another
success
fairly
well
attended.
I
think
in
the
20s
of
people
was
good
for
revenue
collected
a
lot
of
donations.
A
That
was
very
much
appreciated
from
all
of
our
attendees
and
for
those
that
attended.
I
think
that
we
delivered
a
lot
of
value.
I
know
some.
We
got
several
new
community
members
also
who
had
never
participated
in
backdrop.
Otherwise,
and
so
I
think
it
continues
to
show
that
conferences
or
this
online
format
draws
a
different
audience
than
our
normal
development
discussions
and
these
weekly
meetings.
So
a
big
success.
All
around.
A
There
have
been
a
couple
of
requests
for
video
recordings
from
backdrop
live.
However,
the
nature
of
the
conference
is
such
that
the
discussions
are
less
formal
and
less
presentation
driven
and
more
discussion
format,
and
we
also
want
to
allow
people
to
speak
freely
during
those
sessions
to
encourage
discussion.
A
So
in
that
means
that
for
almost
all
sessions
there
are
no
video
recordings
like
we
had.
We
could
have
recorded
them,
but
we
didn't
specifically
to
allow
people
to
be
themselves
and
to
discuss
openly.
There
are
a
couple
of
sessions
that
were
recorded,
however,
the
what's
new
in
backdrop
and
the
backdrop
core
update.
I
know
those
two
sessions
were
recorded.
We
have
not
published
them,
however.
The
events
website
events.backdropscms.org
has
the
capability
of
storing
videos,
so
we
may
publish
them
to
youtube
and
then
and
then
reference
them
from
the
event
site.
A
So,
if
you're
looking
for
videos,
unfortunately,
you
probably
won't
get
video
of
what
it
is
of
a
particular
session,
but
next
time
come
to
backdrop
live
and
then
you
can
participate.
A
Let's
see,
let's
move
on
to
the
progress
report,
infrastructure
wise.
We
have
been
investigating
using
github
actions
for
testing
issue
4753
in
the
court
in
the
core
queue
indigo
zella
has
been
spearheading
an
effort
to
use
github
actions
to
run
our
testing
suite.
A
She
has
found
that
separating
or
splitting
the
runs
on
github
actions
gets
us
comparable
execution
time.
However,
it
needs
to
run
six
operations
in
parallel
instead
of
just
two
like
on
zen
ci,
but
this
continues
to
be
very
promising.
A
Zen
ci
also
can
like
seems
to
be
fighting
us
that,
on
these
pull
requests
to
use
github
actions,
the
tests
are
refusing
to
run
just
like,
but
with
enough
restarts
we're
we're
getting
through
it,
and
I
know
that
that's
a
continuing
problem
on
all
pull
requests
actually
that
the
tests
just
aren't
running
very
consistently.
A
A
Why
that
failure
is
occurring?
Let's
see,
47
53
is
the
main
issue
and
then
51
26
is
the
child
issue
for
a
failure.
That's
happening
every
single
time
on
github
actions
that
doesn't
happen
on
zen
ci
and
we
think
it's
just
a
software
configuration
difference
that
is
actually
pointing
out
an
underlying
bug
in
backdrop
that
we
didn't
know
about
so
we're
fixing
that
underlying
bug,
and
then
it
should
make
the
tests
fast
on
github
actions.
E
E
E
And
I
also
talk,
I
put
a
comment
on
your
pull
request
that
we
we
actually
have
to
check,
if
not
match
separately
from,
if
modified,
since,
because
the
default
behavior
is
that,
if
known
match
overrides,
if
modified
sense,.
A
Got
it
okay,
great
yeah,
so
you've
summed
up
the
problem
there,
joseph
that
backdrop
basically
isn't
following
the
http
spec
properly,
when
certain
cache
headers
are
passed
in
backdrop
returns
a
different
behavior
than
a
proxy
that
does
follow
the
http
spec
so
effectively.
A
What
has
surfaced
is
a
legitimate
bug
in
backdrops
cache
handling
that
we're
not
handling
these
conditional
cache
headers
correctly.
So
the
solution
is
that
we
need
to
make
backdrop
behave
like
the
proxy
and
then
it
doesn't
matter
if
the
proxy
is
in
front
of
it
or
not,
because
you'll
get
the
same
results
so
anyway,
it's
it's
a
nice
find
I'm
glad
that
we're
solving
it
and
we
should
get
better
cash
ability
out
of
it.
As
a
nice
bonus.
E
An
interesting
tidbit
is
that
the
these
cash
headers
are
actually
wrong
on
purpose
to
work
around
a
bug
in
firefox
that
was
filed
17
years
ago
and.
A
Fixed
12
years
ago,
I
also
saw
that
yeah
that
our
code
comments
are
like
this
intentionally.
Does
this
thing
because
of
this
bug
in
firefox
that
was
like
yeah
totally
ancient
yeah,
which
would
also
be
nice?
If
we
could,
I
didn't
deal
with
the
code
comments
updates,
but
yeah
it
wouldn't
hurt.
If
we
went
through
and
updated
the
code
comments
to
just
remove
that
section
on
like
this
ancient
bug
that
no
longer
applies.
A
It
would
also
be
nice
if
you
know
the
workarounds
that
we're
doing.
I
think
that
there's
other
good
reasons.
I
think
that
that
particular
code
comment
was
around
the
way
that
we
set
e
tags,
an
etac
header
which
is
used
for
caching,
there's
still
good
reasons
why
we
should
set
the
etag
the
way
that
we're
doing
it
right
now,
but
that
bug
in
firefox
is
not
one
of
them.
A
Okay-
let's
see,
I
don't
have
any
items
from
119.2
to
discuss
today
and
the
1.20
the
next
minor
version
that
will
include
new
features.
A
Also
doesn't
have
a
lot
of
updates.
We've
got
the
media
library
dialog
issue
3293
that
continues
to
need
some
code
review
and
some
further
testing
and
that's
kind
of
it.
We
already
merged
in
bug
folders
layouts
code,
abstraction
to
make
it
so
that
node,
module
and
layout
module
are
now
decoupled
from
each
other
issue.
5067.
A
And
we
don't
have
a
lot
of
other
items
slated
for
1.20
as
of
yet
at
backdrop
live.
I
did
outline
some
features
that
I
think
that
we
should
prioritize,
maybe
not
necessarily
for
1.20,
but
in
the
in
the
future.
That
included
it's
going
to
be
hard
for
me
to
remember
off
the
top
of
my
head,
but
I
know
automatic
updates
was
in
there
telemetry.
A
Memory
reference
module.
A
A
Oh
and
recipes
that
was
it
yeah
that
recipe
issue
3763,
I'm
sorry
which
actually
links
over
to
a
bug,
issue
3224.
A
the
module
config
is
not
synced
on
install,
has
a
pull
request
that
very
effectively
solves
the
main
problem,
but
we
need
test
coverage
for
it.
That's
the
big
hold
up
on
that
issue,
so
out
of
anything
that
we
can
deliver
for
for
1.20.
This
seems
like
it's
a
very
obvious
candidate.
It's
a
very
small
fix,
a
substantial
increase
in
the
capabilities
it
grants
us
and
it
is
only
blocked
on
test
writing
so
issue
3224.
A
I'm
going
to
wrap
back
around
to
telemetry
because
that's
a
initiative
that
is
potentially
across
multiple
releases.
A
The
telemetry
issue
has
been
moving
forward
quite
a
lot
in
the
past
week,
so
the
core
issue
is
issue
285
and
we
have
new
new
poll
requests
up
that
include
changes
to
the
project
module
and
to
the
core
module.
A
That
would
be
bundled
with
backdrop,
so
the
core
module
is
called
simply
telemetry
and
then
there's
the
module
that
would
run
on
the
server
side
on
backdrop,
cms.org
called
project
telemetry
as
it's
integrated
with
project
module,
and
so
the
new
changes
that
we
have
ready
are
mostly
on
the
server
side
that
we
can
now
configure
per
project
like
backdrop
core,
as
a
project
on
backdrop
cms.org,
whether
or
not
telemetry
is
allowed
to
be
collected
for
that
project,
and
then
what
keys
are
specifically
allowed
to
be
stored
on
backdrop,
cms.org?
A
That
includes
things
like
the
php
version,
my
sql
version
server
os
and
then
other
things
as
we
start
collecting
them.
We'll
specifically
allow
certain
keys
to
be
stored
on
backdropcms.org
and
then
that
data
is
allowed
that's
to
prevent
the
future
problem
of.
If
we
start
allowing
telemetry
for
contributed
modules
that
we'll
need
to
specifically
audit
what
data
contributed,
modules
are
collecting,
because
we
have
a
legal
responsibility
and
a
privacy
responsibility
to
not
store
personal
information
on
backdrop
cms.org.
A
So
as
we
roll
out
telemetry
in
the
future
to
contributed
modules,
we'll
need
to
set
up
a
process
for
I
would
like
to
collect
telemetry
data
on
backdrop
cms.org,
and
then
we
check
the
module,
and
then
we
specifically
allow
that
data
on
a
per
project
level
to
be
collected
and
reported
on
backdrop,
cms.org.
A
A
A
It
also
gives
us
the
opportunity
to
provide
a
human
readable
label
rather
than
these
machine
ones,
and
then
we
also
need
to
specify
when
this
data
is
collected,
how
should
it
be
aggregated
and
displayed
to
users
on
the
front
end,
and
so,
in
the
case
of
php
version,
we're
collecting
the
full
php
version,
strength
from
every
installation,
but
when
we
display
it,
we
want
to
aggregate
those
into
a
larger
number.
So
all
php
7.4
should
be
considered
one
collection
in
all
of
php
7.2,
whether
it's
7.2.10
or
11
or
12
or
whatever.
A
A
So
this
functionality
serves
multiple
purposes
that
not
only
does
it
filter
what
data
gets
stored
on
backdrop
cms.org,
but
then
it
tells
backdropcms.org
when
you're
displaying
this
data,
how
it
should
be
aggregated.
A
So
that's
coming
along
really
well.
The
the
next
steps
here
is
that
we
need
additional
testing.
We
need
a
technical
review
of
all
of
the
code.
There's
two
poll
requests
that
bw
panda
linked
out
to
here.
We
need
to
and
possibly
probably
enable
the
telemetry
module
in
the
standard
profile,
probably
with
a
checkbox
that
says
you
know,
do
you
want
to
collect
information,
and
then
presentation
wise,
like
this-
could
happen
afterwards.
A
Add
some
better
display
of
this
information,
like
probably
in
a
chart
format
rather
than
in
a
table
format.
The
most
obvious
candidate
for
these
initial
ones
would
be
something
like
a
pie
chart
because
these
all
add
up
to
100
currently,
but
that's
all
just
icing
on
the
cake
functionality
wise.
A
This
is
really
coming
along
to
the
point
that
we
could
actually
start
experimenting
with
it
on
backdrop
cms.org
and
on
perhaps
the
1.20,
sorry,
the
1.x
branch
of
backdrop
itself,
but
we
still
have
some
more
code
review,
more
testing
to
be
done,
so
that
actually
has
been
coming
along
very
nicely.
So
I
hope
that
we'll
continue
to
get
some
more
feedback
on
that
and
we'll
see
if
we
can
start
moving
that
into
into
the
core
repository.
A
That's
really
all
I've
got
for
today.
There's
one
last
topic
that
I
don't
want
to
exclude
again,
and
that
is
that
it
was
raised
two
meetings
ago.
I
think
bw
panda
filed
an
issue
about
discussing
the
purpose
of
these
meetings,
not
the
format,
because
we've
been
doing
a
lot
of
details
about
the
format,
but
the
actual
purpose
like
what
is
the
audience
for
this
meeting?
A
What
is
it
that
we
should
be
spending
our
time
doing
while
we're
here,
and
I
haven't
had
time
to
prepare
additional
thoughts
on
that
topic?
Let
me
find
the
issue
where
peter
has
discussed
a
little
bit,
but
if
you
folks
present
have
any
thoughts
about
purpose
of
the
meeting,
I'd
love
to
hear
them.
A
So
peter
says
what
is
the
purpose
of
the
weekly
dev
meeting
some
thoughts
that
come
to
mind,
give
the
wider
community
an
update
on
how
backdrop
development
is
progressing,
solve
problems,
unblock
issues,
revolve,
review,
pull
requests,
etc,
decide
where
effort
should
be
focused
for
upcoming
bug
and
minor
releases
yeah,
which
I
would
agree
like
that's
what
we
do.
I
hope,
like
that's,
that's
my
understanding
of
this
meeting
as
well.
A
But,
like
I
said,
I'm
not
totally
prepared
to
cover
this
because
I
haven't
read
the
full
issue,
so
I
don't
want
to
wing
it
all
and
not
give
it
the
the
time
and
credit
that
it
deserves.
So
potentially,
if
you
guys
don't
have
anything
else
well,
luke
do
you
have
anything
you
want
to
add
nope.
B
A
A
Agreed
so
I'm
just
going
to
reference
that
issue
backdrop
bops
slash
backdrop:
community
issue,
number
six.
A
Yeah
yeah,
I
put
it
into
the
into
the
zoom
chat,
I'll
put
it
in
the
agenda
as
well,
but
yeah.
I
I'm
not
prepared
to
discuss
that
yet,
and
so
I
think
that
I
need
to
read
the
full
issue
before
I
actually
provide
any
thoughts
and
feedback
on.
It
might
also
be
good.
I
know
some
of
our
community
members,
jen
and
tim,
for
example-
aren't
able
to
be
at
this
meeting
today,
because
they're
participating
in
an
event
the
open
source
day
event.
A
So
it
would
also
be
good
to
have
their
presence
to
discuss
so
with
that,
I
think
we'll
call
it
a
meeting
nice
and
short.
I
cancel
that
robert.
You
would
like
to
add
something
I'd
like
to.
A
It's
a
great
question
and
one
that
I
would
like
information
on
as
well.
I'm
not
fully
in
touch
with
how
the
pmc
is
progressing
with
that,
but
last
I
checked
it.
It
stays
kind
of
where
we
we
haven't
moved
since
the
last
update,
which
was
we
were
waiting
for
the
90-day
30-day
waiting
period
before
the
domain
could
be
transferred
a
second
time
because
it
was
just
transferred
into
the
ownership
of
again.
I
remember.
I
should
definitely
remember
this
alan
thank
you.
A
It
was
transferred
into
allen's
ownership,
but
then
we
want
to
transfer
it
a
second
time
and
there
was
a
waiting
period
so
yeah
alan
melz,
so
alan
is
still,
as
far
as
I
know
like
willing
to
transfer
the
the
domain
name
as
soon
as
we
ask
for
it.
But
the
thing
is
that
we
haven't
gone
back
and
said:
hey
the
waiting
period
is
over.
Can
we
transfer
this
domain
name
into
our
ownership?
So
that's
where
we
are
alan
is
still
the
owner
of
backdrop.org
he's
still
willing
to
transfer
it.
A
We
just
haven't
scheduled
the
time
to
do
it,
because
it
it
is
the
sort
of
thing
that
we
probably
need
to
meet
up
real
time
and
do
the
whole
release
the
lock
transfer.
The
thing
accept
the
lock
and
then
go
through
all
of
the
the
process
all
in
one
fell
swoop.
So
I
don't
think
that
that
will
be
a
long
process.
But
then,
once
it's
in
the
ownership
of
the
backdrop
community
under
namecheap,
where
all
of
our
other
domain
names
are,
then
we
still
have
the
discussion
about.
A
A
I
am
looking
forward
to
that,
though.
I
would
like
that.
I
know
that
it's
like
a
a
slip
almost
every
time.
We
refer
to
the
website,
we
actually
say
backdrop.org
and
right
now.
It's
still
backdrop:
cms.org,
there's
a
nice
redirect
now,
if
you
type
backdrop.org
it
redirects
to
backupcms.org,
but
I
hope
my
personal
hope
is
that
we'll
be
able
to
use
that
in
the
future.
A
Okay,
anything
else,
okay.
Well,
thank
you
folks
for
participating
in
today's
meeting.
Thank
you.
Everyone
out
there
for
watching.