►
From YouTube: Backdrop Weekly 12/5
Description
Backdrop Weekly 12/5
A
Alright
and
we're
broadcasting
live
and
I
did
want
to
quickly
say
that
our
broadcasts
have
been
really
successful,
even
though
we
haven't
had
very
many
people
on
our
hangouts
recently,
we've
got
a
lot
of
people
watching
the
videos
afterwards
and
contacting
us
and
and
getting
involved
with
the
project,
so
I
think
that's
really
great,
like
that,
a
bunch
of
interest
in
it,
which
is
great.
Hopefully
it
means
we'll
get
a
lot
of
action
as
well,
and
so
it
looks
like
today
we
have
myself
on
the
college
n
Lampton
in
Nate
hug.
A
We
are
backdrops
founding
workers.
We
also
have
michelle
who's,
been
doing
a
lot
of
work
on
and
the
difference
between
all
of
the
get
commits
that
have
been
made
to
Drupal,
8
and
all
the
stuff
that
we
need
to
do
in
backdrop.
We
have
Victor
who
last
week,
join
us
and
expressed
interest
in
working
on
both
cmi
and
the
blocks
and
layouts
movement
that
we
would
maybe
like
to
focus
on
after
we
get
cmi
going,
which
is
great
and
it's
like.
We
also
have
Andy
I'm,
not
sure
you're
actually
plotting
anything.
A
A
A
matt
has
also
been
dropping
in
and
out
loud
I
think
he
did
two
weeks
ago
to
he
had
some
issues
with
his
internet
connection
as
well,
but
he's
also
been
working
on
the
the
views
and
core
stuff
recently
too.
So
if
he
jumps
in
whoa,
we'll
have
him
on
hand
as
well
she's
good.
Today's
agenda
is
roughly
similar
to
last
week's,
but
since
I
know
last
week
was
thanksgiving
and
a
lot
of
people
weren't
here.
A
What
kind
of
just
recap
in
brief
of
what
we're
working
on
before
we
get
into
the
details,
I
did
want
to
talk
really
quickly
again
about
what
our
goals
are
with
backdrop
and
will
probably
drop
this
from
our
meeting
fairly
soon,
just
because
people
are
probably
tired
of
hearing
me
say
over
and
over
again,
but
the
point
of
backdrop
is
to
make
a
Drupal
8
equivalent
system
or
what
we're
calling
triple-a
comparable,
but
does
lee
don't
think
we'll
be
able
to
get
it
exactly
the
same
on
a
framework
in
api
structure
that
looks
a
lot
more
like
drupal
7,
so
drupal
7,
a
very
large
user
basis.
A
We
all
are
aware-
and
it's
been
relatively
successful
based
on
the
code
that
it
has,
and
so
we'd
like
to
do
is
keep
things
the
same,
because
we
know
that
there's
the
cost
that
comes
with
change
upgrades
are
expensive.
It's
hard
on
the
developer
community,
it's
hard
on
the
client
sites
that
are
running
it
and
our
focus
is
to
be
and
to
keeping
keeping
things
more
similar
to
what
we
already
know
and
just
adding
new
features
to
a
code
base
that
we
think
is
already
pretty
good.
A
So
we're
going
to
be
fixing
bugs,
obviously,
as
they
come
up,
we're
going
to
be
adding
new
features
where
we
feel
like
there
isn't
going
to
be
too
much
API
change
and
we're
going
to
be
simplifying
existing
systems
again,
where
we
feel
like
there
isn't
going
to
be
chin
too
much
API
change
in
order
to
achieve
those
goals,
our
timeline
we're
going
to
aim
to
have
backdrop
one
released
just
before
Drupal
8,
the
sooner
we
can
get
it
done
the
better.
A
We
need
to
kind
of
look
it
up
at
the
commit
list
and
say
you
know,
is
the
bug
fix?
Yes,
we
need
it.
Is
it
a
new
feature?
Maybe
we
need
it?
Is
it
a
conversion
from
one
system
to
another?
We
definitely
don't
need
it.
So
just
trying
to
go
through
that
list
of
all
the
stuff
that's
going
on
and
making
sure
that
you
know
we're
not
behind
Drupal
8
in
terms
of
bug,
fixes
or
anything
like
that,
and
we
have
a
couple
of
major
projects
that
we
want
to
work
on.
A
Cmi
or
the
config
management
initiative
is
what
will
let
us
save
our
configuration
in
code
instead
of
in
the
database,
which
is
going
to
be
huge
for
anyone
using
Drupal
8
and
it
would
hurt
be
hard
to
have
a
Drupal
similar
product
without
having
anything
like
cmi
for
our
users
to
work
with.
So
that's
a
huge
thing
that
we're
working
on
I
know:
Nate's
been
charging
away
on
the
inclusion
of
CM
I
and
our
version
of
backdrop
and
I
know
he's
made
a
lot
of
really
great
progress.
A
B
So
we've
made
a
huge
amount
of
progress.
It's
it's
really
encouraging
to
see
where
we
are
currently
in
the
current
cmi
issue.
It's
it's
issue
number
two
in
the
tracker
signifying
how
important
it
is.
If
you
look
at
issue
number
two
there's
a
new
poll
request,
but
I
filed
just
yesterday,
maybe
day
before
yesterday,
that
gets
all
of
tests
passing
for
the
initial
see
my
patch,
and
it
makes
a
lot
of
significant
progress.
It
converts
one
settings
form
the
system
performance
page
as
well
as
all
image
styles
to
use
the
new
cmi
system
and
I.
B
Think
I
mentioned
this
on
last
week's
call
ba
reiterate:
we
had
an
original
version
of
CM
I
that
we
had
that
was
able
to
be
merged
in
that
was
relatively
close
to
her
for
King
point,
but
as
other
people
suggested,
the
version
that
we
had
was
not
really
that
great
at
all.
So
the
new
version
of
CM
I,
that
is
in
that
pull
request
is,
for
the
most
part,
a
complete
backport,
maybe
not
complete,
but
but
a
back
port
of
identical
Drupal
8
functionality.
So
a
lot
of
the
api's
are
identical.
B
The
way
it
works
is
really
pretty
close.
There
is
some
differences
like
we're
still
using
hooks,
of
course,
instead
of
using
like
event,
listeners
and
there's
a
lot
less
refactoring
necessary
to
use
our
version
of
CM
I
than
the
my
triple
eight
ultimately
proceed.
So,
but
it
looks
really
good.
I
think
at
this
point
we
should
look
at
reviewing
the
code.
All
the
tests
are
passing,
as
I
said,
there's
new
tests
that
actually
test
same
lies
functionality
and
the
UI's,
and
things
like
that.
B
We
should
focus
on
on
reviewing
that
code
and
getting
that
in
as
soon
as
possible,
even
as
a
baseline,
we're
much
much
further
than
where
drupal
8
introduced
their
baseline
for
SI
mi,
because
we
were
able
to
skip
several
iterations
and
just
go
kind
of
straight
to
the
finish.
What
what
Drupal
8
accomplished.
So
we
should
polish
that
up
it
and
put
that
in
and
then
star
going
through
individual
things
and
start
converting
them.
B
We've
already
got
image
styles
in
the
system
performance
page,
but
we
can
go
to
and
convert
all
of
the
configuration
forms
things
like
content
types
menus
all
of
those
things.
We
need
to
start
converting
those
individually
as
well,
so
we've
got
a
really
good,
baseline
and
I
think
that
we
should
work
on
on
moving
it
in
and
then
and
then
start
going
through
and
doing.
Math
conversions,
great.
A
A
What
we
need
is
a
meta
issue
that
contains
all
of
the
conversions
of
all
of
the
sub
components
and
then,
if
you
wanted
to
kind
of
manage
wrangling
a
team
around
you
to
help
get
all
those
conversions
done,
that
would
be
great
because
then
we
can
kind
of
leave
Leave
cmi
in
your
capable
hands,
and
let
me
focus
on
some
of
that
other
stuff
that
we
need
to
get
done
as
well.
Yes,.
D
One
thing
I
do
kind
of
want
is
I
know
we
don't
have
the
resources
in
terms
of
time
to
do
a
pair
programming,
but
I
would
like
to
have
some
time
with
Nate
just
to
get
more
into
everything.
For
example,
I
was
I
had
originally
formed.
Your
fork
of
backdrop
Nate
and
I
was
able
to
refresh
I,
was
able
to
fetch
from
upstream
and
then
merge
that
in
perfectly
well
with
my
own
Fork,
but
but
I'm
having
some
errors
today
trying
to
do
the
same
thing
since
the
last
change.
B
D
I'll
do
I'll
do
a
new
fork
of
yours
and
then
work
from
there.
Okay,
oh,
oh
good,
and
then
I'm
good
they're
not
being
in
a
position
to
and
did
run
some
basic
testing
of
it
and
it
it
seems
to
work
in
the
in
the
you
know
in
the
main
functionality
it
has
right.
So
I
would
just
like
to
get
deeper
into
the
code
and
where
to
start
stuff
like
that,
so
just
want
to
sort
of
touch
base
with
you
in
an
agile
way.
A
I
think
it
would
be
good
for
for
you
guys
to
meet
after
this
meeting
on
IRC
and
kind
of
figure
out
a
game
plan
for
moving
forward
from
here.
And
then
you
do
have
some
time
this
afternoon.
Pictured
it
to
kind
of
work
with
you
and
get
you
up
to
a
point
where
you're
comfortable
and
anyone
else
to.
If
there's,
if
you've
got
questions,
but
anything
we're
working
on,
join
us
in
IRC
and
and
we'll
try
and
figure
out
how
to
great
no
very
life
away.
D
A
You
so
much,
and
so
the
next
issue,
that's
kind
of
pressing
forces
is
fusing
core,
and
this
is
something
that
Matt
offered
to
start
working
on
last
week
and
I
know
he
started
making
a
bunch
of
progress
on
it.
He's
not
here
today
to
give
us
an
update,
I,
don't
know
Nate
if
you
know
any
more
about
how
that's
been
going
or
if
we
should.
Maybe
hang
him
on
IRC
later
and
get
a
different
update,
yeah.
B
So
the
views
and,
in
course,
stuff
Matt-
we
were
discussing
in
the
issue
about
autoloaders
about
how
to
approach
a
plug-in
system.
Matt
feels
that
a
plugin
system
is
necessary
or
had
thought
the
play
systems
or
are
up
plug-in
system
is
going
to
be
necessary
to
do
the
port
of
views.
But
it's
not
really
a
plug-in
system
that
he's
wanting
so
much
as
a
way
of
short
cutting
some
kind
of
naming
convention
around
like
what
the
file
is
called
contains.
This
plug-in
and
so
therefore
is
executed.
B
I,
don't
know
what
would
I
don't
think
that
that
it's
really
necessary,
but
we're
still
discussing
it
in
the
issue
about
how
to
go
about
that
so
I,
don't
know.
He
says
he
says
it's
it's
held
up,
but
I'm,
hoping
that
we
can
push
forward
with
without
really
addressing
that
I
think.
Actually
it's
it's
more
conversion
which
to
introduce
a
plug-in
system,
because
views
itself
doesn't
use
a
plug-in
system
for
all
of
its
own
handlers
and
filters,
and
things
like
that.
B
So
if
we
stick
with
hook,
views
info
I
think
that
that
we're
going
to
be
okay,
so
I,
don't
know.
We
need
to
work
that
out
with
Matt
about
the
approach
that
he
wants
to
take.
Okay,.
A
That's
great
and
blocks
and
layouts
we
obviously
haven't
made
any
progress
on
it's
something
that
we
would
really
like
to
do,
but
it's
obviously
less
pressing
than
cmi
views,
so
we'll
just
hold
off
on
that
for
a
little
while
we've
got
a
bunch
of
other
stuff.
Actually
do
you
think
nate
is
worth
removing
that
from
the
agenda
until
we
start
working
on
it,
yeah.
B
I'm
not
sure
I'm,
it
depends
on
how
effective
we
can
be
at
launching
cmi
I.
Think
once
we
get
a
couple
more
conversions
in
like
those
batch.
Those
conversions
should
be
pretty
easy
to
just
start
rolling
through
through
all
of
them
individually,
and
it
probably
wouldn't
require
my
focus
and
so
I'd
like
to
put
layouts
right
up
next
on
the
list
for
Miller,
so
I'm
hoping,
maybe
I,
can
lay
out
the
foundation
of
layouts
and
then
maybe
we
can
get
somebody
else.
B
A
It
sounds
great
all
right,
so
no
updates
on
that
yet,
but
hopefully
soon
and
then
the
other
issue,
which
is
my
thing,
the
theme
system
clean
up
something
I,
would
really
like
to
focus
on
finding
a
way
to
take
a
lot
of
the
improvements.
So
we've
made
to
the
Tripoli
theme
system
and
get
them
into
backdrop.
Obviously
we're
not
going
to
be
converting
to
twig,
but
I
still
think
there's
a
lot
of
work.
A
We
can
do
and
I
haven't
been
working
on
that
yet,
but
hopefully
I
will
get
a
little
bit
more
time
here
in
that
next
week,
our
table,
so
after
last
week's
meeting
I
did
go
and
update
our
manifesto
page
and
I.
Think
Nate
also
updated
our
handbook
to
include
information
about
these
weekly
meetings.
So
if
anyone
comes
to
our
website
and
wants
more
information
about
how
to
get
involved,
that's
a
little
bit
more
up
to
date.
We
also
set
up
a
backdrop:
CMS
paypal
donation
system.
A
So
if
anyone
wants
to
give
us
money
they
now
can
we
had
a
couple
of
people
who
contacted
us
after
our
indiegogo
campaign
ended
and
wanted
to
give
us
money.
We
did
anyway,
to
take
it
so
we've
solved
that
problem
and
there's
a
paypal
donation
form
on
our
manifesto
page
also.
So
if
we
wanted
to
get
someone
help
us
paper
so
cursed
or
something
we
can
handle
it
just
go,
we
do
still
need
work
on
the
backdrop
CMS
org
primary
website.
This
is
a
you
know.
A
Manifesto
was
good
for
a
little
while,
but
would
be
nice
to
have
something
more
official
up
there.
We
put
out
a
call
last
week
for
someone
who
wanted
to
work
on
content,
and
it
sounds
like
me:
you
got
contacted
by
someone
who
is
interested
in
doing
that,
which
is
good
yeah.
B
We
took
it,
we
got
an
email
from
Michael
Johnstone
if
you're
watching
this.
This
video
hey,
thank
you
for
for
the
offer.
He
seems
like
he's
mostly
interested
in
content
and
copy,
which
is
great
that
we
can
put
him
on
on
actually
creating
some
some
content
for
the
site,
but
we
still
need
like
we
don't
have
a
site
at
all.
A
So
we
also
need
a
kind
of
a
game
plan,
though
I
mean
setting
up
a
Drupal
site
is
fine,
but
knowing
where
we're
going
with
it
was
good
and
it
sounds
like
that's
what
he
was
interested
in
doing
too.
So
that's
great.
We
do
have
a
volunteer
for
design.
We
haven't
gotten
started
on
that
I,
don't
know
if
Nate
you
think
it's
worth
reaching
out
to
Darius
now
just
start
working
on
design
stuff,
or
should
we
wait
until
we
formulate
some
kind
of
plan
for
the
website?
First,
yeah
I.
B
C
B
A
So
we
should
work
on
that
first,
hopefully
with
our
content
person
and
figure
out
what
the
heck
we're
doing
and
then
we'll
get
Darius
on
board
after
that
there's
a
couple
of
other
things
that
we
should
probably
get
going.
A
But
in
order
to
do
that,
we
need
someone
to
just
fork,
github
repository
management
tool
and
create
a
surface
for
it
called
a
backdrop
project
or
something
like
that.
So
if
anyone
is
interested
in
working
directly
with
github
code,
we
need
someone
to
volunteer
their
time
for
that
as
well,
and
we
asked
them
someone
to
work
on
the
API
site.
I.
Think
two
weeks
ago
we
might
have
had
a
volunteer
Oliver
who
was
interested
in
working
on
the
API
site.
A
He
said
he
wanted
to
help
a
little
bit,
but
didn't
want
to
do
everything
I
eat,
something
that
was
compartmentalized
and
he
thought
the
API
site
might
have
been
a
good
starting
point
for
him.
So
we
should
reach
out
and
see
if
he's
still
interested
and
working
on
that
as
well.
But
we
don't
have
any
official
leads
for
any
of
that
stuff.
Yeah.
B
B
A
A
D
A
A
I,
probably
what
we'll
do
is
we'll
need
to
figure
out,
like
you
know
what
the
cost
would
be
in
terms
of
paying
for
the
thing
versus
taking
the
time
to
move
stuff
later,
it
might
be
cheaper
to
be
like
if
it
only
cost
us
twenty
dollars
to
have
it
for
a
month.
We
don't
need
it,
and
it's
going
to
take
us
more
than
half
an
hour
to
move
it
from
one
place
to
another.
It
might
just
be
worth
things
for
my
dollars
for
the
host
like
it
was
Leslie
deployment.
A
A
For
this,
that's
great
next
on
the
agenda
is
sprint,
so
today's
Thursday,
so
after
this
meeting
we're
supposed
to
be
doing
work
on
backdrop,
so
if
anyone
has
any
time
to
contribute
today,
I
know
Victor
and
Nate
will
be
meeting
on
IRC
I'm
gonna
be
lingering
in
there
too
Michelle.
If
you
have
any
questions
on
the
work
that
you've
been
doing,
will
be
in
there
to
help
address
those
and
anyone
else
who
joins
in
maybe
just
after
this
meeting
is
over
and
wants
to
still
talk
to
us.
A
You
can
find
us
in
IRC
to
our
IRC
channel
is
a
pound
backdrop,
and
then
I
mean
I.
Just
did
want
to
mention
again
funding.
If
anyone
wants
to
give
us
money,
there
is
a
paypal
donation
button.
Now,
on
our
manifesto
page
at
backdrop,
CMS
org
does
anyone
who's
on
this
call
right
now
have
any
questions
for
us
or
want
to
add
anything
else
to
the
weekly
agenda.
B
So
something
that
we
should
mention
right
now
is
that
we
are
guess
we
lost
over
this,
the
the
list
of
all
of
the
back
ports
that
we're
planning
on
doing
Michelle
compiled
those
amazing
lists
of
all
of
the
Drupal
7
issues
since
backyard
has
been
forked
and
started
compiling
the
Drupal
8
list
as
well.
Both
this
there's
three
four
issues
now,
because
there's
the
Drupal.
C
B
Another
another
one
for
the
area,
and
so
the
Drupal
7
ones
are
split
up
across
three
issues,
because
I
think
that
the
github
doesn't
allow
posts
there
that
long,
okay,
exactly
too
long,
yeah
too
many
yeah.
So
anyone
that's
interested
in
working
on
doing
some
backports.
We
have
an
enormous
list
of
things
that
are
all
really
pretty
trivial
to
do,
because
it's
just
look
at
the
Drupal
7
patch
applied
to
backdrop,
make
any
necessary
adjustments
which
should
be
pretty
minimal
at
this
point
and
then
file
a
pull
request.
B
What
we're
hoping
to
do
is
make
an
issue
for
every
individual
one,
so
that
giant
the
giant
meta
issues
that
Michelle
compiled
are
for
reference.
Basically,
so
for
every
individual
issue,
we
need
to
every
individual
patch
that
went
into
Drupal
7.
We
need
to
make
an
issue
and
then
file
a
pull
request
against
that
issue,
and
then
that
meta
issue
is
just
for
reference
so
and
the.
C
Drupal
8
list
I've
done
some
winnowing,
like
I've
tooken,
at
taken
out
everything
you
had
to
do
with
converting
stuff
to
PS
or
0
and
anything
had
symphony,
and
but
there
may
be
some
things
in
there
that
slipped
in
that
are
not
relevant.
So
that's
the
harder
list.
The
Drupal
7
list
is
obviously
much
more
straightforward.
Okay,.
A
I'm,
just
gonna
add
those
links
into
our
agenda
too.
So
if
anyone
grabs
this
they'll
be
able
to
get
working
on
this
wow,
this
is
a
lot
of
issues.
Thank
you.
So
much
Michelle
is
a
lot
of
work.
Oh.
B
That
you
can
tackle
what
we're
trying
to
do
with
issues
is
is
in
those
meta
issues
is
after
you
tackle
one
you
edit
the
issue
and
then
mark
it
closed
or
link
to
the
NIT
link
to
the
relevant
issue
or
whatever.
But
I
said
about
that.
Oh
you
can
only
edit
the
issues
or
label
issues
if
you've
been
marked
as
part
of
the
documentation
and
organization
team,
and
we
have
a
job
set
up
right
now
that
if
you
file
a
pull
request,
you
automatically
get
added
to
that
team.
B
C
D
D
Thing
github
does
have
the
task
lists.
Has
anybody
seen
that
at
what
you
do,
is
you
it
within
one
task?
You
can
have
a
lot
of
little
tasks,
which
appear
as
little
checkbox
is
when
they're
minor
it's
very
convenient,
so
you
don't
always
have
to
make
a
meta
task
and
and
the
reference
tasks
it's
covered.
D
C
D
B
American
yeah
might
actually
work.
I
didn't
use
that
on
the
initial
one,
because
I
put
it
into
a
table
and
apparently
you
can't
combine
tasks,
list,
task,
lists
and
tables
at
the
same
time,
but
Michelle
Michelle's
issues
aren't
tables
to
begin
with,
so
I
mean
we
might
as
well
make
checkboxes
to
indicate
like
maybe
well
I,
don't
know,
I,
don't
know,
I
mean
we
already
need.
We
already
need
to
reference
the
individual
issues
and
it's
not
just
done
or
not.
It's
open
closed
or
in
progress.
So
yeah.
C
And
also
one
thing
I
did
was
that
there's
two
links
in
each
line.
One
link
is
the
wine
to
the
Drupal
commit
on
Drupal,
comfortable
code
downloads,
and
the
other
line
is
a
is
actually
a
link
to
the
issue
itself
on
drupal.org.
So
there's
two
links,
so
that's
also
hard
to
deal
with
in
terms
of
yeah,
it's
kind
of
a
table
for
that,
because
there's
those
two
different
links
so
yeah,
okay,.
A
A
Okay?
Well,
then,
I
think
we
should
probably
stop
the
broadcast
and
end
the
meeting.
It's
a
just
130
right
now
and
then,
if
anyone
else
has
anything,
you
want
to
add
or
talk
to
us
about,
offline
will
be
in
IRC
or
you
can
pay
me
or
Nate
Derrek
Lee,
however,
and
thank
you
all
for
coming.
Thank
you
all
for
helping
a
spectra.
Yeah.