►
From YouTube: Backdrop weekly 1/2
Description
Backdrop CMS
B
B
B
2012
anyway,
happy
2014,
okay,
so
I'll
just
go
ahead
and
start
running
down
the
agenda
and
if
other
people
want
to
join
in
the
can,
if
not
they'll
watch
the
video
later,
that's
fine.
So
thank
you
for
joining.
It
is
looks
like
myself
Nate
in
the
end,
either
here
right
now,
we'll
see
if
anyone
else
pops
on
later
and
high-level,
we
could
probably
take
these
off
pretty
soon.
The
reason
we're
here
is
because
there's
a
cost
that
comes
with
change
and
we
think
that
Drupal
8
is
changing
too
much
from
Drupal
7.
B
As
long
as
the
simplification
of
existing
systems,
in
addition
of
new
features,
doesn't
require
very
much
APA
API
change
to
accomplish,
and
we
would
like
backdrop
to
be
released
just
before
Drupal
8.
That's
what
we've
been
saying
all
along
I'm.
Looking
at
recent
timelines
for
when
Drupal
8
may
or
may
not
be
released,
it
looks
like
we
might
end
up
aiming
to
release
a
lot
sooner
than.
A
B
It
depends
on
how
fast
and
Drupal
8
is
able
to
pick
up.
Speed
notes
like
they've,
got
a
lot
more
work
to
do
than
we
do
in
terms
of
being
ready
to
release.
So
hopefully
that
means
we'll
get
done
earlier
and
we
can
start
working
on
updating,
contributed
modules
and
themes
as
well.
The
major
things
that
are
blocking
our
release.
B
Our
we've
got
a
couple
couple
of
big
items,
keeping
up
with
Drupal,
meaning
that
we
include
all
of
the
same
bug
fixes
than
one
into
Drupal
7
minor
changes
as
well
and
new
features
that
one
into
Drupal
8.
So
we've
got
a
bunch
of
meta
issues
that
include
those
I,
don't
know.
If
Andy
you
wanted
to
give
us
an
update.
I
know
you've
been
doing
a
bunch
of
work
like
crazy
this
morning
yesterday,
to
probably
on
getting
some
of
the
changes
from
Drupal
7
crash
ported
over
to
backport.
D
Well
I
still
too
long
and
the
short
of
it
will
be
I'll
have
a
other
cleanly
page.
Ports
are
done
for
the
three
men
issues
by
tomorrow
evening.
I
got
two
of
them
done
yesterday
and
then
the
other
one
is
about
half
done
from
earlier
days,
when
I
I
didn't
realize
the
time
the
timeline
so
I'll
have
those
by
Friday
night
and
then
the
real
work
will
begin.
Then,
because
then
we'll
have
to
figure
out.
B
B
I'll
I'm
happy
to
help
with
some
of
the
the
you
know.
Why
does
the
patch
not
a
pipe
up
like
Langley
stuff,
too
I'm
gonna
start
having
a
bunch
more
time,
is
work
on
this
now
that
it's
2014,
not
2012,
that
that
sounds
great
and
thank
you
so
much
for
putting
all
your
ear
time
into
working
on
that
yeah.
C
It
looks
like
from
these
poll
requests
for
request.
109
110
looks
like
there's
another
44
issues
in
there,
which
is
awesome,
so
I
saw
them
come
in
last
night
and
I
was
super
excited
about
it
and
II.
Thanks
for
for
your
work
on
back
porting
or
on
applying
all
those
patches,
I'll
probably
get
to
review
each
of
these
pull
requests
before
before
a
meeting
next
week.
B
Okay,
so
the
next
major
thing,
that's
preventing
our
release
of
backdrops
four-point-oh
is
the
config
management
and
I
know
that
we
got
the
base
system
committed
and
a
victor
volunteered
to
help
manage
the
list
of
remaining
conversions.
I'm
not
sure
if
there's
been
very
much
progress
on
that
in
this
holiday
season,
but
it
we
do
or
will
very
shortly
have
a
giant
list
of
little
tiny
things
that
anyone
who
doesn't
have
a
lot
of
time
to
volunteer
but
wants
to
come
in.
You
know
just
knock
something.
B
Little
off
can
can
pick
those
up
so
that'll
be
really
great.
We
in
kind
of
didn't
have
a
very
easy
jumping
in
point
for
a
bunch
of
people
until
now,
if
we're
gonna
have
a
bunch
of
great
little
things
where
people
can
kind
of
help
whenever
they
can
so
so
conversions
from
old
style
variables
to
new
cmi
conversions
from
our
old
content
type
configurations
to
see
my
stuff.
All
of
that
that
we
don't
currently
have
in
Drupal
7
that
we
want
interpolate
will
need
to
get
tackled.
B
C
Basically
the
version
of
views
that
we
have
ready
in
issue
number
forty
there's
a
matching
poll
request
for
it.
Let's
see
it
is
pull
request.
Number
108,
poor
request,
number
108
is,
is
pretty
much
ready
to
merge.
I
think
for
the
initial
pass.
All
of
the
tests
are
passing
all
of
the
views.
Implementations
are
all
distributed
across
all
the
individual
modules
and
we
pretty
much
have
complete
parity
with
the
Drupal
7
version
of
views.
C
So
it's
it's
looking
really
good,
but
we
still
have
some
more
work
to
do
to
actually
integrate
this
stuff
more
tightly
with
with
backdrop
itself,
so
I
made
a
bunch
more
follow-up
issues.
Things
like
we
need
to
implement
a
drop
button
handler,
which
is
a
piece
of
cake
that
will
make
it
so
that
we
can
replace
like
edit
and
delete
links
on
various
administrative
pages
with
drop
buttons.
C
You
know
like
unpublished
their
content
and
then
ban
the
account,
for
example,
and
views
bulk
operations
can't
do
all
of
that
together
and
so
what
they
did
in
Drupal
8.
Is
they
simply
kept
all
of
the
confirmation
forms
and
all
the
batch
operations
that
are
currently
being
used
for
nodes
and
users
and
just
wrote,
really
simple
actions
that
do
nothing
but
redirect
the
user
to
the
existing
pages
and
then
reuse
the
existing
forms
for
batch
operations,
so
Drupal
8
doesn't
actually
have
any
bulk
operations
or
or
batch
operations
or
cues
or
anything.
C
The
only
thing
that
it
really
has
is
it
has
an
integration
with
the
action
system
that
has
a
drop-down
list
of
actions
and
then,
when
you
hit
apply,
it
can
do
that
action
all
at
once,
and
so
because
it
doesn't
support
bulk
operations.
They
just
redirect
to
a
single
page.
That
then,
does
the
bulk
operations
on
the
objects
that
were
saved
so
anyway.
That's
our
next
big
task
in
in
views
lands
before
next
week's
meeting.
C
We
should
merge
and
views
branch
and
then
from
then
on
what
we're
going
to
be
test
with
is
converting
existing
listings
into
views
and
we're
going
to
run
into
this
problem
really
quickly
that
we
can't
convert
any
of
the
administrative
listings
until
we
have
this
equivalent
of
useful
corporations.
But
if
we
follow
the
same
path
that
Drupal
8
did
and
implement
this
simple
VPO,
it
should
be
really
pretty
easy,
endeavor,
like
probably
doable
within
another
week
or
two
so
there's
follow-up
issues
in
that
fuse
issue.
Issue
number
40,
there's
a
list
of
follow-up
issues.
C
B
Okay,
and
so
that's
awesome,
I'm
really
excited
about
views
being
almost
done.
I
thought
that
was
gonna
be
a
lot
harder
than
it.
Then
it
turned
out
to
be
yeah
I
to
look
next
up
on
the
list
is
blocks
and
layouts,
and
this
is
something
we
still
want
to
make
some
progress
on
before
release,
but
obviously
isn't
as
important
as
some
of
these
other
things
and
then
other
things
that
we
want
to
work
on.
We've
got
a
bunch
of
minor
things
that
we
should
be
aiming
towards
for
backdrop,
1
point
0
user
experience.
B
Improvements
is
one
that
we
talked
about
adding
on
to
the
agenda
recently
and
one
a
one
big
thing
that
falls
under
that
category
is
getting
a
WYSIWYG
editor
in
court.
We
have
a
Drupal
7
equivalent
to
the
WYSIWYG
editor
that
went
into
a
Drupal,
8
core
and
so
I
think
we
should
start
working
on
getting
that
working
for
backdrop
and
then
HSN
I'm
hear
the
dialogue
system.
So
that's
something
that
views
is
gonna
use
and
woozy.
C
Yeah
right
now,
the
the
dialogue
system
we
have
four
views
is
the
same
approach
that
Drupal
a
used,
which
is
basically
just
directly
poured
it
right
now
and
then
later,
like
views
is
using
its
own
dialogue
system,
essentially
right
now
and
then
later
switch
that
to
using
the
built-in
core
dialogue
system.
So
I'm
really
familiar
with
how
the
dialogue
system
works
in
Drupal
8
we'll
need
to
make
some
adjustments
to
how
we
build
that
out,
because
the
way
the
Drupal
8
does
it
it
it
utilizes.
B
And
there's
some
other
stuff
that
that
we've
been
talking
about
like
getting
a
better
tool
bar
in
their
triple
sevens.
Toolbar,
isn't
quite
as
nice
as
triple
Eight's,
toolbar
I'm,
not
sure
how
crazy
we
want
to
go
without
whether
we
want
to
make
a
drop-down
system
that
can
be
added
or
not
or
if
we
should
just
take
what
you're
Boyd's
done.
B
All
the
great
work
they've
done
on
the
toolbar
stuff
and
add
that,
but
there's
definitely
room
for
improving
the
toolbar
and
then
also
the
node,
add
edit
form
improvements
and
we've
talked
about
how
some
of
the
things
I've
done
in
Drupal
8
aren't
necessarily
improvements
like
replacing
this
event
on
with
a
drop
button.
That's
actually
an
item
list
or
don't
know
what's
going
on
in
there,
but
it
would
be
good
to
at
least
look
at
what
they've
done
in
Drupal
8
take
this
stuff.
B
We
really
like
make
sure
that
we
get
that
in
and
and
then
also
think
about
other
things
that
we
could
do.
I
know
around
workflows
and
and
there's
a
bunch
of
good
ideas
that
WordPress
has
that
we
were
looking
to
steal
as
well,
and
so,
if
anyone
is
particularly
interested
in
user
experience
stuff
and
wants
to
kind
of
give
back
drop
a
pass
over
and
say
you
know,
this
different
drew
place
is
imperative
versus
you
know.
B
Here's
some
other
stuff
from
outside
of
Drupal
that
we
want
to
get
in
there
to
be
good
to
have
a
lead
on
kind
of
the
user
experience
front
and
then
there's
going
to
be
a
bunch
of
smaller
issues
that
kind
of
come
up
as
we
continue
working
on
stuff.
That
would
be
good
to
just
kind
of
keep
track
of
and
make
sure
we
get
those
all
taken
care
of
before
launch.
B
Think
that
that
we
can
make
that
experience
a
little
bit
better
too
again.
We'll
have
to
keep
in
mind
how
much
we
can
actually
change
without
breaking
can
trip
breaking
API
so
that
contribute
to
also
be
good
to
have
a
team
there.
So,
if
anyone's
particularly
interested
in
the
theme
layer
and
doesn't
hate
PHP
template
too
much,
it
would
be
good
to
kind
of
way
change
versus
benefit
for
a
lot
of
these.
These
things
that
we're
going
to
be
dealing
with
so
feel
free
to
contact
me
about
that
too.
B
If
you
want
to
get
started
and
then
I
guess,
there's
been
a
bunch
of
progress
to
on
some
of
the
the
peripheral
things
that
we
have
to
do
a
round
backdrop.
We've
got
a
bunch
of
websites
and
tools
that
we
need
to
build
to
help
our
developers
primarily
backdrop
CMS
org
I
know:
we've
got
a
Luke
on
hand
to
help
kind
of
project
management,
the
whole
thing
which
will
be
really
great.
B
Michael
I
think
also
said
he
had
a
team
where
he
was
willing
to
loan
s
development
skills
to
so.
If
we
can
come
up
with
a
really
clear
project
plan
come
out
of
our
content
strategy
meeting,
knowing
what
we're
going
to
do,
I
think
we're
going
to
be
a
great
position
to
kind
of
hit
the
ground
running
on
that
one.
So
I
think
that
we've
got
a
good
team
in
place
for
the
website.
B
We
just
need
to
figure
out
what
we're
doing
and
then
he'll
be
able
to
take
over
pretty
easily
and
get
going
on
that.
So
that
makes
me
really
excited
I'm.
Looking
forward
to
working
on
that
here
in
the
new
year
as
well,
we
need
an
update
server
I
think
we
still
need
I
figure
out
how
we're
going
to
make
all
of
that
work.
B
So
we
need
some
planning
involved
there
too,
but
if
anyone's
particularly
interested
in
figuring
out
and
working
on
how
to
do
an
update
server
for
backdrop,
that
will
be
a
place
where
we
need
some
volunteers,
so
I
think
yeah
jump
in
there.
If
you
want
to,
we
also
need
an
official
github
service
so
that
people
who
create
modules
and
themes
on
github
can
register
them
as
being
for
backdrop
which
I,
don't
think,
is
a
lot
of
work,
but
it
does
in
does
require
that
you
are
familiar
with
Ruby
and
I.
B
B
I
know
that
we
had
not
volunteered
to
work
on
the
API
site,
but
I'm
not
sure
and
he's
had
any
time
over
the
holidays,
we'll
check
in
with
him
here
in
the
next
few
weeks
and
see,
if
he's
still
a
lil
related
to
work
on
that
or
interested
in
and
other
things.
Now
that
piece
is
coming
along.
He
might
be
more
interested
in
working
on
views,
but
well
we'll
check
in
and
see
what
he's
most
passionate
about
and
make
sure
that
he
has
time
to
do
whatever
it
is.
He
wants.
Yes,.
C
C
Conversion
I
ran
across
a
bunch
of
things
that
I
wasn't
even
aware
of,
because
you
know
backdrop
put
at
the
time
that
it
was
forked
still
had
over
a
year
of
Drupal
8
developments
actually
into
it,
and
there's
there's
a
number
of
change
logs
up
until
that
date
that
apply
to
us
as
well
that
as
I
was
converting
views
like
I
ran
into
things
that
I
wasn't
expecting
things
like
you
know,
taxonomy
get
vocabularies
no
longer
exists
and
other
weird
things
like
that.
I
mean
there's
the
big
things
that
I've
run
into
everywhere.
C
Like
you
know,
the
cash
system
is
now
rewritten
so
that
it
cash
objects
instead
of
just
being
cash.
Getting
cash
set,
so
I
run
into
that
all
over
the
place.
But
during
the
views,
conversion
I
ran
into
half
a
dozen
other
things
that
are
actually
already
existing
changes
that
that
we
inherited
from
early
Drupal
8
cycle,
and
we
need
to
document
those
as
being
specific
backdrop,
changes
and
then
then
also
include
all
of
the
stuff
that
we're
actually
changing
ourselves.
C
B
Okay,
I
think
that's
all
we
had
on
peripherals.
The
last
item
on
our
list
for
this
week
is
sprint's,
so
I've
got
one
more
thing.
I've
got
to
do
for
work
immediately
after
this
meeting,
but
then
I
should
be
available
to
start
working
with
you
guys
this
afternoon.
So
I
don't
know
if
Andy
there's
anything
that
you're
aware
of
already
that
you
are
worried
about
in
terms
of
things
not
merging
cleanly
from
Drupal
7.
B
You
want
to
point
me
at
if
not
then
I'll
probably
start
on
backdrop
website
stuff,
but
yeah
I'll
be
around
in
IRC
this
afternoon,
and
then
I
don't
know
if
there's
anything
else
either
at
knee
or
ND.
You
want
to
bring
up
in
this
meeting
or
stuff
that
you
think
we
should
add
to
the
agenda
for
every
upcoming
meeting.
But
let's,
let's
just
open
up
for
a
couple
minutes
and
see.
C
Yeah,
I
think
we've
been
running
over
this
agenda
and
every
time
we
get
to
the
website
stuff,
you
know
it's
like
a
whole
bunch
of
different
items
that
we're
not
making
a
lot
of
progress
on
at
least
currently,
but
we
do
have
a
lot
of
people
that
are
interested.
Maybe
we
should
look
into
separating
out
the
website
meeting
into
a
separate
weekly
call
yeah,
and
then
then
we
can
get
together
the
separate
team
for
the
website
development
team
and
have
a
meeting
specifically
for
them.
D
B
Okay
and
in
terms
of
like
we
do
have
a
completely
separate
website
team,
but
if
there
I
mean
maybe
I'll
talk
to
them
and
see,
you
know
what
it
is
that
they
need
to
talk
about,
because
if
that
does
start
taking
up
too
much
time
from
this
call,
it
would
make
sense
to
split
it
off,
doesn't
have
anything
yet
I
think
it
might
be
too
early.
Okay,.
C
B
Enough,
let's
get
them
going
and
see
and
see
what
comes
up
and
if
they
all
start
jumping
in
this
meeting
and
want
to
talk
about
stuff
about
the
website,
then
we'll
split
it
off
into
another
meeting.
So
that
doesn't
detract
from
this
one.
But
I
think,
since
this
meeting
still
is
under
half
an
hour
every
week,
we're
probably
fine
to
keep
it
as
one
until
it
starts
to
you
know.
We
need
a
bunch
of
other
stuff
to
talk
about
for
backdrop
and
we're
taking
too
long.
If
that
makes
sense,
yeah
totally.