►
Description
Today’s development agenda: http://bit.ly/2gH11tZ
A
Alright,
we
are
on
air,
it
is
the
15th
of
December,
which
means
we
are
15
days
from
feature
freeze
for
backdrop
16,
which
is
pretty
exciting,
we're
just
going
to
run
through
some
of
the
things
that
we're
working
on
and
try
and
establish.
What's
going
on
in
backdrop
land.
Just
so
everybody
knows
back
java
has
a
community
browse
browser
stack
account
that
is
currently
disabled.
I
think
we're
probably
going
to
want
to
use
that
before
dr.
16
is
released
so
Nate.
A
If
you
get
a
minute,
if
you
could
email
them
and
have
them
turn
it
back
on
it
such
as
long
as
the
person
who
created
an
account
contacted
it,
they
turn
on
the
open-source
account
again
but
okay,
that
just
a
to-do
item
there.
That
should
be
back
shortly.
Everybody,
but
if
you
need
it
just
you
know
it's
not
there
today,
infrastructure,
wise
Oh.
Does
anyone
else
for
the
PMC
have
anything
to
announce
today?
Nothing
that
I
can
think
of.
B
A
Backdrop
CMS
org
we've
got
two
things
that
we're
actively
working
on
on
the
homepage.
Redesign
which
West
has
been
working
on
today
looks
fantastic,
I,
don't
know.
If
you
have
anything,
you
want
to
tell
anyone
about
that.
Wes
know
it's
coming
along
we're
shooting
for
release
of
the
new
homepage
redesign
about
the
same
time
as
backdrop
16
is
released,
we'll
see
how
realistic
that
is
once
we
get
into
January
other
things
we're
working
on
this
showcase.
I
would
like
to
spend
some
time
on
that
today,
but
we'll
see
how
some
of
these
other
issues
go.
A
There's
we
have
a
design
made
of
you
built
I've
been
lagging
on
that
a
little
bit
because
we
don't
have
content
for
it.
Yet
this
is
about
other
things
have
seemed
a
little
more
important
forum
is
also
next
on
our
list.
So
as
soon
as
we
get
the
homepage
redesign
out
mid-january,
we're
hoping
that
and
we'll
be
able
to
focus
on
giving
people
a
place
to
talk
about
backdrops
all
right,
a
backdrop
CMS
itself
Nate.
Do
you
want
to
take
over
bugfix
yeah.
C
Okay,
lemme
see:
okay
yeah
the
install
backdrop
in
other
languages
issued
23
29
is
still
pending
that
really
should
be
merged
at
just
about
any
time.
I,
don't
think,
there's
actually
more
work.
That
needs
to
be
done
there.
We
had
some
notices
about
needing
more
tests,
but
we
can't
add
more
tests
in
the
short
term
because
the
Installer
isn't
covered
by
simple
test.
Essentially,
so
that's
basically
moving
from
like
a
neat
review
to
actually
like.
We
just
need
to
get
that
committed.
C
That's
issue,
23
29,
that's
the
only
critical
bug
fix
that
we've
got
marked
on.
Oh
I'm.
Sorry,
it's
funny!
Sorry.
The
agenda
is
a
little
bit
ordered
in
a
funny
way.
Okay,
there's
also
the
full
bleed
hero
fix
for
basis,
which
is
also
our
TV,
see,
which
is
2190
so
I
think
both
of
those
issues
are
in
a
good
place
and
we
could
merge
both
of
them
get
out
the
next
minor
release,
basically
or
deciding
next
bug-fix
release
pretty
much
any
time
now,
so
that
might
be
happening
in
the
very
near
future.
C
If
it
doesn't
happen
in
the
next
week,
then
we
probably
wouldn't
find
it
very
worthwhile
to
to
make
another
bug-fix
release
until
1.6
itself
came
out.
So
I'd
probably
say:
I'll
try
to
get
that
in
and
release
made
this
week
and
then
we'll
have
one
final
release:
21,
not
five.
So
when
there's
nothing
else
that
comes
up
that's
critical
january
fifteenth
when
1.6
comes
out.
C
Okay,
the
1.6
version
that
is
slated
for
january
50,
as
noted
by
jen.
We
have
two
weeks
essentially
until
january.
First
rolls
around
and
january
first
is
feature
freeze
for
the
1.6
release,
and
we've
got
some
work
to
do
before.
Then.
The
items
that
we've
got
slated
for
1.6
that
are
still
in
progress
include
the
reference
module
adding
that
module
decor.
Let's
issued
1301
there.
C
It
looks
like
there's
it's
really
quiet
in
that
issue,
but
there's
all
of
the
work
is
going
on
in
another
location,
and
that's
that's
why
there
is
a
reference
module,
inking
trip
backdrop,
contribs
/
reference
and
looks
like
we
have
some
work
that
needs
review
from
Jeff.
That
needs
to
be
updated.
Mike,
since
you
guys
hopped
on.
Do
you
have
anything
you'd
like
to
add
regarding
the
status
of
reference
module?
Well,.
D
Current
deputy
yeah
posted
the
the
pull
request
for
getting
the
reference
field
test
case
test
runnings
was
running
now.
We
just
need
to
actually
add
tests
to
it,
so
they
don't
want
to
help
out
with
that
feel
free
to
jump
in
basically
I'm
thinking.
We
need
to
look
at
all
the
other
reference
module
implementations
and
make
sure
that
we
test
for
everything
that
they're
testing
for
another
issue
opened
up
by
her
duel
is
saying
that
we
need
to
do
access
checks
before
displaying
the
entities
which
I
had
somehow
missed
doing.
D
So
we
need
to
figure
out
that
and
I
need
to
actually
look
into
what
the
status
of
access,
whether
we
have
any
sort
of
excess
functionality
in
the
entity
api
and
whether
there
is
a
common
way
to
check
entity
access.
I
know,
that's
a
contribute
all
and
I
think,
do
you
guys
know
what
the
current
status
of
that
is
settled.
C
Yeah,
as
far
as
I
know,
some
systems,
like
notes,
actually
have
like
per
entity
access
control,
but
everything
else
there's.
No,
this
there's
definitely
no
global
system
well,
yeah
and
and
the
individual
entities
I
think
there's
no
more
for
other
than
notes.
Everything
else
just
is
protected
by
a
single
permission.
As
far
as
I
know,
yeah
access
user
profiles
is
universal
kind
of
thingy.
A
D
It
sounds
like
the
different
entity.
Types
have
like
custom
functions
for
this,
which
we're
going
to
have
to
well
I,
don't
know
I
would
yeah
I
need
to
dig
into
it.
I
don't
know
like
currently
the
like
for
the
for
display
rendered
entity
is
calling
the
user
is
calling
me.
It's
calling
the
entity
view
function.
So
the
question
is
whether
the
entity
view
functions
are
actually
doing
the
doing
the
access
check
at
that
point.
D
C
C
So
there
is
I
mean
as
far
as
showing
listings
for
autocomplete
purposes.
There
is
a
pattern
that
we
can
leverage
that
is
pretty
constant
entity
type,
underscore
access
as
a
query
tag,
and
that's
the
query
peg.
What
do
you
mean
to
the
query?
Type,
there's
a
method
literally
called
add
tag,
and
you
add
it
to
the
Select
query,
but
it
has
to
be.
He
became
gquery
and
by
adding
a
tag
that
allows
it
to
be
alterable,
so
it
allows
hook
query
altar
on
that.
If
it
has
tagged
essentially
and
that's
the.
C
C
C
Yeah,
ok,
so
someone's
still
coming
along
I'm
on
the
hook,
I
know
for
helping
with
those
automated
tests,
so
I
would
say:
let's
try
to
get
it
Jeff's
suggestion
to
just
but
stuff
it
all
out
and
then
work
from
there
on
top
of
it,
adding
tests
that
that
match
the
current
coverage
also
relating
to
entity.
Reference
are
too
tough,
so
I
reference
module,
Jen
you've
been
heavily
involved
in
another
issue.
The
view
modes.
One.
Is
that
detracting
from
your
ability
to
attempt
the
great
path
for
reference
module.
It.
A
Depends
how
much
more
work
is
needed
on
the
View
mode
stuff
I
noticed
there
was
a
bunch
of
good
feedback
over
there,
but
it'll
be
great
if
we
could
get
more
eyes
on
that,
because,
on
the
way
the
view
modes,
administration
interface
worked
in
Drupal
7
was
a
little
weird
and
so
we've
added
it.
A
Instead
of
kind
of
floating
off
in
its
own
place
under
structure
we've
added
it
into
field,
you
I,
where
you
actually
manage
even
loads
for
various
different
fields
of
different
entities,
and
it
I
think
it
makes
a
lot
more
sense
there.
That
was
a
recommendation.
Three
different
people
kind
of
came
up
to
at
the
same
time,
we're
like.
Why?
Don't
we
just
let
this
in
the
place
where
we
already
deal
with
veal
modes,
but
it
does
present
some
user
interface
weirdness,
as
is
typical
field
UI,
and
we've
got
a
couple
of
different
solutions.
A
A
couple
different
flow
requests
about
ways
to
solve
that
that
we
could
use
some
feedback
on
like
how
to
throwing
in
like
is
this.
Turning
into
a
field,
you
I
redesign,
or
is
it
the
kind
of
thing
that
we
can
actually
get
in
as
a
part
of
a
future
edition?
So
it
would
be
good
to
just
get
more
people,
even
if
you
just
looked
at
this
freaking
shots
and
that
issue
just
to
weigh
in
and
say
like
whoa.
This
is
too
crazy
or
like.
Yes,
this
is
a
lot
better
user
experience.
A
That
would
be
great
because
I
think
I
think,
both
of
those
poor
requests,
regardless
of
which,
when
we
go
with
they're,
pretty
close,
it's
just
a
matter
of
you
know
who's
going
to
take
them
from
where
they
are
to
being
done.
So
it
doesn't
necessarily
need
me
to
work
on
it.
We
just
need
to
decide
which
way
to
go,
and
then
someone
to
kind
of
do
the
last
cleanup.
C
C
C
Okay!
The
next
item
is
2375,
which
is
adding
a
media
/
file
entity,
a
solution
which
is
a
little
bit
broad.
It
just
changed
the
title
earth.
It's
actually
now
we're
really
just
talking
about
adding
a
view
that
has
bulk
operations
for
managing
finals.
At
this
point
and
for
really
beginning
at
at
square
one.
That
really
means
just
deleting
files
Jen.
A
A
That's
there
is
to
delete
it's
the
only
thing
you
can
do
/
file
individually
as
opposed
to
in
bulk,
but
it
would
be
really
easy
to
add
all
of
those
things
in
later,
because
we
already
have
the
URL
structure
in
place
like
that
route
like
file
/,
whatever
you
just
can't
actually
view
files.
There
now
I
also
only
add
one
additional
permission
or
two
there's
one
to
delete
files
and
one
to
view
the
page
where
all
the
files
are
managed,
but
every
one
of
those
actions
will
need
its
own
permission
to
so.
C
A
Were
a
bunch
of
other
things
that
we're
missing
from
the
pull
request
last
week
too
I
don't
know
how
that
didn't
get
pushed
up,
but
it's
ready
now
there's
a
view
in
there
and
they're
all
the
permissions
are
fading
or
all
set.
So,
okay.
C
Those
items,
I
think
are
those
those
three
are
the
ones
that
I
think
really
should
receive
our
focus
for
release,
but
there's
more
items
in
here
that
we
are
still
hoping
to
complete,
but
the
kind
of
and
a
limbo
state.
Yet
the
first
of
these
two
are
solutions
for
managing
large
number
of
blocks
if
you've
got
similar
block
configurations
across
multiple
layouts
managing
those
blocks
across
all
the
layouts.
At
the
same
time,
we
need
to
come
up
with
solutions
to
that
problem,
and
so
there's
two
pull
requests
that
provide
options
to
solve
that
problem.
C
Both
of
these
power
requests
are
like
that
they
work
from
a
technical
standpoint,
but
both
of
them
introduce
enter
layout
dependencies
where
one
way
out
now
will
be
dependent
upon
another
layout,
because
it
has
a
copy
of
like
the
master
block
or
a
master
region
from
that
other
layout,
and
so
technically
that
this
works.
But
it
makes
it
really
nervous
from
a
site
management
standpoint
about
the
kinds
of
problems
you
could
get
into
it,
a
bunch
of
layouts
having
interdependencies
between
each
other
or
even
trying
to
keep
track
of.
A
I
have
an
idea
what,
if,
in
the
first,
the
first
one
we
add
two
core,
if
that's
just
copy
block
for
16,
we
limited
the
layout
source
to
the
default
layout,
which
is
when
they
can't
ever
be
deleted.
A
And
I
feel,
like
we
at
least
have
the
tool
there
for
contribs,
a
like
hey
I,
want
to
copy
from
my
other
layouts,
where
it's
not
necessarily
our
responsibility,
but
we
are
giving
people
this
feature
that
they've
wanted.
That
allows
you
to
copy
from
something
and
if
you
use
the
default,
you
know
it'll
always
be
there.
Yeah.
D
See
how
this
really
helps
like
and
just
like
goose
it
yeah
I
mean
it
doesn't
just
seems
like
you're
restricting
people
and
they're
going
to
be
confused.
Why
they
can't
just
choose
layout
and
block
like
it's
a
lot
like
a
user
layout
and
I
want
to
do
a
special
user
page
or
something
like
that.
I'm
like
I'm,
going
to
copy
this
block
from
the
user
layout
and
it's
like
yeah,
I
mean
just
saying:
oh
jus.
The
default
really
cuts
down
on
the
actual
usefulness
of
the
function
right
it
does
and
we
go
to
hell.
D
C
C
C
D
A
It
depends
if
you
think
right
anything
in
can
trip
to
leverage
it
and
I.
Think
like
where
we
are
now.
The
number
of
people
are
coming
up
with
crazy
new
ideas
to
do
stuff
and
contribute
very
limited,
but
what
we
will
be
adding
if
we
added
this
as
like
a
starting
point
for
contribs
solve
the
real
problem.
But
if
we
aren't
going
to
have
contribs
off
the
real
problem
in
the
next
four
months,
then
there's
no
point
in
putting
this
in
court
in
the
next
four
months.
Yeah.
C
E
C
B
C
C
Or
minute,
there's
no
conflict
right.
It
would
be
a
lot
like
the
custom
blocks,
listing
that
there's
a
list
of
custom
blocks
that
you
edit
the
custom
block
and
that
affects
all
of
the
places
where
the
custom
block
is
used.
It
would
be
very
similar
that
if
you
could
just
configure
an
arbitrary
menu
block,
for
example,
without
any
layouts
and
then
place
that
single
menu
block,
the
customized
version
in
all
of
the
layouts
exactly
yeah
and
then
then
you're
right
there
wouldn't
be
any
dirt
dependencies
between
layouts.
C
B
Well,
just
on
the
thing
that
you
said
night,
I,
I
personally
wouldn't
mind,
it
could
took
us
longer
to
fix
to
get
it
right.
We
actually
get
right
side
if
we
get
the
other
three
pitches
in
for
one
got
six,
and
we
need
more
time
to
make
it
work
the
way
that
it
will
cause
trouble
in
the
future
then
so
needed.
Let's
have
it
of
what
70
something:
okay,.
C
C
This
issue
was
added
really
late,
actually
into
our
overall,
really
psychos
being
an
item
that
would
like
to
address-
and
it's
still
in
the
almost
brainstorming
phase,
which
makes
me
think
that
if
no
further
activity
happens
like
in
the
next
week
on
it
that
it
should
be
tabled
because,
right
now,
we
don't
even
have
any
any
code
backing
up.
I
think
we've
got
some
pretty
solid
ideas,
but
yeah
there's
there's
no
code
behind
it.
C
At
this
point
and
with
the
the
need
to
not
only
come
up
with
a
solution,
but
then
also
test
it
comprehensively
that
this
is
looking
like
a
really
skeptical
item
to
actually
complete,
which
is
issued
2156.
If
anyone
is
interested
in
doing
a
little
bitter
too
many
clean
up,
that
one
is
free
and
available
for
the
taking
in
the
last
one
that
we
have
here.
Is
this
ongoing
issue
about
improving
the
rich
Texas
Evan?
It's
a
meta
issue.
C
But
then
we
had
that
kind
of
introduced,
a
regression
that
the
right
click
now
we
need
to
figure
what
to
deal
with
how
to
deal
with
the
right
click
to
actually
make
it.
So
the
spelling
suggestions
work
so
there's
a
follow-up
issue
that
it
needs
additional
work.
Essentially,
there's
a
bunch
of
other
self
issues
in
issue,
1087
that
they're
free
available
for
the
taking.
I
don't
think
any
of
them
have
any
progress
made.
C
C
It
depends
actually
because
anybody
can
put
additional
things
in
there
if
you
I,
think
that
we
have
things
like
the
table
plugin,
for
example,
if
you
drag
in
the
table
button,
then
you
can
add
tables
and
then
right.
Click
is
used
for
things
like
add
column
and
add
row.
So
it's
a
little
bit
deeper
than
just
copy
paste.
All.
D
C
Okay,
that's
it
for
the
1.6
release.
There
are
other
items
tagged
for
1.6.
You
get
the
full
list
from
the
github
issue
tracker
and,
as
we
make
progress
will
be
merging
anything
with
that
tag
it
if
there's
something
that
needs
review
or
that
is
ready.
Please
use
both
the
combination
of
a
milestone
to
tag.
C
It
is
1.6,
as
well
as
the
label
to
tag
it
as
needs,
review
or
repeat
issue,
and
that
will
help
us
go
through
the
poll
request,
sir,
that
I
the
issues
that
have
pull
requests
and
get
through
those
reviews,
that's
it
for
the
1.6
update.
We've
got
two
weeks,
yet
let's
go
get
them
mixed
up
and
the
agenda
we've
got
the
community
growth
section
which
tom
is
going
to
be
taking
g'day
aachen
tom
thanks.
E
Nate,
looking
at
community
growth,
there
have
been
a
total
of
seven
thousand
738
backdrop,
CMS
downloads
from
backdrop,
CMS
dot,
org,
slash,
download
that
is
up
87
downloads.
Since
the
last
meeting
there's
been
a
total
of
three
hundred
and
forty
two
projects
for
backdrop,
CMS
on
github,
no
change
since
the
last
meeting,
394
totally
user
accounts
on
backdrop,
CMS
title
organ
increase
of
7
users
since
the
last
meeting
and
59
total
backdrop,
contributors,
no
new
authors
since
our
last
week.
That's
all.
C
Excellent
well
said:
okay
upcoming
events,
we've
got
a
calendar
on
a
backdrop:
CMS
org,
slash
events:
you
can
check
their
for
upcoming
events,
so
feature
bankruptcy,
ms
camps
and
conferences
at
bluish
backdrop,
speakers
have
been
requested
or
batter
up
to
me.
Members
have
been
encouraged
to
attend,
I,
don't
think,
there's
any
notable
items
at
this
points,
an
immediate
future,
that's
it
kind
of
for
the
overall
meeting.