►
From YouTube: Backdrop Weekly 12/19
Description
Backdrop CMS, a Drupal fork
A
Oh,
that
was
much
faster,
this
time,
Google's
improving,
okay,
so
we're
now
broadcasting
and
I
guess
we'll
start
off
the
meeting
with
a
little
introduction.
Nate
and
I
are
obviously
here
we're.
Usually
here
we
Thursday,
we've
got
Andy
with
us
today.
I
know,
there's
a
bunch
of
other
people
in
IRC
and
a
ton
of
people
looking
at
the
google
doc,
I'm,
not
sure
if
anyone's
gonna
join
or
not
I
know,
as
we
had
closer
and
closer
into
the
holidays,
it'll
be
less
and
less
likely
that
we'll
have
people
with
us
on
the
call.
A
A
So
that
means
we
want
to
have
almost
all
the
same
features
is
Drupal
8,
but
we
want
to
use
the
system
that
all
they
sting,
Drupal
developers
know
and
presumably
love
some
of
us
hate
it,
but
we
obviously
are
working
with
Drupal
and
have
really
successful
sites
launched
on
Drupal,
and
so
it
can't
be
that
bad
until
we
want
to
stick
with
what
people
know,
because
learning
new
things
has
a
cost
and
we're
gonna
fix
all
the
bugs
we
can.
Those
are
all
the
ones
that
have
already
been
fixed
in
recent
versions
of
Drupal
7.
A
All
of
the
ones
have
been
fixed
in
newer
versions
of
Drupal
8
and
any
new
bug
fixes
that
that
we
can
fix
that
people
bring
to
our
attention
on
our
own
system
and
hopefully
we'll
work
to
get
those
bug
fixes
at
least
acknowledged
in
Drupal,
so
chic
use,
if
not
also
solved
over
there.
Ideally
we'll
be
able
to
simplify
existing
system,
so
things
in
Drupal
7
that
people
found
harder
confusing.
A
A
So,
if
you
come
to
req,
you
can
find
these
men
issues
and
help
with
us
as
well.
I
know
I'm
Andy
you've
been
doing
a
lot
of
work
on
getting
all
of
our
Drupal
7
stuff,
sorted
out,
which
is
great.
We
have
a
huge
pull
request
with
a
bunch
of
stuff
getting
all
results.
So
it's
wonderful.
Thank
you
for
all
of
your
awesome
or
comment,
and
hopefully
more
in
that
pain
will
be
coming.
Yeah
I
need.
Oh
sorry,
Nate
yeah.
B
I
was
gonna,
I
was
going
to
inject
that
all
of
Andy's
pull
requests
have
already
all
been
merged
in
so
everything
that
that
we've
got
from
Andy.
Thank
you
very
much.
It's
all.
It's
all
in
I,
think
you
got
I,
think
I
counted
them
up,
35,
pull
requests
and
and
or
35
commits
and
a
spread
across
three
pull
requests.
B
That's
absolutely
perfect,
like
I
love,
yeah,
the
approach
of
just
filing
a
pull
request
directly
and
just
including,
as
many
commits
as
you
can,
is
absolutely
perfect,
like
the
minimal
amount
of
work
for
the
maximum
amount
of
ketchup,
so
so
great
job
there.
If
you
do
have
any
updates
and
beyond
progress
or
anything
that
you're
working
on
in
that
area,.
C
No
I
will
be
after
Christmas.
Now
it's
pretty
much
last
week
been
woken
Christmas
parties
and
that
kind
of
stuff.
So
all
that
stuff
is
so
I
things
out
of
the
way
and
all
that
stuffs
out
of
the
way
now,
so
you
know
what
finish
up
work
this
week
and
then
hopefully
get
into
it
next
week
then
come
again
cool.
B
A
B
B
You
know
moving
from
a
previous
major
version
to
the
next
major
version
to
be
you
know,
I
mean
an
undertaking,
but
not
like
a
serious
reinvestment
of
the
entire.
You
know,
sites
cost
so
so
I'm
really
happy
to
see
that
that
update
dot,
PHP
I
think
it's
going
to
work
fine
for
us,
because
we're
not
really
changing
that
much
anyway
anyway.
So
the
upgrade
path
work.
Now,
that's
what
I
was
getting
at
for
image
styles.
B
B
So
I
posted
on
monday
to
the
issue,
then
it
looks
anybody
has
any
last
like
holdups
or
any
any
real
serious
concerns
that
should
prevent
the
initial
branch
from
being
merged
that
we're
going
to
merge
it
today
during
our
code
sprint
after
this
call
so
yay
so
SI
mi
yeah,
and
then
I
can
talk
a
little
bit
more
about
that.
Once
we
get
done,
I
mean.
B
Maybe
I
should
just
go
right
into
the
next
item
on
the
agenda,
which
is
using
Core
yeah
so
with
CM
I,
largely
like
the
basics
of
it
all
all
taken
care
of
and
being
ready
for
the
past
couple
of
weeks,
I
shifted
my
attention
to
probably
that
the
next
most
important
thing,
which
is
using
core
and
I,
started
pouring
that
over
last
weekend
and
I
had
a
huge
amount
of
success.
Porting
views
I
decoupled.
All
of
C
tools
for
the
time
being
in
some
places,
I
use
some
temporary
systems
like
a
sea
tools.
B
Temporary
object
store.
We
need
a
base
system
backed
up
to
handle
all
of
that
in
Drupal
8.
They
have
a
key
value,
temporary
or
key
value
expire
store,
or
something
like
that
that
we
may
want
to
backport
something
similar
to
that,
but
for
the
time
being,
I've
restored
views
just
providing
its
own
temporary
data
store.
Until
that
underlying
system
is
in
place,
follow-up.
B
The
datastore,
so
we
don't
forget
to
do
that
later,
I
did
I
did
so
that
there's
an
issue
for
that
and
then
and
then
I
went
about
porting,
all
of
all
of
use,
as
best
I
could,
and
it's
it's
been
going
great
like
we
needed
a
couple
primary
systems,
we
needed
things
like
a
merging
in
various
pieces
of
C
tools,
so
views
can
stand
alone.
We
needed
drop
buttons
which
have
ben
backported
with
great
success
again,
just
taking
the
Drupal
8
code,
migrating
it
back
to
the
previous
system
and
then
implementing
it.
B
It
all
works
looks
great
actually
in
the
case
of
drop
buttons.
There's
nothing
new
about
the
way
form,
API
elements
work,
so
that
was
literally
was
a
straight
back
port
and
then
so,
let's
see
this
key
value,
store,
drop
buttons.
The
dependency
system
again
that
one
actually
again,
an
exact
straight
back
port
I
found
the
original
issues
that
converted
those
into
into
using
the
state
system,
pound
states
instead
pound
dependency
and
that
patch
applied
almost
flawlessly
to
backdrop
with
a
couple
of
modifications,
for
you
know,
modules
that
we've
removed
and
things
like
that.
B
So
those
three
things
are
the
primary
requirements
that
we
were
using
out
of:
CTools
drop
buttons,
the
dependency
system
and
a
temporary
object
store,
so
temporary
object
store
is
the
one
that
needs
a
follow-up
issue,
but
we
could
actually
do
that
after
we
finish
with
views
and
then
then
swap
it
out
for
a
generic
system
which
actually
would
be
better
because
then
we'd
have
a
use
case
for
the
system
and
we
wouldn't
have
it
built
up
this.
The
views
branch
is
built
on
top
of
CM,
the
cmi
branch.
So
that's
why
we
want
emergency.
B
After
this,
like
the
main
thing
that
is
left
with
views,
there
are
a
couple
of
see
tools,
things
like
mathematical
expressions
and
one
other
CTools
plugin
that
isn't
converted.
Yet
we
can
convert
those
to
some
base
system
in
in
core
or
we
can
leave
them
to
a
follow
up.
But
then,
after
that,
we'll
probably
need
to
back
toward
a
couple
of
other
changes
like
the
views.
Bulk
operations
that
are
in
Drupal
8
we'll
need
some
equivalent
of
that.
B
The
entire
structure
is
still
almost
identical.
That
I
think
I.
Think
upgrading
should
be
relatively
easy
as
long
as
we
continue
on
this
sort
of
direct
conversion-
that's
great,
so
oh
yeah,
regarding
other
other
people,
working
on
that
Matt
2000
still
really
interested
in
helping
with
views,
but
like
many
other
people,
we
are
headed
like
totally
right
into
the
holiday
season.
B
A
Great,
that's
really
exciting,
with
Christ
am
I
almost
done
and
views
completely
under
way.
I
feel
like
both
of
those
things
are
great
huge
chunks
of
work
that,
as
soon
as
we
get
done,
will
enable
a
whole
bunch
of
other
people
to
come
on
and
do
a
bunch
of
little
conversions
like
converting.
You
know,
fields
to
store
and
see
mi
or
converting
these
that
are
should
be
views
important
of
using
course.
So
this
is
great.
A
It's
going
to
unblock
a
lot
of
people
who
maybe
didn't
have
a
huge
amount
of
time
to
contribute,
but
wanted
to
do
a
little
bit.
So
that's!
This
is
huge
for
us
yeah
next
on
the
list
is
blocks
and
layouts,
which
of
course,
is
a
you
know
something
we
really
want
to
get
done,
but
will
come
after
fuse
and
see.
Empire
are
well
underway
and
then
under
minor
projects
and
there's
the
theme
system
cleanup,
which
I
started
a
spreadsheet
for
but
I
figured.
A
A
That
you
know
has
already
been
consolidated,
so
those
are
just
copies
of
issues
from
Drupal
I
think
that
would
be
fine,
but
there's
a
bunch
of
other
stuff
that
we're
going
to
need
to
solve
differently.
Obviously,
because
we're
not
using
twig
that
we
should
think
about
how
that's
going
to
affect
us
versus
trying
to
figure
out.
A
What's
going
on
in
Tripoli,
so
I
think
I'm
a
little
more
strategy
on
that
before
we
start
working
on,
the
coach
is
going
to
be
important
and,
and
then
I
added
another
item
here
for
easier
experience
of
improvements,
and
this
is
just
general
stuff,
like
cleaning
up
the
navigation
and
stuff
that
that
meet
you
and
I
have
been
talking
about
that
I
think
we
should
devote
a
specific
person
too.
So
if
we
have
someone
who's
really
interested
in
I
use
your
interfaces
or
making
Drupal
make
more
sense.
A
It's
probably
something
that
we
should
kind
of
create
a
big
category
floor,
I,
don't
think
it's
urgent
and
which
is
why
it's
just
kind
of
on
here
at
the
bottom
of
the
list.
But
it
is
something
that
I
think
could
kind
of
set
us
apart
from
Drupal
8.
Also,
if
we
can
come
up
with,
you
know
things
that
make
sense
for
us
sources,
things
that
make
sense
for
them,
but
it
doesn't
require
a
lot
of
thinking
and
probably
some
testing
before
we
make
any
changes.
B
Yeah
regarding
user
experience-
and
maybe
this
isn't
user
experience
so
much
as
it
is
user
interface,
I
mean
they
have
a
lot
of
overlap,
but
I
filed
an
issue
to
backport
all
of
the
changes.
27
Ryan's,
our
five
Lions
work
on
the
78
theme,
which
are
just
modernizations
of
the
17
I,
think
that
all
of
those
I
mean
they
look
great
then
they're
definitely
an
improvement
upon
the
existing
seven
appearance.
In
my
mind
at
least
I
filed
an
issue
to
say
you
know
we
should
just
back
port
all
of
those
changes.
B
Some
of
them
are
still
actually
in
progress
that
they
haven't
actually
completed
yet
like
new
tabs,
the
way
they
look
and
a
new
way
of
making
them
integrate
responsibly.
I
think
that
a
lot
of
that
work
is
great
and
my
plan
had
been
like
many
other
things.
You
know
drew
plates
doing
a
lot
of
really
great
stuff,
there's
just
some
fundamental
differences
that
we
that
we
have,
that
all
of
those
changes
I
feel
like
they're
completely
applicable
to
our
project,
but
yeah.
Anyone
interested
in
participating
in
that
discussion.
B
A
B
A
Have
a
question
around
timing
on
that
too,
and
we
have
a
lot
of
a
lot
of
ground
to
cover
not
a
lot
of
time,
but
if
we
haven't
met
issue,
that's
like
by
poured
everything
from
triple
eight
and
we
start
pulling
in
little
pieces
like
oh,
you
know
this
is
really
easy,
because
it's
just
CSS
changes-
or
this
is
really
because
it's
just
this
one
piece
over
here.
How
is
that
gonna
fit
in
with
our
massive
list
of
you
know
drupal
8
stuff
waiting
to
backport?
Does
it
matter?
What?
A
B
Think
it's
probably
not
not
well
documented,
which
we
can
resolve
that,
but
I
think
that
the
back
port
list
from
Drupal
7
that
should
be
our
baseline,
that
we
need
to
get
all
of
the
Drupal
7
backports
completes
and
then,
after
that,
like
the
order
in
which
we
implement
functionality
from
Drupal,
8
I.
Don't
think
I,
don't
think
that
we
can
enforce
an
order,
because
if
we,
if
we
say
that
they
have
to
be
done
chronologically,
then
we'll
create
our
own
bottleneck.
Yeah.
A
B
That
they
need
to
be
done
in
order.
So
I
think
that,
let's,
let's
just
focus
on
on
completing
the
Drupal
7
back
ports
and
after
we
get
the
Drupal
7
back
parts
done,
there's
a
couple
of
issues
that
are
kind
of
far
reaching
but
important
to
the
longevity
of
the
project
that
the
things
like
rename
Drupal
the
backdrop
everywhere.
You
know
like
that
is
really
important
for
us
as
a
project
to
have
an
identity.
But
it's
really
inconvenient
as
as
far
as
back
porting
patches
goes.
B
So,
let's
get
as
far
as
we
can
as
quickly
as
we
can
with
the
trivial
stuff,
which
let's
say
the
Drupal
7
backport
list.
Is
that
trivial
list
of
a
backports
because
we're
very
similar
to
Drupal
7.
But
then
the
Drupal
8
backports
I
mean
already
that
the
14
point
that
we
had
was
as
far
as
we
could
go
before.
Really
significant
differences
started
happening,
so
the
trivia
trivial
backports
from
Drupal
8
will
be
few
and
far
between
anyway.
B
So
so,
let's
say
Drupal
8
and
then
we'll
sorry,
Drupal,
7
backports,
then
we'll
convert
the
major
like
function.
Names
like
give
back
drop
its
own
identity
and
it's
in
its
code
base
with
the
backwards
compatibility
file,
there's
an
issue
for
a
view.
If
you
look
up
in
the
suq
rina
and
drupal
the
backdrop
you'll
find
you'll
find
it
but
we're
playing
on
a
backwards
compatibility
file.
Basically,
that
is
just
included
by
default
that
renames
that
wraps
around
all
the
drupal
functions.
B
So
in
theory,
you
could
do
porting
from
Drupal
7
2
backdrop
really
pretty
easily,
without
changing
too
many
functions,
just
like
avoiding
all
the
straight
rename
triple
the
backdrop
everywhere
but
long-term
like
we
need
to
give
this
project
its
own
identity,
and
so
we
can't
just
keep
using
Drupal
forever.
So
it
unfortunate
like
it's
a
I
mean
the
amount
of
required
change
is
minimal,
but
the
actual
lines
of
code
that
it
would
take.
In
a
legitimate
backdrop,
module
will
be
significant,
but
I
mean
okay,.
A
So
go
number
one
we're
going
to
work
on
back
boarding
stuff
from
Drupal
7
as
soon
as
we
get
all
the
Drupal
7
backports
done
we're
gonna,
rename
Drupal
to
backdrop
and
then,
after
that,
it's
kind
of
anything
goes
on
what
you
want
it
back
part
from
Drupal
8.
So
picking
and
choosing
specific
things
is
fine.
If
their
front
end
thinks
they're
really
easy
to
play,
that's
good!
We
should
just
do
as
much
as
we
can
if
they're
back
in
things
and
they're
really
hard.
A
A
All
right
so
other
things
we
need
work
on,
we've
got
people
who
are
interested
in
doing
content
for
the
backdrop,
CMS
storage
site
I
think
we
had
someone
who
was
interested
in
building
it
for
us
too,
as
of
last
week,
but
I,
don't
think
anyone's
actually
gotten
started.
I
know,
I've
got
two.
People
are
interested
in
working
on
design,
but
we
need
to
figure
out
what
we're
actually
going
to
do
before
we
let
them
loose
on
our
project
and
then
I.
Don't
think.
We've
had
any
progress
on
that.
A
A
But
it
would
be
fun
if
anyone
wants
to
you
and
we
also
need
official
github
service,
for
anyone
who
wants
to
create
modules
are
themes
on
github
so
that
we
can
officially
register
them
as
back
job
modules
and
themes
and
aggravate
them
on
our
own
site.
And
so,
if
anyone
wants
to
have
some
fun
working
on
github,
we
could
do
that.
A
B
A
And
then
Sprint's,
obviously
it's
thursday
so
backed
up
thursday.
If
anyone
wants
to
stick
around
after
the
meeting
today,
you
can
meet
us
an
IHC
and
I'm
gonna
work
for
an
spreadsheets
I,
don't
know
if
anyone
else
is
gonna
be
around
other.
Didn't
you
and
Andy,
but
I
think
Michelle.
It's
done
for
the
day.
I
don't
know.
Who
else
is
my
receipt,
but
yeah
we'll
definitely
be
there.
If.
A
B
Don't
I
don't
have
anything
new
to
add
I,
don't
think
I
mean
well.
Probably
this
week
will
be
for
me
a
focused
on
on
views
and
continuing
to
to
push
it
forward.
There
I
mean
it
works.
Right
now
is
like
you
can
create
views
and
save
them,
and
things
like
that,
but
some
pieces
are
missing
so
I'll
continue.