►
From YouTube: Backdrop Weekly - Dec 27th
Description
Today’s development agenda: http://bit.ly/2rQspgd
A
A
This
meeting
is
to
check
in
on
the
remaining
issues
that
are
likely
to
get
in
backdrop
1:12,
which
comes
out
on
January
15th,
which
means
future
phases
January
1st,
which
is
one
two
three
four
five
days
from
now
so
I
hope
everybody
has
everything
they
want
to
get
in
ready
the
kitchen
we've
got
five
days
to
crank
them
out
and
get
them
before
we
get
to
those,
though,
let's
talk
about
a
couple
of
other
things,
we
have
even
though
there's
a
handful
of
us
working
like
crazy
encore.
A
There
are
a
bunch
of
people
creating
you
can
trim
projects
too,
which
is
great.
In
the
past
week,
we
had
both
a
new
release
for
the
Meo
link
formatter
and
for
corporate
kicks,
which
is
actually
a
new
theme,
so
it
makes
me
really
excited
to
see-
and
this
is
an
example
of
a
CSS,
only
game
which
is
really
gonna,
be
really
good,
that
we
have
people
who
are
able
to
do
that
and
contribute
it,
but
also
now
that
we
have
an
example
for
other
people
to
follow
them.
A
A
There
are
no
updates
since
last
week
on
that
issue,
I
would
like
to
work
on
if
I
keep
getting
distracted
by
more
fun
stuff
like
what's
going
into
112,
so
we
might
who
might
change
gears
and
sort
of
push
that
to
after
code
freeze
at
least
I
will
and
also
the
forum
site
has
been
having
some
issues
lately.
With
running
out
of
memory,
we
found
some
custom
code
that
was
causing
that
problem
and
reverted
it,
but
now
we're
having
some
other
problems.
A
So
Tim
I,
don't
know
if
you
think
the
problems
are
having
now
are
bad
enough,
that
we
need
to
disable
things
again
until
we
get
it
figured
out
or
if
you
think
it's
I
mean
I,
didn't
I
haven't
tested
it.
But
I
saw
your
comment
there,
where
it
behaves
differently
in
different
circumstances,
which
is
at
least
an
estranged
experience
for
people
right.
B
And
I
don't
remember
exact.
There
was
a
while,
since
I
reported
that
so
I
don't
remember
exactly
if
it's
as
bad
as
it
was
so
I
wouldn't
make
a
recommendation
now,
but
certainly
it
was
pretty
bad
people
were
losing
their,
you
know,
typing
long
posts
and
then
losing
them
and
I
think
that's
still
possible.
So
we
might
want
to
okay.
A
It
looks
like
when
you
create
a
new
comment:
everything's
fine,
when
you
edit
an
existing
comment
and
you
hit
preview,
you
get
that
maximum
execution
time.
It
was
less
bad
and
if
you're
creating
a
new
topic-
and
you
hit
preview,
you
get
a
page
not
found,
which
is
a
little
weird
I.
Don't
know
why
that
should
happen.
I
think
we
should
fix
that
and
fix
that
either
be
like
disable
preview.
A
So
nobody
gets
that
and
looses
their
content
or
find
out
why
it's
page
not
founding
in
the
first
place,
which
is
a
little
strange
and
get
that
up
again
and
then
the
maximum
execution
time
thing
I
think
we
do
need
to
actually
look
into.
What's
going
on
an
execution
to
find
out
why
it's
eating
above
that
time
that
yeah
I
don't
know
if
you
think
that's
worth
disabling
the
preview
of
comments
for
now.
A
A
C
Alright,
there's
a
whole
lot
going
on
it's
fantastic,
so,
let's
quickly
go
over
111
4,
which
is
the
next
bug
fix
release
that
we'll
be
creating.
You
know
that
just
just
fixes
issues
in
the
current
release.
We
had
one
large
issue:
the
was
related
to
ckeditor
when
you
link
an
image,
it
causes
a
fatal
air
and
that's
issued
3384.
C
That
issue
has
been
merged
early
today,
so
that
is
good
to
get
that
one
knocked
off,
and
then
we
have
a
whole
bunch
of
cross
ports
from
Drupal
7.16
7061,
which
is
issued
3375
I've
been
working
through
this
one.
There
were
a
whole
lot
of
pull
requests
made
mostly
Gregory,
who
made
them
and
then
Erb
dual
that
went
through
and
reviewed
them.
C
Thank
you
guys
both
and
I've
been
working
through
all
of
those
our
TBC
issues,
I'm
about
two-thirds
of
the
way
through
merging
each
one
of
those
and
then
there's
one
or
two
issues
that
still
need
to
be
kind
of
reviewed
to
see
mostly
if
we
need
to
do
anything
at
all
over
in
the
in
the
back
top
side
of
things.
So
that's
looking
really
great.
C
C
There
are
a
lot
of
issues
that
were
marked
our
TBC
for
the
last
week,
at
least,
and
a
lot
of
those
has
been
merged
options.
Elements
in
core
issue:
1005
has
been
merged,
rendered
taxonomy
term
formatter
issue.
3283
has
been
merged,
adding
a
language
to
taxonomy
terms
so
that
the
terms
have
languages
that
match
content
that
they
are
created
on
issued.
C
C
We
have
lots
of
issues
that
are
on
the
cusp
as
well:
adding
a
link
or
site
adding
a
class
to
a
link
in
the
seek
editor
dialog
for
adding
an
anchor
tag
is
issued
3307
that
one
is
our
TBC
I
could
I
think
that's
the
only
our
TBC
one
that
we've
got
here
in
the
in
the
agenda,
but
let's
see
other
issues,
the
dashboard
for
which
is
495.
I
haven't
had
a
chance
to
look
at
this
one
this
week,
but
I
think
Jen
said
that
there's
lots
of
progress
with
three
exclamation
points.
A
But
what
doc
Loma
had
already
done
is
essentially
taken
a
part
of
the
total
control
module
from
triple7
and
made
it
work
for
backdrop
just
to
be
like
hey
here's,
the
dashboard.
What
do
we
think,
and
so
what
I
did
is,
do
a
super
detailed
review
of
that
pull,
request
modifying
it
so,
rather
than
being
specific
to
table
7.
A
More
specific
to
backdrop
that
uses
our
cleaner
terminology
had
recommendations
for
settings
form
stuff
like
that.
So
while
Dhokla
and
I
are
kind
of
going
back
and
forth
over
the
pull
request,
which
is
great,
there's
also
a
conversation
going
on
in
the
main
issue
about
other
features.
We
might
like
to
add
or
like
how
the
blocks
can
be
configured
or
all
this
other
stuff,
so
I'm
really
looking
for
it.
A
Oh
and
then
last
night,
while
we
were
sleeping
talk
moment,
went
to
an
implement
a
whole
bunch
of
those
suggestions,
so
I'm,
looking
forward
to
seeing
whether
I
haven't
tested
it
again.
Yet
so
I'm
looking
forward
to
seeing
whether
the
changes
were
just
like
technical,
like
stream
changes
and
stuff
I'd
recommended
on
the
for
Buster,
he's,
also
taking
to
account
some
of
the
things
from
the
main
issue.
But
it
was
I'm
really
excited
to
see
that
one
moving
forward.
It
looks
like
the
amount
of
change
is
required
to
get
it
into
core.
A
It's
pretty
minimal
and
we're
just
trying
to
decide
on
what
a
really
solid
initial
feature
set
will
be.
So
we
want
to
make
sure
that
we're
not
putting
in
a
dashboard.
That's
like
triple
sevens
dashboard.
That
did
nothing.
We
want
to
make
sure
it's
a
useful
dashboard
and
we
want
to
make
sure
there's
enough
stuff
on
there.
That
makes
it
worthwhile
to
put
into
112,
but
we
also
don't
want
do
all
of
the
bells
and
whistles
at
once.
We
want
to
kind
of
get
a
good
starting
point
and
then
iterate.
A
E
A
Let's
add,
let's
start
out
really
quick
as
I
think
Nate,
you
might
have
an
opinion
on
that
too.
So
we
could
add
a
visibility
condition
to
the
layout,
that's
in
core
so
like.
If
we
just
add
a
layout
there's
a
way,
you
can
add
a
visibility.
Traditional
pinch
there,
where
you
could
say
this
layout
is
only
visible
to
a
wall
or
a
promotion
or
something,
but
the
way
that
total
control
did
it
and
I
don't
know.
This
is
my
preference
obviously,
because
I
did
this
way
before
is
that
it
added
a
new
permission.
A
That
was
something
like
access
dashboard
and
then
I
was
able
to
leverage
that
permission
to
set
up
a
redirect
so
that,
when
you
logged
into
the
site,
if
you
have
to
purchase
access,
the
dashboard
I
look
redirecting
there.
So
we
also
have
this
issue
with
like
who
do
we
redirect
there
that
you
can't
write
redirector
everyone,
because
I
approve
a
sexist
seat?
The
dashboard
or
shouldn't
have
access
to
see
the
dashboard,
but
maybe
we
could
do
that
in
other
ways
were
like.
A
A
Says
anyone
with
this
permission
and
the
link
is
to
the
permissions
page
and
that's
the
only
setting
is
for
a
redirect
or
not
redirect,
and
so
it's
also
a
little
arbitrary
like.
Where
do
you
then
put
that
setting
right
because
we
don't
have
a
module?
This
is
just
a
layout,
so
my
recommended
system
core
but
yeah.
It
is
a
little
weird
to
have
like
add
a
new
permission
and
then
have
one
setting
that,
like
leverages
that
permission,
what
we
do
have
the
ability
to
have
an
access
check
in
the
dashboard
I
thought.
E
Maybe
the
way
that
the
reason
why
I
expressed
that
opinion
was
because
maybe
I
didn't
get
a
good
idea
of
how
the
technical
solution
would
work
out
and
I
didn't
know
if
this
is
gonna,
be
only
a
layout
based
solution
or
if
it's
gonna
be
actually
a
module.
If
it
is
a
module,
maybe
because
I
actually
looked
for
a
hook,
permissions
thing
in
the
code
and
didn't
find
any.
A
E
Then
my
concern
was
that
we
call
that
the
dashboard-
and
we
have
a
specific
URL
for
it-
is
that
the
intention
to
have
admins
last
dashboard
for
every
desperate
that
people
want
to
create,
because
then
it
means
that
people
can
only
need
to
have
the
access
at
admin
pages
permission
to
be
able
to
access
the
last
modes.
Yes,.
A
A
I
think
that
we
should
only
assume
that
people
have
one
dashboard
I,
think
if
it's
gonna
be
a
layout
and
we
provide
it
for
them.
We
could
even
get
the
path
based
on
that
layout.
So
if
they
learn
to
edit
the
layout
and
edit
the
path
we
could
whatever
setting,
this
is
redirect
them
to
the
dashboard.
It
would
say:
what's
the
what's
the
dashboards
pack?
Yes,
no
redirect
to
that.
A
C
E
And
I'm
not
sure
how
people
are
going
to
use
it
like
most
people
might
only
requires
a
single
password
for
a
single
role
in
this
side,
but
all
the
people
I
think
team.
It
wasn't
you
that
you
mentioned
in
the
no.
It
wasn't
so
someone
else
mentioned
that
they
they
have
multiple
boots
for
multiple
people.
But
since
this
is
a
layout,
people
can
add
block
with
certain
visibility,
so
they
redirect
to
the
same
layout.
E
B
Comments
were
misunderstood:
it
I
had
multiple
different
pages
sort
of
four
different
content
types,
but
I
don't
view
them
as
different
dashboards.
It's
like
really
what
I'd
like
is
on
the
dashboard
is
a
quick
link
to
these
various
management
pages,
so
it
would
be
the
same
role
using
it
and,
and
it
could
all
you
know
a
good
dashboard.
Would
readers
remove
my
need
for
having
those
five
different
sort
of
links
under
the
admin
menu
because
also
built.
A
Sites
with
multiple
dashboards
for
different
roles
like
depending
on
what
people
are
doing
on
this
site
that
thinks
they
might
need
to
have
access
to.
It
could
be
really
different
and
I've
done
that
in
a
couple
of
places,
and
that
one
way
where
it's
like
the
dashboard
itself
changes
then,
and
what
you're
looking
at
what
you
do
with
like
different
blocks
with
disability
conditions.
I've
also
done
it
where
all
of
those
blocks
live
like
on
the
user.
A
Page
right
reads:
when
the
user
page
into
a
dashboard,
and
then
you
have
differing
a
user
page
over
and
you
we
could
already
do
that
with
the
dashboard
block,
so
we're
putting
in
Cori
and
the
other
one.
So
I
think
it'll
kind
of
all
of
the
solutions
that
I've
done
in
the
past
were
sort
of
based
on
the
tools
that
I
had
to
do
it
with.
C
A
I
think
that
what
we
might
see
in
backdrop
like
all
these
these
cases
were
like
well
they're,
all
sort
of
possible.
We
just
don't
know
what
people
are
gonna
want
to
do
most
like
whether
they're
gonna
want
to
have
one
dashboard
with
the
different
blocks
or
the
multiple
dashboards.
Or
what
have
you
and
I?
Think
that
you
know
initially,
we
shouldn't
we
don't
know,
and
so
I
think
it's
just
safe
to
be
like
we
know,
people
are
gonna,
want
a
dashboard,
let's
start
there
and
then,
if
it's
okay
to
hard
cut
all
that
stuff.
A
That
makes
that
job
a
little
easier
because
we
can
set
it
to.
You
know
admin
page
that
Leah
all
that
stuff
admin
theme
and
then
in
the
future.
We
can
say:
okay
well
now,
if
you're
gonna
want
a
different
dashboard
or
work
it
differently
in
Cavan,
future
requests,
that's
okay,
I
want
to
change
the
path
or
what
happily,
to
figure
out
that.
E
Yeah
I'm
a
fan
of
getting
something
better
than
what
we
currently
have
real
quick.
We'll
look
I
mentioned
that
in
the
in
the
issue
as
well.
My
only
concern
is
that
we
don't
buy
the
way
that
we
technically
implement
this.
We
don't
block
any
of
the
possible
features
that
work
yeah.
So
by
mentioning
certain
things.
E
I
don't
want
to
derail
the
discussion
or
risk
not
getting
in
the
feature
which
is
awesome
for
1.12
I
mean
just
you
know,
saying
that
the
way
that
we
implemented
does
not
block
us
from,
for
example,
one
of
my
concerns
was
existing
sites.
We
are
planning
to
redirect
people
to
that
despot
by
the
existing
sites.
That
already
didn't
like
the
fact
that
that
they,
the
people
when
they
logged
in
they
got
yes,
the
user
page.
They
might
have
already
done
something
about
it.
E
So
if
we
redirect
him
out
of
that,
it
might
not
be
desirable,
then,
yet
so
just
something
to
think
about
and
that's
why
that's
why,
when
I
thought
about
it,
enough
and
I
did
some
research
to
see
how
how
things
are
solved.
These
problems
are
solved
in
Drupal
and
I
tried
to
see
what
other
country
modules
are
doing,
and
some
of
them
were
simply
offering
a
solution
to
redirect
specific
roads
difficult
liked
it.
So
I
was
thinking
that
for
fresh
installations
we
can
just
decide
and
say
yep.
E
A
A
E
My
idea
was
this:
that
independent,
so
we
are
tackling.
We
are
trying
to
tackle
this
problem
as
well.
You
know
offering
people
something
more
useful
than
the
user
paid,
but
it
doesn't
have
to
be
in
that
specific
issue.
So
we
can
add
the
dashboard,
but
not
very
direct
right
now.
I'm
just
saying
as
an
idea
and
then
have
a
thought
about
between
can
add
the
redirection
later
on.
I,
don't.
C
E
F
E
C
C
A
C
That
owns
the
layout
and
then
it
wouldn't
be
turned
on
on
existing
sites,
but
you
could
just
turn
on
the
module.
It
would
turn
on
the
dashboard
layout.
It
owns
the
permission
and
and
and
it
does
all
the
redirecting
stuff.
So
if
somebody
wanted
some
other
kind
of
dashboards,
he
just
wouldn't
use
the
one
in
core.
You
know,
but.
A
C
E
A
C
E
Yeah
one
of
my
objections:
it's
not
a
hat
objection.
It's
just
a
matter
of
discussion
was
that
we
we
shouldn't,
be
adding
more
permissions
to
the
already
bloated
permissions
page
like
if
we
can
avoid
it.
But
Jenn
had
a
fair
point
there
that
we
can.
We
can
use
the
visibility
conditions
of
the
layouts
because
they
they
allow
visibility
per
roll.
E
C
Oh
no
I
I
definitely
think
we
should
have
a
permission
for
access
to
dashboard
because
that's
where
I
would
expect
to
find
it
and
then
configured
allowed
to
use
that
permission.
Okay,
I'm,
getting
a
little
hung
up
on
this
being
part
of
system
module,
but
I'll
think
about
that
some
more
and
determine.
If
there's
that's
a
reasonable
complaint.
A
A
A
C
Yeah,
in
order
for
something
to
have
a
revert
capability
like
its
to
specify
it
as
default
and
then
be
it
be
revert
about.
It
has
to
be
owned
by
a
module.
So
like
there's,
no
revert
option
for
the
homepage
layout
because
that's
not
owned
by
a
module.
It's
just
created
for
you
out
of
the
box.
But
in
order
to
have
a
revert
like
we
do
for
views
which
you
can
also
revert
on
layouts.
It
has
to
be
able
to
pull
that
the
default
config
from
somewhere,
which
well.
A
F
A
But
anyway,
that
might
that
might
fade
into
our
decision
here
about
where
to
put
the
dashboards
like.
If
we
are,
you
know
we
have
this
perhaps
issue
with
the
home
page,
where
maybe
we
wanted
to
be
part
of
module
instead
of
part
of
the
profile,
then
that
might
change
our
thinking
about
where
we
want
to
put
the
dashboard
config
file,
whether
it
should
be
part
of
a
module
instead
of
profile,
but.
A
Was
the
it
it's
just
a
layout,
let's
just
throw
it
in
the
standard
profile.
Just
like
the
homepage,
I
didn't
realize
they
were
issues
page.
They
know
you
to
be
concerned
about
and
then
all
of
the
blocks
should
just
go
into
whatever
modules
they
come
from.
So
if
you
have
a
module
that
lists
like
recent
content
in
Chevelle
in
the
node
module-
and
you
have
one
that
lists
recent
user,
so
she
built
a
new
user
module
just
like
the
admin
or
the
dashboard
blocks
for
Drupal
7
came
from
those
respective
modules
and
I.
A
C
C
A
People
who
are
already
running
back
to
wouldn't
necessarily
get
the
advantages
of
using
it
yeah,
but
that
could
also
be
a
bonus
right,
like
it's
very
point
out.
If
someone
already
set
that
off
and
they
didn't
want
to
so
that's
either
either
way,
and
the
other
thing
is
like
we
don't
with
what
what
is
the
point
of
having
a
separate
module
other
than
this
one
checkbox
in
the
permission?
A
C
The
redirect
sounds
like
we've
gotten
some
problems
with
how
the
redirect
works.
You
know,
because
it's
based
on
the
permission
you
know
like
only
redirect,
if
they
have
this
permission,
that's
weird
the
layout
needs
to
live
somewhere
and
we
need
to
add
a
permission.
I
don't
know
all
those
things
could
all
live
together
in
the
module
and
if
we
wanted
to
enable
give
that
to
new
sites
as
they
upgraded,
we
could
just
add
an
update
hook.
That
turns
on
the
dashboard
module
during
the
upgrade
yeah.
E
A
E
B
A
D
D
Our
CMS
is
like
definitely
not
something
we
want
to
be
constantly
fighting
against,
because
we
hide
the
fact
of
what
platforms
our
users
are
using
from
them,
but
I,
don't
think
anything
you
guys
are
discussing
rules
out
doing
what
what
we've
already
done
and
the
type
of
things
that
people
with
enough
resources
would
actually
want
to
customize
and
build
out
so
starting
with
a
Depot
that
is
like
the
civvie
CRM
dashboard.
I,
think
you
know
it
has.
D
A
E
A
They
are,
l
is
what
determines
the
path,
the
admin
status.
So
as
long
as
it's
admin
dashboard,
something
it'll,
be
an
admin
page
and
it
doesn't
hear
it
you're
right
all
of
the
things
that
the
same
path
will
still
work.
But
if
you
wanted
to
create
a
new
one,
it
like
slash
dashboard,
also
not
be
friend
yeah,.
E
Using
yeah,
it's
the
federal
using
paths,
people
can
call
them
the
same
layout,
leave
the
same
path
as
I've
been
dashboard
and
then
play
with
permissions
and
so
on,
and
then
the
the
permissions
do
a
take
over
and
we
direct
the
people
to
the
proper,
whatever
they
meant
to
see,
which
is
I.
Think
right.
It's
like
yeah.
A
So
it
sounds
like
we
still
have
this
issue
with.
The
only
thing
we
need
to
have
in
a
module
is
the
hook
of
my
new
entry
to
make
it
admin
patzert
hook,
em
in
half
century
or
whatever
I
settings
form
with
a
single
check
box
on
it.
In
a
permission,
yeah.
A
A
E
Can
have
any
one
for
new
installations,
we
think
have
it
turned
off
by
default
and
remember
that
we
have
information
system,
as
I
said
we
can
throw
in
for
messages
saying
we
actually
have
a
ticket
for
that.
This
is
what
WordPress
does
and
it
does
it
well.
It
says:
look
welcome
to
the
new
version
of
what
quiz
you
have
updated.
These
are
the
new
features
you
can
enable
those.
So
we
can
take
advantage
of
that
all.
C
E
We
I
actually
was
taking
screenshots
the
like
a
set
up
tests,
installation
of
four
decks
and
upgraded
word
person,
updated
it
to
500
text,
and
they
like
this.
It's
really
awesome.
It
gives
them
the
the
option
to
keep
using
the
old
non
good
in
the
version
with
sub
message,
and
then
it
shows
them
how
the
new
version
of
things
work,
and
they
also
have
tabs
of
credits
which
is
really
great.
It
lists
all
contributors
that
added
code
to
that
version.
It's
pretty
good
ideas
and
we
already
have
a
ticket
for
that.
C
C
E
C
C
F
A
A
A
C
C
He
already
added
new
api's
to
make
it
so
that
translatable
x'
could
be
pulled
out
of
config
files
and
also
stored
in
config
files,
identifying
which
keys
are
translatable,
but
he
recently
updated
the
pull
request
so
that
now,
when
new
config
files
are
imported,
they
are
now
automatically
scanned
for
translatable
and
then
are
run
through
the
locale
function,
which
then
inserts
them
into
the
list
of
strings
that
need
to
be
translated
on
the
site.
So
that's
very
exciting.
I
haven't
had
a
chance
to
do
the
code
review.
C
E
C
E
C
C
Yeah,
so
that
one
needs
some
more
review,
definitely
like
anybody
that
it
has
time
to
take
a
look
at
that
and
see
you
know
what
it
what's
doing.
That
would
be
handy.
It
I'm,
not
sure
the
summary
is
very
accurate
right
now,
like
you
say
Gregory
that
could
be
helpful
to
get
more
eyeballs
on
that,
because
right
now,
I
think
you
kind
of
to
read
the
code
to
figure
out
what
the
heck
it's
actually
even
doing.
C
E
C
C
I
think
several
weeks
ago,
Jen
you
added
the
necessary
fields
to
backdrop:
CMS
dot,
org
itself
like
so
the
data
model
is
there
and
then
with
doc.
One
month
spore
requested
now
starts
populating
that
information
when
new
releases
of
modules
are
made,
and
so
we
can
continue
kind
of
experimenting
with
that,
because
you
know
until
we
document
it
and
start
updating
modules
and
themes
and
layouts
actually
updating
the
code
to
populate
that
information.
It's
not
so
I'm
actually
going
to
do
anything
where.
C
A
A
C
E
E
A
A
C
Okay,
well,
we
should
add
a
comments
about
to
issue
487.
In
the
backdrop,
CMS
not
work.you,
about
removing
the
screenshots
from
the
from
the
directory
in
the
packager,
because
the
easy
he's
he's
working
on
the
package
here,
basically
right
now,
I,
but
and-
and
so
this
is
an
additional
part
of
that
I
think
it
might
be
a
different
place
in
the
code.
So
maybe
that
would
actually
be
a
follow
up,
because
we
could
always
make
the
archive
smaller.
You
know
later
that.
E
Think
it
is
hard
to
help
this,
though
cuz.
How
can
we
test
it?
What
right
yeah
there's
only
a
few
people
that
would
do
working
on
it,
I'm
just
mentioning
that
anyways
before
we
move
on
from
37
before
37
was
pretty
different
issues.
We
also
had
a
series
of
radio
boxes
that
would
filter
by
core
contribute.
E
C
E
The
initial
implementation
had
everything
in
it:
they
had
the
drop
down
with
all
the
tags
or
whatever
the
way
I
had
the
search
filter
and
it
had
the
three
radio
boxes
that
allowed
to
filter
by
core.
And
what
have
you?
Because
we
would
remove
the
groupings,
so
we
needed
a
way
to
allow
people
to
filter
just
by
core
or
by
contrib
or
the
custom
modules,
and
that
was
split
off
to
a
different
issue.
I,
don't
have
a
number
yeah.
A
C
C
Right
now,
it's
still
me
issue
number
37.
It's
all
these
cells
mark
dos
needs
work,
yep,
okay,
let's
move
on
said:
okay,
yep,
okay
field
of
all
file
types.
This
allows
files
to
have
different
types
or
bundles
and
also
have
fields
attached
to
them.
It's
issued
26
to
still
kind
of
in
a
holding
pattern
here,
there's
no
update,
but
it's
still
like
a
comprehensive
set
of
pull
requests.
C
E
Similar
issues
were
where
it
was
modules
that
were
being
meds,
that,
were
you
know,
one
of
those
big
huge
ones.
What
we
used
to
do
is
we
used
to
merge
what
we
thought
was
useful,
and
then
someone
would
just
try
to
do
something
by
following
a
tutorial.
For
example,
that
was
made
for
the
d7
version
of
the
respective
module,
and
then
it
would
find
they
would
find
that
there
was
a
feature
missing,
in
which
case
they
would
just
file
a
ticket
and
get
help
and
then
we'll.
We
add
what
we
left
out.
Mm-Hmm.
A
I
tried
several
times
to
separate
stuff
from
file
entity
into
smaller
pieces
and
I'm,
not
sure
that
worked
very
well,
so
it
might
be
best
to
try
and
leave
as
much
as
we
can
together,
because
it
is
really
hard
that
when
you
start
taking
things
apart,
like
the
whole
thing,
it's
a
lot
of
code
on
a
messy,
but
it
works,
and
we
know
it
works.
We
mess
with
it
the
less
likely
it
will
work
or
at
least
working
the
same
way.
So
I
would
I
would
love.
A
E
Remember
also
that,
although
I
don't
think,
there's
been
any
major
version
of
it
that
we
merged
those
contributors
from
d7
at
some
point,
but
then
we
do
not
follow
the
development,
so
there
might
be
features
that
carotid
and
we
miss
them,
which
is
it's
natural.
We
just
we
add
them,
but
yeah
I'll
see
if
I
can
find
a
tutorial
for
that
and
try
to
do
things.
I
think.
E
That
the
whole
issue
was
triggered
or
something
that
a
comment
there
was
triggered
because
someone
actually
tried
to
do
something
with
fields
and
views
and
they
couldn't
do
it.
So
it
was
something
that
anyways,
what
kind
of
worker
clearly
now
okay.
But
my
point
is
that
if
we
leave
something
out,
if
we
miss
something
or
if
we
break
something
by
putting
it,
because
it's
such
a
big
module,
we
won't
be
able
to
know
off
of
the
start.
But
we
didn't
fix
things
on
the
bag,
release,
aw,
yeah
sure,
don't
worry
about
plans,
I'm.
A
E
C
C
C
Actually
testing
it
out
and
if
yeah
making
sure
that
everything
either
works
comprehensively
or
if
it
you
know,
we,
everybody
is
a
little
bit
overwhelmed
with
the
scope
of
it,
and
so,
if
there's
functionality
that
could
be
separated
out,
you
know,
then
that
might
be
good
to
make
a
suggestion
there
as
well.
I
know
in
particular,
there's
some
weirdness
things
like,
like.
We
add
fields
to
file
if
to
image
files
that
make
it
so
that
you
have
like
alt
text
and
title
text
or
it
are
added
as
fields
to
all
images.
C
But
then
all
text
and
tiled
text
fields
are
not
actually
used
anywhere.
It's
it's
a
little
bit
strange
because
they're
not
built
into
the
way
that
files
themselves
are
like
when
you
upload
a
file,
you
specify
alt
and
title,
and
that's
the
alt
and
title
that
you
used
on
that
note.
And
then,
if
you
reuse
that
file
someplace
else,
you
also
specify
alt
and
title,
but
it
can
be
different
on
that
node
than
it
was
on
the
previous
one.
C
A
F
E
A
F
E
Now
that
you
mentioned
testing
and
all
that
it's
mentioned
below,
but
it
might
be
since
you
merged
ckeditor
in
Wando
text,
it
might
be
a
good
idea
to
ask
some
people
that
have
pull
requests
against
gay
editor
related
things
that
are
still
open.
You
just
closed
the
pool
request
and
we
open
it
so
that
the
instance
can
be
fired
within
it
so
that
people
can
test
them
like
if
there's
any
breakages
they
can
be
detected
before
we,
we
actually
create
a
release.
Yeah.
C
C
The
main
issue
on
which
we're
focused
for
1.12
is
a
sub
issue
of
2018
3271
and
that
adds
the
user
interface
for
enabling
core
updates
not
automatic
updates,
but
just
making
it
so
that
there's
you
can
update
core
in
the
same
way
that
you
can
update,
contributes
to
the
user
interface
currently
needs
review.
It
looks
like
it
has
been
getting
some
eyeballs
on
there
there's
potentially
some
unrelated
problems.
I
guess
that
may
be
updating.
C
Just
anything
at
all,
sometimes
doesn't
work,
I,
think
Tim!
You
were
the
one
that
was
providing
that
feedback.
Thank
you
for
trying
that
out,
even
though
it's
not
working,
but
it
does
seem
like
for
other
people.
If
updating
other
things
is
working,
then
updating
cores
working
as
well
so
I
think
it's
continuing
like
more
eyeballs
Jen.
Do
you
have
anything
that
you
know
is
necessary
there
as
well
yeah.
A
C
A
So
there
were
two
people
who
are
on
shared
hosting
who
I
don't
normally.
If
you
might
know
that
Tim
issue
more
than
me,
but
one
of
them
look
like
they
had
sort
of
a
scary
output
or
outcome.
But
I
don't
know,
I,
don't
know
that
that
was
necessarily
the
same
problem
that
you
are
running
into.
Nothing
happens
at
all
I
feel
like
that's
much
better.
We
maybe
shouldn't
hold
this
up.
Yeah.
C
And
even
even
the
way
it's
implemented,
it's
not
really
possible
for
it
to
like
try
to
delete
half
of
it,
because
all
it
does
is
it
just
renames
it
just
moves
it
to
a
different
location,
puts
the
new
one
in
its
place.
If
it
tried
to
delete
the
old
one,
then
it
would
unsuccessfully
delete
part
of
an
old
one
that
wasn't
being
used
anyway.
So.
A
A
E
E
C
C
C
A
E
I've
tested
this
issue
like
over
its
course
not
lately,
but
a
few
times
when
it
got
updated
and
the
only
issues
that
I
was
coming
across
were,
for
example,
I
used.
I
used
to
use
big
books
for
my
local
development,
and
the
permissions
were
not
certainly
so.
I
also
had
problems
with
updating
modules
automatically
from
the
user
interface.
So
that's
why
it
failed.
G
E
If
we
avoid
deleting
things
like,
if
we
keep
at
least
a
version
or
two
of
core
holders
there
at
least
they
can
manually,
go
there
and
rename
the
folders
or
you
know,
restore
the
side.
You
do
have
the
the
problem
when
the
database
updates
have
run,
but
if
they
fail
to
install
in
the
first
place,
I
doubt
that
the
database
updates
with
a
plan.
C
Yeah
I
I
think
that
that
are
based
on
the
way
that
the
mechanism
of
putting
the
new
files
in
place,
like
renaming
the
directory
and
then
putting
the
new
files
in
place,
I
think
that
the
only
thing
that
is
likely
to
happen
if
they
get
to
the
point
that
they've
changed
anything
is
that
they
wouldn't
be
able
to
delete
the
old
files
like
it
would
run
into
a
problem
deleting
the
old
files,
but
it
wouldn't
actually
negatively
affect
the
running
of
their
site.
Yep.
C
C
C
A
C
D
A
A
E
C
A
C
Yeah:
okay:
let's
see,
there's
no
other
updates
on
in
the
the
big
meta
issue
of
automatic
updates
or
just
2018.
We
do
have
package
signing
in
issue
1992
still
in
progress,
but
no
updates
going
on
there
in
the
agenda.
We
also
have
a
issue
for
keeping
core
libraries
up
to
date.
We
already
covered
ckeditor
that
that
got
updated
to
the
latest
for
that
X
version,
jQuery
and
jQuery
UI
I
think
are
still
on
their
latest
stable
releases
of
Ares
for
jQuery
the
one
dot
X
branch
I.
B
E
F
C
A
E
Saying
a
if
you
need
this
feature
you
can
enable
it
just
for
future
priority
nothing
else,
but
late,
you're,
the
security
expert
on
that
and
there's
a
whole
article
in
d,
dot,
org,
and
it
mentions
that
it
is
a
security
issue.
So
I
don't
want
people
to
think
that
we're
taking
things
lightly
or
something
like
that
or
have
an
argument
to
make
on
that
right,
which.
E
Yeah,
the
picket
is
yeah,
that's
the
one
two
five
six
eight
so
I
have
a
pull
request
ready
for
that.
That
adds
it.
So
we
just
need
to
make
small
decisions
with
regards
to
do.
We
want
the
messages
to
be
it's
not
implemented
to
fire
up
during
installation
for
the
Installer.
They
just
notice
in
their
status.
E
Spades
for
now
adds
support
for
people
that
want
to
use
it
so
I
think
it's
less
intrusive
and
we
just
need
to
decide
because
I
find
it
annoying
for
the
people
that
don't
want
to
use
it,
that
they
get
an
error
message
and
that's
the
dot
there.
So
if
we
degrade
that
to
a
warning,
I
think
would
be
okay
like
if
people
complain,
it
would
say
yeah
if
you
still
use
it,
it.
C
Is
supportive,
yeah,
yeah
I,
know
I
know
on
our
Drupal
eight
sites.
It
has
been
a
stumbling
point
like
really
rather
frequently
every
single
time
we
set
up
a
new
domain
like
it
just
keeps
like
oops,
we
forgot
oops,
we
forgot
about
yeah.
We
know
that
it's
there,
but
you
know
the
DevOps.
People
are
the
people
setting
up
the
new
domain
and
they
don't
realize
they
have
to
make
a
Drupal
code
change
in
order
to
set
up
a
new
domain
or
a
new
dev
site,
and
so
it's
yeah.
It's
really
is
kind
of
problematic.
C
So,
that's
if
you
know
where
it
where
it
is
and
if
you
know
what's
causing
the
error,
yeah
so
I
I'm
on
I'm
on
board,
with
what
you're
saying
like.
If
like
it,
we
can
have
it
as
a
security
enhancement,
that's
possible
for
people
to
use
if
they
would
like
to
use
it.
But
I.
Don't
think
that
we
should
complain
about
it.
I
would
I
would
even
say
that
you
know
it
shouldn't
even
be
a
warning
it
that
it
should
just
be
informative.
E
E
If
this
was
a
block,
it
would
be
perfect,
and
so
this
what
this
does
is
it
just
offers
a
new
styling
easily
to
create
custom
blocks
and
style
them
from
the
user
interface
to
show
up
as
messages
and
in
combination
with
the
block
scheduler
module.
This
could
be.
This
could
also
address
another
common
use
case
where
people
wanna
throw
messages
as
ribbons
or
what
have
you
on
the
sides
on
a
specific
date
and
then
have
them
removed.
So
I
think
it's
a
good
feature,
but
there
were
two
ways
to
fix
it:
either.
E
E
E
C
C
And
then
we
end
up
with
a
huge
number
of
way
more
issues
than
we
would
probably
ever
finish
in
the
next
milestone
just
being
put
into
the
next
version,
and
then
every
time
we
don't
get
them
in,
we
have
to
bump
them
all
to
the
next
one.
So
his
suggestion
is
that
we
make
a
tag
for
milestone.
Suggestion
I,
think
that
you
know
you
would
add
a
label
to
an
issue.
C
Saying
I
suggest
that
we
put
this
into
some
other
version
and
then
anything
that
has
a
milestone
suggestion
we
would
have-
or
we
would
by
policy-
require
a
second
person
to
come
in
and
agree
that
it
should
be
pushed
into
that
milestone.
I
think
that
that's
the
suggestion
being
made
here.
Basically,
it's
a
two-person
process
stuff
into
to
prioritize
something
into
a
milestone,
rather
than
being
unilateral,
yeah.
E
G
E
A
A
If
it's
something
really
oh,
this
is
a
big
problem.
We
can
install
backdrop
like
that
goes
in
there
and
it
stays
on
there
until
it
gets
a
full
request.
But
if
it's
something
that's
like
this
little
thing
over
here
is
broken
or
released
comes
out,
there's
no
pull
requests,
I!
Remove
that
bug
fix
Mouse
down
until
it
still
has
a
label
on
it
bug
so
anytime.
You
have
anything
that
has
a
bug
label
and
it
gets
a
for
us
to
get
back
into
the
next
milestone.
But
just
it's
really.
E
A
That
makes
it
very
bug,
fixes
yeah
and
then
for
things
that
are
big
features
like
you
know,
file
in
a
teen
core
I,
don't
think
we
should
require
a
plus
on
that
before
I
can
get
a
milestone,
because
you
want
to
know
what
you're
working
towards
ahead
of
time
like
so
you
can
set
aside
time
to
work
on
it.
So
I
think
that
having
multiple
people
weigh
in
on
it
there
for
a
minor
milestone
is
good
for
a
bug.
That's
not
sony's
a
fault
list.
Where
are
we
going
to
write
this
down?
I?
C
C
E
A
Can
if
you
like
in
a
perfect
case
in
a
perfect
scenario,
what
we
would
do
is
we
would
review
all
of
the
issues
and
say:
oh
yeah,
this
one's
important
and
like
we
would
have
liked
it
consensus
decision.
We're
like
five
people
will
go.
This
should
be
in
the
next
release
we
put
them
in,
but
the
reality
of
the
situation
is
we're.
A
Never
gonna
have
like
five
people
together
in
the
same
place
and
we're
never
gonna
have
time
to
review
all
the
issues
so
I
think
like
letting
people
bubble
up
the
ones
they're
passionate
about
working
on
it's
valuable.
If
particularly
dark
lamont,
be
like
I'm,
really
passionate
about
this
super
heart
issue
and
then
he'll,
be
you
know,
working
on
file,
entity
and
I
would
love
it
if
there
were
fewer
things
in
the
queue
with
final
entity
so
that
it
got
more
attention.
But
I
don't
know
how
to
how
to
facilitate
that.
E
A
Maybe
for
minor
releases
we
picked
the
three
that
we
think
are
our
top
favorite.
These,
the
three
that
go
on
the
milestone
are
on
the
roadmap
page
on
back
from
CMS
in
org,
and
we
keep
them
there
until
we
either
finish
them
or
they
don't
make
the
release.
And
if
we
finish
them,
we
can
put
another
one.
We
can
finish
much
yeah,
okay,
so
I'll
just
side
to
those
three
are:
is
it
like
people
in
this
meeting
every
week,
I
I.
C
Would
hang
on
I
would
suggest
that
we
use
pinned
issues
specifically
for
if
we
have
made
a
release,
and
it
contains
an
absolutely
major
regression.
That
is
catastrophic,
that
a
lot
of
people
are
going
to
be.
Looking
for,
oh
my
god
why's
my
site
broken,
then
we
should
pin
the
issue
that
is
relevant
to
that
yeah
and.
E
C
I
think
well,
I,
guess
what
we're
trying
to
use
pinning
for
through
your
guys's
suggestion
is
that
we're
trying
to
get
more
people
to
look
at
something
that
is
optional?
You
know
something
that
is
a
feature
where,
as
what
what
I'm
suggesting
is
that
pinning
would
be
used
only
for
things
that
people
are
looking
for,
something
in
particular
like
a
like
a
major
issue
that
they
don't
want
to
have
to
search
for
that
it
would
just
be
like.
Oh
it's
right
there
at
the
top.
This.
E
I,
don't
know
if
it's
a
cookie
or
something
or
specific
to
any
I,
don't
that
I
have
on
my
browser,
but
github
remembers
like
if
you
browse
to
the
issues
of
a
repository.
It
remembers
the
filters
that
you
have
applied
and
I
usually
sorted
by
the
most
recently
commented
one
but
I
think
that
there's
also
helpful
indication
of
how
many
comments
are
in
one
issue
like
I
can
see
issues
of
the
55
Commons.
You
know
that
this
is
important.
Yeah.
C
D
C
That
one
that
was
updated,
which
is
really
annoying
in
my
opinion,
so
using
a
pinned
issue,
is
about
the
only
way
that
if
an
issue
was
over
a
week
old,
it
might
get
pushed
off
the
front
page.
But
it's
really
important
that
it
be
the
first
issue.
If
it's
something
that
is
critical,
you
know,
of
course.
Hopefully
we
wouldn't
have
something
that
critical
open
for
a
week,
but
it.
E
There's
only
one
issue,
and
then
we
just
if
there's
no
important
or
critical
issues,
then
we're
just
not
using
a
feature
that
github
is
offering
us
for
promoting
things,
because
promoted,
promoted
issues
will
also
get
the
attention
of
people
that
wanna
test
things,
not
only
people
that
want
to
work
on
the
imagine
producing
code,
it's
a
way
for
us
to
also
or
it
offers
a
way
for
us
to
also
communicate
that
you
know
this
is
important
for
us.
Please
help
us
test
it
or
provide
feedback.
Mm-Hmm.
C
E
E
C
If
we're
gonna
adopt
any
of
these
changes,
we
need
a
place
to
write
it
all
down.
I
guess
you
know
and
I
I
imagine
what
that
would
probably
be
in
the
processes.
There.
Sorry
procedures
directory
you
know,
or
in
maybe
just
in
the
readme
of
the
backup
issues,
queue
itself.
You
know
that's
yeah
kind
of
weirdly.
C
C
A
G
C
Well,
it
seems
like
the
place
to
start
I
guess
would
probably
be
putting
in
procedures.
Maybe
we
would
put
it
in
read
me
and
the
readme
MD
I'm,
not
not
sure,
but
we
also
haven't
even
really
made
any
decisions
about
what
policies
we
want
to
adopt.
Yet,
however,
I'm
kind
of
feeling
like
maybe
we
should
say,
let's
think
about
that
and
come
back
and
convene
on
it
next
week,
yeah
and.
C
E
C
C
A
Looking
through
the
list
here
for
112,
there
are
a
couple
of
things
that
I
attacked
for
one-twelfth
that
are
all
security
related,
I,
bumped,
those
to
113
s
haven't
gone
to
any
movement
since
people
originally
really
good
idea
and
then
that's
out
there.
But
what
we
might
consider
doing
is
when
we
get
around
to
choosing
a
focus
for
113.
We
might
pick
security
and
that
might
be
a
good
time
to
add
that
feature
Gregory.
You
recommend
about
adding
them
sites
that
can
run
years.
A
E
Is
actually
a
good
compromise
now
that
we're
the
subject
if
we
make
sure
that
we
create
the
next
major
man,
so
minor
milestone
the
13,
we
can
Bob
everything
to
that
and
then
cherry-pick
whatever
we
need,
and
only
blink
like
three
issues
or
whatever
on
their
current
one.
That
might
be
a
better
solution.
So
if
we
make
sure
that
we
also
opened
one
thirteen
milestone,
we
can
push
everything
there
and
when
they
release
the
twelve
we
we
open
the
114
milestone
yeah.
We
bought
everything
there.
Maybe
that's
yeah.
A
That's
it
that's.
A
good
idea
is
everything
you
want
to
come
soon.
Those
two
milestones
out
and
I'm
gonna
thanks
for
working
on,
because
one
milestone
out
and
then
when
we
get,
we
just
bump
bump,
both
of
them
yep,
yeah,
okay,
I'm
gonna,
go
through
this
issue
now
and
March,
some
of
the
things
that
we
know
we
definitely
aren't
going
to
get.
F
C
Well,
there's
there's
still
a
whole
lot
of
things
that
are
in
review
and
a
lot
of
things
that
are
TBC
and
I'm.
Just
letting
people
know
that
I'll
be
continuing
to
grind
through
those
or
probably
get
through
all
of
the
cross
ports
for
sure
and
continue
to
hopefully
clear
out
our
our
backlog
just
a
little
bit,
because
we've
got
a
lot
of
things
that
are
piled
up
on
on
the
comater
site,
so
I'm
working
through
this
today,
okay.
C
Okay,
well,
that's
it
for
the
meeting
then.
Thank
you.
Everybody
I
really
appreciate
you
guys
taking
the
time
for
most,
you
guys
out
of
your
holiday
either
to
join
us
online
and
watch
the
video
or
the
present
here
in
the
meeting.
I
hope
you
guys
have
a
great
next
couple
of
days
and
round
out
2018,
really
strong
and
yeah
we'll
catch
you
guys
all
next
year,
yeah.