►
From YouTube: Backdrop weekly 12/3
Description
Backdrop CMS weekly meeting
A
Right,
everybody
is
ember
third
I'm
happy
new
month.
Happy
december
holiday
season
is
here
in
the
US,
a
couple
general
announcements.
We
have
dragon
t-shirts
and
hoodies.
If
you
guys
like
to
make
a
donation
to
backdrop
CMS
for
twenty-five
dollars,
we
will
send
you
adorable
white
dragon,
t-shirt
or
450,
we'll
send
you
a
warm
and
cozy
gray.
Dragon
hoodie
I
think
everybody
I'm
talking
to
right
now
already
has
one
or
both
Oh.
A
Anyone
was
watching
a
video
later
it
wants
to
get
warm
and
cozy.
We've
got
dragon
live,
so
you
can
go
to
backdrop.
Cms
org,
slash,
contribute
and
make
a
contribution
and
Wilson
you
a
happy
little
thank-you
gifts.
We
also
have
free,
phpstorm
licenses
for
backdrop.
Contributors
I
think
we
should
reach
out
and
contact
the
phpstorm
folks
about
getting
a
new
set
of
licenses
for
2016,
since
we've
only
got
a
couple
months
left
flop
on
the
old
ones.
It
seems
silly
to
keep
ending
this
out.
I
think
they'd
be
open
open
to
that
yeah.
B
They've
also
changed
the
way
the
licensing
works
where
previously
they
were
kind
of
like
perpetual
licenses,
but
now
like
you,
could
keep
using
the
license
even
after
it
expired
as
long
as
you'd
already
downloaded
the
software
and
they
changed
it
to
some
kind
of
subscription
model.
Where
they're
attached
to
your
PA
year,
like
jetbrains,
account
or
something
like
that,
so
the
situation
might
change
in
the
future
we'll
have
to.
We
might
need
to
start
over
kind
of
with
our
licensing
efforts
with
those
guys.
Okay,.
B
B
Okay,
so
last
week,
okay,
of
course,
so
since
we
had
an
extra
week
in
there,
we've
got
some
really
great
numbers.
So
we
have
175
total
projects
for
backdrop,
CMS
org.
In
the
backdrop
can't
rib
group
on
github,
that's
14
new
projects
since
two
weeks
ago.
That's
really
exciting,
so
things
like
field
permissions,
coffee,
which
is
kind
of
like
a
Alfred
like
jumping
thing,
auto
node,
title
better
formats,
bunch
of
really
great
important
modules
that
aren't
maybe
top
50
or
maybe
even
top
100
modules,
but
still
just
really
great
projects
to
have.
B
B
So,
in
addition
to
those
projects
they're
on
github,
we
also
keep
track
of
projects
that
have
made
official
releases
and
therefore
synchronize
over
on
backdrop.
Cms
org
and
there
are
108
total
projects
with
official
releases.
Basically
saying
these
things
are
ready
for
production
environments
on
backdrop,
CMS
org
and
that's
six
new
official
projects.
Since
two
weeks
ago,
they're
also
138
total
releases
on
backdrop,
CMS,
that's
10,
total
new
releases
and
the
difference
there.
Basically
being
releases,
are
constant,
like
they
keep
coming
out
even
for
existing
projects
and,
of
course,
new
projects.
B
A
B
A
I
have
a
bunch
of
modules
that
accorded
that
have
in
the
maintainer
section
it's
got
my
name,
but
then
it
says
seeking
additional,
maintain,
errs
and
I've
had
a
couple.
People
be
interested
in
being
the
maintainer
'he's
on
those
modules,
which
would
be
great.
Some
of
them
are
the
original
authors
of
the
Drupal
modules,
and
some
of
them
are
just
people
they're,
like
I
use
that
on
to
all
the
time,
I'll
be
a
maintainer,
and
so,
if
you're
interested
in
joining
the
backdrop
kinship
group
and
haven't
actually
border
to
module
yourself,
that's
still
fine.
A
We
have
a
process
for
that.
That
says
that
you
just
need
to
be
like
vouched
for
by
the
person
who
you're
going
to
be
working
with
on
that
project
so
like.
If
I
want
to
bring
on
a
co
maintainer
one
of
my
modules,
commentators
from
its
application.
I
say
this
person
is
my
co
maintainer.
I
need
them
and
then
we
grant
them
permission.
So
you
don't
have
to
have
a
project
before
you
get
admitted.
A
You
just
need
to
have
communicated
with
the
person
you're
going
to
be
working
with
and
make
sure
you're
all
on
the
same
page.
But
what's
going
on
so
I'm
running
into
that
more
and
more,
where
I
go
to
the
true
blue,
shook
you
go
I'm
going
to
be
using
this
module
on
a
back
job
site.
Dear
Drupal
offer
you
interested
in
supporting
it
and
they
go
well,
I'm
interested
by
time
time
to
do
the
port
right
now
and
I'm
like
no
problem
I'm,
the
port.
A
Let
me
know
when
you're
ready
and
then
we
can
invite
them
in
and
I
think
that
you
know
as
we
go
forward,
we're
going
to
start
getting
these
people
coming
over.
Calling.
Okay,
let
me
see,
what's
going
on
over
here
and
I
think
will
be
great
to
be
able
to
let
them
in
just
with
that
vouch
process.
Rather
than
having
to
say
you
have
to
port
them
much
all
over
again.
But
just
me.
B
B
We
still
have
this
long-standing
problem
where
we're
collecting
analytics
of
what,
what
or
what
sites
are
out
there
and
what
modules
they
have
running
or
what
project
stamp
running
more
accurately,
but
the
analytics
for
number
crunching,
those
into
actual
charts
or
into
tables
is
not
functioning
quite
correctly.
So
we
have
this
issue
for
a
little
while,
where
it
was
just
zeroing
everything
out,
so
we
lost
a
bit
of
data
for
a
month
or
so
there,
and
since
then
we
turned
back
off
the
number
crunching
script.
B
So
that's
a
that's
an
issue
that
is
actually
in
project
module
itself.
It's
issue
number
nine.
In
the
backdrop,
control-
and
if
you
would
like
to
up
on
that,
we
can
help
facilitate
it
by
getting
you
database
dumps
of
all
of
the
raw
numbers
that
we
have
for
backup,
CMS
org
because
actually
accruing
a
large
number,
a
large
base
of
numbers
from
external
websites
can
be
kind
of
difficult
for
a
local
is
set
up.
B
Let's
see,
some
things
are
hoping
to
do
after
we
get.
The
basics
done
is
that
we
want
to
start
tracking,
not
just
which
projects
are
downloaded
and
enabled,
but
more
specific
things
like
which
individual
modules
are
turned
on,
say
within
core
or
within
a
particular
project,
and
also
things
like
which
options
are
enabled
on
particular
sites
like
how
many
sites
are,
how
many
sites
support
clean
urls
or
how
many
sites.
C
B
Now
we
don't
save
anything
about
those
sites.
The
only
thing
that
we
saved
is
we.
They
report
the
names
of
the
projects
that
they
are
currently
running
in
the
versions
of
those
projects
so
like.
If
you
download
the
you
know
3.4
version
of
web
form,
then
we
are
told
that
you're
running
the
web
form
project
version,
3.4,
okay
and
that's
really.
C
B
C
B
B
Let's
see
okay,
so
project
browser
so
a
feature
that
we'd
love
to
have
in
the
near
future.
I'm,
not
sure
it's
going
to
happen
in
1.3,
because
that's
just
about
a
month
away
honestly
we'd
like
to
make
it
so
people
can
find
and
install
modules
and
themes
from
within
backdrop
without
needing
to
visit
backdrop,
CMS
or
github
or
anywhere
else,
and
so
there's
this
project
that
we've
boarded
an
expanded
called
project
browser.
B
That
is
a
module
that
you
can
install
inside
of
your
backdrop
website
and
uses
the
existing
backdrop
facility
for
installing
modules,
themes
and
layouts,
which
already
exists
and
already
works,
and
it
just
adds
an
interface
on
top
of
it.
Lets
you
actually
find
projects
from
backdrop.
Cms
don't
work
directly
rather
than
needing
to
go
and
find
URL
to
a
zip
file.
So
project
browser
has
actually
been
working
really
great
for
a
while,
but
project
browser
server.
The
component
that
lives
on
backdrop,
CMS
org,
has
been
a
little
bit.
Buggy
we've
got
issue
number
870.
B
B
The
the
query
string
to
specify
how
many
projects
per
page
and,
like
page
one
page
to
page
three,
isn't
working
quite
right
right
now.
It
just
returns
all
projects
all
the
time
which
seems
like
it's
a
relatively
simple
problem
to
fix,
but
it's
a
matter
of
finding
where
that
fix
needs
to
be
applied.
If
we're
pretty
sure
that
it's
some
kind
of
like
you
know
missing
a
equality
operator
or
something
like
that,
like
good
it
wherever
it
is,
it's
it's
it's
going
to
be
a
simple
fix,
but
it's
probably
just
sneaky.
C
We
had
a
discussion
based
on
the
security
issues
of
self
installing
modules,
not
not
only
with
the
fact
that
the
websites
are
then
going
to
be
uploading
their
own
PHP,
but
then,
if
all
of
the
backdrop
websites
are
going
through
one
project
server,
that's
a
single
point
of
failure
and
exploitation.
That
of
someone.
If
we
don't
secure
that
server
well
enough,
they
could
theoretically
compromise
every
backdrop
site
that
uses
the
automatic
project
browser.
B
Yep,
so
it's
it's
interesting,
because
the
the
security
concern
is
actually
identical
to
our
situation
today,
because
a
backdrop
and
Drupal
7
and
Drupal
8
for
that
matter,
I'll
use
that
essentially
the
same
mechanism
for
installing
projects.
So
it
right
now
you
can
install
modules
and
themes
into
a
triple
seven
website
and
you've
always
been
able
to
do
that
for
the
entire
triple
seven
release
through
the
user
interface.
So
the
security
concern
has
not
changed
since
Drupal
7.
Let's
release
the
only
thing
that
we're
doing
is
we're
making
it.
B
So
that
feature
is
actually
useful
by
adding
a
browser
that
provides
the
URLs
for
you
and
then
just
puts
that
into
the
existing
mechanism
for
downloading
and
installing
the
software.
So
the
downloading
in
software
that
downloading
and
installing
is
old.
It's
just
the
browsing
that
is
new
but
I
totally
I
totally
agree
that
it's
going
to
be
a
much
bigger
problem
because
nobody
uses
that
functionality
now,
because
it's
too
arcane
to
just
like
copy
and
paste
a
URL
from
someplace
and
paste
it
in
and
then
say
you
know,
install
it's
just
it.
B
I
mean
the
the
mishmash
of
users
who
would
want
to
use
an
in-browser
installer
versus
users
who
would
want
an
umbrella
and
can
also
copy
and
paste
a
URL
that
they
knows
legitimate,
like
it
totally
negates
the
entire
purpose
of
it.
Almost,
however,
I
totally
agree
about,
like
you
know,
if
that
single
server
were
to
go
down
or
something
like
that
or
to
start
providing
spooky
or
else,
we
would
definitely
have
some
issues.
B
B
Okay,
next
item
on
the
agenda
is
drush
for
backdrop.
Josh
for
backdrop,
is
our
longest-standing
infrastructure
issue.
They've
been
talking
about
it.
Basically,
since
since
they
want
a
backdrop,
there's
some
great
stuff
happening
in
dress
for
backdrop
Lane,
we
have
a
working
prototype
of
brush
for
backdrop.
B
It's
it
currently
is
living
under
my
personal
repository,
but
in
the
future
we
hope
to
move
that
into
the
contribute
and
with
enough
success
that
may
actually
be
moved
into
core,
and,
although,
since
they
have
Mike
here
with
us,
I
know,
Mike's
also
been
advocating
for
having
a
separate
like
backdrop,
specific
command
line
tool
which
I've
always
been
also
kind
of
in
favor,
of
how
every
for
the
short
term
for
the
familiarity
of
the
triple
audience.
I
do
think
that
supporting
drush
would
be
a
great
first
step
for
us
yeah
and
our
own
thing.
B
Yeah
and
I
think
I
think
it
would
be
that
if
we
included
a
command-line
tool,
so
then
in
fact
our
core
itself,
then
that
would
probably
be
the
thing
nothing
in
the
future.
But
yeah
there's
some
convenience
that,
with
the
way,
drush
works
right
now
that
it's
kind
of
just
like
always
available
and
you
can
use
the
outside
of
the
Drupal
installation
to
like
download
Drupal
itself
but
really
beyond
downloading
Drupal
and
installing
Drupal
without
Drupal.
Yet
existing.
It
really
kind
of
has
limited
usefulness
so,
but
yeah.
A
This
is
Drupal
site
and
having
to
like
rewire
their
brains.
Use
different
commands
on
one
versus
the
other,
is
gonna,
take
a
little
while
and
so
I
think.
If
we
could
make
it,
you
know
you
still
typed
rush,
but
maybe
you
can't
use
like
josh
config
update
or
whatever
on
one
side
of
the
other
it'll
help
that
learning
process
of
moving
from
one
to
another
and
sure
when
backrub
two
comes
out,
maybe
well
no,
like
during
the
day
I
spent.
A
Ninety
percent
of
my
time
on
backdrop,
in
only
ten
percent
on
Drupal,
like
it
becomes
less
painful
to
make
a
change
not
have
to
keep
changing
back
and
forth,
but
right
now,
I
think
the
majority
of
people
are
still
spending
the
majority
of
time
on
Drupal
and
using
Josh
the
majority
of
time
and
so
for
life.
If
you
have
to
use
brush,
then
it
wouldn't
be
quite
as
easy.
Yeah.
B
Then,
if
you
switch
to
a
backdrop,
installation
dress
just
recognizes
backdrop
and
the
commands
that
you
are
used
to
using
just
work.
So
you
can
use
drush
up.
Db
dress,
CC
for
CCL
trips,
cron
job
sequel
connects
all
of
those
things
work
right
now,
some
things
that
are
going
to
take
a
lot
more
effort,
though
drush
dl
dress,
dress
up
like
brush
up
on
macho
those
things
are
a
lot
more
elaborate
because
they've
part
integration
with
project
module
and
there's
a
lot
of
very
specific
code.
B
Oh
and
rush,
install
the
installed
thing
and
rush
is
crazy.
It
like
copies
out
like
hundreds
of
lines
of
code
out
of
core
and
puts
it
into
josh,
and
so
of
course,
the
installation
process
isn't
quite
identical
between
backup
and
and
drupal.
So
we
have
to
copy
and
paste
another
big
chunk
of
core
out.
It's
just
not
really
yeah.
B
B
We
should
use
that
same
issue,
issue
47,
to
talk
about
testing
out
the
prototype
and
which
commands
should
be
used
and
things
like
that.
The
the
prototype
itself
says
which
commands
are
supported
and
there's
only
like
a
half
dozen
of
them
and
and
their
children.
So
if
there's
specific
ones
that
you
think
that
we
should
support,
then
let's,
let's
talk
about
it
in
that
issue,
47,
which
is
the
same
issue
that
we've
been
discussing.
Everything
else
dress
related,
okay,.
C
B
B
B
Cool
okay-
let's
see
here,
okay,
so
that
the
flagship
website
back
to
up
CMS
org,
there's
been
a
couple
of
things
that
we've
been
working
on,
that
we
would
love
to
see
happen
in
the
near
future.
One
thing
that
we
we
did
recently
is
that
we
added
pages
for
modules,
themes
and
layouts,
but
there's
issued
to
follow
up
to
add
a
bunch
more
functionality
to
those
pages.
The
issue
is
issue
95
that
talks
about
the
project
search
pages
on
factor
of
CMS
org.
B
A
Of
it,
we
can
do
without
a
ton,
more
development,
because
we
don't
have
the
data
we
need
to
seem
like
there's
no
views
support
for
like
links
to
github,
so
we
can't
put
those
on
paid
on
them
on
the
pages
and
stuff.
So
all
the
stuff,
that's
in
the
design,
needs
to
have
development
done
before
we
can
there's
just
no
there's
no
data
there
to
actually
yeah.
A
So
yeah,
if
we
have
anyone
who
wants
to
put
any
development
time
into
backdrop,
CMS
org,
we
have
beautiful
designs.
We
just
can't
implement
in
the
epic
as
for,
even
though
we
have
data
in
the
database,
there's
no
way
to
get
it
out
and
just
lay
it
on
a
node.
So
we
need
to
either
like
put
it
into
the
node
view,
or
we
need
to
expose
the
two
views
because
we
have
places
like
there
are
listing
pages
right
now
or
abuse.
A
What
we're
also
working
on
right
now
is
allowing
people
the
ability
to
log
in
to
the
backdrop
CMS
to
our
website,
which
we're
hoping
to
open
up
on
january
first,
and
so
in
order
to
get
that
done,
we've
decided
to
look
at
all
the
information
we
want
to
collect
from
people
and
we've
done
a
cursory
setup
of
the
most
of
the
profile
fits
fields
that
we
want
to
collect
on
vector
up
CMS
to
org.
It's
been
even
less
to
give
that
a
test
for
us.
Let
us
know
we
can
create
an
account.
A
You
can
log
in
and
start
playing
with
it.
Let
us
know,
there's
anything
you
think
we
missed
that's
important
to
track
or
if
there's
anything,
we
are
tracking
that
we
shouldn't
be
tracking.
We
ready
to
get
some
feedback
on
that
there's
three
things
that
we
need
to
either
port
modules
for
or
install
modules
for,
and
that
is
the
social
media
link.
So
if
you
want
to
put
your
Twitter
Facebook
or
whatever
on
there,
we
can
add
that
the
country
you
live
in
and
the
languages
you
speak,
those
four
things
are
coming
soon.
A
Everything
else
is
up
there
now
they've
turned
over
these
lists
of
we
want
to
collect
from
people
to
our
designer
Darius
and
we're
supposed
to
get
a
working
profile
page
designed
by
the
seventh
of
December.
So
we
can
have
it
implemented
by
the
first.
If
that
ends
up
not
getting
implemented
in
time,
we'll
probably
still
start
collecting
information
and
then
make
it
pretty
later
on.
A
First
and
then,
shortly
after
that,
we're
going
to
do
single
sign-on
with
github,
so
that
people
can
like
the
github
account
store
their
backdrop
accounts
or
not
have
to
create
a
backdrop
account
in
the
first
place
they
don't
want
to,
and
then
we
can
do
things
like
allow
people
access
to
edit
projects
they
maintain
I,
don't
know
that
wait,
there's
any
significant
reason
to
do
that
right
now.
But
if
we
wanted
to
like
let
people
change
photos
and
stuff
without
having
to
commit
pray,
these
two
get
hub.
A
A
It
would
be
great
to
be
at
a
place
where
you
could
point
them
and
say:
here's
a
bunch
of
sites
that
are
running
back
job,
so
we'll
get
that
on
after
the
user,
login
there's
a
bunch
of
other
stuff.
We
want
to
do
on
our
main
website
to
a
service
provider
listing
an
event,
calendar
jobs
boards
and
a
bunch
of
other
stuff
too,
like
getting
a
blog
up
and
running
where
we
can
talk
about
the
stuff.
A
That's
going
on
with
the
backdrop,
I
think
that
would
really
help
our
marketing
and
you
may
should
put
that
in
this
list
as
well
blog
yeah,
just
it
you
know,
there's
going
to
be
plenty
of
needs
evolving
over
time
so
website.
Our
website
is
a
work
in
progress,
lots
of
shiny
teeth.
Maybe
we
need
to
kind
of
form
something
else
like
that.
C
A
C
C
Just
to
say
one
thing:
one
things
I'd
love
to
see
more
open
great
I'll
doing
it
is
like
there's
a
section
of
enjoy
tons
of
other
improvements,
including,
and
then
we
list
out
all
the
things
that
we've
improved.
If
we
could
is
there,
is
there
a
section
on
the
site
that
actually
sort
of
breaks
those
out
and
actually
describes
the
individual
improvements
leg.
C
That
would
be
great
because
I
keep
trying
to
describe
how
backdrop
has
made
a
bunch
of
improvement
on
drupal
7
like
people
get,
that
is
the
pork
of
drupal
7.
They
go
okay,
drupal
and,
like
you,
had
views
and
stuff
like
that,
but
I
think
our
big
R
big,
the
thing
we
need
to
do
sell
people
on
who
are
coming
from
Drupal
is
that
we're
making
changes
the
core
and
those
changes
make
sense
when
they're?
A
A
C
See
if
we
just
have
one
page
with
everything
on
it
and
then
those
little
both
points
can
link
with
just
with
just
a
anchors
down
to
the
proper
section.
That
would
be
probably
a
good
solution
for
the
moment.
That's
obviously,
obviously
we're
going
to
keep
making
changes
between
Drupal
and
backdrops,
so
I
mean
I.
Think
we
might
want
to
think
about
some
sort
of
change.
C
B
B
C
B
C
We'd
probably
have
we
could
if
we
want
to
do
a
series
of
short
videos,
like
you
know,
hey,
let's
look
at
the
new
layout
thing
is
different
from
Drupal
and
just
run
through
it
and
like
just
a
minute
or
two.
So
we
have
a
page
with
a
bunch
of
these
videos,
so
people
just
watch
really
short
videos
I'm
like
oh.
This
is
how
it
works
now,
just
to
get
just
to
get
Drupal
people
up
to
speed
with
what
changes
have
been
made
so
far.
B
B
Oh
sorry,
every
time
a
new
version
of
Drupal
comes
out,
we
make
sure
that
we
cross
for
every
applicable
fix
for
Drupal
7
into
backdrop
as
well,
and
so
there's
a
number
of
those
since
Drupal
that
Drupal
7
dot
40
came
out
that
have
not
yet
been
patched
ported
over.
Let's
issue
1331.
In
the
backdrop,
CMS
issue
queue.
Those
are
great
issues
for
novice
developers
as
well
as
experienced
developers
because
really
the.
Why
there's
a
wide
range
of
how
complicated
fixes
can
be
in
Drupal
7?
B
One
point
two
point:
three:
it's
really
just
kind
of
whenever
there's
a
significant
number
of
fixes
that
make
having
the
release
worthwhile,
then
we
will
push
out
that
release
and
we
don't
need
to
get
all
of
those
cross
sports
from
7
dot
40
over.
We
can
on
base
the
way
to
the
next
minor
release,
or
next
bug
fix
your
at
least
to
include
those.
B
The
next
item
that
I
have
here
is
a
PHP,
seven
support.
Why?
Because
PHP
7
came
out
today,
it
came
out
like
an
hour
ago.
Exciting.
Is
that
ever
yeah
yeah
I
PHP?
Congratulations,
we're
so
happy
to
have
our
favorite
programming
language
have
a
new
nature
version
like
this
and
so
sub
PHP
7
is
out
and
probably
for
us
lovely
backdrop
developers.
Our
favorite
feature
of
PHP
probably
isn't
going
to
be
the
new
language
features,
because
we
have
a
high
emphasis
on
compatibility,
so
we
will
be
using
great
many
new
language
features
for
a
while.
B
But
the
thing
everybody
will
love
is
that
PHP
7
is
a
lot
faster
than
previous
versions
of
PHP.
They
advertise
up
to
twice
as
fast
as
PHP
5.6,
which
is
always
a
great
thing,
and
so
we
would
like
to
get
backdrops
support
for
PHP
7,
totally
one
hundred
percent
and
we're
actually
really
close
to
that.
We
have
an
issue
for
tracking
PHP
seven
support
its
1386
and
we've
been
working
this
week
on
making
backdrop
fully
PHP
7
compatible.
It's
actually
already
like.
B
Even
if
you
use
it
today,
you
would
have
very
few
problems
with
PHP,
7
and
backdrop,
but
there's
a
couple
of
things
that
really
simple
fixes
that
really
give
us
to
like
ninety-nine
percent
and
then
there's
just
one
or
two
minor
issues
that
are
the
last
little
bit.
But
what
we're
trying
to
do
in
that
issue?
B
Suite
will
run
simultaneously
against
our
minimum
PHP
version,
which
is
PHP
53
and
the
latest
PHP
version,
which
is
PHP
7,
and
so
every
time
we
submit
a
pull
request
will
have
that
tested
against
both
versions
and
in
theory,
if
we
really
wanted
to,
we
could
add
54
and
55
also,
but
there's
a
certain
amount
of
like
responsibility
towards
like
not
totally
crippling
travis
CI,
with
our
with
bunch
of
expensive
back
drop
tests.
That
I
feel
like
for
now
like
just
getting
five
three
and
seven
doing
both
of
those
would
be
a
great
idea.
B
Let's
see
the
next
minor
version
of
backdrop,
one
point
three
point:
oh
we're
hoping
to
make
that
the
user
experience
release,
which
is
basically,
we
don't
have
any
big,
flashy
headline
features
like
date
or
pasado,
like
we
did
in
previous
releases
of
new
major
expansions
of
functionality.
Instead
we're
trying
to
polish
the
functionality
we
already
have
and,
in
particular
the
areas
that
need
the
most
efforts
are
kind
of
like
all
of
the
major
site.
Building
tools.
Layouts
is
a
shoe
345,
more
administration
views
which
is
1101.
B
A
Sure,
there's
a
bunch
of
issues
with
pull
requests
that
are
just
sitting
there
and
then
there's
a
bunch
of
issues
that
are
also
tagged
novice.
So
if
you
wanted
something
that
could
be
a
quick,
easy
improvement
that
could
be
good
place
to
jump
in
I
said,
I
was
grabbing
novice
issues
when
I
don't
have
a
lot
of
hours
to
throw
in,
but
I'm
like.
Oh
I
want
to
make
some
kind
of
headway.
So
I'll
grab
a
novice
issue
and
filed
for
request.
But
then
this
pull
request
sit
there
waiting
to
be.
A
So
you
can
either
jump
in
and
file
for
West
or
you
could
review
pull
requests,
which
is
also
super
helpful
for
us
and
at
least
give
it
a
cursory
look
and
say
you
know:
code
syntax
is
wrong
or
tests
or
failing
needs
work,
and
then
that
way
the
people
who
worked
on
them
will
get
notified
that
they
need
to
come
back
in
just
a
mark.
Yeah.
B
That's
true,
I'm,
totally
being
a
bottleneck,
which
is
something
we
wanted
wanted
to
avoid
and
want
to
avoid
in
the
future
kind
of
the
review
bottleneck,
and
so
if
people
can
review
each
other's
work
rather
than
just
having
the
committer,
which
is
right
now,
it's
just
myself.
Reviewing
everything
then
cross.
Reviewing
of
pull
request
would
be
super
helpful.
B
We
are
also
planning
in
the
future
like
our
management
structure,
we
specifically
organized
it
so
that
we
could-
and
we
we
definitely
do
want
more
members,
both
of
the
guided
council
that
the
PMC
and
have
a
large
number
of
committers,
but
we're
working
on
on
kind
of
getting
I
mean
honestly
there's
a
lot
of
candidates
in
our
current
community
that
we're
just
like
you
know
we're
waiting
for
the
right
time
to
really
get
more
contributors
kind
of
glean
them
from
from
our
community,
because
we
have
great
people
in
our
community
already.
It's
just.
B
A
I
mean,
I
think
I
think
some
of
those
are
metas
like
the
layouts
follow-up,
where
some
of
the
razor
experiencing
some
of
our
new
new
features,
but
as
much
as
it
we
can
get
done.
We
can
I
think
things
like
the
project.
Browser
are
also
going
to
be
significant
user
experience.
Improvements
and
I
know
that
there's
a
lot
of
momentum
around
that.
A
So
if
we
could
get
that
unblocked,
I,
don't
know
if
that'll
get
done
in
time,
but
it
would
be
really
cool
if
it
did
yeah
just
generally
like,
as
you
guys
are
using
the
tool.
You'll
run
into
user
experience,
issues,
I
rented
the
whole
time
and
then
I'm
like
this
is
frustrating
than
likely.
We
can
fix
this
great
an
issue,
and
I
think,
like
the
more
of
those
things
we
can
get
done,
will
improve
that
experience.
People
going
this
is
frustrating
like
that.
A
C
Cool
all
right,
I'd,
say
one
big
outstanding
thing
we
might
want
to
consider
for
maybe
not
circle.
You
XO,
I
think
the
whole
coming
up
with
a
new
base
theme
default
default
based
thing
for
a
face
theme
for
backdrop,
is
company
a
big
at
least,
look
and
feel
issue
that
we
probably
want
to
address
at
some
point
soon.
Yeah.
A
That's
why
Andy
just
sent
to
like
how
do
we?
How
do
we
what's
our
process
for
that?
We
actually
just
talked
about
this
a
little
bit
in
the
design
meeting
as
well,
where
nate
was
looking
through
the
issue
queue
like
where's
the
issue
for
adding
a
new
theme
decor,
and
then
he
was
like.
Oh
there
isn't
an
issue
and
I
think
it's
because
we
needed
something
more
specific
than
that.
Like
there's.
C
A
Well,
what
we
decided
in
half
hour
ago
we
can
use
your
feedback
on
this,
too,
is
that
it
would
be
great
if
the
issue
was
very
specifically
like
put
X
theme
in
poor,
and
then
we
could
evaluate
that
theme
and
figure
out
if
it's
a
candidate
for
core
and
if
not,
why
not?
So
we
can
choose
another
theme
that
might
be
a
good
candidate
for
core
or
if
it
needs
work
like
what
are
the
things
we
need
to
work
on,
so
we
can
actually
get
some
actual
item
job
interesting.
A
C
C
The
issue
that
I
did
was
basically
rather
than
yes
to
give
you
that,
but
it
also
be
good
to
get
a
list
of
what
features
we
want.
The
default
theme
to
have
like,
what's
important
to
us
and
stuff
like
that,
and
just
get
a
general
agreement
on
what
how
we're
evaluating
whether
or
not
it
should
be
the
default
theme.
We
can
actually
sort
of
have
something
to
evaluate
same
time.
Yeah
that'd.
A
A
B
Found
it
it's
1361,
okay,
yep
and
Mike
Mike
goes
in
there,
so
that
that
looks
like
that's,
probably
it
hey.
How
about
that?
Okay,
don't
put
this
into
the
agent
it
I'm
gonna.
Put
this
into
1.4
agree:
I,
don't
think
that's
gonna
happen
anytime
soon,
I
mean
second
half
of
the
next
month.
All
right
I
also.
A
B
A
I
think
we've
already
kind
of
went
on
the
SAS
path,
the
beginning,
and
we
decided
we
didn't
want
to
incest
because
we
wanted
our
code
to
be
accessible
to
the
lowest
common
denominator.
So
these
people
that
use
CSS
but
don't
know
sax
and
then
we'll
we'd
SAS
for
more
sophisticated
people
who
are
going
to
be
working
trip.
That
said,
I
think
you
know,
there's
there's
room
to
re-evaluate
that,
especially
if
we
do
end
up
using
something
like
this
job
or
it's
like
you
can
have
compiled
files
and
non
compiled
versions.
A
C
A
And
also
the
quality
of
the
CSS
that
comes
out
of
something
that's
generated
from
SAS
is
significantly
different
than
something
that
was
handcrafted
by
a
human
being
and
the
way
it's
organized
and
stuff
should
also
be
taken
into
consideration
now,
not
to
say
the
quality
of
the
CSS.
It's
in
poor
right
now
is
any
good
good
or
have
any
you
know
real
world
site
that
always
ends
up,
not
what
you
intended,
but
yeah
I
have
only
thing
we
can.
A
We
can
have
a
competition
again,
just
the
last
time
we
had
it,
we
decided,
let's
just
leave
it
in
CSS
and
not
have
to
worry
about
it
and
I
also
think
it
would
be
great
if
we
can
use
something
like
bootstrap.
The
grid
system
is
a
little
weird
because
the
grid
system
doesn't
Romanian.
Do
the
theme
right.
A
That
would
be
the
layouts,
but
I
think
that
if
we
do
go
with
something
like
bootstrap
in
the
theme,
we
might
want
to
go
with
something
like
boots
Jeff
grid
system
in
the
layout,
so
that
we
can
match
the
two
together.
But
that
would
definitely
be
a
two
point,
O
think
so
it
would
require
like
rewriting
classes
and
CSS
for
our
layout
system.
So
lots
of
interesting
puzzle,
pieces.
B
Yeah,
although
I,
if
we
want
to
talk
about
new
core
themes,
we
do
have
the
design
meeting,
which
was
today,
unfortunately
before
this
being
but
every
two
weeks.
We
have
another
designing
and
that
would
be
the
best
time
to
talk
about
it,
because
it's
always
on
that
agenda
to
talk
about
a
new
front,
end
thing:
yeah,.
A
B
So
other
items
in
so
longer
term
may
15.
2016
is
the
slated
release
date
for
1.4
point
0,
which
is
four
months
after
january,
fifteenth
so
for
a
rolling
release
cycle
every
four
months.
We
have
a
new
release.
So
one
point
four
point:
oh,
it
will
be
out
in
May
and
we
don't
have
fur
my
ideas
or
firm
commitments.
I
should
say
to
any
features
in
one
point:
four
point:
oh,
but
we've
got
some
pretty
good
ideas
of
things
that
we
would
like
to
see.
B
In
particular,
references
module
is
kind
of
really
high
on
our
list
that
we
have
ports
of
no
reference
and
user
reference
modules
that
are
available
for
backdrop,
but
the
entity
reference
module
has
not
been
fully
ported
to
backdrop,
but
it's
kind
of
the
most
likely
thing
that
we
would
like
to
see
in
court.
However,
it
hey
as
entity
references
written
now
is
not
what
we
would
like
to
see,
but
the
capabilities
that
it
provides
based.
C
A
C
B
Well,
anyway,
that's
the
number
one
feature
that
we'd
love
to
see
in
backdrop.
One
point
four
point:
oh,
hopefully,
a
coors,
a
better
entity.
Api
really
makes
it
so
that
there
isn't
so
much
abstraction
necessary
in
whatever
references
module.
We
come
up
with
because
things
like
you
know,
getting
past
an
object
and
getting
its
ID
or
getting
its
entity
type
or
getting.
B
Its
bundle
is
not
they're
out
they're,
all
just
not
methods
onto
the
objects
that
are
passed
in,
and
so
we
have
these
abilities
that
we
didn't
have
in
Drupal
7
that
entity
reference
module
had
to
do
a
bunch
of
crazy
bending
over
backwards
and
weird
abstractions.
In
order
to
get
that
sort
of
information
and
we're
hoping
that
the
backdrop,
implementation
can
be
quite
a
bit
simpler
because
we
can
accommodate
core
to
the
needs
of
the
references
module
if
necessary,
and
hopefully
it
should
already
be
pretty
accommodating
yeah.
A
B
So
that's
number
one
feature
for
1.4.
We
also
had
been
thinking
about
redirect
module
potentially
moving
that
into
core,
whether
that's
a
separate
module
or
part
of
path
module
like
we're
not
totally
clear
on
that
yet,
but
some
effort
into
making
the
redirect
modules
functionality
available
in
court,
and
then
we
just
added
this
running
theme
so
previously
references
and
redirect
or
kind
of
our
big
items
running
theme.
B
Okay,
let's
see
that's
not
all,
though
there's
always
just
the
regular
constant
improvement
to
backdrop
in
particular,
I
mentioned
earlier
the
ux
issues
that
are
square
bracket,
ux
close
square
bracket.
You
can
find
those
on
github.
We
also
have
a
whole
category
of
issues.
Health
developer,
experience
with
which
are
square
bracket,
DX
whole
square
bracket,
both
of
those
are
great
places
to
start.
B
If
you're,
just
getting
into
backdrop
and
looking
at
you
know,
I
just
want
to
do
something
to
to
backdrop
cord
those
kinds
of
things
can
be
great
because
they're
low
pressure,
no
kind
of
deadline
just
whenever
we
can
get
to
it
kind
of
fixes,
so
that
there
can
be
great
starting
points
as
well
Sprint's
every
Thursday.
Today
we
have
after
the
meeting
we
have
a
like
code
review
code
coding
parties.
C
A
The
problem
is
that
get
er
gives
you
one
chat
for
every
repository
and
anyone
who's
a
member
of
either
repository
can
create
one.
So
backdrop,
issues
is
public
repository,
so
it's
a
public
chat
channel
factor
up
whatever
the
other
one
was
just
I.
Think
for
anyone
who's
a
member
of
backdrop,
the
repository,
so
it's
private,
so
I
try.
B
B
So
I
would
say
for
sure
the
most
consistent
and
reliable
thing
is
the
issue
queue
it's
our
primary
means
of
communication
and
that
recommends
participating
there.
If
nowhere
else,
we
also
read
it
ready
to
come
/
r,
/
backdrop
if
you're
interested
sharing
links
of
around
the
web
and
discussing
them
other
backdrop
community
community
members,
that's
a
good
way
to
go.
A
Thursday
well,
okay:
tonight
there
is
auckland
tech
mixer
that
needs
going
to
be
going
to
and
then
next
thursday
we're
doing
a
mini
sprint
with
one
of
the
core
committers
from
Suvi
serum
to
do
a
little
kind
of
show
until
if
both
products
and
then
try
and
sit
down
forks
to
be
and
see
if
we
can
get
earning
on
backdrop,
there's
a
couple
reasons
for
this
nate
night
at
the
nonprofit
developer
summit.
We
were
out
last
week,
then
number
one
two
weeks
ago,
number
one
question
we
got
was:
does
it
work
with
sebi?
A
A
The
backdrop
foundation
might
actually
have
a
really
good
use
case
for
using
sebi
and
if
we
start
on
eating
our
dog
food
using
backdrop
and
to
be
together,
we'll
actually
know
how
good
the
integrations
working
and
making
sure
that
we're.
I
doing
things
in
ways
that
our
community
can
benefit
from
as
well
so
I
think
having
a
little
powwow
with
the
civvy
folks.
A
Next
thursday
is
going
to
be
great
in
terms
of
moving
that
project
forward
for
vectra,
so
I
think
that'll
also
be
really
valuable
to
our
intended
target
audience,
which
is
supposed
to
be
non
profits
because
they
are
often
used
to
me
and
I.
I
also
heard
that
TV
is
coming
out
with
a
whole
bunch
of
new
user
experience,
improvements
as
well
that
I
got
season
designs
at
the
summit
that
look
make
it
look
a
lot
slicker
and
so
I'm
looking
forward
to
getting
my
hands
on
those
too.
So
we'll
see
how
that
goes.
Oh.
A
Also
speaking
of
offense
I'm,
not
sure
if
this
is
in
the
agenda
or
not,
but
we
have
officially
confirmed
a
backdrop
training
again
at
Sam
camp
this
year,
we're
gonna
we're
currently
scheduled
for
a
half
day
on
Thursday,
but
I
think
they're
trying
to
get
us
a
full
day
on
Thursday,
but
will
depend
on
how
many
other
trainings
they
get
and
sign
ups
and
all
that
stuff.
So
if
you
live
near
San
Diego
I
want
to
visit
San
Diego
in
February.
You
can
do
a
backdrop,
training
or
was
one
of
you
guys.
B
B
B
B
But
besides
expanding
our
own
blog
section,
we
should
try
to
author
posts
on
other
existing
blogs,
and
so
he
suggested
the
idea
of
using
guest
posts
where
we
could,
if
we
being
the
backdrop
community,
could
post
to
other
people's
blogs
that
frequently
they
get
a
lot
of
traffic
that
that
allow
other
people
to
basically
say.
Oh,
this
post
is
from
this
person
over
here
and
then
we
can
write
up
a
post
on
somebody
else's
blog
and
I
can
generate
a
lot
of
traffic.
B
B
We
should
put
in
descriptions
of
what
we
talked
about
and
what's
unique
about
each
meeting
in
the
descriptions
and
title
them
appropriately
saying
like
what
the
topic
is
for
this
particular
week,
which
is
a
little
bit
tough
because
you're
talking
about
the
same
things
every
week,
but
there's
there's
always
minor
variations
and
then
also
use
analytics
on
backdrop,
CMS
torque,
which
I
think
we
are
do
you
do
it.
Google
analytics
installed
on
their
gin,
yeah.
A
B
So
anyway,
there's
there's
more
though
apparently
monkey
is
in
marketing.
That's
the
police,
it's
at
City,
one
said
so
and
I
think
backed
it
up
really
strongly
there.
So
there's
a
lot
of
really
great
ideas
in
there
into
the
backdrop.
Cms
org
issue
queue,
issue,
112
and
there's
link
to
it
in
the
agenda.
Of
course,
Jen
are
you
making
some
issues
for
all
of
these
yeah.
A
B
B
Awesome
yeah,
so
lots
of
great
marketing
opportunities
and
lots
of
great
ideas
and
I
think
thing
about
marketing.
Is
that
chennai
and
a
lot
of
other
developers
don't
consider
themselves
marketers,
but
I
think,
and
we're
just
told,
really
obvious
things
like.
Oh,
you
should
put
a
description
in
your
youtube.
Videos
like
it
seems
kind
of
like
a
no-brainer
that
it
shouldn't
take
a
whole
lot
more
work,
hey
something
else.
That's
really
exciting!
Publicity
wise!
B
You
guys,
will
hear
it
here
first,
because
we're
kind
of
keeping
the
wraps
on
it's
on
the
Twitter
until
it
actually
is
available
for
sale.
But
the
first-ever
backdrop
book
is
off
to
the
presses
and
will
be
available
next
week,
which
is
really
exciting.
It's
a
book
from
a
press.
It's
the
same
author
and
publisher,
I
should
add
of
pro
drupal
developer
or
pro
jable
development,
so
Todd
Tolleson
he's
been
working
in
the
background
to
make
a
series
actually
of
backdrop
books
and
he's
released.
B
His
first
one
are
sent
to
the
printers
it's
titled,
the
migrating
from
Drupal
to
backdrop,
which
is
which
is
awesome
because
that's
that's
our
target
audience,
but
it's
also
a
little
bit.
Yeah
I,
guess
a
little
bit
telling
that
that's
our
first
ever
book,
but
he's
working
on
a
second
book
he's
informed
me
called
a
beginning
backdrop,
which
would
be
like
a
an
introduction
to
backdrop
from
a
complete
newbies
point
of
view,
but
I
think
the
first
book
being
a
hey
you're,
familiar
with
Drupal.
B
A
A
So
if
we
have
people
who
have
marketing
skills
and
don't
want
to
write
code
and
want
to
grab
tasks
all
of
this
stuff,
that
was
mentioned,
an
issue
1
21
or
whatever-
has
been
split
into
a
sub
issue
and
tagged
with
that
marketing
thing.
So
if
you
have
people
like
want
to
write
blog
posts
or
guest
blog
somewhere
else
or
update
all
our
videos
or
any
of
that
pay
attention
to
google
analytics
for
us,
these
are
all
good,
discreet
jobs
that
we
could
outsource
to
people
who
are
much
better
at
them.
A
B
B
A
We
like,
oh,
we
should
talk
about
marketing
stuff,
but
now
that
we
actually
have
active
things
that
we
should
follow
up
on
and
be
like
hey
if
we
launched
any
ads,
I,
don't
know
yeah,
you
know
it
might
be
good
to
like
get
an
actual
schedule
of
things
where
it's
like
starting
in
january
or
after
1.3
is
released.
This
is
the
stuff
we
should
focus
on
and
actually
do
it
yeah
easier.
B
B
B
A
There's
a
thought
too,
because
we
have
a
bunch
of
people
who
don't
know
what
to
do
with
a
poor
request
right,
because
we
came
from
this
world
of
Drupal
where
everybody
used
patches
and
there
is
like
a
dirty
little
secret
of
github.
Whereas
if
you
take
your
poll
request
and
put
patch
at
the
end
of
the
URL,
you
get
a
patch.
That's
how
I've
been
testing
things.
That's
how
I've
been
maintaining
my
client
projects
that
include
like
patched
whatever
problems,
but
I
think
you're
right.
A
I
think
if
we
put
if
we
have
an
issue
that
needs
testing,
if
we
put
a
link
to
a
patch
in
the
comment,
it's
much
more
likely
that
someone
will
test
it
and
then
once
they
test
it,
we
can
get
that.
I
reviewed
and
testify
community
status
too.
So
that
is
a
good
idea.
I
think
especially
yeah
I,
the
tags.
The
stuff
is
a
little
weird
like
it
should
be
the
poor
request
that
needs
review.
But
if
people
are
looking
in
the
issue
queue,
they
won't
see
the
poor
request
status.
A
So
then
it's
kind
of
hard
we've
got
to
maintain
both
of
them.
We
have
an
issue
in
our
github
automation
section
that,
should
we
make
sure
the
text
on
both
of
those
stay
in
sync,
but
nobody's
working
on
that.
So
it's
not
likely
to
happen
soon
so
yeah
as
if
you
want
to
add
tags
to
the
issue
that
match
the
tags
on
the
pull
request
and
put
a
link
in
the
issue
for
testing
to
a
patch
version
of
the
poor
request
that
might
get
Mona
activity
yeah.
B
B
B
Okay,
alright,
well
I
think
we
should
wrap
it
up
because
we're
definitely
searching
over
an
hour
now.
So
thank
you,
everybody
for
joining
figure,
everybody
for
watching.
We
really
appreciate
the
constant
help
and
support,
and
it's
been
a
great
couple
of
weeks
for
backdrop
and
we're
hoping
for
more
great
weeks
in
the
near
future.
So
let's
get
ready
for
a
factor
of
1.3
and
make
some
progress
in
all
those
issues.
So,
okay
things,
everybody
goodbye,
hi,
everyone.