►
From YouTube: Backdrop Weekly Meeting April 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
All
right
we
are
live
today
is
thursday
april
15th.
I
think
I
think
the
meeting
agenda
is
labeled
the
14th,
but
I
think
it's
the
15th
it's
the
15th
where
I
am,
which
is
in
california.
It
might
be
the
14th
and
some
places
in
the
18th
and
who
knows,
but
anyway,
this
is
thursday.
A
This
is
our
weekly
developer
check-in
meeting
and
before
we
get
started,
I'd
like
to
go
around
and
do
some
quick
introductions,
I
will
be
happy
to
start.
I
am
john
lampton.
I
am
joining
from
oakland
california.
I
apologize
in
advance.
My
dog
recently
had
surgery,
and
so
I
am
dog
watching
and
should
the
mailman
approach
there
will
be
very
loud
barking
and
I
will
try
and
mute.
A
I
think
oh
also
fun
news
for
me.
I'm
working
on
a
couple
of
really
complicated
drupal
to
backdrop,
upgrades
and
so
you're
about
to
see
me
all
over
the
country,
q,
which
should
be
fun
all
right.
Tim.
B
Oh,
I
already
unmuted,
I'm
tim,
it
is
the
15th
and
I
just
was
in
the
wrong
day.
I
apologize
so
everything
everything
everywhere
is
labeled
incorrectly
for
the
14th,
we'll
I'll
work
on
fixing
it
I'm
in
deerwood
minnesota
and
I
have
been
pretty
swamped.
I
have
two
backdrop:
sites
that
are
going
live
this
month,
along
with
personal
stuff,
just
haven't
had
a
lot
of
backdrop
time,
but
yep
still
trying
to
hang
in
there.
So
nothing
big
to
report
hoping
to
get
out
my
mountain
biking
soon.
B
That's
all
gregory
you're
next.
C
I'm
greg
so
like,
representing
both
europe
or
a
part
of
europe
and
australia,
and
it's
the
16th
here
so
actually
15
minutes
ago,
so
yeah,
I'm
usually
in
australia,
but
now
I'm
back
home
julia
covered
in
greece
joining
for
like
the
the
regular
catch-up
and
see
how
I
can
help
with
things,
but
yet
life's
busy
as
well.
Onboarding
new
people
at
work
drains
a
lot
of
my
energy
but
yeah.
I
hope
to
get
back
into
things.
Olaf,
hi.
D
I'm
olaf
from
hamburg
in
germany-
I
guess
I'm
also
busy
so
all
of
us
and
yeah
I'm
a
member
of
the
bmc
building
a
lot
of
backdrop,
websites
for
quite
a
long
time
and
yeah
also
just
wanted
to
check
in
and
maybe
but
maybe
also
another
time
discuss,
the
80
rule
of
thumb,
but
not
sure
if
it's,
if
I
have
the
energy
to
do
it
today,.
A
All
right,
let's
see
in
the
last
week,
we've
had
one
new
contributed
module.
It's
called
multiple
selects,
which
is
pretty
funny.
I
hadn't
heard
of
that
module
before
I
started
working
on
the
spreadsheet
for
the
site,
I'm
working
on
to
figure
out
which
modules
were
ready
and
it
was
on
the
list
and
I
went
to
check
and
was
like
it
just
got
ported.
So
thank
you.
Whoever
reported
it
timings,
miraculous
but
yeah
very
exciting.
A
On
our
backdrop,
websites
themselves,
we
have
an
ongoing
issue,
backed
up
cms.org
for
supporting
more
information
and
info
files.
I
believe
this
change
has
been
deployed
both
merged
and
deployed.
A
I
think
it
is,
I
think
I
think
we
did
a
update.
We
did
a
backdrop,
security
update
or
something
and
it
got
pushed
with
the
update.
So
I
think
it's
there,
I'm
not
sure
chuck
walnut
knows
that
I
will
put
something
in
the
issue
to
make
sure
that
he
can
start
testing
with
his
contrib
projects.
A
I
don't
know
if
there's
anything
else,
we
should
talk
about
for
backdrop
cms.org
in
the
outreach
meeting.
There
was
some
discussion
at
the
end
about
how
to
better
manage
the
issue
queue.
So
maybe
we
should
just
say
if
you're
interested
in
that
you
can
go
watch
the
outreach
video.
A
Do
you
want
to
add
something
greg?
No
okay,
it
looked
like
you
were
excited.
A
A
And
our
events
site,
we
just
talked
about
a
little
bit
too
we're
going
to
have
a
backdrop,
live
event
coming
up
in
the
next
month
and
a
half
so
we're
going
to
make
some
updates
there,
but
nothing
super
critical
that
needs
to
be
talked
about
today
and
then
probably
progress
report.
This
is
something
that
nate
usually
does,
but
he
is
not
around
today,
so
I'm
going
to
do
my
best
to
muddle
through
it.
A
First,
we
usually
talk
about
issues
that
are
scheduled
for
our
next
bug,
fixed
release.
It
looks
like
we've
got
two
important
issues
to
talk
about
today.
One
of
them
is
php8
support.
I
believe
php8
comes
out
in
the
fall,
so
we
have
a
big
issue
here
that
joseph
has
been
working
on
polar
quest
to
go
through
all
of
backdrop
and
make
sure
that
we
don't
get
any
deprecation
notices
or
worse
on
php.
Eight,
it
looks
like
the
current
pull
request
is
marked,
needs
work,
greg.
It
looks
like
you
tested
this
recently.
C
I
haven't
touched
in
a
couple
of
weeks
so
sorry
and
I'm
always
having
issues
computer
issues
when
I'm
on
zoom,
so
it's
really
slow
bear
with
me.
A
A
It
looks
like
we've
got
a
pull
request,
marked
works
for
me,
but
it's
gonna
need
some
automated
tests,
some
creating
automated
tests
that
match
the
steps
provided
in
the
pull
request
is
hard,
but
I
had
an
idea
about
how
we
could
probably
do
it
with
a
custom
module
that
could
recreate
the
scenario
more
simply
so
I'll
try
and
get
take
a
stab
at
that
one,
and
that
is
it.
So
that's
also
going
to
be
needs
work
for
118.3.
C
C
C
A
This
one
is
rtbc,
so
it
should
go
in
at
any
moment,
which
would
be
great
but
I'll
drop
it
in
here.
Essentially,
what
happens
is
if
you
uninstall
the
comment
module.
Your
homepage
will
break,
but
if
you
uninstall
it
again,
then
it's
fine,
so
yeah
it's
a
little
tricky
but
we'll
fix
it
so
that
when
you
uninstall
it
the
first
time
it'll
work.
Okay,
someone
asked
for
the
dev
meeting
agenda,
I'm
just
going
to
post
the
links
into
it.
E
A
A
The
first
one
is
on
the
media
library
dialogues.
When
you
go
to
add
an
image
or
document,
and
you
want
to
browse
the
existing
items
on
your
site.
There
is
a
filter
there
for
exposed
exposed,
filter
in
views.
One
of
them
has
a
file
name
option
in
it
and
or
we
wanted
to
add
one
with
a
file
name
option
in
it
and
laryn's
been
working
on
it
he's
got
it
working
but
needs
some
help
with
the
pull
request,
which
looks.
A
A
A
Next
one
advanced
caching.
This
is
exciting.
This
is
hashtags
in
course,
so
hashtags
are
something
that
everybody
really
loves
about:
drupal
8.
there
is
a
drupal
7
module
that
can
do
the
same
thing.
Joseph
has
been
working
on
getting
hashtags
going
for
backdrop,
which
would
be
killer
feature,
and
that
issue
is
number
4127.
currently
marked
needs
code.
Review
needs
testing
I'd,
be
willing
to
give
that
one
a
test.
C
Yeah,
I
think
that
last
time,
the
comment
that
I
made
was
that
the
way
that
I
usually
test
such
features
is
that
I
try
to
find,
for
example,
documentation
or
articles
that
describe
how
this
is
done
in
d8
or
d7,
and
then
I
try
to
mimic
it
in
backdrop
and
see
if
it
works.
I
think
that
joseph
said
that
he
would
add
a
few
steps
to
sort
of
like
test
things
just
to
give
us
an
idea.
I'm
not
sure
if
he's
done
that,
though,.
A
Yeah,
I
think
I
could
probably
do
that
too,
based
on
my
recent
experience
with
drupal
9
like
putting
a
note
on
the
front
page
and
then
changing
the
node
and
checking
to
see
if
the
front
page
updates,
we
already
have
the
sort
of
promoted
thing.
That
would
be
pretty
easy
to
do
in
back
job.
So
there's
probably
a
lot
more
tags
than
just
that,
so
we
could
like
check
the
ones
we
can
find,
but
checking
all
of
them
is
going
to
be
tricky.
C
Yeah,
I
think
it's
mostly
like,
even
not
mostly,
but
also
like
views
if,
if
one
node
gets
updated
and
you
have
a
views
block
somewhere,
make
sure
that
that
gets
refreshed
without
the
rest
of
the
yeah.
A
Let's
see
next,
one
field
has
value
visibility,
condition.
I've
got
a
work
in
progress
on
this
one,
but
drama
had
a
fantastic
contrib
module.
I
wanted
to
integrate
in
just
better,
so
this
is
still
marked
needs
work.
A
C
So
that
issue
was
previously
held
captive
because
of
the
dot
info
file
thing:
that's
not
a
blocker
there.
I
guess
it's
a
matter
of
double
mod
filing
time
to
work
on
it
again.
Okay,
well.
A
He's
got
a
pretty
good
recent
comment
on
there.
He
explained
some
things,
which
is.
C
Yep,
so
I
promised
to
any
godzilla
that
I'll
get
back
to
it
and
I
did
get
to
work
on
my
local,
I'm
just
tweaking
a
few
things
should
be
able
to
push
final
changes
this
weekend
and
yeah.
We're
really
close,
as
in
I'm,
really
confident
that
it's
gonna
get
in
the
only
blocker
was
that
so
everything
was
tested.
Everything
was
working
as
expected.
C
The
only
problem
was
that
with
the
the
previous
changes,
when
there
was
a
an
error
when,
with
the
sorry
lost
my
train
of
thought,
the
dashboard
update
module.
Sorry,
the
the
dashboard
update
block,
which
didn't
show
correct
information,
and
then
it
showed
an
error-
and
this
is
fixed
now,
okay,
not
in
the
pull
request
on
my
local
one
I'll
push
the
changes
as
soon
as
I
give
it.
Okay.
C
C
A
A
A
All
right
more
issues,
if
you're
curious
about
what
we're
working
on
for
119,
there
are
issues
that
don't
get
talked
about
every
week.
They
are
slated
in
the
milestone:
labeled,
1.19,
okay,.
A
Initiative
updates-
I
don't
know
if
we
have
anyone
here
to
give
us
updates
on
initiatives
but
documentation
our
unofficial
initiative.
It
sounds
like
tim
greg.
You
guys
were
talking
about
a
lot
of
progress
in
the
outreach
meeting
today
at
least
planning
wise.
C
Yeah,
so
the
documentation
initiative
has
both
has
a
lot
of
moving
parts.
One
of
it
was
merging
api
and
docs
into
a
docs
site
that
has
happened.
There's
a
few
things
that
we
still
need
to
tweak.
I'm
not
sure
where
we're
at
with
the
the
wysiwyg
editors
being
used
for
specific
content
types,
but
that's
not
a
blocker.
There
were
some
discussions
and
I
think
robert,
which
is
on
the
call
mentioned
that
they
would
like
to
contribute
to
documentation.
So
we
discussed
about
giving
more
people
offer
access.
C
Hey,
robert
and
I've
also
been
trying
to
do
a
lot
of
vanilla,
d72
backdrop
upgrades,
so
I'm
trying
to
update
the
documentation.
Then
service
tree
is
looking
to
produce
guides
for
producing
video
tutorials.
So
there's
a
lot
of
moving
things,
there's
a
lot
of
progress,
but
nothing
specific
for
you
know
anything
exciting
super
exciting.
I
mean.
F
I
have
I'm
not
sure
I
have
accounts
on
many
something
it's
not
backdrop
sites,
but
I'm
not
sure
if
I
have
on
docs.
Let
me
just
look
very
quickly.
B
You
know
doesn't
solve
that
larger
problem,
which
is
it's
just
really
hard
for
people
to
submit
ideas
for
changes,
and
we
need
to
figure
that
out-
and
you
know-
we've
been
talking
about
this
documentation
initiative,
but
I
think
that
was
always
intended
to
be
fairly
limited
in
scope,
which
was
just
to
pull
stuff
onto
one
one
website.
Well,
we
have
bigger
issues
around
documentation,
but
but
that
initiative
was
never
set
to
solve
those
bigger
problems
and
we
need
to
figure
that
out.
C
One
of
the
things
with
this
is
related
to
this
whole
discussion
is
that
we
didn't
just
like.
There
were
multiple
reasons
for
for
merging
the
api
and
the
docs
the
documentation
into
a
dock
side,
but
one
of
them
was
that
we
wanted
to
allow
at
some
point
the
same
functionality
as
indeed.org,
which
is
comments
on
the
actual
documentation,
or
we
were
considering
that
so
that
people
can
actually
suggest
or
maybe
even
provide
feedback
that
yeah
this
is
working
for
me.
A
Yeah,
I
do
also
think
we
have
revisions
on
on
the
site,
so,
if
you're
not
sure
about
a
change,
you're
welcome
to
make
it
but
make
a
revision.
So
that
way,
if
you
talk
to
someone
about
it
later,
you
can
revert
to
the
previous
version.
That's
a
good,
safe
thing
to
do.
We
don't
have
a
solution
for
the.
I
want
someone
to
see
it
before.
I
publish
it
problem,
but
we
do
have
the
ability
to
do
that
in
core.
A
We
don't
have
a
ui
for
it,
so
we
could
add
something
that
would
enable
that
for
us
it
just
would
take
some
development
work.
B
Does
the
revisions
provide
any
kind
of
a
diff
file,
though,
because,
like
I
want,
if
like,
I
would
feel
more
comfortable
making
a
change
publishing
it?
If
I
could
then
say,
gregory
go
look
and
I
knew
that
gregory
could
zero
in
on
what
I
changed.
A
A
A
Yes,
but
the
diff
module
provides
the
differences
between
revisions,
and
that
is
not
in
core
and
there
is
a
contrib
version
of
the
diff
module.
I
just
checked
on
it
today,
so
we
could
include
that.
A
And
maybe
just
some
miscellaneous
issue
about
wanting
to
preview
change
before
it
goes,
live.
A
A
Okay
and
then,
let's
see,
are
you
on
here
now
no.
A
No,
no
okay
and
then
theme
stuff,
making
themes
easier
for
people
who
don't
have
front
end
development
skills.
E
F
A
A
Okay,
you
should
have
gotten
an
email,
we'll
see
what
happens
all
right.
Next.
General
discussion
open
cue.
It
q
a
there's,
an
item
on
here
that
says
better
less
us-centric
handling
of
scheduled
meeting
times,
but
I
think
we're
doing
that.
A
E
C
Olaf
olaf
mentioned
that
he
wants
to
discuss
the
80
thingy.
I
think
it's
a
it's
a
good.
D
But
I
have
another
thing
to
mention
because
recently.
D
Occasionally
I
I
talk
with
people
who
are
willing
to
help
with
backed
up
translations
and,
as
you
know,
I'm
a
bit
managing
the
translation
website,
and
so
that
works
quite
good
with
some
people.
But
there
are
others
who
register
and
then
I
communicate
with
them.
But
then
they
stop
doing
things,
and
I
think
it
has
a
lot
to
do
with
that.
The
website
doesn't
work
so
good
in
some
aspects
and-
and
there
are
other
issues,
for
example,
the
documentation
is
not
very
good.
D
I
can
try
to
fix
that
when
I
spend
time
and
time,
but
I
can't
fix
the
issues
with
the
website,
so
some
functionality
and
so
from
time
to
time
I
mention
you
jen
in
respective
issues,
but
I
have
the
impression
you
don't
find
time
to
do
something
there
so
but
you're
at
the
moment.
The
only
person
who
I
can
ask,
so
I
was
thinking
about
yeah
what
to
do
so
and
if
it's
possible
to
find
another
person-
but
I
guess
that's
not
so
easy
yeah
or
if
we
maybe
try
to
find.
A
I
understand
it
we're
having
with
the
website
our
well.
I
don't
know
you
probably
know
better
than
I
do
off,
but
I
tried
to
go
in
there
recently
to
figure
out
how
to
translate
things
and
it's
it's
almost
like
a
user
experience
problem
just
trying
to
find
where
you're
supposed
to
go
to
do
certain
things
as
a
contributor
or
I
feel
like
if
you're
downloading
things,
we've
done
a
pretty
good
job
of
making
it
so
that
you
can
find
what
you
want.
But
if
you're
like
okay,
I
have
this
translation.
A
How
do
I
get
it
in
is
really
hard,
and
I
think
that
what
we
could
do
is
spend
some
more
time
looking
at
how
drupal
solved
those
problems
on
the
drupal
localized
site
and
trying
to
replicate
that,
because
I
think
what
we
have
now
is
sort
of
just
the
modules
installed
and
we
haven't
really
thought
through
the
whole
process.
I
think
there's
a
lot.
A
But
there
are
so
if
we
port
the
whole
thing
to
backdrop.
We
could
do
that
too,
but
now
we're
possibly
introducing
issues
with
the
translation
system,
in
addition
to
the
usability
problems
and
I'm
not
sure
that
just
porting,
it
is
going
to
solve
some
of
the
usability
problems.
D
D
Yes,
there
are
some
smaller
bugs,
so
I
have
to
look
again
through
it,
but
there
are
some
and
there
are
also
yeah
things
I
have
to
compare,
because
also
I'm
not
an
expert
I've
never
translated
in
drupal,
for
example,
so
and
robert
griegos
helped
me
or
to
set
this
up,
and
he
had
more
experience,
and
I
don't
know
how
things
are
supposed
to
work.
D
For
example,
at
the
moment,
if
you
translate
via
the
user
interface,
you
don't
have
the
option
to
directly
translate,
but
it's
automatically
gets
or
becomes
only
a
mod,
a
suggestion,
and
it's
not
clear
to
me
if
it
has
to
do
with
the
change
which
we
made
long
time
ago
for
the
import
so
as
a
side
effect,
for
example.
So
I
have
to
look
again
in
it
so
translating
by
uploading
a
file
works.
D
Fine,
I
think,
but
people
yeah
not
necessarily
know
that
that's
the
best
way,
so
it's
also
a
documentation
issue
and
yeah.
For
that
reason,
I
think
it
would
be
good
if
we
would
find
in
yeah
one
day,
for
example,
in
in
a
month
or
in
two
months
where
we
can
make
schedules
yeah.
A
What
we
really
need
is
someone
to
sort
of
study
the
bigger
issue
of
like
how
can
we
make
this
easier
for
everyone
to
contribute
translations,
and
I
think
you
know
fixing
like
looking
into
why
you
can't
just
do
it
in
the
ui
would
be
good.
I
also
saw
like
a
couple
of
errors
that
sometimes
pop
up
those
little
things
I
think
I
could
commit
to,
but
I
don't
have
time
to
sort
of
sit
down
and
be
like
how
is
this
supposed
to
work
and
same
thing
with
you
all?
A
If
I
haven't
done
a
lot
of
translating
drupal
strings
I've
only
translated
websites
that
you
know
are
running
drupal,
so
yeah.
I
think
there
is
sort
of
a
studying
that
needs
to
happen
there
that
I
am
unable
to
find
time
for,
but
if
we,
if
we
could
set
aside
a
day
to
do
a
sprint,
I
think
that
would
be
good
and
we
could
get.
You
know
some
more
minds
like
greg,
you're,
really
good
at
information,
architecture,
stuff
and
user
experience,
stuff.
A
But
like
figuring
out
how
to
organize
things
so
yeah,
I
think
we
could
get
some
minds
together
and
and
hash
out
some
of
the
problems
with
the
translation
system.
Yeah.
D
D
Yeah
one
other
important
thing
is,
I
I
guess
the
the
forum
issue.
I
don't
know
if
you
remember,
we
had
the
idea
if
we
can
use
the
forum
for
discussions
around
translation
and
it
would
be
good-
and
I
think,
that's
not
possible
at
the
moment
to
have
a
section
in
the
forum
for
translations,
but
then
a
single.
A
Technically
that,
like
architecturally,
all
we
need
to
do
is
make
sure
that
our
taxonomy
terms
can
have
structure
and
we
can
create
those
forums
but
they're
not
going
to
be
displayed
in
a
way.
That's
pretty
because
the
page
that
lists
all
the
topics
doesn't
show
the
indentation.
So
we
can
build
those
places
to
talk
as
long
as
it
look.
You
know
you're,
okay
with
it
not
looking
really
great
for
a
while,
and
then
we
can
have
a
follow-up
issue.
A
A
D
Yeah,
I
think
it
would
be
very
helpful
because
now
I
partially
I
write
emails
to
people
and
they
say
contact
me
in
julie,
but
some
people
do
but
others
not
and
then
also.
I
saw
some
road
opposed
on
the
translation
side
and
they
thought
I
would
get
noticed
about
it,
which.
A
D
A
C
No
okay,
I'm
gonna.
First,
I'm
gonna
bring
up
one.
That
is
a
blocker
of
a
blocker
for
a
thing
that
you
love.
Then
it's
the
the
wordpress
like
sort
of
like
login
page.
C
Okay,
so
I
think
that
we
needed
to
deprecate
a
variable
or
was
it
permission,
a
permission
that
is
yeah
okay,
so
the
issue.
C
C
So
I
have
an
idea,
but
I'm
not
sure
if
people
agree
with
it,
let's
start
with
one
of
the
issues,
because
there's
like
a
trail
of
like
three
at
least
issues
to
your
issue.
So
let's
not,
but
this
one,
which
I
know
is
a
result
of
that
it's
issue
five,
three
one.
E
A
C
All
right,
there's
code,
duplication,
which
is
blocking
me
from
doing
things
useful
things
with
other
things
there,
so
I'm
basically
consolidating
the
generation
of
matrices
into
a
single
function.
So
I
would,
I
would
I
don't
know
like
it
seems
selfish,
because
no
one
else
has
commented
on
that,
but
I
would
like
to
get
it
in
sooner
if
people
agree
or
if
they
disagree.
C
Just
let
me
know
on
the
the
issue
and
then
the
reason
why
I'm
mentioning
it
is
because,
if
you
scroll
to
the
bottom
there's
a
link
to
five
zero
three
zero,
which
is
what
we
well.
I
was
sort
of
like
making
an
entrance
that
a
prelude
to
is
provide
a
mechanism
to
deprecate
permissions.
C
I
guess
yes,
and
so
what
I've
worked
on
my
local
with
is
I
I
have
worked
around
a
deprecated
permission,
so
it's
time
this
permission
is
called
they
will
or
used
by
a
module
or
a
hook.
There
will
be
a
notice
on
status
base
so
that
people
know-
and
I've
also
implemented
some
sort
of
redirect
and
the
reason
why
I
implemented
the
redirect
is
peter's
issue,
which
is
three
seven,
eight
seven,
so
there's
a
there's
heaps
of
related
issues
that
could
benefit
from
that,
but
I'm
not
sure
if
that's
the
right
way.
C
So
all
I
need
is
feedback
on
these
issues.
So
peter
started
this
with
the
problem
that
all
permissions
use
spaces
instead
of
underscores
and
then
everyone's
saying.
If
we
do
that,
then
that's
a
breaking
change,
but
with
the
pull
request,
sorry,
I
didn't
have
a
pull
request.
I
have
it
on
my
local,
with
with
the
fix
that
I
have
for
this
five
five:
zero
three
zero
issue.
C
I
can
tackle
both
issues
deprecating
like
removing
permissions
and
then
what
happens
if
a
another
module
happens
to
be
using
it
and
also
redirecting
permissions
from
like,
provided
an
alias
for
permissions.
So
if
you
have
a
permission
that
it
uses
underscores
instead
of
spices,
it
gets
redirected
to
the
underscore.
Sorry,
if
you
have
one
that
has
spaces,
you
can
get
redirected
to
the
one.
C
It's
basically
backwards
compatible
or
allowing
us
to
move
forward.
So
whoever
has
some
time
to
sort
of
like
have
a
look.
Please
have
a
look
but
that
consolidation
of
the
functions
that
produce
the
mattresses
we've
already
used
it
for
content
types,
I
think,
and
then
vocabularies
and
also,
I
think,
the
contact
module
and
we
basically
duplicate
all
these
functions
all
the
time
so
yeah.
A
Yeah
I
like
that
too,
because
I
think
if
we
provide
a
really
easy
way
for
somebody
to
add
a
permissions
matrix
to
their
interface,
people
will
do
it
more
often,
but
right
now
it's
a
big
pain
because
you
have
to
go
find
the
code
that
does
it
somewhere
else
and
copy
it
and
make
it
work
for
your
scenario
where,
if
it's
like
here,
there's
a
function
that
does
it
for
you,
I
think
it
can
trip,
would
end
up
a
better
user
experience
for
it.
So
I
like
that
idea.
A
I
like
this
idea
of
getting
rid
of
the
spaces
in
the
machine
names,
I'm
not
sure
if
you're
aware
of
this,
but
the
reason
we
have
spaces
is
because
there
was
a
point
in
time
when
there
were
no
keys
and
the
only
thing
that
the
permissions
went
off
was
a
human
readable
name
of
that
permission
and
so
that
what
they
eventually
did
is
they're
like.
Oh,
we
need
a
key,
and
so
then
there
was
they
were
duplicated.
A
A
So
it
is
definitely
a
vestige
of
the
past
that
we
can
get
rid
of.
I
like
the
idea
of
having
sort
of
a
backwards
compatibility
layer
where
we
can
say.
Oh
if
you
say
you
know
a
lot
of
contrib
modules,
use
other
modules,
permissions
and
so
there's
going
to
be
a
lot
of
updating
things
that
has
to
get
done
over
time.
So
having
a
way
where
you
can
say,
oh,
you
have
one
with
spaces,
just
replace
it
with
underscores
and
use
that
instead
is
good.
A
C
Yeah,
so
the
way
that
I
tackled
that
on
my
thing
is
that
you
have
that
I
kind
of
remember
now,
because
it's
been
a
couple
of
weeks
since
I
started
the
process,
so
you
have
a
name
for
the
permission
like
a
key.
It's
his
name,
then
a
description
and
what
I've
added
is
a
new
key
that
is
called
alias.
So
if
you
have
that
alias
it
points
to
another
proper,
canonical
sort
of
like
permission
that.
A
C
C
There's
an
older
issue,
which
I
mentioned
in
the
issue
summary
and
that's
a
triple
three
two,
which
I
suggested
that
we
make
the
permission,
matrices
a
form
api
thing
which
is
of
type
permissions,
and
then
you
specify
a
list
of
permissions
like
an
array
of
permissions,
but
because
I
have
never
worked
on
creating
form
api
elements
and
I
don't
know
what's
involved.
I
just
chose
to
sort
of
like
reduce
the
the
amount
of
code,
duplication
that
we
have
by
introducing
a
new
function.
For
now
it
seems
like
the
easier
road.
A
E
A
Do
both
right
have
the
form,
apl
and
then
call
the
function.
The
only
thing
I
could
see
is
in
the
future
if
contrib
wants
to
call
the
function
and
we
want
them
to
use
the
four
main
elements
instead,
but
yeah,
I
think
ether's,
probably
fine,.
C
Yeah,
either
either
way
any
feedback
on
those
issues,
how
we
should
move
forward
yeah
and
then
again,
if
any,
if
no
one
else
needs
to
sort
of
like
shamelessly
promote
any
issue
that
they're
interested
in.
I
have
another
one:
okay,
all
right
and
bear
with
me,
because
my
computer
is
crawling
today.
It's
5035.
C
Which
is
a
cross
port
of
what
has
already
been
committed
to
d7?
It's
the
the
flat
controls
for
tech,
so
sort
of
like
tech
that
was
committed
recently
and
the
feedback
that
I
want.
There
is
the
way
that
they
introduced
it
in
d7
is
a
settings
php
setting,
but
we
already
have
a
ui
where
we
have
other
flood
control
things
there.
So
should
it
be
just
the
settings,
sorry
just
the
ui,
or
should
it
be
setting
space
b
or
both
well?
C
A
A
Nice,
okay,
interesting
and
this
this
is
in
drupal,
7,
yes,
but
not
in
backdrop.
C
Yet,
oh,
it's
not
in
our
release.
It's
it's
committed,
it's
committed
and
there's
a
taint
record
for
it,
but
but
it
hasn't
been
in
any
release.
There
hasn't
been
a
release
like
in
a
few
months
now,
47.
C
A
B
C
Okay,
so
here's
how
it
works
if
it's
a
feature
that
it's
worth
having,
we
don't
have
to
wait
for
a
d7
release
if
it
has
been
committed
like
if
it
has
actually
been
committed
in
a
dev
version
for
d7.
We
may
release
it
sooner
than
then
because
it
might
take
them
months
right
to
make
a
release,
sometimes
there's
things
that
are
rtbc
which
have
not
been
approved
necessarily
for
for
drupal.
C
But
we
decide
that
it's
good
for
backdrop
and
they've
been
waiting
for
like
years
and
years
rtbc
by
many
computer
members,
which
we
also
include.
If
we
don't
do
any
of
that.
C
We
have
certain
contrib
modules,
though,
which,
like
the
most
prominent
ones,
are
views
or
the
admin
menu
or
path
auto,
which
we
don't
monitor
as
closely
so
it
it's.
Usually
if
it's
bugs
someone's
going
to
report
it
and
someone's
going
to
figure
out
that
hey
this
has
been
reported
in
the
d7
module.
So
let's
grab
the
fix
that
they
also
implemented.
A
I
did
recently
go
through,
I
think
it
was
path
auto
and
redirect.
E
A
So
we've
got
it
all
most
mostly
tracked,
even
though
we
don't
have
all
of
the
projects
on
the
latest
version
right
now,
we
at
least
have
issues
to
make
them
that
way
and
not
every
commit
gets
into
there's
a
bunch
of
stuff
that
you
know
affects
parts
of
drupal,
7
core
that
we've
removed
from
backdrop
like
dashboard
module
or
whatever
and
those
we
just
ignore.
A
And
then
there
are
some
things
that
happen
in
contrib
that
don't
align
with
our
values
like
I've,
seen
a
bunch
of
stuff
in
drupal
7,
where
they're
converting
to
short
array
syntax.
But
we
don't
yet
have
that
as
part
of
our
coding
standard,
so
we'll
exclude
that
commit
from
ours
until
that
gets
in.
So
there's
some
just
a
little
bit
of
review
that
happens
on
all
the
commits
that
are
in
the
drupal
project
before
they
get
merged
into
the
backdrop
project.
C
Yeah
and
there's
a
there's,
a
mix
of
small
changes
which
are
like
straightforward
and
there's
bigger
changes
or
components
like
views
which
are
more,
you
know
elaborate,
which
need
more
testing
and
and
it's
basically
it's
not
hard.
It's
most.
You
know
tedious
and
time
consuming,
but
it's
straightforward
how
to
do
it
or
that's
my
experience
as
well.
At
least
sorry,
it's
just
it
needs
time
to
get
done.
Once
we
have
more
more
hands
on
deck,
it
will
happen
faster
sooner.
C
C
C
C
So
so
some
some
of
the
things
start
getting
you
into
rabbit
holes
like
the
the
second.
I
think
there
was
a
second
issue
that
was
mentioned
again
at
crossport
today
and
we
have
gotten
rid
of
stub
stub
entities
in
in
d7,
so
there
was
a
function
that
was
saying
something
something
stub
entity
create
whatever,
and
we
got
rid
of
that
and
we
have
a
change
record
for
that.
But
there
was
also
a
bear
with
me
field
test,
create
stupidity
which
we
didn't
provide
a
backwards
compatibility
which
is
in
that
change.
C
Sorry,
the
d7
change
which
we
need
to
bring
in
so
my
first
reaction
was
that
oh
there's
a
function
here,
do
we
have
a
respective
function
for
us
and
assets
the
api?
I
couldn't
find
anything
which
led
me
to
the
commit
which
did
the
changes
and
we
took
care
of
the
main
stub
create
thing,
but
not
the
test,
one,
but
again
it's
all
very
straightforward
and
it's
a
good
use
case
so
team.
C
Maybe
it
could
be
a
snap
what
you
call
a
virtual
user
group
thing,
because
it's
not
always
like
it's
not
always
one.
Two
three,
like
fix
that
it's
usually
try
to
find
similar
bits
of
code
between
similar
files,
which
are
basically
90
of
that
between
d7
and
d8,
and
the
chains
and
then
c
take
that
change
one
at
a
time
and
usually
there
might
be
a
function
called
drupal
do
something
and
we
have
a
respective
backdrop
do
something.
So
that's
all
you
have
to
do
change
it,
maybe
add
a
parameter.