►
From YouTube: Backdrop Weekly - June 4th 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
A
C
A
A
For
a
way
style
and
Justin
I,
don't
know
if
you're
available
to
introduce
yourself
he's,
muted,
okay,
just
ignore
septons,
also
here
from
Colorado
all
right
so
jumping
into
the
agenda.
We
have
an
exciting
update
from
the
project
management
committee.
Since
our
last
meeting
we've
had
enough
project
management
committee
members
vote
on
the
new
initiative
item,
so
we
had
proposed
a
telemetry
module
being
added
to
core
being
something
that
might
be
good
as
an
initiative
and
making
backdrop
usable
without
requiring
custom
feeding.
A
We
talked
a
little
bit
about
the
theming
initiative
in
the
last
meeting,
so
I'm
not
sure
if
we
need
an
update
from
that
here,
but
maybe
I
was
thinking,
it'll
be
good
to
have
a
section
in
this
weekly
meeting
where
we
could
talk
about
the
initiatives
every
week
to
so
at
the
bottom
of
this
agenda,
I've
added
in
the
initiative
section,
an
area
that
says
update
from
Luke
and
update
from
job.
So
when
we
get
to
that,
we
can
do
that.
It's
not
today,
because
we
just
found
out
their
initiatives.
A
Okay,
let's
see
so
in
terms
of
what
happens
next
announcing
in
this
meeting,
that
the
initiatives
have
been
accepted
or
approved
would
be
good,
and
then
we
had
some
forum
posts
where
the
initiatives
were
originally
written
up
so
go
after
this
meeting.
Those
posts
had
some
comments,
they're
saying
which
ones
have
been
accepted
and
the
ones
that
haven't
been
accepted
have
not
been
rejected.
A
So
that
includes
people
who
are
watching
this
call
later,
as
opposed
to
people,
are
participating
now
and
then,
since
last
week,
we've
had
two
new
contributed
project
updates,
there
is
thesis,
I
think
is
a
theme
yeah,
it's
a
theme
that
extends
basis
and
then
there's
the
select
to
module,
which
adds
better
options
for
select
widgets
in
forums
all
right.
Let's
turn
it
over
to
Nate.
B
There
are
a
couple
of
regressions
in
the
text:
format,
user
interface,
so
we
made
some
changes
to
the
way
the
text
formats
and
editors
are
saved
in
1/16
and
there's
a
couple
of
things
that
are
lingering
there
that
need
to
be
addressed.
One
of
them
is
that
if
you
have
a
disabled
text
format
in
1/16,
we
added
the
ability
for
you
to
see
when
a
text
format
is
disabled
instead
of
just
hiding
it
from
the
user
interface.
But
it's
still
actually
being
there.
B
When
you
disable
a
text
format,
it
stays
within
the
list,
letting
you
know
that
that
format
had
been
there
previously.
But
it's
not
disabled.
If
you
have
a
disabled
format
in
the
list,
but
then
you
save
the
order
of
the
format's
into
something
else,
then
that
results
in
creating
an
empty
format,
which
is
just
a
weird
weird
thing
that
shouldn't
be
happening.
So,
let's
issue
44:19,
indigo,
gsella
and
herb
dual
have
fixed
that
in
the
past
week
and
that
has
just
been
merged
in
just
before
this
meeting,
so
that
issue
has
been
corrected.
B
There's
another
regression
on
that
same
page,
though,
that
when
you
save
the
filters
into
a
different
order,
the
form
doesn't
reflect
the
newly
saved
order
they
actually
are
saved
into
the
new
order.
It's
just
that
the
form
doesn't
display
them
in
the
new
order,
and
so
that
visual
regression
is
highly
confusing
and
and
and
needs
to
be
fixed.
So
that's
issue
44,
o
7,
the
regression
in
the
ordering
and
there's
no
pull
request
yet
to
correct
that
issue.
B
Currently,
there's
a
limitation
that
you
cannot
remove
blocks
when
switching
layouts.
So
if
you
hang
on
I'm,
not
sure
if
I
can
adequately
explain
this
one,
you
should
be
able
to
when
you
switch
from
one
kind
of.
If
you
change
your
pages
layout
from
one
layout
to
another,
you
should
have
the
opportunity
to
remove
blocks
during
that
conversion.
I
think
that
that's
the
crux
of
it
issue
is
44:20
&
BW
panda
has
already
submitted
a
pull
request
on
that
one,
and
it
is
already
rgbc
as
well.
B
So
that's
great
lots
of
issues
that
are
getting
bug
fixes
in
one
issue.
That
is
part
of
the
views,
maybe
not
part
of
the
views
cross
ports
but
feature
parity
with
Drupal
7.
This
issue,
4382,
has
to
do
with
translation
within
views
that
it
restores
the
ability
to
use,
localization
or
locale
module
to
translate
strings
within
views
configurations,
and
so
this
was
something
that
had
been
removed
in
the
part
of
the
port
2
backdrop
and
individual
has
restored
that
functionality
in
that
pull
request.
So
that
issue
is
also
our
TBC.
B
B
A
B
It
seems
odd,
it
just
looks
like
a
bug
fix,
but
if
it,
if
it
changes
an
API
or
something
I,
don't
know
we'll
see
about
that.
Okay,
that
issue
is
44:24.
It's
currently
marked
RGB
see.
Maybe
that
could
just
use
some
eyeballs
to
get
into
the
right
milestone.
It
seems
like
the
removing
unnecessary
string
concatenation.
That
sounds
like
a
pretty
minor
thing.
B
A
This
is
not
officially
in
the
117
milestone
for
real,
okay
I
think
it
should
be
there,
but
nobody
else
has
chimed
in
on
the
issue
and
believes
that
this
feature
needs
to
be
included
in
the
next
future.
Release
I
would
like
more
eyes
on
it
to
see.
If
maybe
somebody
else
does
agree
with
that,
but
essentially
it
allows
you
to
check
a
box
on
your
means
page
so
that
right
now
you
can
choose
to
display
like
the
content,
editing
form
and
the
administration
theme.
A
Now
you
can
also
choose
to
display
the
login
form
and
the
administration
theme
and
the
login
form
when
displayed
in
the
administration
theme,
will
like
Center
everything
in
the
middle
of
the
page,
and
it
removes
the
log
in
register
tabs
like
stuff
that
themes
often
really
come
commonly
due
to
their
login
pages.
So
if
you
have
a
website
that
only
people
who
are
administrators
log
in
to
you
don't
need
to
worry
about
theming
those
pages,
you
could
just
check
this
box
and
it'll
use
the
theme
that
they're
gonna
see
unless
they're
logged
in
anyway.
A
Nate
mentioned
this
a
couple
of
weeks
ago
in
a
meeting
and
I'm
like
oh,
my
gosh.
That
would
save
me
so
much
time
because
I
always
end
up
trying
to
theme
the
lodging
registration
pages.
Even
when
I
know
only
my
administrators
are
gonna
see
them.
They
bother
me
like
slightly
embarrassed.
If
they
don't
look,
nice
and
and
I
would
love
it
to
just
be
able
to
check
a
box
and
not
have
to
worry
about
anyone.
A
So
yeah,
it's
ready
for
testing
I
have
I've,
got
some
feedback
on
it
that
it
needed
on
the
login
form.
We
have
to
make
sure
we
still
have
the
links
to
reset
your
password
and
create
a
new
account
and
I
removed
the
tabs,
and
so
I
need
to
add
them
as
links
into
the
block.
So
they'll
be
there
shortly,
and
then
we
can
have
more
testing.
B
Superb,
that's
great,
let's
see
is
checking
the
117
milestone.
We
don't
have
anything
else
in
the
117
milestone
as
of
yet,
however,
the
initiatives
could
start
to
create
issues
into
the
next
milestone
here
in
the
near
future,
so
that
includes
telemetry
telemetry,
conceptually
is
to
report
on
the
way
that
people
are
using
their
backdrop
websites,
so
that
we
can
make
decisions
about
what
features
and
functionality
are
important
with
in
court
and
then
backdrop
without
a
custom
theme
Luke.
B
C
B
Yeah
there
was
a
button
there
that
I
wasn't
sure
whether
or
not
making
a
sentence
or
not.
Okay,
let's
see
one
other
thing
that
came
up
sarin
deputy
or
Jeff
last
week
asked
me
in
zou
lip
mentioned.
He
wanted
to
include
it
in
the
agenda
and
that's
an
issue
that
is
long
been
stuck.
It's
automated
code
style
checks
like
pH,
pcs,
you
know
doing
things
like
checking
spaces
and
tabs
and
indentation
and
variable
names
and
all
of
the
documentation,
those
sorts
of
things.
B
The
issue
is
3213
and
it's
been
blocked
for
a
long
time,
and
my
suggestion
on
this
is
a
jeff.
A--
has
posted
a
great
poll
request
that
might
make
it
work,
but
the
thing
is
that
it's
hard
for
us
to
tell
because
our
yeah
mo
file
for
configuring,
how's,
NCI
works
is
stored
on
that
cop
CMS
org,
and
we
have
to
make
modifications
to
both
core
and
to
backdrop
semester
at
oregon
or
to
make
that
change
and
as
part
of
the
new
packaging
changes
that
happened
just
recently.
B
We
can
now
put
llamó
files
in
our
core
repository,
but
have
them
excluded
from
the
downloaded
packages,
and
so
my
suggestion
is
that
we
should
stop
using
this
yam
will
file,
that's
hosted
on
bankruptcy,
mustard,
org
and
instead
start
including
animal
files
directly
in
the
repository
that
makes
it
so
that,
when
you
file
a
pull
request,
you
can
actually
see
if
the
changes
to
the
ammo
file
do
what
you
expect
them
to
do
like
run
the
automated
code
checks.
So
without
that
I
felt
that
we
would.
B
You
know
the
first
poll
request,
wouldn't
work,
and
then
we
have
to
the
second
one
and
then
the
third
one
and
the
fourth
one,
and
we
have
to
do
it
every
single
time.
We
want
to
try
out
a
change,
and
now
we
can
just
make
a
pull
request
and
see
if
the
change
worked
before
we
merge
it
and
then,
if
it
looks
good,
then
we
can
merge,
it
is
so
I
hope.
A
B
Think
that
yeah,
so
in
order
for
the
mo
file
to
actually
be
read,
you
have
to
have
the
web
poke
enabled
that
makes
a
Zen
see
I
like
gets
notified
when
a
pull
request
is
made
and
that
change
is
already
in
place
as
NCI
is
already
being
notified
on
pull
requests.
And
then
it's
a
good
question
about.
Where
does
it
get
the
mo
file
from
I?
Think
that
if
we
added
a
yeah
mo
file,
it
would
probably
use
it,
but.
B
B
A
B
B
A
B
And
that's
where
we
have
a
bunch
of
other
stuff
right
now,
that's
like
what
is
it
that
we
have
in
there.
We
have
some
stuff.
It's
like
the
settings,
a
PHP
file,
that's
used
by
the
tub,
not
tugboat
demos,
but
the
O's,
NCI
demos,
I,
think,
or
something
like
that.
Like
there's
other
automated
platform
stuff,
that's
in
the
misc
directory
that
we
keep
and
they're
already
so,
and
we
don't
strip
that
stuff
out
it
because
our
expectation
is
people
are
never
gonna.
Look
in
there
in
the
first
place.
So
what.
B
A
B
Trying
to
go
why
you
might
want
to
keep
it
separate,
it's
possible
that
you
know
contribute
also
would
want
to
do
code
style,
shucks,
and
it
might
make
more
sense
for
them
to
pull
down
coder
module
like
to
get
the
PHP
CSS
rules
in
their
own
CI
setup.
Then
it
would
pull
down
core,
but
I'm,
not
sure
about
that,
because
they
might
also
need
to
pull
down
core
anyway
to
like
run
the
tests.
So,
okay.
A
So
if
we
forget
about
developers
and
think
about
people
were
actually
downloading
backdrop
via
the
tarball
are
those
people
gonna
need
the
PHP
CS
files
like
would
benefit
them
for
their
like
production
version
of
the
site
and
their
own
pipeline
to
be
able
to
run
those?
Or
do
you
think,
people
who
are
gonna
be
running
code
sniffing
on
their
production
pipeline?
Aren't
gonna,
be
able
to
do
a
git
checkout
and
get
the
files
that
way.
B
B
So
I
think,
maybe
if
it
was
in
core,
don't
think
we
should
be
stripping
it
out
of
the
tar
balls
because
it
weren't
encouraging
everybody
should
be
using
tar
balls.
They
should
be
using
releases
not
get
check
outs
in
their
production
sites,
so
the
tar
balls
should
include
the
PHP
CS
configuration
wherever
we're
putting
them
because
on
any
production
site
you
should
be
using
really
official
releases
of
everything.