►
From YouTube: Backdrop Weekly - June 20th
Description
Today’s development agenda: http://bit.ly/2KkAw04
A
We
also
have
a
couple
of
updates
on
backdrop:
CMS
org.
We
covered
several
of
them
in
the
design
and
user
experience
meeting.
So
if
you're
interested
in
checking
out
what
we're
working
on
there,
you
can
go
ahead
and
watch
that
video,
but
we're
not
going
to
talk
about
here
more
exciting,
though
our
translations
site
offices
is
getting
a
whole
bunch
of
activity.
We've
got
new
people,
volunteering
to
maintain
new
translations
of
backdrop,
and
they
have
a
whole
bunch
of
people
actually
using
it
just
fantastic.
We
built
it.
A
B
A
Right,
I
missed
that.
Thank
you
so
yeah
we
did
get
a
new
kinship
project
this
week
as
Clin
ascend,
corresponding
new
references.
I,
don't
know
what
that
does,
but
I'll
check
it
out.
Yeah.
B
A
Okay,
so
moving
on
to
backdrop
neighborhood
here
this
week
he
is
a
client
on
site,
so
I
just
want
to
run
through
some
of
these
issues.
We
have
a
couple
of
well
I
guess.
It
looks
like
just
one
bug
that
we
think
is
very
important
for
issue
one
13:3,
and
that
is
this
views,
is
none
of
operator
broken,
so
this
is
something
that
I
have
a
bunch
of
sites
that
when
we
updated
to
112
five
of
their
like
home
page
views
ended
up.
A
Broken
I've
been
maintaining
this
patch
for
a
while,
and
now
we
have
the
automated
update
thing
in
core
people
are
very
tempted
to
push
it
and
then
things
break
again,
because
core
needs
to
have
these
patches.
This
one
I
think
is
the
one
that
is
most
obviously
affecting
people,
and
so
I
would
love
to
get
it
in
we've
had
a
fix
for
it
now
for
a
very
long
time,
it
hasn't
gone
in
hasn't,
had
tests
the
tests,
the
dribble
Road,
are
really
complicated.
I
had
a
very
bad
day
last
Friday,
because
I
was
gonna.
A
A
Yeah
I
was
very
frustrated,
but
it
is
mostly
done.
I
got
really
upset
and
was
like
I'm
I
got
all
of
them
testing
and
passing,
except
for
two
I
quit
and
I
like
push
my
code
and
Whitlam
went
to
bed
and
I
woke
up
the
next
morning
and
Gregory
had
come
in
in
Compton.
He's
like
I
figured
out.
Why
so
Thank
You
Gregory?
Oh.
B
B
B
B
C
A
And
now
you
have
two
users,
the
default
user
and
the
one
you
created
in
two
notes,
and
so
it's
comparing
the
node
IDs,
but
in
backdrop
we
already
had
two
pieces
of
content.
So
if
you
create
two
new
pieces
of
content,
it's
not
a
4/4,
and
so
the
only
way
I
can
figure
out
how
to
this
was
like,
rather
than
just
creating
one
user.
It
would
loop
count
the
pieces
of
content
in
the
loop
over
to
create
extra
users
so
now
for
users,
those
comparing
the
note
IDs
of
the
content
in
these
range.
A
But
that
means
all
of
the
tests
that
are
like
this
result
should
have.
Two
records
now
has
like
four
records.
So
how
many
go
through
and
like
update
everything
so
who
knew
the
creating
default
content
would
create
such
a
headache
and
test
land,
but
yeah,
so
I
even
tried.
My
first
attempts
why
this
took
so
long
I
tried
to
switch
to
the
testing
profile.
A
It
has
zero
pieces
of
content,
but
because
the
test
uses
the
tags
field,
which
is
part
of
the
default,
a
standard
install
I
had
to
then
create
the
content
type
and
then
create
the
field
and
then
take
the
same
instance
and
apply
it,
and
it
was
just
didn't
work.
I
was
trying
like.
Why?
Is
it
so
hard
to
create
all
the
things
I
need?
So
it
was
like
okay.
A
A
What's
in
the
standard
profile,
I'm
just
gonna
switch
back
to
system
creating
extreme
users
and
see
if
that'll
work,
but
if
anybody
else
wants
to
try
and
do
this
test
better
I
would
definitely
welcome
you
to
do
it,
but
for
now
I
just
want
to
get
it
done
so
that
all
my
sites
aren't
broken
after
people.
Push,
though,
like
my
site
button,
which
I
really
want
them
to
use
so.
B
A
There
who
okay,
so
that
was
my
bad
Friday,
but
let's
move
on
to
things
that
make
us
happy
stuff,
that's
scheduled
for
Bachrach
114.
We
have
a
couple
of
big
new
features.
Coming
field
goal
files.
This
is
a
paw
request.
The
doc
moment
worked
on
I,
think
maybe
two
core
releases
ago
two
minor
releases
ago,
and
it
got
pretty
close.
B
Needs
review
and
testing,
and
eventually
there
will
be
a
follow-up
where
people
can.
Let
me
recap
what
it
is
so
so
d8
has
introduced
this
trusted
host
buttons
thing
to
prevent
some
security
issues
from
happening,
but
they've
done
it
in
a
way
that
its
destructive,
both
when
the
users
are
installing
it,
because
it
demands
that
to
be
set
and
for
existing
sites
because
they
end
up
broken
actually
with
just
the
blank
page.
B
That
says
something
like
an
error
was
that
so
that
issue
is
set
to
be
back
order
to
d7
as
well
and
I'm,
guessing
that
if
they
take
the
same
approach
as
d8,
it's,
it
is
going
to
be
a
headache
as
well.
The
approach
that
we're
taking
in
backdrop
is
less
intrusive,
I
think
we
support
this
setting
and
we
have
a
notification,
look
just
a
notice,
not
an
error
in
the
status
plates,
but
we
do
not
think
force
it
so
that
the
respective
documentation
pages
have
been
created
indeed
or
toward
sorry--but
afford,
but
they're
amplest.
B
The
code
is
there
that
implements
the
feature
via
the
settings
PHP,
and
there
will
eventually
be
a
follow
up.
I
guess
to
allow
that
from
the
UI
as
well,
so
it's
even
less
intrusive.
So
now
we
basically
warn
people
and
ask
them
to
go
and
mess
with
code
with
settings.php.
It
would
be
great
if
we
just
said.
Oh,
you
haven't
said
that,
but
here's
a
UI
to
do
it.
B
So
this
is
pretty
close
and
thanks
document
for
all
the
work,
and
it's
like
it's
really
exciting.
It's
probably
gonna
be
one
of
the
most
exciting
pictures
that
will
come
with
114,
so
most
of
the
basic
things
have
been
done
to
get
a
most
liable
product
out.
It's
just
that
we
need
to
iron
out
a
few
details,
so
the
latest
iteration
includes
being
able
to
drag
and
drop
and
change
the
ordering
of
rows.
The
only
things
that
dr.
B
Elman
has
posted
a
few
questions
now
with
the
outstanding
tickets
with
discussion,
or
maybe
he
doesn't
understand
what
exactly
is
asked
on
him.
So
we
just
need
to
chime
in
the
ticket
and
just
explain
things
or
discuss
on
how
they
should
be
implemented.
There's
a
few
design
questions
as
well
there,
but
they're.
Quite
a
few
of
them
can
be
follow-up
issues
doesn't
have
to
wait
and
I
think
the
soonest
that
we
get
it
in.
B
A
Alright,
so
I
on
the
114
milestone.
We
also
have
a
more
TBD
item
here,
because
anyone
who
is
really
passionate
about
anything
in
particular
is
welcome
to
become
an
advocate
for
an
issue.
You
don't
have
to
be
a
developer.
You
just
have
to
really
want
to
get
that
issue
in
the
core
and
be
willing
to
give
us
an
update
here.
Weekly.
It
doesn't
have
to
be
every
week,
but
just
loving
letting
us
know
how
that
issue
is
progressing
and
hopefully
you'll
be
able
to
bother
people
in.
A
A
You
can
be
an
advocate
for
the
issue
if
you're
wondering
what's
be
an
advocate
for
you're,
welcome
to
search
our
issue
for
any
issue,
that's
tagged
with
a
milestone
candidate
minor,
and
those
are
things
that
someone
at
some
point
in
the
past
has
thought
would
be
a
good
candidate
for
core,
and
if
you
see
anything
in
there
that
you're
like,
oh
obviously,
we
need
this
thing.
I
want
to
get
it
done.
That
would
be
a
good
place
for
you
to
start
you're.
Welcome
to
add
the
milestone
to
any
issue.
A
That
already
has
that
label
and
add
yourself
as
an
advocate.
You
can
just
edit
the
main
issue
and
put
your
name
in
there
or
if
you
have
something
new,
that's
not
on
that
list.
Yet
you
can
create
a
new
issue
and
add
that
label,
and
as
long
as
somebody
else
agrees
with
you
that
that
issue
is
a
high
enough
priority
to
make
it
into
court,
you
can
go
ahead
and
add
milestone.
B
Yep,
so
maybe
as
a
notable
mention
over
the
recent
couple
of
days-
issue
3-0
72,
which
is
about
allowing
the
the
edit
or
create
forms
to
sort
of
like
be
utilizing
the
regions
so
that
you
can
put
certain
things
on
the
sidebar
and
learn
and
make
it
up.
Not
sure
you
have
any
capacity
to
work
on
it
for
this
circle
for
114.
But
it
would
be
great.
B
C
A
With
a
specific
core
release,
focus
so
we'd
still
have
like
the
issue
that
Gregory
is
working
on.
Is
security
related
I,
think
security
issues
are
high
priority
in
general
and
waking
up
women
to
pretty
much
every
bug-fix
release
unless
it's
something
major
and
so
I,
don't
think
we
need
to
have
a
specific
release.
That's
focused
on
it.
A
We
were
more
concerned
about
having
a
whole
bunch
of
things
that
are
milestones
that
nobody
was
working
on
and
we
thought
it
was
more
important
to
go
with
the
advocate
approach
or,
and
let
the
before
be
more
determined
by
what
the
needs
of
our
community
are.
Then,
by
what
the
pmc
dictates,
but
with
every
minor
release
we
do
post
like
hey
pmc.
A
What
do
you
think
we
should
be
working
on
right
now
and
we
get
a
feedback
from
them
to
make
sure
that
our
what
the
community
wants
is
in
line
with
what
they
think
backdrop
should
be
doing,
and
we
link
to
the
current
milestones
and
say:
does
anyone
have
any
objections
to
the
stuff
that
we're
currently
working
on?
So
if
there's
something
that
we're
working
on
that,
we
shouldn't
be
working
on
we'll
be
stopped,
but
we
are
more
empowered
to
make
those
decisions
without
pmc
coming
in
and
doing
it.
For
us.
B
Sorry
to
answer
the
question
with
regards
to
security's
just
that
we
notice
that
there's
a
lot
of
a
bunch
of
security
related
things
that
are
touching
on
the
UI,
so
we
thought
that
maybe
they
deserve
paid
on
their
own
and
maybe
a
menu
on
their
own.
So
we're
trying
to
figure
that
out,
it
doesn't
have
to
be
I,
think
really
specific
yeah.
It's
just
that
because
these
things
are
so
like
make
seem
that
they
will
be
added
soon
ish.
We
need
a
place
for
them.
Yeah.
A
Yep
and
I
think
that's
something
that
you
know
once
we
have
it.
Ready
can
probably
go
in
a
bug-fix
release
if
the
user
interface,
because
you
know
that
sort
of
a
user
experience
thing
where
it's
like
hey,
we
want
to
make
it
easier
for
you
to
get
all
the
things
to
make
your
site
secure
in
the
same
place
and
I
think
that
should
correspond
with,
like
security,
blog
posts,
a
security
item
being
added
to
the
PMC's
principles,
like
all
the
security
stuff
kind
of
going
on
at
the
same
time
is
fine.
A
B
All
the
individual
three
update
modules
of
data
layouts
and
update
things
things
so
there's
correlated
sort
of
like
planned
features
would
seem
to
be
sort
of
like
we
seem
to
have
a
general
consensus
on
what
like
in
direction
of
what
we
need
to
do
is
just
things
falling
into
place.
Slowly,
it's
the
tiny
things
that
make
its
release
like
small
surprise,
our
guests,
yeah.
D
A
A
They
don't
have
an
update
weekly
if
it's
not
gonna,
be
in
the
next
release,
but
I
just
want
to
throw
that
out
there
if
you're,
one
of
those
people
that
want
to
I.
A
Lee
takes
up
so
much
of
my
day,
yeah
all
right,
well,
I
think
that's
it
for
today's
agenda.
Is
there
anything
we
wanted
to
talk
about?
I
wanted
to
talk
about
github,
stuff,
I,
don't
know
if
we
did
this
before
the
meeting
was
broadcasting
or
not,
but
issue
templates
would
be
really
great
for
our
op
contributors.
This
is
where
people
request
maintainer
applications
and
for
request
ports
of
modules,
I
think
if
we
can
help
them
form
their
requests
in
a
way
that
tells
them
that
they
need.
A
That's
gonna,
be
really
helpful
for
anyone
new
to
join
the
community.
There's
also
this
new
thing
that
github
just
put
out
that's
a
project
template
that
is
intended
for
a
boilerplate
code,
but
I
think
it
might
be
really
useful
for
backup
in
terms
of
training
people
on
how
to
create
a
modular
themer
layout
and
we
could
add,
like
example,
module
furniture
bowl
was
really
great
about
showing
how
like
lots
of
different
api's
could
be
implemented.
A
We
could
have
something
that's
a
much
simpler
version
of
that
that
just
has
all
of
the
files
where
it
could
have
like
a
hook
menu
that
references,
a
different
file
and
then
in
the
file
we
could
have
like
a
you
know,
example
of
a
form
or
something
like
that
where,
if
someone
was
building
a
module,
they
could
use
this
as
a
template.
All
of
the
code
is
in
there
maybe
commented
out,
so
it
wouldn't
do
anything
if
they
weren't
going
to
use
it.
A
B
A
B
A
B
Another
idea,
so
we
have
certain
issues
that
ask
the
status
questions
and
then
we
have
feature
requests.
I,
think
that
at
some
point
maybe
I'm
confusing
things
with
all
their
projects,
but
I
think
there
was
a
tag
for
idea
in
nothing
as
in
here's
an
idea.
It's
not
actually
a
feature
request
or
an
idea
of
how
things
could
work.
I'm,
not
sure.
A
A
B
Maybe
it
makes
sense
it's
just
that
over
the
last
month,
I
think
I
came
up
with
three
issues
that
were
not
actually
tasks.
They
will
not
actually
feature
requests.
There
were
not
questions.
Oh
yeah.
A
I
like
to
have
things
organized
yeah,
I
also
I,
also
wonder
if
maybe
we
should
direct.
So
if
anyone
does
try
and
create
like
a
question
that
issue
template
should
maybe
say
you
can
also
ask
questions
in
and
give
them
some
more
resources
to
like
live
chat
and
forum
and
whatever.
So
it's
like
sure
you
can
ask
here,
but
just
so
you
know
this,
isn't
your
only
Avenue
the
same
thing?
We
could
do
the
same
thing
for
ideas.