►
From YouTube: Backdrop Weekly - Nov 8th
Description
Today’s development agenda: http://bit.ly/2RrucmP
A
All
right
we
are
on
air,
it
is
Thursday
November
8,
and
this
is
a
meeting
to
check
in
on
active,
to
move
out
the
tasks
for
a
backdrop
CMS
before
we
get
into
tasks.
I
did
just
want
to
reiterate
a
discussion
we
had
in
the
project
management
committee
about
GPL
version.
3
finances
lots
before
meeting
too,
but
in
case
anyone
missed
that
one
back.
A
Many
everybody
agreed
that
we
should
make
sure,
but
as
flexible
as
possible
and
so
remaining
tasks
for
that
or
to
update
the
documentation,
in
the
backdrop,
contribute
about
how
and
when
to
use
a
GPL
version,
3
contributed
project,
and
then
that
way,
people
who
need
to
or
have
clear
information
on
how
to
do
that,
including
a
link
to
the
license
file
for
GPL
version
30
instead
of
just
version
2.
So
that
I'll
try
and
do
after
this
meeting,
unless
somebody
else
really
wants
to
do
it.
A
Alright,
since
our
last
weekly
meeting,
we've
got
three
new
context
that
looks
like
one
called
footnotes:
one
called
flipy,
which
is
a
personal
favorite
of
mine
and
one
called
mini
CSS,
which
is
main
theme
so
I
love,
seeing
new
themes
and
they
contribute,
which
is
great
flippy,
is
actually
a
project.
We've
been
waiting
for
for
a
backed-up
seen
as
to
org,
because
we
wanted
to
use
that
for
our
showcase
section,
so
people
can
just
hit
next
next
next
and
browse
get
all
of
the
sites
in
the
showcase.
A
A
That's
a
two
number
442
for
complete,
update,
go
ahead
and
watch
the
design
meeting
from
about
an
hour
ago
and
the
other
one
is
updating
the
homepage
demo
link,
which
is
number
four
22
and
there's
also
a
detailed
explanation
of
how
that
will
work
in
the
design
meeting
is
love.
So
if
anyone
wants
a
more
complete
update,
you
guys
can
check
the
design
meeting,
I'll
watch
it
or
jump
to
my
playthrough
a
little
bit.
A
So
that's
all
of
the
high-level
items
for
back
deck
semester.
Org
normally
Nate
would
be
here
to
do
a
progress
support
on
doctor
up
CMS
itself,
but
he
is
currently
on
the
other
side
of
the
country.
Doing
an
all-day
training,
I
think
today.
So
he
asked
me
to
go
through
the
items
I've
done
my
best
to
take
it.
He
got
the
currents
of
speech
issue,
but
I
might
not
be
completely
up-to-date
on
all
of
them.
So
if
you
get
someone
I
do
feel
free
jump
in
alright.
A
So
let's
start
with
issues
or
backdrop,
one
point
eleven
point:
three
I
think
it's
our
next
version
that
comes
out.
We
have
one
issue
to
add
three
to
mine
color
schemes
for
basis.
He
also
talked
about
that
and
the
design
meaning,
but
basically
we
need
to
run
through
that
the
colors
in
there,
through
an
accessibility
checker,
to
make
sure
that
the
contrast
is
high
enough.
If
anyone
knows
how
to
do
that
or
wants
to
do
that,
we
could
definitely
someone
help
moving
that
issue
forward.
A
A
We
have
one
other
bug
report.
The
info
status
message
cost
a
little
bit
of
a
design,
its
problem
on
an
unrelated
page.
That's
issue,
30305.
That
issue
is
our
TBC,
which
is
great.
That
means
that
it'll
be
included
in
our
next
release,
which
hopefully
will
come
pretty
soon
and
if
anyone
is
interested
in
all
of
the
other
issues,
there's
five
with
the
one
eleven
point
three
milestone
have
that
they're
available
for
people
to
take
a
look
at
if
you
want.
A
A
It's
just
someone
rested
for
requests
on
it,
so
you
aren't
able
to
do
that
or
willing
to
you
can
ping
someone,
maybe
in
hitter
and
find
out
if
you
can
find
someone
again
in
issue
fix,
but
those
are
all
kind
of
like
low-hanging
fruit
like
oh,
we
would
love
to
get
these
six
issues
on
that
milestone
all
right.
Our
next
minor
least
one
@y
is
due
out
January
15th.
That
means
we'll
be
damned
first
practice.
A
I'm
exciting
issues
on
a
buck,
for
that
there
is
issue
with
early
2018,
which
was
funny
that
that
might
get
in
in
2019
what
that
is
adding
core
update
using
long
term.
We
want
to
have
the
core
updates
the
automatic,
but
the
first
step
was
to
make
them
be
manual.
111
includes
a
hidden
button
that
will
let
you
update
your
site
manually
and
one
plug.
A
Another
thing
we
want
to
do
is
issue
in
1992
just
package
signing,
and
that
makes
sure
that
the
file
that
you
downloaded
to
your
site
is
the
file
that
we
wanted
you
to
download
from
your
site
and
that
nothing
else
has
gotten
in
the
middle
and
delivered
anything
naughty
to
you,
and
so
that
is
coming
along
pretty
well.
We
already
have
one
with
the
concept.
Looking
there's
another
one
recommended
on
the
for
request,
so
I
think
that'll
probably
get
in
with
112.
It
would
be
great
and
we've
got
two
possible
ways
to
get
that
done.
A
One
of
our
oldest
issues,
issue
number
37
tags
for
modules,
I
created
for
us
a
while
ago.
Apparently
it's
not
working
there's
some
logic
in
there
that
it's
doing
stuff,
it's
not
supposed
to
do.
I'm
gonna,
try
and
take
a
look
at
that
later
figure
out
what
the
issue
is
and
if
we
can
get
that
results.
I
would
love
to
see
that
get
in
this
issue.
Number
37
is
a
Minimum
Viable,
Product
sort
of.
A
The
major
one
here
is
that
if
we
can
get
tags
associated
with
each
module,
not
only
can
we
use
the
type
search
on
the
modules
page
to
find
them,
but
it'll
give
us
a
better
way
to
filter
the
module
listing
on
back
type
semester,
org
and
in
the
project
installer.
In
order
to
find
the
projects
you
want.
So
this
doesn't
necessarily
improve
the
month,
the
existing
modules
page
as
much
as
it
will
improve
our
ability
to
find
projects
in
the
future.
So.
B
A
Think
that
it's
still
pretty
important,
even
though
isn't
as
big
as
an
overhaul
as
we
wanted
all
right.
The
next
issue
is
one
of
my
personal
favorites.
It's
one
thousand
five.
This
is
adding
options
own
into
court,
so,
instead
of
having
a
massive
text
field
into
which
you
type
a
string
and
then
a
vertical
pipe
and
then
another
string
and
one
supposed
to
be
key
when
I
supposed
to
be
a
label
for
a
select
list
or
instead
of
radio
buttons.
A
Now
it
has
this
beautiful
interface,
where
there's
actual
text
fields
where
you
can
decide
to
define
the
keys
or
Matt
you
can
order
them.
It's
a
huge
improvement
over
the
giant
boxes,
which
you
type
magic
strings
and
not
something
that
existed
for
a
webform,
various
versions
of
Drupal
and
backup
amounts
and
then
that
we're
applying
to
the
field
UI.
So
I
am
really
looking
forward
to
that.
A
The
next
one,
which
is
a
huge
issue
at
number26
32,
is
adding
field
of
all
file
types.
So
in
backdrop,
files
are
already
an
entity
type
which
allows
them
to
be
capable
and
field
about,
but
we
don't
yet
Harvey
during
the
face
set
up
to
make
them
beautiful,
and
so
this
is
taking
that
field
about
interface,
from
Biman
soul
in
triple7
and
putting
it
into
backdrop.
That
is
not
a
great
user
experience
as
it
is,
and
so
we're
trying
to
do
a
little
bit
clean-up
on
the
file
and
the
interface
when
it
goes
into
backdrop.
A
It
looks
like
one
woman's
been
doing
a
bunch
of
work
on
that
he's
asked
for
some
feedback
on
the
current
law
request
to
see
how
much
of
what
is
there
we
actually
want
included
in
back
draft.
Is
there
anything
that
we
could
clean
up,
not
only
in
terms
of
your
in
terms
of
the
amount
of
code
that
were
calling
other?
So
if
anyone
wants
to
give
that
a
test,
I
think
you
thought
could
be
very
welcome.
I'm,
also
looking
forward
to
giving
that
one.
B
A
A
Our
focus
is
pretty
much
on
this
issues
I
just
mentioned,
but
if
there
is
something
else
you
would
love
to
see
it
backed
up
and
you
are
motivated
to
get
it
done,
bring
it
to
our
attention
and
we'll
throw
it
on
the
agenda
that
we
talk
about
every
week
and
if
it
looks
like
it's
close
enough
to
get
in
and
there's
a
lot
of
people
who
agree
that
it's
a
good
improvement,
we
can
definitely
suffice.
Leave
it
for
112.
A
B
And
there's
one
to
get
that
might
be
worth
mentioning,
so
we
should
be
keeping
the
libraries
that
partly
libraries
that
we
built
with
ship
with
core
after
died,
so
issue
33:55
is
for
ckeditor
and
there's
there's
a
couple
of
things
that
the
new
versions
bring
some
new
features,
but
we
decided
that
what
we
do
is
we'll
take
one
step
at
a
time.
So
the
first
thing
is
to
update
ckeditor
for
this
release
and
then
for
1.13
will
aim
to
add
any
itches
and
there's
also
another.
A
B
33:55
and
and
then
there's
another
issue
for
updating,
jQuery
and
jQuery
UI,
so
we
are
using
1
dot,
2
X,
+,
3
dot.
X
is
out
at
some
point.
We
should
consider
I'm
not
saying
for
1.12,
but
at
some
point
we
should
consider
updating
2
dot
X,
which
has
a
compatibility
like
companion
library,
account
remember
what
is
it's
called
sort
of
like
a
sheath
that
you
can
add
so
maybe
for
for
the
next
1.13,
we
should
aim
to
update
a
jQuery.
A
Alright,
so
I
know
what
jQuery
and
jQuery
UI
every
time,
there's
a
major
change
to
that.
It
requires
a
lot
of
testing
and
rewriting
a
bunch
of
stuff
in
core.
So
that's
something
that
we
would
definitely
want
somebody
with
a
lot
of
JavaScript,
or
at
least
jQuery
experience
to
devote
to
testing
and
working
on
making
sure
we
get
that
right.
So
you
can
edit
or
I'm.
B
B
A
B
Be
five
dot,
X
version
that
came
out
and
we
were
not
finding
a
thing
to
update
to
that,
because
there
are
changes.
Major
changes
there
at
account.
Remember
I,
looked
at
it
maybe
a
year
ago,
but
yeah
with
what
these
tickets.
What
we
could
do
is
because
they
are
ongoing
tickets.
We
never
close
them
like
we
we
implement
that
and
then
we
keep
them
open.
It,
maybe
add,
add
a
series
of
tests
that
we
need
to
perform.
A
I
think
maybe
just
doing
like
a
brainstorm
session
with
a
couple
of
people
to
kind
of
say:
okay,
what
are
the
things
that
are
most
likely
to
break
and
make
sure
that
those
things
still
work
like
tests
and
autocomplete
and
tests
I,
don't
know
a
modal
a
test.
You
know
just
like
a
list
of
the
things
that
we
think
that
we've
done
a
bunch
of
stuff
with
it
might
need
a
little
extra.
Yes,
I,
don't
know
what
those
are
but
I
think.
A
B
A
B
A
A
B
B
A
B
A
Voice,
so
that's
all
I
have
for
doctor
up
itself.
It
doesn't
look
like
Jeff
or
land
are
here
today.
Sameer.
Can
you
do
an
update
on
backup
for
good,
but
we
do
have
a
public
issue
queue
if
anyone
has
any
time
and
wants
to
devote
any
resources
source
on
that
project.
This
is
using
that
key
done
under
the
general
just
general
discussion.
We
have
one
issue
that
had
been
talking
about
the
last
few
weeks
about
security
releases
for
concern
projects,
I
change
that
a
little
bit
bit
speaking
with
a
couple
to
do
items.
A
A
So
in
something
writing
the
documentation
in
that
place
is
a
good
first
place
to
do
it,
because
people
sometimes
needn't
maintain,
is
check
there
to
see
what
they
need
to
do
it
for
their
stuff.
I
do
think
long
term.
It
would
be
great
if
we
could
get
single
signups
set
up
on
markup
seamless
at
work,
Aniki
added
into
the
info
file
for
maintainer,
and
then,
if
your
name,
your
login,
on
backed
up
CMS
or
matches
the
name
in
that
info
file,
you
can
grant
you
access
to
edit
that
note
yourself.
A
So
there's
a
couple
of
different
pieces.
We
need
to
get
there.
Are
you
doing
an
in
profile,
but
the
single
sign-on
is
github,
I?
Think
so
you
can
verify
you
are
that
user?
It's
also
really
important.
So
I
put
it
to
do
here,
I'm,
getting
single
sign
up
working
for
the
clips
Anessa
or
single
sign-on
with
github,
and
I
think
that
there
has
been
a
lot
of
work
in
that
area.
A
A
A
Well,
I've
got
a
lot
of
two
items:
I've
got
things
I
want
to
test
that
are
coming
along,
I'm
gonna
go
and
get
that
oh
one
thing
I
did
want
to
mention.
I
went
in
to
go.
Look
at
the
Wikipedia
page
today.
It
looks
amazing.
I
know
you
did
a
lot
of
work
on
that
I,
don't
know
I
think.
Maybe
Tim
was
involved
in
rewriting
that
too
so
I'm
gonna
edit
room
work
on
that.
Just
let
me
say
really
great
job.
It
looks.
It's
really
thorough.
It's
a
bunch
of
references.
It
looks
great.
So
what.
A
B
B
A
B
I
think
they
have
links
with
sort
of
like
see
how
we
have
the
links
that
the
report
this
as
spam.
So
if
people
read
something
and
they
see
something
that's
out
of
place,
they
can
report
an
article.
Maybe
too
many
people
reported
us
in
Jim,
then
yeah
if
they
had
legitimate
or
legitimately
looking
reasons.