►
From YouTube: Backdrop Weekly - June 25, 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
B
C
A
D
A
There
we
go
before
we
get
into
what's
going
on
defective
core
itself.
I
want
to
do
a
quick
update
on
contributed
project.
Since
our
last
vector
weekly
meeting
we've
had
three
new
contributed
project
releases.
Officially
exciting.
We
have
a
new
version
of
flux,
remove
module,
webform
calculator
and
conditional
fields
so
exciting
to
see
those
come
out
coop.
B
116
3
is
their
current
release
of
backdrop
oversee
one
16.2,
as
our
current
release
of
backdrop
and
116
3
will
be
the
next
bug
fix
release.
In
the
past
week,
we've
had
a
couple
additional
fixes.
Merch
done.
We
had
this
issue
relating
to.
When
you
switched
layouts,
you
could
not
remove
blocks
in
the
process
of
changing
the
layout
template.
That
issue
was
44:20
that
was
merged
in
the
past
week.
Also,
rather,
major
improvements
is
this
next
issue
making
views
strings,
translatable
issue
4382.
B
When
we
ported
views
into
backdrop
ages
ago,
translation
had
been
removed,
assuming
that
we
would
end
up
using
configuration
translation
once
that
was
created,
issue
4382
restores
the
ability
to
translate
views
using
a
direct
cross
port
from
what
is
in
Drupal
7.
So
it
turns
out.
We
did
not
use
config
translation,
it's
just
it's
just
using
local
locale
module
same
as
exactly
the
same
as
Drupal
7
are
thinking
there
is
that,
while
config
translation,
we
do
have
that
capability.
Now
that
config
translation
is
made
for
a
simple
use
case
infuses
complex.
B
In
addition
to
that.
More
importantly,
views
already
had
a
mechanism
for
translating
and
it
all
rests
through
locale
module
anyway.
So
in
the
end,
the
translation
mechanism
was
going
to
be
the
same.
It
was
just
the
pathway
that
we
used
to
get
there
so
4382
in
the
name
of
compatibility
and
straightforwardness.
Just
takes
exactly
what
we
having
triple7
andrey
applies
as
a
backdrop,
so
that'll
be
great.
That's
been
merged
into
the
116
branch,
so
it'll
be
in
the
next
bug.
Fix
release
will
finally
have
that
capability
back
in
backdrop.
B
Again,
let's
see
we
next
up,
we
have
an
issue
that
is
of
fair
importance.
That
is
a
regression
in
the
116
branch
itself
that
when
you're
looking
at
the
list
of
text
formats,
the
order
of
text
formats
on
the
administration
page
for
configuring
them
is
not
respecting
the
format
order
and
so
right
now
they're
just
playing
alphabetically
when
they
should
be
ordered
by
weight.
B
It
can
be
very
confusing
because
you're
allowed
to
reorder
them
on
that
page,
but
when
you
save
it
doesn't
appear
that
the
changes
are
saved,
even
though
they
are
so
that
issue
44.
Oh
seven
is
a
visual
regression,
that's
causing
confusion
for
people,
configuring
text
formats
there's
currently
no
pull
request
and
no
code
that
has
been
submitted
for
it
yet.
So
that
is
a
good
issue
that
we
would
like
it
fixed
in
the
near
future
that
doesn't
have
any
assigned
developer
yet
so
forty
four,
oh
seven,
is
something
that
we
could
use
some
help
on.
B
Let's
see
next
up,
Indigo's
Ella
I
think
has
been
working
on
restoring
some
functionality
from
date,
module
yeah
that
date
module
in
Drupal
seven
had
the
ability
to
have
a
pager
that
is
provided
two
views
that
lets
you
go
forward
and
backward
based
on
dates,
and
this
was
important
for
calendar
in
previous
month
next
month.
Type
pagers
and
so
2766
is
porting
that
functionality
into
backdrop
course
date
module.
It
currently
has
a
pull
request
that
needs
review.
B
Jeff
Saren
deputy
asks
that
we
refocus
again
on
improving
some
of
the
automation
tools
that
we
use
and
I
think
that
this
issue
to
automatically
lint
our
code,
that
is
like
checking
against
coding
standards,
would
improve
the
feedback
cycle
for
people
submitting
pull
requests.
The
issue
is
number
32
thirteen,
and
the
suggestion
is
that
we
use
pH
pcs,
which
is
a
code
linting
tool
to
run
automated
checks.
When
all
requests
are
filed,
any
media,
they
provide
feedback.
Saying
hey
this
line,
that
you
changed:
use,
tabs
and
spaces,
for
example.
B
So
the
world
of
linting
on
github
is
changing
rapidly,
though
first
of
all
github
actions
is
now
around
that
makes
so
that
we
can
run
container
based
automation
against
pull
requests
using
github
for
free,
which
is
a
great
built-in
offering
the
kid
hop
started.
Providing
and
in
the
past
week,
github
created
a
new
official
to
love
for
syntax
checking
that
they
called
the
super
linter,
and
so
the
super
linter
is
an
officially
supported,
github
action
that
can
lint
a
half
dozen
languages
right
now,
I
think
maybe
eight
languages.
B
We
still
have
to
write
the
PHP
CS
configuration
files
that
configure
the
way
that
configure
the
rules
that
it
will
use
when
it
does
the
linting
and
when
John
was
looking
at
this
a
couple
of
weeks
ago.
What
done
do
you
want
to
describe
the
caveats
that
you
were
running
into
regarding
like
the
versions
of
libraries
and
how
the
rules
needed.
A
It
so
backdrops
PHP
CS
code
is
for
PHP
SIA
version.
One
Drupal
seven
supports
PHP
cs4
to
Drupal,
8
supports
PHP,
CS,
Persian
3,
and
so
if
we
want
to
go
all
the
way
back
to
version
1,
it
takes
a
like
some
jumping
through
hoops
in
order
to
get
that
version
installed
and
then
that
PHP
CS
fortune
one
doesn't
work
with
PHP
7.
So
our
tests
that
would
test
PHP
7
can't
also
test
the
coding
standards.
A
B
B
B
To
about
half
of
these
look
like
they're
in
needs,
your
views
day
and
the
other
half
have
full
requests
that
need
work.
So
there's
a
lot
of
things
to
potentially
address
just
to
clean
up
our
bug,
fixes
and
pay
down
some
of
our
technical.
That
seems
to
be
where
a
lot
of
our
attention
is
focused
right
now,
1:17
is
the
next
minor
release
of
backdrop,
it'll
be
coming
out,
September
15th
with
feature
freeze
on
September
1st.
B
A
Well,
we
Luke
was
just
an
outreach
meeting
and
it
sounds
like
he's
trying
to
figure
out
the
tools
that
are
available
to
him
for
leading
the
initiative
and
something
to
write
a
little
bit
slow
right
now.
He
said
he
was
gonna
touch
base
with
Jeff
who's,
leading
the
other
initiative
to
try
and
figure
out.
If
there
are
things
in
common
that
they
should
be
doing
but
yeah,
it
looks
like
he's
still
soliciting
the
involvement,
but
things
aren't
moving
incredibly
fast.
Yet,
okay,.
B
A
So
I
might
be
working
on
that
right
now
it
is
almost
done.
The
one
thing
doing
is
I
had
manually
added
the
like
password
reset
link
on
to
the
form
and
rather
than
doing
that,
what
I'm
gonna
do
is
pull
the
local
tasks
and
loop
over
them
and
anything
that
had
a
tab.
That's
no
longer
displayed
as
a
tab
will
end
up
displayed
in
a
bulleted
list
below
the
form.
A
B
Let's
see
separately
from
that,
we
also
merged
in
something
from
117.
That
is
a
design
change
to
the
7
theme
that
the
seven
themes
since
we
redesigned
it
has
been
using
all
uppercase
letters.
It's
been
text,
transforming
fieldset
titles
or
field
set
labels
into
uppercase.
It's
worth
noting
this
in
the
past
week,
we
changed
that
so
that
they
are
no
longer
forced
into
uppercase
letters,
its
issue
41:25
and
the
reason
for
the
justification
for
that.
It
comes
down
to
localization
and
translation
as
well
as
flexibility.
B
That's
text
transforming
to
uppercase,
doesn't
work
in
all
languages,
and
it
also
can
make
localization
difficult
with
characters
that
need
variations
like
them
lots
and
accents
uppercase
variants.
It
doesn't
display
well
plus,
there's
also
space
considerations
that
it
wasn't
making
capital
letters,
take
a
blow
more
space,
then
work.
B
So
that
change
is
already
on
the
one
dot
X
branch,
any
sandboxes,
you
spin
up
fro
free
to
pull
requests
where
they
have
that
change
that
design
change
on
the
backend.
You
might
not
notice
it
specifically,
but
if
one
of
those
things
that
you're
like
something
seems
a
little
bit
different
than
it
had
been,
and
that's
probably
what
it
is,
because
that
affects
almost
every
page
of
the
administrative
interfaces.
B
Okay,
well,
that's
the
heads
up,
then
I
have
there
117
still
wide
open
as
far
as
features
that
could
possibly
be
implemented
in
order
to
move
something
into
the
117
milestone.
We
require
that
the
issue
have
an
advocate
to
promote
it,
and
so,
if
you're
interested
in
putting
something
that's,
my
new
version
of
backdrop
find
an
issue
that
you're
interested
in.
B
D
A
To
have
any
themes
in
decor
I
think
the
plan
was
to
make
the
ones
that
can
trigger
and
then
promote
them.
The
same
way,
we're
gonna,
promote
modules,
in
course,
so
that
they
would
have
a
designated
area
at
the
top
of
the
themes
installed
page
that
had
it
some
kind
of
highlighting
that
was
like
these
were
recommended,
and
that
way
it
would
be
clear
to
people
which
ones
are
actually
gonna
work
on
your
site
versus
which
ones
are
like.
A
Oh
I
just
made
this
theme
and
throughout
and
contribs
to
be
able
to
use
the
code,
and
so
we
have
a
bunch
of
work
to
do
on
the
promoting
things
angle
as
well,
and
that
might
be
something
we
want
to
put
in.
The
next
release
is
to
make
sure
that
Vectra
of
core
can
handle
the
promotion,
putting
a
topless
in
the
whatever
kind
of
color
coding
or
otherwise
indicating
that
section.
A
But
we
also
have
a
bunch
of
work
to
do
on
those
themes,
and
so
it
might
be
good
to
work
on
getting
that
list
of
whatever
those
themes
are
that
we're
going
to
use
and
then
getting
lists
of
things.
We
need
to
do
to
make
them
featured
so
I
think
the
last
time
we
had
a
check-in
on
the
initiative
open
Luke's.
Here
we
created
an
item
that
was
like.
A
A
Oh,
you
have
to
make
sure
you
don't
call
this
function
from
this
file
or
that
you
do
support
this
feature
and
so
I
think
the
first
step
would
be.
What
is
that
list
of
things
we
need
and
then
the
second
step
would
be
what
themes
already
meet
these
requirements
and
then,
after
that,
we
would
have
a
list
of
things
that
didn't
make
the
requirements
needed
it,
but
I
do
like
the
idea
of
getting
the
core
stuff
done
in
117,
since
we
don't
have
a
lot
of
other
things
on
the
to-do
list.
A
D
D
E
I,
don't
think
we
haven't
really
defined
yet
how
the
results
will
be
delivered.
That's
one
of
the
things
we're
actively
working
on
trying
to
figure
out
how
that
is
just
I
supposed
if
it
makes
sense.
Well,
chips
fall.
If,
if
we
want
to
include
a
single
theme
any
time
soon
that
that
sounds
a
little
premature,
I
think
I
think
we're
we're
a
few
clicks
away
and
I.
E
Don't
know
if
that
means
like
weeks
or
what
but
like,
but
like
I,
don't
think
we're
that
far
off
from
an
MPP
well
release
more
than
that
and
I'm,
not
even
sure
what
release
means,
but
but
I
think
it's
got
to
be
more
than
one
I
I
think
it's
got
to
be
three
or
four
of
whatever
it
is
and
and
we're
still
working
on
on
that
now
now
it
might
not
be
premature
to
to
pick
one
or
two
that
that
look
like
they're
gonna
cross.
The
line
I
haven't
gotten
to
that
point.
D
B
D
Of
the
ones
we
have
I'm
not
sure
because
they
do
leave,
we
discussed
a
lot
about
theme
directories
tend
lighter
victories
and
we
have
a
list
in
the
forum
thread,
I.
Think
about
the
first
suggestions
about
external
templates
or
themes
which
we
could
rebuild,
which
GPL
and
I
think
we
need
also
more
feedback
there,
because
now
it's
still
unclear
which
teams
we
want
to
choose
and
but
I
think.
It's
also
quite
clear
that
the
existing
backdrop
themes
are
not
so
ready,
not
only
technically
but
also
design
wise.
E
Yeah
I
agree:
those
are
the
questions,
I,
don't
think
I,
don't
think
I,
don't
think
we're
at
the
point
where
we
have
any
answers
to
the
questions
where
we're
kind
of
halfway
through
the
process
of
determining
what
the
questions
are
but
but
that'll
come
soon.
I
mean
we're
not
far
from
starting
answers.
I
think
that's
coming
up
imminently,
but
we're
not
there.
Yet
I
was.
A
B
E
Probably
miss
my
thing,
which
would
have
been
kind
of
giving
you
no
feedback
on
on
the
on
the
ready-to-wear
initiative,
but
but
really
the
the
pressing
issue
that
I
have
is
I
I
feel
a
need
for
something
scheduled
where,
where
I
can
somehow
on
a
schedule,
know
everybody
who's
involved,
it
wants
to
be
involved.
It
has
a
saying
so
so
I
was
thinking
about
scheduling
a
meeting.
I
think
I'm,
not
sure
how
to
do
that.
I
had
a
like
one
possibility
would
be.
I've
got
a
weird
schedule
unfortunate,
so
so
I'll
have
to
throw
up.
E
You
know
what
I
I
can
actually
wrap
this
up
and
just
say
that
that
I'm
going
to
put
something
on
the
forums
where
I'll
spew
the
stuff,
in
fact
about
there
I
want
to
try
to
establish
probably
like,
like
a
weekly
meeting
just
for
now
to
to
whoever
wants
to
get
deeply
involved
with
the
ready-to-wear
thing
it.
It
doesn't
have
to
be
synchronous.
It
doesn't
have
to
be
like
a
zoom
meeting
or
a
video
thing.
E
A
Think
look
if
you
can
throw
up
a
time
put
in
this
little
channel
too
so
people
who
are
already
involved
can
see
what
it
is,
and
hopefully
you
can
get
a
feel
for
who
can
meet
them
and
if
it
doesn't
work
like
you
can't
find
a
time
that
works
for
everybody,
but
that
one
of
these
weekly
meeting
times
would
work
for
everybody.
We
could
devote,
you
know
half
or
a
quarter
or
third
or
whatever
one
of
these
meetings
to
that.
If
you
needed
so
yeah,
there
are
some
ideas
but
we're
flexible
on
that
all.
E
Right
all
right,
I
I,
think
I
just
need
to
I
want
to
impose
a
schedule,
mostly
on
myself.
I
I
want
to
impose
some
sort
of
like
deadline
as
to
when
decisions
are
asked
when
they're
reached
and
and
I
think
the
mechanism
for
for
how
that
communication
happens
is
less
important
than
the
timing
of
that
information
and
so
I'll
just
wanna.
Let
you
know
I'm
going
to
try
thread
my
way
towards
an
answer
to
that.
Okay,.