►
From YouTube: Backdrop Weekly Jan 9th 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
All
right
we're
on
air
today
is
Thursday
January
9th,
and
this
is
our
weekly
development
meeting.
Looking
at
the
agenda
for
the
day,
it
doesn't
look
like
we
have
anything
to
discuss
other
than
the
progress
of
vector
up
CMS
itself,
which
is
good,
because
this
is
the
last
meeting
we
have
before
the
release.
So
it's
good
to
focus
on
these
issues
before
we
do
that
I'm
gonna
turn
it
over
Nate
to
talk
about
progress
of
things
since
last
week.
A
B
Let's
see
6
days
from
now
on,
January
15th,
as
well
as
in
the
115
version,
so
two
items
that
we've
got
here
include
26:55,
which
is
related
to
menu
items,
not
sorting
correctly
by
alphabetical
sorting
in
the
admin
toolbar,
and
so
it
actually
turned
out
that
this
is
a
broad
problem
that
we
are
attempting
to
do
sorting
in
the
admin
toolbar.
But
our
generic
sort
function
doesn't
always
work
correctly.
B
So
the
backdrop
sort
function
actually
has
some
deficiencies
in
it
and
so
issued
26:55
reworks
the
backdrop
sort
function
also
in
the
same
process
optimizes
it
a
bit.
It
looks
like
which
is
great.
Last
week
when
we
looked
at
this,
we
said
that
we
needed
to
do
performance.
Testing
house.if
came
in
and
made
it
great
suggestion
there
on
how
that
should
be
implemented
and
then
both
BW
panda
and
her
abdullah
went
through
and
and
benchmarked
it
separately,
both
with
really
pretty
positive
results.
B
C
I
wasn't
following
this
issue:
I'm
aware
of
the
problem,
but
I
didn't
read
all
the
comments
into
account:
the
cases
where
we
specifically
want
certain
items
to
be
listed
at
the
top
of
lists
like
when
you
go
under
views.
We
want
the
Settings
thing
to
be
the
first
item,
even
though
it's
not
alphabetical
has
not
been
taken
into
account.
The.
B
Actual
ticket
the
issue
fixes
the
sorting
in
the
admin
menu
but
doesn't
actually
change
any
code
in
admin
menu
at
all.
So
so
I'm
not
actually
sure
what
happens
with
things
like
those
tabs
I'm
pretty
sure
that
they're
not
affected
in
any
way.
Okay,
because
there
isn't
any
actual
change
to
admin
bar
until.
C
B
B
B
Eventually,
although
yeah
we'll
see
my
initial
thought
is
it's
like
well
we're
kind
of
already
in
this
weird
hybrid
world,
where
we're
not
using
all
the
things
that
were
bad
ideas.
You
know
out
of
PHP
5.3,
but
you're
right
that
will
probably
run
into
something
eventually
that
we
use
everywhere.
That
is
no
longer
supported,
but
yeah
that
that's
a
great
point
and
I
think
weed.
C
B
Ish,
the
great
thing
is:
is
that
I
mean
it's
funny
that
we
postpone
these
things
because
we're
like
a
it's,
not
really
bothering
us
not
really
bothering
us
until
we
get
to
the
point.
If
that
thing
really
is
absolutely
completely
irrelevant
and
we're
like,
oh
that,
wasn't
so
bad,
like
we
I'm
glad
that
we're
not
causing
additional
stress
on
our
community
just
for
the
point
of
like
just
because
we're
supposed
to
you
know
just
because
we
want
to
deprecate
it
or
just
because
we
want
to
get
rid
of
it
when
really
there's
no
particular
need.
B
C
Every
now
and
then
something
creaked
up
in
country
bore
two
libraries
like
the
jquery
once
think
that
we
had
to
fix
at
some
point
I
thing
and
then
another
issue
that
comes
with
countable,
arrays
or
objects.
I
have
an
hour
that
comes
up
at
the
bell.
Yeah
we
treat,
we
treat
those
you
know
as
they
come
do.
B
A
Okay
personally,
like
this,
where
there
was
that
one
thing
where
we
learnt
from
Square
back,
it's
two
curly
brackets
like
we
could
very
easily
put
in
the
coding
standard
stuff,
like
we
always
do
square
brackets
because
of
X.
So
when
that
changes,
we
could
do
something
like
recommended
because
of
X,
but
no
longer
strictly
enforced,
or
something
like
that.
So
that
way,
it's
also
gonna
be
really
hard,
though,
if
like
in
some
places,
we
use
one
and
some
places
we
use
the
other.
It's
gonna
make
that
code
really
messy
and
hard
for
people
to
follow.
B
B
B
Yeah,
we
could
also
I
mean
I.
Don't
think
that
we
should
do
it
blanket
across
the
whole
code
base
it.
We
could
do
things
like
standards
within
like
within
a
function,
don't
intermix,
you
know
one
syntax
and
the
other
and
then,
if
possible,
like
within
a
file,
don't
intermix
and
then
and
then
we
go
through
and
like
iterate
iteratively
switch
things
over.
B
D
C
I
think
I
think
that
it
should
be
a
so
like
one
yeah.
That's
that's
what
Jason
just
said:
I'll
get
it
out.
First
of
all,
we
we
have
hundreds
of
thousands,
if
not
all
my
code
and
like
this,
will
reduce
the
size
of
there
I'm
mentioning
the
size-
it's
not
really
important
in
nowadays,
but
it's
time
that
I
update
the
release
I
like
the
Wikipedia
articles,
and
they
mention
how
much
the
file
size
of
the
extracted
code
base
that
we
have
I
mean
we
use
arrays
everywhere.
It's
gonna
yeah,
but.
A
Most
of
the
time
we're
using
them
we're
using
a
single
square
bracket
that
would
change
to
a
single
squiggly
bracket
and
that's
not
gonna,
be
any
reduction
at
all
yeah,
it's
only
when
they're
defined
and
not
even
because
in
PHP
you
don't
have
to
define
it.
You
could
just
go
or
a
square
bracket
whatever
equals
something
else.
So.
C
B
A
B
A
B
A
B
It's
a
lot
okay,
anyway.
Let's
move
on
from
that
anyway.
Php
that
that
one
issue
that
was
opened
still,
nonetheless,
is
a
really
great
thing.
Just
it's
a
couple
of
lines
and
fixes
yeah
a
deprecated
syntax.
So
we
avoid
some
warnings
in
seven
point.
Four
and
those
are
all
the
two
issues
that
we
have
for
the
114
three.
That
I
think
are
worth
mentioning.
However,
there's
like
five
or
six
other
are
TBC
issues
in
the
one
fourteen
three
milestone
I'll
try
to
go
through
those
and
get
them
are
done
as
soon
as
possible
as
well.
B
C
B
Next,
six
days,
which
are
from
a
code
perspective
fairly
minimal,
we
put
a
new
news
block
into
the
dashboard
to
make
it
that
the
dashboard
could
show
you
news
items
from
dropsy,
I'm
SOR,
that's
delivered
via
a
feed
and
that
there's
an
issue
well,
two
issues.
One
is
that
we
need
to
make
it
this
decision
or
policy
around
what
kind
of
news
should
appear
in
this
feed.
So
that's
issue
625
in
the
backdrop
and
CMS
or
get
shook.
B
You
would
also
be
good
just
to
check
the
current
list
of
three
or
four
news
items
that
we're
currently
delivering
in
the
feed
and
just
make
sure
that
those
things
are
you
know
suitable
for
when
people
update
their
sites
who
were
installed
new
backdrop,
sites
I
should
say
because
updated
sites
don't
change,
but
new
sites
will
we'll
get
this
feed
and
we
just
want
to
make
sure
that
it
contains
actually
helpful
and
relevant
information.
Oh
this.
C
C
B
B
D
A
A
I
think
we
need
to
be
careful
about
that
and
I'm
hoping
that,
like
99%
of
the
time,
those
things
will
go
to
our
site
or
our
blog
or
someplace,
where
we
can
give
people
a
little
bit
more
context
than
just
a
string
of
text
that
somewhere
we
get
to
have
like
a
little
paragraph.
That's
like
this
is
why
this
particular
thing
is
relevant
to
you
and
then
give
them
a
link
to
whatever
external
resource
we
need
to
just
for
a
little
better
framing.
B
C
B
B
Second
issue,
with
the
news
block,
is
that
it's
currently
fetching
on-demand
every
single
page
requests
from
backdrop
CMS
org,
which
could
be
a
potential
performance
issue
for
both
the
backdrop
sites
and
for
backdrop,
CMS,
org,
possibly
and
so
issue.
Forty
to
fifty
four
changes,
the
way
that
the
news
feed
is
fetched
so
that
it
uses
a
cache
first
of
all
and
secondly,
updates
on
cron
jobs
instead
of
on-demand.
B
So
there's
just
some
optimizations
in
there
the
pull
request
is
ready,
but
it
has
new
tests
and
that
new
test
coverage
currently
is
in
passing.
So
we
great
we
can
get
the
test
passing.
But
if,
if
there's
an
issue
with
that,
you
know
and
turns
out
to
be
difficult
to
test
because
it's
pulling
from
the
feed,
then
we
could
potentially
like
rework
those
testers
to
remove
the
parts
that
aren't
worse
than
correctly
so.
E
I
haven't
tested
this
or
look
closely
at
what
you're
talking
about
my
experience
with
the
full
request
is
that
it
would
I
changed
or
updated
the
notifications
and
back
wrap
that
org
it
was
I
had
to
like
jump
through
hoops
to
get
it
to
show
up
on
a
site.
There
was
some
sort
of
caching
going
on
and
I
think
and
that's.
E
A
There's
a
lot
of
layers
like
I
think
the
feed
that
got
generated
is
cached.
I
also
think
that
nginx
has
a
cache
of
it.
Backdrop
has
like
a
you,
know:
anonymous
cache,
it's
like
when
you,
when
you
try
and
make
an
update,
you're
like
okay
I
made
an
update.
Okay,
it
cleared
the
cache.
Okay
cleared
the
nginx
cache,
and
then
you
still
have
to
wait
like
two
hours.
For
some
reason.
I
think
this
set
that,
like
your
site
itself,
like
won't
get
a
new
copy
for
awhile.
C
A
C
A
A
C
D
B
E
A
B
E
B
Okay,
so
those
issues,
and
specifically
that
one
about
the
caching
I
think
is,
is,
in
my
opinion,
the
only
critical
issue
that
we
really
have
for
for
115.
There's
two
other
follow-up
issues
that
we
have
tracking
in
the
115
milestone
that
are
related
to
user
interface,
changes
and
potentially
like
strings
and
descriptions
on
things.
We
added
a
feature
that
makes
it
so
you
can
toggle
whether
or
not
the
hover
effect
applies
to
the
drop-down
menus
that
are
in
Korres,
via
the
smarts,
menus,
drop-down,
library
and
so
issue.
B
B
B
B
A
A
B
B
B
We
don't
like
to
change
a
bunch
of
stuff
right
before
releases
anyway,
so
we'll
get
through
these,
the
114
3
might
issue.
Queue
might
actually
see
the
most
activity
because
those
are
like
outstanding
bugs
that
that
will
affect
both
versions.
So
that's
probably
where
our
attention
will
be
pointed
for
the
next
couple
of
days.
Ok,.
E
B
A
C
E
C
B
B
What
I'd
like
to
do
is
parlay
that
discussion
until
the
planning
session
for
the
next
release.
So
we'll
start
talking
about
backdrop
116
the
next
minor
release
of
backdrop
in
a
planning
session.
Our
initial
thought
on
that
is
that
we
normally
do
it
after
the
release
like
one
of
the
first
meetings
afterwards,
but
we
won't
do
it
on
the
16th
just
because
we
want
to
take
the
time
to
celebrate
our
accomplishments
on
January
16th.
B
We
think,
and
so
that's
where
we
do
a
little
bit
of
a
roadmapping
workshop,
to
figure
out
where
our
primary
direction
is
for
for
116,
and
we
can
also
talk
about
some
of
these
workflow
suggestions
about
how
to
make
it
so
that
we
can
move
more
quickly
and
and
possibly
just
allocate
our
resources
in
an
efficient
way.
So
does.