►
From YouTube: Backdrop Weekly - Feb 25th 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
My
name
is
jen
lampton,
I'm
joining
from
oakland
california,
where
it's
sunny
and
beautiful
outside
and
I'd
like
to
turn
it
over
to
him.
B
My
name
is
tim
erickson,
st
paul
tim,
I'm
in
deerwood
minnesota,
and
I
frequently
give
the
wildlife
report
outside
my
window
and
it's
just
been
a
really
boring.
B
Today
so
yeah
and
a
lot
of
things
going
on
diverse
stuff
in
the
community,
I
haven't
been
in
the
issue
too
as
much
lately,
but
I've
got
a
lot
of
backdrop
projects
I'm
working
on.
B
D
Hi,
I'm
greg
usually
in
australia,
but
now
joining
from
greece
lately
haven't
been
as
active
as
I
used
to
be
in
the
queue
I'm
trying
to
catch
up
every
week,
since
once
I
get
motivated
but
yeah,
I'm
all
constantly
interested
in
anything
related
to
backdrop,
and
any
way
that
I
can
know
I'm
trying
to
keep
up
with
you
guys
and
the
rest
of
the
community
passing
it
on
to
terry.
E
Hi,
I'm
terry
erickson,
I'm
tim's
sister,
which
makes
me
st
paul
terry.
I'm
a
strategic
improvement
consultant
actually
a
structural
engineer
who
did
building
design,
but
I'm
hanging
out
with
a
lot
of
scrum
masters
these
days
and
what
we're
trying
to
do
is
learn
from
a
lot
of
different
industries
on
how
to
improve
our
industries.
So
I'm
learning
from
you
guys
and
I'll
try
to
share
things
as
well.
F
I'm
nate
lampton
from
oakland,
california,
I'm
a
court
committer
and
I'm
I'm
kind
of
joining
the
refrain
here
of
yeah.
There's
a
lot
happening
that
I'm
having
trouble
keeping
tabs
on
with
the
time
available.
There's
a
huge
amount
of
work.
That's
been
going
on
and
we'll
give
you
guys
a
brief
update
on
that
and
I'll
try
to
keep
myself
from
being
the
bottleneck
on
some
of
these
items.
So,
let's
go
to
justin.
J
Yeah
just
checking
in
to
see
what's
happening
in
backdrop
world
and
lately
I've
been
working
on
the
backdrop
console
module
and
doing
some
stuff
there
so
yeah.
That's
it.
A
All
right,
I
think,
that's
everyone
so
exciting
news
from
the
project
management
committee
this
week,
there's
been
a
lot
of
activities
since
jack
returned,
which
we
are
thrilled
about
and
tim's
been
making
a
bunch
of
noise
there
too
trying
to
get
us
on
our
toes
and
back
in
action,
which
is
great.
This
past
week
we
officially
passed
the
vote
to
transfer
the
backdrop
trademark
to
the
sf.
Suffers
freedom
conservancy
to
hold
it
for
us,
so
I've
bothered
them
a
lot
about
it.
A
A
Sure
so
me
and
I
registered
the
trademark
in
our
names
five
or
so
years
ago,
when
we
originally
got
it
and
it
comes
up
for
renewal,
I
think
every
two
years
or
something
and
two
years
ago
we
when
it
came
up
from
normal
like
should
we
figure
out
how
to
transfer
this
thing?
Oh
that
sounds
hard
skip,
and
then
this
year
it
came
with
renewal
again
and
we're
like
oh
well,
now
that
we
have
the
conservancy
to
help
us
we're
just
gonna,
send
it
to
them.
A
Instead,
so
we
started
that
process
and
then
we're
like
hold
on.
We
need
an
official
pmc
vote.
We
kicked
it
to
the
pmc,
the
pmc
had
questions.
We
kicked
the
questions
back
to
the
pmc
and
everything
sort
of
ground
to
a
halt
until
we
were
able
to
get
an
answer
from
them
on
what
it
exactly
meant
to
have
the
software
freedom
conservancy
hold
our
trademark.
A
What
happens
if
we
have
problems
with
the
conservancy
in
the
future,
all
of
that
stuff,
and
we
got
some
great
answers
back
from
them,
which
we
will
write
a
blog
post
to
put
it
all
in
for
anyone
else.
In
the
community
who's
concerned,
about
those
same
things,
to
just
sort
of
explain
what
it
means
for
them
to
be
holding
this
on
behalf
of
the
community
and.
B
And
can
you
clarify
there
is
no
official
non-profit
for
backdrop?
Is
there
right
now
right,
so
the
conservancy
is
acting
as
that.
A
Yeah
the
backdrop
there
is
no
backdrop
non-profit
organization.
A
Instead,
we
have
joined
as
a
partner
organization
of
the
conservancy,
and
it
serves
as
both
a
fiscal
and
legal
sponsor
for
us
so
that
we
don't
have
to
figure
out
how
to
run
a
non-profit
and
they
also
specialize
in
software
projects
that
use
the
gpl
license,
which
is
great
because
there
are
a
bunch
of
other
people
are
all
doing
the
exact
same
thing
and
we
get
to
leverage
the
sort
of
shared
community
knowledge
at
the
conservancy
for
how
to
handle
this.
So
they
hold
trademarks
for
a
lot
of
their
other
gpl
community
projects.
A
Also
so,
hopefully,
we'll
be
able
to
yeah
we'll
get
all
of
this
documented
in
a
more
sensible
location
than
the
pmc
issue.
Queue
going
forward.
D
A
Unfortunately,
all
right,
there's
other
stuff
happening
in
the
queue
for
the
pmc.
We
don't
have
any
official
votes
or
announcements
or
anything,
but
I
did
want
to
let
everybody
know
that
we
are
working
on
all
of
the
beginning
of
year,
stuff
that
we're
supposed
to
be
doing,
and
hopefully
there
will
be
more
news
coming
soon,
also
going
on
in
the
community.
This
week
we
have
three
new
contributed
project
releases,
the
ldap
sso
module,
the
ldap
authentication,
module
and
role
watchdog.
A
So
continued
thanks
to
all
of
our
community
members
who
are
plugging
in
hours
and
turning
out
new
modules
for
us,
which
is
great
for
backdrop,
cms
websites
for
the
main
website
factofsums.org.
We
have
this
long
outstanding
issue
for
how
to
support
more
data
in
info
files.
I
want
to
go.
A
Take
a
look
at
that
issue
today
to
merge
it
and
realize
that
there's
some
merged
conflicts,
so
that
just
needs
to
be
rebased
duck
bomb
if
you're
watching
this
later,
if
you
have
a
chance
to
rebase
it,
that's
great,
if
you
don't
I'm
going
to
be
doing
some
work
on
the
backdrop
cms.org
websites
later
on
and
if
you
haven't
gotten
to
it
by
the
time
I
get
back
there,
I
might
take
a
stab
at
untangling
that
pull
request
and
getting
it
in
there.
I
know
you've
been
waiting
a
long
time
to
get
that
done.
A
We
have
a
documentation
website
underway.
Thank
you,
peter,
for
taking
that
on
current
status
with
that,
I
believe
is
that
it
is
weighting
the
feeds
import
of
documentation.
From
the
current
backdrop,
cms.org
site,
I
did
a
bunch
of
work
with
feeds
importers
yesterday
and
hope
to
have
a
working
version
of
that
up
on
the
events
site
later
today,
assuming
I
can
get
the
time
to
wrap
it
up.
D
With
regards
to
that,
sorry,
are
we
going
to
have
new
content
types
where
the
thing's
going
to
be
imported?
It's
going
to
be
documentation,
pages.
A
Yeah
so
I
created
a
new
content
type
and
just
pulled
all
of
the
book
and
doc
content
from
background
cms.org
into
there.
We
might
not
end
up
wanting
to
keep
all
of
it,
but
that
was
the
easiest
way
to
get
it
all
over.
So
I
figured
copying
it
all
and
then
deleting
or
unpublishing
the
stuff
we
wouldn't
want
will
be
easier
than
trying
to
pick
and
choose
what
we.
A
We
want,
if
peter
you
decide,
you
want
it
all
in
with
content
types
we
already
have.
Let
me
know
and
that's
easy
to
change
later,
also.
D
A
A
Okay,
next
up
is
the
events
website
for
backdrop
cms.org.
I
think
we
have
registration
up,
but
donations
are
not
working
yet.
I
have
an
email
into
the
software
freedom
conservancy
about
how
to
handle
transfer
of
funds,
because
last
year
they
were
able
to
get
us
set
up
with
eventbrite,
because
they'd
already
used
eventbrite,
but
now
that
we
want
to
do
it
directly
on
our
website,
it's
going
to
be
a
little
different.
I
haven't
heard
back
from
them,
yet
I'm
a
little
concerned.
A
We
might
not
hear
back
from
them
in
time,
so
I've
started
setting
up
just
a
really
quick
implementation
of
paypal,
smart
buttons,
which
we
can
download
from
our
paypal
account
and
stick
on
there,
and
hopefully,
when
we
hear
back
from
them,
it'll
be
really
easy
to
just
switch
out
our
code
for
their
code
and
continue
moving
forward.
So
I'm
hoping
that
that's
not
going
to
be
a
problem,
but
at
least
we'll
have
something
up
right
away.
A
B
H
Should
be
working
now,
as
far
as
I
know,
I
I
need
to
get
in
there
and
check
and
make
sure
crown's
actually
running
it
successfully,
but
when
I
tested
it
it
was,
it
was
working.
H
We
keep
forgetting
to.
We
have
to
make.
We
have
to
have
the
user
have
permissions
to
make
the
temporary
database
that's
used
in
the
process
of
performing
this
annotation,
so
it
like
makes
the
database
and
then
it
drops
the
database
and
then
it
makes
a
database
and
it
drops
the
database
and
we
forget
to
give
it
those
permissions.
A
F
Sure
so
we
always
start
with
the
current
bug
fix
release.
The
next
bug
fix
release
will
be
118.2
that
will
be
coming
out
as
soon
as
we
accrue
enough
fixes
that
it
warrants
a
release,
there's
no
officially
scheduled
date
and
we'll
go
through
the
items
that
we
have
here
on
the
agenda
as
being
higher
priority.
F
So
the
first
item
that
we
have
is
content
an
editorial
problem
that
could
result
result
in
content
loss
while
you're
creating
content.
So
it's
kind
of
a
big
bigger
deal,
the
maximize
button
in
ck
editor,
if
you
click
it
and
then
minimize
the
editor
again,
you
cannot
save
the
content
on
the
page,
and
so
your
changes
need
to
be
re-entered.
F
It's
a
big
issue.
It
currently
is
easily
reproducible
on
a
new
installation
of
backdrop,
because
the
maximize
button
is
present
out
of
the
box.
So
49
33
is
the
issue
tracking.
That
particular
problem.
There's
no
pull
request.
Yet
it's
just
been
flagged
as
a
problem.
There's
steps
to
reproduce
it,
but
we
haven't
had
a
developer,
take
a
look
at
it
yet
so
it's
probably
javascript
related.
So
if
you
have
any
front-end
skills,
it's
probably
the
area
that
in
which
the
problem
exists,
so
that
needs
a
developer
to
take
a
look
at
it.
F
Next
up
throw
a
warning
if
the
max
input,
vars
php
setting,
is
not
properly
set
issue
3824,
there
is
a
pull
request
that
needs
review.
There
hasn't
been
any
updates
in
a
couple
of
weeks
there,
so
I
don't
think
I'll
recap
that
yet
again
this
issue
that
got
bumped
from
118
into
a
later
version
language
names
not
translated
into
their
native
names
issue
4511.
F
that
one
has
been
marked
rtbc
and
is
ready
to
go
pretty
much
anytime.
I
really
hope
I'll
get
that
merged
in.
So
I
want
to
tell
you
guys
again
next
week
that
it's
still
rtbc
like
I
did
last
week
and
lastly,
is:
oh
sorry,
not.
Lastly,
php8
support
issue.
4772
this
issue
has
a
pull
request.
It's
still
in
progress
could
use
some
additional
testing
to
find
out
if
we
have
everything
working
in
php,
8
completely.
F
You
know
I
haven't
looked
at
that
to
see
if
it's
passing
all
tests,
joseph
you
are
the
originator
of
that.
Is
it
passing
all
tests
right
now.
F
F
It
is
passing
all
tests,
that's
great
okay,
but
I
think
that
we
still
have
managed
to
find
some
like
areas
where,
if
you're
manually,
testing
that
there
are
some
things
that
do
not
work-
and
I
think
more
of
that
manual
testing
is-
would
be
appreciated
on
that
issue.
On
the
flip
side
of
that
it
also,
if
it's
already
passing
tests,
we
could
merge
that
as
it
is
and
then
start
iterating
upon
it
for
edge
cases
with
php
eight
support
as
we
find
them.
F
Okay
and
then
lastly,
menu
active
trail
gets
confused
when
the
same
path
is
used
in
menu
links
for
multiple
languages,
a
very
confusing
circumstance,
but
you'll
know
it.
When
you
see
it
47.98
is
the
issue
has
a
pull
request
that
fixes
the
problem,
but
we
need
test
coverage
automated
test
coverage
on
it
jen.
You
think
you
have
a
way
to
solve
that
problem
now,
possibly
with
the
test
module,
and
so
I
think
we're
waiting
on
that
at
this
point.
F
Okay,
I
also
want
to
just
give
a
shout
out
that
there
are
12
rtbc
issues
that
are
currently
ready
to
be
committed
thanks
so
much
to
our
community
members
that
have
been
putting
that
together,
extra
shout
out
to
alan
mills
and
indigo
zella,
who
have
been
doing
this
tag.
F
Team
thing
where
alan
melz
just
finds
some
inconsistencies
in
the
code
and
says:
hey
we're
not
being
consistent
with
something
and
then
makes
a
pull
request,
and
then
indigozella
and
alan
just
go
back
and
forth
and
now
have
several
rtbc
issues
just
doing
that
tag.
Team
of
cleanup
and
we
love
cleanup
issues.
F
So
thank
you
so
much
for
the
for
your
work.
There,
okay,
119.
119,
is
the
next
minor
version
of
backdrop.
It
is
a
scheduled
release
on
may
15th
2021
feature,
freeze
will
be
may
1st
and
for
minor
versions.
We
have
features
that
well
we're
adding
features,
not
just
fixing
bugs,
and
each
issue
has
an
advocate
that
is
kind
of
the
point
person
to
move
that
issue
forward.
F
D
Kind
of
the
front
end
there's
actually
an
update,
there's,
actually
an
update
latin
filed,
a
separate
request
to
split
out
the
like
to
solve
the
nested
forms
issue,
and
that
pull
request
is
not
linked
to
that
issue
specifically,
but
you
can
see
it.
I
think
I've
added
a
comment
before
my
comment.
There's
a
link
to
that
pr-
and
I
I
reviewed
it-
there's
some
breakages,
but
there
was
a
stat
and
I
think
lan
needs
some
help
with
it
direction.
F
D
A
separate
pull
request
that
only
deals
like
it
doesn't
solve
the
actual.
It
doesn't
have
the
the
exposed
form
it
just
tries
to
decouple
not
the
couple.
What's
the
perfect,
we
just
split
it
move
the
nested
forms
so
that
we
don't
have
nested
forms
in
the
market.
D
F
Great
well
that's
great
that
I
saw
that
your
feedback
mostly
said
that
stuff
wasn't
working
quite
right,
but
I'm
curious.
If
his
approach
could
you
know,
be
a
route
that
we
continue
down
to
like
see
if
we
could,
if
we
can
get
that
part
working,
then
it
might
be,
it
might
unblock
the
rest
of
this.
F
Yeah,
okay,
excellent
thanks
gregory
next
up
is
advanced
caching,
also
known
as
supporting
cash
tags
and
the
cash
dynamic
cash
max
age.
Header
issue
4127.
F
joseph
you
are
the
advocate
for
this,
I'm
not
sure
if
you
are
able
to
speak
to
it,
he
needs
code.
Review
needs
code,
review,
okay,.
F
D
You
had
the
chance
to
go
through
it.
I
recently
had
like
a
job
daily
job
related
task
that
was
involving
cash
tags
and
I
went
through
the
the
drupal
documentation
and
I
mentioned
a
few
things,
so
I'm
asking
a
few
questions
as
to
whether
the
our
solution
would
also
implement
those
things.
F
C
F
Thank
you
for
that
gregory.
Okay,
next
up
is
jen
you're
advocating
for
this
issue.
Add
a
field,
has
value
visibility,
condition
to
layouts
issue
4728.
Are
there
any
updates
this
week?
Not
since
last?
No
not
for
a
while,
though
okay
we'll
move
on,
then
next
up
is
adding
support
for
relationships
to
layout
contexts,
issue
2134,
doc
welmont
is
the
advocate
for
this.
It
still
just
has
a
minor
renaming
task
to
it,
other
than
that
it
appears
to
be
ready
to
go.
F
I
saw
that
he
posted
a
comment
earlier
a
couple
days
ago.
That
said
something
along
the
lines
of
this
is
so
simple.
I
think
that
there's
plenty
of
time
to
do
it
and
that's
why
it's
not
getting
done
so
I
totally
understand
that
feeling
there
but
yeah.
That
issue
doesn't
need
to
be
handled
by
doc,
wilmont
alone.
If
anyone
wants
to
come
in
and
do
that
renaming,
it's
not
a
very
large
task
to
make
the
suggested
changes,
and
I
think
that
we
know
what
changes
we'd
like
to
see.
B
So
nate,
I
think
sometimes
people
are
reluctant
to
do
that
when
somebody
has
put
so
much
work
into
an
issue
which
you
know,
we
should
just
mention
one,
the
the
etiquette
for
doing
that
into
the
the
technical
view.
You
just
do
a
pull
request
on
on
his
pull
request
or
how
exactly?
What
is
the
process
if
somebody
else
were
to
help
yeah.
D
F
F
However,
I
also
don't
want
to
discourage
people
from
taking
the
existing
pull
request
and
making
a
completely
new
pull
request.
That
includes
all
of
those
changes
with
new
changes
on
top
of
it.
I
also
find
that
to
be
completely
acceptable,
and
I
don't
really
think
that
we
should
discourage
that,
because
it
is
a
way
of
moving
a
little
bit
faster
and
yeah.
F
Just
as
long
as
that
person's
the
original
authors
or
commits
are
still
intact,
so
they
get
some
of
the
commit
credit,
although
we
we
commit
it,
we
credit
everyone,
no
matter
what
so.
A
Usually,
when
I
have
to
do
that,
I
usually
close
the
previous
pull
request
and
mark
the
new
one
as
replacing
it,
so
that
committers
don't
get
confused
in
the
future
as
to
which
pull
request
is
newer.
But
then
you
can
mention
that
person
and
make
sure
they
know
that
there's
a
new
pull
request.
So
if
they
want
to
do
the
same
thing
and
get
you
know,
add
to
what
you've
done
to
theirs,
then
at
least
know
that
there's
new
action
happening
somewhere
else.
D
A
F
D
You
you
may
see
that
I
often
may
ask
you
or
someone
else
to
do
that
for
me,
because
I
don't
have
that
level
of
access
to
do
it.
But
it's
good
that
we
have
another
person
and
outside
court
committees
that
can
actually
do
it
for
the
rest
of
the
community,
because
we
often
not
often
sometimes
we
do
need
it.
A
Okay,
maybe
we
should
make
that
an
official
responsibility
and
give
it
to
some
people
other
than
me
too.
F
Yeah,
what
what
I
do
is
a
core
committer
and
peter
is
as
you're
a
core
committer
to.
It
might
not
be
bad
to
officially
formalize
this
that
when
I
merge
in
one
pull
request
on
an
issue,
I'll
also
check
the
the
list
of
other
related
pull
requests
in
the
issue
and
make
sure
that
they're
all
closed,
because
if
one
of
them
has
been
merged,
then
the
other
ones
are
usually
cruft.
F
F
Okay,
next
up
is
gregory
the
issue
that
you're
advocating
for
merging
together
the
update
pages
for
core
modules,
themes
and
layouts
into
a
single
page
issue.
2714
any
updates.
D
Yeah-
and
I
appreciate
the
previous
comments
about
being
able
to
act
on
some
of
the
things-
no
updates
on
that
one.
So.
D
I
say
that
I
didn't
have
enough
time,
so
I've
been
saying
in
past
couple
of
meetings
I'll
get
back
to
it,
but
I
I
just
can't
find
the
time
the
update
as
it
were,
was
that
the
the
feature
itself
was
ready
to
be
committed,
but
there
was
a
breakage
with
the
the
dashboard
block
with
the
updates,
and
I
was
considering
to
split
that
off
onto
a
separate
ticket,
we'll
see
how
it
goes.
F
F
I
don't
think
that
there's
anything
more
to
be
said
on
it
since
last
week,
it's
just
ready
to
go
here
as
soon
as
possible,
peter
you
had
been
advocating
for
that
one.
But
now
you've
moved
on
to
this
new
issue.
49.66
allow
server
settings
to
be
overridden.
F
J
So
with
the
settings.php
file
you
put
in
the
database
connection
information
and
then
that's
like
when
you're
installing
a
site,
that's
what
gets
used.
J
I
think
this
is
mainly
used
with.
I
know:
lando
uses
it
so
when
you're
installing
a
site
using
lando,
then
you
don't
have
to
worry
about
setting
up
settings.php.
It's
all
done
for
you
based
on
there,
because
they
have
a
set
database
name
database
connection
intro,
so
they
do
it
for
you.
I
think
greg
mentioned
that
other
hosting
providers
might
do
that
as
well.
I'm
not
sure
I
think
pantheon
uses
it
yeah,
okay,
so
so
the
issue
is
that
I
have
with
that.
J
Basically,
if
you're
using
a
system
that
has
that
variable
set,
then
it
you
can't
do
anything
about
it,
there's
no
way
of
using
the
settings.php
file
to
do
what
you
want
to
do.
You
can't
sort
of
customize
it
and
I've
had
this
problem
with
lando.
So
the
solution
I
had
was
just
to
add
a
new
setting
to
settings.php,
which
is
disabled
by
default.
But
if
you
enable
it,
then
it
means
that
the
settings.php
file
will
be
used
as
the
main
source
of
information
when
installing
a
site
and
it'll
ignore
the
server
variable.
J
So
it
shouldn't
it
won't
affect
any
existing
sites.
It
won't
affect
any
new
sites
unless
people
specifically
enable
it,
and
obviously
they
only
do
that
if
they
sort
of
don't
know
what
they're
doing,
and
that
means
that
you've
got
more
power
over
what
happens
when
you're
installing
a
site
yet
for
debugging
or.
F
Interesting
I'll
just
throw
it
out
here
so
adding
adding
another
setting
to
settings.php.
F
Makes
me
a
little
nervous
because
I
feel
like
some
developers
when
they
first
are
introduced
to
backdrop
it's
like
the
one
file
they
need
to
manually,
edit
or
one
that
they
will
look
at
frequently,
and
I
think
that
sometimes
they
read
through
that
file
to
see
like
what
options
are
available
to
them,
and
sometimes
you
know
the
more
options
we
have
in
there,
the
more
confusing
it
can
be
like.
F
F
And
so
I
think
I
I
like
to
ask
like:
could
you
just
unset
that
variable
in
settings.php
and
not
introduce
a
new
option
like
because
you
could
just.
C
J
So
when
I
was
trying
to
figure
this
out
in
lando
before
I
opened
this
issue,
I
tried
all
sorts
of
ways
of
disabling
it
unsetting
it
resetting
it
to
just
a
blank
string,
all
that
sort
of
stuff
and
nothing
seemed
to
work.
If
there's
ways
that
I
haven't
thought
of
that,
I'm
missing
and
I'm
open
to
that
and
to
figure
out
how
to
do
it,
because
I
very
much
like
to
yeah
get
around
that.
J
J
So
I've
just
added
a
little
thing
to
the
end
saying
if
this
value
like
this
variable
is
set
and
the
settings
the
new
setting
that
I've
added
is
enabled
then
do
it,
but
otherwise
yeah.
So
I
I
just
had
like
a
little
extra
if
thing
added
there
to
make
it
happen
or
not.
If
there's
a
better
way
of
doing
it,
I'm
open
to
that,
but
yeah.
D
Peter
I
understand
that
this
is
a
blocker
for
the
the
things
that
you
mentioned
for
b,
but
that
my
questions
were
coming
from.
So
in
gov
cms.
We
we
sort
of
like
control
what
sas
customers,
which
should
not
have
certain
liberties
via
variables,
and
we
expect
those
variables
to
not
be
able
to
be
overridden
in
any
way.
J
Yeah,
I
guess
it
depends
on
what
side
of
the
coin
you're
looking
at
like
I'm
from
that
point
of
view,
it's
like
yeah,
you
want
to
be
a
lock
stuff
in
and
have
it
easy
for
the
customer
that
they
just
they
can't
change
stuff.
From
the
other
point
of
view,
if
you're
a
developer
or
just
someone
setting
up
a
backdrop
site
using
one
of
these
situations,
then
it's
like
it's
your
site,
you're
in
control.
You
want
to
be
able
to
do
stuff.
D
F
Well,
I
posted
a
comment
peter
I'm
not
sure
if
you
tried
this
explicitly
but
yeah,
if
you
could
give
it
a
shot,
if
you
haven't
tried
it,
and
maybe
we
can
use
that
as
like
a
like,
if
you
run
into
this
situation,
here's
here's
something
you
can
try.
F
If,
if
and
if
it
works,
then
great,
then
we
can
figure
out
what
to
do
with
this
pull
request
and
if
it
doesn't
work
well
then
I
guess
that
makes
I
think
your
request
more
valid.
You
know
if
there's
no
other
way
to
get
around
it,
then
we
need
to
provide
a
way
to
get
around
it.
I
F
F
Anybody
have
anything
else
for
119
or
just
issues
in
general.
B
I
just
want
to
mention
we
retweeted
our
note
about
advocacy
for
issues
this
week
and
we
got
a
reply
from
someone
asking
well
it's
great
that
you
have
this
process
to
advocate
for
issues
but
who's
advocating
against
issues
like.
B
Who's
advocating
for
not
adding
stuff
to
core,
and
I
had
to
smile,
I
feel
like
that
does
happen.
It's
not
it's
not
that
we're
suffering
from
the
opposite.
On
the
other
hand,
it
is
a
good
point
that,
just
because
somebody
advocates
for
an
issue
doesn't
mean
that
it
it's
gonna
get
into
core,
and
we
need
to
think
about
how
to
I
mean,
I
think,
just
like
the
way
we
handled
it
today
as
an
issue
is
brought
up
with
a
new
advocate
to
sort
of
just
talk
about
like
just.
F
F
And
an
issue
does
have
at
least
one
other
person
has
to
confirm
it
as
being
like
a
a
valid
feature
request,
although
that's
not
a
very
high
barrier,
because
it
can
literally
be
anyone.
A
But
if
there
is
pushback
from
the
community,
we
do
have
a
process
for
advocating
for
escalating
to
the
pnc.
For
like
does
this
go
against
our
principles?
So
I
think
if
it's
serious
enough,
it's
gonna
get
stopped
a
lot
of
times.
You
know,
I
don't
know
if
it's
that
big
a
deal
one
way
or
the
other.
A
lot
of
these
issues
are
like
things
are
bug
fixes
that
just
need
to
go
into
meter
releases
or
features
that
everybody
agrees
on
so
yeah.
B
Down
yeah:
well,
there
was
some
talk
initially
about,
like
I
think
at
least.
The
idea
at
one
point
was
that
any
new
issues
that
were
going
to
be
advocated
for
would
be
brought
to
the
attention
of
the
pmc
that
would
they
wouldn't
require
their
approval,
but
we'd
at
least
let
the
pmc
know
so
that
they
could
object.
I
don't
think
we've
really
been
doing
that
very
well,
but
that
might
be
something
we
want
to
just
keep
in
mind
to
just
at
least
update
the
pmc.
These
are
the
issues
being
advocated
for.
A
I
A
F
B
F
Okay,
let's
move
on
to
initiatives
with
10
minutes.
We
have
three
initiatives.
Initiatives
are
long-running
objectives
that
aren't
necessarily
tied
to
a
particular
release
and
we
have
three
of
them
currently,
one
of
them
kind
of
a
pseudo
initiative,
documentation
improvements,
peter,
is
taking
the
lead
on
that
initiative.
J
I
think
just
waiting
on
jen
to
do
the
migration
of
documentation
from
the
backdrop
cns.org
site
to
the
new
dockstop
backdrop
site.
I
think
once
that's
done,
then
we
can
just
look
at
the
issue
queue
and
see
what
other
stuff
people
want
to
add
or
change.
But
I
think
once
that's
done.
Essentially
the
main
bulk
of
the
work
is
done
and
then
it's
just
work
as
usual
on
issue
queue,
stuff,
okay,.
F
Telemetry
is
the
initiative
to
collect
information
about
the
way
people
are
using
backdrop
and
report
it
into
a
centralized
database
on
backup,
cms.org
tim.
You
are
the
initiative
lead.
Do
we
have
any
updates
this
week.
F
Okay
and
lastly,
theme
development
should
not
be
necessary
to
use
backdrop
luke
mccormick
is
the
initiative
lead
he's
not
present
today,
but
looks
like
there's
an
update
here
in
the
agenda
saying
we
had
a
meeting
last
tuesday
to
report
on
work
done
so
far
and
to
talk
about
how
to
wrap
up
this
initiative.
F
The
meeting
was
recorded
and
available
on
youtube.
I
assume
this
is
under
the
backdrop
channel.
F
B
Right
I'll
just
say
quickly:
the
goals
were
a
little
bit
ambiguous.
Well,
actually,
there
was
some
really
clear
goals
which
was
like
to
get
at
least
four
or
five
more
ready
to
use
themes,
and
there
have
been
about
four
or
five
themes
created
since
we
started
this
initiative.
So
in
that
sense
we
sort
of
accomplished
at
least
that
goal,
which
was
explicitly
stated
at
the
beginning,
but
I
think
quickly.
B
We
started
morphing
the
project
into
other
ambiguous
goals,
and
the
idea
right
now
is
to
just
sort
of
wrap
things
up
to
talk
about
what
we've
learned
and
if
there
are
new
specific
things
that
you
know
emerge
out
of
it
to
form
a
new
initiative
with
maybe
more
concrete
goals
but
in
the
meantime,
releasing
people
from
their
current
commitments.
So
they
can
work
on
other
things.
F
C
This
so
I
have
a
thing
I'd
like
to
ask
about,
but
I
don't
know
if
anyone
can
help
with
this.
I've
been
working
on
trying
to
improve
the
performance
of
the
tests
again
and
an
issue
I
made
a
while
back
was
to
reuse
test
prefixes,
but
I'm
running
into
a
problem
where
multiple
test
runners
are
selecting
the
same
prefix
and
I've
tried.
I've
tried
putting
in
delays
and
I've
tried
using
locking
and
nothing
I
can
figure
out
is
stopping
them
from
doing
this.
F
Yeah,
I'm
having
a
little
bit
of
trouble
understanding
what
what
you
even
mean
by
using
the
same
prefixes
so.
C
C
Take
at
the
end
at
the
beginning
of
a
test
rather
than
creating
a
new
database
prefix.
I
look
for
a
database
prefix,
that's
not
being
used
by
another
test
and
then
get
checksums
for
the
cache
tables
and
get
checksums
for
the
tables
in
that
prefix
and
compare
them
and
if
they're
the
same,
I
just
don't
do
anything
with
them
and
if
they're
different,
then
I
do
the
whole
dropping
and
recreating
the
table
like
the
normal
link,
is
normally
done.
F
Interesting,
isn't
that
really
pretty
likely
that
tests
would
make
changes,
though,
like
I
mean
at
least
some
change
to
the
database.
C
C
F
Interesting,
okay,
well,
yeah.
I
I
want
to
avoid
any
situation
of
like
the
order
of
the
tests
mattering,
you
know
like
it.
If
the
tests,
if
you
add
a
new
test,
suddenly
get
different
results.
Yeah.
C
F
Long
as
we
maintain
the
integrity
of
every
test
starts
with
a
blank
slate
that
is
predictable.
If,
if
there's
optimizations,
you
can
put
on
top
of
that
as
long
as
that's
still
the
case,
then
that's
awesome.
C
Yeah,
the
problem
is
that
so
at
the
start
of
the
setup
process,
I
do
a
lock
wait
and
then,
during
that
it
picks
the
prefix,
but
it
seems
like
the
runners
are
just
ignoring
that
and
continuing
on,
and
there
are
a
lot
of
times
where
there's
race
conditions.
F
Yeah,
I
think
that,
oh
I
I
kind
of
think
I
understand
what
you're
saying
so.
The
the
run
tests
shell
script
runs
tests
in
parallel
right
and,
I
think,
are
like
a
concurrency
of
five
or
something
like
that
is
what
we're
running
on.
F
F
F
F
Cool
reuse,
test
prefixes
instead
of
rebuilding
them
and
great
looks
like
indo
gozala
has
been
providing
you
some
feedback
there
and
doc
belmont.
B
C
F
Okay,
cool,
if
I
get
a
chance
I'll
I'll,
add
this
to
the
agenda
so
that
we
at
least
look
at
it
once
a
week.
B
B
I
think
1
p.m,
pacific
time
in
the
u.s
on
command
line
tools
and
peter
is
going
to
be
talking
to
us
about
b
and
I'd
like
to
think
that
the
pending
vug
has
inspired
him
to,
but
he's
doing
a
lot
of
work
on
b
right
now,
so
that's
exciting,
so
come
join
us
to
talk
about
b
or
other
command
line
tools
next
week
and
and
where
they're
going.
We
have
a
in
theory
right
now.
B
Three
active
projects
for
command
line
tools
out
there
and
it'd
be
nice
to
maybe
start
talking
about
where
to
settle
and
which
one
I
I've
had.
Newcomers
say
like
they're,
confused
by
the
the
different
projects
out
there
and
which
one
should
they
use.
Anyways,
there's
that
and
also
we
are
a
little
over
two
weeks
away
from
back
or
up
live,
which
is
our
supposed
to
be
our
big
event,
and
I
think
progress
got
bogged
down
a
bit
over
the
last
week
or
so.
B
I'm
gonna
try
and
really
dig
in
this
weekend
and
help
move
things
forward.
But
at
this
stage
we
still
plan
to
go
ahead.
We
have
a
lot
of
pre-existing
work
to
build
on,
so
I
think
we
can
still
do
it,
but
we're
getting
a
little
bit
behind
the
curve.
That's
all.
I
B
I'll
tell
you
what
I'm
going
to
say
this.
We
will
probably
meet
tomorrow
if
anybody
at
least
some
of
us,
in
fact,
I'm
just
going
to
say
I'll,
be
available
at
4
30
tomorrow
afternoon
by
my
time,
that's
2,
30
pacific.
It's
one
we've
met
before
to
talk
about
backdrop.
Live
I
don't
know
if
anybody
else
can
be
there,
but
if
you
can
join
me.
F
C
F
Have
other
obligations
so
go
ahead
and
say?
Thank
you
guys
all
for
watching.
Thank
you
guys
for
joining
and
yeah
we'll
see
you
next
week.