►
From YouTube: Backdrop Weekly - Feb 27th 2020
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
Is
February
27th?
This
is
our
weekly
developer
meeting
and
before
we
get
started
on
the
actual
meeting,
I'd
like
to
go
around
all
of
the
smiling
faces
that
are
here
and
do
a
quick
introduction
so
for
everybody
could
tell
us
what
your
name
is
and
why
you
came
to
this
meeting.
That
would
be
great.
Let's
start
with
Tim
my.
B
E
A
G
A
Let's
see,
we've
got
two
exciting
new
announcements
from
the
project
management
committee
this
week.
One
is
that
we
have
a
new
cork
emitter
yesterday,
I
believe
Peter
Anderson,
VW
panda
accepted
the
new
responsibility
of
becoming
in
cork.
Emitter
and
Nate
will
follow
up
with
him
shortly
to
get
moving
on
that
which
is
pretty
exciting,
and
just
this
morning
Tim
Eriksson
accepted
the
responsibility
of
joining
the
project
management
committee.
So
we're
gonna
see
some
new
active
basis
which
is
really
exciting.
A
In
the
last
week
there
weren't
any
new
modules
released
for
backdrop,
but
we
have
five
modules
that
had
new
updates.
So
that's
pretty
exciting
I,
don't
know
titled
if
computed
field
photos
swipe
and
metal
reports
all
came
out
last
week,
and
it
looks
like
two
of
those
were
from
Robert
Gary
goes
in
to
or
from
Graham
72
and
one
was
from
Jason
flat.
I,
don't
know
how
to
pronounce
his
online
handle.
A
C
All
right
so
backdrop,
one
15.1.
It's
now
wow,
it's
been
been
over
a
month
since
one
fifteen
came
out
and
we're
still
on
115
0.0,
which
is
good.
That
means
that
we
haven't
had
anything
critical,
that's
been
pushing
us
to
make
a
new
bug,
fix,
release
things
that
are
in
115
one
there's,
as
always
like
a
pretty
good
list
of
things
that
are
prioritized
for
the
next
bug
fix
release.
C
Let's
see,
there's
currently
63
open
issues
that
are
tagged
for
115
one,
so
we
definitely
have
a
slew
of
work
to
go
through,
but
I
don't
actually
have
any
that
that
are
in
the
kind
of
prioritize.
This
is
what
we
talked
about
during
the
meetings
list.
One
exception
to
that
is
that
we
have
some
work
and
discussion.
That's
been
going
on
around
making
our
tests
run
faster
and
I.
Think
two
weeks
ago,
no
just
just
last
week
we
had
a
little
sink
about
how
we
can
get
that
work
completed
its
issue.
C
4306
and
joseph
did
some
work
to
Joseph
left
its
mark
to
optimizer
tests
and
then
was
working
to
actually
speed
them
all
up
like
going
through
and
refactoring
each
individual
test
and
he
separated
back
out
the
refactoring
of
each.
You
know
each
individual
test
so
that
the
thing
that
just
optimizes
the
test
in
the
heads
timers
to
the
tests
is
a
standalone
now
in
that
issue.
4306
and
it
currently
has
the
pull
request,
that's
ready
for
review
and
with
those
kind
of
limited,
more
limited
scope.
C
B
Can
can
I
ask
I,
think
I
raced
this
last
week,
I'm
just
looking
them
up.
There
were
some
RTL
I
think
bugs
that
got
introduced
in
1.15.
Is
anybody
had
a
chance
to
look
at
those
yet
I'm
looking
at
one
ticket
and
it
looks
like
he
closed
the
ticket,
even
though
it
well?
He
said
it
affects
upgrades,
but
not
new
installs
and
then
closed
the
ticket,
but
it
should
still
be.
B
D
C
Okay,
so
let's
move
on
to
116
116
will
be
our
next
minor
release.
That's
where
we
add
new
features
and
functionality.
It's
release
date
is
May
15th,
with
a
feature
freeze
on
May
1st,
so
items
that
we've
got
cooking
right
now
include
this
functionality
that
allows
any
config
value
to
be
overridden
via
settings,
dot,
PHP
and
backdrop.
We
have
settings
that
are
specified
in
settings
that
PHP
and
then
config
that
are
in
config
files
and
currently
places
that
need
to
be
able
to
set
the
values
from
settings
dot.
Php.
C
We
tell
people
or
the
module
developers
to
check
if
there's
a
value
in
settings
and
if
not
then
read
from
the
config
file,
but
that
requires
modification
for
every
module
that
needs
a
place,
a
special
location
for
these
values.
So
it's
not
ideal
and
so
issue.
2805
allows
you
to
override
any
config
value
in
any
config
file
from
settings.
Dot
PHP,
while
also
not
it
also
won't
save
those
values
back
into
the
config
file.
C
So
any
overrides
are
just
kind
of
like
they're
just
inciting
so
that
PHP
and
then
I'll
actually
affect
the
config
files
that
one
at
we
added.
Some
more
extensive
test
coverage
on
it,
herb
Duarte,
be
seated
I've
added
more
tests
and
then
er
DBC.
It
again
so
I
think
that
that's
probably
ready
to
go
at
any
time.
It's.
E
E
So
what
this
does
is
it
works
for
dress
in
Drupal
7,
as
always,
it
takes
at
variables
that
might
have
been
over
it
in
settings.
So
when
you
do
trust
me
get
it
shows
you
what
has
been
said
with
the
database,
but
if
you
do
does
that
include
overridden,
it
actually
shows
you
the
value
of
what
yeah
it
works.
The
same
way
we
see
it
in
in
dress
in
Drupal,
8
and
9.
That's.
C
Yeah
interesting,
okay,
let's
see
so
next
up
is
base
and
sub
install
profiles.
It's
issue
31
74.
This
is
b2b
pandas
issue,
I,
don't
think
there's
been
yeah,
there
hasn't
been
any
updates
on
this
issue
currently
still
needs
code
review
and
since
he's
not
here
to
add
anything
else,
I
think
we'll
just
kind
of
move
on
from
that
one.
C
E
E
C
E
E
So
so,
basically
is
gonna.
Do
it
everywhere.
We
have
a
link
field
now,
but
also
pages
like
the
site
information,
where
you
specify
four
four
four
three
pages
that
would
be
Auto
link.
Now
you
start
typing
the
name
of
the
page
that
you
want
to
put
in
then
it
sort
of
like
finds
the
spotting,
node,
I,
guess
and.
C
Yeah
thanks:
okay,
all
right.
Let's
see
also
new
this
week
issued
10:32
a
new
text
format
configuration
UI,
dr.
Elmont,
seems
to
be
leading
the
charge
on
this
issue.
1032
I
didn't
get
a
chance
to
look
at
this
before
the
meeting,
but
I'm
I'm
excited
that
these
taking
back
up
this
torch
again
that
configuring,
a
text
format,
is
a
crazy
and
weird
thing,
and
this
issue
is
old
and
there's
been
several
different
attempts
that
user
interfaces
to
improve
it
and
the
latest
approach
is
I.
C
Think
configuring
all
of
the
individual
filters
in
dialogues
I
have
yet
to
actually
try
it
out,
but
the
status
is
that
it
it
currently
is
marked
needs
work,
but
da
Coleman
is
soliciting
feedback.
It's
supposedly
testable,
so
I
think
that
means
that
we
can
go
into
the
sandbox
for
that
individual
pull
request
and
try
it
out
and
provide
feedback
on
how
it
actually
works.
So
that
would
be
really
great
to
get
some
feedback
as
to
how
people
like
that
new
approach,
yeah.
E
I
did
give
it
a
quick
spin
in
the
sandbox.
It
works
as
expected.
It's
just
minor
I,
guess
CSS
tricks
here
and
there
just
to
fix
the
buttons
to
be
consistent
with
what
is
happening
in
other
places
like
I,
think
the
field
when
it's
filled
UI
or
the
displays,
what
we
set,
how
they're
being
like
the
widgets
they're
being
used.
So,
yes,
it
was
minor
things,
but
functionality
was
it.
It
seems
to
work
as
inherited.
E
Is
pleased
because
if
you
look
at
the
screenshots
of
a
top
of
that
issue,
the
first
screenshot
there
right
after
the
rolls
you
have
the
enable
filters
which
is
its
checkbox
may
reveal
another
item
in
the
filter,
processing
order
and
another
item
in
the
filter
settings
which
just
makes
the
page
look
huge
and
it's
like
things
appear
and
disappear
without
being
in
the
view
of
the
user.
So
this
sort
of
like
makes
it
everything,
be
in
one
place.
E
So
what
it
does
is
everything
is
a
take.
The
whole
thing
the
enabled
filter
is
the
filter.
Processing
order
in
the
filter
settings
have
all
been
messed
into
a
single
table
which
has
draggable
reorder
both
rows,
and
it's
fro
has
a
button
that
says
configure
which
solve
like
expands
the
table
with
what
was
the
thing
that
we
introduced.
The
field
formatter
settings
thing
nothing
yeah,
and
then
it
works
that
way.
So
it's
sort
of
like
inline
to
what
you're
actually
editing
when
you
just
save
it
in
works.
C
E
E
C
Yeah
well
that
that
always
means
that
there
seems
to
always
mean
that
it
just
needs
approval
and
direction,
and
then
it
will
get
done,
but
without
those
things
then
he's
gonna,
yeah
and
then
move
on
to
something
else.
You
know:
okay,
okay,
let's
see
next
up
is
1575,
provide
a
way
to
re-enable
disabled
text
formats.
Gregory
yearly
advocate
for
this
issue.
You
give
us
yeah.
E
So
this
the
other
way
at
some
point
document
had
enough.
He
does
he's
a
full
of
ways
to
fix
it,
so
he
just
picked
up
on
where
jen
has
left
off
her
for
requests
LS
for
it
was
then
he
is
implemented
and
again
it's
one
of
those
things
that
needs
code
review
interesting.
I
I
didn't
get
to
test
that
at
all.
E
C
A
A
But
the
hope
is
that
this
document
that
we're
working
on
will
help
us
be
able
to
put
in
an
updated
issue
summary
and
help
us
figure
out
what
steps
are
remaining
to
get
from
the
polar
quest
we
have
now
to
something
that
will
be
a
viable
option
for
inclusion,
so
we're
getting
closer
Tim
D.
If
you
want
to
add
something:
you're,
muted,
yeah.
A
A
B
C
E
Yes,
so,
ideally
there
it
will
be,
it
will
allow
both
future
and
past
revisions
to
exist.
The
revisions
will
have
States,
but
there
were,
there
will
only
be
one
version
that
is
published,
which
will
be
the
actual
yeah
and
the
other
ones
yeah.
The
other
ones
can
be.
You
can
tree
off
of
any
revision
at
any
point
and
create
future
revisions,
and
at
some
point
this
can
be
reviewed
and
published
and
replaced
that
the
published
one.
So
that's
that's
so
the.
B
My
question,
my
question:
is
that
that's
what
that
sounds
tomorrow
to
me
like
what
we've
been
talking
about
from
the
UI
like
what
we
expect
for
users
to
be
able
to
do
now,
but
there,
when
I,
read
that
through
the
issue,
I
feel
like
there's
an
underlying
goal,
which
is
to
make
it
easier
for
a
contribute
at
that
we're
not
even
envisioning
right
now
in
the
UI.
So,
for
example,
we
might
just
have
like
the
current
public
version
and
we
might
have
a
future
revision
in
a
past,
but
in
the
future.
A
C
Yeah
well
and
I
think
that
the
biggest
from
that
we
face
right
now
is
that
the
current
revision
is
always
like
the
most
recent
one
is
always
the
active
slash
current
one
and
there's
no
option
to
not
have
that
be
the
case,
and
so
so
there
there's
no
idea
of
state
like
different
states
on
revisions.
And
yes,
maybe
a
contributor
could
handle
that.
But
in
order
to
facilitate
that
there
needs
to
be
the
ability
to
have
a
revision
that
isn't
the
active
one
or
the
current
one.
A
A
H
H
That
there's
currently
no
way
to
have
the
current
revision,
be
anything
other
than
the
newest
revision.
Is
that
just
because
of
how
the
code
that
saves
the
notes
works
because
we
have
a
field
on
the
node
table?
That
is
a
revision
ID,
and
we
could
just
change
that
to
whatever
revision
we
wanted.
Couldn't
we
yes.
C
So
yeah
you're
right
that
that
it's
possible
already,
but
it's
a
hassle.
So
after
the
note
is
saved,
then
you
have
to
go
back
in
retro
update
the
revision
to
make
a
different
one
active,
so
yeah
it's
the
way.
The
note
is
saved
right
now
is
the
problem
that
it
doesn't
allow
when
you,
when
you
save
a
note
and
make
a
new
revision,
it
always
makes
it
the
active
one,
and
the
initial
idea
was
just
to
make
it
so
that
didn't
have
to
happen
all
right.
C
C
C
B
Still
that
okay
I'm
still
not
officially
advocating
for
one
yet
I,
have
one
in
mind.
I'll
bring
that
up
next
week,
but
just
a
reminder
for
anybody
who
wants
to
advocate
for
an
issue
right,
we're
still
doing
that
yeah.
So
please,
if
you
have
a
particular
issue
in
the
issue,
queue
and
they
want
to
work
on.
Let
us
know
or
put
your
name
down
the
I.
B
Don't
know:
okay,
I
want
to
one
sort
of
new
topic
or
in
the
the
proposed
initiatives
a
group
of
us
they're
talking
about
and
have
decided
that
we
like
to
have
a
meeting
there.
Probably
the
thing
to
do
would
be
to
have
a
meeting
outside
of
this
to
just
grab
our
heads
around
what
that
you
know
what
what
that
would
look
like
whether
or
not
it
becomes
an
official
initiative
or
not
I
think
we're
interested
in
having
that
discussion
and
I
just
want
to
mention
that
during
this
meeting.
B
So
if
anybody's
interested,
they
should
go
to
the
forum
under
the
initiative
section
and
and
let
people,
let
us
know,
you're
interested
and
to
make
sure
that
that's
the
best
way
to
handle
that
or
if
it's
or
if
it
would
be
better
to
set
aside
time
during
one
of
the
future
dub
meetings
to
talk
about
it.
Any
thoughts
on
that
well.
E
B
B
Next
next
Tuesday
Jen
is
doing
a
presentation,
I'm
moving
from
Drupal
7
to
backdrop
and
we've
also
announced
sort
of
open
office
hours
the
day
after
that
which
we'd
plan
to
do
anyways,
but
on
that
particular
day,
it'll
be
a
chance
for,
like
you,
somebody's
at
the
session
on
Tuesday,
and
they
want
to
come
back
on
Wednesday
and
ask
questions
they
can
and
get
her
in
slack
or
get
her
in
soon
anyways.
That
was
one
announcement.
B
D
F
D
Newsletter
and
there's
a
website
there,
where
you
can
submit
content
so
I
say
come
across
any
cool
backdrop
stuff,
like
the
things
that
you
just
said.
Tim
would
be
great
to
get
on
there,
so
just
plug
for
that
check
that
out
and
you
guys
have
blogs
or
information
like
Tim
just
said:
let's
get
it
out
in
there
and.
C
Okay,
speaking
of
announcements
and
events
Janice,
since
we're
all
talking
thanks,
Jen's
doing
march
12th
is
the
san
francisco.
Drupal
users,
group
and
jen
is
going
to
be
presenting
on
backdrop
at
that
event.
So
it's
been
a
while,
since
we've
been
in
the
to
a
local
drupal
users
group
to
pitch
back
up
so
we're
gonna.
Do
that
again.
C
Okay,
I
think
that
might
be
it
anything
else.
Okay,
all
right!
Well,
thanks
everybody
great
meeting
and
things
are
ready
for
coming
and
thanks
are
way
out
there
for
watching
keep
on
doing
the
back
drop
thing
and
see
you
guys
on
the
Internet
I.