►
From YouTube: Backdrop Weekly 1/23
Description
Weekly Backdrop CMS status call.
A
We
get
together
every
week
to
talk
about
backdrop
and
to
check
in
on
status
and
see
how
how
we're
progressing
in
all
of
the
areas
that
we
have
to
move
forward.
Backdrop
CMS
towards
the
one
point
0
release
so
jen
is,
is
currently
unavailable
today,
so
she
is
not
hosting
the
call
so
I'll
be
I'll
be
taking
over.
We
usually
start
off
these
calls.
Thank
you
guys.
Everybody
who's
joined
the
call.
A
If
you
would
like
to
join
the
call,
we
have
it
every
week,
it's
public,
it's
a
it's
a
it's
a
google
hangout,
so
you
can
just
join
via
the
link
that
we
post
every
week
on
Twitter
or
via
IRC,
or
you
can
watch
this
after
the
fact
on
youtube
channel
under
backdrop
CMS.
So
thanks
everybody
for
watching
or
who
is
always
joining
the
call.
A
Let's
see
so
we
aren't
usually
start
off
with
an
overview
of
backdrops
goals.
Backdrop
is
aiming
to
be
a
continuation
of
Drupal
sevens.
Ap
is
so
if
you're
familiar
with
Drupal
7.
You
should
be
very
familiar
with
backdrop,
but
we're
aiming
towards
providing
all
of
the
new
functionality
or
most
of
the
functionality
in
Drupal
8,
on
a
Drupal
7,
like
architecture,
so
less
overall
change,
but
still
providing
the
features
and
functionality
that
people
really
want
out
of
the
next
version
of
Drupal.
A
So
right
now
we're
doing
a
bunch
of
work
and
catching
up
with
Drupal,
7
and
Drupal
8
in
terms
of
the
bug,
fixes
and
functionality
that
it
has
been
added
there
and
that's
where
most
of
our
our
goals
are
right
now.
So
in
the
future,
once
we
get
back
drop
one
point
0
out
after
that,
we're
going
to
be
looking
hard
into
simplifying
existing
systems
down
further
and
adding
additional
functionality
and
features
on
top
of
the
basic
factor
up
on
plano
release
our
timeline.
A
Overall,
we
had
been
saying
that
we
were
planning
on
releasing
around
the
same
time
as
drupal.
8
is
released
from
recent
updates
in
Drupal
8
lands,
though
we're
from
what
I've
seen
like
they're,
going
to
be
pushing
really
hard
to
even
get
a
release
out
this
year
in
2014.
So
our
goal
of
releasing
backdrop
at
the
same
time
miss
Triple
Eight.
A
We
might
need
to
move
up
our
our
time
estimates,
because
what
we're
hoping
for
is
a
release
sometime
this
summer,
so
maybe
not
the
same
time
is
Drupal
8,
but
probably
before
so,
let's
see
progress
reports
so
progress
reports
are.
We've
got
a
number
of
meta
issues
for
porting,
Drupal,
8
and
Drupal
7
patches
to
backdrop
to
make
sure
that
we
don't
miss
any
like
critical
bug,
fixes
or
or
various
features
that
have
been
added
to
Drupal
7
or
to
Drupal
8.
So,
let's
see
we
haven't
met
issue
for
Drupal
8.
A
That
Michelle
has
updated
recently
issue
106
and
she's
going
through
and
adding
all
of
the
various
issues
that
we
need
to
keep
up
with.
We
haven't
been
going
through
the
Drupal
8
list
yet
so
far,
we've
just
been
hitting
the
primary
issues
that
we
need
around
like
views
and
around
cmi
and
we're
doing
all
of
those
issues
a
la
carte,
but
anyone
who's
interested
in
going
through
the
Drupal
8
list
and
just
porting
one
patch.
At
a
time.
A
We
don't
have
anybody
looking
at
that
currently,
but
issue
106
is
is
kind
of
like
the
master
list
of
patches
that
reporting
back
porting
from
from
Drupal
8,
where
we're
doing
a
lot
more
work
right
now
is
making
sure
that
we
don't
miss
any
of
the
functionality
that
was
merged
into
Drupal
7,
and
we
have
three
met,
is
for
that
132,
134
and
135
and
I
know
this
past
week
at
least
Andy
and
Jen.
You
guys
did
a
bunch
of
work
on
the
meta
issue,
number
3,
s.u
135.
B
Jen
made
a
lot
of
progress
and
then
one
day
or
tuesday
I
made
it
up
to
the
very
top
of
the
list
d.
These
are
three
that
are
basically
one
issue,
but
they
are
divided
by
chronological
order.
135
is
the
oldest
up
to
132,
which
is
the
newest
rom,
so
the
they
so
the
yeah
135
of
there's
a
pull
request
made
by
me,
whether
this
week
and
they're
being
reviewed
by
nate
and
the
rest
of
them.
You
might
notice
that
it
is
not
all
222.
B
B
To
be
knock
off
the
list
because
they
do
not
apply
a
I,
can
think
of
several
that
we're
trying
to
apply
to
of
entity
Inc
file
and
apparently
that's
not
vague
drop,
so
yeah
like
some
of
the
easy
ones
like
you
know
like
for
module,
you
could
say:
yeah
I
definitely
see,
but
when
you
you
know,
when
you
start
going
through
it,
and
you
see
the
end
of
a
visual
files
that
you
may
have
used
in
Drupal
7
link
entity
dad
Inc,
then
you
will
find
more.
They
can
cross
off
the
list.
B
A
Speaking
of
that
entity
file,
I
think
what
happened
is
right
around
the
time
that
we
forked
entity
had
been
split
up
into
its
own
module,
so,
instead
of
being
part
of
field
module
and
empty
ink
and
I
in
the
core
/
includes
directory,
it
got
moved
into
its
own
file
but
or
into
its
own
module.
But
I
think
the
contents
of
that
file
are
still
identical.
It
just
lives
in
core
modules
entity.
Entity
Inc
instead
of
includes
entity
that
ink
so
I
just
got
moved
around,
but
yeah
all
right,
y'all.
B
Yep
so
I
guess
for
135
and
then
I
need
to
talk
about
what
to
do
with
the
remaining
catches.
For
that,
if
we
want
to
do
things
chronologically
and
then
we
need
to
move
to
you
know
then
there'd
be
basically
once
they
were
done,
then
we
would
just
move
to
the
next,
oh
so
forth
and
yeah.
That's
that's
just
a
timely
issue,
but
it's
something
that
we
can
kind
of
put
on
the
calendar
and
just
you
know
just
yeah.
A
B
A
We'll
just
get
to
the
one
one
item
at
a
time.
Do
you
have
any
idea,
let's
see
for
the
med
issue
number
three,
it
sounds
like.
Are
there
any
issues
remaining
there
besides
taxonomy
and
the
ones
that
you
have
a
pull
request
for?
Are
there
any
remaining
ones
there?
That's
our
that
are
easy
to
handle
still
emit.
Maybe.
A
B
B
A
A
A
A
That
actually
is
related
to
the
view
system
which
will
more
cover
next,
but
in
order
to
get
some
of
the
other
things
working,
we
also
had
to
introduce
the
state
system.
Drupal
8
has
this
concept
of
states
for
things
that
are
our
previously
used
variables,
but
should
not
actually
be
stored
in
the
config
management
system.
A
So
I
made
a
new
issue
or
I
updated
an
issue
issue
141
for
the
state
system
and
posted
another
poll
request
there
that's
ready
for
review
and
it
converts
six
initial
values,
the
most
common
six
state
values
into
the
state
system,
so
that
that's
needed
for
review.
But
it's
really
so
simple.
It's
basically
identical
to
the
variable
system.
A
So
so
we
have
that
available,
which
should
help
get
our
variable
conversions
underway,
there's
a
dozen
or
so
variables
that
will
be
converted
to
States
and
then
probably
doesn't
more
in
tests
and
tests
or
why
we
need
the
state
system
in
the
first
place
which
we'll
get
to
in
a
second,
so
views
in
core
views
in
core
has
been
going
really
well.
We've
already
got
views
the
base
system
involved.
We've
got
some
volunteers
who
are
starting
to
convert
various
listings.
There's
a
metal
list
of
all
of
the
conversions
that
are
happening
in
issue
151.
A
The
very
first
one
that's
going
to
be
converted
is
the
simple
listing
of
the
front
page,
the
list
of
nodes,
it
/
node.
We
have
a
volunteer
for
that
issue
and
that
is
underway,
but
then
all
of
the
administrative
listings,
in
order
to
replace
like
the
content
listing
or
the
user
listing
or
any
of
those
other
administrative
listings
with
views,
we
need
an
equivalent
to
view,
spoke
operations
and
views.
Bulk
operations
issue
is
issue
142
and
it's
progressing
really
pretty
well.
A
There's
a
pull
request
there
that
gets
view
spork
operation
like
the
the
field
handler
in
and
all
the
functionality
and
that
we
need,
but
it's
stuck
on
entity,
API
entity,
API
in
contraband.
The
views
bulk
operation
uses
entity,
API
module
to
do
things
like
delete
or
update
or
save
any
arbitrary
entity.
So
in
order
for
us
to
have
that
same
kind
of
functionality
and
backdrop,
we
need
to
improve
the
entity
system
so
that
it
can
behave
consistently
on
any
kind
of
entity.
A
Fortunately,
at
the
time
that
we
forked
backdrop,
we
already
had
comments
converted
to
the
new
entity
system
and
so
we're
going
to
run
converting
the
remaining
types
of
data
into
the
new
entity
system,
including
taxonomy
users,
nodes
and
files.
So,
right
now,
we've
got
poor
requests
for
both
taxonomy,
which
is
ready
to
go.
Actually,
it's
been
sitting
for
review
for
a
week
and
that
will
probably
get
merged
in
this
week
and
then
also
for
users.
A
The
pull
request
for
users
is
what
got
stuck
on
the
state
system,
so
the
state
system,
once
that
gets
merged
in
then
we'll
be
able
to
merge
in
the
pull
request
for
users.
As
well,
there's
just
an
issue
with
tests,
you
can
read
the
issue
if
you
want
to
follow
in
on
on
why
that's
actually
necessary.
So
the
the
entity
issue
for
users
is
155
and
that's
that's
ready
for
review
other
than
the
tests
failing
because
we
have
this
dependency
on
the
state
system.
A
I
know
it's
kind
of
like
we're
going
down
this
huge
rabbit
hole
which
is
not
too
surprising
that
you
think
you
think
you
just
need
to
convert.
You
know
views
or
views
bulk
operations
and
then
it's
like.
Oh,
we
also
need
to
convert
the
energy
system,
so
the
views
bulk
operations
can
use
it,
but
all
of
that
is
coming
along,
really
pretty
well.
I
think
we'll
be
able
to
get
all
of
those
things
in
in
the
next
couple
of
weeks
and
then
start
moving
things
to
tease
feasible
operations,
the
version
that
we
have
impact
romp.
A
A
Wysiwyg
incor,
the
dialogue
system,
better
toolbar
editorial
improvements
for
the
no
dad
form,
the
no
dad
for
most
likely,
no
dad
and
edit
for
most
likely
use
the
layout
system
once
that
gets
implemented,
an
administrative
theme
and
any
other
UI
improvements.
So
administrative
theme
there's
currently
an
issue
for
back
porting
Drupal
8
7,
implement
8
implementation.
They've
redesigned
a
lot
of
the
ways
that
that
the
7
theme
looks
in
Drupal
8
and,
after
speaking
with
our
designer
which
we'll
talk
about
in
a
second,
we
talked
with
our
designer
this
past
week.
A
Last
Thursday
we
went
out
and
had
a
meeting
with
him
and
he's
not
the
first
person
to
suggest
this
that,
instead
of
back
porting
triple
sevens,
administrative
theme
is
a
good
opportunity
for
us
to
pursue
a
different
visual
style
for
our
administrative
interface.
So
we
won't
look
like
drupal
sevens
admin
theme
and
we
won't
copy
everything
from
Drupal
8
either.
Instead
we'll
work
on
modernizing
our
administrative
theme,
but
not
by
taking
all
drew
plates
appearance.
A
Basically,
so
after
thinking
about
that,
I
think
that's
a
really
good
idea
on
his
part
that
we
should
start
working
on
identifying
ourselves
as
an
independent
software
project.
As
as
backdrop
in
the
administrative
interface,
rather
than
just
copying,
all
of
Drupal
8,
it
also
makes
for
less
tension.
You
know
that
way.
At
least
I
mean
there's
a
big
difference,
I
think
between
porting
patches,
that
are
functionality
into
backdrop
to
make
it
so
that
people
have
been
continuous,
upgrade
path
versus
like
borrowing
the
visual
style
of
Drupal
8.
A
That
could
just
lead
towards
some
sort
feelings
that
we
don't
really
want
to
get
into
that.
Okay,
so,
let's
see
other
miners.
Priority
is
themed
system
cleanup
which
jen
is
working
on
she's
been
filing
some
issues,
but
at
the
same
time,
she's
also
just
been
pushing
forward
in
various
other
issues,
very
small
things.
So,
let's
see
besides
the
software
itself,
which
is
coming
along
pretty
quickly,
we
have
some
peripheral
items
that
aren't
coming
along
so
quickly.
A
A
Let's
see
so,
besides
the
website,
we
also
need
some
other
things,
ultimately
we're
going
to
need
an
update
server
for
backdrop,
CMS
right
now,
when
you
install
backdrop,
it
connects
to
drupal.org
and
says
your
version
of
Drupal
is
out
of
date,
which
of
course,
isn't
accurate.
So
we
need
to
set
up
an
update
server.
The
makes
it
so
that
when
you
install
backdrop,
it'll
check
for
updates
against
backdrop,
CMS
org
deaths
largely
postponed
on
the
website
itself,
creating
an
official
github
service.
For
the
backdrop
CMS
project.
This
is
issue
number
eight.
A
This
is
basically
how
we're
going
to
handle
can
trip.
We
need
a
way
to
make
it
so
that
you
can
register
your
module
with
the
backdrop
CMS
org
website,
so
that
when
you
go
there
and
look
for
a
list
of
contributed
modules,
it
will
be
informed
of
those
things
via
github.
So
there's
issue
number
eight.
In
the
backdrop,
CMS
org
issue
queue
for
anyone.
That's
interested
in
undertaking
that
that
particular
one
requires
somebody
with
with
some
knowledge
in
Ruby.
A
So
in
a
few,
if
you
have
a
particular
interest
in
backdrop-
and
you
have
some
Ruby
skills,
we
can
use
some
assistance
there
and,
lastly,
there's
the
API
website.
Not
two
thousand
seems
like
he
was
going
to
put
this
together
and
we
think
that
that's
still
the
case,
but
we
haven't
heard
from
him
anytime
recently.
So
API
website
is
just
to
throw
up
the
API
documentation
since
backdrop
is
shifting
its
api's,
just
as
you
might
expect
in
a
new
release
of
triple
okay.
A
Today
is
is
backdrop
day
it's
sprint
day,
so
I'll
be
an
IRC
of
course
Jen
isn't
available
at
all,
so
she
won't
be
around
an
IRC
either,
but
but
I'll
be
around
in
IRC
dancer
any
questions
and
we'll
be
pushing
forward
with
a
couple
of
these
pull
requests
and
things
that
need
review.
That's
all
I've
got
and
Eve.
You
got
anything
else
to
add
or
any
notes
that
you
want
to
add
to
the
document.
I.
B
Was
encouraged
with
a
new
person
in
the
past
process
last
week,
a
Thursday,
unfortunately,
I
forgot
your
name,
but,
however,
you
are
you
remember
who
you
were
last
week.
If
you
were
there
and
I
was
available
to
let
you
know
how
the
patch
process
works,
and
it
is
very
easy
once
you
get
into
the
swing
of
it.
So,
if
you're
interested,
we
could
use
your
help
too,
and
that's
in.
A
A
Ya
hear:
there's
a
I'll
throw
this
in
the
notes
to
anyone
that's
interested
in
getting
in
contributing.
There
is
a
a
handbook
page
on
this
handbook
backdrop:
CMS
org,
slash
code,
/,
pull
requests
and
I
throw
that
through
that
into
the
notes
that
there's
video
for
anyone
that
isn't
familiar
with
using
github
or
how
pull
requests,
work
or
applying
patches.
It
goes
through
the
entire
process
of
how
to
set
that
all
up
and
Andy
with
your
hands
on
experience.
You
probably
also
I've
found
some
things
that
might
not
be
mentioned
in
that
video,
so
Andy.