►
From YouTube: Backdrop weekly 12/26
Description
Backdrop CMS
A
C
A
A
We're
hoping
we
know
that
they're
probably
won't
very
many
people
in
this
meeting,
Thank
You
Victor
for
joining
us.
That's
really
great
we're
hoping
that
a
bunch
of
other
people
might
have
time
in
the
next
few
days.
Hopefully,
they've
got
time
off
and
they'll
be
able
to
watch
the
video,
and
so
hopefully
I
will
so
still
get
some
some
follow
up
this
week.
For
starters,
I
just
wanted
to
really
quickly
go
over
the
goals
of
backdrop.
A
A
Our
timeline
is
that
we
want
to
have
backdrop
done
at
the
same
time
or
slightly
before
Drupal
8,
and
since
we
don't
really
know
what
your
plate
is
done,
we
don't
really
know
what
backdrop
will
be
done,
but
we're
going
to
try
and
use
the
time
we
have
to
make
the
most
important
significant
changes
and
then,
at
some
point
we'll
say:
okay,
it's
good
enough.
Let's
go
ahead
and
ship
it
and
then
we'll
start
working
on
making
sure
we
have
a
contribute
on
that
can
support
backdrop
as
well.
A
So
our
progress
report
will
cover
up
with
a
couple
of
different
things
that
we've
been
working
on
and
we've
got
a
bunch
of
issues
where
we've
been
trying
to
a
backboard
or
cross
port
fixes
from
Drupal
7
into
backdrop,
and
so
we've
got
I.
Think
three
issues
on
github
Republic
around
those
I
know.
Michelle
has
been
doing
a
really
great
job
of
keeping
track
with
them,
and
we've
got
Andy
working
on
doing
a
bunch
of
the
back
ports
too.
I.
A
B
A
Wants
to
work
on
those,
that's
not
not
too
terribly
complicated
and
goes
pretty
quickly
and
then
we've
got
a
couple
of
big
major
projects
were
working
on
as
well,
so
I
config,
cmi,
there's
a
big,
exciting
announcement
there
and
that's
that
Sam
I
was
committed
last
week
after
our
last
meeting.
So
let's.
B
See
mi
is
see
my
is
officially
in
with
some
basics.
It
saves
the
system,
performance,
page
and
image.
Styles
are
currently
the
first
two
things
that
are
converted
and
that
unblocks
us
to
make
it
so
that
we
can.
We
can
move
forward
with
views
as
well,
which
is
another
item
on
our
agenda
so
that
next
we
are
going
yes,
sir.
Okay,
well.
A
Maybe
we
should
talk
about
Vic
here
too
so
I,
just
grunts
TMI
Victor
you've
offered
to
help
us
manage
that
all
of
the
conversion
issues
which
will
be
really
exciting.
We
know
you're
busy
with
treats
you
prepped
now,
but
after
that,
and
he
said
he
was
going
to
take
from
the
metal
list
of
creating
long
things
need
to
be
converted
and
also
tackling
some
of
those
conversions
for
us.
I
think
that'll
be
really
helpful
in
terms
of
the.
B
First
one:
so
the
the
most
obvious
thing
to
convert
is
variables,
variable
get
variable
set
and
we
have
an
equivalent
function
just
with
one
extra
parameter,
config
yet
and
configset.
So
for
the
most
part
replacing
config
yet
with
you
know
very
very
variable,
get
with
config.
Yet
it
is,
it's
probably
the
most
straightforward
one
to
start
on.
But
then
after
that
I
mean
there,
you
can
probably
find
the
Drupal
8
meadow,
which
I
don't
think
I've
found
yet,
but
we've
got
all
the
other
things
you
know,
we've
got,
we've
got
content
types
vocabularies
menus.
You.
B
There's
there's
there's
an
enormous
amount
of
stuff
that
needs
to
be
converted.
Oh,
but
yeah
variables
are
probably
the
first
one,
I
would
say,
and
then
you'd
like
to
do
all
of
them
at
once.
There's
I
think
280
variables
in
Drupal
core
that
you
know
it.
Jim
burning.
All
of
those
all
at
once
would
probably
be
a
lot
of
effort,
so
probably
14
module
would
make
sense.
Do.
A
A
Some
time,
looking
at
that
Victor
and
typing
us
an
IRC
and
see
if
we
can
find
some
way
to
break
that
down
into
more
manageable
chunks,
I
would
imagine
if
you
can
find
the
Drupal
8
met
a
conversion
issue.
They've
already
done
a
lot
of
this,
like
figuring
out
what
manageable
chunks
are
stuff
I'm,
so
we
can
kind
of
steal
their
ID
effort,
I.
C
Would
think
at
a
minimum
you
should
be
able
to
cover
the
same
stuff
that
features
yes
yeah,
so
so
I'm
working
a
lot
on
that
so
I'm
pretty
familiar
season
features
extra
okay
like
stuff,
like
users,
will
not
have
you
us.
They
have
a
you,
you
Maggie,
but
that's
a
whole.
This
debate
so
we'll
leave
that
for
later,
but
I
certainly
variables
all
stuff,
like
that
name.
It
features
extra.
So
I
think
that
would
be
one
guideline
I
mean
I
can
minimum.
C
We
should
be
able
to
cover
the
same
as
google,
seven
with
cases
and
futures
egg
after
then,
then,
whatever
other
stuff,
to
do
Polly
besides,
you
know
that,
but
it
needs
to
do.
I
mean
Lynn
and
the
overall
objective
again
as
far
as
I'm
concerned
is
to
be
able
to
work.
Like
any
other
framework,
you
know,
with
everything
in
cold
right
to
separate
the
configuration,
the
pathological
mixture
of
the
Gotham
of
configuration
and
contact.
So
that's
that's
on
one.
Another
thing
is
up:
I,
don't
know
how
you
guys.
C
We
have
the
uuid,
the
content,
features,
module
and
the
node
export
module,
which
allows
you
to
have
demo
content
in
feature
now.
This
is
this
really
is
out
of
scope.
Isn't
it
Frank
tell
because
it's
more
like
a
deploy
question
of
content
or
a
demo
module,
or
something
would
be
like
that
demo
framework
to
some
of
it,
so
so
very
good,
so
I'll
take
I'll.
Take
it
from
me.
I'll
try
and
get
at
least
one
to
request.
C
B
Yeah
and
we've
made
an
enormous
amount
of
progress
kin
in
views.
There's
issue
number
40
is
convert
of
used
back
and
last,
even
at
last
meeting.
We
had
it
to
the
point
that
views
was
saving
and
you
can
edit
views
in
backdrop,
which
is
great
I've
pushed
up
several
more
commits
that
get
it
so
that
views
is
now
pretty
much
fully
functional.
You
can
create
edit
delete,
clone
import,
export
and
all
of
the
variables
in
views.
Module
itself
have
all
been
converted
to
cmi
as
well.
B
So
there's
no
more
variable
get
a
variable
set
in
views
at
least
they're.
There
are
a
couple
extra
variables
there's
a
new
issue
that
I
just
opened
a
day
before
yesterday.
I
think
that
is
we
need.
We
need
some
system
akin
to
Drupal
8
state
system
because
there's
some
variables
the
one
variable
in
particular
the
views
stores
a
hash
like
a
temporary
hash
and
in
this
variable
set
and
then
and
then
this
variable
get
later
to
to
pull
back
from
it.
B
But
that's
not
actually
configuration
it's
just
views
using
the
variable
system
as
a
state
system,
so
kind
of
like
a
there's.
A
bunch
of
variables
like
this,
like
a
does.
The
menu
need
to
be
rebuilt
or
does
when
was
the
last
time.
Cron
was
wrong.
Things
like
that,
aren't
actually
configuration
they're,
just
a
temporary
state
yeah,
and
so
so
I
made
a
new
a
new.
B
We
don't
have
a
couple
of
ctools
handlers,
converted
for
doing
like
mathematical
expressions,
so
we'll
need
to
move
those
over
and
probably
at
this
point,
like
I'm
feeling
really
really
good
about
views
like
again
like
it's,
it's
a
ton
further
than
like
the
initial
commit
for
Drupal
8,
so
I'm
feeling
like
that
should
happen.
Definitely
in
the
next
two
weeks
we
should
commit
our
first
iteration
of
views
and
then
probably
the
first
order
of
business
of
courses
is
converting
court
listings,
but
converting
corn
listings
means
that
we
also
need
views
bulk
operations.
A
B
Our
initial
conversion
has
really
been
really
successful,
though
I
included
an
upgrade
path
and
there
already,
which
I
tested
out
a
couple
of
times
against
my
drupal
7
sites
and
upgraded
them
to
backdrop
with
all
of
the
views
intact,
and
they
all
moved
over
perfectly.
So
I
think
that
that
we're
looking
really
good
as
far
as
like
conversion
goes
because
again,
like
art,
our
version
is
so
similar
to
the
one
in
Drupal
7.
B
B
A
A
So
if
anyone
who's
watching
this
broadcast
is
interested
in
being
our
I've
used,
converging
master
we're
going
to
one
of
those
starting
here
in
the
next
week
or
two
as
well
and
next
item
on
our
list
is
locks
and
layouts,
which
is
something
that
Nate
will
probably
start
thinking
about
after
we
get
it,
you's
conversion
them
and
that's
a
minute.
We've
done
a
lot
of
talking
and
hand
waving
about
so
far,
but
it's
not
been
a
a
big
enough
priority
to
actually
work
on.
A
Yet
so
I'm
excited
that
we're
going
to
get
start
thinking
about
that
for
real
pretty
soon,
and
then
we've
got
a
couple
of
minor
projects
that
we're
working
on.
At
the
same
time,
we've
got
the
theme
system
cleanup,
which
I
will
start
working
on
as
soon
as
we
are
in
encode
as
soon
as
we
get
all
of
the
Drupal
7
conversions
done.
So
I've
got
some
time
coming
up
in
the
next
few
weeks.
A
So
if
anyone
can
think
of
anything
that
might
be
better,
maybe
we
can
get
some
testing
done
and
see
how
that
goes
as
well.
And
then,
of
course,
we've
got
a
bunch
of
peripheral
things.
We
need
to
work
on
as
well
other
than
backdrops
internal
code.
Now
we're
going
to
need
a
backdrop
CMS
or
website.
We've
been
talking
about
this
for
a
while
as
well
we're
gonna
start
on
Drupal
7
and
we're
going
to
upgrade
to
backdrop.
A
So
it'll
be
a
really
good
test
case
of
upgrading
from
a
Drupal
7
site
to
backdrop
which
will
be
fun
and
got
some
people
are
on
hand
for
design.
We
need
some
more
help
with
content
and
content
strategy
figure
out
what
our
messaging
is
and
how
we're
going
to
say
it
in
a
way
that
makes
sense
and
then
beyond
the
Drupal
or
the
actual
website,
we're
also
going
to
need
an
update
server
so
that
backdrop
can
tell
which
versions
it's
running
and
keep
sites
notified
in
over
their
status.
A
B
So
that
that
is
on
top
of
the
main
website
itself,
though
yeah.
So
we
need
the
main
website
first
and
we
don't
have
even
even
a
starting
on
it,
so
anyone's
interested
in,
like
literally
starting
from
from
the
beginning.
You
know
checking
out
a
Drupal,
7
repository
and
starting
to
set
up
a
site,
get
in
touch
with
me,
and
I
can
give
you
prudential
store
to
our
servers
and.
A
D
A
A
A
Okay,
so
if
anyone
else
wants
to
pitch
in
an
API
say,
it
sounds
like
Matt
to
thousands
our
guy
for
that,
so
we
can
get
you
talking
to
him
and
do
some
brainstorming
thing
get
moving
on
that
as
well.
We
aren't
really
expecting
anything
in
the
next
few
weeks
here,
just
because
everyone
is
traveling
hint
otherwise
over
the
holidays.
So
today
we'll
probably
have
a
little
bit
of
time
to
do
some
sprinting.
B
A
B
So
on
on
our
final
note,
do
we
have
anything
to
be
added
to
the
agenda?
I've
been
thinking
that
we
should
probably
add
in
a
wysiwyg
initiative
at
some
point.
Okay,
obviously,
like
I'm,
really
really
familiar
with
the
waist
week,
conversion
in
Drupal
8
there's
actually
some
benefit
to
delaying
it
longer,
because
it's
still
improving
like
when
where's
and
ck
editor
team
match
is
still
moving.
B
The
wikileaks
stuff
forward,
even
more,
but
I
don't
think
much
of
that
is
is
actually
critical
like
whistling,
is
already
in
a
really
really
good
place
in
Drupal
8,
and
we
can
move
that
back
well.
Actually,
we
don't
even
need
to
move
some
of
it
back,
because
we
can
actually
use
the
stick
and
it
basically
the.
B
Module
which
was
actually
already
a
back
pores
or
a
port
of
the
WYSIWYG
functionality
before
it
got
rewritten
so
so
we
had
like
the
version
before
it
was
rewritten
might
actually
prove
to
be
a
pretty
good
starting
point
for
setting
up
all
of
our
hooks
and
the
way
plug-in
system
with
some
CGI,
your
plugins
that
is,
and
so
so
that
could
be
good.
A
good
start
for
another
project.
B
I'm,
not
really
sure
where
the
priority
is.
You
know,
like
this
views
thing
I,
think
that
will
probably
find
people
to
do
to
pick
up
views
and
then,
after
use,
I'm
wondering
like
up
I
should
look
at
like
we've
got
two
blocks
and
layouts
as
another
thing,
but
I'm
not
really
sure
is
wysiwyg
or
blocks
and
layouts
takes
precedence.
So
we
need
to
figure
that
out.
Okay.
A
A
C
Just
mention
about
and
mark
down
support,
I
think
would
be
very
interesting
because
you
know
use
it
so
much
in
github,
I
know
from
a
developer
perspective
and
not
so
much
we're
talking
about
a
end
user
experience,
but
a
markdown
could
be
a
great
content
strategy
tool
to
encourage
people
to
use
it.
I
I.
A
Think
what
we
should
do
with
markdown
is
marked
on
is
definitely
something
we
should
leave
to
come
true,
but
what
we
should
do
is
just
be
really
careful
with
how
the
WYSIWYG
is
implemented,
so
that,
if
someone
wanted
to
add
a
markdown
filter,
it
so
happens
really
easily.
So
it's
a
kind
of
a
drop
in
thing
like
oh
I,
want
mark
down
on
this
content
type
and
you
can
plug
it
in,
and
our
interface
should
allow
that
really
easily.
A
C
B
Yeah
and
there's
actually
some
opportunity
to
like
it
like
you're
right
that
are,
our
developers
are
going
to
be
using
markdown
quite
a
lot
because
they're
using
github,
we
may
do
things
like
the
API
website
or
the
main
backdrops
dms
org
website.
We
may
actually
include
markdown
as
an
option
for
different
users
on
our
own
site
to
keep
it
familiar
between
flipping
between
github
as.
B
Yeah,
I
don't,
I
don't
think
markdown
will
be
part
of
the
project
at
least
not
well.
Definitely
not
one
point
no,
but
you
know
I'm
not
really
sure
if
I
see
it
in
the
future
either,
but
well,
we'll
see
as
we
go
forward
I.
It
is
a
good.
You
know
a
good
candidate
for
furniture
bid
module
at
this
point,
I
think.
A
C
What
I
just
want
to
add
that
I
did
do
the
spanish
language
presentation
on
backdrop
and
I'll?
Send
you
guys
as
soon
as
d
video
comes
out
I'll,
send
you
guys
the
link?
So
maybe
people
who
you
know
who
could
you
know
maybe
never
really
heard
about
what
expert
is
ruled
out
because
of
the
language
phone
and.