►
From YouTube: Backdrop Weekly - Jan 10th
Description
Today’s development agenda: http://bit.ly/2VtYvvP
A
B
Hey
all
right
today
is
January
10th.
This
is
a
meeting
to
check
in
on
active
development
tests
for
backup
CMS
before
we
get
into
all
the
exciting
stuff.
That's
going
on
for
the
next
bug,
fix
and
minor
release.
I
want
to
talk
about
a
couple
of
things
that
we're
doing
for
the
websites
backdrop
CMS
org.
We
have
two
things.
B
We
really
want
to
try
and
get
done
about
the
same
time
as
one
twelve
comes
out
so
we'll
see
if
that
happens,
or
not
the
modules,
the
themes
and
layouts
pages
are
getting
reworked
number
one
to
make
them
look
nicer,
but,
more
importantly,
to
make
them
more
usable.
So
as
people
are
trying
to
evaluate
backdrop
to
figure
out,
if
it's
good
enough
for
them
to
use,
you
know
to
upgrade
for
an
existing
site
or
to
start
fresh
on.
We
want
to
make
that
process
more
straightforward
and
that
I
have
a
pull
request
on
my
computer.
B
It
needs
to
get
pushed
up
and
tested.
So
we'll
see
how
that
goes.
The
next
one.
We
did
talk
about
it
in
a
lot
more
detail.
I,
don't
think,
was
the
last
design
meeting.
It
was
to
design
meetings
ago.
So,
if
you
want
to
hear
more
about
that,
you
can
watch
that
video
and
in
the
community
outreach
meeting
we
just
had
in
the
last
hour.
We
also
talked
about
replacing
the
button
on
our
home
page.
B
So,
if
you're
interested
in
how
that's
going
go
ahead
and
watch
the
video
from
the
last
hour,
so
that's
over
working
on
backrub
semester,
org
and
then
Olaf
I
noticed
you're
here,
I'm
gonna,
try
and
summarize
what's
going
on
with
localized,
but
if
you
want
to
give
an
update.
You're
definitely
welcome
to
do
that
too.
B
A
A
Sometimes
it's
a
there's,
a
lot
of
conditions
on
to
which
you
know
it's
been
mixed:
mixed
results
between
different
users,
but
any
case
we
know
what
the
problem
is
and
that's
that,
where
person
these
info
files,
that
we
should
be
parsing-
and
so
that
would
be
great
if
we
can
get
back
fixed
so
that
when
one
that
12.1
that
12
comes
out
and
people
start
using
the
UI
options
to
have
back
drops
of
update
that
it
works
all
the
time.
So
that
issue
is
number
300.
A
There's
like
30,
447
and
I'd
say:
that's,
that's
probably
the
biggest
thing
that
we
have
to
fix
before
when
that
call
comes
out,
and
we
can
fix
that
in
111
for
because
it's
an
existing
problem
and
111
actually
can't
self
update
as
well.
It's
just
not
sure
me,
the
user
interface.
So
alright,
that's
our
big
item.
I,
think
other
things
that
are
worth
calling
out
for
111
for
include
adding
predefined
color
schemes
to
basis
that's
3209.
A
That's
been
a
long
issue
for
all
of
the
1.11
release
that
we'd
like
to
have
color
schemes
just
shipped
with
basis,
there's
going
to
updates
on
that
issue.
Although
we've
kind
of
decided
they'd
omits
been
stuck
in
and
a
loop
for
so
long,
but
we'll
just
put
in
basically
what
we
have
as
soon
as
it
gets
any
kind
of
review
whatsoever,
and
just
say
it's
good
enough
for
now,
and
we
can
change
it
later
if
needed.
A
Also,
if
you
check
out
the
111
for
milestone
on
github,
there
are
currently
seven
rtl
issues
right
to
left
language
issues
that
have
been
filed
by
a
new
user
Shah
Baba.
Thank
you
for
creating
all
of
those
issues.
Regarding
backdrop,
not
displaying
correctly
in
right-to-left
languages,
it's
been
very
helpful
in
all
of
those
issues.
It
would
be
lovely
if
we
get
them
reviewed
and
merged
into
backdrop
as
soon
as
possible.
A
Best
stone
our
minor
UX
improvements
and
well
actually,
that's
it
just
minor
UX
improvements.
All
of
the
bug
fixes,
though,
are
still
in
the
111
for
milestone
because
they
can
be
fixed.
It
would
be
preferable
to
fix
them
in
both
versions,
rather
than
just
one,
not
12,
so
that's
it
for
111
for
at
least
112
the
release.
That's
coming
out
in
five
days.
Some
minor
updates
here
on
progress.
A
We
have
a
very
minor
I'm,
not
sure,
quite
if
it's
an
API
change,
just
like
behavior
change
in
that
the
classes
that
you
specify
in
views
now
like
CSS
class
compliant
now
allow
underscores
and
that's
issued
34-28.
That
issue
was
merged
this
past
week
that
matches
a
bug-fix
that
we
put
into
the
previous
bug-fix
release.
That
underscores
were
not
being
allowed
inside
layouts
and
when
we
fix
it
inside
of
layouts,
we
said
we
should
also
fix
this
in
other
places,
like
news,
and
so
that
is
a
behavior
change.
A
It's
pretty
unlikely
that
somebody
would
have
put
in
underscores
into
their
used
custom
class
names
and
then
accepted
the
underscores
getting
converted
to
hyphens.
So
I
think
that
the
risk
there
is
really
low-
it's
mostly
kind
of
an
expansion
to
make
it
so
that
underscores
you're
not
supported
as
previously
it
we're
not.
A
Let's
see
there
is
an
issue
that
is
open
that
adds
additional
configuration
options
to
the
search
block
that
is
issued,
2923
I'm,
not
sure
about
this
one.
It's
kind
of
it's
it's
new
functionality,
so
I'm
not
totally
sure
if
it's
something
that
we
should
be
pushing
in
right
now,
although
it
has
seen
several
rounds
of
reviews,
it's
pretty
well
tested,
I,
don't
know,
I.
Think
if
we're
feeling
really
really
confident
about
that,
then
you
know:
let's,
let's
go
ahead
and
roll
with
it.
B
It's
it's
minor
and
self-contained,
and
it
provides
a
lot
of
utility
like
that's
something
that
people
want
to
change
a
lot.
The
behavior
of
the
search
box,
so
I
think
it
was
also
super
close
on
the
last
release
and
it
got
bumped
from
a
feature
to
a
task
at
the
end,
because
we
thought
we
would
have
time
to
get
it
in,
but
then
we
just
had
a
little
extra
feedback
at
the
end
that
made
it
not
ready
in
time.
So
I
think
it's
probably
fine
to
get
in
this
time.
B
Again
is
a
task
in
our
future,
but
if
you
want
more
reviewers
on
it,
I
think
that's
also
something
we
can
arrange.
It's
a
pretty
straightforward.
You
know
log
into
sandbox,
make
sure
it
works,
run
tests
make
sure
they
pass
sort
of
issue.
B
A
A
This
fits
in
under
qualifications
for
UX
improvements
and
also
pretty
unlikely
to
break
anything
just
adding
images
to
the
to
the
admin
Clark.
It
looks
really
nice
it
look.
It's
a
really.
Actually,
it's
not
a
new
issue
at
all.
It's
been
open
since
2016,
but
yeah
it
kind
of
came
from
nowhere.
That's,
but
no
we're
actually
I
mean
Jen.
A
B
A
So
let's
see
there's
a
couple
of
more
issues
in
the
1.12
milestone,
none
of
them
particularly
critical,
all
just
kind
of
nice
to
have
things,
so
you
can
check
out
the
1.12
milestone
alt,
although
there's
only
seven
issues
in
there,
including
two
of
the
ones
that
we
mentioned
just
now,
yeah
it's
kind
of
expected,
because
we
only
have
five
days
before
they
release
like
the
amount
of
stuff
that
we're
doing
it
to
one
or
twelve,
is
fairly
minimal
right.
That's
the
way
we
like
it.
A
How
it
should
be
Rutland?
What
oh?
No,
it's
usually
like
this
after
the
code
freeze
or
under
the
standards
yeah
so
anyway,
that's
it
for
the
product
update.
It
should
be
all
told
of
fairly
quite
next
couple
of
days
on
Tuesday
the
day
that
we
do.
The
release
will,
of
course,
make
the
issue
for
creating
all
of
the
releases
schedule-wise.
B
A
Actually,
I'm
not
sure,
that's
even
a
good
idea,
because
that's
5:00
p.m.
like,
even
when
we
would
start-
and
we
probably
wouldn't
even
do
it
until
like
6:00
or
7:00
p.m.
and
we're
Pacific.
So
at
least
everybody
to
east
of
us.
That's
even
later
so
I
mean
we
don't
want
to
be
making
releases
at
like
10:00
or
11:00
p.m.
you
know.
It's
too
late
at.
A
B
It's
going
to
be
pouring
in
California
all
weekend,
which
means
that
Nate
and
I
will
be
trapped
indoors
and
likely
working
on
issues.
So
my
plan
is
to
work
on
the
bug,
fix,
milestone
and
see.
If
there
are
any
kind
of
you
know
reported
bugs
from
other
people
that
have
quick,
easy
fixes
and
trying,
because
I
know
every
time
we
bump
like
100
bucks
to
the
next
bug,
fix
milestone.
I'm
like
we
should
really
put
some
time
on
those
special
ease
up.
You.
E
B
So
this
is
alpha
for
handling
issues
into
milestones.
We
are
gonna,
give
it
a
shot
and
see
how
it
goes
we'll
adjust
as
needed.
So
definitely
give
us
your
feedback
on
what
you
think,
but
we
did
have
a
bunch
of
issues
in
the
last
few
releases,
where
some
people,
myself
included,
would
have
an
issue
and
be
like
I
really.
B
And
we
would
just
tag
it
and
other
people
who
are
trying
to
you
know
responsibly
manage.
The
milestones
are
like.
Where
are
all
these
issues
coming
from
people
are
just
throwing
in
here,
and
so
we
decided
that
we'd
better
if
we
had
a
process
for
getting
something
onto
a
milestone,
and
so
that's
both
for
a
bug-fix
Messam
but,
more
importantly,
for
a
minor
version
milestone,
and
so
we
now
have
a
tag.
This
is
recommended
by
Dec
woman
in
the
issue
queue.
It's
currently
called
the
milestone
candidate
I.
B
Think
it's
the
status
milestone
today,
I,
don't
know
I'm
open
to
changing
the
terminology.
Event
wants
to
call
it
that
long
recipe
for
milestone,
suggestion
or
whatever
else,
but
because
we're
using
contributed
a
I
thought.
My
own
candidate
would
be
nice
match.
Anyway,
what
happens
is
if
you
have
an
issue
that
you
think
is
they're
really
important
or
will
make
a
really
big
difference
to
backdrop.
You
can
tag
it
with
milestone
candidate
and
when
all
of
the
issues
get
bumped
from
one
milestone,
move
to
the
next.
B
Someone
will
review
that
Moscow
candidate
list
and
either
say.
Oh
yes
secondary
opinion
says
this
should
put
it
in
to
the
candidate,
so
we
need
two
people
to
agree
that
an
issue
needs
to
be
a
milestone
Kennedy
before
it
goes
in.
However,
it's
gonna
be
a
little
bit
for
bug.
Fixes
it's
gonna
be
a
little
bit
more
critical,
like
the
only
stuff
that
can
get
onto
that
bug
fix
milestone.
It
is
gonna,
be
either
it's
really
important.
Something
like
you
know,
setting
some
PHP
has
an
error
in
it
or
we
can't.
B
It's
gonna
get
bombed
just
such
as
you
know
that,
and
then
for
the
minor
milestones.
That
is
the
kind
of
thing
where,
if
two
people
agree
that
needs
to
be
on
the
list,
that'll
probably
end
up
in
weekly
meeting
agenda
and
if
every
one
of
the
weekly
meeting
in
Greece
that's
not
important,
it
might
get
bumped
off
so
I
think
well,
we'll
play
it
by
ear
for
a
while
and
see
how
it
goes
with
managing
this
milestone,
and
eventually
we
may
have
that
process
sort
of
like
pmc
review
and
say,
like
hey
PM
see.
B
This
is
what
the
future
factor
looked
like
to
agree.
Yes,
no,
and
how
kind
of
a
discussion
about
that
it
we've
been
pretty
good
so
far
about
getting
those
issues
right
just
by
talking
about
them,
so
I
think
having
it
in
a
public
meeting
where
people
can
discuss
is
probably
better
than
a
private,
key
or
PMC
posture
shots,
at
least
for
now,
but
if
we
ever
get
to
something
where
we
need
an
escalate
to
a
private
conversation,
that's
definitely
an
option
but
I
figured.
B
F
B
To
add
milestones,
there's
no,
like
actual
you
know,
preventive
measures
in
place
right.
The
process
would
be
now
instead
of
adding
milestone,
which,
though
you
have
technically
a
permission
to
do,
you
should
add
the
label
that
says
milestone
candidates.
You
have
a
definition
you're
like
whoa.
This
seems
like
a
really
good
feature
out
of
miles.
You
can
add
the
label
and
then
or
if
you
have
a
bug
where
you're
like
oh,
this
seems
really
serious.
B
You
can
add
that
label
as
well,
and
then
that
way,
one
of
the
bugs
or
issues
that
are
currently
in
any
milestone
get
bump
to
the
next
milestone
will
also
review
that
milestone
candidate
tag
and
say:
okay,
yes
or
no.
If
it's
no
we'll
remove
the
tag,
if
it's
yes,
we'll
put
it
into
the
right
milestone
and
make
sure
that
they
get
slotted,
and
if
it
is
a
feature
that
we
think
is
a
big
enough
deal
that
needs
to
get
into
the
next
minor
release.
B
It'll
probably
also
appear
on
this
list
that
we
talked
about
in
the
weekly
meeting
to
make
sure
that
everybody
in
the
meeting
agrees
that
that's
a
big
enough
feature
that
it
needs
to
get
import.
So
we've
done
that
recently
with
things
like
dashboard
right,
where
somebody
started
working
on
it,
everyone's,
like
oh,
that
should
totally
go
in,
but
just
making
sure
that
we
get
more
visibility
on
the
fact
that
dashboard
is
now
on
this
list
for
113
going
forward.
We
want
to
make
sure
everyone's
okay
with
that
would.
B
A
B
B
I
think
the
readme
is
a
good
place,
because
if
people
are
in
the
issue,
queue
they're
likely
to
read
the
readme
anyway.
I
just
saw
that
landing
page.
So
that's
a
good
place
to
start,
and
then
the
problem
is
like
it's
hard
to
update
things
and
get
when
they're
words
and
not
code.
So
I
think
it
would
be
good
also
to
have
a
more
publicly
visible
place.
B
Maybe
for
you
know
on
backed-up,
see
mr.
burke,
when
we
do
get
that
new
documentation,
section
map
that
would
be
a
good
place,
then
this
will
be
a
good
for
now
at
least
getting
it
written
somewhere,
and
then
we
can
review
it
one
one
three
it's
ready
and
see.
If
that's
working
for
us
or
not
alright,
that
is
all
we
had
on
the
list
for
today.
I
want.
A
B
A
A
It's
a
template
that
makes
sense
for
filing
a
feature
request,
so
very
cool
just
that
we
added
issue
summaries
for
these
four
different
categories,
and
so
now
they
all
have
specialized
templates,
which
is
very
nice,
and
thanks
to
you,
get
hub
abilities
like
when
you
start
typing
this.
You
would
automatically
start
suggesting
other
issues
that
might
be
related,
so
yeh,
some
improved,
tooling
and
improved
using
uses
of
our
tooling.
Also.
C
B
The
label
is
automatically
applied
on
the
right
hand.
Side.
Yes,
so
hopefully
that'll
help
us
get
issues
categorized
with
labels
more
more
often
correctly
and
the
security
issue.
One
there's
template
there.
But
if
you
look
at
the
template,
it
just
says
like
stop,
don't
create
an
issue
here,
which
is.
D
B
Yeah
I
think
I
think
we
could
have
more
jobs
for
the
bot
here.
We're
like
we
could
put
a
delete
me
label
on
it
and
the
bot
could
automatically
delete
any
issue
that
went
in
with
the
delete
me
label
on
it,
and
then
we
can
put
in
that
description
like
this
issue.
If
you
create
an
issue,
it'll
automatically
be
deleted
a
security
issue
and
this
do
it'll
automatically
be
deleted,
but
then
it
might
like
email,
the
security
team
with
the
contents
of
the
issue,
something
like
that.
Yeah.
A
Hugh
yeah
yeah
there
might
be
that
nice
failsafe,
but
not
something
we
probably
want
to
establish
is
the
process.
The
process-
yeah
yeah
warily,
visible
yeah
only
is
failsafe,
yeah,
so
very,
very
nice
yeah.
You
can
now
move
issues
between
projects
now
to
that's
been
a
huge
win,
so
somebody
files
an
issue
against
like
one
files,
an
issue
again
score,
but
it's
actually
a
computer
project
or
control
problem.
We
can
move
issues
between
them,
but
unfortunately
the
permissions
do
that
you're
still
slightly
restrict
or
fairly
restricted.